Hello everyone,
I hate to be the person that joins a forum with an immediate question without having contributed anything previously, but here it goes: looking for some advice from experts on this one. I have an AT&T Galaxy S4 i337 that I recently updated to KitKat 4.4.2 - worst mistake I've ever made, not only do I have constant problems getting GPS locks now, perhaps the most aggravating issue is slow charging. It can take upwards of 7 hours to charge to 100% and I've tried everything including new cable and new battery. The phone can be plugged in and charging and still discharge until it dies. This issue surfaced immediately after I updated and, based on other information I've seen on XDA and other forums, it seems entirely probable this is a software issue since a lot of people seem to have the same problem. Plus, I'm getting tired of TouchWiz.
So I've decided to go towards SlimKat custom ROM hopefully to rectify some of these issues. However, I've had major problems at every step especially being on 4.4.2 (and what I believe is the newer firmware MF3?). Here is a summary of what I've done:
1) Tried rooting the phone through the XDA tutorial on this subforum where you use Motochopper, CF root and all of that, I forget the exact issue but it never worked. I tried for quite a long time.
2) I finally got the device rooted through Towelroot, which I had suspicions about because it was so easy and quick, but after installing SuperSU and RootChecker it's working like a charm!
3) Installed TWRP without success through GooManager... it would download and hang or say successfully installed but wouldn't ever boot into recovery.
4) Tried installing SafeStrap and as soon as I downloaded the lastest version and tried to install it from the app/GUI it would say install successful but the state would be listed as Not Installed
5) Moved onto ClockWorkMod which I had success with in the past on my Samsung Vibrant and CyanogenMod several years ago. I tried flashing recovery from the app and while it says it's sucessfully installed, once again I boot into recovery and I get an blue Andriod for a split second then a dead looking Andriod with a No Command error given. It boots into stock recovery, and it has the custom unlock logo under the samsung POST (or bootup) screen but won't launch ClockWorkMod.
So that brings me to where I am at now. I got the latest GS4 drivers from Samsung, made sure Kies was not installed, went through countless processes/cables USB ports (made sure they weren't hubs obviously) and I keep getting the same error when I try flashing ClockWorkMod for the i337 right from Odin3. I get:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
or
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I know the Galaxy S4 i337 from AT&T especially with KitKat 4.4 is notoriously hard to root but I'm on my last nerve with this phone, I wouldn't be so frustrated if the stock OS didn't have so many issues with the update. When in Odin, I tried getting an SGH-i337 16GB PIT file and still got an error so that's not working either. No idea where to go from now, and sick and tired of waiting for AT&T, Google, and Samsung to come out with a fix and network-pushed update.
Please help!!! :fingers-crossed:
Nati0n said:
Hello everyone,
I hate to be the person that joins a forum with an immediate question without having contributed anything previously, but here it goes: looking for some advice from experts on this one. I have an AT&T Galaxy S4 i337 that I recently updated to KitKat 4.4.2 - worst mistake I've ever made, not only do I have constant problems getting GPS locks now, perhaps the most aggravating issue is slow charging. It can take upwards of 7 hours to charge to 100% and I've tried everything including new cable and new battery. This issue surfaced immediately after I updated and, based on other information I've seen on XDA and other forums, it seems entirely probable this is a software issue since a lot of people seem to have the same problem. Plus, I'm getting tired of TouchWiz.
So I've decided to go towards SlimKat custom ROM hopefully to rectify some of these issues. However, I've had major problems at every step especially being on 4.4.2 (and what I believe is the newer firmware MF3?). Here is a summary of what I've done:
1) Tried rooting the phone through the XDA tutorial on this subforum where you use Motochopper, CF root and all of that, I forget the exact issue but it never worked. I tried for quite a long time.
2) I finally got the device rooted through Towelroot, which I had suspicions about because it was so easy and quick, but after installing SuperSU and RootChecker it's working like a charm!
3) Installed TWRP without success through GooManager... it would download and hang or say successfully installed but wouldn't ever boot into recovery.
4) Tried installing SafeStrap and as soon as I downloaded the lastest version and tried to install it from the app/GUI it would say install successful but the state would be listed as Not Installed
5) Moved onto ClockWorkMod which I had success with in the past on my Samsung Vibrant and CyanogenMod several years ago. I tried flashing recovery from the app and while it says it's sucessfully installed, once again I boot into recovery and I get an blue Andriod for a split second then a dead looking Andriod with a No Command error given. It boots into stock recovery, and it has the custom unlock logo under the samsung POST (or bootup) screen but won't launch ClockWorkMod.
So that brings me to where I am at now. I got the latest GS4 drivers from Samsung, made sure Kies was not installed, went through countless processes/cables USB ports (made sure they weren't hubs obviously) and I keep getting the same error when I try flashing ClockWorkMod for the i337 right from Odin3. I get:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
or
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I know the Galaxy S4 i337 from AT&T especially with KitKat 4.4 is notoriously hard to root but I'm on my last nerve with this phone, I wouldn't be so frustrated if the stock OS didn't have so many issues with the update. When in Odin, I tried getting an SGH-i337 16GB PIT file and still got an error so that's not working either. No idea where to go from now, and sick and tired of waiting for AT&T, Google, and Samsung to come out with a fix and network-pushed update.
Please help!!! :fingers-crossed:
Click to expand...
Click to collapse
SGH-i337 has a locked bootloader. That prevents us from replacing the stock kernel and recovery. The only working recovery we have is safestrap.
The bootloader also prevents a downgrade unless the versions are compatible. NB1 and NC1 are compatible and so you should be able to flash the stock NB1 firmware using Odin.
Since you have root already, you can install safestrap after setting SELinux to permissive mode. Use the selinuxmodechanger app from play store for that.
All things AT&T thread.
So I would have to downgrade to compatible NB1 using ODIN (once I do the step you described) and then from there could I flash a custom ROM such as SlimKat? Would safestrap work in NB1 even though it doesn't work in the current firmware?
Nati0n said:
So I would have to downgrade to compatible NB1 using ODIN (once I do the step you described) and then from there could I flash a custom ROM such as SlimKat? Would safestrap work in NB1 even though it doesn't work in the current firmware?
Click to expand...
Click to collapse
Since you successfully rooted with towel root, I guess your firmware is NC1.
You do not need to downgrade to NB1. Your safestrap version should be 3.72. Are you sure your safestrap is not working. To go to the safestrap you simply restart your phone. You do not need to go the recovery mode.
You have locked bootloader so you can not use the custom kernel or AOSP rom like Slimkat. You can only use the TOUCHWIZ roms.
sway8966 said:
Since you successfully rooted with towel root, I guess your firmware is NC1.
You do not need to downgrade to NB1. Your safestrap version should be 3.72. Are you sure your safestrap is not working. To go to the safestrap you simply restart your phone. You do not need to go the recovery mode.
You have locked bootloader so you can not use the custom kernel or AOSP rom like Slimkat. You can only use the TOUCHWIZ roms.
Click to expand...
Click to collapse
Can you help me? I am trying to factory reset my galaxy s4 that is rooted with towelroot to sell on ebay. When I reset it, it saids "ATT detected software not authorized for phone", and it doesn't reset. Anyway to do this?
patstar5 said:
Can you help me? I am trying to factory reset my galaxy s4 that is rooted with towelroot to sell on ebay. When I reset it, it saids "ATT detected software not authorized for phone", and it doesn't reset. Anyway to do this?
Click to expand...
Click to collapse
Flash nb1 firmware using odin
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
Flash nb1 firmware using odin
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok,following instructions here: www.androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html?m=1
Internet is really slow, 1mbps, so started 2.2gb file download and will try it when it finishes downloading, probably tomorrow. Going to post here if it works. Well, July 4th, going to do fireworks later on. Happy Independence day for all of you in U.S!
patstar5 said:
Ok,following instructions here: www.androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html?m=1
Internet is really slow, 1mbps, so started 2.2gb file download and will try it when it finishes downloading, probably tomorrow. Going to post here if it works. Well, July 4th, going to do fireworks later on. Happy Independence day for all of you in U.S!
Click to expand...
Click to collapse
Remember what I already mentioned. Since you are on NC1, you can only flash NB1 (as they are compatible and we dont have a full NC1 tar file). You cannot flash MK2.
sway8966 said:
Since you successfully rooted with towel root, I guess your firmware is NC1.
You do not need to downgrade to NB1. Your safestrap version should be 3.72. Are you sure your safestrap is not working. To go to the safestrap you simply restart your phone. You do not need to go the recovery mode.
You have locked bootloader so you can not use the custom kernel or AOSP rom like Slimkat. You can only use the TOUCHWIZ roms.
Click to expand...
Click to collapse
Ah okay understood, thanks for linking me to that thread I will look through those Touchwiz based roms. I was hoping to go to a Google Play Edition ROM too but from what I'm reading a lot of things don't work on it.
Thanks again everyone for your knowledge and advice. In reality do you think flashing a custom Touchwiz based ROM will address my issues or should I just downgrade to NB1? And is there REALLY no way to unlock the S4 bootloader on GSM devices? I thought someone did it on a CDMA version recently.
UPDATE: I should have reread the first post, after installing SELinuxModeChanger and setting it to permissive, I was able to get SafeStrap to install and boot properly.
You need to have selinux in permissive mode. Use selinuxmodechanger app for that.
jmjoyas said:
Remember what I already mentioned. Since you are on NC1, you can only flash NB1 (as they are compatible and we dont have a full NC1 tar file). You cannot flash MK2.
Click to expand...
Click to collapse
OK, downloaded first file here:http://forum.xda-developers.com/showthread.php?t=2674223
After flashing, I can do OTA update to get one NC1?
Yeah with the combination of TowelRoot, SELinuxModeChanger, and SafeStrap I now have a rooted phone with a recovery installed, what ROMs do you guys recommend that are TouchWiz based for the i337 NC1? I'm looking through the list and not seeing much.
Nati0n said:
Yeah with the combination of TowelRoot, SELinuxModeChanger, and SafeStrap I now have a rooted phone with a recovery installed, what ROMs do you guys recommend that are TouchWiz based for the i337 NC1? I'm looking through the list and not seeing much.
Click to expand...
Click to collapse
All the ROMs listed in the all things at thread will work.
Yeah, with hesitation I ended up going with a Google Play Edition ROM to get rid of touchwiz and man did it work well, my only minor annoyances are wifi (as was warned) and the face that MMS pictures are compressed WAY too much when I send them. The charging issue got marginally better but the battery lasts a lot longer without bloatware and the interface is super sleek.
Nati0n said:
Yeah, with hesitation I ended up going with a Google Play Edition ROM to get rid of touchwiz and man did it work well, my only minor annoyances are wifi (as was warned) and the face that MMS pictures are compressed WAY too much when I send them. The charging issue got marginally better but the battery lasts a lot longer without bloatware and the interface is super sleek.
Click to expand...
Click to collapse
Every time you reboot the phone, you will lose WiFi. You can recover it by soft rebooting the phone.
s4 recovery issues
Nati0n said:
Yeah with the combination of TowelRoot, SELinuxModeChanger, and SafeStrap I now have a rooted phone with a recovery installed, what ROMs do you guys recommend that are TouchWiz based for the i337 NC1? I'm looking through the list and not seeing much.
Click to expand...
Click to collapse
could you tell me the steps you took? i'm stuck with a rooted samsung s4 also. this is my phones info. i would appreciate the help. many thanks will come your way.
Related
Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2
After spending a few hours here on XDA both searching the site and posting on the help thread, I've come to no solution.
So yesterday due to a level of frustration with the amount of bloat that comes pre-installed on the Samsung devices, I decided I would try to set up a custom rom. I've used the Towelroot site to root the device (enable superuser access and disable Knox,) But wasn't able to install CWM. I've downloaded and installed the CWM Rom Manager and inside that app is an option to install CWM manually. Of course it isn't that easy, because although it says it's installed the recovery, when I boot into recover mode, it is still the stock android recovery mode.
So I turned to Odin. Specifically Odin 3.09. This is where the problems start. I start my phone and enable download mode. The phone is recognized by Odin and I choose the CWM file I have (recover-clockwork-touch-6.0.4.4-jflteatt.tar.) I press start and the process begins, but before long I see FAIL! in red at the top
The message box reads as follows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've tried using three different usb cables (including the stock s4 cable included in the packaging) and several different ports of course to no avail.
What exactly does FAIL! (Auth) mean? That seems to be the point where it goes south.
Could I be flashing a bad file? Is the CWM.tar.md5 not the correct file to flash?
I've tried several different versions of both Odin and CWM. Is there something else that I have to do before this step? I've read a lot about the S4 being a pain to load custom roms onto.
Anyways if anyone has a fix to this particular solution then let me know. Otherwise I'll take really any other viable solution to enabling custom roms on the Galaxy S4 for ATT. I'd like this to be a thread that people see when they google search it, so I won't give up and I'll be sure to post with the best process that I can find!
Your boot loader is locked. So, no custom recovery and kernel. The only working recovery we have is safestrap.
More info - http://forum.xda-developers.com/showthread.php?t=2616221
misterbreadcrum said:
Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2!
Click to expand...
Click to collapse
I see this above but need more info... Are you completely stock right now?
You will NOT be able to Odin any CWM to this phone. See below for other brief info for you to look into for CWM/TWRPand how to install IF on MDB or MDL firmware. Or if MF3 Your ONLY OPTION is Safestrap and limited to TouchWiz based Roms.
If you are then when you go to Settings/More/About Phone what does your Baseband say? Does it end with MDB, MDL, MF3?
IF it ends with MDB or MDL the look up Casual Root with TWRP. This will allow you to flash ANY Roms.
IF it ends with MF3 Then look up Safestrap for MF3. This will allow you to flash Safestrap versions of Roms.
ALSO IF it is MF3 you might as well update to MK2 or NB1 then use their safestrap version for root
Sent fron I337 Red BadAss Themed ShoStock 7.0
Hey so one of my friends is having problems getting their S4 to boot. Currently she has K0T49H.L720VPUFNAE on her S4. She has no custom recovery, but did have the phone rooted. Now the device can't boot. It gets past the Samsung Galaxy S4 screen and then goes black, the blue notification light pulses, and the phone makes a beep (almost like the initial boot sound) and then just hangs there. I've tried to odin back to stock, but I receive "failed! (Auth) almost immediately after starting.
On the Samsung Galaxy S4 screen both "Kernel is not seandroid enforcing" & "Warranty bit: kernel" are displayed in the top corner.
I can boot into stock recovery & download mode.
Any help would be appreciated!
It sounds like you are trying to Odin an older version on there than NAE. You cant downgrade, only can flash the NAE tar or the newer NG2.
Download it here, and try flashing it instead. After you flash, if it still wont boot, boot into recovery mode and do a factory reset.
random45 said:
It sounds like you are trying to Odin an older version on there than NAE. You cant downgrade, only can flash the NAE tar or the newer NG2.
Download it here, and try flashing it instead. After you flash, if it still wont boot, boot into recovery mode and do a factory reset.
Click to expand...
Click to collapse
I am trying to flash NAE tar and have tried the NG2. Both result in the errors mentioned above.
I also have gone into stock recovery and performed a factory reset.
Joey43 said:
I am trying to flash NAE tar and have tried the NG2. Both result in the errors mentioned above.
I also have gone into stock recovery and performed a factory reset.
Click to expand...
Click to collapse
can you post the log from odin? Also what version of odin are you using? have you tried flashing Phil's Recovery and maybe just installing a ROM?
random45 said:
can you post the log from odin? Also what version of odin are you using? have you tried flashing Phil's Recovery and maybe just installing a ROM?
Click to expand...
Click to collapse
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
There's the log. I can't install a custom recovery either. It acts like it is installing correctly, but when it reboots it is still stock recovery.
Joey43 said:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
There's the log. I can't install a custom recovery either. It acts like it is installing correctly, but when it reboots it is still stock recovery.
Click to expand...
Click to collapse
what version of odin are you using?
random45 said:
what version of odin are you using?
Click to expand...
Click to collapse
Oh, sorry. I've tried both 3.07 & 3.09
Joey43 said:
Oh, sorry. I've tried both 3.07 & 3.09
Click to expand...
Click to collapse
Okay, its really strange honestly. I spent sometime looking online for possible solutions, and the only thing I can come up with is:
1. make sure you are using the usb cable that came with the phone, and that it is undamaged
2. if its a desktop, make sure the usb cable is connected on the back. if you have usb 3.0 ports try it on there
3. some people say odin and kies dont get along. I do not share this experience, but who knows, doesnt hurt to try uninstalling kies, and install phone drivers
How did this happen by the way?
random45 said:
Okay, its really strange honestly. I spent sometime looking online for possible solutions, and the only thing I can come up with is:
1. make sure you are using the usb cable that came with the phone, and that it is undamaged
2. if its a desktop, make sure the usb cable is connected on the back. if you have usb 3.0 ports try it on there
3. some people say odin and kies dont get along. I do not share this experience, but who knows, doesnt hurt to try uninstalling kies, and install phone drivers
How did this happen by the way?
Click to expand...
Click to collapse
I'm using my S3 cable since her OEM one is broken. I tried around 4 different cables since I had the same thought. I never had kies installed and I did install the drivers.
I have really awful internet stability and speed (like 100kbs) so I'm hoping that the download is just corrupted and I'm just trying to re-download it.
I honestly don't know, she gave it to her brother to look at first, whom I suspect made the issue worse. I'm usually pretty good at fixing these things and I thought that it was an easy fix since it could reach download mode. I really appreciate all the help still.
have you tried flashing a pit file?
here is a 16 GB Sprint L720 NAE pit file you can try. do that with caution, and as a last resort.
Joey43 said:
I'm using my S3 cable since her OEM one is broken. I tried around 4 different cables since I had the same thought. I never had kies installed and I did install the drivers.
I have really awful internet stability and speed (like 100kbs) so I'm hoping that the download is just corrupted and I'm just trying to re-download it.
I honestly don't know, she gave it to her brother to look at first, whom I suspect made the issue worse. I'm usually pretty good at fixing these things and I thought that it was an easy fix since it could reach download mode. I really appreciate all the help still.
Click to expand...
Click to collapse
random45 said:
have you tried flashing a pit file?
here is a 16 GB Sprint L720 NAE pit file you can try. do that with caution, and as a last resort.
Click to expand...
Click to collapse
I tried that and received a "secure check fail: PIT" error. Phone performs the same as before.
i think the phone's busted....maybe try sending it to that one place that can jtag phones?
I think this is the site, but dont hold me to it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair/
random45 said:
i think the phone's busted....maybe try sending it to that one place that can jtag phones?
I think this is the site, but dont hold me to it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair/
Click to expand...
Click to collapse
I got philz custom recovery finally, and was able to flash NG2 pre-rooted, but the baseband version is old and wifi/data isn't working. I'm trying to flash the NG2 Modem.tar under the phone tab in odin, but i receive fail auth still and secure check fail: apnhlos.
I'm currently pursuing .tar to flashable .zip python converters, because it seems I cannot flash anything but one specific version of philz recovery in odin, but can flash anything through custom recovery.
Joey43 said:
I got philz custom recovery finally, and was able to flash NG2 pre-rooted, but the baseband version is old and wifi/data isn't working. I'm trying to flash the NG2 Modem.tar under the phone tab in odin, but i receive fail auth still and secure check fail: apnhlos.
I'm currently pursuing .tar to flashable .zip python converters, because it seems I cannot flash anything but one specific version of philz recovery in odin, but can flash anything through custom recovery.
Click to expand...
Click to collapse
Okay, so your making some progress.
random45 said:
Okay, so your making some progress.
Click to expand...
Click to collapse
where can i get that philz recovery im goin thru the same thang
I don't have this phone anymore. Good luck.
Sent from my SM-N910P using Tapatalk
To be honest TWRP is your better option for recovery on the S4 (I was a staunch supporter of Philz on my S3) one thing you need to make sure when you flash TWRP it to uncheck the auto reboot option. When flash completes, unplug and pull battery and then boot directly into recovery, then it sticks. You may be having WiFi/data issues because of your baseband/ROM combo. Have you tried flashing the latest stock?
Need Help Device stuck After flash?
I have the sprint sph l720t model. I finally acquired root access. I tried to flash Cyogenmod. When I did, it finished and rebooted and a after reboot it says cyogen mod in a circle that just keeps on spinning. I tried to get back to my blue team win screen into recovery but no luck. I got the phone to go into download mode once. I do have backups on my SD card with all the files can I flash a backup? What can I do?? The recovery says in red kernel is not se enforcing then under that in yellow set warranty bit: kernel? Can I use odin to do something in download mode to get my device back up?? I did refash my MD.5 file again from chainfire no luck! Help? Thanks
mattzeller said:
To be honest TWRP is your better option for recovery on the S4 (I was a staunch supporter of Philz on my S3) one thing you need to make sure when you flash TWRP it to uncheck the auto reboot option. When flash completes, unplug and pull battery and then boot directly into recovery, then it sticks. You may be having WiFi/data issues because of your baseband/ROM combo. Have you tried flashing the latest stock?
Click to expand...
Click to collapse
Yes I am now running Lollipop 5.0.1. I also did finally get TWRP installed. Everything is back to normaral. I re-installed the firmware from sam mobile. I then ofcoarse, went and flashed cf-autoroot with Odin. I pulled the batterry this time and booted up into recovery. Somehow everything is working and I do have recovery somewhere in my device. I want to try another Rom but Honestly TWRP makes me nervous evertime I open the app! What should I try next. Its just like factory rom with root but not really root. Its weird. At suggestios would be cool.. Thanks
EngineManShawn said:
Yes I am now running Lollipop 5.0.1. I also did finally get TWRP installed. Everything is back to normaral. I re-installed the firmware from sam mobile. I then ofcoarse, went and flashed cf-autoroot with Odin. I pulled the batterry this time and booted up into recovery. Somehow everything is working and I do have recovery somewhere in my device. I want to try another Rom but Honestly TWRP makes me nervous evertime I open the app! What should I try next. Its just like factory rom with root but not really root. Its weird. At suggestios would be cool.. Thanks
Click to expand...
Click to collapse
You have a lot of options now that you are presumably on the latest baseband. Just download the ROM you want, copy it to your external SD card and flash in TWRP.
If you like TouchWiz I suggest Wicked X:
http://forum.xda-developers.com/showthread.php?t=3115583
It's a fairly modified TW ROM, with quite a few mods that you can apply as you see fit. The developer is fantastic, quick to support and address issues. Every time he changes devices, I change to that device, he's that good. I've been stalking him since his time developing for the S2.
If TW isn't your thing, I suggest BlissPop:
http://forum.xda-developers.com/showthread.php?p=62018060
When I'm not running Wicked X I'm running BlissPop. The only caveat is I have not been able to get data to work properly on the latest builds, but the experimental build from 9/28 that I run is flawless. If you can't find it on their page, let me know I have it up on Mega.
Neither one is better than the other, it just a matter of preference. They both have great battery life, especially when paired with Greenify.
Okay so to keep it brief, I am on alliance rom v5.3, running kitkat 4.4.2 on my Samsung S5, recently Lollipop has come out and I would like to update.
this was my first custom romming so needless to say I'm kinda scared, I am pretty sure I can find out how to flash to another custom rom but how would I go about getting to the default so that I can accept normal update? or is there a custom rom that is usually kept updated? (I am a sucker for having the latest version of things)
Also is there anything I should know about going from one custom rom that is rooted to another? or is it exactly like going from stock to custom?
DarkVamprism said:
Okay so to keep it brief, I am on alliance rom v5.3, running kitkat 4.4.2 on my Samsung S5, recently Lollipop has come out and I would like to update.
this was my first custom romming so needless to say I'm kinda scared, I am pretty sure I can find out how to flash to another custom rom but how would I go about getting to the default so that I can accept normal update? or is there a custom rom that is usually kept updated? (I am a sucker for having the latest version of things)
Also is there anything I should know about going from one custom rom that is rooted to another? or is it exactly like going from stock to custom?
Click to expand...
Click to collapse
just look for stock lollipop rom for your phone ( sammobile)/and flash with odin, just make sure to do a full wipe before flashing the stock rom
Thanks for the quick reply, will this allow me to get future updates? like hotfixes released and stuff? I saw somewhere that once you flash it does something to the kernal which makes updates possibly brick the phone.
Just factory reset the custom, then use ODIN to flash the Stock ROM
Flashing the stock ROM will allow OTA updates so long as you don't root or flash anything else custom like recovery - it needs to stay 100% stock for OTA
But you can still root, and each time an OTA arrives, grab the new ROM from sammobile dot com and use ODIN to flash it, that will update your phone, leaving everything in tact, all your data and images etc will be fine, only thing you'll need to do after updating is root the phone again
Thank you both, I have found my phone model on sammobile but the list of firmwares there is no Australian firmwares(Im Australian) or even any US firmares, the only primarily english firmware that I can see on the list is for the united kingdom? are those what I use or am I missing something? Sorry if I should know this =\
Edit: it shows that I have the G900F under Model number in the settings.
DarkVamprism said:
Thank you both, I have found my phone model on sammobile but the list of firmwares there is no Australian firmwares(Im Australian) or even any US firmares, the only primarily english firmware that I can see on the list is for the united kingdom? are those what I use or am I missing something? Sorry if I should know this =\
Edit: it shows that I have the G900F under Model number in the settings.
Click to expand...
Click to collapse
Try a UK firmware, the latest version BOE5 is in my sig link on MEGA, much faster than Sammobile
There is also samsung-updates dot com you can check out
Sorry to bug you but im getting errors when trying to use odin, im getting "Secure check fail : aboot" on my phone and the following on odin
Code:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
Looking up the codes I see stuff about having the wrong boot loader and to flash a different boot loader and modem and that its impossible to get with others saying its possible but should never be done, then others saying that I need to turn off reactivation lock.
At this stage I have factory reset it(it automatically booted after so I turned off) and I downloaded your G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5 file and put that in the AP section of odin.
DarkVamprism said:
Sorry to bug you but im getting errors when trying to use odin, im getting "Secure check fail : aboot" on my phone and the following on odin
Code:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
Looking up the codes I see stuff about having the wrong boot loader and to flash a different boot loader and modem and that its impossible to get with others saying its possible but should never be done, then others saying that I need to turn off reactivation lock.
At this stage I have factory reset it(it automatically booted after so I turned off) and I downloaded your G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5 file and put that in the AP section of odin.
Click to expand...
Click to collapse
Are you sure you had the phone in Download Mode?
Volume DOWN & HOME & POWER (Then volume up when asked)
And yes, disable Reactivation lock before flashing anything or you'll end up with major problems requiring a massive mess on to fix
Using ODIN 3.10.6 ?
think you need pitfiles with the rom
Yea it was in download mode and I have never heard of this reactivation thing :S the instructions I read had nothing like that in there, any other settings I should change? luckily it booted fine so ill look into changing that.
Edit: Using Odin 3.09 Also I checked and reactivation was disabled.
ad0dh67 said:
think you need pitfiles with the rom
Click to expand...
Click to collapse
Yea I was wondering the same
Try this OP
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Load it into the PIT section along with the ROM in the AP section together and try again
---------- Post added at 19:14 ---------- Previous post was at 19:12 ----------
DarkVamprism said:
Yea it was in download mode and I have never heard of this reactivation thing :S the instructions I read had nothing like that in there, any other settings I should change? luckily it booted fine so ill look into changing that.
Edit: Using Odin 3.09 Also I checked and reactivation was disabled.
Click to expand...
Click to collapse
Here's the latest ODIN
https://mega.co.nz/#!Exo3yADS!y7pFS5-9RVhp4vDxTRAQARAwkjyQAB_9mDZWfXkLqko
There is no pit section inside of Odin 3.10?
Edit: Nevermind I found it but it says not to use it unless im an engineer, how badly will this screw me up =\ Im kind of scared to.
DarkVamprism said:
There is no pit section inside of Odin 3.10?
Click to expand...
Click to collapse
There is on the lower left log / options / PIT section, although clicking that says to load it into the CSC section
Try using the PIT file with your 3.09 version of ODIN first as Im not sure where 3.10.6 wants the PIT file loaded into, it's not very clear
Okay in 3.09 there is a pit up the top where I can put it but but there is also a csc? which one am I supposed to put it in?
DarkVamprism said:
Okay in 3.09 there is a pit up the top where I can put it but but there is also a csc? which one am I supposed to put it in?
Click to expand...
Click to collapse
Put it in the PIT section
I'm just reading up on what 3.10.6 means with that engineer warning
Make sure you load the stock ROM into AP together with the PIT file in the PIT section before flashing
I tried using the rom in the AP and the pit inside the PIT but now its saying secure check fail : pit =\
attempted with odin 3.09
DarkVamprism said:
I tried using the rom in the AP and the pit inside the PIT but now its saying secure check fail : pit =\
attempted with odin 3.09
Click to expand...
Click to collapse
Are you running ODIN as Admin? (Right click > Run as Administrator)
Using a native PC running Windows? All Samsung drivers installed?
It almost sounds as if your bootloader is locked, but you managed to flash custom recovery and root right?
Yea I do have custom recovery and a custom rom and had rooted it. although inside the about device section it said I was using G900F I noticed the download mode said G900I so I searched for my old box and on the box it says it is a G900I so I assume the rom I used modified the model number, could this be screwing with anything?
DarkVamprism said:
Yea I do have custom recovery and a custom rom and had rooted it. although inside the about device section it said I was using G900F I noticed the download mode said G900I so I searched for my old box and on the box it says it is a G900I so I assume the rom I used modified the model number, could this be screwing with anything?
Click to expand...
Click to collapse
Looks like you need to grab the G900I ROM and PIT
I'd try with just the ROM first, hopefully ODIN saved you from bricking when it realised it was for the wrong model phone
Get the G900I ROM, stick it into ODIN like you originally tried, see how you go from there
EDIT - Now it makes sense why there was no Australian ROM for your G900F, there is for the G900I
Okay, good news is sam mobile had the correct firmware now that im using the correct model number(doh) and the phone still boots fine, will update when I have downloaded and tried it, thanks for sticking with me.
My GS5 G900V is stuck to recovery mode while I was trying to root. My mistake was I used odin to flash it back to a older version to try to root it and I did not did my research I know im a dummy. Now its Soft brick. I looked around and looked around to find answers but nothing seems to work for me. Ive tried using odin again to flash it back to the current firmware but Odin does not work.
It will be stuck on the Samsung GS5 screen and will go straight to recovery mode. Ive tried wiping cache and restore to factory settings still did not work. Tried taking out the battery for some time still did not work. I tried flashing through sd card still did not work.
This is the current log I have. Been trying different things since last night. Nothing works.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Found this link here but not sure how to use it: http://forum.xda-developers.com/showthread.php?t=2446269
I saw one thread with my similar problems. I think this is how they fixed it but I do not know how to do it. Can someone tell me how to use it? It will be greatly appreciated.
Thanks for all the help!
j0mz said:
My GS5 G900V is stuck to recovery mode while I was trying to root. My mistake was I used odin to flash it back to a older version to try to root it and I did not did my research I know im a dummy. Now its Soft brick. I looked around and looked around to find answers but nothing seems to work for me. Ive tried using odin again to flash it back to the current firmware but Odin does not work.
It will be stuck on the Samsung GS5 screen and will go straight to recovery mode. Ive tried wiping cache and restore to factory settings still did not work. Tried taking out the battery for some time still did not work. I tried flashing through sd card still did not work.
This is the current log I have. Been trying different things since last night. Nothing works.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Found this link here but not sure how to use it: http://forum.xda-developers.com/showthread.php?t=2446269
I saw one thread with my similar problems. I think this is how they fixed it but I do not know how to do it. Can someone tell me how to use it? It will be greatly appreciated.
Thanks for all the help!
Click to expand...
Click to collapse
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
simplepinoi177 said:
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
Click to expand...
Click to collapse
I believe mine was on OD5
I cant use flashfire because my phone is stuck on recovery mode. I cant get pass that.
j0mz said:
I believe mine was on OD5
I cant use flashfire because my phone is stuck on recovery mode. I cant get pass that.
Click to expand...
Click to collapse
you don't use flashfire...
I'm not saying to do the whole thing on the first post...just NUMBER #4 IN THE NOTES...
You use Odin and the file given to unbrick your phone back to NCG...
again, just go to NOTES and do #4 to unbrick the phone. You should be safe/fine if you are on OD5. Don't forget to root again and install a superuser...
Then you can go here to install whatever version you are interested in... http://forum.xda-developers.com/showthread.php?t=2784880
simplepinoi177 said:
you don't use flashfire...
I'm not saying to do the whole thing on the first post...just NUMBER #4 IN THE NOTES...
You use Odin and the file given to unbrick your phone back to NCG...
again, just go to NOTES and do #4 to unbrick the phone. You should be safe/fine if you are on OD5. Don't forget to root again and install a superuser...
Then you can go here to install whatever version you are interested in... http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
I tried it but Odin cant find it. Its a rar file?
Stuck in recovery mode loop. SM-G900V Verizon G900VVRU2BOG5
Im in the exact same situation... i have been literally sitting in front of my PC for hours on end to try and resolve this issue. I cant get back my current firmware now even. Just stuck on the recovery mode. I flashed NCG kernal and it went through as normal, however, all it does not is after the samsung loading sign it goes back into system recovery. I have tried everything from cache wipe to factory reset, system reboot, everything! it just does the same thing - goes back into recovery mode- it is getting really frustrating for me. I would really appreciate it if someone could tell me exactly how to get out of it and use the phone as normal again.
I am on sm-g900v
G900VVRU2BOG5
Verizon mobile S5
I have tried to flash almost all the available ROMS and nothing works everytime this come up: ( i am using the latest Kies drivers, Odin 3.10.6, etc)..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping.. - - i have the pit file and if i use it to flash i get the same output failed completion.
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP. THANK YOU.
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
m0bk3yn1nj4 said:
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
Click to expand...
Click to collapse
can you boot into download mode? if go here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and flash the full NCG tar then re root your device remember you always wanna flash ni2 kernal or nk2 then flash the rom then the kernal that works with your rom never flash the kernel that works with your rom before you flash the rom
m0bk3yn1nj4 said:
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
Click to expand...
Click to collapse
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
Veid71 said:
can you boot into download mode? if go here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and flash the full NCG tar then re root your device remember you always wanna flash ni2 kernal or nk2 then flash the rom then the kernal that works with your rom never flash the kernel that works with your rom before you flash the rom
Click to expand...
Click to collapse
He said he was on the latest Lollipop version when he tried to root. If so, he cannot flash the NCG file. He wasn't already rooted, he was trying to root on the latest Lollipop build which can't be done at this time.
landshark68 said:
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
He said he was on the latest Lollipop version when he tried to root. If so, he cannot flash the NCG file. He wasn't already rooted, he was trying to root on the latest Lollipop build which can't be done at this time.
Click to expand...
Click to collapse
ah okay i see then his post was kinda confusing
I don't know how to do that ODIN stuff, is there a video guide out or something?
landshark68 said:
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
Click to expand...
Click to collapse
I have no idea what any of this means. Please, can you help me?!
m0bk3yn1nj4 said:
I don't know how to do that ODIN stuff, is there a video guide out or something?
Click to expand...
Click to collapse
m0bk3yn1nj4 said:
I have no idea what any of this means. Please, can you help me?!
Click to expand...
Click to collapse
No offense intended, but if you don't know how to use ODIN and you don't have any idea what any of what I wrote means, you shouldn't be trying to root your phone without understanding all of it. I'm not aware of a video guide for using ODIN but I'd be willing to bet you could probably find one on youtube. If you can't find a video guide, found in post #4 of this thread is an old picture guide that should give you a pretty good understanding of using ODIN:
http://forum.androidcentral.com/ver...=1.251820425.1215152510.1443888191#post542513
I believe the PDA button is now called the AP button. Follow the video guide you found or the attached picture guide and flash the full BOG5 ODIN tar file found in this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
There may even be a guide for using ODIN found here at XDA if you dig around some. Not sure.
landshark68 said:
No offense intended, but if you don't know how to use ODIN and you don't have any idea what any of what I wrote means, you shouldn't be trying to root your phone without understanding all of it. I'm not aware of a video guide for using ODIN but I'd be willing to bet you could probably find one on youtube. If you can't find a video guide, found in post #4 of this thread is an old picture guide that should give you a pretty good understanding of using ODIN:
http://forum.androidcentral.com/ver...=1.251820425.1215152510.1443888191#post542513
I believe the PDA button is now called the AP button. Follow the video guide you found or the attached picture guide and flash the full BOG5 ODIN tar file found in this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
There may even be a guide for using ODIN found here at XDA if you dig around some. Not sure.
Click to expand...
Click to collapse
Much obliged
simplepinoi177 said:
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
Click to expand...
Click to collapse
i have a sm-g900v BOG5. i bricked mine phone so i tried #4 as you said and get FAIL! in Odin. am i doing something wrong?
rachelrgr said:
i have a sm-g900v BOG5. i bricked mine phone so i tried #4 as you said and get FAIL! in Odin. am i doing something wrong?
Click to expand...
Click to collapse
You can grab the stock firmware, either OG5. OK3, or PB1 (newest), and flash with odin in the AP slot, I also recommend grabbing the PIT file (goes in the PIT slot). If you want root, then just go ahead and grab the PB1 and follow the directions on this link.
Firmware Link: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
So I'm trying to install TWRP on my Snapdragon Galaxy S8 so I can flash a ROM. The last device I rooted and got TWRP on was an old Nexus 7 2012, and this have clearly changed since then. Particularly the need for Odin on Samsung devices.
On my phone I get the error "SECURE CHECK FAIL : recovery"
I really don't understand, I've spent the last 3 hours trying to install it and have only run into issues. I eventually tried to just root the phone then easily install TWRP from there, but same issues, different message. Odin simply does not want to work. I'm using the PrinceComsy version, as I've read it was needed. Using the normal version gave me a different error entirely that's not found on the PriceComsy version of Odin. Trying to root led me to completely wipe my phone 4 times now trying, only to fail and restarting my phone wipes it. No matter where I've looked I have not found a solution. Low quality Youtube "fixes" didn't work. And others use the Exynos model which seemingly is much easier to work with in terms of rooting.
If anyone can help, it'd be much appreciated.
EDIT: Can't post an imgur link with a screenshot. Here is the error:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
[Automata] said:
So I'm trying to install TWRP on my Snapdragon Galaxy S8 so I can flash a ROM. The last device I rooted and got TWRP on was an old Nexus 7 2012, and this have clearly changed since then. Particularly the need for Odin on Samsung devices.
On my phone I get the error "SECURE CHECK FAIL : recovery"
I really don't understand, I've spent the last 3 hours trying to install it and have only run into issues. I eventually tried to just root the phone then easily install TWRP from there, but same issues, different message. Odin simply does not want to work. I'm using the PrinceComsy version, as I've read it was needed. Using the normal version gave me a different error entirely that's not found on the PriceComsy version of Odin. Trying to root led me to completely wipe my phone 4 times now trying, only to fail and restarting my phone wipes it. No matter where I've looked I have not found a solution. Low quality Youtube "fixes" didn't work. And others use the Exynos model which seemingly is much easier to work with in terms of rooting.
If anyone can help, it'd be much appreciated.
EDIT: Can't post an imgur link with a screenshot. Here is the error:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Is it a US snapdragon If so the bootloader is locked and you cannot flash twrp to it
TheMadScientist said:
Is it a US snapdragon If so the bootloader is locked and you cannot flash twrp to it
Click to expand...
Click to collapse
Unfortunately, it is US, and it is Snapdragon. I appreciate the quick answer. So is there no possible way to flash a ROM without TWRP? Or must the bootloader be unlocked for that?
[Automata] said:
Unfortunately, it is US, and it is Snapdragon. I appreciate the quick answer. So is there no possible way to flash a ROM without TWRP? Or must the bootloader be unlocked for that?
Click to expand...
Click to collapse
yes bootloader must be unlocked there is 1 rooted rom for it right now look in the dev section for partcyborg
it is rooted and can bassicly do anything except twrp and modify any boot images and such hence no twrp either
[Automata] said:
Unfortunately, it is US, and it is Snapdragon. I appreciate the quick answer. So is there no possible way to flash a ROM without TWRP? Or must the bootloader be unlocked for that?
Click to expand...
Click to collapse
as a side note, if your like me your used to using twrp for backup and restore features also. Chainfire created an app called flash fire (in app store) this app can be used to create backups and restore similar to twrp eventhough our bootloader is locked. It will also flash zips so xposed is possible (was a pain in the ass to implement for me, but possible. The trick was to download an apk of flashfire the exposed framework sdk24 v89 arm64 and the xposed installer and put it on my sd card so as soon as the phone was rooted and booted up I could immediately install flashfire and then flash the framework zip. for some reason if I waited till all the apps had been restored it would bootloop and I would have to start the whole root process over. Anyways thats not what you asked but I though it might be helpful
loopytee said:
as a side note, if your like me your used to using twrp for backup and restore features also. Chainfire created an app called flash fire (in app store) this app can be used to create backups and restore similar to twrp eventhough our bootloader is locked. It will also flash zips so xposed is possible (was a pain in the ass to implement for me, but possible. The trick was to download an apk of flashfire the exposed framework sdk24 v89 arm64 and the xposed installer and put it on my sd card so as soon as the phone was rooted and booted up I could immediately install flashfire and then flash the framework zip. for some reason if I waited till all the apps had been restored it would bootloop and I would have to start the whole root process over. Anyways thats not what you asked but I though it might be helpful
Click to expand...
Click to collapse
But also as another side note lol
That partcyborg had a issue restoring a full backup something hung up with the modems and caused a pretty good brick I believe.
So I would limmit it to backing up EFS,System,and User data for restores
TheMadScientist said:
But also as another side note lol
That partcyborg had a issue restoring a full backup something hung up with the modems and caused a pretty good brick I believe.
So I would limmit it to backing up EFS,System,and User data for restores
Click to expand...
Click to collapse
thank you thank you thank you for the clarification. I haven't tried a complete restore only user data and system. Very glad to know this!
TheMadScientist said:
But also as another side note lol
That partcyborg had a issue restoring a full backup something hung up with the modems and caused a pretty good brick I believe.
So I would limmit it to backing up EFS,System,and User data for restores
Click to expand...
Click to collapse
Yes this is true, but I add in param persist persistent and miscellanious as those have other useful state and can't brick you if flashing goes bad.
Basically take backups of everything (having a backup saved me from a perm brick) but don't restore anything you don't see in a stock rom (modemst1, modemst1, ssd, firmware) etc
TheMadScientist said:
yes bootloader must be unlocked there is 1 rooted rom for it right now look in the dev section for partcyborg
it is rooted and can bassicly do anything except twrp and modify any boot images and such hence no twrp either
Click to expand...
Click to collapse
Yeah I also learned this the hard way. I tried Installing TWRP on my S8 as well and didn't know I couldn't do it even though it was rooted with what you just mentioned. But it's a decent root I think personally.
Rocco210 said:
Yeah I also learned this the hard way. I tried Installing TWRP on my S8 as well and didn't know I couldn't do it even though it was rooted with what you just mentioned. But it's a decent root I think personally.
Click to expand...
Click to collapse
Yea. I have my system modded to the gills and I get decent batt life with my aggressive usage.
And yea even with root still have secure boot on recovery and kernel
TheMadScientist said:
Yea. I have my system modded to the gills and I get decent batt life with my aggressive usage.
And yea even with root still have secure boot on recovery and kernel
Click to expand...
Click to collapse
We don't have twrp for SM-G955U yet do we?
ShizNick said:
We don't have twrp for SM-G955U yet do we?
Click to expand...
Click to collapse
Nope
TheMadScientist said:
Nope
Click to expand...
Click to collapse
When do you think we will?
peachpuff said:
When do you think we will?
Click to expand...
Click to collapse
When ever we figure out how to unlock this marvelous boot-loader Sammy has made for us:good::good: