[Guide] Fix "press any key to shutdown" when unlock bootloader or run fastboot cmd - Xiaomi Mi Mix 2S Guides, News, & Discussion

[Guide] Fix "press any key to shutdown" when unlock bootloader or run fastboot cmd - Xiaomi Mi Mix 2S Guides, News, & Discussion

[Guide] Fix "press any key to shutdown" when unlock bootloader or run fastboot cmd
For some Windows 10 users (like me), it seems impossible to unlock the bootloader of their Xiaomi devices. Because every time they run MiFlashUnlock and connect their phone in fastboot mode to the computer, the phone will immediately exit the fastboot mode and display "press any key to shutdown". At the same time, MiFlashUnlock displays "not connected to the phone".
At the same time, if you manually run the "fastboot devices" command, it can discover the device for the first time, but soon, the device id becomes "??????". After a few seconds, the device completely disappeared from the "fastboot devices" result and disappeared from the Windows Device Manager.
My Xiaomi MIX 2s is facing this problem. I spent a lot of time searching and trying solutions.
* Connect the phone to the USB2.0 interface. Not working.
* Uninstall the kedacom driver. Not working.
* Uninstall all fastboot drivers in safe mode and reinstall the version provided by Xiaomi. Not working.
* Replace fastboot.exe with the version provided by Google. Not working.
* Try different versions of mi unlock tools. Not working.
* Kill all "fastboot.exe" processes and try again. Not working.
Then, I started looking for a different solution on the Internet, and finally found one:
1. Start an admin PowerShell (or admin CMD if you want). You can right click on the start button and select "PowerShell (Administrator)".
2. Enter the following commands to create 3 registry entries.
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
3. Restart your phone, let it enter fastboot mode, and then connect to the computer. At this point, the unlocking should proceed normally, and the device no longer disappears from the "fastboot devices" result and Windows Device Manager.
I have successfully unlocked my Mi MIX 2s with this solution. And "fastboot boot recovery.img" command works well.
If it is useful to you, I will be very happy.

That didn't work for me, but the download from this thread here worked perfectly for me.

SwimmingTiger said:
[Guide] Fix "press any key to shutdown" when unlock bootloader or run fastboot cmd
For some Windows 10 users (like me), it seems impossible to unlock the bootloader of their Xiaomi devices. Because every time they run MiFlashUnlock and connect their phone in fastboot mode to the computer, the phone will immediately exit the fastboot mode and display "press any key to shutdown". At the same time, MiFlashUnlock displays "not connected to the phone".
At the same time, if you manually run the "fastboot devices" command, it can discover the device for the first time, but soon, the device id becomes "??????". After a few seconds, the device completely disappeared from the "fastboot devices" result and disappeared from the Windows Device Manager.
My Xiaomi MIX 2s is facing this problem. I spent a lot of time searching and trying solutions.
* Connect the phone to the USB2.0 interface. Not working.
* Uninstall the kedacom driver. Not working.
* Uninstall all fastboot drivers in safe mode and reinstall the version provided by Xiaomi. Not working.
* Replace fastboot.exe with the version provided by Google. Not working.
* Try different versions of mi unlock tools. Not working.
* Kill all "fastboot.exe" processes and try again. Not working.
Then, I started looking for a different solution on the Internet, and finally found one:
1. Start an admin PowerShell (or admin CMD if you want). You can right click on the start button and select "PowerShell (Administrator)".
2. Enter the following commands to create 3 registry entries.
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
3. Restart your phone, let it enter fastboot mode, and then connect to the computer. At this point, the unlocking should proceed normally, and the device no longer disappears from the "fastboot devices" result and Windows Device Manager.
I have successfully unlocked my Mi MIX 2s with this solution. And "fastboot boot recovery.img" command works well.
If it is useful to you, I will be very happy.
Click to expand...
Click to collapse
you a genius . you fixed my problem

Thanks bro you solved my problem after weeks

