Related
Hi guys, I'm trying to install RomAur onto my device http://forum.xda-developers.com/showthread.php?t=2641067.
1st step is to root the device ON LOCKED BOOTLOADER which leads me to http://forum.xda-developers.com/showthread.php?t=2634196.
And from that thread I've followed the instructions, placed my 2 .ftf files in the firmwares folder within Flashtool.
At which point I've run into 2 problems. 1st, the Z1c isn't recognised by the tool. So I tried to tell the program that it's just a Z1.
Next problem occurs when I try to flash the device, my specific firmware doesn't show up in the Firmware Selector. The only thing showing is X10 V1 BLRelock, which was already there by default.
Could someone give more detailed instructions as to how to flash using Flashtool please.
If you want to unlock the bootloader make sure to back up TA partition!
Check out my guide, it's more detailed: http://forum.xda-developers.com/showthread.php?p=50176658 (rooting is the same process as Darkimmortal's guide)
See step 8, you probably didn't put the ftf file in the correct folder.
zxz0O0 said:
If you want to unlock the bootloader make sure to back up TA partition!
Check out my guide, it's more detailed: http://forum.xda-developers.com/showthread.php?p=50176658 (rooting is the same process as Darkimmortal's guide)
See step 8, you probably didn't put the tft file in the correct folder.
Click to expand...
Click to collapse
Thanks for replying.
I can't seem to manually update the z1c drivers, device manager keeps telling me i have the latest driver. So I skip that step and carry on.
Stuck at 8. I've tried putting the ftf in /firmware as well as other locations and changing the directory that flashtool will search.
Something else is wrong, any other suggestions?
sllik said:
Thanks for replying.
I can't seem to manually update the z1c drivers, device manager keeps telling me i have the latest driver. So I skip that step and carry on.
Stuck at 8. I've tried putting the ftf in /firmware as well as other locations and changing the directory that flashtool will search.
Something else is wrong, any other suggestions?
Click to expand...
Click to collapse
You can see the source folder in the top of the Firmware Selector. Default is "C:\Flashtool\firmwares". Make sure your file is inside there and ends with ftf.
Also check if the file has the correct hash:
SO-02F_14.1.H.1.281_docomo.ftf
MD5: 259221BCEEB54F3AD7F9721111E0EF1D
SHA1: 365C185A3D5B8DA64B8B84ECBEE62DD882739E4A
zxz0O0 said:
You can see the source folder in the top of the Firmware Selector. Default is "C:\Flashtool\firmwares". Make sure your file is inside there and ends with ftf.
Also check if the file has the correct hash:
SO-02F_14.1.H.1.281_docomo.ftf
MD5: 259221BCEEB54F3AD7F9721111E0EF1D
SHA1: 365C185A3D5B8DA64B8B84ECBEE62DD882739E4A
Click to expand...
Click to collapse
Bad hash. Thanks for the help, redownloading now, hope it succeeds this time.
Please let me know if it worked after redownloading, I will add it to the guide :good:
Stuck on step 13.
Run Z1C-lockeddualrecovery(...)installer.zip's install.bat and select option 3 [Installation on unrooted ROM] ( URL goes here )
I'm running the .bat file and selecting option 3 but I get stuck with the text saying 'Waiting for Device, connect USB cable now..."
I can't turn my phone on, well I can't tell if it's on or off since it just stays black, but pressing volume up and down vibrates the phone.
sllik said:
Stuck on step 13.
Run Z1C-lockeddualrecovery(...)installer.zip's install.bat and select option 3 [Installation on unrooted ROM] ( URL goes here )
I'm running the .bat file and selecting option 3 but I get stuck with the text saying 'Waiting for Device, connect USB cable now..."
I can't turn my phone on, well I can't tell if it's on or off since it just stays black, but pressing volume up and down vibrates the phone.
Click to expand...
Click to collapse
Make sure your phone is off (hold volume up and power button 5seconds, if the phone was on it will vibrate 3times and shut down).
Then power on your phone normally (hold power button until there is a slight vibrate). The screen will stay black, this is normal.
Plug in the USB cable to your pc and continue with step 13.
If it still says 'Waiting for device' you either:
a) don't have the drivers installed (check in device manager if something shows up when the phone is connected)
b) didn't correctly execute step 10
c) selected some wrong options in step 11
If it's b) or c), best solution is to start from scratch.
zxz0O0 said:
Make sure your phone is off (hold volume up and power button 5seconds, if the phone was on it will vibrate 3times and shut down).
Then power on your phone normally (hold power button until there is a slight vibrate). The screen will stay black, this is normal.
Plug in the USB cable to your pc and continue with step 13.
If it still says 'Waiting for device' you either:
a) don't have the drivers installed (check in device manager if something shows up when the phone is connected)
b) didn't correctly execute step 10
c) selected some wrong options in step 11
If it's b) or c), best solution is to start from scratch.
Click to expand...
Click to collapse
Ok so I managed to sort it out by starting from scratch.
I think it would be helpful to mention in your guide that the phone is blank from steps 13 through to 15. Thanks for the help, appreciate it.
Hello ..
I have a big problem !! I try to flash the Smartzen rom for try and after when my phone reboot..I have a bootloop
But the problem it's -> I don't acces to the bootloader and the recovery
I make power and volume + and i have vibration and just that
When i put the phone with the usb cable the phone doesn't charge.. and sometimes yes
And sometimes the phone reboot with a bootloop
I can't flash a new rom because my pc don't recognize the phone( just the sound when a device is connected) (it's normal i don't have access to bootloader)
And on the tutorial for the unbrick it's say " Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. " but i don't have that...i have NOTHING
What is the solution please ?? Because i don't see any solution..
quadeur06 said:
Hello ..
I have a big problem !! I try to flash the Smartzen rom for try and after when my phone reboot..I have a bootloop
But the problem it's -> I don't acces to the bootloader and the recovery
I make power and volume + and i have vibration and just that
When i put the phone with the usb cable the phone doesn't charge.. and sometimes yes
And sometimes the phone reboot with a bootloop
I can't flash a new rom because my pc don't recognize the phone( just the sound when a device is connected) (it's normal i don't have access to bootloader)
And on the tutorial for the unbrick it's say " Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. " but i don't have that...i have NOTHING
What is the solution please ?? Because i don't see any solution..
Click to expand...
Click to collapse
If you cant access bootloader i would suggest to use xfstk to reflash the bootloader. follow this guide. I had same problem and successfully recovered from a hard brick.
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
sharkie545 said:
If you cant access bootloader i would suggest to use xfstk to reflash the bootloader. follow this guide. I had same problem and successfully recovered from a hard brick.
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
Thank to you're answer...but xfstk doesnt launch on my computer and i see that on the tutorial
back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. "
I dont have that
quadeur06 said:
Thank to you're answer...but xfstk doesnt launch on my computer and i see that on the tutorial
back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. "
I dont have that
Click to expand...
Click to collapse
Basically as long as you followed the drivers install process correctly under device manager for a quick seccond you will see under IntelSOC you will see moorefield appear then disconnect. If that is good then your on your way.
Simply open xfstk follow the steps link to the proper files for your device, then hit begin download. While the counting is going down, turn on your phone as described in the steps and it should begin flashing.
here is a good video tutorial that helps - credit to timbernot
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
sharkie545 said:
Basically as long as you followed the drivers install process correctly under device manager for a quick seccond you will see under IntelSOC you will see moorefield appear then disconnect. If that is good then your on your way.
Simply open xfstk follow the steps link to the proper files for your device, then hit begin download. While the counting is going down, turn on your phone as described in the steps and it should begin flashing.
here is a good video tutorial that helps - credit to timbernot
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Click to expand...
Click to collapse
Thank you my friends so much!!
same prob here. in my case, I have installeds all things successfuly bt xfstk cant flash after first step. 20 tries and then stop the process. any help?
vyaskd said:
same prob here. in my case, I have installeds all things successfuly bt xfstk cant flash after first step. 20 tries and then stop the process. any help?
Click to expand...
Click to collapse
Usually when this happens xfstk lost communication with the device. Typically I encountered this when xfstk continued to flash the OS file.
In this case the fix is
To Go to Options to change the value in the Value section Override Flag GP 0x80000807. (Note the guide calls for 5 0's but only 4 0's will work)
sharkie545 said:
Usually when this happens xfstk lost communication with the device. Typically I encountered this when xfstk continued to flash the OS file.
In this case the fix is
To Go to Options to change the value in the Value section Override Flag GP 0x80000807. (Note the guide calls for 5 0's but only 4 0's will work)
Click to expand...
Click to collapse
I've done this already before flashing, as told in guide. any other trick to make fone stay connected for little longer? may be some change in xxx807 value?
vyaskd said:
I've done this already before flashing, as told in guide. any other trick to make fone stay connected for little longer? may be some change in xxx807 value?
Click to expand...
Click to collapse
This happened to me too - I solved it the dumbest way possible. The first time I set it up and ran it and it got through the first part and then failed to do the second. I just happened to have to go pick up a pizza at the time, so I went and got the pizza, came back, touched nothing, ran xFSTK again, and it worked! After that, I always ran it once, let it fail, then waited 10 minutes touching nothing, and ran it again. That always works for me (don't know why, and I know it doesn't make sense, but hey it works for me all the time)
Greetings,im Akmal and today I will be sharing some helpful solution to unbrick your Oppo Find 7/7A.Short Story(myb a lil bit longer)¬
So my find 7A got soft bricked when I install custom rom without using TWRP(pretty stupid to do so)
After rebooting my phone keeps on booting to fastboot mode and no matter it happen the same if i press vol up/vol down and power button.
At this stage I knew my phone is soft bricked.So I found the solution to it through some old posts which you have to extract the ColorOS blablabla and adb thingy(I dont wanna go through it here)
But I dont realised that i forget to flash a file name "TZ.MBN"
Now that my phone wont ever boot or even to fastboot which resulted to hard brick.
No recovery screen.
No Charging status screen
No Fastboot screen
No sign of vibrating when i push the power button
-So here is the solution-
Disclaimer-I am not responsible for what ever happen to your device after this-
-there are already some other posts like this but I make this post to let you know that its still working.
1a)First,download the OPPO UNBRICK TOOL HERE
bit.ly/OPPOUNBRICK
1b)goto Google and search for Qualcomm qd loader.download,install and restart your pc.
2)After restarting,Extract the file from OPPO UNBRICK TOOL and open "Msm8974DownloadTool.exe"
3)as you may have notice,its chinese language or some aliens language but dont worry it isn't corrupted,just follow through↓
4)disconnect your device battery,then open the software and press start,after that connect the phone to your pc/laptop (WITHOUT BATTERY) and hold volume up button
5)please wait patiently as it is reflashing stock rom to your device.
6)as you may have noticed maybe your device disconnected but DONT GET PANICKED! press again the power button until its downloading again on the software.
7)If it has done downloading,some row should be in a Green colour.
8)disconnect your cable and try turning on your device again.
That's it!Any comment or curiosity I will try helping you through the comment section but I not guaranteed everything I can answer
P/S:if your device is softbricked,you just should disconnect your battery,and then open the software and press start,then connect the phone to your pc/laptop (WITHOUT BATTERY) and hold volume up button.
If your device is hard bricked(like mine)only holding the power button could work as well
*UPDATE* 24/2/2019
-If you guys still have any concerns kindly contact me through twitter (0728mal)
*UPDATE* 4/7/2020
-yes it is still working guys,no worries kayy
-no you don't need internet for it to work,the software already has all the files needed to flash the device,which is why the file is pretty big.
best regards,
Akmal
Link updated :good:
akmlfhm said:
Greetings,im Akmal and today I will be sharing some helpful solution to unbrick your Oppo Find 7/7A.Short Story(myb a lil bit longer)¬
So my find 7A got soft bricked when I install custom rom without using TWRP(pretty stupid to do so)
After rebooting my phone keeps on booting to fastboot mode and no matter it happen the same if i press vol up/vol down and power button.
At this stage I knew my phone is soft bricked.So I found the solution to it through some old posts which you have to extract the ColorOS blablabla and adb thingy(I dont wanna go through it here)
But I dont realised that i forget to flash a file name "TZ.MBN"
Now that my phone wont ever boot or even to fastboot which resulted to hard brick.
No recovery screen.
No Charging status screen
No Fastboot screen
No sign of vibrating when i push the power button
-So here is the solution which make my phone came to life again-
Disclaimer-I am not responsible for what ever happen to your device after this-
-there are already some other posts like this but I make this post to let you know that its still working.
-make sure to charge the phone first even if you do not know if it charging or not
1)First,download the OPPO UNBRICK TOOL HERE
bit.ly/OPPOUNBRICK
2)Extract the file and open "Msm8974DownloadTool.exe"
3)as you may have notice,its chinese language or some aliens language but dont worry its not corrupted,just follow through
4)Connect your phone to PC and press the power button until you heard some like mounted usb alert on windows.(its ok aslong windows does not detect it on device manager but its ok if you can hear the alert sound.
5)back to the software,no need to mess around with it.Click on start until its downloading a "new life" to your phone.
6)as you may have noticed maybe your device disconnected but DONT GET PANICKED! press again the power button until its downloading again on the software.
7)If it has done downloading,some row should be in a Green colour.
8)disconnect your cable and try to turning on your device again.
That's it!Any comment or curiosity I will try helping you through the comment section but I not guaranteed everything I can answer
best regards,
Akmal
Click to expand...
Click to collapse
hi im having this problem as well. my find 7a is hard bricked after i flash coloros v2.1.5i without twrp. the problem is, my computer does not detect my phone at all even after i hard reset and hold power button for 30 seconds. i dont think the battery is drained because before this happened, my phones battery was about 90% and i try recharging the phone for 30 minutes, and nothing happened. so the debrick tool cannot be used. can you suggest anything for my problem?
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Shadician said:
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Click to expand...
Click to collapse
On Mac's OS, you can always install Windows on its proprietary virtual machine and get the process going that way.
babyenchantress said:
hi im having this problem as well. my find 7a is hard bricked after i flash coloros v2.1.5i without twrp. the problem is, my computer does not detect my phone at all even after i hard reset and hold power button for 30 seconds. i dont think the battery is drained because before this happened, my phones battery was about 90% and i try recharging the phone for 30 minutes, and nothing happened. so the debrick tool cannot be used. can you suggest anything for my problem?
Click to expand...
Click to collapse
hello there!I'm really sorry for not checking this that often and really sorry if i let you down because im too busy with my schools work
btw before my computer can detect my phone i have to download a driver which detect qualcomm processor for my oppo then it can be detected by my pc therefore i can do the unbrick process:good:
Shadician said:
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Click to expand...
Click to collapse
yeah you can try WINE also but i never have any experience with mac os before so i cant guarantee that it will work considering that you're configuring your drivers,which can go wrong if not done correctly
So I have bricked my phone (X9006) while trying to install TWRP recovery. It is stuck on logo and adb/ fastboot does not recognise it anymore. I have tried the above-mentioned tool, but this program also does not do anything for a long time. Am I missing something in applying this solution?
Edit: I am an Windows 10 and I might not have the Qualcomm drivers installed. I don't know how to install
true_friend2004 said:
So I have bricked my phone (X9006) while trying to install TWRP recovery. It is stuck on logo and adb/ fastboot does not recognise it anymore. I have tried the above-mentioned tool, but this program also does not do anything for a long time. Am I missing something in applying this solution?
Edit: I am an Windows 10 and I might not have the Qualcomm drivers installed. I don't know how to install
Click to expand...
Click to collapse
Hello there.have you tried downloading the "Qualcomm"
Driver software on your PC?
is it necessary to remove the battery? I don't have tools for opening my phone and it's battery is non-removable
Perhaps an important step is missing. The Qualcomm qd loader driver is may not signed. I had to boot into the extended start menu on Windows 10 and disable the driver signature check - point 7 - and could now successfully debrick my find7.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
UPDATE 2021-02-28
There has lately been discovered a method to flash begonia/begoniain without the need of an authorised Xiaomi account for flashing. Even if one had earlier not implemented the brick protection method (factory preloader + CFW). This means that CFW is not really needed anymore and that many custom roms are moving away from it. So, in case of brick one can follow this detailed guide in order to unbrick without the need for an authorised Xiaomi account for flashing. There is also an explanatory video that may be helpful for some.
UPDATE 2020-02-25
As of 24 Feb 2020 a new method has been found to help RN8p users avoid bricking their devices. It is a preventive measure and NOT a curative, as it cannot help users who haven't already flashed the specific preloader of the engineering ROM version prior to bricking. For more information see the xda thread by @Agent_fabulous.
ORIGINAL POST
I have created this thread in order to share my experience. I have a Redmi Note 8 Pro that was bricked after flashing a wrong boot.img with TWRP. No fastboot, no recovery, no vibration when pressing the power button. The phone was like dead.
The LED turned on when connected to PC with USB cable. The PC recognised the phone for 5 seconds when holding vol+ before connecting the USB cable. It was recognised as "Mediatek USB port " on Device Manager and after 5 seconds, the PC would lose the connection to the device.
It seems that when holding the vol+ button and connecting the phone to the PC with USB cable, the phone enters to DA mode and waits for a signal that is trying to flash the firmware to it. If the signal doesn't come in the first 5 seconds, the device just gets out of DA mode.
MiFlash does not recognise the phone in this state, as this program can be used only for fastboot flashing.
SP Flash tool recognises the device but returns an "ERROR: STATUS_BROM_CMD_FAIL". This is happening because one has to be logged in with an Authorised Service Account simultaneously when trying to flash with SP Flash Tool. If the authorisation passes, the program starts flashing the firmware to the device.
Requirements
1. MiFlashPro (v4.3.1106.23) downloaded on your pc. (It can be found here.)
2. The stock firmware of your device. (Warning! If you have a Chinese device you have to try with the Chinese firmware. Global device with Global firmware etc. Do not try with Global firmware on Chinese device!)
3. An authorised Service Xiaomi Acount.
The Procedure
0. Unzip your device's firmware.
1. Install MiFlashPro.
2. Navigate to (installation_directory)/MiFlashPro/SP_Flash_Tool/mi and run "account_auth.exe" (Run as administrator). In the window that opens, log in with an authorized Xiaomi Account.
3. Navigate to (installation_directory)/MiFlashPro/SP_Flash_Tool nad run "flash_tool.exe". The SP_Flash_Tool interface opens. Now you have to select the 3 files:
Download-Agent: (installation_directory)/MiFlashPro/SP_Flash_Tool/MTK_AllInOne_DA_mt6765_mt6785.bin
Scatter-loading File: You will find this one on your stock rom folder, especially on the folder called "images".
Authentication File: (installation_directory)/MiFlashPro/SP_Flash_Tool/auth_sv5.auth
4. Press the "Download" button.
5. Connect the USB cable to your PC but NOT YET to your phone.
6. Hold the vol+ button on your phone pressed and NOW connect the cable to it.
7. The program should now react and start the flashing process without giving an error.
8. Wait for the flashing process to end and enjoy!
Sidenote
You surely wonder where you can find an authorised Xiaomi account.
There are rumors that there are people who connect to your PC with remote-desktop programs and provide the log-in details just when they are needed during the flash process. And they get paid for it (~10-15 USD, maybe more).
Another solution would be some mobile-phone technician in you city. He/She may have an authorised account for fixing the phones locally at the store.
You may also be lucky to have a friend with an authorised account.
But I do not know of a valid way to get an authorised account for yourself at the time and age of writing.
Sidenote 2
If I remember correctly, on an older Xiaomi MTK phone, they managed to bypass the authorisation by using a modified DA file. If you don't want to pay for an authorisation service, you can wait for a while. But it is unknown if/when such a file is going to be released for Redmi Note 8 Pro.
polfrank said:
I have created this thread in order to share my experience. I have a Redmi Note 8 Pro that was bricked after flashing a wrong boot.img with TWRP. No fastboot, no recovery, no vibration when pressing the power button. the phone was like dead.
The LED turned on when connected to PC with USB cable. The PC recognised the phone for 5 seconds when holding vol+ before connecting the USB cable. It was recognised as "Mediatek USB port " on Device Manager and after 5 seconds, the PC would lose the connection to the device.
It seems that when holding the vol+ button and connecting the phone to the PC with USB cable, the phone enters to DA mode and waits for a signal that is trying to flash the firmware to it. If the signal doesn't come in the first 5 seconds, the device just gets out of DA mode.
MiFlash does not recognise the phone in this state, as this program can be used only for fastboot flashing.
SP Flash tool recognises the device but returns an "ERROR: STATUS_BROM_CMD_FAIL". This is happening because one has to be logged in with an Authorised Service Account simultaneously when trying to flash with SP Flash Tool. If the authorisation passes, the program starts flashing the firmware to the device.
Requirements
1. MiFlashPro (v4.3.1106.23) downloaded on your pc. (It can be found here.)
2. The stock firmware of your device. (Warning! If you have a Chinese device you have to try with the Chinese firmware. Global device with Global firmware etc. Do not try with Global firmware on Chinese device!)
3. An authorised Service Xiaomi Acount.
The Procedure
0. Unpack your device's firmware.
1. Install MiFlashPro.
2. Navigate to (installation_directory)/MiFlashPro/SP_Flash_Tool/mi and run "account_auth.exe" (Run as administrator). In the window that opens, log in with your Xiaomi Account.
3. Navigate to (installation_directory)/MiFlashPro/SP_Flash_Tool nad run "flash_tool.exe". The SP_Flash_Tool interface opens. Now you have to select the 3 files:
Download-Agent: (installation_directory)/MiFlashPro/SP_Flash_Tool/MTK_AllInOne_DA_mt6765_mt6785.bin
Scatter-loading File: You will find this one on your stock rom folder, especially on the folder called "images".
Authentication File: (installation_directory)/MiFlashPro/SP_Flash_Tool/auth_sv5.auth
4. Press the "Download" button.
5. Connect the USB cable to your PC but NOT YET to your phone.
6. Hold the vol+ button on your phone pressed and NOW connect the cable to it.
7. The program should now react and start the flashing process without giving an error.
8. Wait for the flashing process to end enjoy!
Sidenote
You surely wonder where you can find an authorised Xiaomi account.
There are rumors that there are people who connect to your PC with remote-desktop programs and provide the log-in details just when they are needed during the flash process. And they get paid for it (~10-15 USD, maybe more).
Another solution would be some mobile-phone technician in you city. He/She may have an authorised account for fixing the phones locally at the store.
You may also be lucky to have a friend with an authorised account.
But I do not know of a valid way to get an authorised account for yourself at the time and age of writing.
Sidenote 2
If I remember correctly, on an older Xiaomi MTK phone, they managed to bypass the authorisation by using a modified DA file. If you don't want to pay for an authorisation service, you can wait for a while. But it is unknown if/when such a file is going to be released for Redmi Note 8 Pro.
Click to expand...
Click to collapse
then you can from where for the official account if possible please help I will donate 15usd
itocogan said:
then you can from where for the official account if possible please help I will donate 15usd
Click to expand...
Click to collapse
I am sorry but I don't own an authorized Xiaomi account.
...
hi... my phone has same case with u ... so i try with your method. but at item 5 until 8 cant response with my laptop... can you suggest to me what i must do? ... sorry my english very bad
LepatUbi said:
hi... my phone has same case with u ... so i try with your method. but at item 5 until 8 cant response with my laptop... can you suggest to me what i must do? ... sorry my english very bad
Click to expand...
Click to collapse
Try connecting your phone to the PC with USB cable and then hold pwr+volup buttons for more than 5 seconds. Does it work this way?
polfrank said:
Try connecting your phone to the PC with USB cable and then hold pwr+volup buttons for more than 5 seconds. Does it work this way?
Click to expand...
Click to collapse
no.. dose not work .. i try with off phone >> Hold power + volUp >> connect usb .. it is correct?...
LepatUbi said:
no.. dose not work .. i try with off phone >> Hold power + volUp >> connect usb .. it is correct?...
Click to expand...
Click to collapse
1st way
1. Connect USB cable only to PC
2. Hold vol+ on phone
3. Connect USB cable to phone (while holding vol+)
2nd way
1. Connect USB cable to PC and phone
2. Hold pwr and vol+ for many seconds, until something happens (led turns on and off and phone is detected by the PC).
LepatUbi said:
no.. dose not work .. i try with off phone >> Hold power + volUp >> connect usb .. it is correct?...
Click to expand...
Click to collapse
have u install vcom mtk driver?
polfrank said:
1st way
1. Connect USB cable only to PC
2. Hold vol+ on phone
3. Connect USB cable to phone (while holding vol+)
2nd way
1. Connect USB cable to PC and phone
2. Hold pwr and vol+ for many seconds, until something happens (led turns on and off and phone is detected by the PC).
Click to expand...
Click to collapse
still no effect... do you have other methods?
LepatUbi said:
still no effect... do you have other methods?
Click to expand...
Click to collapse
Unfortunately, these are the only methods that worked for me. In your case I would check these things:
1. Have you installed the right MTK USB driver?
2. Try with another USB port.
3. Try with another USB cable.
polfrank said:
Unfortunately, these are the only methods that worked for me. In your case I would check these things:
1. Have you installed the right MTK USB driver?
2. Try with another USB port.
3. Try with another USB cable.
Click to expand...
Click to collapse
yes.. this link download: http://www.mediafire.com/file/b1xjnx3mj7b7f8y/MTK_USB_All_v1.0.8.zip/file
and i tried with another usb and cable but still cant effect.
All above replying "does not work",, do you all managed to get authorization file??
If so, then kindly do share with all of us.
coolvipcandy said:
All above replying "does not work",, do you all managed to get authorization file??
If so, then kindly do share with all of us.
Click to expand...
Click to collapse
The authorisation file is included in the installation folder of MiFlashPro. It is not the one that is going to make the difference though. The most important thing to do for the process to continue is to log in with an authorized Xiaomi account.
polfrank said:
The authorisation file is included in the installation folder of MiFlashPro. It is not the one that is going to make the difference though. The most important thing to do for the process to continue is to log in with an authorized Xiaomi account.
Click to expand...
Click to collapse
this situation in my computer
So i cant connect my phone with PC..
Your threat actually given me hope to make my redmi note 8 pro power again...
LepatUbi said:
this situation in my computer
So i cant connect my phone with PC..
Your threat actually given me hope to make my redmi note 8 pro power again...
Click to expand...
Click to collapse
Hmm, I really can't think of something else. It seems that you have set up the software as expected and now the only thing that remains is to connect the phone in DA more. But I don't know why it doesn't respond. Hope that you solve it somehow...
Edit: have you tried installing the USB driver with driver signature check disabled in Windows?
polfrank said:
Hmm, I really can't think of something else. It seems that you have set up the software as expected and now the only thing that remains is to connect the phone in DA more. But I don't know why it doesn't respond. Hope that you solve it somehow...
Edit: have you tried installing the USB driver with driver signature check disabled in Windows?
Click to expand...
Click to collapse
i will unistall everything about xiomi.. and will install again in mode driver signature check disabled in Windows. hope this method will success... TQvm my friend
polfrank said:
The authorisation file is included in the installation folder of MiFlashPro. It is not the one that is going to make the difference though. The most important thing to do for the process to continue is to log in with an authorized Xiaomi account.
Click to expand...
Click to collapse
Oh, so its not an either-or situation.
How the people charging for auth keys/ids , getting this from ?
Hi, please try this. Connect to PC then just press volume down button for a minute. If u can get to fastboot then flash or unlock your device again.
If that's not work try press 3 button at the same time for a minute to get to fastboot.
Any feedback is appreciated.
aisidetpipo said:
Hi, please try this. Connect to PC then just press volume down button for a minute. If u can get to fastboot then flash or unlock your device again.
If that's not work try press 3 button at the same time for a minute to get to fastboot.
Any feedback is appreciated.
Click to expand...
Click to collapse
cannot respond in my computer and another computer. it like the same case in first thread by polfrank..
LepatUbi said:
this situation in my computer
View attachment 4872989
So i cant connect my phone with PC..
Your threat actually given me hope to make my redmi note 8 pro power again...
Click to expand...
Click to collapse
when I only run "account_auth.exe" (Run as administrator) it looks like your pics
but when i connect i get this message
LOGIN sucessful
Unauthorized for this operation.
Hey everyone!
So, I've got a HD1903, 8GB RAM 128GB ROM. I updated to OxygenOS 11.0.02, but it was still buggy as hell, so I decided to downgrade. I also had rooted the phone, and decided to get rid of that too. I went to the stock fastboot roms page, downloaded the 10.0.13 ROM and used 'flash-all.bat' file to clear everything. But halfway, it reboots, goes into recovery, then goes to Qualcomm Crashdump mode. That's it. No code or anything, just Qualcomm Crashdump mode, in Blue and Red letters. I tried to hold vol-up, vol-down and power to get into fastboot, but it just loads the fastboot splash screen, then goes back to the same qualcomm crashdump mode screen. Even if i try to hard reset it, by holding vol-up and power, it still goes to the same screen.
Anyone know what to do? I have no idea how to use the 'MSM tool' that everyone talks about, so any guiding advice would be great!
Thanks!
DM me here - https://www.facebook.com/prantor.khan.16 I'll help
HueyT said:
Click to expand...
Click to collapse
I didn't install TWRP, this was all on stock recovery. I also cannot get into fastboot mode.
Msmtool does not need twrp or fastboot--just the software, rom image, drivers, and button combo pushes and holding
OK, so I got it working again, thanks to the advice of reddit users, discord users and the latest msm tool and some googling. I held the vol-up and vol-down buttons for 30 seconds, then connected it to the laptop, with msm running, to a usb 2.0 port, and pressed start. hey presto, it worked. Thanks guys!!
scoped_ar07 said:
Hello
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: only works on Windows PC
1. Unzip the contents of the RAR into a folder.
2. Run the MSM application
3. Click Start.
4. Connect the cell phone in EDL mode (volume up + down button)
5. Wait for the process to finish (it takes a long time, please be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically boot into fastboot mode and display a menu, but if it doesn't and instead boots to the T-mobile screen, you need to force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you need to unlock the bootloader with the command from a Windows CMD window, but you need to download this ADB tool first.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a Windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this time your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, on the command line, run the flash-all.bat file
12. When the phone restarts and the yellow and white letters appear informing that the phone is not safe because the bootloader is unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-PC will detect the phone again in fastboot mode and continue to flash
-Leave the phone and PC still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (ignore it)
13. Finally, the computer will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just turn it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before locking the bootloader again (if you plan to do so) first update via OTA, to the most recent version of Oxygen, otherwise the system will crash again and you will have to repeat the whole process.
Click to expand...
Click to collapse
Stronger1101 said:
Hi
Using the MSM tool is very simple, you just have to download it from this link.
hotdogt_11_O.01_190920 op7t tmo usa patched unlock bootloader.7z
drive.google.com
NOTE: It only works on Windows pc
1. Unzip the contents of the RAR into a
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it is delayed)
6. A message appears informing that the equipment is damaged, do not be careful.
7- Now you must unlock the bootloader with a command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8. Now run this command while the cell phone is connected in Fastboot mode.
fastboo ...
Hi
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: Only works on Windows PC
1. Unzip the contents of the RAR into a folder
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it's time consuming, be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically start in fastboot mode and show a menu, but if it doesn't and instead starts on the T-mobile screen, you must force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you must unlock the bootloader with command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this moment your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, in the command line, run the file flash-all.bat
12. When the phone restarts and the yellow and white letters appear informing that the phone is unsafe due to having the bootloader unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-The PC will detect the phone again in fastboot mode, and continue flashing
-Leave the phone and the pc still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (don't pay attention)
13. Finally the equipment will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just force it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before blocking the bootloader again (if you plan to do it) first update via OTA, to the most recent version of Oxygen, otherwise it will crash the system again and you will have to repeat the whole process.
Click to expand...
Click to collapse
Oh wow that was a long and well defined post. Thank you for taking the time to type it out.
As it happens, I fixed my issue already (IDK if there's a solved flair for XDA or something?). I downloaded the latest (10.0.15) MSM Tool from the XDA page, held the vol-up and vol-down for 30 seconds this time (as per advice from discord users) got the phone into edl mode, connected to a usb 2.0 port and let msm tool do it's thing. Everything is working perfectly now.
I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.
Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.
Āryan-9909 said:
Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.
Click to expand...
Click to collapse
Yes, theyll just change out the motherboard
HueyT said:
Yes, theyll just change out the motherboard
Click to expand...
Click to collapse
If they're going to just change the motherboard, I wonder what the EDL mode is meant for. Anyways, I won't go for motherboard change one can buy a new and better phone at that kinda price.
Anyways, I Fixed it through EDL method, you have to hold vol up and down simultaneously and immediately connect to windows (while still holding both buttons) via original USB cable. Check with Device manager if your device shows up, it's easy enough but you might have to keep trying to you get it right. Thereafter, disable driver verification in windows and if Sahara communications failed message appears in msm tool, turn off phone and repeat the procedure again.
The repair peeps only fix hardware and not software. It's more cost effective for them to swap out hardware faster than messing with msmtool like us
Āryan-9909 said:
I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.
Click to expand...
Click to collapse
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.
scoped_ar07 said:
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.
Click to expand...
Click to collapse
You don't have to hold buttons for that long, you can immediately connect it to PC. There is usually a sound to indicate that a new device has been connected to windows, you can also keep device manager open for confirmation. This video really helped.
After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?
hightech316 said:
After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?
Click to expand...
Click to collapse
Qualcomm 9008 drivers too?
HueyT said:
Qualcomm 9008 drivers too?
Click to expand...
Click to collapse
Yes.
I went ahead and ran another factory reset via recovery, no luck.
New cable, another PC?
HueyT said:
New cable, another PC?
Click to expand...
Click to collapse
Tried both, my desktop would always connect, adb, fastboot, etc.
I had just just freshly installed oneplus drivers including qualcomm on my laptop. Device was not recognized before driver installation or after.
Figure id try on my Mac, and linux laptop. no dice.
ADB is enabled.
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" . Not phone will not even be seen