Hi there,
I am using an HTC One M8. I was using a SkyDragon ROM (SkyDragon+M8+v+3.1+WWE+Sense+7.zip). It was buggy as hell, the phone seemed to be happy for a while but as time went on it just slowed down and slowly camera performance started to degrade. Eventually the camera simply wouldn't work. I view this as a software related issue. I thought maybe it would be better to change to a different more recent ROM so I installed ViperOneM8 4.3.0 and got the phone running again. The camera still doesn't work.
I've searched on Google for a fix to this issue but most posts either suggest a clearing of the camera cache (which didn't work) OR a factory reset (which I didn't do because I just installed a new ROM, so same thing right??) OR they suggest tweaking some setting in your LastPass Manager or other password management tools (I don't have these installed).
I've tried other camera apps to see if it can get working but no other camera app works either, they all give similar errors, "Camera not working", OR "Can't connect to camera", and so on....
I don't believe this to be a hardware failure, it must be a software fault because everything was fine until I unlocked the boot loader and started installing custom ROM's. Any help will be greatly appreciated. Oh and in case anyone is curious I am on the latest version of TWRP, and I have repaired permissions (not that its necessary). Thanks for the help guys
Regards,
Saragn
Did you make a nandroid of you stock ROM? If so, restore it and see if the camera issue persists.
If not, why the heck not???
redpoint73 said:
Did you make a nandroid of you stock ROM? If so, restore it and see if the camera issue persists.
If not, why the heck not???
Click to expand...
Click to collapse
Hi...I didn't make a NANdroid backup of the stock ROM. In hind sight I probably should have.
Try ruu to go back to stock and see if that makes a difference.... If in stock it doesn't work then you might have a hardware defect
danial.aw said:
Try ruu to go back to stock and see if that makes a difference.... If in stock it doesn't work then you might have a hardware defect
Click to expand...
Click to collapse
It's a hardware fault. I have a 3rd party app that is not a camera app BUT allows you to upload pics into the app via a camera function. When you hit the button to take a pic it connects to the camera but the picture is just stripes and purple haze. It's heat damage, I think.
Saragn said:
It's a hardware fault.
Click to expand...
Click to collapse
There is no way you can be sure of that, if you don't return to stock. It doesn't seem you've done any troubleshooting to confirm its not software or firmware. In particular, the firmware is the bridge between software and hardware, and can be fooling you into thinking its a hardware issue. And the fact the problem arose after flashing ROMs (and going from old ROMs to recent ROMs) is highly suspicious, and almost certainly means you firmware is outdated.
What is your hboot number?
redpoint73 said:
There is no way you can be sure of that, if you don't return to stock. It doesn't seem you've done any troubleshooting to confirm its not software or firmware. In particular, the firmware is the bridge between software and hardware, and can be fooling you into thinking its a hardware issue. And the fact the problem arose after flashing ROMs (and going from old ROMs to recent ROMs) is highly suspicious, and almost certainly means you firmware is outdated.
What is your hboot number?
Click to expand...
Click to collapse
Hi,
HBOOT number is: HBOOT-3.19.0.0000
Ok so maybe I should have mentioned why I thought its a hardware failure issue. When I unlocked the bootloader and installed the SkyDragon ROM the camera was fine, there was no issue with it whatsoever. That was for about a month. Then as time went on the camera app would cause the phone to seriously slow down when I tried using the camera. It would hang for up to two minutes, you would not be able to switch the phone off or do anything. When it did that you had to leave it to let it get over what ever was going on and then a restart would get the phone back to normal.
Then, after weeks and weeks of that, the camera eventually just died and would not start at all and that's where I am now with it. The next problem I have is that I do not know how to return to stock, I made no "NANDroid" backup of it before I installed the SkyDragon ROM. I didn't see anything on any of the forum "how-to" documents speak about doing a NANDroid backup, had I seen it I'd have done it.
So in short, I have done "some" troubleshooting, maybe just not to the level that you are comfortable with. So do you understand now why I think it's a hardware fault?
Thanks for the replies.
Saragn
Saragn said:
So do you understand now why I think it's a hardware fault?
Click to expand...
Click to collapse
Do you understand why I might be skeptical of that? See from your first post:
Saragn said:
I don't believe this to be a hardware failure, it must be a software fault because everything was fine until I unlocked the boot loader and started installing custom ROM's.
Click to expand...
Click to collapse
It seems your story is changing. Or at the least, you didn't give the full story to begin with, which makes it hard for us to help.
I'd still recommend returning to full stock. It certainly doesn't hurt, and helps to eliminate the possibility that its a software issue. You've now probably spent more time giving excuses to not return to stock; than it would have actually taken to do so.
Either find your stock nandroid for your CID from the collection here: http://forum.xda-developers.com/showthread.php?t=2701376
Or run the RUU if there is one for your CID.
redpoint73 said:
Do you understand why I might be skeptical of that? See from your first post:
It seems your story is changing. Or at the least, you didn't give the full story to begin with, which makes it hard for us to help.
I'd still recommend returning to full stock. It certainly doesn't hurt, and helps to eliminate the possibility that its a software issue. You've now probably spent more time giving excuses to not return to stock; than it would have actually taken to do so.
Either find your stock nandroid for your CID from the collection here: http://forum.xda-developers.com/showthread.php?t=2701376
Or run the RUU if there is one for your CID.
Click to expand...
Click to collapse
Well, yes, of course the story is changing because what I have experienced with the phone since posting this has made me think otherwise. It's been some time since the first post. At first I thought it was software but then the cues I got from the device seemed more hardware related. Being human my mind is allowed to change. My follow up posts have clearly explained everything.
I never discounted the idea of returning to stock, neither did I make excuses for not wanting to I don't think. You have a very funny way of helping someone mate, either way I do appreciate it, maybe not your tone, but that's irrelevant. Thank you for responding and helping out I do appreciate it.
@Saragn: a custom rom is just that. its been modified, hacked, changed, upgraded. it was built on the devs own phone which means it works perfect (unles he says why it doesnt) on that exact model.
even if you have that model its possible that there are minor differences that cause that rom to not work perfect on yours.
as @redpoint73 says, the only way really now is to go back completely to stock and try it again.
if it works then you will just have to try different roms until you find one that works for you.
if it doesnt, its almost certianly hardware and you need to return it. which will require it to be stock anyway.
this is a good time to learn how to take a nandroid backup so you can easily swap back again to try something else.
p.s. check out @redpoint73 thanks count. at least 3834 people on here appreciate what hes doing to help here and are obviously not bothered about his 'tone'
gazzacbr said:
@Saragn: a custom rom is just that. its been modified, hacked, changed, upgraded. it was built on the devs own phone which means it works perfect (unles he says why it doesnt) on that exact model.
even if you have that model its possible that there are minor differences that cause that rom to not work perfect on yours.
as @redpoint73 says, the only way really now is to go back completely to stock and try it again.
if it works then you will just have to try different roms until you find one that works for you.
if it doesnt, its almost certianly hardware and you need to return it. which will require it to be stock anyway.
this is a good time to learn how to take a nandroid backup so you can easily swap back again to try something else.
p.s. check out @redpoint73 thanks count. at least 3834 people on here appreciate what hes doing to help here and are obviously not bothered about his 'tone'
Click to expand...
Click to collapse
Hi,
Pardon the length of time it has taken me to reply. I was away on business for a while so couldn't really pay much attention to the phone. Ok so my CID number is HTC__016. Also, if I do a "getvar all" I get the following:
C:\>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.10
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.173s
I've looked for an RUU exe or zip that works. The RUU packages for this specific version (4.16.401.10) all come out corrupt. I've downloaded various versions from all over this forum, other forums, I think I've downloaded over 10GB in total, 7 or 8 different downloads and they all come out corrupt and so the RUU process doesn't work. I'm not sure where else to get an actual RUU file that works and that isn't corrupt.
Any ideas? Not sure what to do next. Thanks guys.
PS...Never mind about the tone, its how I read it....doesn't matter!
Saragn said:
Hi,
Pardon the length of time it has taken me to reply. I was away on business for a while so couldn't really pay much attention to the phone. Ok so my CID number is HTC__016. Also, if I do a "getvar all" I get the following:
C:\>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.10
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.173s
I've looked for an RUU exe or zip that works. The RUU packages for this specific version (4.16.401.10) all come out corrupt. I've downloaded various versions from all over this forum, other forums, I think I've downloaded over 10GB in total, 7 or 8 different downloads and they all come out corrupt and so the RUU process doesn't work. I'm not sure where else to get an actual RUU file that works and that isn't corrupt.
Any ideas? Not sure what to do next. Thanks guys.
PS...Never mind about the tone, its how I read it....doesn't matter!
Click to expand...
Click to collapse
ALSO....I've checked this thread: http://forum.xda-developers.com/showthread.php?t=2735235 and it doesn't seem to work. I can't get the device to be S-OFF as the thread suggests and it also doesn't show up as LOCKED....it still shows UNLOCKED. So I'm a bit lost now.
Saragn said:
ALSO....I've checked this thread: http://forum.xda-developers.com/showthread.php?t=2735235 and it doesn't seem to work. I can't get the device to be S-OFF as the thread suggests and it also doesn't show up as LOCKED....it still shows UNLOCKED. So I'm a bit lost now.
Click to expand...
Click to collapse
hi, the thread you are quoting there is for going completely back to stock for selling or rtm for repair.
you dont need to go that far.
S-ON/OFF is the security lock, you dont need to bother with that for what you are doing.
LOCKED/UNLOCKED is for the bootloader. you unlocked it to flash a custom rom now you have to relock it to go back to stock.
you will need to relock the bootloader for this if you are still S-ON but this can be done easily through fastboot usb on the phone and 'fastboot oem lock' from a command prompt.
if you have the right stock zip file for your phone you can flash it back to stock anyway by renaming it to 0P6BIMG.zip, copying it to the sd card and booting to hboot.
hboot it will check the file then ask if you want to install it.
note that you can open and view the zip file but cannot safely extract anything from it. it is probably not corrupt.
check the MD5 if you want to be really sure.
an ruu.exe can be done from windows but there are not many of those around.
(anyone else reading here please correct me if i am wrong)
gazzacbr said:
hi, the thread you are quoting there is for going completely back to stock for selling or rtm for repair.
you dont need to go that far.
S-ON/OFF is the security lock, you dont need to bother with that for what you are doing.
LOCKED/UNLOCKED is for the bootloader. you unlocked it to flash a custom rom now you have to relock it to go back to stock.
you will need to relock the bootloader for this if you are still S-ON but this can be done easily through fastboot usb on the phone and 'fastboot oem lock' from a command prompt.
if you have the right stock zip file for your phone you can flash it back to stock anyway by renaming it to 0P6BIMG.zip, copying it to the sd card and booting to hboot.
hboot it will check the file then ask if you want to install it.
note that you can open and view the zip file but cannot safely extract anything from it. it is probably not corrupt.
check the MD5 if you want to be really sure.
an ruu.exe can be done from windows but there are not many of those around.
(anyone else reading here please correct me if i am wrong)
Click to expand...
Click to collapse
Hi...Thanks for the response.
Ok so I've done all of that, oem lock...I have confirmed on multiple ROM's that I cannot open the zip file. When you try open it simply to view the contents windows says it cannot open the file as it is corrupt. I'm fairly certain I know how a zip file works and how to tell when the archive is corrupt. I tried each file on more than one computer and they all say the same thing so the file locations, mostly listed on threads on this forum, all result in faulty downloads. I have a big pipe at the office so can download anything fairly quickly. So I don't know where to find a zip file that works....I have done the whole renaming to 0P6BIMG.zip but the file does not work, none of them do...I've tried several downloads from several different locations and they are all corrupt.
Really, it can't be that much of a challenge to get back to stock. I don't know why the oem lock doesn't work but they device stays unlocked...the bootloader screen confirms this.
Hi,
not sure why the bootloader will not relock.
only other alternative is to pay $25 for sunshine and get S-OFF then you can install the rom without relocking the bootloader.
maybe if you mention the exact names of the stock roms you have tried, i assume they were from the xda rom collection, in that thread and check if someone has already used one of them.
did get the MD5 and check that out?
there is only one rom for mine (dual sim) which i downloaded before and that works perfectly, but as i said, i can actually open the zip file but just not extract it.
Related
So I thought I'd try GPE, was running Android Revolution HD with the 4.4.4 firmware & 1.21 WWE radio installed, S-Off, Unlocked and SuperCID.
Flashed the rooted GPE RUU via bootloader, which worked fine, except now I have no radio ("Baseband Unknown") and any attempt to flash an alternative radio, either via "fastboot flash radio" in the bootloader or "fastboot flash radio" in the RUU mode gives me errors.
WiFi works and the system seems otherwise stable.
Have I updated too far with an incompatible radio?
I've no doubt done something dumb or missed something obvious, but I've done a fair bit of digging and can't work out what, can anyone help?
knightnz said:
So I thought I'd try GPE, was running Android Revolution HD with the 4.4.4 firmware & 1.15 WWE radio installed, S-Off, Unlocked and SuperCID.
Flashed the rooted GPE RUU via bootloader, which worked fine, except now I have no radio ("Baseband Unknown") and any attempt to flash an alternative radio, either via "fastboot flash radio" in the bootloader or "fastboot flash radio" in the RUU mode gives me errors.
Have I updated too far with an incompatible radio?
I've no doubt done something dumb or missed something obvious, but I've done a fair bit of digging and can't work out what, can anyone help?
Click to expand...
Click to collapse
This is not the first time I've heard of this issue, but sorry, I don't have an answer. I've never run GPE.
Going back to a Sense based ROM might fix it.
But..... What's your firmware/hboot?
I'm not sure that it matters with GPE (actually I don't think it does), but maybe a firmware update would help?
---------- Post added at 07:12 PM ---------- Previous post was at 07:05 PM ----------
What model do you have? GSM or CDMA? GPE only works with GSM I believe.
EDIT: sorry, I see that you are WWE.
xunholyx said:
This is not the first time I've heard of this issue, but sorry, I don't have an answer. I've never run GPE.
Going back to a Sense based ROM might fix it.
But..... What's your firmware/hboot?
I'm not sure that it matters with GPE (actually I don't think it does), but maybe a firmware update would help?
Click to expand...
Click to collapse
I just tried flashing the standalone firmware update from the recovery, doesn't look like anything changed unfortunately.
The symptoms are much the same as when running a 4.4.4 ROM with a 4.4.3 firmware, but as far as I can understand, the full RUU should've had the required files, and if not, then flashing the firmware should've sorted it out.
The RUU I used is the rooted 4.4.4 - 2.12.1700.1 one as per graffixnyc's page from this thread: http://forum.xda-developers.com/showthread.php?t=2708589
The standalone 4.4.4 firmware is from http://www.randomphantasmagoria.com/firmware/htc-one-m8/m8_google/
Current HBOOT is 3.18.0.0000
Radio is 1.14.21331931.LA02_2G (So it _does_ look like it's "downgraded" it)
OS 2.12.1700.1
The actual phone is (I believe) an ex-Hong Kong GSM version which I WWE'd.
knightnz said:
I just tried flashing the standalone firmware update from the recovery, doesn't look like anything changed unfortunately.
The symptoms are much the same as when running a 4.4.4 ROM with a 4.4.3 firmware, but as far as I can understand, the full RUU should've had the required files, and if not, then flashing the firmware should've sorted it out.
The RUU I used is the rooted 4.4.4 - 2.12.1700.1 one as per graffixnyc's page from this thread: http://forum.xda-developers.com/showthread.php?t=2708589
Current HBOOT is 3.18.0.0000
Radio is 1.14.21331931.LA02_2G (So it _does_ look like it's "downgraded" it)
OS 2.12.1700.1
The actual phone is (I believe) an ex-Hong Kong GSM version which I WWE'd.
Click to expand...
Click to collapse
I googled your stuff, and for GPE, your firmware is fine.
The radio thing, I'm not sure about.
Sorry, I was just trying trying help a bit.
I'm sure that someone more familiar with GPE will help.
Good luck buddy!
xunholyx said:
I googled your stuff, and for GPE, your firmware is fine.
The radio thing, I'm not sure about.
Sorry, I was just trying trying help a bit.
I'm sure that someone more familiar with GPE will help.
Good luck buddy!
Click to expand...
Click to collapse
Thanks for trying!
I just tried reflashing the RUU, and noticed this in the log:
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-2,0
(bootloader) [RUU]WP,sbl1-2,100
(bootloader) ...... Successful
(bootloader) current_image_number=5
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=6
So it looks like some of the SBL (Boot Loader?) isn't getting flashed correctly perhaps.
knightnz said:
Thanks for trying!
I just tried reflashing the RUU, and noticed this in the log:
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-2,0
(bootloader) [RUU]WP,sbl1-2,100
(bootloader) ...... Successful
(bootloader) current_image_number=5
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=6
So it looks like some of the SBL (Boot Loader?) isn't getting flashed correctly perhaps.
Click to expand...
Click to collapse
@KJ @redpoint73? I don't know. They do. Don't try to PM them or anything. They will get notified by the mention, and will be better able to help you.
I've never used RUUs. Not that I won't eventually, I've just had no need to yet.
xunholyx said:
@KJ @redpoint73? I don't know. They do. Don't try to PM them or anything. They will get notified by the mention, and will be better able to help you.
I've never used RUUs. Not that I won't eventually, I've just had no need to yet.
Click to expand...
Click to collapse
Reflashed the Sense 4.4.4 firmware (3.28.401.7) & TWRP, then restored my backup and all is as it was, so at least I haven't cooked my SIM or the radio, either I'm missing something, or GPE doesn't like something on this phone.
Will have another try later!
knightnz said:
Reflashed the Sense 4.4.4 firmware (3.28.401.7) & TWRP, then restored my backup and all is as it was, so at least I haven't cooked my SIM or the radio, either I'm missing something, or GPE doesn't like something on this phone.
Will have another try later!
Click to expand...
Click to collapse
So basically, you should have just followed the advice I gave you in the first place?
Cool. Glad you fixed your sh*t.
Not so happy about the help I wasted my time giving you when you could have just listened to me in the first place.
No hard feelings though. Really.
Next time though.................(and I feel there will be a next time)
xunholyx said:
So basically, you should have just followed the advice I gave you in the first place?
Cool. Glad you fixed your sh*t.
Not so happy about the help I wasted my time giving you when you could have just listened to me in the first place.
No hard feelings though. Really.
Next time though.................(and I feel there will be a next time)
Click to expand...
Click to collapse
WTF? I needed to get the phone going for a bit so I could actually use it for something important until I've got some spare time to try this again. (Which given the time I spent trying to get it to work today probably won't be until the weekend)
"Go back to a Sense ROM" does not get cellular working in GPE which was what I was trying to do.
Calm down.
knightnz said:
WTF? I needed to get the phone going for a bit so I could actually use it for something important until I've got some spare time to try this again. (Which given the time I spent trying to get it to work today probably won't be until the weekend)
"Go back to a Sense ROM" does not get cellular working in GPE which was what I was trying to do.
Calm down.
Click to expand...
Click to collapse
Post #7.
It should have sent you down the road to do some research. All the answers were in that link.
Don't expect me to spoon feed you, because I won't.
Visit my links.
Read them.
Profit.
And if you want to Mod your sh*t, be prepared for problems.
And be prepared to at least try to solve problems on your own.
And by that, I mean Google is your friend.
Seriously.
Anyways, I'm happy that you got up and running.
No joke.
Yeah, I guess a couple of hours of Googling, flashing different radios and different firmwares via different methods really doesn't count as trying to fix anything myself.
Given the amount of different hardware I've modified over the years, (incl making goldcards & JTAG flashing), I"m fully aware that I should expect problems, hence why I only did this knowing full well that I can relatively easily revert back to the working system (which is why I had the backups in the first place).
Most people seem to have the conversion working merely by flashing the RUU (as I had researched) - the fact that for whatever reason it didn't work for me is what I was trying to resolve, when I ran out of time to try to get it to work for now, I put it back how it was. If anyone is able to suggest a reason as to why this particular issue has arisen, or when I have some time, I'll give it another crack.
If it doesn't work, then so be it, I thought it might've been interesting to play with.
Sorry to have inconvenienced you.
knightnz said:
Yeah, I guess a couple of hours of Googling, flashing different radios and different firmwares via different methods really doesn't count as trying to fix anything myself.
Click to expand...
Click to collapse
A quote or a mention with an @ would be the best way to reply and get me to notice via a notification.
And I'm sorry. If I would have looked at your stats before I replied, I would not have said that.
It's very common on this forum to not search for answers.
Truely, I'm sorry. No joke.
And I wish I could help you. But I'm not sure I can.
I'll try to get an answer for you, but I don't have one now.
I'll give it a shot. Sorry for being a dink.
You may not realize (but you probably do) how repetitive and constant the same issues are.
Sorry for the offensive tone.
And good luck to you!
EDIT: your edit makes me feel worse.
Like I said, This forum is full of noobs unwilling to take the time.
I can see from your stats and edit that you are not one of them.
Best of luck finding an answer, and I'll keep trying to find a solution as well.\
Cheers!
Also, no inconvenience happened. A few more beers happened.
knightnz said:
So it looks like some of the SBL (Boot Loader?) isn't getting flashed correctly perhaps.
Click to expand...
Click to collapse
Yes, SBL are the hboot modules (3 total). It looks like they didn't flash, but I would have tried the RUU twice, as for some reason the firmware needs to be flashed twice to install everything.
With s-off and SuperCID, I don't see any reason why the SBL modules would not have flashed.
But I see you have since tried a different method of attacking the issue.
redpoint73 said:
Yes, SBL are the hboot modules (3 total). It looks like they didn't flash, but I would have tried the RUU twice, as for some reason the firmware needs to be flashed twice to install everything.
With s-off and SuperCID, I don't see any reason why the SBL modules would not have flashed.
But I see you have since tried a different method of attacking the issue.
Click to expand...
Click to collapse
Just tried reflashing the RUU now, both times it's bypassed flashing the SBL modules.
However - Apparently this is "Normal" - there's 3 modules, and it'll pick whichever one matches the device.
So, back to some sort of hardware incompatibility perhaps, as it looks like the RUU is flashing all A-OK going by this.
Here's the getvar results;
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT463WM01186
(bootloader) imei: (removed)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
From what I can see, all hardware models starting with 0P6B should work fine with GPE, so looks like that's not the issue either.
Have tried SuperCID and GOOGL001 at various stages just in case, made no difference.
Found a post from someone else with the same issue, no word if it was resolved: http://forum.xda-developers.com/showpost.php?p=53943011
Will experiment with some more radios.
knightnz said:
However - Apparently this is "Normal" - there's 3 modules, and it'll pick whichever one matches the device.
Click to expand...
Click to collapse
That is not correct. They are all pieces of the whole. All 3 need to be present for hboot to work, otherwise a brick will occur (I've seen it happen). It could be that if your hboot has already been updated, the flashing is skipped.
I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?
Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there
unifex_ said:
I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?
Click to expand...
Click to collapse
Do as EddyOS says, he will guide you on the best which version to downgrade to (if your looking to do that). Honestly I didnt have any issues with Lollipop, its all good.
my suggestion of the easiest way to totally wipe up your internal memory is to unlock bootloader (if you've already unlocked it, then relock and unlock again), doing that will totally wipe your internal memory, as for ext. sd card, you can just format that.
Flashing original stock rom is done by an RUU.
EddyOS said:
Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there
Click to expand...
Click to collapse
Thanks Eddy, I appreciate the help.
I attach an image of the fastboot output.
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box
EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box
Click to expand...
Click to collapse
Great, that sounds uncomplicated enough. My bootloader is locked, as far as I know, at least I never did anything to unlock it. So I should be good to go.
One question though. At the moment, the phone is unlocked as far as SIM is concerned. I mean that although the CID is from T-Mobile Germany, I'm using O2 as the service provider. Will that RUU keep it that way, or it will make the phone locked towards T-Mobile SIM cards?
Thanks a lot.
It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't
EddyOS said:
It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't
Click to expand...
Click to collapse
In case it would, what would I have to do to unlock it? I don't have any T-Mobile SIM cards around here after all.
Buy a code, like you did last time
EddyOS said:
Buy a code, like you did last time
Click to expand...
Click to collapse
I did not buy any code, I bought a phone. That's how it came from the shop - SIM-unlocked. I had no idea it had the T-Mobile anything in it until I started looking around this forum and someone asked me about my CID.
If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU
EddyOS said:
If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU
Click to expand...
Click to collapse
Great, thanks! I'll let you know how it went.
OK, finally got the time to do it, but unfortunately, the RUU that I downloaded
EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
Click to expand...
Click to collapse
did not work, I attach the screenshot with the error. Any ideas? The error was the same regardless of whether the phone was connected to the PC.
Yeah, it appears that RUU is corrupt
EddyOS said:
Yeah, it appears that RUU is corrupt
Click to expand...
Click to collapse
That's a pity. Do you know where can one find a proper RUU? I looked at the htcdev.com download section, they list the software I need, 4.19.111.2, but the download link brings me simply to the htc.de, where nothing can be downloaded, it's just their regular advertising site.
I also found a zip file with the 4.16.111.2 firmware on a German forum (basically, from a link in the xda thread with RUU and OTA collection), but to be honest, I'm not sure what to do with the bunch of img files.
The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted
EddyOS said:
The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted
Click to expand...
Click to collapse
How about the files from that site (German, though). I found that link on the xda thread for RUU collection.
http://www.handy-faq.de/forum/htc_o...ne_m8_firmwaresammlung_ruus_otas_backups.html
They have a list of various files, for 4.19.11.2 they have nandroid backups and signed firmware, but not a RUU.
Or could you suggest a well working ROM?
You could flash the backup, then the firmware to restore stock recovery and it should work
EddyOS said:
You could flash the backup, then the firmware to restore stock recovery and it should work
Click to expand...
Click to collapse
Could you help me with mine as well
from fastboot
(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: 4.20.631.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH445WM0----
(bootloader) imei: ----------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.177s
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
So, I had a marshmallow update on my phone, and later i converted into GPE, but didn't like it. Went back to Sense, but it just doesn't feel as good as before. One day, the battery died, and when i tried turning it on, it would give me all sorts of errors. This never happened while i was on marshmallow before conversion to GPE. Had to reset it from the recovery. I think it hasn't returned to Sense properly.
As i am S-Off, i was thinking of flashing it with a RUU which is compatible with my device. Please suggest me which is compatible.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.21450002
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.708.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------------------
(bootloader) imei: --------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: 11111111
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s
Based on your MID, looks like you're on a GSM M8? I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
I have read here that flashing carrier RUU can brick the device radio for good. So, this is why I wanted to confirm.
cytherian said:
I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
Click to expand...
Click to collapse
HTC does not post the RUU for his version on HTC Dev.com (many versions are not posted there)
OP's version doesn't have a carrier forum sub-section.
---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------
xexux said:
(bootloader) version-main: 6.16.708.1
Click to expand...
Click to collapse
I don't know if there is an RUU for this version number.
One alternative, is to restore the TWRP backup 6.16.708.1 from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 09:42 AM ---------- Previous post was at 09:38 AM ----------
xexux said:
Went back to Sense, but it just doesn't feel as good as before.
I think it hasn't returned to Sense properly.
Click to expand...
Click to collapse
How exactly did you go back to Sense?
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
xexux said:
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Good to hear that it worked out and thanks for posting. :good:
cytherian said:
Good to hear that it worked out and thanks for posting. :good:
Click to expand...
Click to collapse
This is how I got Sense back, and after that, I started experiencing bugs with M8 as explained in my first post.
xexux said:
So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
redpoint73 said:
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
Click to expand...
Click to collapse
I restored it with the latest TWRP backup for my model. About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
xexux said:
I restored it with the latest TWRP backup for my model.
Click to expand...
Click to collapse
What version number exactly? Perhaps you still have the files on your computer, and can look?
I've seen a number of times, folks say and think they restored the right version for their model, and once we ask for version numbers, we see they actually got it wrong.
xexux said:
About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Click to expand...
Click to collapse
I can see it too. But doyou actually remember manually download and flash the firmware in RUU mode?
Did you convert to GPE using the RUU?
xexux said:
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
Click to expand...
Click to collapse
It's possible. But flashing another region's RUU will also change the radio baseband, and therefore changes the specific bands supported. It may have undesirable results (not support the 3G or LTE band or bands used by your local carrier).
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Bukss said:
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Click to expand...
Click to collapse
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
c:\miniadb_m7>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 99000499834418
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
Abnova said:
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B12000
Click to expand...
Click to collapse
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
redpoint73 said:
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
Click to expand...
Click to collapse
Yeah I realised how big of a mess I was in when I got it back. Anyway
1.)On further investigation it seems like the the phone is in a wierd RUU mode. So it still can interface with the laptop through fastboot. Like I said earlier, trying to reboot to bootloader brings you to the same black screen with the silver Logo (see attached). When the phone is plugged in to the laptop or switches to the HTC silver Logo screen however when it's unplugged, it goes to a wierd bootloader like screen but black and only has the option for RUU. ( See attached)
2.) I took it to them to replace the battery because . The phone would switch off even at 100% battery. It only worked when it stayed plugged in , like a PC. I'm guessing the repair guys saw I had modified the software (I was running Dirty Unicorns, Android 7.1.2, Latest TWRP with a relocked Bootloader, S-Off) and had thought the problem actually had to do with the software. I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Anyway I hope this information helps. Thanks for your help.
Abnova said:
I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Click to expand...
Click to collapse
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Abnova said:
1.)On further investigation it seems like the the phone is in a wierd RUU mode.
Click to expand...
Click to collapse
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Thanks for your contribution, will definitely try tomorrow
redpoint73 said:
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Click to expand...
Click to collapse
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Abnova said:
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Click to expand...
Click to collapse
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
redpoint73 said:
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
Click to expand...
Click to collapse
I tried that, it would flash then refuse to reboot to the recovery. I've tried so many things but none of them worked. My only hope is if someone edited the Android.txt file inside the Rom Zip so that the model ID is the same as that of my corrupt phone. That way it'll flash and hopefully fix it. I've tried myself but everytime I tried to edit it says the zip/archive is corrupt on WinRAR. I don't know whether it's a problem with my laptop or if it's a complication related to the rom.zip. I've downloaded it again but it still does the same thing. So basically I'm stuck because there is no way I can change the MID. This probably means the phone is bricked.
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Jabbah said:
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader menu?
Jabbah said:
have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Click to expand...
Click to collapse
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
redpoint73 said:
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
Click to expand...
Click to collapse
Tried to flash a stock UK rom.
I have no idea how to use that command sorry.
os is 6.12.61.4
(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: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Jabbah said:
Tried to flash a stock UK rom.
Click to expand...
Click to collapse
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
redpoint73 said:
RUU, firmware.zip, or something else?
What is the version number and file name?
Click to expand...
Click to collapse
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
redpoint73 said:
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
Click to expand...
Click to collapse
Thanks for the replies, ive actually gotten somewhere today, Ive installed twrp, and installed the latest Lineage ROM which booted fine .
But.... Not detecting sim card
Always something haha
Another option (especially now that you have unlocked the bootloader, and installed TWRP), is restore stock TWRP backup 6.12.61.4 from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
No need to do Step 3, nor Steps 10 or after (only relevant to get OTA updates - which no longer applies to this device). Just reboot.
Jabbah said:
Thanks for the replies
Click to expand...
Click to collapse
There is a button for that.
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
David.
Jabbah said:
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
Click to expand...
Click to collapse
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
redpoint73 said:
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
Click to expand...
Click to collapse
Got around the sim not detected issue, the phone was simlocked to orange, it just didnt pop up with the enter unlock code dialogue.
Ill try a few see what they are like
Thanks again for your help.
Jabbah said:
Got around the sim not detected issue, the phone was simlocked to orange.
Click to expand...
Click to collapse
Understood. I would not have expected the "SIM not detected" error in that case. So thanks for clarifying.
Jabbah said:
it just didnt pop up with the enter unlock code dialogue.
Click to expand...
Click to collapse
Stock (Sense) ROM is needed to unlock SIM. Which you either figured out, or stumbled upon the solution by luck! :good: