Database Users

[UPDATED]Recover your dead X8/W8.

Hello there fellow X8/W8 users!
This post is intended to point your attention to the simple fact that there's a hardware imposed danger to hard brick your Xperia X8 and W8, applies to E15i/a and E16i/a, at the attempt to unlock the boot loader!
The phones affected by the problem are units being manufactured at, and after, 11W29!
To check if your device is affected by the problem follow this simple steps:
Turn off the phone and open it up
Take out the battery
Look at the sticker below
If the date code on the sticker reads 11W29, or any later date (11W30, 11W31, 11W32, 11W33, ...), DO NOT attempt to unlock the boot loader.
These phones ship with a revamped chipset configuration having the security hole the boot loader unlock uses effectively closed. This means that upon unlocking the boot loader your phone will end up as a hard brick - and you will have NO means to revive the phone yourselves. You either have to send it off to Sony for repair (recommended solution) or find a phone repair shop being able to resurrect shot devices!
The symptom you will experience when unlocking the boot loader on an affected device is like this:
The boot loader unlock will most likely go through fine
At restart the phone will show NO signs of life anymore.
NO LED, NO LCD output, NO vibration.
This is the point where you can not do anything anymore yourself to resurrect the device.
You have been warned, DO NOT TRY to unlock the boot loader on phones manufactured PAST 11W29!
But it has been seen that there are few devices with manufacturing code above 11W29 have also successfully unlocked their bootloader.
For example me,i have 11W34 and unlocked the bootloader just fine..
But let me remind you again that this was just a matter of luck.
You might not be so lucky...
Also if you have manufacturing code above 11W29 and are desperate to unlock your bootloader then there are paid methods for it as reported by few users who had successfully unlocked their bootloader with manufacturing date above 11W29.
Update (2012/02/23):
To clear up the "no means to resurrect the phone yourself": This is true unless you are a experienced electronics technician. If you own a JTAG box (RIFF Box, Medusa Box) you may attempt to resurrect the device through JTAG. It may also be possible to resurrect the device through UART flash by using a test pin connection. Google is your friend here to dig up the required informations.
As posted by baiclark: There's an option to unlock the boot loader on 11W29+ devices, though this involves some Software (setool2) where you need to buy credits to perform the unlock. This is an untested procedure. If you decide to jump the gun please report your experience.
Update: Home-Brew unbricking with Omnius
Forum member aze2learn posted a guide about how to unbrick your hard bricked W8/X8 by using a modified Nokia CA-42 cable and Omnius. Find his valuable contribution at this post.
/!\ Be warned that this requires basic electronics skills to make it happen. /!\

Unbrick your briked X8/W8 via flashtools
Hi all
I made this thread since some guys were having trouble unbricking their X8/W8 via FLASHTOOLS...
And let me make it clear that the following post wont help you if your phone has bricked in attempt to unlock your bootloader when your phones manufacturing code was above 11W29.
In such a case the only (period) solution is to send it off to SONY to have it repaired.
How to unbrick your Soft Bricked phone..
What do you need?
Flashtools.(thanks to androxyde and bin4ry)
X8 stock firmware.
Or from here.
Or here.
X8 drivers installed.
WinRar
Your X8/W8 phone
A USB cable
A PC
Relaxed mind..
Click to expand...
Click to collapse
Now lets begin.
1.First of all download and install Flashtools from the link provided above.
2.Download SE firmware in *.ftf file format and put it in Flashtool/firmwares folder.
3. Now, run the FlashTool and click the
{
"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"
}
Lighting bolt button to start flash.
4.Now click flashmode and choose Xperia X8 (E15i).
4.Now wait for a while till it says you to "remove your phone,press the back button and hold it and install the USB".
Do it and wait for the flashing proceedure to finish...
If everything works fine then CONGRATULATIONS!!!!!! you have successfully unbricked your phone and installed the 2.1.1.A.0.6 version with 015 baseband, fresh and stock!
If your phone doesnt boots up still, then you might have gone wrong somewhere in the flashing process..
So read the steps carefully and do it again..
[OPTIONAL STEP]
Guide for installing the required drivers for flashing, skip this if you have PC Companion installed and connected your phone in flash mode at least once!
If your phone is not recognized by Flashtool that means you don’t have the required drivers installed.
Open folder /Flashtool/drivers and install ggsetup-2.2.0.11
If after the above Flashtool still doesn’t recognize your phone, do the following:
From Flashtool/drivers folder extract the zip file XXX_ADB_driver which corresponds to your phone model
Open “Device manager” on the computer and find the device which is with an exclamation mark on it (do this with connected to the computer phone)
Right click on the device and choose Uptade driver
Choose to find the driver manually and browse to the folder where you’ve extracted the zip file.
That should install the required drivers on your computer.
Click to expand...
Click to collapse
Now as you have successfully unbricked your phone, the first thing you would possibly do is rooting your phone...
So here i show you how to Root your phone with flashtools..
1.Start Flashtool
2.Connect the device to the computer and wait until it's recognized
3.Click the icon with the "Padlock [the second in a row]
4.FT will start pushing files, wait till it finishes. Meanwhile the phone will reboot once.
5.When it's over Flashtool will notify "Root Access Allowed"
6.Open the application list on the phone and look for the app "Superuser".
7.If "Superuser" is there you have Rooted your device successfully.
Congrats!
That's it...........
If you found this thread useful don't forget to click the THANKS button for me...
Thanks to
Bin4ry and androxyde..(for flashtools)
crowds for the original guide..
Leajian for allowing me to use content from his guide.
BlackRabbit1703 for the mirror of firmware.
And all the people who liked my work...
See ya..

