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
Related
Hey I'm new to the forums but been reading them for a while and I just have a question with OTA updates. I have a nexus 4 that's been rooted and have clockwork mod. I have also flashed the .33 baseband on 4.2.2. I have stock rom but Franco kernel however I backed up the stock kernel with his updater app.
I know I can't OTA with the kernel but flashing the stock one is no big deal. Can I OTA with the rest being on there?
Also if I do the lte wifi hotspot fix will that stop the OTA update as well?
Thanks in advance.
Sent from my Nexus 4 using xda premium
As long you have clockwork mod on the rom you can not OTA...its always going to be manual way of flashing the OTA and that process will remove clockwork mod but using apps like voodoo keeps you rooted so you can easily install clockwork mod again after the update.
No Recovery+Stock ROM+Stock Kernel+Stock Latest Radio= auto OTA update.
I hope that made sense..but i could be wrong but that's what works for me.
Sent From My Beasty Nexus 4 with Awesome Beats.
ROM: Mysterious AOKP 4.2.2
Kernel: Faux 123 latest tbm.
Recovery: TWRP
Helderg1984 said:
Hey I'm new to the forums but been reading them for a while and I just have a question with OTA updates. I have a nexus 4 that's been rooted and have clockwork mod. I have also flashed the .33 baseband on 4.2.2. I have stock rom but Franco kernel however I backed up the stock kernel with his updater app.
I know I can't OTA with the kernel but flashing the stock one is no big deal. Can I OTA with the rest being on there?
Also if I do the lte wifi hotspot fix will that stop the OTA update as well?
Thanks in advance.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
You CAN ota if you have a custom recovery.
However, the WiFi hotspot fix will kill it.
I made a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=2145848
Sent from my Nexus 7 using xda premium
So if anything is modded at all except for basic root I won't be able to apply the update that arrives to my phone directly right? I will have to flash it in cwm? I assume I will have to wipe cache and such before I apply the zip right?
Do I have to revert anything back stock or can I just flash the zip directly over what I have now and just re apply the kernel and baseband?
Sent from my Nexus 4 using xda premium
Sorry one more thing with the latest SU I will stay rooted I think but I will lose cwm and have to re obtain it or will I keep it if survival mode is checked?
Sent from my Nexus 4 using xda premium
Helderg1984 said:
Sorry one more thing with the latest SU I will stay rooted I think but I will lose cwm and have to re obtain it or will I keep it if survival mode is checked?
Click to expand...
Click to collapse
If you flash it from CWM then you will keep CWM and also keep root (if you say yes when it asks you).
Sent from my Nexus 4
Sorry I am a bit confused still, when I get the update.zip and flash it in CWM do I have to wipe or no? and if I don't will everything stay the same? or will I lose my 0.33 baseband and kernel? I'm also wanting to do the lte hotspot fix so would I lose that too?
steviewevie said:
If you flash it from CWM then you will keep CWM and also keep root (if you say yes when it asks you).
Sent from my Nexus 4
Click to expand...
Click to collapse
Helderg1984 said:
Sorry I am a bit confused still, when I get the update.zip and flash it in CWM do I have to wipe or no? and if I don't will everything stay the same? or will I lose my 0.33 baseband and kernel? I'm also wanting to do the lte hotspot fix so would I lose that too?
Click to expand...
Click to collapse
You don't have to wipe.It does not matter if you wipe or not, you will still lose your base band, you'll just have to flash the old baseband again. As for the kernel if the ota comes with a new kernel your old stock kernel will be replaced with the new one in the ota.
You actually can accept a ota update with a custom recovery but you have to be stock everything else, no other mods or anything. The ota will install fine and youll see that it goes through your custom recovery when updating. After the update you will lose root and your custom recovery however unless you recovery someone holds onto it.
As I know, we need to modify something after installing custom recovery. Else, stock recovery will be installed upon reboot. So even after modifying, OTA still works ?
Rizy7 said:
You actually can accept a ota update with a custom recovery but you have to be stock everything else, no other mods or anything. The ota will install fine and youll see that it goes through your custom recovery when updating. After the update you will lose root and your custom recovery however unless you recovery someone holds onto it.
Click to expand...
Click to collapse
Sent from Mako
So bascially no matter what i have on the phone update.zip will go through fine and put on the phone what it contains and it's up to me to put everything back? Also I've heard mixed opinions if I will lose root and CWM, mostly people say it will give me an option to keep it after applyng the update.
heat361 said:
You don't have to wipe.It does not matter if you wipe or not, you will still lose your base band, you'll just have to flash the old baseband again. As for the kernel if the ota comes with a new kernel your old stock kernel will be replaced with the new one in the ota.
Click to expand...
Click to collapse
heat361 said:
You don't have to wipe.It does not matter if you wipe or not, you will still lose your base band, you'll just have to flash the old baseband again. As for the kernel if the ota comes with a new kernel your old stock kernel will be replaced with the new one in the ota.
Click to expand...
Click to collapse
Everything about this post is incorrect.
I don't mean to be a jerk but I've seen you post a lot of false info lately. I know you'd like to help, but it only confuses people when they see contradictory info.
Helderg1984 said:
So bascially no matter what i have on the phone update.zip will go through fine and put on the phone what it contains and it's up to me to put everything back? Also I've heard mixed opinions if I will lose root and CWM, mostly people say it will give me an option to keep it after applying the update.
Click to expand...
Click to collapse
Just read the thread I linked earlier. It has answers to your questions.
Sent from my Nexus 4 using xda premium
El Daddy said:
Everything about this post is incorrect.
I don't mean to be a jerk but I've seen you post a lot of false info lately. I know you'd like to help, but it only confuses people when they see contradictory info.
Just read the thread I l
Can you tell me what's wrong with what I said? I was assuming he was on stock rooted with a custom recovery. Is it not true that if you get an ota update and it contains a new baseband and new stock kernel it will overwrite the last last stock kernel and baseband.
Click to expand...
Click to collapse
heat361 said:
El Daddy said:
Everything about this post is incorrect.
I don't mean to be a jerk but I've seen you post a lot of false info lately. I know you'd like to help, but it only confuses people when they see contradictory info.
Just read the thread I l
Can you tell me what's wrong with what I said? I was assuming he was on stock rooted with a custom recovery. Is it not true that if you get an ota update and it contains a new baseband and new stock kernel it will overwrite the last last stock kernel and baseband.
Click to expand...
Click to collapse
No it doesn't overwrite anything. It just fails.
OTA's contain patches. Not complete files. If the original file isn't there it will abort.
I can see how this can be confusing because it is different from custom roms.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
But thats only if he has the lte fix right. So if he just flashes a stock kernel without that patch, the ota could work.
For example the stock boot.img
I'm rooted with cwm, custom kernel and old baseband, stock rom. I mean I can very easily revert my kernel back to stock and flash the newest baseband.
The only thing is there's a bunch of stuff I might want to do more but don't want to make it hard to update since it's important to me.
Sent from my Nexus 4 using xda premium
Sent from my Nexus 4 using xda premium
heat361 said:
But thats only if he has the lte fix right. So if he just flashes a stock kernel without that patch, the ota could work.
For example the stock boot.img
Click to expand...
Click to collapse
Yep. The phone needs to be 100% stock with the exception of the recovery to complete the OTA. If the files,kernel,radio, etc. are replaced to the original state you'd be good to go.
PS. Sorry if I came off as a jerk this morning. I had a case of the Mondays.
Helderg1984 said:
I'm rooted with cwm, custom kernel and old baseband, stock rom. I mean I can very easily revert my kernel back to stock and flash the newest baseband.
The only thing is there's a bunch of stuff I might want to do more but don't want to make it hard to update since it's important to me.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Just as I wrote above, You can do as many modifications as you want, just make sure you bring the phone back to stock before you flash the OTA.zip, otherwise it will fail.
When the new OTA comes out I will update my OTA Help-Desk thread with all the new requirements.
Helderg1984 said:
So bascially no matter what i have on the phone update.zip will go through fine and put on the phone what it contains and it's up to me to put everything back? Also I've heard mixed opinions if I will lose root and CWM, mostly people say it will give me an option to keep it after applyng the update.
Click to expand...
Click to collapse
Just watch this its eazy as 1 2 3!!!
http://www.youtube.com/watch?v=ky5miA8ilr0
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
I have a rooted MK2 device. I tried installing CWM through ROM Manager but my phone will not boot the CWM and when I try it comes up with an error.
It seems to be installing a Loki'd version of CWM recovery will solve the problem, but I don't how to flash loki recoveries and I've looked all over the forums for one specific to loki'd recoveries. Can someone help me out please? I'm relatively new at this so I'm totally unsure about how to proceed. Many thanks!
Sadly, no custom recoveries are currently available for MK2.
Kaze105 said:
Sadly, no custom recoveries are currently available for MK2.
Click to expand...
Click to collapse
Oh no Well I have a few questions then.
1. I would like to install a 4.4 Google Edition rom. Is there any way for me to accomplish this? Also, is it a bad idea to go ahead and flash it without a recovery?
2. Should I revert the recovery back to original? How would I go about doing that?
hsu0216 said:
Oh no Well I have a few questions then.
1. I would like to install a 4.4 Google Edition rom. Is there any way for me to accomplish this? Also, is it a bad idea to go ahead and flash it without a recovery?
2. Should I revert the recovery back to original? How would I go about doing that?
Click to expand...
Click to collapse
There isn't anything you can do so far. The only thing you could do is use an app I can't remember the name of to flash mods to your current system, but you can not flash ROMs and definitely not anything that may need a different kernel. If you want to get a working recovery then find the MJ6-MJ9 thread but only use the recovery tar file, not the rest of it.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
you sir have a locked bootloader (i think)
hsu0216 said:
I have a rooted MK2 device. I tried installing CWM through ROM Manager but my phone will not boot the CWM and when I try it comes up with an error.
It seems to be installing a Loki'd version of CWM recovery will solve the problem, but I don't how to flash loki recoveries and I've looked all over the forums for one specific to loki'd recoveries. Can someone help me out please? I'm relatively new at this so I'm totally unsure about how to proceed. Many thanks!
Click to expand...
Click to collapse
well.....if you were on MF3 then you could load safestrap and then get the google edition but it wont support the 4.4 only the 4.2.2 version of the GE
thats what i did. i highly doubt there will be an unlocked bootloader for MK2 im on mf3 and cant even update to 4.3 MK2.....ill ask the developer of safestrap and ask him because he was getting a MK2 galaxy s4 on att last week and he was doing some testing....or you can do some research your self but im happy to help even though my account says im a junior member i know quite a lot....
if safestrap works here is a link http://forum.xda-developers.com/showthread.php?t=2448726
IF SAFESTRAP WORKS LOOK UP A GUIDE ON HOW TO USE IT I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE BECAUSE I TOLD YOU ABOUT IT also dont use the stock rom slot if all this works
Dude.
Search. Read. Repeat.
Anx XDA says ni question too stupid..Well some reaponses are..Oh GOD!!!
Sent from my SAMSUNG-SGH-I337 using Tapatalk
r1tesh said:
Anx XDA says ni question too stupid..Well some reaponses are..Oh GOD!!!
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
No question too stupid. But asking a question that has been answered hundreds of times and refusing to use the search button...
I have searched the forum and have been overwhelmed with threads that I can't seem to make fit my situation so I apologize if I've overlooked something obvious.
I have an AT&T S4 That came running UCUAMDL. I rooted when I first got it and have not done anything sense. I would like to update the stock rom but I don't want to lose root. At this time I'm not interested in custom roms although I've done it before on my S2. What would be the best option to achieve this aim.
Thank you in advance and again sorry if I missed this somewhere.
podunk said:
I have searched the forum and have been overwhelmed with threads that I can't seem to make fit my situation so I apologize if I've overlooked something obvious.
I have an AT&T S4 That came running UCUAMDL. I rooted when I first got it and have not done anything sense. I would like to update the stock rom but I don't want to lose root. At this time I'm not interested in custom roms although I've done it before on my S2. What would be the best option to achieve this aim.
Thank you in advance and again sorry if I missed this somewhere.
Click to expand...
Click to collapse
Your best option would to be to flash a 4.4.2 custom rom. There is no root for the latest, nb1, firmware.
Sent from my Nexus 5
odin to mk2 then, venom to a kit kat rom.
jd1639 said:
Your best option would to be to flash a 4.4.2 custom rom. There is no root for the latest, nb1, firmware.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for the quick response. Makes since. So as long as I flash a custom rom I don't have to worry about bootlock or anything, right? What's the closest rom to stock as far as stability & compatibility?
Again, much appreciation.
podunk said:
Thanks for the quick response. Makes since. So as long as I flash a custom rom I don't have to worry about bootlock or anything, right? What's the closest rom to stock as far as stability & compatibility?
Again, much appreciation.
Click to expand...
Click to collapse
Do you have a custom recovery and are you familiar with Loki?
Sent from my SAMSUNG-SGH-I727
jd1639 said:
Do you have a custom recovery and are you familiar with Loki?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I don't have my phone right here but I'm fairly certain I'm running TWRP.
podunk said:
I don't have my phone right here but I'm fairly certain I'm running TWRP.
Click to expand...
Click to collapse
Just double checked and yes I've got TWRP installed.
podunk said:
I don't have my phone right here but I'm fairly certain I'm running TWRP.
Click to expand...
Click to collapse
Then I would try kangakat which I believe is loki'd. Make a backup in twrp of your current rom before you do anything. If you don't have titanium backup, get it and backup your apps. And make sure you have Google's backup and restore checked, settings, backup& restore.
Sent from my Nexus 5
iateshaggy said:
odin to mk2 then, venom to a kit kat rom.
Click to expand...
Click to collapse
Worst advice possible. He's on amdl and can flash custom recovery and use loki.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
jd1639 said:
Then I would try kangakat which I believe is loki'd. Make a backup in twrp of your current rom before you do anything. If you don't have titanium backup, get it and backup your apps. And make sure you have Google's backup and restore checked, settings, backup& restore.
Sent from my Nexus 5
Click to expand...
Click to collapse
Yes I have titanium backup and I will be sure to back up everything.
I was not familiar with loki so I did a little reading. Correct me if I'm wrong here but loki is something the rom developer uses to make it so my rom installation will go around the boot loader. I don't need to install anything related to loki I just need to make sure any rom that I chose is "loki'd". Correct? Therefore if my understanding is correct, once i've taken backup precautions, I would copy the loki'd rom to my sd card and flash via TWRP?
Again, I want to thank you for your help.
podunk said:
Yes I have titanium backup and I will be sure to back up everything.
I was not familiar with loki so I did a little reading. Correct me if I'm wrong here but loki is something the rom developer uses to make it so my rom installation will go around the boot loader. I don't need to install anything related to loki I just need to make sure any rom that I chose is "loki'd". Correct? Therefore if my understanding is correct, once i've taken backup precautions, I would copy the loki'd rom to my sd card and flash via TWRP?
Again, I want to thank you for your help.
Click to expand...
Click to collapse
Loki is something the ROM developer can use. You either need to make sure the ROM is loki'd, or if you ever want to try something like an I9505 ROM, flash the loki-doki zip file after flashing the ROM (i'm not sure where the link is). Most ROMs in our dev section will have loki included, but i'd keep the loki-doki zip on your SD card just in case.
DeadlySin9 said:
Loki is something the ROM developer can use. You either need to make sure the ROM is loki'd, or if you ever want to try something like an I9505 ROM, flash the loki-doki zip file after flashing the ROM (i'm not sure where the link is). Most ROMs in our dev section will have loki included, but i'd keep the loki-doki zip on your SD card just in case.
Click to expand...
Click to collapse
+1. Just make sure you wipe in twrp and flash your rom.
Sent from my Nexus 5
I tried to figure this out and I'm lost. I've not been keeping up with development on this phone for a while. I'm currently on stock rooted MDL, stock recovery. I'm looking to move to rooted current stock rom. How do I go about this. As simple as just putting a new recovery on and flashing the new one? Or do I need to be careful of anything?
Feels weird to be out of touch with how everything works now.
cegna09 said:
I tried to figure this out and I'm lost. I've not been keeping up with development on this phone for a while. I'm currently on stock rooted MDL, stock recovery. I'm looking to move to rooted current stock rom. How do I go about this. As simple as just putting a new recovery on and flashing the new one? Or do I need to be careful of anything?
Feels weird to be out of touch with how everything works now.
Click to expand...
Click to collapse
You need to put a custom recovery on. Then flash the ROM in the recovery. Since you're rooted you could use goo manager to put twrp on
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
jd1639 said:
You need to put a custom recovery on. Then flash the ROM in the recovery. Since you're rooted you could use goo manager to put twrp on
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
If that's it awesome. Reading about the latest stock roms I was just confusing myself and thinking there was some new BS to deal with.
cegna09 said:
If that's it awesome. Reading about the latest stock roms I was just confusing myself and thinking there was some new BS to deal with.
Click to expand...
Click to collapse
Just FYI, if on i337, get familiar with loki-doki and when you need to flash it--:good:
I am in the same boat. Have tried goomanager and rom manager but both failed to load recoveries. It seems they have moved on to 4.4.2 kitkat and no longer work with 4.2.2 MDL. Have also tried to find .tar files for older recoveries and flash with ODIN but no luck. Afraid to OTA update from AT&T and get MK2. Any help would GREATLY be appreciated.
capti2 said:
I am in the same boat. Have tried goomanager and rom manager but both failed to load recoveries. It seems they have moved on to 4.4.2 kitkat and no longer work with 4.2.2 MDL. Have also tried to find .tar files for older recoveries and flash with ODIN but no luck. Afraid to OTA update from AT&T and get MK2. Any help would GREATLY be appreciated.
Click to expand...
Click to collapse
Not sure but can you unroot and reroot with Adam's Motochopper. It installs twrp. Maybe JD can confirm that.
Sent from my GT-I9505G using Tapatalk
rugmankc said:
Not sure but can you unroot and reroot with Adam's Motochopper. It installs twrp. Maybe JD can confirm that.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
I can confirm from the short time i was on MDL that CASUAL does install TWRP.
DeadlySin9 said:
I can confirm from the short time i was on MDL that CASUAL does install TWRP.
Click to expand...
Click to collapse
Thank you for the advice . It worked like a charm.
capti2 said:
Thank you for the advice . It worked like a charm.
Click to expand...
Click to collapse
Glad you got it--you can now flash custom recoveries from recovery. I like twrp 2.5.0.2
Don't try goomanager anymore--not needed
There are a couple files to delete so you don't get auto updated. Some have Update in name and one has FOTA. I don't have them in front of me atm
Get a nandroid asap and put copy on pc too
Plus backup efs
Just one last check before I try and mess with things tonight. Since I'm on MDL still, to install a new current ROM (like this one http://forum.xda-developers.com/showthread.php?t=2280556), all I need to do is:
- install a custom recovery (TWRP 2.5.0.2 looks like the most recent)
- backup
- full wipe
- flash new ROM
I shouldn't have to mess with any of the safestrap stuff correct?
Just trying to be cautious.
cegna09 said:
Just one last check before I try and mess with things tonight. Since I'm on MDL still, to install a new current ROM (like this one http://forum.xda-developers.com/showthread.php?t=2280556), all I need to do is:
- install a custom recovery (TWRP 2.5.0.2 looks like the most recent)
- backup
- full wipe
- flash new ROM
I shouldn't have to mess with any of the safestrap stuff correct?
Just trying to be cautious.
Click to expand...
Click to collapse
No SafeStrap. Backup should include System. Make sure to read OP and last few pages of thread for any new info. Make sure ROM doesn't need loki-doki. Most in att forum don't. What recovery are you on now?
Sent from my GT-I9505G using Tapatalk
rugmankc said:
No SafeStrap. Backup should include System. Make sure to read OP and last few pages of thread for any new info. Make sure ROM doesn't need loki-doki. Most in att forum don't. What recovery are you on now?
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Thank you.
I thought I was on stock recovery, but checking just now apparently I put OUDhs CWM Touch Recovery v1.0.3.4 on sometime in the past year. I'll either go to the latest version of CWM or TWRP before doing anything.
cegna09 said:
Thank you.
I thought I was on stock recovery, but checking just now apparently I put OUDhs CWM Touch Recovery v1.0.3.4 on sometime in the past year. I'll either go to the latest version of CWM or TWRP before doing anything.
Click to expand...
Click to collapse
If you are on a custom recovery, you "should" be able to flash this thru recovery--if you want it--:good:
https://www.dropbox.com/sh/yhrq0tia8512rj9/AAB_scBnDHWPcg_w2UXw3V5ha/TWRP_Flashable-2.5.0.2.zip
rugmankc said:
If you are on a custom recovery, you "should" be able to flash this thru recovery--if you want it--:good:
https://www.dropbox.com/sh/yhrq0tia8512rj9/AAB_scBnDHWPcg_w2UXw3V5ha/TWRP_Flashable-2.5.0.2.zip
Click to expand...
Click to collapse
awesome. Again thank you.
I'll play with things tonight and see how it goes.
cegna09 said:
awesome. Again thank you.
I'll play with things tonight and see how it goes.
Click to expand...
Click to collapse
How did everything go? Im on MDL rooted custom rom and really want to get back to stock rooted. I know I dont need to do the same process as you but I was curious how things went.