Database Info

Stuck in Fastboot/ Recovery;

Hey guys,
I unlocked the bootloader for my NS4G, installed CWM 5.8.0.2, and wiped cache, dalvik, battery stats, and boot, and then proceeded to install the v7 JB ROM by hp420... the problem is when I tried to install it, I get a status 7 and an abort. When I try to reboot my phone, it obviously stays in fastboot, because I don't have boot or a ROM, yet I can go back to recovery... can anyone tell me how to revert to a stock ROM or how to install the v7 ROM or another ROM so I can actually use my phone? Thank you! :good:
Edit: Mounted Storage to computer, tried to install a CM9 ROM to the phone, same problem.. seems like CWM is the problem, how would I fix this?

Here's a link to download the 4.0.4 factory image for your phone:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
open it with 7Zip and flash the boot.img and system.img in there with fastboot.

You need to format system when you flash a custom ROM over a stock ROM. Well basically anytime you go from one different ROM to another like aokp - petes- miui and so on.
Its called a full wipe

RE: fastboot cmd line
albundy2010 said:
You need to format system when you flash a custom ROM over a stock ROM. Well basically anytime you go from one different ROM to another like aokp - petes- miui and so on.
Its called a full wipe
Click to expand...
Click to collapse
Okay, thanks guys, I have a problem. When I use fastboot command line, I type fastboot flash system (systempath) and when I hit enter a whole list of options pop up. what should I actually type after? I don't know what to do with the options.
Edit: after an hour of trying, it finally just gave in and it worked! Thank you guys so much!

[Q] Phone Stuck in Boot Loop Why?

Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!

ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck

thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?

Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.

You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium

ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?

ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium

[Q] Custom Rom don't work

Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb

rldieb said:
Unlocked and rooted ATT HTC One X and flashed pa_evita-2.54-09NOV2012-210217 ROM.
Boot up as far as an Android character with the lettering Paranoid Android 2.+ and then freezes there.
Any suggestions?? If nothing else, how do I get back to stock ROM?
Noob rldieb
Click to expand...
Click to collapse
1. What recovery are you using?
2. Did you wipe cache/dalvik-cache, factory reset?
In order to get back to a stock ROM, you will need to boot into recovery, then mount your usb storage. Put the rom on your sd card and then unmount. To be safe, wipe the cache and dalvic cache, then flash the stock rom.

What hboot are you on?
You may have flash boot.img first if you are on hboot 1.14

I think he just didn't full wipe

That's just wrong!
Sent from my Nexus 7 using Tapatalk 2

I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help

