VERIZON SAMSUNG GALAXY NOTE 2 (T0LTE)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.00-B01 (ND7/KK)
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.1.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (3-4 on the S3 due to partition size and internal space) for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
[NEW FOR v4.00+ KK Safestrap] Requirement: Uninstall old Safestrap application.
[NEW FOR v3.75+ KK Safestrap] Requirement: busybox. Grab "Busybox" from the Play Store and run the installer.
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
INSTALL VIDEO by DMX: https://www.youtube.com/watch?v=_RZI...e_gdata_player
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again. (DEBUGGING THIS AS I GET TIME)
- Busybox is now required for the Safestrap APK to work correctly
DOWNLOADS:
CONFIRM THAT YOU ARE USING A VERIZON WIRELESS SAMSUNG GALAXY NOTE 2 (T0LTE) [KITKAT:ND7]
LATEST FILE: Safestrap-T0LTE-4.00-B01.apk
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode , DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery. If you are considering a donation, then please have a look at the Team WIN website: http://teamw.in/project/twrp2
@urphonesux for testing
CHANGES:
4.00-B01
[2015-11-22] Synced with latest TWRP commits.
[2015-11-22] Remove read-only system.
[2015-08-13] Update TWRP recovery to 2.8.7.0 .
[2015-08-13] Materialize Safestrap apk.
Safestrap Recovery theme (Stock TWRP)
How to...
The theme zips are not flashable. First installation has to be done manually:
- Download the theme and rename it to "ui.zip".
- On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
- Copy ui.zip to theme folder.
- Restart to recovery.
Safestrap Stock TWRP theme v4.00 B01.zip
1st!! Everything works fine. Multiple rom slots, backup/restore etc.
Thanks for this Mo!
on ND7 OTA. rooted via ghettoroot. Installed a previous version of safestrap: Safestrap-T0LTE-3.72-B02
it worked but didnt work with rom slots. I uninstalled the previous recovery and then uninstalled safestrap. Then installed this new one. Keeps not installing the safestrap recovery. Any ideas?
Tried doing a system wipe then installed clean 4.00 safestrap. no work..
Tried then system wipe and doing kingroot instead of ghettoroot. same result
albert001 said:
on ND7 OTA. rooted via ghettoroot. Installed a previous version of safestrap: Safestrap-T0LTE-3.72-B02
it worked but didnt work with rom slots. I uninstalled the previous recovery and then uninstalled safestrap. Then installed this new one. Keeps not installing the safestrap recovery. Any ideas?
Tried doing a system wipe then installed clean 4.00 safestrap. no work..
Tried then system wipe and doing kingroot instead of ghettoroot. same result
Click to expand...
Click to collapse
Does busybox installed! From the app too.
What's updated over the previous versions?
Upgrade from 3.72 on Verizon Note 2
I am using 3.72 and wonder if I should upgrade to the latest version. It must be completely removed and not updated as per OP instructions under content?
Thanks
adobrakic said:
What's updated over the previous versions?
Click to expand...
Click to collapse
TWRP is now 2.8.7.0 and its support kitkat..
NB2A said:
I am using 3.72 and wonder if I should upgrade to the latest version. It must be completely removed and not updated as per OP instructions under content?
Thanks
Click to expand...
Click to collapse
yes comlplete remove the old apk as mine has different package name
Hi,in this version works the option restore?
Piombo71 said:
Hi,in this version works the option restore?
Click to expand...
Click to collapse
As reprted by urphonesux its working as it should.
hello sir i try ur recovery mood Everything works fine and install new 5.01 rom in my i605 4.4.2 but samsung logo restart prob. in my phone rom and google apps successfully install in my phone then reboot but my phone not on. :crying::crying:
plzz help me..
djrajiv said:
hello sir i try ur recovery mood Everything works fine and install new 5.01 rom in my i605 4.4.2 but samsung logo restart prob. in my phone rom and google apps successfully install in my phone then reboot but my phone not on. :crying::crying:
plzz help me..
Click to expand...
Click to collapse
Hi,then if it is as in the previous version,this recovery can flash only TW Rom and not CM Rom,because black screen upon reboot.
djrajiv said:
hello sir i try ur recovery mood Everything works fine and install new 5.01 rom in my i605 4.4.2 but samsung logo restart prob. in my phone rom and google apps successfully install in my phone then reboot but my phone not on. :crying::crying:
plzz help me..
Click to expand...
Click to collapse
If you are locked bootloader then AOSP ROMs not for you.
The recovery wont flash any kernel and lack of kernel wont boot the ROM.
mohammad.afaneh said:
If you are locked bootloader then AOSP ROMs not for you.
The recovery wont flash any kernel and lack of kernel wont boot the ROM.
Click to expand...
Click to collapse
i try this 3 roms in my note 2 i605. 4.4.2nd7.
[ROM] [5.1.1_r18] [OFFICIAL] [Layers] XenonHD i605 - Note 2
[ROM] [6.0.1r10] [MULTI-WINDOW][VRToxin][i605] [01/08/2016]
[ROM][5.1/6.0][CM12.1/13][SABER][20160201] Unofficial Build - i605
rom and google apps successfully install but my phone black screen upon reboot..
djrajiv said:
i try this 3 roms in my note 2 i605. 4.4.2nd7.
[ROM] [5.1.1_r18] [OFFICIAL] [Layers] XenonHD i605 - Note 2
[ROM] [6.0.1r10] [MULTI-WINDOW][VRToxin][i605] [01/08/2016]
[ROM][5.1/6.0][CM12.1/13][SABER][20160201] Unofficial Build - i605
rom and google apps successfully install but my phone black screen upon reboot..
Click to expand...
Click to collapse
those ROMs are AOSP and you cant flash over locked bootloader device.
mohammad.afaneh said:
those ROMs are AOSP and you cant flash over locked bootloader device.
Click to expand...
Click to collapse
how to unlock my note 2 bootloader 4.4.2 ND7 Sir ???
djrajiv said:
how to unlock my note 2 bootloader 4.4.2 ND7 Sir ???
Click to expand...
Click to collapse
http://www.mobiletechvideos.com/samsung-galaxy-note-2-bootloader-sboot-downgrade-service/
The only way to unlock the bootloader at this point is to have this done. They will downgrade your Note 2 to 4.1.2 which can be unlocked. Sorry it is what it is.
i follow everything but when i install ss from the app, it doesnt give me an option to reboot recovery , im on 4.4.2
cubajean10 said:
i follow everything but when i install ss from the app, it doesnt give me an option to reboot recovery , im on 4.4.2
Click to expand...
Click to collapse
You installed Busybox?
Related
I've been following instructions to install Android 4.4 KitKat on Galaxy Mega 6.3 via Cyanogenmod 11.
My device has been rooted for some time, but I have never before installed any ROMs.
I have successfully (it seems) installed Clockworkmod via Odin, yet when I boot into Custom recovery mod, there is no "backup and restore" option, and indeed I seem to be in "Android system recovery", not CWM recovery (see screenshot).
I know that I can't install Cyanogenmod without Clockworkmod on board, so I'm nervous to proceed. Can anyone please advise?
AidanBell said:
I've been following instructions to install Android 4.4 KitKat on Galaxy Mega 6.3 via Cyanogenmod 11.
My device has been rooted for some time, but I have never before installed any ROMs.
I have successfully (it seems) installed Clockworkmod via Odin, yet when I boot into Custom recovery mod, there is no "backup and restore" option, and indeed I seem to be in "Android system recovery", not CWM recovery (see screenshot).
I know that I can't install Cyanogenmod without Clockworkmod on board, so I'm nervous to proceed. Can anyone please advise?
Click to expand...
Click to collapse
That looks like the standard recovery, not clockwork mod, what model of mega do you have?
You have to reboot to recovery first after flashing custom recovery. That's because the stock ROM checks if the recovery is changed and overwrites it with the stock recovery again.
Rebooting to recovery first will solve the issue.
Sent from my GT-I9205 using Tapatalk
Thanks for responding guys.
Jzsidebott: It's a Mega 6.3, GT-I9205, in England.
Silesh.Nair: I've installed "ROM Manager" and used "Reboot into recovery", but I get to the same place as before; "Android system recovery <3e>", exactly as the screenshot in my first post.
So I used Odin again, and again apparently successfully installed "GT-I9205-recovery.tar", but still I can only get standard recovery.
Could I ask you guys if you would recommend CyanogenMod Installer?
http://beta.download.cyanogenmod.org/install
I'm a newbie at this, so if this method is considered safe I'd be happy to go down that route. Any advice? Cheers.
Don't use ROM manager. Download the cwm tar file and use Odin to flash. Remember to untick auto reboot in Odin and then reboot to recovery first. It will work for sure. Don't flash anything if you are running Knox enabled firmware else you'll screw up your phone.
Sent from my GT-I9205 using Tapatalk
Thanks. As I said I did use Odin to flash. I just installed ROM Manager afterwards to try to find out whether the Odin Flash had worked. I am a newbie at this and to be honest I have no idea what Knox enabled firmware is or whether I'm running it. I think that for safety's sake I'd best drop the whole thing and not risk bricking my phone, but thank you all for the help all the same.
I have 2 questions. Does Xposed Framework work with LG P76921d? And 2, is it possible to install a recovery and back up your rom without an unlocked bootloader?
V1vatr0n said:
I have 2 questions. Does Xposed Framework work with LG P76921d? And 2, is it possible to install a recovery and back up your rom without an unlocked bootloader?
Click to expand...
Click to collapse
Xposed Framework works with P76920h. Using version 2.5 of the app now. (app_process:50, XposedBridge.jar:46)
GravityBox does not work. It will fill up ALL AVAILABLE internal space with an error log. Our ROM is unsupported anyway, so let it go.
Master Key multi-fix [2.0] DOES WORK.
(An aside: when did you update to 21d?)
It updated last year around august
Also, do you know any modules that might work? If not, there would be no point in installing xposed
V1vatr0n said:
It updated last year around august
Also, do you know any modules that might work? If not, there would be no point in installing xposed
Click to expand...
Click to collapse
I have the LGMS769 which is no different than the P769 and I have xposed framework, gravity box, battery themer, youtube adaway and have used multi window, xblast tools and some others without any issues.
Yes you can install cwm recovery for locked bootloaders with the L9 recovery installer from here -
http://forum.xda-developers.com/showthread.php?t=2095825
Download SuperSU and BusyBox by stericson from the play store. Install SuperSU then install BusyBox, open BusyBox and chose to install BusyBox v1.21.0 to system/xbin. Then install the L9 recovery installer, open the app and click on install ICS/JB stable recovery, once its installed it will tell you to reboot and when the device reboots the front keys will start flasing,(this means you have recovery access) press and hold down the volume (-) down button while the lights are flashing and the device will boot into the recovery. Once in recovery, immediately at this point make sure you perform a nandroid backup before exiting recovery.... this is just in case you get the "Encrypting Reset Phone" error when you exit recovery and boot to android OS, sometimes this will happen because of a BusyBox issue and rebooting back into recovery and flashing your nandroid backup will fix it.
Anyway that's it, you now have cwm recovery installed.
With the cwm for locked bootloaders you can perform and restore backups, flash zips and etc... But you cannot flash custom ROMs with it.
I'd recommend to now install xposed framework and whatever other modules that you want now that you have a nandroid backup. If you want to try a module then try it and see if it works... If it causes problems just uninstall it, if you still have problems or it causes a boot loop, boot to recovery and restore your nandroid backup and your fine.
xdrc45 said:
I have the LGMS769 which is no different than the P769 and I have xposed framework, gravity box, battery themer, youtube adaway and have used multi window, xblast tools and some others without any issues.
Yes you can install cwm recovery for locked bootloaders with the L9 recovery installer from here -
http://forum.xda-developers.com/showthread.php?t=2095825
Download SuperSU and BusyBox by stericson from the play store. Install SuperSU then install BusyBox, open BusyBox and chose to install BusyBox v1.21.0 to system/xbin. Then install the L9 recovery installer, open the app and click on install ICS/JB stable recovery, once its installed it will tell you to reboot and when the device reboots the front keys will start flasing,(this means you have recovery access) press and hold down the volume (-) down button while the lights are flashing and the device will boot into the recovery. Once in recovery, immediately at this point make sure you perform a nandroid backup before exiting recovery.... this is just in case you get the "Encrypting Reset Phone" error when you exit recovery and boot to android OS, sometimes this will happen because of a BusyBox issue and rebooting back into recovery and flashing your nandroid backup will fix it.
Anyway that's it, you now have cwm recovery installed.
With the cwm for locked bootloaders you can perform and restore backups, flash zips and etc... But you cannot flash custom ROMs with it.
I'd recommend to now install xposed framework and whatever other modules that you want now that you have a nandroid backup. If you want to try a module then try it and see if it works... If it causes problems just uninstall it, if you still have problems or it causes a boot loop, boot to recovery and restore your nandroid backup and your fine.
Click to expand...
Click to collapse
How much memory does this need? I tried to back up my phone but it said there was not enough room
V1vatr0n said:
How much memory does this need? I tried to back up my phone but it said there was not enough room
Click to expand...
Click to collapse
Really depends on what you have on the device as far as apps, user data and so forth, but can be around 1-2 gb.
When you make the nandroid backup select to backup to the SD card and not onto the device.
xdrc45 said:
Really depends on what you have on the device as far as apps, user data and so forth, but can be around 1-2 gb.
When you make the nandroid backup select to backup to the SD card and not onto the device.
Click to expand...
Click to collapse
I don't have that option. Do I just move the folder to the sd card?
EDIT: NVM I found it
After you get recovery in your phone... Go & Search this forum for @kuma82 's kumakan rom for locked bootloaders. Its the best I have found. I'm on cm9 for locked boot loader right now but I'm going to probably switch back to kumakan. He's already got the xposed framework & gravity box set up. Internal/external memory swap script too. Highly suggest it.
Sent from my LG Optimus L9 using Tapatalk
Hey guys I'm trying to install the Themed ROM for P769 Locked bootloader. (http://forum.xda-developers.com/showthread.php?t=2468880) I have the phone rooted from awhile back, i cant recall what i used to root it, the phone is still on 4.0.4, I am trying to put a recovery on it to install this ROM, but I dont see any recoveries for 4.0.4, I've seen a few different ones for JB but I'm not sure if its compatible.
This is the recovery it said to install (http://forum.xda-developers.com/showthread.php?t=2095825) but the issue is that the link to the recovery was taken down, so I'm not sure what recovery I can install.
TLDR: I got a rooted T769 on 4.0.4 and i would like to install the themed ROM for T769 with Locked BL.
eric303 said:
Hey guys I'm trying to install the Themed ROM for P769 Locked bootloader. (http://forum.xda-developers.com/showthread.php?t=2468880) I have the phone rooted from awhile back, i cant recall what i used to root it, the phone is still on 4.0.4, I am trying to put a recovery on it to install this ROM, but I dont see any recoveries for 4.0.4, I've seen a few different ones for JB but I'm not sure if its compatible.
This is the recovery it said to install (http://forum.xda-developers.com/showthread.php?t=2095825) but the issue is that the link to the recovery was taken down, so I'm not sure what recovery I can install.
TLDR: I got a rooted T769 on 4.0.4 and i would like to install the themed ROM for T769 with Locked BL.
Click to expand...
Click to collapse
I'm guessing you mean that you have a P769 T-Mobile version.
Here is a link to the L9 Recovery Installer - https://www.dropbox.com/s/l8tegpmiyh8moa5/L9RecoveryInstaller_1.5.0.apk
Since your already rooted, just make sure that you download and install BusyBox by stericson from the playstore, before installing the L9 recovery installer. It needs BusyBox installed on your device for it to work properly.
Download the Kumakan themed ROM to your external sdcard.
Open the BusyBox app and click on and select the version of BusyBox to install to the device and select version 1.21.0 to install.
Then install the L9 recovery installer app. Open the app and select "Install recovery" then select "jb/ics stable version", then grant it root rights through SuperSU when asked for permission.
Once it says recovery is installed, select power down/reboot the device. After the phone starts to boot up you'll see your front keys blinking this means you have recovery success and to enter into recovery immediately press and hold volume(-) down button while lights are still blinking... You are now in recovery mode. I would highly recommend that you immediately preform a nandroid backup of your L9 right now before doing anything else. Select backup and restore, choose backup and choose backup to external sdcard.
Once the nandroid backup is done then you are free to flash the Kumakan themed ROM that you want to install. Just follow the directions from the ROM thread to install the ROM.
xdrc45 said:
I'm guessing you mean that you have a P769 T-Mobile version.
Here is a link to the L9 Recovery Installer - https://www.dropbox.com/s/l8tegpmiyh8moa5/L9RecoveryInstaller_1.5.0.apk
Since your already rooted, just make sure that you download and install BusyBox by stericson from the playstore, before installing the L9 recovery installer. It needs BusyBox installed on your device for it to work properly.
Download the Kumakan themed ROM to your external sdcard.
Open the BusyBox app and click on and select the version of BusyBox to install to the device and select version 1.21.0 to install.
Then install the L9 recovery installer app. Open the app and select "Install recovery" then select "jb/ics stable version", then grant it root rights through SuperSU when asked for permission.
Once it says recovery is installed, select power down/reboot the device. After the phone starts to boot up you'll see your front keys blinking this means you have recovery success and to enter into recovery immediately press and hold volume(-) down button while lights are still blinking... You are now in recovery mode. I would highly recommend that you immediately preform a nandroid backup of your L9 right now before doing anything else. Select backup and restore, choose backup and choose backup to external sdcard.
Once the nandroid backup is done then you are free to flash the Kumakan themed ROM that you want to install. Just follow the directions from the ROM thread to install the ROM.
Click to expand...
Click to collapse
I follow all of the above steps to a tee. The recovery installs fine but when I try to reboot back into my rom all I can get is the white screen that says " encrypting" and " reset phone"... I'm on software version, P76920h.... any help would be appreciated.
Mangani001 said:
I follow all of the above steps to a tee. The recovery installs fine but when I try to reboot back into my rom all I can get is the white screen that says " encrypting" and " reset phone"... I'm on software version, P76920h.... any help would be appreciated.
Click to expand...
Click to collapse
Sorry for the late reply!
Did you make a nandroid backup when you installed and booted recovery?
If so, all you have to do is just reboot to recovery and restore your nandroid backup and you'll be back in businesses.
samsung galaxy s4 sch-1545 vzw
i tried to install a custom rom somthing wrong and now no phone
i can get into download mode but thats it. when i turn on the phone it tells me to connect
to kies to do a recovery but my device is not supported
i have tried to flash stock rom in odin but it fails everytime not sure what im doing wrong please help
porter46985 said:
samsung galaxy s4 sch-1545 vzw
i tried to install a custom rom somthing wrong and now no phone
i can get into download mode but thats it. when i turn on the phone it tells me to connect
to kies to do a recovery but my device is not supported
i have tried to flash stock rom in odin but it fails everytime not sure what im doing wrong please help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2735172
Flash the full-wipe version in Odin.
Then if you want custom roms, follow my instructions:
First, obtain root. Go to your Settings/Security, check "allow installation from unknown sources". Go to www.towelroot.com , click on the lambda, install the towelroot.apk, then open it and hit "make it ra1n". After reboot, download SuperSU. Open it, it will prompt you to update binaries, do so using the "normal" option. Congrats, you're rooted.
The only custom recovery you can have on NC5 is Safestrap, no TWRP or CWM. You can only flash TW rom's and a select few GPE rom's. You need to use AT&T's 3.72 safestrap for kit kat rom's, which can be found here: http://forum.xda-developers.com/show....php?t=2448925
To install safestrap, first install busybox. Find it here: https://play.google.com/store/apps/d....busybox&hl=en
Then, change selinux status to permissive. Do this by using selinux mode changer: https://play.google.com/store/apps/d....selinux&hl=en
Now install the safestrap apk, open it and hit the install recovery button.
To flash a kit kat rom with SS 3.72, you must use the "stock" slot. ROM slots don't work. You can still make a backup of your stock rom incase anything goes wrong. Be warned, you should have Odin and an NC5 tar file ready to go at all times on your comp.
So, you install the rom like you normally do with TWRP or CWM. Wipe data, cache, dalvik cache, system. Then flash rom, modules, and SuperSU.
The NC5 modules are here: https://www.androidfilehost.com/?fid=23486521113837640
The SuperSU zip is here: http://forum.xda-developers.com/show....php?t=1538053
If you forget to flash SuperSU, you may lose root. You can still get it back by using towelroot. If Wifi isn't turning on, try going back into Safestrap and flashing this: https://www.androidfilehost.com/?fid=23487008491963696
To install one of the Google Play Edition ROM's, use the directions in this thread: http://forum.xda-developers.com/gala...ition-t2817708
I seem to have the same exact phone and problem as this guy, so I'll jump in here. I've been working on my un-bootable Verizon Samsung Galaxy S4 i545 phone for about 4 full evenings with no luck.
My history up to this point:
Have Verizon Galaxy S4 i545 with latest OTA stock updates, never rooted. Build number ends with NC5.
Sunday night, performed Towelroot.
Installed SuperSU and SafeStrap.
Performed steps to disable KNOX.
Booted into SafeStrap 3.72.
OK, backed up the Stock Rom to my ext 64gb SD card.
Created a new ROM Slot and tried to install Google Play Edition S4 ROM to it.
On reboots it was booting into the regular Stock ROM (which I had factory reset btw) instead of my custom ROM, even though ROM Slot 1 was active.
Deleted ROM Slot 1 and tried flashing my ROM to Stock ROM slot.
Seem to fail.
SafeStrap now reports this when I click on STOCK ROM:
System partition Size: 0MB (0MB Free)
Data partition Size: 0MB (0MB Free)
Cache partition size: 2046MB (1984MB Free)
OK, so SafeStrap is clearly very messed up.
Booted into Download mode.
Got Odin 3.09 installed on Windows and got the firmware provided here: rootjunkysdl - dot - com/?device=Galaxy%20S4&folder=Firmware that ends in NC5 -- by the way the forum link you posted has dead 404 download links for both Firmwares. Seems like RootJunky was kind enough to mirror them on his server though.
Odin hangs when I try to flash the .tar.md5 file -- it says Device Added and the COM port is there so I know it's connected. After a few minutes with no progress or changes, it says "Complete(Write) operation failed" FAIL.
I think my phone's partitions got screwed up, or else it has a write lock on it. Any help would be MUCH appreciated and will even donate $25 to a project of your choosing upon getting this working.
UPDATE: Sure enough, just 15 minutes after I posted this I gave it one more full go in Odin 3.07 instead of 3.09 and it seems to be working now. Not sure if that had anything to do with it. Sucks that this phone can't work with custom recoveries like ClockWork... SafeStrap takes up a lot of extra space because you have to store both roms on the card at once.
Update 2: You also posted an Error 404 link to the Google Play Edition forum post. I'd like to get that on my phone.
joshm.1219 said:
http://forum.xda-developers.com/showthread.php?t=2735172
Flash the full-wipe version in Odin.
Then if you want custom roms, follow my instructions:
First, obtain root. Go to your Settings/Security, check "allow installation from unknown sources". Go to www.towelroot.com , click on the lambda, install the towelroot.apk, then open it and hit "make it ra1n". After reboot, download SuperSU. Open it, it will prompt you to update binaries, do so using the "normal" option. Congrats, you're rooted.
The only custom recovery you can have on NC5 is Safestrap, no TWRP or CWM. You can only flash TW rom's and a select few GPE rom's. You need to use AT&T's 3.72 safestrap for kit kat rom's, which can be found here: http://forum.xda-developers.com/show....php?t=2448925
To install safestrap, first install busybox. Find it here: https://play.google.com/store/apps/d....busybox&hl=en
Then, change selinux status to permissive. Do this by using selinux mode changer: https://play.google.com/store/apps/d....selinux&hl=en
Now install the safestrap apk, open it and hit the install recovery button.
To flash a kit kat rom with SS 3.72, you must use the "stock" slot. ROM slots don't work. You can still make a backup of your stock rom incase anything goes wrong. Be warned, you should have Odin and an NC5 tar file ready to go at all times on your comp.
So, you install the rom like you normally do with TWRP or CWM. Wipe data, cache, dalvik cache, system. Then flash rom, modules, and SuperSU.
The NC5 modules are here: https://www.androidfilehost.com/?fid=23486521113837640
The SuperSU zip is here: http://forum.xda-developers.com/show....php?t=1538053
If you forget to flash SuperSU, you may lose root. You can still get it back by using towelroot. If Wifi isn't turning on, try going back into Safestrap and flashing this: https://www.androidfilehost.com/?fid=23487008491963696
To install one of the Google Play Edition ROM's, use the directions in this thread: http://forum.xda-developers.com/gala...ition-t2817708
Click to expand...
Click to collapse
You should see about getting this stickied on Q and A. It seems nobody reads anything and maybe a title like "EVERYTHING YOU NEED TO FIX YOUR SOFT BRICKED PHONE" might get some reads.... just a thought.
statikeffeck said:
I seem to have the same exact phone and problem as this guy, so I'll jump in here. I've been working on my un-bootable Verizon Samsung Galaxy S4 i545 phone for about 4 full evenings with no luck.
My history up to this point:
Have Verizon Galaxy S4 i545 with latest OTA stock updates, never rooted. Build number ends with NC5.
Sunday night, performed Towelroot.
Installed SuperSU and SafeStrap.
Performed steps to disable KNOX.
Booted into SafeStrap 3.72.
OK, backed up the Stock Rom to my ext 64gb SD card.
Created a new ROM Slot and tried to install Google Play Edition S4 ROM to it.
On reboots it was booting into the regular Stock ROM (which I had factory reset btw) instead of my custom ROM, even though ROM Slot 1 was active.
Deleted ROM Slot 1 and tried flashing my ROM to Stock ROM slot.
Seem to fail.
SafeStrap now reports this when I click on STOCK ROM:
System partition Size: 0MB (0MB Free)
Data partition Size: 0MB (0MB Free)
Cache partition size: 2046MB (1984MB Free)
OK, so SafeStrap is clearly very messed up.
Booted into Download mode.
Got Odin 3.09 installed on Windows and got the firmware provided here: rootjunkysdl - dot - com/?device=Galaxy%20S4&folder=Firmware that ends in NC5 -- by the way the forum link you posted has dead 404 download links for both Firmwares. Seems like RootJunky was kind enough to mirror them on his server though.
Odin hangs when I try to flash the .tar.md5 file -- it says Device Added and the COM port is there so I know it's connected. After a few minutes with no progress or changes, it says "Complete(Write) operation failed" FAIL.
I think my phone's partitions got screwed up, or else it has a write lock on it. Any help would be MUCH appreciated and will even donate $25 to a project of your choosing upon getting this working.
UPDATE: Sure enough, just 15 minutes after I posted this I gave it one more full go in Odin 3.07 instead of 3.09 and it seems to be working now. Not sure if that had anything to do with it. Sucks that this phone can't work with custom recoveries like ClockWork... SafeStrap takes up a lot of extra space because you have to store both roms on the card at once.
Update 2: You also posted an Error 404 link to the Google Play Edition forum post. I'd like to get that on my phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...ow-to-install-aosp-s4-google-edition-t2817708
Here you go
liljoe727 said:
You should see about getting this stickied on Q and A. It seems nobody reads anything and maybe a title like "EVERYTHING YOU NEED TO FIX YOUR SOFT BRICKED PHONE" might get some reads.... just a thought.
Click to expand...
Click to collapse
I would but I honestly have no confidence in anyone reading a sticky haha
joshm.1219 said:
http://forum.xda-developers.com/gal...ow-to-install-aosp-s4-google-edition-t2817708
Here you go
I would but I honestly have no confidence in anyone reading a sticky haha
Click to expand...
Click to collapse
That would be.... revolutionary. Lol.
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Joserin said:
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Click to expand...
Click to collapse
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
JohnSmit268 said:
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
Click to expand...
Click to collapse
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Joserin said:
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Click to expand...
Click to collapse
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
JohnSmit268 said:
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
Click to expand...
Click to collapse
I already did that.. Root Checker Basic says I do not have proper root access and the TWRP Manager tool also says I do not have root
It is really weird. I'm on i9300 official nightlies and have working root!
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Joserin said:
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Click to expand...
Click to collapse
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
kush2.0 said:
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
Click to expand...
Click to collapse
Already tried that. SU binary just doesn't update. I even downloaded the Update zip and flashed from recovery, it still asks to update the binary after reboot. There is no TWRP option to update the binary either, it directly goes to the normal method and fails everytime. Tried like 20 times probably
I'd say flash back to stock and start over. Installing siyah probably borked something.
shivadow said:
I'd say flash back to stock and start over. Installing siyah probably borked something.
Click to expand...
Click to collapse
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
Joserin said:
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
Click to expand...
Click to collapse
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
kush2.0 said:
What recovery version are you using then?? ??
Click to expand...
Click to collapse
kush2.0 said:
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
Click to expand...
Click to collapse
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Joserin said:
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Click to expand...
Click to collapse
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
kush2.0 said:
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
Click to expand...
Click to collapse
Uhm TWRP Manager doesn't work without root. Already tried that
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Joserin said:
Uhm TWRP Manager doesn't work without root. Already tried that
Click to expand...
Click to collapse
Yeah sorry you do need root access. Your probably better of doing what rp158
Said. Your twrp recovery isn't up to date enough to install a new cm13 based ROM.
rp158 said:
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Click to expand...
Click to collapse
Meh Id rather just let it be for what it is. It's my dad's phone and I just wanted him to have AdAway, he's not much of a tech-head.
Thanks people
No root access to S3 when upgraded to CM 13; affecting full access Ext SDcard
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
kevin.a69 said:
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
Click to expand...
Click to collapse
I flashed QSi9300KK on my phone (with kernel. I forget the name but it was the third option - not Agni or stock) and after that TWRP and then CM13. Everything's working fine now, even root access.
Remember do not pick the first two kernels in the installer, they didn't work correctly. Third one works like a charm.