I have an A8183 from Telstra Australia. I rooted it using the revoked method, following the Telus Desire HBoot 0.83 Root and Flash guide on these forums. (new member unable to link).
I had the Cyanogen mod installed on the phone but didn't really like it. I wanted the HTC sense ui back so I tried to run a few generic RUU to get it back to normal.
Of course I got the Error 130 (Model error) or whatever it was. So I tried the Telstra RUU. I then got Error 140 (Bootloader error) and read around and found out I needed to downgrade to bootloader 0.80. Obviously did not realise this would affect the SLCD screen and remove the display drivers for SLCD to work.
I now have a phone with no screen, it boots and I hear the noises, but no display - not even in the bootloader or recovery mode. I tried putting the FroYo OTA on my gold card, renaming it "update.zip" but it didn't work, probably because I think I have a custom recovery mod I got from following the thread I linked above. Can someone please give me a noob guide to fixing this?
Use your gold card and flash WWE RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe
Your screen is going to come back(the above RUU is SLCD compatible) and then download your Telstra RUU and flash with your goldcard(make sure RUU is SLCD compatible)
I've tried lots of RUU's and it takes about an hour to download one. The ones you just linked look similar to the ones I've already tried. I'm currently downloading it, as well as the Froyo one.
Will post back in an hour or two as to what happens.
EDIT: It says there is a problem with the USB connection whenever I try to run the RUU...How do I fix that? My computer recognises there is something plugged in, and the charging light is on my phone.
I tried this:
1. Remove the battery
2. Insert the gold card
3. Hold down volume down then press power
4. Blindly press power again to get into fastboot???
5. Run: RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe
and/or Run: RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
On step 4, windows recognises a USB device but fails to install the driver. I went into the device manager and there is "Android 1.0" listed there. I tried to update the drivers manually by using the ones in the AndroidSDK. I'm assuming this has something to do with what happens on step 5. *UPDATE* Installed HTC Sync with the driver, uninstalled HTC Sync, windows picked it up. Windows required a restart before I was able to flash any ROMs.
On step 5 it gets up to the screen where it says "Gathering information about your android device" (or something). It times out and says Error 170 - Usb connection error.
*UPDATE* restarting the RUU fixes the USB connection error, however ALL of them give Error 130 - Model invalid. The only RUU that works is RUU_Bravo_Telstra_WWE_1.15.841.14_R4_Radio_32.30.00.28U_4.05.00.11_123851.exe and unfortunately that has already been flashed onto the phone - so it does not fix the screen. If anyone knows of an RUU that will work with my phone? Or perhaps a Telstra one that actually works and restores my bootloader or something.
Someone pleeeeeeeeease help
From what you say, I think the LCD is bricked but the phone is working otherwise. Just to confirm power on the phone and let it boot normally. You should hear the boot sound and then after 2-3 mins try calling from another number to see if it rings.
Once it is at that stage, connect the mobile to PC via usb. Ensure htc sync software is installed (Not the drivers alone, but the full htc sync software). Then run the .exe that is compatible with SLCD. Your phone should get flashed. You cannot see anything on the mobile screen yet, but you can see the status on your computer.
I am not sure if RUU flashing will work from recovery/fastboot screen..... I am guessing you get the timeout error cos the phone is not booted. Give it a try.
Yes, Yes to all of that. Like I said, the only RUU that works is the Telstra one atm, and that is already on the phone. Like I said, I flashed that after downgrading to bootloader 0.80. All the other RUU's that I have tried to flash give a model id error.
If anyone can point me to an RUU from Telstra that enables use of the screen I would like a link please
I may be giving you a wrong advice, but have you tried to turn the phone on while pressing the back button? (not the volume down, the back button), and flash a compatible RUU?
Yea I've tried that with most of the RUU's that I've downloaded. It just gives model ID error. The only compatible RUU that I've come across is this one Telstra one that I've found on this forum. None of the other generic ones seem to work. I can't seem to find another Telstra RUU that will work. I have no idea if the phone is even still rooted, or what version the bootloader is (My guess is still 0.80 - even though it needs to be 0.83).
I'm unable to re-root the phone with a method like unrevoked because I can't enable USB debugging (can't see anything) and unrevoked doesn't find my phone.
At the moment I'm just playing around with flashing different RUU's remaking my gold card, installing/uninstalling HTC sync, flashing RUU in what I think is the bootloader screen, what I think is the fastboot screen, and when the phone is fully booted. (This would be a whole lot easier if I could see what was happening).
The only luck I've had is re-flashing the original Telstra RUU which does nothing to the screen...
(not the volume down, the back button)
Click to expand...
Click to collapse
- What does that do?
Turning the phone on with the volume down key pressed takes you to HBOOT menu
Turning the phone on with the back button pressed takes you to the fastboot menu directly, if I'm not recalling bad you need to be there to flash a RUU, It's worth the try...
I tried it with the back button - Same deal Error 130 - Model ID Error.
Apparently you can fix that with a new gold card. I read somewhere else to remake your gold card step by step. One of the steps requires USB debugging to be on your phone to record the serial numbers listed in the command prompt with the phone plugged in. I already have goldcard.img and have tried putting it on multiple microSD cards, I now have no more to try out.
Anything else I can try?? This is my only phone :S
I am not an expert on flashing, but I had bricked the LCD on my desire before. But mine was unbranded and flashing a unbranded RUU that got my phone and display working again.
What I would suggest is you can try flashing an unbranded WWE Froyo RUU that is compatible with the SLCD desire. If you have the gold card, you can flash any RUU to your phone (That is my understanding)
If you are not able to flash any other RUU, maybe the gold card is not proper. As far as I know, you should use the .img only on the sdcard which was in the mobile when you executed the commands. using .img generated with one card on another sd card will not work I think. At least it didnt for me.
Also the RUU is not bothered about the Hboot version on the phone. An RUU will have it's own bootloader and it will flash it onto the device over the existing bootloader
And above all, do not panic. The device can be recovered and restored. It is just a matter of time and patience and trying out a few things.
Edit: I forgot to ask, Do you have a nandroid backup done immediately after rooting?? If you have done it you could save yourself a lot of time by just restoring it.... If you have not backed up, then Lesson No 1 in rooting -> ALWAYS do a nandroid backup before you do things.
I think I have to agree. After about 20 hours of trawling forums I am 90% sure that I screwed up the initial gold card. (unrevoked doesn't require a gold card - so I thought it worked).
Is there a way to create a new gold card without an android phone? If you could point me to a guide that would be awesome. Obviously I'm prepared to buy a new microsd card to fix my $900 phone :S
Do you have USB debugging enabled?? If it is enabled, you just need the phone to be booted to create goldcard. Insert a formatted sd in the phone and boot it up, connect via adb and generate the CID numbers and try to make one.
If usb debugging is not enabled, then you can play "blind" game and try to enable it without the screen. It's tricky but certainly possible.
It was, but unfortunately the flash that ruined my screen returned it to default, which I assume would turn debugging "off". The blind game? never thought of that, I guess I could try look around for a youtube video of someone doing it or something. If anyones got spare time some STEP BY STEP exact instructions would be awesome
lordmitchell14 said:
It was, but unfortunately the flash that ruined my screen returned it to default, which I assume would turn debugging "off". The blind game? never thought of that, I guess I could try look around for a youtube video of someone doing it or something. If anyones got spare time some STEP BY STEP exact instructions would be awesome
Click to expand...
Click to collapse
If you search for lcd brick fixed, you should find a step by step guide to turn usb-debug on.
To flash a ruu, your phone needs to be booted in android normally, the ruu reboots it in fastboot itself. If you get an error flashing the ruu, try updating the android phone drivers. Even if Windows said it didn't update, try the ruu again. It worked for me with a friends phone.
Sent from my HTC Desire using XDA App
Well here are the steps..
1.Power on the phone and after 2-3 mins, press the power button to load the lock screen
2.Swipe down to unlock.
3.You should be in homescreen if device just booted. Press menu and then press the spot immediately above the search button. This should take you to settings screen
4.Now swipe long strokes with your finger "down to up" 4-5 times on the screen.. you are now swiping down the list.We need to make sure we reach the end of it.
5.Once you reach the settings list's end, the "Applications" link will be located just below the volume "+" key. about 5-7mm below the + mark. press the spot.
6.Now you should be inside the applications. Now keep swiping down on the trackpad. Do it for 10-15 times no problem. There are only 4 items in the list and doing it many times will ensure the selection is now on "Development" which is the last item in the list
7.Press the trackpad. The development should now get selected
8.Wait for a second. Press the trackpad again(No up/down). USB debugging will get selected.
9.Wait a second. Press the trackpad again. The popup "ok" button will get selected.
And you are good to go
Connect to PC and see if you can connect via abd.
This is assuming that Debugging is turned off. If it is already ON, then doing this will turn it off. So first check if you can connect via adb before attempting this.
I followed all the steps in this guide: http://forum.xda-developers.com/showthread.php?t=750852
I even spent an hour getting the debugging to turn on.
I managed to root my Desire again and got down to step 35. Unfortunately that RUU gave a model ID error. Just like all the rest.
Thanks for all your help guys, although this is driving me insane :S
*BEGIN DANCING*
thanks to the awesome guys at http://code.google.com/p/androidscreencast/
After playing the blind game and turning on USB debugging, I was able to use my computer as a screen which made things a whole lot easier.
After following the guide linked in the post above:
- I bought a new microSD
- re-made the gold card
- Followed steps 30 onwards...
- ran the RUU several times (it finally worked whilst in boot mode)
- AND MY SCREEN TURNED ON F*%K YEA!
Great to hear!!!
Now do a Nandorid backup and then you can go about trying out any mod/rom you want and you can always get back your original state with a simple nandroid restore.
And that ScreenCast looks interesting... will give it a try
OK. Im new to XDA and i have read alot of articles trying to fix my screwup. Hopefully someone can help. I was once rooted and i had redemption rom on and i tried to install cm30 nightly and got stuck somewhere and started to try to do wipe and clean amopngst other things and almost bricked it totally.The main thing that happens is when i press power i get 5 vibrate beeps and a blinking green light. i can go to hboot by pressing power and down but i cant go into recovery. Among other things i can plug usb and shows hboot usb but computer only shows android boot loader under device manager.
Now here's where it gets even weirder. I tried to install the pb113img.zip. when i did everything said ok while installing and when i got the choice to reboot it went to a green recycle looking thing then it went to a blank screen and 3 beeps with green blinking light.
I went into fastboot and hit reboot and it did boot into the stock 2.2 rom but if i disconnect a usb cord or when plugged into the wall the phone dies and goes to the blank screen with 5 beeps and blinking lights.
while in hboot the recovery choice is not working and neither is factory reset.
I hit fastboot the choice for bootloader takes me back to hboot.
Now while the usb plug is in the hboot says hboot usb but when i did get it to boot and plugged the usb in it doesnt show on my computer it does however show android bootloader interface on my device manager. Also the sdcard will not read on the phone but the sd card will read in a sdcard adpater where i can transfer files.
I have 2 sdcards and a sd adapter and htc usb cable and htc outlet charger and 2 batterys.
Here are my stats:
S-On
H-boot 0.92
touch panel-ATMEL224_16
radio- 2.15.00.07.28
Please somebody help me i been trying different methods but running into circles here.
If your S is on and it looks like it is and your running the stock 2.2 bring it in to the store and they will warranty it for you.
I did think about that because stock rom looks to be on and s-on as well just wondering if they could be able to tell through h-boot
Unfortunately this is a hardware error code, and you'll probably have to get it replaced.. My Inc came out of the box doing this (had it shipped to me), and the only option I had was to take it right back to the store.
I was able to boot mine normally if it was plugged into the computer at the time, so you might want to try that and see if you can at least verify the installed firmware. Otherwise, a warranty exchange is your only choice.
My incredible started doing the same, it all hapened when i mounted sd in recovery mode and then i was playing with diag mode to flash it. Since then its doing the vibrate and green light thing. Also I rooted it and my s is on. Also I can use the phone if i plug in the usb while turning on and then quickly take it out. Only problem is the phone doesn't detects the internal or external storage. I even got phone to be detected by unrevoked, but it is stuck as pushing recovery since phone doesn't detects the storage. BTW I already tried the Official PB31IMG zip.
Please any help is greatly appreciated.
Same issue flashing CM7 RC2. Could not fix it, Verizon is replacing it.
Here's a few threads to follow:
http://forum.cyanogenmod.com/topic/18381-bricked-my-incredible-installing-cm7-rc2/
http://forum.xda-developers.com/showthread.php?t=808294
It is probably a USB brick
I had the same problem with my HTC Legend a few days ago, it turns out to be a USB brick, which means something had corrupted the misc partition. The fix is simple, just flash a good misc image back to that partition and everything is back to normal, there are tons of USB unbrik TUTs out there.
Hope this could help.
Hi everyone.
I've just bought an htc desire hd that was described as software faulty.
Turns out it has some serious hardware faults too, unfortunately.
Basicaly my problem: phone has locked down due to too many gmail password attepts (not my fault, I already received in thi state).
Phone is in german, and won't let me pass the gmail login screen, can't login to wifi and does not accept my sim card (it's the only thing I was aware, that the phone is sim locked, by I thinked that I can fix it since I have an xtc clip) and only let's me do emergency call.
Unfortunately there is more: volume keys do not work (flex cable has been completely cut off!) and adb is not enabled.
Basicaly I can't enter into bootloader to use the xtc clip or to make a factory reset.
I've have ordered today a replacement volume flex cable, but until it arrives from HK I would like to use the phone and find out what else problems does it have.
Is there any other way to enter bootloader, than the volume key or adb reboot bootloader command?
Any help would be very appreciated.
Thanks.
Mod 1: so I've managed to flash a stock rom, it did a factory reset, so now I'm able to use the phone and enter bootloder through adb.
My only concern now is to use xtc clip.
Mod2: turns out, it has the latest hboot (2.00.0027), wich is not supported by xtc clip.
So I used the advanced ace hack kit to downgrade.
Pre downgrade was successful, but because of lack of volume buttons, instead of zip methods, I tried to downgrade via ruu.
Ruu update started normaly, radio and hboot downgrade were successful, but the upgrade stopped at 16% at said there was an usb connection problem.
Hboot was something like 0.8xxx.
Tried to restart ruu, but same connection issue.
I've restarted the phone, but now it's stuck at htc logo, due to the unfinished update I suppose, and since I don't have working volume buttons, I can't enter into fastboot either (now that it's 0.8xxx I could try xtc clip, if only I were able to enter bootloader).
When connecting phone to the pc and starting it, I hear the connection sound on pc, but it does not respont to adb or fastboot commands, neither does it when it's switch off (I've found a guide here on xda, that says if dhd is in a bootloop and vol down doesn't work--> pull out battery, put it back, connect to pc while shut down, orange light, than adb reboot bootloader--> doesn't work because of factory reset made ruu adb is switched off), ruu update won't start due to connection issues.
When it's turned off and connected to the pc it's shown as a mass storage device (with or without the memory card), if I turn it on it's still detected as a mass storage device.
What to do now?
New volume flex doesn't arrive till 30 days, so I will not be able to use it since then?
It was supposed to be a christmas gift.
Hello.
I have HTC ONE X for a long time.
today i suddenly got a notification for update (as far as i remember it was the"heartbleed fix" update).
ive downloaded the update and start the installation.
at the moment i press start the phone turned off and became like a "zombie".
hes not turning on, doesnt show the red led while charging (and also doesnt heat up while charging like it used to).
i tried to connect the phone to my pc but pc doesn't recognize the device, and the phone doen't respond to the connection.
some details on the phone (if you need it): CID_044, the rom was official, official recovery and boot, it was relocked because i did it withot changing anything except the unluck and relock.
i tried to download drivers and re installing them, as well as java.
tried to press power +volume up\down\both.
tried to search for device using adb.
tried to rebbot via fastboot and adb (throught the pc).
all this without any luck.
anyone got anothe suggestions? the phone i completly dead?
My phone's screen was broken, I could only use my phone with some tools like screenshot. Today before I was about to repair the phone, I wiped all the things (including system, I don't know what I was thinking about, I thought I was doing a factory reset) in TWRP recovery. So now the thing is tricky. I cannot boot my phone, and I don't know what is going on there because the screen is broken. I connected my phone to PC, and after typing "adb devices", I saw that device was offline(but at least there was a device listed, though it was offline instead of attched).
So I cannot use adb, I tried 4.4.3 stock RUU, but it said that "ERROR 170 USB CONNECTION ERROR". I've installed HTC Sync Manager, it couldn't detect my phone, either.
I cannot enter the recovery, either. I don't know what to do now. Wonder if anybody here could help me. Any help appreciated.:crying:
mycityofsky said:
My phone's screen was broken, I could only use my phone with some tools like screenshot. Today before I was about to repair the phone, I wiped all the things (including system, I don't know what I was thinking about, I thought I was doing a factory reset) in TWRP recovery. So now the thing is tricky. I cannot boot my phone, and I don't know what is going on there because the screen is broken. I connected my phone to PC, and after typing "adb devices", I saw that device was offline(but at least there was a device listed, though it was offline instead of attched).
So I cannot use adb, I tried 4.4.3 stock RUU, but it said that "ERROR 170 USB CONNECTION ERROR". I've installed HTC Sync Manager, it couldn't detect my phone, either.
I cannot enter the recovery, either. I don't know what to do now. Wonder if anybody here could help me. Any help appreciated.:crying:
Click to expand...
Click to collapse
Finally it worked, I kept pressing volume up and power button to reboot to fastboot, then pressed volume down and power in order to recovery, now RUU worked just fine. Cheers!