Develop Bugs

Rebooting to fastboot on CM10.1?

Having a small issue with my device, and I could do with getting in to fastboot to troubleshoot.
I have TWRP installed along with a nightly version of CM10.1, When I try ADB reboot bootloader The device reboots, flashes the first bootscreen for a second(Orange and White Kindle Fire) and then shuts itself down.
Any suggestions that don't involve getting a fastboot cable? I can make one if I have too, but I would rather try and find out why it wont work this way.

Nvmd

So, you don't see the blue Kindle Fire logo at all?

I see the Orange and white, then the Blue and White, and then it boots, When I try and reboot to bootloader, I see the Orange and White, and then it shuts down.

Jackering said:
I see the Orange and white, then the Blue and White, and then it boots, When I try and reboot to bootloader, I see the Orange and White, and then it shuts down.
Click to expand...
Click to collapse
Why don't you use the volume button to access recovery?
Hashcode said:
TO ENTER RECOVERY:
Press the left volume button (volume up) while the logo is still YELLOW and keep pressing until the logo turns BLUE. Wait a moment and you should enter recovery.
Click to expand...
Click to collapse

I can enter recovery fine, I want to get in to Fastboot to test something.

Jackering said:
I can enter recovery fine, I want to get in to Fastboot to test something.
Click to expand...
Click to collapse
If your device boots into recovery, you can issue the "reboot bootloader" command from there
If you are able to get into fastboot from there, you know it's the nightly version of CM10.1 that is the problem and not the bootloader. If that's the case, install a different ROM.
[Edit:] For curiosity's sake, what "troubleshooting" are you expecting to do in fastboot?

soupmagnet said:
If your device boots into recovery, you can issue the "reboot bootloader" command from there
If you are able to get into fastboot from there, you know it's the nightly version of CM10.1 that is the problem and not the bootloader. If that's the case, install a different ROM.
[Edit:] For curiosity's sake, what "troubleshooting" are you expecting to do in fastboot?
Click to expand...
Click to collapse
From ADB on the device?
Edit; I get a message "Error: Command not found" or something like that trying to run it on the device.
I just wish to test a reboot to fastboot mode, thats all :good:
Edit2:
Just noticed that when in recovery, Windows Device Manager has an ! next to "Amazon KindleFire2" Yet, There is no ! once booted, Interesting.

Jackering said:
From ADB on the device?
Edit; I get a message "Error: Command not found" or something like that trying to run it on the device.
I just wish to test a reboot to fastboot mode, thats all :good:
Edit2:
Just noticed that when in recovery, Windows Device Manager has an ! next to "Amazon KindleFire2" Yet, There is no ! once booted, Interesting.
Click to expand...
Click to collapse
Oh nevermind, I was wrong. Typically you would use 'idme' to change the bootmode then reboot, but 'idme' isn't included in our version of TWRP. I thought maybe it could be pushed to recovery then executed, but I keep getting a "Segmentation fault" error on this version when trying it on my end. I'm not sure what's causing that other than perhaps this version wasn't made with 'idme' in mind, but that's purely speculation on my part. If you had any other device than a Kindle Fire 2 you wouldn't have any problem accessing fastboot, but as it stands now, I think your only option (to get into fastboot) is to acquire a factory cable or install a different ROM.
But even with fastboot, that's still not addressing your original problem. The fastboot binary is really only useful for overwrite\ing partitions and changing the bootmode. Whatever your problem is, it will likely be fixed by installing a non-nightly version of CM10.1 (nightly = not so stable).
As for your device manager, later versions of TWRP have different hardware IDs than that of the stock OS. Just add the hardware ID to your 'android_winusb.inf' and reinstall it.

soupmagnet said:
Why don't you use the volume button to access recovery?
Click to expand...
Click to collapse
Btw- we don't have volume buttons. Drives me nuts
Sent from my SGH-I727 using Tapatalk 2

Stuck in bootloop. Power button not working.

