I was trying to s-off my HTC Amaze. When I reached wire trick, my first attempt failed and ControlBear told me that s-off failed.
I tried again and suddenly ControlBear stopped detecting my phone. I looked on my phone and it looked like bricked.
I unplugged USB cable and tried to switch on my HTC Amaze but failed. I also tried to log into bootloader by pressing Volume Down + Power but phone did not turn on. I replaced battery, tried to charge the mobile but in vain.
When I put my phone on charge with either USB cable or wall plug, not even charging light turns on.
Now I am unable to turn my HTC Amaze on. I have also tried HTC Unbricking Project http://forum.xda-developers.com/showthread.php?t=1627882 but it does not detect my phone.
Please help me!!
I am S-ON, stock ROM GB.
egulfam said:
I was trying to s-off my HTC Amaze. When I reached wire trick, my first attempt failed and ControlBear told me that s-off failed.
I tried again and suddenly ControlBear stopped detecting my phone. I looked on my phone and it looked like bricked.
I unplugged USB cable and tried to switch on my HTC Amaze but failed. I also tried to log into bootloader by pressing Volume Down + Power but phone did not turn on. I replaced battery, tried to charge the mobile but in vain.
When I put my phone on charge with either USB cable or wall plug, not even charging light turns on.
Now I am unable to turn my HTC Amaze on. I have also tried HTC Unbricking Project http://forum.xda-developers.com/showthread.php?t=1627882 but it does not detect my phone.
Please help me!!
I am S-ON, stock ROM GB.
Click to expand...
Click to collapse
You was trying from windows or Ubuntu??
Sent from my HTC_Amaze_4G using xda premium
ravike14 said:
You was trying from windows or Ubuntu??
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I was trying from Ubuntu.
Try to charge your phone again or hang it to wall charger without battery for 45 minutes and than try it again.
Sent from my HTC_Amaze_4G using xda app-developers app
shubham211995 said:
Try to charge your phone again or hang it to wall charger without battery for 45 minutes and than try it again.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
As per your advice, I put my mobile on charge (without battery) for 45 minutes. After it I tried again but there is no success.
egulfam said:
As per your advice, I put my mobile on charge (without battery) for 45 minutes. After it I tried again but there is no success.
Click to expand...
Click to collapse
did you inform this to the unlimited.io team?? did you download the correct ubuntu version for your device? and the correct one for your phone?? :/ cuz it's really impossible none bricked their phones for a really long time from S OFF
I asked him but he told me that he downloaded correct version...
No issue with that..
Sent from my HTC_Amaze_4G using xda app-developers app
You should try another battery for surity
Sent from my HTC_Amaze_4G using xda app-developers app
I solved it
I had the same problem but I resolved it.
Android
1)Enter in fastboot
Code:
Press vol down + power button
---------------------------------------------------------------------------------------------------------------------------------------------------------
PC
1)Open ubuntu
2)Copy backup to Desktop(I will explain for backup made in clockwork) and restart Ubuntu.
3)When Ubuntu starts(in the screen when you should enter the password) press Ctrl + Alt + F4
4)Enter your username
5)Press Enter
6)Enter your password
7)Press Enter
8)Write in the terminal and enter your password
Code:
sudo -i
9) Install fastboot
Code:
sudo apt-get install android-tools-fastboot
10) Write in the terminal
Code:
cd /home/your username/Desktop/clockworkmode/backup
11)Press ls
12)
Code:
cd /your backup name
Eg: 2015-30-05-12.14.09
13)Flash boot
Code:
fastboot flash boot boot.img
14) Flash recovery
Code:
fastboot flash recovery recovery.img
15)Reboot bootloader
Code:
fastboot reboot-bootloader
16)Your phone now restarts into bootloader
17) Enter into recovery
18)Backup and restore and come back to your backup
I hope my tutorial helped you
Have a nice day.
RelaxedMind said:
I had the same problem but I resolved it.
I hope my tutorial helped you
Have a nice day.
Click to expand...
Click to collapse
Glad you figured it out on your own, and thank you for returning and posting your instructions to help others.
Related
I tried my hand on rooting my Evo 3D. Was successful using revolutionary, but i kept getting error messages so i wanted to put it back to the original way it was.
I did the updating of the ROM through the Shooter Shippoed ROM, i have the drivers installed, and now it's stuck at the HTC screen with triangles on the corners.
When i run the ROM update utility, the update doesnt finish and says, "ERROR [152]: IMAGE UPDATE ERROR". So i proceed with the recovery process, but it still goes through the same thing.
I can't get to Recovery Mode either (through vol down+power)
Help?
BTW, It's GSM.
By recovery mode, do you mean fastboot? Or will it fastboot, but not go into recovery?
Sent from my PG86100 using XDA Premium App
troublein420 said:
By recovery mode, do you mean fastboot? Or will it fastboot, but not go into recovery?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
It won't load the fastboot, so i can't go to recovery options. Basically, when i turn it on, it's stuck on that black screen with HTC and triangles on the corners.
When you plug it to a computer, do any drivers come up? Check device manager in settings system on the comp.
Sent from my PG86100 using XDA Premium App
Edit: use usbview.exe if u cant see anything.
troublein420 said:
When you plug it to a computer, do any drivers come up? Check device manager in settings system on the comp.
Sent from my PG86100 using XDA Premium App
Edit: use usbview.exe if u cant see anything.
Click to expand...
Click to collapse
I installed the drivers, then when i plug it in the first time, it recognizes it but when i unplug and plug it again, it doesn't recognize it anymore.
well when it does come up, try going to sdk tools in command line and run "adb devices" and "fastboot devices" if fastboot comes up, you can probably load everything through there.
Hi everybody,
First of all, I apologize for my bad English ^^
Then, as you can see from my title, I have some problem with my Flyer....
I just update my HoneyComb mwakious Flying Rom (I was already on HoneyComb before) and I used it in the following morning and everthing worked, until the following afternoon.... so I was here to ask for help to you....
Nobody can help me ?
Sent from my GT-I9100 using XDA App
boby08 said:
Nobody can help me ?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
If I were you, I would follow instructions on following thread
http://forum.xda-developers.com/showthread.php?t=1358758
The install is using fastboot so it would work for you.
Your flyer is in QDL mode. There is no way to power it off short of opening the device and disconnecting the battery. Based on your description of how you got there it should be fine ok if you let the battery run down so that it powers off completely and then charge and power on again provided you had a working CWM installed. If that doesn't work you will have to send it in for repair.
globatron said:
Your flyer is in QDL mode. There is no way to power it off short of opening the device and disconnecting the battery. Based on your description of how you got there it should be fine ok if you let the battery run down so that it powers off completely and then charge and power on again provided you had a working CWM installed. If that doesn't work you will have to send it in for repair.
Click to expand...
Click to collapse
I tried to disconnect the battery, charge flyer and put it on but it doesn't work... Is there any way to left QDL mode with a program or something else ? :crying:
From what I understand, Qualcomm download mode means that everything is gone, including the ROM and Hboot. Without hboot, you can't recover from this. As globatron mentioned earlier (in December!) you need to send the phone for repair.
HTC Flyer can't enter recovery mode & USB cable is not detecting during unbrick
Dears please help!!!
I think, i have bricked my HTC Flyer (P510e / PG41100) when i was installing new ROM.. I am unable to enter recovery mode or any other booting mode.. The screen is flashing & vibrating some time with HTC's intro & comes with blank screen.. The orange colour (indicator for charging) is blinking always..
I have tried the steps as per the post http://forum.xda-developers.com/showthread.php?p=16190536#post16190536 . But, the USB cable is not connecting properly with PC. And in Command prompt, the ADB devices is not listing properly. It shows USB connection error when i run stock ROM. Tried in another PCs too. But, failed.
Also, the device is getting connected & disconnected continuously. (shows as a removable disc).. .The sae time, in the screen CWM's interface is coming & going.... Not stable. stays maximum 3 - 5 seconds...
Kindly request you to help me to come out from this problem..
Thanks in advance for your help...
Renjith.
renjithsuresh said:
Dears please help!!!
I think, i have bricked my HTC Flyer (P510e / PG41100) when i was installing new ROM.. I am unable to enter recovery mode or any other booting mode.. The screen is flashing & vibrating some time with HTC's intro & comes with blank screen.. The orange colour (indicator for charging) is blinking always..
I have tried the steps as per the post http://forum.xda-developers.com/showthread.php?p=16190536#post16190536 . But, the USB cable is not connecting properly with PC. And in Command prompt, the ADB devices is not listing properly. It shows USB connection error when i run stock ROM. Tried in another PCs too. But, failed.
Also, the device is getting connected & disconnected continuously. (shows as a removable disc).. .The sae time, in the screen CWM's interface is coming & going.... Not stable. stays maximum 3 - 5 seconds...
Kindly request you to help me to come out from this problem..
Thanks in advance for your help...
Renjith.
Click to expand...
Click to collapse
run adb on pc and conect the device (with usb), then type: adb reboot recovery...u should on cwm recovery now...:good:
sdpinsens said:
run adb on pc and conect the device (with usb), then type: adb reboot recovery...u should on cwm recovery now...:good:
Click to expand...
Click to collapse
sdpinsens thanks for your reply.. But, there is an error while processing adb reboot recovery.."error: device not found".. Could you please advise what has to be done next...
first: make sure htc sync is installed on ur pc, because it's need htc usb driver to define ur device....But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
second: try to boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB....., then in pc adb type command: adb reboot recovery ....
if you still can't resolve the problem, try this command: type command:
fastboot flash recovery recovery.img --------> you can get recovery.img file from: http://forum.xda-developers.com/showthread.php?t=1775840
then
fastboot oem lock
and good luck!
Sent from my HTC Flyer P510e using xda premium
sdpinsens said:
first: make sure htc sync is installed on ur pc, because it's need htc usb driver to define ur device....But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
second: try to boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB....., then in pc adb type command: adb reboot recovery ....
if you still can't resolve the problem, try this command: type command:
fastboot flash recovery recovery.img --------> you can get recovery.img file from: http://forum.xda-developers.com/showthread.php?t=1775840
then
fastboot oem lock
and good luck!
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
:good: Thanks.. CWM working perfectly. Tablet came back to life.. did the following steps..
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Thanks again for your support...
renjithsuresh said:
:good: Thanks.. CWM working perfectly. Tablet came back to life.. did the following steps..
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Thanks again for your support...
Click to expand...
Click to collapse
ur wellcome.....:highfive:
sdpinsens said:
first: make sure htc sync is installed on ur pc, because it's need htc usb driver to define ur device....But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
second: try to boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB....., then in pc adb type command: adb reboot recovery ....
if you still can't resolve the problem, try this command: type command:
fastboot flash recovery recovery.img --------> you can get recovery.img file from: http://forum.xda-developers.com/showthread.php?t=1775840
then
fastboot oem lock
and good luck!
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Thanks. It's working property.
I've tried to also find the tbauto root downloads but my browsers never find the page no matter who's link i try I'm a massive noob but i have rooted my nexus s 4g and last night i put ics onto my friend touch pad so I thought i was able to follow directions but i guess not.
steps i took:
downloaded all files needed to run revolutionary
downgraded
ran revolutionary
got correct code from serial number
reboots into bootloader (on phone ) says waiting for fastboot on revolutionary
help out a noob!
screen shot
View attachment 928832
loook
colbatronbmw said:
I've tried to also find the tbauto root downloads but my browsers never find the page no matter who's link i try I'm a massive noob but i have rooted my nexus s 4g and last night i put ics onto my friend touch pad so I thought i was able to follow directions but i guess not.
steps i took:
downloaded all files needed to run revolutionary
downgraded
ran revolutionary
got correct code from serial number
reboots into bootloader (on phone ) says waiting for fastboot on revolutionary
help out a noob!
Click to expand...
Click to collapse
once the phone boots into the bootloader you have to press the power button to select fastboot from the menu (vol +/- are used to scroll). this will put the phone in fastboot. if your usb connection is detected it should display "fastboot usb" on your phone after a few seconds.
what software version do you have? If it is 2.11.605.9 then there are extra steps need to get it.
---------- Post added at 02:36 PM ---------- Previous post was at 02:32 PM ----------
If you are on the system version stated above use this http://www.cd-net.net/dev/Joomla/index.php/projects/htc-thunderbolt-hacking to root.
Thanks I'll try it
Sent from my Nexus S 4G using Tapatalk
Another option disconnect the phone from the USB and reconnect it after a few seconds. Might have to power cycle the phone also.
Solution to "waiting for fastboot"
I just ran into this same problem, nothing I could find would work. I was using the thunderbolt all-in-one solution to root my phone and was stuck on the revolutionary step. If I power cycled and booted into recovery and selected fastboot, the phone would say "fastboot usb" for a moment, but then it would just say "fastboot". Finally, I found a solution. With Revolutionary stuck at "waiting for fastboot...." I did the following:
* uninstalled the HTC drivers
* reinstalled the drivers
* power cycle phone and boot into recovery
* select fastboot
again it said "fastboot usb", then toggled to "fastboot", but then windows gave me a message telling me that a device driver was installed, and it togged back to "fastboot usb". revolutionary was then able to find my phone and go to the next step which was... booting into fast boot (once moar). again it hung here, and I had to repeat all of the above steps.
after this I was able to install CWM successfully, and use the all-in-one tool to install the super user program.
What version of windows are u on?
Sent from my Liquidsmooth Rezound using xda app-developers app
tburns said:
What version of windows are u on?
Sent from my Liquidsmooth Rezound using xda app-developers app
Click to expand...
Click to collapse
I am on Windows 7
Try running the tool on administrator. Also when you connect the device before you start the process and you get the prompt to run HTC sync don't touch it. Don't close or allow the dialog just leave it be until the tool is run.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Try running the tool on administrator. Also when you connect the device before you start the process and you get the prompt to run HTC sync don't touch it. Don't close or allow the dialog just leave it be until the tool is run.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Great idea, thanks. If I root another tbolt I'll try this out.
Hello,
I was trying to convert my T-Mobile HTC One to a Developer Edition so I could receive OTA updates by following the instructions here. I made it to step 11 where I changed the CID to BS_US001 (from T-MOB010), but encountered an error trying to change the MID to PN0712000 (from PN0713000). I also tried to change the CID to 11111111 which also worked, but I was still unable to change the MID. At this point I searched around for alternate ways to change the MID and found this post which I was able to follow until step 5. When I rebooted to bootloader at step 5, the phone never turned back on and I got a message in Windows saying "USB device not recognized".
The phone doesn't turn on at all, I have tried to hold power and power + vol down for around 30 seconds and nothing happens aside from a few vibrations every 20-30 seconds. I've tried holding power + both volume buttons for over 2 minutes to no avail. The PC I'm using is Win 8.1 using the USB 2.0 ports. I left it connected to the wall charger overnight and it only gave me a flashing red light.
Am I permanently bricked? No matter what I've tried, the phone just will not turn on at all. I tried running the RUU but of course it didn't work because the phone wasn't recognized as being plugged into the PC. Any help would be greatly appreciated. I've also attached a screenshot of the command window up until the point where I tried to reboot and it never turned back on.
When you get the "unrecognized device" the phone is on. Chances are, it's running a badly modified HBOOT that is trying and failing to get into RUU. LAst tiome that happened to me, holding the power button for *exactly* 16 seconds brought it into RUU mode (did not display the HTC RUU logo). From there I was able to run the RUU.
If you can get to that point, the RUU should install so long as you are SuperCID. If it does not;
Make sure you have the latest adb/fastboot - (or search google for "Minimal ADB and Fastboot" which has always worked for me)
fastboot reboot-bootloader
Install the modified tmous hboot following the instructions here:
http://rumrunner.us/hboots/
This will enable the use of the fastboot oem writemid command allowing you to change your MID.
I use this HBOOT when doing any conversions on my device. It allows all of the commands and has yet to fail me getting RUU's to run.
I have converted from T-Mobile to Dev, GPe and Int'l (and back to T-Mobile) several times and haven't bricked.
Keep working at it. These things are hard to brick!
Thank you for the reply! I'll try what you mentioned and report back on the results. I probably should have waited until I had a windows 7 PC to work on, but mine is currently in shipment. Hopefully with those tools you mentioned I can resurrect it.
Sent from my Galaxy Nexus using xda app-developers app
Well, I was able to get it working again. I actually tried plugging it into the usb 3.0 port on win 8.1 and it didn't give the unrecognized device message so I went from there. I did have to install some 8.1 fastboot drivers for usb 3.0 which was easy. I tried to run the t mobile ruu which didn't work because I had changed the CID but after that the device just booted normally.
Sent from my HTC One using xda app-developers app
dg32 said:
Well, I was able to get it working again. I actually tried plugging it into the usb 3.0 port on win 8.1 and it didn't give the unrecognized device message so I went from there. I did have to install some 8.1 fastboot drivers for usb 3.0 which was easy. I tried to run the t mobile ruu which didn't work because I had changed the CID but after that the device just booted normally.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Try flashing a bright light into the proximity sensor while holding the power button + vol down buttons together.
:good:
So long story short my cousin tried to flash the SlimKat ROM the other day and somehow managed to soft brick his phone. Now it gets stuck on the splash screen of "HTC Quietly Brilliant". I thought it would be an easy fix by sideloading a new ROM by adb but that didnt work. I can get it into bootloader (1.44.0000) and fastboot but the real problem is that the computer doesnt recognize the phone at all. I uninstalled and reinstalled all the drivers and have tried 2 different computers and 3 different cables. I can get it to say fastboot usb but whenever I type a fastboot command it gets stuck "waiting for device" and when i type "adb devices" it doesn't find any device.
Has anybody seen this or have a solution?
hold vol down + power... Until boot loader shows up, select recovery.
Sent from my HTC One using XDA Premium 4 mobile app
TopoX84 said:
hold vol down + power... Until boot loader shows up, select recovery.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So now it finds the adb device, but when i do
adb sideload (filename).zip
It only comes up with a list of available adb commands. Am I not doing the command right? As far as I can see the phone has no /system partition and it cant mount /external_sd to install the old ROM zip from the sd
U have to move the ROM into the adb.exe folder, rename the ROM into ROM.zip
Sent from my HTC One using XDA Premium 4 mobile app
Thanks for the help. I ended up following the instructions from the very bottom of this guide.
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
After that it worked great!