Thank you!
This worked for me on Xiaomi Redmi Note 6 Pro (WIndows 10, unlock tool version 5.5.224.24).

I cant get the Unlocker to work. Tried everything on two different PC`s.
Fastboot and ADB find the device in windows, but the UnlockTool dont. Dunno why this is such a hazzle

lifeflayer said:
That didn't work for me, but the download from this thread here worked perfectly for me.
Click to expand...
Click to collapse
i can confirm also its working the solution in that thread.
PS:i didnt try the solution in this thread it was easier to download the bat from the other thread.

Alucard77fa said:
Bro u save my life,I try a lot of methods for 2 hours and your post helped me in less than 2 minutes, thanks!
Click to expand...
Click to collapse
Hi, would you mind to share a xqcn backup ? my mi mix 2s is lossing imei, tried qcn from internet does restore imei but doesn't restore the signal.

zacky_travis said:
Hi, would you mind to share a xqcn backup ? my mi mix 2s is lossing imei, tried qcn from internet does restore imei but doesn't restore the signal.
Click to expand...
Click to collapse
Sorry man but i dont have the mi a2 anymore, im only working fixing phones and i return the cellphone the same day .

find someone made bat file use those commands, remember run this file with admin right
https://drive.google.com/file/d/1dnQyJrpRgN-lqluQru1o93HU6BxbqaUf/view?usp=drivesdk

Related

[Q] Windows drivers for Nabi2

I've read a couple dozen of the pages from http://forum.xda-developers.com/showthread.php?t=1905674&page=95 titled
Nabi2 root and Gapps install
Click to expand...
Click to collapse
.
Using Win7 x64. Nabi2 version: 1.9.37 recently updated.
Can't post to above thread because this is my first post (restricted to "General" forums).
In "Jmz Nabi Recovery Installer" window it is always stuck in the "If stuck here drivers are not installed" step.
Prior to installing "PdaNet for Android" from http://junefabrics.com/index.php,
I had 2 devices in Control Panel under "Other devices" with a yellow '!'. One of the looked like the Nabi device. The other is named "MTP".
After installing PdaNet, only MTP remains with the yellow exclamation point.
What should the Nabi look like in the Control Panel if its properly configured with a driver and where would it be?
And what is MTP?
Apparently I'm still having a driver/connection problem from adb.
USB Debugging is on in the Nabi.

Put the nabi in 'fastboot' mode
Open a CMD Prompt and browse to the 'files' folder within 'jmzrootpackage'
Then type:
adb.exe
fastboot devices
It should return a value (fastboot working and drivers are installed)
Let me know how it goes.

Put the nabi in 'fastboot' mode
Open a CMD Prompt and browse to the 'files' folder within 'jmzrootpackage'
Then type:
adb.exe
Click to expand...
Click to collapse
Part of this command is missing right? Without input parms it just outputs the "uses" message.
fastboot devices
Click to expand...
Click to collapse
Unfortunately this returned nothing for me.
I'm glad you responded. Other suggestions?

Here is how i done it using Windows 8 x64
I done 3 nabi2's this way but had a lot of trouble first so here is what worked for me:
Sadly, i don't have any nabi2 with me now to explain exactly how i done it
1) First boot the Nabi2 normally and turn off usb debugging.
2) When fully booted connect USB cable.
3) Check device manager and drivers should be installed.
4) Unplug USB cable and turn on USB Debugging and Unknown Sources.
5) Reconnect USB Cable.
6) Drivers should install.
7) Install PDA Net on Laptop/PC
8) Select Samsung device from option screen when installing.
9) Wait for install to complete and drivers to install
10) Shut down Nabi2
11) Boot Nabi in fastboot (Hold + and Power buttons)
12) Select fastboot protocol
13) Here i seen Windows 8 take about 60 seconds installing fastboot drivers
To make sure fastboot drivers are installed i went to this thread
Code:
http://forum.xda-developers.com/showthread.php?t=1590800
and download ADB (save it to C:\SDK\platform-tools) and read over the helpful instructions in the thread.
Open command Prompt
Type the following (shown in RED) in the CMD window the opened:
cd\
cd C:\SDK\platform-tools
adb.exe (a list of options should be listed)
fastboot devices (it should list a number after you enter this)
If number displayed then you are good to go.
Reboot Nabi2 and wait to complete
Go to the location you saved jmzrootpackage
Go to files folder inside jmzrootpackage
Double click install.bat
Follow on screen prompts ( I took option 1)
TWRP recovery installs
I had trouble installing GAPPS.zip with an error being displayed about unable to mount /data
I copied GAPPS.zip to a SD Card and inserted to Nabi2
i install zip from EXT-SD Card even though it gives a load of errors about not able to mount /data
Wipe Cache/Dalvik
Reboot Nabi2
Go to daddy/mommy mode and you should have Google Apps installed.
Any problems let me know.

I'm using Windows 7 x64.
Your instructions with selecting "Samsung" for PdaNet install appears
to have done something right. So maybe I'm a little closer.
It completed the PdaNet install successfully and when I reconnect the
Nabi I see a message popup on Windows saying PdaNet connected something.
(It was too quick.)
So maybe I'm not doing the "Fastboot" portion correctly.
On Nabi hold <Power> and <Vol+> down at same time to turn it on.
Resulting Menu:
Boot Normally
Fastboot Protocol
Recovery Kernel
Forced Recovery
Use <Vol-> to move the selected item.
Moved selected item down to "Fastboot Protocol".
Use <Vol+> to "enter" selected item.
New Menu:
Bootloader
Continue
Reboot-bootloader
Reboot
Poweroff
Selected "Continue", and entered(<Vol+>).
At this point the Nabi boots up.
On PC in adminstrator mode for command window and with ALL anti-virus
security turned off:
> adb.exe kill-server
> adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> fastboot.exe devices
Nothing. (sigh)

After looking at Victoria Antonio's youtube of this process I'm convinced the driver install is still not correct.
Somehow it gets mucked up when I use PdaNet. Not sure how or why.
To make this picture clearer I posted some screen shots on my website: http <colon, 2 forward slashes>skippyvondrake.com
I hope someone can tell me how to unmuck what I've mucked.

skippyV said:
Selected "Continue", and entered(<Vol+>).)
Click to expand...
Click to collapse
Don't press Continue on the Nabi after selecting fastboot protocol
After selecting fastboot protocol leave it.
skippyV said:
> fastboot.exe devices
Click to expand...
Click to collapse
The command is:
fastboot devices
not
fastboot.exe devices

Thanks for telling me about when I'm in fastboot mode.
I DO get a device number when in fastboot mode and from 'fastboot devices'
But adb still cannot "see" the device. All commands using adb result in:
error: device not found
Regardless of what mode the Nabi is in.

SOLVED
I finally decided to try this with a different computer. Same OS and architecture.
But this computer didn't have various android development "kits" installed previously.
And it worked without a hitch.
The youtube by Victoria Antonio pointed out a few nuances I didn't know.
And you helped too, BBKGTTDi, so giving you "thank you" points.
Chow!

Glad you got it work SkippyV
I just need to figure out now, when i download a game to the Nabi2 from the playstore, how to get it so show in the kids mode

BBKGTTDi said:
Glad you got it work SkippyV
I just need to figure out now, when i download a game to the Nabi2 from the playstore, how to get it so show in the kids mode
Click to expand...
Click to collapse
When I get there - if I figure it out - I'll send you a private email sense that would be a different "thread'. There are other nuances I've noticed too...

show game in Nabi mode after rooting
@BBKGTTDi, I thought there would be a way to send private messages/emails on this forum - but I don't see it.
I ran into the same problem after rooting the Nabi. The "Add Apps" app doesn't work as its supposed to.
It worked prior to rooting.
It does list the newly installed apps, but selecting them for Nabi-Mode, rebooting, and they aren't there.
Only visible in Mommy/Daddy mode.
So if you figure it out please let me know!

The "Add Apps" app is working correctly now. Don't know what happened before.
I must be getting "Nabi-ed out".
Let me know if you're still having troubles.

skippyV said:
I'm using Windows 7 x64.
Your instructions with selecting "Samsung" for PdaNet install appears
to have done something right. So maybe I'm a little closer.
It completed the PdaNet install successfully and when I reconnect the
Nabi I see a message popup on Windows saying PdaNet connected something.
(It was too quick.)
So maybe I'm not doing the "Fastboot" portion correctly.
On Nabi hold <Power> and <Vol+> down at same time to turn it on.
Resulting Menu:
Boot Normally
Fastboot Protocol
Recovery Kernel
Forced Recovery
Use <Vol-> to move the selected item.
Moved selected item down to "Fastboot Protocol".
Use <Vol+> to "enter" selected item.
New Menu:
Bootloader
Continue
Reboot-bootloader
Reboot
Poweroff
Selected "Continue", and entered(<Vol+>).
At this point the Nabi boots up.
On PC in adminstrator mode for command window and with ALL anti-virus
security turned off:
> adb.exe kill-server
> adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> fastboot.exe devices
Nothing. (sigh)
Click to expand...
Click to collapse
I ve got the same problem using windows xp, 7 or 8.1 after OTA update to jellybean.
Any ideas of what is going on?

arvati said:
I ve got the same problem using windows xp, 7 or 8.1 after OTA update to jellybean.
Any ideas of what is going on?
Click to expand...
Click to collapse
I did have those problems last year. Still think they were driver related.
I use mehtuus's package now. He has a useful install script.
http://forum.xda-developers.com/showthread.php?t=2172843
And when I want to use adb in "manual" mode I just launch a command prompt from his
'adb' directory (package is named 'mn2ri-v1.5.0-beta2.zip').
Try playing with his installer. And see if anything is displayed using:
Code:
adb devices

Thanks skippyV. I got it in fastboot last week with ubuntu and installed TWRP sucessfully.

[Q] Windows 7 x64 isn't accepting Nexus S in fastboot, driver issue

I've been at this the entire evening, but can't seem to get it to work.
I installed the latest driver package (https://github.com/koush/UniversalAdbDriver) which should make W7x64 accept my NexS in fastboot mode. But it doesn't. All other modes are recognized, but in fastboot it keeps saying "Android 1.0" with that yellow exclamation mark on it.
I also tried the "have disk..." option and fed it the "android_winusb.inf", but it said this wasn't compatible with x64. What else can I try?

How to Install ADB and Fastboot: Method 1
To quickly and easily install ADB and Fastboot on your Windows XP, Vista, 7, and 8/8.1 computer (32-bit and 64-bit), do the followingownload the latest*ADB Installer file*(adb-setup-1.4.2.exe).Right-click the file*adb-setup-1.3.exe*and choose “Run as Administrator“.Type “Y” and press Enter to install ADB and Fastboot, and set the environment variables. Enter “N” if you don’t want to do the same and want to just install the drivers.In the next step, enter “Y” to install the drivers for your device. Enter “N” to skip this step.Wait till the driver installation finishes up. That would take only some seconds.To verify that you have successfully setup ADB and fastboot, open up a command prompt (press*Windows key + R*-> type in*cmd*->*OK) and enter “adb version” (without quotes). If it returns something like “Android Debug Bridge version x.x.xx“, then your ADB and Fastboot are all-ready.Congrats! You are ready to rock!Read more at http://dottech.org/21534/how-to-ins...m8Vo3.99QUOTE=Lex_Michdeandroid;56140163]I've been at this the entire evening, but can't seem to get it to work.
I installed the latest driver package (https://github.com/koush/UniversalAdbDriver) which should make W7x64 accept my NexS in fastboot mode. But it doesn't. All other modes are recognized, but in fastboot it keeps saying "Android 1.0" with that yellow exclamation mark on it.
I also tried the "have disk..." option and fed it the "android_winusb.inf", but it said this wasn't compatible with x64. What else can I try?[/QUOTE]
Hi There.

Fix "unable to load" using fastboot and windows 10

I have been frustrated trying to use fastboot commands, especially the "flash" command on my windows 10 laptop. I continually got an "unable to load' message. I have reloaded the drivers manually as recommended by some, which still did not work. Well, it turns out that you need the complete path in the fastboot command line when using 10. Put your img, bin files in a folder you will be using. Open the command prompt using the windows-x keys. Select the command prompt from the menu.. It does not need to be the administrator. Use the fastbooot devices command to make sure the computer can see your device. I then issue the fastboot command I want: fastboot flash logo and then drag the file from the folder you are in and drop it on the command line. In this case I used, nowarning.bin. When it populated the complete path starting with the c: prompt shows up. Make sure there is a space before the C: and the previous command. Hit enter. I have searched everywhere and have not found an answer to this problem. I did see a video on youtube where the fellow dragged a file from the folder and dropped it in the command prompt window. So thanks to him for that simple yet effective trick.. Hopefully this will work for you if your having the same problem I had...

[ROOT] Coolad Modena 2 / Sky 2 (E502)

Recently, I successfully ported TWRP from Coolpad Note 3 Lite to Modena 2. After testing, everything works fine, on both devices. Since this device has locked bootloader, we need to bypass this by enabling fastmmi mode and factory mode to enable temporary root access and make initial backup and flashing. So, let´s get started.
Remember to read this post carefully. I am not resposible for any damage to your device. If you brick your device while flashing the TWRP you can *almost* always recover it using SP Flash Tool and YGDP Tool
IF YOU ACCIDENTALY BRICK YOUR DEVICE AND YOU WANT TO FLASH IT VIA SPFT, DO NOT FORMAT THE DEVICE IN SPFT!!! If you´ll format partitions in TWRP, that´s fine, but don´t do FORMAT ALL + DOWNLOAD or FIRMWARE UPGRADE! This will brick your device, like mine This tutorial will not (hopefully) brick it, but just in case something goes wrong, now you know what not to do.
Preparing the environment on your computer
Windows
Download ADB and Fastboot from this link
Open it
Install it system-wide
Also, install the drivers
GNU/Linux (Ubuntu / Debian based distros)
Open terminal
Type "sudo apt install adb fastboot libusb-dev" without the quotes (")
Other things, that are required
Since the file size of the recovery exceeds the maximum 8MB of allowed upload size, you can download it from DataFileHost.
Preparing the device
First, you need to remeber that this could render your device unbootable and will void warranty.
Enable developer options
Go to Settings -> About phone
Tap the build number 7 times
Go back
Go to Developer options
Make sure OEM unlocking and USB Debugging is enabled
Enabling factory mode
Open dialer app
Dial *#9527*#
Click on "DM"
You will be prompted to insert RD personnel password. Enter: 54321
Click cancel button
DM button should change colour to RED
Exit the app by clicking home button
Installing and setting up openrp app
Open terminal / command prompt
Type:
Code:
adb start-server
Type:
Code:
adb devices
Now, click on your phone allow debugging and make sure to tick the radiobutton to remember / always trust this computer
Type:
Code:
adb install
Press spacebar after the install word and drag and drop the downloaded openrp.apk file to terminal
Hit enter
After it´s done, type:
Code:
adb shell monkey -p com.yulong.openrp -v 500
Now, the fun part. ROOTING the device
But before that, BACKUP
Now, keep your phone plugged in, and do a normal reboot by pressing and holding the power button and clicking reboot
When it vibrates, press and hold the Volume down key (Vol-)
You will see these lines on the screen:
Code:
=>[Factory mode]
Code:
=>VolumeDown key is pressed
Code:
=>[fastmmi mode]
After that, you´ll see the LED turns green and "Up Down" text on the screen
Now, back to your computer, type in the command prompt
Code:
adb devices
You should see XXXXXXXXXXXXXX device listed (where XXXX... is the serial number)
Type in the command prompt:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery of=/storage/self/primary/stock_recovery.img
and
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot of=/storage/self/primary/stock_bootimg.img
Flashing the TWRP Image
Type in the command prompt:
Code:
adb push (drag and drop the recovery image file here, like you did with the openrp.apk file) /storage/self/primary/
Type:
Code:
adb reboot
Press and hold VolumeDown key (Vol-) to boot to fastmmi mode
Type:
Code:
adb shell dd if=/storage/self/primary/recovery_twrp_e502.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery
Type
Code:
adb reboot
Press and hold the VolumeUp key (Vol+) to boot into recovery. If you see white screen with "Recovery" text in it, congrats. Everything is working. If not, try again.
Flashing the SuperSU package
Download the zip from SuperSU website
Copy the zip over to the device, with TWRP running
In TWRP, click install, click the zip and confirm the installation.
Factory reset is not required, but you should at least wipe the cache
If this post was useful for you, hit the thanks button

RESERVED

Hi i have a problem here. at the part to drag and drop the openrp file. When i have downloaded the file a drag it and drop it after the install word. The problem is that if I want to drop it there it will do nothing, nothing there shows or anything. Please respond.

I guess you can type the path to the installation file instead of dragging.

Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.

helo, can i get help, when i try to install openrp on abd and fastboot, it printed this message "Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]"
can anyone help me on that step, so i can root my e502

TCRakt said:
Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.
Click to expand...
Click to collapse
how to disable the factory mode ?? :crying:

Firefa23 said:
how to disable the factory mode ?? :crying:
Click to expand...
Click to collapse
Hello,
If I recall correctly (I don't have the phone anymore, just touched it once to root it at the time), you basically undo the "Enabling factory mode" step.
I think if you dial the number, you'll be back in the menu where you have the option to disable the factory mode.
Factory mode should be disabled when 'DM' is green.
Good luck

very good

Need Custom rom please
nougat / pie

Hello, could you resend the twrp recovery file for this phone again?. old links not work!.
(sorry for my bad english)

Flash zip files without recovery

How to flash zip files without recoveries like twrp? pls help me

To flash ZIP-files Android device always must get booted into Recovery mode - where it's irrelevant whether Android dvice gets booted into Stock Recovery or Custom Recovery ( like TWRP ) this because Andoid OS must not be running whilst flashing.

jwoegerbauer said:
To flash ZIP-files Android device always must get booted into Recovery mode - where it's irrelevant whether Android dvice gets booted into Stock Recovery or Custom Recovery ( like TWRP ) this because Andoid OS must not be running whilst flashing.
Click to expand...
Click to collapse
I have booted into color os recovery(my phone's recovery) and then I choose install from storage device after that i choose install from phone storage finally i choose my zip file to flash and after loading is said install package failed
Plus: I don't have sd card

Here excerpt of a small Windows command script that shows how most people do it:
Code:
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <FULL-PATH-ON-PC-TO-ROM-ZIP>

jwoegerbauer said:
Here excerpt of a small Windows command script that shows how most people do it:
Code:
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <FULL-PATH-ON-PC-TO-ROM-ZIP>
Click to expand...
Click to collapse
thank. i will tell you if it works soon

jwoegerbauer said:
Here excerpt of a small Windows command script that shows how most people do it:
Code:
adb devices
adb reboot recovery
timeout /t 10 /nobreak >nul
echo In Recovery menu shown on device select "Update from ADB" and apply
echo Press any key when done ...
pause >nul
adb sideload <FULL-PATH-ON-PC-TO-ROM-ZIP>
Click to expand...
Click to collapse
OMG it works thanks you now i can root my phone .

Database Info

welcome