Related
Alright, so we all know it's confusing to differentiate the One XL from the One X, especially since Rogers and AT&T insist on calling it the One X.
IF YOU HAVE A "ONE X" FROM ROGERS/AT&T, YOU HAVE THE ONE XL. DON'T EVEN BOTHER VISITING THE ONE X FORUMS.
Now, you've gone and downloaded CWM from the One X forums and flashed it to your One XL, and you're semi-bricked. Let's get you out of that pickle. Please note that I have not done any of this to my own One XL, as there's no ROMs or custom recovery images or kernels for our phone yet. However, just this morning I performed a similar operation on my Jetstream, and the steps will be identical. I take no responsibility for any problems you experience.
First, you'll need to download the leaked RUU that can be found here: http://forum.xda-developers.com/showthread.php?t=1550930
EDIT: designgears has offered a newer recovery image. I'm not sure what advantages it would bring, but at least there's a second option: http://www.gigashare.in/53885
Please note that this is marked as the AT&T RUU, so there's no guarantee this will work for Rogers. However, your recovery mode is screwed anyway, so in my opinion, it couldn't hurt to try.
Once you've downloaded the RUU, run it. You don't need to install the RUU itself, we just have to have the application running. Once running, it'll create a "rom.zip" file in a temp folder somewhere in your user profile. While the RUU is open, just search for "rom.zip" and you should find it. Open this file and extract "recovery_signed.img" to your computer, into the same folder as your "fastboot" application. Once you've done this, close the zip file and exit the RUU.
Now, boot your device into fastboot mode
Code:
adb reboot bootloader
Once in bootloader mode, you may need to select "fastboot" from the menu.
Now that you're in fastboot mode, you can flash the recovery we extracted from the RUU:
Code:
fastboot flash recovery recovery_signed.img
Your screen will go through a couple brief steps, something like "sending recovery_signed.img" then "writing recovery_signed.img" and then "OK."
Try to boot into recovery now, and you should see the standard HTC recovery mode!
I really hope this helps everyone out. I'll iterate again that I have no tried this with my One XL, so I have no actual proof that this will work. But, if you've already flashed the wrong recovery image, you should be somewhat familiar with these steps already.
EDIT: Please post your success with this method. As I haven't tested, I'd like to know if everything's kosher, and I can change the instructions accordingly if something's wrong.
Hey, sorry I didn't get back to you sooner, went to bed.
Here is just the recovery image for a newer, unreleased leak.
http://www.gigashare.in/53885
1.61.502.1 CL49502
designgears said:
Hey, sorry I didn't get back to you sooner, went to bed.
Here is just the recovery image for a newer, unreleased leak.
http://www.gigashare.in/53885
Click to expand...
Click to collapse
Heh, don't apologize to me, my phone's locked and running fine. (I've had the phone since Friday... I think this is the longest I've ever gone without rooting an Android phone.)
I'll put that link up in the first post, thanks!
EDIT: Oh! And is that AT&T or Rogers?
craig0r said:
Heh, don't apologize to me, my phone's locked and running fine. (I've had the phone since Friday... I think this is the longest I've ever gone without rooting an Android phone.)
I'll put that link up in the first post, thanks!
EDIT: Oh! And is that AT&T or Rogers?
Click to expand...
Click to collapse
It's AT&T recovery.
Flashed but still having trouble. Got into recovery but can't boot.
Going to see if re-locking the bootloader may help. Only thing different I've done is that I ran that flash_boot.zip thing that Leedroid had on his page. It just seems to push a boot.img file and clear the fastboot cache.
Does anyone have that particular boot.img file? Pretty please?
For myself I will leave it for now and wait until an official rogers RUU or custom recovery to make sure I don't break it again
Sent from my HTC One X
bongd said:
Flashed but still having trouble. Got into recovery but can't boot.
Going to see if re-locking the bootloader may help. Only thing different I've done is that I ran that flash_boot.zip thing that Leedroid had on his page. It just seems to push a boot.img file and clear the fastboot cache.
Does anyone have that particular boot.img file? Pretty please?
Click to expand...
Click to collapse
The rom.zip file from the AT&T ruu should have the boot.img file in it. you can flash it with
Code:
fastboot flash boot boot.img
However, the boot partition is a WEE bit more critical to the phone's function than the recovery partition. Dunno if I'd be flashing it myself, at least not to a Rogers phone.
Sent from my HTC One X using xda premium
craig0r said:
The rom.zip file from the AT&T ruu should have the boot.img file in it. you can flash it with
Code:
fastboot flash boot boot.img
However, the boot partition is a WEE bit more critical to the phone's function than the recovery partition. Dunno if I'd be flashing it myself, at least not to a Rogers phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks, man. Someone said they flashed the entire RUU to their Rogers phone so I don't think it could be too harmful.
I only have my Ubuntu machine and Wine is being fussy and not extracting the rom.zip archive properly. I'll see if something gets released soon. I rarely see Rogers RUU so hopefully I'm not waiting too long. Reactivated my SIM for my Galaxy Nexus but still sad lol
I feel your pain!
bongd said:
Thanks, man. Someone said they flashed the entire RUU to their Rogers phone so I don't think it could be too harmful.
I only have my Ubuntu machine and Wine is being fussy and not extracting the rom.zip archive properly. I'll see if something gets released soon. I rarely see Rogers RUU so hopefully I'm not waiting too long. Reactivated my SIM for my Galaxy Nexus but still sad lol
Click to expand...
Click to collapse
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
krepler said:
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
Click to expand...
Click to collapse
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
bongd said:
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
Click to expand...
Click to collapse
Ok, I'm in the middle of downloading the evita leaked files. I can't extract it from my phone since I need root... unless you know a way other than adb shell? Either way, I don't think you can access it without root. I've tried a few ways with no luck.
I see you can't access the evita files so the best I can do for you is extract it from there for you. Download is slow as hell, so bear with me!
krepler said:
Ok, I'm in the middle of downloading the evita leaked files. I can't extract it from my phone since I need root... unless you know a way other than adb shell? Either way, I don't think you can access it without root. I've tried a few ways with no luck.
I see you can't access the evita files so the best I can do for you is extract it from there for you. Download is slow as hell, so bear with me!
Click to expand...
Click to collapse
No need to ask for my patience, bro. It's hugely appreciated! Thanks a ton!
bongd said:
No need to ask for my patience, bro. It's hugely appreciated! Thanks a ton!
Click to expand...
Click to collapse
My new issue is I'll have to make a couple more posts before I can add urls to them, since I never post on the forums. Gotta start somewhere...
Scratch that, you the good 'ol copy and paste.
http://www.gigashare.in/d4129 = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 recovery_signed.img
http://www.gigashare.in/8adee = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 boot_signed.img
krepler said:
My new issue is I'll have to make a couple more posts before I can add urls to them, since I never post on the forums. Gotta start somewhere...
Scratch that, you the good 'ol copy and paste.
http://www.gigashare.in/d4129 = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 recovery_signed.img
http://www.gigashare.in/8adee = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 boot_signed.img
Click to expand...
Click to collapse
and the latest:
http://www.gigashare.in/0029e = Cingular 1.68.502.1 Radio 0.16.32.09.01 boot_signed.img
http://www.gigashare.in/03695 = Cingular 1.68.502.1 Radio 0.16.32.09.01 recovery_signed.img
Should've just waited and posted these ones... buuuuuuut, I have no patience.
Hopefully the boot.img works for you! Let me know how she goes.
bongd said:
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
Click to expand...
Click to collapse
Bongd, The recovery works for you? My situtation is in the same boat with Krepler minus the boot.img. I am little bit worry if I load the AT&T recovery and that will conflict the boot.img in Rogers phone.
---------- Post added at 07:25 AM ---------- Previous post was at 07:22 AM ----------
krepler said:
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
Click to expand...
Click to collapse
Krepler, Can you tell me how did you solve your recovery? I am in your sisutation as well, flash the wrong recovery and once I boot to recovery and it will occur the boot loop, however I am still able to use the One X (Semi-bricked). Did you flash the stock recovery from Rogers or the one that you just posted from AT&T?
Elin28 said:
Bongd, The recovery works for you? My situtation is in the same boat with Krepler minus the boot.img. I am little bit worry if I load the AT&T recovery and that will conflict the boot.img in Rogers phone.
Click to expand...
Click to collapse
One does not interfere with the other. Recovery is pretty much its own operating system, completely segregated from the rest of the phone. It can neither hinder nor enhance the booting of your phone in normal mode. You could theoretically flash a random sequence of ones and zeros to the recovery partition, and the phone would continue to boot just fine. Until you try and go into recovery mode that is. Flashing the recovery_signed.img as per my instructions is safe in regards to the phone's normal operation. I can't promise that it's a working recovery, however, as I've not tried it myself.
Awesome! Just booted up, my man. A thousand fellatios to you!! Please message me your Paypal address so I can buy you a beer or two.
Haven't tried the Cingular ones but the AT&T ones worked just fine. I'm betting it'll be damn near identical, save probably a few radio adjustments or very minor adjustments.
Booted to the main screen so I should be able to set things up. But I'll chime in and report if there are any major issues. Thanks again!!
Hey I am happy your phone boot up man!!
I am still having trouble with the recovery. I try flash the att& the cingular recovery. good thing is no bootloop I see an image showing black phone and a green circle. then I end up with image of a phone with red triangle with a "!" inside. and then the phone reboots.
am I doing something wrong?
Thanks
bongd said:
Awesome! Just booted up, my man. A thousand fellatios to you!! Please message me your Paypal address so I can buy you a beer or two.
Haven't tried the Cingular ones but the AT&T ones worked just fine. I'm betting it'll be damn near identical, save probably a few radio adjustments or very minor adjustments.
Booted to the main screen so I should be able to set things up. But I'll chime in and report if there are any major issues. Thanks again!!
Click to expand...
Click to collapse
@bongd
Awesome bro!!!! Glad you got your hox up and running.
Sent from wherever I am!
yoohoohoo said:
Hey I am happy your phone boot up man!!
I am still having trouble with the recovery. I try flash the att& the cingular recovery. good thing is no bootloop I see an image showing black phone and a green circle. then I end up with image of a phone with red triangle with a "!" inside. and then the phone reboots.
am I doing something wrong?
Thanks
Click to expand...
Click to collapse
Have you tried running "fastboot erase cache"?
What other steps have you done as well? The killer for me was the boot.img file that Leedroid created as part of his ROM installation. The AT&T recovery is what I had used. For a moment I thought I might need to try flashing the system.img file like redwreck had to, but I didn't need to.
Perhaps someone could upload that as well, please? If you need to flash that, it's "fastboot flash system system.img" and it'll flash that too. I always do "fastboot reboot" after as well.
I trust that these should work. Hopefully there'll be a full Rogers RUU so we can flash that just to be on the safe side. Best of luck! I'll keep an eye on this thread as well.
Since I posted earlier I've been setting things up and it's working like a damn charm. Tried exhausting every weird and quirky feature I thought might screw up, but I can't find anything that's not working.
hi there,
I have Hboot 1.08, is there any flash-able zip files to update the radio?
Check the op of the OTA update thread in this very section
Sent from my HTC One S
ultimul said:
hi there,
I have Hboot 1.08, is there any flash-able zip files to update the radio?
Click to expand...
Click to collapse
The answer is yes, so do as Pheroh says
Try to either flashing through recovery or manually dd-ing the image files.
Don't take an OTA or run an RUU, as that will update your HBOOT.
You want to stay on 1.08.
-Jobo
I dont want the OTA update, anyway the phone is rooted and using custom rom so dont think ota will ever work.
where can I find the latest radio, zip files flashable thru recovery or fastboot?
touch of jobo said:
Try to either flashing through recovery or manually dd-ing the image files.
Don't take an OTA or run an RUU, as that will update your HBOOT.
You want to stay on 1.08.
-Jobo
Click to expand...
Click to collapse
ultimul said:
I dont want the OTA .. where can I find the latest radio, zip files flashable thru recovery or fastboot?
Click to expand...
Click to collapse
This is the thread Pheroh was referring to: OTA Update to Android 4.0.4 for S4 is Out! You can extract the images from the OTA .zip or use any of the methods explained in post #1.
I used the one by Dima901 and flashed thru twrp
https://www.dropbox.com/s/zvi1a70n41yy2ri/radio_OTA_19072012.zip
rugmankc said:
I used the one by Dima901 and flashed thru twrp
]
Click to expand...
Click to collapse
10x a lot;
flashed thru recovery in no time.
hope will solve the few little problems with data and Bluetooth I had.
It has helped many from reading posts. I am not sure I gained anything though.
But, always nice to have latest anything--
rugmankc said:
It has helped many from reading posts. I am not sure I gained anything though.
But, always nice to have latest anything--
Click to expand...
Click to collapse
I can only hope will improve something. I have a problem with data switching from G to 3G to H for few seconds when I first start every session, I dont know it has impact on actually speed;
most annoying is the Bluetooth dropout from time to time, even at (very) short distances, my earpiece has no problem cause i tested with my other phones.
Anyway, if things goes wrong I still can go back to 0.16 radio I had before ( I hope at least )
Yes, flashing radios is Rom independent. Just don't upgrade to hboot .13 or higher. Or, you will have issues flashing radios. Hope new radio helps.
rugmankc said:
Yes, flashing radios is Rom independent. Just don't upgrade to hboot .13 or higher. Or, you will have issues flashing radios. Hope new radio helps.
Click to expand...
Click to collapse
for the moment I use trickdroid 6.0, probably I'll change in the future if support and updates stop;
from what I know, changing rom's shouldn't change the hboot, only ruu upgrade will change it. true?
correct-
radios and hboots stay unless flashing a ruu
if/when we get s-off then hboot can be changed and we will be able to adjust partition table sizes for more data size
first day of testing, results are confusing
the data icon stays now mostly at 3G, think this is the real provider network; the differences in speed are not noticeable
for the bluetooth, the same thing, earpiece disconnect after few minutes even if with the phone in my hand; something is wrong here; I'll have to look for my older earpiece to try it. maybe plantronics 520 is not fully compatible with htc one s
should I try a custom kernel? any chance will help?
I had the Bluetooth disconnect issue . Haven't flashed a radio yet but flashing the Sensisimo Rom has seem to have fixed the Bluetooth disconnect. Fix could have something to do with the Rom being based off the latest update available (2.21 or something like that). I'm having data disconnect issues, does new radio fix it?
T-MobileUS HTC One S
I would try it, no harm done
looks like bloetooth disconnect is a small bug in trickdroid 6.0; tried another 2 earpieces and all are doing the same;
just flash trickdroid 7.1.0, I'll try it tomorrow and came back with feedback.
I won an S4 S off of ebay, but on the downside that the vibrate motor & the touch buttons at the bottom of the screen didn't work
I bought it on a gamble that it was a software problem and a root/flash would resolve it, unfortunately It didn't. I've stripped it down and reseated various ribbon cables but that didn't help either - is there an app that can show button presses to see if its totally dead?
For now I'm getting by with pie launcher
With the vibrate motor I can get a replacement for that and have no problem fitting it, are the onscreen buttons in any way matched to this bottom circuit board or are they part of the screen?
Any help is appreciated
Edit
Reading through this thread It seems like it could be a hboot issue? The seller did say that it occurred after the OTA to JB.
My current info is: s-off, supercid
Hboot: 2.13.0000
Radio: 1.11.50.05.20
Opendsp: v31.1.0.45.0815
In this thread it states that phones that have been OTA'd are at risk of bricking, however at the end of the thread the OP states the method is superceeded now s-off has been achieved.
Can a different hboot just be flashed much the same as a new radio or are there other risks involved? if so I'll get flashing and experiment
Chilled
Edit 2
I've managed to partially solve the issue - I bought a replacement vibrate motor/mic/ribbon assembly off of amazon here now I don't know if it was me tearing down/rebuilding and reseating the cables (you have to go right to seperating the screen from its housing to be able to get the motor off) but now I have the home and 'switcher?!' buttons working - just not the back button - but I can deal with that
Hopefully that might help someone else with this
Urinal_Mint said:
Can a different hboot just be flashed much the same as a new radio or are there other risks involved?
Click to expand...
Click to collapse
Yes. If you're S-Off, you can flash hboot.
I posted up some in this thread: http://forum.xda-developers.com/showthread.php?t=1777223 in post #148 and #274 (..modded to blank out the red warning overlay text, as well as originals)
touch of jobo said:
Yes. If you're S-Off, you can flash hboot.
I posted up some in this thread: http://forum.xda-developers.com/showthread.php?t=1777223 in post #148 and #274 (..modded to blank out the red warning overlay text, as well as originals)
Click to expand...
Click to collapse
Cheers touch, i'll give that a try and see what happens.
Am I right in my understanding that I can't downgrade my hboot to an earlier version without creating an expensive brick?
Urinal_Mint said:
Am I right in my understanding that I can't downgrade my hboot to an earlier version without creating an expensive brick?
Click to expand...
Click to collapse
No. If you're S-Off you can just flash hboot. No bricking required.
The bricking method was (is?) for downgrading hboot with S-On.
-Jobo
Sweet, right time to go on a flashing mission and see what happens!
same problem here
Urinal_Mint said:
I won an S4 S off of ebay, but on the downside that the vibrate motor & the touch buttons at the bottom of the screen didn't work
I bought it on a gamble that it was a software problem and a root/flash would resolve it, unfortunately It didn't. I've stripped it down and reseated various ribbon cables but that didn't help either - is there an app that can show button presses to see if its totally dead?
For now I'm getting by with pie launcher
With the vibrate motor I can get a replacement for that and have no problem fitting it, are the onscreen buttons in any way matched to this bottom circuit board or are they part of the screen?
Any help is appreciated
Edit
Reading through this thread It seems like it could be a hboot issue? The seller did say that it occurred after the OTA to JB.
My current info is: s-off, supercid
Hboot: 2.13.0000
Radio: 1.11.50.05.20
Opendsp: v31.1.0.45.0815
In this thread it states that phones that have been OTA'd are at risk of bricking, however at the end of the thread the OP states the method is superceeded now s-off has been achieved.
Can a different hboot just be flashed much the same as a new radio or are there other risks involved? if so I'll get flashing and experiment
Chilled
Click to expand...
Click to collapse
I have the same problem with my HTC One S. There is no physical damage to the hardware buttons but they do not work. Here are my observations so far:
If I turn on the phone from power off, the buttons work fine. After the phone goes to sleep, the buttons stop working. I have put the phone on to never sleep and the buttons stay working. Once the power button is pressed (put it to sleep) or auto timer sleep, buttons stop working.
Does yours behave the same?
My phone info:
Bootloader unlocked
S-OFF, SuperCID
HBOOT 2.15
I have tried many ROMs and some RUU, all with the same results.
---------- Post added at 10:51 AM ---------- Previous post was at 10:08 AM ----------
catdogdiamond said:
I have the same problem with my HTC One S. There is no physical damage to the hardware buttons but they do not work. Here are my observations so far:
If I turn on the phone from power off, the buttons work fine. After the phone goes to sleep, the buttons stop working. I have put the phone on to never sleep and the buttons stay working. Once the power button is pressed (put it to sleep) or auto timer sleep, buttons stop working.
Does yours behave the same?
My phone info:
Bootloader unlocked
S-OFF, SuperCID
HBOOT 2.15
I have tried many ROMs and some RUU, all with the same results.
Click to expand...
Click to collapse
I just tried [ROM][S4][AOSPA3+][10jun] UNOFFICIAL PARANOIDANDROID 3.60 | HALO 10
and my buttons work all the time now.
Seems to be a great ROM. Only unable to rotate the screen which is a known bug but I would really like that to be able to use as a daily driver.
Right now it fixes my phone so it's the one I'm using. Also has PIE built in.
catdogdiamond said:
I have the same problem with my HTC One S. There is no physical damage to the hardware buttons but they do not work. Here are my observations so far:
If I turn on the phone from power off, the buttons work fine. After the phone goes to sleep, the buttons stop working. I have put the phone on to never sleep and the buttons stay working. Once the power button is pressed (put it to sleep) or auto timer sleep, buttons stop working.
Does yours behave the same?
My phone info:
Bootloader unlocked
S-OFF, SuperCID
HBOOT 2.15
I have tried many ROMs and some RUU, all with the same results.
---------- Post added at 10:51 AM ---------- Previous post was at 10:08 AM ----------
I just tried [ROM][S4][AOSPA3+][10jun] UNOFFICIAL PARANOIDANDROID 3.60 | HALO 10
and my buttons work all the time now.
Seems to be a great ROM. Only unable to rotate the screen which is a known bug but I would really like that to be able to use as a daily driver.
Right now it fixes my phone so it's the one I'm using. Also has PIE built in.
Click to expand...
Click to collapse
On mine I've had nothing from the buttons at all, so far come from stock, to vibers & now on carbon
My hboot is the same as yours and I'm on the latest EU firmware 3.16.401.8. I've flashed every hboot from 1.06 up to 2.15 and it made no difference
I'll give PA a flash onto there and see how it goes.
Currently looking into how to flash new firmwares onto it to downgrade to a pre JB firmware as that was the reported cause of the buttons to stop working - seems I have to relock, flash, unlock again - but not sure as i'm s-off
Edit
Sadly PA didn't restore button function for me, i'll have to do more fiddling
Just a hunch, but could either of you try and flash the rpm.img from an older RUU, say 2.31 or older. (It goes into p10.)
-Jobo
(If you don;t know how to do this, I can make a flashable zip but not right now.)
i would like to try it
touch of jobo said:
Just a hunch, but could either of you try and flash the rpm.img from an older RUU, say 2.31 or older. (It goes into p10.)
-Jobo
(If you don;t know how to do this, I can make a flashable zip but not right now.)
Click to expand...
Click to collapse
Hi I am interested in trying anything. I have tried RUU older stock versions of T-Mobile, Bell and Rogers. Could you please make the zip or tell me the steps. Thanks
touch of jobo said:
Just a hunch, but could either of you try and flash the rpm.img from an older RUU, say 2.31 or older. (It goes into p10.)
-Jobo
(If you don;t know how to do this, I can make a flashable zip but not right now.)
Click to expand...
Click to collapse
I would be interested in giving this a try, is it as simple as extracting an older RUU & replacing rpm.img in p10 - or do i need to flash it via recovery?
Downgrading from JB firmware to an ICS one is in my list of things to try, but I don't know how risky this is - assuming replacing rpm.img has a similar effect.
My one s is chilling out on my desk at work atm, on my trusty sensation for the time being - but do have a new ribbon cable for vibrate/mic on order to fix that side of things (hopefully!) i'll be back in the office on tues & do some more testing!
[OT] Gahh, the capatcha is annoying! [/OT!]
catdogdiamond said:
Hi I am interested in trying anything. I have tried RUU older stock versions of T-Mobile, Bell and Rogers. Could you please make the zip or tell me the steps. Thanks
Click to expand...
Click to collapse
Attached is a .zip that contains the rpm.img from the 1.78 RUU. (I flashed it on my own device before posting.)
But if you've already tried older RUUs yourself, this will likely not help.
Urinal_Mint said:
I would be interested in giving this a try, is it as simple as extracting an older RUU & replacing rpm.img in p10 - or do i need to flash it via recovery?
Click to expand...
Click to collapse
Yes, it's as simple as extracting the image from a RUU and dd-ing it into P10. The attached zip does that. It is recovery flashable.
Do your capacitive buttons work when booted into recovery?
-Jobo
touch of jobo said:
Attached is a .zip that contains the rpm.img from the 1.78 RUU. (I flashed it on my own device before posting.)
But if you've already tried older RUUs yourself, this will likely not help.
Yes, it's as simple as extracting the image from a RUU and dd-ing it into P10. The attached zip does that. It is recovery flashable.
Do your capacitive buttons work when booted into recovery?
-Jobo
Click to expand...
Click to collapse
I never tried the buttons in recovery before, but now I did and they work in recovery. Thanks for making the zip. It did not change anything. I RUU back to RUU_Ville_U_Rogers_WWE_1.70.631.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254139_signed since ParanoidAndroid was a lot more buggy and I can use LMT to get the functionality of the buttons once they stop working.
I also tried upgrading the firmware to T-MOBILE 1.8.1 and the ROM from [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/ but that just made things worse, bootloops and such.
Thanks again
touch of jobo said:
Attached is a .zip that contains the rpm.img from the 1.78 RUU. (I flashed it on my own device before posting.)
But if you've already tried older RUUs yourself, this will likely not help.
Yes, it's as simple as extracting the image from a RUU and dd-ing it into P10. The attached zip does that. It is recovery flashable.
Do your capacitive buttons work when booted into recovery?
-Jobo
Click to expand...
Click to collapse
My buttons don't work in recovery either.
Thanks for the zip, but sadly it didn't have any effect for me.
If I want to go down the downgrade firmware route, with s-off do I just run the RUU or do I need to relock, default recovery, run RUU, unlock again?
Urinal_Mint said:
My buttons don't work in recovery either.
Thanks for the zip, but sadly it didn't have any effect for me either.
If I want to go down the downgrade firmware route, with s-off do I just run the RUU or do I need to relock, default recovery, run RUU, unlock again?
Click to expand...
Click to collapse
I just relocked the bootloader and then ran the RUU. Afterwards I would go back and unlock my bootloader and install TWRP 2.3.3.0 and SuperSU. I needed to root for LMT.
catdogdiamond said:
I just relocked the bootloader and then ran the RUU. Afterwards I would go back and unlock my bootloader and install TWRP 2.3.3.0 and SuperSU. I needed to root for LMT.
Click to expand...
Click to collapse
With s-off i changed my CID to HTC__001 and just ran the RUU, it booted ok - but I will need to reflash recovery!
Tried the 1.78.401.2 & 2.31.401.5 RUU's to no effect, so I'm guessing its more than that that have caused them to die!
Is there any other notable RUUs to try before I just use pie launcher and not worry about the buttons?
Urinal_Mint said:
Is there any other notable RUUs to try before I just use pie launcher and not worry about the buttons?
Click to expand...
Click to collapse
I don't know, but I think yours are truly dead. catdogdiamond has working buttons in recovery, so thats different. With the two RUUs you tried, I don't think another one will have a different result.
-Jobo
touch of jobo said:
I don't know, but I think yours are truly dead. catdogdiamond has working buttons in recovery, so thats different. With the two RUUs you tried, I don't think another one will have a different result.
-Jobo
Click to expand...
Click to collapse
No worries, thank you I appreciate the help so far.
I've got a new vibrate/ribbon cable on order & might be able to get my hands on an s with a smashed screen so I'll have some spare parts to play with. If not back on ebay it goes! No buttons I can handle but no vibrate either is a deal breaker.
Hopefully catdogdiamond can get life back out of the buttons
Also in the first post:
I've managed to partially solve the issue - I bought a replacement vibrate motor/mic/ribbon assembly off of amazon here now I don't know if it was me tearing down/rebuilding and reseating the cables (you have to go right to separating the screen from its housing to be able to get the motor out) but now I have the home and 'switcher?!' buttons working - just not the back button - but I can deal with that.
Seems it could be more a hardware issue than a software one in my case at least - it is on the same firmware/hboot before I replaced the motor to after and the buttons now work
Hopefully that might help someone else with this
Edit
Bugger - in the teardown/rebuild I managed to kill my signal, it can see my network but not register on it. Back into pieces it goes for another rebuild to see what I missed
I've Just bought a Macbook pro for my music production. I'm just getting started into the stuff I need for my phone and I have a few questions.
Firstly I like to flash back to stock with the RUU between custom roms but as they are .exe's. Is there a safe way round this?
I also transfer a lot of music back and forth but find android file transfer is unreliable and just loses connection all the time. Whats the best way for avoiding this or is it something I'll just have to put up with because android and apple just don't want to mix.
Finally are there any must have tools I will need before I start s-off and start flashing?
I know these might seem like noob questions but info on doing this on osx seems to be pretty sparse.
there was a little discussion. Doesn't look promising for running a RUU
http://forum.xda-developers.com/showthread.php?t=2412415
tivofool said:
there was a little discussion. Doesn't look promising for running a RUU
http://forum.xda-developers.com/showthread.php?t=2412415
Click to expand...
Click to collapse
Ive heard of something called openRUU but I don't thinks its for our device. I don't see any reason as to why something similar couldn't be used though
Here's a link to what I found.
http://www.mikesouthby.co.uk/2010/09/openruu-for-linux-and-mac-osx-users/
What options do I have for flashing back to stock?
FCW said:
What options do I have for flashing back to stock?
Click to expand...
Click to collapse
I do everything from a (2~3 year old) MacBook Pro. (Only use Windows in VM for extracting the rom.zip from RUUs.)
Personally I've never been in the situation where only a RUU would fix it. As long as you have fastboot and an unlocked bootloader, you're fine. I also recommend getting S-Off, so you can flash radio and wifi images.
If you ever want to get back to complete stock, maybe to sell the device, you can just wipe everything, then recovery-flash all images extracted from a RUU, including system, then fastboot-flash the stock recovery, re-lock, S-On.
-Jobo
touch of jobo said:
I do everything from a (2~3 year old) MacBook Pro. (Only use Windows in VM for extracting the rom.zip from RUUs.)
Personally I've never been in the situation where only a RUU would fix it. As long as you have fastboot and an unlocked bootloader, you're fine. I also recommend getting S-Off, so you can flash radio and wifi images.
If you ever want to get back to complete stock, maybe to sell the device, you can just wipe everything, then recovery-flash all images extracted from a RUU, including system, then fastboot-flash the stock recovery, re-lock, S-On.
-Jobo
Click to expand...
Click to collapse
how do you get s-off on a mac. It also turns out that the Ruu is corrupt from the dev section. Does anyone have a working one?
FCW said:
how do you get s-off on a mac.
Click to expand...
Click to collapse
I used facepalm. It only requires fastboot (for rebooting into RUU mode and flashing the zip) and adb for pushing and executing the binary that sets the flag.
-Jobo
Stuck...just displays the HTC logo on white screen.
I had cleanrom 5.0 final. TWRP, super SU, rooted, unlocked. Firmware 2.20.
I dropped in the new ROM, did a factory reset in TWRP, and installed new rom. I read that that would work with my current setup, but apparently not. I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
I flashed back to 5.0 with no issues, but I would really like to try to get the cleanrom 7 working if possible. Any ideas?
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
timmaaa said:
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your reply. You are correct, I am s-on. But I was able to re-load CleanROM 5. This is my second custom rom on this phone (the first being CleanROM 5). But this is only my third custom rom ever, so I am pretty much of a noober. :cyclops:
klaypigeon said:
I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
Click to expand...
Click to collapse
The ROM threads are to inform you of the features and requirements of the ROM, not to be a step-by-step guide. There are plenty of step-by-step guides in various places, for those that care to read and look.
If you don't flash often, a good resource is my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
My Index will at least point you to the s-off process. I intend to add some info about the 2.15 firmware (as people keep constantly asking about it), but work has been chaotic, to say the least.
Another good thing to do, is read through the more recent pages of the ROM thread, or do a search on the thread.
Thanks, I am subscribed to your index, that's where I found the ROM and what I used during my first flash.
I did the process for unlocking the 2.20 firmware about a year ago as that is what my phone came with. I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
'CID Getter' says I have no CID, which I read means I have superCID.
Firmware : 2.20
SuperSU installed and functioning (I have root)
Current ROM: CleanROM 5 Final
S-ON
TWRP 2.3.1.0
So you think I need to do s-off as described here? http://forum.xda-developers.com/showthread.php?t=2155071
If I brick this phone I am using a clam-shell for a year until contract renewal :/
klaypigeon said:
I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
Click to expand...
Click to collapse
You shouldn't be assuming anything. You just said the CID Getter says S-on. You can also confirm s-on or s-off by going into bootloader.
The main reason CleanROM7 will not boot, is that you forgot to extract boot.img from the ROM file, and flash it separately using fastboot. Some older versions of CleanROM didn't require this (boot.img was flashed in the AROMA installer), so that may be why you don't remember doing this.
S-off removed the requirement to flash boot.img separately (will flash in recovery automatically when you flash the ROM). It will also allow you to install hboot 2.15 and associated firmware, if you happen to suffer from signal drops or random reboots while on Sense 5 ROMs.
Further to that, CID Getter doesn't show your actual CID. The proper way to display your CID is by using the fastboot command "fastboot oem readcid". Like Redpoint said, you shouldn't be assuming anything.
Sent from my Evita
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
What did you flash?
Sent from my Evita
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
timmaaa said:
Further to that, CID Getter doesn't show your actual CID.
Click to expand...
Click to collapse
Ha, that's not a very useful app, then. What is it actually reading?
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
klaypigeon said:
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
Click to expand...
Click to collapse
Do you mean "locked the bootloader" instead of "flashed"?
If you locked the bootloader, this is what is supposed to happen. Locking the bootloader assumes you will be running RUU, and renders the phone unable to boot normally.
I know you got it back up and running. But for future reference, this phone is almost never bricked, as long as the screen comes on.
---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------
klaypigeon said:
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
Click to expand...
Click to collapse
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
I'm not sure what CID Getter is actually reading, but when I used it it came up with the incorrect CID, can't remember exactly what it was now but it was definitely incorrect because I already had SuperCID.
Sent from my Evita
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
Click to expand...
Click to collapse
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
If you have s-off you don't need to flash the boot.img via fastboot, that's only required if you're s-on. It might be worthwhile updating your TWRP to the 2.6 version though.
What Redpoint was saying is that you need to have a firm understanding of what you're doing when it comes to modifying your phone. If you only do it once a year that's cool, but that probably means that once a year you need to brush up before making any changes to your device. Rushing in without the required knowledge is how bricks occur. This is only being suggested to help you, for your own good.
Sent from my Evita
klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do.
Click to expand...
Click to collapse
Only with hboot 1.14 or later and s-on. If s-off the protection which prevents boot.img from being written in recovery is bypassed.
I believe TWRP 2.3.1 was a pretty trustworthy version (although older). So not sure why CleanROM didn't flash. Might not be a bad idea to update to 2.6.0 (although the latest 2.6.4 seems to have some bugs).
klaypigeon said:
I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
Yeah, I understand that you only do this on a seldom basis. And its a lot of esoteric knowledge to have to relearn (or take in, since things have likely changed since lasts time). However, that doesn't change the fact that not fully understanding all the concepts and steps can have dire consequences for your phone.