Hi guys,
for those on system/bootstack by tron1, this is what i did to flash B02 with root and fastboot working.
Thnx to @wineds , @tron1
In detail this is what i did ( because i couldn't update the .zip from sd nor update through adb sideload after i installed stock recovery 711 - @wineds could flash the .zip over SD though - thats up to you to choose)
1. I redownloaded fota B02 (to be sure ) from : http://dl1.ztems.com/zxmdmp/downloa...ages/HK/ZTE/ZTE A2017G/401379/fota_B02_B04.up
2. I didn't change .up to .zip. Put it in ADB folder (you know how...)
3. reinstalled Bootstack B01 tron1 via TWRP ( i reuploaded it here because some users had zip problems : https://www.androidfilehost.com/?fid=457095661767157153 )
4. reinstalled System B01 tron1 via TWRP ( i reuploaded and checked it again because some users had zip problems : https://www.androidfilehost.com/?fid=529152257862722738 )
5. installed stock recovery from factory img 7.11 , I uploaded it here https://www.androidfilehost.com/?fid=745425885120725539
6. in TWRP reboot to recovery----> you will reboot in stock recovery
7. update from ADB sideload ( adb sideload yourupdateB02file.up)
8. let it update...will take +-5 min in my case, in my case it was hanging a while on 47% (i thought it froze and tapped on power once, it continued...perhaps you don't have to and wait )
9. reboot system----> you'll have B02
10. use adb again, use ADB REBOOT EDL (https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379), use command ' axon7tool -w recovery' just to reflash TWRP 3.0.2.2 (if needed : https://www.androidfilehost.com/?fid=529152257862720446) . It will reboot system ok. Reenter TWRP 3.022 again and stay there.
11 to get fastboot again, use same thread as above under B ( leave TWRP running), in ADB you'll see you're in recovery mode, that's ok.
12. refollow steps 6 to 14. Reboot to fastboot will be ok again !
13 now in ADB type : fastboot flash recovery 'yourlatestrecovery 3.1'.img (if needed : https://www.androidfilehost.com/?fid=529152257862720448)
14. fastboot reboot
14. your system will reboot without the anoying " blah blah blah unlocked"
15 reenter TWRP 3.1 again and flash SU2.79 again
16 done
17 pls comment/feedback if you succeeded as well
@raystef66
Your links in steps 1 and 10 are invalid due to copy/paste ellipsis (...).
dnlilas said:
@raystef66
Your links in steps 1 and 10 are invalid due to copy/paste ellipsis (...).
Click to expand...
Click to collapse
Some of them were...weird, i never had this problem reffering to other threads..
Did update links. Check them out to verify pls.
Thnx !
I tried your method, everything is fine until I sideload b02 because I get a message when the current system is being verified "E3005: EMMC:/dev/block/bootdevice/by-name/boot: (here are some numbers) has unexpected content" Error in sideload Status 8
And I cannot update to B02, even though currently I am on b01 by tron1 .
S0wL said:
I tried your method, everything is fine until I sideload b02 because I get a message when the current system is being verified "E3005: EMMC:/dev/block/bootdevice/by-name/boot: (here are some numbers) has unexpected content" Error in sideload Status 8
And I cannot update to B02, even though currently I am on b01 by tron1 .
Click to expand...
Click to collapse
Have you tried in stock recovery to update with sd instead of sideload with adb? You also could try changing . UP to . ZIP
raystef66 said:
Have you tried in stock recovery to update with sd instead of sideload with adb? You also could try changing . UP to . ZIP
Click to expand...
Click to collapse
I tried with stock recovery with sideload and with sd as well. with .up and .zip too and I get the same error .
@raystef66 thanks for ur guide
I need to update to b02 but I don't have courage to lose root
Anyone please report after success
Sent from my ZTE A2017G using XDA-Developers Legacy app
tuiyaan said:
@raystef66 thanks for ur guide
I need to update to b02 but I don't have courage to lose root
Anyone please report after success
Sent from my ZTE A2017G using XDA-Developers Legacy app
Click to expand...
Click to collapse
this method has been tried originally by @wineds - he only updated via SD, that's all and changed .up into .zip
In fact you have nothing to fear because when f.e. you're in stock recovery and things won't update as expected, you always can go back in ADB and flash recovery again with axon7tool (EDL) etc...there's always a way out. And have root back....
When your update succeeds after all, you WILL obtain root again as i discribed. Just follow the steps carefully.
I managed to do this in 1 take
S0wL said:
I tried your method, everything is fine until I sideload b02 because I get a message when the current system is being verified "E3005: EMMC:/dev/block/bootdevice/by-name/boot: (here are some numbers) has unexpected content" Error in sideload Status 8
And I cannot update to B02, even though currently I am on b01 by tron1 .
Click to expand...
Click to collapse
Yes rename FOTA as a .zip file and try update from SD card in stock recovery. The fIle needs to be on your external SD. However the error seems to indicate one of your partitions has been modified.
Isn't it easier to
-update to B02
-axon7tool -w recovery
-disconnect before the Success, rebooting countdown ends
-boot TWRP??
Someone made a flashable fastboot zip. haven't tested yet but I guess it will get us fastboot easier
Choose an username... said:
Isn't it easier to
-update to B02
-axon7tool -w recovery
-disconnect before the Success, rebooting countdown ends
-boot TWRP??
Someone made a flashable fastboot zip. haven't tested yet but I guess it will get us fastboot easier
Click to expand...
Click to collapse
Nope, did that too and was a no go. That would have been one of the options to do (i made a thread for this too) but in this case fastboot didn't want to boot with that method strange enough. But you could try and see for your self.
For me this method worked great and i stay 100% stock despite other flashable b02's which are customized.
raystef66 said:
Nope, did that too and was a no go. That would have been one of the options to do (i made a thread for this too) but in this case fastboot didn't want to boot with that method strange enough. But you could try and see for your self.
For me this method worked great and i stay 100% stock despite other flashable b02's which are customized.
Click to expand...
Click to collapse
Yeah, fastboot doesn't want to boot because it isn't there... I mean get to EDL then flash TWRP from there with axon7tool.
I used this method on my guide and it's been working flawlessly
Choose an username... said:
Yeah, fastboot doesn't want to boot because it isn't there... I mean get to EDL then flash TWRP from there with axon7tool.
I used this method on my guide and it's been working flawlessly
Click to expand...
Click to collapse
To get fastboot back you have to downgrade aboot to b01 version :
https://forum.xda-developers.com/showpost.php?p=71847111&postcount=39
wineds said:
To get fastboot back you have to downgrade aboot to b01 version :
https://forum.xda-developers.com/showpost.php?p=71847111&postcount=39
Click to expand...
Click to collapse
Yeah, and you can flash that once you get TWRP
I'm going to update that guide, but the XDA app doesn't let me edit, and I'm far away from a computer. I'll write the process and see if I can try to get fastboot with that zip storming did. For now the process i have in mind is:
Get axon7tool, adb reboot edl, install Zadig qusb_bulk drivers, reload edl with 3 buttons, axon7tool -w recovery (after a backup ofc), disconnect before the tool restarts the phone (you get stock recovery), flash that zip.
Choose an username... said:
Yeah, and you can flash that once you get TWRP
I'm going to update that guide, but the XDA app doesn't let me edit, and I'm far away from a computer. I'll write the process and see if I can try to get fastboot with that zip storming did. For now the process i have in mind is:
Get axon7tool, adb reboot edl, install Zadig qusb_bulk drivers, reload edl with 3 buttons, axon7tool -w recovery (after a backup ofc), disconnect before the tool restarts the phone (you get stock recovery), flash that zip.
Click to expand...
Click to collapse
Or use my method
Works too you know :laugh:
Never mind how you do it every method is ok.
I kept it to the basics every one should know by now. In fact performing the steps to get fastboot again lasts no more then a minute. Just copy paste...
Btw, don't brick your phone again! :cyclops: as i remember you came from the other side of the moon...
raystef66 said:
Or use my method
Works too you know :laugh:
Never mind how you do it every method is ok.
I kept it to the basics every one should know by now. In fact performing the steps to get fastboot again lasts no more then a minute. Just copy paste...
Btw, don't brick your phone again! :cyclops: as i remember you came from the other side of the moon...
Click to expand...
Click to collapse
Lol I wiped system and data and was holding the power button... Can't believe I was that silly.
My guide actually turned out pretty huge too. So whatever man
Choose an username... said:
Lol I wiped system and data and was holding the power button... Can't believe I was that silly.
My guide actually turned out pretty huge too. So whatever man
Click to expand...
Click to collapse
Cheers mate and...happy flashing! :good:
Hi, when I try to flash stocksystem by tron1, TWRP tell me that the zip is incorrect and he can't flash it. I tried to download it again and again but still doesn't work.
fabro91 said:
Hi, when I try to flash stocksystem by tron1, TWRP tell me that the zip is incorrect and he can't flash it. I tried to download it again and again but still doesn't work.
Click to expand...
Click to collapse
Dont think the zip is incorrect. Flashed it without any errors. Others too. You're on latest 3.1.0.0 and SU2.79? Is zip in root of sd/internal?
No on external sd
---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------
Didn't work with sideload anymore
Related
Hi,
i had B00 with root and chinese recovery
after updating to b121 i goot bootloop
than i changed recovery back to stock
tried to delete cache and system etc. nothing worked
B100 Upgrade via dload/update.app not working cause version mismatch i think
what can i do now. I don't need 349 euro trash.
please help me
Same problem here
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
Click to expand...
Click to collapse
Thanks mate, I'll give it a try.
pappapishu said:
Thanks mate, I'll give it a try.
Click to expand...
Click to collapse
any chance?
Fixed it with honor 6 multi-tool, huwaeiupdateextractor and fw b100.
Now i'm installing the b121 right away.
@evilmumi: hope you fixed it as well.
---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------
evilmumi said:
any chance?
Click to expand...
Click to collapse
sorry, i didn't see your previous post.
yes, i figured out:
- downlaod the fw b100 version
- download honor 6 multi-tool (yes, even if it's made for the 6, it worked for 7 as well) and follow the "unbrick" procedure
if you have any question please ask
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here ...
Follow the instructions in the included documents.
Click to expand...
Click to collapse
thanks
you are my hero.
back in business
i hope i can use titanium backup to restore my old data w/o root
i am in trouble! i have erased all (cache dalvick data and system) by twrp! Now obviously the phone is on bootloop...i need desperately a system rom to flash
flibblesan said:
Try updating with the full B121 ROM. I have uploaded it here https://mega.nz/#!dgZwAQpb!XcZSZJOWvG1DIDoJRr_EYSehtqTU1ciPE53bNhII8JQ
Follow the instructions in the included documents.
Click to expand...
Click to collapse
Alphasampei said:
i am in trouble! i have erased all (cache dalvick data and system) by twrp! Now obviously the phone is on bootloop...i need desperately a system rom to flash
Click to expand...
Click to collapse
just read the thread
short:
0.)download from mega
1.) copy update.app on micro sd card /dload
2.)boot with volume up down and power than you can work!
evilmumi said:
just read the thread
short:
0.)download from mega
1.) copy update.app on micro sd card /dload
2.)boot with volume up down and power than you can work!
Click to expand...
Click to collapse
nope! still boot in twrp, i have no system inside the phone
sometimes we have this problem in our german forum too! More on rooted devices!
reflashing the full B100 or B121 rom help
we do it like your user described it here:http://forum.xda-developers.com/showpost.php?p=63070827&postcount=9
BTW: Where we can find the "updateextractor"? All versions of it that i have found, doesn’t work for H7 Roms!:crying:
Back to System boot
evilmumi said:
Hi,
i had B00 with root and chinese recovery
after updating to b121 i goot bootloop
than i changed recovery back to stock
tried to delete cache and system etc. nothing worked
B100 Upgrade via dload/update.app not working cause version mismatch i think
what can i do now. I don't need 349 euro trash.
please help me
Click to expand...
Click to collapse
When the phone is in RecoveryMode try a long press vol-up/vol-down/special-key and power all together for a few seconds until the phone reboots ... after that, the phone will start in SystemMode ... for me it worked.
stalfst said:
When the phone is in RecoveryMode try a long press vol-up/vol-down/special-key and power all together for a few seconds until the phone reboots ... after that, the phone will start in SystemMode ... for me it worked.
Click to expand...
Click to collapse
I realized that when I plugged the charger to phone and then powered it, it went off the TWRP boot loop. I fdon't know if any others have same issue.
When I updated my phone I had same kind of problem so I flashed stock recovery and then made the force upgrade following the rom's intructions.
Now eveything works again.
Alphasampei said:
nope! still boot in twrp, i have no system inside the phone
Click to expand...
Click to collapse
Twrp has a bootloop bug.. I also got this after rooting. What you need to do is to get it out of the bootloop by getting the phone in fastboot/download mode. I have no clue on how I finally got it to boot in fastboot mode, but I tried and tried until it finally booted in fastboot. Then I flashed stock recovery and everything was good after that. Lesson learned was that twrp and especially Chinese twrp is buggy as hell!
kjettern said:
Twrp has a bootloop bug.. I also got this after rooting. What you need to do is to get it out of the bootloop by getting the phone in fastboot/download mode. I have no clue on how I finally got it to boot in fastboot mode, but I tried and tried until it finally booted in fastboot. Then I flashed stock recovery and everything was good after that. Lesson learned was that twrp and especially Chinese twrp is buggy as hell!
Click to expand...
Click to collapse
I had no problems at all, no bootloops or any other weird stuff. Perhaps because I wiped cache + dalvik after supersu installation?
have the same problem, what should i do?
sugarray21 said:
have the same problem, what should i do?
Click to expand...
Click to collapse
Read instruction HERE
Fix Bootloops
Breaking out of bootloops depends on your device state and what kind of problem you are having. In this section, we are going to focus on the popular case where you can’t access neither the system nor the recovery partitions.
• Step 1: Turn off the phone.
• Step 2: Press Volume UP + Power Button For 10 seconds while connecting the USB cable from your device to your computer. That must make you boot into the bootloader mode.
(Update: A user has reported that holding the power button is optional on some models. Thanks to @sminki for pointing that out).
• Step 3: Head to your computer and download and install the following tool:
http://forum.xda-developers.com/show....php?t=2433454
• Step 4: Download the latest complete update file (B121) from:
http://www.modaco.com/forums/topic/3...s-121115-b140/
Then, extract it and get its UPDATE.app file.
• Step 5: Use the Huawei Update Extractor to extract the (BOOT.img), (SYSTEM.img), (RECOVERY.img), (CACHE.img), (CUST.img), and (USERDATA.img) from the UPDATE.app file that you have extracted from Step 4.
• Step 6: Open your command prompt, and navigate to the right directory where you have extracted the image files. Use the “cd” and “..” commands to do so.
• Step 7: Type the following commands and execute them one by one >
Code:
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
• Step 8: You can also erase the user data if you like by typing and executing the following >
Code:
fastboot flash userdata USERDATA.img
• Step 9: Reboot your device using the following command >
Code:
fastboot reboot
• Step 10: You must be able to boot successfully into the system.
(Noten this model, the "fastboot erase [Partition]" command has been reported by two users that it is not working. Thus, flash the image files directly and if it did not work, then check with the Huawei support center to fix your device. Thanks to @sminki for reporting this).
http://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
TWRP Terminal Emulator command method.
I followed the steps here, http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ Thanks to the Author... hash_brown.1855790
Which is actually for LG, but slightly altering for Honor7 it works!!
for Honor 7 the commands to be run from TWRP Terminal command emulator will be
dd if=/dev/zero of=/dev/block/platform/hi_mci.0/by-name/fota
Click to expand...
Click to collapse
Hit GO/enter(return)...wait, takes a few seconds
Now input this
dd if=/dev/zero of=/dev/block/platform/hi_mci.0/by-name/misc
Click to expand...
Click to collapse
Hit enter (return)...wait again.
When its complete, reboot.
:good:
Alphasampei said:
nope! still boot in twrp, i have no system inside the phone
Click to expand...
Click to collapse
I had the same problem with twrp i can walking through how to unbrick your phone happy to help
Back to Stock with @raystef66's Files
This guide used a method stemmed from paranoia. Now that we have decent flashable files everything is much simpler!
We'll be using raystef66's flashable TWRP files to go completely back to stock. At the end there's instructions if you want to lock your bootloader.
Be sure that you are on the latest TWRP version!
1) Files to Download:
- TWRP Flashable Bootstack/Stocksystem Image from here: Download Center. Download the latest BOOTSTACK and STOCKSYSTEM from there.
- If you want to lock the bootloader, also download the STOCK RECOVERY zip from the same stocksystem version that you downloaded. The flashable stock recovery zips are on the Factory Images Division, right above the TWRP flashable files.
- Magisk 15.2 (or latest), or SuperSU 2.79 (Latest not recommended ). If you will relock the bootloader, skip this part.
2) Installation
- Put all the files on the internal storage or SD card. Backup your important stuff from the internal storage, because you might need to format it!
- Go to TWRP. Wipe data, system and cache (don't format data though).
- Install the bootstack that you downloaded. Then install the stock system.
- If you will NOT relock the bootloader, install Magisk or SuperSU
- Reboot
If the phone asks for a password when it gets to the system, go to TWRP. It will ask for a password, just select Cancel. After you're on the main TWRP screen, select Wipe, then Format data, then type yes. After that, reboot.
3) 5 second screen removal / restore Fastboot
This is useful whether you're relocking the bootloader or not. Just go to raystef66's guide and follow it completely. After doing it your phone will have Fastboot (very good for softbricks and relocking), no 5 seconds screen (your phone will boot up faster) and it will be even closer to full stock.
4) ONLY FOR RELOCKING - Replace TWRP with Stock Recovery
Simply go to TWRP and flash the stock recovery file you downloaded. After that, enable OEM unlocking and USB debugging from the dev options, and then go to Fastboot and issue "fastboot oem lock".
@Choose an username... thanks for the credits.
you can return to stock in that way. you can reflash twrp with tool, allways checking bootloader still unlocked.
I allway update in this way, reboot to twrp, flash the recovery image, not a zip, its the same, but I make sure that the recovery correspond to the base version in my phone. after that, I reboot to system directly, update in the ota way, or the zip way, but from running android, rooted or not, and I dont have to wipe.
After update is done, the most important thing is leave the phone till it is completly booted, then you can reflash twrp with axon7tool again.
You dont need to root, you dont need anything to keep twrp. You only need to flash supersu or magisk if you use darkenfx zips. And if you do it, you have to backup wipe and restore cause you lose encryptation.
But thats all. I think stock rom its still the best, not in battery life, but in camera and bundled apps, It works perfectly, except, I have 2 bugs since allways, wake up with proximity sensor covered, and whatsapp online with app in background, I can live with that
I can re-lock bootloader after this process?
thanks for the guide.
Help Needed ! A2017g Bricked while trying to returning to stock
Hi, Please help me to get my Axon 7 in a working state. I was using Xenon HD Rom for A2017g Oreo. With twrp version as suggested in the guide.
I followed the procedure, installed the bootstack and then stock system B09
But when I tried to reboot, it said no OS Installed. Then I rebooted, and it was stuck at bootloader with no twrp and just the message as follows :
Android Recovery : ZTE/P996A04_N/ailsa_ii
7.1.1/NMF26V/20171120.101942
user/release-keys
Use volume up/down and power
and then certain other options in blue
Please help !
I also have a Problem.
I tried going back to stock from LOS 14.1. Now I am stuck on the 5 seconds screen, it won't continue.
The files I used were the Nougat B10 Files :-/
HansWursT619 said:
I also have a Problem.
I tried going back to stock from LOS 14.1. Now I am stuck on the 5 seconds screen, it won't continue.
The files I used were the Nougat B10 Files :-/
Click to expand...
Click to collapse
Enter the recovery, it should be the stock one (turn the phone off, then hold vol+ and power). Then download a stock B10 file (not the twrp flashable one) and install it from an SD card
No its not the stock one, its still TWRP.
I only flashed Bootstack and stock system (step 2). The reboot afterwards doesnt work
What do you mean by "a stock B10 file"? There are so many files types :-/
I am not quite sure what I should do now, do I have to do the EDL route? That one sounds confusing as well.
EDIT: I tried using B08 Files and now the reboot prompt in TWRP tells me there is no os installed.
Will I, like naveen09y, end up without TWRP if I reboot now?
HansWursT619 said:
No its not the stock one, its still TWRP.
I only flashed Bootstack and stock system (step 2). The reboot afterwards doesnt work
What do you mean by "a stock B10 file"? There are so many files types :-/
I am not quite sure what I should do now, do I have to do the EDL route? That one sounds confusing as well.
EDIT: I tried using B08 Files and now the reboot prompt in TWRP tells me there is no os installed.
Will I, like naveen09y, end up without TWRP if I reboot now?
Click to expand...
Click to collapse
Probably, so just don't. You should just wipe system and data, flash the bootstack, then the system. Also follow raystef's guide to "remove bootloader unlocked inscription"
I now managed to get the phone working with EDL flash of MM B10.
But I cant relock the bootloader :-/
Bascially my bootloader is gone so I cant reboot to it and do "fastboot oem lock".
Why is this such a hassle
HansWursT619 said:
I now managed to get the phone working with EDL flash of MM B10.
But I cant relock the bootloader :-/
Bascially my bootloader is gone so I cant reboot to it and do "fastboot oem lock".
Why is this such a hassle
Click to expand...
Click to collapse
You didn't follow my instructions. Follow raystef's removed unlocked bootloader inscription and you'll get fastboot back. You can do that with the phone on.
Don't relock it unless it's really necessary (i.e. warranty). If you're gonna sell it just follow that guide and don't relock, the 5 seconds screen will disappear and it'll look like it's locked
I cant follow the guide because I can't access the bootloader...
Also the TWRP files in https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 this guide (step 6) are no longer accessible.
HansWursT619 said:
I cant follow the guide because I can't access the bootloader...
Also the TWRP files in https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 this guide (step 6) are no longer accessible.
Click to expand...
Click to collapse
What? Lol
First of all - you are basically installing the bootloader with raystef's guide, so I have no idea why you want to enter it...
You have to enter TWRP and follow the guide from there.
The guide from Controllerboy is basically the same guide but it also has instructions on other things (i.e. unlock etc.). I don't know what you are trying to accomplish with it. Use EDL Tool by djkuz if you want to install TWRP (it is explained there how to do that).
Phone was rooted with Magisk 16, I was on AEX Android 8.1 ROM. I'm trying to return to stock and relock bootloader.
I wiped everything, I flashed A2017G-N-B10-bootstack and A2017G-N-B10-stocksystem from "TWRP flashable Bootstack/Stocksystem Images" section. Booted to system and now phone is stuck on the ZTE POWERED BY android boot screen. 5 minutes there. Is it normal?
Edit: Got tired of waiting and kept pressing the power button. After doing so, the phone reboots but same thing. And I can't access TWRP with VOL INCREASE + POWER BUTTON.... VOL DECREASE + POWER BUTTON takes me to Factory Test Mode.
aLexzkter said:
Phone was rooted with Magisk 16, I was on AEX Android 8.1 ROM. I'm trying to return to stock and relock bootloader.
I wiped everything, I flashed A2017G-N-B10-bootstack and A2017G-N-B10-stocksystem from "TWRP flashable Bootstack/Stocksystem Images" section. Booted to system and now phone is stuck on the ZTE POWERED BY android boot screen. 5 minutes there. Is it normal?
Edit: Got tired of waiting and kept pressing the power button. After doing so, the phone reboots but same thing. And I can't access TWRP with VOL INCREASE + POWER BUTTON.... VOL DECREASE + POWER BUTTON takes me to Factory Test Mode.
Click to expand...
Click to collapse
Try this.
Oki said:
Try this.
Click to expand...
Click to collapse
Yes, thanks. I already had seen it some minutes ago. It's so convenient that you posted this guide today lol
I want to flash stock rom from RR Nougat. I have installed latest twrp, flash bootstack and then stock system. After that I flash supersu 2.79. But when I press reboot system it say no OS installed
Willchi said:
I want to flash stock rom from RR Nougat. I have installed latest twrp, flash bootstack and then stock system. After that I flash supersu 2.79. But when I press reboot system it say no OS installed
Click to expand...
Click to collapse
The best way to return to stock is via EDL, for example MiFlash or EDL tool. If you have an U, then DrakenFX's zips can do that, it happened to me already. Usually G zips like raystef's work just fine.
Try using Magisk instead of SuperSU, just in case. Use 16.7
@Choose an username...
Thanks for posting this.
Credits to all concerned a big thumbs up.
I do however feel that there are to many versions of the Axon 7 packages and I can see why people are ending up with boot issues etc.
Syberclone said:
@Choose an username...
Thanks for posting this.
Credits to all concerned a big thumbs up.
I do however feel that there are to many versions of the Axon 7 packages and I can see why people are ending up with boot issues etc.
Click to expand...
Click to collapse
what
you do realize this guide is older than a year right?
Yeah, its all good
Hi to all. I'm new in Honor world and I've stopped my Android experience with KitKat so I'm a little bit confused ...
I've read several guides (on XDA too) that that three steps to obtain root are unlock bootloader, flash TWRP via ADB and then install Magisk or SuperSU via TWRP. But in the thread on TWRP is clearly written that to install Magisk decryption is needed and to have decryption we must flash a kernel with encryption disabled in fstab. But no guide says anything about this step. Can someone explain me how encryption/decryption work doing a standard installation of TWRP ? Is needed a flash of a modified kernel ? And where find it ?
And another question (if it's not too much ). Since I don't need to install custom rom (I want root only to use some apps like Titanium) how can I make a backup of stock rom, boot.img, efs partition and all that can be useful to restore phone to the starting point if, by chance, I need Huawei warranty ?
Thanks a lot
Hi, apparently there's a way to get root on an encrypted system. Follow the rebrand guide and then flash supersu in TWRP via ADB sideload. It worked for me and a few others, there is no comment from the developers as of right now.
So basically in short follow this guide until you are finished with the TWRP section:
https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829
Then
- enter twrp
- adb sideload supersu
Afterwards follow the "rooting!" section with point 2
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
unvisigoth said:
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
Click to expand...
Click to collapse
The method is also working fine with Magisk. Let me know if you need help
zxz0O0 said:
The method is also working fine with Magisk. Let me know if you need help
Click to expand...
Click to collapse
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
unvisigoth said:
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
Click to expand...
Click to collapse
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
shiboby said:
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
Click to expand...
Click to collapse
Here what I have done:
Unlock bootloader
install adb drivers (find something that is right for your PC. For example minimal ADB found on XDA weren't suitable for me. Google adb drivers...). Open a command windows (shift+right click). If typing "adb devices" your phone is found that's ok
Enable usb debugging and oem unlock (or in other words disable FRP, factory reset protection)
Put the phone in fastboot mode ("adb reboot bootloader"). If all ok typing "fastboot devices" your phone is found
Type "fastboot oem unlock xxxxxxxx" (xxxxxxxx is the code provided by Huawey)
Bootloader unlocked
Flash TWRP
Download TWRP recovery for Honor 9 (link found on other thread on this forum)
Put the phone in fastboot mode
Type "fastboot flash recovery xxxxx.img" (where xxxx.img is the recovery downloaded)
Reboot phone directly in Recovery to avoid erecovery overwrite TWRP. Booting on TWRP let TWRP patch to avoid erecovery booting
Now here I've had some issues as said (read previous post). My tip is the following:
after rebooting in TWRP make all wipes then reboot again in TWRP
Install Magisk.zip (for me download here https://geekaxe.com/root-honor-9-twrp-bootloader-unlocking/)
Reboot recovery
All wipes
Reboot to system
If it's all OK you can install magisk.apk and you are rooted
I suggest after flashing TWRP to make backup of all partitions on external SD (for some reasons, maybe encryption, backup on internal storage gives error). Again I suggest to copy all files that you need (i.e. magisk files) on external sd before starting all.
Pay attention that if you update firmware after this procedure I think that you must repeat all. For me I remain on original firmware found on phone (B100). B130 seems to have some bugs, B120 doesn't seem improve much. Moreover all releases are 7.0 based. I wait for Oreo, hopefully in some custom rom!
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Zuzler said:
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Click to expand...
Click to collapse
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
unvisigoth said:
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
Click to expand...
Click to collapse
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
adriansticoid said:
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
Click to expand...
Click to collapse
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Observe and be careful man.
Sent from my Honor 8 Pro using XDA Labs
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Which TWRP version did you use?
I had a similar problem after formatting all data with the OpenKirin TWRP 3.1.1 Perhaps its an issue with this TWRP release?
I was able to recover in similar circumstances by flashing a stock boot.img over fastboot. Based on this, it's looking like Magisk is really the way to go for rooting atm. Making sure to pull my twrp backup with adb this time though.
If I'm lucky enough to install magisk and not get a bootloop the safetynet always fails. Anyone got a valid method of actually getting magisk working fully?
I wanted to make sure everyone read this part first so that you know it's critical to backup because it happened to me figuring things out. If for any reason you are stuck in a boot loop, just reload twrp recovery and restore boot.img that you backed up for an easy quick fix.
Install drivers and adb on your PC.
Open command prompt or search 'cmd'.
Navigate to the directory with adb.exe
Download and store TWRP 2.2.2 (preferred) in the same directory where adb is located. Recommend renaming recovery file to recovery.img
Enable usb debugging on device by going to settings > about > and click on MIUI version repeatedly until developer settings are enabled. Go back and select additional settings to enable usb debugging.
Run the command: adb devices - to verify if able to connect to device (the serial number of your device will populate if so.
Run the command: adb reboot bootloader and phone device should say "Fastboot" in blue font
Run the command: fastboot boot recovery.img
Recovery will show in Chinese, click on the bottom right button to select English
May require to enter your default password you use to unlock your phone normally.
Click backup and be sure to backup system, boot, and recovery most of all so it's easy to recover your device moving forward.
Download and save SuperSU (I have been unsuccessful in getting Magisk to work at this time) onto storage device from PC to MI 8 that should appear with your Internal storage
Click on "Mount" in TWRP and unselect read-only
Click "Install" and flash SuperSU then reboot (my device rebooted one time and fully boot up the 2nd time so you're not alarmed)
Links:
SuperSU: https://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip?retrieve_file=1
TWRP: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-2-0703-t38126005
Appreciate any feedback, ideas, thoughts, or suggestions where all can collaborate and expand where we help each other further. Look forward to the future development of the MI 8 folks! Please note, I wanted to share the method that seemed to work best for me, but please be aware each and every single MI 8 device is not always exactly the same and the end result may vary and I'm not held accountable or responsible should you choose to follow the directions listed above. However, I wanted to share this information to help avoid any frustration going forward and save you time.
p.s. - If someone could help me figure out how to get twrp recovery to hold and not end up being replaced by mi recovery I would be most grateful as this has been an issue for me (I tried flashing, booting, and installing the img through twrp with no success). Thank you.
Hello thanks for your guide but i think we first need to unlock bl And for the twrp recovery to stick and not to be replaced by xiaomi recovery we need to flash something called "dm-verity " it basically removes that check, which replaces any other recovery by xiaomi recovery
Have a nice day and thanks for your work
I thought so as well, unfortunately I just haven't had much luck with dm verity which led to a soft brick on my device. I'll have to look over the code as it may vary in comparison to other xiaomi devices.
Sent from my MI 8 using Tapatalk
Fastboot flash recovery Command should do it ..
mekaziah said:
I wanted to make sure everyone read this part first so that you know it's critical to backup because it happened to me figuring things out. If for any reason you are stuck in a boot loop, just reload twrp recovery and restore boot.img that you backed up for an easy quick fix.
Install drivers and adb on your PC.
Open command prompt or search 'cmd'.
Navigate to the directory with adb.exe
Download and store TWRP 2.2.2 (preferred) in the same directory where adb is located. Recommend renaming recovery file to recovery.img
Enable usb debugging on device by going to settings > about > and click on MIUI version repeatedly until developer settings are enabled. Go back and select additional settings to enable usb debugging.
Run the command: adb devices - to verify if able to connect to device (the serial number of your device will populate if so.
Run the command: adb reboot bootloader and phone device should say "Fastboot" in blue font
Run the command: fastboot boot recovery.img
Recovery will show in Chinese, click on the bottom right button to select English
May require to enter your default password you use to unlock your phone normally.
Click backup and be sure to backup system, boot, and recovery most of all so it's easy to recover your device moving forward.
Download and save SuperSU (I have been unsuccessful in getting Magisk to work at this time) onto storage device from PC to MI 8 that should appear with your Internal storage
Click on "Mount" in TWRP and unselect read-only
Click "Install" and flash SuperSU then reboot (my device rebooted one time and fully boot up the 2nd time so you're not alarmed)
Links:
SuperSU: https://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip?retrieve_file=1
TWRP: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-2-0703-t38126005
Appreciate any feedback, ideas, thoughts, or suggestions where all can collaborate and expand where we help each other further. Look forward to the future development of the MI 8 folks! Please note, I wanted to share the method that seemed to work best for me, but please be aware each and every single MI 8 device is not always exactly the same and the end result may vary and I'm not held accountable or responsible should you choose to follow the directions listed above. However, I wanted to share this information to help avoid any frustration going forward and save you time.
p.s. - If someone could help me figure out how to get twrp recovery to hold and not end up being replaced by mi recovery I would be most grateful as this has been an issue for me (I tried flashing, booting, and installing the img through twrp with no success). Thank you.
Click to expand...
Click to collapse
Skickat från min MI 8 via Tapatalk
what issues do you get with magisk? I was able to flash it without any issues.
superior8888 said:
Fastboot flash recovery Command should do it ..
Skickat från min MI 8 via Tapatalk
Click to expand...
Click to collapse
Yes it does. Don't know why anyone would run SuperSU though.
mekaziah said:
I thought so as well, unfortunately I just haven't had much luck with dm verity which led to a soft brick on my device. I'll have to look over the code as it may vary in comparison to other xiaomi devices.
Click to expand...
Click to collapse
MAKE SURE U HAVE UNLOCKED BOOTLOADER
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
-fluffy- said:
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
Click to expand...
Click to collapse
Would you mind stating the version of Magisk?
Strange Guide no Attention for Unlok Bl.
barrielui said:
Would you mind stating the version of Magisk?
Click to expand...
Click to collapse
16.4
magisk has been working fine for me for a while
samwise110712 said:
what issues do you get with magisk? I was able to flash it without any issues.
Click to expand...
Click to collapse
What's your ROM version? I flash twrp then magisk, bootloop...
-fluffy- said:
MAKE SURE U HAVE UNLOCKED BOOTLOADER
here is wat i do
first i boot into twrp
(make sure u have rom.zip magisk/superuser.zip an twrp.img) on internal storage
then i wipe
dalvik cache
cache
data (NOT FORMAT)
system
then i flash
rom.zip
twrp.img
then i reboot recovery
fkash magisk.zip
then reboot system
now i have new rom an still have twrp on
Click to expand...
Click to collapse
Hello how did you flash the TWRP through the TWRP ???
What version of MiUi you have ???
omek07 said:
Hello how did you flash the TWRP through the TWRP ???
What version of MiUi you have ???
Click to expand...
Click to collapse
simple put twrp.img on ur storage
then flash img from twrp
-fluffy- said:
simple put twrp.img on ur storage
then flash img from twrp
Click to expand...
Click to collapse
Yes but its asking after in which partition.
What partition you chose ?
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
-fluffy- said:
simple put twrp.img on ur storage
then flash img from twrp
Click to expand...
Click to collapse
Could you please tell me what rom you have ???
Thank you
omek07 said:
Yes but its asking after in which partition.
What partition you chose ?
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
Could you please tell me what rom you have ???
Thank you
Click to expand...
Click to collapse
u choose recovery
im using miui eu
magisk is running without any issue.
i am on the newest xiaomi eu beta rom and flashed magisk 16.7 without any issue right now
(after waiting horrible 15 days for unlocking the bootloader)
Ok so both of you have the xiaomi eu. I have global stable 9.5.11. so maybe that's the problem
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
So both of you have xiaomi eu rom. I have global stable 9.5.11. maybe that's the problem.
omek07 said:
Ok so both of you have the xiaomi eu. I have global stable 9.5.11. so maybe that's the problem
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
So both of you have xiaomi eu rom. I have global stable 9.5.11. maybe that's the problem.
Click to expand...
Click to collapse
I have the lastest global version, I cannot get the root access...
Someone tell me flash the Chinese verision then flash xiaomi.eu and magisk.
felixrao said:
I have the lastest global version, I cannot get the root access...
Someone tell me flash the Chinese verision then flash xiaomi.eu and magisk.
Click to expand...
Click to collapse
My friend i changed to the Xiaomi eu and everything worked. You dont have to flash the Chinese Version first you can go from Global to Xiaomi.eu. Just dont forget to do FORMAT data and not only Wipe Data.
The TWRP for the HD1910 works perfectly on the HD1925. Decryption works too. Install TWRP by using the installer.
Exact the img from the installer zip.
Boot to fastboot
Open a CMD within the extracted TWRP installer folder and type in
"fastboot boot recovery.img"
Once TWRP boots, then install the TWRP installer zip file.
I flashed magisk and it flashed with no issues. I used the latest version here.
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
NOTE: I did it on the latest version, 11.0.1.18 So I'm not sure if it works on any older versions but I would assume so.
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
starcms said:
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
Click to expand...
Click to collapse
I already know about all that. I've had this phone over a year, so I'm familiar with the hidden "secrets".
starcms said:
Yep, been out a while now. Works perfectly! However I highly highly recommend not using the twrp installer zip on our phones nor installing it by doing "fastboot flash recovery name_of_twrp.img"
Just download the latest .img and do "fastboot boot name_of_twrp.img" whenever you need to go into twrp recovery. Or you're just asking for trouble with OTA updates definitely no longer working (until you restore the stock recovery that matches the exact version of OOS that you are running) and a good possibility of getting a Qualcomm Crash-dump and losing or breaking all kinds of stuff.
Click to expand...
Click to collapse
BTW, with unlocked bootloader OTA's are not available no matter what type of recovery you have installed. Unless you have reinstalled the reserve.img after unlocking the bootloader
AntiSocialSingh said:
@BobbyLynn I followed your tutorial to install the CrDroid recovery. Can you tell me how to flash TWRP? Bit of a noob for this phone.
Click to expand...
Click to collapse
Exact (Unzip) the zip folder. Within the extracted folder you'll see some other files. One of them is a recovery.img file. Open a command or PowerShell in the extracted folder. Reboot to fastboot.
Boot to fastboot and run this command
"fastboot boot recovery.img"
Once it boots into TWRP, then click on "install" and locate the TWRP installer zip and select it. It'll most likely be in the download folder. Just make sure you know where the TWRP installer zip is located before you even boot into TWRP
BobbyLynn said:
Exact (Unzip) the zip folder. Within the extracted folder you'll see some other files. One of them is an .img file (recovery). Open a command or PowerShell in the extracted folder. Reboot to fastboot.
Boot to fastboot and run this command
"fastboot boot recovery.img"
Once it boots into TWRP, then click on "install" and locate the TWRP installer zip and select it. It'll most likely be in the download folder. Just make sure you know where the TWRP installer zip is located before you even boot into TWRP
Click to expand...
Click to collapse
BTW download this TWRP from the link in my thread "twrp-installer-3.6.1_11-0-hotdog.zip"
AntiSocialSingh said:
@BobbyLynn Do i need to flash both a & b like i did in the case of crDroid?
Click to expand...
Click to collapse
Not at all. The installer will take care of all that once you boot into TWRP
AntiSocialSingh said:
@BobbyLynn Should I take a backup? Would it wipe my storage? or it would be as it is?
Click to expand...
Click to collapse
No it won't wipe data or anything else. But it's always good to have a backup just in case anything goes sour.
AntiSocialSingh said:
@BobbyLynn I am on the screen which says Install, Wipe, Backup, restore...... what should i do to install the zip file now?
Click to expand...
Click to collapse
Just click on "install" then located the installer zip file then select it and install it
AntiSocialSingh said:
I copied the .zip file on my phone but cannot navigate to it since all it shows is (Up A level), does not show the directories inside the storage
Click to expand...
Click to collapse
Select up a level then scroll down until you see a file called "storage" that'll take you to your storage. If it doesn't, the go back and click on "sdcard" But I'm almost certain it's in the storage folder
AntiSocialSingh said:
I think i need to flash it once via TWRP, i'll try it later, but thank you, it means that this TWRP works!
Click to expand...
Click to collapse
I just checked..... The "sdcard" folder is the one that takes you to the internal storage where the download folder is located. But as soon as you hit 'install" it should've taken you straight to the internal storage. If it didn't, then it sounds like it's still encrypted. If that's the case, then remove any screen locks on your phone before flashing TWRP
AntiSocialSingh said:
@BobbyLynn Let me try once again with the screen lock removed.
Click to expand...
Click to collapse
When I installed TWRP I didn't have a screen lock. But after installing TWRP I set a screen lock and TWRP decrypted just fine. So I'm guessing if you install TWRP while you have a screen lock it doesn't install properly so it can't decrypt. It appears that any screen locks must be removed before installing and after installing reapply a screen lock
AntiSocialSingh said:
@BobbyLynn It worked! So basically, I had to remove both fingerprint and pattern locks to get it to work. Thanks a ton!!
Click to expand...
Click to collapse
No problem
BobbyLynn said:
No problem
Click to expand...
Click to collapse
I'm kinda curious, why did you install TWRP? Are you fixing to "test drive" some custom ROM's or flash some mods? Or did you install TWRP just for the hell of it?
AntiSocialSingh said:
@BobbyLynn The latter yes, test driving some mods, and I am used to the interface of TWRP, not crDroid much, personal preference hahahaha....Thank you so much once again. you're a legend.
Click to expand...
Click to collapse
I'm more use to TWRP myself. I started using TWRP about 10 years ago, it was and still is the best recovery out there. I just happened to install crDroid the other day just to test something. And that test turned out to be a great discovery of a simple way to root the stock firmware. Since I have a extra McLaren, I do quite a bit of testing and modding and experimental stuff. I'm currently working on installing the global firmware (unbranding) it. No luck yet, but I might be getting close.
AntiSocialSingh said:
@BobbyLynn I will be the first one to follow your tutorial if you manage to flash the Global ROM on it sir. I promise haha!
Click to expand...
Click to collapse
You can bet your ass that if I pull off that trick it'll get LOT'S of comments from people thanking me lol. We've been wanting to install the global firmware on this phone, but nobody can figure out how to mod the ROM to make it flash on this phone. There's some very smart developers that own this phone, so I'm surprised that none of them have figured it out yet. So I've been tinkering around with trying to install it. It's looking like I'm going to have to make some modifications to the global ROM and/or the phone too to make the MSM tool see the phone as a comparable device
BobbyLynn said:
BTW, with unlocked bootloader OTA's are not available no matter what type of recovery you have installed. Unless you have reinstalled the reserve.img after unlocking the bootloader
Click to expand...
Click to collapse
Well, yeah, restoring reserve.img is a prerequisite to get OTAs with the bootloader unlocked, but it only has to be done once. After that, for each ota, just restore the boot image to stock (uninstall magisk) and you're good to go
starcms said:
Well, yeah, restoring reserve.img is a prerequisite to get OTAs with the bootloader unlocked, but it only has to be done once. After that, for each ota, just restore the boot image to stock (uninstall magisk) and you're good to go
Click to expand...
Click to collapse
I wanted to do OTA how should I restore my reserve.img?