Related
hi, this is how i managed to get root working on my tab, everything went fine for me till it came to booting into recovery then nothing use to happen so i combined two separate guides to get it working. thanks (bcmobile and 411tecknology)
the command in "(getting root 5) )" worked for me as i was getting stuck with "fastboot flash recovery skitzandroid-recovery.img"
i unlocked the bootloader by firmware upgrade the the following
for all those people like me with no experience in dos commands or linux, hope this works for you
PREPARE:
1) With your Tab in fastboot mode (step 1 of “GETTING ROOT” below), make sure you have a working fastboot implementation:
working dir\\fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won’t get any response.
2) Downlad the two files attached to this thread
3) create a folder in drive c naming it "root"
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!) c: root
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder( c: root) should now have 1 IMG file and one ZIP file.
6) copy fastboot files to the the folder that you are going to use as working dir ( c:root)
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
working dir or c:\root>adb push skitzandroid-10-1v-root.zip /sdcard
GETTING ROOT:
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
keep doing cd.. until you get to "c:>" then
cd/root
5) Run the following command:
c:\root> fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options)
to select “Install zip from SDCARD” (or something like that)
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
Once complete, use the Volume rocker to select “REBOOT” from the menu and press (tap!!!) the POWER button to confirm selection.
9) YOUR’RE DONE. Press the thanks button on this thread to continue
TESTING:
Check your apps menu to confirm the existence of SuperUser app.
whats wrong with this?
http://forum.xda-developers.com/showthread.php?t=1079781
Nothing!
I used it on UNLOCKED 10.1v (not from Vodafone) and had no data loss!
Great, Thanks
Frank
I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes
TNTCOSMOS said:
I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes
Click to expand...
Click to collapse
once you start your device in fastboot mode and connect it with the computer to make sure your device is recognized by the computer you open command prompt take it to your working dir.. (ie. c:>root) in our case type fastboot devices and hit enter, if your computer recognized your device you will the serial number under it.
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
assuming you have installed sdk if not please do so, then staying in sdk go to
(C:\android\android-sdk-windows\platform-tools ) by clicking your mouse in desktop
(not cmd prompt). above eg.. is how i installed sdk on my desktop yours may be different, now in platform-tools you will see two files called fastboot copy them both to to your folder called ..root.. and you are set to go.
bottom line is if you want to start fastboot from any folder in cmd you have to have these two files in the folder.
also if you know that your device is detected by your computer dont worry about step 3. all it does is tell you that your device is connected.
I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!
TNTCOSMOS said:
I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!
Click to expand...
Click to collapse
Glad to hear that you finally got the root.
same problem
TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
i've tried with pdanet too but it's not working....like the computer can't see the device...any ideea ???
and when i write "fastboot boot ......etc......" it says <waiting for the device>
please help
You need the drivers installed for fastboot, have you installed them? Please have a look at the [Guide] Unlock your bootloader thread. it contains all the details to get fastboot working.
thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???
zbuggy said:
thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???
Click to expand...
Click to collapse
The easiest way if you are rooted is to install rom manager from the market. It has an option to reboot to recovery if you have CWM installed. It also allows you to update to the latest CWM recovery if there is one.
i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?
Download latest rom and instructions from samfirmware.com using odin Get ur tab into fastboot mode with 3 button recovery and start from scratch.
It should work out
Sent from my GT-P7500 using Tapatalk
zbuggy said:
i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?
Click to expand...
Click to collapse
Do the following. If you have not yet odin.
Download the full rom.
Follow instructions in how to get into fasboot in sticky thread.
Once in fastboot you can load recovery via it, to do that download the recovery from droidbasement.com/blog, search on pershoot's website for recovery 4.0.4 if i remember correctly then type
fastboot boot recovery.img
where recovery.img is the name of the file you downloaded from droidbasement.com
Recovery will then load give it a minute or so.
Once loaded you can push the downloaded full rom via adb. That is part of the android sdk.
Like this: adb push romfile.zip /data/media/ (this will take a few minutes)
Then in cwm instal rom.
I hope it helps. Btw, remember you need to flash the wipe script of the rom before you install the rom if you are comming from stock.
Send from my GT-P7100
10x everybody it worked!!!!!!!!
Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...
DannyBiker said:
Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...
Click to expand...
Click to collapse
Hello,
I have been successful with rooting on win7. With win xp - after a few day struggling - fastboot did not give a go. Hope this helps
I just can't get the "Adb Original" signature from Pdanet. I always get standard Adb. I add the galaxy tab lines in the .inf file but still...
Do you guys edit the inf file with Wordpad or another tool ?
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step
hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
I was having the exact same problem last night, following the same instructions. I still could not figure out how to sideload the OTA, so I ended up just flashing the update and starting from fresh. Wish I had the answer for you.
Here was my thread asking pretty much the same thing: http://forum.xda-developers.com/nexus-6/help/disconnects-computer-entering-bootloader-t3230705
danarama said:
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step
Click to expand...
Click to collapse
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
In the command window — make sure you are in the directory where ADB and Fastboot reside — type: “adb sideload [the full name of the file].zip” without the brackets around the file name.
The update will install and reach 100 percent.
Reboot and enjoy the latest version of Android Marshmallow.
Click to expand...
Click to collapse
(red arrow) and then the cmd says the null error, i am trying this now
I had the same problem. Turned MTP on and then it worked. You're told to turn it off but don't... Its in Settings-Storage-touch the ... Menu top right corner, USB settings and turn ON MTP mode. It worked well for me. I also used the Nexus Root Toolkit - makes things much easier!
Click to expand...
Click to collapse
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)
hendyanto said:
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
(red arrow) and then the cmd says the null error, i am trying this now
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)
Click to expand...
Click to collapse
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.
danarama said:
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.
Click to expand...
Click to collapse
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.
hendyanto said:
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.
Click to expand...
Click to collapse
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)
I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!
danarama said:
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)
Click to expand...
Click to collapse
qwerty1gr said:
I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!
Click to expand...
Click to collapse
Thank you guys! But after this "happy"night, i woke up to the OTA for marshmallow arrived on my phone, so see you guys on the rooting section instead, Thank you thank you for the help
Disclaimer:
I am not responsible for what you do to your device, I tested these things for myself and posted it from my own experience, if you point the finger at me for whatever happens to your device, I will laugh at you.
HOWEVER, I am willing to help as long as it is asked kindly, and provided me with enough information.
Requirements:
Huawei P8 Lite ALE-L21 (DUAL-SIM)
5.0 Firmware of choice
Unlocked bootloader
Patience
Correct drivers
SD card of atleast 8 GB
Drivers: Install these before even starting!
Minimal ADB Fastboot drivers
Huawei HiSuite
Kingoroot Windows
TWRP 3.0.2.0 Kirin variant
Preparing environment: Making sure no admin priveledge is necessary
Install all drivers mentioned above in their standard directories, don't change anything.
Go to the following path:
Code:
For x64 OS:
C:\Program Files (x86)\Minimal ADB and Fastboot
For x86_32 OS:
C:\Program Files\Minimal ADB and Fastboot
Copy these files:
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
And paste them on the desktop, in a folder called "rootingtools" so you're easily able to find it.
Then, go to your phone and enable USB debugging mode by going to
settings - about phone - press Build number 7 times
settings - developer options - USB debugging
Copy the content of "TWRP-3.0.0-2_P8-lite_KIRIN_variant.zip" and paste it into the "rootingtools" folder.
Backing up: Even though the unlocking process is not going to wipe your data, atleast it didn't for me, make SURE you have everything that you need backed up from the phone's internal memory.
Backing up your SD card wouldn't hurt neither.
First things first, unlock your bootloader!
I used this: https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
What you do is: fill in everything correctly and get the number at the end. It should be something in the words of:
Code:
Your unlocking password is: XXXX XXXX XXXX XXXX
(X resembles numbers, 16 numbers in total)
Copy the 16 numbers and go to the "rootingtools" folder on your desktop.
Hold the SHIFT key and right click inside the folder, then press "open command window here"
Now take your phone, power it off and power it on by holding volume DOWN and POWER.
You will get a white screen that says something like fastboot, and an android logo.
Plug your phone into the PC via USB cable.
In the command window write:
Code:
fastboot.exe oem unlock UNLOCKKEY
Where UNLOCKKEY represents the key you just copied, right clicking pastes the key in the command window.
It should return finished, so now your phone should be unlocked!
If you look at the screen, there will be text beneath the green Android logo saying "unlocked".
In this case, the operation has succeeded and you can go to the next step, else you can try again or post a reply.
Now write:
Code:
fastboot.exe reboot
Now the phone will boot up like normal.
Close the command window.
Android 5.0:
If your android version right now is Android 5.0, and you actually WANT to root 5.0 or anything below 6.0 you can proceed with this step, if you have 6.0 or want to root 6.0, skip this step.
Since your android version is 5.0 you're blessed!
You can easily root, but before proceeding you might want to make a backup
Make sure you have about 8GB of free storage either on an SD card or internal memory first.
Connect your phone to your PC in the booted-up state where you can see the homescreen, making sure that USB debugging is enabled.
Shift + right click inside the rootingtools folder to open a command window and write:
Code:
adb.exe reboot-bootloader
Your phone will reboot into the bootloader, a white screen with a green Android logo that says "unlocked" beneath it.
Now on the command window write:
Code:
fastboot.exe flash recovery recovery.img
Wait for it to finish and pull out the USB cable so it is NOT attached.
Power off the device by holding the power button, and power up by pressing volume UP + POWER.
Keep holding volume up until you see the Team Win logo.
Just slide the slider to the right.
Now go to "backup" and check every partition available.
In "name" you write:
Code:
MainBackupURTD
Then, go to the "options" tab and enable compression.
Go back to the "backup" tab and press "select storage".
From here you can choose where to back your data up, whether it be the internal storage or external SD card.
Press OK and swipe the slider to the right to start backing up.
Plug your phone in to make sure it doesn't power off during backing up, this process takes a while and you should let it do its thing.
When done, press "reboot system", your phone will reboot.
Let it fully start up.
Then, run Kingoroot on your PC.
Meanwhile, download the "SuperSU" app from the Play store.
Press the big "ROOT" button in Kingoroot and press "cancel" on every app your phone tries to install.
That way you will not install Kingoroot but SuperSU.
It will say "succeeded".
Now you can go on your phone and open the SuperSU app.
It will ask for an upgrade, press OK and go further with the normal installation (not the TWRP/CWM installation).
Let it do its thing and restart your phone.
Install any root checker and see if you're rooted!
Android 6.0:
Firmware version B188 or higher, below B524/B535 (excluding B524/B535):Upgrade firmware to this one: LINK (Link fixed)
Installation instructions: place file to the "dload" folder in your SD card or internal storage, then go to settings - updates - menu - local update and press the update.zip.
Then, follow the guide reported here: http://rootmygalaxy.net/root-huawei-p8-lite-android-marshmallow-6-0-update/
Enabling Gyro sensor (rooted android 6.0, B524/B535 firmware only! ( sorry :[ ) ):
Download attached file.
Put attached file to SD card.
Open ES file explorer, swipe to the right, enable root browser and click the R/W tab, then set /system as RW.
Then copy the attached file.
Paste the attached file in /system/etc/permissions
Press the search button and search for "gyro" without quotation marks.
Long press the only file that's there - menu and press properties.
Then change the permissions to 644, it should look like this O represents off, X represents on;
X X O
X O O
X O O
Set UID is off, Set GID is off, Sticky bit is off.
Reboot phone and download "Sensor box for Android" on the Play store and enjoy your gyroscope!
Now you can use Google Cardboard, though you have to install the APK...
You can watch 360 videos on youtube too.
Credits, sources and links:
http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320
http://huaweifirmware.com/huawei-p8-lite
http://www.androidsage.com/2016/02/...-6-0-marshmallow-beta-firmware/#axzz48veWSvTk
http://forum.xda-developers.com/p8lite/general/root-huawei-p8-lite-ale-l21-android-6-0-t3307686
https://www.kingoapp.com/
Subject to change
Hiya, will the gyro hack work on a L02 B130 Android 5.0 as i can't get an update to 6.0 here in New Zealand?
unable to get unlock code
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
@sevenaudio
As far as I know, the hack is for android 6.0 but there should be no problem in trying it out
It's just that it only worked for me on these FW
@DrLittle
I think Huawei has this policy of using your Huawei ID for 2 weeks (2 weeks online time) before you can unlock it
You could try sending them an email!
always i get the error failed status malformed 1 bytes
finished total 0.005s
eriuzz said:
always i get the error failed status malformed 1 bytes
finished total 0.005s
Click to expand...
Click to collapse
Hi, can you pinpoint what you were trying to do when it got stuck?
As in, what were you trying to flash.
And what is your phone model?
oziboy said:
Hi, can you pinpoint what you were trying to do when it got stuck?
As in, what were you trying to flash.
And what is your phone model?
Click to expand...
Click to collapse
just trying to unlock the bootloader i have my code from huawei and when i try to use it through adb appear that error i said
eriuzz said:
just trying to unlock the bootloader i have my code from huawei and when i try to use it through adb appear that error i said
Click to expand...
Click to collapse
Are the dorrect drivers installed, are you sure you copied the whole key?
Use an other usb porta.
oziboy said:
Disclaimer:
I am not responsible for what you do to your device, I tested these things for myself and posted it from my own experience, if you point the finger at me for whatever happens to your device, I will laugh at you.
HOWEVER, I am willing to help as long as it is asked kindly, and provided me with enough information.
Requirements:
Huawei P8 Lite ALE-L21 (DUAL-SIM)
5.0 Firmware of choice
Unlocked bootloader
Patience
Correct drivers
SD card of atleast 8 GB
Drivers: Install these before even starting!
Minimal ADB Fastboot drivers
Huawei HiSuite
Kingoroot Windows
TWRP 3.0.2.0 Kirin variant
Preparing environment: Making sure no admin priveledge is necessary
Install all drivers mentioned above in their standard directories, don't change anything.
Go to the following path:
Code:
For x64 OS:
C:\Program Files (x86)\Minimal ADB and Fastboot
For x86_32 OS:
C:\Program Files\Minimal ADB and Fastboot
Copy these files:
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
And paste them on the desktop, in a folder called "rootingtools" so you're easily able to find it.
Then, go to your phone and enable USB debugging mode by going to
settings - about phone - press Build number 7 times
settings - developer options - USB debugging
Copy the content of "TWRP-3.0.0-2_P8-lite_KIRIN_variant.zip" and paste it into the "rootingtools" folder.
Backing up: Even though the unlocking process is not going to wipe your data, atleast it didn't for me, make SURE you have everything that you need backed up from the phone's internal memory.
Backing up your SD card wouldn't hurt neither.
First things first, unlock your bootloader!
I used this: https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
What you do is: fill in everything correctly and get the number at the end. It should be something in the words of:
Code:
Your unlocking password is: XXXX XXXX XXXX XXXX
(X resembles numbers, 16 numbers in total)
Copy the 16 numbers and go to the "rootingtools" folder on your desktop.
Hold the SHIFT key and right click inside the folder, then press "open command window here"
Now take your phone, power it off and power it on by holding volume DOWN and POWER.
You will get a white screen that says something like fastboot, and an android logo.
Plug your phone into the PC via USB cable.
In the command window write:
Code:
fastboot.exe oem unlock UNLOCKKEY
Where UNLOCKKEY represents the key you just copied, right clicking pastes the key in the command window.
It should return finished, so now your phone should be unlocked!
If you look at the screen, there will be text beneath the green Android logo saying "unlocked".
In this case, the operation has succeeded and you can go to the next step, else you can try again or post a reply.
Now write:
Code:
fastboot.exe reboot
Now the phone will boot up like normal.
Close the command window.
Android 5.0:
If your android version right now is Android 5.0, and you actually WANT to root 5.0 or anything below 6.0 you can proceed with this step, if you have 6.0 or want to root 6.0, skip this step.
Since your android version is 5.0 you're blessed!
You can easily root, but before proceeding you might want to make a backup
Make sure you have about 8GB of free storage either on an SD card or internal memory first.
Connect your phone to your PC in the booted-up state where you can see the homescreen, making sure that USB debugging is enabled.
Shift + right click inside the rootingtools folder to open a command window and write:
Code:
adb.exe reboot-bootloader
Your phone will reboot into the bootloader, a white screen with a green Android logo that says "unlocked" beneath it.
Now on the command window write:
Code:
fastboot.exe flash recovery recovery.img
Wait for it to finish and pull out the USB cable so it is NOT attached.
Power off the device by holding the power button, and power up by pressing volume UP + POWER.
Keep holding volume up until you see the Team Win logo.
Just slide the slider to the right.
Now go to "backup" and check every partition available.
In "name" you write:
Code:
MainBackupURTD
Then, go to the "options" tab and enable compression.
Go back to the "backup" tab and press "select storage".
From here you can choose where to back your data up, whether it be the internal storage or external SD card.
Press OK and swipe the slider to the right to start backing up.
Plug your phone in to make sure it doesn't power off during backing up, this process takes a while and you should let it do its thing.
When done, press "reboot system", your phone will reboot.
Let it fully start up.
Then, run Kingoroot on your PC.
Meanwhile, download the "SuperSU" app from the Play store.
Press the big "ROOT" button in Kingoroot and press "cancel" on every app your phone tries to install.
That way you will not install Kingoroot but SuperSU.
It will say "succeeded".
Now you can go on your phone and open the SuperSU app.
It will ask for an upgrade, press OK and go further with the normal installation (not the TWRP/CWM installation).
Let it do its thing and restart your phone.
Install any root checker and see if you're rooted!
Android 6.0:
Firmware version B188 or higher, below B524/B535 (excluding B524/B535):Upgrade firmware to this one: mega:///#!OBVU3RyT!gSDNFMVtWVqA1HyneCuofhFmVVJ6lUDonzfKzjucbFs
Installation instructions: place file to the "dload" folder in your SD card or internal storage, then go to settings - updates - menu - local update and press the update.zip.
Then, follow the guide reported here: http://rootmygalaxy.net/root-huawei-p8-lite-android-marshmallow-6-0-update/
Enabling Gyro sensor (rooted android 6.0, B524/B535 firmware only! ( sorry :[ ) ):
Download attached file.
Put attached file to SD card.
Open ES file explorer, swipe to the right, enable root browser and click the R/W tab, then set /system as RW.
Then copy the attached file.
Paste the attached file in /system/etc/permissions
Press the search button and search for "gyro" without quotation marks.
Long press the only file that's there - menu and press properties.
Then change the permissions to 644, it should look like this O represents off, X represents on;
X X O
X O O
X O O
Set UID is off, Set GID is off, Sticky bit is off.
Reboot phone and download "Sensor box for Android" on the Play store and enjoy your gyroscope!
Now you can use Google Cardboard, though you have to install the APK...
You can watch 360 videos on youtube too.
Click to expand...
Click to collapse
Android B560 will update from b170
---------- Post added at 09:50 AM ---------- Previous post was at 09:40 AM ----------
eriuzz said:
just trying to unlock the bootloader i have my code from huawei and when i try to use it through adb appear that error i said
Click to expand...
Click to collapse
you got to test everything. from changing usb port to changing usb cable. htc is a brand that has this problem alot. and until now there's no right answer.
search around a little.
I'm stupid. I posted on the wrong thread, sorry.
Edit: delete
I have android 6.0 firmware B311 and it doesn't show up the option local update, what should I do?
Attach pictures please
Its in portuguese, I had the option on the stock ROM but i don't have it now.
Should I downgrade to the firmware B300 and then install the new firmware?
do you think this works with ALE-L21 single sim too?
Teixaz said:
I have android 6.0 firmware B311 and it doesn't show up the option local update, what should I do?
Click to expand...
Click to collapse
Local update option has been removed from Marshmallow, you must use *#*#2846579#*#* and go to sd card upgrade to further upgrade it
amageek said:
Local update option has been removed from Marshmallow, you must use *#*#2846579#*#* and go to sd card upgrade to further upgrade it
Click to expand...
Click to collapse
Does not work when its inside the zip and if I extract it when it start to install it fails
anyone?
Please help. I have 5.0.1 Android
So When you say " we are blessed", do we only do that 5th step or all the steps before that and then 5th step?
I am asking because im havin trouble unlocking bootloader. Nobody from Huawei is answering my email where I sent them all neccecary data, and when I go to this link It says there is a server problem. Either that or Im redirected to some site filled with japanese signs http://www.vmall.com/ and I dont know what to press
How do I unlock my bootloader?? What e-mail do I use to contact huawei about this matter?
Thanks
Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix
Greetings fellow Black Shark users!
This guide is made for Black Shark 3 Pro Global version, but in theory it should work with any version if the bootloader is unlocked.
Warning: Before you start, backup your phone data as this would wipe your phone!
Do this at your own risk, I'm not responsible if you break your phone!
Prerequisites:
- Update your phone to the latest version possible.
- Download ADB, BOOTLOADER UNLOCK TOOL & TWRP Installer for Black Shark 3 Pro Global or Black Shark 3 Global.
On Phone:
1- Enable Developer Options. (Go to Settings, then About Phone, then Tap on Build number 7 times, then enter your password if needed)
2- Enable OEM unlocking. (Go to Settings, then Additional Settings, then Developer Options, then enable OEM unlocking option, then enter your password if needed)
3- Enable USB Debugging. (Go to Settings, then Additional Settings, then Developer Options, then enable USB Debugging option)
On PC:
4- Run BS3Pro_by_KM Installer. (Use the right version for your device. Right click and choose run as administrator. On driver installation popup click Next, then Install and Finish. Also Install dotNet3.5 if it ask for it. You must reboot your PC after the installation.)
5- Connect your Phone to PC using USB cable.
On Phone:
6- When Allow USB debugging popup appear, tap OK. (Tick Always allow from this computer)
On PC:
7- Make sure google drivers installed correctly and that your PC can see your Phone. (Android ADB Interface)
8- Open Command Prompt as administrator. (Type CMD in Windows search bar, then right click on Command Prompt ‘cmd’ and click on Run as administrator)
9- In CMD type:
Code:
cd c:\adb
Then press Enter key.
10- In CMD type:
Code:
adb devices
Then press Enter key. (If you can see a Device ID with ‘device’ written on its right, then continue to next step, if not then recheck your drivers. If you see a Device ID with ‘unauthorized’ written on its right, then go back to step 6)
11- In CMD type:
Code:
adb reboot edl
Then press Enter key. (To enter EDL mode)
On Phone:
12- You will only see a black screen on your phone. (This is normal, but your phone will be connected to your PC)
On PC:
13- Disconnect and reconnect your Phone to PC using USB cable then make sure the drivers are installed correctly and that your PC can see your Phone. (Qualcomm HS-USB QDLoader 9008)
14- Go to C:\adb and run MiFlash application, then click “refresh”. (You should see your device in the table now)
15- Click “select” and choose “C:\adb\Unlock” folder, then click “OK”, then click “flash”. (When it says done go to next step)
On Phone:
16- Disconnect the USB cable from your Phone, then hold power button and volume down button for 15 seconds until the phone reboots into Fastboot mode.
17- Make sure you see Fastboot mode on your phone screen. (With big green START on top)
On PC:
18- Reconnect your Phone to PC using USB cable then make sure google drivers installed correctly and that your PC can see your Phone. (Android Bootloader Interface)
19- In CMD type:
Code:
fastboot devices
Then press Enter key. (If you can see a Device ID, then continue to next step, if not then recheck your driver setup)
20- In CMD type:
Code:
fastboot flashing unlock
Then press Enter key. (This will unlock the bootloader, if you see an error make sure that your model is supported)
21- In CMD type:
Code:
fastboot erase userdata
Then press Enter key. (This will wipe userdata “Factory Reset”)
22- In CMD type:
Code:
fastboot getvar current-slot
Then press Enter key. (This will show you which slot you’re currently using, note it down)
23- In CMD type:
Code:
fastboot boot twrp.img
Then press Enter key. (This will boot TWRP, if it doesn’t work the first time, then force reboot your phone and repeat steps 16-21, you can skip step 20-22 if you already performed them)
On Phone:
24- Make sure TWRP is booted on your phone.
On PC:
25- In CMD type:
Code:
adb pull /dev/block/bootdevice/by-name/boot_a stock_boot_a.img
Then press Enter key. (This will copy the stock boot_a.img into your current directory)
26- In CMD type:
Code:
adb pull /dev/block/bootdevice/by-name/boot_b stock_boot_b.img
Then press Enter key. (This will copy the stock boot_b.img into your current directory)
On Phone:
27- In TWRP, go to Reboot, then system.
28- Download and install Magisk Manager from here. (Once the phone is booted correctly)
On PC:
29- In CMD type:
Code:
adb push stock_boot_X.img /sdcard/Download
Then press Enter key. Change ‘X’ to your current slot from step 22, mine was ‘stock_boot_a.img’. (This will copy your stock boot.img to your phone’s Downloads directory)
On Phone:
30- Run Magisk Manager, tap on the first INSTALL button on the top right, when it asks you to Install Magisk tap INSTALL, then tap on Select and Patch a File, and choose your stock_boot_X.img from ‘Download’ directory. When it’s done it will create a new file in your ‘Download’ directory named magisk_patch.img. (Don’t tap Reboot, just tap back and close the App)
On PC:
31- In CMD type:
Code:
adb pull /sdcard/Download/magisk_patched.img
Then press Enter key. (This will copy the patched boot.img to your current ‘adb’ directory)
32- In CMD type:
Code:
adb reboot bootloader
Then press Enter key. (To enter Fastboot mode)
33- In CMD type:
Code:
fastboot flash boot_x magisk_patched.img
Then press Enter key. Change ‘X’ to your current slot from step 22, mine was ‘boot_a’. (This will flash Magisk to your boot)
34- In CMD type:
Code:
fastboot reboot
Then press Enter key. (This will reboot your phone)
On Phone:
35- Run Magisk Manager, check if Magisk is installed and you have two green ticks on the left.
Congratulations! Now you have successfully rooted your Black Shark 3 Pro !
Fingerprint Calibration Tutorial (This is needed if the fingerprint sensor is stopped working)
1- Dial this from your phone
Code:
*#*#466349#*#*
This will take you to the fingerprint calibration page.
2- Tap on 售后校准, then you will be ask you to add the FLASH FLA.
3- Now tap START, and then immediately press your thumb on the fingerprint scanner area, keep you finger pressed until the step is completed.
4- Now it will ask you to add the black FLAT. (This means you have to wear a 'black' cloth on your thumb or a black glove before pressing your thumb on the fingerprint scanner, then hold your thumb on the fingerprint scanner area until the calibration is complete.)
5- When done successfully, reboot your device then try to add your fingerprints.
Full OTA Factory Image for Black Shark 3 Pro Global “MBU-H0" - Fix most phone's issues and restore it to factory state. This also fixes OTA updating issues.
1- Download this zip file MOBS2005121OS00MP1.
2- Rename km_update.zip to update.zip and move it to “ota” directory in your phone.
3- Dial this from your phone
Code:
*#*#1027#*#*
Then press "LOCAL UPDATE" and start updating your device. (You might need to do this twice)
4- Update your device to the latest version from the settings.
Special thanks to:
@John Eveline for the Bootloader Unlocking Tools.
@wzsx150 for Black Shark 3 Pro TWRP.
@topjohnwu for Magisk.
@Snoop05 for ADB Installer Code.
PS: I put a lot of time and effort in making this guide, if you want to copy it to somewhere else, then at least give credit!
miflash keep says no fastboot
cant recognize my phone
rowihel2012 said:
miflash keep says no fastboot
cant recognize my phone
Click to expand...
Click to collapse
Please redownload it, it should work fine now.
KM7 said:
Please redownload it, it should work fine now.
Click to expand...
Click to collapse
Ok thanks my friend
KM7 said:
Please redownload it, it should work fine now.
Click to expand...
Click to collapse
same problem
no fastboot
all drivers installed
rowihel2012 said:
same problem
no fastboot
all drivers installed
Click to expand...
Click to collapse
Try downloading it again, sorry for this a file was misplaced. Fixed now.
KM7 said:
Try downloading it again, sorry for this a file was misplaced. Fixed now.
Click to expand...
Click to collapse
sorry bro
no fastboot
it cant detect my phone
same problem
when i try to unlock the bootloader
i got an error : the write timed out
rowihel2012 said:
sorry bro
no fastboot
it cant detect my phone
same problem
Click to expand...
Click to collapse
Make sure the drivers are installed correctly and reboot your PC. I've just tried it and everything work just fine on my PC.
stark7i said:
when i try to unlock the bootloader
i got an error : the write timed out
Click to expand...
Click to collapse
You mean in MiFlash or Fastboot? please specify which step # you are stuck in.
KM7 said:
You mean in MiFlash or Fastboot? please specify which step # you are stuck in.
Click to expand...
Click to collapse
i am stuck at step 13. the miflash cant find my phone. i have re-downloaded everything and still doesnt work. any suggestions?
appless said:
i am stuck at step 13. the miflash cant find my phone. i have re-downloaded everything and still doesnt work. any suggestions?
Click to expand...
Click to collapse
Make sure your drivers are installed correctly as shown above. When in edl mode the drivers are different than fastboot. Try reinstall the application with right click and ‘run as administrator’.
Do you know how to relock the bootloader?
KM7 said:
You mean in MiFlash or Fastboot? please specify which step # you are stuck in.
Click to expand...
Click to collapse
its was in the miflash but it works fine now i have changed my usb cable to an original one and it works fine , i have successfully rooted my BS3 with TWRP thanks alot
KM7 said:
Make sure your drivers are installed correctly as shown above. When in edl mode the drivers are different than fastboot. Try reinstall the application with right click and ‘run as administrator’.
Click to expand...
Click to collapse
still a no go for me. i have reinstalled every driver and still doesnt work. nothing is showing up on miflash. the pc made the sound when i connected but still nothing. my pc sees the device but the miflash cant. any suggestions?
appless said:
still a no go for me. i have reinstalled every driver and still doesnt work. nothing is showing up on miflash. the pc made the sound when i connected but still nothing. my pc sees the device but the miflash cant. any suggestions?
Click to expand...
Click to collapse
Use your original usb cable from blackshark. Mine works and use other cable wont work..
chaict said:
Use your original usb cable from blackshark. Mine works and use other cable wont work..
Click to expand...
Click to collapse
using the original cable still doesnt work. now its just saying no fastboot.
stark7i said:
its was in the miflash but it works fine now i have changed my usb cable to an original one and it works fine , i have successfully rooted my BS3 with TWRP thanks alot
Click to expand...
Click to collapse
Glad that it worked for you, enjoy.
appless said:
using the original cable still doesnt work. now its just saying no fastboot.
Click to expand...
Click to collapse
It seems that there is something wrong with the drivers, or maybe the adb installation. Try to find other fastboot.exe and adb.exe then delete all duplicates except for "C:\adb", and don't forget to restart your PC.
jekz_07 said:
Do you know how to relock the bootloader?
Click to expand...
Click to collapse
This should do it but, I'm not sure if this is going to work on a rooted device.
Code:
fastboot flashing lock_critical
fastboot flashing lock
Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
{
"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"
}
Your main window should look like this:
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!
For whatever reason, my devices isn't showing up when writing "fastboot devices" but shows up in QFIL. Any suggestions?
Joncka said:
Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
View attachment 5741653
Your main window should look like this:
View attachment 5741651
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!
Click to expand...
Click to collapse
I got one with the "GLOBAL ROM" which miss a lot of feature so I follow this tutorial to flash the stock rom and works like a charm.
The only question is why I can't get any OTA?
Due to te unlocked bootloader?
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.
Ale_ax said:
I got one with the "GLOBAL ROM" which miss a lot of feature so I follow this tutorial to flash the stock rom and works like a charm.
The only question is why I can't get any OTA?
Due to te unlocked bootloader?
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.
Click to expand...
Click to collapse
Yes, this one is weird. Some people are able to lock it, and some are not.
To my understanding you need to lock it to get OTA's. It's still possible to update, though, through downloading the newer update and installing the update in .zip format on stock ROM.
Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?
Ale_ax said:
Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?
Click to expand...
Click to collapse
See if you can find the right incremental updates here: https://drive.google.com/drive/u/0/mobile/folders/1BZuFF4ZwYHCjIWua-INiEFe1YItjAYz2
I'm on crDroid, I just flashed from the standard 13.0.586 ROM.
Joncka said:
See if you can find the right incremental updates here: https://drive.google.com/drive/u/0/mobile/folders/1BZuFF4ZwYHCjIWua-INiEFe1YItjAYz2
I'm on crDroid, I just flashed from the standard 13.0.586 ROM.
Click to expand...
Click to collapse
Thank you, btw they are for the "TB-J716F" Xiaoxin pad pro 2021n, Legion Y700 is "TB-9707F"
Ale_ax said:
Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?
Click to expand...
Click to collapse
hi, in my case after fresh flash to zui 13 official i can use ota to zui 14 even the tablet in unlocked state, someone in xiaoxin pad pro thread suggested using vpn 'returness' set to china (shanghai 11) i think... and ota did works, zui 14 is about 3 half gig so i ended up using link from y700 thread to install manually
Just for anyone else having trouble getting into EDL mode (my Y700 wasn't bricked, I just wanted to restore stock rom):
When the tablet is running normally, go to developer options, enable USB debugging, then go to the platform-tools folder on your PC and open a command prompt there, then type "adb reboot edl". Then you'll see the "Qualcomm HS-USB QDloader 9008 (COMxx)" Port under Ports in Device Manager.
To re-lock, I believe you can use these instructions. The command "fastboot flashing lock" brought up the menu on the Y700 screen to re-lock, but I didn't do it because I didn't want to delete my user data (I'd just spent time setting up all my apps!)
When I was in fastboot, the tablet was showing up with an exclamation point and just called, "Android device" in Device manager, I used the drivers from here to get it to show up as "Android Bootloader Interface".
Don't do what I just wrote!! I did it and now I'm stuck and it won't boot, and I can't get to EDL mode.
I don't have time to work on it now but my tablet is effectively bricked.
I'm in a bootloop to the fastboot screen, and it shows up in Device Manager as "Android Bootloader Interface". I can't flash in QFIL as described above because it just says "No Port Available". I can't get to EDL mode as I did before because I can't boot the tablet as usual to enter the "adb reboot edl" command.
"adb devices" doesn't show the Y700.
Can anyone tell me how to get to EDL mode when I can't get adb to work?
Ale_ax said:
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.
Click to expand...
Click to collapse
That's what happened to me! How did you get it back into EDL mode after unlocking?
Mine isn't showing the Qualcomm device under Ports in Device Manager anymore, so I can't get the port to show in QFIL!!
Got it to work getting to EDL mode, phew!
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
Click to expand...
Click to collapse
This got the Qualcomm port to show up again.
So I'm now running the stock rom but still unlocked so no OTA. What a waste of time that was.
Hoping someone can work out how to re-lock.
shahrul5689 said:
hi, in my case after fresh flash to zui 13 official i can use ota to zui 14 even the tablet in unlocked state, someone in xiaoxin pad pro thread suggested using vpn 'returness' set to china (shanghai 11) i think... and ota did works, zui 14 is about 3 half gig so i ended up using link from y700 thread to install manually
Click to expand...
Click to collapse
Yep, I can get ota with that vpn
gnoted said:
Got it to work getting to EDL mode, phew!
This got the Qualcomm port to show up again.
So I'm now running the stock rom but still unlocked so no OTA. What a waste of time that was.
Hoping someone can work out how to re-lock.
Click to expand...
Click to collapse
you have to use Chinese vpn, it’s not because of unlocked booloader, I will link you the one I used later, btw no need to relock bootloader, for getting ota
Ale_ax said:
Yep, I can get ota with that vpn
you have to use Chinese vpn, it’s not because of unlocked booloader, I will link you the one I used later, btw no need to relock bootloader, for getting ota
Click to expand...
Click to collapse
Haha, maybe I should read more of the comments before assuming things.
Hic, I just got a second hand Y700, it had an original Zui 13 chinese rom, and I started to OTA update upto ZUI 14. Then the Google Play disappeared, also the PC mode. I tried to downgrade to ZUI 13 with this guide WITHOUT enabling usb debugging nor oem unlock. The flashing process succeeded, but when the tablet reboots, it shows for the first time "Your device is corrupt, It can't be trusted and will not boot", after that keeps showing bootloader menu.
Please help me what to do from this step?
I'm in a different state from others here, I think; my Y700 appears to be totally bricked. It's plugged in to charge and nothing's happening at all. I originally installed crDroid on it, but ran into Widevine issues and was going to revert. I don't remember the last steps I took on it (it was a month or so ago), but when I picked it up again a few days ago, turning it on showed only a black screen (only detectable by seeing the backlight), so I let it discharge the battery entirely planning to try and fix it via reflash later. Now, however, it's doing... nothing.
I'm going to let it charge overnight and see if that changes anything, but if anybody has ideas what might have happened or things to try to get out of this, I'd appreciate it!
Hi, I'm stuck after flashing the Chinese stock rom on my legion y700. I was first successful except for upgrades which were proposed and installed but wouldn't show after reboot. I decided to flash again hoping that would solve the problem. But now my tablet remains in EDM mode and won't start. The final message in Qfil was 'download successful'. It is fully charged
Any idea on how to solve this issue?
I am in yet another state. I only run Linux (Mint 21), and have not been able to get any version of wine working, so I cannot use QPST or QFIL (windows .exe's). I CAN access my Y700 via adb or fastboot, and it is now unlocked. It was unsealed when it arrived, but does NOT have any google stuff on it.
I have downloaded all of the components needed from apkmirror, and followed instructions in the Y700 topic to activate them, to no avail.
Sadly, since I do not read Chinese, and the use requirement needs google, it might as well be a brick.
Further, despite more than 40 years doing technical support on all sorts of computers, I have never yet flashed an android device. Can it be done from adb or fastboot? If so, how do I specify which partition to flash? Does anyone have a guide to help me get started? I wish to put cdroid on it, do I use the .xz file or extract the .img?
OK, I've just found something I missed, but it doesn't work for me. My terminal is in the same folder as the .img
fastboot flash boot crDroid-8.10-arm64_bgN-Unofficial.img
Sending sparse 'boot_b' 1/15 (262088 KB) OKAY [ 8.186s]
Writing 'boot_b' FAILED (remote: 'Value too large for defined data type')
fastboot: error: Command failed
What am I missing (apart from a brain!) is this the correct partition to write crDroid to? is there an option to set the data type size? if so what?
Joncka said:
Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
View attachment 5741653
Your main window should look like this:
View attachment 5741651
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!
Click to expand...
Click to collapse
A lot of this does not seem to work on Linux (Mint 20.3).
fastboot flashing unlock
worked for me, and while I have no problem getting into recovery or fastboot modes on my Y700, I never see anything I recognize as EDL. On a machine with 'wine' installed and working, QTSP installs and appears to run OK, as also does QFIL. I can select the "rawprogram" and "patch" files OK, but it cannot find a port.
Both adb devices and fastboot devices report the correct device when it is in the appropriate mode, and
fastboot flash system crDroid-8.10-arm64_bgN-Unofficial.img appears to have successfully flashed correctly, but it is still unable to communicate with Google servers. All good (tear hair out type) fun!