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 )
Related
Hello togehter,
i found this to-do-list:
1. Flash a ROM and boot image based on 1.26 (e.g ARHD 2.1)
2. Clear fastboot cache
Code:
fastboot clear cache
3. Boot your phone
4. Charge you phone completely
5. Download stock recovery
6. Flash stock recovery
Code:
fastboot flash recovery endeavoru_recovery_signed.img
7. Relock bootloader
Code:
fastboot oem lock
8. Run 1.26 RUU
Click to expand...
Click to collapse
so not that big deal at all. i got the vodafone 1.26 ruu
but i dont find i 1.26.x rom. could i doo this from a 1.29 rom too? normaly the ruu should override everthing right?
one x got wlan problems, signal jumping like hell, nothing helps (reboot, reflash, router reboot, other router...). SO back to stock for warrenty exchance.
greetings and thanks
Hello neighbour..xD
Should be no problem like you posted it, flash 1.29 and you are good to go..
thanks
downloading ruu... takes 2 hours. to premium @ filefactory^^
greetings
ah, just one more question
which recovery to flash?
stock 1.26 for 1,26 ruu right?
or 1.29 for running 1.29 rom in the back
greetings
This video might help...
bigoliver said:
This video might help...
Click to expand...
Click to collapse
That's a good guide, but btw...
Make sure your phone is AT LEAST 50% charge.
Because, during the updating process, it will not charge with the usb cable and therefore not going to charge the phone.
If it shuts off during updating, you cannot charge the phone even if it's off.
NitNav said:
That's a good guide, but btw...
Make sure your phone is AT LEAST 50% charge.
Because, during the updating process, it will not charge with the usb cable and therefore not going to charge the phone.
If it shuts off during updating, you cannot charge the phone even if it's off.
Click to expand...
Click to collapse
Good advice, you should always flash with plenty of battery.
Sent from my HTC Desire using xda premium
holy.......
RUU won't run
i think its because the blank cid number.
what RUU will work? device just boot in fastbook mode, nothing else possible now
greetings and HELP
Havoc2k said:
holy.......
RUU won't run
i think its because the blank cid number.
what RUU will work? device just boot in fastbook mode, nothing else possible now
greetings and HELP
Click to expand...
Click to collapse
I had this problem, I was trying to flash the original rom that came with the phone, but, because I had, at some point, officially ota updated the software I needed to revert back to the updated software. Hope this helps,
Oliver
Sent from my HTC Desire using xda premium
sy i dont get the point.
so what to do?
phone was running at 1.29.xx (latest FW from htc)
ruu is for 1.26.xx
recovery img is 1.26 too
can't flash anything right now cause the phone is relocked now
greetings
edit: fault msg:
Error [131] CUSTOMER ID ERROR
The ROM Update Utility cannot update your Android phone
please get the correct rom update utility and try again.
Click to expand...
Click to collapse
so its because the CID, but hmm what to do now :/
greetings
Havoc2k said:
sy i dont get the point.
so what to do?
phone was running at 1.29.xx (latest FW from htc)
ruu is for 1.26.xx
recovery img is 1.26 too
can't flash anything right now cause the phone is relocked now
greetings
Click to expand...
Click to collapse
When RUU 1.26 didn't work for me I tried RUU 1.28 (latest three branded RUU) And that worked.
I think you might be trying to flash the wrong RUU you need the latest version of your RUU that you have previously ran on your phone.
It sounds to me from your posts that you need the 1.29 RUU but it's your responsibility to make sure you use the correct RUU.
Sent from my HTC Desire using xda premium
Does any one know How I can install JB? I have unlocked and installed custom room. I relocked the phone but can't return to stock as there is no ruu available for my software version. I have the ota update on my phone but when I try to install it doesn't work.
Ideas?
Sent from my HTC One X using xda premium
Shelby5 said:
Does any one know How I can install JB? I have unlocked and installed custom room. I relocked the phone but can't return to stock as there is no ruu available for my software version. I have the ota update on my phone but when I try to install it doesn't work.
Ideas?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
you have to wait for the RUU or a Nandroid Backup of that stock rom
matt95 said:
you have to wait for the RUU or a Nandroid Backup of that stock rom
Click to expand...
Click to collapse
I have been waitng close to 2 months already. Thanks for responding anyway. Is there any other alternative?
Sent from my HTC One X using xda premium
There is a thread in here (it's quite new) somewhere on backups for different versions, which you might be able to install.
There is another thread on using an older RUU, extracting the ROM and boot.img, and installing them (I think).
Ultimately you want to get to 2.17, 2.18 was unofficial, so I suspect the OTA will only apply to 2.17.
Edit: I might be making that up, maybe 2.18 was official.
BenPope said:
There is a thread in here (it's quite new) somewhere on backups for different versions, which you might be able to install.
There is another thread on using an older RUU, extracting the ROM and boot.img, and installing them (I think).
Ultimately you want to get to 2.17, 2.18 was unofficial, so I suspect the OTA will only apply to 2.17.
Edit: I might be making that up, maybe 2.18 was official.
Click to expand...
Click to collapse
I think The OTA is official, its from HTC and i downloaded to my phone ota. It was my phone that adviused me on the update The version is 3.18.751 on the update. Every time i try to load the update it goes to the fastboot screen and wont let me install the update.
2.18.751 is official, release not long after 2.17 OTA. It contained small fixes for taiwan chungwa's One X. If I am not wrong, it doesn't update hboot and recovery version, affecting ROM only.
For OP:-
Best options was using your nandroid backup.
OR
Grab the firmware.zip inside 3.14.751.20's OTA, then flash it like how they did to .401.
OR
There are a custom RUU that can help you convert your phone to taiwan unbranded CID (709) then receive 3.14.709.20 OTA. Your CID will change to HTC_621. You will need unlock bootloader for this method.
HebeGuess said:
2.18.751 is official, release not long after 2.17 OTA. It contained small fixes for taiwan chungwa's One X. If I am not wrong, it doesn't update hboot and recovery version, affecting ROM only.
For OP:-
Best options was using your nandroid backup.
OR
Grab the firmware.zip inside 3.14.751.20's OTA, then flash it like how they did to .401.
OR
There are a custom RUU that can help you convert your phone to taiwan unbranded CID (709) then receive 3.14.709.20 OTA. Your CID will change to HTC_621. You will need unlock bootloader for this method.
Click to expand...
Click to collapse
Great thank for that info. That finally gives me something to try to make it work.
HebeGuess said:
Grab the firmware.zip inside 3.14.751.20's OTA, then flash it like how they did to .401.
.
Click to expand...
Click to collapse
Can you please expand a little bit further on this or provide me a link? I'm in this exact same case with no luck just yet Thanks!
mudito said:
Can you please expand a little bit further on this or provide me a link? I'm in this exact same case with no luck just yet Thanks!
Click to expand...
Click to collapse
Ok i have successfully upgraded. Mudito i used the tool here
http://forum.xda-developers.com/showthread.php?t=1604439
I flashed the recovery image off the OTA update. Im now in 3.14.751.20
I will say i made an error and luckily i didn't brick my phone.
Bacislly i followed the steps from the link above on the video placeing the the official images in the relevant folders instead of custom ones.
I didn't place the correct files on my SD so after doing perm root the phone was locked on a screen(never seen it before so dont know what to call it). Then i realised i hadn't put the files on sd luckily when i reset the phone it turned on and then i downloaded the update and it installed perefctly.
but the used the official recovery/ boot images etc.
android 4.1.1
sense 4+
baseband 5.1204.162.29
Hey, I got the EXACTLY same problem as you do - although I'm not using a custom rom, just messed abit with mine too much (CWM + root, something messed up so I can't update even going back to stock recovery), so can you please explain step by step what I should do to get the JB update?
Thanks alot!
(and will this make my phone able to get the next update if one will get out too? I mean - is it stock rom?)
noodlez04 said:
Hey, I got the EXACTLY same problem as you do - although I'm not using a custom rom, just messed abit with mine too much (CWM + root, something messed up so I can't update even going back to stock recovery), so can you please explain step by step what I should do to get the JB update?
Thanks alot!
(and will this make my phone able to get the next update if one will get out too? I mean - is it stock rom?)
Click to expand...
Click to collapse
Ok do you have 2.18.751? If you have this version I can give you the update as I have it on pc. Its 3.14.751.20. I just have to work out how to upoad it to xda site.
I woulnt follow my steps exactly as I'm lucky I didn't damage my phone.
The up date has firmware.zip that contains boot.img, recovery.img etc. Follow the instructions Hansen toolkit video on the link. I flashed the HTC recovery and boot image. Then went to perm root my phone. It was on a screen I don't know what to call and was stuck there as I didn't flash other recoveries like cwm etc.. I then rebooted by power&vol and downoaded update again and it instaled. Note my phone automatically advised of the OTA if yours hasn't then there is something different.
I would highly recommend NOT to following my steps. Follow tookit video. That should get you there.
It is the official update from HTC so it should allow future updates.
Sent from my HTC One X using xda premium
Thanks guys.
Finally I went the other way... I was trying so hard to do this that soon I realized that I will be getting a custom ROM in a matter of time. But I usually use Stocks Modded ROMs so I did this.
Relocked the boot loader.
Flashed Firmware.zip from the OTA 3.14.751 from OTA.ZIP file. My word here is USE THE FIRMWARE FOR YOUR CID!!! ONLY THAT ONE
Flashed CWM 5.8.4.0 Recovery (i had an old one).
Downloaded Custom ROM (tried 2 in two days so far. same procedure, ARHD and InserCoin)
Flashed Boot.img from that custom ROM.
Went to Recovery, install ZIP from SDcard. and Flashed the custom ROM.
Preety Neat I must say.
Enjoying performance from JB... Photo CAM is insanely FAST
Thanks to Everyone. XDA Is a great place to find info but it could be messy some times.
Shelby5 said:
Ok do you have 2.18.751? If you have this version I can give you the update as I have it on pc. Its 3.14.751.20. I just have to work out how to upoad it to xda site.
I woulnt follow my steps exactly as I'm lucky I didn't damage my phone.
The up date has firmware.zip that contains boot.img, recovery.img etc. Follow the instructions Hansen toolkit video on the link. I flashed the HTC recovery and boot image. Then went to perm root my phone. It was on a screen I don't know what to call and was stuck there as I didn't flash other recoveries like cwm etc.. I then rebooted by power&vol and downoaded update again and it instaled. Note my phone automatically advised of the OTA if yours hasn't then there is something different.
I would highly recommend NOT to following my steps. Follow tookit video. That should get you there.
It is the official update from HTC so it should allow future updates.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Shelby5, Can you please send me the link to the video? and yes, that IS my version, and I've been notified of the update - but because of my modded rom couldn't install it.
JB requires a newer hboot, no? mine currently has 1.12, and I've understood that it requires 1.33, so does it cover that too?
Thanks!
about the ZIP file - is it the one that your device downloaded OTA to install? cause if so - I got that one. and if not - I'd appreciate if you can upload it even to dropbox or something for the day and tomorrow so I can download it
Noodlez I can do it for you later Today. Ill msg you later with details.
Sent from my HTC One X using xda premium
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.
Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
yasha.sinitski said:
Hey folks.
So I was running CM11 on my Rogers M8 for quite some time, until I decided to flash Sense based roms. Uh-oh, Wifi doesnt work anymore. Decided to do some digging, and realized that it's due to my older firmware which needs to be updated.
I followed the guides, and did the following to prepare:
Flashed stock recovery. I know it worked due to the triangle and explamation mark.
Relocked the bootloader through ADB commands.
Proceeded to ADB "fastboot getvar all" to see my current version.
That's when I saw that right next to the "version-main" it's empty. No numbers. Consequently, I haven't been able to flash any firmwares since it never passes any checks.
I am S-ON (firewater didnt work), CID is ROGER001, and completely exhausted. Please, help me figure this out.
Click to expand...
Click to collapse
The Bootloader 3.18. tells you, you have 2.x firmware
So what is stopping me from flashing new firmware each time?
yasha.sinitski said:
So what is stopping me from flashing new firmware each time?
Click to expand...
Click to collapse
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
xunholyx said:
Not being SuperCID?
What do you mean each time?
You can flash stock firmware without going back to stock. As long as your MID and CID match.
Just download stock rogers firmware, rename and install it in hboot, or use RUU mode in fastboot.
Click to expand...
Click to collapse
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
yasha.sinitski said:
You see, I tried that. I downloaded stock rogers firmware, and ADB just spits out an error message saying that something doesnt match up. If I recall, it was error 12.
Click to expand...
Click to collapse
It might be because you have a modified /system partition. Do you use Xposed?
xunholyx said:
It might be because you have a modified /system partition. Do you use Xposed?
Click to expand...
Click to collapse
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
yasha.sinitski said:
No. My endgoal is to simply be running Roger's stock rom with full functionality. I just cant figure out how to get to that. I dont care about getting OTAs.
Click to expand...
Click to collapse
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
EDIT: I'm mistaken here. You need them unzipped. PM sent.
For others with the same issue of returning to Canadian stock, go to this thread for links and a guide on how to do so.
xunholyx said:
Here are all the files to download to go back to stock rogers. Download and zip them, then use TWRP to flash. Afterwards you will just have to install a stock recovery to be fully stock, but if you don't carte about OTAs, stick with TWRP. That way you can make nandroid backups.
Click to expand...
Click to collapse
Are you going to post links? No matter what you do, I cant thank you enough for your help.
yasha.sinitski said:
Are you going to post links? No matter what you do, I cant thank you enough for your help.
Click to expand...
Click to collapse
Whoops!
Here ya go.
xunholyx said:
Whoops!
Here ya go.
Click to expand...
Click to collapse
Doing all that right now. I'll update how it goes.
yasha.sinitski said:
Doing all that right now. I'll update how it goes.
Click to expand...
Click to collapse
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Otherwise you brick your phone.
That the firmware number is not showing is not critical i think. Its a symtom of some roms.
I flashed the newest firmware to my m7, number was showing. Then i flash Viper 7.0.1 and after that, my number is hidden.
But everything works, so i think its not critical.
Roma80 said:
The getvar tell me, you are S-ON.
But you need S-OFF to flash a new firmware.
Click to expand...
Click to collapse
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
BerndM14 said:
Not true, you can flash the latest firmware if you're S-ON, the only "catch" is that it MUST be the correct MID and CID(That's in Firmware.zip) else it won't flash.
It's also the only way for an S-ON device to update it's Radio, as it won't be able to manually flash Radio's if it's not S-OFF.
Of course you need to relock your bootloader to do this with S-ON. So get stock recovery also, of course make backups of everything you need backed up as relocking it might erase all data.
Click to expand...
Click to collapse
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Roma80 said:
Oh okay, good to know.
I read wrong / missunderstood on other thread.
Click to expand...
Click to collapse
Yeah, Mike's guide has some good info. A lot of misinformation out there about some stuff.
He also has an excellent blog with plenty of info/resources if you're bored and what to read up on some stuff. Great site.
Android Revolution HD :good:
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.