Related
Hi
I have tried a lot to unbrick my Lenovo Vibe Shot. Now I am helpless and looking for some workable solution:
I used Lenovo Smart Assistant to download a proper firmware so it turned out it is:
z90a40_USR_S363_1606250500_Q202533.1_ROW.zip
I tried to use Lenovo Smart drive assistant to update ROM or Device Rescue, but both wont detect phone
The phone default Lenovo recovery can be loaded by pressing VOL+, VOL- and power button, and then releasing power button
when logo appears. I used an Update.zip in 8GB mem card and used the option: ‘install update package’ then it complete the process 100% I was happy that I was going to get my phone unbrick
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but when it asked for reboot and I rebooted it, it vibrated
2 times, first it vibrated, and showed logo of Lenovo for 1 second then it vibrated long like 2/3 seconds and turned off. I repeated many times these steps but still it behaves same.
Another thing is after brick, it showed this in My Computer:
And with each new drive letter it shows following. I tried to format but it then says Write protected error.
Then tried 3 or 4 methods from following
https://boycracked.com/2016/02/07/stock-rom-frimware-lenovo-vibe-shot-z90/
I was just simply not able to use Qualcomm Lenovo HS-USB QDLoader 9008
as on all my PCs it is detecting as some Diagnostic 9006 version instead of above.
Tried on different PCs and ROMs/Firmwares titling Lenovo Vibe Shot, Either the following error or Delete drive layout comes.
Then I followed next method for QFIL but still it cannot download it.
Please help me how can get things right, I have tried on 3 PCs (2 of them were 32 bit windows, and a Win 10 laptop)
Still no luck
I have the same problem. tried everything, QFIL MiFlash Recovery. no luck. Partition tool does not delete the partition. tried deleting all of them and creating a new 1. nothing happened. the pc no longer detected the multiple write protected drives but the partition tool still does and when I plugged it in a different PC, the multiple write protected drives appeared again. Hope we find a solution for this. I haven't been sleeping that much for the past week because of this.
babui21 said:
I have the same problem. tried everything, QFIL MiFlash Recovery. no luck. Partition tool does not delete the partition. tried deleting all of them and creating a new 1. nothing happened. the pc no longer detected the multiple write protected drives but the partition tool still does and when I plugged it in a different PC, the multiple write protected drives appeared again. Hope we find a solution for this. I haven't been sleeping that much for the past week because of this.
Click to expand...
Click to collapse
I figured it out from my semi-sleepless nights. But b4 the solution that worked for me, I had to
learn a lot out of my desperation to finally get it worked on the day I decided to hand over to
some technical guy from local market
The full comment form Francisco Kadzi helped me finally do it from following youtube link:
https://www.youtube.com/watch?v=SmMg00Wqabc&t=1s
Besides I had to take care of many things. First here are the things I was doing wrong:
- Not taking care of a heavily charged phone, I would try to unbrick after just 1 hour
or less charging from a total uncharged device.
- I was going to a backward step whenever I failed on something (Reboot in
fastboot mode, trying with QFIL etc.). Whereas many different forums (mainly XDA),
people were saying to try again and again.
- I was using improper ROMS or flash files my device was: Z90a40_USR_S363_1606250500_Q202533.1_ROW
- When I would see 9006 mode again I would be disappointed and would try different solution.
The correct thing to try was uninstall this driver and then connect the device again with
PC in fastboot mode .
Then I used Lenovo Smart Assistant and got this proper file:
Z90a40_USR_S363_1606250500_Q202533.1_ROW
OK read my first post to know what problems I faced, but at the end the multiple
partitions were not really the problem. The actual problem was getting 9008 mode
in Device Manager of my Windows 7. I always got it as Diagnostics 9006 mode. One
I started getting 9008, things went in my way gradually. So the person posting on
above comment from youtube link helped me
Am a happy fellow at the moment and will help anyone with same problem if needed
My email id is: usman400 on G Mail
usman400 said:
I figured it out from my semi-sleepless nights. But b4 the solution that worked for me, I had to
learn a lot out of my desperation to finally get it worked on the day I decided to hand over to
some technical guy from local market
The full comment form Francisco Kadzi helped me finally do it from following youtube link:
https://www.youtube.com/watch?v=SmMg00Wqabc&t=1s
Besides I had to take care of many things. First here are the things I was doing wrong:
- Not taking care of a heavily charged phone, I would try to unbrick after just 1 hour
or less charging from a total uncharged device.
- I was going to a backward step whenever I failed on something (Reboot in
fastboot mode, trying with QFIL etc.). Whereas many different forums (mainly XDA),
people were saying to try again and again.
- I was using improper ROMS or flash files my device was: Z90a40_USR_S363_1606250500_Q202533.1_ROW
- When I would see 9006 mode again I would be disappointed and would try different solution.
The correct thing to try was uninstall this driver and then connect the device again with
PC in fastboot mode .
Then I used Lenovo Smart Assistant and got this proper file:
Z90a40_USR_S363_1606250500_Q202533.1_ROW
OK read my first post to know what problems I faced, but at the end the multiple
partitions were not really the problem. The actual problem was getting 9008 mode
in Device Manager of my Windows 7. I always got it as Diagnostics 9006 mode. One
I started getting 9008, things went in my way gradually. So the person posting on
above comment from youtube link helped me
Am a happy fellow at the moment and will help anyone with same problem if needed
My email id is: usman400 on G Mail
Click to expand...
Click to collapse
I had problem like you, and i couldnt solve it so i sent it to repair shop and waiting now to hear from them.
I managed to get 9008 port, tryed to downgrade, upgrade, flash would complete, i tried literaly all row and china rom, no way to boot up sucessfully.
I even flashed twrp and tryed cm rom and mokee, i could boot after lenovo sign.
But i have same situation like you, many partitions and thats all. I think problem is read only partitions...
Can you tell me what drivers did you use?
I was able to fix exactly same problem this morning an hour before important meeting. All contacts and location puns were on gdrive and hadn't slept full night. You need to download correct qualcom drivers. Enter in Google: android qualcom urdu checked. Inside the zip unpack "checked" folder, right click and select install all infs. Run adb reboot bootloader while phone attempts to boot, when command succeeds run adb reboot edl, or fastboot reboot-edl whichever works. Keep miflash open and refresh. Then you see a short Comm port name. Now shoot flash with any rom that you have. If you do Chinese version then SNAPit lags badly, install correct version.
To sum up, focus on implementing correct qualcom drivers. In windows 10 run command testsign off and reboot in advance.
Actually I bricked my phone a whole lot of times even after my post thats because once I knew that it is just soft bricked and I can get it back somehow, I got the confidence and tried advanced things that bricked my phone again and again
And it was only the recent time (around 3 weeks ago), that I figured the 100% working 9008 method for my phone
actually u have to drain the battery completely out then it will get 9008 mode to do it u shall try turning your phone on again and again so that battery goes off
For example: Press Power button for a few seconds to turn it on.
Or press 3 buttons at same time (VOL+, VOL- and Power), then release only Power button when you get vibration. Then after 2 seconds release both VOL buttons as well (this is for going to recovery mode)
This way you can drain all battery of phone, and you will know when the battery is all gone when you will press the Power button and phone will not show any LED light or screen light, it will just vibrate and will be off
Now you connect ur phone to PC in following way:
If at bricking you you were on Lollipop (Android 5): Pressing VOL+ key and plug the USB cable in WITHOUT PRESSING POWER BUTTON ! 9008 will open use Qfil to flash the ROM u want
OR If at bricking you were on Marshmallow (Android 6): Plug the USB cable in phone, then connect cable to PC and exactly at the same time press power button (some times u dont need to press power button so try with both options). Then if you see 9008 mode in Qfil, then immediately press the Download button in Qfil
If you see Qfil error then repeat the above process to get 9008 mode and use miflash instead of Qfil miflash worked for me better than Qfil from such situation as Qfil often gives error in between
And when you get the flashing 100% then phone will either auto restart or you have to restart it manually Using Qfil it shows u message when it is restarting the phone, and I think using miflash it just says process 100% complete then u have to restart phone yourself
Remember at this point (after restart) connect your phone charger properly in a electricity power socket instead of PC as the battery was already drained so you need to charge the device while it shows the long booting process due to new ROM flashed.
Good luck,
I had the same problem from two days my phone is bricked and when i connect it to my pc too many partitions appears and when flashing by miflash it says (incorrect function) and i tried too many methods without any good result
But I finally unbricked my vibe shot successfully
At first i downloaded Qualcomm Lenovo HS-USB QDLoader 9008 driver definition, i searched for it by google until i get a zip file with the driver definition. i installed it manually from device manager on computer when my phone was connected to pc.
After that i downloaded an official z90a40_s240 for flashing via Qfil.
Steps:
1- disconnect your phone
2- go to recovery mode by ( holding power button with volume+ and volume- at the same time) until booting to recovery mode.
3-In recovery mode chose English then power off
4- open Qfil and get it ready to flash the official firmware
5-connect the USB to your pc then keep holding volume up and connect your phone to USB.
6- your phone screen should be turned off, also the LED light and you should see 9008 mode
7- click to download button and the flashing will start.
And congratulations your phone unbricked successfully ?
I have facing same problem on my phone. Could you help to show me hơ to unbricked it . Thanks you so much.
Hi guys,
Looks like I have a big problem now on my Mi5s Plus. After flashing a chineese developer ROM 6.12.29 in EDL mode I got permanent MI.COM icon on the screen, so device is bricked, power button only restarts the icon. The worst thing is I cannot enter EDL mode anymore since I cannot switch off the device. I have deep flash cable, but it doesn't help, because the phone has to be turned off before release a button. The bootloader is locked, I have permission to unlock, but it doesn't work, saying account on the device is different to account I logged in.
Does anybody know how can I enter again EDL mode in this situation? How can I proceed to get the device unbricked? Please suggest.
I have tried chinees MiFlash to flash the ROM, but also without result (stops in the beginning).
Many thanks in advance.
USB cable mod, search for "USB cable EDL mode"
zebster said:
USB cable mod, search for "USB cable EDL mode"
Click to expand...
Click to collapse
I could find only the topic with modified fastboot, tried, no effect, restart to the same logo.
Could you please give me a link of the post which you think will help me.
Many thanks!
http://en.miui.com/thread-324300-1-1.html
As simple as that.
You have to join the two wires and then connect it to the usb port on PC.
To flash you have to separate them as a normal cable.
zebster said:
http://en.miui.com/thread-324300-1-1.html
As simple as that.
You have to join the two wires and then connect it to the usb port on PC.
To flash you have to separate them as a normal cable.
Click to expand...
Click to collapse
It doesn't work in my situation, I've been trying already since 4 days, because to use this method and cable the phone has to be switched off, and this is not possible, because it always restarts when I press power button. I tried to switch it off in fastboot mode, leaving it in fastboot mode not connected to anything, then after approx. one minute the screen is fully off, but when I connect deep flash cable with joined wires and release the wires, it is just switching on to the same MI.COM logo and then the battery charging screen...((( The cable was working when device was alive, so contacts are correct (black and green)...
I need either the way how to bypass bootloader locking in fastboot, or another way how to reach EDL mode.
I really thought it is always possible to go into EDL with deep flash cable, but looks like it is not... Maybe I use the wrong moment to release the button. I insert cable into PC and wait 3 seconds, then release the button... Tried many times and different moments. But when device was alive it was working immediately and always...(((
Are there other ideas, guys?
Please help!!!
DR2010 said:
It doesn't work in my situation, I've been trying already since 4 days, because to use this method and cable the phone has to be switched off, and this is not possible, because it always restarts when I press power button. I tried to switch it off in fastboot mode, leaving it in fastboot mode not connected to anything, then after approx. one minute the screen is fully off, but when I connect deep flash cable with joined wires and release the wires, it is just switching on to the same MI.COM logo and then the battery charging screen...((( The cable was working when device was alive, so contacts are correct (black and green)...
I need either the way how to bypass bootloader locking in fastboot, or another way how to reach EDL mode.
I really thought it is always possible to go into EDL with deep flash cable, but looks like it is not... Maybe I use the wrong moment to release the button. I insert cable into PC and wait 3 seconds, then release the button... Tried many times and different moments. But when device was alive it was working immediately and always...(((
Are there other ideas, guys?
Please help!!!
Click to expand...
Click to collapse
No, you don't have to have the phone swithed off.
Connect the cable with the mod and then press the power button until it shutsdown.
When it restarts it will be already on EDL mode.
I had exactly the same problem as you.
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
With the phone as you have do this:
- use the modded usb cable and connect the phone to PC
- press power button until the phone restarts
- disconnect usb from PC
- use normal USB cable to connect phone to PC
Now you should see the "Qualcomm HS -USB QDLoader 9008" device on you PC device manager, EDL mode on the phone with a black screen
zebster said:
No, you don't have to have the phone swithed off.
Connect the cable with the mod and then press the power button until it shutsdown.
When it restarts it will be already on EDL mode.
I had exactly the same problem as you.
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
With the phone as you have do this:
- use the modded usb cable and connect the phone to PC
- press power button until the phone restarts
- disconnect usb from PC
- use normal USB cable to connect phone to PC
Now you should see the "Qualcomm HS -USB QDLoader 9008" device on you PC device manager, EDL mode on the phone with a black screen
Click to expand...
Click to collapse
Unfortunately it doesn't work, as I told above(((
When I press the power button and do not release it, the phone cyclically restarts independently if it is connected to something or not and with mod cable or not...
When did you release a power button?
1. Have you tried to press both power and volume up to enter recovery? If you can, select download to flash with MIflash.
2. Can you enter fastboot mode? I so:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
zebster said:
1. Have you tried to press both power and volume up to enter recovery? If you can, select download to flash with MIflash.
2. Can you enter fastboot mode? I so:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Click to expand...
Click to collapse
Dear zebster, many thanks for your kind efforts to help me.
Yes, I can enter both - standard recovery and fastboot. In standard recovery there is no any selection possible. MiFlash doesn't see anything in this mode as expected.
There is only animated (connected/disconnected) cable and adb interface available on the phone when I connect in this mode to PC, but chineese Mi PC Suite can see the phone, starts flashing even, but hangs on 5% approximately, saying there was an error, please try again (of course doesn't help).
Also I have tried before modified fastboot utility from the link to enter EDL, only restarts the phone, like I pressed the power button, and I get again lovely MI.COM logo...(((
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you can see this option you should be able to flash thru miflash
zebster said:
if you can see this option you should be able to flash thru miflash
Click to expand...
Click to collapse
no, I have just standard recovery from official ROM (but God knows from which one now...): on the black background screen the white edges of smartphone are pictured and the USB cable below. When I connect device to PC cable becomes connected, when disconnect - disconnected. That's all. You have different recovery...
You have this:
My advice is to download the original rom and flash it thru fastboot:
http://en.miui.com/download-314.html
zebster said:
You have this:
My advice is to download the original rom and flash it thru fastboot:
http://en.miui.com/download-314.html
Click to expand...
Click to collapse
As far as I know it would work if the bootloader would be unlocked, but it is locked!
And the unlocking software says that account is different (I even have official permission to unlock the bootloader). So, I got stucked in a circle((((
I even tried it yesterday, but MiFlash itself in this case crashes...
DR2010 said:
As far as I know it would work if the bootloader would be unlocked, but it is locked!
And the unlocking software says that account is different (I even have official permission to unlock the bootloader). So, I got stucked in a circle((((
I even tried it yesterday, but MiFlash itself in this case crashes...
Click to expand...
Click to collapse
I've flashed mine with bootloader locked in EDL mode.
If you can use Miflash with bootloader you can flash it even with bootloader locked.
Download the oficial ROM and flash thru MIflash.
To unlock you may need to flash the China Developer ROM.
zebster said:
I've flashed mine with bootloader locked in EDL mode.
If you can use Miflash with bootloader you can flash it even with bootloader locked.
Download the oficial ROM and flash thru MIflash.
To unlock you may need to flash the China Developer ROM.
Click to expand...
Click to collapse
Thanks, but again doesn't work on my device...
As I expected, MiFlash 2016.12.14.1(Release) in fastboot mode says that "Partion flashing is not allowed" and finishes with error...
The same as I do it manually via fastboot command interface...(((
Which version of MiFlash did you use? Where can I download it?
Use miflash 2015.10.28.0
Was the version that worked for me.
You can also try to enter EDL on fastboot using:
fastboot oem edl
zebster said:
Use miflash 2015.10.28.0
Was the version that worked for me.
You can also try to enter EDL on fastboot using:
fastboot oem edl
Click to expand...
Click to collapse
fastboot oem edl needs the bootloader to be unlocked.
do you have a link to download miflash 2015.10.28.0?
thanks!
I had the same problem with my Mi 5s.
This is what I eventually did to solve it (from memory - Google a bit for detailed instructions):
Download the Chinese version of Mi PC Suite (It has more options than the english version)
You can then recover from bootloop, by using it's recovery;
- Start MiPCSuite
- Boot phone to recovery (volume up + power)
- Select "Connect with MiAssistant" (bottom option)
- Phone should be detected, and a popup will show on PC with recovery options.
I believe it could download the latest version for you, or you can select a downloaded .zip file to flash.
It will have to be the same type that was previously installed (during the failed flash). So you can not go from Dev to Stable, or from CN to Global.
Go here for (Mi 5s) roms: http://en.miui.com/download-314.html#456
On the PC it immediately said flash failed, but the phone re-flashed the ROM anyway.
Hope this helps some...
P.S. Used my old phone with Google Translate App to read Chinese (Instant translation with the camera)
P.P.S. Other options won't work, because Xiaomi locked out the EDL in Chinese Developer versions. Even with the Deep Flash cable.
I'm now running Chinese Dev. version, and can not enter EDL anymore. I'll have to wait for bootloader unlock before I can flash again...
P.P.P.S. It seems I was wrong about not being able to switch: just flashed Global ROM 8.0.3.0 (From Chinese Dev. ROM 7.1.20) using the same method.
Again on the PC it said flashing failed (immediately) and stays at 0%, but the phone shows it's updating...
After flashing had to clear/reset data (again from MiPCSuite - Middle option in popup - Red button in 2nd popup), otherwise all apps keep crashing.
Because I'm back to Global ROM now, I can also use my Deep Flash cable again.
Dear Zappo, many thanks for your reply! I still fighting with the problem... already tried to disconnect the battery, not going to EDL as well.
I think only JTAG-flasher will help in my case (cannot get it, because I'm out of "civilisation" for a long time), but you have given to me the last hope))
Could you please make a screenshot where you did see the option "Connect with MiAssistant". Which version of chinese MiPCSuite did you use?
I used version 2.3.0.9091, it hangs on approximately 5% (on the phone) and does not proceed... was waiting for 30 minutes, no progress... I used it in a way to download the latest ROM and then install it.
My dear friend Zappo, I still do not believe, but I had success recovering this brick with chinese MiPCSuite v2.3.0.9091. It just downloaded the latest ROM for the device from internet and was flashing it during 1 hour 10 minutes!!! Before I had no success because I was waiting only half an hour, not more!)) But exactly after half an hour it continues and finalizes successfully!!! Another reason of my success I think could be (but less probable) that I have opened a device some days ago and disconnected the battery in order to try to get in EDL mode without the power (but was also not successful). Also today before I started MiPCSuite I have switched on the device from completely OFF state with Volume+ and Power button... So, I really do not know how the success come, but now I'm really happy!!! Many, many, many thanks for your help and for second breath )))
My device is a Note 8 Ginkgo, but for some reason TWRP recognize it as a Willow (Note 8T), so only allows me to flash Willow stuff (if I try to flash .zip for Ginkgo it shows me an error message saying that the device is a Willow).
To install TWRP first I flash the vbmeta.img.
I was able to install LineageOS 17 for Willow on it, and work without big issues (GCam doesn't work, but any other camera app does).
But I was trying to install a GSI LineageOS 17 ROM, and following a tutorial that teach how to flash a Android 10 GSI, I may have commit a huge mistake.
This tutorial guide to wipe everything expect Internal Storage and flash the firmware before the ROM, but I was afraid to wipe the Vendor layer/partition on TWRP, so I uncheck it and wipe the rest.
After wiping, I flash the firmware for Willow using TWRP and reboot.
When the device tried to reboot, it just blink a black screen for 1,5 second without anything appearing and turn off.
Trying to hold the power button lead to the same, but the device vibrate first.
Holding the power button plus volume down shows the Fastboot image for the same 1,5 second and turn off again.
If I connect it to the power cable, its stay with this behave in a loop, blinking the screen while the cable is on.
So, I don't know if the mistake I made was by flashing the Firmware without wiping Vendor, or if was because I flash the Firmware for Willow, or both, or because I use TWRP instead doing by Fastboot.
Just to clarify my question, did it is bricked or there is a solution?
A video of this behave down bellow.
https://youtu.be/B28Np_e2APs
Rodolfo Candido said:
My device is a Note 8 Ginkgo, but for some reason TWRP recognize it as a Willow (Note 8T), so only allows me to flash Willow stuff (if I try to flash .zip for Ginkgo it shows me an error message saying that the device is a Willow).
To install TWRP first I flash the vbmeta.img.
I was able to install LineageOS 17 for Willow on it, and work without big issues (GCam doesn't work, but any other camera app does).
But I was trying to install a GSI LineageOS 17 ROM, and following a tutorial that teach how to flash a Android 10 GSI, I may have commit a huge mistake.
This tutorial guide to wipe everything expect Internal Storage and flash the firmware before the ROM, but I was afraid to wipe the Vendor layer/partition on TWRP, so I uncheck it and wipe the rest.
After wiping, I flash the firmware for Willow using TWRP and reboot.
When the device tried to reboot, it just blink a black screen for 1,5 second without anything appearing and turn off.
Trying to hold the power button lead to the same, but the device vibrate first.
Holding the power button plus volume down shows the Fastboot image for the same 1,5 second and turn off again.
If I connect it to the power cable, its stay with this behave in a loop, blinking the screen while the cable is on.
So, I don't know if the mistake I made was by flashing the Firmware without wiping Vendor, or if was because I flash the Firmware for Willow, or both, or because I use TWRP instead doing by Fastboot.
Just to clarify my question, did it is bricked or there is a solution?
A video of this behave down bellow.
https://youtu.be/B28Np_e2APs
Click to expand...
Click to collapse
Maybe you do have a Willow and not a ginkgo..
Try holding power button for 10 secs or something....also what happens if you press the vol up and power button
You use the buttons to go on the fastboot, what happen if you use the commands on adb fastboot.
If you are lucky and have access to the fastboot then your phone is totally salvable.
First you need to download an official fastboot rom (you need to be sure of your phone though check your box 8= Gingko 8t= willow)
I personally used this website and it did work (I got a Willow)
Willow: https://mirom.ezbox.idv.tw/en/phone/willow/
Ginkgo: https://mirom.ezbox.idv.tw/en/phone/ginkgo/
Then proceed to flash it using miflash.
I used this tutorial and it did fix my phone https://www.youtube.com/watch?v=yBK-duw43BQ
Hope it will work. If you have access to fastboot and it is just the screen flickering it worth a try.
---------- Post added at 03:50 AM ---------- Previous post was at 03:31 AM ----------
If you don’t have access to the box another way to check what fastboot Rom to get is to look at the chin of the phone on the note 8T it is slightly bigger.
Check on those photos
Redmi Note 8 (Ginkgo)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Redmi Note 8T (Willow)
If you are not able to access fastboot or recovery mode then I am afraid that you have bricked your phone and the only way to repair it will be by going to the official service centre .
Also, please try to access the recovery mode (only saying this because you haven't talked about it). If you are able to enter into the recovery mode then the recovery process will be easy as you only have to wipe all partitions (including vendor) and installing a new ROM.
islander29 said:
You use the buttons to go on the fastboot, what happen if you use the commands on adb fastboot.
If you are lucky and have access to the fastboot then your phone is totally salvable.
First you need to download an official fastboot rom (you need to be sure of your phone though check your box 8= Gingko 8t= willow)
I personally used this website and it did work (I got a Willow)
Willow: https://mirom.ezbox.idv.tw/en/phone/willow/
Ginkgo: https://mirom.ezbox.idv.tw/en/phone/ginkgo/
Then proceed to flash it using miflash.
I used this tutorial and it did fix my phone https://www.youtube.com/watch?v=yBK-duw43BQ
Hope it will work. If you have access to fastboot and it is just the screen flickering it worth a try.
---------- Post added at 03:50 AM ---------- Previous post was at 03:31 AM ----------
If you don’t have access to the box another way to check what fastboot Rom to get is to look at the chin of the phone on the note 8T it is slightly bigger.
Check on those photos
Redmi Note 8 (Ginkgo)
Redmi Note 8T (Willow)
Click to expand...
Click to collapse
Nope lol, I have a Ginko and the chin is just as big as the willow image. The picture they used to advertise the Note 8 is fake, with a much smaller chin than reality.
A better test is whether it has a notification led. Willow does not have one
One more thing try to boot into fastboot mode even if your screen is turning on/off. This behaviour is may be because you have flashed willow firmware on ginkgo.
If your MI Flash tool is recognising your device then you can save your device.
Follow these steps to flash from fastboot mode.
https://c.mi.com/thread-1712713-1-1.html
Thank you guys for the response, but as I said, it doesn't enter neither Fastboot or Recovery. It behaves exactly the same when I try to boot, blinking the screen and turning off.
Asking for help in the amazing group in Telegram, a very helpful user said that could be Kernel Panic, and I should enter EDL mode to be able to fix.
He recommended to take the phone in a Service Center, where they could solve.
I will do that and post the results later.
I have the same problem that you, twrp says my device is willow, but in fact is ginkgo, hope you can solve your problem and someone someday figure out why this stupid device have an identity crisis
Rodolfo Candido said:
Thank you guys for the response, but as I said, it doesn't enter neither Fastboot or Recovery. It behaves exactly the same when I try to boot, blinking the screen and turning off.
Asking for help in the amazing group in Telegram, a very helpful user said that could be Kernel Panic, and I should enter EDL mode to be able to fix.
He recommended to take the phone in a Service Center, where they could solve.
I will do that and post the results later.
Click to expand...
Click to collapse
Jos_Hdez22 said:
I have the same problem that you, twrp says my device is willow, but in fact is ginkgo, hope you can solve your problem and someone someday figure out why this stupid device have an identity crisis
Click to expand...
Click to collapse
hope both of you flashed the latest recovery..if you have the older version then flash recovery.img via recovery itself and just select recovery partition while flashing...although I do know few other guys who have the same issue. I might know a workaround though..If you are absolutely sure it's a ginkgo, and you are flashing a ginkgo rom then in the rom.zip you can go to META-INF/com/google/android/updater-script->here remove the following line:
Code:
getprop("ro.product.device") == "ginkgo" || abort("E3004: This package is for \"ginkgo\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Now recovery won't verify your device and you can flash the proper rom. Although don't extract your full rom.zip. Just open(not extract) with winrar, go to the mentioned path and extract the updater-script, make changes with notepad++ and drag the new modified updater-script back in the same path.
Alternatively you can visit service center but you cannot explain them this exact issue as unlocking bootloader/flashing roms/root=no warranty.So you might have to boot device in EDL mode or brick your device somehow so it's in edl mode and then visit service center(I STRONGLY DO NOT RECOMMEND BRICKING YOUR OWN DEVICE.)
Hope it helps for now
will update you if I find any proper solution.
Weird result actually
Bro I did the same mistake Did you made it to fix it I was reading something about buy a EDL cable or you can made your own in home( you will need a micro usb cable and type c adapter look for it how to make one in YouTube but in my country we are under Quarantine I cant get the goddam usb type c adapter well with that cable you boot in EDL Mode and mi flash will recognize your phone like qualcom port 9008 you will able to bring him back to life Hope this info help you In my case I need to wait the end of quarantine and buy my usb type c adapter to fix mine tell me if it work for you
Greetings from panama city stay safe
Sorry for.my crappy english with doesnt talk english here
jean000 said:
Bro I did the same mistake Did you made it to fix it I was reading something about buy a EDL cable or you can made your own in home( you will need a micro usb cable and type c adapter look for it how to make one in YouTube but in my country we are under Quarantine I cant get the goddam usb type c adapter well with that cable you boot in EDL Mode and mi flash will recognize your phone like qualcom port 9008 you will able to bring him back to life Hope this info help you In my case I need to wait the end of quarantine and buy my usb type c adapter to fix mine tell me if it work for you
Greetings from panama city stay safe
Sorry for.my crappy english with doesnt talk english here
Click to expand...
Click to collapse
EDL cable and everything won't work..better visit a service center.... Xiaomi has changed it's policies and you can't flash anything if your phone is in EDL mode...it requires authorized accounts which Xiaomi provides only to service centers..
the_weird_aquarian said:
EDL cable and everything won't work..better visit a service center.... Xiaomi has changed it's policies and you can't flash anything if your phone is in EDL mode...it requires authorized accounts which Xiaomi provides only to service centers..
Click to expand...
Click to collapse
Bro I dont Know about your country but here in panama we are under quarantine everything its close and its going to be for a long long time and I live in panama there´s no oficial center here not yet
jean000 said:
Bro I dont Know about your country but here in panama we are under quarantine everything its close and its going to be for a long long time and I live in panama there´s no oficial center here not yet
Click to expand...
Click to collapse
Like I said...EDL mode won't help you..trust me....you will gain nothing by buying that EDL cable or anything because you won't have an authorised account to flash..
I got the same problem... Any fix yet? Did you fix it?
same here, with a willow. Any solution?
Try the xiaomitool2
Authorized account for flashing ginkgo/another device t
JohnyVole said:
I got the same problem... Any fix yet? Did you fix it?
Click to expand...
Click to collapse
U can send messages if U need Authorized account for flashing ginkgo/another device t.me/tesbot99
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pmppm said:
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
View attachment 5788047
Click to expand...
Click to collapse
From the image you posted, it looks like you are using the wrong MSM version. "Device not match image".......
TheGhost1951 said:
From the image you posted, it looks like you are using the wrong MSM version. "Device not match image".......
Click to expand...
Click to collapse
I used this exact version on this phone like 2 days ago, I dont think it is a version problem, but thanks for the help!
And it is pretty interesting.. As far as i know EDL connection only alive for 5-10 sec, but currently MsM tool shows Connected until my phone was plugged in (even after refreshing it)
pmppm said:
I used this exact version on this phone like 2 days ago, I dont think it is a version problem, but thanks for the help!
Click to expand...
Click to collapse
Just like the other posted said. If it says that error, it means that your device ID is different. Did you possibly use the India MSM which would change your device ID and not allow you to use the one you were using before? You can also try unchecking sha265check and check use lite firehose and see if it works that way.
TheSayaMan said:
Just like the other posted said. If it says that error, it means that your device ID is different. Did you possibly use the India MSM which would change your device ID and not allow you to use the one you were using before? You can also try unchecking sha265check and check use lite firehose and see if it works that way.
Click to expand...
Click to collapse
Okay so basically, you're both right. I got the Global version, but with the correct MsM version for that did not worked. The solution was to use the Indian version to unbrick it, then ofc switch back to the global. I took this idea from this post, It's seemed so idiot to do it that way, but I had nothing to lose. Thanks again!
pmppm said:
Okay so basically, you're both right. I got the Global version, but with the correct MsM version for that did not worked. The solution was to use the Indian version to unbrick it, then ofc switch back to the global. I took this idea from this post, It's seemed so idiot to do it that way, but I had nothing to lose. Thanks again!
Click to expand...
Click to collapse
Once you used the Indian MSM, then to go global you have to install the updater tool from Google Play store to choose the version you want and install it that way. I believe.....
TheGhost1951 said:
Once you used the Indian MSM, then to go global you have to install the updater tool from Google Play store to choose the version you want and install it that way. I believe.....
Click to expand...
Click to collapse
I don't believe it's available in play store, have to Google search for it but otherwise your right, once you use the India MSM, your device ID is permanently changed and can no longer use the reg MSM for the device.
TheSayaMan said:
I don't believe it's available in play store, have to Google search for it but otherwise your right, once you use the India MSM, your device ID is permanently changed and can no longer use the reg MSM for the device.
Click to expand...
Click to collapse
Would this not work?
I am not sure how OnePlus implements it, but many devices have a Qualcomm USB mode or "Emergency Download Mode" for performing a low level reflash of basic firmware such as the bootloader. Most often, when a device screen doesn't come on, but it vibrates and a PC shows a connected device, this is the case - the PC has detected the QUSB mode.
Unfortunately, Qualcomm does not make their Qualcomm Product Support Tool available to the public, and most OEMs do not provide the necessary binaries to restore the bootloader. The device cannot be repaired or restored without these tools, unless the mainboard is replaced. Unfortunately in this case, I believe that is your only option.
V0latyle said:
I am not sure how OnePlus implements it, but many devices have a Qualcomm USB mode or "Emergency Download Mode" for performing a low level reflash of basic firmware such as the bootloader. Most often, when a device screen doesn't come on, but it vibrates and a PC shows a connected device, this is the case - the PC has detected the QUSB mode.
Unfortunately, Qualcomm does not make their Qualcomm Product Support Tool available to the public, and most OEMs do not provide the necessary binaries to restore the bootloader. The device cannot be repaired or restored without these tools, unless the mainboard is replaced. Unfortunately in this case, I believe that is your only option.
Click to expand...
Click to collapse
It is called the MSM Download Tool. And it is device specific and ready available.
TheGhost1951 said:
It is called the MSM Download Tool. And it is device specific and ready available.
Click to expand...
Click to collapse
Oh, specifically for the OnePlus. Good to know. I suppose I'm of absolutely no help here
Odin is for flashing Samsung devices. Samsung and now OnePlus are the only two devices I have worked with.
pmppm said:
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
View attachment 5788047
Click to expand...
Click to collapse
India device or global devices
And tip
Reboot to edl
Power off the phone
And press and hold pressed the voll up and voll down
And putt in the usb cable and hold pressed the voll up and voll down
And try msm tool
V0latyle said:
Oh, specifically for the OnePlus. Good to know. I suppose I'm of absolutely no help here
Click to expand...
Click to collapse
Not only specific to OnePlus but also specific to OOS versions.
Might try to uninstall Qualcomm drivers, make sure PC driver signing is disabled. Reboot PC, then re-install latest Qualcomm drivers, re-boot PC and try again with MSM tool. The windows sound when plugging in before is the sound of a device plugged in but couldn't recognize it and threw it out of device manager. That was the reason for the TWO sounds you heard. Also try holding down on vol + - and pressing power and holding it down to try to boot into fastboot mode. If it does, flash boot boot TWRP.img and then boot into edl from there with phone connected to PC and MSM tool in start mode ready to flash as soon as device is connected.
I just unboxed new OnePlus 9 Pro, then i was installing an update and during update phone’s case held power off button, so phone turned off and showing current error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can’t boot in Android and in Recovery mode. Everything working is Fastboot mode. I was trying to “unbrick” phone, installing Fastboot ROM( files like boot.img, recovery.img and so on),but in cmd on my pc shows while using commands like: “fastboot flash boot boot.img” or fastboot -w“, only error “Failed (remote:’Erase is not allowed in Lock State’)”.
Now i want to unlock device state if it is possible.
Remind that phone was just unboxed, so it doesn’t have enabled lever OEM unlocking.
try 'fastboot --set-active=other' or unbrick with MSM Download tool or https://github.com/bkerler/edl
chizari said:
I just unboxed new OnePlus 9 Pro, then i was installing an update and during update phone’s case held power off button, so phone turned off and showing current error.
View attachment 5813705
I can’t boot in Android and in Recovery mode. Everything working is Fastboot mode. I was trying to “unbrick” phone, installing Fastboot ROM( files like boot.img, recovery.img and so on),but in cmd on my pc shows while using commands like: “fastboot flash boot boot.img” or fastboot -w“, only error “Failed (remote:’Erase is not allowed in Lock State’)”.
Now i want to unlock device state if it is possible.
Remind that phone was just unboxed, so it doesn’t have enabled lever OEM unlocking.
Click to expand...
Click to collapse
bro just use the msm tool. there's a tool for every variant of the 9 pro (LE2120-2125). Look for the post on our Device xda and use it.
aIecxs said:
try 'fastboot --set-active=other'
Click to expand...
Click to collapse
cmd says: fastboot: unknown option -- set-active=other
I think it doesn’t understand what‘s --, maybe ’cause i dont have libraries or drivers
ishansnp said:
bro just use the msm tool. there's a tool for every variant of the 9 pro (LE2120-2125). Look for the post on our Device xda and use it.
Click to expand...
Click to collapse
i know about msm tool, but i cant enter in qualcomm emergency mode, cause when i connect phone to pc, it starts charging and when phone starts charging it can’t load “charge image” and gives same error as in the attachment
chizari said:
i know about msm tool, but i cant enter in qualcomm emergency mode, cause when i connect phone to pc, it starts charging and when phone starts charging it can’t load “charge image” and gives same error as in the attachment
Click to expand...
Click to collapse
turn off the phone fully, press volume up and down fully for 3 seconds then while still holding those buttons, plug in the phone with MSM open on your laptop. it should immediately detect the device. the phone screen will still be black and thats normal. once device is shown as connected, just select target O2 and start
disconnect usb, let battery drain, ensure it is really powered off, press both volume keys, connect usb
chizari said:
I just unboxed new OnePlus 9 Pro, then i was installing an update and during update phone’s case held power off button, so phone turned off and showing current error.
View attachment 5813705
I can’t boot in Android and in Recovery mode. Everything working is Fastboot mode. I was trying to “unbrick” phone, installing Fastboot ROM( files like boot.img, recovery.img and so on),but in cmd on my pc shows while using commands like: “fastboot flash boot boot.img” or fastboot -w“, only error “Failed (remote:’Erase is not allowed in Lock State’)”.
Now i want to unlock device state if it is possible.
Remind that phone was just unboxed, so it doesn’t have enabled lever OEM unlocking.
Click to expand...
Click to collapse
MSM Tool time. What model do you have?
aIecxs said:
disconnect usb, let battery drain, ensure it is really powered off, press both volume keys, connect usb
Click to expand...
Click to collapse
ok, i ll try
TheGhost1951 said:
MSM Tool time. What model do you have?
Click to expand...
Click to collapse
LE2123
chizari said:
LE2123
Click to expand...
Click to collapse
Get the MSM tool for LE2123 from this thread....
How To Guide OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
Does somebody know how long it takes to let battery drain from 100%?
And maybe, Are there some advices how to let battery drain faster?
You will also need to 1) disable driver signature see this https://www.techpout.com/disable-driver-signature-enforcement/ then reboot computer 2) install latest OnePlus USB drivers then 3) install latest Qualcomm driver then reboot PC 4) start the MSM Tool uncheck 256 and check use lite firehose the click start. 5) start phone in edl mode with button sequence.... MSM should automatically start flashing!
As for edl mode, check to see if you can get to fastboot by holding vol + and - and power buttons down and hold them to see if fastboot loads. This is if you cannot get to edl the button wat as described above.
TheGhost1951 said:
As for edl mode, check to see if you can get to fastboot by holding vol + and - and power buttons down and hold them to see if fastboot loads. This is if you cannot get to edl the button wat as described above.
Click to expand...
Click to collapse
Fastboot menu loads
Now i need to wait few days to let battery drain…
Maybe you know any advices how to let it drain faster?
chizari said:
Fastboot menu loads
Now i need to wait few days to let battery drain…
Maybe you know any advices how to let it drain faster?
Click to expand...
Click to collapse
No need to wait.... Do you have the latest platform-tools installed on PC?
TheGhost1951 said:
No need to wait.... Do you have the latest platform-tools installed on PC?
Click to expand...
Click to collapse
Yeah, i installed it with android studio
chizari said:
Yeah, i installed it with android studio
Click to expand...
Click to collapse
Good now download this file and save it to the platform-tools folder and change the name to twrp.img.... https://dl.twrp.me/lemonadep/twrp-3.7.0_11-0-lemonadep.img make sure the phone is connected to PC in fast boot mode if you have already installed all the drivers....
TheGhost1951 said:
You will also need to 1) disable driver signature see this https://www.techpout.com/disable-driver-signature-enforcement/ then reboot computer 2) install latest OnePlus USB drivers then 3) install latest Qualcomm driver then reboot PC 4) start the MSM Tool uncheck 256 and check use lite firehose the click start. 5) start phone in edl mode with button sequence.... MSM should automatically start flashing!
Click to expand...
Click to collapse
here you mentioned qualcomm drivers, you mean Qualcomm HS-USB QDLoader 9008 Drivers
chizari said:
here you mentioned qualcomm drivers, you mean Qualcomm HS-USB QDLoader 9008 Drivers
Click to expand...
Click to collapse
Yes