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?
Related
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
PytSkee said:
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
Click to expand...
Click to collapse
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
elaurens said:
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
Click to expand...
Click to collapse
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
PytSkee said:
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
Click to expand...
Click to collapse
Hm, from what I've found on the miui forum, you're not the first one having this issue. These are the "possible" solutions I've gathered from a couple of threads.
1) Flash TWRP using fastboot (rename twrpxxxx.zip to recovery.zip and place it in the same folder as the fastboot executable):
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
2) Update your current ROM (stable/developer) to the latest version if that isn't the case yet and try flashing TWRP again trough the update app
3) Flash TWRP using Flashify
1. download flashify app from playstore and give root acces
2. download img of twrp for redmi 2 note and put in your sd card (I prefer sdext root folder)
3. Open flashify, select "recovery image", find the img file you've downloaded
4. confirm flash, wait until it's done
4) Re-download a copy of TWRP or use a different one (like this one for example)
Let me know how it went..
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
PytSkee said:
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
Click to expand...
Click to collapse
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
I remember seeing this right after I ordered my phone. I had totally forgotten about it by the time I got it though, as it was more than a month later But thanks for reminding me, I already have it installed on my home PC!
https://dl.twrp.me/angler/
So flash, much excite, such new. Wow.
Edit - I know I sound weird but I don't like dirty flashes. I always reboot into bootloader, fastboot erase recovery and then fastboot flash recovery twrp.img ( I rename it twrp.img for short) then boot into it. I have done this for years on BL unlocked devices and never had a problem flashing twrp. It's just ME, but I think it is fun typing the stuff, and it assures me that I have a clean state and am not dirty flashing anything! Also, on others phones I use RASHR instead of flashify. Once again, personal preference but have had better luck.
XDA Thread updated
And backs up with finger print
^ That's great news.
I tried flashed this but after trying to reboot into recovery got the broken android icon. Reflashed back to older version and it worked. Not sure if I had a corrupt come. Do you have to reboot the bootloader after flashing from fastboot for it to take? I just rebooted to system after flashing.
synnyster said:
I tried flashed this but after trying to reboot into recovery got the broken android icon. Reflashed back to older version and it worked. Not sure if I had a corrupt come. Do you have to reboot the bootloader after flashing from fastboot for it to take? I just rebooted to system after flashing.
Click to expand...
Click to collapse
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Gytole said:
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Click to expand...
Click to collapse
I flashed via fastboot after I updated to the newest android February security patch.
synnyster said:
I flashed via fastboot after I updated to the newest android February security patch.
Click to expand...
Click to collapse
Okay you're on stock?
Gytole said:
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Click to expand...
Click to collapse
Gytole said:
Okay you're on stock?
Click to expand...
Click to collapse
Stock systemless root. Used Heisenberg's guide step 10 to update. Saw TWRP 3.0 so decided to try that.
synnyster said:
Stock systemless root. Used Heisenberg's guide step 10 to update. Saw TWRP 3.0 so decided to try that.
Click to expand...
Click to collapse
Fastboot erase recovery, then reflash twrp recovery, boot into recovery and reflash systemless root.
No problem dirty flashing here, but the process is a little different than it was on my previous phone where you would just flash it like a ROM...
You gotta:
"Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash."
OP's method seems like the best bet though...
Sent from my Nexus 6P using Tapatalk
"No problem dirty flashing here, but the process is a little different than it was on my previous phone where you would just flash it like a ROM..."
That's cause you're use to flashing zips people make flashable, i'm old school and use img's hahaha "LET'S MAKE FLASHING FUN!" Shutup Gytole...
Just out of curiosity has anyone tried flashing twrp as boot? I also have a thread in the tmobile G3 section and I almost wonder if thats why they bork their phone...lol
Just did it on my girlfriends G3 through twrp and was like, "they totally flashed it as boot...."
Used twrp manager from Google store was simple and easy
ROADKING17 said:
Used twrp manager from Google store was simple and easy
Click to expand...
Click to collapse
Way to deviate from the norm! Haha
Gytole said:
Way to deviate from the norm! Haha
Click to expand...
Click to collapse
Takes all kinds...
Sent from my Nexus 6P using Tapatalk
No need for this thread, as there is a TWRP thread in the development forum.
Thread closed.
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
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?
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed