Develop Bugs

[Q] Can't get in Fastboot or Flash mode

Hi
i've got a little Problem with my Sony Ericsson Xperia Play.
I can't get anymore into the fastboot or the flashmode.
if i press the back button while i plug in the usb cable the led on the top is green for about a half a second and then it boots the normal system. the same is with the search button. there the led is blue for half a second and then it boots normal.
i also tried to reboot into fastboot mode via ADB but then it only boots into the cwm recovery system.
so how can i fix this problem?
or is there a other way to flash a new kernel?
would be nice if you could help me.
and sorry for my bad english skills

try another cable, or another usb port on pc

I tried different USB ports. I even tried differend PC's
I only have one cable but i've ordered another one. But I don't think that the cable is the problem because moving files and using adb works with it.

Hi if you can get into cwm can you boot into fastboot from there? On doomlords kernel you can boot from there not sure about cwm:fingers-crossed:

nope. i searched it several times and there is no option to go to fastboot mode

To get into fastboot mode your bootloader needs to be unlocked. Fastboot mode is disabled on locked bootloaders. But you do have acces to flash mode.

aofMoh ADAMS
My bootloader is unlocked.
And some times ago i was able to flash new kernels.
Or is it possible that a new kernel relock the bootloader?
edit:
sorry for the strange title. i typed the captcha in the wrong text box xD

ChrisOboe said:
My bootloader is unlocked.
And some times ago i was able to flash new kernels.
Or is it possible that a new kernel relock the bootloader?
edit:
sorry for the strange title. i typed the captcha in the wrong text box xD
Click to expand...
Click to collapse
not that i know of unless the kernel was built to lock the device which i dont think it is so i think you OTA-bricked your device

[Q] Kindle Fire Bricked??(Hopefully not)....

i had rooted my kindle with firefirefire by KFU and had accidentally erased the SDCARD, so i found a new gingerbread kindle fire OS.zip online no problem and installed it, had it up and working again, all fine and dandy.
Then everytime i booted it up it would always come up with the whole blue "kindle fire" and "press power button for boot options" screen and i decided i didnt want twrp on my kindle anymore and that i wanted to return it back to factory condition. so i looked up on youtube how to de-root you kindle fire and i referenced myself with this video:
http://www.youtube.com/watch?v=AzbmxV45x10
i downloaded the update.zip and flashed my kindle with twrp (just like it said) and everything went fine. however the next time i turned it on (well when it turned itself on after the update) it just got stuck in a boot loop... it will display the factory setting "kindle fire" with the red color, not twrp's blue "kindle fire", then the screen will go brighter like it is about to load the unlock screen, then it just goes back to the darker screen (all whilst displaying the kindle fire logo) then it will shut off. after about 5-10 seconds of being off, it will boot itself back on and repeat the same cycle again.
i have tried to hook it up to the computer, but it only shows up in "My Computer" for about a millisecond. thought maybe it was just my computer that couldnt load fast, so i tried a different computer, same thing.
i have tried holding the power button down for anywhere between 20- 60 seconds, still nothing.
i have tried opening the KFU and going to install firefirefire and letting it load to the point of <waiting for device> and then plugging in my device, still nothing.
i am extremely grateful of any ideas and solutions you guys/girls can offer and help me out. i loved my kindle fire quite dearly and used it everyday. i am willing to accept the fact that i have a $200 brick, but will do just about anything to fix. please help http://forum.xda-developers.com/images/smilies/frown.gif

Have you tried to factory reset it? Very likely you will need to purchase a factory cable to force it into fastboot in order to resend twrp and fff to the device so that you can flash a new rom.

James.Whaton said:
it will display the factory setting "kindle fire" with the red color...then the screen will go brighter like it is about to load the unlock screen, then it just goes back to the darker screen (all whilst displaying the kindle fire logo).
Click to expand...
Click to collapse
Yep, you definitely need a factory cable. You have to wipe both system and factory reset when reverting back to stock or...well...this will happen. Keep your device turned off until you get it because it probably won't charge in that state, and you don't ALSO want to be dealing with a dead battery.

