Database Info

[Q] My atrix 2 is on the edge of dying. please help.

I'm really sorry if this doesn't belong here.
My atrix 2 (MB865 from Singapore) updated by OTA to ICS then rooted successfully and I installed custom roms (scv7 and swifty etc) and even mods (xLoud and Beats) but in CWM (Bootstrap + cwm-on-boot script) it would usually say ''installation aborted'' whenever I tried to flash a custom rom, which is pretty weird since I was using the correct roms for my device.
One day I decided to go back to stock ICS by flashing a ics fzw in RSD Lite 6.0 (I tried flashing 6.7.2_EDEM-18-SEARET_cfc.xml and 6.7.2_EDEM-18-ASIAOPS_cfc.xml) but every time it would stop at step 14/20 ''writing system.img'' but the progress arrows would still keep moving. So after an hour of waiting, I disconnected the phone from the usb cable and I got the black screen with Flashmode (Flash Failure) with ''cannot program'' and ''battery low''. Now the battery died and it won't even charge when I connect it to the wall adapter, it would only boot into the flashmode (flash failure) screen and when I turn it off and try to to it on again it won't. I don't think it's hardbricked because when the battery was still on, I could turn it off and boot back up into fastboot with options like normal boot or go to the stock android recovery.
What do I do now?

Hey, so you have 2 issues here. 1 is that your battery is dead, and you need to charge it.
you can try to find the diy method posted here a while ago, but be careful as you could fry your phone if your not careful. or you can find another phone to charge the battery in (another a2). if neither of those work, you can buy an external charger online to do it.
2 is the issue of why it is not flashing. make sure you are using the exact right fxz for your phone version, there are many available.

