Hopefully I'm just being blind here -- and I have tried a number of guides to fix this -- but I'm pretty stuck.
Couple of days ago the volume down button started playing up, then the menu and search keys stopped working. At the time I had rooted the phone with unrevoked and installed CM7.3 (iirc), and taken the S-OFF with Alpharev 1.8. I figured it was probably a software issue and for some reason decided to go back to run an RUU (rather than just running a different ROM, don't really know why on earth I did that). Kind of having a feeling that I was very dense and ran the wrong RUU, as now the phone is simply stuck at HBOOT.
When I say stuck, I mean as soon as I turn on the phone it goes directly into the stock HBOOT (FASTBOOT -- RECOVERY -- CLEAR STORAGE -- SIMLOCK) yet NONE of the buttons work (so I cannot navigate it at all). Perhaps it is actually a hardware issue, which would make sense as it boots straight into HBOOT, no HTC screen or anything. When it runs the SD check it comes back with wrong / image missing in all the checks.
Tried running ADB, couldn't find the phone. Other RUU's return error 170 as though they can't find the phone. Phone does register "HBOOT USB PLUG" when plugged in though, and my Windows 7 machine does recognise it, but as there's a new RUU on there USB debugging is not enabled and I cannot access the SD card through the phone.
The full info on the HBOOT screen is --
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
Any help would be much appreciated... Later on today I'll pick up a card reader, figure my only option now is to try and get through to it that way?
Hmmmm!
I'm not sure but it actually could sound like a hardware issue. You have the STOCK HBOOT and then ran the RUU for the HTC Desire? If u did so I cant see it as a software brick. PM me if you need some more help. I had a Desire for some month ago that i bricked A LOT more than yours, and i got it fixed (by myself... took some nights thought :/
Yeah I thought that as well, but before I flashed the RUU, although the phone was powering directly into HBOOT, I could use the buttons to navigate the menu. Now, I simply can't.
I should maybe add that when it checks the SD it returns with wrong / missing image (can't remember the exact wording -- pops up then goes pretty quickly).
Also this afternoon I opened up the desire and checked and reseated the buttons, all seem to be working as normal. Seeing as it's stuck at HBOOT, I think I'll just need to buy a new SD card and put whatever the image it's looking for is on it?
Edit: I was thinking that reformatting the SD card (through a PC USB reader) as FAT32, then placing the PB99IMG.zip from the latest 2.3 HTC WWE RUU might work? I can't see any reason why not -- think the Desire is unbranded so no goldcard required.
Edit2: Still waiting on a new adapter, but was wondering why the RUU failed -- the file was RUU_Bravo_Froyo_Vodafone_UK_2.33.161.2_Radio_32.49.00.32U_5.11.05.27_release_157522_signed.exe from shipped-roms. Don't see any reason why flashing it would have ended up leaving me in this position -- even if it was a hardware issue underlying it.
Sorry to double post...
Tried putting the PB99img from the RUU (and tried the 2.3 update PB99img) to no avail on both the SD card that I'd been using recently and the one that had originally come with the phone -- no luck; once HBOOT detects the img and runs through it, it gets stuck at the "parsing... [1] [2] [3]" etc page.
Any help would be massively appreciated, would be appalled if I have managed to brick this in my enthusiasm for fixing a volume button problem -.-
Already checked bortak's troubleshooting guide?
Yep and anything else I could find really. Starting to think this little droid is doomed.
Related
Hey all,
I am not a huge Smart phone buff, been dinking around on the tutorials. So I succesfully unREvoked my phone last night and it was working. I was doing an Update to the WiMax and for whatever reason I had an old PCIMG file left on there and I stupididly clicked yes to update to that image.
Well it wiped out my recovery and now I am not able to do anything (no card reader either). When I goto Recovery just a red ! and when I try to boot it just keeps looping me back to the bootloader.
I have tried connecting it to the computer, which has the Android drivers etc installed. The computer detects the device in some form, but when trying to get access via ADB no devices found. I am not really sure how to proceed, I will probably go buy a card reader and try and get the right PCIMG file back on and re-flash it. But if anyone has another method, I am all ears. Here is my information.
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-1.36.00.04.02
MAR 30 2010, 122:24:04
If nothing else I will try the SD Card and put on the IMG I had used originally, but would like to save a few bucks if I can.
Sorry if there is an answer posted already for this question. I did about 6 hours of research and looked through all the Wiki guides and came up with nothing.
Well, I bought a card reader and put the correct image back on the card which after a re-flash fixed it.
Thanks.
Hello all. I am a noob to working on rooting or doing anything of the sort with phones. I am more for desktops. With that said, I am in DESPERATE need of some guidance with my EVO 4G. I did not attempt to root the phone, I assume someone else did before I got it (from EBAY)..the phone itself appears to be brand new with no scratches, or any other markings. When the phone turns on, the screen shows:
SUPERSONIC UNKNOWN_ENG_ S-OFF
HBOOT-2.10.0001 (0?n eso=10 noig"t-"><gtredfutre
MICROP-041f
TOUCH PANEL-AMTELC03_16ac
RADIO-2.15.00.05.02
Mar 30 2010, 11:24:04
<vol UP> to previous item
<VOL DOWN) to next item
<POWER> to select
Bootloader
Reboot
Reboot Bootloader
Powerdown
ON THE OTHER MENU:
the only difference is that is says clear and SIMLOC
Since, I am new....I of course researched what the issue could possibly be. I read that some have issues with the memory card so, after trying the two that I have...I went and bought a new one. I proceeded to try various PC36IMG files and each time I got the 'MODEL ID INCORRECT' message. I tried downloading items like unrevoked and RUU software (I also downloaded two different drivers) but, with one driver my device shows as 'my htc' and with the other drivers, it shows as 'android bootloader'.
So, I cannot actually access the device through the computer. I downloaded a 'pack' called Evo Brick Fix but, had no luck with it when trying to put on the sd card and then into phone. I have tried putting Amon Ra on the sd card and attempting to load on the phone but, whether it is Amon or another PC36IMG, I will say that a pc36diag file one other file cannot be found. It tried to load the PC36IMG file and as soon as the bar is all the way filled, it says Model ID incorrect.
Somehow, through my fumbling around, I managed to change out some files between PC36IMG downloads and I managed to get the phone to BEGIN loading the PC36IMG but, it says parsing for about 1-2 seconds and then very quickly flashes something about NV so (loading NV - I think...it flashes that extremely fast) and goes right back to the screen you see pictured above. It does not do differently if I try it on phone in hboot or fastboot.
Can some please help with any advice? It would be greatly appreciated as I am at my wits end and feels this Evo is as good as dead.
Thanks,
Anna
Try and search here on XDA for 3.70 ruu tutorial.I've tried posting the link but it won't work unless its directed.The 3.70 ruu is the one you want to run with your current radio and hboot versions and it should get you up and running.
So, figured I'd attempt to root the thing today via the AAHK on my locked DHD. According to the effen manual, I won't need to gold card it beforehand either.
I went through the process, and I was told that the ROM that I had installed (2.5.3? Sense 3.0) had to be downgraded, so I went ahead with it. After downgrading, I was brought to an unresponsive bootloader. Being patient enough, I let it sit while I watched a movie, yet nothing happened after. I took out the battery and restarted it, and all I got was the Hutchinson 3G (my carrier) logo and it just stops there.
When I try booting in recovery mode to get to the bootloader, it does so, but it hangs.
After enough tinkering, I noticed the bootloader was only responsive once I rebooted without the memory card inserted. The phone itself is still inaccessible as it just stops at the 3G logo.
So far, I've tried to restore it through an RUU, but since it's still (I assume) carrier locked, I have to find the ROM that shipped with it. Unfortunately, I can't find a ROM that caters to Hutchinson 3G ROI (Ireland), so right now I'm downloading a UK version of it to see if it works. Apart from that, any recommendations on what I could do next?
Thanks :3
people are gonna need a little more info eg. what does it say on the boot screen s-off etc
what rom your trying to flash, formatted sd-card or not, possibly a corrupted download
AAHK does the business well, but can baulk at the slightest thing.
fairly new to some of this myself, but learning, my DHD took 4 attempts to finally do now on JT R4
Oh, mmkay:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
eMMC-boot
Apr 12 2011, 0:55:45
-----------------------------
Anything else I should include up there?
As for the ROM, I wasn't trying to flash anything bar the one that was downloaded through the AAHK client itself during the downgrade process.
After more tinkering, I've decided to leave it till today afternoon. Though I've made a few observations; so far
- The bootloader works fine when I turn it on WITHOUT the memory card
- The phone gets detected under the name "Android 1.0" when plugged in via USB both in hboot and fastboot. The fact that it gets detected I'll assume is a good thing
- Which leads to the second bit; it can be restored, since I've tried an Asian DHD ROM. It didn't complete because I was apparently supposed to find the appropriate ROM for it, which I assume is the H3G ROI version of it
- Aaand, the ROM still won't load up, and gets stuck at the H3G boot logo.
- According to the effen manual, it could be that my SD card was corrupt, so now my intention is just to merely restore it until I can actually afford to attain another memory card, which will be in a good few weeks and I don't wanna be smartphone-less for that period of time. But the only problem is; how?
if memory serves there isnt a rom in AAHK. the zip you intend using should copied be on your sdcard and initiated via recovery - vol down and on button. you should also be "s" off - did it offer to downgrade first [if needed]
from the manual
Insert the SDCard into the phone
Boot the phone
Turn on USB Debugging (Yes, plug it IN - use original cable plugged directly into the system board.)
IMPORTANT: Turn phone to charge-only mode. The phone stays in charge-only mode throughout this entire process. To make sure of this, check the default (menu > settings > connect to PC > charge only)
Win7/Vista: Right click on hack-ace.cmd and start as administrator (This will start the tool and bring you to the main menu)
option - 1
Install Clockworkmod
Clockworkmod version 5.0.2.7 -- yes
How to flash a custom ROM with ClockworkMod Recovery
Place the zipfile to be flashed on the sdcard. Do NOT unzip it.
Froyo disable Fast Boot: Menu > Settings > Applications > uncheck fast boot
Gingerbread disable Fast Boot: Menu > Settings > Power Options > uncheck fast boot
Turn phone off, no usb connected
Hold down vol- button, then press power to start, keep holding the vol- down button until Hboot menu shows up
Use the vol- down button to scroll down to recovery after some file checks are done (they will flash by quickly)
Press power to start recovery
Use vol down button to navigate, and the capacitive search button (bottom row of buttons, far right) to select
NOT VERY OPTIONAL/STRONGLY RECOMMENDED: If recommended by rom author or if flashing over another rom type (ex: cyanogenmod over anything else), wipe data/factory reset in Clockworkmod Recovery
Install zip from sdcard > choose zip from sdcard > select zipfile > Yes - (name of zipfile)
Repeat choose zip from sdcard for any add ons (gapps, themes, kernels, etc)
Press back button when flashing is complete until "reboot system now" is at the top of the screen.
Press power to reboot the system.
If desired, return the fast boot setting to ON in settings. (See above)
once yu crack it you'll see where you were going wrong
radio flashing is the easiest way to brick if you dont know exactly what your doing 99.9% of other stuff is recoverable
restoration is a more complicated path than rooting for noobs
I'm aware that there's no ROM included with the AAHK, I'm referring to the one that was downloaded THROUGH the AAHK when it said I'm gonna have to downgrade it beforehand.
And with reference to hboot, that's where another problem lies; my memory card is the one causing hboot to freeze. Hence, removing it prior to booting is the only way to get to it.
can you rerun AAHK and make a goldcard during setup and go that route -- wont help i know but being as its still "s"on you can return under warranty aslong as you dont send sim and sd-card tell them it wont go past h-boot.
if you have a card reader then format the card to make sure its clean, the drag and drop the required files on it - i have a lappy solely for this job with AV etc permanently turned off
Well, I'll rerun AAHK when I can find the SD card adapter, but since I've only recently moved house, it's gonna be near impossible until I get time off to unpack, which, till then, I'm still gonna need a functioning phone, so right now, I'm just looking for ways to return it to stock :3
i cant assist any further then as i've not yet RUU'd any devices as of yet.
hope you get it sorted
Thanks for trying anyways :3
I've been searching for an Irish RUU. Currently trying a UK version of it hoping it MIGHT just work. Anyone have more ideas?
Edit: Ok it didn't. Posted on the Three Ireland support boards trying to see if I can get an RUU
Ok, so have a serious issue
at first i was able to successfully root and flash clockwork mod recovery on my DInc using the rooting method from unrevoked 3 and was running Clockwork mod recovery +Cyanogen mod7 through the Rom manager (cannot remember exactly which versions.) it was all running fine, then just decided to unroot it with a few different methods (one didnt work and the others failed as well, maybe because i mismatched the stuff i used during the First try at the unrooting process..but because i tried one method after the other, and it was soo long ago, i forgot exactly how i ran into this problem
basically somehow i screwed up the Unrooting process.
SO now I am Having the System UIDs are inconsistent message every time i start my Incredible, Tried recovery that didnt work, tried factory reset+ erase all data on phone SD card (i probably accidentally erased the recovery image) it seems to reboot and be all restored, like a stock image, but weirdly the Superuser Ninja holding the AR15 still shows up in my app drawer (even after i unrooted and restored everything.) so i i decided to check out if the permissions were still enabled and they were not... SU shows up and doesnt function (just blank). I investigated further by downloading ROMmanager and then everything ended up forceclosing over and over again...I went to download "# Root Checker" and pressed "check" and it proclaims that its not rooted but under "User" it said "root"... i guess that its saying im rooted but im not?!?! LOL
anwhyo here are my DInc Specs as of Right now:
my DInc is an SLCD, running android 2.3.4. baseband is 2.15.10.07.07
Kernel 2.6.35.13-g03546aa
[email protected]#1
Fri Oct 7 10:52:52 CST 2011
software number 4.08.605.2
im still able to Access HBOOT and the screen says
*** UNLOCKED***
INCREDIBLE XD SHIP S-ON,
HBOOT-1.02.0000
MICROP 0417
TOUCH PANEL- ATMELC03_16ac
RADIO-2.15.10.07.07
DEC 21 2011,23:37:16
when i tried to see if i can reflash it through fastboot, the device manager in my W8.1 Pro 64 bit says "Device failed Enumeration" and USB notification popped up from the system tray saying that the device wasn't recognizable
so the drivers provided by Unrevoked for enabling the phone to be detected dont work, and the HTC Sync program doesnt even detect the Incredible.
However,,,,
the Fast boot, Boot Loader, and HBOOT still works upon pressing the Volume-down + Power and am still able to access Internal Phone Memory AND the SD card when the Phone is plugged into my computer via micro USB (so it looks like im able to flash things to it, but stuck as to how and what)
Because im still able to access the the SD card and internal Memory,
I tried putting PB31mg.zip on the root of the SD and ran HBOOT> and i gave it a second to detect the file.. then it said "Main Version is older Update Fail!"
the guy in this thread http://forum.xda-developers.com/showthread.php?t=1286223 seems to have had Similar problems..... I have added symtoms and issues on top of the whole 2.3.4 with S-on and Radio 2.15.10.07.07....
I just want to get back to vanilla-stock on my incredible with absolutely no modifications and without the System UID/feeling lucky pop up bugging me. and dont care what route i take, weather it be rerooting and reflashing , just reflashing. i just dont know what to do to get it that way from here.
Can anyone please help me figure out how to get back to normal with this DInc???
Im sorry if i dont make any sense im having a hard time explaining it. if you do understand me, i would appreciate your help. also if you need me to clarify things just ask me.
I'm a little rusty, but I remember this was the preferred method for rooting because of problem with the 1click unlockers,
(nuts, can't post links yet)... Google, "[HOW TO](gaining root)unlock,downgrade,and achieve s-off with htcDev" and look for it on androidforums.com
Try picking it up from step2, just keep the unlock_code.bin from miniadb_inc files from step1 on the phone. As long as typing 'adb devices' displays your phones serial number, you should be ok. As a long shot, you could try a PC with Windows7.
Try this ruu thru hboot http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip
Hi Guys,
A lot of this stuff is new to me. I have an old HTC Desire which I hadn’t turned on in a while. When I tried to boot it up, it only got as far as the O2 splash screen. I know the basics so tried volume down and power button and got to the fastboot screen,
Bravo PVT4 Ship S-on HBOOT-0.93 0001 MicroP-051d Touch Panel SYNT0101 Radio-5.09.050.30_2 August 10 2010
Tried recovery but again stalled on the splash screen. Been looking through the forum, some great info there and the HTC Desire troubleshooting guide is very good. But I just don’t know exactly whats wrong with the phone as sometimes I get a stall on screen with white HTC, sometimes on O2 splash screen and one time it stopped with three android men in the middle of the screen.
I got myself a SD Adapter for the micro sd in my phone and copied/backup this info on my laptop. I’ve tried clearing all on the Micro sd and running a RUU but always comes up with the error cannot connect to pc (windows 7). Don’t mind losing all on the sd card as I have pics/videos on the laptop, just want to have the phone work again. Would ideally like to start from scratch and put the minimum amount of information needed on my microsd to boot up the phone correctly. I think there may be a chance as I can get to the hboot screen. Appreciate any help I can get
Regards
Well done for finding the troubleshooting guide and having a read in the first place, a lot of people don't bother!
If you just want it booting, try running the the 2.3.3 RUU using the PB99IMG,zip method, which doesn't require a PC connection.
- Download the .zip URL="http://d-h.st/d44"]here[/URL],
- Put it directly on the root of the sd card (not in any folder)
- Boot to bootloader (Vol down + power)
- It should find the file, select power to run it.
Cheers Eddie for getting back so quickly.
Just tried what you said but getting "wrong image or no image" briefly flashing
up on the screen when i select bootloader. I put the zip file itself onto the root of the sd card. Should i delete everything else
on the sd card?
Another thing i've noticed is that i get seven random vibrates every now and again when it HBOOT mode.
Thanks again Eddie
That's weird, should find the file.
Sorry have to double check:
- You didn't rename the file? You shouldn't have to modify the zip at all, should be named PB99IMG.zip and not PB99IMG.zip.zip
- It's definitely on the root of the sd card (not in a folder)
You shouldn't need to format it as it scans the whole card for the file, but no harm in trying if it's backed up. Reformat the sd card completely, to a single FAT32 partition. Put only the zip on there, try again.
If that still doesn't work, try it with another sd card.
Getting there!!
Ok i got my HTC to recognise the zip file. Problem was PB99IMG file was called zip.zip. Easy to miss
because on the root of the sd card it only has .zip but when i tried to copy it in again it asked me do
i want to replace PB99IMG.zip.zip with PB99IMG.zip.zip...
So Vol down and power button and HTC starts the process
Do you want to start update .....vol up
Updated Bootloader ok but
unfortunately for me it stalled while updating RADIO V2.... waited good 5 mins but did not progress
Disappointed as i thought i was nearly there. Has anybody any experience of this!
Eddie only seen your post after i put this one up. You were right with the naming of the file .zip.zip
Eddie only seeing your post now. you were right about the .zip bit, cheers.
Tried again and this time success, got all updated except Radio which gave a "fail PU"
Down the bottom in black it said "partition update fail"
Then i pressed vol up to reboot Htc turned off... and didn't reboot
Going to leave it at that for now and head to bed. Thanks for your help today
If you have any ideas i'll give it a go tomorrow:fingers-crossed:
Well progress is good the .zip.zip error is surprisingly common.
Does it say "RADIO V2 Fail" or similar?
This unfortunately is not a good sign, suggests a radio brick, or an overheating motherboad I believe. You're not the only one to see this error.
Try putting the desire in a bag in the freezer for a few minutes (not joking), the re-running the RUU same method.
This may get it to boot, but I fear that it won't be long before the same thing happens again and it gets stuck on the splash screen, no guarantees at this point with that error.
eddiehk6 said:
Well progress is good the .zip.zip error is surprisingly common.
Does it say "RADIO V2 Fail" or similar?
This unfortunately is not a good sign, suggests a radio brick, or an overheating motherboad I believe. You're not the only one to see this error.
Try putting the desire in a bag in the freezer for a few minutes (not joking), the re-running the RUU same method.
This may get it to boot, but I fear that it won't be long before the same thing happens again and it gets stuck on the splash screen, no guarantees at this point with that error.
Click to expand...
Click to collapse
Yeah "radio v2 fail" tried to run again but now won't turn on at all. Tried freezer...nothing and hasn't turned on since. I suspect your right with
motherboard over heating and i'm resigned to it being a lost cause.
Thanks for the help anyway Eddie