Stuck at DELL boot logo.
I mistakenly flashed another file when i was FastbootMode , now my streak is unable to boot and stuck at DELL logo and the capacitive buttons are light when i turn the device on. Can not access the fastboot mode at all.
What steps should i take , to make it alive again ?
when i take the cover off , it still stay at bootlogo until i take off the battery
What does this mean, shouldn't it be automatic?
What am i missing ? (the right adb driver ??)
I did install the drivers form dell ftp://ftp.dell.com/Handheld/R288920.exe
It makes a reboot attempt , shows the battery % changed and then shuts off.
QDL report:
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Mon Dec 05 23:40:38 2011
Check image DBL: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: F:\dell\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device .........
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2011/12/05 23:41:20
Elapsed Time: 40.38 sec
Can anyone show me how to install the RIGHT adb driver , i am searching but to no avail so far.
Tried several adb installation, but i dont see the ADB composite on my Device Manager, btw i am running windows XP SP3.
Any help or right info is very much appreciated as this device is not dead at all , just needs the right procedure , which i am trying to find but i need some help on the right directions.
Thank you
Solved !!!
Problem solved !!!
As it is impossible to brick the Streak by just uploading software to it, i found out that all the problem was caused by my USB port and the outdates drivers i was installing on my Windows XP installation.
I found out and downloaded the old QDL 2.7.4.5, streakflash.zip was the name of the package, then i had access to FASTBOOT and recovery menu, the rest was easy then.
Installed the recovery.img that goes with 406 Olleh, then updated to 406 to be sure all the other mbn files were updated as well, then installed StreakMod and finally the DSC 0.6b and last 0.62b http://forum.xda-developers.com/showthread.php?t=1314898
Amassing resource of info here
Hell no... the streak is in fact capable of a true brick by uploading software to (mine died 2 days ago) and it doesn't seem to have a solution (with practicaly no help from the experts here)
ThisisZAK said:
Hell no... the streak is in fact capable of a true brick by uploading software to (mine died 2 days ago) and it doesn't seem to have a solution (with practicaly no help from the experts here)
Click to expand...
Click to collapse
And what did you do , exactly that you consider it a brick now (i highly doubt it thou).
I saw your problem , tell me how to get the image you need from my Streak and i will upload it somewhere so you can try , btw it is up to you to tell me whats needed as i don't know, i am just willing to help you if i can.
Have you tried android.modaco.com/topic/311538-hardware-hacking-this-puppy-input/
ThisisZAK said:
Hell no... the streak is in fact capable of a true brick by uploading software to (mine died 2 days ago) and it doesn't seem to have a solution (with practicaly no help from the experts here)
Click to expand...
Click to collapse
That's because Fastboot -w or Fastboot -erase is pretty much a death sentence for any Streak and the enthusiasts (NOT experts) here know that. The members here also know to carefully read information before attempting to do anything to their devices.
@abauer: What ThisisZAK did does in fact turn the Streak into a virtually unrecoverable brick that not even the QDL tool can fix. He didn't help his cause by not paying close attention to the advice given, which was to unformat the MicroSD. He ended up formatting it, which is why he's looking for an image file so he can flash the image onto the MicroSD and restore his Streak.
If you can help him, that's great. You'll need to take your Streak apart, get the MicroSD from its slot, and image the drive using a program like DriveImage XML.
I have created an image of my inner SD Card right after a factory reset.
Download Here
I created this using Clonezilla, you should be able to use Clonezilla to restore it. It is an image of the entire sd card. You need to unzip the downloaded file to use it.
Note: I am running DSC_Rom, which is Gingerbread based. I don't think it makes a difference.
Edit: I did restore this image to another 2 GB Sd Card and my Streak booted fine.
I dont believe it should. All innerSD partitions have always been ext3 while all nand partitions are yaffs2 (though i believe GB can remount system as ext4 or something, I dont really understand how that works)
with the inner sd card been an ext its linux so its accessible but i am yet to play with it really
Related
I got all the drivers that I need and im at the last part where you hold down the volume button and then plug in the usb cable but nothing im stuck any help would be much appreciated.....ps how many of my drivers should I have deleted at the begining of this how thing
Do yo have repairtool.zip (or same QDLTool)?......
Greetings .
wear90.
wear90 said:
Do yo have repairtool.zip (or same QDLTool)?......
Greetings .
wear90.
Click to expand...
Click to collapse
QDL tool man all I want is 2.2 on this sick five inch this is day two of trying and look at forms and every thing mehhhhh
scaronscar said:
I got all the drivers that I need and im at the last part where you hold down the volume button and then plug in the usb cable but nothing im stuck any help would be much appreciated.....ps how many of my drivers should I have deleted at the begining of this how thing
Click to expand...
Click to collapse
When you say "volume up" are you using the volume up as it would be if it was in portrait? If your holding in landscape, the "volume up" is the left one (closest to the headset speaker)
scaronscar said:
QDL tool man all I want is 2.2 on this sick five inch this is day two of trying and look at forms and every thing mehhhhh
Click to expand...
Click to collapse
Hi SCARONSCAR.....do not you get mad!!!!!.....if you already have QDLTool, all you have to do is follow instructions in this link.
Please, tell you me how it goes.
Greetings .
wear90.
Kohawk09 said:
When you say "volume up" are you using the volume up as it would be if it was in portrait? If your holding in landscape, the "volume up" is the left one (closest to the headset speaker)
Click to expand...
Click to collapse
if I hold it in landscape on my Dell streak the volume up is on the right so your saying if in landscape I should use the volume down on mine the one closer to the headphone Jack? I think I have tried both ways but ill do it again....
Oh ya sorry I didn't get back to you guys I got it working the next day love 2.2 on this beast.... I still like SlideIT better then swype on this and the problem I think was a Dell file I had to open and it did a little black pop window and it was done in a second then when I did everything before it work... After all was ready and going it took about five minutes for streak to load.... Thanks and 2.2 is sick
QDL tool issues?
I have been trying for a month to upgrade, and I am just missing something. I have my device rooted and have tried the QDL tool, it gets about half way through the process and fails. I don't recall everything I have done, as I have tried a dozen times.
I rooted the device.
I downloaded some drivers and installed them.
I downloaded the QDL tool
Did you go from At&t 1.6 to O2 1.6 first (that I have not done).
A step by step would be wonderful.
I get this:
HW:
Board ID:
Comment:
QDLTool: M 2.7.4.8, Build ID: 1.301.20101022, SW: 12-324012-AUSB1AM-09
--
LOG
--
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Tue Feb 15 19:57:40 2011
Check image DBL: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \dbl.mbn ...
Check image FSBL: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \fsbl.mbn ...
Check image OSBL: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \osbl.mbn ...
Check image AMSS: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \amss.mbn ...
Check image DSP1: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \dsp1.mbn ...
Check image APPSBL: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \appsboot.mbn ...
Check image DT: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \DT.img ...
Check image boot.img: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \boot.img ...
Check image system.img: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \system.img ...
Check image userdata.img: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \userdata.img ...
Check image recovery.img: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \recovery.img ...
Check image logfilter.img: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \logfilter.img ...
Check image Region: C:\Streak\QDLTool3rd_20101022_GAUSB1A130500\images \RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-324012-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
ERROR[D14]: Streaming hello Failed!
ERROR: Download fail!
Please remove the battery and try again.
Wait for modem set up ......
Download Fail! - 2011/02/15 19:58:21
Elapsed Time: 40.52 sec
I went from 1.6 to 2.2 from at&t streak there is a link at the top of this its a step by step with video and everything good luck man sorry you have been having such a problem....
There is link at the top of the page and its a step by step with a video good luck man sorry you have been having such a problem with it
I have watched the video a dozen times. I don't see anything I missed. It just won't happen for me.
scaronscar said:
QDL tool man all I want is 2.2 on this sick five inch this is day two of trying and look at forms and every thing mehhhhh
Click to expand...
Click to collapse
Don't be too worried, it took me 5 days to figure out the streak.. it has crazy ****..
use streakdroid.com
follow step by step! you don't have to use streakdroid, but follow tut all the way through QDL. try different usb port, that was my problem..
and make sure you ahve the correct drivers... Also ran into that.
Change to a different USB plug, that worked for me.
Phone not booting into Fastboot. Will QDL help.
Hey All,
I searched for my problem in many places, no go.
No one talking about Streak not going into Fastboot mode.
Here's what happened...
I was trying to install GingerStreak 2.4.4 from GingerStreak 2.4.3.
http://forum.xda-developers.com/show....php?t=1333010
According to the instructions, I flashed
amss.mbn - http://mirror2.streakdroid.com/amss.mbn
and
dsp1.mbn - http://mirror2.streakdroid.com/dsp1.mbn
(got both the files from the first link above)
Then when I tried to reboot into Bootloader (Power+Vol Up+Vol Down) but nothing happens apart from the Dell logo being displayed.
I try to boot normally, still stuck at the Dell logo. The phone never even reaches the boot animation.
I try to go boot into fastboot (power+camera key)mode, but the phone never even boots. The screen stays off, so do the LED lights.
I figured out that the files downloaded above were incomplete(due to slow speed Chrome showed incomplete files as download complete).
amss downloaded: 111KB. Actual Size: 15.41MB
DSP1 Downloaded: 250KB. Actual Size: 8.94MB
So, I flashed the wrong files.
Now, I guess, the phone is bricked big time.
I need big time to get into fastboot mode (to flash the correct files) or anyhow get my phone working.
I need to know if QDL tool will help me sort this out. It is currently downloading. If I get the answer, will post back.
Guys, need help. Please help me out and get this issue sorted out.
hi, I'm newbie in here, so I don't know where should I put this question.
I'm using LG L70 D325 running on CM12 Unofficial. since the /system partition size is small (around 571 MB) I tried to increasing it's size from this thread. previously it got me working and change my system partition from 571 MB into 1,44 GB for about 2 week but somehow, I uninstalled a wrong system application and I have to reflash CM12 all over again. when I tried to resizing the system partition, it got me stuck for 2 days (I've tried countless times) since my system partition won't resized like it used to. and I type this on fastboot :
Code:
fastboot flash APPSBL appsboot_250_134_64.mbn
but it got me error saying that the APPSBL partition is not available. so I look to another site and foolishly tought that my APPSBL partition is my sbl1 partition and type this :
Code:
fastboot flash sbl1 appsboot.mbn
fastboot continue
and remove the battery. now, my phone can't turned on, can't charge, doesn't even showing any sign that it has a power even if I insert the cable data while still removing the battery (I believe this is called hard bricked). so is there any way round to make it turned on, or I have to sent it into service center? all help and advice are welcome. thanks
Hello.
I'm struggling with this for days now without any result, so I decided to ask for some help.
I had this phone staying in my closet for a few months. A couple of days ago when I tried to charge it, I got the logo saying "Powered by Android" and get stuck there. (the phone was working perfectly before)
Interesting thing was, that most of the time I was not able to power it up at all.
Sometimes I managed to got it into Fastboot Mode TA, but not always.
Reading post here, I tried to reflash with stock ROM using YGDP.
It went smoothly, but now the bootloader is completely corrupted. Not able to get into Fastboot Mode anymore. Doesn't respond to any key at all.
It is recognised as Qualcomm hs-usb qdloader 9008.
After reading some more, I tried to get yhe bootloader back using QFIL without success.
No matter what I try, I get:
13: C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn
14:37:07: Requested ID 13, file: "C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn"
14:37:07: ERROR: function: is_ack_successful:988 SAHARA_NAK_INVALID_DEST_ADDR
14:37:07: ERROR: function: sahara_start:825 Exiting abruptly
14:37:07: ERROR: function: sahara_main:854 Sahara protocol error
14:37:07: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Same errors with prog_emmc_firehose_8936.mbn
It doesn't even get any acknowledge back from the phone?
Any help is highly appreciated.
Thanks.
Hi , I think you need a full emmc backup.img from working device in order to put your device in fastboot mode and be able to normaly flash stock firmware ....
https://forum.xda-developers.com/general/general/guide-unbrick-coolpad-dazen1-qualcomm-t3362253
Where to get an eMMC dump from?
I've tried with that dump in that post, but absolutely no change at all.
Will the phone read the SD card while it's off? At least that's what that post is telling me to do.
• After successful completion of writing eMMC backup image to SD card, insert the MicroSD card in your device and remove all sim cards. Insert battery into your device now. Do not power it on yet.
• Now you can boot to fastboot mode with the eMMC image on SDCARD.
Click to expand...
Click to collapse
I don't really get this part...
Hi you can't use backup from another device so you need to have the same working device it need to be rooted in order to do make debrick.img which you will make it bootable on micro sd card with Win32DiskImager tool . So then you should put your device in fastboot mode and flash normaly official stock firmware with YGDP tool ... If you don't know someone who can do that for you , check on the internet or YouTube who has device like your to make full emmc dump .
But it you don't have it then you can try Qualfast flash tool , but it required device to be into fastboot mode also you need to extract CPB firmware
Qualfast flash tool
https://androiddatahost.com/asaew
Download firmware from here :
http://www.mediafire.com/file/b3xdr59s6roj0jz/Coolpad_7576U_4.4.230.33.T3.140715.7576U.zip
Example how to extract CBP firmware files .
https://www.youtube.com/watch?v=OEbWKkzfiSA
Example how to use Qualfast flash tool :
https://www.youtube.com/watch?v=R4Bvy0Sax6Q
Just select path from extracted firmware for example C:/Users/SZabio/Desktop/Coolpad 7576U estracted firmware/ , wait all bars to be colored ....
Another option what you can try is one chinese app called COOLPAD DOWNLOAD ASSISTANT SETUP :
Download from here :
English language:
https://drive.google.com/file/d/0B5vyMGZJJmcnclVJb2Y2cHNNQkU/view
Chinese language
http://www.mediafire.com/file/e28degd1vjvevh3/Coolpad+Download+Assistant+Setup+V1.89_141231.rar
add path of CPB firmware (4.4.230.33.T3.140715.7576U.vf_ro.CPB) on number 2 ( browse) and click on green button ( Check Rom) , from up will be 100% loaded , now connect your device without the battery once the app detect your tool it will start writing files to your device .
Example how it should be :
https://www.youtube.com/watch?v=ZhWtvNVlqzE
Good Luck my friend , I hope you will finally get him to work again .
Thank you for trying to help, but as I said, the phone cannot be put into FastBoot mode.
It is completely dead, does not react to any button presses, does not even charge the battery anymore.
It is detected by the PC as "Qualcomm hs-usb qdloader 9008".
That's all.
I know nobody to get a full eMMC dump from unfortunately.
I've found out, that the phone's CPU is a Qualcomm MSM8210 Snapdragon 200, so I tried prog_emmc_firehose_8x10.mbn programming file.
Now QFIL is able to communicate with the phone, but all I'm getting is a bunch of errors, because the configuration .xml files are wrong.
I need rawprogram0.xml patch0.xml and partition.xml for this phone.
I don't understand why the bootloader was not blocked, so it could not have been overwritten by mistake.
Does anyone have some info on how the partitions are organised? Would be enough to write the bootloader in correctly, to get fast boot mode working again?
I downloaded a stock KDZ for my device and LGUP got stuck at 99% and eventually, it turned itself off but then nothing happened after that. Now it doesn't boot up at all and when I plug it in, it shows "unrecognized USB device" from windows. I tried to boot back into download mode but I can't do that and the screen is still black. Any help would be appreciated.
jimmysofat6864 said:
I downloaded a stock KDZ for my device and LGUP got stuck at 99% and eventually, it turned itself off but then nothing happened after that. Now it doesn't boot up at all and when I plug it in, it shows "unrecognized USB device" from windows. I tried to boot back into download mode but I can't do that and the screen is still black. Any help would be appreciated.
Click to expand...
Click to collapse
You need to download Qualcomm drivers for HS_qdloader9008 mode. Your phone is in emergency download mode. You'll also need a qfil style rom for the flash programer (emmc_firehose_MSM8909.mbn). Use emmcdl.exe to install rom.
lehmancurtis said:
You need to download Qualcomm drivers for HS_qdloader9008 mode. Your phone is in emergency download mode. You'll also need a qfil style rom for the flash programer (emmc_firehose_MSM8909.mbn). Use emmcdl.exe to install rom.
Click to expand...
Click to collapse
So I got the ROM and extracted it and made appropriate programmable files and proper patch0.xml files. Now where can I get the flash programmer file (emmc_firehose_MSM8909.mbn) (Firehose File/Programmer File)? Also where can I get a QFIL style ROM for my phone? with the flash programmer file and the other xml files? I tried a bunch of mbn files for MSM8909 that I found for the flash programmer and I'd end up with these errors.
2019-04-11 17:02:52.223 13: E:\LG K7\DZ Extractor With Combined System.bin\prog_emmc_firehose_8909_ddr.mbn
2019-04-11 17:02:52.227
2019-04-11 17:02:52.227 17:02:52: ERROR: function: rx_data:247 Error occurred while reading from COM port
2019-04-11 17:02:52.231
2019-04-11 17:02:52.231 17:02:52: ERROR: function: sahara_main:924 Sahara protocol error
2019-04-11 17:02:52.231
2019-04-11 17:02:52.231 17:02:52: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2019-04-11 17:02:52.235
2019-04-11 17:02:52.235
2019-04-11 17:02:52.235 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2019-04-11 17:02:52.235 Finish Download
Most oem flashers have been leaked. You just have to keep looking. It'll be named prog_emmc_firehose_msm8909.mbn roughly. That with the patch xml and you'll need rawprogram0.xml.
lehmancurtis said:
Most oem flashers have been leaked. You just have to keep looking. It'll be named prog_emmc_firehose_msm8909.mbn roughly. That with the patch xml and you'll need rawprogram0.xml.
Click to expand...
Click to collapse
I've been looking around for quite a while and I haven't found it. Is there a way to make a firehose file from the kdz file? If not, then can you help me find it?
lehmancurtis said:
Most oem flashers have been leaked. You just have to keep looking. It'll be named prog_emmc_firehose_msm8909.mbn roughly. That with the patch xml and you'll need rawprogram0.xml.
Click to expand...
Click to collapse
I used a file that was similarly named to that or exactly named that and the flash still failed with the same error from before. Would you happen to have a functional firehose file?
I don't have it but I'm trying to find one also. Or another option
---------- Post added at 03:49 PM ---------- Previous post was at 03:47 PM ----------
Sometimes if you hold power and volume+ for over 30 seconds it triggers a reset from edl.
lehmancurtis said:
I don't have it but I'm trying to find one also. Or another option
---------- Post added at 03:49 PM ---------- Previous post was at 03:47 PM ----------
Sometimes if you hold power and volume+ for over 30 seconds it triggers a reset from edl.
Click to expand...
Click to collapse
Ok I tried using Tool Studio and inputed the files but there's a problem. There's no RAM or BOOT image for me to flash and the program wont continue without it. If possible, would you happen to have the RAM or BOOT image for the LGMS330? All the files are there except for those two files. It's that and if you know any other tools I can use to flash my phone besides qfil and tool studio.
I do have a boot image. I'll post it asap. When you get things working please post your findings.
#UPDATE
I am uploading a folder with the stock boot.img and the split image / ramdisk produced from using [email protected]
Heres the link. Best of luck to ya.
https://drive.google.com/folderview?id=1i7FTfCD04gvT_SGSBahrAIbwVhjZcvva
lehmancurtis said:
I do have a boot image. I'll post it asap. When you get things working please post your findings.
#UPDATE
I am uploading a folder with the stock boot.img and the split image / ramdisk produced from using [email protected]
Heres the link. Best of luck to ya.
https://drive.google.com/folderview?id=1i7FTfCD04gvT_SGSBahrAIbwVhjZcvva
Click to expand...
Click to collapse
Do you know how to put the ramdisk image into a mbn file? The tool I'm using seems to only accept those types of files for the ramdisk.
Edit: Also would you happen to know if you can also put the boot image into a mbn file as well?
If you have busybox or a linux machine run this on the boot.img
Code:
dd if=/path/to/boot.img of=/path/you/save/boot.mbn
Be sure to use ur paths.
lehmancurtis said:
If you have busybox or a linux machine run this on the boot.img
Code:
dd if=/path/to/boot.img of=/path/you/save/boot.mbn
Be sure to use ur paths.
Click to expand...
Click to collapse
Would you happen to know how to turn the ramdisk image into a mbn or img file?
It's Something But Back to Square One
I decided to use eMMC software download and flash the os to a micro sd card as I saw other people do it for other phones as I saw no other way out of qloader mode. After I did that, I put the sd card into the phone and plugged it in, the screen is still black but now it comes up as LGE AndrodNet USB Serial Port. When that came up, I thought I could use LGUP but there's a problem with every LG tool I used
LGUP Would Show unknown model and show a com port number and nothing after it. When I did select that port it would say "you have to select a known model please"
When I used LG FlashTool 1.8.1, every time I would load a firmware and press the yellow arrow, It would say "Failed PreviousLoad()". (I know this software works because I have tried it on different phones and it would work)
When I use LG Bridge, I'd select update error recovery and it would go on "checking device information" and would return back with "connect your mobile device to the USB port. If it is already connected, contact LG customer service.
When I use LG Flash Tool 2014, It would say "problem with communication between cell phone and PC"
Does anybody have any other ideas for me to try or any other tools to use? All help is appreciated
The mkboot binaries are available on github. If I remember correctly one of the output files when you split a boot image with mkboot can be used for that. Also, dd is a file conversion tool. I've been playing with the lglaf.py tool. But you would would need to be able to access laf. First you have to overcome edl. The flash programmer is out there somewhere.
Something I just discovered that work on a 8909 ZTE device might help you also. If you have the rawprogram0.xml file.
Code:
emmcdl -p COM"your port" -x rawprogram0.xml
You need all ur files in the same folder (ROM & emmcdl.exe).
## I'm going to play aroung with LGUP and see if some of the modded versions can find edl.
lehmancurtis said:
Something I just discovered that work on a 8909 ZTE device might help you also. If you have the rawprogram0.xml file.
Code:
emmcdl -p COM"your port" -x rawprogram0.xml
You need all ur files in the same folder (ROM & emmcdl.exe).
## I'm going to play aroung with LGUP and see if some of the modded versions can find edl.
Click to expand...
Click to collapse
Well I tried this and all that happens is that it gets stuck in sectors remaining and that's it. Im assuming this is the correct emmcdl that I found in my windows folder.
Code:
E:\LG K7\DZ Extractor With Combined System.bin>emmcdl -p COM"5" -x rawprogram0.xml
Version 2.16
Programming image
Finding all devices in emergency download mode...
Qualcomm HS-USB QDLoader 9008 (COM5)
Finding all disks on computer ...
\\.\PhysicalDrive5Successfully opened disk
start_sector: 34 physical_partition_number: 0 num_partition_sectors: 131072 filename: NON-HLOS.bin file_sector_offset: 0
Sparse image not detected -- loading binary
In offset: 0 out offset: 34 sectors: 101376
Sectors remaining: 99328
jimmysofat6864 said:
Something I just discovered that work on a 8909 ZTE device might help you also. If you have the rawprogram0.xml file.
Well I tried this and all that happens is that it gets stuck in sectors remaining and that's it. Im assuming this is the correct emmcdl that I found in my windows folder.
Click to expand...
Click to collapse
Try this
Code:
emmcdl.exe -p COM5 -x rawprogram0.xml SetActivePartition=0
lehmancurtis said:
Try this
Code:
emmcdl.exe -p COM5 -x rawprogram0.xml SetActivePartition=0
Click to expand...
Click to collapse
It appears the same thing happens even with that. If you have this phone can you send the files instead because it might be because my rom files are wrong. I don't think so but it's a possibility. Even with that the same thing happened.
Code:
E:\LG K7\DZ Extractor With Combined System.bin>emmcdl.exe -p COM5 -x rawprogram0.xml SetActivePartition=0
Version 2.16
Programming image
Finding all devices in emergency download mode...
Qualcomm HS-USB QDLoader 9008 (COM5)
Finding all disks on computer ...
0. \\.\PhysicalDrive0 Size: 244198MB, (500118192 sectors), size: 512 Mount:C:, Name:[]
1. \\.\PhysicalDrive1 Size: 14944MB, (30605312 sectors), size: 512 Mount:E:, Name:[]
\\.\PhysicalDrive5Successfully opened disk
start_sector: 34 physical_partition_number: 0 num_partition_sectors: 131072 filename: NON-HLOS.bin file_sector_offset: 0
Sparse image not detected -- loading binary
In offset: 0 out offset: 34 sectors: 101376
Sectors remaining: 99328
D o you have metro or TMobile?
lehmancurtis said:
D o you have metro or TMobile?
Click to expand...
Click to collapse
I have the MS330 Model so it's definitely a Metro PCS model.
So long story short , i flashed a ROM using mtk client and usbdk driver and now my device wont turn on , doesnt display corrupted rom or boot or anything like that , no fastboot no recovery and somehow i get the boot to boot into BROM mode , now problem is when i am injecting payload from mtk client using command " python mtk payload " the payload injection is done succesfully but problem comes when i execute the next command which is " python mtk_gui " it gets stuck on detecting phone 0x200000 and the mtk_gui menu just doesnt open it stays stuck there forever , in the command windows it says no preloader detected amd daxflash error. Any idea if anyone of you could help me with this one ?
Also drivers installed are OPPO mtk vcom 1668 driver and usbdk driver .
No idea how to use sp flash tool as there are no exact instructions for sp flash tools
I tried flashing many roms like govix and other roms but still the phones screen just stays black .
The Phone gets stuck on
Jumping to 0x200000 ok. in MTK GUI
in command console it says : No preloader given . Operation may fail due to no DRAM Setup .
Uploading Stage 2
DAXFlash
Error on sending data: DA hash mismatch
Error on booting to DA
Any help would be appreciated .
You should've flashed the TWRP through fastboot and then flash the ROM from there, I honestly don't know how you flashed it from MTK, but anyway...
Try using the live-distro which is on MTKClient's GitHub page; flash it into an USB and boot from it. Had no issues at all on it (mostly used the GUI version), compared to Windows.
Flash a version's stock firmware partitions (A.20 is overall the best), all of them except seccfg, persist, nvcfg, nvdata, nvram, protect1, protect2, which are device-specific partitions.
Here's Giovix's guide.