[Q] Need install-recovery.sh for AT&T I337UCUAMF3? - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I need the install-recovery.sh file found here on your I337-UCUAMF3. Must have root access.
/system/etc/install-recovery.sh
like an idiot, i didnt make a backup of that file, and I deleted it not realizing that there is no recovery for UCUAMF3 and tried to install a custom recovery.
Now I cant get into the normal recovery mode and gets stuck in odin mode, in order to boot up i have to do the restart option when i do a physical button boot into odin. its annoying and i want to go back to stock and wait until there is a bootloader unlock and recovery for UCUAMF3.
unfortunately I cant do a factory reset because during the reset process it boots back into odin mode, and recovery doesnt work.
my thinking is if i can get back this install-recovery.sh it will be able to do a factory reset? Also do I need to unroot to go back to factory settings? Any thoughts? Thanks again for any help, and yes ive learned my lesson, spend at least 20 minutes searching the EXACT model/baseband and make sure the guide is for your device..

You can't return to stock, there is no odin flashable firmware. Don't do anymore messing with your phone. You'll just make it worse. Your going to have to live with it the way it is until there is firmware available. As an alternative, best buy can flash it back to stock.
Edit, see this
http://forum.xda-developers.com/showthread.php?p=45359306

i cant just do a factory reset in settings? im pretty sure the problem is that it cant boot into the stock recovery because of the deletion of 'install-recovery.sh'
my phone once, already had the odin bootloop thing, then i fixed it so it could boot up normally, but thats because i still had the 'install-recovery.sh' on there...any chance you send that file my way? once i have that im pretty sure ill be able to do a factory reset and remove root.

jd1639 said:
Edit, see this
http://forum.xda-developers.com/showthread.php?p=45359306
Click to expand...
Click to collapse
read that, but their problem seems like their devices wont boot at all. mines does boot, and did normally when i had 'install-recovery.sh'
im pretty sure that file is device specific and varies from device, ive found the file but not one that was from an ATT S4 running UCUAMF3, there is already root access for UCUAMF3 so it someone should be able to copy that file since i was able to delete it?

I don't have mf3. What the f are you messing with stuff like that for when you're on mf3. You need to do some more research on the limitations of returning your device to stock if you mess something up. You're going to end up with an expensive brick.

jd1639 said:
You can't return to stock, there is no odin flashable firmware. Don't do anymore messing with your phone. You'll just make it worse. Your going to have to live with it the way it is until there is firmware available. As an alternative, best buy can flash it back to stock.
Edit, see this
http://forum.xda-developers.com/showthread.php?p=45359306
Click to expand...
Click to collapse
jd1639 said:
I don't have mf3. What the f are you messing with stuff like that for when you're on mf3. You need to do some more research on the limitations of returning your device to stock if you mess something up. You're going to end up with an expensive brick.
Click to expand...
Click to collapse
yeah it was an accident on my part....do you have i337? is there a difference at all between the 'install-recovery.sh' on i337 and i337 with mf3?
UPDATE: just did a power off and a reboot, phone booted fine into android, none of the odin-mode stuff..

also go here, it could help...
http://forum.xda-developers.com/showthread.php?t=2413746

Related

[Q] To brick or not to brick

