Database Info

Honor 5C Soft Brick / Hard Brick HELP??!!??

Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!!
So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo.
The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share.

please....please.......help???
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small!

[Solved] Possibly bricked, eRecovery not working

I wanted to flash a ROM, so I unlocked the bootloader and installed TWRP successfully. Then I downloaded the ROM, factory reset, format data, and installed the ROM. When the phone booted, it showed a black screen, and only the hardware buttons worked. I could lock the phone, and if I pressed the power button, it would "light up" the screen, but still black. Holding the power button gave me the power menu from the ROM I flashed (advanced boot options).
I did another factory reset and flashed the ROM again, and from thereon out, it never made it to the lock screen again.
I have attempted the eRecovery function, but it doesn't fix the issue either. The firmware downloads and is installed, but then it just boot loops for a couple times, then goes back to the screen suggesting a recovery operation.
Is this permanent now, or can it can still be salvaged?
Huawei Mate 9
Version: MHA-L29C567B190
*Edit:
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Solution:
Apparently, unlocking the bootloader several times seems to have solved the issue.
Once again, thanks to everyone who helped me out with this.

Which rom did you install.
What was the rom, which was installed before?
Did you change branding via manipulating oem info?
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)

use another Android phone download huaweifirmware finder on the google play ，select mha-l29c567，than select dns update，change your router dns，you can do erecovery after setup dns！

sweetjuice said:
use another Android phone download huaweifirmware finder on the google play ，select mha-l29c567，than select dns update，change your router dns，you can do erecovery after setup dns！
Click to expand...
Click to collapse
Thank you for your response. However, I tried it and it didn't work for me. I downloaded the app, checked the firmware was available, registered the update, changed my router DNS, and then attempted the eRecovery. It downloaded the package then installed it, but the same problem continues.

audioralf said:
Which rom did you install.
What was the rom, which was installed before?
Did you change branding via manipulating oem info?
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Click to expand...
Click to collapse
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.

Which stock? Model and firmware Version?
My device: Mate 9 supersu B190 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)

you can install a full firmware with hwota method.

audioralf said:
Which stock? Model and firmware Version?
My device: Mate 9 supersu B190 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Click to expand...
Click to collapse
Is this the information you're asking for?
Huawei Mate 9
Version: MHA-L29C567B910
I don't know how to get any other information (other than the IMEI and SN which are on the box), since I can't make it past the boot logo screen.

mavera said:
you can install a full firmware with hwota method.
Click to expand...
Click to collapse
How would I go about doing that? I can't take the phone past the boot logo screen; it just boot loops then goes to the eRecovery screen. And when I try that recovery method, it only gives me the option to download latest version over WiFi and install it. Which does not fix the problem.

cr33p3r1n1134 said:
How would I go about doing that? I can't take the phone past the boot logo screen; it just boot loops then goes to the eRecovery screen. And when I try that recovery method, it only gives me the option to download latest version over WiFi and install it. Which does not fix the problem.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 use this guide. You can change your reg code as c432, c636 etc. Only you must know your unlock code.

mavera said:
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 use this guide. You can change your reg code as c432, c636 etc. Only you must know your unlock code.
Click to expand...
Click to collapse
Rebranding is not really necessary.
@OP
For MHA-L29C567B190 (you wrote B910 which I assume is incorrect), use:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1356/g77/v84935/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...35/f2/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/.../v84935/f2/full/hw/usa/update_full_hw_usa.zip

I don't want to count my chickens before they hatch, but somehow it appears my phone is now working again. I did not rebrand nor update it. I simply unlocked the bootloader, AGAIN (which is what confuses me since I tried it before and it didn't work, at all). Regardless, I am not complaining!
I am not marking this thread as solved yet, just in case, but I will do so later on in the day if the phone continues working as before.
I want to thank all of you for your time and input, I really appreciate it.
Also, I'm never trying to flash anything on this phone again; I have learned my lesson. :/

