Database Users

[Q] Need some clarification on OTA update.

Ok I am full rooted thanks to un-revoked.
I have downloaded the new update on my phone but havent installed yet, Battery was to low so gave me a notification in status bar to update later.
I understand i have to flash to the Amon ra recovery.
all i want is the stock rom, with the ability to use wireless tether and adfree, so obviously i need superuser permission.
Will i have to flash to a stock rooted rom?? or will i just be able to install these and be good to go?? is there even a stock rooted rom out yet??
Thanks for any and help. love the site dont post much cause normally i can figure things out, but wanna double check on this one.

Here you go.
http://forum.xda-developers.com/showthread.php?t=1038701
Make back up and perform full wipes.
You must install the rooted Rom for precautionary reasons.

so should i even update my phone then?? or should i just flash right to one of these?? seems like it would be easier just flashing right too those since i currently have clockwork installed.

drew454u said:
so should i even update my phone then?? or should i just flash right to one of these?? seems like it would be easier just flashing right too those since i currently have clockwork installed.
Click to expand...
Click to collapse
Flash the odexed or deodexed versions and enjoy.
Sent from my PC36100 using Tapatalk

drew454u said:
so should i even update my phone then?? or should i just flash right to one of these?? seems like it would be easier just flashing right too those since i currently have clockwork installed.
Click to expand...
Click to collapse
Simple answer is NO YOU SHOULD NOT DO THE OTA... The rom is out there already (rooted versions)

novanosis85 said:
Flash the odexed or deodexed versions and enjoy.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Whats the difference in them?? and do i have to flash a kernel also?? not gonna lie i have never flashed a different rom before. never had a need too really.

drew454u said:
Whats the difference in them?? and do i have to flash a kernel also?? not gonna lie i have never flashed a different rom before. never had a need too really.
Click to expand...
Click to collapse
No difference really. Just flash the odexed version and that is all. No kernel needed.
I'm not familiar with cwmod so I can't guide you through the flash but also you need to have an updated version.
Sent from my PC36100 using Tapatalk

novanosis85 said:
No difference really. Just flash the odexed version and that is all. No kernel needed.
I'm not familiar with cwmod so I can't guide you through the flash but also you need to have an updated version.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ok thank you sir, much appreciated.

drew454u said:
ok thank you sir, much appreciated.
Click to expand...
Click to collapse
Flash Amon on your phone download odex version and flash thru recovery
Sent from my EVO rocking Evervolv Gingerbread

All I did was wiped everything and flashed the rooted update Rom using amon recovery. Now I a running the same thing as th ota and I'm still rooted. That's the easiest and safest option u have.
Sent from my PC36100 using XDA App

Lite'ning 1.5, CWM and ROM Manager

Hi all,
I've flashed my GS2 one week ago with Lite'ning 1.5, during the week I've purchased ROM Manager Premium. As I wanted to flash again to new Lite'ning 2.0 I've tried to make a rom backup with Rom Manager but I get the error "Failed to verify whole file signature" (android system is 3e). I've tried the CWM Recovery from ROM Manager selecting device Samsung Galaxy S2 but still cannot backup my rom.
I've noticed that the CWM app coming with Lite'ning 1.5 is v1.80 and the one in ROM Manager is 4.0.0.2, could it be the issue?
Please let me know

I've read somewhere that ROM Manager is not compatible with CWM, can anyone confirm it?

yupo72 said:
I've read somewhere that ROM Manager is not compatible with CWM, can anyone confirm it?
Click to expand...
Click to collapse
Yup, its true. Rom manager isnt compatible. Use the cwm app that is included with the cfroot that chainfire has created.
Sent from my GT-P1000 using XDA Premium App

[Q] how to flash cwm?howwww?

okay, i looked around a bit , found out cwm is temporary and need to flash a kernel. but which kernel? and if i wish to undo this in the future, how to do so?

TheStormBreaker said:
i am seriously confused now..how to flash cwm? i cannot find anything.
do i need to flash a kernel or can i directly flash roms?
helllllllp!
Click to expand...
Click to collapse
If you already rooted the phone then you can install ROM Manager which can be used to flash the latest CWM recovery image.
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
Sent from my SGH-T999 using xda app-developers app

TheStormBreaker said:
okay, i looked around a bit , found out cwm is temporary and need to flash a kernel. but which kernel? and if i wish to undo this in the future, how to do so?
Click to expand...
Click to collapse
hell fusion,gnu,merruk, and white kernel have cwm..if u want to undo just flash stock kernel

..can someone know how to flash the kernel with steps??

greatwhovian said:
If you already rooted the phone then you can install ROM Manager which can be used to flash the latest CWM recovery image.
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
you are providing wrong information,
ROM manager does not work with some kernels and could potentially result in a software malfunction,
@op and everyone else having the same question:
please just read the original instructions from the kernel developer to ensure success of the installation