Before I give up and get a new phone, I was hoping someone had a solution.
Little backstory on how the bootloop occurred, I flashed the latest Cyanogenmod 10.2 and everything seemed to be working fine minus the Google apps and SU. I realized that I forgot to flash the GAPPs also and was trying to figure out how I should boot into recovery (completely forgetting about adb). A friend said he could "fix" it and flashed a previous Cyan, leading me to the bootloop.
My power button has not worked for months which has only been a hinderance really, as I can still function with the volume rocker and gestures to turn the screen off and on.
But this is the one special case I was worried about where I would need my power button to boot into fastboot or recovery, and I am not able to.
I can get the phone on via plugging into computer, battery pull then put battery back in and wait, but that only leads to the bootloop.
Any help would be appreciated as I have tried anything I could think of as adb won't work in the bootloop for me.
Thanks.

AugustJuly said:
Before I give up and get a new phone, I was hoping someone had a solution.
Little backstory on how the bootloop occurred, I flashed the latest Cyanogenmod 10.2 and everything seemed to be working fine minus the Google apps and SU. I realized that I forgot to flash the GAPPs also and was trying to figure out how I should boot into recovery (completely forgetting about adb). A friend said he could "fix" it and flashed a previous Cyan, leading me to the bootloop.
My power button has not worked for months which has only been a hinderance really, as I can still function with the volume rocker and gestures to turn the screen off and on.
But this is the one special case I was worried about where I would need my power button to boot into fastboot or recovery, and I am not able to.
I can get the phone on via plugging into computer, battery pull then put battery back in and wait, but that only leads to the bootloop.
Any help would be appreciated as I have tried anything I could think of as adb won't work in the bootloop for me.
Thanks.
Click to expand...
Click to collapse
I don't know if it works but you can try to push vol up+vol down and plugging it in to a computer. If it boots as you say it may be boot into fastboot..
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
I don't know if it works but you can try to push vol up+vol down and plugging it in to a computer. If it boots as you say it may be boot into fastboot..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Sadly, that's one of the first things I tried.
Thanks for the idea though.

Did I ruin my phone?

Was trying to switch from TWRP to CWM (having trouble with TWRP installing CM nightlies). I installed the latest CWM via fastboot. Seemed to load OK, but when I tried to start up the recovery, it just rebooted after showing 'Entering Recovery...' in pink at the top.
Now I'm really stuck. No matter what I do, the phone starts up, shows Entering Recovery at the top, and then shuts down. I cannot enter the bootloader. I cannot start up the phone into the ROM (which is a TikTak ROM that was working fine). Basically, I'm unable to do anything.
When the phone is plugged in, no orange charge light comes on. Vol Down + Power doesn't work. Vol Up + Power doesn't work. Either way, the phone tries to enter recovery, then shuts down.
Is there anything else I can try? Is this phone bricked?

What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uzephi said:
What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...

mobilemedic20 said:
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...
Click to expand...
Click to collapse
If you can't get a charge light while it is off, DO NOT let it die! It will not charge while dead. When it is booting, can you do adb or fastboot commands from your PC? If so, try:
ADB/fastboot reboot bootloader
Sent from my HTC6500LVWBLU using XDA Free mobile app

Usually, the command: fastboot erase cache
Will resolve such issues, though it doesn't always work, depends on what's causing the actual issue.
But that is what I would suggest trying from fastboot.

Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.

mobilemedic20 said:
Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.
Click to expand...
Click to collapse
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.

santod040 said:
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.
Click to expand...
Click to collapse
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.

mobilemedic20 said:
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.
Click to expand...
Click to collapse
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.

santod040 said:
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.
Click to expand...
Click to collapse
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.

mobilemedic20 said:
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.
Click to expand...
Click to collapse
Well that's too bad. Sorry to hear you're having these issues.
I noticed in your first post in this thread, you said you did this:
fastboot flash recovery cwm.zip
Was the file actually a zip?
It should have been a .img file.
Just trying to figure out what happened, as it could help in finding a resolution.
As it stands right now, there is nothing really to go off of.

Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?

mobilemedic20 said:
Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?
Click to expand...
Click to collapse
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app

Uzephi said:
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
'Send it in for JTAG'... sorry, what does this mean?
I'm also going to try bringing it to Verizon and claiming ignorance to see if I can get a warranty replacement. What's the downside, right?

adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?

synisterwolf said:
adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?
Click to expand...
Click to collapse
Appreciate the suggestion but have no idea how to proceed with this. Read that link, even more clueless.

