Initially device had following software properties:
- Stock rooted jb rom
- S-off
- TWRP jb recovery
What messed up everything was that I flashed an ICS rom (AOKP) over my JB hboot.
Now phone doesn't boot (remains stuck at HTC logo).
I can acces only fastboot. If I try to acces recovery system remains stuck at HTC logo.
I've tried to reflash recovery (TWRP, Philz Touch, Atti's - all jb recoveries) in fastboot but with no result. It says operation succesful but still cannot acces recovery. I also did fastboot erase cache.
When entering fastboot getvar all I get the following information:
Code:
(bootloader) version-bootloader: 1.25.0002
(bootloader) version-baseband: 1.15.40.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: u�n�g"�a6����
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: ���e����(����Q�~���Q��=��/ `oj\
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-02bbe6c44f94272745d8398b32e3f3e4f
getvar:all FAILED (unknown status code)
finished. total time: 0.067s
I would really appreciate it if someone could point me in the right direction to resolve this problem.
Thank you all!
Oops, reread, sorry.
I have no idea why the recovery will not reflash. Sorry for wasting time.
EDIT: I had an idea!
Because you are S-off, your recovery can access way more partions and could have just flashed another incorrect one besides your recovery etc.
Go to the s-off thread, there are a lot of partion images posted. Flash as many as you can find to the right partions and maybe see if that works.
EDIT: Lack of vibrations. Look for which partion causes it.
Hopefully I've been somewhat helpful, though unlikley,
Thanks! I will try it and give feedback.
Sent from my LG-P500 using XDA Free mobile app
That's right. Good idea @CurtisMJ! He should try zu flash radio partition (after backup of course, don't remember the partition number now), because the seven vibrations are caused by radio if I remember right.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
That's right. Good idea @CurtisMJ! He should try zu flash radio partition (after backup of course, don't remember the partition number now), because the seven vibrations are caused by radio if I remember right.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have searched the entire rumrunner thread from here http://forum.xda-developers.com/showthread.php?t=2630531.
But I couldn't find any radio partitions or whatsoever. All there is are hboot images which I cannot flash because of my screwed up model id; I get the error
41 Model Id check fail
Click to expand...
Click to collapse
.
Am I looking in the wrong place? Where could I find a radio partition?
Could someone help me out with some block partitions from our device?
How can I check if device has ENG hboot?
Guys...If u are begginer why u complicate everything with S-OFF I never had issue like this.... =] And I dont see need to do S-OFF.
Sent from my HTC Desire X using Tapatalk
mefistoreyon said:
Guys...If u are begginer why u complicate everything with S-OFF I never had issue like this.... =] And I dont see need to do S-OFF.
Sent from my HTC Desire X using Tapatalk
Click to expand...
Click to collapse
You are right. But for me it's too late. Can't manage to do anything now with my softbricked device
Actually I bricked many times my phone ,but without S-OFF.And for that I think Im not able to help
One really stupid qestion.
What If to flash stock recovery+stock boot.img ?...
I will try it.
Sent from my LG-P500 using XDA Free mobile app
hey guys
i brick my phone too with exactly same var but without s-off i'm with s-on and i still can't unbrick it i try 2 stock roms but nothing.. :/ (sorry for my bad english)
This is what happens when someone doesn't read carefully ?
ICS AOKP builds are based on buggy sources and not maintained for years.
Odesláno z mého HTC Desire X pomocí Tapatalk
dfvikicha said:
i brick my phone too with exactly same var but without s-off i'm with s-on and i still can't unbrick it i try 2 stock roms but nothing.. :/ (sorry for my bad english)
Click to expand...
Click to collapse
Maybe u already know but...When u flash stock rom u have to flash too stock boot.img and recovery i think.Anyway if u are with ics hboot u can use RUU
I've sent mine back to service. Waiting to see if they fix it (it's still in waranty but you know...)
My desire x came back from service today. They replaced its motherboard!
Related
Hi guys,
I just wanted to write this post to help anybody who lost imei number because I've lost too.. Thanks for helpskotag82
If you lost your imei number (after root, unlock or something else) this means your efs directory has failed. Maybe removed (my efs was removed). In this situation, follow with these steps:
Relock your bootloader (Look this thread: http://forum.xda-developers.com/showthread.php?t=1994961)
Enter bootloader and connect with computer with a cable (Also you can enter with using toolkit that given first step)
Choose and download RUU for your mobile (You can download from this link: http://htcruu.com/?dir=ENRC2B )
Install RUU by following Instal Shiled's steps
And then your mobile is back!
NOT:You will lose your data so if you can, backup them. Your device get back to first situation (factory building).
Thanks.
dmrc1143 said:
Hi guys,
I just wanted to write this post to help anybody who lost imei number because I've lost too.. Thanks for helpskotag82
If you lost your imei number (after root, unlock or something else) this means your efs directory has failed. Maybe removed (my efs was removed). In this situation, follow with these steps:
Relock your bootloader (Look this thread: http://forum.xda-developers.com/showthread.php?t=1994961)
Enter bootloader and connect with computer with a cable (Also you can enter with using toolkit that given first step)
Choose and download RUU for your mobile (You can download from this link: http://htcruu.com/?dir=ENRC2B )
Install RUU by following Instal Shiled's steps
And then your mobile is back!
NOT:You will lose your data so if you can, backup them. Your device get back to first situation (factory building).
Thanks.
Click to expand...
Click to collapse
is there a way to back up your imei?
Andrew149 said:
is there a way to back up your imei?
Click to expand...
Click to collapse
Yes. By copying your efs folder, you can move your IMEI to a safe zone (pc, sd card..) or you can back up with some application but I don't know these applications will run HOX+.. I haven't tried before.
HTC one x lost the IMEI and baseband
So I bumped into this thread although I dont have the htc one x+.
I have the HTC one x international model. I lost the baseband and IMEI: possibly corrupted efs folder. I dont have the backup. Do you think these instructions work in my case.
Also I cant seem to access htcruu.com website is there another website where I can download it.
http://androidfiles.org/ruu/
The biggest problem should be to get the newer RUUs, necessary through new firmware...
That site doesnt have RUU for one x. Any other reliable places My CID is 001.
thanks.
if you are able to get the RUU, is it possible to fix the IMEI issue?
spacemango80 said:
That site doesnt have RUU for one x. Any other reliable places My CID is 001.
thanks.
Click to expand...
Click to collapse
It has have look here newest one is 3.14.401.31, it is last one on the list... to be sure you need to post your full CID (HTC__001)
spacemango80 said:
if you are able to get the RUU, is it possible to fix the IMEI issue?
Click to expand...
Click to collapse
OP solved his IMEI problem by flashing RUU
kotag82 said:
It has have look here newest one is 3.14.401.31, it is last one on the list... to be sure you need to post your full CID (HTC__001)
OP solved his IMEI problem by flashing RUU
Click to expand...
Click to collapse
Yes I flashed this ROM but still my IMEI and baseband are unknown.
Cant connect to network..
thanks
one x imei
so i just got my new htc one today and i want to mess around with my one x a bit, i have seen loads of stuff about imei unlock and change and thing but how can i imei unlock to use anywhere in the world?
whats with this change imei? how would that benifit the handset?
New User
dmrc1143 said:
Hi guys,
I just wanted to write this post to help anybody who lost imei number because I've lost too.. Thanks for helpskotag82
If you lost your imei number (after root, unlock or something else) this means your efs directory has failed. Maybe removed (my efs was removed). In this situation, follow with these steps:
Relock your bootloader (Look this thread: http://forum.xda-developers.com/showthread.php?t=1994961)
Enter bootloader and connect with computer with a cable (Also you can enter with using toolkit that given first step)
Choose and download RUU for your mobile (You can download from this link: http://htcruu.com/?dir=ENRC2B )
Install RUU by following Instal Shiled's steps
And then your mobile is back!
NOT:You will lose your data so if you can, backup them. Your device get back to first situation (factory building).
Thanks.
Click to expand...
Click to collapse
Hello i'm a new user for HTC one x + 64G i bought it about a week ago and i found the ROM is customized and the device is unlocked , i would like a help from you or any one in the following :
1- is the ROM for HTC one x plus is the same as HTC one x ? i mean can i install stock rom from htc one X
2- where can i find stock ROM support Arabic Keyboard ?
i've tried to restore factory default but still the same rom as there is no backup .
thanks
7emoo said:
Hello i'm a new user for HTC one x + 64G i bought it about a week ago and i found the ROM is customized and the device is unlocked , i would like a help from you or any one in the following :
1- is the ROM for HTC one x plus is the same as HTC one x ? i mean can i install stock rom from htc one X
2- where can i find stock ROM support Arabic Keyboard ?
i've tried to restore factory default but still the same rom as there is no backup .
thanks
Click to expand...
Click to collapse
Hey,
1.ROM differ from phone to phone, you can't install HTC One X rom to HTC One X +
2.try some keyboards like swift key etc, I am using this as my default settings.
It supports multiple languages
Greetings
Sent from my HTC One X+ using xda premium
got this issue when trying to flash CM10.1... this helped to get me back working again. Need to yet try pushing that CM again...
Having the same issue...
have u solved the problem....
Info:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.35.0000
(bootloader) version-baseband: 3.1204.168.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.17.401.1
(bootloader) serialno: FAXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXXX
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3761mV
(bootloader) devpower: 37
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
crazy_kamal said:
Having the same issue...
have u solved the problem....
Info:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.35.0000
(bootloader) version-baseband: 3.1204.168.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.17.401.1
(bootloader) serialno: FAXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXXX
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3761mV
(bootloader) devpower: 37
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
I have the same problem. Until now, nothing (restore of cwm-/twrp-backup, flash the boot.img and so on) worked succesfully to restore the imei. I will be very happy if someone has the one-right-solution for this problem. Thanks in advance....
PS: i have hboot 1.40
thx
Thanks,dude
I get back my lost imei number very fast!!
hey everyone, i have the one x + at&t device running viperxl 1.1.0. hboot is 1.32.0000. i have lost my imei. following the op is to get the hasoon toolkit http://forum.xda-developers.com/showthread.php?t=1994961. unfortunately it looks as though that thread is locked and download links have been removed. is there any other way to lock the bootloader without the toolkit?
I've downloaded the proper ruu but stuck on this bootloader issue. Any advice would be very much appreciated.
Leebert225 said:
hey everyone, i have the one x + at&t device running viperxl 1.1.0. hboot is 1.32.0000. i have lost my imei. following the op is to get the hasoon toolkit http://forum.xda-developers.com/showthread.php?t=1994961. unfortunately it looks as though that thread is locked and download links have been removed. is there any other way to lock the bootloader without the toolkit?
I've downloaded the proper ruu but stuck on this bootloader issue. Any advice would be very much appreciated.
Click to expand...
Click to collapse
Are you s-off or s-on ? S-on carry on reading. s-off - doesn't need relocked bootloader
You should lock boot loader with
fastboot oem lock
That is the reason for hansoon toolkit ... Do it proper old fashion way
Be aware RUU WILL WIPE YOUR SD card
Sent from my HTC One using xda premium
kotag82 said:
Are you s-off or s-on ? S-on carry on reading. s-off - doesn't need relocked bootloader
You should lock boot loader with
fastboot oem lock
That is the reason for hansoon toolkit ... Do it proper old fashion way
Be aware RUU WILL WIPE YOUR SD card
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks, got it fixed!
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
TopoX84 said:
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did just as you posted this, thanks!
codejunkie83 said:
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
or you could try this which is supposed to be the latest version that at&t has gotten out
http://androidromupdate.com/2013/10/09/att-htc-one-official-4-3-ota-update-stock-ruu-3175023/
Sent from my HTC One using xda app-developers app
TopoX84 said:
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
EDIT: I also tried that latest AT&T version from androidromupdate, but it failed the same
codejunkie83 said:
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
Click to expand...
Click to collapse
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Okay, seems like I've followed all of those steps. I ran fastboot oem lock, but each time I try the RUU I get the 155 message. I had just installed the latest HTC drivers last week, as that was when I went to the GPE. I'm using the same USB port that I had been using then, so no differences there.
Thank you for your responses - if you need any more information I'll be glad to give it.
TopoX84 said:
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Click to expand...
Click to collapse
Okay, so one thing that I have noticed - my main versions seems to be X.XX.1540.X, which as best I can tell is the US Dev Edition. However, my CID is CWS_001, which should have X.XX.502.X as the main version. Unfortunately, I think the conflict here is causing my RUUs to fail. Any suggestions?
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
codejunkie83 said:
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
Click to expand...
Click to collapse
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
mb_guy said:
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
codejunkie83 said:
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
Click to expand...
Click to collapse
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
mb_guy said:
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
Click to expand...
Click to collapse
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
codejunkie83 said:
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
Click to expand...
Click to collapse
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
BTW: have you tried "fastboot oem unlock" again
mb_guy said:
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
Click to expand...
Click to collapse
Thanks, will do!
Hey, I don't know where to start from...
I just bought a Sprint HTC One Max yesterday and I was happy to S-Off and Root it, so I followed this guide... http://forum.xda-developers.com/showthread.php?t=2550559
I followed every instruction all the way down the Step 4c. At Step 4d I got confused and skipped to 4f which is "Issue the command fastboot flash boot boot.img" after that my phone went from the HTC logo starting over and over to it being stuck in bootloader mode. Now I can't do a Factory Reset or a Recovery.
I've tried to go back to stock and flash this RUU file: 0P3PIMG_T6_WHL_JB43_SENSE55_SPCS_Sprint_WWE_1.14.651.1_Radio_1.30.50.1022_NV_SPCS_4.50_003_release_338466_signed_2.zip
During the flashing process, I got two errors
FAILED (remote: 43 main version check fail)
FAILED (remote: 12 singature verify fail)
I am new to this and something told me to just wait but I didn't listen. If anyone could help me, I would really appreciate it, I just got this phone yesterday and I didn't even get to use any features, because I was too eager to S-OFF and Root. All I want to do is go back to stock, play games on my new phone and never attempt to root or S-Off again. =,(
Thanks!
-----------------------------------------------------------------------------------
If this helps, my bootloader screen says this:
***TAMPERED***
***RELOCKED***
***Security Warning***
T6WHL PVT SHIP S-ON RH
HBOOT-2.46.0000
RADIO-v33.120.274_T6.0829
QSC-
OS-1.16.651.4
eMMC-boot 2048MB
Nov 6 2013,17:04:11.0
------------------------------------------------------------------------------------
My fastboot getvar all results
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.46.0000
(bootloader) version-baseband: 1.35.50.1106
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.651.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000428505809
(bootloader) product: t6whl
(bootloader) platform: HBOOT-8064
(bootloader) modelid: 0P3P70000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4118mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-70784205
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
You should have used firewater. Look that up, it's quick, easy, and you don't need HTCdev.
Sent from my HTC One Max using Tapatalk!
gimmeitorilltell said:
You should have used firewater. Look that up, it's quick, easy, and you don't need HTCdev.
Sent from my HTC One Max using Tapatalk!
Click to expand...
Click to collapse
I wanted to but I didn't want to know where to start, so I just went ahead and used Punk9's guide.
This forum is for the Sprint HTC One . This belongs in the HTC one max forum
Sent from my HTCONE using xda app-developers app
pelon90005 said:
This forum is for the Sprint HTC One . This belongs in the HTC one max forum
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Sorry, how do I move it to the HTC One Max section?
You can message a moderator and ask that it be moved to the one max q&a thread.
Sent from my HTC One Max using Tapatalk!
Can someone tell me what RUU file I need to download?
Jet_Life said:
Can someone tell me what RUU file I need to download?
Click to expand...
Click to collapse
It looks like you had the right RUU file... But anyways you can get to your bootloader so you aren't bricked.. I believe if you search around someone posted all the phones image files ex: system.img recovery.img boot.img etc etc.. Grab those and fastboot them back to the phone. It already sounds like your terminal talks to your boot loader via fastboot so it would be "fastboot devices" make sure you get your devices serial number then "fastboot flash boot boot.img" fastboot flash recovery recovery.img" "fastboot flash system system.img" etc etc hit me up if you need some help
Murrda said:
It looks like you had the right RUU file... But anyways you can get to your bootloader so you aren't bricked.. I believe if you search around someone posted all the phones image files ex: system.img recovery.img boot.img etc etc.. Grab those and fastboot them back to the phone. It already sounds like your terminal talks to your boot loader via fastboot so it would be "fastboot devices" make sure you get your devices serial number then "fastboot flash boot boot.img" fastboot flash recovery recovery.img" "fastboot flash system system.img" etc etc hit me up if you need some help
Click to expand...
Click to collapse
For some reason, I unlocked my bootloader and my phone started right up, so I finished Punk9's guide and now I am ROOTED & have S-OFF. Thanks for the help though!!!
Is there an RUU for Verizon One Max?
I saw a pointer for Sprint and Intl, but not for
Verizon. I asked HTC support, they said
VZW wont let them distribute it.
Thanks
fuzzynco said:
I saw a pointer for Sprint and Intl, but not for
Verizon. I asked HTC support, they said
VZW wont let them distribute it.
Thanks
Click to expand...
Click to collapse
Distribute what? If your talking bout vzw Ruu there is one.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
yes, that is what I meant
thayl0 said:
Distribute what? If your talking bout vzw Ruu there is one.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do you have a link to the post or the download?
fuzzynco said:
Do you have a link to the post or the download?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2587336
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Thanks... got it.
Murrda said:
It looks like you had the right RUU file... But anyways you can get to your bootloader so you aren't bricked.. I believe if you search around someone posted all the phones image files ex: system.img recovery.img boot.img etc etc.. Grab those and fastboot them back to the phone. It already sounds like your terminal talks to your boot loader via fastboot so it would be "fastboot devices" make sure you get your devices serial number then "fastboot flash boot boot.img" fastboot flash recovery recovery.img" "fastboot flash system system.img" etc etc hit me up if you need some help
Click to expand...
Click to collapse
Sorry to bother you, but, you would happen to know how to flash to Cricket from Sprint would you?
Hi everyone,
i have just one "easy" question.
How can i install AOKP ROM Here an HTC Desire X with hboot 1.25 ?
I dont want get golden card.
Thank you
http://forum.xda-developers.com/showthread.php?t=2213663
MrHackCZ said:
Hi everyone,
i have just one "easy" question.
How can i install AOKP ROM Here an HTC Desire X with hboot 1.25 ?
I dont want get golden card.
Thank you
Click to expand...
Click to collapse
I wouldn't recommend to install this ROM because it is unstable and there is no support anymore from the developer. So if you experience problems after this, you will be on your own. You have been warned.
I'm screwed
I tried to flash this AOKP rom like a dumbass....I forgot I was on hboot1.25 and flashed it.
Now phone doesn't boot.
I can't acces recovery.
All I can acces is fastboot.
I have a back-up on sd but cannot acces it because the recovery seems to be broken or something. Any advice on what should I do guys?
You can access recovery, so just reflash recovery through fastboot with fastboot flash recovery recovery.img (choose appropriate recovery for 1.25 hboot)
BTW
Maybe soon someone will port AOKP ROM based on CM 10 who is almost stable.
Sent from my HTC Desire X using Tapatalk
dansou901 said:
You can access recovery, so just reflash recovery through fastboot with fastboot flash recovery recovery.img (choose appropriate recovery for 1.25 hboot)
Click to expand...
Click to collapse
I tried many times to reflash recovery through fastboot but although it says it was succesfull I still cant enter recovery. The sreen just hangs saying "entering recovery" but nothing happens.
Something got really screwed up and I really dont know what to do.
dodialfaed said:
I tried many times to reflash recovery through fastboot but although it says it was succesfull I still cant enter recovery. The sreen just hangs saying "entering recovery" but nothing happens.
Something got really screwed up and I really dont know what to do.
Click to expand...
Click to collapse
Try to reformat cache from fastboot by typing fastboot erase cache
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
Try to reformat cache from fastboot by typing fastboot erase cache
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I also erased cache every time.
I did this:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Still no succes :crying:
And another strange thing, because I'm S-off every time I used to enter recovery the phone vibrated several times but now it only vibrates one time.
Which recovery do you try to flash?
Sent from my HTC Desire X using XDA Premium 4 mobile app
I tried TWRP and PhilzTouch - the jb versions
---------- Post added at 06:08 PM ---------- Previous post was at 05:14 PM ----------
If I do getvar all in fastboot I get the following:
Code:
(bootloader) version-bootloader: 1.25.0002
(bootloader) version-baseband: 1.15.40.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: u�n�g"�a6����
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: ���e����(����Q�~���Q��=��/ `oj\
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-02bbe6c44f94272745d8398b32e3f3e4f
getvar:all FAILED (unknown status code)
finished. total time: 0.067s
It seems thast serial number and model id are corrupted.
What now?
Seems like you are in bad luck and you have a paperweight now... At least I don't know a way of reviving anymore. Maybe it could be resolved using JTAG...
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
Seems like you are in bad luck and you have a paperweight now... At least I don't know a way of reviving anymore. Maybe it could be resolved using JTAG...
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah. Thanks anyway. I'm gonna try my luck in Q&A Troubleshooting forum and if that doesn't work out I'll just S-on and relock bootloader and send it to service saying that it was a bad udate or something. (it's still in waranty)
Did you ever try this recovery ? http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66 btw there was a way to make boothloader LOCKED instead of RELOCKED.
Take the S-OFF and downgrade your HBOT to 1.24. Then flash this ROM. PS: I recommend the new AOKP ROM for HBOT 1.25 (It's Android 4.1.2) http://forum.xda-developers.com/showthread.php?t=2764335 Good luck!
PepinCZ said:
Take the S-OFF and downgrade your HBOT to 1.24. Then flash this ROM. PS: I recommend the new AOKP ROM for HBOT 1.25 (It's Android 4.1.2) http://forum.xda-developers.com/showthread.php?t=2764335 Good luck!
Click to expand...
Click to collapse
He can't do S-OFF as he is not able to boot the phone!
I hope not to make a duplicate thread but sorry if I do.
I took on this project trying to help a friend out. This is the first VZW phone I've operated on. I've been to multiple threads on different websites and tried various procedures all to no avail.
This phone was all stock b4 the update....tried to take the update and has been in a bootloop ever since.....phone gets stuck at the white HTC quite briliant screen.
I've tried unlocking the bootloader via revone but for some reason adb will not recognize the phone....although fastboot commands are not a problem....
I'm almost at the point of installing some linux distro just so I can try moonshine..
I've tried 2 different RUU's for this phone....both fail....
HTCdev failed me also.....couldnt get the token....smh
Turning the phone back in to VZW wasnt an option because is was opened previously...warranty voided.
any help would be good help as far as I'm concerned.
I'm still trying to figure out how to find out what firmware is on the phone....and I take it "fastboot getvar all" doesnt tell you that...
On both RUU's that I have...they tell me that I have image 4.09.(xxx) <---I cant remember the last digits right now
**SOLVED** HERE'S THE THREAD THAT HELPED ME. https://forum.xda-developers.com/droid-dna/general/official-exe-ruus-s-t2935556
MUCH THANKS TO @dottat :good::good:
DuceTheTruth said:
I hope not to make a duplicate thread but sorry if I do.
I took on this project trying to help a friend out. This is the first VZW phone I've operated on. I've been to multiple threads on different websites and tried various procedures all to no avail.
This phone was all stock b4 the update....tried to take the update and has been in a bootloop ever since.....phone gets stuck at the white HTC quite briliant screen.
I've tried unlocking the bootloader via revone but for some reason adb will not recognize the phone....although fastboot commands are not a problem....
I'm almost at the point of installing some linux distro just so I can try moonshine..
I've tried 2 different RUU's for this phone....both fail....
HTCdev failed me also.....couldnt get the token....smh
Turning the phone back in to VZW wasnt an option because is was opened previously...warranty voided.
any help would be good help as far as I'm concerned.
I'm still trying to figure out how to find out what firmware is on the phone....and I take it "fastboot getvar all" doesnt tell you that...
On both RUU's that I have...they tell me that I have image 4.09.(xxx) <---I cant remember the last digits right now
Click to expand...
Click to collapse
We will need the info on the bootloader screen, all of it please. It will provide info which can be useful
.torrented said:
We will need the info on the bootloader screen, all of it please. It will provide info which can be useful
Click to expand...
Click to collapse
Thanks for replying....
***LOCKED*****
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.01.1112
OpenDSP-v-10.120.274.0520
OS-4.09.605.1
eMMC-boot 2048MB
Mar 13 2014, 19:19:14.0
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4225mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
DuceTheTruth said:
Thanks for replying....
***LOCKED*****
MONARUDO PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.01.1112
OpenDSP-v-10.120.274.0520
OS-4.09.605.1
eMMC-boot 2048MB
Mar 13 2014, 19:19:14.0
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4225mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
Click to expand...
Click to collapse
I can tell you that the phone is indeed on the latest update, bootloader, baseband, and version-main all indicate that it is on the 4.09.605.1 update, have you tried to do a factory reset from within the bootloader/stock recovery?
That may help, may not. since you are locked and s-on, there really isnt much else to do.
Just for the heck of it, have you tried to flash the flashable RUU-ROM.zip from my firmware thread? Probably wont work but idk what else there is to do, being as you are still stock and locked.
.torrented said:
I can tell you that the phone is indeed on the latest update, bootloader, baseband, and version-main all indicate that it is on the 4.09.605.1 update, have you tried to do a factory reset from within the bootloader/stock recovery?
That may help, may not. since you are locked and s-on, there really isnt much else to do.
Just for the heck of it, have you tried to flash the flashable RUU-ROM.zip from my firmware thread? Probably wont work but idk what else there is to do, being as you are still stock and locked.
Click to expand...
Click to collapse
Interesting.....
I have tried the factory reset in the bootloader and it just goes to a picture of a green down arrow with two green arrows in a circle facing clockwise.... Then goes back to white HTC screen...
And I did try the flashable RUU zip.... And I will try it again..
Is it true that have to unlock the bootloader before anything else?
I'm searching for ways to do that while in this bootloop state....
And then possibly downgrading?
And if this phone really is stuck I feel that Verizon is at fault here.. . Even if it was dropped and the back came off....
My friend told me that at the time the update came through he had very little memory....
And I've read elsewhere that the exact same issue caused similar problems on some phones....
I'm surprised there's no class action on the horizon.
Htc black screen with four triangles
Man I really need help. ...I tried to flash and something went wrong to where I erased the entire os and I continued to fix this issue because all I had access to was twrp(custom rom) and bootloader. then what was crazy is that it appeared that based on the fact that I was on 4.4.2 kit kat that I was unable to fix it. after researching I found a ruu that didn't have the boot image so I flashed the factory ruu with no boot image and my htc scrren with the status bar filled all the way up but it never moved off of that screen I assume because that ruu didn't have the boot image so I thought that common sense would be to at one of the boot images that I had to the zip file of the ruu without the boot image....that's when I made things worst and now im stuck on this htc screen with the four triangles...my pc wont detect my device and im in need of some serious help....can you help? can anybody help?
I believe i can help!!!
ducethetruth said:
interesting.....
I have tried the factory reset in the bootloader and it just goes to a picture of a green down arrow with two green arrows in a circle facing clockwise.... Then goes back to white htc screen...
And i did try the flashable ruu zip.... And i will try it again..
Is it true that have to unlock the bootloader before anything else?
I'm searching for ways to do that while in this bootloop state....
And then possibly downgrading?
And if this phone really is stuck i feel that verizon is at fault here.. . Even if it was dropped and the back came off....
My friend told me that at the time the update came through he had very little memory....
And i've read elsewhere that the exact same issue caused similar problems on some phones....
I'm surprised there's no class action on the horizon.
Click to expand...
Click to collapse
whats your current status? I just got myself out of a very bad situation with my htc dna just read some of the stuff ive posted in your thread.....are you s-off or s-on?
CHRIST STARZ said:
whats your current status? I just got myself out of a very bad situation with my htc dna just read some of the stuff ive posted in your thread.....are you s-off or s-on?
Click to expand...
Click to collapse
it is s-on
I'm in the same boat. OTA update crashed and now phone wont boot. It's S-ON with the latest radio and hboot. Apparently you can't downgrade with an older RUU. I cannot seem to find a 4.09.605.5 RUU anywhere. Any suggestions?
Thanks
-CMY
cmylxgo said:
I'm in the same boat. OTA update crashed and now phone wont boot. It's S-ON with the latest radio and hboot. Apparently you can't downgrade with an older RUU. I cannot seem to find a 4.09.605.5 RUU anywhere. Any suggestions?
Thanks
-CMY
Click to expand...
Click to collapse
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
carl1961 said:
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
Click to expand...
Click to collapse
Yah...I was able to recover with some other files. But I have downloaded this and archived it just in case I run into problems in the future. Thanks!
-CMY
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
Here is what I used to resolve my issues back in Nov...
http://forum.xda-developers.com/showpost.php?p=56405268&postcount=4
-CMY
carl1961 said:
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
Click to expand...
Click to collapse
That's a rom BTW, and won't flash on an S-on phone. S-on requires encrypted and signed images to restore.
Hence ruu
carl1961 said:
probably way late
https://www.androidfilehost.com/?fid=95747613655040155
Click to expand...
Click to collapse
man....i just pulled this phone out the drawer and wiped the dust off lol.....
now im trying to figure out how to make this work
thanks for the post by the way