[Q] phone will not boot after installing any kernel - Verizon Samsung Galaxy S III

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?

Related

Boot Loop Issues

Okay...So I'm having boot loop issues ever since I tried to flash Vincom's Superlite rom. Before attempting to switch to a different rom I had a a older version of CWM, not sure what it was....But I was under the impression I needed CWM touch to be able to use the Superlite rom. So I flashed sk8's CWM touch using a older CWM...With touch, I flashed the Dark Side Super Wipe 3x's and also did the wiped dalvek 3x's.....After all the wiping I flashed the superlite rom....my previous rom was CM10, by the way.....i got stuck in bootloop so I tried the darkside-wipe-cache, because that solved all my bootloop issues with the CM 9 and CM 10.......I tried to revert back to CM 10 via flash and got stuck in a boot loop....I tried multiple times to reflash and wipe with both superlite and CM 10...I couldnt get anything...So I gave up and flashed to stock firmware UCL6 via CWM Touch.....My phone is functional I just dont want this stock "rom"...I want to be able to use CM 10 again because the t-mobile radios dont work with the stock....Im thinking its the CWM....I tried using different kernels as well...and i still get a boot loop......
daygobaker said:
Okay...So I'm having boot loop issues ever since I tried to flash Vincom's Superlite rom. Before attempting to switch to a different rom I had a a older version of CWM, not sure what it was....But I was under the impression I needed CWM touch to be able to use the Superlite rom. So I flashed sk8's CWM touch using a older CWM...With touch, I flashed the Dark Side Super Wipe 3x's and also did the wiped dalvek 3x's.....After all the wiping I flashed the superlite rom....my previous rom was CM10, by the way.....i got stuck in bootloop so I tried the darkside-wipe-cache, because that solved all my bootloop issues with the CM 9 and CM 10.......I tried to revert back to CM 10 via flash and got stuck in a boot loop....I tried multiple times to reflash and wipe with both superlite and CM 10...I couldnt get anything...So I gave up and flashed to stock firmware UCL6 via CWM Touch.....My phone is functional I just dont want this stock "rom"...I want to be able to use CM 10 again because the t-mobile radios dont work with the stock....Im thinking its the CWM....I tried using different kernels as well...and i still get a boot loop......
Click to expand...
Click to collapse
Bump? Anybody?
Manually do the following wipes: wipe data/factory reset, cache, dalvik, format/data, format/system, format/cache all x3. Then reflash his ROM followed by gapps. Let it sit for 10 min as caches need time to settle and the initial boot always takes much longer.
Which version of cwm touch are you on?
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398[/QUOTE]
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
daygobaker said:
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
Click to expand...
Click to collapse
Clear cache clear dalvik cache flash radio if you has issues refresh Rom from scratch DO NOT REFLASH RADIO
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
daygobaker said:
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
Click to expand...
Click to collapse
Nope. Just wipe dalvik and cache and flash it. But it's likely to be an exercise in folly anyway, because it you have uclf5 and you flash uclf6, you still have the uclf5 libs. Changing the radio libs is a much more complicated procedure and without doing so you get limited benefit from flashing a new radio. But sometimes it does help anyway. Might be worth a try if you're getting poor connectivity.
daygobaker said:
Success!!! Everything works...Thank you so much....just one more question....what is the proper way of reflashing a radio? Do I have to format system and reflash the rom everytime I want to try a different radio?
Click to expand...
Click to collapse
No need to do a whole clean install simply to switch out the radio. I 95% positive you only need to wipe cache, dalvik, flash radio and reboot. I only changed radio once and it was during a clean install so I never really paid that close attention to the steps when you put it over the top of your ROM. Do what I said and you should be fine.
Or grab the torch and pitchfork. Jk there's nothing to worry about
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398
Still bootlooping...
Mike on XDA said:
Manually do the following wipes: wipe data/factory reset, cache, dalvik, format/data, format/system, format/cache all x3. Then reflash his ROM followed by gapps. Let it sit for 10 min as caches need time to settle and the initial boot always takes much longer.
Which version of cwm touch are you on?
Click to expand...
Click to collapse
Hey Mike,
I've been bootlooping as well. A little background...
I'm on CWM Touch 6.0.1.2 _sk8erwitskil_
I was on cm-10-20120812-EXPERIMENTAL-syyrocket-alpha3
Yesterday, I went to cm-10-20120912-UNOFFICIAL-skyrocket
I was ok until just a little bit ago I was on a call and the phone rebooted. Since then, bootloop-city.
I tried this procedure, reflashed 0912 and no joy. I think, at this point, the unreliability of CM10 (at this time) has worn thin (no dis to all the awesome developers out there) and I just want to go back to a stable CM9.
Any suggestions?
Thanks,
Bob
EDIT: Ya know, just when you think all is lost, there is Nandroid! I'm back to CM9 and no longer bootlooping!

