Database Info

[Q] I need help please, completly lost....

Hi,
i've got a htc desire S and surprise, surprise i've run into another problem (most probably caused by me right now phone is in a state of "zombification" (freezes at boot screen, boots to hboot screen but loops back to hboot screen when choosing recovery or factory wipe)
I was running edymion v3.5 base release, with pdroid. but i noticed apps kept crashing/ force closing (facebook, default mail, youtube etc) bypassed most of these by reinstalling them or finding alternatives. few weeks later loads of the app started crashing, especially the camera (cashing limited to default and background apps). I decided that a reinstallation of endymion MIGHT fix this so i factory wiped using clockworkmod recovery and reflashed endymion + pdroid.
Alas, it froze on the HTC boot screen. this had happened before when i tried rooting and all..... so i did what i did before...http://forum.xda-developers.com/showthread.php?t=1728513
which failed cause the update kept stopping midway, so i pulled battery, and repeated a few times, tried using a RUU and a OTA
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
and
OTA_Saga_S_HTC_Europe_2.10.401.8-2.10.401.5_release_225212pe4gpljm46wwfk8i
these failed as well, either stopped halfway or completed then freeze on HTC boot screen.
Phone is s-off from revolutionary, no clockworkmod now (thanks to multiple wipes) and i dont think it is rooted anymore....
here is data that may help
fastboot screen
-revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4057mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Mar 10 2011, 14:58:38
please advice....
P.S. sry this was so lengthy, thought more details would help fix it quicker

is your device still recognized by adb? if YES then this should enable you flash a recovery through fastboot.
exert from 4ext touch thread which is what I'd recommend that you use.
Code:
There's a [URL="http://www.4ext.net/ddl/saga/recovery.zip"]direct download[/URL] for a version you can flash via fastboot.
Download this file
Unzip it
check md5sum of the included image file
attach device through USB to PC
flash through fastboot
Code:
fastboot flash recovery recovery.img
I'd then suggest a full wipe and attempt to include a custom ROM

ben_pyett said:
is your device still recognized by adb? if YES then this should enable you flash a recovery through fastboot.
exert from 4ext touch thread which is what I'd recommend that you use.
Code:
There's a [URL="http://www.4ext.net/ddl/saga/recovery.zip"]direct download[/URL] for a version you can flash via fastboot.
Download this file
Unzip it
check md5sum of the included image file
attach device through USB to PC
flash through fastboot
Code:
fastboot flash recovery recovery.img
I'd then suggest a full wipe and attempt to include a custom ROM
Click to expand...
Click to collapse
Thanks for replying, i was begining to lose hope
unfortunately it does not register with adb since it won't switch on. But it DOES register with fastboot, so i'm trying it right not. So far it has stopped moving at
c:\Users\ME\Desktop\adroid>fastboot flash recovery recovery.img
sending 'recovery' (6038 KB)...
OKAY [ 1.021s]
writing 'recovery'...
But i'll give it some time before trying again, will report back soon
update:
Soo, waited a while, then tried flashing again. stopped at the exact same spot (writing 'recovery')

If you manage to flash a recovery, search for guide to change your misc version. Then search for a guide to change your bootloader. There is one in my signature. Finally download a T-Mobile RUU since your phone is branded. Do not flash any other versions
Sent from my HTC Desire S using xda app-developers app

amidabuddha said:
If you manage to flash a recovery, search for guide to change your misc version. Then search for a guide to change your bootloader. There is one in my signature. Finally download a T-Mobile RUU since your phone is branded. Do not flash any other versions
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
thanks, can't seem to flash recovery though, stops and just stays at "writing recovery"

Getting stuck when trying to write one of the partitions is bad news.

Jack_R1 said:
Getting stuck when trying to write one of the partitions is bad news.
Click to expand...
Click to collapse
lol yea, i've pretty much given up. trying to find some one who can fix it, buti guess i'll have to wait to get a new phone

In which case, you surely have nothing to loose sending the dead device in for warranty fix, best leave the battery out.
Sywepd form my DsereiS

[Q] Newbie stuck , would love some help guys

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

Stock AT&T XL won't boot after factory reset

I'm not sure where to start. My brother handed me his phone after stupidly following a friend's suggestion that his phone would be faster if he did a factory reset. The phone displays the white screen with the HTC logo, then goes to a black screen and gets stuck there.
I'm able to get to fastboot, but I'm not really sure where to go from there.
The phone's never been tampered with before. S-ON, locked bootloader.
Here's the text I'm seeing on fastboot:
Code:
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012 <- I assume this date is because of the factory reset?
If I understood correctly from what I've been reading, I'm probably gonna need to reflash a stock ROM from fastboot through adb.
I got this HTC_One_X_RUU_5.18.502.1.exe from one of the threads. How do I extract the ROM from there?
I'd appreciate if anyone pointed me in the right way. I'm a Samsung guy and this phone is absolutely alien to me.
EDIT: Here's some more info I got from fastboot:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(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: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Here goes Serial#
(bootloader) imei: Here goes IMEI
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(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

How did he do the factory reset? Through recovery?
The symptoms you list are identical to what happens when flashing a new Rom without S-OFF.
My understanding is that due to write restrictions it can't copy the boot.img file to boot, which is required begin running the operating system.
I'm not sure if this is the case for factory resets though. So it may depend on how he tried to do the factory reset.
If the above situation is the case, then the fix is to flash the boot.img file of the same stock rom. Alternatively, you could flash a new rom and it's respective boot.img file.

He did that through fastboot. In fact he did the factory reset several times after the phone didn't boot.
I already tried flashing a boot.img from a ROM I found in the development section, but fastboot just says (remote:signature verify fail).
I have absolutely no freaking idea where to get that specific stock ROM. (It's 3.18.502.6, right?)
I added some extra info in the OP in case its useful.
EDIT: I downloaded the 3.18.502.6 OTA update, extracted the boot.img and the phone keeps spitting (remote:signature verify fail)

Since he flashed through recovery it may have screwed up because the bootloader is still locked (this may be the reason why you're getting errors too).
Unlocking the bootloader is what allows you to write to internal memory and is required to flash a rom.
I unlocked my bootloader using this nifty tool:
http://forum.xda-developers.com/showthread.php?t=2470972
This should then allow you to flash the boot.img file with the command
Code:
fastboot flash boot boot.img

I don't think flashing a boot.img is going to help. You're gonna need to run an RUU, either of these should be fine:
http://androidruu.com/getdownload.p..._10.130.32.34_release_signed_With_Partial.exe
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Transmitted via Bacon

Hey timmaaa, thanks for the help.
This phone is insufferable. Now I'm getting this:
Code:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip rom_02.zip
sending 'zip' (798796 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.007s
I actually managed to flash rom_01.zip and now I'm able to boot into recovery.
When I'm on recovery the log says:
Code:
Can not mount SD Card (No such file or directory)
What would you suggest I do next?

Why are you doing that though? That's not how you use an RUU, you're not meant to extract anything, it's an executable file so all you do is connect your phone in bootloader mode and run the program. Plus, who knows what's been done to the device at this point with all the mucking around that's happened with it, flashing just the ROM component won't achieve the desired result. You need to run the RUU as intended so it can update all aspects of the phone and bring everything back into line. There's a pretty good guide to using an RUU here:
Running a Rom Update Utility (RUU) on the HTC One XL Evita
Follow that guide exactly and your phone will hopefully be revived.

I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.

Mighty_Rearranger said:
I initially tried manually flashing thru fastboot because the RUU installer wasn't detecting the phone.
Turns out I didn't have the right drivers.
Thanks a bunch, man.
Click to expand...
Click to collapse
All good, is the phone booting now?
Transmitted via Bacon

Yup, it booted up alright. I think I'm gonna see how to install a custom recovery so I can fix it easier if he screws the phone up again.

Cool, I have detailed instructions for this device here:
http://forum.xda-developers.com/showthread.php?t=2593382

[Q] Rogers HTC One X help with customer recovery issue...

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!

Tried to convert to GPE, stuck in Fastboot

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.