My dad has an HTC One Max. Got it international. Came S-off, rooted, but with bootloader locked w/o TAMPERED message. Update's not working so trying RUU. Problem is I can't get ADB to recognize. When in fastboot usb, windows shows a "Android 1.0" device under "Devices and Printers" but when I try simple "adb devices" nothing shows. Got HTC Sync so I should have the right driver shouldn't I? I've done the exact same thing with an Evo 4g LTE with no issue, but here I can't figure what I'm doing wrong.
Extra info
Just for more info, here's the "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.14.651.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA3BDSC05086
(bootloader) imei: 990004285129866
(bootloader) meid: 99000428512986
(bootloader) product: t6whl
(bootloader) platform: HBOOT-8064
(bootloader) modelid: 0P3P70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4188mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.129s
Having the same issue. Need to reflash twrp.img but can't get adb to pick up the device. Going to look more into it tomorrow. I'll let you know if I find anything or vice versa.
Edit/Update
Got mine working - for starts, try some different USB cables, especially if you're not using the stock cable.
After that, go to 'Device Manager' and you should see "Android USB Devices" and under that you should have something to the effect of "My HTC". Right click there and you should be able to update the driver.
I did both of those things and I'm up and running again.
Sent from my HTC0P3P7 using XDA-FORUM, powered by appyet.com
Related
I just ran fastboot getvar all and the mainver came up blank. All other info showed up but that one had nothing. I've done it before way back when, on my old phone running GB and it showed up.
Phone is s-on and has global leak running EclipticRez. Anyone know why this is?
Code:
c:\android-flasher>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.27.0000
(bootloader) version-baseband: 2.22.10.0801r/2.22.10.0803r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4103mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ad3368f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.502s
main version is really a thing to worry about unless you want to go backwards on ruu but if you want to write it back to 1 follow this link : http://forum.xda-developers.com/showthread.php?t=1526316
use this post http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4
Shouldn't it say something after the "(bootloader) version-main:" listing? I was just looking it up to try to help someone out and that's blank.
In my notes from the old days where I put how to look up mainver I have that mine was 2.01.605.11 (at the time) but now I have nothing there. That is the spot it's supposed to be, right?
Never dealt with main version before.
It's all on you synister.
main version is really there so that when you want to install and RUU the signature will allow it to only update and not go back. when you flash the RUU it will write to it to show you are on version X.X and not X.Y. mine on my inc 4g is blank and it doesnt hurt it one bit.
Hello,
I have an AT&T HTC One, on which I loaded Cyanogenmod's 10.2 rom. I tried to do an update to their 11.0 snapshot rom, and the system locked up during the installation. I wasn't able to recover, and now my phone is looping at boot. I can get into the bootloader screen, which shows this:
****TAMPERED****
****UNLOCKED****
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3418.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09:32:41.0
I can get Fastboot to work, but not ADB. Here's the results from my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT33PW905337
(bootloader) imei: 354439054019387
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
I have wandered all over this forum and the internet in general, downloaded multiple versions of HTC drivers, various RUU files, tried to make the S-OFF using both rumrunner and revone without any success. I've tried both USB 2.0 and USB 3.0 ports, and I've tried multiple USB cables.
When I select RECOVERY in the bootloader menu, the phone goes back to the looping on and off.
My ideal scenario would be to load the latest AT&T software load of Android 4.4.2/Sense5.5, but at this point, just getting a usable phone would be wonderful!
Does anyone have any ideas? Thank you in advance for your help!
sprezz32 said:
Hello,
I have an AT&T HTC One, on which I loaded Cyanogenmod's 10.2 rom. I tried to do an update to their 11.0 snapshot rom, and the system locked up during the installation. I wasn't able to recover, and now my phone is looping at boot. I can get into the bootloader screen, which shows this:
****TAMPERED****
****UNLOCKED****
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3418.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09:32:41.0
I can get Fastboot to work, but not ADB. Here's the results from my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT33PW905337
(bootloader) imei: 354439054019387
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
I have wandered all over this forum and the internet in general, downloaded multiple versions of HTC drivers, various RUU files, tried to make the S-OFF using both rumrunner and revone without any success. I've tried both USB 2.0 and USB 3.0 ports, and I've tried multiple USB cables.
When I select RECOVERY in the bootloader menu, the phone goes back to the looping on and off.
My ideal scenario would be to load the latest AT&T software load of Android 4.4.2/Sense5.5, but at this point, just getting a usable phone would be wonderful!
Does anyone have any ideas? Thank you in advance for your help!
Click to expand...
Click to collapse
How about this
http://forum.xda-developers.com/showthread.php?t=2676986
sprezz32 said:
Hello,
I have an AT&T HTC One, on which I loaded Cyanogenmod's 10.2 rom. I tried to do an update to their 11.0 snapshot rom, and the system locked up during the installation. I wasn't able to recover, and now my phone is looping at boot. I can get into the bootloader screen, which shows this:
****TAMPERED****
****UNLOCKED****
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3418.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09:32:41.0
I can get Fastboot to work, but not ADB. Here's the results from my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT33PW905337
(bootloader) imei: 354439054019387
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
I have wandered all over this forum and the internet in general, downloaded multiple versions of HTC drivers, various RUU files, tried to make the S-OFF using both rumrunner and revone without any success. I've tried both USB 2.0 and USB 3.0 ports, and I've tried multiple USB cables.
When I select RECOVERY in the bootloader menu, the phone goes back to the looping on and off.
My ideal scenario would be to load the latest AT&T software load of Android 4.4.2/Sense5.5, but at this point, just getting a usable phone would be wonderful!
Does anyone have any ideas? Thank you in advance for your help!
Click to expand...
Click to collapse
your going to reflash recovery then a rom
download twrp 2.6.3.3 here > http://techerrata.com/browse/twrp2/m7
then flash it in fastboot
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then download the rom post below and sideload it to your phone
boot to recovery then
TWRP / Advanced / Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
mb_guy said:
How about this
http://forum.xda-developers.com/showthread.php?t=2676986
Click to expand...
Click to collapse
He can't get into recovery
Thank you!
Thank you for your help! Your instructions worked perfectly. As a side note, I noticed that I could use adb when the TWRP recovery image was loaded, but not when I was just in the bootloader screen. Anyway, thank you again for the help!
Hi guys, I have a big problem, my phone will not boot into android, endlessly restarts at the first splash screen.
but I can go into bootloader.
Can I restore the phone through fastboot? that this requires?
I can not find RUU for Hboot1.56.0000 to try to flash through fastboot.
cant downgrade Hboot, because S-ON
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37HW914082
(bootloader) imei: 354439056063896
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I hope for your help and sorry for my english ...
igorya79 said:
Hi guys, I have a big problem, my phone will not boot into android, endlessly restarts at the first splash screen.
but I can go into bootloader.
Can I restore the phone through fastboot? that this requires?
I can not find RUU for Hboot1.56.0000 to try to flash through fastboot.
cant downgrade Hboot, because S-ON
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37HW914082
(bootloader) imei: 354439056063896
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I hope for your help and sorry for my english ...
Click to expand...
Click to collapse
is the phone unlocked with custom recovery or stock ?
clsA said:
is the phone unlocked with custom recovery or stock ?
Click to expand...
Click to collapse
absolutely stock
igorya79 said:
absolutely stock
Click to expand...
Click to collapse
Here is a RUU 4.18.502.7, your bootloader must be locked to run this. All you have to do is download this to your computer and with the phone on connect it to the computer. Double click the file and follow the instructions on the screen.
majmoz said:
Here is a RUU 4.18.502.7, your bootloader must be locked to run this. All you have to do is download this to your computer and with the phone on connect it to the computer. Double click the file and follow the instructions on the screen.
Click to expand...
Click to collapse
If that RUU gives you problems try flashing just the firmware first. It's here >https://www.androidfilehost.com/?fid=23329332407580581
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
thanks for the help, the process of the firmware was successful!
but unfortunately the problem is not solved.
I recently dropped in the water this phone (but after drying the phone even a week worked without problems).
probably in the phone spoiled, not part of the software ...
but if there is any way to revive a phone - please let us know ...
HTC Proto / DESIRE X
Playing with custom ROM and everything connected to it I've managed to erase Serial No and model Id No.
here is the getvar all:
D:\'ndroid\onxr>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.25.0002
(bootloader) version-baseband: 1.15.40.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: u¥næg"öa6ü↨¡õ¥↨
(bootloader) imei: 355803051093548
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: ┤ò£e㸪ñ(Éè¨─Q¤~*¼╩Q§¼=Ò±/ `oj\±
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2b02a5bf
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
Even worse, my bootloader is Relocked and I can not use adb since even with correct drivers. So I'm left with Fastboot only.
It will not apply RUU since it can not pass serial and model check...and now I have a bricked phone.
Is there anyone here who might have idea on how to pull out of this?
HTC Desire X
Nobody? really?
ivar_sa said:
HTC Proto / DESIRE X
Playing with custom ROM and everything connected to it I've managed to erase Serial No and model Id No.
here is the getvar all:
D:\'ndroid\onxr>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.25.0002
(bootloader) version-baseband: 1.15.40.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: u¥næg"öa6ü↨¡õ¥↨
(bootloader) imei: 355803051093548
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: ┤ò£e㸪ñ(Éè¨─Q¤~*¼╩Q§¼=Ò±/ `oj\±
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2b02a5bf
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
Even worse, my bootloader is Relocked and I can not use adb since even with correct drivers. So I'm left with Fastboot only.
It will not apply RUU since it can not pass serial and model check...and now I have a bricked phone.
Is there anyone here who might have idea on how to pull out of this?
Click to expand...
Click to collapse
ivar_sa said:
Nobody? really?
Click to expand...
Click to collapse
Your phone is S-OFF. You probably deleted/formated/flashed certain partitions on your phone that are only accesable when you are S-OFF.
This means, most probably and unfortunatelly, that you have to replace the phone's mainboard.
So, no chance to use some RUU to patch this up?
dodialfaed said:
Your phone is S-OFF. You probably deleted/formated/flashed certain partitions on your phone that are only accesable when you are S-OFF.
This means, most probably and unfortunatelly, that you have to replace the phone's mainboard.
Click to expand...
Click to collapse
ivar_sa said:
So, no chance to use some RUU to patch this up?
Click to expand...
Click to collapse
As far as I know there are no jb hboot RUU's. Only for ICS hboot.
And I am sure you can't downgrade your hboot to ICS because of the corrupted data regarding serial number.
I tried changing my HTC One M8_WHL PVT SHIP S-OFF into developer edition using the guide on http://htc-one.wonderhowto.com/how-...edition-for-super-fast-sense-updates-0156524/ . I successfully changed the MID and the CID without breaking a sweat. After, I used TWRP to restore the backup which the guide instructed me to download and restore. After restoring that backup, device could only boot HBOOT. Now I tried running the RUU.exe for Developer Edition and I get the error which asks that I run the correct RUU for the device. Now, the device doesn't boot pass HBOOT
What I can do ...
1. Boot into TWRP recovery
2. Give fastboot commands with HBOOT
3. Boot into RUU via fastboot
What I can't do ...
1. Boot the device
2. Revert the MID change to its original state cos I will need to run ADB Shell to do that, which cannot be done from HBOOT
3. No RUU.exe is responding to flashing the device
The specific help I need ...
1. Be able to Change MID using Fastboot so I can run a SPRINT RUU
fastboot getvar all results ...
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43BSF02932
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499006400
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US002
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
PLEASE HELP!