Develop Bugs

[HOWTO] Install Google SDK and ADB drivers in Windows 7

I'm posting this guide because my Galaxy Nexus I9250 I purchased from Google Play would not to recognize in any way, shape or form the official Google drivers provided into Android SDK. Obviously, if you installed any Samsung drivers, you will have to uninstall them. Personally, I always connect the device to my PC and let Windows Update find the best driver. In this way, the basic Windows interface is handled by Microsoft drivers:
{
"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"
}
Google SDK 64bits Setup
This is a quick howto for those who actually want to setup their SDK properly in Windows 7 64bits. I saw a lot of craziness on the Internet so I wanted to share how I set a proper 64bits development environment.
Android SDK: http://developer.android.com/sdk/ (installer_r21-windows.exe)
Java JDK: http://www.oracle.com/technetwork/java/javase/downloads/ (jdk-7u5-windows-x64.exe)
Eclipse Classic: http://www.eclipse.org/downloads/ (eclipse-SDK-4.2-win32-x86_64.zip)
First, download the 64bits software versions, not 32bits. Android SDK is the only 32bits package but it will work fine with 64bits development tools, if you know what you are doing. Obviously, if you are on a 32bits OS download the 32bits software versions. We are discussing a 64bits setup, so let's move on.
Install Java JDK and only if you run a 64bits OS, set a JAVA_HOME variable with value "%ProgramFiles%\Java\jdk1.7.0_05" into Environment Variables (adjust the value with whatever version you downloaded):
Reboot your PC to enable all the settings done above.
Next, install Android SDK. You only need to download Android SDK Tools, Android SDK Platform-tools and Google USB Driver, if you just want to play with the phone. If you plan to develop apps, install also the API of your choice and Eclipse Classic (yes, that is the recommended version by Google devs).
To make available everywhere your platform tools (adb, fastboot, etc.), add your platform-tools directory to Path:
Myself, I installed the SDK in "C:\Program Files (x86)\Android\sdk" directory, so my path looks like:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%ProgramFiles(x86)%\Android\sdk\platform-tools
Technically, you need to add the ";%ProgramFiles(x86)%\Android\sdk\platform-tools" location at the end of your current path.
Reboot your PC to enable all the settings done above.
Now, on with the fun part. There are 2 drivers needed for Google Nexus, the Composite ADB and Bootloader (Android 1.0).
Android Composite ADB Interface Driver
First, enable USB Debugging in your phone:
Plug your USB cable, you will notice in Device Manager the failed driver notice:
Right-click on it and select "Update Driver Software...", then "Browse my computer for driver software". Don't bother browsing to your ADB USB driver location, it will not install the proper driver. Instead, click on "Let me pick from a list of device drivers on my computer" button:
Make sure "Show All Devices" is selected and click on Next button:
With the list of devices displayed, click on Have Disk button:
Browse to your Google Driver location, mines is set in "C:\Program Files (x86)\Android\sdk\extras\google\usb_driver":
Pick the "Android Composite ADB Interface" driver and click on Next button:
You will be asked to accept the driver installation, do it and be done with this part of drivers setup:
Android Bootloader Interface Driver
Make sure USB Debugging is still enabled in your phone. With the USB cable connected, manually boot into Bootloader mode by powering down your phone and restarting it with all 3 buttons pressed (Volume Up + Volume Down + Power). You will notice in Device Manager the new unrecognized Android 1.0 device. Follow the same steps explained above and when you reach the driver selection, choose "Android Bootloader Interface":
To test the setup, run few basic commands:
Code:
adb devices
adb reboot bootloader
fastboot reboot
You are done, enjoy the official USB drivers from Google.

Quick Root Command references
Nexus Images: https://developers.google.com/android/nexus/images#mysid
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
SuperSU: http://download.chainfire.eu/205/SuperSU/
Root Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
Code:
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install, then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
Code:
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
Backup Device
Code:
adb backup -apk -shared -all -f backup.ab

TECK said:
Nexus Images: https://developers.google.com/android/nexus/images
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
Root Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
Code:
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install, then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
Code:
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
Click to expand...
Click to collapse
This is nice I wish this was around 2 weeks earlier when I got this phone this would have made setting up a lot easier. This deserves to be sticky
Sent from my Galaxy Nexus using Tapatalk 2

I added also a quick Howto for the Android SDK setup in Windows 64bits. Lots of crazy info out there on the Internet so I said might as well post it so others can do it right in their computers.

