Is my M9 IS DEAD?PLEADE HELP - One (M9) Q&A, Help & Troubleshooting

i tried to install a new rom and somthing went wrong.i cant go into recovery just to download mode.
Can i fix it ?please?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It surely isnt dead if download mode works.

What'd you try to install?
Sent from my HTC One M9 using Tapatalk

What happens when try to go to recovery?

Locked bootloader + custom recovery is usually a recipe for trouble. When did you relock? And, I sure hope you checked "allow OEM unlock" in developer settings or you may indeed have a brick on your hands.

The thing is i advertise for a friend.he told he tried to go back on stock rom and he locked the boatloader

Its ok he marked that option.the thing is i need to burn a new ruu?and his version his 2.10.401.1 and there is ruu for that version.
Can i downgrage the ruu version by flashing an old version?

If you can get to download mode, you can flash the appropriate RUU and start over. I'd recommend doing that.

idoguy said:
Its ok he marked that option.the thing is i need to burn a new ruu?and his version his 2.10.401.1 and there is ruu for that version.
Can i downgrage the ruu version by flashing an old version?
Click to expand...
Click to collapse
Only if you are s-off.

idoguy said:
Its ok he marked that option.the thing is i need to burn a new ruu?and his version his 2.10.401.1 and there is ruu for that version.
Can i downgrage the ruu version by flashing an old version?
Click to expand...
Click to collapse
You're s-on, so you're stuck with the firmware you have. A 2.xx.401 ruu should work if you can find one.

Is it possible to find one?I tried and didnt find any

I found this is it good?
http://forum.xda-developers.com/one-m9/help/htc-one-m9-stock-2-10-401-1-t3221074

You're already on 2.10, correct? That ruu will not run because you're s-on. I don't know if there is a signed 2.10.401 ruu out there.

So i cant do anything about that am i right?except waiting.

idoguy said:
So i cant do anything about that am i right?except waiting.
Click to expand...
Click to collapse
Just keep the boot loader relocked and use the same software number you have
Don't try downgrade you're S-on you will Brick your m9
What happened to you is you lost the OS and need flash firmware to fix that BUT YOUR M9 S-ON DON'T FLASH FIRMWARE ON S-ON
you can flash the firmware with using RUU.EXE the same software number
My best
Sent from my HTC One_M8 using Tapatalk

This is the latest wwe rom in zip format. https://drive.google.com/file/d/0B4vTiHTBB629cHFFNTF4Zzd4Rjg/view?usp=docslist_api dont know if itll help any.
I wish I stole my HTC M9.

KARIM9377 said:
Just keep the boot loader relocked and use the same software number you have
Don't try downgrade you're S-on you will Brick your m9
What happened to you is you lost the OS and need flash firmware to fix that BUT YOUR M9 S-ON DON'T FLASH FIRMWARE ON S-ON
you can flash the firmware with using RUU.EXE the same software number
My best
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
you are telling him wrong things my friend.
at first he can't even downgrade because the phone is s-on. therefore no way to brick.
he can Flash the Firmware with unlocked bootloader. he just Need the proper one for his Software number / CID
he also can at first unlock again the bootloader, Flash a custom recovery and Flash ARHD for example to s-off the device if he owner allows that.. but i think it's better not to s-off, otherwise the owner will brick it most likely next Time

DeeZZ_NuuZZ said:
you are telling him wrong things my friend.
at first he can't even downgrade because the phone is s-on. therefore no way to brick.
he can Flash the Firmware with unlocked bootloader. he just Need the proper one for his Software number / CID
he also can at first unlock again the bootloader, Flash a custom recovery and Flash ARHD for example to s-off the device if he owner allows that.. but i think it's better not to s-off, otherwise the owner will brick it most likely next Time
Click to expand...
Click to collapse
That is what I told him to do
Don't downgrade on s-on and even can't flash firmware on s-on
The best way to recover your phone is RUU check fastboot getvar
And use the same software number you have and cid
That is all
Thank you my friend @DeeZZ_NuuZZ
Sent from my HTC One_M8 using Tapatalk

KARIM9377 said:
That is what I told him to do
Don't downgrade on s-on and even can't flash firmware on s-on
The best way to recover your phone is RUU check fastboot getvar
And use the same software number you have and cid
That is all
Thank you my friend @DeeZZ_NuuZZ
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
lol i see now that i wrote unlocked instead of re-locked bootloader when he want to flash signed firmware.zip since only that can work for s-on

