Hello guys, i have a problem i can't solve with this phone.
Info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3851mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.164s
I have TWRP 2.7.0.1 installed. And like old said in this thread i tried them all.
I used this recovery backup by old (Non-LTE, first link) as base rom. First i extracted radio and android info file from the 4.1.2 OTA and flashed through bootloader then flashed that 4.2.2 backup over it. No reception. Then I extracted them from 4.2.2 OTA firmware.zip flashed through bootloader then flashed 4.2.2 stock rom but no reception from this one either. Why it's not getting any reception guys any ideas ? Thanks!
I don't know, what you all have flashed, because you asked some days agon in another thread for cricket files.
But all i can say is:
- downgrade hboot
- flash ICS RUU
- run the updates til you are on 4.2.2
Now you should be on a stock up to date phone.
If you still have reception problems, it seems more like a hardware issue or related to something wrong you have flashed before.
And just to make clear: i don't need multiple pm's with the same content you have posted here.
old.splatterhand said:
I don't know, what you all have flashed, because you asked some days agon in another thread for cricket files.
But all i can say is:
- downgrade hboot
- flash ICS RUU
- run the updates til you are on 4.2.2
Now you should be on a stock up to date phone.
If you still have reception problems, it seems more like a hardware issue or related to something wrong you have flashed before.
And just to make clear: i don't need multiple pm's with the same content you have posted here.
Click to expand...
Click to collapse
Im so sorry for those multiple pm's. Thats because i couldnt see my messages in the sent folder. Again sorry for that disturbance. I will try what you said. Thank you for your reply.
Related
hello, ive got this rogers htc one x that is stuck in a bootloader loop, anyway heres my info i really need help with this:
C:\adb>fastboot getvar all
(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.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24DW307580
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3706mV
(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: 1.031s
C:\adb>
actually its stuck in qhusb_dload
How did it get in this state?
Can you not get to bootloader?
slickwidnick said:
hello, ive got this rogers htc one x that is stuck in a bootloader loop, anyway heres my info i really need help with this:
C:\adb>fastboot getvar all
(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.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24DW307580
(bootloader) imei: 32
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3706mV
(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: 1.031s
C:\adb>
actually its stuck in qhusb_dload
Click to expand...
Click to collapse
well now ive managed to mess around and got aokp_evita-rohan-milestone6.4 rom loaded on my phone, but its stuck in a boot loop at the boot animation... ahhh, this is frustrating.....
How did you get it out of QHSUSB_DLOAD mode? You're s-on so you probably just need to flash the boot.img from the ROM zip via fastboot to get it to boot.
Sent from my Evita
timmaaa said:
How did you get it out of QHSUSB_DLOAD mode? You're s-on so you probably just need to flash the boot.img from the ROM zip via fastboot to get it to boot.
Sent from my Evita
Click to expand...
Click to collapse
just tried flashing the boot.img from the rom twice to make sure and it still bootloops at the boot animation...
and for how i ended up getting it off of qhusb_dload, i just downloaded all of what i could find for the rogers htc on x and tried flashing this, flashing that, and i dont really know exactly what it was that kicked it out of that mode...
im still confused as to why it wont boot after flashing the boot.img from the rom..
While "flashing this and that" has gotten you out of trouble this time I wouldn't suggest doing that again in the future, it was likely a huge fluke and flashing random things is a pretty bad idea. What ROM are you trying to flash?
Sent from my Evita
timmaaa said:
While "flashing this and that" has gotten you out of trouble this time I wouldn't suggest doing that again in the future, it was likely a huge fluke and flashing random things is a pretty bad idea. What ROM are you trying to flash?
Sent from my Evita
Click to expand...
Click to collapse
well originally i was trying to flash i think it was eragon and i got as far as flashing boot.img and then the rom wouldnt flash. now i have aokp_evita-rohan-milestone6.4 rom loaded but it bootloops.
should i try to flash another rom and keep trying till i find one that will startup?
What is eragon? If that's a ROM you've flashed a ROM that isn't for this device, no such ROM exists for the Evita (HTC One XL / AT&T One X). You're lucky you didn't brick your phone. Have a look through our development sections which you'll find here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Don't ever download ROMs from anywhere except within those two development sections or you're on a dangerous road to phone bricking land. Find a ROM you think you'll like, read the OP, make sure you meet any requirements it lists prior to flashing, and flash it.
PS. You should really remove your IMEI number from your first post, and the other post where you quoted it. Don't ever post your IMEI publicly.
Sent from my Evita
My phone is telling me that I have a system update to 5.0.1 available, but when I try to get it installed, it just goes back into Fastboot during the process. I am currently S-off and rooted. What do I need to do to get the OTA?
Here are the specs:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0321
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.55.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxxx
(bootloader) imei: 99xxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 99xxxxxxxxxxx
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__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: fd3e0448
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.014s
veyec said:
My phone is telling me that I have a system update to 5.0.1 available, but when I try to get it installed, it just goes back into Fastboot during the process. I am currently S-off and rooted. What do I need to do to get the OTA?
Here are the specs:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0321
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.55.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxxx
(bootloader) imei: 99xxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 99xxxxxxxxxxx
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__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: fd3e0448
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.014s
Click to expand...
Click to collapse
I doubt it's 5.0.1. You aren't even up to date as is. Screen shot the message.
Here it is.
veyec said:
Here it is.
Click to expand...
Click to collapse
Sending you a pm shortly.
veyec said:
Here it is.
Click to expand...
Click to collapse
If your rooted pull the OTA.zip from /cache and post it somewhere please
sent from space
This is very interesting....
There wasn't anything in the cache folder so I'll DL it again a not try to run it.
And here is the info screen that shows up during download:
runandhide05 said:
If your rooted pull the OTA.zip from /cache and post it somewhere please
sent from space
Click to expand...
Click to collapse
The Stig 04 said:
This is very interesting....
Click to expand...
Click to collapse
Looks to be a gpe custom Rom to me.
runandhide05 said:
If your rooted pull the OTA.zip from /cache and post it somewhere please
sent from space
Click to expand...
Click to collapse
I got the phone used and have had it for about 6 months or so. It came rooted with the stock sense ROM. I quickly got rid of sense. It started giving me the OTA Update notice about 2 days ago.
I have tried to install it a couple of times. Each time, after it downloads, it goes to reboot and ends up in the bootloader. It will not go into recovery, saying in the quick little flashing screen in the bootloader that the image file doesn't match. I end up having to flash a new recovery (TWRP) into the phone using ADB. After the failed install it boots into the existing Sinless ROM without any issues.
I have the .zip. I do not have a account where I can host the file other than Google Drive. It is 528 MB. I have it on my Google Drive and here is a link:
OTA.zip
veyec said:
I got the phone used and have had it for about 6 months or so. It came rooted with the stock sense ROM. I quickly got rid of sense. It started giving me the OTA Update notice about 2 days ago.
I have tried to install it a couple of times. Each time, after it downloads, it goes to reboot and ends up in the bootloader. It will not go into recovery, saying in the quick little flashing screen in the bootloader that the image file doesn't match. I end up having to flash a new recovery (TWRP) into the phone using ADB. After the failed install it boots into the existing Sinless ROM without any issues.
I have the .zip. I do not have a account where I can host the file other than Google Drive. It is 528 MB. I have it on my Google Drive and here is a link:
OTA.zip
Click to expand...
Click to collapse
f8f2c3d027d30a96573d22bc5deb09e70dc38810.OTA_M8_UL_L50_STOCK_UI_MR_Google_WWE_3.11.1700.5-2.12.1700.1_release_403384[1].zip
5 items
META-INF
patch
system
firmware.zip
fotaBoot
Displaying f8f2c3d027d30a96573d22bc5deb09e70dc38810.OTA_M8_UL_L50_STOCK_UI_MR_Google_WWE_3.11.1700.5-2.12.1700.1_release_403384[1].zip.
Your m8 is running a gpe Rom. The firmware is Verizon. That's why you aren't able to flash the ota. That ota doesn't really do us any good. You can however update your vzw firmware (not using this zip) and then you can flash the latest gpe Rom which is L.
dottat said:
f8f2c3d027d30a96573d22bc5deb09e70dc38810.OTA_M8_UL_L50_STOCK_UI_MR_Google_WWE_3.11.1700.5-2.12.1700.1_release_403384[1].zip
5 items
META-INF
patch
system
firmware.zip
fotaBoot
Displaying f8f2c3d027d30a96573d22bc5deb09e70dc38810.OTA_M8_UL_L50_STOCK_UI_MR_Google_WWE_3.11.1700.5-2.12.1700.1_release_403384[1].zip.
Your m8 is running a gpe Rom. The firmware is Verizon. That's why you aren't able to flash the ota. That ota doesn't really do us any good. You can however update your vzw firmware (not using this zip) and then you can flash the latest gpe Rom which is L.
Click to expand...
Click to collapse
Thanks dottat! i will work on getting the firmware installed now. Is THIS the latest firmware that I would want? And All that I need is the firmware, not the recovery or boot image, correct?
veyec said:
Thanks dottat! i will work on getting the firmware installed now. Is THIS the latest firmware that I would want? And All that I need is the firmware, not the recovery or boot image, correct?
Click to expand...
Click to collapse
Yes. That's the right firmware. It already has kernel and recovery omitted.
dottat said:
Yes. That's the right firmware. It already has kernel and recovery omitted.
Click to expand...
Click to collapse
Thanks everyone! Here are the results of the flash:
(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.28.605.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxx
(bootloader) imei: 99xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 99xxxxxxxxxxxxx
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.018s
Any suggestions for a good stable rom where everything works?
Hi! so I bought an Factory unlocked M8 from amazon to upgrade my M7, I check for updates and none, go to HTC see there is marshmallow for factory unlocked phones. I made a post on android forums and a guy helped me with info on my phone apparently it was an LRA phone a variant of verizon, I have T-Mobile as my carrier and the phone works on the network. I have loaded custom recovery, changed the CID, have SU and S-OFF. I read that I can turn this into a Dev edition and get marshmallow, and I couldn't get the firmware to flash (Thank god because I might have bricked my phone) If anyone can help me with the correct firmware or point me to a guide to do what I need to do it would be greatly appreciated. I can also provide any information you need.
Thanks in advance!
Here is the original info:
sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.21.512.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429861529
(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: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e7c075a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
and here is the changed info:
C:\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.21.512.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000429861529
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(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: e7c075a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
ok since no one has responded, here is another question, do I need to flash firmware on this phone to use a rom?
You can't flash dev edition firmware on Verizon variant device.
You can flash Verizon latest firmware. I'd link you to it but I'm on my phone. It's easily found however.
Edit: here ya go
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
As for using T-Mobile - no idea so can't help in that area. Idk if u flash T-Mobile ROM or verixoy and edit APNs.
But I do know u want to flash Verizon firmware I linked above.
andybones said:
You can't flash dev edition firmware on Verizon variant device.
You can flash Verizon latest firmware. I'd link you to it but I'm on my phone. It's easily found however.
Edit: here ya go
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
As for using T-Mobile - no idea so can't help in that area. Idk if u flash T-Mobile ROM or verixoy and edit APNs.
But I do know u want to flash Verizon firmware I linked above.
Click to expand...
Click to collapse
Awesome, just wanted to make sure I wouldn't damage my phone, otherwise i would have to go back to using my m7. Thanks for the link much appreciated!
one last question, if I flash t-mobile radios would it interfere with anything since I use their network? or just keep the APN settings.
Djhumphries said:
one last question, if I flash t-mobile radios would it interfere with anything since I use their network? or just keep the APN settings.
Click to expand...
Click to collapse
No idea about using T-Mobile on Verizon. I'd stick to the firmware meant for the device.
Others may be able to chime in.
were you able to find firmware for your device?
I also have LRA__001, I had flashed the wrong one and i have no signals now, using it as a TAB
I inadvertently posted this on the wrong forum. Just re-posting this in the correct location and adding some notes.
Hi all,
I started down a slippery slope which was what I hoped was an easy task of upgrading a relative's android phone to a later version into a several day ordeal with a broken phone.
I have a Vodafone from germany HTC One S. I wanted to upgrade to android 4.3 which seems to require a firmware update, but I'm having a very hard time finding the correct version of the RUL to apply.
Can someone help me if you happen to have that wonderful file laying around.
Here's my device's: 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: 3.16.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH25BW400482
(bootloader) imei: 359901048362418
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4137mV
(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
I'm currently running:
Android 4.1.1
Software Number: 1.14.709.16
Kernel: 3.4.10-gf987dcd
I would really really appreciate it if anyone had the correct RUU or could point me in the right direction.
Thanks so much.
The reason my bootloader is locked is because from what I read it needed to be locked in order to perform a firmware update. If that's not the case I can easily unlock it again.
Older thread for reference: http://forum.xda-developers.com/htc-one/help/looking-correct-ruu-vodafone-t3440997
Did the RUU u got from "alray" work? (cant post the androidfilehost link, but the file name is PJ40IMG_Ville_U_JB_45_S_Vodafone_UK_3.16.161.10_Radio_1.15.50.05.29_10.30.50.08L_release_314501_signed.zip)
Edit:
OH MY GOD... it works, after 20 hours of serching in this Forum i found you and your Link. Now i have a working OS for the first time. I got this Phone without OS,S-on and twrp was not working properly (unable to mount SD-card) Now I have a Base and I can proceed my Plans, unlock bootloader again, get SuperCID, S-off, a recovery and a custom ROM with root. Thank you so much!!
Hello guys
I had purchased a HTC E8 which was working absolutely fine but I found out that it was rooted before my purchase. I managed to install Xposed and everything worked fine.
However, I hadn't received an OTA update notification and even checking for updates in the phone gave back no results so I thought of manually updating (via fastboot) by flashing the 2.32.651.11 (Modified Firmware w/ Radio....removed boot & recovery) update found here
The process didn't report any errors and the phone rebooted from the process however I noticed that the version was exactly the same as before (1.22.651.1, KitKat).
That and I lost my sim signals and basically found out about the missing baseband after having it checked out in the market.
The repair person can't get it back to work though I have yet to ask what he has tried as of yet.
My phone's info is as follows (before the update):
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0701
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.22.651.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mec_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ5****
(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: d0c41a5b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Strangely enough, the model on the back cover is actually M8Sb, which simply does not exist in the table here: http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
My guess is that the previous rom installed was basically the "Stock Rooted ROM" provided in the link above.
Restoring the system via TWRP backup didn't fix the problem.
I don't have much experience fixing HTC software issues as much as I have with Nexuses on my own.
Searching through forums suggested that I should flash the radio files but I couldn't find those with the baseband version I had.
The next best option seems to be to flash RUU as I can tell but I am confused as to whether should I try flashing the KitKat RUUs or later.
Can I flash the single sim RUUs from other regions since it has super CID or will it hard brick the device?
Will flashing the RUUs fix the problem at all?
I am sure you guys have experience with the phone so I am desparately looking for any help I can get. It will be greatly appreciated.
Thankyou for reading.
I have similar problem here with the same model...
Any help would be appreciated
This happened to me as well. I have tried twrp backup and new firmware but no luck. In fastboot getvar all I can se both IMIE and basband but my feeling is that the rom can't access the data. Anyone have any ideas?