Database Info

[Q] Desire S boots into recovery mode automatically!!

hello, I have a problem with a desire s phone which keeps booting into recovery mode when i turn it on. here's my step by step of what I did that got me into this predicament.
the phone had a stock 1.48 asia rom 0.98.0002 bootloader locked, and unrooted. so first I ran revolutionary had no problems there, had a revolutionary logo on my bootloader afterwards and the bootloader version was now 6.98.0002 or something I forget. anyway the next thing i did was I downloaded the stock euro rom 2.10.401.9 and extracted the rom.zip then renamed it to PG88img.zip copied it to the memcard ran fastboot, then fastboot automatically installed the zip after installation restarted the phone, now the phone was stuck on the white htc screen, so I ran recovery press the power and vol up and did a factory reset, had no luck with it still stuck on htc screen, now after reading a lot of threads, downloaded the ENGpg88img bootloader flashed it using fastboot and it was successful, the revolutionary logo was gone and the bootloader was now 6.98.0000 ( PG880000) but now when I rebooted the phone it would go directly back to recovery!! So the next thing i did was ran the euro rom again from the memcard thru fastboot and it updated the bootloader to the newest version and had a "locked"on top of the screen, so i did a boot unlock using htcdev and now its unlocked, then downloaded the clockwork recovery for saga then flashed it using fastboot with no problems. so now when I turn on the phone it goes straight to clockwork recovery! So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.

long story short, I can only use fastboot, and if I use clockwork mod recovery to mount system i can do some adb commands. i also tried putting it in fastboot and ran an official RUu but I always get error 150. any help would be greatly appreciated.

It seems that your chip is gone. I have the same problem (boot looping) and had to try reclamation by phone provider. Find thread with "boot looping", or "white screen". You will find some software for a searching of your chip. Finaly all depends on your mobile vendor

yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech

batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Could you tell us how you solved it?

batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Hi, I have the same problem with HTC Desire.
Could you tell how you solved this please?

I don't know if he did what he wrote, but a big mistake was the last step.
batmite said:
So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
Click to expand...
Click to collapse
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Sent by my fingers to your head.

eyahl said:
I don't know if he did what he wrote, but a big mistake was the last step.
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Click to expand...
Click to collapse
Have to disagree with you there, what he said was
installed ROM
wiped DATA
wiped CACHE
rebooted
The ROM ZIP would have been flashed into SYSTEM not DATA, so wipe shouldn't have caused a problem
question is did BOOT flash ok?

Bootloop help

So I was cruising around the Nexus S forums and found a rom I liked after I unlocked and rooted my phone.
I flashed Paranoid Android and then flashed the Matr1x kernel. Thus putting me in a neverending bootloop.
No ability to go back to CWM so I can't restore. And I can't put it in download mode so no ODIN.
What the heck do I do?
Can anyone help?
BTW if this is actually called a soft brick I'm sorry my terminology might be off.
Also I did this because the last phone I did extensive flashing with was an HTC Inspire 4G and it was easy to flash stuff just clear everything and flash what you wanted no bootloops. Sadly this phone not so much.

Hmm... No recovery...I've been stuck in a bootloop but I had recovery!
Sorry for the useless post, I cant help you..

Are you able to get into bootloader?

Usually when a bootloop occurs you should still be able to go in recovery.
When you say "no ability to access CWM" do you mean ROM Manager? Or the recovery mode?
What happens when you try to access the recovery mode?

same issue like urs
http://forum.xda-developers.com/showthread.php?t=1775933
try clean install;
flash Rom-Wiper.zip
flash Dalvik-Wiper.zip
then;
factory reset,
Format the system, data, cache, boot & partitions of your device.

I mean no access to recovery. CWM is Clock Work Mod Recovery. I have no access to fastboot either. The only thing my phone can do is bootloop.

You have to be mistaken.
Press power and volume up to get into fastboot ( bootloader). Then pick recovery....
That rom or kernel will not erase recovery. If your phone is in a bootloop it is making it past the bootloader

So it appears it as if I was mistaken. I got into fastboot and booted into CWM I'm still confused as to what I did, but I think I corrupted the Kernel.
It was the weirdest thing though. I tried it at least a dozen times, then I tried to run down the battery and try it again afterwards, and it didn't work so I gave up. Then I tried it again about 5 minutes ago and it worked. I'm sorry I cause you guys so much confusion. I've been doing this for so long I guess I just didn't doubt I was doing it right.

[Q] Trapped on my Infuse 4G's CWM boot recovery screen.

Okay, so I'm not stuck in some sort of infinite loop here with my Infuse, it will show the Samsung logo, then the Samsung logo with the Cyanogen Mod logo, then CWM Boot Recovery. the thing is, that is all I can do. I have tried rebooting several times, tried to install various ROMs and flavors I have, all installations seem to fail, I have tried wiping and clearing and all that jazz, but I cannot seem to get it to install to anything. Recovery doesn't seem to be working either.
Does anyone know what I should do? I have Odin, but since I still have access to CWM on the device, I thought it might be better to get some more opinions before I totally wipe my everything with a fresh rom.