Noob question... If i install clockwork recovery and do a nand backup, will i be able to restore my phone, no matter what i do to it (software-wise) or can i still brick it?
Im new to rooting and mods and im looking for a way out of trouble if i screw things up.
once you are done with the rooting process, and have clockwork installed as your recovery - it is very very difficult to brick your phone.
if you are dealing with the standard roms here - there is almost no way you can really screw up, to a point where you can't just go back to a functioning nandroid backup.
for further security - i copy my nandroids backups to PC, so if the sdcard ever gets toasted or corrupted - I will still have a good recovery image.
From what I hear you gotta do something really really stupid to brick your phone. If anything I think it's the rooting process that can brick your phone since there's no nandroid yet or if you don't do a proper procedure during a rom flash. Unrevoked makes it painless and easy. I suggest running Ubuntu then rooting because I had trouble with windows. Follow the guides and you're set =)
Edit: Here's the guide I used. Very easy and painless. http://forum.xda-developers.com/showthread.php?t=741824
really the only way i can see you bricking the phone is if you screw up flashing the recovery/radio or boot image.
Ok so if the power goes out when im flashing my phone its lost right? Even if i have my nand backup. And what about the warranty? If i flash back to my original backup and unroot, will anyone be able to tell i've been messing with my phone?
I don't know that "unrooting" is as easy as just removing the superuser app, and flashing back a stock recovery image. The best way to unroot - is to flash an RUU stock image (which includes the stock recovery, and unrooted system image)
you can find the stock at&t RUU from shipped-roms.com under "liberty"
dexmix said:
I don't know that "unrooting" is as easy as just removing the superuser app, and flashing back a stock recovery image. The best way to unroot - is to flash an RUU stock image (which includes the stock recovery, and unrooted system image)
you can find the stock at&t RUU from shipped-roms.com under "liberty"
Click to expand...
Click to collapse
So dumbing this back down to superNoob level, you're saying that I could root my phone and then put it back the way it was later so that AT&T/HTC would be none the wiser?
911jason said:
So dumbing this back down to superNoob level, you're saying that I could root my phone and then put it back the way it was later so that AT&T/HTC would be none the wiser?
Click to expand...
Click to collapse
yes.... you can go back to the un-rooted state at any time.... it is quite easy... i have tested this... it took me about five minutes to un-root my phone with the HTC RUU ... everything was stock with all the dang bloat ware and no root .... i then re-rooted and put a nandroid back up on that i made just before un-rooting...

[Q] I need I337UCUAMF3 official firmware

I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
I might be wrong here as im not the sharpest tool in the shed, but i do believe there is a new post like this every single day and all get the same response. There is no MF3 image available for flash through odin or otherwise. Search = Friend.
If you repeat three times "owaa tagoo siam" it might magically appear.
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
It seems useless
So did you try it or just say its useless? There are a couple other methods that have been shown to work as well.
Sent from my GT-I9505G using XDA Premium HD app
You are going to have to wait for Samsung to release the MF3 on kies or a leak of the tar to happen.
Sent from my GT-I9505G using Tapatalk 2
chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
salwansk said:
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
Click to expand...
Click to collapse
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
scott14719 said:
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
Click to expand...
Click to collapse
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
salwansk said:
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
Click to expand...
Click to collapse
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
scott14719 said:
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
Click to expand...
Click to collapse
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
salwansk said:
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
Click to expand...
Click to collapse
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
scott14719 said:
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
Click to expand...
Click to collapse
thanks bud, and yes i started read about this issue just today.
i know samsung is way easier than HTC when it comes to unlocking and flashing, thats why i didn't care at first. but what freaked me out when i tried to sim unlock galaxy s4 yesterday. today i found out about the MF3 and how is it pain in the axx :laugh: .... thanks for the info bro :good:
add myself to the thread for future fixes...
Scott that was probably the best explanation I have seen yet. You should have it pinned lol
Sent from my GT-I9505G using XDA Premium HD app
agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
Well Thank YOU ALOT.. you saved me TONS OF WORRIES. That trick got me out of a boot -> recovery -> odin mode loop. I thought I was going to have to confess to ATT and beg for them to fix my phone. I wont be touching my recovery again for a while. Not until a confirmed method and hugely tested recovery/custom rom method comes out.
Thank you! I knew that little bit of advice would help somebody one day.

How to return phone to bone stock?