um, mine's an 11W29 and it unlocked just fine. it's only the one's AFTER it that have issues.

I have 11W33 and unlocked 2 times now without a problem ! and works fine

Realtbhuion said:
um, mine's an 11W29 and it unlocked just fine. it's only the one's AFTER it that have issues.
Click to expand...
Click to collapse
We also had a few phones in the 11W3x region that unlocked perfectly, but the hard bricks we observed so far all start at 11W29 - and newer.
The source from where we got the information about the hard brick danger is a post of the_laser on setool.net ...
seems most of lately produced msm7227-based phones have chipset with FIXED security hole, which used to altbypass unlock.
(that is not 100% confirmed, we only have few reports, however better be warned)
such phones will DIE after successful unlock procedure.
such dead phones CAN NOT be recovered. ( perhaps, jtag can fix that, perhaps, qualcomm fixed jtag security hole too )
there is NO WAY to determine if phone has fixed chipset or chipset with security hole.
the ONLY safe way is to use unlock by resurrection cables.
if phone can be connected and booted by resurrection cables, phone is safe to unlock.
if phone can not be booted by resurrection cables, phone has fixed chipset and could not be unlocked.
you have been warned.
get and use resurrection cables.
update:
e16 phone with manufacture date 11w38 affected, i think we should care about phones which produced after 11w26
Click to expand...
Click to collapse
As you can see the_laser referenced 11W26 as the "threshold" where our observation is that 11W29 is where the trouble really starts.
EDIT: See this thread for reference - post #62 and #63 where we summed up a few hard bricks. But that's just the tip of the iceberg, there have been way more.
You're of course free to dismiss the warning and do as you please, just don't come ranting about your hard brick - you've been warned.

My phone is 11W30 (I forgot to check this before unlock bootloader) but all works fine for me.

Mine was 11W37, and I said "was" 'cause I just bricked it.
So Im reading this thread too late lol
However, this situation only hurries things because I'm getting Xperia Ray soon. Now I have to get it sooner.
For now, I have a fa(i)lPhone, wich was a present from my dad. So no worries at all. But having my X8 completely bricked will be a good challenge, as I'll try to bring it back to life no matter if you say there is nothing I can do.
Of course, in case I achieve it, I'll share it! If not, then I'll have a nice modern piece of decoration for my living room: a smartphone XD

x8-11w37 new phone HARD BRICK!
I was lucky ennough they replaced my bricked x8. . No unlocked bootloader for me.

El Brillantinas said:
Mine was 11W37, and I said "was" 'cause I just bricked it.
But having my X8 completely bricked will be a good challenge, as I'll try to bring it back to life no matter if you say there is nothing I can do.
Of course, in case I achieve it, I'll share it!
Click to expand...
Click to collapse
To be precise - there is something that can be done, it's just not very easy.
On the one hand you can try to read up over at setool.net. The latest versions of SETool are able to resurrect shot W/X8's. However, you either need to know to which test-pins to you need to connect the cable from your computer or simply try to get one of the Qualcomm resurrection cables fitting the W/X8. Apart from that you need "credits" for SETool to actually perform the operation. This means you have to pry your W/X8 apart to gain access to the PCB - that's not exactly something everyone around here is able to do - and connect to the right pins to flash in UART mode.
On the other hand you can always try to find someone (private person / repair shop) having a RIFF Box to see if the phone can be resurrected by JTAG, though the way it sounds (the post I read on setool.net about UART resurrection) a JTAG restore seems to be impossible - but feel free to try.
If you can work out a working, and relatively simple to follow, solution to restore shot W/X8's be our guest to write up a post.

thks, for the info, My x8 manuf.code is 11W28, is it safe for unlock BL?

Can i unlock my bootloader?
My W8 code is 11W25 can i unlock my bootloader??

B.Jay said:
If the date code on the sticker reads 11W29, or any later date (11W30, 11W31, 11W32, 11W33, ...), DO NOT attempt to unlock the boot loader.
Click to expand...
Click to collapse
NarutoDroid said:
thks, for the info, My x8 manuf.code is 11W28, is it safe for unlock BL?
Click to expand...
Click to collapse
akhi24nick said:
My W8 code is 11W25 can i unlock my bootloader??
Click to expand...
Click to collapse
So ... 11W28 and 11W25 are below 11W29, right?
No guarantee given as there's always the chance that you may mess up, but it should be safe to try and unlock the boot loader.

Mine is 11W21 (uhm semms a old version or something like that...?), soon I'll try unlocking...
But it has a f..... sinaptic touchscreen, damn...

Hmmmm..... I got 11W34 and i can unlock my Droid

