Related
I've found two posts about a user wanting to flash firmware to erase the LDU(Live Demo Unit) and use the phone as a regular snapdragon S8/S8+. I have been given by my Assets Protection team at Target, both the S8 and S8+ demo phones because they were going to throw them in the compactor since the Samsung Rep told them to dispose of them. I asked if I could mess around with them and they obliged. I have no intention in trying to resell these phones, or use them with cellular service(I have an Axon 7).
I was wondering if anyone has any experience with getting these phones to work with firmware from other versions.
I was able to flash G955USQS2BRB1 with Odin, but I get a security error.
Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair / return for this issue may have additional cost
Click to expand...
Click to collapse
So essentially, the phone is bricked. I haven't tried anything with the S8(G950XU) because it has screen burn in from being on display for almost a year.
If this is something that the moderators feel is inappropriate and that I should return the phones to Samsung, please notify me and I will do so. My only intention is to use them for home(YouTube, Reddit, Facebook..etc.) so I don't burn up my Axon 7 battery. These phones don't even have a proper IMEI(all 0s)
So, with that said, are there any work arounds for this error?
Did you try Comsey Odin?
Yeah, I use three different versions of Odin because certain BL and AP won't flash with certain versions of Odin. I can't do a factory reset in Recovery because
MDM doesn't allow a factory wipe
Click to expand...
Click to collapse
ibphantom said:
Yeah, I use three different versions of Odin because certain BL and AP won't flash with certain versions of Odin. I can't do a factory reset in Recovery because
Click to expand...
Click to collapse
Maybe this is the answer https://forum.xda-developers.com/galaxy-s8+/how-to/testers-t3744200
Hello Guys i have been searching all over the internet for a few month, where do i find the boot unlock for this particular phone? I need this in order to root and install lineage OS custom rom
I really appreciate if someone has the information.
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?
ibex333 said:
CAN ANYONE HELP PLEASE? I need to unlock bootloader for Verizon SM-G930V
Click to expand...
Click to collapse
Emmalfal said:
I just picked up this model myself and find myself in the same boat. My developer options do list an "OEM unlock" option. Does yours?
Click to expand...
Click to collapse
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.
Droidriven said:
It doesn't matter, Verizon devices have locked bootloaders that can't be unlocked, don't waste your time trying, it isn't going to happen. Verizon devices have been this way for years now, I don't forsee that changing at any time in the future.
Click to expand...
Click to collapse
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.
Emmalfal said:
My device has the "oem unlock" button. Does that not matter? I was surprised as hell to find that.
Click to expand...
Click to collapse
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com
Droidriven said:
You can try it but I'm pretty certain that Verizon has it locked down. There is a root method for Verizon S7 and S7 edge but no TWRP or custom ROMs that I know of.
Verizon S7 / S7 Edge [Root Guide] SM-G930V SM-G935V [NO KNOX TRIP]
Hi, I am compiling this guide for rooting the verizon variant. I also hope to fill in some gaps in the other guides. I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU MAY CAUSE OR ENCOUNTER I did not develop this, I'm only telling you how to do it...
forum.xda-developers.com
Click to expand...
Click to collapse
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Emmalfal said:
Figured I'd give it the old college try. Got Odin to recognize the phone and went through the root process. All looked well until the very end. "Complete (write) operation failed."
Click to expand...
Click to collapse
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
How about an unlocked device that can be used on Verizon's network?
Droidriven said:
It might depend on what version/build number of stock firmware is installed on the device. That guide might be for an older version of a specific version. If what you have is newer than what the guide was written for, that might be why it failed.
Does it say anything in the guide thread about it requiring a specific stock firmware or specific bootloader version?
Click to expand...
Click to collapse
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.
Droidriven said:
How about an unlocked device that can be used on Verizon's network?
Click to expand...
Click to collapse
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
Droidriven said:
Try a version of Odin from around the same time the S7/S7 edge was released onto the market. Some versions work better with certain devices, as android evolved and as Odin gets updated to newer versions for newer devices, there are slight differences along the way that can effect how it works on older devices.
If the stock firmware that you are trying to flash is older than what was already installed on the device, it will probably fail due to not allowing the device to be degraded to an older version, it's a "security" measure put there to prevent you from installing a less "secure" operating system.
Click to expand...
Click to collapse
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.
Emmalfal said:
I've gone through a couple different tutorials and they all seem to link to the same files that I need to download. It's been frustrating because looking for proper files for a phone this old leads to a lot of dead links. I'm probably going to give it up soon, but you know how it is. There's always "one more thing" to try. I tell you, I'm going to research like hell before I buy another phone. I need to know for sure that it can be rooted. In this case, I inherited my wife's old phone and a quick search revealed that it ought to be a piece of cake to root. There's always some little detail that trips me up. I appreciate your help with this.
Click to expand...
Click to collapse
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.
Emmalfal said:
Yeah, that would work. It's been so long since I messed around with this stuff -- I've had the pixel for six or seven years I think -- that I've forgotten everything I once knew.
I'll look that up and try it out. Nothing to lose at this point. All I'm trying to flash at this point is the CF Auto Root Tar.md5, as per the instructions.
Click to expand...
Click to collapse
The vulnerability that CF autoroot takes advantage of may have been patched in newer versions of firmware.
I haven't been able to root any of my devices for last 4-5 years.
Droidriven said:
No, I mean does it say anything about it requiring a specific version of stock firmware or specific version of bootloader to be already installed on the device "before" you do the rooting process described in the guide?
Sometimes these kinds of things require your device to have a certain stock software version as a starting point before the device is modified. Most of the time, if the device is ever updated to a newer version, the specific exploit that was being used to root gets patched in the update, killing the effectiveness of the exploit used to root. From that point on, chances of rooting are nil.
Click to expand...
Click to collapse
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.
Emmalfal said:
Yeah, I've been careful to download files in keeping with my specific phone, not just the G930V but the longer version of that model number, which seems super specific. Nothing works. I've tried three or four different versions of Odin at this point, but they all either fail or get stuck somewhere in the process. Probably time to start searching for a new phone. I looked around for other ways to root this s7 but i'm not finding much. I rooted the PIxel with Magisk.
Click to expand...
Click to collapse
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device. Some guides/methods only work on specific build numbers of stock firmware or only work if a specific version of bootloader is installed on the device.
Droidriven said:
I'm not talking about model number version, I mean the specific build number of the firmware that is installed on the device.
Click to expand...
Click to collapse
Ah. I'll check that.
Emmalfal said:
And now, using the latest version of Odin (I somehow downloaded an older one the first time around) it got to recovery.img and just stuck there. An exercise in frustration as you had warned. I need a Verizon phone that can 100 percent be rooted. I'm using a rooted original Pixel now but that sucker is getting worn out.
Click to expand...
Click to collapse
The S7 *can* be rooted, with lots of limitations afterwards. It just can't be BL unlocked
It could be failing due to the usb port or cable. I have an S8 that i can no longer flash only because I don't have a usb port in my pc old enough to flash it. I assume the S7 is the same way
the boot.img file was loaded into my phone in order to get root after that it could not detect imei numbers. Although they are in fastboot. I tried many different firmwares for this phone, but there is no result! I ask for your help. I was left without communication (sorry for not being very clear. I don't understand Russian and don't understand English at all, that's why I'm writing through a translator
The first thing you want to do is STOP FLASHING random images. It sounds like you are going to cause more harm than good if you keep going.
Figure out which firmware you started on (WW, EU, CN) and get the raw firmware for it. Follow the instructions to flash the raw firmware.
If that doesn't work, then you may need to contact the manufacturer, BUT at least you will be restored to stock. I cannot promise they will help you, but it sounds like you did more than flash a boot image. The IMEI is not stored there.
twistedumbrella said:
The first thing you want to do is STOP FLASHING random images. It sounds like you are going to cause more harm than good if you keep going.
Figure out which firmware you started on (WW, EU, CN) and get the raw firmware for it. Follow the instructions to flash the raw firmware.
If that doesn't work, then you may need to contact the manufacturer, BUT at least you will be restored to stock. I cannot promise they will help you, but it sounds like you did more than flash a boot image. The IMEI is not stored there.
Click to expand...
Click to collapse
Tell me where you can find the pure CN firmware? This phone was presented to me in this form already. And they told what happened to him. I doubt that ASUS support will help me, since in addition to everything according to the owner, the EMMCCDL_GUI utility was used. So I ask for help from knowledgeable people here.
And most importantly, what to flash and how?
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
twistedumbrella said:
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
did not help(
What? So no one will help ???
Return the phone or wait until the methods exist.
Those are the only quick answers left.
twistedumbrella said:
Return the phone or wait until the methods exist.
Those are the only quick answers left.
Click to expand...
Click to collapse
It was opened. This is not an option either
If you purchased it used and the seller refused a return, it sounds like they were trying to recover what they could by selling their problem to someone else. It's likely they knew there wasn't a self-service fix right now.
Just to be clear, what you need is a low-level EDL restore. As it stands, one of the files required is not available to the public. If you have a local repair shop, they may be able to do it (and will likely charge a fee).
Do NOT pay someone over the internet. It CANNOT be done remotely.
I've been trying to flash my G900 (AT&T version), So far I've tried LGUP, LGUP Dev and The official LG flashing tool, My main goal here is to at least remove AT&T from the device as it's throwing me errors when I try to update from Android 10 to Android 11. Any suggestions? I've searched around and there doesn't seem to be much about thus specific device.
Divine_42O said:
I've been trying to flash my G900 (AT&T version), So far I've tried LGUP, LGUP Dev and The official LG flashing tool, My main goal here is to at least remove AT&T from the device as it's throwing me errors when I try to update from Android 10 to Android 11. Any suggestions? I've searched around and there doesn't seem to be much about thus specific device.
Click to expand...
Click to collapse
What are you trying to flash exactly, and how are you trying to flash it?
iBowToAndroid said:
What are you trying to flash exactly, and how are you trying to flash it?
Click to expand...
Click to collapse
Well basically I'm trying to crossflash the device with a clean firmware/OS
I have confirmed numerous times it should work fine, as the devices are identical; only distinction is firmware.
I have used all the LG flashing tools I can find, They all see, connect and flash, only to fail with an error, that's either blank or changes every time.
Divine_42O said:
Well basically I'm trying to crossflash the device with a clean firmware/OS
I have confirmed numerous times it should work fine, as the devices are identical; only distinction is firmware.
I have used all the LG flashing tools I can find, They all see, connect and flash, only to fail with an error, that's either blank or changes every time.
Click to expand...
Click to collapse
So which firmware are you trying to flash, exactly?
I have tried anyway with LGUP. A bug for protection does not allow anything. I want to upgrade to 11. Nothing at all. The dll I extract it from the Firmware and neither. Firmware from Lg-firmwares.com for this AT&T Velvet 5G.
dude you'll never install anything LG directly gives you since you can't unlock the bootloader
swaguduzo said:
dude you'll never install anything LG directly gives you since you can't unlock the bootloader
Click to expand...
Click to collapse
Uhhhh, the bootloader doesn't need to be unlocked in order to flash stock firmware. That applies to almost every model from every manufacturer
swaguduzo said:
dude you'll never install anything LG directly gives you since you can't unlock the bootloader
Click to expand...
Click to collapse
I understand what they say about bootloader unlocking. It is true the majority, the vast majority do not need it. But this AT&T device has made my life impossible to do so. I also can't find a way to unlock bootloader.
Please, someone who can give me a good tip, of what I have to do. On the other hand, can someone explain to me how to extract the KDZ from my own phone. I'm not talking about downloading a KDZ but about making a backup of the device itself. As you know, the bootloader is not unlocked and I would need a tool that allows it without having to root it.
I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.
Doesn't exist. Ideally, you would dump the firmware yourself from the phone.
Now that the phone is released, stock images should be available soon here:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
kobiandy said:
I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.
Click to expand...
Click to collapse
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?
Morgrain said:
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?
Click to expand...
Click to collapse
No it was never locked to begin with. Does this mean even original stock firmware( when released) won't work?
kobiandy said:
Does this mean even original stock firmware( when released) won't work?
Click to expand...
Click to collapse
That is highly likely, but don't let me stop you from trying. Maybe you will have success. Also keep your eyes out for the Android Flash tool or the Pixel Repair tool, once Google updates them for the P7 Pro. Big companies usually not have all the tools interconnected, so chances are that the Repair tool won't check for blacklisted hardware IDs, it's just important that under no circumstances you may connect to the Internet with that thing, IF you manage to get it running and as long as it runs stock.