Anyone have a set of instructions or a link to returning my phone to completely bone stock? I know I can flash an unrooted and stock firmware, but the bootloader will still be unlocked. I need to RMA my phone and the store has turned me away in the past for having a modified firmware or bootloader.
wotan2525 said:
Anyone have a set of instructions or a link to returning my phone to completely bone stock? I know I can flash an unrooted and stock firmware, but the bootloader will still be unlocked. I need to RMA my phone and the store has turned me away in the past for having a modified firmware or bootloader.
Click to expand...
Click to collapse
The boot loader is not locked stock, so that's not a problem. Simply download the MF9 firmware and install using odin. Perform a factory reset in the stock recovery. Then use Triangleaway to reset the flash counter and you will be stock with no signs of tampering.
cruise350 said:
The boot loader is not locked stock, so that's not a problem. Simply download the MF9 firmware and install using odin. Perform a factory reset in the stock recovery. Then use Triangleaway to reset the flash counter and you will be stock with no signs of tampering.
Click to expand...
Click to collapse
dont you have to be rooted to use TriangleAway? I would assume that using Odin to go back to MF9 would cause you to lose root, no?
Correct. You need to be rooted for TA.
What I'd do is use TA first. Then use Odin to install MF9 (or one of the older stock rom's). If the download screen still says custom, do another RTN/Factory Reset. That should clean it all up.
You could also try to just flash the stock recovery. Then run TA and see if that resets it all to Official on the Download screen. If it does, all you should need to do from there is Full Unroot from the SuperUser app.
wotan2525 said:
Anyone have a set of instructions or a link to returning my phone to completely bone stock? I know I can flash an unrooted and stock firmware, but the bootloader will still be unlocked. I need to RMA my phone and the store has turned me away in the past for having a modified firmware or bootloader.
Click to expand...
Click to collapse
Go here: http://www.sxtpdevelopers.com/showthread.php?t=231
Download the ODIN one click for SPH-L720_MDC_Stock_Restore.exe and follow the instructions on that site.
Puts you back at original release and then if you want, you can update through Sprint for the two upgrades you'll need to get back to MF9. You'll have everything back to stock, no counter trips and everything back at zero. I wish they made the ODIN one clicks for MF9, they're so easy.
mmark27 said:
Go here: http://www.sxtpdevelopers.com/showthread.php?t=231
Download the ODIN one click for SPH-L720_MDC_Stock_Restore.exe and follow the instructions on that site.
Puts you back at original release and then if you want, you can update through Sprint for the two upgrades you'll need to get back to MF9. You'll have everything back to stock, no counter trips and everything back at zero. I wish they made the ODIN one clicks for MF9, they're so easy.
Click to expand...
Click to collapse
Thank you! This is what I needed....
Coming from the Galaxy S2, it seemed like there were a million 1-click ODINS. Any idea why the S4 doesn't have these?
wotan2525 said:
Thank you! This is what I needed....
Coming from the Galaxy S2, it seemed like there were a million 1-click ODINS. Any idea why the S4 doesn't have these?
Click to expand...
Click to collapse
Well, I think that answer is complicated because there was some sort of fall out between users here at XDA and people that were part of the SXTP forums or they started their own forums or whatever. I don't really get into those politic things, I just look for resources that are useful and thank all those that are involved. That and there really aren't as many builds coming out for the S4 like there were for the S2 and the S3 for that matter.

[Q] Accidentally wiped my nandroid