Thank you all guys but iam not following .can i fix this phone without waiting for the ruu file?becuase i havent found it online.
is there another way?

Related

[Q] Please let me know How to S-On after AlphaRevX S-Off

How to restore S-On after AlphaRevX S-Off on my htc desire.
i flashed many RUU's but none of them works for me. now i am unrooted but s-off.
i want s-on??
maniacscorpio said:
How to restore S-On after AlphaRevX S-Off on my htc desire.
i flashed many RUU's but none of them works for me. now i am unrooted but s-off.
i want s-on??
Click to expand...
Click to collapse
Flashing RUU should restore your phone to its original software. Did you install the proper drivers when you attempted to flash the RUU ?
The safest way to approach this operation is to install HTC Sync and then attempt to flash the proper RUU. Here is a list of RUUs. Please check if your phone is branded and post additional information on the reason of flash failure.
paul.c said:
Flashing RUU should restore your phone to its original software. Did you install the proper drivers when you attempted to flash the RUU ?
The safest way to approach this operation is to install HTC Sync and then attempt to flash the proper RUU. Here is a list of RUUs. Please check if your phone is branded and post additional information on the reason of flash failure.
Click to expand...
Click to collapse
i tried many RUU but no success...... i did it with proper method..
hboot stills shows s-off
maniacscorpio said:
i tried many RUU but no success...... i did it with proper method..
hboot stills shows s-off
Click to expand...
Click to collapse
Well, obviously you missed something. Did you boot your phone in fastboot (back button + power) ?
paul.c said:
Well, obviously you missed something. Did you boot your phone in fastboot (back button + power) ?
Click to expand...
Click to collapse
yes i can....
guys read alpharev.nl
search downgrade
omg lol you people are useless.
Go to the alpharev.nl website and download the "downgrader". Flash it over fastboot like you would any Hboot, THEN run the RUU. This will return it back to S-ON
bortak said:
omg lol you people are useless.
Go to the alpharev.nl website and download the "downgrader". Flash it over fastboot like you would any Hboot, THEN run the RUU. This will return it back to S-ON
Click to expand...
Click to collapse
i am bit confused which file should i flash?? can you help me??
i dnt wanna that wrong hboot image will make my phone brick..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
alphaxrev also mentioned -
PHP:
Will my phone stay S-OFF forever?
Yes and no. [B][COLOR="Red"]As soon as you decide to flash a stock RUU that has a HBOOT update in it, this hacked HBOOT will be overwritten.[/COLOR][/B]
You do have the option to remove the HBOOT update from the rom.zip inside the RUU. Since your phone no longer checks signatures, you could easily do that.
Also, you then still have the option to flash custom recovery, or different kernels using the fastboot functions described above (fastboot flash, et al).
i already update new RUU nothing happened. even i updated to new 2.3 nothing happens again??

[FAILED] Another S-OFF Theory

