Hello everyone, I bought an LG L70 Dual D325F which was soft-bricked hoping it as to be easily fixed via flashing the stock firmware, but to my great surprise, I was unable to access the download mode, I was facing the "DemiGod Crash Handler : DBI Err Fatal!"
{
"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"
}
Then I tried this tutorial, but I after following the thread, the device switch to Qualcomm HS-USB QDLoader 9008, thus I started searching a solution, then I found out about this method, which involved the use of an SD Card, thus it did worked out, and I was able to boot to download mode in order to flash the firmware, but the firmware flashing was getting stuck and then reset while displaying 'ASSERT' in Red at 7%, sometimes at 15% and the maximum I did reach was 33%, before restarting again.
Then after spending hours on google, I found out that the it is normal and that I should keep forcing until 100%, but after my attempt to 33%, the process wouldn't past 7%, thus I googled for another method then I came across a method involving BoardDiag 3.99, thus when I tried it out, but during the test, it EMMC test fails and output the following:
Note: I used the other driver, this was just to show the error which was being output.
Despite that, I did continue with the method and flash the imgs. Then I decided to look inside the files and found out the partition.txt was incorrect, thus I did calculate and created my own using the files from my stock extracted firmware. But still it didn't worked out, thus after I googled, I came across a tutorial which was meant for LG G3 unbrick using BoardDiag, and it the tutorial, the guy mentioned that use the option erase and then switch it back to Read/Write, and it should fix the error, but it didn't worked out. and the EMMC partition was completely wiped. then check I checked the rawprogram xml in BoardDiag, It looked like it was incorrect, but I wasn't able to edit it properly, so I gave up on this one.
Then the next day, I googled and came across a tutorial from XDA that shows how to fix an LG L7 P715, so I started following the tutorial as from Step 4, but I was unable to continue as the application was search for the Sahara XML, I wasn't able to get my hands on. After some research I found out the provided files wasn't compatible with my device, thus I finally got my hands on some of the files.
1. MPRG8x10.hex (It is the eMMC programmer file to help download the bootloader into eMMC, and I guess it can be used with all Snapdragon 200 MSM8x10 processor. And I've already got this file somehow).
2. 8x10_msimage.mbn (It is the bootloader image file and specific to the phone. I wasn't able to get the file, because I wasn't able to determine the proper bootloader file for the device from the stock firmware.)
3. Raw XML and Patch XML files (These XML files contain the partition details of phone. And I don't have these two. And I was unable to even a edit the files properly as I wasn't able to exactly understand what was going on, so I gave up on this one.).
Then the next day, I tried again using the SD Card method, but once the SD Card is inserted, the device shows the Demi-God Crash error. Thus when I hooked it up to my computer, I saw the EMMC as a removable partition but I was unable to format it, thus I tried writing the partition table (PrimaryGPT) to the device, but no success. Then I download a full dump for the D325 and wrote it to the EMMC, but still fails to boot as the EMMC is clean once I unplug it and plug it again. Thus when I hooked up the SD Card through a card reader to my device, it shows that the SD Card was partitioned as a regular emmc for a phone to boot, I did try to to backup the partition table and then restore it to the EMMC, but still in vain. Then I tried to write the files manually using linux to partitions manually, including the system partition, which I did merge the different bin files to one img and then flash it, I took about 10min to fully write it. But still it didn't boot. Well I'm stuck here (am currently trying to write the full dump to the SD card and try to boot of it, if it does boot). I hope that someone will be able to help me out to fix this issue. Thanks in Advance!
Note: The reason for which I'm posting this thread is because I'm stuck.
Related
Hi, I was wondering if anyone can help me.
My tablet is unable to mount my /efs directory, or whatever. And while I don't know if they are directly connected,
things like my lock screen, holding my power button to get options like Flight Mode, Data Network, Restart, Etc., is gone. And I have tried screen lock to work, it doesn't. Holding my power button shuts my tablet down (in the same amount of
time that holding it would normally bring up the options screen, as well). I also loose completely my 3g, no matter wish successfully installed rom I run. I am not new to flashing rom at all and navigate trough all kind of step regarding specifics to rom by heart. All I can remember was to try the latest Android 4.1.1 - CyanogenMod 10 Preview and failed to load it, I was stuck in the boot animation for half an hour. So I decide to go back to the new stuck 4.0.4 from my provider. That is where I found the problem. Since, I have try 4.0.4 stuck, 4.04 rooted. The problem occur the same way in every rom and everything else was juste fine. I try the 3.1 stuck and 3.2 stuck and the message E: failed to mount /efs appear when rebooting from odin install.Never been able to load any version of the latest 4.1.1 from pershot. I have found a thread about the same issues from another device http://forum.xda-developers.com/showthread.php?t=1766748. I pass the entire day reading the web for solution, but no cigars so far.
I have the a Telus samsung galaxy tab 10.1 3g.
Thanks in advance if you have any idea how to resolve the /efs mounting problem.
I will added these picture to show that I have lost all important information that is apparently store in some file inside this /efs folder. Apparently this folder as been corrupt when flashing the CyanogenMod 10 Preview especially made for my tablet. So my new question would be to ask.
Do anyone know how to restore this folder even if I have no backup of it?
{
"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"
}
on off on off
try to copy the content of the efs folder with any root browser. it will have files and folders like in the screenshot atached.
Solved.
i had exactly the same problem. Was working on it for the last two days (ofcourse i am a simpleton and rookie )
But yes at last the phone is fixed and working fine with all the parameters.
So dont worry dear. Try to follow these steps : -
1. flash a rom using odin or heimdall - either stock or Cyanogenmod. You can check the repartition if using with the pit file.
2. Root your phone if not already rooted
3. Install busybox
4. Install kTool.apk (Its a small and wonderful apk. Freely available)
5. Install any file manager that supports root browsing
6. Make a backup of your efs with the help of kTool.apk (Its simple)
7. Decompress your earlier backup and copy all the files in the root efs folder with the root explorer
8. Now rename the one that you decompressed the files from as efs.img and copy it into the internal sdcard root
9. Now retore the egs.img using the kTool.apk
This will solve the problem i guess.
Good luck
8.
No file in /efs folder, and no backup
Thanks a lot for the answer guys, but unfortunately there is nothing inside my /efs folder. It's completely empty and therefore I can't copy it, move it backup it,or anything. I also have no backup of this folder. As I understand some file in this folder contain the super important information of my own system like IEME, Serial, etc... So my concern is more like is there is a way to restore this folder even if it doesn't exist. I think the answer is no and the only solution for me is to send it back to Samsung with the stuck roms from my provider and hope for them to not deny the repair so I won't have to pay. I wonder if there is other thing to do but I am pretty sure not. If someone know something let me know. I have already contact Samsung and tell them that my 3g is broken and some strange behavior occur during OTA update. They are going to send me something for me to send the tablet for reparation. Til then I really want to know if there is something I don't understand and if there is still hope. Anyway thanks in advance for anyone who know better then me.
This is EXACTLY what's going on with my tablet, and yes, there's nothing to copy. What do we do?
I originally edited my old post with this, but I wanted to be sure the OP saw it.
I finally fixed mine. See my thread at http://forum.xda-developers.com/showthread.php?t=1876260
I hope it helps
I have a Landvo L200G 4G MTK MT6582 phone from China. The phone only has 4GB of storage space.
I wanted to repartition it so the primary partition would have 3GB instead of the less than 1GB it currently has.
I followed the MTK repartitioning video on YouTube exactly. Even though the preloader flashed successfully, the new EBR files did not work. The phone would only boot to the logo screen and hang. When I flashed the preloader using the original EBR files, the phone will boot up normally.
I tried 3 different EBR files from xdadevelopers website, specifically for the MTK 6582 4GB. They all flashed OK but left the phone in a boot to logo screen only condition.
The phone is currently back to it's original condition. Can anyone help me with my problem regarding the repartitioning of the primary partition size? Thank you.
The partitions size was changed. Problem in boot. There are two boot screens. Boot of the kernel and boot of the Android. Which one of this screens is last? If first screen, than the kernel can't find ramdisk. This is strange behavior. If second, than init.rc can not mount file systems, run daemons, because partitions were changed. In this case you must compile Android form source with correct values of partitions size. Or maybe there is an easier way.
AlexanderBabansky said:
The partitions size was changed. Problem in boot. There are two boot screens. Boot of the kernel and boot of the Android. Which one of this screens is last? If first screen, than the kernel can't find ramdisk. This is strange behavior. If second, than init.rc can not mount file systems, run daemons, because partitions were changed. In this case you must compile Android form source with correct values of partitions size. Or maybe there is an easier way.
Click to expand...
Click to collapse
The phone only boots with the Landvo animation screen. Then the home screen appears.
When I tried the other EBR files, the phone booted with the Landvo logo on screen with no animation and remained like that.
This means that Android can not boot. When ROM was compiled from Android source, there is file BoardConfig.mk in source. It contain device specific information like CPU, and partitions. ROM was compiled for standart partition scheme. It can not find partitions in old places. I think problem in this.
This is example of BoardConfig from LG Mako.
{
"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"
}
AlexanderBabansky said:
This means that Android can not boot. When ROM was compiled from Android source, there is file BoardConfig.mk in source. It contain device specific information like CPU, and partitions. ROM was compiled for standart partition scheme. It can not find partitions in old places. I think problem in this.
This is example of BoardConfig from LG Mako.
Click to expand...
Click to collapse
I assumed that using the Flash Tools program to change the partition size would modify any other files required for boot, such as BoardConfig.mk
The instructional video by xda-developers for changing partition sizes I watched was specifically for the MTK 6852, which is the type of handset I have. I used the same instructions to change the partition on a L200 phone that worked OK.
Do I need to make some changes to the BoardConfig.mk file to get the partition changes to work?
Can you give link to instructional video?
AlexanderBabansky said:
Can you give link to instructional video?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=rDf6SpuOuz4
I finally got this fixed (sort of)
I ended up using EBR Tweak to allocate 3Gb of space.
I used MTK Droid Tools to backup and create scatter file. From that I tool the generated EBR files and copied them to EBR Tweak folder and ran the application, selecting the 3Gb option.
I copied the 2 new EBR files generated to the Files To Flash folder and used SP Flashtools to flash the phone.
The storage partition space was changed. However, there is a notification now saying Damaged Phone Storage - Try formatting the SD card.
I backed up the SD card and chose to format. The phone doesn't proceed to format the card and all data on it is intact.
In summary; phone storage is fixed but have that error constantly now.
Hi, I am trying to root this phone using the guide here: bbs.elephone.hk/thread-9919-1-1.html#.WGr04lzUHIU
However in Windows 10, nothing happens when I hit the download button, and in Linux this error happens when using the files I got from the guide:
{
"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"
}
this is the same PC, with Ubuntu and Windows 10 dual boot
I have tried the fastboot method, but I can't get my bootloader to unlock, the vol up button simply doesn't register on the phone.
So is there any fix? Or am missing something?
Problem solved! Windows 10 doesn't like the drivers provided. However Windows 7 does, so I advise that you keep your Windows 7 install somewhere
Follow this it will explain what you need to do. I had same issue with Windows 10 but rooted my P9000 no problem. I used FlashTools - all the info you need here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
I gave up following tutorials on elephone.hk forum & just followed tutorials from here, but whatever your personal preference - hope it helps ;0)
Need my elephone back
Not sure if this is best placed here???
So....tried to flash my Elephone P9000 using the SmartPhone Flash Tool and all the steps provided tutorial at:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Using Win10 so it took me a while to disable the driver signature enforcement option to get the drivers installed. Got that done and all..so far so good.
Download all the files as the tutorial says...clicked download and connected the phone which was powered off. Up pops a messages "PMT changed for ROM; it must be downloaded."
Google search for this and came across some pages that informed me to click on the 'Format' section in the Flash Tool
Did this and then went back into 'Download' and hey presto, the flash worked and I got the big green tick.
Lovely stuff...until I tried to power on my phone....dead in the water. Power+Volume Up does nothing, power on its own does nothing. I've downloaded loads of instances of the Flash Tool, tried the elephone stock ROM scatter file, recovery image files etc and still nothing. Read loads of similar pages where it's happened to others but just wont work for me!!!!
Can anyone help?
jfk247 said:
Not sure if this is best placed here???
So....tried to flash my Elephone P9000 using the SmartPhone Flash Tool and all the steps provided tutorial at:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Using Win10 so it took me a while to disable the driver signature enforcement option to get the drivers installed. Got that done and all..so far so good.
Download all the files as the tutorial says...clicked download and connected the phone which was powered off. Up pops a messages "PMT changed for ROM; it must be downloaded."
Google search for this and came across some pages that informed me to click on the 'Format' section in the Flash Tool
Did this and then went back into 'Download' and hey presto, the flash worked and I got the big green tick.
Lovely stuff...until I tried to power on my phone....dead in the water. Power+Volume Up does nothing, power on its own does nothing. I've downloaded loads of instances of the Flash Tool, tried the elephone stock ROM scatter file, recovery image files etc and still nothing. Read loads of similar pages where it's happened to others but just wont work for me!!!!
Can anyone help?
Click to expand...
Click to collapse
this usually happends when your flashing with old preloader... try installing CM13 with updated preloader, it should work.
Thanks Ruben, I managed to get the green tick in the sm flash tools using the 'Elephone P9000 Preloader_Lk_Boot_Recovery update' scatter text file.
Phone still wont power on at all and i can't access the sd card to copy across any ROMS so I'm back to square 1 by the looks of it. I'll keep pluggin away at it.
My fellows and friends,
One of these days, I received an update from LineageOS and when installing it from OTA ( using TWRP ), the first lines ( about 10 to 15 ) from the istallation sequence activities were all red, showing that something went wrong. Immediately I removed the batery to stop the process and installed the first version of the custom rom, using the TWRP. It worked fine and I received some notifications about the new revisions of the rom. I skipped the one that caused problems and accepetd the download the one on the Nov, 17, 2018 of the rom, and had installed. It appeared to me that everything was ok but, one day I turned the phone off during thje night. The next morning, I tryed to boot the phone without success. It started an infinite loop situation..... So, I tryed to repeat the same procedure to install the very first version of the rom using TWRP at the recovery mode. When I was using the TWRP to perform the advanced wipe, the dalvik cache, data and system could not be wiped. The answer about the problem was shown as : failed to mount /efes ( inavlid argument ).
I got the information that, in cases like that, the stock rom should be installed. I downloaded it from www.stockrom.net and had it istalled with the use of Odin. Unfortunately, the boot loop was there again.
What was worse now was that no TWRP was installed and Odin could not recognize the phone, although I had installed the newest set of drivers from Samsung, applicable to any devices from them.
Please I need your help to see if there is a possible solution to solve this case. Phone Model: GT-i9300 SSN -I9300GSMH - in Brazil
The message I got from the phone: E: failed to mount /efes ( inavlid argument )
{
"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"
}
I thank you in advance any help from you guys,
Gilberto Leite
Flashing a stock ROM will always replace TWRP with the stock recovery.
Are you trying to flash the latest stock ROM?
Do you have a backup of the EFS directory? It's an important directory as that is where a lot of information, including the IMEI is stored.
Hi Audit 13, thnaks for replying.
No I don't have the back up for the folder you mentioned. I was trying to install the last stock rom downloaded from www.stockrom.net, which I suppose was the last one. The worst part is that to computer does not recognize the phone since then.... I do not know what to do. I suppose that there is not a way to back up the folder you mentioned. I think that I have to install something from the very begining, as if the phone was to receive the installation of the very first program, as if it was just coming from the factory, totaly clean. Is that so? Am I right? And, how to do it? I tryed to download the stock rom from Samsung, but I think it was difficult and could not have it accomplished.
Thanks a lot and I'm still waiting instructions of how to solve this problem.
You should try using different USB cables and different USB ports to recognize the phone.
I assume you are using Windows since you mentioned Odin. When you connect the phone, do you see any new devices appear under Device Manager?
What is the phone's model # in download mode?
Is the the ROM you used: https://www.stockrom.net/2015/11/stock-rom-original-de-fabrica-samsung_19.html ?
Did you try using Odin 3.07?
Hi Audit13!
Thanks a lot for your help! I've already got hte files you mentioned and am preparing for trying to do the procedure you taught me.
Thanks again and soon, I hope, to be back to confirm whether it succeded.
Bie....
Hi Audit13,
Unfortunately the computer is not recognizing the SGS device.
I was ready to install the sock rom you suggested, had downloaded the Odin 3.07. I use Windows 10 and the latest drivers have been installed. The phone was in the download mode and tryed all available USB port. I've waited some minutes in each USB port for recognition with no success.
I thank you for your help. Is there any other method we could try? If you could please indicate, I thank you again.
Is there a method available using ADB procedures?
Hope there is.
Thanks, anyway for the help.
Hi Audit13
I think that the situation got a little worse. I tryed to do some recovery on the emergency recovery mode, but none of them succeeded. Now, what I get when tryng to get to the recovery mode is an android robot with an open belly with a red triangle coming out of it.... It gets to thedownload mode, but no recognition from the computer. This happened after trying to ionstall the stock rom obtained from the site you mentioned. The only thing that I could do was through the Universal-Android-Diag-Enabler-V2, what made the qualcomm start. Is there a way to make a comand to the phone that could star the USB debbuging? I tryed the various ODIN versions but with no success.
There is another problem - I'm using Windows 10 and the PowerShell uses different command lines not recognized by adb. I tipped devices and the program indicated that there was an mistake.
Is ther an Instructions Booklet for Odin?
What is your opinion? Do you think that there still exists a solution for my phone's case? If so, what to do?
Please, I ask you to help me on solving this problem.
Thanks in advance...
greetings. i need help with my lg v10 f600s which is now hard bricked. the story go so, when i go the phone . it was running on marshmelow no issues or problems.then i installed termux and when i wanted to update or download packages it kept on giving me errors.o googled around and found out it had to o the it no longer been maintained on mm software.so i searched around and found an update for the phone to nougaout firmware, so i downloaded it and updated the phone and thats when all my problems started .first my speaker phone stoped working , the major issue was the phone would randomly turn off at 40, 50, 60 percent charge.so i donwloaded the stock mm firmware to downgrade back to mm used lg up but it would not work and kept giving error.tried several other lg flash tools to no avail. then so a video about using qfil, then i built a qfil flashable firmware and managed to get the phone in to edl mode but while flashing i got these errors
{
"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"
}
then i switched to miracle tool and kept gettint this error even with the system.img file present
all throug this process my phone was boot up but all of a sudden when i tried turning it on ,it would not boot up or charge again. i can still enter the edl mode by shorting test points, and also the pcd would heat up when i enter edl mode.pleas how do i solve this.
The V10 was a flagship with known bootloop & heat issues. LG extended it's warranty by 2yrs. Try https://duckduckgo.com/?q=xda unbrick v10
ok thanks let me check it out
It is a really neat phone. Mine still works.
Try clearing Davik, etc, caches.
Try pulling the battery, then holding the power button down for a few.
Try another charger and cord.
If all else fails, it might like to visit the inside of your freezer for a few min.
Anyways, dont worry it to hard. $10-$30 ones can be easily gotten on ebay.
ǀcey said:
It is a really neat phone. Mine still works.
Try clearing Davik, etc, caches.
Try pulling the battery, then holding the power button down for a few.
Try another charger and cord.
If all else fails, it might like to visit the inside of your freezer for a few min.
Anyways, dont worry it to hard. $10-$30 ones can be easily gotten on ebay.
Click to expand...
Click to collapse
tried the link but could not find any solution, and i cant clear cache even if the phone was on because i had booted in to recovery but there were no cammmands, and it does not boot into fastboot mode.and i am in cameroon so ebay is not an option.this phone is realy giving me a headache and right now i am not in the position to buy a new PHONE NOW.if only i had access to a box that would make things easier .there is also one thing i noticed when i disassembled the phone it written on the board F600L__EAX66751701_1.1_MAIN. I THINK THIS MEANS I ACTUALLY HAVE BUT AN F600L AND NOT F600S.BUT THEN ON LGUP IT SHOWED F600S
Once mine was updated by LG repair(vs990), LG up could not overwrite it or roll it back.
I think all other variants could be rolled back via workarounds which can be all found here within xda.
If I remember correctly it had to be plugged into a pc(?), While power button(+ volume up(?)) was held down to enter certian menus.
There is apps out now which can send it adb commands via wifi ip or bluetooth. Easy Fire Tools is one.
Often their charge ports would go bad due to a weak soder. The batteries often failed from heat. You mentioned heat.
It sounds like you may have used a wrong update file meant for a different board/variant.
ǀcey said:
Once mine was updated by LG repair(vs990), LG up could not overwrite it or roll it back.
I think all other variants could be rolled back via workarounds which can be all found here within xda.
If I remember correctly it had to be plugged into a pc(?), While power button(+ volume up(?)) was held down to enter certian menus.
There is apps out now which can send it adb commands via wifi ip or bluetooth. Easy Fire Tools is one.
Often their charge ports would go bad due to a weak soder. The batteries often failed from heat. You mentioned heat.
It sounds like you may have used a wrong update file meant for a different board/variant.
Click to expand...
Click to collapse
i managed to flash all other partitions using MIRACLE except the SYSTEM partition by editing the RAWPROGRAM0 XML file and removing the line of code that enables flashing SYSTEM partition which got rid of the error "CAN NOT FIND SYSTEM.IMG".now i am trying to flash the system partition alone
i am getting "sahara_rx_data:194 unable to read packet header.only read 0 bytes"
using qfil
finally flashed the system partition using MIRACLE TOOLl but phone wont still turn on.i think it realy is an f600l and not f600s.i will build a different firmware using the f600l kdz and flash it see if that works
greetings i have flashed the f600l firmware but still no change phone is still dead. even flashed the firmware dump that i took before the phone got bricked but still no change.and the firehose file only works with miracle tool when i use qfil it keeeps given me errors.pleas can some one help me with a firehose file that will work with qfil