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...
Related
I thought I had it all figured. Root, with Clockwork Recovery, Rom Manager. Nothing could go wrong. Now I am stuck at the splash screen with no Clockwork Recovery.
I searched fourum after forum to find a solution, but mine seems to be different. Just so you know I am 21, and a freelance computer technician so I am not afraid of the command line
What have I done to my device:
=Originally it had 2.1
=I rooted the phone via exploid method
=I installed CyanogenMod 6.1.1
+My computer only recognized my phone in HBoot mode, I think usb debugging is turned off though because I cannot acces my sd while it is in my phone.
I do have a microsd card reader
+I tried Esprimg.zip updates. It works .but I still cannot get into recovery mode.
For extra precaution, I backed up all of my sd card data on my pc.
Symptoms and problems:
+I am stuck at the white My tough slide 3g splash screen.
Holding up and power for at least 30 seconds does not get me in recovery mode. All I see is the white My tough slide 3g splash screen. No Black screen with a triangle(Biggest Problem)
+Holding down and power does get me into the HBoot.
+The recovery option will make the Mytouch slide reboot, but it will freeze at the splash screen.
+The clear storage option executed, but it did not solve my problems.
+I have also removed the battery, sim, and sd card.
Summuaray-
I need to get Into Recovery mode, but when I press up and power it does not work. I only see a white.I never though there would be a day where I could not get into recovery.
Also, I constantly charge the device so it wont turn off during an update.
Do you have S-OFF? If you do it should not be hard to recover.
If you don't I can't think of any other method now. But just to make sure which Esprimg.zip method did you tried? Because that should work in the first place.
Mine says S-On
Esprimg.zip
I used my microsd card reader to put esprimg.zip on the sd card. Boot the device while holding down and power. I let the phone check for the esprimg.zip and then the update was successful.
Conclusion:
I hold up and power and i cannot access recovery mode.
Possible causes:
By doing the clear storage, would that change my device to s-on. Honestly I never noticed s-on until now. However, I was able to root and get clockword mod 6.1.1 and it ran smoothly for a weeks.
darko4 said:
By doing the clear storage, would that change my device to s-on.
Click to expand...
Click to collapse
No. Only by flashing another bootloader will you get S-ON back. You probably did not have S-OFF before anyways but FYI Esprimg.zip does flash the bootloader so you're stuck on S-ON for now.
If the Esprimg.zip update method was successful it should have flashed back the stock recovery for you. I can't think of anything that could go wrong at this point except that u have a bad or corrupted Esprimg.zip. Did you use the champion build or the ENG build? If me I'd try to download it again and give it another go.
Good luck!
Ok so Esprimg.zip may be bad, and pretty much that is my only saviour;ok I understand.
I was using Esprimg.zip from other guides. Those were 137 mb
This time I used the one from here.
HOW-TO * Flash the Eng-Release to the Slide *6/15/2010
http://forum.xda-developers.com/showthread.php?t=703076
I am going to assume this the the eng build. It was 137.1 mb.
If this does not work the I guess I have to go champion build.
------------------------------------------------------------------
Failed
Champion build esprimg.zip is next.
A few more ideas.
manually install the recovery using fastboot.
troubleshooting without simcard?
My spl s-on so would that be possible?
Is there a way to maybe re root?
I read in one post that a guy sold it on ebay..i would hate to do that with just a month of ownership. would Htc make a warranty request even though I bought it used. Besides you only see bootloader and hboot spl s-on so how could they tell?
So you reach the screen where it asked you whether you want to install the update, you choose "yes" and it goes on to flash everything, radio, bootloader, yada yada, and it fails to boot?
Basically with S-OFF you can boot into fastboot and run
fastboot flash recovery recovery.img
in this case recovery img is CWM recovery. With S-ON fastboot flash is disable so it's not possible.
EDIT: If you do have the champion build on it's basically stock.
I have this exact same issue right now, I've tried the champion and engineering builds of ESPRIMG but with no success. I can't think of anything else that would be causing this in the first place, which is making it so difficult to troubleshoot. The only difference is that I was using CM7 instead of 6, but the exact same thing is going on. I have tried everything that the OP has with no luck. The only possible cause I can think of is that something was somehow corrupted while the phone was on and sitting on my table...because when I picked it back up, it was off and when I tried to boot, I got splash screen... Any other ideas?? I'm all out and just sitting here waiting for some genius light bulb to go off....attic's kinda dusty though..
With S-ON fastboot flash is disable so it's not possible.
So basically these are my options
esprimg.zip (if that does not work then use different)
Hboot clear memory,
with S-ON I have limited option
and keep it charged.
Although with fastboot and s-on is there something I could do?
Would rerooting be an option
darko4 said:
Would rerooting be an option
Click to expand...
Click to collapse
I don't see a root method in the forum that does not involve booting into a usable system.
Wait, you guys were able to flash the esprimg.zip right? Because in the guide when it says it requires root it's for flashing the mtd0.img first before rebooting into HBoot. Since you don't have a working system you cannot do that and if HBoot refuse to take your esprimg.zip then you need to do the Goldcard method. Otherwise I don't see why having root will make a difference.
So at this stage of the game I should do this..
1.get on my knees
2.put my hands together.
3.and just pray?
ok all jokes aside. Continue to try Esprimg.zip and update(all are successful but I still get splash)
I can't change my recovery since I have s-on
and no way of getting s off since i cant get in the phone, not even recovery,just h boot
So in a sense i have a lovely soft bricked mytouch 3g slide.
Later I might compose a list of the programs i had on the device, but i doubt that would make a difference. I appreciate the help and assistance, I am going to click the thank button for you gents.
In the mean while i got a tmobile comet for 136 one day shipping..No rooting on this one cause finals are coming and I do not have time to troubleshoot for hours. I love android cause of custom roms, but not being able to get in recovery mode...ah say no more. I am going to be one of those people who just downloads free software and complain to phone carriers about OTA.
Same here. I held off rooting and all until my exams were over because I know I'm going to go all the way until I get S-OFF.
I know many discourage S-OFF because it can potentially brick during the process but if you do read up and follow instructions very carefully it is really not that risky. And it'll be very useful in situations like this.
I'm sorry to hear you have a soft-brick. Maybe a dev will stumble upon and provides new insights but I afraid this is all we have in the forum for now.
to be honest i skimmed through the post, and im sure you did try this but just want to ask have you tried the official RUU update to see if you can get things back up running that way?
yeah I understand following directions carefully, but when you follow all of directions and get it working,and make backups, but then you turn the phone off and then turn it on. Then all of this happens.
ah let me stop my whining and download more esprimg.zip .
I just want to know what caused it. was it an application, cause if that is the case then I want to know so no one else get hurt.
(one interesting note, avg antivirus said my device was infected with viruses. It said with the apps, I did not clean it. i uninstalled avg. I presumed it was a false alarm cause the phone is rooted with applications with high privileged) Oh well
---------------------------------------------------------------------------------------------------------------------------------------------------
oh well. back to the esprimg.zip
never tried RUU, if it comes in a esprimg.zip then i guess i can try. if not then i do not know how to use it with mine in its current state
S on (so no advanced fast boot options
Hboot only
no recovery.
clear memory
only productive thing is successful esprimg.zip updates
its the official update to froyo, and need HTCsync and the RUU from htc how the installs procces goes i dont really know, but im sure there is a RUU update that you can use to update via bootloader,
ok i got htc sync
and the official exe.
my pc only detects the device in hboot. The device will read usb hboot.
1 might fiddle around for 20 mins to see whats what.
.
If it was like a esmprimg.zip then it would seem more feasible.
goood luck hope you get your phone back up and running
well a week ago it finally booted. I felt that it was a fluke so I pressed the power button to reboot. I tried to turn it back on then it was stuck at the splash screen.
I am now starting to think it is a hardware problem. Either way the unrooted tmobile comet,yes it is small, is doing wonders. The battery life is way better then a iphone 3g.
Just remember guys, if you get an android phone, make sure it is a popular one. That way you are more likely to get support because of the bigger fan base. Oh well it was fun while it lasted. The only thing I hate is that i could have gotten an xbox 360 for the same price. oh well, thanks for the assistance. i will lets you know any further updates.
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!
I need help repairing my dinc. First, let me apologize for the long post, but I wanted to provide as much detail as possible.
My cousin dropped his phone in water and tried to dry it off. I don't know if he tried to turn it on after drying it off. Also, I don't know what attempts he has made to bring the phone back to life, but he has given up and handed the phone over to me. He figured since I am an IT guy and also do hardware repairs I would figure it out.
This is new to me because I've never owned a Smartphone before. He turned off his service on the dinc and used another Verizon phone he had lying around.
I've research different forums for a fix for the past few days, but nothing has worked. I’ve seen posts with similar symptoms, but in all cases they were able to get more functionality from their phone than mine. Also, my issue is related to water and not from a bad ROM upgrade. Here's a summary of things I've already tried:
Dried the phone out with the rice in Ziploc bag trick for 3 days (phone is completely dried)
Reformatted the micro sd card to fat32
Did a system update
Placed PB31IMG.zip into the root of the sd card
md5 checksum: 31bb1611a0fa8197d447c0438426717e
When I remove or rename the PB31IMG.zip file and hold the down button+power, here is the outcome for the following:
Fastboot: Gives me the following options Bootloader, Reboot, Reboot Bootloader, & Power Dwn
Bootloader takes me back to the main HBoot screen.
Reboot would get me stuck on a continuous loop (stuck on the "HTC Incredible" white screen) and freeze
Reboot Bootloader just takes me back to the Fastboot menu
Power Dwn would do the same thing as the Reboot
Recovery: does the same thing as Reboot; it would freeze at the white "HTC Incredible" screen
Clear Storage: does the same thing as above
Factory Reset: does the same thing as above
Each time it gets stuck at the white HTC Incredible boot up screen, I would have to pull the battery. Hitting/holding the power button doesn't seem to do anything.
From what I've been reading, I don't think the phone is bricked, since it still turns on, has limited functions, & I can get to the HBoot screen. The only thing I haven’t tried is reinstalling the OS (not sure if the OS is included in the PB31IMG.zip file)? Also, I was going to try to reformat the hard drive (just in case the partition is damaged).
The phone has never been rooted and I am not trying to root/unroot the phone... just trying to repair the phone. The phone has the S-ON.
I have uploaded a 10 min. YouTube video so you can see what I'm dealing with. Any help would be much appreciated. If there is anything you want me to try or anything you want to know that I may have left out, please don't hesitate to ask. At this point, I'm willing to try anything.
www(dot)youtube(dot)com/watch?v=gHXDJl6G2X4
Sorry, I can't post a link to my video so just replace the (dot) with a "."
You need to do an ruu with a PB31IMG.zip.
You can get the ruu here http://pvillecomp.com/?page_id=22
If you ever want to be able to root you need to use the froyo one as gingerbread cant be rooted if your s-on. Just download, rename exactly PB31IMG.zip, place on your sdcard in no folders, make sure its not connected to a computer, then pull battery and replace then boot into hboot (vol down + power) it should automaticly find the file after a couple secs and then prompt you to press vol up to install. Once its done you will be promptet to reboot , do so and if all is as expected you should boot up normally. Note that the first boot will take a long time so be patient, it may seem like it freezes at the boot animation but give it time.
cmlusco said:
You need to do an ruu with a PB31IMG.zip.
You can get the ruu here pvillecomp(dot)com/?page_id=22
If you ever want to be able to root you need to use the froyo one as gingerbread cant be rooted if your s-on. Just download, rename exactly PB31IMG.zip, place on your sdcard in no folders, make sure its not connected to a computer, then pull battery and replace then boot into hboot (vol down + power) it should automaticly find the file after a couple secs and then prompt you to press vol up to install. Once its done you will be promptet to reboot , do so and if all is as expected you should boot up normally. Note that the first boot will take a long time so be patient, it may seem like it freezes at the boot animation but give it time.
Click to expand...
Click to collapse
I ran the RUU program, which took about 10 min to complete. When it finished the update process, it rebooted the dinc, but I'm now stuck on the white htc incredible screen as demonstrated in my video. How long I'm I suppose to wait as this white screen? It seems as if it's frozen, but I'm not sure. Am I missing something?
Should I rerun it or try to run the PB31IMG.zip file? BTW, I grabbed the PB31IMG.zip file from the same site from your link.
HiJacK69 said:
I ran the RUU program, which took about 10 min to complete. When it finished the update process, it rebooted the dinc, but I'm now stuck on the white htc incredible screen as demonstrated in my video. How long I'm I suppose to wait as this white screen? It seems as if it's frozen, but I'm not sure. Am I missing something?
Should I rerun it or try to run the PB31IMG.zip file? BTW, I grabbed the PB31IMG.zip file from the same site from your link.
Click to expand...
Click to collapse
Have you done a logcat?
HiJacK69 said:
I ran the RUU program, which took about 10 min to complete. When it finished the update process, it rebooted the dinc, but I'm now stuck on the white htc incredible screen as demonstrated in my video. How long I'm I suppose to wait as this white screen? It seems as if it's frozen, but I'm not sure. Am I missing something?
Should I rerun it or try to run the PB31IMG.zip file? BTW, I grabbed the PB31IMG.zip file from the same site from your link.
Click to expand...
Click to collapse
So your saying you did the ruu exe with your pc and it compleeded sucessfully?
dmeadows013 said:
Have you done a logcat?
Click to expand...
Click to collapse
No, I haven't. Can you please explain what this is and how it's done? I'm assuming this will pull up the syslog on the phone?
cmlusco said:
So your saying you did the ruu exe with your pc and it compleeded sucessfully?
Click to expand...
Click to collapse
Yes, but let me explain. When I first turned on my phone it would freeze at the white htc incredible screen. The pc would not recognize the device. The HTC Sync program would also not recognize the device.
I pulled the battery and did pushed the down button+power to get the HBoot. Then I would plug in the usb cable and the device is still not recognized. I would have to select the fastboot option, then bootloader a few times before the ruu program can detect my phone. HTC Sync would still not detect my phone.
After the phone is recognized by ruu I ran the program. I can see a black screen on my phone with big white HTC letters. Then I would see a green scan bar running. The ruu program completed and the phone rebooted. I hit the "finished" button on the ruu program and exit.
The phone rebooted and got stuck on the white htc incredible screen. I waited for 15 mins and it's still stuck on the same screen. If you watch my video, you can see exactly what I'm talking about. I've tried re-running the PB31IMG.zip file, but it's not working.
Any other ideas? You think the partition is damaged or the phone is bricked?
Ok I watched the video. My only other sugestion would be to try and root it with unrevoked so you can get the custom recovery, wipe everything from in recovery, and then try flashing a custom rom such as jermains rooted gingerbread+ rom. If that dosent work i would say there is some type of hardware failure.
cmlusco said:
Ok I watched the video. My only other sugestion would be to try and root it with unrevoked so you can get the custom recovery, wipe everything from in recovery, and then try flashing a custom rom such as jermains rooted gingerbread+ rom. If that dosent work i would say there is some type of hardware failure.
Click to expand...
Click to collapse
When I root it with Unrevoked, can I use the online method where I log on to their site or does matter?
Can I still root the phone even though HTC Sync does not recognize my phone? Yeah, someone from another forum suggested it might be a hardware issue from the water. If my cousin turned the phone on while it was still wet, he could have shorted out some circuits on the motherboard. I told him what he should do if it ever happened to him next time.
Thanks for helping me out!
HiJacK69 said:
When I root it with Unrevoked, can I use the online method where I log on to their site or does matter?
Can I still root the phone even though HTC Sync does not recognize my phone? Yeah, someone from another forum suggested it might be a hardware issue from the water. If my cousin turned the phone on while it was still wet, he could have shorted out some circuits on the motherboard. I told him what he should do if it ever happened to him next time.
Thanks for helping me out!
Click to expand...
Click to collapse
I wasnt aware there was an online method. I'm not sure if unrevoked will work or not but i know you have to uninstall htc sync before you use the downloadable method. Its a pretty simple process and worth a shot. Hardware failure is verry possible though, especially if it was turned on wile still wet. Even if it wasnt turned on wet it probably got droped in the water wile on possibly causing a short right away.
cmlusco said:
I wasnt aware there was an online method. I'm not sure if unrevoked will work or not but i know you have to uninstall htc sync before you use the downloadable method. Its a pretty simple process and worth a shot. Hardware failure is verry possible though, especially if it was turned on wile still wet. Even if it wasnt turned on wet it probably got droped in the water wile on possibly causing a short right away.
Click to expand...
Click to collapse
That's my bad; it's like 2am now and I was thinking about something else. I had to download the unrevoked3 program and run it. You're right, I had to uninstall htc sync. I was unable to use the program because it wanted me to enable usb debugging mode, which I am not able to do with my phone in its current state. It could not detect my device.
Someone from another forum stated that after watching my video, he noticed that the image I flashed contained a VZ radio. He said he's heard of cases where users were waiting up to 2 hours in the htc incredible screen before the update is complete. This seems like a very long time, but I'm willing to try.
He wanted me to make sure my phone is fully charged. Then he wants me to run the update in the bootloader and just let it sit. He says it may take up to 2 hours. He said if it doesn't work then it's a hardware related issue caused by the board getting shorted out.
Thanks for all your help!
HiJacK69 said:
No, I haven't. Can you please explain what this is and how it's done? I'm assuming this will pull up the syslog on the phone?
Click to expand...
Click to collapse
You need to have adb installed. If you don't, google how and there are many in depth tutorials. Then, once adb is installed, cd to your adb directory in terminal/command prompt and type ./adb logcat.
HI. Okay, so a couple weeks ago, I received a notification from HTC that said there was a new update available. Since I had S-Off and an unlocked bootloader (don't ask why, I just ****ing do.) I could not update, as it would give me errors, and cancel the update. So, earlier today I was fed-up with how slow my phone was being, and I wanted to fix it by updating. So I scoured XDA and found a thread about how to update by updating the HBoot or whatever. I followed those instructions and everything was fine, until I got to the initial part of installing the new **** through RUU. It was running fine, and then all of a sudden, the phone disconnected and ****ed the installation up. My battery was fully charged, and still has a charge as I am writing this. I digress. Whenever I would try to power my phone on, I would feel THREE (3) vibrations, and nothing would happen after. I tried booting into the stock recovery (fastboot, recovery, etc) and would still get THREE (3) vibrations. Bricked. So, I looked through a few threads on XDA, and found a few ways to fix it. Something about a Blind HBoot, or a Qualcomm Diagnostic Mode being stuck or something. Figured it was my best shot to try these. I tried them all. I put the PG76IMG.zip into my SD card, and booted up when holding Volume down, and only got THREE (3) vibrations. The tutorial said I was supposed to get FIVE (5) vibrations. So, I thought maybe it was something strange, and kept going through the tutorial. After five minutes, I'm supposed to press VOL UP, and should feel THREE (3) vibrations. Nothing happened. I waited and waited and tried again, and still, nothing. My phone is still lying here as a paperweight, and I want to get this working, so I can sell it because this phone is too much of a ****ing hassle for me. NOTHING HAS WORKED. ROMS, KERNELS, NOTHING. HAS. WORKED. I'M TIRED OF IT. I'm not a noob, I've been working with Android phones for a long time, and have never quite used an HTC device before. I had a Samsung Galaxy S Fascinate (CDMA) and it lost it's flash after I had moved to a different state. (The state I'm in does not have any towers for that carrier here.) SO. Can ANYONE give me a HIGHLY DETAILED tutorial, STEP BY STEP, to fix my phone?
HTC Wildfire S *Relocked* bootloader S-OFF CDMA METRO PCS.
I have tried everything I can find, and I have reached my wits end, man. Please, for the love of GOD, help me. I would really appreciate it.
I had 1000 rom flashes
3 Updates through RUU
Never had a brick
I hope someone can help you.
This is same as this thread http://forum.xda-developers.com/showthread.php?t=1522235
m1ndh4x8r said:
I had 1000 rom flashes
3 Updates through RUU
Never had a brick
I hope someone can help you.
This is same as this thread http://forum.xda-developers.com/showthread.php?t=1522235
Click to expand...
Click to collapse
I don't see how this helps me.
Help in the sense u have sent it to HTC for repair
Try this http://forum.xda-developers.com/showthread.php?t=1432425
Sent from my HTC_A510c using Tapatalk
kyleisah said:
HI. Okay, so a couple weeks ago, I received a notification from HTC that said there was a new update available. Since I had S-Off and an unlocked bootloader (don't ask why, I just ****ing do.) I could not update, as it would give me errors, and cancel the update. So, earlier today I was fed-up with how slow my phone was being, and I wanted to fix it by updating. So I scoured XDA and found a thread about how to update by updating the HBoot or whatever. I followed those instructions and everything was fine, until I got to the initial part of installing the new **** through RUU. It was running fine, and then all of a sudden, the phone disconnected and ****ed the installation up. My battery was fully charged, and still has a charge as I am writing this. I digress. Whenever I would try to power my phone on, I would feel THREE (3) vibrations, and nothing would happen after. I tried booting into the stock recovery (fastboot, recovery, etc) and would still get THREE (3) vibrations. Bricked. So, I looked through a few threads on XDA, and found a few ways to fix it. Something about a Blind HBoot, or a Qualcomm Diagnostic Mode being stuck or something. Figured it was my best shot to try these. I tried them all. I put the PG76IMG.zip into my SD card, and booted up when holding Volume down, and only got THREE (3) vibrations. The tutorial said I was supposed to get FIVE (5) vibrations. So, I thought maybe it was something strange, and kept going through the tutorial. After five minutes, I'm supposed to press VOL UP, and should feel THREE (3) vibrations. Nothing happened. I waited and waited and tried again, and still, nothing. My phone is still lying here as a paperweight, and I want to get this working, so I can sell it because this phone is too much of a ****ing hassle for me. NOTHING HAS WORKED. ROMS, KERNELS, NOTHING. HAS. WORKED. I'M TIRED OF IT. I'm not a noob, I've been working with Android phones for a long time, and have never quite used an HTC device before. I had a Samsung Galaxy S Fascinate (CDMA) and it lost it's flash after I had moved to a different state. (The state I'm in does not have any towers for that carrier here.) SO. Can ANYONE give me a HIGHLY DETAILED tutorial, STEP BY STEP, to fix my phone?
HTC Wildfire S *Relocked* bootloader S-OFF CDMA METRO PCS.
I have tried everything I can find, and I have reached my wits end, man. Please, for the love of GOD, help me. I would really appreciate it.
Click to expand...
Click to collapse
ok, im not saying i can get it going again but i`ll do my best to help. lets start from the beginning, what actually works atm? you say when you try boot up the phone in any way it just vibrates 3 times.
does it do anything else, does the screen light up?
does it even stay on?
when you connect it to the charger does the led still light up?
have you tried to connect it to the pc? have you tried to connect it too the pc with volume down first?
all seem very basic stuff obviously but if the pc can register it in hboot we might be able to get a ruu running on it.
Found this on a different thread...
Nevermind. Just realized you were still getting three vibrates. Sorry man. I'll keep an eye out if I see anything else that might help.
what is your hboot version? i was see 1.09.099 like in forum maybe you can start with update hboot.
you can use adb for all of this works. download a ruu and run it. after some steps you can find rom.zip in windows/temp extract it to a folder like c:\android\rom and use adb for install all *.img files. maybe it can fix that problem
hypercode said:
what is your hboot version? i was see 1.09.099 like in forum maybe you can start with update hboot.
you can use adb for all of this works. download a ruu and run it. after some steps you can find rom.zip in windows/temp extract it to a folder like c:\android\rom and use adb for install all *.img files. maybe it can fix that problem
Click to expand...
Click to collapse
seriously , adb can install img files ?!
Alright, well, I called htc and told them about my problem, and I might have to just send it in. BUT. I had my phone rooted, and had CM Recovery on it. So, since nothing is booting up at all, only the three vibrates when trying to enter either boot mode, will they be able to see that I had it rooted or anything? They said they'll charge 35$ just to ship it back in the same condition if it is. Can't really afford anything like that right now.
tl;dr I had my phone rooted, but nothing on my phone comes up, will they see my root or anything?
if you are rooted you are probably s-off or at least have unlocked bootloader. and both they will find out very easily.
Sorry for my bad it was fastboot.exe you can install .img files with fastboot.exe i was installed stock recovery with that
Sent from my HTC Wildfire S A510e using XDA App
Hi all,
I was having some random reboots on my HTC desire Z lately and decided it was time to try a custom rom. I followed the right steps to first downgrade to froyo, which was successful and next rooted the phone, which seem to have worked as well.
The next step was to get into recovery mode to install the rom, but I did not get to that. I took out the battery while it was still on to power it off, but then it did not power on anymore. Also connecting the charger has no effect at all, so it sure seems to be bricked.
Does anyone have a suggestion on what I can try, or what happened to it?
The way I downgraded and rooted was by using Strawmetals guide which can be found here:
http://minus.com/mu9vZ3P38
and was suggested in this thread:
http://forum.xda-developers.com/showthread.php?t=1178912
I carefully completed all the steps, checked the MD5's etc. and made sure the notifications/verifications I got back in the process were correct..
Also, I wonder if I would run into problems if I send it back in for warranty. If I can't get it to boot, will they? And next they will probably blame me for rooting, right?
Regards & TIA
Yes they gonna blame you for rooting. I was had a same problem, no boot to recovery. I solved the problem with install 4Ext updater and fromit install 4ext tuch,and now I can flash roms. Try to find a charged battery or put yours into another phone and charge it. If I understand right your battery died?!
Sent from my HTC Vision using xda app-developers app
Sounds like it might be bricked mate, same thing happened to me... 3 times. They probably won't be able to get the phone to boot, where did you buy the phone from? My second one was from Vodafone with a warranty, when it bricked I took it in, they plugged the phone in and left it for a few minutes and tried to power it on, tried a different battery (All things I already tried) to see if the device was showing any signs of life, it wasn't and I walked out with a new phone. I doubt they'd be able to bring it back to life to see that it's been rooted. You COULD connect your phone to a car battery and fry it, tell them you went to sleep and woke up and the phone was very very hot and it burnt your hand and melted the charger cable, not sure if I could recommend this, never done it myself... but if you have no other option.
These were also the options I considered. Got to give it a try with a different battery, if I can find one. If that doesn't make a difference, I'll just hand it in and see what they have to say, as there's nothing else I can do without being able to power on the phone..
All of a sudden the phone started working again . And afterwards I was able to complete the update to Mimicry 1.5.
Strange problem, as the phone seemed to be dead for hours.. Hope it doesn't happen again!