anyone else experiencing problems installing nightlies 11 and 10 of november?
i install those roms using cyan delta, and when its done, it restarts my cell, shows the htc logo, and than nothing, it keeps restarting, no cm logo shows up
litmeister said:
anyone else experiencing problems installing nightlies 11 and 10 of november?
i install those roms using cyan delta, and when its done, it restarts my cell, shows the htc logo, and than nothing, it keeps restarting, no cm logo shows up
Click to expand...
Click to collapse
Did you flash the boot.img separately via fastboot? if you are on the latest hboot, i think you need to do this, as the device is s-on.
If you are still able to get to bootloader you can navigate to the cmupdater folder (using adb shell to find it) on the sdcard and reflash it manually.
codeprimate said:
Did you flash the boot.img separately via fastboot? if you are on the latest hboot, i think you need to do this, as the device is s-on.
If you are still able to get to bootloader you can navigate to the cmupdater folder (using adb shell to find it) on the sdcard and reflash it manually.
Click to expand...
Click to collapse
when i originally installed cm10, i was on 11/03, and i updated daily via cyan delta. i didnt have to flash a boot from fastboot. it was everything ok, until the last 2 updates
11/10 gave me boot loop using cyandelta.. Had to do a factory reset in twrp then manually flash boot .. Working fine now.. Going to use flash img guide next time
Sent from my One X using xda app-developers app
litmeister said:
when i originally installed cm10, i was on 11/03, and i updated daily via cyan delta. i didnt have to flash a boot from fastboot. it was everything ok, until the last 2 updates
Click to expand...
Click to collapse
I don't think cyandelta is writing to /boot (with the 1.14 hboot) so if you are upgrading by cyandelta, I think you are not writing the kernel, just the rest of the OS. This will work for some changes, but will break with some. The next time you try a CyanDelta upgrade, check the krenel version [Settings] -> [about phone] -> kernel version. I think you'll find (if you have the 1.14 hboot) that the kernel is older than the nightly/experimental/stable CM10 version you installed. If you have an older hboot (1.09 for example) this is a non-issue, as you are able to write to /boot .
I may be wrong, but I think this may be the case. If you are having issues with the newer nightlies, check your hboot. If it is 1.14, back up your apps, boot into recovery and get the zip folder from /sdcard/cmupdater/ then you can extract the boot.img. Then you can flash this onto the boot partition manually ("fastboot flash boot boot.img").
If you have an earlier hboot, ignore my ramblings, and continue about your business.
codeprimate said:
I don't think cyandelta is writing to /boot (with the 1.14 hboot) so if you are upgrading by cyandelta, I think you are not writing the kernel, just the rest of the OS. This will work for some changes, but will break with some. The next time you try a CyanDelta upgrade, check the krenel version [Settings] -> [about phone] -> kernel version. I think you'll find (if you have the 1.14 hboot) that the kernel is older than the nightly/experimental/stable CM10 version you installed. If you have an older hboot (1.09 for example) this is a non-issue, as you are able to write to /boot .
I may be wrong, but I think this may be the case. If you are having issues with the newer nightlies, check your hboot. If it is 1.14, back up your apps, boot into recovery and get the zip folder from /sdcard/cmupdater/ then you can extract the boot.img. Then you can flash this onto the boot partition manually ("fastboot flash boot boot.img").
If you have an earlier hboot, ignore my ramblings, and continue about your business.
Click to expand...
Click to collapse
and how do i extract the boot.img?
litmeister said:
and how do i extract the boot.img?
Click to expand...
Click to collapse
open zip up in winrar or 7-zip and extract the boot.img, no need to unzip and rezip the whole thing
litmeister said:
and how do i extract the boot.img?
Click to expand...
Click to collapse
i have hboot 1.14, i tried flashing the boot.img but it didnt work. no problem while flashing but when i open my cel it still on the same cm version
litmeister said:
i have hboot 1.14, i tried flashing the boot.img but it didnt work. no problem while flashing but when i open my cel it still on the same cm version
Click to expand...
Click to collapse
there were some people that had some issues with the nightlies around this time, maybe you could wipe system/cache/dalvik and install CM 10.0 stable from recovery (flashing boot.img manually). Make sure you back up anything on the system folder that you'll need.
Related
There is a guide on how to flash a new radio on the One S, but its outdated and obsolete.
While we still dont have S-OFF yet, there is a trick that lets you flash radio images.
Requirements.
The latest TWRP recovery image. Available here.
Grab the latest US or EU radio here and copy it to your SD Card. (adb push filename.zip /sdcard/radio.zip) Click the changelog-button to see which radio's are US and EU.
Lets get flashing
Reboot your device into the bootloader.
Code:
adb reboot bootloader
Use fastboot to boot up into recovery.
Code:
fastboot boot openrecovery-twrp-2.3.1.0-ville.img
You will boot directly into recovery from the recovery image, and no restrictions apply. Now simply flash the radio.zip file that you pushed over earlier, and you're all set!
Enjoy!
Credits to xkonni for the tip!
Is it really bad if I flash a EU radio on my TMOBUS device? I have done so 24hrs ago and notice very fast speeds and good signal strength. I don't get why there is a difference.
Closed Source Project said:
Is it really bad if I flash a EU radio on my TMOBUS device? I have done so 24hrs ago and notice very fast speeds and good signal strength. I don't get why there is a difference.
Click to expand...
Click to collapse
i would like to know the answer to this also
No it works great on my tmobile one s no problems here
sent from a guy living in a van down by the river
Untouchab1e said:
There is a guide on how to flash a new radio on the One S, but its outdated and obsolete.
While we still dont have S-OFF yet, there is a trick that lets you flash radio images.
Requirements.
The latest clockwork recovery image. Available here. Make sure you get the latest version for the Ville. (released on or after 29-apr-2012).
Grab the latest US or EU radio here and copy it to your SD Card. (adb push filename.zip /sdcard/radio.zip) Click the changelog-button to see which radio's are US and EU.
Lets get flashing
Reboot your device into the bootloader.
Code:
adb reboot bootloader
Use fastboot to boot up into recovery.
Code:
fastboot boot recovery-clockwork-5.5.0.4-ville.img
You will boot directly into recovery from the recovery image, and no restrictions apply. Now simply flash the radio.zip file that you pushed over earlier, and you're all set!
Enjoy!
Credits to xkonni for the tip!
Click to expand...
Click to collapse
got the same result by just rebooting into bootloader, then choosing fastboot>recovery.....then chose radio.zip i placed on "sdcard"...never having to plug phone into PC
On leedroid without the radio it gets about 12mb but with this radio i get 10mb, when i load the same site, this radio loads about 2seconds faster..tmobUS thanx btw
I too just flashed the .zip from Clockwork Recovery from my T-Mobile US phone for the EU radio. Working just fine.
I'm getting an error when I enter stock recovery that it can't find /sdcard cause the file doesn't exist... a little help please
ralph96gt said:
I'm getting an error when I enter stock recovery that it can't find /sdcard cause the file doesn't exist... a little help please
Click to expand...
Click to collapse
Had the exact same problem as you.
I just flashed the recovery with CWM recovery image. The one in this topic didn't work for me cause it wouldn't mount the /sdcard either. I used a different version.
Then I just installed the radio.zip from this topic.
So if I have the last CWM, just I have to put the zip to the SD, and flash it from recovery?
Edit: The radio I have now is the 0.15.31501S.19_2_10.13.31501S.06L
cualla84 said:
So if I have the last CWM, just I have to put the zip to the SD, and flash it from recovery?
Edit: The radio I have now is the 0.15.31501S.19_2_10.13.31501S.06L
Click to expand...
Click to collapse
From what Ive been told, and what I did, was to boot directly into the latest recovery image. Meaning, you dont flash the recovery image first, you simply fastboot boot into it, then you flash the radio.zip from there.
Again, make sure you pick the newest version of the recovery image.
Untouchab1e said:
From what Ive been told, and what I did, was to boot directly into the latest recovery image. Meaning, you dont flash the recovery image first, you simply fastboot boot into it, then you flash the radio.zip from there.
Again, make sure you pick the newest version of the recovery image.
Click to expand...
Click to collapse
Thank you! I have the CWM 5.8.3.1. I have to wipe before flashing?
cualla84 said:
Thank you! I have the CWM 5.8.3.1. I have to wipe before flashing?
Click to expand...
Click to collapse
No, you dont have to wipe data before flashing a new radio.
Untouchab1e said:
No, you dont have to wipe data before flashing a new radio.
Click to expand...
Click to collapse
Thank you very much! I'll make a nandroid my rom, and flash radio and alpha8 of CM9
cualla84 said:
Thank you very much! I'll make a nandroid my rom, and flash radio and alpha8 of CM9
Click to expand...
Click to collapse
Sounds like a good plan! Enjoy Alpha8. Nightly builds are available too (check signature)
Untouchab1e said:
Sounds like a good plan! Enjoy Alpha8. Nightly builds are available too (check signature)
Click to expand...
Click to collapse
Better then flash the nightly? What improvements have regarding alpha8? I can´t see the features!
cualla84 said:
Better then flash the nightly? What improvements have regarding alpha8? I can´t see the features!
Click to expand...
Click to collapse
No Ville-specific improvements, just the latest CM9 commits. Its basically the exact same ROM, just with the latest CM9 improvements.
Thanks Untouchab1e!
Untouchab1e said:
No Ville-specific improvements, just the latest CM9 commits. Its basically the exact same ROM, just with the latest CM9 improvements.
Click to expand...
Click to collapse
OK! I will charge the battery and I get to it!
Flashed 1.78 EU radio to stock tmous and I'm getting zero issues and excellent battery life so far. Thx
Sent from my HTC VLE_U using xda premium
flash directly from cwm?
having already unlocked, root and flashed the latest cwm, can't i just move the radio.zip file to the phone and flash directly in cwm instead of all commands?
Hi i'm new to the att htc one x, just rooted, and installed twrp... then flash cleanrom5. I also noticed clean has a kernel, i did not see an install guide, but i've installed kernels before on my captivate. So what i'm wondering if it's as easy as....
1. place kernel on phone storage
2. reboot into recovery
3. install kernel from recovery
4. reboot
If there anything i am missing or if i am completely off could someone please help me out with this?
Thank you :good:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
redpoint73 said:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
Click to expand...
Click to collapse
Would you mind walking me through that process?
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
cannon19932006 said:
Would you mind walking me through that process?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
absolutelygrim said:
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
Click to expand...
Click to collapse
I don't see anything about flashing kernels in that thread.
cannon19932006 said:
I don't see anything about flashing kernels in that thread.
Click to expand...
Click to collapse
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery. fastboot flash method http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
edit: btw, what exploit did you use to achieve root? Was it the x-factor exploit?
cannon19932006 said:
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
Click to expand...
Click to collapse
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
redpoint73 said:
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
Click to expand...
Click to collapse
i used x-factor yes, and yes it's 1.14, thank you both for the help.
cannon19932006 said:
i used x-factor yes, and yes it's 1.14, thank you both for the help.
Click to expand...
Click to collapse
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
absolutelygrim said:
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
Click to expand...
Click to collapse
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
cannon19932006 said:
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
Click to expand...
Click to collapse
Well, If cleanROM is using the same Kernel as stock, then you got lucky. If they use the same kernel, no need to flash boot.img.
If they are different kernels and you dont flash boot.img, you are now in a bootloop
lol Universal City
not bad
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
cannon19932006 said:
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
Click to expand...
Click to collapse
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
absolutelygrim said:
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
Click to expand...
Click to collapse
Success, THANKS!
absolutelygrim said:
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery.
Click to expand...
Click to collapse
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
cimenta said:
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
Click to expand...
Click to collapse
Because the new hboot makes it to where you cant flash kernels through recovery. only fasboot
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
cimenta said:
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
Click to expand...
Click to collapse
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
absolutelygrim said:
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
Click to expand...
Click to collapse
So although ROM zip file contains boot.img when flashing boot.img won't be flashed? That's why we need to flash is separately? Is it important to flash it before flashing ROM?
Thank you.R
I'm also, learning as I go. From reading and multiple failed attempts at flashing ROMs and kernels, I have found the correct way with 1.14 Hboot.
-dl the rom/kernel
-extract only the boot.img file
- save both .zip and boot to your desired folder.
-go into recovery and mount sd card to pc
-transfer .zip file to your phones sd card
-get back into fastboot on your phone
-transfer boot.img to fastboot folder
-from fastboot cmd prompt(if you have win7, open your folder with fastboot in it hold shift+right click and open cmd)
-type "fastboot boot boot.img" without quotes
-go back into recovery and clean cache/delvik
-then install .zip that you copied to the sd card
You should be good to go from there.
If I have left anything out, please feel free to correct.
Sent from my HTC One X using xda app-developers app
It is often stated that it is necessary to manually flash boot.img via fastboot AFTER installing a xxrom.zip in recovery.
Is this really necessary?
If you take a look in the file updater-script, which belongs to every xxrom.zip, you find that boot.img is flashed as last action in the update procedure (seen e.g. in the latest CM10-nightly). So I guess that it is not necessary to additionally flash it afterwards using fastboot.
Am I right?
1aladdin1 said:
It is often stated that it is necessary to manually flash boot.img via fastboot AFTER installing a xxrom.zip in recovery.
Is this really necessary?
If you take a look in the file updater-script, which belongs to every xxrom.zip, you find that boot.img is flashed as last action in the update procedure (seen e.g. in the latest CM10-nightly). So I guess that it is not necessary to additionally flash it afterwards using fastboot.
Am I right?
Click to expand...
Click to collapse
You are wrong and right lol. If your Hboot is 1.09 or lower TWRP can flash the boot.img but if you higher you have to fastboot or use Flash Image GUI app. And always a good idea to flash boot.img just in case it has changed but thats more for AOSP roms.
Darknites said:
You are wrong and right lol. If your Hboot is 1.09 or lower TWRP can flash the boot.img but if you higher you have to fastboot or use Flash Image GUI app. And always a good idea to flash boot.img just in case it has changed but thats more for AOSP roms.
Click to expand...
Click to collapse
I have Hboot 1.13 - so I need to "fastboot flash boot boot.img"
Unfortunately there is no error message showing that flashing the boot-partition during xxrom.zip-Installation in TWRP-recovery has failed.
I suppose that there is no particular order between installing the xxrom.zip and flashing boot-partition. Am I right?
1aladdin1 said:
I have Hboot 1.13 - so I need to "fastboot flash boot boot.img"
Unfortunately there is no error message showing that flashing the boot-partition during xxrom.zip-Installation in TWRP-recovery has failed.
I suppose that there is no particular order between installing the xxrom.zip and flashing boot-partition. Am I right?
Click to expand...
Click to collapse
I use to fastboot first then rom but now I just use Flash Image GUI. TWRP wont say its failed for some reason but it can if you remove the boot.img but thats nothing to worry about.
there is a method how to downgrade hboot:
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade+unbrick
it's a little bit tricky and requires some linux knowledge, but it takes you down to hboot 1.06
Just got an OTA from CM that says a stable build (CM10.0.0) is ready to be installed. My phone is currently running the 1109 nightly.
Has anyone gotten this and successfully installed? I'm about to try it, but wonder if we still need to flash the boot.img first, or if the actual OTA takes care of that. Would be completely awesome if it does.
If you have the old hboot then you can just ota. If you have the new one, fastboot flash boot.img
Sent from my HOX running Cyanogenmod 10
I'm currently running the CM10 nightly from 10/11 and tried the OTA upgrade to the stable version. Well, once I flashed the new version my wifi wouldn't turn on.
It's the same problem I've had previously. My wifi works fine on the 10/11 nightly, but anything after that and my wifi just won't turn on. It shows that it's off in my settings and when I try to turn it on it just hangs and never turns on.
No one else seems to be having this problem so I'm not sure what's going on. I would love to upgrade to the stable build but I need wifi to work. I ended up having to reflash the older ROM and Gapps, so my wifi is working fine now.
Anyone else have problems turning wifi on with the new version??
Thanks. Installed with TWRP and everything is working great.
Just didn't realize that CM even pushed OTAs. A coworker also got an OTA on his GS3 today and installed that way with no problem. They don't have the extra boot.img step to deal with.
danny39 said:
If you have the old hboot then you can just ota. If you have the new one, fastboot flash boot.img
Sent from my HOX running Cyanogenmod 10
Click to expand...
Click to collapse
danny39 said:
If you have the old hboot then you can just ota. If you have the new one, fastboot flash boot.img
Sent from my HOX running Cyanogenmod 10
Click to expand...
Click to collapse
Does this mean I need to wipe like I did the first time I installed CM10 or is there a way to do this as an update without losing apps and settings?
Also, is there a way to do this directly on the phone or does it need to be done over USB like I did with the initial ROM install? Sorry, this is my first update since rooting recently. I'd like to make sure I do this correctly.
ctennenh said:
Does this mean I need to wipe like I did the first time I installed CM10 or is there a way to do this as an update without losing apps and settings?
Also, is there a way to do this directly on the phone or does it need to be done over USB like I did with the initial ROM install? Sorry, this is my first update since rooting recently. I'd like to make sure I do this correctly.
Click to expand...
Click to collapse
You shouldn't lose apps or settings, but never hurts to do a backup anyway.
If you rooted from the 2.20 firmware: download the rom from CM and extract the boot.img file on the computer. Then put the two on the phone's sd card. From there, you do the same thing you did the first time. Flash the boot.img and then the rom and GApps. Everything should work fine.
If you came from 1.85, apparently you can install directly from the OTA on the phone.
Thanks for the help. Do I need to do fastboot on boot img from the computer as well, or is there a way to manage it on the phone?
I wish I could just do OTA updates like people on the older hboot.
ctennenh said:
Thanks for the help. Do I need to do fastboot on boot img from the computer as well, or is there a way to manage it on the phone?
I wish I could just do OTA updates like people on the older hboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1982442
ctennenh said:
Thanks for the help. Do I need to do fastboot on boot img from the computer as well, or is there a way to manage it on the phone?
I wish I could just do OTA updates like people on the older hboot.
Click to expand...
Click to collapse
I use FlashImageGUI to flash the boot.img on the phone. Only thing I do on the computer is extract the actual boot.img file from the ROM.
joe23521 said:
I use FlashImageGUI to flash the boot.img on the phone. Only thing I do on the computer is extract the actual boot.img file from the ROM.
Click to expand...
Click to collapse
Ok, just so I have it straight and because Flash Image GUI is warning me over and over: after I extract the correct boot.img I flash it using the Flash Image GUI, then use TWRP to install the boot.img, then the rom zip, then my gapps.zip? Thanks.
I was able to install it without flashing the boot.img. I was coming from the the latest nightly.
Sent from my One X using xda app-developers app
ctennenh said:
Ok, just so I have it straight and because Flash Image GUI is warning me over and over: after I extract the correct boot.img I flash it using the Flash Image GUI, then use TWRP to install the boot.img, then the rom zip, then my gapps.zip? Thanks.
Click to expand...
Click to collapse
Flash the boot.img with Flash Image GUI, ignore all the warnings. Then, it'll ask you if you want to boot into recovery. Say yes. Then in TWRP, just flash the rom and gapps zips. Don't touch the boot.img again.
h1m said:
I was able to install it without flashing the boot.img. I was coming from the the latest nightly.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Interesting. Did you root from the 2.20 firmware?
No Stable for me
The CM10 Stable release for HTC One X is not on get.cm and it does not come up on my ota check on the CM10 nightly (i have the latest nightly)
Any ideas
Hello everyone,
This is the issue i had, when going from 1109 to stable the system will not do a clean OTA, the system will not load, attempted cleaning everything but nothing worked, at one point i even corrupted my memory so i had to do a factory reset, lastly what i did was flash the boot.img again and reinstall the system this got everything back to work. so from experience it seems the stable will need to do a full reinstall.
I hope that will help other people.
EDIT: updated to 1114 but it seems that broke the search feature so going back to 10.0.0 :S
ozozdil said:
The CM10 Stable release for HTC One X is not on get.cm and it does not come up on my ota check on the CM10 nightly (i have the latest nightly)
Any ideas
Click to expand...
Click to collapse
Definitely there. http://get.cm/get/4LO
Excellent. Thanks so much. I managed to get it done. Here are my steps, FYI:
Coming from the 2.20 root with the latest hboot.
I downloaded but did not install the 10.0 stable update.
I went through my file browser to sdcard/cmupdater and copied the 10.0 evita zip to my Downloads folder.
After extracting the zip I copied the boot.img to the root directory of my sdcard. I don't think it has to be there, though.
I ran Flash Image GUI on the boot.img file, even with all the warning.
I then chose to reboot into recovery, where I installed the 10.0 evita zip, then installed the gapps zip.
Everything seems to work, including WiFi. I really appreciate all the help here at XDA. Hopefully my process above will help someone else.
deleted
That link is for the One XL Evita lte dual core version, I'm talking about the One X international hspa quad core version.
Thaks for thehelp anyway
Sent from my HTC One X using xda premium
Hey Guys
I'm struggling to locate an OTA for my HOX, is it only the XL that was updated with a stable release? as im unable to locate an endeavoru stable release for CM10?
I've taken a look through get.cm but cannot locate a copy anywhere? did we miss out? ?
Hey guys, I bought a used one x at&t and it came with twrp 2.2.20 and cleanromv5 I wanted to install cyanogenmod 10 and i was downloadingnit through rom toolbox,i also saw that there was twrp version 2.3.3.1 availiable so iinstalled it when i rebooted into recovery it booted into twrp 2.2.2.0 so i rebootedinto into system and then it booted into twrp 2.3.3.1 and everytime i reboot the same thing happens,i even tried wiping the phone and my backup.pls help me out!!!!!
maybe try flash 2.4 TWRP via fastboot?
claytonmas said:
Hey guys, I bought a used one x at&t and it came with twrp 2.2.20 and cleanromv5 I wanted to install cyanogenmod 10 and i was downloadingnit through rom toolbox,i also saw that there was twrp version 2.3.3.1 availiable so iinstalled it when i rebooted into recovery it booted into twrp 2.2.2.0 so i rebootedinto into system and then it booted into twrp 2.3.3.1 and everytime i reboot the same thing happens,i even tried wiping the phone and my backup.pls help me out!!!!!
Click to expand...
Click to collapse
For1n said:
maybe try flash 2.4 TWRP via fastboot?
Click to expand...
Click to collapse
i think that the twrp 2.2.2.0 that came with the phone is from the boot img, but what i dont understand is that when is ekect reboot system option it reboots into twrp 2.3.3.1 even after resetting the phone etc.plsgive me a solution.
Don't use rom toolbox... you could potentially download an incorrect rom
Sent from my evita using Tapatalk 2
InflatedTitan said:
Don't use rom toolbox... you could potentially download an incorrect rom
Sent from my evita using Tapatalk 2
Click to expand...
Click to collapse
what do i do now?
claytonmas said:
what do i do now?
Click to expand...
Click to collapse
i think i flashed the twrp 2.3.3.1 in the boot partition and not recovery.
claytonmas said:
i think i flashed the twrp 2.3.3.1 in the boot partition and not recovery.
Click to expand...
Click to collapse
you'll need to flash at least a new kernel (which is written to the boot partition), and maybe a new ROM. You may also want to flash the newest version of TWRP to your recovery (which is 2.4 now).
So to flash the recovery, you'll want to run this command in fastboot -> fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
then boot into your recovery and either use "adb push ROM.zip" or mount the sdcard as removable storage and drag the file from your comp onto your sdcard. Once it is on there, you can flash away (remembering to flash the boot.img if your hboot version is 1.14 or higher).
you'll need to flash at least a new kernel (which is written to the boot partition), and maybe a new ROM. You may also want to flash the newest version of TWRP to your recovery (which is 2.4 now).
So to flash the recovery, you'll want to run this command in fastboot -> fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
then boot into your recovery and either use "adb push ROM.zip" or mount the sdcard as removable storage and drag the file from your comp onto your sdcard. Once it is on there, you can flash away (remembering to flash the boot.img if your hboot version is 1.14 or higher).
Click to expand...
Click to collapse
thanks alot.one more question,im going to install cm10 and i think the boot .img of cm 10 has cwm .pls tell me how to flash the boot.img,also i i a factory reset in the bootloaer and now the sd car wont mount in recovery,havn't trie on pc yet.pls reply. thanks a million.
The boot.img of the ROM does not contain a recovery. They are separate.
Sent from my HTC One X using Tapatalk 2
claytonmas said:
thanks alot.one more question,im going to install cm10 and i think the boot .img of cm 10 has cwm .pls tell me how to flash the boot.img,also i i a factory reset in the bootloaer and now the sd car wont mount in recovery,havn't trie on pc yet.pls reply. thanks a million.
Click to expand...
Click to collapse
Skip twrp 4.0 and use 4.1... 4.0 has mounting problems.
.You'll need to install twrp. Youll have to download it from the thread in original dev section. Drop that download in your adb/fastboot folder... right click and choose open cmd prompt here... youll have to google the cmd because i havent used it since may... Enter twrp and mount.
Go to my computer, right click on removable storage and choose format..
You'll need to download a rom on your computer at this point, as formatting takes 20 minutes or so. Personally I recommend the latest viperxl 2.3.1, as this one flashes the boot.img for you so that's one less step you'll have to take.
Once formatted, you should be able to read storage.. so drag the rom into your sdcard. Wipe cache, dalvick, factory reset, system wipe ONLY IN TWRP!!!
you should be good... if not report back but don't do anything crazy.
Sent from my evita using Tapatalk 2
InflatedTitan said:
Skip twrp 4.0 and use 4.1... 4.0 has mounting problems.
.You'll need to install twrp. Youll have to download it from the thread in original dev section. Drop that download in your adb/fastboot folder... right click and choose open cmd prompt here... youll have to google the cmd because i havent used it since may... Enter twrp and mount.
Go to my computer, right click on removable storage and choose format..
You'll need to download a rom on your computer at this point, as formatting takes 20 minutes or so. Personally I recommend the latest viperxl 2.3.1, as this one flashes the boot.img for you so that's one less step you'll have to take.
Once formatted, you should be able to read storage.. so drag the rom into your sdcard. Wipe cache, dalvick, factory reset, system wipe ONLY IN TWRP!!!
you should be good... if not report back but don't do anything crazy.
Sent from my evita using Tapatalk 2
Click to expand...
Click to collapse
Thanks alot guys ,i got my phone running cm 10 but one problem ,my simcard is from Qatar an now im roaming in india ,my sim used to register on airtel n i could send and recieve ,essages aswell as make calls now it registers on tata docomo and i cant make any calls nor receive them.ps :my one x was unlocked.
You will need to add the APN for your carrier. Settings then mobile networks then APN. Menu add son and putthe settings in.
Sent from my HTC One X using Tapatalk 2