Related
Hi Guys,
It's been a while since I wrote on this forum... I may be tired, but I can't work out a few things:
I have a T-Mobile UK HTC One X, due to some circumstances I needed to completely wipe...
I was already running an unbranded stock firmware on it, but after the complete wipe i wanted to install JB 4.2.2 S5 - I usually unlock the bootloader, install clockworks, copy the original unedited complete firmware zip on it and install it via the recovery, then relock the bootloader and job done, but I cannot seem to find a complete unedited rom, is either RUU.exe (which I cannot run as the PC wont see the phone due to no firmware on it, I think) or nandrom backups which I don't really want, all the OTA ones seem to just be updates and am stuck with a phone that only has clockwork recovery on it....
Where can I get an official unedited zip that I can install via clockworks?
Thanks
LondonVirus said:
Hi Guys,
It's been a while since I wrote on this forum... I may be tired, but I can't work out a few things:
I have a T-Mobile UK HTC One X, due to some circumstances I needed to completely wipe...
I was already running an unbranded stock firmware on it, but after the complete wipe i wanted to install JB 4.2.2 S5 - I usually unlock the bootloader, install clockworks, copy the original unedited complete firmware zip on it and install it via the recovery, then relock the bootloader and job done, but I cannot seem to find a complete unedited rom, is either RUU.exe (which I cannot run as the PC wont see the phone due to no firmware on it, I think) or nandrom backups which I don't really want, all the OTA ones seem to just be updates and am stuck with a phone that only has clockwork recovery on it....
Where can I get an official unedited zip that I can install via clockworks?
Thanks
Click to expand...
Click to collapse
Give the result from command fastboot getvar version-main
Thant said:
Give the result from command fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 3.16.110.4
cidnum: T-MOB005
But as I said, I want a non branded, complete flash room please
LondonVirus said:
version-main: 3.16.110.4
cidnum: T-MOB005
But as I said, I want a non branded, complete flash room please
Click to expand...
Click to collapse
sorry fastboot getvar all and delte your S/N and IMEI from the info I didn't read what you wamt you want rom with sense 5 give the result to see your hboot version
Thant said:
sorry fastboot getvar all and delte your S/N and IMEI from the info I didn't read what you wamt you want rom with sense 5 give the result to see your hboot version
Click to expand...
Click to collapse
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.163R.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.110.4
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s
Sorry it took me a while... life and kids eh lol... I am trying to sort this phone for the MRS, I have a Galaxy S5, great device
I must say I would even be happy with the TMO UK RUU, this pone is doing my head in at the moment and really don't have the time to be messing with it now, just need it working...
I wanted to change Super CID it but apparently it will need to be s-off and cant get round to do that, I wanted to install a non branded RUU but this is not allowed due to the wrong CID arg, stupid phones, was easier to flash unbranded firmware to old Nokia on Symbian...
LondonVirus said:
C:\Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.163R.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.110.4
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: low
(bootloader) battery-voltage: 3446mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s
Sorry it took me a while... life and kids eh lol... I am trying to sort this phone for the MRS, I have a Galaxy S5, great device
I must say I would even be happy with the TMO UK RUU, this pone is doing my head in at the moment and really don't have the time to be messing with it now, just need it working...
I wanted to change Super CID it but apparently it will need to be s-off and cant get round to do that, I wanted to install a non branded RUU but this is not allowed due to the wrong CID arg, stupid phones, was easier to flash unbranded firmware to old Nokia on Symbian...
Click to expand...
Click to collapse
You have good hboot for sense 5 rom 4.2.2 install MaximusHD or ARHD or any sense 5 rom and you are ready to go.
I wanted a stock ROM, the Mrs is not very technical minded lol and a customer ROM won't help her, either TMO UK or in branded, where can I get the RUU for it?
Thanks all
Unfortunately T-Mobile skipped the sense 5, 4.2.2 update, I have the same device and cid and called them countless times, spoke to managers and had it escalated to the highest level only to be told they would not be updating past 4.1.1
Every other network pushed that but them, if you stick to stock T-Mobile ROM you would be missing 2 very important updates, one being the heartbleed patch.
Just grab MaximusHD from the development forum, its the best sense 5 ROM out there and has important ota updates too.
I suppose I will have install it via the custom recovery, could I not install the unbranded RUU 4.2.2? Does anyone know how to s-off correctly, so that I can change the CID.
By the way thank you all for your replies
LondonVirus said:
I suppose I will have install it via the custom recovery, could I not install the unbranded RUU 4.2.2? Does anyone know how to s-off correctly, so that I can change the CID.
By the way thank you all for your replies
Click to expand...
Click to collapse
NO S-OFF for HOX
Thant said:
NO S-OFF for HOX
Click to expand...
Click to collapse
I assume that HOX means Htc One X lol... so I will not be able to change the CID?
Any "re-pack" unedited versions of the genuine unbranded europe RUU that I can install via custom recovery?
Thanks again all
There must be a way to s-off the Maximus HD ROM says "1. Make sure your device is unlocked or have s-off"
Why would it say that on "http://forum.xda-developers.com/showthread.php?t=2410320" if there was no s-off ways? am confused lol
LondonVirus said:
There must be a way to s-off the Maximus HD ROM says "1. Make sure your device is unlocked or have s-off"
Why would it say that on "http://forum.xda-developers.com/showthread.php?t=2410320" if there was no s-off ways? am confused lol
Click to expand...
Click to collapse
Don't be confused mate..HOX can s-off but via java card( will cost money to make it).In here no have chance to be s-off.
Installation of Maximus HD no hanging on this screen, flashed Kernel and wiped the memory fkn phones!
LondonVirus said:
Installation of Maximus HD no hanging on this screen, flashed Kernel and wiped the memory fkn phones!
Click to expand...
Click to collapse
Never mind, seems to have worked lol
LondonVirus said:
Never mind, seems to have worked lol
Click to expand...
Click to collapse
Phone hanging on boot screen don't know why...
LondonVirus said:
Phone hanging on boot screen don't know why...
Click to expand...
Click to collapse
are you flashed the boot.img from maximushd archive via fastboot with the command fastboot flash boot boot.img
Thant said:
are you flashed the boot.img from maximushd archive via fastboot with the command fastboot flash boot boot.img
Click to expand...
Click to collapse
Thank you for your reply, I did flash the boot via the "Kernel+Flasher+21.0.0" looking at the coding inside the batch file, it calls a batch in a sub-folder with the command fastboot flash boot boot.img, and I did run it and got Okay message in the command window...
LondonVirus said:
Thank you for your reply, I did flash the boot via the "Kernel+Flasher+21.0.0" looking at the coding inside the batch file, it calls a batch in a sub-folder with the command fastboot flash boot boot.img, and I did run it and got Okay message in the command window...
Click to expand...
Click to collapse
do it manually like I write you in my post not with flasher or tool
Thant said:
do it manually like I write you in my post not with flasher or tool
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------
C:\Android\sdk\platform-tools>fastboot flash zip rom.zip
sending 'zip' (716000 KB)...
OKAY [ 90.451s]
writing 'zip'...
(bootloader) Can not find [android-info.txt] in zipped image!
FAILED (remote: 24 parsing android-info fail)
finished. total time: 125.830s
---------------------------------------------------------------------------------------------------------------------
fastboot oem rebootRUU
fastboot flash zip rom.zip <----- This is Maximus HD....
and this is after a flashed the correct kernel/boot.img....
Hello everyone! glad to be a new member of this amazing community! I am a new member with a tough problem, would love if I get ideas on how to solve it.
So After flashing stock unrooted GPe rom as per the most common methods circulating around (changing CID, MID, S-Off, etc), I was thrilled to see the boot splash screen change into google's except that it keeps booting into the bootloader; for some reason I could not get into recovery either (but I flashed TWRP again and it works now)
So as it stands now I have the following:
S-Off
Unlocked
Software status: Official
Working TWRP (which keeps saying NO OS IS INSTALLED)
Unable to mount /data (whatever that means) + "error: closed" when attempting to sideload the RUU roms via ADB
I did not install any firmware or kernels
and whenever I try to boot the OS I get put back in bootloader over and over.
As far as im concerned this phone seems bricked for me, but im also new so I wouldn't know, having said that, I am open for the most radical of options and procedures to get this working.
Thank you all in advance!
Flash it again via adb, the flashing command must be executed twice.
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Megaliths said:
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Click to expand...
Click to collapse
That unrooted GPE was for dual sim? I see you have a dual sim.
Make a screenshot.
Details about the ROM would help.
Do a fastboot getvar all command also.
Actually I don't know if the Rom is for dual sim or not, I figured as long as I get CID and MID right it should fit? pardon my ignorance on the matter. ill post a screenshot as soon as possible!
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Megaliths said:
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Click to expand...
Click to collapse
Delete the IMEI.
OP - Do you want it back to Sense?
EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
Come to think about it now, I'd rather go to stock now if it all possible.
Megaliths said:
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
Click to expand...
Click to collapse
Megaliths said:
Come to think about it now, I'd rather go to stock now if it all possible.
Click to expand...
Click to collapse
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
EddyOS said:
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
Click to expand...
Click to collapse
It never booted up correctly no. I'd love if you can help me go to stock with such a messed up state my phone had gotten into.
We should be able to sort things out, but I'll need to get to a proper PC and get links together
EddyOS said:
We should be able to sort things out, but I'll need to get to a proper PC and get links together
Click to expand...
Click to collapse
Thank you so much!
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
EddyOS said:
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
Click to expand...
Click to collapse
That is amazing thank you, ill try it and get back to you asap.
I have two questions:
Will I still get OTAs even if I don't have the original CID and MID? (I remember the original CID which is J15 but I can't remember the mid).
Also, I am currently on custom recovery and in your guide above I do not see anything about flashing stock recovery, should I do that first?
Thank you again!
The RUU flashes everything stock, so it'll overwrite it all
I'd change the CID back to stock once it's all working again but the MID I'm not sure on so I'll see if I can find out for you
At step 8 I get an error "DNS server not authoritative for zone", how to resolve that?
Nvm I resolved the DNS thin, but now I get error 41 model id check fail. It is probably because of bad MID isn't it?
Thank you again for helping me, I hope it is not much trouble.
Helllo there!
I'm making a new thread because I couldn't find anyone with the exact same problem and don't want to brick my phone or such.
Now to the problem: every time I try to update my HTC one m8 (Europe) it stops when installling and tells me this:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.101.007
Package expects build fingerprint of htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.9:user/release-keys
or htc/htc_europe/htc_m8:5.0.1/LRX22C/448934.10:user/release-keys;
this device has htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.6:user/release-keys.
Installation aborted.
Write host_mode 0 done
getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone is rooted, the bootloader unlocked, it has the stock recovery, it's s-on and it says "software status: modified".
The only thing I can see in the error is that this nine:
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]9[/U][/B]:user/release-keys
is a six
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]6[/U][/B]:user/release-keys
on mine.
I am pretty new here still, so i don't know how to fix it, and i don't want to break it.
Best regards
Schmix
Root phone
vinayluck said:
Root phone
Click to expand...
Click to collapse
What are you trying to say?
Schmix said:
What are you trying to say?
Click to expand...
Click to collapse
You should post your getvar all (deleting your imei number and S./N ) there is a post here but it is in german with the same problem which points to an incorrect recovery!
http://www.android-hilfe.de/wiederh...ge-expects-build-fingerprint-fingerprint.html
Shepps
vinayluck said:
Root phone
Click to expand...
Click to collapse
Being rooted or not has no bearing on OTA update.
Also, it seems that you are trying to tell the OP to root (not completely clear, with the 2 word post), when he clearly states he is already rooted.
Getvar info added!
By the way, the other guy had a different problem.
Has anyone got an idea of whats wrong?
Schmix said:
Helllo there!
I'm making a new thread because I couldn't find anyone with the exact same problem and don't want to brick my phone or such.
Now to the problem: every time I try to update my HTC one m8 (Europe) it stops when installling and tells me this:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.101.007
Package expects build fingerprint of htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.9:user/release-keys
or htc/htc_europe/htc_m8:5.0.1/LRX22C/448934.10:user/release-keys;
this device has htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.6:user/release-keys.
Installation aborted.
Write host_mode 0 done
getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone is rooted, the bootloader unlocked, it has the stock recovery, it's s-on and it says "software status: modified".
The only thing I can see in the error is that this nine:
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]9[/U][/B]:user/release-keys
is a six
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]6[/U][/B]:user/release-keys
on mine.
I am pretty new here still, so i don't know how to fix it, and i don't want to break it.
Best regards
Schmix
Click to expand...
Click to collapse
Download and run the 3.28.401.10 RUU first (a quick search here and you'll find it), then run this one.
Schmix said:
Getvar info added!
By the way, the other guy had a different problem.
Has anyone got an idea of whats wrong?
Click to expand...
Click to collapse
Wrong stock recovery image.
OTA needs stock recovery 3.28.401.9 (389838.9) or 4.16.401.10 (448934.10)
but you installed 3.28.401.6 (389838.6)
Get the right recovery image, OTA will proceed.
I have one here - 3.28.401.9_recovery.img : http://sourceforge.net/projects/htconem8/files/Recovery/3.28.401.9_recovery.img/download
ckpv5 said:
Wrong stock recovery image.
OTA needs stock recovery 3.28.401.9 (389838.9) or 4.16.401.10 (448934.10)
but you installed 3.28.401.6 (389838.6)
Get the right recovery image, OTA will proceed.
I have one here - 3.28.401.9_recovery.img : http://sourceforge.net/projects/htconem8/files/Recovery/3.28.401.9_recovery.img/download
Click to expand...
Click to collapse
Okay thank you so far!
But now it comes up with a different error; It says "/system/xbin/nc has unexpected contents".
Let me tell you the whole story:
Some time ago i installed busybox, xposed and xprivacy (and luckypatcher) and used it normaly.
Then the Lollipop update came around and since it wasnt working (giving out the unexpected contend error) i thought it would be a good idea to just do a factory reset.
It didnt work afterwards either, so i went here to ask what the problem was, and i was told it was because of xposed.
However, xposed wasn't installed anymore (the app), and (i think) the newer versions installed it somewhere else, so installing and then uninstalling (the button in the app) it didnt delete the old directory. (Btw. in an last attempt i tried installing the stick recovery and got the wrong one apparently)
So yeah, i have no idea on how to fix this problem, but i would be okay with having to reset my phone.
Schmix said:
But now it comes up with a different error; It says "/system/xbin/nc has unexpected contents".
So yeah, i have no idea on how to fix this problem, but i would be okay with having to reset my phone.
Click to expand...
Click to collapse
That's expected
There are a few methods to solve your problem.
The easiest one is RUU it back to stock.
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2735235
You need to relock bootloader and also make a backup of your internal storage files/pic/music or whatever you like to keep.
The RUU will update your device to the latest
ckpv5 said:
That's expected
There are a few methods to solve your problem.
The easiest one is RUU it back to stock.
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2735235
You need to relock bootloader and also make a backup of your internal storage files/pic/music or whatever you like to keep.
The RUU will update your device to the latest
Click to expand...
Click to collapse
But i don't have S-Off... is that a problem?
And are the files correct?
Schmix said:
But i don't have S-Off... is that a problem?
And are the files correct?
Click to expand...
Click to collapse
You don't have S-Off - that's why you need to relock bootloader
That's the only difference - read the thread thoroughly.
First step - relock bootloader with command fastboot oem lock
then follow the step 3 onwards
Also note you need to use htc_fastboot.exe not the usual fastboot.exe
Anything you need to ask, you can ask there. I believe @EddyOS will gladly help you
ckpv5 said:
You don't have S-Off - that's why you need to relock bootloader
That's the only difference - read the thread thoroughly.
First step - relock bootloader with command fastboot oem lock
then follow the step 3 onwards
Also note you need to use htc_fastboot.exe not the usual fastboot.exe
Anything you need to ask, you can ask there. I believe @EddyOS will gladly help you
Click to expand...
Click to collapse
Keep meaning to add a few bits that can be done with S-ON, been super busy of late!
ckpv5 said:
You don't have S-Off - that's why you need to relock bootloader
That's the only difference - read the thread thoroughly.
First step - relock bootloader with command fastboot oem lock
then follow the step 3 onwards
Also note you need to use htc_fastboot.exe not the usual fastboot.exe
Anything you need to ask, you can ask there. I believe @EddyOS will gladly help you
Click to expand...
Click to collapse
Thank you very much, I got it to work now!
Have a good day!
ckpv5 said:
Wrong stock recovery image.
OTA needs stock recovery 3.28.401.9 (389838.9) or 4.16.401.10 (448934.10)
but you installed 3.28.401.6 (389838.6)
Get the right recovery image, OTA will proceed.
I have one here - 3.28.401.9_recovery.img : http://sourceforge.net/projects/htconem8/files/Recovery/3.28.401.9_recovery.img/download
Click to expand...
Click to collapse
I have the same issue with my htc desire 820n can you help me pleas
ammarhigh said:
I have the same issue with my htc desire 820n can you help me pleas
Click to expand...
Click to collapse
I believe you do know this is M8 thread and not HTC Desire 820n
But .. this is what you can do to fix your problem ...
Check for OTA as usual, download OTA then select install later.
Connect your device to PC then copy the OTA zip from internal storage\download folder to PC
Open the OTA zip with 7-zip, you'll see firmware.zip. Open firmware.zip and extract out recovery.img <--- this is the one that you need.
Boot your device to bootloader
Fastboot flash this extracted recovery.img
Reboot, check for OTA again, this time select install now
Done
I'm sorry for posting here but i did it and it's not working when i'm flashing the recovery i tooked it from the OTA it's give me error when flashing it the update is lollipop and i'm on kitkat 4.4.4
Sent from my HTC Desire 820 using XDA Free mobile app
Guys please help me i just bought my phone and i am without OS already what a stupid i am i messed it up by using twrp and i didn't back up my stock rom dam it (( (((
my phone is boot unlocked and carrier unlocked ( i guess cos i am in cyprus and i got it from hong kong ) or maybe carrier is GSM ? how do i find this out
could you please someone give me a link to a pure HT C stock rom so i can update it to 5.0.1 ?
i found this on here but i can't see the link or there is no link
http://forum.xda-developers.com/showthread.php?t=2694994
please help me
than you so much in advance
post fastboot getvar all result (minus serial no & imei no)
then people will know which ROM version is yours.
I have managed to delete everything ( i think ) from my phone. Below is my data. I am S-ON , unlock bootloader. If i flashed custom bootloader , it tells me that i don t have OS installed.
How can i recover that ?
Thank in advanced.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
dotexe said:
I have managed to delete everything ( i think ) from my phone. Below is my data. I am S-ON , unlock bootloader. If i flashed custom bootloader , it tells me that i don t have OS installed.
How can i recover that ?
Thank in advanced.
Click to expand...
Click to collapse
First ... remove the serial no. & imei no in your post as they are sensitive info.
You have 3 options :
1. Restore 4.16.401.10 TWRP backup - http://forum.xda-developers.com/showpost.php?p=60147089&postcount=5104
It read as WWE 4.20.401.10 TWRP Backup but that's typo error .. it should read as WWE 4.19.401.10 TWRP Backup
or
2. Relock your bootloader and install 4.16.401.10 RUU.exe - http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1
(make backup of your internal storage important data as this will wipe everything)
or
3. Relock your bootloader and fastboot flash the 4.16.401.10 RUU.zip - http://forum.xda-developers.com/showthread.php?t=2735235
(make backup of your internal storage important data as this will wipe everything and also note you need htc_fastboot instead of normal fastboot)
thanks for your fast response.
adb restore <file name> ?
4.16.401.10_HTC__001_TWRP.7z
It is 7zip . This should be repacked as a normal ZIP ?
edit
d:\htc\One\Data>adb restore 4.16.401.10_HTC__001_TWRP.ZIP
adb: unable to connect for backup
dotexe said:
thanks for your fast response.
adb restore <file name> ?
4.16.401.10_HTC__001_TWRP.7z
It is 7zip . This should be repacked as a normal ZIP ?
edit
d:\htc\One\Data>adb restore 4.16.401.10_HTC__001_TWRP.ZIP
adb: unable to connect for backup
Click to expand...
Click to collapse
Read the thread linked in my signature on how to restore a TWRP backup.
You need to extract it with 7-zip and put those files in your backup folder not to ADB it nor fastboot it.
hi guys
I have similar problem.
i flashed stock recovery and ran OTA update 4.16.401.13 (i think) on modified, unlocked, rooted, S-ON HTC One M8 in South Africa, and now stuck on boot logo or black screen.
This is my details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
software number was 4.16.401.10 before OTA update.
can i also use the files above to try to fix the phone?
Thank you. restore is in progress.
After restore i will flash back stock recovery and then relock the bootloader.
If i do that, my top line in bootloader will disappear ? right now is : "Software status: Modified "
Herschelle said:
hi guys
I have similar problem.
i flashed stock recovery and ran OTA update 4.16.401.13 (i think) on modified, unlocked, rooted, S-ON HTC One M8 in South Africa, and now stuck on boot logo or black screen.
software number was 4.16.401.10 before OTA update.
can i also use the files above to try to fix the phone?
Click to expand...
Click to collapse
Yes .. you can use them.
I just put up a link in my thread for my own 4.16.401.10 TWRP backup.
Check : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 10:54 PM ---------- Previous post was at 10:51 PM ----------
dotexe said:
Thank you. restore is in progress.
After restore i will flash back stock recovery and then relock the bootloader.
If i do that, my top line in bootloader will disappear ? right now is : "Software status: Modified "
Click to expand...
Click to collapse
No need to relock bootloader.
Only when running RUU.exe or RUU.zip you need to relock bootloader when S-On.
Using a backup no need to relock bootloader. Just flash stock recovery then do OTA.
If that backup fails (as I'm not sure whether that's fully stock or not), I put up my own stock backup in my thread .. you can try that later if current one fails.
Restore successfully completed. Now, in order not to have problems with latest OTA , i have to restore stock recovery, right ?
dotexe said:
Restore successfully completed. Now, in order not to have problems with latest OTA , i have to restore stock recovery, right ?
Click to expand...
Click to collapse
Yes .. 4.16.401.10 stock recovery
Herschelle said:
hi guys
I have similar problem.
i flashed stock recovery and ran OTA update 4.16.401.13 (i think) on modified, unlocked, rooted, S-ON HTC One M8 in South Africa, and now stuck on boot logo or black screen.
Click to expand...
Click to collapse
Are you sure that you started installing OTA after flashing stock recovery ?
dotexe said:
Are you sure that you started installing OTA after flashing stock recovery ?
Click to expand...
Click to collapse
Yes. OTA downloaded and I tried twice to install, but all it did was restart phone into bootloader.
After flashing stock recovery, I rebooted phone, ran OTA and update started.
After update completed, phone rebooted to white start screen with HTC logo and froze there.
I have read that this is probably because I ran OTA on rooted device.
So now i am stuck with no OS and hope these files will help.
Thanks ckpv5 for help and link.
stock nandroid restore worked. got my phone back
flashed stock recovery and running OTA again now. fingers crossed.
but whatever happens, just wanna say thanks again guys. much appreciated.
Please update us
dotexe said:
Please update us
Click to expand...
Click to collapse
YAY!
can confirm above files and files/procedure in signature link worked.
OTA worked and now updated to 4.16.401.13
thanks very much guys.
now to flash custom TWRP recovery and re-root.
if I may ask, what is the safest method to run OTA in future?
i dont really know. Anyway , how about your free space. i dont know what happened because now i have less that 1 GB free space.
Herschelle said:
YAY!
can confirm above files and files/procedure in signature link worked.
OTA worked and now updated to 4.16.401.13
thanks very much guys.
now to flash custom TWRP recovery and re-root.
if I may ask, what is the safest method to run OTA in future?
Click to expand...
Click to collapse
Boot the custom recovery and make a pure stock backup. Restore that one if you need to ota update again
dotexe said:
i dont really know. Anyway , how about your free space. i dont know what happened because now i have less that 1 GB free space.
Click to expand...
Click to collapse
The best solution for me if I ever have this problem .. I will format data (not wipe data) in TWRP before I restore the backup (of course need to backup internal storage data somewhere else first)
Done . Now i have free space. many thanks !!
I used to have a custom rom on my phone but I tried to wipe it and im not sure what happened but I don't think there's an OS on there anymore. It gets stuck on the HTC white screen. I am able to access fastboot and I have TWRP recovery installed that I'm able to access, but I believe it's an older version. I tried just downloading another rom and flashing it but it still wont boot. I'm not sure what I need to get it working again.
bavman said:
I used to have a custom rom on my phone but I tried to wipe it and im not sure what happened but I don't think there's an OS on there anymore. It gets stuck on the HTC white screen. I am able to access fastboot and I have TWRP recovery installed that I'm able to access, but I believe it's an older version. I tried just downloading another rom and flashing it but it still wont boot. I'm not sure what I need to get it working again.
Click to expand...
Click to collapse
First, what ROM you tried to install?
Tell me your current Firmware Version and CID (look in Bootloader).
DavidYouKnow? said:
First, what ROM you tried to install?
Tell me your current Firmware Version and CID (look in Bootloader).
Click to expand...
Click to collapse
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
bavman said:
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Yes your Firmware is the version-main and its empty, thats crappy.
First download this TWRP Stock Nandroid Backup: https://mega.nz/#!mYxDWApA!JbdLZAhYkz8fas5MpPfOQqGScikCLCmG21KBsjRJKQQ
Then use latest twrp recovery 3.0.2-0: https://dl.twrp.me/m8/twrp-3.0.2-0-m8.img.html and install it.
Here is the Stock Recovery that you need later: https://mega.nz/#!SUATBBbQ!-IUlr_tqnpkYFUM0bedRSRH3w__nCZjEAYls-5zncX4.
Then do this taken from this page: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
The basic idea is : fastboot flash recovery NameOfRecovery.img
2. Download TWRP backup - link in post #2 & post #3
3. Download stock recovery - link in post #4
4. Extract the downloaded x.xx.xxx.x_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6(a). Reboot, connect device to PC then
open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
open SD Card - TWRP/BACKUPS/SerialNo./ (if backup is set to MicroSD)
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
7. Transfer the extracted x.xx.xxx.x folder (not x.xx.xxx.x_ckpv5 folder) and its content to the backup path on your device, so it looks like this :
TWRP/BACKUPS/SerialNo./x.xx.xxx.x
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader (when TWRP asks whether you want to root your device, select do not install)
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery x.xxx.xx.x_recovery.img
12. reboot - check for OTA, download, install
13. you may have multiple OTA when your device currently on a lower version
14. done
If you want to flash TWRP again, use the latest TWRP after last OTA
NOTE : There is no need to relock bootloader when doing the nandroid way to revert to stock and do OTA.
Click to expand...
Click to collapse
..............................................................................
And then install the twrp recovery and your custom ROM, tell me what ROM you want to install ?
DavidYouKnow? said:
Yes your Firmware is the version-main and its empty, thats crappy.
First download this TWRP Stock Nandroid Backup:
********
And then install the twrp recovery and your custom ROM, tell me what ROM you want to install ?
Click to expand...
Click to collapse
These won't work for his device because his current firmware is too low.
---------- Post added at 05:45 PM ---------- Previous post was at 05:31 PM ----------
bavman said:
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You won't be able to run current ROMs because your firmware is too low version.
What you can do is run the latest RUU to get back to stock at Marshmallow firmware then reinstall TWRP to install any custom ROM that you like
1. You need these drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. You need to relock bootloader because your device is S-On, use command
fastboot oem lock
fastboot reboot-bootloader
3. You need to install htc signed 6.20.531.5 firmware
Download :
https://mega.nz/#!yIhBTRKJ!5rZldUEzCaFqYUhomn4mO_IgA_-nW6-gV9HX5LCzT5Y
run commands
fastboot oem rebootRUU
fastboot flash zip fw_6.20.531.5.zip
you'll see error : FAILED
repeat fastboot flash zip fw_6.20.531.5.zip
fastboot reboot-bootloader
4. You need to install the latest 6.20.531.5 RUU
Download : http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
right click the RUU.exe and select run as administrator, follow the instructions - agree/accept, next,next,update,blablabla until it finish.
Now you'll have a out of the box state device.
You can unlock the bootloader again with the unlock_code.bin
Re install TWRP - use the latest TWRP 3.0.2-0
You can install any custom ROM that you like.
All the above procedure require you to put the device on bootloader/fastboot mode and connect to PC.
The above procedure will wipe everything in your device including internal storage data/files (if you want to backup first, install TWRP 2.8.1.0 and in recovery you can enable MTP after connect to PC to copy out files from Internal storage)
All these require you to have a Windows PC with USB2.0
DavidYouKnow? said:
Yes your Firmware is the version-main and its empty, thats crappy.
Click to expand...
Click to collapse
Hboot 3.16 means OP is on 1.xx firmware.
Which also means the nandroid and stock recovery you suggested are off by 3 versions (4.xx). Are you guessing at the version number?
ckpv5 has the best route. RUU will update the firmware, and get the phone back up and running.
redpoint73 said:
Hboot 3.16 means OP is on 1.xx firmware.
Which also means the nandroid and stock recovery you suggested are off by 3 versions (4.xx). Are you guessing at the version number?
ckpv5 has the best route. RUU will update the firmware, and get the phone back up and running.
Click to expand...
Click to collapse
No i didnt guessing at the version number, i thought that he have a higher Firmware version. Im so sorry, i had the problem earlier also on my M7 and yes then i have taken a RUU too, but that was off by 1 version And i haven't the Problem on my M7 with a clear os display in bootloader.
ckpv5 said:
These won't work for his device because his current firmware is too low.
---------- Post added at 05:45 PM ---------- Previous post was at 05:31 PM ----------
You won't be able to run current ROMs because your firmware is too low version.
What you can do is run the latest RUU to get back to stock at Marshmallow firmware then reinstall TWRP to install any custom ROM that you like
1. You need these drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. You need to relock bootloader because your device is S-On, use command
fastboot oem lock
fastboot reboot-bootloader
3. You need to install htc signed 6.20.531.5 firmware
Download :
https://mega.nz/#!yIhBTRKJ!5rZldUEzCaFqYUhomn4mO_IgA_-nW6-gV9HX5LCzT5Y
run commands
fastboot oem rebootRUU
fastboot flash zip fw_6.20.531.5.zip
you'll see error : FAILED
repeat fastboot flash zip fw_6.20.531.5.zip
fastboot reboot-bootloader
4. You need to install the latest 6.20.531.5 RUU
Download : http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
right click the RUU.exe and select run as administrator, follow the instructions - agree/accept, next,next,update,blablabla until it finish.
Now you'll have a out of the box state device.
You can unlock the bootloader again with the unlock_code.bin
Re install TWRP - use the latest TWRP 3.0.2-0
You can install any custom ROM that you like.
All the above procedure require you to put the device on bootloader/fastboot mode and connect to PC.
The above procedure will wipe everything in your device including internal storage data/files (if you want to backup first, install TWRP 2.8.1.0 and in recovery you can enable MTP after connect to PC to copy out files from Internal storage)
All these require you to have a Windows PC with USB2.0
Click to expand...
Click to collapse
Thanks for this information. I had tried to revert back to stock using that exact RUU from the HTC website but it would keep failing and I didn't know why. Using the stock firmware steps you included got it work. I appreciate the help.
bavman said:
Thanks for this information. I had tried to revert back to stock using that exact RUU from the HTC website but it would keep failing and I didn't know why. Using the stock firmware steps you included got it work. I appreciate the help.
Click to expand...
Click to collapse
If you had posted the RUU failure symptoms (Error number and message, if there was one; specific behavior and results, etc.) we could have helped there (and still be happy to, if you are at all curious about getting RUU to work). But it looks like you sorted it without RUU, anyway.
---------- Post added at 09:43 AM ---------- Previous post was at 09:38 AM ----------
DavidYouKnow? said:
Im so sorry, i had the problem earlier also on my M7 and yes then i have taken a RUU too, but that was off by 1 version And i haven't the Problem on my M7 with a clear os display in bootloader.
Click to expand...
Click to collapse
Restoring by RUU versus nandroid are two completely different things, and you should be careful not to confuse the two:
RUU re-writes all partitions, including firmware, so there is no chance of a mismatch between firmware and ROM. Therefore, you don't need to match the RUU version to firmware, as long as the RUU is equal or greater number than the current firmware on the phone (no "downgrading" with s-on). And with s-off, this requirement is removed entirely, so you can run any version RUU that matches your CID, MID.
Restoring by nandroid is a completely different animal. Nandroid just contains the ROM and kernel. It needs to match the firmware on the phone, otherwise it won't work properly.
redpoint73 said:
If you had posted the RUU failure symptoms (Error number and message, if there was one; specific behavior and results, etc.) we could have helped there (and still be happy to, if you are at all curious about getting RUU to work). But it looks like you sorted it without RUU, anyway.
Click to expand...
Click to collapse
I understand his post differently .. he managed to run RUU after firmware is flashed, a step his missed before (a needed step to run a MM RUU on lower firmware, but never told earlier).
ckpv5 said:
I understand his post differently .. he managed to run RUU after firmware is flashed, a step his missed before (a needed step to run a MM RUU on lower firmware, but never told earlier).
Click to expand...
Click to collapse
Now I understand. Its confusing, since the 2 methods (both of which have you to credit) to return to stock are both referenced in this thread (another user references the nandroid method); and folks often use the term "firmware" incorrectly to refer to the ROM.
It also means that the user did not follow your instructions in Post #5 in the proper sequence. So RUU failing was inevitable, and easily avoidable; if they had followed your instructions in the proper order.