So a friend handed me his bricked HTC One and asked if I can unbrick it for him. I have fastboot and ADB installed and functioning on my Ubuntu box, but I can't seem to talk to the phone.
The phone is bootlooping after what I presume was a failed attempt to root/unlock/flash. Here's what it says:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.03
OpenDSP-V32.120.274.0909
OS-3.24.531.3
eMMC-boot 2048MB
Oct 4 2013,17:31:32.0
FASTBOOT USB
When I try to go into the bootloader menu and chose recovery (or any other option really) it just reboots into the above screen.
When I query from the command prompt:
lsusb
Bus 001 Device 005: ID 0bb4:0ff0 HTC (High Tech Computer Corp.)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
fastboot devices
no permissions fastboot
adb devices
List of devices attached
So basically I feel like if I can somehow talk to the phone, I can push a recovery boot? And restore the factory rom? But so far I can't seem to talk to it.
I tried using a win7 box I have access to but got into a cascade failure situation with malware or something.
Can anyone help or point me in the right direction?
Thanks in advance!
The first step is trying to run the RUU with a Windows machine. You can try to extract the rom.zip from the RUU but it'd probably be easier to just borrow a Windows computer for a bit. You need to make sure you find the right RUU for the device.
fastboot getvar all
will tell you the current firmware and carrier.
Related
Hey guys, I was hoping somebody could help me out with this. I can't seem to get my identifier token from the One. I've tried in Windows and Ubuntu. In windows, adb and foastboot wouldn't even recognize the phone whether in the fastboot mode or debug while booted normally. In Ubuntu, fastboot devices shows the device, but when I run fastboot oem get-identifier-token all I get is:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
Is there anything I can do?
Edit: I should add, that I wasn't even getting Ubuntu to recognize the device until I added the 99-Android.rules file in udev. I am running Ubuntu 12.10.
Edit 2: Got fed up and switched back to Windows. fastboot devices now shows the phone, but I am getting the same error as above now. This is soooo frustrating. Why does is work so easily for everyone else?
In case it helps, this is what my bootloader screen reads:
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 18 2013, 18:29:18:-1
Click to expand...
Click to collapse
And when I am trying to run the get-identifier-token command, there is a red box that says "FASTBOOT USB" inside it.
OK, I've officially been crowned dumb-**** of the new millenium. I started thinking to myself, "There is no way that this should be causing so much trouble for you if everyone else is getting it so easily. You must be making a really simple mistake."
Well, I found my assinine error. I was using hyphens instead of underscores in the get_identifier_token command. I could have just deleted this thread, but I'm going to give everyone the chance to laugh at my idiocy and the fact that I spent 3 hours trying to figure this **** out.
Copy and paste is your friend.
Sent from my HTC One using xda app-developers app
That's okay. I spent half an hour making the token paste properly into the box on htcdev
If anyone could spare a moment that would be most appreciated. I have searched for hours and my laptop is crying under the "weight of a thousand tabs" at the moment and have finally decided that my problem is not going to be solved by more forum browsing. Luckily I have all the links to tutorials I was following so I can pinpoint exactly where things went wrong.
The carrier: Virgin Mobile
The problem: Stuck in bootloader, no options working. Recovery and factory reset both yield nothing. RUU fails with error 170.
The History: I decided I was going to try and root my phone today. That actually worked via stock. Followed a guide that showed me how to unlock the phone (using HTCDEV) and pushed TWRP as my recovery.img. I flashed the stock ROM and had root access. Then I was following another guide to obtain S-OFF. It said that I should flash SetMainVersionLow via my recovery and the next step was to run "fastboot oem lock" which worked. Then it told me to run the RUU.exe which simply gives me error 170 "USB Connection Error". I was running adb and fastboot commands early from this same machine, and nothing changed from the point of "fastboot oem lock" and running the RUU, though now my device won't even show up in fastboot or adb.
Any help would be most appreciated. I'm 12 hours in surfing on the web for solutions and have got nothing. I have learned that this site rocks (just looking through posts and the general responses people get) and you can bet and help some stranger will give me on the internet will be paid forward five times over. I'm a computer major in school so I am well versed with technology but as you can tell my rooting experience is non-existent. Thanks all.
More info:
Windows 8 64-Bit
Bootloader displays the following:
*** RELOCKED ***
*** Security Warning ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
RADIO-1.09.00.0108
OpenADSP-v2.6.0.226.00.0217
eMMC-boot
May 17 2012,15:06:44
EDIT: I have, through restarting both laptop and phone a few times, obtained fastboot. My RUU now proceeds past where I would encounter error 170, but still fails. When I unplug the USB it says HBoot older. Anyone have a "newer" RUU?
fastboot getvar cid = SPCS_002
fastboot getvar mainver = 1.00.000.0
I was trying to use:
RUU_Shooter_ICS_35_S_Sprint_WWE_VM_1.13.652.2_Radio_1.06.00.0426_NV_1.53_144_release_262287_signed.exe
I also tried:
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
'
which gave me the error "CID incorrect"
I'm in Canada. HOX+ unlocked, bootloader too.
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.40.0000
CPDL-None
MICROP-None
RADIO-SSD: 2.14.55.11
eMMC-bootmode: disabled
CPU-bootmode: disabled
HM Secure boot: enabled
MODEM TYPE : MDM9215M
Dec 28 2012, 22:18:14
Stuck in bootloop after trying to update ViperXL.
MTP driver won't load no matter what I try. ADB doesn't see my device.
Can get to recovery TWRP v2.4.1.0 Venom
But that is ALL!
No data anywhere. No ROMs, no backups. NOTHING
All I can do is go to reboot and Power Off. If I try to reboot it tells me there is no OS.
And I cannot do anything...... Flash or Sideload...... ADB doesn't see my device.
I've read and tried for hours, days, months!
Any ideas out there??
Thanks
vectorer said:
I'm in Canada. HOX+ unlocked, bootloader too.
EVITARE_UL PVT SHIP S-ON RL
HBOOT-1.40.0000
CPDL-None
MICROP-None
RADIO-SSD: 2.14.55.11
eMMC-bootmode: disabled
CPU-bootmode: disabled
HM Secure boot: enabled
MODEM TYPE : MDM9215M
Dec 28 2012, 22:18:14
Stuck in bootloop after trying to update ViperXL.
MTP driver won't load no matter what I try. ADB doesn't see my device.
Can get to recovery TWRP v2.4.1.0 Venom
But that is ALL!
No data anywhere. No ROMs, no backups. NOTHING
All I can do is go to reboot and Power Off. If I try to reboot it tells me there is no OS.
And I cannot do anything...... Flash or Sideload...... ADB doesn't see my device.
I've read and tried for hours, days, months!
Any ideas out there??
Thanks
Click to expand...
Click to collapse
Install proper android drivers and androidsdk, I'm fairly sure that the reason for you being unable to sideload is that you haven't installed the proper drivers on your PC to actually do so.
No Joy
aardappel12 said:
Install proper android drivers and androidsdk, I'm fairly sure that the reason for you being unable to sideload is that you haven't installed the proper drivers on your PC to actually do so.
Click to expand...
Click to collapse
OK, I've tried every driver I can find, if you've got options please help.
Device Manager says the drivers are all good but fails to install every time, I've used a bunch of different USB cords too!
But it fails to install the MTP device every time.
"This device cannot start. (Code 10)"
adb version is 1.0.31
adb devices shows no devices, but in the Recovery(TWRP v2.4.1.0 Venom)>Advanced>Sideload the device shows with sideload, When I try to Sideload (ROM QX Senseless v2.1, 1 of the 4 from this post http://forum.xda-developers.com/showthread.php?t=2051032) it fails at 45% every time.
If I try the push command I get the error: closed
C:\Development\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Development\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>adb devices
List of devices attached
HT2BAW302181 sideload
C:\Development\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>adb sideloa
d QXSenselessv2.0.zip
* failed to write data 'protocol fault (no status)' *
C:\Development\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>adb push QX
Senselessv2.0.zip /sdcard
error: closed
C:\Development\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>adb version
Android Debug Bridge version 1.0.31
C:\Development\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
New ideas??
Thanks
A rUU will definitely fix you but you'll loose everything...a little last resort but only if fastboot is working in hboot
Sent from my HTC One X+ using XDA Free mobile app
NooBOnTheBlock said:
A rUU will definitely fix you but you'll loose everything...a little last resort but only if fastboot is working in hboot
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
can't find the RUU for this phone. the radio is different
Solved
Thanks aardappel12
updated TWRP and the sideload worked!
Issue : Unable to do software update for android OS on my htc one.
Details:
The output in the fastboot bootloader is as follows :
moonshine S-OFF
M7-UL PVT SHIP S-OFF RH
CID-11111111
HBOOT -1.44.4444
RADIO-4A.14.3250.15
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013,20:01:28:-1
I am suspecting that bootloader is locked ? How can I confirm ?
In some mobiles I see it shows in the fastboot bootloader screen. But in mine, it doesn't.
I tried to unlock the bootloader with fastboot process. when I issue adb devices it returns the serial number.
But when i issue fastboot devices, it is not returning anything.
What I can do here ?
How can I get the software updates now ?
Please anyone can help me to get the updates.
SanthoshGunturu said:
Issue : Unable to do software update for android OS on my htc one.
Details:
The output in the fastboot bootloader is as follows :
moonshine S-OFF
M7-UL PVT SHIP S-OFF RH
CID-11111111
HBOOT -1.44.4444
RADIO-4A.14.3250.15
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013,20:01:28:-1
I am suspecting that bootloader is locked ? How can I confirm ?
In some mobiles I see it shows in the fastboot bootloader screen. But in mine, it doesn't.
I tried to unlock the bootloader with fastboot process. when I issue adb devices it returns the serial number.
But when i issue fastboot devices, it is not returning anything.
What I can do here ?
How can I get the software updates now ?
Please anyone can help me to get the updates.
Click to expand...
Click to collapse
This post explains what the OTA is looking for to have a successful update. One of the things I notice with T-Mobile OTA is they don't like SuperCID.
ADB works in the OS when USB Debugging is enabled and in Recovery. Fastboot works in bootloader/FASTBOOT USB.
There are also the last two RUUs in this General Forum. Please read through the last four or five pages of each post to see if there were any issues found.
So the story is I got this phone from a friend for free and it's not working. Next is some info I have found.
First is the forever bootscreen.
*** LOCKED ***
*** SECURITY WARNING ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011, 15:03:01
....................
Some phone info.
HTC 3D EVO FCC ID: NM8PG86300
Model: PG86300
IMEI: 35871044661787
S/N: HT1CYV211753
P/N: 99HNJ004-00
a token example from fastboot, at htcdev returns error 150 - doesn't allow me to proceed with unlock of the bootloader.
<<<< Identifier Token Start >>>>
47B3145FF96274E03070C998F66FF7BD
C7245D1F8DF602901AAD442C71F4EB5C
B9B4081EA26F6A82B3EABDC8544686F1
1AC27EA1394FF8AEDA634395FA0A8FBE
6288792606968C46841EE9B7670F20C9
5D1B1C1295D3882C81BCA01AE0E3A179
11673423F363A34C1797CDA128371DAE
9DB4C0B7500FE097C43CCBFB50377180
F56738F0C03BA925749693A2FCEF1E9A
AAAEFE9EFDD676CB56E9787B9D42F3BA
D87FBEAD3B4F8D0A283D2C2E376A1779
36C5EA4FF479C7B811BB3B273E4DEF8A
066110BCDEB9AF842DC2588DAB982383
73A0E6825419B45B5CF37CA6A011DBF0
CDCFF3D8EE40F36DE4223A70272CE7E4
4D16C6CB24E5CD3FC0D03BFDACBC7F4F
<<<<< Identifier Token End >>>>>
I hope that's enough data.
To sum up it is locked with S-ON. Selecting recovery/factory reset reboots it in 1 sec to bootloader. Phone does respond to some fastboot commands, most useful was fastboot oem rebootRUU that takes me to a black screen with an HTC logo and if I disconnect a usb cable I'm stack in bootloader like menu with the only choice 'RUU' that is not click able at all. I have tried enormous number of .img files through fastboot flash (loads, throws: remote: signature verify fail) and using an sd card(loads, verifies, goes back to main menu). I'm in process of trying out RUU exe files from website url androidruu with provider shooter (I can't post urls) First run I thought was going to be a success, it found the phone said that the current version is something like &20, started doing something - restarted the phone and phone got stuck at black screen when the program exited with code 155, while waiting for the phone to get to bootloader I assume. Please your suggestions, maybe deeper knowledge of fastboot protocols would help. Device is not showing up under adb. I was trying all of that using windowsXP/ubuntu computer. please help reinstalling, reviving, flashing this half alive HTC EVO 3D. I believe it is called roger as well. And I assume the previous owner is an idiot.
Some more to say
Ive spent 24 hours with google, HTC EVO 3D (GSM i believe), usb cable and an SD card, i'm lost and despair.
first of all make sure your bootloader is locked .you can lock it via fastboot : Type the following in the command prompt window:
fastboot devices
This is to ensure that your device is detected, if nothing appears on screen with this command, then it means you don’t have the proper drivers installed on your PC. And if that’s the case you should download and install/re-install the HTC Sync software given in Step 1.1Now type the following command to re-lock your HTC bootloader
fastboot oem lock then download and run this and follow the instructions http://www.androidruu.com/getdownlo...00U_11.25.3504.06_M_release_262714_signed.exe
Sent from my Panasonic printer Buy me a beer cause i'm alcoholic and i need more and more https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=HN6YQLDZT76EE
Hi i have a same problem,,,after install the RUU its says everithing is ok and fine your phone is now reboot,,,and after reboot it stuck at the white screen with a HTC logo,,,i dont know what can i do,,,can you help me please ? my bootloader is locked and i think i dont do anything wrong,,,,and my second problem is i cant go into recovery mod,,,if i press the power button to open the recovery mode in bootloader the phone will reboot as normall and stuck at the white screen with a HTC logo,,, :/ i looking for a soution 3 days,,, but noting happened,,, i really dont know what can i do ,,, any ideas ? plss.. :/
Informations :
Shooter_U (ics) S-on
Radio : 11.25.3504.06_m
and the Ruu what i used is ( RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed .exe)... im very depressed about it... (( please help me to get back to life my evo... :/,,and sorry for my bad english :/
first of all you cant get to recovery cauese the ruu erased your custom recovery.if the ruu was succesful and you can not boot your phone it can be a hardware damage...
edit: what is the result after running ruu? its succesful or what?
Sent from my Panasonic printer Buy me a beer cause i'm alcoholic and i need more and more https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=HN6YQLDZT76EE
yes,,,its says succesful,,,you are succesfuli installed the stock rom now your android phone will reboot and ready to use.. ,,or something like that,,,but after reboot its stuck on white screeen...
Any solution? plss help me .. :/