Related
Sorry for the noob questions but I can't seem to find a specific answer to my problem.
I am trying to create a backup of my stock Touchwiz ICS 4.0.4 using Rom manager premium v.5.0.2.1 so that I can flash CM10 to my Verizon S3. I have flashed the "ClockworkMod Recovery".
Current Recovery: ClockworkMod 6.0.1.2
Latest Recovery: ClockworkMod 6.0.1.2
Now when I try to "Backup Current ROM" my phone boots into a menu. I was under the impression that it should begin creating a Nandroid backup when I did this. It boots into Android system recovery <3e>
Word for word this is what I get
Volume up/down to move highlight:
Power button to select.
Reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition apply update from cache
_______________________________________________
# MANUAL MODE #
--Applying Multi-CSC...
Applied the CSC-code : VZW
Succesfully applied multi-CSC
From there I didn't see an obvious Create backup type of option so I chose "Reboot system now" which then booted up normally. In Rom manger there is no file under Manage and Restore backups. Do I need to choose a different option in the boot menu. I could manually make a nandroid backup I think, but I'm not sure if it would work properly since I flashed the ClockworkMod Recovery.
Sorry, I am very new to this!
How did you flash your recovery? Was it through rom manager or through ez recovery?
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
Yeah you have the stock android recovery. (3e) Try using the "EZ-recovery for VZW Galaxy S3" app from the play store. I have always heard ROM manager can be kind of buggy.
JBO1018 said:
Yeah you have the stock android recovery. (3e) Try using the "EZ-recovery for VZW Galaxy S3" app from the play store. I have always heard ROM manager can be kind of buggy.
Click to expand...
Click to collapse
No, not at all, Rom manager works fine, but only if you flashed your recovery through it. If you used ez recovery, rom manager does not know that it has cwm recovery on it and will not operate correctly. Flash recovery through rom manager and it will work correctly. EZ is a foundation app intended to simplify recovery without rom manager. Not good if you know what your doing.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
annoyingduck said:
No, not at all, Rom manager works fine, but only if you flashed your recovery through it. If you used ez recovery, rom manager does not know that it has cwm recovery on it and will not operate correctly. Flash recovery through rom manager and it will work correctly. EZ is a foundation app intended to simplify recovery without rom manager. Not good if you know what your doing.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
Click to expand...
Click to collapse
He said he did use ROM manager to flash recovery and that it says he has CWM installed. Yet from his descripton when his phone reboots into recovery he is getting Android recovery 3e. (stock recovery) So something isnt working right. That's why I suggested ez recovery and mentioned ROM manager has been notoriously unreliable in the past for me and many other I know. It may work fine for this phone. I just, out of habit, tend to stay away from it.
JBO1018 said:
He said he did use ROM manager to flash recovery and that it says he has CWM installed. Yet from his descripton when his phone reboots into recovery he is getting Android recovery 3e. (stock recovery) So something isnt working right. That's why I suggested ez recovery and mentioned ROM manager has been notoriously unreliable in the past for me and many other I know. It may work fine for this phone. I just, out of habit, tend to stay away from it.
Click to expand...
Click to collapse
Good call!
I didn't see any mention of how he flashed his recovery, just assumed it was not through rom manager due to the issues he's having.
My experience with ez recovery made rom manager (an app I like alot) not work correctly. As soon as I re flashed through rom manager, all was well. Not knocking ez, just trying to get his rom manager app working for him.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
I am having the same problem. I flashed mine through Rom Manager also. It worked on the first reboot in recovery and has worked one other time in touch. Here's my thread. - http://forum.xda-developers.com/showthread.php?p=32795611#post32795611
Solutions?
If I install ez Recovery, how will that effect CWM?
I'm running the premium version of rom manager. Are you guys running the free version? I can't imagine why your having these issues, could it be related?
I originally used ez to install cwm 6.0.1.2, then used rom manager to flash the touch version of 6.0.1.2. Have not had these issues.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
annoyingduck said:
I'm running the premium version of rom manager. Are you guys running the free version? I can't imagine why your having these issues, could it be related?
I originally used ez to install cwm 6.0.1.2, then used rom manager to flash the touch version of 6.0.1.2. Have not had these issues.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
Click to expand...
Click to collapse
I got premium, I thought the same cause mine wont let me download roms either. It tells me to upgrade to the latest version.
Should we maybe uninstall and try a different install method, such as yours. Would there be any consequences?
I don't see any issues with that. To get touch through RM, there are 2 ways. One is in app purchase (don't do this, it's a one time, one use add on. Does not stay if you install a different recovery. Kind of a scam). The other is in RM you can link directly to cwm site and dl the apk for free. Just be sure you get the one for our phone, the site page is a little weird to navigate. Then you have it forever.
Sent from my VZW GS3 running Synergy/LeanKernel/Dark Horse Rises
This might be your problem, see if you gave the file mentioned in the last post and delete it.
http://forum.xda-developers.com/showthread.php?p=32346811
Sent from my S3 running Eclipse 2.1
kintwofan said:
This might be your problem, see if you gave the file mentioned in the last post and delete it.
http://forum.xda-developers.com/showthread.php?p=32346811
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
What file? Im still noob confused about all of this. S-P-E-L-L it out. Can I just go ahead and do ez now or do I need to do anything to RM
Thanks for your help, its greatly appreciated.
travis.bridges10 said:
What file? Im still noob confused about all of this. S-P-E-L-L it out. Can I just go ahead and do ez now or do I need to do anything to RM
Thanks for your help, its greatly appreciated.
Click to expand...
Click to collapse
Just try ez recovery first and see if it works, its in the play store. If it doesn't I'll try to find the exact path of the file. I'm not stock so its hard I'll have to search for it
Sent from my S3 running Eclipse 2.1
kintwofan said:
Just try ez recovery first and see if it works, its in the play store. If it doesn't I'll try to find the exact path of the file. I'm not stock so its hard I'll have to search for it
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
It worked the first time I rebooted from RM, then I tried to enter manual recovery and it went to android recovery, then I tried RM reboot to recovery and it went into android recovery. Do I need to back it up before I reboot? It seems like the reboot in recovery right after a flash works, but then looses it after reboot.
I still have the problem also of it not allowing me to download roms, says I need to upgrade to latest version.
travis.bridges10 said:
It worked the first time I rebooted from RM, then I tried to enter manual recovery and it went to android recovery, then I tried RM reboot to recovery and it went into android recovery. Do I need to back it up before I reboot? It seems like the reboot in recovery right after a flash works, but then looses it after reboot.
I still have the problem also of it not allowing me to download roms, says I need to upgrade to latest version.
Click to expand...
Click to collapse
Then that file needs deleted. I'll try to find it.
But the easiest fix would be to download whatever ROM you want directly from the forum. Use Ez recovery and in that first boot into recovery flash the ROM you downloaded following the instructions in the ROMs post.
Sent from my S3 running Eclipse 2.1
kintwofan said:
Then that file needs deleted. I'll try to find it.
But the easiest fix would be to download whatever ROM you want directly from the forum. Use Ez recovery and in that first boot into recovery flash the ROM you downloaded following the instructions in the ROMs post.
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
ok... Thats probably what ill do then. I have to do some more reading on flashing roms... I dont want anymore problems. I got three more questions for you since youve been so helpful.
1. Any idea why its not letting me get into the download ROMS in RM. Saying I need to upgrade to the latest version of RM
2. Im sure I could find the answer to this but Ill ask since I got you here. I just went through over the last few days adding a lot of customizations, like nova, widgets, widgetlocker, tasker, etc. When I do flash a new rom whats the most efficient way to transfer apps, settings, designs, etc
3. If I was to keep the stock ROM what happens with VZW OTA updates. Doesnt it mess things up. This last update has messed everything up for GS3's and I bet the next will have even more "restrictions"
Thanks again
travis.bridges10 said:
ok... Thats probably what ill do then. I have to do some more reading on flashing roms... I dont want anymore problems. I got two more questions for you since youve been so helpful.
1. Any idea why its not letting me get into the download ROMS in RM. Saying I need to upgrade to the latest version of RM
2. Im sure I could find the answer to this but Ill ask since I got you here. I just went through over the last few days adding a lot of customizations, like nova, widgets, widgetlocker, tasker, etc. When I do flash a new rom whats the most efficient way to transfer apps, settings, designs, etc
Thanks again
Click to expand...
Click to collapse
1. I don't use RM so can't be much help there.
2. I personally use titanium backup to back up and restore user apps. I don't recommend restoring system settings.
Sent from my S3 running Eclipse 2.1
---------- Post added at 09:02 PM ---------- Previous post was at 08:52 PM ----------
One either thing make sure you backup your imie...there's a guide in the development section.
Sent from my S3 running Eclipse 2.1
I figured it out earlier. When you do the first reboot the recovery menu gives you the option to disable stock recovery from flashing. Select it and it's been working fine since.
Sent from my SCH-I535 using xda app-developers app
travis.bridges10 said:
I figured it out earlier. When you do the first reboot the recovery menu gives you the option to disable stock recovery from flashing. Select it and it's been working fine since.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Good. I don't remember seeing that option, but I've been rooted for a while.
Sent from my S3 running Eclipse 2.1
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
iwearthebelt said:
So I just rooted my Verizon Galaxy S3 and unlocked the bootloader. I flashed Clockworkmod recovery using Rom Manager to update to the latest version. Made a nandroid, installed Titanium Backup, linked it to my Dropbox and uploaded. I downloaded the latest CM10 nightly to flash but the stock android recovery appeared instead of CWM. Found some info that I need to flash a clockwork compatible kernel first. The questions I have are: If I install the latest CM 10 nightly will it automatically install a clockwork compatable kernel? If not, where can I download it from? and if I do need to flash a kernel first can anyone give me detailed instructions how to do this as i'm relatively new to this stuff and don't want to brick my phone. Thanks, any info would help.
Click to expand...
Click to collapse
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
darkhawk3383 said:
Did you unlock your bootloader? for a custom recovery to stick you need to unlock your bootloader. Follow this guide
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I did, had it unlocked and rooted. I guess there was some sort of issue with Rom Manager on the S3. I use it on my Galaxy Nexus and have no issues. I ended up abandoning what I was doing, uninstalling Rom Manager and going a different route. I have no prior experience with Odin but figured out how to install CWM . Downloaded I535vrblk1, flashed CWM, unlocked & rooted again. . Thanks anyway for the reply.
You can reinstall ROM Manager. It is something to do with some of the newer OTA's and the leaks. I have read a few posts in the forums about this in the GS3 and I really can't remember the fix but your recovery not sticking had nothing to do with ROM Manager. I think the fix was when you rebooted to recovery to flash a kernel right away, whether it be KT747, LK, or any of the other. Now that I typed this I'm about 99% sure that was the fix. Like I said above though, it has nothing to do.with ROM Manager, so if you're like me and find a lot of the tools in it handy you should be able to reinstall it. If you have a problem again just flash a kernel.
Sent from one of the many Anthropomorphic Personalities on the Disc
Good morning...
Right now, my phone (Galaxy S III on Verizon) will not boot past the "Galaxy S III" logo. Odin will not flash a stock Jelly Bean ROM from StockRoms.net. It gets stuck on the first .img, boot.img. I am downloading a new stock ROM right now and will try a full wipe.
Being silly and ambitious, I do not have a nandroid before it wouldn't boot. On Monday (two days ago) I rooted it. I flashed the VRALEC boot chain, rebooted, flashed ClockworkMod recovery, and installed the SuperSU bootloader and root patch through recovery. I rebooted, allowing CWM to disable the automatic re-flashing of the recovery. With my newly rooted phone, I jumped at trying to install Google Wallet. I went with the route of using Wallet Installer as found on the app store. And, being silly, I checked all three OS options (JB, ICS, and one other). After authorizing the superuser request, my phone almost immediately shut off. I think I made a nandroid through CWM after that, but not one that would run.
I thought it was going to be just build.prop having issues, so I went on a wild quest trying to find a working one online and get it on the device. I worked it into the updater script of my SuperSU patch. Nonetheless, nothing there fixed it. I've tried a bunch of things, including (get this) extracting the stock system.img.ext4 image, mounting it, tarring the device, creating an MD5 for it, and wrapping it up like a nandroid to "restore" with CWM.
I'm thinking I'm going to try and wipe the entire device, maybe leave /recovery, and flash a new I-535 ROM with Odin, see if that works. I don't know if it will. Any advice?
My flash counter is at about 5 after many attempts to get back to something that will boot, so warranty is not an option. Not that they've ever been a whole lot of help anyways.
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Sent from my SCH-I535 using Tapatalk 2
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Sent from my SCH-I535 using xda app-developers app
joaquinla1 said:
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Click to expand...
Click to collapse
My phone has CWM recovery on it, but I don't see any reason CWM's factory reset and cache wipe would be any different. I'll give it a shot.
mentose457 said:
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Click to expand...
Click to collapse
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Thanks for all your help. The ROM I'm going to try and flash now is the official stock from stockroms.net. I can't post the link as I'm new but it's I535BLK_nowipe.zip. I'll keep this updated.
sworld said:
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Click to expand...
Click to collapse
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Sent from my SCH-I535 using Tapatalk 2
mentose457 said:
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Click to expand...
Click to collapse
That makes more sense.
UPDATE: I "factory reset" the data partition and formatted /system and /cache through ClockworkMod. Turned it off, flashed VRALEC through Odin, rebooted, flashed the stock ROM, and then CWM. I'm restoring my nandroid of /data right now, and I'm awaiting an OTA firmware update to bring it up to the latest VZW JB. Then I'll root.. finally.
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
z06mike said:
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
Click to expand...
Click to collapse
Really? I've only odined once on the s3 and didn't have to wipe. On the fascinate and an older version of Odin after the flash before it booted it would automatically wipe.
Sent from my SCH-I535 using Tapatalk 2
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So, the phone is functioning now. Of course, I am running a slightly older version and once I connect to a solid Wi-Fi network I'll request the newest update again.
However, I did already try to download the software update from Verizon, and it seemed to work fine. It rebooted into recovery and CWM seemed to handle it okay, although it claimed the signature was bad. It installed though, rebooted, and updated some app databases. And then, it said the update failed with "Code 401."
Right now I'm not too worried. Hopefully I can apply the update properly soon. It is worth noting that simply using CWM "advanced restore" on only the /data partition, without exactly matching the ROM build, has seemed to leave it hanging at the "4G LTE" logo.
Thanks for all of your help!
The phone will not install a Verizon update with a custom recovery installed.
ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Make sure u cwm is the most recent
Sent from my SCH-I535 using XDA Premium 4 mobile app
Mylt1 said:
ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Click to expand...
Click to collapse
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
yes, CWM was updated just before flashing. i installed the recommended modem for the rom i was installing. not sure why it was stuck at the logo on 4.3 when i flashed a 4.1.1 rom and it booted right up just fine.
resolved. thanks guys.
Mylt1 said:
resolved. thanks guys.
Click to expand...
Click to collapse
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
CenFlo said:
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
Click to expand...
Click to collapse
i used the Philz touch CWM found here, http://forum.xda-developers.com/showthread.php?t=2201860 worked like a charm.
jonny30bass said:
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
Click to expand...
Click to collapse
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
CenFlo said:
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
Click to expand...
Click to collapse
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
ShapesBlue said:
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I thought I updated to the latest Phliz and I do believe that's the error I was getting when I tried to load the ROM.
I'll check again Monday.
I appreciate the info.
The issue was with Philz.
I upgraded to the latest TWRP and loaded the new ROM fine.
Hi all,
This is an app by which you can flash the NC1 stock KK kernel(while on lollipop OC3) that is Safestrap friendly. Then you can enter to SS recovery and flash whatever you need onto your LP ROM. As we all know that SS won't work after flashing a lollipop ROM using muniz_ri method, unless you Odin a KK kernel. All you have to do is download the app and open it up then hit " flash", wait for it to finish then hit "tap to reboot" and it will take you directly to SS recovery. Then you can flash whatever MODs or addons you wish without having to be stuck or having to use Odin to flash the KK kernel. We are not always home by the PC to use Odin. After done flashing your files MAKE SURE TO FLASH THE I337_OC3_Stock_KERNEL_Recovery-Flashable before you reboot in order for your phone to boot up.
(NOTE: OC4 recovery flashable kernel is located here for those who need it. Thanks to Carl again)
-I did NOT make this app and I take absolutely no credit for it. All thanks go to @benwaffle the original creator of this app for our AT&T Note 3 and @carl1961 for remaking it for the S4.
If you have any questions, please let me know.
-Please note that the purpose of this thread is only to help users. No donations needed. A "thank you" is more than enough
Hope this will help.
WARNING: it may or may not work for some of you. It DID work for me with no problem, so use it at your own risk.
K-alz said:
Hi all,
This is an app by which you can flash the NC1 stock KK kernel(while on lollipop OC3) that is Safestrap friendly. Then you can enter to SS recovery and flash whatever you need onto your LP ROM. As we all know that SS won't work after flashing a lollipop ROM using muniz_ri method, unless you Odin a KK kernel. All you have to do is download the app and open it up then hit " flash", wait for it to finish then hit "tap to reboot" and it will take you directly to SS recovery. Then you can flash whatever MODs or addons you wish without having to be stuck or having to use Odin to flash the KK kernel. We are not always home by the PC to use Odin. After done flashing your files MAKE SURE TO FLASH THE I337_OC3_Stock_KERNEL_Recovery-Flashable before you reboot in order for your phone to boot up.
-I did NOT make this app and I take absolutely no credit for it. All thanks go to @benwaffle the original creator of this app for our AT&T Note 3 and @carl1961 for remaking it for the S4.
If you have any questions, please let me know.
-Please note that the purpose of this thread is only to help users. No donations needed. A "thank you" is more than enough
Hope this will help.
WARNING: it may or may not work for some of you. It DID work for me with no problem, so use it at your own risk.
Click to expand...
Click to collapse
Sound Fantastic! Lets see if I got it straight: 1. Using the Safestrap/Odin method get into LP. 2. Then install the NC1 app to get SS. 3. Flash the file you want then Flash I337 OCS Stock Kernel and the reboot.
Sound right?
Source is here https://github.com/benwaffle/AT-T-Note-3-Kernel-Flasher
rfb813 said:
Sound Fantastic! Lets see if I got it straight: 1. Using the Safestrap/Odin method get into LP. 2. Then install the NC1 app to get SS. 3. Flash the file you want then Flash I337 OCS Stock Kernel and the reboot.
Sound right?
Click to expand...
Click to collapse
Yup, you got it. I was actually worried that I didn't make sense. LOL
From my Allianced S5!
benwaffle said:
Source is here https://github.com/benwaffle/AT-T-Note-3-Kernel-Flasher
Click to expand...
Click to collapse
Thank you so much, man.
From my Allianced S5!
Used this to make a backup in safestrap just to test it out. Worked great, so I plan on trying to flash the Imperium ROM when I gat a chance. This will be very useful since Flahfire doesn't work with aroma yet. Thanks for this.
Cats_PJs said:
Used this to make a backup in safestrap just to test it out. Worked great, so I plan on trying to flash the Imperium ROM when I gat a chance. This will be very useful since Flahfire doesn't work with aroma yet. Thanks for this.
Click to expand...
Click to collapse
Thank you for confirming, bro. I'm glad it's helping. And what ROM are you talking about? Can't find it in the development section. I want to flash it, too!
K-alz said:
Thank you for confirming, bro. I'm glad it's helping. And what ROM are you talking about? Can't find it in the development section. I want to flash it, too!
Click to expand...
Click to collapse
It's in the 9505 forum. I know that those ROMs worked on our phones on 4.4.2 so I thought they may still work, but I'm not guaranteeing anything.
Cats_PJs said:
It's in the 9505 forum. I know that those ROMs worked on our phones on 4.4.2 so I thought they may still work, but I'm not guaranteeing anything.
Click to expand...
Click to collapse
Well, I think you should ask in the thread first. Just in case the ROM comes with any other kernel then give it a try.
from my lollipoped Alianced N3!
K-alz said:
Well, I think you should ask in the thread first. Just in case the ROM comes with any other kernel then give it a try.
from my lollipoped Alianced N3!
Click to expand...
Click to collapse
I just gave it a shot. It did boot but kept popping up the message " unfortunately system ui has stopped". Not sure if there's a way to solve this, but for now I just restored my backup from safestrap, so at least I can confirm that part.
Cats_PJs said:
I just gave it a shot. It did boot but kept popping up the message " unfortunately system ui has stopped". Not sure if there's a way to solve this, but for now I just restored my backup from safestrap, so at least I can confirm that part.
Click to expand...
Click to collapse
That's an easy one. If you can sideload nova launcher, I think that message won't pop up. Unless, it's constant.
Could you give me the link for the thread?
Cats_PJs said:
I just gave it a shot. It did boot but kept popping up the message " unfortunately system ui has stopped". Not sure if there's a way to solve this, but for now I just restored my backup from safestrap, so at least I can confirm that part.
Click to expand...
Click to collapse
Or maybe you did a dirty flash? Did you wipe system along with caches and internal in safestrap?
K-alz said:
Or maybe you did a dirty flash? Did you wipe system along with caches and internal in safestrap?
Click to expand...
Click to collapse
I always clean flash, here's the link. Good luck, I would have looked into it more but I need my phone for tomorrow and it's time to call it a day .http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-imperium-ll-v1-0-t3046889
Cats_PJs said:
I always clean flash, here's the link. Good luck, I would have looked into it more but I need my phone for tomorrow and it's time to call it a day .http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-imperium-ll-v1-0-t3046889
Click to expand...
Click to collapse
Thanks. I won't flash it now. I'll wait for tomorrow as well. ?
from my lollipoped Alianced N3!
I updated to OC3 via the safestrap method muniz_ri posted. I completely debloated my phone and decided to play a bit. Thinking hey I need a backup! So I downloaded this NC1 flasher granted it root access and let it flash the NC1 kernel then hit the reboot button. Safestrap is alive. I made a backup of my now debloated rooted OC3 S4. Just to check I then in safestrap restored the backup I just made and flashed the recovery flashable OC3 kernel. While still in safestrap I wiped dalvik and cache then rebooted the phone. It went through the usual barrage of safestrap screens until the Ole Sammy logo finally showed up. When the phone booted I was greeted with nothing but force closes. No home screen nothing. Everything forced closed. Thinking the backup failed I first decided to boot stock recovery and delete the cache there. Upon reboot a bunch of safestrap screens then it booted up as usual. No force closes! The backup flashed fine and now have a slim working fall back of OC3. Thanks to everyone who has contributed here on xda. Without these forums my I337 would be att junk lol.
I flashed NC1 apk after installing safestrap and busybox on my Rom which had been flashed with The safestrap method. Flash worked great and then I backed up the Rom. I then flashed another Rom which I decided against and rebooted into safestrap and restored my original Rom. Perfect! I then tried to reboot into Safestrap with the NC1 apk and nothing happened it just rebooted into the Rom. I removed and reinstalled Safestrap and the NC1 apk and tired again. Nothing. Any Ideas?
Did you reinstall recovery thru safestrap too?
macasus76 said:
I updated to OC3 via the safestrap method muniz_ri posted. I completely debloated my phone and decided to play a bit. Thinking hey I need a backup! So I downloaded this NC1 flasher granted it root access and let it flash the NC1 kernel then hit the reboot button. Safestrap is alive. I made a backup of my now debloated rooted OC3 S4. Just to check I then in safestrap restored the backup I just made and flashed the recovery flashable OC3 kernel. While still in safestrap I wiped dalvik and cache then rebooted the phone. It went through the usual barrage of safestrap screens until the Ole Sammy logo finally showed up. When the phone booted I was greeted with nothing but force closes. No home screen nothing. Everything forced closed. Thinking the backup failed I first decided to boot stock recovery and delete the cache there. Upon reboot a bunch of safestrap screens then it booted up as usual. No force closes! The backup flashed fine and now have a slim working fall back of OC3. Thanks to everyone who has contributed here on xda. Without these forums my I337 would be att junk lol.
Click to expand...
Click to collapse
I'm thinking the force closes happened because you restored your back up without a clean wipe, but that's just a guess, though.
rfb813 said:
I flashed NC1 apk after installing safestrap and busybox on my Rom which had been flashed with The safestrap method. Flash worked great and then I backed up the Rom. I then flashed another Rom which I decided against and rebooted into safestrap and restored my original Rom. Perfect! I then tried to reboot into Safestrap with the NC1 apk and nothing happened it just rebooted into the Rom. I removed and reinstalled Safestrap and the NC1 apk and tired again. Nothing. Any Ideas?
Click to expand...
Click to collapse
First of all, if you have used the safestrap method to upgrade to OC3, then you don't need to reinstall SS and busybox again. They're both there already. It's just that SS isn't compatible with the OC3 kernel and that's why it doesn't show up and only shows up when you flash NC1 back (because it works with NC1).
Secondly, I remember that on KitKat, when having trouble with SS installing it was recommended to download SElinux changer and change the SElinux to permissive instead of enforcing. I don't know if this method would work with Lollipop and never actually tried it. Do you wanna try that and see? Do it on your own risk, though. Lol
If not then just install SS again and uninstall recovery and reinstall it again and try.
Let me see if i got it right
1. Extract the .zip file and intall the app
2. Flash the nc1 kernel using the app
3. Boot to ss
4. Install the rom
5. Flash the oc3 kernel using ss
Is that right?
7mada said:
Let me see if i got it right
1. Extract the .zip file and intall the app
2. Flash the nc1 kernel using the app
3. Boot to ss
4. Install the rom
5. Flash the oc3 kernel using ss
Is that right?
Click to expand...
Click to collapse
Yes. But if you're already on a KK ROM, you don't need it. This is only for those who are on a Lollipop ROM and want to reboot into SS.
Also, if you want to flash a ROM, like you said, make sure to wipe your phone first so you don't a ton of FCs.