I have some problems with my google glass, explorers edition. First of all I got it from a company. They had an admin tool on it, I uninstalled it via adb and try to install the latest firmware. But strangely, I did not get into the bootloader (fastboot mode), not via adb and not via the recovery menu. So it was impossible to flash the latest firmware. Then I made a factory reset, but now I can not set up the device, it get the bluetooth connection, but then it says it can not connect to the account (before it worked with the same).
Do you have any ideas?
Related
So I'm sending in my Kindle HD7 for a replacement, and I'd like to revert it back to stock. However, for some reason I can't get fastboot commands to work. It was working just fine the day before
I have root, version 7.3.0 stock ROM, and Hashcode's bootloader on my device. ADB works fine. Plugging in the factory cable boots the HD7 into fastboot mode, but commands aren't going through.
Things I've tried or attempted (along with searching the forums :silly:
- Reinstall Kindle drivers
- Reinstalled SDK and such
- Attempted to use SoupKit (though I gave up since I had a hard time adjusting with the Ubuntu interface)
- Kindle Restore Tool (hangs on waiting device)
- KFFirstAide (hangs on waiting device)
- Manual flashing via command prompt (hangs on waiting device)
I know this problem usually comes about because the drivers aren't correctly installed. I did notice that when in fastboot mode, device manager shows a triangle for "'tate-pvt-08". At this point however, I have no idea how to approach this problem.
Seems like I am either left with getting fastboot to work so I can flash to stock, or somehow use TWRP to flash back to stock (but it won't wipe out the 2nd bootloader?).
Any help is much appreciated!
Well I was able to restore to stock using TWRP.
All I had to do was download the 7.2.3 bin file from Amazon and flash it using TWRP. Doing this removed bootloader, twrp, root, as well as restored the device to stock.
It was an obvious solution...just took me a while to realize it lol
I do still wonder what was happening with my fastboot drivers/access though...
Closed as per OP request.
MD
I'm having problems connecting to my phone through ADB. I've flashed back and forth between 4.1.2 and 4.2.2 roms multiple times and had no problems with wiping everything (to ensure the proper file structure etc.) and then sideloading a zip to flash. However this time, I rebooted into recovery (TWRP 2.6.3.0), wiped everything (factory reset, then wiped data, then advanced wipe with the first 5 selected) and when I went to ADB sideload my new rom, I couldn't connect to my phone. I've followed multiple guides that attempt to establish a connection between the phone and Windows 7. I've installed multiple people's "updated USB drivers that fix the problem," but no go. While in recovery, the phone shows up in my device manager under "Other Devices > M7WLS" with the '!' icon under it. While in fastboot it connects under "Android Devices > My HTC" but no ADB commands will work here. And everything is already wiped so I currently can't use my phone until I get this fixed. Any help is greatly appreciated!! Fastboot will connect though so if I have to RUU, I can.
Solved!
If anyone else is having this problem, flash recovery back to TWRP 2.5.0.0 and then you will be able to connect to ADB through recovery. Hope this helps!
hamiltoes said:
I'm having problems connecting to my phone through ADB. I've flashed back and forth between 4.1.2 and 4.2.2 roms multiple times and had no problems with wiping everything (to ensure the proper file structure etc.) and then sideloading a zip to flash. However this time, I rebooted into recovery (TWRP 2.6.3.0), wiped everything (factory reset, then wiped data, then advanced wipe with the first 5 selected) and when I went to ADB sideload my new rom, I couldn't connect to my phone. I've followed multiple guides that attempt to establish a connection between the phone and Windows 7. I've installed multiple people's "updated USB drivers that fix the problem," but no go. While in recovery, the phone shows up in my device manager under "Other Devices > M7WLS" with the '!' icon under it. While in fastboot it connects under "Android Devices > My HTC" but no ADB commands will work here. And everything is already wiped so I currently can't use my phone until I get this fixed. Any help is greatly appreciated!! Fastboot will connect though so if I have to RUU, I can.
Click to expand...
Click to collapse
Use this
http://forum.xda-developers.com/showthread.php?t=2386956
Delete every other driver including HTC sync and set those as your drivers.
Do this by going to control panel, then to device management. Find your HTC and update drivers then find the folder you downloaded, and set it to that.
Sent from my HTCONE using XDA Premium 4 mobile app
twrp 2.5.0.0 unresponsive to touch
hamiltoes said:
If anyone else is having this problem, flash recovery back to TWRP 2.5.0.0 and then you will be able to connect to ADB through recovery. Hope this helps!
Click to expand...
Click to collapse
so i was having this same problem. i flashed 2.5 like you suggested, and it did read the adb, but now the recovery is unresponsive to touch... so close this time. any suggestions?
I have two H811, mine and my wife's. I managed to root and install TWRP fine on mine via adb/fastboot with no problems but I can NOT get my PC to see the other H811. I can see it in the LGUP app just fine. I see it in device manager just fine. But, from the cmd box, I get nothing when I type "adb devices" or "fastboot" devices. Dev options are enable, OEM unlock checked and USB debug works because I can see it in my file explorer. I've rebooted both devices a bunch of times after disabling and reenabling stuff. Still, nuthin'.
Any suggestions?
EDIT -- After much muckin' about with reinstalling devices and drivers, I finally got adb to see the H811. Fastboot still doesn't see it though.
EDIT 2 -- It dawned on me that I have to be in the bootloader (I think) before I can use fastboot. At least fastboot sees the H811 and I can issue commands to the device. However, I can't flash anything to it.
After all the above stuff, I FINALLY got to flash SuperSu! Seems there's been some changes in the latest command verbage in fastboot. Since I've been using it, it's always required something like "fastboot flash recovery recoveryimagename.img" With the latest version, the word "recovery" is no longer required. Once I got it up and running, I flashed TWRP using Flashify. YMMV
Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day
I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll
SOLVED
Hi there.
I had my couple's mobile rooted with Magisk and MIUI Global 10.3. Once wanted to update twrp and the issues began. Actually the mobile isn't rooted but with unlocked bootloader, apparently.
I list the issues down below:
1) Trying to install twrp with fastboot by CMD, pressing enter after the command the cursor just blinks and nothing happens. At first it showed "waiting for device", so I installed adb drivers and the mobile appeared in Device Manager. It run once up to "sending 'recovery'" but not farther. The mobile was connected in fastboot mode indeed as well as in usb debugging but couldn't activate oem unlock as it stated it as unlocked and the option was dimmed.
2) Tried to unlock the mobile with Miflash_unlock and the phone was recognized, but the tool checked the device up to 50% and then showed that it Couldn't verify the device.
3) Then I tried to make a backup of the user data and doing a Hard Reset from settings. It went forward up to reboot, so I did, then it entered in fastboot mode for a few seconds and it powered off. Rebooted the phone and it was up and running as if nothing happened. So I cannot make a hard reset.
4) I can't enter the recovery too. If pressing volume - and power on it enters in fastboot mode. With volume + and power on it does the same With recovery enter tools isn't possible either. It seems as it's been corrupted.
5) I've just tried to flash the Global_8.0 rom with MiFlash 2019.12.6.0 and on the progress line it says "echo Mismatching image and device" How? I'm sure its a Mi Mix 2 'chiron' Rom, so... Anyway, I start to flash and the tool seems to progress but it never ends. So I disconnect the phone, reboot, and it keeps untouched running as before, OMG
6) On top of that I can't update android by OTA, as it gets downloaded, then reboot, then enters fastboot mode and after few seconds it powers off as before, and powering it on afterwards shows that it couldn't be updated
So I don't know what to do next. However, the mobile runs apparently ok.
May someone lend me a hand, please?
Thank you.
SOLVED: The Xiaomi Mi MIX 2 is up and running with the last firmware installed. The issue was that, as I build a new PC lately, I connected the phone in fastboot mode to the front USB ports, which are 3.0 version, and you need a 2.0 USB port at most, causing errors in MiUnlock and MiFlash.