soupmagnet said:
Yep, you definitely need a factory cable. You have to wipe both system and factory reset when reverting back to stock or...well...this will happen. Keep your device turned off until you get it because it probably won't charge in that state, and you don't ALSO want to be dealing with a dead battery.
Click to expand...
Click to collapse
i do have a rocketfish cable that is a step up from the factory cable, always worked in the past whenever i used it for the kindle, i can get it to charge, just not stay connected to my computer... i dont quite know why this happened because all i did was install that update... not quite sure why it did this... any ideas on how to get it back to normal?

Thepooch said:
Have you tried to factory reset it? Very likely you will need to purchase a factory cable to force it into fastboot in order to resend twrp and fff to the device so that you can flash a new rom.
Click to expand...
Click to collapse
how would i factory reset it? i cant get it hooked up to the computer and twrp is completely off the system (or so i would seem) i have a rocketfish cable that is a higher quality then the factory cable or are you talking about a specialized cable that does something other than hook it up to the computer?

James.Whaton said:
how would i factory reset it? i cant get it hooked up to the computer and twrp is completely off the system (or so i would seem) i have a rocketfish cable that is a higher quality then the factory cable or are you talking about a specialized cable that does something other than hook it up to the computer?
Click to expand...
Click to collapse
You wipe system and factory reset BEFORE you revert to stock. Now you need to use the factory cable to get into fastboot and reinstall TWRP so you can go back and do it the right way.
As for the computer not detecting the device...see my post here:
http://forum.xda-developers.com/showthread.php?t=2088864

soupmagnet said:
You wipe system and factory reset BEFORE you revert to stock. Now you need to use the factory cable to get into fastboot and reinstall TWRP so you can go back and do it the right way.
As for the computer not detecting the device...see my post here:
http://forum.xda-developers.com/showthread.php?t=2088864
Click to expand...
Click to collapse
my computer will detect the device but only for a second, because it never fully loads it is only in the booting mode.my computer cant see it due to the kindle not being available. where would i purchase a foctory cable becuse by the way you guys are talking about it it sounds like the cable isnt just a cable but it can make it boot differently... the cable i have now connects it to the computer very easily and just fine, and the only reason that it isnt working now is because the kindle is in a boot loop.

http://forum.xda-developers.com/showthread.php?t=1392693 post 9 James the factory cable will force the device into fastboot so you can use kfu to resend fff and twrp to the device in order to do a full wipe and flash a new system.

forgive me for being curious, but how exactly does this factory cable work? i know that it isnt you who is making them, but i would hope that if you are suggesting to use it you would understand how it works... i have my cable here so why go buy a new one instead of just doing it myself? it seems like it is just a simple soldering job, which i could handle. after a little research it looks like i need to connect pin 1 to pin 4 which wouldnt be all that difficult to do by myself.
could anyone tell me how i could simply create on myself. yes ive read this post:
http://forum.xda-developers.com/showthread.php?t=1392693
but they never quite explain in detail what i need to do to make one. i watched a couple videos on youtube to figurre out what i had to do, but i still would like a more professional opinion as to what i need to do and as to how it works. thank you

lost OS
i have done every thing to the T to get OS back. when i down load the new OS and place it in the kindle updates folder it does not show up in TWRP when I unmount the KF.
suggestions> I have been beating my head on this since some screwball decided to pay with it.

[Q] Kindle Fire on a Constant 30 sec Reboot w/NO recovery & NO Permissions

I cannot seem to get my kindle fire unbricked despite reading and trying all solutions I could find and/or think of. I've tried KFU, Kindle Fire Debricker/Unbricker, followed various tutorials, and even made my own factory cable all to no avail yet. My Kindle simply keeps rebooting itself into the stock OS 6.3.1 of amazons about every 30 seconds +/-. Nothing I do can/will change that. When it starts up it shows the kindle fire bootloader then onto the main "Home" screen where various notices come up stating that basically everything is NOT working and they've all failed miserably and horribly. Then onto the next reboot. There is no longer any sort of recovery as far as I can tell. I cant get it to respond to any sort of fastboot anythings. On the positive side I do have the drivers loaded and can use adb with it at will, including adb shell. But all that is just about pointless as any command I try and enter, it simply responds with something about me not having any rights to do anything. I'm pretty sure I know what happened, far as I can tell I was in TWRP recovery when I tried to flash the stock firmware from there and everything just failed. Anyhow, if anyone has any idea what so ever on what to try or where to look for an answer, I'd be eternally grateful. Or if any other info is wanted, just let me know. Thanks all for any advice given ahead of time.

http://forum.xda-developers.com/showthread.php?t=2120816
"That's a special kind of stupid. The kind that makes me laugh."

24861 said:
I cannot seem to get my kindle fire unbricked despite reading and trying all solutions I could find and/or think of.....On the positive side I do have the drivers loaded and can use adb with it at will, including adb shell. But all that is just about pointless as any command I try and enter, it simply responds with something about me not having any rights to do anything. I'm pretty sure I know what happened
Click to expand...
Click to collapse
Try right clicking and select run as administrator.
Sent from my Amazon Kindle Fire using Tapatalk HD

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2120816
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Not to be rude, but..... Any chance on any actual help? Like maybe what to do? mLike I previously said I already have a factory cable but have gotten no where with that. Thank you

24861 said:
Not to be rude, but..... Any chance on any actual help? Like maybe what to do? mLike I previously said I already have a factory cable but have gotten no where with that. Thank you
Click to expand...
Click to collapse
Sure, but I need to know a few things first...
Do you understand what the factory cable is for? Do you know how to use it?
Do you know what fastboot is and how to use it? If so, do you know how to use it to install recovery?
Do you have a general idea of what you need to accomplish to fix your KF? (see the link provided)
"That's a special kind of stupid. The kind that makes me laugh"

soupmagnet said:
Sure, but I need to know a few things first...
Do you understand what the factory cable is for? Do you know how to use it?
Do you know what fastboot is and how to use it? If so, do you know how to use it to install recovery?
Do you have a general idea of what you need to accomplish to fix your KF? (see the link provided)
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
In general....... yes.
Factory cable is simply to put it in fastboot (although I dont know that it does on mine).
I do know what fastboot is and can type in the needed commands if you'd be willing to tell me, though I know a couple.
And yes, Im looking to install TWRP and then flash a stock rom and stock recovery.... I believe.
Then again, all that is probably wrong, ergo why I ask you sir.
Thank you

24861 said:
In general....... yes.
Factory cable is simply to put it in fastboot (although I dont know that it does on mine).
I do know what fastboot is and can type in the needed commands if you'd be willing to tell me, though I know a couple.
And yes, Im looking to install TWRP and then flash a stock rom and stock recovery.... I believe.
Then again, all that is probably wrong, ergo why I ask you sir.
Thank you
Click to expand...
Click to collapse
Okay...
When you plug your powered off Kinlde Fire into the computer with the factory able, it should boot directly to fastboot. Meaning, it will stay at a bright Kindle Fire logo and not go dim or flash.
Anything outside of that would make me wonder if your factory cable is defective (probably not likely) or your battery is near dead. The 30 second reboot is a good indicator of the latter, although that particular situation usually results in a much faster reboot loop (5-10 seconds).
Plug your device into your stock charger and immediately hold the power button down until it shuts off. Then let it charge for a while then try again later.

soupmagnet said:
Okay...
When you plug your powered off Kinlde Fire into the computer with the factory able, it should boot directly to fastboot. Meaning, it will stay at a bright Kindle Fire logo and not go dim or flash.
Anything outside of that would make me wonder if your factory cable is defective (probably not likely) or your battery is near dead. The 30 second reboot is a good indicator of the latter, although that particular situation usually results in a much faster reboot loop (5-10 seconds).
Plug your device into your stock charger and immediately hold the power button down until it shuts off. Then let it charge for a while then try again later.
Click to expand...
Click to collapse
Okay. So far so good. Is doing just what you said, except for I evidently have no fastboot driver installed. Plus it doesnt recognize that the fire is plugged in (in fastboot mode) inside the device manager. So....? Is there a specific driver (fastboot driver) that I need to load (and do you have it?) and how do I get the fire to atleast become recognized?
Thanks again bud

