Related
Hello all,
I'm hoping someone can tell me what I'm doing wrong.
I went to HTCdev and got the unlock code emailed but this is happening when i try to unlock,I put the code in the same folder as the fastboot...
C:\Joey\Unlock Tools>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 09676CC238975AE58745ED43A1A50C8A
(bootloader) ECF90A6E24B47051377B15F0178DF92C
(bootloader) A393503ADCC8606FC14ED1761E2456F6
(bootloader) F57F798477728947A8B7E1EBD8C343BA
(bootloader) 3966E2A81DF8844D9470FF08C7F75B60
(bootloader) AE0F848DE98EA5CE3D0C4341902723C5
(bootloader) F773CAAACE0D1F8E84BCB246BCC410E3
(bootloader) 02670551F637FB8AD6E4783FDDABD8D4
(bootloader) CAC4613F93ABB73203D1EB8552BA705F
(bootloader) 9417AC2E0E0DFD82F424EB0141A0E47F
(bootloader) B1CDF5791CD1F196A2B5282143FCFB1E
(bootloader) 57453E81BFC316B3D372F6DD74D65FA6
(bootloader) F6DB2C323BCB1BFE4040B59C10B4FC90
(bootloader) 77CFE117D6670229E2FF6C64C6125601
(bootloader) C7671A07B7034C492C85213FCCDC0DD3
(bootloader) A019ADDF0F220049A7404264BAE50571
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Joey\Unlock Tools>fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'
Idea
I don't see the part where you got an email with the unlock code from HTC.
You have to submit that text to HTC, get an email with the file, put the file in the same folder as Fastboot, and then apply it.
Thanks for the reply,I got the code emailed and downloaded.I put it in the folder with the fastboot and got the error...I have no Idea what I did wrong.
Don't reboot your phone...also...male sure the phone is still in fastboot obviously.
Sent from my ADR6425LVW using XDA App
Thanks for your reply also.
I got it unlocked I had to change the folder name,I guess it wouldn't work cause unlock was in the folder name as soon as I changed it and entered the path it went though.. so I'm guessing that was the problem.
shooter_454 said:
Thanks for your reply also.
I got it unlocked I had to change the folder name,I guess it wouldn't work cause unlock was in the folder name as soon as I changed it and entered the path it went though.. so I'm guessing that was the problem.
Click to expand...
Click to collapse
Glad you got it figured out man!
Use fastboot for kernels, lol, I wish I had and almost bricked my phone.
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 ..
Hi,
Unlocked my wife's Legend using the HTC-Dev method. Installed CM7 and she was happy... Now she is missing the HTC weather animations and wants to go back to the stock Froyo.
I have the correct RUU for her phone, carrier, and region, extracted from:
RUU_Legend_BellMobility_WWE_2.02.666.3_Radio_47.37.35.09_7.08.35.05_release_130094_signed.exe
First I tried to flash by renaming the rom.zip to LEGEIMG.zip. The bootloader saw it and chewed on it for a while, but the RUU ended up not being applied and the phone booted back into CM. Confusing.
Next attempt: fastboot, with bootloader unlocked.
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.795s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
[B]FAILED (remote: 99 unknown fail)[/B]
finished. total time: 18.643s
Did some more reading, found that RUUs only apply when the bootloader is locked. So I relocked the bootloader with fastboot oem lock and tried again:
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
< waiting for device >
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.874s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[B]FAILED (remote: 43 main version check fail)[/B]
finished. total time: 44.062s
And trying the LEGEIMG.zip method after relocking:
Code:
Main version is older!
Update Fail!
Do you want to reboot device?
Here are my bootvars:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0000
(bootloader) version-baseband: 7.13.35.13
(bootloader) version-cpld: None
(bootloader) version-microp: 0816
(bootloader) version-main: 3.30.0.0
(bootloader) serialno: HT05NRA07XX
(bootloader) imei: XXXXX
(bootloader) product: legend
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PB7611000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-39ec9098
(bootloader) hbootpreupdate: 11
Apparently this means that I'm trying to flash an RUU that is older than what is on the device. The problem is, the RUU update that I last applied was the HTCDev one to allow unlocking. So the most recent "full" RUU is older than the HTCDev RUU and I can't seem to downgrade.
Am I missing something? I must be missing something. Please help, or the wife will have one up on me. Can't allow that
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
When I remember right, there was no version check during installation, you can install it with Clockwork mode Recovery.
alligator_asl said:
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
Click to expand...
Click to collapse
Thanks, that's an acceptable workaround for now. I ended up going this route. Since CWM 5.X doesn't like "amend" scripting, it took some doing though. :highfive:
If anyone knows of a way to downgrade to a stock RUU after applying the HBOOT 1.02 RUU to the Legend, that would be a help.
I'd suggest if you really need to go back stock froyo it can't be done with hboot 1.02, I have tried various different methods with no success.
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Sent from my Legend using xda app-developers app
ranger4740 said:
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Click to expand...
Click to collapse
Yeah, that sounds right.
So for anyone reading this thread in the future, if you've unlocked your bootloader using HTC-dev you will be unable to return to stock Froyo using an official RUU without first downgrading to HBOOT 1.01 or older.
The HBOOT downgrade process is pretty involved. You need a goldcard and the hack4legend kit. See this thread for details.
And for good measure, here's a thread with someone else working out the same problem we just worked out here... :silly:
At the end of the day, if you ran a nandroid backup of your stock ROM before blowing it away, you won't need all this jazz.
ariaxu said:
Since CWM 5.X doesn't like "amend" scripting, it took some doing though.
Click to expand...
Click to collapse
You can take an older Versin of CWM ( recovery-clockwork-2.5.0.7-legend.zip ), ther are no problems with scripting, a google search brings several results.
If necessary, you lan load the old version of CWM from the new version and then you can flash this ROM !
[Stock Backup & OTA Zip] Int - T6UL | Sense 5.5[2.61.707.1] & Sense 6[3.14.707.3]
Stock Backup TWRP - International | Unrooted | Sense5.5 | 2.61.707.1
[2014-06-17--17-34-28 KOT49H release-keys] - [2.61.707.1] [Stock ROM Unrooted]
Info : 13 Splits 100MB RAR File
Size : 1.23GB
Download : https://www.mediafire.com/folder/zc5097wdc65ij/
Stock Recovery : http://www.mediafire.com/download/envapmqe1ev31iu/
☛ Move the extracted backup folder into folder "TWRP\BACKUPS\FA3BXXXXXXXX\" and restore via TWRP ☚
☛ Preload apps already added in the backup ☚
☛ If you're going to take OTA, Flash stock recovery, lock bootloader and you're ready to get OTA ☚
Stock Backup TWRP - International | Unrooted | Sense6 | 3.14.707.3
[2014-06-17--18-30-09 KOT49H release-keys] - [3.14.707.3] [Stock ROM Unrooted]
Info : 12 Splits 100MB RAR File
Size : 1.09GB
Download : https://www.mediafire.com/folder/8u5okmczf5206/
Stock Recovery : http://www.mediafire.com/download/n8apfhsujg84dje/
☛ Move the extracted backup folder into folder "TWRP\BACKUPS\FA3BXXXXXXXX\" and restore via TWRP ☚
International T6UL - hboot 3.14.707.3 no red text modified
Download & Instruction : Here
Alt. download : http://www.mediafire.com/download/7ab1sn3r2wdvqx8/
Credit & thanks to : @abusalza
☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢
OTA Zip Only - T6UL - International | Sense6 | 3.14.707.3
version-bootloader: 2.49.0000
version-baseband: 4T.27.3218.14
version-main: 3.14.707.3
product: t6ul
modelid: 0P3P52000
cidnum: HTC__044
hbootpreupdate:12
[3.14.707.3] OTA_T6_UL_K44_SENSE60_MR_hTC_Asia_WWE_3.14.707.3-2.61.707.1_release_379462.zip
Size : 561.65MB
MD5 : BC7576A355508D2978E9E7885AF5425E
Download : http://www.mediafire.com/download/y86ri4h7zu9gypo
Firmware.zip only ~Removed~ due to complaints and fail to match device requirements can cause device hard bricks when flashed.
Please download full package official OTA update by htc from above link.
How to install OTA update package on stock ROM t6ul 2.61.707.1 :
1. Download OTA update file package
2. You can rename it to a simple name e.g: 'update.zip'
3. Copy to root of SD card
4. Boot device into Bootloader
5. Enter Recovery
6. Select Update from zip
7. Select 'install update.zip from SD card'
☢☣ Install at your own risk ☣☢
If im s-off and unlock, can i flash this firmware?
Winins said:
If im s-off and unlock, can i flash this firmware?
Click to expand...
Click to collapse
If your device version is matched in the OP, the answer is YES. Flash firmware.zip in RUU.
I have supercid, this firmware only update hboot and radio, no?
Winins said:
I have supercid, this firmware only update hboot and radio, no?
Click to expand...
Click to collapse
This firmware.zip will update/replace recovery, hboot, boot.img, and radio.img
After flash firmware.zip in RUU,
1. You need to reboot.
2. Reflash custom recovery.
3. Dirty flash your current custom rom
4. Profit!
Your supercid will be replace with stock hboot CID. Redo step to get supercid after flash
Intl hboot 3.14.707.3 no red text modified
You must be S-Off to do this! This one's for International variant only
I can not be held responsible for this zip please flash at your own risk!!
Place the zip in your adb/ fastboot directory on your computer
Put the device in fastboot mode and connect to the computer
Enter the following commands from cmd from the adb/ fastboot directory:
fastboot oem rebootRUU
fastboot flash zip 3.14.707.3_NoRedText_hboot.zip
Note: The progress on the screen may not fully 100% but it's normal. but make sure it's writen "successfully" on the cmd windows on your PC
fastboot reboot-bootloader
@abusalza , Thanks buddy! appreciated your work.
edit : it works perfect!
mafyas said:
@abusalza , Thanks buddy! appreciated your work.
Click to expand...
Click to collapse
you're very welcome buddy...
i flashed firmware zip and my phone dont reboot, what am i doing?
do i bricked my one max?
How did you flash it? What does it tells at the end of the process? Your phone didnt boot mean? Cant get into bootloader or cant get into homescreen?
Give some details sir so i could help.
Blackscreen!! i cant power on my phone. No bootloader, no fastboot, no recovery, no normal boot... i think i brikced it, i used this:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot-bootloader
when i connect my phone with my pc, pc show qhsusb_dload in usb.
Winins said:
Blackscreen!! i cant power on my phone. No bootloader, no fastboot, no recovery, no normal boot... i think i brikced it, i used this:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot-bootloader
when i connect my phone with my pc, pc show qhsusb_dload in usb.
Click to expand...
Click to collapse
That's weird, should not be any problem if your device is matched version in the OP because I have no problem flashing firmware. Hardly say that your device bricked. I don't know how to help in this case, try search forum if any helpful thread regarding recover bricked.
can anyone help me with qhsusb_dload?
Winins said:
can anyone help me with qhsusb_dload?
Click to expand...
Click to collapse
what happens if you hold volume up and power for sixty seconds with the phone not connected to the PC?
Sent from my SM-T320 using Tapatalk
nothing, blackscreen all time, i think my phone bricked
perhaps this could help!
Winins said:
nothing, blackscreen all time, i think my phone bricked
Click to expand...
Click to collapse
Don't intend to mess this up, but when you hold vol up + power buttons for tens of seconds did you see the capacitive buttons blink a few times?
If so, then you can wait until it stops blinking (should be about 5-8x blinking) and quickly release both vol up and power buttons, then hold vol down for a few seconds then release it. it should bring you to HBOOT mode.
This worked for me when I thought I had bricked my One max from accidental build.prop modification (changed the value and forgot to set correct permission).
If holding vol up + power does not make the capacitive buttons blink a few times, then sadly it could be a hard brick.
captative buttons arent on when i used vol up + power. Hardbrick
Updated
OP updated with latest [Stock Backup TWRP - International | Unrooted | Sense6 | 3.14.707.3]
Startet Flash of Firmware. And my Phone switched off by itself. Windows now detect qhsusb_dload and nothing more is working I have now the same Problem like Winins. I have a international Version of the One Max Modellid and all other things matched. Is not my First Phone from Htc that i flash i am sure i did nothing wrong and now i Have a brick wow. Hopfully my waranty will help me out of this Problem. Or can i do anything now. I found some people with same Problem but with other HTC devices and there exist a fix but i don´t know if these fixes will work with One Max.
Here a copy of the Flash Report:
C:\1>fastboot flash zip firmware.zip
target reported max download size of 1554698240 bytes
sending 'zip' (45929 KB)...
OKAY [ 2.783s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping for pre-update...
(bootloader) start image[sbl1-1] flushing...
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ...... Bypassed
(bootloader) start image[sbl1-2] unzipping for pre-update...
(bootloader) start image[sbl1-2] flushing...
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ...... Bypassed
(bootloader) start image[sbl1-3] unzipping for pre-update...
(bootloader) start image[sbl1-3] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-4] unzipping for pre-update...
(bootloader) start image[sbl1-4] flushing...
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ...... Bypassed
(bootloader) start image[sbl1-5] unzipping for pre-update...
(bootloader) start image[sbl1-5] flushing...
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ...... Bypassed
(bootloader) start image[rpm] unzipping for pre-update...
(bootloader) start image[rpm] flushing...
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 6.820s
Oh man.. I hate to see this happen. The flash report says, "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" . Did you flash it again? When it does say "Failed", you should re-flash it immediately. When it says "Okay", that's the real Okay and good to reboot. The most important, device must be S-OFF. I have done it for my friends, 4 One Max devices, no problem at all. Sigh. I'm just sharing the OTA since few people PM me for it.
OP update with sense5.5 [2.61.707.1] stock twrp backup
Hi guys, I read thousands of post and didn't found a similar case to mine. This is what happened (sorry for my english, i speak spanish )
I bought my HTC One X+ on eBay believing it was the international version because they sold me unlocked and cleaned, but after flashing a wrong firmware version (thousands of times) I realized that my phone is the AT&T or Telus (evitare_ul) version :crying:
I was so desperate that even I changed the CID (I was S-off). At the beginning had SuperCID, now I have HTC__001 and the worst of all is that I changed the android-info.txt file from these kernels https www androidfilehost (dot) com / ?w=files & flid = 32755 and i flashed.. PUM hboot bricked, I know I'm a fool my fault, i didn't read the warnings.. :crying:
- I trying different RUU for my wrong combination of CID (HTC__001) and modelid: PM631**** and I didn't found.
- I downloaded the source code from htcdev (dot) com / devcenter/ downloads but I don't know what combination i have to do. I need some extra help to build a new firmware for my rare combination of CID, hboot, baseband version and modelid
I need your help please!
I will make a donation through Paypal to the person to help me with this. :fingers-crossed:
Summarize:
Code:
version-bootloader: 1.72.0000
version-baseband: 3.1204.171.33 (for my country we use GSM and UMTS 850/1900 Mhz)
version-main: 1.15.502.9
serialno: HT2BRW302088
product: evitare_ul
platform: HBOOT-T30S
modelid: PM631****
cidnum: HTC__001
battery-status: low
battery-voltage: 3598mV
devpower: 6
partition-layout: None
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Let me know if you need anything else.
Any help would be greatly appreciated.
Thanks!
jcaballero said:
Hi guys, I read thousands of post and didn't found a similar case to mine. This is what happened (sorry for my english, i speak spanish )
I bought my HTC One X+ on eBay believing it was the international version because they sold me unlocked and cleaned, but after flashing a wrong firmware version (thousands of times) I realized that my phone is the AT&T or Telus (evitare_ul) version :crying:
I was so desperate that even I changed the CID (I was S-off). At the beginning had SuperCID, now I have HTC__001 and the worst of all is that I changed the android-info.txt file from those kernel https www androidfilehost (dot) com / ?w=files & flid = 32755 and i flashed.. PUM hboot bricked, I know I'm a fool my fault, i didn't read the warnings.. :crying:
- I trying different RUU for my wrong combination of CID (HTC__001) and modelid: PM631**** and I didn't found.
- I downloaded the source code from htcdev (dot) com / devcenter/ downloads but I don't know what combination i have to do. I need some extra help to build a new firmware for my rare combination of CID, hboot, baseband version and modelid
I need your help please!
I will make a donation through Paypal to the person to help me with this. :fingers-crossed:
Summarize:
Code:
version-bootloader: 1.72.0000
version-baseband: 3.1204.171.33 (for my country we use GSM and UMTS 850/1900 Mhz)
version-main: 1.15.502.9
serialno: HT2BRW302088
product: evitare_ul
platform: HBOOT-T30S
modelid: PM631****
cidnum: HTC__001
battery-status: low
battery-voltage: 3598mV
devpower: 6
partition-layout: None
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Let me know if you need anything else.
Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Breathe...
first up you need to charge the device, once you've done that grab one of the EVITAREUL the AT&T rom's and recoveries and flash them.
Sorted.
FAILED (remote: 12 signature verify fail)
Thanks for response, I charged my phone and I tried flashing these firmware (from forum.xda-developers com / showthread.php?t=2235248) but i got an error
Code:
C:\adb>fastboot flash zip RUU_EVITARE_UL_JB_45_Cingular_US_1.19.502.1_Odexed.zip
sending 'zip' (609633 KB)...
OKAY [ 77.719s]
writing 'zip'...
(bootloader) signature checking...
[B]FAILED (remote: 12 signature verify fail)[/B]
finished. total time: 104.810s
Code:
C:\adb>fastboot flash zip RUU_EVITARE_UL_JB_45_Telus_WWE_1.20.661.1_Odexed.zip
sending 'zip' (588120 KB)...
OKAY [ 71.639s]
writing 'zip'...
(bootloader) signature checking...
[B]FAILED (remote: 12 signature verify fail)[/B]
finished. total time: 97.739s
Wouldn't it be because my CID is HTC__001 = WWE and mi modelid: PM631****?
Is there a way to change the build.prop from these zip files to match my CID or another info?
Remember: I'm stuck in boot-mode: RUU, can't go to the recovery to unlock and change my CID (like before)
Thanks!:good:
jcaballero said:
Thanks for response, I charged my phone and I tried flashing these firmware (from forum.xda-developers com / showthread.php?t=2235248) but i got an error
Code:
C:\adb>fastboot flash zip RUU_EVITARE_UL_JB_45_Cingular_US_1.19.502.1_Odexed.zip
sending 'zip' (609633 KB)...
OKAY [ 77.719s]
writing 'zip'...
(bootloader) signature checking...
[B]FAILED (remote: 12 signature verify fail)[/B]
finished. total time: 104.810s
Code:
C:\adb>fastboot flash zip RUU_EVITARE_UL_JB_45_Telus_WWE_1.20.661.1_Odexed.zip
sending 'zip' (588120 KB)...
OKAY [ 71.639s]
writing 'zip'...
(bootloader) signature checking...
[B]FAILED (remote: 12 signature verify fail)[/B]
finished. total time: 97.739s
Wouldn't it be because my CID is HTC__001 = WWE and mi modelid: PM631****?
Is there a way to change the build.prop from these zip files to match my CID or another info?
Remember: I'm stuck in boot-mode: RUU, can't go to the recovery to unlock and change my CID (like before)
Thanks!:good:
Click to expand...
Click to collapse
If you can issue fastboot commands, you can issue fastboot flash recovery recovery.img >
Select hboot (ignore the crap that shows up)
Select recovery
You CANNOT flash the modified sense rom's in fastboot as the MD5's or whatever the hboot looks for are wrong, hence the wrong signature.
I tried with two original recovery.img from AT&T, but i get: FAILED (remote: not allowed)
Code:
C:\adb>fastboot flash recovery recovery_signed.img
sending 'recovery' (7500 KB)...
OKAY [ 0.926s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.960s
Code:
C:\adb>fastboot flash recovery ATTrecovery.img
sending 'recovery' (8224 KB)...
OKAY [ 1.019s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.040s
I can't flash anything because i'm S-ON, I'm stuck in RUU mode and I think that the only way to revive my phone is with an original RUU.exe (that doesn't exist because i changed my CID) I tried with all these RUU (www androidruu com / ?developer=EvitaRE) and i get the same error about the signature or wrong model.
I don't know if compiling from the source code (www htcdev com / devcenter / downloads) with my requirements would work, but I will pay the person who do that and makes a zip signed or encrypted firmware capable to flash in my phone...
I'm about to buy an used board to replace my f***g bricked HOX+
I don't know what to do. I'm about to give up :crying:
I extracted the rom.zip from this RUU RUU_EVITARE_UL_JB_50_S_Cingular_US_2.15.502.1_Radio_2.21.5517.15_18.27.11.35L_release_341689_signed_0220.exe
Code:
C:\adb>fastboot flash zip rom_01.zip
sending 'zip' (33584 KB)...
OKAY [ 4.109s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) Your memory size = 59640MB, choose rawpt_64g.img
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.627s
I want to edit the android-file.txt from the .zip to put my CID HTC_001 (that i changed for fool) but i need to resign or encrypt the zip before flashing again. Is there a tool that do that? I think i'm screwed :crying:
Also, i can't do the same step with this RUU_EVITARE_UL_JB_45_TELUS_WWE_1.15.661.11_Radio_1.09.55.17_18.20.95.55L_release_290307_signed because the zip is corrupted, i downloaded several times
Code:
C:\adb>fastboot flash zip rom.zip
sending 'zip' (669207 KB)...
OKAY [ 81.936s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) time: 4018
(bootloader) rom parsing finish ...
(bootloader) Your memory size = 59640MB, choose rawpt_64g.img
(bootloader) Read zipped android_info fail!
Anyone have the version not corrupted of this RUU? I downloaded the corrupted from www.androidruu.com/?developer=EvitaRE
Thanks!
Are there no other WWE evita ruus you can find? I agree you are probably out of luck, but that would be the only way to fix things that I can think of.
I think, though, you've learned why it's a very bad idea to go back to s-on after modifying your phone. There is no good reason to ever do it, and the risks are large. You changed around a whole bunch of basic settings and firmware, and then locked them down before determining if your phone was stable.
If the ruus don't work, a repair shop with jtag might be able to fix it by flashing the motherboard directly.
Okay, lets just recap.
So you flashed a kernel that was not supported by your model and now the device wont boot. So you tried to flash a ruu, but couldnt find one with your cid. So you changed your cid and re-applied s-on?
So no ruu flash occured?
Just the bad kernel flash?
Then how about this for a plan.
1. htcdev unlock the bootloader.
2. Flash a compatiable custom recovery from your device specific section.
3. Flash a compatiable custom rom for your device, thus making it boot again.
If your hboot has not been damaged ie wrong hboot flashed then a htcdev unlock should work fine. No ruu needed, not that they will work without the mid and cid matching.
Sent from my LG-D802 using Tapatalk
Edited to remove irrelevant data.
Jtag, my last chance
Hi guys, thanks for your help
iElvis, you right, I did things that I didn't know what it was about, I was so desperate.
I'll send my phone to a repair center where use the JTAG. Thanks for the info, I didn't know there was such thing :good:
heavy_metal_man
Yeah, that's the summary of what I did.. but.. I can't go back to the recovery (hboot don't work), i'm stuck in ruu mode (black screen with htc logo), So, I can't unlock de bootloader because I can't go in fastboot mode, I'm S-ON and everything I've tried I get this error: FAILED (remote: not allowed) :crying:
If you know someone (an oriental guy hahaha) that know how to encrypt a modified zip RUU to flash in ruu mode, please let me know
Thanks for everything :good:
Cheers.
jcaballero said:
Hi guys, thanks for your help
iElvis, you right, I did things that I didn't know what it was about, I was so desperate.
I'll send my phone to a repair center where use the JTAG. Thanks for the info, I didn't know there was such thing :good:
heavy_metal_man
Yeah, that's the summary of what I did.. but.. I can't go back to the recovery (hboot don't work), i'm stuck in ruu mode (black screen with htc logo), So, I can't unlock de bootloader because I can't go in fastboot mode, I'm S-ON and everything I've tried I get this error: FAILED (remote: not allowed) :crying:
If you know someone (an oriental guy hahaha) that know how to encrypt a modified zip RUU to flash in ruu mode, please let me know
Thanks for everything :good:
Cheers.
Click to expand...
Click to collapse
Try the command
fastboot reboot-bootloader
To get out of ruu mode.
Sent from my LG-D802 using Tapatalk
heavy_metal_man said:
Try the command
fastboot reboot-bootloader
To get out of ruu mode.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
No man, It brings me back to the ruu mode, i damaged my hboot
Guys, I will try this tool to encrypt the ruu.zip with the modified CID, i'm installing a linux virtual machine.. I will keep you informed...
http://forum.xda-developers.com/showthread.php?t=2199638
Bad news
I re-encrypted a ROM, but I have the same issue about the signature..
"The leading 256 bytes is the signature of the zip file, you'll need to disregard it. There's no way we can sign the zip correctly without HTC's private key"
https://github.com/kmdm/ruuveal/issues/8
Sending to a Jtag repair center...
Cheers