[Q] ATT Update to 5.0.1 fails, confirming a solution - Galaxy S 4 Active Q&A, Help & Troubleshooting

It has been over a year since I last flashed a S4A phone, so refreshing my notes and hoping someone can confirm the bits below are correct.
In case another, shorter way to accomplish same exists, kindly suggest it.
Background first.
Phone is SG4 Active, running Android 4.4.2. Baseband I537UCUCNH3, model is Samsung SGH I537, Build KOT49H.I537UCUCNH3
Phone is unlocked and was flashed with Odin one year ago to 4.3 and then ATT updated automatically to current version.
Status today.
When ATT offers download and install the 900 plus MB 5.0.1 update, it fails at 27 percent, reboots phone, repeatedly.
Phone has about 8 GB free space on internal memory and about 10 GB on SD card. As far as I can determine, no special mods have been done to phone and I have uninstalled all user installed apps so it has only ATT, Samsung and Google apps.
Proposed solution.
Found the original I537UCUBML2 bundle *2gb* (Android 4.3) with BL,AP,CSC,CP and I think that since Bootloader already installed, it should be possible to run Odin again and just flash AP,CSC and CP.
Once flashed the system will be back to 4.3 and the OTA updates should work, first to 4.4 and later to 5.0.1.
Can not recall right now just how to do the Odin flash but will use search to figure it out but is my thinking correct or am I missing something important ? For example, don't remember if I have to reboot phone first or if Odin handles it all once the USB cable is connected.
Thank you.