TECK said:
I added also a quick Howto for the Android SDK setup in Windows 64bits. Lots of crazy info out there on the Internet so I said might as well post it so others can do it right in their computers.
Click to expand...
Click to collapse
glad i came across this post. I'm going to use your instructions to return my daughter's GSM Galaxy Nexus to stock JB so we can determine if the proximity sensor is bad or if it's due to the other JB ROMs i've put on her phone. right now, the proximity sensor does not turn the screen off when she places the phone to her ear during phone calls.
question: i prefer not to overwrite the CWM recovery, so i'm planning to remove the recovery.img from the image-yakju-jro03c.zip file before updating via fastboot. next i'll reboot to recovery and flash the superuser zip file to gain ROOT access. my question is this: will removing the recovery img cause the update via fastboot to fail? thanks to anyone who replies to my question.

I would simply flash the entire stock image without skipping any files. Then temporarily flash back the CWM, just to keep the phone stock.
Code:
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
This will not write CWM to the phone, but rather use it once to bypass the stock recovery. Personally, I'm only interested to root the device and will not install custom ROM's. But even if you do install custom ROM's, you rarely need CWM... and if you do, you will work near your computer where you have access to adb.

This is a splendid guide!
Absolutely what all new Androiders need.
Sent from my Transformer TF101 using Tapatalk 2

Did everything you said and got to the point where I was testing those commands, and it says devices attached but my device isnt listed. I was still in boootloader and fastboot usb was attached. is that correct? any ideas? I do have CM9 installed and there are plenty of options regarding root access.

TECK said:
To test the setup, run few basic commands:
Code:
adb devices
adb reboot bootloader
fastboot reboot
Click to expand...
Click to collapse
Mate, when I type "adb devices" I am getting an error saying that "'adb' is not recognized as an internal or external command, operable program or batch file"
I installed Android SDK and Java SE JDK and it all went well. I installed the drivers and when in fastboot mode, I get "Samsung Galaxy Nexus BootLoader Interface" in Device Manager, which I think is what I should be getting.
Would you know what is it that I am missing? Could it be something that I haven't installed from the Android SDK? Thanks again for the tutorial.

You need to change to the directory in which you installed the SDK
So like:
cd <insert directory here and remove the arrow brackets>
Sent from my Galaxy Nexus using Tapatalk 2

geoffcorey said:
You need to change to the directory in which you installed the SDK
So like:
cd <insert directory here and remove the arrow brackets>
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that, thanks.
His screenshot shows that he is not in the SDK installed folder though.
My phone was in fastboot mode when I tried that. I hope that's the correct mode.
One more thing, when I choose go to Recovery in fastboot, the red triangle comes up, but Volume Up + Power doesn't do anything and I have to take out the battery in order to reboot.

bozint said:
I'll try that, thanks.
His screenshot shows that he is not in the SDK installed folder though.
My phone was in fastboot mode when I tried that. I hope that's the correct mode.
Click to expand...
Click to collapse
That is because you missed this part:
TECK said:
[snip]
To make available everywhere your platform tools (adb, fastboot, etc.), add your platform-tools directory to Path:
Myself, I installed the SDK in "C:\Program Files (x86)\Android\sdk" directory, so my path looks like:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%ProgramFiles(x86)%\Android\sdk\platform-tools
Technically, you need to add the ";%ProgramFiles(x86)%\Android\sdk\platform-tools" location at the end of your current path.
Reboot your PC to enable all the settings done above.
Click to expand...
Click to collapse
bozint said:
One more thing, when I choose go to Recovery in fastboot, the red triangle comes up, but Volume Up + Power doesn't do anything and I have to take out the battery in order to reboot.
Click to expand...
Click to collapse
What you are seeing is the main screen for the stock recovery. To access the menu from that screen, hold power and press volume up.

efrant said:
That is because you missed this part
Click to expand...
Click to collapse
I did add a line in the Environment Variables, I installed the Android SDK in the root of "C" though (C:\!Android\.....). It might be the issue, and I will use default path after I uninstall it and then install it again. I also added the Java SE in the Environment Variables.
efrant said:
What you are seeing is the main screen for the stock recovery. To access the menu from that screen, hold power and press volume up.
Click to expand...
Click to collapse
Thanks for this, I got into now. I guess all the time I was holding vol.up and then power.
I am on stock now, so in order to root, should I be following the following procedure?
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
My baseband is XXLF1, and the build is JRO03C.I9250WLH2, if this helps in any way.
Thanks for the comment guys, much appreciated.
====================================================
EDIT: @efrant, I just checked your guide on rooting without unlocking the bootloader, so should I fail with the backup you also referenced in you guide, I will give it a try. The phone is rather new though, so even if I lose some apps it's not that big a deal.

bozint said:
[snip]
I am on stock now, so in order to root, should I be following the following procedure?
Click to expand...
Click to collapse
I think you are confusing a few things. Unlocking the bootloader is not the same as getting root. You should have a look at the "basics" link in my signature.

