Related
Hello,
Problem:
I own a Samsung Galaxy S4 I337 model from AT&T with a locked bootloader. While using safestrap I accidentally checked the /system folder while wiping the STOCK ROM. I didn't yet have another working ROM loaded onto the phone (Safestrap allows you to boot from multiple different ROMS). My phone now freezes at the Samsung logo when I try to boot normally, and I can't reflash the stock ROM in download mode as the bootloader is still locked (I can, however, boot into download mode).
My phone is recognized by ADB which (theoretically) means I can push files back to the device. I haven't yet tried although I'm afraid it may not work as only 2/3 drivers successfully install on my computer when I plug the phone in.
My request from the great tech gods at XDA Forums:
1) If anyone can please reply with any ideas/solutions to my problem I would greatly appreciate it. (PLEASE, ANYTHING. I'M DESPERATE!)
2) If anyone could supply me with a download for the Galaxy s4 I337 /system folder I could attempt to use ADB to push it onto the phone and reboot. WARNING: I'm not an expert on Android and know nothing about the /system folder. Using the /system folder from your personal phone could supply me with very personal information about you/your phone. Please only do this if you know what you're doing!
My ideas:
1) Use android ADB to push the missing files back to my phone, although I don't know if I deleted the entire /system folder or just select things inside it. Also I can't find any downloads for a /system folder anywhere on the Internet.
2) Take it back to AT&T and play dumb. Hopefully they can at least temporarily unlock the bootloader to reflash the stock ROM for me.
Any ideas are GREATLY appreciated,
JT
PS: If you need any more information please leave a reply and I will update the post ASAP. :good:
EDIT: I am running 4.3 Jellybean. Also in answer to your response, I can't flash the firmware again as the bootloader is locked. (Unless I'm missing something and you know more than me, I'm no expert.)
EDIT 2: Looks like I may be wrong and you can reflash the stock ROM on my locked bootloader. Also, for future responses, my S4 has the MF3 baseband although I'll try the thread you suggested. (With the files for my device of course)
EDIT 3: Having trouble flashing stock firmware again with ODIN even though I've now been told that it's possible, read below for more details. I think it's due to the PIT file or the fact that I was running 4.3 and I believe I am trying to flash back to 4.2.2. Please help!
SOLVED: Thanks to ted77usa, I flashed the MK2 stock ROM to my phone through ODIN and this time everything went without a hitch. THANKS A TON!
Also if any mods want to move/delete/do whatever with this post feel free to do so, I don't see this post being very useful for educational purposes as my logic on locked bootloaders was wrong and I don't want people getting the wrong idea.
What firmware are you on? I'd Odin flash the tar files for that firmware.
JTrocks said:
Hello,
Problem:
I own a Samsung Galaxy S4 I337 model from AT&T with a locked bootloader. While using safestrap I accidentally checked the /system folder while wiping the STOCK ROM. I didn't yet have another working ROM loaded onto the phone (Safestrap allows you to boot from multiple different ROMS). My phone now freezes at the Samsung logo when I try to boot normally, and I can't reflash the stock ROM in download mode as the bootloader is still locked (I can, however, boot into download mode).
My phone is recognized by ADB which (theoretically) means I can push files back to the device. I haven't yet tried although I'm afraid it may not work as only 2/3 drivers successfully install on my computer when I plug the phone in.
My request from the great tech gods at XDA Forums:
1) If anyone can please reply with any ideas/solutions to my problem I would greatly appreciate it. (PLEASE, ANYTHING. I'M DESPERATE!)
2) If anyone could supply me with a download for the Galaxy s4 I337 /system folder I could attempt to use ADB to push it onto the phone and reboot. WARNING: I'm not an expert on Android and know nothing about the /system folder. Using the /system folder from your personal phone could supply me with very personal information about you/your phone. Please only do this if you know what you're doing!
My ideas:
1) Use android ADB to push the missing files back to my phone, although I don't know if I deleted the entire /system folder or just select things inside it. Also I can't find any downloads for a /system folder anywhere on the Internet.
2) Take it back to AT&T and play dumb. Hopefully they can at least temporarily unlock the bootloader to reflash the stock ROM for me.
Any ideas are GREATLY appreciated,
JT
PS: If you need any more information please leave a reply and I will update the post ASAP. :good:
EDIT: I am running 4.3 Jellybean. Also in answer to your response, I can't flash the firmware again as the bootloader is locked. (Unless I'm missing something and you know more than me, I'm no expert.)
Click to expand...
Click to collapse
You can use ODIN just fine on the locked bootloaders. Follow the directions in the MK2 TARs thread in the general section.
RE: ODIN on locked bootloader
DeadlySin9 said:
You can use ODIN just fine on the locked bootloaders. Follow the directions in the MK2 TARs thread in the general section.
Click to expand...
Click to collapse
My phone has the MF3 baseband although I'll try the thread you suggested. (With the files for my device of course) Thanks!
Firmware Number
jd1639 said:
What firmware are you on? I'd Odin flash the tar files for that firmware.
Click to expand...
Click to collapse
I'm on 4.3 Jellybean although I don't believe I can reflash the firmware because of my locked bootloader.
EDIT: According to the above post, I can reflash it. Can someone please clarify what files I will need to do so?
JTrocks said:
I'm on 4.3 Jellybean although I don't believe I can reflash the firmware because of my locked bootloader.
EDIT: According to the above post, I can reflash it. Can someone please clarify what files I will need to do so?
Click to expand...
Click to collapse
You need the mf3 tar files. Have you found then?
Flashing tar files with ODIN
jd1639 said:
You need the mf3 tar files. Have you found then?
Click to expand...
Click to collapse
I'm downloading them now from here. Can you verify for me that this is up to date/correct? I previously tried to flash the .tar.md5 file for my phone although I got a "write error" and after researching it I found that you can't flash files in download mode with a locked bootloader. Apparently this is wrong though, thanks for the all the help so far!
JTrocks said:
I'm downloading them now from here. Can you verify for me that this is up to date/correct? I previously tried to flash the .tar.md5 file for my phone although I got a "write error" and after researching it I found that you can't flash files in download mode with a locked bootloader. Apparently this is wrong though, thanks for the all the help so far!
Click to expand...
Click to collapse
Yep, those are the ones. Read the thread on how to use them
Flashing with ODIN
jd1639 said:
Yep, those are the ones. Read the thread on how to use them
Click to expand...
Click to collapse
I followed the thread exactly as it said but it failed. Then I included the the PIT file but still failed. I've attached a screenshot of ODIN after I tried with the PIT file.
EDIT: My phone is giving a message that reads: "SECURE CHECK FAIL : PIT" I read that PIT files have to be signed with a device-specific key to work, although it seems that most people aren't having a problem using one found off of the Internet. Any ideas?
EDIT 2: I believe those files are for 4.2.2, I was running 4.3, is this the issue? Also I don't know if my phone was updated OTA or not, I bought it from eBay. :/
JTrocks said:
I followed the thread exactly as it said but it failed. Then I included the the PIT file but still failed. I've attached a screenshot of ODIN after I tried with the PIT file.
EDIT: My phone is giving a message that reads: "SECURE CHECK FAIL : PIT" I read that PIT files have to be signed with a device-specific key to work, although it seems that most people aren't having a problem using one found off of the Internet. Any ideas?
EDIT 2: I believe those files are for 4.2.2, I was running 4.3, is this the issue? Also I don't know if my phone was updated OTA or not, I bought it from eBay. :/
Click to expand...
Click to collapse
@JTrocks ....If u are on 4.3 rom it mean that either u took OTA to MK2 firmware and then someone either u or the seller from ebay flash the modem back to MF3 to complete SIM UNLOCKED( if u ever sim unlocked ) .........either way just follow my thread..........
| ★ MK2 ★ FULL ODIN TAR FILES ★ MK2 ★ | ★ UNBRICKED ★ Jan.31.2014 ★ | u can restore to stock 4.3 MK2 firmware or even update to MK2 if u coming from MF3.....tested my self and others confirmed as well....:good::good: Check post #2 for guide on how to ,......BUT IF U STILL WANT TO FLASH THAT MF3.TAR .....TRY TO UN-CHECK RE-PARTITION FROM ODIN ONLY AUTO REBOOT AND F.RESET TIME ARE CHECK.....U DONT HAVE TO LOAD THAT PIT FILE.....JUST BOOTLOADER,PDA,MODEM AND CSC IS ENOUGH....ALSO TRY DIFFERENT ODIN VERSION FROM MY THREAD POST#2 THERE IS ODIN3 V1.85 ....GOODLUCK.....LET ME KNOW HOW IT GO....:good::good:
ted77USA
ted77usa said:
@JTrocks ....If u are on 4.3 rom it mean that either u took OTA to MK2 firmware and then someone either u or the seller from ebay flash the modem back to MF3 to complete SIM UNLOCKED( if u ever sim unlocked ) .........either way just follow my thread..........
| ★ MK2 ★ FULL ODIN TAR FILES ★ MK2 ★ | ★ UNBRICKED ★ Jan.31.2014 ★ | u can restore to stock 4.3 MK2 firmware or even update to MK2 if u coming from MF3.....tested my self and others confirmed as well....:good::good: Check post #2 for guide on how to ,......BUT IF U STILL WANT TO FLASH THAT MF3.TAR .....TRY TO UN-CHECK RE-PARTITION FROM ODIN ONLY AUTO REBOOT AND F.RESET TIME ARE CHECK.....U DONT HAVE TO LOAD THAT PIT FILE.....JUST BOOTLOADER,PDA,MODEM AND CSC IS ENOUGH....ALSO TRY DIFFERENT ODIN VERSION FROM MY THREAD POST#2 THERE IS ODIN3 V1.85 ....GOODLUCK.....LET ME KNOW HOW IT GO....:good::good:
Click to expand...
Click to collapse
Thanks for the reply, but before I go any further I should clarify some information about my phone. I bought an AT&T Samsung Galaxy S4 from eBay, when I got the phone it was running 4.3. The catch: My phone isn't actually on AT&T service OR SIM unlocked (I think), I'm with a cell provider called NET 10. How NET 10 works is that it pays AT&T to run off of their service, NET 10 is cheaper for the customers because it isn't as fast as AT&T. AT&T and Net 10 have an agreement where you can take any phone from AT&T and hook it up to NET 10 without unlocking it. Although I think that NET 10 may unlock your phone when you hook it up to their service, I'm not sure. What makes my think that is that when I booted my phone up after transferring to NET 10, a picture of an open padlock appeared under the Samsung logo.
Being on NET 10 may have changed some of that, specifically the MF3/MK2 baseband. Not being an expert on basebands and how they correlate to your cell service provider, will following your instructions result in not being able to connect to NET 10's service? It's probably a stupid question, I know, but with my minimal knowledge I figured I should ask before I followed through with anything.
JTrocks said:
Thanks for the reply, but before I go any further I should clarify some information about my phone. I bought an AT&T Samsung Galaxy S4 from eBay, when I got the phone it was running 4.3. The catch: My phone isn't actually on AT&T service OR SIM unlocked (I think), I'm with a cell provider called NET 10. How NET 10 works is that it pays AT&T to run off of their service, NET 10 is cheaper for the customers because it isn't as fast as AT&T. AT&T and Net 10 have an agreement where you can take any phone from AT&T and hook it up to NET 10 without unlocking it. Although I think that NET 10 may unlock your phone when you hook it up to their service, I'm not sure. What makes my think that is that when I booted my phone up after transferring to NET 10, a picture of an open padlock appeared under the Samsung logo.
Being on NET 10 may have changed some of that, specifically the MF3/MK2 baseband. Not being an expert on basebands and how they correlate to your cell service provider, will following your instructions result in not being able to connect to NET 10's service? It's probably a stupid question, I know, but with my minimal knowledge I figured I should ask before I followed through with anything.
Click to expand...
Click to collapse
It shouldn't. Your phone is the same model, and the firmware appears to be the same. At most you might have to put in an APN to get your mobile data back.
Continuing with Instructions
DeadlySin9 said:
It shouldn't. Your phone is the same model, and the firmware appears to be the same. At most you might have to put in an APN to get your mobile data back.
Click to expand...
Click to collapse
Thanks, I'm aware of the APN. I had SEVERAL issues with NET 10 when I first set that up. (THEY MISSPELLED THE F****** IP ADDRESS ON THEIR WEBSITE!) Still frustrated about that one. D:<
I'm now preparing to follow through with ted77usa's instructions. Sorry if I respond slow, I have to wait 5 minutes after each post/edit as I haven't been approved by a mod yet.
EDIT: I may have to continue this tomorrow, the site ted77usa used to host the .tar files is pretty slow. The download is going to take an hour and it's getting late here. I can't believe how much support I'm getting from everyone, thanks a TON! I'm clicking the thanks button on everyone who's helped me, it's the least I can do!
JTrocks said:
Thanks, I'm aware of the APN. I had SEVERAL issues with NET 10 when I first set that up. (THEY MISSPELLED THE F****** IP ADDRESS ON THEIR WEBSITE!) Still frustrated about that one. D:<
I'm now preparing to follow through with ted77usa's instructions. Sorry if I respond slow, I have to wait 5 minutes after each post/edit as I haven't been approved by a mod yet.
EDIT: I may have to continue this tomorrow, the site ted77usa used to host the .tar files is pretty slow. The download is going to take an hour and it's getting late here. I can't believe how much support I'm getting from everyone, thanks a TON! I'm clicking the thanks button on everyone who's helped me, it's the least I can do!
Click to expand...
Click to collapse
While u waiting. ... try to read all the thread so that would give u an idea what others issue incase u run same problem..... As long as u check md5 if they match then u should good to go. ... and seem to me u know usb debugging. ...all the driver already installed....PM me if u need more help ....:thumbup::thumbup:
Swyped From MK2 Dark Venom SS Edition
All Good!
ted77usa said:
While u waiting. ... try to read all the thread so that would give u an idea what others issue incase u run same problem..... As long as u check md5 if they match then u should good to go. ... and seem to me u know usb debugging. ...all the driver already installed....PM me if u need more help ....:thumbup::thumbup:
Swyped From MK2 Dark Venom SS Edition
Click to expand...
Click to collapse
AMAZING! Everything went without a hitch!! My phone now indicates that it is running Android 4.3, Baseband version MK2, and calls/texts are working just fine. I have to enter my APN settings again as DeadlySin9 mentioned, but I expect everything should work fine. Thanks to everyone who helped me out (especially ted77usa with the link to his thread), if there's anything I can do to help any of you out in return just let me know! THANKS A TON!!!
JTrocks said:
AMAZING! Everything went without a hitch!! My phone now indicates that it is running Android 4.3, Baseband version MK2, and calls/texts are working just fine. I have to enter my APN settings again as DeadlySin9 mentioned, but I expect everything should work fine. Thanks to everyone who helped me out (especially ted77usa with the link to his thread), if there's anything I can do to help any of you out in return just let me know! THANKS A TON!!!
Click to expand...
Click to collapse
Glad that u got your phone back..... and u also got great community in here...... the best place to learn and give back .....:thumbup::thumbup:
Swyped From MK2 Dark Venom SS Edition
atnt splash screen
JTrocks said:
AMAZING! Everything went without a hitch!! My phone now indicates that it is running Android 4.3, Baseband version MK2, and calls/texts are working just fine. I have to enter my APN settings again as DeadlySin9 mentioned, but I expect everything should work fine. Thanks to everyone who helped me out (especially ted77usa with the link to his thread), if there's anything I can do to help any of you out in return just let me know! THANKS A TON!!!
Click to expand...
Click to collapse
Hey, i had a similar problem. MK2 safe root method. became rooted and everything was great. downloaded xposed framwork/installer. selected fast boot option by accident been stopping at the atnt splash screen ever since. i am able to boot into download/odin mode as well as recovery. I have tried mutiple wipes and facotry resets but same outcome, hangs at atnt screen. i creeped around the threads and found this. My first question is did Ted77usa files from his link take forever for you also? and second how many attmepts did it take with odin?
semarj said:
Hey, i had a similar problem. MK2 safe root method. became rooted and everything was great. downloaded xposed framwork/installer. selected fast boot option by accident been stopping at the atnt splash screen ever since. i am able to boot into download/odin mode as well as recovery. I have tried mutiple wipes and facotry resets but same outcome, hangs at atnt screen. i creeped around the threads and found this. My first question is did Ted77usa files from his link take forever for you also? and second how many attmepts did it take with odin?
Click to expand...
Click to collapse
@semarj If you follow my thread and guide on post#2 it should get u back on stock MK2 less then 6 minutes. .... As long as u have usb debugging check. ... Good usb cable. ....Good driver installed and make sure ONLY auto reboot and F. Reset Time CHECK from Odin..... GOODLUCK. ....PM ME IF YOU NEED MORE HELP. ....:thumbup::thumbup:
Swyped From MK2 Dark Venom SS Edition
semarj said:
Hey, i had a similar problem. MK2 safe root method. became rooted and everything was great. downloaded xposed framwork/installer. selected fast boot option by accident been stopping at the atnt splash screen ever since. i am able to boot into download/odin mode as well as recovery. I have tried mutiple wipes and facotry resets but same outcome, hangs at atnt screen. i creeped around the threads and found this. My first question is did Ted77usa files from his link take forever for you also? and second how many attmepts did it take with odin?
Click to expand...
Click to collapse
It took about an hour for me to download ted77usa's files but I have relatively fast internet (16 mb/ps). As soon as the files downloaded it worked first try, are you in download mode? If you are and it's still not working you may need the PIT file and to make sure that re-partition is checked along with the 2 others that ted77usa mentioned.
drivers finished
ted77usa said:
@semarj If you follow my thread and guide on post#2 it should get u back on stock MK2 less then 6 minutes. .... As long as u have usb debugging check. ... Good usb cable. ....Good driver installed and make sure ONLY auto reboot and F. Reset Time CHECK from Odin..... GOODLUCK. ....PM ME IF YOU NEED MORE HELP. ....:thumbup::thumbup:
Swyped From MK2 Dark Venom SS Edition
Click to expand...
Click to collapse
I will post back asap. the drivers were taking forever to download so i started a kias emergency firmware recovery. thats taking forever also. its only at 79% but have been running for an hour. should i let finish? and if unsuccessful try odin or just quit and do odin?
Here is how i boot looped my phone, I rooted it by following this thread https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039 and I rooted it successfully. The I needed to unroot my phone and tried following the unroot method on that thread. But I got an error with odin saying "FAIL! (AUTH)" and thought it was the version I was using. So i tried downloading a few different versions and tried the latest update for the s7 and it failed which boot looped my phone. And if i hold power + Volume Up + Home it says recovery booting.... and keeps doing that over and over. so that doesnt work. All i want to do at this point is get my phone unboot looped and unrooted If anybody can help. please do. BTW i have the SM-G930V
c0ff33 said:
Here is how i boot looped my phone, I rooted it by following this thread https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039 and I rooted it successfully. The I needed to unroot my phone and tried following the unroot method on that thread. But I got an error with odin saying "FAIL! (AUTH)" and thought it was the version I was using. So i tried downloading a few different versions and tried the latest update for the s7 and it failed which boot looped my phone. And if i hold power + Volume Up + Home it says recovery booting.... and keeps doing that over and over. so that doesnt work. All i want to do at this point is get my phone unboot looped and unrooted If anybody can help. please do. BTW i have the SM-G930V
Click to expand...
Click to collapse
Try loading all 4 files in odin 3.12 as starting fresh. Qa4 should be available. Or look at some of the posts in the bs free thread and see if any of this workarounds work
gunz.jones said:
Try loading all 4 files in odin 3.12 as starting fresh. Qa4 should be available. Or look at some of the posts in the bs free thread and see if any of this workarounds work
Click to expand...
Click to collapse
All 4 files of the latest update? or the older version?
c0ff33 said:
All 4 files of the latest update? or the older version?
Click to expand...
Click to collapse
BL, AP, CSC, CP
https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124/page16
gunz.jones said:
BL, AP, CSC, CP
https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124/page16
Click to expand...
Click to collapse
this happens when i try loading the files i have which is the latests update https://gyazo.com/754847c67703f53c5e53c285882bcf63
That's odd. Try using the files and instructions from the thread i linked to. See if you have the same result.
gunz.jones said:
That's odd. Try using the files and instructions from the thread i linked to. See if you have the same result.
Click to expand...
Click to collapse
should i use tmobile files bc thats all i see on that thread? or what else do i use
c0ff33 said:
should i use tmobile files bc thats all i see on that thread? or what else do i use
Click to expand...
Click to collapse
Yes, they should still work without that error you're getting now
gunz.jones said:
Yes, they should still work without that error you're getting now
Click to expand...
Click to collapse
I installed the tmobile and it worked but when i got to the flash ap file using that app it said it doesnt have root powers. and that my phone is tmobile is a problem bc i need to turn it in to get an s8
c0ff33 said:
I installed the tmobile and it worked but when i got to the flash ap file using that app it said it doesnt have root powers. and that my phone is tmobile is a problem bc i need to turn it in to get an s8
Click to expand...
Click to collapse
Try getting the qa2 files off updato.com and flashing those. May be a bad dl that is causing your problem. If it flashed the tmo files with no issue, then that's the only thing i can think of
gunz.jones said:
Try getting the qa2 files off updato.com and flashing those. May be a bad dl that is causing your problem. If it flashed the tmo files with no issue, then that's the only thing i can think of
Click to expand...
Click to collapse
would this be it? http://updato.com/firmware-archive-select-model?record=4143C97E042B11E7963AFA163EE8F90B
c0ff33 said:
would this be it? http://updato.com/firmware-archive-select-model?record=4143C97E042B11E7963AFA163EE8F90B
Click to expand...
Click to collapse
And with that file do i flash the AP , CP , BL , And HOME_CSC ?
c0ff33 said:
And with that file do i flash the AP , CP , BL , And HOME_CSC ?
Click to expand...
Click to collapse
Yes, flash all those listed. It should fix your issue if all files are correct. If you have an issue with home csc, try the base csc and factory reset
gunz.jones said:
Yes, flash all those listed. It should fix your issue if all files are correct. If you have an issue with home csc, try the base csc and factory reset
Click to expand...
Click to collapse
FIXED thanks so much your awesome
c0ff33 said:
FIXED thanks so much your awesome
Click to expand...
Click to collapse
You're welcome
So after I flashed the stock rom back on the phone is functioning good and everything seems to be in order. However when i try to root it it gives me this error in odin http://prntscr.com/g3sml0 . Does anyone know why this is happening to my SM-G935U ???
Thanks for the help in advance
I still get secure check fail in odin for no reason at all
intramorph said:
I still get secure check fail in odin for no reason at all
Click to expand...
Click to collapse
It sounds like a bad download. I think you need the .tar file and not the tar.md5 file...
check and try again.
intramorph said:
So after I flashed the stock rom back on the phone is functioning good and everything seems to be in order. However when i try to root it it gives me this error in odin http://prntscr.com/g3sml0 . Does anyone know why this is happening to my SM-G935U ???
Thanks for the help in advance
Click to expand...
Click to collapse
I've tried rooting SM-G935U multiple times. The ENG boot image flashes fine in Odin but once it boots into the OS it reboots every 45-60 seconds. I never get to flash the root.bat
I'm thinking something has definitely changed. Others aren't reporting quite the same struggle I'm experiencing (at least not to the extent I have.) I just got this phone 2 weeks back. It came with Nougat.
Though I don't get any errors in Odin. Are you using the modified version?
KLit75 said:
I've tried rooting SM-G935U multiple times. The ENG boot image flashes fine in Odin but once it boots into the OS it reboots every 45-60 seconds. I never get to flash the root.bat
I'm thinking something has definitely changed. Others aren't reporting quite the same struggle I'm experiencing (at least not to the extent I have.) I just got this phone 2 weeks back. It came with Nougat.
Though I don't get any errors in Odin. Are you using the modified version?
Click to expand...
Click to collapse
No i'm using the original one from sam's mobile. I'm also on nougat. I had the same issue the first time i tried to root,got stuck in a reboot loop so i had to flash original firmware. After that my phone is working as intended but i get this error in odin now. Is there another way to root this device or am i out of luck xD
By modified version do you mean if it's a t-mobile device "for example" with the U firmware flashed? in that case no it's the original SM-G935U device.
TheOne741 said:
It sounds like a bad download. I think you need the .tar file and not the tar.md5 file...
check and try again.
Click to expand...
Click to collapse
Hi and where can i find the .tar file please. Forgive me for being such noob
intramorph said:
Hi and where can i find the .tar file please. Forgive me for being such noob
Click to expand...
Click to collapse
G935U Bootloader is locked
take a look here
https://
forum.xda-developers.com/sprint-s7-edge
intramorph said:
No i'm using the original one from sam's mobile. I'm also on nougat. I had the same issue the first time i tried to root,got stuck in a reboot loop so i had to flash original firmware. After that my phone is working as intended but i get this error in odin now. Is there another way to root this device or am i out of luck xD
By modified version do you mean if it's a t-mobile device "for example" with the U firmware flashed? in that case no it's the original SM-G935U device.
Click to expand...
Click to collapse
By modified I just meant the version of Odin youre using.
When you say you had to flash back to the original firmware, do you happen to know which version?
KLit75 said:
By modified I just meant the version of Odin youre using.
When you say you had to flash back to the original firmware, do you happen to know which version?
Click to expand...
Click to collapse
I do i used this one https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/TMK/download/G935UUES4BQG1/181625/
also i tried the modified version of odin as well as the latest. By now i've just given up. it's just not worth it imo
intramorph said:
I do i used this one https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935U/TMK/download/G935UUES4BQG1/181625/
also i tried the modified version of odin as well as the latest. By now i've just given up. it's just not worth it imo
Click to expand...
Click to collapse
I hear ya. Long process only to have it not work.
But when I asked about the firmware I meant the one you successfully rooted last. The one you posted was the same one I tried. And like I said, eng boot flashed fine but the subsequent reboot loop made it impossible to run the root.bat
My only theories are either something was changed by samsung and/or the devices that previously had M installed ARE able to be rooted.
One thing Im certain of is the new firmware does not like that engineering boot img.
But Im still holding out hope for root...
KLit75 said:
I hear ya. Long process only to have it not work.
But when I asked about the firmware I meant the one you successfully rooted last. The one you posted was the same one I tried. And like I said, eng boot flashed fine but the subsequent reboot loop made it impossible to run the root.bat
My only theories are either something was changed by samsung and/or the devices that previously had M installed ARE able to be rooted.
One thing Im certain of is the new firmware does not like that engineering boot img.
But Im still holding out hope for root...
Click to expand...
Click to collapse
It wasnt successful. It send me into a boot loop. Much like you. I couldn't run the root.bat file either. After that I just flashed original rom and that's it
Sent from my SM-G935U using Tapatalk
KLit75 said:
I hear ya. Long process only to have it not work.
But when I asked about the firmware I meant the one you successfully rooted last. The one you posted was the same one I tried. And like I said, eng boot flashed fine but the subsequent reboot loop made it impossible to run the root.bat
My only theories are either something was changed by samsung and/or the devices that previously had M installed ARE able to be rooted.
One thing Im certain of is the new firmware does not like that engineering boot img.
But Im still holding out hope for root...
Click to expand...
Click to collapse
Hey man i was wondering if you still want to root. here's what worked for me. https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502 . This method works for the sm-g935u. Also xposed works as well
The only thing i could find that was wrong was that my device was a bit laggy after rooting it but i gave it some time and it's lag-free now. I'm glad i did this. The downside is there's no custom recovery but maybe we'll get one soon. Good luck
intramorph said:
Hey man i was wondering if you still want to root. here's what worked for me. https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502 . This method works for the sm-g935u. Also xposed works as well
The only thing i could find that was wrong was that my device was a bit laggy after rooting it but i gave it some time and it's lag-free now. I'm glad i did this. The downside is there's no custom recovery but maybe we'll get one soon. Good luck
Click to expand...
Click to collapse
I just rooted it Sunday night but thanks for letting me know!:good:
If you could though, please tell me which version of xposed you flashed. Was it the purify os v87 sdk24 from 7/26?
KLit75 said:
I just rooted it Sunday night but thanks for letting me know!:good:
If you could though, please tell me which version of xposed you flashed. Was it the purify os v87 sdk24 from 7/26?
Click to expand...
Click to collapse
it was purifyos and you flash the zip in Flashfire mount system
My friend got an old phone from his dad, who had an old custom ROM installed on it, and asked me to return it to the original software.
I used ODIN 3.09 and installed the appropriate ROM which I downloaded from Sammobile.
The phone went into a bootloop, so I wiped the cache and when that didn't work, I wiped all data. After that the phone booted into the Welcome screen and my friend started to configure it. In the middle of the process, the phone rebooted, and now it loads into the Welcome screen, but reboots after a few seconds.
After that I've tried reflashing the software and doing multiple resets, to no avail. Any ideas?
Please let me know of any Ideas. I am very ashamed of damaging my friend's phone.
PS: I should say, I put a bootloader into ODIN the first time I flashed the software because some tutorial recommended it and I haven't seen that requierement in any other tutorial since. Might this be the cause? How could I test that?
What model what firmware what bootloader ??
JJEgan said:
What model what firmware what bootloader ??
Click to expand...
Click to collapse
The phone is a Note 3 N900 UB, the firmware I installed was N900UBSEBQB5, and to be honest, I can't quite tell what the bootloader is, the file I downloaded is just called "bootloader".
the file I downloaded is just called "bootloader
My guess is that's the fault as bootloaders are named same as firmwares
Example >>> BL_N9005ZSUGPJ2
Could be a bootloader for anything .because some tutorial recommended
Have you taken a chance to reflashing the official firmware with ordin , that would be helpful all the time.
After that you should make sure your phone work fine on the official rom .
Then update your Recovery to a third party Rec,like CWM or TWRP .
Next step,flashing an original rom.
larrycn said:
Have you taken a chance to reflashing the official firmware with ordin , that would be helpful all the time.
After that you should make sure your phone work fine on the official rom .
Then update your Recovery to a third party Rec,like CWM or TWRP .
Next step,flashing an original rom.
Click to expand...
Click to collapse
Thats wrong .
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
bothambhai said:
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Click to expand...
Click to collapse
just checking... are you using the edited princecomsy odin? http://d-h.st/gsDA or use the link here https://forum.xda-developers.com/att-s7-edge/help/princes-odin-t3545104
find the correct rom here https://forum.xda-developers.com/sprint-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3569834
just use files from one rom at a time. get good at that first. maybe you are careful but it really looks like you were guessing what goes where at the end of your post.
i just have tips on what helped me. passing along the info and the link.
epikroms said:
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
Click to expand...
Click to collapse
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
bothambhai said:
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
Click to expand...
Click to collapse
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
epikroms said:
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
Click to expand...
Click to collapse
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
bothambhai said:
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
Click to expand...
Click to collapse
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
epikroms said:
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
Click to expand...
Click to collapse
Thanks for your reply. If it is not too much can you please break down the steps a bit more because I don't want to guess and mess it up again and also if you could please kindly point me to the other thread as well so I can download the appropriate stuff from there and read a bit more about it. I am right now unable to use the phone with the sprint firmware on it on TMo, it's super annoying.
Thanks in advance.
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Did you get it sorted out? Hopefully you are on the rom and haven't bricked your device. I attached a picture so you could see that I am on what I say I am on.
epikroms said:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Click to expand...
Click to collapse
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
bothambhai said:
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
Click to expand...
Click to collapse
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
thats pretty interesting being on the binary 5 baseband and binary 4 rom. to clarify, you were on the binary 5 rom and reverted? or were you on the baseband 4 and upgraded just the baseband? thanks for the info.
epikroms said:
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
Click to expand...
Click to collapse
I odined the AP_Nougat_S7_Edge_EngBoot.tar.md5 then ran the root.bat file from Nougat_S7_Root_2_82_All_Carriers_V2 , I chose the options to install the fingerprint fix and install the root without any gpu tweaks. I watched the whole process complete and the cmd prompt close, my phone never asked my permission to ALLOW anything, everything was on the computer. I ran the root.bat from cmd as an administrator and the program ran evidently because it asked me about the fingerprint fix and root with or without tweaks etc. I noticed the phone reboot and there was a notification, the phone was rooted but no SU and flashwire says no root access. I tried it back from square one a couple of tries more right back from flashing stock sprint firmware and trying the whole rooting process again, same results except the next two times the phone doesn't reboot after running the root.bat file. I notice now when the phone boots up there is a sign saying "CUSTOM" beneath the samsung logo on the screen. I don't know where I am going wrong in the process though. I don't know if it is because I am on the binary 5 however I also read somewhere that people have been successful in rooting their binary 5 sprint S7 edges. I have rooted many devices before and installed roms etc, this has been, by far, the most perplexing phone in every which way.
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
epikroms said:
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
Click to expand...
Click to collapse
Bummer about your phone. On a glad note I managed to root and flash my phone and everything works great now. I was taking the hard nerdy way to do it by running cmd as an administrator and having that run the root.bat file. I read somewhere else you could just double click the file and it worked for me . From there on the aroma part was pretty straightforward. I am grateful to you for pointing me in this direction and breaking it down for me, I seriously doubted me being able to achieve this on my binary 5 phone but it turned out to be smooth.
I do wish you the best and thanks once again.