Related
Sent from my Nexus 7 using Tapatalk 2
My N4 is from PlayStore USA, and I live outside of US. A few days ago I did a stupid mistake and flashed a wrong bootloader (please don't ask why - the embarrassment still hurts! ). The N4 is now totally dead - cannot be turned on, and won't boot no matter which sets of buttons I hold down.
I have been searching the net for solutions but have not found any simple enough (for me) solution. I read of several similar cases and the solution has been to send back to Google/LG. As I live outside of US, this isn't much of an option. I have also read about use of Gtag to unbrick devices but this is beyond my capability and this service is also not available in my country. Sending the N4 to my local LG service centre for repairs (there's no International warranty) is a last resort but I am not sure whether they have tbe tools and knowhow to unbrick my N4. They may not even want to get involved!
So I am writing in this forum to ask for help. Any advice will be appreciated. Thanks in advance.
Why the hell would you even flash the bootloader manually?
Anyway, there was a thread recently about Qualcomm's debugging mode. However, you'll need the appropriate drivers and most likely other software for it to work.
I don't know if anyone actually got it working, though
I dont know why I did it too - just following wrong instructions ; out of sheer stupidity!
Sent from my Nexus 7 using Tapatalk 2
download the quacomm usb high speed drivers and install them you might have to do have disk to install them in device manager. then doqnload the QPST qualcomm tool. this will allow you to flash phone images and other files here. It should pick your phone up in download state. Only problem now is that the Qualcomm tool only allows hex image files to be flashed. this is where i was stuck
Thanks for the qualcomm suggestion. I will look through it when I return to my home country in a week`s time. But from what you have described, the procedure seems too complex for me. I am also following the other `bricked Nexus 4` thread in this section which I was not aware of till yesterday. All indications are that my bricked Nexus 4 will be a total loss - LG in my country has told me that they will not touch my unit until Nexus 4 is officially launched in my country (that could be a couple of months away), and returning the unit back to Google USA will be extremely difficult, complex and cumbersome as I just learned that the unit has to be returned by the original purchaser from USA (I bought the N4 from a 3rd party in my country). Its an expensive mistake and I can only blame myself for the stupid mistake I made.
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
chwads2k8 said:
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
Click to expand...
Click to collapse
Not that simple. If you want, read this thread for some good info: http://forum.xda-developers.com/showthread.php?t=1914359
What where you trying to flash?
Anyone tried succesfully?
These are the Folders & Files I used in the DE-HARD-BRICKING of the Verizon variant of the LG G4. The word out on the streets is that plenty of infected Qualcomm tools have been floating around, so I decided to share with the XDA community, as far as I know, the most recent and infection free versions that really work. I can feel for the ethical hackers out here that need to get things done with the peice of sound mind that there is nothing involved that may risk their machines security or waste time with tweaked versions that wont work for some reason or other. About the Firehose, Raw, & Patch... These are THEE ones for vs986 & ls991. I DO NOT KNOW if they will work with any other variants, although, I SUSPECT that they may work with all G4's. On the other hand . . . they very well may not. AGAIN, I DO NOT KNOW. Only vs986 & ls991 are confirmed. I am looking for HardBricked G4 owners to use these with non-confirmed variants to establish a consensus of statistics to universally root the G5 using Qualcomm Utilities. I know, Iknow. eMMc & UFS are different, Bro. BLAH! Blah! BlAh! I'm only asking for volunteers whom have a G4 in the 9008 coma and have nothing to loose. If somebody knows something that I don't, that can convince me I'm wasting my time, I am open to "practical reason". or if somebody knows that these DO WORK for all G4 models on all Android LP & MM, then this I'd also like to know also. Misdirection shan't be tolerated. MY un-bricking method is posted here
DriverPack>https://drive.google.com/file/d/0B41ACD_ESYnHQU1qSnVlVXhORjA/view?usp=sharing
G4BootRepair>https://drive.google.com/file/d/0B41ACD_ESYnHQy1sY0paaWYwQUU/view?usp=sharing
method>https://forum.xda-developers.com/g4/help/lg-g4-vs986-super-hard-brick-unbrick-fw-t3666784
QPST>https://drive.google.com/file/d/0B41ACD_ESYnHemxoOEdGVFVOVUE/view?usp=sharing
QFIL>https://drive.google.com/file/d/0B41ACD_ESYnHRG4ta2ZZMFVtcW8/view?usp=sharing
Driver Enforcement>https://drive.google.com/file/d/0B41ACD_ESYnHWWY4Rm1GelZZZ2c/view?usp=sharing
I'll be putting together a more detailed tut. if I feelm it's needed. but for now I'm assuming most of us are pretty far along. A big thank You to TheMadScientist for being the first volunteer of the G5. MODs , if this needs to be moved feel free.
CAN'T FORGET TO MENTION THIS GREAT WORK OF ART https://forum.xda-developers.com/showthread.php?t=2600575 & * USE BOARD_DIAG-2.99 FOR TOTS
There are things which are important when it comes to using this method
first of all there are no infected files out there. at least none I'm aware of and you can believe me I know a little about this topic.
the next thing is that it highly depends on what files you are using because they are device specific! I don't say they would not work though but they will make your phone a different one.
there is NO universal one package available to unbrick all device models with the same files! This is just imposssible.
There is one method available which is able to convert any G4 and for this just check my PoC thread in the G4 forum.
It's not possible to make all this without device specific files because you flash parts of the bootloader stack and those are always device specific.
I haven't looked into your files here yet but when they work for both device models then your files are converting ones which means either it will convert to ls991 or it will convert to vs986 depending on what files you have. I strongly believe you have those for the ls991.
I can say that I have all of them and I investigated then in deep.
There are some rare for ex for the H815 which work without converting and without blowing the fuses. But there some named as h815 but containing converting to ls991.
Keep in mind that converting a device this way may be irreversible depending on the files used.
If you blow efuses you're lost and its not possible to have your previous device model back again. Well ok when you buy a new mainboard then.. But that's the only way.
I just want to warn users especially bc I'm working on a safe way for converting a device forward and backwards.
When you have a vs986 and used that method: you should bring your device in fastboot mode. Check the serial. Does it starts with LGLS991....? Then you converted the device.
sfX
Sent from my LG-H815 using XDA Labs
Well put.I agree with every thing you mention. Although the end result I'm achieving is download mode to flash the correct FW that matches the board. This is why I only use the files related to laf and take notice that I am not including the boot.IMG because that would essentially be a game changer like you said. I personally am not interested in converting carrier variants.
I'd like to add, I have personally used these firehouse ,raw, & patch on both sprint and Verizon g4's to handle 9008 bricks. I just don't have in my possession an AT&t or TMO to try these files with. If anybody has an AT&T or TMO G4 that is 9008 bricked and would like to attempt something they have not tried yet. Do Not include any boot.IMG in the created recovery folder that is to be flashed. We are achieving download mode. That's it. To be able to use LGUP TO FLASH kdz or tot.
ls991 "Download Mode" recovery image
I have taken this https://drive.google.com/file/d/0B41ACD_ESYnHa3pIQlFLYUttdzg/view?usp=sharing and simply relaced sprint stuff with verizon stuff. maybe I should rename my thread from "unbrick " to "recover download mode".
If when
If when I flash the ls991 recovery folder to vs986 in QFIL, fastboot is acheived and the command prompt window report back as my verizon with the correct serial number. maybe this info can be useful to you, I hope. Because I change carriers more than I change devices and the crossover is a major PITA.
gratefuldeaddougie said:
If when I flash the ls991 recovery folder to vs986 in QFIL, fastboot is acheived and the command prompt window report back as my verizon with the correct serial number. maybe this info can be useful to you, I hope. Because I change carriers more than I change devices and the crossover is a major PITA.
Click to expand...
Click to collapse
What do you see in fastboot? Can you make a pic for me?
Sent from my LG-H815 using XDA Labs
I can not today. As I have sold the vs986 but am receiving 2 more bricked vs986's this week. I will post a pick. Pic of phone or PC cmd window? Which is of interest. Just curious although I'll post both.
gratefuldeaddougie said:
I can not today. As I have sold the vs986 but am receiving 2 more bricked vs986's this week. I will post a pick. Pic of phone or PC cmd window? Which is of interest. Just curious although I'll post both.
Click to expand...
Click to collapse
no just a photo of the fastboot screen is enough. thx
btw: the download you link in your OP does not contain any image files - only the XMLs and the firehose?! or do i miss something here?
thx
sfX
I wanna jump on the hard brick train
Just everybody remember improper use or jumping the gun can lead past hard brick to totally unrecoverable device seen it happen a many times.
Ready Set Go
Before I begin, In reference to infected files, there are many discussions such as this https://forum.xda-developers.com/g4/help/mbn-msm8992-qpst-2-7-430-unbrick-g4-t3292097 Today I received a vs986 that as of first connection does not appear in device manager. I'm gonna be reviving it regardless of what it may needs. It's 98% cosmetically and I got it for $29 and I love doing this. the process will be documented and posted. And most of all I'd like to thank TheMadScientist & steadfasterX for their inspiration or I wouldn't be doing this. Let's cross are fingers and hope for a 9008 brick. I'll force QDloader mode with test points and screenshot the device manager and go from there. If a hardware issue is present then I will deal with that deck of cards first. Until then. . . . . . . . .. .
@ steadfasterX
Maybe I assume too much. I imagine that those who have made it this far are aware of the fact that they should have a copy of the firmware version they bricked on. At least as the bare minimum to get started with. Be back tomorrow with the results.
Having trouble?
https://drive.google.com/file/d/0B41...ew?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
This will only work if the device bricked on 27C or earlier. If you know what FW version you bricked on the extract that FW and replace the appropriate files in the recovery image folder. (for ls991 sprint>https://drive.google.com/file/d/0B41ACD_ESYnHa3pIQlFLYUttdzg/view?usp=sharing
i have my g4 on 28a so it means is not possible yet with mine ? :S
This guy figured it out back in May. Exactly the method I used. Here is his guide> http://forum.gsmdevelopers.com/showthread.php?t=28897&highlight=VS986+REPAIR I can now confirm this works only with the files from the version of FW that the device bricked on. .
28a kdz mega link
gustax said:
i have my g4 on 28a so it means is not possible yet with mine ? :S
Click to expand...
Click to collapse
https://mega.nz/#!blN0UCRB!OqJbq776ePL_PNBjzzooGU8kwTPWLAHNyXQz52TxovI
I HAVE TRIED TO EXTRACT THE FILES FROM FW 28A WITH WindowsLGFirmwareExtract-1.2.5.0, I CAN EXTRACT THE DZ FROM KDZFILE BUT WHEN I TRY TO EXTRACT THE FILE FROM DZ, THE SOFTWARE CRUSHED, I HAVE TRIED WITH WINDOWS 10 AND WINDOWS 7 AND THE SAME ISSUE. THE KDZ IT IS OK BECAUSE IT IS THE ONE I USED TO UPDATE MY PHONE
COULD YOU HELP WITH THIS
i downloaded the fw 27c and tried to extract the dz and happened the same issue, so i guess the problem is te software, but i dont know what a i need, any advice?
gustax said:
i downloaded the fw 27c and tried to extract the dz and happened the same issue, so i guess the problem is te software, but i dont know what a i need, any advice?
Click to expand...
Click to collapse
I will try the extraction on my PC. I have learned something about this method this weekend. This is a one time shot. After the second attempt the device blows a fuse. I believe the firehose programmer is the same, but, the raw & patch files are specifically for the sprint. I think I may have permanently bricked a device attempting to re-create the scenario in which I was successful with during the first go at it. I'm gonna look at the 27C.kdz real quick
Hello, Ya all... hope you're doing fine.
I searched for days to find a serious guide to root moto c, xt1754, and wasnt successful. Now, am an older guy and I sure cant dive as deep as you do into that area Had me a fine Moto G and rooted it with XDA know how pretty good. Unfortunately this device got stolen a few weeks ago. Since am not a rich man and that I needed a new device, I got the Moto C. I can see for myself thats a pretty simple piece... but till am able to get a better Moto - I'd like to root XT1754 either. So, is anyone willing to help me? Could I use the files I once successful used for Moto E and G, logically updated?
Is Moto C another kind Moto E?
Hope I'd describe my case well enough for you. I also truly hope someone might have mercy with me and can let me know what I've to do.
Wish you all a Good Time at All.
Tyd27
In short, no, you cannot use the same files as on previous gen Moto's. The reason behind it... quite simple: they have absolutely nothing in common. This Moto C sports an MTK processor, to begin the long list of differences.
What you can try is this:
1. Unlock your bootloader. Either via Motorola Developer Website, or via fastboot oem unlock.
adb reboot bootloader
fastboot oem unlock
OR
fastboot oem unlock UNLOCK_CODE_FROM MOTOROLA
Once you're done with that, re-enable USB Debugging and OEM UNLOCK ( if you need to turn it back on ).
Then install the latest Magisk app from www.tiny.cc/latestmanager
At this stage, you will need your original boot image ( from here: https://www.needrom.com/download/moto-c-4g-xt1754-nrd90m-054-row-official-rom/). You will need to register there, and wait basically until forever for that firmware file to finish downloading. Open that up with 7zip and extract it. Find the file called boot-signed.img.
Patch it using Magisk.
move that patched_boot.img in your ADB directory.
adb reboot bootloader.
fastboot flash boot patched_boot.img
At this point, 2 options:
a. It will flash, in which case you will do fastboot reboot
b. it will not flash, in which case you will get an error ( boot image not signed etc)
If the first option occurs, you might get a "corrupt" error screen upon reboot. Follow the steps and let the phone do a factory reset. If it reboots properly, re-install Magisk and enjoy root.
if it does not want to reboot properly... you'll congratulate yourself on having the firmware handy
So, thanx alot for this answer. Am happy that someone took care now coz i really dont like unrooted devices. Well, the other side is am 58 now and not a professional at phones. Rooted a few motos with xda help and all went good. Unfortunately my last moto g got stolen and fir what reason ever else i chose to get moto c. Probably it was realky damn ****n stupid. Until i can afford another moto i going to try everything to root moto c. I'll read your reply now before i start doing it. Too bad that there is no way rooting it like moto g. Does it mean i wont have twrp neither?
Have a Good Day.
Tyd27
Definitely no TWRP on it, until someone with the knowledge will port it. That's just how it goes with MTK Devices and their closed source, I'm afraid.
Hi can u make a custom recovery for moto c xt1754
https://forum.xda-developers.com/android/development/recovery-twrp-3-1-1-0-moto-c-t3703184
Moto G5 Plus dead after the downgrade of stock rom from latest august security patch.LED Blinks . Also tried all blank flash files nothing works. HELP!! Thank you :crying:
Currently we don't have a leaked blankflash that's newer than the April 2017 Moto Z2 Play albus blankflash. (if you want the blankflash, here's one here https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M ). As such, we may not be able to rescue newer corrupted bootloaders (like yours, with a corrupted August 2018 bootloader - corrupted by flashing an old OTA update). Unfortunately, you may have to give your device to a service centre and may have to pay for a motherboard replacement (which are quite expensive). The alternative is to give up the device and buy another device and put this up to an expensive learning lesson - especially with Moto devices, do not use OTA updates when you've flashed older stock firmware, especially if that flash downgraded your stock firmware.
You may be lucky if someone decides to make a cloned image of a working G5 Plus and uploads that, in a similar process used to rescue G5/G5S devices : https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-create-mmcblk0-img-device-t3803176 https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150 However, that cloned image is a full copy of whatever device it came from, including IMEI, serials and any data left on it, so really it's only if someone wanted to give up their G5 Plus. If you really need a working device now, unfortunately you'll have to pay for the motherboard repair or buy a new device.
echo92 said:
Currently we don't have a leaked blankflash that's newer than the April 2017 Moto Z2 Play albus blankflash. (if you want the blankflash, here's one here https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M ). As such, we may not be able to rescue newer corrupted bootloaders (like yours, with a corrupted August 2018 bootloader - corrupted by flashing an old OTA update). Unfortunately, you may have to give your device to a service centre and may have to pay for a motherboard replacement (which are quite expensive). The alternative is to give up the device and buy another device and put this up to an expensive learning lesson - especially with Moto devices, do not use OTA updates when you've flashed older stock firmware, especially if that flash downgraded your stock firmware.
You may be lucky if someone decides to make a cloned image of a working G5 Plus and uploads that, in a similar process used to rescue G5/G5S devices : https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-create-mmcblk0-img-device-t3803176 https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150 However, that cloned image is a full copy of whatever device it came from, including IMEI, serials and any data left on it, so really it's only if someone wanted to give up their G5 Plus. If you really need a working device now, unfortunately you'll have to pay for the motherboard repair or buy a new device.
Click to expand...
Click to collapse
I had wondered about whether or not that approach would work, never had the inclination to try it. We do have to remember that essentially the block device is just a collection of filesystems, just like any other PC or laptop hard drive / SSD.
Just noting that the process could be adapted to skip the persist partition on restore, so that the existing persist could be preserved. The dd command allows you to skip a certain number of blocks, using either the skip or count options with a suitable block size. Would need someone to get their calculator out, and to take time to look at the partition layout. All the best to the OP if they can find someone who can help out.
Edit: Or it could be done partition by partition. That would hopefully work as well?
NZedPred said:
I had wondered about whether or not that approach would work, never had the inclination to try it. We do have to remember that essentially the block device is just a collection of filesystems, just like any other PC or laptop hard drive / SSD.
Just noting that the process could be adapted to skip the persist partition on restore, so that the existing persist could be preserved. The dd command allows you to skip a certain number of blocks, using either the skip or count options with a suitable block size. Would need someone to get their calculator out, and to take time to look at the partition layout. All the best to the OP if they can find someone who can help out.
Click to expand...
Click to collapse
Hmm, that's a possibility - since all we need is a cloned image to write to an SD card (effectively acting as a secondary flash storage), in theory you could skip the persist partition when making the original copy. Then, uploading it may not be as big a problem with regards to IMEI as the image wouldn't contain another device's persist partition for someone to copy.
Persist, as I understand it, wouldn't be affected on the original device since all we're using the cloned image for is to boot the original device - the cloned image's bootloader in theory should be able to load in the event the original device's bootloader is damaged (as in this case where an OTA update corrupted the original bootloader). Then, you'd re-flash the stock firmware and a working bootloader to the original device, leaving the original persist intact.
echo92 said:
Currently we don't have a leaked blankflash that's newer than the April 2017 Moto Z2 Play albus blankflash. (if you want the blankflash, here's one here https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M ). As such, we may not be able to rescue newer corrupted bootloaders (like yours, with a corrupted August 2018 bootloader - corrupted by flashing an old OTA update). Unfortunately, you may have to give your device to a service centre and may have to pay for a motherboard replacement (which are quite expensive). The alternative is to give up the device and buy another device and put this up to an expensive learning lesson - especially with Moto devices, do not use OTA updates when you've flashed older stock firmware, especially if that flash downgraded your stock firmware.
You may be lucky if someone decides to make a cloned image of a working G5 Plus and uploads that, in a similar process used to rescue G5/G5S devices : https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-create-mmcblk0-img-device-t3803176 https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150 However, that cloned image is a full copy of whatever device it came from, including IMEI, serials and any data left on it, so really it's only if someone wanted to give up their G5 Plus. If you really need a working device now, unfortunately you'll have to pay for the motherboard repair or buy a new device.
Click to expand...
Click to collapse
what about the JTAG method here in pune there is a service on JTAG method the said that they while recover my phone ??? website - http://mobileunbrick.com/ .......thanks for reply check that website
ruturaj0077 said:
what about the JTAG method here in pune there is a service on JTAG method the said that they while recover my phone ??? website - http://mobileunbrick.com/ .......thanks for reply check that website
Click to expand...
Click to collapse
You could give them a try, see if they can unbrick your device.
echo92 said:
You could give them a try, see if they can unbrick your device.
Click to expand...
Click to collapse
Thanks for the reply !! ok but when will latest blankflash will release any idea after the oreo update ??
ruturaj0077 said:
Thanks for the reply !! ok but when will latest blankflash will release any idea after the oreo update ??
Click to expand...
Click to collapse
I don't have any idea nor any guarantees that we'd even see one. Most of the blankflashes we have on XDA are leaked from the OEMs, so as such there may be no newer blankflash at all. OEMs see these blankflashes as internal development tools and releasing then may be a security risk. You may have a sympathetic engineer leak one, at the possible risk of their job, or see if the Motorola one gets a leaked blankflash (as it comes with a SD 625). However, i would not bet money on either outcome. If you want to get a working device now, you'll have to pay unfortunately, the cost of hardbricking any device, i guess.
ruturaj0077 said:
Moto G5 Plus dead after the downgrade of stock rom from latest august security patch.LED Blinks . Also tried all blank flash files nothing works. HELP!! Thank you :crying:
Click to expand...
Click to collapse
mine stuck in bootloader what to do now please help
zooreo said:
mine stuck in bootloader what to do now please help
Click to expand...
Click to collapse
bootloader ?? flash the stock rom with the help of adb commands ....fastboot method
Hello, thank you very much for reading, I hope you can help me. I need one or more files to be able to recover my phone: Samsung Galaxy S7 Active.
These are the files that I need:
prog_emmc_firehose_8996.mbn (.elf)
rawprogram0.xml
patch0.xml
I do not know if I would also need these:
MPRG8996.hex
rawprogram_unsparse.xml
I think these files are the same as prog_emmc_firehose_8996.mbn (.elf):
8996_msimage.mbn
MSM8996.mbn
How did I make a brick my phone? Installing the first official version:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
Previously I used this version without any problem:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
I wish someone could help me, I have read more than 50 pages, but I have not been able to solve the problem.
Please.
Can anybody help me?
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
I hope someone helps us.
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
yakine13 said:
hey.... i'm on the same situation..
i need zuk Z2 pro/ prog_ufs_firehose_8996_ddr_zuk.mbn but i only have elf....
it's to remove this stupid frp lock from someone who forgot his first mail... :/
keep going we are going to find out the solution
Click to expand...
Click to collapse
yakine13 said:
HEY!
I found a way!!!
...for me:/
why you want this emmc_firehose_8996.mbn?
actually, i think that you don't need that file especially, it doesn't exist from where i've searched.
if it's to flash your phone all you need is odin and a flashable file of your phone firmware
i had a zuk z2 pro and was locked with frp when i wanted to setup custom rom AOSP 9.0.0 for example.
but i managed to unlock it by flashing a custom rom without gapps in the first place to no get locked out.
tell me how your phone is reacting, what do you have access to, and your initial step before brick
Click to expand...
Click to collapse
Hello, sorry for my bad English. My phone is a Samsung Galaxy S7 Active (SM-G891A). I will try to explain what happened.
I had this version of Android 6 installed (via Odin) on the phone:
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT
With that version my phone was fine, but then I tried to install the first version of Android 6 (official) via Odin:
SM-G891A_G891AUCU1APG7_ATT_Full_Repair_Frimware
When the installation was completed (Odin said the installation was successful), the phone never restarted. There is no way to turn it on with any combination of buttons, nor with a microSD with a debrick.img. A USB JIG has not worked for me either.
Windows detects my phone in Qualcomm 9008 mode. Odin does not detect it.
did you find a solution?
actually it look like to be a hard brick but as it's snapdragon 820 you can recover from it
I'm waiting for the day when noobs and half-noobs (no offense, all of us have been there) will start reading before writing and stop assuming that their 1st aid kit will revive a kitten ran over by a train.
It's okay not to know, but before writing a spam reply, just consider for a second that the user already tried your solution and is already a step ahead.
Listen guy, go to Halab Tech. They have certain firmwares for what you need, but they ask money.
Those type of firmwares have a prefix "DEBUG_EMERGENCY_DOWNLOAD_FA....'
In my case it's "DEBUG_EMERGENCY_DOWNLOAD_FA70_G955U1SQU6ASG1_CL12542406_QB24669289_REV00_user_mid_noship_MULTI_CERT.tgz"
As I consider that a bastard move (since they are selling Samsung's intellectual property as their own, stuff that should be public in the first place), I encourage you to share the files if you buy them, so that we can all use them and screw over these monopoly playing-intellectual property stealing bastards.
I'm now working on a recovery of my G955U1 (S8+ Qualcomm USA). I paid $25 for a god damn firmware and I'm gonna post it in next couple of days.
I'm personally having trouble of flashing the firmware (because not many flash tools support flashing .elf flash loaders), but I used one FRP tool (Octoplus FRP tool) to check the loader and it managed to send it, receive the "hello" packet, read partitions and erase the FRP partition (I assume it worked by the log), but I don't have a way to flash other partitions yet.
You people should have in mind one thing: even though certain devices have the same chipset, doesn't mean that you can use the same firehose flash loader, since manufacturers create different loaders for them and write their digital signatures into the chip (don't know is it hardwired or flashed), meaning that you cannot use Xiaomi's prog_ufs_firehose_8998_ddr.elf (just an example) to flash a Samsung device with MSM8992 chipset.
In fact, I think that each phone model and possibly even it's different firmware revisions have unique loaders, since I didn't manage to get a successful response from my G955U1 by sending G955U2 loader, and the loader which I managed to send is actually stated to be for G955U1U6 (U6 is the bootloader revision number, while U1 is the part of the model number).
Best of luck, contact me if you need help.