bozint said:
I did add a line in the Environment Variables, I installed the Android SDK in the root of "C" though (C:\!Android\.....).
Click to expand...
Click to collapse
So the path was not the issue. Originally I had this in Path in the Environment Variables: "....;%!Android%\Google_Dev\android-sdk\platform-tools" and adb did not work unless I went directly inside the platform-tools folder in command prompt.
I then tried to add additional line in Environment Variables for the whole path, without the % symbol (C:\!Android\Google_Dev\android-sdk\platform-tools). And it worked, now adb lists the device at any time and location.
The final line in Path looks like this: ....bunch of lines......;%!Android%\Google_Dev\android-sdk\platform-tools;C:\!Android\Google_Dev\android-sdk\platform-tools

bozint said:
Mate, when I type "adb devices" I am getting an error saying that "'adb' is not recognized as an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
If you add adb to the Windows path, you will not get this error. I explained into tutorial what to do.
Edit: Never mind, efrant explained well what to do.

efrant said:
I think you are confusing a few things. Unlocking the bootloader is not the same as getting root. You should have a look at the "basics" link in my signature.
Click to expand...
Click to collapse
I got it rooted now, but I need to do some additional reading yes. I'll read the guide and hopefully things will be more clear. Thanks guys.

bozint said:
I am on stock now, so in order to root, should I be following the following procedure?
Click to expand...
Click to collapse
No. The tutorial has separate sections, Root Device" and "Stock Device", not "Rooted Device". You want to root, so you follow the "Root" procedure, right?

Does anyone have a separate link to the ADB drivers for windows? I need this pc to recognize my N7 in bootloader etc but I don't want to go through the whole Java SDK etc hassle to get ADB just to get the drivers, it's not my pc.
Thanks

Logic_ said:
Does anyone have a separate link to the ADB drivers for windows? I need this pc to recognize my N7 in bootloader etc but I don't want to go through the whole Java SDK etc hassle to get ADB just to get the drivers, it's not my pc.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1379875

[Q] Stuck at stock bootloader

I am such a noob and suck at rooting.I got problem during rooting my kindle fire,here's the stories.I try to search all the way in the forum. But,all of it not working. Could you guys help me ?
1) follow root instruction and downloaded KFU
2) successfully installed superuser and go launcher
3) TWRP or CWR or FFF doesn't appear when i reboot back my device to flash custom rom.
4) I tried to run install_driver and run it again and select bootmode menu
5) I choose 3 for recovery.and its brick.luckily i could switch off my kindle.but when i wanna turned it on,its doesnt return to home menu.its stuck at the stock bootloader.
I'm hoping you guys could help me and suggest me the way how to solve it.
I also attach some screen shot of the kindle and my notebooks when i plugged in usb cable in.
Cheers.
{
"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"
}

it seems to be in fastboot mode - you have to fix your windows driver for fastboot mode, then you can continue with kfu.
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
detailed explanation here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

b63 said:
it seems to be in fastboot mode - you have to fix your windows driver for fastboot mode, then you can continue with kfu.
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
detailed explanation here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
thanks for the advice.I will try it after this and inform you back. Btw, do i need kindle usb cable? for fastboot, since i purchased used kindle so the seller didnt gimme those cable. im currently using sony micro usb cable.

no - every micro usb cable will work

b63 said:
no - every micro usb cable will work
Click to expand...
Click to collapse
i will try to read all of it, try to understand it.and get you know once i already figure it out okay?:cyclops:

i already update my driver.and why in KFU,my device is offline.

21th century apes said:
i already update my driver.and why in KFU,my device is offline.
Click to expand...
Click to collapse
your device seems to be in fastboot mode - you have selected the wrong driver.
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
if the device is in fastboot mode "adb status" is allways "offline".
if you have installed the right driver you can check manually
with "fastboot devices" and "fastboot getvar product".
if you get response to this commands you are good to go.

i finally able to install bootloader and twrp.i thought i never make a mistakes.but unfortunately,during time im backing up stock rom,(nandbackup).i check all the boxes (for the left side) and for right side nothing.its running,when completed.its show huge amount of data (around 780 mb).i really think dat tis is normal for backup.in twrp,and video by tom gt,time for backup for 10 minutes.but me,already 5 hour still stuck in twrp.cant go anywhere.

b63 said:
your device seems to be in fastboot mode - you have selected the wrong driver.
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
if the device is in fastboot mode "adb status" is allways "offline".
if you have installed the right driver you can check manually
with "fastboot devices" and "fastboot getvar product".
if you get response to this commands you are good to go.
Click to expand...
Click to collapse
bro i hope you can help me solve tiz things off.during backup nand.for the first time.its stuck and as i mention previously its stuck 5 hours but for almost 2 days.its still not finish.am i brick my fire?am i miss out something?later i'll attach picture for your preferences.i think when i already booted up kindle fire,its consider no such big issues.maybe for me that not familiar.

