I was on CM10.1 for a very long time, and just recently decided to flash something newer. So I tried flashing Philz recovery (had CWM), then used that to flash VRUBMF1 and VRUCML1 baseband afterwards (from this thread). Without booting my phone, I then flashed CM11 and the kitkat gapps. When trying to restore apps through Titanium Backup, I got a random reboot. Since then, I would get many random reboots, most often in the middle of a Titanium Backup restore of my user apps because it's the first thing I want to do. Sometimes the phone will reboot before even getting to the app restore. I have tried flashing PAC rom (4.3--I flashed jb gapps with this) and unofficial Paranoid Android (4.4) as well, and the problem persists no matter which rom I am running. Of course, I have tried reflashing many times.
I am also trying and currently on TWRP, but this hasn't helped. Going back to CWM and trying to restore my CM10.1 backup gives me a fail error.
Before each flash, I wiped data, and rewiped cache and dalvik afterwards too. Is there a problem in my flash process? What can I do to solve this issue?
Related
about a week ago i updated to the newest cm10.1 nightly with gapps 4.2. after flashing those i tried to flash leankernel. my battery was low and the phone turned off when rebooting after the leankernel flash. since then i cannot flash any kernel. i have to do a battery pull to get back into cwm recovery. once in recovery i can wipe data and reinstall cm 10.1 with the standard kernel. i have tried just about every combo of wiping cache, davlik, fix permissions. still not able to flash any kernel. could it have something to do with gapps 4.2 or the phone shutting off mid flash? if so does anyone know how to repair? i already flashed back to stock and rerooted re-unlocked, etc. thanks
and to clarify , it was gapps 4.2.2
Ive found that 3.4 based kernels work with some roms and not with others.
try an older build date its likely not 3.4 based.
or, if your trying a non 3.4 kernel and it wont boot, try a 3.4 kernel.
If you're trying to flash LeanKernel, what's the zip file you're attempting to flash? Also, what are you wiping prior to flashing the kernel?
Sent from my SCH-I535 using xda app-developers app
i tried the mastamoon 3.4 kernel with no luck . the rom i amrunning is the cm-10 nightly 2013-03-24. the leankernel version i am running is lk_s3vzw_aosp_jb42-v2.9. i wipe cache then wipe davlik then flash, it always worked with that procedure before, but since the problem i have tried wiping both after along with fixing permissions. before this issue it was simple as pi, wipe cache, davlik, flash, reboot .
You could always try twrp. Ha. It would make no sense why you couldn't install a kernel.
I would assume since you went back to Odin stock. It would flash factory kernel and give you a clean slate.
So unless cwm is outdated.... ?
Sounds very weird.
actually that is another variable that i didnt think of. cwm updated from 6.0.1 to 6.0.3 or something like that. but then again the original recovery i used after the clean slate was the ez recovery which used 6.0.1 stupid question, but how does twrp work? i always used cwm. i tried flashing twrp but cwm came up when i went to recovery when i tried using twrp?! that was before i did a stock recovery so it couldnt be possible that i am running both? should i delete cwm before i use twrp? if so how? if you dont feel like going into that much detail, i can search it.
i figured out twrp. never gave it achance. ill see if that does the trick
tried twrp. still the same thing going on. gonna go to bed now. ill check back tomorrow after work to see if there are any more ideas. thanks
Problem solved. I went into my internal SD via astro and deleted all old traces of cwm as well as ez unlock and ez recovery. I was getting a generic (showed setting icon instead of regular su icon)super user screen come up prior to that, after deleting those files the regular super user came back. Rebooted into recovery via twrp , cleared cache, Davlik, flashed lean kernel and it worked. What do you think the issue was? Lingering files from ez recovery? That weird su thing?
Hi Folks, I hope this is posted in the right forum and sorry if I've missed seeing something similar already here.
I have a rooted Verizon GSIII on which I have been flashing custom ROMs and restoring nandroid backups without any problems for a while now (most recently I've been on Paranoid Android). Today I decided to try out Carbon ROM. I generated a nandroid backup using TWRP, then downloaded the ROM (the most recent nightly) and Gapps zip files using GooManager and flashed these after doing a factory reset. After rebooting the phone it seemed to start up OK... but it got as far as trying to find the network, which it unable to do. After selecting the skip option I then tried to sign in to my WiFi, but the keyboard didn't show up for me to type in the password. So I figured I'd cut my losses and just reboot into recovery and restore my PA backup. I was able to reboot into recovery and restore the backup but the PA backup pretty much did the same thing the carbon ROM did... just looped trying to find the network.
So... I'm not sure what went wrong or what to do next. Any suggestions???
I am able to boot the phone into recovery, but I'm afraid to start messing around too much without help as I'm no expert!
I do have the most recent nandroid backup and several earlier ones that did restore OK on my computer. Is there a way to flash any of these to the phone or to go back to stock?
Any help would be greatly appreciated.
Cheers.
Wipe catche dalvik factory reset then flash fresh batch of rom and gaaps if that works well getting tru start up then flash ur backup thats what i did.. If that dnt work then u gotta go tru odin back to stock
So I can't get 4.3 ROMs to reboot. I have tried several different Roms and always the same thing. Mainly Pac. It loads the first time fine, but when I reboot it just hangs on the Galaxy S4 screen. I have updated TWRP to 2.6 and tried wiping cache and dalvik between flashing the ROM and gaaps. And still nothing the only way I can get to do anything after that is to reformat and do a factory reset and the reflash the ROM. Any help would be greatly appreciated.
captainjibblet said:
So I can't get 4.3 ROMs to reboot. I have tried several different Roms and always the same thing. Mainly Pac. It loads the first time fine, but when I reboot it just hangs on the Galaxy S4 screen. I have updated TWRP to 2.6 and tried wiping cache and dalvik between flashing the ROM and gaaps. And still nothing the only way I can get to do anything after that is to reformat and do a factory reset and the reflash the ROM. Any help would be greatly appreciated.
Click to expand...
Click to collapse
So just in case anyone else runs into this problem, I figured it out myself. I am running the MDK build so the only thing you would change is th rooting process.
1. Reflash Stock using ODIN
2. Reroot http://forum.xda-developers.com/showthread.php?t=2381382
3. Install newest 2.6.3 TWRP
4. Back up Stock
5. Flash 4.3 ROM and 4.3 Gapps
I'm not sure if it was reflashing stock or the newest update to twrp but whichever. It worked.
I'm having trouble mounting the system on my Nexus 5. I initially had some trouble mounting the system when I first got the phone back in December. It took a few times to finally root the phone.
Last night, I downloaded a few Xposed Modules (nothing major, just minor tweaks) and restarted the phone. It would boot up and go to the lockscreen, but it would never progress beyond that (keeps rebooting).
I tried formatting the cache and dalvik cache. I had to reboot into recovery several times because it failed to mount anything, including the system. No dice.
I thought about trying to reflash TWRP Recovery and the Purity ROM I am on, but I can't seem to do that either in bootloader mode.
Any ideas on how to fix this?
What version of twrp are you using?
After a few hours of trial and error, I ultimately just did a Stock Rom / Unroot and downloaded/installed a new copy of TWRP, latest Purity ROM, and re-installed the ElementalX Kernel.
Everything is running smoothly now. Just have to remember to backup everything to my mac to avoid starting from scratch.
Javeline4 said:
After a few hours of trial and error, I ultimately just did a Stock Rom / Unroot and downloaded/installed a new copy of TWRP, latest Purity ROM, and re-installed the ElementalX Kernel.
Everything is running smoothly now. Just have to remember to backup everything to my mac to avoid starting from scratch.
Click to expand...
Click to collapse
I think it you probably had an old version of TWRP.
so i had been running my nexus 5 with cataclysm ROM for a while.,today i decided to do a cm12 nightly flash ...i worked well it booted fine, everthing worked well ,flashed gapps ,tibu,restored my apps .now after a reboot i kept getting "system uid inconsistent " errors.I (like a idiot) tried "fix permissions "in TWRP which resulted in a boot loop.so i decided to flash cataclysm rom freshly again.It worked well but now sometimes i get force close errors like "android.process.acore" and sometime google playstore force closes.
i am scared i might have spoiled something,
also the cm12 nightly reflashed bootloader as it was 5.0.2 and also radio ,do these things cause something to break??
how do i return to normal??
I have updated my Radio while I am still using Cataclysm and I didn't face any of the problems you mentioned above. I have also switched from Cataclysm to other ROMs (including CM12) and back couple of times in between and never faced any problems.
I generally wipe everything except Internal Memory when switching ROMs. Did you do the same?
Yes,its a clean flash.
Just a question has this got something to do with the "fix permission" thing I did in TWRP?
Even though I wiped and flashed cataclysm later??
Also I googled around .does a corrupt data partition cause these kind of errors to pop up??
Currently the occurrence of these errors is rare but I've notice reccurent notifications from google playbooks even after I remove the notifications they reappear after some time .
I've decided to use my nexus 5 for a while and see if the problems are reproducible .
But I feel like the only wrong thing I did was "fix permission " in TWRP other than that its was just regular ROM flashing.
Yes... a corrupt data partition might cause this.
Generally I wipe the following when I am flashing a new ROM:
Dalvik Cache
System
Data
Cache
As you see I wipe data as well when I am moving to completely different ROM.
Does that mean my device is not fit for flashing new Roms anymore.?
How can I fix my data partition to be as good as new??
No... What I meant was to wipe the Data partition as well before flashing a new ROM. Wipe all the partitions except the Internal Storage partition. (Note: Data and Internal Storage are not the same)
If that still doesn't work, try flashing the factory image to rollback to stock. Then again flash the recovery and try flashing a custom ROM.
You might try just reflashing the CM12 nightly and see if that fixes it. Otherwise you'll have to flash from fresh. I wouldn't recommend doing a full backup restore if possible.