Database Users

Help with screwed up clockwork recovery

In an effort to get back to stock I took things a step too far and now have a phone that won't power on. I had successfully rooted the phone and installed Rom Manager and flashed the clockwork recovery and immediately created a nandroid backup. Sometime later my phone started acting funny... usb connected/disconnected events when it was not plugged in, crashes, etc. I felt confident that this was a hardware issue (started after my daughter chewed on it when I wasn't looking). Anyway, I followed the instructions here in the dev forum (True Stock 2.1 firmware for vibrant) for the vibrant to get back to stock ( I apparently can't post the link because I'm new...) . So that I'd be able to try and get it replaced. I kept noticing that no matter how hard I tried clockwork was still installed... then I did the bad thing. I should have known better, but I made the rookie mistake and deleted the clockwork folder from the internal flash. I don't know what possessed me to do it, but I did. Since then the phone doesn't seem to boot. I can get it into download mode to flash images from odin (battery out, battery in, volume up + volume down, connect usb and download comes on). And after a successful download it seems to restart ok. But if it crashes (which it is now prone to do) or is powered off it won't boot after that. Worse I can't get to the stock recovery either.
I'm hoping that someone who has a nice rooted stock phone with clockwork installed can just help me get a copy of that folder back and everything will be fine... if not I may just have to see if playing dumb with tmobile will get the phone replaced as is...
Thanks in advance for any help.

Are you talking about stuff in /sdcard? If so, that won't effect the boot. You could delete everything in there and not change anything. Some apps might not work as you will have deleted their data, but if you're flashing a stock ROM with Odin, that's fine.
Enable debug mode in the settings and use "adb reboot recovery" at a command prompt. That should get you to the stock recovery. Try a factory reset from there, that might help. If not, delete anything in /sdcard that's not supposed to be there and swap with TMobile as it sounds a hardware issue at that point. Don't forget to keep your external SD card if you've replaced it.

Is USB debugging on?
When you get the phone up, can you connect to it via ADB and then adb reboot recovery or adb reboot download?

Thanks for the suggestions. I did get the sdk installed and used adb to reboot into normal recovery, so it's not completely boned. Since I could use adb for resets I went ahead and followed the rooting process again and reflashed clockwork. The phone still won't boot on it's own. I'm starting to think whatever was going south with the hardware has continued to get worse. I'm going to use odin to get back to "true stock" again and try to use adb to reboot into recovery and do a factory reset suggested above and see if that helps.
Thanks again.

I went back to stock with odin, ran the factory reset, and still can't power up normally or into recovery. I can get into download though, load with odin, come up normally after the reset. I'm going to try giving it back to Tmobile in it's refusing to power up state and see if I can get them to swap it. It's as stock as I can make it so the problem should not be mine.
Thanks again for the help.

FWIW - i just installed Rom manager this morning, the premium version, and today experienced 5 force closures, one on google maps
before this i've had maybe one FC some 2-3 weeks ago - and like you i did a clockworkrecovery backup or nandroid backup

[Q] First blue screen, now boot loop.

Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.

Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?

Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.

Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]

I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.

PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)

Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)

Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.

just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..

Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.

hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!

Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started

i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off

astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??

Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little

U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App

all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^

How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link

Looks like you are not having much luck. Did you try to factory reset?

astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much

[Q] Help going back to stock?

Hi, im in the process of selling my phone and am following the tutorial on here about turning the phone back onto stock. The flash with flashtool was successful but im forever stuck on the boot screen? with now no way to go into custom recovery? i installed the correct rom for the phone so why hasnt it worked? thanks in advance.

