So I restored stock system and boot, flashed the stock recovery and locked (relocked) the bootloader. (I'm S-On)
Is it normal that I still can't take OTA updates?
Which exact build number are you on and what were the exact steps you took to get back. Without those information it's hard to tell if there's an update available for your exact build number at all.
A fastboot getvar all would be helpful to pin down the issue if there is anyone at all.
Sent from my HTC 10 using XDA Labs
And you do not have to relock the bootloader to take OTA.
1: pure stock system image/backup
2: matching stock recovery
That's all you need
Mr Hofs said:
And you do not have to relock the bootloader to take OTA.
1: pure stock system image/backup
2: matching stock recovery
That's all you need
Click to expand...
Click to collapse
I flashed a pure stock backup from the stock tread aswel as the complient recovery. I can't get it to update OTA. It says that there is a problem in the storage. When I try to manually do the OTA trough the stock HTc recovery it gives a status 7 (Error in /sideload/package.zip). I've never had a custom kernal or rom on this device.
Riyan_Fransen said:
I flashed a pure stock backup from the stock tread aswel as the complient recovery. I can't get it to update OTA. It says that there is a problem in the storage. When I try to manually do the OTA trough the stock HTc recovery it gives a status 7 (Error in /sideload/package.zip). I've never had a custom kernal or rom on this device.
Click to expand...
Click to collapse
Hello, I had the very same error 7. I suppose it's because I restored both system & system image with twrp.
So I put the 1.30.401.1 zip ruu on my SD card , flashed back the according stock recovery and then installed the ruu. A few days later, the 1.80.401.1 ota showed up and the update process went just fine
Riyan_Fransen said:
I flashed a pure stock backup from the stock tread aswel as the complient recovery. I can't get it to update OTA. It says that there is a problem in the storage. When I try to manually do the OTA trough the stock HTc recovery it gives a status 7 (Error in /sideload/package.zip). I've never had a custom kernal or rom on this device.
Click to expand...
Click to collapse
I had the similar issue yesterday with my HTC 10 on T-Mobile. I was originally on viperone Rom with the 1.21 firmwarr. Heard that the 1.81 had rolled out. I relocked my bootloader thinking that would help. But it just completely messed things up. It prompted me to decrypt Android. It said my pin was correct but needed to format for corruption. I had to reboot several times before it actually formatted properly and brought me back into intial setup. My firmware was 1.81 but my build version in software was still reflecting 1.21. When trying OTA it said there was an error and corruption. So I found a twrp 1.81 backup, unlocked bootloader again, reinstalled twrp. Flashed the back up and now I got rid of the error from OTA and now reads that I am up to date.
Hope this helps ur situation a little if any.
This might be a dumb question but I'm trying to revert everything back to stock on my phone and I can't find the files for the T-Mobile version, I haven't don't the getvar deal yet but I haven't seen the ruu file for T-Mobile HTC 10 so I haven't bothered yet as I really don't want to brick it and have to shell out $175 just to switch back to the note 5
htcfresh said:
This might be a dumb question but I'm trying to revert everything back to stock on my phone and I can't find the files for the T-Mobile version, I haven't don't the getvar deal yet but I haven't seen the ruu file for T-Mobile HTC 10 so I haven't bothered yet as I really don't want to brick it and have to shell out $175 just to switch back to the note 5
Click to expand...
Click to collapse
If your s-off look here::::http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520/page33
htcfresh said:
This might be a dumb question but I'm trying to revert everything back to stock on my phone and I can't find the files for the T-Mobile version, I haven't don't the getvar deal yet but I haven't seen the ruu file for T-Mobile HTC 10 so I haven't bothered yet as I really don't want to brick it and have to shell out $175 just to switch back to the note 5
Click to expand...
Click to collapse
If you do it the way I did it you will be on stock but rooted with tarp.
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.
I have a Htc One M8 ; s-off, hboot 3.16, running 4.4.2. CID is Roger001, unlocked boot
Problem I have is I'm trying to restore the phone to stock because I want to do OTA updates. I followed the guide to return Canadian HTC1m8 to stock - downloaded the nandroid backup, restored it, flashed a stock image through fastboot;
However, now if I try a OTA it just reboots my phone and normally stalls out on the HTC screen. Nothing gets updated . If i try a factory reset, same thing, and it won't boot into bootloader until I wait a while then restart it. My data won't work anymore and TWRP recovery has disappeared. I think my issue is i flashed the wrong recovery .img, I'm a fairly noob. Checked all the related links and can't figure it out.
Any help would be amazing.
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
htcspark said:
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
Click to expand...
Click to collapse
I would but
I can't find an ruu that would work, there doesn't seem to be one for rogers...I dunno if any US carriers would work?
htcspark said:
Use an ruu For your phone to update your hboot and make your you flash to recovery partition for twrp
Click to expand...
Click to collapse
I got an update to work, I think I had the wrong stock installed so it wouldn't work properly. Only thing now is my data isn't working, any assistance with that that could be??
Instead of trouble shooting, I would just flash this TWRP backup tested to work on Rogers M8:
http://forum.xda-developers.com/showthread.php?p=58611288
See end of 1st post in above link.
It is already in lollipop. No OTA update needed.
Use latest TWRP recovery, see 2nd post in above link.
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
ruubs said:
Hi guys,
I've updated my M9 to 7.0 through OTA update. After installing my phone boots directly in to the bootloader. I can enter download and recovery mode without any trouble but that's about it. When i try to boot in to the phone it boots back to the bootloader. My phone is S-ON so i can't flash a RUU through ADB, however the phone is unlocked.
I tried to flash a RUU through the external micro SD card method but that failed because the firmware is lower than my firmware.
Current M9 Status:
*Unlocked*
S-On
Firmware 4.14.401.7
Stuck in bootloader/recovery/downloadmode
I tried everything to my knowledge. Is there someone who encountered the same problems as i do? Or is there someone who knows a solution to all of this?
Click to expand...
Click to collapse
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
computerslayer said:
Some questions:
Did you have a completely stock device when you applied the OTA?
Did it ever successfully boot into Nougat, or did the OTA immediately result in the current condition?
I wonder if you could either flash TWRP or use it via your computer (there's a way to run it in your phone without installing it) so that you could apply the OTA again. I'm not sure if it would fix whatever went wrong, though.
Alternatively, you could flash a ROM (again, via TWRP), obtain S-OFF, change your MID & CID to the developer version and apply that RUU.
Click to expand...
Click to collapse
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
ruubs said:
I did have a completely stock device before i installed the OTA.
It did never successvully booted into nougat. Right after the install it booted in to the bootloader.
How can i flash TWRP or another ROM while im S-ON? Or am i wrong in this? Please help me out
Click to expand...
Click to collapse
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
computerslayer said:
S-ON is no obstacle to flashing TWRP or another ROM. You will need to unlock your bootloader in order to do either but I assumed that you had already done this since you posted that your status is unlocked.
Click to expand...
Click to collapse
The phone status is indeed unlocked.
I didn't know I could flash TWRP or a ROM. I thought I needed S-OFF for that.
I want my phone to be as stock as possible. Can I flash a stock ROM or does it have to be a custom one.
And do i need to flash TWRP in order to flash a ROM?
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
ruubs said:
So i've searched around and came to the conclusion to fix my phone is to flash TWRP first. After that FLASH a custom ROM, if that goes as planned S-OFF my phone with the SunShine method. After that go back to stock and hope everything goes well.
Click to expand...
Click to collapse
That's the route I would take too. The readme thread has a section dedicated to changing your SKU in order to use other RUUs.
Hi people, this is my first time posting on a forum. I've always fixed my problem by googling them but now i failed.
I fixed the problem mentioned in the title and now i'm back to the original problem.
I followed a guide on the web to root my HTC 10. What i did was unlocking the bootloader and then flashing TWRP and till then things went good.
Then i tried to root it by flashing superSU and after that my phone went in bootloop and i found out i didnt have a system image anymore.
I tried to flash the RUU with my cid but i got the following error "RU_MAIN_VER_FAIL...".
This is my situation:
-i can access download, recovery and bootloader
-I've TWRP installed and my internal storage is blank, it only has an empty TWRP folder.
-My external memory has the following folders: Android, TWRP, .android_secure, LOST.DIR
What is my problem? I even tried to restore a TWRP backup without succeeding from https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Please help me!!
rorou said:
Hi people, this is my first time posting on a forum. I've always fixed my problem by googling them but now i failed.
I fixed the problem mentioned in the title and now i'm back to the original problem.
I followed a guide on the web to root my HTC 10. What i did was unlocking the bootloader and then flashing TWRP and till then things went good.
Then i tried to root it by flashing superSU and after that my phone went in bootloop and i found out i didnt have a system image anymore.
I tried to flash the RUU with my cid but i got the following error "RU_MAIN_VER_FAIL...".
This is my situation:
-i can access download, recovery and bootloader
-I've TWRP installed and my internal storage is blank, it only has an empty TWRP folder.
-My external memory has the following folders: Android, TWRP, .android_secure, LOST.DIR
What is my problem? I even tried to restore a TWRP backup without succeeding from https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Please help me!!
Click to expand...
Click to collapse
Grab an ruu that is at least at the same version you are, or flash a custom rom from twrp
Tarima said:
Grab an ruu that is at least at the same version you are, or flash a custom rom from twrp
Click to expand...
Click to collapse
thank you for your reply! i tried already a ruu solution with the version of my cid but it didnt workout. You're saying i need to install a custom rom and then revert back to stock?
rorou said:
thank you for your reply! i tried already a ruu solution with the version of my cid but it didnt workout. You're saying i need to install a custom rom and then revert back to stock?
Click to expand...
Click to collapse
No I meant you can flash a custom rom instead of stock. If you want stock you'll have to run a stock ruu. What's your current software number and which ruu are you trying to run?
Tarima said:
No I meant you can flash a custom rom instead of stock. If you want stock you'll have to run a stock ruu. What's your current software number and which ruu are you trying to run?
Click to expand...
Click to collapse
I've used this ruu 1.90.401.5 that has same mid and cid as my phone. And before wiping my internaL storage i had nougat, 7.0 i think. This ruu thing is really twisting my mind, never heard about it before today... maybe that's because i got in trouble. I've installed viper and the phone seems to work now but i have my doubts on whether to keep it or not. I'll try this so rom for a week, i want to see if it has battery or overheating issues.
But in case i wanted to go back to stock, i dont know what went wrong and why the ruu i've picked failed to install even if it had the same cid and mid.
rorou said:
I've used this ruu 1.90.401.5 that has same mid and cid as my phone. And before wiping my internaL storage i had nougat, 7.0 i think. This ruu thing is really twisting my mind, never heard about it before today... maybe that's because i got in trouble. I've installed viper and the phone seems to work now but i have my doubts on whether to keep it or not. I'll try this so rom for a week, i want to see if it has battery or overheating issues.
But in case i wanted to go back to stock, i dont know what went wrong and why the ruu i've picked failed to install even if it had the same cid and mid.
Click to expand...
Click to collapse
If you had Nougat before, that means your firmware version is 2.x.x.x. This is newer than the ruu you're trying to flash. You can only run an ruu that is at the same version as or above your current firmware version, and you cannot downgrade. That's what I mean by "run an ruu that's the same version as your phone."
Get your software info by doing fastboot getvar all from download mode. Then find an ruu that is for your CID/mid and at the same or higher version that you have. That'll take you to stock.
Tarima said:
If you had Nougat before, that means your firmware version is 2.x.x.x. This is newer than the ruu you're trying to flash. You can only run an ruu that is at the same version as or above your current firmware version, and you cannot downgrade. That's what I mean by "run an ruu that's the same version as your phone."
Get your software info by doing fastboot getvar all from download mode. Then find an ruu that is for your CID/mid and at the same or higher version that you have. That'll take you to stock.
Click to expand...
Click to collapse
That explains everything! thank you so much!!!