Pretty sure I effed up... Before reading further please know I am a very novice Android user, but am great at following directions.
In an attempt to install a custom ROM on my phone I'm having some serious issues getting it to work. I was able to unlock the bootloader on my device quite easily but after attempting to install TWRP the device boots to a black screen when trying to load the recovery. I know the phone is on because I have to press and hold power for a while before I can get back into the actual system. I figured I'd try installing CWM but it does the same thing. I installed the ROM Manager app as suggested by another site but it really is of no help to me without my phone being rooted, which it is not... yet. The app does show that both TWRP and CWM are installed but gets an error flashing CWM and if i try to set it to use the outdated version of CWM or TWRP it says that it's configured to use the existing recovery installation and makes no difference trying to load the recovery.
Phone info: (Let me know if you need anything not listed.)
Android Version: 4.1.1
HTC Sense: 4+
Software#: 3.17.631.3
HTC SDK API leve: 4.63
Build#: 3.17.631.3
Kernel version: 3.4.0-g240d4d5
I'm at a loss for what to do to either get a working custom recovery or restore the factory one to working condition, which I can't seem to find online anywhere.
Edit: Grammar.
Edit2: Update - I was able to get TWRP to run and then attempted to install CyanogenMod, when it installs it says MD5 file not found but says successfully installed. After rebooting to system it just gets stuck in an endless reboot cycle. Ideas / Suggestions?
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
nogotaclue said:
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
Click to expand...
Click to collapse
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
13rennon said:
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
Click to expand...
Click to collapse
Reported and will be moved
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
audit13 said:
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
Click to expand...
Click to collapse
Yes I was doing a full wipe before flashing, but not after. Situation has changed a bit though... I was working with someone via reddit (Full thread here: reddit.com/r/root/comments/3a4cc2/htc_one_x_root_for_beginner/ ) Long story short: Finally got CyanogenMod installed but let it sit over an hour and just stuck on spinning CM logo. Forced shutdown, booted into TWRP and wouldn't recognize SD or mount (eMMC). Read this can be due to not doing a factory reset, tried to do the factory reset but same deal. Tried to ruin an RUU that matched my info but it failed and with a locked bootloader I cant even get into TWRP, I need to unlock the bootloader and reinstall TWRP after failing an RUU.
Phone details as requested:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.631.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
When I try to RUU I start by relocking the bootloader with "fastboot oem lock" and then I run "fastboot erase cache" then "fastboot oem rebootRUU" then "fastboot flash zip RUU.zip" when it's on the black screen with silver HTC logo. I get this:
c:\Android>fastboot flash zip RUU.zip
sending 'zip' (650005 KB)...
OKAY [ 25.324s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 97.643s
The RUU file I'm using is OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip I've read they can sometimes give odd errors so I ran it a second time as suggested, same error running a second time. If I try to boot after this it boots to the white HTC quietly brilliant screen.
I see you have s-on and you do not have super CID.
With s-on, I think you have to flash the boot.img file for the phone to boot.
Easiest way to solve the problem may be to get s-off and supercid.
This is what my Rogers HTC One X says:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.23a.32.09.29
version-cpld: None
version-microp: None
version-main: 3.17.707.1
version-misc: PVT SHIP S-OFF
serialno: HT
imei: 3596
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4081mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a0
hbootpreupdate: 11
gencheckpt: 0
all: Done!
Related
Right now I can not turn my phone on, it just gets stuck in the htc quietly brilliant "This build is for development purpses only" red text screen every time I reboot it.
I have TWRP v2.4.3.0 installed and working, bootload is unlocked, I don't know what to do next. Could anyone be kind enough to give me a clear set of instructions ("flash rom" isn't helping - would help a lot if you mentioned which rom and how to flash it and whether to reset factory settings/clear cache). all I want to do is to get past the htc quietly brilliant screen, no matter how. Help please.
Info about my phone below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.17.31501S.10_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:***************
(bootloader) imei: *********
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3774mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It's pretty easy. All you have to is to follow the instructions over here.
rootrider said:
It's pretty easy. All you have to is to follow the instructions over here.
Click to expand...
Click to collapse
I think the root of my problem may be finding a custom rom compatible with hboot 1.13..
Every rom i try to install fails (trickdroid, viperones), is there any way i can update hboot first?
rootrider said:
It's pretty easy. All you have to is to follow the instructions over here.
Click to expand...
Click to collapse
Helloooooo?
I'm stuck, it's not like I didn't try installing roms before.
They're failing because I have hboot 1.13 and I can't find ANY roms that are compatible with 1.13.
I also can't download an RUU, because no RUU is available for my carrier/version (CID: ROGERS001)
that link given is for the S3 variant
i can't tell by your specs--do you have an S3 as opposed to S4
i don't think Rogers would have S3, but not up to speed on that stuff
those roms are for the S4
i don't know why .13 is an issue
you don't give your specific flashing process for which rom
did you flash boot image an do all OP install instructions to include wiping system as part of wipe
i am calling it a nite, but we would need more specifics like i mentioned, unless rootrider gave you that link bc you are S3
rugmankc said:
that link given is for the S3 variant
i can't tell by your specs--do you have an S3 as opposed to S4
i don't think Rogers would have S3, but not up to speed on that stuff
those roms are for the S4
i don't know why .13 is an issue
you don't give your specific flashing process for which rom
did you flash boot image an do all OP install instructions to include wiping system as part of wipe
i am calling it a nite, but we would need more specifics like i mentioned, unless rootrider gave you that link bc you are S3
Click to expand...
Click to collapse
I'm S4, and I managed to fix it... never got viperones to work though, first i did the superCID process and downloaded a t-mobile ruu, and then tried to custom rom viperones which didn't work ended up working with aokp, so thanks anyways, how do I close this thread
Get different twrp. Many people have problems flashing roms with 2.4.3.0 version.
Sent from my HTC One S using xda app-developers app
Glad you got it. Mod may close it. Since you asked.
Okay so heres the deal. Bought a new evita from a dealer. Dont remember/have what the stock software was, but it was booting with an att rom and all the bloatware. I downloaded the all in one eztoolkit and unlocked the bootloader successfully. Heres my problem, I can get into fastboot and twrp, but all of my flashes fail regardless of what rom I flash. I tried cm 10.2, 10.4, and 11 beta and they all failed. Then I tried to revert using both att ruus I could find, including the 2.20 and 3.18 updates directly from att. Both of them reboot to the ruu loader and appear to be working, but fail citing the incorrect software version. I assume its because I manually changed the recovery and flashed boot.img files from each of the roms I tried to flash, but I am not certain. Heres is the getvar information:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 0.19as.32.09.11_
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.20.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24DW304126
(bootloader) imei: 359691042468010
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3897mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Can this be solved by flashing the correct rom, and if so can you direct me to it? Otherwise, how can I fix this?
Thank you.
edit: flashed cm 10.0.0 and related gapps after manually flashing the boot.img and I got it to boot.
Going to try to s-off so I can be done with all this garbage.
edit: Got it booting, got s-off. Still on 10.0.0 with root and s-off. Not sure where to go from here unless anyone can give me further direction. I'd prefer to have the latest cyanogen etc, but I am ok with this if I cant go any further.
Thanks all !
Where are you downloading your ROMs? You mentioned earlier that you flashed cm10.4 but there is no such ROM for this device. You need to be careful about where you get your ROMs, flashing a ROM that isn't intended for this device can easily result in a brick.
Your ROM flashes were failing because your firmware is too old, it does state pretty clearly in the install instructions on the cm threads that you need to update your firmware via the 3.18 RUU. So you need to download the 3.18 RUU and run that which will update your firmware. Here's a very useful thread which details how to run an RUU.
After you've done that you'll need to flash TWRP again. If you want to flash the latest cm, which is cm11, you need to install the modified version of TWRP 2.6.3.0 recovery which can be found in our Original Android Development section. Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter TWRP and flash your ROM + gapps. Because you're new here I'd suggest you click the Everything Evita link in my signature and bookmark it, it contains links to basically everything for our phone. You should also click the other links in my signature and read those threads, you'll find them very helpful. Here's a few important links for you too:
One XL Main Page
http://forum.xda-developers.com/forumdisplay.php?f=1538
One XL Q&A
http://forum.xda-developers.com/forumdisplay.php?f=1572
One XL Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1726
Make sure you only ever download ROMs from the development sections I've linked there, many people make the mistake of wandering into the HTC One X forum and flashing those ROMs, many of those people bricked their phone. That might seem confusing but you don't have the HTC One X (Endeavoru), you have the HTC One XL / at&t One X (Evita). If you have any further questions just ask either here or in my q&a thread (link in my signature).
Sent from my Evita
Hello Lads
Sorry to trouble you but ive read and read and tried and tried various options but no luck. I was up till two this morning and have been on this all day when I was supposed to be out with the wife. Shes not a happy bunny.
Got an HTC ONE S here on Vodafone, I can get into Bootloader and custom recovery twrp-2.7.1.0a-ville.img
but I cant load any image nothing, The phone wont boot and keeps restarting in a boot loop. I've tried various options and nothing.
I have reflashed stock recovery and tried to put a vodafone ruu on but I keep getting an error
htc android phone update rom utility 1.04 2011
error 140 bootloader version error
Click to expand...
Click to collapse
All I want to do is put a stock vodafone rom back on this phone but teh three ive tried give the same error
I thin I have to flash stock recovery
Then relock Bootloader through fastboot
Then run RUU while phone is in fastboot USB
Is this correct and can anyone point me to the correct RUU
details are
TAMPERED
UNLOCKED
VLE PVT SHIP ON RL
HBOOT -2 .15.0000
RADIO -1.15.50.05.29
OPENDSP - V31.1.0.45.0815
EMMC -BOOT
DEC 14 2012. 17:10:57-1
Click to expand...
Click to collapse
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23SW403509
(bootloader) imei: 359901041141397
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3944mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
C:\fastboot>
Click to expand...
Click to collapse
Thanks for taking the time to read this , hope someone can put me out of my misery.
mitch127 said:
Hello Lads
Sorry to trouble you but ive read and read and tried and tried various options but no luck. I was up till two this morning and have been on this all day when I was supposed to be out with the wife. Shes not a happy bunny.
Got an HTC ONE S here on Vodafone, I can get into Bootloader and custom recovery twrp-2.7.1.0a-ville.img
but I cant load any image nothing, The phone wont boot and keeps restarting in a boot loop. I've tried various options and nothing.
I have reflashed stock recovery and tried to put a vodafone ruu on but I keep getting an error
All I want to do is put a stock vodafone rom back on this phone but teh three ive tried give the same error
I thin I have to flash stock recovery
Then relock Bootloader through fastboot
Then run RUU while phone is in fastboot USB
Is this correct and can anyone point me to the correct RUU
details are
Thanks for taking the time to read this , hope someone can put me out of my misery.
Click to expand...
Click to collapse
Try getting the ICS RUU instead of straight up JB then from there update to JB. Worth a try, hope this helps!
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
YoungDev said:
Try getting the ICS RUU instead of straight up JB then from there update to JB. Worth a try, hope this helps!
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for replying to my question Pal.
I've managed to figure out how to unlock, root, get SuperCid, relock, get another unlock token and then eventually get S_ OFF,, which wouldn't work until I relocked then unlocked again with a new bin file.
Once I had done all this I re flashed a new twrp recovery, then flashed a new rom from recovery, then gapps.. Still cant the find a vodafone stock rom I was on but as I now have S Off I guess that doesnt matter and I can flash the european latest rom if i want to.
Thank you for taking the time to help me Mate, I am Grateful.
Im still on 1.15 radio and I think I will try to flash that next with the 1.20 or higher version to see if it helps with my phone signal which is not very good
Hello! Before you guys flame me with messages of how much dumb I am or anything similar - don't bother, i already know it and i regret it...
So... I have AT&T HTC One X, with Hboot 2.14, CID CWS__01 which i just destroyed as much as i could >.> Let me reproduce things i've tried..
First of i changed my CID to 11111111 and unlocked the bootloader - took me an hour, but i did it and it was working...
I've installed recovery, even rooted the ROM... But that wasn't enough - i wanted to install ParanoidAndroid ( and i didn't read that it needs S-OFF, realized that just after i installed it and rebooted the phone )..
So after a reboot, the white HTC logo it just went black screen and nothing else... So i've began to look up on forums if someone else had this kind of a problem...
Then i tried another 2 ROM's, which worked as well as PA - just black screen...
So i thought - maybe i'll do everything from scratch ? Why not, I changed CID back to stock, wiped everything etc. and locked the bootloader....
But now I've got a weird problem - i can't change CID with "fastboot oem writecid" - it returned me error
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.282s
Click to expand...
Click to collapse
So now i have no access to recovery, so i can't even do anything to the storage, the phone doesn't boot up, tried RUU for ATT version ( RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105 - i guess its for HBoot 1.44, not 2.14 >.> ) it just showed me an error that it couldn't send data to the phone and i should check my connection to the phone ( drivers are installed and working fine )
I've also tried fastbooting the OTA zip to the phone - well, the phone is on S-ON and it just declines any zip that i try to flash
Also i lost connection to ADB - its impossible to connect to it while phone is in bootloader, right? : /
So i'm left with empty phone without any rom, recovery - anything...
Is there any way of fixing it ? Its 5th hour where i just sit and try to look up for any information, but I just can't find anything...
I guess i just hard bricked the phone and i can try to play some volleyball with it >.>
Your mistake was thinking that you needed s-off to flash the ROM(s), you don't, all you needed to do was flash the boot.img via fastboot after flashing the ROM with your recovery. There's an Evita FAQ thread which contains this information stickied at the top of the q&a section you've posted this thread in . This is in no way intended to flame you, just show you the catalyst point for this mayhem.
Anyway, what is your current CID? Check it with this command:
Code:
fastboot oem readcid
You must be connected in fastboot mode (bootloader) in order for fastboot commands to work (and in answer to your question, no, adb does not work in fastboot mode, only in Android and in recovery).
Transmitted via Bacon
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT28GW304238
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3403mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Click to expand...
Click to collapse
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
prechcik said:
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
Click to expand...
Click to collapse
Glad to see you're all working now. But you need to edit your IMEI out of your post asap, never post your IMEI publicly.
Transmitted via Bacon
Hi,
A couple of weeks ago I got a new HTC One M8 Verizon from amazon. I bought it cause I wanted to covert it to GPE. After looking for some tutorials I decided to try the one described in this youtube video:
" How To: Convert HTC One M8 to Google Play Edition (5.0.1 Lollipop) with OTA Updates! " from MaowDroid - Since I'm a new user I can't post links, so I posted the video full name so you can look for it.
Later on I discovered I missed the " GSM Device (Not Sprint or Verizon) " legend in the video description. Very stupid of me! Anyway, everything went smooth until I flashed the image, then after restarting the device nothing happened and all I can do is to turn off the phone. If I choose HBOOT -> Recovery, the phone restarts. Same thing happens if I choose HBOOT -> Factory Reset.
Besides this video was not for my verizon device... I'm almost sure my second mistake was not to update the firmware before doing the whole process.. changing CID, ModelID and flashing the GPE image. I've been looking how to fix this but since I can't boot the OS I haven't been able to change the ModelID or CID, so whenever I've tried to flash a different image I get an error that says something about incorrect values, which from what I've learned in this process, its because those images are for different ModelID and CID values.
After that I asked for help in Android Forums ( http ://androidforums.com/threads/htc-one-m8-tried-to-convert-to-gpe-stuck-in-fastboot.931142/ ), where EarlyMon is being really nice and tried to help me resolve this issue. However it seems my problem is more difficult, so he suggested me to ask here so that we get more opinions to avoid making a fatal mistake. In summary, EarlyMon asked me to
1. flash recovery twrp-2.8.7.0-m8.img
2. Mount and Install ViperOneM8 4.3.0
Which I tried but at the end I get a Status 7 Error
-- Delete the spaces between "http:" and "//" --
http ://s13.postimg.org/4ktywhmzr/htconem8_Viper_One_M8_Error_Status7.jpg
Can you help me go to GPE or at least to Sense?
Any help will be really appreciated.
Thanks in advance.
PS.
This is my "fastboot getvar all" result and a picture of how fastboot looks when turning on or restarting the phone.
Code:
C:\Users\MIROSCAR\Desktop\HTC\miniadb_v1031>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.1700.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: eee2521c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Fastboot Image
-- Delete the spaces between "http:" and "//" --
http ://s24.postimg.org/ag2jj3jn9/htconem8fastboot.jpg
karlangazz said:
Hi,
A couple of weeks ago I got a new HTC One M8 Verizon from amazon. I bought it cause I wanted to covert it to GPE. After looking for some tutorials I decided to try the one described in this youtube video:
" How To: Convert HTC One M8 to Google Play Edition (5.0.1 Lollipop) with OTA Updates! " from MaowDroid - Since I'm a new user I can't post links, so I posted the video full name so you can look for it.
Later on I discovered I missed the " GSM Device (Not Sprint or Verizon) " legend in the video description. Very stupid of me! Anyway, everything went smooth until I flashed the image, then after restarting the device nothing happened and all I can do is to turn off the phone. If I choose HBOOT -> Recovery, the phone restarts. Same thing happens if I choose HBOOT -> Factory Reset.
Besides this video was not for my verizon device... I'm almost sure my second mistake was not to update the firmware before doing the whole process.. changing CID, ModelID and flashing the GPE image. I've been looking how to fix this but since I can't boot the OS I haven't been able to change the ModelID or CID, so whenever I've tried to flash a different image I get an error that says something about incorrect values, which from what I've learned in this process, its because those images are for different ModelID and CID values.
After that I asked for help in Android Forums ( http ://androidforums.com/threads/htc-one-m8-tried-to-convert-to-gpe-stuck-in-fastboot.931142/ ), where EarlyMon is being really nice and tried to help me resolve this issue. However it seems my problem is more difficult, so he suggested me to ask here so that we get more opinions to avoid making a fatal mistake. In summary, EarlyMon asked me to
1. flash recovery twrp-2.8.7.0-m8.img
2. Mount and Install ViperOneM8 4.3.0
Which I tried but at the end I get a Status 7 Error
-- Delete the spaces between "http:" and "//" --
http ://s13.postimg.org/4ktywhmzr/htconem8_Viper_One_M8_Error_Status7.jpg
Can you help me go to GPE or at least to Sense?
Any help will be really appreciated.
Thanks in advance.
PS.
This is my "fastboot getvar all" result and a picture of how fastboot looks when turning on or restarting the phone.
Code:
C:\Users\MIROSCAR\Desktop\HTC\miniadb_v1031>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.1700.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: eee2521c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Fastboot Image
-- Delete the spaces between "http:" and "//" --
http ://s24.postimg.org/ag2jj3jn9/htconem8fastboot.jpg
Click to expand...
Click to collapse
You can boot to hboot correct? First change CID back to Verizon, you can do this in hboot (bootloader)
fastboot devices (your device should be listed)
fastboot oem writecid VZW__001 (2 underscores)
fastboot reboot-bootloader
Then try flashing the Verizon RUU
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
andybones said:
You can boot to hboot correct? First change CID back to Verizon, you can do this in hboot (bootloader)
fastboot devices (your device should be listed)
fastboot oem writecid VZW__001 (2 underscores)
fastboot reboot-bootloader
Then try flashing the Verizon RUU
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Click to expand...
Click to collapse
Hi,
Ok, but, maybe a dumb question but which S-OFF RUU version should I use (4.4.4, 4.4.3, 4.4.2 ) ?
Thanks for your help man!
karlangazz said:
Hi,
Ok, but, maybe a dumb question but which S-OFF RUU version should I use (4.4.4, 4.4.3, 4.4.2 ) ?
Thanks for your help man!
Click to expand...
Click to collapse
I'd use the latest 5.0.1
andybones said:
I'd use the latest 5.0.1
Click to expand...
Click to collapse
Hi,
I just tried the 5.0.1 RUU.
First I changed the CID as instructed.
Then I renamed and copied the zip file to the SD as suggested in the ROM instructions.
Rebooted and choosed HBOOT, the ROM is detected but, after a few minutes I get a " Update Fail! " error.
https ://drive.google.com/file/d/0BwRKcAC_V-OscVVhMjdNbHUyRkk/view?usp=sharing
Am I doing something wrong?
karlangazz said:
Hi,
I just tried the 5.0.1 RUU.
First I changed the CID as instructed.
Then I renamed and copied the zip file to the SD as suggested in the ROM instructions.
Rebooted and choosed HBOOT, the ROM is detected but, after a few minutes I get a " Update Fail! " error.
https ://drive.google.com/file/d/0BwRKcAC_V-OscVVhMjdNbHUyRkk/view?usp=sharing
Am I doing something wrong?
Click to expand...
Click to collapse
Honestly not too sure, hopefully someone more information than myself can chime in. Keep in mind this is just what I'd do. Anything you choose to do with your device is your choice.
maybe try changing cid to supercid
i think supercid will fix it
---------- Post added at 05:32 PM ---------- Previous post was at 05:18 PM ----------
karlangazz said:
Hi,
I just tried the 5.0.1 RUU.
First I changed the CID as instructed.
Then I renamed and copied the zip file to the SD as suggested in the ROM instructions.
Rebooted and choosed HBOOT, the ROM is detected but, after a few minutes I get a " Update Fail! " error.
https ://drive.google.com/file/d/0BwRKcAC_V-OscVVhMjdNbHUyRkk/view?usp=sharing
Am I doing something wrong?
Click to expand...
Click to collapse
Yea try supercid, then ruu again
fastboot oem writecid 1111111
andybones said:
Honestly not too sure, hopefully someone more information than myself can chime in. Keep in mind this is just what I'd do. Anything you choose to do with your device is your choice.
maybe try changing cid to supercid
i think supercid will fix it
---------- Post added at 05:32 PM ---------- Previous post was at 05:18 PM ----------
Yea try supercid, then ruu again
fastboot oem writecid 1111111
Click to expand...
Click to collapse
Hi,
I just changed to superCID, I just looked it up somewhere else cause I think yours was missing a 1.
So I changed my CID to superCID,
Rebooted and selected HBOOT.
I got the same error.
https ://drive.google.com/file/d/0BwRKcAC_V-OsZDZpQW5TV1dIU0U/view?usp=sharing
Hoperfully someone else may have some other ideas.
Thanks a lot for your help man!
All your suggestions are welcomed!
karlangazz said:
Hi,
I just changed to superCID, I just looked it up somewhere else cause I think yours was missing a 1.
So I changed my CID to superCID,
Rebooted and selected HBOOT.
I got the same error.
https ://drive.google.com/file/d/0BwRKcAC_V-OsZDZpQW5TV1dIU0U/view?usp=sharing
Hoperfully someone else may have some other ideas.
Thanks a lot for your help man!
All your suggestions are welcomed!
Click to expand...
Click to collapse
Install team viewer and pm me the details with a good time to screen share and fix your phone.
Sent from my HTC6535LVW using Tapatalk
dottat said:
Install team viewer and pm me the details with a good time to screen share and fix your phone.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Thanks a lot for your help man!
The phone is now back to Sense and working!
I'll follow your advice and stick to ROMs no GPE!
Again, thank you very much for helping me save my device!
Regards!
karlangazz said:
Thanks a lot for your help man!
The phone is now back to Sense and working!
I'll follow your advice and stick to ROMs no GPE!
Again, thank you very much for helping me save my device!
Regards!
Click to expand...
Click to collapse
No problem man. Always glad to help!
Sent from my HTC6535LVW using Tapatalk
dottat said:
No problem man. Always glad to help!
Click to expand...
Click to collapse
Nicely done, magic.