Alright, I've been running back and forth between pages and making this phone worse and worse.
- Prologue -
I started with a beautiful AT&T version. Since the sellers never gave me the unlock code, I decided to do it the "fun" way.
I S-OFFed via Sunshine out of desperation to unlock properties within.
First Sense seemed limited, so I looked up how to put GPU and did it via RUU
Yay, I pop SIM card and witnessed in horror as the SIM refused to be connected to MetroPCS
I looked up the SuperCID, did the thing, then.... nothing.
Then I did Sieempi's little trick and, to my added disgust, the SIM refused to cooperate.
- Actual Story -
Then I tried to flash back to stock Sense ROM to see if Sense could do anything about it.
Gettin' ready to flash via TWRP, let's flash this ROM, "Error Flashing _____"
I throw a random radio in to flash, fails as well.
Try DH's Beyond Stock Kernel. It also failed, maybe 'cause it was a Kernel.
Then tried to put back the Splash Sense .... thing, wiped out TWRP.
Also saw a thread that said I should also lock bootloader... BIG MISTAKE!!!
Now bootloader is "Relocked" and can't access TWRP, can't unlock bootloader via "WinDroid" (Used this in addition to cmd for the entire time)..... yeah...
HALP
Windows 7 x64
Getvar all
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA13G
version-cpld: None
version-microp: None
version-main: 1.54.401.5
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
Any other things ya need from me, just ask...
OK well your still S-OFF so if your phone don't boot than pull out the sdcard and put it in another device or a card reader so you can ruu using the 0P6BIMG.zip method .now keep in mind if you converted to GPE than I would stick with it just to have a booted phone.
Sim unlock method and read the thread .
http://forum.xda-developers.com/showthread.php?t=2708567
Related
Okay, a little background about my situation...
So my contract is coming to an end and I decided to flash a 4.4 based ROM. I didn't do enough research and although I successfully unlocked the bootloader, flashed a custom recovery and flashed the ROM...it wouldn't boot (which I now understand was caused by not having flashed the boot.img from within the ROM).
So anyways, I had wiped this/that/the other in order to try and resolve my above issue.
After much fiddling, I managed to get a Nandroid backup onto my phone (2.17 - restored and booted successfully). I then wanted to use an RUU to return the phone completely to stock. However, no matter what I do, I can't get the RUU to successfully install because my version-main is too new.
Firstly, is what I'm trying to do even possible? The reason why I want to be able to do this is so that if I ever decide to sell the phone on, that I can restore/reset it to as near to complete factory as possible.
Here's my FASTBOOT GETVAR ALL:
Code:
version: 0.5a
version-bootloader: 1.39.0000
version-baseband: 5.1204.163R.30
version-cpld: None
version-microp: None
version-main: 3.16.110.4
serialno: HT23SW116477
imei: 359188042240051
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: T-MOB005
battery-status: good
battery-voltage: 4150mV
devpower: 100
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
I should've known better than to attempt it without more research (didn't think HTC would make it harder to flash ROMs and then go back to stock...lesson learned)
Dazzd88 said:
Okay, a little background about my situation...
So my contract is coming to an end and I decided to flash a 4.4 based ROM. I didn't do enough research and although I successfully unlocked the bootloader, flashed a custom recovery and flashed the ROM...it wouldn't boot (which I now understand was caused by not having flashed the boot.img from within the ROM).
So anyways, I had wiped this/that/the other in order to try and resolve my above issue.
After much fiddling, I managed to get a Nandroid backup onto my phone (2.17 - restored and booted successfully). I then wanted to use an RUU to return the phone completely to stock. However, no matter what I do, I can't get the RUU to successfully install because my version-main is too new.
Firstly, is what I'm trying to do even possible? The reason why I want to be able to do this is so that if I ever decide to sell the phone on, that I can restore/reset it to as near to complete factory as possible.
Here's my FASTBOOT GETVAR ALL:
Code:
version: 0.5a
version-bootloader: 1.39.0000
version-baseband: 5.1204.163R.30
version-cpld: None
version-microp: None
version-main: 3.16.110.4
serialno: HT23SW116477
imei: 359188042240051
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: T-MOB005
battery-status: good
battery-voltage: 4150mV
devpower: 100
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
I should've known better than to attempt it without more research (didn't think HTC would make it harder to flash ROMs and then go back to stock...lesson learned)
Click to expand...
Click to collapse
No RUU for this main version you must to find stock nandroid backup
Yeah, go and grab from the nandroid backup post in general section the 3.16.110.4 backup. Flash the recovery that it's in the backup, flash the boot image, and the restore the nandroid.
Sent from my HTC One X
Okay guys thanks. Not quite what I was hoping to hear. :crying:
Just wish HTC would make it easier for people to customize and then go back to stock with an RUU...a bit like my old Desire where I was able to use an older RUU than the software version on my phone to go back to stock (can't remember the actual process I used).
I think I may ditch HTC when I get my upgrade.
Okay, so I'm a Samsung Note 3 owner that's helping out a guy to unscrew his AT&T M8. We're trying to return to nandroid stock using this guide http://forum.xda-developers.com/show....php?t=2701376, and I'm at the step where it says to flash the nandroid .zip file in TWRP. This is all fine and dandy, but even though it's located in the TWRP/backups folder, and apparently it's the correct nandroid version, it FAILS immediately. Maybe I got the wrong version??? I've googled around, but I can't seem to get the right info on this one!
Any and all help would be appreciated!!!:good:
Read that thread thoroughly ...
You don't flash the nandroid.zip
You extract the nandroid.zip and transfer the content to TWRP backup folder.
Anyway ... browse thru AT&T forum, you should be able to find the correct RUU
http://forum.xda-developers.com/att-htc-one-m8/general
No RUU will flash!!!! No main version shown in RUU utility...
ckpv5 said:
Read that thread thoroughly ...
You don't flash the nandroid.zip
You extract the nandroid.zip and transfer the content to TWRP backup folder.
Anyway ... browse thru AT&T forum, you should be able to find the correct RUU
http://forum.xda-developers.com/att-htc-one-m8/general
Click to expand...
Click to collapse
I have tried a few newer RUU's since I'm on 3.16 bootloader and S-ON. When I go to flash using the RUU utility, it doesn't show any installed rom...because there IS no installed ROM!
Therefore, it fails. As you can see below...there is nothing showing in version-main. Any idea on how to fix this??? The phone isn't bricked...there's just no rom installed. Should I use TWRP instead???
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA43SWM04387
imei: 358718050243422
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
I have tried a few newer RUU's since I'm on 3.16 bootloader and S-ON. When I go to flash using the RUU utility, it doesn't show any installed rom...because there IS no installed ROM!
Therefore, it fails. As you can see below...there is nothing showing in version-main. Any idea on how to fix this??? The phone isn't bricked...there's just no rom installed. Should I use TWRP instead??? What RUU should I be using???? (A friend came over trying to return this back to stock, after a bad Venom rom flash)
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA43SWM04387
imei: 358718050243422
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
........
jreed3786 said:
I have tried a few newer RUU's since I'm on 3.16 bootloader and S-ON. When I go to flash using the RUU utility, it doesn't show any installed rom...because there IS no installed ROM!
Therefore, it fails. As you can see below...there is nothing showing in version-main. Any idea on how to fix this??? The phone isn't bricked...there's just no rom installed. Should I use TWRP instead??? What RUU should I be using???? (A friend came over trying to return this back to stock, after a bad Venom rom flash)
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA43SWM04387
imei: 358718050243422
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
You have 4.4.2 firmware. The reason ViperOne caused you problems is because you need updated firmware.
You'll need to find an AT&T RUU. You'll also have to re-lock your bootloader before running it. It also will have to be a signed RUU. All three of these things are because you are S-On.
You could also download ViperOne 1.x.x (a 4.4.2 base), put that onto your extSD, and flash that as normal in recovery. It will get you back running, and is a compatible version of ViperOne for your phone.
You can download ViperOneM8 1.7.1 from this link.
xunholyx said:
You have 4.4.2 firmware. The reason ViperOne caused you problems is because you need updated firmware.
You'll need to find an AT&T RUU. You'll also have to re-lock your bootloader before running it. It also will have to be a signed RUU. All three of these things are because you are S-On.
You could also download ViperOne 1.x.x (a 4.4.2 base), put that onto your extSD, and flash that as normal in recovery. It will get you back running, and is a compatible version of ViperOne for your phone.
You can download ViperOneM8 1.7.1 from this link.
Click to expand...
Click to collapse
I tried doing fastboot oem lock....no luck. Any ideas? Is CWS__001 the correct CID for AT&T M8?
jreed3786 said:
I tried doing fastboot oem lock....no luck. Any ideas? Is CWS__001 the correct CID for AT&T M8?
Click to expand...
Click to collapse
It didn't work? That's weird. Does it show "unlocked" in your bootloader?
And yes it is the correct CID. I wondered why you asked, then saw saw your signature. I knew AT&T because of you being in the US and your CID.
Never mind. I figured it out on my own.
xunholyx said:
You have 4.4.2 firmware. The reason ViperOne caused you problems is because you need updated firmware.
You'll need to find an AT&T RUU. You'll also have to re-lock your bootloader before running it. It also will have to be a signed RUU. All three of these things are because you are S-On.
You could also download ViperOne 1.x.x (a 4.4.2 base), put that onto your extSD, and flash that as normal in recovery. It will get you back running, and is a compatible version of ViperOne for your phone.
You can download ViperOneM8 1.7.1 from this link.
Click to expand...
Click to collapse
Thank you very much, though! I'm just glad I chose a Samsung product! I remember the Hell says of my Sensation! Lol!
jreed3786 said:
Thank you very much, though! I'm just glad I chose a Samsung product! I remember the Hell says of my Sensation! Lol!
Click to expand...
Click to collapse
That's funny, I'm glad I chose to leave Samsung products.
Hi.
I have a HTC ON M8 that bought a few days ago. 4.4.2 android had K.K., so I decided fastboot flash by. He had signal problems since it was unstable and could not connect to 3g or 4g. Only 2g. I descargueé install the USB drivers for htc, I placed the fastboot folder in c: \ fastboot, but it has given me some problems. I can perfectly restart in bootoader mode, verify mid, cid, model, but leave flashing me any zip because fastboot says. "ERROR: CAN NOT LOAD firmware.zip I can also unlock the bootloader with Unlock_code because fastboot says" REMOTE: NOT ALLOWED ".
Because of this, I had to update by RUU.
Download 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed and I put it on my SD card. The process did not produce errors, but incender my M8, threw a warning in red letters, "device tree is not totally matched." After setting my M8, I noticed that the signal was much more unstable. In almost all times no signal, and when it does, it is going slowly.
I'm really desperate. I do not know what to do, friends. I am from Chile, South America, and the M8 should work well with 4g (2600) and 3g networks.
These are the RUU I installed, but have not given me a solution to my problem:
- 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
- 0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
- 0P6BIMG_M8_UL_K444_SENSE60_MR_HTC_Europe_3.28.401.9_R_Radio_1.22.21331147A1.29G_20.67.4196.01_release_402839_signed
I'll leave information about my HTC ONE M8:
- The bootloader is LOCKED.
(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: XF SHIP S-OFF
(bootloader) serialno: HT43TWM04554
(bootloader) imei: 35871**************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(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
I hope you can help me, please.
Regards.
Black_Wolf83 said:
Hi.
I have a HTC ON M8 that bought a few days ago. 4.4.2 android had K.K., so I decided fastboot flash by. He had signal problems since it was unstable and could not connect to 3g or 4g. Only 2g. I descargueé install the USB drivers for htc, I placed the fastboot folder in c: \ fastboot, but it has given me some problems. I can perfectly restart in bootoader mode, verify mid, cid, model, but did not leave me any zip flash. I can not unlock the bootloader with Unlock_code because it gives me error. Displays a warning that could not be loaded.
Because of this, I had to update by UCP. Download 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed and I put it on my SD card. The process did not produce errors, but incender my M8, threw a warning in red letters, "device tree is not totally matched." After setting my M8, I noticed that the signal was much more unstable. In almost all times no signal, and when it does, it is going slowly.
I'm really desperate. I do not know what to do, friends. I am from Chile, South America, and the M8 should work well with 4g (2600) and 3g networks.
These are the RUU I installed, but have not given me a solution to my problem:
- 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
- 0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
- 0P6BIMG_M8_UL_K444_SENSE60_MR_HTC_Europe_3.28.401.9_R_Radio_1.22.21331147A1.29G_20.67.4196.01_release_402839_signed
I'll leave information about my HTC ONE M8:
- The bootloader is LOCKED.
(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: XF SHIP S-OFF
(bootloader) serialno: HT43TWM04554
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(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
I hope you can help me, please.
Regards.
Click to expand...
Click to collapse
your getvar all is displaying imei. (if it is correct, delete it. but i think it is wrong one.)
the first thing you should do is unlock bootloader. if your device is already rooted, it is not problem.http://forum.xda-developers.com/showthread.php?t=2708571. however your device is uncommon. (XF SHIP) did you buy your device in s-off condition?
what type of errors did you get when you were trying to flash ruu 0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.1 0?
umesh.lk said:
your getvar all is displaying imei. (if it is correct, delete it. but i think it is wrong one.)
the first thing you should do is unlock bootloader. if your device is already rooted, it is not problem.http://forum.xda-developers.com/showthread.php?t=2708571. however your device is uncommon. (XF SHIP) did you buy your device in s-off condition?
what type of errors did you get when you were trying to flash ruu 0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.1 0?
Click to expand...
Click to collapse
I will try to use the method post the link that hit me.
To install the RUU, so I place on the SD card, then reboot in bootloader mode. Checking the UCP does well. After restarting been installed, my M8 and the logo HTC me a message saying "DEVICE IS NOT MATCHED TREE" appears. Subsequently, remains frozen for a few seconds, another HTC logo appears and from there start setting up my M8. But the other problem I have is that no network signal. Rarely it takes and is too unstable.
I could not fastboot flash ROMs because you do not connect with my M8 for flashing ZIP. He tells me "ERROR: CAN NOT LOAD firmware.zip"
Galaxy S5 had before. A few days ago I permuté HTC ONE M8 this coming with S-OFF, CID 11111111 and Boot LOCKED.
Black_Wolf83 said:
I will try to use the method post the link that hit me.
To install the RUU, so I place on the SD card, then reboot in bootloader mode. Checking the UCP does well. After restarting been installed, my M8 and the logo HTC me a message saying "DEVICE IS NOT MATCHED TREE" appears. Subsequently, remains frozen for a few seconds, another HTC logo appears and from there start setting up my M8. But the other problem I have is that no network signal. Rarely it takes and is too unstable.
I could not fastboot flash ROMs because you do not connect with my M8 for flashing ZIP. He tells me "ERROR: CAN NOT LOAD firmware.zip"
Galaxy S5 had before. A few days ago I permuté HTC ONE M8 this coming with S-OFF, CID 11111111 and Boot LOCKED.
Click to expand...
Click to collapse
confirm whether your imei number on sim tray & imei given by system match. if you can, check your imei through an imei data server to find whether your imei is valid or invalid.
i think, there maybe a connection between your imei & no signal problem. however it is better to return your device to seller.
If you buy m8 again, concern whether it is M8_UL PVT
good luck!
umesh.lk said:
confirm whether your imei number on sim tray & imei given by system match. if you can, check your imei through an imei data server to find whether your imei is valid or invalid.
i think, there maybe a connection between your imei & no signal problem. however it is better to return your device to seller.
If you buy m8 again, concern whether it is M8_UL PVT
good luck!
Click to expand...
Click to collapse
Hi. I solved the problem of flashing zip. The unlock_code file was wrong. I went back to get it from HTCDev and resolved. I have my M8 with root, recovery and rom viper 6.0.0. The theme of the signal is much better, although still only 2g, but I read somewhere that you have to open the band to work on 3G and 4G of my country. I hope that solved my problem of signal, but even I notice appears on the screen every time I turn HTC along with the message "DEVICE IS NOT MATCHED TREE". I do not know why that warning. [emoji45]
Enviado desde mi HUAWEI GRA-L09 mediante Tapatalk
Hey, guys. I bought a used M8 with bootloop issues hoping to fix it, the first part was simple as I unlocked the Bootloader through HTCDev, then installed the latest TWRP 3.1.1 and installed a ROM in it. After doing this process I found myself with no SIM detected. After some reboots the phone finally got the SIM going well but right after the next reboot (due to no charge left) the SIM wasn't detected again, only got detected after another series of reboots.
Every ROM I tested did not solve this problem, installed ViperOne M8, S.Team S5.2 and JW7.5, DarkNess reDefined 7.1.2, right now Im on ICE. Tried wiping the usual to intall a ROM and wiping DALVIK/ART cache, Cache, System, Data, Internal Storage. Also tried to put it back to stock using TWRP backup but the TWRP didn't see the file.
Does anyone know how to solve it? Below is my getvar all
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.24_2G
version-cpld: None
version-microp: None
version-main: 6.20.709.2
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__621
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 205bdca3
hbootpreupdate: 11
gencheckpt: 0
Since you received the phone this way, I suspect the SIM tray may be physically damaged. I don't see anything you did (unlock bootloader, custom recovery, custom ROMs) that would affect the functionality of the SIM, and your firmware looks up-to-date.
Well, since it already worked with me I think that should be software. About an hour ago I installed Lineage 15 and SIM is working, let's see if it keeps this way.