Related
Hi all,
Been given a Nexus S i9023 by my brother who has been "tampering" with it and now it seems a bit messed up.
When booting up - it gets stuck on the "Google" screen with a padlock on it... I can get into fastboot and I can flash recovery but when I attempt to load any recovery - I get that same Google screen with the padlock! I've downloaded a stock rom and even flashed system etc via fastboot but that still gets me nowhere past the damn padlock!!
I've tried to "fastboot boot recovery.img" and I still get the Google screen with the padlock but it says "Fastboot status - OK" on the bottom left.
I've searched and searched but everyone just seems to give tips on how to flash recovery. I know how to flash recovery; it just seem to be going into it though! Could the internal memory be screwed?
Thanks for any advice!
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
albundy2010 said:
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
Click to expand...
Click to collapse
The phone stops at Google with the padlock on boot! Can't even get into the OS. Going to try to unbrick it and Odin but left my ubuntu laptop at my parents and can't be bothered to go get it... couldn't get it to work booting off cd rom. Kept giving me the "SBL Injection Failure Failed to find device" error booting ubuntu on a CD!
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
albundy2010 said:
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
Click to expand...
Click to collapse
No idea why I said Odin - I meant the unbrickable recovery thing.
I tried Odin with a Jig last night; got it into download mode and flashed with odin. Got the same result.
fastboot -w also gives the same issue...
If I have a storage issue - is there any way I can tell?
Basically you can tell by the issues you're having. Doing all the proper stuff to flash images etc and still having a booting/working device.
As far as a actual diagnostic tool I don't know of one. But it sure sounds like a hw issue to me.
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Pironi90 said:
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Click to expand...
Click to collapse
Reflash your recovery using fastboot.
polobunny said:
Reflash your recovery using fastboot.
Click to expand...
Click to collapse
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Pironi90 said:
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Click to expand...
Click to collapse
Flash custom recovery.img part
http://wiki.cyanogenmod.org/wiki/fastboot#Flash_Custom_Recovery.img
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
polobunny said:
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
I think so yes, I could access recovery before if that's what you mean by unlocked
Pironi90 said:
I think so yes, I could access recovery before if that's what you mean by unlocked
Click to expand...
Click to collapse
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
You are entering recovery. Stock recovery
If you want a custom one either flash with fastboot or if you're rooted with a app. Goo manager. Rom manager etc.
Keep it mind that if you're on a stock ROM the custom recovery gets overwritten back to stock when the phone boots up the os
Q
UselessSniper001 said:
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
Click to expand...
Click to collapse
Then my phone is unlocked yes
polobunny said:
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
In installed the drivers and I installed the fastboot executable, but what do I have to do next? If I run the fastboot.exe, it just quickly shows a CMD-window and then disappears.
Edit:
I just discovered that, when I'm at the bootloader (I think it's called that way, the screen where you can select recovery), and I choose to reboot, I get the same 'error' as when I try to enter recovery.
Edit:
Alright, I was able to flash a new recovery, using cmd, but now when I try to enter my recovery, the phone gets stuck at a black screen with Google logo and padlock...
I have same problem as wolverine_2k who made the post. My nexus, can't start, I tried reboot and recovery but didn't work. After reboot or recovery I see Google logo, than Nexus screen and that is it. It didn't move to home screen and it stay with lighting screen all the time till I remove the battery. I can't power off it and don't know what to do. I can't transfer data with my PC (it don't recognize the device - only notice that "unknown device" is connected). Please any ideas?
P.S.: My English is not good, if someone answer do it simple please
Thanks!
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
@bitdomo might be able to help you lol
Might be bad eMMC or something?
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
simms22 said:
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
Click to expand...
Click to collapse
Hey I'm using "fastboot flash recovery recovery.img" and that's what I've used in the past. I've had a fully functioning rom with fully functioning recovery for a while until yesterday.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok thanks I'll try this and check the text in fastboot after work today. Thanks for the responses guys.
After reading some more last night I'm afraid it's an emmc problem but I like to be proven wrong sometimes.
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
beekay201 said:
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
Click to expand...
Click to collapse
I actually have that thread open on my computer. It was my next attempt of repair before starting the thread late last night. Thanks for the suggestion I will certainly try it.
Update: I tried pushing Philz recovery to the phone which seemed to work fine until I selected go to recovery mode. It just went back to that barely light black screen. I'll try again when I get home. Going to try Bitdomo's advice about locking bootloader first.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Out of curiosity what's the reason for using two brands, or were they just available so they were used?
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Bitdomo I'm trying the Flashtool but it's staying at 0% on the firmware update and nothing is popping up on computer or in Device Manager. Had no connection issues prior to the brick or with adb/fastboot. My Ports aren't evening showing at all in DM even if I select show hidden devices.
aburn95 said:
How do I lock the bootloader without being able to put the .zip on my internal memory?
Click to expand...
Click to collapse
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I honestly wanted to do that but it seemed too easy. I was trying to lock it like I did before when i had to send original back to T-Mobile. Sorry and thanks.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok so it stayed locked so that's a start. I'm back in download mode again but it's staying at 0% and nothing on computer.
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Unzip the zip and use manual flash commands. Clikc the link in my signature and read my "adb and fastboot. What is it?" thread of you're unsure of the commands.
Sent from my Nexus 5 using Tapatalk
aburn95 said:
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Click to expand...
Click to collapse
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
bitdomo said:
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
Click to expand...
Click to collapse
Sorry I meant to tell you yesterday... D820H 16GB. Should I still be able to toggle the tamper tag so they will take it back with no problems? Or am I screwed?
aburn95 said:
Sorry I meant to tell you yesterday... 820H. Should I still be able to toggle the tamper so they will take it back with no problems? Or am I screwed?
Click to expand...
Click to collapse
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
bitdomo said:
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
Click to expand...
Click to collapse
Ok thanks. I haven't quite figured out the adb sideload function yet. I tried doing it through TWRP but it just sits there and does nothing after selecting. Maybe I'm trying the wrong thing. I got my phone from T-Mobile so I'll need to solve this. Thanks for the help.
This phone is being a real a-hole. I'm trying to boot to stock recovery but it just sits on a screen with a really big android with wiggling antennae. I pressed up+power many times but it stayed that way. So I tried booting to TWRP again and it did but went immediately to an "OpenRecoveryScript," had a little bar at the bottom for a while with some other stuff on the screen, then turned off.
I tried stock recovery again and it went to the little dead android this time but still nothing when I press up+power.
Any recommendations on removing TWRP and restoring stock recovery so I can move up to 7.1.1?
I don't have a backup of the old recovery.
Moogagot said:
Any recommendations on removing TWRP and restoring stock recovery so I can move up to 7.1.1?
I don't have a backup of the old recovery.
Click to expand...
Click to collapse
Flash the boot.img from the stock system image. This has been mentioned many times around this forum. Search is your friend.
cntryby429 said:
This has been mentioned many times around this forum. Search is your friend.
Click to expand...
Click to collapse
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Moogagot said:
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Click to expand...
Click to collapse
Well, it's actually everywhere. However, you have to discern what apply to you and what do not. That's the danger of a public forum such a this. Everyone has an opinion. Sometimes, an inaccurate answer is provided. Most other times, the incorrect question was originally posed.
In your case, you don't need to go back to the original stock image. Assuming your bootloader is still unlocked, just flash 7.1.1 and get on with your life. Download 7.1.1 stock image from the Google developers' web site. Extract it. Edit the flash-all.bat file to remove the -w switch if you don't want to lose userdata. Boot the phone into bootloader. Execute flash-all.bat. Then you have 7.1.1.
If you don't have a recovery backup, then you're taking a risk. I have not only a recovery backup, but more importantly, a complete set of Titanium backup on my laptop.
Moogagot said:
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Click to expand...
Click to collapse
Download the factory image for the version of Android that you're currently running. Look inside the zip and you'll find another zipped file. Open that and you'll see a file in there that's named boot.img. Extract the boot.img file the same folder as your fastboot is in, open a command prompt in that folder flash it with fastboot.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
That will get you back to the stock bootloader and stock recovery.
robocuff said:
Download the factory image for the version of Android that you're currently running. Look inside the zip and you'll find another zipped file. Open that and you'll see a file in there that's named boot.img. Extract the boot.img file the same folder as your fastboot is in, open a command prompt in that folder flash it with fastboot.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
That will get you back to the stock bootloader and stock recovery.
Click to expand...
Click to collapse
I tried flashing some other stuff and it bricked Google is sending out a replacement.
Moogagot said:
I tried flashing some other stuff and it bricked Google is sending out a replacement.
Click to expand...
Click to collapse
Well, hope there's not a next time, but power + volume up should take you to the recovery menu. It's next to impossible to brick phones any more. Lord knows I try daily to see how I can brick my phones, just so I can assist others.
quangtran1 said:
Well, hope there's not a next time, but power + volume up should take you to the recovery menu. It's next to impossible to brick phones any more. Lord knows I try daily to see how I can brick my phones, just so I can assist others.
Click to expand...
Click to collapse
I broke recovery. I just says "No Command"
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
No you didn't, at that screen with "No Command":
Hold the Power button and press Volume Up once, and a menu will appear.
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
Come on man, you can do it next time. Please?
http://lmgtfy.com/?q=no+command+stock+recovery+pixel
krelvinaz said:
No you didn't, at that screen with "No Command":
Hold the Power button and press Volume Up once, and a menu will appear.
Click to expand...
Click to collapse
No menu appears. I just get a flash and back to no command.
I can get into the bootloader, but again, any option leads to the No Command screen.
Ok, from the bootloader I was able to manually flash a different image and things are looking a little better.
I now have the dancing dots and ADB see's a device attached. PROGRESS!
The devices throws errors on bootup, but it runs for now.
Please ignore. Posted to wrong thread. Sorry!
Here's the easiest way I've found to update. You'll need TWRP, so go ahead and download it - https://twrp.me/devices/googlepixel.html. Put the img file on your computer and the zip file on your phone. You'll boot into TWRP by using the "Fastboot boot" command. DO NOT "fastboot flash" it or you'll have to re-flash the boot image to get your phone out of a bootloop.
Now that you're in TWRP, you'll need the OTA file. I've only tested going up one increment so I suggest doing it that way. If you're brave, go ahead and download the latest OTA - https://developers.google.com/android/ota. Worst case TWRP won't flash it and you'll have to go back and do them incrementally.
Now that you're in TWRP and have the OTA and TWRP-RC1.zip on your phone, flash the update just like you would a rom. As soon as it successfully flashes (and before you reboot), flash the TWRP zip.
I did this incrementally from NMF260 > NMF26U > NMF26V without any issues. I believe it'll work as long as you're moving up an OTA just as the phone would have normally received them. Just remember to flash TWRP every time after you install the OTA as it gets overwritten with each OTA.
Sent from my Pixel using Tapatalk
Google needs to start voiding warranty for people who want to unlock bootloader
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
I Know this post is old, I am just researching but, sounds to me like you really need to search, read, and actually learn before you attempt anything on your phone. I am not being hateful or rude, just pointing out the obvious....
Hi!
Okay, this case is really weird and of course is thanks to my negligence. I'm gonna post it hoping someone can help me, or at least keep other people aware about trying stupid things lol
I tried to update to Nougat with an unofficial method (I don't consider necessary to tell what method...) and I just messed it up, badly. I'll try to give a detailed explanation:
The phone has the bootloader unlocked. After trying to update to Nougat, it got stuck when rebooting. After the unlocked bootloader warning message, the phone won't go further than that, it just stays there. If I hold and press the power button for more than 10 seconds the phone won't shut down, it will restart to get stuck again after the unlocked BL warning, making impossible to turn it off completely.
I try to enter to stock recovery by pressing vol + and power button at the same time (tried other combinations, vol - and power button & vol -, vol + and power button) but I have no luck, it just gets stuck at the same point.
I already tried extracting BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img from an official update.app and flash them in that order via fastboot (yeah, I can enter to fastboot mode). The process is successful in terminal (I use Linux) but when I reboot the phone, it gets stuck again after the warning.
The only recovery that is actually working is TWRP, the one ported for the Honor 8 (flashed via fastboot), but it won't let me install any custom ROM, it just stays in "patching image unconditionally" forever, making me press and hold the power button but this won't shutdown the phone, it reboots, gets stuck and... so on *infinite loop*
Btw, when I wipe cache, dalvik and data in TWMP, the message "failed to mount /cust" with red letters appears, so it's probably a very corrupted system partition. also, It's impossible to repair the custom partition. This appears:
Repairing Custom using e2fdck...
/sbin/e2fsck -fp /devblock/mmcblk0p44 process ended with ERROR: 8
Unable to repair Custom.
Click to expand...
Click to collapse
Tried HiSuite from Huawei (in Windows) and it doesn't even recognize the phone.
Hope somebody could possibly give a solution, if there's any. If not, I'm afraid I have a beautiful paperweight now...
Oh yeah, one very important part: my Honor 8 is the US version (FRD-L04), and yes, I'm making sure I'm getting the current update.app for this model.
Any help would be greatly appreciated. Thanks in advance.
Hi There
you try this method.
Get a SD CARD
make a directory at the card root name dload
put your best update.app in the directory (the most older version the best)
insert into your phone 2nd sim slot
try everyway to make the 3 button combo.
hope this help
edit: you need stock recovery to do this
chongns said:
Hi There
you try this method.
Get a SD CARD
make a directory at the card root name dload
put your best update.app in the directory (the most older version the best)
insert into your phone 2nd sim slot
try everyway to make the 3 button combo.
hope this help
edit: you need stock recovery to do this
Click to expand...
Click to collapse
Hey, thanks!
unfortunately, as far as I know is that for this method I have to enter to stock recovery, but then again, I can't get in. The phone gets stuck trying any combination of pressed buttons... But I'll try it.
Edit: Trying your method right now, hope it goes well...
El Brillantinas said:
Hey, thanks!
unfortunately, as far as I know is that for this method I have to enter to stock recovery, but then again, I can't get in. The phone gets stuck trying any combination of pressed buttons...
Click to expand...
Click to collapse
Yes, but since you r able to go into TWRP, can your use adb command like adb reboot bootloader than flash stock recovery image?
after that since it is keep rebooting, you can hold your volume up and down all the way to force update.
IDK if this work. but no harm to try it, since it is "very hard brick"
Edit: Fastboot erase {partition} before flash back the image maybe help
chongns said:
Yes, but since you r able to go into TWRP, can your use adb command like adb reboot bootloader than flash stock recovery image?
after that since it is keep rebooting, you can hold your volume up and down all the way to force update.
IDK if this work. but no harm to try it, since it is "very hard brick"
Click to expand...
Click to collapse
Yep, I'm trying it now and right now is installing the update (the EMUI logo with the circular progress bar). Hope it works *crossed fingers*
Edit: No luck. After the process finished, it says:
Software install failed!
Get help from: http//www.emui.com/emotionetcetc.
Click to expand...
Click to collapse
El Brillantinas said:
Yep, I'm trying it now and right now is installing the update (the EMUI logo with the circular progress bar). Hope it works *crossed fingers*
Edit: No luck. After the process finished, it says:
Click to expand...
Click to collapse
I assume you having the update.app from a L04 full firmware, not the OTA.
for the not able to repair partition like custom maybe you can erase it using fastboot erase command and fastboot flash it back
or you can fastboot erase all the known partition like system, cache, data, custom etc.... and fastboot flash back the image.
i assume your fastboot still able to access
chongns said:
I assume you having the update.app from a L04 full firmware, not the OTA.
for the not able to repair partition like custom maybe you can erase it using fastboot erase command and fastboot flash it back
or you can fastboot erase all the known partition like system, cache, data, custom etc.... and fastboot flash back the image.
i assume your fastboot still able to access
Click to expand...
Click to collapse
I did it!!
I could bring it back following some of your methods. Here's how I achieved it:
-Formatted the Custom partition in fastboot.
-Flashed BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img again.
-Forced the update by putting the entire firmware in the dload folder located in the sdcard, it failed at the end, but I rebooted by pressing and holding the power button.
-The phone passed beyond the point where it was getting stuck (finally!), but now it got stuck in the Honor 8 blue screen. Rebooted it again doing coldboot.
-Entered to stock recovery, wiped everything.
Then I just rebooted it and Voalá! It started all new!
Guess it was not that hard brick haha. I'll have to change the name of the topic.
A million thanks @chongns, you rock!
El Brillantinas said:
I did it!!
I could bring it back following some of your methods. Here's how I achieved it:
-Formatted the Custom partition in fastboot.
-Flashed BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img again.
-Forced the update by putting the entire firmware in the dload folder located in the sdcard, it failed at the end, but I rebooted by pressing and holding the power button.
-The phone passed beyond the point where it was getting stuck (finally!), but now it got stuck in the Honor 8 blue screen. Rebooted it again doing coldboot.
-Entered to stock recovery, wiped everything.
Then I just rebooted it and Voalá! It started all new!
Guess it was not that hard brick haha. I'll have to change the name of the topic.
A million thanks @chongns, you rock!
Click to expand...
Click to collapse
Good to know you succeed.
please tag a moderator to move your thread to Guide, News and Discussion section..
most of the time ppl search solution at there.
Guide in another Huawei phone XDA forum.
http://forum.xda-developers.com/mate-8/general/fuss-debrick-restore-mate-8-t3457969
Moderatos, can you please move this topic to the Guides and discussion section? Thanks in advance.
Glad you fixed it bro. That was very critical.
El Brillantinas said:
Moderatos, can you please move this topic to the Guides and discussion section? Thanks in advance.
Click to expand...
Click to collapse
good to hear u go phone back , and there is another guides already exist to restore a framware throw the same method , thank you for sharing ur experience .
Here's the issure I'm having. My Honor 8 FRD-L04 is stuck at a hard brick. It won't reach the recovery. I tried to flash images using fastboot. But I end up with the error: FAILED (remote: Command not allowed)
Any help would be appreciated
bho01 said:
Here's the issure I'm having. My Honor 8 FRD-L04 is stuck at a hard brick. It won't reach the recovery. I tried to flash images using fastboot. But I end up with the error: FAILED (remote: Command not allowed)
Any help would be appreciated
Click to expand...
Click to collapse
Is your frp status lock in fastboot?
faizalotai said:
Is your frp status lock in fastboot?
Click to expand...
Click to collapse
No it's unlocked
bho01 said:
No it's unlocked
Click to expand...
Click to collapse
Your phone status?
faizalotai said:
Your phone status?
Click to expand...
Click to collapse
Still can't get into recovery and I'm still getting the "FAILED(Command not allowed)" error whenever I try to flash stock images
bho01 said:
Still can't get into recovery and I'm still getting the "FAILED(Command not allowed)" error whenever I try to flash stock images
Click to expand...
Click to collapse
I mean your phone status in fastboot.
Its comes with frp and phone status..both have to be unlocked in order to flash images.
Try using the dload method of flashing
faizalotai said:
I mean your phone status in fastboot.
Its comes with frp and phone status..both have to be unlocked in order to flash images.
Click to expand...
Click to collapse
Also unlocked
I have a Honor 6x (BLN-L24) with EMUI 5+, Android Nougat, all updated. It is the U.S. edition. I unlocked the Bootloader, installed ADB / Fastboot tools and can flash the correct TWRP recovery image (3.1.1-0-berlin.img) but everytime I try to reboot into recovery, the standard EMUI recover overwrites TWRP and I just end up in the EMUI recovery.
I've looked at every forum I can find, articles, etc... but can't wrap my head around this one. If anyone with a similar experience and/or with a solution could help, I'd be most grateful.
Thank you!
I agree with with Rommco05. He IS correct, as I wondered the same thing till I realized to try unplugging it. Also make sure its the Power AND up buttons at same time. If you happen to hold only the up button it will take you to the erecovery feature where it trys hooking to WiFi for updates , which wont help you either.
Still doesn't work
Thanks for the responses. Unfortunately, unplugging doesn't do it either with the key combination you suggested. The following article is helpful for key combinations but alas, it still won't load into TWRP.
It is really strange as I can't even get past "Your device has been unlocked and can't be trusted" screen now. It just stays there...
Super frustrating. I didn't know if it had anything to do with my model being the BLN-L24 US version. I bought it at BestBuy unlocked.
Also, when I try to download "Latest Version and Recovery" from "Huawei eRecovery", I'm getting "Getting package info failed". I
Try OpenKirin twrp from recoveries section here on 6X forums
etmartinkazoo said:
Super frustrating. I didn't know if it had anything to do with my model being the BLN-L24 US version. I bought it at BestBuy unlocked.
Click to expand...
Click to collapse
That's not the cause. My phone is also a BLN-L24 purchased from Best Buy and I have no issues using TWRP. What did you do after you install TWRP? Did you let the phone just reboot or did you try to go into TWRP before rebooting?
This is straight from TWRP website:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Key combination timing?
galapagos said:
That's not the cause. My phone is also a BLN-L24 purchased from Best Buy and I have no issues using TWRP. What did you do after you install TWRP? Did you let the phone just reboot or did you try to go into TWRP before rebooting?
This is straight from TWRP website:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Click to expand...
Click to collapse
This is helpful, thank you. I found a page "Key Combinations Clarified for Honor 6x" which has a number of key combinations but nothing is helpful in my case that I know of. Do I use these key combinations imediately after the flash?
Is there a specific tutorial or guide that was helpful for you? I'd be grateful for any further assistance.
Thanks.
Rommco05 said:
You need enter to recovery? TWRP?
Click to expand...
Click to collapse
That is the problem, I'm unable to enter TWRP after flashing it, unplugging the usb cable, holding power/volume up...
Finally got Twrp installed. Rooted and installed custom Rom (lineageos) but when I reboot after flash screen, it's just blank...
If I were you, I would go completely back to stock and start over. Once you fastboot flash TWRP, it is imperative that you reboot back into TWRP before booting into the OS. Also, bootloaders don't overwrite recoveries. They are separate partitions, so your title is a bit misleading.
Regardless, you must still have stock recovery on your device since it is "defaulting" to that instead of TWRP. Like I said, it is extremely important to boot into recovery after you first flash it.
fastboot flash recovery recovery.img
let it do it's thing.
fastboot reboot recovery OR you can do it manually in TWRP right after the flash.
Have you tried rebooting to recovery from the system?
Connect your device to your computer, enable USB Debugging, and run
Code:
adb reboot recovery
from Windows CMD or Linux Shell, or any other one you prefer.
If this works, then you are doing the recovery key combination wrong.
Cheers
I'm having the same issue as OP. I have a BLN-L24 from Best Buy in the US. Reverted to emui 4.1 and android 6, unlocked bootloader, flashed twrp-3.2.1-0-berlin.img, and it keeps booting into huawei erecovery.
I didn't get any info on what the OP actually did to get twrp installed.
FWIW, there is no "fastboot reboot recovery"
FWIW2, you can't turn off the honor 6x from the bootloader. the best you can do is a hard reboot.
etmartinkazoo said:
That is the problem, I'm unable to enter TWRP after flashing it, unplugging the usb cable, holding power/volume up...
Click to expand...
Click to collapse
I'm having your exact same problem. I can get into fastboot mode, flash TWRP berlin, but I cannot enter TWRP after flash. It just goes back to the normal warning screen "this phone is unlocked", boot normally or go to EMUI recovery.
What worked for you?
hexag1 said:
I'm having your exact same problem. I can get into fastboot mode, flash TWRP berlin, but I cannot enter TWRP after flash. It just goes back to the normal warning screen "this phone is unlocked", boot normally or go to EMUI recovery.
What worked for you?
Click to expand...
Click to collapse
RedSkull fixed my problem!