Related
Tried searching the forums on this topic but could not find anything that could resolve my problem
attempting to install a ROM on my phone for the 1st time.
I am using i9082 on android 4.2.2
my OS is ubuntu 12.04 hence used Heimdall 1.4
Tried to Flash ClockworkMod recovery using Heimdall 1.4
i am trying to flash this by using baffin.pit file (otherwise the options dont show up) and into the partition named "RECOVERY" but i always get an error "setting up interface failed!"
the device is detected on heimdall and the phone is on download mode but yet it does not go further
could someone help me out please
also since odin has been suggested on many forums, tried to run it with wine but it does not detect the phone(no com port in yellow)
yogneo said:
Tried searching the forums on this topic but could not find anything that could resolve my problem
attempting to install a ROM on my phone for the 1st time.
I am using i9082 on android 4.2.2
my OS is ubuntu 12.04 hence used Heimdall 1.4
Tried to Flash ClockworkMod recovery using Heimdall 1.4
i am trying to flash this by using baffin.pit file (otherwise the options dont show up) and into the partition named "RECOVERY" but i always get an error "setting up interface failed!"
the device is detected on heimdall and the phone is on download mode but yet it does not go further
could someone help me out please
also since odin has been suggested on many forums, tried to run it with wine but it does not detect the phone(no com port in yellow)
Click to expand...
Click to collapse
Hope you are using recovery.img(*.img) huh?
What you get when you execute heimdall detect command in Terminal.
And definitely you cant install recovery without PIT, so baffin.pit is essential. It looads the Partition Information Table.
Once the PIT has been loaded, the "Partition (Files)" field will be clickable. Click "Add", now the "Partition Details" field becomes clickable. Under "Partition Name", select "KERNEL". Click "Browse" on the "File" field directly underneath.
And i guess this is what you had done till now.
See whether the img or tar file which u used is correct and that is for Galaxy Grand Duos.
And using wine wont help.. may be because driver identification may be a mess in emulators. also try installing Kies in Wine and Odin.
If u have access to Windows, Odin, that would be the best choice.
DMJoh said:
Hope you are using recovery.img(*.img) huh?
What you get when you execute heimdall detect command in Terminal.
And definitely you cant install recovery without PIT, so baffin.pit is essential. It looads the Partition Information Table.
Once the PIT has been loaded, the "Partition (Files)" field will be clickable. Click "Add", now the "Partition Details" field becomes clickable. Under "Partition Name", select "KERNEL". Click "Browse" on the "File" field directly underneath.
And i guess this is what you had done till now.
See whether the img or tar file which u used is correct and that is for Galaxy Grand Duos.
And using wine wont help.. may be because driver identification may be a mess in emulators. also try installing Kies in Wine and Odin.
If u have access to Windows, Odin, that would be the best choice.
Click to expand...
Click to collapse
- the file has been extracted and i am using recovery.img
- the command displays "device detected"
- I am using the baffin.pit file of the internet for this particular device, will that be a problem? if so then how do i get this file.
- i've tried under kernal and it displays the same error
i do not have any access to a windows computer, is there anyother way i could load the recovery?
cheers
yogneo said:
- the file has been extracted and i am using recovery.img
- the command displays "device detected"
- I am using the baffin.pit file of the internet for this particular device, will that be a problem? if so then how do i get this file.
- i've tried under kernal and it displays the same error
i do not have any access to a windows computer, is there anyother way i could load the recovery?
cheers
Click to expand...
Click to collapse
Baffin.pit wont be a problem.
Make sure you are doing the correct procedure. I am not that good in the process, so you should research a bit in this.
You can Get pit from here. But I dont think that its the problem of the pit u use.
By the way from where you got the IMG file?
got it from the thread below
http://forum.xda-developers.com/showthread.php?t=2563557
yogneo said:
got it from the thread below
http://forum.xda-developers.com/showthread.php?t=2563557
Click to expand...
Click to collapse
Are you using the frontend Heimdall or by executing commands in Terminal.
If you are using terminal try the frontend app too, i guess u are well aware of this.
And its too hard for me to get my device detected by Ubuntu, and so i prefered Odin later.
As you said it wont go further can you post the log messages in Heimdall window
Overview
Now, I have seen many people facing problems like lost IMEI or NVRAM warning in their wifi list! Well, these are normal errors when you often flash a custom and wiped system or update using SP Flash Tools. So fix isn't that hard! But still, many people suffer from this! Now, this guide is applicable for every device(MTK) but BPLGU modem file will vary from device to device. I have specially made this guide for Lenovo Vibe K4 Note users!:laugh:
WARNING !!! IMEI CHANGING IS ILLEGAL. THIS GUIDE ONLY HELPS YOU HOW TO RESTORE ORIGINAL IMEI OF YOUR DEVICE! I DONT TAKE ANY RESPONSIBILITY OF ANY ILLEGAL ACTION TAKEN AGAIN YOU! BE AWARE IF YOU ARE NOT SURE FOR WHAT IMEI IS USED FOR ALSO I DONT TAKE ANY RESPONSIBILITY OF DEAD DEVICES/ BRICKS! PLEASE DO SOME RESEARCH IF YOU ARE NOT AWARE OF ANYTHING. HOWEVER, THIS GUIDE WILL HELP YOU DEAL WITH THINGS, IF YOU READ CAREFULLY AND FOLLOW INSTRUCTIONS THEN YOU DONT NEED TO WORRY ABOUT ANYTHING!
Click to expand...
Click to collapse
So lets fix it up !
Required stuffs !
Windows PC (7/8/8.1/10)
Usb Cable
Few tools
Drivers
Your device, ofc !
Download Section !
1. Scatter files !
2. MauiMETA
3. Temoprary IMEI fix.zip
Now before we start doing anything make sure you download everything from the download section. Also, make sure your device is having TWRP installed.
Process !
Now most of you must have thought hey Max where is NVRAM fix? There was nothing about NVRAM in title Well chill down I will target NVRAM NOW !! So let us begin! Now as you have downloaded entire scatter files so NVRAM needs entire scatter files. "Woosh! Thank god it was useful somehow" most of you must have thought Hehehe Well one more thing if you are using permanent NVRAM fix then use it before you flash IMEI or else you lose it again if you fix NVRAM after IMEI. However, a temporary fix can be flashed later on.
* Now navigate to the firmware folder
* Look for scatter file open it in notepad or notepad ++
* There look for this line, "partition_name: NVRAM"
* There you will also notice, "s_download: false"
* Just change it to, "s_download: true"
* Save and exit!
* Open Sp flash tools and load scatter file(Remember a thing, you will have to use an older version of SP Flash Tools)
* You will see checkbox of NVRAM just choose it and keep rest options unchecked!
* Flash into your device and all set!
NVRAM IS FIXED PERMANENTLY :good:
But now for those who are lazy doing this, there is a temporary zip file which you can flash and NVRAM problem will be fixed for a limited time to do so just go to download section and download temporary fix zip file and flash it into TWRP (Yes, that's why we needed TWRP):angel:
Now before we start doing anything make sure you download everything from the download section. Also, make sure your device is having TWRP installed. (YES AGAIN MAKE SURE YOU HAVE EVERYTHING)
• After that, run Maui META 3G
• Use USB COM
• From Options menu, select “Connect smartphone in meta mode”.
• Press Reconnect and connect the phone in the switched off state.
• Wait for a minute. Your Device automatically boots into meta mode. The blinking led will become yellow and you can see "connected with target"
• Now from the drop-down menu select “IMEI download”. Click ok till you see IMEI download box.
• Click Change NVRAM Database FIle and browse to “MT6753 DB” folder and select the following file.
File\MT6753\
BPLGUInfoCustomAppSrcP_MT6753_S00_K5_ROW_LWG_V56_ 1_lwg_n (BPLGU modem file for mt6753, do a double check as the name might change with firmware versions).
[Well I have not extracted this file yet from stock ROM scatter files. However, I have given you the download link of entire stock ROM look the file there itself !]
• Click ok on any warning.
• Leave IMEI Increasemnt 0.
• Write first 14 digits of your IMEI in IMEI box and last 15th digits will go in checksum(should be entered automatically). Eg:- if IMEI is 123456789123456, write 12345678912345 in IMEI and 6 in the checksum. Do same for Sim_2
[Now most of you must be wondering where is my IMEI. I don't remember it and also it's not there in the list. Don't worry pull your back cover and you will see IMEI sticker there just type the same IMEI]
• Press Download To Flash. You will see Download IMEI flash successfully. Now close the box (or alt+f4 or close from task manager if stuck).
• Restart the phone
• Open Dialer and type *#06# and you will get your valid IMEI number.
* Well if you saw the same IMEI then you are done !!! :good:
Credits : Yaas !! Why not ?
meprakash_pyc
Sahil_Sonar
KM (One who made NVRAM fix for lazy people :silly
If this post was helpful to you just hit :good: below my posts !
Drivers ?
Hey Maxx where are our drivers? Well, come on relax as you have downloaded scatter files all the drivers are there you can additionally get extra drivers from my https://forum.xda-developers.com/k4-note/how-to/bootloader-unlock-t3846902 another post [/url] Yes the same one! TWRP one! I have added ADB Drivers there follow the same process also there is a manual how to install drivers same is applicable for these drivers!
after loading that modified scatter file, it says that it should not be treu value
yes bro, after modifying scatter file, flash tool wont allow to load it. im hoping this will fix my wifi issue.
royskeyz said:
yes bro, after modifying scatter file, flash tool wont allow to load it. im hoping this will fix my wifi issue.
Click to expand...
Click to collapse
Actually, I have tested this thing on my own device... No idea what's wrong with you. You can also try notepad c++
jaskoooo said:
after loading that modified scatter file, it says that it should not be treu value
Click to expand...
Click to collapse
royskeyz said:
yes bro, after modifying scatter file, flash tool wont allow to load it. im hoping this will fix my wifi issue.
Click to expand...
Click to collapse
Try older version of SPFT.
I've downloaded your drivers and tried many other drivers,None worked,Please help me.With the drivers i have im able to Flash stock through SP,Device gets detected too,But i dont know y its not working for this tool or SN writer..This is the error im getting..Communication through either RS232 or IPC error,Please reconnect..
JaSomTy said:
Try older version of SPFT.
Click to expand...
Click to collapse
Exactly!
where is nvrm file 's ?
where is nvrm file 's ?
Can anyone tell which version of sp tool worked for them? that would really really be helpful
Edit: Files are no longer available on google drive
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.
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
link is restricted
Bro. Share file pls on your googledrive. We cantdownload it
Flar4eg said:
Bro. Share file pls on your googledrive. We cantdownload it
Click to expand...
Click to collapse
Excuse me, is that I uploaded the files to my google drive cloud and I detect a dll, or part of the flashtool as a virus, now I upload it again and put the link
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
multiuploader error: WinDNWApi.dll file could not be found.
Skyfall191299 said:
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Click to expand...
Click to collapse
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Skyfall191299 said:
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
Click to expand...
Click to collapse
getting error that el3mon_dram not found. can you help me?
Hello someone has the files ? The download link is inactive
The download link is inactive, please active or reupload please.
Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
good jod
im follwed to this instruction but all links not woriking
pla give me ur telegram or whtas app
and upload files to the new link plz
eldon301 said:
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Click to expand...
Click to collapse
how to create with hex bro ?
links not woriking
link isn't working please fix
akbarshoxdedamirzayev said:
how to create with hex bro ?
Click to expand...
Click to collapse
Find the exact firmware that’s currently in the device, extract sboot from the firmware. You need to find correct location of bl1 bl2 el3 and others, names correspond to which is cut. You need 5 files from sboot. Am stuck on the forth file failing and I still don’t understand how to find them. What I did was follow others with exactly the same problem to see and understand how they got there’s and then tried it on my sboot. I am failing on part4 don’t even know how to make a cfg but from what I understand e for exynos and the number after so mine is e7885. Still not sure like I said
http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip/file download link
Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
Can you check the addresses and lenghts of the partitions cut out of sboot?
I think you've made a mistake.
Can give me the precise partition details?
Are you 100% positive that this is valid at least for most devices of the same chipset?
I'd like to try to make an automated script or a tool of some sort.
Also when I was dividing my A515F U5 sboot I've spotted some long breaks in data which I assumed were empty blocks at the end of partitions.
What confused me about it is that I didn't find those where you said partitions are ending.
Can you demonstrate graphically your partitions in a linear projection?
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
eldon301 said:
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
Click to expand...
Click to collapse
I'd like to help
NonStickAtom785 said:
I'd like to help
Click to expand...
Click to collapse
Hello my friend I am try to get life back into a A750G, it’s completely hard bricked showing exynos usb in device manager. Can i direct message you or should I keep it in the forums. I was falling on part 4 off the files needed to create, I didn’t even know if my cfg file was correct but I tried my best at understanding the creation of the files. Plz help my brothers
So, this post is about the error some people (like me) may encounter after pressing the download button in SP flash tool when following the Hard brick guide
Im going to show you all how to fix it
so the problem resides in step 12: "2ND RUN THIS.bat"
so in the bypass folder, there is a file called mt6785_payload.bin, but redmi note 9 processor is mt6768
so you need to delete mt6785_payload.bin, go into the payloads folder thats in the bypass folder, copy the mt6768_payload.bin file and paste it in the root of the bypass folder
now do everything again starting from step 10 and you should be good to go
Instead of creating a new thread, maybe contact the OP of that guide and recommend he incorporate your additions?