I recently had to replace my phone through warranty and so now I'm new to Safestrap.
So please bare with me!
So what I am trying to do is root my phone keep the stock lollipop and put Xposed on but when I flash Xposed my phone gets stuck on AT&T.
The other day I ended up trying something different and yes Xposed work but I was getting gasps and google play not wroking.
Here are my steps for when my phone gets stuck on AT&T ( These are also my notes for me that I keep and follow)
1. Odin through computer and put I337UCUFNB1_Rootable_Full_Odin.
2. Once installed and gone through set up steps, installed Towelroot, and Root Phone.
3. Install Super User. (Sometimes after it disables Knox it requires to reboot or If disabling Knox takes WAY too long get out of app press menu key and close out all apps and clear ram. Re open super su and it will disable Knox and no reboot is required)
4. Install Flash Fire.
5. Flashed - I337_OC3_Stock_DeOdexed_ROM.zip through Flash Fire (Flash Zip or OTA). Once it tries to restart for about 10-20 minutes there will be AT&T logo.
6. Once installed and gone through set up steps again, install Busy Box, Safestrap, & NC1 Flasher.
7. In Safestrap app - clicked on Install Recovery
8. NC1 app - Flashed and reboot.
9. Safestrap loads up.
10. Wipe Factory reset
11. Install ATT_OC3_modules
12. Install I337_Stock_OC3_kernel_recovery_flashable and then reboot. Again AT&T logo sits for about 10 - 20 minutes and I do a battery pull.
13. Install Flash Fire and XposedInstaller_3.0_alpha4.apk
14. Flash xposed-v74-sdk21-arm.zip through Flash Fire.
15. The phone will sit at the AT&T logo for ever. I do a battery pull and still the same thing. Will not Boot up.
I DON’T THINK THIS IS PROCESS IS RIGHT BUT XPOSED DID WORK AND GASPS AND GOOGLE PLAY STOPPED WORKING.
-Note the Colored lines is what I did differently from up above
1. Odin through computer and put I337UCUFNB1_Rootable_Full_Odin.
2. Once installed and gone through set up steps, installed Towelroot, and Root Phone.
3. Install Super User. (Sometimes after it disables Knox it requires to reboot or If disabling Knox takes WAY too long get out of app press menu key and close out all apps and clear ram. Re open super su and it will disable Knox and no reboot is required)
4. Install Flash Fire.
5. Flashed - I337_OC3_Stock_DeOdexed_ROM.zip through Flash Fire (Flash Zip or OTA). Once it tries to restart for about 10-20 minutes there will be AT&T logo.
6. Once installed and gone through set up steps again, install Busy Box, Safestrap, & NC1 Flasher.
7. In Safestrap app - clicked on Install Recovery
8. NC1 app - Flashed and reboot.
9. Safestrap loads up.
10. Wipe Factory reset
11. Install I337_OC3_Stock_DeOdexed_ROM.zip
12. Install ATT_OC3_modules
13. Install I337_Stock_OC3_kernel_recovery_flashable and then reboot. Again AT&T logo sits for about 10 - 20 minutes and I do a battery pull.
14. Install Flash Fire and XposedInstaller_3.0_alpha4.apk
15. Flash xposed-v74-sdk21-arm.zip through Flash Fire.
16. The phone will sit at the AT&T logo for ever. I do a battery pull and still the same thing. Will not Boot up.
17. Battery Pull and go into Recovery Mode.
18. Wipe Clean and then Installed I337_OC3_Stock_DeOdexed_ROM.zip
19. I believe this is the time when it was able to restart the phone. Xposed work but got GASPS and GOOGLE not working.
I have also tried to install Xposed through Safestrap but I believe it didn't work.
I know this is long but I've finally been trying to keeps notes on what and how I've been doing this.
Can someone Please help me with this process?
You need to sdk22 version of xposed for the S4.
Sent from my SGH-I337 using XDA Free mobile app
Actually you need the unofficial xposed for tw, look here. http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
Unless the official xposed works now, I haven't checked the thread lately.
I had the same problem. After some trial and error and many bootloops later, I found the right files. I've attached the ones I use. I use GoldenEye ROM, but it should work on OC3 Deodexed ROM too.
Related
Hi,
i try to encrypt and root my note 4.
After rooting the phone i try to encrypt it, but it always stuck after reboot on the samsung logo (for hours)
Without rooting it will encrypt in ~10 mins.
Ps. the note is rootet with the 4.4.4 cf-auto-root from chainfire.
anyone had a soulution for me ?
thank you so mutch ! :good:
edit:
I found a soulution for this.
1. root your phone with cf-auto root
2. install busybox
3. install a terminal app
4. open the terminal app and type:
su
pkill -KILL daemonsu
after this you should be back at the "$" prompt
now directly encrypt your phone, dont reboot or change something in the terminal app
Nexus-Nerd said:
Hi,
i try to encrypt and root my note 4.
After rooting the phone i try to encrypt it, but it always stuck after reboot on the samsung logo (for hours)
Without rooting it will encrypt in ~10 mins.
Ps. the note is rootet with the 4.4.4 cf-auto-root from chainfire.
anyone had a soulution for me ?
thank you so mutch ! :good:
edit:
I found a soulution for this.
1. root your phone with cf-auto root
2. install busybox
3. install a terminal app
4. open the terminal app and type:
su
pkill -KILL daemonsu
after this you should be back at the "$" prompt
now directly encrypt your phone, dont reboot or change something in the terminal app
Click to expand...
Click to collapse
Thank you for this! It worked for me.
Just a word for advice for anyone that tries to DECRYPT their phone after having encrypted it using this method. When I tried decrypting my phone I got a decrypt fail error telling me I had to reset the device, but because I had a custom ROM the reset wasn't working. I had to ODIN back to stock and start all over.
So, though I didn't try it again, you probably need to follow the same steps prior to decrypting. Either way, keep in mind you may be forced to reset so do backups before you attempt to decrypt.
That was on a T-Mobile Note 4 on KitKat, not Lollilop BTW.
Another method (success)
Just to share my experience, maybe it will be useful for someone.
I have Galaxy Note 4 rooted using CF-auto-root, and when trying to encrypt the device, all I got was green android logo on black screen for hours. The phone froze, so I eventually had to pull out the battery. After booting I got the message that encryption failed due to interruption, and promted to do a factory reset, which I did.
I tried the method above, but it did not work. The result was exactly the same -- green robot and nothing else.
Then I tried another method I found in another thread, and it worked!
1-Root your device and install/update SuperSu;
2-Convert SuperSu to system app (there is an option in SU config). Reboot.
-OBS: If your root method has already installed SuperSu as a system app, this step can be skipped;
3-As SuperSu is now a system app, it can be deactivated through Applications Management in settings. Deactivate it;
-OBS: does NOT use deactivate in SU own config;
4- Reboot in Safe Mode. This can be done pressing both Volume Up/Down while rebooting;
5-Start encryption the normal way and wait until it finishes. Enter your password and wait device boot normally;
6-Go to Applications Management in settings and activate SuperSu;
7-Reboot one more time and your system is encrypted with SuperSu working normally.
Oscar_6 said:
Just to share my experience, maybe it will be useful for someone.
I have Galaxy Note 4 rooted using CF-auto-root, and when trying to encrypt the device, all I got was green android logo on black screen for hours. The phone froze, so I eventually had to pull out the battery. After booting I got the message that encryption failed due to interruption, and promted to do a factory reset, which I did.
I tried the method above, but it did not work. The result was exactly the same -- green robot and nothing else.
Then I tried another method I found in another thread, and it worked!
1-Root your device and install/update SuperSu;
2-Convert SuperSu to system app (there is an option in SU config). Reboot.
-OBS: If your root method has already installed SuperSu as a system app, this step can be skipped;
3-As SuperSu is now a system app, it can be deactivated through Applications Management in settings. Deactivate it;
-OBS: does NOT use deactivate in SU own config;
4- Reboot in Safe Mode. This can be done pressing both Volume Up/Down while rebooting;
5-Start encryption the normal way and wait until it finishes. Enter your password and wait device boot normally;
6-Go to Applications Management in settings and activate SuperSu;
7-Reboot one more time and your system is encrypted with SuperSu working normally.
Click to expand...
Click to collapse
I have been trying to find a way to do this on my TMobile branded Note 4 for some time now. As I am contemplating updating to the recently released 5.0.1 for my variant, I wanted to know if you have had any problems with your device after using your method? Were there any issues with regard to decryption?
PS- Anyone else take 15 tries to get through the blasted image verification.
KingBeef said:
I have been trying to find a way to do this on my TMobile branded Note 4 for some time now. As I am contemplating updating to the recently released 5.0.1 for my variant, I wanted to know if you have had any problems with your device after using your method? Were there any issues with regard to decryption?
Click to expand...
Click to collapse
I have upgraded to Lollipop before encrypting the phone. I didn't try to decrypt it after encryption. So far, everything is working normally.
Followed guide for safestrap AT&T, only part that I might have messed up was when flashing modules zip and it says to pull battery, I pulled after it booted to safestrap, I never got success or passed message, I then flashed partitions and it booted after 15 minutes or so but WiFi isn't working and I'm getting random restarts, like I clicked home button and just restarted. Also when I tried opening stock messaging app, screen would just flash like a soft reboot but nothing would open. After few tries text app did open. Any ideas what to do? Thanks
Update:
this has turned into a PIA, lost root, safestrap wont boot into recovery anymore it just keeps showing safestrap boot screen when i press recovery. wifi wont turn on and tried factory reset as well. also tried reflashing oc3 kernel mod zip again and still no wifi.
Any ideas on what is causing wifi to not even attempt to turn on when i hit the toggle? I saw something about needing to flash safestrap modules after installing rom on verizon models....lost.... thanks for any help
There are a couple of things you need. You can find the links in the thread just search for them. But you need the flashable zip for the oc3 kernel and the apk for nc1 flasher. Then after you run nc1 you'll boot directly into safestrap. Then in safestrap you can flash your modules to get wifi working.
As far as root goes, goldeneye is funny, it comes prerooted but in supersu settings you have to select grant supersu automatically because it won't prompt for SU access.
Hope this helps.
Sent from my SGH-I337 using Tapatalk
My SGS4 i9505 (Intl.) is running CyanogenMod 13.0, specifically cm-13.0-20160114-NIGHTLY-jfltexx with Gapps flashed.
I also have TWRP 2.8.7 installed on Recovery.
My phone had been working perfectly until this evening. I opened SuperSU app (which I downloaded from Play Store) and a message popped up saying i had to install SuperSU binary Normally or using TWRP/CWM. Normal Install popped up an error message, so I downloaded the zip from download.chainfire.eu (UPDATE-SuperSU-v2.46). Then saved it on my SD card and flashed it through TWRP.
After the installation-flashing was complete, I tapped on Reboot->System and since then I am stuck on loading screen.
Is there a way to undo the flashing (Don't care about SU, just want my data unharmed)?
What did I do wrong so as to avoid doing it next time?
Please help as soon as possible,
Thanks in advance.
no hope you needed to backup your data and format your phone anyway
CM13 is already rooted. You need to enable developer options and then enable root access under developer options.
Just dirty flash your phone with the cm13 zip and you should be fine.
Also remember twrp at times needs a shock treatment (in my language)
When your at the samsung logo which comes before the booting and it has been a while..just pull tbe battery out and after 30 seconds put it back and turn the phone on
Things should be fine.
Hi,
If you need SuperSU on CM13, use SuperSU 2.56 or newer.
Sent from my GT-I9500
EDIT: This can be marked as resolved -- I used ADB to succesfully send a reboot recovery command to the phone and it worked!
Hope I don't run into any more issues down the road.
-----------
Hi guys
In short, my LG D802 International model has lost it's ability to enter DL mode, and the recovery is also missing.
It is now running Stock Lollipop (Custom version) which I installed according to instructions with no problem
However once it was installed I then realized TWRP is no longer accessible. My next step was to then go to the Play Store and download Autorec Lollipop for LG G2 D802
https://play.google.com/store/apps/details?id=b007.autorec2&hl=en
Once that was installed I tried to install the recovery, but the app was unresponsive. The author of the app then mentioned ->If you experience unresponsive button (the button flash doesn´t work) look up this post
http://forum.xda-developers.com/showpost.php?p=65698392&postcount=797
I went ahead to uninstall SuperSU using it's full cleanup and remove function. BIIIG mistake!
That's where the problems compounded, because now SuperSU is not even working and won't let me install the SU Binaries, and the app is telling me to search forums for help
Basically: No TWRP -- No Download Mode -- No Root -- Cannot install SuperSU either!
I'm now stuck with a very unstable phone that hangs and crashes every 10 minutes. I have tried to factory reset but to no avail -- I still cannot use SuperSU.
Thanks in advance
Hello all,
This may seem like a stupid question, but I want to make sure that I know what i'm doing before I mess something up and become
So I'm running a Samsung Galaxy S5 (G900V ovbiously), and it has the tobisha emmc chip
Is the only way to gain root on Marshmallow/Nougat or whatever is by reverting to Lollipop, gaining root access, installing TWRP, and then flashing LineageOS/some ROM?
Directions For Users With CID 11 Toshiba eMMC
1. Download EMMC_11_ Root S5_QB2_PB1.zip
2. Unzip
Copy the following to your External SD card:
Root S5 Folder,
EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip,
and the TouchWiz ROM you want to install.
3. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
4. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
5. Flash and let the phone reboot. It will reboot to recovery and finish install then it will reboot and take about 20 seconds to boot.
6. If you do not have an External SD Card, copy the following NOW to your Internal Storage:
Root S5 Folder,
EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip,
and whatever TouchWiz ROM you want to install.
7. Use the File Manager in the app drawer of the phone and install Apex_Lancher.apk press home button and set Apex as the default launcher.
Install Superuser.apk, Busybox.apk and SafeStrapKK.apk do not open anything yet.
8. Now Install tr_v2.apk.
Open TowelRoot and CLICK MAKE IT RAIN . It should tell you you have succeeded.
9. Now Open Superuser app and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot. You can skip doing this. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
10. Now open the BusyBox app, grant SuperSU access and install BusyBox.
11. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed) if not click "install" again, reboot phone and open SafeStrap and try to install recovery again
12. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
13. Once in SafeStrap Recovery, choose what firmware you want to be on:
Lollipop 5.0 Firmware=EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip
Marsmhallow 6.0 Firmware=EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip
14. Install the firmware zip, and then flash a TouchWiz Lollipop ROM. (Here is the latest stock rooted Lollipop Rom: VZW_BPB1_ODEX_DEODEX_V9.zip). You may want to download a copy of the latest SuperSu zip, and flash if installing a Lollipop ROM that is not rooted. Remember, you cannot root Marshmallow ROMs, so do not try and flash the SuperSu zip on a Marshmallow Rom (you will softbrick if you do).
15. After you install any Lollipop ROM, you may need to reinstall SafeStrap Recovery. Most of the time you don't have to and SafeStrap can be reached by flashing the KitKat Kernel in Download Mode with ODIN. But, in some cases, when flashing a ROM that flashes a system.img instead of a system folder, you may lose SafeStrap during install. This will be the case if you install the above ROM. You can reinstall it after the ROM is booted up. A Safestrap-G900V-4.04_LL_MM.apk is included that will flash a version of SafeStrap that will allow you to reboot to SafeStrap Recovery without flashing a KitKat kernel in Odin. Install BusyBox again from the BusyBox App in the RootS5 Folder. Install Safestrap-G900V-4.04_LL_MM.apk and make sure to grant SuperSU access. It may take a few seconds to prompt. If SafeStrap is not installed, click "Install Recovery". If Safestrap is still installed click on "Uninstall Recovery", close the app, and reopen it. It should say recovery is not installed. Now click on "Install Recovery". If this doesn't work, reboot the phone and try again. Once installed, you can just click reboot to SafeStrap from the SafeStrap app and you will reboot straight to SafeStrap. Remember to flash the appropriate Kernel when leaving SafeStrap!
Download and place these on your device:
LL_KERNEL_SS-FF_Flashable.zip, and
MM_KERNEL_SS-FF_Flashable.zip
If something bad goes wrong you can usually get back to SafeStrap by simply rebooting the phone to Download Mode and flashing NI2_stock_kernel.tar.md5. When the phone reboots, watch for the SafeStrap splash screen and enter SafeStrap.
16. Do NOT change ANY boot options in SafeStrap. ROM slots cannot be used, so you must flash to the Stock ROM slot EVERY TIME OR YOU WILL SOFTBRICK. Some functions don't work in SafeStrap, like choosing an image file to flash directly. All image files must be flashed via zip file.
---------- Post added at 12:50 AM ---------- Previous post was at 12:49 AM ----------
Get the needed files at https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529