Related
Dear Community
As I wanted to update my ROM to Android 5, but with working WiFi, i tried to flash a new firmware. I'm on S-ON. My HBOOT is 3.16. After relocking and booting to RUU-Mode I attempted to flash the firmware.zip (version 4.19.161.2) which leaded to failure with error code 42. My CID is VODAP110 (Swisscom). After this not working i rebooted to fastboot, unlocked the bootloader again, reflashed recovery (philZ-touch, latest version). I tried to reboot and ended in a bootloop. So I went to recovery and reflashed the OS (SlimKat 4.4.4, build 8). After rebooting i was still in bootloop. I tried already to flush the cache, but this didn't help either.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.
Also, here is my getvar all Dump:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(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: VODAP110
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.339s
Click to expand...
Click to collapse
Greetings,
Michael
ppcinj said:
Dear Community
As I wanted to update my ROM to Android 5, but with working WiFi, i tried to flash a new firmware. I'm on S-ON. My HBOOT is 3.16. After relocking and booting to RUU-Mode I attempted to flash the firmware.zip (version 4.19.161.2) which leaded to failure with error code 42. My CID is VODAP110 (Swisscom). After this not working i rebooted to fastboot, unlocked the bootloader again, reflashed recovery (philZ-touch, latest version). I tried to reboot and ended in a bootloop. So I went to recovery and reflashed the OS (SlimKat 4.4.4, build 8). After rebooting i was still in bootloop. I tried already to flush the cache, but this didn't help either.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.
Also, here is my getvar all Dump:
Greetings,
Michael
Click to expand...
Click to collapse
Delete the Serial Number and the IMEI.
UniversalKID said:
Delete the Serial Number and the IMEI.
Click to expand...
Click to collapse
Could you please point me to an tutorial how to do so?
ppcinj said:
Could you please point me to an tutorial how to do so?
Click to expand...
Click to collapse
He means from your first post - it's not wise to show the IMEI and serial number of your device as someone could clone your phone
EddyOS said:
He means from your first post - it's not wise to show the IMEI and serial number of your device as someone could clone your phone
Click to expand...
Click to collapse
Oh, ok, thanks for the correction
ppcinj said:
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.
Greetings,
Michael
Click to expand...
Click to collapse
What you need is a 2.xx.166.x 1.xx.166.x backup, but I don't have any idea on the full no.
So to have a working phone so you can make a phone call, temporarily just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup from this thread : http://forum.xda-developers.com/showthread.php?t=2701376
That's only a temp solution until you can find a right backup and firmware for your hboot 3.16.0000
If you want a Android for 5.0, you need firmware 4.19.166.2 which is available but I'm not sure whether you can jump from hboot 3.16.0000 directly to 3.19.0000
Jump should be fine, so long as it goes through without an error but I've gone from 3.16.0000 to 3.19.0000 having converted back from GPe to latest Lollipop RUU
EddyOS said:
Jump should be fine, so long as it goes through without an error but I've gone from 3.16.0000 to 3.19.0000 having converted back from GPe to latest Lollipop RUU
Click to expand...
Click to collapse
I know it's ok for S-Off device, just not sure about S-On. Let's see what OP intend to do now.
ckpv5 said:
I know it's ok for S-Off device, just not sure about S-On. Let's see what OP intend to do now.
Click to expand...
Click to collapse
Yeah, good point.
It shouldn't be a problem going UP a version but going down won't work without S-OFF...
ckpv5 said:
I know it's ok for S-Off device, just not sure about S-On. Let's see what OP intend to do now.
Click to expand...
Click to collapse
Ok, but what exactly do I need now? Could you help me out finding the right file? I found backups for 2.x.161.x, but not for 2.x.166.x... And also what are the most secure steps for me to do now for avoiding a brick? Flashing the new 4.x.x.x so i can haz Android 5 or reverting to 2.x.x.x and stick with Android 4?
And also if you need some more data, screenshots, etc. feel free to ask for them
ppcinj said:
Ok, but what exactly do I need now? Could you help me out finding the right file? I found backups for 2.x.161.x, but not for 2.x.166.x... And also what are the most secure steps for me to do now for avoiding a brick? Flashing the new 4.x.x.x so i can haz Android 5 or reverting to 2.x.x.x and stick with Android 4?
And also if you need some more data, screenshots, etc. feel free to ask for them
Click to expand...
Click to collapse
I wrote "just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup" means any 2.xx.xxx.x 1.xx.xxx.x including the EU WWE... this just to get your device working again. But you're stuck at 4.4.2 for awhile. This is what at least you need for now as mentioned on post #1
Restoring a nandroid backup won't brick a device.
You can't install 4.xx.xxxx.x because hboot is too low version.
Damn ... just notice I gave you wrong info. hboot 3.16.0000 you can restore only 1.xx.xxx.x backup
ckpv5 said:
I wrote "just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup" means any 2.xx.xxx.x 1.xx.xxx.x including the EU WWE... this just to get your device working again. But you're stuck at 4.4.2 for awhile. This is what at least you need for now as mentioned on post #1
Restoring a nandroid backup won't brick a device.
You can't install 4.xx.xxxx.x because hboot is too low version.
Damn ... just notice I gave you wrong info. hboot 3.16.0000 you can restore only 1.xx.xxx.x backup
Click to expand...
Click to collapse
Maybe this doesn't mean anything, but my OS is Version 4.4.4. (At least, this is what they say on the official Page & in Settings)
ppcinj said:
Maybe this doesn't mean anything, but my OS is Version 4.4.4. (At least, this is what they say on the official Page & in Settings)
Click to expand...
Click to collapse
I don't know anything when it comes to AOSP ROM requirement.
What I talked about here is to get your device up and running on Sense ROM.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.Your fastboot getvar all tells that your original Sense OS is 4.4.2
ckpv5 said:
I wrote "just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup" means any 2.xx.xxx.x 1.xx.xxx.x including the EU WWE... this just to get your device working again. But you're stuck at 4.4.2 for awhile. This is what at least you need for now as mentioned on post #1
Restoring a nandroid backup won't brick a device.
You can't install 4.xx.xxxx.x because hboot is too low version.
Damn ... just notice I gave you wrong info. hboot 3.16.0000 you can restore only 1.xx.xxx.x backup
Click to expand...
Click to collapse
I've tried now to restore the zip file... I used this one: 1.54.401.5 - CWM Philz touch. After restoration process I rebooted the system and then the Slimkat logo appeared again, and it's still in bootloop.:crying:
Edit: This is one problem i noticed already some time ago: I couldn't flash any other rom than slimkat since i flashed it the first time...
Edit2: Also After I flashed philz once I couldn't go back to twrp... THen it stuck in "Entering recovery" screen.
Sorry, i was an idiot, i didn't realise, that i need to extract the zip first -.-. I will try it again now.
ckpv5 said:
I don't know anything when it comes to AOSP ROM requirement.
What I talked about here is to get your device up and running on Sense ROM.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.Your fastboot getvar all tells that your original Sense OS is 4.4.2
Click to expand...
Click to collapse
Ok, im trying to restore now one of the downloaded Backups, however i can't manage to do so... It's always checking for img files, however it doesnt find them, and therefore doesn't restore them... Do I need to do anything special with the downloaded files?
ppcinj said:
Ok, im trying to restore now one of the downloaded Backups, however i can't manage to do so... It's always checking for img files, however it doesnt find them, and therefore doesn't restore them... Do I need to do anything special with the downloaded files?
Click to expand...
Click to collapse
I expect you know how to use a nandroid backup zip.
I want to help you but I'm not familiar with Philz recovery, only TWRP
The basic thing is, the nandroid backup zip to be extracted on PC. Then transfer the extracted the last folder that you see with its contents to recovery backup folder.
Also make sure the backup is meant for the right recovery.
What I read : philz --> Clockworkmod\Backups\
What I know : TWRP --> TWRP\BACKUPS\serialno\BackupFolderHere
For TWRP, simply make a nandroid backup of your boot, so you'll see the correct path then paste the nandroid folder that you extracted to this folder
ckpv5 said:
I expect you know how to use a nandroid backup zip.
I want to help you but I'm not familiar with Philz recovery, only TWRP
The basic thing is, the nandroid backup zip to be extracted on PC. Then transfer the extracted the last folder that you see with its contents to recovery backup folder.
Also make sure the backup is meant for the right recovery.
What I read : philz --> Clockworkmod\Backups\
What I know : TWRP --> TWRP\BACKUPS\serialno\BackupFolderHere
For TWRP, simply make a nandroid backup of your boot, so you'll see the correct path then paste the nandroid folder that you extracted to this folder
Click to expand...
Click to collapse
Ok, this worked for now and my Mobile is back in running state. Because of a strange feeling in my stomach i think that it's not possible now to simply download an OTA and get the new Android 5? What options do I have to get android 5?
ppcinj said:
Ok, this worked for now and my Mobile is back in running state. Because of a strange feeling in my stomach i think that it's not possible now to simply download an OTA and get the new Android 5? What options do I have to get android 5?
Click to expand...
Click to collapse
Not possible unless:
1. Use SunShine (paid service) to S-Off then you can flash other region ROM
or
2. Search/google around for a backup for your region device 1.xx.166.x (I have no idea the exact no.)
or
3. A risky one - flash your region 5.0 firmware 4.19.166.2 then install any 5.0 ROM .. I cannot guarantee this will work on hboot 3.16 as its a big jump from 3.16 to 3.19 .. you may brick your device.
ckpv5 said:
Not possible unless:
1. Use SunShine (paid service) to S-Off then you can flash other region ROM
or
2. Search/google around for a backup for your region device 1.xx.166.x (I have no idea the exact no.)
or
3. A risky one - flash your region 5.0 firmware 4.19.166.2 then install any 5.0 ROM .. I cannot guarantee this will work on hboot 3.16 as its a big jump from 3.16 to 3.19 .. you may brick your device.
Click to expand...
Click to collapse
You have written a second time 1.xx.166.x. Are you sure about this, and that it's not the .161 region?
ppcinj said:
You have written a second time 1.xx.166.x. Are you sure about this, and that it's not the .161 region?
Click to expand...
Click to collapse
Your fastboot getvar tells that :
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP110x.xx.166.x
modelid: 0P6B10000
cidnum: VODAP110
cidnum: VODAP120
mainver: 4.19.166.2
There is no CID VODAP110 in
x.xx.161.x
modelid: 0P6B10000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAP405
cidnum: VODAPE17
cidnum: VODAPD18
cidnum: VODAP304
mainver: 2.22.161.6
Good luck ... got to rest now
Would there be any possible way to update my firmware without unrooting my phone?
Here is my bootloader information but my main version did not seem to show up.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA43NWM05793
(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: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 06f11f5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What exactly are you trying to accomplish: stock updated Marshmallow (or Lollipop?) ROM (but with root), custom ROM, etc.?
Does it read LOCKED, RELOCKED, or UNLOCKED near the top of the bootloader screen?
It reads unlocked on the bootloader
I was wanting to revert my HTC back to complete stock. But now I basically want the latest firmware. I just don't know if the main version being blank has anything to do with it where it could brick my phone.
redpoint73 said:
What exactly are you trying to accomplish: stock updated Marshmallow (or Lollipop?) ROM (but with root), custom ROM, etc.?
Does it read LOCKED, RELOCKED, or UNLOCKED near the top of the bootloader screen?
Click to expand...
Click to collapse
It reads unlocked on the bootloader
I was wanting to revert my HTC back to complete stock. But now I basically want the latest firmware. I just don't know if the main version being blank has anything to do with it where it could brick my phone.
XtreMe579 said:
now I basically want the latest firmware.
Click to expand...
Click to collapse
I think you may be confusing the term "firmware" (using it interchangeably with "ROM"). Do you want to update to stock T-Mobile Marshmallow OS, plus latest hboot, radio, etc.?
If so, one option is to run the RUU linked at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
The RUU will wipe the phone, so backup anything you want to keep before RUU. Also, you'll need to root again. But really, since you are s-off and bootloader unlocked, the matter of rooting will take about 5 minutes, and should be the least of your worries.
The RUU will update you to the Marshmallow OS, including firmware (hboot, radio, etc.). From there you can just flash TWRP back onto the phone, and SuperSU 2.65 to root again.
XtreMe579 said:
I just don't know if the main version being blank has anything to do with it where it could brick my phone.
Click to expand...
Click to collapse
No, it won't. Main version being blank if very common, its a result of using certain TWRP builds, and doesn't really affect anything (aside from you not knowing what the present main version is!).
redpoint73 said:
I think you may be confusing the term "firmware" (using it interchangeably with "ROM"). Do you want to update to stock T-Mobile Marshmallow OS, plus latest hboot, radio, etc.?
If so, one option is to run the RUU linked at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
The RUU will wipe the phone, so backup anything you want to keep before RUU. Also, you'll need to root again. But really, since you are s-off and bootloader unlocked, the matter of rooting will take about 5 minutes, and should be the least of your worries.
The RUU will update you to the Marshmallow OS, including firmware (hboot, radio, etc.). From there you can just flash TWRP back onto the phone, and SuperSU 2.65 to root again.
No, it won't. Main version being blank if very common, its a result of using certain TWRP builds, and doesn't really affect anything (aside from you not knowing what the present main version is!).
Click to expand...
Click to collapse
Sweet! Sounds like a piece of cake! Well I'll give it a try once I have some free time on my hands! Thank you
XtreMe579 said:
Sweet! Sounds like a piece of cake!
Click to expand...
Click to collapse
In theory, yes. Although hiccups can sometimes occur with RUU. If you have any issues, take note of any error messages, etc. and come back here and we'll troubleshoot (Error 155 is common with the MM RUUs).
redpoint73 said:
In theory, yes. Although hiccups can sometimes occur with RUU. If you have any issues, take note of any error messages, etc. and come back here and we'll troubleshoot (Error 155 is common with the MM RUUs).
Click to expand...
Click to collapse
I'll keep that in mind. Hopefully I don't get that error and everything runs smooth and dandy
redpoint73 said:
In theory, yes. Although hiccups can sometimes occur with RUU. If you have any issues, take note of any error messages, etc. and come back here and we'll troubleshoot (Error 155 is common with the MM RUUs).
Click to expand...
Click to collapse
Dang got that Error 155. Any recommendations on how to go past it?
XtreMe579 said:
Dang got that Error 155. Any recommendations on how to go past it?
Click to expand...
Click to collapse
I thought that might happen. As mentioned, its common to get this when flashing the MM RUU on a device that presently has LP firmware. What you need to do is find the 6.20.531.5 firmware (meaning a zip that contains hboot, radio, and several other modules, but not meaning a ROM or a full RUU) and flash it with fastboot. After that, the RUU should run fine with no Error 155.
I'll try to take a look and see if I can find the firmware posted (don't know off hand).
EDIT: I've been looking, and can't find the 6.20.531.5 firmware.zip. Another way to update to MM firmware, is to run the 4.20.531.4 RUU to return to "full stock" then OTA update to MM. LP RUU is here: http://forum.xda-developers.com/showthread.php?t=2714456
EDIT2: Found the 6.20.531.5 firmware: https://www.androidfilehost.com/?fid=24438995911976759
So flash this by either method in Post #1 of the following thread (under "How to Flash" or "Alternative method"): http://forum.xda-developers.com/showthread.php?t=2754063
Then run the RUU again.
Thank you! Got it to work. Did the older version RUU then OTA to MM
Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!
A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.
Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.
Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).
Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.
Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.
Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(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:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.
My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse
Hello everyone,
I'd want to sell my HTC One M8, unlocked, with recovery and with a custom ROM. I'd want to return to stock (just flash the old firmware, without lock the bootloader).
How can I flash the old original firmware (maybe no-brand firmware)?
Thank you
First, I suggest you avoid using the word "firmware" the way you are. On this device, there is a package specifically named "firmware.zip" which is a small zip (around 80 MB) that contains a few partitions necessary for the ROM to work (hboot, kernel, radio, etc.) but does not actually contain the stock ROM itself (which is much larger, about 1.5 GB).
In fact, taken literally, flashing the stock firmware (with s-on) without then flashing RUU or ROM, will render the phone unable to boot to OS.
If you mean stock ROM, say stock ROM. If you mean RUU, say RUU.
You can restore a stock TWRP backup (stock ROM) and flash stock recovery to the device (without relocking the bootloader). But if there is an RUU available for your version, it's probably easier (and a better idea) to relock bootloader and RUU back to full stock.
In any case, it's probably not a good idea to sell the phone with the bootloader unlocked, unless the buyer is specifically asking for that (and aware what that means). Leaving it unlocked, leaves them vulnerable to a variety of issues, which they may not be remotely aware of. Most folks are not tech savvy, and will have no idea what an unlocked bootloader even means.
If you want more help (finding the right TWRP backup, RUU, etc.) do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
@redpoint73 Thank you for your satisfactory answer.
So, I would want to lock bootloader and then flash a RUU.
This are the results:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: yyy
(bootloader) imei: xxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: TIM__401
(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: e2b942c6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I've found, on my backup hard disk, three files:
3.31.901.9_ckpv5.zip (with relative recovery.img) (info in attached image)
4.20.901.3_ckpv5.zip (with relative recovery.img) (info in attached image)
2.22.901.5_firmware.zip (with relative recovery.img) related to 4.4.3 - TIM__401
Could they be useful?
Thank you very much.
.Fè said:
I've found, on my backup hard disk, three files:
3.31.901.9_ckpv5.zip (with relative recovery.img) (info in attached image)
4.20.901.3_ckpv5.zip (with relative recovery.img) (info in attached image)
2.22.901.5_firmware.zip (with relative recovery.img) related to 4.4.3 - TIM__401
Click to expand...
Click to collapse
EDIT: The first 2 files you listed are TWRP backups. You can restore the backup 4.20.901.3 using the instruction listed here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The firmware file, as mentioned before, is not a full RUU or ROM, and will result in no boot.
redpoint73 said:
You should be able to relock the bootloader, and flash the 4.20.901.3 RUU.
3.31.901.9 will likely fail due to being a lower version number than what is on the phone (can deduce from the current radio baseband number, that the current OS number is probably 4.20.901.3). And you can't flash a lower version RUU ("downgrade") with s-on.
The firmware file, as mentioned before, is not a full RUU or ROM, and will result in no boot.
Click to expand...
Click to collapse
Thanks!
So, how can I flash the 4.20.901.3 RUU?
Thank you.
Actually, looking at the files in your screenshot, I realize those are not RUUs. They are TWRP backups.
I don't know if your version has RUU.
So you can restore the TWRP stock backup that you have (4.20.901.3 as I stated before is still correct) using the instructions in the following thread: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can also restore stock recovery 4.20.901.4, which you can download from Post #4 of the same thread.
Do not relock the bootloader in this case. I don't know if there is a way to revert to locked/relocked bootloader, and have a working phone, since there is no RUU for your version M8, that I know of. So it would be best to inform prospective buyers that the bootloader is unlocked.
My apologies for any confusion there. I've edited my previous post, to avoid any confusion by others reading this thread.
redpoint73 said:
Actually, looking at the files in your screenshot, I realize those are not RUUs. They are TWRP backups.
I don't know if your version has RUU.
So you can restore the TWRP stock backup that you have (4.20.901.3 as I stated before is still correct) using the instructions in the following thread: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can also restore stock recovery 4.20.901.4, which you can download from Post #4 of the same thread.
Do not relock the bootloader in this case. I don't know if there is a way to revert to locked/relocked bootloader, and have a working phone, since there is no RUU for your version M8, that I know of. So it would be best to inform prospective buyers that the bootloader is unlocked.
My apologies for any confusion there. I've edited my previous post, to avoid any confusion by others reading this thread.
Click to expand...
Click to collapse
Ok, I will use TWRP to install my stock backup.
I would want to know if it could be possible to flash a no-brand RUU, instead of the stock one? Thank you.
.Fè said:
I would want to know if it could be possible to flash a no-brand RUU, instead of the stock one? Thank you.
Click to expand...
Click to collapse
No, it's not possible to flash an RUU intended for another version M8 (another CID) unless you get s-off (need s-off to change the CID). And the only working method to get s-off is by sunshine ($25 US), and it's not worth spending money on a phone you are trying to sell.
Doing a quick Google search, there is an RUU 4.20.901.4, but you have to pay money to download it. Again, not worth it. Use the TWRP backup approach, as already described.
SOLVED - THANKS!
Dear community,
Goal: I want to put a HTC One M8 device into stock. The phone used to be unlocked before and had a custom rom (think it was LineAge).
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Please understand, that I am very new to the topic and have read a lot of stuff, tutorials and because of so many different information and missing experience from my side, I am not sure what to do.
fastboot getvar all
(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: 4.16.401.13
(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__203
(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
all: Done!
finished. total time: -0.000s
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s
Think because the bootloader is locked?
I have really no clue how to proceed.
gskill150 said:
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Click to expand...
Click to collapse
Probably correct, that mostly likely, you restored the wrong TWRP backup version (not compatible with the firmware on the phone - firmware is not the same thing as the ROM or TWRP backup - that part may be confusing).
What version number TWRP backup did you restore (using the guide)?
gskill150 said:
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s
Think because the bootloader is locked?
Click to expand...
Click to collapse
Yes, this is because you relocked the bootloader. You can't flash a custom recovery with a locked or relocked bootloader, by definition.
But relocking the bootloader is not part of the guide, in regards to restoring a TWRP backup. What exactly were you trying to accomplish the relocking the bootloader?
I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories. I would try this next. Or what do you recommend?
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Thanks and best regards
gskill150 said:
I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
Click to expand...
Click to collapse
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
gskill150 said:
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories.
Click to expand...
Click to collapse
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
gskill150 said:
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Click to expand...
Click to collapse
In short, yes, that is the current version number of the firmware on the phone.
When "firmware" is discussed for this device, it does not refer to the ROM or OS number. But rather, firmware is a small file that is needed for the ROM to work and includes hboot, radio, and a number of other partitions (Bluetooth, WiFI), but does not contain the ROM itself. This is confusing, as some folks like to use the terms "firmware" and "ROM" interchangeably. At least for this device, you should wipe that notion from your mind.
Flashing a custom ROM or restoring a stock TWRP backup will not touch firmware, as flashing a ROM by TWRP will only change the system and boot.img partitions, and not touch things like hboot, radio. And flashing a ROM in TWRP will also not affect the version number reported in getvar. That number will only change if you flash firmware.zip or RUU.
RUU is a complete factory image (40+ partitions) which also includes firmware. Some folks will call the RUU the "stock ROM" but you can now see, it is much more than that.
A little confusing, right?
First of all, many thanks for your detailed help and sorry for providing incomplete information from my side. This topic is really hard to understand and confuses me a lot. Sorry for that.
redpoint73 said:
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
Click to expand...
Click to collapse
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
Click to expand...
Click to collapse
Sorry for that - as written I am new to the topic and was mixing up things that do not belong together (RUU, ROM, firmware). Again in a few words: phone used to have LineAgeOS (CustomRom) and I just wanted get rid of it and restore the original android version as if I had bought the phone completely new
I tried it through TWRP because I found this tutorial here in the forum and thought this would be the right path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
Click to expand...
Click to collapse
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
Click to expand...
Click to collapse
I meant the RUUs from the other guide I have just posted above
A little confusing, right?
Click to expand...
Click to collapse
To be honest, now it is completely clear to me thanks to your really good explanation. Thanks mate!
So I could go for the ruu.zip flashing path to achieve what I want right?
gskill150 said:
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
Click to expand...
Click to collapse
That is the right number stock backup to restore (same number as firmware number - version main in getvar). I don't know why you are having issues with WiFi and Bluetooth.
Might be a problem with the firmware. Flashing RUU is probably the best approach. Not only will it restore the stock ROM, but also restore stock firmware. Which hopefully will resolve your WiFi and Bluetooth issue.
gskill150 said:
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
So I could go for the ruu.zip flashing path to achieve what I want right?
Click to expand...
Click to collapse
That RUU should be okay. Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).
redpoint73 said:
Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).
Click to expand...
Click to collapse
Hi, thanks for your reply. I will give it a try! :good:
gskill150 said:
Hi, thanks for your reply. I will give it a try! :good:
Click to expand...
Click to collapse
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!
gskill150 said:
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!
Click to expand...
Click to collapse
You're quite welcome. Glad it worked for you.
Hello guys,
I have an HTC one m8 , I have been running a rooted device with custom rom which has been working terribly on my device...Now I want to return to stock rom, I have relocked bootloader and it's on s-on...I have tried out diverse RUU but all seems not working...I'm always getting this error in the process "rom update utility cannot update your andriod phone"" which i guess the ruu's have been using are not compatible with my phone...I would so much appreciate if anyone can get me the RUU executable file for my device that will be compatible with it........ Here is the fastboot getvar all details....Your prompt responses will be appreciated
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: S**********6
(bootloader) imei: 35*************7
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Jjohnson0830 said:
I have tried out diverse RUU but all seems not working...
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
Click to expand...
Click to collapse
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.
redpoint73 said:
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.
Click to expand...
Click to collapse
Ok, pls where can i get the stock TWRP backup and how am i going to return to stock using it?
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again
Jjohnson0830 said:
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again
Click to expand...
Click to collapse
No, you really don't. Please.