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.
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?
I was running LiquidSmooth 2.9. Decided to try the latest KK nightly. Downloaded everything, made a backup, etc. Went to flash and it said (status 7) error. Tried again, same thing. Decided to update to the latest TWRP and try again. Same error. Tried one more time and it worked. After the rom was loaded I immediately noticed that the rom was not stable enough for a daily driver.
Booted into recovery and tried to restore to my previous backup. For whatever ready TWRP could not locate the backup. I tried to move the back up for a while but it wouldn't move to the correct folder. I said screw it I will just download the Liquid Smooth 2.37 which was the latest official release and just reflash. Downloaded everything, then flashed it. Everything set successful, gaps and rom, but now it wont get past the splash screen. I have reflashed like 5 times now all without issue but stuck at splash screen. I can get into recovery fine.
What is my next step to revert back to my previous backup or reflash to a working rom? Any help would be greatly appreciated.
Odin my friend
Sent from my SCH-I535 using Tapatalk
I had the same problem on kk i had to do a factory reset wipe catche dalvik then flash liquid smooth kk pa gapps im working fine. Honestly my own opinion i prefer liquid 2.37 over kk. I read couple post ppl had to get the latest cwm recovery to flash KK roms
Were you able to revert back to 2.37? I'm stuck here in limbo at the moment.
1967ls2 said:
Were you able to revert back to 2.37? I'm stuck here in limbo at the moment.
Click to expand...
Click to collapse
Yes after couple tries I just factory reset flashed rom
i did these steps
factory reset install rom 2.9 or 2.37 then after all set up i went bck to recovery flashed a backup file I had of 2.37
twistedillutions said:
Yes after couple tries I just factory reset flashed rom
i did these steps
factory reset install rom 2.9 or 2.37 then after all set up i went bck to recovery flashed a backup file I had of 2.37
Click to expand...
Click to collapse
what recovery are you using? TWRP or CWM?
I'm getting no where.
1967ls2 said:
what recovery are you using? TWRP or CWM?
I'm getting no where.
Click to expand...
Click to collapse
Twrp
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
sheltont said:
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
Click to expand...
Click to collapse
Use Odin to restore to the stock ROM. Download the stock rom from samfirmware.com and flash it in Odin as PDA. Then, use the latest recovery (either TWRP, CWM, OR PhilZ) from @Android-Andi's recovery thread in the Dev section. You should now be able to flash any ROM you want to. Make sure you do a backup and a wipe system, cache, Dalvik, data, and android secure (if it's an option.)
Sent from my SGH-T989
thanks and....
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
sheltont said:
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
Click to expand...
Click to collapse
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
yep
jrc2 said:
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did twice and it's still hung after apparent success installation according to Odin. I've tried it twice.
No success
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
sheltont said:
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
Click to expand...
Click to collapse
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
good idea but still no success....
jrc2 said:
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
Hi, I've retried all that this morning-i must admit that I didn't know about wiping cache after install, however it's not made any difference, and still hangs on first boot...
Any other ideas? Thanks for all your help.
Happy success
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
sheltont said:
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
Click to expand...
Click to collapse
Which version of PhilZ? And I have found that TWRP 2.7.1.0 works better than other versions for KK.
Sent from my SGH-T989
Use latest Philz touch recovery. And use the rom and gapps compatible to your tab. Don't forget to reset to factory setting, clear cache and wipe dalvic cache before flashing the rom and gapps ☺
Sent from my GT-P3100 using XDA Free mobile app
Hi mates.
So, I was running CM12 nightlies on my phone but it began to get slow and buggy.
I decided to go back to stock 4.4.4, ans then flash CM11 on dit
I did full wipe (data, system, cache, dalvik), installed stock 4.4.4 (latest official build)
Then i downloaded CM installer but couldn't get it to work.
So I used Nexus foot toolkit on PC, but the flashing process went wrong somehow, just when it reboots the phone to recovery, nothing happened, no flashing process whatsoever.
From this moment, my problem had appeared
So I rebooted normally, downloaded CM11 and I was unable to flash it. Signature check failed.
I've tried OTA 5.0.1, not working either, same error.
So I am currently running latest 4.4.4 without any problem, but even after an other full wipe I'm not able to flash anything, custom or stock. My recovery is the latest TWRP from the Google play app.
Could you please help me ? I don't mind wiping my phone, and I'd prefer a "no PC" solution but I still can use a PC if needed.
Thanks
visclo49 said:
Hi mates.
So, I was running CM12 nightlies on my phone but it began to get slow and buggy.
I decided to go back to stock 4.4.4, ans then flash CM11 on dit
I did full wipe (data, system, cache, dalvik), installed stock 4.4.4 (latest official build)
Then i downloaded CM installer but couldn't get it to work.
So I used Nexus foot toolkit on PC, but the flashing process went wrong somehow, just when it reboots the phone to recovery, nothing happened, no flashing process whatsoever.
From this moment, my problem had appeared
So I rebooted normally, downloaded CM11 and I was unable to flash it. Signature check failed.
I've tried OTA 5.0.1, not working either, same error.
So I am currently running latest 4.4.4 without any problem, but even after an other full wipe I'm not able to flash anything, custom or stock. My recovery is the latest TWRP from the Google play app.
Could you please help me ? I don't mind wiping my phone, and I'd prefer a "no PC" solution but I still can use a PC if needed.
Thanks
Click to expand...
Click to collapse
stop using toolkits, learn something for a change
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Hi.
Im a noob on XDA but have enjoyed the freedom of custom roms for some time now on my note 4 (N910C). So far it has only been stock based touchwiz roms. A few days ago i decided to give CM13 a go and since then i have been unable to revert back. Every touchwiz rom (stock and custom) i have tried just ends in a bootloop but when i flash CM13 again it boots up just fine.
I have tried flashing numerous android 6.0.1 stock roms through odin, even from different regions but still for the same version. Its always stuck in a bootloop.
Tried flashing stock and then immediately flashing custom stock based rom (both clean install after wiping and trying to dirty flash over stock rom)
I have done all the suggestions of factory resetting, wiping caches and you name it after clean flashes and even tried them with dirty flashes. Whatever i do i cannot get any stock or stock based rom to boot up.
A few months ago i tried out cm12.1 and had no problem going back to a stock based rom, but after CM13 my phone absolutely refuses to boot anything stock or stock based.
I would appreciate any advice and suggestions. Please ask if theres any more info needed of my device or roms i already tried.
JackalJC said:
Hi.
Im a noob on XDA but have enjoyed the freedom of custom roms for some time now on my note 4 (N910C). So far it has only been stock based touchwiz roms. A few days ago i decided to give CM13 a go and since then i have been unable to revert back. Every touchwiz rom (stock and custom) i have tried just ends in a bootloop but when i flash CM13 again it boots up just fine.
I have tried flashing numerous android 6.0.1 stock roms through odin, even from different regions but still for the same version. Its always stuck in a bootloop.
Tried flashing stock and then immediately flashing custom stock based rom (both clean install after wiping and trying to dirty flash over stock rom)
I have done all the suggestions of factory resetting, wiping caches and you name it after clean flashes and even tried them with dirty flashes. Whatever i do i cannot get any stock or stock based rom to boot up.
A few months ago i tried out cm12.1 and had no problem going back to a stock based rom, but after CM13 my phone absolutely refuses to boot anything stock or stock based.
I would appreciate any advice and suggestions. Please ask if theres any more info needed of my device or roms i already tried.
Click to expand...
Click to collapse
You might be having kernel issues. If the stock you're flashing is a flashable zip then it might not include the stock kernel, if it doesn't include the stock kernel then its leaving the custom kernel from CM13. If that's the case it won't work because stock won't work with a CM kernel.
You said you did the wipes when you flashed, did you mean that you did factory reset, wipe cache and wipe dalvik cache? Or did you mean that you did the advanced wipe options to wipe system partition and data partition before flashing?
If you didn't do the advanced wipe before flashing then it might help if you did them before flashing. Wipe system and wipe data then factory reset then flash ROM then wipe cache and dalvik after flashing then reboot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
You might be having kernel issues. If the stock you're flashing is a flashable zip then it might not include the stock kernel, if it doesn't include the stock kernel then its leaving the custom kernel from CM13. If that's the case it won't work because stock won't work with a CM kernel.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
I flash stock roms through Odin with the .tar.md5 file.
JackalJC said:
Hi.
Im a noob on XDA but have enjoyed the freedom of custom roms for some time now on my note 4 (N910C). So far it has only been stock based touchwiz roms. A few days ago i decided to give CM13 a go and since then i have been unable to revert back. Every touchwiz rom (stock and custom) i have tried just ends in a bootloop but when i flash CM13 again it boots up just fine.
I have tried flashing numerous android 6.0.1 stock roms through odin, even from different regions but still for the same version. Its always stuck in a bootloop.
Tried flashing stock and then immediately flashing custom stock based rom (both clean install after wiping and trying to dirty flash over stock rom)
I have done all the suggestions of factory resetting, wiping caches and you name it after clean flashes and even tried them with dirty flashes. Whatever i do i cannot get any stock or stock based rom to boot up.
A few months ago i tried out cm12.1 and had no problem going back to a stock based rom, but after CM13 my phone absolutely refuses to boot anything stock or stock based.
I would appreciate any advice and suggestions. Please ask if theres any more info needed of my device or roms i already tried.
Click to expand...
Click to collapse
Usually if it bootloops after flashing with Odin, you boot to stock recovery and factory reset/wipe cache and it should boot after that.
The times that you tried stock and then went back to CM13, are you rooting and reflashing TWRP again so you can flash back to CM13? Or is it leaving custom recovery on the device even after flashing with Odin? If its leaving TWRP on the device then Odin isn't flashing correctly.
Are you flashing the full stock firmware in Odin? Or are you flashing a modified stock .tar?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Usually if it bootloops after flashing with Odin, you boot to stock recovery and factory reset/wipe cache and it should boot after that.
The times that you tried stock and then went back to CM13, are you rooting and reflashing TWRP again so you can flash back to CM13? Or is it leaving custom recovery on the device even after flashing with Odin? If its leaving TWRP on the device then Odin isn't flashing correctly.
Are you flashing the full stock firmware in Odin? Or are you flashing a modified stock .tar?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
I have tried all the factory reset/wipe cache suggested on other threads and websites i have found regarding bootloops.
When going back to CM13 after trying methods to get stock back i flash TWRP again as flashing stock through Odin replaces TWRP with stock recovery again and then do a restore of CM13 through TWRP with all my necessary apps on, much easier than installing everything again after each try (a fresh install of CM13 also works fine with no problems). I also tried various versions of Odin just in case it was a problem with the version i used but every time i get the same same results.
I am flashing full pure stock from sammobile.