Hi, new here of course but read many posts about what my issue is at this moment. Just can't figure this out.
Steps I have gone through...
Rooted, installed 7.26 gapps, CM10 and d2vzw_recovery.img
flashed with 8.13 - no issues.
Saw 8/14... rebooted into recovery, wiped dalvik, and flashed 8.14. Ever since then i am in a boot loop. Recovery back to 8.13 and i even wiped everything and still same.
Any ideas?
I am rooting back to stock with Odin now, hopefully that fixes it and i can start over.
think I figured it out
Looks like I accidentally wasnt using the right CWM recovery. Lost data, but didnt have much to lose.
8.14 on the S3..
Related
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!
Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
Click to expand...
Click to collapse
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.
Phizban said:
I followed basically the same pattern and didn't have an issue, aside from the fact that I didn't Darkside wipe (if you are using the latest clockwork touch I don't think it's necessary anymore). I also flashed the instigator kernel (6.2.1) but that was after I rebooted without issue.
Sidenote, the instigator 6.2.1 seems to possibly have some overheating trouble, so I am running the Darkside Hercules kernel for the moment, and it seems to be working well.
Click to expand...
Click to collapse
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.
Droid111 said:
Yeah, reading the thread it seems like a pretty rare problem. Somebody actually posted something similar yesterday that I missed and nobody really knew. I wasn't sure if I should Darkside wipe or not so I chose to anyways. I haven't tried flashing a new kernal but as I said I can't even get to the boot animation.
Click to expand...
Click to collapse
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.
mjwhirly said:
I would stay away from the darkside wipe, it has been reported through many threads that it can sometimes lead to problems when installing a rom. Your best bet is to just wipe data, format system, wipe dalvik cache, either format /cache or use Darksidewipe.cache not the darkside wipe that's wipes everything. Then install rom and gapps. Reboot phone and let it sit for 5 to 10 minutes, (i usually let it sit 10). From there you can decide if you want to flash one of the two available kernels, results may very with the two.
Click to expand...
Click to collapse
Thanks for the help. I'm going to try it within the next few days. Right now I have SKY-ICS going fine but I'll definitely try that.
What do the different kernels do?
Droid111 said:
Hello,
I was running the CM10 Alpha 2 for my GSII. Alpha 3 came out so I decided to update. I installed the newest CWM and the alpha 3 package, gapps and darkside wipe.
When installing I had no problems that I noticed. Everything said it worked fine. However, once rebooting the phone after darkside wipe finished, I couldn't boot up my phone. I can get past the Samsung screen, but I don't even make it to the CM animation boot screen.
I decided to pull the battery after waiting a while and go back into recovery. I did this and decided to restore my backup. My phone is stuck on "Restoring .android_secure" right now and will not work.
I can use Odin to flash back to ICS and how to came but I'm wondering why it didn't work? I know I did the procedure right, as I did it when flashing CM10 alpha 1, 1a and 2. I read about needing the latest CWM for it so I got that, too. A bit of a weird issue that I'd post in the CM10 thread if I had over ten posts.
Thanks in advance to those who can help!
Click to expand...
Click to collapse
I used TWRP and flashed over CM9 with no problems. Did it as an upgrade. Wipe system> install CM10> install gapps> Wipe cache
Several people have reported that TWRP worked for them.
Sigh... It got deleted once let me see if I can type this out again without losing it all...
So I went to update to the latest nightly this morning and cleared my cmupdater folder like I usually do before downloading it, then I rebooted and ran a TWRP backup which completed successfully. Upon rebooting the phone I was met with a spinning Cyanogenmod logo for about 20 minutes and nothing else.
I've searched around and someone said sometimes CM10 does this occasionally so I tried to flash the boot.img using fastboot, I tried several boot.img since I couldn't remember exactly which nightly I'm running. I had no luck at all.
So then I tried to use TWRP to recover to the 31st (today's) backup. Same thing. Then I tried using TWRP to flash the 31st nightly's update and same thing again. Spinning Cyanogenmod logo and me getting even more frustrated with this week's start...
Any advice where I go next? My next plan is probably to use TWRP to recover to my last successful backup just under a week ago.
digitLbraVo said:
Sigh... It got deleted once let me see if I can type this out again without losing it all...
So I went to update to the latest nightly this morning and cleared my cmupdater folder like I usually do before downloading it, then I rebooted and ran a TWRP backup which completed successfully. Upon rebooting the phone I was met with a spinning Cyanogenmod logo for about 20 minutes and nothing else.
I've searched around and someone said sometimes CM10 does this occasionally so I tried to flash the boot.img using fastboot, I tried several boot.img since I couldn't remember exactly which nightly I'm running. I had no luck at all.
So then I tried to use TWRP to recover to the 31st (today's) backup. Same thing. Then I tried using TWRP to flash the 31st nightly's update and same thing again. Spinning Cyanogenmod logo and me getting even more frustrated with this week's start...
Any advice where I go next? My next plan is probably to use TWRP to recover to my last successful backup just under a week ago.
Click to expand...
Click to collapse
Seems like you're probably gonna need to wipe data
WOW well I wish I could say I knew what had happened but it seems my 12/19 backup (ugh so far back for me...) restored it to working condition... Now the question is do I jump the loop and install the 31st's nightly! Lol.
With my luck the phone will just go nuclear at that point.
This happened to me and what I did to fix it was just flash the latest nightly like normal in TWRP and then reboot. Make sure to wipe cache/dalvik.
pOLLYpOCKET said:
This happened to me and what I did to fix it was just flash the latest nightly like normal in TWRP and then reboot. Make sure to wipe cache/dalvik.
Click to expand...
Click to collapse
I'll keep that in mind if it happens again. I ended up restoring to the 19th, updated all my apps that were out of date and downloaded missing ones, ran a backup today, then updated to the 31st nightly and it worked fine this time.
Your problem had a simple solution wipe data and system each time you flasha new Rom
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?
So I haven't used my Xoom (wifi) in literally 2 years or so, I grabbed it from the basement today thinking I'd update it and see what I could do.
I jacked it up pretty good as fsr as I'm concerned and not knowing what to do since its been so long.
I was running eos rom and running their nightlies like (46) or something.
I realized I didnt have my gapps (no playstore etc). I booted into recovery and realized I had twrp 2.3.3.0. I went into the dev section and found twrp, the bigpart one and was going to flash cm11. I downloaded the newest twrp like 2.6.3, booted into recovery and flashed the new twrp version. I had already out cm11 on my sd card and was proceeding to wipe everything as it said to do, I wiped my stuff and it kept saying failed. I went ahead and flashed cm11 thinking it was just saying failed and it cleared everything.
When it xomes up it says it needs to be reset, I hit reset it takes me to recovery and the twrp blue welcome screen is stuck, wont let me into do anything
What do I need to do, can anyone please help me?
hey y'all i have a 6045i US and it keeps bootlooping it all started by flashing CM 12.1 4/03/16 verison by the marionetteso i also flashed gapps xposed and root so it gave me the bootloops so what i did is wipe data factory reset nothing worked so i flashed another ROM wipe data everything and flashed bootloop fix kernel and nothing,same results im at the homescreen and im doing things and bootloops from there even recovery rebooted alot lol im not sure why so i flashed another older verison of it (i risked btw) and it worked so with that recovery i flashed a TWRP backup from one of the threads to stock ROM wipe data etc. and nothing same results!!! bootloops from homescreen so if theres another way to fix id appreciate it so much a clean install as in out of the box also i tried the alcatel upgrade app and nothing everytime i shut down the phone and plug the USB it just turns on for some reason bootloader works still with fastboot commands so i dont know whats going on this is my first issue with this phone,thank you
EDIT: fixed i finally got the alcatel app to work mods please close this thread