Earlier this week, I had flashed a Rohan's kernel for CM10. For unrelated reasons - I decided to go back to a previous backup of CM10. The backup was of a previous nightly. That nightly was running the stock CM10 kernel.
I did factory reset, restored backup, cleared cache, dalvik, then loaded the boot.img using the One XL All in One Toolkit. I could not get past the spinning CM10 logo. I tried just installing the stable CM10 package, same install procedure and couldn't get anywhere. Just for fun, I tried installing ViperXL to see if I could get *something* to install, and it worked just fine. Hmmm...
Tried CM10, a nightly this time, no luck. Because I was running out of ideas (and had read so many threads here, thanks all :good I decided to try something else. I downloaded the HTC Auto Boot.ini installer (see the thread here http://forum.xda-developers.com/showthread.php?t=1962428) I installed the same nightly I had been trying before, using the same procedure - but this time flashed the boot.img using the HTC Auto Boot.ini one click tool. Well....it worked
Who knows, may have been coincidence but I really feel like I had tried everything else, and maybe for whatever reason, the All in One Toolkit wasn't getting the boot.img to stick.
I just wanted to mention this as something to try if anybody else was experiencing the same problem. The problem could very well have been me, or some other odd situation I created by trying to revert to a backup with a different kernel. The All In One Toolkit was *very* helpful for rooting, etc so I don't want to speak ill of it. It may work just fine for flashing boot.img in most cases. But if you get stuck, well, try the HTC Auto Boot.ini installer and see if it helps you out.
Related
I've been using CM7 Nightlies ever since build 3 without any problems on my D1. All of the sudden, I am unable to boot into clockwork recovery. So now I can't backup, update, or recover. Any thoughts?
I'm considering a full wipe if I can't get this resolved. Thanks in advance for all of the help
i am currently having the same issue with my Moto Droid.
Running CM7rc2 wont boot into CWR.
I've tried updates of CRW (currently version 2.5.0.1) but it wont flash high versions...
Updated Rom manager, that wont boot into it.
CM7 reboot menu wont boot into it.
X+power wont boot and volume down one wont work either...
Also tried the alternative recovery flash and rom manager cant flash it.
I feel your pain, it was very frustrating. After a few days of not being able to backup, recover, or update, I decided it was time to wipe the droid and start with a clean slate. It took me a couple hours to get everything back up but I didn't know what else to do. Hopefully someone out there has a better solution so you don't have to do the same thing.
airballwall said:
I feel your pain, it was very frustrating. After a few days of not being able to backup, recover, or update, I decided it was time to wipe the droid and start with a clean slate. It took me a couple hours to get everything back up but I didn't know what else to do. Hopefully someone out there has a better solution so you don't have to do the same thing.
Click to expand...
Click to collapse
I've been struggling with this for weeks, finely found out it is a simple fix, turn off debug. settings, applications, development, UNCHECK debug.
It works.
I found a fix as well. I simply flashed an alternate recovery, at the very bottom of the rom manager app, and then reflashed clockwork. I really should have thought of this first, oh well.
Sent from my Droid using XDA App
I've tried CM10 stable, CM10 nightlies. MIUI, Viper, Blackbean, Trickdroid. Just about every one. I am on CM9 now wanting to get the bean. None of them work. I always get Google Wizard process stopped working and then endlessly process.android crashes over and over. My actual goal was/is CM10. Is my phone screwed up? Seems like tons of other folks can upgrade. Do a lot of people have the same issue as I?
Using a One S with CWM. Installs fail the same way regardless if I do them from Rom Manager or download and run from CWM.
Thanks folks!!
EDIT: Just tried again. Upon bootup for CM10 "Unfortunately, the process com.android.phone has stopped". No matter how many times I hit OK it pops back up.
Dilnad said:
I've tried CM10 stable, CM10 nightlies. MIUI, Viper, Blackbean, Trickdroid. Just about every one. I am on CM9 now wanting to get the bean. None of them work. I always get Google Wizard process stopped working and then endlessly process.android crashes over and over. My actual goal was/is CM10. Is my phone screwed up? Seems like tons of other folks can upgrade. Do a lot of people have the same issue as I?
Using a One S with CWM. Installs fail the same way regardless if I do them from Rom Manager or download and run from CWM.
Thanks folks!!
EDIT: Just tried again. Upon bootup for CM10 "Unfortunately, the process com.android.phone has stopped". No matter how many times I hit OK it pops back up.
Click to expand...
Click to collapse
Did you wipe everything prior flashing?
Dilnad said:
I've tried CM10 stable, CM10 nightlies. MIUI, Viper, Blackbean, Trickdroid. Just about every one. I am on CM9 now wanting to get the bean. None of them work. I always get Google Wizard process stopped working and then endlessly process.android crashes over and over. My actual goal was/is CM10. Is my phone screwed up? Seems like tons of other folks can upgrade. Do a lot of people have the same issue as I?
Using a One S with CWM. Installs fail the same way regardless if I do them from Rom Manager or download and run from CWM.
Thanks folks!!
EDIT: Just tried again. Upon bootup for CM10 "Unfortunately, the process com.android.phone has stopped". No matter how many times I hit OK it pops back up.
Click to expand...
Click to collapse
What is your install process?
Sent from a baked One S
If I've helped hit the thanks button
Dilnad said:
I've tried CM10 stable, CM10 nightlies. MIUI, Viper, Blackbean, Trickdroid. Just about every one. I am on CM9 now wanting to get the bean. None of them work. I always get Google Wizard process stopped working and then endlessly process.android crashes over and over. My actual goal was/is CM10. Is my phone screwed up? Seems like tons of other folks can upgrade. Do a lot of people have the same issue as I?
Using a One S with CWM. Installs fail the same way regardless if I do them from Rom Manager or download and run from CWM.
Thanks folks!!
EDIT: Just tried again. Upon bootup for CM10 "Unfortunately, the process com.android.phone has stopped". No matter how many times I hit OK it pops back up.
Click to expand...
Click to collapse
To fix it:
Grab the all in one tool kit from development forum
Open the zip file for the CM10 rom and copy the boot.img.
Then paste the boot.img file where the tool kit can see it. This would be the /data/kernel folder of wherever you placed the toolkit.
The just hit use the flash kernel command in the toolkit.
Reboot
When you're back up and running get this tool so you can do it from the phone next time.
http://forum.xda-developers.com/show....php?t=1954121
thanito said:
Did you wipe everything prior flashing?
Click to expand...
Click to collapse
I sure did.
thanito said:
Did you wipe everything prior flashing?
Click to expand...
Click to collapse
beats4x said:
What is your install process?
Sent from a baked One S
If I've helped hit the thanks button
Click to expand...
Click to collapse
Several. I've chosen to install both the stable and the nightly CM10s from the download option within ROM Manager Premium. I always Wipe Cache, make backup and wipe Dalvik from there. I've also tried several other roms that way. Additionally I have tried downloading the CM10 ( and some other ) files and flashing them from Clockwork Recovery ( I don't have CWM Touch ) with the same results.
Not real experienced with this but follow instructs pretty well.
dc211 said:
To fix it:
Grab the all in one tool kit from development forum
Open the zip file for the CM10 rom and copy the boot.img.
Then paste the boot.img file where the tool kit can see it. This would be the /data/kernel folder of wherever you placed the toolkit.
The just hit use the flash kernel command in the toolkit.
Reboot
When you're back up and running get this tool so you can do it from the phone next time.
http://forum.xda-developers.com/show....php?t=1954121
Click to expand...
Click to collapse
Thanks for the infos. I will try that out this weekend. The only problem is that link is not working for me. Get a 404. Looks truncated.
In all your posts, I don't see you flashing the boot.img. In higher hboots, this must be flashed in fastboot...otherwise, you are trying to use an older Sense kernel with the other ROMs which will result in random problems...at the very least, you should be using TWRP, not the outdated and unsupported CWM.
Here is the link
http://forum.xda-developers.com/showthread.php?t=1954121
el_smurfo said:
In all your posts, I don't see you flashing the boot.img. In higher hboots, this must be flashed in fastboot...otherwise, you are trying to use an older Sense kernel with the other ROMs which will result in random problems...at the very least, you should be using TWRP, not the outdated and unsupported CWM.
Click to expand...
Click to collapse
The missing part here is you are under the assumption that I'm not an idiot. You would be wrong <cackle>
Seriously though. I am very new to this. I got a Nexus One a couple years ago and my buddy put me on CM. When I got my new phone, I followed one of the guides on the site here to put CM9 on my phone. I went with CWM because it was the only thing I know. I have since followed another guide to root and put CM10 on my Kindle Fire. That one has TWRP and I like it. Just don't yet understand how to put it on my One S. Have some friends that are going to assist hopefully this weekend. There is just soooooo much info out there and much of it assumes a higher level of Android competency than I posess.
BTW I'm pretty sure I flashed a boot image but honestly don't know.
Thanks for the advice. I'll get there eventually :good:
We can't flash same way as N1, I had one. We have no s-off and have to flash boot separate.
Do get TWRP. Download GooManager from PlayStore and flash TWRP thru it. You have to open GooMananger then use menu to find and tap on Install OpenRecoveryScript. Rest will prompt you--have your Nandroids first.
Also, I don't see you mentioning wiping System--much need when flashing a new rom.
Another app is Flash Image GUI from Market that allows to flash boot from within the rom--no fastboot needed.
I don't use it cause I have an hboot under .13 and can flash everything thru the rom and can also flash radios. If you are at or above .13 no luck on doing it that way.
Yes, flashing a boot image is important. You have to make sure you are flashing a boot image with an AOSP kernel not SENSE. For newer kernels you can check our the sticky on the DEV page related to ROMs and kernels. A new 3.0 fusion kernel for AOSP ROMs was recently posted. This worked for me along with the new PAC man ROM.
AKToronto
Sent from my HTC One S using xda premium
Went to my friends house. He did everything you all said to do. Now on TWRP, He flashed the boot image from CM10 after flashing CM10 on the phone. Same thing. Crash Crash Crash Crash Crash. Every app will stop working with an error. He was using LogCat and every error referred to a Java class file not found. Tried a CM10 nightly and same issue. Once again I am restored back to CM9 and my guru is scratching his head LOL. Seems to work for everyones One S but mine.
So I was able to successfully root my AT&T HTC One X and decided I wanted to install the CM 10 ROM (1st ROM install). I did all the data backups with Titanium, downloaded the latest zip files from cyanogenMod (both the 12/13 and 12/14 nightly versions), transferred them to my phone, booted into recovery (TWRP), did a back-up, did a system wipe, flashed the ROM and then did a reboot. However, when it boots it gets stuck in the boot-up screen (bootloop) and doesn't do anything. I have read on this and it keeps saying to wipe system data again and flash the ROM again and it keeps doing this. I want to install this ROM, but I need some help. Any suggestions on what I did wrong?
Note: I accidentally posted this in the Android Q&A section, so I apologize for the double post. I just think this is probably the best place to get my answer.
Did you flash the boot.img?
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
jon8105 said:
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
Click to expand...
Click to collapse
if they are backups from sense, that *MAY* cause problems, but don't quote me on that. I don't use sense, can't say for sure
OK, maybe that is why. Not a big deal since I haven't had the One X too long. Thanks for the help guys.
Good to know
I have tried to do this a couple of times since the new version of BMM came out. I followed all of the instructions to make it work. Then I flashed PACman and I got stuck on the loading (seemed like a bootloop) screen for like half an hour. And no matter what ROM that I use this seems to be happening. I would like to use either the PACman or AOKP that alerted has up. Any suggestions?
at2smithjason said:
I have tried to do this a couple of times since the new version of BMM came out. I followed all of the instructions to make it work. Then I flashed PACman and I got stuck on the loading (seemed like a bootloop) screen for like half an hour. And no matter what ROM that I use this seems to be happening. I would like to use either the PACman or AOKP that alerted has up. Any suggestions?
Click to expand...
Click to collapse
Did you flash the gapps too?
If it were me, I'd FXZ back to stock ICS then root, install BMM, boot into BMM, factory reset, flash ROM, flash gapps then reboot. Works for me every time.
Brought to you by time and relative dimensions in space.
I always make sure that I get the proper gapps.apk file for the version of the rom that I am installing. I think that the only thing that you are doing different than me is the factory reset. Thanks. I will give this a try and i will keep my fingers crossed.
at2smithjason said:
I always make sure that I get the proper gapps.apk file for the version of the rom that I am installing. I think that the only thing that you are doing different than me is the factory reset. Thanks. I will give this a try and i will keep my fingers crossed.
Click to expand...
Click to collapse
You no do factory reset before flashing ROM? That's the cause for bootloop.
And if you have BMM set up and different ROMs on various systems, then doing a factory reset on any system wipes other systems too. You just have to delete the partitions for that system in order to delete it.
And btw Gapps come in flashable zip and not apk
Remember, if you're trying to flash any of the Kexec based ROMs (like anything posted by deveshmanish) and you keep getting stuck at the boot screen, then you may be one of the unlucky "Kexec - rejects" like myself.
If so, then none of those ROMs will work for you. You need to try one of the non-kexec versions. There are several by different devs.
Sent from my personal phone thingy.
Hi, I just tried flashing cyanogenmod on my us cellular galaxy s3, and I ran into a problem. I followed a great youtube tutorial on how to flash cyanogen, and everything went fine. the tutorial used goomanager, and was done only using the phone, no computer. I flashed the rom after backing everything up through titanium, and everything appeared to be working like it should. After the flash was complete, the cyanogen animation popped up on my screen, but as soon as it finished loading, two messages popped up: setup wizard has stopped and goo.apps has stopped. I would hit okay, but the two messages just kept popping up. I restored my stock rom, but id still like to flash cyanogen and I need to know what I need to do to prevent this from happening again and how to restart the flash process. Any help would be greatly appreciated!
intelligentduck said:
Hi, I just tried flashing cyanogenmod on my us cellular galaxy s3, and I ran into a problem. I followed a great youtube tutorial on how to flash cyanogen, and everything went fine. the tutorial used goomanager, and was done only using the phone, no computer. I flashed the rom after backing everything up through titanium, and everything appeared to be working like it should. After the flash was complete, the cyanogen animation popped up on my screen, but as soon as it finished loading, two messages popped up: setup wizard has stopped and goo.apps has stopped. I would hit okay, but the two messages just kept popping up. I restored my stock rom, but id still like to flash cyanogen and I need to know what I need to do to prevent this from happening again and how to restart the flash process. Any help would be greatly appreciated!
Click to expand...
Click to collapse
before you flashed the rom did you wipe data and cache? you might also be on the nightly version, try looking for the stable version, and if its on 10.1 its on 10.1, theres nothing you can do but wait for it to become stable if it isent already.
Trozzul said:
before you flashed the rom did you wipe data and cache? you might also be on the nightly version, try looking for the stable version, and if its on 10.1 its on 10.1, theres nothing you can do but wait for it to become stable if it isent already.
Click to expand...
Click to collapse
Everything was wiped. what I think happened was when I backed everything up, I didn't set titanium to not restore my app data, causing a bootloop. I could be very wrong about that though. What I need to know is how to reflash it, as I have already tried to but when I do it brings up system recovery instead of reflashing. Is it because I already tried flashing it once? and if that's the case how do I start from scratch? Oh, and I did flash the stable version. it was 10.1.2
intelligentduck said:
Everything was wiped. what I think happened was when I backed everything up, I didn't set titanium to not restore my app data, causing a bootloop. I could be very wrong about that though. What I need to know is how to reflash it, as I have already tried to but when I do it brings up system recovery instead of reflashing. Is it because I already tried flashing it once? and if that's the case how do I start from scratch? Oh, and I did flash the stable version. it was 10.1.2
Click to expand...
Click to collapse
might want to try flashing a stock rom via odin cause it sounds like you have stock recovery now, i dont know if anyone will pick you up in the q&a section, since yours is us cellular i dont think they have a forum for that specific contractor just only t-mobile at&t and verizon would have one. you can ask them in their q&a but tell them your situation and that your on us cellular. good luck mate. if ya have any questions just ask right here.