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:
Related
I bought my One with bootloader unlocked but the guy who sold me the phone unrooted the phone before shipping and i've tried to follow the rooting and the unlocking bootloader through fastboot methods but every time i open sdk manager it just says i have to update, i update then it says restart, and no mater what i do, cmd just keeps telling me fastboot is not a recognized command... blah blah... short question is, is there a rooting app i can purchase or if anyone can give me a helping hand?
Edit: I have followed the steps exactly, switched off fastboot in power menu, and powered off entered fastboot from bootloader, plugged in device, entered cmd and tried it but i get the aforementioned error.
Edit 2: I made the folder and placed my files and it seemed to go a little smoothly but it says waiting on device and just hangs there. The computer is still not recognizing the phone, i still get USB not recognized. try reconnecting the device....
Oh also, trying to install a recovery to this, so i can root... but just an easy way
Please help me, someone... the bootloader says unlocked btw. but fastboot does nothing when trying to flash via cmd.
if you are running windows 8 you may need to install the correct drivers, i had the same problem when i tried to root my M7 and im runinng windows 8, if youd like the drivers, PM me i cant remember where i got them from, but i have them still. Also if you can try switching USB ports, i had to use a different one and everything went kinda smooth after that.
sakumaxp said:
if you are running windows 8 you may need to install the correct drivers, i had the same problem when i tried to root my M7 and im runinng windows 8, if youd like the drivers, PM me i cant remember where i got them from, but i have them still. Also if you can try switching USB ports, i had to use a different one and everything went kinda smooth after that.
Click to expand...
Click to collapse
I sent you a pm... i am on win8, and i don't think its the ports because when the phone is fully on, it i can open it through windows, its just it doesn't work when it's in bootloader/fastboot
HyDRo1X said:
I sent you a pm... i am on win8, and i don't think its the ports because when the phone is fully on, it i can open it through windows, its just it doesn't work when it's in bootloader/fastboot
Click to expand...
Click to collapse
ok i switched to a win8 an everything seemed fine, but i get a long list of processing cmd after i type the fastboot flash recovery... and then continued as followed but nothing... still get red triangle
Ok got it... Windows 8 problems
Sent from my HTC One using xda premium
Hey, I am new here so sorry if I'm posting in wrong board.
I rooted my P70 a while ago and everything was fine. Now I decided that I want to flash 5.1.1 on it. I proceeded to flash TWRP.
I tried it with SP flash on pc, I checked that my scatter file and recovery.img was correct. I opened the scatter file in SP, connected my phone and clicked download, but nothing happened. Only the phone started charging, I have enabled USB Debugging and developer mode. The bootloader was still the stock one. Why?
Next thing I tried is to put the recovery.img on SD card and downloading Uncletools, I flashed it and it asked me if I want to reboot in bootloader, so I did, but it was still the stock bootloader.
What am I doing wrong? Thanks a lot for any response.
Anyone got any idea?
Click download and conecting usb cable to hh
Hey,
I have the same issue. The phone is rooted but the SP flash tool will not do anything. I've read that it's because the USB drivers are incorrect. However I am unable to install the drivers as the phone does not show up under other devices but rather under portable devices. I tried to install the android sdk and use those drivers or ones I found on the web but none of them will take. I found the ADB device signed driver under USB devices in the device manager.
I am honestly at a loss here. Would be grateful if anyone has ideas I could try!
Thanks
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.
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
Hello, guys.
Recently, I've tried to root a Cubot Power 4G following a guide I found online. I probably should have been more catious about it, cause now the phone is stuck on a bootloop. I tried to install a custom recovery to try and fix this, but as there was no official twrp for Cubot, I once again downloaded something that was probably shady. Thus, now the phone is stuck on bootloop, won't access recovery mode, is now turned off because battery gave out, but if I try to connect it to the pc, it will start to bootloop again. I cannot access adb, or at the least I don't know a way to, since it keeps bootlooping and I have no way to access a recovery mode(since there's no one, or at the least, if there is, it's faulty). What can I do here?
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
jwoegerbauer said:
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
Click to expand...
Click to collapse
I did! Or so I think... The moment I connect it to the pc, it starts bootlooping and so the pc cannot actually connect there
Bootloop is a situation where you cannot get into the "normal" Android system. Take note that as soon Android logo is shown on phone's display Android kernel got successfully initialized, ADB & Fastboot are ready.