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.
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 ?
Hi guys, I've been scouring Google for 3 days now and can't come up with an answer, everything says use Odin for this and use Odin for that... well I can't.
A few days ago I downloaded an app from the Google store Linuxonandriod or something like that, it's pretty much an installer to place Ubuntu on your phone side by side with Android, the instructions began with rooting the phone, I began that process and believe I accidently loaded the incorrect pda to the phone (I have so many files now on my comp, I have no clue which one I selected). Odin rebooted the phone and that's that.
If I try to turn on the phone it goes to the first screen that just says SAMSUNG then turns off, never getting to the Samsung Galaxy III screen. The USB on the phone seems to have been botched, none of my computers will recognize it (Windows or Linux), the phone will not even charge. I can however get into both recovery and download modes without problem.
Naturally, download mode does no good because the USB is useless and I do not have clockwork mod installed on the phone to bypass the verification error.
I tried to simply install clockwork via recovery in hopes that would do something, but I get a verification error with that.
Is there anyway around this using the SD card or am I holding a $300 paperweight?
Thanks
Maybe try this-http://forum.xda-developers.com/showthread.php?t=2369125
{
"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"
}
bilgerryan said:
Maybe try this-http://forum.xda-developers.com/showthread.php?t=2369125
Click to expand...
Click to collapse
Thanks, for the link. I did check it out, but couldn't figure out what the poster was talking about with drive letters and such. That dmesg | tail told me nothing about my sd. I unzipped everything to the card by a different method but my the computer still wouldn't recognize the phone, so booting back into windows did nothing.
Sorry for the delay in response, I've been extremely busy with work.
I'm still at a total loss on this.
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.
After a bunch of research I finally decided to take the plunge to try and move to Lineage OS.
Phone is a Google unlocked 128GB 2 XL.
I was able to get through the unlock portion but after that all the guides went different directions. I was following the process from TWRP and at one point had the TWRP recovery app showing via fastboot but now all I get is the "device is corrupt" warning which then ends up in the white screen with Google logo and small unlocked icon.
Any chance I can get back to scratch or press forward to LineageOS/other ROM or is this thing a brick?
*Update* Not sure what key combination I used but I can get to the following TWRP screen. However the touchscreen does not respond and after the screen hibernates any key returns it to this state:
{
"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"
}
Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.
Strephon Alkhalikoi said:
Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.
Click to expand...
Click to collapse
Not sure how I can do that.
I can get to the default green START option. If I selection that the system boot to a white screen adn stops.
If I select BOOTLOADER the device pops back to the green START.
If I select RECOVERY it gets to the TWRP screen but the touchscreen nor buttons work.
I've tried connecting the phone via USB to my PC but no matter what mode I put it in ADB never detects it.
The "green Start" is where you want to be here. That's the bootloader. You need to make sure the driver - assuming Windows - is set to ADB Bootloader Interface in Device Manager as well as make sure you have the latest version of the ADB / Fastboot package.
I would like to know how to enter fastbootd! mode???
Enable the USB debug mode in the Developer options, install adb (it's the part of Android Studio, or as a separate tool for Linux available in the official repos) and execute "adb reboot bootloader".
This is FastBootd! mode ??
{
"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"
}
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
uluruman said:
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
Click to expand...
Click to collapse
so I can install GSI by the dynamic partitions
PaulinoBaslio said:
so I can install GSI by the dynamic partitions
Click to expand...
Click to collapse
Probably. May be. From my experience it simply doesn't work. It sorta flashes something but may be it just takes forever to complete or it's really just stuck but there's no response whatsoever. Fastboot mode is absolutely minimalistic, it does not report anything, no progress, nothing, and I guess it's intended to be like that, because it boots before anything else and theoretically allows you to flash even the very first bootloader. Anyway, I tried something like fastboot flash system lir-v316-220325-arm64-bvZ.img and the CLI tool reported Sending 'system' and then nothing else happened for the next 15 minutes or so, after which I just hit Ctrl+C, ran fastboot reboot and observed that nothing changed, the old system booted just like it was, so I guess nothing was really flashed, even partially. I don't know really, may be it's unpacked internally only when the image is fully uploaded and I didn't give it enough time, but for that time Odin would already flash the whole set of firmware. What else is to try, besides waiting more time, is converting the image to/from Android sparse format using the img2simg & simg2img tools, and try other partition names, such as "system_root" but I am sure this latter thing is absolutely wrong. The GSI system partition is called system, it just must be called that, system_root is something else (I guess it's the system root of the recovery mode).