Related
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.
Okay Idk what's going on exactly but I've tried downloading sacs custom 7.2 several times md5s all check out and when I go to flash it in twrp 2.6.3 it fails same with twrp 2.5.2.zip they both keep failing. However I was recently able to flash miuiv5 after a download so the recovery is still working (also it restores backups fine)... So. I'm wondering what's going on here they aren't bad files and it just won't flash! Does this rom have that aroma installer? Am I missing something that allows that?
Currently running trifforce 3.1 with agat kernel and twrp 2.63
Sent from my SPH-L720 using XDA Premium 4 mobile app
coke32 said:
Okay Idk what's going on exactly but I've tried downloading sacs custom 7.2 several times md5s all check out and when I go to flash it in twrp 2.6.3 it fails same with twrp 2.5.2.zip they both keep failing. However I was recently able to flash miuiv5 after a download so the recovery is still working (also it restores backups fine)... So. I'm wondering what's going on here they aren't bad files and it just won't flash! Does this rom have that aroma installer? Am I missing something that allows that?
Currently running trifforce 3.1 with agat kernel and twrp 2.63
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It could be a product assert. If the TWRP is not made for t0ltespr (Sprint Note II) or ROM isn't made for that the two could be trying to verify the wrong model against each other and failing. You can remove this from the zip by looking for the assert in update-script.
Another option if you're open to it is to try my unofficial CWM and see if that avoids your issue.
Good luck!
rom help
In order for it to work, you need to flash sach's custom rom version 7.0. Let it do a full install and setup, then boot back into recovery. Then flash the 7.1 or 7.2 update. Hope this helps.
---------- Post added at 09:50 AM ---------- Previous post was at 09:45 AM ----------
Do Not, I repeat DO NOT do a system wipe in TWRP after installing 7.0 or 7.1. Let the aroma installer do the wipe. I learned the hard way, I wiped it myself and went to update to 7.2 and got nothing but failure notices. Once I re-flashed 7.1 and let the aroma installer do the wipe, it installed with no problem
ive always done a system wipe with no problems. be sure you are downloading the full rom and not the update. and make sure your downloading from a pc over a good wifi conection, then i make sure the file size is about the same size before transferring and flashing. hope this helps
coke32 said:
Okay Idk what's going on exactly but I've tried downloading sacs custom 7.2 several times md5s all check out and when I go to flash it in twrp 2.6.3 it fails same with twrp 2.5.2.zip they both keep failing. However I was recently able to flash miuiv5 after a download so the recovery is still working (also it restores backups fine)... So. I'm wondering what's going on here they aren't bad files and it just won't flash! Does this rom have that aroma installer? Am I missing something that allows that?
Currently running trifforce 3.1 with agat kernel and twrp 2.63
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After wiping system,caches,data in Twrp advanced wiped are you getting the fail? if so just reboot recovery and try to install again without wiping. I have had the flash fail for me too and a recovery reboot solved the issue for me. Also in aroma don't factory reset wipe just wipe cache and dalvik. Also I am on TWRP 2.6.3.1
Sent from my SPH-L720 using Tapatalk 2
As the title Im noob, I Just rooted my note 3 CF auto root and flash twrp recovery, i cant post on the official Thread don't have enough post.
I have flash version 17 and 18 which was on posted today having same problem, it install fine in recovery done full wipe, when it comes to set up put in all my details get to last page for device name and click to finish get Unfortunately, Samsung setupWizard has stopped any way around this just me?
After simple stock rom, this looks like one of them
I tried X Note Rom before this work fine didn't like it just to much overwhelming
Thanks in advance, Hoping someone can point me in the right direction
Did you flash Omega from external SD??
TWRP recovery is the newest??? (2.7.1.0)
Yes I did, I have the latest twrp recovery installed no joy , flash few times same problem, using different rom, probably try different recovery later, is the stock rom With root?
Using twrp 2.7.2.0, 64gb sandisk card
Make sure you check wipe /system data when doing a complete wipe or it's not classed a a fresh install.
uspsilencer said:
Yes I did, I have the latest twrp recovery installed no joy , flash few times same problem, using different rom, probably try different recovery later, is the stock rom With root?
Using twrp 2.7.2.0, 64gb sandisk card
Click to expand...
Click to collapse
For Omega v18 you need to do a factory reset in twrp, than wipe cache, dalvik cache before you flash the ROM. Do that and than report back.
Thanks, got it working really nice Rom
I booted into to recovery through ROM manager and tried to flash CM 10.2 but even leaving it for 30 minutes it just keeps showing the CM boot logo, Am I in a boot loop if so how do I get out of it?
flash another cwm and after this a new rom,that shall be working,good luck
TheGamerCatHD said:
I booted into to recovery through ROM manager and tried to flash CM 10.2 but even leaving it for 30 minutes it just keeps showing the CM boot logo, Am I in a boot loop if so how do I get out of it?
Click to expand...
Click to collapse
Did you wipe data/factory reset?
Goto recovery and do that if not already done.
Wipe also dalvik cache from advanced
Your phone will boot into CM10.2
That was my problem, I wiped dalvik cache and regular cache and now I'm running CM 10.2 and will install a KK ROM later today. thanks for the help
Sent from my Ascend Y300 using XDA Free mobile app
skyinfo said:
Did you wipe data/factory reset?
Goto recovery and do that if not already done.
Wipe also dalvik cache from advanced
Your phone will boot into CM10.2
Click to expand...
Click to collapse
Although I do have a different issue no matter what I do I can not, What so ever change my kernel. I did a factory reset through TWRP and no matter what I do I cannot change my kernel. Anyone know what's wrong
Thanks
EDIT-I'm trying to flask the same kernel as yours the S1Kernel
Guys i keep getting thsame problem with my L5 e610 every time i flash a rom my screen stops working.
The phone boots normaly and it strts but the screen is totaly dead, if i use KDZ to get back to stock it works fine, but when i flash a rom it wont work.
Iv tried every thing, from installing the rom zip and rebooting to install gapps. To doing a whipe and reset every time i flash a rom and gaaps.
My cwm is 6.0.5.0
Nesh89 said:
Guys i keep getting thsame problem with my L5 e610 every time i flash a rom my screen stops working.
The phone boots normaly and it strts but the screen is totaly dead, if i use KDZ to get back to stock it works fine, but when i flash a rom it wont work.
Iv tried every thing, from installing the rom zip and rebooting to install gapps. To doing a whipe and reset every time i flash a rom and gaaps.
My cwm is 6.0.5.0
Click to expand...
Click to collapse
Try updating your CWM to 6.0.4.8
Link: https://www.mediafire.com/?l8mpej31m3k81tj
Hope this helps!
Yeah i did, still nothing, tried to flashing karnel to. But that didnt work eather.
What version of CM or other ROM are you trying to flash?
Sent from my Ascend Y300 using XDA Free mobile app
Im not on CM, i tried [AOKP4_E612-v2] and [pa_e610-4.4-20140625]
thoes are the roms i tried.
Make sure your using CWM 6.0.4.8, Remember to wipe your cache and dalvik cache and try to install this ROM
Link: http://www.mediafire.com/?8rq7jsniv5gasb7
P.S- I do actually have an L5 which I have successfully rooted and flashed ROMs just my daily driver is a rooted Y300 running CM11 nightlys.
Hope this helps
Sent from my Ascend Y300 using XDA Free mobile app
Actualy im downloading an update for the paranoid rom, im going to trie it. Yes my cwm is 6.0.4.8 and im not sure if this paranoid will work but il defenetly trie the rom you posted
And i whiped every thing and formated systeam to.
Who knows whats wrong with this damn thing.
Im on my L7 p705 its stock and it sucks, but i cant flash any thing on it yet till i take care of my L5 i use bothe phones daylie. And thank you for your support buddy
---------- Post added at 11:48 PM ---------- Previous post was at 11:03 PM ----------
Damn, still not working! the screen is still frosen
---------- Post added 7th October 2014 at 12:35 AM ---------- Previous post was 6th October 2014 at 11:48 PM ----------
I tried flashin e610 3.4.0 karnel and e612 3.40 karnel. Still nothing
Nesh89 said:
Actualy im downloading an update for the paranoid rom, im going to trie it. Yes my cwm is 6.0.4.8 and im not sure if this paranoid will work but il defenetly trie the rom you posted
And i whiped every thing and formated systeam to.
Who knows whats wrong with this damn thing.
Im on my L7 p705 its stock and it sucks, but i cant flash any thing on it yet till i take care of my L5 i use bothe phones daylie. And thank you for your support buddy
---------- Post added at 11:48 PM ---------- Previous post was at 11:03 PM ----------
Damn, still not working! the screen is still frosen
Click to expand...
Click to collapse
Can you load you the stock ROM onto an SD card?
If you can try doing a factory reset and flashing the CM11 I linked you to in the post above
Hope this helps
Well i dont have a stock rom, i didnt do a backup of it. But is it posible to flash a stock rom with cwm? And will it install normaly with cwm?
Btw if it can, do you maybe have a stock zip? I dont have a pc atm to go in to kdz.
Sad to say I don't think you'd be able to flash a stock ROM without a PC, Just because of the .kdz file extension. So you're telling me after trying to flash 3 ROMs, every time you get a blank screen.
Can you send me a picture of the log you get after trying to install a custom ROM or even better send me a video of what's going on.
P.S-Are you getting a black or blank screen or a frozen screen?
Sent from my Ascend Y300 using XDA Free mobile app
Nesh89 said:
Well i dont have a stock rom, i didnt do a backup of it. But is it posible to flash a stock rom with cwm? And will it install normaly with cwm?
Btw if it can, do you maybe have a stock zip? I dont have a pc atm to go in to kdz.
Click to expand...
Click to collapse
Sad to say I don't think you'd be able to flash a stock ROM without a PC, Just because of the .kdz file extension. So you're telling me after trying to flash 3 ROMs, every time you get a blank screen.
Can you send me a picture of the log you get after trying to install a custom ROM or even better send me a video of what's going on.
P.S-Are you getting a black or blank screen or a frozen screen?
Sent from my Ascend Y300 using XDA Free mobile app
Ok i uploaded the install bug on to youtube
http://m.youtube.com/watch?v=ZTlMQPmrbxM
Heres the url.
The video is called LG L5 e610 frozen after ROM installation.
Ok i re installd stock with kdz, flashed recovery, flashed 6.0.4.8 and iv tried multiple roms inkluding yours, iv tried installing with format system and with oud just whiping catch and delvic. Every time i boot a rom the screen wont work, same thing with every rom. Il just go back to stock. I cant beleave that my phone cant install a rom how stupid.
Nesh89 said:
Ok i re installd stock with kdz, flashed recovery, flashed 6.0.4.8 and iv tried multiple roms inkluding yours, iv tried installing with format system and with oud just whiping catch and delvic. Every time i boot a rom the screen wont work, same thing with every rom. Il just go back to stock. I cant beleave that my phone cant install a rom how stupid.
Click to expand...
Click to collapse
Try wiping everything besides /system and try flashing the rom
Tell me your results
Hope this helps
Ok i didnt trie that yet, il trie it tonight.
Sent from my LG-P705 using XDA Free mobile app
I successfully rooted and modded my Note 3 to run CyanogenMod 11-20140916-SNAPSHOT-M10-hlte. Since that time there have been 2 updates (M11 and M12).
I have downloaded and attempted to update both by using ROM Manager as well as the Update feature in the Settings Menu. Whenever I try to do this, I get the phone's opening splash screen along following messages:
RECOVERY BOOTING ...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
The phone then reboots and returns to this screen.
The only thing I can do is pull the battery, reinsert it, then perform the Volume Down + Home + Power reboot then press Volume Down to force the reboot back to normal.
Did I screw up something when I rooted my phone that is preventing the updates from processing, or am I stuck with manual updates from here on out. If that is the case, what do I need to do to make that happen?
Anyone? Anyone? Beuller? Beuller?
I am bumping this in hopes to get an answer. I am getting really sick of the instability and want to get the newest ROM flashed or, if that's not possible, flash the stock ROM back on the phone.
Odin a recovery like twrp after the odin is done shut down the phone . press volume up +power+home to get back in recovery . from here flash the cm ROM.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
Lol and if you don't know what Odin is than you shouldn't be messing with your phone..
Do a clean flash and it will be good...factory reset+wipe cache and dalvik....
gabesir said:
Odin a recovery like twrp after the odin is done shut down the phone . press volume up +power+home to get back in recovery . from here flash the cm ROM.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
Lol and if you don't know what Odin is than you shouldn't be messing with your phone..
Click to expand...
Click to collapse
I am familiar with Odin, but was able to do everything the first time with ROM Manager.
osutuba said:
I am familiar with Odin, but was able to do everything the first time with ROM Manager.
Click to expand...
Click to collapse
so it doesnt boot into recovery at all? the only way to fix it is to odin your recovery again and than flash your rom.
gabesir said:
so it doesnt boot into recovery at all? the only way to fix it is to odin your recovery again and than flash your rom.
Click to expand...
Click to collapse
Yeah, I had to Odin TWRP on there. Now, I just need to figure out which CM build to use, because there's only nightlies for my specific model (T-Mobile), while there are snapshots of the base model.
I'm welcome to trying other ROMS, but CM is what I am most accustomed to.
osutuba said:
Yeah, I had to Odin TWRP on there. Now, I just need to figure out which CM build to use, because there's only nightlies for my specific model (T-Mobile), while there are snapshots of the base model.
I'm welcome to trying other ROMS, but CM is what I am most accustomed to.
Click to expand...
Click to collapse
Awesome man! glad you back in TWRP..
Look for a CM11(most stable) port for your phone and go from there. :highfive:
gabesir said:
Awesome man! glad you back in TWRP..
Look for a CM11(most stable) port for your phone and go from there. :highfive:
Click to expand...
Click to collapse
Well, I have tried several different mods and keep getting the same error in TWRP:
E:Unable to open ZIP file
Error flashing zip <filename.zip>
Updating partition details ...
Ideas/suggestions? I'm comfortable enough with Odin now to the point that I can flash a ROM that way, if necessary.
rayman95 said:
Do a clean flash and it will be good...factory reset+wipe cache and dalvik....
Click to expand...
Click to collapse
Do read before you post. OP couldn't even access his recovery.
osutuba said:
Well, I have tried several different mods and keep getting the same error in TWRP:
E:Unable to open ZIP file
Error flashing zip <filename.zip>
Updating partition details ...
Ideas/suggestions? I'm comfortable enough with Odin now to the point that I can flash a ROM that way, if necessary.
Click to expand...
Click to collapse
First of all, why is it called filename.zip? Put the CM .zip file to internal or external SD card (latter preferred if you have one) and then flash it directly from there after wiping (I wipe system, data, cache, dalvik cache).
Someguyfromhell said:
Do read before you post. OP couldn't even access his recovery.
First of all, why is it called filename.zip? Put the CM .zip file to internal or external SD card (latter preferred if you have one) and then flash it directly from there after wiping (I wipe system, data, cache, dalvik cache).
Click to expand...
Click to collapse
why do you propose him to flash CM11 if he can't get recovery mode????
Someguyfromhell said:
First of all, why is it called filename.zip?
Click to expand...
Click to collapse
I used <filename.zip> as a generic marker, as I have tried several different ROMs with the same outcome. As I stated in a previous reply, I was able to flash TWRP using Odin without issue. I have even re-flashed it several times since getting the aforementioned error, thinking something wasn't working.
Someguyfromhell said:
Put the CM .zip file to internal or external SD card (latter preferred if you have one) and then flash it directly from there after wiping (I wipe system, data, cache, dalvik cache).
Click to expand...
Click to collapse
I don't have an external SD Card on hand at the moment, otherwise I would try that.
rayman95 said:
why do you propose him to flash CM11 if he can't get recovery mode????
Click to expand...
Click to collapse
Please keep an eye on the topic. You can see that he solved the issue (after your and before my post) with accessing recovery, thereby we have moved on to solve his next problem - flashing the ROM.
osutuba said:
I used <filename.zip> as a generic marker, as I have tried several different ROMs with the same outcome. As I stated in a previous reply, I was able to flash TWRP using Odin without issue. I have even re-flashed it several times since getting the aforementioned error, thinking something wasn't working.
I don't have an external SD Card on hand at the moment, otherwise I would try that.
Click to expand...
Click to collapse
Re-download the .zip file and place it on the internal storage then. Do MD5 check also before moving, seems like the zip file was corrupted (faulty download?) when you tried to flash it.