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.
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 am creating this post as a tip and warning to everyone with an at&t htc one x (mostly noobs for help). If you have rom manager on your phone do not use it to flash the new recovery listed for the htc one x (gsm). I've been messing with android since 2009, but me seeing a new recovery for the one x with (gsm) next to it thought hey finally got an official clockwork recovery for our phones!!!!! Well i was wrong. Its for the international versions only not ours. The partition it writes the recovery to is on our bootloader partition, and flashing it will kill your phone. I flashed it, kept it on for hours but as soon as i rebooted the phone it turned off and would not turn on or charge. You'll pretty much be screwed and have to get a new phone unless you know how to run linux and ask for help fixing it which is harder than you think. Again do not flash the htc one x (gsm) recovery in rom manager!!!!!
Hope this helps some of you before hand and not after.
If this post isn't necessary i am sorry and please close it.
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
nooomoto said:
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
rob219 said:
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
Click to expand...
Click to collapse
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
sugeraddict said:
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
Click to expand...
Click to collapse
The ruu has to access the boot loader to verify your version. If you end up flashing a device and it writes certain partitions of your boot loader (ICJ).... Well your left with a permabrick, until someone finds a way to JTAG the One X(AT&T). I've heard that its already been done, but the person who has performed it has kept the pinout secret.
I'm not entirely sure which partitions your ROM manager has wrote to, if you can find that out you might be able to fix it... Depending on which ones have been written too.
Sent from my One X using xda app-developers app
Zombie thread alert!
Like many of us have said before. We are not the one x. We are the one XL.
Sent from my One X using xda app-developers app
_MetalHead_ said:
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Click to expand...
Click to collapse
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
MaverickCoast said:
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
Click to expand...
Click to collapse
You must be doing something wrong then. You don't even need to locate backups with TWRP, they're found automatically. Anyway, was it really necessary to revive an 18 month old thread just to say that?
Sent from my Evita
I'm sure I haven't bricked this phone, because in the process of rooting it, it will eventually say it's S-OFF. But after getting to that point, I can choose Recovery in CWM and when it gets to the white screen with the green HTC logo, after about 4 seconds, it will fade to black. This has happened to 2 phones I've rooted. Luckily mine worked like a charm, but after the last 2...I'm afraid to root another one. Does this sound like a bad memory card, or maybe it's not a gold card? I've searched around and couldn't find an answer, so maybe someone here at XDA has experienced this problem and has an answer.
TIA
t4duzan said:
I'm sure I haven't bricked this phone, because in the process of rooting it, it will eventually say it's S-OFF. But after getting to that point, I can choose Recovery in CWM and when it gets to the white screen with the green HTC logo, after about 4 seconds, it will fade to black. This has happened to 2 phones I've rooted. Luckily mine worked like a charm, but after the last 2...I'm afraid to root another one. Does this sound like a bad memory card, or maybe it's not a gold card? I've searched around and couldn't find an answer, so maybe someone here at XDA has experienced this problem and has an answer.
TIA
Click to expand...
Click to collapse
I quite don't get that....you can choose recovery in CWM?? what does that is supposed to mean? CWM is a custom recovery. I guess that you are probably refering to hboot. Anyway, if you are S-OFF, then you might not have a recovery installed, so flash a new one (use the guide in my signature or look for post # 7 in the Ace Think Tank in the general section of the Desire HD forum)
Make sure first that you are S-OFF for certain, if you are not, then you won't be able to flash anything at all. Then, try re running the Hack Kit again from the white splash screen as the manual tells you to.
glevitan said:
I quite don't get that....you can choose recovery in CWM?? what does that is supposed to mean? CWM is a custom recovery. I guess that you are probably refering to hboot. Anyway, if you are S-OFF, then you might not have a recovery installed, so flash a new one (use the guide in my signature or look for post # 7 in the Ace Think Tank in the general section of the Desire HD forum)
Make sure first that you are S-OFF for certain, if you are not, then you won't be able to flash anything at all. Then, try re running the Hack Kit again from the white splash screen as the manual tells you to.
Click to expand...
Click to collapse
Yes, I guess I did mean hboot. In the process of Recovery is when it will fail and there is a ROM loaded for it to recover from on the SD card. Is it possibly because it is looking for the clockworkmod/backup folder and there is not one? I just realized that maybe I can copy a backup from my phone (we have the same exact phone) and place in there if it's possible. I don't have access to the phone now, as it is a friends. Also, if it fades out at the white HTC logo and just gets hung up, there is no way to re-run the Hack Kit is there?
Thanks for the help glevitan, as you've helped me before and I HAVE downloaded your Ultimate Hack Guide and keep it on my phone for reference.
t4duzan said:
Yes, I guess I did mean hboot. In the process of Recovery is when it will fail and there is a ROM loaded for it to recover from on the SD card. Is it possibly because it is looking for the clockworkmod/backup folder and there is not one? I just realized that maybe I can copy a backup from my phone (we have the same exact phone) and place in there if it's possible. I don't have access to the phone now, as it is a friends. Also, if it fades out at the white HTC logo and just gets hung up, there is no way to re-run the Hack Kit is there?
Thanks for the help glevitan, as you've helped me before and I HAVE downloaded your Ultimate Hack Guide and keep it on my phone for reference.
Click to expand...
Click to collapse
Just a question, are you sure that the phone is S-OFF? or has an unlocked bootlaoder? In either way you can flash recovery again from fastboot and then a custom rom again.
If you need help, I can lend you a hand via teamviewer..just let me know. :good:
glevitan said:
Just a question, are you sure that the phone is S-OFF? or has an unlocked bootlaoder? In either way you can flash recovery again from fastboot and then a custom rom again.
If you need help, I can lend you a hand via teamviewer..just let me know. :good:
Click to expand...
Click to collapse
I'm going by after work to pick up the phone and will work on it this weekend. Thanks for the offer of help too. I'll post back with how this turns out.
t4duzan said:
I'm going by after work to pick up the phone and will work on it this weekend. Thanks for the offer of help too. I'll post back with how this turns out.
Click to expand...
Click to collapse
ok. Good luck!
Ok glevitan, I believe the problem might be in the PD98IMG.zip that's on the root of my SD card. I noticed when the phone booted into hboot, it would display that the image file was wrong, or something to that effect and then would force an update, which would load the HTC spashscreen and then ultimately fade out. I figured it had a bad PD98IMG.zip file, so I found the original aahk-13012012.zip and extracted the PD98IMG.zip from there and overwrote the one in the root. It didn't work. A different story...I noticed on my Inspire 4G (working correctly, but hboot had same error, even though I could load recovery from there) that it wasn't finding the correct image either. I copied over the PD98IMG.zip onto my phone and now both phones are now fading out on the HTC splashscreen after about 4 seconds. This tells me that it's in the SD card, right? If so, any suggestions? Both phones were rooted using this version of aahk.
Edit: Also, with this new PD98IMG.zip image, hboot will go into the process of parsing for
[1] boot
[2] recovery
[3] radio_v2
Once this is done, I push Power to reboot and that's when I get the failure in the HTC splashscreen.
Edit: I noticed in the PD98IMG.zip there was no md5 file, so I stuck one in there and got my phone working (which is not the one with the original issue started in this thread) and was able to restore a nandroid backup. I put this same SD card in the original damaged phone and it didn't restore like mine did. I still think it's an SD card issue causing the HTC splashscreen fadeout, but don't know where to go know.
Also, my PD98IMG.zip only has a recovery.img and a recovery.md5 file in it. I noticed that the original aahk PD98IMG.zip has those along with a boot.img and a radio.img. Should those be in the PD98IMG.zip? I know this post was edited twice and is very jumbled, so if you can make sense of it and offer solutions, much obliged.
t4duzan said:
Ok glevitan, I believe the problem might be in the PD98IMG.zip that's on the root of my SD card. I noticed when the phone booted into hboot, it would display that the image file was wrong, or something to that effect and then would force an update, which would load the HTC spashscreen and then ultimately fade out. I figured it had a bad PD98IMG.zip file, so I found the original aahk-13012012.zip and extracted the PD98IMG.zip from there and overwrote the one in the root. It didn't work. A different story...I noticed on my Inspire 4G (working correctly, but hboot had same error, even though I could load recovery from there) that it wasn't finding the correct image either. I copied over the PD98IMG.zip onto my phone and now both phones are now fading out on the HTC splashscreen after about 4 seconds. This tells me that it's in the SD card, right? If so, any suggestions? Both phones were rooted using this version of aahk.
Edit: Also, with this new PD98IMG.zip image, hboot will go into the process of parsing for
[1] boot
[2] recovery
[3] radio_v2
Once this is done, I push Power to reboot and that's when I get the failure in the HTC splashscreen.
Edit: I noticed in the PD98IMG.zip there was no md5 file, so I stuck one in there and got my phone working (which is not the one with the original issue started in this thread) and was able to restore a nandroid backup. I put this same SD card in the original damaged phone and it didn't restore like mine did. I still think it's an SD card issue causing the HTC splashscreen fadeout, but don't know where to go know.
Also, my PD98IMG.zip only has a recovery.img and a recovery.md5 file in it. I noticed that the original aahk PD98IMG.zip has those along with a boot.img and a radio.img. Should those be in the PD98IMG.zip? I know this post was edited twice and is very jumbled, so if you can make sense of it and offer solutions, much obliged.
Click to expand...
Click to collapse
Ok, I quite don't get much...sorry, but that version of the Hack Kit is old, so use the lastest one: http://tau.shadowchild.nl/attn1/?p=74
But again, I don't still get if the phone is S-OFF or not. If you are S-OFF there is no need to do all that process. Even, you can flash a RUU without using the PD98IMG way if you suspect that the sdcard is messed.
You can flash it over fastboot.... Anyway, you will have to flash this RUU (which is the gingerbread update 2.3.3 version of ATT. the lastest one, if you are not S-OFF will make things a bit harder for you to run the hack kit later): http://https://dl.dropbox.com/u/30674730/RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe
Put the phone in fastboot usb (when in hboot, plug the phone and it should read fastboot usb in red, if not, just press power button to toggle to fastboot). Then, just run that .exe file and it should flash...
glevitan said:
Ok, I quite don't get much...sorry, but that version of the Hack Kit is old, so use the lastest one: http://tau.shadowchild.nl/attn1/?p=74
But again, I don't still get if the phone is S-OFF or not. If you are S-OFF there is no need to do all that process. Even, you can flash a RUU without using the PD98IMG way if you suspect that the sdcard is messed.
You can flash it over fastboot.... Anyway, you will have to flash this RUU (which is the gingerbread update 2.3.3 version of ATT. the lastest one, if you are not S-OFF will make things a bit harder for you to run the hack kit later): http://https://dl.dropbox.com/u/30674730/RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe
Put the phone in fastboot usb (when in hboot, plug the phone and it should read fastboot usb in red, if not, just press power button to toggle to fastboot). Then, just run that .exe file and it should flash...
Click to expand...
Click to collapse
Sorry, I thought I had said I was S-OFF. I can get my phone to be fastboot usb when hooked up with a usb in hboot, but can't reflash aahk or anything computer related. It just doesn't seem to recognize anything on the PC.
Edit: And I apologize glevitan, I've searched and found a couple of threads related to the black screen after the HTC logo, so I know you guys have helped and explained this numerous times before. I just couldn't get any of the suggestions from those threads to work out. Thanks for any help you may input.
t4duzan said:
Sorry, I thought I had said I was S-OFF. I can get my phone to be fastboot usb when hooked up with a usb in hboot, but can't reflash aahk or anything computer related. It just doesn't seem to recognize anything on the PC.
Edit: And I apologize glevitan, I've searched and found a couple of threads related to the black screen after the HTC logo, so I know you guys have helped and explained this numerous times before. I just couldn't get any of the suggestions from those threads to work out. Thanks for any help you may input.
Click to expand...
Click to collapse
I was having a similar problem, I'm not too sure if it relates to what your experiencing. But I was trying to gain s-off my hboot was in fact unlocked but was still s-on. I was reading around and flashed a few boot.img with fast boot. I had that problem where htc screen would show then fade to black, and then stay black.
What I did was (I had installed recovery pretty early on) I did a factory reset in recovery then went to restore. Prior to this thank god I had transfered my nandroids to the pc b4 flashing new boot.img(s) then flashed the boot.img from the nandroid I just restored. All was well back into stock. I then found the insecure boot.img to use for aahk, flashed that in fastboot and relocked hboot. Reran aahk in linux. Got me to S-OFF with unlock.
If you need a fairly stock nandroid I can provide one.
t4duzan said:
Sorry, I thought I had said I was S-OFF. I can get my phone to be fastboot usb when hooked up with a usb in hboot, but can't reflash aahk or anything computer related. It just doesn't seem to recognize anything on the PC.
Edit: And I apologize glevitan, I've searched and found a couple of threads related to the black screen after the HTC logo, so I know you guys have helped and explained this numerous times before. I just couldn't get any of the suggestions from those threads to work out. Thanks for any help you may input.
Click to expand...
Click to collapse
Ok, you need to reflash the RUU I posted above....you just need to flash that from fastboot usb. If you can't do it, Then you need to flash it manually. Just let me know and I can lend you a hand over teamviewer. When you get the phone back, then you run the hack kit.
glevitan said:
Ok, you need to reflash the RUU I posted above....you just need to flash that from fastboot usb. If you can't do it, Then you need to flash it manually. Just let me know and I can lend you a hand over teamviewer. When you get the phone back, then you run the hack kit.
Click to expand...
Click to collapse
glevitan, you're awesome. I restored the phone by running the RUU executable and reran the aahk and am now fully rooted. Both times I got the black screen on this phone previously was on the same PC, but this time I ran aahk on my PC and it ran correctly. I sincerely appreciate your help in helping me to achieve root for this phone. Hopefully this thread helps someone in the future.
Can you or anyone do step by step on how too root the HTC inspire? From step one an not for get anything even if its an hour long video? Anything would help. I'm new with the HTC inspire. It seems that I can't root it at all. I'm not saying I can't root phones I rooted a lot. I have done the HTC Evo sprint the HTC amaze tmobile I have done three galaxy s2's the sprint the boost an the straight talk an many more. But this HTC inspire has me at a "STOP" noting seems too work at all. Please Help Me.
Sent from my SGH-I777 using xda app-developers app
jimmyport said:
Can you or anyone do step by step on how too root the HTC inspire? From step one an not for get anything even if its an hour long video? Anything would help. I'm new with the HTC inspire. It seems that I can't root it at all. I'm not saying I can't root phones I rooted a lot. I have done the HTC Evo sprint the HTC amaze tmobile I have done three galaxy s2's the sprint the boost an the straight talk an many more. But this HTC inspire has me at a "STOP" noting seems too work at all. Please Help Me.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
What have you tried? AAHK is the only real option. There is a very clear guide over at the Ace Think Tank post #7, linked in my signature.
jimmyport said:
Can you or anyone do step by step on how too root the HTC inspire? From step one an not for get anything even if its an hour long video? Anything would help. I'm new with the HTC inspire. It seems that I can't root it at all. I'm not saying I can't root phones I rooted a lot. I have done the HTC Evo sprint the HTC amaze tmobile I have done three galaxy s2's the sprint the boost an the straight talk an many more. But this HTC inspire has me at a "STOP" noting seems too work at all. Please Help Me.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Besides what bananagranola said, you need to know that video tutorials suck. They skip important details and that, will probably get you stuck. Read the guide adviced, and the hack kit site (got the link in the Ace Think Tank Thread)...that is all you need to know.
I have tryed the Aahk. My problem is when it ask me to downgrade ruu an all that. All my phone dose when I run the aahk I push 1 an then it ask too downgrade so i put y then something about the ruu an I put y then it says pushing the 9 something file. ( sorry I'm not home on my computer ) so I'm not 100% on what it is saying. But then my phone boots to Hboot dose its thank. Then says bad image. I have done this a lot of times with the aahk. I even tock the s-on off an on. Is there a way that someone can jump into my computer an do this?
Sent from my SGH-I777 using xda app-developers app
---------- Post added at 10:11 AM ---------- Previous post was at 10:03 AM ----------
I wish they would do a video an not skip anything at all. That would be really nice. I fill like there is stuff I'm missing. Dose anyone know off there heads what all needs too be downloade? I have the aahk an drivers. I did everything I been reading the fing manual. I have a ROM an gapps ready too go. Just need too root the phone so I can run the rom.
Sent from my SGH-I777 using xda app-developers app
jimmyport said:
I have tryed the Aahk. My problem is when it ask me to downgrade ruu an all that. All my phone dose when I run the aahk I push 1 an then it ask too downgrade so i put y then something about the ruu an I put y then it says pushing the 9 something file. ( sorry I'm not home on my computer ) so I'm not 100% on what it is saying. But then my phone boots to Hboot dose its thank. Then says bad image. I have done this a lot of times with the aahk. I even tock the s-on off an on. Is there a way that someone can jump into my computer an do this?
Sent from my SGH-I777 using xda app-developers app
---------- Post added at 10:11 AM ---------- Previous post was at 10:03 AM ----------
I wish they would do a video an not skip anything at all. That would be really nice. I fill like there is stuff I'm missing. Dose anyone know off there heads what all needs too be downloade? I have the aahk an drivers. I did everything I been reading the fing manual. I have a ROM an gapps ready too go. Just need too root the phone so I can run the rom.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Try using a different sdcard. If the RUU image is not being read, that is probably due to a bad sdcard. It is corrupted to work as a goldcard but fine for usual day use.
I have. I have had 4 of them now. Two 2 gigs one 36gig an one 8 gig. New I paid for them an a new USB cored fast data cable for the phone.
Sent from my SGH-I777 using xda app-developers app
jimmyport said:
I have. I have had 4 of them now. Two 2 gigs one 36gig an one 8 gig. New I paid for them an a new USB cored fast data cable for the phone.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
2gb is enough...don't use another cable but the oem one that came with the phone. Anyway, that seems to be a sdcard issue. Try with another one and then report back.
I will go buy one more. But I Dont thank its that. An why not use a fast data cored for my phone?
Sent from my SGH-I777 using xda app-developers app
I've got an AT&T HTC One, I rooted it and installed TWRP and haven't had the down time to do much else with it, including installing a rom yet.
I don't mind the oem ATT rom but I do need the Hotspot feature to work for my wifi tablet.
I've tried to turn on the hotspot feature with a couple scripts I've found on XDA but none of them seem to work so I've come to the conclusion that I'm going to have to change rom to be able to use the hotspot so this morning I Downloaded CM10 and placed it on the "SDcard" of my phone. I then tried to install it with TWRP. everything goes well half way through the install and then it hangs up about 60% through, it eventually seems to time out after like 15-20 minutes of not doing anything.
I then reboot it and all I get is an infinite animated CM boot logo.... I let it sit for an hour just to make sure it wasn't just a slow install.
I reinstalled it three times and the outcome was the same each time so I tried to ADB sideload it with the same outcome.
I even went on CM's site and downloaded another copy of CM10 but it made no difference.
I ended up having to reinstall the backup I made prior to starting this so I had my phone as I needed to go run some errands.
Does anyone know why I had the issues I was having with installing CM10?
Something I did wrong? How do I get CM to install?
Thanks
jessepatty said:
I've got an AT&T HTC One, I rooted it and installed TWRP and haven't had the down time to do much else with it, including installing a rom yet.
I don't mind the oem ATT rom but I do need the Hotspot feature to work for my wifi tablet.
I've tried to turn on the hotspot feature with a couple scripts I've found on XDA but none of them seem to work so I've come to the conclusion that I'm going to have to change rom to be able to use the hotspot so this morning I Downloaded CM10 and placed it on the "SDcard" of my phone. I then tried to install it with TWRP. everything goes well half way through the install and then it hangs up about 60% through, it eventually seems to time out after like 15-20 minutes of not doing anything.
I then reboot it and all I get is an infinite animated CM boot logo.... I let it sit for an hour just to make sure it wasn't just a slow install.
I reinstalled it three times and the outcome was the same each time so I tried to ADB sideload it with the same outcome.
I even went on CM's site and downloaded another copy of CM10 but it made no difference.
I ended up having to reinstall the backup I made prior to starting this so I had my phone as I needed to go run some errands.
Does anyone know why I had the issues I was having with installing CM10?
Something I did wrong? How do I get CM to install?
Thanks
Click to expand...
Click to collapse
What hboot? You may have to flash boot image separately in adb or s-off.
Venomtester said:
What hboot? You may have to flash boot image separately in adb or s-off.
Click to expand...
Click to collapse
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
jessepatty said:
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
Click to expand...
Click to collapse
On 1.14 the boot image needs to be flashed separately. Flash from fastboot..
Fastboot flash boot boot.img
The boot image is inside the Rom.zip your flashing. Keep a copy of the Rom on pc and extract files with winzip or whatever you like to use. But boot.img in adb folder and type the command, reboot and it should boot.
S-off can be done but only on a sense based Rom like viperXL.
Also read the stickies... They are there for a reason..
Sent from my HTC One X using xda app-developers app
This is not true. I s-off'd with cm10. Though you need to enable ADB root in settings for it to work.
Sent from my HTC One X using xda app-developers app
jessepatty said:
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2136172
exad said:
This is not true. I s-off'd with cm10. Though you need to enable ADB root in settings for it to work.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Well that explains why I was having issues on cm10.
Sent from my HTC One X using xda app-developers app
Make sure you're using the cm 10 for one xl (evita) and not the one x.
http://wiki.cyanogenmod.org/w/Evita_Info
I'll check out the links, thanks.
I can see allot has changed since December when I last messed with the phone. Back in December Clockwork recovery wasn't supported on the ATT version of the HOX. I see it now is in a touch version.
apparently I am doing something wrong as I keep getting the same indefinite CM boot logo and can't get past it. It appears I do not fully understand the process to side load the rom.
With that said, I restored it from a backup and I guess I'll just wait until I can confidently install a rom. This phone is so much different then my previous phones and tabs in regards to how it was unlocked and the install of different roms. I didn't have any problem figuring those out but this one has more steps involved which is aiding to my confusion. Maybe I'll find a step by step for my Hboot that I can follow, in the meantime I'll just keep having to look for free wifi for my tablet while I'm out and about.
You'd think there would be an easier way to enable the wifi hotspot on the phone.... LoL
Thanks for the info guys.....truly appreciated.
Try this...
http://code.google.com/p/android-wifi-tether/
Sent from my HTC One X using xda app-developers app
I flashed twrp recovery from HOX interational version by mistake. Now the phone is stuck in bootloop. Tried to boot into bootloader by pressing vol down + power but that didnt work and i also tried to reboot via adb but that also threw me an error . I cant even turn off my phone it just keep rebooting.. Is there anyway i can revert this? Btw my phone is recognized by PC in disk manager though.
My phone is s-off and unlocked.
Any help would be appreciated.
Hold the volume down button while it's rebooting, do not let go, it should hopefully get to the bootloader. The next problem is that you could have borked the recovery partition by flashing the wrong recovery. Try to flash the right recovery, it might work. Otherwise you'll need to run an RUU.
Out of interest, how in the world did you manage to flash a recovery from the Endeavoru?
Sent from my Evita
rangers said:
I flashed twrp recovery from HOX interational version by mistake.
Click to expand...
Click to collapse
Be extremely careful to only flash mods from this forum section specific to the EVITA: http://forum.xda-developers.com/one-x-att
You can also use my Index thread (also EVITA specific): http://forum.xda-developers.com/showthread.php?t=1671237
Especially since you are s-off, you need to be extremely careful about what you flash (and you obviously were not) since all safety checks (such as device check) are disabled with S-off. Different devices have different partitions, and flashing a mod for another device could have easily messed up the hboot partition and bricked the phone.
The fact the phone still turns on is a good sign, and you can probably get it sorted at as timmaaa instructed in the previous response. But consider this a close call and don't make the same mistake again.
Thank you so much timmahy. Just pressing volume down worked and I flashed a RUU after. I was searching for "recovery for hox" on Google and I found one and it happened to be the international versions twrp recovery. This is my gfs phone and I really did not know about the whole evita and hox Tegra difference. Thanks a lot again
Sent from my Nexus 5 using xda premium
Cool, glad to help. Just make sure you only stay within our forum, the main page is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Sent from my Evita
rangers said:
I was searching for "recovery for hox" on Google and I found one and it happened to be the international versions twrp recovery. This is my gfs phone and I really did not know about the whole evita and hox Tegra difference.
Click to expand...
Click to collapse
Google is not your friend, when searching for phone mods. Stick to the proper XDA forum, and always do the proper research to be absolutely certain you are flashing the right thing. There are plenty of devices (not just the HOX) with different carrier versions, variants, etc. that can get you bricked if you flash the wrong version.