[Q] problem with recovery and boot - HTC One X+

hi guys
i've unlocked my HTC ONE X + international!
but now i can't go further the HTC logo
i tried fastboot, flashing boot and recovering recover.img. but nothing go right.

---

Some questions:
Which rom did you try to flash?
What method did you use to flash it? (e.g. Hasoon's all in one tool/through recovery/sideload)
Did you make sure to flash your kernel (boot.omg) separately?
Did you perform a full wipe before flashing?
Can you enter the bootloader by holding volume-down while powering the phone on?
Can you use adb or fastboot to interact with the phone? e.g.
Code:
$ adb reboot bootloader
or
$ fastboot devices
Sent from my cellular telephone using xda premium

---

o_O said:
Some questions:
Which rom did you try to flash?
What method did you use to flash it? (e.g. Hasoon's all in one tool/through recovery/sideload)
Did you make sure to flash your kernel (boot.omg) separately?
Did you perform a full wipe before flashing?
Can you enter the bootloader by holding volume-down while powering the phone on?
Can you use adb or fastboot to interact with the phone? e.g.
Code:
$ adb reboot bootloader
or
$ fastboot devices
Sent from my cellular telephone using xda premium
Click to expand...
Click to collapse
after i unlocked the phone i've used fastboot to fastboot recovery.img
and that's all i did .
now i have low battery

---

Boot into bootloader by holding volume-down and restarting the phone (if you don't know how to do that, hold the power button until the capacitive lights flash).
Then, try flashing a recovery image. You can get twrp from the thread in the One X+ Original Android Development forum. I think you already have the platform tools (adb and fastboot).
The command to flash a recovery is:
Code:
$ fastboot flash recovery recovery.img
This is assuming your recovery filename is "recovery.img" and that it's in the same directory as your command prompt when you run the command.
Sent from my cellular telephone using xda premium

---

o_O said:
Boot into bootloader by holding volume-down and restarting the phone (if you don't know how to do that, hold the power button until the capacitive lights flash).
Then, try flashing a recovery image. You can get twrp from the thread in the One X+ Original Android Development forum. I think you already have the platform tools (adb and fastboot).
The command to flash a recovery is:
Code:
$ fastboot flash recovery recovery.img
This is assuming your recovery filename is "recovery.img" and that it's in the same directory as your command prompt when you run the command.
Sent from my cellular telephone using xda premium
Click to expand...
Click to collapse
thanks bro )))
but now it says there is no any zip file
is there any methods to "put custom rom inside" the phone???

---

tyomaus said:
thanks bro )))
but now it says there is no any zip file
is there any methods to "put custom rom inside" the phone???
Click to expand...
Click to collapse
If you've gotten the recovery installed, then you can sideload the rom onto the phone. I can give you instructions to do that with TWRP as your recovery. With your phone connected to your computer, enter the recovery from the bootloader. Choose the "Advanced" button, and then "ADB Sideload" and then swipe to start the sideload process.from your command line on your computer, you can now start the sideload process:
Code:
$ adb sideload name-of-rom-zip-file.zip
Obviously you would need to put the actual name of your rom's zip file and make sure your zip is in the correct directory to be picked up by the command. You should see the rom begin to upload to your phone, and when it's done, it will automatically flash.
I've found that sometimes sideload can take a little while to detect the phone but usually it detects it immediately. If it's taking a while, try running the following command and then do the sideload again; it might help:
Code:
$ adb kill-server
$ adb sideload name-of-rom-zip-file.zip
Don't forget that because we haven't gotten S-OFF for our device yet, we need to flash the kernel separately. Just open the rom zip file, and extract "boot.img". Then you need to enter the bootloader and flash that to your phone with this command:
Code:
$ fastboot flash boot boot.img
Hopefully that helps to sort your phone out.

---

thanks for help! )))
, MAN u r the best!!!! thanks a lot ! ))))

---

No problem! Glad to help.

---

