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.
Related
What is the best way to get the firmware update without losing root and have to do all those things all over again? I know SunShine, but I don't think my parents would allow it.
Billchen0014 said:
What is the best way to get the firmware update without losing root and have to do all those things all over again? I know SunShine, but I don't think my parents would allow it.
Click to expand...
Click to collapse
return to stock and wait for the official OTA
stathis95194 said:
return to stock and wait for the official OTA
Click to expand...
Click to collapse
it does mean i will lose root and will have to get root again, right? and I don't know how to get back to the stock rom either... bummer
Billchen0014 said:
it does mean i will lose root and will have to get root again, right? and I don't know how to get back to the stock rom either... bummer
Click to expand...
Click to collapse
You don't lose root. You can restore a stock nandroid backup for your cid and the stock recovery and be prepared for the OTA.
You can find stock backups and recoveries here:
http://forum.xda-developers.com/showthread.php?t=2701376
stathis95194 said:
return to stock and wait for the official OTA
Click to expand...
Click to collapse
stathis95194 said:
You don't lose root. You can restore a stock nandroid backup for your cid and the stock recovery and be prepared for the OTA.
You can find stock backups and recoveries here:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
i can't find one for this device...
here's the getvar outputs
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.012s
Billchen0014 said:
i can't find one for this device...
here's the getvar outputs
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.012s
Click to expand...
Click to collapse
Of course there is...check the link above again.
CID VODAP021
1.12.710.17 - CWM Philz touch Thanks to rolphez
STOCK RECOVERY 1.12.710.17
stathis95194 said:
Of course there is...check the link above again.
CID VODAP021
1.12.710.17 - CWM Philz touch Thanks to rolphez
STOCK RECOVERY 1.12.710.17
Click to expand...
Click to collapse
I hate how HTC handles these things... Jumping from a Nexus this is like a nightmare
So The file you suggested is just a ROM right? and the recovery has nothing to do with CIDs? So any recovery with the same version number will do?
First file is the stock ROM for your cid.
Second is the stock recovery for your CID. After you flash those 2 you will be ready to receive an OTA when your carrier release it.
Billchen0014 said:
it does mean i will lose root and will have to get root again, right? and I don't know how to get back to the stock rom either... bummer
Click to expand...
Click to collapse
Based on your post count, device history, and amount of time you've been on XDA, I find it surprising you don't know how, or can't figure out how to return to the stock ROM.
Not trying to be mean, but restoring a nandroid and stock recovery are not difficult things, basic concepts and steps, really. Maybe just take a little time to wrap your mind around the concepts, and you might feel more comfortable about them. If these things are over your head, you certainly shouldn't mess with S-off and flashing firmware.
And re-rooting after an OTA should take about 5 or 10 minutes, so I don't see much reason for concern. Just re-install custom recovery and flash SU/SuperSU or a rooted ROM.
redpoint73 said:
Based on your post count, device history, and amount of time you've been on XDA, I find it surprising you don't know how, or can't figure out how to return to the stock ROM.
Not trying to be mean, but restoring a nandroid and stock recovery are not difficult things, basic concepts and steps, really. Maybe just take a little time to wrap your mind around the concepts, and you might feel more comfortable about them. If these things are over your head, you certainly shouldn't mess with S-off and flashing firmware.
And re-rooting after an OTA should take about 5 or 10 minutes, so I don't see much reason for concern. Just re-install custom recovery and flash SU/SuperSU or a rooted ROM.
Click to expand...
Click to collapse
This is my first HTC device and the stock Rom nandroid for my Cid isn't twrp compatible and cwm is doing what I already it to do. That's problem one, I have never seen such messy system to return to stock, CIDs and all this rubbish. And I swear for all these years I've never had to flash a firmware in order to flash a Rom, and heck, even pay to have full rights over my device (sunshine) I'd say HTC is the least friendly phone I've used by far when it comes to flashing custom roms
Billchen0014 said:
This is my first HTC device and the stock Rom nandroid for my Cid isn't twrp compatible and cwm is doing what I already it to do. That's problem one, I have never seen such messy system to return to stock, CIDs and all this rubbish. And I swear for all these years I've never had to flash a firmware in order to flash a Rom, and heck, even pay to have full rights over my device (sunshine) I'd say HTC is the least friendly phone I've used by far when it comes to flashing custom roms
Click to expand...
Click to collapse
Nexus is made for easy unlocking etc.
HTC is reasonably good in this regard, IMO, having dealt with some 30 phones over 3 years for testing my apps.
HTC has bootloader unlock program. LG has nothing like that (Although allegedly considering it). I hate my G2 for that reason.
I've never directly dealt with Samsungs' KNOX, but that creates major headaches too.
We are lucky to have ANY S-Off solution.
We are also lucky to have so much enthusiast & ROM dev interest in the M8. Some of the forums here on XDA are barren.
Phew, used firewater and flashed the new firmware. painless for the most part after SuperCID and thanks XDA again for this wonderful crowd. proud to be part of this great community. this is going to be an exiting weekend!
cheers
Billchen0014 said:
Phew, used firewater and flashed the new firmware.
Click to expand...
Click to collapse
You've spent all this time complaining about sunshine, when you could have just used firewater??? Why didn't you try it in the first place?
---------- Post added at 09:40 AM ---------- Previous post was at 09:33 AM ----------
Billchen0014 said:
And I swear for all these years I've never had to flash a firmware in order to flash a Rom, and heck, even pay to have full rights over my device (sunshine) I'd say HTC is the least friendly phone I've used by far when it comes to flashing custom roms
Click to expand...
Click to collapse
Pay for sunshine is the developer's choice, and has nothing to do with HTC. For all we know, developers can choose to charge money for any root solution on any device, if they want.
Complaining is not going to accomplish anything except piss off folks who enjoy this device (which is most folks here). Aside from the sunshine fee, all the concepts and steps that you seem to have trouble with are very basic. If you can't understand and accomplish them, you shouldn't be rooting your phone in the first place.
HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(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: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
fgarcia10 said:
HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(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: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Have you flashed a custom recovery on the device? If yes, just try to restore a nandroid back from @Mr Hofs thread and your phone will be fine
Problem is, I don't think there is any nandroid backups available for his device LRA__001. First time I've seen that CID mentioned. Going by MID doesn't help much either, I think the Verizon has the same MID. Going by the "product: m8_wlv" it also indicates Verizon. I do see that he's on AT&T on his profile though but...
Being stuck on bootloader screen for 10minutes or more won't be surprising at all if he flashed a 2.xx.xxx.x firmware based custom ROM instead of a 1.xx.xxx.x version. Need to upgrade firmware in order to do that.
You don't happen to recall what version software your device ran?
Hi, I had the 2.7 TWRP recovery but found the 2.8.0.6 works better. I was able to flash PA ROM and it is working now. Plus now is rooted and S-off and super CID.
The phone has no branding and bought from amazon as unlock from factory. But is funny you mention Verizon has similar IDs because when I plug the phone to HTC sync the first splash screen shows Verizon wireless assistant and then go to the normal HTC one.
I tried the latest HD ROM and it was force closing a lot so I think the firmware is 1.... Something. I want to upgrade but don't know which one to get. Maybe I should look on the Verizon forum, thanks for letting me know that.
I spoke with developer support at HTC and they told me they will help restore to stock and escalated the call. I will let you know if they do help.
Thanks for the replies.
fgarcia10 said:
Hi, I had the 2.7 TWRP recovery but found the 2.8.0.6 works better. I was able to flash PA ROM and it is working now. Plus now is rooted and S-off and super CID.
The phone has no branding and bought from amazon as unlock from factory. But is funny you mention Verizon has similar IDs because when I plug the phone to HTC sync the first splash screen shows Verizon wireless assistant and then go to the normal HTC one.
I tried the latest HD ROM and it was force closing a lot so I think the firmware is 1.... Something. I want to upgrade but don't know which one to get. Maybe I should look on the Verizon forum, thanks for letting me know that.
I spoke with developer support at HTC and they told me they will help restore to stock and escalated the call. I will let you know if they do help.
Thanks for the replies.
Click to expand...
Click to collapse
Honestly if its that much of a hassle, you should stick with something safe, Change the MID and CID to a Dev Edition/Europe, to do a full convert and you wont have to worry about the LRA_001. If you do those 2 steps the the OTA will be automatic as follows.
Else just flash a custom recovery, wipe data/cache and so and restore with one of the TWRP backups posted around here and you'll be good to go :good:
Cool I will try that. I did not know that.
fgarcia10 said:
Cool I will try that. I did not know that.
Click to expand...
Click to collapse
Don't forget though, best steps as follow, change MID, CID, restore via TWRP backup. If youre in Europe then change the MID to EUR, but the CID change it to super CID. Youve gotten past the hardest part which is the SOFF so everything is a breeze from there on out.
You won't lose your internal data if you do any of the following steps but dumping them on your SD card would be safe too.
I had an SG manufactured one, and the OTA came out pretty weird, was an unbranded one too. changed it to Dev/Unlocked MID and the super CID, downloaded the B_US002 TWRP dump thats posted here and restored that. Might want to download the OTA too aswell would save massive time after the first 159MB ota.
Awesome. Thanks!
was any one here ever able to get things working?
i am on LRA__001 and got my radio to stop working, no phone signals
contacted HTC dev and they provided me a zip, flashing that didn't help much, still no signals and can't boot into stock recovery.
seems like i've flashed the wrong hboot or something that's causing everything to be flashed on wrong partition addresses.
any help ?
fgarcia10 said:
HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(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: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
hey
were you able to get it working ?
do you still have that phone?
i need some help
genious_t said:
hey
were you able to get it working ?
do you still have that phone?
i need some help
Click to expand...
Click to collapse
This isn't the same issue as the OP. You flashed the wrong firmware which is much more serious. This thread isn't relevant to your issue, in addition to being over a year old (which also most likely won't help your issue).
redpoint73 said:
This isn't the same issue as the OP. You flashed the wrong firmware which is much more serious. This thread isn't relevant to your issue, in addition to being over a year old (which also most likely won't help your issue).
Click to expand...
Click to collapse
I am just trying to trace ppl with the same variant so I can request them to dump couple of partitions for me. and there is no relevant thread for this particular variant, some says it s bluegrass some says its verizon variant, but according to HTCDev its actually rural area variant.
genious_t said:
I am just trying to trace ppl with the same variant so I can request them to dump couple of partitions for me. and there is no relevant thread for this particular variant, some says it s bluegrass some says its verizon variant, but according to HTCDev its actually rural area variant.
Click to expand...
Click to collapse
The LRA version is the LRA version. there's no question there. Its based on Verizon, but its not Verizon.
Sounds like you are trying to make up solutions. What you need is LRA firmware or RUU (RUU may not exist).
redpoint73 said:
The LRA version is the LRA version. there's no question there. Its based on Verizon, but its not Verizon.
Sounds like you are trying to make up solutions. What you need is LRA firmware or RUU (RUU may not exist).
Click to expand...
Click to collapse
i've got complete RUU from HTCDev to flash via hboot, did flash that but lost the IMEI and baseband version under settings > about, however the getvar all is still showing that information. so just trying to figure out what went wrong. either something is missing in what they have provided. or the hboot version is mismatching.
read bout the boot process and got to know that hboot reads IMEI and baseband while booting up and holds into some shared memory variables which later read by kernel.
just trying to figure out things and also looking for somebody who can provide dumps so i can try flashing them.
genious_t said:
i've got complete RUU from HTCDev to flash via hboot, did flash that but lost the IMEI and baseband version under settings > about, however the getvar all is still showing that information. so just trying to figure out what went wrong. either something is missing in what they have provided. or the hboot version is mismatching.
Click to expand...
Click to collapse
You flashed a hacked Verizon RUU. Its not the LRA RUU, and its also not an official RUU.
redpoint73 said:
You flashed a hacked Verizon RUU. Its not the LRA RUU, and its also not an official RUU.
Click to expand...
Click to collapse
No I explained them my case and they asked to couple of days time and then they provided a zip file to flash via hboot. They claimed that they have prepared this file especially for me. I flashed that file. It was 5.0.1 with almost all the images.
One thing that I doubt is that the hboot is not updated since the android-info.txt says hbootpreupdate=12 and my getvar says 11 so just wondering whether it was updated or not.
Also I dumped mmcblk0p3 (board-info) and I can see my IMEI there too.
Just don't know where to nock my head
genious_t said:
hey
were you able to get it working ?
do you still have that phone?
i need some help
Click to expand...
Click to collapse
I did get it to work again, HTC help me to get it back to stock. I still have the phone. They send me the files to restore it.
genious_t said:
No I explained them my case and they asked to couple of days time and then they provided a zip file to flash via hboot. They claimed that they have prepared this file especially for me. I flashed that file. It was 5.0.1 with almost all the images.
One thing that I doubt is that the hboot is not updated since the android-info.txt says hbootpreupdate=12 and my getvar says 11 so just wondering whether it was updated or not.
Also I dumped mmcblk0p3 (board-info) and I can see my IMEI there too.
Just don't know where to nock my head
Click to expand...
Click to collapse
they send me the wrong files a couple of times. But they did get me the right one at the end. it seems you have the same problem I did. I still the hboot file and the system image. The hboot zip should be installed on download mode and the system image should be rename to OP6BIMG.zip and put in the sd card and re-start the phone in bootloader and let the zip install itself. It takes a long time but it worked. I have the files in my google drive I don't mind sharing it.
fgarcia10 said:
they send me the wrong files a couple of times. But they did get me the right one at the end. it seems you have the same problem I did. I still the hboot file and the system image. The hboot zip should be installed on download mode and the system image should be rename to OP6BIMG.zip and put in the sd card and re-start the phone in bootloader and let the zip install itself. It takes a long time but it worked. I have the files in my google drive I don't mind sharing it.
Click to expand...
Click to collapse
In my case they gave up, the guy said it can still be fixed but I don't know what to do.
Would you be able to share the stuff that worked for you ?
genious_t said:
In my case they gave up, the guy said it can still be fixed but I don't know what to do.
Would you be able to share the stuff that worked for you ?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0Bw_sCYzL1RITbGkzRExWTmU1d1U/view?usp=sharing
https://drive.google.com/file/d/0Bw_sCYzL1RITN0ttSVBZZ3VUYkk/view?usp=sharing
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.
Hello,
this is my first post here, and i'm sorry for my maybe bad english. I'm from Germany.
I have some Problems with my M8 and i try to depict it to you.
Hello there,
I have kind of a strange problem . I wanted to flash my HTC on a Ungebrandetete version .
I have S - OFF and the bootloader is unloked .
I flashed the following RUU from the collection : RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
after the flash process the HTC restarts , it optimizes 262 Apps , then comes quite normal the establishment of smartphones . and I can use the phone .
Once I restart the Phone I can see the HTC ONE logo and hear the boot sound and then nothing happens . If I put it back to factory reset in the bootloader , the phone starts again , optimizes the 262 apps and re- establishing the Phones .
I'm really on despair : here is an excerpt from my " GETVAR all "
Code:
(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-OFF
(bootloader) serialno: XXXXX
(bootloader) imei: XXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
EDIT:
I just flashed the CM13.0 Nightly and that works wonderfully i can restart the phone and it starts normaly. But the last snapshoot form cm12.1, Viper ROM, GPE Rom starts only 1 time after flashing and then nothing.
So my guess is that it is up to the RUU , not fit ? I thought with S -OFF can I flash anything i want
greetings
Kryptik
no one any idea?
Kryptik86 said:
no one any idea?
Click to expand...
Click to collapse
Can't see what can be causing the issue, unfortunately. But I can offer up a few comments to your top post:
Kryptik86 said:
I thought with S -OFF can I flash anything i want
Click to expand...
Click to collapse
Not quite "anything". Yes, on past HTC devices s-off meant that all restrictions were lifted. But on this device, you still need to match CID and MID for signed RUUs, firmware, etc.
Kryptik86 said:
So my guess is that it is up to the RUU , not fit ?
Click to expand...
Click to collapse
Did the RUU run to completion without any error messages?
If so, the issue is not the right RUU.
redpoint73 said:
Can't see what can be causing the issue, unfortunately. But I can offer up a few comments to your top post:
Not quite "anything". Yes, on past HTC devices s-off meant that all restrictions were lifted. But on this device, you still need to match CID and MID for signed RUUs, firmware, etc.
Did the RUU run to completion without any error messages?
If so, the issue is not the right RUU.
Click to expand...
Click to collapse
The RUU ran to the end without error . The idea with the MID sounds ineressant , have already read how to change them . But if I have understood correctly you have to ROOT/ superuser rights? And the phone is in debug mode?
Kryptik86 said:
The RUU ran to the end without error . The idea with the MID sounds ineressant , have already read how to change them . But if I have understood correctly you have to ROOT/ superuser rights? And the phone is in debug mode?
Click to expand...
Click to collapse
Yes, you need to have s-off (which you do), root and in debug mode (as you will be using adb to issue the commands) to change MID.
But this is to run a different CID/MIDs RUU (different from your present CID, MID). Is that what you are talking about doing?
Note that changing the MID may brick the device, if you screw it up. So proceed with extreme caution, and follow instructions carefully (and only instructions for the M8). And you should note the existing MID, in case you need to change it back.
Also, flashing another CIDs RUU may change the network band support on the phone, as it flashes a different radio baseband.
What are you thinking of doing, exactly?
so i'm now @work i think i try it tomorow.
In first i will check my MID, and try to find out whats maybe wrong with it - or not.
i did CID change 2 or three times to super CID and to google CID and back to HTC__102 thats not a prob for me.
But in first i CHECK my MID and post it here, maybe someone know whats the Problem with the phone and the ROM's
i'm just wondering that Cyagenmod 13_nightly works without the 2nd boot problem.
I'm going crazy, thats my 2nd m8.
with my first M8 (main phone) i tryed nearly all custom roms, and now I'm on GPE 6.0. without any problems.
hope you can understand what i'm trying to say
greetings
kryptik
Kryptik86 said:
so i'm now @work i think i try it tomorow.
In first i will check my MID, and try to find out whats maybe wrong with it - or not.
But in first i CHECK my MID and post it here, maybe someone know whats the Problem with the phone and the ROM's
Click to expand...
Click to collapse
I think you are making up problems that don't exist (MID). Or at least thinking of "solutions" with no basis.
If the MID was wrong, the RUU would have failed (same as if the CID was wrong).
And the MID is correct, based on your getvar output posted in the top post (modelid).
MID won't affect custom ROMs.
Don't mess with the MID, for the reasons stated previously. I don't see how it will help you; and if you make a mistake you will brick.
yes, i thinking like you, there is no prob. with my mid.
so the searching going on
I would try the RUU again, maybe something didn't install correctly the first time.
redpoint73 said:
I would try the RUU again, maybe something didn't install correctly the first time.
Click to expand...
Click to collapse
i have tryed to Install this over 15 times. every time the same "error" after install the system starting normal.
after reboot nothing happen on the "HTC ONE" logo, only whey i do a factory reset, then it starts normal again, till i restart the phone next time.
yesterday i try to install a MIUI rom from XDA this one
and it works. so my thinking is, that is something with 5.X ROM's because it seems that only this not working.
MIUI = 4.4.4 = Work
CM12.1, VIPER ROM, STOCK, GPE 5.1 = 5.X = Don't work :silly: :crying:
CM 13 = 6.0 = Work
what do u thinking?
Kryptik86 said:
what do u thinking?
Click to expand...
Click to collapse
Don't know, its pretty puzzling. Especially since you have the error on full stock (RUU) and also on CM12.1.
I'm out of ideas, short of changing your CID/MID to flash another versions RUU (which seems pretty drastic).
push
All of a sudden my phone hang up.
I booted into the stock recovery - factory reseted and everything and then this happened:
The optimizing started like when I made a wipe and data reset through recovery. xxx out of 164
but as soon as it finished I got the same problem as before:
"Android is starting.. starting apps"
and there it gets stuck
So I unlocked the phone, installed custom recovery and ROM, tried 3 different ones but still get the same issue. What might be the problem?! what can I do... I really dont know what else to do... :/
Do fastboot getvar all, and post the results (delete IMEI and serial number).
What ROMs did you try (and what version numbers)?
redpoint73 said:
Do fastboot getvar all, and post the results (delete IMEI and serial number).
What ROMs did you try (and what version numbers)?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT444******
(bootloader) imei: 358718**********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.018s
I tried the
Venom Viper (which is my favorite on the HTCs)
Android Revolution HD
Maximus HD
all the latest versions!
TWRP have the latest v3 installed too!
Did you wipe data, cache and Dalvik (this is the "default" wipe option in TWRP) before flashing the ROMs?
If so, I can't see anything that is obviously wrong. You might consider running the 6.12.1540 RUU to start from a completely "clean" baseline image, and see if the problem persists. Be aware, RUU will wipe the phone.
redpoint73 said:
Did you wipe data, cache and Dalvik (this is the "default" wipe option in TWRP) before flashing the ROMs?
If so, I can't see anything that is obviously wrong. You might consider running the 6.12.1540 RUU to start from a completely "clean" baseline image, and see if the problem persists. Be aware, RUU will wipe the phone.
Click to expand...
Click to collapse
I have done that 100 times... this crap doesnt boot at all... flashed the stock RUU multiple times! and of course multiple times clean the cache and internal data etc etc... it just wont start... :/
the only thing I didnt do is unlocking the CID... but I dont think this is that important?!
greek_lover_69 said:
I have done that 100 times... this crap doesnt boot at all... flashed the stock RUU multiple times! and of course multiple times clean the cache and internal data etc etc... it just wont start... :/
Click to expand...
Click to collapse
The response makes it sound like you are mad for me asking?
We can't know what you did, if you don't tell us. We aren't mind readers. And what may seem like an obvious thing to you, is a common mistake by many others.
Additionally, the simple answer is often (while not always) the correct one.
greek_lover_69 said:
the only thing I didnt do is unlocking the CID... but I dont think this is that important?!
Click to expand...
Click to collapse
You mean changing the CID? No, I don't see why that would make a difference.
If you've successfully installed the RUU, and the issue persists, I tend to believe this is a random hardware failure (such as emmc going bad). This theory would also explain why this happened "all of a sudden".
redpoint73 said:
The response makes it sound like you are mad for me asking?
We can't know what you did, if you don't tell us. We aren't mind readers. And what may seem like an obvious thing to you, is a common mistake by many others.
Additionally, the simple answer is often (while not always) the correct one.
You mean changing the CID? No, I don't see why that would make a difference.
If you've successfully installed the RUU, and the issue persists, I tend to believe this is a random hardware failure (such as emmc going bad). This theory would also explain why this happened "all of a sudden".
Click to expand...
Click to collapse
no no sorry.. why should I be mad at you.. you are just trying to help... I^m mad at my PHONE!
i^m guessing hardware failure too... can explain it else..
thanks! will have to sent it back.
I bought it from china.. maybe it had a problem and was fixed or something..
greek_lover_69 said:
no no sorry.. why should I be mad at you.. you are just trying to help... I^m mad at my PHONE!
Click to expand...
Click to collapse
No worries. I thought that might be the case (frustrated at the phone) which is why I posed it as a question. You'd be surprised at what folks here can sometimes take as an insult.
In any case, good luck and sorry we couldn't do more to help.