Related
Is there a file in the android system that, sort of like an autoexec.bat, lists what to do on startup? For example forcing the system into recovery or download on power on?
I flashed the latest Vibrant firmware and did so with the option to repartition, which Im now finding out was not the right way to flash this one.
Long story short, it didnt contain the dbdata directory information and now, I am unable to boot and unable to get to download. I still have ADB access, it just isnt responding to ADB reboot download, it just comes right back up booting into recovery to flash the last stage of odin before it starts up.
Is there a way to force the phone back into download mode or force it to stop rebooting into recovery?
Pull battery out and USB to use the hardware buttons to manually get into download mode?
P.S. wrong forum
Aren't there some apps that can do that? I do it manually but like you said its not working for you, p.s im downloading that firmware
Sent from my SGH-T959 using XDA App
iwillkillyou said:
Aren't there some apps that can do that? I do it manually but like you said its not working for you, p.s im downloading that firmware
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
OP said that he isn't able to boot so I believe he's stuck on the loadup to Android.
zephiK said:
Pull battery out and USB to use the hardware buttons to manually get into download mode?
P.S. wrong forum
Click to expand...
Click to collapse
Manual buttons arent seemingly working, so far ive tried every conceivable combination of vol up down and power, even if all I do is plug the phone in Im back in recovery before the battery turns green.
(ps. I know, but I had a billion percent better chance not getting a mouthbreather response, despite the definite chance of flame posts lol)
Viralblack said:
Manual buttons arent seemingly working, so far ive tried every conceivable combination of vol up down and power, even if all I do is plug the phone in Im back in recovery before the battery turns green.
(ps. I know, but I had a billion percent better chance not getting a mouthbreather response, despite the definite chance of flame posts lol)
Click to expand...
Click to collapse
Try every step here: http://forum.xda-developers.com/showthread.php?t=771247
Have you successfully gotten into Download mode with hardware buttons before? Or are you one of those vibrants with "locked download?"
I have a feeling mines locked, Ive never used the buttons to successfully get into download mode, just adb reboot download
EDIT: Tried the posts suggestions, problem is second I plug in the USB and the battery pops up it goes right to recovery. Even if im holding the buttons before hand.
Viralblack said:
I have a feeling mines locked, Ive never used the buttons to successfully get into download mode, just adb reboot download
EDIT: Tried the posts suggestions, problem is second I plug in the USB and the battery pops up it goes right to recovery. Even if im holding the buttons before hand.
Click to expand...
Click to collapse
x_x don't know what to tell you then. With locked hardware, you have to be really careful because if something goes wrong you cant manually get back in there. Do you have Clockwork Recovery? try restoring to a previous nandroid backup.
zephiK said:
x_x don't know what to tell you then. With locked hardware, you have to be really careful because if something goes wrong you cant manually get back in there. Do you have Clockwork Recovery? try restoring to a previous nandroid backup.
Click to expand...
Click to collapse
I was working with that a bit, but it just kept getting to datadata and being unable to wipe or flash to it due to the odin botch. I tried wiping it clean and it just wouldnt let me do that to reflash.
So now im stuck at the samsung recovery screen without the ability to get into clockwork or flash lol
This smells like 130 bucks for a new phone I think... brick number two >.>
Viralblack said:
I was working with that a bit, but it just kept getting to datadata and being unable to wipe or flash to it due to the odin botch. I tried wiping it clean and it just wouldnt let me do that to reflash.
So now im stuck at the samsung recovery screen without the ability to get into clockwork or flash lol
This smells like 130 bucks for a new phone I think... brick number two >.>
Click to expand...
Click to collapse
Why did you change update.zip? Update.zip should always lead to Clockwork :|
zephiK said:
Why did you change update.zip? Update.zip should always lead to Clockwork :|
Click to expand...
Click to collapse
I didnt! But when I was formatting and it failed to reapply the nandroid completely cause of the section it couldnt mount, now when I hit reinstall packages it just reboots. Same with shell, it just yells at me and tells me to die in a fire.
if you didnt figure this out, the way to fix it is to first flash WITH ODIN the original JVD firmware and check repartition, then flash the new one IN ODIN without the repartition box checked.
first update includes the dbdata that the phone is looking for.
Yeah, I figured it out now, but Odin is seriously the devil if your phone doesnt have the hardware buttons enabled.
Now heres a question, if I can still get into stock recovery... is there a way to like, you know, recover using the stock system? lol
BUT THE GOOD NEWS IS that Tmo is letting me warranty out my phone for free, shipping me a new one, and gave me a loner while I wait.
TMo for the win.
Viralblack said:
BUT THE GOOD NEWS IS that Tmo is letting me warranty out my phone for free, shipping me a new one, and gave me a loner while I wait.
TMo for the win.
Click to expand...
Click to collapse
lol looks like you and I are in the same boat man. Hardware lock FTMFL. I have never been able to get into download mode, or recovery mode with the hardware keys, only with adb reboot recovery/download and terminal emulator app with SU privs. I wish there was a jumper we could reset to unlock it haha that'd be the s*# son. Good old pentium 133 in the palm of the hands, but no . Atleast they are taking care of the people who don't do things properly.
I did the same thing and ended up with the same problem, but i was able to get in into download mode. When i would plug it in it would try to boot into recovery after the battery screen i would use the keys to make it boot to download mode instead of recovery, it was a *****, but i got it, though idk if there is another way for people with locked down phones.
I loaded the latest CM7 RC to my SD card, and selected it via ROM Manager to flash, and when the phone reboots, it hangs on the HTC screen.
Any ideas? Help!
I think the issue maybe related to the Clockwork recovery that was just updated, but I cannot tell. I did Flash the ROM a month ago before the ROM Manager and Clockwork recovery updates.
Hold volume down button and press and release power to get into recovery, reflash from there or restore a backup
Sent from my HTC Hero CDMA using XDA App
Thanks, but my phone freezes on the recovery option. I have gone in the HBoot and chosen recovery and it freezes.
Have you tried turning off your phone and then holding down home and pressing power? I usually find it better that way.
joetobey said:
Thanks, but my phone freezes on the recovery option. I have gone in the HBoot and chosen recovery and it freezes.
Click to expand...
Click to collapse
Sent from my HERO200 using XDA App
radrian92 said:
Have you tried turning off your phone and then holding down home and pressing power? I usually find it better that way.
Click to expand...
Click to collapse
That asks me to clear storage...do I really want to clear storage?
joetobey said:
That asks me to clear storage...do I really want to clear storage?
Click to expand...
Click to collapse
Don't hold the power button - just press and release it.
still frozen at the htc splash screen
When I go into HBoot I see this (or as close to it as I could read)
Loading....[HERCDIAG.zip]
no Image
Loading....[HERCDIA3.nbh]
no image or wrong image
Loading....[HERCDIA2.nbh]
no image or wrong image
Loading....[HERCDIAG.nbh]
no image or wrong image
Loading....[HERCIMG.zip]
no Image
Loading....[HERCIMG.nbh]
no image or wrong image
What does this mean?
I never saw you mention a wipe, so did you ? If its your first time flashing gingerbread you need to wipe. Go to aospCMod gingerbread first post and click the "readme", its a wiki with really good instruction.
sent from a series of tubes
I will give that a read tonight. That wouldn't explain why ROM Manager is not allowing me to boot into recovery though? Would the Wipe help with that?
I will read the Wiki (in case I am asking a question that is answered there)
I Flashed the ClockworkMod again, and now I can get into recovery. I think I should be good from here. Thanks!
Just an fyi, I always flash roms from recovery directly, not rom manager. Has always worked better that way in my experience.
Sent from my HERO200 using XDA App
OK, so I am not new to flashing ROM's, but I formatted system from recovery (storage and mounts) and was going to flash unleashed 1.1, but somehow I accidentally rebooted phone before flashing anything!
Now the phone only boots into the M dual core logo, and wont go any further. After a battery pull, I attempted to go into recovery by volume up/down and power button simultaneously, and choose recovery, but the phone goes to the exclamation point inside the triangle and wont boot into recovery.
What do I do?
There's a partial fxz that will reflash just the stock system partition. Find that and use it.
Sent from my DROID BIONIC using Tapatalk
I just started looking into the FXZ, and am downloading it right now. I dont see a partial file though. the whole one is huge! searching now....
I've pm'ed you
Sent from my DROID BIONIC using Tapatalk
OK, so this file must be it
http://forum.xda-developers.com/showpost.php?p=17560174&postcount=21
I guess this is relatively simple. Haven't had to use RSD, so will search for a tutorial. Hope this file will download from the coffee shop I am at in the next 30 minutes!
Easy. Pull battery. Put battery back in. Hold vol down button. Press the power button to get the black screen with white letters. Launch rsd pick the file you downloaded select uncompress and flash. Go have a cigarette or quick beer and it will be done.
I have done it way too many times by bricking my phone trying to edit services jar to get 1% battery increments although i may throw in the towel soon on that
Sent from my DROID BIONIC using XDA App
theproj said:
Easy. Pull battery. Put battery back in. Hold vol down button. Press the power button to get the black screen with white letters. Launch rsd pick the file you downloaded select uncompress and flash. Go have a cigarette or quick beer and it will be done.
I have done it way too many times by bricking my phone trying to edit services jar to get 1% battery increments although i may throw in the towel soon on that
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Geez, you were right on time with this. I was starting to stress because I couldnt get RSD to recognize the phone, and I have no idea how to open a command prompt in windows ( i know. Retarded)
THANK YOU (phone just booted up)
Glad to hear. Now root your phone (faq in the dev forum will help) set it all up how you want and make a nandroid backup for the next time you brick your phone.
Sent from my DROID BIONIC using XDA App
theproj said:
Glad to hear. Now root your phone (faq in the dev forum will help) set it all up how you want and make a nandroid backup for the next time you brick your phone.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Actually, was already rooted and had a back up, was gonna update from unleashed 1.0 to 1.1, and pulled a dumb A** mistake. First time since having a rooted D1, and Incredible that I have done this!
I love this forum and all its users!
I had the same problem FINALLY got it working.
Ok I might sound retarded, but I can not get this phone started. I root the one with one of the One-click programs then i went on to remove the bloatware, however I guess I removed the home launcher without installing another one from the market. Now the phone will not pass the screen that comes right after the big M. What do i do? can someone please help?
gkybjk said:
Ok I might sound retarded, but I can not get this phone started. I root the one with one of the One-click programs then i went on to remove the bloatware, however I guess I removed the home launcher without installing another one from the market. Now the phone will not pass the screen that comes right after the big M. What do i do? can someone please help?
Click to expand...
Click to collapse
You're gonna have to use RSD lite again
AP Fastboot Flash Mode (S)
Battery OK to Program
Transfer Mode : USB COnnected
I am stuck at this screen. Wont let me do anything! Anyone knows what I should do? Thanks
I swear I just saw a post last night that stated you could get into recovery by the following method.
pull the battery, put battery back in, hold down the volume up and down buttons while pressing the power button simultaneously. This should take you to the screen with exclamation mark inside triangle.
Next (this is the part where I get uncertain. Darn memory)
press the volume buttons simultaneously and it takes you to factory recovery? or volume down by itself. If you can get to recovery you can wipe cache/dalvik cache and system format under (mounts and storage), then re-flash the rom again.
But I am not certain about that, because I cant find it again, but it wont hurt to try.
If that doesnt work, you may have to do the following, but It would seem like that is extreme fix for just removing your launcher?
someone chime in here.
theproj said:
Easy. Pull battery. Put battery back in. Hold vol down button. Press the power button to get the black screen with white letters. Launch rsd pick the file you downloaded select uncompress and flash. Go have a cigarette or quick beer and it will be done.
I have done it way too many times by bricking my phone trying to edit services jar to get 1% battery increments although i may throw in the towel soon on that
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Thanks
I got it figured it out. I had to install fastboot images and flash them to phone by windows command prompt. Thanks everyone!
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
Are you running stock, or did you root and customize?
Try plugging it in to a computer. A lot of us are finding better results when you do. You may end up having to do more. But just being connected to a computer has helped in the past. Quick fix before you start trying adb
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.
kiewee3 said:
Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.
Click to expand...
Click to collapse
Err ..... it won't boot.
Does ADB work at this stage? Assuming you are rooted with CWM recovery, try
Code:
adb reboot recovery
Then from recovery, power it off completely. If fastboot is the problem, this should workaround it for you.
morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
It's karma because of your ridiculous signature.
Anywho. What did you do to the device? Attempt to root it? What happened between it working and not working?
khaytsus said:
It's karma because of your ridiculous signature.
Click to expand...
Click to collapse
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!
wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
Right. I can't figure out why people think others want to see large pictures of their crap.
just lou said:
Right. I can't figure out why people think others want to see large pictures of their crap.
Click to expand...
Click to collapse
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).
Rock-&-Roll-Hedgehog said:
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).
Click to expand...
Click to collapse
Oh. Now I see.
The nice thing is that Signatures can be disabled if you so choose, it'd just be nice if everyone kept a modestly sized signature.
wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
XDA Signatures: The new Geociities
morell2 said:
it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!
Click to expand...
Click to collapse
wat?
When you oem unlock, data is deleted, it tells you that. Otherwise, no idea what you're talking about.
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.
evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
wmoore said:
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.
Click to expand...
Click to collapse
Not neccessarily true. I use an app called Quick boot. I can boot into recovery from it with Ease. Lets me set up Widgets/icon for recovery and I have one for reboot. No need for me to hook up to pc. Anywhere at anytime I can boot into recovery on my Nexus 7. I can also set one up for bootloader. If someone gets stuck on bootloader screen, the hardware button press for reboot works to get out of there.
They have a free version of the app and it works perfectly. Check it out. No need to run to a pc everytime you want to flash a rom or something. Battery is nothing to worry about. As long as you have 50%(really even less than that), you good to flash, wipe, or what ever.
demandarin said:
Not neccessarily true. I use an app called Quick boot.
Click to expand...
Click to collapse
Me too. Though I'm old school and still like to type commands rather than point and click. I'll be looking at Quick Boot but still go to PowerShell (which I always have open) and type adb reboot.:silly:
All the various apps that offer rebooting options will work as they are still executing the same terminal commands that you would've had to type in in order to reboot it.
The issue is that you would still require a working system partition in order to boot into recovery (stock/twrp/cwm) without any USB connection. Incase of a soft brick, you will need to connect to a computer in order to get into recovery so i would suggest people make sure they have one nearby when they're flashing stuff.
I just went through this. I boinked my setup and it was bootlooping. I couldn't get into CWM.
Just press and hold Power+VolDwn+VolUp until you get into the stock bootloader. Now plug in your USB to to a PC.
Stay in the bootloader. Mine actually kinda froze but it will unfreeze after a while. Don't select anything. Just stay there.
Now you can use Fastboot commands to reboot into CWM. ADB only works when the phone is on.
I think the command is "fastboot reboot recovery".
This will put you in CWM. You can also take this opportunity to reflash your recovery here too. I reflashed mine just to be on the safe side before rebooting it.
Sent from my Nexus 7 using xda premium
I think the problem was I tried flashing cyanogenmod from a custom rom, or I wiped the OS. I can't turn off the phone or get it into recovery/bootloader. If I hold down the power button it the buttons light up but it never turns off. Am I going to have to wait until the battery runs out? It was at like 66%.
Yep just wait till battery runs doqn then go into recovery mode and flash rom from there, its not a good idea to flash a rom wile running your rom.
Sent from my Nexus 4 using xda app-developers app
Thanks for the reply, after I flashed the zip, I wiped dalvik, cache, data, and system in TWRP. Did I wipe too many things? Usually I wipe these before flashing a new rom, but the guide mentioned wiping after flashing.
treefingerz said:
Thanks for the reply, after I flashed the zip, I wiped dalvik, cache, data, and system in TWRP. Did I wipe too many things? Usually I wipe these before flashing a new rom, but the guide mentioned wiping after flashing.
Click to expand...
Click to collapse
I'm pretty sure you would only need to wipe cache/del cache after flashing
Use the file attached to see if you can get into recovery and sideload the rom again
Press shift and right click inside the folder and choose open cmd window here
then type adbreboot recovery
that should get you to recovery
bigdaddy619 said:
I'm pretty sure you would only need to wipe cache/del cache after flashing
Use the file attached to see if you can get into recovery and sideload the rom again
Press shift and right click inside the folder and choose open cmd window here
then type adbreboot recovery
that should get you to recovery
Click to expand...
Click to collapse
I am not sure what you mean by pressing shift and right clicking for the cmd window, when I shift and right click in the folder nothing different happens than if I just right click.
After you flashed the Rom, you erased it by wiping system...you do your wipes before, never after. The zip should still be on internal, unless you wiped that too..
Sent from my HTCONE using xda premium
bigdaddy619 said:
I'm pretty sure you would only need to wipe cache/del cache after flashing
Use the file attached to see if you can get into recovery and sideload the rom again
Press shift and right click inside the folder and choose open cmd window here
then type adbreboot recovery
that should get you to recovery
Click to expand...
Click to collapse
Found the cmd window option, couldn't edit post. it says "adbreboot not recognized as internal command"
the zips should still be on the internal, didn't wipe that.
treefingerz said:
Found the cmd window option, couldn't edit post. it says "adbreboot not recognized as internal command"
the zips should still be on the internal, didn't wipe that.
Click to expand...
Click to collapse
my bad adb reboot recovery
For what its worth, I've ran into the frozen hard boot issue and read in the international forum that if you hold it over/under a bright light while holding down the power key or power/volume key it will then work. I tried it after being hung up and it worked for me. Just wanted to put that out there in case anyone runs into that issue in the future.
Sent from my HTCONE using Tapatalk 2
smatherlee said:
For what its worth, I've ran into the frozen hard boot issue and read in the international forum that if you hold it over/under a bright light while holding down the power key or power/volume key it will then work. I tried it after being hung up and it worked for me. Just wanted to put that out there in case anyone runs into that issue in the future.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Interesting, I locked up my phone once and it was doing same thing as op. It would just never reboot. I had to wait till the battery died.
Sim-X said:
Interesting, I locked up my phone once and it was doing same thing as op. It would just never reboot. I had to wait till the battery died.
Click to expand...
Click to collapse
Yea as strange as it seems, that technique worked for me.
Sent from my HTCONE using Tapatalk 2
treefingerz said:
Thanks for the reply, after I flashed the zip, I wiped dalvik, cache, data, and system in TWRP. Did I wipe too many things? Usually I wipe these before flashing a new rom, but the guide mentioned wiping after flashing.
Click to expand...
Click to collapse
Ya theres your issue when you wiped system you wiped your rom. That shouldn't be done unless your about to flash a new rom but my best bet is to drain the battery then charge it for a couple minutes and reboot your phone and flash your rom since system only wipes your rom not your files.
Sent from my SPH-L710 using xda app-developers app
smatherlee said:
For what its worth, I've ran into the frozen hard boot issue and read in the international forum that if you hold it over/under a bright light while holding down the power key or power/volume key it will then work. I tried it after being hung up and it worked for me. Just wanted to put that out there in case anyone runs into that issue in the future.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
I can vouch for this as well. I tried every other method out there to get it to reboot (adb, button combinations, and the like). Went outside and pressed power and volume down in front of my car headlights, BOOM reboot. Weird, but useful knowledge, I feel like it should go in the FAQ.
iskatebad45 said:
I can vouch for this as well. I tried every other method out there to get it to reboot (adb, button combinations, and the like). Went outside and pressed power and volume down in front of my car headlights, BOOM reboot. Weird, but useful knowledge, I feel like it should go in the FAQ.
Click to expand...
Click to collapse
I will add it now
bigdaddy619 said:
I will add it now
Click to expand...
Click to collapse
Cool thanks man
smatherlee said:
For what its worth, I've ran into the frozen hard boot issue and read in the international forum that if you hold it over/under a bright light while holding down the power key or power/volume key it will then work. I tried it after being hung up and it worked for me. Just wanted to put that out there in case anyone runs into that issue in the future.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
WOW that worked. I was stuck on boot screen and thinking I am not liking this phone very much If i cant pull that battery when things go south...... and waiting for a full battery to die is ridiculous.
Thanks man!!!.
smatherlee said:
For what its worth, I've ran into the frozen hard boot issue and read in the international forum that if you hold it over/under a bright light while holding down the power key or power/volume key it will then work. I tried it after being hung up and it worked for me. Just wanted to put that out there in case anyone runs into that issue in the future.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Thanks!