Develop Bugs

[Q] How do I get past "initiating swagger" boot loop

Hello,
I'm new to the OneV phone (CDMA), coming from the awesome Rezound. Starting from stock, I used Hasoons One V all in one kit. I'm unlocked and using TWRP 2.2. I first wiped my phone, installed the Nov 18 aokp primoc unofficial, flashed gapps-jb-4.2-V1-20121117-signed, and then flashed the extracted boot.img from the same rom using the command prompt fastboot flash. I did this process a few times now, but I still get stuck at the loop screen.
I've also tried flashing Jellyboot5.
Anyone have an idea what I am doing wrong? I've flashed roms many times on the Rezound, but it was so much simpler!

http://forum.xda-developers.com/showthread.php?t=1996665

cybervibin said:
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
Thanks for responding. So if the kernal is a .zip file, I should rename the entire file "boot.img" correct? I don't extact the boot.img file from the zip...

it will be in .img format by default if not try opening it and see!

cybervibin said:
it will be in .img format by default if not try opening it and see!
Click to expand...
Click to collapse
Right, I figured the boot.img inside the kernal .zip is all that is necessary. I still can't figure out where I'm flashing wrong. I was able to successfully flash my nandroid of my stock.
1. In TWRP, I wiped cache/davilk, system, and did a factory reset
2. Then flashed a stable/nightlies version of rukins AOKP jellybean
3. Flashed gapps (also tried w/o flashing this)
4. In the bootloader, I flashed the boot.img in cmd (tried from rom .zip and jellyboot)
5. After phone restarted it was at the stuck at the boot loop "initiating swagger" *sigh*
Maybe its the rom version I'm using? Can you or someone recommend a good rom to start off with along with what kernal I should use?

ninjastic said:
Right, I figured the boot.img inside the kernal .zip is all that is necessary. I still can't figure out where I'm flashing wrong. I was able to successfully flash my nandroid of my stock.
1. In TWRP, I wiped cache/davilk, system, and did a factory reset
2. Then flashed a stable/nightlies version of rukins AOKP jellybean
3. Flashed gapps (also tried w/o flashing this)
4. In the bootloader, I flashed the boot.img in cmd (tried from rom .zip and jellyboot)
5. After phone restarted it was at the stuck at the boot loop "initiating swagger" *sigh*
Maybe its the rom version I'm using? Can you or someone recommend a good rom to start off with along with what kernal I should use?
Click to expand...
Click to collapse
I was able to figure out that I needed to flash a older RUU to be able to flash a custom rom. :laugh:

ninjastic said:
Hello,
I'm new to the OneV phone (CDMA), coming from the awesome Rezound. Starting from stock, I used Hasoons One V all in one kit. I'm unlocked and using TWRP 2.2. I first wiped my phone, installed the Nov 18 aokp primoc unofficial, flashed gapps-jb-4.2-V1-20121117-signed, and then flashed the extracted boot.img from the same rom using the command prompt fastboot flash. I did this process a few times now, but I still get stuck at the loop screen.
I've also tried flashing Jellyboot5.
Anyone have an idea what I am doing wrong? I've flashed roms many times on the Rezound, but it was so much simpler!
Click to expand...
Click to collapse
Did you happen to install an ota update when you still had your stock rom on your phone?
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
ok.... never mind

Can you please elaborate on what you mean by flashing an older RUU? I am stuck at the same screen you speak of. I just got the phone and started flashing away. PRIMOC if that matters. Thanks!

It's to restore your phone to stock ...if you got a bootloop or your phone isn't booting

donhashem.dh said:
It's to restore your phone to stock ...if you got a bootloop or your phone isn't booting
Click to expand...
Click to collapse
Thanks for the reply. You are saying to restore my phone using the back up I created using the recovery then reflash?
Or are you saying to download a factory restore and flash that? From what the op states he needed to flash an older build.
---------- Post added at 09:36 PM ---------- Previous post was at 09:03 PM ----------
so I erased my rom, reflashed with the same image and it now boots into the rom. I am seeing a lot of issues though. The android keyboard has FC numerous times. The home button only seems to function one time, it asks which launcher to use, I select on then it will not work as a home button again. Also the button that shows all open application is opening context menus (the ... you see on some apps) instead of showing recent apps I tried reflashing again with the same results. Thoughts/comments?

are u cdma?

EDIT: Issue I has was unrelated to this thread I believe. If anyone else experiences what I described read this post, I outline everything I did and how to fix it (different gapps file )

mrdally204 said:
Can you please elaborate on what you mean by flashing an older RUU? I am stuck at the same screen you speak of. I just got the phone and started flashing away. PRIMOC if that matters. Thanks!
Click to expand...
Click to collapse
For anyone else reading this (and thx to donhashem below for elaborating) the stock RUU can be found here. Kudos to all who put these links together :good:

Stuck on boot

Hey again..
I was hoping my first custom ROM flashing would be successful considering I've read plenty of threads on how to do it and were pretty careful, but that's not the case.
I tried to give Slim Bean a shot, downloaded Slim-endeavoru-3.1.0-OFFICIAL from their page, and Slim_Gapps along with it.
HBOOT is 1.39, CWM is 5.8.4.0
So I did just as instructed, booted into recovery, wiped data, formatted /system, and then flashed Slim Bean, and Gapps after that was done. When I reboot I just get stuck in the Slim Bean loading screen for a while without anything happening. Tried rebooting and re-flashing a couple of times doing the same procedure - but nothing. Can anyone help me out?

do u flash the boot.img

beanbean50 said:
do u flash the boot.img
Click to expand...
Click to collapse
boot.img is in the Slim-endeavoru-3.1.0-OFFICIAL.zip file already so I thought if I flashed the whole zip it would flash the boot.img along with it, no?

No, you should flash boot.img via your computer.
Search in this forum how to do it.
Unfortunately in developer's tread for the ROM you choose it is not good explained...
Sent from my HTC One X using xda premium

BlueSingA said:
boot.img is in the Slim-endeavoru-3.1.0-OFFICIAL.zip file already so I thought if I flashed the whole zip it would flash the boot.img along with it, no?
Click to expand...
Click to collapse
Someone tell me if I am wrong but the reason you have to flash the boot.img separately is because we have not achieved S-OFF with the HTC One X which gives us unbridled access to everything.
Take the boot.img out of the rom '.zip' and put your phone into fastboot mode. Using the command line and fastboot type 'fastboot flash boot boot.img' obviously for this exact command to work the boot.img needs to be in the same folder as fastboot.exe. Otherwise just type the exact location of it.
Your phone should boot if everything else has been done perfectly.

I'll try that right away.

BlueSingA said:
I'll try that right away.
Click to expand...
Click to collapse
and:
fastboot erase cache
fastboot reboot

beanbean50 said:
and:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Thanks, I always forget to do that myself haha

leonforthewin said:
Someone tell me if I am wrong but the reason you have to flash the boot.img separately is because we have not achieved S-OFF with the HTC One X which gives us unbridled access to everything.
Click to expand...
Click to collapse
correct...!

Okay so I went into fastboot mode, shift-right click on where the fastboot folder on my PC is, opened command prompt (previously pasted the boot.img from Slim Bean to that folder), typed in fastboot flash boot boot.img, fastboot erase cache and fastboot reboot. After reboot I went straight into recovery, flashed the ROM and Gapps, rebooted and now it's stuck HTC's boot screen. :/

With what unzip program you extracted the boot.img?
Try with 7zip...
One more thing- if I remember correct you need to use special boot.img for using 4.1 or 4.2 roms, because they do not work with latest hboots 1.31-39.
Search for such boot.img.
Sent from my HTC One X using xda premium

WinRAR. Okay, gonna try with 7zip.. Also, by extracting the boot.img from the zip you guys mean just to extract it or taking it out of the zip completely? Because I removed it from the zip entirely and flashed it via fastboot only.

WinRAR. Okay, gonna try with 7zip.. Also, by extracting the boot.img from the zip you guys mean just to extract it or taking it out of the zip completely? Because I removed it from the zip entirely and flashed it via fastboot only.
Click to expand...
Click to collapse
You'll be fine with WinRAR. Check back on the forum thread page of the rom you downloaded and look for a md5 sum/number. Google MD5 checker or something to that effect and check whether the MD5 checks up. Could be that a few 1's and 0's are out of place.
My other concern is the rom you have flashed. SlimBean – not tried it, I'm guessing it's a light weight Jelly Bean yeah? Are you sure that you have the correct hboot version for Jelly Bean yet? You can't force update all HOX's to Jelly Bean yet.
EDIT: Missed a bit of your post – I'm not aware of the implications but I and many others have always just copied the boot.img not cut. Obviously if you cut it and it gets zipped back up the MD5 will definitely not match. Save yourself a the head ache and download the rom again to be 100%. Delete the old.

Please see here:
theDroidfanatic said:
Here you go,
It is the NCX AOSP Kernel v13 (Latest) repacked with Seadersn's ramdisk for the new hboots, and has AMAZING Battery life. Download from here and flash in fastboot. Dont forget to flash modules from here
Click to expand...
Click to collapse
Hope this helps you.
Sent from my HTC One X using xda premium

Okay, checked the MD5 sums and they indeed didn't match.. redownloaded again, and it matched since I didn't cut out the boot.img. I'll try again.
@jorjino can you just give me a really short insight (since I bugged you enough, lol) on what is that kernel supposed to do? And do I flash those modules from fastboot as well?

You have to download the newhboot.img from my previous post, rename it to boot.img and flash it via fastboot and cmd menu your PC. That's all. No more downloads or steps.
Sent from my HTC One X using xda premium

Now I'm in a bootloop with the new boot.img... think I'm going to try a different ROM.

jorjino2000 said:
You have to download the newhboot.img from my previous post, rename it to boot.img and flash it via fastboot and cmd menu your PC. That's all. No more downloads or steps.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I don't wish to be rude but did you ignore the fact that the MD5's didn't match?

Last try with this download:
poggus said:
I confirm NCX 217 v13 run very well on Jelly Bam Rom (no need to repack, except for newer hboot you have to repack with this kernel source before flash : http://forum.xda-developers.com/attachment.php?attachmentid=1523418&d=1354254249</p> )
Click to expand...
Click to collapse
Do not forget to rename the file to boot.img.
Sent from my HTC One X using xda premium

BlueSingA said:
Now I'm in a bootloop with the new boot.img... think I'm going to try a different ROM.
Click to expand...
Click to collapse
Can you post me the link to the rom you downloaded? I'm looking on their site and there are no current files in the Jelly Bean HTC One X category. They have old unsupported roms for the HTC One X here.. http://www.slimroms.net/index.php/downloads/all/viewcategory/144-endeavoru.

One X stuck at "HTC ONE X"

ok im truely frustrated after trying to figure this out in past 2 days and reading more than 60 threads/websites.
Problem:
my one x was running 4.0.4 rooted +supre user+CWM, till i got the notification for 4.1 update. i pressed install now and downloaded around 380 MB, during the update phase a red exclamation icon appeared and phone rebooted into 4.0.4.
relocked bootloader, flashed stock recovery and downloaded it again and this time copied the OTA file before pressing install. so i installed and same issue.
uninstalled Avast AV (android) and ran through the same process again, same thing, started up into 4.0.4 again.
unlocked the bootloader, flashed CWM 5.8.4, copied ota file into phone and renamed it to update.zip. ran it from recovery menu and got status 7 error.
downloaded and ran JBFWTOOL21 and followed the instructions, during one of the steps i encountered an error and after restarting the phone i was stock at "HTC One x" with "beatsound" logo at bottom.
NOW NOTHING WORKS
what ive tried so far:
relocked loader and flashed stock recovery and tried Factory Reset, no luck.
unlocked loader and flash CWM and tried wiping cache and wiping disk. nothing.
relocked loader,flashed recovery and ran stock RUU "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed" but it doesnt work, give an error related to version numbers or something.
extracted system.img, boot.img from RUU temp folder ROM.zip and tried to flash but cant flash system.img (918mb). something about not enough HEAP i think.
from the OTA JB zip extracted recovery.img, boot.img and recovery.img and flashed them. nothing.
downloaded "One_X_All-In-One_Kit_v2.1" and tried kernel flash, nothing.
clearing cache via fastboot command also doesnt work
really appreciate any helpful input guys, im really frustrated. thanks

Oh my.. First, stop unlock and relock of bootloader. Do you have a cwm backup from before all this started? Flashing cwm and restoring that backup will get you far.
The first ota attempt failed due to cwm, always return to stock recovery (recovery.img from your cwm backup image) before applying ota update!
Kind Regards
TwinAdk

unfortunately, no. no backup.
since it all started from the official update i didnt make any backups.

Stop trying flash randomly. Run the following command:
fastboot getvar version-main

it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4

woomera said:
it wasnt just random flashing, i starting reading different posts and so tried them all one-by-one to see which works, anyway the output:
version-main: 3.16.415.4
Click to expand...
Click to collapse
Well that's why the older RUU wouldn't work. You have the latest.
You'll need to go to the ROM backups thread and see if you can get a backup and flash its boot.img and restore it from CWM.
Actually, reboot your PC and try to flash system.img and boot.img again. You will probably need to be locked.

but isnt that the boot.img from "OTA_ENDEAVOR_U_JB_45_S_HTC_ARA_3.16.415.4-2.17.415.2_release_304331jrfus698taf4vm1x"?
cause i have already tried it, didnt work. i have the OTA file.

Modified my post. Look up.

i have boot.img from firmware with hboot 3.16 and 3.19, which one to use?
and the system.img is from stock RUU which is "RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.28.415.9_Radio_1.1204.103.14_release_25679_signed", will that work?
the OTA JB is a zip file and doesnt have system.img.

Err.. 1.39?

yes
the firmware included in "JBFWTOOL21" is 1.36 which is used by many to manually upgrade to JB but the firmware inside the OTA file itself is 3.19 which is also the version i updated to since i thought its the reason the update doesnt work.
the Hboot version on my phone is 1.39 at the moment.

Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.

BenPope said:
Hmmm. Looks like you'll have to find a backup in the backups thread and flash it.
Click to expand...
Click to collapse
i dont understand, a backup of what? the system.img?

Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?

sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
I thought about suggesting that too, but I'm new to flashing so I didn't feel confident enough to do it..
But off the top of my head, a custom rom, complete with boot.img and everything should work..
I'm using http://forum.xda-developers.com/showthread.php?t=2013506, it's super great and support all hboot versions.
No guarantees it will work though.
Kind Regards
TwinAdk

sridheepan said:
Something similar happened to me....my phone was bootlooping. I flashed a custom rom and it booted up fine... did u try flashing a custom rom?
Click to expand...
Click to collapse
guess it worth a try even though i'd rather fix the problem in hand in another fashion.
gonna give it a try and post the results.

k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM

woomera said:
i dont understand, a backup of what? the system.img?
Click to expand...
Click to collapse
A nandroid backup, like what Clockworkmod recovery makes.

woomera said:
k so i downloaded the Blade rom and it worked, thanks "TwinAdk".
so now about JB. should i just use "JBFWTOOL21" or better if i do it manually?
and is this the right order to do it manually: ?
-unlock bootloader
-flash CWM
-flash boot.img
-install from zip in CWM
Click to expand...
Click to collapse
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
NOTE: These instructions require that you have one of the ICS hboot versions in order to work (1.12.0000 or lower). If you have one of the new JB hboots 1.28, 1.31 or 1.33 there is currently no way to return to stock until a JB ruu is released for your device.
Click to expand...
Click to collapse
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk

BenPope said:
A nandroid backup, like what Clockworkmod recovery makes.
Click to expand...
Click to collapse
thanks for the clarification
TwinAdk said:
NP, glad it worked! So now you have a phone that can actually boot up and make phone calls.. Not on the stock rom you wanted, but it's better than when you started this thread
From this point on, you can use a "return to stock" thread for the HOX.
1. Make a NANDROID backup via CWM (so you can get back to what you have now!)
2. Move the backup to your computer, to avoid anything happening to it
3. See this tutorial ([TUT] Getting back to stock after flashing custom roms [Noob friendly])
NOTE: The thread says the following in the top:
The "new jb hboots" also refers to 1.39.
I have the 1.39 myself, and i believe i am able to return to stock via my CWM backup of my stock phone, from before i flashed a custom rom the first time.. Is that assumption wrong? Someone more experienced than me to the rescue, please
Kind Regards
TwinAdk
Click to expand...
Click to collapse
i have read the same thing, also "BenPope" mentioned it. so with this version of Hboot (1.39) i cant restore unless its a nandroid backup.
but i dont wanna go back to stock ICS! i wanna finish what i was trying to do in first place, Upgrade to JB.
but no matter what i do i get the "status 7 error". i have tried it with the OTA my phone downloaded and also downloaded it again directly from HTC website via a link from one of the threads in forum.
so status 7 apparently is related to CRC error but how can that be? and what is my option right now to do the upgrade? also bear in mind that before all these happened the normal upgrade process via the "system update" also failed with a red icon error.

[Q] Wifi & Bluetooth issues

I all, I've recently been having issues with my HTC One X and the Wifi and Bluetooth connectivity/range.
I've found that my wireless headphone need to be almost on top of the phone to connect, and the wifi drops to only just connected whilst other phones can sit just beside with full signal.
This has not always been the case, it may have been related to flashing the XM Kernal, but cannot be certain.
Since I have flashed CM10.2 nightly and understand it flashes it's own kernal, but I'm still experiencing these issues.
Can someone help?
Thanks, Joss.

Crazynutt said:
I all, I've recently been having issues with my HTC One X and the Wifi and Bluetooth connectivity/range.
I've found that my wireless headphone need to be almost on top of the phone to connect, and the wifi drops to only just connected whilst other phones can sit just beside with full signal.
This has not always been the case, it may have been related to flashing the XM Kernal, but cannot be certain.
Since I have flashed CM10.2 nightly and understand it flashes it's own kernal, but I'm still experiencing these issues.
Can someone help?
Thanks, Joss.
Click to expand...
Click to collapse
did you flash the modules to go with the kernel?

nogotaclue said:
did you flash the modules to go with the kernel?
Click to expand...
Click to collapse
Ahh, I assume no because I'm not sure that modules are.
I assumed I would simply need to flash the rom file and boot.img & it would do the rest.

Crazynutt said:
Ahh, I assume no because I'm not sure that modules are.
I assumed I would simply need to flash the rom file and boot.img & it would do the rest.
Click to expand...
Click to collapse
I made the same mistake when I first flashed a custom kernel. copy the zip file, that you extracted the boot image from, to your sdcard and install it via recovery

nogotaclue said:
I made the same mistake when I first flashed a custom kernel. copy the zip file, that you extracted the boot image from, to your sdcard and install it via recovery
Click to expand...
Click to collapse
The steps I've taken so far is to flash the boot.img via fastboot.
Installed the CM10.2 .zip via CWM Recovery.
And the appropriate clearing of cache and data etc.
The rom is booting just fine and works a treat, except for the low quality wifi and bluetooth.
Have I missed something else?

Crazynutt said:
The steps I've taken so far is to flash the boot.img via fastboot.
Installed the CM10.2 .zip via CWM Recovery.
And the appropriate clearing of cache and data etc.
The rom is booting just fine and works a treat, except for the low quality wifi and bluetooth.
Have I missed something else?
Click to expand...
Click to collapse
Yes you missed something, as I said above, the zip file that you downloaded from xm, the one you got the boot image from, needs to be installed in recovery as well as the rom zip
Where are the cakes?

nogotaclue said:
Yes you missed something, as I said above, the zip file that you downloaded from xm, the one you got the boot image from, needs to be installed in recovery as well as the rom zip
Where are the cakes?
Click to expand...
Click to collapse
I had XM installed, I thought by flashing CM though I would go back to it's default kernel.
I assume that would be a better setup...doesn't it automatically override XM when I flash the CM rom?
My current kernel version is 3.1.10-cyanogenmod+ [email protected] #1 Wed Aug 21 00:21:13 PDT 2013

Is your one x s-off ?
Where are the cakes?
---------- Post added at 09:47 AM ---------- Previous post was at 09:27 AM ----------
ok I'll assume your phone is s-off. either way do this:- if you have the rom installed already, flash the XM boot.img via fastboot, then reboot into recovery and mount usb storage and copy the entire original XM zip file(not just the boot .img) onto your card. now install the XM zip while in recovery and reboot

nogotaclue said:
Is your one x s-off ?
Where are the cakes?
---------- Post added at 09:47 AM ---------- Previous post was at 09:27 AM ----------
ok I'll assume your phone is s-off. either way do this:- if you have the rom installed already, flash the XM boot.img via fastboot, then reboot into recovery and mount usb storage and copy the entire original XM zip file(not just the boot .img) onto your card. now install the XM zip while in recovery and reboot
Click to expand...
Click to collapse
Phone is s-on...not sure what you mean by cakes.
Can I do the above with s-on or do I need to get s-off first?

Crazynutt said:
Phone is s-on...not sure what you mean by cakes.
Can I do the above with s-on or do I need to get s-off first?
Click to expand...
Click to collapse
sorry it took a while to reply I couldn't type properly for laughing, don't be offended but "where are the cakes" is my signature lol. and yes you can do that with s-on also, although if you are s-on and flash the xm boot image via fastboot installing the rom afterwards should not overwrite the xm boot.img. anyway do what i said, with installed rom, flash xm boot, then install modules in recovery(the xm zip file)

nogotaclue said:
sorry it took a while to reply I couldn't type properly for laughing, don't be offended but "where are the cakes" is my signature lol. and yes you can do that with s-on also, although if you are s-on and flash the xm boot image via fastboot installing the rom afterwards should not overwrite the xm boot.img. anyway do what i said, with installed rom, flash xm boot, then install modules in recovery(the xm zip file)
Click to expand...
Click to collapse
How is that your signature...it's only on some of your replies?
Anyway, I'm pretty sure I followed your instructions correctly, but now CM won't boot...whenever this happened previously, it was because I had not re-flashed the CM boot.img.
Should I have done this, or are you trying to leave the XM boot.img there?

Did u flashed the cm version of xm kernel or the sense version?
Sent from my HTC One X using xda premium

Crazynutt said:
How is that your signature...it's only on some of your replies?
Anyway, I'm pretty sure I followed your instructions correctly, but now CM won't boot...whenever this happened previously, it was because I had not re-flashed the CM boot.img.
Should I have done this, or are you trying to leave the XM boot.img there?
Click to expand...
Click to collapse
its only my sig on phone but not pc.
yes you have to leave the xm, that is the point of flashing the custom kernel, it replaces the cm one. and convictmoody asked a relevant question, did you get the correct xm kernel, the aosp one?

convict_moody said:
Did u flashed the cm version of xm kernel or the sense version?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This time I did the CM version - previously I've had sense on it.
nogotaclue said:
its only my sig on phone but not pc.
yes you have to leave the xm, that is the point of flashing the custom kernel, it replaces the cm one. and convictmoody asked a relevant question, did you get the correct xm kernel, the aosp one?
Click to expand...
Click to collapse
Okay, got it now
And...I'm still stuck - not passing the CM boot screen.

Crazynutt said:
This time I did the CM version - previously I've had sense on it.
Okay, got it now
And...I'm still stuck - not passing the CM boot screen.
Click to expand...
Click to collapse
ok what recovery are you using?

ClockworkMod Recovery v5.8.4.0

Crazynutt said:
ClockworkMod Recovery v5.8.4.0
Click to expand...
Click to collapse
ok from the beginning, download Xm kernel aosp version, copy the boot image from the downloaded zip into your fastboot folder.
next go into recovery and format these four, system, data, cache and sdcard.
now mount usb storage and copy the the cm rom.zip onto sdcard and then the whole xm zip file that you downloaded.
now boot into boot loader and do these exactly without the quotes, and when you press enter after each command make sure it says "okay" so you know it actually worked. "fastboot erase cache" then "fastboot flash boot boot.img" then again "fastboot erase cache".
now reboot recovery and install the rom but DO NOT REBOOT.
now clear dalvik
next, while still in recovery, install the xm zip file that you copied over with the rom.
again clear dalvik and then reboot.

nogotaclue said:
ok from the beginning, download Xm kernel aosp version, copy the boot image from the downloaded zip into your fastboot folder.
next go into recovery and format these four, system, data, cache and sdcard.
now mount usb storage and copy the the cm rom.zip onto sdcard and then the whole xm zip file that you downloaded.
now boot into boot loader and do these exactly without the quotes, and when you press enter after each command make sure it says "okay" so you know it actually worked. "fastboot erase cache" then "fastboot flash boot boot.img" then again "fastboot erase cache".
now reboot recovery and install the rom but DO NOT REBOOT.
now clear dalvik
next, while still in recovery, install the xm zip file that you copied over with the rom.
again clear dalvik and then reboot.
Click to expand...
Click to collapse
Alright, did all that...word for word.
Still stuck on CM boot screen.

Crazynutt said:
Alright, did all that...word for word.
Still stuck on CM boot screen.
Click to expand...
Click to collapse
you do know it takes a few minutes on first boot, sometimes 5 or 6 minutes?

nogotaclue said:
you do know it takes a few minutes on first boot, sometimes 5 or 6 minutes?
Click to expand...
Click to collapse
Okay, I've been waiting about 5 mins, but I'll wait patiently for a bit more
Thanks for your help by the way.

HTC One X doesn't want to boot

Hi guys,
I'm new in this section because I had an HTC One SV, but today I receive One X. Now... I have a very serious problem: after I flashed a custom kernel, HTC doesn't seems to boot, but it it's stuck in the white screen with the green HTC word. I tried to flash another kernel and stock kernel too, but this doesn't seems to be useful... Please help me!!! (I'm not S-Off)

TheSura said:
Hi guys,
I'm new in this section because I had an HTC One SV, but today I receive One X. Now... I have a very serious problem: after I flashed a custom kernel, HTC doesn't seems to boot, but it it's stuck in the white screen with the green HTC word. I tried to flash another kernel and stock kernel too, but this doesn't seems to be useful... Please help me!!! (I'm not S-Off)
Click to expand...
Click to collapse
flash the boot.img via fastboot you must take it from modules archive and paste it on your fastboot folder then run from cmd fastboot flash boot boot.img and restart

Thant said:
flash the boot.img via fastboot you must take it from modules archive and paste it on your fastboot folder then run from cmd fastboot flash boot boot.img and restart
Click to expand...
Click to collapse
I tried many times and finally, my HTC booted until the lockscreen. If I tried to unlock, it returned that White screen, but my PC recognized it and I could copy Viper ROM inside it. So, I flashed the ROM and now it work. But if I want back to stock? I don't have any nandroid backup and; I don't know why, I can't do S-Off: using rumrunner, it does all the procedure, but it stucks on pouring: it arrives to pouring (8) and then it says me to reboot and retry. So, what can I do?

TheSura said:
I tried many times and finally, my HTC booted until the lockscreen. If I tried to unlock, it returned that White screen, but my PC recognized it and I could copy Viper ROM inside it. So, I flashed the ROM and now it work. But if I want back to stock? I don't have any nandroid backup and; I don't know why, I can't do S-Off: using rumrunner, it does all the procedure, but it stucks on pouring: it arrives to pouring (8) and then it says me to reboot and retry. So, what can I do?
Click to expand...
Click to collapse
No S-OFF for ONE X international Endeavoru, your only way is restore nandroid backup find it from somewhere

Thant said:
No S-OFF for ONE X international Endeavoru, your only way is restore nandroid backup find it from somewhere
Click to expand...
Click to collapse
Well, I understood. Thank you so much! I've found a nandroid yet, but I'm having problems with the process "HTC.opensense.social" or something similar because it stopped improperly. Sorry if I do so many questions, but I'm n00b <_< Thank you

TheSura said:
Well, I understood. Thank you so much! I've found a nandroid yet, but I'm having problems with the process "HTC.opensense.social" or something similar because it stopped improperly. Sorry if I do so many questions, but I'm n00b <_< Thank you
Click to expand...
Click to collapse
da a full wipe(system,data,cache and davlik cache) and don't forget to flash the boot.img from nandroid backup

Thant said:
da a full wipe(system,data,cache and davlik cache) and don't forget to flash the boot.img from nandroid backup
Click to expand...
Click to collapse
I did yet before restoring nandroid! But I didn't flash the boot.img because after restoring, I flashed a new kernel from recovery and from fastboot. The cause could be the custom kernel?

TheSura said:
I did yet before restoring nandroid! But I didn't flash the boot.img because after restoring, I flashed a new kernel from recovery and from fastboot. The cause could be the custom kernel?
Click to expand...
Click to collapse
are you flash the boot.img from the kernel?

Thant said:
are you flash the boot.img from the kernel?
Click to expand...
Click to collapse
Yes, I did

thesura said:
yes, i did
Click to expand...
Click to collapse
@TheSura
Sorry, Wich kernel do you try to flash

Thant said:
@TheSura
Sorry, Wich kernel do you try to flash
Click to expand...
Click to collapse
I flashed this kernel: http://forum.xda-developers.com/showthread.php?t=2586808
Now I want to try another because it has overclock to 1.7: http://forum.xda-developers.com/showthread.php?t=2138586
Is this good?
Ps: doesn't matter the error: I'm going to return to viper, so don't worry

TheSura said:
I flashed this kernel: http://forum.xda-developers.com/showthread.php?t=2586808
Now I want to try another because it has overclock to 1.7: http://forum.xda-developers.com/showthread.php?t=2138586
Is this good?
Ps: doesn't matter the error: I'm going to return to viper, so don't worry
Click to expand...
Click to collapse
in this aroma flasher have 6 kernels you must to flash the coerct boot.img from modules archive

Thant said:
in this aroma flasher have 6 kernels you must to flash the coerct boot.img from modules archive
Click to expand...
Click to collapse
Understood! Thank you very much!