cr33p3r1n1134 said:
I don't want to count my chickens before they hatch, but somehow it appears my phone is now working again. I did not rebrand nor update it. I simply unlocked the bootloader, AGAIN (which is what confuses me since I tried it before and it didn't work, at all). Regardless, I am not complaining!
I am not marking this thread as solved yet, just in case, but I will do so later on in the day if the phone continues working as before.
I want to thank all of you for your time and input, I really appreciate it.
Also, I'm never trying to flash anything on this phone again; I have learned my lesson. :/
Click to expand...
Click to collapse
Unlocking bootloader does a factory reset so that might be why it's working again

cr33p3r1n1134 said:
I wanted to flash a ROM, so I unlocked the bootloader and installed TWRP successfully. Then I downloaded the ROM, factory reset, format data, and installed the ROM. When the phone booted, it showed a black screen, and only the hardware buttons worked. I could lock the phone, and if I pressed the power button, it would "light up" the screen, but still black. Holding the power button gave me the power menu from the ROM I flashed (advanced boot options).
I did another factory reset and flashed the ROM again, and from thereon out, it never made it to the lock screen again.
I have attempted the eRecovery function, but it doesn't fix the issue either. The firmware downloads and is installed, but then it just boot loops for a couple times, then goes back to the screen suggesting a recovery operation.
Is this permanent now, or can it can still be salvaged?
Huawei Mate 9
Version: MHA-L29C567B190
*Edit:
The ROM I attempted to install was ROM-Aur-v1.5.
I had no ROM installed previously; phone was stock.
I did not manipulate the OEM info; all I did was unlock the bootloader with the unlock code I was given by the Huawei online site.
Solution:
Apparently, unlocking the bootloader several times seems to have solved the issue.
Once again, thanks to everyone who helped me out with this.
Click to expand...
Click to collapse
I know this is a really old thread, but this is happening to me too. How did you unlock the bootloader again? adb isn't recognizing my device? Any suggestions?

ji_mestone said:
I know this is a really old thread, but this is happening to me too. How did you unlock the bootloader again? adb isn't recognizing my device? Any suggestions?
Click to expand...
Click to collapse
Unfortunately, I do not remember the exact process I performed in order to unlock the bootloader the final time.
I remember I had to play a lot back and forth with adb and fastboot. Have you checked if fastboot recognizes your phone?
I believe that what I did was start from the very beginning; installing a recovery (I used TWRP). If fastboot recognizes your phone, and you are able to install a recovery, from there I'm pretty sure adb will recognize your phone and then you can unlock the bootloader.
I would recommend not trying anything fancy. Only recovery and bootloader.
I hope this answers your question and helps you out. Best of luck.

cr33p3r1n1134 said:
Unfortunately, I do not remember the exact process I performed in order to unlock the bootloader the final time.
I remember I had to play a lot back and forth with adb and fastboot. Have you checked if fastboot recognizes your phone?
I believe that what I did was start from the very beginning; installing a recovery (I used TWRP). If fastboot recognizes your phone, and you are able to install a recovery, from there I'm pretty sure adb will recognize your phone and then you can unlock the bootloader.
I would recommend not trying anything fancy. Only recovery and bootloader.
I hope this answers your question and helps you out. Best of luck.
Click to expand...
Click to collapse
Thanks for responding! I'm still at a loss two hours later.
Unfortunately USB debugging got turned off somewhere along the way, so ADB and fastboot aren't recognizing my phone. I can still access TWRP, but when I try adb sideload in TWRP is just says it's starting but keeps loading and nothing comes up and I get a message on my computer that says "the last USB device you connected to this computer malfunctioned, and Windows does not recognize it"

ji_mestone said:
Thanks for responding! I'm still at a loss two hours later.
Unfortunately USB debugging got turned off somewhere along the way, so ADB and fastboot aren't recognizing my phone. I can still access TWRP, but when I try adb sideload in TWRP is just says it's starting but keeps loading and nothing comes up and I get a message on my computer that says "the last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
Click to expand...
Click to collapse
Yeah, the ADB sideload problem also happened to me. Eventually gave up on that.
I hope I'm allow to post links.
But here is a link to something I remember using.
http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/
Using those tools mentioned in that post helped me out. I had to do a lot of experimenting with that as well. Every time I connected and disconnected my phone from my computer, I checked which were the references that needed deleting, then deleted them. It was tedious, but I'm not expert, so maybe I took the long way.
Maybe try using those tools?

