Hello everyone,
I want to flash HadesROMv3 on my GalaxyS8 Exynos which is currently on OneUI 1.0 / android 9 with april 2021 security patch (oddly I haven't get the november 2021 patch).
But I have never done such a thing before and even after going through a lot of threads here on XDA and on other websites I still have a few concerns about the process (English isn't my native language so it's not always easy to gather information here and there).
I will recap here what I understand I have to do :
- Activate OEM Unlock + USB Debugging, reboot in download mode.
- Flash TWRP with Odin.
- Boot in TWRP, format data.
- Install HadesROM in TWRP.
- Setup and boot.
For the few steps above I know how to do them but here are my concerns :
1) What is the thing with RMM/KG State Prenormal ? I read a lot about it but when I go into Download Mode I have nothing that looks like RMM/KG State saying "Checking", "Prenormal" or I don't know what (see picture below). Does that mean that I won't have any problem regarding this issue and I don't have to worry about it ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(edit : i forgot to activate OEM unlock before doing the above picture but when I do so it only change "FRP Lock" and "OEM Lock" to "off")
2) Do I need to flash no-verity-opt-encrypt ? It looks like yes according to what I read on XDA but I haven't seen any tutorial that says anything about that.
3) Do I need to flash RMM-State_Bypass (link) ? Since I'm not having "prenormal issue" and since RMM Bypass seems to be included in Hades Rom I would say that I don't need to flash it but I'm not sure.
4) If I indeed have to flash one or both of the above, when do I need to do so in the process ? And which one before the other ?
5) Do I need to do anything to be able to use banking apps (something about SafetyNet) or is it okay since I'm only flashing a ROM and not rooting my device ?
Thanks in advance !
And sorry if answers to these questions are easily findable, I read a lot and couldn't find 100% trustable answers...
I also posted this on reddit and I got a very complete answer.
Here it is below, in case anyone is interested.
2. no-verity-opt-encrypt is 2 in 1
- disable dm-verity
- disable forced encryption
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
https://twrp.me/samsung/samsunggalaxys8.html
that's what this zip does. it disables dm-verity in the fstab (if partition is rw). if you ignore this warning, OneUI won't boot anymore just because TWRP is installed. unrelated to rooting. does not concern custom ROMs.
furthermore TWRP does not support samsung encryption. therefore TWRP backup feature (main purpose of TWRP) only available if unencrypted. but encryption is enforced on boot. this zip disables the enforcement. it does not actually unencrypt anything, this is still your own task (requires formatting)
aIecxs said:
2. no-verity-opt-encrypt is 2 in 1
- disable dm-verity
- disable forced encryption
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
https://twrp.me/samsung/samsunggalaxys8.html
that's what this zip does. it disables dm-verity in the fstab (if partition is rw). if you ignore this warning, OneUI won't boot anymore just because TWRP is installed. unrelated to rooting. does not concern custom ROMs.
furthermore TWRP does not support samsung encryption. therefore TWRP backup feature (main purpose of TWRP) only available if unencrypted. but encryption is enforced on boot. this zip disables the enforcement. it does not actually unencrypt anything, this is still your own task (requires formatting)
Click to expand...
Click to collapse
Thanks for your precisions !
To be sure I have correctly understood : "does not concern custom ROMs" means that I don't need to flash it if I'm installing a custom rom right ?
edit : I want to do a backup before installing the rom so I'll need to flash it (correct?).
you can't backup from TWRP because userdata partition is encrypted
aIecxs said:
you can't backup from TWRP because userdata partition is encrypted
Click to expand...
Click to collapse
Yes so in order to do a backup I need to flash no-verity-opt-encrypt before backing up ?
I don't understand. removing encryption requires formatting userdata partition (factory reset) - backup of empty partition is pointless
Oh okay I'm sorry I think I haven't really understood...
So just one simple question : do I need to install no-verity-opt-encrypt in order to flash HadesRom, yes or no ?
No, HadesRom is prepatched against both
Okay, thanks again !
Related
Hello, I have a root issue. I have an Axon 7 2017G V1.2.0B08 with unlocked bootloader and TWRP. Anyway, when I try to flash SuperSU (2.82), it does not give to me the root access. I mean, when I open the app of SuperSu, it alert to me "Root undetected". Can you help me?
Thanks,
youngz
Try Magisk 14
youngz89 said:
Hello, I have a root issue. I have an Axon 7 2017G V1.2.0B08 with unlocked bootloader and TWRP. Anyway, when I try to flash SuperSU (2.82), it does not give to me the root access. I mean, when I open the app of SuperSu, it alert to me "Root undetected". Can you help me?
Thanks,
youngz
Click to expand...
Click to collapse
Version 2.82 is crap. Users of my toolkit had bootloops because of it. Use 2.79 instead.
Hi, I tried to flash supersu 2.79 and the result is the same.
In order to flash magisk 14, I have to do some particular procedure o I have to just flash it?
Edit: furthermore, I want to modify the host file in system partition. But if I use only magistik, I suppose to be not able to modify that partition.
youngz89 said:
Hi, I tried to flash supersu 2.79 and the result is the same.
In order to flash magisk 14, I have to do some particular procedure o I have to just flash it?
Edit: furthermore, I want to modify the host file in system partition. But if I use only magistik, I suppose to be not able to modify that partition.
Click to expand...
Click to collapse
Just wipe system, reflash your ROM and then flash Magisk. I didn't understand what you said about the 'host file', if you mean that you wanna use adaway then yes you should be able to use it
Yes, I means adaway. Thanks for your reply! Another information. I have to wipe also the data partition? It will be boring install again all my apps, SMS, and stuffs..
youngz89 said:
Yes, I means adaway. Thanks for your reply! Another information. I have to wipe also the data partition? It will be boring install again all my apps, SMS, and stuffs..
Click to expand...
Click to collapse
Your phone is encrypted if you didn't install magisk or supersu. If you want to install a new ROM you will have to format data (which means losing the internal storage too). But you don't need to wipe anything to instal Magisk. Just a suggestion, make a system backup
Thank you for your suggestions. I had reinstalled the system and I flash magisk 14. Anyway, now, when I open the application and I start the check, the app return:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Furthermore, when I try to install some software, it return an error about the partition mount:
Have you any solution about these problems?
Thanks
youngz89 said:
Thank you for your suggestions. I had reinstalled the system and I flash magisk 14. Anyway, now, when I open the application and I start the check, the app return:
Furthermore, when I try to install some software, it return an error about the partition mount:
Have you any solution about these problems?
Thanks
Click to expand...
Click to collapse
Alright. What did you do to install the system again with magisk? Tell me step by step
Ok, my steps:
1) Wipe caches, system, and data with twrp
2) flash the bootstack
3) flash the rom
4) flash magisk 14
5) flash again twrp (as precaution)
6) boot the os and config it
7) update magisk app mannualy with the last version
I also use a command (reboot disemmcwp) from twrp shell to enable the writing on system partition but the result was the same.
Maybe I have a solution (maybe). In twrp, I set the system partition as read only. Anyway, could I remove it without risk (as an overwriting of recovery or bootloader)?
Thank you.
Unofficial release -TWRP recovery for the Galaxy SM-M105F/DS, Exynos7870
About Samsung Galaxy M10
Here are some of the key features and specifications of the newly launched Samsung Galaxy M10 smartphone.
- Firstly, it has a 6.22 inches display with a resolution of 720 by 1520 pixels. A total of 270 pixels per inch.
- And Samsung Galaxy M10 also comes with Android 8.1 OREO.
- And under the hood, the phone has an Exynos 7870 chipset.
- The Phone also comes with 3GB/2GB Ram and 32GB/16GB Storage.
- Furthermore, the camera sensor is – 13MP + 5MP dual rear camera and 5MP front shooter.
- Finally, the battery on the phone is a non-removable 3400 mAh.
tested on SM-M105F with android 8.1.0 (must work in other models but not tested).
-mtp not work in linux
if adb not work disable MTP from mount menu in recovery
use odin or heimdall for flash recovery image.
use Magisk 18.1 for rooting.
before flash recovery file you need to unlock bootloader with OEM unlock from developer options.
Heimdall file ----> download
Odin file ----> download
use latest kernel source from opensource.samsung.com and A3 2017 official device three for building.
hi there can you provide step by step installation guide please.. appreciated!
Hello thank you for your work, i have a SM-M105F from India in Germany.
I have unlocked the OEM Bootloader and Reset the Phone.
Twrp installed with Odin and Boot into Twrp work.
The System not Booting. It is in Bootloop, but Twrp work.
I have now install the Official Firmware back with Odin.
I need to make TWRP an System work parallel with Root.
I need Help.
gtabuni said:
Hello thank you for your work, i have a SM-M105F from India in Germany.
I have unlocked the OEM Bootloader and Reset the Phone.
Twrp installed with Odin and Boot into Twrp work.
The System not Booting. It is in Bootloop, but Twrp work.
I have now install the Official Firmware back with Odin.
I need to make TWRP an System work parallel with Root.
I need Help.
Click to expand...
Click to collapse
Maybe try flashing 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
EDIT: Flash Magisk zip too (it removes dm-verity), and format the data partition
Thank you for your good tips, i need to test it.
gtabuni said:
Hello thank you for your work, i have a SM-M105F from India in Germany.
I have unlocked the OEM Bootloader and Reset the Phone.
Twrp installed with Odin and Boot into Twrp work.
The System not Booting. It is in Bootloop, but Twrp work.
I have now install the Official Firmware back with Odin.
I need to make TWRP an System work parallel with Root.
I need Help.
Click to expand...
Click to collapse
by default dm-verity is active for system , vendor and odm partitions. you can use magisk to disable it
surbiks said:
by default dm-verity is active for system , vendor and odm partitions. you can use magisk to disable it
Click to expand...
Click to collapse
so just flash magisk to remove dm-verity and get root ?
madi3d8 said:
so just flash magisk to remove dm-verity and get root ?
Click to expand...
Click to collapse
yes. use magisk
please make a more detailed tutorial because I have already burned my phone a faith and I want to be sure of what I am doing this faith. thank you
This work for m105g?
No, its not
BlacklightMG said:
Maybe try flashing 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
EDIT: Flash Magisk zip too (it removes dm-verity), and format the data partition
Click to expand...
Click to collapse
where is 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
madi3d8 said:
where is 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
Click to expand...
Click to collapse
RMM Bypass: https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
no-verity-opt-encrypt: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
ojol Cipinang said:
This work for m105g?
Click to expand...
Click to collapse
i dont know, you must test, but its must be work
surbiks said:
i dont know, you must test, but its must be work
Click to expand...
Click to collapse
I have tested at m105g twrp It was successfully installed and the root was successful but after rebooting I was stuck on a screen that read "storage of damaged devices" please reset your device. Always like that ... help me
Please TWRP for SM-A105G/DS
Can we flash gsi image with this recovery??
I got an error
I do everything infact after install twrp i also install the no verity opt and rmm bypass but i still got this **** error everytime i boot my phone..
Data is corrupt reset your mobile i do it many times but same again bootup and gives this msg...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have on my SM-M105FD the Firmware 8.1.0 and Working Root. With twrp System not work.
Download the Firmware 8.1.0 on the PC and the AP File put on the Phone.
Download and install magisk apk on your Device and patch the AP in Magisk file.
flash the Firmware full with Odin but put on the AP Option the Patched AP file flash and work.
I have with Magisk install the Xposed Framework and install nice plugins.
gtabuni said:
I have on my SM-M105FD the Firmware 8.1.0 and Working Root. With twrp System not work.
Download the Firmware 8.1.0 on the PC and the AP File put on the Phone.
Download and install magisk apk on your Device and patch the AP in Magisk file.
flash the Firmware full with Odin but put on the AP Option the Patched AP file flash and work.
I have with Magisk install the Xposed Framework and install nice plugins.
Click to expand...
Click to collapse
How to unlock the bootloader M10? is It enough by enabled OEM unlock option?
Hi Guys,
My son has a MI9T.
Hé wanted to flash a custom rom the day after he got this phone from me (why i dont know) but he never did it before. And i aM no expert either.
Hé installed a few custom kernals, and roms and TWRP'S and dont actually know what hé is dooing.
But the phone is stuck in startup screen with Every rom he installed so far.
Hé did no backups from the working device either........???
The phone have working TWRP now and unlocked bootloader.
i tried to do the Xiaomi recovery (Miflashtool) but wont work either cuz of the fault:
Anti Rollback protection and i cant find a right firmware for IT.
The anti rollback protection is on 1 on this phone.
Can Any one help me out maybe?
or is the phone already to throw away?
Hi. The anti-rollback protection exists purely in a file in the fastboot image. Here is a tutorial on how to avoid triggering it on our device:
https://telegra.ph/Fix-fastboot-flashing-problems-09-20
The reason that no roms he tried are booting is most likely that on this device he has to wipe data + internal storage after flashing or it will most likely not boot.
nckmml said:
Hi. The anti-rollback protection exists purely in a file in the fastboot image. Here is a tutorial on how to avoid triggering it on our device:
https://telegra.ph/Fix-fastboot-flashing-problems-09-20
The reason that no roms he tried are booting is most likely that on this device he has to wipe data + internal storage after flashing or it will most likely not boot.
Click to expand...
Click to collapse
i tried to do that but now i have an error: flash crc list error
so it wont work either i guess.
olso tried to flash another rom and did wipe data + internal storage but no effect, still stuck in startup.
Bramcl said:
Hi Guys,
My son has a MI9T.
Hé wanted to flash a custom rom the day after he got this phone from me (why i dont know) but he never did it before. And i aM no expert either.
Hé installed a few custom kernals, and roms and TWRP'S and dont actually know what hé is dooing.
But the phone is stuck in startup screen with Every rom he installed so far.
Hé did no backups from the working device either........???
The phone have working TWRP now and unlocked bootloader.
i tried to do the Xiaomi recovery (Miflashtool) but wont work either cuz of the fault:
Anti Rollback protection and i cant find a right firmware for IT.
The anti rollback protection is on 1 on this phone.
Can Any one help me out maybe?
or is the phone already to throw away?
Click to expand...
Click to collapse
Download the latest fastboot rom for your device. Extract it and open the flash_all.bat file with Notepad++. Remove all the lines before "fastboot% erase.." line. Then run the bat file.
Preetam286 said:
Download the latest fastboot rom for your device. Extract it and open the flash_all.bat file with Notepad++. Remove all the lines before "fastboot% erase.." line. Then run the bat file.
Click to expand...
Click to collapse
thx for reaction
i deleted lines and made sure that fastbootlines start on 1st line now
but now its says flash crclist error.
Try to Flash fastboot rom from EDL mode... You have unlocked bl, download this tool
https://github.com/Saki-EU/XiaomiAD...ad/6.6.2/XiaomiADBFastbootTools-6.6.2-Win.zip
Put phone with this tool in EDL mode and try to flash fastboot rom.
Bramcl said:
thx for reaction
i deleted lines and made sure that fastbootlines start on 1st line now
but now its says flash crclist error.
Click to expand...
Click to collapse
Move the fastboot rom folder (with the modified bat file) to C:/. Then try flashing again with miflashtool.
nothing worked for me. tried all the above and many other tricks but no.
zkrayem said:
nothing worked for me. tried all the above and many other tricks but no.
Click to expand...
Click to collapse
OK! Let's try something different. First of all, the phone is not dead, so, don't worry. We just have to figure it out.
Enter TWRP, format DATA, tipe Yes (it's not wipe, it's format data).
Just to be sure, flash the latest TWRP https://dl.twrp.me/davinci/twrp-3.4.0-0-davinci.img
Since you formated data, you will have no files on your phone (be shure of that, if it isn't empty, you haven't formated data), you have to tranfer this TWRP from the computer or OTG.
After flashing TWRP, reboot to recovery. Now, let's flash some stable rom. Try this: https://sourceforge.net/projects/xi...K20MI9T_V12.0.4.0.QFJCNXM_v12-10.zip/download
Flash only the rom (no magisk, nothing). Reboot! Now, wait patiently. The first boot will take time (from 5 to 10 minutes).
Then, give us feedback. Ground your son until the weekend. Good luck, mate!
Hi
Do you find solutions???
used the above steps except edl mode and was able to sucessfully flash fastboot rom without crc list error
RCstZero1 said:
Move the fastboot rom folder (with the modified bat file) to C:/. Then try flashing again with miflashtool.
Click to expand...
Click to collapse
Thanks, mate for the suggestion. Initially was getting anti-rollback check then crc error. Your suggestion save my day. Again Thankyou very much. In the end, got this error but the device booted successfully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the post, my question didn't really get answered on the General Q&A Nood Friendly Thread:
Xenophoresis said:
I have Android 9 and August 1, 2020 security patch on it (YouTube was mentioning security patches? dunno why).
I would like TWRP and a future goal of changing to Lineage OS/Tissot.
Which rooting guide can I follow?
( I got confused with the available threads.)
Click to expand...
Click to collapse
After posting, I tried follow this guide thread
I was able to do step 1 which is to unlock but, I don't know if I should still be flashing a Stock Fastboot ROM?
Also there is no link for TWRP, or which version of TWRP I should get...
The last time I rooted something was a Galaxy Note 2 back in 2012-ish so my relevant knowledge is definitely expired.
Please give me a lead on where to find the correct TWRP file and further instructions.
you want step by step guide to flash custom rom?
- You have unlocked bootloader?
- what OS version you are on at the moment ?
Dont worry i will help you in best of my knowledge i have been through what you are going after some time i learned answer question and we will begin
Yes, my bootloader is already unlocked and fastboot was enabled.
OS is stock Android 9, Aug 2020 security patch:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No Fastboot ROM (if that is necessary) or TWRP is installed yet.
PS: I do not know where or which TWRP I should be getting for this phone
Xenophoresis said:
Yes, my bootloader is already unlocked and fastboot was enabled.
OS is stock Android 9, Aug 2020 security patch:
No Fastboot ROM (if that is necessary) or TWRP is installed yet.
PS: I do not know where or which TWRP I should be getting for this phone
Click to expand...
Click to collapse
There is a tutorial u can follow on youtube by Vikram, for Pie with August 2020 patch. N u can download what it needs in the description. Its in Indian language but u can follow what he do. Should be okay n safe
Good luck
Lost149ers said:
There is a tutorial u can follow on youtube by Vikram, for Pie with August 2020 patch. N u can download what it needs in the description. Its in Indian language but u can follow what he do. Should be okay n safe
Good luck
Click to expand...
Click to collapse
I was hoping to get instructions or help in English; I've watched his YouTube tutorial in Indian but I was afraid that I'd do something wrong because I didn't understand what he said.
You can follow the instructions provided for LOS:
https://wiki.lineageos.org/devices/tissot/install
Simply exchange the LOS installing part with the ROM of your choice.
Xenophoresis said:
I was hoping to get instructions or help in English; I've watched his YouTube tutorial in Indian but I was afraid that I'd do something wrong because I didn't understand what he said.
Click to expand...
Click to collapse
timeo78 said:
You can follow the instructions provided for LOS:
https://wiki.lineageos.org/devices/tissot/install
Simply exchange the LOS installing part with the ROM of your choice.
Click to expand...
Click to collapse
Thank you, I'm done with the custom rom and root
Sorry for late reply i couldn't login because of xda forum migration process
steps i used:
- install Twrp (download latest version details below)
- download custom rom and gapps (and transfer it into sdcard or internal storage or your phone)
- download Adb/fastboot tool and drivers (download it in windows pc install it details below)
- Install Twrp (download it from https://dl.twrp.me/tissot/) there are 2 files .zip and .img you would need fastboot and adb drivers https://androiddatahost.com/uq6us install adb minimal in location where of your choice copy twrpX.XXXX.img file beside adb/fastboot.exe , from start menu open command prompt right click run as administrator locate to adb/fastboot folder .
Power off your mi a1 when its powerd off hold down volume down and power button until you see fastboot mode on the phone connect it to pc wait for drivers to install let me know if you need in this regard. Inside command prompt run " fastboot devices " if you see device with bunch of numbers below than it means your phone is connected and drivers are working than enter this command " fastboot boot twrpXX.XXXX.img " it will take no more than 5 seconds your phone will turn on into twrp recovery there you can copy twrpxx.xxx.zip file to your internal storage or sd card flash it when its done restart -> Recovery.
Warning: After flashing twrp zip dont restart to system if you do your phone will show you message that phone has been destroyed so dont restart .
- Installing custom roms: download custom rom of your choice transfer it into internal or sd card from twrp install-locate to custom rom .zip file and flash it also keep in mind lots of roms didn't include gapps so you have to download it from opengapps(for android 8-10) and nikgapps(android 11). Flash gapps . Keep in mind after installing custom roms you will lose twrp recovery so if you want twrp at this stage go ahead and install it
- If you want root access download and flash magisk
Its always good practice to keep stock rom and xiaomi flash tool with you just in case if something goes wrong you can reflash stock rom and boot normally.
Let me know if you need help
Cheers
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Proudly Presents
Another Exclusive Release
Supported Model
Cricket Dream 5G
Device Codename
FIH - EC211001
Recoveries
OrangeFox_11 Recovery
PitchBlack_11 Recovery
SkyHawk_11 Recovery
TWRP_11 Recovery
Roms
CricketRom Custom Stock - Android 11
AncientOS Custom GSI - Android 12
ArrowOS Custom GSI - Android 12
CherishOS Custom GSI - Android 12
Corvus Custom GSI - Android 12
CrDroid Custom GSI - Android 12
-AIO ToolKit Prerequisites-
1- Linux: Linux Mint Cinnamon (Suggested)
2- Python 3
3- Pip install Command: sudo apt install python3-pip
-AIO ToolKit -
Unlocks Bootloader
Selection of 4 Installable Recoveries, Pre-Patched with Magisk
Makes Full Device Backup Or Selection Of A Few Various Partitions
2 Generic UnBrick Options(Needs More Testing)
Rom Notes/Disclaimer/Warning
**CricketRom Custom Stock Rom WILL NOT Bypass Carrier Hotspot Limits(Currently, WIP) **
**All Custom GSI Rom Releases Have Working Service, Data, Volte, 5G OOTB**
**All Custom GSI Rom Releases Bypass Carrier Hotspot Limits **
** All Roms Will Flash Magisk 24.3 Patched TWRP Boot Image **
**All Roms Will Flash Custom LK (Cleans Up Unlocked Bootloader Nag Screen) **
**All Roms Use A Custom MTP Service & Script For Insanely Fast Usb Plugged Recognition **
**All Roms Use A Custom R/W Service & Script To Ensure Proper Read/Write Access **
**Device Files Based Off Firmware Update 5-8-2022(Except lk cause I'm lazy and didn't want to repatch it)**
-CricketRom Flash Procedure-
1- Move CricketRom To Device (External SD)
2- Boot Recovery
3- Wipe Cache, Dalvik Cache, Data (Factory Reset)
4- Install CricketRom
5- Enjoy!!
-Custom GSI Rom Flash Procedure-
1- Move GSI Rom zip To Device (External SD)
2- Boot Recovery
3- Wipe Dalvik, Cache, Data (Factory Reset)
4- Install Custom GSI Rom zip
5- Boot Custom GSI Rom & Wait Until A-Team Notification & Reboot
6- Enjoy!!
Contributors
@PizzaG
@lopestom for his nicely done fstab for recovery that I'm using
@Welkwo for the line to kill encryption
@phhusson for his GSI work
AndyYan for his GSI work
@topjohnwu for Magisk
Google for Android
Big Thanks To The Folks Who Have Come To The A-Team Telegram Group To Help Test
Device Downloads
Located Below
Recovery Device Trees
Recovery Device Tree Source
A-Team Website
A-Team Supported Devices
TeleGram Live Support
A-Team Digital Solutions
-Updates-
6-21-22: Uploading...
Reserved-2...
hmm, not sure why some releases are a bad thing.....
PizzaG said:
hmm, not sure why some releases are a bad thing.....
Click to expand...
Click to collapse
Not sure how or why, either.
I haven't gotten the Dream, yet, so to be clear: the phone is rootable, bootloader unlockable, and has custom ROMs? And still works on Cricket?
If so, that's amazing for an entry-level "free" phone from an MVNO!
rczrider said:
Not sure how or why, either.
I haven't gotten the Dream, yet, so to be clear: the phone is rootable, bootloader unlockable, and has custom ROMs? And still works on Cricket?
If so, that's amazing for an entry-level "free" phone from an MVNO!
Click to expand...
Click to collapse
Yes to everything you said above. I'm running an android 12 gsi rom as my daily.
So sorry, I forgot about locking the bootloader that'll cause the "no os" message when I was trying to reset it to stock to sell.
What can I do to get it to boot into the OS again? The bootloader is locked, so I couldn't do most of what people said since it required flashing. I did download this tool and fired it up in Linux. Fastboot detects the phone, but setting up the mtk client resets in "missing setup.py" and using the "unbrick menu" doesn't do anything. I am using the 0.02 files.
TIA
hawk1500 said:
So sorry, I forgot about locking the bootloader that'll cause the "no os" message when I was trying to reset it to stock to sell.
What can I do to get it to boot into the OS again? The bootloader is locked, so I couldn't do most of what people said since it required flashing. I did download this tool and fired it up in Linux. Fastboot detects the phone, but setting up the mtk client resets in "missing setup.py" and using the "unbrick menu" doesn't do anything. I am using the 0.02 files.
TIA
Click to expand...
Click to collapse
check the setup for mtkclient on github
PizzaG said:
check the setup for mtkclient on github
Click to expand...
Click to collapse
Hello, yeah, so I had gotten it to install, and I tried running both the shorter and the longer unbricking procedure, but there was no change and still gives me the no os message on bootup.