Device model: Motorola G51 5G
Android Version: Android 12
I need assistance, please. After I restarted my phone, I get this message saying "No valid operating system could be found. The device will not boot." My device is rooted through Magisk, by the way.
I searched & I found that flashing it with a stock firmware would resolve it. Motorola's Rescue And Smart Assistance isn't working for me, it says that "Some key information cannot be read from the device, please unplug and reconnect your device with fastboot" when I plug it in my laptop. Manually selecting my device's model name is giving me the message, "The model associated with the IMEI for your device is currently not supported by Rescue And Smart Assistant.
Then I tried using ADB but my device doesn't show up when I type the command "adb devices." ("fastboot devices" command work though, it shows my device). I installed Android SDK, Google USB Drivers & Motorola Drivers but it still doesn't show up. I tried connecting a different phone & it shows up but not the G51.
Hoping for assistance, thank you.
*EDIT*
Nevermind. I was able to fix my phone successfully through ADB somehow. Please delete this thread.
Related
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Have you reviewed the jmztaylor method?
Have you reviewed this method?
http://forum.xda-developers.com/showthread.php?t=1905674
Worked for me after I grabbed the drivers from PDAnet.
I have one issue of Android is Updating stuck in loop that some others in that thread have sorted out but I can't quite get working yet!
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
same problem.
I am having the same exact problem. I have reviewed the jmz method and keep getting stuck in cmd saying path not specified. Any solutions. All steps have been followed to the letter.
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
cruise350 said:
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
This thread goes through doing it manually, it is written for Ubuntu(linux) but it can be used in windows as well, you just don't use sudo for the commands. Also the package in the following thread already has the updated gapps package that does away with the "android upgrading" on every boot.
http://forum.xda-developers.com/showthread.php?t=2016463
fast boot won't install
Had ''path not specified'' it gets to the if stuck here drivers aren't installed. A window pops up saying ''installing fast boot'' but then says it failed. Thats where im stuck.
4.1.1 OS
2.4 product version
Thinking the 2.4 update is a problem.
Any suggestions?
I know i'm years late here but I really HATE adb and esp. BAT files that are just suppose to do their thing........I'm hitting a wall with this Nabi 2 Bat file for TWRP / ROOT. I've used PDAnet plenty in the past for internet but never for the purpose of just getting drivers so I have no idea I hate that program too. ANYWHO , I'm getting "cannot find specified path" which I probably could fix if I ****ing knew which ****ing path it was looking for. SO if anyone could please enlighten me here , I've installed and uninstalled PDA net some 10 times now , with Samsung selected , with LG selected with OTHER selected , I cannot get this to work. I can do FASTBOOT devices , and poof it shows up , adb works fine all that , show the device but I cannot get this ****ing BAT all in one installion to work. I'm really just about to flash it all manually through ADB but I'd rather use the installer to make sure I get the random WINGS files removed or whatever. Any help would be great , thanks.
I have a HTC Google Nexus 9 tablet. I recently received the update to Android 6.0.1 via the normal push notification. The update got stuck on ‘optimizing your apps 1 of 74’. It normally moves up in the numbers within minutes but it remained on ‘1 of 74’ for an entire night. So, the next morning I switched off by holding the power button.
The system still booted but soon enough I received error messages like ‘there is an internal error, contact the manufacturer’ and during the boot it says that my system was corrupted.
I decided on a factory reset. It went through with it. But when setting up the cleaned system, there is another problem: I can pick my language and connect to my WIFi without problem. But then it goes to a screen where it says ‘checking connection. This may take a while.’ It gets stuck there for several hours - so it is clearly faulty as I don’t think ‘a while’ means 12 hours and more. I also don’t think that the factory reset solved the problem anyway as I still receive error messages, hinting at a corrupted system, during and after the boot.
So, I decided to try to flash a system image.
I got the Minimal Android Debugging Bridge ADB and Fastboot on Windows 7 and Ubuntu,
Then I followed the Google developers instructions and downloaded Volantis MOB30D from there.
I also got Android drivers for Windows, but I’m not entirely certain if they are right.
When I connect the Nexus 9 to the Windows computer, I now see in Device manager: ASUS Android Devices -> Android ADB Interface
It’s not an ASUS tablet though and I can’t see the Nexus 9 in ‘Computer’ (it used to show up there as ‘Portable Media player’
Is it possible that I got the wronger drivers and if so, how would I install the correct ones?
Then I start the Nexus 9 and hold power and volume up down to get to the bootloader.
It says ‘Fastboot USB’
I also says ‘device state - locked’ . I can’t get to the system settings to do the OEM unlock as I’m stuck on ‘checking connection’ when I boot normally.
Then I opened ‘Minimal ADB and Fastboot’ on Windows and tried the following commands:
Fastboot flashing unlock
… and it says:
FAILED (remote not allowed)
Then …
Fastboot oem unlock
… and it says:
(bootloader) ability is 0
(bootloader) permission denied for this command
Then I tried the same on Ubuntu. The device doesn’t show in the left hand side panel. When I try the above commands it just says
waiting for device
So, I guess Ubuntu doesn’t even recognize the Nexus 9
I then opened ‘Additional Drivers’ but it just says searching for available drivers and then no proprietary drivers are in use on this system
Any advice for Nexus 9 drivers on Ubuntu?
I also tried from the bootloader: Hboot → Recovery → Apply update from ADB
In Ubuntu I went to the directory where the ZIp file of the system image is located
Then I typed in the terminal:
adb sideload image-volantis-mob30d.zip
And it says …
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
1. You don't have correct drivers for Nexus 9. The Nexus Root Toolkit has a driver instillation guide.
2. You can not sideload factory images.
Try sideloading the failed ota available here
Code:
April 2016 Nexus OTA Updates - Security Level 2016-04-02
Nexus 9 (LTE) [URL="https://android.googleapis.com/packages/ota/google_flounderlte_volantisg/9ae7d85d6433d055a9e4f3049ac86eb0e562bbf1.signed-signed-volantisg-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
Nexus 9 (Wi-Fi) [URL="https://android.googleapis.com/packages/ota/google_flounder_volantis/6a2119f2077022c1ba852f2c613b8ce942c33836.signed-signed-volantis-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
If that doesn't work try sideloading Android N OTA
aeglyss said:
Any advice for Nexus 9 drivers on Ubuntu?
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
Click to expand...
Click to collapse
I don't know specifically about Ubuntu, but I've done several updates to usb-connected android devices using Debian linux, and I've never needed to add a device-specific driver.
Some additional ideas on the permissions:
(1) Did you enable "USB Debugging" in Settings->Developer Options?
(2) From your Linux machine, did you try to run adb as the root user or use sudo? I have to do this for both adb and fastboot. (Example command line: '$sudo adb devices', without the quotes.)
(3) Finally on the Linux side, did you try to connect first via adb? And, if so, did you look on your Nexus for an "Enable..." approval notification?
Good luck!
cheers,
john
Thanks everyone. I managed to fix it
aeglyss said:
Thanks everyone. I managed to fix it
Click to expand...
Click to collapse
Hi, I am at a similar point, my Google Nexus 9 failed doing the update, I then tried to factory re-set it and now it is trying to check connections...
I have downloaded the bootloader and my Windws 10 pc can see the tablet via explorer. I believe I have also switched the tablet to Fastboot but bootloader doesn't sem to be able to make the connection.
I was wondering if you are able to provide me with instruction as to how to rescue this tablet. I am not an expert, so I would appreciate any instructions to be as simple as possible.
Thank you for your help,
Mike
Hello. I just flashed the AOSiP OS ROM onto my Moto Z2 Force, and now I think my phone is soft bricked but in the strangest way possible.
I can't get past the booting animation so I can't get into the OS, but I can still get into recovery mode and download mode, but virtually nothing is working for me in those modes. In download (Fastboot Flash Mode) mode when I plug my phone into my PC, the computer doesn't let me do anything with the phone. If I plug it in Windows makes the sound like something has just been plugged in, but it doesn't let me access the device. If I go to devices and printers, I see it under unspecified as Fastboot nash S. And if I go to properties it recognizes it. It says Motorola ADB Interface and recognizes it as an android device, but I can't do anything with it and I can't access any files. Fastboot itself doesn't recognize the device either. When I type "adb devices" in my command prompt it doesn't come up in the list, and so I can't flash anything from my computer to fix this. I think it may be because before my phone bricked USB debugging wasn't enabled, but I don't think there is any way to enable now. If anyone knows of a method to enable it that'd be awesome.
I have installed all appropriate drivers, and up until right now it has detected it with no problem.
This is what the command prompt says when I try to detect it: (also tried adb sideload with no luck)
C:\Users\Louis\AppData\Local\Android\Sdk\tools>adb sideload twrp-3.3.1-0-nash.img
loading: 'twrp-3.3.1-0-nash.img'
error: no devices/emulators found
C:\Users\Louis\AppData\Local\Android\Sdk\tools>adb devices
List of devices attached
If I go to recovery mode (it was TWRP but now after flashing AOSiP it's back to just regular android recovery mode because I made a mistake so I lost everything) I get an immediate error message saying:
"Supported API:3
E: Failed to Clear BCB message: failed to open /dev/block/bootdevice/by-game/mi.... and the rest of the text goes off screen and I can't see it.
Below that it says
: No such file or directory."
If I try apply update from SD card I get an error message saying:
-- Couldn't mount /sdcard.
Installation aborted. Followed by the same error message as above.
Just like with download mode this was working perfectly fine before flashing this rom.
I feel totally stuck and I have no idea what to do.
Any help would be greatly appreciated.
I unlocked my bootloader recently and all went fine. But my banking apps didn't work, so I decided to relock it. This is where everything went wrong
I get an error message with "The current image(boot/recovery) have been destroyed and cannot boot. Please flash the correct image or contact customer service to fix it"
I went into recovery mode and wiped my data, still doesnt work.
When I try to install from storage, it doesn't give me any usb option and the online update doesn't connect to the internet.
In adb I can find the device, but it's unauthorised so any command comes up with
"This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
This also means I can't go into fastboot to flash a system image.
Does anyone know how I can fix this?
Turn off the device, and then hold the power button as well as BOTH volume buttons, this should put you into fastboot mode
a
There is dedicated thread for u r solution in how to
Hi,
I just went through the unlocking process and wanted to share a few things I noticed. It won't be a "unlocking guide", but more kind of a "collection of tips and tricks". Hope this can help someone in sorting things out. Happy unlocking to everyone!
Disclaimer
I am writing these things here with my best knowledge, but I cannot guarantee they are 100% correct. So please take them at your own risk! Feel also free to respond in case I (probably) got something wrong.
"EU/global version" of Mi Pad 4
As someone stated in another thread, and as I understood it, there is no such "global" or "EU" version of this tablet, but there is a "global/EU" ROM you can flash on it. And it seems that in europe there has been some market on these tablets that came with the global ROM preinstalled. As far as I know, the only way to flash the global/EU ROM is to unlock the bootloader, so these sellers had to go through the same process of unlocking. Now the problem is: to unlock the bootloader you require to link the tablet with a Xiaomi account, and you need the same account to unlock it again. So I guess that for these tablets one needs to be careful when buying them with the global ROM preinstalled, as you may need the phone number associated with the Xiaomi account that was set by the seller back then to unlock it again! Fortunately the one I bought came with the official chinese ROM and with no Xiaomi account linked to it, so I could manage to unlock it.
SIM card being necessary to unlock bootloader
I read that in some guides it is stated that you need to have a SIM card to unlock the bootloader installed in the tablet, and some users are asking how to do this on wifi only tablets. From what I've seen, there is no such prerequisite for wifi-only devices (which is kind of obvious, but peaople still ask). You still have to give a phone number to confirm your Xiaomi account as there is the need to enter some security code sent via SMS at some point. But the SIM card holding that number can obviously be on any phone!
About Xiaomi Fastboot drivers for Windows
I had several issues on making the Xiaomi Fastboot drivers working on my Windows PC: On my laptop running Windows 11, I had the issue that whenever the Xiaomi Unlock Tool was trying to connect, the Fastboot mode on the tablet just stopped with the message "press any key to shutdown". This seems to be a driver issue on some USB3 ports. Someone claimed there is a solution (see this post), but I used a Windows 10 laptop instead (also with only USB3 ports) and it worked OK there. Also, sometimes I connect the tablet via USB in Fasboot mode and I get no response on Windows (as nothing is attached). I solved it by uninstalling the device and re-installing the drivers manually that are provided in the Xiaomi Unlock Tool "driver" folder.
To check whether the drivers are working, just connect the tablet via USB while in Fastboot mode and check the Windows device manager. If device "Android Bootloader Interface" is properly installed (I got Xiaomi Drivers v16.0.0.0), you should be all set. If you get "Android device" or something with a question mark on it, I suggest to install manually the drivers (right click on the device, select "update drivers", then "Browse on my computer", and point to the "driver\win10" or "driver\xp-win7-win8" folder of the Xiaomi Unlock Tool).
If you have fastboot in your Windows PATH, read here, otherwise just ignore this
It seems that the Xiaomi Unlock Tool has a "fasboot.exe" in its own folder, which it has to use to unlock the bootloader. In my case, I already had adb and fastboot in my Windows PATH (so that I could just type "adb" in any CMD), and I think that the tool was using my fastboot version instead of its own one. The issue I had is that for some reason, the unlock process was hanging on 99%, and the tablet was then exiting fastboot and booting back to system. I checked the log and it seems to me that some fastboot commands were failing. As soon as I removed fastboot from Windows path, it magically worked. So my advice here is to simply remove whatever fastboot you have in the Windows path before using the unlock tool.
Unlocking steps I did
Finally, here's what I did to unlock it. Again, disclaimer: I don't know if these steps are 100% correct, but they worked in my case. So follow them at your own risk!
I did it on a Mi Pad 4 Wifi with the stock chinese ROM (running MIUI 10.3.2 & Android 8.1.0).
Go to Settings -> Mi Account and login to your Xiaomi account on the tablet, or if you don't have any, make one. Make sure the phone number you entered is reachable.
Go to Settings -> Additional settings -> Developer options and make sure "OEM Unlocking" and "USB Debugging" are turned on.
Still on the Developer options, go to "Mi Unlock Status". If it says "Unlocked", well guess what., you can stop here . If not, tap on "Add account and device" and wait for the success message. If you get something like "try later" (my case), what I did is to logout and re-login on the Xiaomi account. I then got the "success" message finally.
Download the Xiaomi Unlock Tool from here. Extract somewhere but do not start yet.
Open Windows Device Manager (Win+R, enter "devmgmt.msc").
Turn off the tablet and boot to Fastboot (Vol. Down + Power buttons). Now connect the tablet via USB.
First check on the tablet: if it shows "press any key to shutdown", then you have a driver issue. Please see this post for the solution, or try using a different PC.
Then, check on the device manager. If you see just "Android" with a question mark popping up, then you need to install the drivers. If you see "Android Bootloader Interface", then you are all set. If you don't see anything, then you need to uninstall and reinstall the drivers instead.
To install the drivers: right click on the device with question mark, select "update drivers", then "Browse on my computer", and point to the "driver\win10" or "driver\xp-win7-win8" folder where you extracted the Xiaomi Unlock Tool. After installing the drivers, try to boot to fastboot a second time. If you don't see the previously mentioned "press any key to shutdown", then you are all set.
To uninstall the device: On Windows Device Manager menu, go to "View" -> "Show hidden devices". You should find a greyed out "Android Bootloader Interface". Right click on it and select "Uninstall". Then, repeat the process again (boot to fastboot etc) and hopefully you will get the "Android device" with question mark where you can install drivers on.
Before starting the unlock tool, make sure you don't have any adb or fastboot in your windows PATH. You can check it by simply typing "fastboot --version" on any Windows CMD and see if it does something. In case you have, you better remove it, as the unlock tool has its own version of fastboot packed with it and you better let it use that one instead.
Once drivers are installed, start the Unlock Tool and login to your Xiaomi account. Then, once you see "not connected to the phone", boot the device to Fasboot again and quickly connect it via USB. If you see "Please wait 168 hours" or something like that (I did not see any of that), then most of the guides say that unfortunately you have to wait.
If you see the "Unlock button" not being grayed out anymore, then go for it. Get rid of the annoying popups saying "you are a bad person if you unlock", and finger crossed everything goes smooth!
Cheers,
Michele
Hi thank you for sharing this,
My Mipad 4 is LTE version, however the SIM only works when I turn on Wifi. Therefor, I can't start unlocking as I couldn't connect via Mobile Data.
Is there any solution for this?