o_O said:
No problem! Glad to help.
Click to expand...
Click to collapse
hi, i have one more problem (((
i've installed custom ROM, but only AOKP is working but not properly, after installing says there is no SD card ((
others stuck in loading screen.

---

This is because the default location of your SD card has changed from /data/media to /data/media/0. You can fix it by simply moving the contents of /data/media to /data/media/0.
Code:
$ adb remount
$ adb shell
# mv /data/media /data/0
# mkdir /data/media
# mv /data/0 /data/media/
Make sure you copy the commands exactly, including the slashes and that should have the contents of your SD card accessible again.

---

o_O said:
This is because the default location of your SD card has changed from /data/media to /data/media/0. You can fix it by simply moving the contents of /data/media to /data/media/0.
Code:
$ adb remount
$ adb shell
# mv /data/media /data/0
# mkdir /data/media
# mv /data/0 /data/media/
Make sure you copy the commands exactly, including the slashes and that should have the contents of your SD card accessible again.
Click to expand...
Click to collapse
thannks MAN, but it does not work (((
i tried to install OrDroid and it flies normally, however i'd like to use CM 10 4.2.2 which stuck in loading logo
maybe there is something i do wrong?!

---

tyomaus said:
thannks MAN, but it does not work (((
i tried to install OrDroid and it flies normally, however i'd like to use CM 10 4.2.2 which stuck in loading logo
maybe there is something i do wrong?!
Click to expand...
Click to collapse
every rom needs the correct boot.img/kernel to work. did you flash blade kernel for CM 10.1? did you wipe/factory reset your phone in recovery before you flashed CM 10?

---

Exactly what reaper90 said, the first thing you should check when you get a bootloop is the kernel.
A lot of other phones don't require you to flash the kernel separately, but those phones have S-OFF available to them. Since we're stuck with S-ON (for now), the boot partition is locked and can't be written to from the phone. So you have to flash the img containing the kernel + ramdisk separately. Also note that max has done three different versions of the BLADE kernel, so you need to ensure that you're grabbing the correct one.
Check max's post here: http://forum.xda-developers.com/showpost.php?p=34962464&postcount=1
Edit: Just another couple of things:
1. Like reaper90 said, doing a full wipe really helps when switching between roms. Usually you can get away without wiping if you're installing a new version of the SAME rom, but to be on the safe side I personally wipe everything when I flash a different rom.
2. If you're certain that you've done everything correctly, and it's still not working, try clearing your cache and dalvik cache from the recovery. Occasionally that can fix minor problems.

---

cool
reaper90 said:
every rom needs the correct boot.img/kernel to work. did you flash blade kernel for CM 10.1? did you wipe/factory reset your phone in recovery before you flashed CM 10?
Click to expand...
Click to collapse
thank you MAN!!! it's working! :good:

---

yourthebest
o_O said:
Exactly what reaper90 said, the first thing you should check when you get a bootloop is the kernel.
A lot of other phones don't require you to flash the kernel separately, but those phones have S-OFF available to them. Since we're stuck with S-ON (for now), the boot partition is locked and can't be written to from the phone. So you have to flash the img containing the kernel + ramdisk separately. Also note that max has done three different versions of the BLADE kernel, so you need to ensure that you're grabbing the correct one.
Check max's post here: http://forum.xda-developers.com/showpost.php?p=34962464&postcount=1
Edit: Just another couple of things:
1. Like reaper90 said, doing a full wipe really helps when switching between roms. Usually you can get away without wiping if you're installing a new version of the SAME rom, but to be on the safe side I personally wipe everything when I flash a different rom.
2. If you're certain that you've done everything correctly, and it's still not working, try clearing your cache and dalvik cache from the recovery. Occasionally that can fix minor problems.
Click to expand...
Click to collapse
nothing to say, just HUGE THANKS!!! )))

---

i have more questions, one of them is - how can i rollback stock ROM for my HOX+? i've bought it in UAE!
is it possible to install original ROM, if so where can i find one for my HOX+ ?
thanks in advance !

---

Sure, it's possible, and you have a couple of options depending on how "stock" you want to go.
If you just want to go back to a Sense rom, you can go to the One X+ Android Development forum and download any of the international roms from there. You would need to flash Elite kernel or hXORe kernel, which can also be found in that forum, and the process for flashing the rom and kernel is exactly the same as the AOKP/CM roms you already tried.
If you specifically need to get back to STOCK, then it's a little more complicated. You need to run a RUU (Rom Update Utility) for your device, which will put the original software back on your phone, but you need to remember to re-lock your bootloader before you run it, or it will fail. You can download the correct RUU for your device here (http://androidfiles.org/ruu/?developer=ENRC2B).
I would hazard a guess that you can find the right version by matching the radio version on your phone to the radio version on the RUU, along with your geographic location. You can find your phone's radio version by going to settings > about phone > baseband version. A quick explanation behind that logic is that a normal rom-flash won't touch your phone's radio, so you're likely to still have the same radio version that your phone shipped with.
WARNING, however, messing with your radio can brick your device so please please make sure you have the right one before you flash. I'm not sure which is the correct one for your device and the only RUUs I've ever flashed were way back in the early Windows Mobile days, so hopefully someone else here can give you better direction on that point.
Finally, if I were to give my opinion, you're better off taking a rom from the Android Development forum. I'm a die-hard AOSP fan, but I've flashed and played with the roms in there and our Sense devs have done a great job with the X+. The only reason I'd go back to stock is if I had to for warranty purposes.

---

tyomaus said:
i have more questions, one of them is - how can i rollback stock ROM for my HOX+? i've bought it in UAE!
is it possible to install original ROM, if so where can i find one for my HOX+ ?
thanks in advance !
Click to expand...
Click to collapse
As already said, I'd recommend installing a stock like custom rom, for example Android Revolution HD, it's very close to stock. You can find stock kernel/boot.img in the thread and if you want it as close to stock as possible you can just leave out all the tweaks options in aroma installer.

---

reaper90 & thank u BROS! )))