-
Thanks, let me try that AT&T ROM. I have a very slow connection so it will take some hours to download. I will try it and go from there.
The problem is not only your slow connection, is the server itself who limits the speed of the download, being free and used by most of the users who provide ROMS.
That 7Z file that 7Z could not unpack, it seems it uses some different algorithm, maybe LZ4, and I believe I might have some success with Linux. If I can crack it I will try flashing that too. It has a fifth file called HERO2QLTE_USA_ATT.pit. What is it? Should I put that one in the fifth box of Odin?
No, forget that file you downloaded before. And don't input that PIT anywere, or you are really going to make it even worse then. PIT is the re-partition file for the phone, so it sets new partition allocations in the flash storage of the file, same as partitioning your USB drive, and that screws really everything. It was used in old versions of ODIN and I really don't recommend.The entire thing is a PITA because I have Linux and Win7 on the same machine and have to keep rebooting. In the meanwhile Win7 is wasting a lot of time with updates etc.
In the meanwhile I have the phone plugged into the USB and it repeatedly flashes the Samsung Galaxy S7 Edge splash screen. I can't turn it off and I am afraid of letting the battery run down so I keep it plugged in. By holding the three keys I can get it to download mode again.
If it flashes the logo it means it still have the bootloader intact, so it's not an Hard Brick. You are in the Boot loop mode currently.
Try what I said before:
Turn off the phone.
Press and then hold the Home and Volume UP keys, then press and hold the Power key.
When the Samsung Galaxy S7 Edge shows on the screen, release the Power key but continue holding the Home and Volume Up keys.
When the Android logo shows, you may release both keys and leave the phone be for about 30 to 60 seconds.
Using the Volume Down key, navigate through the options and highlight ‘wipe cache partition.’
Once highlighted, you may press the Power key to select it.
Now highlight the option ‘Yes’ using the Volume Down key and press the Power button to select it.
Wait until your phone is finished wiping the cache partition. Once completed, highlight ‘Reboot system now’ and press the Power key.
The phone will now reboot longer than usual.
If it doesn't work then do this:
Turn off your Samsung Galaxy S7 Edge.
Press and then hold the Home and Volume UP keys, then press and hold the Power key. NOTE: It doesn’t matter how long you press and hold the Home and Volume Up keys, it won’t affect the phone but by the time you press and hold the Power key, that’s when the phone starts to respond.
When the Samsung Galaxy S7 Edge shows on the screen, release the Power key but continue holding the Home and Volume Up keys.
When the Android logo shows, you may release both keys and leave the phone be for about 30 to 60 seconds. NOTE: The “Installing system update” message may show on the screen for several seconds before displaying the Android system recovery menu. This is just the first phase of the entire process.
Using the Volume Down key, navigate through the options and highlight ‘wipe data / factory reset.’
Once highlighted, you may press the Power key to select it.
Now highlight the option ‘Yes — delete all user data’ using the Volume Down key and press the Power button to select it.
Wait until your phone is finished doing the Master Reset. Once completed, highlight ‘Reboot system now’ and press the Power key.
The objective is to clean whatever is in the cache that makes the phone reboot constantly, reinstalling the software from factory that he have on the memory and reboot as new, since in reality nothing were written by the log on the image, just a failed connection. -
I downloaded G935AUCS4BRC1_7.0_4File_USA (AT&T).7z, which took quite a few hours, but then the 7Z program says it cannot uncompress it because [whatever] so no dice.
OK, using Linux I managed to extract those files and using Odin I managed to successfully get them on the phone. So it seems the problem was with the files I was trying to install.
The phone started up and required connecting to the Internet to continue. (Updates?) Then it requires me to open a Google account ... so I have to find "skip"in every screen.
So, the good news is finally I seem to have a "working" phone again. I am pretty much back to where I started two days ago except I have lost the few apps I was using. That should not be a major problem because I can reinstall them.
I am still downloading the file you linked to. But I understand that is the ATT version. Like the one I have already installed?
The one that refuses to install is a "neutral" one? Is that the one I want?
What do you suggest should I do next?
-
Ok Solar, excellent!
Yes that ones are the AT&T ones, and if they worked the phone yes is back to defaults. Now you know in case you screw how to do the roolback.
Now then it's up to you: You want to try to update again or leave it that way?
If yes update, then:
Open the Settings application on your Samsung.
Locate "build number" in settings. This is usually under the "System" option but varies for different devices.
Tap on the "build number" multiple times until you get a message saying developer options have been enabled.
Go back into settings and find developer options.
Find USB debugging and enable this option.
I forgot to check if the tutorials I sent to you had this, I rechecked and it didn't have. My mistake, I'm sorry for not checking really, it could have been a very expensive mistake.
If you can in the same menu look for OEM Unlocking and activate. OEM Unlocking is used if you want to install a custom, no official Samsung ROM, like the Lineage OS using TWRP . But for Samsung ROM is not needed, although being active doesn't make anything in this case, so activate just in case (trying to prevent errors again).
Turn off the phone then and the procedure will be again the same as before, hoping that this time you will have the correct rom again:Ok, by parts:
The drivers I talked was this ones:
https://www.progeeksblog.com/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
That's the ones you should install before you connect the phone in bootloader mode to ODIN. To enter in Bootloader/download mode: To do it, hold down the Volume down+Home+Power simultaneously for about 6 sec until Android warning sign appears on the screen. Release all buttons and Hit Volume up to continue.
Then after connecting to the PC a new device should appear in the Device Manager, check if the drivers are the ones from the Samsung that you download and install before.If not just with 7zip, right click on the exec with the drivers, and unzip the folder that says 20_NXP_Driver. or unzip everything and force the install of the drivers by that folder for the new device that pop up.
For instructions, this one is basically the best one if you use original Samsung Stock Firmware:
https://www.progeeksblog.com/how-to-use-odin/
When you connect the phone via USB in download mode and disconnect you should see messages popping up in the status window of ODIN saying ID something ADDED and ID something REMOVED.
On the file part where they say to put the firmware file in AP, in your case since you will have 4 files after unzip the firmware you download, you should do as in the XDA Forum, the link with the conversion from GT935A to GT935U.
https://forum.xda-developers.com/att-s7-edge/how-to/samsung-sm-935u-firmware-install-guide-t3411451
Here when you decompress the ZIP file it will give you 4 files each starting with letters: Put the AP_ on the AP_ field, the BL_ on the BL_, CP_ on CP_ and CSC_ on CSC_. The process should not take more than 10 min. After it says PASS in green, the phone will reboot, and you can disconnect after the configuring screen from android pops up (you can before, when you reboot, but as good measure I always disconnect when it starts the configuration screen).
Note from the XDA Forum:QuoteWhen using the second version of Odin, I encountered an issue where the phone would crash during setup just after the wifi screen. If you have any problems with either, please report back and let me know. Either way, this seems safe to try on the AT&T version of the S7 Edge. I am able to go back to the stock AT&T firmware I’ve uploaded in my other thread just fine. So if this doesn’t work for you, it’s possible to go back. I have went back and forth 4 times now, and met with success going to and from the stock AT&T firmware to this one each time. However as always, try at your own risk.
Have the original firmware from the phone too, the Stock AT&T for rollback in case of failure.
https://forum.xda-developers.com/att-s7-edge/how-to/sm-g935a-stock-oreo-odin-g935aatt4cre4-t3803860
Same way four files, each on their respective fields on the ODIN application for PC.
Anything more just ask.
And I hope that this time you give a success reply...
-
OK, did all that and it still will not load. Failure.
I did finish downloading the latest one (Samsung) and that one did load and that is what I have now. So it seems the AT&T and Samsung versions do load correctly but the first one you linked to (debloated?) does not work no matter what I do.
At this point I think I might as well stop wasting time on this and maybe just leave the Samsung version which I have right now and maybe remove by hand one by one things I don't need. I am back where I was when I started except I will need to install the apps I had.
What do you think?
-
Yes it's the best then, I agree totally, lets stop hitting the
. The Samsung one is good enough for removing the bloatware from AT&T
Regarding the apps that you had, since you don't use Google, for sure you use this website to download the APKs right?
https://www.apkmirror.com/
If not then there it is. If yes then regard this as white noise.
Again thank you for the patience with me, we both learn something new today. Specially me, from now I will read thoroughly before I post a link to help someone. Just because I know the procedure by head, I should check if what I post also have the same procedure the same way instead of reading some lines in diagonal and posting thinking it was OK.
That in this case could had resulted in an expensive ornament for the table. My fault totally and I'm glad it wasn't that serious and I'm sorry. I will take measures from now on. -
I appreciate your time and effort. Even if I have ended up where I started, I am familiarizing myself with the phone and with Android. To me it is very unfamiliar and uncomfortable and even the simplest things are long and difficult. I am used to my desktops and have no inclination towards phones but I guess I will have to get used to it. I was using an iPhone 4 and I was used to doing the few things I needed but now I am forced to transition to this Samsung S7 and learn everything all over again.
I would have been better off just leaving the phone with the OS as I got it because now I am having to get rid of stuff that the previous owner already had cleaned out. For me this is a pain because I do not know my way around Android and every little thing is a PITA.
Part of the problem I have is that I search Google for "how do I do X?" and I find many solutions which do not work on my phone because my menu tree is completely different. It is very frustrating. I just cannot find my way around the screens/icons. I will have to install and configure everything little by little.
I have downloaded Wechat.APK directly from Wechat.com to my computer. It's good to know apkmirror. I have probably downloaded from there before just by searching for specific apps. I will make a note of it. I have already downloaded WIFI Analyzer from there.
Now the problem I have is that I cannot transfer files from the computer to the phone because of that problem caused by trying to install the new Samsung driver in Win XP. There is no direct way to fix that because I cannot roll back the driver but I imagine I can modify whatever it needs in the Registry. The phone still works with other WIN XP computers but I don't want to have to fire up a computer just to transfer a few photos. Maybe I should start a separate thread about this although I am afraid it would get no response.
The battery is not very good and will need replacing soon. I have looked at videos of how to do it and, while I am pretty sure I could do it, I really do not feel like doing it so I might just wait even if it means carrying an external battery bank with the phone. Generally I wait to do these repairs when I am in China and I can save some money that way.
One thing I liked about older phones is that you could switch batteries if one was running low. You could just carry a spare battery in your pocket.
Thanks for your time and interest.
-
Now the problem I have is that I cannot transfer files from the computer to the phone because of that problem caused by trying to install the new Samsung driver in Win XP. There is no direct way to fix that because I cannot roll back the driver but I imagine I can modify whatever it needs in the Registry. The phone still works with other WIN XP computers but I don't want to have to fire up a computer just to transfer a few photos. Maybe I should start a separate thread about this although I am afraid it would get no response.
You can not uninstall the driver via clicking on the device in Device Manager and then Uninstall, checking the box that says remove driver?
So basically as on Windows 7:
Add Remove Programs, Uninstall Samsung USB Driver;
Restart and then connect the phone and uninstall the rest of the trash left behind as I said above? Sorry, the last time I used Windows XP was some time ago. I was a Certified Microsoft Windows XP Administrator, but with Linux and the new operative systems, the last time I used XP was like 2010.
I think that functionality was available on Window XP too, I'm sure. It is on Windows 7.
Don't also forget that when you connect the phone to the PC via USB it pops up a status bar on the phone asking you to change the kind of connection you want to use with USB.
-
Here is what happened as close as I can remember. Remember this is a Win XP SP3 machine.
Before I could plug in the Samsung phone and it would appear in the Device Manager with a Microsoft driver dated 2006 and photo transfer worked fine.
Then I installed the Samsung driver and photo transfer stopped working. The phone no longer appears in the device manager so there is no driver there to roll back.
Here is my interpretation: The Samsung driver is newer and uses something called MTP (media transfer protocol) which is newer and does not work with Win XP.
Now the phone is (virtually) not connected directly to the computer but to the MTP thing. Since MTP is not working the phone cannot connect but the problem is not with the phone driver but with the MTP software. That is why the phone no longer shows up in the Device Manager. Look at the graphic in post #13.
So it seems to me the solution would be to remove the new Samsung driver and, very especially, the MTP software so that when I plug in the phone again it would detect it the old way and use the old driver.
The problem is there is no easy way that I know to remove all that stuff I installed. I have no idea how it works. I have only messed up one computer so I can always compare Registry entries with other computers I have still running XP.
I do not understand why it would install the driver and MTP in a system that does not support it. You would think before installing anything it would check that.
On second thought and looking again at the error message I wonder if the MTP is just missing something I could supply and then it would work...QuoteThe required section was not found in the INF
-
Well, the MTP driver is missing...
Try this ones, this ones are the Windows XP drivers. You may have to force installation:
https://www.filehosting.org/file/details/827601/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
It was me who uploaded this file, so its without virus.
Please confirm the size and date of the file with the current one you have from before. -
Well, the MTP driver is missing...
I don't think it is missing as much as misconfigured. Reading around posts from people who have similar problems many say they need to install Samsung KIES but I am reluctant to install it on fear of making things worse.Try this ones, this ones are the Windows XP drivers. You may have to force installation:
https://www.filehosting.org/file/details/827601/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
It was me who uploaded this file, so its without virus.
Please confirm the size and date of the file with the current one you have from before.
It requires my email which I am not willing to do. It is probably the same one I already installed. V1.5.51.0, MD5=78043F66677A917948C99ECDEDD73570.
At any rate I think it is more a problem with MTP than with the phone driver itself. It seems they are different things and Windows is complaining about the MTP .inf file being incomplete.
It complains there is a section missing in the INF file. I think I found the relevant INF file but I have no idea what might be missing. I assume it is the same file for Win7 where it does work. Maybe WinXP needs something more.
I have found ssudmtp.inf which I believe is the relevant inf file and I have found a single ssudmtp entry in the registry defining the driver.
I wonder if deleting (hiding) these two items would make windows resort to the old driver.
Or maybe I can find out what is missing from the INF file and try to provide it.
It seems this problem is not restricted to Win XP and happens to other versions of Windows. One post saysQuoteThe best way to transfer files from a Samsung device to your computer when it is not being recognized as an MTP is to use Samsung SideSync. Samsung SideSync has the MTP driver built into the program so it will recognize your device as a MTP.
SideSync requires Windows Media Player 11 or above. WTF?
https://www.samsung.com/us/sidesync/
-
You don't need to use your email...
https://temp-mail.org/en/
This website generates a temporary email, insert that email, see the website for the reply with the link, then download and close the browser. Done you have the file, and the website have a fake email that doesn't exist anymore... I uploaded the same way...
1.7
But yes, it may be other cause. I can't talk about the other apps like SideSync and Kies, I know that they work well on Windows 7, on XP never tried.
-
Installed new driver. Still get same error.
-
Jesus, what the fu#k is happening with this... What did your computer have against you?
I've been searching and what I found was the same as you.