21th century apes said:
bro i hope you can help me solve tiz things off.during backup nand.for the first time.its stuck and as i mention previously its stuck 5 hours but for almost 2 days.its still not finish.am i brick my fire?am i miss out something?later i'll attach picture for your preferences.i think when i already booted up kindle fire,its consider no such big issues.maybe for me that not familiar.
Click to expand...
Click to collapse
if you managed to install bootloader and twrp then you are good to go.
you tried to make a backup of the stock firmware and now the twrp is stuck.
i don't know what options you checked, but this should be no problem.
just hold the power button for ~20sec till it turns off and try again.
check only options which exist on your device then the backup should be done in ~10min.

b63 said:
if you managed to install bootloader and twrp then you are good to go.
you tried to make a backup of the stock firmware and now the twrp is stuck.
i don't know what options you checked, but this should be no problem.
just hold the power button for ~20sec till it turns off and try again.
check only options which exist on your device then the backup should be done in ~10min.
Click to expand...
Click to collapse
Thank you dude.Finally im able to use custom rom.oh,yeah .Btw,i got one last question.Why i cant connect my kindle with computer.instead its show my kindle,its only charging.coz i need to backup all my stuff inside my kindle to computer.

21th century apes said:
Thank you dude.Finally im able to use custom rom.oh,yeah .Btw,i got one last question.Why i cant connect my kindle with computer.instead its show my kindle,its only charging.coz i need to backup all my stuff inside my kindle to computer.
Click to expand...
Click to collapse
that depends on the rom you used. some have a option to enable this function.
the best advise would be to search or ask in the section of the rom you used.
great that it's working now - much fun with your kf

hey dude.im already killed my kindle fire and now its dead.here the stories :
i try to backup all my stuff to my computer.as what you told me before,i try to follow.pick ROM that have usb debugging option for transfering data.okay done.but when i transferring my data from kindle to pc.(i dunno what happen) accidentally my kindle fire hang and i disconnect all the cable hoping that my kindle fire will be okay.but thats the end of my kindle fire.its failed to boot.just plain black screen.when i plugged in the cable.led light blinking.like normal.red and yellow.but there's nothing i can do.i open up device manager on my pc,instead of android phone appeared during time im connecting my phone with pc,its appeared usb mass storage (code 10).device cant start and load.hope you could guide me.anybody.
all guide will be kindly appreaciated.thanks.

ADB can't recognize my Asus Zenfone 2 phone - Please Help!

Sorry, I have checked with many forums, but couldn't find any solution to this problem...
I shall present a detailed step-by-step recollection of events...
1.) I am running Windows 7 (64-bit) on my PC.
2.) I have recently bought an Asus Zenfone 2 (ZE551ML) on 05-July-2015.
Specs: 2.3 GHz, 4 GB RAM, 64 GB in-built memory, Android 5.0 Lollipop.
OEM Firmware no. that the phone came with is: <WW 2.15.40.13_20150506>
3.) The first thing I did upon receiving the phone is to set a password and encrypt the phone (encryption took only 30 seconds or so).
At that time, my phone did NOT have any SIM card or External SD Card.
Phone was also NOT rooted.
4.) Enabled USB Debugging on my Zenfone 2 (in MTP mode).
5.) Downloaded latest updated Firmware from Asus Support Centre: <WW V2.19.40.22> dated 03-07-2015
The firmware is in ZIP format and is stored on my PC's harddrive.
6.) Downloaded "ASUS Android USB Drivers for Windows" v2.0 dated 05-03-2015
7.) Downloaded "Intel USB Driver for Android Devices" v1.9.0 dated 29-Apr-2015
8.) Downloaded latest ADB FastBoot Drivers v1.4.2
9.) Installed the Intel USB Driver (from step-7 above).
10.) Restarted PC.
11.) Went to Windows Device Manager, updated driver from ASUS Android USB drivers (from step-6 above), even though Intel's drivers are more recent.
After installing Asus's own drivers, my Device Manager looks like this (see image):
{
"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"
}
12.) Restarted PC.
13.) At this time, Zenfone 2 is connected to Windows via both MTP (Media Files) and PTP (Camera files) modes.
14.) Installed ADB drivers into System-wide Mode (C:\adb) in Windows.
15.) Turned-off the phone and restarted phone in Recovery Mode.
16.) Connected the phone to Windows PC by OEM cable.
17.) On phone's recovery menu, selected "apply update from ADB".
18.) Opened Windows Command Prompt in the ADB folder (C:\adb),
and typed: "adb devices".
19.) This is where I am stuck. The CMD screen looks like this (see image)
20.) After reading some forums, I have switched to PTP Mode in phone's Settings->Storage USB Settings.
But the problem persists. I cannot get ADB running in Windows to detect to my Android phone even after connecting to it.
Can anyone tell what have I missed? If someone knows the solution, please please help me.

