I am trying to unlock the bootloader on my US Moto G 16 G. I have followed the instructions provided in Unlock Youe Device and Android Pit. I have followed the instructions in the FAQ as well.
After I input "$ fastboot oem get_unlock_code" i get the following reply " '$' is not recognized as an internal or external command, operable program, or batch file."
I have searched for the reply in Google, but I cannot come across another user who has documented this issue and how to resolve it. Any help would be greatly appreciated.
You are not supposed to write the $ symbol, start with "fastboot..."
Sent from my XT1032 using xda app-developers app
kafepuya said:
I am trying to unlock the bootloader on my US Moto G 16 G. I have followed the instructions provided in Unlock Youe Device and Android Pit. I have followed the instructions in the FAQ as well.
After I input "$ fastboot oem get_unlock_code" i get the following reply " '$' is not recognized as an internal or external command, operable program, or batch file."
I have searched for the reply in Google, but I cannot come across another user who has documented this issue and how to resolve it. Any help would be greatly appreciated.
Click to expand...
Click to collapse
The $`s are not to be typed bro and the correct cmd command afaik is : fastboot oem get_unlock_data
Thanks for pointing out the mistake on the command. I tried the correct way of doing it, and I still get essentially the same reply. Here is a screenshot to illustrate my situation.
{
"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"
}
I got the same, when you paste the code into the box click and delete all spaces and make sure there are no spaces at the beggining of the code also.
kieranc88 said:
I got the same, when you paste the code into the box click and delete all spaces and make sure there are no spaces at the beggining of the code also.
Click to expand...
Click to collapse
No dice bro. No matter what I type, I get back "[whatever the first word in the command I type] is not recognized as an internal or external command, operable program or batch file.
I don't even know what to try next.
Oh I get you now, have you got fastboot and adb installed? If so point it to the folder that contains fastboot and adb iI usually place it on c drive in a folder called android so in command prompt to point it adb I would type cd c:/android then execute your commands
kieranc88 said:
Oh I get you now, have you got fastboot and adb installed? If so point it to the folder that contains fastboot and adb iI usually place it on c drive in a folder called android so in command prompt to point it adb I would type cd c:/android then execute your commands
Click to expand...
Click to collapse
Well, I don't know if I have adb installed. I only downloaded and installed the 2 files mentioned in the Motorola page. Android SDK and the latest Motorola drivers. I can navigate to any folder in terminal (all I do is Shift+Right click on a folder and select open command window here...)
If you haven't got adb and fastboot installed look here http://forum.xda-developers.com/showthread.php?p=42407269
kieranc88 said:
If you haven't got adb and fastboot installed look here http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
Well, that sure is quite more than was in the Motorola website. Ill read up on that and figure out how to do it. Thanks a lot. I'll keep you posted.
You don't actually need the android SDK ,install adb and fastboot from the previous link I posted above
Install drivers point cmd to folder containing adb and fast boot type in cmd "adb devices" if your phone is recognised it will show a serial number,if so continue with the unlock process,
If its not recognised the drivers aren't installed properly if so download pdanet for windows and set it up ( its a tethering app but it installs drivers) get it here http://pdanet.co/bin/PdaNetA4126.exe
Check again if device is recognised and if so continue with rest of process
---------- Post added at 12:59 AM ---------- Previous post was at 12:51 AM ----------
For an easier way to install adb check this out http://forum.xda-developers.com/showthread.php?t=2588979
kieranc88 said:
You don't actually need the android SDK ,install adb and fastboot from the previous link I posted above
Install drivers point cmd to folder containing adb and fast boot type in cmd "adb devices" if your phone is recognised it will show a serial number,if so continue with the unlock process,
If its not recognised the drivers aren't installed properly if so download pdanet for windows and set it up ( its a tethering app but it installs drivers) get it here http://pdanet.co/bin/PdaNetA4126.exe
Check again if device is recognised and if so continue with rest of process
---------- Post added at 12:59 AM ---------- Previous post was at 12:51 AM ----------
For an easier way to install adb check this out http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I did it! Thanks for all the great help, specially kieranc88. Xposed here I come!!!
Related
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
quantum94 said:
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
Click to expand...
Click to collapse
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
root-expert said:
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
Click to expand...
Click to collapse
nopes...on typing "fastboot code", it redirects me to the current directory:
{
"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"
}
what to do?
Are you sure you are in fastboot mode?
root-expert said:
Are you sure you are in fastboot mode?
Click to expand...
Click to collapse
pretty sure...u can see the pic at:
What now!? :crying:
quantum94 said:
pretty sure...u can see the pic at:
What now!? :crying:
Click to expand...
Click to collapse
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
root-expert said:
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
Click to expand...
Click to collapse
sorry for the late reply....
I tried the same thing on different pc and it worked!
But i have another problem!
I installed cm11 nightly for my on my x plus from here:
http://get.cm/get/qG0
After that my imei has gone blank along with the baseband version.
I did a bit of research and found that by using ruu, u can get the imei back.
So for that i needed turn my s-on to s-off by the foll commands:
adb reboot
if i am not mistaken, while the phone is rebooting i am supposed to put the 2nd command:
adb wait-for-device push firewater /data/local/tmp
The problem here that I think is the phone reboots so fast that i guess the command fails to execute and i get an error saying :
error protocol fault (no status)
So, how to turn off fastboot or quickboot in cm11? There is absolutely no option in the phone. I tried battery settings,power settings, everything!
is there a way to disable fastboot/quickboot in bootloader mode?
plz help!
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Bencaill said:
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Click to expand...
Click to collapse
Hello, are you sure you have the boot.img also in the direcotry?
DallasCZ said:
Hello, are you sure you have the boot.img also in the direcotry?
Click to expand...
Click to collapse
yes, I am sure I have it
Bencaill said:
yes, I am sure I have it
Click to expand...
Click to collapse
i tried it again and it works well for me.
can you post a creen of the folder where you extracted the files?
{
"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"
}
you have to run the root.bat file, you cannot dir the boot.img
I know I have to run the bat file but you asked me a screen of the folder
I have this message:
strange... idunno for me its working well (windows 7 pro) and the boot.img is in the same directory... do you have some antivirus, anti spam apps running?
A other member of Frandroid forum has exactly the same issue. But he is running W8.1
That is really strange.
I am running win 8.1 as well
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
The problem seems to be resolved by using Windows 7 instead.
http://forum.frandroid.com/topic/223905-tuto-root-de-l-idol-3-55/?p=3417628
using win 7 is not a solution... there have to be a way how to do it, because there are thousands of users with win 8.1 who using fastboot and adb commands...
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
is your bootloader unlocked?
And I take it you've enabled Developer Options and USB Debugging?
After all my talk about the ease of communicating with Android devices from a Mac, I'm now unable to successfully issue fastboot commands when in the bootloader. I've tried using sudo, making sure to include arguments that address the device, etc. I can execute adb commands when the phone's system is booted, though. But fastboot commands either get me a "waiting for device" or nothing at all. I thought I was able to do this successfully yesterday, when I was just testing it out. Today, I was going to root by booting into TWRP and flashing SuperSU.
maigre said:
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
Click to expand...
Click to collapse
If it was a driver issue, my phone would not restart with the command, every drivers are OK
ractar28 said:
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
Click to expand...
Click to collapse
Your method worked !!!!!!!!!!!!!!! THX !!!!!
Being used to the back button on the right side and the recent items on the left i noticed there is no option to set that in the settings menu.
Or at least i could not find it.....
You will need ADB on the PC/Laptop and connect the phone to it.
Download of ADB can be found here: https://forum.xda-developers.com/showthread.php?t=2588979
So i found a nice post https://forum.xda-developers.com/pixel-xl/help/swap-recent-button-oreo-t3687721 that enables it.
NO ROOT required, just enable ADB in developer settings.
Then start ADB shell
Enter this command and you are done.
settings put secure sysui_nav_bar "space,recent;home;back,space"
All happy now.
Thanks !
Do you know if we can change long press action with this method ?
rqdb said:
Thanks !
Do you know if we can change long press action with this method ?
Click to expand...
Click to collapse
If we can find the command for it i suppose we can. Not sure how we can find this.
Verstuurd vanaf mijn Nokia 7 plus met Tapatalk
Thanks for sharing and one stupid question....OTA still work after ADB shell?
supremeee said:
Thanks for sharing and one stupid question....OTA still work after ADB shell?
Click to expand...
Click to collapse
It should. No modification is done to the file system.
Verstuurd vanaf mijn Nokia 7 plus met Tapatalk
Brotuck said:
Then start ADB shell
Enter this command and you are done.
settings put secure sysui_nav_bar "space,recent;home;back,space"
All happy now.
Click to expand...
Click to collapse
Doing this you'll loose the keyboard switching icon that appears when you have multiple virtual keyboards. The command including this icon is:
settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
I'm having difficulties getting ADB to work(authorization popup does not appear). Any ideas?
{
"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"
}
:edit:
Any chance this feature is hidden in the global built (albeit hidden) and can be pulled out using adb?
Answer by Nokia assistance:
Thank you for contacting Nokia Mobile Care and your interest in Nokia mobile devices.
Regarding your request, we would like to inform you that this option does not exist.
We remain at your disposal if you have other questions or need our help.
Does the switch remain after rebooting the phone ? Or do i have to do this every time i reboot ?
Inpain said:
Does the switch remain after rebooting the phone ? Or do i have to do this every time i reboot ?
Click to expand...
Click to collapse
The change remains after reboot
After put in the command through adb shell, with Nokia 7 plus attached to the pc, I got a system ui error, phone does start up, but after that I got a black screen only , had to do a hard reset, lost all data.
riseandshine32 said:
After put in the command through adb shell, with Nokia 7 plus attached to the pc, I got a system ui error, phone does start up, but after that I got a black screen only , had to do a hard reset, lost all data.
Click to expand...
Click to collapse
Same
OC-Freak said:
Same
Click to expand...
Click to collapse
Working fine here, on Build number: 00WW_2_22A (May security patch build).
Did you type in the commands correctly (semicolons and commas) ?
Just did the command again on a fresh installed version with the May patches and all is fine.
Please make sure you type exact the correct syntax.
I always do a copy / paste on my laptop from the text on a adb shell
Excellent mate. worked like a charm on my Nokia 7 plus with latest system update
Nokia 7 Plus
Hey, I got the same phone like you!
But my phone is not in the devices list (adb devices)
Please help
Hello, I tried this but I'm always getting this error in adb command line:
C:\adb>settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
'settings' is not recognized as an internal or external command, operable program or batch file.
The underlined text I copy pasted it from this xda thread. When I do adb devices I see my device in the list, its the only android device thats connected to my computer. I don't have an idea how to fix it.
After some further experimenting I've gotting it done
In the adb command line you type folllowing command
1. adb devices
2. adb shell
3. settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
4. that's all
Wuter said:
Hello, I tried this but I'm always getting this error in adb command line:
C:\adb>settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
'settings' is not recognized as an internal or external command, operable program or batch file.
The underlined text I copy pasted it from this xda thread. When I do adb devices I see my device in the list, its the only android device thats connected to my computer. I don't have an idea how to fix it.
After some further experimenting I've gotting it done
In the adb command line you type folllowing command
1. adb devices
2. adb shell
3. settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
4. that's all
Click to expand...
Click to collapse
After Step 2 press ENTER
then the command prompt should enter a shell (you will see b2n_sprout:/)
in the shell you paste the command
See attached screenshot
Its there a way to change the icons to vanilla?
I am using 'fastboot oem unlock' but
Erorr shows me
'fastboot (remote : unknown command)
How to solve this problem
???
Please help me
Download the latest version of fastboot & ADB.
You can see what version adb and fastboot you have installed, just open a command window and type: sudo adb --version (then hit enter) sudo fastboot --version (hit enter key) that will show your installed version of those tools. I believe right now the latest is 31.02 but I could be wrong. It is updated often and using an older release of adb and fastboot can and will cause issues..
Go here to download adb and fastboot. https://developer.android.com/studio/releases/platform-tools
Just download the android sdk for whatever OS you use on your computer, unzip...
What is the device you are trying to unlock? Have you enabled developer options on the phone and changed usb settings to file transfer instead of the default which is charging? Also have if that was done did you keep a close eye on your device because there will be a small box that pops up that must be immediately checkmarked so that your computer can communicate with your device. Have you selected "allow oem unlock"Also in the developer options? it might be good idea to set your lock screen to "none" instead of having a lock set for it. Any time anything is installed on a computer it almost always needs to be rebooted. If you have not done any of that I would suggest doing it all.
Also depending on what device you are attempting to unlock the bootloader on, the wording could be slightly different. My Pixel 4XL uses: fastboot flashing unlock , to unlock bootloader. So keep that in mind as well. If you use Windows OS on your computer some day when you have a minute check out Linux. You can make a "live USB" burn a copy of a Linux distro to a USB drive and boot from it and or install it along with your Windows OS, aka dual boot... The very first time I used Linux, it was Ubuntu and quite a few years ago and I would never return to Windows!! Can't stand it! Linux is made for doing what we do to our phones.
If you need more any help with this some other time and still cannot get it installed message me on here or should I say "start a conversation" with me here on xda. Same thing with the new layout.. My user name is the same here on XDA as it is on telegram. Feel free to shoot me a message any time. It may take a some time to respond depending on what day it is and what time and all that but I will respond.
Here is one of the best guides in my opinion on how to get and setup adb and fastboot tools on MAC, Linux and Windows OS. https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
(Edited)
flash713 said:
it is not working, same error after update.............
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"
}
MBF_9802 said:
View attachment 5323891
Click to expand...
Click to collapse
Try typing: sudo fastboot --version & sudo adb --version and make 100/% that they are most current and up to date. I'll go grab a link really fast...
Okay idk how you installed adb & fastboot but this guide in my opinion is the best!!! https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Try using different ports, reboot your computer..
Did you already have the pop up on your device once connected to computer or no? If not your it won't work at all.
Enable developer options
USB debugging
Now plug in to a different USB port.
Now scroll down on phone to default USB configuration and change it from the default which is "charging" to "file transfer" but keep your eyes on your device screen because the pops up will only show itself for a few seconds. When it does checkmark the box. You should be good then. Windows has driver issues alot of the time!! I switched to Linux years ago and I have no driver issues. Or anything else far as that goes.
flash713 said:
Try typing: sudo fastboot --version & sudo adb --version and make 100/% that they are most current and up to date. I'll go grab a link really fast. Brb
Click to expand...
Click to collapse
MBF_9802 said:
View attachment 5323897
Click to expand...
Click to collapse
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
All try but reason only command not found
Please help......
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
Same error in updated version
How to solve
MBF_9802 said:
Same error in updated version
How to solve
Click to expand...
Click to collapse
Did you ever onstll universal usb drivers for adb? If not install them and afterwards reboot your computer and then try.
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
Same error in updated version
flash713 said:
Did you ever onstll universal usb drivers for adb? If not install them and afterwards reboot your computer and then try.
Click to expand...
Click to collapse
yes but same problem in universal usb drivers
Good morning,
I'm new here, and i hope you can help me with my problem.
I have a mi MJJGYY02FM projector and i did a update with USB stick with files from Xiaomi.
Now after the update the projector start with MI logo and than shuts down, after that he start up with no screen and do nothing.
Can someone help me how to fix this. i can't get the projector in a boot menu with the remote, maybe he dont recognize the remote.
Kind Regards,
Bas
Reflash projector's Stock ROM.
jwoegerbauer said:
Reflash projector's Stock ROM.
Click to expand...
Click to collapse
I have the stock ROM on USB now, but hè will not install it. When i press the home and enter button and plug the power cable. Hè start up with the MI logo and shuts down, then start up with no screen.
Are there other ways to install the stock ROM?
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Thanks
Im gonna search out and try that option.
I let it know when it works. maybe i have some questions.
jwoegerbauer said:
AFAIK the Stock ROM typically gets installed by means of ADB Sideload method:
Code:
adb devices
adb reboot sideload
adb sideload <FULL-PATH-TO-STOCK-ROM-ZIP-FILE-ON-PC-HERE>
Click to expand...
Click to collapse
Im trying something, but do you have a discription how to make that USB with the Stock Rom?
I got your files on my pc. I have a 16GB USB format FAT32.
What is the way to make that sideload with the ROM version?
Im sorry for the questions, but i have never done this before.
I have done thist thing
{
"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"
}
The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.
jwoegerbauer said:
The USB-stick, once plugged into Windows computer, in Windows OS is recognized as a drive: note down this drive letter returned. Then sequentially run the ADB commands listed above.
Click to expand...
Click to collapse
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?
Vross46 said:
Must i do the commander when the stock ROM is on the USB?
By what command must i write the letter from the USB?
Click to expand...
Click to collapse
My drive letter is :e
Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name
jwoegerbauer said:
Didn't think it can be so difficult.
Assumed the Stock ROM's file is located in root of E: drive then the ADB command in your case becomes
Code:
adb sideload E:\<NAME-OF-STOCK-ROM-ZIP-FILE>
where you have to substitute
<NAME-OF-STOCK-ROM-ZIP-FILE>
by ROM's true file name
Click to expand...
Click to collapse
ah ok. lets try.
It seems not so difficult but, for the first time is everything more difficult
What do i wrong. sorry! I do really my best
1, i have a format 16gb usb FAT32
2. i have install ADB installer.
3. i have download the stock rom (see picture)
4. my drive name is e:
5. When i zip my stock rom file, i got an another zip file, and an file of 1kb
in the next picture is what i do in CMD
anglee_full_9.0.0.1911 is my zipped stock rom downloadfile
the other 2 are the unzipped files from the first file
1st screenshot provided above shows
1. Device isn't connected via USB-cable with PC or, if, not powered on
2. The ROM's archive name you entered is without fileextension -> required :ZIP
If ROM's archive is packed as .RAR file then you have it to repack to .ZIP file
I think it will not gonna help.
When i connect my projector to the pc, the pc dont recognize him.
What i try, nothing works.
but thanks for your help anyway
Have you ever enabled "USB Debug" in Android's Settings -> Developer otions?
I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check
Vross46 said:
I dont know if its enabled. But now in can not come in the menu.
MI logo shine for 1 second. And it turns off.
So i have no possibillity to check
Click to expand...
Click to collapse
Hello Vross46, have you been able to solve your problem? I’m stuck with the logo as well