dav08094194 said:
Hi, im in the process of selling my phone and am following the tutorial on here about turning the phone back onto stock. The flash with flashtool was successful but im forever stuck on the boot screen? with now no way to go into custom recovery? i installed the correct rom for the phone so why hasnt it worked? thanks in advance.
Click to expand...
Click to collapse
The only way I could get it to work was the following; however there is one thing to try before you try my way because mine did this also - after the wipe and flash with flashtool etc. The only way I found to get out the bootloop was to do a factory restore after when its looping. So from the boot screen loop hold the power button until it goes off then on then off again.
Then do the process to get into the recovery so hold down and power then release power as soon as the lg logo appears (first one) then press it again immediately that SHOULD get ya to the grey factory reset screen. Press the power button 3 x and it should do a factory restore and boot up this time. First boot may take a minute it should eventually start up.
Failing that try this - Open the lg mobile support tool and connect the phone in download mode (volume up and power with plugged in usb on mine) then go to options and upgrade recovery. it will download a file usually about 2GB then install it, the phone will reboot at 100% on the phone and 80ish% on the lg tool it will then start into the setup feature,
DO NOT disconnect the phone until it gets to 100% and finishes. This way you shouldn't need to do an extra factory reset.
I understand for this the phone needs to be seen on com 4 (it shows on the phone screen) so if necessary go into device manager with the phone still plugged in in download mode and select com ports then select the phone com port then right click >properties> advanced and change the com port to 4. It may tell u its already being used but don't worry it is fine. Save and exit device manager.
please bare in mind these are just my experiences on MY LG D802 however its worked every single time for me without fail and ive done it a good few lol.
HTH:good:

[Q] Did I turn my G2 into a non-recoverable brick?

Good evening everyone,
I will start off by saying that I really didn't do things by the book this time around. I have run out of ideas even as to what to Google to find similar cases to mine.
I wanted to flash Cyanogenmod onto my G2. Since I already had CWM installed, I loaded the ROM and Gapps. After wiping the phone, I went to flash from the zip. The flash failed. I tried again, and it happened again. I wiped the cache and dalvik again, and tried again. Still no flash.
At this point I go for the reboot only to realize that my phone is now stuck in a bootloop that is contantly landing me back into recovery.
I believe I really screwed up from here as I read about a way to exit the cwm bootloop by flashing a new "exitrecovery.zip" file. Since ADP wouldn't push the file for some reason, I used that function where the phone waits the file to be pushed and flashes it. That succeeded.
The phone switched off (after hanging on CWM for a bit) and now won't do anything at all. No boot logo, nothing. Can't get into CWM anymore either.
The computer brings up a bunch off drives which it wants me to format when I plug the phone in. Only one of them has a folder called "image" on it.
The display switches on, but won't do anything there.
Holding power+up reboots it after a few seconds and so does power=down.
I am thinking of just seeing if I can get it assessed by my carrier, hoping they'll have the tools to just reflash it... somehow. Else, is there a way to potentially fix this?

Back to stock
Put the phone in download mode (vol up while plugging in USB) and use the LG Flash Tool to return to stock. Instructions are posted in General section.

Rule number 1.
ALWAYS MAKE A BACKUP.

bodom_hc said:
Rule number 1.
ALWAYS MAKE A BACKUP.
Click to expand...
Click to collapse
I have a backup I made with CWM.
If that helps, please point me into the right direction to restore it. I fail to see how I can do that without even being able to start cwm up.
missiveusa said:
Put the phone in download mode (vol up while plugging in USB) and use the LG Flash Tool to return to stock. Instructions are posted in General section.
Click to expand...
Click to collapse
I will try this, but the screen never shows anything at all

Recovery from bootloop (and other issues)

