Recently I had a brick on my Desire, which caused that I couldn't boot past the HTC Boot logo. I already made a thread about it, but without a solution. I sent my desire back for repair, but I think it wouldn't be a good idea if we all had to do this. So I would advice everyone to unroot, untill one of the genius devs has found a solution.
Symptoms:
-Boot stuck at HTC Boot Logo
-Going in to recovery takes a long time
-Recovery usually doesn't even work
Posible Solution:
-Some users are reporting, they can boot without SD and SIM (dont know if repartitioning the sd totally solves everything)
-Some users report, say that the situation is solved if you flash a diffirent rom (didn't work for me)
Finally I would like to motivate my opinion why people should unroot.
When I posted my first entry I though I was the only one, but now more and more people are getting this problem.
This problem is as said above probably something which can be solved but right now its a dangerous development.
This is the first I've heard of this issue and it not being solved by the SD card removal or reformatting.
How many people have this problem unresolved, and what exactly were you running when it happened? What rom, radio, which recovery was used etc.
I have rooted my phone and flashed about 20-30 ROM's and haven't had a single problem.
I must have been lucky to get a phone that don't brick so easy. I hope that you who have problem with this get a solution soon.
socktug said:
This is the first I've heard of this issue and it not being solved by the SD card removal or reformatting.
How many people have this problem unresolved, and what exactly were you running when it happened? What rom, radio, which recovery was used etc.
Click to expand...
Click to collapse
I've read about 5 diffirent posts about this. All the post are on the first two pages i think. I was running DeFrost, and used r5's recovery. And I was running the most recent radio that is now availible
@Milioo So what you said make me feel like you blame all the devs here at XDA comminity bricking your phone and have to be responsible for your bricked phone and it was bricked because of THEM. Hello, when you first rooted it and started to get cooked roms into it, you should have known there are chance that you phone would be bricked. That's always the first thing you need to put in your mind and every single dev has told so.
So if I were you, I would just shut and find the way to solve the problem or ask for solution. Anyone here would try to help. Clearly, you are not asking for solution but complaining.
khoaitaychienvn said:
@Milioo So what you said make me feel like you blame all the devs here at XDA comminity bricking your phone and have to be responsible for your bricked phone and it was bricked because of THEM. Hello, when you first rooted it and started to get cooked roms into it, you should have known there are chance that you phone would be bricked. That's always the first thing you need to put in your mind and every single dev has told so.
So if I were you, I would just shut and find the way to solve the problem or ask for solution. Anyone here would try to help. Clearly, you are not asking for solution but complaining.
Click to expand...
Click to collapse
I'm really sorry if i made you or anyone else feel like that. I've always have great respect for the devs who work their asses of to make great roms for us. and always look forward to new cooked roms made by them. The only reason the I made this thread is that i don't want other people to get bricked.
Could you please tell me where i implied that the devs were a fault here?
And finally, if anyone is to blame its HTC who are working so strongly against people putting custom roms on their phone, who ust want to make their user experience better.
I've had the same problem that the phone wont boot at all and get stuck at the white HTC Logo.
But it was easy fixed with a run of all the wipe options, and then flash the rom again.
Giland said:
I've had the same problem that the phone wont boot at all and get stuck at the white HTC Logo.
But it was easy fixed with a run of all the wipe options, and then flash the rom again.
Click to expand...
Click to collapse
Ok guys i'm sorry for posting this thread, clearly it isn't really a problem. I just wanted to post it because these instructions dind't work for me. But i will gladly remove this thread (If its possible)
hi mate .
I have the exact problem and I think it is a real problem - see my thread
Can someone help me - stuck on htc boot - very strange situation -- I was not allowed to put the link to it...
I did everything do get it started but no luck at all. is strange that can access fastboot, the pc recognize the device but the recovery didn't work at all, even one time I couldn't get it: when I push the power button the logo htc screen just appear and get stuck there.
so if every one has any idea what could be please help us,there are more than a week I tried every day to get it work again.
many thanks.
I had this problem months ago I was running my desire on a custom rom had a2sd installed formated the sd card and the phone wouldnt boot reflashed a fresh rom and everything worked fine again.
I too had this problem...
You didn't by any chance apply the unrevoked recovery did you? If so, did you also use ROM Manager.
If you read the top page of the unrevoked thread you'll see that it says that the two combined cause a problem with flash memory. To fix the brick I ran an offical HTC RUU, re-rooted using Paul's method, and then re applied unrevoked. I now definitely DO NOT use Rom manager.
Hope it was some help mate.
Yes best option if u can access hboot is to go back to stock using ruu
then re root it shd solve all probs
in my case I can acces hboot.
I did also stock ruu and PB99IMG.zip, and installed ok but just won't load OS getting stuck again on htc logo screen. I mention that I had hboot 0.75 and after stock ruu I got hboot 0.80...
still in truble, really don't know what else to try, because recovery don't work at all and I can't install a new recovery.
Is there a way to flash a recovery from fastoob???
RUU
When I flashed a RUU, it was still stuck at the bootloop.
Milioo said:
When I flashed a RUU, it was still stuck at the bootloop.
Click to expand...
Click to collapse
If you can do a logcat of the boot-loop and pastebin it. We'll see what the problem is...
In terminal or command, write adb logcat or adb-windows logcat and then run it for the duration of the loop.
laupc said:
in my case I can acces hboot.
I did also stock ruu and PB99IMG.zip, and installed ok but just won't load OS getting stuck again on htc logo screen. I mention that I had hboot 0.75 and after stock ruu I got hboot 0.80...
still in truble, really don't know what else to try, because recovery don't work at all and I can't install a new recovery.
Is there a way to flash a recovery from fastoob???
Click to expand...
Click to collapse
Yea the RUU upgrades your H-boot, Does just running the RUU achieve anything, you should just have a fresh clean non-rooted ROM load up on your device straight after running it?
Pop onto irc and visit the modaco chat room....we can have a talk about possible fixes
chat.freenode.net
#modaco
Feel free to look for me, and message me
just give the adb logcat comand while in bootloop and saying waiting for device and that's all
Have you tried restoring a good misc image? Just incase this could be related to that like other forms of brick are...
how can I restore the misc?
laupc said:
how can I restore the misc?
Click to expand...
Click to collapse
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
Although... with the mention of recovery taking an age, is that standard recovery, unrevoked or fake flash?
The above method uses the standard HTC recovery image, similar to fakeflash does. Worth a try *if* you can get it to work... May or may not resolve the issue though (I'm just guessing here) but could possibly in a weird kinda way help you to do a successful RUU restore using the PB image method...
Related
I just recently tried to flash the Rom DeFroST using the Clockworkmod.
I can now not boot into the Rom (I get a looping splash, the cool colourfull nexus one X animation) and if I try boot into clockworkmod, it stalls at the Telstra splash (still image). I also cannot browse any files on the SD card, I have to remove it and insert it into the adpater.
I'm really afraid I've bricked it :/ Can someone help me? I can still get into HBOOT.
a1m said:
I just recently tried to flash the Rom DeFroST using the Clockworkmod.
I can now not boot into the Rom (I get a looping splash, the cool colourfull nexus one X animation) and if I try boot into clockworkmod, it stalls at the Telstra splash (still image). I also cannot browse any files on the SD card, I have to remove it and insert it into the adpater.
I'm really afraid I've bricked it :/ Can someone help me? I can still get into HBOOT.
Click to expand...
Click to collapse
your phone is not bricked.
did you root your phone first?
I have a Telstra phone and I had to flash an official WWE ROM first, then use gold card to root my phone and now I can flash any ROM.
My phone came unlocked, it was unlocked by the company from whom I ordered it from. Yes I did root it first. Atleast, I assume I did...
I used the linux version of rewvoked 3 and it completed with out errors. It has been trying to boot for approximately 13 minutes now and is still stuck on the animated nexus one splash...
It is now into its 21st minute, I somehow doubt it's going to boot
a1m said:
My phone came unlocked, it was unlocked by the company from whom I ordered it from. Yes I did root it first. Atleast, I assume I did...
I used the linux version of rewvoked 3 and it completed with out errors. It has been trying to boot for approximately 13 minutes now and is still stuck on the animated nexus one splash...
Click to expand...
Click to collapse
Unlocked and rooted are two different things. Is this your first flash of a custom ROM for the Desire?
Whenever you flash a ROM for the first time it does take a LONG time for it to process. I don't remember how long, can't tell you if 15 min is to long. You can always re-flash by putting the phone into recovery mode manually and using the USB method for flashing.
Yes this is my first ROM.
That's the problem, the phone stalls if I try and put the phone into recovery mode... :/ Unless that too is meant to take a very long time?
Ok, surely 1/2 an hour is beyond what it should take?
a1m said:
Ok, surely 1/2 an hour is beyond what it should take?
Click to expand...
Click to collapse
you need to start over.
did you read ALL of this before you started (not trying to insult you in anyway, just question) http://forum.xda-developers.com/showthread.php?t=696189
it will tell you how to put is into recovery mode and then how to flash using USB
Yes I did, although I did end up following separate guides as my boot loader was 0.83 as opposed to 0.8 and 0.75 or whatever those guides included. Ok, start over. Sounds good... I'll try that, but you'll likely hear back from me!
a1m said:
Yes I did, although I did end up following separate guides as my boot loader was 0.83 as opposed to 0.8 and 0.75 or whatever those guides included. Ok, start over. Sounds good... I'll try that, but you'll likely hear back from me!
Click to expand...
Click to collapse
My boot is .80, I am not sure if it changed when I flashed an official ROM first. I did that to get rid of all the Telstra stuff.
One thing you can try is to flash an official WWE ROM first. Then after you can go onto a custom ROM.
Ok, clockwork mod is working again, now to install thisWWE ROM, what exactly is it, where can I get it and what should I do?
Double post sorry
a1m said:
Ok, clockwork mod is working again, now to install thisWWE ROM, what exactly is it, where can I get it and what should I do?
Click to expand...
Click to collapse
here is the link to official ROM for the HTC Desire http://forum.xda-developers.com/showthread.php?t=695667
They may have a radio in them as well. Once you flash one make sure your desire works. Then try flashing your custom ROM. Many custom ROM's need to have the latest radio so make sure you follow the instruction for that ROM and the radio that ROM uses.
alwayslearning said:
here is the link to official ROM for the HTC Desire http://forum.xda-developers.com/showthread.php?t=695667
They may have a radio in them as well. Once you flash one make sure your desire works. Then try flashing your custom ROM. Many custom ROM's need to have the latest radio so make sure you follow the instruction for that ROM and the radio that ROM uses.
Click to expand...
Click to collapse
one more thing, once you get an official ROM working, go to market and download ROM manager, use it to flash a custom ROM, it might work better for you.
Ok thankyou! But to me a radio is a small transistor based device that uses variable capacitance in order to change frequencies... What is it in this case?
By the way, I thank you for your help, you've been of great assistance!
EDIT: One more thing, that's a lot of roms, which one do I want? Any? do I want signed or unsigned?
Ok I'm even more confused, they're mostly .exe's, how do I use them?
EDIT: It also says they're not rooted, does that mean I have to re-root my phone again?
Having the exact same problem as you, also a telstra phone.
Boots and gets stuck on the "X" colored animation.
If you get it going, please post here what you did
a1m said:
Ok I'm even more confused, they're mostly .exe's, how do I use them?
EDIT: It also says they're not rooted, does that mean I have to re-root my phone again?
Click to expand...
Click to collapse
A radio is the software that works your phone, GPS and wifi portions of the device.
use the first ROM on the list. Hold the volume down key and press the power key at the same time, hold them until you enter the recover screen. it will take about 30 sec to process, use the volume down key to select clear storage follow the instructions and this should set your phone back to factory setting (using the last ROM that worked on your phone). Your phone should be working and you should be able to boot-up.
From this point you will be able to connect your phone to your PC then click on the ROM (exe file) and follow the instructions to flash the official ROM
let me know what happens.
Ok so i need a windows PC? I'm on Ubuntu.
My Windows decided to implode after an update earlier this evening. Will probably leave that to download and go to bed. I'll post here tomorrow with how I get on tomorrow morning!
Ok, so I was trying to get my Evo running on the Verizon network, and ended up messing with some NV items that I probably shouldn't have. Long story short it's stuck in a boot loop. I can get to the bootloader just fine, but recovery is a no-go. Also, I was able to do an RUU flash from fastboot, but that didn't fix the boot loop. What should I do?! Please help me!
Sounds like you took a big step and should not have. Next why would you want to go to Verizon? you can not use 4g over there. i think there is a post here or on another android site on getting your phone out of a boot loop with no recovery. Search is your friend
http://lmgtfy.com/?q=stuck+in+boot+loop+without+recovery+android+evo
I found a solution to this exact problem.
Flintr said:
Ok, so I was trying to get my Evo running on the Verizon network, and ended up messing with some NV items that I probably shouldn't have. Long story short it's stuck in a boot loop. I can get to the bootloader just fine, but recovery is a no-go. Also, I was able to do an RUU flash from fastboot, but that didn't fix the boot loop. What should I do?! Please help me!
Click to expand...
Click to collapse
I found a solution to this exact problem after I wrote some nv items from a boost phone. no recovery, evo 4g boot loop over and over till the battery dies and only fastboot commands work. dont even think about saying flashing the boot or system images to fix this thats a no no, it will not work although it wont break the phone either. If anyone is in this same awful position and cant find a fix just pm me or reply to this post and i'll write a full tutorial of what i did. I just dont wanna waste my time and there might be an answer out there already. All i know is that I could'nt find one anywhere and I am literally a part of every mobile forum you can think of. Anyone interested?
marley183rd said:
I found a solution to this exact problem after I wrote some nv items from a boost phone. no recovery, evo 4g boot loop over and over till the battery dies and only fastboot commands work. dont even think about saying flashing the boot or system images to fix this thats a no no, it will not work although it wont break the phone either. If anyone is in this same awful position and cant find a fix just pm me or reply to this post and i'll write a full tutorial of what i did. I just dont wanna waste my time and there might be an answer out there already. All i know is that I could'nt find one anywhere and I am literally a part of every mobile forum you can think of. Anyone interested?
Click to expand...
Click to collapse
i REALLY COULD USE YOUR HELP
need help
I have the same problem, i used a tp2 as a donor, everytihng qorked but data, after copying the needed nv items(CDMA WS 2.7) and still didnt work i copied ALL available items from tp2 to the evo OOOOUCH , now i am at the endless boot loops , the only thing working is fastboot but not adb. i flash all types of roms with no luck, please tell us what you did to get it back running, you help will be appriciated
Need help
I have the same problem, i used a tp2 as a donor, everytihng qorked but data, after copying the needed nv items(CDMA WS 2.7) and still didnt work i copied ALL available items from tp2 to the evo OOOOUCH , now i am at the endless boot loops , the only thing working is fastboot but not adb. i flash all types of roms with no luck, please tell us what you did to get it back running, you help will be appriciated
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
I am experiencing the boot loop issue also. Really weird, all I have done is root via UnRevoked, use Rom Manager to install CM 6.1.2, and been running this ROM exclusively. I have never overclocked, or even installed or used any task killers in CM 6... I started noticing a couple weeks ago some odd force closes and sync issues with gmail that would come and go. Then, my phone would reboot every once in a while. Sometimes when I was using it, most of the time while it was just sitting on the counter. Then one day it just started the boot loop. Vibrate, white HTC Evo screen for a few seconds, then dark again, over and over. I can't boot into recovery, and have tried a bunch of recovery images (they unpack and update succeeds but attempting to boot to recovery just starts the loop again). I thought about unrooting and bringing the phone back to the store but the instructions I found for unrooting require me to at least get into recovery.... At the time I rooted (Sept '10) I had all the latest OTA... any advice for me to try?
S-OFF
HBOOT-2.10.0001
RADIO 2.15.00.11.19
I made a writeup
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54needed files.
Update
So I never could fix this issue, although I got some really great suggestions and learned a lot from cutthroatamft.
Ended up just deciding to completely brick the phone (in case the Sprint tech might check my bootloader screen for S-OFF). To do this, I just removed the battery while I was flashing an engineering image (while it was updating the radio). After that, not only would the phone not power on at all, but the charging LED wouldn't even light up when plugged in to a power source. They gave me a refurbed Evo.
Haha, I was able to fix my Evo (dont remember what I did) but I have since sold it.
dwreck_ said:
So I never could fix this issue, although I got some really great suggestions and learned a lot from cutthroatamft.
Ended up just deciding to completely brick the phone (in case the Sprint tech might check my bootloader screen for S-OFF). To do this, I just removed the battery while I was flashing an engineering image (while it was updating the radio). After that, not only would the phone not power on at all, but the charging LED wouldn't even light up when plugged in to a power source. They gave me a refurbed Evo.
Click to expand...
Click to collapse
Do you mind pointing me to the image you flashed? I just pulled the battery while flashing a radio, but i'm still booting haha.
You should find it fairly easy if you search Google for eng-pc36img.zip
Looks like the first link.
Sent from my Evo using XDA App
I wish I could, but honestly it's been so long that I dont have any idea.
Thanks cutthroat.
dwreck, at what point did you pull?
I've pulled it twice while it was updating Radio_V2, with the red bar about 1/3 of the way, and nothing about my phone seems to change.
Did you pull a little later? Or did you pull during Radio_Cust? That thing is hard to catch, it updates quickly.
My friend says it took him about a hundred times to fully brick his Evo. Just keep trying I suppose.
Sent from my Evo using XDA App
Sprint was backordered on Evo's. It might take me more than a week to get another one, and it's still 35 bucks. Cutthroat or dwreck, do either of you guys know if it would be safe for me to send my Evo into HTC? I did the battery pull (it took about 20 tries) and the phone doesn't turn on, no led or anything. Will htc know it's rooted regardless?
You should be fine to send it to HTC, my friend has gotten two replaced that exact way. He had no issues with them finding out his were rooted.
Sent from my Evo using XDA App
pthr3e said:
i REALLY COULD USE YOUR HELP
Click to expand...
Click to collapse
Please refer to the post below for a fix. This will in no way help you if you started having reboots and then a bootloop while running CM7. It is meant to fix issues that come from corrupted NV items only.
http://forum.xda-developers.com/showpost.php?p=16133086&postcount=54
I'd just like to take a sec to give props to cutthroat. His guide is GREAT if you've screwed up your NV files (unfortunately that wasn't my problem). Anyways I appreciate you helping me out even after that.
Hey guys, I tried to perma root my wife's G2 last night using Visionary+ r14 but when it tried to reboot it doesn't get past the green and white "HTC" screen, so now I have a couple of questions.
I bought this phone from someone off of Craigslist and it was working great until I tried to root it so it is technically out of warranty do you think I can get it replaced since everything is still stock?
Also I tried to apply the HTC OTA update to fix it and I still have the problem, is there anything I can do to repair this phone? Thanks in advance guys and mahalo!
Okay pull your battery out and put it back in..after dat press power button and volume down button until you get to the recovery screen and do a factory reset..
Sent from my HTC Vision using XDA App
Thanks for the reply jboiii15. I did a factory reset before I flashed the OTA update and I have factory reset several times but still no go. I appreciate you taking the time to help me out.
Did you try this? http://forum.xda-developers.com/showthread.php?t=842495
aznsnake666 said:
Did you try this? http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
I haven't tried it because I can't get ADB to work with the phone the way it is, Fastboot works but ADB just shows nothing there while I'm in recovery or the boot screen. Thank you also for the reply. My wife is pissed lol.
Try to extract the ROM from the official RUU and rename it to PC10IMG.zip. Put this on the root of your SD card and boot into bootloader and leave it to work. This should solve your problem Fingers Crossed
JD
do you have s-off??
I don't have S-OFF as I just started the rooting procedure when it decided to take a dump on me, after this I don't think my wife will want me to root any more of her phones although I know she'll miss it after having a rooted G1 running CM and a rooted Slide running Chromatic. Good thing I didn't sell her Slide yet lol.
I'll try to find information on the PC10IMG.zip method now and see what can be done.
Thank you guys for all the help, I really appreciate it all.
itsmekeoni said:
I don't have S-OFF as I just started the rooting procedure when it decided to take a dump on me, after this I don't think my wife will want me to root any more of her phones although I know she'll miss it after having a rooted G1 running CM and a rooted Slide running Chromatic. Good thing I didn't sell her Slide yet lol.
I'll try to find information on the PC10IMG.zip method now and see what can be done.
Thank you guys for all the help, I really appreciate it all.
Click to expand...
Click to collapse
I think the rooting process has corrupted your kernel or rom, it is rare to get a brick from just the visionary process, but i know there has at least been one that this has happened to.
Report back to tell us if the extracted ROM worked for you, there is still hope;')
JD
Oh man this is just getting worse lol. I had the phone sitting here plugged into my laptop while the phone was in the Hboot screen where you can select Fastboot, Recovery and so on. All of a sudden my here Windows give off the noise as if something was connected or disconnected from my computer and I see the screen shut off on the G2 with a red light blinking. Now the phone doesn't power on and the red light blinks while the phone is plugged into the computer but doesn't power on.
As I was typing this the red light came on solid as if it is charging now, maybe it doesn't charge while in that screen and the battery just died I dunno, strange.
JupiterDroid said:
I think the rooting process has corrupted your kernel or rom, it is rare to get a brick from just the visionary process, but i know there has at least been one that this has happened to.
Report back to tell us if the extracted ROM worked for you, there is still hope;')
JD
Click to expand...
Click to collapse
Well I called T-Mobile and they are sending out a new phone, I'm unsure if I should still mess with it or not. I did flash the TMOUSA OTA update and that didn't help, I didn't unpack it to see if it contained a new Kernel but I'm sure it had a new system.img, still think it is one of those that is messed up?
I'm having a hard time finding the things to get the PC10IMG.zip going, work is calling me in different directions and my A.D.D is kicking in lol.
try this http://forum.xda-developers.com/showthread.php?t=855764 i had the same problem like you, steviewevie told me to do it, if you have problem to connect your g2 with sdk download pda net, it works for me and now i have my g2 back with the new root... just do what it said on that link believe me works...
P.D. I am a androidnoober always have a iphone and this was my first time using sdk adb or whatever name is and I did it
Thanks AndroidNoober, I've seen that link in my search for an answer to my problem. One of the issues that is making this harder is that after the phone "bricked" it lost ADB connectivity. I've tried it on two computers that have a properly working ADB (I test it with my N1 and 3G Slide) and it used to work with the G2 but now I can't get it to see the phone, I've heard Recovery has ADB blocked.
semi bricked attempting permaroot
i attempted permaroot and semi bricked my phone. will not boot past htc screen. i can't get adb to work. i am trying to get pdanet installed but it keeps getting stuck on installing on phone. can it install while phone is in recovery mode? i have had no sucess trying to figure this out on my own and phone is not covered with a warranty
i have gotten the phone to read an update.zip file.
it is reading the pc10img.zip as well.
now i just have to get past the htc screen.
i do have s-on as i had just started the process.
any help would be appreciated
So before everyone yells because of my inability to search the forum, please understand that not only have i searched this forum, but just about every other one. And if someone finds a thread with an answer to my question than i will admit defeat and have myself stoned and crucified.
I will greatly appreciate anyone's and everyone's help.
History in cliffnotes
Rooted with Unrevoked about a month ago, since then been running CM 6.
Have been happy with just using stock CM 6 and nothing else, haven't flashed any other kernels, radios, or for that matter roms.
Have always had problems with random reboots but didn't care.
Last night my phone appeared to have the desire to random reboot, and on start up got into a boot loop, just HTC splash boot loop. I can get into bootloader but if i try to go to recovery it is just more boot loops.
I'm running mac OS X however i eventually just tried running RUU on my roommates computer but to no avail, mostly, i think, because my phone can't boot into a state where its recognized by the program or sync, etc...
The real problem
As of now i've gone as far as basically completely unrooting, using a pc36img that i found through you guys here
So if you guys have any ideas, at this point, i'm completely willing to try them because, this was completely random that it happened, and i really am at a complete loss as to what to do besides buy a new phone.
i love you all in a masculine plutonic way. thanks.
well you could always re-root with unrevoked. all it needs is bootloader mode to root it and then once its done, flash a rooted rom on it, then proceed to unroot.
EDIT:
btw, i am a mac user too and unrevoked works great. if it fails, run it again. and no need to use an ruu, look up a thread in our development section titled shpped roms and they have pc36img versions of the ruu. you will be able to root with your mac and unroot all on the device. unrevoked has an s-on zip on their web page. to unroot it, flash the s-on zip then run the pc36img zip from the base of your sd card. thats all!
EDIT#2:
YOU CAN ALWAYS FLASH A RECOVERY VIA BOOTLOADER ALSO AND FLASH A ROM. LET ME KNOW WHICH RECOVERY YOU PREFFER, I GOT BOTH CLOCKWORKMOD AND RA.
EDIT#3: LOL, Sorry i didnt see that you mentioned a pc36img to unroot.
why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom
t3project said:
why dont you just download download the recovery img of amon_ra 2.2.1 in pc36img format and run it from boot loader. done, problem solved.
if that doesnt work download caukulins format all zip and run it and them reload your recovery and rom
Click to expand...
Click to collapse
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!
Well since you can't get into recovery, we suggested to flash a recovery in pc36img.zip format in bootloader mode.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
paulieb81 said:
I am not trying to thread jack, but i too am having the same problem. I am not a noob at flashing and I am stuck at the white Evo screen and it just reboots when I click on recovery from the boot loader.
I too have flashed the recovery image from amen ra and it flashed ok, but each time I reboot and try to get into recovery it just reboots, so that did not fix getting into recovery.
The problem with the above suggestion is that you need to be able to boot into a recovery to use Caukulins format all zip, and if you can't get into recovery it does no good.
If anyone has any other suggestions please let the both of us know!
Click to expand...
Click to collapse
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader
t3project said:
thats why i said flash a recovery in pc36img format first. more specifically this:
http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
rename to pc36img.zip and boot into bootloader
Click to expand...
Click to collapse
If you read my message you will see that I DID flash a recovery, that same one you just linked, and it flashed ok, but when i restart and choose to enter the recovery the phone just reboots again!
Did you solve this?
Yes I did, I went back to the store and had them replace the phone. I could not get it to boot into recovery for some reason.
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
Did they give you any problems about s-off being visible in the bootloader when you got your phone replaced? I'm to that point of taking it back with the EXACT same problem but I didn't know if it was an issue. (or is there any trick to get s-on back without being able to load into recovery i.e. a fastboot command?)
i was worried about the s-off as well because i also was unable to change that. all i could find for that was the s-on tool but since u cant actually flash anything, had to leave it s-off. i even tried a battery pull during the radio update on a pc36img so that they wouldnt be able to get to bootloader but i couldnt even brick it. i live more than 50 miles from a sprint store so they didnt make me drive to a sprint store. they sent me a replacement and i mailed my evo back. on the paperwork for the new phone they said i could still be charged 75 dollars for a recoverable phone and 125 for an unrecoverable phone. it was probably 2 weeks ago or so when i sent my old broken evo back and i havent been billed yet so i dont know what if anything they will charge. when i talked to the sprint tech on the phone i told him it was rooted because i knew they would see the s-off and i didnt want to get screwed when i sent them my broken phone and they said "u rooted, ur problem" but he said he would still replace it and he did.
k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm in the same boat buckley. I don't get it?! I did run cm for a couple days but I was always looking at my phone wondering if something was going to happen. Almost gave myself a panic attack so I just went back to sense, lol.
ChacocII said:
heppened to me too and since then ive seen at least 5 cases of this exact same problem from cm7 roms. so far no one has found a way to fix it that has been posted here. we have all had to have our phones replaced.
Click to expand...
Click to collapse
And I just wanted to say, that although you've seen 5, and I've seen around 10, and that does suck, that the fact is, that this is an EXTREMELY low percentage of CM users that are experiencing this problem. With that noted, it's still enough for me to use a different rom, at least until someone can at least figure out what caused that to happen. I am just extremely curious, as to what the actual malfunction with the device is, when this sort of things happens. And why it seems to only be happening on CM. (at least from the reports I've seen around here)
Add me to the list of people with this problem. I think I'm going to try my chances at the Sprint store. They've been good to me so far.
k2buckley said:
I dont know what causes this, but this is like the 10th person on a CM rom that's had this exact scenario. Its weird how it happens out of the blue, and then RUU and pc36img just don't work. Very strange. I was just trying to help a guy the other day in this exact scenario. Nothing would get him out of the splash screen. No RUU, PC36IMG of recovery OR a factory ROM, fastboot RUU didn't work. Nothing. Just bricked at the bootloader somehow. I always thought if you could get to the bootloader then you could recovery, but lately there have been quite a few of this exact scenario, and each one was on the same rom. I would love to know what causes this, when the phone is just sitting there, and then goes into a bootloop out of the blue, and then this is the result. It's leaving me frightened to run CM, seriously. What on earth could be causing this type of thing?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It has nothing to do with CM. It is clearly a hardware problem. It has happened on other roms, but more likely to happen to someone using CM as it is the most used Rom.
Sent from my PC36100 using XDA Premium App
Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..
jkxklutz said:
Sorry to open this again, but I'm having the same issue. I'm actually on the HTC Sensation, but I'm posting this here because after hours of searching, this is the ONLY place that seemed to address this seriously.
The reboots began even on the original stock rom. I bought it from a guy on Craigslist, but I'm fairly certain it was the original stock rom, with S-off, unrooted, etc. I thought flashing other roms would help, but they haven't.
Here's my furthest observations thus far:
I have actually found a way to get out of this incessant boot loop. As you said, even recovery is impossible. I was so confused when everyone kept telling me to just go into bootloader mode and go to recovery. I can always get into bootloader mode, but recovery, as you guys said, is pointless, because it just boot loops.
However! I have found that if I leave the battery out for an extended period of time, maybe an hour to several hours later, upon inserting the battery back in, I'm able to load up correctly. But that doesn't last long. Usually I only get one chance. If I use that chance to go into recovery mode the next time it'll just boot loop again.
So now I really think it's something to do with the battery, because when I leave it out for a while, I can finally boot up the phone or get into recovery. I do know that HTC has that lame battery problem of boot looping when the battery is low, so do you guys think that it could be related to the battery stats? When my next "battery-free shift" is over, I'm going to try charging the phone and wiping battery stats.
Sometimes the other way I can get out of the boot loop is to charge the phone fully until it's green, so I'm just not sure. This is insane... any input at all would be greatly appreciated..
Click to expand...
Click to collapse
If its anything like the evo you might want to try and wipe cache and dalvik cache when you get into recovery let it boot back up if that doesn't work try to fix permission if that doesn't work wipe battery stats when your phone is at 100% using battery calibration app and if none of that works do a full wipe and flash a new ROM or unroot and run the ruu of the stock ROM .
Sorry I know nothing about that phone so IDK if any of that will work for you just trying to help and those are pretty much the steps I would take.
Sent from my PC36100 using XDA App
Happened to me
Hey guys this happened to me and i was running cm and sense roms i have had alot of experience with this and its an actual glitch that causes the os to stack on each other and confuse the boot the only way to fix is to wipe the entire phone back to stock if that dosent work call sprint and they gladly replace ur phone due to manufacture defect its been happening to unrooted phones also from the updatesnot being installed properly phone needs to be wiped every time u do a new rom
Hi im new here and hope this is in the right place. I have a htc m8 on o2 network in the uk. Its basically not booting past the htc logo then it restarts again. I have booted into the boot loader via power button and volume down. When i go into recovery there is nothing to recover. Factory reset doesnt fix it niether does wipe the cache etc.... Tried them all. I have read a few guides and had a look at twrp but always get errors flashing them to phone. I also tried to do it via sd card but samr errors. Is anyone able to help me or advise me on what go do? My email is [email protected] if you wanted to email instead. Thank you for your time.
Skarekrow0121 said:
Hi im new here and hope this is in the right place. I have a htc m8 on o2 network in the uk. Its basically not booting past the htc logo then it restarts again. I have booted into the boot loader via power button and volume down. When i go into recovery there is nothing to recover. Factory reset doesnt fix it niether does wipe the cache etc.... Tried them all. I have read a few guides and had a look at twrp but always get errors flashing them to phone. I also tried to do it via sd card but samr errors. Is anyone able to help me or advise me on what go do? My email is [email protected] if you wanted to email instead. Thank you for your time.
Click to expand...
Click to collapse
I had a similar issue once and it was the micro switch under the volume button itself being stuck. Have you had any issues with the volume sticking either up or down before?
No nothing like that m8. Ill double check that though.... i think its software issue..
Skarekrow0121 said:
No nothing like that m8. Ill double check that though.... i think its software issue..
Click to expand...
Click to collapse
Sorry it couldn't have been something as simple as that. May I suggest that you re-post your issue in the M8 help area of the forum located at, https://forum.xda-developers.com/htc-one-m8/help ?
That area seems to receive more traffic by experienced users than this one, so hopefully someone can point you in the right direction as there aren't many dinosaurs like us left using "antique" novelty items like the M8 anymore.
HemiMoparMan said:
Sorry it couldn't have been something as simple as that. May I suggest that you re-post your issue in the M8 help area of the forum located at, https://forum.xda-developers.com/htc-one-m8/help ?
Click to expand...
Click to collapse
Better to report the thread and the mods will move it. Otherwise, it doesn't really fix the problem (thread in the wrong place) but actually makes it worse (multiple threads in different sections, both asking the same question).
I'll ask the mods to move the thread.
Skarekrow0121 said:
I have read a few guides and had a look at twrp but always get errors flashing them to phone.
Click to expand...
Click to collapse
Would be helpful to know what the errors say.
If it says "remote not allowed" it is because your bootloader is locked. It needs to be bootloader unlocked (via HTCDev.com), in order to flash custom recovery TWRP.