I wanted to flash LeeDroid's rom. After I flashed the boot image I realized that I haven't put the rom into the root of the phone's storage! silly me. I tried rebooting the system but it won't boot. Then I tried the unbrick methods on the forum but found no luck. At last I tried relocking it and restore it using RUU but it still won't work! It is saying that I got the wrong version of RUU, but where can i find the RUU for 1.28? Hope someone can help!!
chowdyg said:
I wanted to flash LeeDroid's rom. After I flashed the boot image I realized that I haven't put the rom into the root of the phone's storage! silly me. I tried rebooting the system but it won't boot. Then I tried the unbrick methods on the forum but found no luck. At last I tried relocking it and restore it using RUU but it still won't work! It is saying that I got the wrong version of RUU, but where can i find the RUU for 1.28? Hope someone can help!!
Click to expand...
Click to collapse
What country are you in, which network are you on and did you buy your phone sim free?
If you go into fastboot mode and then boot into CWM using the command:
fastboot boot <CWM img file>.img
You'll then be able to use adb to push the rom zip onto your device which you can then flash with CWM.
If the RUU says you have the wrong version you probably have the RUU for another region/carrier.
It's pretty much impossible to permanently brick the one x (without s-off) so don't worry, you'll get it working eventually.
Thanks man. I am in Hong Kong and i am pretty sure it is sim free. after I tried running the RUU i have relocked the bootloader. for some reason I can't even get into recovery right now! When I try the RUU it saids the image version is 1.28.708.10 and I get error140
chowdyg said:
Thanks man. I am in Hong Kong and i am pretty sure it is sim free. after I tried running the RUU i have relocked the bootloader. for some reason I can't even get into recovery right now! When I try the RUU it saids the image version is 1.28.708.10 and I get error140
Click to expand...
Click to collapse
Which RUU did you download?
rogersnm said:
Which RUU did you download?
Click to expand...
Click to collapse
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2
I guess it is not the right one is it
chowdyg said:
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2
I guess it is not the right one is it
Click to expand...
Click to collapse
You can't install the 1.26 RUU after you've updated hboot with the 1.28 OTA.
Try installing this RUU: http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257077_signed.exe, it's the same region but a newer version.
Flash the stock 1.28 recovery image and relock your bootloader before trying to install the RUU.
The 1.28 recovery image can be found here: http://hoxroms.serveftp.com/Asia_1.28_RUU/recovery_signed.img
rogersnm said:
You can't install the 1.26 RUU after you've updated hboot with the 1.28 OTA.
Try installing this RUU: http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_257077_signed.exe, it's the same region but a newer version.
Flash the stock 1.28 recovery image and relock your bootloader before trying to install the RUU.
The 1.28 recovery image can be found here: http://hoxroms.serveftp.com/Asia_1.28_RUU/recovery_signed.img
Click to expand...
Click to collapse
Thanks so much!!
but i have already relocked the bootloader without flashing the recovery image ... would that make a difference?
If the RUU runs successfully then don't worry about it, if it throws another error then flash the stock recovery and try again.
rogersnm said:
If the RUU runs successfully then don't worry about it, if it throws another error then flash the stock recovery and try again.
Click to expand...
Click to collapse
Thanks again. but how do i do it with the bootloader locked
chowdyg said:
Thanks again. but how do i do it with the bootloader locked
Click to expand...
Click to collapse
Just unlock it by running "fastboot flash unlocktoken Unlock_code.bin" like you did before and then relock it after
rogersnm said:
Just unlock it by running "fastboot flash unlocktoken Unlock_code.bin" like you did before and then relock it after
Click to expand...
Click to collapse
now it is saying error 170. whenever i try to flash something it just says waiting for device
chowdyg said:
now it is saying error 170. whenever i try to flash something it just says waiting for device
Click to expand...
Click to collapse
Disconnect and reconnect your phone, reboot your phone and your pc, try again.
ps. Make sure you relocked your bootloader
rogersnm said:
Disconnect and reconnect your phone, reboot your phone and your pc, try again.
ps. Make sure you relocked your bootloader
Click to expand...
Click to collapse
Thank you so much!! problem solved!!
Related
Hi Guys, I've been using Custom Roms a long time so It came... Jelly Beans finally.
I tried to go back to stock...basically I installed a NANDROID compatible with my system...everything went fine till the last update JB...
I downloaded it...OK ,
After INSTALL NOW...It reboots the phone to install...After that, shows a message and go back to BOOTLOADER...I cannot see well the message... What can I do?? It's driving me crazy
Logo HTC and this message...after that...goes back to bootloader...What Happened??
QUOTE
"This build if for development purposes only
do not distribute ourside of HTC
without HTC a writter permission
Failure to comply may
lead to legal action"
blankfile99 said:
Hi Guys, I've been using Custom Roms a long time so It came... Jelly Beans finally.
I tried to go back to stock...basically I installed a NANDROID compatible with my system...everything went fine till the last update JB...
I downloaded it...OK ,
After INSTALL NOW...It reboots the phone to install...After that, shows a message and go back to BOOTLOADER...I cannot see well the message... What can I do?? It's driving me crazy
Logo HTC and this message...after that...goes back to bootloader...What Happened??
QUOTE
"This build if for development purposes only
do not distribute ourside of HTC
without HTC a writter permission
Failure to comply may
lead to legal action"
Click to expand...
Click to collapse
you installed an OTA?
I'm using a Stock from a recovery Nandroid, not mine but the same CID 044... I guess I shold go back to RUU...but I've tried without any success
I can't even use my RUU file...donno why... I have this file: (RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed) and It works, not now but It used it once...do you have a suggestion so I can use it again??
blankfile99 said:
I can't even use my RUU file...donno why... I have this file: (RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.29.707.11_Radio_1.1204.105.14_release_260743_signed) and It works, not now but It used it once...do you have a suggestion so I can use it again??
Click to expand...
Click to collapse
you are on JB now and you can't run ICS RUUs, you can't downgrade...
matt95 said:
you are on JB now and you can't run ICS RUUs, you can't downgrade...
Click to expand...
Click to collapse
I'm not...I'm on 2.17 yet...JB update does not install...that's the main problem
and I have noticed that NO MATTER I CHANGE...IT WONT CHANGE THIS VERSION... OMG
tks man!
You need to relock your bootloader (if you haven't already) and run THIS RUU.
The problem is that the version of software you're running (2.17) is newer than the RUU you're trying to install (1.29). you can't revert to an older RUU. you can only flash the same version or newer.
Once you've flashed the RUU, you'll be able to download and install the JB OTA.
Sentinel196 said:
You need to relock your bootloader (if you haven't already) and run THIS RUU.
The problem is that the version of software you're running (2.17) is newer than the RUU you're trying to install (1.29). you can't revert to an older RUU. you can only flash the same version or newer.
Once you've flashed the RUU, you'll be able to download and install the JB OTA.
Click to expand...
Click to collapse
Thank you very much man, You renew my faith!!
It will work like a FORMAT SYSTEM with the same Rom?
I'll keep in touch!!
Also, this may sound silly but did you reflash stock RECOVERY?
blankfile99 said:
Thank you very much man, You renew my faith!!
It will work like a FORMAT SYSTEM with the same Rom?
I'll keep in touch!!
Click to expand...
Click to collapse
No worries, let us know how you go, and don't forget the Thanks button.
ArmedandDangerous said:
Also, this may sound silly but did you reflash stock RECOVERY?
Click to expand...
Click to collapse
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Well I am currently running Team Venom's Viper but I have HBOOT 1.31. My device's CID is HTC_J15.
I have checked the list of RUUs but unfortunately all of them are older than the version I need, which has to be 3+.
Does anybody know if there's an RUU available for my device? It is an ubranded WWE version, 401 if I remember correctly.
ArmedandDangerous said:
Also, this may sound silly but did you reflash stock RECOVERY?
Click to expand...
Click to collapse
I'm using the same as the NANDROID, taken from it...right?
Sentinel196 said:
No worries, let us know how you go, and don't forget the Thanks button.
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Click to expand...
Click to collapse
That's all I need... I'll give my feedback later.
Sentinel196 said:
No worries, let us know how you go, and don't forget the Thanks button.
You don't need stock recovery to flash an RUU. You just need a locked or relocked bootloader, and a less or equal main-version.
Once you run an RUU, you will have stock everything(including recovery) and will be able to install whatever OTAs are available.
Click to expand...
Click to collapse
In my experience the 2.17.707.xx RUU Asia WWE does not work properly. It does its thing installing everything, relocks the bootloader but somehow it does not reflash the recovery. After 4 hours trying everything under the sun, I gave up and looked for a nandroid of 2.17 for CID_044 and restored from that, reflashed stock recovery and went to town with the OTA.
That's very strange, no such problem when I did the same thing. You'd think it would throw an error or something if a component of the image failed to flash.
Glad you managed to figure it out!
Did you run it when your bootloader was unlocked? Maybe that's the problem? I ran it with the bootloader relocked and didn't ahve any problems. I was under the impression you couldn't run an RUU with an unlocked bootloader, but haven't tried it myself.
Refer custom to stock thread posted earlier. Go through step by step procedure. It will help u to be on stock Rom. After that flash any Rom suitable to your CID only
http://forum.xda-developers.com/showthread.php?t=1859714
Hit Thanks if u like.
Sent from my HTC One X using xda app-developers app
Got It guys!!
What I did... NOTHING else...
Only Reboot the phone...wait to initialize completely, then reboot again, when came a little update about 1.25mb...installed and reboot...after that...JB update installed correctly.
If someone else needs...Someone like me who relocked the phone waiting for JB and Has problems
1. Unlock Phone
2. fastboot flash recovery recovery.img (from nandroid 2.17)
3. fastboot flash boot boot.img (from nandroid 2.17)
4. fastboot erase cache
5. restart bootloader (I like to do this way)
6. Install RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed on windows
7. Wait to boot completely, then restart phone.
8. Update Software ...a little update came before JB. (about 1.25mb)
9 Reboot phone.
10. Update Software... finally to JB.
Thanks guys!
Sentinel196 said:
That's very strange, no such problem when I did the same thing. You'd think it would throw an error or something if a component of the image failed to flash.
Glad you managed to figure it out!
Did you run it when your bootloader was unlocked? Maybe that's the problem? I ran it with the bootloader relocked and didn't ahve any problems. I was under the impression you couldn't run an RUU with an unlocked bootloader, but haven't tried it myself.
Click to expand...
Click to collapse
The RUU ran with no problem, and it relocked my bootloader, but it still did not receive any OTAs. So I had no choice but to do a nandroid restore instead (recommended anyway )
Hi, I'm heading back to stock JB Sense from the original JB Maximus rom (which worked very well). I relocked in fastboot and went to flash original RUU (3.14.401.31) and I got the error message to use the correct RUU. My cid is HTC__001, it's from Clove UK. Do I need to change the HBOOT? It's from the first Maximus JB rom. It's just booting to the bootloader now. Thanks for any help!
Do this:
fastboot getvar version-main
and post the result here...
vin4yak said:
Do this:
fastboot getvar version-main
and post the result here...
Click to expand...
Click to collapse
3.09.401.100
Thanks very much!
Firs you need to update your firmware to 3.14.401.31 with Hboot 1.39..
Download (firmware): http://www.androidrevolution.nl/downloader/download.php?file=3.14.401.31.zip
And then run this RUU:
http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/
Hi, thanks very much, that was the RUU I used but I'll try with that firmware and report back. Cheers for the prompt help!!
Hi, I've downloaded the firmware a few times but when I try to flash it I'm getting "cannot determine image filename for 'firmware.zip'
I moved the firmware download to my fastboot folder and renamed it firmware.zip. Then I did "fastboot flash firmware.zip" < EDIT YEP THAT was the problem
Thanks again!
Honestly at this point I'd just even go back to Maximus 4.1 at this point, but those threads all disappeared.
EDIT: I got the firmware updated, now going for the RUU
Got the RUU installed, thanks very much vin4yak. Now the screen is flashing (flickering) on the sides once it booted, do you have any idea what I can do about that? I'm happy to install a different Sense rom if that helps.
Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Thanks in advance
Froschfinger
Froschfinger said:
Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Click to expand...
Click to collapse
That's what I got the first time I tried to run the RUU, before flashing the new firmware. You may need firmware with a higher HBOOT to use this JB RUU. Once I flashed the firmware above, the RUU in this thread worked fine. I'm having some flashing now but heck, I had that when my phone was stock when I first got it, heh. I remember that issue now!
otarinz said:
Got the RUU installed, thanks very much vin4yak. Now the screen is flashing (flickering) on the sides once it booted, do you have any idea what I can do about that? I'm happy to install a different Sense rom if that helps.
Click to expand...
Click to collapse
Glad you sorted it out mate!
if you had just gone to stock to update... Then I will recommend you to use a custom sense rom if your attached to sense that much!
Use ViperX... It needs Hboot 1.31 at least..
Steps for flashing are the same as any other rom...
1. Wipe Data..Wipe Cache...Wipe Dalvic Cache... Or use Super Wipe Script(Recommended) : https://www.dropbox.com/s/0y31poo1kiaif4y/Super wipe script.zip
2. Flash rom. Flash Patch. (Check ViperX Thread)
3. Reboot.
Froschfinger said:
Hey there,
similar problem: I have 3.09.401.100 as well, flashed the firmware successfully, relocked, tried to run the appropirate RUU but got a signature error (132) while it tries to send the it to the phone. I have the appropriate CID HTC___102 for the RUU etc. My HBOOT is 1.23.0000 - could that be a problem with the RUU? Any insights?
Thanks in advance
Froschfinger
Click to expand...
Click to collapse
You first have to update your firmware... Download this : http://goo.gl/M0hLq
and then run the ruu...
Hey there,
it sounds as if the HBOOT is in fact my problem. Quick question: How exactly did you flash the firmware, especially the HBOOT? I flashed the boot.img and recovery.img via command since I have no SD card access, but this doesn't seem to have changed the HBOOT.
Thanks again
Froschfinger
Relock the bootloader:
"fastboot oem lock"
Reboot RUU:
"fastboot oem rebootRUU"
Flash the firmware:
fastboot flash zip firmware.zip
You might get an error the first time you do it... try again until you get a successful message.
After successful flashing...
Go to fastboot again,,,
Now if you want to install a custom rom, you need to flash custom recovery by unlocking the bootloader... or if you want to go full stock then run the RUU...
Hey vin4yak,
that was the missing piece in the puzzle. Flashing the whole .zip file. Finally I got it working - thank you so much!!!!
All the best
Froscher
I got a slight issue with my htc one x. My phone was switching off by itself anytime it wanted, so I decided to unroot it and send it back to vodafone. I did follow Video " Unroot the htc one x :back to stock. Cursed4Eva" and did exactely what was said till applying RUU., my pc cant conect to my phone in bootloader mode, so I am stuck now with relocked phone....
Hboot 1.36
Firmware 4.1.1
Is there any other way how to install RUU???
korkis said:
I got a slight issue with my htc one x. My phone was switching off by itself anytime it wanted, so I decided to unroot it and send it back to vodafone. I did follow Video " Unroot the htc one x :back to stock. Cursed4Eva" and did exactely what was said till applying RUU., my pc cant conect to my phone in bootloader mode, so I am stuck now with relocked phone....
Hboot 1.36
Firmware 4.1.1
Is there any other way how to install RUU???
Click to expand...
Click to collapse
Is your phone recognized by the PC in fastboot?
matt95 said:
Is your phone recognized by the PC in fastboot?
Click to expand...
Click to collapse
Well when i conect usb cabel, phone says fastboot usb, but when i try to run ruu , phone has not found...
Hope, that is what u asked, coz i am still an android newbie
So is here anyone who could help me out????
korkis said:
So is here anyone who could help me out????
Click to expand...
Click to collapse
Have you installed the proper drivers on your PC?
Before installing RUU, try the command "fastboot devices" to see if it's recognizing your device.
Edit: You'll have to do that from a folder with fastboot in it or you have to have fastboot in your PATH info.
webpatrick said:
Have you installed the proper drivers on your PC?
Before installing RUU, try the command "fastboot devices" to see if it's recognizing your device.
Edit: You'll have to do that from a folder with fastboot in it or you have to have fastboot in your PATH info.
Click to expand...
Click to collapse
When I type fastboot devices this one appears : SH256W104119 Fastboot
korkis said:
When I type fastboot devices this one appears : SH256W104119 Fastboot
Click to expand...
Click to collapse
Looks like you are connected, so I don't know why the RUU cannot find your device.
I have tried it again, and Ruu found my phone, but bootloader error appeared:
The ROM update utility cannot update your android phone. Please get the correct ROM update utility and try again...
Any ideas where to get the corect one for vodafone UK???
webpatrick said:
Looks like you are connected, so I don't know why the RUU cannot find your device.
Click to expand...
Click to collapse
I can't find the appropriate RUU anywhere..... Is there any possibility to downgrade my phone from that state as it is now????
korkis said:
I can't find the appropriate RUU anywhere..... Is there any possibility to downgrade my phone from that state as it is now????
Click to expand...
Click to collapse
This thread might help.
http://forum.xda-developers.com/showthread.php?t=2135632
columbo67 said:
This thread might help.
http://forum.xda-developers.com/showthread.php?t=2135632
Click to expand...
Click to collapse
Yeah, but actually this one still seems like doesnt sort out my issue, I did find the right nandroid backup and I would flash it in recovery if I had any..
Don't forget that right at the beginning I was about to go for stock Rom, so I did flash stock recovery and I locked the bootloader.... So the question now is if I can flash again some recovery (which one) while my bootloader is relocked. Or should I go ahead and do relock the bootloader again and than flash recovery...? Sorry but I am still a bit lost, and I dont wanna my HOX to become a brick.... Thx
korkis said:
Yeah, but actually this one still seems like doesnt sort out my issue, I did find the right nandroid backup and I would flash it in recovery if I had any..
Don't forget that right at the beginning I was about to go for stock Rom, so I did flash stock recovery and I locked the bootloader.... So the question now is if I can flash again some recovery (which one) while my bootloader is relocked. Or should I go ahead and do relock the bootloader again and than flash recovery...? Sorry but I am still a bit lost, and I dont wanna my HOX to become a brick.... Thx
Click to expand...
Click to collapse
Looks like you can't go back to stock, there is no RUU, no nandroid backup.
You could still ask if somebody is willing to post a nandroid backup for your CID and version, and in the meanwhile you can unlock your bootloader again, flash a custom recovery and flash a ROM (+boot.img) of your choice that fits your hboot version.
webpatrick said:
Looks like you can't go back to stock, there is no RUU, no nandroid backup.
You could still ask if somebody is willing to post a nandroid backup for your CID and version, and in the meanwhile you can unlock your bootloader again, flash a custom recovery and flash a ROM (+boot.img) of your choice that fits your hboot version.
Click to expand...
Click to collapse
Thanks buddy, my phone is now sorted, back to stock and in case of anything I got 2.17 , 3.14 and also 4.17. Nandroid backups I really appreciate ur help
I've rooted my htc desire 820u(Indian Dual sim) running on Lollipop 5.0
Then I found MIUI 7 ROM in XDA site. So I tried to flash it after wiping all the data-system-cache-internal storage and it didn't go well and ended up with boot failure. But before doing so, I backed up all the data using TWRP (Boot-System-Data). So when i tried to restore the data, the process is finished successfully.
But when the phone is rebooted I got several error messages like "system ui crashed", "htc dot view crash" "package installer help crash". And notification bar and soft toggle keys are gone. Nothing is accessible now. I tried recovering the same 3-4 times. But the same happened every time. What should I do now?
PLEASE HELP ME.
Try to flash the Ota again. And than restore your backup. You will find the Ota zip in the development section. Dont try to flash KK over Lollipop. You cant downgrade.
Or try a factory reset after restoring, maybe it helps.
Oel said:
Try to flash the Ota again. And than restore your backup. You will find the Ota zip in the development section. Dont try to flash KK over Lollipop. You cant downgrade.
Or try a factory reset after restoring, maybe it helps.
Click to expand...
Click to collapse
I tried Factory reset after restoring but didn't work. So can I flash ota zip in unlocked bootloader? how to flash it.
Thanks a lot
Oel said:
Try to flash the Ota again. And than restore your backup. You will find the Ota zip in the development section. Dont try to flash KK over Lollipop. You cant downgrade.
Or try a factory reset after restoring, maybe it helps.
Click to expand...
Click to collapse
Is it necessary to re lock the boot-loader before flashing ota zip file?
I have the same problem. When i try to flash the ota i get error 32 when bootloader is unlocked and then i tried locking the bootloader and doing the same and i get error 12 . Please help
Rahsam said:
I have the same problem. When i try to flash the ota i get error 32 when bootloader is unlocked and then i tried locking the bootloader and doing the same and i get error 12 . Please help
Click to expand...
Click to collapse
hi
Are you S-OFF ?
Are you sure about the ota is for your CID ?
Flashed it using RUU mode ( HTC Silver logo ) or just using fastboot only in bootloader ?
alikhoshi said:
hi
Are you S-OFF ?
Are you sure about the ota is for your CID ?
Flashed it using RUU mode ( HTC Silver logo ) or just using fastboot only in bootloader ?
Click to expand...
Click to collapse
Im sure tat the ota is for my CID and i did it with fastboot oem rebootRUU command and the silver logo appeared. But mine is s-on. How do i s-off??
Rahsam said:
Im sure tat the ota is for my CID and i did it with fastboot oem rebootRUU command and the silver logo appeared. But mine is s-on. How do i s-off??
Click to expand...
Click to collapse
I said S-OFF to do Super CID , if you sure about that no need to change your CID
Take a picture of Error
Rahsam said:
I have the same problem. When i try to flash the ota i get error 32 when bootloader is unlocked and then i tried locking the bootloader and doing the same and i get error 12 . Please help
Click to expand...
Click to collapse
Hey dont worry. If you are having locked bootloader, let it be.
Follow your original thread,
http://forum.xda-developers.com/desire-820/help/htc-820-toggle-buttons-notification-bar-t3239258
I hope this will work for you.
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
There is always a recovery installed. Either the stock one or the custom one. What does it do when you go to the recovery?
10rdan said:
Is it possible to have a working phone without a recovery installed ?
Unlocked bootloader, flashed twrp 3.0.1.0, phone wouldn't boot into recovery.
Relocked bootloader cause phone is s-on, ran 401 ruu but can't get into stock recovery but otherwise phone works ok
:banghead:
Click to expand...
Click to collapse
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files. When he flashed the ruu he could be seeing the exclamation mark that is normal as a warning before entering the stock recovery for which you need to push a volume and power button combo (don't know them heads up)
A possibility is to clear the cache and try to enter again (as this was a thingy on older HTC devices) or indeed as suggested at least to use the latest twrp available
Click to expand...
Click to collapse
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
10rdan said:
It doesn't get as far as red exclamation mark, that's what I was waiting for. I'll try the newer version of twrp tomorrow after I've unlocked bootloader again. Do you think the same unlock code will work again?
Click to expand...
Click to collapse
Yes i think it does work again. But that's a try and find out. There is always the possibility i could be wrong.
Edit :
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Mr Hofs said:
With s-on you need to relock the bootloader to use official signed ruu files.
Click to expand...
Click to collapse
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
jollywhitefoot said:
Sorry, but I believe this is misinformation, possibly residual to older HTC devices. I've heard this going back to the M7.
You need to be s-off to flash in download mode, but s-on can flash signed firmware and ruu's in RUU mode. I'm s-off so I can't test at the moment, but I'm about 99% that my information is correct.
S-on, you can only flash same or newer, though. You can't flash older firmware.
See post 19 here:
http://forum.xda-developers.com/htc-10/how-to/unlocked-official-ruu-t3378540/page2
I'm 100% that you can flash signed firmware package in ruu mode with bootloader unlocked and s-on.
Click to expand...
Click to collapse
That's new to me. Hopefully it isn't just tied to the developers edition then.
Thanks for the information
Mr Hofs said:
This is why i love s-off....no more relocking / unlocking the BL with also an increased chance of bricks. The BL isn't made to be relocked and unlocked over and over.
Click to expand...
Click to collapse
I'll bare that in mind, will unlock tomorrow again and try newer twrp. Only reason I relocked was to run ruu to get phone running again.
jollywhitefoot said:
Just fyi, but I'm pretty sure you can flash RUU in RUU mode with bootloader unlocked.
Phone works fine without recovery, but you can't take an ota, flash roms (custom recovery) or wipe data/cache.
I'd unlock again, and flash either stock recovery, run the RUU again, or flash TWRP 3.0.2-2. Why were you using such an old version in the first place? That's likely the cause of your issue in getting the phone to boot to TWRP.
Click to expand...
Click to collapse
Where can I find 3.0.2.2, can only see 3.0.2.0 on twrp site?
Cheers
Edit.... Found it. ?
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
10rdan said:
@jollywhitefoot
I've got stock recovery back on phone. Can you think of any reason, other than old version, as to why twrp wouldn't boot after flashing it ?
Will try again tomorrow.
Click to expand...
Click to collapse
I'm not exactly sure, but up until 3.0.2.2 Captain Throwback didn't even have the device and was working blind. I know he was trying different things to make it compatible with different variants, too, so in my mind that was a test build. I'm not sure why they have it on the downloads page. For me, I always download it from the download section of the twrp thread.