Hi everyone,
I have just bought an used HTC Radar 4g. It worked normally until I tried to flash the ship rom from Tmobile using RUU, it got an error and cancelled at 5%. Since then, the phone stuck at the bootloader screen and I even cannot enter the usb host mode by holding camera + volume down + power.
I tried to flash another ship rom from vodafone or europe with RUU but it got error too.
I already prepared goldcard usb and Y cable for goldcard method, but I cannot enter the usb mode to do it.
One more thing, the phone cannot be turned on without plugged into the power supply or laptop.
Here's some information in the bootloader screen:
PI06110
SPL-1.8.160015.3(131745)
eMMC SAMSUNG 7376MB
TOUCH A1(F:80, ID:10, V20, B:AA)
Radio-16.23.02.09_2
Can anyone help?
Happened to me with my second "test" radar. Nothing worked, not even Y-cable.
I'm afraid, we have a small dusty cold brick
CreAtive_34 said:
Happened to me with my second "test" radar. Nothing worked, not even Y-cable.
I'm afraid, we have a small dusty cold brick
Click to expand...
Click to collapse
Got it, just sent it to the repairing service and wait
Someone tell me my phone need to change the mainboard, is it really that bad?
Related
All,
I inherited a seriously injured HTC surround, and I have decided to use it as a project phone.
Current status - Half Bricked on the bootloader + when it boots it immediately asks to be connected to restore backup. Unfortunately I have no zune backup and neither does the original owner of the device.
So I have read everything I could find on the half-brick issue and it seems that some folks are having success using the goldcard method to over write their boot loader with various HTC devices. I am will to try this but all the vids I have seen tutorials etc show that you have to put the device into enter usb host mode (blue writing on white screen)
Only problem is ....I have no idea how to do this on the Surround. I have tried every button combo on boot and cannot find it.
Someone here must know how to do this in return I will post my findings on whether or not the Goldcard trick works to repair a 1/2 brick surround.
Thanks
rob243 said:
All,
I inherited a seriously injured HTC surround, and I have decided to use it as a project phone.
Current status - Half Bricked on the bootloader + when it boots it immediately asks to be connected to restore backup. Unfortunately I have no zune backup and neither does the original owner of the device.
So I have read everything I could find on the half-brick issue and it seems that some folks are having success using the goldcard method to over write their boot loader with various HTC devices. I am will to try this but all the vids I have seen tutorials etc show that you have to put the device into enter usb host mode (blue writing on white screen)
Only problem is ....I have no idea how to do this on the Surround. I have tried every button combo on boot and cannot find it.
Someone here must know how to do this in return I will post my findings on whether or not the Goldcard trick works to repair a 1/2 brick surround.
Thanks
Click to expand...
Click to collapse
Hi,
Power off the device
Press and HOLD both camera and volume down buttons
Press power on button and KEEP holding both battery and volume down buttons
After boot screen will follow the usb screen
Now release battery and volume down buttons
Regards, ansar
Ok I can only get to the tricolor screen showing the 1/2 brick spl. is the the usb host mode? Because I see on some videos on youtube a white screen with blue writing that says enter usb host mode. This is what I am trying to achieve.
Or if this is the USB host mode should I just attempt to do the flash via gold card and see if I can get rid of teh 1/2 brick?
USB Host mode
To enter USB host mode turn off the phone, then press and hold VOL down + camera buttons, then press power.
But the phone will not enter USB host mode if you only see one line en the tricolor screen (this state is half bricked). For the phone to be able to enter USB host mode, the tricolor screen must have more than 1 line but the only missing part must be Serial/USB at the bottom. Check well the videos on youtube, and you will notice before entering USB host mode that the tricolor screen have more than 1 line (someone call this state small half bricked).
My phone is also half bricked (one line in the tricolor screen), the only solution I have found is to do an HTC OEM update, either by waiting for HTC to release an update (that includes a bootloader) through zune or by forcing it (for this the phone needs to be developer unlocked).
P.S. ChevronWP7 is not selling more unlocking tokens at the moment, and the $99 AppHub membership is too expensive for me.
Thanks Guys
After reading your posts I tried it out on my good surround and sure enough was dumped directly into Enter USB Host Mode screen
So now I am sitting here wondering what can I do with this thing it will not boot to anything but the screen to connect to restore backup.
Could I give anyone here anything useful about the device? Maybe disect it and post pics? Maybe someone could find these jtag posts? Or keep it for spare parts? Seems like a waste to just chuck it
Maybe you can repair it
rob243 said:
After reading your posts I tried it out on my good surround and sure enough was dumped directly into Enter USB Host Mode screen
So now I am sitting here wondering what can I do with this thing it will not boot to anything but the screen to connect to restore backup.
Could I give anyone here anything useful about the device? Maybe disect it and post pics? Maybe someone could find these jtag posts? Or keep it for spare parts? Seems like a waste to just chuck it
Click to expand...
Click to collapse
rob243, you can try to install a new firmware, depending if the firmware is a version inferior to 2250.21.40500.502. You can use a tool called Cab Sender (http://forum.xda-developers.com/showthread.php?t=1306415) to send firmware version mondrian_2250.21.40500.502.cab (search in xda-developers), for the enter the phone to recovery mode (just press and hold CAMERA, then power, ang then release the 2 buttons).
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
thermbug said:
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
Click to expand...
Click to collapse
If you can get into hboot you arn't bricked.. Tho you usb port may be dicked like a broken part..
I would try to go stock for the hell of it.. I haven't had any issues.. I have in the past hung my phone locked it and dicked sense up.. But a battery pull always helped get back into hboot
So I wonder what is going on with yours.
Have you tried using a different usb cable ?? Or pluggin the phone in and let it charge over night ??
#Root-Hack_Mod*Always\
thermbug said:
Yesterday, battery was at 70% when I headed out. Phone wouldn't boot when I tried it later so I assumed battery died.
Put it on charger and it went to green quicker than expected but still wouldn't boot.
PWR Vol- wouldn't go to bootloader
Went home and connected to PC with ADB, adb devices showed me in recovery, screen stayed off. Issues an adb reboot command litt the screen briefly to the white background green HTC but went back to dark.
Issuing adb reboot-boorloader did bring me to bootloader screen but it wouldn't stay there.
Saw notes that my recovery may have been hosed. so tried to re-push cwm with fastboot flash recovery c:\reco.img (renamed cwm to reco.img)
I don't recall my prompt responses. I'm hoping that along the way I didn't flash recover to boot or vice versa. I think I have may have flubbed one of the commands along the way.
Anyway at this point the 3 button boot does nothing, nor does pwr vol - not does it appear via usb as a device on 2 separate pc's with frresh driver installs and fresh sdk installs.
I have dropped pc86img.zip in the root of the sdcard now just in case i get it to boot.
The usb port is being sorta wonky with my red light coming on only intermittently and I now have to wiggle carefully.
I had been running current rev of viper rom. hadn't touched kernel or poked the phone in naughty places for weeks.
Running RUU exe doesn't detect phone either.
Now for the conspiracy part, has anyone else noticed a few more postings of this ilk in recent days? I may now be paying more attention to 'I'm bricked' postings than normal but it feels like there are other similar stories of unexplained malfunctions. I'm not saying sprint or htc pushed something but maybe an update in apps that many of us rooted users have in common?
When boot key combinations do nothing, doesn't show in adb with usb connected and it won't boot is one truly "bricked?"
I'll head to sprint to diagnose usb connector. If that is the issue, I'll reflash to stock and revert to s-on. I don't feel that anything I've done recently contributed to the death f the phone. No OC or under volting.
Click to expand...
Click to collapse
youre not bricked... you get into hboot fine... its running that you have a problem with so we go tier up...the eMMC of it all...there is a post by unknownforce that is for downgrading hboot 1.5 to .14 or less but follow those directions to the T and it willrewrite everything in there and then if you choose to do so you caqn update to hboot 1.5 and the new RUU and all from there
Can't get into hboot anymore.
can't get into hboot anymore, and if I'm s-off I can't run the process.
thermbug said:
can't get into hboot anymore, and if I'm s-off I can't run the process.
Click to expand...
Click to collapse
Well flashing anything important via usb cable when you don't have a solid connection is a very bad idea, it's quite possible that you are bricked if your phone literally won't even turn the screen on. You can try going to the hboot downgrade thread (I personally bricked my phone while flashing an experimental ROM, and I recovered everything by using step 3 ONLY in the hboot downgrade thread), but I wouldn't try doing anything until you get that usb port on your phone fixed...it shouldn't have any "wiggle room" when the usb cable is plugged in
Edit: if you get a charging light when your phone is plugged in, you're probably not bricked. I never once saw a charge light when I was bricked
w0rdOo said:
Well flashing anything important via usb cable when you don't have a solid connection is a very bad idea, it's quite possible that you are bricked if your phone literally won't even turn the screen on. You can try going to the hboot downgrade thread (I personally bricked my phone while flashing an experimental ROM, and I recovered everything by using step 3 ONLY in the hboot downgrade thread), but I wouldn't try doing anything until you get that usb port on your phone fixed...it shouldn't have any "wiggle room" when the usb cable is plugged in
Edit: if you get a charging light when your phone is plugged in, you're probably not bricked. I never once saw a charge light when I was bricked
Click to expand...
Click to collapse
A slight wiggle is alright. If your led light is coming on and off then somethin is broke.
Sent from my PG86100 using xda premium
Try taking the battery out for a few hours and letting the phone rest. This worked somehow for a few users.
Here is the story. my parent bought my brother the amaze 4g for his birthday. he was messing with it trying to root it and such and today he was trying to install a new rom and while it was installing he disconnected the cable, the screen is a black background with green arrows and a phone. I'm not familiar with this but when i press the power button and down button it says unlocked at the top. When i tried to install the stock rom it keeps coming up with no image.
Is there a way to fix this? Thanks in advance
Was he trying to make it s=off? When I did that on my phone that happened, and it is easy to fix. Ask your brother first, but if he was trying to get s=off, all you have to do is get the leaked ICS image from the dev section and flash it. Download the file from here: http://forum.xda-developers.com/showthread.php?t=1615164&highlight=leak, rename it to PH85IMG.zip and put it on the external SD card, then boot into the bootloader and press the up volume button when it asks if you want to update. However, this only works on T-Mobile phones.
I tried that a bunch of times already but every time it starts checking and at the then it just says no image and goes back to H boot
Edit: It is a T-Mobile phone
Sorry, I just reread your original post, your bootloader has to be locked to flash the file, so boot into fastboot and run "fastboot oem lock" from your computer's command prompt.
I just tried it and it gets stuck on "waiting for device" and I don't know if it makes a difference but something happened with his SD card and my computer couldn't read it so I had to reformat it and its empty right now
If that doesn't work, I am not sure what can be done. I wouldn't think the SD card would matter, but make sure you formatted it as FAT32, just in case, and leave the zip file off of it, go into bootloader and use the volume buttons to go to fastboot, and click the power button to select it, then plug it into the computer. If it then says fastboot usb I would think the oem lock should work, but if that fastboot usb doesn't come up, there might be something wrong with the whole boot loader or something. Sorry I could not help any more.
I went into fastboot and connected the USB cable and it didn't change, it still just say fastboot highlighted in red
I have no idea what you could do to fix that, then. Again, I apologize that I couldn't help more, and I wish you the best of luck with this.
Thanks for trying to help anyway
edit
Adb debugging wasn't on I bet :banghead:
I don't get how he got in this position. I don't use a cord to install ROMs. If he were to unplug, I don't see what that would do except stop charging... Unless he was in disk mode and it caused a bad unmount and corrupted card.
I would try the steps above with a fresh sd card and it should work. Redownload the ics or gingerbread ruu and go through the steps.
He was in the process of flashing his phone with some rom he wanted but then somehow he accidentally disconnected the USB cable and it froze up. Now every time you turn the phone on, after the HTC screen it shows the picture that its being flashed (black background with green arrows going into the phone) so I can't turn the phone on at all but I do know that his phone had usb debugging on before he flashed it.
Ok so I found out he was actually trying to get S-off with some "wire trick" and he said at the beginning of the process the phone was restarting and he accidentally unplugged the usb and when the phone rebooted, it got stuck in the dark screen with the green arrows
This just means he needs to continue trying the wire trick. I was stuck at the screen too. I just kept running the program and attempting the wire trick until I got it right.
Sent from my HTC_Amaze_4G using XDA
I just tried the wire trick and it got all the way to counting 45 seconds and the phone keeps rebooting. So I tried to run the program again and now it says connect device and install drivers
Is there a way to get this phone to work again?
Djordje1000 said:
Is there a way to get this phone to work again?
Click to expand...
Click to collapse
install htc drivers, thats also why it didnt read the fastboot demands
I did I installed one from the htc website for the amaze 4g and one that someone posted on this forum
Djordje1000 said:
I did I installed one from the htc website for the amaze 4g and one that someone posted on this forum
Click to expand...
Click to collapse
i dont know what to say then :/ mabey the computer cant read the amaze
Since I can't get past the htc screen. The computer wont recognize that the phone is connected to it
I has a similar problem when trying to do s-off - try installing htc drivers again after plugging in the usb.
I have a T-Mobile HTC One, unrooted and running the stock OS. A few hours after installing the 4.3 OTA update, the phone had a series of crashes in UIServer (or something similar), and when I attempted to restart it, it didn't start up again. The phone was charging at the time, and its red charging LED stopped working shortly afterward.
Now the phone won't boot, and when I connect it to my computer it shows up as QHSUSB_DLOAD. What can I do?
i<3burritos said:
I have a T-Mobile HTC One, unrooted and running the stock OS. A few hours after installing the 4.3 OTA update, the phone had a series of crashes in UIServer (or something similar), and when I attempted to restart it, it didn't start up again. The phone was charging at the time, and its red charging LED stopped working shortly afterward.
Now the phone won't boot, and when I connect it to my computer it shows up as QHSUSB_DLOAD. What can I do?
Click to expand...
Click to collapse
Unfortunately I have the same issue. I have contacted HTC and they told me to do the volume up and down and power button to recalibrate the battery but to no avail. I have tried using the T-mobile RUU but it doesn't recognize the device when plugged in to the PC. I bought the phone unlocked so I am not sure if T-mobile will even help me send it into HTC. I would be grateful for any help!
Can you get into the bootloader?
No, the phone is completely unresponsive, can't get into boot loader, the light and volume key thing didn't work either. I'm starting the phone is just hardware bricked. My device is completely stock too, how could HTC allow a manufacturer software update hardbrick their phone? Not sure if I will ever buy HTC again after this.
fenrir604 said:
No, the phone is completely unresponsive, can't get into boot loader, the light and volume key thing didn't work either. I'm starting the phone is just hardware bricked. My device is completely stock too, how could HTC allow a manufacturer software update hardbrick their phone? Not sure if I will ever buy HTC again after this.
Click to expand...
Click to collapse
Hold down the power button for 20 seconds or so. This brought me to boot loader from this issue. Flashed an RUU from that point to get working again.
(You will have to hold down the power button until it gets the HTC screen every time the RUU says 'waiting for bootloader' unless it's already there.)
Sent from my Nexus 10 using Tapatalk 4
yesterday i went from citrus to slimrom. Dont know what caused this, but I havent found anyone else with this problem when i tried to search for it.
This is what I have found out:
1. If I connect my charger when the phone is on, nothing happens (cant seem to connect it to the computer either..).
2. If i reboot it with charging cable in. it hangs with the "blinking red light".
I can reboot it by unplugging the charger and pressing power button a couple of times.
3. If I reboot it and let it boot to mi-logo, I can connect charger and it will charge.
This is the only way I have found it to charge: reboot, wait until logo and then connect charger, it will charge every time. Never if I connect it when the phone is booted).
Anyone know how to fix it, the phone works perfectly otherwise.
I have tried this:
installed CM 13, with cm 13 firmware.
installed Citrus again.
Installed exodus MM-rom.
nothing changes this.
The phone came with unlocked bootloader when I bought it from ebay, guess it is unofficially unlocked? Any way to check if its unofficially or officially unlocked? does it matter?
Sounds very similar to what happened to me and it was because the bootloader somehow locked itself again. I just plugged it back into my computer and unlocked it again.
Thanks, but when I try to unlock it with mi unlock tool, it says "couldn´t verify device, no need to unlock"...
I can enter twrp, is my device still locked but I can enter recovery?
Update: I have tried this:
Flashed a stock rom, relocked bootloader, still had the same problem...
unlocked bootloader officially. Rooted and installed krexus rom, still have the same problem...
Found this thread: https://xiaomi.eu/community/threads/redmi-note-3g-not-charging-no-pc-connection.26290/
Does anyone know how to enter engineering mode on rn3sd?
Anyone know if I can short circuit the charging port like described in that thread?:
"After connecting a faulty USB cable my phone stopped connecting to PC and charging - It shows the symptoms of being in USB Host mode permanently.
I was able to charge the phone by entering engineering mode (Dial *#*#3646633#*#* ) and going to the Hardware Testing tab, scrolling up to UART/USB switch and selecting UART
The phone would then charge normally."
"I had that problem too. And I did what u did too.. the problem is that there is some sort of confusion between Otg and USB... so you will have to short circuit the charging port to revive it.
First open up your phone. To make the internal components visible.
Then connect ur charger to the phone.
While the charger is connected, use a flat metal or wire to short circuit the charging port. You should see a small spark and your phone would off.
Connect battery and Switch it back on. If it doesn't work try again for three -four times. If it doesn't still work then send your phone for repairs.
Don't be afraid, it's only 5volts your phone won't blow up. Short circuiting the charging port would revive it..
I did that to mine and it has been working well till now. "
Holy crap my usb has been busted for a while now (charges only and no usb to pc connection) and I might just try this
asusm930 said:
Holy crap my usb has been busted for a while now (charges only and no usb to pc connection) and I might just try this
Click to expand...
Click to collapse
Let me know how, i dont know what to do
FIXED! Suddenly it works.. I have used a couple of different roms. slim 7, miui, slim 6 etc.
Flashed the new zephyr 7 rom, and suddenly my phone can charge without rebooting!
Just wanted to update the thread if someone gets the same error!