Related
this is maybe nothing new to many of you and will hopefully become obsolete soon, but i thought i post it anyway.
it´s probably already written elsewhere on xda, i don´t know.
this is not an elegant way to do it, but it works.
be aware that both operating systems will share the internal storage (storage/emulated/0).
i´m not sure if this could cause any problems. maybe you can tell me ?
updates marked in green and yellow.
always make nandroid backups and maybe it´s not a bad idea to backup your internal storage too !
i´m not responsible for anything you do or not do !
flashing a kernel will raise your knox counter to 0×1 !
from the safestrap blog:
DON’T RESTORE A CUSTOM ROM-SLOT BACKUP TO THE STOCK ROM. THIS WILL MOST LIKELY BRICK YOUR PHONE.
if you uprade to 4.4.2 kitkat you can´t go back to to 4.3 no more because kk comes with a new bootloader. you can not dual boot a 4.3 and a 4.4.2 rom and you wont be able to use CM. i dont know if safestrap is compatible with 4.4.2 as i´m still on 4.3.
requierements:
safestrap, CM rom and kernel(flashable zip) that works on the rom, TW based rom and kernel(flashable zip) that works on the rom, microsd card, supersu(when coming from CM)
i´m using temasek's UNOFFICIAL CM11 BUILD and bobcatrom for this guide. did it with x-note and the official cm nightly also. if you get an error installing the nightly, remove the first line from the updater-script.
put the required files on your external sd card and follow the instructions.
coming from installed TW rom:
1.install safestrap apk.
2.open safestrap app and select install.
3.reboot into safestrap and make a nandroid backup of your rom.
4.create a rom slot and set it active.
5.restore the backup you just made to that rom slot. (this way you can have any rom on a rom slot. safestrap doesn´t support aroma installer but you can restore backups of aroma based roms, that you installed with twrp to the "stock rom slot" first.)
6.(optional) reboot to see if everything is ok. your rom now boots from rom slot 1.
7.now that you have successfully "cloned" your rom, reboot to safestrap again.
8.set the "stock rom" slot active and wipe.
9.install CM to the "stock rom" slot.
10.reboot into twrp (not safestrap !) and flash CM kernel.
11.reboot your brand new CM and enjoy. for now, you can only boot into CM, safestrap and your TW rom are unreachable.
12.to make your TW rom boot again, reboot into twrp and flash TW kernel.
13.reboot. safestrap shows up again, enter recovery and set rom slot 1 active.
14.reboot. you are back to your TW rom.
from now on, whenever you want to switch between operating systems, just repeat steps 10 - 14.
you can not have CM on a rom slot, it must be on the "stock rom" slot !
this is how to do it:
coming from installed CM rom:
1.install supersu (not superuser !). i used the flashable zip but downloading it from playstore should work too. (if you did just install CM and want to use the flashable supersu, reboot into CM one time and finish the wizard. flashing it directly after installing CM, without rebooting will result in system inconsistency.)
2.install the safestrap apk and open safestrap. grant su permission and select install recovery (if you dont get the supersu popup and safestrap shows "not rooted", uninstall safestrap and reinstall again). do not choose reboot to recovery from the safestrap app, just do a normal reboot.
3.reboot into twrp, flash your TW kernel then reboot. (if you don´t do this, safestrap wont show up as it does only work with TW kernel.)
4.safestrap splashscreen shows up. enter safestrap recovery and backup your "stock rom" (your installed CM).
5.reboot into twrp. wipe and install the TW rom of your choice.
6.boot into your brand new TW rom and install safestrap once again as you did in step 2. (skip this step if you are still able to enter safestrap recovery)
7.follow steps 3 - 14 from the TW route written above. on step 9 you do not install of course, you do restore your backup of CM.
you can of course do this with 2 or more TW roms too (without CM), you wouldn´t normally be able to install in safestrap (aroma!).
you just don´t switch kernels then.
if you flash with twrp often, there is a chance to get the efs corruption issue. if wireless connection are dead, your phone does some weird things and you do not have an efs backup, there is a fix in this thread.
have fun !
important !
even when you flash stock rom with odin, your rom slots wont be removed. you have to delete them first in safestrap recovery to get your full internal storage capacity back !
Would someone be able to make a safestrap for tge N900T
Sent from my SM-N900T using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2011403
[MOD][JAN 04] MultiROM v21 anyone?
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 07:27 AM ---------- Previous post was at 07:25 AM ----------
Porting that over to Note 3 would be great! It's also on Nexus 5! And Nexus 5 & Note 3 has the same chipset! MSM8974? Correct me if im wrong would be great with a port though..
Sent from my SM-N9005 using XDA Premium 4 mobile app
M8 the for the info but do we know if this will work with latest tw rom 4.4.2?
Στάλθηκε από το SM-N9005 μου χρησιμοποιώντας Tapatalk
I read about multirom, awesome tool.
Hope too that sb will port it. @BlueChris i dont see why this shouldnt work.
Just flash it with odin, take a backup and so on...
CM 11 is also kitkat based.
Be aware, that when you flash it with odin, you loose everything. So backup first!
I can not try it by myself atm. I have a very slow connection where i am now, would take me a week to download.
Edit: some people seem to have trouble with flashing kitkat, so you better read a few pages before doing a mistake.
kk comes with a new bootloader, might be a good idea to get some info before flashing it.
updated: CM route
Kernels
This information is really great, thanks a ton for posting this! I'm currently up to step 10, where can I get Cyanogenmod's kernel only? Furthermore, it sounds like I'll need stock kernel only too, right?
CauselessEffect said:
This information is really great, thanks a ton for posting this! I'm currently up to step 10, where can I get Cyanogenmod's kernel only? Furthermore, it sounds like I'll need stock kernel only too, right?
Click to expand...
Click to collapse
the kernel is somewhere inside the rom archive, cant remember. just extract it and search for boot.img.
put boot.img into the root of the flashable zip i attached and you are ready for step 10.
be sure to have any touchwiz kernel ready to be on the safe side.
any kernel will work for both(CM/TW).
Cool, thanks! Boot.img was in the root directory of the extracted CM zip. It all works now! By the way, if anyone is interested, I'm using the T-Mobile version of the Note 3. To get Safestrap working, you have to use the AT&T version 3.71. This is the file I used coming from stock 4.3: goo.im/devs/Hashcode/note3/hlteatt/safestrap/Safestrap-HLTEATT-3.71.apk
Since I didn't know where to find the stock kernel, I ended up experimenting and just did a restore of only the boot partition from TWRP. This got Safestrap back and then I just reactivated Slot 1 to get back to stock. Is there anything else on the boot partition besides the kernel that I should worry about regularly flashing? I'm hoping this is essentially the same thing as flashing a zipped kernel.
I just discovered that I could take the file "boot.emmc.win" from my original TWRP backup (not the one made from Safestrap), copy it to my computer, rename it to "boot.img", copy it into that zip you shared, and now I have a flashable stock kernel too!
Thanks for your help and for taking the time to make this tutorial. This is something I plan on using very frequently, it's so much nicer to not have to do complete TWRP backups and restores each time.
Hi, just some questions
1- Can I do it coming from latest Cyanogen nightly but having kk as base? (I have spanish NB4 base)
2- Can I update Cyanogen rom without fear of something to happen because of the kernel?
3- What could happen if I change the kernel?
Thanks
If there's someone interested in porting Tasssadar's MultRom to the Note 3, then she or he might find this link helpful; https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
A.N.Droid said:
this is maybe nothing new to many of you and will hopefully become obsolete soon, but i thought i post it anyway.
it´s probably already written elsewhere on xda, i don´t know.
this is not an elegant way to do it, but it works.
be aware that both operating systems will share the internal storage (storage/emulated/0).
i´m not sure if this could cause any problems. maybe you can tell me ?
updates marked in green and yellow.
always make nandroid backups and maybe it´s not a bad idea to backup your internal storage too !
i´m not responsible for anything you do or not do !
flashing a kernel will raise your knox counter to 0×1 !
from the safestrap blog:
DON’T RESTORE A CUSTOM ROM-SLOT BACKUP TO THE STOCK ROM. THIS WILL MOST LIKELY BRICK YOUR PHONE.
if you uprade to 4.4.2 kitkat you can´t go back to to 4.3 no more because kk comes with a new bootloader. you can not dual boot a 4.3 and a 4.4.2 rom and you wont be able to use CM. i dont know if safestrap is compatible with 4.4.2 as i´m still on 4.3.
requierements:
safestrap, CM rom and kernel(flashable zip) that works on the rom, TW based rom and kernel(flashable zip) that works on the rom, microsd card, supersu(when coming from CM)
i´m using temasek's UNOFFICIAL CM11 BUILD and bobcatrom for this guide. did it with x-note and the official cm nightly also. if you get an error installing the nightly, remove the first line from the updater-script.
put the required files on your external sd card and follow the instructions.
coming from installed TW rom:
1.install safestrap apk.
2.open safestrap app and select install.
3.reboot into safestrap and make a nandroid backup of your rom.
4.create a rom slot and set it active.
5.restore the backup you just made to that rom slot. (this way you can have any rom on a rom slot. safestrap doesn´t support aroma installer but you can restore backups of aroma based roms, that you installed with twrp to the "stock rom slot" first.)
6.(optional) reboot to see if everything is ok. your rom now boots from rom slot 1.
7.now that you have successfully "cloned" your rom, reboot to safestrap again.
8.set the "stock rom" slot active and wipe.
9.install CM to the "stock rom" slot.
10.reboot into twrp (not safestrap !) and flash CM kernel.
11.reboot your brand new CM and enjoy. for now, you can only boot into CM, safestrap and your TW rom are unreachable.
12.to make your TW rom boot again, reboot into twrp and flash TW kernel.
13.reboot. safestrap shows up again, enter recovery and set rom slot 1 active.
14.reboot. you are back to your TW rom.
from now on, whenever you want to switch between operating systems, just repeat steps 10 - 14.
you can not have CM on a rom slot, it must be on the "stock rom" slot !
this is how to do it:
coming from installed CM rom:
1.install supersu (not superuser !). i used the flashable zip but downloading it from playstore should work too. (if you did just install CM and want to use the flashable supersu, reboot into CM one time and finish the wizard. flashing it directly after installing CM, without rebooting will result in system inconsistency.)
2.install the safestrap apk and open safestrap. grant su permission and select install recovery (if you dont get the supersu popup and safestrap shows "not rooted", uninstall safestrap and reinstall again). do not choose reboot to recovery from the safestrap app, just do a normal reboot.
3.reboot into twrp, flash your TW kernel then reboot. (if you don´t do this, safestrap wont show up as it does only work with TW kernel.)
4.safestrap splashscreen shows up. enter safestrap recovery and backup your "stock rom" (your installed CM).
5.reboot into twrp. wipe and install the TW rom of your choice.
6.boot into your brand new TW rom and install safestrap once again as you did in step 2. (skip this step if you are still able to enter safestrap recovery)
7.follow steps 3 - 14 from the TW route written above. on step 9 you do not install of course, you do restore your backup of CM.
you can of course do this with 2 or more TW roms too (without CM), you wouldn´t normally be able to install in safestrap (aroma!).
you just don´t switch kernels then.
if you flash with twrp often, there is a chance to get the efs corruption issue. if wireless connection are dead, your phone does some weird things and you do not have an efs backup, there is a fix in this thread.
have fun !
important !
even when you flash stock rom with odin, your rom slots wont be removed. you have to delete them first in safestrap recovery to get your full internal storage capacity back !
Click to expand...
Click to collapse
Sorry to bring back this thread, but I've spent a few weeks looking and I think this may be the solution to my problems.
I broke the screen on my old Verizon rooted S3 running CM11, but managed to get a backup on my SD card before hte phone became unusable.
I then purchased another galaxy S3 running 4.3 stock (so locked bootloader) Using this dual-boot method for CM, is it possible for me to restore my old ROM onto my new phone? If so, please advise on any possible differences I may need to follow in the procedure.
Thank you so much!
Yellow is a horrible color to look at. Change it to something less bright
Guys is this safe? I think I saw people saying they get stuck in bootloops and all that. I have an international note 3 running s5 port 4.4.2
Sent from my SM-G900F using XDA Premium 4 mobile app
nicholaschum said:
Yellow is a horrible color to look at. Change it to something less bright
Click to expand...
Click to collapse
Yellow looks great in tapatalk with dark theme
__________________________________
any news for lollipop dualboot??
fefuzzo said:
any news for lollipop dualboot??
Click to expand...
Click to collapse
+1
+2
Checkout:
http://forum.xda-developers.com/showthread.php?t=2447534&highlight=9005
OR
http://forum.xda-developers.com/android/software-hacking/tool-multirom-recovery-replacement-t3102395
I have had a look at them, and can see how they would work.
I would like to use them one or the other to setup TW and CM12.1
I have not had the time to sit there and do this. So am posting these links as Untested. But multiple reports show it does work.
To start, my device is fine (AFAIK ), and I'm inquiring for informational/learning purposes.
I was running franco kernel and wanted to flash the stock kernel again and these are the steps I took.
1) Flashed system.img first and then flashed boot.img second in fastboot
2) Reboot
3) System update was available, realized I flashed 4.4 files instead of 4.2 files so I accepted the update (I assume I should have just flashed the proper system.img and boot.img from 4.4.2)
4) After update I notice root was no longer working and upon launching SuperSU it told me there was an issue (didn't prompt to install/update)
5) Boot into recovery and I get the Android with a red '!', realize my recovery is borked and proceed to re-install TWRP from flashboot
6) TWRP successfully installed so I boot into TWRP and install the same SuperSU zip I used to originally install root
7) Boot back into my Nexus 5 and SuperSU isn't installed. I check the Play Store and see the app has the option to install (which verifies it wasn't installed)
8) Install SuperSU from Play Store, it requires an update which I do
9) I now have root and verified via FKU that I'm running stock kernel (which I then proceeded to uninstall FKU)
So, what happened with my root install via TWRP? It's the same zip I used to install my original root (which was only 1-2 weeks ago) and TWRP successfully installed the zip with no errors. Does anyone know what happened? Why wasn't SuperSU installed?
Also, on a side note, I'd appreciate if someone could verify I did this all correctly and properly recovered? AFAIK everything is running smooth, but if you notice I did a major mess and I should rectify it, I'd appreciate knowing. I'm new to rooting, so I did my best to recover, but I'm also a fan of reassurance.
1. all you had to do was flash the boot.img. that would have replaced franco kernel and no time nor data would of been lost. its a several second procedure.
2. you took an update. when you do that, you lose your custom recovery and root. its been that way since day 1 of android. theres so much info about that out there that you should have known that, its the most basic knowledge of the modding community. what im saying is there are no excuses
3. supersu got updated, and you were flashing an older version. you should have just grabbed it from the play store, installed the app, opened it, and updated the binaries. or, you can always get the most recent supersu here then flash it http://download.chainfire.eu/381/SuperSU/UPDATE-SuperSU-v1.91.zip
simms22 said:
1. all you had to do was flash the boot.img. that would have replaced franco kernel and no time nor data would of been lost. its a several second procedure.
2. you took an update. when you do that, you lose your custom recovery and root. its been that way since day 1 of android. theres so much info about that out there that you should have known that, its the most basic knowledge of the modding community. what im saying is there are no excuses
3. supersu got updated, and you were flashing an older version. you should have just grabbed it from the play store, installed the app, opened it, and updated the binaries. or, you can always get the most recent supersu here then flash it http://download.chainfire.eu/381/SuperSU/UPDATE-SuperSU-v1.91.zip
Click to expand...
Click to collapse
1. I was misinformed on this. The franco FAQ stated to flash the system.img and boot.img. Based on your response, I'm guessing the system.img is only required for devices other than the Nexus line?
2. I completely understand, and I realize it as soon as I accepted the update. I seen the update, jumped to accept as I'm accustomed to, and preceded to immediately facepalm.
3. So basically, if I understand correctly, I already had SuperSU installed and updated via the Play Store. When I attempted to flash my zip, I was flashing an older version (I was flashing 1.80, your link is up to 1.91). By flashing the older version, it messed with the install, hence why it was missing when I booted back into Android. This is is also why I had to re-install from the Play Store. Did I get that correctly?
alamarco said:
1. I was misinformed on this. The franco FAQ stated to flash the system.img and boot.img. Based on your response, I'm guessing the system.img is only required for devices other than the Nexus line?
2. I completely understand, and I realize it as soon as I accepted the update. I seen the update, jumped to accept as I'm accustomed to, and preceded to immediately facepalm.
3. So basically, if I understand correctly, I already had SuperSU installed and updated via the Play Store. When I attempted to flash my zip, I was flashing an older version (I was flashing 1.80, your link is up to 1.91). By flashing the older version, it messed with the install, hence why it was missing when I booted back into Android. This is is also why I had to re-install from the Play Store. Did I get that correctly?
Click to expand...
Click to collapse
1. flashing the system img would replace the rom itself. if franco kernel changes system files, then this would technically replace them. dirty flashing your rom would do the same. if franco kernel replaces system files, then it(or others based off franco kernel) is the only kernel i know of that does. anyways, i bet leaving whatever changes done to the system wouldnt hurt you if you left it. ill ask francisco if and what system files he changes
2.
3. right. or flash the newer zip.
simms22 said:
1. flashing the system img would replace the rom itself. if franco kernel changes system files, then this would technically replace them. dirty flashing your rom would do the same. if franco kernel replaces system files, then it(or others based off franco kernel) is the only kernel i know of that does. anyways, i bet leaving whatever changes done to the system wouldnt hurt you if you left it. ill ask francisco if and what system files he changes
2.
3. right. or flash the newer zip.
Click to expand...
Click to collapse
Awesome, I appreciate your help and information. I now have a full grasp on what I did wrong so as to not make the same mistake next time. I screwed up this time, but no better time to learn than after a mistake.
I believe that flashing the Franco kernel does change a couple of system files as noted in the Franco kernel Learner Lounge
(aka FAQ)
"Return to stock romz
Franco's kernel changes these system files below, so to change them back you can remove the .bak extension, or fastboot system.IMG and boot.IMG from a factory image found https://developers.google.com/androi...s/images?csw=1 which is probably easier and faster.
Quote:
Originally Posted by franciscofranco View Post
1 - Rename /system/lib/hw/power.msm8974.so.bak to /system/lib/hw/power.msm8974.so
2 - Rename /system/bin/thermal-engine-hh-bak to /system/bin/thermal-engine-hh
3 - Reboot to the boot loader and flash stock Kernel by downloading the Nexus images and then fastboot flash boot boot.img
4 - If you're using those Moto X dalvik patches you gotta reflash stock system.img, just use the images you just downloaded from 2) and do fastboot flash system system.img
5 - ???
6 - Profit.
Click to expand...
Click to collapse
GooGooMuck said:
I believe that flashing the Franco kernel does change a couple of system files as noted in the Franco kernel Learner Lounge
(aka FAQ)
Click to expand...
Click to collapse
That's where I originally got my information from and why I flashed the system.img. Everything else after that was my fault.
Hi All
I succesfully upgraded my firmware and am running the newest Viper and it works great. After reading about multi-rom I got super excited as there was a program I used with a pervious androud (htc phne even i think) to switch between MIUI and a few other ROMS.
Anyways.. I get the "non-exec kernel error" inside of ROM manager as well as TWRP under multiROM ( i think when I attempt to flash another rom in a diff slot).
I've tried installing a few of the kernels through the multirom app and it always seems sucessful as well as just downloading the kernels and flash in TWRP without error.
Does anyone have any suggestions or any extra info I can provide to get this to work? I'd LOVE multiROM so I can try new things and keep my daily driver.
Thanks in advance friends
I have been playing with this also recently. As far as I can tell only the select few kernels work with multirom. The kernel has to be patched to work with multirom. I'm using lunar kernel(as my primary rom kernel) and everything works fine. You can't use any of the kernels from the international m8 that's on multirom thread. Those are not designed for Verizon m8. I made the mistake of trying to flash those also.
Only the primary ROM needs to be patch with exec. Make sure if your flashing a kernel to a secondary ROM do it in twrp under multi ROM advanced settings and choose the ROM you want to flash the kernel to. The twrp main screen is for your primary rom
Sent from my One M8
I can't get the multirom manager app to "see" the ROM I want to install....Where does one put (ie: folder placement) the zip file you want to install as your secondary?
I rooted using the on-board iroot app. I now have root access and SU on my N8013.
Can I now simply
- use ODIN to load the Gnabo 7 ROM.
- Flash Gnabo, remove phone stuff, and wifi fix.
- Can I use the stock kernel or must I flash a different kernel?
Will this give me the update to KitKat?
mangurian said:
I rooted using the on-board iroot app. I now have root access and SU on my N8013.
Can I now simply
- use ODIN to load the Gnabo 7 ROM.
- Flash Gnabo, remove phone stuff, and wifi fix.
- Can I use the stock kernel or must I flash a different kernel?
Will this give me the update to KitKat?
Click to expand...
Click to collapse
Try rashr inline flash tool from Google play store and flash twrp recovery image from the app this way you have a modern recovery tool and will be able to flash what ever ROM you want.
Just download all the necessary parts to your tablet, reboot into recovery and flash in the given sequence via twrp. Good luck.
tsukaza said:
Just download all the necessary parts to your tablet, reboot into recovery and flash in the given sequence via twrp. Good luck.
Click to expand...
Click to collapse
I would be grateful if you could provide just a bit more info.
- what are the necessary parts?
- where on my table should I put them?
- "given sequence" = Gnabo 7 ROM, then remove phone stuff, then wifi fix??
Sorry to seem so dull. I am just timid about doing this whole ROM bit.
Thanks,
mangurian said:
I would be grateful if you could provide just a bit more info.
- what are the necessary parts?
- where on my table should I put them?
- "given sequence" = Gnabo 7 ROM, then remove phone stuff, then wifi fix??
Sorry to seem so dull. I am just timid about doing this whole ROM bit.
Thanks,
Click to expand...
Click to collapse
Download the ROM, SuperSu, Kernel for N801X, WiFi Fix for N801X and Remove phone stuff for N801x
- Install rashr from Google play store and grant root when asked.
- from rashr install the latest twrp recovery image.
- reboot into twrp recovery to be sure it is working.
- boot back normal.
- down from gnabo v8 post and put zips in the internal/external sdcard, put them in one directory after you downloaded all 5 needed zip files. ROM, su, kernel, fix phone stuff and fix WiFi.
- boot into twrp recovery image.
- Full wipe (cache, dalvik, data, system)
- Flash the ROM, SuperSu, Kernel and Remove phone stuff for N801x ********
- Reboot and do the setup
- Reboot in recovery
- Flash WiFi Fix for N801X ******
- Reboot
well
mangurian said:
I rooted using the on-board iroot app. I now have root access and SU on my N8013.
Can I now simply
- use ODIN to load the Gnabo 7 ROM.
- Flash Gnabo, remove phone stuff, and wifi fix.
- Can I use the stock kernel or must I flash a different kernel?
Will this give me the update to KitKat?
Click to expand...
Click to collapse
posting in the correct section this is not the Q & A..
I don't even believe anybody should respond with any other answer then, please read the forum rules. before posting or beginning a thread. And direct you to the right place.
EASY... relatively speaking.
I read XDA forums for hours and hours... and hours. Seriously. I spent about 20 hours reading XDA just for this. All the info is out there, but it is spread out across a dozen different threads, and multiple posts within those threads.
When I actually went through the process, I had (no lie) eighteen windows open, each with a relevant thread/post.
Sheesh, and people think this is complicated... [/s]
But in the end - I have a custom Lollipop ROM on my phone (Goldeneye v53) and it is working beautifully. And I had NO issues with the process, it all went smoothly.
The phone (which previously was starting to run out of space, lag, and just all-around felt "old") is now like new. And, dare I say... better than a stock S6? It is certainly leaner and meaner than a stock system (that's a good thing - I despise all the bloat on stock systems)
So, to make it easier for all those who come behind me, here is how to do it. In 39 easy steps.
One post.
One list.
Bullet points.
Links.
EASY.
Do this EXACTLY - and you will have a custom ROM on your S4.
Do something "just a little" different... Or miss a step... I'm pretty sure your device will explode, or at least catch on fire.
Either way, there is no express or implied warranty on this process I have collected and posted here. Anything you choose to do to your device is on you, and if something goes wrong, I accept no liability.
For risk mitigation in my case (as I'm an overly anal type) - I made sure that I dug my previous phone out of the closet, charged the battery, installed my SIM, and confirmed that I could use the old phone to at least make calls/texts in the event that "something" happened to my S4 during the upgrade process and I had to go to work the next day without my S4. Everything went smoothly, but IMO you should definitely have a contingency plan just in case.
Note - this is only for those NOT on MDB or MDL bootloaders. You guys have it easy. Don't do all the crap below - you don't need to, and if you DO do it, you are locked into this "complicated" method FOREVER (mwa-ha-haaa!!!)
1. Preparation
1.1 READ THROUGH THIS POST 27 TIMES (NO LESS, NO MORE) AND MAKE SURE YOU "GET IT". IF NECESSARY, READ THE THREADS LINKED THROUGHOUT THIS POST. <<< THIS IS THE SINGLE MOST IMPORTANT PART OF THE PROCESS. IF YOU JUST READ THE FIRST FEW STEPS AND START FLASHING CRAP, YOU ARE GOING TO F SOMETHING UP. READ IT ALL, UNDERSTAND IT, THEN DO IT. I CAN'T EMPHASIZE THIS ENOUGH.
1.2 Backup. Back your stuff up. Back it all up - ALL of it. Understand that whatever you do not back up now, YOU WILL LOSE. This process is going to wipe your device clean. Anything you want to save, you need to back it up now.
1.2.1 Do not use Titanium Backup - for anything. It will F your stuff up. Which is unfortunate, because TB is a great app that is incredibly useful - just not this time. Apparently TB has issues when migrating form one version of Android to another (i.e. 4.x.x to 5.x.x). Sorry, but you gotta do it manually.
1.2.2 Copy your pics/vids to your PC
1.2.3 Use "SMS Backup& Restore" from the Play store
1.2.4 Let Google sync your contacts and calendar.
1.2.5 Any apps that store your data locally (not sync'd to their server) - manually find it (I like ES File Explorer) and copy it to your PC if you care about it.
All of that said - I found that wiping my device and migrating to Lollipop was a GREAT way to clean a bunch of useless crap I no longer needed off of my phone.
2. Rooting and Flashing STOCK KitKat (4.4.2) ROM (relevant thread - see post #2, under the "NB1 - KitKat 4.4.2 > Option 2" section.
Note: The reason you have to do this is because you must have rooted Lollipop on your device in order to flash custom Lollipop ROMS. If you just want stock, non-rooted Lollipop maybe you COULD just use Odin to flash Lollipop directly? But there is no way to get root on Lollipop directly - and you must be rooted if you want to wind up with a custom ROM. So you have to do this intermediate step of flashing and rooting a 4.4.x or higher OS. This version of NB1 is easiest because you can use Odin to flash a ROOTABLE ROM which makes the root process simple with Towelroot.
2.1 Download Odin v3.09 here. Place on PC.
2.2 Download ROOTABLE NB1 ROM here. Place on PC.
2.3 Download towelroot v3 here. Place on PC and copy to device (likely your SD card).
2.4 Use Odin to flash ROOTABLE NB1 ROM to your device. When the phone boots up, just speed through the "initial setup" screens, it doesn't matter since you're going to install a couple more ROMs before the finished product.
2.5 Go to settings>more>security and check "unknown apps", and uncheck "verify sources".
2.5 Navigate to towelroot v3, and install it.
2.6 Open towelroot and click the "make it rain" button.
Congrats, you are now rooted on KitKat NB1.
3. Upgrading to ROOTED STOCK OC3 (Lollipop) using "keep root" method (relevant thread)
As mentioned, this process takes you from ROOTED NB1 (KitKat, 4.4.x) to OC3 (Lollipop, 5.x.x). The only way to get rooted OC3 is to first get root in any 4.4.x version or higher and then upgrade to OC3 using the "keep root" method. There is (as of this writing) no way to root OC3 Lollipop directly. "keep root" reference thread - post #1
3.1 Download Flashfire app using below steps. (no direct link available).
3.1.1 Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
3.1.2 Sign up to receive the BETA versions from Play Here.
3.1.3 Use the link provided after sign-up to download the app. Note - the link was not immediately available for me, and apparently that is normal. (There was a link, but it told me something like "link not found" when I tried to access it at first.) I had to sign up, and then 30 minutes later I went back and had access to the Flashfire file.
3.2 Download I337_OC3_Stock_Rooted_ROM here.
3.3 Place ROM on SD card.
3.4 Use Flashfire to flash ROM (see "keep root" reference thread from above for specific details of using Flashfire)
Congrats, you are now on rooted (stock) Lollipop.
4. Install your CUSTOM Lollipop ROM
4.1 Download ROM and prepare Safestrap recovery
4.1.1 Download your chosen ROM. I chose Goldeneye v53 here. (I chose Goldeneye because after brief reading, Goldeneye seemed to be one of the more stable options, and stability is what I wanted when going through this the first time.) Place it on your SD card. Here are other options for Lollipop custom ROMs on AT&T GS4. If you happen to wander into the development section and see all the shiny, new, intriguing ROMs floating around, keep in mind that most of them won't work for the AT&T GS4. Any custom ROM on this device must be based on Touchwiz and setup to be compatible with safestrap - only a handful meet those criteria.
4.1.2 Download Safestrap v3.75 here. Place it on your SD card. Do not install it at this point, Safestrap is currently not compatible with Lollipop - you are going to flash a different Kernel in Step 4.2 to work around this.
4.1.3 Download BusyBox from Play store
4.1.4 Install BusyBox on your device.
4.1.5 Install Safestap 3.75
4.1.6 Open Safestrap
4.1.7 I did not do this step because I did not start this process with any previous version of SS on my phone. But if you did have a previous SS recovery installed, use the Safestrap to "uninstall" the previous recovery version. It is my understanding that you can't install v3.75 on top of another version, you need to first remove the old version before installing the new version. The "uninstall" option is done from within the SS app, not the Android application manager - you are uninstalling the custom recovery, not the SS app.
4.1.8 "Install Recovery" (from within Safestrap). NOTE: this only INSTALLS safestrap, it does not boot you into safestrap recovery. There is no need to go into safestrap recovery yet. That's later.
4.2 Flash NC1 Kernel
As mentioned above, you need to flash the NC1 Kernel so that you can do your thing in Safestrap. But then you MUST remember to reflash the OC3 Kernel after using Safestrap to install the ROM, or else your phone will explode (probably).
4.2.1 Download NC1 flasher app from here. Place it on your SD card.
4.2.2 Download I337_stock_OC3_kernel_recovery_flashable from here. Place it on your SD card.
4.2.3 Download OC3 modules from here. Place it on your SD card.
4.2.4 Open NC1 flasher app and press "flash" (it's the only button)
4.2.5 Wait for completion and press reboot. NOW you will get automatically rebooted into safestrap recovery.
4.3 Install your custom ROM!!!
(note: all the below is done in safestrap recovery)
4.3.1 Go to "Wipe" and perform factory reset (will wipe system data, cache, and dalvik)
4.3.2 Flash your ROM. For Goldeneye ROM, it uses the AROMA installer. Choose the options that you like, but make sure to READ THEM ALL BEFORE SELECTING ANYTHING - IF ONE OF THE OPTIONS MENTIONS AT&T/SAFESTRAP, YOU MUST CHOOSE THAT OPTION. HELLFIRE, BRIMSTONE, AND ETERNAL DAMNATION WILL AWAIT YOU IF YOU CHOOSE ANOTHER OPTION.
4.3.3 At the end of the ROM installation, uncheck the "reboot now" option and continue - it will send you back to safestrap.
4.3.4 From within SS, install the OC3 modules from your SD card.
4.3.5 From within SS, install the I337_Stock_OC3_kernel_recovery_flashable from your SD card.
4.3.6 Reboot > system
4.3.7 Keep hitting "continue" when you get the safestrap recovery screen. This is a symptom of Lollipop not being compatible with Safestrap. Hit "continue" repeatedly (like 4 or 5 times) and eventually you will get into your ROM.
4.3.8 (Optional) Install safestrap.apk (that you d/l to your SD card) to your phone, and then use it to UNINSTALL recovery. This will avoid the above step 4.3.7 happening every time you reboot your phone.
Congrats, you now have a custom Lollipop ROM running on your device.
Note: SuperSU is finicky on Lollipop. See this thread for how to manipulate SuperSU to get your root apps working.
.
.
.
.
See? EASY.
Safestrap never works. I always select recovery when its powering on and it just powers up normally and takes me to my lockscreen. I installed safestrap using the apk, im already rooted on stock lollipop.
Israelsalinas19 said:
Safestrap never works. I always select recovery when its powering on and it just powers up normally and takes me to my lockscreen. I installed safestrap using the apk, im already rooted on stock lollipop.
Click to expand...
Click to collapse
You probably missed the step where he said to flash the nc1 kernel.
Yup, safestrap is known to be not fully compatible with OC3, that's why you have to flash the NC1 kernel in order to be able to use SS to flash your custom ROM. Don't forget to flash back to the OC3 kernel though, as stated in step 4.3.4.
Bootloops everytime. Flash kernels and modules after rom..reboot, samsumg custom screen then safestrap then 10 seconds later back to custom screen. After flashing kernels and modules I'm still able to get into recovery, nc1 should be gone in order for ss to work. I'm so sick of odin... :what:
Sent from my sghi337 on oc3
robot_head said:
Bootloops everytime. Flash kernels and modules after rom..reboot, samsumg custom screen then safestrap then 10 seconds later back to custom screen. After flashing kernels and modules I'm still able to get into recovery, nc1 should be gone in order for ss to work. I'm so sick of odin... :what:
Sent from my sghi337 on oc3
Click to expand...
Click to collapse
So you got all the way to step 4.3.6 successfully, it sounds like? And now you are just getting the Safestrap screen - where you can either "continue" or "recovery"? How many times did you hit "continue" and go through the "bootloop" (if any)?
After step 4.3.6, when you boot into your custom ROM, you will have the Safestrap screen pop up several times (like, at least four or five) - keep hitting "continue" and you will eventually get into the ROM. This is another symptom of Lollipop not being fully compatible with Safestrap.
I did not put that detail in the writeup. Very sorry it caused you issues. I am updating with that info now.
I must of not been patient enough, with so many failed rom installs with this locked bootloader i just odin'd back to nb1 to get to oc3... Any custom recovery would be such a relief as ss acts wonkey in lollipop, and flashfire isn't accessible if you're caught in a bootloop or the radical "att unauthorized software". Thanks for the help
Sent from my sghi337 on oc3
Update:
So once again I follow the instructions completely to the t
After I flash the ROM and the kernel and the modules and I reboot I get the Samsung custom screen then to safe strap then 20 seconds reboots to Samsung Galaxy s4 screen then safestrap then again to the Samsung Galaxy s4 screen with reboot to recovery again and this time it puts me into stock recovery no safestrap after rebooting system each time from recovery. It does the same thing and eventually i end up at the system recovery... I've tried this about 11 times, with no success to boot into the ROM
Sent from my sghi337 on oc3
robot_head said:
Update:
So once again I follow the instructions completely to the t
After I flash the ROM and the kernel and the modules and I reboot I get the Samsung custom screen then to safe strap then 20 seconds reboots to Samsung Galaxy s4 screen then safestrap then again to the Samsung Galaxy s4 screen with reboot to recovery again and this time it puts me into stock recovery no safestrap after rebooting system each time from recovery. It does the same thing and eventually i end up at the system recovery... I've tried this about 11 times, with no success to boot into the ROM
Sent from my sghi337 on oc3
Click to expand...
Click to collapse
Did you try wiping data/cache in the stock system recovery?
Yes wiped with system recovery and safestrap. This is an issue of flashing the oc3 kernels and modules with safestrap. I think.....
sent from my sghi337 on oc3
Read through your tutorial, very nice. ?The only thing I noticed is you flash the kernel before the modules. I think flashing the kernel should be the very last step before rebooting, I'm not sure it matters, but it might. Also when the phone is booting I never touch any buttons (continue or recovery) just let it work through the screens on it's own.
Thanks, Cats_PJs - I will edit the OP to indicate flashing the modules before the kernel. I didn't see such a recommendation to flash one or the other first in my research, and I honestly can't remember now which I flashed first. But I will update the OP to recommend flashing the kernel last, just in case.
If I'm safestrap'd and rooted on a custom 4.x.x ROM, should I flash to rootable NB1 per step 2.2 then start here with step 3? Thanks for compiling all this, I chuckled at the 18 pages open comment. I know that pain.
What version are you running now? If you already have root on a KitKat 4.4.x or higher ROM, you should be able to go straight to rooted Lollipop using the muniz_ri keep root method method here. (see the very first line of the linked reference post.) So if you meet that criteria, you could start in Step 3.
If you're on a lower build, you'll want to just start with step 2 and flash NB1 via Odin. I believe that you will need to uninstall your current version of safestrap at some point to be able to install the required v3.75.
So I have an update I finally found that sometimes safestrap won't flash the kernel so you have to Odin it even if its downgrading the kernel or upgrading. I've been able to flash any lollipop rom since I've been doing the Odin method for the kernels you still have to safestrap your ROM though. In another thread it said to flash the OC3 partition which I didn't find necessary and when I did try to flash them Odin kept failing therefore it wasn't required you must also flash the module with safestrap right after you do your rom unless you have your modules in a tar file then just do it via Odin. So to go over it one more time... you have to be able to use safestrap so if you were on lollipop you must downgrade your kernel (via odin or nc1 flasher) then you can use safestrap to flash your ROM and flash your oc3 modules then reboot into download mode and use Odin to flash your oc3 kernel(sometimes it will fail,just try again, i hold my phone gently to comfort it through the process) and it boots up going through the safestrap screen at least 4 to 5 times.
Confirmed to work. ..
Goldeneye
Imperium
Car hd
I'll be testing all the compatible lollipop roms for my device it's exciting I can finally flash roms thank you for this tutorial for heading me in the right direction.
:thumbup::thumbup:
Sent from my GT-I9505 using XDA Free mobile app
robot_head said:
So I have an update
I finally found that sometimes safestrap won't flash the kernel so you have to Odin it even if its downgrading the kernel or upgrading.
I've been able to flash any lollipop rom since I've been doing the Odin method for the kernels - you still have to safestrap your ROM though.
In another thread it said to flash the OC3 partition which I didn't find necessary and when I did try to flash them Odin kept failing therefore it wasn't required
You must also flash the module with safestrap right after you do your rom unless you have your modules in a tar file then just do it via Odin.
So to go over it one more time... you have to be able to use safestrap so if you were on lollipop you must:
downgrade your kernel (via odin or nc1 flasher)
then you can use safestrap to flash your ROM and flash your oc3 modules
then reboot into download mode and use Odin to flash your oc3 kernel (sometimes it will fail, just try again, i hold my phone gently to comfort it through the process)
and it boots up going through the safestrap screen at least 4 to 5 times.
Confirmed to work. ..
Goldeneye
Imperium
Car hd
I'll be testing all the compatible lollipop roms for my device it's exciting I can finally flash roms thank you for this tutorial for heading me in the right direction.
:thumbup::thumbup:
Click to expand...
Click to collapse
robot_head, glad to hear you got the custom ROMs working on your device! I will add a note in the OP regarding your experience so it helps others that might have the same issue.
Sorry, but stupid question - you did only try to install flashable ".zip" files from within safestrap, and ".tar" files using Odin? Your word choice in your above post seems to indicate that you do recognize the difference. But I ask that because I did not realize the difference at one point, until I tried to load a .zip into Odin and encountered issues. (and also I wanted to make this distinction for any others reading this thread)
Question for you – when you are swapping between custom ROMs, are you backing up your system settings and apps/data, then restoring them to each ROM (or are you just “sampling” each ROM for limited time and not worrying about your apps)? Based on advice I read in several places, I didn’t use Titanium Backup when I upgraded from 4.x.x to 5.0.1, but I figured I could use it to swap between ROMs now that I’m on Lollipop. But I just wanted to be sure I could easily move between ROMs without requiring so much time manually downloading apps like I did for the upgrade.
@sac02 yes I do have backups of all of my firmware and roms and yes I am just sampling through all of the roms and any apps that I need backed up are on my SD card and Google Play backs up the ones from them automatically. Yes when I'm flashing with safestrap obviously it has to be a zip file and Odin has to be a tar. And if you search the site there are downloads for your kernel in a tar format I actually got half of the help I needed from this thread and the other half from the Goldeneye thread when someone was having an issue with safestrap they had to Odin everything.
Sent from my GT-I9505 using XDA Free mobile app
The instructions are good. You may have a bad download of kernel file. Note that the instructions call for the "reflashable kernel zip file" which can also be found on the NC1 flasher thread.
My main problem is i couldnt flash kernels with safestrap after the rom. Tried a different download, same thing. Either said unauthorized att software
Or firmware update failed, use kies
Or bootloop into system recovery.
Finally. ..just odining kernels solved my issue.
Sent from my GT-I9505 using XDA Free mobile app
I have root on a base NJ4 4.4.4 ROM. I couldn't get the google play edition working on my i337 (dimming sensor worked poorly during calls) so I went to something basic. I'll try your recommendation, thanks again.