Q&A for [2014.10.11][GUIDE] FUU and Firmware flashing
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Firmware 3.28.401.6 with Viper 2.5.0 ?
Can i flash Viper Rom 2.5.0 on M8 with Firmware 3.28.401.6 ?
compujoe said:
Can i flash Viper Rom 2.5.0 on M8 with Firmware 3.28.401.6 ?
Click to expand...
Click to collapse
Yes. Works perfect. Best battery life ever, signal also good (for me at least).
compujoe said:
Can i flash Viper Rom 2.5.0 on M8 with Firmware 3.28.401.6 ?
Click to expand...
Click to collapse
Yes. Works perfect. Best battery life ever, signal also good (for me at least).
i also flashed the 3.xx update. im on s-off, supercid and my custom rom was viperone 2.5... when i was flashing the update, error 24 appeared. im already on supercid so i wonder why would it fail. so i reflashed the previous firmware which is 2.22.401.5.. it went well but then when im alrady on my homescreen, i notice that i don't have a signal from my mobile network and after a few minutes the phone restarts. could you help me?
angelo.bautista5 said:
i also flashed the 3.xx update. im on s-off, supercid and my custom rom was viperone 2.5... when i was flashing the update, error 24 appeared. im already on supercid so i wonder why would it fail. so i reflashed the previous firmware which is 2.22.401.5.. it went well but then when im alrady on my homescreen, i notice that i don't have a signal from my mobile network and after a few minutes the phone restarts. could you help me?
Click to expand...
Click to collapse
yea well depends... a 401 firmware did previously work for you? The new 401 firmware should then work too.
Looking at my error code list i see an error 23 which is a zip error and another close number which is also a close number and also a zip error.
I suppose there was an issue with the firmware zip you flashed. Did you verify the MD5 hash before you flashed it?
It might have been damaged during download and the zip wasn't actually flashed?
I suggest you choose the ZIP flash method and manually reflash it, then post the console window content here. It will tell me which images got flashed and what error occured (maybe). If there was no error, it means the new radio probably just doesnt work for you or the ROM and Carrier combination or something like that....
anyhow... without knowing exactly what happened, it can not be diagnosed properly.
Sneakyghost said:
yea well depends... a 401 firmware did previously work for you? The new 401 firmware should then work too.
Looking at my error code list i see an error 23 which is a zip error and another close number which is also a close number and also a zip error.
I suppose there was an issue with the firmware zip you flashed. Did you verify the MD5 hash before you flashed it?
It might have been damaged during download and the zip wasn't actually flashed?
I suggest you choose the ZIP flash method and manually reflash it, then post the console window content here. It will tell me which images got flashed and what error occured (maybe). If there was no error, it means the new radio probably just doesnt work for you or the ROM and Carrier combination or something like that....
anyhow... without knowing exactly what happened, it can not be diagnosed properly.
Click to expand...
Click to collapse
thanks. the 2.22.401 did work for me but the new 3.x.401 update after i flashed, caused (maybe) the no signal problem. i already dealed with the error 23 problem but unfortunately, as i mentioned, the signal was gone. all the method i used for flashing was fastboot. i already tried to revert to the stock rom and stock recovery that matched the original cid. what i noticed was the imei was unknown. tried to fix it but i guessed i just bricked my phone. now it is not turning on . i don't know if there is another way to unbrick it other than using jtag.
angelo.bautista5 said:
thanks. the 2.22.401 did work for me but the new 3.x.401 update after i flashed, caused (maybe) the no signal problem. i already dealed with the error 23 problem but unfortunately, as i mentioned, the signal was gone. all the method i used for flashing was fastboot. i already tried to revert to the stock rom and stock recovery that matched the original cid. what i noticed was the imei was unknown. tried to fix it but i guessed i just bricked my phone. now it is not turning on . i don't know if there is another way to unbrick it other than using jtag.
Click to expand...
Click to collapse
Try holding down the power button+vol. up for 20 seconds and see if your phone boots up. Doing this is the equivalent of a battery pull.
xunholyx said:
Try holding down the power button+vol. up for 20 seconds and see if your phone boots up. Doing this is the equivalent of a battery pull.
Click to expand...
Click to collapse
i've tried power +vol button several times already. i don't know how long i hold it but i guess it's longer than 20 seconds. but i'll still try later. do i have to do it with charger plugged or unplugged?
***Software status : Official***
After uploading new firmware 3.28.401.6 appeared in the bootloader message *** Software Status: Official ***
How to delete this?
Hi,
i have an international htc one m8 my cid is 044 and I'm using viperone rom.
can i flash any of these stock firmwares ?
And I'm S-on
lukas_system said:
After uploading new firmware 3.28.401.6 appeared in the bootloader message *** Software Status: Official ***
How to delete this?
Click to expand...
Click to collapse
Hello sir,
Please look for the guide to remove the tampered flag by @scotty1223 - that guide is also suitable for this new message, that replaces the old tampered message.
mobile post
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
ahmad.gh1 said:
Hi,
i have an international htc one m8 my cid is 044 and I'm using viperone rom.
can i flash any of these stock firmwares ?
And I'm S-on
Click to expand...
Click to collapse
Hello sir, in order to use my firmware you'll need to S-OFF first.
As stated in post #1, this is not for S-ON users.
Other than that, if your CID is HTC__044, this firmware is for your device as well.
mobile post
Thanx for guide !!!
Its work
I can see some people mention 3.28.401.7 FW, but you have the 3.28.401.6. Any reason to use x.7 instead of x.6?
P.S.: i love your FUU ?
/ Sent from my phone /
jkolner said:
I can see some people mention 3.28.401.7 FW, but you have the 3.28.401.6. Any reason to use x.7 instead of x.6?
P.S.: i love your FUU ?
/ Sent from my phone /
Click to expand...
Click to collapse
No mate. All i know is it contains a fix for croatia. Its been rolled out to other countries too though, so i made FUU's and ZIP's because i guess there are more fixes in there. Just don't know what yet.
This was a totally blind update. Tested, yes, but not taken apart and looked at like i usually do. I have NO clue whats inside. Only thing i checked is Recovery and whether or not it was updated. Yes it was.
Anyhow, HTC often doesn't do much more like build date changes. Sometimes, hboots or recoveries get pushed out that are just newer, but not changed.
They have a streamlined building process and if they update one major thing, they often just automatically build a RUU or OTA Firmware and all files get new build date stamps. At least that is what i have seen occasionally in the past. Files that are 100% identical in hex view except the file header that contains the creation date.
*** Software Status: Official ***
Sneakyghost said:
Hello sir,
Please look for the guide to remove the tampered flag by @scotty1223 - that guide is also suitable for this new message, that replaces the old tampered message.
mobile post
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
Hello sir, in order to use my firmware you'll need to S-OFF first.
As stated in post #1, this is not for S-ON users.
Other than that, if your CID is HTC__044, this firmware is for your device as well.
mobile post
Click to expand...
Click to collapse
so I tried the method 'tampered flag' from scotty1223 and does not work. Next I *** Software Status: Official ***
I FW 3.28.401.7
lukas_system said:
so I tried the method 'tampered flag' from scotty1223 and does not work. Next I *** Software Status: Official ***
I FW 3.28.401.7
Click to expand...
Click to collapse
Well, you will need to ask Scotty1223 then. I am not really able to support that method. I never used it myself.
HTC_Asia_TW
hi..is the 3.xx firmware for HTC_Asia_TW out yet?
mine is CID HTC__621, MID is 0P6B11000
xuldigiorgio said:
hi..is the 3.xx firmware for HTC_Asia_TW out yet?
mine is CID HTC__621, MID is 0P6B11000
Click to expand...
Click to collapse
Hi Sir,
unfortunately i do not know where to look to keep track of Asia Firmware. I rely on my users to send me such.
@Sneakyghost thank you man, i'm very very rookie about Android but with your guide and little bit help of google, now my M8 is 4.4.4 with Venom 3.0.1 thanks again and god bless you, i owe you a coffee
Related
Hey guys, I'm running ViperOne 2.4.0. with TWRP recovery installed. For some reason when it boots up, the only thing it shows is an unusual HTC splash screen with red writing at the bottom, similar to if it were booting into recovery, but without the pink "entering recovery" message at the top. What is causing this, can it be changed by adding a new splash screen and/or boot animation? It just stays on this screen for a painfully long time, and then goes black. I tap the screen and it's on, and everything is fine. Thanks in advance.
chattguy said:
Hey guys, I'm running ViperOne 2.4.0. with TWRP recovery installed. For some reason when it boots up, the only thing it shows is an unusual HTC splash screen with red writing at the bottom, similar to if it were booting into recovery, but without the pink "entering recovery" message at the top. What is causing this, can it be changed by adding a new splash screen and/or boot animation? It just stays on this screen for a painfully long time, and then goes black. I tap the screen and it's on, and everything is fine. Thanks in advance.
Click to expand...
Click to collapse
I've got the same issue..... plz help.
Because you guys on the lower version firmware which is meant for 4.4.2
And the ROM requires a newer firmware for 4.4.3
ckpv5 said:
Because you guys on the lower version firmware which is meant for 4.4.2
And the ROM requires a newer firmware for 4.4.3
Click to expand...
Click to collapse
Okay.....so can I update the firmware? Do I have to be truly S-off to do that?
chattguy said:
Okay.....so can I update the firmware? Do I have to be truly S-off to do that?
Click to expand...
Click to collapse
You don't need S-Off to upgrade firmware with official untouched firmware.
With S-On you can't downgrade.
I believe your device is T-Mobile so grab the OTA.zip from T-Mobile section and extract out the firmware and use it.
Or.. do a proper OTA update.... or use the RUU ... all your answers are in T-Mobile section
---------- Post added at 12:24 AM ---------- Previous post was at 12:20 AM ----------
oogierule said:
I've got the same issue..... plz help.
Click to expand...
Click to collapse
And yours ... the same as above but the AT&T ones in AT&T section
ckpv5 said:
You don't need S-Off to upgrade firmware with official untouched firmware.
With S-On you can't downgrade.
I believe your device is T-Mobile so grab the OTA.zip from T-Mobile section and extract out the firmware and use it.
Or.. do a proper OTA update.... or use the RUU ... all your answers are in T-Mobile section
---------- Post added at 12:24 AM ---------- Previous post was at 12:20 AM ----------
And yours ... the same as above but the AT&T ones in AT&T section
Click to expand...
Click to collapse
Okay, and to find out the current firmware I'm running, that's listed as "Build Number" in settings, yes? It says I'm currently running 2.22.531.5 CL365360 release-keys. Is there a newer firmware than that? If so I'm not finding it.
chattguy said:
Okay, and to find out the current firmware I'm running, that's listed as "Build Number" in settings, yes? It says I'm currently running 2.22.531.5 CL365360 release-keys. Is there a newer firmware than that? If so I'm not finding it.
Click to expand...
Click to collapse
I never know a Viper ROM is based on 2.22.531.5 CL365360 release-keys Your OP is mentioning about Viper.
Firmware is what written on bootloader - OS : ?????????
In Build Number in settings is the ROM version.
Well I guess I need to stop responding to Q&A for devices which have their own specific forum ....
I know nothing when it comes to T-Mobile, AT&T, Sprint and Verizon ... sorry
users with specific device can understand better and offer a better help and advice.
always wondering why people with specific device with specific forum post in Int'l GSM forum
ckpv5 said:
I never know a Viper ROM is based on 2.22.531.5 CL365360 release-keys Your OP is mentioning about Viper.
Firmware is what written on bootloader - OS : ?????????
In Build Number in settings is the ROM version.
Well I guess I need to stop responding to Q&A for devices which have their own specific forum ....
I know nothing when it comes to T-Mobile, AT&T, Sprint and Verizon ... sorry
users with specific device can understand better and offer a better help and advice.
always wondering why people with specific device with specific forum post in Int'l GSM forum
Click to expand...
Click to collapse
First of all, this isn't an "international GSM" forum. It's an HTC One M8 forum. That to me, means that it's for all users of this particular phone. Second, there is nothing that explains in explicit detail how I can fix this particular problem, in the T-Mo specific forum. Anyway, thanks.
chattguy said:
First of all, this isn't an "international GSM" forum. It's an HTC One M8 forum. That to me, means that it's for all users of this particular phone. Second, there is nothing that explains in explicit detail how I can fix this particular problem, in the T-Mo specific forum. Anyway, thanks.
Click to expand...
Click to collapse
No problem about that ... it just me need to learn not to respond to specific device Q&A
Anyway ...about the firmware ... what is it ? Not the one written in build numbers ... what's the one written on bootloader ?
ckpv5 said:
No problem about that ... it just me need to learn not to respond to specific device Q&A
Anyway ...about the firmware ... what is it ? Not the one written in build numbers ... what's the one written on bootloader ?
Click to expand...
Click to collapse
Here's what it says:
HBOOT 3.16.0.0000
Radio-1.16.21331931.LA24G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
chattguy said:
Here's what it says:
HBOOT 3.16.0.0000
Radio-1.16.21331931.LA24G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Click to expand...
Click to collapse
That's what I'm trying to tell.
You do have a lower version firmware meant for 4.4.2 (the reason why it takes long time to boot and the black screen)
Firmware 4.4.3 has hboot 3.18.0.000 or greater than 3.16.0.0000
ckpv5 said:
That's what I'm trying to tell.
You do have a lower version firmware meant for 4.4.2 (the reason why it takes long time to boot and the black screen)
Firmware 4.4.3 has hboot 3.18.0.000 or greater than 3.16.0.0000
Click to expand...
Click to collapse
Do I flash this in Hboot? Do I need to be on a stock rom, or S-off? I'd rather not have to deal with that if I can help it.
chattguy said:
Do I flash this in Hboot? Do I need to be on a stock rom, or S-off? I'd rather not have to deal with that if I can help it.
Click to expand...
Click to collapse
There is no need to go for S-Off if you don't need it. The only thing is once you updated to 4.4.3, S-Off thru SunShine may not work too. (currently)
So it's all depends on what you want/prefer to do :
1. backup your current Viper ROM and revert to stock ROM and do normal OTA (no need to relock bootloader)
Once complete, reinstall TWRP and restore your Viper ROM backup (so no reinstalling hassle)
or
2. revert to stock ROM with RUU (you need to relock bootloader)
Once complete, you need to reunlock bootloader and install TWRP and restore your backup.
or
3. keep/backup your current setup of Viper ROM and flash only the HTC signed firmware either thru fastboot or use a external_sdcard method. Both way you need to relock bootloader and re-unlock again after complete. Always remember unlocking bootloader will wipe your data. So make a backup to PC first. And you need to reflash TWRP too. You can try without relock bootloader first and see as I can't remember whether it will work on an unlocked bootloader or not. If not working, then try again with relocked bootloader.
I guess you can have all the info and files needed in this thread : http://forum.xda-developers.com/showthread.php?t=2714456
ckpv5 said:
There is no need to go for S-Off if you don't need it. The only thing is once you updated to 4.4.3, S-Off thru SunShine may not work too. (currently)
So it's all depends on what you want/prefer to do :
1. backup your current Viper ROM and revert to stock ROM and do normal OTA (no need to relock bootloader)
Once complete, reinstall TWRP and restore your Viper ROM backup (so no reinstalling hassle)
or
2. revert to stock ROM with RUU (you need to relock bootloader)
Once complete, you need to reunlock bootloader and install TWRP and restore your backup.
or
3. keep/backup your current setup of Viper ROM and flash only the HTC signed firmware either thru fastboot or use a external_sdcard method. Both way you need to relock bootloader and re-unlock again after complete. Always remember unlocking bootloader will wipe your data. So make a backup to PC first. And you need to reflash TWRP too. You can try without relock bootloader first and see as I can't remember whether it will work on an unlocked bootloader or not. If not working, then try again with relocked bootloader.
I guess you can have all the info and files needed in this thread : http://forum.xda-developers.com/showthread.php?t=2714456
Click to expand...
Click to collapse
Okay thanks man. None of that sounds like something I feel like doing this weekend. I'll see how I feel Monday and attempt it. Many thanks for your patience.
Speaking personally, I would say if you currently have the ability to s-off you may as well do it and save yourself some headaches. Reason being, if you're s-off you can, for example, flash a modified firmware that doesn't erase your rom or bootloader, which to me, is a lot less confusing and troublesome. You can also do things like flash different radios, animations, etc without installing new roms and what not. Anyways, that's just my opinion and I don't claim to be an expert or anything, just another random user.
Q&A for Firmware Flashing without the panic attacks...
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
LTE bands
Hi all,
I have an AT&T HTC One M8 with stock firmware and Android Revolution HD 11.1 with working LTE.
If I upgrade the firmware to the latest worldwide version, will I lose access to LTE since the LTE bands are different?
In other words, are the LTE bands tied to the phone hardware or SIM card or firmware?
panther757 said:
Hi all,
I have an AT&T HTC One M8 with stock firmware and Android Revolution HD 11.1 with working LTE.
If I upgrade the firmware to the latest worldwide version, will I lose access to LTE since the LTE bands are different?
In other words, are the LTE bands tied to the phone hardware or SIM card or firmware?
Click to expand...
Click to collapse
It's tied to your phone firmware. Just like their are phones that are 3g only.
cant update firmware to 3.28 from 2.23
Hi , i have an ATT htc one M8 running on viperone 2.5.0 with 2.23 FW. i am trying to update to 3.28, Ive read all over the thread and people who had the same problem as me, was fixed by downloading the firmware from a different browser or showing hidden extensions, i have done both and still no luck. this is what i am doing
1. downloaded the firmware 3.28
2. renamed it to 0P6BIMG.zip , placed in external SD
3. adb reboot bootloader
4. SD CHECKING..
Loading..[0P6DIAG.zip]
No image!
Loading..[0P6DIAG.nbh]
no image or wrong image!
loading..[0P6BIMG.zip]
Wrong zipped image!
can someone please tell me what i am doing wrong, been trying all sorts of things for the past week.
Super CID and MID should match the EU unlocked version.
HTC One M8
ramenn0odles said:
Hi , i have an ATT htc one M8 running on viperone 2.5.0 with 2.23 FW. i am trying to update to 3.28, Ive read all over the thread and people who had the same problem as me, was fixed by downloading the firmware from a different browser or showing hidden extensions, i have done both and still no luck. this is what i am doing
1. downloaded the firmware 3.28
2. renamed it to 0P6BIMG.zip , placed in external SD
3. adb reboot bootloader
4. SD CHECKING..
Loading..[0P6DIAG.zip]
No image!
Loading..[0P6DIAG.nbh]
no image or wrong image!
loading..[0P6BIMG.zip]
Wrong zipped image!
can someone please tell me what i am doing wrong, been trying all sorts of things for the past week.
Click to expand...
Click to collapse
Are you S-Off and SuperCID?
xunholyx said:
Are you S-Off and SuperCID?
Click to expand...
Click to collapse
Just got it to update. I thought it i already supercid but i forgot the last "1" , thank you for your help friend, much appreciated
You awesome dude
Work for me
Thanx before
And achieves up to firmware version 2.22.401.5 not understand the procedures well !! Now I have to get a rom with 2.22.401.5 FW to be able to make the next update or what is the next procedure to doing the update to install 4.4.4
hdelvalle009 said:
And achieves up to firmware version 2.22.401.5 not understand the procedures well !! Now I have to get a rom with 2.22.401.5 FW to be able to make the next update or what is the next procedure to doing the update to install 4.4.4
Click to expand...
Click to collapse
What is it that you are trying to do ? Maybe I can help
jxcorex28 said:
What is it that you are trying to do ? Maybe I can help
Click to expand...
Click to collapse
I want to upgrade the FW to use 4.4.4. I've made up my FW to version 2.22.401.5 the other problem is i dont have pc.
hdelvalle009 said:
I want to upgrade the FW to use 4.4.4. I've made up my FW to version 2.22.401.5 the other problem is i dont have pc.
Click to expand...
Click to collapse
Don't need one read the op
---------- Post added at 07:33 PM ---------- Previous post was at 07:29 PM ----------
I have had three phones over the past five years and only once ever used a computer for flashing firmware radios ROMs etc. You don't need one if you do your research
str8str said:
Don't need one read the op
---------- Post added at 07:33 PM ---------- Previous post was at 07:29 PM ----------
I have had three phones over the past five years and only once ever used a computer for flashing firmware radios ROMs etc. You don't need one if you do your research
Click to expand...
Click to collapse
OP?
sorry, not much English I'm trying to reach for translator ...
You don't need a pc unless you want to learn how to use fastboot and adb commands. I , no longer use toolkits as it limits your ability to learn ...
Check out this thread for information about firmware flashing w/o a pc
http://forum.xda-developers.com/showthread.php?t=2824048
OP = Original Post... As in the first post of this thread.
Except you are in the Questions & Answers thread...
m8 firmware update
Hi, I tried this method to update my firmware from 4.4.3 to 4.4.4 but it doesn't work out for me. Maybe I didn't know how to do?. Hboot always say Model id incorrect. I can't understand. I need help to update my HTC one m8( CID__ 622) firmware to latest 4.4.4(GSM). Please I do need some help,thanks
Very easy
help
markmart74 said:
Very easy
Click to expand...
Click to collapse
Hi man,how did you do it? My firmware version now is 2.22.401.5 how can I update to the latest firmware version with this method? I'm s-off. Please help.thanks
Skippersway said:
Hi man,how did you do it? My firmware version now is 2.22.401.5 how can I update to the latest firmware version with this method? I'm s-off. Please help.thanks
Click to expand...
Click to collapse
You can go to the fw file and extract.
Android info text and edit. Add in your cid like shown. Compress extracted file. I think that's how you do it...
Or just supercid
firmare update
markmart74 said:
You can go to the fw file and extract.
Android info text and edit. Add in your cid like shown. Compress extracted file. I think that's how you do it...
Or just supercid
Click to expand...
Click to collapse
Thank you so much for your help. Though yet I couldn't update,your help was very good. I followed the instructions and the thumbnails but when I get to HBOOT it ONLY appeared press power to reboot and it never updated. I am sorry to ask for more help and to correct my first mistake,my cidnum is HTC_622. I did with this cidnum but it couldn't..or maybe it is because my bootloader is unlocked? Do I have to do something specific to be able to update? I am not supercid..I am currently using viperone m8 Rom version 2.22.401.5 and supersu running on the phone. Thank you again for your help.
Plz help. I have htc one m8 developer edition its s_on, unlocked, tampered. I want to know will i ever receive ota updates? Because I'm still on 4.4.2.
w69 said:
Plz help. I have htc one m8 developer edition its s_on, unlocked, tampered. I want to know will i ever receive ota updates? Because I'm still on 4.4.2.
Click to expand...
Click to collapse
If it is a true developer edition, you might try backing up, running one of the Developer Edition RUU's to get back to 100% stock, and then see if you can get the OTA update. If this was a conversion, make sure the CID/MID are correct (which requires S-off).
w69 said:
Plz help. I have htc one m8 developer edition its s_on, unlocked, tampered. I want to know will i ever receive ota updates? Because I'm still on 4.4.2.
Click to expand...
Click to collapse
If its truly the Dev Edition, on the stock ROM and stock recovery, you should get OTA.
insert coin
redpoint73 said:
If its truly the Dev Edition, on the stock ROM and stock recovery, you should get OTA.
Click to expand...
Click to collapse
bro i doubt its stock because it is also showin insert coin. are insert coin roms stock or custom??
w69 said:
Plz help. I have htc one m8 developer edition its s_on, unlocked, tampered. I want to know will i ever receive ota updates? Because I'm still on 4.4.2.
Click to expand...
Click to collapse
lock the bootloader and flash then newest RUU
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Then simply unlock the bootloader
flash TWRP recovery and SuperSU and a kernel if you need system r/w
w69 said:
bro i doubt its stock because it is also showin insert coin. are insert coin roms stock or custom??
Click to expand...
Click to collapse
Then why did you state in the thread title and OP "stock"?
InsertCoin is a custom ROM and not stock. So you need to return to a stock ROM to install OTA.
---------- Post added at 10:08 AM ---------- Previous post was at 10:07 AM ----------
clsA said:
lock the bootloader and flash then newest RUU
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Click to expand...
Click to collapse
1540 is US Dev Edition, and the OP has Euro DE. The RUU likely will not run with incorrect CID, MID. And not sure this is the stock baseline he would want to be on.
Htc one m8 CID: 002, european, stock demo rom (receiving ota)
redpoint73 said:
Then why did you state in the thread title and OP "stock"?
InsertCoin is a custom ROM and not stock. So you need to return to a stock ROM to install OTA.
---------- Post added at 10:08 AM ---------- Previous post was at 10:07 AM ----------
1540 is US Dev Edition, and the OP has Euro DE. The RUU likely will not run with incorrect CID, MID. And not sure this is the stock baseline he would want to be on.
Click to expand...
Click to collapse
ok i changed the custom insert coin rom to this demo rom unfortunately. yet my device is S-on, unlocked boot loader, its cid is 002, european model. the problem is i cant flash any other rom on this demo version rom. i only need a 100% stock rom (sense) to receive ota updates in future. plz reply asap cant use my phone the demo app comes again and again.
w69 said:
ok i changed the custom insert coin rom to this demo rom unfortunately. yet my device is S-on, unlocked boot loader, its cid is 002, european model. the problem is i cant flash any other rom on this demo version rom. i only need a 100% stock rom (sense) to receive ota updates in future. plz reply asap cant use my phone the demo app comes again and again.
Click to expand...
Click to collapse
Whats a Demo Rom ?
do you have TWRP installed ?
Install this >> http://www.androidrevolution.org/downloader/download.php?file=One_M8_2.22.401.4_odexed.zip
That will get the phone working and Sunshine should get you s-off
clsA said:
Whats a Demo Rom ?
do you have TWRP installed ?
Install this >> http://www.androidrevolution.org/downloader/download.php?file=One_M8_2.22.401.4_odexed.zip
That will get the phone working and Sunshine should get you s-off
Click to expand...
Click to collapse
yes i have twrp-2.8.1.0 installed. demo roms are those roms like in shops they have demo phones with playing demo videos again again in it. this rom is only supporting 2G. i used this link http://forum.xda-developers.com/showthread.php?t=2735235 and copied the odexted zip to twrp. it runs successfully but after that phone is in same old condition. is it true that the odexted rom is not installing because im S_ON??
and tell me if i S_OFF will i get ota updates with the odexted rom? sunshine needs 25$. well havnt tried firewater on this demo rom. and bro the link u sent is not working.
w69 said:
is it true that the odexted rom is not installing because im S_ON??
Click to expand...
Click to collapse
Don't know where you obtained that info, but its false. S-off is not needed to install any ROMs.
If the phone is a demo unit, you should have stated that right away in your top post. On a previous HTC device (One X) I believe the demo unit was very difficult, if not impossible to make fully functioning. But no idea if the same is true for the M8 demo unit you have.
redpoint73 said:
Don't know where you obtained that info, but its false. S-off is not needed to install any ROMs.
If the phone is a demo unit, you should have stated that right away in your top post. On a previous HTC device (One X) I believe the demo unit was very difficult, if not impossible to make fully functioning. But no idea if the same is true for the M8 demo unit you have.
Click to expand...
Click to collapse
i have no ideo what was it. i got it from ebay. it had a custom rom 4.4.2 insert coin.i was not receiving fota thats y i thought to shift to full stock. on a facebook page of htc one M8 someone sent me a link to flash it and said its full stock rom. i flashed it with twrp but i came out demo. now im stuck. someone told if me i flash a custom rom again it will be fixed even if its S-ON. kindly tell me a good updated custom rom which doesnot require S-OFF.
w69 said:
on a facebook page of htc one M8 someone sent me a link to flash it and said its full stock rom.
Click to expand...
Click to collapse
Sounds like you just got some random advice, with an unknown link and flashed it. Why on earth would you do such a thing? Stick to XDA, at least here you can go by reputation (number of thanks, Recongnized Contibutor, or Recognized Dev titles).
w69 said:
someone told if me i flash a custom rom again it will be fixed even if its S-ON. kindly tell me a good updated custom rom which doesnot require S-OFF.
Click to expand...
Click to collapse
As I just said in my last response, you do not need S-off to flash any ROMs. If you want help, you need to start actually paying attention to the help that is being given to you. You are also making it very hard to help you, by not giving enough info, and just leaking it out little by little.
You say you can't flash any other ROMs, but that isn't enough information. What happens when you try to flash? Does it fail with an error message? Or flash successful, but doesn't boot? What other ROMs have you tried?
If you want to return to stock to receive OTAs, you will need to find and flash the appropriate nandroid and stock recovery for our CID. Stock backup collection can be found sticky at the top of the General section. There are also various guides on how to return to stock, if you need them just search.
redpoint73 said:
Sounds like you just got some random advice, with an unknown link and flashed it. Why on earth would you do such a thing? Stick to XDA, at least here you can go by reputation (number of thanks, Recongnized Contibutor, or Recognized Dev titles).
As I just said in my last response, you do not need S-off to flash any ROMs. If you want help, you need to start actually paying attention to the help that is being given to you. You are also making it very hard to help you, by not giving enough info, and just leaking it out little by little.
You say you can't flash any other ROMs, but that isn't enough information. What happens when you try to flash? Does it fail with an error message? Or flash successful, but doesn't boot? What other ROMs have you tried?
If you want to return to stock to receive OTAs, you will need to find and flash the appropriate nandroid and stock recovery for our CID. Stock backup collection can be found sticky at the top of the General section. There are also various guides on how to return to stock, if you need them just search.
Click to expand...
Click to collapse
Thanx a lot for your help and concern. now i have installed android revolution rom. i think its good. will see for L rom in future. but the problem was that i found exact rom and rocovery for my device which is 401 wwe european having cid 002 latest HBoot . flashed it and flashing was successful but when i reboot the device its still the same. means the flash didnt work. yes u are right i was leaking out info a little. it was because i knew my device a little and i didnt know what is the current status of my device. now after reasearch of few days my mind is clear. thanx for your help and interest again. this page is a blessing for beginners like me.
w69 said:
Thanx a lot for your help and concern. now i have installed android revolution rom. i think its good. will see for L rom in future. but the problem was that i found exact rom and rocovery for my device which is 401 wwe european having cid 002 latest HBoot . flashed it and flashing was successful but when i reboot the device its still the same. means the flash didnt work. yes u are right i was leaking out info a little. it was because i knew my device a little and i didnt know what is the current status of my device. now after reasearch of few days my mind is clear. thanx for your help and interest again. this page is a blessing for beginners like me.
Click to expand...
Click to collapse
I glad you got it working .. sorry about the dead link, i wish Mike would leave the old version on his site longer
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
Hello
My htc one m8 is the Asian version (HTC__044) , upon using getvar all, I noticed that my version-main was missing along with the os in hboot. If I were to flash a firmware, would I need to relock the bootloader? Would I lose my data on locking the bootloader? Also, im on base .401 , would I directly be able to flash a .707?
Thanks in advance.
wasdapple said:
If I were to flash a firmware, would I need to relock the bootloader?
Click to expand...
Click to collapse
If s-on, yes. Otherwise if s-off, no.
Also, be aware that with s-on you can only flash a firmware that is HTC signed/encrypted. Some are not, and require s-off.
wasdapple said:
Would I lose my data on locking the bootloader?
Click to expand...
Click to collapse
Yes.
wasdapple said:
Also, im on base .401 , would I directly be able to flash a .707?
Click to expand...
Click to collapse
How are you determining 401? From what I'm seeing, the stock software/firmware for your CID should be 707.
You should be able to flash 707 firmware (assume you want to update to Lollipop) on your version, provided the previously mentioned requirements are met.
redpoint73 said:
If s-on, yes. Otherwise if s-off, no.
Also, be aware that with s-on you can only flash a firmware that is HTC signed/encrypted. Some are not, and require s-off.
Yes.
How are you determining 401? From what I'm seeing, the stock software/firmware for your CID should be 707.
You should be able to flash 707 firmware (assume you want to update to Lollipop) on your version, provided the previously mentioned requirements are met.
Click to expand...
Click to collapse
Thanks for replying. I believe it may have been the rom ive installed that changed my firmware, along with the fact it writes .401 on my software information page. Yes the default firmware should be .707 which I believe is also the main cause of my inability to connect to 4g in my area.
So assuming I find a signed firmware for .707 I would simply be able to flash it on the .401? Or would I have to still relock my bootloader.
Also, would the empty os/ version-main be a problem and if so how do I fix it.
Thanks for replying as you've also helped me a great deal the previous time.
wasdapple said:
I believe it may have been the rom ive installed that changed my firmware, along with the fact it writes .401 on my software information page.
Click to expand...
Click to collapse
Flashing a ROM will not change your firmware. It does change software number, so if that is where you are getting 401 from, that is normal. Software number is just the base of your current ROM, not your firmware number.
Your firmware number is indicated on your bootloader screen under "OS" and also as "main version" when doing getvar all.
wasdapple said:
So assuming I find a signed firmware for .707 I would simply be able to flash it on the .401? Or would I have to still relock my bootloader.
Click to expand...
Click to collapse
Are you s-on or s-off?
If still s-on, there is no way you could have ever flashed a 401 firmware on your phone. I still think you are confused between software and firmware numbers, and I don't guess that you ever flashed a 401 firmware.
If you are s-on, I still think you are on 707 firmware, and there is some other factor causing your 4G problem.
Yes, you need to relock your bootloader to flash 707 firmware while s-on. If you are s-off, you don't need to relock the bootloader.
wasdapple said:
Also, would the empty os/ version-main be a problem and if so how do I fix it.
Click to expand...
Click to collapse
It shouldn't be a problem. It will be fixed if you flash a firmware.
This bug was caused by older versions of TWRP. If you flash a current version of TWRP after flashing firmware, the problem should not re-occur.
---------- Post added at 10:19 AM ---------- Previous post was at 10:17 AM ----------
wasdapple said:
Thanks for replying as you've also helped me a great deal the previous time.
Click to expand...
Click to collapse
We always like repeat customers, and satisfied ones.
So is it possible that I am actually on 707 but my rom is making it show 401? Im terribly sorry for my lack of understanding of this whole situation.
Would using the twrp app on the play store update twrp? It should fix the empty main-version ?
wasdapple said:
So is it possible that I am actually on 707 but my rom is making it show 401? Im terribly sorry for my lack of understanding of this whole situation.
Click to expand...
Click to collapse
I know in the past, folks have often used the word "firmware" to mean the same as the ROM. But you should probably erase that notion from your mind. On this device, the word "firmware" is used specifically to partitions that are not flashed when you flash a ROM, and include hboot, radio, WiFi, Bluetooth, and others.
Yes, your firmware may still be 707 (which can normally be found as OS number on hboot screen, or main version when doing getvar all); while your software (ROM) which is shown in Settings>About>Software information can be 401. Firmware and ROM are 2 completely different things.
I've asked twice now, are you s-on or s-off?
wasdapple said:
Would using the twrp app on the play store update twrp? It should fix the empty main-version ?
Click to expand...
Click to collapse
TWRP Manager app will update TWRP, yes.
You can also just download the latest version and flash with fastboot, which is my preferred method: https://twrp.me/devices/htconem8gsm.html
However, this alone won't fix the issue of main version missing, I don't believe. It will only stop if from re-occurring. But the only way to get the main version back is to flash a firmware. After that, having an updated TWRP will stop if from main version displaying "blank" again. If you use an old TWRP, it will blank out the main version again.
Get it?
I'm sorry I kept forgetting to reply to that, I am actually s-on.
So for instance I want to be back on 707 I should just revert to rooted stock?
wasdapple said:
I'm sorry I kept forgetting to reply to that, I am actually s-on.
Click to expand...
Click to collapse
Than its simply impossible for you to ever have flashed a 401 firmware. Some of the firmware partitions (hboot, radio) are write protected with s-on, and can only be flashed with your CID version firmware (707).
wasdapple said:
So for instance I want to be back on 707 I should just revert to rooted stock?
Click to expand...
Click to collapse
Yes, rooted or unrooted should be fine.
But you will want to make sure your firmware and software versions match up. What are your hboot and radio numbers? Do you remember if you were on Lollipop before unlocking the bootloader?
My hboot would be 3.19.0.0000 and my radio is 1.25.21331147A1.06G
Yep I was on lollipop before unlocking my bootloader.
wasdapple said:
My hboot would be 3.19.0.0000 and my radio is 1.25.21331147A1.06G
Yep I was on lollipop before unlocking my bootloader.
Click to expand...
Click to collapse
You can get the stock 4.19.707.2 nandrioid here (Post #2): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Keep in mind, this is a TWRP "nandroid" backup, not a flashable ROM zip. So follow the directions carefully to restore this stock nandroid.
Also note that this is the stock ROM, not the firmware.
Would I get back my 707 if I flashed this instead http://forum.xda-developers.com/htc...-sd-14-19-707-21st-android-5-0-sense-t3010391 ?
im seeing an Asian wwe base and it is 707.
Also I wouldn't be able to dirty flash a completely different rom right?
wasdapple said:
Would I get back my 707 if I flashed this instead http://forum.xda-developers.com/htc...-sd-14-19-707-21st-android-5-0-sense-t3010391 ?
Click to expand...
Click to collapse
Not sure what you mean by "get back my 707", and you need to explain more clearly.
If the intent is to return to 707 firmware, its not needed, I'm confidant you already are on current 707 firmware. And flashing a ROM does not change your firmware (as I've already explained multiple times).
If the intent is to make the main version appear again, flashing a ROM won't do that either. As mentioned, you can only make that reappear by flashing a firmware.zip (not a ROM.zip).
If the intent is to just return to a 707 ROM base, then yes the ROM you linked will do that. But the only reason I see for you to do so, is to see if it helps your network issue. Using ROMs of other bases will not normally affect network service (as long as your carrier's APN is correct). And I've already linked you to stock 707 nandroid, which is probably the best baseline to troubleshoot from. Or are you not comfortable with the nandroid restore process?
Again, you haven't really explained what you are trying to accompish; so its hard to answer the question.
wasdapple said:
Also I wouldn't be able to dirty flash a completely different rom right?
Click to expand...
Click to collapse
If the ROM is a similar enough base, it might be possible to dirty flash. But its not recommended, and still possible to have various severe bugs, or not even boot. Therefore, full wipe is normally recommended when moving between different ROMs (and often even major updates of the "same" ROM).
Any person flashing ROMs should know how to backup and restore their personal data (using Titanium Backup and/or other means) when moving between ROMs.
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
I've actually been trying to update the firmware on my M8 today as well, but when I go to "flashboot flash zip firmware.zip" I am returned the message "not enough space."
I've cleared the cache successfully, and that didn't open up enough space. I tried to delete userdata, but it wouldn't let me do it remotely.
So I'm a little confused as to my next move here...
and I've relocked my phone and s-on.
wasdapple said:
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
Click to expand...
Click to collapse
Yes. You will get your software number back if you flash a 707 based ROM, such as stock.
So, here we go.
Download this 4.19.707.2 RUU onto your PC
When the download is finished, plug your phone into your PC, double click on the downloaded file, and follow the prompts. This will update you to Lollipop and you will be on the stock ROM again.
Since you are S-On, you will first need to relock the bootloader.
In fastboot (obviously) fastboot oem lock before you proceed with this.
Also, THIS WILL WIPE YOUR PHONE, so be sure to backup anything that is important to you.
Is the ruu rooted, or purely stock pre-root?
Kindrex said:
I've actually been trying to update the firmware on my M8 today as well, but when I go to "flashboot flash zip firmware.zip" I am returned the message "not enough space."
I've cleared the cache successfully, and that didn't open up enough space. I tried to delete userdata, but it wouldn't let me do it remotely.
So I'm a little confused as to my next move here...
and I've relocked my phone and s-on.
Click to expand...
Click to collapse
What is your current OS number on the bootloader screen, and what firmware are you trying to flash?
---------- Post added at 10:53 AM ---------- Previous post was at 10:21 AM ----------
wasdapple said:
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
Click to expand...
Click to collapse
If the intent it to return to 707 based ROM to see if that helps your 4G issue, then yes the custom ROM you previously posted will do that. It will also make 707 appear for software number in the phone Settings.
wasdapple said:
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
Click to expand...
Click to collapse
I was more talking "if" you can find the 4.16.707 firmware. The main firmware collection I refer to doesn't have 4.16.707, just old 707 firmwares (which you don't want)]: http://forum.xda-developers.com/showthread.php?t=2696282
If the firmware can't be found, the RUU listed by xunxholyx is your best bet if you really want to flash the 707 firmware. But I really don't think this is needed. As I'm nearly 100% sure you are already on the current 707 firmware, and the only benefit of flashing the 707 firmware (by RUU) is to get the OS number to appear again on the bootloader screen and on getvar all (which is really not that important).
On the other hand, RUU to full stock may be a good way to troubleshoot your 4G issue, especially if flashing the 707 based custom ROM still doesn't fix the issue. RUU is not just a stock ROM, but a complete factory image, complete with bootloader, radio, etc.
---------- Post added at 11:08 AM ---------- Previous post was at 10:53 AM ----------
wasdapple said:
Is the ruu rooted, or purely stock pre-root?
Click to expand...
Click to collapse
It appears to be 100% official and stock (unrooted). It will also wipe your phone.
---------- Post added at 11:09 AM ---------- Previous post was at 11:08 AM ----------
xunholyx said:
Yes. You will get your software number back if you flash a 707 based ROM, such as stock.
So, here we go.
Download this 4.19.707.2 RUU onto your PC
Click to expand...
Click to collapse
Nice find. I didn't know Asia version had any RUUs.
redpoint73 said:
Nice find. I didn't know Asia version had any RUUs.
Click to expand...
Click to collapse
Yeah, they are hard to come by. I was helping a user here six to eight weeks ago, and told him I didn't know of any Asia RUUs. He came back the next day replying that he found one, so I asked for the link and gave it to Sneakyghost and Alex (from AFH) to upload to androidruu.com
They have a few that aren't common there, and are always looking for more hard to find ones. If you come across one, you could PM me or Sneakyghost to have it added. Always nice to have a good RUU repository to go to.
Hey everyone. I'm having a similar issue, and I don't want to start a new thread, so I'm going to add on to this one.
I've been on AOKP since it was released for this phone, so I've missed out on some OTA updates. Every time I try to flash a Lollipop ROM I get all these weird issues (WiFi not working, systemUI crashes, etc.), and after reading a few threads, I believe its an issue with the firmware.
I tried going back to stock, but the only Nandroid backup I could find for my phone isn't compatible with my firmware (WiFi refuses to work, only data). So I was wondering what else I could do to update the firmware. Reading this thread, it looks like the RUU is another method, but I'm not too sure how to get started with that, or which one to use, as my OS in the Bootloader and my version-main is blank.
Any advice is appreciated, please let me know if you need more info.
My Device:
Rooted
TWRP 2.8.7.0
S-Off
CID-TELUS001
watidk said:
I tried going back to stock, but the only Nandroid backup I could find for my phone isn't compatible with my firmware (WiFi refuses to work, only data). So I was wondering what else I could do to update the firmware. Reading this thread, it looks like the RUU is another method, but I'm not too sure how to get started with that, or which one to use, as my OS in the Bootloader and my version-main is blank.
Any advice is appreciated, please let me know if you need more info.
My Device:
Rooted
TWRP 2.8.7.0
S-Off
CID-TELUS001
Click to expand...
Click to collapse
What are your hboot and radio numbers?