Hello XDA,
Sorry for the long post but I am desperate!
The first ROM I ever flashed was CM 10 M2 which ran well and went without any problems. For this I used CWM. I found a stable nightly early in December and decided to update. I also wanted to store my backups on my external however, so I switched to TWRP and created a new backup of my stock TouchWiz rom using TWRP then backed my CM10 M2 up just in case. I flashed the update without wiping the data (factory reset) but did wipe the dalvik cache. This worked fine; all my apps were still there as well as my background. So when GooManager told me there was a 10.1 update for my Rom I thought why not try it out. I figured this was a big update so I wiped dalvik and did a factory reset. After flashing I ended up in a loop of "com.android.something or other has stopped" which turned into "setup wizard has stopped". The homescreen would not load. Fine. Booted into recovery last night after this and reinstalled my latest backup of the nightly I had been using for about 20 days. Seemed OK but the "android activation" screen was taking forever so I pushed home, plugged my phone in and passed out. I Woke up this morning and tried to send a text but it wouldn't send. Tried to call and I couldn't. Now I have restored every recovery I had (Stock, M2, Nightly) multiple times and same problem except that in stock I get a roaming charge warning. I was sure returning to stock would solve this. Does anyone know what I can do? Im not sure exactly how to factory reset but am willing if thats what it takes.
Thanks a ton!
Pups
Try here: http://forum.xda-developers.com/showthread.php?t=2065285. It has worked for several people.
Related
Hi all, first time poster! I was going to post in the development section (CM10 releases) but since I'm a new user, I came here
I just had a few questions about the 8/25 nightly and flashing new ones in general.
The first time, I was on stock (rooted, unlocked), went to CWR, flashed both nightly & gapps without doing a fact reset.
Didn't exactly put me in a bootloop, but it would go to a nexus 7 bootscreen (which I had installed myself, I think), and it would continue forever without visually appearing to loop to boot animation. So maybe it was a bootloop, but the animation just seemed to continue smoothly without any visual glitches...forever. If that made sense. Since it smoothly loops in the first place, I thought a bootloop might make the loop irregular etc. OKAY MOVING ON.
I got back into recovery mode, did a factory reset, wiped the cache partition, flashed everything, then booted it up...and it worked (thank god, no $600 brick)! But for some reason it showed the CM9 boot animation for some reason. Is this what's supposed to happen?
Also, when I flash new nightlies, will I have to factory reset every time? Is there anything else a noob might have to know about CM10, flashing, etc that isn't immediately obvious?
Thanks a lot for your time (fantastic noob video, by the way, and I apologize for my lack of brevity but I try to make up for it with sincerity in thanks)! Any help is greatly appreciated!
It still has the cm9 boot animation(doesnt bother me) it will get updated soon for the cm10 bootanimation. I think you can flash the cm10 bootanimation. You don't have to factory reset every nightly but you mightrun into problems if you dont. for sure wipe dalvik and cache every nightly.For now i would factory reset every nightly because they are still changing alot of things.
Gotcha! Thanks, yeah at first I just went WTF because I thought I had flashed the wrong ROM ^^;;
Hope I'm able to find a stable version then so I can at least get set up and back up my apps etc before having to fact reset for the next nightly haha.
Another issue I was having on stock TW was that for some reason installing third-party apps would be impossible--I could click on cancel but not on install when the package installer screen came up. Flashing CM10 actually fixed this
Hi,
I recently have flashed some new roms on my phone. So heres what happened... I had been using MIUI for months now for my NxS4g but the MIUI rom was just getting too laggy for me for daily use. So then I flashed Factory Rom. Worked good for a while then it started this rebooting randomly.. I Did Full Wipe, Format etc before flashing.. It seems fine while using it but once I turn the screen off and let it sit it just starts to randomly reboot. So I thought oh well its just the rom. Then I went back to MIUI and flashed the new Miui 2.10.26.2 which is a great running rom and I thought it fixed my problem because I spent an hour or 2 installing fresh new apps from the market, didnt restore anything or flash a custom kernel everything was stock and all fresh new apps. So I went to bed woke up at 6am like usual and noticed my phone had stopped responding... had to take the battery out and boot it up.. sometimes it does that and i have to pull the battery and sometimes it fully reboots. So now I am stumped ive tried everything i know. full format/wipes, fixing permissions, wiping dalvik and cache, and still not working! I hope my phone isnt dying or something. It was working fine. Please if anyone has a fix or knows what to do please help me! The only thing I haven't done is formatted my SD card which is what im about to try.
Thanks in Advance!
Adam
Hi,
What factory ROM?
Every ns4g responds to different kernels differently...maybe the newest version of that ROM u installed had a different kernel that sometimes causes many random reboots... so check that plz.
But u say udid a factory reset and stuff... did u wipe Dalvik and cache? Cuz that is important.
Good luck
Vs Nexus S4G using tapatalk2
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
Hi Everyone,
On my TF300T I am running the 4.2 bootloader, I have put TWRP 2.5 recovery on and it is working perfectly. The only issue is that on the two custom roms I have tried (Unofficial CM10.1, CROMi-Xenogenesis 4.6.4) my wifi won't turn on, I have flashed back to stock and the wifi works again. I have tried a couple of kernels on CROMi but that didn't help. I have tried searching but I couldn't find any useful results, what I am missing?
Cheers,
Wipe
jezzam said:
Hi Everyone,
On my TF300T I am running the 4.2 bootloader, I have put TWRP 2.5 recovery on and it is working perfectly. The only issue is that on the two custom roms I have tried (Unofficial CM10.1, CROMi-Xenogenesis 4.6.4) my wifi won't turn on, I have flashed back to stock and the wifi works again. I have tried a couple of kernels on CROMi but that didn't help. I have tried searching but I couldn't find any useful results, what I am missing?
Cheers,
Click to expand...
Click to collapse
I had this same issue when I first tried CROMI-X. I reflashed doing a full wipe (data, system, factory reset, and caches) and everything worked great. It is slightly more time consuming since you have to reinstall all of your custom apps. Also be sure to make a backup of all data and personal files on an sd card.
Once I had the custom ROM installed, I didn't have to do the full wipe for any later updates, only the caches.
Ok I reflashed after doing a wipe of data, caches, and system, then a factory reset. Still no wifi, it just won't turn on, it gets stuck at 'Turning Wi-Fi on..." and eventually times out and the switch goes back to off.
Any other ideas?
Bluetooth works so I have been able to tether through my nexus 4, no wifi is pretty annoying.
Figured it out, had encrypted my tablet, decrypted by going back to stock rom and recovery and then doing a factory reset. Now all is working fine.
Good deal!
jezzam said:
Figured it out, had encrypted my tablet, decrypted by going back to stock rom and recovery and then doing a factory reset. Now all is working fine.
Click to expand...
Click to collapse
Glad to hear you got it figured out. I will make a note of this for future reference should somebody else have the same problem.
I've been trying to upgrade to a LiquidSmooth KitKat (3.0 Nightly Beta) ROM but it's been failing. So I figured it's Sunday, it's early, let me try again. Let's get a baseline:
Last usable (as of earlier this morning) ROM: LS 2.7 (4.2.2)
TWRP 2.6.3.0
SuperSU installed
So I *WAS* unlocked and rooted.... now... I don't know what the heck is wrong.
Saturday I downloaded "EZ Unlock 1.2" and installed it; Unlock Status was "UNKNOWN" and even after clicking the UNLOCK button it still showed "UNKNOWN"
So, this morning, I made sure I had the new ROM (LS KitKat 3.0 Nightly Beta 2) on my external SD card, booted in to TWRP, and updated to the latest TWRP (2.6.3.1). I then cleaned out some old ROM backups and made a new one (using compression) which was successful. Rebooted to system, all looked & worked normally, so I rebooted to TWRP Recovery, did a Factory Reset + system (so cache, dalvik, data, & system) and that went fine. Tried to install the new ROM... FAILED. So I rebooted to Recovery and tried to restore the backup I had just made, and it seemed to succeed, but when the phone rebooted, it only got to where it reads "Samsung Galaxy S III" and got no further. I let it sit like that for 10 minutes, then pulled the battery. I booted back in to Recovery and tried restoring a backup made 2 days ago (that I have previously restored from successfully) and that gave a "successful" result, but same thing after rebooting: stuck at where it reads "Samsung Galaxy S III" and would go no further.
I am in DOWNLOAD mode currently and want to get back to the point of being able to restore my backup from 2 days ago. I'll lose text messages basically, and that's fine. I have downloaded ODIN 3.07 but it's been about a year since I last tinkered with it.
Can someone help please? I either get this phone working in the next few hours, or I have to go buy something else off craigslist... or full retail... and I'd really just prefer to get this phone working again.
If I need to "start from ground zero" and redo the boot unlock and root it, so be it. Basically, how do I unbrick my S3?
papadelogan said:
I've been trying to upgrade to a LiquidSmooth KitKat (3.0 Nightly Beta) ROM but it's been failing. So I figured it's Sunday, it's early, let me try again. Let's get a baseline:
Last usable (as of earlier this morning) ROM: LS 2.7 (4.2.2)
TWRP 2.6.3.0
SuperSU installed
So I *WAS* unlocked and rooted.... now... I don't know what the heck is wrong.
Saturday I downloaded "EZ Unlock 1.2" and installed it; Unlock Status was "UNKNOWN" and even after clicking the UNLOCK button it still showed "UNKNOWN"
So, this morning, I made sure I had the new ROM (LS KitKat 3.0 Nightly Beta 2) on my external SD card, booted in to TWRP, and updated to the latest TWRP (2.6.3.1). I then cleaned out some old ROM backups and made a new one (using compression) which was successful. Rebooted to system, all looked & worked normally, so I rebooted to TWRP Recovery, did a Factory Reset + system (so cache, dalvik, data, & system) and that went fine. Tried to install the new ROM... FAILED. So I rebooted to Recovery and tried to restore the backup I had just made, and it seemed to succeed, but when the phone rebooted, it only got to where it reads "Samsung Galaxy S III" and got no further. I let it sit like that for 10 minutes, then pulled the battery. I booted back in to Recovery and tried restoring a backup made 2 days ago (that I have previously restored from successfully) and that gave a "successful" result, but same thing after rebooting: stuck at where it reads "Samsung Galaxy S III" and would go no further.
I am in DOWNLOAD mode currently and want to get back to the point of being able to restore my backup from 2 days ago. I'll lose text messages basically, and that's fine. I have downloaded ODIN 3.07 but it's been about a year since I last tinkered with it.
Can someone help please? I either get this phone working in the next few hours, or I have to go buy something else off craigslist... or full retail... and I'd really just prefer to get this phone working again.
If I need to "start from ground zero" and redo the boot unlock and root it, so be it. Basically, how do I unbrick my S3?
Click to expand...
Click to collapse
Have you try to wipe cache/dalvik cache/system/ format sd, make sure everything is mounted the do the restore again?
buhohitr said:
Have you try to wipe cache/dalvik cache/system/ format sd, make sure everything is mounted the do the restore again?
Click to expand...
Click to collapse
I am currently backing up my external SD card (all pics & backups go to ExtSDCard) before doing any formatting. I was going to try that next, but am expecting it to fail. What I've found on XDA so far has mostly for those that took an OTA but that is not my case. I am severely pressed for time (use my phone for work as well as personal) and am planning for "worst case scenario" so, assuming your suggestion fails, do I get the original ROM, flash that back using ODIN, then re-do the boot unlock & root?
papadelogan said:
I am currently backing up my external SD card (all pics & backups go to ExtSDCard) before doing any formatting. I was going to try that next, but am expecting it to fail. What I've found on XDA so far has mostly for those that took an OTA but that is not my case. I am severely pressed for time (use my phone for work as well as personal) and am planning for "worst case scenario" so, assuming your suggestion fails, do I get the original ROM, flash that back using ODIN, then re-do the boot unlock & root?
Click to expand...
Click to collapse
That would be the right way..good luck!
buhohitr said:
That would be the right way..good luck!
Click to expand...
Click to collapse
I was hoping for a bit more than "good luck" actually since it's been a good year since my last trip with Odin... but thanks.
papadelogan said:
I was hoping for a bit more than "good luck" actually since it's been a good year since my last trip with Odin... but thanks.
Click to expand...
Click to collapse
I have high confidence that you will have this issue resolved shortly. It's not your fault, lately, some custom roms did not behave accordingly...