Simple straightforward way to update firmware on Asus Zenfone 2 without ADB
GOD SAVE ME!!!
Barely minutes after I had given up on the ADB thing, I have found a way to install firmwares on my Asus Zenfone 2 phone.
Note: The main problem I have outlined in this thread is to be able to install Updated OEM Firmware from ASUS. This is not OTA upgrade, but FULL firmware update.
I shall share my experience on this subject in a step-by-step way:
1.) First, make sure that you can transfer files from your Android phone to Windows via USB cable (install the necessary drivers – see my post above.)
2.) You must also have downloaded the latest firmware in ZIP format from ASUS support page (for links, please refer to my above post).
Rest of the stuff I am paraphrasing from ASUS Support section:
3.) Connect your phone with PC via micro USB cable, and copy the entire ZIP file (firmware) to the root directory of internal storage of phone (see pic below).
4.) After copying is complete, detach the USB cable from the phone.
5.) The notification for firmware update will pop-up on status bar (top-left corner, see pic below):
6.) Pull down the notification bar, and tap "System Update File Detected..." (see pic below).
Follow steps to update firmware.
- Phone may restart several times during update,
- Phone must have min. 15% charge, or best, connect phone to power source while update is on.
7.) After update, I have noticed that:
- Phone encryption is intact and is just like what it was before update,
- But screen UI settings have been completely reset,
- I can't comment on Phonebook / Contacts, because my phone still does NOT have a SIM card.
- My phone is still NOT rooted.
8.) Do remember to delete the original Firmware ZIP file on the root directory of your phone. The file size is huge and the phone does NOT delete it automatically. Besides, once updated, there is no need for the ZIP file, I think.
So this is a simple (and the official) way to update firmware on an Asus Zenfone 2 without any need for Rooting / ADB and other hacks.
No need to install ADB, no need to Root the phone!
Easy!

But despite the above solution, the fact still remains that the "15 seconds ADB Installer v1.4.2" does not work with Asus Zenfone 2 (as least that is my experience so far).
I am looking for another ADB installer in which, hopefully, my phone will be detected by ADB so that I can root/flash stuff.

xbox-er said:
GOD SAVE ME!!!
Barely minutes after I had given up on the ADB thing, I have found a way to install firmwares on my Asus Zenfone 2 phone.
Note: The main problem I have outlined in this thread is to be able to install Updated OEM Firmware from ASUS. This is not OTA upgrade, but FULL firmware update.
I shall share my experience on this subject in a step-by-step way:
So this is a simple (and the official) way to update firmware on an Asus Zenfone 2 without any need for Rooting / ADB and other hacks.
No need to install ADB, no need to Root the phone!
Easy!
Click to expand...
Click to collapse
xbox-er said:
But despite the above solution, the fact still remains that the "15 seconds ADB Installer v1.4.2" does not work with Asus Zenfone 2 (as least that is my experience so far).
I am looking for another ADB installer in which, hopefully, my phone will be detected by ADB so that I can root/flash stuff.
Click to expand...
Click to collapse
Seriously this method was there since ages... Nothing new.. And how is it possible that the tool which worked for every android user didnt work for u i didnt even install "ASUS Android USB Drivers for Windows" on my PC just installed "Intel USB Driver for Android Devices" and "15 sec adb installer" and eveything works fine from adb to MTP/PTP... Forget doing "adb devices" command just try this simple command "adb reboot bootloader" ... You will see your phone reboot into bootloader/fastboot mode...if this works it means you have a working adb.... And if you were trying to sideload a file via adb you just had to enter adb sideload "filename" and press enter...Thats it!! no adb devices and all

mhp1995 said:
Forget doing "adb devices" command just try this simple command "adb reboot bootloader" ... You will see your phone reboot into bootloader/fastboot mode...if this works it means you have a working adb.... And if you were trying to sideload a file via adb you just had to enter adb sideload "filename" and press enter...Thats it!! no adb devices and all
Click to expand...
Click to collapse
adb devices is an easy way to detect if adb can see any devices.
If adb devices returns nothing, then no matter what adb commands you enter, nothing will work. You're basically telling him to enter commands while nothing is detected. They'll have no impact.

