I'm trying to update the baseband on my phone, however whenever I flash the firmware nothing happens. The phone start, but the baseband is the same 1.16.
I have an international phone, I think. I live in Canada.
This is a Rogers phone.
Running custom rom ARHD 11.1
S-OFF
The CID is ROGER001
And the HID is 0P6B16000
baseband 1.16
buildnumber 2.22.401.5
I've tried downloading the 2.22.401.5 firmware from VomerGuides, I updated the phone, but no change. I would really like help with this. Am I using the wrong update? I don't know what the latest update is anyways, but 2.22 seams like that's the one, so why is my baseband not updating?
SpaceGold said:
I'm trying to update the baseband on my phone, however whenever I flash the firmware nothing happens. The phone start, but the baseband is the same 1.16.
I have an international phone, I think. I live in Canada.
This is a Rogers phone.
Running custom rom ARHD 11.1
S-OFF
The CID is ROGER001
And the HID is 0P6B16000
baseband 1.16
buildnumber 2.22.401.5
I've tried downloading the 2.22.401.5 firmware from VomerGuides, I updated the phone, but no change. I would really like help with this. Am I using the wrong update? I don't know what the latest update is anyways, but 2.22 seams like that's the one, so why is my baseband not updating?
Click to expand...
Click to collapse
CID : ROGER001
Update your Phone(Rogers) to the latest firmware first then update to the latest ARHD.
Firmware for your device and instructions on how to flash it can be found In this post by ckpv5
Note: It's the same post from ckpv5 that I got the backups from for the Rogers.
Thank you for your help. Do I follow all his steps from 1. Or just the firmware part? Since my phone is S-off and unlocked, or what ever it was, if I do everything from 1 will that brick my phone? Or will it be safe?
EDIT:
I followed all the instructions in the end. Ended up losing root. I had to unlock bootloader and get root back. so far, the phone is back up and running. Thank you for your help.
SpaceGold said:
..... I had to unlock bootloader .....
Click to expand...
Click to collapse
If you really followed the instructions correctly ... there is no instruction that say you need to relock bootloader :silly:
I'm very new to this, but SuperSU stopped working, it told me I lost root, and recovery (TWRP) was totally gone, at the time I did not know how to get that back ether, only after... Anyways, it was a good learning experience, I'm more glad the phone did not get bricked. Anyways thank you very much for your help.
EDIT:
How or where do you go to find out what the latest firmware is? I've tried looking everywhere, and if BerndM14 didn't point out your thread, I would have never found it.
SpaceGold said:
I'm very new to this, but SuperSU stopped working, it told me I lost root, and recovery (TWRP) was totally gone, at the time I did not know how to get that back ether, only after... Anyways, it was a good learning experience, I'm more glad the phone did not get bricked. Anyways thank you very much for your help.
EDIT:
How or where do you go to find out what the latest firmware is? I've tried looking everywhere, and if BerndM14 didn't point out your thread, I would have never found it.
Click to expand...
Click to collapse
[Discussion] HTC One M8 - Updates Can get some info about updates etc in that thread. Post 3 has a collection of OTA.zips but it's still a work in progress. You'll notice that the Rogers, Telus etc isn't on there, but it'll get there eventually. You can also just hop from that thread from time to time for general info about updates, firmware or otherwise.
[CANADA] HTC One M8 Canadian Users
[GUIDE] Return to stock for Canadian HTC One M8 (2014)
Some threads for Canadian users.
Another thread, even though it's actually for backups, a lot of people head over there for stock recoveries when new updates come out, so it's a nice one to get "on top" of news if you missed it in one of the other threads.
COLLECTION of Stock backup's
Thank you very much for pointing me to those threads. Time to figure out what some of there are used for...
Related
I've just finished rooting and installed a custom ROM on my device, but now I'm looking into S-Off. My question is, how?
I did this ROM: http://forum.xda-developers.com/showthread.php?t=2706391
and now I don't have Wi-Fi, which apparently means that my firmware needs to be updated.
How, exactly, does one do that when you're no longer on the service provider it was on?
I'm on T-Mobile now, it was on AT&T. The phone is an AT&T HTC One M8.
I've got the files for Firewater, but I'm not 100% sure how to go about it, other than following tutorials I've found. Anyway, if someone could assist me in this search, it would be greatly appreciated.
Chances are firewater is not going to work, you'll need to use Sunshine S-off (pay 25$), S-off jas nothing to do with carrier
Sunshine: http://theroot.ninja
Firewater instructions: http://firewater-soff.com/instructions/
If I try Firewater, is there a chance to royally mess up my work? I.E. brick me, or will it error out beforehand?
firewater does NOT work. and will never work again. You can own the files but they won't work as it has has to establish a connection to the s-off server which is offline. sunshine is the one and only way. you can read that in the s-off thread here on xda and on their website !
and also questions belong in the Q&A section so please use that board the next time instead of the general subforum.
good luck with sunshine
Fubukiyo said:
I've just finished rooting and installed a custom ROM on my device, but now I'm looking into S-Off. My question is, how?
I did this ROM: http://forum.xda-developers.com/showthread.php?t=2706391
and now I don't have Wi-Fi, which apparently means that my firmware needs to be updated.
How, exactly, does one do that when you're no longer on the service provider it was on?
I'm on T-Mobile now, it was on AT&T. The phone is an AT&T HTC One M8.
I've got the files for Firewater, but I'm not 100% sure how to go about it, other than following tutorials I've found. Anyway, if someone could assist me in this search, it would be greatly appreciated.
Click to expand...
Click to collapse
Theirs a AT&T RUU here >>link removed by request
that will let you flash some roms here, not all
You'll have to relock your bootloader to flash it - fastboot oem lock -
and when your finished updateing unlock the bootloader and flash TWRP and root
Mr Hofs said:
firewater does NOT work. and will never work again. You can own the files but they won't work as it has has to establish a connection to the s-off server which is offline. sunshine is the one and only way. you can read that in the s-off thread here on xda and on their website !
and also questions belong in the Q&A section so please use that board the next time instead of the general subforum.
good luck with sunshine
Click to expand...
Click to collapse
Ah, see, this is the info that I couldn't find at all. I had no idea it was server-related, so it wouldn't work. I thought all the files were local, that's why I was investigating. Well, as long as Sunshine will work and not mess anything up, I guess that's what I'm going to have to do. Even though there's another ROM on my phone, I should still be able to use Sunshine and get the firmware updated without any issues, yeah? I would just like to get confirmation from someone who knows my exact situation and not search the forums to a situation "Similar" to mine and eff up my phone.
Fubukiyo said:
Ah, see, this is the info that I couldn't find at all. I had no idea it was server-related, so it wouldn't work. I thought all the files were local, that's why I was investigating. Well, as long as Sunshine will work and not mess anything up, I guess that's what I'm going to have to do. Even though there's another ROM on my phone, I should still be able to use Sunshine and get the firmware updated without any issues, yeah? I would just like to get confirmation from someone who knows my exact situation and not search the forums to a situation "Similar" to mine and eff up my phone.
Click to expand...
Click to collapse
S-OFF means do as you like, change firmwares, convert to GPE and back to sense. S-OFF is freedom
Okay, here's where I'm at, if anyone would inform me in the direction I should take...
I've unlocked the bootloader, flashed a ROM, and rooted. Wi-Fi doesn't work because I need the newer firmware on the device.
In order to get the newer firmware, I need to have S-Off. I don't. Sunshine doesn't work because the ROM I have flashed is a 5.0.1 version.
http://forum.xda-developers.com/showthread.php?t=2706391 If it helps.
Can I go digging to find a KitKat-based ROM and see if Sunshine will work then, or do I need to go through the BS to flash stock everything on my phone and THEN run Sunshine? I'd really like some advice before I royally mess something up.
Thanks in advance!
Edit: I found this and it looks like something that might work. Flash InsertCoin, download and pay for Sunshine, S-Off, flash firmware, go back to SkyDragon?
http://htc-one.wonderhowto.com/how-...-one-m8-install-custom-firmware-mods-0154461/
You simple need the stockest rom you find.. Best is restore your backup ..make it root and than do s off.. Or flash the rooted stock of mike s thread not arhd ..
Alex-V said:
You simple need the stockest rom you find.. Best is restore your backup ..make it root and than do s off.. Or flash the rooted stock of mike s thread not arhd ..
Click to expand...
Click to collapse
Forgive me for asking, but I've searched... Where is this rooted stock one you're talking about?
All right, I've flashed back to as stock as I can find, but it's still not allowing Sunshine to be installed.
However, I've stumbled upon something saying that if the Recovery is fastboot booted, it acts as though the device is S-Off? If I run the recovery in such a manner, could I possibly flash a new Firmware on there like that?
Fubukiyo said:
Forgive me for asking, but I've searched... Where is this rooted stock one you're talking about?
All right, I've flashed back to as stock as I can find, but it's still not allowing Sunshine to be installed.
However, I've stumbled upon something saying that if the Recovery is fastboot booted, it acts as though the device is S-Off? If I run the recovery in such a manner, could I possibly flash a new Firmware on there like that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2694994
I did it with that one..
Okay, here's an update:
I flashed that ROM you showed me, Alex, and then used Sunshine to S-Off my M8. That worked. I paid for it, all is well.
Flashed the Viper ROM, but didn't have Wi-Fi. So, I went back to SkyDragon, same thing.
I flashed firmware 4.28.401.9 (I think. I did typed that from memory..) but I still have no Wi-Fi.
I'm going to try to flash the GPE firmware now. I'll edit once I get it up and running!
Thanks so much guys! I really appreciate your help!
Fubukiyo said:
Okay, here's an update:
I flashed that ROM you showed me, Alex, and then used Sunshine to S-Off my M8. That worked. I paid for it, all is well.
Flashed the Viper ROM, but didn't have Wi-Fi. So, I went back to SkyDragon, same thing.
I flashed firmware 4.28.401.9 (I think. I did typed that from memory..) but I still have no Wi-Fi.
I'm going to try to flash the GPE firmware now. I'll edit once I get it up and running!
Thanks so much guys! I really appreciate your help!
Click to expand...
Click to collapse
If your wifi isn't working with ViperOne, then the firmware didn't flash correctly. Go to your bootloader/hboot and check the readout there. What it says under OS is your firmware version. If it is blank it is because of your recovery. TWRP 2.8.0.3 is recommended. You can also tell by the hboot number. 3.19 = 4.4.4 firmware
xunholyx said:
If your wifi isn't working with ViperOne, then the firmware didn't flash correctly. Go to your bootloader/hboot and check the readout there. What it says under OS is your firmware version. If it is blank it is because of your recovery. TWRP 2.8.0.3 is the recommended recovery to use with ViperOne. You can also tell by the hboot number. 3.19 = 4.4.4 firmware
Click to expand...
Click to collapse
That's awesome to know. I literally just flashed the GPE firmware, and I think I partitioned properly. (no errors while installing) It's currently doing the first boot.
Flashing that GPE firmware was nerve-racking. It went sooo slow. Here's hoping it goes through! UPDATES TO COME! I'm excited.
UPDATE:
HOLY HNNNNNNNNNNNNNG IT WORKED.
Good LORD I CAN FINALLY DOWNLOAD MY UPDATES.
Please excuse the caps, I'm effing excited right now. THANKS SO MUCH EVERYONE.
Nice that you have it working.. Don't forget.. If you want to go back to sense you need the sense firmware.. As the partitions are a bit different.. Btw I'm very happy ? with gpe 5
Alex-V said:
Nice that you have it working.. Don't forget.. If you want to go back to sense you need the sense firmware.. As the partitions are a bit different.. Btw I'm very happy ? with gpe 5
Click to expand...
Click to collapse
Right at this point, I don't care to go back to Sense firmware. I'm spoiled by the bright look of SkyDragon, so this is where I'm staying!
Hello!
I recently bought a HTC One m8 used. Sadly i did not check up on the Software and it was pre-rooted and had some older version of Viper Rom on it (2.7 i think). It was also s-on and had that bug (i believe it was a TWRP one) so it would not show me the CID nor the current version it was on. So my thought was that id like to initially get to the point where i would recieve OTA Updates again so i could update the base system to install any ROM id like. After doing research for hours and trying various stuff it seemed i could not get back to stock without the CID. So what i initially did then was use Method 2 described in this thread to Upgrade the Firmware which is now 3.28.401.9. I then change the CID to the google OTA Update one and installed the Google Play Edition Rom. The ROM was kinda buggy and did not work properly tho (i assume its still an issue that the underlying Firmware is not up-to-date enough) so i went back, changed the CID to HTC__001 and installed the stock 3.28.401.9 Rom + Recovery hoping the OTA Updates would come. It has not yet happened and i am not sure it will.
So here is my question: Will OTA Updates come if my initial CID does not match the CID i currently have even if i set it with fastboot? Is there a way for me to figure out my initial CID at this point? All i really want are working OTA Updates, after that i can install any ROM anyway, but this seems to elude me.
Thanks you!
Best Regards
ly
lyeeth said:
Hello!
I recently bought a HTC One m8 used. Sadly i did not check up on the Software and it was pre-rooted and had some older version of Viper Rom on it (2.7 i think). It was also s-on and had that bug (i believe it was a TWRP one) so it would not show me the CID nor the current version it was on. So my thought was that id like to initially get to the point where i would recieve OTA Updates again so i could update the base system to install any ROM id like. After doing research for hours and trying various stuff it seemed i could not get back to stock without the CID. So what i initially did then was use Method 2 described in this thread to Upgrade the Firmware which is now 3.28.401.9. I then change the CID to the google OTA Update one and installed the Google Play Edition Rom. The ROM was kinda buggy and did not work properly tho (i assume its still an issue that the underlying Firmware is not up-to-date enough) so i went back, changed the CID to HTC__001 and installed the stock 3.28.401.9 Rom + Recovery hoping the OTA Updates would come. It has not yet happened and i am not sure it will.
So here is my question: Will OTA Updates come if my initial CID does not match the CID i currently have even if i set it with fastboot? Is there a way for me to figure out my initial CID at this point? All i really want are working OTA Updates, after that i can install any ROM anyway, but this seems to elude me.
Thanks you!
Best Regards
ly
Click to expand...
Click to collapse
as far as I know the stock 3.28.401.9 Rom + Recovery is the newest version. Your not getting updates because their are none
clsA said:
as far as I know the stock 3.28.401.9 Rom + Recovery is the newest version. Your not getting updates because their are none
Click to expand...
Click to collapse
That makes me happy to hear. I'll just wait and hope for an early Lollipop then. Thank you!
lyeeth said:
That makes me happy to hear. I'll just wait and hope for an early Lollipop then. Thank you!
Click to expand...
Click to collapse
I do see a 3.29.401.9 firmware but I think it was a small OTA fix
try pushing your date ahead and trying to find it
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks
Run the ruu for your cid and revert to stock
rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
Click to expand...
Click to collapse
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.
rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks
Click to expand...
Click to collapse
You flashed firmware for your specific device in the firmware/RUU thread before clean flashing to the update on viper? Like iElvis said you are describing what some users have posted in a few threads where users checked the 1.40 kernel and 1.40 in base(I think, I haven't flashed viper), but didn't properly flash the firmware for their device via fastboot or RUU back to stock to get official OTA(if OTA was released from HTC for users specific device.). Hope you get it sorted out
Do you have a back up of your system before viper update? (1.90 or below) or back up ROM ?
---------- Post added at 11:05 PM ---------- Previous post was at 10:46 PM ----------
iElvis said:
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.
Click to expand...
Click to collapse
Correct me if I'm wrong, but I thought viper allowed user (sprint for example) to run their "1.40 base" on old firmware, they just had to select 1.32 kernel in aroma and would lose out on newer features
that's my main thing, I dont really know what my CID is because I superCID when installing the firmware..
iElvis said:
Are you sure you updated the firmware? You're describing the bug that arises from running 1.40 roms on 1.32 firmware.
Click to expand...
Click to collapse
im pretty sure, yes. Because It shows so in Download mode and in the about section of settings of my phone. I came across pre update error 1.90 and it fixed itself when the phone rebooted in downlaod mode.
Had this same issue, you just have to revert back to whatever firmware you were previously on,
No need to clean flash ROM again, just flash the previous firmware the same way you updated it
rpimentel1 said:
that's my main thing, I dont really know what my CID is because I superCID when installing the firmware..
Click to expand...
Click to collapse
You follow instructions and read the FAQ's posted in this thread? Your best bet is to check what firmware number is displayed on download mode, and I'm not familiar of going back to previous firmware on this device(make sure to read all info to prevent any adverse efftects), but I'd check this thread , see if your device is supported and then try restoring previous working backup if that is a plausible solution.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
rpimentel1 said:
hi guys I have updated the firmware of my m9 to 1.40 coming from 1.32.x dont remember or wrote down and now everytime I lock the screen the second time I try to unlock the phone reboots, have tried literally everything from going back to the previous firmware to wiping everything or installing elementalxm9 custom kernel.
http://forum.xda-developers.com/att-one-m9/help/m9-reboots-display-off-twice-t3126764
I am abroad for work and my life and job are basically depending on the phone. Couldnt help the itch to update tho...
Currently running viperonem9 2.30 on 1.40.401.5
thanks
Click to expand...
Click to collapse
Just flash rom and make sure your on 1.40 firwamre, DO NOT USE EX kernel, or you will have reboots.
If you want to use EX kernel, flash 1.32 firwmare.
EDIT:Are you on tmobile?Because than you need to flash back 1.32 firmware, as our installer will install older tmobile kernel in order for wifi calling to work, or you need to manual flash international boot.img if you want to keep 1.40 firmware.
BUBBA DUB'S said:
You follow instructions and read the FAQ's posted in this thread? Your best bet is to check what firmware number is displayed on download mode, and I'm not familiar of going back to previous firmware on this device(make sure to read all info to prevent any adverse efftects), but I'd check this thread , see if your device is supported and then try restoring previous working backup if that is a plausible solution.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Click to expand...
Click to collapse
ivicask said:
Just flash rom and make sure your on 1.40 firwamre, DO NOT USE EX kernel, or you will have reboots.
If you want to use EX kernel, flash 1.32 firwmare.
Click to expand...
Click to collapse
kash20 said:
Had this same issue, you just have to revert back to whatever firmware you were previously on,
No need to clean flash ROM again, just flash the previous firmware the same way you updated it
Click to expand...
Click to collapse
Ok guys so up to now I've isolated the problem. Seems to be when I try to upgrade to 1.40 that the reboots start. I successfully fully wiped to 1.32.401.8 and the reboots stopped. Then I flashed the 1.40.401.8 nowipe firmware I got from https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml and the reboots started all over again. I must be missing something regarding the compatibility of the firmwares or which version to follow which. My phone is the unlocked version and the CID is 111111. Which nowipe zip should I flash having 1.32.401.8?
rpimentel1 said:
Ok guys so up to now I've isolated the problem. Seems to be when I try to upgrade to 1.40 that the reboots start. I successfully fully wiped to 1.32.401.8 and the reboots stopped. Then I flashed the 1.40.401.8 nowipe firmware I got from https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml and the reboots started all over again. I must be missing something regarding the compatibility of the firmwares or which version to follow which. My phone is the unlocked version and the CID is 111111. Which nowipe zip should I flash having 1.32.401.8?
Click to expand...
Click to collapse
Is your device Europe based 1.32.401.8? I think your official OTA is available (see link)
https://mobile.twitter.com/LlabTooFeR/status/608567895921160192?s=09
I'd say Flash the RUU (with red text) for previous firmware (if s off) reflash stock recovery and then let the device grab the official update to 1.40.401.8 and then reflash twrp and try flashing a ROM. I'm not 100% positive on these steps, maybe @LlabTooFeR can clear this up if he has a chance. Other than that stay with what works for now until someone else provides a definite solution.
Also check out this thread
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
BUBBA DUB'S said:
Is your device Europe based 1.32.401.8? I think your official OTA is available (see link)
https://mobile.twitter.com/LlabTooFeR/status/608567895921160192?s=09
I'd say Flash the RUU (with red text) for previous firmware (if s off) reflash stock recovery and then let the device grab the official update to 1.40.401.8 and then reflash twrp and try flashing a ROM. I'm not 100% positive on these steps, maybe @LlabTooFeR can clear this up if he has a chance. Other than that stay with what works for now until someone else provides a definite solution.
Also check out this thread
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
Click to expand...
Click to collapse
What I've done up to now is go back to stock on 1.32.401.8 and then flashed the 1.40.401.8, flashed in TWRP and installing right now VIPER2.30 I just noticed I've been checking TMOBILE as a carrier which automatically gets you back to the old kernel (Which seems like the most plausible explanation on why I've been getting the reboots) as of now the phone is first booting and I'll keep everybody updated. Thanks for the help man.
rpimentel1 said:
What I've done up to now is go back to stock on 1.32.401.8 and then flashed the 1.40.401.8, flashed in TWRP and installing right now VIPER2.30 I just noticed I've been checking TMOBILE as a carrier which automatically gets you back to the old kernel (Which seems like the most plausible explanation on why I've been getting the reboots) as of now the phone is first booting and I'll keep everybody updated. Thanks for the help man.
Click to expand...
Click to collapse
No problemo, I enjoy reading into all the various options (carrier/software) to see how they differentiate from one another on the same hardware of the m9. Also a shout out to @augie7107 @kash20 @iElvis @ivicask for their expertise and making it easier to pin point the issue at hand with hopes of resolving this issue. God speed Mr rpimentel1! :good:
BUBBA DUB'S said:
No problemo, I enjoy reading into all the various options (carrier/software) to see how they differentiate from one another on the same hardware of the m9. Also a shout out to @augie7107 @kash20 @iElvis @ivicask for their expertise and making it easier to pin point the issue at hand with hopes of resolving this issue. God speed Mr rpimentel1! :good:
Click to expand...
Click to collapse
just one quick question, my phone says 0PJA11000 in the MID instead of 0PJA10000. Which version is it???
rpimentel1 said:
just one quick question, my phone says 0PJA11000 in the MID instead of 0PJA10000. Which version is it???
Click to expand...
Click to collapse
Check out this link it might help , also in the first link I posted I think I saw someone reference what you are asking but I'm not 100% sure.
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
I attempted to install lollipop OTA update on my rooted, unlocked, S-ON M8 yesterday but it wouldn't install because I had TWRP recovery enabled. Basically now I've formatted the whole thing and I can't find a stock recovery ROM for it anywhere, as it's not Verizon or Sprint etc. It's CID is H3G__001 and it is registered on contract to Three UK.
I have tried flashing many things with no success. Please help.
Try looking in this thread.
You will find a stock H3G ROM backup there, the stock recovery you need, and instructions on how to install them.
search for firmware 4.25.771.6 or 4.20.771.2 and you'll be on the right track.
x.x.771.x is always H3G__001.
I'm assuming this will be enough for you since not even I am unable to find the marshmallow firmware for H3G anywhere.
Wish you the best of luck.
Kyuubi10 said:
search for firmware 4.25.771.6 or 4.20.771.2 and you'll be on the right track.
x.x.771.x is always H3G__001.
I'm assuming this will be enough for you since not even I am unable to find the marshmallow firmware for H3G anywhere.
Wish you the best of luck.
Click to expand...
Click to collapse
No, searching for firmware won't help him, because he is S-On.
He has the OTA already downloaded, so going back to stock with the instructions and downloads provided in the link I posted is his best option.
And if "not even you" can find firmware for H3G, then this is the only option for updating to Marshmallow, short of going S-Off and flashing WWE/International firmware.
Also, in the title of the thread, going back to stock is what he requested.
xunholyx said:
No, searching for firmware won't help him, because he is S-On.
He has the OTA already downloaded, so going back to stock with the instructions and downloads provided in the link I posted is his best option.
And if "not even you" can find firmware for H3G, then this is the only option for updating to Marshmallow, short of going S-Off and flashing WWE/International firmware.
Also, in the title of the thread, going back to stock is what he requested.
Click to expand...
Click to collapse
Well, yeh. But ideally, depending on what his firmware is, he could just flash a nandroid of 4.25 and flash the corresponding custom recovery. Which is basically like going back to stock, but skipping loads of OTAs. Which is what I did.
Never the less, I didn't tell him to flash the firmware (although it is possible even with S-ON apparently), but I said that if he searched for that he would be on the right track.
Then almost anything he would have found could have helped him...a nandroid backup, or an RUU or even better advice than the one I'm able to give. (e.g. the ones I found while searching for the firmware myself)
The point is, I was simply giving directions
Hi.. I've not used my M8 for some time and I'd like to put it back on a stock rom and give it to my mother-in-law. Unfortunately I can't remember how to do much with regards to rooting, fuu, roms, etc, and I'm finding the forums a bit overwhelming.
It is an ATT phone, but the CID was changed to 11111111 so I could sim-unlock it. It's currently on 4.16.401.10, and on the ViperOneM8 v 4.6.1.
We need it to remain sim-unlocked, and on the stock rom.. I've looked around a little bit and found [tutorial] How to get back on stock with TWRP Stock Nandroid Backups. I've downloaded M8_6.12.401.4_WWE_FullStock.zip - if I flash this in TWRP will it return the phone to a stock rom, and will receive OTA updates?
Thank you for any help or answers you can give me,
mewikime
mewikime said:
Hi.. I've not used my M8 for some time and I'd like to put it back on a stock rom and give it to my mother-in-law. Unfortunately I can't remember how to do much with regards to rooting, fuu, roms, etc, and I'm finding the forums a bit overwhelming.
It is an ATT phone, but the CID was changed to 11111111 so I could sim-unlock it. It's currently on 4.16.401.10, and on the ViperOneM8 v 4.6.1.
We need it to remain sim-unlocked, and on the stock rom.. I've looked around a little bit and found [tutorial] How to get back on stock with TWRP Stock Nandroid Backups. I've downloaded M8_6.12.401.4_WWE_FullStock.zip - if I flash this in TWRP will it return the phone to a stock rom, and will receive OTA updates?
Thank you for any help or answers you can give me,
mewikime
Click to expand...
Click to collapse
You can't flash it in recovery. You need to flash it in fastboot, or via SDcard/hboot.
I've given instructions to another user recently on the ViperOneM8 thread. You can see them here.
xunholyx said:
You can't flash it in recovery. You need to flash it in fastboot, or via SDcard/hboot.
I've given instructions to another user recently on the ViperOneM8 thread. You can see them here.
Click to expand...
Click to collapse
@xunholy do I need to use 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip that you linked to in your instructions, or a different one for mine? I'm a bit nervous because that says HTC Europe, and mine is ATT in the US. I'm s-off, too, while the person you were helping there was s-on
mewikime said:
@xunholyx do I need to use 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip that you linked to in your instructions, or a different one for mine? I'm a bit nervous because that says HTC Europe, and mine is ATT in the US. I'm s-off, too, while the person you were helping there was s-on
Click to expand...
Click to collapse
If you want to keep WWE firmware, yes.
If you want to go back to AT&T firmware (and this is probably a better option for you), there is another way.
Go here (HTC's US website). Scroll down to the Manual System Update Instructions, and read them. There is an RUU download at the end of the instructions.