I'm almost too embarrassed to post this question, but... I accidentally formatted my data partition and as a result, deleted my nandroid back up of my stock ROM. I'm on a SG4 i337 with the MDL boot loader. I have no intention of taking the phone back to AT&T for service or anything like that, but in the off chance that I may want to sell the phone, or simply go back to stock, what are my options? Obviously I don't want to update my bootloader, so is there a stock image that I can flash that will allow me to keep my current bootloader?
Thanks,
Mike
mmcneil said:
I'm almost too embarrassed to post this question, but... I accidentally formatted my data partition and as a result, deleted my nandroid back up of my stock ROM. I'm on a SG4 i337 with the MDL boot loader. I have no intention of taking the phone back to AT&T for service or anything like that, but in the off chance that I may want to sell the phone, or simply go back to stock, what are my options? Obviously I don't want to update my bootloader, so is there a stock image that I can flash that will allow me to keep my current bootloader?
Thanks,
Mike
Click to expand...
Click to collapse
Go to Sammobile and get the MDL firmware. Flash it through Odin. If you don't know what I am talking about, make sure you do some research and reading before you do it.
scott14719 said:
Go to Sammobile and get the MDL firmware. Flash it through Odin. If you don't know what I am talking about, make sure you do some research and reading before you do it.
Click to expand...
Click to collapse
Thanks Scott. And I'm a flash junkie, so I know what your're talking about So just clarify, I can flash the stock Sammy MDL and it won't screw up my boot loader?
Thanks again,
Mike
mmcneil said:
Thanks Scott. And I'm a flash junkie, so I know what your're talking about So just clarify, I can flash the stock Sammy MDL and it won't screw up my boot loader?
Thanks again,
Mike
Click to expand...
Click to collapse
No it won't but you're going to want to keep WiFi off until you can freeze the att update app because it's going to want to up date you. Root and put a custom recovery and rom on as soon as you can. Make sure you plan ahead on this before flashing the firmware.

Need help flashing stock S5 G900R4

Hello there,
So, I have a Samsung Galaxy S5 G900R4 with U.S. Cellular. I've heard of rooting your phone, and I decided I'd give it a try. Now, the rooting went fine, and the phone was working like a charm, until I started to have some issues. SuperSU needed to update its binary, and I allowed it to try, but it continued to tell me that it could not update it. Hence, I let it reboot when it offered. Now, for whatever reason, the phone won't boot past the U.S. Cellular 4G logo that appears, it just sits there on that screen.
Now so far, I haven't been able to find anyone that has encountered this specific problem, as most people say their soft-bricks are bootlooping and whatnot. I'm not sure if my specific case is technically a soft brick, or something else, but I wanted to just return it to stock format. I loaded up Odin again, downloaded the 1.5g firmware file, and I got the SW REV CHECK FAIL error.
I did some research, and I searched EVERYWHERE, and the closest I could find to a solution was http://forum.xda-developers.com/showthread.php?t=2798396 <-- this thread. Which makes sense, when I read it. I'm guessing the bootloader is locked on my phone, or something. The problem is that this thread is for the Galaxy S5 G900AU, and I don't have that phone.
Maybe I'm just not searching on the web enough, or I didn't search the site well enough, but I have not been able to locate a similar set of AP, CP and CSC files for my specific model.
I would really appreciate it if someone could point me in the right direction or, if the issue I'm actually having with my phone is NOT a soft-brick and there is another solution, suggest another way for me to fix the phone.
Thank you.
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
*Detection* said:
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
Click to expand...
Click to collapse
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Xeretius said:
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Click to expand...
Click to collapse
Try this link, if it works, it won't work for long
Code:
http://am4-r1f4-stor08.uploaded.net/dl/800e713b-624b-4a91-a57c-1639c6b5071e
*Detection* said:
Try this link, if it works, it won't work for long
Click to expand...
Click to collapse
It worked, it's downloading now, just have to give it some time.
nice one
*Detection* said:
nice one
Click to expand...
Click to collapse
I really hope this works, when it finishes >.>
Any idea what's happening with the phone to cause it to stay at the U.S. Cellular screen?
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
*Detection* said:
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
Click to expand...
Click to collapse
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Xeretius said:
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Click to expand...
Click to collapse
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
*Detection* said:
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
Click to expand...
Click to collapse
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Xeretius said:
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Click to expand...
Click to collapse
Great
Flashing a stock ROM won't void your warranty, but if it is indeed void (KNOX 0x1), then just flash this with ODIN
http://download.chainfire.eu/404/CF-Root1/CF-Auto-Root-klteusc-klteusc-smg900r4.zip
Tripping KNOX only happens when you flash something not signed by Samsung, IE: A custom recovery, ROM or Kernel etc
I have the same issue, same phone I ended up flashing a custom ROM because I luckily flashed twrp before it bricked on the us cellular screen.. How did you fix this I just want to get back to stock remove my root completely

Categories

Resources