Right so here goes, story so far, HTC m8, ORANG001 cid, bootloader unlocked and rooted but s-on. Flashed ARHD 11.2 all working happy days. I then saw ARHD 20.1 is out but seeing as it needs a 3.***** based firmware i was unable to flash it. So I thought i will use a stock nandroid for my carrier from this thread http://forum.xda-developers.com/showthread.php?t=2701376 re flash the corresponding stock recovery and then do s-off with Sunshine. Well even thou i am back to stock sunshine still wouldn't work :crying: I had a notification that a OTA was available, and I thought maybe that will make a difference, so it installed fine but then i noticed my WiFi wont work, ie the actual toggle in settings will not flick over it just goes grey. I fastbooted getvar-all and noticed that i am still on a 2.26.61.1 base which is what ARHD 11.2 was working on, Is this where my problems are??
If i download the OTA (1.70.61.3 i presume) and then before installing it extract the firmware , then install the OTA , then manually flash the firmware would this help/solve my problems or am i way off?
I have literary been through post after post trying to figure this mess out, i am basically stuck at the moment, can't upgrade, can't downgrade, can't s-off
Any guiance would be amazing guys, thank so much in advance
Gareth
ARHD 21 is based on 3.28.401.7 and if you don't have that same Firmware (3.28.401.6 or 3.28.401.7) your wifi don't work.
If you flash a 4.4.3 Rom (3.28.401.5) your Wifi will work with that Rom.
jkolner said:
ARHD 21 is based on 3.28.401.7 and if you don't have that same Firmware (3.28.401.6 or 3.28.401.7) your wifi don't work.
If you flash a 4.4.3 Rom (3.28.401.5) your Wifi will work with that Rom.
Click to expand...
Click to collapse
Yeah I understand that, thats why I haven't attempted to use arhd 21 yet. My WiFi breaks after I use a stock ROM and do the first ota that I am prompted to do. So from a stock ROM not custom anything, recovery is stock as well
Sent from my HTC One (M8)
Peggy1104 said:
Yeah I understand that, thats why I haven't attempted to use arhd 21 yet. My WiFi breaks after I use a stock ROM and do the first ota that I am prompted to do. So from a stock ROM not custom anything, recovery is stock as well
Sent from my HTC One (M8)
Click to expand...
Click to collapse
Hey. I know this is from a long time ago but did you manage to find a solution? I'm having the same problem just now. Went back to stock NAND from that thread and first OTA kills wifi.
Downloading the next OTA via internet pass-through so hopefully that sorts it.
Thanks
Edit - Fixed it by downloading OTA's via internet pass-through
Azzabear said:
Went back to stock NAND from that thread and first OTA kills wifi.
Click to expand...
Click to collapse
Are you sure the stock nandroid matched the firmware previously on the phone (before OTA)? Did WiFi work after you restored the stock nandroid?
redpoint73 said:
Are you sure the stock nandroid matched the firmware previously on the phone (before OTA)? Did WiFi work after you restored the stock nandroid?
Click to expand...
Click to collapse
The firmware matched. The Wifi worked after restoring but after doing the first update it stopped. I left my phone to download the next few OTA's via internet pass-through and the Android 4.4.4 update fixed the Wifi again.
I'm guessing that update changed something to do with the radio that a nandroid restore can't change with S-On.
If anyone else is having this problem, restore the stock nandroid backup from here, once finished flash the stock recovery, and let the OTA's do their thing. The first can use Wifi, the 2nd and 3rd will need internet pass-through (found in Mobile Network Sharing in settings), and the 4th can use Wifi again.
Azzabear said:
I'm guessing that update changed something to do with the radio that a nandroid restore can't change with S-On.
Click to expand...
Click to collapse
Each OTA will typically deploy a WiFi firmware module that corresponds to the software in that OTA. If not, than something was wrong with that OTA. Its not unheard of, I've seen a few reports of full stock M8's losing WiFi after an OTA.
A nandroid restore only effects the partitions that you specify (system, boot.img, cache, data). That's only 4 partitions, and this phone has something like 40 partitions.
These comments are just academic, than anything. I'm glad to see your issue was fixed by the subsequent OTAs.
redpoint73 said:
Each OTA will typically deploy a WiFi firmware module that corresponds to the software in that OTA. If not, than something was wrong with that OTA. Its not unheard of, I've seen a few reports of full stock M8's losing WiFi after an OTA.
A nandroid restore only effects the partitions that you specify (system, boot.img, cache, data). That's only 4 partitions, and this phone has something like 40 partitions.
These comments are just academic, than anything. I'm glad to see your issue was fixed by the subsequent OTAs.
Click to expand...
Click to collapse
RUU THE B*TCH! is always the right answer.
Related
I (prematurely) update to the leaked version of the Android 2.2 release. I would like to revert back to 1.47.651.1 so I can install Cyanogen 6 Mod. I am fairly new to working with Android ROMs, but I have tried several things.
1.32.651.1 and .6 RUU's do not work. I get "ERROR [140]: Bootloader Version Error".
1.47.651.1's RUU, refuses to see the phone getting "ERROR [171]: USB Connection Error".
I tried multiple "update.zip" files to no avail. I constantly get "signature verification failed" when I try and revert back to these files (renamed as update.zip):
Supersonic_1.32.651.6_rooted.zip
Supersonic_1.32.651.1_rooted.zip
Evo-Froyo-2.2-Rooted-Stock-Odexed-netarchy-signed.zip
I've also tried PC36IMG.zip and receive a "Main Version Older. Update Failed" error.
Is there any way to revert back to 1.47/1.32.xx or am I stuck on this half-baked version of Android?
quite sure there is no root method for the ota update at the moment.
should have read the post saying to wait for root.
last but not least WRONG SECTION POST THIS IN Q AND A
ROFL 100th one today prob
This belongs in Q&A but...
Did you use the rooted or unrooted OTA update?
If you flashed the rooted version you're screwed until someone roots it.
If you flashed the unrooted version, just reboot into recovery and restore the nandroid I'm certain you made before flashing an updated ROM.
Here's another thread about this problem (also in Development)
Once on 2.2, no root...
If you flashed a rooted version of the latest leak I don't think you should have any problems...
I has Fresh 3.0b2 on my phone (based off of newest OTA, but rooted of course) and I just re-flashed the latest CM6 nightly
smw6180 said:
This belongs in Q&A but...
Did you use the rooted or unrooted OTA update?
If you flashed the rooted version you're screwed until someone roots it.
If you flashed the unrooted version, just reboot into recovery and restore the nandroid I'm certain you made before flashing an updated ROM.
Click to expand...
Click to collapse
Just a heads up, for the sake of confusion. I think you got the rooted and unrooted mixed up....
If you flashed the rooted version, you should be able to restore. If you flashed the UNrooted version, you have to wait for a Root method to be found.
Why flash why are you not doing a nandroid when you flash bell cw ask u and then it restores it just the way it was u know like using ghost on a pc
v1pe said:
If you flashed a rooted version of the latest leak I don't think you should have any problems...
I has Fresh 3.0b2 on my phone (based off of newest OTA, but rooted of course) and I just re-flashed the latest CM6 nightly
Click to expand...
Click to collapse
Sent from my EVO using XDA App
kwajr said:
Why flash why are you not doing a nandroid when you flash bell cw ask u and then it restores it just the way it was u know like using ghost on a pc
Sent from my EVO using XDA App
Click to expand...
Click to collapse
except that nandroid or not, you flash the UNROOTED OTA you are screwed for now. your nandroid will be there, but it won't be doing much for you if we can't root the new OTA.
Sorry about the wrong section; I was reading under development and I didn't think to switch.
Now just out of plain curiosity, how come the stock RUU will not work? I understand it is a different bootloader version, but doesn't it just install over it?
thefsfempire said:
Sorry about the wrong section; I was reading under development and I didn't think to switch.
Now just out of plain curiosity, how come the stock RUU will not work? I understand it is a different bootloader version, but doesn't it just install over it?
Click to expand...
Click to collapse
It doesnt work because HTC is not ****ing retarded. If they allowed it to work, what would be the point of them fixing the exploits that allow root?
The last two OTAs have come with bootloaders that have a concept of a minimum version requirement. It's a method to avoid downgrading. Despite the old OTA being "stock" or "official" or whatever you want to call it, it's a lower version than the minimum your current bootloader requires, meaning it would be a downgrade.
Sorry man, you're gonna have to sit tight while some nice dev bails you out.
Thanks for explaining. I don't mind waiting, I under stood the risks. Only thing is that I didn't quite understand how this part of it worked. Thanks for the explanation.
For science see if this method works:
http://forum.xda-developers.com/showthread.php?t=741294
jrmithdobbs said:
For science see if this method works:
http://forum.xda-developers.com/showthread.php?t=741294
Click to expand...
Click to collapse
I'd like to know that as well.
Permission denied when running flash_image through adb.
Does not seem to work on 2.2 FroYo OTA
So if you flashed a rooted rom you can just revert with a NAND backup. Are there any other ways to revert back to a previous version?
Also lets say you go from the currently 2.2 roms back to 1.47, can you then turn around and revert to stock?
sekigah84 said:
So if you flashed a rooted rom you can just revert with a NAND backup. Are there any other ways to revert back to a previous version?
Also lets say you go from the currently 2.2 roms back to 1.47, can you then turn around and revert to stock?
Click to expand...
Click to collapse
If you are rooted, you can do whatever. You can find a zip file of the original rom and just flash it from recovery. I'm not sure if it is possible to downgrade your radios when (I've never tried), but it probably is.
sekigah84 said:
So if you flashed a rooted rom you can just revert with a NAND backup. Are there any other ways to revert back to a previous version?
Also lets say you go from the currently 2.2 roms back to 1.47, can you then turn around and revert to stock?
Click to expand...
Click to collapse
The stock 2.2 rom removes the custom recovery, so you cant use nandroid to revert.
GumboChief said:
The stock 2.2 rom removes the custom recovery, so you cant use nandroid to revert.
Click to expand...
Click to collapse
This is why you use the rooted ones posted on XDA.
I didn't make a nandroid backup before I flashed a custom rom (stupid, I know) and the only stock nandroid backup I can find is a version older than my current firmware. So now I want to flash a stock rom and recovery that is a version older (e.g. current FW: 2.11.708.2, nandroid backup and recovery is 1.60.708.2), is this safe to do?
edit: also would I be able to get official OTA updates this way as well?
Thanks!
Maybe.
It depends on whether all modules are included in the firmware package. Most importantly, hboot consists of 3 modules (sbz 1, 2, and 3). If the firmware zip came from an OTA, its possible only some (not all 3) of the modules were included. Reason being, depending on the OTA, its possible that not all modules needed to be updated depending on what OTA came before it (does that make sense? A bit confusing I know). And in short, if all 3 modules don't play well together, you will have a broken hboot and a hard brick.
At least I've seen this happen on my old One X EVITA. It seems that most of the OTAs for the M8 are complete (and contain all 3 hboot modules), but I can't say that for certain (simply too many different OTAs to keep track of).
Short story, open the firmware zip on your computer using a program like 7zip. If you see sbz1,2,3 in the package, you should be okay. I think hboot is the only thing that comes deployed in "pieces" like that. Otherwise, you should be okay flashing any of the modules back and forth.
But I'm not guaranteeing anything when flashing a firmware zip. To me, its simply a scary thing to do; as any time you flash hboot or radio there is a tiny chance something goes wrong and you get a true brick.
Also, you need s-off to downgrade firmware.
redpoint73 said:
Maybe.
It depends on whether all modules are included in the firmware package. Most importantly, hboot consists of 3 modules (sbz 1, 2, and 3). If the firmware zip came from an OTA, its possible only some (not all 3) of the modules were included. Reason being, depending on the OTA, its possible that not all modules needed to be updated depending on what OTA came before it (does that make sense? A bit confusing I know). And in short, if all 3 modules don't play well together, you will have a broken hboot and a hard brick.
At least I've seen this happen on my old One X EVITA. It seems that most of the OTAs for the M8 are complete (and contain all 3 hboot modules), but I can't say that for certain (simply too many different OTAs to keep track of).
Short story, open the firmware zip on your computer using a program like 7zip. If you see sbz1,2,3 in the package, you should be okay. I think hboot is the only thing that comes deployed in "pieces" like that. Otherwise, you should be okay flashing any of the modules back and forth.
But I'm not guaranteeing anything when flashing a firmware zip. To me, its simply a scary thing to do; as any time you flash hboot or radio there is a tiny chance something goes wrong and you get a true brick.
Also, you need s-off to downgrade firmware.
Click to expand...
Click to collapse
Thanks for the reply redpoint.
I'm S-ON and my current firmware was updated through OTA. So what I'm wondering is would it be okay for me to flash a stock rom (the original one when the M8 was first released) on my HTC M8 WITHOUT downgrading my current firmware version. I'm scared if firmwares are not backwards compatible with roms.
zentenk said:
I'm S-ON and my current firmware was updated through OTA. So what I'm wondering is would it be okay for me to flash a stock rom (the original one when the M8 was first released) on my HTC M8 WITHOUT downgrading my current firmware version. I'm scared if firmwares are not backwards compatible with roms.
Click to expand...
Click to collapse
Yeah, I'm not sure. I haven't heard of anyone "downgrading" the OS and keeping newer (mismatched) firmware. I'd be afraid of lack of backwards compatibility, as well.
redpoint73 said:
Yeah, I'm not sure. I haven't heard of anyone "downgrading" the OS and keeping newer (mismatched) firmware. I'd be afraid of lack of backwards compatibility, as well.
Click to expand...
Click to collapse
Because I couldn't find the corresponding firmware . I found the stock nandroid backup and stock recovery for 1.60.708.2, but not the firmware... So I was thinking I could get away with flashing a stock ROM with earlier version and just let the OTAs do its thing and get everything up to date.
Edit: Also because if I want to get S-OFF I need to be in stock ROM anyway for firewater/sunshine
zentenk said:
Because I couldn't find the corresponding firmware . I found the stock nandroid backup and stock recovery for 1.60.708.2, but not the firmware... So I was thinking I could get away with flashing a stock ROM with earlier version and just let the OTAs do its thing and get everything up to date.
Edit: Also because if I want to get S-OFF I need to be in stock ROM anyway for firewater/sunshine
Click to expand...
Click to collapse
Yes, I understand perfectly what you are asking, and why. I just don't have an answer for you.
Just a suggestion, I would try to restore nandroid and stock recovery, and see what happens.
I think the worst that will happen, is you have to flash back to your current setup because of firmware issues.
Can someone make things clear for me ?
am S-on , firewater doesnt work
my country doesnt support payments for the sunshine
( so i cant get S-off )
so am Stuck on 4.4.3 Rom
i cant update to anything because i need a new firmware
so HTC sold us the device , and anyone who wants to update should go and get S-off ??? RIDICULOS !
i want to get an Ota and update without doing things on my COmputer
that should be okay for the latest htc device right ?
skywalker_fakih said:
i want to get an Ota and update without doing things on my COmputer
that should be okay for the latest htc device right ?
Click to expand...
Click to collapse
If there is an OTA on your version, than yes you can update that way, which will also update your firmware.
Stock ROM and stock recovery are required to OTA.
redpoint73 said:
If there is an OTA on your version, than yes you can update that way, which will also update your firmware.
Stock ROM and stock recovery are required to OTA.
Click to expand...
Click to collapse
Someone said last time that he upgraded via OTA and lost wifi
just like what happens when i flash 4.4.4 rom while S-On
skywalker_fakih said:
Someone said last time that he upgraded via OTA and lost wifi
Click to expand...
Click to collapse
A random bug, and isolated incidents (I've seen a couple of similar reports as well).
skywalker_fakih said:
just like what happens when i flash 4.4.4 rom while S-On
Click to expand...
Click to collapse
This on the other hand, I can virtually guarantee will break your WiFi.
redpoint73 said:
A random bug, and isolated incidents (I've seen a couple of similar reports as well).
This on the other hand, I can virtually guarantee will break your WiFi.
Click to expand...
Click to collapse
So i should restore my stock 4.4.2 , and ugrade to 4.4.3 with stock recovery
after that i can flash 4.4.4 custom rom ?
or i should upgrade to 4.4.4 Ota also ?
will upgrading Ota make me capable of flashing 4.4.4 custom roms ?
skywalker_fakih said:
So i should restore my stock 4.4.2 , and ugrade to 4.4.3 with stock recovery
after that i can flash 4.4.4 custom rom ?
or i should upgrade to 4.4.4 Ota also ?
will upgrading Ota make me capable of flashing 4.4.4 custom roms ?
Click to expand...
Click to collapse
Flashing a 4.4.4 ROM while on 4.4.2 or 4.4.3 firmware will result in broken WiFi (and possibly very long boot times as well). You need to be on 4.4.4 firmware, its simple as that.
Return to stock, OTA to 4.4.3, than OTA to 4.4.4. This will put you on the current firmware.
Or just s-off. I think someone on here mentioned that the sunshine devs will accept gift cards as payment for locations that don't support PayPal.
I just got an OTA notification for 5.1 too. I'm running GPE RUU rooted 5.0.1 with the latest TWRP recovery.
I got the firmware off of the link below
http://graffixnyc.com/m8.php
It has the stock recovery listed as version 3.11.1700.5. Should i flash this version or a more recent one?
Thanks in advanced for the help!
To flash the OTA you HAVE to bee 100% stock, not even root. OTA updates changed in Lollipop and if anything is different from the original system image it'll fail
EddyOS said:
To flash the OTA you HAVE to bee 100% stock, not even root. OTA updates changed in Lollipop and if anything is different from the original system image it'll fail
Click to expand...
Click to collapse
I don't think that is the case regarding root. I think installing the update will mean I will loose root but as long as I have a stock recovery and system it should install. I'm just not sure about which version recovery to use..
bentez2003 said:
I don't think that is the case regarding root. I think installing the update will mean I will loose root but as long as I have a stock recovery and system it should install. I'm just not sure about which version recovery to use..
Click to expand...
Click to collapse
Nope, it's ALL changed. In Lollipop if you're rooted, it'll fail. You HAVE to be 100% stock. It wasn't an issue pre-Lollipop, though
EddyOS said:
Nope, it's ALL changed. In Lollipop if you're rooted, it'll fail. You HAVE to be 100% stock. It wasn't an issue pre-Lollipop, though
Click to expand...
Click to collapse
Does that mean that the only way to upgrade now for people who use root, Xposed, etc. is to do a Titanium Backup and then run a full RUU upgrade to the new image?
Backup your data, restore your stock backup (which you all made, of course), restore stock recovery and then apply the update and restore your data/re-root
Hello,
I have rooted my HTC One m8(No S-OFF). It also has TWRP and it's on Android 5.0.1/HTC Sense 6
I googled and read about reverting to stock recovery and then doing an OTA upgrade of the OS. But I'd rather not go back to stock and then TWRP back again.
Is there any way or instructional to follow that can enable me to update to Android 6 whilst keeping TWRP and my root settings on.
Any help is appreciated
My experience, is that Marshmallow ROMs work fine on Lollipop firmware. I've been doing so since December, for no better reason than I've been too lazy to update my firmware.
So that means you should be able to just restore the proper Marshmallow TWRP backup for your version, and just run that without updating anything else. Although, be sure to leave yourself an escape plan, just in case it doesn't work (either your own LP backup, or be prepared to use one from the collection).
However, for best compatibility, you should really update your firmware. And doing so, either by flashing stock firmware, OTA, or RUU by "official" means (and official/signed means are what you need to use, since you are s-on) will by definition wipe out TWRP.
But honestly, flashing TWRP back to the phone is easy. You just download the .img file to your computer, than flash with a single fastboot command, with the phone connected. This is actually a fast and simple process, when compared to the other stuff you are talking about doing (restoring stock backup and recovery, OTA update).
Plus, since you are updating to Marshmallow, you'll also want to update to TWRP 3.0.2 anyway.
redpoint73 said:
My experience, is that Marshmallow ROMs work fine on Lollipop firmware. I've been doing so since December, for no better reason than I've been too lazy to update my firmware.
So that means you should be able to just restore the proper Marshmallow TWRP backup for your version, and just run that without updating anything else. Although, be sure to leave yourself an escape plan, just in case it doesn't work (either your own LP backup, or be prepared to use one from the collection).
However, for best compatibility, you should really update your firmware. And doing so, either by flashing stock firmware, OTA, or RUU by "official" means (and official/signed means are what you need to use, since you are s-on) will by definition wipe out TWRP.
But honestly, flashing TWRP back to the phone is easy. You just download the .img file to your computer, than flash with a single fastboot command, with the phone connected. This is actually a fast and simple process, when compared to the other stuff you are talking about doing (restoring stock backup and recovery, OTA update).
Plus, since you are updating to Marshmallow, you'll also want to update to TWRP 3.0.2 anyway.
Click to expand...
Click to collapse
Thanks redpoint73.
My chief motivation behind moving to Android 6 is a sound problem I've been having lately. I installed the AcousticX sound mod but when I listen to audiobooks, I hear a clipping sound sometimes.
The developer over @ AcousticX suggested a few things and one of which was making the switch to marshmallow.
thread: http://forum.xda-developers.com/showthread.php?p=68881108#post68881108
From some reading and your suggestions, I gathered the right way to go about this is, is to flash stock recovery(overriding twrp). Do an OTA upgrade(1.6 gb download/install) and afterwards reinstall TWRP and whatever else was previously done.
Am I correct in surmising this?
Thanks
AadilK said:
From some reading and your suggestions, I gathered the right way to go about this is, is to flash stock recovery(overriding twrp). Do an OTA upgrade(1.6 gb download/install) and afterwards reinstall TWRP and whatever else was previously done.
Am I correct in surmising this?
Click to expand...
Click to collapse
Not only the stock recovery, but you also need to restore the unrooted TWRP backup (never rooted ROM, "unrooting" doesn't work). Since having root will prevent OTA.
The full process is described here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The other option, depending on what M8 version you have, may be to RUU to Marshmallow. That allows you skip a lot of the steps needed in the previous method (restoring a never rooted TWRP backup, restoring stock recovery, OTA updated) but adds a couple other steps (relock bootloader to RUU, unlock it again after RUU to flash TWRP); plus the RUU will wipe all user data on the device.
So its a judgment call for you (if your version has RUU) what path is preferred.