[Q] no working rom; acces to SD from bootloader? - HTC One X

I have tried to install CM9 to my One X, but appearantly something went wrong (after installing it tries to boot, but doesn't pass the nicely done/animated 'loading' screen).
is there a way to acces the SD-card from the bootloader (which still works, unlocked etc). So i can copy over the .zip again incase that was faulty.
Also; when going into recovery from the bootloader it just reboots the phone (go into CM9 again). so that wont work :/
any thoughts?
edit1:
oh yeah:
C:\Users\username\Desktop\HTC\onexroot>fastboot flash recovery-clockwork-touch-5.8.3.1-endeavoru.img
unknown partition 'recovery-clockwork-touch-5.8.3.1-endeavoru.img'
error: cannot determine image filename for 'recovery-clockwork-touch-5.8.3.1-end
eavoru.img'
wut? ^^

try using fastboot erase cache first
might fix everything
this command is wrong
C:\Users\username\Desktop\HTC\onexroot>fastboot flash recovery-clockwork-touch-5.8.3.1-endeavoru.img
it should be fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
and you can use adb push to send files to your phone

Yeah, noticed the command was wrong. Fixed that, got a working recovery now.
However, clearing the cache didn't fix the issue. My 'guess' is that the CM9 .zip is just faulty.
Ill look into that adb push thing now, to find out how to push the img to the phone.
TY so far

might want to check the md5sum of the file you downloaded
it used to give me trouble back then. Some internet issues corrupted the file.
Hmm, btw, did you flash the kernel?
I mean the cm9 specific kernel?

My guess is i did not flash the kernel
im still quite new to all this, have rooted/custom rommed my desire before; but that was all 1 click
How does one update the kernel and what is the main purpose?

U need to extract file "boot.img" from the rom ZIP. put it in your fastboot folder.
Then use fastboot Command:
'fastboot flash boot boot.img'
erase Cache recommended before first boot
Edit: oh yeah ... and the purpose is, that the Rom needs the appropriate kernel to run. Its like the heart of the System.
Sent from my HTC One X using xda premium

IceDustbin said:
My guess is i did not flash the kernel
im still quite new to all this, have rooted/custom rommed my desire before; but that was all 1 click
How does one update the kernel and what is the main purpose?
Click to expand...
Click to collapse
devs are usually supplying both the rom and the kernel for the hox.
There is an issue that prevents the kernel to be flashed from CWR so you have to flash it yourself.
use flashboot boot kernel name.img on fastboot
kernel is the bridge between hardware and software or something like that

fredfb said:
devs are usually supplying both the rom and the kernel for the hox.
There is an issue that prevents the kernel to be flashed from CWR so you have to flash it yourself.
use flashboot boot kernel name.img on fastboot
kernel is the bridge between hardware and software or something like that
Click to expand...
Click to collapse
The issue is caused by the device being s-on.
The command is fastboot flash boot boot.IMG after do fastboot erase cache.
But yes the kernel sits between applications and hardware.
Sent from my HTC One X using xda premium

Fixed the problem
i DID update the kernel; so that was fine (just didn't know the boot.img was in fact the kernel)
Fixed the recovery after which i could access the SDcard to update the CM9 zip file.
This time it installed fine and despite some known bugs seems to do the trick.
Ty for all your help really needed a push in the right direction ^^
Ice

Related

Question regarding kernel

Ok... this is weirdest bug i ever seen.
After wipe all data (all thing) up new rom eg. paranoid, AOKP, myOneV... all of them.
1/Stock kernel is default, but modder need uploaded new kernel to run ether rom.
2/Flash new rom needed...yeah we got new kernel at first time... but when reboot phone.... what the f.... auto back-up to default kernel??
IE: AOKP, myOneV, CM10, ... need newest kernel to run, done... but only first time, the second boot is bricked....
=>Solve this for me plzzzz
My idea: why we don't cook new kernel vs new rom when release new version?
u need to do fastboot flash recovery (nameofrecovery). img
u must have done fastboot recovery (nameofrecovery). img
Sent from my One V
paarthdesai said:
u need to do fastboot flash recovery (nameofrecovery). img
u must have done fastboot recovery (nameofrecovery). img
Sent from my One V
Click to expand...
Click to collapse
"Flash new rom needed...yeah we got new kernel at first time" i know so do i ... that's my problem, flash done 1st run is ok but reboot in 2nd is bricked. So i MUST flash recovery when 2nd and 3rd and 4th when reboot... fk... i my phone gonna R.I.P
i ain't understanding a **** u tokn dude
Sent from my One V
paarthdesai said:
i ain't understanding a **** u tokn dude
Sent from my One V
Click to expand...
Click to collapse
lemme explain what did he say, he got prob when up new rom, the rom needed flash boot (new kernel), he know about it. The 1st is flash, boot to phone, he can see new kernel in setting then use whatever like overclock, undervolt, install app,... then he make a reboot (restart) go to setting menu, he regconize the original kernel is back, overclock is disable, same at undervolt and bricked phone if original kernel no compatible with that rom. That's the PROBLEM.
kenintel said:
lemme explain what did he say, he got prob when up new rom, the rom needed flash boot (new kernel), he know about it. The 1st is flash, boot to phone, he can see new kernel in setting then use whatever like overclock, undervolt, install app,... Then he make a reboot (restart) go to setting menu, he regconize the original kernel is back, overclock is disable, same at undervolt and bricked phone if original kernel no compatible with that rom. That's the problem.
Click to expand...
Click to collapse
bootloop is not bricked phone!!!
If you had a bricked phone you will never ever be able to power up your phone!
1ceb0x said:
bootloop is not bricked phone!!!
If you had a bricked phone you will never ever be able to power up your phone!
Click to expand...
Click to collapse
err my bad, so how to solve this?
I mean default kernel loop when 2nd reboot...
Do this
Go to fast boot
Open cmd
Fastboot flashboot boot.img
Now don't restart go to the recovery and wrote all cache and then flask which ever roms u want, believe me this will work ....
Sent from my One V using xda app-developers app
cybervibin said:
Do this
Go to fast boot
Open cmd
Fastboot flashboot boot.img
Now don't restart go to the recovery and wrote all cache and then flask which ever roms u want, believe me this will work ....
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
1/Go to fast boot
Open cmd
Fastboot flashboot boot.img <---- which boot.img? "stock kernel"
When flashboot device MUST restart, i cant resist that...
2/Now don't restart go to the recovery and wrote all cache
Wipe all data or wipe all cache? dalvik cache? can u explain....
See when u go.to a rom page there will be a link for kernel......and take the kernel and don't restart our it will be stuck in boot loop....
No go to recovery with out restarting....wipe all data if a new rom...
And then download the link and
Sent from my One V using xda app-developers app
i think they are using hassoon tool to flash the kernel, because that script will automatically reboot the phone after the kernel is flashed .
1.You need to first, take THE kernel for the RESPECTIVE ROM
2. Rename it to boot.img
3. You have to have installed the Android SDK + the platform tools to be able to take advantage of fastboot
4. Reboot your phone into bootloader.
5. Connect your phone to your PC.
6. Press start, enter RUN and type cmd. Press enter.
7. Type your path where your sdk is installed (i.e CD C:\Program Files\Android\android-sdk\platform-tools\)
8. Put the boot.img into the platform-tools folder
9. Now go back to CMD use "fastboot flash boot boot.img" without the quotes.
10. It will send a message like "sending boot.img.... done... writing boot img.... done.... elapsed x seconds).
11. Reboot Recovery from bootloader.
12. Wipe everything and then flash your rom.
13. Reboot and that's it.
As simple as that. If you don't know how to use android sdk or you don't have it installed, simple use the search bar and type android sdk tutorial.
thanhi said:
Ok... this is weirdest bug i ever seen.
After wipe all data (all thing) up new rom eg. paranoid, AOKP, myOneV... all of them.
1/Stock kernel is default, but modder need uploaded new kernel to run ether rom.
2/Flash new rom needed...yeah we got new kernel at first time... but when reboot phone.... what the f.... auto back-up to default kernel??
IE: AOKP, myOneV, CM10, ... need newest kernel to run, done... but only first time, the second boot is bricked....
=>Solve this for me plzzzz
My idea: why we don't cook new kernel vs new rom when release new version?
Click to expand...
Click to collapse
I edited your thread title. In the future, please follow forum rules and include a relevant and descriptive thread title. Using vulgarity is unnecessary, offensive, and not welcome on XDA.

Both CM9/CM10 hangs at boot.

My procedure in chronological order:
Flashed recovery TWRP 2.3
Wiped everything possible in the wipe-tab
Installed CM9/10 from zip on SD-card (zip contains META-INF, system and boot.img)
Flashed boot.img from the zip file CM9/10
Issued the command fastboot erase cache
Unplugged cable and reboot
What happens is that I am stuck at the HTC booting screen. I have been here for about 30-40 minutes. If I try any adb shell command I receive this error: - exec '/system/bin/sh' failed: No such file or directory (2) -. Clearly, something is not right here. I will not speculate because I lack the knowledge to do so. Any help is appreciated because I have been phone-less for a day now and it is getting irritating. Thanks!
Seems you did everything correctly.
Try to flash via ClockWorkMod recovery.
Sent from my HTC One X
TToivanen said:
Seems you did everything correctly.
Try to flash via ClockWorkMod recovery.
Click to expand...
Click to collapse
I just did the same procedure as before but with clockworkmod instead. Still hung at booting screen. I get the same error as before. Is root access a must? I have not done any exploit, only thing I have done is unlocked my boot loader at HTCDev.
zettez said:
I just did the same procedure as before but with clockworkmod instead. Still hung at booting screen. I get the same error as before. Is root access a must? I have not done any exploit, only thing I have done is unlocked my boot loader at HTCDev.
Click to expand...
Click to collapse
Root should not be needed since most roms are rooted by default.
Did you flash gapps?
TToivanen said:
Root should not be needed since most roms are rooted by default.
Did you flash gapps?
Click to expand...
Click to collapse
No, I have not. Maybe I should give it a try? Or is it not required? Should I not be able to start the phone without any gapps?
Do you by chance have any ROM you can recommend that works so I could try it out and exclude problems? Would very like to know if it is my phone or ROM that is buggy.
It should boot without them, but better to give it a try.
Ironically, I've been using CM10 for more than a month now and never had any problems booting.
Sent from my HTC One X
If you have an hboot newer than 1.12 you need a different boot.img, check the bottom if the ROM OP.
TToivanen said:
It should boot without them, but better to give it a try.
Ironically, I've been using CM10 for more than a month now and never had any problems booting.
Click to expand...
Click to collapse
Would you mind telling me which CM10 build you are using and which boot.img you flashed?
BenPope said:
If you have an hboot newer than 1.12 you need a different boot.img, check the bottom if the ROM OP.
Click to expand...
Click to collapse
I have hboot 1.3 or something I think. I downloaded the different builds at get.cm. Where can I get the boot.img if not the one in the zip file? Do you mean whichever thread that CM have posted themselves here on xda? Would you mind sending a link to where I can find the boot.img?
zettez said:
I have hboot 1.3 or something I think. I downloaded the different builds at get.cm. Where can I get the boot.img if not the one in the zip file? Do you mean whichever thread that CM have posted themselves here on xda? Would you mind sending a link to where I can find the boot.img?
Click to expand...
Click to collapse
Normally it would be found in the bottom of CM10 threads OP but the link is down.
Here you go:
http://forum.xda-developers.com/showpost.php?p=34829297&postcount=9173
Remember to repack it with the one found in zip. Repack tool stickied on android development forum.
Sent from my HTC One X
TToivanen said:
Normally it would be found in the bottom of CM10 threads OP but the link is down.
Here you go:
http://forum.xda-developers.com/showpost.php?p=34829297&postcount=9173
Remember to repack it with the one found in zip. Repack tool stickied on android development forum.
Click to expand...
Click to collapse
Thanks, but still a no go. What I did was take the modified boot from your link and the boot.img from the zip file, do the online converter as stickied on the forum, then did the procedure all again but this time I flashed the new boot.img I got from combining the old and the new boot.img. Still hangs at boot. Very annoying. I am currently using a modified stock ROM and I dislike it very much.
Hey,
I have exactly the same issue. I've unlocked my bootloader using the method as specified by htcdev.com. Then I flashed the newest CWM recovery. But if I flash any ROM, I'm stuck at its boot animation. However if I then unzip the boot.img from the ROM, and flash that (fastboot flash boot boot.img), my phone won't boot past HTC screen. Even erasing the cache didn't help (fastboot erase cache).
I've restored the stock ROM using the RUU, however during the process something went wrong and it formatted my sd-card. So I'm stuck with the stock ROM, without any applications or data.
Can anybody help me flash CM10?
My Hboot version is 1.36.0000
And I'm trying to flash the cm-10-20121210-NIGHTLY-endeavoru.zip ROM.
Thanks in advance
Han
irundaia said:
Hey,
I have exactly the same issue. I've unlocked my bootloader using the method as specified by htcdev.com. Then I flashed the newest CWM recovery. But if I flash any ROM, I'm stuck at its boot animation. However if I then unzip the boot.img from the ROM, and flash that (fastboot flash boot boot.img), my phone won't boot past HTC screen. Even erasing the cache didn't help (fastboot erase cache).
I've restored the stock ROM using the RUU, however during the process something went wrong and it formatted my sd-card. So I'm stuck with the stock ROM, without any applications or data.
Can anybody help me flash CM10?
My Hboot version is 1.36.0000
And I'm trying to flash the cm-10-20121210-NIGHTLY-endeavoru.zip ROM.
Thanks in advance
Han
Click to expand...
Click to collapse
You cannot use the boot.img that comes with the zip out of the box if you have Hboot 1.36. What you have to do is repack it, taking the boot.img from the zip file and then a modified boot.img here http://forum.xda-developers.com/show...postcount=9173 (thanks TToivanen), then as I understood it, repack it for instance here http://forum.xda-developers.com/showthread.php?t=1815607, download the repacked boot.img and flash that.
With that said, I could not get it running but it might be something wrong with my phone. Please try this out and tell me if it works or not so I may start to conclude where the error lies.
zettez said:
Thanks, but still a no go. What I did was take the modified boot from your link and the boot.img from the zip file, do the online converter as stickied on the forum, then did the procedure all again but this time I flashed the new boot.img I got from combining the old and the new boot.img. Still hangs at boot. Very annoying. I am currently using a modified stock ROM and I dislike it very much.
Click to expand...
Click to collapse
Sorry, but all I can say is that you did a mistake at some point.
Try installing again with full wipe and remember to wipe cache and dalvik.
You are referring to the official CM10 and not Trip's or any other builds right?
TToivanen said:
Sorry, but all I can say is that you did a mistake at some point.
Try installing again with full wipe and remember to wipe cache and dalvik.
You are referring to the official CM10 and not Trip's or any other builds right?
Click to expand...
Click to collapse
Will try again. I got the latest build from http://get.cm/?device=endeavoru. Will try cm-10-20121213-NIGHTLY-endeavoru.zip as it came out today.
zettez said:
You cannot use the boot.img that comes with the zip out of the box if you have Hboot 1.36. What you have to do is repack it, taking the boot.img from the zip file and then a modified boot.img here http://forum.xda-developers.com/show...postcount=9173 (thanks TToivanen), then as I understood it, repack it for instance here http://forum.xda-developers.com/showthread.php?t=1815607, download the repacked boot.img and flash that.
With that said, I could not get it running but it might be something wrong with my phone. Please try this out and tell me if it works or not so I may start to conclude where the error lies.
Click to expand...
Click to collapse
I did that and now my phone is still stuck on the HTC screen. Trying to restore my backup of the stock ROM atm.
---------- Post added at 04:35 PM ---------- Previous post was at 04:30 PM ----------
hmm the backup was useless... Off to the RUU it is....
irundaia said:
[/COLOR]hmm the backup was useless... Off to the RUU it is....
Click to expand...
Click to collapse
You flashed the stock boot.img before restoring?
irundaia said:
I did that and now my phone is still stuck on the HTC screen. Trying to restore my backup of the stock ROM atm.
Click to expand...
Click to collapse
I see, then it is not only I who have this problem.
And a heads up, if the backup would go wrong, I currently use this ROM and it works pretty good if you want stock or cannot be arsed to get a root exploit for the stock ROM. http://forum.xda-developers.com/showthread.php?t=2035203.
Would be great if anyone has any ideas why irundaia and I cannot make CM10 work?
TToivanen said:
You flashed the stock boot.img before restoring?
Click to expand...
Click to collapse
You're right, I forgot to do that. I does boot now, still at a loss though. Can't we downgrade our Hboot to a version in which we know that CM can be flashed?
Kinda out of ideas here...
Can you confirm that the boot.img flashes ok? (should say OKAY)
Also confirm that you have endeavoru and not evita.

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.

[Q] Will installing new ROM wipe X-Parts CWM?

Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Artemicion said:
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Click to expand...
Click to collapse
Yes, if you wipe the system partition there will be no more CWM. For CM10, you need to flash a custom kernel for it to work. This custom kernel will usually come with a CWM recovery so it will not be wiped when you flash a new ROM.
僕のLT18iから送られてきた
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Artemicion said:
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Click to expand...
Click to collapse
Is your bootloader unlocked?
And yes you will have to flash GB ftf using flashtool
Sent from my LT18i
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Artemicion said:
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Click to expand...
Click to collapse
If I am not mistaken the kernel boot img should be inside the ROM zip. Check the ROM zip. Just flash the boot img using fastboot, boot into CWM recovery and flash ROM & gapps.
僕のLT18iから送られてきた
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Artemicion said:
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
Click to expand...
Click to collapse
You don't need to add -i 0xfce to the command. Just type fastboot flash boot <name of boot image>.img
僕のLT18iから送られてきた
tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Thanks, I'll give that a go, not going to be able to try for a few days now, but will. FYI, I took the line of code I was trying directly from the Cyanogenmod wiki for Anzu
tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Artemicion said:
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Click to expand...
Click to collapse
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
popthosegaskets said:
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Looks to just be "boot.img" to me, no spaces or anything.
Have you tried flashtool?
Sent from my LT18i using xda premium
tangosierra_ said:
Have you tried flashtool?
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
No, guess I'll try that next. As I remember, that's what I used to flash in order to root it ages ago. Thanks

[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.

Categories

Resources