Related
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
I tried everything in this thread:
http://forum.xda-developers.com/p8lite/general/hand-fixing-bootloop-t3464740
to no avail. One thing I noticed is that the link given in the Fastboot menu links to a Chinese (?) website - http://zh.ui.vmall.com/emotiondownload.php?mod=restore - I'm not sure if this is indicative of me having a device for the East Asian markets and if there are any software differences?
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
GfIsGonnaKillMe said:
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
Click to expand...
Click to collapse
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
XePeleato said:
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
Click to expand...
Click to collapse
Just the very static image, it doesn't even go into the animation.
Edit: this is a newly bought P8 Lite, the Box says Android 5.0, don't know if relevant?
by now I've wiped stuff with TWRP more times than I can count, and tried manually flashing the boot, recovery, cust and system of b132, b170, b190, and b564 to no avail
GfIsGonnaKillMe said:
Just the very static image, it doesn't even go into the animation.
Click to expand...
Click to collapse
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
XePeleato said:
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
Click to expand...
Click to collapse
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
GfIsGonnaKillMe said:
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
Click to expand...
Click to collapse
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
XePeleato said:
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
Click to expand...
Click to collapse
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
GfIsGonnaKillMe said:
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
Click to expand...
Click to collapse
[ 8.389146s][pid:1,cpu1,init]BUG: failure at /cloud/jenkinswh/ci/workspace/Alice_Channel_ANDROID/android_code/kernel/drivers/video/hisi/hi6220/balong_compose.c:613/vpu_on_notice_ade()!
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
XePeleato said:
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
Click to expand...
Click to collapse
It is very nice of you to look into this! Worst case scenario, the device was broken from the start and has now lost its warranty (though I booted it up once without problems right in the beginning).
For the main problem - which is my gf - I simply factory reset my own P8 Lite and put the stickers from the new one on it. Now I don't have a phone, but at least I get to keep my relationship
ninja edit: checking my terminal history, I remember trying to fix the not-installing SuperSU by trying fastboot -w and fastboot format cache as recommended elsewhere, but both failed
Playing around with it again, it seems the only fastboot commands working are fastboot flash and fastboot reboot, everything else is giving a "FAILED (remote: Command not allowed)" error, even for things like getvar
flashing b564 allows me to get into stock recovery, will try dload update now!!
EDIT: IT WORKS!!!
Things I learned from this:
- it is important to flash right update version
- use dload if you can boot into stock recovery
- recovery will only be loaded if not connected via USB, otherwise EMUI crap will launch
- vendors do not always have correct information on device package!!
GfIsGonnaKillMe said:
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
Click to expand...
Click to collapse
delete
For unbrick, its easy if your bootloader is unlocked.
Just need time and flash few files by adb (downgrade)and update your device's to the android version you want.
If you want I have all the necessary files.
After your device's is like at his first boot.
Sent from my SM-N9005 powered by QS-N9005-LP
I have successfully unlocked the bootloader and managed to install TWRP 3.1.0-3 but that's about it. I cannot install any other TWRP version but the one I mentioned. I tried installing Magic Rainbow custom ROM but it doesn't work properly (apps are super slow, entering developer settings makes the settings app crash, can't set a password etc.). So with that I can at least access the phone interface with limited options. Developer settings crashes when I choose it; if I can get through then I can't enable USB debugging, it keeps turning itself off right as I enable it. I can't use update function so I have to use 3 button installation, which randomly fails to work very often. Due to this I haven't been able to install any updates.
I kinda gave up on rooting already, I just want to get my old firmware back at this point but I can't even do that. SRKTools stock marshmallow recovery doesn't work either. It's as if TWRP 3.1.0 has taken over everything. On the rare occasions that I managed to get EMUI update via 3 button installation it would say that the update doesn't match the current version (or something like that). I tried using recover for b378 and managed to run the 3 button update but it always gets stuck at 5%. It gives up after a while, tries booting twice and then goes into eRecovery screen. My bootloader PHONE unlocked text is in red if it matters.
I've been actively trying to fix this for the last 11 hours (yes I'm not exaggerating at all). Please, PLEASE someone help me out with this!
I've also tried using the unbrick tool of the latest SRK Tool 2.0 for b378. It goes flawless, phone restarts and does a factory wipe but then doesn't boot after the Huawei screen. It tries booting twice and then it goes into eRecovery screen. Have I ruined some hardware here?
It seems like 3 button upgrade is my salvation and it doesn't work. Many times I hold it down, I get a slightly different screen but it again hangs at booting text. I managed to flash all recovery, boot and system image files and got the installing update screen in my b378 update, but it hangs at 5%. I couldn't even manage to get the installing update screen for common b136. Also when I try to flash system.img I get an error with flashing system which is FAILED (remote:sparse flash write failure).
First at all: The Magic Rainbow custom ROM is based on B383 so it wont work on B378 firmware thats your fault here.
Just flash the rollback package (find it in my signature) and after this flash B383 or if it not work start with B136. U have to do all with the dload method.
Fast solution?
https://forum.xda-developers.com/p9/development/p9-moonlight-rom-v1-0-b378-stock-t3567223
flash the B378 version. probably your problem is solved by this.
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Lauran_N said:
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Click to expand...
Click to collapse
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
xtcislove said:
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
Click to expand...
Click to collapse
I cannot flash rollback using 3 buttons method. I see the "your device is booting now" text and then it goes to TWRP menu. Nothing happens. This is what I mean with 3 button method not working. Every single update fails probably because of this. Is there anything else I can do to flash it?
I've also tried flashing b378 and then doing the rollback. Still doesn't work: It hangs at 5% as it did with the b378 update.
Also, is there a special way of flashing those 2 files of b383? Is it just one after another? I doubt I can flash them at the same time since they have the same name.
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Glad it worked for you.
Next time just read the threads in this forum.
There are several toturials how to flash the p9 the right way.
Lauran_N said:
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Click to expand...
Click to collapse
Can you explain in detail how your fact? That would be nice
Genysix said:
Can you explain in detail how your fact? That would be nice
Click to expand...
Click to collapse
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
xtcislove said:
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
Click to expand...
Click to collapse
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Genysix said:
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Click to expand...
Click to collapse
Ok first of all, using TWRP back up everything you have there (backing up SD card isn't really needed unless you plan to wipe it too). Then, using TWRP again just wipe everything but OEM and SD card (external storage). Then, create a folder called "dload" in the main SD card directory and put ONLY the update.app in it (use the stock b136 as suggested). Now you need to flash a stock recovery using bootloader again. Just use the Huawei Update Extractor and get both recovery.img and boot.img from the rom that you're using to flash (in this case b136). Put them in the same folder as adb. Run adb cmd, write commands "fastboot flash recovery recovery.img" and then "fastboot flash boot boot.img" and finally "fastboot reboot". Quickly unplug your usb cable and use the 3 button force update (Vol Up+Vol Down+Power button all held together and don't let go until you see the update start). It should work without a problem if you had managed to wipe everything using TWRP. If it still doesn't work you could try deleting OEM info as well and flashing a new one (c432) which you can find on the forums. Back up is important in case it still doesn't work, you might need them to undo things.
If it boots, it means you've learned how to do it and you can probably unbrick it as much as you want haha. You can update to Nougat (7.0) and EMUI 5 using Huawei Updater 2.0 along with HiSuite, there is a guide here on the forums to do so by updating to b182 then to b360/b361>b378>b383 which I was unable to find for now. After that you can install a custom rom without an issue. I figured I wouldn't mess with it anymore but frankly it's likely that you are just soft bricking by skipping something very simple and failing because of that unless you went ahead and did things that you are explicitly told not to do so. If you end up having it unlocked/relocked might as well try and get a custom rom really.
If the update gets stuck at 5% or you have the icon of a usb cable end with a lightning on it your mistake is that you didn't unplug it. If the update keeps failing without these it's likely that you're using the wrong firmware and you could try using another one (FULL+PV+MV ones if you're going for a higher one). Or you could try to follow the rollback and then the update as I did. if you do the rollback then the update, your phone might get a LOCKED status again (yes not relocked).
If you are missing something or you think you have a stupid question and too shy to ask it here just PM me.
Phil_UK said:
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Click to expand...
Click to collapse
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Lauran_N said:
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Click to expand...
Click to collapse
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Phil_UK said:
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Click to expand...
Click to collapse
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Lauran_N said:
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Click to expand...
Click to collapse
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Phil_UK said:
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Click to expand...
Click to collapse
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Lauran_N said:
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Click to expand...
Click to collapse
Many Thanks
I managed to flash B360_update.zip via recovery instead. I also have a B360_update_data_full_hw_eu.zip but not sure what that is for.
So, I ****ed up.
Earlier this night i hard bricked my device while trying to uninstall Magisk. Used a guide that worked and was back on stock OOS 3.5.0.
In the old Oxygen OS I installed TWRP. But the thing with the recovery was that you needed to boot recovery from the command line with the command
Code:
fastboot boot twrp.img
. If I booted into recovery in any other way the screen is just black and never boots.
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
I relocked it, and when it was done I got the prompt to fill in the password to start Android. But the thing was I did not use any security options, no fingerprint or pin code. So zero luck there. And now I can't boot into recovery because I didn't flash the stock recovery because I'm a retard, so when I'm trying to boot recovery it's just black. So I have no chance to come back. Please help...
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
thes3usa said:
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
Click to expand...
Click to collapse
Thank you for your reply, I tried to do the method with the MSMDownload thing yesterday, but the computer did not recognize the device. It was late in the night (5am) so I went to bed. This morning I took my other computer and plugged my phone in, it recognized it and I was able to fully recover the phone!
avveawesome said:
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
Click to expand...
Click to collapse
This isn't good idea. As already noted, never relock the bootloader on this device with TWRP, root, etc. It should only be relocked after returning to full stock condition.
Also, never install an incremental OTA when you have TWRP (root, etc.), only the full update zips should be used in that case.
Try to stick to these forums for advice. Maybe the guidance your found above is not specific to this device?
Hello guys, I have a big problem.
I was restoring a TWRP backup, something went wrong and now I have a soft locked phone.
When powered up, it shows the Huawei logo and goes straight into eRecovery Mode, where I have 3 options: downdload latest version and continue (it obviously fails), reboot and shutdown.
Vol + and power don't trigger TWRP (I'm fairly sure it was overwritten by the stock recovery)
Pressing Vol - and connecting USB I can enter fastboot & recovery mode (PHONE Unlocked, FRP Unlock), but every fastboot command gives me "FAILED (remote: Command not allowed)" during writing.
What can I do? I can't flash a recovery, I can't flash a zip.
When plugged in the PC in eRecovery I can hear a Windows 10 notification sound and HiSuite activates, but it doesn't recognize the phone.
Joseki100 said:
Hello guys, I have a big problem.
I was restoring a TWRP backup, something went wrong and now I have a soft locked phone.
When powered up, it shows the Huawei logo and goes straight into eRecovery Mode, where I have 3 options: downdload latest version and continue (it obviously fails), reboot and shutdown.
Vol + and power don't trigger TWRP (I'm fairly sure it was overwritten by the stock recovery)
Pressing Vol - and connecting USB I can enter fastboot & recovery mode (PHONE Unlocked, FRP Unlock), but every fastboot command gives me "FAILED (remote: Command not allowed)" during writing.
What can I do? I can't flash a recovery, I can't flash a zip.
When plugged in the PC in eRecovery I can hear a Windows 10 notification sound and HiSuite activates, but it doesn't recognize the phone.
Click to expand...
Click to collapse
Despite your bootloader shows as "unlocked", it most definitely is not; unlock it again and then you will be able to flash stuff
CarlosAG10 said:
Despite your bootloader shows as "unlocked", it most definitely is not; unlock it again and then you will be able to flash stuff
Click to expand...
Click to collapse
Okay, I've done it and now, I've entered TWRP and I discovered that I had unmouted a bit of stuff and that's why it wasn't working. Silly me
CarlosAG10 said:
Despite your bootloader shows as "unlocked", it most definitely is not; unlock it again and then you will be able to flash stuff
Click to expand...
Click to collapse
Okay I've done it, and I discovered that I unmounted some stuff.
Now I have another problem, my backup was busted. I want to flash the latest no brand EU firmware, and flashing PRA-LX1C432B199 fullota using fastboot seems to work, but the phone gets stuck in the "your device is booting now..." phase.
EDIT: sorry for the double post
Joseki100 said:
Okay I've done it, and I discovered that I unmounted some stuff.
Now I have another problem, my backup was busted. I want to flash the latest no brand EU firmware, and flashing PRA-LX1C432B199 fullota using fastboot seems to work, but the phone gets stuck in the "your device is booting now..." phase.
EDIT: sorry for the double post
Click to expand...
Click to collapse
First off, backup and restore procedure have been proved NOT WORKING for PRA devices unless you use haky's method which involves flashing a decrypted boot before starting, which I don't think you've done. So basically, forget about that backup (and for the next time, follow haky's method at codeofhonor.tech)
Secondly, B199 is a NON RELEASED firmware, maybe it's not even signed by Huawei, so you're taking some risks there; I would suggest flashing an older firmware and, if that doesn't work, following the restore method in the guide I told you about, with the firmware it provides.
Good luck!
CarlosAG10 said:
First off, backup and restore procedure have been proved NOT WORKING for PRA devices unless you use haky's method which involves flashing a decrypted boot before starting, which I don't think you've done. So basically, forget about that backup (and for the next time, follow haky's method at codeofhonor.tech)
Secondly, B199 is a NON RELEASED firmware, maybe it's not even signed by Huawei, so you're taking some risks there; I would suggest flashing an older firmware and, if that doesn't work, following the restore method in the guide I told you about, with the firmware it provides.
Good luck!
Click to expand...
Click to collapse
I've done the "Reset via TWRP" but the backup doesn't show up in TWRP. Is it because it's a no brand firmware and mine was a branded P8?
CarlosAG10 said:
First off, backup and restore procedure have been proved NOT WORKING for PRA devices unless you use haky's method which involves flashing a decrypted boot before starting, which I don't think you've done. So basically, forget about that backup (and for the next time, follow haky's method at codeofhonor.tech)
Good luck!
Click to expand...
Click to collapse
I understood that backup / restore do not work for /data partition (may even brick), but that we can backup/restore, for example, /system. Am I right ??
sambastrakan said:
I understood that backup / restore do not work for /data partition (may even brick), but that we can backup/restore, for example, /system. Am I right ??
Click to expand...
Click to collapse
I did successfully backup system, vendor and boot while decrypted, but not data. Anyway, I wasn't planning on restoring emui from twrp either, lots of chances of bricking involved.
Hi All,
I'm hoping someone will be able to help as I've spent most of the day chasing my tail it seems.
My 'stock' (non-rooted/non-flashed) Pixel 5 went into a boot loop randomly last night.
I've restarted, I've gone into the recovery mode and have tried to flash an OTA via ADB (which may not sound like much but is an achievement for someone with my limited technical skills), it's getting to 94% and then I'm receiving an error on the cmd prompt saying 'adb: failed to read command: No error' but on the phone itself it says that is was a 'success' status 0.
I've tried the current OTA and the developer version and I'm getting the above issue on both.
I tried copying the 'zip' to a USB stick and have plugged that in using the USB A to USB C dongle that comes with the pixel but I'm receiving an error stating that it cannot be initiated.
Can anyone suggest a possible next step? I have some files that I've realised don't go to my cloud backup and they are important to me so I'd like to if possible not have to wipe the device.
Many thanks.
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
l7777 said:
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
Click to expand...
Click to collapse
Hi, thanks for taking the time to respond. Everything was downloaded yesterday so is up to date. I re-downloaded just now and checked again and am still getting the same.
(~94%) adb: failed to read command: No error on cmd
Install from ADB completed with status 0 on the phone.
Is there a simple guide on how to flash-all (for someone as not technical as me) that you can point me towards?
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
did you try a different cable or usb port? borrow your friend's pc perhaps?
l7777 said:
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
Click to expand...
Click to collapse
Hi, thanks for this, I'll try another sideload with the April update and attempt it from another laptop, if that still doesn't work then I'll try the flash as you suggest.
swangjang said:
did you try a different cable or usb port? borrow your friend's pc perhaps?
Click to expand...
Click to collapse
I tried a different cable and port but not another laptop. I'll try that next after trying the April update.
Thanks.
tinhsoftware said:
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
Click to expand...
Click to collapse
Hi, no not yet. I think this will be the last step before I factory reset. Will try another cable, laptop and the April OTA this evening when I have time.
Thanks.
WFHbot said:
Hi, no not yet. I think this will be the last step before I factory reset. Will try another cable, laptop and the April OTA this evening when I have time.
Thanks.
Click to expand...
Click to collapse
Also a note on trying to use the web flash utility. Make sure to look at the advanced options on the installation page, it gives you an option to flash the latest update without wiping your device at all.
That could help in getting the phone running again so you can recover your important files, before deciding to do a compete wipe, if that's what you have planned.
Just look around the settings carefully before flashing and everything should go well .
The same thing happened to me, it must have been the April update, I updated my phone, everything seemed to work and then all of the sudden I was watching a video last night and the phone rebooted itself and kept being stuck in boot, it won't load the os but it keeps restarting itself.
I tried accesing recovery mode but on the bootloader screen it won't let me use the volume keys to start the phone in recovery mode or to try and hard reset it, while on the bootloader screen it resets itself... :/ I'll give google a call
Chad_Petree said:
The same thing happened to me, it must have been the April update, I updated my phone, everything seemed to work and then all of the sudden I was watching a video last night and the phone rebooted itself and kept being stuck in boot, it won't load the os but it keeps restarting itself.
I tried accesing recovery mode but on the bootloader screen it won't let me use the volume keys to start the phone in recovery mode or to try and hard reset it, while on the bootloader screen it resets itself... :/ I'll give google a call
Click to expand...
Click to collapse
That sucks. Hopefully they'll be able to do something more than just a factory reset.
I've tried sideloading the April update and that also failed at 94%. Will try another laptop in a while and see if that works, then try the flash as suggested above, if not then it's a factory reset for me.
ProjectAlly said:
Also a note on trying to use the web flash utility. Make sure to look at the advanced options on the installation page, it gives you an option to flash the latest update without wiping your device at all.
That could help in getting the phone running again so you can recover your important files, before deciding to do a compete wipe, if that's what you have planned.
Just look around the settings carefully before flashing and everything should go well .
Click to expand...
Click to collapse
Thanks, will have a look around and see what I can work out. It's looking like I'll have to go this route...
DO I need to unlock the bootloader do do this flash?
tinhsoftware said:
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
Click to expand...
Click to collapse
Thanks, will have a look and see if this works.
DO I need to unlock the bootloader do do this flash? If so, would this wipe the device?
WFHbot said:
Thanks, will have a look and see if this works.
DO I need to unlock the bootloader do do this flash? If so, would this wipe the device?
Click to expand...
Click to collapse
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
l7777 said:
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
Click to expand...
Click to collapse
Thanks, I tried that. Edited the file and tried running the flash-all.bat file but it's giving me an error:
Setting current slot to 'b' FAILED (remote: 'Fastboot command (set_active: ) is not allowed when locked')
fastboot: error: Command failed
Not sure what I'm doing wrong. Am I missing a step? Should the phone be on a certain menu when running the bat file?
l7777 said:
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
Click to expand...
Click to collapse
Is that a fact? I haven't had a bl unlock for many years now but I thought I could only do an OTA flash from fastboot with a locked bootloader. I know I can factory reset but other than that .. So if I loaded the beta 12 I could go back and flash a factory image? I would certainly flip the OEM switch first just in case.
bobby janow said:
Is that a fact? I haven't had a bl unlock for many years now but I thought I could only do an OTA flash from fastboot with a locked bootloader. I know I can factory reset but other than that .. So if I loaded the beta 12 I could go back and flash a factory image? I would certainly flip the OEM switch first just in case.
Click to expand...
Click to collapse
That's a good question. I assumed it was possible otherwise why have a factory image available. The consensus seems to be mixed though.
OP: I just did an update from January to April and yes I also got the error at 94% from ADB but the phone reported status 0. Booted up no problem. Have you tried booting into safe mode? Is USB Debugging on? Can you get a logcat of the attempted boot?
l7777 said:
That's a good question. I assumed it was possible otherwise why have a factory image available. The consensus seems to be mixed though.
OP: I just did an update from January to April and yes I also got the error at 94% from ADB but the phone reported status 0. Booted up no problem. Have you tried booting into safe mode? Is USB Debugging on? Can you get a logcat of the attempted boot?
Click to expand...
Click to collapse
Hi,
I've tried booting into safe mode by keeping the volume down button pressed but no luck.
I'm pretty sure that the USB debugging is enabled, but not 100% certain.
How would I go about getting logcat of the attempted boot?
Thanks for all the help thus far.
WFHbot said:
Hi,
I've tried booting into safe mode by keeping the volume down button pressed but no luck.
I'm pretty sure that the USB debugging is enabled, but not 100% certain.
How would I go about getting logcat of the attempted boot?
Thanks for all the help thus far.
Click to expand...
Click to collapse
You'll have to factory reset in recovery. I had something similar happen yesterday morning. The reboot was done by me on the way to work though. A factory reset fixed it. Of course all user data was wiped, but Google backups did a good job of restoring almost everything I wanted restored (except for apps not on the G Play Store of course). You'll need to sign into everything again, but most things won't be lost including root.