Database Users

TWRP restore

I restored my phone using TWRP. Everything works ok except if I try to restart the phone it hangs at the Samsung logo. Please someone help me to get my phone back working :crying:

I'm asking you restored a stock backup. Did you wipe before restoring? Have you wiped since?

Yes and yes. My phone works perfect but won't boot up if I restart it. Then I need to wipe, format, restore just to boot up again. Has happened three times in a row so now I cannot restart or turn off my phone without taking 15 minutes to restore again
Sent from my stock rooted i337m

WHAT DEVICE
Sheez, how can someone help if you do not tell us what type of att device you have, I suppose you have a att, or you would not be posting here...we are not Houdini's here...help us help you.
You have a kernel issue with your backup, I bet. get the correct kernel for YOUR device, restore backup, AND BEFORE YOU BOOT, flash the kernel.

TheAxman said:
WHAT DEVICE
Sheez, how can someone help if you do not tell us what type of att device you have, I suppose you have a att, or you would not be posting here...we are not Houdini's here...help us help you.
You have a kernel issue with your backup, I bet. get the correct kernel for YOUR device, restore backup, AND BEFORE YOU BOOT, flash the kernel.
Click to expand...
Click to collapse
I'm sorry that I neglected to mention which device in particular. I am using a ROGERS SGH-I337m Galaxy S4. It is currently running TW stock (rooted with motochopper). If I understand you correctly, I should turn my phone off, and then boot into recovery, and then flash the stock rogers kernel, (wipe cache, dalvik, fix permissions) and then it should boot? I should note that the last time I tried wiping Dalvik before booting the system, the dalvik wipe failed.....
P.S. I couldnt get wifi working on Omega v7 so I tried google edition 1.3 but found it too vanilla. I really want omega v7

trueking7 said:
I'm sorry that I neglected to mention which device in particular. I am using a ROGERS SGH-I337m Galaxy S4. It is currently running TW stock (rooted with motochopper). If I understand you correctly, I should turn my phone off, and then boot into recovery, and then flash the stock rogers kernel, (wipe cache, dalvik, fix permissions) and then it should boot? I should note that the last time I tried wiping Dalvik before booting the system, the dalvik wipe failed.....
P.S. I couldnt get wifi working on Omega v7 so I tried google edition 1.3 but found it too vanilla. I really want omega v7
Click to expand...
Click to collapse
I'd be more worried of getting my phone working not what rom you want to flash.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Right now I am trying to find out if flashing the stock kernel will enable me to reboot normally? I will copy the kernel to the card just in case my phone powers off. Then I will try flashing it to see if phone will boot. If not then I will restore from nandroid yet again and be unable to reboot.
I will use Odin as a last resort.
Ps. This would be a lot easier if install instructions were carrier specific.
jd1639 said:
I'd be more worried of getting my phone working not what rom you want to flash.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
TheAxman said:
WHAT DEVICE
Sheez, how can someone help if you do not tell us what type of att device you have, I suppose you have a att, or you would not be posting here...we are not Houdini's here...help us help you.
You have a kernel issue with your backup, I bet. get the correct kernel for YOUR device, restore backup, AND BEFORE YOU BOOT, flash the kernel.
Click to expand...
Click to collapse
Sent from my stock rooted i337m

here is your answer..
flash omega
before you boot, flash YOUR CARRIER kernel.
thats it...easy easy easy.
course this after you get the correct kernel flashed so you can even boot.
answer is...
get into recovery, flash YOUR CARRIER kernel, you should boot up with no problem
your welcome

TheAxman said:
here is your answer..
flash omega
before you boot, flash YOUR CARRIER kernel.
thats it...easy easy easy.
course this after you get the correct kernel flashed so you can even boot.
answer is...
get into recovery, flash YOUR CARRIER kernel, you should boot up with no problem
your welcome
Click to expand...
Click to collapse
I got my phone booting properly again. I re-rooted. I installed TMO KTweaker. I can still reboot. I took another nandroid. I will try flashing omega + ktweaker again this time without formating via TWRP which apparently casused my problem.

Usually when you have restore problems, its either a MD5 mismatch, or corrupt micro SD card. You don't have to wipe when restoring, TWRP does it automatically when you restore.

I got Omega v7 working with the TMO KTweaker on my rogers i337m. Thank you all!

everything works perfect now thanks!!

good deal

Can't get passed boot logo..

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.

2 Serious problems

