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 )
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
mayashoval said:
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
Click to expand...
Click to collapse
Have you tried relocking your bootloader? 'fastboot oem lock'
Also, maybe try flashing the stock kernel as well?
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
ArmedandDangerous said:
Also, maybe try flashing the stock kernel as well?
Click to expand...
Click to collapse
I'm hesitant about flashing a kernel, as I did not change the original stock one, and it feels too risky.
BenPope said:
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
Click to expand...
Click to collapse
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
mayashoval said:
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
Click to expand...
Click to collapse
I think the update to hboot requires it to be locked, your previous update was most likely ok with the hboot it was on.
mayashoval said:
I thought about that
Click to expand...
Click to collapse
Then look for a backup of your ROM version in the backup thread.
BenPope said:
Then look for a backup of your ROM version in the backup thread.
Click to expand...
Click to collapse
Sorry to be a noob but what do you mean? I thought I couldn't use a backup older than the one listed under "main version". Or am I confusing things?
Edit:
Can I install the most recent RUU?
INFOversion-main: 2.18.751.7.
latest RUU is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_ 2.1204.136.21_release_275588_signed.
Update: locking the phone did not help
I locked the phone, but the update still fails at the same location. The green bar expands for about 20 seconds, covering about a quarter of the bar, and the the red triangle appears.
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
sorry for being a noob
gffmac said:
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
Click to expand...
Click to collapse
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
mayashoval said:
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
Click to expand...
Click to collapse
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
exocetdj said:
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
Click to expand...
Click to collapse
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
mayashoval said:
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
Click to expand...
Click to collapse
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
exocetdj said:
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
Click to expand...
Click to collapse
don't really have a choice now...
downloading maXimus as per your recommendation (and because ADHD will take another 9 hours
You can restore an older backup, it's just like installing a custom ROM.
You might also be able to install a 2.17 RUU on 2.18, I'm not sure the hboot was updated. It's also possible to dissect an RUU and install the bits manually.
You have a few options.
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
Sorry did not find a solution. Ended up installing a custom rom, even though I wanted to keep using the stock one
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
I hope you did this the other way around......first flash the recovery and the relock the bootloader.....
But if you are on stock rom, kernel and recovery you do not have to relock the bootloader, it updates fine with a unlocked one.
My Desire was rooted before with a custom ROM. I've flashed back the original firmware, therefore the root was gone.
I followed the tutorial at this thread but I get stuck when I want to boot into recovery. The standard holding power and volume down procedure didn't work so I used ADB to boot into recovery. My device rebooted, but I get the red triangle and after that the 'Can't open /cache/recovery/command' error. I found out this means that the recovery isn't proparly installed.
When I use ADB to flash clockworkmod recovery Ithe message '< waiting for device >' remain standing. My Desire is in the HTC Sync modus, I see My HTC in windows device manager.
What is the next step to take? I've bricked an tablet before so I want to do the right thing.
Are you s-off? Also you use fastboot to flash the recovery, not adb.
chromium96 said:
Are you s-off? Also you use fastboot to flash the recovery, not adb.
Click to expand...
Click to collapse
Good point, I was forgotten all about s-off and on, it was a long time ago that I rooted my Desire.
I think I am not, beacause flashing the ROM of HTC also gives me a non-rooted phone. I'll check it this evening. Is using the tool from htcdev.com/bootloader the best way to become s-off?
musicfreak said:
Good point, I was forgotten all about s-off and on, it was a long time ago that I rooted my Desire.
I think I am not, beacause flashing the ROM of HTC also gives me a non-rooted phone. I'll check it this evening. Is using the tool from htcdev.com/bootloader the best way to become s-off?
Click to expand...
Click to collapse
No that will unlock your bootloader, not give you s off. Use revolutionary.
I found out I'm s-off, after I flashed clockworkmod recovery I used unrevoked to root. The rooting didn't succeed, I get the message 'failed to get root. Is your firmware to new?
I was on RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release, I have flashed an older stock ROM from the list on this page (1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984), and will try it again.
I'll let you know what the results are.
musicfreak said:
I found out I'm s-off, after I flashed clockworkmod recovery I used unrevoked to root. The rooting didn't succeed, I get the message 'failed to get root. Is your firmware to new?
I was on RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release, I have flashed an older stock ROM from the list on this page (1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984), and will try it again.
I'll let you know what the results are.
Click to expand...
Click to collapse
After you flashed recovery, there was no need to use unrevoked. All you had to do was boot into recovery and flash superuser.zip file. That would have rooted your existing rom.
However, what is your ultimate aim? If you want a ROM, you can simply flash the optimal hboot for the ROM (optional but recommended), boot into recovery, full wipe and flash the rom. The ROM will already be pre-rooted.
musicfreak said:
I found out I'm s-off, after I flashed clockworkmod recovery I used unrevoked to root. The rooting didn't succeed, I get the message 'failed to get root. Is your firmware to new?
I was on RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release, I have flashed an older stock ROM from the list on this page (1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984), and will try it again.
I'll let you know what the results are.
Click to expand...
Click to collapse
Don't use unrevoked. just flash the super su zip using cwm.
eddiehk6 said:
However, what is your ultimate aim? If you want a ROM, you can simply flash the optimal hboot for the ROM (optional but recommended), boot into recovery, full wipe and flash the rom. The ROM will already be pre-rooted.
Click to expand...
Click to collapse
You're completly right, I was somewhatconfused, it has been a while since I last flashed a ROM, I was to much happy with Oxy ZM. :silly:
Everything is ok now, I've flashed succesfully. Thanks.
Hey guys !
As the title suggests. What does that mean? and how do i revert to official locked ?
I have s-on and have rooted and installed twrp, and cwm afterwards. And decided to go back to stock( because the current methods of changing to s-off are not working) by flashing through cwm a RUU backup. And flashing the stock recovery afterwards. I have also declined root access when prompted by cwm after RUU install.
What can I do to return to 100% stock ?
After entering fastboot The first text is ***MODIFIED*** and at os there is blank space. I want to return my phone to out of the box state.
sherbibv said:
Hey guys !
As the title suggests. What does that mean? and how do i revert to official locked ?
I have s-on and have rooted and installed twrp, and cwm afterwards. And decided to go back to stock( because the current methods of changing to s-off are not working) by flashing through cwm a RUU backup. And flashing the stock recovery afterwards. I have also declined root access when prompted by cwm after RUU install.
What can I do to return to 100% stock ?
After entering fastboot The first text is ***MODIFIED*** and at os there is blank space. I want to return my phone to out of the box state.
Click to expand...
Click to collapse
You need S-OFF. With S-ON you cannot remove the 'MODIFIED' text.
XSL-FO said:
You need S-OFF. With S-ON you cannot remove the 'MODIFIED' text.
Click to expand...
Click to collapse
I don't just want to remove the text. I want the whole rom to be brand new and stock. And LOCKED
sherbibv said:
I don't just want to remove the text. I want the whole rom to be brand new and stock. And LOCKED
Click to expand...
Click to collapse
You must S-OFF. Remove texts, unroot, relock bootloader and go S-ON.
sherbibv said:
I don't just want to remove the text. I want the whole rom to be brand new and stock. And LOCKED
Click to expand...
Click to collapse
Doesn't matter, you can restore stock ROM until the cows come home. You won't be able to change the modified flag in the bootloader. You need S-OFF to change the text to "official" just like you'll need S-OFF to change the bootloader "locked" text to "Locked" and not "Relocked" if you relock the bootloader.
You will NOT be able to have it show the same way it was "out of box" if you do NOT have S-OFF.
So the only way is to buy the s-off service with 25$ right?
BerndM14 said:
Doesn't matter, you can restore stock ROM until the cows come home. You won't be able to change the modified flag in the bootloader. You need S-OFF to change the text to "official" just like you'll need S-OFF to change the bootloader "locked" text to "Locked" and not "Relocked" if you relock the bootloader.
You will NOT be able to have it show the same way it was "out of box" if you do NOT have S-OFF.
Click to expand...
Click to collapse
Sorry for the noob question, but what does modified imply ? What does it mean exactly?
sherbibv said:
Sorry for the noob question, but what does modified imply ? What does it mean exactly?
Click to expand...
Click to collapse
It means unlocked botloader and of course rooted. It means that you have tampered with the software.
XSL-FO said:
It means unlocked botloader and of course rooted. It means that you have tampered with the software.
Click to expand...
Click to collapse
But I can continue running like this without a problem right?
It won't cause any instability ?
And also, can I install OTAs?
sherbibv said:
But I can continue running like this without a problem right?
It won't cause any instability ?
Click to expand...
Click to collapse
Any at all. You can run it safely like this.
XSL-FO said:
Any at all. You can run it safely like this.
Click to expand...
Click to collapse
what about OTAs?
sherbibv said:
what about OTAs?
Click to expand...
Click to collapse
You will be able to recieve OTA's but if you want to install them you will need to go back to stock recovery. Easy. After OTA flash again a custom one.
XSL-FO said:
You will be able to recieve OTA's but if you want to install them you will need to go back to stock recovery. Easy. After OTA flash again a custom one.
Click to expand...
Click to collapse
I'm currently on stock recovery
sherbibv said:
I'm currently on stock recovery
Click to expand...
Click to collapse
It's ok. Keep it if you want.
sherbibv said:
I'm currently on stock recovery
Click to expand...
Click to collapse
Then you're fine.
Rooted, S-OFF, Modified status, none of those will prevent OTA updates. You MUST have stock reocovery and stock ROM for OTA updates i.e No changes to system files, no deleted apps, no xposed framework.
If all those are stock you can get and install OTA no problem. Don't even have to relock the bootloader for it.
BerndM14 said:
Then you're fine.
Rooted, S-OFF, Modified status, none of those will prevent OTA updates. You MUST have stock reocovery and stock ROM for OTA updates i.e No changes to system files, no deleted apps, no xposed framework.
If all those are stock you can get and install OTA no problem. Don't even have to relock the bootloader for it.
Click to expand...
Click to collapse
I had Xposed and still I was able to upgrade.
Thanks allot guys !
Have e great day ! :good:
sherbibv said:
Thanks allot guys !
Have e great day ! :good:
Click to expand...
Click to collapse
You too. Good luck.
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.