Related
HTCDreamOn said:
A word of advice: I strongly recommend temporarily booting any images (be it recoveries or kernels) you are about to flash to your device. This is simply a case of using the command "fastboot boot blahblah.img" whether blahblah.img is a recovery or kernel.
Click to expand...
Click to collapse
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
purplepizza said:
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
Click to expand...
Click to collapse
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
HTCDreamOn said:
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
Click to expand...
Click to collapse
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
acejavelin said:
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
Click to expand...
Click to collapse
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
purplepizza said:
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
Click to expand...
Click to collapse
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
purplepizza said:
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
Click to expand...
Click to collapse
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
acejavelin said:
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
Click to expand...
Click to collapse
Just curious, how did you go from 5.1.1 to 6.0?
purplepizza said:
Just curious, how did you go from 5.1.1 to 6.0?
Click to expand...
Click to collapse
OTA... part of soak test on December 22.
acejavelin said:
OTA... part of soak test on December 22.
Click to expand...
Click to collapse
Hey thanks for helping to answer this, your explanation was much better I thought it had something to do with loading into RAM but wasn't sure. I didn't know some devices don't allow fastboot boot commands though, I've always relied on them. Part of the reason I'm avoiding htc now.
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
To answer your nandroid question: It basically just takes an image of the partitions you choose, usually /system, /data, and /boot (where kernel stuff is) which is the least you need to boot back with all your data. It doesn't backup recovery and when you restore it doesn't write anything to recovery, so yes twrp will still be in place. In general you should only ever flash stuff to the recovery partition whilst in fastboot mode (i.e. using fastboot flash recovery recovery.img), I know on some devices you can flash recoveries as zip files in the recovery itself but you shouldn't.
I've seen quite a few people querying about the 6.0 OTA: in short, I wouldn't worry about it because once they start rolling out, people always catch the OTA and post here on xda. You can flash that and it'll return you to stock 6.0 anyway, at which point you can reroot and everything if you want.
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
purplepizza said:
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
Click to expand...
Click to collapse
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
acejavelin said:
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
purplepizza said:
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
Click to expand...
Click to collapse
It is not the bootloader... It is the /boot partition of the phone, basically the kernel and RAM disk. If you screw things up and need to restore, you typically want to restore /boot, /system, and /data, and occasionally /cache (if you want to restore to save time and get an exact duplicate of the previous image, otherwise many people skip /cache and let it rebuild on the first boot which takes 10-15 minutes extra).
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
HTCDreamOn said:
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
Click to expand...
Click to collapse
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
purplepizza said:
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
Click to expand...
Click to collapse
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
acejavelin said:
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
Click to expand...
Click to collapse
Any recommendations how to proceed?
I also need help with my soft bricked moto g3
Moto g3 (xt 1550, Indian dual sim 16 gb version)
I officially upgraded to 6.0.0 via ota and my objective was to root my phone and use xposed modules. I am not interested in any other custom rom (I'd rather keep stock rom just for moto display and ota upgrades) or custom recovery like twrp(I'm afraid it may cause ota upgrades to fail).
I used the method described here in the question- http://android.stackexchange.com/qu...rsu-using-play-store-versus-a-custom-recovery
So I first successfully unlocked my bootloader using the official motorola method.
I then proceeded to use google's backup settings to re-install all the apps that were uninstalled due to unlocking the bootloader. I also put supersu.zip version 2.46 on internal sd card.
I then proceeded to (without rebooting) enter fastboot where i used minimal adb to temporarily boot into twrp version2.8.7 r5 (link - http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 ).
Once in twrp, I located and flashed the supersu.zip. It flashed successfully. I procceded to clear dalvik cache and then after clearing cache I tried to reboot my phone using twrp.
However, it did not go beyond the "Warning - Bootloader Unlocked" screen that you get on unlocking a motorola bootloader. I left it for over 10 minutes (usb was still plugged in, I had >80% battery) but it did not proceed.
Long -pressing the power button causes the phone to vibrate and again attempt to boot, stuck at the same initial screen. Adb quite understandably does not work here.
I can press vol down+power and enter fastboot , where adb works fine.
I can enter stock recovery from the fastboot sceen too.
Using adb in fastboot, I am able to boot twrp . In fact, I tried to re-install supersu.zip. I retried version 2.46 and then tried version 2.56. On all occcassions, it was able to successfully flash it, but gets hung on the initial boot screen.
USB Debugging is also enabled, and I have a backp of my sd card data.
I tried taking a backup of the system and apps in twrp (3 gb in total) and tried to reflash it, but it still hangs at the same screen.
Is there any way I can unbrick my device and- (in decreasing order of preference)
1. Keep my stock rom and recovery?
2. Keep stock rom with twrp? (It should not be a problem)
3. Custom rom with custom recovery - perhaps official cm. Least preferred as I want Moto Display and stock/vanilla android.
Also, is SELinux involved anywhere with my phone getting bricked? I also read that a custom kernel is required for rooting 6.0, which I don't have. Supersu Version 2.56 is said to prevent soft bricks if the kernel is incorrect (systemless root), yet even after flashing the newer one it is still bricked. Where am I going wrong? What should I do? Thanks in advance! :good:
purplepizza said:
Any recommendations how to proceed?
Click to expand...
Click to collapse
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
acejavelin said:
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
Click to expand...
Click to collapse
I have not rooted yet. I guess I can try by booting TWRP then flashing SuperSU.
Can you think of any reasons not to try fastboot again the re-flash TWRP?
Under AICP14 i had significant problems with Bluetooth, so I'm back to the latest pie version via erecovery ... all right. Then in preparation for root in TWRP noticed that data is again encrypted. So reset to factory settings via twrp, rebooted into the TWRP3.2.3-3 and formatted data with yes. Thereafter, on the screen was "formatting done," but down the blue animation was still running around, about 10 minutes, apparently hung. Since I could not do anything else, power button long pressed and booted again into the TWRP, but the hangs at the entrance screen, probably clear in the unsuccessful attempt to decrypt data. The Erecovery with the ability to restore the system and the stock recovery is not reachable for me, with everything I've tried. Fastboot is still to reach ... When booting the device will always hang at the inscription "The device is booted" ...has someone an idea? ? Thanks for thinking!
How to restore erecovery? It was pie, latest version installed from erecovery on the device before this crash...
Flash the erecovery partition. Extract the IMG from the update.zip file and flash the same.
shashank1320 said:
Flash the erecovery partition. Extract the IMG from the update.zip file and flash the same.
Click to expand...
Click to collapse
Got an error trying to extract:
borisku said:
Got an error trying to extract:
Click to expand...
Click to collapse
Go to settings and disable checksum or some verification. Dont remember the exact one but its there in setting
shashank1320 said:
Go to settings and disable checksum or some verification. Dont remember the exact one but its there in setting
Click to expand...
Click to collapse
I Managed to extract ERECOVERY_RAMDI.img and ERECOVERY_RAMDI.img header... i also extracted SYSTEM.img/header and RECOVERY_RAMDIS.img/header frum the update.app
Is it correcht to follow this syntax:
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img
to reflash the erecovery? btw. i dont know the exact version of the firmware i installed, it was yesterday i think it had been BKL-L09 (9.0.0.233) C432E4R1P12 , but i cant find that as an update.zip. So i took BKL-L09C432E4R1P8B108-log (9.0.0.108) and extracted the files from there...
borisku said:
I Managed to extract ERECOVERY_RAMDI.img and ERECOVERY_RAMDI.img header... i also extracted SYSTEM.img/header and RECOVERY_RAMDIS.img/header frum the update.app
Is it correcht to follow this syntax:
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img
to reflash the erecovery? btw. i dont know the exact version of the firmware i installed, it was yesterday i think it had been BKL-L09 (9.0.0.233) C432E4R1P12 , but i cant find that as an update.zip. So i took BKL-L09C432E4R1P8B108-log (9.0.0.108) and extracted the files from there...
Click to expand...
Click to collapse
As long as it is pie erecovery, it should work fine. Yes, flash that file.
shashank1320 said:
As long as it is pie erecovery, it should work fine. Yes, flash that file.
Click to expand...
Click to collapse
No success:
sending erecovery_ramdisk (32768KB)
okay [0.707s]
writing 'erecovery_ramdisk
FAILED (remote: command not allowed)
or should i flash to recovery_ramdisk not to Erecovery_ramdisk?
borisku said:
No success:
sending erecovery_ramdisk (32768KB)
okay [0.707s]
writing 'erecovery_ramdisk
FAILED (remote: command not allowed)
Click to expand...
Click to collapse
Is your bootloader still unlocked? There was a guide i posted in v10 section for going back to stock if that's what you are interested.
shashank1320 said:
Is your bootloader still unlocked? There was a guide i posted in v10 section for going back to stock if that's what you are interested.
Click to expand...
Click to collapse
Phone unlocked
FRP unlock
i try to come back to erecovery to install latest Emui 9, and from that point i want to return to AICP14...
@edit: I got it following this post:
https://forum.xda-developers.com/showpost.php?p=78752217&postcount=22
i reached erecovery and i´m installing 9.0.0233 via wifi.... hope it wil run til its completed
The most ****ty problem comes if you want to remove the idiotic encryption via formatting data partition in twrp with the red "yes" ...
Thanks to shashank1320!
After updating TWRP using TWRP it self i can't boot into custom recovery again the phone just stays loading forever, the phone is also wiped so no custom image or stock image and i cant use it since even in fastboot it just keeps saying "FAILED (remote: Command not allowed)".
The phone on FASTBOOT mode says:
Phone unlocked
but says FRP lock
maybe that is the problem? if so how can i solve it? i really want to make my honor 8 work again so thanks for your help!
Ps. Sorry for my bad English
RicardoVs said:
After updating TWRP using TWRP it self i can't boot into custom recovery again the phone just stays loading forever, the phone is also wiped so no custom image or stock image and i cant use it since even in fastboot it just keeps saying "FAILED (remote: Command not allowed)".
The phone on FASTBOOT mode says:
Phone unlocked
but says FRP lock
maybe that is the problem? if so how can i solve it? i really want to make my honor 8 work again so thanks for your help!
Ps. Sorry for my bad English
Click to expand...
Click to collapse
What android version are you on? Have you tried flashing stock recovery? Which twrp are you using? Are sure that you did not flash twrp on the wrong partition?
PremiumBlaze said:
What android version are you on? Have you tried flashing stock recovery? Which twrp are you using? Are sure that you did not flash twrp on the wrong partition?
Click to expand...
Click to collapse
I was using Paranoid android 7.1 i believe but i wiped the phone so there is no Android at all at the moment, i tried updating to the latest twrp since i was getting error 7 trying to flash the stock room, stock recovery just says "failed to get information from the server" every time and for last i did flash it in the right partition, every comand i execute in fastboot it gives me that error and it's also important to mention that i can't find my phone in "adb devices" only in "fastboot devices". I saw some people using the Dload get the stock system back maybe thats an option? i dont know i feel completely lost.
Thanks for the reply
RicardoVs said:
I was using Paranoid android 7.1 i believe but i wiped the phone so there is no Android at all at the moment, i tried updating to the latest twrp since i was getting error 7 trying to flash the stock room, stock recovery just says "failed to get information from the server" every time and for last i did flash it in the right partition, every comand i execute in fastboot it gives me that error and it's also important to mention that i can't find my phone in "adb devices" only in "fastboot devices". I saw some people using the Dload get the stock system back maybe thats an option? i dont know i feel completely lost.
Thanks for the reply
Click to expand...
Click to collapse
Are you able to boot inside TWRP at this moment? And also what is this "latest twrp" that you said that your were flashing. I believe if the TWRP stays loading forever, it means that it does not work for the device.
Make sure your trying to flash this TWRP for nougat:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563/amp/
PremiumBlaze said:
Are you able to boot inside TWRP at this moment? And also what is this "latest twrp" that you said that your were flashing. I believe if the TWRP stays loading forever, it means that it does not work for the device.
Make sure your trying to flash this TWRP for nougat:
https://forum.xda-developers.com/honor-8/development/twrp-t3566563/amp/
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-1-frd.img
target reported max download size of 471859200 bytes
sending 'recovery' (25188 KB)...
OKAY [ 0.538s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s
RicardoVs said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-1-frd.img
target reported max download size of 471859200 bytes
sending 'recovery' (25188 KB)...
OKAY [ 0.538s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s
Click to expand...
Click to collapse
Have you tried dload yet?
PremiumBlaze said:
Have you tried dload yet?
Click to expand...
Click to collapse
No, what do I need to do? What files should I put in the Dload folder? I never used that method and didn't manage to find information online
RicardoVs said:
No, what do I need to do? What files should I put in the Dload folder? I never used that method and didn't manage to find information online
Click to expand...
Click to collapse
1. Download the update.zip of the stock rom
2. Extract the update.zip of the stock rom
3. Make a folder named "dload" on your sdcard
4. Place the UPDATE.APP on the dload folder
5. Press volume up + volume down + power button until Huawei logo appears
PremiumBlaze said:
1. Download the update.zip of the stock rom
2. Extract the update.zip of the stock rom
3. Make a folder named "dload" on your sdcard
4. Place the UPDATE.APP on the dload folder
5. Press volume up + volume down + power button until Huawei logo appears
Click to expand...
Click to collapse
Ok, i already had the files so i did everything and it didnt work "Software install failed!"
RicardoVs said:
Ok, i already had the files so i did everything and it didnt work "Software install failed!"
Click to expand...
Click to collapse
In the old nougat days, Ive had the same problem. As I always say, dont use twrp on honor 8. They all suck! Anyways, did you tried eRecovery?
Or you should be able to dload a proper firmware in all cases. You just need to find the right package. It fixed me the same problem in the past.
Braiteyy said:
In the old nougat days, Ive had the same problem. As I always say, dont use twrp on honor 8. They all suck! Anyways, did you tried eRecovery?
Or you should be able to dload a proper firmware in all cases. You just need to find the right package. It fixed me the same problem in the past.
Click to expand...
Click to collapse
I got the update.zip for my specific FRD device but still... it failed... im starting to think there is no way so fix this
RicardoVs said:
I got the update.zip for my specific FRD device but still... it failed... im starting to think there is no way so fix this
Click to expand...
Click to collapse
Dont loose hope man! There is a way to fix it every time. Just try another full ota package with same vendor as you are running rn.
Braiteyy said:
Dont loose hope man! There is a way to fix it every time. Just try another full ota package with same vendor as you are running rn.
Click to expand...
Click to collapse
I tried every single file for my FRD-L09C432B405 on Team mt and nothing :/
Do i need to delete everything on the sd card and leave only de dload folder? Maybe i need to format it in an specific format?
No, you dont need to format your sd card. I am gonna help you tomorrow. I am going to sleep rn. See you! need to format it in an specific format?[/QUOTE]
RicardoVs said:
I tried every single file for my FRD-L09C432B405 on Team mt and nothing :/
Do i need to delete everything on the sd card and leave only de dload folder? Maybe i need to format it in an specific format?
Click to expand...
Click to collapse
I realised you said that you updated your TWRP and you cant get in. Did you tried different buttons? I remember some of twrps had volume up + power button and some had volume down and power button and some had vol up and down and power button. Try everything. The frp lock is probably because it somehow disabled oem unlocking by itself. I am gonna try to find a link for latest nougat for you. Good luck man!
EDIT: You should try to relock yor bootloader and unlock it again.
Here are the links: http://update.dbankcdn.com/TDS/data/files/p3/s15/G1774/g1755/v208402/f1/full/update.zip
http://update.dbankcdn.com/TDS/data...l/FRD-L09_hw_eu/update_full_FRD-L09_hw_eu.zip
http://update.dbankcdn.com/TDS/data...02/f1/full/public/update_data_full_public.zip
RicardoVs said:
I tried every single file for my FRD-L09C432B405 on Team mt and nothing :/
Do i need to delete everything on the sd card and leave only de dload folder? Maybe i need to format it in an specific format?
Click to expand...
Click to collapse
Could you try to follow this guide to see if it works:
https://www.stechguide.com/downgrade-honor-8-from-nougat-to-marshmallow/
It may lead your to marshmallow but hopefully it makes the device works. You are going to need the B131 update.zip and flashing rollback package (the site has rollback package download) using dload first before flashing the B131's update.app using dload.
So basically:
1. Flash the rollback package's update.app using dload
2. Flash update.app from B131's update.zip using dload
Once your in marshmallow, you can go back to nougat because there should be at least a twrp for honor 8 marshmallow somewhere around xda
PremiumBlaze said:
Could you try to follow this guide to see if it works:
https://www.stechguide.com/downgrade-honor-8-from-nougat-to-marshmallow/
It may lead your to marshmallow but hopefully it makes the device works. You are going to need the B131 update.zip and flashing rollback package (the site has rollback package download) using dload first before flashing the B131's update.app using dload.
I am really sure that this would work because I tried it before and I was able to go to Marshmallow without any software install fails using dload.
So basically:
1. Flash the rollback package's update.app using dload
2. Flash update.app from B131's update.zip using dload
Once your in marshmallow, you can go back to nougat because there should be at least a twrp for honor 8 marshmallow somewhere around xda
Click to expand...
Click to collapse
The rollback package worked but not the B131, i tried to flash the update.app for my android the B405 as well but nothing...
RicardoVs said:
The rollback package worked but not the B131, i tried to flash the update.app for my android the B405 as well but nothing...
Click to expand...
Click to collapse
I thought this is gonna happen. It happened to me too. I just dont ****in remmember how did I make dload work.
delete
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
hey i can help ! which version of twrp are you trying to flash ?
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Venkata Lochan Nune said:
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Click to expand...
Click to collapse
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
My bad , I thought the update website to be huawei's official one(something like update.hicloud and all isn't it?). Well, thanks for the information but I still prefer gsi. It's buttery smooth .
And one more thing, if you follow the youtube video I mentioned, you don't need any gsi. You can get your device back on stock EMUI 5.
King_of_Android said:
hey i can help ! which version of twrp are you trying to flash ?
Click to expand...
Click to collapse
Hey I have a doubt... Will the recoveries we find in twrp official website / app work on EMUI 8? I wanted to try them but I'm afraid I might brick my device again. Getting it back is a hectic thing and I already had to face it thrice. LOL .
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
lmaohelp said:
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
Click to expand...
Click to collapse
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Venkata Lochan Nune said:
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Click to expand...
Click to collapse
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
lmaohelp said:
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
Click to expand...
Click to collapse
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Venkata Lochan Nune said:
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Click to expand...
Click to collapse
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
lmaohelp said:
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
Click to expand...
Click to collapse
I'm attaching one that works with emui 8 try using it (Remember you have to flash it to recovery_ramdisk).
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
speedson said:
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
Click to expand...
Click to collapse
His problem us with twrp.
He can only access fastboot but isn't able to flash twrp...
Venkata Lochan Nune said:
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
Click to expand...
Click to collapse
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
lmaohelp said:
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
Click to expand...
Click to collapse
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Venkata Lochan Nune said:
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Yup, I tried that as well, and it told me "invalid command"
lmaohelp said:
Yup, I tried that as well, and it told me "invalid command"
Click to expand...
Click to collapse
Well as you said, you partitions must have been really messed up. I have no other ideas except the test point method.
Are you trying anything else?
Ok we have some option that could help you...
Im read in the 4PDA (the russian XDA xD) forum that it should be possible to flash the oeminfo by fastboot command. So just download the HWOTA_BLN_Eng and expand it. Then go to 7 or 8 Folder and there you go to oeminfo folder. There you choose the right one for your Device and local area...for example BLN-L21 (Device) C432 (European Area)
Extract the file to your desktop and rename it to BLN-L21C432.img
--->be sure that you have the right Device driver installed and the right ADB driver for your device to<---
ok now Copy and Paste the BLN-L21C432.img to ADB folder and start command with admin rights
start the phone into fastboot mode
--->bootloader must be unlocked<---
in the command
fastboot flash oeminfo BLN-L21C432.img
wait for the result and it can not hurt to pray a bit in this moment...hihi
if this have success...you type in command
fastboot reboot
wait to the screen you can press 3 seconds Vol+ to go into erecovery....connect to wlan and it should work step by step like it should.
after download and recover the stock rom reboot and go again to erecover by press Vol+ for 3 seconds and now go to the second option...wipe data/factory reset and write yes+enter
in stock recovery wipe Data after that wipe Cache...reboot and wait that system boot the initial boot for first setup.
If this will not working...tell me what honor 6x you have and wich local area you are from and wich firmware you stock had before you doing wronng
good luck bro
solong
speedson
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
ajg32 said:
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
Click to expand...
Click to collapse
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
dcarvil said:
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
Click to expand...
Click to collapse
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
ajg32 said:
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
Click to expand...
Click to collapse
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
dcarvil said:
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
Click to expand...
Click to collapse
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
ajg32 said:
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
Click to expand...
Click to collapse
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
dcarvil said:
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
Click to expand...
Click to collapse
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
ajg32 said:
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
Click to expand...
Click to collapse
"boot_a image size: 100663296" is the wrong size. How are you transferring boot.img and the patched image between your phone and PC? You should be using adb push/pull. If you did use adb push/pull, I'd need to see all the commands you used, and a directory listing of all the files to see if I can spot something wrong. Also, what version of Magisk?
You could try renaming magisk.apk to magisk.zip and installing the zip with TWRP, but I don't know if that method still works on the Pixel 3. I've never tried that method. Make sure you just boot TWRP (fastboot boot twrp.img), and do not install TWRP. If that breaks things, at least you know how to recover now.