Loki'd Slim Bean Won't Boot

Anyone else have the issue of it just continuously trying to boot? I'm using the CWM auto-loki that's in the development section.
Reflashed it three more times. Now it freezes @ Samsung battery screen when charging, or if I wait long enough it'll unfreeze. Still loops at Slim Bean startup, what sucks though is that for one thing it mounts as an MTP device so it seems like it's on but just not initializing, another thing is that the original flash I was able to get to the slim bean battery charging screen (but obviously still couldn't turn it on)
Thinking it might be a kernel issue, since I installed ktoonsez's AOSP kernel when I installed it. Any recommendations of a kernel to use? I'm using the CWM recovery that has auto loki so, I could probably use ones made for 9500,9505, etc.
(Pasted this from the Slim Bean thread, haven't gotten an answer in like 5 hours and it's a little urgent xD. I'm on the AT&T S4 of course, any other information I'll be glad to provide. Hopefully this is just a simple fix)

I bet is related to the kernel. I have been using Slim Bean flawlessly, with none of the issues you mention. Using TWRP to flash and recover.
Sent from my SGH-I337 using xda app-developers app

Spunjah413 said:
I bet is related to the kernel. I have been using Slim Bean flawlessly, with none of the issues you mention. Using TWRP to flash and recover.
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
What kernel are you on then, just stock?

Stock Kernel.
Sent from my SGH-I337 using xda app-developers app

I installed Slim Bean with Ktoon kernel and it worked fine. Just make sure to wipe system and the caches. It did take a little longer to boot the first time but after that it was all good.
Sent from my SGH-I337 using xda app-developers app

Isn't ktoonsez kernel for a Touchwiz based ROM?
Slim Bean is AOSP, therefore i'm not sure they jive correctly, which would clearly explain the OP's problem.
EDIT: Didn't realize he updated an AOSP based Kernel. In anycase OP, I would still attempt using the stock kernel to see if you problems get fixed.

Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP

LostInMyHead said:
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
Click to expand...
Click to collapse
Patching a patched kerenel changes nothing. Dan said if you run loki on a patched recovery or kernel it just send the original to the output. Nothing happens.
Sent from my AT&T S4 running an international ROM.

_Dennis_ said:
Patching a patched kerenel changes nothing. Dan said if you run loki on a patched recovery or kernel it just send the original to the output. Nothing happens.
Sent from my AT&T S4 running an international ROM.
Click to expand...
Click to collapse
Thanks for clarification.

LostInMyHead said:
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
Click to expand...
Click to collapse
I know someone else clarified this already, but when I downloaded Slim it actually wasn't Loki patched for whatever reason, and I couldn't boot without reinstalling stock. I did download the one in the right thread, it just didn't have a boot.lok in it for whatever reason. Anyways, I'm gonna try reflashing and wiping /system another time, wish me luck. I don't have the original kernel backed up though because I'm an idiot, so does anyone have a link to that? If not I could probably scour it out somewhere, but just wondering for convenience's sake.

iKat said:
I know someone else clarified htis already, but when I downloaded Slim it actually wasn't Loki patched for whatever reason, and I couldn't boot without reinstalling stock. I did download the one in the right thread, it just didn't have a boot.lok in it for whatever reason. Anyways, I'm gonna try reflashing and wiping /system another time, wish me luck. I don't have the original kernel backed up though because I'm an idiot, so does anyone have a link to that? If not I could probably scour it out somewhere, but just wondering for convenience's sake.
Click to expand...
Click to collapse
In advanced restore boot is the kernel.
Download the ROM and addons again, you shouldnt have any issues... If you are currently on stock, do a comprehensive wipe, a manual format of system and data

LostInMyHead said:
In advanced restore boot is the kernel.
Download the ROM and addons again, you shouldnt have any issues... If you are currently on stock, do a comprehensive wipe, a manual format of system and data
Click to expand...
Click to collapse
No files found :/ I guess I'll reinstall stock, back stuff up, and do the comprehensive wipe like you said. I really, really want Slim, lol.
Edit: Well, ****. Reinstalled stock with Odin and now no matter how many times I reboot I only have a status bar.. phone is fairly hot too. So, now I don't even have access to recovery ;-;

iKat said:
No files found :/ I guess I'll reinstall stock, back stuff up, and do the comprehensive wipe like you said. I really, really want Slim, lol.
Edit: Well, ****. Reinstalled stock with Odin and now no matter how many times I reboot I only have a status bar.. phone is fairly hot too. So, now I don't even have access to recovery ;-;
Click to expand...
Click to collapse
Flash back to stcok with ODIN
Use the one click tool to get LOKI recovery
The ROM and addons are in the OP of the SLIM LOKI Thread

LostInMyHead said:
Flash back to stcok with ODIN
Use the one click tool to get LOKI recovery
The ROM and addons are in the OP of the SLIM LOKI Thread
Click to expand...
Click to collapse
Oh my lord, thank you good sir. Slim Bean is up and working as of right now ^^;. May be a little bit before I apply a custom kernel though o.o

Stock att kernal, updating camera firmware

I've been searching for the stock kernal for at&t users for s bit now, can't find it I'm trying to fix the annoying "updating camera firmware,please wait..." message. Unless there's a better way, I'll just assume you have to flash the sock kernal to update it. But if you flash the sock Kernal, wouldn't the phone fail on boot?
Sent from my GT-I9505 using xda app-developers app

bubblebuddyi said:
I've been searching for the stock kernal for at&t users for s bit now, can't find it I'm trying to fix the annoying "updating camera firmware,please wait..." message. Unless there's a better way, I'll just assume you have to flash the sock kernal to update it. But if you flash the sock Kernal, wouldn't the phone fail on boot?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
What ROM are you running? Omega?
Sent from my GT-I9505 using xda app-developers app

rcklss1 said:
What ROM are you running? Omega?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
No, I'm running Wanamlite v1.0.
I just reinstalled the stock AT&T rom to allow the camera to update, but when I ran the camera, no update appeared. So I figured it was all set. After re-rooting, I re-installed Wanamlite and KT kernal, open up the camera, and sure enough the message re-appears. I didn't perform any wipes. But it looks like I'll have to because all the AT&T bloatware was re-installed again.

bubblebuddyi said:
No, I'm running Wanamlite v1.0.
I just reinstalled the stock AT&T rom to allow the camera to update, but when I ran the camera, no update appeared. So I figured it was all set. After re-rooting, I re-installed Wanamlite and KT kernal, open up the camera, and sure enough the message re-appears. I didn't perform any wipes. But it looks like I'll have to because all the AT&T bloatware was re-installed again.
Click to expand...
Click to collapse
Your mistake was reinstalling Wanamlite again. Here's how you install non AT&T ROMs
1. Root your phone. I used the one click TWRP and Loki method.
2. Factory Reset and install custom ROM.
3. Install AT&T kernel. Let it boot up. Open Camera.
4. Reboot to recovery. Install custom kernel. Wipe cache and Dalvik. Fix Permissions.
5. Reboot. All done.
Sent from my Galaxy S4

Baldilocks said:
Your mistake was reinstalling Wanamlite again. Here's how you install non AT&T ROMs
1. Root your phone. I used the one click TWRP and Loki method.
2. Factory Reset and install custom ROM.
3. Install AT&T kernel. Let it boot up. Open Camera.
4. Reboot to recovery. Install custom kernel. Wipe cache and Dalvik. Fix Permissions.
5. Reboot. All done.
Sent from my Galaxy S4
Click to expand...
Click to collapse
Thanks, you're right about my mistake lol I ended up just installing someone else's ROM and it works perfectly. I'm a bit lost reading your instructions, It was my understanding that custom ROM's would not load with stock kernel?

bubblebuddyi said:
Thanks, you're right about my mistake lol I ended up just installing someone else's ROM and it works perfectly. I'm a bit lost reading your instructions, It was my understanding that custom ROM's would not load with stock kernel?
Click to expand...
Click to collapse
You need a carrier kernel for your custom ROM.
Sent from my Galaxy S4

Baldilocks said:
You need a carrier kernel for your custom ROM.
Sent from my Galaxy S4
Click to expand...
Click to collapse
can you link to a stock kernel for the AT&T i337?

xxhorseriderxxx said:
can you link to a stock kernel for the AT&T i337?
Click to expand...
Click to collapse
Exactly, its nice he can recommend installing a stock kernel, but they are not to be found. I asked in another thread and didn't get an answer. I somehow got it to work just wiping and installing Omega 5.0 Then to get wifi to work I installed ktoonez kernel.
Sent from my GT-I9505 converted SGH-I337

highaltitude said:
Exactly, its nice he can recommend installing a stock kernel, but they are not to be found. I asked in another thread and didn't get an answer. I somehow got it to work just wiping and installing Omega 5.0 Then to get wifi to work I installed ktoonez kernel.
Sent from my GT-I9505 converted SGH-I337
Click to expand...
Click to collapse
okay, assuming you're using the AT&T variant, I did this:
I got the looping "installing camera firmware" and tried faux an ktoonsez with no luck
I flashed this tmobile stock kernel and the camera firmware updated successfully by going into the camera app.
I then just flashed faux kernel back and everything worked great.
http://forum.xda-developers.com/showthread.php?t=2271976
I use shabbypenguin's auto loki CWM recovery, but you'll have to definitely flash the loki patch after the tmo kernel to make this work.
http://forum.xda-developers.com/showthread.php?t=2291956