Related
Hi guys,
I am using the link below to perform the restore to stock from CM13 but I think I am not interpreting the questions in this post correctly.
http://forum.xda-developers.com/honor-5x/how-to/guide-kiw-l24-to-stock-t3318268
I tried to follow them to get my Honor 5x back to stock rom (while still keeping TWRP) and it was a no go. I kept getting stuck in a boot loop. I was able to immediately reflash CM13 though and get it functionaly. Would someone be kind enough to verify for me as to what steps exactly I need to follow (including ROM names, etc.)? I would greatly appreciate it.
Thanks.
@DigiGoon here's a person needing your help
I have a couple questions for you:
1) Before flashing CM13, what stock firmware version were you on? (e.g. b130, b140, b151, b331)
2) Before flashing CM13, did you take a NANDROID backup of your stock setup? Most guides have this step.
Follow these steps, and you'll get your stock ROM back.
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
Hope this helps you.
@DigiGoon
You are a lifesaver. That seems to have done the trick. Thanks a lot man!
fistfullofbeer said:
Hi guys,
I am using the link below to perform the restore to stock from CM13 but I think I am not interpreting the questions in this post correctly.
http://forum.xda-developers.com/honor-5x/how-to/guide-kiw-l24-to-stock-t3318268
I tried to follow them to get my Honor 5x back to stock rom (while still keeping TWRP) and it was a no go. I kept getting stuck in a boot loop. I was able to immediately reflash CM13 though and get it functionaly. Would someone be kind enough to verify for me as to what steps exactly I need to follow (including ROM names, etc.)? I would greatly appreciate it.
Thanks.
Click to expand...
Click to collapse
There is also a full, latest twrp, recovery backup o.o for b331
You restore everything except data, erecovery, and recovery... 1.6 gig download o.o does the job in one fell swoop as long as you have latest twrp.
Just did this the other day...
fistfullofbeer said:
@DigiGoon
You are a lifesaver. That seems to have done the trick. Thanks a lot man!
Click to expand...
Click to collapse
Happy to help buddy.
DigiGoon said:
Follow these steps, and you'll get your stock ROM back.
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Flash all other extracted files similarly firing these commands.
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
Hope this helps you.
Click to expand...
Click to collapse
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
gabepaul said:
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
Click to expand...
Click to collapse
Yes it does replace, and you simply need to reflash TWRP again
gabepaul said:
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
Click to expand...
Click to collapse
It replaces the TWRP, and if you are flashing stock via 3 button method, then there is no way you can keep it, but if you are getting on stock by flashing individual files then just dont flash the recovery file and you will just have the TWRP alone.
gabepaul said:
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
Click to expand...
Click to collapse
Instead of flashing full update.app , i can help u just to stop doing a lot of work after flash
DigiGoon said:
It replaces the TWRP, and if you are flashing stock via 3 button method, then there is no way you can keep it, but if you are getting on stock by flashing individual files then just dont flash the recovery file and you will just have the TWRP alone.
Click to expand...
Click to collapse
So which is the three button method and which is the other?
gabepaul said:
So which is the three button method and which is the other?
Click to expand...
Click to collapse
Three button method is nothing but by placing update.app in /sdcard/dload/
And then put off the phone followed by pressing vol down+vol up+ power button . This will let it install full stock rom and phone looks brand new in terms of software
gabepaul said:
So which is the three button method and which is the other?
Click to expand...
Click to collapse
As @gopinaidu77 said about three button method, its just that. And about the other one, in that you have to extract all the important img files from UPDATE.APP and flash it via fastboot commands.
DigiGoon said:
As @gopinaidu77 said about three button method, its just that. And about the other one, in that you have to extract all the important img files from UPDATE.APP and flash it via fastboot commands.
Click to expand...
Click to collapse
so I've tried both, and I'm getting stuck on the "Honor for the brave, powered by Android" screen.
I should probably also add that im trying to downgrade from lineage 14.0 Nougat to the android 6.1 emui 3.1
gabepaul said:
so I've tried both, and I'm getting stuck on the "Honor for the brave, powered by Android" screen.
I should probably also add that im trying to downgrade from lineage 14.0 Nougat to the android 6.1 emui 3.1
Click to expand...
Click to collapse
Sorry. 6.0.1 is emui 4.0.1 . Well bro , u can still unbrick ur device . Can i know which build number u are on before u flashed lineageos ?
gopinaidu77 said:
Sorry. 6.0.1 is emui 4.0.1 . Well bro , u can still unbrick ur device . Can i know which build number u are on before u flashed lineageos ?
Click to expand...
Click to collapse
Oh yeah, I have restored it already. I made a nandroid backup, and so when it happened, I just rebooted into fastboot and reflashed TWRP, then restored my phone from the backup. Not sure which build. Wondering what went wrong? And how I can successfully convert to stock
gabepaul said:
Oh yeah, I have restored it already. I made a nandroid backup, and so when it happened, I just rebooted into fastboot and reflashed TWRP, then restored my phone from the backup. Not sure which build. Wondering what went wrong? And how I can successfully convert to stock
Click to expand...
Click to collapse
Extract UPDATE.APP via Huawei Update Extractor tool, pull out relevant img files (system.img, boot.img, recovery.img, recovery2.img(if not in your device), cust.img) flash this one by one via fastboot by booting your device in fastboot mode, fire the given below commands.
Code:
fastboot flash <img name w/o extension> <full path to the relevant img file>
After this try the three button method, if it doesn't work then boot into eRecovery then tap "Download Latest Firmware". It will connect to Wi-Fi and will start downloading the latest firmware of your device. After the process gets completed you'll be on stock ROM with your bootloader in "Locked" state.
You are guiding wrong bro . There is a need of extension too. Else it will give error saying file not found
CUST issue
Hi,
I tried to do the same, Boot.img, system.img and recovery.img are flashed successfully but I cannot flash CUST.img, following error occurs, please help.
it says: while writing 'cust'...,
error: FAILED (remote: command not allowed)
Please help, thanks in advance.
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 Guys,
I've got a SGP511 WiFi only (castor_windy), with root access and an unlocked bootloader. but to install AOSP 7.1 I need to update my version of TWRP to 3.0.0.
I installed TWRP via TabZ2-lockeddualrecovery2.8.26 batch file and can access recovery but every time i select install look at my SD card and change to images and select the castor_winsy 3.0.0 image i dont get an option to install to recovery i only get kernel how do i resolve this ?
I have re flashed FW (KitKat) via flashtool loads of times
rooted
installed TabZ2-lockeddualrecovery2.8.26 batch file
and every time i get the same option.... cant flash to recovery or boot only kernel
i have attached a screenshot so that nobody thinks i am going mad
can you please help me thanks :fingers-crossed:
It's been a while since I used TWRP 2.8.XX...so no idea what's the issue there but I'd just flash TWRP recovery via fastboot. Worked for me without any problems :good:
T4ke5 said:
It's been a while since I used TWRP 2.8.XX...so no idea what's the issue there but I'd just flash TWRP recovery via fastboot. Worked for me without any problems :good:
Click to expand...
Click to collapse
Hi ... Is that using the ADB fastboot recovery TWRP.img?
I am on KitKat just wondering if that's why it won't work have you got to be on 6.01 ?
Well, actually it shouldn't matter on which Android version you are, but to have the latest boot.img and radio.img installed I'd flash the latest stock ROM available here on XDA which means by the way having TWRP 3.0.2.0 as well and after that you might be ready for AOSP 7.1
Just have look at kulvertti's thread in the "General" subforum. Since you have already intalled a custom recovery there shouldn't be any problems.
Lockeddual recovery is not compatible with any custom rom
Please follow the instructions in the thread
rcstar6696 said:
Lockeddual recovery is not compatible with any custom rom
Please follow the instructions in the thread
Click to expand...
Click to collapse
Hi @rcstar696 have you got a link to the instructions please as I can't seem to find it ... thanks
nickbaker66 said:
Hi @rcstar696 have you got a link to the instructions please as I can't seem to find it ... thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpe.../aosp-6-0-marshmallow-sony-xperia-z2-t3235935
first two steps of instruction
rcstar6696 said:
http://forum.xda-developers.com/xpe.../aosp-6-0-marshmallow-sony-xperia-z2-t3235935
first two steps of instruction
Click to expand...
Click to collapse
Hi @rcstar6696,
i had no problem flashing the boot.img that part was ok but when i went to flash the recovery it never seemed to work for me, in the terminal window in the SDK programme tools folder which is the same folder as the image i downloaded from your thread is in (Twrp-3.0.0-0-castor-windy.img and twrp_castor_windy.img) it said something about sizes but said it went ok tried to boot into recovery and it never worked
in the terminal window whilst my SGP511 was in fastboot mode i typed fastboot recovery Twrp-3.0.0-0-castor-windy.img is this is correct script or have i got this wrong ?
i am currently on Kitkat does this matter
thansk
nickbaker66 said:
in the terminal window whilst my SGP511 was in fastboot mode i typed fastboot recovery Twrp-3.0.0-0-castor-windy.img is this is correct script or have i got this wrong ?
thansk
Click to expand...
Click to collapse
The right command is
fastboot flash recovery PathToRecovery*
Click to expand...
Click to collapse
*C:\stuff\more_stuff\TWRP_castor-windy.img for instance
T4ke5 said:
The right command is
*C:\stuff\more_stuff\TWRP_castor-windy.img for instance
Click to expand...
Click to collapse
Cheers guys I'll give that a go
T4ke5 said:
The right command is
*C:\stuff\more_stuff\TWRP_castor-windy.img for instance
Click to expand...
Click to collapse
rcstar6696 said:
http://forum.xda-developers.com/xpe.../aosp-6-0-marshmallow-sony-xperia-z2-t3235935
first two steps of instruction
Click to expand...
Click to collapse
hi guys i tried what you said and still could get it to work, please see screenshot and check if i have entered something wrong, i dont thinki have but i might be wrong
is it because i have not done the boot image first via fastboot ?
Looks quite good. Did you already try to enter the recovery?
T4ke5 said:
Looks quite good. Did you already try to enter the recovery?
Click to expand...
Click to collapse
i tried to access recovery via the down volume button when the tablet starts up but no green light appears and it just starts normally ...... i ve not flashed the boot.img first then flashed recovery as ive seen it can be done via recovery the only option left now is to try flashing the boot.img first .... i have no option but to try that tonight and see if that can do it that way
@T4ke5 @rcstar6696 thanks very much guys for your help TWRP on 3.0.0 now and AOSP 7.1 installed now
Sweet! :good:
T4ke5 said:
Sweet! :good:
Click to expand...
Click to collapse
Don't laugh but I can't put my WiFi code in because there's no keyboard just tap to speak how can I have the keyboard back lol
T4ke5 said:
The right command is
*C:\stuff\more_stuff\TWRP_castor-windy.img for instance
Click to expand...
Click to collapse
Cheers mate worked a treat
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Edit: I can flash system, I did flash kernel, I can flash recovery too, but when I try to flash anything else, it gives me that error
Edit2: can someone tell me which files do I need to extract via huawei update extractor to flash? I know that system.img is one of them
konopla4 said:
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Click to expand...
Click to collapse
Check if you're still FRP unlock in Fastboot.
ante0 said:
Check if you're still FRP unlock in Fastboot.
Click to expand...
Click to collapse
Both bootloader and from are unlocked
konopla4 said:
Both bootloader and from are unlocked
Click to expand...
Click to collapse
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
You could use HWOTA for Mate 10 Lite if you can get into stock recovery, as it will flash the full update.app rather than the limited partitions fastboot can flash.
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
Click to expand...
Click to collapse
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
konopla4 said:
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
Click to expand...
Click to collapse
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
Click to expand...
Click to collapse
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
konopla4 said:
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
Click to expand...
Click to collapse
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
ante0 said:
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
Click to expand...
Click to collapse
Waaaait it, I can update from TWRP?
Or is it a specialized one?
konopla4 said:
Waaaait it, I can update from TWRP?
Or is it a specialized one?
Click to expand...
Click to collapse
It's a script, but it needs a TWRP that's compatible. The one by Catuva21 is (or so I've heard).
I flashed Hongkong firmware which is Android 13 just now and I patched boot.img with magisk and I flashed it, boot to system successfully, but after a while it turned off and rebooted to recovery, said that system may not in stock and may need to erase user data. I reboot it but same. So how to root in Android 13?
I patched my boot.img and after reboot to fastboot flashed patched img and reboot
raven213 said:
I patched my boot.img and after reboot to fastboot flashed patched img and reboot
Click to expand...
Click to collapse
This is what I've done however there is another thread which states to flash vbmeta also, is this required?
Also if possible could you give me information about how to setup newsflasher? As last I've used this it was on an Xperia x10i lmao now I see there's no .exe to it
Mijan94 said:
This is what I've done however there is another thread which states to flash vbmeta also, is this required?
Also if possible could you give me information about how to setup newsflasher? As last I've used this it was on an Xperia x10i lmao now I see there's no .exe to it
Click to expand...
Click to collapse
I didn't flashed vbmeta and for newsflasher just download the firmware and after copy all the files from newsflasher to the firmware folder.
raven213 said:
I patched my boot.img and after reboot to fastboot flashed patched img and reboot
Click to expand...
Click to collapse
I do the same when it's Android 12 and works well but today I flashed new firmware of Android 13, it failed.
wednesyao said:
I do the same when it's Android 12 and works well but today I flashed new firmware of Android 13, it failed.
Click to expand...
Click to collapse
What error do you get? I did a fresh installation of A13 maybe that's why?
raven213 said:
What error do you get? I did a fresh installation of A13 maybe that's why?
Click to expand...
Click to collapse
Emm sort of. It's because of my thermal remove module of scene5, once I disable it my phone's back.