xdafly said:
It has been over a year since I last flashed a S4A phone, so refreshing my notes and hoping someone can confirm the bits below are correct.
In case another, shorter way to accomplish same exists, kindly suggest it.
Background first.
Phone is SG4 Active, running Android 4.4.2. Baseband I537UCUCNH3, model is Samsung SGH I537, Build KOT49H.I537UCUCNH3
Phone is unlocked and was flashed with Odin one year ago to 4.3 and then ATT updated automatically to current version.
Status today.
When ATT offers download and install the 900 plus MB 5.0.1 update, it fails at 27 percent, reboots phone, repeatedly.
Phone has about 8 GB free space on internal memory and about 10 GB on SD card. As far as I can determine, no special mods have been done to phone and I have uninstalled all user installed apps so it has only ATT, Samsung and Google apps.
Proposed solution.
Found the original I537UCUBML2 bundle *2gb* (Android 4.3) with BL,AP,CSC,CP and I think that since Bootloader already installed, it should be possible to run Odin again and just flash AP,CSC and CP.
Once flashed the system will be back to 4.3 and the OTA updates should work, first to 4.4 and later to 5.0.1.
Can not recall right now just how to do the Odin flash but will use search to figure it out but is my thinking correct or am I missing something important ? For example, don't remember if I have to reboot phone first or if Odin handles it all once the USB cable is connected.
Thank you.
Click to expand...
Click to collapse
ML2 won't help you. If you give me about 5-10 minutes I'll link you to the file you need (I'm slow because I'm on mobile and it's a tiny screen for my fat fingers lol)
---------- Post added at 02:43 PM ---------- Previous post was at 02:37 PM ----------
OK here is the file you need. Download and save it to your EXTERNAL SD card (internal storage won't work) and flash the file in stock recovery. You can boot to recovery by shutting the phone off, then holding down power and vol+simultaneously
If you want to be rooted, don't do this, I can point you to a different method

Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.

xdafly said:
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
Click to expand...
Click to collapse
Use Odin to restore NE3 kit kat instead of ML2. I can link to that too if you need
NE3 kit kat
You have to extract all 4 tar files and flash all 4 with Odin simultaneously

xdafly said:
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
Click to expand...
Click to collapse
The reason your install is failing is because you've modified the stock firmware. When you try to install an AT&T update, manually or automatically there is a script in that update that checks all the files on your phone to ensure that they are the original, unmodified files. If any single one of them is not original or modified, then the update will fail as you have experienced. So if you root your phone you are modifying system files. Even if you unroot, the system files were still modified at one point and the update will fail. I suspect you've done something like this.
The only way you can update to stock OC6 (5.0.1) is to flash your phone back to stock firmware and in your case it should be NE3. As has been explained you will need to flash the NE3 Odin package, but beware this will completely wipe your phone so backup anything you don't want to lose. There is a method for updating your phone without flashing back to stock described in this thread. Also, if you're ever looking for information on rooting and updating your phone it would be a good idea to familiarize yourself with the links in the i537 Firmware Guide.

Use Odin to restore NE3 kit kat instead of ML2.
Click to expand...
Click to collapse
Got it. Downloading (as suspected, the update.zip failed) and will hook up cable and run Odin 3.09 with all 4 files
All important data is backed up to Google so unless I lose some ATT settings, such as the IMEI code or similar, all should be well
Does the phone have to be in recovery mode before starting Odin ? Can't remember now and all Youtube videos show only AP being applied, not all 4 files simultaneously.
Edit, read http://www.samsungodindownload.com/odin-tutorial/
Thank you

BL file to bootloader (BL), CP file to phone (CP), CSC file to CSC, like below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Related

HTC One - Couldn't Install on USB Storage or SD Card

Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.
Make a nandroid and flash another rom to see if that fixes it.
You're using an old custom ROM! Flash any new ROM of your choice from the dev section and it should fix the problem. The issue is within the kernel.
StephanBotha said:
Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.
Click to expand...
Click to collapse
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
Hi,
I have this exact same issue. Nothing in secure folder etc. From 4.4 to 4.4.2 via OTA.
roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
The only fix for this is to install Android Revolution ROM. At least, that's the only way I could fix mine :crying:
You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.
BenPope said:
You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.
Click to expand...
Click to collapse
That's unfortunate, since I like twrp. To reinstall stock recovery, do I just flash the image like I did with twrp?
Yes. You can put TWRP back on after the OTA is on.
BenPope said:
Yes. You can put TWRP back on after the OTA is on.
Click to expand...
Click to collapse
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.
roman1984 said:
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.
Click to expand...
Click to collapse
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?
DyingBlade said:
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?
Click to expand...
Click to collapse
Once I was able to update using the stock recovery, all I had to do was flash TWRP and everything worked fine (no need to reinstall the GPE ROM since that was already running).

[Q&A] [RECOVERY LOCKED] Safestrap Recovery v3.75 [2014-06-29 KK B03]

Q&A for [RECOVERY LOCKED] Safestrap Recovery v3.75 [2014-06-29 KK B03]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Hey guys,
I installed safestrap 3.75 on my att note 3 (NC2 version). Couple issues I've noticed. When I reboot the phone, the screen says safestrap: disabled. So I click on "recovery mode". Now I"m in SS and try to back up my stock rom. I select backup, swipe to perform backup. It says backup failed. Questions are how do I get ss to enabled and why did the backup failed? Was ss installed incorrectly in the first place?
TIA.
Cyanogenmod?
Has anyone had any luck with installing Cyanogenmod via Safestrap? I'm currently getting just a black screen with CM11 (M11) or the CM-variant temasek v151.
clamchowder86 said:
Hey guys,
I installed safestrap 3.75 on my att note 3 (NC2 version). Couple issues I've noticed. When I reboot the phone, the screen says safestrap: disabled. So I click on "recovery mode". Now I"m in SS and try to back up my stock rom. I select backup, swipe to perform backup. It says backup failed. Questions are how do I get ss to enabled and why did the backup failed? Was ss installed incorrectly in the first place?
TIA.
Click to expand...
Click to collapse
first of make sure you're running the latest version, second it will say safestrap disabled when you have your Rom in stock slot, it becomes active when you have your stock Rom on stock slot and you create a slot and install your custom Rom in another slot.
AySz88 said:
Has anyone had any luck with installing Cyanogenmod via Safestrap? I'm currently getting just a black screen with CM11 (M11) or the CM-variant temasek v151.
Click to expand...
Click to collapse
With locked bootloader you can't install anything but stock based roms, for our note 3, and you're not flashing kernel either. Until the bootloader get unlocked nothing aosp based or cm we'll boot up.
RoloRacer on KillerKat Note 3
I have used this before on the t-mobile version of the note 3. I used it initially because I didn't want to break Knox. However, I now have twrp fully working on my note, with Knox tripped, but I'm wandering if it is save to use this to dual boot roms. That way I can rock my regular dd, and still boot some rocking aosp roms or some cm. Any thoughts on this would be appreciated.
Where's the .apk?
I followed the links for download at the top of the thread, but once downloaded all I have is a .zip file. There's no .apk in the zip. Suggestions welcome.
Unable to download the Safestrap-HLTEATT 3.1 version.
Unable to download the Safestrap-HLTEATT 3.71 version. Link not working. Please resolve this issue. I am using the at&t note 3 running on jelly bean. I installed safestrap 3.75. It showed installed. But the recovery option is not working. When I click on recovery it simply restarting the mobile. Please help me regarding this issue
Thank you
OC2 is available
Got OC2 update for AT&T Note 3 today when manually checked for software updates.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what is the OC2 update? your screenshot still says android version 5.0
Anyone know why I can't get safestrap to mount system? Can't make a backup, it fails during DATA. And if I try to install another rom in a slot, it also fails but for a reason I can't remember atm ...
From rooted Lolipop I did a backup and now the system won't boot. Makes me wish I didn't do the backup.
Does anyone have the safestrap apk for at&t ive looked all over the net and can not find it....
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Never mind 8 found it sorry guys
here ya go http://forum.xda-developers.com/attachment.php?attachmentid=3119865&d=1421514108
I download the safestrap app and installed the recovery, but my phone won't boot into recovery despite installing it. I have a galaxy s5 g900a and I'm running lollipop 5.0 rooted (which I manually flashed via odin).
*update* i downgraded to kitkat and it works perfectly again
Samsung Galaxy Note 3
MY note 3 SM-N900A
will not do anything after i tried to update, and now its saying firmware upgrade encountered an issue. Please select recovery mode in Kies (all versions) and try again, but ive tried that and it keeps saying my phone isnt supported, please help me.
I have a Galaxy Note 3 n900a AT&T and its rooted, busboy installed, Knox disabled and superuser. I followed every step to install safestrap but it doesn't boot into recovery at all. It boots to the Samsung Galaxy note 3 screen twice and then that's it. I've even tried wiping and factory reset and starting over. That didn't work either. Any idea where to go from here? ?

G920AUCU2AOF3 FlashFire Update | Keep Root

G920AUCU2AOE2 -> G920AUCU2AOF3 Updater
This is a modified version of the official OTA.
Upgrade from OE2 to OF3
Retains Root
Retains OE2 Bootloader
Retains OE2 Recovery
All checks removed (deleted, modified system files won't be patched, but it won't break the entire patching process)
If you unroot while on OF3 you will have to downgrade to OE2 kernel with Odin and use PingPong root.
Edited files WILL NOT be updated, they're skipped instead of breaking the entire update process like the stock OTA. If you want to update those files they need to be returned to stock OE2.
Download and unzip "OF3 Update.7z," extract G920AUCU2AOF3.zip to your sdcard.
In Flashfire select "Flash ZIP or OTA"
Select G920AUCU2AOF3.zip from your sdcard
Leave all of the settings default and flash.
After it has flashed, reboot to download mode and use Odin to flash the updated kernel and modem.
In Odin put boot.tar.md5 in the AP slot.
Put modem.tar.md5 in the CP slot.
Leave all other settings alone and click start.
Once the phone has rebooted you should be on OF3.
OF3 Update.7z
MD5: 2af43b437f238491ebe0aceb987de433
https://www.androidfilehost.com/?fid=24052804347773723
Is there a new baseband with this build? I flashed this in FlashFire and it still shows the old OE2 baseband.
Capt said:
Is there a new baseband with this build? I flashed this in FlashFire and it still shows the old OE2 baseband.
Click to expand...
Click to collapse
Seeing this made me go look. Same here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this update compatible with Scrosler's CleanRom?
ChristopherXDA said:
Is this update compatible with Scrosler's CleanRom?
Click to expand...
Click to collapse
Yes I used it and it worked fine
Mine says OF3
Sent from my SAMSUNG-SM-G920A using Tapatalk
I have to use Google+ to get Flashfire to flash this? Barf.
Well, I swallowed my bile and jumped through the G+ hoops to get FF. The update seems to be working well, but I was constantly getting a notification saying "Unauthorized Activity has been detected. Reboot now to undo the unauthorized changes." I disabled all Knox apps and the Security Log with Titanium Backup and it went away.
How did you get the OF3 baseband and the newest kernel? I have the old baseband/kernel.
Capt said:
How did you get the OF3 baseband and the newest kernel? I have the old baseband/kernel.
Click to expand...
Click to collapse
What Kernel version is your phone showing?
Mine is showing
3.10.31-4823236
[email protected] #1
Sun May 3 00:35:28 KST 2015
Which is the same as Cbass15 except his build date
Thu Jun 1818:20:13 KST 2015
Mine is showing 3.10.61 - 4823236. Sun May 3.
Capt said:
Mine is showing 3.10.61 - 4823236. Sun May 3.
Click to expand...
Click to collapse
I show the same, and appear to be having the same issues as you that you brought up in the other thread.
ChristopherXDA said:
Is this update compatible with Scrosler's CleanRom?
Click to expand...
Click to collapse
I know this is a stupid question, but can I flashfire this over my XtreStoLite ROM, or will I have re-flash the ROM after doing this?
Sorry! Maybe adding to the stupid questions.
Has anyone been brave enough to flashfire from OCE to this? I am unable to use a windows computer with ODIN for quite at least a week or two. Only have a access to a Mac.
What if I've already upgraded to OF3?
I wanted to check out OF3 so I flashed back to stock OE2 and updated it. After I found out that this rooted update was possible I tried flashing back to [email protected] but kept getting errors. Is that even possible or is there any way for me to get to rooted OF3? I just can't seem to flash back to OE2. Thanks for the help!
NizzleFish98 said:
I wanted to check out OF3 so I flashed back to stock OE2 and updated it. After I found out that this rooted update was possible I tried flashing back to [email protected] but kept getting errors. Is that even possible or is there any way for me to get to rooted OF3? I just can't seem to flash back to OE2. Thanks for the help!
Click to expand...
Click to collapse
No way back to OE2 if you took the OF3 OTA. The bootloaders are updated and don't allow you to roll back.
Also, I discovered you can't roll back the radio either, you just get unknown baseband.
designgears said:
No way back to OE2 if you took the OF3 OTA. The bootloaders are updated and don't allow you to roll back.
Also, I discovered you can't roll back the radio either, you just get unknown baseband.
Click to expand...
Click to collapse
Aw man that sucks Is it likely Ping Pong will be updated for this versions or no? Thanks for the response btw!
I updated the OP with new instructions. The initial release I made that was a Flashfire backup worked great for updating the modem and boot. I didn't notice that that few that used that had the proper things updated and those who used the modified OTA didn't. The new instructions and files take care of all of that.
designgears said:
I updated the OP with new instructions. The initial release I made that was a Flashfire backup worked great for updating the modem and boot. I didn't notice that that few that used that had the proper things updated and those who used the modified OTA didn't. The new instructions and files take care of all of that.
Click to expand...
Click to collapse
Worked perfect thank you sir!
I'm getting "unauthorized actions have been detected"? Anyone else?
Sent from my SAMSUNG-SM-G920A using Tapatalk
4redstars said:
I'm getting "unauthorized actions have been detected"? Anyone else?
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
Yep. freeze 4 knox app entries and one other - some security one, I forget the exact name - long press the notification and it will tell you - with TiBu and it will go away. That worked on the flash that didn't work right for me anyway, in the process of doing this new process now.

EXAMPLE How to install a CUSTOM ROM without tripping Knox 0x000 5.1.1 920T.

I decided to create a Thread because there were to many people asking how to Install a Custom ROM using the engineered bootloader and not tripping knox. (I Will not provide links to the Bootloader i already provided the MD5 number to compare so search on google)
I used to have Rapture 2.0 that is based on COF8(I UPDATED to Rapture 2.1 Have wificalling but didn't have time to UPLOAD pictures because i changed to XtreStolite 2.2) and i still have this method. KNOX 0x000.
I don't own any of this files, i just recompiled from the forum. All thanks to the developers and their respective work. (Aou's, g.lewarne and iB4STiD and Others). I REPEAT i don't own any of the files so don't ask for files if they get removed.
Flash it at your own Risk, I am not responsible if you damage your phone or don't follow instructions. Just tested on 920T and 925T tmobile variant and it works. YOU MUST use the engineer bootloader or you will trip knox. Fingerprint and Miracast not working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I used this Method:
DOWNLOAD These first:
Download ODIN3 3.10.6 from Here
Download Samsung USB Drivers from HERE
IF you are on 5.0.2 AOCG you must first UPDATE to COF6 from here and not FULL COF8 so you can get back to COF6 if needed. COF8 have more benefits but you still don't know.
STEPS:
1. OPEN ODIN and select AP and choose the 5.1.1 COF6 mentioned before.(Make sure RE-Partition is not selected in options. ONLY Auto Reboot and F. Reset Time) Wait until it verify.
2. Click on START and wait until your PHONE reboot(Never turn it off before it finishes)
3. After phone reboot continue bellow.
Before you do this make sure to ENABLE OEM Unlocking ON, on the Developer Options. (To enable Developer Options, go to Settings/About Device and After tapping the build number 7+ times, you will be notified you are a developer and the option will be there Settings/Developer Options)
1. Flash sboot.bin for you model. (Odin Select BL) Search on Google
S6 920T MD5: 6F8D0372CDF94A5B95B8034B7641E132
S6 925T MD5: 528F23A8138BF6570D1BAE0857B916E4
2. Flash Latest Unikernel from here (AP Odin , To give SE permisive) (Thanks to g.lewarne) Have the In Audio call fixed.
3. Odin-flashable TWRP recovery that Aou's put together (AP Odin) (Original Thread Here) (Thanks to Aou's)
4. Make a full Backup on TWRP just in Case. (Beware Touch screen will be Inverted on TWRP)(Right is left and left is right)
5. Go to REBOOT on TWRP and select DOWNLOAD , Open ODIN Select CP and Flash the G920T_UVU2COF8_BASEBAND.tar.md5. (Original Thread here) (Thanks to iB4STiD)
6. Go into TWRP WIPE/Advance WIPE and select dalvik cache, cache, data, system r/w (DON'T Select Internal Storage) Swipe to wipe.
7. Install Rapture 2.1 from Here. (Original Thread here) (Thanks to iB4STiD)
8. WIPE, Swipe Factory Reset
9. Wait 5-10 minutes first boot.
10. MAKE SURE to ENABLE AGAIN OEM Unlocking like you did the first time before you started the process so you don't have a problem later on with FRP LOCK.
11. ENJOY !!
It is recommended to Charge your phone to 100% and use a Battery Calibration, Restart your phone wait until it boots and remove the charger. Let it discharge until it turns off. Charge it again without interruption up to 100% and remove the charger and use it normally so the battery and system adapts.
In case of any problems you can Wipe and Restore from TWRP or ODIN STOCK 5.1.1 COF8 from HERE to fix any problems.
If you are on firmware COF6 with ONLY COF8 MODEM use the COF6 Odin from here.
Thanks for the write-up! Could you add how you updated from 5.0.2 to COF6? Its too bad fingerprint scanner doesn't work.
Billyvnilly said:
Thanks for the write-up! Could you add how you updated from 5.0.2 to COF6? Its too bad fingerprint scanner doesn't work.
Click to expand...
Click to collapse
Srry for the delay, i added it today the steps. I have been very busy lately creating a Custom ROM and kernel testing it.
Am I able to flash any custom rom using this method and still retain my warranty?
I flashed the ROM in the OP but now I have no sound making phone calls or receiving them.
GeorgeNYer said:
Am I able to flash any custom rom using this method and still retain my warranty?
Click to expand...
Click to collapse
Did you read the OP?
sent from my Hyperdrive powered G Note 10.1
The Apostle said:
Did you read the OP?
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
I'm just double checking, so can I?
Deleted
GeorgeNYer said:
I'm just double checking, so can I?
Click to expand...
Click to collapse
Did you flashed the Unikernel or Unistock latest? If not that is the audio problem.Yes it works with any released Custom rom. Currently i am using latest XtreStoLite Deo-Mod Edition 2.2 [478MB ○ BOGG](Thanks to edgarf18) and if you care for wifi calling xtrestolie doesnt have it. But you can install talkatone(example) can be any app that give you a US number and call fowarding to it when you dont have signal and have wifi and works the same.
Remember sboot or engi bootloader is for 920t or 925t.
It works now after flashing unikernel v6-0001rb. Thank you for finding a way go install custom roms without tripping Knox!!! Now there's still no way no make the fingerprint scanner to work?
GeorgeNYer said:
It works now after flashing unikernel v6-0001rb. Thank you for finding a way go install custom roms without tripping Knox!!! Now there's still no way no make the fingerprint scanner to work?
Click to expand...
Click to collapse
Nop there is no way. I am currently making a hybrid custom rom sometimes it works and sometime cratches... The problem lies in the bootloader invoking it a little diferent because its a 5.0.2 bootloader.
[MY SCREEN IS OPPOSITE] I may have installed something for the Edge variant, although I got lost in trying to get back to stock, which I currently am back at. (5.1.1)
So.... hoping this gets seen, I might xpost over to another thread, but here it goes.....
Notes: 5.1.1
920T model
Ultimately I am trying to get Alliance on my S6 (920T), and no I don't care if the know counter gets tripped (*spoiler* already done)
I started trying to get root for alliance ROM, and got the samsung splash lock after using odin to root. After re-loading the 5.1.1 firmware everything was working again, so I tried this *example* thread on how to install alliance again. After following things around and now have bizzaro phone, to where the opposite sides of the screen need to be pressed for the corresponding action, I am looking for help.....
What about aroma installer roms, can I flash them using this method without tripping the Knox counter?
So I'm all good running a custom ROM with Knox untripped, if I want to flash a different ROM I can just flash normally in twrp and it won't trip Knox?
GeorgeNYer said:
What about aroma installer roms, can I flash them using this method without tripping the Knox counter?
Click to expand...
Click to collapse
Not sure... alliance hasnt worked for me with this... Im going to try another tomorrow. I'll let you know....
If you need call audio or fingerprint scanner working just flash back to the stock F8 bootloader. You can always reflash to the engineering bootloader to flash more things down the line.
Edit: My mistake, seems this is not possible without tripping it.
Calnyx said:
If you need call audio or fingerprint scanner working just flash back to the stock F8 bootloader. You can always reflash to the engineering bootloader to flash more things down the line.
Click to expand...
Click to collapse
Just to make sure i am understanding right - after step 11, i can flash back a stock COF6/8 bootloader, and retain everything (root, custom ROM, etc) without tripping knox, so long as i dont try to flash anything further? I value my fingerprint scanner, and would love to not lose it and knox if at all possible. For future flashing, go back to the eng bootloader, flash, and then reflash the stock again?
If u flash Stock bootloader it will trip knox.
For the screen problem make sure you have unikernel v6.0001. If it doesnt work maybe you have the Aou twrp. Find the Twrp that is for 920t variant. If not fixed try *#2663# and select TSP FW UPDATE AND IT WILL get fixed.
Call audio gets fixed with unikernel... v6.0001
It will work for unified and 920/5t custom roms. I have tried them all and knox still 0x000 never flash stock bootloader with anything that is custom
... or u will trip knox.
Well, thats a bummer, but i figured as much; if it was as simple as flashing back, i figured people would have been doing it.
Still, thank you for the excellent guide. Followed it on my rooted 5.0.2, and everything worked as advertised. Have root, knox, and only fingerprint reader of course is busted (no huge loss)..
is this verified to work with COH8 without tripping KNOX?

M7 OTA : OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651. 10-6.23.651.7_R_release

Just got the notification for OTA update for m7 .
File name: OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10-6.23.651.7_R_release_452237.zip
Size: 189.61 mb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sprint Website
Download link
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers
tangojoker said:
Just got the notification for OTA update for m7 .
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers
Click to expand...
Click to collapse
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.
Won't this wipe everything?
jy04 said:
Won't this wipe everything?
Click to expand...
Click to collapse
I don't believe so. The OTA typically leaves the /data partition alone. Of course, as always, everything you do to your phone is at your own risk.
coal686 said:
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.
Click to expand...
Click to collapse
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk
This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.
So 6.23.651. 10 is not patched for "stagefright"?
Joshlul said:
This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.
Click to expand...
Click to collapse
Just updating the firmware to the previous version won't be enough to allow the update to work.
Most OTA updates, unless they are a full Rom update or RUU, contain patch files.
Those patch files will check the MD5 of every single system file before patching each one.
So even if your firmware is current or your build.prop is edited, to pretend like you have the last version, it will still fail when checking the system files it intends on patching.
There is no way to trick an OTA to work.
You have to have the proper system files, for them to patch at all or properly.
So don't waste your time on that...you need the previous stock Rom for the latest OTA to ever apply properly, or at all.
Good luck!!
Sent from my HTC6535LVW using Tapatalk
links broken can anyone post the OTA update zip like ,i'm rooted with twrp recovery with s-on
santod040 said:
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)
chrishonson said:
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)
Click to expand...
Click to collapse
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk
I can't post links yet so pm me if anyone wants the link.
The funny thing about this rom is that TWRP didn't root it like i expected it would. It installed SuperSU but "There is no SU binary installed, and SuperSU cannnot install it..."
Maybe I'm missing something.
santod040 said:
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
having a similar issue. relocked and RUU'd using last release. For some reason my OTA fails. I found some other guidance that said to extract the stock recovery from the OTA and flash it then run the OTA again, but for some reason I can't extract recovery from firmware. If anyone can post it, I'd like give that method a try. Thanks!
yeah so twrp-2.8.7 wasn't able to flash super su binary in a way that would stick. twrp-2.8.6 worked fine. I think may have seen this issue elsewhere.

Categories

Resources