Hey guys.
The HTCDEV RUU for 2.13.401.2 has 2 update packages
rom01.zip and rom02.zip.
rom01.zip was told to S-OFF the device.
Now someone found out, how to downgrade (http://forum.xda-developers.com/showthread.php?t=1445867)
And now I ask myself, if it would be possible to S-OFF downgrading to 2.13.401.2 again and then only flash the rom1.zip.
I just concluded 2 facts that go around here.
1. You can downgrade and then flash the 2.13.401.2 RUU again
2. The rom01.zip makes S-OFF.
So, anybody tried that?
Would be nice if anybody could try who gets the downgradeing working.
theq86 said:
Hey guys.
The HTCDEV RUU for 2.13.401.2 has 2 update packages
rom01.zip and rom02.zip.
rom01.zip was told to S-OFF the device.
Now someone found out, how to downgrade (http://forum.xda-developers.com/showthread.php?t=1445867)
And now I ask myself, if it would be possible to S-OFF downgrading to 2.13.401.2 again and then only flash the rom1.zip.
I just concluded 2 facts that go around here.
1. You can downgrade and then flash the 2.13.401.2 RUU again
2. The rom01.zip makes S-OFF.
So, anybody tried that?
Would be nice if anybody could try who gets the downgradeing working.
Click to expand...
Click to collapse
Great but someone should make an ruu that only contains rom1.zip what do you guys think?
I'm on my phone...........
A RUU is not neccessary. Just extract rom01.zip from the official htcdev RUU, rename it PG76IMG.zip, put on SD, go into HBOOT and let the magic play.
But this requires a working downgrade to 2.13.401.2. Then we should be able to flash this thing.
Okay ...
Although I flashed my misc partition and double-checked if it was changed and flashed correctly, I was not able to run any RUU that is below my software version.
I have no clue why it does not work, because several users reported it working.
It may also be, that the brand new HTCDEV RUU for 2.13.401.3 did fix that exploit (I bet HTC is reading xda-dev and learns how to spit in our soup)
So, conclusion is: Not able to downgrade -> not able to flash the old HTCDEV radio -> no S-OFF this way.
Maybe somebody else can test it, too. Maybe anyone is still on 2.13.401.2.
but for now, this method is not working
theq86 said:
Okay ...
Although I flashed my misc partition and double-checked if it was changed and flashed correctly, I was not able to run any RUU that is below my software version.
I have no clue why it does not work, because several users reported it working.
It may also be, that the brand new HTCDEV RUU for 2.13.401.3 did fix that exploit (I bet HTC is reading xda-dev and learns how to spit in our soup)
So, conclusion is: Not able to downgrade -> not able to flash the old HTCDEV radio -> no S-OFF this way.
Maybe somebody else can test it, too. Maybe anyone is still on 2.13.401.2.
but for now, this method is not working
Click to expand...
Click to collapse
Wish I could try it but I'm stuck with 2.17.531.1
EDIT: Do you have a copy of rom01.zip that I could try?
Yes, but since i'm over my volume my internet speed was reduced. upload would take forever :/
rom01.zip does not make S-OFF. It does actually nothing important. Just flashes the new radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img. Hboot and radio are still locked. See:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The software version in the misc partition starts from 0x000000A0. If you want to enter 2.13.401.2, change the number to
Code:
32 2E 31 33 2E 34 30 31 2E 32 [b]00 00 00 ...[/b]
Current bootloader status starts from 0x000000E0. HTCU (48 54 43 55 00 00 ...) - means unlocked, HTCL (48 54 43 4C 00 00 ...) - means (re)/locked.
PS. Remember to relock the bootloader (>fastboot oem lock). Without that you won't be able to flash PG76IMG.zip. Good luck.
so what about all the people reporting to be s-off after flashing rom_01.zip`? just a myth?
misc.img give info about the OS version.
hboot version is checked somewhere else, phone will block downgrading hboot i think...
But it might be possible, with inner exploit what would not even work, i'm not so deep in android, upgrading hboot to newer what will exploit itself to downgrade, in theory would work, but its only an theory, if phone exploits itself's we can get s-off easly.
If i'm wrong sorry, its just my way of logic thinking ^^
theq86 said:
so what about all the people reporting to be s-off after flashing rom_01.zip`? just a myth?
Click to expand...
Click to collapse
Look at the picture from my previous post - I flashed rom_01.zip - radio was changed to 7.54.39.08M and phone was still S-ON. As you know there is only one update with 7.54.39.08M radio (mentioned htcdev ruu). So yes, I think it's a myth.
Unkheq said:
misc.img give info about the OS version.
Click to expand...
Click to collapse
Yes, that's right but
Unkheq said:
phone will block downgrading hboot i think...
Click to expand...
Click to collapse
is not. Updating requires only a suitable software version. If the update RUU/zip file is signed and android-info.txt contains hbootpreupdate:0 or hbootpreupdate:13 the bootloader would be flashed. If there is hbootpreupdate:12 (i saw only one RUU) only a newer bootloader would be flashed.
Okay, after some experiments and successful downgrading I can tell:
At least the EU version of the 2.33.401.2 HTCDEV rom_01.zip makes no S-OFF (not even after downgrading to any lower version)
so this is definately a myth and not working.
rezo said:
Look at the picture from my previous post - I flashed rom_01.zip - radio was changed to 7.54.39.08M and phone was still S-ON. As you know there is only one update with 7.54.39.08M radio (mentioned htcdev ruu). So yes, I think it's a myth.
Click to expand...
Click to collapse
Untrue. I was 0.90 bootloader when I flashed rom_01.zip for the above radio update. It __DID__ make HBOOT report S-OFF. However, if you flash the radio file from a bootloader newer than 0.90 it still says S-ON.
So one of two things could be happening:
1) HBOOT 0.90 is not sophisticated enough to work out what some aspect of the 7.54 radio means and it incorrectly thinks S is Off, or
2) The 7.54 radio is only able to achieve S-OFF when flashed over the 0.90 bootloader.
I am, however, certain that flashing the 7.54 radio while on bootloader 0.9 made my HBOOT report S-OFF.
And to further muddy the waters, I was in the same situation as alc027 and I 'think' that my phone was S-OFF after flashing the radio, but I was a complete noob and didn't realise the significance. I carried on and flashed the second ROM and my phone was back to S-ON
alc027 said:
Untrue. I was 0.90 bootloader when I flashed rom_01.zip for the above radio update. It __DID__ make HBOOT report S-OFF. However, if you flash the radio file from a bootloader newer than 0.90 it still says S-ON.
So one of two things could be happening:
1) HBOOT 0.90 is not sophisticated enough to work out what some aspect of the 7.54 radio means and it incorrectly thinks S is Off, or
2) The 7.54 radio is only able to achieve S-OFF when flashed over the 0.90 bootloader.
I am, however, certain that flashing the 7.54 radio while on bootloader 0.9 made my HBOOT report S-OFF.
Click to expand...
Click to collapse
Nicknoxx said:
And to further muddy the waters, I was in the same situation as alc027 and I 'think' that my phone was S-OFF after flashing the radio, but I was a complete noob and didn't realise the significance. I carried on and flashed the second ROM and my phone was back to S-ON
Click to expand...
Click to collapse
You fu*k my mind guys I see one explanation. Hboot 0.90000000 is "dirty-bootloader". I don't really understand idea of dirty bootloaders, but it seems that mentioned radio with dirty bootloader makes S-OFF.
I would test it but.... It is impossible to flash dirty bootloader over 'clean bootloader'. This is reason why we can't downgrade to 0.9000.. We can change hboots which are 'clean' - 1.8, 1.3, htcdev hboots, ?.

