Related
Okay so my sisters sensation would freeze up every time she got calls from certain people so I told her to let me root it. Since this is something I have done many times before I didn't think I would have any problems, but I do.
I can only boot into bootloader and then recovery. I can flash ROMs, restore, and do anything else you do in recovery, except afterwords when I choose reboot the phone just turns off and nothing happens and I can't boot into recovery for several minutes (during these minutes the phone has to be charging). I've been up for literally 5 hours, 1-6 am, trying to figure this out. Someone PLEASE help me. Seriously WILLING TO PAY for an answer that works.
Thank you.
Boot into the bootloader and then flash the RUU back to stock. If that works then perhaps try again
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
JayIce11 said:
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
Click to expand...
Click to collapse
I doubt that's the problem. If he forgot to remove PG58IMG.zip, then every time he boots into bootloader, it would just try to update, not prevent him from booting up the phone.
Have you tried SuperWiping first, then flashing the FW, then the ROM? I don't think this would make a difference but since you've tried FW -> SW -> ROM, can't hurt to mix it up.
EDIT: Just thought of this: did you flash a FW for your region? If not, you might need to super CID.
JayIce11 said:
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
Click to expand...
Click to collapse
Yea I've taken it off the sd and tried that didn't work either man
tr1p7s said:
I doubt that's the problem. If he forgot to remove PG58IMG.zip, then every time he boots into bootloader, it would just try to update, not prevent him from booting up the phone.
Have you tried SuperWiping first, then flashing the FW, then the ROM? I don't think this would make a difference but since you've tried FW -> SW -> ROM, can't hurt to mix it up.
EDIT: Just thought of this: did you flash a FW for your region? If not, you might need to super CID.
Click to expand...
Click to collapse
See my problem with super CID is the guide that I see for it http://forum.xda-developers.com/showthread.php?t=1459767 requires me to be able to actually use my phone and I screwed that up lol. I tried that fastboot method too and it didn't work. I fear I've really messed this up.
EddyOS said:
Boot into the bootloader and then flash the RUU back to stock. If that works then perhaps try again
Click to expand...
Click to collapse
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
brandonsmooth said:
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
Click to expand...
Click to collapse
Should be able to find your phones RUU in the development part of the forums.
Also most of the major Western carriers have the firmware posted on this forum. Did you download the correct one?
brandonsmooth said:
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
Click to expand...
Click to collapse
Download an RUU from here http://forum.xda-developers.com/showthread.php?t=1074559 to your pc making sure it is the appropriate one for your device (give me more details if you are unsure), boot your phone into fastboot (volume down and power), plug the usb cable into your phone and pc. Your device should now say fastboot usb then double click the RUU.exe that you have downloaded to your pc. This will restore your device to stock.
So problem is the rom refuses to boot, but recovery, bootloader does?
Check whatever fw you flashed is compatible with the rom you are trying to boot. If not change one.
If this does not help then use Eddy's suggestion and run correct ruu. Make sure your CID supports the one you use, or forget this if you have superCID.
Sent from my Pyramid-T
Do what is said here: http://forum.xda-developers.com/showthread.php?t=1192300 (the superCID part) and skip steps 5,6 and 7 just boot into bootloader manually. Then, flash the firmware you need, you won't have to worry about the CID. Get it from here: http://forum.xda-developers.com/showthread.php?t=1459767
Having almost the exact same problem after flashing the firmware..
Def. Gonna try this.
Hey guys,
I'm currently running Sense-O-Maniac on my HTC Sensation. (I'm completely clueless about 99% of rooting, so if you need more info in order to help me, I'd be glad to get the info for you) I'm attempting to flash ViperS , but I keep getting caught in a boot loop after setup. I'm not sure if I'm missing something, or I'm not compatible with the ROM. Any info would help, Thanks in advance!
Vinny Bacon said:
Hey guys,
I'm currently running Sense-O-Maniac on my HTC Sensation. (I'm completely clueless about 99% of rooting, so if you need more info in order to help me, I'd be glad to get the info for you) I'm attempting to flash ViperS , but I keep getting caught in a boot loop after setup. I'm not sure if I'm missing something, or I'm not compatible with the ROM. Any info would help, Thanks in advance!
Click to expand...
Click to collapse
So you must already be rooted and S-OFF? Sounds like a firmware issue, did you make a nandroid backup before trying to flash ViperS?
goatee84 said:
So you must already be rooted and S-OFF? Sounds like a firmware issue, did you make a nandroid backup before trying to flash ViperS?
Click to expand...
Click to collapse
I do have S-OFF (I used revolutionary months ago, and I've neglected my root ever since)
By a nandroid backup you mean the backup that is under "Backup and Recovery" menu? The ones that are named by the date and time it was done? If so than yes, I have multiple of them.
UPDATE: I just went through the SuperCid process (because to be honest, I don't remember if I've ever done it before. Attempting to flash ViperS now.
Vinny Bacon said:
UPDATE: I just went through the SuperCid process (because to be honest, I don't remember if I've ever done it before. Attempting to flash ViperS now.
Click to expand...
Click to collapse
UPDATE: NOPE, Still caused a boot loop, restoring to the backup made earlier today
Vinny Bacon said:
I do have S-OFF (I used revolutionary months ago, and I've neglected my root ever since)
By a nandroid backup you mean the backup that is under "Backup and Recovery" menu? The ones that are named by the date and time it was done? If so than yes, I have multiple of them.
Click to expand...
Click to collapse
Yep, that's a nandroid. So you've got something to get your phone operational again if necessary. Now that you're superCID I would try installing 3.33 universal firmware from here then reflash ViperS and see what happens. Before you install the firmware double check superCID from bootloader using adb (fastboot getvar cid).
One thing to keep in mind, your nandroid backup will only work with the firmware you were using when you created the backup, so if you wanted to be REALLY careful you could restore your latest nandroid before doing anything else, check firmware version in Settings/About Phone, download a copy of that firmware, THEN try and install new firmware/flash ViperS.
EDIT: Ok just saw your latest post. Since you're restoring a nandroid you can check that firmware version before going any further as mentioned.
goatee84 said:
Yep, that's a nandroid. So you've got something to get your phone operational again if necessary. Now that you're superCID I would try installing 3.33 universal firmware from here then reflash ViperS and see what happens. Before you install the firmware double check superCID from bootloader using adb (fastboot getvar cid).
One thing to keep in mind, your nandroid backup will only work with the firmware you were using when you created the backup, so if you wanted to be REALLY careful you could restore your latest nandroid before doing anything else, check firmware version in Settings/About Phone, download a copy of that firmware, THEN try and install new firmware/flash ViperS.
EDIT: Ok just saw your latest post. Since you're restoring a nandroid you can check that firmware version before going any further as mentioned.
Click to expand...
Click to collapse
I went to Software Information and found:
ANDROID VERSION : 2.3.5
HTC SENSE VERSION: 3.5
Should I still download that 3.3 universal firmware? If so, what do I do once it's downloaded? Do I have to flash it or anything?
UPDATE:
I clicked the link and read through the tutorial. I'm just not sure if it's still necessary to install that 3.3 firmware.
IT WORKED!!! THANK YOU SO MUCH! You were such a great help!
Vinny Bacon said:
I went to Software Information and found:
ANDROID VERSION : 2.3.5
HTC SENSE VERSION: 3.5
Should I still download that 3.3 universal firmware? If so, what do I do once it's downloaded? Do I have to flash it or anything?
UPDATE:
I clicked the link and read through the tutorial. I'm just not sure if it's still necessary to install that 3.3 firmware.
Click to expand...
Click to collapse
There should be another entry under those two you mentioned called Software Number or something similar?
To install firmware, when you boot into bootloader it scans your SD card for PG58IMG file then asks if you want to update. So as long as your firmware file is called PG58IMG.zip it will work.
I glanced at the ViperS thread and it says it's based on 1.11.401.110 RUU, seems that those running the ROM are using the 3.33 firmware.
---------- Post added at 03:56 AM ---------- Previous post was at 03:54 AM ----------
Vinny Bacon said:
IT WORKED!!! THANK YOU SO MUCH! You were such a great help!
Click to expand...
Click to collapse
Great enjoy your new ROM, glad I could help :good:
Hello,
I'm new here but today I tried to root my phone and put CM10 on it. Rooting was not that hard but with flashing the rom I had some problems. I used a tutorial from youtube "Htc One s jellybean 4.2.2 Nightly Cm10.1 Rom" and did everything as he said but when I tried to boot CM it came in a boot loop so I restored my backup and everything was back normal again. But I thought i'll give it another try so I did that and it still didn't work so I restored (via recovery) and at the end it said: It appears your phone isn't rooted do you wanna do it now...(or something like that)? I found that a bit strange but I clicked yes but now if I boot up my phone first you just see "HTC - quietly brilliant" and then the red letters come beneath it saying its a developers version. I Couldn't do anything so I jumped into my bootloader and did factory reset but now everything is gone and I still have that booting problem,
I can acces bootloader and recovery mode but that's it
I really need my phone soon and don't have much time to look on the internet for solutions so could you please help me?
Thanks in advance!!
Lennard
Do you have the RUU for your phone? Maybe that would be the quick fix to take it back to stock. You can use an RUU that's equal or newer than what you have currently.
BTW: I went through this as well.
808phone said:
Do you have the RUU for your phone? Maybe that would be the quick fix to take it back to stock. You can use an RUU that's equal or newer than what you have currently.
BTW: I went through this as well.
Click to expand...
Click to collapse
I don't even know what that it >.< (sorry for being noob )
Did you flash boot.img with cm10
Sent from my One S
ka_55 said:
Did you flash boot.img with cm10
Sent from my One S
Click to expand...
Click to collapse
Jep, as instructed in the youtube video
Which hboot version and radio?
Cm10 uses 3.4.x kernel, it won't boot with old firmware
Sent from my One S
ka_55 said:
Which hboot version and radio?
Cm10 uses 3.4.x kernel, it won't boot with old firmware
Sent from my One S
Click to expand...
Click to collapse
Hboot : 2.15.000
Radio : 1.15.50.05.29
Then it can be a bad download. If not I I'm out of ideas
Sent from my One S
Do you remember doing any of the following?
-wipe data/factory reset
-wipe dalvik cache
I think that was my problem that I didn't wipe the cache completely. Possibly a bad download too. Do a search on md5. It's basically a check to see if your download is ok before flashing.
As far the RUU is concerned, it will take you back to stock. You will need the info that appears when you start the phone up by holding down VOL DOWN and POWER. Hold down volume down, then press the power for a second or 2. Then it will boot up into HBOOT.
Write down the info that appears and search for a matching RUU equal or newer.
What is the carrier???
808phone said:
Do you remember doing any of the following?
-wipe data/factory reset
-wipe dalvik cache
I think that was my problem that I didn't wipe the cache completely. Possibly a bad download too. Do a search on md5. It's basically a check to see if your download is ok before flashing.
As far the RUU is concerned, it will take you back to stock. You will need the info that appears when you start the phone up by holding down VOL DOWN and POWER. Hold down volume down, then press the power for a second or 2. Then it will boot up into HBOOT.
Write down the info that appears and search for a matching RUU equal or newer.
What is the carrier???
Click to expand...
Click to collapse
I did the factory reset, dalvik cache and cache wipe. When I tried to install CM it indeed said unable to find md5 or something like that.
I think I have a europe version and looked for fitting RUU but the numbers are completely different maybe you could find a good RUU? (See attachement) Btw I have S4/Ville/Z520e
CID
Could you please read out your CID? Then we can get right RUU.
You can do this by booting your One S into fastboot mode and use the toolkit from the link:
http://forum.xda-developers.com/showthread.php?t=2471151
LS.xD said:
Could you please read out your CID? Then we can get right RUU.
You can do this by booting your One S into fastboot mode and use the toolkit from the link:
http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
I don't know if this is it but it says CID: HTC__E11
Lennardude said:
I don't know if this is it but it says CID: HTC__E11
Click to expand...
Click to collapse
yes thats it
This should be the right RUU http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
MAY anyone who reads this confirm it? Just to be safe at all.
btw. "HTC_E11" = unbranded Netherlands
Due to you're S-ON you will have to relock your bootloader to perform a RUU update.
Here you can find a step by step RUU guide by "Flashalot" http://forum.xda-developers.com/showthread.php?p=51016251
LS.xD said:
yes thats it
This should be the right RUU http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
MAY anyone who reads this confirm it? Just to be safe at all.
btw. "HTC_E11" = unbranded Netherlands
Due to you're S-ON you will have to relock your bootloader to perform a RUU update.
Here you can find a step by step RUU guide by "Flashalot" http://forum.xda-developers.com/showthread.php?p=51016251
Click to expand...
Click to collapse
Should I first relock my bootloader and follow the tutorial to flash that RUU of vice versa?
Lennardude said:
Should I first relock my bootloader and follow the tutorial to flash that RUU of vice versa?
Click to expand...
Click to collapse
For RUU you need stock recovery and "locked" BL. Please read the guide again and only proceed, if you're sure you got it.
Another question:
You said you got a working recovery? Which version do you use? And have you tried install another custom rom.zip? That would be more easy and safe to you. May be your storage got corrupted and thats why your phone crashed and you can't install the rom.zip stored on the sd-card. You could connect the phone to your pc as mass storage via recovery, format it and put a new customrom.zip on it. By the way, why you installed such an old rom? You can use CM11 for sure
LS.xD said:
For RUU you need stock recovery and "locked" BL. Please read the guide again and only proceed, if you're sure you got it.
Another question:
You said you got a working recovery? Which version do you use? And have you tried install another custom rom.zip? That would be more easy and safe to you.
Click to expand...
Click to collapse
In that guide it doesn't say anything about a relocked bootloader.
I do have a working recovery but how can I get a zip file on it? I can't acces the files of my phone in windows explorer or something like that. Also I don't know if I have a stock recovery but if I don't I have to install that via a zip but how can I get that on my phone...?
Lennardude said:
In that guide it doesn't say anything about a relocked bootloader.
I do have a working recovery but how can I get a zip file on it? I can't acces the files of my phone in windows explorer or something like that. Also I don't know if I have a stock recovery but if I don't I have to install that via a zip but how can I get that on my phone...?
Click to expand...
Click to collapse
PLS boot in recovery mode and tell me what "version" it is You should find it. If you're not sure about it, you can flash a new recovery before installing a rom. Whe you have a working custom recovery you can mount your sd-card to your computer via recovery.
Found the RUU guide i had in mind http://forum.xda-developers.com/showthread.php?t=2501542
LS.xD said:
PLS boot in recovery mode and tell me what "version" it is You should find it.
Click to expand...
Click to collapse
v2.6.0.0
Lennardude said:
v2.6.0.0
Click to expand...
Click to collapse
that is TWRP. My suggestion ist installing the latest Recovery and try install CM11. I just get the links for you.
LS.xD said:
PLS boot in recovery mode and tell me what "version" it is You should find it. If you're not sure about it, you can flash a new recovery before installing a rom. Whe you have a working custom recovery you can mount your sd-card to your computer via recovery.
Found the RUU guide i had in mind http://forum.xda-developers.com/showthread.php?t=2501542
Click to expand...
Click to collapse
The problem is, we're talking about an HTC One S which DOESN"T have a SD Card slot...
Can somebody explain me,how can i go back to stok to apply ota update if im rooted and have opend bootloader!?
krepsz said:
Can somebody explain me,how can i go back to stok to apply ota update if im rooted and have opend bootloader!?
Click to expand...
Click to collapse
Hi,
me too i want to back to stock but i think it's to complicated, so what i know : 1st backup ur current custom rom (for safe ^^);
2nd restore stock recovery; 3th restore RUU for your A9 (hiaeuhl or hiaeul etc ... ) that all i know but i heard that we need to restore the /system partition (i dont backup this before install cm13 :/ ) if anybody know what to do exactly :fingers-crossed: :silly:
the s-on/s-off scare me too xD i dont know what to do to restore stock properly ^^' maybe we have another thread for that i look later
S-on/off has nothing to do with going back to stock (unless you want to change version).
if you flash RUU you'll be 100% stock but you'll lose everything including root
bootloader is fine i guess.
syntenza said:
S-on/off has nothing to do with going back to stock (unless you want to change version).
if you flash RUU you'll be 100% stock but you'll lose everything including root
bootloader is fine i guess.
Click to expand...
Click to collapse
I relocked bootloader and flash stock recovery,but if i want flash the RUU fil i get this:
target reported max download size invalid sparse file format at header magi
krepsz said:
I relocked bootloader and flash stock recovery,but if i want flash the RUU fil i get this:
target reported max download size invalid sparse file format at header magi
Click to expand...
Click to collapse
Verify that you have the correct RUU for your phone. If you do, and it still isn't working, try the RUU .exe while your phone is in download mode. Also, make sure you're not using a USB 3.0 port. Sometimes that can cause problems.
CSnowRules said:
Verify that you have the correct RUU for your phone. If you do, and it still isn't working, try the RUU .exe while your phone is in download mode. Also, make sure you're not using a USB 3.0 port. Sometimes that can cause problems.
Click to expand...
Click to collapse
I found just one old RUU zip file for my phone.RUU.exe i dont know where i can found.Usb port working with all command before.
krepsz said:
I found just one old RUU zip file for my phone.RUU.exe i dont know where i can found.Usb port working with all command before.
Click to expand...
Click to collapse
What A9 version do you have? (Unlocked, carrier, EU, etc.)
CSnowRules said:
What A9 version do you have? (Unlocked, carrier, EU, etc.)
Click to expand...
Click to collapse
Vodafone UK
modelid: 2PQ910000
cidnum: VODAP001
Refer to this thread by @alray.
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Download 1.27.161.6 from post #1, then follow the steps from post #2. I'd try the first method, first.
This should work unless your firmware was updated to a later version than 1.27.161.6.
CSnowRules said:
Refer to this thread by @alray.
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Download 1.27.161.6 from post #1, then follow the steps from post #2. I'd try the first method, first.
This should work unless your firmware was updated to a later version than 1.27.161.6.
Click to expand...
Click to collapse
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
krepsz said:
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
Click to expand...
Click to collapse
Gotcha, I'd recommend that you use the external sd/stock recovery method to return to stock. That's probably the most bulletproof way to return to stock. If you no longer have the stock recovery, no problem. It's pretty simple to extract the recovery from the RUU and flash it first.
Also, did you download the RUU again? It is possible that you may have a corrupted RUU.zip if it is crashing your fastboot.
So me i'm on CM13 nightlies with twrp and boot.img modified, to back to stock i had to flash stock recovery( * ) than flash the RUU( ** ) ? that all ?
*: i had to extract it from the RUU coresponding i'm good ? ^^"
**: my cid is HTC_034; my mid is 2PQ910000 so i had to take the 1.10.401.7 RUU i'm good ? ^^' or the 1.56.401.70 or 1.27.401.5 ? i'm lost, on my dowload mode it's say i'm on 1.10.401.7 (but i'm on cm13 latest nightlies ... >< )
Than, when i'm succefully back to stock if i choose to return to cm13 i can flash my backup(recovery+boot+/system+rom) of cm13 with twrp if firmware doesn't upgrade with OTA on stock i'm good ?
Lots of question i know ^^' thx for help.
krepsz said:
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
Click to expand...
Click to collapse
If you use the sd card method (copy the RUU.zip to external sd) fastboot is no longer necessary. The RUU is flashed using the stock recovery. There's no fastboot to crash at that point.
---------- Post added at 04:01 PM ---------- Previous post was at 03:49 PM ----------
ValdOr7 said:
So me i'm on CM13 nightlies with twrp and boot.img modified, to back to stock i had to flash stock recovery( * ) than flash the RUU( ** ) ? that all ?
*: i had to extract it from the RUU coresponding i'm good ? ^^"
**: my cid is HTC_034; my mid is 2PQ910000 so i had to take the 1.10.401.7 RUU i'm good ? ^^' or the 1.56.401.70 or 1.27.401.5 ? i'm lost, on my dowload mode it's say i'm on 1.10.401.7 (but i'm on cm13 latest nightlies ... >< )
Than, when i'm succefully back to stock if i choose to return to cm13 i can flash my backup(recovery+boot+/system+rom) of cm13 with twrp if firmware doesn't upgrade with OTA on stock i'm good ?
Lots of question i know ^^' thx for help.
Click to expand...
Click to collapse
You shouldn't have any trouble returning to stock at all. I've had quite a few Heineken at this point, but flashing boot, recovery, and system of your stock rom is no problem at all if you have backups.
CSnowRules said:
If you use the sd card method (copy the RUU.zip to external sd) fastboot is no longer necessary. The RUU is flashed using the stock recovery. There's no fastboot to crash at that point.
---------- Post added at 04:01 PM ---------- Previous post was at 03:49 PM ----------
You shouldn't have any trouble returning to stock at all. I've had quite a few Heineken at this point, but flashing boot, recovery, and system of your stock rom is no problem at all if you have backups.
Click to expand...
Click to collapse
Could you state how this is done? I recently moved to the A9 from having the M7 since it came out, (which had NO external SD card support) , so this is the 1st I'm hearing of being able to apply an RUU Without fastboot... Does the RUU have to be in any specific folder, or the root of the external SD card?
Any details would be GREATLY appreciated.
bdizzle1686 said:
Could you state how this is done? I recently moved to the A9 from having the M7 since it came out, (which had NO external SD card support) , so this is the 1st I'm hearing of being able to apply an RUU Without fastboot... Does the RUU have to be in any specific folder, or the root of the external SD card?
Any details would be GREATLY appreciated.
Click to expand...
Click to collapse
This http://forum.xda-developers.com/showpost.php?p=63640734&postcount=2 explains in detail. I THINK this utilizes the stock recovery in the process. In any case, it allows flashing an RUU.zip without any fastboot involvement.
It's possible to return s-on and bootloader locked (not relocked)? Thank's.
CSnowRules said:
You shouldn't have any trouble returning to stock at all. I've had quite a few Heineken at this point, but flashing boot, recovery, and system of your stock rom is no problem at all if you have backups.
Click to expand...
Click to collapse
Yes i know but u dont understand me i think, for the RUU there 3 version for my phone 1.10 -> 1.27 -> 1.56 so witch one i had to take ? CM13 run with 1.27 ? 1.10 with cm13 isn't possible no ? because on my download mode(bootloader) it's say : OS-1.10.401.7 in theory i would take the 1.10.401.7 RUU but a man (on this forum) tell me this was a bug of cm13 and its run with 1.27 it's wrong ??
ValdOr7 said:
Yes i know but u dont understand me i think, for the RUU there 3 version for my phone 1.10 -> 1.27 -> 1.56 so witch one i had to take ? CM13 run with 1.27 ? 1.10 with cm13 isn't possible no ? because on my download mode(bootloader) it's say : OS-1.10.401.7 in theory i would take the 1.10.401.7 RUU but a man (on this forum) tell me this was a bug of cm13 and its run with 1.27 it's wrong ??
Click to expand...
Click to collapse
Any one of the three would return you to stock, as long as the version number is greater than or equal to the firmware that you have installed. (Which is the topic of this tread...)
As far as compatibility with CM, you should check that thread...but I think CM is compatible with the 1.27 firmware. If you're still s-on, you DO NOT want to upgrade the firmware to a newer version than CM supports, if you intend to use CM.
---------- Post added at 02:44 PM ---------- Previous post was at 02:39 PM ----------
CEDRIC23 said:
It's possible to return s-on and bootloader locked (not relocked)? Thank's.
Click to expand...
Click to collapse
I'm sure it's possible...just a matter of finding exactly what you need to hex edit and where it is. Experimenting with this likely carries a chance of bricking your device, since the variables would have to be used by HBOOT and/or download mode. Maybe someone else has already accomplished this?
krepsz said:
Thank you very much,but i was try 3 times and i get always error and force closed my fastboot.See post 4 from this thread!
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash a RUU, not the regular fastboot.exe from the android sdk.
CSnowRules said:
This http://forum.xda-developers.com/showpost.php?p=63640734&postcount=2 explains in detail. I THINK this utilizes the stock recovery in the process. In any case, it allows flashing an RUU.zip without any fastboot involvement.
Click to expand...
Click to collapse
The stock recovery is not used when flashing a RUU from the sdcard. The bootloader handles the process, not the recovery. Stock recovery isn't needed at all, using fastboot or the sdcard methods.
alray said:
The stock recovery is not used when flashing a RUU from the sdcard. The bootloader handles the process, not the recovery. Stock recovery isn't needed at all, using fastboot or the sdcard methods.
Click to expand...
Click to collapse
Thanks, Alray, for the clarification on the sd card method.
Hi
I really need help to go stock on my device.
I unlocked my bootloader, flashed TWRP and Magisk on stock rom and installed the ViperU Magisk Module.
I also made a NANDROID of the stock ROM before, unfortunately there is no Recovery in it, since i had TWRP already installed.
Then an OTA (oktober 17 security patch) was available for my device and i startet the install process, but it didn't install.
TWRP open recovery would run not even 1 second then exit.
In order to get the OTA I restored stock recovery (which i had to extract from OTA, since i forgot to back it up) and started OTA.
--> Red Triangle!
Even after restoring stock NANDroid the OTA wouldn't install.
My mistake i think was that i didn't kept the stock system read only when i did the backup in twrp and swiped to allow modifications.
According to some threads here, even mounting the system r/w would break OTA functionality.
So since i also have no RUU for my device, i don't have the chance either to go back to stock. Maybe you did that mistake too.
The only way i can think of now, is to go temporary S-OFF, change CID and MID (to 401 international for example), flash Firmware and run the RUU for it.
But i'm not sure it'll still work after flashing the firmware.
Can anyone maybe confirm this way would work?
And is there an other way available?
Thanks!
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000
Nightmare
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000[/QUOTE said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
michaelbsheldon said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Hi
Yes, unfortunately there's nothing available for my device.
Does the phone boot into os?
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
schmeggy929 said:
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
Click to expand...
Click to collapse
Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
2eli0 said:
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
Click to expand...
Click to collapse
since s-off is still temporary it will go back to s-on as soon as you boot into recovery or rom.
also, i flashed the 1.27.401.5 ruu, since i wanted to see if the update to 1.27.401.12 ota works with twrp and magisk installed.
it does, just remember to keep recovery read only!
What do you mean by "read only"? Is there a setting where I can do that?
2eli0 said:
What do you mean by "read only"? Is there a setting where I can do that?
Click to expand...
Click to collapse
If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Nightmare[ITA said:
;75529278]If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Click to expand...
Click to collapse
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
2eli0 said:
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
Click to expand...
Click to collapse
Pretty much, ya. I missed that part the first time too
Nightmare[ITA said:
;75529808]Pretty much, ya. I missed that part the first time too
Click to expand...
Click to collapse
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
2eli0 said:
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
Click to expand...
Click to collapse
Yes, over the last few months AFH has been extremely slow.
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
I have already seen that, but its like 400 mb big, if I remember correctly, hence not the entire files, right?
schmeggy929 said:
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
The htcdev stuff is source only. No good. Also, once you flash twrp you can't take ota. You must be stock to take ota (s-off and bootloader remain untouched and do not matter for flashing, there is no need to s-on nor relock the bootloader ever).
To achieve stock just flash the same firmware you currently use as a zip from the external sdcard. The only things lost is root and twrp.
Nightmare[ITA] said:
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
Click to expand...
Click to collapse
Yeah i guess you are right it is the source code. Even with TWRP stills seems like a lot of work to update. Ya'll need some custom ROMs installed. Flash signed firmware.zip, reflash TWRP and flash updated ROM. All done. If by chance you ever needed to return to stock, flash your system image backup. Ya'll make things so complicated when they really aren't. lol
Nightmare[ITA said:
]Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Click to expand...
Click to collapse
Well, I managed to do it exactly the way you did.
Everything worked just fine. I changed the CID to HTC__034 and flashed the ruu file updated to Oreo and flashed TWRP kept it at read only and rooted the phone.
Thanks for that :good: