hi there
i have been using CM10.1 since the nightlies came out for my i9305
i thought it might be time for a new rom and went to the cm site and downloaded the newest version i rebooted into cwm recovery to install the os and it keeps on failing, so i thought i would try a different version and no matter what i try it seems to fail all the time now my phone was backed up so i can use it but would still like to know how to remedy this issue
thanks
Related
I was happily running along with my GT2 10.1 5113 using CM10, updating nightlies, all is well. Then I put the CM 10.1 unofficial, that went well, was using it and put the 12/09 version on, that went well also. However I decided I didn't like it and wanted to go back to CM10. I had a back up that I made in CWM with the 12/08 nightly and had begun restoring it when an error came up stopping the restore, only said file error restore can't continue. OK, that kinda blows chunks cause I know my rom just got hammered. Tried to restart, boot loop. Got back into recovery re flashed the CM 10.1, trying to save my data, bootloop. Got back in recovery and wiped data re flashed, bootloop. On an act of desparation I flashed the 12/08 nightly and, viola she lit up and booted to the setup screen.
Set it all back up and updated to the next nightly, 12/10 and I'll be danged, bootloop. Went back to recovery re-flashed the 12/08 nightly and all went well. No data loss just worked fine.
Bottom line I can't get anything but the 12/08 nightly to boot up. I even flashed stock with Odin, that bootlooped too! So I'm stumped.
It boots into the 12/08 nightly just fine and that's it.
I know this is wordy, but I wanted to make a thorough explanation. I feel this is related to the CWM error, but I have no idea where to go from here.
Anybody got a suggestion? All help is greatly appreciated.
I think cm10 installs jelly bean on your system. and switching back to an older version will cause the bootloop. that's what i believed happened to me when I installed cm10 by mistake instead of cm9 which is what i wanted. it took me several tries with odin and the stock rom to be able to go back.
I think the key is when you have cm10 installed then you need to enable the "usb debugging" in the developers section. that is probably what is stopping you from switching back to an earlier version or a new version or the stock rom using odin.
anyway that's how I was able to switch back to stock.
I think the reason you can´t restore CM10 is the fact that Android 4.2 introduces muti-users management. Thus, the system do not store in /sdcard/ any longer, but in /sdcard/0/ (for the first user). Since you still have a 4.1 recovery version, it doesn´t find the backups files any more. A solution is to move your sdcard data from /sdcard/0/ to /sdcard/ before restoring your backup.
As for CM10, the 12/09 and 12/10 nightlies don´t boot, due to kernel changes. These changes were reverted in 12/11, so this one should boot.
Einril said:
As for CM10, the 12/09 and 12/10 nightlies don´t boot, due to kernel changes. These changes were reverted in 12/11, so this one should boot.
Click to expand...
Click to collapse
Bingo! That worked, 12/11 worked. I had no idea that was happening. I made all the file changes actually because I wound up with sdcard/0/0/0 from all the flashing back and forth, that was funny. All is normal now thanks!
Sent from my GT-P5110 using xda premium
I've been using CM10.1 on this phone pretty much since it's been available and updating nightlies about once a week usually. Typically I use Ktoonsez kernel and also update this regularly. Also I am on the MF1 firmware. So, I'm pretty comfortable with the update process and have done it many times.
The other day I attempted to update to CM10.1 7/8 nightly while also installing a kernel I've never tried before called 'Sultan-kernel-Venturi-r5-USA'. Also completing the update process I rebooted and the phone would not move past the CM loading animation splash screen. After about 10 minutes of this I pulled the battery and rebooted, hoping it was just a hiccup but the same thing happened. After dirty installing various CM10.1 nightly and release versions with various combos of no custom kernel and the KT kernel but nothing would fix the boot issue.
I then attempted to wipe and ended up eventually wiping everything on the phone except the external SD card. Still, I could not get the phone to move past the CM splash screen. I then tried a few other AOSP ROMs with the same issue presenting.
Eventually I installed a TW based ROM and was able to get the phone to boot and and able to at least use my phone now. I've tried a couple time since to do a nandroid backup then try installing CM10.1 again and still nothing changes. I can restore the backup and the TW ROM works fine again.
Any ideas on what could have happened to cause this or anything else I can try to get AOSP ROMs working on my phone again?
I would say Odin back to 4.0.4 stock, do the OTA's, reroot with the one click root in the developer section, and it should work.
Sent from my SCH-I535 using xda app-developers app
I did get this figured out. Somehow my EFS partition was wiped. TW based ROMs would actually boot but displayed a 'Factory Mode' warning on startup. AOSP ROMs would not finish booting at all. After restoring EFS from backup everything started working again.
Hi everybody,
I decided to go back to Cyanogenmod, because i had some issues with the ROM I used before. First I flashed the CM 10.1.3 stable, everything worked fine, but I couldn't connect to any WiFi. So i tried flashing the nightly 10.2 10.2 2013111 over the Updates in the preferences. Still, i couldn't connect to any WiFi. I tried it two more times with full wipes and flashing the nightly over my Recovery, but couldn't make it work.
All these times i flashed the boot.img after flashing the nightly. I don't really know what to do anymore and thought anyone might have an idea for me?!
I didn't have any major issues until today, so i don't know what Information you might need to help me, so please tell me if I should say something more about the system or how I flashed it etc.
Thanks in Advance!
Edit: Same Problem with CM11...
Edit 2: Tried to flash the Bubba Kernel, because i read something about it...now i can't even turn the wifi on. -.-
so It has been a few months since I flashed a new ROM.
The Last ROM I installed was a the stable release for 10.2 d2vzw
I recently decided to update my ROM maybe to a new CM or something difffernt.
Well I tired to download and install Smasher X-6.0 But partway thru the flashing process, it failed.
I rewiped and tired again and again, Even tired to reinstall CM. and It keeps failing.
Now when I attempt to turn my phone off, TWRP says i need to fix root, and when I turn my phone back on it goes straight to TWRP.
Its been so long since I have had a problem with my phone, I now dont know what to do to even maybe fix it.
Im guessing I might need to completely restore my phone, and then maybe moving forward from there, but I cant find anything to help.
Please someone help me fix my phone
EDIT: I am also not sure which Kernel Im using, So im not even sure if I can ODIN back to stock and just redo the whole process.
TyPunchesTURTLES said:
so It has been a few months since I flashed a new ROM.
The Last ROM I installed was a the stable release for 10.2 d2vzw
I recently decided to update my ROM maybe to a new CM or something difffernt.
Well I tired to download and install Smasher X-6.0 But partway thru the flashing process, it failed.
I rewiped and tired again and again, Even tired to reinstall CM. and It keeps failing.
Now when I attempt to turn my phone off, TWRP says i need to fix root, and when I turn my phone back on it goes straight to TWRP.
Its been so long since I have had a problem with my phone, I now dont know what to do to even maybe fix it.
Im guessing I might need to completely restore my phone, and then maybe moving forward from there, but I cant find anything to help.
Please someone help me fix my phone
EDIT: I am also not sure which Kernel Im using, So im not even sure if I can ODIN back to stock and just redo the whole process.
Click to expand...
Click to collapse
Are you trying to update to a kk rom?
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Hello!
I was using the SungSonic ROM for almost a year now and I decided to change it today. So I flashed a CyanogenMod Nightly build for the P3100 This morning.
It booted up fine, and there were no issues in the beginning.
But then it started disconnecting calls randomly. Like, Someone calls, The phone rings for a second and boom! It shows a missed call.
I figured rebooting it would fix it but it made my problem only worse.
It now barely shows any Network service at all. If it is there, only for about 20s before it goes back off.
Is there any way to fix it without flashing another ROM? I like CyanogenMod and plus, its for my mother and I prefer keeping it simple.
Also, keep in mind that my Tab does not get recognised on any PC with any Cable I could find.
So, I am stuck with PhilZ Recovery for the P3100.
If the problem can be fixed via Flashing a new Mode/Baseband then please, give me a .zip for only the modem and not the whole ROM.
Thank You for Reading and I will hope you guys help me out.
Regards,
Shinichi Reshima
Always do a nandroid B/U before you flash so if you run into a problem like this you can go back. CM nightlys are not always stable, and sometimes you can't use them unless you have the base stable version of that ROM already installed. Must try and install the base version of the build, it may fix your problem. I run CM11 by Android Andi with no issues and no nightlys.
Pp.