Hi community
I have a Samsung Galaxy S7 SM-G930V with Android 7.0. I tried to get root but first I had to unlock bootloader. I flashed the "Engineer Bootloader" (a file named Samsung_G930x_QC_Rooted_BOOT.TAR) with Odin for engineering bootloader and no problem then the phone reboot. There comes the problem, the phone is on a bootloop, it shows the screen "Samsung Galaxy S7" and restart again, over and over.
People suggest to go to recovery mode and wipe data and factory reset, I already did that but it didn't work.
I'm sure that flash the complete ROM again will solve the problem but the ROM is 2.50 GB and my Internet connection is very very slow so I can't download it. Maybe flashing just the custom boot.img the problem gets solved, can somebody bring me just that file? Please I need it really much.
Thank you very much.
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
dude, THANK YOU VERY MUCH!!! you saved my life. I don't understand why people post tutorials with wrong files. THANK YOU VERY MUCH AGAIN.
CVertigo1 said:
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
Click to expand...
Click to collapse
Wow... I have searched high an low for this. Thank you.
CVertigo1 said:
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
Click to expand...
Click to collapse
Is there a version of this that's just stock, no root or special engineering version?
ItsKipz said:
Is there a version of this that's just stock, no root or special engineering version?
Click to expand...
Click to collapse
Hi I was just experimenting with the Verizon Recovery Utility tools on windows 10 on the computer and noticed it was temporary copying ALL BL, AP, CSC ext. Well I selected it and copied in another folder before it could erase the files when done flashing my S7 verizon back to stock. It worked! I got all the files straight from Verizon's official tool. Since windows will throw a error message to anything trying to delete files in use, when verizon tool tried to erase the temp stock files, it denied it since the file was in use by me. Aka copying to another folder as the verizon tool downloaded the files I was right there copying the files mid download and the computer let the files finish download complete and it ended up being I got the files. Im proud of myself. Lol! Being new at this.
So someone just tell me what I do to get you all a copy. They are the most current stock files from verizon. I uploaded them all into Onedrive already so files are safe just waiting for the moment someone needs them and tells me how to upload them. I see androidhostfile or something site. Can I use that one? Even though Im new at this?
Here is my screen shot of my new files.
Scottie32583 said:
Hi I was just experimenting with the Verizon Recovery Utility tools on windows 10 on the computer and noticed it was temporary copying ALL BL, AP, CSC ext. Well I selected it and copied in another folder before it could erase the files when done flashing my S7 verizon back to stock. It worked! I got all the files straight from Verizon's official tool. Since windows will throw a error message to anything trying to delete files in use, when verizon tool tried to erase the temp stock files, it denied it since the file was in use by me. Aka copying to another folder as the verizon tool downloaded the files I was right there copying the files mid download and the computer let the files finish download complete and it ended up being I got the files. Im proud of myself. Lol! Being new at this.
So someone just tell me what I do to get you all a copy. They are the most current stock files from verizon. I uploaded them all into Onedrive already so files are safe just waiting for the moment someone needs them and tells me how to upload them. I see androidhostfile or something site. Can I use that one? Even though Im new at this?
Here is my screen shot of my new files.
Click to expand...
Click to collapse
This is what the file looks like I have...
Related
Hey guys i couldn't get in the beta so i was wondering if anyone has the Nougat update file that i can flash with odin.
Thanks
Join the club. No one has the VZW one for the flat s7 either....
Illogi.xbone said:
Join the club. No one has the VZW one for the flat s7 either....
Click to expand...
Click to collapse
Someone said they are going to try. I offered help if need be
billydroid said:
Someone said they are going to try. I offered help if need be
Click to expand...
Click to collapse
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.
jakemastaflash said:
I cannot post outside links so please PM me if you would like to test the file. I will also upload it to Android File Host when I am approved.
Click to expand...
Click to collapse
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?
diego97yey said:
Hey, send me the link. Other than the files, the proccess should be the very basic odin proccess right?
Click to expand...
Click to collapse
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.
jakemastaflash said:
I believe it can be flashed from Recovery. It's being tested now, I will be checking for updates\consistency tomorrow with a clean flash and update.
Click to expand...
Click to collapse
Keep us posted man
Footer and verification error so far
Same here
Sent from my SM-G930P using XDA-Developers mobile app
dgr581 said:
Same here
Sent from my SM-G930P using XDA-Developers mobile app
Click to expand...
Click to collapse
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.
jakemastaflash said:
Sounds like it is throwing errors for everyone . I will be trying to grab a fresh copy today, or tomorrow. Link removed until we have a working update.
Click to expand...
Click to collapse
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.
vegoja said:
I tried using winrar to repair it but still got error code my recovery has been acting strange tho. It says install system update when i boot to it then gives me a dead droid with yellow triangle but then enters recovery like normal.
Click to expand...
Click to collapse
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!
jakemastaflash said:
I believe I have a solution. I am working on it now. Additionally, I'm getting close 10 posts!
Click to expand...
Click to collapse
Another update pull failed verification and resulted in another footer error. If installed without any modification it works, but after rooting and pulling the update.zip, trying to install it results in an error. It could be a security measure introduced to the update.zip to prevent installing on a phone without the matching signature assigned during the initial download.
Whenever i tried to follow the link it asked me for a security key ????
footer error
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian
N3ksta said:
I read on another nougat beta thread that if you get a footer error then you should decrypt your SD and try agian
Click to expand...
Click to collapse
I did not have my SD Card encrypted. I have also noticed some discrepancies between the update.zip I am extracting and the working VZW update.zip. Things like: the boot.img is 0kb, and there are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
I have tried extracting it in several different ways\environments and get problems with every pull.
Other variants are working on the same thing with the same issues. I have the last pull I made, but I can't continue working on this as heavily since I'm using my daily driver. I'll try again as new info\solutions come up.
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Originally Posted by zimgir124
A method has been found to install the beta without being accepted!
Thanks @jrkruse for finding this method!
1. reboot to download mode (power + volume up +home) and make sure phone says Official under system and binary.
2. If it does not then you must odin the PH1 firmware, use the pit file and the full csc not the home csc file
3. go through setup
4. enable developer options
5. turn OEM unlock off
6. enable USB debugging
7. place Update.zip on Ext sd card in folder named fota
8. power off phone
9. reboot to download mode make sure both system and binary are official.
10. reboot to recovery (Power + volume down + home)
11. choose apply Update.zip from SD card
12. find Update.zip in the fota folder you created on your Ext sdcard
13. click yes to apply
After this it should update to the Android 7.0 beta and hopefully will be able to download future beta OTAs.
You will not lose anything as this is an OTA
You do not want to be rooted. You must be stock for this to work!
There is no gear VR available on the beta.
Troubleshooting:
"E: footer is wrong" followed by "E: signature verification failed" : Decrypt SD Card and try again.
Click to expand...
Click to collapse
jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out corrupt\incomplete. Good luck!
Link to the update.zip.
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
So should this method work for us?
jakemastaflash said:
Seems like getting root (with current methods) may be disturbing the file structure. There may be something else at play here since all the pulls still come with a boot.img that is 0kb, and are missing CERT.RSA, CERT.SF, or MANIFEST.MF files under META-INF folder.
Here is the link to the WIP update.zip. I'm going to stop working on this until someone can suggest a better way to root or pull the file without it coming out
Here is the flashing method used by the VZW folks:
Click to expand...
Click to collapse
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)
15jpenni said:
So should this method work for us?
Click to expand...
Click to collapse
Ideally it should. However, I have not been able to successfully reproduce the same results as installing the update file without modification.
---------- Post added at 09:04 PM ---------- Previous post was at 09:00 PM ----------
N3ksta said:
Is it for the flat or edge? also have you tried using adb to pull the file (you probably have, but just asking)
Click to expand...
Click to collapse
This is for the SM-G930P regular S7 (not edge). I have pulled it via filemanager app after full root, and via adb on linux and windows after eng kernel root and full root. All of them yielded an apropriately sized update.zip, but it seems to get corrupted during the rooting or extraction process.
Also, there may be a reason behind our update.zip not having a boot.img. We may not need a new boot.img after updating to PJ2, so it isnt packaged in our update. If someone can repackage the update.zip so it passes verification we may have more luck.
Should have enough posts to include links now.
These are the stock files I purchased from a persian site for 12$ since nobody had them posted on the forums. Flashed with the latest unmodded Odin. I also had the benefit of suddenly getting data toggle with it after flashing the AP file. Not sure if everyone else will get it too.
https://drive.google.com/open?id=0B0vffDY5Mf5sY1JpY3ViWlV1OVU
I can also confirm that root works with this.
And thanks for the hookup.. lol
i got it recently and going to flash this firmware and will try root.. will reply
Obies said:
i got it recently and going to flash this firmware and will try root.. will reply
Click to expand...
Click to collapse
It works. However, you REALLY need to run the V15 fix script.. The older builds ran like crap, even with the fix script, however with APK1, my phone runs normal and doesn't overheat. However, if you don't run that script with APK1, your phone will run sluggish and hot.
yeah i do aware abt bad lagging after rooted.. anyways my phone is on rooted with Fixes V15 and xposed install with XtouchWiz module so i can use tethering for my laptop/tablet while i am away from home. but no Toggle Data for me.. maybe bad luck but i did odin 4 files and factory reset..
Thanks for this files!
Is this the Stock AT&T PK1 that I have on my phone with the last OTA dated Nov. 1
I downloaded all these files, deleted .rar off the end so Odin would recognize the files (did i do that right?), plugged all 4 files in to the right spots and tried to flash them. I’ve used Odin plenty of times and haven’t had any problems before but I am far from an Odin master. This time I just get stuck at file analysis after i click the start button. Any idea what i could be doing wrong?
jermo said:
I downloaded all these files, deleted .rar off the end so Odin would recognize the files (did i do that right?), plugged all 4 files in to the right spots and tried to flash them. I’ve used Odin plenty of times and haven’t had any problems before but I am far from an Odin master. This time I just get stuck at file analysis after i click the start button. Any idea what i could be doing wrong?
Click to expand...
Click to collapse
You need to decompress the RAR files first using something like 7-Zip (it will extract files with a tar.md5 extension). Those are the files you use in Odin.
Been having an issue with my ATT S7 when it goes to do some kind of OTA update and fails, then my apps start randomly crashing and of course I decide to reboot. When I reboot I get stuck on the white att screen. This is the second time is has happened, first time I just did a factory reset and was back up and running. Well today it went to do an update, update failed and I am back at a white screen again. I decided to start researching what the newest firmware was and can’t seem to get a straight answer. I also have no idea what bootloader I am on and so on…From what I can tell is PK1 is the newest firmware am I right?!? No idea where to check what bootloader I have…
So I decided I was going to just install everything from this thread in hopes to cure my issue https://forum.xda-developers.com/att-galaxy-s7/how-to/pk1-odin-files-t3522168
I downloaded all the files, deleted .rar off the end so Odin would recognize the files (did i do that right?), plugged all 4 files in to the right spots and tried to flash them. I’ve used Odin plenty of times and haven’t had any problems before but I am far from an Odin master. This time I just get stuck at file analysis. I’ve done the normal dumb stuff like latest drivers, get the same error on Odin 3.10.6 and 3.12, ran Odin as admin first then set phone to download and plugged it in. Odin is definitely recognizing my phone as it says added. Just can’t figure out what I’m doing wrong and want to get this damn phone on the latest everything so it will quit downloading updates and taking a **** on me. Any help is much appreciated!
Sorry about this replied to wrong phone.
Sent using SM-G891A & MultiCam Black Tapatalk.
jermo said:
Been having an issue with my ATT S7 when it goes to do some kind of OTA update and fails, then my apps start randomly crashing and of course I decide to reboot. When I reboot I get stuck on the white att screen. This is the second time is has happened, first time I just did a factory reset and was back up and running. Well today it went to do an update, update failed and I am back at a white screen again. I decided to start researching what the newest firmware was and can’t seem to get a straight answer. I also have no idea what bootloader I am on and so on…From what I can tell is PK1 is the newest firmware am I right?!? No idea where to check what bootloader I have…
So I decided I was going to just install everything from this thread in hopes to cure my issue https://forum.xda-developers.com/att-galaxy-s7/how-to/pk1-odin-files-t3522168
I downloaded all the files, deleted .rar off the end so Odin would recognize the files (did i do that right?), plugged all 4 files in to the right spots and tried to flash them. I’ve used Odin plenty of times and haven’t had any problems before but I am far from an Odin master. This time I just get stuck at file analysis. I’ve done the normal dumb stuff like latest drivers, get the same error on Odin 3.10.6 and 3.12, ran Odin as admin first then set phone to download and plugged it in. Odin is definitely recognizing my phone as it says added. Just can’t figure out what I’m doing wrong and want to get this damn phone on the latest everything so it will quit downloading updates and taking a **** on me. Any help is much appreciated!
Click to expand...
Click to collapse
When i flashed the APK1 files it hung on file analysis for about a good 5 min. I was fixing to reset and try again and it finally got past that part. I'm not sure why it took so long. The APK1 files are the latest files for the G930A. It is bootloader 4. What version of odin are you using.
dirtydodge said:
When i flashed the APK1 files it hung on file analysis for about a good 5 min. I was fixing to reset and try again and it finally got past that part. I'm not sure why it took so long. The APK1 files are the latest files for the G930A. It is bootloader 4. What version of odin are you using.
Click to expand...
Click to collapse
I've tried using odin 3.10.6 and 3.12.3...both always hang and i've waited way past 5 mins. I'll try again though and let it go for a long time, you do all 4 of them at a time right? Or do you do BL first, then AP and so on?
jermo said:
I've tried using odin 3.10.6 and 3.12.3...both always hang and i've waited way past 5 mins. I'll try again though and let it go for a long time, you do all 4 of them at a time right? Or do you do BL first, then AP and so on?
Click to expand...
Click to collapse
I did all of them at the same time. The only thing i did different than you was that i extracted the .rar instead of renaming it.
dirtydodge said:
I did all of them at the same time. The only thing i did different than you was that i extracted the .rar instead of renaming it.
Click to expand...
Click to collapse
Oh man that's exactly what the problem was lol I feel super retarded right now...anyway extracted the md5 files and it went through fine. I knew it had to be something ridiculous, thanks again everyone!
jermo said:
Oh man that's exactly what the problem was lol I feel super retarded right now...anyway extracted the md5 files and it went through fine. I knew it had to be something ridiculous, thanks again everyone!
Click to expand...
Click to collapse
I thought you just extracted the zip files to a folder and used them then to put into Odin slots. After unzipping they are MD5 files. At least that is what mine say after unzipping. CORRECT????
tailgunner9 said:
I thought you just extracted the zip files to a folder and used them then to put into Odin slots. After unzipping they are MD5 files. At least that is what mine say after unzipping. CORRECT????
Click to expand...
Click to collapse
I figured that was the case too but odin doesnt recognize .rar files. I looked at the files i downloaded and they were named '.tar.rar'. Odin recognizes .tar files so i figured id just delete the .rar and it would work but nope you have to open the rar files in WinRar or whatever program you like and extract the MD5 files. Then plug those MD5 files in odin and it will go through just fine. PK1 feels pretty sexy so far!
Hi everybody,
yesterday I found this news:
https://www.sammobile.com/2017/10/16/galaxy-j3-2016-android-7-1-1-nougat-update-released-att/
Here the official page:
https://www.att.com/devicehowto/tut...tep_KM1147672?make=Samsung&model=GalaxyJ32016
I googling for a bit and I found the file of that update, those 4 file are tar.md5 and it's possible to use them by odin. Unfortunate when odin try to install the new system it show this error: Rev. system incorrect magic string (or something very similar)
I extrac those file and try to install separately any img or bin partition using heimdall in ubuntu, but again system and sboot image give me this error: ERROR: Failed to confirm end of file transfer sequence!
I don't know why, considering that my phone it's exactly the model, it suppose to be easy install those file.
Anyone already try to install that update or someone can give me some advice about those error?
I really like to see my phone with nougat running and this lñooks like the best chance.
Hope someone can help with that.
Thanks
Root isn't working atm, not sure if it will without unlocking either. But it is downgradable back to mm... I only have the update.zip, ill upload it in a bit.
Where's the 4 files? I couldn't find it
DamienMc said:
Root isn't working atm, not sure if it will without unlocking either. But it is downgradable back to mm... I only have the update.zip, ill upload it in a bit.
Where's the 4 files? I couldn't find it
Click to expand...
Click to collapse
Hi @DamienMc, here a couple of link where find those filehope I can post those link without breaking any rules, if i do sorry and tell me please)
http://gsm-firmware.com/index.php?a=browse&b=category&id=10851 (paid)
https://androidfilehost.com/?fid=962021903579486981
I found the first link in the beginning so I've downloaded from there.
What do you mean with "Root isn't working atm"?
My phone it's already unlocked carrier. Witch version of android do you have for that update.zip?
The best I did was flashing the recovery, boot, param partition using the pit file inside of one of those 4 files. There also a folder with foto.zip file, but I can't use it for now.
Please let me know any ideas about how to flash that update.
I posted it here https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
It's the ota zip, edited by me. You need to be rooted and use flashfire. My edits unroot your device then the original update takes over. Pita but that's all I have. I'll look at the full firmware or try to pull it from Samsung again.
But yeah, I wasn't able to root the thing. Haven't given up yet tho
@Iurop
Full firmware installed just fine here (besides an eof error on AP, prolly cause of the fota.zip)... are you sure you're not j320ag?
A and AZ have the same magic string, but AG is different. And can't crossflash with Odin.
@DamienMc
You right my it's a J320AG I was hoping that the firmware works fine for me, but my knowledge for now it's not enough to figured out how to flash those file. Do you know if there's any chance to do it in some way?
I will try your update.zip. In case you work around those nougat file and figured out how to use it on j320ag let me know.
Thanks.
I am afraid your stuck until you get the official update.
While your device can use the same system files here, it cannot use the kernel. And a new kernel is required for nougat.
On top of that your device is now two updates behind the j320a.
Here a couple of screenshot of the firmware version I had right now.
I don't know if Samsung will update this phone to nougat. Will be great.
After flashing the version of your update.zip and make the update, witch version of firmware will be present?
Flashing my phone with a at&t version of the firmware can help in some ways? Or at&t only manage J320A and AZ?
Thanks anyway.
AG = AQB1
AZ = AQG1
A = BQI5
The update.zip is BQI5.
Your best chance would be to try and dd the firmware you posted to see if it boots. I know i tried the system.img, not sure if I did the whole thing. Super dangerous tho...or just wait it out
[EDIT]
After further thought, a real rom.zip might just work on AG...a good test could be to boot a stock boot.img from A or AZ. Won't be 100%, but it'll be a good indication.
Or run it thru kitchen and try it out, if not I'll get to it when I have spare time
[/EDIT]
DamienMc said:
AG = AQB1
AZ = AQG1
A = BQI5
The update.zip is BQI5.
Your best chance would be to try and dd the firmware you posted to see if it boots. I know i tried the system.img, not sure if I did the whole thing. Super dangerous tho...or just wait it out
[EDIT]
After further thought, a real rom.zip might just work on AG...a good test could be to boot a stock boot.img from A or AZ. Won't be 100%, but it'll be a good indication.
Or run it thru kitchen and try it out, if not I'll get to it when I have spare time
[/EDIT]
Click to expand...
Click to collapse
@DamienMc, here what I've try until now:
-try to flash boot.img from this stock rom J320AZTUS3AQG1 using PIT file from my versios AG and also using PIT file from AZ version = can't be flashed in any ways.
-flash boot.img from J320A_J320AUCU3BQI5_AT&T_USA_7.1.1 using my PIT file = flashed but after the reboot hang on J3 logo
I don't understand what do yopu mean with "Or run it thru kitchen and try it out", can you explain please?
Also I don't know if Samsung release an update to Nougat for all J320 or it just the AT&T carier to do it. For that reason I've been trying to flash.
@Iurop
Well its good it doesnt fail with 7.1.1 boot....hopefully we can get it going.
I suggested that you create a rom.zip from the system.img a kitchen. But it wasnt that simple, i think i have a working zip now but cannot test it until later...i will pass it to you when its ready
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.