I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
jcxmej said:
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Click to expand...
Click to collapse
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
RikRong said:
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
Click to expand...
Click to collapse
Like I said on first post Im using TWRP now. Previously I was using safestrap. I removed it and installed TRWP. Anyways thanks.
PantherVT said:
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
Click to expand...
Click to collapse
Thanks man. I will upgrade TWRP or reinstall it first. Thanks for that tip. Will post again if it doesnt work.
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
jcxmej said:
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
Click to expand...
Click to collapse
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
jco23 said:
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
Click to expand...
Click to collapse
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
jcxmej said:
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
Click to expand...
Click to collapse
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
jco23 said:
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
Click to expand...
Click to collapse
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
jcxmej said:
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
Click to expand...
Click to collapse
which ROM are you trying to install?
jco23 said:
which ROM are you trying to install?
Click to expand...
Click to collapse
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
jcxmej said:
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
Click to expand...
Click to collapse
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
jco23 said:
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
Click to expand...
Click to collapse
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
jcxmej said:
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
Click to expand...
Click to collapse
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
jco23 said:
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
Click to expand...
Click to collapse
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
jcxmej said:
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
Click to expand...
Click to collapse
I don't think changing the kernel will do it.... I suspect the issue is with your recoveries - will respond in other thread....
Related
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
hockeyfamily737 said:
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
Click to expand...
Click to collapse
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
No OC kernel....Just trying to get the nightly to run before worrying about that. I can nanadroid back to any of my former roms with no problem. I'm going to try just doing a ONLY a cache wipe and load it again......just as soon as I run out of patience with my black "ANDROID_" screen of frustration, I'm currently looking at for the last 7 minutes.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
Yeah........It's a no go. Nand back to 7.0.2, reboot to recovery, wipe cache only, instal zip for Nightly 63......."ANDROID_".....DAMMIT!!!!
I'm back to 7.0.2 again until someone has something else I can try.
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Interesting... I'm using 3.0.1. I'll try updating it tonight.
sent from my Ginger-Hero CDMA
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Just another quick note.....To anyone having problems overclocking the new nightly builds. You need to use the ext. 4 overclock kernel, which can be downloaded here......http://forum.xda-developers.com/showthread.php?t=925451&page=239
hockeyfamily737 said:
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Nevermind.
janko10 said:
Is there a way to update CWM without burning a new image to SD card? I currently have 3.0.1.0 as well and I don't want to wipe my rom or SD card just to update to 3.0.2.8 but I can't seem to find any other way to do that.
Sorry but this is my first Andriod device so bit of a noob here.
Click to expand...
Click to collapse
I was going to say ROM Manager, but forgot it doesn't have 3.0.2.8 for Nook.
Here is the recovery zip file, flash from CWR. http://db.tt/gDlb5mw
- download to your SD card for Nook, boot into CWR, choose install zip from SD/choose zip, flash, reboot recovery
On my nexus 7 8gb model I tried flashing mmuzzyrom for grouper. No success. So I thought it was twrp that was causing the problem, so I flashed cwm and tried that. Also not successful. So then I thought it might be the roms, so I tried to flash cyanogenmod nightly and it didn't work. I noticed when I try to flash a rom it doesn't mount /system or anything but when I flash gapps it mounts /system and I think it actually works. Any ideas? Thanks
Did you run factory reset in recovery before flashing the rom?
Sent from my Galaxy Nexus
Pirateghost said:
Did you run factory reset in recovery before flashing the rom?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Won't that delete the rom? And my nandroid?
skiman10 said:
Won't that delete the rom? And my nandroid?
Click to expand...
Click to collapse
no. in fact you have to run factory reset in your custom recovery (CWM or TWRP) before flashing any rom....otherwise you get EXACTLY what is happening to you now. This is a well documented thing when flashing roms.
running FACTORY RESET in a custom recovery will wipe everything but /data/media where your 'sdcard' resides
Pirateghost said:
no. in fact you have to run factory reset in your custom recovery (CWM or TWRP) before flashing any rom....otherwise you get EXACTLY what is happening to you now. This is a well documented thing when flashing roms.
running FACTORY RESET in a custom recovery will wipe everything but /data/media where your 'sdcard' resides
Click to expand...
Click to collapse
Ah I get it now, actually I was trying to perform a dirty flash but I guess that isn't gonna work
Well thanks for your help
if you want your new rom to be performing well, its best NOT to do a dirty flash. some roms you can dirty flash between, but most require a factory reset.
you can almost ALWAYS do a dirty flash when upgrading from one version of the same custom rom to the next, but completely different custom roms will require a reset
Pirateghost said:
if you want your new rom to be performing well, its best NOT to do a dirty flash. some roms you can dirty flash between, but most require a factory reset.
you can almost ALWAYS do a dirty flash when upgrading from one version of the same custom rom to the next, but completely different custom roms will require a reset
Click to expand...
Click to collapse
Ok thanks for that info ill see what happens.
I did it!
Thanks so much! I'm a frickin idiot for thinking I could dirty flash.
skiman10 said:
Thanks so much! I'm a frickin idiot for thinking I could dirty flash.
Click to expand...
Click to collapse
You can get away with it when the ROM you are coming from is quite closely related to the ROM you are going to. For instance, if you were flashing CM 10.1 nightlies over the course of a few weeks. But in general, it's not really a great idea - it is a terrible idea for unrelated ROMs.
The best practice is probably to use something like TiBu or Carbon, and ONLY back up market apps and their data - never pre-installed system apps (e.g. gapps). For home screens, you can just use a launcher that allows backup/restores of it's home screen configurations.
Even in this case, you can still run into UID issues restoring market apps & data - it appears that the Android boot process assigns UIDs in a serial fashion (without any gap between system apps and market apps), so as soon as it runs through all the .apks it finds in /system/app, it continues with the next (+1) UID available for the .apks found in /data/app. The net result of this is if you install a ROM that has more .apks in /system/app than your prior ROM did, it is likely you will have common-uid collision issues. The custom recovery "fix permissions" can try and fix this up - I'm not sure if they cover all the bases though (multiple user accounts, stuff in /data/app-secure, etc).
good luck
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
jimmyco2008 said:
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
Click to expand...
Click to collapse
are you mounting system first? never used CWM on this device, but in TWRP, they install just fine. I believe that most devs use TWRP (although, it should not make a difference).
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
jimmyco2008 said:
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
Click to expand...
Click to collapse
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
jcxmej said:
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
Click to expand...
Click to collapse
are you sure you uninstalled SS via the app (and not via the android system)?
jco23 said:
are you sure you uninstalled SS via the app (and not via the android system)?
Click to expand...
Click to collapse
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
jcxmej said:
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
Click to expand...
Click to collapse
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
jco23 said:
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
Click to expand...
Click to collapse
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
jcxmej said:
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
Click to expand...
Click to collapse
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
jco23 said:
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
Click to expand...
Click to collapse
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
jcxmej said:
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
Click to expand...
Click to collapse
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
jco23 said:
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
Click to expand...
Click to collapse
Just installed SS and unnistalled it thru the app. I ll wait for any reboots before I reflash the ROM. Hope this works. (finger crossed)
This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.
Try flashing a different compatible kernel.
ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app
I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!
Glad it's working out for you.
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.
Hi all
Got an I9505 on O2 and since lollipop update it restarted a few times by itself. Now it keeps going into a loop where it will restart and the home screen loads, you can use it for about 20-30 seconds and it will reboot again!
Initially when I researched I though it was an app problem but couldn't find the culprit. Then I took it into the Samsung repair centre and they said it needed a clean flash by them. This didn't work and they fitted a new mother board and this still hasn't worked.
I can say that it has twice happened when the Wifi hasn't been working properly so I have turned it off but other than that I have no idea!
Also I have tried rebooting into safe mode but it still does it, aaarrrggghhhh!!!
Any ideas where I can go from here please?
P
Return to kitkat if you can. Otherwise use a custom rom. These would be my suggestions. Since Samsung's repair couldn't fix it, warranty should not be a problem anymore.
Thanks, I am more than willing to try a Custom ROM. Any recommendations? And how easy is it as never done before!
PJBXDA said:
Thanks, I am more than willing to try a Custom ROM. Any recommendations? And how easy is it as never done before!
Click to expand...
Click to collapse
It's fairly easy. Depending on what S4 model you have. Some models have a locked bootloader and that makes the whole thing trickier.
This is what I did:
1) Root with CF-Auto-Root. Thread here.
2) Backup all my apps.
3) Install a custom recovery (TWRP). Download and instructions here.
4) Flash custom rom. Most roms have their own instructions.
You can skip 1 and 2 if you don't want to backup.
Installing a custom recovery can be done using Odin. I recommend TWRP since it's the only one I've used.
Lollipop GPE rom. I've used this rom and didn't have any issues. CM12 seems a bit faster, but the GPE was more stable and bug-free.
Thanks I tried to install the CM12 before you posted using the instructions there but it failed, I assume that it needs to be rooted.
PJBXDA said:
Thanks I tried to install the CM12 before you posted using the instructions there but it failed, I assume that it needs to be rooted.
Click to expand...
Click to collapse
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Go to Install (if on TWRP), go to the location where you saved the downloaded rom zip and select it. The swipe the slider to begin flashing. Afterwards flash the gapps zip. Reboot.
Also, don't use the recovery posted in the CM12 thread. It was specially made by the dev and will convert your file system to f2fs. What it basically means is that it will wipe your internal storage completely.
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Thanks, doing that now
Click to expand...
Click to collapse
PJBXDA said:
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Thanks, doing that now
Click to expand...
Click to collapse
On the CF-Root page it says to open Odin and click on the PDA button but I cannot find a PDA button!
Edit: It is the AP button on the newer version!
Click to expand...
Click to collapse
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Go to Install (if on TWRP), go to the location where you saved the downloaded rom zip and select it. The swipe the slider to begin flashing. Afterwards flash the gapps zip. Reboot.
Also, don't use the recovery posted in the CM12 thread. It was specially made by the dev and will convert your file system to f2fs. What it basically means is that it will wipe your internal storage completely.
Click to expand...
Click to collapse
When you say go to install, do you mean install update... in the recovery menu? I do not have an install from zip option
PJBXDA said:
When you say go to install, do you mean install update... in the recovery menu? I do not have an install from zip option
Click to expand...
Click to collapse
You don't have a custom recovery installed. That is probably the stock recovery. You can't flash a rom using the stock recovery.
You absolutely need a custom recovery if you want to flash a custom rom.
Custom recoveries are: TWRP (Team Win Recovery Project), CWM (ClockworkMod Recovery) and PhilZ Touch Recovery. Either one should work. But you necessarily need one.
GDReaper said:
You don't have a custom recovery installed. That is probably the stock recovery. You can't flash a rom using the stock recovery.
You absolutely need a custom recovery if you want to flash a custom rom.
Custom recoveries are: TWRP (Team Win Recovery Project), CWM (ClockworkMod Recovery) and PhilZ Touch Recovery. Either one should work. But you necessarily need one.
Click to expand...
Click to collapse
Thanks I have installed TWRP, then it asked me to install Busybox which I did. Tried to Install from Zip and it went back to the original recovery and now when I am trying to restart the phone I just get messages telling me things have stopped working (Google play, settings etc etc) and a black screen!
Currently factory resetting and will try again
PJBXDA said:
Thanks I have installed TWRP, then it asked me to install Busybox which I did. Tried to Install from Zip and it went back to the original recovery and now when I am trying to restart the phone I just get messages telling me things have stopped working (Google play, settings etc etc) and a black screen!
Currently factory resetting and will try again
Click to expand...
Click to collapse
Follow the link I gave you. They have several instrunctions on how to install TWRP. You can install TWRP with Odin too.
Here, There are 3 ways to install. Use Odin. It doesn't require root and should be the easier one. Just UNTICK auto-reboot in Odin before flashing. Once it's done, turn the phone off and use the key combo to get into TWRP recovery.
GDReaper said:
Follow the link I gave you. They have several instrunctions on how to install TWRP. You can install TWRP with Odin too.
Here, There are 3 ways to install. Use Odin. It doesn't require root and should be the easier one. Just UNTICK auto-reboot in Odin before flashing. Once it's done, turn the phone off and use the key combo to get into TWRP recovery.
Click to expand...
Click to collapse
I think I am in, got through to the TWRP recovery and flashed the files but now I have a blue face with a pulsing white light behind it and have had for about 10 minutes. Any idea what is happening please?
PJBXDA said:
I think I am in, got through to the TWRP recovery and flashed the files but now I have a blue face with a pulsing white light behind it and have had for about 10 minutes. Any idea what is happening please?
Click to expand...
Click to collapse
I guess that's the CM12 logo. First boot after flashing always takes some time because the rom is configuring stuff.
If you still don't get into android, turn off the device and turn it on again. If you've done everything correctly there is no reason why it shouldn't boot.
GDReaper said:
I guess that's the CM12 logo. First boot after flashing always takes some time because the rom is configuring stuff.
If you still don't get into android, turn off the device and turn it on again. If you've done everything correctly there is no reason why it shouldn't boot.
Click to expand...
Click to collapse
It is their logo but it seems to be taking forever, any idea how long a first boot should take?
PJBXDA said:
It is their logo but it seems to be taking forever, any idea how long a first boot should take?
Click to expand...
Click to collapse
It shouldn't take that long. For me it always took under 5 minutes. Tell me exactly what you did.
GDReaper said:
It shouldn't take that long. For me it always took under 5 minutes. Tell me exactly what you did.
Click to expand...
Click to collapse
Did as you said, in the end I tried flashing the other GPE ROM and that has worked but I do not really like it. Trying the Cynogen again by downloading direct to the SD card and not copying it over. I want to say a very big thank you GDReaper for all your help, it is and has been very much appreciated.
PJBXDA said:
Did as you said, in the end I tried flashing the other GPE ROM and that has worked but I do not really like it. Trying the Cynogen again by downloading direct to the SD card and not copying it over. I want to say a very big thank you GDReaper for all your help, it is and has been very much appreciated.
Click to expand...
Click to collapse
No problem. You could try a different build. Or you could try a CM12 based rom. SaberMod worked fine for me. And it's the closest to the actual CM12 you can get.
GDReaper said:
No problem. You could try a different build. Or you could try a CM12 based rom. SaberMod worked fine for me. And it's the closest to the actual CM12 you can get.
Click to expand...
Click to collapse
Cheers, I have CM12 up and running now. Downloaded the files straight to the SD card and they worked. Seems OK but might try others, how do I go about trying SaberMod, do I need to flash that? Sorry to keep asking what are no doubt pretty obvious questions but I'm pretty new to this!
Want to get rid of the google search box for starters!
PJBXDA said:
Cheers, I have CM12 up and running now. Downloaded the files straight to the SD card and they worked. Seems OK but might try others, how do I go about trying SaberMod, do I need to flash that? Sorry to keep asking what are no doubt pretty obvious questions but I'm pretty new to this!
Want to get rid of the google search box for starters!
Click to expand...
Click to collapse
SaberMod is a rom. SaberMod CM12.1.
They are very similar. The difference is how they tackle optimizations.
Yes, you will have to flash it. But you can also stick with normal CM12 if you don't have any issues.
The google search box from the home screen or the recents?
You can change the launcher to get rid of it from the home screen.
To remove it from the recents there is an option somewhere in the settings.