Ok, so... this is gonna be quite long to tell, but I need to explain the situation as carefully as possible because the problem I have seems to be very specific and potentially solutionless.
So, a week ago my Samung Galaxy Tab S6 Lite (SM-P610, CSC: ITV, which is the Italian Country Code and it's for unbranded devices, since my model is Wi-Fi only), suddenly started to restart itself and it's been stuck for days in a bootloop (i.e. it's stuck on the logo and if I hard restart it with Volume Down + Power, it gets stuck there again). Yesterday I found out that it's most likely a software problem, so re-installing the Android version should fix everything up... right? Well, I did just that but the device is still stuck on the bootloop.
Here I want to be more detailed: firstly, I'm 100% positive that the problem I have is NOT due to a virus, as I've never done ANYTHING that could potentially lead me to taking a virus (such as downloading apps outisde Google Play, visiting risky sites etc.); secondly, I followed a procedure that was supposed to repair my device without losing data. That's because I've stupidly never made a backup and I can't afford to make a factory reset. The procedure I followed consisted in finding the Android update I needed with Frija, and then downloading everything in the tablet with Odin. Also, I'm 100% positive that I made NO mistakes during the installation procedure. The only step that I did differently is HOW I installed the update: I did it with Download Mode, not with fastboot, because when I go into Recovery Mode and reboot the device into bootloader, the PC doesn't recognize my Tab, even if the PC does recognize that it's connected, as it makes the typical sound of when you plug something in a USB port (I have the USB drivers installed in my PC, I think it doesn't work because I never unlocked bootloader). What I get when I reboot into bootloader is "entering fastboot..." stuck screen and the PC and Odin aren't able to recognize it.
My questions are therefore these:
Is there a way to make a backup of the data of my device if I can't boot it (maybe via Download Mode)?
Is there a way to make fastboot work if I can't boot my device?
Is there some other way to repair my tablet that I can try?
Thank you for any help, this is my last hope to find a solution for my problem.

neo4458232 said:
When your device is stuck on an Android boot loop issue then you can fix it by simply doing a soft reset. Turn off your device and the problem will be resolved.
Here are the steps to follow:
First, switch off your device and take out your battery from the phone.
If your battery is non-removable then turn off the phone for 3 to 5 minutes and again turn it on.
This method works effectively to fix the error of the boot loop issue. But if a soft reset does not work for you to fix Android phones stuck in the boot loop issue then you should follow the next method.
Method 3: Reboot System in Recovery Mode​Rebooting a phone in the Recovery Mode is known for fixing several errors and issues on your Android phone. So, if you are unable to start your phone in normal mode or your Android is stuck in a reboot loop, then restart your phone in Recovery Mode.
Method 4: Remove and Reinsert SD Card​You may also try to remove the SD card to fix the boot loop in Android. According to several user reports, this trick worked for them. So, you should try this.
First, turn off your phone > remove the SD card > turn on your phone normally, and check if your phone is out from the boot loop or not.
If it is still stuck in the boot loop, then go for the other solution.
Method 5: Reboot the Phone in Safe Mode​This problem may also occur due to problematic 3rd party apps. If you have recently installed an app on your phone and then you started facing this issue, then remove it from your device.
Or, if you are not sure which app is responsible, then try rebooting your phone in safe mode. Doing this will disable all the third-party apps on your Android phone and then you can easily find out if this is the reason behind this issue or not.
To do this, you need to follow these steps:
Start rebooting your phone.
When the device logo appears on the screen, long-press the volume-down button at the same time.
Now, your phone will automatically switch to Safe mode.
If your phone is no more getting into the boot loop, then it means one of the third-party apps installed on the device was causing this issue.
Now, find out the problematic app and uninstall it to fix the Android boot loop without losing data.
Method 6: Use Custom Recovery Mode​When you find your Android is stuck on the startup screen due to the boot loop issue, then you must try to restart the phone in the Custom Recovery mode. Here is the guide to do so:
To enter into the Custom Recovery mode press the Power + Volume down buttons simultaneously.
Select the “Advanced” option in the Custom Recovery menu.
Next, choose “Wipe Dalvik Cache”. Choose “Yes” when prompted for confirmation.
Move to the “Mounts and Storage” option and choose “format/cache”. It will clear the cache files completely.
Restart your device.
Method 7: Fix Android Bootloop Error Via CWM Recovery [For Rooted Phone]​Maybe you are not aware of this method but it’s a useful way to fix the boot loop issue on Android after the update. Remember that this method is only for rooted phones. Here CWM means ClockworkMod and if your phone is stuck on the Android boot loop then it must be downloaded and installed on phone. Read me
Click to expand...
Click to collapse
Thanks for replying but I already tried every method listed here.

At this point it sounds like you need to bring it in to a local repair shop & see if they have a fix.

The solution is to wait on the turned on screen until the battery dies completely. Then put it to charge and after a bit using the reset combo (pwr+volume down) once the circular battery charging indicator with the green border comes. (It's a matter of luck, this keeps happening to my tablet and even the official samsung store can't fix it even though they took money to do the same)