[Q] HTC One X - Boot Loop / Bricked ? o2-uk

After looking around the web & trying a few things out myself I am left stuck and in need of help.
I would like to get a o2 UK (32GB Tegra3) HTC One X back to Stock everything (on Jelly Bean)
My friend has given me her old HOX that will not load past the ‘HTC Quietly Brilliant’ screen.
She had unlocked the bootloader via HTCDev & installed ClowckWorkMod Recovery (5.8.4.0). It was working fine.
When getting the phone, I did not know much about rooting. My own HOX is all stock. I wanted to update the handset to Jelly Bean. In recovery I clicked format cache, data, sdcard, system & cleared some dalvik cache to remove everything; this is what probably messed things up.
Right now, I am still stuck at the ‘HTC Quietly Brilliant’ screen. ClockWorkMod Recovery has been removed.
I have tried reverting to the stock recovery. This is what I got:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When loading the phone into the bootloader I get the following message:
If I click recovery I get this:
After a few secs, it changes to this:
I click FASTBOOT and plug in the USB to my PC. I hear the noise to say something is connected. Clicking on My Computer does not display anything. In Device Manager I see this:
Below are all the details I would imagine anyone needs to figure out what is wrong?
***UNLOCKED***
ENDEAVORU PVT SHIP S-ON RL
HBOOT- 1.12.0000
CPLD-None
MICROP-None
RADIO-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 28 2012, 11:31:28
IMAGE CRC after it has calculated, it tells me:
HBOOT : 0xE9BDD7AD
BOOT :0x8E7F8988
RECOVERY :0xDF73200A
SYSTEM :0xCDE281A4
CID is
o2___001
RUU is
2.17.206.2
Can someone please give me a step by step, with all the links I need to download so that I can get this HOX back to stock everything?
I see MyHTC in the device manager ... that's good
Try this ... Put the phone in the bootloader and relock the bootloader
Fastboot oem lock
Download this file
http://bugsylawson.com/index.php/fi...62-radio-2120413520-release-275038-signedexe/
Keep the phone in the bootloader after the relock and right click the ruu.exe and select
Run as administrator
YES!
Its now working and currently updating.
Before you had posted, I managed to put ClockWorkMod Recovery back on.
Will this cause any issues or should I leave it be?
Sorry, in my excitement I forgot to say
Thank you very much for your help
The ruu flashed back the phone to full stock. The recovery too Everything okey now ?
Yes, its all running, updated to Jelly Bean. My sister is now using it.
Thanks again!
Good :thumbup: !!!
CASE CLOSED !
htc one x
hi can anyone please help me out htc one x o2 cid: o2_001 unlocked with hboot 1.36.0000 endeavoru pvt ship s-on rl radio 5.1204.162.29 image version 3.14.206.27 and i cant find the correct ruu file since it has started flickering every second in all the roms i used viberX cyanogen carbon all .....so i wanted to get back to stock and i havent backed up earlier so please help with the ruu file since i tried both the asia and europe one but all are higher image versions i will be glad if you.
You can't run a ruu on a s-on device from a different region. You can only go back to stock with a nand backup.
Check the general section - collection of stock backups thread if there is one available for you !
Sent from my HTC One X using XDA Premium 4 mobile app
I don't believe there is one available, I too am in the same position with no NAND and there is no RUU for 1.36 :/
Edit :
There is no 2.17 available, only a 1.29 and in theory that would work too but the account is generated to much traffic so the link is not active !
Maybe in a few days it's back up
Sent from my HTC One X using XDA Premium 4 mobile app
Mr Hofs;50700806: o2 uk
thanks mate, is there possibility i can stop the flickering since sometimes my phone4 sends messages and calls i don’t intend to and that really makes me sick any idea on how to stop since it all started when i updated to viberX 4.0.6 it goes really fast and i have to switch it off and on again please i would be really glad am stuck with it or even assist me with instructions on how to restore using nandroid i have the download but dont know how i tried to install it like a new rom but it got aborted since i know its different compared to ruu please am in Nairobi, Kenya tech is a big thing here.
Read the backup collection thread in the general section. All is described very well there
Sent from my HTC One X using XDA Premium 4 mobile app

