Related
Hello everybody, so I noticed a lot of people struggling with marshmallow + autorec hard bricks (symptoms: no download mode, no recovery, black screen)
Just to make sure: I'm not responsible for any damages done. This worked for me perfectly, should work for you too. Use it only if you bricked D855 30B!!! (Marshmallow)
Here's what you have to do to fix that:
First follow this amazing guide by senior member l33tlinuxh4x0r, big thanks to him. ---> LINK TO GUIDE
Important stuff: You need to install qualcomm drivers (windows 8, 10 users need to disable driver signature enforcement), you need to short the circuit of your phone, like it's shown in that guide, by shorting it correctly and plugging it in you immediately get connection (keep note of that, there's no need to wait for something, no sound - redo.)
Instead of extracting tot, like it's shown there, use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go.
DOWNLOAD HERE
Didn't know where to upload, so sorry for using this abomination
hi...please help~
catercousin said:
Hello everybody, so I noticed a lot of people struggling with marshmallow + autorec hard bricks (symptoms: no download mode, no recovery, black screen)
Just to make sure: I'm not responsible for any damages done. This worked for me perfectly, should work for you too. Use it only if you bricked D855 30B!!! (Marshmallow)
Here's what you have to do to fix that:
First follow this amazing guide by senior member l33tlinuxh4x0r, big thanks to him. ---> LINK TO GUIDE
Important stuff: You need to install qualcomm drivers (windows 8, 10 users need to disable driver signature enforcement), you need to short the circuit of your phone, like it's shown in that guide, by shorting it correctly and plugging it in you immediately get connection (keep note of that, there's no need to wait for something, no sound - redo.)
Instead of extracting tot, like it's shown there, use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go.
DOWNLOAD HERE
Didn't know where to upload, so sorry for using this abomination
Click to expand...
Click to collapse
i don't get what the meaning "use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go. "
can u explain how to done this step???
is this hard brick the result of using the Autorec MM or the old Lollipop one?
shun95 said:
i don't get what the meaning "use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go. "
can u explain how to done this step???
Click to expand...
Click to collapse
Select the attached download folder as "Target DIR" in the application, it will load the files and let you flash them like it's shown in the tutorial
Broloff said:
is this hard brick the result of using the Autorec MM or the old Lollipop one?
Click to expand...
Click to collapse
The Lollipop one
Hi thank you for this post
catercousin said:
Hello everybody, so I noticed a lot of people struggling with marshmallow + autorec hard bricks (symptoms: no download mode, no recovery, black screen)
Just to make sure: I'm not responsible for any damages done. This worked for me perfectly, should work for you too. Use it only if you bricked D855 30B!!! (Marshmallow)
Here's what you have to do to fix that:
First follow this amazing guide by senior member l33tlinuxh4x0r, big thanks to him. ---> LINK TO GUIDE
Important stuff: You need to install qualcomm drivers (windows 8, 10 users need to disable driver signature enforcement), you need to short the circuit of your phone, like it's shown in that guide, by shorting it correctly and plugging it in you immediately get connection (keep note of that, there's no need to wait for something, no sound - redo.)
Instead of extracting tot, like it's shown there, use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go.
DOWNLOAD HERE
Didn't know where to upload, so sorry for using this abomination
Click to expand...
Click to collapse
I've the same problem as you describe here.After I upgraded g3 to marshmallow I applied autorec and my device became hard brick.now my phone under com ports as Qualcomm 9008.
from this point I'm confused that which way to go the first your description 'Instead of extracting tot, like it's shown there, use attached files (target Dir)', Then again, flash them like it's shown in the tutorial'',the second tot file of the rom that we were running. (not older not newer same version).The first way I did not understand attached files where are they ?
if I follow the second way how can I find tot of my rom D855 30B!!! (Marshmallow)?
thank you waiting your help
Instead of tot you use the files from the download link in my post since you don't need to extract tot now, just mark that folder in "target dir" and follow the second guilde, as you call it. Good luck!
Help
catercousin said:
Hello everybody, so I noticed a lot of people struggling with marshmallow + autorec hard bricks (symptoms: no download mode, no recovery, black screen)
Just to make sure: I'm not responsible for any damages done. This worked for me perfectly, should work for you too. Use it only if you bricked D855 30B!!! (Marshmallow)
Here's what you have to do to fix that:
First follow this amazing guide by senior member l33tlinuxh4x0r, big thanks to him. ---> LINK TO GUIDE
Important stuff: You need to install qualcomm drivers (windows 8, 10 users need to disable driver signature enforcement), you need to short the circuit of your phone, like it's shown in that guide, by shorting it correctly and plugging it in you immediately get connection (keep note of that, there's no need to wait for something, no sound - redo.)
Instead of extracting tot, like it's shown there, use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go.
DOWNLOAD HERE
Didn't know where to upload, so sorry for using this abomination
Click to expand...
Click to collapse
The link is DEAD...
Maybe someone can reupload? I messed up and didn't save it in my computer, didn't think I'd need it anymore. Oops.. Or create them yourself
You need do extract .kdz, then .dz,
use this guide to create partition.txt
http://forum.xda-developers.com/lg-g2/general/how-to-create-partition-txt-file-kdz-t3109859
and rename files to ****.mbn
i just had my phone back to normal after marshmallow autorec brick
Get the right tools from scamex only..
U going to need :
Qdloader hs-usb driver for your pc 32/64bit
Install it
Then get smart boot diagnostic tool
Along that also get ap-chip dll and att
Then extract it the ap folder inside smart boot diagnostic tool
Get document to shows how to flash a "dead boot"
Then run thr smart boot diagnostic tool
Then follow instruction from the document and pay attention on page 14, 15 & 16
After recovering qfprom anti-roolback issue.
Your phone should be back to normal as before the autorec root hardbrick
catercousin said:
Maybe someone can reupload? I messed up and didn't save it in my computer, didn't think I'd need it anymore. Oops.. Or create them yourself
You need do extract .kdz, then .dz,
use this guide to create partition.txt
http://forum.xda-developers.com/lg-g2/general/how-to-create-partition-txt-file-kdz-t3109859
and rename files to ****.mbn
Click to expand...
Click to collapse
hey, the guide from the link is gone. do you happen to remember how to get partition.txt from .kdz ...or do you have one?
Hey!
Can anyone reupload the files from the OP?
Thanks!
Link is dead, can someone reupload the files please!?
unbelieveable.
every single link is dead for this
GET DROPBOX.
shoaibiftekhar said:
hey, the guide from the link is gone. do you happen to remember how to get partition.txt from .kdz ...or do you have one?
Click to expand...
Click to collapse
Still the case.
Could anyone help, please?
I found a guide to create "partition.txt" (maybe a copy the original guide here) but that's for the G2.
Any help is greatly appreciated :crying:
Bricked my razer a while back reinstalling the stock firmware. The cable unplugged from the phone and corrupted the storage. Cant enter recovery or bootloader. But according to some resources that i came across while doing some research, im able to interface with the device using the qualcomm hs-usb protocol. With that im able to directly access the devices storage. If anyone is willing to help, what id need is for you to wipe your device clean, and run these commands
Adb shell
Su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
From there id be able to delete the partition table, and copy the devices storage config from the backup. Once thats established id be able to access bootloader recovery and system.
If anyone is able to help, id really appreciate it
Thanks
i too have done the exact same now stuck with a brick hope someone can help
slavix66 said:
Bricked my razer a while back reinstalling the stock firmware. The cable unplugged from the phone and corrupted the storage. Cant enter recovery or bootloader. But according to some resources that i came across while doing some research, im able to interface with the device using the qualcomm hs-usb protocol. With that im able to directly access the devices storage. If anyone is willing to help, what id need is for you to wipe your device clean, and run these commands
Adb shell
Su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
From there id be able to delete the partition table, and copy the devices storage config from the backup. Once thats established id be able to access bootloader recovery and system.
If anyone is able to help, id really appreciate it
Thanks
Click to expand...
Click to collapse
hi any look on finding emmc or a work around for this?.i been at it all day i even resorted to opening device up to disconnect battery...nothing
parky169 said:
hi any look on finding emmc or a work around for this?.i been at it all day i even resorted to opening device up to disconnect battery...nothing
Click to expand...
Click to collapse
Nope nothing yet, we need either emmc development files for the phone, no likely to find. And with the qualcomm tools the corrupted storage can be re partitioned and again be written to.
However if someone with a working razer was to wipe the device clean, and dump partition info. Then the images can be written to the device, over writing the damaged partitions.
Black screen on my razer phone. can't access download or recovery. any help will be greatly appreciated. the computer makes a sound when I plug in the razer phone.
sinkoo1979 said:
Black screen on my razer phone. can't access download or recovery. any help will be greatly appreciated. the computer makes a sound when I plug in the razer phone.
Click to expand...
Click to collapse
Your razer is in a state known as EDL. I5s the qualcomm Emergency Download mode. Used to program your emmc storage. That is exactly what the few of us are experiencing, however with no owners of the device willing to share a default wiped image of their emmc, there is no way for us to remap the partitions appropriately in order to once again flash and access the bootloader.
If you could let me know how one would do it I might be able to help you before I sell my razer phone
Thank you, if you restore your phone back to factory settings, connect to pc via adb and run the command in the initial post. That command should (from what i read elsewhere) create a full backup of the partitions on your device. If you are successfull and are able to share through some cloud storage such as dropbox or something of the like, i should be able to restore my razer.
slavix66 said:
Thank you, if you restore your phone back to factory settings, connect to pc via adb and run the command in the initial post. That command should (from what i read elsewhere) create a full backup of the partitions on your device. If you are successfull and are able to share through some cloud storage such as dropbox or something of the like, i should be able to restore my razer.
Click to expand...
Click to collapse
im guessing i will need root to run those commands, atm i am performing a full nandroid backup of everything before i do the reset, my phone is rooted and has twrp installed on both a and b partions
extracted the files, the img is 13GB so gonna compress it before i upload it, hopefully it should work but will have to be tomorrow now
uploading the file now
ok done, heres the link
http://www.mediafire.com/file/j3j6pp3ym161t0q/backup.7z/file
you will need 7zip to extract it which you can get from here for free www.7zip.org
slavix66 said:
Bricked my razer a while back reinstalling the stock firmware. The cable unplugged from the phone and corrupted the storage. Cant enter recovery or bootloader. But according to some resources that i came across while doing some research, im able to interface with the device using the qualcomm hs-usb protocol. With that im able to directly access the devices storage. If anyone is willing to help, what id need is for you to wipe your device clean, and run these commands
Adb shell
Su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
From there id be able to delete the partition table, and copy the devices storage config from the backup. Once thats established id be able to access bootloader recovery and system.
If anyone is able to help, id really appreciate it
Thanks
Click to expand...
Click to collapse
hi xda member dtronics has very kindly uploaded a complete back up approx 13gb
file.do you know how to use this to restore/repair our phones?.
Excellent, i will take a look and see if i can push it to the device in edl mode. The thread has been dead for a while, so it may take a while for me to review all the previous resources that led me to the point where i had posted this thread.
Thank you so very much!
This is the article I was using to attempt salvaging my phone.
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Unfortunately I am in the EDL mode where my device storage is not recognized, so I am unable to tamper with it until the razer phones flash programmer or firehose files have been leaked.
Hopefully someone else may have success resurrecting their device using dtronic's backup and or with the information provided in the link.
Thank you any and all of you who have contributed or followed the thread. But my trail ends here unless the flash programmer files are somehow made available.
Unfortunately sadly I too couldn't work out a way to flash or recover razer phone with the upload from dtronics.thank you to all involved,but I think it's time to chuck the old razer in the bin.this is my first ever failure or perm bricked device since I started rooting etc with the HTC wildfire.
?
Tried Klinik handphone medan (google search). They have firehose for msm 8998 but I removed the usb cable when it was flashing (didn't look like it was flashing anything) now the computer don't even recognize the phone....
getting this message "Unknown USB Device (Device Descriptor Request Failed)".
parky169 said:
Unfortunately sadly I too couldn't work out a way to flash or recover razer phone with the upload from dtronics.thank you to all involved,but I think it's time to chuck the old razer in the bin.this is my first ever failure or perm bricked device since I started rooting etc with the HTC wildfire.
Click to expand...
Click to collapse
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
---------- Post added at 04:07 AM ---------- Previous post was at 04:07 AM ----------
slavix66 said:
This is the article I was using to attempt salvaging my phone.
https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Unfortunately I am in the EDL mode where my device storage is not recognized, so I am unable to tamper with it until the razer phones flash programmer or firehose files have been leaked.
Hopefully someone else may have success resurrecting their device using dtronic's backup and or with the information provided in the link.
Thank you any and all of you who have contributed or followed the thread. But my trail ends here unless the flash programmer files are somehow made available.
Click to expand...
Click to collapse
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
sinkoo1979 said:
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
---------- Post added at 04:07 AM ---------- Previous post was at 04:07 AM ----------
is there any way to pull the firehose and xml file from working razer phone? getting another one for cheap.
Click to expand...
Click to collapse
I wouldnt know for sure. But my understanding is the programmer files (firehose or sahara files) arent stored on the device. They are used by programmer interface to identify the processor as well as the storage media, possibly all harware for the device. If this were a more mainstream device the programmer files may have been available to us through a leak. Only way to fix it at this point would be to bring it to a shop, they should have access to the files one way or another.
I don't know, I don't have my razer phone any more, went and got myself a OnePlus 6t, the emmc file is still available to download from my post and still looking for people to mirror the file
If you try this method, I nor anybody else is responsible for any further damage done to your phone.
Models Confirmed : V300L
We currently have firehose for V30.
Therefore, we can program UFS flash memory in 9008 mode.
It requires rawprogram?.xml(s) and patch?.xml(s) to program it.
It's easy to generate rawprogram?.xml(s) from kdz file, but generate patch?.xml(s) is not easy. (Unfortunately, I couldn't have time to generate patch?.xml(s)).
I have edited kdztools to generate rawprogram?.xml(s) easily (You can generate it by using "-r" argument. Currently, generate patch?.xml(s) is not supported. I'll add it soon).
I used patch?.xml(s) in post. it works well, but boot loop in the LG Logo.
However, it was possible to enter download mode.
------------------- GUIDE -------------------1. Download rawprogram?.xml patch?.xml with images from link. (It uses V300L30h000906.kdz)
2. Download firehose (prog_ufs_firehose_8998_lgev30.elf) from link.
<< Linux >>
3. Build qdl or download pre-built binary
4. Extract zip or tar.gz files 1, 2, 3 in any folder.
5. Run
Code:
$ ./qdl --storage ufs prog_ufs_firehose_8998_lgev30.elf rawprogram0.xml patch0.xml rawprogram1.xml patch1.xml rawprogram2.xml patch2.xml rawprogram3.xml patch3.xml rawprogram4.xml patch4.xml rawprogram5.xml patch5.xml rawprogram6.xml patch6.xml
in the terminal.
6. If LG logo shows, enter to the download mode.
<< Windows >>
3-6. You can program by QFIL similar as qdl.
7. Connect to any Windows PC with LGUP (must support Android Pie).
8. Flash kdz with ChipErase. (IMPORTANT)
9. If it boots successfully, your device has unbricked.
you can create rawprogramer and patch.xml with this program
I have already tried it on lg v10 kdz with successful.
after extract kdz :
1-open qualcomtool 2.4 and go to EMMC tabe.
2-clic browse and select primarygpt_0.bin
3- select all partitions and click exract partition
4- click extract firmware
you will find every things you need in extracted folder.
you can edid rowprogramer.xml with notepad ++ .
edit : tryed with lg v30 kdz not work
(gpt not present when select file)
Thank you for your work
download problem
quickwshell said:
If you try this method, I nor anybody else is responsible for any further damage done to your phone.
Models Confirmed : V300L
We currently have firehose for V30.
Therefore, we can program UFS flash memory in 9008 mode.
It requires rawprogram?.xml(s) and patch?.xml(s) to program it.
It's easy to generate rawprogram?.xml(s) from kdz file, but generate patch?.xml(s) is not easy. (Unfortunately, I couldn't have time to generate patch?.xml(s)).
I have edited kdztools to generate rawprogram?.xml(s) easily (You can generate it by using "-r" argument. Currently, generate patch?.xml(s) is not supported. I'll add it soon).
I used patch?.xml(s) in post. it works well, but boot loop in the LG Logo.
However, it was possible to enter download mode.
------------------- GUIDE -------------------1. Download rawprogram?.xml patch?.xml with images from link. (It uses V300L30h000906.kdz)
2. Download firehose (prog_ufs_firehose_8998_lgev30.elf) from link.
<< Linux >>
3. Build qdl or download pre-built binary
4. Extract zip or tar.gz files 1, 2, 3 in any folder.
5. Run
Code:
$ ./qdl --storage ufs prog_ufs_firehose_8998_lgev30.elf rawprogram0.xml patch0.xml rawprogram1.xml patch1.xml rawprogram2.xml patch2.xml rawprogram3.xml patch3.xml rawprogram4.xml patch4.xml rawprogram5.xml patch5.xml rawprogram6.xml patch6.xml
in the terminal.
6. If LG logo shows, enter to the download mode.
<< Windows >>
3-6. You can program by QFIL similar as qdl.
7. Connect to any Windows PC with LGUP (must support Android Pie).
8. Flash kdz with ChipErase. (IMPORTANT)
9. If it boots successfully, your device has unbricked.
Click to expand...
Click to collapse
thank you so much,but can't download zip from this website,if you can offer other download way,such as google,mega,onedrive,i will apreciate it so much,thanks for your work
Johoneycn said:
thank you so much,but can't download zip from this website,if you can offer other download way,such as google,mega,onedrive,i will apreciate it so much,thanks for your work
Click to expand...
Click to collapse
Sorry for the late reply
mega. nz/#!zCZBkC4D!Vxo9wrd1c9vsZgCfQIrLelcp3unTY7sJAqMXjANvzjQ is V30_UNBRICK.zip
and mega. nz/#!PLIBzQ6L!JKtfq_RH2iFgcQckkRi_LtZGt9u2zaO2YF6x8dtHL6A is a firehose.
It is a shame we resort to such lengths for this. Shame on vendors. It is like pure gold or diamonds when we come across a programmer...
Hi, @quickwshell, could you see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot. Does the problem I'm facing now is what your method targeting to?
@quickwshell
Thank you so much for sharing firehorse for v30 and this solution. I have LS998 bricked bootloop after interrupting upgrade as @zacox123. I tried your files posted but still phone cant get download mode. Now Im trying to create rawprogram.xml and patch.xml from specific firmware model ls998 but I want to know what partitions are necesary just for getting download mode and then try to upgrade for usb mode.
Could you please help me?
thanks in advance
Pulian said:
@quickwshell
Thank you so much for sharing firehorse for v30 and this solution. I have LS998 bricked bootloop after interrupting upgrade as @zacox123. I tried your files posted but still phone cant get download mode. Now Im trying to create rawprogram.xml and patch.xml from specific firmware model ls998 but I want to know what partitions are necesary just for getting download mode and then try to upgrade for usb mode.
Could you please help me?
thanks in advance
Click to expand...
Click to collapse
How did you do with your phone? Have you made your phone into 9008 mode? Did you use the correct tool?
I have not processed my problem yet. But I read some other posts introducing that, use qpst or miracle box or any similar tools with the edl file provided by @quickwshell to flash in twrp directly, instead of getting download mode back. Maybe you can have a trial.
I was converting my lg [email protected] for unlocking. I have tools for flashing and I did it before with others phones. Accidently flashing process was interrupted and phone got that condition, no download mode. Now I'm using testpoint connection and UMT (tool for repair Qualcomm Phones) for trying to recover download mode. I suppose you can use QFIL for programming after we have correct rawprogramer.xml and patch.xml. Let me finish my test and I'll post results.
Pd: bootloader is not unlocked and I don't know if I can write twrp and it'll work.
Could you share links referring this topic and phone? Thanks.
Well, it definitely worked :good:.
Partitions extracted from us998 firmware
. Now I'm flashing again.
Pd: sorry for inverted picture. I make it from cellphone without edition
Do we need any special process before the computer work, @quickwshell and @Pulian? Is any special cable or teardown work needed? I have never used 9008 before but see other brands like xiaomi cannot simply enter 9008 mode directly.
---------- Post added at 04:27 PM ---------- Previous post was at 04:08 PM ----------
Pulian said:
Well, it definitely worked :good:.
Partitions extracted from us998 firmware
. Now I'm flashing again.
Pd: sorry for inverted picture. I make it from cellphone without edition
Click to expand...
Click to collapse
I see octoplus in your pic. Could you please share your tools and detailed steps? I have never tried 9008, so I hope some extra hand-by-hand instructions. Thanks.
The post I read is from an Android community app, and I'm afraid I cannot provide a link to it. And the author of that post said he had not tested yet, just some common sense and rough idea. I'd hear more from you, afterwards you have succeeded.
Thanks again @quickwshell. Firehorse file is the most important think for starting.
1. I extracted files partitions from firmware KDZ using this software https://forum.xda-developers.com/showthread.php?t=2600575
2.. I used testpoint for getting EDL (QUALCOM 9008) connection. https://forum.xda-developers.com/showpost.php?p=78573920&postcount=2
3. I tried firmware posted here without success (Maybe it works on others). So I wrote critical partitions extracted from my specific firmware (US998) using UMT box and I didnt need to create .xml files because this tool can read and detect internal partitions.
4. I got download mode and just write firmware by USB using octoplusbox. Phone Alive!!
I think every step here can be replaced using diferent software. good luck!
nate0 said:
It is a shame we resort to such lengths for this. Shame on vendors. It is like pure gold or diamonds when we come across a programmer...
Click to expand...
Click to collapse
yes,i think so too, lg is too bad on the software
Pulian said:
Thanks again @quickwshell. Firehorse file is the most important think for starting.
1. I extracted files partitions from firmware KDZ using this software https://forum.xda-developers.com/showthread.php?t=2600575
2.. I used testpoint for getting EDL (QUALCOM 9008) connection. https://forum.xda-developers.com/showpost.php?p=78573920&postcount=2
3. I tried firmware posted here without success (Maybe it works on others). So I wrote critical partitions extracted from my specific firmware (US998) using UMT box and I didnt need to create .xml files because this tool can read and detect internal partitions.
4. I got download mode and just write firmware by USB using octoplusbox. Phone Alive!!
I think every step here can be replaced using diferent software. good luck!
Click to expand...
Click to collapse
After getting download mode back, do we need chiperase like @quickwshell mentioned? I don't know if octoplusbox did it before writing firmware and I suppose most people would still use LGUP for firmware writing. Did you lose s/n, imei, etc. after phone booting? If not, I guess partition dl should be OK.
I didnt touch imei and security partitions. My phone worked after flashing without problems.
Pulian said:
Thanks again @quickwshell. Firehorse file is the most important think for starting.
1. I extracted files partitions from firmware KDZ using this software https://forum.xda-developers.com/showthread.php?t=2600575
2.. I used testpoint for getting EDL (QUALCOM 9008) connection. https://forum.xda-developers.com/showpost.php?p=78573920&postcount=2
3. I tried firmware posted here without success (Maybe it works on others). So I wrote critical partitions extracted from my specific firmware (US998) using UMT box and I didnt need to create .xml files because this tool can read and detect internal partitions.
4. I got download mode and just write firmware by USB using octoplusbox. Phone Alive!!
I think every step here can be replaced using diferent software. good luck!
Click to expand...
Click to collapse
I searched a lot for UMT Box and it seems like one has to collect it with the dongle or else it's not gonna work. Getting frustrated here Are there any way other than umt? Can you or anyone suggest?
moyedchowdhury said:
I searched a lot for UMT Box and it seems like one has to collect it with the dongle or else it's not gonna work. Getting frustrated here Are there any way other than umt? Can you or anyone suggest?
Click to expand...
Click to collapse
use cracked miracle box
seloka180 said:
use cracked miracle box
Click to expand...
Click to collapse
THANKS FOR COMING BACK. Mine is a LS998 converted into US998.
I'm So disappointed right now. Past few days have been unbearable. Even my Blood pressure is getting high
I'll describe what happened so that the situation is understood and you could suggest accordingly.
*I unlocked bootloader by wtf method.
*Tried several roms.
*Decided to stay on LOS 17.1 Q [Nearly got f*****g everything]
*Flushed a module via magisk which offered pixel boot animation(actually was searching for smartpixel to turn off 50% pixels)
*Rebooted and the device stuck into bootloop
*Rebooted into fastboot mode and reinstalled twrp and reboot- No luck
*Used a guide to wipe different partitions via fastboot and then reinstall twrp. Success but still boot stuck.
*Tried to go into download mode by pressing volume up while connecting USB, went into the mode but "waiting for any connection..." showed and was not detected by device mgr.
*Thought relocking the bootloader might get me into download mode.(That's when I burnt my luck I guess...)
*Did lock the bootloader.
*Aaaand still not detected in device manager.
*Moreover, now showing that Your device has failed a routine security check and will not boot!
{
"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"
}
*Opened the back and test pointed motherboard, detected in 9008 mode
*Tried QFIL with V30_Unbrick.zip, sahara error.
*Tried a bunch of other tools most of them were so old that they didn't even have the firehose for this model.
Please someone help.
seloka180 said:
use cracked miracle box
Click to expand...
Click to collapse
Can't thank you enough mate! Used it and miracle did happen. I even tried to use it before but after you said it, I tried hard this time. Searched here and there, then took some risk and started to do things like this way -
I had V30_UNBRICK.zip unzipped in a folder with firehose and xml files.
*Disable defender or any other antivirus. (Normally not recommended, but it's the first thing I do when doing these things, also I have an extra laptop where I do all these which doesn't have any private or necessary files, never had any problem though).
*Also, disable driver signature enforcement on Windows(https://windowsreport.com/driver-signature-enforcement-windows-10/)
1. I searched and found Miracle box Thunder v2.93 with loader (No box needed)
2. Select Qualcomm, then flashing and Write Flash.
3. Untick the auto button beside firehose.
4. Under "write flash"
see this image
i. Select firehose, this doesn't recognize the .elf file so renamed it to .mbn (finger was crossed) and it worked!
ii. There are six rawprogram?.xml and patch?.xml (Here, ? = 1, 2, 3....6), I only used rawprogram0.xml and
iii. patch0.xml
5. Got everything ready and then detached the phone from cable.
6. Pressed the start button right after entering into Testpoint EDL Mode. The process starts and failed after a while due to missing files. Then I matched which files were present corresponding to the lines in the xml file, after that deleted all the extra lines(i. e. file was not present in the V30_UNBRICK.zip) from rawprogram0.xml and saved the file (patch0.xml was untouched). I used Notepad++ for editing.
7. Again detached the phone, detached battery, reattached battery, pressed the start button right after I shorted the edl test points, even before the device was detected in the device manager, no delay.
8. The process was completed, files flashed. These files were flashed so that we can now flash proper kdz with download mode. Do not turn on the phone. Or else you'll get into bootloop.
9. Detached the battery, shorted power button for a while(skip if you don't understand), reattached the battery.
10. Pressed volume up and inserted USB cable. Not detected first time. Detached and reattached with pressing volume up button hard this time.
11. witnessed one of the happiest moment seeing it was detected as an LG device in device manager. Wasn't 100% sure yet.
12. Flashed chiperase(important) with patched LGUP in dev mode. And it was done.
13. I will upload the XML file, you can use it with the existing files inside V30_UNBRICK.zip.
the xml file here
Before doing all that I spent five horrific days searching for a solution and almost ordered a motherboard from Aliexpress with a price tag of $100. I tried to be as elaborative as possible so that whoever next encounter the issue don't have to go through what I experienced past few days. If you're reading this and having a problem understanding anything, read again, repeat 10 times, then repeat more 10 times(worked for me), still no solution? knock me here (also: [email protected]). I could help you(with v 30, g6) remotely if I have time, no charges, donate if you will and if you don't I'll still be happy to help. Keep flashing, peace.
---------- Post added at 05:36 AM ---------- Previous post was at 04:57 AM ----------
quickwshell said:
If you try this method, I nor anybody else is responsible for any further damage done to your phone.
Models Confirmed : V300L
We currently have firehose for V30.
Therefore, we can program UFS flash memory in 9008 mode.
It requires rawprogram?.xml(s) and patch?.xml(s) to program it.
It's easy to generate rawprogram?.xml(s) from kdz file, but generate patch?.xml(s) is not easy. (Unfortunately, I couldn't have time to generate patch?.xml(s)).
I have edited kdztools to generate rawprogram?.xml(s) easily (You can generate it by using "-r" argument. Currently, generate patch?.xml(s) is not supported. I'll add it soon).
I used patch?.xml(s) in post. it works well, but boot loop in the LG Logo.
However, it was possible to enter download mode.
------------------- GUIDE -------------------1. Download rawprogram?.xml patch?.xml with images from link. (It uses V300L30h000906.kdz)
2. Download firehose (prog_ufs_firehose_8998_lgev30.elf) from link.
<< Linux >>
3. Build qdl or download pre-built binary
4. Extract zip or tar.gz files 1, 2, 3 in any folder.
5. Run
Code:
$ ./qdl --storage ufs prog_ufs_firehose_8998_lgev30.elf rawprogram0.xml patch0.xml rawprogram1.xml patch1.xml rawprogram2.xml patch2.xml rawprogram3.xml patch3.xml rawprogram4.xml patch4.xml rawprogram5.xml patch5.xml rawprogram6.xml patch6.xml
in the terminal.
6. If LG logo shows, enter to the download mode.
<< Windows >>
3-6. You can program by QFIL similar as qdl.
7. Connect to any Windows PC with LGUP (must support Android Pie).
8. Flash kdz with ChipErase. (IMPORTANT)
9. If it boots successfully, your device has unbricked.
Click to expand...
Click to collapse
Thank you, Your post helped me to understand a lot of things. Without whome I'd be having an expensive brick which can't even be used to build anything.
This is the way I recovered. So posting it here for people might get help.
seloka180 said:
use cracked miracle box
Click to expand...
Click to collapse
Can't thank you enough mate! Used it and miracle did happen. I even tried to use it before but after you said it, I tried hard this time. Searched here and there, then took some risk and started to do things like this way -
I had V30_UNBRICK.zip unzipped in a folder with firehose and xml files.
*Disable defender or any other antivirus. (Normally not recommended, but it's the first thing I do when doing these things, also I have an extra laptop where I do all these which doesn't have any private or necessary files, but never had any problems).
*Also, disable driver signature enforcement on Windows(https://windowsreport.com/driver-sig...nt-windows-10/)
1. I searched and found Miracle box Thunder v2.93 with loader (No box needed)
2. Select Qualcomm, then flashing and Write Flash.
3. Untick the auto button beside firehose.
4. Under "write flash"
see this image
i. Select firehose, this doesn't recognize the .elf file so renamed it to .mbn (finger was crossed) and it worked!
ii. There are six rawprogram?.xml and patch?.xml (Here, ? = 1, 2, 3....6), I only used rawprogram0.xml and
iii. patch0.xml
5. Got everything ready and then detached the phone from cable.
6. Pressed the start button right after entering into Testpoint EDL Mode. The process starts and failed after a while due to missing files. Then I matched which files were present corresponding to the lines in the xml file, after that deleted all the extra lines(i. e. file was not present in the V30_UNBRICK.zip) from rawprogram0.xml and saved the file (patch0.xml was untouched). I used Notepad++ for editing.
7. Again detached the phone, detached battery, reattached battery, pressed the start button right after I shorted the edl test points, even before the device was detected in the device manager, no delay.
8. The process was completed, files flashed. These files were flashed so that we can now flash proper kdz with download mode.
9. Detached the battery, shorted power button for a while(skip if you don't understand), reattached the battery.
10. Pressed volume up and inserted USB cable. Not detected first time. Detached and reattached with pressing volume button hard this time.
11. witnessed one of the happiest moment seeing it was detected as an LG device in device manager. Wasn't 100% sure yet.
12. Flashed chiperase(important) with patched LGUP in dev mode. And it was done.
13. I will upload the XML file, you can use it with the existing files inside V30_UNBRICK.zip.
the xml file here
Before doing all that I spent five horrific days searching for a solution and almost ordered a motherboard from Aliexpress with a price tag of $100. I tried to be as elaborative as possible so that whoever next encounter the issue don't have to go through what I experienced past few days. If you're reading this and having a problem understanding anything, read again, repeat 10 times, then repeat more 10 times(worked for me). Keep flashing, peace.
Good day,
Bricked my G710VM a few weeks ago and trying to get back. I know the process to get back to stock but a lot of fails extracting etc. To make it easy, lets just say I deleted all my partitions one by one and loaded new ones from the KDZ extract getting me to this point
- Latest KDZ file from lgfirmwares.com will extract with LG Firmware Extract
- DZ Extract with LG Firmware Extract WILL NOT produce good .bin files
- Hovatech extract program seems to produce DZ files with data
- LGUP will not recognize phone, even using UPPERCUT
- NO DL Mode, only EDL
- Can't find XML Files to DL online. Plan to make my own but even if I succeed, no LGUP access.
Any help is greatly appreciated. My mom has the same phone on stock I could use to pull whatever I need assuming it connects to LGUP. I have scoured this site and most that use english, I find others with the same issues but only a few seem to resolve
i have lg g710vm only this files can use, then crossflash to verizon kdz. i lost imei but i can keep using my phone only whit kdz verizo..
you need add apn for 4g....
Pixel 6 Pro runs on a Google Tensor CPU which is in fact an Exynos CPU
This means that there is Exynos boot recovery in the CPU
You can repair the bootloader using the Samsung Exynos Tool
Nothing could be flashed from the mode, however it loads into the RAM the fastboot mode, from here reflash the bootloader image using fastboot
Unpack BL1, BL2 AP boot, ELR_EL3, BL etc from stock image (use your device and version)
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Set this up using windows 7 32 bit
use this config not the one he has included, but use his tutorial
DNW_STORE exynos down 200 20 bl1.bin
DNW_STORE exynos down 2000 20 bl2.bin
DNW_STORE exynos down 200 20 elr_el3.bin
DNW_STORE exynos down 200 20 lastly.bin
DNW_WAIT
;PIXEL ROM RECOVERY
DNW_STORE exynos down 20000 20 bl.bin
NOTE: this is EDL mode!!
If not working or you need help let me know
@pierre383
Have you recovered any Pixel 6/6 Pro unit in real life yet using this procedure? If so, then kindly post a more elaborate guide so that we can cover it for the portal.
===
AFAIK, a hard-bricked Google Silicon device (e.g. the Pixel 6/6 Pro) by default exposes a serial interface with vendor ID 18D1 (aka Google) and device ID 4F00.
SkandaH said:
@pierre383
Have you recovered any Pixel 6/6 Pro unit in real life yet using this procedure? If so, then kindly post a more elaborate guide so that we can cover it for the portal.
===
AFAIK, a hard-bricked Google Silicon device (e.g. the Pixel 6/6 Pro) by default exposes a serial interface with vendor ID 18D1 (aka Google) and device ID 4F00.
Click to expand...
Click to collapse
Hi sorry am making this fast, when you have it as a unverified device in device managment, install Exynos mode USB driver (USE 32BIT operationing system for the one in the post I linked), prepare the boot + cfg (just take mine), hold the power button and select in the software it should begin, if you have problems uncomment the DNW_WAIT or try another USB cable, the motherboard in your computer is the difference
if your computer say the driver is not compatible on 32bit computer, pick install anyway, install manually a driver for the selected device from a list of installed drivers on the computer (in device manager)
if you need more help or can help me make it better pls let me know
Linux will work also with different tool, but the DNW_WAIT can't be replicated :? so got stuck on pixel rom recovery line, fastboot did not load on the phone
after dnw_wait if phone is not recognized hold power button while DNW_WAIT sequence maybe
Unpack BL1, BL2 AP boot, ELR_EL3, BL etc from stock image (use your device and version)
Click to expand...
Click to collapse
it's amazing ! but how to unpack these bin files? stock image only has a bootloader.img
or could i use dd to copy it that from my phone filesystem in terminal ?
split bootloader as explained, it is inside bootloader.img if you need more guidence let me know and yes dd can copy bootloader.img however this assume that you phone can't turn on so you can't copy it from dd terminal in the phone because how can you do that in brick state... don't try and prepare for brick, rollback protection will assure that you can't boot a old bootloader from long time ago you prepared incase of brick you need new BL
iCassius said:
it's amazing ! but how to unpack these bin files? stock image only has a bootloader.img
or could i use dd to copy it that from my phone filesystem in terminal ?
Click to expand...
Click to collapse
oh I see it ! it means I need split bootloader.img to 4 bin files .
so it we can get 64bit drivers , it means newly computer and windows is useable?
iCassius said:
oh I see it ! it means I need split bootloader.img to 4 bin files .
so it we can get 64bit drivers , it means newly computer and windows is useable?
Click to expand...
Click to collapse
I recommend using a virtual machine with 32bit Windows 7 or XP or Vista, working with making the Linux work, Install Windows 32 bit on your laptop (you can use a 2nd partition maybe)
It is about fixing the phone that cost 600€, working 1 hour to make Windows 32bit work in 1 or another way is not a big deal
However there are 64 bit drivers around but they are not on XDA, so yes, theoretically it can work with modern 64bit windows
Could you please explain how to split the bootloader image or attach the files?
pierre383 said:
Linux will work also with different tool, but the DNW_WAIT can't be replicated :? so got stuck on pixel rom recovery line, fastboot did not load on the phone
Click to expand...
Click to collapse
Hi @pierre383 thanks for your guide. I have a bricked Pixel 6. But it only stays visible in Pixel ROM Recovery Mode for about 10s.
What linux tool is available? and where?
Thanks
speedpat said:
Hi @pierre383 thanks for your guide. I have a bricked Pixel 6. But it only stays visible in Pixel ROM Recovery Mode for about 10s.
What linux tool is available? and where?
Thanks
Click to expand...
Click to collapse
GitHub - frederic/exynos-usbdl: Unsigned code loader for Exynos BootROM
Unsigned code loader for Exynos BootROM. Contribute to frederic/exynos-usbdl development by creating an account on GitHub.
github.com
Look into building this, or dm me for discord or telegram and I can gladly guide you through building and using it
z3r0skull said:
Could you please explain how to split the bootloader image or attach the files?
Click to expand...
Click to collapse
I could post in the weekend
Hi @pierre383. You might want to change this thread type from "Question" to "How to guide". Just either edit the first post and you can then change the thread type there, or click the 3-dot menu in the upper right corner above the first post and choose "Edit thread" and you can change it there instead - either way.
pierre383 said:
I could post in the weekend
Click to expand...
Click to collapse
Thanks that would be nice.
Also my pixel is not recognized by the "multidownloader" tool mentioned in the other guide. Did you install any specific driver for it to work?
Thank you.
Hi! Any updates on where to get those files?
Also another thing: the driver is not picked up be the phone, it is still stays as USB Composite Device.
z3r0skull said:
Could you please explain how to split the bootloader image or attach the files?
Click to expand...
Click to collapse
@z3r0skull
you can extract the file with imjtool from the bootloader.img
on Linux that would be:
Code:
imjtool.ELF64 bootloader-oriole-slider-1.2-8085990.img extract
pierre383 said:
Pixel 6 Pro runs on a Google Tensor CPU which is in fact an Exynos CPU
This means that there is Exynos boot recovery in the CPU
You can repair the bootloader using the Samsung Exynos Tool
Nothing could be flashed from the mode, however it loads into the RAM the fastboot mode, from here reflash the bootloader image using fastboot
Unpack BL1, BL2 AP boot, ELR_EL3, BL etc from stock image (use your device and version)
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Set this up using windows 7 32 bit
use this config not the one he has included, but use his tutorial
DNW_STORE exynos down 200 20 bl1.bin
DNW_STORE exynos down 2000 20 bl2.bin
DNW_STORE exynos down 200 20 elr_el3.bin
DNW_STORE exynos down 200 20 lastly.bin
DNW_WAIT
;PIXEL ROM RECOVERY
DNW_STORE exynos down 20000 20 bl.bin
NOTE: this is EDL mode!!
If not working or you need help let me know
Click to expand...
Click to collapse
I extracted the bootloader but I don't see ELR_EL3, LASTLY or BL. Below is a list of the files that were extracted.
abl
bl1
bl2
bl31
gsa
ldfw
partition_0
partition_1
partition_2
partition_3
pbl
tzsw
ufs
ufsfwupdate
jac0b said:
I extracted the bootloader but I don't see ELR_EL3, LASTLY or BL. Below is a list of the files that were extracted.
abl
bl1
bl2
bl31
gsa
ldfw
partition_0
partition_1
partition_2
partition_3
pbl
tzsw
ufs
ufsfwupdate
Click to expand...
Click to collapse
Lastly is BL1 again, EL3 and BL31 is the same, BL is PBL (Short for primary BL)
I can't make the flashing work with the multidownloader
[COM3]Write thread Start##################
[COM3]Write Fail
[COM3]Write thread Exit##################
I'm using a Win7 32bit VM in VirtualBox
Did anyone actually recover a Pixel 6/pro device using this method?? I'm in the same position right now a serial interface with vendor ID bla bla.... cant go into bootloader nothing just dead device.