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.
Related
hey guys my first thread, and ill be begging for help -_-
so i rooted my htc one s ville s4( model pj40110) and after that i tried flashing a custom rom, and i soft bricked it
now it only boots up to hboot, i tried installing custom recovery and installing other roms as it was rooted, but nothing worked
well i know how to revert it to stock, but i for got to get the S-On to S-Off and now i can't find the specific ruu for my device
looked for a week, now i resort to help
please kindly help me through this, its an emergency
im posting my getvar data here
C:\Users\Lance\Downloads\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT251W422764
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3977mV
(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.070s
my hboot is 2.15.0000
radio is 1.11.50.05.28
and if you need my version-main, every time i input fastboot getvar version-main, nothing shows,
it just shows version-main : (blank)
please guys do help me, its a friend's phone and he is leaving abroad in a few days
hogol said:
hey guys my first thread, and ill be begging for help -_-
so i rooted my htc one s ville s4( model pj40110) and after that i tried flashing a custom rom, and i soft bricked it
now it only boots up to hboot, i tried installing custom recovery and installing other roms as it was rooted, but nothing worked
well i know how to revert it to stock, but i for got to get the S-On to S-Off and now i can't find the specific ruu for my device
looked for a week, now i resort to help
please kindly help me through this, its an emergency
im posting my getvar data here
C:\Users\Lance\Downloads\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT251W422764
(bootloader) imei: 352103050279088
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3977mV
(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.070s
my hboot is 2.15.0000
radio is 1.11.50.05.28
and if you need my version-main, every time i input fastboot getvar version-main, nothing shows,
it just shows version-main : (blank)
please guys do help me, its a friend's phone and he is leaving abroad in a few days
Click to expand...
Click to collapse
First of all, remove serial number and imei.
There's no Jelly Bean RUU for Rogers instead you can download OTA.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
First of all, remove serial number and imei.
There's no Jelly Bean RUU for Rogers instead you can download OTA.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
first
i can't figure out how to edit my original post
second
i tried looking, i really am not sure which ota ruu i need, hence the thread
it would be kind of you to help me find it please :fingers-crossed:
hogol said:
first
i can't figure out how to edit my original post
second
i tried looking, i really am not sure which ota ruu i need, hence the thread
it would be kind of you to help me find it please :fingers-crossed:
Click to expand...
Click to collapse
- There's option at the bottom of your first post to Edit it. Your serial/IMEI can be used for dangerous purposes.
- Refer to This Post to find the correct OTA.zip.
- To install the OTA.zip, there are a few steps to be done. What was the last ROM you installed? Did you update to JellyBean via OTA?
use this guide http://forum.xda-developers.com/showthread.php?t=2394165
khan.orak said:
- There's option at the bottom of your first post to Edit it. Your serial/IMEI can be used for dangerous purposes.
- Refer to This Post to find the correct OTA.zip.
- To install the OTA.zip, there are a few steps to be done. What was the last ROM you installed? Did you update to JellyBean via OTA?
use this guide http://forum.xda-developers.com/showthread.php?t=2394165
Click to expand...
Click to collapse
The last rom i had was 4.1.1 stock, and currently i have no rom installed, where the entire problem started
can i flash an OTA on a phone which has no rom?
plus i have downloaded this
OTA_Ville_U_JB_45_S_Rogers_WWE_3.16.631.8_1.11.50.05.28_10.27.50.08L_release_301897nn5lu23br8cg9q7l.zip
but i don't know how to install a zip to a phone with no rom -_-
and there are many rogers ota/ruu available
which one is for my phone?
hogol said:
The last rom i had was 4.1.1 stock, and currently i have no rom installed, where the entire problem started
can i flash an OTA on a phone which has no rom?
plus i have downloaded this
OTA_Ville_U_JB_45_S_Rogers_WWE_3.16.631.8_1.11.50.05.28_10.27.50.08L_release_301897nn5lu23br8cg9q7l.zip
but i don't know how to install a zip to a phone with no rom -_-
and there are many rogers ota/ruu available
which one is for my phone?
Click to expand...
Click to collapse
I have given the Rogers OTA in the above list refer to that.
That's the core RUU you have downloaded
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
I have given the Rogers OTA in the above list refer to that.
That's the core RUU you have downloaded
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
so i install the core ruu then the ota?
or the ota then the ruu?
and which ota do i need?
quite a few....
sorry for all the noob questions, my first time working with a htc
hogol said:
so i install the core ruu then the ota?
or the ota then the ruu?
and which ota do i need?
quite a few....
sorry for all the noob questions, my first time working with a htc
Click to expand...
Click to collapse
Sorry for my weird typos. I was half asleep while I was typing that. I realized it now.
That's the correct OTA you download. It is in the form of a zip file correct?
You can flash that OTA with the help of the method stated in my signature
..
Edit:
Lol man I can't stop laughing at my typos. And the subsequent question asked by you hahaha
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
Sorry for my weird typos. I was half asleep while I was typing that. I realized it now.
That's the correct OTA you download. It is in the form of a zip file correct?
You can flash that OTA with the help of the method stated in my signature
..
Edit:
Lol man I can't stop laughing at my typos. And the subsequent question asked by you hahaha
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
well followed your tut through fully
and now after step 14, my phone wont boot, not at all
my phone had no OS installed, the recovery was stock
and i flashed the firmware.zip, now the phone wont even boot, and it my pc detects it as an alcatel device :|
i have no idea whats happening
hogol said:
well followed your tut through fully
and now after step 14, my phone wont boot, not at all
my phone had no OS installed, the recovery was stock
and i flashed the firmware.zip, now the phone wont even boot, and it my pc detects it as an alcatel device :|
i have no idea whats happening
Click to expand...
Click to collapse
Can you go into bootloader/fastboot?
Sent from my Nexus 7 using Tapatalk HD
many mpurnm
khan.orak said:
Can you go into bootloader/fastboot?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
nope, thats the problem
i would have continued following the tut if it booted into bootloader
its not responding at all :crying:
hogol said:
nope, thats the problem
i would have continued following the tut if it booted into bootloader
its not responding at all :crying:
Click to expand...
Click to collapse
no light blinks or anything?
Did you flash the firmware twice? at first it usually gives error.
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
hogol said:
nope, thats the problem
i would have continued following the tut if it booted into bootloader
its not responding at all :crying:
Click to expand...
Click to collapse
But this method has worked for many people. Two of them reported yesterday.
at 10th step I had already given that you shouldn't flash firmware if you had already updated to jellybean.
But I seriously am think what could have could have caused the brick as the OTA matches with your firmware.
Did you do SuperCID?
Try VolDown+Power Button to go into bootloader.
khan.orak said:
no light blinks or anything?
Did you flash the firmware twice? at first it usually gives error.
Click to expand...
Click to collapse
yes done it twice
thing is
after it said done in command prompt, the green progressbar wouldn't leave, i mean it was stuck at the green progress bar
the thing is, i waited for a while for it to finish, a lil bit was left at the end in the progressbar, but it said done in command prompt
so after a lot of waiting, i just hard reset it, but after that the phone is not booting into bootloader and not responding at all
what is happening?
khan.orak said:
no light blinks or anything?
Did you flash the firmware twice? at first it usually gives error.
---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------
But this method has worked for many people. Two of them reported yesterday.
at 10th step I had already given that you shouldn't flash firmware if you had already updated to jellybean.
But I seriously am think what could have could have caused the brick as the OTA matches with your firmware.
Did you do SuperCID?
Try VolDown+Power Button to go into bootloader.
Click to expand...
Click to collapse
i had jellybean 4.1.1 before but after rooting i tried installing a custom rom, but that failed and it left me with no OS on the phone at the end of it
hence i wanted to go back to stock
and no i didn't do superCID, dont even know what that is
hogol said:
i had jellybean 4.1.1 before but after rooting i tried installing a custom rom, but that failed and it left me with no OS on the phone at the end of it
hence i wanted to go back to stock
and no i didn't do superCID, dont even know what that is
Click to expand...
Click to collapse
Bro I can't find anything that you did incorrectly. I don't know what the problem is. But I think that incomplete firmware update bricked it.
khan.orak said:
Bro I can't find anything that you did incorrectly. I don't know what the problem is. But I think that incomplete firmware update bricked it.
Click to expand...
Click to collapse
but it said done in command prompt, and i waited for so long for it to finish, but it never finished
anything i can do to fix this??
hogol said:
but it said done in command prompt, and i waited for so long for it to finish, but it never finished
anything i can do to fix this??
Click to expand...
Click to collapse
Unless it turns on, there's nothing much we can do with it.
You can use this thread however http://forum.xda-developers.com/showthread.php?t=2116062
He unbricks HTC One S.
khan.orak said:
Unless it turns on, there's nothing much we can do with it.
You can use this thread however http://forum.xda-developers.com/showthread.php?t=2116062
He unbricks HTC One S.
Click to expand...
Click to collapse
cant believe this is happening to me
phone wont even respond to charging, absolutely nothing...
i dont know what to do now :crying:
ota/ruu
hogol said:
hey guys my first thread, and ill be begging for help -_-
so i rooted my htc one s ville s4( model pj40110) and after that i tried flashing a custom rom, and i soft bricked it
now it only boots up to hboot, i tried installing custom recovery and installing other roms as it was rooted, but nothing worked
well i know how to revert it to stock, but i for got to get the S-On to S-Off and now i can't find the specific ruu for my device
looked for a week, now i resort to help
please kindly help me through this, its an emergency
im posting my getvar data here
C:\Users\Lance\Downloads\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT251W422764
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3977mV
(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.070s
my hboot is 2.15.0000
radio is 1.11.50.05.28
and if you need my version-main, every time i input fastboot getvar version-main, nothing shows,
it just shows version-main : (blank)
please guys do help me, its a friend's phone and he is leaving abroad in a few days
Click to expand...
Click to collapse
this is where i found what vi needed http://androidruu.com/?developer=Ville
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
Hi,
I have a Verizon variant HTC One M8 that lost all cellular function after flashing a ROM. I was running DigitalHigh's GPE ROM and everything was perfectly fine until I flashed the 5.1 update. Ever since then I cannot make calls, send SMS, use data, and I get a no SIM card notification. It seems like I also lost IMEI, baseband, and other info from the about screen when the phone is booted, but this info is found when I use "fastboot getvar all." While the phone is booted I also get random reboots every few minutes or so.
I've tried various ROMs including previously working ones (such as the 5.0.1 version of DH's rom) and they do the same. I also tried to flash the 4.4.4 OTA update I have provided by my stock rom (which I've lost, unfortunately) but anytime I flash a stock recovery I get an annoying boot loop that is hard to get out of. I would attempt a RUU but I'm not sure if I should. I have a Verizon variant phone, but my carrier is not Verizon and my CID is a "rural version" that I do not see pop up very often: LRA_001. I usually run supercid though.
My fastboot getvar all results are below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.31.512.2
(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: 0P6B20000
(bootloader) cidnum: LRA__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: 2e9b7c51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope someone can help!
BaconBaconBacon said:
Hi,
I have a Verizon variant HTC One M8 that lost all cellular function after flashing a ROM. I was running DigitalHigh's GPE ROM and everything was perfectly fine until I flashed the 5.1 update. Ever since then I cannot make calls, send SMS, use data, and I get a no SIM card notification. It seems like I also lost IMEI, baseband, and other info from the about screen when the phone is booted, but this info is found when I use "fastboot getvar all." While the phone is booted I also get random reboots every few minutes or so.
I've tried various ROMs including previously working ones (such as the 5.0.1 version of DH's rom) and they do the same. I also tried to flash the 4.4.4 OTA update I have provided by my stock rom (which I've lost, unfortunately) but anytime I flash a stock recovery I get an annoying boot loop that is hard to get out of. I would attempt a RUU but I'm not sure if I should. I have a Verizon variant phone, but my carrier is not Verizon and my CID is a "rural version" that I do not see pop up very often: LRA_001. I usually run supercid though.
My fastboot getvar all results are below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.31.512.2
(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: 0P6B20000
(bootloader) cidnum: LRA__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: 2e9b7c51
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope someone can help!
Click to expand...
Click to collapse
I hate to say this, but on all of these I have seen you need a new motherboard. I even had one go in this same fashion. Your phone is failing to start the embedded modem.
dottat said:
I hate to say this, but on all of these I have seen you need a new motherboard. I even had one go in this same fashion. Your phone is failing to start the embedded modem.
Click to expand...
Click to collapse
Well that's disappointing. I guess I'll just need to go get a new phone then?
BaconBaconBacon said:
Well that's disappointing. I guess I'll just need to go get a new phone then?
Click to expand...
Click to collapse
did you manage to get your phone working, i have one with similar problem i can see the imei and baseband in booloader but they don't show up in settings > about, contacted HTC dev and they provided me a complete zip file to flash, it didn't help me much, besides the reboot issue in OS (which is due to wrong kernel).
i can share the zip file if you want.
genious_t said:
did you manage to get your phone working, i have one with similar problem i can see the imei and baseband in booloader but they don't show up in settings > about, contacted HTC dev and they provided me a complete zip file to flash, it didn't help me much, besides the reboot issue in OS (which is due to wrong kernel).
i can share the zip file if you want.
Click to expand...
Click to collapse
i have same problem please can send me file to flash(problem i can see the imei and baseband in booloader but they don't show up in settings)
Bro, I am reading your posts in XDA forum for the past 1 week.
genious_t said:
did you manage to get your phone working, i have one with similar problem i can see the imei and baseband in booloader but they don't show up in settings > about, contacted HTC dev and they provided me a complete zip file to flash, it didn't help me much, besides the reboot issue in OS (which is due to wrong kernel).
i can share the zip file if you want.
Click to expand...
Click to collapse
Bro, I am reading your posts in XDA forum for the past 1 week. I understood that you also have the same device as mine. I have the same HTC M8 device. I bought it via ebay. I am now in 3.31.512.2. Android 4.4.4.
Can u tell me anyway to upgrade to next version without losing Network functionalities. Lollipop or Marshmallow.
I am in India. I am using GSM network. The device is S-Off and Locked.
When I searched HTC website it shows the following things. It shows two versions
One M8 | LRA | USA | CRC | 3.4.0 | v4.4.4 | 432 MB | 3.31.512.2 |
One M8 | LRA | USA | MR | 1 3.4.0 | v5.0.2 | 535 MB | 4.21.512.4 |
Help me with this Bro .....
Aravindhan Leo said:
Bro, I am reading your posts in XDA forum for the past 1 week. I understood that you also have the same device as mine. I have the same HTC M8 device. I bought it via ebay. I am now in 3.31.512.2. Android 4.4.4.
Can u tell me anyway to upgrade to next version without losing Network functionalities. Lollipop or Marshmallow.
I am in India. I am using GSM network. The device is S-Off and Locked.
When I searched HTC website it shows the following things. It shows two versions
One M8 | LRA | USA | CRC | 3.4.0 | v4.4.4| 432 MB| 3.31.512.2 |
One M8 | LRA | USA | MR | 1 3.4.0 | v5.0.2| 535 MB| 4.21.512.4 |
Help me with this Bro .....
Click to expand...
Click to collapse
You won't find help in the Verizon section for this. Check out the main m8 section.
Sent from my HTC6545LVW using Tapatalk
dottat said:
You won't find help in the Verizon section for this. Check out the main m8 section.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
No problem Mate, I am new to the forum I found some guys talking about ( sw ver =3.31.512.2 ) here. Thats why I posted up my query. I already found the solution.
I flashed the correct RUU yesterday. It is working fine. If anyone searching for any info related to ( sw ver =3.31.512.2 )( OS-3.28.605.4, OS-4.21.512.4 ) click down the below thread.
http://forum.xda-developers.com/htc-one-m8/help/help-friends-t3402398/post67421791#post67421791
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!