When I "Swipe to wipe" in twrp, twrp instantly resets.
I can not swipe to wipe.
I successfully had rooted access and twrp installed with Slimroms on Nexus 9 running correctly.
I Tried to install an 8.0 Oreo rom but it crashes and resets on the google screen.
when i try to return to old roms I get "Error 7" in Twrp.
and I can no longer swipe to wipe or factory reset.
Anyone know how to fix this issue so I can return to 7.1.2 SlimRoms?
the nexus 9 no longer shows up in windows or under ADB Devices.
So i cant access adb functions.
did my bootloader have a problem?
it seems twrp is crashing when its trying to format or wipe mounts ?
Have you tried flashing the latest firmware from Google with fastboot? That's where I would start.
Sent from my SM-T820 using XDA-Developers Legacy app
Can i do that with only twrp?
Does flashboot require adb access from a pc? I cant seem to get the device to show under windows or adb.
Can i use a memory stick and twrp to install those ?
Ill try tonight if thats possible without pc adb acess.
RecIV said:
Can i do that with only twrp?
Does flashboot require adb access from a pc? I cant seem to get the device to show under windows or adb.
Can i use a memory stick and twrp to install those ?
Ill try tonight if thats possible without pc adb acess.
Click to expand...
Click to collapse
No, can't do it in TWRP. If you're having trouble, try wugfresh toolkit. It's no longer updated but you can use it to flash a factory image that you download yourself. Toolkit might help with your issue of not being recognized by your PC.
Wugflash cant recognize the device if windows cant also.
I tried.
I can get into twrp and fastboot. But i have no connection to pc, except for usb memory stick.
The device says unlocked inside of fastboot.
Why cant i connect to adb windows? Ive installed usb drivers many times for many different phones and pcs. I dont think thats the problem.
RecIV said:
Wugflash cant recognize the device if windows cant also.
I tried.
I can get into twrp and fastboot. But i have no connection to pc, except for usb memory stick.
The device says unlocked inside of fastboot.
Why cant i connect to adb windows? Ive installed usb drivers many times for many different phones and pcs. I dont think thats the problem.
Click to expand...
Click to collapse
I've had to do it few times to get it to recognize device. That's the only reason I suggested wugs. It has quick options to retry driver install. But manually is better of course. Windows 10 gave me a heck of a time with driver's.
Related
Well I accidentally erased my OS and now I TWRP can not mount USB storage.
I tried pushing through adb but it said "device not found".
I tried connecting in fastboot usb but windows can not install driver.
I have no ROM on my storage and I'm stuck.
I really need help, please.
First install a working SDK/ADB tool folder (link in my signature)
Then the sideload should work via TWRP, it takes sometime to activate but stay tune it will work.
From there you should be able to recover a ROM
Lucky Thirteen said:
First install a working SDK/ADB tool folder (link in my signature)
Then the sideload should work via TWRP, it takes sometime to activate but stay tune it will work.
From there you should be able to recover a ROM
Click to expand...
Click to collapse
ADB does not work for some reason even though I followed your steps. Windows starts installing drivers and ends up failing.
GTFX said:
ADB does not work for some reason even though I followed your steps. Windows starts installing drivers and ends up failing.
Click to expand...
Click to collapse
Which Windows version you have? Is your account an Administrator one? Did you enable USB Debugging on your phone?
Can you can try those drivers?
I have the drivers installed, but I don't know about USB debugging. I did enable it on my previous ROM if that helps but since I cleared all my data, I have nothing in my storage and I also can't access it via TWRP.
I tried your adb steps but it still tells me "device not found".
And I'm on Win7 x64 and using an admin account.
Have you tried this?
http://forum.xda-developers.com/showthread.php?p=35897885
Sent from my HTC One X+ using Tapatalk 2
Got it all worked out, thanks for the help.
Installed the latest drivers once again, downloaded the SDK files given on HTCDev and it adb pushed the ROM.
Worked like a charm.
I'm running windows 8.1. My device shows fine while booted into android under adb devices, but once I boot into fastboot, the device no longer shows. I've tried re-installing the driver several different ways but to no avail. Can anyone help me please? I need to flash stock recovery.
Use command fastboot devices to see it while in fastboot. Adb devices is for when it is booted.
3L3C7R0 said:
I'm running windows 8.1. My device shows fine while booted into android under adb devices, but once I boot into fastboot, the device no longer shows. I've tried re-installing the driver several different ways but to no avail. Can anyone help me please? I need to flash stock recovery.
Click to expand...
Click to collapse
I'm running windows 7 and have yet to get mine to see the device. Good luck.
3L3C7R0 said:
I'm running windows 8.1. My device shows fine while booted into android under adb devices, but once I boot into fastboot, the device no longer shows. I've tried re-installing the driver several different ways but to no avail. Can anyone help me please? I need to flash stock recovery.
Click to expand...
Click to collapse
put device in fastboot.
got pc, setting, system, device manager. towards top click my htc and update drivers. dont search automatically, coose device from list.
when the list comes up, you should see a few different drivers listed. choose one and try.
if one dont work, try another
Ps make sure you usb drivers are up to date. i had to install updated axhi usb drivers for my motherboards usb 3.0
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Darrian said:
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Click to expand...
Click to collapse
There is none. The only safe way to root is to flash TWRP in fastboot. Right now, you can try to force update through update.app
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Darrian said:
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Click to expand...
Click to collapse
Oh. But like I said, there is none.
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Darrian said:
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Click to expand...
Click to collapse
Have you tried changing the drivers.?
Yes
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Darrian said:
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Click to expand...
Click to collapse
Glad you fixed it. :highfive:
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Luinwethion said:
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Click to expand...
Click to collapse
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
ante0 said:
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
Click to expand...
Click to collapse
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Luinwethion said:
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Click to expand...
Click to collapse
I ran into this also and I un-installed HiSuite, then re-installed it and after that in device manager set up drivers as seen in screen copy in attachement.
I also refer to this page for more info: https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
Luinwethion said:
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
Click to expand...
Click to collapse
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
AntoRei said:
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
Click to expand...
Click to collapse
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Luinwethion said:
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Click to expand...
Click to collapse
You can use this guide with linux?
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I've been attempting to recover my samsung galaxy A8 from a brick, by flashing the original firmware for 3 days. I successfully got TWRP flashed, and couldn't connect to the phone using MTP, so I ended up using an SD card to transfer the firmware zip. Long story short, I tried to treble it, and it completely bricked, leaving me without TWRP, or anything to boot.
I've put it in download mode, swapped through 10 different USB C cables, and still can't get my PC to recognize it. I've tried two computers, one running arch linux, and the other one through windows 10 and arch linux. Nothing. Whenever I run "lsusb" I can't see the phone. I also can't see it in device manager.
windowsagent said:
I've been attempting to recover my samsung galaxy A8 from a brick, by flashing the original firmware for 3 days. I successfully got TWRP flashed, and couldn't connect to the phone using MTP, so I ended up using an SD card to transfer the firmware zip. Long story short, I tried to treble it, and it completely bricked, leaving me without TWRP, or anything to boot.
I've put it in download mode, swapped through 10 different USB C cables, and still can't get my PC to recognize it. I've tried two computers, one running arch linux, and the other one through windows 10 and arch linux. Nothing. Whenever I run "lsusb" I can't see the phone. I also can't see it in device manager.
Click to expand...
Click to collapse
have you tried flashing it as update via sideload in adb ?
do you have the latest samsung drivers installed ?
try using my tool located here
gav83collins said:
have you tried flashing it as update via sideload in adb ?
do you have the latest samsung drivers installed ?
try using my tool located here
Click to expand...
Click to collapse
I'm stuck without TWRP, so I can't adb sideload. I did try it back when TWRP did boot, but it still didn't recognize it (I tried lsusb and adb devices)
windowsagent said:
I'm stuck without TWRP, so I can't adb sideload. I did try it back when TWRP did boot, but it still didn't recognize it (I tried lsusb and adb devices)
Click to expand...
Click to collapse
you dont need twrp to sideload, you can do it via adb, my tool above will guide you through the process
gav83collins said:
you dont need twrp to sideload, you can do it via adb, my tool above will guide you through the process
Click to expand...
Click to collapse
I'll try to do it then, while in download mode. Thanks!
windowsagent said:
I'll try to do it then, while in download mode. Thanks!
Click to expand...
Click to collapse
my tool will boot you into download mode when necessary. just follow the onscreen instructions
gav83collins said:
my tool will boot you into download mode when necessary. just follow the onscreen instructions
Click to expand...
Click to collapse
My device is just not listed. I see it's just running adb devices, and nothing shows up.
windowsagent said:
My device is just not listed. I see it's just running adb devices, and nothing shows up.
Click to expand...
Click to collapse
Plus I've already got all the drivers installed.
windowsagent said:
Plus I've already got all the drivers installed.
Click to expand...
Click to collapse
you havent got your phones settings for usb set to "charge only" have you ?
gav83collins said:
you havent got your phones settings for usb set to "charge only" have you ?
Click to expand...
Click to collapse
My phone doesn't boot. I deleted the system partition. It's on a bootloop, and the only thing I can do is access download mode.
I was able to plug it in. I used the sim card remover to try to clean up the port.. I'm seriously an idiot...
windowsagent said:
I was able to plug it in. I used the sim card remover to try to clean up the port.. I'm seriously an idiot...
Click to expand...
Click to collapse
so even in download mode, my tool doesnt detect it ? what about in device manager ? does it show up in there ? are you running a windows machine or windows via a virtual machine
Hi so im having a almost same situation here with my a8 2018 so it seems on the phone that it was doing an update and failed and cant boot to android (i think it got corrupted or something) i can access the samsung recovery but if i do reboot or any data deletion i cant get it to work i tried installing twrp recovery but im a biginer and well idk how to do it from the adb update option
ocasds said:
Hi so im having a almost same situation here with my a8 2018 so it seems on the phone that it was doing an update and failed and cant boot to android (i think it got corrupted or something) i can access the samsung recovery but if i do reboot or any data deletion i cant get it to work i tried installing twrp recovery but im a biginer and well idk how to do it from the adb update option
Click to expand...
Click to collapse
update: i managed to get twrp installed
also i found out i need to install new android so if you can link me something good for the a8 2018 i would be gratefull