I have been a Samsung Galaxy Y user for more than a year. I have to say that this device is awesome. But.... I have later noticed 2 problems.
1) One day I tried to install Elegance ROM. I followed all steps very carefully and when the installation was done, I rebooted my phone. Unfortunately, my phone booted up again at Samsung stock firmware. I tried to enter recovery mode because I wanted to see what went wrong, but I was automatically redirected to CWM recovery. I tried once again to install Elegance ROM, and the result was the same. From that day, CWM is my default recovery. Why? How to fix this??? I can't access stock recovery and I also cannot install any custom ROMs. How to fix this?
2) Even my SD card is full with songs, photos and videos, the "Gallery" and "Music" apps don't read any file. Why? How to fix this?
P.S. I'm running stock 2.3.6 rooted.
Thanks for help.
Sent from my GT-S5360 using xda app-developers app

You have a permanent cwm because you are using a custom kernel with a permanent cwm - probably was included in the rom zip
If you want stock recovery flash stock kernel (can be found in general section or flash hells fusion #50 from dev section and select option to flash stock kernel)
you would of remained on stock rom after flashing another rom because you didn't mount system in cwm before you flashed the zip
As for your other problem flash stock rom via odin as you have probably mucked something up from flashing zips incorrectly

So.... If I flash the stock kernel, will I be able to access stock recovery and flash CWM every time I want?
By the way, this mess with the files started when I changed my phone's SIM card. When I turned my ohine on again, I opened by mistake the "Galery" app. I noticed that no images were there. I also thought that the "music" might also had the same problem. And that's what happened. Which Odin version I will need?
Thanks again.
Sent from my GT-P3110 using xda premium

dimsar2013 said:
So.... If I flash the stock kernel, will I be able to access stock recovery and flash CWM every time I want?
By the way, this mess with the files started when I changed my phone's SIM card. When I turned my ohine on again, I opened by mistake the "Galery" app. I noticed that no images were there. I also thought that the "music" might also had the same problem. And that's what happened. Which Odin version I will need?
Thanks again.
Sent from my GT-P3110 using xda premium
Click to expand...
Click to collapse
Dude ur 2nd problem may be caused by Ur sd card!!
Try another sd card may it help you!!

dimsar2013 said:
So.... If I flash the stock kernel, will I be able to access stock recovery and flash CWM every time I want?
By the way, this mess with the files started when I changed my phone's SIM card. When I turned my ohine on again, I opened by mistake the "Galery" app. I noticed that no images were there. I also thought that the "music" might also had the same problem. And that's what happened. Which Odin version I will need?
Thanks again.
Sent from my GT-P3110 using xda premium
Click to expand...
Click to collapse
Yes stock kernel = stock recovery and you can flash a temporary cwm
there is no problems with a permanent cwm in custom kernels as you need cwm to flash roms
If you goto phone settings about phone it will show you your current baseband - for example mine is xxlf3
You can either download that stock rom firmware from dokys thread if there or any other from your country

Thanks everybody. You are all really helpful. I appreciate your help. But tell me, do I need to mount system before installing Elegance? And while I'm having a custom kernel installed, can I flash roms or I need the stock kernel?
Thanks again.
Sent from my GT-P3110 using xda premium

dimsar2013 said:
Thanks everybody. You re awesome. I appreciate your help. But tell me, do I need to mount system before installing Elegance? And while I'm having a custom kernel installed, can I flash roms or I need the stock kernel?
Thanks again.
Sent from my GT-P3110 using xda premium
Click to expand...
Click to collapse
Follow instructions on the op of the rom you want to flash
you must always mount system before flashing a zip else nothing will happen - you can flash zips all day and no changes would happen as it can't write to system as it's not mount!
As a general rule
wipe system
wipe data
wipe cache
mount system
mount data
mount cache
flash zip
format data (not always required just for some roms)
restart
you do not need to go back to stock to change rom
There are guides in general section - please read them first then you would understand the process

My current ROM. Stock 2.3.6 rooted
Sent from my GT-S5360 using xda app-developers app

A few months ago, I installed Creed 3.5 ROM. It was awesome. I want to install it again but tell me:
Can I install it while I have a custom kernel installed? If yes, do I need to mount system before installing? Thanks for help

dimsar2013 said:
A few months ago, I installed Creed 3.5 ROM. It was awesome. I want to install it again but tell me:
Can I install it while I have a custom kernel installed? If yes, do I need to mount system before installing? Thanks for help
Click to expand...
Click to collapse
Yes you can flash it over any kernel and yeah mount all the partitions after formatting them.

dimsar2013 said:
A few months ago, I installed Creed 3.5 ROM. It was awesome. I want to install it again but tell me:
Can I install it while I have a custom kernel installed? If yes, do I need to mount system before installing? Thanks for help
Click to expand...
Click to collapse
I refer you to my previous post in this thread
wipe data system cache
mount everything
flash rom
you can use any compatible kernel

The problem with the files is caused by the sdcard
Sent from my GT-P3110 using XDA Premium 4 mobile app

Does anyone have a flashable .zip of the 9.8.1Q-78-1 kernel?

I flashed argghhh's kernel and am having bluetooth stutters (with apt-x headphones). I am not sure it's because of the kernel though and want to test a bit.
Does anyone know how to restore the previous kernel without re-flashing the stock rom?

Coronado is dead said:
I flashed argghhh's kernel and am having bluetooth stutters (with apt-x headphones). I am not sure it's because of the kernel though and want to test a bit.
Does anyone know how to restore the previous kernel without re-flashing the stock rom?
Click to expand...
Click to collapse
Just dirty flash the stock ROM, without wiping anything. Well, you could wipe cache/dalvik just to be safe. If you don't wipe data, dirty flashing the ROM shouldn't affect anything.

Coronado is dead said:
I flashed argghhh's kernel and am having bluetooth stutters (with apt-x headphones). I am not sure it's because of the kernel though and want to test a bit.
Does anyone know how to restore the previous kernel without re-flashing the stock rom?
Click to expand...
Click to collapse
As sloosecannon made clear a simple solo restore of the boot partition / img is replacing the kernel.

9.8.1Q-78-1 Stock Kernel

Thanks everyone!
And thanks Attack!

Update: Oh wow, that was it. No skips at all now. 2/3 of my audio programs would skip before when starting a song (again, only when using an Apt-X compatible bluetooth headset). Or they'd skip when opening a menu while playing a song, or turning off the screen. Skips would continue for 5-10 seconds and then it would even out.
Not even once on the stock kernel. I guess I'll report this to arrghh

ATTACK said:
9.8.1Q-78-1 Stock Kernel
Click to expand...
Click to collapse
Hmm, I tried this and it installed and all, but my wifi is broken. I wonder if it is because I was on a deodexed stock rom. Will try a dirty flash of the whole thing now.

Coronado is dead said:
Hmm, I tried this and it installed and all, but my wifi is broken. I wonder if it is because I was on a deodexed stock rom. Will try a dirty flash of the whole thing now.
Click to expand...
Click to collapse
Weird... I'm on stock deodexed and I didn't have any problems. I used it to restore from arrrghhh's kernel.

ATTACK said:
Weird... I'm on stock deodexed and I didn't have any problems. I used it to restore from arrrghhh's kernel.
Click to expand...
Click to collapse
Yeah, no idea. A dirty flash got it all back and working.
If I pressed the wifi toggle it would just turn back to off. After a few times I got the 10 fast vibrates and still nothing. Wiped caches a few time, still no.
But I'm back up and running

I was having an issues with my WiFi when using arggghhss.
Flashed the stock kernel from this thread and now I have the same problem with my WiFi not turning on. A dirty flashed fixed this? What's a dirty flash and where can I find a stock ROM?
Sent from my XT907 using xda app-developers app

Franteeko said:
I was having an issues with my WiFi when using arggghhss.
Flashed the stock kernel from this thread and now I have the same problem with my WiFi not turning on. A dirty flashed fixed this? What's a dirty flash and where can I find a stock ROM?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Dirty flashing is just flashing without wiping anything. Just dirty flash whatever ROM you're using and it will reload the original kernel that came with that ROM. You can wipe cache/dalvik to be safe, but don't worry about wiping data when you're dirty flashing.

RikRong said:
Dirty flashing is just flashing without wiping anything. Just dirty flash whatever ROM you're using and it will reload the original kernel that came with that ROM. You can wipe cache/dalvik to be safe, but don't worry about wiping data when you're dirty flashing.
Click to expand...
Click to collapse
Thank you. I am just using stock ota ROM rooted and unlocked. I'm not sure where I can obtain a stock ROM because the one I have I received ota.
Anyone know where I can download a stock ROM? And when i flash, will I have to reroot?
Sent from my XT907 using xda app-developers app

Franteeko said:
Thank you. I am just using stock ota ROM rooted and unlocked. I'm not sure where I can obtain a stock ROM because the one I have I received ota.
Anyone know where I can download a stock ROM? And when i flash, will I have to reroot?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
http://droid-hive.com/index.php?/forum/469-roms/

jco23 said:
http://droid-hive.com/index.php?/forum/469-roms/
Click to expand...
Click to collapse
Downloaded and attempted flash twice. It errord both times. Anyone have a stock ROM I can flash?
To clarify, I can't seem to get WiFi working on the stock kernel. WiFi functions somewhat on arrgs.
Sent from my XT907 using xda app-developers app

Franteeko said:
Downloaded and attempted flash twice. It errord both times. Anyone have a stock ROM I can flash?
To clarify, I can't seem to get WiFi working on the stock kernel. WiFi functions somewhat on arrgs.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
what recovery are you using? i'm using TWRP.

jco23 said:
what recovery are you using? i'm using TWRP.
Click to expand...
Click to collapse
Clockwork mod. I should switch to twrp maybe?
Sent from my XT907 using xda app-developers app

Franteeko said:
Clockwork mod. I should switch to twrp maybe?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
it should still work via CWM - but I think most folks are using TWRP.
what are your steps in the process?
mine would be:
copy zip file to the root folder of the sdcard (mnt/external1)
reboot recovery
mount system
wipe cache
wipe dalvik
wipe data/factory reset
wipe system
reboot recovery (not sure if this in an option in CWM, if not, then just make sure that system is still mounted)
mount system
install ROM
reboot

jco23 said:
it should still work via CWM - but I think most folks are using TWRP.
what are your steps in the process?
mine would be:
copy zip file to the root folder of the sdcard (mnt/external1)
reboot recovery
mount system
wipe cache
wipe dalvik
wipe data/factory reset
wipe system
reboot recovery (not sure if this in an option in CWM, if not, then just make sure that system is still mounted)
mount system
install ROM
reboot
Click to expand...
Click to collapse
Well I got it flashed. I was doing a dirty flash so I didn't wipe data or system. But I guess I didn't realize that you had to Mount system. I assumed that the recovery did that automatically.
After mounting system the stock rom flashed just fine and my WiFi is golden. Thanks to everyone who helped.
Sent from my XT907 using xda app-developers app

Franteeko said:
Well I got it flashed. I was doing a dirty flash so I didn't wipe data or system. But I guess I didn't realize that you had to Mount system. I assumed that the recovery did that automatically.
After mounting system the stock rom flashed just fine and my WiFi is golden. Thanks to everyone who helped.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
yeah, I think what happened was that you were installing a ROM with an incompatible kernel (existing one) or vice versa... in either case, glad you got it working. i almost always mount when tinkering....

jco23 said:
yeah, I think what happened was that you were installing a ROM with an incompatible kernel (existing one) or vice versa... in either case, glad you got it working. i almost always mount when tinkering....
Click to expand...
Click to collapse
Good advice JC thank you.
Sent from my XT907 using xda app-developers app

Bootloop regardless of what rom I flash

I've tried installing the d3rp rom and optimus rom using twrp and cwm. It installs fine according to either recovery, but upon reboot I just get a loop of the sprint logo. I can restore back to my original recovery with no problem. Does anyone know why I just don't get to use custom roms? I have the v8 ota as well

I was able to flash the furnace kernel fine as well.

first of all
★ ☆ ✰ Q&A, Help & Troubleshooting do not go in the Development Section. ✰ ☆ ★
When you flash roms, you have to wipe everything EXCEPT internal memory. I *hope* you made a backup of the stock rom before trying to flash. Also, which version of recovery are you using?

I'm using twrp 2.6.3.3 installed through freegee. I backed up my stock rom and have no problem recovering to it after it bootloops. I just don't understand why none of the custom rom flashes will take. I've wiped everything but system and internal storage every time before flashing, multiple times on some attempts, but every time I just get a loop. However, flashing the furnace kernel on stock worked fine and did not cause a loop

I had the same problem. I tried 4 different rooms and only the flex one took.
Sent from my LG-D800 using xda app-developers app

duffmcwhalen said:
I'm using twrp 2.6.3.3 installed through freegee. I backed up my stock rom and have no problem recovering to it after it bootloops. I just don't understand why none of the custom rom flashes will take. I've wiped everything but system and internal storage every time before flashing, multiple times on some attempts, but every time I just get a loop. However, flashing the furnace kernel on stock worked fine and did not cause a loop
Click to expand...
Click to collapse
Your problem is you need to whipe system and data.
Sent from my LG-LS980 using xda premium

mchlbenner said:
Your problem is you need to whipe system and data.
Sent from my LG-LS980 using xda premium
Click to expand...
Click to collapse
You are correct. I figured that out yesterday. Thanks for the help though.