Related
Here We have the Root And CWM for Nexus 7 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 7 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 7 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 7.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-grouper.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
fastboot flash recovery recovery-clockwork-touch-6.0.2.3-grouper.img
Click to expand...
Click to collapse
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 7 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 4
Root and CWM for Nexus 10
Reserved...
udimars30 said:
Reserved...
Click to expand...
Click to collapse
Thank you a lot...but the link for the fastboot its not aviable
Nano23 said:
Thank you a lot...but the link for the fastboot its not aviable
Click to expand...
Click to collapse
link updated
and this belongs in original development how? why not post a thread in original development asking about need for speed too..
Step 4 and step 7
I am a little confused about step 4 as I didn't think any nexus 7's had a SD card slot. I purchased mine right from google. I just put the zip file directly on the device itself and I know from my experience with my old Nexus One that this works too, just wondering who is selling the one with SD card slots. My second question, and really the more important one is step 7. I have tried to make the device go into fastboot several times and when I hold the volume keys down, the device boots to a black screen with no ability to do anything after that. If I mess with the power button (meaning I hold it in for a long time then let it out, and do this several times) I can get the device to preform a normal boot. Any thoughts?
thanks
Thanks its worked for my nexus 7..
udimars30 said:
Here We have the Root And CWM for Nexus 7 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 7 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 7 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 7.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-grouper.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 7 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 4
Root and CWM for Nexus 10
Click to expand...
Click to collapse
Thanks a million man! I was having all kinds of trouble updating to 4.2.2 and finally figured that out. Then I was having problems rooting again until I found this. Your method worked great but I used TWRP instead and it still did the trick. Thanks again.
I tried this but when I want to flash the recovery, my fastboot.exe will then not respond and will try to close. What gives?
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Click to expand...
Click to collapse
Just a quick note here, to enter Fastboot Mode you just need to turn the Nexus 7 off, then turn on again, soon as you see the Google logo press the Volume Down key and hold (Hold both Power button and Volume Down Key).
No need for holding the power button, the vol down button does the whole trick
worked for me. thanks very much
sicameron32 said:
I am a little confused about step 4 as I didn't think any nexus 7's had a SD card slot. I purchased mine right from google. I just put the zip file directly on the device itself and I know from my experience with my old Nexus One that this works too, just wondering who is selling the one with SD card slots. My second question, and really the more important one is step 7. I have tried to make the device go into fastboot several times and when I hold the volume keys down, the device boots to a black screen with no ability to do anything after that. If I mess with the power button (meaning I hold it in for a long time then let it out, and do this several times) I can get the device to preform a normal boot. Any thoughts?
Click to expand...
Click to collapse
yes you can do that for the normal boot
Spenzert said:
Just a quick note here, to enter Fastboot Mode you just need to turn the Nexus 7 off, then turn on again, soon as you see the Google logo press the Volume Down key and hold (Hold both Power button and Volume Down Key).
Click to expand...
Click to collapse
Thanks..
I don't have N7 that's why did not know!
Leonhan said:
I tried this but when I want to flash the recovery, my fastboot.exe will then not respond and will try to close. What gives?
Click to expand...
Click to collapse
re-install the fastboot with all it's extensions in the same folder!
If you want to use fastboot by a easy way, use this guide you don't need adb line command, just fastboot line command and it's an child game by this way
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "Fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
If you want to flash a boot.img:
Code:
c:\fastboot>fastboot flash boot boot.img
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
don´t i have to unlock bootloader first ?
Domx92 said:
don´t i have to unlock bootloader first ?
Click to expand...
Click to collapse
Yes, it is a prerequisite if you want to root your android device.
Ok, so I am running the 4.2.2 update, and after jumping through numerous hoops trying to have my device recognized by adb, I just want to make sure that my very first step should be to boot up in fastboot mode and then issue the following command...
"fastboot oem unlock"
???
Then I can go ahead and proceed to flashing the CWM recovery and flashing the SuperSU file...?
Sent from my SCH-I535 using Tapatalk 2
EDIT: I've tried multiple times, but everytime I boot into "fastboot" mode, which I guess is another way for saying the bootloader, ADB loses its connection with my Nexus 7! Also, if it helps anyone to know, I'm running Win7 64-bit.....I'm not sure if that matters, but the first time I booted up into fastboot mode, my computer recognized it and installed it as an "Android Bootloader Interface" in the Device Manager! When the device boots up normally, ADB does recognize it again, and it also shows up differently in the Device Manager (Android Composite ADB Interface)! ANY help or suggestions would be greatly appreciated, as I obviously can't issue commands to a device that ADB can't see when it's in fastboot mode!
vmancini3 said:
Ok, so I am running the 4.2.2 update, and after jumping through numerous hoops trying to have my device recognized by adb, I just want to make sure that my very first step should be to boot up in fastboot mode and then issue the following command...
"fastboot oem unlock"
???
Then I can go ahead and proceed to flashing the CWM recovery and flashing the SuperSU file...?
Sent from my SCH-I535 using Tapatalk 2
EDIT: I've tried multiple times, but everytime I boot into "fastboot" mode, which I guess is another way for saying the bootloader, ADB loses its connection with my Nexus 7! Also, if it helps anyone to know, I'm running Win7 64-bit.....I'm not sure if that matters, but the first time I booted up into fastboot mode, my computer recognized it and installed it as an "Android Bootloader Interface" in the Device Manager! When the device boots up normally, ADB does recognize it again, and it also shows up differently in the Device Manager (Android Composite ADB Interface)! ANY help or suggestions would be greatly appreciated, as I obviously can't issue commands to a device that ADB can't see when it's in fastboot mode!
Click to expand...
Click to collapse
Hi, vmancini3...
Forget about ADB when your tablet is in FASTBOOT/BOOTLOADER mode...
Here are the salient commands....
Code:
fastboot devices
- should return a serial number to confirm your FASTBOOT connection -
Code:
fastboot oem unlock
- will unlock the BOOTLOADER and will WIPE and FACTORY RESET THE DEVICE; unfortunate, but necessary .
--------------------
With the BOOTLOADER unlocked, begin to set up your Nexus 7 again... as though it was a brand new, just purchased tablet... ie., country, regionalization, WiFi key... etc.
Go online with your Nexus 7 browser (Chrome), and download Chainfire's SU Updater .ZIP package from here...
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Upon completion of this download, shut down the tablet.
--------------------
Reboot again into FASTBOOT/BOOTLOADER mode... VOL down button + POWER ON button.
From your PC, run this command...
Code:
fastboot flash recovery recovery.img
....where the recovery.img is your CWM or TWRP .img file.
Both of which are available here...
CWM - http://www.clockworkmod.com/rommanager
TWRP - http://www.teamw.in/project/twrp2/103
--------------------
Congratulations.... you've just FLASHED a CUSTOM RECOVERY!!!
--------------------
When the self-congratulatory round of self applause has died down, ... and with the Nexus 7 still in FASTBOOT/ BOOTLOADER MODE, use the VOL buttons to navigate and the POWER button to select... reboot into RECOVERY.
Using the new CUSTOM RECOVERY, flash Chainfires SU updater package that you downloaded earlier... usually found in the /download folder...
Done.
Reboot.
Rooted.
--------------------
I really don't understand why some people seem to have a problem with this procedure... it takes less time doing it, than actually describing how to do it.
Rgrds,
Ged.
This is Nvidia's own instruictions which I just followed works great! For new members please be aware that you may have to edit a command given in the instructions below which I will point out (depends on what OTA you have downloaded) for example
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb Highlighted in red is the name you may have to change within the extracted ota, Just look in the extracted file and locate the .dtb now just copy and paste the name of your .dtb and change the fastboot command --> example--> fastboot flash dtb tegra144-tn8-p1761-1270-a04-xda-battery.dtb
Please Read Carefully!
Follow here to get OTA
http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116
What you must have
You need a unlocked boot loader instructions further below.
Also in cmw recovery, please wipe all partions! and reboot in to fastboot mode whilst still in recovery!
SHIELD RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
or you can just download this little .exe Minimal ADB and Fastboot this is what I used.please extract your recovery.zip into where you have installed Minimal ADB and Fastboot example c:\program files x86\Minimal ADB and fastboot.
https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
Before flashing this recovery image to your SHIELD, connect your SHIELD
via USB to the PC where you downloaded this recovery image example same as above c:\program files x86\Minimal ADB and fastboot.
Next, put your SHIELD into fastboot mode using one of the following methods:
SW method 1:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method 2 :
- Turn off the device
- Press and hold "Back"+"Home"+"SHIELD" buttons till device boots
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb <---------------------------------------------------------------------
Now restart your device
now wait a min or two and you have just returned to stock!
Unlocking the Bootloader
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the Home button on the device to highlight "Unlock".
- Press the Shield button to confirm the unlock. Your device's bootloader is now unlocked.
Also worth noting that on Linux, you can install the "android-tools" package that gives you ADB and Fastboot anywhere.
For example, on fedora 20, run:
$ sudo yum install android-tools
Make sure you run fastboot with su- privileges (not doing this caused me no end of frustration before finding out why my device wasn't detected).
MRobbo80 said:
This is Nvidia's own instruictions which I just followed works great! For new members please be aware that you may have to edit a command given in the instructions below which I will point out (depends on what OTA you have downloaded).
Unlocking the Bootloader
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the Home button on the device to highlight "Unlock".
- Press the Shield button to confirm the unlock. Your device's bootloader is now unlocked.
Click to expand...
Click to collapse
Umm having a little trouble unlocking. Am I to understand that you unlock with the device turned on ? because otherwise there isn't a home button...and where is the shield button ? I only have power and volume
buttons. This looks like the unlock method for the Shield not the Shield Tablet.
Sent from my Shield Tab
Wulfpk said:
Umm having a little trouble unlocking. Am I to understand that you unlock with the device turned on ? because otherwise there isn't a home button...and where is the shield button ? I only have power and volume
buttons. This looks like the unlock method for the Shield not the Shield Tablet.
Sent from my Shield Tab
Click to expand...
Click to collapse
Your device should first be turned on. Then connect to PC and open a command prompt in your Android tools folder (where the ADB file resides) and type, "ADB reboot bootloader" (without the quotation marks).
Can I flash a ROW image in a US device?
The instructions in this guide are outdated and way more complicated than necessary. Once the official release of Android 7.0 Nougat becomes available/rooted, I will update the procedures in this thread. In the meantime, I recommend referencing this post along with the original instructions.
A massive shout out to @cheep5k8 for all the hard work he did in getting root and recovery working on the Pixel C. Please donate to him if you can. He deserves it.
Disclaimer: This will wipe your device. Backup anything important before you start. I mostly made this guide for selfish reasons. cheep5k8 has done a great job but some of the instructions are a little vague. I like being spoon fed and I wanted a resource to refer to in the future. You know the drill. If it breaks, not my problem. Post in the forums or hop onto the XDA IRC channel.
There may be more efficient ways to do this, but this will get you where you need to be. If you find any problems or have any suggestions, feel free to reply (BE VERY SPECIFIC WITH STEPS) and I will do my best to update the instructions.
Prerequisites:
ADB/Fastboot - Minimal ADB and Fastboot
ADB/Fastboot Drivers - I recommend using Wugfresh's Nexus Root Toolkit and using the full driver installation guide. Alternatively, you can install them yourself using the official Google Drivers (no installer)
An easy way to access the ADB prompt is to navigate to the directory that ADB is installed in, hold shift and right click inside the directory. This will give you an expanded right click menu that includes an option to "Open command window here." Select this option and a command prompt will open that is already in the ADB directory, saving you from having to do a bunch of cd nonsense. You can check to see if your device is recognized in ADB by typing "adb devices." If ADB and the driver are all working correctly, it should come back with something like "5A20001071 device." You can also check to make sure your device is recognized in fastboot by booting to the bootloader and typing "fastboot devices." It will show something similar.
Necessary Files:
Pixel C Recovery - Cheap5k8's Recovery -- NYCHitman's Recovery (newer)
Pixel C Root files - Download the XCeeD kernel, su.img, and SuperUser.apk
Copy these files to your directory that contains the ADB and Fastboot executables.
Device Prep:
Enable developer mode
Go to Settings > About tablet
Tap on Build Number 7 times until it says "You are now a developer"
Enable OEM Unlocking
Go to Settings > Developer options
Enable OEM Unlocking
Tap on Enable when a disclaimer pops up
Enable USB Debugging (ADB)
Go to Settings > Developer options
Enable USB debugging
Tap on OK when prompted with a disclaimer
If the ADB USB driver has been installed, you will see a popup that says "The computer's RSA key fingerprint is: xx:xx:xx:xx(blah blah)"
Check the box next to "Always allow from this computer"
Tap on OK
Unlock Bootloader:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
Input the following to unlock the bootloader:
Code:
fastboot flashing unlock
You will be prompted on the tablet screen with a warning about unlocking the bootloader.
Press the power button to unlock the bootloader.
The device will reboot and say "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds." You will also hear an audible beep. You will then see the green android with some spinny stuff. This is the userdata being formatted.
When complete, the device will boot back into the bootloader and say
Code:
Waiting for fastboot command...
Boot back into Android by inputting:
Code:
fastboot reboot
Your Pixel C will be reset, so you will need to re-enable USB debugging. Connect to your wireless network and then skip past everything else in the initial setup, as all of this setup info will be wiped again later on. Refer to the "Enable USB Debugging (ADB)" steps above to re-enable USB debugging.
Install Custom Recovery:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
With the Pixel C in the Fastboot bootloader and the recovery file in your ADB directory, input the following:
Code:
fastboot flash recovery (replace with custom recovery filename).img
Example:
Code:
C:\>fastboot flash recovery twrp-2.8.7.0-dragon-ryu-01082016-2.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
(bootloader) erasing flash
OKAY [ 0.054s]
sending 'recovery' (13760 KB)...
OKAY [ 0.349s]
writing 'recovery'...
(bootloader) writing flash
OKAY [ 0.375s]
finished. total time: 0.783s
Reboot into Recovery using the physical buttons. If you reboot the device back into Android, it will write over the custom recovery with the stock one. This will be fixed in the future.
Code:
Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
Install Root:
In TWRP, navigate to Wipe > Format Data
Type "yes" in the warning prompt and wait for the userdata partition to format. Again, this will wipe your tablet.
Press the Home button at the bottom when the format is complete
Navigate to Reboot > Bootloader to boot back into Fastboot
In the ADB prompt, flash the new kernel:
Code:
fastboot flash boot (replace with xCeeD kernel filename).img
Example:
Code:
C:\>fastboot flash boot xceed-kernel-google-dragon-02-01-2016-RC1.img
target reported max download size of 268435456 bytes
erasing 'boot'...
(bootloader) erasing flash
OKAY [ 0.064s]
sending 'boot' (6220 KB)...
OKAY [ 0.161s]
writing 'boot'...
(bootloader) writing flash
OKAY [ 0.197s]
finished. total time: 0.426s
Reboot into Android. The device may boot twice.
Code:
fastboot reboot
Reboot back into Recovery. Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
In TWRP, navigate to Mount and check only Data
In the ADB prompt move su.img to /data:
Code:
adb push su.img /data
Example:
Code:
C:\>adb push su.img /data
5677 KB/s (33554432 bytes in 5.772s)
In TWRP, navigate to Mount and uncheck Data
In TWRP, navigate to Reboot > System
Perform initial device setup
Once you are at the home launcher, re-enable USB debugging (Refer to Device Prep)
In the ADB prompt, install superuser.apk:
Code:
adb install Superuser.apk
Example:
Code:
C:\>adb install Superuser.apk
8612 KB/s (6227998 bytes in 0.706s)
pkg: /data/local/tmp/Superuser.apk
Success
Install Busybox from the Play Store: link
Congrats. You are now rooted (not in the Australian sense).
Big big thanks
Amazing, great job.
P.S. One thing to add, for those who bought SuperSU Pro, you can install that too from the Play Store instead of installing the APK, but at the moment, it will say that the su binary is outdated (because the xCeeD kernel comes with 2.66, but SuperSU is already at 2.67). There needs to be a somewhat better solution but it's a bit hard to come up with it.
xCeeD v1-RC4 will have SuperSU updated to 2.67, and I'm thinking of how to make it possible to flash the normal SuperSU ZIP in TWRP. I will probably modify TWRP in some way to make that possible.
Very good step by step, guide, I went through the same process myself yesterday, although without the benefit of your guide!
Just one additional suggestion I would make, especially for people who have already got things set up nicely on their device.
Before doing anything you can make a backup of your device data using adb.
I used the guide at - http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Although you cannot guarantee everything will restore perfectly (I recommend that for important apps that have the capability - backup the settings manually and remember to copy them off the device), it certainly saved me a heck of a lot of time in putting things back exactly as they were before - and it is a lot quicker than letting google backup restore things.
Does this void the warranty?
Great job,anyway
Enviado desde mi Pixel C mediante Tapatalk
Cool, but you don't mind make put the video or pictured for guides.
Keep it up!!
there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command
Scarfacez2007 said:
there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command
Click to expand...
Click to collapse
Are you booting into TWRP recovery or the stock Android recovery?
I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command
Thank you for this in depth tutorial.. GREATLY appreciated..my C will be in tomorrow just in time for RC4! Hopefully all goes smooth with this. So no need to swipe fastboot fix in twrp??
Scarfacez2007 said:
I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command
Click to expand...
Click to collapse
I had that too after my first attempt, I reinstalled TWRP and it worked after the second flash.
There were no errors shown either time.
The same thing - no command, though the TWRP is installed. Re-installing doesn't help at all.
UPD Just managed to do this step by manually booting into recovery without booting the ui.
I updated the instructions saying to use the physical buttons to boot into recovery immediately after writing TWRP to flash. I believe this should mitigate the issue with the device overwriting the custom recovery before the kernel is flashed.
You don't mind guide put with the video or picture?
Scarfacez2007 said:
You don't mind guide put with the video or picture?
Click to expand...
Click to collapse
I have no plans to make a video or pictures.
Finally I got rooted about time!!!! thanks oRAirwolf!!!!
I just wondering I can download Xposed 6.0.1 on my pixel c?
Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
I have no idea. I would probably start a new thread in the Q&A section.
Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
Yep xposed works fine
How did you get download xposed with arm64 for Google Pixel C? where get it? you don't mind can find for me on link?
This document ALSO provides knowledge about android system work flow
The following Steps will help and resolve issues related with Zenfone 2 Series,
Do remember that most of the steps which are provided here are not automated, So have patience.
This guide will help you Recover Completely bricked mobiles - You are responsible for you own actions
We will try to do
1. adb and fastboot installtion
2. Unlock Bootloader
3. Custom Recovery Installation
4. Root Device
5. Unbrick (Asus Zenfone 2 ze551ml/ze550ml ONLY)
6. Recover lost IMEI's and Device Serial number( Of course the valid one Which is mentioned for your device ) (Asus Zenfone 2 ze551ml/ze550ml ONLY)
7. Recover serial number, mac, bluetooth address (Asus Zenfone 2 ze551ml/ze550ml ONLY)
____________________________________________________________________________________________
*************************** 1. adb and fastboot installtion ********************************
____________________________________________________________________________________________
used for Basic troubleshooting and updating android system
In windows just copy these four files into windows(c:/windows) folder or install it in windows folder
AdbWinApi.dll AdbWinUsbApi.dll adb.exe fastboot.exe
Download Link https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/
For Linux refer distribution guide
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
********************************** 2. Unlock Bootloader ************************************
____________________________________________________________________________________________If you are on Android L(5.x) Asus provide boot loader unlock tool you can download it from asus.com
Doing so will make your device warranty void. or you can use custom bootloader unlock
if you are on Android M(6.x) Asus doesn't provide any tool to unlock for Android MM
You should use custom bootloader unlock you can follow the procedure provided by the unlock tool
FAQ
Can we relock device ?
YES
Why we need to unlock bootloader ?
Bootloader is a program which will allow your device to load Android OS
Why Bootloader is locked ?
To protect the devices from unauthorized access to third party. More of Business tactics
How to
Download the file from https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!Ux9HlCzA zip file which corresponds to your Device
follow the instructions provided in the zip file
The successful of that unlocking process conclude that your device bootloader is unlocked, but its not ROOTed
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
**************************** 3. Custom Recovery Installation *******************************
____________________________________________________________________________________________
There are majorly two custom recoveries used
* CWM - clock work MOD
* TWRP - Most flexible recovery mode ( more than just recovery)
you can download cwm from link (search google)
and TWRP from https://twrp.me/Devices/
once you downloaded the binary file from respected link provided
boot the device into fastboot mode
Follow Steps (only Asus Devices)
--------------------
* Turn off the mobile, Press and hold the volume UP button, Then press and hold the power button until device vibrates release only power button, once you see the ASUS logo release the Volume button
* fastboot devices - (in Computer prompt) wait till your device listed
* fastboot flash recovery filename(cwm.img or twrp.img) - it will take 20-50 Sec to complete
* press vol+ or Vol- until you see recovery mode on the screen and press power button
Once all the steps completed successfully you should be able to see the custom recovery screen
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
************************************ 4. Root Device ****************************************
____________________________________________________________________________________________
Everyone who started using android device they all come across the word "ROOT" soon or later.
No wonder, whoever have root access to device can do wonders on android device. Root is nothing but having administrator privilege to make system wide changes, changes applied using root will applied without any question. no more, no less. whatever happens to device(system) you are your own, "SU" is nothing but "super user" and root is a super user which is from UNIX and Linux.
After unlocking android device bootloader, you need to patch su(binary file) command into android system which will allow you to run commands from adb shell prompt as root user.
There is no universal procedure to ROOT device, everything depends on the android device company, so based on manufacturing company you can google and get your device ROOTed
To root your Ze551ml/Ze550ml
Tools Required
---------------
Unlocked Bootloader Asus Zenfone 2(Ze551ml/Ze550ml)
SuperSU-2.78SR1-zf2_6.0.1.zip (Google search SuperSU-2.78SR1-zf2_6.0.1) download the zip file which has zf2 in filename or try https://www.yadi.sk/d/vVk0Qd-Ow7fdK
Custom Recovery (TWRP or CWM)
Steps to Root Device
---------------------
# copy SuperSU-2.78SR1-zf2_6.0.1.zip file into sdcard
# adb reboot recovery
OR
* Turn off the mobile, Press and hold the volume UP button, Then press and hold the power button until device vibrates release only power button, once you see the ASUS logo release the Volume button
* press vol+ or Vol- until you see recovery mode on the screen and press power button
# From TWRP main screen select install
# Browse and select SuperSU-2.78SR1-zf2_6.0.1.zip from sdcard
# select reboot
# adb shell
# su ( allow the permission from superSU app on mobile)
That concludes you are at root prompt (Device Rooted successfully)
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
*************************************** 5. UNBRICK *****************************************
(Asus Zenfone 2 ze551ml/ze550ml ONLY)
____________________________________________________________________________________________
Cause
----------------
Custom or Wrongly flashed ROMS
Most of the time unlock bootloader and ROOTing device leads to bricked mobile
Symptoms of bicked Device
------------------------------
1. Black Screen - You can sense vibrations only, from the device when you press power button but nothing on the screen(Unless screen hardware faulty)
2. Vibrations - Device keeps on vibrating at same interval of time (usually every 5-10 mins loop)
Tools required
-------------------
- Xfstk windows application (google search "xfstk-downloader_v1.7.0")
- Intel Soc windows driver (google search "iSocUSB-Driver_v1.2.0")
- xFSTK_ZE551ML-sal358-amtech.vn.zip do (google serach "xFSTK_ZE551ML-sal358-amtech.vn" download the zip file which contains 3 bin files)
- Asus user UL-Z00A-xx-x.xx.xx.xxx-user.zip you can download this zip file from asus website (https://www.asus.com/in/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/)
- partition.tbl (https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB)
some files are located at https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB
Remember the windows operating system will block some of the drivers from loading on windows 7, 8 or 10 just override that, install the driver first, Intel Soc windows driver after that install Xfstk windows application
How to Steps
--------------
* Open XFSTK Downloader, Click MRD tab A0 / B0 + A0 + CRC Tab, scanning shows Moorfield in device list.
* Click Options--> modify settings check Enable Override and change GP Flag overide value 0x800000807. Click OK.
* Change value of Device detection timeout to 120
* FW DNX should point to droidboot_dnx.img.POS_sign.bin (browse and locate)
* IFWI should point to ifwi.bin (browse and locate)
* OS DnX dont make any change to this field
* OS Image should point to droidboot_dnx.img.POS_sign.bin (browse and locate)
* Click Begin Download (Remember Once you see Scanning ....... device detected:1 which will be changing 0 to 1, couple of times wait till you see download sucessful before that mobile screen goes on and off let it continue for couple of minutes usually (2-5 mins) later you see 4 color strip on mobile screen and it enter into fastboot mode if you see that, your device is unbricked. if you dont see fastboot mode just turn off your mobile and try to enter into fastboot mode using volume up (press and hold) and power button(Press and hold release only power button when device vibrates)
* extract UL-Z00A-xx-x.xx.xx.xx-user.zip into a folder and copy partition.tbl into same folder open command prompt in that folder
* Run these commands one after another on every sucessful completion of command
fastboot oem erase_osip_header
fastboot oem erase_token
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase APD
fastboot erase ADF
fastboot oem wipe splashscreen
fastboot oem stop_partitioning
fastboot flash splashscreen splashscreen.img
fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin (Note This file is located in ifwi.zip)
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
* select Recovery mode using volume up or down key and press power button
* When you see android logo on the screen press and hold power button, press and release volume up key then release power button
* select sideload using voulme key and press power button
* on computer enter adb devices, should show connect device
* Run command adb sideload UL-Z00A-xx-x.xx.xx.xx-user.zip and enter, this command will take minimum 20-30mins to complete
if everything goes well your device is back to life, Congrats
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
******************** 6. Recover lost IMEI's and Device Serial number **************************
(Asus Zenfone 2 ze551ml/ze550ml ONLY)
IT's ILLEGAL TO TAMPER IMEI RELATED INFORMATION AND IT IS PUNISHABLE OFFENCE
THIS IS JUST AN OVERVIEW AND
FOR KNOWLEDGE PURPOSE ONLY____________________________________________________________________________________________Its mobile user's NIGHTMARE when they see Wrong IMEI and serial number
Cause
---------------------------
Custom or Wrongly flashed ROMS
Symptoms of Wrong IMEI and Serial Number
-------------------------------------------
Unable to connect to network even though mobile boots properly and works normally
How to Check
---------------
When you run adb devices from your pc its shows device serial number
IMEI can be checked in Settings --> About --> Status --> IMEI information OR
Call Dialer enter *#*#4636#*#* and select Device Information
Tools required
-----------------
Digma_SoFia_IMEI_recovery.rar (Google search "Digma_SoFia_IMEI_recovery file contains contains Digma software and windows driver)
IntelAndroidDrvSetup1.10.0.exe (Google search "IntelAndroidDrvSetup1.10.0") IntelAndroidDrvSetup1.10.0.exe
Rooted Device
links
Digma - https://yadi.sk/d/30q9w4KJjvgHd
IntelAndroidDrvsetup - https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB
Steps :
* To identify the com port turn on your device and run command adb shell(from computer command prompt)
* Run su
* your device should be rooted so it will give su prompt(#)
* Run setenforce 0
* Run setprop system.at-proxy.mode 1
* Install IntelAndroidDrvsetup and intel mobil family imc1 driver which is included in Digma software ( This is the hard part to setup as windows driver installation restrictions and identifying com ports on usb interface make sure these software and driver installed properly)
* after successful installation of driver and Phonetool run Phonetool
* settings --> Phonetool check RTS and DTR on select your phone com port listed in port list click ok
* click on update info (Should say success connecting to port)
* Click modes --> security click on show advanced options
* Click unlock
* Click on personalization programming tab
* scroll down and click add button
* add your mobile phone imei number (only first 14 digits) again add one time if you mobile is dual sim phone
* Click Execute (will take upto 60 sec)
* if above all steps completed without any error, just reboot your phone and check your imei number should show your real imei numbers
Note some times you needs to flash imei number after setting setprop system.at-proxy.mode 3 to flash 2 imei number just try until both imei show correctly on you mobile check your imei number by dialing *#*#4636#*#*
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
**************** 7. Recover serial number, mac, Bluetooth address **************************
____________________________________________________________________________________________
Refer https://forum.xda-developers.com/showpost.php?p=66877096&postcount=28 Thanks to BORETS24
Thanks, helped a lot.
Unsure of what happened to my phone
Hey, I was trying to root my zenfone 2 ZE551ml by following a youtube video. It asked me to first put superSu.zip inside the SD Card which I did. Next - unlock the bootloader of my phone by downloading an zip which has an unlocker.bat file. Then it asked me to flash TWRP recovery using fastboot which I also did and then to boot into twrp and install the supersu.zip. I did everything but the last step, as when i tried to boot into the recovery to use twrp, the phone restarted, came to the white asus screen, stayed there for a very long time and then went back into the bootloader.
At this point I got frustrated and thought of reinstalling everything. So I downloaded the zip file for the latest firmware, flashed recover, boot and droid boot and then when I restarted the phone to go into the recovery, the white asus screen just keeps on repeating itself. The device keeps on shutting down and then restarting but never goes past the white asus logo screen where it says "powered by android", doesn't even let me get into fastboot.
I am new to all this and any help from anyone is highly appreciated. Thanks
error loading partition.tbl? edit: now im stuck on "cannot load fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin "
after doing these steps
fastboot oem erase_osip_header
fastboot oem erase_token
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase APD
fastboot erase ADF
fastboot oem wipe splashscreen
fastboot oem stop_partitioning
fastboot flash splashscreen splashscreen.img
fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin (Note This file is located in ifwi.zip)
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
when i reboot and select recovery i cant load recovery , it opens bootloader
how to install recovery
Hi, good day.
I am having 0 response when I hit this command. setprop system.at-proxy.mode (number) Do you know why ?
Device is rooted, since I've unlocked the bootloader using the ASUS app.
Fastboot erase config....
After that I stucked at boot logo
Used xfstk then aft but stucked at boot used fastboot commands for flashing system all gonna smooth but stucked at boot...
Used recovery to sideload marshmallow ... succeed. But also stucked at boot ..unlock boot loader flash TWRP flashing custom rom also stucked at boot logo... PLZZ help me guyzzz
And it shows error in TWRP
Unable:to mount Config(invalid argument)
I'm on step, Run setenforce 0, but it returns an error message, "Couldn't set enforcing status to '0': Permission denied". Please advise. Thank you in advance!
***MOD EDIT: BE WARNED THAT WHEN PERFORMING THESE INSTRUCTIONS, THAT ALL DATA WILL BE WIPED (FACTORY RESET) FROM THE DEVICE - THIS INCLUDES THE INTERNAL DEVICE STORAGE (INTERNAL SDCARD). YOUR EXTERNAL SD FILES, HOWEVER, ARE SAFE AND WILL NOT BE MODIFIED.***
Hello.
I will attempt to keep this tutorial as concise as humanly possible, without the expenditure of costly applicably valid information. There are many other persons (whom I do not know) to thank for the majority of this information (from XDA Developers and other sites around the world wide web). Without further adieu: Let's begin!
The base operating system that this tutorial references is a Windows distro (I am operating on: Windows 10 Home OEM).
Target phone specs (http://www.lg.com/us/cell-phones/lg-MS330-White-k7):
Carrier: MetroPCS®[*]
[*]Make: LG K7 ("HW" or "White")
[*]Model: LG MS330
[*]Build number: LMY47V
[*]Software version: MS33010m
[*]Android version: 5.1.1
[*]Android security patch level: 2017-04-01
[*]Kernel version: 3.10.49
Prerequisites:
A USB cable (able to transfer data)
A functional copy of Windows
An internet connection (to download the software tools)
If you opt to not download and install the stock firmware ROM (*.kdz) and LG UP (used for many things):
You are taking a great risk in the event something catastrophic occurs (no backup; Corrupted partition(s); Broken hard-key reset; etc).
The LG UP tool combined with the ROM file enables you to fully slate the drive on the phone (effectively restoring it to a manufacturers state; No partitions, no data, nothing!).
It also acts as a major fail-safe as previously iterated.
You can also (if you take the time of day) use it to create your own customized 'factory style' bloatware free, customized filled state *.KDZ ROM! Although TWRP backups should be capable of emulating this type of behavior.
The ROM is ~1GB in file size from the server (capped at ~10MB/s download rate at the time of the writing of this post). Translation: It takes a while (~30min) to download. Fortunately for me: I had it and had to use it earlier today (TWRP backup failed).
Software tools (ADB, TWRP, SuperSU, LG UP, ROM):
ADB (Android Debug Bridge): https://developer.android.com/studio/releases/platform-tools.html
TWRP (Team Win Recovery Project) v3.2.1.0: https://twrp.me/lg/lgk7.html
SuperSU (SuperUser) v2.82: http://www.supersu.com/download
LG UP Lab v1.10: https://www.mylgphones.com/download-lg-up-software
Stock ROM (MS33010i -- *.kdz): https://mega.nz/#F!sdwRDLbZ!yPOiRPv5QJS_9I4hzL4ptQ!ddJHSBhR
This will be a step-by-step process; If you skip a step: Make sure you have a good reason!
I will be assuming you have followed the links above and both downloaded and installed the appropriate software (ADB, LG UP). Keeping everything organized is key.
For instance: Create a folder on your main drive ("C" drive is common traditionally). Name this folder "Rooty." Create a short-cut of "adb.exe" and place it there. Place the SuperSU *.zip and *.kdz ROM data files in the same directory as well.
Overview of procedures:
Enable "OEM unlock"
Enable "USB debugging"
Unlock OEM bootloader
Install ("flash") TWRP
Using LG UP (after TWRP is either installed or live loaded)
Install SuperSU
Step 1) Enable developer options
Enabling developer options -- Navigate to "Settings," then to "About phone," then to "Software info," then tap on "Build number" until the dialog states: "No need, you are already a developer."
Step 1.1) Enable OEM unlock option
Traverse two levels up; Tick off "Enable OEM unlock"; Scroll down 2 options and tick off "USB debugging."
Step 2) Unlocking the OEM bootloader
Insert your USB cable to connect your desktop/laptop to your cellphone; When the dialog comes up asking for permission to debug: Accept it (OPTIONAL: Tick off the 'always allow this device'). Ensure "Media device (MTP)" option is selected (it will automatically install the drivers from your phone to your computer if enabled).
Step 2.1) Unlocking the OEM bootloader (for the not-so-technically-inclined)
Create a textfile and name it whatever you'd like (I prefer the filename: "OEM_Unlock.bat").
Copy and paste this script and simply place it in the same directory ('folder') as ADB.
Code:
REM This will reboot the phone into "bootloader" mode
adb reboot bootloader
REM This will unlock the OEM bootloader (a message will display on the starting logo afterwards)
fastboot oem unlock
REM This is just to verify that it was successfully unlocked ("unlocked: yes")
fastboot getvar unlocked
Alternatively: You can manually input the commands one at a time by typing them yourself or copying and pasting.
Step 3) Installing TWRP
You can just use ADB to directly flash the recovery partition of the ROM on the phone:
Code:
fastboot erase recovery
fastboot flash recovery C:/Android/recovery.img
You can also simply 'live boot' into TWRP (less risk of a faulty TWRP):
Code:
fastboot boot C:/Android/recovery.img
Now TWRP is installed (unless you simply loaded the image file into the phone's RAM).
Using LG UP to flash the ROM ("WIPE" every partition of the phone with TWRP; EVERYTHING will be lost:
To use LG UP: You only need to power down the phone fully (ensure it is not yet connected to the computer).
Hold the "VOLUME UP" key (do not release); Insert the USB cable. The phone should (within moments) place itself into "DOWNLOAD MODE." At which point LG UP will recognize the phone. There will be two options: "Refurbished" and "Upgrade"; Tick off 'upgrade' every time! Below that is "3 dots" which enables you to navigate (GUI) to the directory of your desired *.tot or *.kdz file. Simply hit "start" and it'll flash the phone (it usually takes ~300s or ~5m).
Step 4) Installing SuperSU
Through TWRP: Click on "Advanced"; Then click on "ADB Sideload"; Tick both the "Wipe Dalvik cache" and "Wipe cache" (these will force all APKs to be reinstalled via root level). Then slide the bar across. Return your attention to Windows.
You can just use ADB to directly sideload SuperSu onto the phone.
Code:
adb sideload C:/Android/SuperSU.zip
The final page asks if you would like to install the "official TWRP app" and also if you'd like to install it under "system" privileges (one less than root).
The end! You now have root accessible privileges through the "SuperSu" application (which contains root privilege at this point).
Alternatively to manually inputing everything by hand into ADB: I've whipped up this simple batch script for Windows:
Code:
ECHO OFF
CD\
CLS
ECHO Waiting for the device to communicate (ensure you are not in 'recovery,' 'sideload,' or 'bootloader' state)
adb wait-for-device
REM Reboots to the bootloader
adb reboot bootloader
REM Unlocks the OEM bootloader
fastboot oem unlock
REM Quick check to see if it successfully unlocked
fastboot getvar unlocked
REM Flashes (deleting the stock ROM recovery program)
fastboot erase recovery
REM Flashes (copies the TWRP custom recovery program)
fastboot flash recovery C:/Android/recovery.img
REM Loads the TWRP custom recovery program into memory (a "live boot")
fastboot boot C:/Android/recovery.img
REM Pauses execution until the phone boots into "recovery" state
ECHO Wait until the phone enters a "recovery" state...
adb wait-for-recovery
CLS
ECHO Traverse to "Advanced" then to "ADB Sideload"
ECHO Check off clearing both the Dalvik cache and cache
ECHO Press any key *after* you swipe the bar across
ECHO(
PAUSE
REM Copies over the APK to the ROM (security exploit to gain root permissions)
adb sideload C:/Android/SuperSU.zip
adb reboot
How to use the batch script file to root your phone with ADB, TWRP and SuperSU:
Place: SuperSU.zip and TWRP.img in the same directory as the ABD/fastboot executables
Modify the absolute paths and file names to your system (EG: "C:/Android/" and "recovery.img")
I hate to post this, but I feel it to be utterly important to express my deepest gratitude to all those who have posted this information that was scattered about the internet. This is my first Android or PHONE for that matter to root! It was quite the under-taking (nearly a 48 hour scourge of research). I've learned quite a bit how the Android OS works internally as a result; as well as the tool-kits that are commonly used in conjunction with modding the Android (out of the scope of this thread).
I hope this very recently updated and compiled information will help ease the suffering of another's entrance into the world of rooting Android phones. I also hope it really deepens the understanding of what they're doing (EG: The commands being utilized with abd and fastboot).
Here is a helpful link in regards to adb/fastboot:
- Quick reference to abd commands (syntax and meaning): https://developer.android.com/studio/command-line/adb.html
- Alternatively: You can use "adb help" to see a print-out of the commands and arguments (same applies to fastboot).
Happy rooting, y'all!
Thanks for the write-up!
The attached SuperSU.zip worked perfect to gain root on my K7 m1 using the adb sideload in Twrp and PC.
My bootloader I had already unlocked. Twrp, I flashed before I accomplished that feat!
Was rooted with Kingroot but wasn't satisfied with that.
Factory reset, and followed your adb sideload instructions to gain root with SuperSU.zip ..
Thanks again my friend.
Custom Roms for the K7 seem to be scarce, unless I am looking in all the wrong places.
Would be much appreciated if anyone could help me on that front?? ... Please let me know.
Good Day
With very insignificant changes to syntax used above I found this works perfectly on OSX as well.
Thanks
hi, i cant seem to unlock the bootloader. i have already enabled oem unlock and usb debuggin from settings but it always fails
Code:
PS C:\adb> adb devices
List of devices attached
ZSTSS8DUSWZD9LCE unauthorized
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot devices
ZSTSS8DUSWZD9LCE fastboot
PS C:\adb> fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 9.294s
I should note that kingrot also failed to root
i dont know whats wrong, imma gonna try factory reset and try again
UPDATE
It seems the allow oem unlock option got disabled by itself somehow, i re enabled, tried again and unlocked succesfully
UPDATE 2
Aaaaand Bootloop, dunno what went wrong, iv'e reached step 4, flashed twrp, then tried to reboot into twrp and now im stuck in bootloop
Code:
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 8.981s]
finished. total time: 8.983s
PS C:\adb> fastboot getvar unlocked
unlocked: yes
finished. total time: 0.003s
PS C:\adb> fastbot erase recovery
fastbot : The term 'fastbot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastbot erase recovery
+ ~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastbot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\adb> fastboot erase recovery
erasing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.004s
PS C:\adb> fastboot flash recovery c:/adb/lg.img
target reported max download size of 134217728 bytes
sending 'recovery' (12010 KB)...
OKAY [ 0.394s]
writing 'recovery'...
OKAY [ 0.706s]
finished. total time: 1.103s
PS C:\adb> adb reboot recovery
error: device '(null)' not found