11W48
Hi there,
actually I was following guides in the manner google -> blogs -> direct links to oneclickroot/roms -> direct links to bootloader unlocker and...
Well, unfortunately 11W48 (pretty fresh, huh?) got hard bricked xD
I understand it's motherboard failure now and we can do NOTHING more than sending my new paperweight back to SE?
Also I'm looking forward to finding another way to unlock bootloader with new chips in case the one I get back won't be <11W29
Thanks in advance for your reply

Ahh i wish so much i had red this thread and didn't act too much excited about unlocking it.

10W48 ---> unlock with flashtool!

2010matej said:
10W48 ---> unlock with flashtool!
Click to expand...
Click to collapse
Man.... You are exceptional on EARTH.....
You unlocked bootloader with 11w48 making. You have battery backup beyond 6 days.
May be you can overclock your X8 upto 1Ghz and have Multitouch instead of dualtouch even its also possible that SE will make a firmware 4.0 only for you....
Really, you are an amazing guy...

that's very good to warn everyone here before attempting ^^

my is 11w06

My LG G2 is COMPLETELY bricked.

So after 20 hours of fiddling... I can safely say that this LG G2 D803 is completely done.
Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet.
I attempted the .TOT method described here, where I used LGTools. I then only realized that this method was only suitable for an US device, such as AT&T, T-Mobile, or Verizon (couldn't find a Rogers .TOT). I didn't modify the phone in any way.
I then continued to download the Rogers KDZ file here. Using the method described in the same post above, I performed the upgrade, only to realize that this was method wasn't working either.
I then did some scouring to find a way to boot into TWRP (which was already installed). I found this trick: If you hold the power button down until the phone turns off, you can hold power and down until you see the LG symbol, and then depress and press them again immediately to get into TWRP!
In TWRP... I realized that the partitions were all messed up. It was showing 6GB internal, and countless errors were popping up. Another dead end. ADB was working, but I was unable to push anything.
I then realized I should attempt to flash updated partitions using fastboot. Using the cmd line in Windows, I erased and flashed partitions I downloaded here after putting the phone in fastboot mode.
This is where I did something stupid.
Instead of clicking and downloading on that site, I right-clicked "save-as" and downloaded 8kb corrupted partition files. I continued and flashed them unknowingly... and right after, the phone decided to not boot at all.
Using VMWARE and Ubuntu 14.04, I attempted to reflash the partitions using Linux commands described here. Unfortunately, the device would not show the /sd* partitions. Certainly, the bootloader that communicates with the PC does not allocate the partitions properly anymore.
Alright, the phone wont boot, because I flashed a bad bootloader. No biggie right? I would see the device as Qualcomm hs-usb qdloader 9008.
That's when I scoured for a new method to fix the partitions. I came across QPEST and eMMC Software App to get this device back alive.
I spent hours trying to find the right .hex and .mbn file on Chinese websites. I found 8974_msimage.mbn, MPRG8974.hex, flash.xml, rawprogram0.xml and patch0.xml. I had to create accounts of a bunch of sites to finally download the correct files.
Carefully using QPST, I was able to get the phone in Download Mode (Qualcomm download mode, not LG download mode), and pushed the instructions to the device.
... too bad. I thought I did everything right. The device times out in the process EVERYTIME.
{
"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"
}
The phone is officially dead, there isn't a way I know of to get it started (at least to fastboot again). It really pays off to check what you're flashing before you do it. The internet is full of crap.

BuffMcBigHuge said:
So after 20 hours of fiddling... I can safely say that this LG G2 D803 is completely done.
Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet.
I attempted the .TOT method described here, where I used LGTools. I then only realized that this method was only suitable for an US device, such as AT&T, T-Mobile, or Verizon (couldn't find a Rogers .TOT). I didn't modify the phone in any way.
I then continued to download the Rogers KDZ file here. Using the method described in the same post above, I performed the upgrade, only to realize that this was method wasn't working either.
I then did some scouring to find a way to boot into TWRP (which was already installed). I found this trick: If you hold the power button down until the phone turns off, you can hold power and down until you see the LG symbol, and then depress and press them again immediately to get into TWRP!
In TWRP... I realized that the partitions were all messed up. It was showing 6GB internal, and countless errors were popping up. Another dead end. ADB was working, but I was unable to push anything.
I then realized I should attempt to flash updated partitions using fastboot. Using the cmd line in Windows, I erased and flashed partitions I downloaded here after putting the phone in fastboot mode.
This is where I did something stupid.
Instead of clicking and downloading on that site, I right-clicked "save-as" and downloaded 8kb corrupted partition files. I continued and flashed them unknowingly... and right after, the phone decided to not boot at all.
Using VMWARE and Ubuntu 14.04, I attempted to reflash the partitions using Linux commands described here. Unfortunately, the device would not show the /sd* partitions. Certainly, the bootloader that communicates with the PC does not allocate the partitions properly anymore.
Alright, the phone wont boot, because I flashed a bad bootloader. No biggie right? I would see the device as Qualcomm hs-usb qdloader 9008.
That's when I scoured for a new method to fix the partitions. I came across QPEST and eMMC Software App to get this device back alive.
I spent hours trying to find the right .hex and .mbn file on Chinese websites. I found 8974_msimage.mbn, MPRG8974.hex, flash.xml, rawprogram0.xml and patch0.xml. I had to create accounts of a bunch of sites to finally download the correct files.
Carefully using QPST, I was able to get the phone in Download Mode (Qualcomm download mode, not LG download mode), and pushed the instructions to the device.
... too bad. I thought I did everything right. The device times out in the process EVERYTIME.
The phone is officially dead, there isn't a way I know of to get it started (at least to fastboot again). It really pays off to check what you're flashing before you do it. The internet is full of crap.
Click to expand...
Click to collapse
there is a lot of crap on the internet but when you start fastbooting or dding partitions without verifying the integrity of the stuff you downloaded you will eventually brick something. Perhaps this experience will goad you into checking md5 or sha1 before you go about flashing things.

DeathmonkeyGTX said:
there is a lot of crap on the internet but when you start fastbooting or dding partitions without verifying the integrity of the stuff you downloaded you will eventually brick something. Perhaps this experience will goad you into checking md5 or sha1 before you go about flashing things.
Click to expand...
Click to collapse
It's very rare that I ensure the md5 is correct. In this case, the file sizes were completely off (8kb rather than 512kb), which is more noticeable than the hash. You're absolutely right. I sent the phone to MobileTechVideos for a JTag repair. I'll post the results when I get it returned.

You made a valiant effort, good luck man.

My hat goes off to you, man. Is it under a warranty that covers accidental damage? A good smashy-smashy would cover your tracks and relieve your stress all at once

I tell you though - fine attempt. Made my day reading this. Never stop at no. Hope you get your phone fixed.
Onward.
Sent from my LG-D802 using XDA Premium HD app

1 LG G2 down
20 million+ units still in combat working the daily grind!

Now phone is dead so go to the warranty method.

BigBoyPL said:
Now phone is dead so go to the warranty method.
Click to expand...
Click to collapse
he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief.

xlr8me said:
1 LG G2 down
20 million+ units still in combat working the daily grind!
Click to expand...
Click to collapse
make it 2 lg g2 mine is dead too...
mine is back to life finally

Can you not use a fastboot cable and re flash the correct partition images from there. I used that method to recover a completely bricked Kindle fire recently.

ClawOfDoom said:
Can you not use a fastboot cable and re flash the correct partition images from there. I used that method to recover a completely bricked Kindle fire recently.
Click to expand...
Click to collapse
I think this are the cases when the warranty should be used. The phone is not on it's best condition, so that should take care of this.

Any updates on the repair? I have a bricked D801 too...

zPacKRat said:
he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief.
Click to expand...
Click to collapse
I respectfully disagree. everything described is software related. The hardware is still fine. At least from what I was reading. Which means the phone could be sent back, under warranty and repaired in probably under 5 minutes. It might get a dollars worth of new plastic on it. Repackaged up and sent off to somebody else to replace their broken phone. The losses on the replacement phone would be recouped almost instantly.
Sent from my VS980 4G using Tapatalk

Can you help me.
Dear BuffMcBigHuge!
I have a situation same you, Now my LG G2 L-01F - NTT DOCOMO total Dead, it show Qualcomm HS-USB QDLoader only.
I searched many forum, but havent find out these file.
Can you give me these file for me to try unbrick My G2.
My email: [email protected]
Many thanks you.

dm6939 said:
Dear BuffMcBigHuge!
I have a situation same you, Now my LG G2 L-01F - NTT DOCOMO total Dead, it show Qualcomm HS-USB QDLoader only.
I searched many forum, but havent find out these file.
Can you give me these file for me to try unbrick My G2.
My email: [email protected]
Many thanks you.
Click to expand...
Click to collapse
+1 = I have the same here...

So after sending the device to MobileTechVideos, I was able to get it fully repaired and back into working order! They converted it to a D801, and its back in full working order!
Highly recommended!

BuffMcBigHuge said:
So after sending the device to MobileTechVideos, I was able to get it fully repaired and back into working order! They converted it to a D801, and its back in full working order!
Highly recommended!
Click to expand...
Click to collapse
Fantastic news glad there are still teams that are dedicated to there work and know what they are doing
Danzano's happy place

Danzano said:
Fantastic news glad there are still teams that are dedicated to there work and know what they are doing
Danzano's happy place
Click to expand...
Click to collapse
Any more updates here ? looks like we need 2 important files specific to the G2 . The .hex and the mnb file to enable writing to eMMC.

zathus said:
I respectfully disagree. everything described is software related. The hardware is still fine. At least from what I was reading. Which means the phone could be sent back, under warranty and repaired in probably under 5 minutes. It might get a dollars worth of new plastic on it. Repackaged up and sent off to somebody else to replace their broken phone. The losses on the replacement phone would be recouped almost instantly.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
bc OP stated:
"Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet"
so when a device is broken, (whether it be hardware or software) by the user, that is not a manufacturer defect. That is misuse, nonwarranty. thats why the guy you responded to said "he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief." and i agree with him. I actually cringe when i see people on here brick their phones, then ask for ways to unroot so they can get it repaired under warranty. Manufacturers are going to continue to make it harder to gain root access bc im sure theyre tired of wasting time on people who broke their phones themselves, then want it repaired for free. sigh...

SM-G930A Unbrick Image

I have a hard bricked AT&T Galaxy S7 (SM-G930A). I'm trying to unbrick it by using an SD card and an unbrick image, as described here or here. However, I don't have access to a rooted Galaxy S7 of the same model. Can someone create an unbrick image I can use?
Thanks!

PantherMan594 said:
I have a hard bricked AT&T Galaxy S7 (SM-G930A). I'm trying to unbrick it by using an SD card and an unbrick image, as described here or here. However, I don't have access to a rooted Galaxy S7 of the same model. Can some create an unbrick image I can use?
Thanks!
Click to expand...
Click to collapse
How did you hard brick it? Did you mess with settings in Odin? Try to flash the wrong FW?

Ph0nysk1nk said:
How did you hard brick it? Did you mess with settings in Odin? Try to flash the wrong FW?
Click to expand...
Click to collapse
I don't know how it was bricked, I'm trying to fix it for a friend. It doesn't turn on at all, so I can't get it into download mode to flash the stock rom. I know it's a Qualcomm variant because I can see "Qualcomm HS-USB QDLoader 9008" in device manager when I plug it into my computer, so the SD card method might work.

PantherMan594 said:
I don't know how it was bricked, I'm trying to fix it for a friend. It doesn't turn on at all, so I can't get it into download mode to flash the stock rom. I know it's a Qualcomm variant because I can see "Qualcomm HS-USB QDLoader 9008" in device manager when I plug it into my computer, so the SD card method might work.
Click to expand...
Click to collapse
So... can you please post either a picture or the names of the the files you attempted to flash? I have an idea

Ph0nysk1nk said:
So... can you please post either a picture or the names of the the files you attempted to flash? I have an idea
Click to expand...
Click to collapse
I can't flash anything because it won't turn on at all, so I can't get into download mode.

PantherMan594 said:
I can't flash anything because it won't turn on at all, so I can't get into download mode.
Click to expand...
Click to collapse
Not what I asked. What files did you TRY TO FLASH? Give me a link to the site you got them from or put them in a folder and take a pic of the files.

Ph0nysk1nk said:
Not what I asked. What files did you TRY TO FLASH? Give me a link to the site you got them from or put them in a folder and take a pic of the files.
Click to expand...
Click to collapse
I haven't tried to flash anything yet, and I don't know what my friend flashed to brick the phone. I will try to flash this if I can boot the phone into download mode.
{
"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"
}

So... I'm gonna take a guess and assume that your friend didn't really know what he was doing and flashed the first firmware he saw. (Which was probably the F firmware.) Causing it to brick. The F firmware IS NOT MEANT four our devices. Hence he broke it. Probably unrecoverable. Plus he might not have used Odin making it even worse.

Ph0nysk1nk said:
So... I'm gonna take a guess and assume that your friend didn't really know what he was doing and flashed the first firmware he saw. (Which was probably the F firmware.) Causing it to brick. The F firmware IS NOT MEANT four our devices. Hence he broke it. Probably unrecoverable. Plus he might not have used Odin making it even worse.
Click to expand...
Click to collapse
Well that's discouraging... I would still like to try booting from and SD card though, so it would be great if you (or anyone) can provide a debrick image.

PantherMan594 said:
Well that's discouraging... I would still like to try booting from and SD card though, so it would be great if you (or anyone) can provide a debrick image.
Click to expand...
Click to collapse
Even that might not because of our locked bootloader. Friend is more than likely dicked out of his phone unless he files a for replacement or something. :/

I have a hard bricked Galaxy S7 (SM-G9300). I'm trying to unbrick need unbrick image
create a Debrick IMG :
-you need to have a rooted device
-need to install busybox
-need a terminal
-open terminal type
(su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/200mb.img bs=4096 count=50000)

I think this is a waste of time in this forum. All clever guys have left, just kidds remained.
They just copy others posts...
Can anyone really make an unbrick image? Is it soo difficult?
Seems everybody just cares for themselves....
Lets hope...
And just a comment, you dont need a "rooted" phone to create the image.
Insert a blank sd card on your phone, at least 32GB
Enter download mode,
Load files in ODIN
Select in options tab in Odin (T-Flash)
And flash
All flash will happen to the SD card NOT in the phone and TADA, you have a sd card where you can extarct the recovey image
Piece of cake.
Anyone help?

PadsPCB said:
I think this is a waste of time in this forum. All clever guys have left, just kidds remained.
They just copy others posts...
Can anyone really make an unbrick image? Is it soo difficult?
Seems everybody just cares for themselves....
Lets hope...
And just a comment, you dont need a "rooted" phone to create the image.
Insert a blank sd card on your phone, at least 32GB
Enter download mode,
Load files in ODIN
Select in options tab in Odin (T-Flash)
And flash
All flash will happen to the SD card NOT in the phone and TADA, you have a sd card where you can extarct the recovey image
Piece of cake.
Anyone help?
Click to expand...
Click to collapse
Did you ever get the debrick image? My S7 bricked while trying to downgrade with flashfire :/

g930a-v models same sda flash
my phone same problem bro help me
If for some reason it doesn't work, then try to create an emergency scdard from an identical model with identical firmware version as your broken one, root it by eng-boot, read out the first 1GB of the "sda" partition, write the dump to a fast class U1/U10 32GB sdcard using Win32Disk, insert the card into the sdcard slot and power it up while holding Vol Down + Home + Power. If everything was done correctly, the phone should boot into download mode, then just flash the latest full stock to fix it.
To create an emergency sdcard for Qualcomm based G930/G935:
adb shell
su
dd if=/dev/block/sda of=/storage/emulated/emergency.bin bs=1024 count=131072
exit
adb pull /storage/emulated/emergency.bin
g930a-v models same sda flash
PantherMan594 said:
I have a hard bricked AT&T Galaxy S7 (SM-G930A). I'm trying to unbrick it by using an SD card and an unbrick image, as described here or here. However, I don't have access to a rooted Galaxy S7 of the same model. Can someone create an unbrick image I can use?
Thanks!
Click to expand...
Click to collapse

I have a bricked S7, att variant. I used modded odin to force a lower bootloader and now it will only boot to a screen that says sbl error. I got the edl cable. What do I do now?

reviving a thread for a minute. I too was given a phone that is hard bricked. meaning that it will not be recognized by odin. however, it is recognized and i have the qualcomm drivers through my work. so i have access to qpst and qfil. the downside is that i cannot find a full copy of the software.
qpst requires both phone image and boot image in .hex format,
and qfil gives me a bit more playing area such as elf type and the xml files, or i can extract the files needed if i have the FFU.
my problem is the only versions of the software that i keep finding are for odin. so my request is, i have a couple of different software versions for the g930a, can someone extract the hex files, or convert to FFU? that's the part i'm getting stuck in. lots of tutorials on how to extract to convert to md5 for odin, or how to extract if you have a rooted g930a, but i don't have access to that.

Made a complete ZVA dump

So after following some basic instructions that i still managed to mess up
i made a complete dump on zva. which means a debrick image can be made.
if we had the needed firehose.bin we could possibly fix hard-bricks in qfil in qpst.
I'm uploading said dump to my google drive but kinda reluctant to share it in fear if u used my dump then u might also get my iemi. so once i figure that one out i will make it available to all

So i was looking around in a few of the files in my hex editor and noticed. Id have to pull it up on i think bootloader backup. That user debug is set to 0. Wonder if its modifiable to set to 1 and enable a debug bootloader

Any idea how to dump the PRL? QPST 2.7.460 crashes when I try to read the info from the phone. LGUP might be able to do it with the proper LS992 DLL, but I can't find one that works.

Hai Karate said:
Any idea how to dump the PRL? QPST 2.7.460 crashes when I try to read the info from the phone. LGUP might be able to do it with the proper LS992 DLL, but I can't find one that works.
Click to expand...
Click to collapse
ive never had to dump a prl before every cdma phone i get i gsm unlock
ive read the prl on my g4 i use 2.7.402 and its never failed me

TheMadScientist420 said:
So after following some basic instructions that i still managed to mess up
i made a complete dump on zva. which means a debrick image can be made.
if we had the needed firehose.bin we could possibly fix hard-bricks in qfil in qpst.
I'm uploading said dump to my google drive but kinda reluctant to share it in fear if u used my dump then u might also get my iemi. so once i figure that one out i will make it available to all
Click to expand...
Click to collapse
Kinda a long shot but could we inject root into the system after boot using the sd card method of loading a dump?

thjubeck said:
Kinda a long shot but could we inject root into the system after boot using the sd card method of loading a dump?
Click to expand...
Click to collapse
I dont know rite now
my g5 is down

thjubeck said:
Kinda a long shot but could we inject root into the system after boot using the sd card method of loading a dump?
Click to expand...
Click to collapse
Interesting idea, have a link or can you go more into detail about loading a dump via SD? This is my first LG and I'm still trying to figure some things out. My Samsungs were so easy to root, flash TWRP in Odin, flash SuperSU, done.
{
"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"
}

bilgerryan said:
Interesting idea, have a link or can you go more into detail about loading a dump via SD? This is my first LG and I'm still trying to figure some things out. My Samsungs were so easy to root, flash TWRP in Odin, flash SuperSU, done.
Click to expand...
Click to collapse
Ive been doin lgs for some time now, It sounds like he is describing the rooted system injection like on sprint g4 with the dd commands.

bilgerryan said:
Interesting idea, have a link or can you go more into detail about loading a dump via SD? This is my first LG and I'm still trying to figure some things out. My Samsungs were so easy to root, flash TWRP in Odin, flash SuperSU, done.
Click to expand...
Click to collapse
I originally had the root shell from December but it was useless and I ended up flashing a newer KDZ file and have not been able to downgrade yet so for me that method is out and was not working and I have been looking for other options.
So far have two options. https://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
UPDATE: The send_command.exe does find the phone so testing to see what happens here
UPDATE 2: Que the haters LAF got me forgot about that guys sorry. So looks like LGUP may be the only option if we can figure out how to convince it to work.
UPDATE 3: Purposely bricking your phone gets you into LAF mode. You have to stop it at 10% on a KDZ update and it will allow you to use LAF mode again.
My other option is use the "expanded" version of LGUP and flash the system partition.I have tried extracting the system partition and flashing but having trouble getting LGUP to flash .img to the system. Seems to only let you choose where to put the partition if you are using a .dz or .kdz file.
As for the SD method, I read a post about using the SD card with a dump of the phone to recover from a hardbrick. Not completely sure of the details on that.
The G5 is not currently my daily driver so am able to experiment some with it.
P.S. Disclaimer to anyone who comes across this reply looking for root. I know some about what is possible with this phone but do not quote me as fact as I can and have been wrong before

thjubeck said:
I originally had the root shell from December but it was useless and I ended up flashing a newer KDZ file and have not been able to downgrade yet so for me that method is out and was not working and I have been looking for other options.
So far have two options. https://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
UPDATE: The send_command.exe does find the phone so testing to see what happens here
UPDATE 2: Que the haters LAF got me forgot about that guys sorry. So looks like LGUP may be the only option if we can figure out how to convince it to work.
My other option is use the "expanded" version of LGUP and flash the system partition.I have tried extracting the system partition and flashing but having trouble getting LGUP to flash .img to the system. Seems to only let you choose where to put the partition if you are using a .dz or .kdz file.
As for the SD method, I read a post about using the SD card with a dump of the phone to recover from a hardbrick. Not completely sure of the details on that.
The G5 is not currently my daily driver so am able to experiment some with it.
P.S. Disclaimer to anyone who comes across this reply looking for root. I know some about what is possible with this phone but do not quote me as fact as I can and have been wrong before
Click to expand...
Click to collapse
I saw a post somewhere about making your own kdz, let me see if I can find it again. We were able to get a downgrade working as far back as ZV8.

bilgerryan said:
I saw a post somewhere about making your own kdz, let me see if I can find it again. We were able to get a downgrade working as far back as ZV8.
Click to expand...
Click to collapse
Not getting anywhere on the custom kdz. Found some tools and have got the kdz extracted but recompiling seems to be the issue here.

This might help you for kdz
https://forum.xda-developers.com/showthread.php?t=2215929

Hello, I need urgent help, I tried an unlocking service for my G5 and the person using the remote server bricked my phone. It is not stuck on download mode, I cannot even get into recovery. I don't know how to reflash this phone, I think if I had the correct .dll for the LG flash tool it would help me greatly as I could at least try to flash it. Thank you for your consideration.

Kevovaz said:
Hello, I need urgent help, I tried an unlocking service for my G5 and the person using the remote server bricked my phone. It is not stuck on download mode, I cannot even get into recovery. I don't know how to reflash this phone, I think if I had the correct .dll for the LG flash tool it would help me greatly as I could at least try to flash it. Thank you for your consideration.
Click to expand...
Click to collapse
Already answered you in the unlocking thread.

majedalanni said:
This might help you for kdz
https://forum.xda-developers.com/showthread.php?t=2215929
Click to expand...
Click to collapse
The first tool looks promising but since google code went to archive mode seems that it can't be found.

TheMadScientist said:
So after following some basic instructions that i still managed to mess up
i made a complete dump on zva. which means a debrick image can be made.
if we had the needed firehose.bin we could possibly fix hard-bricks in qfil in qpst.
I'm uploading said dump to my google drive but kinda reluctant to share it in fear if u used my dump then u might also get my iemi. so once i figure that one out i will make it available to all
Click to expand...
Click to collapse
Just wondering about this but is the reason the original tool posted by unmentionable names removed because it involves purposely bricking your phone? I found a forum post on the G4 about this and tried it with the G5 and I can get into LAF mode although limited on the newest bootloader version.

thjubeck said:
Just wondering about this but is the reason the original tool posted by unmentionable names removed because it involves purposely bricking your phone? I found a forum post on the G4 about this and tried it with the G5 and I can get into LAF mode although limited on the newest bootloader version.
Click to expand...
Click to collapse
Yea i bricked mine but a diffrent reason and no fix cause g5 uses .elf not firehose.bin

TheMadScientist said:
Yea i bricked mine but a diffrent reason and no fix cause g5 uses .elf not firehose.bin
Click to expand...
Click to collapse
Okay. I posted on another forum and asked one of developers of that tool if they'd be willing to let someone try it who doesn't really care about the fact that you could brick your phone so here's hoping they'll let someone else try to finish the tool and get something working. Didn't get anywhere with the kdz method so thought I'd try stirring up the hornets nest again by asking.

thjubeck said:
Okay. I posted on another forum and asked one of developers of that tool if they'd be willing to let someone try it who doesn't really care about the fact that you could brick your phone so here's hoping they'll let someone else try to finish the tool and get something working. Didn't get anywhere with the kdz method so thought I'd try stirring up the hornets nest again by asking.
Click to expand...
Click to collapse
Wheres that at i might poke at that nest too. I hate to think my g5 is truly dead.

TheMadScientist said:
Wheres that at i might poke at that nest too. I hate to think my g5 is truly dead.
Click to expand...
Click to collapse
https://forum.xda-developers.com/tmobile-lg-g5/help/jcase-beaups-lg-tool-t3357312/page3
I replied to jcase at the end of this post on the tmobile forum. Thought about PMing him but its supposedly taboo to ask about the tool they posted so I figured I'd see if he would reply. Any other ideas let me know. I really want to know how they got root working and if it was full root or just user debug as the full root is helpful but userdebug was not as useful.
Really hate it that someone was stupid and released it early and got them ticked off about it.

Question How I can obtain a firmware file for this device?

Hello all!
I have a question concerning a device, I have a Cricket Dream 5G and the device is completely bootloader unlocked. However, I'm trying to figure out how I can obtain a firmware file for the device seeing as the Carrier or manufacturer hasn't released one. It is a MediaTek device running the MT6833 and efforts to make a scatter file in order to read with SP Flash tools have been unsuccessful,
I've also attempted to download an OTA update and see if it saved the file locally, as well as packet dump the update process via Wireshark. No Cigar.. it appears to be in the Cache partition which isn't accessible without root (which cannot be obtained without running TWRP with the device being Android 11). does anyone have any suggestions on how I might be able to get a copy of the system image or boot images for the use of making a working TWRP?
Thanks a lot!

Josephdbrewer25 said:
Hello all!
I have a question concerning a device, I have a Cricket Dream 5G and the device is completely bootloader unlocked. However, I'm trying to figure out how I can obtain a firmware file for the device seeing as the Carrier or manufacturer hasn't released one. It is a MediaTek device running the MT6833 and efforts to make a scatter file in order to read with SP Flash tools have been unsuccessful,
I've also attempted to download an OTA update and see if it saved the file locally, as well as packet dump the update process via Wireshark. No Cigar.. it appears to be in the Cache partition which isn't accessible without root (which cannot be obtained without running TWRP with the device being Android 11). does anyone have any suggestions on how I might be able to get a copy of the system image or boot images for the use of making a working TWRP?
Thanks a lot!
Click to expand...
Click to collapse
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.

SubwayChamp said:
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.
Click to expand...
Click to collapse
I've successfully backed up the device and gained root access. Thank you so much for recommending this tool. It worked, just voided my warranty lol. Had to disconnect the battery which requires taking apart the device

SubwayChamp said:
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.
Click to expand...
Click to collapse
Also do you know where the stock recovery is located. I can't seem to find it anywhere, like it doesn't even exist.

Josephdbrewer25 said:
I've successfully backed up the device and gained root access. Thank you so much for recommending this tool. It worked, just voided my warranty lol. Had to disconnect the battery which requires taking apart the device
Click to expand...
Click to collapse
Usually when a device's software had been modified, it may lose the warranty, or not, depending on what the "small" letters on a contract says, anyway, you could restore to its original state at any time, as you see in the need to claim it.
Normally, this tool works only installing the USDK64 drivers, and connecting device when power off, pressing the two volume buttons, I never need to open the back cover as MediaTek devices have the preloader mode, that it used by this tool to bypass the DA/SLAA protection, it does in the first stage the same thing that this tool does https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/ but without the need to use SP Flash tool but reading/writing directly onto the device.
Josephdbrewer25 said:
Also do you know where the stock recovery is located. I can't seem to find it anywhere, like it doesn't even exist.
Click to expand...
Click to collapse
Newer devices doesn't have a dedicated recovery partition.

SubwayChamp said:
Usually when a device's software had been modified, it may lose the warranty, or not, depending on what the "small" letters on a contract says, anyway, you could restore to its original state at any time, as you see in the need to claim it.
Normally, this tool works only installing the USDK64 drivers, and connecting device when power off, pressing the two volume buttons, I never need to open the back cover as MediaTek devices have the preloader mode, that it used by this tool to bypass the DA/SLAA protection, it does in the first stage the same thing that this tool does https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/ but without the need to use SP Flash tool but reading/writing directly onto the device.
Newer devices doesn't have a dedicated recovery partition.
Click to expand...
Click to collapse
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.

Josephdbrewer25 said:
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.
Click to expand...
Click to collapse
My device is the Cricket Dream 5G EC211001. It's weird

Josephdbrewer25 said:
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.
Click to expand...
Click to collapse
It doesn't really need to stay in preloader, this is the whole purpose of this tool, preloader is, actually, useless for flashing, when you press the two volume buttons, the device enters to preloader mode
{
"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 installed correctly the drivers, then, mtkclient detects the device, in the short time, and make it return to BROM mode through a handshake, to bypass the DA/SLAA authorization,
BROM mode is disabled by OEMs, similarly to EDL point, without this kind of tool, no more remedy that opening the back cover.
Moto 1st gen, it's a long time ago. It is placed in a tiny portion of the ramdisk, but you don't need to find where’s located.
If you think to port it, actually is not as easy due to newer implementations, A/B slots, virtual slots, a way to fix it permanently, etc., but basically what you need is in the boot image