threetwentyfizzle said:
I'm having the same issue. I'm trying to flash this same rom on a device rooted on 2.20. I think my issue has something to do with flashing the boot.img. I have tried to flash using hasoon's toolkit, which doesnt seem to work, i have extracted the zip and placed the boot.img in the kernel folder, and when the command prompt tries to flash it, it says error. I have also tried flashing the kernel from the phone directly using the flash flash image gui app, and it says flash is successful, but when it prompts to boot into recovery, the command doesnt work from my phone so i have to boot into recovery manually.
can anyone give a solid link or tutorial on how to successfully flash the boot img onto my device, every link I have read uses windows cmd prompt, which when i try to replicate, it never works.. So, for now I flashed back to viper rom, since it has its own installer. It would be so nice if all these other roms were able to install like that.
thanks in advance for the help
Click to expand...
Click to collapse
I do have a solution! Download Flash Image GUI from the market (it's $1.99) and it will do the process for you, no commands needed! The app is also available via XDA for free, do a search and download it.

[Q] Flashed boot.img in Fastboot, works - flashed in TWRP, does not work

Hey guys, thanks for all the previous help i've gotten from here.
Here's the deal, I have a 2.2, rooted and unlocked ATT HOXL. I flashed the SU binary and have root and everything. I'm on the stock 2.2 ROM.
Do you need to install a different ROM before flashing the kernel? If so, then I will wait until this download finished for CleanROM. If not, then continue below..
I flashed the boot.img for ElementalX-3.1 in Fastboot (Fastboot 1.14), rebooted phone like normal, phone came up, kernel is showing in the information page on the phone, it is running at 1.7ghz. That's fine, but then I realized I had never gotten any installer or anything. So, I went into recovery to flash the whole ZIP file. Go to reboot the phone and it hangs on boot after the first HTC logo.
I tried flashing the boot.img, then rebooting to recovery, and flashing the ZIP, then clearing the cache, and then rebooting. Still hangs. I am able to go into recovery and restore a backup if I need to, so at least my phone isn't dead, but I want to do this.
I also tried installing the ZIP, then rebooting into Fastboot and flashing the img, and then booting the phone up normal.
So as it sits now, I have the Kernel installed from ONLY the boot.img, I did not run the ZIP.
Do I need to flash a stock kernel in Fastboot, and then try just flashing the whole thing in TWRP? From what I have read, the steps for flashing the kernel on 1.14 is:
1. Flash boot.img
2. Reboot to recovery
3. Flash ZIP
4. Clear cache
5. Reboot phone as normal
Are those the correct steps? Do I need to flash a stock kernel before trying this again, or can I just start from square one, as if I were using a stock kernel?
Thanks

You can't flash kernels from recovery on the higher hboot. You have to fastboot them or use the flash image GUI app.
Some ROMs/kernels use a script that works around that, but not all do.

Really frustrated, phone keeps booting to recovery after failing to boot to rom

Hi all, I've been trying for the past 8 hours(you can imagine how frustrated i am right now) to install HatkaXL(http://forum.xda-developers.com/showthread.php?t=2075783) for so long now and I have literally no idea where to go. I was only just trying to switch from cleanrom to Hatka. And I've ended up with absolutely no progress since 8 hours have passed. Actually, i've probably lost progress because i accidentally wiped my data without backing up. Here's what i've done so far:
i'm under AT&T, hboot-1.14, any other info i'll be glad to share. it's rooted and currently unlocked of course.
1. Used fastboot flash boot boot.img to no avail
2. Re-locked bootloader, ran an RUU(i made sure it was compatible), unlocked it and tried to flash HatkaXL froma fresh start
3. Wiped data, cache, etc. then flashed the rom(which still didnt work)
4. flashed TWRP, rebooted, went into TWRP, wiped data, cache, etc. and then flashed HatkaXL
What the problem is that my one x won't go past the HTC screen with all that red developmental font. It'll boot and then go to the screen, stay there for about 10 seconds and then turn off. Then it'll start up again 10 seconds later to boot back to TWRP.
At one point, i encountered a boot loop where it actually went past the red developmental font screen and to the HTCtm Beats Audio and then it just restarted from there. However, now that issue disappeared and it's just booting to recovery after shutting down.
Now that's where I was thinking that maybe since it's booting directly to TWRP that would mean that I would have to go into cmd and 'fastboot flash boot boot.img' right? I did exactly that, one, twice, three times, even with fastboot erase cache.
i can't even remeber everything i did because i'm so tired since i've been up through the night reading throug threads, trying to fix this damn thing.
I would really really appreciate it if anyone could help me out here because i've never been this lost when it came to technology lol.

It sounds like you were on the right track, I am lost why it failed for you?
Can you install cleanrom again? eg is it just HatkaXl that is not working? Perhaps your download is bad or the ROM is simply broken and you need to report it to the dev?
When you were flashing the boot.img did it say success? Did you triple check you are extracting the correct boot.img to the correct folder?
Just to be clear to install ROM's I often do:
1)wipe data and system
2)install ROM
3)fastboot flash boot boot.img

