Hi Guys,
I got a preowned device, since I own it it has been broken. Don't know what its old owner did.
I know there are a lot of similar problems out there, but:
I guess my device has no boot, no recovery, not whatever. But It is recognized by computer (shows USB), fastboot is accessible.
I flashed a lot of zips, none worked. Apparently bootloader was unlocked, now it is relocked. I think the big problem is: I got OS 7.18.111.51. This is a german T-Mobile Software, nowhere I found a fitting RUU. I found an OTA Zip, but flashing won't work. All zips are failing because of many reasons: signature verification failed, CID doesnt fit, even all the RUUs are canceling. All are beginning writing boot and then some kind of verification is failing.
I even tried unlocking bootloader, but then it reboots and freezes while entering recovery.
I really need some help. Is there still anything I can do?
Thanks in advance.
ICWS said:
Hi Guys,
I got a preowned device, since I own it it has been broken. Don't know what its old owner did.
I know there are a lot of similar problems out there, but:
I guess my device has no boot, no recovery, not whatever. But It is recognized by computer (shows USB), fastboot is accessible.
I flashed a lot of zips, none worked. Apparently bootloader was unlocked, now it is relocked. I think the big problem is: I got OS 7.18.111.51. This is a german T-Mobile Software, nowhere I found a fitting RUU. I found an OTA Zip, but flashing won't work. All zips are failing because of many reasons: signature verification failed, CID doesnt fit, even all the RUUs are canceling. All are beginning writing boot and then some kind of verification is failing.
I even tried unlocking bootloader, but then it reboots and freezes while entering recovery.
I really need some help. Is there still anything I can do?
Thanks in advance.
Click to expand...
Click to collapse
Please post your "fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.111.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid: XXXXXXXX
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4304mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-07a9e40d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
There you go. Anything helpful?
Related
Hi,
I wanna get an idea about the issue on my HTC One. I have a,
HTC One International version
Unlocked
S-On
Hboot: 1.54.0000
OS: 2.24.401.9
Earlier: TWRP 2.6.3.3
Now: TWRP 2.7.0.0
which rooted and I have been using various Sense based custom roms for about 6 months. After recent custom rom installation, my device didn't load the initial setup wizard. It was saying "service.htc.htcdialer failed". So what I did was I installed another custom rom. It also gave the same issue. After that I downloaded a Stock Zip file from here and flashed using these instructions. But I have no luck because it gave me an error like this during flashing process.
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
OKAY [ 35.969s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 88.871s
Currently, My device is loading into bootloader and that is it. Nothing loads when you turn the device on. Only the HTC logo and then restart. I also flashed TWRP 2.7.0.0 finally thinking that it might be more helpful than the Stock recovery.
I'm pulling my hair now and I wanna fix my device. Can anyone direct me to find the correct RUU or Zip file to flash?. Also please tell me how do I prepare my device to fix it?. This will be a great help.
Thanks you very much.
Dam.
im having the same problem. i can get to bootloader but i cant start my phone. its also boot looping. i found http://forum.xda-developers.com/showthread.php?t=2317985& but i dont know what .zip file im supposed to have or where to get it.
Hark! You need the RUU that matches your phone's CID. Find this by running "fastboot getvar all" and looking through the output. Then google for that. If it doesn't exist (many CIDs only have a backup made from ClockworkMod), things will be a lot harder, and you'll need to decide whether to attempt to restore your phone to a stock-like state, or to start using custom ROMs (great for tweakers, and also reasonably error-free and simple for average people).
But you haven't told us what preceded this problem. Booting to fastboot and running "fastboot erase cache", or a factory reset ("fastboot erase data") may help. Try wiping cache, booting to recovery and using that to backup your data, then factory reset. If that doesn't help, do my above advice.
fenstre said:
Hark! You need the RUU that matches your phone's CID. Find this by running "fastboot getvar all" and looking through the output. Then google for that. If it doesn't exist (many CIDs only have a backup made from ClockworkMod), things will be a lot harder, and you'll need to decide whether to attempt to restore your phone to a stock-like state, or to start using custom ROMs (great for tweakers, and also reasonably error-free and simple for average people).
But you haven't told us what preceded this problem. Booting to fastboot and running "fastboot erase cache", or a factory reset ("fastboot erase data") may help. Try wiping cache, booting to recovery and using that to backup your data, then factory reset. If that doesn't help, do my above advice.
Click to expand...
Click to collapse
sorry to jack your thread damithark
hey fenstre. so my problem is i installed cyananomod correctly but then i tried to install this http://forum.xda-developers.com/showthread.php?t=2249774. i ran through the whole thing but when it said it was going to boot my device, it never did. now i cant boot up my phone but i can get to the bootloader. i also just ran the fastboot getvar all but im not sure what im looking for. ive tried factory resetting and everything else that you can do from the bootloader.
fenstre said:
Hark! You need the RUU that matches your phone's CID. Find this by running "fastboot getvar all" and looking through the output. Then google for that. If it doesn't exist (many CIDs only have a backup made from ClockworkMod), things will be a lot harder, and you'll need to decide whether to attempt to restore your phone to a stock-like state, or to start using custom ROMs (great for tweakers, and also reasonably error-free and simple for average people).
But you haven't told us what preceded this problem. Booting to fastboot and running "fastboot erase cache", or a factory reset ("fastboot erase data") may help. Try wiping cache, booting to recovery and using that to backup your data, then factory reset. If that doesn't help, do my above advice.
Click to expand...
Click to collapse
This was caused because of a strange issue I encountered. After a reboot, I got a message saying my internal storage is encrypted and asked a password to decrypt. I didn't attempt any encryption and from what I found from google is that I need to do a data reset. So I did that and installed a Rom from TWRP and that was not starting up. It said "service.htc.htcdialer failed to start". So I had to then install a stock recovery and try flashing a RUU zip file. It also failed with this.
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
OKAY [ 35.969s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 88.871s
I have a these RUU files,
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4.exe
RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted.zip
Guru_Reset_M7_2.24.401.8.zip
and these are the info,
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA36RW908595
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4250mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
How am I to proceed?.
Thanks.
redelmos said:
sorry to jack your thread damithark
hey fenstre. so my problem is i installed cyananomod correctly but then i tried to install this http://forum.xda-developers.com/showthread.php?t=2249774. i ran through the whole thing but when it said it was going to boot my device, it never did. now i cant boot up my phone but i can get to the bootloader. i also just ran the fastboot getvar all but im not sure what im looking for. ive tried factory resetting and everything else that you can do from the bootloader.
Click to expand...
Click to collapse
It's alright mate. Hope you'll find an answer. :good:
So I red some threads recently and found an RUU that supports my CID number. Any help to continue?.
redelmos said:
i installed cyananomod correctly but then i tried to install this http://forum.xda-developers.com/showthread.php?t=2249774. i ran through the whole thing but when it said it was going to boot my device, it never did. now i cant boot up my phone but i can get to the bootloader.
Click to expand...
Click to collapse
I think issues like that are common. You can wipe: cache/dalvik cache/data. You can also boot recovery and do a filesystem check on /system with this command: "e2fsck -f /dev/something/something", where you can find what "something" is by mounting /system and running "mount|grep system", then unmounting it. If none of that works, the kernel installer must have borked your existing CM install, and you'll need to reinstall.
damithark said:
So I red some threads recently and found an RUU that supports my CID number. Any help to continue?.
Click to expand...
Click to collapse
Good. I suggest googling it.
I think I found the issue. I can't flash any RUU that are available because my HBOOT version is 1.54. RUU file needs a earlier version of the HBOOT version (Eg: HBOOT 1.44). So to downgrade my HBOOT, I think I need to S-OFF. Because I'm in a boot loop, I can't S-OFF because it requires me to enable debugger mode. Is there a way to S-OFF using bootloader?. Please help me. I'm Stuck with this for 2 days now.
Thanks.
I really love to get some help on this one please.
I don't know why anyone doesn't helps me. I have a HTC One which is,
Loading to bootloader,
Have TWRP 2.7 installed,
Device fully Data Wiped,
In a bootloop,
ADB doesn't recognize my device.
Only fastboot does.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What do I do to fix my phone?. I'm from Sri Lanka where mobile is mostly needed these days because it is the Festival season here. Any help will be greatly appreciated.
Thanks.
damithark said:
I don't know why anyone doesn't helps me. I have a HTC One which is,
Loading to bootloader,
Have TWRP 2.7 installed,
Device fully Data Wiped,
In a bootloop,
ADB doesn't recognize my device.
Only fastboot does.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What do I do to fix my phone?. I'm from Sri Lanka where mobile is mostly needed these days because it is the Festival season here. Any help will be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Buy a USB OTG cable (very cheap, about $5)
Copy ARHD/any other rom of your choice to a USB
Plug in your USB OTG cable with the USB containing the rom attached to the cable
Mount USB OTG in the Mounts section (within TWRP)
Hit Install, scroll up to the root of the phone (NOT THE /sdcard)
There, choose storage or USB OTG (whatever in shows)
Flash the ROM and wipe in Aroma
Profit
i already told you go back to 2.6.3.3 or .4
nkk71 said:
i already told you go back to 2.6.3.3 or .4
Click to expand...
Click to collapse
I did and it worked. Now I have another issue,
So what I did was I sideloaded a Custom Rom (ViperOne_5.8.0).
Installed it.
It loaded for the first time and says, "Process 'com.htc.htcdialer' isn't respoding" . After a while, device restarts.
It continuously happens every time the device restarts. Can't pass the initial screen.
What do I have to do now?.
Thanks a lot.for the help so far.
damithark said:
I did and it worked. Now I have another issue,
So what I did was I sideloaded a Custom Rom (ViperOne_5.8.0).
Installed it.
It loaded for the first time and says, "Process 'com.htc.htcdialer' isn't respoding" . After a while, device restarts.
It continuously happens every time the device restarts. Can't pass the initial screen.
What do I have to do now?.
Thanks a lot.for the help so far.
Click to expand...
Click to collapse
Wipe all the partitions except Internal Storgae in the 'Wipe' section of TWRP and in the Aroma and then re-install the ROM. For some reason, the Aroma wipe doesn't work properly. I also had the same issue........
The wipe did the trick
damithark said:
I did and it worked. Now I have another issue,
It loaded for the first time and says, "Process 'com.htc.htcdialer' isn't respoding" . After a while, device restarts.
Click to expand...
Click to collapse
that doesn't sound good
In booted ROM, if you go to "Settings -> About -> Software information -> More" does baseband show up correctly?
and "Settings -> About -> Phone identity" shows correct IMEI, IMSI?
Is it saying:
Baseband version - unknown
IMEI - Unknown
IMWI SV - Unknown
Imsi - unavailable
hope not!!
raghav kapur said:
Wipe all the partitions except Internal Storgae in the 'Wipe' section of TWRP and in the Aroma and then re-install the ROM. For some reason, the Aroma wipe doesn't work properly. I also had the same issue........
The wipe did the trick
Click to expand...
Click to collapse
Thanks for the tip raghav. I did what you said and it doesn't work. Same issue appears saying "Process 'com.htc.htcdialer' isn't respoding".
and, reboots after a while. Do you think this is a hardware issue?.
Thanks for the help.
nkk71 said:
that doesn't sound good
In booted ROM, if you go to "Settings -> About -> Software information -> More" does baseband show up correctly?
and "Settings -> About -> Phone identity" shows correct IMEI, IMSI?
Is it saying:
Baseband version - unknown
IMEI - Unknown
IMWI SV - Unknown
Imsi - unavailable
hope not!!
Click to expand...
Click to collapse
Problem is, I can't get to that step because the phone is not passing the initial setup. What I can do is,
fastboot getvar all and it gives me this info,
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hope it is alright.
Thanks.
damithark said:
Problem is, I can't get to that step because the phone is not passing the initial setup. What I can do is,
fastboot getvar all and it gives me this info,
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hope it is alright.
Thanks.
Click to expand...
Click to collapse
Very very strange. I was on the latest Kitkat firmware, S-OFF and SuperCID though. @nkk71 had suggested me to wipe when I had that issue. That solved my problem. However, ARHD ALWAYS worked for me. InsertCoin and ViperOne gave me that same error. And, my networking wasn't working at all either in ViperOne/InsertCoin. I flashed ARHD, which has a 100% success rate for me.
My suggestion: Flash ARHD 31.6, which SHOULD work
Then S-OFF through Rumrunner
Update to 4.19.401.11
Then SuperCID
After that, choose any ROM
damithark said:
Problem is, I can't get to that step because the phone is not passing the initial setup. What I can do is,
fastboot getvar all and it gives me this info,
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__A48
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hope it is alright.
Thanks.
Click to expand...
Click to collapse
1- Remove IMEI and s/n from your post.
2- get a "thinner" ROM, for example: http://forum.xda-developers.com/showthread.php?t=2272945
then check the above information
Hello everybody, hope everyone is having a better day than I am. I will try to keep this short but I am more than happy to provide more details as they are needed.
I picked up a replacement HTC One (ATT) after a warranty claim for a bad speaker and I immediately rooted it. After rooting the phone and before flashing a custom rom it started rebooting itself every couple of minutes. I went ahead and flashed a custom rom (many to be honest) and the phone booted up just fine, however, the phone would not recognize the sim card. I tried the sim card in a different phone and it worked fine. Then, with the sim card replaced, all of a sudden the phone worked for about 30 minutes. After that it started rebooting itself at will every couple of minutes. I decided that i must have flashed a bad file or something so i decided to go back to stock with RUU.exe. I locked the bootloader and ran the .exe from my laptop (windows 7) Now my phone i "relocked" and the RUU flashed a recovery that I can not get into. My boot screen now reads this
***relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
(date and time)
this is the RUU.exe I loaded
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2 - HTC1Guru
Now when I start my phone it loads to the ATT screen with the globe, sometimes plays the chim, and then goes to a white screen with the green HTC. after about a minute it reboots and loads to the exact same spot. It will do this until I enter the bootloader and power it down
I don't know what to do anymore as I have read about a thousand threads and I am getting confused on what the next step should be. I would greatly appreciate a point in the right direction.
Although the POS phone I am using with a modified sim card holder is pretty awesome
Thanks in advance
Get ATT to replace to it again?
there is more back story that I did not go into and i don't know if I can get it replaced again.
Now when I turn on the phone it loads to the initial start up screen where it ask to set up my account and set up wifi. but agian after a minute or so it just reboots and loads to about the same spot and then restarts.
I still think this is fixable
Can anyone point me in the right direction?
Thanks
What software version are you on now? I'm not near a computer but my first thought is that because you are s-on, you can not run an RUU that is older than your current version. So if you are on KitKat now, you can't run a Jelly bean 4.3 ruu.
You would need to be s-off in order to do that.
Sent from my HTC One using Tapatalk
to tell you the truth I don't know anymore because i have tried to load so many different things, how can I tell for sure?
another question...Now that I have a relocked bootloader can I try to rerun the RUU.exe file? I will check my getvar this evening to find the correct RUU but just don't know if this will work with a locked bootloader and no recovery.
redraider25 said:
another question...Now that I have a relocked bootloader can I try to rerun the RUU.exe file? I will check my getvar this evening to find the correct RUU but just don't know if this will work with a locked bootloader and no recovery.
Click to expand...
Click to collapse
Sure will work as long as RUU is same level as your phone
I would try re-running the RUU. Sometimes they don't do everything correctly. But done right, it should wipe your phone of any custom software and take you back to clean stock.
Finally made it back home I wanted to post my getvar all so please tell me if you see something bad
c:\miniadb_m7>adb devices
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please advise me if I should still rerun the RUU.exe file above or do I need to do something different first
Well it looks like you are on 3.17 and the Ruu is 3.17 so give it a shot.
Sent from my HTC One using Tapatalk
redraider25 said:
Finally made it back home I wanted to post my getvar all so please tell me if you see something bad
c:\miniadb_m7>adb devices
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please advise me if I should still rerun the RUU.exe file above or do I need to do something different first
Click to expand...
Click to collapse
What about factory reset from bootloader?
42 22435958
Well I tried to RUU.exe again and now the phone will load to the setup. I went through that, but it is not recognizing my sim card. I can sign on to wifi which works and I can navigate the homescreens. after about 2 minutes the phone reboots itself and the whole cycle happens again. i tried to do a software update but with out the sim card being recognized it says Network not available. the signal bar has an "X" and it does not recognize when I try to remove the sim card to reposition it.
should I try a different RUU.exe file? Thanks for all the help, I think we are getting close. One thing I think is strange is when I ran getvar all, it has a strange line I noted it below. Anybody know what this means?
c:\miniadb_m7>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88 THIS LINE HERE!!!!!!!!!!!!!!!!!!!!!!!!!
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks in advance
While the phone is up, can you go to settings > about devices > hardware info> baseband.. is it empty?
The baseband says "unknown"
redraider25 said:
The baseband says "unknown"
Click to expand...
Click to collapse
Its dead Jim.
SaHiLzZ said:
Its dead Jim.
Click to expand...
Click to collapse
really, thats it? No mas htc one for me?
So am I the proud owner of a BRICK?
I'm new to the HTC One and I almost didn't know what I was doing, so I messed up really bad.
What did I do:
My friend wanted to try cm11 in his phone, so I unlocked the bootloader, installed cmw 6.0.2.8 and then the cm11 rom. It all went fine, but he realized that a lot of data he had wasn't recovered by Google's backups. so I thought that installing a rom with htc sense we could recover the majority of contacts and other things that he had. So I downloaded and installed this rom:
HTML:
http://forum.xda-developers.com/showthread.php?t=2626050
and installed it (wrong rom). When the installation finished, the phone rebooted into bootloader with the 'Active cmdline overflow' error.
I tried different solutions but nothing worked for me.
So, here goes the phone's info: (I got it in RUU mode, I hope it doesn't matter)
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA**********
(bootloader) imei: 35*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG309
(bootloader) battery-status: good
(bootloader) battery-voltage: 3866mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I flashed recovery a few times, always erasing cache, but I still can't enter recovery.
I hope someone can help me.
Frinalal said:
I'm new to the HTC One and I almost didn't know what I was doing, so I messed up really bad.
What did I do:
My friend wanted to try cm11 in his phone, so I unlocked the bootloader, installed cmw 6.0.2.8 and then the cm11 rom. It all went fine, but he realized that a lot of data he had wasn't recovered by Google's backups. so I thought that installing a rom with htc sense we could recover the majority of contacts and other things that he had. So I downloaded and installed this rom:
HTML:
http://forum.xda-developers.com/showthread.php?t=2626050
and installed it (wrong rom). When the installation finished, the phone rebooted into bootloader with the 'Active cmdline overflow' error.
I tried different solutions but nothing worked for me.
So, here goes the phone's info: (I got it in RUU mode, I hope it doesn't matter)
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA**********
(bootloader) imei: 35*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG309
(bootloader) battery-status: good
(bootloader) battery-voltage: 3866mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I flashed recovery a few times, always erasing cache, but I still can't enter recovery.
I hope someone can help me.
Click to expand...
Click to collapse
this fix is touch and go with your current hboot, give it a try, if it works then :fingers-crossed: if not then its :crying: as your s-on
http://forum.xda-developers.com/showthread.php?t=2739126
Seanie280672 said:
this fix is touch and go with your current hboot, give it a try, if it works then :fingers-crossed: if not then its :crying: as your s-on
Click to expand...
Click to collapse
Yes, I alredy tried it, but after installing the noBCB recovery, I still cant access it.
I also searched for nand backups for my CID, but there aren't any. (I don't know if that would even help at all)
Frinalal said:
Yes, I alredy tried it, but after installing the noBCB recovery, I still cant access it.
I also searched for nand backups for my CID, but there aren't any. (I don't know if that would even help at all)
Click to expand...
Click to collapse
nope, nothing will work until you fix that error.
if you carry on reading through that thread you will see that people experiencing that problem have had to downgrade their HBOOT in order to get it to work, unfortunately you need to be s-off to do that, I think one user had success using a certain version of cwm recovery, here you go, try this:
http://forum.xda-developers.com/showpost.php?p=53634257&postcount=90
Seanie280672 said:
nope, nothing will work until you fix that error.
if you carry on reading through that thread you will see that people experiencing that problem have had to downgrade their HBOOT in order to get it to work, unfortunately you need to be s-off to do that, I think one user had success using a certain version of cwm recovery, here you go, try this:
Click to expand...
Click to collapse
Thanks for helping. I tried it and it still doesn't work. I'll keep searching around the forums to see if I can do anything.
Hi Guys,
I have been reading around the forum but cant seem to find the answer to my problem. Or the suggestions are going over my head, so hope you can help.
I have a stock htc one m7 that is unrooted but it is sim unlocked. Went to bed with the phone working and then woke up with it stuck on the htc boot screen.
Things I have tried:
- get into HBOOT (which i can), then try recovery. This just reboots the phone to the white htc screen or screen just goes off.
- try and hard reset from hboot, but this does the same and either turns the screen black or reboots.
Both times i have left the phone for a while to see if it is up to anything but nothing happens.
I read about clearing the cache, but I could not get my head around the guides I read, so is there an idiots guide (I usually pretty good with tech stuff but not done much to do with phones etc)
Or any other suggestions. I use my phone for work so would be nice to get it working again without wiping it but most of the stuff should be back up anyway.
Thanks
Tom
From what I have tried I guess I should now try and flash the RRU?
The phone is on UKs EE network, as it is not rooted do I need to flash it with their branded rom or not? If so where can I get that from.
Thanks
Tommy_G5 said:
From what I have tried I guess I should now try and flash the RRU?
The phone is on UKs EE network, as it is not rooted do I need to flash it with their branded rom or not? If so where can I get that from.
Thanks
Click to expand...
Click to collapse
Do you have an sdk installed on your pc for adb/fastboot? If so can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting :good:
Danny201281 said:
Do you have an sdk installed on your pc for adb/fastboot? If so can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting :good:
Click to expand...
Click to collapse
Just downloading sdk now but I used another program i found on my travels. Is this all the info you need?
C:\toolkit>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(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-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.052s
If you need other info ill post it when sdk is downloaded and installed
Thanks for your help!
Tommy_G5 said:
Just downloading sdk now but I used another program i found on my travels. Is this all the info you need?
C:\toolkit>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(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-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.052s
If you need other info ill post it when sdk is downloaded and installed
Thanks for your help!
Click to expand...
Click to collapse
Yep that's what we wanted, unfortunately there's no ruu for your phone
If you've got warranty on the device I would send it in for repair.
If you don't have warranty you gonna need to unlock the bootloader to do anything with it. If your gonna do it go here www.htcdev.com register an account and go to the Unlock My Bootloader section of the site and follow the instructions to unlock :good:
Ok. I will do that.
So once the bootloader is unlocked, what is my solution? installing a different Ruu? Or installing a different Rom (or are they the same thing)
Thanks
Tom
Tommy_G5 said:
Ok. I will do that.
So once the bootloader is unlocked, what is my solution? installing a different Ruu? Or installing a different Rom (or are they the same thing)
Thanks
Tom
Click to expand...
Click to collapse
Once your Unlocked you can flash a Custom or Unbranded Stock Rom. To be able to use RUU's you will need to go s-off. As your on hboot 1.57 the only way to s-off is Sunshine app. But this costs $25 to use. So I would just go with flashing a Custom Recovery and ROM for the time being. :good:
Unlocking the bootloader void warranty. If you have none, then proceed. In my opinion, your phone has suffered hardware failure and will not be recoverable, hence warranty.
Thanks
Thanks for the help guys. Turns out its still under warranty which is good news. I know with other custom roms you can use adb to retrive info off the device.
Any chance I can do the same, as most of the stuff is backed up except some photos ( last couple of months worth).
If not Ill get over it but just in case.
Thanks for your help so far.
Tom
Hello everybody!
I am loosing my mind with this, would be grateful if someone could help me!
Received an HTC One M7 Nordic (HTC__Y13) version, HBOOT 1.61.0000, radio 4T.35.3218.16, ODSP 35.120.274.0718 OS.
Firstly, I unlocked the bootloader via HTCdev, then, as I did with other devices, installed CWM which I used to wipe just about everything and I installed LineageOS. (S-ON, Tampered, Unlocked bootloader). To my surprise, LOS didn't boot, booting back to fastboot. I gave it another try, reinstalling it, failed to boot again. Then I started trying the RUUs, and the farthest I could reach was the signature rejection at 4%. I am using a Mac with both Sierra and a windows XP SP3 VM in Parallels, which I also used to try with a myriad of toolkits made for this phone. In HTC Sync, although the phone is recognised, all info, like OS version, are blank.
Well, here I am with a device without OS which boots to fastboot and TWRP/CWM. Since the beginning of this adventure, I couldn't boot once to a ROM, and I lost 3 long nights on this already. I believe the only things I could have missed are: using the right RUU.exe or zip, or someway getting the phone S-OFF without using an OS, since I don't have one.
When trying to "fastboot flash -zip ruu.zip", I always have some kind of error like "remote 02 data length is too large" or a variant of this.
I am getting kinda afraid I may have bricked the phone. Could someone help me?
Thanks!
here is the "getvar" dump
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3BRWxxxxxx
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
wasserprojekt said:
When trying to "fastboot flash -zip ruu.zip", I always have some kind of error like "remote 02 data length is too large" or a variant of this.
Click to expand...
Click to collapse
You must use htc_fastboot.exe from a Windows pc, not the regular fastboot. Make sure you have the latest RUU for your cid/mid
Thanks for your answer. I was about to give up on this, but then I finally found the right RUU. There are so many variants it becomes a nightmare finding the adequate one, eve worse if version is not one of the best selling.
But, as someone may need this advice in the future, I'll leave a summary of the important steps in here:
Return to stock ROM (for S-ON & unlocked bootloader & tampered):
- relock your device;
fastboot oem lock
Click to expand...
Click to collapse
-find the adequate RUU;
(for HTC__Y13, it's the RUU_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.exe)
-close all programs which may connect to phone (includes HTC sync, any fastboot or adb command window...), otherwise there will be no progress in the RUU;
-start the RUU with phone connected (VMs work - at leaset in Parallels with XP SP3).
Thanks to everyone.