I need help getting back to stock recovery on my h7.
I have twrp right now and basically, i need a way to flash stock recovery without a pc since i don't have access to one anymore.
Any help would be appreciated
I have version B140 eu,bootloader unlocked,rooted with xposed
You will need to find the b140 recovery file some where but there is a official twrp app in the playstore that can flash your recovery (Even if the file isn't twrp).
Edit: I have attached the recovery from B330 (From the UK build. not eu or us) I think it should just work even if your on a different emui version since it work independently but I'm not sure so do it at your own risk.
0v3r cl0ck3d said:
You will need to find the b140 recovery file some where but there is a official twrp app in the playstore that can flash your recovery (Even if the file isn't twrp).
Edit: I have attached the recovery from B330 (From the UK build. not eu or us) I think it should just work even if your on a different emui version since it work independently but I'm not sure so do it at your own risk.
Click to expand...
Click to collapse
my personal suggestion is not to mess with different recoveries unless you know that wont hurt to flash, that can lead full bricking device....
thelous said:
my personal suggestion is not to mess with different recoveries unless you know that wont hurt to flash, that can lead full bricking device....
Click to expand...
Click to collapse
You could still just go into bootloader mode and flash everything back to stock (Although a pc would be needed).
I have the b140 recovery and i saw 3 apps. Flashify,rashr,flashFire. I was going to try flashify yesterday but didn't because im afraid my whole device may brick. What do u think? Should i try? Which app then? :/
Related
I accidentally flashed TWRP to the boot instead of recovery. Whenever I turn on the phone it goes straight to TWRP. As it stands the phone is unsuable! AS far I understand it the way to fix this is to flash the phone's original boot.img to the boot. Is this correct? If so my phone is MT2L03 with the 5.1 update. Does anynone know of any link or could anyone PLEASE share their stock boot.img with me. I really need help!
Thank You.
Boot image is part of OS. If you want to install CM12, while you are in twrp, just transfer the cm12 rom and gapp from pc to your sdcard, then flash both. You get complete cm12 with its boot image.
But if you want stock boot image back, you can just flash the stock firmware using the 3 button boot. It is available in the "official stock firmware" section in the INDEX page: http://forum.xda-developers.com/showthread.php?t=3149530
If you have difficulties doing that, let us know. I maybe can find it somewhere, but to be honest, I don't use stock anymore once CM is out.
Thanks. CM12 flash problem
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
fcbfan2k said:
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
Click to expand...
Click to collapse
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Moody66 said:
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Click to expand...
Click to collapse
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Also twrp, have you install the twrp listed in that same page? other twrp version doesn't work.
Edit, saw you mentioned already that install twrp error using app. So try install the correct twrp in bootloader.
fcbfan2k said:
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Click to expand...
Click to collapse
If you flashed b321 boot image you are not on b322 boot... And the correct twrp is found in the same OP....
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
undesputed said:
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
Click to expand...
Click to collapse
Reinstallt it try this TWRP http://www.mediafire.com/download/15g5i63gke9ddgp/kiwi_twrp_3-21_recovery.img its version 3.0.2.0 (Most recent)
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
mooms said:
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
Click to expand...
Click to collapse
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Arobase40 said:
Do you mean 3.0.2.0 is newer and supports more partitions than 5-14 ???
Click to expand...
Click to collapse
Their both 3.0.2.0 the one I just posted has more features
Sent from my SM-N920T using Tapatalk
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
@clsA
frp is labeled as "UNLOCK" as oppsed to bootloader labeled as "UNLOCKED".
If it's just about removing my google account, will this be resolved the next time I do a factory reset?
Nevertheless, thank you so much for the command fastboot boot twrp.img, I realized that that was what I had used the last time.
I'm currently able to boot into TWRP this way. Awesome!
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
mooms said:
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
Click to expand...
Click to collapse
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
clsA said:
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
Click to expand...
Click to collapse
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
mooms said:
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
Click to expand...
Click to collapse
USB-OTG works flawlessly on the 5-14 version I was not able to use it with the newer one @yuweng posted in his guide
the screen shots show all the partitions it's able to work with
Arobase40 said:
I thought 3.0.2.0 was just an interim version between twrp_2-27 and twrp_5-14... ^^
Click to expand...
Click to collapse
your confusing TWRP versions with TWRP release dates
2-27 and 5-14 are release dates where as 3.0.2.0 is the version of TWRP not the date
the first version of TWRP for this device was actually 2.8.7.0 and was released on 2-16-2016
Same issue
Hey so I have the same exact issue umm did you ever resolve this problem becuSe I can't seem to crack it and it's a bit frustrating cuz by no means am I a pro but coming from using the OnePlus one the OnePlus 2 the OnePlus x and the Nexus 6 rooting them and restoring them after many failed attempts resulting in bricking my phone and even eventually unbrick them I do know a thing or two and I am stumped please help you are the only other person in this world other then my self that seems to be having this issue if you don't mind would you be so kind and email gmail me cuz I don't use or check this forum often thanks millerfamily805
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
Can it be used with other honor devices?
Got my answer... Thanks...
Sent from my PLK-L01 using XDA Labs
It depend on the device
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Fonku said:
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Click to expand...
Click to collapse
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
zinko_pt said:
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
Click to expand...
Click to collapse
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Fonku said:
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Click to expand...
Click to collapse
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
zinko_pt said:
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
Click to expand...
Click to collapse
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Fonku said:
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
You can use B130 as it is also Lollipop. But all the img from the same rom. You can update to B350 manually after, but first you need a stable rom working.
Let us know man if you fixed your phone. So if not, we can give firther recommendations.
Sent from my Galaxy Tab 3 using XDA Labs
Hi.
The last couple days, I unlocked my bootloader to install the phh-treble rom and experiment with this phone but the *unlocked bootloader* message every time that I power up my phone, is very annoying.
So I ask if anyone knows which firmware to install to my phone so I can lock the bl and receive otas as normal
Thanks
t-shock said:
Hi.
The last couple days, I unlocked my bootloader to install the phh-treble rom and experiment with this phone but the *unlocked bootloader* message every time that I power up my phone, is very annoying.
So I ask if anyone knows which firmware to install to my phone so I can lock the bl and receive otas as normal
Thanks
Click to expand...
Click to collapse
It's just a guess, but i think that you should flash an original "system. img" with fastboot and then reset you device.
You can use Huawei Unpacker to get your system.img from a FullOTA firmware (you can download it with Firmware Finder).
Pretoriano80 said:
It's just a guess, but i think that you should flash an original "system. img" with fastboot and then reset you device.
You can use Huawei Unpacker to get your system.img from a FullOTA firmware (you can download it with Firmware Finder).
Click to expand...
Click to collapse
Thanks for that
But having used this guide ( https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 ) I guess it changes more that the system
t-shock said:
Thanks for that
But having used this guide ( https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 ) I guess it changes more that the system
Click to expand...
Click to collapse
When you go to recovery now, is it Huawei recovery or some aosp recovery?
If Huawei you should be able to use that same guide to go back to stock. You just need to download the Firmware your phone came with (Ex. L29 C432), then update using the guide. Or you could rebrand and install fw.
ante0 said:
When you go to recovery now, is it Huawei recovery or some aosp recovery?
If Huawei you should be able to use that same guide to go back to stock. You just need to download the Firmware your phone came with (Ex. L29 C432), then update using the guide. Or you could rebrand and install fw.
Click to expand...
Click to collapse
It is the Huawei recovery but the weird thing is that it flashes another recovery and kernel before at the fastboot mode.
Anyhow, I just wonder, if I go back to the 127 (following the method above) which is verified thru IMEI, will I be able to get OTAs?
Or
Which is the correct method of restoring the full stock rom in order to have OTAs and lock the BL
t-shock said:
It is the Huawei recovery but the weird thing is that it flashes another recovery and kernel before at the fastboot mode.
Anyhow, I just wonder, if I go back to the 127 (following the method above) which is verified thru IMEI, will I be able to get OTAs?
Or
Which is the correct method of restoring the full stock rom in order to have OTAs and lock the BL
Click to expand...
Click to collapse
Yes, you will get OTA.
If you install a full firmware everything will be replaced (though you can keep bootloader unlocked, but you're asked when you run repack so select yes ("Lock bootloader?").
The "correct" ways would be: HWOTA8, Dload (if available for your firmware), FunkyHuawei (paid).
ante0 said:
Yes, you will get OTA.
If you install a full firmware everything will be replaced (though you can keep bootloader unlocked, but you're asked when you run repack so select yes ("Lock bootloader?").
The "correct" ways would be: HWOTA8, Dload (if available for your firmware), FunkyHuawei (paid).
Click to expand...
Click to collapse
Thanks a lot
Just one last question, if I only have unlocked bootloader and no root , will AI "brake"?
Thanks
t-shock said:
Thanks a lot
Just one last question, if I only have unlocked bootloader and no root , will AI "brake"?
Thanks
Click to expand...
Click to collapse
It shouldn't. And it works again with root. Apparently something broke in SEPolicy, but mankindtw fixed it in his pre-rooted ramdisk. Though, we can install Magisk "normally" now (as a package through recovery) so it shouldn't be a problem anyway SuperSU should install in a similar way too, if one would take the time to make it. I prefer Magisk though
So far throughout xda, I have just got links to stock ROM for other variants like LX1(mostly), which dont support the VoLTE feature. However I fail to find any link for complete stock ROM, both fastboot and recovery, for the ANE-AL00 C675 variant. I am well versed with unbricking Xiaomi, Sony and old samsung devices both from recovery and fastboot, but have no experience with Huawei Devices, and the method for huawei devices seem a bit different.
For e.g. if i want to just boot to recovery(temporarily) and not permanently, I used the command "fastboot boot (recovery_file_name).img" , but I am unable to do so with huawei devices. Seems, commands are slightly different. I am just curious to know a full guide of flashing stock ROM for ANE-AL00 C675 variant both from fastboot and recovery method.
Links for the C675 ROMS would be very much appreciated. Kindly help!!
fbh59 said:
So far throughout xda, I have just got links to stock ROM for other variants like LX1(mostly), which dont support the VoLTE feature. However I fail to find any link for complete stock ROM, both fastboot and recovery, for the ANE-AL00 C675 variant. I am well versed with unbricking Xiaomi, Sony and old samsung devices both from recovery and fastboot, but have no experience with Huawei Devices, and the method for huawei devices seem a bit different.
For e.g. if i want to just boot to recovery(temporarily) and not permanently, I used the command "fastboot boot (recovery_file_name).img" , but I am unable to do so with huawei devices. Seems, commands are slightly different. I am just curious to know a full guide of flashing stock ROM for ANE-AL00 C675 variant both from fastboot and recovery method.
Links for the C675 ROMS would be very much appreciated. Kindly help!!
Click to expand...
Click to collapse
You can use Firmware Finder app from google play and browsing online with this link to find all firmware available from Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=&firmware_page=0
Boot temporary in the recovery I think it is not possible or I don't know the right commands.
Flash a complete firmware via fastboot mode should be possible but as far as I know only a pay service can handle that, like DC Phoenix.
Flash the most important partition via fastboot mode is possible, like recovery_ramdisk, ramdisk, cust, system, etc.
Flash Full ROM:
- System update (stock recovery)
- Firmware Finder (stock recovery)
- HuRUpdater (TWRP)
- HwOTA8 for Huawei P20 Lite (Recovery_NoCheck)
kilroystyx said:
You can use Firmware Finder app from google play and browsing online with this link to find all firmware available from Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=&firmware_page=0
Boot temporary in the recovery I think it is not possible or I don't know the right commands.
Flash a complete firmware via fastboot mode should be possible but as far as I know only a pay service can handle that, like DC Phoenix.
Flash the most important partition via fastboot mode is possible, like recovery_ramdisk, ramdisk, cust, system, etc.
Flash Full ROM:
- System update (stock recovery)
- Firmware Finder (stock recovery)
- HuRUpdater (TWRP)
- HwOTA8 for Huawei P20 Lite (Recovery_NoCheck)
Click to expand...
Click to collapse
Thank you for the help, however I went through the above link (the russian link) earlier too, but could not find any link for C675 variant of P20 Lite handset. Nor it was available in the android app.
Secondly, will a nandroid backup via twrp help me in unbricking my device, in case I flash a wrong firmware or if i try some custom ROMs like Ressurection Remix and later want to switch back to my official ROM with which my device was shipped with? If yes, what partitions should I select for backing up as I have never done with a Huawei device?
(Prior to my experience with Huawei, I took a nandroid backup once in my life with an old Xperia C602, but the restoration bricked my device, but got my device back to life by flashing a full fastboot ROM) So I just wanted to be sure that a nandroid restoration not to cause any soft-bricking of my device.
fbh59 said:
Thank you for the help, however I went through the above link (the russian link) earlier too, but could not find any link for C675 variant of P20 Lite handset. Nor it was available in the android app.
Secondly, will a nandroid backup via twrp help me in unbricking my device, in case I flash a wrong firmware or if i try some custom ROMs like Ressurection Remix and later want to switch back to my official ROM with which my device was shipped with? If yes, what partitions should I select for backing up as I have never done with a Huawei device?
(Prior to my experience with Huawei, I took a nandroid backup once in my life with an old Xperia C602, but the restoration bricked my device, but got my device back to life by flashing a full fastboot ROM) So I just wanted to be sure that a nandroid restoration not to cause any soft-bricking of my device.
Click to expand...
Click to collapse
I didn't saw any firmware for your region so far, the idea is that you can look anytime...
- Yes, nandroid can help you but depends the way how you brick the device. In case that you can reach TWRP should be enough.
- To have more success to unbrick your device you should have always the booloader unlocked and FRP unlock.
- Restore to stock should be also possible in case you are in the customizes ROMs.
- Lock bootloader I think is not possible yet, only relock. Don't try do it with unofficial firmware installed.
- Cust, kernel, odm, product, ramdisk, system, vendor and version are the most important partitions to recovery from the customized rom. You don't need to know this by heart, just check the flashable zip from customized rom which partition was installed previously or better just install the official Huawei firmware.
- Is very easy soft-brick Huawei devices, so, do only things already tested by other users.
If you can wait to have firmware released for your device is more safety because you have more options for unbrick it.
kilroystyx said:
I didn't saw any firmware for your region so far, the idea is that you can look anytime...
- Yes, nandroid can help you but depends the way how you brick the device. In case that you can reach TWRP should be enough.
- To have more success to unbrick your device you should have always the booloader unlocked and FRP unlock.
- Restore to stock should be also possible in case you are in the customizes ROMs.
- Lock bootloader I think is not possible yet, only relock. Don't try do it with unofficial firmware installed.
- Cust, kernel, odm, product, ramdisk, system, vendor and version are the most important partitions to recovery from the customized rom. You don't need to know this by heart, just check the flashable zip from customized rom which partition was installed previously or better just install the official Huawei firmware.
- Is very easy soft-brick Huawei devices, so, do only things already tested by other users.
If you can wait to have firmware released for your device is more safety because you have more options for unbrick it.
Click to expand...
Click to collapse
Thanks for sharing the knowledge
Has anyone found this variant? Needed to relock my bootloader.
I want to know rooting method for ANE-AL00 C675 variant
Arseon said:
Has anyone found this variant? Needed to relock my bootloader.
Click to expand...
Click to collapse
I tried every method that i know to do it.
But failed in each and every method .
Help me out!!