I am looking to go back to the HTC stock ROM on my HTC One X (North America Version). Here is the information about my device:
C:\Users\Niket\Desktop>cd C:\Android
C:\Android>fastboot getvar all
< waiting for device >
(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: HT287W302376
(bootloader) imei: 359691045845263
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3928mV
(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.067s
Can anyone help me put this back to the stock ROM? I unfortunately don't have a Nandroid backup... Please helps guys!
Scozzar said:
You would have to run the 3.18 RUU. That will restore your phone back to stock. Recovery will be erased and returned to stock as well. However, security status and unlocked bootloader will not change
Click to expand...
Click to collapse
Could you provide the exact steps for that? Where to find the RUU and how to go about putting it back to my phone. Thanks for your help
Scozzar said:
You would have to run the 3.18 RUU. That will restore your phone back to stock. Recovery will be erased and returned to stock as well. However, security status and unlocked bootloader will not change
Click to expand...
Click to collapse
Wait. Before he runs an RUU he need to get s-off or he could brick.
Sent from my Evita
---------- Post added at 07:13 AM ---------- Previous post was at 07:09 AM ----------
npat09 said:
Could you provide the exact steps for that? Where to find the RUU and how to go about putting it back to my phone. Thanks for your help
Click to expand...
Click to collapse
You need to get s-off first or you'll brick. Go here and follow the instructions. Only after you've done that and you definitely have s-off you can RUU.
You'll find the 3.18 RUU here. All you do is put your phone in fastboot mode, connect it to your pc, and run the RUU program. Make sure screen saver/hibernation is turned off, and make sure no other programs are running.
Are you wanting to go back to stock because you're selling the phone? If so, there are extra steps to do after this.
Sent from my Evita
timmaaa said:
Wait. Before he runs an RUU he need to get s-off or he could brick.
Sent from my Evita
---------- Post added at 07:13 AM ---------- Previous post was at 07:09 AM ----------
You need to get s-off first or you'll brick. Go here and follow the instructions. Only after you've done that and you definitely have s-off you can RUU.
You'll find the 3.18 RUU here. All you do is put your phone in fastboot mode, connect it to your pc, and run the RUU program. Make sure screen saver/hibernation is turned off, and make sure no other programs are running.
Are you wanting to go back to stock because you're selling the phone? If so, there are extra steps to do after this.
Sent from my Evita
Click to expand...
Click to collapse
I can't seem to get an S-off. At the very last step it keeps saying "permission denied" What should i do?
What ROM are you on?
Sent from my Evita
timmaaa said:
What ROM are you on?
Sent from my Evita
Click to expand...
Click to collapse
CyanogemMod 10.1
npat09 said:
CyanogemMod 10.1
Click to expand...
Click to collapse
you have to give adb root access in developer options.
Before giving the adb commands you need to give root access to adb in developer settings.
Sent from my Evita
Thanks guys for all your help, I was able to get it to the stock rom and make use of the warranty again!
Related
So i'm new here and was messing around with the phone and exploring the different things I can do with this phone.
I want to go back to stock ROM, my problem is that I do not know my original cid before I rooted it. Is this a problem here is my main-ver information
(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: XXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4145mV
(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
I apologize greatly if I can not find this anywhere on the forums. I have access to a Linux box if that helps. I am trying to just get back to at&t bloatware rom.
You could just get s-off so then you can run an RUU without worrying. S-off thread is here.
Sent from my Evita
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
Or you could just flash a stock ROM from the Android Development section.
Sent from my Evita
I found my RUU and got the Rom_01.zip and Rom_02.zip
Rom_02.zip - SFX ZIP archive, unpacked size 1,680,452,716 bytes
that file has boot in there and recovery could I just flash that zip and be ok?
timmaaa said:
You could just get s-off so then you can run an RUU without worrying. S-off thread is here.
Sent from my Evita
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
Or you could just flash a stock ROM from the Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
How did you retrieve those zips from an RUU? An RUU is an exe file.
And why did you even do that? I gave you the options you should try.
Sent from my Evita
scrizo said:
I found my RUU and got the Rom_01.zip and Rom_02.zip
Rom_02.zip - SFX ZIP archive, unpacked size 1,680,452,716 bytes
that file has boot in there and recovery could I just flash that zip and be ok?
Click to expand...
Click to collapse
I would NOT mess with it. Both the Jellybean RUU and OTA will brick the phone, so its not exclusive to the RUU, and running the extracted file may still brick you.
The consequences are catastrophic (a true brick, only fixable by JTAG), so its not worth the risk when easy and low risk options exist. Either just S-off (as previously suggested) or another option is to change the CID back to your proper carriers ID.
I unencrypted them and extracted them. In regards to S-off I believe I have it except my phone won't run the SuperSU.zip file, I have Tampered and Unlocked on my bootloader screen.
timmaaa said:
How did you retrieve those zips from an RUU? An RUU is an exe file.
And why did you even do that? I gave you the options you should try.
Sent from my Evita
Click to expand...
Click to collapse
If you have s-off it will say so in your bootloader.
Sent from my Evita
Ok looking now. Will let you know.
timmaaa said:
If you have s-off it will say so in your bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Followed steps and now have S-OFF !
timmaaa said:
If you have s-off it will say so in your bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Ok, now you can run an RUU to get back to stock. Don't mess with it though, just run the exe program.
Sent from my Evita
Successfully installed ViperXL ROM
Having problems getting the latest firmware/ hboot installed on my att htc one xl. I did try turges but would not take the zip file. So instead i used carls zip through twrp and this is what i found out. Im currently running turges viperxl 4.2.0 with elementalx 8.3.2 kernal installed.
my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
let me know what i need to do and what i did wrong. Thanks for the help appreciate you guys!
I have some questions about this too , I running cleanrom , if I flash turge 's firmware ,that's the tmobile version right , is there any way to revert back to the att version( 3.18 hboot 2.14, my current) to return to stock
Sent from my HTC One XL using xda app-developers app
mrmcshagbag said:
Having problems getting the latest firmware/ hboot installed on my att htc one xl. I did try turges but would not take the zip file. So instead i used carls zip through twrp and this is what i found out. Im currently running turges viperxl 4.2.0 with elementalx 8.3.2 kernal installed.
my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
let me know what i need to do and what i did wrong. Thanks for the help appreciate you guys!
Click to expand...
Click to collapse
Did you flash Turge's firmware twice as per the instructions?
Sent from my Evita
---------- Post added at 01:30 PM ---------- Previous post was at 01:29 PM ----------
kevintran.98 said:
I have some questions about this too , I running cleanrom , if I flash turge 's firmware ,that's the tmobile version right , is there any way to revert back to the att version( 3.18 hboot 2.14, my current) to return to stock
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I answered your question in the CR thread.
PS. Duplicate posts aren't allowed.
Sent from my Evita
mrmcshagbag said:
my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
let me know what i need to do and what i did wrong. Thanks for the help appreciate you guys!
Click to expand...
Click to collapse
The radio was updated, but hboot did not. My guess, is that you did not pick the option in AROMA to update hboot. You can just flash again, and pick the option to flash hboot.
---------- Post added at 11:58 AM ---------- Previous post was at 11:54 AM ----------
kevintran.98 said:
I have some questions about this too , I running cleanrom , if I flash turge 's firmware ,that's the tmobile version right , is there any way to revert back to the att version( 3.18 hboot 2.14, my current) to return to stock
Click to expand...
Click to collapse
Yes, you can always revert hboot with s-off (which is required to run Turge's firmware update, anyway).
But unless you want to run an AOSP ROM that does not support hboot 2.15, there shouldn't be any reason to revert hboot.
redpoint73 said:
The radio was updated, but hboot did not. My guess, is that you did not pick the option in AROMA to update hboot. You can just flash again, and pick the option to flash hboot.
---------- Post added at 11:58 AM ---------- Previous post was at 11:54 AM ----------
Yes, you can always revert hboot with s-off (which is required to run Turge's firmware update, anyway).
But unless you want to run an AOSP ROM that does not support hboot 2.15, there shouldn't be any reason to revert hboot.
Click to expand...
Click to collapse
Thanks for the info. Turges zip wouldn't flash at all for me tried 20 times. So i got carls twrp zip and it worked installed all but the kernal for fw update since im running elementalx on my viperxl rom. it updated everything but htboot. will this be a problem since im on an att phone or will this be okay.. also reflashed carls same as above still on 2.14 hboot.
mrmcshagbag said:
it updated everything but htboot. will this be a problem since im on an att phone or will this be okay.. also reflashed carls same as above still on 2.14 hboot.
Click to expand...
Click to collapse
Maybe, maybe not. Are you getting any signal issues or random reboots? If not, then the radio and other modules alone may have taken care of this. Or if you never had these problems to begin with, it might just not apply to you (not everyone gets these issues).
Being AT&T doesn't have any effect on what hboot you should have (2.14 versus 2.15). 2.15 is not even an official hboot version for AT&T yet anyway (might be once they release Sense 5 officially, or they might get their own hboot version).
I don't foresee to many problems being on hboot 2.14, as long as your phone is operating correctly. The only thing I can think of, is if AOSP devs decide in the future they want to force everyone to hboot 2.15 like they did with 2.14. If that happens, you won't be able to flash those ROMs, or you would have to find some way to upgrade hboot.
redpoint73 said:
Maybe, maybe not. Are you getting any signal issues or random reboots? If not, then the radio and other modules alone may have taken care of this. Or if you never had these problems to begin with, it might just not apply to you (not everyone gets these issues).
Being AT&T doesn't have any effect on what hboot you should have (2.14 versus 2.15). 2.15 is not even an official hboot version for AT&T yet anyway (might be once they release Sense 5 officially, or they might get their own hboot version).
I don't foresee to many problems being on hboot 2.14, as long as your phone is operating correctly. The only thing I can think of, is if AOSP devs decide in the future they want to force everyone to hboot 2.15 like they did with 2.14. If that happens, you won't be able to flash those ROMs, or you would have to find some way to upgrade hboot.
Click to expand...
Click to collapse
I see. Yeah i had to flash the 3.18 radio and wifi partitions back because carls was giving me problems. i only seem to get reboots during music playback with screen off via htc music.
I'm trying to get my father's phone ruu'ed to 3.14 tmo.
I rooted his phone and unlocked through htc dev a long time ago.
He is currently running cm10 w/ hboot 1.09 and radio 0.16.31501s.
S-on w/ tmo CID.
I used faceplam S-off on my phone and lost 3g/4g. I do not want this to happen to his phone.
So what I'am asking is what do i have to do to get his tmo HTC ONE S safely onto the JB 3.14 from htc/tmo?
When i try to ruu using the 3.14 i get ERROR [159]: IMAGE ERROR. It says i have the wrong image and to download the correct one. Its the same one i used on my phone repeatably.
Any help would be great. Really afraid of borking his phone.
after some googling. I found that the ruu has to match the hboot and be re-locked. Some one also suggested flashing a stock zip and stock recovery. However i cant find a stock rom zip for 1.53. So i just tried re-locking and ruu'ing, but now i get ERROR 155.
Any help would be great. Again i can't s-off for fear of being stuck on edge like my phone
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_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: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4132mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
billydroid said:
after some googling. I found that the ruu has to match the hboot and be re-locked. Some one also suggested flashing a stock zip and stock recovery. However i cant find a stock rom zip for 1.53. So i just tried re-locking and ruu'ing, but now i get ERROR 155.
Any help would be great. Again i can't s-off for fear of being stuck on edge like my phone
Click to expand...
Click to collapse
tmobile U.S.
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
to relock
while phone is in bootloader >fastboot USB
fastboot folder, shift right click open command window
from command window type
fastboot oem lock
(also heard but haven't tried because I'm S-Off that you can run RUU.exe from fastboot USB without relocking bootloader)
Edit: to answer the bootloader question. Yes you can ruu a different hboot as long as it is a higher hboot. (s-off no matter)
I got it. I had to re-lock and run ruu 1.84 rc2 first. Then it let me ruu 3.14.
Sent from my HTC VLE_U using Tapatalk
I have my Sprint HTC One e8 set up with TWRP and it is rooted.
It is still set to S-On (firewater failed saying that HTC patched the vulnerability).
So far, I have only used TWRP to backup: boot, data, and system.
How would I go about getting the device back to its original state?
I am on a Mac and have ADB installed.
I may have found this file online: 0PAJIMG_M8_ACE_WHL_K44_SENSE60_Sprint_WWE_1.12.651.1_Radio_1.08.20.0707_2_NV_SPCS_2.30_003_release_384985_signed_2.zip
*** CORRUPT FILE - DO NOT USE ***
But, if it is possible to reset the phone using the files that TWRP has access to on the phone?
My goal is to restore this phone to its original state if possible.
You dont need to restore any file,you need to connect phone in fastboot mode and to type fastboot oem lock or something like that i am not sure i am writi g from my phone and i am not at home.
Sent from my HTC One_E8 using XDA Premium 4 mobile app
But, will that remove TWRP and remove the TAMPERED tag?
addy18 said:
You dont need to restore any file,you need to connect phone in fastboot mode and to type fastboot oem lock or something like that i am not sure i am writi g from my phone and i am not at home.
Click to expand...
Click to collapse
Nope, that simple re-locks the phone.
I was to restore it to how it was before rooting.
No root, nothing, just the original software.
I think you need to get S-OFF to do that, and Google kinda agrees.
Any thoughts on how to do that without Firewater?
crystal_ball said:
I think you need to get S-OFF to do that, and Google kinda agrees.
Click to expand...
Click to collapse
As far as I know the only other option is paying $25 for SunShine.
somebody tried firewater metod for s-off? i read on google it doing almost all htc models but i cant try yet i need first to restore stock ruu
I tried it. Firewater reports back that HTC patched the vulnerability. I am wondering if HTC pushed the patch in a way that I can revert it and then use Firewater.
Someone on another forum suggested that if I flash the ROM to CM11 that I might be able to use Firewater over that to get S-OFF. But, I don't think that CM11 is compatible with the E8 yet. Am I wrong about that?
addy18 said:
somebody tried firewater metod for s-off? i read on google it doing almost all htc models but i cant try yet i need first to restore stock ruu
Click to expand...
Click to collapse
CM11 reports that the device is "Unsupported".
So, regardless of its similarities to the M8, rooting an E8 still doesn't let you do much...
crystal_ball said:
As far as I know the only other option is paying $25 for SunShine.
Click to expand...
Click to collapse
The guys at Sunshine are wonderful. Incredible support via their IRC channel. Totally worth the $25.
StevenJayCohen said:
The guys at Sunshine are wonderful. Incredible support via their IRC channel. Totally worth the $25.
Click to expand...
Click to collapse
Hi,
Could you share fastboot getvar all for HTC E8 Sprint?
Thanks!
> fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.08.20.0707_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXX
(bootloader) imei: XXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXX
(bootloader) product: mec_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ50000
(bootloader) cidnum: SPCS_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: 36899d18
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Hi, would the RUU below work on HTC One M8Sw S-offed and superCIDed?
0PAJIMG_M8_ACE_WHL_K44_SENSE60_Sprint_WWE_1.12.651 .1_Radio_1.08.20.0707_2_NV_SPCS_2.30_003_release_3 84985_signed_2.zip
I'm trying to get rid of the Chinese stock rom and replace it by WWE stock with OTA available.
Thanks
Vendestkirox said:
Hi, would the RUU below work on HTC One M8Sw S-offed and superCIDed?
0PAJIMG_M8_ACE_WHL_K44_SENSE60_Sprint_WWE_1.12.651 .1_Radio_1.08.20.0707_2_NV_SPCS_2.30_003_release_3 84985_signed_2.zip
I'm trying to get rid of the Chinese stock rom and replace it by WWE stock with OTA available.
Thanks
Click to expand...
Click to collapse
Think you can't flashed it. The RUU is for Sprint network which is CDMA and single SIM. Your phone should be GSM and dual SIM. Better do not to try
Make sense.. thanks for the reply
Guess I'll have to wait for the E8 dual SIM to be released in Europe in order to get official RUU
Sent from my HTC M8Sw using XDA Free mobile app
Possibility is using India RUU. But never find this RUU available yet.
Technically if we have India RUU we can change CID and MID by scoopy method then you can flash India RUU on your M8sw. I have ask scoopy to work on it.
---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------
StevenJayCohen said:
> fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.08.20.0707_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXX
(bootloader) imei: XXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXX
(bootloader) product: mec_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ50000
(bootloader) cidnum: SPCS_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: 36899d18
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Click to expand...
Click to collapse
Hi Steven,
Thanks.
Could you share mmcblk0p2 and mmcblk0p5 from your Sprint HTC One E8?
Thanks.
ian.anindya said:
Possibility is using India RUU. But never find this RUU available yet.
Technically if we have India RUU we can change CID and MID by scoopy method then you can flash India RUU on your M8sw. I have ask scoopy to work on it.
If I'm not wrong, India RUU is built for CDMA while China Unicom is WCDMA/GSM.
1) Would flashing that rom prevent the sim card to work?
2) Does India RUU comes with as much bloatware as China RUU and Indian based language Blinkfeed as well?
Thanks for your time
Click to expand...
Click to collapse
ian.anindya said:
Possibility is using India RUU. But never find this RUU available yet.
Technically if we have India RUU we can change CID and MID by scoopy method then you can flash India RUU on your M8sw. I have ask scoopy to work on it.
---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------
Hi Steven,
Thanks.
Could you share mmcblk0p2 and mmcblk0p5 from your Sprint HTC One E8?
Thanks.
Click to expand...
Click to collapse
Could you please share scoopy method link?
Still work on progress will be posting soon.
We need dump partition mmcblk0p2, p3, p5, p6 and p34
If you can pull out from your phone please upload and pm me link togather with data fastboot getvar all.
I'm really in need of help here
so first some background, i have a verizon htc one m8 being used on a gsm carrier outside of the us..i had the latest digital high rom running with his 5.0 firmware and supercid as well as googleplay MID
today i tried to flash the latest GPE firmware 5.0.1 and after a sucessfull flash the phone went back to the bootloader screen but this time its black and not white as before and for some reason it deleted my os and partitions..now i am stuck in bootloader and even tho i am able to flash twrp recovery each time i install a rom via RUU (in this case stock gpe rom since i changed the phone to gpe) it will not boot into the rom..ive tried and searched all day but cant find anything that helps
i tried flashing digital highs's firmware again but it does not change/overwrite the gpe firmware
and i am unable to flash a stock verizon RUU because the MID has changed..
BTW my sdcard slot does not work
C:\android-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT43XSF01633
(bootloader) imei: 990004998541332
(bootloader) imei2: Not Support
(bootloader) meid: 99000499854133
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.029s
kooliebwoy said:
I'm really in need of help here
so first some background, i have a verizon htc one m8 being used on a gsm carrier outside of the us..i had the latest digital high rom running with his 5.0 firmware and supercid as well as googleplay MID
today i tried to flash the latest GPE firmware 5.0.1 and after a sucessfull flash the phone went back to the bootloader screen but this time its black and not white as before and for some reason it deleted my os and partitions..now i am stuck in bootloader and even tho i am able to flash twrp recovery each time i install a rom via RUU (in this case stock gpe rom since i changed the phone to gpe) it will not boot into the rom..ive tried and searched all day but cant find anything that helps
i tried flashing digital highs's firmware again but it does not change/overwrite the gpe firmware
and i am unable to flash a stock verizon RUU because the MID has changed..
BTW my sdcard slot does not work
C:\android-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT43XSF01633
(bootloader) imei: 990004998541332
(bootloader) imei2: Not Support
(bootloader) meid: 99000499854133
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.029s
Click to expand...
Click to collapse
Pm me teamviewer info and I can help you.
---------- Post added at 05:50 PM ---------- Previous post was at 05:06 PM ----------
kooliebwoy said:
I'm really in need of help here
so first some background, i have a verizon htc one m8 being used on a gsm carrier outside of the us..i had the latest digital high rom running with his 5.0 firmware and supercid as well as googleplay MID
today i tried to flash the latest GPE firmware 5.0.1 and after a sucessfull flash the phone went back to the bootloader screen but this time its black and not white as before and for some reason it deleted my os and partitions..now i am stuck in bootloader and even tho i am able to flash twrp recovery each time i install a rom via RUU (in this case stock gpe rom since i changed the phone to gpe) it will not boot into the rom..ive tried and searched all day but cant find anything that helps
i tried flashing digital highs's firmware again but it does not change/overwrite the gpe firmware
and i am unable to flash a stock verizon RUU because the MID has changed..
BTW my sdcard slot does not work
C:\android-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT43XSF01633
(bootloader) imei: 990004998541332
(bootloader) imei2: Not Support
(bootloader) meid: 99000499854133
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.029s
Click to expand...
Click to collapse
And don't do anything else in the meantime to it.
dottat said:
Pm me teamviewer info and I can help you.
---------- Post added at 05:50 PM ---------- Previous post was at 05:06 PM ----------
And don't do anything else in the meantime to it.
Click to expand...
Click to collapse
thanks alot for the response..It looks like i have found a solution....
it seems that the hboot got updated which caused the problem i downloaded firewaters hboot and flashed it which allowed me to sideload dh custom rom and with that as soon as i got into the rom i changed back to VZW official 4.4.4 firmware to get the latest compatible hboot and then did another flash of dh's custom 5.0 firmware and finally reflashed the OS with my prefered settings and im currently updating all my apps..so far the device functions fine
I hope this helps someone else who may get into this dilemma..
kooliebwoy said:
thanks alot for the response..It looks like i have found a solution....
it seems that the hboot got updated which caused the problem i downloaded firewaters hboot and flashed it which allowed me to sideload dh custom rom and with that as soon as i got into the rom i changed back to VZW official 4.4.4 firmware to get the latest compatible hboot and then did another flash of dh's custom 5.0 firmware and finally reflashed the OS with my prefered settings and im currently updating all my apps..so far the device functions fine
I hope this helps someone else who may get into this dilemma..
Click to expand...
Click to collapse
helped me ty
Same issue with my m8 whl
kooliebwoy said:
thanks alot for the response..It looks like i have found a solution....
it seems that the hboot got updated which caused the problem i downloaded firewaters hboot and flashed it which allowed me to sideload dh custom rom and with that as soon as i got into the rom i changed back to VZW official 4.4.4 firmware to get the latest compatible hboot and then did another flash of dh's custom 5.0 firmware and finally reflashed the OS with my prefered settings and im currently updating all my apps..so far the device functions fine
I hope this helps someone else who may get into this dilemma..
Click to expand...
Click to collapse
hi i have an htc one m8_whl(sprint unlocked gsm bought from aliexpress refurbished). S-off Unlocked boot loader, Rooted. it was on 4.4.2 i tried to flash this rom using adbRUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip(from graffixnyc ). i had installed twrp custom recovery before. now when i flashed this rom after i rebooted its just stuck at boot loader page. i can go to recovery options and i did sideload this rom again but it didn't work. same stuck at boot loader page. please help me with this situation. i really wanna install GPE rom on my phone.
ksingh007 said:
hi i have an htc one m8_whl(sprint unlocked gsm bought from aliexpress refurbished). S-off Unlocked boot loader, Rooted. it was on 4.4.2 i tried to flash this rom using adbRUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip(from graffixnyc ). i had installed twrp custom recovery before. now when i flashed this rom after i rebooted its just stuck at boot loader page. i can go to recovery options and i did sideload this rom again but it didn't work. same stuck at boot loader page. please help me with this situation. i really wanna install GPE rom on my phone.
Click to expand...
Click to collapse
sprint isnt a gsm native phone. You are in the verizon section and likely will have more luck in either the regular M8 section and likely less luck in the sprint section. You will have no luck here.....
Need Help plz
dottat said:
Pm me teamviewer info and I can help you.
---------- Post added at 05:50 PM ---------- Previous post was at 05:06 PM ----------
And don't do anything else in the meantime to it.
Click to expand...
Click to collapse
Hello plz help me out my htc m8 just got dead, i was going back to stock with ARU wizard after 80% phone got stuck and now dead tried all methods volume+power buttons but no luck so plz help me
ok_then_so said:
Hello plz help me out my htc m8 just got dead, i was going back to stock with ARU wizard after 80% phone got stuck and now dead tried all methods volume+power buttons but no luck so plz help me
Click to expand...
Click to collapse
Is your battery dead?
Sent from my HTC6535LVW using Tapatalk
dottat said:
Pm me teamviewer info and I can help you.
---------- Post added at 05:50 PM ---------- Previous post was at 05:06 PM ----------
And don't do anything else in the meantime to it.
Click to expand...
Click to collapse
I need HTC Desire 620G dual sim stock rom. Can you please help me sir.
punkshamil said:
I need HTC Desire 620G dual sim stock rom. Can you please help me sir.
Click to expand...
Click to collapse
No.
Sent from my XT1575 using Tapatalk