Harfainx said:
adb devices is an easy way to detect if adb can see any devices.
If adb devices returns nothing, then no matter what adb commands you enter, nothing will work. You're basically telling him to enter commands while nothing is detected. They'll have no impact.
Click to expand...
Click to collapse
I know but sometimes when i also enter adb devices i also dont get anything... But then if i enter adb reboot recovery etc or just sideload the zip file it works...Maybe he has the same problem...

I had this problem this morning, tried three different micro USB cables and the third one worked. The first two would charge but not let the device get detected by ADB.

I have similar issue..adb recognizes my phone...but i can't flash .img onto the phone..when i type fastboot devices my phone doesnot come out next....what can i do?
Sent from my ASUS_Z00AD using Tapatalk

Try this
http://forum.xda-developers.com/showthread.php?p=61528830
OTA links for stock ROM
yemnic said:
I have similar issue..adb recognizes my phone...but i can't flash .img onto the phone..when i type fastboot devices my phone doesnot come out next....what can i do?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
If you're in adb the code is
adb sideload
Not
fastboot sideload
Sent from my ASUS_Z00AD using XDA Free mobile app

Nope..am trying to flash my recovery SKU to WW...cos mine is CN,
Sent from my ASUS_Z00AD using Tapatalk

My zenfon 2 works with adb when its open in android. But it is not recognized in recovery. If i do adb reboot recovery, it works. But when i try adb sideload filename.zip from recovery, it says: device not found!

ione2380 said:
My zenfon 2 works with adb when its open in android. But it is not recognized in recovery. If i do adb reboot recovery, it works. But when i try adb sideload filename.zip from recovery, it says: device not found!
Click to expand...
Click to collapse
did you first select " apply updates from adb " on your phone before " adb sideload filename.zip " from PC command prompt
select " apply updates from adb " on your phone first, then the phone say's give the zip file from your pc command prompt using " adb sideload filename.zip ".... at the time only the sideload code work.

Yes, i did that, of course.

ione2380 said:
Yes, i did that, of course.
Click to expand...
Click to collapse
Nothing new here? i have the very same problem..

I think i found the final soloution.
Download the newest ADB Tool here: http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
(its an old one mentioned in the guide on XDA how to flash Zenfone2)
Also - use the latest Intel (IntelAndroidDrvSetup1.10.0) driver found here: https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Then try again. If you search for devices in ABD (by typing "abd devices") it might still not show your phone, but all the commands will work and you will be able to flash your phone in recovery mode.

Have you found a solution for this? I'm experiencing the same thing on my zenfone 2 (z00ad) on 2.20.40.139. I've tried 4 usb cables and 2 pc's one 64bit win7 and one 32bit win7. Both setup the same way with latest drivers/adb/fastboot and adb system wide installed. This isn't my first android, but it is the first android to leave me stumped with no fastboot/adb access. Also tried with mtp selected, then ptp selected, then none selected. Still the same "Fastboot devices <waiting for devices>" developer mode is enabled with usb debugging enabled

Hi everyone,
Installing only Intel USB Driver won't solve the problem. You should update the driver manually.
Plug in the device in state where you will update the driver from (like on Recovery mode). Open Device Manager, right click on the only driver with exclamation mark and select 'Update Driver Software...'. A new window will appear. Select 'Browse my computer for driver software', and then select 'Let me pick from a list of device drivers on my computer'. Select ADB drivers and then any driver with ASUS ADB name.
The driver will be installed. You can verify if the driver is installed or not by typing adb devices on a Command Prompt window.
Sent from my ASUS_Z00AD

krasCGQ said:
Hi everyone,
Installing only Intel USB Driver won't solve the problem. You should update the driver manually.
Plug in the device in state where you will update the driver from (like on Recovery mode). Open Device Manager, right click on the only driver with exclamation mark and select 'Update Driver Software...'. A new window will appear. Select 'Browse my computer for driver software', and then select 'Let me pick from a list of device drivers on my computer'. Select ADB drivers and then any driver with ASUS ADB name.
The driver will be installed. You can verify if the driver is installed or not by typing adb devices on a Command Prompt window.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
:good::good: WOOOOOOOOORKKKKSSSSS thanks bro, work fine, just update and enjoy ! adb sideload FILENAME.zip enjoy thanks bro!