Help: Bootloader corrupt

Hi everyone
my friend give me his DHD that I install ICS rom on it
I had unlocked bootloader via htc , and installed recovery , flashed Stock rooted rom
then I flash 4ext recovery trought 4ext recovery updater
then I wont to s-oof and I used "EasyS_OFF" package
now it messaged that bootloader corrupt, Do not rebbot and Seek help from XDA
WHAT I SHOULD DO ? pls help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ardanai said:
Hi everyone
my friend give me his DHD that I install ICS rom on it
I had unlocked bootloader via htc , and installed recovery , flashed Stock rooted rom
then I flash 4ext recovery trought 4ext recovery updater
then I wont to s-oof and I used "EasyS_OFF" package
now it messaged that bootloader corrupt, Do not rebbot and Seek help from XDA
WHAT I SHOULD DO ? pls help me
Click to expand...
Click to collapse
Have you read this from the tool thread??
NOT COMPATIBLE WITH DEVICES SHIPPED WITH GINGERBREAD 2.3 Or Updated bootloaders. No longer Supported
Nice job buddy, you have messed your bootloader and put it in superslow motion...only way to fix it is this one....(not painless thou)
http://tau.shadowchild.nl/attn1/?p=188
glevitan said:
Have you read this from the tool thread??
NOT COMPATIBLE WITH DEVICES SHIPPED WITH GINGERBREAD 2.3 Or Updated bootloaders. No longer Supported
Nice job buddy, you have messed your bootloader and put it in superslow motion...only way to fix it is this one....(not painless thou)
http://tau.shadowchild.nl/attn1/?p=188
Click to expand...
Click to collapse
tank you man
I went to http://tau.shadowchild.nl/attn1/?p=188 and I did everything
But I get failed in CMD as below image
now I have bootloader, hboot 2.00.0029 unlocked
But Splash screen will be as long as 15 - 20 minutes
How can I fix it ?
ardanai said:
tank you man
I went to http://tau.shadowchild.nl/attn1/?p=188 and I did everything
But I get failed in CMD as below image
now I have bootloader, hboot 2.00.0029 unlocked
But Splash screen will be as long as 15 - 20 minutes
How can I fix it ?
Click to expand...
Click to collapse
Relock bootloader first. In fastboot type: fastboot oem lock
Then try hboot fix again
glevitan said:
Relock bootloader first. In fastboot type: fastboot oem lock
Then try hboot fix again
Click to expand...
Click to collapse
I relocked bootloader , now I get failed again
Can I install RUU with htc sync to get stock hboot without slow motion ?
ardanai said:
I relocked bootloader , now I get failed again
Can I install RUU with htc sync to get stock hboot without slow motion ?
Click to expand...
Click to collapse
You then need to downgrade your main version...not easy to do with a messed bootloader.
Does your bootloader say S-OFF?
glevitan said:
You then need to downgrade your main version...not easy to do with a messed bootloader.
Does your bootloader say S-OFF?
Click to expand...
Click to collapse
no, it is s-on
and now I dont know what I should do ?
with bootloader relocked I cant install RUU to get correct hboot
and with unlocked bootloader I can't install any custom rom or doing s-off
Read http://tau.shadowchild.nl/attn1/?p=188 carefully i have used this methord not only to S-Off but to S-On as well.
hacktrix2006 said:
Read http://tau.shadowchild.nl/attn1/?p=188 carefully i have used this methord not only to S-Off but to S-On as well.
Click to expand...
Click to collapse
I read it , but I get failed that I showed it in previews post
ardanai said:
I read it , but I get failed that I showed it in previews post
Click to expand...
Click to collapse
Then You will Need To gain temp root And downgrade the Main version first
ardanai said:
no, it is s-on
and now I dont know what I should do ?
with bootloader relocked I cant install RUU to get correct hboot
and with unlocked bootloader I can't install any custom rom or doing s-off
Click to expand...
Click to collapse
With UNLOCKED bootloader you cann't do anything
Let's LOCKED bootloader again then flash RUU to return stock (optional), then use newest Ace Hack Kit to S-Off your phone.
Some phone have difficulty to use AAHK directly, so you might be need to make sdcard as gold card first then copy PD98IMG.zip for your branch to sdcard before using AAHK
coolpixs4 said:
With UNLOCKED bootloader you cann't do anything
Let's LOCKED bootloader again then flash RUU to return stock (optional), then use newest Ace Hack Kit to S-Off your phone.
Some phone have difficulty to use AAHK directly, so you might be need to make sdcard as gold card first then copy PD98IMG.zip for your branch to sdcard before using AAHK
Click to expand...
Click to collapse
I suggest that You Read better before recommending that, that will brick his device.
glevitan said:
I suggest that You Read better before recommending that, that will brick his device.
Click to expand...
Click to collapse
What are the reasons of brick phone ?
I've read thru all post before reply
My experience are:
My phone is 2.3.5 Sense 3.5 version 3.17.0010...hboot 2.0.0030
- First time of using AAHK to S-Off failed many times, then I choose method of Unlock bootloader by htcdev to flash custom rom
- Someday, I need change the flash splash screen, radio and kernel then I find that I need to get S-Off to do so
=> I relocked bootloader also by inverse method of htcdev then flash RUU rom agian back to original, then use AAHK. This time, It success-S-off. that's all
PS: I think that it is not mesh hboot
He cann't install RUU rom because he hasn't found correct RUU for his branch phone.
eg: My case, my phone from CID: 01__KT (KTF Korea) so I have to find my RUU for KT
In his case I don't know ...He must have to find correct RUU so can be install after RELOCK bootloader
coolpixs4 said:
What are the reasons of brick phone ?
I've read thru all post before reply
My experience are:
My phone is 2.3.5 Sense 3.5 version 3.17.0010...hboot 2.0.0030
- First time of using AAHK to S-Off failed many times, then I choose method of Unlock bootloader by htcdev to flash custom rom
- Someday, I need change the flash splash screen, radio and kernel then I find that I need to get S-Off to do so
=> I relocked bootloader also by inverse method of htcdev then flash RUU rom agian back to original, then use AAHK. This time, It success-S-off. that's all
PS: I think that it is not mesh hboot
He cann't install RUU rom because he hasn't found correct RUU for his branch phone.
eg: My case, my phone from CID: 01__KT (KTF Korea) so I have to find my RUU for KT
In his case I don't know ...He must have to find correct RUU so can be install after RELOCK bootloader
Click to expand...
Click to collapse
Then You didn't Read Well. He flashed a froyo Ruu And messed his bootloader. Flashing a ruu will definitely Make things worse. Hack kit will fail as the bootloader Is in super Slow motion, not To mention that hack kit has been retired And so has support
I think my problem is about missed or double HBOOT
Also I have high speed internet and I can download and flash any RUU
I have this RUU: RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_R_Radio_12.65.60.29_26.14.04.28_M_release_233505_signed
but when I relocked and installed this RUU, I get error 140(Bootloader version error)
After it I make goldcard , then exclude rom.zip from this RUU, rename it to PD98IMG.zip, but after checking it in bootloader nothing occurred
and it didn't ask me press vol down to install PD98IMG.zip
now which RUU I should download and install?
this is my fastboot getvar all
Code:
INFOversion: 0.5
INFOversion-bootloader: 2.00.0029
INFOversion-baseband: 26.14.04.28_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 3.13.0.0
INFOserialno: HT23VRX02120
INFOimei: 356357048251387
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: HTC__102
INFObattery-status: good
INFObattery-voltage: 3784mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: fcef1579
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
glevitan said:
Then You will Need To gain temp root And downgrade the Main version first
Click to expand...
Click to collapse
How Can I downgrade the main version? I did it for my EVO3D, But in 2 years ago and I forget that method
ardanai said:
How Can I downgrade the main version? I did it for my EVO3D, But in 2 years ago and I forget that method
Click to expand...
Click to collapse
There is something weird about your issue. The bootloader doesn't seem to be a froyo one, however corruption of the bootloader occurs when flashing a froyo ruu. I would recommend that you contact the developer of the tool to see how it works because I have no clue on what it does and how.
If you want to try to downgrade the main and then try the hboot fix, you will need some knowlegde of adb commands. Just let me know and I will address you in the right direction. I gotta look for the information first.
glevitan said:
There is something weird about your issue. The bootloader doesn't seem to be a froyo one, however corruption of the bootloader occurs when flashing a froyo ruu. I would recommend that you contact the developer of the tool to see how it works because I have no clue on what it does and how.
If you want to try to downgrade the main and then try the hboot fix, you will need some knowlegde of adb commands. Just let me know and I will address you in the right direction. I gotta look for the information first.
Click to expand...
Click to collapse
in fact I had hboot 2.00.0027 ,Android 2.3.5 and sense 3.0
when I want to unlock with htcdev , it suggest me upgrade hboot and give me a link to PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe and I install it
then I had 2.00.0029 hboot
after that I flashed ViperDHD_v2.2.0.zip, but phone stuck at splash screen, I flash stock boot.img via fastboot and again it stuck at splash screen
then I format everything and install DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00.zip but it stuck at splash screen again, during that phone stuck at Splash screen I searched from for s-off because I did my Evo 3D s-off and I cn install every rom and kernel on it
Suddenly I heard htc-boot-sound and phone went into bootanimation and start OS
then I use Easy s-off and it messaged me that my bootloader is corrupred
Its funny because I used this exact tool to s-off my completely stock DHD, I didn't even have radio s-off, does PD98IMG files not work either?
Sent from my Desire HD using Tapatalk 2
ardanai said:
in fact I had hboot 2.00.0027 ,Android 2.3.5 and sense 3.0
when I want to unlock with htcdev , it suggest me upgrade hboot and give me a link to PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe and I install it
then I had 2.00.0029 hboot
after that I flashed ViperDHD_v2.2.0.zip, but phone stuck at splash screen, I flash stock boot.img via fastboot and again it stuck at splash screen
then I format everything and install DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00.zip but it stuck at splash screen again, during that phone stuck at Splash screen I searched from for s-off because I did my Evo 3D s-off and I cn install every rom and kernel on it
Suddenly I heard htc-boot-sound and phone went into bootanimation and start OS
then I use Easy s-off and it messaged me that my bootloader is corrupred
Click to expand...
Click to collapse
Well, if you have just kept the unlocked bootloader you wouldn't be regreting it now...S-OFF it is not necessary for most of the customization tasks.
It seems that your bootloader was not overwriten but got corrupted before somehow. This is the first time that I see that a 0029 hhboot version is corrupted and your main is even 3.13.x, I guess that you need to do some extra work and that will risk your device in every step you run.
If it is ok with you we can arrange something over teamviewer and I will lend you a hand...do not promise anything thou..

