Hey folks,
I already searched on XDA and the web, but found nothing helpful, so I decided to start an new thread:
I got my new ONE X PLUS just a few weeks ago and now I wanted to start with unlocking the bootloader and rooting it.
I already got some experience in unlocking, rooting and flashing with an HTC Incredible S and SE Xperia X8.
Prerequisites my Computer(win7 x64) fulfills:
Latest Android SDK installed
HTC Divers installed
Folder on HDD: C:\android\onexplus containing all necessary files.
So I followed all the steps on htcdev.com like I did with my Incredible S.
I´ve got my Unlock_Code.bin and wanted to flash that on my ONE X+.
So I executed
Code:
fastboot flash unlocktoken Unlock_code.bin
prompted the dialog on the phone with "YES" and got:
Code:
C:\android\onexplus>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.126s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Unknown error))
finished. total time: 49.707s
When I boot into bootloader again, it displays "unlocked" (see attached picture),although fastboot displayed an error.
So I tried to root it via rootboot, like mentioned in a whole lot of tutorials.
This is, what rootboot.bat returns to me:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
mount: Operation not permitted
failed to copy 'Tools/su' to '/system/xbin/su': Read-only file system
failed to copy 'Tools/Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Press Enter
That seems to me like unlocking has failed and the phone is still locked.
When I want to lock it again via
Code:
fastboot oem lock
, fastboot displays the same error, but the bootloader again says locked!
Problem sources that I kicked out already:
Changed USB Cable and Port
Phone was always charged at least 90%
Reinstalled latest HTC Drivers and Android SDK & restarted the PC
Submitted my OEM_Identifier_Toeken again and got a new Unlock_Code.bin
Deleted all my old Files from rooting and flashing the IncS & X8
got a new folder (C:\android\onexplus) with all necessary files
Tested whole procedure also on a x64 Linux Box(latest Archlinux release): Same result: fastboot displays error code, but the Bootloader says "UNLOCKED". Interesting fact: The error on linux differs from the one on windows:
Code:
[email protected]:~/android: sudo ./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... INFOunlock token check successfully
FAILED (status read failed (Cannot send after transport endpoint shutdown))
I am at my wit's end, obviously I did something wrong, but what ? Or is the device correctly unlocked and I just failed on rooting it ?
Is there another way to check if the device is correctly unlocked?
I don´t know if it´s useful, but here´s the result of "fastboot getvar all":
Code:
C:\android\onexplus>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.35.0000
(bootloader) version-baseband: 3.1204.168.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.17.401.1
(bootloader) serialno: FA2BRW103800
(bootloader) imei: 353567051431246
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3817mV
(bootloader) devpower: 48
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.448s
Thanks in advance for your answers
Roman
Attached Pictures:
-HTC ONE X + Incredible S in HBOOT (to compare)
-HTC ONE X + in FASTBOOT USB
After reinstalling the whole HTC Drivers and software pack, to have a clean base; Now I encounter another error when I execute
Code:
fastboot flash unlocktoken Unlock_code.bin
This time fastboot reports the following error:
Code:
C:\android\onexplus>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.078s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 41.211s
And also the lock command gives me:
Code:
C:\android\onexplus>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.104s
Another thought: Could this be a problem with the bootloader and fixed by installing an new RUU by HTC ?
And, like mentioned above, is there any way to check if the device was unlocked correctly ?
TIA
Roman
leuprechtroman said:
After reinstalling the whole HTC Drivers and software pack, to have a clean base; Now I encounter another error when I execute
Code:
fastboot flash unlocktoken Unlock_code.bin
This time fastboot reports the following error:
Code:
C:\android\onexplus>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.078s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 41.211s
And also the lock command gives me:
Code:
C:\android\onexplus>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.104s
Another thought: Could this be a problem with the bootloader and fixed by installing an new RUU by HTC ?
And, like mentioned above, is there any way to check if the device was unlocked correctly ?
TIA
Roman
Click to expand...
Click to collapse
I'm no expert but on the past 4 HTC phones I've unlocked and the several I have unlocked for friends this error with "to many links" always comes up and says failed. It has never stopped any device I have from functioning.
Kraizk said:
I'm no expert but on the past 4 HTC phones I've unlocked and the several I have unlocked for friends this error with "to many links" always comes up and says failed. It has never stopped any device I have from functioning.
Click to expand...
Click to collapse
Thanks a lot man :good:
TIA
PS: Edited, I really missed the forest for the trees
The too many links error, is usually cause you have more than one android device connected, or running the android emulator.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
The too many links error, is usually cause you have more than one android device connected, or running the android emulator.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Never had more than one plugged in and never had emulator running. Either way it sounds fixed.
Absolutely fixed
Thanks a lot for the tips you two, great job! :good:
HOX+ running perfectly rooted.
Thank you
Roman
I see a little old but how did you fix this issue leuprechtroman? I am running into the same type of error.
Yes, I'd like to know too what was the way out of this?
leuprechtroman said:
Absolutely fixed
Thanks a lot for the tips you two, great job! :good:
HOX+ running perfectly rooted.
Thank you
Roman
Click to expand...
Click to collapse
Hey bro how can u fix this problem same error taken ..
I was going through the steps to try to flash the Google Edition ROM onto my T-Mobile HTC One using this guide: http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
I have unlocked the bootloader, rooted, and gotten S-off. I'm on Step 3, changing the model ID if necessary. I was stupid and was not reading carefully enough, and missed the edit at the top of the section saying I didn't actually need to change this. So I went to the guide he linked to: http://forum.xda-developers.com/showthread.php?t=2322820
In this guide, I downloaded the PL83IMG.zip and edited the text file to put in my current Model ID, Cell ID, and ROM version. Rezipped, then did the command he gives:
Code:
c:\sdk-tools>fastboot flash zip android-info.zip
target reported max download size of 1526722560 bytes
sending 'zip' (479 KB)...
OKAY [ 0.247s]
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,43
(bootloader) [RUU]UZ,hboot,99
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.401s]
finished. total time: 2.653s
Ok, now as he says in the guide, I saw the HTC logo and a progress bar that was sitting at about 3/4 done. He says to reboot the phone, so I did this. The screen remains blank, I don't get the gray spotted screen he describes. I tried the "fastboot oem writemid PN0712000" command, and it just sat on "< waiting for device >" for a long time, until I finally cancelled the command.
I can still get into the bootloader by holding down power and volume down, but if I try to boot normally or boot into recovery, the screen just turns off and remains off. Also, the device can no longer be recognized on my computer. I get a popup from Windows saying "the last USB device connected to this computer malfunctioned, Windows does not recognize it." And neither adb or fastboot can see that there is a device connected.
So...is my phone bricked? Is there some way I can recover from this? I assume the problem is this HBOOT that I flashed. This is what I'm seeing on my bootloader screen
Code:
*** LOCKED ***
M7_UL PVT ENG S-OFF
CID-T-MOB010
HBOOT-1.39.2000 (PN0713000)
OpenDSP-v32.120.274.0909
eMMC-boot
I do notice that it changed to LOCKED from UNLOCKED and TAMPERED.
Mine followed the same pattern. You should be able to make sure your in fastboot and write your CID and MID and then run an RUU through the fastboot OEM rebootRUU command
Sent from my Nexus 10 using Tapatalk 4
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?
Greetings,
This issue occurred between Friday 7/26/2019 midnight and Saturday 7/27/2019 afternoon.
I found my nexus 6p in a boot loop at the 'Google' logo.
It's in a state where I can get to the boot loader with (power + vol down), but the only valid options, is a reboot (boot loops), reboot boot loader (works), recovery mode (boot loops)
I'm no stranger to tinkering with ads/fastboot, flashing other mobile (Samsung note , with odin, etc)
I'm aware of the main issues plaguing this mobile device (battery drain issue and the infinite boot loops - rampant 2017).
I've had the phone since 2015, and I don't remember honestly of flashing to factory and all of that -- probably did (as it was the reason to getting a nexus, rooting, loading custom roms, developer options, turning on debugging mode, etc).
I did replace my battery, I didn't really encountered the boot loop issue till now.
I don't know if the phone did an update or had an update pushed to it, but after going to bed Friday 7/26 (working phone) and when I woke up around noon on 7/27, I had a non-functional, google boot looping nexus 6p
I'm sure that the phone has been on developer mode, with oem unlocked settings, and other "settings" tweaked, such as the usb debugging option and how to handle connection (charging, media xfer, etc...)
Not sure if anyone else over the weekend had their Nexus 6P turn into a brick...
At this point, I would like to just be able to get to the point where I can connect via fastboot/adb (functionally) to pull off data, before any full wipe is done--if at all possible, else I will cut my losses...painfully as it may be. Yes, shame on me, should have backed up all of my pics/media files/contacts, etc...,
I do realize if the unlocking of the boot loader is done, it will also fully wipe system and user data, I've been googling all day and trying commands left and right.
the fastboot seems to be the only thing that connects...
the adb doesn't list any devices (went through kill-server, reconnect, etc...)
I will trying to provide whatever additional output that I'm able to get access to.
Last ditch effort, reach out to Huawei customer support and see if there's anything they can/will do.
If there's a chance to get it to a state where I can retrieve data off of it, I'm ok with moving on (abandoning nexus 6p) to another mobile device...
Willing to try and work with whomever and however long it takes if possible to recover...
==output
sh-3.2# ./fastboot devices
5VT7N15C03002060 fastboot
sh-3.2#
sh-3.2# ./fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:no
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-03.88
(bootloader) version-bootloader:angler-03.84
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1c3957ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:5VT7N15C03002060
(bootloader) kernel:lk
(bootloader) product:angler
all:
Finished. Total time: 0.179s
sh-3.2# ./adb kill-server
sh-3.2# ./adb devices -l
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
sh-3.2# ./adb devices -l
List of devices attached
sh-3.2#
sh-3.2# ./adb reconnect
no devices/emulators found
sh-3.2#
sh-3.2# ./fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
fastboot: error: Command failed
sh-3.2#
==
sincerely
in despair