Maybe help
acidRain burns said:
Okay, so I'm not stuck in some sort of infinite loop here with my Infuse, it will show the Samsung logo, then the Samsung logo with the Cyanogen Mod logo, then CWM Boot Recovery. the thing is, that is all I can do. I have tried rebooting several times, tried to install various ROMs and flavors I have, all installations seem to fail, I have tried wiping and clearing and all that jazz, but I cannot seem to get it to install to anything. Recovery doesn't seem to be working either.
Does anyone know what I should do? I have Odin, but since I still have access to CWM on the device, I thought it might be better to get some more opinions before I totally wipe my everything with a fresh rom.
Click to expand...
Click to collapse
I run into something the last few times. There may be a problem with you losing root. I tried to install the last CM11, and it kept ending in the error 7 thing. Try this. Do the reset thing in cwm, then partition and then dalvic. Take the battery out, and restart it into cwm (hold both volume keys and press power. Then start all over and do the reset, partition, and dalvik thing again, and then try to install rom. Hope it helps.

acidRain burns said:
Okay, so I'm not stuck in some sort of infinite loop here with my Infuse, it will show the Samsung logo, then the Samsung logo with the Cyanogen Mod logo, then CWM Boot Recovery. the thing is, that is all I can do.
Click to expand...
Click to collapse
Can you see Cid on the booting screen or CyanogenMod 4.x.x flashing on the booting screen only without Samsung logo? And can you boot to recovery? Are u on kitkat? I think it's a Gapps problem! Use Paranoid Gapps mini modular!
If so I had a similar problem some time ago. Was about to smack the phone on the wall as it remained on the booting load screen! But I removed battery every time it blocked (about 7 times) and reboot! Took battery out again and left the phone off about 4 hours. Remember to charge if you think necessary. Switched on and after 5 minutes loading (yeah it's long), it finally booted successfully!
If doesn't work, do a dirty flash, i.e, go to recovery, flash same or a newer ROM. back, back, Reboot device. If stuck or error 7 appears on recovery screen, reboot to recovery again and flash ROM again, followed by gapps(I seriously recommend using MINI MODULAR PA paranoid GAPPS), and reboot device. If boot is successful, consider doing a Wipe Dalvik Cache. This should not delete any files!
If nothing works, I guess Odin back to Stock

[Q] Stuck on Google Balloons

Hi everybody.
I hope I will get some help here.
My phone is rooted but still with stock ROM (4.4.4).
Couple of hours ago I used APToide to update 7 apps, one of which was "Google Search". After updates had finished, I would constantly get a message telling me that "Google Search had crashed", thus after several times I decided to uninstall it from APToide: this brought back the "default" one.
Besides the above, SuperSU was updated as well and it told me to update its binary: I did this as well, rebooted the phone and it seemed ok. I was able to open Twitter and from there open a URL in Chrome. As soon as I wanted to go back to my homescreen, nothing would happen: none of the buttons would do anything! Thus I decided to shut the phone down.
Now restarting the phone brings it up, it goes past the Google word and gets stuck at the four colored balloons!!! Now if I keep the power button pressed long enough, the phone simply reboots...
The weird thing is that the phone is getting WLAN and IP and it reacts to incoming Hangout messages vibrating!!!
Any help will be very much appreciated!
Thanks in advance,
F.

Since you are phone is already rooted, install custom recovery. I recommend TWRP recovery. Because you cannot boot up your device, use Nexus 5 toolkit or push it via adb to flash custom recovery.
Once you are in custom recovery, clear cache and dalvik. Hopefully that should do the trick. If not you may have to flash stock kernel via adb or Nexus 5 toolkit.

badboy47 said:
Since you are phone is already rooted, install custom recovery. I recommend TWRP recovery. You cannot boot up your device, use Nexus 5 toolkit or push it via adb to flash custom recovery.
Once you are in custom recovery, clear cache and dalvik. Hopefully that should do the trick. If not you may have to flash stock kernel via adb or Nexus 5 toolkit.
Click to expand...
Click to collapse
Hi badboy... in the meantime I got into stock recovery and did a full wipe/reset... now it works again...
Why do you recommend TWRP custom recovery?
Thanks,
F.

Glad you fixed it! TWRp has the best and friendly user interface with great features. I never have any problems flashing ROMs / kernels. Things like phone stuck on logo, not booting up, can be fixed in seconds in custom recovery. There is also cwm recovery. I used it for years but I eventually switched to twrp. Its so much better. I would say try both.

No do not try CWM. Use TWRP or PhilZ touch.

P5110 stuck in reboot loop, from OS?

Hi all,
I have a P5110 tab 2.
I rooted and installed CM 10 on this device some time ago, and it's been working fine for many months.
Recently, it's started rebooting itself from the OS - i.e not at boot logo etc - it actually gets into the OS, lets you do a few things for a few seconds, then thows you out and reboots.
This device has an older version of CWM on.
I can boot into CWM Recovery, have tried wiping dalvic, cache, - everything - but still the reboots.
Have tried to load twp from zip via CWM, it says installed ok. I reboot, go back into recovery, and its still this old version of CWM.
With this being an older version of CWM, it wont let me install the later versions of CWM.
Im thinking of reflashing the stock rom (4.x.x afair), to hopefully stop the reboots, so I can get into the OS and flash the later version of TWRP, so I can then flash a later version of CM.
All a PITA!
Question is - why does the p5110 keep rebooting, out of the OS?
I read somewhere that this could be a hardware issue - chip over heating or something.
Is this device worth bothering with?
Second question - why wont CWM let me install TWRP (from Zip in external SD, .img is in the zip) - even though it says it has installed it?
Any thoughts or assistance greatly appreciated!

Could this be the "dreaded emmc chip" issue?
If this was indeed the issue - would it boot to the OS at all?
I'm assuming not, and therefore this isnt the issue - can someone confirm?
http://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862

Maybe it is. You said you tried to flash the later versions of cwm but it didn't work yes? I think one of the symptoms is that you can't flash anything on the device because it became read-only. I may be wrong though so kindly check
EDIT: Maybe do a factory reset? If everything is still there after the wipe, 99% your emmc got read-only.