[Q] HTC one x updating problem

Hello Guys
I purchased Htc One X just few days ago in India and it is on android 4.0.4.
When i connect it to internet, it shows that an update is available i.e 4.1 with sense 4+.
and when i try to update,it shows a red triangle after 20%-30% while installing.
I am totally newbie here so please help me step by step ,if possible.
Every help will be appreciated.
hotboyz012345 said:
Hello Guys
I purchased Htc One X just few days ago in India and it is on android 4.0.4.
When i connect it to internet, it shows that an update is available i.e 4.1 with sense 4+.
and when i try to update,it shows a red triangle after 20%-30% while installing.
I am totally newbie here so please help me step by step ,if possible.
Every help will be appreciated.
Click to expand...
Click to collapse
Are you with stock recovery and stock rom? Are your bootloader is unlocked? Check this thing and report back
Thant said:
Are you with stock recovery and stock rom? Are your bootloader is unlocked? Check this thing and report back
Click to expand...
Click to collapse
I don't know what is stock recovery and stock rom? It's my first time to update. Here are some pics
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and when i start the phone by power+volume down button,it shows :-
***** locked****
ENDEAVORU PVT SHIP S-OFF RL
CID -111111111
HBOOT -1.12.0000
CPLD -NONE
MICROP -NONE
RADIO -2.1204.135.20
eMMC BOOTMODE -DISABLED
cPU BOOTMODE - DISABLED
HW SECURE BOOT : ENABLED
MODEM PATH -OFF
JUN 282012,11:31:28
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SHOW BARCODE
IMAGE CRC
MODEM PATH
hotboyz012345 said:
I don't know what is stock recovery and stock rom? It's my first time to update. Here are some pics
and when i start the phone by power+volume down button,it shows :-
***** locked****
ENDEAVORU PVT SHIP S-OFF RL
CID -111111111
HBOOT -1.12.0000
CPLD -NONE
MICROP -NONE
RADIO -2.1204.135.20
eMMC BOOTMODE -DISABLED
cPU BOOTMODE - DISABLED
HW SECURE BOOT : ENABLED
MODEM PATH -OFF
JUN 282012,11:31:28
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SHOW BARCODE
IMAGE CRC
MODEM PATH
Click to expand...
Click to collapse
Download this RUU and install and report back
You have S-OFF device really nice good for you
I have downloaded the RUU....
Now What?
Put the phone in the bootloader/fastboot usb mode (where you see fastboot usb in red text)
Now select the ruu.exe with your right mouse button and select
Run as administrator
Please tell , full step by step procedure in comment
so i can upgrade it more appropriately
Lol that's all i can say about it ...... there is nothing else to say. It works that way. What is the difficulty then ?
i have the same issue . can i directly update my version from ics 0.95 to 3.14. JB?
meye143 said:
i have the same issue . can i directly update my version from ics 0.95 to 3.14. JB?
Click to expand...
Click to collapse
Only via firmware. Not with a ruu
Reading is a gift ............. use it !
Mr Hofs said:
Only via firmware. Not with a ruu
Reading is a gift ............. use it !
Click to expand...
Click to collapse
sir im confuse if what update should i take. i need hboot 1.36 to install JB. i am on hboot 0.95. should i do it with ruu or via ota update.? could you please send me a link to the firmware you are saying.
What's your main number ?
Reading is a gift ............. use it !
Mr Hofs said:
What's your main number ?
Reading is a gift ............. use it !
Click to expand...
Click to collapse
htc_01 europe
i have unlocked bootloader and i already s-off my hox.
my current version 1.29.401.12 .
i tried downloading ota for ics and jb . i rename my jb ota as firmware.zip but it failed in flashing via cmd. and i tried installing ruu and it failed also.
You can't have s-offed your hox yourself. Or it came that way or a shop did it.
Well download the firmware from the placeholder thread 3.14.401 firmware. And flash that. You can't just flash the ota zip. Only the firmware.zip !
Reading is a gift ............. use it !
Mr Hofs said:
You can't have s-offed your hox yourself. Or it came that way or a shop did it.
Well download the firmware from the placeholder thread 3.14.401 firmware. And flash that. You can't just flash the ota zip. Only the firmware.zip !
Reading is a gift ............. use it !
Click to expand...
Click to collapse
theres no 3.14.401 firmware there. i dowloading this 3.62.401.1.zip instead. is this ok?
There is defo the 3.14.401 zip.
Reading is a gift ............. use it !
---------- Post added at 02:48 PM ---------- Previous post was at 02:45 PM ----------
http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One_X/401/
All of the 401s via the placeholder thread. Don't were you been looking then
Reading is a gift ............. use it !
Mr Hofs said:
There is defo the 3.14.401 zip.
Reading is a gift ............. use it !
---------- Post added at 02:48 PM ---------- Previous post was at 02:45 PM ----------
http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One_X/401/
All of the 401s via the placeholder thread. Don't were you been looking then
Reading is a gift ............. use it !
Click to expand...
Click to collapse
I downloaded RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
and tried to install it in my htc one x.
But it shows Error[159]: Image Error
What to do now?
hotboyz012345 said:
I downloaded RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
and tried to install it in my htc one x.
But it shows Error[159]: Image Error
What to do now?
Click to expand...
Click to collapse
If your bootloader is unlocked you must to lock. If is locked just start the RUU and fallow the instruction!
Deleted, see above......that's what you get when others hijack the thread !!!
***** locked****
ENDEAVORU PVT SHIP S-OFF RL
CID -111111111
HBOOT -1.12.0000
CPLD -NONE
MICROP -NONE
RADIO -2.1204.135.20
eMMC BOOTMODE -DISABLED
cPU BOOTMODE - DISABLED
HW SECURE BOOT : ENABLED
MODEM PATH -OFF
JUN 282012,11:31:28
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SHOW BARCODE
IMAGE CRC
MODEM PATH

Categories

Resources