I write here because i can't write to he's thread.
I installed the 6.0 rom for my HTC One M8 from graffixnyc, but has not sound and it write's driver error, unknown problem. What's the problem?
I have S-on, custom recovery (twrp) and unlock bootloader. Plus the Hboot write's wrong image error.
I can't convert the cid to GOOGL_001, i have T-MOB101. That's the problem?
Thanks for the help!
Sorry for my bad English, I'm Hungarian!
Old firmware probably, you likely need to go back to stock and wait for all ota updates . BTW, this should be in q and a not general
timbohobbs said:
Old firmware probably, you likely need to go back to stock and wait for all ota updates . BTW, this should be in q and a not general
Click to expand...
Click to collapse
I can't back to stock because, not have original rom, firmware and ruu for this M8. It's a DE phone supposedly, but i can use it from Hungary with my Hungary sim card.
I wanna try to upgrade once and the phone bricked and i install twrp and a stock rooted rom from android revolution hd.
You'll probably run into problems if your firmware is out of date. S off may get you out of a hole
peti439 said:
I can't back to stock because, not have original rom, firmware and ruu for this M8. It's a DE phone supposedly
Click to expand...
Click to collapse
By DE you mean Developer's Edition? But your top post says T-MOB101.
If you don't know what your version is, you'll never get an RUU to work.
You can restore to stock nandroid from the collection posted on these threads, but again you need to know your correct CID version.
Do fastboot getvar all, and post the output (be sure to delete IMEI and serial numbers, as these are personal info) and we may be able to determine your actual CID version.
---------- Post added at 02:31 PM ---------- Previous post was at 02:31 PM ----------
peti439 said:
I can't convert the cid to GOOGL_001, i have T-MOB101. That's the problem?
Click to expand...
Click to collapse
You need s-off to change CID.
redpoint73 said:
By DE you mean Developer's Edition? But your top post says T-MOB101.
Click to expand...
Click to collapse
T-Mobile DE (Germany) - T-MOB101 - software version no. x.xx.111.x
ckpv5 said:
T-Mobile DE (Germany) - T-MOB001 - software version no. x.xx.111.x
Click to expand...
Click to collapse
Thanks! I thought that might be the case, but it was ambiguous. That's why its best for folks to be specific and detailed when asking for help!
To OP, still need getvar output to properly identify the right stock nandroid.
redpoint73 said:
Thanks! I thought that might be the case, but it was ambiguous. That's why its best for folks to be specific and detailed when asking for help!
To OP, still need getvar output to properly identify the right stock nandroid.
Click to expand...
Click to collapse
Agreed ... a typo is corrected - should read T-MOB101
redpoint73 said:
Thanks! I thought that might be the case, but it was ambiguous. That's why its best for folks to be specific and detailed when asking for help!
To OP, still need getvar output to properly identify the right stock nandroid.
Click to expand...
Click to collapse
I go to my computer and make a picture for the cidnum number. Wait a little
Here's what i got. My Hboot is 3.19.0.0000 and the Radio is 1.25.214500021.06G ( I don't know this are need )
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.111.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB101
(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
peti439 said:
Here's what i got.
Click to expand...
Click to collapse
I clearly posted previously (Post #5 above) to delete your IMEI and serial numbers from getvar output. These are personal data what should never be posted online. Please delete these numbers for your own protection.
---------- Post added at 09:37 AM ---------- Previous post was at 09:33 AM ----------
peti439 said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021
(bootloader) version-main: 4.19.111.2
Click to expand...
Click to collapse
The above info indicates that firmware shouldn't be an issue.
Did you do a full wipe (data, cache, Dalvik) when installing the GPE ROM?
---------- Post added at 09:41 AM ---------- Previous post was at 09:37 AM ----------
peti439 said:
Plus the Hboot write's wrong image error.
I can't convert the cid to GOOGL_001, i have T-MOB101. That's the problem?
Click to expand...
Click to collapse
It sounds like you are trying to do 2 different things:
- Flash the ROM zip in TWRP
- Flash the RUU (s-off required)
Which is it? You need to make up your mind, and understand the difference between the 2.
redpoint73 said:
I clearly posted previously (Post #5 above) to delete your IMEI and serial numbers from getvar output. These are personal data what should never be posted online. Please delete these numbers for your own protection.
---------- Post added at 09:37 AM ---------- Previous post was at 09:33 AM ----------
The above info indicates that firmware shouldn't be an issue.
Did you do a full wipe (data, cache, Dalvik) when installing the GPE ROM?
Click to expand...
Click to collapse
I make a full wipe before install the rom ( i make a full wipe before install any rom ). I installed the rom, make the setup steps ( login, etc ) and I can't hear any sound. I make a reboot and I looked the driver error.
peti439 said:
I make a full wipe before install the rom ( i make a full wipe before install any rom ). I installed the rom, make the setup steps ( login, etc ) and I can't hear any sound. I make a reboot and I looked the driver error.
Click to expand...
Click to collapse
Try to flash again.
Did you read the ROM thread to see if others had this issue?
redpoint73 said:
Try to flash again.
Did you read the ROM thread to see if others had this issue?
Click to expand...
Click to collapse
I flashed the rom three times and doesn't work. I not see others have any issues.
---------- Post added at 09:41 AM ---------- Previous post was at 09:37 AM ----------
redpoint73 said:
It sounds like you are trying to do 2 different things:
- Flash the ROM zip in TWRP
- Flash the RUU (s-off required)
Which is it? You need to make up your mind, and understand the difference between the 2.
Click to expand...
Click to collapse
I try to flash the ruu with 0p6bdiag.zip in HBoot and try to flash the rom with twrp. That was the problem to writes the error in Hboot?
peti439 said:
I try to flash the ruu with 0p6bdiag.zip in HBoot and try to flash the rom with twrp. That was the problem to writes the error in Hboot?
Click to expand...
Click to collapse
"Wrong image" means you are trying to run an RUU that doesn't match your CID. You need s-off to change CID.
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
peti439 said:
I flashed the rom three times and doesn't work. I not see others have any issues.
Click to expand...
Click to collapse
Try downloading the ROM zip to eliminate the possibility that it was corrupted during download.
Did you cancel the option in TWRP to root the ROM, as directed in the ROM thread?
redpoint73 said:
"Wrong image" means you are trying to run an RUU that doesn't match your CID. You need s-off to change CID.
---------- Post added at 10:16 AM ---------- Previous post was at 10:15 AM ----------
Try downloading the ROM zip to eliminate the possibility that it was corrupted during download.
Did you cancel the option in TWRP to root the ROM, as directed in the ROM thread?
Click to expand...
Click to collapse
I canceled to root the rom because I tried to root the rom, i got bootloop everytime.
peti439 said:
I canceled to root the rom because I tried to root the rom, i got bootloop everytime.
Click to expand...
Click to collapse
Which is expected, and clearly indicated in the ROM instructions.
But it sounds like at least on the latest flash attempts, you properly cancelled the root option.
I don't seen much reason for the bugs you are experiencing. Did you try to download the ROM again as previously suggested?
redpoint73 said:
Which is expected, and clearly indicated in the ROM instructions.
But it sounds like at least on the latest flash attempts, you properly cancelled the root option.
I don't seen much reason for the bugs you are experiencing. Did you try to download the ROM again as previously suggested?
Click to expand...
Click to collapse
I downloaded two times. Once my computer and second time to my girlfriend laptop ( that was three days ago ) and doesn't work, the zip was not corrupted.
Related
Hey, guys, one day i was searching for Lollipop ROM for my HTC One M8, i had stock 4.4.3 and stock 4.4.3 firmware, after installing SkyDragon ROM i lost my Wi-Fi, i wanted to get back to full stock, but i have S-ON and Unlocked bootloader, idk which firmware and software i had because when i am running "getvar all" main version is blank, CID is HTC_059, i tried to restore nandroid backup for TWRP 2.22.707.4 and 2.22.707.3, TWRP gives unknown error, then i tried to fastboot old recoveries randomly, nothing helped, and the stock recoverie that possibly was on my htc says: "Device_CW_Install: No CW files. Skip cw installation. Write host_mode:0 done":crying: What can i do?
I also think that MID and CID changed during my manipulations, is that possible on S-ON Device?
MID & CID change is not possible with S-On
To confirm, run this command in fastboot mode - fastboot getvar all and post the result here (delete the serialno and imei no)
If HTC__059 then TWRP 2.22.707.4 and 2.22.707.3 are correct.
You mentioned unknown error .. please explain what error.
How do you restore the backup zip ? You are not supposed to install them but extract them on PC and transfer to your device TWRP/BACKUPS/serialno/folder
ckpv5 said:
MID & CID change is not possible with S-On
To confirm, run this command in fastboot mode - fastboot getvar all and post the result here (delete the serialno and imei no)
If HTC__059 then TWRP 2.22.707.4 and 2.22.707.3 are correct.
You mentioned unknown error .. please explain what error.
How do you restore the backup zip ? You are not supposed to install them but extract them on PC and transfer to your device TWRP/BACKUPS/serialno/folder
Click to expand...
Click to collapse
I extract them on the sd card, the twrp backup folder, then go to TWRP "Restore" and choose the folder where i extracted it, it just says FAILED. And here is the "getvar":
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(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: HTC__059
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Please help!!!
1. change your TWRP to the latest version. What you have is very old, that is why you have that empty version-main.
2. use the TWRP to make a backup of boot then see where the backup goes ... your downloaded backup folder should go to the same directory ... or simply copy the content of downloaded backup to that boot backup folder.
Most of the time, the error is due to wrong directory.
Your getvar all confirmed that your CID & MID are correct for TWRP 2.22.707.4 or 2.22.707.3 .. it is better to use 2.22.707.3 backup first then do the necessary OTA up to the latest 3.32.707.9
ckpv5 said:
1. change your TWRP to the latest version. What you have is very old, that is why you have that empty version-main.
2. use the TWRP to make a backup of boot then see where the backup goes ... your downloaded backup folder should go to the same directory ... or simply copy the content of downloaded backup to that boot backup folder.
Most of the time, the error is due to wrong directory.
Your getvar all confirmed that your CID & MID are correct for TWRP 2.22.707.4 or 2.22.707.3 .. it is better to use 2.22.707.3 backup first then do the necessary OTA up to the latest 3.32.707.9
Click to expand...
Click to collapse
Thanks a lot, i will try that later and notify if that works! And at least what version should TWRP be? i used 2.7.0.
Use this one - http://forum.xda-developers.com/showpost.php?p=56478315&postcount=704
click on "built a quick version of 2.8.1.0 with the font issue fixed" to download
ckpv5 said:
Use this one - http://forum.xda-developers.com/showpost.php?p=56478315&postcount=704
click on "built a quick version of 2.8.1.0 with the font issue fixed" to download
Click to expand...
Click to collapse
Hey, so i moves the unziped folder to the twrp backups folder and when i try to restore the nandroid twrp says "Unable to mount /data" what should i do?
ckpv5 said:
Use this one - http://forum.xda-developers.com/showpost.php?p=56478315&postcount=704
click on "built a quick version of 2.8.1.0 with the font issue fixed" to download
Click to expand...
Click to collapse
Also i forgot to say that Hboot says Tampered and there is no OS.
I have the same problem, though with sense, s-off and and locked boot loader, had gpe installed but went back to sense because of the lack of being unable to move apps to SD..
Have no idea how to fix it, or what information I need to get help with it, just wanna return phone to 100% stock.
Geoffr86 said:
I have the same problem, though with sense, s-off and and locked boot loader, had gpe installed but went back to sense because of the lack of being unable to move apps to SD..
Have no idea how to fix it, or what information I need to get help with it, just wanna return phone to 100% stock.
Click to expand...
Click to collapse
Start with fastboot getvar all info (delete the serialno and imei no)
then many around here can give suggestions.
---------- Post added at 09:36 PM ---------- Previous post was at 09:32 PM ----------
Everest8872 said:
Hey, so i moves the unziped folder to the twrp backups folder and when i try to restore the nandroid twrp says "Unable to mount /data" what should i do?
Click to expand...
Click to collapse
That's something that never happen to me and not familiar with.
Have you try to restore only system and boot only ?
ckpv5 said:
Start with fastboot getvar all info (delete the serialno and imei no)
then many around here can give suggestions.
Click to expand...
Click to collapse
Thanks for quick reply, I'll do that when I have access to a PC, Unless it can be done via phone?
Everest8872 said:
Hey, so i moves the unziped folder to the twrp backups folder and when i try to restore the nandroid twrp says "Unable to mount /data" what should i do?
Click to expand...
Click to collapse
This issue crops up in TWRP from time to time. Did you update TWRP as ckpv5 suggested? Re-installing TWRP will sometimes make this error go away.
redpoint73 said:
This issue crops up in TWRP from time to time. Did you update TWRP as ckpv5 suggested? Re-installing TWRP will sometimes make this error go away.
Click to expand...
Click to collapse
yep!
ckpv5 said:
Start with fastboot getvar all info (delete the serialno and imei no)
then many around here can give suggestions.
---------- Post added at 09:36 PM ---------- Previous post was at 09:32 PM ----------
That's something that never happen to me and not familiar with.
Have you try to restore only system and boot only ?
Click to expand...
Click to collapse
YAY!!!! THAT WORKED!!! THANKS!!! I will make a donation asap!!!
Okay so.. In december i rooted my phone to Cyanogenmod. I lost the phone and got it back after 6 months.
I have reinstalled everything on my computer so i dont have the cyanogenmod left, unlock code or anything just so you know.
However.
Yesterday i tried to go back to stock android, HTC Sense.
So i searched on youtube how to do it, i followed the steps and i apparently had the wrong RUU.
What happend is weird..
Somehow i could startup my phone and it looked like i still had cyanogenmod. However this time i could not load up any applications without it crashing. I could not start my wifi or anything.
So i tried everything over again.
Installing twrp and.. after that i couldnt get into recovery.
Everytime i load up fastboot and try press recovert or factory reset it says "Entering recovery..." and then it reboots into android.
So i tried to install a new RUU.
Apparently still the wrong one, and this time im stuck in fastboot. No matter what i do i cant get out from fastboot.
So i'm asking you guys, do you have any idea of what i can do?
Oh and i managed to relock my phone, even though it said "failed" on CMD, it rebooted and then it said relocked.
So i cant unlock it either now. It just says "!!ERROR!!"
So im sitting here with what i think is a bricked phone, and im hoping for the best that it isnt..
So can you help me with this? Is it possible?
I can give you all information you need if you ask for it. For now i dont know what to say about this.
EDIT: Yes i have looked through 1000 different threads about beeing stuck in fastboot. But nothing helps.
If you need pictures of how it looks or anything i can fix that.
rambofreac said:
Okay so.. In december i rooted my phone to Cyanogenmod. I lost the phone and got it back after 6 months.
I have reinstalled everything on my computer so i dont have the cyanogenmod left, unlock code or anything just so you know.
However.
Yesterday i tried to go back to stock android, HTC Sense.
So i searched on youtube how to do it, i followed the steps and i apparently had the wrong RUU.
What happend is weird..
Somehow i could startup my phone and it looked like i still had cyanogenmod. However this time i could not load up any applications without it crashing. I could not start my wifi or anything.
So i tried everything over again.
Installing twrp and.. after that i couldnt get into recovery.
Everytime i load up fastboot and try press recovert or factory reset it says "Entering recovery..." and then it reboots into android.
So i tried to install a new RUU.
Apparently still the wrong one, and this time im stuck in fastboot. No matter what i do i cant get out from fastboot.
So i'm asking you guys, do you have any idea of what i can do?
Oh and i managed to relock my phone, even though it said "failed" on CMD, it rebooted and then it said relocked.
So i cant unlock it either now. It just says "!!ERROR!!"
So im sitting here with what i think is a bricked phone, and im hoping for the best that it isnt..
So can you help me with this? Is it possible?
I can give you all information you need if you ask for it. For now i dont know what to say about this.
EDIT: Yes i have looked through 1000 different threads about beeing stuck in fastboot. But nothing helps.
If you need pictures of how it looks or anything i can fix that.
Click to expand...
Click to collapse
In fastboot, issue the command fastboot getvar all, and post the readout here. Be sure to edit out the serial # and IMEI from it though. Never post those on a public forum.
I, or someone else here, will be able to direct you to the proper RUU with that information..
xunholyx said:
In fastboot, issue the command fastboot getvar all, and post the readout here. Be sure to edit out the serial # and IMEI from it though. Never post those on a public forum.
I, or someone else here, will be able to direct you to the proper RUU with that information..
Click to expand...
Click to collapse
I have now solved it, and i will post how i did it. Thx anyway, even if it was a bit late.
rambofreac said:
I have now solved it, and i will post how i did it. Thx anyway, even if it was a bit late.
Click to expand...
Click to collapse
Yeah. I scrolled the Q&A forum this morning looking for unanswered posts. Yours was one of them. I'm glad to hear that you have fixed it.
xunholyx said:
Yeah. I scrolled the Q&A forum this morning looking for unanswered posts. Yours was one of them. I'm glad to hear that you have fixed it.
Click to expand...
Click to collapse
same problem and i cant solve it . help plz
7anata said:
same problem and i cant solve it . help plz
Click to expand...
Click to collapse
Same info needed that I asked the last user for. fastboot getvar all results, minus your ser# and IMEI
xunholyx said:
Same info needed that I asked the last user for. fastboot getvar all results, minus your ser# and IMEI
Click to expand...
Click to collapse
version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: HTC__622
(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
and why there is no version main number
7anata said:
same problem and i cant solve it . help plz
Click to expand...
Click to collapse
Same problem, meaning you rooted the phone a year ago, put CM on it, then lost it and got it back 6 months later???
That's an incredible coincidence!!!!
Seriously, some constructive advice for a new forum user: DO NOT EVER say "same problem" then don't post any details on your phone and issue. It makes it virtually impossible to provide you any help. There are far too many variables such as carrier versions, software versions, and personal setups; that guarantee that issues may be similar, but never the "same". That's why its important to provide details, otherwise you just waste time us having to ask you for them.
Additionally, what were you doing with the phone that brought it to this point (stuck in fastboot)? Provide as much detail as possible (you can never really provide too much detail). Exact steps, what you were trying to flash, install or update, etc. Any error messages or other behaviors from the phone before it got stuck, etc. Also, what TWRP version? Do you have a nandroid (TWRP backup) available? Do you have a custom ROM installed?
---------- Post added at 10:40 AM ---------- Previous post was at 10:35 AM ----------
xunholyx said:
minus your ser# and IMEI
Click to expand...
Click to collapse
Also, xunholyx was very clear that you should delete your serial number and IMEI before posting getvar data. These are personal data, that should never be posted on open forums; so please delete them from the above post.
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
7anata said:
and why there is no version main number
Click to expand...
Click to collapse
Known version caused by old TWRP builds.
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
[/COLOR]
Known version caused by old TWRP builds.[/QUOTE]
thanx alot , but i have latest version of TWRP 2.8.7.0 , how can i know version-main , thanx in advance
7anata said:
thanx alot , but i have latest version of TWRP 2.8.7.0 , how can i know version-main , thanx in advance
Click to expand...
Click to collapse
If an older version of TWRP was used at any point in the past, it would have wiped out the main version, and the only way to make it reappear is to flash a firmware or RUU.
Based on your CID and radio number, I believe your main version is 4.18.708
If you want further help, you need to provide the information I asked for (and that you have ignored):
redpoint73 said:
Additionally, what were you doing with the phone that brought it to this point (stuck in fastboot)? Provide as much detail as possible (you can never really provide too much detail). Exact steps, what you were trying to flash, install or update, etc. Any error messages or other behaviors from the phone before it got stuck, etc. Do you have a nandroid (TWRP backup) available? Do you have a custom ROM installed?
Click to expand...
Click to collapse
redpoint73 said:
If an older version of TWRP was used at any point in the past, it would have wiped out the main version, and the only way to make it reappear is to flash a firmware or RUU.
Based on your CID and radio number, I believe your main version is 4.18.708
If you want further help, you need to provide the information I asked for (and that you have ignored):
Click to expand...
Click to collapse
sorry man i didn't ignore the info , i didn't see that , iam tring to update cm 13 17/12/2015 recovery , iam on cm13 15/12/2015 rom , i solved the stuck problem but can't get excat version main so i can uroot my phone .....
and according to this link there isn't main version is 4.18.708 with cid Htc__622
I was running the official CM12.1 on my Verzone HTC One M8 and everything was working as expected. About a month after installing it, one day my phone stopped picking up a cell signal altogether. I re-flashed the CM12.1 that was on my phone and have only been able to pick up 3g signal since then. In the cellular network options i have tried to change the settings but the only settings are global, LTE Mode and LTE/Legacy 3gpp mode. The latter 2 don't work and the first one works but only picks up 3g. I'm not sure why the LTE/CDMA option isn't there.
In an attempt to fix it, I have restored with most recent version of TWRP back to a couple previous backups from before this issue presented itself but it still only picks up 3g.
I updated the firmware/radios using the thread below and it didn't change anything.
http://forum.xda-developers.com/veri...mware-t3196906
I flashed the stock rooted firmware in the thread below:
http://forum.xda-developers.com/veri...mware-t3196906
I'm currently running the fluentrom from the thread below but still nothing has changed. It will only pick up 3g.
http://forum.xda-developers.com/veri...540-8-t3007173
I also go a new sim card but that didn't change anything either.
FYI, it's s-off
Any suggestions to get LTE back?
Unlock your phone ie Super CID it..... latest firmware and try another rom........if it doesnt work with another rom you know its firmware. And wipe everything and format when installing do not dirty flash
eskimosound said:
Unlock your phone ie Super CID it..... latest firmware and try another rom........if it doesnt work with another rom you know its firmware. And wipe everything and format when installing do not dirty flash
Click to expand...
Click to collapse
I've already flashed multiple roms and did a full wipe (cache, dalvik cache, system, data) before each new install. What I didn't wipe was the internal storage, micro sd card, android secure, usb-otg and sd-ext. Should I wipe any of those before flashing?
pinkfloydviste said:
I've already flashed multiple roms and did a full wipe (cache, dalvik cache, system, data) before each new install. What I didn't wipe was the internal storage, micro sd card, android secure, usb-otg and sd-ext. Should I wipe any of those before flashing?
Click to expand...
Click to collapse
OK, don't wipe the micro SD card, that's where your rom is. Wipe internal storage, and Android secure, I don't think it will let you wipe anything else. Then format completely, then flash new rom, it should work if it doesn't then it is definitely your firmware. Have you got super cid?
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
eskimosound said:
OK, don't wipe the micro SD card, that's where your rom is. Wipe internal storage, and Android secure, I don't think it will let you wipe anything else. Then format completely, then flash new rom, it should work if it doesn't then it is definitely your firmware. Have you got super cid?
Click to expand...
Click to collapse
Try wiping everything except micro sd. It won't let you do a couple of things but that's OK, then format.
eskimosound said:
OK, don't wipe the micro SD card, that's where your rom is. Wipe internal storage, and Android secure, I don't think it will let you wipe anything else. Then format completely, then flash new rom, it should work if it doesn't then it is definitely your firmware. Have you got super cid?
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
Try wiping everything except micro sd. It won't let you do a couple of things but that's OK, then format.
Click to expand...
Click to collapse
I don't have supercid, I"m reading up on it right now.
It'll take me a few minutes to transfer everything I want from my internal storage and then I'll try wiping it too.
Why keep on guessing it's the firmware !
Fastboot getvar all
Post the output and you know almost everything !
Mr Hofs said:
Why keep on guessing it's the firmware !
Fastboot getvar all
Post the output and you know almost everything !
Click to expand...
Click to collapse
I just changed it to supercid but still haven't wiped anything more. Here is what printed out when I typed in Fastboot getvar all
C:\Users\Upstairs1\Desktop\Modding\Android\M8\One_M8_All-In-One_Kit_v1.0.1\One_M
8_All-In-One_Kit_v\Data>Fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.605.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT447SF00104
(bootloader) imei: 990004998579845
(bootloader) imei2: Not Support
(bootloader) meid: 99000499857984
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(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: 66da6304
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
Well man, wipe and reinstall, see what happens, I don't know what any of that getvar means, well I do but now you are Super CID it doesn't matter!!!
eskimosound said:
Well man, wipe and reinstall, see hat happens, I don't know what any of that getvar means, well I do but now you are Super CID it doesn't matter!!!
Click to expand...
Click to collapse
Explain please, what doesn't matter ? And do you know it or not .... the output ?
@OP.
I suggest to bring the phone back to full Verizon stock to begin with. Backup what you need to a PC because be prepared to wipe the entire phone and all storage partitions !
Have a read here
http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-with-android-5-0-1-lollipop-ruufuu/
It contains all info for your Verizon device and it has the latest lollipop ruu download.
Mr Hofs said:
Explain please, what doesn't matter ? And do you know it or not .... the output ?
Click to expand...
Click to collapse
Well I know:
His bootloader is: 3.19.0.0000
His Baseband is: 1.12.20.1211
His firmware is: 4.17.605.9
He has S-Off and he's now Super CID...
Thats all you need to know...
So update to latest firmware and stick on whatever Rom you like.......
eskimosound said:
Well I know:
His bootloader is: 3.19.0.0000
His Baseband is: 1.12.20.1211
His firmware is: 4.17.605.9
He has S-Off and he's now Super CID...
Thats all you need to know...
Click to expand...
Click to collapse
Yeah of course that's the output from the command, i can read that too......
But what "doesn't matter" ?
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
eskimosound said:
Well I know:
His bootloader is: 3.19.0.0000
His Baseband is: 1.12.20.1211
His firmware is: 4.17.605.9
He has S-Off and he's now Super CID...
Thats all you need to know...
So update to latest firmware and stick on whatever Rom you like.......
Click to expand...
Click to collapse
That's bull, he's on a 3.19 hboot that's already good enough to install the latest roms available. Has nothing to do with the "suddenly dropping 4g" issue because it worked before
Mr Hofs said:
Yeah of course that's the output from the command, i can read that too......
But what "doesn't matter" ?
Click to expand...
Click to collapse
Ah I get you, well after you go Super CID you no longer need to worry about your carrier, i.e. I was O2 International and needed the specific firmware after Super CID they all work........
Well 4g doesn't stop automatically after a month. So it must have given some error/issue somewhere but it's not the firmware and also not the support in CID's.
In my opinion it's best to bring it back to original stock as it came out of the box and see to it to get that working including 4g.
Mr Hofs said:
Yeah of course that's the output from the command, i can read that too......
But what "doesn't matter" ?
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
That's bull, he's on a 3.19 hboot that's already good enough to install the latest roms available. Has nothing to do with the "suddenly dropping 4g" issue because it worked before
Click to expand...
Click to collapse
Hey you wanna sort it out, sort it out, I thought yeah this has happened to me, exactly the same it was corrupt firmware I reinstalled the firmware it worked.
Thats my experience and it didnt show up on my getvar as corrupted, so I was being told all sorts.
But hats what it was firmware.
Now I don't know what this is all I know is that to fix every error like this needs a clean full wipe. format and a reinstall and if that doesnt work a firmware. Its a radio issue as you know and that is included in the firmware.
But hey over to you Im just a passing hobbiest I know Mr Hoff you are a God in such matters
eskimosound said:
Hey you wanna sort it out, sort it out, I thought yeah this has happened to me, exactly the same it was corrupt firmware I reinstalled the firmware it worked.
Thats my experience and it didnt show up on my getvar as corrupted, so I was being told all sorts.
But hats what it was firmware.
Now I don't know what this is all I know is that to fix every error like this needs a clean full wipe. format and a reinstall and if that doesnt work a firmware. Its a radio issue as you know and that is included in the firmware.
But hey over to you Im just a passing hobbiest I know Mr Hoff you are a God in such matters
Click to expand...
Click to collapse
Definitely no god here, we all learn and even i have to learn !
I appreciate both of you taking the time to help. I'm currently working on backing up what I want from my phones' internal memory. Then, I think I'll restore it to the pre-rooted stock rom and see if I get lte connectivity. Assuming I get LTE connectivity, I'll reinstall twrp and flash the rom of my choice. I'll keep you posted.
pinkfloydviste said:
I appreciate both of you taking the time to help. I'm currently working on backing up what I want from my phones' internal memory. Then, I think I'll restore it to the pre-rooted stock rom and see if I get lte connectivity. Assuming I get LTE connectivity, I'll reinstall twrp and flash the rom of my choice. I'll keep you posted.
Click to expand...
Click to collapse
Good luck, hope you succeed very soon !
Mr Hofs said:
Good luck, hope you succeed very soon !
Click to expand...
Click to collapse
I have everything backed up. It will take about 20 minutes to download the utility. I think I'll try the full wipe and reinstall the rom like you suggested in the meantime.
Mr Hofs said:
Good luck, hope you succeed very soon !
Click to expand...
Click to collapse
Yep good luck to you... :silly:
I'm sure you will sort it... see this post... my early days....http://forum.xda-developers.com/htc-one-m8/help/various-problems-t3070636
See the last post by Redpoint73......
Oh and if you are both bored with the lack of colour on the Extreme Power Saver screen see this:
http://forum.xda-developers.com/htc...heme-extreme-power-saver-leaf-colour-t3195079
eskimosound said:
Yep good luck to you... :silly:
I'm sure you will sort it... see this post... my early days....http://forum.xda-developers.com/htc-one-m8/help/various-problems-t3070636
See the last post by Redpoint73......
Oh and if you are both bored with the lack of colour on the Extreme Power Saver screen see this:
http://forum.xda-developers.com/htc...heme-extreme-power-saver-leaf-colour-t3195079
Click to expand...
Click to collapse
So, wiping everything but the sd card and reinstalling the rom didn't work. Still just have 3g. I'll try the other method now that the utility has downloaded.
So here's my predicament, a long while ago i had installed a rom to my phone assuming i had done everything correctly. This ROM i installed is the Bad Boys One M8 L Sense 7 v 1.0, it is currently still what I'm currently using. What I've been trying to do for days now to return my phone back to stock. My bootloader is unlocked and s-off. I have been unable to install any ROM whatsoever besides the current bad boyz rom. Also when trying to use sunshine, it seems to also encounter problems. If anyone can offer some help or a method to go about fixing this it would greatly appreciated.
Jdp2510 said:
So here's my predicament, a long while ago i had installed a rom to my phone assuming i had done everything correctly. This ROM i installed is the Bad Boys One M8 L Sense 7 v 1.0, it is currently still what I'm currently using. What I've been trying to do for days now to return my phone back to stock. My bootloader is unlocked and s-off. I have been unable to install any ROM whatsoever besides the current bad boyz rom. Also when trying to use sunshine, it seems to also encounter problems. If anyone can offer some help or a method to go about fixing this it would greatly appreciated.
Click to expand...
Click to collapse
For Sunshine to work, flash MaximumHD , or you could also flash ViperOneM8 (suggested by JCase, one of the Sunshine devs) for it to work.
If you want to go back to stock, you need to provide more info. Post the results of fastboot getvar all here (minus your IMEI and serial#), and I or someone else here will be able to give you proper directions.
xunholyx said:
For Sunshine to work, flash MaximumHD , or you could also flash ViperOneM8 (suggested by JCase, one of the Sunshine devs) for it to work.
If you want to go back to stock, you need to provide more info. Post the results of fastboot getvar all here (minus your IMEI and serial#), and I or someone else here will be able to give you proper directions.
Click to expand...
Click to collapse
I have tried the maximus hd with it getting stuck at the recovery screen. As for the other I'll do what i can to figure out that info for you
Jdp2510 said:
I have tried the maximus hd with it getting stuck at the recovery screen. As for the other I'll do what i can to figure out that info for you
Click to expand...
Click to collapse
Not much to figure out.
Hook your phone up to your PC, get into ADB/fastboot, and enter the command fastboot getvar all.
xunholyx said:
Not much to figure out.
Hook your phone up to your PC, get into ADB/fastboot, and enter the command fastboot getvar all.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.25.651.18
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499318193
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_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: 0f94b3b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I've tried running the appropriate RUU; I've tried flashing other roms with no success; I just can't seem to get the correct directions on what I need to do. If anyone has any ideas it will all be very appreciated.
Jdp2510 said:
I've tried running the appropriate RUU; I've tried flashing other roms with no success; I just can't seem to get the correct directions on what I need to do. If anyone has any ideas it will all be very appreciated.
Click to expand...
Click to collapse
You are S-On, so to run the RUU successfully you'll need to re-lock your bootloader first.
In fastboot : fastboot oem lock
Then run the RUU again
I did try that but it kept failing, I'll try one more time.
Like I thought, it failed again, error 155:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
I'm downloading the correct RUU. http://www.htc.com/us/support/rom-downloads.html - The HTC One M8.
Jdp2510 said:
Like I thought, it failed again, error 155:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
I'm downloading the correct RUU. http://www.htc.com/us/support/rom-downloads.html - The HTC One M8.
Click to expand...
Click to collapse
Error 155 is common for MM RUUs, as there is a peculiarity with the MM RUUs, in which you can't upgrade from LP (or KK for that matter) by RUU unless you first run the MM firmware.zip.
Try flashing the full signed firmware 6.20.651.3 from the following thread (with instructions on how to flash) then run the RUU 6.20.651.3 again:
http://forum.xda-developers.com/showthread.php?t=2729173
Or your other option is to flash the 4.25.651.18 RUU (same thead) and OTA to MM.
---------- Post added at 11:10 AM ---------- Previous post was at 11:08 AM ----------
Jdp2510 said:
I have been unable to install any ROM whatsoever besides the current bad boyz rom.
Click to expand...
Click to collapse
Hard to know what you are talking about, if you don't supply the required specifics (what ROMs exactly).
But only ROMs that specifically support Sprint, will work on your phone, due to kernel differences between Sprint and most other versions of the M8.
Running the MM RUU isn't going to change this fact. It seems your goal is to be able to install other ROMs?
What kind of specifics do you need?
I haven't been able to get any other roms to work. The ruu meant for my phone keeps failing, the name of the ROM is what details my phone says,
Jdp2510 said:
What kind of specifics do you need?
Click to expand...
Click to collapse
I already asked exactly what ROMs you tried.
You say you can't get "any ROMs" to work, and only name one (that does work).
You probably are trying to flash ROMs that don't support the Sprint version M8.
---------- Post added at 10:05 AM ---------- Previous post was at 10:04 AM ----------
Jdp2510 said:
The ruu meant for my phone keeps failing, the name of the ROM is what details my phone says,
Click to expand...
Click to collapse
Yup, and it will keep failing, if you just try the same thing over and over.
Did you try to do as I suggested in my post #10 above (flash MM firmware.zip, then try the RUU again)?
Hi guys anybody can help me ? My Htc one m8 has been bricked i can't flash stock ruu please help me
this are my fastboot getvar all value :
(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.20.709.2
(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: 0P6B11000
(bootloader) cidnum: HTC__621
(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.008s
so my bootlader is locked with security warning and software status : modified
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
redpoint73 said:
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
Click to expand...
Click to collapse
When i flash RUU faced with "remote : 12 signautre verify fail" and this is a RUU that i flashed : HTC One M8 6.20.709.2 sense 8
redpoint73 said:
Which RUU did your try (version number, file name)? And what does that mean you "can't flash stock ruu"? Did you get any error messages, what point did it fail, etc.?
You also need to tell us how it is "bricked"? Were you trying to flash something, or update, etc.? Or just happened on its own (failed to boot to OS)?
Did you do any mods to the phone, or is it (as far as you know) stock? For that matter, did you get the phone used?
Click to expand...
Click to collapse
when i unplugged the phone from charger this problem occurred i didn't flash any RUU later and my phone is unrooted .
mamali0067 said:
when i unplugged the phone from charger this problem occurred .
Click to expand...
Click to collapse
I assume when you say "bricked" it means you can't boot to Android OS, but you can get to bootloader (otherwise, you wouldn't have been able to do fastboot getvar).
On the bootloader screen, does it say LOCKED or UNLOCKED near the top?
Also, I recommend you delete IMEI and serial number from your top post. These are personal info, and should not be posted online (and also, not needed to help or advise you).
---------- Post added at 09:09 AM ---------- Previous post was at 09:09 AM ----------
mamali0067 said:
When i flash RUU faced with "remote : 12 signautre verify fail" and this is a RUU that i flashed : HTC One M8 6.20.709.2 sense 8
Click to expand...
Click to collapse
To confirm, the file actually says "RUU" in the file name, and about 1.5 GB in size?
redpoint73 said:
I assume when you say "bricked" it means you can't boot to Android OS, but you can get to bootloader (otherwise, you wouldn't have been able to do fastboot getvar).
On the bootloader screen, does it say LOCKED or UNLOCKED near the top?
Also, I recommend you delete IMEI and serial number from your top post. These are personal info, and should not be posted online (and also, not needed to help or advise you).
---------- Post added at 09:09 AM ---------- Previous post was at 09:09 AM ----------
To confirm, the file actually says "RUU" in the file name, and about 1.5 GB in size?
Click to expand...
Click to collapse
yes of course it's about 1.6 GB and in my bootloader it say LOCKED
mamali0067 said:
yes of course it's about 1.6 GB and in my bootloader it say LOCKED
Click to expand...
Click to collapse
Is this a zip format RUU? If so, cut/paste the exact commands you used.
redpoint73 said:
Is this a zip format RUU? If so, cut/paste the exact commands you used.
Click to expand...
Click to collapse
yes the RUU is a zip file , but i flashed that RUU perefer in finding right RUU thread and faced with remote : 12 signature verify fail
mamali0067 said:
i flashed that RUU perefer in finding right RUU thread
Click to expand...
Click to collapse
I'm not going to jump around threads looking for the info. I already told you that twice. You should be trying to make it easier for folks to help you, not harder!
redpoint73 said:
I'm not going to jump around threads looking for the info. I already told you that twice. You should be trying to make it easier for folks to help you, not harder!
Click to expand...
Click to collapse
Okay dude , so help me here !
mamali0067 said:
Okay dude , so help me here !
Click to expand...
Click to collapse
You didn't provide the info I asked for: cut/paste the exact commands you used
redpoint73 said:
You didn't provide the info I asked for: cut/paste the exact commands you used
Click to expand...
Click to collapse
Yes , I have been cutted and pasted the command