My device is stuck on HTC logo, i can enter into recovery mode, but i can't flash nothing, always the same error: getprop ro.product.device.
Can anyone help me with this? I noticed this problem:
C:\android-tools>Fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0005
(bootloader) version-baseband: 26.03.02.26_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 1.34.405.5
(bootloader) serialno: ***************
(bootloader) imei: ***************
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-9ddda97c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
Problem?...
Your entire setup has nothing to do with Saga
This is a good reason for some people to stay S-ON or go through an exam before getting XTC Clip.
Good for you that you have superCID. Use a RUU for Desire S this time
P.S.: and remove the IMEI from your post
Sent from my HTC Desire S
+1 - I think that's a Desire Z listing (that's what the HTC Vision was marketed as for the international market).
Also - remove your IMEI number from the listing. Never, ever post that info unless you don't actually want to be able to keep on using your phone.
I have received phone in this state. I can't install official rom (error 130). Goldcard change nothing, still error 130.
blasei said:
I have received phone in this state. I can't install official rom (error 130). Goldcard change nothing, still error 130.
Click to expand...
Click to collapse
So - what model of phone is it? If you're not sure then take the battery out and get the model information off there.
SimonTS said:
So - what model of phone is it? If you're not sure then take the battery out and get the model information off there.
Click to expand...
Click to collapse
Desire Z of course. Sorry, my mistake.
blasei said:
Desire S of course.
Click to expand...
Click to collapse
Well ... Your phone thinks it's a Desire Z - based on the bootloader info - so I would suggest that you put a different bootloader on there.
i have some problem too..
my htc stuck on recovery mode only
Unless you have flashed a ROM for the Desire S onto a Desire Z then you haven't got the same problem.
Don't just hop onto someone else's thread unless you have got exactly the same problem or can contribute.
Open a new thread with all the details that you should give and you are more likely to get help.
But ... make sure you search and read properly first as the answer to 99% of problems is already out there.
Sent from the darkest corners of my mind.
Related
So this is my first post, and I have a problem with bricked HOX.
I tried to put custom ROM, ViperX, with CWM (previously I unlocked bootloader and flashed with custom CWM recovery.img). After installation, I flashed with boot.img, but I couldn't boot. Now I have bricked, unlocked, HOX. I tried to unbrick with ruu, but ruu warned that my bootloader version is not good for ruu.
So how can I unbrick my HOX, is there ruu version for my HOX (and is there any way to unbrick it at all?)?
My HOX's specs:
CID: HTC__032
version-main: 3.20.401.3
HBOOT-1.39.0000
RADIO-5.1204.162A.29
Please help, and sorry for my bad English. I hope you understood
retsamor said:
So this is my first post, and I have a problem with bricked HOX.
I tried to put custom ROM, ViperX, with CWM (previously I unlocked bootloader and flashed with custom CWM recovery.img). After installation, I flashed with boot.img, but I couldn't boot. Now I have bricked, unlocked, HOX. I tried to unbrick with ruu, but ruu warned that my bootloader version is not good for ruu.
So how can I unbrick my HOX, is there ruu version for my HOX (and is there any way to unbrick it at all?)?
My HOX's specs:
CID: HTC__032
version-main: 3.20.401.3
HBOOT-1.39.0000
RADIO-5.1204.162A.29
Please help, and sorry for my bad English. I hope you understood
Click to expand...
Click to collapse
Wrong forum, this is for dual core. You'll wanna go here http://forum.xda-developers.com/forumdisplay.php?f=1533
RollTribe said:
Wrong forum, this is for dual core. You'll wanna go here http://forum.xda-developers.com/forumdisplay.php?f=1533
Click to expand...
Click to collapse
Thanks for for warning me.
Yes, I figured it later, so I posted in HTC One X forum.
Can somebody please remove this thread?
HTC ONE 802W Bricked
Hallo, I have the htc one 802W dual sim variant. It has HTC_802w_CWM_recovery_6.0.3.3_PhilZ_Touch_5 recovery & s-off, and the european rom version. PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125
My problem begins when I try to change model ID to flash the new 4.4.2 version, in the process it bricks and now is black screen, no led charging, but PC recognizes it when I connect by USB cable.
The fastboot getvar all is:
C:\SDK Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: (IMEI deleted for privacy reasons, but is OK)
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3445mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
C:\SDK Android\sdk\platform-tools>
I understand the English better than I write it, so I appreciate any help. A greeting.
asustekk said:
Hallo, I have the htc one 802W dual sim variant. It has HTC_802w_CWM_recovery_6.0.3.3_PhilZ_Touch_5 recovery & s-off, and the european rom version. PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125
My problem begins when I try to change model ID to flash the new 4.4.2 version, in the process it bricks and now is black screen, no led charging, but PC recognizes it when I connect by USB cable.
The fastboot getvar all is:
C:\SDK Android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: (IMEI deleted for privacy reasons, but is OK)
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3445mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
C:\SDK Android\sdk\platform-tools>
I understand the English better than I write it, so I appreciate any help. A greeting.
Click to expand...
Click to collapse
Unfortunately you're in the wrong device forum, this is the HTC One XL form. You need to ask in your own device forum, the people there are experienced with your phone and will be able to help you.
Sent from my Evita
Sorry I post it in the correct forum, can somebody delete this? thanks in advance.
timmaaa said:
Unfortunately you're in the wrong device forum, this is the HTC One XL form. You need to ask in your own device forum, the people there are experienced with your phone and will be able to help you.
Sent from my Evita
Click to expand...
Click to collapse
I have a HTC desire that was running Cyanogen and was rooted with revolutionary.io, but as I needed to unlock this phone I have had to go back to stock (apparently I could not unlock it with this Cyanogen ROM).
I have managed to get the phone back to S-on, but I cannot update any stock HTC ROM onto it now.
When I try to install the the standard Euro Desire S ROM (RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed), I get the error 131 customer id error
Below is the information that I can get from the phone if this helps;
C:\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.61.1
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4105mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
I can only access fastboot.
Any ideas on how I get the stock Desire S to run on this phone would be appreciated, as currently I can only get into the boot screen
Remove your imei and serial no.
I think we can assume your still soft with hboot 0.98 , try checking it in hboot.
Any reason why u want to return to stock? Custom roms are better and more stable, unless u are doing some troubleshooting no point in going back stock.
If your hboot is still s-off with 0.98 , update your hboot, make sure u have a custom recovery, then start flashing a rom.
Cheers
FromTheDesiredS
Removed the serial and IMEI....thank for the heads up!
I am needing to return to stock, as I need to unlock the phone. I have the code to unlock, but under the Cyanogen rom I was running the phone lept saying that the code had been accepted, but did not unlock. Infact I discovered that I could enter any code, and got that message, without unlocking. The company that supplied the code informed me that the phone needs to be running a stock rom for this code to work.
The hboot is now s-on.....does this give me a problem?
I was considering sending this phone to JTAG specialist for repair. Would this be necessary, or is there something that I could do to recover this situation?
mikepreece said:
I have a HTC desire that was running Cyanogen and was rooted with revolutionary.io, but as I needed to unlock this phone I have had to go back to stock (apparently I could not unlock it with this Cyanogen ROM).
I have managed to get the phone back to S-on, but I cannot update any stock HTC ROM onto it now.
When I try to install the the standard Euro Desire S ROM (RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed), I get the error 131 customer id error
Below is the information that I can get from the phone if this helps;
C:\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.61.1
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4105mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
I can only access fastboot.
Any ideas on how I get the stock Desire S to run on this phone would be appreciated, as currently I can only get into the boot screen
Click to expand...
Click to collapse
First reason why it fail is because ur "version-main" is 1.47 and the ruu that ur trying to flash is 1.28, u cant downgrade.
Second reason is that ur locked to orange so u cant use a europe ruu, u will have to use orange branded ruu.
Either find the orange ruu 1.47 or above and flash it but if u use one above then u will have downgrade after to achive s-off. Theres guides here in dev thread on how to do it. Or u can create a goldcard and then use a wwe/europe ruu, the goldcard bypasses the cid check of the ruu. All guides r here on xda, just search, im on my phone cant post links. (i could but its easier on laptop)
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
Not a noob but not that smart either....
Verizon HTC M8 stuck in a boot loop. Shows HTC screen and reboots. Recovery and Factory reset just send it into the same loop. Tried fastboot erase cache, didn't help. Thought I found the stock recovery.img here and tried flashing that, but got:
(bootloader) signature checking...
FAILED (remote: signature verify fail)
Any thoughts or something else I should try? I'm actually not sure what someone might have tried to make this start happening - friend of mine sold it, and they guy gave it back saying it was doing the loop when he got it.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0222
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.605.11
(bootloader) version-misc: PVT SHIP S-ON
(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: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3a4162f9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I could be wrong (probably am) but I don't think you can flash recovery.img with a locked bootloader. Have you tried booting into RUU mode and flashing the verified stock RUU? I dont know if those have been released into the wild though.
wildbluesky said:
Not a noob but not that smart either....
Verizon HTC M8 stuck in a boot loop. Shows HTC screen and reboots. Recovery and Factory reset just send it into the same loop. Tried fastboot erase cache, didn't help. Thought I found the stock recovery.img here and tried flashing that, but got:
(bootloader) signature checking...
FAILED (remote: signature verify fail)
Any thoughts or something else I should try? I'm actually not sure what someone might have tried to make this start happening - friend of mine sold it, and they guy gave it back saying it was doing the loop when he got it.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0222
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.605.11
(bootloader) version-misc: PVT SHIP S-ON
(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: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3a4162f9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
If you locked with s-on I would take it to VZW store an say look at this.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Tigerstown said:
If you locked with s-on I would take it to VZW store an say look at this.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am starting to think it might actually be a hardware problem anyway. I've gotten it to at least stay on for a minute and recovery actually works now, but it's still just constantly booting.
wildbluesky said:
I am starting to think it might actually be a hardware problem anyway. I've gotten it to at least stay on for a minute and recovery actually works now, but it's still just constantly booting.
Click to expand...
Click to collapse
How do you have a recovery with a locked son phone? Or are you talking bout your stock recovery? I'm confused
Sent from my red HTC M8 using Tapatalk cause Xda apps keep f/c?
Tigerstown said:
How do you have a recovery with a locked son phone? Or are you talking bout your stock recovery? I'm confused
Sent from my red HTC M8 using Tapatalk cause Xda apps keep f/c?
Click to expand...
Click to collapse
Stock recovery. Couldn't even get into that before.
Hi DEVs,
My phone is stuck ina bootloop and been searching for tow days but no luck.
i will be soo thankfull if someone could provide me with the correct rom
(Bootlouder Locked and S-ON)
C:\ADB>fastboot getvar all
< waiting for any device >
(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: 3.11.401.106
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT39JTP00464
(bootloader) imei: ----------------
(bootloader) meid:
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.097s
None gonna help me ?
medpks said:
None gonna help me ?
Click to expand...
Click to collapse
If you can run Android, you should first do S-OFF.
Read and understand >this< post and adapt the appropriate files to your k2_u device (without LTE).
ze7zez said:
If you can run Android, you should first do S-OFF.
Read and understand >this< post and adapt the appropriate files to your k2_u device (without LTE).
Click to expand...
Click to collapse
Thanks for your reply, but as i mentioned above i am stuck ina bootloup so no way i could perform a S-OFF
ze7zez said:
If you can run Android, you should first do S-OFF.
Read and understand >this< post and adapt the appropriate files to your k2_u device (without LTE).
Click to expand...
Click to collapse
Thanks for your reply, but as i mentioned above i am stuck in a bootloup so no way i could perform a S-OFF
medpks said:
Thanks for your reply, but as i mentioned above i am stuck in a bootloup so no way i could perform a S-OFF
Click to expand...
Click to collapse
If the bootloop is on every startup, the eMMC memory may be corrupted.
In this case there is a small chance that the RUU will help.
Anyway, I can see the ROM > here <.
If after logging in you will not be able to access the file, check the remaining links after searching in google.
I wish you luck.
ze7zez said:
If the bootloop is on every startup, the eMMC memory may be corrupted.
In this case there is a small chance that the RUU will help.
Anyway, I can see the ROM > here <.
If after logging in you will not be able to access the file, check the remaining links after searching in google.
I wish you luck.
Click to expand...
Click to collapse
I agree with you about That eMMC could be corrupted :good: , but im having a slight doubt it could be a software issue, and i want to try Flash first then confirn.
Btw thanx for the RUU link, but its a paid file.. wish i could test my phone with a free file
Official OTA
medpks said:
(...cut...) wish i could test my phone with a free file
Click to expand...
Click to collapse
You should be satisfied. Below is the link to the official OTA from HTC.
OTA_K2_U_JB422_SENSE50_MR_HTC_Europe_3.11.401.106-2.14.401.107_release_339145qf6n2sk971fk7x3k.zip
Guide: How To Manually Flash OTA File