Code:
*** I'm not responsible for dead sd cards, thermonuclear war, getting you fired because the alarm has failed. Your warranty is void if you continue! ***
Code:
*** Everything you read here was a success for my ATU-L21 variant of the Huawei Y6 (2018). Don't be alarmed, the files mentioned here are 100% compatible with the phone ***
Hey, dear Forum Users!
Prerequisite things:
Install HiSuite, it has the proprietary drivers needed to operate ADB and Fastboot.
You need to unlock your bootloader, get them from dc-unlocker, it's 4 euros.
You need the following:
The 2018 kernel and vendor image: https://drive.google.com/open?id=1aFTTMSArwBuF5tsJBkWJ7f_d7IQc7zyy (credits goes to Boki, @deadliestPixel on Twitter)
You need this TWRP to boot up: https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831 (thanks to @leepicstitch on Twitter for finding this)
You'll need to flash this TWRP to recovery_ramdisk: https://www.mediafire.com/file/7nyab3whb6bp7r8/twrp_3.2.3_atu.rar/file
Choose a ROM that will suit your needs from this thread: https://forum.xda-developers.com/huawei-y6/development/index-list-roms-y62018-t3854167 or try other GSIs
(I recommend Resurrection Remix with gapps and su)
So if you have everything, let's do this.
Before we start everything make sure you have a microSD card that has the VENDOR.img and the system.img you downloaded.
So, we need to make a backup of our current recovery_ramdisk for later, you can follow the TWRP XDA post above to do so.
After you've done that go to fastboot and flash the older kernel with this command:
Code:
fastboot flash kernel /path/to/KERNEL.img
Flash the recovery you downloaded with
Code:
fastboot flash recovery_ramdisk /path/to/recovery.img
Now boot up that screen flasher recovery you had before. If you booted it up just reboot the phone to recovery with
Code:
adb reboot recovery
, the Y6 Prime 2018 recovery should boot up.
Now go to Install -> Change Storage -> Micro SD -> flash image -> choose the vendor.img and flash it to the VENDOR partition.
Do the same for the system.img file.
Go to the main menu and go to wipe, then wipe dalvik/art cache, cache, data, internal storage.
go to the main menu and go to reboot, then bootloader.
Now we need to flash our stock recovery_ramdisk back, because eRecovery will complain about a damaged data partition. Do a low level data format, type yes, and when the emui recovery pops up, do another data wipe.
Now, just hit reboot and the phone should boot into the ROM.
Turn off the phone and reboot back into fastboot and flash back the Y6 Prime 2018 recovery just in case if eRecovery wants to do something weird.
Now just reboot your phone and enjoy it.
If you need any help send me a DM on Twitter (@miklos_akos) or on Discord (miklos_akos#0001).
hawkhu said:
Hey, dear Forum Users!
Prerequisite things:
Install HiSuite, it has the proprietary drivers needed to operate ADB and Fastboot.
You need to unlock your bootloader, get them from dc-unlocker, it's 4 euros.
You need the following:
The 2018 kernel and vendor image: https://drive.google.com/open?id=1aFTTMSArwBuF5tsJBkWJ7f_d7IQc7zyy (credits goes to Boki, @deadliestPixel on Twitter)
You need this TWRP to boot up: https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831 (thanks to @leepicstitch on Twitter for finding this)
You'll need to flash this TWRP to recovery_ramdisk: https://www.mediafire.com/file/7nyab3whb6bp7r8/twrp_3.2.3_atu.rar/file
Choose a ROM that will suit your needs from this thread: https://forum.xda-developers.com/huawei-y6/development/index-list-roms-y62018-t3854167 or try other GSIs
(I recommend Resurrection Remix with gapps and su)
So if you have everything, let's do this.
Before we start everything make sure you have a microSD card that has the VENDOR.img and the system.img you downloaded.
So, we need to make a backup of our current recovery_ramdisk for later, you can follow the TWRP XDA post above to do so.
After you've done that go to fastboot and flash the older kernel with this command:
Flash the recovery you downloaded with
Now boot up that screen flasher recovery you had before. If you booted it up just reboot the phone to recovery with , the Y6 Prime 2018 recovery should boot up.
Now go to Install -> Change Storage -> Micro SD -> flash image -> choose the vendor.img and flash it to the VENDOR partition.
Do the same for the system.img file.
Go to the main menu and go to wipe, then wipe dalvik/art cache, cache, data, internal storage.
go to the main menu and go to reboot, then bootloader.
Now we need to flash our stock recovery_ramdisk back, because eRecovery will complain about a damaged data partition. Do a low level data format, type yes, and when the emui recovery pops up, do another data wipe.
Now, just hit reboot and the phone should boot into the ROM.
Turn off the phone and reboot back into fastboot and flash back the Y6 Prime 2018 recovery just in case if eRecovery wants to do something weird.
Now just reboot your phone and enjoy it.
If you need any help send me a DM on Twitter (@miklos_akos) or on Discord (miklos_akos#0001).
Click to expand...
Click to collapse
One question, I have to flash the system.img as a vendor?... (BECAUSE YOU SAY ABOVE THAT WITH THE SYSTEM. IMG WE MADE THE SAME AS WITH THE VENDOR)
dj 77mx said:
One question, I have to flash the system.img as a vendor?... (BECAUSE YOU SAY ABOVE THAT WITH THE SYSTEM. IMG WE MADE THE SAME AS WITH THE VENDOR)
Click to expand...
Click to collapse
System.img goes to the system partition, obviously.
This worked flawlessly, the only difference is that I couldn't flash Kernel.
The ROM I used: PHH Treble 9.0 github.com/phhusson/treble_experimentations/releases/tag/v117
The steps I took:
- Factory reset phone
- Backup stock recovery_ramdisk
- Download kernel (unused) and vendor
- Boot fastboot
- Flash twrp in recovery_ramdisk
- Boot twrp
- Flash vendor, flash system
- Clean caches
- Reboot fastboot
- Flash stock recovery_ramdisk
- Reboot
erecovery did not complain, everything was ok there
Anyone tried this at atu l22 latest build?
UlysistheNewbie said:
Anyone tried this at atu l22 latest build?
Click to expand...
Click to collapse
Since the ATU-L21 and L22 is the same hardware wise it should work without any problems.
i keep either getting a black screen or vendor not mount or system not mount if not vendor ( ATU-L22 Y6 2018 )
UlysistheNewbie said:
Anyone tried this at atu l22 latest build?
Click to expand...
Click to collapse
.REPLYING--- Hey bro have you tryed flashing custom rom to the Atu-L22 with any luck?
Still trying to flash a custom system.img to my Atu-L22 after weeks of no success but flowing thru with countless amounts of tutorials, Anyone have any ideas for this phone, any help much appreciated haha?
I'm stuck in a boot splashscreen... This phone is really not easy to work with x(
edit : Narrowing it down, apparently, I don't have a vendor partition to flash the vendor to... I am starting to loose hope.
I need stock recovery_ramdisk.img . Anyone have? (Im sorry for my bad English )
Related
What you need:
ROM
VENDOR IMAGE
TWRP RC1
Verifiedbootsigner v6.1 BYCHAINFIRE
MAGISK OR SU (NOT TESTED WITH ME)
1. wipe all (system,data,cache)
2.Flash rom (MAKE SURE YOU CHECK WHICH SLOT YOU ARE FLASHING INTO)
3.flash twrp and vendor
4. flash Verifiedbootsigner
5. POWER OFF PHONE
6. boot to bootlaoder and then boot to RECOVERY.
7. REFLASH BOOT SIGNER
8. BOOT TO BOOTLOADER
9. OPEN UP CMD ON COMPUTER AND USE COMMAND BOOT (inactive slot) recover twrp.img
10. once booted into recovery flash twrp rc1 and then reflash bootsigner(force if you have to)
11. Then switch bootslots to the active one which has the rom and boot.
12. NOW FLASH MAGISK AFTER YOU BOOT
The above is my method and how i got around it, i understand i could have made the above abit more cleaner but i am in a rush and wanted to help a few fellows.
If anyone has a more detailed description of the above, please let me know so i can post.
Thanks
asad510 said:
What you need:
ROM
VENDOR IMAGE
TWRP RC1
Verifiedbootsigner v6.1 BYCHAINFIRE
MAGISK OR SU (NOT TESTED WITH ME)
1. wipe all (system,data,cache)
2.Flash rom (MAKE SURE YOU CHECK WHICH SLOT YOU ARE FLASHING INTO)
3.flash twrp and vendor
4. flash Verifiedbootsigner
5. POWER OFF PHONE
6. boot to bootlaoder and then boot to RECOVERY.
7. REFLASH BOOT SIGNER
8. BOOT TO BOOTLOADER
9. OPEN UP CMD ON COMPUTER AND USE COMMAND BOOT (inactive slot) recover twrp.img
10. once booted into recovery flash twrp rc1 and then reflash bootsigner(force if you have to)
11. Then switch bootslots to the active one which has the rom and boot.
12. NOW FLASH MAGISK AFTER YOU BOOT
The above is my method and how i got around it, i understand i could have made the above abit more cleaner but i am in a rush and wanted to help a few fellows.
If anyone has a more detailed description of the above, please let me know so i can post.
Thanks
Click to expand...
Click to collapse
And not a verizon phone
asad510 said:
What you need:
ROM
VENDOR IMAGE
TWRP RC1
Verifiedbootsigner v6.1 BYCHAINFIRE
MAGISK OR SU (NOT TESTED WITH ME)
1. wipe all (system,data,cache)
2.Flash rom (MAKE SURE YOU CHECK WHICH SLOT YOU ARE FLASHING INTO)
3.flash twrp and vendor
4. flash Verifiedbootsigner
5. POWER OFF PHONE
6. boot to bootlaoder and then boot to RECOVERY.
7. REFLASH BOOT SIGNER
8. BOOT TO BOOTLOADER
9. OPEN UP CMD ON COMPUTER AND USE COMMAND BOOT (inactive slot) recover twrp.img
10. once booted into recovery flash twrp rc1 and then reflash bootsigner(force if you have to)
11. Then switch bootslots to the active one which has the rom and boot.
12. NOW FLASH MAGISK AFTER YOU BOOT
The above is my method and how i got around it, i understand i could have made the above abit more cleaner but i am in a rush and wanted to help a few fellows.
If anyone has a more detailed description of the above, please let me know so i can post.
Thanks
Click to expand...
Click to collapse
On step one. After you wipe system, data, and cache, your wiping the system to your active slot.the one your on. So I would say you would want to switch slots right here. So your new rom goes on clean slot.
In my experience so far after your step 5 you will have to fastboot boot TWRP again, because you just flashed a rom now and it's not signed anymore. So TWRP will not boot. Unless you have April bootloader in that slot, if you have may in both slots you will have to fastboot boot twrp. So far this is what I have had to do. I would like to know if someone has figured out how to flash a rom on may bootloader's without having to use fastboot.
mac796 said:
On step one. After you wipe system, data, and cache, your wiping the system to your active slot.the one your on. So I would say you would want to switch slots right here. So your new rom goes on clean slot.
In my experience so far after your step 5 you will have to fastboot boot TWRP again, because you just flashed a rom now and it's not signed anymore. So TWRP will not boot. Unless you have April bootloader in that slot, if you have may in both slots you will have to fastboot boot twrp. So far this is what I have had to do. I would like to know if someone has figured out how to flash a rom on may bootloader's without having to use fastboot.
Click to expand...
Click to collapse
Mac your right mate. I'm not sure you can do it but what I have noticed is that twrp rc1 is needed for may bootloader
WHO IS THIS GUIDE FOR:
Anyone updating factory images within the same OS version (10 to 10)
Anyone upgrading from one OS to another (9x to Android 10)
Below is a QUICK REFERENCE guide for those who have done this before, and a DETAILED STEP BY STEP guide for the first or second timer who needs each and every step outlined. Links to all required files are also provided (make sure you are selecting the latest version)
UPDATE TO THE LATEST FACTORY IMAGE . . . UPGRADE TO THE NEXT OS. . .
PREP WORK:
* Unlocked bootloader. (*performing critical_unlock only required with bootloader versions PRIOR to TMZ20a) read it here.
* Latest SDK Platform Tools found here.
* USB 2.0 & 3.0 cables available (trust me)
* Remove screen lock security before starting
* Remove all substratum overlays
*Download and extract the latest Taimen factory image (place the second extracted folder in Platform Tools folder)
CLEAN FLASH (wipe everything) or DIRTY FLASH (keep data)
Decide now whether you want a fresh OS that will restore your device to factory setup OR if you want to flash the latest factory image but keep your data.
For a clean flash: leave the FLASH-ALL file intact, change nothing.
To retain your data: EDIT the FLASH-ALL file and REMOVE the -w near the end of the script. Save the file and reopen it to ensure the -w has been removed,
When UPGRADING from one OS to another I reco a CLEAN FLASH (leave the -w intact)
Place these files on your sdcard (either before dirty flash or from PC after clean install):
* Latest TWRP.ZIP
* Your preferred customer kernel zip, I use ElementalX kernel
* Magisk uninstall instructions In the event you need to manually uninstall and reinstall MM
* Latest Magisk.zip
* Latest Magisk Manager APK
NOTE: On Android 10, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the warning "FAILED TO MOUNT '/system' (invalid argument) this is a known issue with TWRP + 10 but affects nothing :good:
QUICK REFERENCE GUIDE for updating/upgrading Pixel 2 XL:
Once you verify 'fastboot devices' on command prompt
Type flash-all to install factory image (allow it to install, and boot into system)
Hold vol down and power button to boot into bootloader
Fastboot into twrp 3.3.0-0.IMG
Flash the twrp installer 3.3.0-0.ZIP,
Flash custom kernel, I use flar2's ElementalX Kernel. SELECT THE CORRECT 9X OR ANDROID 10 KERNEL
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit
DETAILED STEP BY STEP GUIDE for updating monthly factory images, or upgrading to the next OS (ie: 9x to 10x)
I reco a CLEAN FLASH (leave the -w intact) when jumping from one OS to a new one (not necessary when doing monthly factory updates within the same OS version)
Requirements:
*Unlocked bootloader and Critical_unlock* completed. (*critical_unlock required with bootloader versions PRIOR to TMZ20a) read it here.
*Latest SDK PlatformTools found here
*USB 2.0 & 3.0 cables available (trust me)
These files on your sdcard:
* Latest TWRP.ZIP
* Your preferred Custom Kernel, I use Elemental X Kernel
* Magisk uninstall instructions In the event you need to manually uninstall and reinstall MM
* Latest Magisk.zip
* Latest Magisk Manager APK
These files in your Platform Tools Folder:
* Latest factory image (MAKE SURE YOU DL THE CORRECT DEVICE IMAGE :good: )
* Latest TWRP.IMG
1. Make backup, move to PC (because you never know)
2. Disable all security; patterns, pins, etc.
3. In Developer Options, make sure USB DEBUGGING is on
4. Connect device to PC, verify fastboot is working type; fastboot devices (should see your device's serial number)
5. Fastboot latest factory image (To KEEP internal storage intact, edit and remove -w in "flash-all.bat" file and SAVE, to wipe entire device, leave flash-all unedited)
Type: FLASH-ALL (hit enter) Allow the OS to reboot and settle for a minute *REMEMBER LEAVING THE -W INTACT WILL WIPE YOUR DEVICE*
6. Reboot into BOOTLOADER, in CMD screen Type: fastboot boot <twrpxxx.img name> to boot into Latest TWRP.IMG
7. Once in TWRP, install Latest TWRP.ZIP from sdcard
8. Reboot back into Recovery
9. Install compatible custom kernel, I use flar2's ElementalX Kernel.
10. Reboot back into Recovery
11. Reboot into System, allow OS to settle for a few minutes
12. Boot into Recovery
13. Install Latest Magisk.zip
14. Reboot into System
15. Profit
Troubleshooting Tips & Other Information
Click here for * * * BASIC FASTBOOT/ADB TROUBLE SHOOTING FOR THE 2XL * * *
If you get stuck at the G screen, or bootloop into TWRP, try these steps:
-Perform a hard reboot (long press the power button) or
-Get back to TWRP (whether by booting into it from fastboot, or rebooting into bootloader -long press power & vol down- then boot into recovery) and reinstall the Magisk Uninstaller in TWRP a few times.
- If you are bootlooping into TWRP with Magisk installed, READ THIS!
- Safety Net message in Magisk "The Response Is Invalid" is a known issue[/URL] ... Be patient
View attachment 4572738
Make sure you have all the correct and/or latest versions of SDK Tools, factory image, TWRP.img and TWRP.zip, and Magisk
Note: as a matter of superstition, I reboot back into recovery each time after installing TWRP, cust kernel, and magisk, prior to booting into system. It is NOT required, but it works
Again, HUGE thanks to @Badger50 for his invaluable input
Az Biker said:
A lot of users have had success upgrading from Oreo to Pie and there are several tutorial / guide posts located in different threads, so I figured I'd centralize instructions in a Quick Reference Thread, that includes all needed file links and an easy to follow step by step.
Please feel free to make any suggestions to simplify or make this more accurate.
Requirements:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
These files on your sdcard:
* TWRP 3.2.2-0.ZIP
*Flash kernel 3.0
* magisk uninstaller
*magisk zip 1674
* MM 5.8.3 APK
These files in your Platform Tools Folder:
* 9.0 factory image
*TWRP 3.2.2-0.IMG
1. Make backup, move to PC (because you never know)
2. Disable all security; patterns, pins, etc.
3. In Developer Options, make sure USB DEBUGGING is on
4. Verify fastboot is working type; fastboot devices (should see your device's serial number)
5. Fastboot 9.0 factory image(To KEEP internal storage intact, remove -w in "flash-all.bat" file and SAVE, to wipe entire device, leave flash-all unedited)
6. Type: fastboot boot <twrpxxx.img name> to boot into TWRP 3.2.2-0.IMG
7. Once in TWRP, install TWRP.ZIP on sdcard
8. Reboot back into Recovery, and install the magisk uninstaller in twrp,
9. Reboot back into Recovery and install Flash kernel 3.0
10. Reboot back into Recovery
11. Reboot into System, allow OS to settle for a few minutes
12. Install MM 5.8.3 APK
13. Reboot into Recovery
14. Install magisk zip 1674,
15. Reboot back into Recovery
16. Reboot into System
17. Profit
Note: as a matter of superstition, I reboot back into recovery each time after installing TWRP, cust kernel, and magisk, prior to booting into system. It is NOT required, but it works
Thanks to @Badger50 for figuring out the right steps in this process!
Click to expand...
Click to collapse
Well done my brother!! :good::good:
Badger50 said:
Well done my brother!! :good::good:
Click to expand...
Click to collapse
I use unlock bootloader normal.
I was done follow your step but it's boot stuck google logo after flash magisk(16.74).
newyesor said:
I use unlock bootloader normal.
I was done follow your step but it's boot stuck google logo after flash magisk(16.74).
Click to expand...
Click to collapse
Sometimes it takes 5 minutes or so on first boot. If it doesn't work, do a hard restart a few times. If that doesn't work, flash magisk again in twrp.
You use unlock bootloader normal??
Badger50 said:
Sometimes it takes 5 minutes or so on first boot. If it doesn't work, do a hard restart a few times. If that doesn't work, flash magisk again in twrp.
You use unlock bootloader normal??
Click to expand...
Click to collapse
I use normal unlock bootloader.
I wait devices boot around 5 minutes and it 's reboot in to twrp recovery.
newyesor said:
I use normal unlock bootloader.
I wait devices boot around 5 minutes and it 's reboot in to twrp recovery.
Click to expand...
Click to collapse
So your bootloader _critical partition isn't unlocked?? Which can't be right either since you've been able to boot fastboot the update to P. Guess I just don't know what your trying to say.
Badger50 said:
So your bootloader _critical partition isn't unlocked?? Which can't be right either since you've been able to boot fastboot the update to P. Guess I just don't know what your trying to say.
Click to expand...
Click to collapse
I use this command for flash unlock bootloader.
fastboot flashing unlock
newyesor said:
I use this command for flash unlock bootloader.
fastboot flashing unlock
Click to expand...
Click to collapse
Have you ever ran fastboot flashing unlock_critical..?
Have you actually booted into the 9.0.OS yet?
Badger50 said:
Have you ever ran fastboot flashing unlock_critical..?
Have you actually booted into the 9.0.OS yet?
Click to expand...
Click to collapse
I have never ran fastboot flashing unlock_critical.
Yes,My devices is base on android P and I was booted into the 9.0.OS.
newyesor said:
I use this command for flash unlock bootloader.
fastboot flashing unlock
Click to expand...
Click to collapse
If you flashed the factory image with no issues, then you must have completed critical_unlock as well, otherwise the new bootloader shouldn't have taken (as far as I understand).
I'd start from scratch again, and make sure you follow the process exactly. Many users have used this with no issue, so maybe you missed something? The first time I flashed the factory image to my 6P (my backup) I totally skipped flashing the boot.img, and wondered why it wouldn't boot
Kudos, just what I needed to update!
newyesor said:
I have never ran fastboot flashing unlock_critical.
Yes,My devices is base on android P and I was booted into the 9.0.OS.
Click to expand...
Click to collapse
Have you flashed the magisk uninstaller as well? Why are you showing magisk 16.0?
Badger50 said:
Have you flashed the magisk uninstaller as well? Why are you showing magisk 16.0?
Click to expand...
Click to collapse
Yes,i was flashed the magisk uninstaller as well.
I try to root with magisk on my devices.
I try to flash patch boot for root without twrp but it's not work.
I try to flash magisk follow you but it's not work.
Is flashing the kernel mandatory?
newyesor said:
Yes,i was flashed the magisk uninstaller as well.
I try to root with magisk on my devices.
I try to flash patch boot for root without twrp but it's not work.
I try to flash magisk follow you but it's not work.
Click to expand...
Click to collapse
Something just seems fishy to me. I've never heard of anyone not unlocking _critical, and being able to fastboot the factory image. However, it seems that you have somehow. All I can suggest is to fastboot the 9.0 again to both slots, and let it boot up each time.
Then fastboot into twrp, flash the installer zip, and let it boot up. Then go back to twrp, flash magisk uninstaller zip, then flash custom kernel, and let it boot up. Then go back to twrp, and flash magisk 1674 again.
If none of that works, I'd unlock _critical, which will wipe your phone, and then start over.
aznriceballman said:
Is flashing the kernel mandatory?
Click to expand...
Click to collapse
Not mandatory, but it keeps TWRP touch screen working among other things...
Just wanted to say thanks for this!
I didn't have time to update from DP5 yesterday, but I guess that was a good thing because now there's this guide, and it worked perfectly. Upgraded from DP5/flash 2.44 and who knows what Magisk version to all the latest and greatest in no time at all.
Thanks!
Badger50 said:
Something just seems fishy to me. I've never heard of anyone not unlocking _critical, and being able to fastboot the factory image. However, it seems that you have somehow. All I can suggest is to fastboot the 9.0 again to both slots, and let it boot up each time.
Then fastboot into twrp, flash the installer zip, and let it boot up. Then go back to twrp, flash magisk uninstaller zip, then flash custom kernel, and let it boot up. Then go back to twrp, and flash magisk 1674 again.
If none of that works, I'd unlock _critical, which will wipe your phone, and then start over.
Click to expand...
Click to collapse
im having an issue, i followed all instructions and got booted up an everything but when i flash twrp img it stays stuck on the twrp logo, flashed the one mentioned in o.p and the newest as well to remove any doubts, but no go. Any suggestions?
shooterlgk said:
im having an issue, i followed all instructions and got booted up an everything but when i flash twrp img it stays stuck on the twrp logo, flashed the one mentioned in o.p and the newest as well to remove any doubts, but no go. Any suggestions?
Click to expand...
Click to collapse
Do you have screen lock disabled?
Badger50 said:
Do you have screen lock disabled?
Click to expand...
Click to collapse
Yes sir
Hi,
Does a thorough guide exist on how to flash custom ROM on this phone?
I have done quite a lot of flashing in my life but can't a ROM flashed for the love of God.
Got TWRP installed, ADB works, cables are good.
Thanks!
After quite some hours I finally managed to get Havoc Pie running (GSI ARM64 AB, downloaded here).
My first problem was the fact that you need to be on stock Oreo before starting, this took me a while to figure out.
I used the most recent 'back to stock' Oreo from this page.
After installing this, I booted up, and went straight for enabling USB-debugging in Developer options.
Then do ADB REBOOT BOOTLOADER to enter fastboot mode.
There I erased system on both A and B partitions by using FASTBOOT ERASE SYSTEM command, then FASTBOOT SET_ACTIVE OTHER to switch to the other partition, and then once more FASTBOOT ERASE SYSTEM to also erase the system on this partition.
After that I ran FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img, on the one partition, then FASTBOOT SET_ACTIVE OTHER and after that FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img to flash it on the other partition.
After that I installed TWRP by running FASTBOOT FLASH BOOT twrp-3.2.3-0-mata.img (downloadable here).
After that, I rebooted into TWRP recovery by running ADB REBOOT RECOVERY.
There, I put twrp-installer-mata-3.2.3-0.zip (downloadable at the previously mentioned TWRP website) on internal memory and flashed it.
This automatically flashes both A and B partitions (switching between A and B at the reboot screen).
After doing that, I wiped /DATA on both A and B.
Then I put the Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img on internal memory and flashed it on /SYSTEM for both A and B.
Then it is time for GAPPS.
As I prefer Stock GAPPS with my own GAPPS-CONFIG.TXT, I ran into the Error 70: because of the large size of Havoc, there is not enough room for large GAPPS.
So because of that I needed to do the Resize /SYSTEM partition for both A and B (in the Advanced wipe menu section).
After that I was able to flash my Stock GAPPS on both A and B.
Now I need some rest to regain my sanity before I tackle rooting the ROM.
I probably did too much double stuff, but it is not easy to know when only A or B needs to be done.
Comments and tips are welcome.
Waancho said:
After quite some hours I finally managed to get Havoc Pie running (GSI ARM64 AB, downloaded here).
My first problem was the fact that you need to be on stock Oreo before starting, this took me a while to figure out.
I used the most recent 'back to stock' Oreo from this page.
After installing this, I booted up, and went straight for enabling USB-debugging in Developer options.
Then do ADB REBOOT BOOTLOADER to enter fastboot mode.
There I erased system on both A and B partitions by using FASTBOOT ERASE SYSTEM command, then FASTBOOT SET_ACTIVE OTHER to switch to the other partition, and then once more FASTBOOT ERASE SYSTEM to also erase the system on this partition.
After that I ran FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img, on the one partition, then FASTBOOT SET_ACTIVE OTHER and after that FASTBOOT FLASH SYSTEM Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img to flash it on the other partition.
After that I installed TWRP by running FASTBOOT FLASH BOOT twrp-3.2.3-0-mata.img (downloadable here).
After that, I rebooted into TWRP recovery by running ADB REBOOT RECOVERY.
There, I put twrp-installer-mata-3.2.3-0.zip (downloadable at the previously mentioned TWRP website) on internal memory and flashed it.
This automatically flashes both A and B partitions (switching between A and B at the reboot screen).
After doing that, I wiped /DATA on both A and B.
Then I put the Havoc-OS-v2.0-20181027-GSI-ARM64-AB-Official.img on internal memory and flashed it on /SYSTEM for both A and B.
Then it is time for GAPPS.
As I prefer Stock GAPPS with my own GAPPS-CONFIG.TXT, I ran into the Error 70: because of the large size of Havoc, there is not enough room for large GAPPS.
So because of that I needed to do the Resize /SYSTEM partition for both A and B (in the Advanced wipe menu section).
After that I was able to flash my Stock GAPPS on both A and B.
Now I need some rest to regain my sanity before I tackle rooting the ROM.
I probably did too much double stuff, but it is not easy to know when only A or B needs to be done.
Comments and tips are welcome.
Click to expand...
Click to collapse
Wow, here's all i did :
Flashing ProjectTreble GSIs on the Essential using TWRP
1) either boot or fastboot into TWRP
2) Wipe Cache, System, and Data (1 GSI required internal to be wiped, i forget which)
3) From Main Menu, select Install and Flash UN-ZIPPED A/B system.img
4) Reboot Recovery (It's going to say there's no OS, act like you didnt see it.)
5) Reboot System and Enjoy!
6) Most of the later GSIs from October to Present I have flashed and am happy to say
they all contain pre-installed Magisk and ALL but 1 contains Gapps.
AndroidDevices said:
Wow, here's all i did :
Flashing ProjectTreble GSIs on the Essential using TWRP
1) either boot or fastboot into TWRP
2) Wipe Cache, System, and Data (1 GSI required internal to be wiped, i forget which)
3) From Main Menu, select Install and Flash UN-ZIPPED A/B system.img
4) Reboot Recovery (It's going to say there's no OS, act like you didnt see it.)
5) Reboot System and Enjoy!
6) Most of the later GSIs from October to Present I have flashed and am happy to say
they all contain pre-installed Magisk and ALL but 1 contains Gapps.
Click to expand...
Click to collapse
Thanks!
Next time i will try your method.
For some reason, if i did anything different, the phone would just keep rebooting into recovery.
And of course, the ROM that i chose (Havoc) did not have Magisk pre-installed.
I am now back to stock and liking it, which says a lot about the PH-1 software!
Waancho said:
Thanks!
Next time i will try your method.
For some reason, if i did anything different, the phone would just keep rebooting into recovery.
And of course, the ROM that i chose (Havoc) did not have Magisk pre-installed.
I am now back to stock and liking it, which says a lot about the PH-1 software!
Click to expand...
Click to collapse
It does have Magisk installed, it should if its one of the newer builds and all you need to do is install Magisk Manager which in turn activates Magisk
Installing Magisk manager was one of the first things I did, but unfortunately, the latest version A/B Havoc at the aforementioned link did not have Magisk.
There's about 6 or 7 and probably a bunch of YouTube's
Sent from my PH-1 using XDA Labs
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma,
* thermonuclear war, or your mom getting upset with you for being on the computer all day
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
THIS GUIDE APPLIES TO JETER AND ALJETER DEVICES
FOR ALJETER DEVICE OWNERS ONLY.
there are ALOT of different variants of the aljeter so please before beginning this root method go to settings, system, about phone. look for either sw version or software channel verison and either remember what it says or write it down. me or anyone else will need this to help troubleshoot which aljeter variant you have. this will also be important to know incase you mess up and need to reflash stock firmware which those instructions are at the bottom of this guide.
The following devices have been confirmed to work on devices with Android 8 (Oreo)
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile/ Virgin Mobile
XT1922-9 Motorola Retail
The following devices have been confirmed to work with Android 9 (pie)
XT1922-7 (Jeter) boost Mobile/ Virgin Mobile.
XT1922-3 (Aljeter)
XT1922-5 (Aljeter retbr)
Please make backups using TWRP IN CASE OF FAILURE.
Original stock firmware FOR JETER can be found here. https://mirrors.lolinet.com/firmware/moto/jeter/official/ and here FOR ALJETER https://mirrors.lolinet.com/firmware/moto/aljeter/official/
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisite:
Unlocked bootloader.
FOR LINUX USERS. If you're using a linux distro then congrats this is all you should have to run. open command prompt and run this. "sudo apt-get install adb" without quotation marks. then follow Motorolas bootloader guide in provided link. continue to step 1 after.
FOR WINDOWS USERS.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio...platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Minimal adb/fastboot v1.4.3 installer can be found here. https://androidfilehost.com/?fid=746010030569952951
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
DECRYPTION AND BACKUP.
NOTICE
IF YOU YOU ARE USING THE 32GB MODEL OR THE 16GB MODEL AND ARE ON ANDROID 9 (PIE) PLEASE USE THE ANDROID 9 (PIE) MODEL TWRP. USERS WITH THE 16GB MODEL AND THE 32GB MODEL ON ANDROID 8 (OREO) WILL STILL NEED TO USE SEPERATE TWRPS
MAKE SURE TO SWIPE RIGHT IN TWRP TO ALLOW SYSTEM MODIFICATIONS.
Step 1.) Download and extract twrp image to the ADB/Fastboot folder on your computer.
FOR ANDROID 8 (OREO)
16gb model twrp: https://www.androidfilehost.com/?fid=6006931924117921836
32gb model twrp: https://www.androidfilehost.com/?fid=6006931924117927211
FOR ANDROID 9 (PIE)
https://www.androidfilehost.com/?fid=6006931924117921849
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding the power button and volume down button at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel)
Step 5.) time to backup your stock recovery and stock boot. use these commands one at a time.
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you need to revert to stock later.
Step 6.) time to decrypt which will also format your data so make sure to make a backup. while still booted in twrp touch the "wipe" button then touch "format data", type yes and after its all done reboot to bootloader use this command.
Code:
adb reboot bootloader
CONGRATS! if you read this correctly and or didnt skim then you have successfully decrypted your device and backed up your stock recovery and stock boot.img. proceed below for root process.
ROOT PROCESS.
Step 1.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery twrp.img
Step 2.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. swipe right to allow modifications. IT SHOULD NOT ASK YOU FOR A PASSWORD THIS TIME IF IT DOES YOU MESSED UP DURING THE DECRYPT PROCESS
Step 3.) Follow this link to the creators site to download the disabler zip. https://zackptg5.com/android.php#disverfe download it to your ADB/Fastboot folder.
Step 4.) Download the Magisk Beta v20.0 and or the latest zip file from https://github.com/topjohnwu/Magisk/releases to your ADB/Fastboot folder. (I personally use beta so I use beta in this guide but you don't have to)
Step 5.) Run the following command to push the dm_verity force encrypt disabler and magisk zip to your device
Code:
adb push Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip /tmp
adb push Magisk-v20.0.zip /tmp
This will push the Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip and Magisk-v20.0.zip to your /tmp folder
Step 6.) Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 7.) Flash Magisk-v20.0.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 8.) Reboot your device
Step 9.) Just wait for the device to boot up. might take a bit and it might seem its in a bootloop but if you followed this guide exactly as is just wait it out it took about 5-10 minutes before i got to the "lets get started" screen after updating to pie (android 9)
Step 10.) Verify Magisk Manager is installed and the root functionality works. sometimes the manager apk wont be installed so download the magisk manager apk from the provide links. click advanced to see if the boxes are unchecked. (2022 edit) If you see magisk app and magisk needs updated you can do it but I can't confirm if it's safe and what works and doesnt after
CONGRATS! IF YOU DIDNT SKIM MY GUIDE YOU SHOULD HAVE A SUCCESSFULLY ROOTED AND ENCRYPTION DISABLED DEVICE, HAVE FUN.
IF YOU MESSED UP, DIDNT PUT A COMMAND IN CORRECTLY, SKIMMED, OR ARE INA GENUINE BOOTLOOP/BRICK THIS SECTION IS FOR YOU
Step 1.) DOWNLOAD STOCK FIRMWARE HERE FOR JETER AND CERTAIN ALJETER DEVICES (from what i can tell usa variant aljeter devices are consided jeter) https://mirrors.lolinet.com/firmware/moto/jeter/official/ IF YOU REMEMBER OR WROTE DOWN YOUR SW CHANNEL VERSION THEN DOWNLOAD STOCK FIRMWARE FOR BASICALLY EVERY OTHER ALJETER DEVICE HERE. https://mirrors.lolinet.com/firmware/moto/aljeter/official/ UNZIP STOCK FIRMWARE TO YOUR ADB/FASTBOOT FOLDER TO FLASH IT. TO REVERT BACK TO STOCK YOU HAVE TO REFLASH STOCK FIRMWARE FROM THE BOOTLOADER if your device is bootlooped or bricked or not working right you have to reflash the stock firmware your device came with. PLEASE INPUT THESE COMMANDS ONE AT A TIME DO NOT DO THEM ALL AT ONCE. I KNOW ITS A HASSLE BUT IT GUARANTEES A SUCCESSFUL REFLASH. I CANNOT EMPHASIZE THIS ENOUGH
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastbot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
Credits: @kwiksi1ver for making the original guide. @topjohnwu for magisk. @shimp208 for minimal adb/fastboot. @Spaceminer for providing the new twrps for 16gb and 32 gb devices, and @Zackptg5 for making the Universal DM-Verity, ForceEncrypt, Disk Quota Disablers.
QUICK NOTE/EDIT: SINCE I DO NOT OWN THIS DEVICE ANYMORE I CANNOT CONFIRM IT BUT YOU SHOULD BE ABLE TO UPDATE TO THE LATEST MAGISK 24.3 FROM THE MAGISK APP AFTER YOU INSTALL V20, AGAIN I AM NOT ABLE CONFIRM IF IT WORKS, CAUSES BOOTLOOPS, OR ANYTHING SO KEEP THAT IN MIND, but hopefully it does work for yall I've also updated the ADB commands for the disabler to reflect its latest version and I've updated the magisk link to topjohnwus GitHub as that's where all updates happen/ go first
RESERVED
In order to update the confirmed working models for this guide, if anyone that has this device with a unlocked bootloader and does root and decrypt successfully using my guide and it's not on the confirmed device list. PLEASE JUST PM ME and let me know. Please include device model number, name, and if on aljeter your software channel version.( For example. Xt1922-5 aljeter, sw channel: retbr)
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
blowingoff said:
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
Click to expand...
Click to collapse
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Kuntitled said:
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Click to expand...
Click to collapse
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Spaceminer said:
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Click to expand...
Click to collapse
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
blowingoff said:
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
Click to expand...
Click to collapse
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes" to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Spaceminer said:
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes"no to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Click to expand...
Click to collapse
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Kuntitled said:
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Click to expand...
Click to collapse
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
Click to expand...
Click to collapse
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
Click to expand...
Click to collapse
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Starkiller2 said:
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Click to expand...
Click to collapse
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Kuntitled said:
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Click to expand...
Click to collapse
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Kuntitled said:
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Click to expand...
Click to collapse
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Starkiller2 said:
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Click to expand...
Click to collapse
Do i check the file system for data at any point?
Kuntitled said:
Do i check the file system for data at any point?
Click to expand...
Click to collapse
Only if it won't mount
Starkiller2 said:
Only if it won't mount
Click to expand...
Click to collapse
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Kuntitled said:
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Click to expand...
Click to collapse
No that's fine
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues
Click to expand...
Click to collapse
But data won't work as ext4, hence the boot loop
Try going to fastboot and typing
Fastboot -w
Then boot to recovery
---------- Post added at 02:10 PM ---------- Previous post was at 02:07 PM ----------
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Click to expand...
Click to collapse
I honestly don't see how, especially if stock is working
Hi, I've been trying to get out of this situation for days.
My mi 9t went into boot loop after having wipe a twrp wipe.
Now if I try to flash a ROM it returns the antiroolback error check because my arb is 1 and the rom I find is 0.
I can't even install the twrp anymore, the installation process with fastboot is successful but it always restarts in fastboot and not in recovery.
Can someone help me?
m.92.grosso said:
Hi, I've been trying to get out of this situation for days.
My mi 9t went into boot loop after having wipe a twrp wipe.
Now if I try to flash a ROM it returns the antiroolback error check because my arb is 1 and the rom I find is 0.
I can't even install the twrp anymore, the installation process with fastboot is successful but it always restarts in fastboot and not in recovery.
Can someone help me?
Click to expand...
Click to collapse
Download this TWRP'S:
1. CHINESE TWRP - https://mega.nz/#!dVYX3SzT!CN2lTDmF3xmMlEw-LbU9xDWcFFmFdjcB_ZR1vnk_Gas
2. RUSSIAN TWRP - https://mega.nz/#!AcAlVITI!p15vuiNoSDxhViGzW1PhZwuAI9hMi3_k9FFzYiiLhoM
After installation one of these two (your choice ) TWRP'S, you can boot to your rom or:
1. FORMAT /data partition (NEVER wipe System or Persist!)
2. Copy ROM to the internal storage,
3. Install ROM,
4. Reboot,
5. Done!!!
Download Fastboot Rom
Extract
Reboot phone to fastboot
Open cmd
Go Inside folder
Type fastboot flash system system.img
Fastboot Flash Recovery recovery.img
Done