G955FD Softbricked. OEM Unlock is Disabled.

Help Help Help :
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got TWRP cant install.Because. OEM locked.
It flashed. Great. But now IT STILL DOESNT BOOT. I'm stuck at NO COMMAND, it keeps restarting after 20-30 seconds of showing no command. and it's looping all over.*
i flashed stock firmware.It is flashed.Then reboot.Then install system update.Then Erasing.Then rebooting.Then NO COMMAND.Then reboot itselve recovery mode.Then i wiped factoory and cache.Then press rwboot to system.Then Samsung Galaxy S8 Plus.Then install system update.Erasing.No Command. etc. Keeps rebooting. its on NO command screen. It just restarts. Doesnt boot. I want to enable OEM Unlock. I installed combination binary. But not appear in Developer Mode.
i flash atock with Kies emergency.I flash different stock firmware from updato.com. But nothing happend.

I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?

JeffDC said:
I'm a little confused.
What state is your phone currently in, i.e. can you get into download mode, turn off... what?
Click to expand...
Click to collapse
KIES says that. (THR) Stock. i downloaded it and flashed with Odin. Then reboot. Then system install update. Then Erasing. Then reboot and No Command! 30 seconds keeps rebooting itself 30 seconds interval Random.
I did factory format, cache clear. then the same problem. i want to install twrp recovery with oden. It says Oem Lock. Not allowed. But i flashed Combinary file. I can get into system and i to developer mode but dosnt seem OEM UNLOCK that ll do enable it.

Ok mate, but if you press Vol- + Bixby + power for couple of seconds, can you access to download mode? If you can, I think you'll have to install the firmware all over again.

Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.

Did OP find a fix to this problem?
I am experiencing a similar issue. Picked my phone up to find had randomly gone into a boot loop. Tried soft reset, cache wipe, factory reset - all successful but the phone would still reboot and be stuck on device model screen. Next I decided to flash the device with stock firmware. The flash passed in Odin, the phone then rebooted, loaded to device model screen, then a screen appeared saying "installing updates" which would make it to 25% then crash. After this the phone keeps booting, shows a screen with a dead android icon and says "no command" or "error". I have tried to flash the device using Oreo and Nougat firmware but have failed every time (although the flash did pass in Odin)
Any help would be greatly appreciated as I would rather not buy a new phone due to a random hardware fault which is out of my control.

southsideswaggar said:
Try flashing using latest firmware from sammobile. Use Odin to flash all the files contained in firmware download. Make sure you get latest firmware for your carrier. Google how to flash using Odin. Hope this gets you in the right direction. Good luck finding what u need, do copious amounts of research before attempting any rooting of devices and if all steps aren't clear as day to you then do not attempt it unless you don't mind buying multiple expensive phones to tinker with.
Click to expand...
Click to collapse
This is perfect if you have soft bricked your phone!

follow this video maybe it help you
https://forum.xda-developers.com/ga...g-aqg5-fix-t3636857/post73032395#post73032395
https://www.youtube.com/watch?v=VTi3uBkpJic&t=155s

Bricked when returning to stock (No command)

Hey guys,
decided to flash the latest DBT Firmware via Odin to get back to stock completely. (G930FXXU3ESA3)
After flashing the firmware through Odin the phone reboots and then installs an update and erases data (blue background).
After a second reboot I end up with a blue screen and the simple error: "No command".
I can not get into recovery, as I end up with the same error message wether booting into recovery or the system.
I CAN however get into downloadmode and flash twrp, after that I can boot into system but I want to keep the whole system vanilla, without TWRP.
Installing TWRP keeps the device encrypted, no matter what. I can wipe, then install no-verity-encrypt and as soon as I reboot the device is encrypted again.
Ive tried: Different Firmware Version (December 2018), 3 different cables, different odin versions.
Edit: attached an Image of the message that Pops up after about 30sec on the no command screen.

Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.

