Database Info

[Q] CWM Recovery Not Acting Correctly.

Hey all,
My phone was acting up and had a lot of clutter so I ODIN'ed to stock WITH root and e3. I downloaded Rom manager and flashed recovery. Seemed to work. I did the double install deal. Loaded green recovery: great. Reboot the phone. Turn it off to boot back into recovery. As i do the two volume plus power button combo, phone boots and i come to the blue and yellow install screen for recovery. Happens everytime.
I even tried going back to entirely stock. No root or anything. I then rooted, added e3, and flashed. Same deal.
Whats going on?!
I'm flashing a rom right now to see if that fixes anything.
It can't be normal to have to reinstall the package everytime i reboot into recovery.
And it only boots into green. Not blue or red.
Help!

Just finished flashing Zeus and went into recovery. Booted right into red. I guess problem solved?

galaxy s phones and the infuse don't conform to the android standard. they use a kernel with initramfs for boot in place of a boot.img partition. the initramfs can't be modded short of compiling a kernel and flashing it to the phone. the behavior you described is absolutely normal for high end Samsung phones. there isn't really any other safe or easy way to do it. the green recovery is the one designed for the i9000 with the stock kernel. the red/blue versions are themed and modded version that are baked into the kernel. once you flash a rom with a custom kernel you will have red unless it is cm7 or miui which will have blue.

Thanks for the explanation! Makes sense now.

Bricked galaxy tab 2 7.0

I think I bricked my tab 2 (gt-p3113) it keeps on looping at boot, I recently flashed cm10 on it then flashed stock rom (it was laggy, so I tried flashing clockworkmod recovery to reinstall cm10) after flashing clockworkmod, it kept on looping. I don't know what the problem is, please help.
UPDATE: I kept on pressing random buttons to reach download mode, but I need a stock rom + stock recovery (this rom was 4.0.3) for my device (samsung-updates site is moving servers or so)
I downloaded my stock rom from this post : http://forum.xda-developers.com/showthread.php?t=1645295&page=3 it's laggy + apps kept on crashing)
I need a new stock rom because flashing clockworkmod recovery on this rom always causes a bootloop, I want to install cwm recovery to restore my data.

