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?
Related
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.
I can access recovery, Hboot and flashboot, but no luck getting the phone to boot up past the splash screen, it think it, its the white screen with HTC logo on it
Have you tried a factory reset from recovery, then flashing a custom ROM?
post-mortem said:
Have you tried a factory reset from recovery, then flashing a custom ROM?
Click to expand...
Click to collapse
I have tried factory reset from hboot, my cwm recovery, and i cant find a custom rom. I have extracted the rom.zip from my original ruu found on htcdev. I put it on sd card and tried flashing thru recovery and thru hboot. I try doing fastboot, with the system.img and it actually crashes my pc, and when loading thru hboot, i get stuck at parsing .zip
I think you need to ask people who are more familiar with HTC devices. Type "htc rhyme" in the search bar at the top right of this page.
CWCOXXX said:
I have tried factory reset from hboot, my cwm recovery, and i cant find a custom rom. I have extracted the rom.zip from my original ruu found on htcdev. I put it on sd card and tried flashing thru recovery and thru hboot. I try doing fastboot, with the system.img and it actually crashes my pc, and when loading thru hboot, i get stuck at parsing .zip
Click to expand...
Click to collapse
Boot into fastboot and run the RUU.
Theonew said:
Boot into fastboot and run the RUU.
Click to expand...
Click to collapse
I did, believe me, I have spent hours and days googling, and every similar situation ppl have, the soution doesnt work for everybody, lol, and I just happen to be one of them. My rhyme is an upgraded OTA, from the original stock rom which is an ruu: RUU_Bliss_C_VERIZON_WWE_1.26.605.6_Radio_1.15.00.0816_NV_VZW2.67_release_214911_signed, and when i try running the ruu installer it says; From:image version 2.0.0.134076
To: 1.26.605.6, After 16% PROGRESS, ERROR [155]: UNKNOWN ERROR, The ROM upadate uti;ty couldn't update, please find correct RUU and update again. I dont know what else to do, ive been researching for a while and so now im in the XDA forums asking for help, before i was just searching for anything related to this problem with HTC rhyme, and not much about the rhyme it self is out there for support in these situations, so ive been researching the issue with all htc devices, and even android in general. I'll admit i am a noob at androids, but im actually pretty familiar with OS's and computers period. All help is much appreciated too, so thank you and if you know something i dont, please feel free to let me know where I am screwing up. I can get My CWM on it, and actually before all this, i had CWM touch recovery, somehow i lost it too and had to put the one i have now on it. i also parsed thru hboot my boot.img, and recovery before, , and it said it was successful. when doing system.img thru the PI46img.zip with boot and recovery, it freezes on parsing, and if i fastboot the system.img, it causes my computer to freeze, and i got the system.img from the rom.zip out of this RUU, that i mentioned above. ive done all the wiping from recovery of partitions that ppl had mentioned, and still no luck, and also when trying to flash it thru CWm it always says installation aborted. tahnk s for responding too man, ive noticed most questions with The HTC RHyme, get the shaft....and thats why i feel like im at a deadend, and i dont know if there is some number out there for support in theses situations, because HTC wont help after the bootloader has been unlocked, and it would seem a lil easier having someone walk you through it on either a live chat or over the phone
http://forum.xda-developers.com/images/smilies/confused.gif
.
BLISS XC SHIP S-ON RL
HBOOT-1.32.0011
RADIO-1.23.00.0224
eMMC-boot
HTC rhyme recovery prob.
Hi I really need help. I unlocked the boot loader from HTC Dev. Then rebooted the the bootloaderbfrom adb. The fastboot flash recovery. Everything was good until I pushed the mount through adb it gave me an error. Now every time I try a factory reset or try to go to recovery it takes me to the white HTC logo and nothing happens. Please help. The phone is switching on everything is working. I just can't factory reset or go to the recovery.
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
First for the One XL it is suggested you use TWRP and not CWM
You can get it here from their website .
It tells you how to fastboot flash it.
If you did an OTA to 2.20 or your device came with 2.20 you probably need to flash the boot.img /kernel
So in your CM10 zip, extract the boot image.
and use fastboot to flash the boot img with the command
fastboot flash boot boot.img
and that should help you out.
I also suggest reflashing the rom with TWRP just in case. Hope this helps.
Can adb see the phone?
FrustratedAndConfused said:
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
Click to expand...
Click to collapse
This is the one xl correct, not the international on x?
If you can get anything on your screen, your phone isn't hard-bricked.
First, which phone do you have? ClockworkMod Touch Recovery does not work on the AT&T One X (One XL). If you tried flashing a ROM through it, it's not going to work and it's probably not booting up because the ROM is corrupted.
I would start with flashing a new recovery in adb. Use TWRP, because even the basic CWM is not supported for this phone and can cause issues.
Can you get into recovery? If so is the SD card mountable?
First time I flashed i had a similar issue where the SD couldn't mount. I ended up having to run the factory RUU after relocking the bootloader & then start again. I waited for a later nightly to come out. Also seems to go better if you flash a different rom first like viper.
NismoR31 said:
Can you get into recovery? If so is the SD card mountable?
Click to expand...
Click to collapse
Doesn't matter. He flashed the wrong recovery (not for our phone). There is not Touch CWM for our version.
i should really refresh pages before replying
Hey guys!
My Sensation recently died on me, or should I say it won't boot ANY ROM available here. It just enters bootloop and cuts off on first glimpse of the boot animation (or sometimes after fresh ext4 format it just hangs on the splash screen - white bg with HTC). I have installed 4EXT recovery because I thought it was due to CWM Recovery. I had ViperS installed andd I got occasional random reboots followed by bootloops. After pulling the battery out the ROM booted fine until today. Now I can't boot any ROM, flashing goes OK, I tried restoring my factory ROM, but that just bootloops and cuts off at the beats logo, too.
What to do? Is there any fix?
5ageman said:
Hey guys!
My Sensation recently died on me, or should I say it won't boot ANY ROM available here. It just enters bootloop and cuts off on first glimpse of the boot animation (or sometimes after fresh ext4 format it just hangs on the splash screen - white bg with HTC). I have installed 4EXT recovery because I thought it was due to CWM Recovery. I had ViperS installed andd I got occasional random reboots followed by bootloops. After pulling the battery out the ROM booted fine until today. Now I can't boot any ROM, flashing goes OK, I tried restoring my factory ROM, but that just bootloops and cuts off at the beats logo, too.
What to do? Is there any fix?
Click to expand...
Click to collapse
S-ON or S-OFF?
rzr86 said:
S-ON or S-OFF?
Click to expand...
Click to collapse
It's all in my sig, I only have 1.27 now. S-OFF, rooted, unlocked. Flashed many ROMs and they worked fine, even now every ROM installs without any error but they all get stuck in bootloop
5ageman said:
It's all in my sig, I only have 1.27 now. S-OFF, rooted, unlocked. Flashed many ROMs and they worked fine, even now every ROM installs without any error but they all get stuck in bootloop
Click to expand...
Click to collapse
i am really blind
ok.i assume you have now 4ext
if yes then:
format all partitons except sdcard
flash the rom
otherwise flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1 step)
rzr86 said:
i am really blind
ok.i assume you have now 4ext
if yes then:
format all partitons except sdcard
flash the rom
otherwise flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1 step)
Click to expand...
Click to collapse
It happens
I tried both, 4EXT wipe and flashing the boot.img, but that didn't help
Now, this is weird! I thought after countless tries to try again, just before I give up, and try restoring my CWMR backup of the stock factory ROM I had and after one bootloop the phone started booting and now works normally :silly: even after couple of restarts.
Thanks for trying to help, but now I'm afraid to flash anything else on it. Could it be my hardware is not right?
Hey Guys. Im running cm12s on my oneplus one, and i would like to switch to oxygenOS because they are getting the touchscreen firmware fixes. Ive flashed recoveries onto multiple phones without this issue before.
I downloaded twrp, booted the phone into fastboot, unlocked it, got the success signal, flashed it, again, success, and then rebooted. Then i powered down and booted to recovery aaaand..... stock recovery. WTF? So i wipe all user data and clear the cache with the stock recovery and try again. Nope. Its still the stock recovery. i dont understand it. I tried with CWM aswell. It says success, so why did it not work? I booted into the OS and checked developer settings, and disabled update recovery and all that, Nevertheless, when i flash TWRP or CWM, it does not work. I dont understand how this could happen.
I followed the steps from the Official guide on the official oneplus forum, It wont let me post a link.
I am using an OEM samsung cable.
Can anyone help me?
fastboot reboot-bootloader ; just after recovery flash.
Orphee said:
fastboot reboot-bootloader ; just after recovery flash.
Click to expand...
Click to collapse
Alright, I've just tried that. After flashing it, i Ran this command and as expected it rebooted back to the bootloader. Nothing else todo there, so i rebooted and booted to the recovery. It STILL boots to the stock recovery! So i tried again, but this time, i flashed it a second time after rebooting to the bootloader, but that still has not worked. is my unit defective? I will try now with another computer.
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
I figured it out!
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
theangrynoob5 said:
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
Click to expand...
Click to collapse
CM didn't just do that to you, it's happened to every single person who's tried to flash TWRP after taking the Lollipop update, that's why the question is included in the FAQ thread.
XDA Moderator
Transmitted via Bacon