My previous phone was the HTC Inspire which had S-On, S-Off settings. Because my phone was S-On, I had to flash a boot.img file each time I flashed a ROM.
Once I root my GS4, is it necessary to go through the whole flashing of the boot.img file?
topcatzs13 said:
My previous phone was the HTC Inspire which had S-On, S-Off settings. Because my phone was S-On, I had to flash a boot.img file each time I flashed a ROM.
Once I root my GS4, is it necessary to go through the whole flashing of the boot.img file?
Click to expand...
Click to collapse
no, when flashing a rom in recovery the boot.img is already included in the zip
topcatzs13 said:
My previous phone was the HTC Inspire which had S-On, S-Off settings. Because my phone was S-On, I had to flash a boot.img file each time I flashed a ROM.
Once I root my GS4, is it necessary to go through the whole flashing of the boot.img file?
Click to expand...
Click to collapse
The Galaxy S4 (and all Galaxy variants afaik) does not have an "S-On" or "S-Off". However, we do have a locked/encrypted bootloader on some models, including the AT&T and Verizon versions. To flash ROMs on an AT&T device, be sure to do one of the following:
- Only flash ROMs that have been "Loki" patched, or "Lokified". Thanks to djbliss's Loki exploit, we are still able to flash ROMs and Recovery partitions that have been patched with this exploit.
- If you flash a ROM that is not Lokified, be sure to IMMEDIATELY flash a Loki-patched Kernel that's compatible with the ROM you just flashed - do NOT reboot until you have done so.
- Flash a Lokified Recovery that does "Auto-Loki" - meaning that it will automatically patch any ROM or Kernel that is flashed through this Recovery.
Aou said:
The Galaxy S4 (and all Galaxy variants afaik) does not have an "S-On" or "S-Off". However, we do have a locked/encrypted bootloader on some models, including the AT&T and Verizon versions. To flash ROMs on an AT&T device, be sure to do one of the following:
- Only flash ROMs that have been "Loki" patched, or "Lokified". Thanks to djbliss's Loki exploit, we are still able to flash ROMs and Recovery partitions that have been patched with this exploit.
- If you flash a ROM that is not Lokified, be sure to IMMEDIATELY flash a Loki-patched Kernel that's compatible with the ROM you just flashed - do NOT reboot until you have done so.
- Flash a Lokified Recovery that does "Auto-Loki" - meaning that it will automatically patch any ROM or Kernel that is flashed through this Recovery.
Click to expand...
Click to collapse
Great! Thanks.
Related
Tried to flash a rom using TWRP and now I'm stuck on the Samsung Custom screen??? Seems like a soft brick. Need the phone to function......
Looks like you didn't flash the proper version of TWRP and flashed one for one of the other versions of the S4, 9500 or 9505 which have unlocked bootloaders. A special version of TWRP is made for the SGH-I337 because of its locked bootloader which contains the Loki exploit to allow it to boot.
Download Odin and the Stock Firmware, install USB drivers for phone, drivers are included in Samsung Kies or you can get them seperately
Put phone into Download mode
Restore stock firmware.
Use this to Root your phone and install the proper TWRP in one blow. http://forum.xda-developers.com/showthread.php?t=2297900
Use TWRP to flash any SGH-I337 Rom you want if thats what you were going to do, as long as it has the Loki patch. (Current CM10.1 does).
I haven't flashed a new ROM in quite a while and I've been quite happy with TWRP for quite some time now.
I've started looking around again, and there seems to be a lot of push for Safestrap Recovery-oriented ROMs.
What exactly is it? From what I've gathered, it's a recovery that doesn't directly interact with a bootloader, so you can still have a recovery even if your bootloader is locked?
If that's true, why is it necessary, especially for the Galaxy S4? I'm running the ATT version and unlocked the bootloader with no problems over a year ago.
The boot loader has never been unlocked on the ATT S4. The initial ones (MDB &MDL) had a bug that Loki exploited and allowed for replacing the kernel and recovery.
That bug got fixed in MF3.
Safestrap recovery doesn't replace the stock recovery and is available during the normal boot itself.
People with newer firmware on ATT S4 have no choice but to use safestrap.
With MDB or MDL bootloader you used the loki bootloader bypass. YOUR bootloader IS STILL LOCKED down, but the LOKI BYPASS allowed us to run twrp. Loki is what allowed for using twrp. With twrp you can flash ANY Roms, modems, KERNELS. Pretty much can flash anything as long as you Loki the kernel. You can run AOSP based Roms like CM, AOKP, Etc.
For those that got there phone AFTER MF3 bootloader and Newer the exploit that allowed LOKI and TWRP was fixed. Those users are stuck using Touchwiz based Roms that run the stock ATT kernel and can ONLY use safestrap recovery. Safestrap recovery can ONLY flash Touchwiz based Roms (except maybe a small few converted Roms like google based Roms that can use the stock ATT kernel). As safestrap CANNOT flash modified kernels, so no custom kernels to undervolt/over volt/ etc. This also means no AOSP based Roms for the most part.
Hi,
I am running on rooted stocked OC4. This was done following the instruction which uses Flashfire to flash ROM and then ODIN to flash bootloader.
I am now looking to flash custom ROM (T-Mobile ROM specifically). From what I can read, the suggestion is to use safestrap which get around the locked boot loader in order to flash ROM.
However, there has been no update for saftstrap on 5.0.
Flashfire was able to flash stock ROM. Does it mean it has ways to get around locked bootloader?
Thanks
Okay, here is the deal. I was trying to install a costum rom on my att galaxy s4. What I did was I rooted it using king root and tried to flash a rom through rom toolbox, but I believe it was just going to take me to my recovery. After that the screen got stuck on the costum screen with the padlock, and only seems to turn on with a charger plugged into it. I am on 5.0.1 lollipop and have managed to flash the original recovery, but any stock rom I try to flash using Odin fails by saying complete thread failed or something like that, and says on my phone binary 1 or something like that. I really need help on where to start.
Thanks
What is the exact Odin error?
AT&T never released a full firmware for flashing via Odin beyond 4.1.2. Look here for a possible solution: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Once the phone is running a 4.3 or higher bootloader, the bootloader is locked and custom ROMs can't be installed unless the custom ROM is based on a stock ROM.
There's an ODIN flashable Android 4.2.2 MDL bootloader tar file out there somewhere too.
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
audit13 said:
If the bootloader is locked, and it sounds like it is since it's running 5.01, Odin will not be able to flash a 4.2.2 ROM or bootloader.
Click to expand...
Click to collapse
Are there any other options, or should I just give up on it?
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2
audit13 said:
Look at this thread: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814.
Pay attention to this part of the post which may help:
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/show...10&postcount=2
Click to expand...
Click to collapse
I finally fixed it. I had downloaded that rom before, but it hadn't worked. I decided to try it again and used a different USB port and it worked! Thanks for the help!
Guys Please help me. I am having Moto X Play (XT1562 dual sim version) which is unlocked bootloader, TWRP recovery, Rooted and Xposed framework flashed. Rom is stocked rom. Now I would like to revert to the stock recovery with stocked rom. How could I do it.
Once I installed Cyanogenmod Rom for my device and i returned to stock rom as per guidelines provided by senior member. I have all those files that needed at that time. but that is for whole ROM but now for me I need only stock recovery. Can I flash only recovery.img file that I extracted from stock factory image?
Please advice.
yes, you need to flash recovery.img from stock firmware. just make sure it's intendended for your phone model.
minimale_ldz said:
yes, you need to flash recovery.img from stock firmware. just make sure it's intendended for your phone model.
Click to expand...
Click to collapse
done smoothly. Just one more query. Can I revert to locked bootloader state.
sumangh01 said:
done smoothly. Just one more query. Can I revert to locked bootloader state.
Click to expand...
Click to collapse
AFAIK you can't revert your phone to fully locked state (your warranty will be void no matter what you do), you can only re-lock it. Hre's a thread about it:
https://forum.xda-developers.com/moto-x-play/help/how-relock-bootloader-moto-x-play-t3311497