[Q] SM-T700 Frozen in stock android recovery

Hi there. Today I bought a Samsung Galaxy Tab S 8.4" (SM-T700)
It's been awhile since I played around with rooting and installing custom firmware and it's the first time that I've owned a non Nexus Samsung device. I wanted to Root and install a custom firmware and started with downloading the Unified Toolkit stickied in this section of the forums. Everything was going fine, I got the samsung drivers installed and pushed TWRP to the tablet over ADB. After pushing the files over instead of booting into TWRP it booted into the stock Android recovery. I read that some devices automatically revert to the stock recovery every time you reboot. While I was in the stock recovery I accidentally wen't into the ADB sideload section when I tried to reboot the device. Now I'm completely stuck on this screen. I've tried all of the button combinations (Power+Vol up+Home/Power+Vol down+Home) and nothing happens. Right now I just have it sitting waiting for the battery to die.
http://i.imgur.com/k2hR4EH.jpg
Trying to reboot the device into anything (recovery, download mode, android OS) from the Skipsoft toolkit just gives me an "Error: closed" error message in the cmd window. Trying to reflash the stock recovery again or push any files over doesn't work. It will just stall at "Waiting for USB debugging to be enabled" since I can't reboot into the OS.
Is there anything I can do to power off or reset the device short of waiting for the battery to die or prying it open and disconnecting the battery? It's frustrating to not be able to use my brand new device.

How about trying power, home, vol up and down buttons for 10 seconds at the same time? If not just let it die. Next time use odin to flash twrp

DUHAsianSKILLZ said:
How about trying power, home, vol up and down buttons for 10 seconds at the same time? If not just let it die. Next time use odin to flash twrp
Click to expand...
Click to collapse
Ding ding ding! I tried it so many times and it didn't work, but I guess I didn't hold long enough when I tried it since it wasn't one of the combinations I saw mentioned. Thank you very much.
Odin is what the toolkit was using to flash TWRP. I'll give it another go tomorrow when I'm not as tired.

eShrooms said:
Ding ding ding! I tried it so many times and it didn't work, but I guess I didn't hold long enough when I tried it since it wasn't one of the combinations I saw mentioned. Thank you very much.
Odin is what the toolkit was using to flash TWRP. I'll give it another go tomorrow when I'm not as tired.
Click to expand...
Click to collapse
Glad it worked! Umm try unticking autoreboot next time in odin and reboot manually on the combo keys I mentioned. That should force it not to revert back to stock recovery.

eShrooms said:
Hi there. Today I bought a Samsung Galaxy Tab S 8.4" (SM-T700)
It's been awhile since I played around with rooting and installing custom firmware and it's the first time that I've owned a non Nexus Samsung device. I wanted to Root and install a custom firmware and started with downloading the Unified Toolkit stickied in this section of the forums. Everything was going fine, I got the samsung drivers installed and pushed TWRP to the tablet over ADB. After pushing the files over instead of booting into TWRP it booted into the stock Android recovery. I read that some devices automatically revert to the stock recovery every time you reboot. While I was in the stock recovery I accidentally wen't into the ADB sideload section when I tried to reboot the device. Now I'm completely stuck on this screen. I've tried all of the button combinations (Power+Vol up+Home/Power+Vol down+Home) and nothing happens. Right now I just have it sitting waiting for the battery to die.
http://i.imgur.com/k2hR4EH.jpg
Trying to reboot the device into anything (recovery, download mode, android OS) from the Skipsoft toolkit just gives me an "Error: closed" error message in the cmd window. Trying to reflash the stock recovery again or push any files over doesn't work. It will just stall at "Waiting for USB debugging to be enabled" since I can't reboot into the OS.
Is there anything I can do to power off or reset the device short of waiting for the battery to die or prying it open and disconnecting the battery? It's frustrating to not be able to use my brand new device.
Click to expand...
Click to collapse
Press only 2 buttons few seconds for restart: Power and Vol ume -
Regards

HTC One M8 (Bricked?) PLEASE HELP!