[Q] Having slight problems with CROMI 3.0.4

First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
furou said:
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
Click to expand...
Click to collapse
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
I think I read somewhere about a CROMI forum? If there is one, can someone point me to it?
sbdags said:
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
Click to expand...
Click to collapse
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
furou said:
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
Click to expand...
Click to collapse
Either is ok but kernel Installer is faster to do

[Q] TWRP 2.6.6 on Carbon unable to flash Synergy

Title kind of tells the story trying to flash to Synergy-yes md5 passed on the download.I wiped everything twice and then cache and davlik seperately and launched TWRP and when I try to install it just hangs and then eventually prompts me to close the app.
Do I need to flash back to stock and then install a custom ROM?I wipe everything but remain on Carbon of course.
For those running Synergy what recovery were you using-any issues with TWRP.What process worked for you?
Luckily my restore back to Carbon worked no problem.
Thanks
I wipe system internal storage data a the caches. You may also want to try cwm as it might work better. Make sure your download for synergy is for the vzw one.
Sent from my SCH-I535

[Q] 4.3 not rebooting on Verizon Galaxy S 4

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.

[Q] Change recovery-Rom

HI, i have been having isues with my asus tf101 baterry, about one month ago it suddenly charge and discharges, like: 10%-25%-40%-70%-80%-100%...I made a factory reset but nothing. 2 weeks ago, it solved alone, without do anything, and was ok for 2 weeks, now again i have the problem..
i have installed cwm recovery, i want to change to android revolution rom, to see if the problem finish:
1 question: How i change from cwm to twrp recovery? installing twrp from cwm using a zip? is there no problem?? or downloading goomanager, installing recovery script?? Is there any problem to use cwm or twrp( i have read, to instal kk i dont use cwm)?
2 question, what rom is stable to try to solve this? i see kk 4.3 etc, but i just one my baterry works ok...
3 question, is there any way to clean absolutely the stock rom? i tried wipe cache, dalvik, factory reset(again) but nothing solve.
4 question, is possible to wipe ALL including system, and install the asus stock rom using zip¿?
Thanks for your atention, please be the most specifically possible because i am new on this, and i just one my tablet for study(read books).
I have a asus tf101 b70 root, with CWM recovery is a old version 5.0.26 something..
cesar_cjx said:
HI, i have been having isues with my asus tf101 baterry, about one month ago it suddenly charge and discharges, like: 10%-25%-40%-70%-80%-100%...I made a factory reset but nothing. 2 weeks ago, it solved alone, without do anything, and was ok for 2 weeks, now again i have the problem..
i have installed cwm recovery, i want to change to android revolution rom, to see if the problem finish:
1 question: How i change from cwm to twrp recovery? installing twrp from cwm using a zip? is there no problem?? or downloading goomanager, installing recovery script?? Is there any problem to use cwm or twrp( i have read, to instal kk i dont use cwm)?
2 question, what rom is stable to try to solve this? i see kk 4.3 etc, but i just one my baterry works ok...
3 question, is there any way to clean absolutely the stock rom? i tried wipe cache, dalvik, factory reset(again) but nothing solve.
4 question, is possible to wipe ALL including system, and install the asus stock rom using zip¿?
Thanks for your atention, please be the most specifically possible because i am new on this, and i just one my tablet for study(read books).
I have a asus tf101 b70 root, with CWM recovery is a old version 5.0.26 something..
Click to expand...
Click to collapse
Q1: I think you can just flash the new recovery via the current recovery if you have the new recover zip file.
Q2: Kat Kiss works fine for me.
Q3: If you want to completely return to stock, you would have to use NVFlash. There are tons of instructions on the Dev thread. I primarily use Tubuntu for flashing with NVFlash. [http://forum.xda-developers.com/showthread.php?t=1995157]
You can find other images as well. I used a stock image once to RMA the tablet but now I'm not sure where I got it. This method will ensure that every bit in your memory is exactly as it left the factory. Including the bootloader, recovery partition and everything else.
Q4: Refer Q3.
Download flashable TWRP 2.6.3.11 zip for TF101:
http://forum.xda-developers.com/devd...ct/dl/?id=3280
You should use TWRP for KatKiss ROMs, do not use CWM
Flash that Zip from CWM then reboot fully into your current ROM, then reboot into Recovery to check it has flashed properly
From TWRP you can wipe everything and flash KatKiss & Gapps
*Detection* said:
Download flashable TWRP 2.6.3.11 zip for TF101:
http://forum.xda-developers.com/devd...ct/dl/?id=3280
You should use TWRP for KatKiss ROMs, do not use CWM
Flash that Zip from CWM then reboot fully into your current ROM, then reboot into Recovery to check it has flashed properly
From TWRP you can wipe everything and flash KatKiss & Gapps
Click to expand...
Click to collapse
Is this the same process for going from TWRP to TWRP? just "install" the newest version from recovery and do the reboots?
stache12 said:
Is this the same process for going from TWRP to TWRP? just "install" the newest version from recovery and do the reboots?
Click to expand...
Click to collapse
Yep, so long as you reboot into your ROM after flashing the new TWRP before booting back into recovery
Thanks for your reply, i will tray soon. So i want to clean the asus stock room to see if battery goes ok, i tried wipe data, cache, dalvik, with cwm, but nothing.
If i install twrp what more options can i try before change the rom? what more wipe do i need?? and finally, if i change the rom, is possible to go back to asus stock just flashing from recovery? or how should i do?
Apart from wiping the ROM (SYSTEM) there's not much else you can wipe, you could try wiping the same as you have already done, but from TWRP, see if that makes any difference, maybe the battery is coming to the end of its life
You can flash stock ASUS ROMs back again from TWRP yes, but you will wipe your recovery & ROM back to 100% stock by doing it
Best thing to do is to make a full Nandroid Backup from TWRP before flashing any custom ROMs, save it to MicroSD Card, then if you want to go back to the way it is now, just restore the backup from TWRP
That way you keep TWRP and can switch between as many ROMs as you like and always have your stock backup to go back to whenever you want
46999589
*Detection* said:
Apart from wiping the ROM (SYSTEM) there's not much else you can wipe, you could try wiping the same as you have already done, but from TWRP, see if that makes any difference, maybe the battery is coming to the end of its life
You can flash stock ASUS ROMs back again from TWRP yes, but you will wipe your recovery & ROM back to 100% stock by doing it
Best thing to do is to make a full Nandroid Backup from TWRP before flashing any custom ROMs, save it to MicroSD Card, then if you want to go back to the way it is now, just restore the backup from TWRP
That way you keep TWRP and can switch between as many ROMs as you like and always have your stock backup to go back to whenever you want
Click to expand...
Click to collapse
Thanks!! I will try, but apart from wipe system(rom) what more wipes can i try without erase the rom?..I think not, because a week ago the battery was perfect working...i hope so.
CACHE,
DALVIK CACHE,
FACTORY RESET,
INTERNAL STORAGE,
FORMAT DATA
Only other 2 options are SYSTEM & EXTERNAL STORAGE

Categories

Resources