FLASH No verity.zip
VIA TWRP
https://forum.xda-developers.com/attachment.php?attachmentid=4490455&d=1525176288

cooltt said:
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
Click to expand...
Click to collapse
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP

Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)

Scorpionea said:
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Click to expand...
Click to collapse
Did a efs backup through TWRP just in case, then flashed the latest DBT firmware with nand erase -> still the same problem.
I can only guess that this was caused by using a backup from another phone back when Oreo came out, this probably messed something up really badly. Very weird, im kinda lost.

Killuminati91 said:
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Click to expand...
Click to collapse
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.

cooltt said:
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
Click to expand...
Click to collapse
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.

Killuminati91 said:
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Click to expand...
Click to collapse
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.

cooltt said:
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
Click to expand...
Click to collapse
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.

Killuminati91 said:
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Click to expand...
Click to collapse
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.

cooltt said:
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
Click to expand...
Click to collapse
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.

Killuminati91 said:
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Click to expand...
Click to collapse
Thats because he's a scammer. Never donate to get your phone fixed! Donate to Rom developers and things you like but never to get the phone fixed, they're usually lying.
The serial number should be the same ON the phone as displayed IN phone. Tell me the story about the phone, how did you get it? what region? where are you? what firmware was installed? Can you still flash a ROM with TWRP? Can you check OEM unlock?
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
nmnmnmnmnmnmnmnmnm

Pretty sure he was just trying to remote repair for a price, which is not allowed on XDA. Would obviously donated on my own if he actually fixed it.
Bought the phone unlocked directly from a provider (simply - germany - dbt - g930f) back in 2016. Tripped kn0x after a few months, installed a few custom roms until Oreo came out.
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Since then I had constant connection problems, weak internet connection, dropped calls and so on.
Broke my screen and then decided to repair it myself. Bought a new frame, screen, battery, usb-port, earpiece and vibrator - managed to assemble all of that.
I can install all latest official firmwares (bootloader 3) through Odin. If I leave it at that I have no recovery and end up with the initially shown screen and "No command".
If i install TWRP from there and simply root with magisk or apply dm-verity-fix I can boot into the stock firmware with everything working.
I can also install ROMs. Just going completely vanilla is not possible anymore. OEM Unlock is checked, USB debugging works.
Edit: What is also astounding: If I flash version DBT-G930FXXS3ERHD-20180918145033 (oldest possible Oreo Version) I can enter recovery and do a factory reset and wipe cache.
If I do that however I am stuck at the Galaxy S7 Logo, not even bootlooping.

Killuminati91 said:
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Click to expand...
Click to collapse
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.

cooltt said:
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
Click to expand...
Click to collapse
Dang it. Thank you! Off to find someone who can do this via remote access or in Berlin.

Same situation right now with my S7. Damn.

Hi everyone. Did you guys find any way to resolve this issue? i have exactly the same issue here.. but in my case i cannot use twrp cuz i never installed it before... the issue happened right after i tried to enter the recovery mode by pressing the buttons...
my wife's galaxy s7 touch screen was acting weird and i tried to get into the recovey mode..which is pretty muh easy to do... but once i tried the no command msg came up and now i have exatly the same case as the guy that opened this thread....also done everything hes done....any clue about this anyone?
id appreciate some help..
thanks in advance
Diego Boffa

Anyone?

I have exactly the same error with "fail to open recovery_cause(No such file or directory)#
My Tablet is now stuck with a blue "android dead" screen saying "No command".
My history to disaster:
- i've recovered a "broken" Samsung Tablet (sm-T585) with corrupted file system via
* Download Mode works -> TWRP install -> Mount option -> use ADB to recreate EFS partition -> re-flash stock image (android 8) with odin
- device works fine
- then i've noticed it can only be used with a certain cell provider (o2)
- then i've tried to flash an older version of the stock rom (android 7) due some problems in Android 8 (often some slow downs while operating)
- this doesn't work, the flash don't start
- therefore nothing should be happend, or?
- then i've can't get anymore in the stock recovery to wipe all data
...therefore the mess began:
* i can't flash TWRP anymore
* i can't flash stock recovery anymore
* i only can get into download mode
* i can only flash a certain rom type successfully (green PASS within odin), but with the final stuck with boot loop, with the mentioned blue screen
* other rom version can't flashed
I hopefully ask you guys here, if anyone can help me?
Any help would be very appreciated ...

