Using Rom Manager (after updating it today), I flashed CWM Recovery to 5.0.0.1 as it suggested I should.
I rebooted to check it out, and now my Phone is stuck in FASTBOOT.
No matter what option I choose, it simply reboots to FASTBOOT again.
Yes, I tried the VOL-Up + PWR, and VOL-Down + PWR. VOL-Up + PWR gives me 3 vibrations and no other reaction. VOL-Down + PWR does nothing.
Any suggestions?
Did the same thing to me. I had to pull battery and restart and it worked fine after.
Yea, unfortunately I forgot to mention that I tried that about 10 times
Guess I get to learn how to ADB flash the recovery all over again (been about 6 months).
Side note: I did notice when selecting "Recovery" from the HBOOT screen, it seems to be scanning my sd card for a file and says it cannot find it. (It goes REALLY FAST then disappears, so I'm not sure what file it's looking for)
Do you use twitter? Send koush a message. He always responds.
I had this problem, too. In my case, it turned out that I needed to update my version of ROM Manager to 4.4.0.5. Once I did that, I just re-flashed 5.0.0.1. Works just like it should now.
I had the same thing happen to me before, turned out Clockwork did not install properly so I downloaded the HBOOT flashable recovery from here http://dougpiston.com/?page_id=85 and that did the trick.
It turned out that my troubles all stemmed from a failing sd card.
I've yet to see one, but is there an app available that performs a integrity check on mounted sd cards?
Sent from my ADR6300 using XDA App
Not that I know of. But that missing file u were talking about I believe is normal. Everytime I flash or nandroid, that error missing file thing pops up and then gets ignored. It doesn't cause an issue for me as I have flashed probably 2 dozen ROMs with several being daily drivers over the last 17 months and nandroided just as much. Never an issue.
Sent from sweet snacks off tapatalk.
Related
Rooted my Incredible yesterday...with relative ease...some very helpful guides out there.
After searching a little...I can't find anything similar to my issue, and the pieces I can find don't piece together for me.
Was accessing hboot (power plus volume -) this morning and accidentally hit the power button to select "fastboot", rather than the "recovery" option i was wanting to get to to make another backup since I had added a few apps after my root.
My phone booted into froyo without any issue...and all my rooted apps worked fine (mainly wireless tether...the main reason I rooted). I shut down the phone and attempted to access hboot again...but got 5 vibrates and a green blinking led, with a blank black screen.
Pulled the battery...and let the phone boot normally (which I was hoping for since I thought I may have bricked it) and all is well...still with root applications working fine. I have tried hboot again with same result (5 vibrates and green flashing led), so I have let the phone stay with froyo for fear that if i screw around with it too much I may brick it after all.
Am I over-reacting to the lack of hboot? Suggestions for a fix are appreciated!
This is wierd, the only time ive heard this prob is when someone tries to flash a rom and then this happens. Sry man i have no idea its strange
Sent from my ADR6300 using XDA App
Download Rom Manager if you dont already have it a then install CWM recovery through it. It just sounds like it didn't install correctly the first time. That usually works for me when I get the problem of only being able to get into HBoot and Fastboot.
tried flashing cm7 and now my phone is in bootloop. I have tried everything. When I go to hboot and try anything, it just goes to clockworkmod and will not do any commands. Tried connecting to pc, but will not read the device. Any help would be greatly appreciated as I love this phone and hope it is not bricked.
To me it doesn't sound "bricked." This may be redundant if you have tried them all already.
But all I can think of doing is battery pull, and waiting about 5-10 min.
Boot into hboot and then recovery and restoring a nandroid if you have one.
If you don't have a nandroid boot into hboot and do a full factory restore.
If those don't work I have an idea you can try, it can't hurt. Try getting into recovery and reflashing the rom or flash a new one altogether.
I have tried the battery pull about 25 different ways. It does not allow me to do anything when I get into clockworkmod. I can't flash, reboot, factory reset/wipe data or any of the other options, It just goes into "hat screen" and stays there forever. It will then go back to clockworkmod menu screen if I press the power button. I have tried everything with both the sd card in and out and while pullin it out or putting it in during the processes. I have tried connecting to the pc and flashing a rom, but it recognizes the drive, but does not allow anything to be out into it. I think she's dead.
could be another dumb suggestion but in recovery (clockworkmod) you don't press power to select an option you press the trackball.
you can flash a stock rom while in HBOOT. for example download the rom below rename the file to PB31IMG.zip put it in the root of your sd then boot into hboot. wait awhile and HBOOT should detect that you have a file to flash and ask you if you want like to update.
http://dougpiston.com/files/RUU/bui...and-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
that worked, thanks.
I had this problem once flashing from cm7 to something else i forgot which. In the end i found out it was just me being an idiot. I was using the power button to try to select my options in CWM instead of using the optical at the bottom lol. If you use the power button in CWM it just gives you the hat until you press it again. I was freaking out big time and almost slapped myself when i found out what i was doing wrong lol. I see your problem was resolved but by chance do you know what button you were pressing?
My Gmail emails weren't coming into my HTC EVO 4G so I tried to power cycled it (my non-Gmail emails were coming in just fine). When I powered it back it on nothing came on the screen, nothing happened. It is rooted (Unrevoked) so I tried holding the power button and volume up button, but it just vibrated three times, nothing came on the screen and nothing happen. I tried power button and volume down button and it boots in HBOOT. Seconds later it runs something and there's a message saying something about wrong image. I stopped here as I haven't used HBOOT before.
What's going on here? How do I get my phone to boot normally again?
P.S. - it's not the battery, because its been charging all night.
DiGiTY said:
My Gmail emails weren't coming into my HTC EVO 4G so I tried to power cycled it (my non-Gmail emails were coming in just fine). When I powered it back it on nothing came on the screen, nothing happened. It is rooted (Unrevoked) so I tried holding the power button and volume up button, but it just vibrated three times, nothing came on the screen and nothing happen. I tried power button and volume down button and it boots in HBOOT. Seconds later it runs something and there's a message saying something about wrong image. I stopped here as I haven't used HBOOT before.
What's going on here? How do I get my phone to boot normally again?
P.S. - it's not the battery, because its been charging all night.
Click to expand...
Click to collapse
It is normal for it to scan and give you that 'wrong image' message. If you had a PC36IMG on your sd card, that's when the bootloader would find it, and ask you to update. Since you dont have a PC36IMG on your card, it scans and finds nothing, so it says 'no image or wrong image'. No worries. What were you trying to accomplish by holding power and volume up? Its power and volume down that puts you to the bootloader. What were your intentions once you got to the bootloader? Were you trying to get to recovery, to clear cache or reflash a rom or something? If you want to reboot your phone without really doing anything, from where you're at in the bootloader, you'll see an option that says 'fastboot'. Select that. Once at the fastboot screen, you'll now see an option to reboot phone, and to power phone off. Select reboot, and see if she powers up for you. Shouldn't be any issues
Weird. So in HBOOT I chose "reboot" from the FASTBOOT main menu and the phone restarted and got back to the desktop/launcher successfully. Everything looks normal.
My Gmail inbox just now began updating from yesterday (even though the phone was on up until a couple of hours ago). Also the apps I set up to install yesterday from market.android.com just started to download and install too.
What's going on here? Is the internal storage/memory/ROM dying or something (come to think of it I did have this Gmail issue last week too, but that power cycle was successful)?
DiGiTY said:
Weird. So in HBOOT I chose "reboot" from the FASTBOOT main menu and the phone restarted and got back to the desktop/launcher successfully. Everything looks normal.
My Gmail inbox just now began updating from yesterday (even though the phone was on up until a couple of hours ago). Also the apps I set up to install yesterday from market.android.com just started to download and install too.
What's going on here? Is the internal storage/memory/ROM dying or something (come to think of it I did have this Gmail issue last week too, but that power cycle was successful)?
Click to expand...
Click to collapse
I'm not sure what would cause the problems you're describing. What ROM are you currently on? Have you tried wiping cache and dalvik cache? Perhaps it's an issue with the Gmail app itself. In any case, I'd first try wiping cache and dalvik. If that works, great. If it fails, I'd probably do a complete wipe and fresh install. That usually solves any issues for me.
Sorry, I saw your initial post after my second post.
I just realize what the confusion may have been. When I powered off the phone I figured I might as well take the opportunity and do a full backup with nandroid. So I proceeded to get into clockworkmod recovery with power + vol. up button (this is when it vibrates 3 times and does nothing). The confusion, I think, is that I've been installing/flashing various ROMs for my new Viewsonic G Tablet for the past 2 days straight (with very lil' sleep) and thought the recovery method (power + vol. up) for the G Tablet was also the method for the EVO.
Anyhoo, at this point I'm very confused. I could of sworn I installed clockworkmod recovery on my EVO and I used power + vol. up to get to it when rooting. I even see the clockworkmod folder on my EVO's microSD card. Weirdness.
My EVO is working now so I guess I shouldn't stress it. I'll just figure out how to do a full backup later.
Thanks!
DiGiTY said:
Sorry, I saw your initial post after my second post.
I just realize what the confusion may have been. When I powered off the phone I figured I might as well take the opportunity and do a full backup with nandroid. So I proceeded to get into clockworkmod recovery with power + vol. up button (this is when it vibrates 3 times and does nothing). The confusion, I think, is that I've been installing/flashing various ROMs for my new Viewsonic G Tablet for the past 2 days straight (with very lil' sleep) and thought the recovery method (power + vol. up) for the G Tablet was also the method for the EVO.
Anyhoo, at this point I'm very confused. I could of sworn I installed clockworkmod recovery on my EVO and I used power + vol. up to get to it when rooting. I even see the clockworkmod folder on my EVO's microSD card. Weirdness.
My EVO is working now so I guess I shouldn't stress it. I'll just figure out how to do a full backup later.
Thanks!
Click to expand...
Click to collapse
Yea, its power down and volume that takes you to the bootloader. You wont get directly to recovery unless your rom has the 4 option quickboot, then u can select recovery. Anyways, so once youre at the bootloader, you just need to select recovery. Then youll boot to clockwork. From there, you can make a new backup, flash a new rom, wipe caches etc.
Sent from my PC36100 using XDA App
Oh, okay. Thanks again!
DiGiTY said:
Oh, okay. Thanks again!
Click to expand...
Click to collapse
You're welcome. I'm glad to help out
Hi Guys -
First time android user and attempted rooting using the odin method. I followed the instruction listed here http://forum.xda-developers.com/showthread.php?t=1311194 to the "T" before starting. I was doing alright until after flashing the recovery-cwm-hercules.tar, then it gets weird. It didn't flash to recovery but just rebooted to the main screen (where I could see the background picture with the locker pattern), then it immediately shuts off and the cycle begins again.
The weird thing is that I can't even access recovery mode (hold vol. up+down+power), because I'll see the Clockworkmod logo then it flickers and reboot itself. This happens every time I attempted recovery mode.
My attempts to fix it:
1. I flashed the recovery, http://forum.xda-developers.com/showthread.php?t=1315390, to see if it makes any difference. The same story happens with loading to main screen w/locker then it reboots itself again and again. Sometimes I'll be lucky to input the pattern but before soon it will reboot itself again. Same thing with recovery mode as described above.
2. Flashing the stock kernel provided by http://forum.xda-developers.com/showthread.php?t=1311229 to see if it does anything. Nope, same story for both recovery mode/home screen.
3. The insecure kernel, http://forum.xda-developers.com/showthread.php?t=1320946. Same story. nope, nope.
4. Tried these in all order and permutation. Nada.
5. Tried it both ways using samsung driver/kies.
6. Tried it both ways with/without SIM card.
7. Battery is fully charged when attempting any flashing.
8. All the above in my second computer to no avail.
I'm sorry if this might come across as long winded but I just want you guys to get the full picture. I would really appreciate it if you guys could offer any solutions or advice on how to correct this problem. Please be gentle with this first time android user haha, thanks in advance man.
Manually boot into recovery (vol up/down keys) and make a backup (be sure to do this). Then try wipe data/factory reset through recovery. Sounds like a ROM issue not a hardware issue
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
redlaws said:
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
Click to expand...
Click to collapse
Ok, so if it actually boots into the ROM but reboots, try rebooting to recovery from adb -- "adb reboot recovery"
think it's a no go . i tried using adb recovery method and the same thing would occur, it would restart and seems to load into recovery mode but then I would only see the logo, then it flickers and restart itself.
then the vicious cycle of loading up to the screen-locker and restarting itself begins. guess this is the smartphone version of being friend-zoned.
Have you tried taking battery out then back in and while holding volume up/down plug it back into computer? That has never failed to get me into d/l mode. Man I hope you get it working.
Yeah I tried that and getting to download mode is not the problem. just that recovery mode doesn't boot properly in that it would restarts itself. and when i boot normally to screen, i would see the locker and background picture then within 3 secs, it would restart itself.
Guess last resort is to go to t-mobile store, play dumb, and get samsung on it. only problem is that i worry about the flash rom counter # since mine is like 10 already (my attempts to address this problem). Let's hope those tmobile reps aren't that tech savvy.
Thanks for all the help fellas, great early posting experiences so far.
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
kt0ce said:
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I'm going to give it another try. I've been trying it with different files for a good 2 days now though.
AllGamer said:
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
Click to expand...
Click to collapse
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
redlaws said:
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
Click to expand...
Click to collapse
did you let go of holding the vol+ & vol- buttons as soon as you see the blue text in CWR ?
it can easily reboot by accident when holding those buttons and hitting power, but the buttons are so responsive it selected the first option to reboot the phone by accident a couple of times on me
I'm positive that I held it properly and long enough. I never got to the blue text, just the CWR logo showing then turns off (like you shutting off a tv) and reboots itself. Trying to flash it again with Odin didn't work either and I tried the recoveries from different sources as well.
I went to the Tmobile store today and seems like they'll mail me a replacement then I'll return my current one to them. Only thing is stocking/processing fee but it's a small price to pay if it resolves everything.
glad they will give you another one..
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
reocej said:
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
Click to expand...
Click to collapse
Dude, I understand that it should but it's not. I've flashed the stock recovery for more than 10 times and I still can't past the home screen. It would just reboot itself in less than 3 sec. And I'm positive I flashed it properly. Believe me I don't want to spend extra money if I don't have too.
I've currently attempted to root my Galaxy and everything went well until I tried to back up my applications.
I can't get clockworkmod to work, I hold vol up, power, and home and it shows my the android character laying back with a red ! in Android System Recovery.
Not really sure what to do. I've been searching for possible solutions but I can't find anything.
I followed this method, http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
The FAQ section under it talks about two files that should be deleted as it overrides CWM but file explorer isn't finding them for me.
Just use the Root66 rooting method : http://forum.xda-developers.com/showthread.php?t=1949687 .
It sounds like whatever you did, it did not work and you still have stock recovery. Just do it through Odin as described in the thread linked - it is very easy.
Any possible chance of me bricking my phone by adding additional files along with the ones I've added? CWM seems to be working through the ROM Manager app but not working through Vol Up, Home, and Power.
You press power. Wait a second or two, then hold vol up and home.
If you hold power, the phone will never turn on. If you wait too long, the phone will boot into the OS. It's a timing thing.
I've done that and that's how I get sent to Android System Recovery.
I've downloaded CWM through ROM Manager but I can only access CWM right after I download I. It worked last night but today when I tried accessing CWM it sent me to Android System Recovery. I downloaded CWM again then it worked.
For some reason it seems CWM isn't sticking onto my device.
Oh, I misunderstood. To fix that, flash CWM (version 6.0.3.0) again. And when you reboot your device, before your device boots into the OS, drop into recovery mode. It will allow you to disable the script that keeps overwriting CWM for you (you will get this option when you attempt to exit CWM).
Oh wow, I did what you said my phone rebooted. I did vol up, power, and home and got sent into CWM. I think its working now
Thank you so much bro
Sent from my SGH-T999 using xda app-developers app
Now save yourself time and hassle and flash twrp recovery cwm is.in my opinion troubled... twrp seems to be the rec of choice
With goomanager from market.
Sent from my LG-MS770 using xda app-developers app
They are crawling out of the woodwork.
There is nothing wrong with CWM. There is nothing wrong (mostly) with TWRP. They both work. Pretty well, in fact. Though, I still have issues with TWRP pretending I pressed the back button when I didn't.
Since you are on TWRP, tell me if you can reproduce this: Go into the timezone settings and start selecting different timezones as fast as you can (also works with typing filenames for nandroids, but this is quicker for reproduction). What happens on my device is I get knocked back into the settings page. It is 100% reproducible, but inconsistent with presses/time required to make it crash. I have seen other people complain about this, but not nearly as many as I would expect, given the severity and prevalence of the bug.