Hey everyone. I'll keep it as short as I can.
-Tried to unload boot loader and root
-Failed, got a "No Command" error.
-No problem, let's just relock and try another day.
-Go into fast boot cmd
-find the command "fastboot oem lock" as according to the FAQ
-"sst lock failure!" presented with.
As far as my limited ability thinks, I haven't actually done anything bar unlock the boot loader. I can still get to KitKat 4.4.2 and everything seems okay there, just wiped (as to be expected and I knew when unlocking the bootloader).
Basically, does anyone have any help to just get my bootloader relocked and for the message to go away?
Related
Hi,
Today i attempted to unlock my phones bootloader and flash TWRP (twrp-2.8.1.0-20142812-memul). I unlocked it fairly easily using the htc.dev website but encountered an issue when trying to flash the Recovery. The phone is stuck in the bootloader with the message ***TAMPERED*** ***UNLOCKED*** showing at the top. I cannot get off this and every attempt to get into the phone, such as by clicking on Reboot or holding the POW+VOL UP+VOL DOWN buttons, has failed, simply dumping me back on the bootloader homescreen. Does anybody know how to solve this issue?
Kind regards
James
Try re-flashing recovery from fastboot on your pc, I would even try redownloading the recovery just to be sure you didn't get a corrupted copy previously, also clear cache after flashing recovery.
The tampered message is normal so just ignore that.
You can even try rebooting boot loader and or recovery using fastboot commands, just search fastboot commands on Google and you'll find a list of relevant commands.
Jameswebb97 said:
Hi,
Today i attempted to unlock my phones bootloader and flash TWRP (twrp-2.8.1.0-20142812-memul). ...
Kind regards
James
Click to expand...
Click to collapse
there's a few problems with TWRP i notice in other phones. one of them was stuck in bootloader.
my solution was remove usb cable before rebooting.
got same issue...
Jameswebb97 said:
Hi,
Today i attempted to unlock my phones bootloader and flash TWRP (twrp-2.8.1.0-20142812-memul). I unlocked it fairly easily using the htc.dev website but encountered an issue when trying to flash the Recovery. The phone is stuck in the bootloader with the message ***TAMPERED*** ***UNLOCKED*** showing at the top. I cannot get off this and every attempt to get into the phone, such as by clicking on Reboot or holding the POW+VOL UP+VOL DOWN buttons, has failed, simply dumping me back on the bootloader homescreen. Does anybody know how to solve this issue?
Kind regards
James
Click to expand...
Click to collapse
I had that issue according to my version of TWRP. Try it with 2.8.5.0. After i re-flashed it with that, all worked fine. Give me feedback if you could solve it.
agh well after ages of trying different methods nothing worked. Even took it to my local phone shop who do software tweaks and recovery, the guy told me the entire Android OS had been removed...? Gave up and bought a new phone, thank you guys for trying anyway <3
I have a verizon htc one m7 that will boot to the verizon logo then restart. i can access the bootload/fastboot and recovery. when i issue the fastboot command of fastboot oem rebootRUU the command completes and phone goes black then the green htc logo appears and continues to try and boot normally. does anybody have any suggestions on how to get to the RUU mode? bootloader is locked and s-on is active. this is a completly stock phone.
I think you need unlocked bootloader (but I'm not sure). So try unlocking it (keep in mind that you'll loose the guarantee)
suchauser said:
I think you need unlocked bootloader (but I'm not sure). So try unlocking it (keep in mind that you'll loose the guarantee)
Click to expand...
Click to collapse
1- no need for an unlocked bootloader
2- he's on Verizon so he can't use HTCdev to unlock, and sunshine won't work without a booted phone
idragoncell said:
I have a verizon htc one m7 that will boot to the verizon logo then restart. i can access the bootload/fastboot and recovery. when i issue the fastboot command of fastboot oem rebootRUU the command completes and phone goes black then the green htc logo appears and continues to try and boot normally. does anybody have any suggestions on how to get to the RUU mode? bootloader is locked and s-on is active. this is a completly stock phone.
Click to expand...
Click to collapse
how about some background info, how you ended in this situation... if it's a complete stock phone (so you weren't messing around with flashing things), then it could very well be a hardware problem... but the above info isnt enough, you need to provide more details of how this came to be
it's also good practice to copy/paste the entire command prompt output, so we can take a look of what was typed and what the output generated
Customer bought the phone too me in a boot loop state.. he claims he was using it and it just went black then came back on but never fully booted kept restarting at the verizon logo. htc told him to try and factory reset the phone but that was a no go as well. i have tried a RUU utility and when the program says rebooting to bootloader it doesnt go into bootloader just trys to boot up normally. the same thing happens when i attempt to put it in RUU mode it just reboots and trys to boot normally.
idragoncell said:
Customer bought the phone too me in a boot loop state.. he claims he was using it and it just went black then came back on but never fully booted kept restarting at the verizon logo. htc told him to try and factory reset the phone but that was a no go as well. i have tried a RUU utility and when the program says rebooting to bootloader it doesnt go into bootloader just trys to boot up normally. the same thing happens when i attempt to put it in RUU mode it just reboots and trys to boot normally.
Click to expand...
Click to collapse
sorry, dont get me wrong, but since i've been back (for a few hours), people are ... let's just say, not very forthcoming
what would help:
a screenshot of bootloader
a "fastboot getvar all" (excluding the last 6 digits of IMEI, MEID, and serial number... those need not be shared)
possibly a fastboot oem last_dmesg
though if the phone is completely stock, never been tampered with, then you have a high chance it's a hardware problem
http://imgur.com/73JGfka
https://goo.gl/photos/hkdxnmNtB7ctd2XA9
http://imgur.com/El0SNkj
idragoncell said:
http://imgur.com/73JGfka
https://goo.gl/photos/hkdxnmNtB7ctd2XA9
http://imgur.com/El0SNkj
Click to expand...
Click to collapse
thanks for the details, nothing "looks" wrong from those, but the "fastboot oem last_dmesg" has to be done after attempting to flash something, after a (non flashing reboot) it will just be empty.
couldn't find much, but have you tried this RUU:
http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
EDIT:
1- RUU.EXE will leave a log (before you close the .exe), in c:\ruu_log\.......txt
2- command prompt copy/paste is preferred to a screenshot, since it's much easier to read
good luck
So I picked up a nexus 6 that was said to be bricked. It was cheap so I figured what the hell. Anyway it's stuck in fastboot. No matters options it goes back to the fastboot screen. In logs it says "invalid boot image header." device is locked status code 2. What chances do I have of getting this back up and running?
Sent from my D6708 using Tapatalk
Locked code status 2 = bootloader locked right?
Paperweight.
So there is nothing possible to do? I was under the impression is was almost impossible to hard brick a nexus 6. I guess i was ignorant. lol
the N6 and N9 was when they started having the oem unlock enabler in developer settings menu and without the ability to boot and enable that setting its just as screwed as any other locked phone.
Are you talking about bootloader mode?
Locked bootloader+stock recovery (no TWRP) =bricked.
I've read where others have typed "fastboot erase bootloader" which has removed the bootloader so the phone won't even start.
If you have an unlocked bootloader and TWRP then you can recover from most issues. I've formatted my phone with no OS before. You can adb pull a zip in or flash via OTG. Locking the bootloader with no custom recovery or ROM prevents you from installing anything
I'm stuck.
My phone boots to the welcome screen all the way to the wifi selection but stops after that saying the setup wizard cannot launch. So I cannot go into phone settings to "enable OEM unlocking" to follow the official HTC procedure for the bootloader unlock (which was once unlocked but is now relocked).
I looks like I have no recovery, because I cannot boot into recovery, it just fails.
If I go to (what I thought was) Download/Fastboot mode and try to Fastboot flash twrp for example, it says: FAILED (remote: cannot flash this partition in s-on state) ----> but I then read that this was because I was NOT actually in Download Mode.
So I think I managed to get to Download mode and tried the Fastboot command to flash TWRP again and now it says: FAILED (remote: 9: SD_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCK).
I suppose it means that my Bootloader isnt unlocked...but as mention initially, I cannot access the OS and enable the OEM unlocking toggle.
Since Fastboot isnt working, I dont know if an RUU would work.... And look like I will never know because everytime I launche the EXE file, it extracts, asks me to to accept the conditions, then nothing happens...
Please help!!
maximepull said:
I'm stuck.
My phone boots to the welcome screen all the way to the wifi selection but stops after that saying the setup wizard cannot launch. So I cannot go into phone settings to "enable OEM unlocking" to follow the official HTC procedure for the bootloader unlock (which was once unlocked but is now relocked).
I looks like I have no recovery, because I cannot boot into recovery, it just fails.
If I go to (what I thought was) Download/Fastboot mode and try to Fastboot flash twrp for example, it says: FAILED (remote: cannot flash this partition in s-on state) ----> but I then read that this was because I was NOT actually in Download Mode.
So I think I managed to get to Download mode and tried the Fastboot command to flash TWRP again and now it says: FAILED (remote: 9: SD_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCK).
I suppose it means that my Bootloader isnt unlocked...but as mention initially, I cannot access the OS and enable the OEM unlocking toggle.
Since Fastboot isnt working, I dont know if an RUU would work.... And look like I will never know because everytime I launche the EXE file, it extracts, asks me to to accept the conditions, then nothing happens...
Please help!!
Click to expand...
Click to collapse
I am replying to myself. After trying several things on the phone, I went back to the OS's setup wizard. The second step (2 steps before the crash), has some text and one has a clickable link saying "learn more". It actually opens some phone settings, and from there, you can access all of the phone settings. So I was able to activate Dev mode, OEM unlock and debugging without going through the Wizard!!
Followed the BL unlock procedures on HTC website and as soon as it was unlocked, phone rebooted and TWRP reappeared! I'm saved!!
Thought I would share my discovery in case this ever happens to you too.
I also discovered another possible course of action. When accessing the same "link" to get to settings, go to the network settings and put the phone on Airplane mode. Go back to the setup wizard and skip the connection to wifi. I think it will skip the part of the Setup that made the OS crash.
I got two brand new Pixel 4a (5G) for my girlfriend and me. Mine worked perfect, hers was freezing and rebooting all the time. To solve this, I wanted to reflash the factory image.
I messed up the two devices and didn't notice, that the bootloader on hers wasn't unlocked yet. So I ran flash-all.sh on locked bootloader. Now the Pixel says "Can't find valid operating system." and I'm stuck in fastboot-mode with locked bootloader. Neither can start Rescue-, nor Recovery mode.
After I'm not able to unlock bootloader (because I never allowed it on her phone), I will bring it back to the shop tomorrow and ask for an exchange/repair.
But how can that be? Shouldn't a locked bootloader protect the device from a brick like that? I mean the flash-all.sh runs some "fastboot flash" and a "fastboot update" command, and they should just fail on locked bootloader, shouldn't they?
Weltraumpenner said:
I got two brand new Pixel 4a (5G) for my girlfriend and me. Mine worked perfect, hers was freezing and rebooting all the time. To solve this, I wanted to reflash the factory image.
I messed up the two devices and didn't notice, that the bootloader on hers wasn't unlocked yet. So I ran flash-all.sh on locked bootloader. Now the Pixel says "Can't find valid operating system." and I'm stuck in fastboot-mode with locked bootloader. Neither can start Rescue-, nor Recovery mode.
After I'm not able to unlock bootloader (because I never allowed it on her phone), I will bring it back to the shop tomorrow and ask for an exchange/repair.
But how can that be? Shouldn't a locked bootloader protect the device from a brick like that? I mean the flash-all.sh runs some "fastboot flash" and a "fastboot update" command, and they should just fail on locked bootloader, shouldn't they?
Click to expand...
Click to collapse
Try fastbooting the newest ota instead of the full factory image. Also, try going to Android recovery and hitting the factory reset inside the menu there. I believe to access the recovery through fastboot you wait for the dead Android guy and then press volume up and power at the same time.
Sent from my Pixel 4a using Tapatalk
Did you ever figure this out? Google had a chrome extension flag tool. Instead of cmd/cli adb.