Related
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
http://www.filefactory.com/file/c0f....00_11.16.3504.20_2_release_227956_signed.zip
Click to expand...
Click to collapse
Download the CWM recovery image:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.7-doubleshot.img
Click to expand...
Click to collapse
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Here's a pointer to restoring your phone to stock, courtesy of blue:
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
So if we've gotten this far, is S-OFF going to gain us anything more? Are we still locked out of certain areas? The tool worked for me, but I'm using the rest of your guide to flash CWM. Thanks for writing it!
xzuhto said:
So if we've gotten this far, is S-OFF going to gain us anything more? Are we still locked out of certain areas? The tool worked for me, but I'm using the rest of your guide to flash CWM. Thanks for writing it!
Click to expand...
Click to collapse
In my opinion, S-Off won't really gain you much more. You'll have to flash kernels separately when flashing ROMs, but that doesn't seem to be a big deal (IMO).
You could probably flash back to the original release software if you wanted, and gain S-OFF with revolutionary, but I haven't tried that and have no idea if it will work.
The only thing you can't do with Unlocked/S-ON is flash radios.
Well in that case this phone is right where I want it. I've never messed with kernels on any phone I've had previously nor have I messed with flashing radios. I just got done completing the steps and I'm now root along with CWM. Great work throwing this up for everyone.
jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
the doubleshot img downloads painfully slow, do you have another link?
edit: also i think you missed somthing here"
[*]Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
"
ac3theone said:
the doubleshot img downloads painfully slow, do you have another link?
...
Click to expand...
Click to collapse
Well, where football is hosting the new PG59IMG.zip file is the only place we have it - i just found it yesterday and we haven't had time to up it anywhere else yet.
We are working on making mirrors for it now - give us some time to get set up with our new data.
---------- Post added at 01:38 AM ---------- Previous post was at 01:33 AM ----------
jonnycat26 said:
In my opinion, S-Off won't really gain you much more. You'll have to flash kernels separately when flashing ROMs, but that doesn't seem to be a big deal (IMO).
You could probably flash back to the original release software if you wanted, and gain S-OFF with revolutionary, but I haven't tried that and have no idea if it will work.
The only thing you can't do with Unlocked/S-ON is flash radios.
Click to expand...
Click to collapse
No, you can't go back to retail factory if you are S-ON. This new PG59IMG.zip I found is the furthest back you can go completely.
With S-ON you cannot replace hboot, or radio - those two are a big deal - i'm still working on an S-OFF solution for S-ON people with hboot 1.45.0013.
With S-OFF I can swap out hboots on a whim, and thrice43 even flashed a Sensation hboot to his doubleshot and it worked out for him - but with S-ON you cannot do this. (and if you could, you would brick)
S-OFF is very much preferable to S-ON UNLOCKED.
I've also had problems flashing OTA updates through stock recovery manually when S-ON where I had no trouble doing so while S-OFF.
There are still a lot of things you can't do with your device while S-ON.
EDIT:
also, all the PG59IMG.zip files I made for people to flash recoveries, hboots, and so on in the dev reference sticky cannot be used by anyone S-ON because they fail the signature checks. My custom PG59IMG.zip files don't have an HTC signature which you must have for an S-ON device to load the PG59IMG.zip file.
...so there are a number of reasons why S-OFF is something to get.
xzuhto said:
Well in that case this phone is right where I want it. I've never messed with kernels on any phone I've had previously nor have I messed with flashing radios. I just got done completing the steps and I'm now root along with CWM. Great work throwing this up for everyone.
Click to expand...
Click to collapse
You must flash a kernel if you want to flash an ICS ROM or any GB ROM with a modified kernel.
Also:
Here's a faster mirror, hopefully: http://www.4shared.com/zip/vVHQuid0/PG59IMG_Doubleshot_TMOUS_15553.html
I see the downsides to s-on but I'm happy to have root and cwm. I will however be excited to get this thing fully unlocked. I won't be messing with custom roms till then. lol
Sent from my myTouch_4G_Slide using Tapatalk
I managed to host it on my Dropbox
Edit:
Oh sorry Lime, I didn't see that you were already hosting it...
this might deserve a sticky?
If anyone is going to mirror it please keep the original filename - we have more then one PG59IMG.zip file with an HTC signature (retail launch and this one).
If they are not named including the software version and radio then people may be confused on what they are getting - thanks guys!
it worked, now to get su. thanks for the guide
delete post
jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Cant do this last few steps.Don't understand what to do as yet
Scondrel said:
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
fastboot flash recovery recovery.img
Cant do this last few steps.Don't understand what to do as yet
Click to expand...
Click to collapse
You need to transfer the recovery image to the directory with your fastboot.exe file.
You would then need to rename it to recovery.img
Then you boot your phone into fastboot mode, and plug it into the computer.
Open a command prompt, and navigate to the directory with fastboot.exe and run the command:
fastboot flash recovery recovery.img
Thanks got it now.Appreciate the help
---------- Post added at 01:23 AM ---------- Previous post was at 12:53 AM ----------
Scondrel said:
Thanks got it now.Appreciate the help
Click to expand...
Click to collapse
Didn't work for me,I all the way to final step, but once i enter recovery for CWM,and try to flash the superuser file or anything else, it just shows the icon and nothing else happens.Once i click the power button it goes back to the CWM Home screen.Any advice on this guys ?
Scondrel said:
Thanks got it now.Appreciate the help
---------- Post added at 01:23 AM ---------- Previous post was at 12:53 AM ----------
Didn't work for me,I all the way to final step, but once i enter recovery for CWM,and try to flash the superuser file or anything else, it just shows the icon and nothing else happens.Once i click the power button it goes back to the CWM Home screen.Any advice on this guys ?
Click to expand...
Click to collapse
You are using the trackpad to "select" within CWM, not the power button, right?
jonnycat26 said:
You are using the trackpad to "select" within CWM, not the power button, right?
Click to expand...
Click to collapse
Thanks it was 'nt that. There wasn't enough space on the memory card and I didn't have USB debugging on.Got it solved now .Thanks for the speedy responses.Truly appreciated .Feels so good to be a part of this community.
jonnycat26 said:
So, you've got the latest OTA (1.55.531.3) and the HTC unlocker tool won't work? Tired of waiting for HTC to issue a fix/resume the OTA? You no longer have to wait in agony.
These are the steps I took to unlock the latest OTA. They worked for me, they may not work for you. Anything you do to your phone is not my responsibility.
That said..
Backup what you can. Your phone is going to be wiped.
Make sure your battery is charged up.
Download the full 1.55.531.3 image. This contains the confirmation splash screen which wasn't loaded on older MT4GSes, and is the reason the unlocker tool won't work on our devices. You can get the full image (it's over 400MB) here:
Download the CWM recovery image:
Rename the full image downloaded in the first step to PG59IMG.zip and place it on the root of the SD card in your phone.
Shut the phone down, remove the battery, and boot back up while holding both the volume down and power buttons down.
The phone will check the PG59IMG.zip file and will ask you if you want to restore that image. You want to do this, but keep in mind this is going to wipe your phone. All data will be lost.
The phone will restore the image. This takes a few minutes. When it's done, you'll be prompted to reboot, and you'll boot into a completely stock MT4GS experience.
Use the unlock tool on htcdev.com to generate your unlock code. The splash screen is now on your phone, and you should be able to unlock (I had no issues).
I rebooted at this point, just to be safe, and set up my phone.
Copy the recovery image you downloaded earlier into the directory where you're running fastboot. Rename it to recovery.img
Shut down, boot into the bootloader/fastboot, and enter the following command to flash CWM recovery:
At this point, you should probably reboot the bootloader before entering CWM. Once you've done that, you can go ahead and flash superuser/roms/etc.
Click to expand...
Click to collapse
These instructions worked perfectly! Can not believe it worked. This should be stickied! Thank you.
tbalden said:
this might deserve a sticky?
Click to expand...
Click to collapse
revo420 said:
This should be stickied!
Click to expand...
Click to collapse
Eh, why not. Done .
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
He probably forgot to flash boot.img in fastboot.
If you are bricked, this phone will not turn on and be listed as QHSUSB_DLOAD in windows.
edit: cwm + evita(htc one xl) = bad.
he needs TWRP
wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Crappyvate said:
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Click to expand...
Click to collapse
absolutelygrim said:
He probably forgot to flash boot.img in fastboot.
Click to expand...
Click to collapse
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
wiiareonfire said:
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
Click to expand...
Click to collapse
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
First, extract boot.img onto comp. Move boot.img into adb files. Rezip Rom and transfer to sdcard. Fire up command prompt where you stored boot.img. type --> fastboot flash boot boot.img
Once successful, flash Rom IN RECOVERY. profit
Tell your FRIEND to follow posts before blindly flashing, he'd be more prepared
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
absolutelygrim said:
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
Click to expand...
Click to collapse
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
subarudroid said:
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
Click to expand...
Click to collapse
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
wiiareonfire said:
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
Click to expand...
Click to collapse
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Crappyvate said:
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Click to expand...
Click to collapse
Code:
C:\Android>adb reboot recovery
error: device not found
Surprisingly enough, you need to be booted into android for adb commands to work. Even the bootloader option for "recovery" gets me nowhere.
Out of nowhere, he tells me he tried to flash a rom.
Ali: the rom that i flashed hmmm.
if i sent that to you would you be able to do anything?
well, tried flashing?
Me: a download link would be preferable
but yes, i'll need that
Ali Haider: got it.
give me a few minutes.
what if the rom wasn't supported?
because i can't completely remember which of the several roms i tried to flash were the problem
Me: what do ya mean "not supported"
Ali:
like clockwork- it apparently doesn't work
Me:
gimme whichever you flashed most revently
a link
i'll need the boot.img
and if you don't know which rom, gimme a list to narrow it down
and i'll go one by one
Click to expand...
Click to collapse
TL;DR, he flashed with CWM and that's why it's screwed up.
Ladies and gents, we might be getting somewhere with this. Albeit, slowly, thanks to my friend who can't read the posts.
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Sent from my One X using xda premium
subarudroid said:
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Click to expand...
Click to collapse
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
wiiareonfire said:
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
Click to expand...
Click to collapse
What happens after flashing twrp in flashboot ? what msg do you get ?
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
wiiareonfire said:
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
Click to expand...
Click to collapse
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Crappyvate said:
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Click to expand...
Click to collapse
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
I believe Fat32, but I may be wrong on that.
And you can use windows built in formatter.
wiiareonfire said:
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
Click to expand...
Click to collapse
yep fat 32, dunno windows sorry...
Yup fat32. That what I did. My first hox I soft bricked as well with cwm
Sent from my One X using xda premium
I formatted with FAT32... It's still not accepting the file. TWRP crashes when the adb push command is finished. Is there something I'm missing?
Hi,
Normally, I try to troubleshoot things myself without bothering others, but I'm in need of help this time. The tricky part is, I just bought this HTC One S from a stranger, so I don't have its complete history. With that said, here's what I need help with. The phone came with Pacman installed (v18.0.0). But, I would like to install this ROM: http://forum.xda-developers.com/showthread.php?t=2082451
It's basically a stock ICS ROM (the lite version mentioned with stuff removed). In attempt to do this myself, I found this post on here:
Yes the only other solution for you involves rooting. It is possible to go back to ICS by rooting your phone, going through a bootloader downgrade, hexediting a particular partition, then running an older compatible RUU... Its all possible, but requires some time to understand and do. And definately requires a few wipes of phone data in the mean time (which can be backed up through titanium and custom recoveries).
Only need to do that if you want to downgrade hboot. All you have to do is root and flash a rom, I have JB radio and hboot and run ICS Trickdroid 8.1.0.
So, I put the ICS ROM in the internal sdcard, did the usual wiping stuff (I've owned several HTC phones, so this part I know how), then installed the ROM. Unfortunately, it didn't work. When I rebooted the phone, it got stuck in boot loop. It would go to HTC logo screen with the development purpose only warning and just keep turning off and on. Fortunately, I was able to get back into recovery and restored it to Pacman. So, apparently, you can't just flash any ICS ROM over JB setup... Can someone help me figure out what I need to do to install that modified stock ROM please? I very much appreciate your help. My One S is S4 from T-Mobile.
Thank you,
GT
Did you flash boot.img?
Sent from my HTC VLE_U using xda app-developers app
thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.
dr_rick13 said:
thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.
Click to expand...
Click to collapse
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.
goldentequila said:
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.
Click to expand...
Click to collapse
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.
dr_rick13 said:
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.
Click to expand...
Click to collapse
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
If the Toolkit can't see your phone then you might need to install the drivers that come with it for it to work.
goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Ya 4EXT is coming soon.
dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Also try rebooting the computer if its still not working.
goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT
goldentequila said:
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT
Click to expand...
Click to collapse
oops, it was late last night when I wrote that.. my bad
Sent from my HTC One S using xda premium
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
we do not have S-OFF yet, so until we do.. people with hboots 1.13+ will need to flash boot.img. But HTC still hasn't said anything about when we will get S-OFF or if we will get it.
pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.
Darknites said:
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.
Click to expand...
Click to collapse
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.
Darknites said:
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.
Click to expand...
Click to collapse
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2
pnut22r said:
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Yep very good app I did use it in till I downgraded.
I was running a rom on my phone working fine until the new update came and I tried to install which sent me to my recovery page (TWRP v2.5) I then factory reset hoping this would work and managed to delete my recoveries and now whenever i restart my phone i either get the message of no os installed or when i install a rom and it actually works i get stuck in a boot loop. im not sure if it is the rom or not (KickDroidXL v5) any help would be appreciated, Thankyou
Your problem is your recovery version, TWRP 2.5 is very buggy and has major issues with wiping and with flashing. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can flash the ROM again and you should be fine.
Sent from my Evita
thanks for that, successfully running twrp 2.6 however when i attempt to install my rom it loaded into recovery as if i chose it from the bootloader screen. when i skipped that one and tried another it got to the htc screen then turned off
thanks again, its now working after looking at your q&a thread! was stuck on the boot loop without the boot.img file, too easy
Guested said:
thanks for that, successfully running twrp 2.6 however when i attempt to install my rom it loaded into recovery as if i chose it from the bootloader screen. when i skipped that one and tried another it got to the htc screen then turned off
thanks again, its now working after looking at your q&a thread! was stuck on the boot loop without the boot.img file, too easy
Click to expand...
Click to collapse
Yeah, you should get s-off either here or here. Then you won't have to worry about flashing the boot.img anymore. You're gonna need s-off to upgrade your firmware anyway, otherwise you're gonna suffer signal losses and random reboots.
so trying to use s-off at the moment and i am not able to boot into recovery (just goes to htc startup screen and phone turns on) i then tried usb debugging where i got the response, needs to be formatted, tried that and said it was impossible as i didnt have any permissions! any ideas?
Neither of the s-off processes need to boot into recovery, what do by mean by that?
Sent from my Evita
so i tried the rum runner method which got stuck when on test 2 it tells me it must ferment longer, i wait in this process for awhile and it attempts to start my phone however it doesnt start up only a black screen with no led (i assume the phone is off) the only way to start is by holding down the power and waiting for the 15 flashes from the buttons then putting it into bootloader, from there i chose recovery and it starts normally without entering the twrp screen.
Test 2: Booting device
Waiting for ADB (19/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[TTTT********************************************************]
Press ENTER to exit
Do you have SuperCID? If so you could try the Facepalm method instead.
Sent from my Evita
timmaaa said:
Do you have SuperCID? If so you could try the Facepalm method instead.
Sent from my Evita
Click to expand...
Click to collapse
no CID, i tried using http://androidforums.com/sensation-4g-all-things-root/636482-guide-how-supercid.html
didnt work came up with an error of too many links after getting to this stage -change CID
fastboot oem writecid 11111111 (eight ones)
okay so i assume it has something to do with the rom, i flashed twrp 2.6 back and recovery works fine! any suggestions on a battery low and stable rom?
Asking which ROM is best/most stable/fastest/prettiest question isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Sent from my Evita
timmaaa said:
Asking which ROM is best/most stable/fastest/prettiest question isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Sent from my Evita
Click to expand...
Click to collapse
thanks for that, didnt know! got a new rom running smoother, however rum runner doesnt work and no method to change the CID works? when changing it to 11111111 it gets an error that the device is not connected
Guested said:
thanks for that, didnt know! got a new rom running smoother, however rum runner doesnt work and no method to change the CID works? when changing it to 11111111 it gets an error that the device is not connected
Click to expand...
Click to collapse
You need to get adb/fastboot and your drivers sorted out. Try using an app called pdanet+ from the Play Store, you download it to your phone and then another component on your PC. When you open the PC component it'll install drivers, it's what got everything working for me.
Sent from my Evita
Hello,
I have a carrier unlocked ATT HTC One x (sim unlocked), it is not rebooting after the battery was accedently drained. That happened after I put it on the charger and I saw it starting to charge, and then I hit the power on, but it did not go past the HTC One white screen. After the battery is fully charged, I tried to recover it but I got a red triangle with exclamation mark on a phone icon during the recovery process, then it go to the freezing welcome screen again. I saw many very useful posts but they all do not address the specific problem I am facing. The phone is locked for boot-loader, so I have problem installing an new image. As the phone shut down accidentally I did not set the usb debugger enable mode that seams to be required, also it is not rooted. From the posts I see that I needed to get a temporary superuser by accessing one of the phone files (mmcblk0p4) which is also not possible at this stage. I am able to communicate with the phone with my computer (I got fastboot usb on my phone when connected to the windows 7 pc), I can use fastboot command from the cmd-shell screen (when I do fastboot device, I get the serial number, when I do fastboot oem readcid I get CWS__001 as expected from a loced ATT booter as I understood, I got the identifier but got MID not allowed from the HTCdev site, fastboot command seams to work but when I try anything else that seams more useful to me, suggested in the posts, I got FAILD (remote: not allowed) error, when did fastboot flash recovery recoveryimage.img got sending, then writing, then FAILD (remote: signature verify fail) fastboot oem unlock give Command error, I can also do fastboot oem rebootRUU and reboot-bootloader, not sure what is rebootRUU does but seams that I can flash the system this way.. not sure if I need that now or not yet, or if it is even doable), also it seams that I can not use adb that is described in the very useful post below, when I do adb devices (The adb version 1.0.29) it give me "list of the devices attached" message only with no devices, it seams that adb is the key to what I am doing here and if it is not working then I do not know how to proceed.
http://forum.xda-developers.com/showpost.php?p=49019103
doing adb shell give error: device not found. I downloaded many useful packages that I think for 3.18 or 5.18 software, but I am not sure if these are appropriate to my phone software as I do not recall the exact build, not sure if the Hboot version can tell anything about that or not.
Now I know that I need to get superCID, unlock the bootloader, and then recovery, but I can not pass the first step. I am not clear about what is the S-on or off has to do with that or if it is a required step.
Sorry for the very long post, but wanted to be clear as much as I can, the bootloader info is below.
I appraciate your help very much
EVITA PVT SHIP s-on RL
Hboot ver 1.14.0002
radio ver 0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
eMMc-boot
jun 11 2012, 14:36:28
As long as you have fastboot access you can run an RUU. I'd suggest running the 3.18 RUU to get your phone back up and running again. If you need a tutorial there's one here:
http://forum.xda-developers.com/showthread.php?t=2593037
The fastboot oem unlock command doesn't work on this phone unless you have s-off, to unlock the bootloader you need to go to htcdev and do it there. But you first need to follow section 1a in my guide thread to get SuperCID. You must run the 3.18 RUU first though.
I'd advise against using the rebootRUU mode unless you really know what you're doing, messing around with this stuff without proper knowledge is how phones become fully bricked.
So anyway, run the RUU and that should get your phone up and running again. If you want to unlock your bootloader after that then do what I suggested above.
Transmitted via Bacon
timmaaa said:
As long as you have fastboot access you can run an RUU. I'd suggest running the 3.18 RUU to get your phone back up and running again. If you need a tutorial there's one here:
http://forum.xda-developers.com/showthread.php?t=2593037
The fastboot oem unlock command doesn't work on this phone unless you have s-off, to unlock the bootloader you need to go to htcdev and do it there. But you first need to follow section 1a in my guide thread to get SuperCID. You must run the 3.18 RUU first though.
I'd advise against using the rebootRUU mode unless you really know what you're doing, messing around with this stuff without proper knowledge is how phones become fully bricked.
So anyway, run the RUU and that should get your phone up and running again. If you want to unlock your bootloader after that then do what I suggested above.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaaa, I will go through this instruction and will tell you how it goes. I appreciate your prompt replay.. Regards ..
timmaaa said:
As long as you have fastboot access you can run an RUU. I'd suggest running the 3.18 RUU to get your phone back up and running again. If you need a tutorial there's one here:
http://forum.xda-developers.com/showthread.php?t=2593037
The fastboot oem unlock command doesn't work on this phone unless you have s-off, to unlock the bootloader you need to go to htcdev and do it there. But you first need to follow section 1a in my guide thread to get SuperCID. You must run the 3.18 RUU first though.
I'd advise against using the rebootRUU mode unless you really know what you're doing, messing around with this stuff without proper knowledge is how phones become fully bricked.
So anyway, run the RUU and that should get your phone up and running again. If you want to unlock your bootloader after that then do what I suggested above.
Transmitted via Bacon
Click to expand...
Click to collapse
Timmaaa, thank you again, your help is highly appreciated, I was able to run the specific RUU, as it turned out that I have the 2.20 software, after little hassle as the process stopped at 56% and I did not know what to do, but saw your comment on another post saying that there is no option, actually I did not take the USB cable out, but rebooted with fastboot from the command window and it worked in the second time. After that I went one step and rooted the phone successfully. Now, I need to get red of the AT&T software currently installed, I saw many posts about that where you also were involved, but the posts were old, so which is the most updated image that I should use to replace the AT&T image that you recommend? I also saw people updating the HTC One X with lollypop android .. is that good or bad, is the hardware able to work good with that new release? I am not clear on the relation between the software update from AT&T to another image, and updating the Android version, are they the same or two different steps? Thank you.
aabdo said:
Timmaaa, thank you again, your help is highly appreciated, I was able to run the specific RUU, as it turned out that I have the 2.20 software, after little hassle as the process stopped at 56% and I did not know what to do, but saw your comment on another post saying that there is no option, actually I did not take the USB cable out, but rebooted with fastboot from the command window and it worked in the second time. After that I went one step and rooted the phone successfully. Now, I need to get red of the AT&T software currently installed, I saw many posts about that where you also were involved, but the posts were old, so which is the most updated image that I should use to replace the AT&T image that you recommend? I also saw people updating the HTC One X with lollypop android .. is that good or bad, is the hardware able to work good with that new release? I am not clear on the relation between the software update from AT&T to another image, and updating the Android version, are they the same or two different steps? Thank you.
Click to expand...
Click to collapse
If you want to use custom ROMs you'll need to do some more work first.
1. Flash the Kickdroid 5.0 ROM. This is only temporary, you need this ROM to get s-off in the next step.
2. Go to the Rumrunner Site and follow the instructions there to get s-off.
3. Go to my guide thread and follow instructions there to flash the 2.15 firmware.
Now you can flash whatever ROM you like. Lollipop is perfectly fine for this device.
Transmitted via Bacon
timmaaa said:
If you want to use custom ROMs you'll need to do some more work first.
1. Flash the Kickdroid 5.0 ROM. This is only temporary, you need this ROM to get s-off in the next step.
2. Go to the Rumrunner Site and follow the instructions there to get s-off.
3. Go to my guide thread and follow instructions there to flash the 2.15 firmware.
Now you can flash whatever ROM you like. Lollipop is perfectly fine for this device.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaaa, I will work on that and I will let you know how it goes. Best regards ..
timmaaa said:
If you want to use custom ROMs you'll need to do some more work first.
1. Flash the Kickdroid 5.0 ROM. This is only temporary, you need this ROM to get s-off in the next step.
2. Go to the Rumrunner Site and follow the instructions there to get s-off.
3. Go to my guide thread and follow instructions there to flash the 2.15 firmware.
Now you can flash whatever ROM you like. Lollipop is perfectly fine for this device.
Transmitted via Bacon
Click to expand...
Click to collapse
I went through the steps, studied them all first .. then started one by one. First I downloaded Kickdroid 5.0 Rom on my phone storage, although I saw a requirement to have a special firmware package (that to install I needed S-off) post #4 in http://forum.xda-developers.com/showthread.php?t=2485865 , I skipped that requirement and then was able to install Kickdroid 5.0 from the recovery, it flashed successfully, but then the phone did not boot, it hanged on the first white screen, I tried 3 times with changing the options .. I started by not downloading any thing in the flashing process, then last I kept the default except I had to choose to keep sense 5 as there was no default option .. then I cleaned the catch and rebooted .. same result. So I had to go back and restore my original system (as I had it backed up before). I went through the post and in page 19 I saw someone had a similar problem and someone suggested to wipe the storage in order to make it work, which I did not, but then he said it worked without needing to do that. Another suggested to flash a boot.img first with fastboot, which was not in the instructions. Not sure what is the problem I am facing exactly. I use TWRP 2.3.1 to run the zip file on the phone SD, with 75 to 80% battery charged. One more question, I saw a youtube for someone who is getting S-off for HTC One (not x) without that Kikdroid step, https://www.youtube.com/watch?v=MCMJkVbIiIg , he is using your step 2 exactly, Would you please explain to me why I need the first step in my case? Thank you very much for your help.
aabdo said:
I went through the steps, studied them all first .. then started one by one. First I downloaded Kickdroid 5.0 Rom on my phone storage, although I saw a requirement to have a special firmware package (that to install I needed S-off) post #4 in http://forum.xda-developers.com/showthread.php?t=2485865 , I skipped that requirement and then was able to install Kickdroid 5.0 from the recovery, it flashed successfully, but then the phone did not boot, it hanged on the first white screen, I tried 3 times with changing the options .. I started by not downloading any thing in the flashing process, then last I kept the default except I had to choose to keep sense 5 as there was no default option .. then I cleaned the catch and rebooted .. same result. So I had to go back and restore my original system (as I had it backed up before). I went through the post and in page 19 I saw someone had a similar problem and someone suggested to wipe the storage in order to make it work, which I did not, but then he said it worked without needing to do that. Another suggested to flash a boot.img first with fastboot, which was not in the instructions. Not sure what is the problem I am facing exactly. I use TWRP 2.3.1 to run the zip file on the phone SD, with 75 to 80% battery charged. One more question, I saw a youtube for someone who is getting S-off for HTC One (not x) without that Kikdroid step, https://www.youtube.com/watch?v=MCMJkVbIiIg , he is using your step 2 exactly, Would you please explain to me why I need the first step in my case? Thank you very much for your help.
Click to expand...
Click to collapse
You need to flash the boot.img from the Kickdroid ROM zip via fastboot after flashing the ROM in recovery because you're s-on. I'm guessing you haven't done that, and that's why it didn't boot. I wouldn't go anywhere anything that OneXRoot posted honestly, just follow my directions here.
Transmitted via Bacon
timmaaa said:
You need to flash the boot.img from the Kickdroid ROM zip via fastboot after flashing the ROM in recovery because you're s-on. I'm guessing you haven't done that, and that's why it didn't boot. I wouldn't go anywhere anything that OneXRoot posted honestly, just follow my directions here.
Transmitted via Bacon
Click to expand...
Click to collapse
Yes I did not flash the boot.img after I used Kikdroid Rom .. Thank you for clarifying this .. I will try again and let you know .. best regards ..
timmaaa said:
You need to flash the boot.img from the Kickdroid ROM zip via fastboot after flashing the ROM in recovery because you're s-on. I'm guessing you haven't done that, and that's why it didn't boot. I wouldn't go anywhere anything that OneXRoot posted honestly, just follow my directions here.
Transmitted via Bacon
Click to expand...
Click to collapse
But would you please confirm that the second step is exactly as shown in the youtube clip? I am just not positive as it is another device and wanted to hear your opinion .. not sure if there is a difference or not between the hardware of HTC One X and HTC One. Thanks.
aabdo said:
But would you please confirm that the second step is exactly as shown in the youtube clip? I am just not positive as it is another device and wanted to hear your opinion .. not sure if there is a difference or not between the hardware of HTC One X and HTC One. Thanks.
Click to expand...
Click to collapse
Seeing as the steps in the clip aren't numbered I have no idea which part you're talking about. It's very straight forward though, flash Kickdroid (including the boot.img), go to Rumrunner and follow their instructions, flash the firmware in my guide.
timmaaa said:
Seeing as the steps in the clip aren't numbered I have no idea which part you're talking about. It's very straight forward though, flash Kickdroid (including the boot.img), go to Rumrunner and follow their instructions, flash the firmware in my guide.
Click to expand...
Click to collapse
Thanks .. yes it seams straight forward, but as I have no experience, I try to be cautious as much as I can, the entire clip is your step 2 in the instructions you gave me for running the rumrunner .. Sorry if I wasted your time to watch the clip, I should not have asked that, but thanks.
Now I am still stuck actually at the first step, I flashed the KickdroidXL 5 successfully, then I flashed the boot.img (fastboot flash boot boot.img) using the boot.img in the Kickdroid package, as you recommended, a little progress I saw, it start with a new logo "T" then the first HTC white screen I used to be stuck on before, then the One X white screen .. but then does not boot. I flashed the Kickdroid twice and every time I do cache erase with the TWRP and with fastboot (fastboot erase cache). Please let me know if I seam to be missing any steps that cause it to not boot .. Thank you for your help and prompt response .. Regards ..
aabdo said:
Thanks .. yes it seams straight forward, but as I have no experience, I try to be cautious as much as I can, the entire clip is your step 2 in the instructions you gave me for running the rumrunner .. Sorry if I wasted your time to watch the clip, I should not have asked that, but thanks.
Now I am still stuck actually at the first step, I flashed the KickdroidXL 5 successfully, then I flashed the boot.img (fastboot flash boot boot.img) using the boot.img in the Kickdroid package, as you recommended, a little progress I saw, it start with a new logo "T" then the first HTC white screen I used to be stuck on before, then the One X white screen .. but then does not boot. I flashed the Kickdroid twice and every time I do cache erase with the TWRP and with fastboot (fastboot erase cache). Please let me know if I seam to be missing any steps that cause it to not boot .. Thank you for your help and prompt response .. Regards ..
Click to expand...
Click to collapse
Ok, dust things first, lets get Kickdroid booting. When you flash a new ROM you need to perform a full wipe, this means wiping system, data, cache, and dalvik cache.
Transmitted via Bacon
timmaaa said:
Ok, dust things first, lets get Kickdroid booting. When you flash a new ROM you need to perform a full wipe, this means wiping system, data, cache, and dalvik cache.
Transmitted via Bacon
Click to expand...
Click to collapse
OK thank you temmaaa, that was my mistake the, I was trying to not wipe anything, but that seams to be wrong. The strange thing is that after I was able to boot, I still see my data on the phone sd storage. Question for you, when I failed to boot Kickdroid 5, I tried to restore my old AT&T system which I backed up with TWRP and saved on the phone (as well as outside) but that did not restore .. does the boot.img flashing is the reason for that? it seams that I needed to flash another boot.img to get back the old system.. is my understanding correct?
Now I will proceed to the second step .. running rumrunner.. I will follow the instruction from the link you gave me.
Also, would you please explain to me why I need to flash the 2.15 software which is step 3 in your instructions?
Is there any risky step here that I need to take special attention to?
Thank you for your help .. really appropriate it.
aabdo said:
OK thank you temmaaa, that was my mistake the, I was trying to not wipe anything, but that seams to be wrong. The strange thing is that after I was able to boot, I still see my data on the phone sd storage. Question for you, when I failed to boot Kickdroid 5, I tried to restore my old AT&T system which I backed up with TWRP and saved on the phone (as well as outside) but that did not restore .. does the boot.img flashing is the reason for that? it seams that I needed to flash another boot.img to get back the old system.. is my understanding correct?
Now I will proceed to the second step .. running rumrunner.. I will follow the instruction from the link you gave me.
Also, would you please explain to me why I need to flash the 2.15 software which is step 3 in your instructions?
Is there any risky step here that I need to take special attention to?
Thank you for your help .. really appropriate it.
Click to expand...
Click to collapse
No worries, please refer to my guide that I've linked you to, it contains instructions for pretty much anything you need to do.
The wipes that I mentioned don't wipe your sd card, that isn't wiped unless you explicitly choose to wipe it in the advanced wipe menu.
When you made the backup of your stock ROM did you backup boot? If not, that's why your restore isn't booting. If you did, did you restore that as well?
You need to flash the 2.15 firmware because all recent ROMs require the updated firmware to be installed in order to operate correctly. In fact, they won't even flash of the firmware isn't present as there's a check in the updater script that'll stop the install if you don't have the correct firmware. There's no real risk, as long as you follow the directions correctly. In saying that though, there's always a small risk when flashing anything to your phone, but as long as you do what you're supposed to do you can mitigate that risk.
Transmitted via Bacon
timmaaa said:
No worries, please refer to my guide that I've linked you to, it contains instructions for pretty much anything you need to do.
The wipes that I mentioned don't wipe your sd card, that isn't wiped unless you explicitly choose to wipe it in the advanced wipe menu.
When you made the backup of your stock ROM did you backup boot? If not, that's why your restore isn't booting. If you did, did you restore that as well?
You need to flash the 2.15 firmware because all recent ROMs require the updated firmware to be installed in order to operate correctly. In fact, they won't even flash of the firmware isn't present as there's a check in the updater script that'll stop the install if you don't have the correct firmware. There's no real risk, as long as you follow the directions correctly. In saying that though, there's always a small risk when flashing anything to your phone, but as long as you do what you're supposed to do you can mitigate that risk.
Transmitted via Bacon
Click to expand...
Click to collapse
First I would like to express my appreciation for your help and detailed instructions, Thank you.
Kikdroid 5 seams really nice, I finally got rid of the AT&T image.
You are right, I did not backup the stock boot.img .. I did not know I needed to .. or overlooked it in some instructions, well as I said, I have no experience and trying to learn... If there is a reference that I can read to understand mainly the terminology and the relationship better them .. please point it to me .. I have problem understanding some the used terminology, specially that kernel word seams that the kernel is the Android version .. maybe..
My worry with firmware flash is that I see in some instructions .. if it did not work .. or give an error .. flash it again "immediately" .. that immediately word scares me very much .. what if I did not do it fast enough .. am I going to loose my phone. That is something completely unclear to me, I have some knowledge in computers, but I do not understand how a software can damage a hardware.
Best regards ..
aabdo said:
First I would like to express my appreciation for your help and detailed instructions, Thank you.
Kikdroid 5 seams really nice, I finally got rid of the AT&T image.
You are right, I did not backup the stock boot.img .. I did not know I needed to .. or overlooked it in some instructions, well as I said, I have no experience and trying to learn... If there is a reference that I can read to understand mainly the terminology and the relationship better them .. please point it to me .. I have problem understanding some the used terminology, specially that kernel word seams that the kernel is the Android version .. maybe..
My worry with firmware flash is that I see in some instructions .. if it did not work .. or give an error .. flash it again "immediately" .. that immediately word scares me very much .. what if I did not do it fast enough .. am I going to loose my phone. That is something completely unclear to me, I have some knowledge in computers, but I do not understand how a software can damage a hardware.
Best regards ..
Click to expand...
Click to collapse
The XDA Encyclopedia is pretty handy for learning terminology:
http://forum.xda-developers.com/other-special/encyclopedia
The kernel isn't the Android version, it's a low level layer of firmware that basically handles interactions between the hardware and the software. Searching "what is a kernel" on Google should return a much better explanation than I can give.
When those instructions say you must give the same command again immediately it really just means to do it without anything else in between. You should actually give the command twice even if you don't receive the error, so make sure you do it twice.
Transmitted via Bacon
timmaaa said:
The XDA Encyclopedia is pretty handy for learning terminology:
http://forum.xda-developers.com/other-special/encyclopedia
The kernel isn't the Android version, it's a low level layer of firmware that basically handles interactions between the hardware and the software. Searching "what is a kernel" on Google should return a much better explanation than I can give.
When those instructions say you must give the same command again immediately it really just means to do it without anything else in between. You should actually give the command twice even if you don't receive the error, so make sure you do it twice.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaaa .. I will work on the following steps and update you with my progress .. best regards ..
timmaaa said:
The XDA Encyclopedia is pretty handy for learning terminology:
http://forum.xda-developers.com/other-special/encyclopedia
The kernel isn't the Android version, it's a low level layer of firmware that basically handles interactions between the hardware and the software. Searching "what is a kernel" on Google should return a much better explanation than I can give.
When those instructions say you must give the same command again immediately it really just means to do it without anything else in between. You should actually give the command twice even if you don't receive the error, so make sure you do it twice.
Transmitted via Bacon
Click to expand...
Click to collapse
timmaaa, I successfully got S-off on my phone, which is the second step in your instruction, that was not possible without your help, Thank you ..
I will now study the third step which I see explained very well in your guide to flash the 2.15 firmware.
I still have the Kickdroid 5 and I noticed that the phone is restarting very often now, it also looses signal, and that Google hangouts is not working, hopefully that will get better with the 2.15 firmware. By the way, what is that 2.15 Firmware? is that HTC officially released ROM? (firmware is a ROM?), I hope the relationship between the recovery, the boot, and the firmware are explained in the link you provided, because still these not clear to me. I am guessing I will not have Kickdroid 5 after flashing the 2.15 firmware .. is that correct?
Thank you very much for your help throughout this process.
aabdo said:
timmaaa, I successfully got S-off on my phone, which is the second step in your instruction, that was not possible without your help, Thank you ..
I will now study the third step which I see explained very well in your guide to flash the 2.15 firmware.
I still have the Kickdroid 5 and I noticed that the phone is restarting very often now, it also looses signal, and that Google hangouts is not working, hopefully that will get better with the 2.15 firmware. By the way, what is that 2.15 Firmware? is that HTC officially released ROM? (firmware is a ROM?), I hope the relationship between the recovery, the boot, and the firmware are explained in the link you provided, because still these not clear to me. I am guessing I will not have Kickdroid 5 after flashing the 2.15 firmware .. is that correct?
Thank you very much for your help throughout this process.
Click to expand...
Click to collapse
Those problems will stop once you have flashed the firmware. The firmware isn't a ROM, it's a lower level of firmware that includes the radio/modem, hboot, and various drivers. It is official from HTC. You will still have Kickdroid after installing the firmware.
XDA Moderator
Transmitted via Bacon