I've managed to flash (using the guide here: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814) the incorrect firmware to my phone. I used the 8.0.0.140 firmware for the BKL-L09 to my BLA-L09. Now, it reports as having no IMEI number and I have no SIM car recognised.
I've tried using the guide above, but it reports as BKL not supported.
How screwed am I? Would something like FunkyHuawei Unbrick Flash Tool work (although the download keeps being reported as having a virus). Has anyone got any ideas?
Thanks.
nea102 said:
I've managed to flash (using the guide here: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814) the incorrect firmware to my phone. I used the 8.0.0.140 firmware for the BKL-L09 to my BLA-L09. Now, it reports as having no IMEI number and I have no SIM car recognised.
I've tried using the guide above, but it reports as BKL not supported.
How screwed am I? Would something like FunkyHuawei Unbrick Flash Tool work (although the download keeps being reported as having a virus). Has anyone got any ideas?
Thanks.
Click to expand...
Click to collapse
See if you can flash TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
If it works, you can re-flash BLA using: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you don't get FBE working you should be able to just Wipe -> Format Data -> 'yes' and use Reboot -> Recovery. This will remove encryption.
After this transfer the HuRUpdater script and firmware zips to internal sdcard.
Be sure to backup internal sdcard before Format Data as this will wipe it.
I'm amazed your phone even boots
ante0 said:
See if you can flash TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
If it works, you can re-flash BLA using: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you don't get FBE working you should be able to just Wipe -> Format Data -> 'yes' and use Reboot -> Recovery. This will remove encryption.
After this transfer the HuRUpdater script and firmware zips to internal sdcard.
Be sure to backup internal sdcard before Format Data as this will wipe it.
I'm amazed your phone even boots
Click to expand...
Click to collapse
You and me both!
I've got TWRP on, but so far it's just showing me the TWRP splash screen and not actually loading into it.
nea102 said:
You and me both!
I've got TWRP on, but so far it's just showing me the TWRP splash screen and not actually loading into it.
Click to expand...
Click to collapse
Boot looping with TWRP. Only shows the splash page for a bit then reboots to the eRecovery.
Evening my brother,
Please relax and don't panic, as you are not alone and by the look of things you won't be the last one. I also did the same thing by rebranding my mate 10 pro to porsche design and flashed the porsche firmware to my 10 pro. After all that my device booted and it was rebranded to porsche design, but without imei, not detecting sim and all I had to do was to rebrand it back to BLA-L29 and flashed the BLA-L29 firmware. All is back to normal working order. I just hope your bootloader is still unlocked.
The bootloader is unlocked, I just can't get into TWRP at the moment.
You don't need TWRP and all you need is to follow the guide in this forum about rebranding. You also don't need FH paying method. Just follow that guide and it is straightforward.
---------- Post added at 06:08 AM ---------- Previous post was at 06:03 AM ----------
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Hayeni said:
You don't need TWRP and all you need is to follow the guide in this forum about rebranding. You also don't need FH paying method. Just follow that guide and it is straightforward.
---------- Post added at 06:08 AM ---------- Previous post was at 06:03 AM ----------
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
I've tried following that method but I get an error message saying "No support BKL".
Ok I see. Please download the firmware package of the exact original model of your mate 10 and try and flash it using the same guide, but of course without rebranding and see if it will take it.
Hayeni said:
Ok I see. Please download the firmware package of the exact original model of your mate 10 and try and flash it using the same guide, but of course without rebranding and see if it will take it.
Click to expand...
Click to collapse
Tried that as well. Still says "No support device BKL"
Ok, I'm in to TWRP. However, it will not let me mount the phone as storage. Nor does it have an SD Card slot that I can put the files on to. Ideas?
nea102 said:
Ok, I'm in to TWRP. However, it will not let me mount the phone as storage. Nor does it have an SD Card slot that I can put the files on to. Ideas?
Click to expand...
Click to collapse
Can your browse to /data using Advanced - File Manager?
And does ADB work?
ADB working - I am currently pushing the files to the phone.
ante0 said:
Can your browse to /data using Advanced - File Manager?
And does ADB work?
Click to expand...
Click to collapse
Ok, so I got all the files on there and tried flashing using HuRUpdater but it errors out. Log here: https://pastebin.com/gXh0sesh
nea102 said:
Ok, so I got all the files on there and tried flashing using HuRUpdater but it errors out. Log here: https://pastebin.com/gXh0sesh
Click to expand...
Click to collapse
Open TWRP terminal OR adb shell:
mount -r /vendor
mount -o rw,remount /vendor
See if it want to flash now.
Which TWRP are you using BTW? (post link to thread)
I've tried a few versions - one starts the install but reboots randomly and then others that bomb out straight away.
ante0 said:
Open TWRP terminal OR adb shell:
mount -r /vendor
mount -o rw,remount /vendor
See if it want to flash now.
Which TWRP are you using BTW? (post link to thread)
Click to expand...
Click to collapse
Still bombs out using this one: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
I've tried 0.4 (reboots), 0.5 and 0.6.
I've also tried this one (random reboots) https://forum.xda-developers.com/mate-10/development/recovery-twrp-3-2-1-0-touch-recovery-t3752399
And I've tried this one: https://forum.xda-developers.com/honor-9/development/oreo-t3754483 (same - bombs out)
Is there a way to recover this installing the Huawei zips through ADB or something?
ante0 said:
See if you can flash TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
If it works, you can re-flash BLA using: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you don't get FBE working you should be able to just Wipe -> Format Data -> 'yes' and use Reboot -> Recovery. This will remove encryption.
After this transfer the HuRUpdater script and firmware zips to internal sdcard.
Be sure to backup internal sdcard before Format Data as this will wipe it.
I'm amazed your phone even boots
Click to expand...
Click to collapse
thanks alot for the link of the tool.
i successfully rebranded my mate 10 pro back to BLA from RNE.
nea102 said:
Is there a way to recover this installing the Huawei zips through ADB or something?
Click to expand...
Click to collapse
Actually, have you tried TWRP for V10?
https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
Else you can try NoCheck, it will let you flash firmware using stock recovery (patched to not do verification).
https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085
(It has only been tested on L04, but I guess it's worth a shot)
You'd just need to get Magisk, which should be easy as you'd only need to patch ramdisk or if you already have it installed.
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
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?
As you know, TWRP still doesn't support FBE, so in-case if you wanna flash another system.img the Wipe data/factory reset in TWRP wouldn't work (at least didn't work for me).
That would force you to get back to stock recovery, which allows a successful factory reset.
Steps are pretty straight forward, if you already have a backup of your stock recovery just do the below steps, if else you could download one from the below link.
Put the device into fastboot mode. There are two ways to do that.
1)By long pressing the power button and volume down button whilst the USB is connected.
2)Just do a adb reboot bootloader command if you could boot into the system.
Then just do
Code:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Then disconnect the USB and long press the power and volume up button until you see the "The device is booting now" message.
Downloads
- Stock recovery for BKL-L09
Thanks, you saved me.
Thanks
Just created a md5sum of your recovery and my backed up recovery. It's exactly the same size but the md5sum is different.
A quick look with a hex editor also shows some big differences. Is that expected?
Copperhead100 said:
Just created a md5sum of your recovery and my backed up recovery. It's exactly the same size but the md5sum is different.
A quick look with a hex editor also shows some big differences. Is that expected?
Click to expand...
Click to collapse
MD5 hash wouldn't possibly match, because the backup was taken using dd and there might be some config files modified or added when I used the stock recovery once. But, hey the thing would work if you have BKL-L09 device
Thanks. This works!
shihabsoft said:
As you know, TWRP still doesn't support FBE, so in-case if you wanna flash another system.img the Wipe data/factory reset in TWRP wouldn't work (at least didn't work for me).
That would force you to get back to stock recovery, which allows a successful factory reset.
Click to expand...
Click to collapse
Mate, will this stock recovery work in Indian model(BKL-L09-C675)?
atf2m4 said:
Mate, will this stock recovery work in Indian model(BKL-L09-C675)?
Click to expand...
Click to collapse
Ofc it does
shihabsoft said:
Ofc it does
Click to expand...
Click to collapse
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
atf2m4 said:
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
Click to expand...
Click to collapse
Not sure, as it might check integrity before giving updates. Just download Firmware Finder app and check for updates constantly.
atf2m4 said:
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
Click to expand...
Click to collapse
You will receive the updates but you won't be able to install them with TWRP. Simply flash the stock recovery and the updates will self install when they come. You'll have to root again with Magisk after the updates, but that's a simple process.
Sent from my Honor View 10 using XDA Labs
Hie,
How can I get back from lineage OS to stock using this? I guess I'm on the same boat as a lot of people out there and could really use some help here. I'm on Cosmos OS and can't go back to stock. I tried flashing this recovery.img but can't figure out a way back.
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Can you help me with the commands please?
---------- Post added at 09:20 PM ---------- Previous post was at 09:12 PM ----------
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Wildfire, can you please help me with the commands? I believe there's an inclusion of ramdisk in the commands now.
---------- Post added at 09:52 PM ---------- Previous post was at 09:20 PM ----------
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoys.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Apparently, there isn't any system.img file in the Indian firmware I downloaded. The rest are there but not the system.img.
Someone please help me out
I can't flash system.img as I was told in an earlier reply, it returns me an error that says 'Error: Cannot load System.':crying: I tried using -P and 256M commands to see the space divided and none of these worked either. CAN SOME PLEASE HELP ME OUT WITH THIS?
I cannot find system.img in the Indian firmware either, that is making things tough for me.
ankan1993 said:
I can't flash system.img as I was told in an earlier reply, it returns me an error that says 'Error: Cannot load System.':crying: I tried using -P and 256M commands to see the space divided and none of these worked either. CAN SOME PLEASE HELP ME OUT WITH THIS?
I cannot find system.img in the Indian firmware either, that is making things tough for me.
Click to expand...
Click to collapse
You should have made a backup before you started "tinkering" with your device. Lesson learned, hopefully.
Sent from my Honor View 10 using XDA Labs
Einwod said:
You should have made a backup before you started "tinkering" with your device. Lesson learned, hopefully.
Sent from my Honor View 10 using XDA Labs
Click to expand...
Click to collapse
Indeed! Can you please help me this one time?
ankan1993 said:
Indeed! Can you please help me this one time?
Click to expand...
Click to collapse
I cannot help you as I do not have your firmware or know anything about the Indian version. Where did you get this firmware from?
Einwod said:
I cannot help you as I do not have your firmware or know anything about the Indian version. Where did you get this firmware from?
Click to expand...
Click to collapse
I downloaded this from https://www.getdroidtips.com/huawei-honor-view-10-b160-oreo-firmware/#Downloads.
ankan1993 said:
I downloaded this from https://www.getdroidtips.com/huawei-honor-view-10-b160-oreo-firmware/#Downloads.
Click to expand...
Click to collapse
What device do you have exactly?
Hey!
A few months ago I rooted my Mate 10 Pro (UK version on Three) using that all-in-one tool. It installed TWRP and Magisk.
I've been having a pending OTA update for months and it fails when trying to install rebooting onto TWRP.
Is there a safe way to go back to stock recovery, let the phone update and then root back? (without wiping the whole thing?) If so, could you please guide me giving some very specific steps? Many thanks!
Use hrupdater 0.4 and twrp, but read well how to do it, if you are on a xloader2 version, you can't install xloader1 version. First read well all threads you can and then if you know what are you doing, update and root again. If you only want to update and you don't mind about root, install the stock recovery and unroot and update via OTA.
Huawei is a diificult smartphone for rooting in my view, be carefull and do all by your own risk, there are many people that have bricked this smartphone due to the lack of knowledge of what they were doing (and others due to bad luck of the downgrade of xloader)
My question is how can you flash to the lastest OTA EMUI 9.0 if twrp doesn't support emui 9.0.
durc12 said:
Use hrupdater 0.4 and twrp, but read well how to do it, if you are on a xloader2 version, you can't install xloader1 version. First read well all threads you can and then if you know what are you doing, update and root again. If you only want to update and you don't mind about root, install the stock recovery and unroot and update via OTA.
Huawei is a diificult smartphone for rooting in my view, be carefull and do all by your own risk, there are many people that have bricked this smartphone due to the lack of knowledge of what they were doing (and others due to bad luck of the downgrade of xloader)
Click to expand...
Click to collapse
I just wanted to continue to expand on this. All the info I gathered is pulled from the link below.
Xloader checker
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you are rooted can also dump your own xloader if you want to see what you're currently on.
Download Terminal Emulator from the play store and open it
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
hungrymr2 said:
I just wanted to continue to expand on this. All the info I gathered is pulled from the link below.
Xloader checker
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you are rooted can also dump your own xloader if you want to see what you're currently on.
Download Terminal Emulator from the play store and open it
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
Click to expand...
Click to collapse
Thank you so much for taking the time to help me out. However, I clicked on that link and I don't understand anything!
My goal is to install the update and keep my phone rooted (a must!). So I downloaded terminal emulator and followed your instructions, now I have an "xloader.img" on my SD card and I don't know what to use to open it or do next. Please have some patience and help me out?
93starletgt said:
Thank you so much for taking the time to help me out. However, I clicked on that link and I don't understand anything!
My goal is to install the update and keep my phone rooted (a must!). So I downloaded terminal emulator and followed your instructions, now I have an "xloader.img" on my SD card and I don't know what to use to open it or do next. Please have some patience and help me out?
Click to expand...
Click to collapse
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
hungrymr2 said:
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
Click to expand...
Click to collapse
I just did an OTA update with HiSuite 9.0.2.304, it was ridiculously easy. I simply clicked update. There's a chance you might lose root.
hungrymr2 said:
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
I just did an OTA update with HiSuite 9.0.2.304, it was ridiculously easy. I simply clicked update. There's a chance you might lose root.
Click to expand...
Click to collapse
Thanks for the tip. Were you rooted before the update? If so, was it Magisk or SuperSu? Also, did you have TWRP installed?
I was not rooted when I installed the ota
hungrymr2 said:
I was not rooted when I installed the ota
Click to expand...
Click to collapse
Right, that's my main problem. If I wasn't rooted I could do the normal update through HiSuite or OTA. I'll click on those links you sent and read thoroughly. Thanks.
First restore stock recovery, flash this script in TWRP to do that https://mega.nz/#!8Swx3QaC!3JQ9imU70E9O1BxgO53Z754lGCZxCbKGgSHqvTEcXsQ
(assuming you haven't modified eRecovery as it will copy its ramdisk to recovery).
Secondly you can go to menu in System Updater and Download Latest full. That one will not fail to install. OTA can fail if you have modified ramdisk, kernel, system, vendor, product, cust (but not all are checked/patched in all OTA).
Full will not wipe data.
ante0 said:
First restore stock recovery, flash this script in TWRP to do that https://mega.nz/#!8Swx3QaC!3JQ9imU70E9O1BxgO53Z754lGCZxCbKGgSHqvTEcXsQ
(assuming you haven't modified eRecovery as it will copy its ramdisk to recovery).
Secondly you can go to menu in System Updater and Download Latest full. That one will not fail to install. OTA can fail if you have modified ramdisk, kernel, system, vendor, product, cust (but not all are checked/patched in all OTA).
Full will not wipe data.
Click to expand...
Click to collapse
I just noticed your reply! So, if I understand correctly, that Mega script is a flashable Zip through TWRP that will restore the stock recovery?
93starletgt said:
I just noticed your reply! So, if I understand correctly, that Mega script is a flashable Zip through TWRP that will restore the stock recovery?
Click to expand...
Click to collapse
Yes. It will write eRecovery_ramdisk to recovery_ramdisk (these partitions are exactly the same, only different entrypoints).
So as long as you have not modified eRecovery_ramdisk by flashing TWRP to it, it will restore your stock recovery.
ante0 said:
Yes. It will write eRecovery_ramdisk to recovery_ramdisk (these partitions are exactly the same, only different entrypoints).
So as long as you have not modified eRecovery_ramdisk by flashing TWRP to it, it will restore your stock recovery.
Click to expand...
Click to collapse
Thank you very much! I booted into TWRP, uninstalled Magisk (by flashing Magisk Uninstall Zip), flashed the stock recovery through TWRP (using the file on the link you gave me: https://mega.nz/#!8Swx3QaC!3JQ9imU70...bKGgSHqvTEcXsQ), rebooted and phone was stock again! I appreciate your help!