That may not necessarily be the case. What color is your Kindle Fire logo?
"That's a special kind of stupid. The kind that makes me laugh"

soupmagnet said:
That may not necessarily be the case. What color is your Kindle Fire logo?
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
Its white and orange. Although I believe my current issue is that it is stuck in fastboot (4002) mode. Even though it still reboots into normal mode, it remains stuck in fastboot. And I am unsure as to how to get it back as nothing will recognize it, so no drivers will ever install. So I am currently trying to let it run dry of juice in hopes it will reset when its dead. Any ideas?

Don't let the battery die!
I'll tell you what you need to do later when I have more time. In the meantime, keep it turned off.
"That's a special kind of stupid. The kind that makes me laugh"

Draining Is never a good idea. It`s very common for the stock bootloader to be difficult to detect even more so now after there recent update in the past few months, because Amazon tampered with the bootloader enough to cause some people issues.

soupmagnet said:
Don't let the battery die!
I'll tell you what you need to do later when I have more time. In the meantime, keep it turned off.
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
okay. Waiting on you. Thanks

Thepooch said:
Draining Is never a good idea. It`s very common for the stock bootloader to be difficult to detect even more so now after there recent update in the past few months, because Amazon tampered with the bootloader enough to cause some people issues.
Click to expand...
Click to collapse
Just had stock bootloader drivers all installed and what not before I started in with the factory cable (thereby putting it in fastboot (4002) mode.

24861 said:
Just had stock bootloader drivers all installed and what not before I started in with the factory cable (thereby putting it in fastboot (4002) mode.
Click to expand...
Click to collapse
Agreed it`s still normal to be undetected by kfu how does it show in device manager?

24861 said:
Just had stock bootloader drivers all installed and what not before I started in with the factory cable (thereby putting it in fastboot (4002) mode.
Click to expand...
Click to collapse
So far everything seems to be working the way it's supposed to.
Using the factory cable to get into fastboot, type the following command and hit enter:
Code:
fastboot getvar product
When you see "waiting for device", hold the power button to turn the device off. Unplug then replug the factory cable to boot the device back into fastboot. When it boots, you should see an output of "kindle" in the command window.
If that works, do the same thing for the commands to install recovery and change the bootmode.
If you really want to go back to stock, do what you did previously, only this time be sure to do a "factory reset" before installing the update.zip.

soupmagnet said:
So far everything seems to be working the way it's supposed to.
Using the factory cable to get into fastboot, type the following command and hit enter:
Code:
fastboot getvar product
When you see "waiting for device", hold the power button to turn the device off. Unplug then replug the factory cable to boot the device back into fastboot. When it boots, you should see an output of "kindle" in the command window.
If that works, do the same thing for the commands to install recovery and change the bootmode.
If you really want to go back to stock, do what you did previously, only this time be sure to do a "factory reset" before installing the update.zip.
Click to expand...
Click to collapse
Nothing doin' there champ......... just same old "waiting for device" followed to a tee, but nada. Anything else?

Make sure you're using a 2.0 usb port.

I assuredly am using a 2.0 USB port, but still nada. Anything else anybody? Please.................

So.... back to where I was (I had to switch PC's though). I can get adb running just fine. I can getshell even. But cant do much with as all permissions seem denied. And I have continuous access to the sd card as its always mounted it seems, even thru every restart. So...... what to do now?

[Q] Bootloop and not working Volume Rocker - Any Solution?

Hey Guys
I really could need a good Advise. In the past my USB-Port was broken, so i repaired it with a new one, anyway i wasnt careful enough - i pulled of the Volume-Rockers' Connector. There are no contacts left on the Mainboard, so i cant easily install some new Volume Rockers.
Well that wasnt a big Problem for me so far, i just used a Volume-Widget instead. But unfortunately my Device is now stucking within a Bootloop.
Due to the missing Volume-Rocker, i cant access Fastboot or Recovery. I tried to access the Device with the GNex-Toolkit but it wont let me install the Drivers, i guess the Driver crashes within the Bootloop. Letting the Device Boot while connected via USB, wont recognize it as ADB-Device.
I am owning a Galaxy S4 now, but i would like to repair the GNex, so that my Gilfriend might use it. Any chance to access Fastboot Mode or Recovery without the Volume Rockers on a Bootlooping Device?
I allready downloaded the OMAPFlash_tuna Package and managed it to install the OMAP 4440 Driver (it is giving me 2 Seconds to install them when i plug in the powered-off Device). After a few attempts the Omap-Flash Bat-File was running properly. But the Device is still stuck in its Bootloop. Any Advices would be really great.
Best regards

apsis said:
Hey Guys
I really could need a good Advise. In the past my USB-Port was broken, so i repaired it with a new one, anyway i wasnt careful enough - i pulled of the Volume-Rockers' Connector. There are no contacts left on the Mainboard, so i cant easily install some new Volume Rockers.
Well that wasnt a big Problem for me so far, i just used a Volume-Widget instead. But unfortunately my Device is now stucking within a Bootloop.
Due to the missing Volume-Rocker, i cant access Fastboot or Recovery. I tried to access the Device with the GNex-Toolkit but it wont let me install the Drivers, i guess the Driver crashes within the Bootloop. Letting the Device Boot while connected via USB, wont recognize it as ADB-Device.
I am owning a Galaxy S4 now, but i would like to repair the GNex, so that my Gilfriend might use it. Any chance to access Fastboot Mode or Recovery without the Volume Rockers on a Bootlooping Device?
I allready downloaded the OMAPFlash_tuna Package and managed it to install the OMAP 4440 Driver (it is giving me 2 Seconds to install them when i plug in the powered-off Device). After a few attempts the Omap-Flash Bat-File was running properly. But the Device is still stuck in its Bootloop. Any Advices would be really great.
Best regards
Click to expand...
Click to collapse
i dont see a way to boot into fastboot mode without volume keys or adb
i suggest to get a usb jig and flash stock via odin

samersh72 said:
i dont see a way to boot into fastboot mode without volume keys or adb
i suggest to get a usb jig and flash stock via odin
Click to expand...
Click to collapse
Thanks mate, i really appreciate your Help. I'm sorry that im just answering so late, but i was waiting for my USB jig to arrive. I didnt knew that there is this Option with the USB Jig, i just want to let you know that everything went well, and my Galaxy Nexus is finally back to life.
Thanks for your fast reponse :good

Need Some Clarifications

Hi all,
After reading many posts i got a little confused and i'm not getting any result. Please help.
What i want?: Flash stock rom and later consider rooting, and flashing haden or lineagos. (already found guidance but..)
The issue?: It doesn't get recognized through USB with my PC. (drivers installed, cable connected but...)
My questions? (correct me if wished):
1) In Odin mode (which i enter) is the usb port enabled by default? or it depends on the phone configuration.
2) In recovery mode i still cannot see the phone through the USB so is it open by default on stock recovery?
3) Finally can i flash stock rom i downloaded from sammobile through SD card? i found that to be my last resort but i think odin actual proper way or not?
I first thought it was the cable...since is not the original but it seems not be the case...which leads me to think its the phone's usb port....but with the cable i can charge the phone although i cannot see it through my PC.
So bottom line if the answer to my questions are that is always open (accesible through usb port) then it HAS to be the cable right?
If last quesiton is possible then i will conclude my searchings to be ended for now.
Thanks to all the posts within this tree.

Findings
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...

There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again

verdugon said:
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
Click to expand...
Click to collapse
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.

Light at the end of the tunnel!!!
PMFRTT said:
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
Click to expand...
Click to collapse
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks

Light at the end of the tunnel!!!
SnowFuhrer said:
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Click to expand...
Click to collapse
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.

verdugon said:
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
Click to expand...
Click to collapse
And to unlock the bootloader, just enable OEM unlock in the dev settings and it's ready to flash twrp. I remember when I got my Samsung and I was trying to fastboot unlock it lol.

Thanks to both of you! I will keep the thread on just in case...anyway may be it helps someone else.

verdugon said:
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Click to expand...
Click to collapse
Good luck! Let me know how it went.