Related
I was running streakdroid 1.8.1, and was having the wifi/3g problem, and after trying the below suggestion (which was posted in the dev section of the 1.8.1 thread post#367 link=http://forum.xda-developers.com/showpost.php?p=11869560&postcount=367):
--------------------------------------------------------------------------
Originally Posted by strvmarv
This put me on baseband GAUSB1A134031-US and appears to have cleared up the Data that wouldn't enable without a reboot, so far:
1. extracted the decoded ATT 2.2 340 pkg from here...it's the dropbox link BTW! (dropbox link)
2. grabbed the amss.mbn and dsp1.mbn (if you don't want to do step 1 then get the already extracted files here)
3. went into fastboot and flashed both of them
Dumb question, anyone know if it's possible to lose your carrier unlock when doing such things?
--------------------------------------------------------------------------
Now my streak doesn't boot, can't get to fastboot (pwr+camera), or recovery (vol+,vol-, pwr). Sometimes all three led's light up, and stay on and nothing happens, and sometimes the LED's stay off and nothing happens.
I tried using qdltool (vol+, usb connection to PC) , and it timesout after reboot ok message after I click RUN in qdltool. I installed both the qualcomm and dell fastboot drivers as per instructions, and I don't have a yellow ! in device manager.
Would appreciate any suggestions on what I should try next.
jfvidalc said:
I was running streakdroid 1.8.1, and was having the wifi/3g problem, and after trying the below suggestion (which was posted in the dev section of the 1.8.1 thread post#367 link=http://forum.xda-developers.com/showpost.php?p=11869560&postcount=367):
--------------------------------------------------------------------------
Originally Posted by strvmarv
This put me on baseband GAUSB1A134031-US and appears to have cleared up the Data that wouldn't enable without a reboot, so far:
1. extracted the decoded ATT 2.2 340 pkg from here...it's the dropbox link BTW! (dropbox link)
2. grabbed the amss.mbn and dsp1.mbn (if you don't want to do step 1 then get the already extracted files here)
3. went into fastboot and flashed both of them
Dumb question, anyone know if it's possible to lose your carrier unlock when doing such things?
--------------------------------------------------------------------------
Now my streak doesn't boot, can't get to fastboot (pwr+camera), or recovery (vol+,vol-, pwr). Sometimes all three led's light up, and stay on and nothing happens, and sometimes the LED's stay off and nothing happens.
I tried using qdltool (vol+, usb connection to PC) , and it timesout after reboot ok message after I click RUN in qdltool. I installed both the qualcomm and dell fastboot drivers as per instructions, and I don't have a yellow ! in device manager.
Would appreciate any suggestions on what I should try next.
Click to expand...
Click to collapse
search for the QDL tool, follow instructions and you will be in business again.
I tried QDL tool, and it fails with a fastboot timeout error:
"wait ADB fastboot mode timeout!"
That means you dont have the fastboot driver loaded right.
First is the qualcom driver which you made through... after the small stuff loads. It then pops over to fastboot driver.
Try another driver or pc
Sent from my Dell Streak using Tapatalk
I download and successfully installed the Dell R288920 drivers.
Is there some other driver that works better?
i would remove fastboot drivers... reboot, use reinstall drivers and use a different usb...
are you running x64 windows by chance?
I have both a 64bit Win7 and a 32bit WinVista. I followed instructions on streakdroid.com to install qdl tool on 64bit, as well as trying it on 32bit, and they both fail in the same place.
Here's the tail end of the qdl tool log file:
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/03/06 23:34:45
Elapsed Time: 30.55 sec
It may be the drivers or it may be the Streak. I have a Streak that isnt recognized as a USB device when plugged in and will not boot into fastboot mode (black screen) with the camera+power buttons. I have tried on 3 PC's(2 windows 7, 1 linux) and none will talk to it via ADB. However they will talk to my other working Streak so I know it isnt the driver.
I suspect it is corrupt NAND memory and have come to the conclusion that the only way to fix it is to get someone to JTAG reprogram it or swap out the mainboard. I would love it if someone can prove me wrong though...
BTW i bought this Streak in this condition so I dont know for sure how it got in this state.
your missing something.. def a driver issue says so itself.
do you get fastboot to work at all outside the qdl tool? if so can you follow the following guide?
http://forum.pocketables.net/showthread.php?t=8285
That's just it, the streak won't power up (pwr+camera), which would allow me to do fastboot outside of qdl tool.
Before I bricked it, I was able to run fastboot outside of qdltool all the time without any problems.
its not bricked... there is an issue with the timing of the driver kicking in or something driver related.. try another pc.
this is a pc issue.. not a streak issue. This part was always the biggest pain in my ass.. took me hours to get my system working right for this stuff.. the streak.. no issues....
i think the streak is unbrickable like the galaxy s phones.
I've tried both my PC's (desktop Win7 64, laptop WinVista 32), and both get the same error.
I've also tried different usb ports. When I first tried fastboot a couple of months ago, I was able to install the correct driver because I was able to start the streak in fastboot mode which then allowed me to install the driver on the desktop ( called android something if I recall correctly).
The problem I had with the QDL tool was the ADB driver also. The instructions I watched didn't include installing it, but did include downloading the folder that had it. If you are following the visual tutorial from the streakdroid website, go into all the folders you downloaded in the process. Somewhere in there is your specifc ADB driver. I was getting the ADB fail also until I found my driver and it installed. Good luck.
Sent from my Dell Streak using XDA App
I agree with the above post. You havent updated the correct driver. I noticed that when i searched through the recovery folders i notoced that the qcuser driver or whatever it was called, was in multiple folders....i experienced the same ADB error you did but i just kept switching with qcuser driver until i found the correct one. Go have a second look or third look....im sure ull find the right one.
Sent from my Dell Streak using XDA App
I've tried all three qcser,qcusb and qcmdm in the repairtool (qdltool) driver subdirectory for 32bit windows in winvista and wnet, with no luck.
Did any of you have problems putting the streak in fastboot mode independent of the PC, because that's not working for me. It used to work for me by pressing pwr + camera buttons.
I believe the ADB drivers were in the other folder you downloaded per the directions.
Also, I was able to get into fastboot prior to the QDL tool, but I don't believe that matters at all. The QDL tool is halfway there at the point it errors on you. You just need that correct ADB driver. You are so close, don't give up. Try the faq section of streakdroid.com
Furthermore, if you have access to an XP machine use it. You are almost back to Streakville.
Sent from my Dell Streak using XDA App
see if this helps:
http://forum.pocketables.net/showthread.php?t=8214
EUREKA!!!!.
Looks like the flashboot image on the streak was corrupt, so I was able to use streakflash to recover it.
Running nandroid restore as I type this. so hopefully I can get back in business.
Thanks to all of you guys for your suggestions.
I'll let you know if the nandroid restore is successful.
jfvidalc said:
EUREKA!!!!.
Looks like the flashboot image on the streak was corrupt, so I was able to use streakflash to recover it.
Running nandroid restore as I type this. so hopefully I can get back in business.
Thanks to all of you guys for your suggestions.
I'll let you know if the nandroid restore is successful.
Click to expand...
Click to collapse
What is streakflash? a new tool? like QDL?
Krad said:
What is streakflash? a new tool? like QDL?
Click to expand...
Click to collapse
See this page - it is a version of QDLTool that only flashes some files. I believe that it is used to repair the boot.img.
From this page:
Q: I’m trying to flash my Streak with the QDLTool but it keeps coming up with Error D2 ADB Timeout
A: This can be for a number of reasons. Firstly, look at what is displayed on the screen of the Streak:
Nothing / Screen is blank: This could be a sign of a corrupted fastboot image. Download streakflash.zip from the Downloads section and use the version of QDLTool it contains to reinstall the base images. You can then retry using QDLTool from repairtool.zip
Black screen, says “DT is in FASTBOOT_MODE”: This can be the sign of a driver issue – Try reloading the Fastboot/ADB drivers
White screen, says “FASTBOOT_MODE”: Go through the process again, this time using a different USB port.
Click to expand...
Click to collapse
Nandroid restore of streakdroid 1.6.0 successful.
I've been trying to upgrade to the more recent versions, but none of them (at least in my case) are as stable as 1.6.0.
1.6.1 with it's builtin perfmod is unstable.
Both 1.7.x and 1.8.1 are stable, but they suffer from the wifi/3g problem. Both wifi and 3g work, but I usually have to reboot to switch from one to the other, which is a hassle.
Yes, I've tried factory resets on all of them, but eventually, I either have random reboots, or FC's galore.
I know other people have gotten 1.6.1, 1.7.x, and 1.8.x to run stable, but I've had no such luck.
So for now, I'm sticking with 1.6.0 ( I get quadrant scores in the 1600-1700 range, which is pretty good).
Anyway, thanks again for all your help.
i just got a streak yesterday,i tried to flash recovery img,and it said waiting for device....but nothing ever happens,now it wont boot up,i tried factory reset but still same thing,also i put a few different roms on,1.6.0,1.5.1,02 1.6,and even 1.9.0,i then tried each one by renaming them update.pkg(one at a time)but it gets this error
E:signature verification failed
what can i do to get it booted back up......i want to eventually have 1.9.0 on it
i think i have the gausbxxx34041
mokokawi said:
i just got a streak yesterday,i tried to flash recovery img,and it said waiting for device....but nothing ever happens,now it wont boot up,i tried factory reset but still same thing,also i put a few different roms on,1.6.0,1.5.1,02 1.6,and even 1.9.0,i then tried each one by renaming them update.pkg(one at a time)but it gets this error
E:signature verification failed
what can i do to get it booted back up......i want to eventually have 1.9.0 on it
i think i have the gausbxxx34041
Click to expand...
Click to collapse
i blve your gona have to use the QDL tool
mokokawi said:
i just got a streak yesterday,i tried to flash recovery img,and it said waiting for device....but nothing ever happens,now it wont boot up,i tried factory reset but still same thing,also i put a few different roms on,1.6.0,1.5.1,02 1.6,and even 1.9.0,i then tried each one by renaming them update.pkg(one at a time)but it gets this error
E:signature verification failed
what can i do to get it booted back up......i want to eventually have 1.9.0 on it
i think i have the gausbxxx34041
Click to expand...
Click to collapse
Not Android Development
Please post in the correct forums
Moving to general
sorry.....should have it in genearal
i tried qdl afew times,i have it in the right diagnostic 9002 driver,but when it gets too"starting adb" it crashes,i know i have the adb driver,and it uses those when i just connect normally?
btw:when i put streak in fastboot,and try any commands through cmd,it just says waiting on device,and never does anything : (
mokokawi said:
btw:when i put streak in fastboot,and try any commands through cmd,it just says waiting on device,and never does anything : (
Click to expand...
Click to collapse
Try different usb ports especially the one near the cpu and try reinstalling your drivers. That is a new device that is why your computer is acting **** that, I just received my replacement and it did just that. You've done it before, you can do it again, no need for you to use qdl just a matter of trouble shooting with the drivers especially if you are using windows 7
Sent from my Dell Streak using XDA Premium App
ok,i got it to boot up into 1.6.0
i didnt have the winusb drivers in the right folder i think....lol
Just got my streak yesterday, only had it a few hours and i've somehow managed to brick it already !
Started on the official 1.6, upgraded to official 2.2, rooted it, installed clockwork recovery. All was fine up until this point, i then went to install the performance fix http://forum.xda-developers.com/showthread.php?t=848487 but after doing so my streak stopped booting, since then its just hanging at the dell logo.
First thing i tried was restoring to the default recovery rom by holding power + volume buttons and option 2. This didnt work so i then tried this http://android.modaco.com/content/d...2-1-downloads-how-tos-rom-superboot-recovery/ and still no luck.
I've been at it for hours and its late so im giving up for now, i just hope the xda community can help me out.
Edit: I should add that the recovery image (option 2) is going through fine without errors, its only that when it boots it hangs at the dell logo. Also, fastboot is working so hopefully its not completely bricked. Is there anything i can do ?
get qdl tool and see if u can get to 305 stock
GET QDL TOOL HERE
Turn phone completely off, hold volume up and plug phone to computer
Open QDL Tool
if you have the correct driver, it will recognize ur phone
if not, the driver is included but u have to search how to install it
Hit Run and wait about 3-5 minutes
When its done it will reboot and be on stock 305 and then u can try again with ur update
Thanks just had a go at QDL but cant seem to get it to work. I got it to detect my phone as the Qualcomm HS-USB Diagnostics 9002 but after clicking run it just errors.
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Thu Apr 28 02:21:41 2011
Check image DBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\Users\Mark\Downloads\repairtool\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
ERROR[D14]: Streaming hello Failed!
ERROR: Download fail!
Please remove the battery and try again.
Wait for modem set up ......
Download Fail! - 2011/04/28 02:22:01
Elapsed Time: 19.70 sec
After countless hours of going insane i have managed to get my streak working again using the o2 package (build 8105) found here http://android.modaco.com/content/d...2-1-downloads-how-tos-rom-superboot-recovery/
I couldnt get QDL to work for some reason so in the end i just downloaded the above package, copied to sd, renamed to update.pkg, powered on with volume buttons and chose option 2.
Its working now so thats the main thing, i was worried i might have bricked it for good ! Now i just need to get back to the official dell rom
If I wre doing this, I would get the multi_recovery tool. I would put the 351 package on your SD card
Flash the 351 recovery with the tool. Do not boot up go right into the recovery and point it to the 351 package. Make sure the 351 package has been renamed to the proper name. Either update.pkg or update.zip.
Worked like a champ for me.
Sent from my Dell Streak using XDA App
alperin1 said:
If I wre doing this, I would get the multi_recovery tool. I would put the 351 package on your SD card
Flash the 351 recovery with the tool. Do not boot up go right into the recovery and point it to the 351 package. Make sure the 351 package has been renamed to the proper name. Either update.pkg or update.zip.
Worked like a champ for me.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
That's the method that just broke my phone.
ducehlmg said:
get qdl tool and see if u can get to 305 stock
GET QDL TOOL HERE
Turn phone completely off, hold volume up and plug phone to computer
Open QDL Tool
if you have the correct driver, it will recognize ur phone
if not, the driver is included but u have to search how to install it
Hit Run and wait about 3-5 minutes
When its done it will reboot and be on stock 305 and then u can try again with ur update
Click to expand...
Click to collapse
Sorry but bug in but I'm having the same issue. I finally got QDL to work but after it finishes, the phone shows a screen with "Andriod system recovery utility
Press the shutter button to start emergency software recovery
Warning all data will be erased
Press the Volume up button to power off without recovering".
After I press shutter the it loads the update.pkg and then sits on the dell logo, and sits, and sits.
I'm now back on the official dell 2.2, in the end i had to flash the 351 recovery image to get the rom pkg to work.
I flashed the above recovery in fastboot mode since i cant get QDL to work, checked my drivers countless times, tried windows 7 64 bit and 32 bit, aswell as windows xp 32 bit. 64 bit always gives me the d14 error and 32 bit is the d2 error so i just cant understand why it wont work, surely it cant be a driver issue since fastboot works flawlessly and i've spent hours checking the driver now. Also i've followed the guide on streakdroid to the book so im pretty certain my setup is perfect.
Anyway, im happy with the official 2.2 for a while now but at some point i would like to try a custom rom through qdl, etc.
drkdeath5000 said:
After countless hours of going insane i have managed to get my streak working again using the o2 package (build 8105) found here http://android.modaco.com/content/d...2-1-downloads-how-tos-rom-superboot-recovery/
I couldnt get QDL to work for some reason so in the end i just downloaded the above package, copied to sd, renamed to update.pkg, powered on with volume buttons and chose option 2.
Its working now so thats the main thing, i was worried i might have bricked it for good ! Now i just need to get back to the official dell rom
Click to expand...
Click to collapse
That's it? WHen I installed the recovery from your link, after it said recovery install done(something along those lines) the phone didn't restart like it has with my previous recovery installs. I waited a few minutes, pulled the battery, and restarted into recovery, hit update and it has been a blank screen since.
I think I'm out of luck. I had the phone plugged into the charger all night and I'm trying to flash it now and the battery is at 0%. Can't charge it or anything. Time to call dell.
I'm stucking at booting logo and can't connect my phone to pc.
I tried to install drivers from LG from http www lg com/uk/support/product/support-product-profile-mobile-redux.jsp?customerModelCode=GT540&initialTab=documents but my computer still can't recognize the phone.
I tried to go to device manager but can't find modems to disable LG Modem Driver
I tried LGMobile update through customer support -> recovery phone -> IMEI # but it's not working
I tried to use kdz to flash on 3 mode: CS, DIAG, EMERGENCY and still get this message:
[R&D Test Tools Log File]
01:14:37 : Launching SW update
01:14:37 : Unpacking KDZ
01:14:38 : KDZ file extraced
01:14:39 : Files were extracted.
01:14:39 : LGMobileDL Load.
01:14:39 : Port = -1
01:14:39 : Connecting to phone
01:14:39 : PHONE WAS NOT FOUND!
01:14:41 : ===FINISHED===
Click to expand...
Click to collapse
I've been searching around all night but can't find a solution
Pretty much I can't do anything to make pc recognize the phone...
I would appreciate any help to fix this phone. LG GT540 Optimus
By the way, I used the usb port on the back of my computer...
try to flash in DOWNLOAD MODE. when turning on phone click power and volume down maybe then computer find phone.
The phone is recognized in download mode. However KDZ says phone not found?
check in windows hardware manager if you have in modems your phone turn the modem off and then try flash via kdz
gt540bricked said:
The phone is recognized in download mode. However KDZ says phone not found?
Click to expand...
Click to collapse
Indeed, I tried to connect the phone on download mode but still cant flash anything because kdz showed phone not founded.
Sent from my SGH-T989 using XDA Premium App
zxcvbnnm said:
check in windows hardware manager if you have in modems your phone turn the modem off and then try flash via kdz
Click to expand...
Click to collapse
I cant flash in download mode, and i cant find modems in device manager. Im pretty sure i have all the drivers, even tried to uninstall/reinstall reset computer...
Sent from my SGH-T989 using XDA Premium App
ahhh i no have more idea :/ i had too that problem, only first logo lg and nothing more but i flashed in download mode without problems. Good luck
Im still trying but im getting nowhere, is there anyone know about this problem?
Sent from my SGH-T989 using XDA Premium App
yes this problem is not new many others had this problem either they some how fix it or its lg service center...
Does anyone have lg gt540 international driver ?
Sent from my SGH-T989 using XDA Premium App
Here are all of my GT540 Win7 drivers:
LGAndroidDriver_WHQL_ML_Ver_1.0_All_Win7.exe
LGAndroidPlatformDrivers_WHQL_ML_Ver_1.2_All_Win7.msi
LGBluetoothDrivers_WHQL_Ver_1.1.msi
LGSmartPhone_ModemlinkDUNDrive_WHQL_ML_Ver_1.0.exe
LGSmartphone_USBDriver_WHQL_ML_Ver_1.0.exe
LGUSBModemDrivers_WHQL_ML_Ver_4.9.7_All_Win7.msi
LGUSBModemDriver_WHQL_ML_Ver_4.9.7_All_Win7.exe
download link: http://dl.dropbox.com/u/230395/netöröld/driver.zip
Thank you very much, i will try it as soon as i can and will post the result.
Sent from my SGH-T989 using XDA Premium App
4me it was a driver problem ...
drivers in download above should be good versions
if you are using win7 go to device-manager select everything like lg... or android... and uninstall with deleting drivers
uninstall lg suite, lg drivers, you can also clean up windows i.e. with glary utils, reboot, install drivers from above, connect phone AFTER installing all the driver-packages.
you can also try another usb-port
edit: maybe also a Security-Kit is blocking like Comodo Internet Security because it uses a sandbox for execution of unknown software.
Sadly I still get the same message in kdz with the driver prwnd (thanks for trying).
- I made sure that I uninstall everything related to lg and its driver
- Installed new driver, restarted.
- Connect the phone on download mode (volume down + plug in usb), the usb port is from the back of my comp, directly to mobo.
- Still no hope
I believe I read somewhere state that, if the phone can enter download mode, it's not fully bricked and I hope I can fix this phone for my friend...
Any help would be appreciated.
Re
Do you have access to fastboot or recovery??? POWER + HOME or POWER + CAMERA BUTTON ????
And one more thing which os do you use??? WIN 7 X86 or X64 or WIN XP???
If you don't have access to fastboot or recovery just reply which os do you use...
Thanks for the reply and sorry for the late response, i still have some hope
I dont have access to fastboot or anything, all i can get is either boot logo or download mode
im using win 7 64 bit
Sent from my SGH-T989 using XDA Premium App
Re
Go to someone who has WIN XP 32 bit install drivers an try all that stuff again i think that should do it... if don't send a pm....
I cant find anyone still using win xp 32 bit for now
Sent from my SGH-T989 using XDA Premium App
A few days ago I was running xodus rom and the battery was at about 50% and the phone instantly shut off and I have not been able to get it back on since. I have tried the method of letting it sit for 12 hours and then charging for 6 but that didnt work. I have been trying the unbrick methods on the forums here but I cant get any of those to work. The problem is when I get to the step where I run the recovery tool and press start, nothing happens. I am running it as admin. Ive tried different ports on the computer and even running a vm of a different version of windows but nothing. Any help with this would be much apreciated. I can even teamviewer with someone if theyre willing to take a look at what I mean.
Edit: I am getting this on the recovery tool:
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_main0.bin: OK
userdata.img: FAILED open or read
userdata_64G.img: FAILED open or read
rawprogram0.xml: FAILED
rawprogram0_64G.xml: FAILED
NON-HLOS.bin: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED open or read
cache.img: FAILED open or read
persist.img: OK
recovery.img: FAILED
system.img: FAILED open or read
ONEPLUS 2 bricked
i am also facing same issue .
stevecaboose said:
A few days ago I was running xodus rom and the battery was at about 50% and the phone instantly shut off and I have not been able to get it back on since. I have tried the method of letting it sit for 12 hours and then charging for 6 but that didnt work. I have been trying the unbrick methods on the forums here but I cant get any of those to work. The problem is when I get to the step where I run the recovery tool and press start, nothing happens. I am running it as admin. Ive tried different ports on the computer and even running a vm of a different version of windows but nothing. Any help with this would be much apreciated. I can even teamviewer with someone if theyre willing to take a look at what I mean.
Edit: I am getting this on the recovery tool:
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_main0.bin: OK
userdata.img: FAILED open or read
userdata_64G.img: FAILED open or read
rawprogram0.xml: FAILED
rawprogram0_64G.xml: FAILED
NON-HLOS.bin: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED open or read
cache.img: FAILED open or read
persist.img: OK
recovery.img: FAILED
system.img: FAILED open or read
Click to expand...
Click to collapse
Are u referring to the qualcomm recovery tool? I semi bricked mine yesterday and took me a while to figure out how to get into that mode. I even tried on 3 different PCs to get the drivers working as i got it messed with ADB then OnePlus drivers. Into consideration too that 1 of the machine was in windows7, two on 8.1 so need to go to the driver signature disable thingy. Lucky me, i have my screen on as i still have like 70% battery in it. not sure bout yours.
If youre able to charge and boot it to at least fastboot or get the LED blinking to show it has battery to boot, next step is just to play around and get the qualcomm recovery mode working well. Dont give up man. you can do it.
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21
try this. This is slightly modified version. This worked for me after trying it for three times.
(Also flash H2OS, because O2OS doesn't install when you get up to recovery.)
Turns out that my phone shut off and was not able to recover with the qualcomm tool because of hardware damage.