Is my supposed non-brickable ZUK Z2 bricked???? - Lenovo ZUK Z2 (Plus) Questions & Answers

Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie

chazhammer said:
Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
Click to expand...
Click to collapse
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.

sanjay.2704 said:
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
Click to expand...
Click to collapse
Thank you very much for your suggestion, Sanjay, it is very much appreciated :good:
When I choose recovery, everything just "hangs" - black screen that doesn't go anywhere (that's why I thought that maybe there was some kind of conflict, where the phone didn't know how to chose between the two options perhaps (pure specuclation!)
I have tried the solution you suggest, but it didn't work for me.
I will re-attempt this an extra ten times or so (you never know) just in case, and let you know how things go.
This one:
(https://forum.xda-developers.com/lenovo-zuk-z2/how-to/reboot-to-edl9008-modetotally-bricked-t3720932)

OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie

For a little added information, the other recovery was: TWRP Red Wolf
(https://zukfans.eu/community/thread...r-image-error-7-installing-a-custom-rom.8347/)
While flashing this with TWRP there was an option to flash to.... I don't remember the options and can no longer consult to check, BUT at 2am, about to give up, and not knowing exactly what to select, I selected about 3 options at this stage
I believe there were something like 5 options and I selected "boot" I think, plus..?
Very stupid of course and obviously I was too confident in not creating a problem that couldn't be solved!
I have been playing around with flashing ROMs etc for the last 10 years, over 3/4 different devices and despite having read all the warnings, since over this time I have never had any issues, I kind of considered it to be almost impossible to get into a situation where things are irretrievable...so my comuppance :-/
Again, if anyone has any ideas, I would greatly appreciate

chazhammer said:
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
Click to expand...
Click to collapse
Edl cable approach would work for you.. Here is the thread guide for you..
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/deep-flash-revive-zuk-z2-hard-brick-t3577146..
Also I would suggest to stick to official twrp as that's more stable as compared to redwolf..
Hit thanks if it helps.

Thank you again Sanjay.
I have ordered a new lead (to cut open and attempt this intervention)!
I will let you know how I get on.

OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal

chazhammer said:
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
Click to expand...
Click to collapse
You can go ahead with qfil now.. You should see same port in qfil as well.
Once qpst is completed phone should boot up..

After some issues with the Sahara error (needed to update to edl mode and press download immediately) I finally managed to flash back to stock ROM
Thank you for all of your help!!!

Related

Password Locked, no debugging, no recovery mode menu, options for flashing new ROM?

Hello again. I've posted this problem in another thread and didn't get very far so I'm re-rolling the issue and posing it another way. Ok, here goes:
Tablet is a generic Chinese tablet. Klu by Curtis model number LT7052. This is a password locked unit that the original owner could not fix and has since abandoned the unit. I'm attempting any method for working around this problem and have gone through all the normal procedures. USB debugging is off. I can access recovery mode, however no combination of button pushing will yield the actual menu, you just see Andy, lying on his back with a red triangle and exclamation point hovering above him (maybe some kind of added caution screen, maybe corrupted recovery?). When I attach it to the computer at this point, load the Android ADB drivers, and type in "adb devices" I get:
"0123456789ABCDEF recovery"
"abd shell" yields the "No such file or directory <2>" error. Not really surprising as USB debugging is off.
When I use the "reboot fastboot" command and then reinstall the appropriate drivers the device is not found. Again, locked, no debugging, not really a huge surprise. I've even tried the wipe command from fastboot and it just sits there waiting for the device, again not a huge surprise since it cant be found.
I was able to locate the original firmware on the manufacturer's website and downloaded it, but I'm not sure what options I have at this point. It's really just a fun project for me trying to figure this out, but having the tablet operational would be a plus. If anyone has any ideas on how to proceed at this point I'd be willing to try just about anything, no matter how "off the cuff" it may seem. Any way to force feed this tablet the original OS without shell access? Thoughts? Suggestions? Thanks a ton for reading.
Bump for another look. Thanks!!

[Q] cant enable usb debugging, fastboot doesnt work

I have a Nexus 7 2013 that wont boot. USB Debugging was not enabled. At this point, I am just trying to wipe the machine with a stock image, but I am having trouble.
I have installed the sdk and drivers (so many drivers!)
Recovery mode fastboot does not recognize the device.
ADB recognizes the Nexus, but I cant seem to get it to do anything with it.
e: failed to mount anything.
I have read through so many forum threads that I'm just overwhelmed, and they all seem to require the machine being in USB debugging mode before any changes can be made.
Please help or tell me what pertinent information I have omitted.
Thank you
I think USB debugging only matters in ADB, which is when the device is actually booted into Android OS. You probably want fastboot, which is a different "application" and set of commands in a command prompt.
Code:
fastboot devices
Does that give you anything when the tablet is in fastboot mode? It should list the serial number of the device, similar to "adb devices" does. If not, it could be drivers, or another issue with the device.
Have you tried unlocking the bootloader? This will induce a factory reset of the current firmware version, which may allow you at least boot normally and take any available OTA updates.
Hello,
fastboot devices lists nothing, while adb does show the serial number.
I have used so many tutorials and a couple of toolkits that now I have no idea what is happening with my drivers.
Unlocking the bootloader to force a factory reset sounds amazing, but all the information I can find says I need to have USB debugging enabled to do so. I can not boot into the system to enable it.
Is there a way to force a reset without USB debugging?
Thank you
Usb debugging is irrelevant. Forget about it, it's only used when the system is booted.
You need to get fastboot devices to recognize the tablet.
Uninstall any and all toolkits and drivers. Redownload the sdk. Boot to the bootloader and plug it in, the drivers should install automatically. If not install the google usb drivers from the sdk manager in the sdk.
Try fastboot devices again. If it doesn't work try a different usb cord/port/computer.
You are in the bootloader when running this command right? Not the recovery? I think with the tablet off it's volume down and power. The screen that says start in big green letters at the top and has device info in the bottom left is what you want.
Edit: Did you boot to recovery and select the options to wipe data and cache? Sometimes thats all thats needed.
Also booting to recovery and performing a factory reset may be sufficient.
ADB will indeed function in recovery. I don't think you have to enable USB debugging to get this to work though.
Are you typing fastboot devices while booted in recovery? Typing fastboot devices while in recovery or booted into Android will do nothing.
hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?
helpmynexus said:
hello, thank you for your advice. I now get the nexus seen by fastboot (and win 7) but have hit a wall. The last time I had my computer and the nexus together was weeks ago, when I my computer BSOD during what I thought was a simple flashing of the the stock image, but turned out to be hours of the nexus saying it was erasing personal data ... and then crash. I have replaced and added fans so my cpu wont overheat again, so please offer ideas why "fastboot flashall" or "fastboot flash image-razor-kot49h" wont work.
I appreciate all responses, and believe the answer is either very simple or a catastrophic hardware failure. I base this belief on what is left in my head after smashing it into the wall so many times over the last month when my wife asks me, "have you fixed my nexus yet, or do I need to figure out a way to buy a new one next month?"
I am stuck at unlocking the bootloader. I have highlighted "yes" on the nexus and pressed power and my command window says "erasing user data." It has said this for the last 18 hours. This is the second computer I have tried this on, using 3 different usb cables. What am I missing?
Click to expand...
Click to collapse
I have the same problem .. Have You reslove it?
bikicviki said:
I have the same problem .. Have You reslove it?
Click to expand...
Click to collapse
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
---------- Post added at 07:12 PM ---------- Previous post was at 06:57 PM ----------
Troops42 said:
This may help...it may not. But I was having issues getting my bootloader unlocked also when I started on mine. My remedy was to
1 plug in the nexus into the usb
2 I run Linux so it gives me choices on what to do with newly plugged in usb device. I noticed two identical choices to mount device. Choosing one just mounted the camera for some strange reason. I closed that window, then chose the other choice to mount device, the window opened and my full internals were there in the window
3 from a terminal I just wrote a prompt: fastboot oem unlock
and for some reason, it unlocked.
To sum it up I'm convinced it has something to do with how the device gets mounted. At least on mine anyway.
As for activating developer from a terminal I read it could be done but never tried it myself, if you want here's the link for the info, read the second answer down.
https://stackoverflow.com/questions/47510232/is-there-any-adb-command-to-enable-developer-options
Also check out the fastboot manual for some other things to try, you never know some may work in your situation at a terminal prompt
man fastboot
Click to expand...
Click to collapse
Tried to edit but anyway:
After re..re, rereading your post, and responces. Have you tried the old fashioned way
Hold down the (down volume) button at the same time the (power) key.."Together" If you get anything that pops on your screen let go of the keys, one tap at a time tap the volume up or down key ONLY, until it says (START), its in green type. if you get there you should be ok, to move along

Can't get the phone to recognize data connection through USB port

Sadly i had to come to the painful conclusion that my problem relies at this point on the data detection of the phone itself.
I have read tons of tutorials pointing to adb or fastboot upgrades and different stuff and methods to update. I'm stuck in 2.20.40.139 and cannot find an update within the OS. I will enumerate now the things i see in order to clarify this situation.
_USB debugging on or off makes no difference.
_MTP or the other mode returns nothing. No detection on device manger in windows.
_Phone always charges when plugged to USB ports.
_Tried 4 cables and 3 pc's all of them tested with other phones and tablets.
_On fastboot mode nothing happens and device is nowhere to be found.
_ADB is the same. adb devices shows nothing for this.
_Recovery returns an error as if it tries to update something that isn't there MOFD_SUPDATE.zip
_after that error i get into recovery pressing power+vol up for a few seconds.
_did a factory reset on the phone and wipes in recovery.
_copied file in root of the phone. Detected the update. failed when trying to apply.
_bootloader in fastboot shows unknown. serial is 0123456789ABCDEF or something like that (serial was ok before i used the bootloader unlocker from ASUS website)
i can't think anything else for this right now... it's really driving me crazy since android works without an issue. Phone is not rooted or even has been tried to root.
If someone knows or can think anything regarding this please help me out. There's nothing i like more to share thoughts and ideas to have this updated.
Thanks in advance,
see thread about unbrick soft/hard bricked zf2

emmc error? Suddenly black screen

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.
slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.
slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
Post SS of the device manager after connecting the phone to the PC
150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.
@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...
Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722
slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode
150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.
nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?
nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.
150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.
Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?

Question [Solved] POCO F3 - Unable to unlock bootloader/fastboot no device

Hey there,
sorry for the undescriptive title, but I really don't know what is going on. I received my new Poco F3 on tuesday and since then I am trying to make some progress with unlocking the bootloader. I went through the steps:
- enable developer options
- download the Flash tool from Xiaomi
- enable OEM unlock and USB debugging
- registering a new Mi account
- pairing the Mi account from the phone in Dev-Options/Mi-Unlock Status (while on data with the same SIM and phone number used in my Mi Account).
I tried it from various computers and with different cables. Somehow the phone is not detected when in Fastboot mode. Here are some things I tried (tbh - I really can't recall everthing I tried):
- installing ADB tools in Linux and Windows
- Using the XiaoMiTool V2
- installing various USB driver found in the net on WIndows
- Using an older version of the Mi Unlock Tool from their website (4.5.813.51) as there where USB drivers included.
- "unpaired" and paired my phone with the Mi Account, also detached the Mi account from the phone and reattached it.
I know that I won't get any unlock at the moment as the wait period is not over. However I expect at least that I see an error message indicating that I need to wait for X-hours longer or something. But in the various tools the phone doesn't even appear when in fastboot mode.
Using Linux and XiaoMiTool was the "most successful" method - but even here the fastboot mode was not recognized. I just got a "Service Token invalid" message - which looked like it is caused by not having a connection to the fastboot mode.
At least I now figured out that it is totally normal that devices in fastboot have "d00d" as idProduct, because this was what changed when I attached the phone in normal mode (idProduct=4ee7).
Running "adb devices" in fastboot also doesn't show anything (Windows and Linux).
I fear that I may ended up in a trap like with my first phone - the Samsung S2 i9100g - that was the "same" but different from the "normal" S2. Is there something known? Using CPU-Z I see that the CPU seems to be at least a SM8250 - so that looks promising. The Model is M2012K11AG (alioth_eea) if that helps anything.
Any hints, tips, suggestions on how to proceed are welcome I am flashing my phones since almost 10 years, so I should be able to make this work here too, right?
Thanks
"I know that I won't get any unlock at the moment as the wait period is not over. "
You managed to start the unlock timer using the tool though?
I think at first I had the same worry of it not being recognized (adb devices never worked) but as it did show in both the unlock tool and the flashtool and managed booting (fastboot boot x.img) to twrp.img recovery also after. (you load fastboot with power - & volume?)
Plugging it in when booted and/or in fastboot should result in some connected sound. I trust you checked in the system devices if the device got installed/recognized?
sathariel74 said:
Hey there,
sorry for the undescriptive title, but I really don't know what is going on. I received my new Poco F3 on tuesday and since then I am trying to make some progress with unlocking the bootloader. I went through the steps:
- enable developer options
- download the Flash tool from Xiaomi
- enable OEM unlock and USB debugging
- registering a new Mi account
- pairing the Mi account from the phone in Dev-Options/Mi-Unlock Status (while on data with the same SIM and phone number used in my Mi Account).
I tried it from various computers and with different cables. Somehow the phone is not detected when in Fastboot mode. Here are some things I tried (tbh - I really can't recall everthing I tried):
- installing ADB tools in Linux and Windows
- Using the XiaoMiTool V2
- installing various USB driver found in the net on WIndows
- Using an older version of the Mi Unlock Tool from their website (4.5.813.51) as there where USB drivers included.
- "unpaired" and paired my phone with the Mi Account, also detached the Mi account from the phone and reattached it.
I know that I won't get any unlock at the moment as the wait period is not over. However I expect at least that I see an error message indicating that I need to wait for X-hours longer or something. But in the various tools the phone doesn't even appear when in fastboot mode.
Using Linux and XiaoMiTool was the "most successful" method - but even here the fastboot mode was not recognized. I just got a "Service Token invalid" message - which looked like it is caused by not having a connection to the fastboot mode.
At least I now figured out that it is totally normal that devices in fastboot have "d00d" as idProduct, because this was what changed when I attached the phone in normal mode (idProduct=4ee7).
Running "adb devices" in fastboot also doesn't show anything (Windows and Linux).
I fear that I may ended up in a trap like with my first phone - the Samsung S2 i9100g - that was the "same" but different from the "normal" S2. Is there something known? Using CPU-Z I see that the CPU seems to be at least a SM8250 - so that looks promising. The Model is M2012K11AG (alioth_eea) if that helps anything.
Any hints, tips, suggestions on how to proceed are welcome I am flashing my phones since almost 10 years, so I should be able to make this work here too, right?
Thanks
Click to expand...
Click to collapse
I'm you're saver !!!!
Download this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file
Extract it launch the exe then u see drivers like qualcomm,google... Then click on install when u see a pop up in chinese close all see if fastboot is recognizing you're device
ALSO LATEST ADB AND FASTBOOT VERSION : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Mother_Teresa said:
You managed to start the unlock timer using the tool though?
Click to expand...
Click to collapse
Well, I don't see any timer in the tool. However the new flash tool doesn't seem to promising (that batch one). Also in XiaomMiTool I don't see any timer. So maybe the registration is already messed up?
Mother_Teresa said:
think at first I had the same worry of it not being recognized (adb devices never worked) but as it did show in both the unlock tool and the flashtool and managed booting (fastboot boot x.img) to twrp.img recovery also after.
Click to expand...
Click to collapse
Well, this one does not work for me as it is locked...so I suppose this is a dead end at the moment. Tried this in Linux (I am more comfortable with).
Mother_Teresa said:
(you load fastboot with power - & volume?)
Click to expand...
Click to collapse
Yes, I actually do that usually (besides of the automatic Fastboot loading from XiaoMiTool).
Mother_Teresa said:
Plugging it in when booted and/or in fastboot should result in some connected sound. I trust you checked in the system devices if the device got installed/recognized?
Click to expand...
Click to collapse
Yes, it gives some connected sound in both modes (normally booted - can even mount the phone storage - and in fastboot). Not sure about the device correctly installed when in fastboot - I tried to follow some threads/videos on that but somehow it looked different for me.
X0PIRAT3 said:
I'm you're saver !!!!
Download this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file
Extract it launch the exe then u see drivers like qualcomm,google..; Clique on install when u see a pop up in chinese close all see if fastboot is recognizing you're device
ALSO LATEST ADB AND FASTBOOT VERSION : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
Thanks! I may try those out (not sure if I can make this during the weekend).
EDIT: The drivers from @X0PIRAT3 really did the trick! I just installed them and tried it. Now it says 165 hours wait time (it maybe 3 hours that I last tried to rebind my account during trouble shooting!). Thanks a lot to you 2! You are really genius!
sathariel74 said:
...
Thanks! I may try those out (not sure if I can make this during the weekend).
EDIT: The drivers from @X0PIRAT3 really did the trick! I just installed them and tried it. Now it says 165 hours wait time (it maybe 3 hours that I last tried to rebind my account during trouble shooting!). Thanks a lot to you 2! You are really genius!
Click to expand...
Click to collapse
Yay, well done.
I kept default MIUI and rooted with Magisk (install this in Magisk app to fix safetynet pass).
More details here.
Well, I can endure a lot but not MIUI - its not my kind of android. I will go for LineageOS initially I think Lets see what surprises come up, luckily I still have my 5T.
sathariel74 said:
Well, I can endure a lot but not MIUI - its not my kind of android. I will go for LineageOS initially I think Lets see what surprises come up, luckily I still have my 5T.
Click to expand...
Click to collapse
Not to bash etc but what is so bad?
I installed my preferred launcher (Nova) and it works for being a familiar front-end.
Options and tweaks are mostly there these days in the settings (fe. flashlight on double-press) and if not there is root.
is it bloatware? (if so, can we fix it? )
Lineage is of course a safe bet and I probably end up trying some but I need some encouragement .
BTW: beware the Miu Flash tool not enabling 'lock device' when flashing.
edit: how to use smileys. Now it seems super happy but without it seems so serious....
Well, besides of lack of trust (which is most likely just my issue), I really dislike that "all at startscreen" quite a lot. And yes, those 20-30 apps that I was able to delete plus the 20 apps I would like to delete are another thing showing me that this ROM is not for me. Especially that memory manager stuff that enables your "high performance game experience" is a sign to better stop using MIUI. There are also some bugs (strange behaviour I saw/felt - can't even really describe) I didn't like.
I like to manage my stuff myself, even if this is more work. But I somehow know how its "glued" together. So LineageOS is what I like. Or some of the other AOSP ROMs available.

Categories

Resources