3.) Connect your phone with PC via micro USB cable, and copy the entire ZIP file (firmware) to the root directory of internal storage of phone (see pic below).
View attachment 3392841
4.) After copying is complete, detach the USB cable from the phone.
5.) The notification for firmware update will pop-up on status bar (top-left corner, see pic below):
View attachment 3392842
6.) Pull down the notification bar, and tap "System Update File Detected..." (see pic below).
Follow steps to update firmware.
- Phone may restart several times during update,
- Phone must have min. 15% charge, or best, connect phone to power source while update is on.
View attachment 3392843
7.) After update, I have noticed that:
- Phone encryption is intact and is just like what it was before update,
- But screen UI settings have been completely reset,
- I can't comment on Phonebook / Contacts, because my phone still does NOT have a SIM card.
- My phone is still NOT rooted.
8.) Do remember to delete the original Firmware ZIP file on the root directory of your phone. The file size is huge and the phone does NOT delete it automatically. Besides, once updated, there is no need for the ZIP file, I think.
So this is a simple (and the official) way to update firmware on an Asus Zenfone 2 without any need for Rooting / ADB and other hacks.
No need to install ADB, no need to Root the phone!
Easy![/QUOTE]
Do you think can work if i want to substitute de cn firmware with ww firmware?

juanpirata said:
:good::good: WOOOOOOOOORKKKKSSSSS thanks bro, work fine, just update and enjoy ! adb sideload FILENAME.zip enjoy thanks bro!
Click to expand...
Click to collapse
Please can you tell me exactly what you did step by step and can you include download links please

Huawei Watch Update 1.4 is here!

Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you are connected to your charging dock.
Make sure you are running the latest update LCB43B.
I did all this on Win 10.
1. Just be fully stock including recovery. Refer to Skin1980's guide here to return to stock if you used his previous kernel or did any other mods like TWRP or root. (http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596)
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339) (People have reported PDANET drivers are working if the naked drivers do not work for them and are somewhat easier to install.)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip and make sure its located inside the root directory of your adb installation.
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Don't forget to hit the thanks button! I appreciate it!

Thank you. Can you please create a step by step guide for idiots like me, who have never used adb etc..?

hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there

chachin said:
hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there
Click to expand...
Click to collapse
I updated OP check the steps again. adb commands won't work in bootloader. Once in recovery swipe down and select apply update from adb then issue the "adb sideload update.zip" command.

so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
Make sure the update file is inside your root adb directory on your hard drive.

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
It looks like your device is still not visible to adb. Make sure you don't have any other devices connected like a phone with debugging turned on also. And you do need to be in recovery with it awaiting the sideload update.zip command. You seemed to be in the correct place.

Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk

xceebeex said:
Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
YAY! Always the best way to go. Where are u located?

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
But... the phone must be connected on the pc? I can't detect the watch with adb devices..

I was wondering why I couldn't boot to the recovery directly so thanks a ton for the help! Also dayum, the speaker sure is quite loud for a smartwatch!
To the person above no, you do not need to have the phone to your pc connected for it to work.

got it installed like it so far, to me the speaker sounds alot better then the one in the gear s

{
"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"
}
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk

Tried installing the naked drivers in the link but that fails, any suggestions?

str8spir said:
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Very glad we could help! Just wanted everyone to be as happy as I was when I saw the file drop!

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
Thanks worked flawlessly...

ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
Let me test mine and see if it is visible while waiting on the adb sideload update.zip command

No luck for me installing these drivers

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
C:\ADB>adb devices
List of devices attached
MQB7N15914000616 sideload
This is what I see while in sideload mode inside recovery. Not sure why its not working for you.:crying:

How to root Your MICROMAX IN1B (64GB)

First of all, before i start, I'll make this clear, i have done this procedure and rooted my IN1B successfully BUT if anything goes wrong with your device,
I WILL NOT BE RESPONSIBLE FOR BRICKED DEVICES
PreRequisites (Stuff you will need)
So, Let's get into it.
Before Begining, Here are the things you'll need :-
1. A windows PC with all the necessary drivers.
2. ADB and fastboot which you can get from here.
3. A USB C cable, preferably the original one.
4. Make sure your Device is atleast 60% charged.
5. Backup all your data because the very first step will reset your phone.
NOTE- MICROMAX DOES NOT PROVIDE ANY USB DRIVERS. So i had trouble finding the Drivers too, so i recomend you use "Driver booster" it's free, you can get it from here. After installing the driver booster, let it scan and then update all the drivers related to "Android" and "ADB".
That's it, once you are done with all the above points we are good to start.
These are the PATCHED files you need to flash to root your device.
1. Get the files from Here
After you download the files, copy and paste the files in the folder where ADB & Fastboot is located, if you have not changed the Install location, it should be at this directory- C:\Program Files (x86)\Minimal ADB and Fastboot
After you paste all the 3 downloaded files in the ADB folder, the process will now start.
Unlocking the BootLoader
The first step is to unlock the boot loader.
1. Connect your device with a USB C cable.
2. Enable USB debugging from the developer options-
{
"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"
}
3. Now run ADB and run this command- adb devices As you run this, something like this should appear on your mobile-
4. Now allow it and Voila!, you are now connected!
5. Now find "OEM Unlocking" and enable it.
6. Now enter this command- adb reboot bootloader As you run this command your device will reboot and show a black screen with only "fastboot" written on it.
7. Now finally Enter this command- fastboot flashing unlock
8. Now it will ask you to confirm, if you change your mind and dont want to root now, press the "Volume-Down" Button or if you want to root, press the "Volume-Up" button.
NOTE- UNLOCK MAY VOID SOFTARE WARRANTY. FOR DETAILS, CHECK THIS (Read 6e)
9. Awesome! Now you have unlocked your boot loader!!
Flashing the Patched Files
Now remember you need the 3 files i linked above, once you get them, paste them in the ADB folder.
Make sure you DON't change the file names.
Let's Start!
1. Run this command- fastboot flash boot patched_boot.img
2. After that, Run this- fastboot --disable-verification flash vbmeta vbmeta.img
3 And he final command, run this- fastboot flash recovery recovery.img
After all these 3 complete succesfully, Just run- fastboot reboot This will start your device normally, go on and set up your device.
1.As you complete the setup, you should see the magisk app-
2. Now the magisk app will ask you to install the full version, click on confirm and it will install the magisk app, you will have to turn on the "Unknown sources" option.
3. Once it is installed, you can ENJOY YOUR ROOTED IN 1B!!
IF YOU NEED ANY HELP, FEEL FREE TO WRITE IT BELOW, OR DM ME ON TELEGRAM- Âkio or DISCORD- Âkio#7134

