Related
have recovery twrp working, unlock boot loader, S-ON. Spent last three days reading post, threads etc.
clear cache, have atempted all on these threads that apply
http://forum.xda-developers.com/wiki/HTC_One_X , http://forum.xda-developers.com/showthread.php?t=1609190
Including the RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17.32.09.12_10.86.32.08L_release_262092_signed. Shows signature error on the RUU at end of install. Am I missing something? Any links to resolve this would be greatly appreciated. I'm guessing the RUU for cingular might be my problem there. Even flashed rom on twrp and not working.
Update: ROM trying to download was corrupt. Guess after rooting G2, viewsonic tab, HTC inspire just fine I should start to listen to the senior members about backups.
subarudroid said:
have recovery twrp working, unlock boot loader, S-ON. Spent last three days reading post, threads etc.
clear cache, have atempted all on these threads that apply
http://forum.xda-developers.com/wiki/HTC_One_X , http://forum.xda-developers.com/showthread.php?t=1609190
Including the RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17.32.09.12_10.86.32.08L_release_262092_signed. Shows signature error on the RUU at end of install. Am I missing something? Any links to resolve this would be greatly appreciated. I'm guessing the RUU for cingular might be my problem there. Even flashed rom on twrp and not working.
Click to expand...
Click to collapse
If you're attempting to RUU, need to re-lock bootloader. Enter the following command in fastboot to re-lock:
fastboot oem lock
ddebart2 said:
If you're attempting to RUU, need to re-lock bootloader. Enter the following command in fastboot to re-lock:
fastboot oem lock
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin
fastboot oem lock
fastboot erase cache
Thank you for the advise :highfive: tried it both ways just to see. Doesn't matter now anywho. Running my fav rom CM9 and don't care about the stock rom being byebye. at&t bloatware can suck it.
I've looked everywhere for something like this, and so far no one has experienced this.
Okay, so check this out:
I've already rooted and S-Off and SuperCID and all of that, the works. Had ViperROM XL and everything. I got curious to try out KarbonRom 4.4, and tried to flash it in TWRP, didn't work obviously, blah blah blah, short story is, I RELOCKED and installed the AT&T 3.18 RUU. At that point, TAMPERED was gone, and I had RELOCKED there instead, S-Off and SuperCID persisted.
I used the WinDroid Toolkit to originally root and S-Off my Evita. I tried it again. I succeeded in unlocking the bootloader, no problems there. When I go to flash TWRP on it, it says it succeeds. Now, here's when things get weird: I go to push Superuser, and at first it gave me all kinds of hassle, saying the toolkit wasn't detecting my phone, to saying it failed and to try again in a few moments. It was only until I booted back to stock and tried pushing Superuser that it gave me a success message and began to reboot to recovery. It's here that the phone fails to do this, every time. The screen goes black, and when plugged into my PC a Found New Hardware message pops up, asking me to search for drivers for QHSUSB_DLOAD, or something or other. I'm like, "no, that's not right." So after figuring out the 2-button reset to go back to HBOOT, I try to manually boot into recovery; no dice. Same results. So basically, I cannot access any recovery. Furthermore, my HBOOT says UNLOCKED and S-Off and CID-11111111, but TAMPERED is MIA. Not sure if that has anything to do with this, but I certainly did not have this problem the first time I unlocked everything. For your information, I'm on 2.14 HBOOT, 3.18 RUU. Thanks for any points in the right direction.
First thing, you didn't need to relock your bootloader to run the RUU, having s-off means that isn't necessary. Secondly, ditch the toolkit, it's unnecessary and causing problems.
I think you're possibly a bit confused about what you need to be doing. If your end goal was to flash a KitKat ROM why were you attempting to root the stock ROM? The tampered flag is missing from your bootloader because you don't have a custom recovery installed. Exactly which version of TWRP did the toolkit say it was installing? Hopefully all you need to do is flash a working recovery, then you can flash a ROM.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery.
Sent from my Evita
timmaaa said:
First thing, you didn't need to relock your bootloader to run the RUU, having s-off means that isn't necessary. Secondly, ditch the toolkit, it's unnecessary and causing problems.
I think you're possibly a bit confused about what you need to be doing. If your end goal was to flash a KitKat ROM why were you attempting to root the stock ROM? The tampered flag is missing from your bootloader because you don't have a custom recovery installed. Exactly which version of TWRP did the toolkit say it was installing? Hopefully all you need to do is flash a working recovery, then you can flash a ROM.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the swift reply, I'm gonna go ahead and give this a try. To answer your question, through trying to flash KarbonRom, I wiped and factory reset without backing anything up, silly, I know, but I live a little too dangerously I suppose. I tend to get to cocky with this stuff, through all the devices I've rooted and so on. After failing to flash it, I knew I was stuck, which is why I came to the conclusion the only way out was to revert to stock RUU. If there was anything else I could do, I wasn't thinking of it. In hindsight, I suppose I could have ADB Sideloaded Viper XL again. Also, I was unaware that I didn't need to relock the bootloader to install the stock RUU, this is news to me, so thank you for that. I'll reply again after trying your link.
EDIT: This worked, thank you again. You've made me wiser in the ways.
One thing I forgot to mention. The QHSUSB_DLOAD that your phone was showing up as when connected to your PC usually means that a device is bricked. So, under no circumstances should you use that toolkit ever again, because whatever it was doing wasn't good at all.
Sent from my Evita
timmaaa said:
One thing I forgot to mention. The QHSUSB_DLOAD that your phone was showing up as when connected to your PC usually means that a device is bricked. So, under no circumstances should you use that toolkit ever again, because whatever it was doing wasn't good at all.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the heads up, I'll keep it in mind. It seems the most reliable way to do this stuff is just do it yourself. I'm still green to the ways of adb and fastboot, I've always let one-clicks and toolkits do the work for me, but I'm learning that just doing it yourself is the most reliable method. Thanks again, man, your insight has always helped me out of tough situations.
Doing it yourself is definitely the most reliable method. It might seem daunting at first, but I can assure you it's totally simple, and once you've done it a couple times you'll see that. The manual way is the best way, hands down. A bonus is that it feels great to learn something and to have an extra bit if control over your device.
Sent from my Evita
Hello,
My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:
***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
Please help me, any help greatly appreciated!
Update:
The phone is working and has an update but it can not update on the device, is there a way i can get the downloaded OTA file on to my PC?
CoolAndroid1 said:
Hello,
My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:
***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
Please help me, any help greatly appreciated!
Click to expand...
Click to collapse
Hi,
What do you want to flash stock sense 6...??
greets
shivasrage said:
Hi,
What do you want to flash stock sense 6...??
greets
Click to expand...
Click to collapse
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks
CoolAndroid1 said:
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks
Click to expand...
Click to collapse
Ok
First I recommend you to unlock your bootloader.
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
I´m sorry but without get connectet via ADB or fastboot I think there is no chance to get it working again.
greets
shivasrage said:
Ok
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
With out get connectet via ADB or fastboot I think there is no chance to get it working again.
greets
Click to expand...
Click to collapse
I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8
CoolAndroid1 said:
I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8
Click to expand...
Click to collapse
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Ok, I will use a win 7 pc and let you know
shivasrage said:
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Click to expand...
Click to collapse
After i fix my drivers issue what can i do afterwards?
shivasrage said:
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Click to expand...
Click to collapse
I can now do the fastboot command from CMD
CoolAndroid1 said:
After i fix my drivers issue what can i do afterwards?
Click to expand...
Click to collapse
If you have a connection via fastboot you first have to decide what ROM you want, search for the matching firmware.
for example flash the latest firmware for M_4... 4.09.401.3 from here (new partition layout for e.g. sense 6):
https://docs.google.com/file/d/0BzCFBBNdXagdcEMybkdBME5iUE0/edit
After that flash TWRP 2.7.1.1 or philz and format all you have to try one of this recoverys should work.
Next push or sideload a ROM via adb I recommend you one them:
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
You can decide what you want rooted or not it doesn´t matter.
After installing with succsess try to reboot that´s it.
greets
I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?
To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)
Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)
Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good
As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.
If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.
jollywhitefoot said:
I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?
To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)
Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)
Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good
As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.
If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.
Click to expand...
Click to collapse
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either
CoolAndroid1 said:
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either
Click to expand...
Click to collapse
Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.
You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.
Are you getting this error when you attempt to unlock?
FAILED (remote: unlock token check failed)
jollywhitefoot said:
Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.
You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.
Are you getting this error when you attempt to unlock?
FAILED (remote: unlock token check failed)
Click to expand...
Click to collapse
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!
CoolAndroid1 said:
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!
Click to expand...
Click to collapse
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109
jollywhitefoot said:
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109
Click to expand...
Click to collapse
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!
CoolAndroid1 said:
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!
Click to expand...
Click to collapse
That's what i had to do when i first tried to root my phone. I was on Windows 7, but it was an old install and had all kinds of software on it that might have been preventing usb from working (iTunes, HTC Sync, some other random software, etc.) Sometimes, I would even have trouble connecting an external HD!
I ended up installing a clean copy of XP on an old computer that i now use strictly for flashing stuff to my phone.
New problem
I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?
CoolAndroid1 said:
New problem
I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?
Click to expand...
Click to collapse
I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.
jollywhitefoot said:
I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.
Click to expand...
Click to collapse
Hello,
I found an FUU for 4.4 Kitkat on the link you posted earlier, It does all the necessary actions with no failures and completes with a Congrats screen but the firmware is the same?
Hi!
I have a serious problem here. I offered to try and fix a friend's HTC One SV (4.2.2 Jelly bean). His battery died a few days ago, everything was working fine before that. He charged the phone and tried turning it on, but now it gets stuck on the HTC One welcome screen. (I've added a photo of the bootloader screen as well) The phone is not rooted. I've tried everything - clearing cache, recovery mode, factory reset.. Nothing helps. While researching for solutions, I stumbled upon a post where they said that if it were rooted, a custom recovery or RUU would be possible.
Since I am a bit of a newbie to rooting and hacking in general, then I'd like to ask if it's possible to root the damn thing now that it's not turning itself on properly and unlock the bootloader so I could flash a new ROM for example. Will it do any harm? Do you have any suggestions?
P.S.
Taking it back to the shop is an option and I am aware that warranty will void once it's unlocked. Despite this, we're willing to give it a try.
Thanks in advance.
I'm a bit confused, about that "Security Warning" on the picture. Not normal at all!
But if you really want to root, unlock your bootloader at htcdev.com.
Follow the steps, they provide a guide on their website, how to unlock.
old.splatterhand said:
I'm a bit confused, about that "Security Warning" on the picture. Not normal at all!
But if you really want to root, unlock your bootloader at htcdev.com.
Follow the steps, they provide a guide on their website, how to unlock.
Click to expand...
Click to collapse
Turned the phone on and went to the bootloader, the security warning is gone. That's good, I assume? What about this ***tampered*** part?
raisinette said:
Turned the phone on and went to the bootloader, the security warning is gone. That's good, I assume? What about this ***tampered*** part?
Click to expand...
Click to collapse
It seems the phone was unlocked/S-off already, and the one who locked it back to stock forgot to reset the Tampered flag.
old.splatterhand said:
It seems the phone was unlocked/S-off already, and the one who locked it back to stock forgot to reset the Tampered flag.
Click to expand...
Click to collapse
That can't be. He is the first owner and hasn't touched it in any way.
Tampered appears only after unlocking the bootloader.
Maybe a refurbished device!?!
old.splatterhand said:
Tampered appears only after unlocking the bootloader.
Maybe a refurbished device!?!
Click to expand...
Click to collapse
Ah, yes! I completely forgot about that. He had its power button repaired a few months, perhaps the tech guys did something with it.
Will this change anything?
No, not really. You need to unlock at htcdev.com.
Thats your first step.
old.splatterhand said:
No, not really. You need to unlock at htcdev.com.
Thats your first step.
Click to expand...
Click to collapse
I've been trying to do that for the past 2 days, but I'm stuck at step 5 - when I type in cmd ''fastboot oem get_identifier_token'', it says ''fastboot is not recognized as an interal or external command, operable program or batch file''. When I clicked on the fastboot.exe, it said something like adbwinapi.dll is missing. Downloaded that, the error was gone.
I've googled for solutions and so far none of them have worked. What could be wrong?
raisinette said:
I've been trying to do that for the past 2 days, but I'm stuck at step 5 - when I type in cmd ''fastboot oem get_identifier_token'', it says ''fastboot is not recognized as an interal or external command, operable program or batch file''. When I clicked on the fastboot.exe, it said something like adbwinapi.dll is missing. Downloaded that, the error was gone.
I've googled for solutions and so far none of them have worked. What could be wrong?
Click to expand...
Click to collapse
Do you have htc drivers installed on your pc?
old.splatterhand said:
Do you have htc drivers installed on your pc?
Click to expand...
Click to collapse
I have HTC Sync Manager. The drivers should come along with that, or not?
EDIT: Something odd happened - the phone started bootlooping, so I did a factory reset and then a red text appeared saying ''this build is for development purposes only.... etc''. I have not started unlocking the phone, it was simply connected to the usb while the bootloader was open. After the hard reset it does not bootloop anymore, but it is still stuck on the welcome screen. Thought it may be important.
I don't know, what happened to your device. But you need to solve this fastboot issue on your pc to proceed.
Also check, if the bootloader still is locked.
old.splatterhand said:
I don't know, what happened to your device. But you need to solve this fastboot issue on your pc to proceed.
Also check, if the bootloader still is locked.
Click to expand...
Click to collapse
I finally got my bootloader unlocked - it turns out Windows 8.1 was the problem. I couldn't manually install any drivers, so I refreshed my Windows back to 8.0, that helped.
Now, I'd like to root it and flash a custom rom to see if it helps me get out of the stuck HTC screen, but every rooting guide requires USB debugging to be enabled. How can I do that if I can't access the settings, because the phone won't turn on?
You can boot into bootloader, do that. Plug your phone to the pc and make sure your phone is in fastboot (usb) mode, not in hboot mode.
Download this three things:
- http://download.chainfire.eu/supersu
(copy to sdcard of your phone)
- the recovery from first post of this thread http://forum.xda-developers.com/showthread.php?p=41456540#post41456540
(copy to the folder on your pc where your fastboot.exe is)
this stock rom for your variant (or another rom for your variant http://forum.xda-developers.com/showthread.php?t=2512742
(copy to sdcard of your phone)
Follow the "How to" in recovery thread to flash recovery, then follow the "How to" in the rom thread to flash the rom from recovery and at last step flash supersu.zip from recovery.
old.splatterhand said:
You can boot into bootloader, do that. Plug your phone to the pc and make sure your phone is in fastboot (usb) mode, not in hboot mode.
Download this three things:
- http://download.chainfire.eu/supersu
(copy to sdcard of your phone)
- the recovery from first post of this thread http://forum.xda-developers.com/showthread.php?p=41456540#post41456540
(copy to the folder on your pc where your fastboot.exe is)
this stock rom for your variant (or another rom for your variant http://forum.xda-developers.com/showthread.php?t=2512742
(copy to sdcard of your phone)
Follow the "How to" in recovery thread to flash recovery, then follow the "How to" in the rom thread to flash the rom from recovery and at last step flash supersu.zip from recovery.
Click to expand...
Click to collapse
Thanks for taking the time to help, your instructions and advice has been indescribably useful
The phone is working fine again and it's all thanks to you.
Cool, you're welcome :laugh:
Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.
kunalrokz said:
Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.
Click to expand...
Click to collapse
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
Thanks I'll try it out shortly!!
kunalrokz said:
Thanks I'll try it out shortly!!
Click to expand...
Click to collapse
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp
I'm on the same boat as you... Any news?
wranglerray said:
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp
Click to expand...
Click to collapse
The unlock token wont flash gives me a permission error. I will post the exact error in a while.
OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
I tried your recommendation but to no avail. when I boot into the bootloader and send the fastboot command it gives me error "FAILED (remote: GetVar Variable Not found)" and when I do it in download mode it says okay and gets stuck on booting... the phone itself downloads the recovery and displays flash images success (1/1) but nothing else happens.
HOWEVER after sending that command I tried the unlock bootloader command and miraculously it WORKED! I got access to recovery!! I think that being in the download mode explicitly helped the bootloader recognize the unlock token.
zopostyle said:
I'm on the same boat as you... Any news?
Click to expand...
Click to collapse
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
Good to hear!
Cheers
Your neighbor to the south
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
sweet!
zopostyle said:
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...
Click to expand...
Click to collapse
stock recovery or twrp? you'll need to give more specifics...
OMJ said:
sweet!
stock recovery or twrp? you'll need to give more specifics...
Click to expand...
Click to collapse
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)
zopostyle said:
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)
Click to expand...
Click to collapse
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.
kunalrokz said:
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.
Click to expand...
Click to collapse
Hum, OK, thanks.
Yes, my bootloader is unlocked and I can flash recovery and boot.img successfully.
I'm at work right now at night I'm gonna try that fastboot -w option.
About the custom rom I've already tried leeDroid and MaximusHD but none of then booted.
What is this?
Failed to mount '/cota' (invalid argument)
AndrzejQ said:
What is this?
Failed to mount '/cota' (invalid argument)
Click to expand...
Click to collapse
An error that I received.
I got it working already.
i have the same problem. had you worked this out ? what's the solution ?
Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...
Void tracer said:
Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...
Click to expand...
Click to collapse
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.
MSMC said:
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.
Click to expand...
Click to collapse
I can't guarantee this will work, but try the following:
Use the spreadsheet here to find the latest RUU for your phone's CID and MID.
Rename the downloaded RUU to 2PZCIMG.zip
Move 2PZCIMG.zip to the root of your external SD card. If you don't have an external SD card you'll need to get one. If using a PC make sure to format the card as exFAT.
Follow the instructions at 'https://www.the custom droid.com/how-to-restore-htc-u11-stock-firmware/#Method-1-Flashing-RUU-in-Download-Mode' to flash the RUU to your phone.
Good luck!
EDIT: I don't why but XDA forums are filtering the string c u s t o m d r o i d (w/o the spaces)