It is difficult to explain what happened. It was quite irresponsible of me. I didn’t research it properly before wiping my phone. Now my zuk folders are not showing up on my pc, and I can't format it using TWRP. I was on a Custom Rom with Android 10 and went to another with Android 8.1, just to test it. I didn't like it and was about to install one with Android 9. When the problem happened.
I tried to install the drivers for the zuk z2 plus on the pc. My pc recognizes the phone only as a Media Player and does not even allow to create a folder.
I tried to use adb fastboot with qfill but it is not possible to activate usb debugging, so I cannot install a factory stock rom.
It seems I'm just too late?
First power the phone off by unplugging the battery. You can then short-circuit the test points on the mainboard of Z2 (Plus) before plugging USB cable, to enter Qualcomm EDL mode (9008), then you will be able to export data with QFIL's partition manager, or just flash the stock ROM.
{
"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"
}
This works for me. It works even if the "deep flash cable" (USB cable with its D+/GND pins short-circuited) can't work (because the detection of such deep flash cable is done by SBL in the PBL->SBL->aboot->Linux kernel boot chain).
However, use it at your own risk.
linuxnoobbbb said:
It seems I'm just too late?
First power the phone down by unplugging the battery. You can then short-circuit the test points on the mainboard of Z2 (Plus) before plugging USB cable, to enter Qualcomm EDL mode (9008), then you will be able to export data with QFIL's partition manager, or just flash the stock ROM.
This works for me. It works even if the "deep flash cable" (USB cable with its D+/GND pins short-circuited) can't work (because the detection of such deep flash cable is done by SBL in the PBL->SBL->aboot->Linux kernel boot chain).
However, use it at your own risk.
Click to expand...
Click to collapse
Ty for helping but i fixed my phone. The problem was the TWRP. My last custom rom downgraded my twrp. I used fastboot and was able to flash the latest twrp and voila. Problem solved. Never gonna try to install android 8 again, just gonna stay with 10 before i got myself in more problems.
Related
Hey there forum. I made an account just to ask this question because I just spent 7 hours looking for the answer to what SHOULD be a simple fix. I have a T-Mobile HTC Wildfire S with the US RUU installed and the 1.09.0099 HBOOT as well. Now, I have tried to unlock my bootloader on the HTC website like you're "supposed" to. But whenever I put my phone into the bootloader and plug in it in as in the guide. Then I cannot get past step 8. Because my bootloader does NOT stay in "FASTBOOT USB" It goes back to FASTBOOT in around 30 seconds. I have gotten the command prompts in before it goes back but to no avail. When it is in FASTBOOT USB mode, it's as if it's not connected. Then when it goes to the regular FASTBOOT mode, then my Windows 8, 64 bit laptop (in case it was important), makes the sound that it does when you connect something with USB. Some help would be GREATLY appreciated because I am stuck with this phone and I need some CFW.
The drivers don't work on Win8 iirc.
Follow this
Also, welcome to Xda.
omnomnomkimiiee said:
The drivers don't work on Win8 iirc.
Follow this
Also, welcome to Xda.
Click to expand...
Click to collapse
Thanks for the drivers! They successfully installed but I'm still getting the problem where my phone won't stay in FASTBOOT USB...
omnomnomkimiiee said:
The drivers don't work on Win8 iirc.
Follow this
Also, welcome to Xda.
Click to expand...
Click to collapse
{
"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"
}
This picture shows what my device manager looks like when my phone is in FASTBOOT USB.
And this picture shows what happens in the device manager after my phone drops out of FASTBOOT USB and into FASTBOOT. The computer makes the little connecting noise and then THAT.
Tbh, I dual-boot win7 and win8 just for my phone :/
Seeing how it seems you're just trying to unlock your bootloader and root, maybe borrow a friend's pc/laptop for the 30 minutes ?
Hello guys... today i power my s4 mini and nothing commands worked...
The odin did not install anything and on the cell phone the blue bar did not appear and neither the Philz touch recovery did not work ...Here below I will put prints of the odin and my screen ... If someone sober how to fix please contact me ... urgently ... (already tried recovery by kies also and the same problem occurs)...
{
"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"
}
Hvee said:
Hello guys... today i power my s4 mini and nothing commands worked...
The odin did not install anything and on the cell phone the blue bar did not appear and neither the Philz touch recovery did not work ...
Click to expand...
Click to collapse
I would guess memory is broke or corrupted. (so it's brick) Did it shut itself down when battery went flat? Did it turn off normally?
But normally (if your phone is still able to boot normally) when stuck at "initialization" it's a communication issue, so try use another usb cord, usb port, different version of Odin (older or newer).
Try shut PC & phone down, pull battery reinsert after a minute and try again.
[ didn't newer version of Odin have problem flashing Philz? I'd recommend TWRP from neozone thread anyhow].
But normally (if your phone is still able to boot normally) when stuck at "initialization" it's a communication issue, so try use another usb cord, usb port, different
Yes, in fact it connects normal but a little before spoiling the philz was running, however, it started installing the AOSP rom and in the middle the screen erased, I suspect it is the hd ... Now it just turns on the Odin and the screen Vibrate and black fics in Recovery mode (no signal). I tried the recovery with 3 different computers and 2 different cables ... several stockroms and several versions of Odin .. but nothing worked.
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
result was:
{
"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"
}
after leaving it like that for 30 minutes nothing has changed, the screen on my mobile was the the default fastboot screen nothing ever changed
so i tried to just launch TWRP without installing it:
nothing changed like before and i've stopped after 5minutes
i also have the same result with RedWolf Recovery Project:
I also tried using XiaoMiTool but all i got was the message that my phone is not connected to my MiAccount and still locked and did nothing
Does anyone have any idea whats going?
Edit:
seems like flashboot commands dont work? tried flashboot continue to reboot the device after checking with fastboot devices to see if it was recognized by the system and it was indeed.
and the result were the same as above cmd was stuck mobile didnt react....
Thanks
Dugma
Dugma said:
Hey,
I've unlocked my Mi 6 today (i'm using the global developer ROM 8.9.13 (MIUI10)) and wanted to root it, as many guides said I have to replace the default recovery with something like TWRP
[...]
Click to expand...
Click to collapse
I'd rather flash the recovery than just booting to it. You can flash it with fastboot flash recovery recovery.img
You should be able to boot to recovery afterwards. Or at least that's what I did when I bought my phone. I updated to the latest version of MIUI (android 8.0), then I enabled "oem unlock") and I was able to flash twrp with no problems. Keep in mind that the stock rom erases any custom recovery with the default one on boot.
Facing the same issue. Tried everything but no success.
[HELP] G532M Can't upload firmware via "DOWNLOAD MODE" since it gets stuck at half!
Hello everybody, first thread on XDA.
I will tell you about my problem since it seems to be unusual.
I have a J2 Prime G532M that one day suddenly when I woke up and I turn on my phone a blue screen with the following message appeared "this phone has been flashed with unauthorized software [...]" this made me confused because my phone had the OFFICIAL ROM and I've never rooted it.
So I downloaded the official rom from Sammobile and I tried to flash it via Odin. The weird issue here is that when I try to flash it it stucks at half of the process. Sometimes at 12% exactly when it arrives at 360mb/3.75gb uploaded to the device. I downloaded two differente roms bc I thought that the first was corrupted, but both of the roms makes the same.
Also, when the phone is in Download Mode after disconnecting and reconnecting the phone to the computer Windows shows me:
{
"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"
}
"The last USB device you connected to this computer malfunctioned, and Windows does not recognize it".
When I first connect the phone everything its OK. After a while (10 seconds approx) the phone stop receiving data from Odin and when I
reconnect it Windows shows that.
What my problem could be? i'm reading all the comments. Thanks in advanced.
Try using another usb cable. Maybe it's because of your usb cable. Because my phone is J2 PRIME SM G532G Variant I was FRP locked by google but then when I try to flash my stock rom via Odin it stucks and stops halfway of the process. So what I did is just changed my USB Cable and it worked for me. Hope it works for you too. There are a lot of options changing your usb cable. Or so I could analyze the real problem here include the logs of your Odin here when it stopped halfway. Copy your Log and paste it here.
EDIT: RESOLVED
I was in TWRP and decided to format-all (checked all the boxes).
Then, for some reason I decided to switch to the other side (Boot_B) and do the same there.
But the TWRP on that side was broken.
And now I'm stuck with no OS installed.
And my PC won't recognize my phone when I plug it in.
I've tried all three of my known-working cables and both of my computers.
Windows Device Manager doesn't see anything being plugged in.
It's not even coming up as an unrecognized device. Windows pretends like I haven't plugged anything in.
So, no ADB device, no Fastboot device, no Qualcomm device, no unrecognized device.... simply NOTHING.
Now the phone just boots to "The bootloader is unlocked" or to the broken (frozen) TWRP where even a USB-OTG mouse won't work.
With phone plugged in:
{
"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"
}
FINALLY got it to boot into fastboot mode!
First, power it all the way off.
Wait a minute then press & hold all three buttons.... Volume (+) & (-) and Power-button until you see fastboot.
And finally my computer sees it.
Cool, and I was able to do a "fastboot set-active a" and then reboot to the properly-working TWRP.
I should be good to go now!
EDIT:
Actually, I still can't get into MSM (nothing in device manager).
And ADB sideload or ROM install from TWRP ends in “kInstallDeviceOpenError”
EDIT 2:
I remembered that TWRP has a "reboot to EDL" option, so I used that and I'm now MSM'ing just fine.
Don't use TWRP on these devices. Even on A11 it doesn't work right. ROM devs post a recovery that's meant to be used with their ROMs, use that.
EtherealRemnant said:
Don't use TWRP on these devices. Even on A11 it doesn't work right. ROM devs post a recovery that's meant to be used with their ROMs, use that.
Click to expand...
Click to collapse
I use TWRP for full ROM backup & restore purposes.
And it works fine as long as I don't try to get too fancy.