Situation changed.
Anyhow, I've unlocked my Bootloader but every time I try to flash anything whatsoever, the phone just crashes. Boot, recovery, etc. Looking for some insight from those with more experience.
fastboot devices DOES return my device.
Other commands (getvar) do work
fastboot boot does not work
fastboot flash does not work
these are the commands that work with fastboot...
http://android-dls.com/wiki/index.php?title=Fastboot#Fastboot_Commands
How does it crash? What file(s) are you trying to flash?
If you are willing to flash the AT&T leaked rom, you can just put the su binary in there before flashing.
I know how fastboot works. That being said, I've tried flashing a custom boot.img, stock boot.img, custom recovery, and stock recovery. None of them work. It says "sending file 'boot.img' (****kb)..." or similar, and hangs there until I disconnect the device. The device locks up as soon as a fastboot flash or fastboot boot command is run.
As far as flashing the ATT rom, I'm concerned with it a) working on my device and b) taking away my 3g/4g toggles. Seeing as we have no Rogers RUU yet, it's a legitimate concern.
i don't know mate. wish i could help you. without a device in hand it's harder for me to troubleshoot.
Only thing I can think of is that it's a Rogers ROM issue. I want to flash the ATT RUU, but I have no way to revert if it doesn't work, and that scares the piss out of me, to be blunt. Lol
RMatt1992 said:
Only thing I can think of is that it's a Rogers ROM issue. I want to flash the ATT RUU, but I have no way to revert if it doesn't work, and that scares the piss out of me, to be blunt. Lol
Click to expand...
Click to collapse
If you can live without the toggles for a while (until Rogers RUU), then it wouldn't be so bad. If this is your only device, don't gamble!
Pretty much how it's gonna be. When a Rogers RUU comes out, I'll be all over that like a dirty shirt and maybe I can get this thing rooted, just maybe. Until then, I'm not going to take the chance!
I am gonna wait until this forum gets cooking
You're going to have to wait at least till the 6th of may or a few days after. No one here in canada knows how to root i guess
Which operating system are you running? It's probably something silly that's being overlooked. I've had a ton of issues like that. But right now I'm running Ubuntu and I just have to do "sudo fastboot xxx" and it works just fine.
I was one of the few that accidentally try flashing HTC One X ROMs for the Tegra 3 chip, but I got everything working on my Rogers HTC One XL. I'm not in an LTE enabled area but I'm getting 10+mbps for my download and almost 5mbps for the upload so I don't know if that answers the LTE question or not. At least 3G is working solid as hell though.
Glad to hear you're up and running again ...
bongd said:
Which operating system are you running? It's probably something silly that's being overlooked. I've had a ton of issues like that. But right now I'm running Ubuntu and I just have to do "sudo fastboot xxx" and it works just fine.
I was one of the few that accidentally try flashing HTC One X ROMs for the Tegra 3 chip, but I got everything working on my Rogers HTC One XL. I'm not in an LTE enabled area but I'm getting 10+mbps for my download and almost 5mbps for the upload so I don't know if that answers the LTE question or not. At least 3G is working solid as hell though.
Click to expand...
Click to collapse
Hey, I hadn't come across any of your posts for a few days. I'm happy to hear that you've got your Rogers unit up and running again.
I'm patiently waiting for someone to find a way to root the Rogers unit. I'm sure it will happen soon enough, but waiting isn't my strong point.
Peter
bongd said:
Which operating system are you running? It's probably something silly that's being overlooked. I've had a ton of issues like that. But right now I'm running Ubuntu and I just have to do "sudo fastboot xxx" and it works just fine.
I was one of the few that accidentally try flashing HTC One X ROMs for the Tegra 3 chip, but I got everything working on my Rogers HTC One XL. I'm not in an LTE enabled area but I'm getting 10+mbps for my download and almost 5mbps for the upload so I don't know if that answers the LTE question or not. At least 3G is working solid as hell though.
Click to expand...
Click to collapse
Did you flash the ATT RUU? And, I'm running Ubuntu 12.04 64bit but I run sudo -s. I'll try sudo normally anyhow to see if the outcome changes.
Edit: ^ no difference. Is it possible that my bootloader didn't properly unlock the first time, and that I should relock and unlock it? Just an idea...
RMatt1992 said:
Did you flash the ATT RUU? And, I'm running Ubuntu 12.04 64bit but I run sudo -s. I'll try sudo normally anyhow to see if the outcome changes.
Edit: ^ no difference. Is it possible that my bootloader didn't properly unlock the first time, and that I should relock and unlock it? Just an idea...
Click to expand...
Click to collapse
Strange how it didn't work. I'd try a lock and re-lock just to be on the safe side. I don't understand why it's not working.
anyone simply try renaming the rom.zip from the at&t evita 1.6x ruu to PJ83IMG.zip, stuffing it on the internal storage, and booting to bootloader? I haven't tried it yet, but I bought my phone outright for $704, tax in, and dont want to risk it without a rogers evita ruu in my hands. It wouldnt get you rooted, but it would get you running a test keys build at least with exploitable holes (thats if it'll allow you to downgrade).
JSLEnterprises said:
anyone simply try renaming the rom.zip from the at&t evita 1.6x ruu to PJ83IMG.zip, stuffing it on the internal storage, and booting to bootloader? I haven't tried it yet, but I bought my phone outright for $704, tax in, and dont want to risk it without a rogers evita ruu in my hands. It wouldnt get you rooted, but it would get you running a test keys build at least with exploitable holes (thats if it'll allow you to downgrade).
Click to expand...
Click to collapse
I actually think I saw some devs complaining about HTC's unlocking process for the bootloader. I think with newer devices you can't flash p*img.zips from HBOOT and things of that sort.
Also, they're being real wankers and not releasing the source for their kernels either. I thought their bootloader unlocking was a real win for the community but it looks like they've taken steps backwards in other areas.
bongd said:
I actually think I saw some devs complaining about HTC's unlocking process for the bootloader. I think with newer devices you can't flash p*img.zips from HBOOT and things of that sort.
Also, they're being real wankers and not releasing the source for their kernels either. I thought their bootloader unlocking was a real win for the community but it looks like they've taken steps backwards in other areas.
Click to expand...
Click to collapse
I noticed that as well... also, the file sizes of the new bootloader, and recovery images.... jesus... comparing them to the size of th DHD's (the device I came from) they're almost triple the size. I love how they continue to complicate what doesn't need to be complicated.
At this point the only thing holding me back is knowing I don't have a way to get back to stock if I screw up, and I have no other handset. I'm tempted to try the rom.zip thing, but again, if something goes wrong I'll cry. If bongd (or anyone else) can tell me that they've successfully flashed the ATT RUU onto their Rogers device I will then go ahead and try to get us rooted, however until then, I can't stand to temp-brick my device and be unrecoverable.
I don't know if I read it here or over on Rootz, but someone was saying they went and bricked their Rogers HOX and the ATT RUU actually worked
Sent from my HTC One X using xda premium
SN4K3B1T3 said:
I don't know if I read it here or over on Rootz, but someone was saying they went and bricked their Rogers HOX and the ATT RUU actually worked
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
The only thing that I'm skeptical about (regarding that) would be the inability to 'downgrade' (lower bootloader version in the at&t 1.68 RUU), and different CID's (because of the carriers). That's why i'd love to see some confirmation from those people who semi-bricked their devices when flashing stuff ment for the Endeavour(PJ43).
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.
I've been running CM9 for a few weeks now, but have decided that I want to get S-Off and open the phone's capability up some more... Anyway, I'm on a MT4GS:
HBOOT 1.45.0013
Nov 21 2011 build
Tried flashing this https://www.cx.com/mycx/share/O2W61....00_11.16.3504.20_2_release_245247_signed.zip
from weekendsr2short's mirror page (http://forum.xda-developers.com/showthread.php?t=1878329) of Blue6ix's stuff...(i tried autoflashing from the bootload/fastboot screen)
anyway, it loads up like it is going to actaully flash, but nothing changes on the Bootloader screen. The phone is unlocked via HTC's tool and is rooted. Any help is greatly appreciated! Please lemme know if any more info is needed.
Josh
more to it than flashing an hboot
read up on THIS
SurfRodder said:
I've been running CM9 for a few weeks now, but have decided that I want to get S-Off and open the phone's capability up some more... Anyway, I'm on a MT4GS:
HBOOT 1.45.0013
Nov 21 2011 build
Tried flashing this https://www.cx.com/mycx/share/O2W61....00_11.16.3504.20_2_release_245247_signed.zip
from weekendsr2short's mirror page (http://forum.xda-developers.com/showthread.php?t=1878329) of Blue6ix's stuff...(i tried autoflashing from the bootload/fastboot screen)
anyway, it loads up like it is going to actaully flash, but nothing changes on the Bootloader screen. The phone is unlocked via HTC's tool and is rooted. Any help is greatly appreciated! Please lemme know if any more info is needed.
Josh
Click to expand...
Click to collapse
If you're rooted, install a stock-based ROM and then use juopunutbear.
blackknightavalon said:
If you're rooted, install a stock-based ROM and then use juopunutbear.
Click to expand...
Click to collapse
OK, that's what I was hoping to do. I noticed in the JB instructions that it said I must be a stock RUU not a custom ROM or something to that effect. I am on CWM 5.Something so a rom flash is NP. Any recommended ROMs? I.e One that worked for you? I tried the wire trick about 100 times over the course of an hour or so(on cm9.1), but then reread the bit shout the rom again.
Thanks for all the responses so far!
Any stock based ROM will do. I went with MikTouch myself and it worked like a charm! (on the 4th try so be patient....)
demkantor said:
more to it than flashing an hboot
read up on THIS
Click to expand...
Click to collapse
Thanks, after reading that thread <again> it linked me the this http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
Which I have Also already read,but noticed this time that I cannot be unlocked via HTC and still flash pg59imgs... so im off to relock, if the stock rom method doesn't work...
WeekendsR2Short said:
Any stock based ROM will do. I went with MikTouch myself and it worked like a charm! (on the 4th try so be patient....)
Click to expand...
Click to collapse
Awesome, thanks brotha
well, one down, one to go. I have my phone all dialed in...now its time to fix my wife's... Thanks again Gents! (& Ladies, as applicable!)
edit: well, hers is done now... I ended up using another SD card, the original one I tried was kinda old, but the newer one I normally use worked on the 2nd try... didnt lose any data either... her sd card on the other hand was toasted and needed to be reformated... anyway, both phones are now S-Off!!
SurfRodder said:
well, one down, one to go. I have my phone all dialed in...now its time to fix my wife's... Thanks again Gents! (& Ladies, as applicable!)
edit: well, hers is done now... I ended up using another SD card, the original one I tried was kinda old, but the newer one I normally use worked on the 2nd try... didnt lose any data either... her sd card on the other hand was toasted and needed to be reformated... anyway, both phones are now S-Off!!
Click to expand...
Click to collapse
Man, that's GREAT! Once you knew HOW, the process was nothing for you. That's a far cry from most. Way to go!
WeekendsR2Short said:
Man, that's GREAT! Once you knew HOW, the process was nothing for you. That's a far cry from most. Way to go!
Click to expand...
Click to collapse
yeah, Ive been running root since my MT3G way back when...couldnt stand how laggy that thing was with all the bloat... wasnt even that great with CM6 but still night and day better than stock (=hooked on rooting). then upgraded to the MT4g and now this thing... was fairly concerned about all the extra hoops but wouldve just chosen another platform had I borked it...glad I didnt, saved me some funds!
On a related note, what radios are you guys running? Are there any issues between the GB radios and ICS ones? Im assuming so, but with the custom ROMs/kernels anything should be able to be overcome I'm hoping... I know I def. had issues on CM7 -> CM9 on the reg. 4G when swapping radios...
I don't generally swap my radios around since there are only two that I'm aware of. But I DID find that the new one (when I replaced my phone) seemed to lock a signal a bit quicker but for me the original radio gets MUCH better phone reception. Depends on your phone I suppose.
(you'll be glad you went with this phone though. basically a Sensation with a keyboard)
WeekendsR2Short said:
I don't generally swap my radios around since there are only two that I'm aware of. But I DID find that the new one (when I replaced my phone) seemed to lock a signal a bit quicker but for me the original radio gets MUCH better phone reception. Depends on your phone I suppose.
(you'll be glad you went with this phone though. basically a Sensation with a keyboard)
Click to expand...
Click to collapse
cool, I just flashed the older one today... been having really crappy recption on campus lately (esp. since switching from the MT4G) better reception is what I'd rather have... ill give this one a week or so and see if I think its any better... I like the phone a lot already... i still use the soft keyboard from time to time as I forget the other one is there, but it comes in really handy on certain sites...
Hello guys, I've been lurking the forums for hours trying to find a thread with an issue close to mine, and this is the closest I got. I followed all the necessary steps on the first page, but the problem I'm having is when I try to flash the PG59IMG.zip file, it says "Loading... PG59IMG.zip", but then it says "Checking....PG59IMG.zip" and afterwards it says "Wrong zipped image!" Any ideas what it could mean? I just want to get it back to stock. Any help is greatly appreciated.
THIS MAY HELP YOU
Thanks for the link. It said I need to relock the phone in order to flash the image, but when i type "fastboot oem lock" into command prompt, I get a message saying 'fastboot' is not recognized as an internal or external command, inoperable program or batch file." I'm guessing this means my fastboot wasn't set up correctly, but I don't know where to go from here. As always, thanks again for any help or advice.
The third post in this thread
http://forum.xda-developers.com/showthread.php?p=27796375
It was made for the g2 so don't use the drivers in it, but it will at least give you an idea of what to do
Sent from my HTC Vision using xda premium
Hanenbow said:
Thanks for the link. It said I need to relock the phone in order to flash the image, but when i type "fastboot oem lock" into command prompt, I get a message saying 'fastboot' is not recognized as an internal or external command, inoperable program or batch file." I'm guessing this means my fastboot wasn't set up correctly, but I don't know where to go from here. As always, thanks again for any help or advice.
Click to expand...
Click to collapse
Does fastboot work like this
./fastboot oem lock
On my PC some of my fastboot commands need that.
Sent from my Freaked out JellyBean
Thanks so much for your help guys. I followed the instructions on the pathing link, and the phone is currently flashing the image. I'll post a final time once I can confirm everything is fine.
Hi all,
I have an AT&T One X. The bootloader is unlocked but is S-ON. I want to return this phone to as close as stock as possible. This phone is destined to go to another user who knows nothing of rooting and such so I don't care if it is rooted or not.
I understand I have to relock the bootloader to be able to flash an RUU right? Hboot is currently at 1.14.002, Radio is at 0.19as.32.09.11_2. TWRP 2.3.1.0 is installed.
The phone is currently running Cleanrom 6.5 and all works fine. I just want this back to as close to AT&T stock as possible so that the user I am giving the phone to will not have any problems.
If I relock the bootloader can I return this to stock via the most recent AT&T 3.18 RUU located here: http://forum.xda-developers.com/showthread.php?t=2191477 or is there something else I need to do first?
Thanks for all your help.
Tersanyus said:
Hi all,
I have an AT&T One X. The bootloader is unlocked but is S-ON. I want to return this phone to as close as stock as possible. This phone is destined to go to another user who knows nothing of rooting and such so I don't care if it is rooted or not.
I understand I have to relock the bootloader to be able to flash an RUU right? Hboot is currently at 1.14.002, Radio is at 0.19as.32.09.11_2. TWRP 2.3.1.0 is installed.
The phone is currently running Cleanrom 6.5 and all works fine. I just want this back to as close to AT&T stock as possible so that the user I am giving the phone to will not have any problems.
If I relock the bootloader can I return this to stock via the most recent AT&T 3.18 RUU located here: http://forum.xda-developers.com/showthread.php?t=2191477 or is there something else I need to do first?
Thanks for all your help.
Click to expand...
Click to collapse
You'll need to S-OFF first or you'll brick.
There's a howto on the original android development section.
exad said:
You'll need to S-OFF first or you'll brick.
There's a howto on the original android development section.
Click to expand...
Click to collapse
Just flash a stock rooted Rom. Most users won't even know it's rooted. And having a custom recovery (even if they don't know they have it) can help if there is ever an issue. S-off so in the future if there's a update it won't brick the phone.
Sent from my HTC One X using xda premium
31ken31 said:
Just flash a stock rooted Rom. Most users won't even know it's rooted. And having a custom recovery (even if they don't know they have it) can help if there is ever an issue. S-off so in the future if there's a update it won't brick the phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I agree, except for leaving it rooted. I would leave just the bootloader unlocked and S-OFF and RUU, this way the buyer doesn't get shocked or confused if an app asks for root access, but has the option to do whatever they want to their phone if they so decide.
exad said:
I agree, except for leaving it rooted. I would leave just the bootloader unlocked and S-OFF and RUU, this way the buyer doesn't get shocked or confused if an app asks for root access, but has the option to do whatever they want to their phone if they so decide.
Click to expand...
Click to collapse
I forgot about su access prompt. That could be a shocker lol
Sent from my HTC One X using xda premium
exad said:
I would leave just the bootloader unlocked and S-OFF and RUU.
Click to expand...
Click to collapse
I agree. Couple reasons (both related to RUU). If the new user for some reason needs to recover the phone, and runs the RUU (not unheard of, HTC support will sometimes direct customers to do this), that person will either:
1) Brick the phone, if its left as SuperCID and S-on
2) If S-on (but CID is changed back), and bootloader is left unlocked, the RUU won't run. The person will have no idea why, and will likely be stuck.
S-off solves both of these potential issues. If you are at all worried about the next user. I would S-off, then run the RUU to return the phone to stock. The only thing that would be "not stock" is unlocked bootloader and S-off. But neither of these will mean anything or affect a less experienced user.
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
iElvis said:
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
Click to expand...
Click to collapse
Fair point. Switching the phone back to the AT&T CID and locking the bootloader might be the best alternative. Then run the RUU to get it back on stock recovery and ROM.
Giving/selling the phone to an unsuspecting noob with SuperCID and S-on just seems like a bad idea. Worse than S-off.
iElvis said:
I'm going to disagree with the above.
If this person knows nothing of rooting and doesn't care, you should give them a stock phone. Being s-off is a potential security risk that should only be taken by someone who a) knows about it, and b) knows what it means. If you're selling this phone, it's arguably deceptive to give them something with a lurking vulnerability.
Click to expand...
Click to collapse
I've seen bricks after RUUing, even after changing the CID back to default.. It's a toss up I guess. Typically, when I sell my phone or hacked device, I just sell it as being hacked this way people know what they are getting into. Advertising as such has never hindered my ability to sell it either.
redpoint73 said:
Fair point. Switching the phone back to the AT&T CID and locking the bootloader might be the best alternative. Then run the RUU to get it back on stock recovery and ROM.
Giving/selling the phone to an unsuspecting noob with SuperCID and S-on just seems like a bad idea. Worse than S-off.
Click to expand...
Click to collapse
I didn't mean leaving it supercid--that is obviously a risk.
exad said:
I've seen bricks after RUUing, even after changing the CID back to default.. It's a toss up I guess. Typically, when I sell my phone or hacked device, I just sell it as being hacked this way people know what they are getting into. Advertising as such has never hindered my ability to sell it either.
Click to expand...
Click to collapse
That's kind of my point. Selling it rooted is fine, just represent it for what it is. You shouldn't give a modified phone to someone who doesn't know what that even means.
The phone is going to a friend who has a Pantech Burst currently. As someone mentioned I didn't want them to get a SuperSU prompt for root access and have no idea what that means. I tried a stock rooted rom but it kept rebooting. I did factory reset/data wipe and reloaded the rom twice but still kept doing it. I thought it odd too. Cleamrom is acting just fine though.
After hard bricking a Droid DNA which I don't know if it was due to being unlocked and such I'm starting to feel rooting and custom roms isn't for me anymore. The Droid DNA was replaced and the replacement was never unlocked (and since it has most recent software it couldn't be unlocked. Don't get me wrong, I love not running stock devices. It's such a great feeling to get rid of all that carrier added bloat that I most liked.
I've actually moved on from the DNA as well. I'm on a One now from AT&T as my primary phone. And I so hate all that AT&T bloat in there. It's all disabled but still seeing it there just sends chills down my spine.
So now I am not so sure what to do about the One X now. My original thought was RUU back to factory and relock the bootloader and keep S-ON. That way if someone did look they'd only see "RELOCKED".
Makes me miss the easy days when I used a Captivate and Note 1. Those were so easy to use custom roms on.
iElvis said:
I didn't mean leaving it supercid--that is obviously a risk.
Click to expand...
Click to collapse
Your previous post didn't explicitly say anything about that, one way or another. So I was just clarifying for the benefit of the OP. I knew what you meant, but wanted to make sure the OP did, too!
Ok, I have never been more tempted to throw a phone in all my life. This has me VERY irritated.
I got this htc one x on a hunch, was a good deal, seen great roms on here, thought it was a good idea. I've had nothing but trouble. Heres my deal:
I went to the htcdev site to get the boot loader unlocked. Im no dummy, I've gotten into LOTS of phones. This thing is crazy. I've watched 20 videos, used 3 different computers, NOTHING works. ALWAYS says Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Now this isn't my first rodeo, I read, searched, paused videos made sure I was getting the same info selected, spaces, EVERYTHING that were showing between my screen and the youtube screens. This phone has taken the latest att update. Is this the problem? Has getting into the phone been cut out? Is there another way to get in and load roms? Should I ditch it for a galaxy?
You have supercid, right? The One XL can't have bootloader unlock without it. AT&T Doesn't like for people to use phones the way they're intended to be used
There is a new method for unlocking on the latest update over in general.
Sent from my HTC One XL using xda premium
I've never owned a phone so hard to deal with... Everything I read says I need to be rooted, I need to have bootloader unlocked to root, different direction loops I cant seem to break... The noobproof all require bootloader unlocked... there is SO much info, it all points in different directions, and I cant make heads or tails out of it to be honest. I've been reading for 2 days and am about to pitch this thing as far as I can.
I cant find the directions for supercid, just what it does. I normally don't require hand holding... I have an upgrade coming in September.....
Part of my issues is I don't have a charge only mode...
what carrier did the phone come from and what software version are you on?
klloyd said:
Part of my issues is I don't have a charge only mode...
Click to expand...
Click to collapse
Newest update doesn't have this option. There's a root method in dev section, however you need linux to run the script. But that's easy to make a bootable CD just to run the script. After you root then dev unlock. Then you can proceed to either fastboot a recovery or use goo manager to install the latest. Then flash away...
I recommend you follow the S-off thread too... That way you don't need fastboot to flash boot.img. then if it came with 3.18 firmware, you'll also need to follow the touchscreen downgrade thread if you plan on using Aosp roms.
It's really not hard to do the last 2 steps, but I have to agree you need to go through an a$$load of steps to get the desired effect. But this phone is great with custom roms. Some call me crazy, but if I run carbon Rom tweaked it'll rival my buddies S4 no problem
Sent from my HTC One XL using Tapatalk 2
Its a true blue att phone. Running 4.1.1, software 3.18.
I actually run Linux on about everything... I am using my wifes computer to do all this, cause it seemed windows was easier. (insert shame here)
Im just use to the one clicks, the easy additions of clockwork in a single flash on the galaxy phones. Im not giving up, but believe you me, there is an note2 or and s4 in my future.
klloyd said:
Its a true blue att phone. Running 4.1.1, software 3.18.
I actually run Linux on about everything... I am using my wifes computer to do all this, cause it seemed windows was easier. (insert shame here)
Im just use to the one clicks, the easy additions of clockwork in a single flash on the galaxy phones. Im not giving up, but believe you me, there is an note2 or and s4 in my future.
Click to expand...
Click to collapse
*Gags a little* lol. Good luck man
Sent from my HTC One XL using Tapatalk 2
The reason info conflicts is AT&T phones cant use htcdev unlock by AT&T request.
All other evita's can use htcdev fine.
So AT&T phones need root to change cid to pretend to not be an AT&T phone before they can unlock.
Sent from my HTC One XL using xda app-developers app
As normal, wonderful help! Im on the right track this time! Thanks!
klloyd said:
Its a true blue att phone. Running 4.1.1, software 3.18.
Click to expand...
Click to collapse
If that's the case, you need to go here:
http://forum.xda-developers.com/showthread.php?t=2283760
That will change you Cid so it no longer identifies your phone as an AT&T model. Then, and only then will you be able to use htcdev to unlock your phone.
Sent from my HTC One X using xda app-developers app
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Sent from my Evita
timmaaa said:
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Click to expand...
Click to collapse
Thanks for the reply. I believe the reason I'm not bricked is because I backed out of the installation of Maximus HD during the setup screen progression. The actual ROM was never flashed. However, I have flashed the boot.img and ROMs for Viper, Xylon, and Cyanogenmod with no success. The result is the same every time (HTC screen, then black). I extract the boot.img from each of the roms, flash it, and then flash the ROM. The ROM I flash is a copy of the the original with the boot.img still inside. Perhaps I should be removing the boot.img if I am going to flash it separately in fastboot? And I realize that the threads are specific for certain phones now. It's all kind of a mess to get into at first.
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Madcat8686 said:
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
Click to expand...
Click to collapse
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Oh, that's great. Usually it shouldn't matter which order you flash in, but at least it got you out of trouble this time.
Sent from my Evita
roycedavies said:
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Click to expand...
Click to collapse
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
Hey, you should take the credit, I believe flashing it afterwards was what got his phone booted :thumbup:
Sent from my Evita
Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
timmaaa said:
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply! I will get the bootloader info ASAP bit don't I need to be s-of in order to RUU? from what I've read, if you don't have unlocked bootloader, root access, and s-off, you'll end up bricking your phone with RUU. I'd really like to do it but I have tried to get s-off to no avail.
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
roycedavies said:
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
Click to expand...
Click to collapse
Definitely not normal. A few recommendations:
1. Back up all your stuff, wipe everything except the SD card, Flash a fresh copy of the Rom, Flash the boot.img (you really should consider S-Off), Wipe the cache and DALVIK cache one more time, boot up the system.
2. Same as above except choose another Rom. There are plenty to choose from. The 4.4 Roms are getting a lot better now that the new Kernel fix got rid of the boot loops/reboots.
Sorry about the delay, it's been a heavy week at work. Hope things work out for you.
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
Sometimes is pays to see if there is a page 2 to the thread...Sorry about that! lol
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
timmaaa said:
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have no idea how much I have vicariously learned from your posts. Thanks Timmaa! I keep thinking if more of these folks would go ahead and get S-Off they would have waaaaaaaaaay less issues.
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I totally agree now because after rereading the post, there is a radio issue in addition to the boot issue. Is it possible that the Endeverou boot.img messed something up?
Yeah, that's exactly what I'm thinking. An RUU will hopefully fix that right up.
Sent from my Evita.
timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
That sounds like a good plan. (I'm really appreciating all your input by the way! Thanks so much!) One question though, upon checking out the rumrunner website, there isn't specific mention of the HTC One X Evita. Call me paranoid, but after what I've been through I want to make 100% sure I'm compatible before moving forward. Have you or anyone used this specific method for S-Off on the One X Evita?
For the Evita you use the universal HTC method. I've created a thread for it if you want to make sure it's worked for other Evita owners.
http://forum.xda-developers.com/showthread.php?t=2540232
Sent from my Evita.