So, when I was messing around with the Kindle Fire, at times it was farely easy for it to get stuck on certain screens, depending on what you set the bootmode to using fastboot. Anyways, after relocking the bootloader of my One X, I got stuck in the bootloader. I would try to reboot but it would just keep coming back to the bootloader no matter what happened. Evenetually, I installed the 1.85 RUU I downloaded and that got me out of the bootloader loop, but I was wondering if anyone might know what happened and how to get out of the situation without resorting to an RUU. With the Kindle Fire, the fastboot command was
Code:
fastboot oem idme bootmode 4000
so I was just wondering/hoping if there might be a similar command for the One X.
When you relock the bootloader all you can do is install the ruu. So what you saw is normal.
gunnyman said:
When you relock the bootloader all you can do is install the ruu. So what you saw is normal.
Click to expand...
Click to collapse
Ah, that makes sense...thx!
Related
Hi,
My phone is bricked and it won't come off the splash screen. I can't run into recovery mode, I can only run fastboot commands. Whenever I try to do something (install CWM, fastboot recovery) I get the message "Command not allowed" and I think it's because the bootloader is not unlocked.
The only tutorials I find to unlock are using abd commands, but since the phone is bricked I can only run fastboot ones.
Is there any way yo unlock it by using fastboot commands?
Thanks
Found a solution
Skylip said:
Hi,
My phone is bricked and it won't come off the splash screen. I can't run into recovery mode, I can only run fastboot commands. Whenever I try to do something (install CWM, fastboot recovery) I get the message "Command not allowed" and I think it's because the bootloader is not unlocked.
The only tutorials I find to unlock are using abd commands, but since the phone is bricked I can only run fastboot ones.
Is there any way yo unlock it by using fastboot commands?
Thanks
Click to expand...
Click to collapse
For those who may have the same problem, this solution worked for me: modaco.com/topic/355873-guidepossibly-a-new-rom-downgrade-upgrade-tool-found/.
Thanks
Skylip said:
For those who may have the same problem, this solution worked for me: modaco.com/topic/355873-guidepossibly-a-new-rom-downgrade-upgrade-tool-found/.
Thanks
Click to expand...
Click to collapse
Hi.
But a question that I think will be important... What have you done to get the bricked phone? Because if it was for a bad upgrade... there are many ways to correct it. But it is important to know how it has been.
So, the backlight crapped out on my device after being a bit spotty (would come back after pressing around on the phone a bit). I'm thankfully still within the warranty period, but I'm S-OFF, bootloader's unlocked, and I'm running Sense 5. I'd like to minimize the chances of having my warranty invalidated for taking the bootloader unlock and everything, but it's quite difficult to do so without a screen to look at.
RUU'ing and switching back to CWS__001 should be easy as pie with fastboot, but I'm not sure how to relock the bootloader without the "relocked" tag and return to S-ON without flashing zips in recovery. I can't really adb sideload because I don't know TWRP's UI well enough to navigate around without seeing where all the UI elements are. Perhaps someone could guide me through navigation.
Lastly, I can't really verify visually whether or not I have TAMPERED, RELOCKED, or S-OFF, so is there any way to check all three via fastboot/adb?
To change it so that it's says ***LOCKED*** you can use the customize hboot tool here and make a custom plug hboot file http://forum.xda-developers.com/showthread.php?t=2156368 There is a fastboot comand that will basically read off the bootloader to you, fastboot get... Something. Exad knows this command, so he could tell you.
RollTribe said:
To change it so that it's says ***LOCKED*** you can use the customize hboot tool here and make a custom plug hboot file http://forum.xda-developers.com/showthread.php?t=2156368 There is a fastboot comand that will basically read off the bootloader to you, fastboot get... Something. Exad knows this command, so he could tell you.
Click to expand...
Click to collapse
I think it's
fastboot getvar all
doesn't show if it's locked or not though..
If you run an RUU
then use the Locked spoofer
then fastboot oem writesecureflag 3
You should be just fine.
So that's 5 instances where the backlight/display has stopped working for no apparent reason? I'm thinking it may HTCs fault and not the user..
Sent from my Nexus 4
I have owned this phone for about 5-6 months now and have never unlocked the bootloader. I know I probably should of done that when I got it but for some reason I have been able to flash TWRP, Root the phone, and install custom roms without wiping the phone no problem. I am currently on Paranoid Android 4.6 Beta 6 and TWRP 2.8 but I wanted to go back to CM11S, and I thought maybe it's time that I unlock the bootloader. I have installed the correct drivers and when I type "fastboot oem unlock", the Command Prompt said "finished in 0.06 seconds", I then rebooted and nothing happens. I also tried a Toolkit to unlock it but that didn't do anything either. Can anyone help? I don't want to Hard Brick my phone.
Thanks
It sounds like your bootloader is already unlocked.
Try running
fastboot oem device-info
to see what it says. Post your results here and somebody should be able to help you.
The right command is:
Code:
fastboot oem device-info
Transmitted via Bacon
check this
Matt7262 said:
I have owned this phone for about 5-6 months now and have never unlocked the bootloader. I know I probably should of done that when I got it but for some reason I have been able to flash TWRP, Root the phone, and install custom roms without wiping the phone no problem. I am currently on Paranoid Android 4.6 Beta 6 and TWRP 2.8 but I wanted to go back to CM11S, and I thought maybe it's time that I unlock the bootloader. I have installed the correct drivers and when I type "fastboot oem unlock", the Command Prompt said "finished in 0.06 seconds", I then rebooted and nothing happens. I also tried a Toolkit to unlock it but that didn't do anything either. Can anyone help? I don't want to Hard Brick my phone.
Thanks
Click to expand...
Click to collapse
hello ..
i have oneplus 64 that the Tampered was true and unlock false.
i have original recovery . that i cant run not signed zip
i tried everything even install coloros ( and its failed)
finaly after alot of hours the soultion very simple
1.install throw adb sideload the signed rom ... https://www.androidfilehost.com/?fid=95747613655046106
2. its take you to factory rom
3. after that u can unlock your oneplus with fastboot oem unlock
thanks
timmaaa said:
The right command is:
Code:
fastboot oem device-info
Click to expand...
Click to collapse
Thanks, edited to fix.
I have a nexus 5 that keeps bootlooping, I can get into recovery and bootloader but when I run the fastboot command to unlock the bootloader it shows unlocked but as soon as I restart the phone it shows that it's locked.
I've tried unlocking and flashing but flashing things via fastboot doesn't take any effect.
I was wondering if there is any way to get the phone running or if its dead.
Thanks
mafiaboy01 said:
I have a nexus 5 that keeps bootlooping, I can get into recovery and bootloader but when I run the fastboot command to unlock the bootloader it shows unlocked but as soon as I restart the phone it shows that it's locked.
I've tried unlocking and flashing but flashing things via fastboot doesn't take any effect.
I was wondering if there is any way to get the phone running or if its dead.
Thanks
Click to expand...
Click to collapse
Sounds to me like your emmc is fried. You're gonna have to RMA it, unfortunately.
_MetalHead_ said:
Sounds to me like your emmc is fried. You're gonna have to RMA it, unfortunately.
Click to expand...
Click to collapse
That's what I figured, its out of warranty so no sense in sending it in.
I kept my phone on charge for a few mins and when I came back to unplug, it was stuck on google screen. tried turning off the device or restarting it but nothing works. The phone was extremely hot. My phone is completely factory stock. the bootloader is locked too. how to recover it now ? please help.
i tried entering recovery mode but as soon as i select recovery it gets back to google logo screen again.
right now i have kept the phone in freezer now.
my bootloader is locked .. can i still unlock it and flash factory image ?
help ?
not a single reply ? bump...
Are you able to communicate with the device using fastboot?
Try flashing the stock images via fastboot
You won't need an unlocked bootloader for this
post-mortem said:
Are you able to communicate with the device using fastboot?
Click to expand...
Click to collapse
yes im able to communicate with the device through fastboot. but my bootloader is locked.
wahur1 said:
yes im able to communicate with the device through fastboot. but my bootloader is locked.
Click to expand...
Click to collapse
Try the instructions at the top of the page here https://developers.google.com/android/images
It may work without unlocking the bootloader.
post-mortem said:
Try the instructions at the top of the page here https://developers.google.com/android/images
It may work without unlocking the bootloader.
Click to expand...
Click to collapse
whatever command i use it says OEM unlock is not allowed.
Just throwing out ideas that you may have already tried. If I understand right you cannot get into recovery which eliminates trying to sideload the stock image. Your bootloader is locked and it will not let you unlock so booting into TWRP is out of the question. Are you just wanting your phone operational again? Have you tried wiping/factory resetting with fastboot commands? i.e. fastboot erase userdata or fastboot format userdata.
wahur1 said:
whatever command i use it says OEM unlock is not allowed.
Click to expand...
Click to collapse
Have you tried flashing without unlocking the bootloader?
post-mortem said:
Have you tried flashing without unlocking the bootloader?
Click to expand...
Click to collapse
yes i have tried flashing by giving the fastboot command "flash-all.bat" it starts flashing and it stops in the initial stage by giving error " restarting bootloader" then I get 2nd error " bootloader locked" and process repeats again
toasterboy1 said:
Just throwing out ideas that you may have already tried. If I understand right you cannot get into recovery which eliminates trying to sideload the stock image. Your bootloader is locked and it will not let you unlock so booting into TWRP is out of the question. Are you just wanting your phone operational again? Have you tried wiping/factory resetting with fastboot commands? i.e. fastboot erase userdata or fastboot format userdata.
Click to expand...
Click to collapse
both command not working .. same bootloader locked message.
error message " Please unlock the device to activate this command"
anyone else can help ?
I would contact Google customer support. Even though my phone was out of warranty and I was not the original buyer (bought in eBay), they were willing to make a one-time exception for an RMA. I didn't use it because my phone is rooted and I was afraid of being charged for any repairs. As long as your phone is stock and unrooted, you have a chance. Just say that you think you have a hardware failure and while you understand that they are in no obligation to help, you would appreciate anything they can do.
Sent from my Pixel XL using Tapatalk