Database Users

Back to stock gone wrong

In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien

jfpesant said:
In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien
Click to expand...
Click to collapse
I'm in the same boat as you. I've tried 6 computers. 1 detects it and I can unlock/lock bootloader but fails when I try to flash stock image.The other 5 computers, when I plug it in it freezes my tab in fastboot. WTF

logan_izer10 said:
I'm in the same boat as you.
Click to expand...
Click to collapse
Welcome aboard !

in the toolkit make sure you have the right model number in the "change" section,in the back to stock section check the "cant boot up"bit,then click flash stock + unroot,works all the time for me

jfpesant said:
In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien
Click to expand...
Click to collapse
As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn. The following instructions assume some basic Windows command prompt skills.
Read all the directions before you begin and perform the steps at your own risk.
I want to assume that you have the correct drivers installed, but I wont. This and any following verbosity is not to be condescending, but rather not to assume anything. If you're certain the adb and fastboot drivers are correctly, skip to step 7.
To obtain the tools and drivers needed, download the Android SDK - http://developer.android.com/sdk/index.html
Run the SDK installer that you downloaded and follow the on-screen instructions.
Make note of the install location which defaults to: C:\Users\<user name>\AppData\Local\Android\android-sdk this is where the tools and drivers will be downloaded to. This will be referred to as your sdk directory
Note: Java SE JDK is required by Android SDK. Download and install the Java SE JDK from Oracle
Run SDK Manager.
Under Tools, check the box labeled "Android SDK Platform-tools" - this provides adb and fastboot
Under Extras, check the box labeled "Google USB Driver"
Press the "Install # Packages..." button and follow the on-screen instructions.
Install the abd driver - detailed instructions can be found at http://developer.android.com/tools/extras/oem-usb.html
Note: in order for your device to be detected, USB debugging must be enabled on the device
Once the driver is installed open a command prompt and change directories to <your sdk directory>\platform-tools (see #2). From the command prompt run "adb devices". This will list any adb-capable devices that are attached to the computer by their serial number assuming your drivers are installed correctly. Recap:
Code:
> cd \Users\<user name>\AppData\Local\Android\android-sdk\platform-tools
> adb devices
# the following output should be returned
List of devices attached
<device serial number> device
Use adb to boot the device to the bootloader:
Code:
> adb reboot-bootloader
The device should now be in fastboot mode and Windows should be attempting to install the fastboot driver. You can verify that the driver has been installed by running the following command:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
Download the factory image for Nexus 7 from https://developers.google.com/android/nexus/images#nakasi. The resulting file will have the extension .tgz. You will need something that can reliably decompress and extract files from this archive. If in doubt at all, use 7-Zip http://www.7-zip.org/download.html.
Open the archive with 7-Zip you should see a single .tar file. Open the .tar file with 7-Zip as well.
Inside the .tar file is a directory that will resemble "nakasi-jro03d". Open that directory.
Extract the contents of the "nakasi-jro03d" directory to <your sdk directory>/platform-tools. The extracted files should be as follows: bootloader-grouper-3.34.img, image-nakasi-jro03d.zip, flash-all.sh, flash-base.sh
The flash-all.sh file is a shell script that contains all the commands required to flash the factory image using the fastboot command. In order to use fastboot, we need to boot the device to fastboot mode. This can be done with adb:
Code:
> adb reboot-bootloader
In order to do anything useful, the bootloader must be unlocked. Do that like so:
Code:
> fastboot oem unlock
Follow the directions on the device, using the volume and power buttons to select "Yes".
In fastboot with your device's bootloader unlocked, run the commands listed in flash-all.sh in sequence, waiting for each command to finish. For convenience I have them here:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-3.34.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jro03d.zip
# optionally re-lock the bootloader.
# You may want to do this if you're returning the device for warranty work.
> fastboot oem lock
# finally, reboot
> fastboot reboot
That should do it.

tonybhoy said:
in the toolkit make sure you have the right model number in the "change" section,in the back to stock section check the "cant boot up"bit,then click flash stock + unroot,works all the time for me
Click to expand...
Click to collapse
Worked for me !!! Thanks bro !
(I previously have tried this, but didn't choose the right model number... so it didn't work)

comminus said:
As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn. The following instructions assume some basic Windows command prompt skills.
Click to expand...
Click to collapse
Thanks a lot for the insight. I'm all about DIY so I'll definitely give this a try next time I have to play in android.
Julien

jfpesant said:
Thanks a lot for the insight. I'm all about DIY so I'll definitely give this a try next time I have to play in android.
Julien
Click to expand...
Click to collapse
No worries, I'm glad the simpler route worked!

[HOW-TO]Unlock the Bootloader on the Nvidia Shield

Introduction
The purpose of this guide is to provide you with step-by-step instructions on how to unlock the bootloader on your Nvidia Shield.
Why Would I want to Unlock my Bootloader?
Unlocking your bootloader allows you to modify all aspects of your device to suite your needs which includes but is not limited to, installing custom Recovery images such as Clockworkmod Recovery or Team Win Recovery Project, installing custom ROM's, custom Kernels, as well as other MOD's and patches.
Will Unlocking my Bootloader Void my Warranty?
Warning: Unlocking your Nvidia Shield's bootloader will void the warranty, please note that even if you re-lock the bootloader the bootloader still show a flag that the device is voided for warranty.
This warning being given please also see this post by JordanKeyes regarding warranty information as it relates to hardware issues or hardware failures.
Unlocking your Bootloader
1. Backup everything on your device that you don't want to loose such any apps (And there respective data), pictures, videos, music, etc. as unlocking your devices bootloader will erase all data on the device. You can fully backup your devices contents without root using ADB's backup command or by using the Holo Backup Tool.
2. Download and install the ADB and Fastboot drivers for your Shield, the drivers can be downloaded here. You can also follow along with wwjoshdew's excellent video tutorial on how to properly install the ADB and Fastboot drivers for your Shield on Windows.
3. Make sure you have ADB and Fastboot setup and installed on your computer. If you haven't already setup and installed ADB and Fastboot a simple ADB and Fastboot installer can be downloaded from here.
4. Fully power off your Shield by long pressing on the Power button until the power menu appears, then select the "Power off" option.
5. Boot your Shield into Fastboot mode using one of the following ways:
5. A. Power on your Shield while simultaneously holding the Power button + Back button + Home button. Release the buttons once the Fastboot bootloader screen appears.
5. B. Run the following ADB command from a command prompt window (USB cable must already be connected from your Shield to your Computer):
Code:
adb reboot bootloader
6.Now that you are at the Fastboot bootloader screen, connect your Shield to your computer using your USB cable. Make sure that your USB cable is plugged into a USB 2.0 port directly connected to your motherboard as sometimes USB 3.0 ports can cause problems and front panel USB connections can be unreliable.
7. Open up a command prompt window (cmd) in the directory where installed ADB and Fastboot to. For example if I installed ADB and Fastboot to a folder on my Desktop which is on my D: drive I would open a command window in "D:\Desktop\Fastboot_ADB".
8. From the command prompt windows enter the following command:
Code:
fastboot devices
If you device is detected and it shows your devices serial number you are ready to move on to the next step. If no device is shown make sure you have the correctly installed the ADB and Fastboot drivers from step number 2.
9. Now that your device is detected by Fastboot the following command is used to unlock your bootloader:
Code:
fastboot oem unlock
10. You will now be presented with the bootloader unlock menu. After reading the disclaimer, use the Back button and the Home button to navigate to the "Unlock" option. Once the "Unlock" option has been highlighted use the Shield button to confirm your selection of unlocking your bootloader. It's important to remember that unlocking the bootloader will wipe all your data from the device, and that a flag showing your warranty is void will appear at the bootloader screen.
11. Once your bootloader has finished being unlocked, you will be taken back to the fastboot bootloader screen. From here you can power off your Shield.
Re-locking your Bootloader
To re-lock your bootloader you can following steps 4-8 of the procedure listed above and when you come to step 9 run the following command instead of "fastboot oem unlock":
Code:
fastboot oem lock
The above command will re-lock your Shield's bootloader. Note: As previously mentioned re-locking your Shield's bootloader will not restore your warranty or remove the warranty void flag on your device's bootloader.
Conclusion
Now that you have successfully unlocked the bootloader on your Nvidia Shield you are free to flash custom Recoveries, ROM's, Kernel's, MOD's etc. enjoy :good:.
If you are stuck with the bootloader unlocking procedure I would recommend checking out this great video tutorial by wwjoshdew.

I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Edit: followed the instructions in the following video and all is dandy now. http://www.youtube.com/watch?v=XSisjVwcPbE&hd=1

themichael said:
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Click to expand...
Click to collapse
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.

fastboot error
chevyowner said:
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
Click to expand...
Click to collapse
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.

gogul1 said:
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
Click to expand...
Click to collapse
Nvidia just released a new set of USB drivers in their Tegra for Android Development Pack which you can download from here. I would recommend installing the development pack and the drivers it includes.

ok
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148

gogul1 said:
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
Click to expand...
Click to collapse
From that pic you posted the mount command failed because you were not root.

chevyowner said:
From that pic you posted the mount command failed because you were not root.
Click to expand...
Click to collapse
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.

shimp208 said:
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
Click to expand...
Click to collapse
Huh??????????
EDIT
Were you trying to answer this post

chevyowner said:
Huh??????????
EDIT
Were you trying to answer this post
Click to expand...
Click to collapse
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!

shimp208 said:
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
Click to expand...
Click to collapse
No problem.
I had to change to oil in my car in a parking lot earlier because it was cheaper to change it then it would have been add 3-4 quarts and change it when I got home. My car need 5 quarts of oil. I was not in a a good mood then.

I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs

thx. works nice.

wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: [
How To Root the Nvidia Shield: []
Click to expand...
Click to collapse
Sweet thanks

wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Click to expand...
Click to collapse
I tried another proggie to root and got jammed up.. following the videos josh did had me rooted in minutes. Great job and thanks!

why?
Code:
C:\Users\Thomas>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I tried it with the Shield RAM tool, but won't work either..

so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.

mr.dude5660 said:
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
Click to expand...
Click to collapse
Where did you find the towelroot apk? Been searching for over a month with no success.
Sent from my VS980 4G using Tapatalk

BTW, bootloader mode on the tablet:
- Hold "Volume Down" -> Press "Power" and continue to hold "Volume Down" until device boots into bootloader mode.
There is no home or back button to press while the device is off.

Sorry for bump this thread, but i have to.
I want to unlock my bootloader to revert back into KK and then try to do a clean installation of LP. Reading this guide and watching the videos, and also looking into the img downloaded from nvidia, it says i have to install the fastboot drivers. The problem is that i have already installed fastboot and adb drivers since i have some other devices as a Xperia and stuff. For me, there is no Yellow sign as shown in the video, my device is recognized as Portable Device and it already says "Shield Tablet" MTP.
I've tried going into bootloader to see if it prompts any new devices but i got nothing. adb devices show my device, but i'm not sure if i need more.

Stock Nexus 7 (2012) soft bricked

Hello all this is my first post here, please be nice
I have absolutely no knowledge of computing/ IT, but after tearing my hair for the past two days (and a lot of googling) I have come here hoping for a solution
I have a stock nexus (see I have learnt new terms) which is now soft bricked and stuck on the X screen
Been looking for solutions including nexus root kit but none have really helped
eg one solution says step 1: install latest android SDK (and in the process of installing I have to ensure usb debugging is turned on, too late already soft bricked)
I am assuming that I have failed because
I have not rooted the device
I have not enabled usb debugging
I have not enabled changes previously eg unlocking
I am however able to enter bootloader mode
I have cleared cache partition and also tried to factory reset but to no avail
Could some one please please help me as it is out of warranty

docians said:
Hello all this is my first post here, please be nice
I have absolutely no knowledge of computing/ IT, but after tearing my hair for the past two days (and a lot of googling) I have come here hoping for a solution
I have a stock nexus (see I have learnt new terms) which is now soft bricked and stuck on the X screen
Been looking for solutions including nexus root kit but none have really helped
eg one solution says step 1: install latest android SDK (and in the process of installing I have to ensure usb debugging is turned on, too late already soft bricked)
I am assuming that I have failed because
I have not rooted the device
I have not enabled usb debugging
I have not enabled changes previously eg unlocking
I am however able to enter bootloader mode
I have cleared cache partition and also tried to factory reset but to no avail
Could some one please please help me as it is out of warranty
Click to expand...
Click to collapse
flash factory image via fastboot, since you can access bootloader and already install adb debugging.. follow step 6 (6.you can verify...) onward from this post http://forum.xda-developers.com/showthread.php?p=32075129
Sent from my Nexus 7

usb debugging
dexviajiboy said:
flash factory image via fastboot, since you can access bootloader and already install adb debugging.. follow step 6 (6.you can verify...) onward from this post http://forum.xda-developers.com/showthread.php?p=32075129
Sent from my Nexus 7
Click to expand...
Click to collapse
Unfortunately I do not have usb debugging enabled
And my tablet is soft bricked
Is there a way around this?
Please any help is appreciated
thanks

Try this from youtube. I have also softbrick my nexus when ota to kitkat. Use this methods and it works. Also before flash the factory image, unlock your bootloader first. I think this method did not required to enable usb debuging.
http://m.youtube.com/watch?v=-E-EF0QC0Gc
I hope this will help
Sent from my Nexus 7 using xda premium

You don't need usb debugging enabled to flash images via fastboot -- you just need to be able to get into the bootloader screen.

unlock bootloader
deny_kei said:
Try this from youtube. I have also softbrick my nexus when ota to kitkat. Use this methods and it works. Also before flash the factory image, unlock your bootloader first. I think this method did not required to enable usb debuging.
I hope this will help
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the video
I have followed everything until it (the video) tells me that the process will only work if I unlock my bootloader
Now I can access my bootloader but it states Lock State- Locked
My difficulty is how do I unlock my bootloader as my nexus is stuck at boot loop
I have tried the unlock function on Rootkit, but it says I have to enable usb debugging
To summarise my understanding:
My nexus will get out of bootloop if I flash the ROM
To flash the ROM I have to unlock the bootloader (as per the video)
To unlock the bootloader I have to enable usb debugging (as per nexus root kit)
To enable usb debugging I have to get out of bootloop
To get out of bootloop I have to flash the ROM............
Any simple way of unlocking the bootloader on a soft bricked nexus?
Any help appreciated thanks

like jfmcbrayer said.. if you can access bootloader, you can flash via fastboot either you enabled or not usb debugging, the important thing fasboot can verify your device before start flashing..
Sent from my Nexus 7

bootloader locked
dexviajiboy said:
like jfmcbrayer said.. if you can access bootloader, you can flash via fastboot either you enabled or not usb debugging, the important thing fasboot can verify your device before start flashing..
Sent from my Nexus 7
Click to expand...
Click to collapse
Absolutely agree
However when I try to follow your instructions
> fastboot devices
# the following output should be returned
<device serial number> fastboot
I do not get a device serial number
I suspect it is because the bootloader is locked, the device will not be recognised
Happy to be proven wrong because I need a means to get my nexus working

docians said:
Absolutely agree
However when I try to follow your instructions
> fastboot devices
# the following output should be returned
<device serial number> fastboot
I do not get a device serial number
I suspect it is because the bootloader is locked, the device will not be recognised
Happy to be proven wrong because I need a means to get my nexus working
Click to expand...
Click to collapse
seen like you got problem with adb driver on you pc..
Sent from my Nexus 7

adb driver
dexviajiboy said:
seen like you got problem with adb driver on you pc..
Sent from my Nexus 7
Click to expand...
Click to collapse
Indeed! Perhaps because the first step in installing an adb driver in my pc is this:
1. Enable usb debugging on your device (found under Settings > Developer Options)
As I have been saying from the start
My nexus is stuck in boot loop
I do not have usb debugging enabled
Is there anyone who can help me with unlocking my bootloader (on my soft bricked stock nexus) so I can flash rom
Thanks in advance

docians said:
Indeed! Perhaps because the first step in installing an adb driver in my pc is this:
1. Enable usb debugging on your device (found under Settings > Developer Options)
As I have been saying from the start
My nexus is stuck in boot loop
I do not have usb debugging enabled
Is there anyone who can help me with unlocking my bootloader (on my soft bricked stock nexus) so I can flash rom
Thanks in advance
Click to expand...
Click to collapse
goodluck ?
Sent from my Nexus 7

bricked
dexviajiboy said:
goodluck ?
Sent from my Nexus 7
Click to expand...
Click to collapse
thanks bud
I will need all the luck in the world now that I have to deal with Asus/ google now that the tablet is out of warranty

docians said:
thanks bud
I will need all the luck in the world now that I have to deal with Asus/ google now that the tablet is out of warranty
Click to expand...
Click to collapse
dont you try flash factory with guide from this thread http://forum.xda-developers.com/showthread.php?t=1907796
pm me with part you stuck.. I'll try assist you

soft brick
dexviajiboy said:
dont you try flash factory with guide from this thread http://forum.xda-developers.com/showthread.php?t=1907796
pm me with part you stuck.. I'll try assist you
Click to expand...
Click to collapse
just to be absolutely sure were on the same page I've copied all the instructions from your link
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Notice: If you are going to flash the nakasi android 4.3 JWR66Y factory image, you will need to download the bootloader from JWR66V and replace the one from the factory image. The bootloader in JWR66Y will fail flashing with a signature mismatch error on the device and InvalidState on fastboot.
The objective of this thread is to provide detailed instructions on flashing a factory image using fastboot rather than a toolkit. As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn about the process. The following instructions assume some basic Windows command prompt skills.
Read all the directions before you begin and perform the steps at your own risk.
Overview
This will restore your Nexus 7 to it’s factory state. All user data will be deleted, so now is a good place to stop and backup anything you don’t want to lose.
This guide is in three parts - basic knowledge and obtaining the required software, driver installation, and flashing the factory image. This and any following verbosity is not to be condescending, but rather not to assume anything.
Basic Knowledge
This guide assumes some basic Windows command prompt skills - changing directories, etc and is written primarily for Windows users. Make sure that you have file extensions enabled in Windows Explorer.
Software Requirements•Android SDK - adb, fastboot, usb drivers
•Java SE Development Kit - required by Android SDK
•A Nexus 7 factory image
•7-Zip - used to extract factory images from a .tgz file
1.Download and install 7-Zip - http://www.7-zip.org/download.html
2.Download the Nexus 7 factory image - https://developers.google.com/androi.../images#nakasi and save it somewhere you can easily retrieve it.
Make sure to download the correct image for your device variant (Wi-Fi vs GSM/HSPA+; nakasi vs nakasig)
3.Download and install the Java SE JDK - http://www.oracle.com/technetwork/ja...ads/index.html
4.Download and install the Android SDK - http://dl.google.com/android/installer_r21-windows.exe
5.NOTE: Notice the install location. This defaults to C:\Users\<user name>\AppData\Local\Android\android-sdk the platform tools (adb, fastboot) and usb drivers will be downloaded to this location. This will be referred to from here on as your sdk directory
6.Run the SDK Manager
7.Under Tools, check the box labeled "Android SDK Platform-tools" - this provides adb and fastboot
8.Under Extras, check the box labeled "Google USB Driver"
9.Press the "Install # packages..." button and follow the on-screen instructions.
10.The platform tools will be installed at <your sdk directory>\platform-tools and the usb drivers will be in <your sdk directory>\extras\google\usb_driver
Driver Installation
This seems to be the most confusing part for many people. Be patient and thoroughly read all the instructions.
Huge thanks to @tetakpatak for taking the time to put together a video showing this process! http://www.youtube.com/watch?v=bhA5C...yer_detailpage..
1.Enable usb debugging on your device (found under Settings > Developer Options)
NOTE: Since Android 4.2 the Developer Options are hidden by default.
To enable them, go to Settings > About Phone, and tap on build number around seven times. A small dialog will appear letting you know "You are now a developer!"
2.Install the abd driver - detailed instructions for installing or upgrading and existing driver on your version of Windows can be found at http://developer.android.com/tools/extras/oem-usb.html
3.Once the driver is installed open a command prompt and change directories to <your sdk directory>\platform-tools (see #2). From the command prompt run "adb devices". This will list any adb-capable devices that are connected to the computer by their serial number assuming your drivers are installed correctly. Recap:
Code:
> cd \Users\<user name>\AppData\Local\Android\android-sdk\platform-tools
> adb devices
# the following output should be returned
List of devices attached
<device serial number> device
4.Use adb to boot the device to the bootloader:
Code:
> adb reboot-bootloader
5.The device should now be in fastboot mode and Windows should be attempting to install the fastboot driver. NOTE: if you had drivers previously installed, you may need to upgrade them. This is the same procedure described at http://developer.android.com/tools/extras/oem-usb.html
6.You can verify that the driver has been installed by running the following command:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
7.Do not proceed further if fastboot can not recognise your device. You are in driver hell and this must be resolved before continuing.
Extract the Factory Image
In order to extract the necessary files from the factory image archive, we will use 7-Zip because it can do this reliably. At this point you should have already installed 7-Zip and downloaded the factory image archive.
1.Use 7-Zip to open the factory image .tgz file. You should see a single .tar file. Open this file with 7-Zip as well.
2.Inside the .tar file is a directory that will resemble “nakasi-jwr66y”. Open that directory and extract the contents to <your sdk directory>\platform-tools.
3.The extracted files should be as follows: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh
Flashing the Factory Image
1.Put the device into fastboot mode by running the following adb command:
Code:
> adb reboot-bootloader
2.In order to do anything useful in fastboot, the bootloader must be unlocked. To do this, run the following fastboot command:
Code:
> fastboot oem unlock
3.Follow the directions on the device, using the volume and power buttons to select "Yes". NOTE: this will wipe all personal data.
4.In fastboot with your device's bootloader unlocked, run the commands listed in flash-all.sh in sequence, waiting for each command to finish.
Follow the commands for your device variant - Wi-Fi (nakasi) or GSM/HSPA+ (nakasig). For convenience I have them here:
NOTE: you will see some messages about the archive not containing boot.sig, recovery.sig and system.sig. That is normal, dont worry.
Wi-Fi devices (nakasi)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-4.23.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jwr66y.zip
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.23.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jwr66y.zip
After the final command completes, the device will reboot.
5.If you are sending the device in for warranty work, you may want to re-lock the bootloader
Code:
> fastboot oem lock
6.Finally, reboot the device
Code:
> fastboot reboot
Click to expand...
Click to collapse
Following the thread this is precisely where I get stuck
Driver Installation
This seems to be the most confusing part for many people. Be patient and thoroughly read all the instructions.
Huge thanks to @tetakpatak for taking the time to put together a video showing this process! http://www.youtube.com/watch?v=bhA5C...yer_detailpage..
1.Enable usb debugging on your device (found under Settings > Developer Options)
NOTE: Since Android 4.2 the Developer Options are hidden by default.
To enable them, go to Settings > About Phone, and tap on build number around seven times. A small dialog will appear letting you know "You are now a developer!"
Will pm you with the same as I need your help in Driver Installation

docians said:
Following the thread this is precisely where I get stuck
Driver Installation
This seems to be the most confusing part for many people. Be patient and thoroughly read all the instructions.
Huge thanks to @tetakpatak for taking the time to put together a video showing this process! http://www.youtube.com/watch?v=bhA5C...yer_detailpage..
1.Enable usb debugging on your device (found under Settings > Developer Options)
NOTE: Since Android 4.2 the Developer Options are hidden by default.
To enable them, go to Settings > About Phone, and tap on build number around seven times. A small dialog will appear letting you know "You are now a developer!"
Click to expand...
Click to collapse
You're welcome, mate....
Installing drivers is not difficult, you must read the post by comminus carefully.
I tought it is too a boring part to film it....
@docians take your time to read step by step mate, that guide can help you to unbrick.
Guys, just be aware, that the drivers will have to be instaled two times: once for normal boot mode in OS, another time in fastboot mode.
What might confuse you: the ADB drivers get installed within the SDK and not as usual with downloaded drivers from the website of the manufacturer.

Did this end up being solved?
In the same situation where my Nexus 7 (2012) 4.4.4 is soft bricked and stuck in a bootloop.
Not sure how to go about installing the drivers. Just lost. :silly:

deanomalino said:
Did this end up being solved?
In the same situation where my Nexus 7 (2012) 4.4.4 is soft bricked and stuck in a bootloop.
Not sure how to go about installing the drivers. Just lost. :silly:
Click to expand...
Click to collapse
Yes, solved
You will find them in google, search for "google USB drivers for Windows"
Download the zip, unzip it and run the install/setup.exe
After that, boot your N7 into the bootloader mode and connect your tab with the USB cable and wait for 1 minute until it gets installed.
After that you will can execute all fastboot commands. Then just follow the guide by comminus how to flash factory image with fastboot.
tetakpatalked from N7100

tetakpatak said:
Yes, solved
You will find them in google, search for "google USB drivers for Windows"
Download the zip, unzip it and run the install/setup.exe
After that, boot your N7 into the bootloader mode and connect your tab with the USB cable and wait for 1 minute until it gets installed.
After that you will can execute all fastboot commands. Then just follow the guide by comminus how to flash factory image with fastboot.
tetakpatalked from N7100
Click to expand...
Click to collapse
Awesome, thanks.
Have run into another problem now.
Got to the part "fastboot flash bootloader bootloader-grouper-4.23.img"
And I get a message in cmd saying "FAILED <remote: <Invalid State>>"
Then on the tablet it says "Signiture Mismatch".
I'm using the 4.4.4 (KTU84P) from the Factory Images website if that's any help....

deanomalino said:
Awesome, thanks.
Have run into another problem now.
Got to the part "fastboot flash bootloader bootloader-grouper-4.23.img"
And I get a message in cmd saying "FAILED "
Then on the tablet it says "Signiture Mismatch".
I'm using the 4.4.4 (KTU84P) from the Factory Images website if that's any help....
Click to expand...
Click to collapse
Doesn't 4.4.4 image need a KitKat bootloader? Ver 4.23 was used for Jelly Bean 4.3 AMAIK
tetakpatalked from Nexus 7 flo

tetakpatak said:
Doesn't 4.4.4 image need a KitKat bootloader? Ver 4.23 was used for Jelly Bean 4.3 AMAIK
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Hmmm
Well that was the bootloader that was in the 4.4.4 download when I unzipped everything. :/
Is there meant to be another one?
Should I maybe just try and flash a Jelly Bean image onto the tablet then?
Thanks again for your help.

Root and install Custom Rom and Recovery on ZTE Open C without using Upgrade Tool

This is a guide how to root and install custom rom and recovery on ZTE Open C.
I tested it on Linux but it should work with Windows and Mac just fine.
1. Download and install Android SDK
2. Install Android SDK Tools, Android SDK Platform-tools, Android SDK Build-tools, API 19 and Google USB Driver(Windows only)
3. Download Recovery and keep it on you computer
Download Gapps and Rom and put it either on your sd card or keep it on your computer
Extract FFOS+to+Android from the rar DONT EXTRACT THE ZIP!
4. Enable external Debugging on settings>Device information>More Information>Developer>Remote Debugging
5. Connect your phone to your computer
6.
Code:
adb devices
If it shows a serial number you can skip the following and continue at step 7
If not try
Linux: type "sudo" before every command Windows:Right click on cmd and tick "Run as administrator"
If it fails try
Code:
adb kill-server
Code:
adb start-server
If it fails either try
Code:
adb shell
ctrl+c
If it fails either try to disable Remote Debugging and enable it again then repeat step 6
7.
Code:
adb reboot bootloader
Code:
fastboot flash recovery path to recovery
Example:
Code:
fastboot flash recovery /home/tobias/Downloads/cw_recovery_50.img
8. Flash Rom either via sd or via adb sideload
9. Rebbot
Select "Yes" both times
10. Reboot into recovery and flash SuperSu
Reboot
Select "Yes"
11. Reboot into recovery and flash gapps
Reboot
12. Done
Congratulations! You now have a rooted Andoid 4.4.2 Smartphone with Gapps.
Downloads
Recovery(by vampirefo)
Rom(official ZTE)
SuperSu(by Chainfire)
Gapps

if i want ffos back???

Back up with recovery before flashing anything ever. Then restore from recovery if needed

plmosqueda said:
if i want ffos back???
Click to expand...
Click to collapse
You can download FFOS from here and put it on your SD card.
Then you boot into recovery and install it.

7.
Code:
adb reboot bootloader
When i doing this , My pone Don't Turn On again. where its problem ? Any Sugtn ?

GamblerTobi said:
This is a guide how to root and install custom rom and recovery on ZTE Open C.
I tested it on Linux but it should work with Windows and Mac just fine.
1. Download and install Android SDK
2. Install Android SDK Tools, Android SDK Platform-tools, Android SDK Build-tools, API 19 and Google USB Driver(Windows only)
3. Download Recovery and keep it on you computer
Download Gapps and Rom and put it either on your sd card or keep it on your computer
Extract FFOS+to+Android from the rar DONT EXTRACT THE ZIP!
4. Enable external Debugging on settings>Device information>More Information>Developer>Remote Debugging
5. Connect your phone to your computer
6.
Code:
adb devices
If it shows a serial number you can skip the following and continue at step 7
If not try
Linux: type "sudo" before every command Windows:Right click on cmd and tick "Run as administrator"
If it fails try
Code:
adb kill-server
Code:
adb start-server
If it fails either try
Code:
adb shell
ctrl+c
If it fails either try to disable Remote Debugging and enable it again then repeat step 6
7.
Code:
adb reboot bootloader
Code:
fastboot flash recovery path to recovery
Example:
Code:
fastboot flash recovery /home/tobias/Downloads/cw_recovery_50.img
8. Flash Rom either via sd or via adb sideload
9. Rebbot
Select "Yes" both times
10. Reboot into recovery and flash SuperSu
Reboot
Select "Yes"
11. Reboot into recovery and flash gapps
Reboot
12. Done
Congratulations! You now have a rooted Andoid 4.4.2 Smartphone with Gapps.
Downloads
Recovery(by vampirefo)
Rom(official ZTE)
SuperSu(by Chainfire)
Gapps
Click to expand...
Click to collapse
Hello,
I own a FXOS Zte Open C (ebay EU one)
I work on Linux Mint
I suceeed from step 1 to 7 but then in the recovery I am not able to flash any ROM
- adb sideload: not working, it starts but fails at 59% with error message
adb sideload EU_FFOS+to+Android.zip
* failed to write data 'protocol fault (status len)' *
- flash ROM the file on external_sdcard: impossible because recovery is
not able to mount external_sdcard (whereas it isperfectly seen in FXOS)
It is not able to format it either....
I do not know how to move forward
adb devices return correct ID
fastboot devices also returns correct ID
Could anyone propose a solution ?
Thanks for your help

SuperThieu said:
Hello,
I own a FXOS Zte Open C (ebay EU one)
I work on Linux Mint
I suceeed from step 1 to 7 but then in the recovery I am not able to flash any ROM
- adb sideload: not working, it starts but fails at 59% with error message
adb sideload EU_FFOS+to+Android.zip
* failed to write data 'protocol fault (status len)' *
- flash ROM the file on external_sdcard: impossible because recovery is
not able to mount external_sdcard (whereas it isperfectly seen in FXOS)
It is not able to format it either....
I do not know how to move forward
adb devices return correct ID
fastboot devices also returns correct ID
Could anyone propose a solution ?
Thanks for your help
Click to expand...
Click to collapse
I found the problem: my sd card has been formatted by Windows and recovery did not appreciate....
I did format it with Linux and then everything went fine, I did flash the zip on sdexternal card.
Thanks for the tutorial !

This has not worked for me
adb reboot bootloader does nto seem to reboot not sure if it is supposed to or not.
i get to fastboot recovery and that seems to work
but when i adb sideload FFOS+to+Andorid.zip
it gives me and error: device not found
booting using the power button and volume up and selecting install zip and install zip sideload
halts at 59% and i get the error
* failed to write data 'protocol fault (status len)' *
any ideas whats wrong?

Complete Rooting Guide!

I have seen a lot of people using unofficial and third-party methods to root, which can result in a lot of adverse circumstances to say the least.
So I'm presenting a complete noob-friendly guide to rooting.
Prerequisites:
1. A computer ( I'm using Windows 10 but any OS would do)
2. A USB cable
3. Basic computer know-how
Part 1 (Getting computer ready)
Download sdk tools (adb and fastboot) from here
Note that in the entire guide I'm using official products.
So in Windows, download the zip and extract it in any folder.
Now download latest twrp recovery from here
The lastest version as of 7th August, 2017 is 3.1.
The downloaded file will be named as twrp-x.x.x-0-x3.img.
Now rename this as recovery.img (this will make our work easier)
Now move that file to platform-tools folder which we extracted earlier.
Also, I suggest downloading Intel USB drivers for Android from here
Part 2 (Getting Phone Ready)
Unlocking bootloader didn't format my phone but taking a backup is still important.
Now go to Settings<About Phone and click on Build until it says "You have become a developer"
Now back to main settings menu and find "Developer Options". And turn USB debugging on.
Download magisk install.zip, unistall.zip ans apk from here
Now connect your phone to PC via USB cable.
Step 3 (Rooting!!)
Now open platform-tools folder and press Shift+ right click.
Select "open command prompt here".
Now a terminal will open.
Type
Code:
adb devices
Now you will get a prompt on your phone. Accept it.
Now type
Code:
adb reboot bootloader
Your phone will automatically reboot and fastboot will come up.
Now type
Code:
fastboot oem unlock
[Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
And type prompt. Now type
Code:
fastboot flash recovery recovery.img
Flashing will start.
When you get type prompt again, type
Code:
fastboot reboot
And when the screen switches off, hold power up+power button.
(
Code:
fastboot reboot emergency
should work but it's effect was same as
Code:
fastboot reboot
If you get something like red state... verification failed... Then it's a good news.
Wait a few seconds and then twrp will launch. I suggest swiping on the first screen
[because letv is almost dead and we can't expect any updates. Plus my bootloader was relocked in my first attempt when I didn't swipe.]
(I suggest wiping dalvik cache and cache)
Now you can just reboot your phone normally.
Now install magisk apk.
Now reboot again to recovery. (Easiest way is Update app>tree dots menu> reboot to recovery)
When twrp starts, go to install> download and find magisk zip. Swipe to install.
Reboot and you have a fully rooted phone!!

Will it work with Le1s eco x509
Will the given method work with le 1s eco x509

Yes it will!

Im stuck in <waiting for any device>. I've installed the Intel drivers , what do you mean by select unrecognized device and install the Intel driver in it?

deepu_ said:
Im stuck in <waiting for any device>. I've installed the Intel drivers , what do you mean by select unrecognized device and install the Intel driver in it?
Click to expand...
Click to collapse
Intel driver will not work try downloading drivers from skyneel for our phone

deepu_ said:
Im stuck in <waiting for any device>. I've installed the Intel drivers , what do you mean by select unrecognized device and install the Intel driver in it?
Click to expand...
Click to collapse
Intel drivers worked for my leeco le 1s. Ideally, Intel drivers should work for all devices.
I'll make a tutorial with screenshots on setting up the drivers whenever I get time.

i cant find "open command prompt here" with shift+ Right click in platform-tools folder

junaidshaik96 said:
i cant find "open command prompt here" with shift+ Right click in platform-tools folder
Click to expand...
Click to collapse
Make sure the directory is writable .

stealthinator16 said:
I have seen a lot of people using unofficial and third-party methods to root, which can result in a lot of adverse circumstances to say the least.
So I'm presenting a complete noob-friendly guide to rooting.
Prerequisites:
1. A computer ( I'm using Windows 10 but any OS would do)
2. A USB cable
3. Basic computer know-how
Part 1 (Getting computer ready)
Download sdk tools (adb and fastboot) from here
Note that in the entire guide I'm using official products.
So in Windows, download the zip and extract it in any folder.
Now download latest twrp recovery from here
The lastest version as of 7th August, 2017 is 3.1.
The downloaded file will be named as twrp-x.x.x-0-x3.img.
Now rename this as recovery.img (this will make our work easier)
Now move that file to platform-tools folder which we extracted earlier.
Also, I suggest downloading Intel USB drivers for Android from here
Part 2 (Getting Phone Ready)
Unlocking bootloader didn't format my phone but taking a backup is still important.
Now go to Settings<About Phone and click on Build until it says "You have become a developer"
Now back to main settings menu and find "Developer Options". And turn USB debugging on.
Download magisk install.zip, unistall.zip ans apk from here
Now connect your phone to PC via USB cable.
Step 3 (Rooting!!)
Now open platform-tools folder and press Shift+ right click.
Select "open command prompt here".
Now a terminal will open.
Type
Code:
adb devices
Now you will get a prompt on your phone. Accept it.
Now type
Code:
adb reboot bootloader
Your phone will automatically reboot and fastboot will come up.
Now type
Code:
fastboot oem unlock
[Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
And type prompt. Now type
Code:
fastboot flash recovery recovery.img
Flashing will start.
When you get type prompt again, type
Code:
fastboot reboot
And when the screen switches off, hold power up+power button.
(
Code:
fastboot reboot emergency
should work but it's effect was same as
Code:
fastboot reboot
If you get something like red state... verification failed... Then it's a good news.
Wait a few seconds and then twrp will launch. I suggest swiping on the first screen
[because letv is almost dead and we can't expect any updates. Plus my bootloader was relocked in my first attempt when I didn't swipe.]
(I suggest wiping dalvik cache and cache)
Now you can just reboot your phone normally.
Now install magisk apk.
Now reboot again to recovery. (Easiest way is Update app>tree dots menu> reboot to recovery)
When twrp starts, go to install> download and find magisk zip. Swipe to install.
Reboot and you have a fully rooted phone!!
Click to expand...
Click to collapse
It works perfectly on x507, thanks bro

Orange State
stealthinator16 said:
I have seen a lot of people using unofficial and third-party methods to root, which can result in a lot of adverse circumstances to say the least.
So I'm presenting a complete noob-friendly guide to rooting.
Prerequisites:
1. A computer ( I'm using Windows 10 but any OS would do)
2. A USB cable
3. Basic computer know-how
Part 1 (Getting computer ready)
Download sdk tools (adb and fastboot) from here
Note that in the entire guide I'm using official products.
So in Windows, download the zip and extract it in any folder.
Now download latest twrp recovery from here
The lastest version as of 7th August, 2017 is 3.1.
The downloaded file will be named as twrp-x.x.x-0-x3.img.
Now rename this as recovery.img (this will make our work easier)
Now move that file to platform-tools folder which we extracted earlier.
Also, I suggest downloading Intel USB drivers for Android from here
Part 2 (Getting Phone Ready)
Unlocking bootloader didn't format my phone but taking a backup is still important.
Now go to Settings<About Phone and click on Build until it says "You have become a developer"
Now back to main settings menu and find "Developer Options". And turn USB debugging on.
Download magisk install.zip, unistall.zip ans apk from here
Now connect your phone to PC via USB cable.
Step 3 (Rooting!!)
Now open platform-tools folder and press Shift+ right click.
Select "open command prompt here".
Now a terminal will open.
Type
Code:
adb devices
Now you will get a prompt on your phone. Accept it.
Now type
Code:
adb reboot bootloader
Your phone will automatically reboot and fastboot will come up.
Now type
Code:
fastboot oem unlock
[Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
And type prompt. Now type
Code:
fastboot flash recovery recovery.img
Flashing will start.
When you get type prompt again, type
Code:
fastboot reboot
And when the screen switches off, hold power up+power button.
(
Code:
fastboot reboot emergency
should work but it's effect was same as
Code:
fastboot reboot
If you get something like red state... verification failed... Then it's a good news.
Wait a few seconds and then twrp will launch. I suggest swiping on the first screen
[because letv is almost dead and we can't expect any updates. Plus my bootloader was relocked in my first attempt when I didn't swipe.]
(I suggest wiping dalvik cache and cache)
Now you can just reboot your phone normally.
Now install magisk apk.
Now reboot again to recovery. (Easiest way is Update app>tree dots menu> reboot to recovery)
When twrp starts, go to install> download and find magisk zip. Swipe to install.
Reboot and you have a fully rooted phone!!
Click to expand...
Click to collapse
There was a prompt for TWRP update and Magisk Update.
After it has started showing Orange State instead of Red State.
The phone got rebooted and all installed apps were deleted.
Xposed got uninstalled.
Playstore, Googlemaps got unistalled.
Camera is working.
Calling is working.
Now it shows Orange State.
Is it safe.
Can we bring it to red state?
As per this link
https://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/
Orange warning: Your device is in an “unlocked” state. This means that your operating system can’t be checked to make sure that it’s safe to use.
Red warning: The operating system on your device has been changed or corrupted and is not safe to use. The device may not work properly and could expose your data to corruption and security risks.
Orange State seems to be a better state than red.

eighty9sid said:
There was a prompt for TWRP update and Magisk Update.
After it has started showing Orange State instead of Red State.
The phone got rebooted and all installed apps were deleted.
Xposed got uninstalled.
Playstore, Googlemaps got unistalled.
Camera is working.
Calling is working.
Now it shows Orange State.
Is it safe.
Can we bring it to red state?
As per this link
https://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/
Orange warning: Your device is in an “unlocked” state. This means that your operating system can’t be checked to make sure that it’s safe to use.
Red warning: The operating system on your device has been changed or corrupted and is not safe to use. The device may not work properly and could expose your data to corruption and security risks.
Orange State seems to be a better state than red.
Click to expand...
Click to collapse
I too got orange state when I had to reroot my device after it got bricked, but there was no issue, everything worked perfectly.

Hi l used this very step by step guides but sadly l got stuck at the :-
Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
Here l select the unrecognized device and install the Intel drivers but it stuck at the "Okay,,,,Okay" prompt. Meaning that l didn't get this okay prompts and it keeps me on waiting the whole day.
Secondly, till this command l stop it and power down the phone, so after l power back on and try opening the "Application" folder, then it's not working anymore, it shuts down itself.
Please help!!

Valambok said:
Hi l used this very step by step guides but sadly l got stuck at the :-
Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
Here l select the unrecognized device and install the Intel drivers but it stuck at the "Okay,,,,Okay" prompt. Meaning that l didn't get this okay prompts and it keeps me on waiting the whole day.
Secondly, till this command l stop it and power down the phone, so after l power back on and try opening the "Application" folder, then it's not working anymore, it shuts down itself.
Please help!!
Click to expand...
Click to collapse
Don't power off your phone. Post a screenshot of what exact problem you face with driver installation.

Phone Dead
Hi, after completing this step by step guides my Le 1s can't boot to normal anymore, even if I try booting up system from twrp also it doesn't help, I cant even power off now. So, please please help me out again on how to get back to a normal phone. Thanks in advance.
N.B: My phone shows Orange state