I have tried to update my droid with update.zip. It failed with a weird message, smth like could not update modem (the phone was ok before)
Now i got mass of downloaded files, like rsdlite and two sbfs
VRZ_A956_2.4.33_1FF_01.sbf and DROID2WE_X6_2.4.29_FULL.sbf
both stop at 100% and i get a popup message telling new device is found QHSUSB_DNLD or something like that. I've checked ALL motorola drivers (5.2.x update) for subject of this string with the hardware id of PID_9008 but i have found nothing! It just simply DOES NOT exit!
I have found proper dirvers, it looks like MSM6600 default drivers. So when RSD switched to BP mode it won't see anything, tho i get the drivers running and in the device manager i clearly see smth like Qualcomm ..Download 9008 but the RSDLite keeps searching and fails to process - Phone disconnected...
So, maybe anyone here got the same problem or has a clue of how to get rid of bootloader screen? Wiping cache, erasing to factory does nothing, I don't just get what this rsdlite wants? which device appears when it switched to BP download mode? Isn't it the one i get?
I have tried 3 PC, 2xXP and 1xWIN7 so it's NOT the PC's fault.
RSDLite is 5.4.5 - latest, the drivers - latest!
Please guys, need your input!
EDIT: I have joined only 3 files: CG05, RDL1.smg and RDL3.smg to test faster - it will immediatelly switch to BP mode, so no need to erase or reflash whole device. Will upload to rapidshare if anyone wants to test.
jinns said:
RSDLite is 5.4.5 - latest, the drivers - latest!
Please guys, need your input!
Click to expand...
Click to collapse
This nice manual, does not help either
http: //droid.koumakan. jp/wiki/SBF
Try http://www.droidforums.net/forum/droid-2-global-hacks/170060-tool-ezsbf-d2g.html — this is a bootable CD image (which can be also used with a USB stick) that performs the task.
Note: 2.4.29 is the recommended (at least by me, after quite some experience) image; it's best to update to 2.4.330 OTA.
Thank you.
But here is the fact:
"If you already use Linux as your OS of choice you can flash with your current system, grab sbf_flash and the SBF file then simply cd to where you put the files, then:
chmod +x sbf_flash
./sbf_flash filename.sbf"
I have Linux Ubuntu and i have tried it already. No use.
“No use” doesn't quite describe the problem, to be honest.
Gasai Yuno said:
“No use” doesn't quite describe the problem, to be honest.
Click to expand...
Click to collapse
Ok it will flash it flawlessly, no problem. But it does not flash the BP module. It just ignores the fact that in package there are AP and BP firmwares, so sbf_flash will flash only the AP part.
plz help
i have same problem ...................help plz...
Is there any solution for my droid
plz help me friendz i need help
shahjeee said:
plz help me friendz i need help
Click to expand...
Click to collapse
I am not yet able to help but at least i can give an answer that will probably point into the right direction.
What actually happens:
Droid 2 Global has 2 CPUs : OMAP (AP) & Qualcomm(BP)
At some reason the update via sdcard or failed sbf flashing in BP mode erases the BP content and fails to write the new data into the nand/emmc(whatever), so Qualcomm will jump into Emergency download more each time the RSDLite will try to switch to BP mode, thus you will see the QHSUSB_DLOAD device (COM PORT actually) that's it.
The chip is CDMA1x QSC6085 so it barely has any security on board, making it possible to use any Qcom flasher compatible with the chip and + ramdownloader.
What to do:
Get a qualcomm flasher (PSAS or other tools)
Get a ramdownloader (boot loader) for the 6085 (can be found, for older phones)
Extract the original SBF file content and use the *.mbn files and flash it.
This way may help.
Thank you alot of you reply me can you explain me step by step and software links ,................................thanks..
i have mac pc and windows both
Hello,
I have a new Lenovo A606, that came with a strange ROM (IMEI not recognized, some weird WIFI setup) from 2014. I was able to set it up and correct the problems (thanks to google), but I still had some language issues (the Lenovo Apps including dialer, contacts, sms, etc… were English only). I was able to root it fine, and no working problem.
I decided to install a clean stock ROM, ROW: the A606_USR_S036_1502271022_V3_MP_ROW that is more recent and fully supports multilanguage.
I took a PC with Windows XP, and installed the latest SP Flash Tool, following a tutorial.
I was able to install android adb drivers and the MTK driver from the ROM image. The phone was showing in the devices, then was disappearing, then showing again… I had an error, but then I tried again with the option to update the firmware, and the Flash Tool reached the end and said it flashed succesfully.
Problem: after that, the phone was totally bricked. It would not start at all. When I plug it on the PC, it shows sporadically a device called "VENDOR 0E8D - communication" that disappears very quickly. I cannot flash it again. I just lost my brand new phone…
I tried with SP Flash Tool, and Flash SPMDT, with different ROMs, CN only, ROW, different versions… But nothing. It always says that Flash failed. Even when the phone is not plugged, I have an error with Flash SPMDT, with all ROMs, saying that (1)COM ports number is repetitive or invalid, or (2) Brom and preloader have the same comport number! and it asks me to modify them in INI file or scan again. Of course, scan fails, when I plug the phone pressing vol up + vol down (only way to make the phone recognized by the computer without a battery), the progress goes to 100% then either stays stuck there, or says it failed. SP Flash Tools gives this error: 'BROM ERROR s_ft_enable_dram_fail (4032)'
I tried several drivers, to clean drivers with usbdview, I tried several versions of SP Flash Tools… I don't know what to do anymore. I hope that Lenovo has a warranty and that they could flash it back to normal.
I don't know if it is a problem accessing the META mode on the phone, or bad roms… I tried on one computer with XP, and another with Windows 8.1, and the problem is the same.
ANY HELP would be appreciated, thank you!
Hi, thank you for using XDA Assist. It sounds like you've tried everything possible. Since it sporadically shows up on your pc try a different USB cable. If that doesn't work then I think it is bricked and you'll have to check with whomever you purchased the device from to see if they can fix it.
Thread closed.
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Tiic said:
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Click to expand...
Click to collapse
How your device got bricked?
Which recovery tool you tried?
Mr.Ak said:
How your device got bricked?
Which recovery tool you tried?
Click to expand...
Click to collapse
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Tiic said:
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Click to expand...
Click to collapse
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Mr.Ak said:
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Click to expand...
Click to collapse
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Flashing 8974_msimage.mbn nin a loop.... you're not the only one with this problem. I couldn't find a solution to this problem so far. Have tried fresh installs of Windows XP and Windows 7 and drivers installed in Test Mode without success. Please report back once you could figure out what's wrong.
Tiic said:
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Click to expand...
Click to collapse
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Mr.Ak said:
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Click to expand...
Click to collapse
Just redownloaded the tools and tried again.
Still the same issue, i also tried the color os toolkit like you suggested.
I have the same issue too, keep installing 8974_msimage.mbn again and again.
I'm still open for sugestions since the issue is still there
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
kthejoker20 said:
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
Click to expand...
Click to collapse
Although it is correct that you must run it as admin, this isn't the issue at all. There are phones that appear to be broken beyond the point where you can fix it with software.
MrBrainstorm said:
Although it is correct that you must run it as admin, this isn't the issue at all..
Click to expand...
Click to collapse
Yep, i always run tools like this as admin, the issue is something else in this case, but i wouldn't know what exactly
I may have found a solution/work-around to the problem described (in case anyone's still trying to unbrick a OPO after all this time). I must warn, however, that I really have no idea what I'm doing as I'm new to all of this, and have blundered through with no real understanding of what's going on, so pay heed at your own risk. It uses Qualcomm's QFIL program and Zyxxeil's OPO unbricking tool. I want give detail in describing the steps involved, so this will be fairly long.
***background***
My 64GB OPO has for the past couple of months almost always failed to get past the first 6-7 seconds of booting, and powered off before reaching the Cyanogen animation. It did the same when booting into fastboot and recovery, and at some point it stopped being able to access recovery at all. Very rarely it would boot, but pressing the power button while it was on would cause it to crash a few seconds later. I discovered that it would consistently boot properly if volume up were tapped while holding down the power button before it vibrates and the OnePlus logo appears, but this fix simply stopped working recently, and so it became impossible to turn the OPO on. Before giving up on it, I decided it would be worth trying the hard unbricking tool based on the ColorOS installer by Zyxxeil. However, I had the problem where the tool continually repeats the step of flashing 8974_msimage.mbn without progressing any further, to which nobody ever seemed to find a solution. I may have found a way to get around the problem, however.
Even though the procedure seems to have worked, the phone still shuts down after a few seconds as it did before (so I suspect my device has a hardware problem, possibly with the power button, and there's nothing that can be done for it). This means that I can't confirm that the fix actually works, but only that it appears to have worked. What it did was:
1) unbricked the phone - it probably wasn't even bricked before, but it definitely was after the installer hung on 8974_msimage.mbn ; it wouldn't respond to the power button at all afterwards. Applying the workaround allowed it to show signs of life again.
2) installed the COS11 fastboot. I'm not sure and can't tell whether the rest of the OS is there or intact, but the fastboot logo has changed from the newer small one to the bigger one from older versions.
***the problem***
The standard method for dealing with a hard-bricked OPO is to use the ColorOS tool as described in the "[GUIDE] [UNBRICK] Unbrick Oneplus One" thread and then flash Cyanogen, or to use Zyxxeil's tool which goes straight there. A common issue in both is that after pressing start, the tools repeat the step of flashing 8974_msimage.mbn , seemingly disconnecting the phone each time, and never progressing beyond that. This happened to me as well. This will happen if the tool is not run as an administrator, but for some people the same problem is seen even if it's run as an administrator. To the best of my knowledge, nobody has posted a solution to this problem, but some have suggested using alternative methods such as using QFIL (which I have gotten to work) or MiFlash.
***potential solution***
From what I understand, QFIL does the same thing as the unbricking tool, only not automatically. I directed it to use the files provided by Zyxxeil's tool, and it was then able to do something that unbricked the device as described above. This is what I did: (all on Windows 10, *not* using the original cable)
Required files:
1) Obtain the Qualcomm QDLoader driver. I used the the Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64 driver from Zyxxeil's tool's thread (page 5, #48).
2) Download Zyxxeil's tool. I used the 64GB version. Extract DRIVER.iso and run setup.exe as described. I'm not sure whether this actually did anything and presume manually installing the driver in 1) overrides this, but I'm including this for completeness.
3) Download QFIL version 1.0.0.2 . I originally used 2.0.0.5 , but this did not work (it produced the error "unable to read packet header. only read 0 bytes", to which the recommended solution was to use an older version). This can be run from the extracted folder. Open it once, and then close it again - it seems not to behave properly the first time it is run.
Preparation:
4) Create a new folder, for instance on the desktop, and give it a short name. Copy and paste (or just move) the contents of the "OnePlusRestoreTool" folder from Zyxxeil's tool into here. This step is because QFIL supposedly doesn't like long folder names or locations (I'm not sure whether this is true or not but there's no harm in making sure).
5) Install the QDloader driver: (the PC may need to be disconnected from the internet for this stage, I think Windows may try to automatically download and install incorrect drivers)
>Open device manager, then plug the OPO into the computer. It should come up after a few seconds under "Ports (COM & LPT)" as something like QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Mine originally showed up as "Quectel QDLoader 9008". If it comes up as a malfunctioned device ("Unknown USB Device") under "Universal Serial Bus controllers", try holding the power button on the OPO down for a few seconds, or holding it down for a few seconds at the same time as volume up. If it's still not recognised, try rebooting the PC and repeating this step.
>Right click on the device as it appears in device manager, select "Uninstall device", tick the box saying "Delete the driver software for this device", and click on "Uninstall".
>The OPO will disappear from device manager. Unplug and then replug it into the PC, and after a few seconds it should be recognised again, perhaps as "Unknown USB Device" again, requiring the same procedure as above. It should now show up as QHSUSB_BULK under "Ports (COM & LPT)"
>Right click on the device and select "Update driver", then "Browse my computer for driver software". Paste in the file path for the folder containing the driver as downloaded above, which will be called "20561190_ed08f7139a2028da454a6668162f44ac311facc0" if using the driver specified above. Ensure "Include subfolders" is ticked, and click on Next. This should install the driver, and because it's signed, it shouldn't present problems often encountered in this stage. Your device should now be called "Qualcomm HS-USB QDLoader 9008", with (COM#) after it.
Fix:
6) Restart the PC, leaving the phone plugged in. Open device manager again. At this point, if it is detected as a malfunctioned "Unknown USB Device", do not try to remedy it as described above - leave it as it is. This is exactly what happened in my case.
7) Run QFIL.exe as an administrator. I don't know whether this is actually necessary to run as an administrator, but seeing as problems arise in the normal methods from not doing so, it seems sensible. If the device is listed as "Unknown USB Device", then QFIL should say "No Port Available".
8) In QFIL, click on "Browse" in the "select programmer" section. Navigate to the folder where the contents of Zyxxeil's tool were copied/moved to, and open "prog_emmc_firehose_8979.mbn". Lower down, click on "Load XML", which should give you three files to choose from. As I couldn't fully boot my OPO afterwards I don't know which one is most appropriate, but I have tried the procedure with each and it worked for all of them. Perhaps start with rawprogram_unsparse.xml and if that doesn't work try the other two. Click Open, then select patch0.xml , then click Open again.
9) Paying attention to the QFIL window, hold down power+volume up until the text changes from "No Port Available" to "Qualcomm HS-USB QDLoader 9008 (COM#). Incidentally, this will also cause the device to change from "Unrecognised USB Device" to "Qualcomm HS-USB QDLoader 9008 (COM#)" in device manager. I believe that this step starts "Qualcomm's debugging mode" as explained in Zyxxeil's thread, and this is necessary for the process to work.
10) Click on "Download" (below "Load XML"). QFIL should do its thing, and if nothing has gone wrong the phone might be unbricked at the end of the process. Disconnect from the PC and see if it works.
In my experience, where this step did not work it gave one of two errors:
"unable to read packet header. only read 0 bytes" - this happens on the newer version of QFIL, which is why I used the older one.
"unable to download flash programmer using sahara protocol" - this was the troublesome one. I believe it means that the phone is not in Qualcomm's debugging mode. This would probably be the case if, for whatever reason, the PC recognised the phone immediately as Qualcomm HS-USB QDLoader 9008, and so it wasn't necessary to hold power+volume up for the PC to recognise it properly. In my case the program ran properly the first time but was interrupted because I hadn't transferred all of the right files to the target folder. After I had done this and tried again, it gave this error. I fixed this by holding down power+volume up, while the device was recognised, until the PC made a sound indicating something had been plugged in. The next attempt to download was successful.
If the procedure doesn't work properly, it might also be worth using one of the other two XML files mentioned in step 9.
*** ***
Anyway, after hours of searching and trial and error, this unbricked the phone, with it becoming responsive once more to button presses, despite still having the original problem of powering down during boot. It seems to have the CM11 fastboot as expected, and I was able to have my PC recognise it in the short time it stays on using fastboot devices. Other than that, I'm afraid I don't know how successful this was, or how successful it would be for other people. I hope this is useful nonetheless!
hi follow this guide https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I have found some nice web site and tools, hope they can help Moto users like us.
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process.
Get Moto serials Stock Firmware from motostockrom via https://motostockrom.com/
Get RSD Tool from https://rsdlitetool.com/
#How to use RSD : https://androidmtk.com/use-rsd-lite-tool
Get LMSA Tools from Motorala official site https://www.motorola.com/us/lenovo-motorola-smart-assistant
#About LMSA tool: Lenovo Moto Smart Assistant (LMSA) tool, can help diagnose and resolve issues on your Motorola phone.
#PC client is provided for Windows.
XT1900-1 is missing for Google Fi. But overall an interesting set of resources. Thanks for sharing.
doesnt work on my pc says all the time i need to restart my computer
Failed to switch to fastboot mode
I tried to re-install my stock rom with it, and i got the message on status "Fail to switch to fastboot mode". But i'm already on fastboot mode. I saw someone saying i need the original cable, and i using it.
I'm not really sure what to do, i have my phone bricked right now, any help would be welcome.
@MotoX4
Viics said:
I tried to re-install my stock rom with it, and i got the message on status "Fail to switch to fastboot mode". But i'm already on fastboot mode. I saw someone saying i need the original cable, and i using it.
I'm not really sure what to do, i have my phone bricked right now, any help would be welcome.
@MotoX4
Click to expand...
Click to collapse
Check if your drivers are properly installed or not by using the following command:
fastboot devices
this should give you a list of devices attached to the PC (recognized by the OS/ adb)