Hey! So I just had my first success, used Odin to repair an old S8 that was stuck in safe mode by reimaging with a stock firmware. On to my next task of wanting to update these phones to a newer OS as it seems 9 is as high as they go from manufacturer.
I understand that being Canadian devices (SM-G950W) I can't unlock OEM, and so I have to use something like https://forum.xda-developers.com/t/samsung-galaxy-s8-root-snapdragon-sampwnd.3659305/ to root it. Am I correct in thinking that once I root it, I can load a custom OS (like Lineage or Pixel Experience)? Or is that still a no because no OEM unlock.... I don't need them to be able to connect to cell towers, I won't be putting sims in them, just WiFi so the kids can play.
Any info would be appreciated while I bang away at them. Thanks!
Related
What used to be a simple patch to permit AT&T Galaxy Tabs to download apps from sites other than the Google Market is no more. We recently got our Tab back from the Samsung repair facility and it was wiped clean and loaded with a new Android version that now puts your Tab in an endless boot loop if you attempt to patch the config setup to permit downloads from outside Google Market.
Simple solution: DON'T BUY AT&T-BRANDED GALAXY TABS.
If there were some sort of unlimited data plan, this kind of behavior might be warranted but since AT&T charges by the amount of data you consume, there's really no excuse for crippling these devices... other than just being assholes!
Not entirely sure what you're referring to here. I have an AT&T SGT and it works just fine with sideloaded apps.
Did you run SuperOneClick root and then enable non-market apps?
Either way, nuke that horrid stock ROM with one of the Euro roms and you'll never have to worry about AT&T's crippled version again.
Yeah, but...
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
What version of firmware did your Tab come back with?
What method did you attempt to enable side loading?
I find this very hard to believe because every single ATT Android device to date has been able to side load after a simple 1 bit edit of the device settings db.
I believe that you had problems with the SuperOneClick app but there is a much cleaner / safer way to do it.
Sent from my SGH-I987 using Tapatalk
NerdUno said:
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
Click to expand...
Click to collapse
I don't believe my ATT SGT came with a protected bootloader, and if I'm not mistaken, AT&T hasn't released any firmware updates via KIES or OTA. So while there's always the possibility of Samsung "screwing" us all with that mess, it's only been seen on the leaked firmwares. Not that I don't put it past the big blue DeathStar to opt to use something like that to prevent people from avoiding their preloaded garbage....
I'm happy I liberated my device from the clutches of the Evil Empire, and will gladly look to XDA for my future upgrade paths.
Could just be a bad software flash from factory. A number of t-mobile vibrants couldn't get to restore via volume up/down power because of a buggy flash file they put on a certain build date
Sent from my Galaxy Tab
So my gf bought herself a used S7 SM-G930A off eBay. I'm honestly unfamiliar with the S7 or the ROM scene as things apply to is so I'm coming into this at a disadvantage (I'm on an S5). However things don't seem quite right:
1) on the boot screen, there's an unlocked padlock icon with "Custom" under it
2) There's nothing for Software updates under About Device
3) Build number MMB29M.G930AUCS2APC2, Android Security patch level "February 1, 2016" (out of date?)
4) Repeatedly gets message: "Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes"
I checked some videos and I don't think this is a fake S7, but maybe it was rooted and/or had a custom ROM in a previous life. Honestly, if it's been rooted she really doesn't need that. I'd prefer to take it back to unrooted stock for her so she can have the normal consumer experience, getting carrier updates OTA, able to use Android/Samsung Pay, etc. Can anyone shed light on the state of things and guide me into getting her to where she needs to be? I'm ok running ODIN but am having trouble finding the latest stock ROM. Thanks.
(I apologize for not doing the normal amount of due diligence searching I'd normally do before pleading for assistance, but she's in a pickle now being phone-less until we can get this working).
The first thing you should do, if you haven't already, is check the IMEI.
https://swappa.com/esn
Many sellers on eBay buy cheaper phones and install the ATT rom. If it is a genuine att phone, you can restore it to stock by flashing software through Odin
Here is the latest post I found with the latest ATT software:
http://forum.xda-developers.com/att...are-g930aucs4api2-bootloader-4-t3481957/page2
This thread shows how to root and restore the galaxy s7:
http://forum.xda-developers.com/ver...s-root-install-xposed-unroot-t3411039/page206
Thanks, Luke. I just tried that link and the IMEI comes up clean and correct for the model.
As is my style, I didn't stop working on it after I posted that last night. I ultimately did find all the pieces for a stock re-flash, getting ODIN set up in a Windows 10 VM. It seemed to work, not only giving the phone a slightly newer firmware and security update, but fixing all the weirdness. So with any luck she's good to go. I suspect the phone was customized/hacked up a bit by the previous owner, and he didn't do a proper job returning it to 100% stock. Thank goodness she had someone like me who could fix it for her, otherwise an normal innocent buyer would've been in for a world of frustration and hassle.
Hello!
I've never used a phone that is specific to one carrier. All my phones have been unlocked.
My girlfriend has a Verizon Samsung S7 edge and I've convinced her to ditch Verizon and go with StraightTalk with a Verizon compatible SIM. I hadn't considered software updates since I typically update my phone directly from the manufacturer or by flashing a custom ROM.
is it still possible to install an OTA update to her phone since she no longer has an account with Verizon? Or do i have to unlock her bootloader, download the latest update, and use Odin to manually install it?
Her phone is not rooted and it will be a battle to convince her to let me do it.
Any help would be greatly appreciated!
Probably the easiest for you is to install on the phone and on PC the Samsung SmartSwitch: https://www.samsung.com/us/support/downloads/
Inside that app, while the phone is connected via USB to the PC, if there are any updates for the phone, they will show up and you can install them.
BTW, if you want to change the firmware to "U" version, Odin flashes the official files without root, phone remains in original untouched state.
Personally I have flashed "U" firmware over my "V" S7 Edge, just to gain access to hotspot, using this thread to make the switch (I was on Nougat then). I am using Total Wireless (same SIM as StraightTalk, both owned by Tracfone) and, since then, I got the updates for Oreo and the following security update.
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
UPDATE!
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
MajinMight said:
My wife's camera stopped working on her phone. I read flashing back to a previous firmware might fix the issue. I thought it was worth a try (and easier) before physically cracking the phone open and examining the hardware. But boy was I sure wrong about that!
I've read so much crap about this within the past few hours my head could explode. But I think the problem is trying to source the correct firmware.
This is a SM-G935V with a snapdragon processor in it according to spec websites.
The baseband version is: G935VVRSBCTC1
I haven't figured out how to find the current PDA version on the phone yet, but when I was trying to flash it with random firmware with Odin, the phone screen gave me error message: Fused 11 > Binary 4
From what I read, I understand that to mean I'm trying to flash binary 4 over 11 and that won't work. The flash only works if the number is greater....or I'm hoping maybe it will work if the number is the same. I would be happy just to flash Android 8.0 at this point in any form just to see if the camera starts working again. I've already tried a factory reset, clearing camera app data and cache, booting into safe mode, and resetting phone settings to fix the camera - nothing worked.
Could anybody please help me figure out my current PDA version on the phone? Or help me source the correct firmware? I'm starting to think it might be easier just to root the phone and install that ONE UI with android 9 or the Lineage OS with Android 10. But I've never rooted a phone before, this is my first attempt at any of this and to be honest this phone is not giving me the confidence I need to attempt the root and new OS. I can't even get the current firmware to reinstall.
Any help would be very appreciated. Like I said, I've stayed up all night and I'm so freaking tired at this point. But I feel like I'm soooooo close.
I have an SD card with Magisk, no-verity-opt-encrypt, and twrp ready to go. I have Odin ready and installed Samsung USB. Do you guys think I should just try another firmware and root the phone? Any links to firmware that don't take 12 hours to download would be appreciated.
Click to expand...
Click to collapse
UPDATE #2
As you can tell I haven't given up yet. I found my current firmware version for download on a different website:
https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/"]https://samfrew.com/download/Galaxy__S7__edge__/b3kj/VZW/G935VVRSBCTC1/G935VVZWBCTC1/
It's another slow download option which really sucks. But I'll be able to test If I can flash the same firmware to the phone (not technically a downgrade and carries the same fused binary). So we shall see. If this doesn't work I'll be looking into the other android 9 or 10 roms and rooting the phone.
Thanks, Derek
MajinMight said:
I found the PDA version with that handy "Phone Info *Samsung*" app in the play store.
The PDA version is G935VVRSBCTC1 5TH DIGIT FROM THE RIGHT GIVES US THE FUSED BINARY "B". I guess when they got past the number 9 the switched to Alpha characters. I found some "A" firmwares on Updato.com. But I didn't see any with a "B". So there's a good chance the one's I'm trying to download over 12 hours right now won't work.
I also scrolled over to the "Hardware" section in the phone and it asked for access to the Camera. I gave it access. But now the field is blank/empty. I didn't populate any info on the Camera. I don't know if that means anything just wanted to point that out. Could still be firmware or hardware as far as I know.
Thanks, Derek
Click to expand...
Click to collapse
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Dang! Well thanks for the info! I guess all the videos I've seen with S7's and custom roms have not been done on the US-Verizon phone. What a bummer. Well this was a major learning experience at least.
My only idea now is to crack her open and make sure the camera didn't come unplugged from a drop. I also seen camera replacements were really cheap online. I don't know if it's worth my time....we are due for a phone upgrade anyway.
SkylineDriver said:
TL/DR your full posts but I will cut to the chase on some points. If your phone is SM-G935V (US-Verizon) then you:
1) can NOT root binary B firmware. Binary A (10) yes, B (11) no, at least not until the ENG file becomes available- IF it ever comes. Official S7 support is next to dead.
2) even if you were lucky flashing binary A firmware and successfully rooted, you still would NOT be able to flash ANY custom ROM's such as Lineage. Also, Magisk is useless and will not work on our phones either.
US-spec Snapdragon phones are bootloader locked. There is no workaround. Locked bootloaders prevent flashing custom ROM's, kernels, etc. We are lucky we have root access and it took years just to get that. Bootloader unlocking will never happen for US-spec S7. Much as I love my S7e, if I ever have to replace it I will never get another US "Crapdragon" that you can't do anything with.
I do not know what the issue is with your camera. Maybe other forum members will have ideas. I do wish you luck getting everything back to normal.
Click to expand...
Click to collapse
Hi there,
I have a Samsung SM-A515x LDU phone, its legally obtained with the right permissions, I also understand it is a 6.X inch tablet as it has no imei or cellular capabilities, I'm looking to do this for the sole purpose of getting updates and getting recent security updates also.
Phone is "clean" I have removed the retail mode lock so phone is fully usable, not rooted and not installed a customer recovery yet.
I live in the UK and spec apps show the phone has having the exynos chip, I'm making the assumption that its likely to be an SM-A515F model (the version it would of been shipped with was a515fxxu1askj/a515foxaskj) But, before i flash all this info through odin, How do I go about making a full backup of the device incase I need to do a rollback, I read about NAND backups but will this truely save me if it gets soft bricked into a boot loop?
attached are screenshots of my update page and my software info page, hopefully this helps.
Yeah I probably would not waste too much time on this device, and no you cannot flash unlocked firmware onto an X variant. The only thing you can do is try to get the demo mode password, but even than you still wont receive any software updates as these "X" variants run on their own update channel.