first, try to download the stock recovery from sammobie.com , put it on your external sd & then try to re install CWM via odin, wipe your data and everything (if you're returning from CM10 to stock one) and then re-flash the stock ROM, hope this might help you

rickywinataa said:
first, try to download the stock recovery from sammobie.com , put it on your external sd & then try to re install CWM via odin, wipe your data and everything (if you're returning from CM10 to stock one) and then re-flash the stock ROM, hope this might help you
Click to expand...
Click to collapse
I couldn't find it on sammobile, but I googled it (794MB, downloading..) I think the problem was that I flashed cwm for 4.0.4 (seeing as I had 4.0.4 before cm10) then the stock rom I flashed was 4.0.3 (I can't update my device via OTA, idk why)
I'm just afraid the newest firmware I'm downloading lags and so, because the one I downloaded earlier (the 4.0.3 one) keeps lagging and force closing apps.
UPDATE: I flashed it, works perfectly fine, now I'm on my way to flash clockworkmod recovery and to root it in order to run cm10, but is there a way I can ONLY flash the stock recovery back? the md5 file I downloaded contains recovery.img is there a way I can flash it in odin without the whole ROM?

Bibicp said:
I think I bricked my tab 2 (gt-p3113) it keeps on looping at boot, I recently flashed cm10 on it then flashed stock rom (it was laggy, so I tried flashing clockworkmod recovery to reinstall cm10) after flashing clockworkmod, it kept on looping. I don't know what the problem is, please help.
UPDATE: I kept on pressing random buttons to reach download mode, but I need a stock rom + stock recovery (this rom was 4.0.3) for my device (samsung-updates site is moving servers or so)
I downloaded my stock rom from this post : http://forum.xda-developers.com/showthread.php?t=1645295&page=3 it's laggy + apps kept on crashing)
I need a new stock rom because flashing clockworkmod recovery on this rom always causes a bootloop, I want to install cwm recovery to restore my data.
Click to expand...
Click to collapse
Your Tab is not bricked. A bricked Tab / Phone will not turn on. There won't be any response from the device, whatever you do. Because, I bricked one of my friends Mobile.
All you need to do you is, to install a proper firmware on your Tab 2. PM me if you need any help.

Mine started acting like it was bricked. Refused to turn on. I held the power button for 2+ minutes, nothing. Then I let it charge for 4+ hours and tried to turn it on, again, nada. I then unplugged it and held the power button and it booted. The first time the screen went to sleep it would not respond again. Plugged the cable in for a minute, then unplugged and it started. Battery was at 90%. It is on it's way back to Samsung now. They say 7-10 business days, we'll see.

Trouble Rooting UCLB3 Gingerbread 2.3.6

- I am running Android 2.3.6. I flashed the UCLB3 via Heimdall. I have GB bootloaders from Heimdall
- I have the bootloaders from Samsung Kies Mini
- I have USB Debugging on, but when I connect to the computer it says “USB Connected” rather than “USB debugging connected.”
- I try rooting through Odin using jscott's tar.md5 files in the PDA window, but the window does not turn yellow (indicating the phone is not recognized) and after the process the Gingerbread setup greets me, but I do not have Superuser.
- SuperOneClick just freezes up when I try to root.
- I've tried to use the modified 3e recovery via replacing the “recovery” file in /system/bin but there is no recovery file there and the paste “fails” due to lack of superuser access, I presume.
- Basically, I'm stuck and unable to root or flash anything that has SuperUser unless I can either get Odin to recognize my device or find another way that does.
When I first got the phone it was on froyo. I stupidly tried to flash an ICS ROM (Dark Knight) because I assumed it was on GB. I successfully rooted using SuperOneClick and flashed CWM recovery, but got the rainbow distortion from lack of GB bootloaders. I then proceeded to flash the UCLB3 via Heimdall and got my phone working again, but with ranbow distortion on boot and in recovery mode (rendering the CWM recovery useless as it would not respond with the rainbow distortion. I then re-flashed UCLB3 using Heimdall and checked the “GB bootloaders” box this time, which got rid of the distortion. But now I'm stuck and unable to root or flash anything because Odin won't recognize my device (it says it's there but the window does not turn yellow) and no other methods give me SuperUser. Kies Mini recognizes my device and says there are no updates, so it's not the cord. However, Kies regular does not. I think it's something to do with USB debugging not working properly and allowing Odin to recognize the phone so it can root it.

JoeyofBladez said:
- I am running Android 2.3.6. I flashed the UCLB3 via Heimdall. I have GB bootloaders from Heimdall
- I have the bootloaders from Samsung Kies Mini
- I have USB Debugging on, but when I connect to the computer it says “USB Connected” rather than “USB debugging connected.”
- I try rooting through Odin using jscott's tar.md5 files in the PDA window, but the window does not turn yellow (indicating the phone is not recognized) and after the process the Gingerbread setup greets me, but I do not have Superuser.
- SuperOneClick just freezes up when I try to root.
- I've tried to use the modified 3e recovery via replacing the “recovery” file in /system/bin but there is no recovery file there and the paste “fails” due to lack of superuser access, I presume.
- Basically, I'm stuck and unable to root or flash anything that has SuperUser unless I can either get Odin to recognize my device or find another way that does.
When I first got the phone it was on froyo. I stupidly tried to flash an ICS ROM (Dark Knight) because I assumed it was on GB. I successfully rooted using SuperOneClick and flashed CWM recovery, but got the rainbow distortion from lack of GB bootloaders. I then proceeded to flash the UCLB3 via Heimdall and got my phone working again, but with ranbow distortion on boot and in recovery mode (rendering the CWM recovery useless as it would not respond with the rainbow distortion. I then re-flashed UCLB3 using Heimdall and checked the “GB bootloaders” box this time, which got rid of the distortion. But now I'm stuck and unable to root or flash anything because Odin won't recognize my device (it says it's there but the window does not turn yellow) and no other methods give me SuperUser. Kies Mini recognizes my device and says there are no updates, so it's not the cord. However, Kies regular does not. I think it's something to do with USB debugging not working properly and allowing Odin to recognize the phone so it can root it.
Click to expand...
Click to collapse
download mode:
http://forum.xda-developers.com/showpost.php?p=25526654&postcount=3
profit

Thanks for quick reply and it worked!

I flashed a rom (Dark Knight) but every time I reboot, it goes straight to recovery. Do I need to change some settings or what? No matter how many times I flash it, the phone boots straight to CWM Recovery. What did I do wrong? What should I do now? I think I'm just stuck in a boot loop but I don't want to restore to stock and try again because I'll probably just keep making the same mistake. Instead I'd rather wait for someone to tell me why that flash didn't work and what I should do to make it work. Ive done work on a few other (newer) phones and I've never had this happen.

JoeyofBladez said:
I flashed a rom (Dark Knight) but every time I reboot, it goes straight to recovery. Do I need to change some settings or what? No matter how many times I flash it, the phone boots straight to CWM Recovery. What did I do wrong? What should I do now? I think I'm just stuck in a boot loop but I don't want to restore to stock and try again because I'll probably just keep making the same mistake. Instead I'd rather wait for someone to tell me why that flash didn't work and what I should do to make it work. Ive done work on a few other (newer) phones and I've never had this happen.
Click to expand...
Click to collapse
Read the OPs.
You need to flash CM9 twice, with a wipe in between.
If you accidentally did a reboot to recovery and suck in a loop, use the GB kernel flash in heimdall, wipe. Download mode, flash the Jt kernel and try again

qkster said:
Read the OPs.
You need to flash CM9 twice, with a wipe in between.
If you accidentally did a reboot to recovery and suck in a loop, use the GB kernel flash in heimdall, wipe. Download mode, flash the Jt kernel and try again
Click to expand...
Click to collapse
I read the instructions and i didn't see it say to wipe in between flashes, just to reboot recovery. I do follow directions you know but can't follow directions that aren't written in the spot I'm reading them and assuming them to be right. But thank you for telling me what I should havedone. So once I have jt kernel, I just flash, wipe, reboot recovery,and flash again?

I did the UCLB3 Repartition One Click and then wiped everything. Then I flashed JT's kernel and flashed the ROM. Before I could do anything else, it started on its own and everything is fine now. THanks for your help, I'm still a little confused but you pointed me in the right direction. Thanks will be given.

JoeyofBladez said:
I did the UCLB3 Repartition One Click and then wiped everything. Then I flashed JT's kernel and flashed the ROM. Before I could do anything else, it started on its own and everything is fine now. THanks for your help, I'm still a little confused but you pointed me in the right direction. Thanks will be given.
Click to expand...
Click to collapse
Glad it worked for you.
While in cwm recovery, re-boot into recovery means powering off and then turn back on with 3 finger salute.
Selecting "Reboot Recovery" may not work and may send a user into a loop recovery image.
I've found from experience that flashing a different kernel with different cwm version may erase that loop and let you start over.
As you have discovered what I've been saying along and if you read the ops on the heimdall thread, you will understand that rooting the official firmware is pointless if you are planning on flashing a custom firmware.
Root it only to run it with root permissions.
Flashing in download mode does not require root. Just flash the kernel with cwm recovery.
have fun

[Q] SOLVED Problem flashing CyanogenMod 9.1.0 Stable

I rooted my MT4GS a few months ago but stuck with the stock ROM. I decided I wanted to try out the CyanogenMod 9.1 ICS ROM. I followed the following steps:
1) Installed ROM Manager.
2) ROM Manager indicated a newer version of ClockworkMod Recovery and I installed it (5.0.2.7).
3) Using ROM Manager, did a full backup of the current ROM. All went well.
4) Using ROM Manager, downloaded and installed CyanogenMod 9.1.0 stable-doubleshot. I specified to wipe the data and cache partitions. The installation seemed to go normally.
When the phone rebooted, it was stuck at the logo screen. Had to remove the battery to turn it off. Tried a couple times, still the same.
Since I had the backup, I decided I would use CWM to restore the old ROM.
When I boot into recovery mode, it shows CWM 5.0.2.7, but whatever option I try to choose from the recovery menu, The screen just goes blank with the CWM logo in the middle and nothing else happens. Hitting the power button returns me to the menu, but no option works, even power down or reboot. It just goes back to the CWM logo again and I have to remove the battery to shut it down.
So, I thought I would try using fastboot to flash the ROM again. When I boot the phone into the boot loader and select fastboot, then plug the phone in via USB, nothing happens. Windows does not see the phone and ADB or fastboot don't see it either. It's not a driver issue, as the computer is still setup from when the computer was rooted and I connect the phone all the time with no problems.
When the phone is off and plugged into USB or the charger, I still get the charging light, though it goes off after about 10 seconds, then comes back on and cycles like that.
Is there anything I can try at this point, or is my phone bricked? It seems like I followed all the steps correctly. Is there an update.zip I can put in the root folder and see if it picks it up?
Any help would be appreciated.

brucehvn said:
I rooted my MT4GS a few months ago but stuck with the stock ROM. I decided I wanted to try out the CyanogenMod 9.1 ICS ROM. I followed the following steps
...
Click to expand...
Click to collapse
Ok, after rebooting Windows, I was able to get the USB connection to the phone to work in fastboot. It seems I missed the step described in this thread:
http://forum.xda-developers.com/showthread.php?t=1508556
which states with S-ON you must flash the boot.img separately. I did that via fastboot and the phone boots into cyanogenmod now.
However, I still seem to have the issue with clockwordmod recovery. As long as I do the recovery functions from rom manager, everything is fine, but when I manually boot into the recovery menu, I get the same behavior of any choice from the menu just blanks the screen except for the CWM logo and nothing happens. I tried reflashing the recovery image using fastboot, but still no go.

brucehvn said:
However, I still seem to have the issue with clockwordmod recovery. As long as I do the recovery functions from rom manager, everything is fine, but when I manually boot into the recovery menu, I get the same behavior of any choice from the menu just blanks the screen except for the CWM logo and nothing happens. I tried reflashing the recovery image using fastboot, but still no go.
Click to expand...
Click to collapse
This is solved also. Seems on the MT4GS, the trackball is the selection button. The power button appears to only be a back button.

What a thread! Two nicely phrased problem definitions, two well explained solutions, and all from the same guy. Sorry we weren't able to help directly, but you obviously found the answers you needed elsewhere in the forum. And you updated the title as well to show it was solved. Thanks.

[HELP THREAD] My N5 won't boot.

Hi everyone, I just bought a N5 yesterday (i was using a N4 for almost 2 years) and I unlocked my device using the Nexus Root Toolkit, flashed the latest TWRP, installed ParanoidAndroid as my main OS and everything was fine untill the next step...
I was an avid user of MultiRom on my N4, so I flashed MultiRom on my N5 and everything was fine, I even tried to flash the official MiUI as a secondary OS but i got some errors and I just deleted that listed rom, no biggies... after that I booted into PA and flashed a custom kernel.
First, I flashed Franco's using his tool, and everything went smooth. I even restarted the device like 2 or 3 times while i was installing the usual apps (xposed, changed the font etc), the problem started when I downloaded the HellsCore kernel app from the playstore and flashed the kernel, after that, every time I try to boot my device it gets stuck on a black screen, it doesnt even show the Google logo with the unlocked icon at the beginning, it just gets stuck at that point.
My guess was that the Hellscore kernel had some issues with Multirom, and I started the fastboot recovery via ADB and flashed Franco's Kernel again... nothing happened, I still got a black screen.
I tried flashing the entire rom again (PA) and the same, black screen.
I also tried installing the original TWRP (not the MultiRom modded TWRP) and guess what??? I stilll got the same black screen.
The only way to get past thu it is to disconnect my device from USB, press power for 10 secs and after that i have to press power+volup+voldown.
That gets me to the fastboot. If I try to boot to the OS from there, i get a black screen. If I try to boot into the recovery, it boots ok.
The only way to boot into ParanoidAndroid is using the Nexus Root Toolkit and using the Franco's Kernel (r57) to boot TEMPORARY into the OS.
I dont know what else can I try, can someone please give me some advice??? Please. D=
Thanks in advance!!!

Return to stock. Links via signature.
Sent from my Nexus 5 using Tapatalk