Cannot load Android System. Your data may be corrupt.

Backstory: I upgraded to android 10 a few weeks ago, aside from a few user apps breaking, there weren't any system issues. Recently, I received another update (seems like a patch ?) to android 10 and updated as well. I'm not sure if this recent update actually completed.
Last night, it seems like my phone went into a boot loop while I was sleeping. When I woke up the phone was hot, and each boot was so short that there was no opportunity to go into recovery mode. I pretty much had no choice other than to let the battery drain.
So I walked away and came back a while later to a peculiar recovery screen that said "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
There's only 2 options: "Try again" and "Factory data reset". `adb devices` from the PC is unable to detect my pixel 3 here. "Try again" simply attempts to boot, and I just return to this same screen again (at least it doesn't loop now). I'm reluctant to factory reset as I want to at least have the chance to back up some data.
I am able to enter fastboot from this screen using Power + Volume Down. `fastboot devices` from the PC is able to detect the phone. However, because the bootloader is locked (haven't unlocked the bl since i started using nexus/pixel phones), I don't know if there's much i can do here.
My question is, is there anything that I can try at this point to boot into android 10, recover some data, then do a factory reset ?

From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota

sliding_billy said:
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
Click to expand...
Click to collapse
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.

superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Not knowing what is available with the BL locked... Is the new rescue mode option one of the power up/down choices from your BL/Fastboot screen? That rescue mode is supposed to allow ADB command to work. If not, you are going to have to do a factory reset and if that doesn't help contact Google and RMA. Ability to get out of bricks is the biggest reason to unlock your BL (if you purchased a Google unlockable BL phone) unless you purchased a Verizon phone and can't. In that case, back to the last comment about factory reset/RMA.

superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Had this happen and I had to do a factory reset prior to unlocking bootloader ,which as was mentioned above is way easier to fix because you can reflash factory image without wiping all data

same thing happened to me; the previous comments gave me the outline of what was needed, so thank you. now for the op:
1. on the screen that offers try again or factory erase, choose "try again"
2. IMMEDIATELY press and hold volume down
3. when you reach the bootloader screen, you may release volume down
4. this is the standard bootloader screen for pixel 3. you should be able to cycle options do so to select 'recovery" (or whatever it says. I'm not going to reboot my phone to see exactly what it says, but I'm sure you get the idea)

Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.

Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
Sounds like this problem. https://forum.xda-developers.com/t/...xxxx_sn-xxxxxxxx.4205331/page-7#post-85981389

Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.

AsItLies said:
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
Click to expand...
Click to collapse
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.

Prudhvi89 said:
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Click to expand...
Click to collapse
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructions​The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers

AsItLies said:
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructions​The factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
Click to expand...
Click to collapse
Hi, thanks for quick response. I am getting below error, not sure how to correct it.

Prudhvi89 said:
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Click to expand...
Click to collapse
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.

Currently I am not able to switch on my phone !!!

AsItLies said:
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Click to expand...
Click to collapse
Currently I am not able to switch on the device !!

Prudhvi89 said:
Currently I am not able to switch on the device !!
Click to expand...
Click to collapse
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.

AsItLies said:
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
Click to expand...
Click to collapse
Ok got it !! Thanks for your prompt response & support.

The "Cannot load Android system, Your data may be corrupt" error is known as Rescue Party. Fortunately, fixing it should be relatively simple.
Try dirty flashing the factory image. Do not attempt to flash a patched boot image; leave everything stock.
If that fails, select "Factory data reset". It will wipe your phone, but it should reboot into Android system.
That bootloader message "Your device is corrupt. It can't be trusted" means that the signed key for Verified Boot somehow got screwed up. In this case, I would also recommend reflashing the factory image.
In both cases, the easiest option is to use the Android Flash Tool. It's like a GUI for flashing the factory image.