twistedddx said:
It sounds like you were on the right track, I am lost why it failed for you?
Can you install cleanrom again? eg is it just HatkaXl that is not working? Perhaps your download is bad or the ROM is simply broken and you need to report it to the dev?
When you were flashing the boot.img did it say success? Did you triple check you are extracting the correct boot.img to the correct folder?
Just to be clear to install ROM's I often do:
1)wipe data and system
2)install ROM
3)fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks for the response. Yep, every time i flash the boot.img, it's always a success. i also mae sure it's the correct one.
sending 'boot' (6156 KB)...
OKAY [ 0.933s]
writing 'boot'...
OKAY [ 1.475s]
finished. total time: 2.413s
Click to expand...
Click to collapse
I just tried to install cleanrom 5.1 again and it's not working either. Actually, it's stuck at the red developmental font screen this time so atleast it's not immediately rebooting to go to TWRP.
UPDATE: It's working! CleanROM! Thank you so much man! I'll be back to ask you another question. Gotta go real quick.

Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen

a box of kittens said:
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
Click to expand...
Click to collapse
I also noticed this. Op, a few things to remember when flashing boot.img.
The boot.img needs to be extracted from the rom you are flashing.
The phone must be in bootloader, plugged in to pc and in fastboot usb mode. (the phone will say fastboot usb.
The boot.img must be in the folder with the fast boot and adb programs.
I have more than just a feeling you were doing something wrong
Sent from my One X using xda app-developers app

Thanks for the responses guys, you guys are saving me lots of stress and time.
a box of kittens said:
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
Click to expand...
Click to collapse
You are correct that clean rom 5.1 flashes it for you, which is through its AROMA installer. However, HatkaXL also uses the AROMA installer, and there's a line in the installation screen where it says "flashing boot.img." - both ROMs have that line. Interestingly, it worked when I followed twistedddx's order so I'm going to try that again.
exad said:
I also noticed this. Op, a few things to remember when flashing boot.img.
The boot.img needs to be extracted from the rom you are flashing.
The phone must be in bootloader, plugged in to pc and in fastboot usb mode. (the phone will say fastboot usb.
The boot.img must be in the folder with the fast boot and adb programs.
I have more than just a feeling you were doing something wrong
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yup, I have those in the same folder correctly. I always extract the boot.img from the rom zip into the folder with both fastboot and adb(how else would I able to have fastbooted in the first place?), always made sure the phone was in bootloader, plugged in, and in fastboot usb.
edit: I wiped, then installed hatkaXL, then fastboot flash boot boot.img, and now it starts, it gets past the red developmental screen, INTO the HTC Onetm beats audio screen, turns off and then restarts again through the whole process. it's jst looping now.
edit2: Flashed ViperXL, that's working. I guess HatkaXL just isn't for my phone.. sigh. I hope this thread helps anyone else.

devfrost said:
Thanks for the responses guys, you guys are saving me lots of stress and time.
You are correct that clean rom 5.1 flashes it for you, which is through its AROMA installer. However, HatkaXL also uses the AROMA installer, and there's a line in the installation screen where it says "flashing boot.img." - both ROMs have that line. Interestingly, it worked when I followed twistedddx's order so I'm going to try that again.
Yup, I have those in the same folder correctly. I always extract the boot.img from the rom zip into the folder with both fastboot and adb(how else would I able to have fastbooted in the first place?), always made sure the phone was in bootloader, plugged in, and in fastboot usb.
edit: I wiped, then installed hatkaXL, then fastboot flash boot boot.img, and now it starts, it gets past the red developmental screen, INTO the HTC Onetm beats audio screen, turns off and then restarts again through the whole process. it's jst looping now.
edit2: Flashed ViperXL, that's working. I guess HatkaXL just isn't for my phone.. sigh. I hope this thread helps anyone else.
Click to expand...
Click to collapse
Could be a kernel issue.. Try flashing stock kernel after flashing rom?... That's all I can think of. Also, I don't know if you do but I always wipe cache, dalvik, system, and then factory reset in twrp and I've never had any issues with any roms.
Sent from my One X using xda app-developers app