Related
Hi,
First time user of an Android device. I have a branded Vodafone HTC One X that I unlocked and flashed Cyanogenmod 10 on. It works wonderful, runs really fast and is overall much better than Sense. Now that Cyanogenmod 10.1 has reached beta stage, I'm intending on trying out JB 4.2.1. In order to do that, I need to update my HBOOT past 1.28.
It is here that I am quite lost. I did a bit of reading around on xda and other forums to figure out the best method and got a lot of different and sometimes conflicting info. I think this FAQ is the most accurate to my situation although I am worried that it is out of date: http://forum.xda-developers.com/showthread.php?t=1660807
If it helps, the current HBOOT version on my phone is 1.12 and the CID is VODAP021.
It seems the consensus is that I have to (from top to bottom order):
Revert back to stock Sense ROM
Revert back to stock recovery
Relock bootloader (Do I lose root when I do this?)
Run the correct RUU for my phone in order to update HBOOT
Re-unlock bootloader, re-root (if necessary), re-flash custom recovery and flash CM10.1
Are all the above steps correct?
I am aware that there is a collection of stock Nandroid backups somewhere on this forum, but for simplicity's sake can I just restore the Nandroid backup I made prior to flashing Cyanogenmod on my phone? Will restoring the backup also restore the boot.img file? Will the backup also revert my phone back to stock recovery?
Also, I looked on the RUU directory (http://www.androidfiles.org/ruu/?dir=Endeavor) and found two RUU's that match my phone's CID: 1.26.862.3 and 1.29.862.11. Which one is correct?
Sorry if I seem to be bombarding with questions. I think I get the gist of it, but I'm rather paranoid of screwing up so I just want to triple check my understanding before I do anything. If I am over-complicating things, please let me know.
Yes root is lost on lock ( only remporarily ). When you unlock with fastboot oem unlock_token.bin you get back root.
Has Vodafone released JB update for your phone? If yes , then you dont need RUU. After returning to complete stock ( even recovery ) you cant update with official OTA . This will update the hboot.
You only have to revert to full stock and stock recovery. The bootloader can stay unlocked ! :thumbup:
And yes the ota is out for him
The basic steps are :
Flash the boot.img from the nandroid backup
Full wipe in recovery (caches,data,system)
Restore the nandroid backup
Flash the stock recovery
According to your hboot 1.12 you are on 2.17 based android 4.0.4 software .....
This is your stock recovery
http://db.tt/U5CK4noo
There was indeed an OTA for my phone which updated HBOOT to 1.36. Updated to CM10.1 with no dramas and was much simpler than I anticipated.
Thanks everyone for all the advice!
Nice ! Glad we could help !
CASE CLOSED !
How is CM10.1 working?
Scrambled777 said:
There was indeed an OTA for my phone which updated HBOOT to 1.36. Updated to CM10.1 with no dramas and was much simpler than I anticipated.
Thanks everyone for all the advice!
Click to expand...
Click to collapse
Sounds cool! How is the Cm10.1 working on your HOX? GPS and camera working fine? Battery life? Im thinking about the change...
Please help hboot
HTC ONE X on 3G UK network cid is hg3__001 can i change to htc__001 so i can upgrade to Renovate Jelly Bean ROM JBFWTOOL21 wont upgrade hboot to 1.39 my hboot is 1.12 im running cyanogen mod 10 i tried to upgrade ota to cyanogen mod 10.1 Failed also my stock RUU wont flash back to stock which is
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.1204.103.14H_release_256494_signed my phone is s-on
gilly1973 said:
HTC ONE X on 3G UK network cid is hg3__001 can i change to htc__001 so i can upgrade to Renovate Jelly Bean ROM JBFWTOOL21 wont upgrade hboot to 1.39 my hboot is 1.12 im running cyanogen mod 10 i tried to upgrade ota to cyanogen mod 10.1 Failed also my stock RUU wont flash back to stock which is
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.1204.103.14H_release_256494_signed my phone is s-on
Click to expand...
Click to collapse
Im a noob, but I think you have to go back to the stock sense ROM and then gete the official update to Jelly Bean. After that you will have the 1.39 HBOOT and then you can install CM10.1
aricdb said:
Im a noob, but I think you have to go back to the stock sense ROM and then gete the official update to Jelly Bean. After that you will have the 1.39 HBOOT and then you can install CM10.1
Click to expand...
Click to collapse
it wont let me flash back to stock because hboot is different higher
Go here and do the firmware flash... READ freakin carefully !
http://forum.xda-developers.com/showthread.php?t=1927048
the firmware flash lifts the hboot to a JB one and then install any JB rom you like
THANK YOU
Mr Hofs said:
Go here and do the firmware flash... READ freakin carefully !
http://forum.xda-developers.com/showthread.php?t=1927048
the firmware flash lifts the hboot to a JB one and then install any JB rom you like
Click to expand...
Click to collapse
MATE YOU ARE A GOD ALL UPDATED TO JB HBOOT 1.39 IVE BEEN PULLING MY HAIR OUT FOR MONTHS LOOKING FOR THIS LOL:laugh:
ONCE AGAIN THANKS MR HOFS FOR INFO
Glad it worked for you !
I flashed CyanogenMod version 10.1.2 endeavoru. After using for awhile I decided I wanted to go back to the stock rom with the idea of being able to OTA if an update is released.
Unfortunately I didn't have the backup to go back to, when I tried the correct RUU it gives an error message 140 stating, basically the bootloader version is newer on the phone, so I tried to use a stock Nandroid from the collection that was uploaded by BugsyLawson and this seems to restore but then when the phone loads up the hard buttons seem to work but the touch screen isn't responsive, any help would be appreciated or even a point in the right direction, as I can't find anything from searching.
Model number: HTC One X
Android version: 4.2.2 Jelly Bean
Kernal version: 3.1.10-cyanogenmod+ [email protected] #1
CyanogenMod version: 10.1.2-endeavoru
Endeavoru PVT SHIP S-ON RL
HBOOT - 1.39.0000
CPLD - None
RADIO-5.1204.162A.29
Thanks
Post this :
Fastboot getvar version-main
That number will tell you the exact number of nandroid backup you need !
You probably restored an older ics nandroid backup while you have the updated touchpanel drivers. So that's probably why touch doesn't work.
So get the main version and check for that nandroid. Flash the boot.img from the backup, make a full wipe and restore the nandroid.
Mr Hofs said:
Post this :
Fastboot getvar version-main
That number will tell you the exact number of nandroid backup you need !
You probably restored an older ics nandroid backup while you have the updated touchpanel drivers. So that's probably why touch doesn't work.
So get the main version and check for that nandroid. Flash the boot.img from the backup, make a full wipe and restore the nandroid.
Click to expand...
Click to collapse
I did originally use the wrong nandroid back and then I found this http://forum.xda-developers.com/showthread.php?t=2384861 where your links and posts were very helpful, so it's all restored and seems to be working fine.
Thank you very much :good:
Good ! :thumbup:
CASE CLOSED !
what an helpful thread, thanks for the share.
Htc one x back to custom rom from cm10.2
Hi everyone. ı m new on the forum so maybe ı m writing my problem to wrong place, anyway. ı installed cm10.2 into my htc one x. but, now ı want to back to stock rom 4.2.2 with sense 5.0 but ı can't.
My device info:
HBOOT:1.72.0000
ver. base band:5.1204.167.31
version main: 4.18.401.2
cid:HTC__M27
ı searched nearly all over the internet and ı know that there is no RUU for 4.18.401.2. how can ı back to stock rom. help me please.
metalpena said:
Hi everyone. ı m new on the forum so maybe ı m writing my problem to wrong place, anyway. ı installed cm10.2 into my htc one x. but, now ı want to back to stock rom 4.2.2 with sense 5.0 but ı can't.
My device info:
HBOOT:1.72.0000
ver. base band:5.1204.167.31
version main: 4.18.401.2
cid:HTC__M27
ı searched nearly all over the internet and ı know that there is no RUU for 4.18.401.2. how can ı back to stock rom. help me please.
Click to expand...
Click to collapse
Read here
http://forum.xda-developers.com/showthread.php?t=1975140
Mr Hofs said:
Read here
http://forum.xda-developers.com/showthread.php?t=1975140
Click to expand...
Click to collapse
ı have already red this before.
no 4.18.401.2 htc M__27 bac up included.
Do this :
Download any 3.20.401 nandroid backup. Restore it and flash back the 3.20 stock recovery after that. Then reboot the phone and do all OTA updates via the settings-software update menu. After that you can relock the bootloader if you wish. The official ota will make the cid correct again.
Hi i have been given a HOX to look at and it's had me stumped for the last 24 hours so now i'm asking for help. Here we go.
The phone has no IMEI/Baseband. The fasboot getvar all command returns the correct IMEI to the box but it just doesn't show in android so no signal at all stuck on airplane mode etc. It's a TMOB005 cid.
Tried loads of custom roms and methods no signal.
Tried to return to stock to flash stock RUU. My main 3.16.110.4 so try RUU RUU_ENDEAVOR_U_ICS_40_S_TMO_UK_2.17.110.5_Radio_2.1204.137U.21_release_284360_signed.exe it fails with script error and all other RUU fail at bootloader version.
I downloaded recommended nandroid for my main. 2012-10-29.07.35.43 from thread on here. Flashed boot img in fastboot. Flashed stock 1.29 recovery. Got the small 1.25mb OTA but then nothing after that and still no signal.
Tearing my hair out now. HBOOT is 1.39. Let me know if i've missed any info please any ideas now will help.
Oke i will give it a go !
You restored a 2.17 nandroid backup ? And flashed back a 1.29 stock recovery ?
In this case your rom won't respond to touch on screen ! You say your main version is 3.16 then you need a nandroid backup with at least that number....and a stock 3.16 recovery and not a 1.29 one
So.....enlighten me ?
Now you have me all confused?! The touch screen works fine with the stock recovery i flashed. It's one you recommended to someone else in a TMOB005 thread i saw. I'm not sure recovery is the real issue here anyway. The issue is not being able to flash an RUU, stock not doing the OTA it only reports the small one 1.25MB. Never asked for Jellybean OTa it just doesn't want to work.
The nandroid should be correct too as it's a TMOB005 one too.
If you can help let's start from my main as we know that's 100% right.
So what nandroid stock rom do i need, what recovery and anything else required?
Thanks for reply so far.
Oke you need a stock nandroid backup 3.16 if you have it (or already restored it) that's good then. Now we need your stock 3.16 recovery and not the 1.29 one.....
Is your 3.16 number matching this command ?
Fastboot getvar version-main
Ok I'll check when I'm at home next, I'll still appreciate any help/ideas/input from anyone. I'm sure my version matches the one with the version main command.
Does the recovery version have to match too? Where would I find the relevant one?
Try this one
http://db.tt/mp3v3KrP
Mr Hofs said:
Try this one
http://db.tt/mp3v3KrP
Click to expand...
Click to collapse
Thanks and is the nan droid I mentioned the correct one at all? Like I say it offers the small OTA does that have any significance?
Is there no possible way to flash ANY RUU?!
If the nandroid matches the main version number 3.16.110 then you have indeed the correct one. And no a ruu is not available so that's not possible atm.
I saw something about an RUU hack where it makes it think you have an older version or is that not possible any more? The custom RUU file isn't available for download any more.
Well its probably possible for some, but if the phone has updated touch drivers then its of no use. Ics and lower roms don't work because touchscreen doesn't respond !
And the OP is on 3.16 so that's a no go.
From 3.14 and lower it could work.
"fastboot getvar version-main" returns that my main is definitely 3.16.110.4. So what nandroid for definite matches and what recovery? Can anyone provide links please? Is 3.16.110.4 supposed to be Jellybean?!
Yes 3.16 is Jellybean. And the recovery will be in the nandroid backup, as well as the boot.img.
Will the nandroid backup not have clockwork mod recovery in it as that is required to make the backup?!
Hold on....
you have the 3.16.110 nandroid backup ?
No i have a main of 3.16.110.4. I have the 2.17.110.5 nandroid as i understand this should work for OTA as i read in another thread. As long as the red part matches. I have installed a 3.16 stock recovery too yet STILL not being offered the proper OTA (still get the 1.25MB one) plus the phone is still stuck without IMEI or baseband.
EDIT:
This guy you helped here... http://forum.xda-developers.com/showthread.php?t=2204955 was offered the OTA after using the same nandroid as me so what's going on?!
Well give it a go then !!!
Here is the 2.17 stock recovery......trying to recall what i missed/forgot.
http://db.tt/OtcxVXh5
Mr Hofs said:
Well give it a go then !!!
Here is the 2.17 stock recovery......trying to recall what i missed/forgot.
http://db.tt/OtcxVXh5
Click to expand...
Click to collapse
Still no offer of the OTA hmm. It's such a shame we can't change CID or flash any RUU as I'm sure that would help me. I'm just stuck and this phone is useless.
What ota are you talking about anyway ? Restore the 2.17 nandroid and the 2.17 stock recovery and then ota up to JB !
Mr Hofs said:
What ota are you talking about anyway ? Restore the 2.17 nandroid and the 2.17 stock recovery and then ota up to JB !
Click to expand...
Click to collapse
That's exactly my aim but it's not happening.i've restored the correct nandroid (100% certain) unless there is a 3.16 nandroid? Then i've tried with stock recovery 3.16 and 2.17 both times. The only OTA i get offered is the first 1.25MB one and that's it nothing after it. Tried with bootloader locked and unlocked although this shouldn't matter.
Do you need GSM signal to be offered the OTA? As if you do i'll never get offered it as i don't have an IMEI or baseband etc.
I appreciate all the help you are offering Mr Hofs i see you have helped a LOT of people on here.
Just tried the recovery 2.17 that you uploaded as it's a diferent size to the ones i've previously tried but still no luck. No OTA at all.
Is stock recovery supposed to just show a red triangle? It's shows green first then changes to a red triangle ni'm not sure this is right even with bootloader locked.
Does recovery have to match as in 2.17.110?
No this stock 2.17 recovery works on branded phones too, its weird but indeed it could be related to no baseband and imei !
Hey Guys,
I'm in a bit of a pickle! + I'm a newbie (with some background knowledge - i know how to flash, use cmd etc.)
I want to unroot my One X back to the original stock rom, how it was like when i got it out of the box!
Now i have currently CWM + Insertcoin
I installed a nandroid backup, but it failed, as in (No Wifi+No Mobile Network)
So thats why i went on to install a custom rom so my phone could work for now.
MY PHONE
S-ON
CID: OPTUS001
HBOOT: 1.36
Radio: 5.1204.162.29
Main Ver: 3.14.980.27
Now the issue.....
So as i said before, i want to go back to stock, so i can receive the OTA updates.
The real problem is that the latest RUU i can find for my One X is:
" RUU_ENDEAVOR_U_ICS_40_Optus_AU_1.29.980.11_Radio_1.1204.105.14_release_260560_signed "
So since my version is updated to JB 3.14 i need that RUU, so the real question is does any have
HTC ONE X OPTUS JB 3.14 RUU ??????
COULD SOMEONE PLEASE HELP!!!
Also....
>I have also tried running the customRUU to install the ICS RUU but.... NO LUCK! I got an invalid Error [156]
Anybody know how to fix that?? if that is the only way?
>Nandroid - FAIL
I would just like to be back at original stock rom, with no root, no nandroid, anything!! PLEASE HELP :'(
Another panic button...
You have no wifi/mobile network because you have a kernel on device that does not match the modules included on your ROM.
Use this untouched nandroid to get back to stock, make sure your flash boot.img 3 times for my favor.
[COLLECTION]Stock Nandroid Backups for Different CIDs
Thanks heaps for that HebeGuess!!
But now that i have the nandroid working, how can i unroot and go back to stock how it came out of the box, so basically no CWM and i can get OTA updates.
What do i do after installing the nandroid?
Thanks
zorbad18 said:
Thanks heaps for that HebeGuess!!
But now that i have the nandroid working, how can i unroot and go back to stock how it came out of the box, so basically no CWM and i can get OTA updates.
What do i do after installing the nandroid?
Thanks
Click to expand...
Click to collapse
Read the FAQ in that thread.
In case, recovery is the same across Official ROM despite vary CIDs.
HebeGuess said:
Read the FAQ in that thread.
In case, recovery is the same across Official ROM despite vary CIDs.
Click to expand...
Click to collapse
Ok, so just to be clear, all i need to do is flash the "stock recovery" and i should be fine?
My M8 has the CID of HTC_044 and I would like to flash latest ROM. However it requires latest firmware, ie 2.22.401.4, I am wondering if it is safe to flash the firmware to my device being with different CID as the firmware's android-info does not contain my device CID.
I have S-OFF on my device, I am wondering if I change mt CID to supercid would allow my device to run the firmware without issue.
Thanks in advance.
Yep,if your phone is supercid,u can flash that firmware...
hellcommando said:
My M8 has the CID of HTC_044 and I would like to flash latest ROM. However it requires latest firmware, ie 2.22.401.4, I am wondering if it is safe to flash the firmware to my device being with different CID as the firmware's android-info does not contain my device CID.
I have S-OFF on my device, I am wondering if I change mt CID to supercid would allow my device to run the firmware without issue.
Thanks in advance.
Click to expand...
Click to collapse
If your firmware for CID HTC__044 is 2.22.707.3, it is not necessary for you to flash another firmware to run a 2.22.401.4 ROM.
As long as the firmware is 2.22.xxx.x ... you're good to go.
Anyway it's up to you if you want to flash 2.22.401.4 firmware but your Radio will be the EU region if the firmware that you flash come with radio image. If you currently in Asia, it's best to keep 2.22.707.3 firmware
hdorius said:
Yep,if your phone is supercid,u can flash that firmware...
Click to expand...
Click to collapse
Thank you!
ckpv5 said:
If your firmware for CID HTC__044 is 2.22.707.3, it is not necessary for you to flash another firmware to run a 2.22.401.4 ROM.
As long as the firmware is 2.22.xxx.x ... you're good to go.
Anyway it's up to you if you want to flash 2.22.401.4 firmware but your Radio will be the EU region if the firmware that you flash come with radio image. If you currently in Asia, it's best to keep 2.22.707.3 firmware
Click to expand...
Click to collapse
Thank you! However I have heard there was one 2.22.7xx posted but was meant for M7, and at the moment I could not find 2.22.707.3 firmware from any firmware repository. I'm from Asia, could you please kindly post the link so that I wont brick my phone? Thank you!!
hellcommando said:
Thank you! However I have heard there was one 2.22.7xx posted but was meant for M7, and at the moment I could not find 2.22.707.3 firmware from any firmware repository. I'm from Asia, could you please kindly post the link so that I wont brick my phone? Thank you!!
Click to expand...
Click to collapse
When we read firmware we look at x.xx.707.x not 2.22.7xx.x
You don't need 2.22.707.3 firmware if you already done the OTA update.
Please advise your current firmware that you have ... check what is written on the bootloader ... is it 1.54.707.7 or 2.22.707.3 ?
If it is 1.54.707.7 then you need to do OTA update.
If it is 2.22.707.3 then you're good to flash any ROM.
ckpv5 said:
When we read firmware we look at x.xx.707.x not 2.22.7xx.x
You don't need 2.22.707.3 firmware if you already done the OTA update.
Please advise your current firmware that you have ... check what is written on the bootloader ... is it 1.54.707.7 or 2.22.77.3 ?
If it is 1.54.707.7 then you need to do OTA update.
If it is 2.22.707.3 then you're good to flash any ROM.
Click to expand...
Click to collapse
Couldn't check my firmware version as the OS field is empty in the bootloader.
Hboot: 3.16.0.0000
Radio: 1.16.2133156.UA10G
But I highly doubt my firmware is 2.22.707.3, I would think it is more likely to be 1.54.707.7 as I have rooted by phone before newer firmware roll out.
So can I use your firmware in http://forum.xda-developers.com/showthread.php?t=2701376&page=141
and flash it by using this guide? http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
hellcommando said:
Couldn't check my firmware version as the OS field is empty in the bootloader.
Hboot: 3.16.0.0000
Radio: 1.16.2133156.UA10G
But I highly doubt my firmware is 2.22.707.3, I would think it is more likely to be 1.54.707.7 as I have rooted by phone before newer firmware roll out.
So can I use your firmware in http://forum.xda-developers.com/showthread.php?t=2701376&page=141
and flash it by using this guide? http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Click to expand...
Click to collapse
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
I don't post firmware on XDA. Those that I posted are recovery and stock backup.
If you insist to update firmware without OTA update .. that's you call. Someone maybe will guide you how to do it as I don't feel comfortable telling how to update firmware.
ckpv5 said:
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
I don't post firmware on XDA. Those that I posted are recovery and stock backup.
If you insist to update firmware without OTA update .. that's you call. Someone maybe will guide you how to do it as I don't feel comfortable telling how to update firmware.
Click to expand...
Click to collapse
Awesome! I just followed your advice by doing the safe way, flashed stock recovery and backup. I'm running on 2.22.707.x now! Thanks a lot :good:
hellcommando said:
Awesome! I just followed your advice by doing the safe way, flashed stock recovery and backup. I'm running on 2.22.707.x now! Thanks a lot :good:
Click to expand...
Click to collapse
Great
Now you can flash any Sense 6 custom ROM that you like.
Only remember that you don't need to flash another firmware, your current one is good enough.. just flash ROM.
I am having the same issue - I have the HTC__044 and need new firmware to get the newest ROM.
I am S-On and CANT get S-off (s-off needed to flash firmware)...firewater does not work with my phone after multiple tries.
I tried getting Sunshine to work for s-off, but I need to be on a stock Sense ROM (I am on Viper 1.8) and don't have a stock backup. I can't find ANY stock ROM's online! Once I have supercid i was going to flash firmware, but without S off...I'm going nowhere (it seems)
anyone have an idea where I should start?
charkswitlazers said:
I am having the same issue - I have the HTC__044 and need new firmware to get the newest ROM.
I am S-On and CANT get S-off (s-off needed to flash firmware)...firewater does not work with my phone after multiple tries.
I tried getting Sunshine to work for s-off, but I need to be on a stock Sense ROM (I am on Viper 1.8) and don't have a stock backup. I can't find ANY stock ROM's online! Once I have supercid i was going to flash firmware, but without S off...I'm going nowhere (it seems)
anyone have an idea where I should start?
Click to expand...
Click to collapse
Stock ROMs and recoveries for HTC__044
http://forum.xda-developers.com/showthread.php?t=2701376
charkswitlazers said:
anyone have an idea where I should start?
Click to expand...
Click to collapse
Everything that you need is here : http://forum.xda-developers.com/showthread.php?t=2701376
1. Restore nandroid backup 1.54.707.7
2. flash stock recovery 1.54.707.7
3. reboot and check for OTA
4. install OTA
5. done .. your ROM will be 4.4.3 - 2.22.707.3
6. flash any 4.4.3 custom ROM that you like if any
All above no need to relock bootloader or S-Off, it works on S-On
If you want to S-Off with sunshine, step 1 & 2 then sunshine
or after step 5 then sunshine (both way should work)
ckpv5 said:
Everything that you need is here
1. Restore nandroid backup 1.54.707.7
2. flash stock recovery 1.54.707.7
3. reboot and check for OTA
4. install OTA
5. done .. your ROM will be 4.4.3 - 2.22.707.3
6. flash any 4.4.3 custom ROM that you like if any
All above no need to relock bootloader or S-Off, it works on S-On
If you want to S-Off with sunshine, step 1 & 2 then sunshine
or after step 5 then sunshine (both way should work)
Click to expand...
Click to collapse
I'm still a little on the noob side with rooting/flashing..I am at work and don't have time to read much - i will go home and give it a go... I'm sure I will have lots of questions
A quick look at the site, i saw lots of recoveries but not very many stock ROMs. I mainly just need a plain/rooted stock Sense rom to run Sunshine. After which i can flash new firmware, then the new custom ROM i've been wanting. Also, does a nandroid HAVE to be HTC__044, or can it be any WWE cid? (like anything that's "HTC__xxx")?
Excuse my ignorance...trying to learn as much as possible
I just got my m8 from Tmobile today, and I am on firmware 157.531.7
I've checked several times for updated firmware, but always comes back nothing.
Am I stuck on this, or will it take awhile for the network to "see me" and send it?
not rooted, fully stock for now
thanks so much!
charkswitlazers said:
I'm still a little on the noob side with rooting/flashing..I am at work and don't have time to read much - i will go home and give it a go... I'm sure I will have lots of questions
A quick look at the site, i saw lots of recoveries but not very many stock ROMs. I mainly just need a plain/rooted stock Sense rom to run Sunshine. After which i can flash new firmware, then the new custom ROM i've been wanting. Also, does a nandroid HAVE to be HTC__044, or can it be any WWE cid? (like anything that's "HTC__xxx")?
Excuse my ignorance...trying to learn as much as possible
Click to expand...
Click to collapse
If your main purpose to restore to stock to get SunShine working, then any nandroid backup will do either HTC__044 or WWE. You don't really need a rooted stock as SunShine works on non-rooted ROM too.
As you said you're a noob, that is why I suggest to restore to 1.54.707.7 then OTA to 2.22.707.3 so you don't need to manually flash firmware to get other custom ROMs running flawlessly. It is not necessary to have 2.22.401.4 firmware but it is necessary to have a 2.22.xxx.x firmware for those custom ROMs, unless you're not in Asia.
As you can see in my sig, I'm on 2.22.707.3 firmware, I can run any ROM without problem.
Being a noob, you may make a stupid mistake when flashing firmware.
There is also by mike or so a stock Rom as a zip.
Flash it like a custom Rom Flash the stock kernel and better the recovery and do sunshine...easier then with getting nandroid backup etc
Slow Booting & Sense 6 Toolbox Not Working On ARHD v10.2
One-M8-Master said:
There is also by mike or so a stock Rom as a zip.
Flash it like a custom Rom Flash the stock kernel and better the recovery and do sunshine...easier then with getting nandroid backup etc
Click to expand...
Click to collapse
Hi One-M8-Master,
I've read quite a few of your posts & given that your moniker seems appropriate, I'm wondering if you might be able to help me?
I've posted this on another thread but haven't got very far as yet, so am hoping that you might be able to get me out of the stupid hole I've dug myself into :fingers-crossed:
It is quite a long description but if you don't fall asleep reading it, I'd really appreciate any help you might be able to give me.....Here goes:
"Hi Guys,
Now I know you're all already thinking that I didn't update my firmware before I flashed ARHD & now I'm getting all the problems that come along with not doing that......& you'd be correct....kind of. HOWEVER, as it turns out, I already seem to have it. Let me explain.
As you can see, I'm relatively new to all this but successfully unlocked, rooted & installed a custom ROM on my ASUS TF700T tablet, so I wanted to do it with my One M8. I always do loads of reading before I start anything (I even read the instructions for new games before I attempt to play them because I'm a bit weird like that!) but what happened on this occasion was that I did the reading, unlocked the phone, flashed TWRP, & rooted it but then ran into the problem that some people appear to have had when trying to s-off via the adb commands & Firewater, that is, my pc could see the phone but when I gave the reboot command, it told me it wasn't connected.
I then got into hours of reading to try & solve this issue, discovered that (without Sunlight) on some devices it just doesn't work once you've accepted the 'should we allow this pc to connect every time' message (which I NEVER normally say 'yes' to), unless you install the Android Studio & Java Develpers Kits, update your version of adb, & force the phone to ask again (which I did but it turned out that I already had the latest version of adb, so that route proved fruitless!). I actually missed a night's sleep trying to resolve the problem, so work wasn't good the next day! but I think it is here is where my problems started because I was so tired & frustrated that I just picked a ROM & flashed it. I had even read the warning about not flashing it if you didn't have the correct firmware but I think that being so tired, it didn't really sink in, or I'd forgotten about it by the time I just flashed the ROM.
By this point, I'd been sat in front of my pc for about 30 hours & needed to go to work but the phone was actually booting through to ARHD, so I was relatively happy in the knowledge that at least I hadn't bricked it! On starting to use the phone that evening, I noticed the long boot times & then that my Sense 6 Toolbox didn't seem to be making any changes, even if I rebooted the device, so I went back to the beginning of this thread & started reading again. Thus, I re-read the firmware warning & panicked (my 2nd mistake!), thinking that I was getting the problems because I hadn't updated the firmware (it still didn't occur to me to just check because I think I just assumed that I wouldn't have it). So.....I tried to restore my TWRP backup of the stock ROM that I made after I had unlocked/rooted, with the intention of reverting to the stock ROM, getting the OTA update & then re-flashing ARHD but despite TWRP telling me that the backup had been successful, the phone went into a bootloop back into TWRP. I solved this by re-flashing the ARHD ROM that I knew at least would get my phone out of the bootloop & back into KitKat, which it did. I then checked what version of the firmware I had & to my surprise, my Build Number in About\Software Information\More says "2.22.401.4 CL365360 release-keys", so it looks like I had the correct firmware version all along?
The above being the case, I'm now puzzled as to why I'm getting the problems that I'm getting with ARHD? Does anyone have any clues/answers that might get me out of this hole I've dug for myself & get my awesome One M8 working like it should?
I know I've caused this problem by doing things when I was too tired to think straight but I'm fresh as a daisy now (still fairly noobish but fresh ) & now I need your help to sort myself out. I would be so grateful for any help anyone can give me to get me back on track.
I hope all of that makes sense & thanks in advance."
@dan5001
The firmware you speak of is the displayed version main number of the flashed rom. It has no relation to your actual installed firmware. Check your bootloader and post here what it says. I bet it is still hboot 3.16 and if that's the case your firmware is not updated.
Mr Hofs said:
@dan5001
The firmware you speak of is the displayed version main number of the flashed rom. It has no relation to your actual installed firmware. Check your bootloader and post here what it says. I bet it is still hboot 3.16 and if that's the case your firmware is not updated.
Click to expand...
Click to collapse
Hi.
This is my own fault but I'm getting really frustrated with it because I've probably spent a total of 40 hours on it so far
I tell you that because I know that I needed S-OFF & SUPER CID to be able to update my firmware, so I just thought "screw it" & I paid for Sunshine. I now have S-OFF & following Vomer's guide here:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I now have S-OFF & SUPER CID. I thought that would be the end of my issues but it would appear not!
Looking at my bootloader, you are correct, HBOOT is 3.16.0.0000!
However, I've tried to upgrade this firmware by downloading what I think is the correct update .zip from the list at the bottom of the aforementioned Vomer's guide (v2.22.401.5 (Rename to firmware.zip after downloading)), renaming it as suggested, & then flashing it in TWRP but it just keeps telling me that the update has failed!
Do I have to do it using the adb commands on Vomers guide? I didn't think so but it's just not working??
I appreciate any help you can give me with this. Given that I've spent so long on this & have paid for Sunshine, you can see that I'm trying to help myself but I've still got rain!!
EDIT
Just a thought, I do still have ARHD v10.2 installed at the moment because even though it's not working properly without the correct firmware, it's the only ROM I've got at the moment, so it means I can use the M8 to a degree; would that cause the problem with upgrading the firmware?
Firmware flash can be done via fastboot commands, that's how i did it
Installed rom has no influence on the to flash firmware, try it via fastboot