Related
Hello All
I purchased a phone from a friend of a friend so I don't have all the history of the phone. It looks like they attempted to root it and failed.
I only got it to boot op fully one time. (and I can't get it to boot up fully again) It goes to the htc incredible logo and starts over.) So here's what I know. I didn't see a superuser apk the one time I got it to boot. It has the radio that ends in 07.28. It has s-on. It has a recovery but not one that I'm used to (like on ogdroid)
Its says android system recovery <3e>
reboot
apply update.zip
wipe/factory
wipe cache partition
and at the bottom
E: Can't open /cache/recovery/command
I've tried the unroot method to try to get it going, but no luck. I'm stuck. Any thoughts? Thanks for any help.
You can follow this thread, part 2
http://forum.xda-developers.com/showthread.php?t=786436
Basically, download this file
http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.26.605.1_RUU.zip
Rename it to PB31IMG.zip, put it on the root of your SD card, boot the phone into the bootloader (hold vol + & pwr when turning on) and let it update. It should return it to a completely stock 2.2 with no root. From there you can go root it or do whatever you would like.
Ok I tried that. The update goes through successfully but I'm still stuck in the loop.
Is there a way to root or get s-off with out booting the phone? (I'm using a mac)
this happened to me recently - I reloaded RUU - hard reset - removed sd - left battery out for a while - used my wifes battery - power plugged in - Wiped everything possible in cwr (before ruu)
The phone is completely stock and wont stay on for more than 5 seconds if it even gets to the lock screen at all. In the end I had to put s-on and request a replacement
one thing I did notice though (hope this helps) I left my battery out of the phone overnight and in the morning without power connected it did boot all the way and I popped on to the market and used the browser for about 15 minutes - then fell back in to a boot loop and I wasn't able to reproduce that working state again.
Incredible
Try looking for a Ruu to return it stock,
make sure you wipe all.
Sometimes it helps to be patient and watch out for heat issues.
Not sure if this is related but My Hd2 on 2.3 and Mytouch 4g on 2.3 would boot loop when it got a little warm Remove the batter and let it sit for 10 minutes.
Ok
It's back to stock. I still have the same issue. It is the same problem that h0x90 had. This phone isn't activated and I'm not sure if it has a warranty or not. I would rather try to fix it if I can. Can I root it with adb or otherwise in its current state? I wonder if a rom would fix the problem. It seems to be software and not hardware, correct?
Before I was desperate enough to wipe everything (ruu) I loaded several different roms and loaded my backups - so in my case it was a hardware issue.
Verizon told me they cover the phone for 12 months from purchase date - and they're overnighting a refurb to me for free which is nice. Maybe if nothing else you can get a hold of the previous owner and attempt to get a replacement.
Best of luck though either way!
nothing0 said:
Ok
It's back to stock. I still have the same issue. It is the same problem that h0x90 had. This phone isn't activated and I'm not sure if it has a warranty or not. I would rather try to fix it if I can. Can I root it with adb or otherwise in its current state? I wonder if a rom would fix the problem. It seems to be software and not hardware, correct?
Click to expand...
Click to collapse
As the Incredible hasn't been on the market for a year yet, it's assuredly still within the warranty period.. As for trying to fix it yourself, I can all but guarantee that you cannot since what you're experiencing seems to be a relatively common hardware failure.
I finally gave up. I did find out that PCD at 1.800.229.1235 does warranty work for HTC. Maybe that information will help others. Thanks to all that helped.
Ok I'm lost. I'm working today and my phone tries to reboot for no apparent reason and is put into a boot loop that I cannot get out of no matter what. In boot loader I have no recovery. Downloaded amon ra recovery's PC36IMG.zip. Booted into bootloader it said it updated the recovery but after I've rebooted I still have no recovery. I don't think this is very good.
Bootloader asked you to update and reboot and it went through completely?
Yeah, it said update was succesful. Thats why I'm so confused.
So when you go into recovery from the bootloader, do you see the triangle?
Nope just back to white screen boot loop. Trying to flash sprint lovers with the pcm36img over it maybe that will bring me back to stock rooted stat.
Edit: Back to white screen boot loop.
this same thing happened to me a week ago. were u running a cm7 rom?
yeah ex10 i was going to switch last night guess its too late
Damn I feel bad for you
I had that same problem when i first rooted and flashed my evo. I suddenly got into an infinite boot loop where i no longer had a recovery. Sorry man i had to take it to a sprint store after i tried flashing a different bootloader and then retry flashing a different recovery from clockwork to amon. and then even tried to flash the stock rom none work. if none of those work then you most likely is going to have to go to a sprint store.
Well, you could try running an RUU. This will leave you unrooted and completely stock so you will need to root again.
Here's a how-to over on Android Central.
http://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/19278-how-unroot-return-stock.html
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Threw mine out of the window of my car and called sprint and told them I lost it. Cost me $100 to get a replacement and now I'm going to have to spend forever getting back to root and eng boot ect... sucks.
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies? Because I'm really wanting to go to the CM7 nightlies but not if the chance this is going to happen again.
ChacocII said:
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Click to expand...
Click to collapse
Does the bootloader let you run a PC36IMG.zip? If so, try running one (of a factory unrooted ROM), and when it goes to reboot and shows the green arrow facing down (if it gets that far) yank the battery at that point. I think that is when it's writing the radio image. If you can get it to that point, and then pull the battery, I'm pretty sure you'll have a brick. Aside from a battery pull during the radio flash, I'm not sure how to make a brick, without it being obvious of what you've done. You could rig your phone charger up to a 230 volt outlet from a drier or something, and plug it in. haha. maybe that would fry it, tell sprint you got a power surge when it was charging, and then it wouldnt turn on. (only 1/8 serious on that last part )
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
ChacocII said:
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
Click to expand...
Click to collapse
Damn, so you can still see s off? I have no clue how to get it to s on then, or make it so you can't even get to the bootloader. Yea, if you microwaved it (haha) i'm sure it wouldnt ever turn on again. However, whoever looks at it would be able to tell that something went very, very wrong, and it wasn't the phone's fault. ha. Maybe it won't even matter that it's s off. I've heard of people having luck with sprint looking at a phone that is s off, but I've also heard the oppositte (more often).
i actually told the sprint tech on the phone that i had rooted it and he still warranty replaced mine. im just hoping they dont change their minds when they get it back and see s-off and try to charge me 500 bucks for my new one.
Wow. Yeah, if it won't even run a PC36.img from bootloader, you're kinda SOL. That's pretty much a last resort. Granted, you should try a few different img's (different d/l sources) before assuming it's screwed. Sometimes, you can get a bad download. I had a stock Evo that wouldn't go into recovery, so I flashed a RUU from bootloader, and everything was fine. Best of luck with your replacement though, brother.
well i have 14 more days before i have to send it back. there must be some way to get it to not turn on at all without physical damage, just gotta figure it out.
UPDATE TO MY PREVIOUS POST. I HAVE INCLUDED MUCH MORE DETAIL AS TO WHAT IS WRONG NOW. ANY HELP PLEASE?:
I am stuck in HBOOT currently, Ship s-off and of course my phone is rooted. What happened was my battery died sometime on the weekend and i tried turning it on to see the HBOOT screen. None of the buttons were responding when being pressed, not even the Vol. down + Power button was working... It randomly after a day decided to turn back on, then the next day i was at college and my battery went dead again and i'm now back at the HBOOT screen. I should have kept a check on it but i wasn't aware it would happen for a second time. Anyway...
I downloaded the PD98IMG.zip file and placed it on my goldcard (i'm on T-mobile) and attempted to re flash my device via the phone and left it for 6 hours or so whilst sleeping last night as it said it was parsing files. It sat on the same screen for the whole of the time. Tried flashing via my mac with instructions from a previous thread followed everything correct apart from putting into fastboot as i couldn't select it and thought it was worth a shot anyway Anyway, I came back with a message in terminal saying 'sending 'radio' (24960 KB)... FAILED (status malformed (1 bytes))'... As you could see it said failed. quite fed up now after looking for solutions since monday and i was hoping someone could come up with a fix :/.
If anyone knows whats going on with my DHD let me know ASAP. I am 95% sure its not bricked as its charging and turning on to HBOOT.
THANKS!!!!!
have you pulled the battery? thats what I normally do
Have you switched it back on without the charger plugged in?
Well i eventually got it working some how just after i posted this, but now it has just gone off again! It seems to be every time my battery goes completely dead. I plug it in, turn it on and Hboot screen pops up and repeats the same process each time, i dont know how to stop it doing this and i generally don't know how to get it back on.
I tried the ideas suggested but i've tried these previously and tried them again but no luck... One thing now though, my volume down button doesn't respond. If there is no fix i guess i'll just have to watch my battery usage but if anyone can suggest anything i can do to get it straight back on that would be great
I actually really need my phone to work right now , it ain't happening though, its been on hboot all day once again, it happens when the battery runs out, i press the power button and doesn't even vibrate or anything of the sort, just sits there and then pops up with the green writing after like 5 seconds saying:
SD Checking...
No image
Loading... (PD98IMG)
No image or wrong image
It says something like that, its only very briefly though. If anyone knows what i mean.... my phones on t-mobile so i made a goldcard so i could flash some roms, would that have anything to do with it?
THANKS!
Hi,
What info do you see in bootloader.
SHIP S-ON/OFF or ENG S-OFF
And have you performed Radio S-OFF?
andyharney said:
Hi,
What info do you see in bootloader.
SHIP S-ON/OFF or ENG S-OFF
And have you performed Radio S-OFF?
Click to expand...
Click to collapse
Yea i have ship s-off, which is shown. I can't press the volume buttons on the h-boot screen to scroll through menu either just to add... DO you actually have any clue what this may be?
Yeah, you've messed up your handset.
Letting your battery run completely flat will damage your battery. It shouldn't however harm your handset.
What I'd recommend doing, as you already have a goldcard, download the 1.32.405.6 PD98IMG.zip put that on your card and boot into bootloader. Follow the prompts and restore your handset.
Oh my battery is fine, i know for future reference to not let it run completely dry! will that mean i won't have the rom, which i previously flashed? Do i put the PD98IMG file on the goldcard or on my normal sd that i am currently using?
There is something wrong with your phone. When your battery dies your handset shouldn't lock you in HBOOT.
Put the PD98IMG.zip on your goldcard. You will lose everything that is not backed up.
Its your call, stay stuck in HBOOT or try to recovery it.
I'll give it a try and let you know the out come, thabks! By the way, after this wht should i do to get miui back up and running, the sme as what i previously did ?
I'll go for the recovery of course haha... Thanks anyway though, i'll give it a shot and see how it goes down . I'll let you know if i have any success!
How long does it take for it to Parse the package? it automatically started doing it so.
Update: Well I have had this going for quite some time now and its continued to show the following...
Parsing...(SD ZIP)
Bootloader
Boot
Recovery
System
UserData
Splash1
Splash2
TP
TP
TP
TP
Radio_V2
Radio_Cust
Would really appreciate any help ASAP as to why this has just been in the same position for quite some time, obviously something is not right?
Im guessing this isn't very common is it? nobody seems to know what to do
wow.. stuck in the same situation... ive rooted and unlocked my partners DHD from telus... just about a week ago, it just suddenly went to the white HBOOT screen. Since then, ive been able to somehow get into clockwork by pulling the battery out, plugging in the usb cable, then inserting the batter, it would somehow take me to the clockwork mods menu screen. I was using an outdated version tho. I would be able to reboot from that menu which would start regularly booting the phone. One interesting thing tho is that the volume - button stopped working around that time.... Ive been pulling my hair out trying to make a goldcard (did it once, but havent been able to do it since i started trying again) so i can reflash the stock telus ruu. For some reason, the goldcard program im using isnt finding the mm2... just the mm1 and mm0... any ideas why? im formating a 8gb class 4 micro sd card... fat32, ive tried 32 and 64kb sector sizes... any suggestions?
Aidanio said:
How long does it take for it to Parse the package? it automatically started doing it so.
Update: Well I have had this going for quite some time now and its continued to show the following...
Parsing...(SD ZIP)
Bootloader
Boot
Recovery
System
UserData
Splash1
Splash2
TP
TP
TP
TP
Radio_V2
Radio_Cust
Would really appreciate any help ASAP as to why this has just been in the same position for quite some time, obviously something is not right?
Click to expand...
Click to collapse
I´m in the same situation.I think the PD98IMG file don´t match with previously installed ROM (radio,hboot?)...I come from a MIUI ROM,android 2.3.4 version.
I´m proudly to inform you that I did it!
All the thing was (I think) the ROM manager who flashed a wrong recovery.
How I recovered it?
Without adb drivers,without goldcard,without downgrade.
Simply I downloaded a PD98IMG file,I unzipped it and I changed the recovery.img with a 3.0.2.6 recovery version.Ahh,I deleted the radio.img,too(I don´t know if matter or not).After this,I zipped the files again and I renamed the file to PD98IMG.Copy to sdcard,wait to process PD98IMG and finally the power and volume buttons revives!
Good bye!
OK.. I've had several dinc's and finally got a charge. A buddy gave me a dinc and here's what I got. I can get into hboot fine. Phone was wiped when I got it. I have lights when charging and all seems well. I boot and just after HTC splash everything is black. He told me he did the latest ruu (pb31img method) . I've tried using the PC ruu and the .zip method to no avail.
Its hboot 0.92
Radio 2.15.10.07.07
And is s-on :s ( I know)
Can't get into any recovery...factory reset.. or anything. Also when using the pb31img method of restore it will sometimes just "go black" as soon as I try to update. Any help would be greatly appreciated.
I would try flashing the stock 7.28 radio (If you can) and see if that helps.
I've tried flashing just the radio as well as the older gingerbread ruu and radio being older than gb. It will even complete the ruu update (1 out of 10 times). But will not reboot. But if doing the ruu from PC it will still connect/disconnect USB. All the while screen is pitch black. But here is the interesting thing. Its actually booted all the way to sense unlock screen just for a second... then poof.
Now that I think about it my brother had this similar issue with his Inc. It first started doing random reboots constantly. I tried everything I could think off. At the end it would just reboot over and over and once in a while after letting it sit for a day or 2 it would load as far as the unlock screen and then reboot. Turned out to be a hardware issue. This may be the case for your Inc...I hope not though!
Ya me too.. but the more and more I delve into it its starting to look like a hardware issue.. but like I said.. it's just a hobby/mod phone (although its still better than my charge..lol) but ill continue to tinker. Thanks for the info.. ill post if it does wind up working.
Hi there,
I had a very nice trip with my rooted desire with a miui rom on it for now maybe, 1 year smthg.
Recently, i bought a new µSD and wanted to prepare it for my phone ; i downloaded rom manager, and tried the "partition SD" functionality, which told me that i would have to update my clockworkmod, which i tried with the "update recovery" in it, which failed.
After a while, i found that i forgot to S-OFF my phone, and that was the reason why i couldn't update the recovery. So i decided to S-OFF. Unfortunately, my phone didn't went to the last step, and stayed stuck at the boot screen until its battery died, maybe an hour after.
I began a long journey trying to figure out if my phone was bricked or not, since i wasn't able to boot it up ; only the hboot was responding. I tried MANY ways, MANY posts, i tried to flash with a nand backup without success ('access denied'), i tried to flash just the recovery (same or 'signature failed'). I tried to put a PB99IMG.zip file from alpharev into my phone without any success...
BUT. I succeed in recovering my phone with putting a stock PB99IMG.zip from shipped-roms and it boots up very well on a crappy sense rom.
From that, i tried hard to root it again since i want to try again to S-OFF it, and after that, return back to my beloved miui rom. I'm stuck because of a mysterious problem into my phone. It looks like it doesn't like the third step which (i guess) requires a boot script. So nothing happens to it, it freezes to the bootscreen, while unrevoked says "waiting for reboot..." endlessly.
I succeeded once (only) in passing this step, but then unrevoked said to me something like : "Internal error: failed to unlock NAND flash?" which seems crazy since i'm in a 0.93 HBOOT (since the RUU reset). I hadn't any Superuser app nor signs of rooting ("su" command failed in terminal).
For now, i'm trying to root it via the Visionary app, but i don't think it will work.
If anyone has any suggestion in making things better, i'll be pleased to hear !
PS : I'm writing this post because i feel it could be full of useful infos for anyone else stuck with a "bricked" phone.
use this guide to S-OFF, install custom recovery and root.
read all the instructions, several times.
oh and rom manager is often not recommended for this phone as it can often cause usb bricks. once s-off you can flash different recoveries via fastboot or android flasher.
use gparted or 4EXT recovery to partition your sd card.
Unfortunately, it seems like the time for me to change phone has come.
While i was doing an other time a RUU reset because of loopboot created by an unrevoked related bug, my phone decided to stop, and die. The battery is still charged — i can feel the fuzz with putting my tongue on it — but the phone just doesn't turn on ; it doesn't show the charging led when i put it on charge...
I'm currently looking for an other device, such as the Desire S (because of the size, mainly ; others blockbusters are too big)
If someone has an idea to make my Desire turn on again, anything i can do, i will do.
Thx for the answer, the guide link, and all !
ynk said:
Unfortunately, it seems like the time for me to change phone has come.
While i was doing an other time a RUU reset because of loopboot created by an unrevoked related bug, my phone decided to stop, and die. The battery is still charged — i can feel the fuzz with putting my tongue on it — but the phone just doesn't turn on ; it doesn't show the charging led when i put it on charge...
I'm currently looking for an other device, such as the Desire S (because of the size, mainly ; others blockbusters are too big)
If someone has an idea to make my Desire turn on again, anything i can do, i will do.
Thx for the answer, the guide link, and all !
Click to expand...
Click to collapse
don't just go flashing RUU's randomly, you may get amoled/slcd incompatibility for instance, which is what this might be.
try reading the troubleshooting guide, you can probably save your phone.
read carefully before you do anything in future...this situation could probably have been avoided
Thanks a lot again
I should be more patient when trying to do things, but it's kinda annoying not to have it working...
Btw, i wasn't acting *that* randomly (at least, for me) : since anytime i was using unrevoked was blocking the phone onto the boot screen, the only way i found to restore it was flashing it again. But yeah, maybe it was done too randomly though...
The guide you gave me is full of good advices, but the only thing that could be matching for my case is a bad RUU flashing ; this doesnt look to be my case, since even if i put my phone on charge, the charging led doesn't turn on. The phone doesn't warm after pressing the power button... It looks like there's something related to electricity inside that have been broken somewhere... Don't you think so ?
[EDIT] I found some guys having my (new) problem here : http://www.htcdesireforum.com/htc-d...h-on-or-respond-to-a-charger-what's-happened/ I'm quite relax since it's not a "0day" problem : lots of people are talking about it, so i have some solutions : wait and pray, if not, try another battery, or let it dead.
ynk said:
Thanks a lot again
I should be more patient when trying to do things, but it's kinda annoying not to have it working...
Btw, i wasn't acting *that* randomly (at least, for me) : since anytime i was using unrevoked was blocking the phone onto the boot screen, the only way i found to restore it was flashing it again. But yeah, maybe it was done too randomly though...
The guide you gave me is full of good advices, but the only thing that could be matching for my case is a bad RUU flashing ; this doesnt look to be my case, since even if i put my phone on charge, the charging led doesn't turn on. The phone doesn't warm after pressing the power button... It looks like there's something related to electricity inside that have been broken somewhere... Don't you think so ?
[EDIT] I found some guys having my (new) problem here : http://www.htcdesireforum.com/htc-d...h-on-or-respond-to-a-charger-what's-happened/ I'm quite relax since it's not a "0day" problem : lots of people are talking about it, so i have some solutions : wait and pray, if not, try another battery, or let it dead.
Click to expand...
Click to collapse
that problem sounds different as that was posted ages ago, and they weren't messing around with rooting and RUUs...
i don't think you should 'wait and pray, try another battery, or let it dead'
can you get to recovery/bootloader/fastboot at all? please post more details. if you can then it's probably not bricked.
i'm unsure of whether you've actually tried anything in the troubleshooting guide. try [2] advanced boot problems, S-ON. create a goldcard and try the WWE RUU
if none of it makes sense ask directly in that thread
and if you get the RUU to boot, don't use unrevoked...follow my 1st reply...
I stopped all the things i was doing when i had your reply, trust me !
As i said, i can't get the device to be powered on ; since, i'm not able to have any access to hboot, fastboot, nor adb. The phone does not charge when plugged to a charger neither to a computer. The led stays black, and the battery doesn't get warm (which normally does when charging).
Since the phone doesn't turn on, the guide you gave me is useless (but i learnt a lot from it, so thanks for that). The only section which *could* have been useful was the one talking about wrong RUU flashing with SLCD off ; but since my screen was working, and the symptoms are different (my phone is not recognized by the computer), this is not describing my problem definitly.
Be sure that if i can boot that phone once again, i'll follow your 1st reply and won't use unrevoked on it ever...
I'm trying now to find an other battery, to know which from the battery xor the mobo of the phone is dead. If battery, i'll just buy a new one ; if mobo, i'll buy a Desire S, since my phone reached the warranty limit, and i would have to pay to repair it...