Akahat27 said:
First of all, before i start, I'll make this clear, i have done this procedure and rooted my IN1B successfully BUT if anything goes wrong with your device,
I WILL NOT BE RESPONSIBLE FOR BRICKED DEVICES
PreRequisites (Stuff you will need)
So, Let's get into it.
Before Begining, Here are the things you'll need :-
1. A windows PC with all the necessary drivers.
2. ADB and fastboot which you can get from here.
3. A USB C cable, preferably the original one.
4. Make sure your Device is atleast 60% charged.
5. Backup all your data because the very first step will reset your phone.
NOTE- MICROMAX DOES NOT PROVIDE ANY USB DRIVERS. So i had trouble finding the Drivers too, so i recomend you use "Driver booster" it's free, you can get it from here. After installing the driver booster, let it scan and then update all the drivers related to "Android" and "ADB".
That's it, once you are done with all the above points we are good to start.
These are the PATCHED files you need to flash to root your device.
1. Get the files from Here
After you download the files, copy and paste the files in the folder where ADB & Fastboot is located, if you have not changed the Install location, it should be at this directory- C:\Program Files (x86)\Minimal ADB and Fastboot
After you paste all the 3 downloaded files in the ADB folder, the process will now start.
Unlocking the BootLoader
The first step is to unlock the boot loader.
1. Connect your device with a USB C cable.
2. Enable USB debugging from the developer options-
View attachment 5326971
3. Now run ADB and run this command- adb devices As you run this, something like this should appear on your mobile-
View attachment 5326979
4. Now allow it and Voila!, you are now connected!
5. Now find "OEM Unlocking" and enable it.
View attachment 5326983
6. Now enter this command- adb reboot bootloader As you run this command your device will reboot and show a black screen with only "fastboot" written on it.
7. Now finally Enter this command- fastboot flashing unlock
8. Now it will ask you to confirm, if you change your mind and dont want to root now, press the "Volume-Down" Button or if you want to root, press the "Volume-Up" button.
NOTE- UNLOCK MAY VOID SOFTARE WARRANTY. FOR DETAILS, CHECK THIS (Read 6e)
9. Awesome! Now you have unlocked your boot loader!!
Flashing the Patched Files
Now remember you need the 3 files i linked above, once you get them, paste them in the ADB folder.
Make sure you DON't change the file names.
Let's Start!
1. Run this command- fastboot flash boot patched_boot.img
2. After that, Run this- fastboot --disable-verification flash vbmeta vbmeta.img
3 And he final command, run this- fastboot flash recovery recovery.img
After all these 3 complete succesfully, Just run- fastboot reboot This will start your device normally, go on and set up your device.
1.As you complete the setup, you should see the magisk app-
View attachment 5326989
2. Now the magisk app will ask you to install the full version, click on confirm and it will install the magisk app, you will have to turn on the "Unknown sources" option.
3. Once it is installed, you can ENJOY YOUR ROOTED IN 1B!!
IF YOU NEED ANY HELP, FEEL FREE TO WRITE IT BELOW, OR DM ME ON TELEGRAM- Âkio or DISCORD- Âkio#7134
Click to expand...
Click to collapse
ON which android version u have done this given me firmware name

pankspoo said:
ON which android version u have done this given me firmware name
Click to expand...
Click to collapse
I did on the android 10 which it initially came with..