Hi there,
So recently I just tried rooting my HTC One M8, with the All-In-One tool kit. It was successful, I was messing around with it for a while, removing bloat wear, ect. Then I figured out about custom roms, and heard about CyanMod11. It turns out that it couldn't read my sim card for whatever reason, but it still worked and loaded up. Then, I tried Android Revolution. THAT one worked flawlessly, besides the fact that I couldn't take screen shots for whatever reason. I should of just left it there. Here's where things go wrong. Then, I tried ViperOneM8. After that, it failed to load up and is now in a endless boot loop. I can't get into fast boot either. However, one time I somehow did manage to get into fast boot, but I didn't see the "recovery" option anymore. So... I'm out of ideas here. I'm really worried I bricked my device for good. My device powers on and everything, it just won't load up any OS, and I can't get into fastboot/recovery. Why I'm mainly worried is I failed to create a back up also. I'm running out of ideas here, and if ANYONE could help me that would be great.

RadicalMushroom said:
Hi there,
So recently I just tried rooting my HTC One M8, with the All-In-One tool kit. It was successful, I was messing around with it for a while, removing bloat wear, ect. Then I figured out about custom roms, and heard about CyanMod11. It turns out that it couldn't read my sim card for whatever reason, but it still worked and loaded up. Then, I tried Android Revolution. THAT one worked flawlessly, besides the fact that I couldn't take screen shots for whatever reason. I should of just left it there. Here's where things go wrong. Then, I tried ViperOneM8. After that, it failed to load up and is now in a endless boot loop. I can't get into fast boot either. However, one time I somehow did manage to get into fast boot, but I didn't see the "recovery" option anymore. So... I'm out of ideas here. I'm really worried I bricked my device for good. My device powers on and everything, it just won't load up any OS, and I can't get into fastboot/recovery. Why I'm mainly worried is I failed to create a back up also. I'm running out of ideas here, and if ANYONE could help me that would be great.
Click to expand...
Click to collapse
first you posted in the wrong forum this goes in Q&A
second what do you mean it won't go into fastboot / recovery ? what happens when your in the bootloader ?
I need the results of fastboot getvar all to determine what files you need to fix your phone ( not you serial no. or IMEI)
most likely your on an older firmware and you have s-on and the Rom you flashed requires s-off and the latest firmware

Gah sorry, I find this forum layout kind of confusing. So this is another problem. I cannot access "getvar", it just says device offline, and I close that command prompt and then the next one just says "please wait," and nothing happens.
What I mean by it won't go into fast boot, is when I hit power + volume down it won't load anything. Here's a pic I found off Google, I can't get to this screen here.
http://img.wonderhowto.com/img/22/98/63533775104674/0/unlock-bootloader-root-your-htc-one-m8.w654.jpg

RadicalMushroom said:
Gah sorry, I find this forum layout kind of confusing. So this is another problem. I cannot access "getvar", it just says device offline, and I close that command prompt and then the next one just says "please wait," and nothing happens.
What I mean by it won't go into fast boot, is when I hit power + volume down it won't load anything. Here's a pic I found off Google, I can't get to this screen here.
http://img.wonderhowto.com/img/22/98/63533775104674/0/unlock-bootloader-root-your-htc-one-m8.w654.jpg
Click to expand...
Click to collapse
Easy way to get into boot loader
Turn on your phone
When it gets into bootloop
Press and hold power+vol up+vol down until screen goes off
As soon as that happens press and hold power+vol down
You'll be in boot loader
And I must say you are a major noob
Navigate to hboot using vol buttons then press power button to select, you'll find recovery
These are just 2 modes hboot and fastboot
From fast boot you can select hboot and vice versa
And also getvar will work ONLY when you're in fastboot mode
Hboot mode is used for accessing recovery

navid0308 said:
Easy way to get into boot loader
Turn on your phone
When it gets into bootloop
Press and hold power+vol up+vol down until screen goes off
As soon as that happens press and hold power+vol down
You'll be in boot loader
And I must say you are a major noob
Navigate to hboot using vol buttons then press power button to select, you'll find recovery
These are just 2 modes hboot and fastboot
From fast boot you can select hboot and vice versa
And also getvar will work ONLY when you're in fastboot mode
Hboot mode is used for accessing recovery
Click to expand...
Click to collapse
I fixed my HTC One M8! Followed some advice on another thread and I just reflashed my TWRP, then I flashed the ROM again and everything is going smooth now!