*** I've been receiving many requests and PMs from members asking to help them unbrick their device. Please note that I no longer own this device (and even if I did I would not purposely brick it just to reproduce your problem), therefore I am unable to help out beyond this tutorial. ***
Hello,
First some background and credits:
There are a few ways to brick a phone. Sometimes it's lack of experience, sometimes it's an accidental thing, sometimes there just isn't an explanation for what went wrong... (share your experience here, if you wish). For me, I owned my OPO for about 4 hours before things went wrong. First thing I did was I rooted it and installed TWRP. After creating a nandroid backup of the stock image I installed my favorite custom ROM and restored all my apps with TiBu. Everything was great and configured just the way I wanted it. I then wiped my old phone (Nexus 4), installed a new ROM and got it all ready for my wife. She was so excited to get rid of her GNex and move up to the N4. But then, for whatever reason, I opened an app on my OPO that I used to manage, download, and install kernels with. It came up with "there is a new kernel update!" and I instinctively clicked on "Install". 10 seconds later my phone was bricked. Nothing came on the screen, no fastboot, no recovery, nothing to boot to, no way to send data to and from it. The second the screen went black and the phone became lifeless I got that wretched feeling in my gut as I realized I just flashed a N4 kernel on my new OPO. Restoring the kernel management app with TiBu made it act like it's still running on my old phone, and in my excitement I didn't take a second to think things through...
I received a bit of consolation when a quick XDA search revealed that I am not the only dumbass to brick his phone this very way. I joined forces with some pretty smart and desperate people and tried different things, all described in the following thread: http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696. Unfortunately it took us what seemed like many long weeks to figure it all out. Well, in the end a solution was found and I documented it in the the following post: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136.
This was a few months ago, but I recently noticed many people continue to search for these directions and have problems finding them hidden among many pages and other threads, so I've decided to put this stand alone thread with these, now updated, directions.
Let me get one more thing straight, for the record. I did not find the way to unbrick the OPO. In fact I wasn't even the very first one to do it. It was a collective effort of few people who tried many different approaches and ideas, and I eventually documented these steps for others to follow. Being said, the following people deserve credit as well: @os_man, @rezor92, @Mnt-XDA. If I am forgetting other significant names and efforts, I apologize.
***CAUTION***
The following instructions are for hardware bricked devices ONLY and will not work on soft bricked devices. To determine whether your device is soft or hard bricked, click the button below:
Hardware brick
A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB. You might have a bricked OPO as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.
Software brick
Please do not attempt to use these directions if your phone is soft bricked. A software bricked OPO is one that might be stuck in a bootloop, but has a working bootloader, recovery partition, fastboot, or adb. If you press the power button and images appear on the screen and you are able to enter fastboot mode (Power + VolUP) or recovery (Power + VolDOWN) then your device is soft bricked. This thread does not encompass soft brick recovery, the instructions below do not apply and will not work on these phones. Consult other threads for help on soft bricked devices.
If based on the above explanation of differences between soft and hard bricks you determined your device is hard bricked, here's what you will need to do...
1:
Download Color.zip from (mirror needed).
After downloading, unzip the archive on your computer.
2:
Next, you need proper Windows drivers. There are architectural differences between Windows XP and Windows 7/8, so follow the directions below that pertain to you. One quick note about the drivers: the installation and process is very simple and straightforward on Windows XP (I also tested successfully on Windows 2003), but proves to be quite a challenge when running on Windows 7 or 8. Over and over people report issues when attempting the unbrick procedure on Windows 7/8, some have more luck than others. Being said, if you have access to a Windows XP computer, I highly recommend that you use that. If you have no choice but to use a Windows 7 or 8 computer and have problems, please share them here and read others' experiences.
So first, by now you probably tried a few different things to fix your phone and you've already installed some drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried so far and use the ones listed below. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then:
2a:
Windows XP users:
You are in luck, driver installation is straightforward. Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.
2b:
Windows 7 and Windows 8:
These operating systems block unsigned driver installations by default. Follow these steps (thanks @nag4pl for testing these):
Download and extract these Qualcomm 2012 drivers: (mirror needed).
Connect your bricked phone and let Windows do its thing.
Now something very essential you need to do here is to execute two commands to allow you to install unsigned drivers for QHUSB_BULK. Click on Start Menu > Type cmd.exe > Right Click and Run as Administrator.
In the CMD window type in the following commands (hit enter after each):
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Code:
bcdedit.exe -set TESTSIGNING ON
After both the commands should run successfully, restart your computer.
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software. For driver software location provide the path where you have extracted Qualcomm 2012 drivers you downloaded and make sure 'Include Subfolders' is checked. Proceed through all the installation prompts ignoring any warnings.
3:
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.
4:
Optional Steps:
Your phone is no longer bricked. You now have a few options to get back to stock. The easiest way is to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can flash an image manually by following directions from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541. Download the proper image zip and after extracting it, run the following commands in fastboot mode:
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue.
Good luck! Share your experience here and let me know if I can improve this thread.
Please click the Thanks button if you found the above guide useful.
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
did this and it finally worked but still i have unknown baseband and no imei.........flashed coloros using the msm tool and rom goes into a bootloop......tried all the ways with no luck....even flashed the persist.img......still no luck.......my last hope is claiming warranty and act like a noob in service center.......will they get to know taht i unlocked the bootloader?
mysterio619 said:
did this and it finally worked but still i have unknown baseband and no imei.........flashed coloros using the msm tool and rom goes into a bootloop......tried all the ways with no luck....even flashed the persist.img......still no luck.......my last hope is claiming warranty and act like a noob in service center.......will they get to know taht i unlocked the bootloader?
Click to expand...
Click to collapse
You should be able to boot to fastboot now. From there flash the cm11s image. I believe that "fastboot flash sbl1 sbl1.mbn" will fix the imei issue.
Also, unlocking bootloader does not void your warranty. Not with OPO.
netbuzz said:
You should be able to boot to fastboot now. From there flash the cm11s image. I believe that "fastboot flash sbl1 sbl1.mbn" will fix the imei issue.
Also, unlocking bootloader does not void your warranty. Not with OPO.
Click to expand...
Click to collapse
Tried it......still no imei
mysterio619 said:
Tried it......still no imei
Click to expand...
Click to collapse
Just to give one last try, flash color os modded zip from relic, i used 2.0.43 purezip and it gave me back my imei. Had the same issue as you last week. Be sure to flash TWRP 2.8.4.1 first and then flash color os.
Legit method.
Worked for me 2 weeks ago!
unbrick oneplus one, oppo 7
Hi there my friend, i had many works about unbricking solutions, a few of you know that, i have much easier and faster ways now, tested many times before i decided to share with you, it will be a long topic ( and my brain is messed up to sum them up clearly), as soon i can think clearly again, i start to write them, till then,
greetings from Istanbul to all geeks around thw world.
Ps: including restoring imei's if they got lost during this process.
Ps2: just a quick info abou imei, if your imei is "invalid" , this means your modem.bin (NON-HLOS.bin, baseband) is not inadaptable with your rom, just try flashing the right modem ( from fastboot), your imei will be back.
Ps3 : This will lead us to unbrick many Snapdragon's out there , not only oneplus one's or oppo's.
I had to use this tutorial some days ago.
There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.
Tutorial to install the driver:
1. Open your device manager (Start - right click on computer - properties - devices manager)
2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
michaeldepotter said:
I had to use this tutorial some days ago.
There is also a modified .zip where the tool from OPO flashed CM11s instead of ColorOS.
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I had many driver problems and i had to use this driver from qualcomm so my win7 could recognize the phone.
Tutorial to install the driver:
1. Open your device manager (Start - right click on computer - properties - devices manager)
2. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
3. Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
Click to expand...
Click to collapse
Hi, Dropbox link for drivers seems to be wrong.. could you please update correct one.. I am in very much need of it! pls!!
nag4pl said:
Hi, Dropbox link for drivers seems to be wrong.. could you please update correct one.. I am in very much need of it! pls!!
Click to expand...
Click to collapse
Sorry. Here is the link:
https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
Sent from my A0001 using XDA Free mobile app
michaeldepotter said:
Sorry. Here is the link:
https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you.. Troubleshooting my phone now..
may i ?
http://www.androidbrick.com/?wpdmdl=2599
Back from Brick!!
First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.
Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz
All you need to do is:
1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
2. Extract to some folder under C: or whichever drive you prefer.
3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.
Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
4b. Now type below command
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
>hit Enter
bcdedit.exe -set TESTSIGNING ON
> hit Enter again
4c. Both the commands should run successfully, then restart your computer.
These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.
After machine booted back to desktop
5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
7. Right click on the same > Update Driver Software > Browse my Computer for driver software
8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
"C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.
Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.
I have attached the screenshots for the same just for confirmation.
SuccessfullDriver - showing successful installation of driver
FlashInProgress - showing tool flashing the system image
FlashSuccess - showing green row indicating successful flash.
Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!
nag4pl said:
First of all Thanks a lot to @netbuzz(for such a life saver guide on unbricking 1+1) and @michaeldepotter for providing link to download appropriate drivers.
Here is some good news by my findings and can be a quick help for those who do not have or can't get XP. You can use Windows 7 itself for the process mentioned by @netbuzz
All you need to do is:
1. Download drivers from link provided by @michaeldepotter : https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0
2. Extract to some folder under C: or whichever drive you prefer.
3. Connect your bricked phone after pressing Volume Up and Power key (make sure phone vibrates once)
4. Now that QHUSB_BULK should be detected and Windows will eventually try to download drivers from update, which you can skip and close the window.
Now something very essential you need to do here is to execute some commands so that you will be able to install unsigned drivers for QHUSB_BULK.
4a. Click On Start Menu > Type cmd.exe > Right Click and Run as Administrator (make sure you are running cmd as admin)
4b. Now type below command
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
>hit Enter
bcdedit.exe -set TESTSIGNING ON
> hit Enter again
4c. Both the commands should run successfully, then restart your computer.
These steps are to disable driver sign verification. You must proceed to next steps only after above steps executed successfully.
After machine booted back to desktop
5. Now Open Device Manager by Start > Run > type "devmgmt.msc" and hit enter
6. You should be seeing ugly yellow warning under other devices for QHUSB_BULK.
7. Right click on the same > Update Driver Software > Browse my Computer for driver software
8. Now under driver software location, provide the path where you have extracted drivers which you downloaded from step 1. For me it was:
"C:\Users\Arjun\Downloads\Qualcomm 2012\fre\Windows7" - Remember to provide path only till windows 7 and make sure 'Include Subfolders' is checked.
9. Click next, and it should install driver for QHUSB_BULK. Click on Install Driver if you get any warnings.
Now your driver set-up for QHUSB_BULK in Windows 7 is complete and now you may proceed with the steps to run Msm8974DownloadTool as provided by netbuzz.
I have attached the screenshots for the same just for confirmation.
SuccessfullDriver - showing successful installation of driver
FlashInProgress - showing tool flashing the system image
FlashSuccess - showing green row indicating successful flash.
Once again, thanks a lot for all the guide and help. Hope this quick guide helps some one in need!!
Click to expand...
Click to collapse
Thanks for this Win7/8 workaround. I'll be adding your info to the OP.
Finally Unbricked mine...Drivers resolved on Win 7
netbuzz said:
Second note about drivers is that I had the worst time trying to get things to work on my Windows 7 computers. Both Windows 7 and 8 block unsigned driver installations by default. I've tried overwriting these settings in Windows and spent half a day messing with it, and I never got things to work properly. At first all looked good to go, but then latter steps were failing. You might have a better luck getting drivers to work on Windows 7 or 8 (I've heard some people did it), but if you have access to a Windows XP or 2003 machine, try it first, it should save you some major headache.
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Click to expand...
Click to collapse
I have used the override tool for certificates: DSEO - Driver signature enforcement overrider
to allow the unsigned drivers to be used and it worked like charm on windows 7 64 bit.
Also, I used the additional Qualcomm 2012 drivers and not sure which one might got picked in that mess :cyclops::cyclops:
Thanks!!
:good::good::angel::angel:
nevermind!
Well I managed to hardbrick my phone. I am download the ColorOS file from Mega at the moment. It's downloading at 30KB/s and will take around 6.5 hours. Is there any other source to download it from ? Thanks !
Also, about the driver ...
While I wait on the colorOS to download I want to clarify one more thing about the driver.
According to the screenshot of @nag4pl the driver should show as Qualcomm USB diagnostic 9006, while for me it shows as Qualcomm HS-USB QDloader 9008. Is this going to be an issue ?
This is what I did. I uninstalled the default driver that came with windows 7. After that it failed to install the driver provided in this forum because it kept saying that device descriptor failed. I rebooted the phone several times and changed the USB ports and eventually windows detected it but AGAIN with the windows driver even though I had checked the option to delete the original driver while uninstalling it. Through the update driver option I managed to force it to install the unsigned driver.
Now I can see both the drivers under the update drivers option. Interestingly the default driver is a version ahead of the unsigned driver provided in this forum.
My only concern is that I see a different driver name compared to the one posted by @nag4pl
Thanks! Very useful for me!
That shouldn't be a problem. Not sure if that is specific to region, mine is India version phone.. Can some one clarify on this?
Related
I am running Windows 7 x64 I have no idea if following this guide on another operating system will work, this is just a step by step of EXACTLY how I did this, Not to say this is the only way. I have tested other methods and I have put in different variables and I have successfully gotten it to work several times in a row doing it this way while following jp4756's guide. I am sure this is not the only way to accomplish root, however this worked for me perfectly. PLEASE don't skimp out on any step. There is no shortcut here just follow the steps and jp4756's guide to the TEE!!!
Step 1.
Uninstall pdanet/htc sync/ any other thing you installed to get all this to work before
Unplug phone from computer usb cables and have phone powered on and in settings menu
Step 2.
download USBDeview(install it) easy to google it
download HTC SYNC(do NOT install it yet) for mytouch slide easy to google it
Step 3.
While in settings menu go to Application
go to Development
and check the box USB debugging
Step 4.
In settings go to Connect to PC
touch Default connection type and choose Sync
At this point you have the phone not plugged in, you have the setting on the phone changed, you have dowloaded usbdeview and installed it, and have htc sync dowloaded
Step 5.
Start USBDeview(some may have to right click the exe and run as administrator) and delete all android drivers and mytouch drivers, anything relating to android
Install HTC SYNC and let it completely install
Step 6.
Plug phone into computer and let the computer auto install drivers etc...
Step 7.
turn the phone off. Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button ) After it does its little thing your computer will beep and start auto installing drivers and stuff
Step 8.
If everything has gone according to plan in Device Manager it will show Android 1.0 or w/e with a exclamation point. Right click on that and choose Update Driver Software
2 options pop up choose Browse my Computer
then choose Let me Pick from list...
a list will appear giving lots of choices
choose Android Phone should be the first choice that says android....
then 3 options will appear, choose the 3rd one that has Composite in it and choose okay.
Step 9.
Now select Recovery from the bootloader menu
after it is done doing its thing completely 2 things will happen
1) In device manager you will now have something under disk drives
2) USBDeview a new driver will pop up at the end of the list, something like this:
Port_#0004.Hub_#0004 T-Mobile myTouch 3G Slide USB Device Mass Storage Yes No No No E: HT05RPS05696 6/16/2010 4:00:58 PM 6/16/2010 4:07:35 PM 0bb4 0ff9 08 06 50 USBSTOR USB Mass Storage Driver USBSTOR.SYS USB @usbstor.inf,%generic.mfg%;Compatible USB storage device
Step 10.
This new driver to appear shows Yes under the Connection column. This needs to be disabled. Right click on it and choose Disable Selected Device
after about 10 seconds it should no longer say Yes under connection column, if this does not happen then you are not running it under Admin.
Okay so now you are literally almost freaking there.
Step 11.
Now basically all you have to do is follow jp4756's guide starting with step 5. Im going to assume you already understand steps 1-4 in his guide. And you already have the package listed in his guide as well. You have already put those files where they belong
Step 12.
Okay so we are basically following his guide now. first things first
5. run the update.zip it will fail(MUST DO)
6. now in cmd type adb reboot recovery (don’t press enter)
7. in the recovery hit reboot system now( once it starts rebooting run that command rapidly untill back into recovery) <--- Basically while the phone is rebooting you are just hitting up arrow enter up arrow enter up arrow enter up arrow enter in CMD. You will know when you can stop when the CMD freezes for a sex, computer makes beeping noises and the phone reboots basically. It is headed for recovery and we must switch our command now
8.type adb devices(if it says nothing repeat the steps, if it says offline unplug it and then plug it back in, if it says recovery your fine) <---- Basically after you know its headed for recovery you change command to adb devices and you repeat previous procedure, up arrow enter up arrow enter up arrow enter etc.... I did not use loop, i did this all manually.
This may take a few tries, if it does not show offline then go back to step 6 rinse and repeat. You go back and forth just a few times and you will have it. Literally within about 3 tries you should accomplish the annoying goal of having offline stay there.
My job is done, follow guide and continue on your quest for root
There is no guarantee this will work for everyone. I am not claiming that this is 100% Im just giving an explanation as to how i got it and what might have been causing everyones trouble. Results may vary
Thank you to all the devs who made this possible and jp4756 for his wonderful guide
Wow that is just way to much stuff there...
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
Also It just might be your computer so I would try and use a different one if you can.
jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
Sorry that we all can't be as cool as you jnight666, but some of us are having real problems with no apparent explanation. I am an IT professional with access to every kind of computer used in the modern world, and trust me, I've tried all the ones that apply. Rubbing it in our faces that it was just so easy for you is just rude.
THE DRIVER MAKES NO DIFFERENCE FOLKS. IF YOU CHANGES DRIVERS AND THEN IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON MANY DIFFERENT DRIVERS.
THE CONNECT TO PC SETTING ON THE PHONE DOES NOT MAKE A DIFFERENCE IN FASTBOOT/RECOVRY FOLKS. IF YOU CHANGED THIS SETTING AND IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON VARIOUS DIFFERENT SETTINGS.
That being said, this didn't solve mine. I still cannot root.
And Yes, my cap locks was on purpose.
Okay, please dont come in here and start telling me how my method is wrong. I already stated there are other ways to accomplish it. I had already stated that this isnt 100%. I am merely offering an exact procedure that i duplicated SEVERAL times, with it working for me every time. If this isnt how you accomplished it then pls, theres no reason for you to be in this thread posting negative comments.
With that said fermunky, did you follow the procedure to the tee? - btw im not assuming anything so please dont take it personal. Im just trying to help ppl : )
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Completely understandable, and definitely no disrespect to you or anyone here
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
And if anyone want to say anything about this I'll go load up my Pentium III machine and see if it works on that...
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
3 different computers 3 different op systems installed uninstalled drivers different programs etc...some phones are hard to root its a ambiguous situation
Yeah sorry I wasn't trying to be rude.
I was just trying to be helpful, sorry if it came out that way...
I also have the loop not working issue but i usually only happens once or twice..
I feel your pain I had trouble with the push Update.zip part of this thing and I was trying it for hours...
I was just trying to tell you what worked for me...
If you tried different computer and still no luck then im guessing its the Phone that is the issue or the USB Cable...
gofizzle said:
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
Click to expand...
Click to collapse
You definitely don't want to do that, as one of them is one that you need to be connected once you finally get to see offline stay. Are you rebooting using the method described in jp4756's guide? meaning your rebooting using the recovery option reboot, then in command doing the adb reboot recovery, then once you no the phone is gonna boot into recovery you switch to spamming adb devices? When you say your in a loop it sounds to me maybe your not doing the adb devices after the phone listened to your adb reboot recovery command
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
before plugging your phone into your computer a single time, can you confirm that you started up USBDeview and uninstalled every single driver related to android, or mytouch or htc etc... Also before ever plugging your phone in a single time did you install htc completely?
Code3VW said:
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
Click to expand...
Click to collapse
Right Click Android Phone - Properties - Driver - Update Driver - Browse My Computer - Let me pick from a list of device drivers (click this, don't give it the path in the upper box) - Have Disk - Browse to yours C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 - click androidusb.inf and select Open - OK - Unclick Show compatible hardware - Select "T-Mobile myTouch 3G Slide" - Next - All Done.
after getting some sleep and starting fresh, i tried this method again this morning. on the fourth or fifth try i got my slide to stick in offline mode. so then i unplugged it and plugged it back in to get into recovery. lost it, and now im on my 50th or so try to get it back to offline mode.
i need a stiff drink lol
it seems partially a driver issue and also an adb issue i thinks. it connects 'when it feels like it'
i'll report back if i make any progress.
btw im doing this on XP Pro SP3 fully updated
edit: I also noticed when adb does catch the slide, 2 instances of adb are running, then one closes and loses the phone. maybe this will help solve some of the problems
You've misunderstood that post. Only one instance of ADB will show when the loop is not running. Once you start the loop, another instance of ADB will show up and disappear many times. This is normal. As long as only one instance is showing before loop, you are fine.
fermunky said:
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Click to expand...
Click to collapse
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
mtjnkee said:
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
maybe your downloads were corrupted. that's really strange...
man, that really sucks! I am truely sorry...
after spending 20 hours or so on rooting, I really feel your pain.
After I reboot into recovery mode and then use adb to check for my device I never get it to show up. Just so I am clear when you say 'spamming your device' you mean after reboot and rapidly entering the reboot recovery command, then looking for device with adb devices command. I never get it to show.
Thanks for the reply!
No devices in adb?
So I had this same problem with my MT3G. Type in "adb devices" kills the last device and it lists connected devices and NONE were listed. Not sure exactly what I did, but did eventually get it working. (I was trying to use the emulator)
Now though I'm having the same problem with my wife's MTS. Any ideas?
I have a Nexus 7 Wifi Tab.
It was rooted and I was flashing Android 4.4.4 Facory images on it.
It was supposed to restart automatically but it didn't so I manually powered it on.
The Google Logo Appeared and it Stayed there, There was also a start icon on the top just like there is in the bootloader mode.
I got it into bootloader mode after waiting for some time and I did a format of the OS ACCIDENTALLY.
Now when I restart it form TWRP it gives a NO OS WARNING and if I still restart it The Google Logo appears with the Start Icon on top and a small "boot failed" text on the top left.
PLZ HELP.
PLEASE SEE THE VIDEO OF THIS ON THE LINK IN THE ATTACHED PDF FILE:::
I CAN ACCESS THE BOOTLOADER and RECOVERY MODE BUT MY LAPTOP(WINDOWS) DOESN'T READ DEVICE.
:crying: :crying: :crying:
Maarij2001 said:
I have a Nexus 7 Wifi Tab.
It was rooted and I was flashing Android 4.4.4 Facory images on it.
It was supposed to restart automatically but it didn't so I manually powered it on.
The Google Logo Appeared and it Stayed there, There was also a start icon on the top just like there is in the bootloader mode.
I got it into bootloader mode after waiting for some time and I did a format of the OS ACCIDENTALLY.
Now when I restart it form TWRP it gives a NO OS WARNING and if I still restart it The Google Logo appears with the Start Icon on top and a small "boot failed" text on the top left.
PLZ HELP.
PLEASE SEE THE VIDEO OF THIS ON THE LINK IN THE ATTACHED PDF FILE:::
I CAN ACCESS THE BOOTLOADER and RECOVERY MODE BUT MY LAPTOP(WINDOWS) DOESN'T READ DEVICE.
:crying: :crying: :crying:
Click to expand...
Click to collapse
Look at this thread... http://forum.xda-developers.com/showthread.php?t=2403884
I think it will help you!
Thanks but...
THE COMPUTER DOESN'T READ MY DEVICE!!!!!!
:crying:
Maarij2001 said:
THE COMPUTER DOESN'T READ MY DEVICE!!!!!!
:crying:
Click to expand...
Click to collapse
You may be in what comminus calls "driver hell"
Cue the dun-dun-dun.
As of this post, I am in driver hell as well (that rhyme). For now, I suggest you carefully read the driver installation instructions in this thread http://forum.xda-developers.com/showthread.php?t=1907796 - CAREFULLY. The video linked in the thread shows @tetakpatak going through the whole process. In the video description, tetapak made a "SDK - ADB - BOOTLOADER CHECKLIST". I recommend you follow this, as it helps with driver installation. I am following this too, by the way.
People have commented on the video saying that they were able to unbrick their Nexus 7.
THERE IS HOPE FOR US! (I hope)
I am also a kid who is going through the depresssion of losing his Nexus.
A problem again
I Told you that my device can't be accesed by my computer.
Buying Something Else
I've decided that if I can't fix My NEXUS 7 Then I will Buy the "HP SLATE 7"
It's Features mostly are that of the Nexus 7 exept that its display is more of a "blue Hue".
Maarij2001 said:
I Told you that my device can't be accesed by my computer.
Click to expand...
Click to collapse
Don't worry mate, you will probably fix that without problems.
What you can do, you could for example run fastboot or ADB commands directly from Ubuntu, no drivers are needed there. It is really easy, check my little thread here under short section "INSTALL ONLY FASTBOOT":
http://forum.xda-developers.com/showthread.php?t=2726287
In the section beyond is described several ways how can you run Ubuntu on Windows computer.
Alternatively, I must ask if you have SDK on your Windows computer? You will need fastboot working so if you install Google USB driver properly, you should just open cmd, cd to your platform-tools folder and connect your tab in bootloader mode via USB cable and wait until it installs your N7 unit for fully working ADB and fastboot.
After that, you will be able to run fastboot commands. Here is excellent guide by our forum mate comminus, I suppose you already know it:
http://forum.xda-developers.com/showthread.php?t=1907796
Don't hesitate to ask if you need help.
Question
I do Have SDK Manager on my Computer.
I have installed android SDK Platform tools but under EXTRAS there is no Google USB Drivers option.
Can I install Google USB Drivers from the Website : "developer.android.com/sdk/win-usb.html"
And I am REALLY THANKFUL to you for Helping me out.
:laugh: :laugh: :laugh:
Maarij2001 said:
I do Have SDK Manager on my Computer.
I have installed android SDK Platform tools but under EXTRAS there is no Google USB Drivers option.
Can I install Google USB Drivers from the Website : "developer.android.com/sdk/win-usb.html"
And I am REALLY THANKFUL to you for Helping me out.
:laugh: :laugh: :laugh:
Click to expand...
Click to collapse
You are welcome!
Yes, you definitelly can install the driver from the site
http://developer.android.com/sdk/win-usb.html
On the upper right part of that page are the links and instruction.
tetakpatalked from Nexus 7 flo
Question
Another Question That when I download the Google USB Driver from this website do I have to Keep it in .zip format.
Maarij2001 said:
Another Question That when I download the Google USB Driver from this website do I have to Keep it in .zip format.
Click to expand...
Click to collapse
No mate, unzip it and then run the executable application from extracted folder on your PC. That will install the drivers
tetakpatalked from Nexus 7 flo
Hello fellow xda users i some how bricked the oneplus during reverting back to cm from oxygen os. I tried everything but nothing seems to solve the issue so i went to oneplus one hoping they will solve the issue and here is what i got. See for yourself
Are you really sure you briked it? That's pretty hard to do.
Buddy, there are two guides how to unbrick your oneplus in this oneplus general section. It's easy to follow.
Oneplus customer service was only as bad as you reading the guides/requirements and tutorials for flashing and modifying files :silly:
big_b0sss said:
Hello fellow xda users i some how bricked the oneplus during reverting back to cm from oxygen os. I tried everything but nothing seems to solve the issue so i went to oneplus one hoping they will solve the issue and here is what i got. See for yourself
Click to expand...
Click to collapse
Honestly, from what I can see you could have easily recovered your phone had you done the right research and followed the multiple tutorials on how to unbrick this phone. And the fact is, you bricked the phone because you were doing things to the device without really knowing what you were doing. That isn't their fault.
XDA Moderator
Transmitted via Bacon
Would anyone help me through TeamViewer?
big_b0sss said:
Would anyone help me through TeamViewer?
Click to expand...
Click to collapse
This helped me last time when my phone brick, black screen at all.
I can't find where's the original post well, I posted below.
http://forum.xda-developers.com/one...nel-black-screen-fastboot-adb-t2835696/page39
Quote:
Originally Posted by netbuzz
EDIT 1/29/2015
I am leaving the original post below the line, however please be advised that I created a new forum thread with updated instructions and workarounds for Windows 7 and Windows 8 users. This thread is located at: http://forum.xda-developers.com/onep...s-one-t3013732
================================================== ================================================== =
OK, as promised I wanted to write up more detailed steps on how I unbricked my OPO. First, thanks to all who contributed, found the needed files and solution.
The solution is in fact to download Color.zip from https://mega.co.nz/#!BkpwyYSB!rkYSkF...p1-MX1cLLtaiRo.
After downloading, unzip the archive.
Next, Windows drivers. If you're like me you've already tried different drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then, go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through.
Second note about drivers if that I had the worst time trying to get things to work on my Windows 7 computers. Both Windows 7 and 8 block unsigned driver installations. I've tried overwriting these settings and spent half a day messing with it, and I never go the next steps to work properly. I ended up trying installing the drivers from Setup.exe and the following steps on my Windows 2003 server and things worked properly first time. I am not saying that you won't get this to work on Window 7 or 8, but if you're having troubles try Windows XP, that might make a difference.
Anyway, once you have the drivers straightened out, connect your phone to the computer, start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com devices. If you unplug the phone and move it to another port, or computer, it will show your bricked phone on a different line. There is no reason to click in or select at lines, the program knows where the phone is.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Anyway, once you see the phone in the list, click Start. You should see the programs starts writing different files to the phone. Each time it writes a file you'll see a progress bar. Once this is going you know you will be good to go... After all files are written, the line with your device will turn green. You're good, unplug and reboot your phone to ColorOS.
If there is a problems flashing the device, the line will turn Red. That's what I was getting on my Windows 7 after like 3 seconds after clicking Start. After moving to Windows 2003, everything worked like a charm.
Once you're on ColorOS and want to go to Cyanogenmod 11S, you have a few options. The easiest way if to use a toolkit from http://forum.xda-developers.com/onep...9-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/onep...stock-t2826541 and run the following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue. If you're still getting stuck, let me know, I'll see if I can help.
Click to expand...
Click to collapse
Netbuzz has a dedicated thread for his unbrick tool now, it's here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Closing this thread, as there are already dedicated threads on how to un-brick your device.
Hello everybody !
I 've spend a long time on this forum and i've found a lot of interesting and useful tips.
I'm in a bad situation today and I can not find a solution so i thank you for the time spent reading this.
Yesterday i've seen an icon on my desktop and i couldn't remember what application it is. I clicked and it was the beginning of an endless nightmare... A huge lag began by making the phone unusable and apps was installing one after one...
When it has calmed down a bit, i tried to install cleaning softwares but i couldn't do anything so I tried to do a factory reset. After that... the malware was still here... So i've decided to clean all by installing a new ROM.
This is a Jiayu S3 4G 5.5 Inch MT6752 Octa Core RAM 3GB 1080P Screen Dual SIM 4G LTE Mobile Phone (invoice description) so i wanted to try the CM12.1 for Jiayu S3 (found on needrom).
My phone was Rooted and TWRP was installed so i've copied the ROM files on a SD card, rebooted in recovery mode, wiped cache, data, dalvic and system and tried to install the new ROM. it was abnormally rapid and now the phone bootloops.
The only thing i can do is activate Fastboot (if i choose normal boot or recovery it continues to bootloop).
I've tried to flash recovery with :
fastboot flash recovery recovery.img
but i get an error message : FAILED (remote : partition 'recovery' not support flash).
Does anyone has ever been in this situation and solved it ?
Thanks for your help !
Hello,
I got exactly the same problem. Did you find a solution?
My phone is in a bootloop, I can only access to the fastboot mode. (fastboot devices show my device).
In this mode, I can't flash my recovery.img:
fastboot flash recovery recovery.img --> partition 'recovery' not support flash.
I can't see my device with the command adb devices (adb devices doesn't show my device, I think because USB debugging is off, but i can't switch it on)
Did someone find a solution ?
Any help would be appreciated, thanks !
That's the behavior of a wrong preloader that was flashed / malware that affected preloader.
Grab a full spftools ROM set, and flash the entire ROM using " upgrade mode"
Cheers
PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
PPS: this will destroy all of your data, so back it up first ..
Thanks for your answer.
So, I downloaded latest version of Flash_Tools, but i can't find any complete set for flashing... only recovery.img (I'm searching on needrom.com). Do you have a place to find these?
>PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
I think i got another problem: with Flash_Tools, I'm unable to flash anything to my device... There is a special mode to launch, as you explained, but it seems I can't access it... By pressing both up and down volume button, the phone should boot on a special mode ? How can I know if the phone is booted in this mode ? The USB cable must be plugged before/after booting the phone in this mode ?
mick605 said:
Thanks for your answer.
So, I downloaded latest version of Flash_Tools, but i can't find any complete set for flashing... only recovery.img (I'm searching on needrom.com). Do you have a place to find these?
>PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
I think i got another problem: with Flash_Tools, I'm unable to flash anything to my device... There is a special mode to launch, as you explained, but it seems I can't access it... By pressing both up and down volume button, the phone should boot on a special mode ? How can I know if the phone is booted in this mode ? The USB cable must be plugged before/after booting the phone in this mode ?
Click to expand...
Click to collapse
There is no special mode, please serach the forum on how to use sptools, i am sure you will find plenty of them.
Sorry for late answer !
Thanks for this advice, i will try as soon as possible and post if it's ok or not.
Hello everybody !
Ok, I got it !
My problem came from the drivers... But not the ADB drivers, the preloader drivers.
In the Windows device manager, when I plugged my phone (previously swithced off), I got a "MT65xx Preloader" device with a warning. Be careful, this item stay 2 or 3 seconds before disappearing ! This driver wasn't installed correctly, that's why Flash Tools didn't worked for me (it didn't see my phone) !
So, I got the driver on the web, by typing "MT65xx Preloader driver", I got the drivers that I installed. This guide gave me the files and a method to install them:
http: //laurentiumihet.ro/sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices/ (can't post links, delete space after http: )
To install the driver, you can set up manually by right clicking on the "MT65xx Preloader" > "Update drivers". Then, browse to the drivers you previously downloaded (a folder containing .inf and .sys files). Windows should detect the driver and install it.
To check if the preloader driver is correctly installed, power off your phone and unplug it, them plug it. Instead of the previous "MT65xx Preloader" entry, you should now see a "MediaTek PreLoader USB VCOM Port" under "Ports (COM & LPT)" (same as before, this item is displayed only 2-3 seconds...).
Now that the preloader driver is correctly installed, Flash Tools works for me. I successfully flashed a new rom I got from needrom.com (a full set, as suggested by superdragonpt), and my phone boots now =)
Thanks all for your answers ! Xehon, hope it will works for you !
Thanks mick605 !
I travel for work so i can't try all the advices on this forum atm.
I'll check this when i get back home and i'll tell you if it's ok
Thanks again !
mick605 said:
Hello everybody !
Ok, I got it !
My problem came from the drivers... But not the ADB drivers, the preloader drivers.
In the Windows device manager, when I plugged my phone (previously swithced off), I got a "MT65xx Preloader" device with a warning. Be careful, this item stay 2 or 3 seconds before disappearing ! This driver wasn't installed correctly, that's why Flash Tools didn't worked for me (it didn't see my phone) !
So, I got the driver on the web, by typing "MT65xx Preloader driver", I got the drivers that I installed. This guide gave me the files and a method to install them:
http: //laurentiumihet.ro/sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices/ (can't post links, delete space after http: )
To install the driver, you can set up manually by right clicking on the "MT65xx Preloader" > "Update drivers". Then, browse to the drivers you previously downloaded (a folder containing .inf and .sys files). Windows should detect the driver and install it.
To check if the preloader driver is correctly installed, power off your phone and unplug it, them plug it. Instead of the previous "MT65xx Preloader" entry, you should now see a "MediaTek PreLoader USB VCOM Port" under "Ports (COM & LPT)" (same as before, this item is displayed only 2-3 seconds...).
Now that the preloader driver is correctly installed, Flash Tools works for me. I successfully flashed a new rom I got from needrom.com (a full set, as suggested by superdragonpt), and my phone boots now =)
Thanks all for your answers ! Xehon, hope it will works for you !
Click to expand...
Click to collapse
First of all hi I'm new in this thread,
I have installed everything correctly but I still have only 3 seconds before my phone showes the the charging icon and disconnects.
Can anybody please help me? I actually have been stuck with this problem for months now and all these months I have been using the samsung galaxy s advance (launched in 2011) on marshmallow.
First of all, i have read some similar threads about this, and all advise diffrent solution besides the hardware mod, I have tried for 2 days all methods in Miui forums and none have worked for me except the hardware method.
My Device: Xiaomi Redmi Note 3 Pro / SD version.
State:
-would only show "Mi" logo when powered on.
-Would enter only Fastboot.
- No EDL mode
- No recovery
-bootloader locked
-In this state, you can't flash absolutely nothing with any software. (from fastboot).
Requirements:
- windows 7/ windows 10 x64 edition.
- ONLY LATEST version of miflash, from 2016 onward, so it has the required drivers and methods to work with the phone. (I have tried with older versions and it did not work, i thought there was no hope for my phone).
- one hard bricked Redmi Note 3 Pro
- any fersion of Stable FASTBOOT OFFICIAL rom. (.tgz extension) - I personally used kenzo_global_images_V7.2.3.0.LHOMIDA_20160129.0000.14_5.1_global_c85ba6c524.tgz
- medium disassembly skills,
- a lot of patience,
- minimum set of tools (one small cross screwdriver, 1-2 strong finger nails, good eyesight).
- one microusb cable
HOW TO:
1. uninstall all drivers and software related to the Xiaomi phone. (I ended up reinstalling windows 7 just to be sure all was gone - that is how desperate I became). To be sure this is done correctly, with the phone turned off, connect it to the computer.
Go into device manager, search in com ports, or wherever any drivers are installed for the phone, and uninstall all of them, ticking remove driver files also.
after doing this, hit refresh, and see if any drivers get installed again.
Repeat until there are no drivers installed, and the device will be without a driver.
2. Disconnect the phone and RESTART WINDOWS
3. Disable driver signature verification/enforcement:
a. in windows 7, this is easy: restart windows, hit f8 until a menu pops up where you can choose disable driver signature verification/enforcement.
b. in windows 10, it is a little bit longer, but: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ - Be careful, when choosing the option in the last menu, use F... keys, not number keys.
4. while in windows, in the bottom right corner, there should be a message saying "test mode"
5. install ONLY the LATEST VERSION of Miflash! you may get some messages about driver installation (2 times), allow installation!
6. RESTART WINDOWS
7. Prepare the phone!: I followed the video here, even I did not understand the language: http://choimobile.vn/threads/video-...o-snapdragon-650-fix-download-mode-edl.65098/
- First, I used my nail to open the phone up, just like in the video. It is great that the screen is not glued to the body, there are only some clips holding it in place!
- after opening the cover please be careful - there is a cable connecting the case to the mainboard - the fingerprint sensor.
- after this, unscrew the 7 or 8 screws as in the video.
- unlock the cables as in the video - please be sure not to disconnect all the cables.
- now, first get the antenna plastic cover outside of the way.
- after disconnecting the camera module, I would personally advise you to get the camera out of the way first, as there is a piece of foil glued between the mainboard and the underneath of the camera module (on the display)
- with great care, rise the Mainboard from the display.
- to have better access to the testpoint pins, I turned the Mainboard over the battery.
- now, connect the microusb cable to the phone.
8. connect the phone to the computer.
9. go into device manager and check if there are any devices installed, there should be under ports.... a device called Qualcomm HS-USB Diagnostics 900E.
10. Now comes the tricky part, switching the phone to EDL mode (emercency download)
look on the back of the motherboard of the phone to connect the 2 testpoint pins as in the video. You can use anything to do this. a metal wire, a small scissors, an untied paperclip... You will have to do this while device manager is opened, as you must check it when the driver changes to "qualcomm hs-usb qdloader 9008".
Please be careful when trying to connect the 2 pins not to touch any metal housing, ans this will restart the device each time.
Now, try and try and try until the driver changes to "qualcomm hs-usb qdloader 9008".
11. unzip the rom using 7 zip to a destination of your choosing. I advise as short destination as possible and no spaces used in the folder naming. I unpacked it in C:\rom\
12. Open Miflash
13. As per other many many instructions:
a. click browse - select the folder where you unpacked the rom (for me, c:\rom\)
b. click the arrow next to brows button and select advanced.
c. in the first field, navigate to the folder where the rom was unpacked and select flashall.bat
d. in the third field select prog_emmc_firehose_8976_ddr.mbn from the "images"folder in the folder whre he rom was extracted
e. field 7: rawprogram0.xml and field8: patch0.xml
f. Hit the Refresh button, the device should appear as a com port in the white field of Miflash.
g. just to be sure, tick also "flash all" in the bottom of miflash.
14. Hit the Flash button on Miflash and this should be the last step before powering up your revived Xiaomi Redmi Note 3.
This is what I learned in the past 2-3 days.
Different errors I got during the learning process and what i did to avoid them:
- different problems with drivers not installing correctly or showing different device names - just use the method i pointed out in the beginning to uninstall any driver previously installed on the computer, with the refresh in device manager and than uninstalling all.
- "end of package" error at second 2 while flashing in Miflash - you are using an older or an unsupported version of miflash, just use the latest one.
- not being able to flash anything while in fastboot - if you have a locked bootloader, on redmi note 3 snapdragon version, you simply won't be able to flash anything. end of story. this is the whole purpose of having a locked bootloader.
- trying to go into EDL mode using fastboot comand "fastboot oem eld" - this will not work for a really bricked device as was mine. the only solution is to go through the tespoint pin connection.
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Please move the thread into guides/tutorial section.
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
jujusito said:
Now is possible unbrick without disassembly:
http://en.miui.com/thread-267263-1-1.html
http://www.htcmania.com/showthread.php?t=1174700
Click to expand...
Click to collapse
please read through all the thread, don't just throw in a link. the method mentioned by you will not work on some bricked devices, including mine. this did not work for me, so I ended up disassembling the phone.
aabenroi said:
Well, mine was bricked too 2 days ago... even I already unlock the bootloader using the official way.
It happened because I'm on AOSP and I flash Xiaomi.EU ROM from TWRP.
'MI' Logo flashed twice then the phone turns off itself.
It can't boot, can't enter EDL mode. I just can go into fastboot mode. But nothing can be done there because it always says 'device is locked'.
'fastboot oem device-info' also says the phone is on locked state.
Dunno why this happen, I think its because I play with the unlock bootloader toggle on previous MIUI and AOSP ROM.
After countless of times trying to get into EDL, I give up.
Device manager always show "QCom HS-USB Diagnostic 900E" instead of "QCom HS-USB QLoader 9008"
Finally I try the official Mi Unlock software, re-unlock success and BAM... Phone boots again into system. lol...
This makes me think the bricked problem can prevented/solved to by:
- At least bind a Xiaomi Account to your phone once when using official ROM (recommended China Dev ROM)
- Use that account to apply for the unlock, and when you got the phone bricked/relocked, you can re-unlock it using official way to revive the phone
Click to expand...
Click to collapse
I also applied for an unlock code, but this takes up to 15 days, and I have the phone for only 3 days . I could not wait for the code, I had to do something to revive it.
meangreenie said:
i wonder if there's a way not to make trwp locked in the recovery partition, so if someone flashes a factory rom without precaution, twrp will simply get overwritten by factory recovery. Wouldn't that prevent these hard bricks?
btw, nice guide
Click to expand...
Click to collapse
I made a modified TWRP which will not cause hard bricks
Rajdip said:
I made a modified TWRP which will not cause hard bricks
Click to expand...
Click to collapse
great work! your modded twrp will no doubt save me when i forget i have to delete the emmc file in the future.
Dear, thank you for your contribution, this deserves to be a section more important, really saved my phone from the hard brick. Again very grateful
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
xdarkmario said:
how do i know what a test point looks like on any phone? like the new redmi 3s? i cant get into edl because im stuck in Qualcomm HS-USB Diagnostics 900E
Click to expand...
Click to collapse
maybe look for something like this?
http://choimobile.vn/Temp/Testpoint_Redmi_Note3_PRO_3.jpg
I doubt they will have much variance from xiaomi phone to phone to make it easy for factory / repair centers to fix many models... (I could be wrong though), other brands are probably different.
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
ilvmyname said:
Well you can enter edl mode from fastboot via this simple tool
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
And then you can flash any miui .tgz based rom and resurrect.
I hard bricked my Device last night and resurrected
PS : you must have the MiPcSuit installed
Click to expand...
Click to collapse
links dead
Quick addition: if you're using Virtual Box, like me (on a mac), you need to enable USB 2.0 on the virtual machine. On Virtual Box, this means you have to add an extension pack. This might save you 48hrs, like it cost me