Related
can my htc one t-mobile uk...be saved,,,its stuck in boot loop ..i cant boot to recovery....tryed hanson tool....htc rom upgrade dont work....iv beem playin about with it for a week.....need desperate help//////////
its not mounting system sd cashe....iv tryed following tutorals on this site but no luck....relocked..tampered...security warning
i take it the fones usless then????????????
No recovery or anything ? U could flash a new ruu thru fastboot or bootloader
Sent from my HTC One using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=2358781
this will convert your phone to a google play edition you can keep it like this if you like but if you want to get back to stock Download THIS it will downgrade the bootloader. (doing the GPE conversion upgrades the bootloader....)
To downgrade the bootloader....:
navigate to you android sdk folder. open the platform-tools folder create a new folder inside it name it
Code:
HBOOT-DG
. inside that folder extract the zip you downloaded. open the android-info.txt and replace its contents with this.
Code:
modelid: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
modelid: PN071****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
mainver: 1.29.401.12
btype:1
aareport:1
hbootpreupdate:3
save the file highlight both android-info and hboot_signedbyaa right click on either item and add to a zip archive "i recommend using z-zip"
name the zip
Code:
hbootdg
move the newly created zip into your platform tools folder and navigate back to your android sdk directory.
Code:
click Once on the platform-tools folder then hold shift and right click the platform tools folder and click open command window here.
make sure your phone is plugged in to you computer and type
Code:
adb reboot-bootloader
then after you phone boots in to a BLACK screen "GPE hboot is black standard hboot is white" make sure it says fastboot usb then type this command.
Code:
fastboot oem rebootRUU
wait for your phone to reboot into a screen that says htc make sure Your battery is charged. "dont want it powering off on you in the middle of a vital update"
type this command.
Code:
fastboot flash zip hbootdg.zip
if your device dosnt automaticly reboot just type
Code:
fastboot reboot
after your hboot is downgraded you can now flash the rom of your choice or go back to stock if you so please.
Troubleshooting:
if you get a bad CID error.
type
Code:
fastboot reboot-bootloader
then type
Code:
fastboot getvar all
look for the line that says cidnum: save the value that is there.
then type
Code:
fasboot oem writecid 11111111
then re run the flash zip command. Important. if going back to stock make sure you change your cidnum back to what it originaly was.
if you need further clairfication just ask.
Hi, I just recently relocked my bootloader in order to get some warranty stuff cleared out (I thought I did), but it turns out bootloader didn't have to be relocked. So, I'm trying to unlock it again, but nothing's working. The screen asking me about unlocking bootloader doesn't even show up, and it's not responding to any fastboot commands. Can you please help me??
HTC One GPE Converted from HTC One AT&T Using RUU
cid: GOOGL001
Version 4.4.1 (or 4.4.2, which ever one is the latest)
When I type "fastboot oem unlock", this shows up
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.567s]
finished. total time: 0.572s
Please help me!! I have no idea what is going on!! Thanks.
Do you have a custom recovery? If so restore a backup and see if that works.
Are you still s-off? If so, you can use revone to run some commands that will unlock your bootloader.
revone can be found here
If you have S-off the steps will be
1. Download revone (above) and push it to your device: adb push revone /data/local/tmp/
2. Open an adb shell and:
* cd /data/local/tmp
* chmod 755 revone
3. Have revone unlock by running the command: ./revone -u
(Yes, the period before the slash is necessary)
This is an easy-to-follow and complete guide on how to achieve S-OFF on HTC Desire V (T328w, Wind) using the Rumrunner tool (primary for HTC One, adapted for us)
Rumrunner copyright notice: As per the license terms on the official Rumrunner site: http://rumrunner.us/ mirror links of Rumrunner software are not allowed. Using Rumrunner packages hosted on other sites or from other members is risky/outdated and official support is not applicable if you cannot S-OFF or end up bricking your device. You should always download the latest Rumrunner version from the official site: http://rumrunner.us/downloads-2/
Step-by-step procedure before attempting to S-OFF (with non-universal builds of Rumrunner):
1. Your HTC Desire V must be unlocked & rooted.
If it's not rooted, the bootloader must first be unlocked. Follow the instructions in the "Unlocking bootloader" section in this guide:http://forum.xda-developers.com/showthread.php?t=2265618.
2. Go to Settings > Developer options > check USB debugging. (If you cannot see Developer options, go to Settings > About > Software information > More > tap on Build number 7 times until you get a pop-up message saying: You are now a developer!)
3. Go to Settings > Power > uncheck Fast boot.
4. Uninstall HTC Sync if you have it, as well as all other phone software (Samsung Kies, PDANet, etc.)
5. Disable all your internet security software (antivirus, antispyware such as Windows Defender, etc) and disable firewall (you need unrestricted internet access otherwise Rumrunner will fail).
6. Disable Screen lock security on your HTC Desire V. (Go to Settings > Security > Screen lock > select None) (no passcode lock/no pattern lock/no face lock)
7. A working internet connection on the device.
8. Required a stock ROM but also been successfully tested on Baidu 5.1 & Baidu ROM43
9. Install HTC drivers: here
Hint: If you previously had HTC Sync installed, you should have the drivers already. You can uninstall HTC Sync separately, without removing the drivers.
If you got an error during installing the driver in mode android 1.0, try alternative PDANet drivers
10. You need adb and fastboot: here/mirror
11. Use your HTC USB cable to connect the device to a USB 2.0 port on your PC. (Do not connect through USB hubs or USB 3.0 ports)
12. Connect to FASTBOOT USB mode and test if your phone is accessible via adb fastboot. (Hold the power button down until the phone powers off. Press Volume Down and Power buttons to start the device into Bootloader mode. Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button. Connect the device via the original HTC USB cable to a USB 2.0 port in your PC . Now, click on Start > Run > Type "CMD". This will open the DOS Command Prompt window. Navigate through DOS to your adb folder. Mine is located at C:/ Android so i type in the following order:
Code:
CD C:\Android
fastboot devices
This will display your HTC Desire V 's serial number, indicating that you have successfully established USB connection. Here's my log from the Command Prompt window:
Code:
C:\Documents and Settings\Administrator> CD C:\Android
C:\>cd Android
C:\ Android >fastboot devices
HT273P****** fastboot
If you see nothing after entering the fastboot devices command, then there is a problem with the USB connection - you may have a faulty USB cable and/or you need to install the correct HTC USB drivers depending on your OS).
13. Charge your HTC Desire V to 100%. Some users have reported that if the battery level is below 50%, the S-OFF procedure will sometimes fail.
14. Download the rumrunner_proto_0.7.1 version of Rumrunner according to your OS: http://rumrunner.us/downloads-2/.
Hint: Yes, it`s for HTC Desire X, but method is the same.
15.Connect your HTC Desire V using the HTC USB cable via a USB 2.0 port and boot up the phone. Leave it on its homescreen. Close any open Command Prompt windows. Unzip the Rumrunner file on your hard drive C:\. Make sure that you have administrator rights on the computer. Double-click on soju.exe to start the S-OFF operation (or right-click on soju.exe to run as Administrator).
15.a) Agree to the terms and conditions you are prompted with in soju (Yes)
15.b) Allow the exploit to do its work (Yes).
Your device will reboot 4-6 times throughout the process.
Do not touch device! Wait until the console appears "Press ENTER to exit". Disconnect your HTC Desire V
15.c) Reboot device in the bootloader & check S-OFF
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is my complete log from successful Rumrunner S-OFF execution:
==================== rumrunner S-OFF 0.7.1 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (14/120)
Waiting
Test 2: Booting device
Waiting for ADB (21/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (14/120)
Waiting for ADB (20/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
heh, just a shot glass for this one....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
heh, just a shot glass for this one....
pouring (1).................................
heh, just a shot glass for this one....
pouring (2)........................
heh, just a shot glass for this one....
pouring (3).................
Waiting for ADB (24/120)
must ferment longer...
what's that in the bottle still? rum foul, sloppy, real sloppy...
heh, just a shot glass for this one....
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
Press ENTER to exit
Click to expand...
Click to collapse
Attention : USING S-OFF METHOD YOU WILL GET VIBRATIONS ON BOOT !
HTC Desire V (as well as HTC Desire X) has a known bug where it will vibrate multiple times (7) on EVERY boot after using rumrunner. This is NOT reversible. You’ve been warned!!!
New possibilities with S-OFF
New possibilities with S-OFF
Means, you already know how to use adb commands, you have installed necessary drivers and S-OFF / unlock bootloader
1. Get SuperCID 11111111 via adb (this will remove the region lock on your phone)
Code:
CD C:\Android
C:\Android>adb reboot bootloader
C:\Android>fastboot oem writecid 11111111
2. Firmware upgrade to the latest available for optimal performance (Firmware.zip, Hboot, radio)
HTC_Europe_Hboot_1.30.0008_Radio_1.10.34D.17_20.26.30.27U_Stock_Boot&Recovery
HTC_Asia_WWE_Hboot_1.14.0001_Radio_1.10.34D.17_20.26.30.27U_Stock_Boot&Recovery
3. Remove red warning text in your bootloader.
Stock Hboot 1.30.0008 signed
Hboot 1.30.0008 Removed red warning text
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hboot.zip
fastboot reboot
4. Adb shell commands to change the status of the Bootloader Locked/Unlocked/Relocked (information provided by Softor, confirmed by ckpv5 here & here)
4a. So, for Locked status, connect you (S-OFF) Desire V (turned on normal mode) to BB via 2.0 USB and type in the open DOS Command Prompt window following command:
Code:
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=32256
exit
exit
adb reboot bootloader
or
Code:
adb wait-for-device shell su -c "echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=32256"
4b. To change the Bootloader status to Unlocked (without htcdev.com service)
Code:
adb shell
su
echo -ne '\x15\x08\x84\x19' | dd of=/dev/block/mmcblk0p7 bs=1 seek=32256
exit
exit
adb reboot bootloader
or
Code:
adb wait-for-device shell su -c "echo -ne '\x15\x08\x84\x19' | dd of=/dev/block/mmcblk0p7 bs=1 seek=32256"
4c. And for Relocked status:
Code:
adb shell
su
echo -ne '\x15\x08\x85\x19' | dd of=/dev/block/mmcblk0p7 bs=1 seek=32256
exit
exit
adb reboot bootloader
or
Code:
adb wait-for-device shell su -c "echo -ne '\x15\x08\x85\x19' | dd of=/dev/block/mmcblk0p7 bs=1 seek=32256"
Here is my complete log from successful upgrade Hboot with removed red warning text & getting SuperCID:
CD C:\Android
C:\Android>adb reboot bootloader
C:\Android>fastboot getvar version-bootloader
version-bootloader: 1.14.0001
finished. total time: 0.003s
C:\Android>fastboot oem rebootRUU
...
OKAY [ 0.171s]
finished. total time: 0.172s
C:\Android>fastboot flash zip hboot.zip
sending 'zip' (363 KB)...
OKAY [ 0.224s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
OKAY [ 3.917s]
finished. total time: 4.144s
C:\Android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.167s]
finished. total time: 0.167s
C:\Android>fastboot getvar version-bootloader
version-bootloader: 1.30.0008
finished. total time: 0.003s
C:\Android>fastboot oem writecid 11111111
...
(bootloader) →╜tjHTCE
(bootloader) Done!
(bootloader) HWIO_SDC1_MD_REG_ADDR=0xA86000A0
(bootloader) HWIO_SDC1_NS_REG_ADDR=0xA86000A4
(bootloader) HWIO_SDC3_MD_REG_ADDR=0xA86000B0
(bootloader) HWIO_SDC3_NS_REG_ADDR=0xA86000B4
(bootloader) phys_to_virt(HWIO_SDC1_MD_REG_ADDR)=0xB32000A0
(bootloader) phys_to_virt(HWIO_SDC1_NS_REG_ADDR)=0xB32000A4
(bootloader) phys_to_virt(HWIO_SDC3_MD_REG_ADDR)=0xB32000B0
(bootloader) phys_to_virt(HWIO_SDC3_NS_REG_ADDR)=0xB32000B4
(bootloader) sdc_ns_reg value=0xFF9E0B58
(bootloader) HWIO_SDC1_MD_REG_ADDR=0xA86000A0
(bootloader) HWIO_SDC1_NS_REG_ADDR=0xA86000A4
(bootloader) HWIO_SDC3_MD_REG_ADDR=0xA86000B0
(bootloader) HWIO_SDC3_NS_REG_ADDR=0xA86000B4
(bootloader) phys_to_virt(HWIO_SDC1_MD_REG_ADDR)=0xB32000A0
(bootloader) phys_to_virt(HWIO_SDC1_NS_REG_ADDR)=0xB32000A4
(bootloader) phys_to_virt(HWIO_SDC3_MD_REG_ADDR)=0xB32000B0
(bootloader) phys_to_virt(HWIO_SDC3_NS_REG_ADDR)=0xB32000B4
(bootloader) sdc_ns_reg value=0xFF9E0B58
(bootloader) sdcc_init_memory_device done
(bootloader) HWIO_SDC1_MD_REG_ADDR=0xA86000A0
(bootloader) HWIO_SDC1_NS_REG_ADDR=0xA86000A4
(bootloader) HWIO_SDC3_MD_REG_ADDR=0xA86000B0
(bootloader) HWIO_SDC3_NS_REG_ADDR=0xA86000B4
(bootloader) phys_to_virt(HWIO_SDC1_MD_REG_ADDR)=0xB32000A0
(bootloader) phys_to_virt(HWIO_SDC1_NS_REG_ADDR)=0xB32000A4
(bootloader) phys_to_virt(HWIO_SDC3_MD_REG_ADDR)=0xB32000B0
(bootloader) phys_to_virt(HWIO_SDC3_NS_REG_ADDR)=0xB32000B4
(bootloader) sdc_ns_reg value=0xFE2B0B5A
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) buf_addr:1FC300,buf_size:200,start_sector:1739D
(bootloader) HWIO_SDC1_MD_REG_ADDR=0xA86000A0
(bootloader) HWIO_SDC1_NS_REG_ADDR=0xA86000A4
(bootloader) HWIO_SDC3_MD_REG_ADDR=0xA86000B0
(bootloader) HWIO_SDC3_NS_REG_ADDR=0xA86000B4
(bootloader) phys_to_virt(HWIO_SDC1_MD_REG_ADDR)=0xB32000A0
(bootloader) phys_to_virt(HWIO_SDC1_NS_REG_ADDR)=0xB32000A4
(bootloader) phys_to_virt(HWIO_SDC3_MD_REG_ADDR)=0xB32000B0
(bootloader) phys_to_virt(HWIO_SDC3_NS_REG_ADDR)=0xB32000B4
(bootloader) HWIO_SDC1_MD_REG_ADDR=0xA86000A0
(bootloader) HWIO_SDC1_NS_REG_ADDR=0xA86000A4
(bootloader) HWIO_SDC3_MD_REG_ADDR=0xA86000B0
(bootloader) HWIO_SDC3_NS_REG_ADDR=0xA86000B4
(bootloader) phys_to_virt(HWIO_SDC1_MD_REG_ADDR)=0xB32000A0
(bootloader) phys_to_virt(HWIO_SDC1_NS_REG_ADDR)=0xB32000A4
(bootloader) phys_to_virt(HWIO_SDC3_MD_REG_ADDR)=0xB32000B0
(bootloader) phys_to_virt(HWIO_SDC3_NS_REG_ADDR)=0xB32000B4
(bootloader) sdcc_init_memory_device done
(bootloader) HWIO_SDC1_MD_REG_ADDR=0xA86000A0
(bootloader) HWIO_SDC1_NS_REG_ADDR=0xA86000A4
(bootloader) HWIO_SDC3_MD_REG_ADDR=0xA86000B0
(bootloader) HWIO_SDC3_NS_REG_ADDR=0xA86000B4
(bootloader) phys_to_virt(HWIO_SDC1_MD_REG_ADDR)=0xB32000A0
(bootloader) phys_to_virt(HWIO_SDC1_NS_REG_ADDR)=0xB32000A4
(bootloader) phys_to_virt(HWIO_SDC3_MD_REG_ADDR)=0xB32000B0
(bootloader) phys_to_virt(HWIO_SDC3_NS_REG_ADDR)=0xB32000B4
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 22.104s]
finished. total time: 22.105s
Click to expand...
Click to collapse
My complete log from Locked Bootloader command and results photo:
C:\Users\User>CD C:\Android
C:\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=32256
dd of=/dev/block/mmcblk0p7 bs=1 seek=32256 <
4+0 records in
4+0 records out
4 bytes transferred in 0.009 secs (444 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Android>adb reboot bootloader
C:\Android>
Click to expand...
Click to collapse
My complete log from Unlocked Bootloader command and results photo:
C:\Users\User>CD C:\Android
C:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne '\x15\x08\x84\x19' | dd of=/dev/block/mmcblk0p7 bs=1 seek=32256
dd of=/dev/block/mmcblk0p7 bs=1 seek=32256 <
4+0 records in
4+0 records out
4 bytes transferred in 0.008 secs (500 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Android>adb reboot bootloader
C:\Android>
Click to expand...
Click to collapse
A tried all ways but in vein
this is my log
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>CD C:|Android
'Android' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>CD C:\Android
C:\Android>fastboot oem rebootRUU
...
OKAY [ 0.190s]
finished. total time: 0.190s
C:\Android>fastboot flash zip hboot_mod.zip
sending 'zip' (363 KB)...
OKAY [ 0.230s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.820s
C:\Android>fastboot flash zip hboot.zip
sending 'zip' (363 KB)...
OKAY [ 0.220s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.710s
C:\Android>
any solution?
almozaffar said:
A tried all ways but in vein
this is my log
C:\Android>fastboot flash zip hboot_mod.zip
sending 'zip' (363 KB)...
OKAY [ 0.230s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.820s
C:\Android>fastboot flash zip hboot.zip
sending 'zip' (363 KB)...
OKAY [ 0.220s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.710s
C:\Android>
any solution?
Click to expand...
Click to collapse
What is your CID & mainver?
can't write CID
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\LGNB>CD C:\Android
C:\Android>fastboot oem writecid 11111111
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Android>fastboot oem writecid 11111111
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Android>fastboot oem writecid 1111111
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Android>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Android>fastboot oem writecid 11111111
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Android>fastboot oem writecid 11111111
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Android>
Main Version is Baidu 44
HBOOT 1.14.0001
RADIO 1.10.34D.17
eMMC-hboot
PRIMODS PVT SHIP S-ON RL
Apr 30 2012 2:15
It's no solution to get supercid or flash hboot till you have S-ON.
Response by rummer
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exit
almozaffar said:
..........
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exit
Click to expand...
Click to collapse
Don't you see anything abnormal in the log?
Read manual carefully, check USB debugging, USB cable and USB ports on BB & device (don't use USB 3.0 ports or hubs). It's no correct Desire V's adb drivers for windows 8.1, so do it on older versions (better win 7).
mr.wasssup said:
Don't you see anything abnormal in the log?
Read manual carefully, check USB debugging, USB cable and USB ports on BB & device (don't use USB 3.0 ports or hubs). It's no correct Desire V's adb drivers for windows 8.1, so do it on older versions (better win 7).
Click to expand...
Click to collapse
Thanks for your help, but
1-I am using Windows 7 Ultimate
2-debugging is on
3-my Laptop doesn't have USB 3, its USB
4- HTC drivers are up to date
5-ScreenLock is off
6-adb are from this post
I think the problem is in my gadget, it refuses to writecid or to flash, why?
---------- Post added at 01:38 AM ---------- Previous post was at 01:32 AM ----------
mr.wasssup said:
It's no solution to get supercid or flash hboot till you have S-ON.
Click to expand...
Click to collapse
Mine is still S-ON
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\LGNB>CD C:\Android
C:\Android>fastboot devices
HT2Axxxxxxxx fastboot
Fastboot can detect my Desire V
finally I got it working but failed to doenload
==================== rumrunner S-OFF 0.7.1 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (12/120)
Waiting
Test 2: Booting device
Waiting for ADB (21/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please.............................................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (12/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
almozaffar said:
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
Click to expand...
Click to collapse
Steps 5 and 7 of manual.
I removed all kinna antivirus, stopped all services, windows defender and firewall, but no luck
Any advice?
Hello! Just now add in New possibilities with S-OFF section "Commands to change the Bootloader status"
almozaffar said:
I removed all kinna antivirus, stopped all services, windows defender and firewall, but no luck
Any advice?
Click to expand...
Click to collapse
If you are sure about сorrectly installed drivers, qualitative of USB connection and all the other additional requirements are met, try rumrunner 0.7.1 with same other firmware version.
What if you go back to S-ON? Phone still vibrating on startup?
janda said:
What if you go back to S-ON? Phone still vibrating on startup?
Click to expand...
Click to collapse
Yes.
S-OFF completed and CID changed. :laugh: Here are my summary.
1. Running hTC_Asia_TW_1.59.709.3 System & Recovery on CID-HTCCN703
2. Unlocked Bootloader / flashed Custom Recovery 5.5.0.4 / rooted
3. Run rumrunner_proto_0.7.1 failed with message
hmm, cap is on tighter than I expected........
heh, just a shot glass for this one....
pouring (1)........................
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
4. Flash Baidu ROM v5.1 for HTC T328w
5. Run rumrunner_proto_0.7.1 again successfully
6. Change CID from HTCCN703 to 11111111
7. Copy official Desire V Taiwan ROM to MicroSD Card.
Rename "PL11IMG_PRIMO_DS_ICS_40A_hTC_Asia_TW_1.59.709.3_Radio_1.05.34D.29_20.21.30.23U_release_264969_signed.zip" to "PL11IMG.zip"
Reboot to HBOOT mode with VOL Down & Power Button
Follow instruction & flash the official rom
8. Relock bootloader successfully
9. Perform OTA update from 1.59.709.3 > 1.73.709.4 > 1.74.709.6
hellolalalam,
Did you relock bootloader with supersid (11111) ?
mr.wasssup said:
hellolalalam,
Did you relock bootloader with supersid (11111) ?
Click to expand...
Click to collapse
Yes. I relocked the bootloader for applying OTA as my aim is running latest Taiwan stock ROM only.
Attached the latest boot screen.
mr.wasssup said:
Attention : USING S-OFF METHOD YOU WILL GET VIBRATIONS ON BOOT !
HTC Desire V (as well as HTC Desire X) has a known bug where it will vibrate multiple times (7) on EVERY boot after using rumrunner. This is NOT reversible. You’ve been warned!!!
Click to expand...
Click to collapse
what do you mean by this notice?
the phone may hard brick? wont boot? or its just that it vibrate but behave normally?
hellolalalam said:
S-OFF completed and CID changed. :laugh: Here are my summary.
1. Running hTC_Asia_TW_1.59.709.3 System & Recovery on CID-HTCCN703
2. Unlocked Bootloader / flashed Custom Recovery 5.5.0.4 / rooted
3. Run rumrunner_proto_0.7.1 failed with message
hmm, cap is on tighter than I expected........
heh, just a shot glass for this one....
pouring (1)........................
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
4. Flash Baidu ROM v5.1 for HTC T328w
5. Run rumrunner_proto_0.7.1 again successfully
6. Change CID from HTCCN703 to 11111111
7. Copy official Desire V Taiwan ROM to MicroSD Card.
Rename "PL11IMG_PRIMO_DS_ICS_40A_hTC_Asia_TW_1.59.709.3_Radio_1.05.34D.29_20.21.30.23U_release_264969_signed.zip" to "PL11IMG.zip"
Reboot to HBOOT mode with VOL Down & Power Button
Follow instruction & flash the official rom
8. Relock bootloader successfully
9. Perform OTA update from 1.59.709.3 > 1.73.709.4 > 1.74.709.6
Click to expand...
Click to collapse
last night i tried rumrunner 2 times on stock rom & it failed like yours both the time.
today morning i flashed stock rom,boot & recovery (Clean Install)
LOL WHEN I WENT TO BOOTLOADER TO FLASH RECOVERY I SAW S-OFF AND I DIDN'T TRIED RUMRUNNER STILL, HOW?
LONG STORY SHORT - I GOT S-OFF EVEN AFTER RUMRUNNER FAILED!!!:silly:
EDIT:
I forgot to root the phone & relocked BL now i want root on Stock ROM how can reunlock it & than lock it again?
I have AT& T HTC One M7 (unlocked is displayed in HBOOT). It had crashed once before but I was able to get it back up and running using this thread: http://forum.xda-developers.com/htc-one/help/bricked-htc-one-m7-attempting-to-t2856447
But now it has crashed/bricked again and even after following the same steps, I am unable to get it up and running. Two new things I see is even if I select install recovery during installation, it goes back to twrp and looks like twrp is never able to install root access on this device. Specifics of my device are below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 4130mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any thoughts what could be wrong. I even tried wiping out cache, delvik cache, data, system from twrp but no luck. Also, I have copy of HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip but not sure how I can restore this and if it will help.
cagashe said:
I have AT& T HTC One M7 (unlocked is displayed in HBOOT). It had crashed once before but I was able to get it back up and running using this thread: http://forum.xda-developers.com/htc-one/help/bricked-htc-one-m7-attempting-to-t2856447
But now it has crashed/bricked again and even after following the same steps, I am unable to get it up and running. Two new things I see is even if I select install recovery during installation, it goes back to twrp and looks like twrp is never able to install root access on this device. Specifics of my device are below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 4130mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any thoughts what could be wrong. I even tried wiping out cache, delvik cache, data, system from twrp but no luck. Also, I have copy of HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip but not sure how I can restore this and if it will help.
Click to expand...
Click to collapse
Download the stock 5.12.502.2 recovery and place in your adb/fastboot folder.
Boot into bootloader/FASTBOOT USB:
Code:
fastboot flash recovery 5.12.502.2.recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot into Recovery and perform a factory reset
Reboot back to bootloader
Flash TWRP 2.6.3.3
I would stick with the Guru Reset it can be done in TWRP. If the stock Recovery does not do the trick, then you could try the stock firmware. You will have to relock your bootloader before you can flash it.
Well.. I am clueless now
majmoz said:
Download the stock 5.12.502.2 recovery and place in your adb/fastboot folder.
Boot into bootloader/FASTBOOT USB:
Code:
fastboot flash recovery 5.12.502.2.recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot into Recovery and perform a factory reset
Reboot back to bootloader
Flash TWRP 2.6.3.3
I would stick with the Guru Reset it can be done in TWRP. If the stock Recovery does not do the trick, then you could try the stock firmware. You will have to relock your bootloader before you can flash it.
Click to expand...
Click to collapse
Well.. I am clueless now... I tried all the above steps you provided and and used Guru Reset along with firmware. Also, I tried ViperOne 6.2 with no luck.
To be precise the issue now I am running into is no matter what I tried all installations show up as successful but then on reboot phone gets in bootloop (it comes up fine until HTC beatsaudio screen and reboots again). Any thoughts/ideas?
cagashe said:
Well.. I am clueless now... I tried all the above steps you provided and and used Guru Reset along with firmware. Also, I tried ViperOne 6.2 with no luck.
To be precise the issue now I am running into is no matter what I tried all installations show up as successful but then on reboot phone gets in bootloop (it comes up fine until HTC beatsaudio screen and reboots again). Any thoughts/ideas?
Click to expand...
Click to collapse
After you ran the stock firmware or Guru Reset did you try to boot into system? If you didn't then you need to see if that fixed your issue. It might be ViperOne causing the issue with a bad boot.img. You can check the firmware to see if it has a boot.img in the zip. Just open the zip and look to see if there is a boot.img.
majmoz said:
After you ran the stock firmware or Guru Reset did you try to boot into system? If you didn't then you need to see if that fixed your issue. It might be ViperOne causing the issue with a bad boot.img. You can check the firmware to see if it has a boot.img in the zip. Just open the zip and look to see if there is a boot.img.
Click to expand...
Click to collapse
Yes.. I do see the boot. img in the Guru Reset; however, for some reason I am unable to open the firmware zip. I guess I am going to try flashing guru reset without firmware. Another question I had was about "You will have to relock your bootloader before you can flash it." I am trying to flash it leaving bootloader unlocked. Could that be the problem. If yes, can you please please give me the exact sequence I need to follow before flash and after copying Guru Reset to device. (I am using adb push for the same).
cagashe said:
Yes.. I do see the boot. img in the Guru Reset; however, for some reason I am unable to open the firmware zip. I guess I am going to try flashing guru reset without firmware. Another question I had was about "You will have to relock your bootloader before you can flash it." I am trying to flash it leaving bootloader unlocked. Could that be the problem. If yes, can you please please give me the exact sequence I need to follow before flash and after copying Guru Reset to device. (I am using adb push for the same).
Click to expand...
Click to collapse
If you are flashing the firmware, then you have to lock your bootloader since you are S-ON. Here is how you would flash the firmware.
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
fastboot oem lock
Then, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
You will have to unlock your bootloader before you push Guru Reset to your phone. If you have your old Unlock_code.bin you might try it first, if it fails use the whole procedure:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Still no luck
majmoz said:
If you are flashing the firmware, then you have to lock your bootloader since you are S-ON. Here is how you would flash the firmware.
You will have to unlock your bootloader before you push Guru Reset to your phone. If you have your old Unlock_code.bin you might try it first, if it fails use the whole procedure:
Click to expand...
Click to collapse
I tried all the steps and see a little progress.. now my phone keeps rebooting on HTC beatsaudio screen. The sequence I followed was as below:
1. Unlocked the device with unlock bin from HTCdev and rebooted in bootloader (Shows as unlocked and tampered).
2. Pushed TWRP and Guru_Reset_M7_5.12.502.2_clsA
3. Installed Guru_Reset_M7_5.12.502.2_clsA using install from TWRP.
4. Checked if the phone is up and running on reboot --> No luck (rebooting on HTC beatsaudio screen)
5. Rebooted phone again in bootloader.
6. Locked the device (fastboot oem lock) . At this step got an error on last line "too many links"
7. fastboot oem rebootRUU (got the silver screen)
8. fastboot flash zip firmware.zip (twice) waited for about a minute after getting confirmation in command prompt.
9. fastboot reboot
I believe I am not doing anything wrong. It is really frustrating now since everyone is sending me birthday wishes today on phone and I am unable to see any :crying:
cagashe said:
I tried all the steps and see a little progress.. now my phone keeps rebooting on HTC beatsaudio screen. The sequence I followed was as below:
1. Unlocked the device with unlock bin from HTCdev and rebooted in bootloader (Shows as unlocked and tampered).
2. Pushed TWRP and Guru_Reset_M7_5.12.502.2_clsA
3. Installed Guru_Reset_M7_5.12.502.2_clsA using install from TWRP.
4. Checked if the phone is up and running on reboot --> No luck (rebooting on HTC beatsaudio screen)
5. Rebooted phone again in bootloader.
6. Locked the device (fastboot oem lock) . At this step got an error on last line "too many links"
7. fastboot oem rebootRUU (got the silver screen)
8. fastboot flash zip firmware.zip (twice) waited for about a minute after getting confirmation in command prompt.
9. fastboot reboot
I believe I am not doing anything wrong. It is really frustrating now since everyone is sending me birthday wishes today on phone and I am unable to see any :crying:
Click to expand...
Click to collapse
Since the last thing you flashed was the stock firmware, boot into Stock Recovery and do a factory reset then reboot back to bootloader. Install TWRP and if the Guru Reset is still on your phone then flash it. If not, then push it to your phone like before. Hopefully, the factory reset in Recovery will clean out any outstanding issues.
Moved on to M8.. but still like to fix m7
Unfortunately none of the above steps worked hence I decided to move on with M8. However now that I have a working phone (M8) I am open to experiment with my M7.
Yesterday I tried restoring M7 nandroid backup from HTC guru and had some luck. But I guess I downloaded an older version of nandroid backup. So two questions:
1. Can anyone point me to correct version of nandroid backup that I can restore. (Phone is unlocked, S-On and not rooted. If I need to root it then I will need some guidance).
2. Any other method you guys can suggest to get the phone up and running again.
Below are getvar details.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 4130mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
cagashe said:
Unfortunately none of the above steps worked hence I decided to move on with M8. However now that I have a working phone (M8) I am open to experiment with my M7.
Yesterday I tried restoring M7 nandroid backup from HTC guru and had some luck. But I guess I downloaded an older version of nandroid backup. So two questions:
1. Can anyone point me to correct version of nandroid backup that I can restore. (Phone is unlocked, S-On and not rooted. If I need to root it then I will need some guidance).
2. Any other method you guys can suggest to get the phone up and running again.
Below are getvar details.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 4130mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
The nandroid backup is in the same post as the Guru Reset
http://forum.xda-developers.com/showthread.php?t=2775650
clsA said:
The nandroid backup is in the same post as the Guru Reset
http://forum.xda-developers.com/showthread.php?t=2775650
Click to expand...
Click to collapse
Thanks @clsA.. I have downloaded and copied the nandroid to device as mentioned in the post. Just one more question before I restore.. do I need to modify anything in the recovery. txt or I can simply restore it as-is
cagashe said:
Thanks @clsA.. I have downloaded and copied the nandroid to device as mentioned in the post. Just one more question before I restore.. do I need to modify anything in the recovery. txt or I can simply restore it as-is
Click to expand...
Click to collapse
it's fine as is
sometime a factory reset is needed after the restore is complete
clsA said:
it's fine as is
sometime a factory reset is needed after the restore is complete
Click to expand...
Click to collapse
@clsA.. I was able to restore the backup and saw the home screen. However after that it went to bootloop. I tried factory reset as you mentioned but no luck. Any thoughts? I am thinking of updating firmware?
cagashe said:
@clsA.. I was able to restore the backup and saw the home screen. However after that it went to bootloop. I tried factory reset as you mentioned but no luck. Any thoughts? I am thinking of updating firmware?
Click to expand...
Click to collapse
firmware is not going to help you have already done that
go into TWRP and wipe / format data ..type yes
push this rom to your phone and try it
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
clsA said:
firmware is not going to help you have already done that
go into TWRP and wipe / format data ..type yes
push this rom to your phone and try it
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
Click to expand...
Click to collapse
@clsA.. tried installing new rom you mentioned but no luck and it's back to bootloop from HTC screen. I am now thinking to restore your nandroid backup and look into build.prop. In one of the readings I came across this command which I believe is for getting usb debugging enabled.
write /sys/class/android_usb/android0/enable 1
start adbd
I am thinking to boot in twrp and run above command in adb shell. If successful then I think I can try rumrunner or firewater to s-off the phone... Totally frustrated now.. I have no idea why nothing is working on this phone.
USB Debugging ON now
clsA said:
firmware is not going to help you have already done that
go into TWRP and wipe / format data ..type yes
push this rom to your phone and try it
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
Click to expand...
Click to collapse
@clsA... after some more research I found a way to enable USB debugging so steps I followed were:
1. Restored nandroid backup you mentioned in above post.
2. Modified build.prop and default.prop from PC and pushed them back in /system and / respectively.
3. I can now see usb debugging enabled in the home screen.
Only issue I am facing now is even after factory reset phone goes in bootloop from home screen (home screen always remains locked). Any thoughts?
If I somehow get S-Off by rumrunner or firewater would I have more options?
Please help me unroot my phone. I've been on here since 1 pm and its almost 6 pm, and no closer to solving my problem. I'm fed up with, "just follow this link and you'll get a solution" only to have more questions. or get to dead links. I need a step by step set of instructions. Please. Remember, this might be second nature/old school for you, but I've been on here coming on 5 hours reading thread after thread where each thread refers to each other in a freaken loop.
Ok
I have the HTC One M7
CID T-Mob010
getvar main 1.27.531.7 (The closest I found is 1.27.531.11, can I use it?)
I have no clue about update.zip files
I have no clue about recovery.img
I have no clue on firmware.zip.
I don't know where to find previous updates on the phone and can't find the system folder.
Oh, and as you may know, there may be no RUU for my phone.
And I don't have enough posts to respond to developer posts, so if you direct me to something like that, its useless for me.
I should say, I'm rooted, I ignored updates on my phone for a long time. And I want to unroot, so I can have a simple phone again. I keep getting prompted to upgrade to 1.27.531.8. And if I say yes, my phone goes to recovery screen, tells me it's updating, FOREVER. I have to wait for my phone battery to die before I can use it again.
I have the HTC All-in-One.
What do I do to unroot my phone please. Please... Please.
MrLostsoul said:
Please help me unroot my phone. I've been on here since 1 pm and its almost 6 pm, and no closer to solving my problem. I'm fed up with, "just follow this link and you'll get a solution" only to have more questions. or get to dead links. I need a step by step set of instructions. Please. Remember, this might be second nature/old school for you, but I've been on here coming on 5 hours reading thread after thread where each thread refers to each other in a freaken loop.
Ok
I have the HTC One M7
CID T-Mob010
getvar main 1.27.531.7 (The closest I found is 1.27.531.11, can I use it?)
I have no clue about update.zip files
I have no clue about recovery.img
I have no clue on firmware.zip.
I don't know where to find previous updates on the phone and can't find the system folder.
Oh, and as you may know, there may be no RUU for my phone.
And I don't have enough posts to respond to developer posts, so if you direct me to something like that, its useless for me.
I should say, I'm rooted, I ignored updates on my phone for a long time. And I want to unroot, so I can have a simple phone again. I keep getting prompted to upgrade to 1.27.531.8. And if I say yes, my phone goes to recovery screen, tells me it's updating, FOREVER. I have to wait for my phone battery to die before I can use it again.
I have the HTC All-in-One.
What do I do to unroot my phone please. Please... Please.
Click to expand...
Click to collapse
Assuming you are S-ON, you will need to perform the following:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
[*]If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
[*]If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
[*]Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
[*]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
RUU TMOUS 1.27.531.11
RUU TMOUS 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.9
Reboot your phone to the bootloader
Shut Down / Hold volume down + Power till you see the Bootloader screen
When in bootloader connect your phone to your PC you should see FASTBOOT USB
Now type in a command window:
Code:
fastboot oem lock
With your bootloader locked you can now run the RUU's in order.
If you want to S-OFF, I would do it with the earlier RUU because the later RUU will require you to pay to achieve S-OFF.
Response
Thank you for responding. Sorry for my delayed response, I work 2 jobs during the week and can only work on this during the weekend. I will post an update on Saturday. What is S-OFF? I've seen it. I know it's a setting. I can't recall what it stands for. Thank you.
majmoz said:
Assuming you are S-ON, you will need to perform the following:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
[*]If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
[*]If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
[*]Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
[*]
Download:
RUU TMOUS 1.27.531.11
RUU TMOUS 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.9
Reboot your phone to the bootloader
Shut Down / Hold volume down + Power till you see the Bootloader screen
When in bootloader connect your phone to your PC you should see FASTBOOT USB
Now type in a command window:
Code:
fastboot oem lock
With your bootloader locked you can now run the RUU's in order.
If you want to S-OFF, I would do it with the earlier RUU because the later RUU will require you to pay to achieve S-OFF.
Click to expand...
Click to collapse
MrLostsoul said:
Thank you for responding. Sorry for my delayed response, I work 2 jobs during the week and can only work on this during the weekend. I will post an update on Saturday. What is S-OFF? I've seen it. I know it's a setting. I can't recall what it stands for. Thank you.
Click to expand...
Click to collapse
S-ON is security on which will keep the user from corrupting the internal root folders. When you are S-OFF there is no security (security off) and the phone will not stop the user from corrupting the internal folders. You have to be very careful when updating firmware or RUU when you are S-OFF if you make a mistake it can brick your phone. With S-ON, it will keep you from installing the wrong firmware or RUU.
majmoz said:
S-ON is security on which will keep the user from corrupting the internal root folders. When you are S-OFF there is no security (security off) and the phone will not stop the user from corrupting the internal folders. You have to be very careful when updating firmware or RUU when you are S-OFF if you make a mistake it can brick your phone. With S-ON, it will keep you from installing the wrong firmware or RUU.
Click to expand...
Click to collapse
"With your bootloader locked you can now run the RUU's in order."
"If you want to S-OFF, I would do it with the earlier RUU because the later RUU will require you to pay to achieve S-OFF."
Download:
RUU TMOUS 1.27.531.11
RUU TMOUS 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.9
"Run the RUU's in order."
Does that mean start with 1.27.531.11, then 3.24.531.3, etc... Or just do 1.27.531.11?
MrLostsoul said:
"With your bootloader locked you can now run the RUU's in order."
"If you want to S-OFF, I would do it with the earlier RUU because the later RUU will require you to pay to achieve S-OFF."
Download:
RUU TMOUS 1.27.531.11
RUU TMOUS 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.9
"Run the RUU's in order."
Does that mean start with 1.27.531.11, then 3.24.531.3, etc... ?
Click to expand...
Click to collapse
Yes, start with 1.27 then do the rest in order.
Than you, still working on this.
majmoz said:
Yes, start with 1.27 then do the rest in order.
Click to expand...
Click to collapse
I can't download the following. I get directed to other locations that don't have these:
RUU 4.19.531.10
RUU 5.14.531.9
I've had to work these last 2 weekends. I'm trying to get this done. Do you know where else I can get them. also, I'm getting beat up with popups. I have to clean my computer before continuing. Also, why are the files gigabyte long, each? ok, I think I have all 4. It will be a while to download them.
Wait, RUU 4.19.531.10 leads me to a xba forum and the only link may be for the HTC M8, I have the M7, download it anyway?
@majmoz I'm in a similar situation. Trying to get my wife's phone updated to the latest Lollipop because the 4.4.3 downloads were failing to install. I'm currently factory reset on 4.4.2.
I had previously unlocked, put TWRP on there, but have done a couple things over the last 6 months and can't remember now. I just flashed a stock recovery, and then relocked the bootloader so it's showing;
*** TAMPERED ***
*** RELOCKED ***
Here's my situation:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.14.531.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3896mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What's the reason for installing all the RUU's in order? Can I just install the RUU for Lollipop (I have RUU_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421697_signed_2.exe downloaded)?
Just want to get back to a stock recovery, locked phone with stock Lollipop.
Thanks for any help!
lamenting said:
@majmoz I'm in a similar situation. Trying to get my wife's phone updated to the latest Lollipop because the 4.4.3 downloads were failing to install. I'm currently factory reset on 4.4.2.
I had previously unlocked, put TWRP on there, but have done a couple things over the last 6 months and can't remember now. I just flashed a stock recovery, and then relocked the bootloader so it's showing;
*** TAMPERED ***
*** RELOCKED ***
Here's my situation:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.14.531.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3896mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What's the reason for installing all the RUU's in order? Can I just install the RUU for Lollipop (I have RUU_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421697_signed_2.exe downloaded)?
Just want to get back to a stock recovery, locked phone with stock Lollipop.
Thanks for any help!
Click to expand...
Click to collapse
Unfortunately, Lollipop requires 6.xx framework. So you will need to run the RUU 6.10.531.10 first. Since you are S-ON your bootloader must be locked. Just follow the instructions on the download page.
majmoz said:
Unfortunately, Lollipop requires 6.xx framework. So you will need to run the RUU 6.10.531.10 first. Since you are S-ON your bootloader must be locked. Just follow the instructions on the download page.
Click to expand...
Click to collapse
Bootloader is locked.
So before you replied I ran the RUU updater for Lollipop. It detected the phone, and is now trying to update.. but it's just sitting at:
Updating.. (1/6) Sending...................
Updating the ROM image on your Android phone...
Please do not remove the USB connection from the Android phone or launch any programs duing the update process.
Remember, the operation will take about 10 minutes.
Says it will take 10 minutes, but it's been about 30+.
Kind of afraid to kill the update process at this point..
edit: OK unplugged the USB cable. Downloading the 4.4.3 RUU and will try it out.
But if a proper OTA update failed previously (way before I started unlocking, putting a custom recovery, etc), why would this work? I would always get the red exclamation mark when I tried doing the proper OTA update. :/
lamenting said:
Bootloader is locked.
So before you replied I ran the RUU updater for Lollipop. It detected the phone, and is now trying to update.. but it's just sitting at:
Updating.. (1/6) Sending...................
Updating the ROM image on your Android phone...
Please do not remove the USB connection from the Android phone or launch any programs duing the update process.
Remember, the operation will take about 10 minutes.
Says it will take 10 minutes, but it's been about 30+.
Kind of afraid to kill the update process at this point..
Click to expand...
Click to collapse
It should eventually error out. Then run the KK 6.10 first and good luck.
majmoz said:
It should eventually error out. Then run the KK 6.10 first and good luck.
Click to expand...
Click to collapse
It gave me the error 155.
In the boot screen I'm seeing:
Hboot version is older!
Update fail!
Any thoughts? And thanks again for your help!
---------- Post added at 11:14 AM ---------- Previous post was at 11:10 AM ----------
Oh.. it's because I tried to update to Lollipop first, isn't it...
hboot is now on 1.61.0000
if worse comes to worse, can I:
Unlock bootloader again
Flash TWRP
Find a flashable stock Lollipop ROM
Do you think that will work? And if so what do you recommend?
lamenting said:
It gave me the error 155.
In the boot screen I'm seeing:
Hboot version is older!
Update fail!
Any thoughts? And thanks again for your help!
---------- Post added at 11:14 AM ---------- Previous post was at 11:10 AM ----------
Oh.. it's because I tried to update to Lollipop first, isn't it...
hboot is now on 1.61.0000
if worse comes to worse, can I:
Unlock bootloader again
Flash TWRP
Find a flashable stock Lollipop ROM
Do you think that will work? And if so what do you recommend?
Click to expand...
Click to collapse
Just to make sure you can check fastboot getvar all to see if that is the case. If it is then you will need to gain S-OFF to downgrade your hboot so you can run the KK RUU successfully.
I am not sure that Sunshine S-OFF will work but it will tell you if it will before you pay.
The issue with flashing just the stock ROM, your firmware will be the old version and you can not upgrade it.