lkrasner said:
Hey, so you have 2 issues here. 1 is that your battery is dead, and you need to charge it.
you can try to find the diy method posted here a while ago, but be careful as you could fry your phone if your not careful. or you can find another phone to charge the battery in (another a2). if neither of those work, you can buy an external charger online to do it.
2 is the issue of why it is not flashing. make sure you are using the exact right fxz for your phone version, there are many available.
Click to expand...
Click to collapse
Thanks alot man, i've stopped stressing, I'll find a way to get the battery charged. But then the problem is in how to escape this damned AP Fastboot Flash Mode "Flash Failure" screen. I mean the fxz I mentioned should work (they match the phone's specifications) but whenever I use FDS Lite 6.0 it always gets stuck at step 14/20 "system.img" for like an hour, is it maybe a drivers problem? Should I try another computer? Should I claim warranty for it even though it's rooted? Thanks in advance

aligex said:
Thanks alot man, i've stopped stressing, I'll find a way to get the battery charged. But then the problem is in how to escape this damned AP Fastboot Flash Mode "Flash Failure" screen. I mean the fxz I mentioned should work (they match the phone's specifications) but whenever I use FDS Lite 6.0 it always gets stuck at step 14/20 "system.img" for like an hour, is it maybe a drivers problem? Should I try another computer? Should I claim warranty for it even though it's rooted? Thanks in advance
Click to expand...
Click to collapse
I am going to be totally honest here. You are using the wrong fxz file for your phone. I see you are trying to flash the SEARET fxz, that is for south east asia phones ONLY, and would not work on say an AT&T phone that was purchased someplace else and just being used there.
First off what region/country are you in?
Second does the phone have the AT&T logo at the bottom front of the phone?
Did you get the phone through proper channels in your part of the world, or did you buy it on ebay or something?
Yes all of these things matter. You will need to do the McGyver method to charge your battery (lkrasner mentioned it as the diy method). It is in this forum, just Search for it.
After you get us the information I asked for above we will be able to better help you.
Also one last thing to check is to see if the MD5sum matches. If not you prolly have a corrupt download and that is why it may not be working as well.

With respect to our developers this will allow you to flash without a battery. It does nothing else useful but does get around the low battery issue
http://forum.xda-developers.com/showthread.php?t=1910027
There are other forms however being in Singapore may limit your options. Remember Google is your friend.

jimbridgman said:
I am going to be totally honest here. You are using the wrong fxz file for your phone. I see you are trying to flash the SEARET fxz, that is for south east asia phones ONLY, and would not work on say an AT&T phone that was purchased someplace else and just being used there.
First off what region/country are you in?
Second does the phone have the AT&T logo at the bottom front of the phone?
Did you get the phone through proper channels in your part of the world, or did you buy it on ebay or something?
Click to expand...
Click to collapse
To follow up on that, there is a simple way to check if your Atrix 2 is from Singapore. Open the back cover, remove the battery, and look for
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you see that, your phone is indeed a Singapore version, and the SEARET fxz is the correct one to flash.

matthew5025 said:
To follow up on that, there is a simple way to check if your Atrix 2 is from Singapore. Open the back cover, remove the battery, and look for
If you see that, your phone is indeed a Singapore version, and the SEARET fxz is the correct one to flash.
Click to expand...
Click to collapse
That is great information! Thanks!

LG G3 D850 is stuck on boot loop Error 570/8130

vI accidently flashed the TWRP recovery image to my kernel and ever since then my g3 been stuck in this awful boot loop that won't even pass the LG logo.
I've been looking to find different ways to successfully unbrick my g3 and I keep running into the LG Flash Tool. I downloaded it but I cant seem use it because I don't have the .KDZ file appropriate for my phone.
if anyone knows of a different method of unbricking my phone please help, or if you know where I can find the .kdz file appropriate for the D850
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

12345678910111213141516 said:
I accidently flashed the TWRP recovery image to my kernel and ever since then my g3 been stuck in this awful boot loop that won't even pass the LG logo.
I've been looking to find different ways to successfully unbrick my g3 and I keep running into the LG Flash Tool. I downloaded it but I cant seem use it because I don't have the .KDZ file appropriate for my phone.
if anyone knows of a different method of unbricking my phone please help, or if you know where I can find the .kdz file appropriate for the D850
Click to expand...
Click to collapse
I'd suggest you follow the actual guide.. - http://forum.xda-developers.com/showthread.php?t=2785089 ... If you follow it you'll see there is two different methods and that the D850 AT&T version is TOT method only and in which you download the zip, extract it and flash it.

hyelton said:
I'd suggest you follow the actual guide.. - http://forum.xda-developers.com/showthread.php?t=2785089 ... If you follow it you'll see there is two different methods and that the D850 AT&T version is TOT method only and in which you download the zip, extract it and flash it.
Click to expand...
Click to collapse
You're right. I didnt see that first time but have tried that method prior to moving on to the .kdz one. The reason why i did so was because the LG FLASH TOOL would stop working. Im not sure if its because im on windows 10 or what.

12345678910111213141516 said:
You're right. I didnt see that first time but have tried that method prior to moving on to the .kdz one. The reason why i did so was because the LG FLASH TOOL would stop working. Im not sure if its because im on windows 10 or what.
Click to expand...
Click to collapse
Windows 10 can cause issues. But if you have the D850. Tot is the only way.
Sent from my iPhone using Tapatalk

i was able to flash via LG flash tool TOT method fine no more then an hour ago running windows 10. Keep in mind like that OP says "it could take up to 45 mins".. although i flashed successfully it did take near that amount of time.. GL

First things first, can you go into download mode or not? If the answer is yes, then you have to tell where exactly does the Flashtool stop? Because the only method with d850 is tot method. Did you connect it on port 41 or not? If yes, have you provided it with proper tot file and dll? If yes, then Does the flashtool stop at ~ 6% where it says it cannot recognize your phone model, or @ ~ 13%, where it says it cannot go into download mode? You have to be more specific in describing your problem. If the answer is no to the first question, then how does windows recognize your phone? Is it connected as Android Device, or QDLoader 9008, or QHSUSB_BULK?
In my view, if you have just messed with the kernel (boot) partition, you should still be able to go to download mode and flash the correct firmware by following the tot procedure detailed by hyelton.

stops at 6%(cant change to download mode)
unikorn74 said:
First things first, can you go into download mode or not? If the answer is yes, then you have to tell where exactly does the Flashtool stop? Because the only method with d850 is tot method. Did you connect it on port 41 or not? If yes, have you provided it with proper tot file and dll? If yes, then Does the flashtool stop at ~ 6% where it says it cannot recognize your phone model, or @ ~ 13%, where it says it cannot go into download mode? You have to be more specific in describing your problem. If the answer is no to the first question, then how does windows recognize your phone? Is it connected as Android Device, or QDLoader 9008, or QHSUSB_BULK?
In my view, if you have just messed with the kernel (boot) partition, you should still be able to go to download mode and flash the correct firmware by following the tot procedure detailed by hyelton.
Click to expand...
Click to collapse
I followed step 7 and at step 10, I press down power button and it starts and stops immediately at 6%(cant change to download mode).what can I do?

Really confusing softbrick (small reward offered for fix)

TLDR: LGUP will just straight up not recognize my G5 no matter what. I'll give you five bucks on Paypal for a solution, if that means anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi guys, I try to avoid posting, but I've searched high and low for an answer and I really can't find it.
I've got a T-Mobile LG G5 H830, that I have recently rooted and installed TWRP on it. Last night, I decided to try changing a value in build.prop, stupidly without making a backup first and after I changed the value and rebooted, stuck at T-Mobile bootscreen, go figure. All I did was change a value from false to true for adoptable storage..
Anyway-- I tried factory resetting, I tried flashing that FLUENCE rom I found somewhere here on XDA, I've tried just about every thing I could, before I gave up and decided it would be easier to just revert back to stock and unroot. I wasn't really utilizing root for more than Titanium Backup anyway.
To the point; I've got the LG UP program installed, I've got the DLL for it installed and inserted, and the appropriate .tot file to flash it back to factory default. No matter what I do, no matter how many different COM ports I try, different drivers I've tried etc, I cannot get it to read my phone in download mode. ADB mode works in TWRP still, but this is driving me insane. The only other phone I have is a busted up BlackBerry Priv, and I want this phone working again asap.
If someone can shed some light on whatever the hell I'm doing wrong, it would mean the world to me.
Please.
P.S: yes I've tried just about every USB port on my computer, and I've tried restarting Windows many times.

you have tried jiggling it?

You know what? Hell, if someone finds me a working solution to my problem, I will personally paypal them five dollars. I just want this fixed. I've had LG G3s brick on me obnoxiously and then never come back from it, I don't know what it is about LG phones.. Samsung phones, Nexus phones, and basically any other Android phones I've worked on aren't nearly this hard to restore and repair.

speedanderson said:
You know what? Hell, if someone finds me a working solution to my problem, I will personally paypal them five dollars. I just want this fixed. I've had LG G3s brick on me obnoxiously and then never come back from it, I don't know what it is about LG phones.. Samsung phones, Nexus phones, and basically any other Android phones I've worked on aren't nearly this hard to restore and repair.
Click to expand...
Click to collapse
Use the twrp restore file in the development thread it will revert your build prop back, and from there your phone will work again. Editing build prop is not advised on the H830 has been discussed on numerous threads even before root was established. At least it's only a soft brick .

Have you tried jiggling it perhaps?

so did @wolfu11 get the 5 bucks? his solution should have fixed it.

autoprime said:
so did @wolfu11 get the 5 bucks? his solution should have fixed it.
Click to expand...
Click to collapse
I don't know if he's been back on since his initial post.

wolfu11 said:
I don't know if he's been back on since his initial post.
Click to expand...
Click to collapse
Last Activity: Today 12:52 AM
good luck :fingers-crossed:

autoprime said:
Last Activity: Today 12:52 AM
good luck :fingers-crossed:
Click to expand...
Click to collapse
Not holding my breath lol. That's why I declined any of the root bounty.

Try manually pointing to either the lg drivers, or adb drivers had that same problem when trying to root H830.
Sent from my LG-H830 using XDA-Developers mobile app

IDK if u fixed it or not, but i have a simular issue where LGUP does not recognize my phone. i'm guessing it could be the buildprop could have broken it. i have factory reset my phone, but upon turning on wifi, the phone crashes and i need to factory reset. i am rooted and retain root. My guess is that changing the buildprop causes the phone to be unrecognized. I did backup my buildprop but its stuck in an encrypted backup. Thanks alot gooogle...

Same problem here
I am having the same problem but I never touched my build prop. I rooted and decided to install cm14. When i flashed, none of my partitions are mounting and phone would not boot. I put stock back on and flashed tot and tried mounting partitions and nothing. Now computer doesn't recognize it as well as it will not boot into recovery or android.

I have seen this and I think I fixed it by disabling one of the two, in device manager. 1st listed, iirc.

Barsky said:
I have seen this and I think I fixed it by disabling one of the two, in device manager. 1st listed, iirc.
Click to expand...
Click to collapse
ill give it a shot, thanks

Bricked MT6577 SoSoon/Senq X8 Elite 3, NO USB Debug/ADB, Stock Recovry No Roms to D/L

I've had an MT6577 phone sitting around for a few years now that's been stuck in a boot loop. My phone karked it today and this is the only device lying around, hoping it can be revived some how to save a few dollars.
It all happened one time when I tried to use an app to install a new font just to see what it looks like.
Seems to be the most obscure thing ever made as it has many names and models all with 0 firmware available. Typically SoSoon X8 Elite 3 shows up as the most common make but I recall the original box having Senq X8 Elite on it.
The bad?:
USB Debugging is almost certainly off because ADB can't find a device no matter if I just plug it in off, in bootloop (shows 2 drives on my PC that are not ready to be used in this stage), fastboot mode, recovery (install update from ADB)
Questionable root, one of those generic one click apps.
No stock or custom roms available any where that I have found from searches here and there over the last few years
I tried to follow a tutorial to port an MT6577 rom but I would need the kernel off the phone, which can't be done to my limited knowledge.
No custom recoveries available, running Android System Recovery 3e. Can't use TWRP MTK 1 click install on my PC because the device needs to be fully booted to work.
The good?:
Fastboot seems to work as it does show the device in the command prompt "fastboot devices"
I think the bootloader was unlocked at some point, no idea on the relevance of that.
Any information on if/how to sort it out is greatly appreciated.
Last ditch effort to try revive it because it was decently usable for what it is, hoping that someone on here has one lying around somewhere.
Will add more information as I remember and reply to any responses asap
Thanks for your time

Hello have you tried a hard reset so far ?

-Hope- said:
Hello have you tried a hard reset so far ?
Click to expand...
Click to collapse
I have, through the recovery "Wipe cache partition" and "Wipe data/factory reset" have been done a few times as I've tried different ways to try and fix it

can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations

-Hope- said:
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
Click to expand...
Click to collapse
Good news: Tired it
Bad news: Nothing happened
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also tried "getvar all" which according to a post on a xiaomi forum, is an MTK specific command, returned nothing anyway.
Just showed the "..." until I pulled the USB cable out.
Thanks for the suggestion, guess that's a pretty significant strike against any kind of fix for it.

the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope

-Hope- said:
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
Click to expand...
Click to collapse
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.

weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too

weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the whole system.img unless you have TWRP or can sideload apps in the recovery that you have.
Sent from my SM-S903VL using Tapatalk

-Hope- said:
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
Click to expand...
Click to collapse
Thank you for finding this, much closer than anything I've ever found. From what I can see on it, it's really close spec wise. I'll download it and have a look through the files before trying it.
Droidriven said:
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the while system.img.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did try that. I have all kinds of zips that could supposedly be flashed with the stock roboto font as well as the file itself ofcourse but I could never get fast boot to so anything with it. Based solely off the assumption that all android devices use it as the default, and assuming that the app was just renaming custom fonts to Roboto or something along those lines.

flashed wrong bootloader

Idk what to do I flashed the wrong bootloader on my S7 (snapdragon) through flashfire and now I get a black screen with a blue LED with a green LED slowly blinking behind it. How to recover? Right now I'm just letting it die. Can't hard reset either.

rifek4 said:
Do a download mode is working for you?
Click to expand...
Click to collapse
Nope. Sadly. I get no response from the phone whatsoever. I heard a USB jig can fix this but i need to make sure before i buy..

savagevegeta said:
Nope. Sadly. I get no response from the phone whatsoever. I heard a USB jig can fix this but i need to make sure before i buy..
Click to expand...
Click to collapse
USB jig doesn't work on the S7, got one here
Probably gonna have to take it somewhere for repair unless there is a program similar to SP Flash Tool (Smart Phone Flash Tool) which can flash a seemingly dead device, for the S7

*Detection* said:
USB jig doesn't work on the S7, got one here
Probably gonna have to take it somewhere for repair unless there is a program similar to SP Flash Tool (Smart Phone Flash Tool) which can flash a seemingly dead device, for the S7
Click to expand...
Click to collapse
Even a completely dead one? I don't want to have to buy a replacement motherboard, but it looks like i HAVE to. I was counting on the usb jig working, but i guess not. Not even my PC can recognize it. When i plug it it, nothing happens. Do you know of anyway i can revive it?

savagevegeta said:
Even a completely dead one? I don't want to have to buy a replacement motherboard, but it looks like i HAVE to. I was counting on the usb jig working, but i guess not. Not even my PC can recognize it. When i plug it it, nothing happens. Do you know of anyway i can revive it?
Click to expand...
Click to collapse
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult

*Detection* said:
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult
Click to expand...
Click to collapse
I am open to suggestions on what tools i may use. Im trying the flash tool as soon as i get home.
I tried to downgrade using flashfire after rooting the device but it failed and thats why it's dead.
At first it was just a blue light with a green one blinking behind it, but i let it die over night in hopes of being able to recover it in the morning. Now, there isnt even the light.
The battery isnt dead according to my multimeter.
While the bootloader is locked, it HAD engineerboot so maybe that allows something. :/
I would have taken it to a repair shop but the closest one knows nothing about software issues and only suggest hardware repairs, hence me wanting to replace the motherboard.
I'm going to search how to fix it with linux since i have a linux machine, i just have no experience with it at all. At least pushing the bootloader will help an awful lot. If you have any knowledge on any of these, even the slightest, do share. Ill do some research meanwhile and if i find a fix, I'll post it. This phone was so good and i miss it dearly, which is why i need all the help and research i can get.
Apparently no one has ever bricked the snapdragon version of this phone, given the lack of any google results similar to this situation on this phone. ;-;

*Detection* said:
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult
Click to expand...
Click to collapse
Its in QUSB_BULK now. At least the computer SEES it

savagevegeta said:
Its in QUSB_BULK now. At least the computer SEES it
Click to expand...
Click to collapse
Yea seems to be as suspected, here is a different device with same QUSB ID, and the fix is as I suggested using adb and different flash tools to push the correct files to the device
https://xiaomi.eu/community/threads/sudden-death-or-hardbrick.36285/#post-334687
http://www.androidbrick.com/xiaomi-mi5-how-to-flash-global-multilanguage-rom-unbrick-guide/
This is not for the S7 though, so don't copy it or use their tools, but it will give you a general idea of what the process would be if you had the correct files and flash tools available
---------- Post added at 22:51 ---------- Previous post was at 22:25 ----------
Not sure how to enable the bootloader update function, if it will enable once you load firmware into the sections on the right, but try ODIN 3.12.10
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 22:53 ---------- Previous post was at 22:51 ----------
https://forum.xda-developers.com/showthread.php?t=2711451

*Detection* said:
Yea seems to be as suspected, here is a different device with same QUSB ID, and the fix is as I suggested using adb and different flash tools to push the correct files to the device
https://xiaomi.eu/community/threads/sudden-death-or-hardbrick.36285/#post-334687
http://www.androidbrick.com/xiaomi-mi5-how-to-flash-global-multilanguage-rom-unbrick-guide/
This is not for the S7 though, so don't copy it or use their tools, but it will give you a general idea of what the process would be if you had the correct files and flash tools available
Click to expand...
Click to collapse
Thanks for researching this. It did give me an idea, but it sucks that there is no tools for samsung devices stuck in QHSUSB_BULK mode. I found a guide that allows me to flash a PIT file and the bootloader file onto an SD card, and then insert it into the bricked S7, but that process requires a second S7 to flash the files onto. I tried flashing the boot.img and recovery.img onto the SD and hoping for the best, but still no luck. I'm looking for other methods. I saw on youtube that some guy used a program to flash an unbrick.img onto an SD, and that got it to go into download mode, but the tool he used was S5 specific and the video was a guide for the S5

savagevegeta said:
Thanks for researching this. It did give me an idea, but it sucks that there is no tools for samsung devices stuck in QHSUSB_BULK mode. I found a guide that allows me to flash a PIT file and the bootloader file onto an SD card, and then insert it into the bricked S7, but that process requires a second S7 to flash the files onto. I tried flashing the boot.img and recovery.img onto the SD and hoping for the best, but still no luck. I'm looking for other methods. I saw on youtube that some guy used a program to flash an unbrick.img onto an SD, and that got it to go into download mode, but the tool he used was S5 specific and the video was a guide for the S5
Click to expand...
Click to collapse
Yea I know about the one for the S5, that was my phone before the S7, maybe PM that dev (He's from XDA) on the S5 forums and see if he could help you out?