Related
Here is a link to the OTA. I didn't want to apply it till some smarter fellas could dig into it and see what kind of damage it does, so hopefully this will speed that process up a little.
Do not flash this .zip, it's for developmental purposes. I just made it available because I received the OTA on my phone this morning and did not see it posted yet.
https://docs.google.com/open?id=0B3QFSwNX3WR4VXpZcVR2M2NlQUU
Here's an alternative link if the above one fails or is too busy
http://db.tt/lLyptM9n
Sent from my HTC VLE_U using XDA
ozzie1p said:
Here is a link to the OTA. I didn't want to apply it till some smarter fellas could dig into it and see what kind of damage it does, so hopefully this will speed that process up a little.
https://docs.google.com/open?id=0B3QFSwNX3WR4VXpZcVR2M2NlQUU
Click to expand...
Click to collapse
Epic thank you sir
You guys rock!!!
EDIT: Sorry that sounded really NEWBish... I am unrooted and am currently having an issue re-unlocking my bootloader to root.
Is there an RUU available that I might be able to flash?
I wouldn't flash it until it gets sorted out what's in it. It looks like the firmware.zip has a new h-boot (hboot_8960_1.09.0000_20120402_signedbyaa.img) so if they've patched some holes that were in the old one then flashing this might screw you if they get s-off on the previous h-boot.......I think
Cayniarb said:
** this assumes that you have adb and fastboot in your PATH and that you know how to use them.
** this also assumes that you have some recovery.img file (named as such) saved in whatever directory you are running terminal commands from.
** this also assumes you are running linux. If all of the above conditions are met, the process should also be the same on Windows and OS X, but I have not tested that and cannot confirm that.
** this assumes that if you do not fully comprehend all of the above, that you will stop reading now. I am not responsible for any damage caused to your device by following these instructions.
Step 1: Find and download the following images from the 1.78.41.2 RUU: radio.img, wcnss.img, and adsp.img. Save them on your device's storage partition (/sdcard) named as listed here (** this assumes that if you use other names you also know how to adjust future commands).
Step 2: Boot your device into fastboot mode. Your choice of 'adb reboot bootloader' or manually powering down, booting to hboot, and selecting fastboot. (Future commands assume your device is plugged in to the computer at this point)
Step 3: On the computer, run: fastboot boot recovery.img
Step 4: Wait for your device to boot in to what looks like a normal recovery session. While it looks this way, it is not normal. In this recovery, you have the ability to do pretty much everything you can on an s-OFF device (flashing boot or other partitions, etc).
Step 5: This will depend on your recovery. Whatever the process is, make sure that your /sdcard partition is mounted (not mounting USB, but making the /sdcard partition readable to things like adb).
Step 6: On the computer, run:
adb shell
dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd if=/sdcard/wcnss.img of=/dev/block/mmcblk0p19
dd if=/sdcard/adsp.img of=/dev/block/mmcblk0p18
Step 7: In the same recovery session, on the device, flash whatever 1.78-based ROM you like (Note: I have not seen ill effects using this on a 1.53-based ROM, but YMMV).
Step 8: Reboot. Enjoy.
Click to expand...
Click to collapse
This is from the radio thread i would assume, that it will work the same way. All those files are included in the OTA zip file. Thoughts?
ozzie1p said:
I wouldn't flash it until it gets sorted out what's in it. It looks like the firmware.zip has a new h-boot (hboot_8960_1.09.0000_20120402_signedbyaa.img) so if they've patched some holes that were in the old one then flashing this might screw you if they get s-off on the previous h-boot.......I think
Click to expand...
Click to collapse
Right now I just want to get my damn bootloader unlocked and I cant seem to figure out what is going on with it. I've done this a million times so its not that I dont know what im doing like all the others have accused me of, its simply an issue that the unlock token flashes fine but upon rebooting the bootloader is still relocked. Its driving me mad right now... I just want to flash an T-Mo RUU to get back to stock at this point.
go to the official ruu thread by football and download the tmous ruu from there... put your phone into fastboot usb mode and start the ruu.
Will that RUU overwrite a newer H-Boot?
Radio 0.16.31501S.16_2_10.22.31501S.10L flashable zip here
Edit: Yes. This is from the update.
http://db.tt/W3l8QdGU
Another link just in case
Sent from my HTC One S
strker45 said:
go to the official ruu thread by football and download the tmous ruu from there... put your phone into fastboot usb mode and start the ruu.
Click to expand...
Click to collapse
I appreciate you trying to provide assistance. An RUU with a lower HBOOT will not overwrite a newer one so that option is not possible.
Thanks
how can this manually be applied? or is it even possible i know things have changed . but for w/e reason my phone still isnt seeing the ota and i've restored completely to stock with the offical ruu
Thanks guys, will try to update TrickDroid TMOUS ASAP
infinityhombre said:
Radio 0.16.31501S.16_2_10.22.31501S.10L flashable zip here
Click to expand...
Click to collapse
This is one version number short of the EU Radio.
Code:
EU Baseband Version: 0.16.31501S.17_2_10.23.31501S.10L
US Baseband Version: 0.16.31501S.16_2_10.22.31501S.10L
infinityhombre said:
Radio 0.16.31501S.16_2_10.22.31501S.10L flashable zip here
Click to expand...
Click to collapse
Did you pull this from the OTA?
Im kind of a noob here, how do i manually flash the OTA?
doktortaru said:
This is one version number short of the EU Radio.
Code:
EU Baseband Version: 0.16.31501S.17_2_10.23.31501S.10L
US Baseband Version: 0.16.31501S.16_2_10.22.31501S.10L
Click to expand...
Click to collapse
Makes me wonder if it's even worth updating to the US one. Seems like it'd be better to just use the EU radio.
There's one way to find out....
infinityhombre said:
Radio 0.16.31501S.16_2_10.22.31501S.10L flashable zip here
Click to expand...
Click to collapse
Thanks! Quick and easy
Okay so I have a question I'm rooted on my gf shift 2.3.4 with S-on with clockworks do I need to downgrade to 2.2 or anything to flash any Rom here ??
Sent from my SPH-D700 using xda app-developers app
ivcesar said:
Okay so I have a question I'm rooted on my gf shift 2.3.4 with S-on with clockworks do I need to downgrade to 2.2 or anything to flash any Rom here ??
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
It will make things a lot simpler for you if you are Fully Rooted ( S-Off ) . You can Flash Roms with S-On, but it is a bit more involved. Because you cannot flash any Kernels. Being that most Roms have custom Kernels it creates a bit of an issue. It can be done, it just means you are going to have to modify any Rom that has a Custom Kernel before you try and flash it. You were using THIS THREAD correct? I would recommend finishing the Downgrade process to 2.2 in order to achieve Full Root. It will make life much easier in the long run.
+1!
Sent from my PG06100 using xda premium
prboy1969 said:
It will make things a lot simpler for you if you are Fully Rooted ( S-Off ) . You can Flash Roms with S-On, but it is a bit more involved. Because you cannot flash any Kernels. Being that most Roms have custom Kernels it creates a bit of an issue. It can be done, it just means you are going to have to modify any Rom that has a Custom Kernel before you try and flash it. You were using THIS THREAD correct? I would recommend finishing the Downgrade process to 2.2 in order to achieve Full Root. It will make life much easier in the long run.
Click to expand...
Click to collapse
Thank you for taking your time an swering my questions its my first htc phone trying to root so I'm all lost an all over the place haha well to answer your question yes I'm stuck between 15 an step 18. I wasn't sure how flash misc.img file from adb or phone I was a little lost their
Sent from my SPH-D700 using xda app-developers app
ivcesar said:
Thank you for taking your time an swering my questions its my first htc phone trying to root so I'm all lost an all over the place haha well to answer your question yes I'm stuck between 15 an step 18. I wasn't sure how flash misc.img file from adb or phone I was a little lost their
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Make sure the misc.img is on the Root of your SD Card. Also the PG06IMG.zip from the OP. You can Copy and Paste. Or push them there with ADB. I use the Copy and Paste method. Since it sounds like your a little lost on the exact commands, I'll give them to you to do using Terminal Emulator as per the Guide.
Open Terminal Emulator.
Type: su
Hit Enter
Type: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Hit Enter
After that just go to Step #18 of the Guide, and follow the rest of the Instructions. Before you do anything I would suggest that you Reread instructions, and Re-watch the Videos. Just for your own peace of mind . Personally though I would probably if it were me start the Entire process over. RUU back to 2.3.4 and just redo the entire process. But that's just me .
prboy1969 said:
Make sure the misc.img is on the Root of your SD Card. Also the PG06IMG.zip from the OP. You can Copy and Paste. Or push them there with ADB. I use the Copy and Paste method. Since it sounds like your a little lost on the exact commands, I'll give them to you to do using Terminal Emulator as per the Guide.
Open Terminal Emulator.
Type: su
Hit Enter
Type: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Hit Enter
After that just go to Step #18 of the Guide, and follow the rest of the Instructions. Before you do anything I would suggest that you Reread instructions, and Re-watch the Videos. Just for your own peace of mind . Personally though I would probably if it were me start the Entire process over. RUU back to 2.3.4 and just redo the entire process. But that's just me .
Click to expand...
Click to collapse
Hey I just saw the reply thank you again for taking your time i figure it out i when into adb shell since i could get to do anything in terminal for nothing push with adb when to 2.2 root now in a search of a rom lol thank you for you help
Sent from my SPH-D700 using xda app-developers app
Glad you got it sorted out . I would try a few different Roms before settling on one. A few pieces of advice. One is to make sure you Flash the Rom, or Roms of your choosing correctly. Meaning do a Full Wipe, before Flashing. Also after you Flash a Rom, make sure that you give it a least a few days to settle in. That way you have a better idea of how each Rom is, before making a decision on whether you like it or not.
prboy1969 said:
Glad you got it sorted out . I would try a few different Roms before settling on one. A few pieces of advice. One is to make sure you Flash the Rom, or Roms of your choosing correctly. Meaning do a Full Wipe, before Flashing. Also after you Flash a Rom, make sure that you give it a least a few days to settle in. That way you have a better idea of how each Rom is, before making a decision on whether you like it or not.
Click to expand...
Click to collapse
So my question is... I had intentionally 'half rooted' my phone cause i wanted to stick with the stock ROM for the time being and SuperUser granted enough permissions to do some of the things i needed to do. Evervolv came out with a JB build that I wanted to try; so I have to get it to S-OFF now (which I did initially but restored it cause at the time I didn't like the ROM I flashed and ran an RUU). If I made a CWM backup of my current 2.3.4 settings, after I downgrade and root can i revert back to it if I don't like the new ROM?
Thanks
So I'm not sure I follow you. Are you currently " S-Off " ? If you are, and made a Nandroid backup. Then yes you can revert back to the Nandroid backup at any time. But if you ran an RUU, then no you cannot Nandroid back. The Nandroid backup is still on your SD Card, but you cannot access it with the Factory Recovery.
prboy1969 said:
So I'm not sure I follow you. Are you currently " S-Off " ? If you are, and made a Nandroid backup. Then yes you can revert back to the Nandroid backup at any time. But if you ran an RUU, then no you cannot Nandroid back. The Nandroid backup is still on your SD Card, but you cannot access it with the Factory Recovery.
Click to expand...
Click to collapse
Ok, sorry. I rooted it and got s-off when I first got my shift but decided to go back stock via RUU. few weeks later i went back and followed Vicodan's post only halfway to get root when I needed it via SuperUser. So I do have CWM installed and my backups work (I found out when the ROMS i been trying to load won't even boot and restoring from backups work fine). Thanks for clarifying that for me, here I come Evervolv
Just curious as to why you do not want Full Root ? Also if your still " S-On " trying to flash Roms can become a PIA . Reason being, most Roms have custom kernels. Which if you are not Full Root " S-Off " becomes an issue.
To flash any ROM while s-on unlocked you will need to use fastboot for the kernel. So have adb and fastboot setup and drag the boot.img from the ROM your flashing into your fastboot folder. Boot into recovery and do a full wipe as always and flash the ROM, Once the ROM is flashed plug the phone in and open a command prompt, cd to your platform-tools folder and type adb reboot bootloader, once it reboots into bootloader make sure it says fastboot usb in red. If it don't choose fastboot, then use this command fastboot flash boot boot.img and once it says it's done reboot to enjoy the custom ROM/KERNEL combo
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
To flash any ROM while s-on unlocked you will need to use fastboot for the kernel. So have adb and fastboot setup and drag the boot.img from the ROM your flashing into your fastboot folder. Boot into recovery and do a full wipe as always and flash the ROM, Once the ROM is flashed plug the phone in and open a command prompt, cd to your platform-tools folder and type adb reboot bootloader, once it reboots into bootloader make sure it says fastboot usb in red. If it don't choose fastboot, then use this command fastboot flash boot boot.img and once it says it's done reboot to enjoy the custom ROM/KERNEL combo
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Yes Sir that's what he'd have to do every time he flashed a Rom with a custom kernel. Like I said, more involved than the way you would normally Flash a Rom . It's easier to be Fully Rooted, if your able to be IMO.
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
Yes Sir that's what he'd have to do every time he flashed a Rom with a custom kernel. Like I said, more involved than the way you would normally Flash a Rom . It's easier to be Fully Rooted, if your able to be IMO.
TEAM MiK
MikROMs Since 3/13/11
Click to expand...
Click to collapse
Oh definitely, because if he wanted to test a kernel he would have to flash the new kernel in recovery so the modules for wifi/wimax are placed correctly then go into fastboot to flash the boot.img and that is just way to damn much work.
The advantages to s-off are endless IMHO
Sent from my myTouch_4G_Slide using Tapatalk 2
He'll yes to much work. Not mention you don't really gain anything by not having Full Root " S-Off " . In almost every case it makes things more difficult
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
Just curious as to why you do not want Full Root ? Also if your still " S-On " trying to flash Roms can become a PIA . Reason being, most Roms have custom kernels. Which if you are not Full Root " S-Off " becomes an issue.
Click to expand...
Click to collapse
After going s-off and trying some roms initially, I reverted back and for a while I liked the stock 2.3.4, so I just rolled with that and was content with not having full root (the few things i wanted to tweak, superuser could do). Seeing now that there is finally a somewhat usable ICS build (4g is a non issue since I live in a fringe area anyways) I tried to load it to no avail. So it was time to be full s-off again :laugh:
Anyhow, I got s-off quickly and now running a new ROM :good:
Good to hear . I'm a big advocate of being Full Rooted " S-Off " on any Android device. Even if your running the Stock Rooted Rom. Which BTW since you said you liked it, did you see THIS thread. It's the latest OTA Stock Rooted.
prboy1969 said:
Good to hear . I'm a big advocate of being Full Rooted " S-Off " on any Android device. Even if your running the Stock Rooted Rom. Which BTW since you said you liked it, did you see THIS thread. It's the latest OTA Stock Rooted.
Click to expand...
Click to collapse
Thanks - I wanted to get away from GB for the time being and try the new ICS/JB stuff but I'll keep this one just in case
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?
I've got an HTC One X that unfortunately has not survived several attempts to tinker with it (screen replacement didn't go as planned). I'd like to attempt to repurpose it. It boots, I can access it via adb. I was hoping that I'd be able to use something like my hdmi out dongle to get some kind of output, but for some reason, it's not working (can't remember if I need to enable it in the software or not). Wondering if there's a way I can either flash some software to the phone, access it via abd to get hdmi working, or some other solution that I haven't thought of. It's currently running some version of CleanRom (can't remember which at the moment) and I can get a screen cast (albeit laggy) from a java app I found floating around the internet.
Any suggestions from the smart folks here?
ChummyDays said:
Your phone feels like its been raped multiple times and been beaten. Haha it sounds like you trashed that thing
I'm sorry I couldn't resist
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Well... You're not wrong.
nice avatar Smackdog
Just how stubborn/capable are you? Here's one idea if you're persistent enough.
http://forum.xda-developers.com/showthread.php?t=1728222
This is for the Tegra 3 HOX but seems like someone could manage a port.
iElvis said:
Just how stubborn/capable are you? Here's one idea if you're persistent enough.
http://forum.xda-developers.com/showthread.php?t=1728222
This is for the Tegra 3 HOX but seems like someone could manage a port.
Click to expand...
Click to collapse
This is a pretty good solution. At this point I think I'm just looking to figure out a way to flash a rom that would give me HDMI out by default. I used to be able to flash things via Odin, but that was with my samsung phones. Not sure if there's a similar process for the HTC guys. And also not sure if there's a way to get whatever ROM to output to HDMI without having to mess with settings. Ideas?
Smackdog said:
This is a pretty good solution. At this point I think I'm just looking to figure out a way to flash a rom that would give me HDMI out by default. I used to be able to flash things via Odin, but that was with my samsung phones. Not sure if there's a similar process for the HTC guys. And also not sure if there's a way to get whatever ROM to output to HDMI without having to mess with settings. Ideas?
Click to expand...
Click to collapse
I haven't tried it but I thought we had that stock?
http://forum.xda-developers.com/showthread.php?t=1651296
iElvis said:
I haven't tried it but I thought we had that stock?
http://forum.xda-developers.com/showthread.php?t=1651296
Click to expand...
Click to collapse
Then it might be the fact that my ROM doesn't support it? I'd have no problem flashing back to stock, I just need a way to flash either via adb, or another non-recovery based method.
Smackdog said:
I just need a way to flash either via adb, or another non-recovery based method.
Click to expand...
Click to collapse
You can flash roms via adb on some phones via fastboot update if you are HTCDev unlocked. I have not done this nor I have I heard of anyone doing it with a One X. But since your phone is already on life support, what's the harm?
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#ROM_Flashing_2
I would try to use a stock rooted rom rather than anything custom.
iElvis said:
You can flash roms via adb on some phones via fastboot update if you are HTCDev unlocked. I have not done this nor I have I heard of anyone doing it with a One X. But since your phone is already on life support, what's the harm?
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#ROM_Flashing_2
I would try to use a stock rooted rom rather than anything custom.
Click to expand...
Click to collapse
Excellent. I wasn't sure if you could do this with any ol' zipped ROM or if there was a special file format that needed it. I'll give this a go tonight and see if it pans out. Thanks again for the suggestion!
Fastboot won't let you flash any unsigned zips. Ur best bet is to pull the system.img and boot.img from a ruu, then with adb, dd the system.img to dev/block/mmcblk0p33 and boot.img to dev/block/mmcblk0p21, reboot and your back to stock
Sent from my HTC One XL using Tapatalk 2
18th.abn said:
Fastboot won't let you flash any unsigned zips. Ur best bet is to pull the system.img and boot.img from a ruu, then with adb, dd the system.img to dev/block/mmcblk0p33 and boot.img to dev/block/mmcblk0p21, reboot and your back to stock
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Sorry, don't quite understand what you mean by "dd the *.img files". Could you elaborate?
18th.abn said:
Fastboot won't let you flash any unsigned zips. Ur best bet is to pull the system.img and boot.img from a ruu, then with adb, dd the system.img to dev/block/mmcblk0p33 and boot.img to dev/block/mmcblk0p21, reboot and your back to stock
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Smackdog said:
Sorry, don't quite understand what you mean by "dd the *.img files". Could you elaborate?
Click to expand...
Click to collapse
For system.img
dd if=/"location of system.img without quotes" of=/dev/block/mmcblk0p33
For boot.IMG
dd if=/"location of boot.img without quotes" of=/dev/block/mmcblk0p21
I had to do something similar to another device
The screen wouldn't come on, I had to boot into boot and select recovery then used adb shell with similar commands above to set it to stock
Sent from my One X using Tapatalk 2
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.