Hi Everyone.
After look up for a 2nd hand phone works for one hours, and just dead. the google logo bootloop.
after a ton of google, i choose Nexus root toolkit to understand if that is really a "hardware fail" as everyone says, or just another OS issue.
i saw that was nothing happening after some tries (google logo still looping) to re-flash, and left the phone and goes for lunch, when i´m back suddenly i have a few different screens randomly:
1- from google logo goes for the 4 animated dots.
2- from google logo goes to "encrypt unsuccessfull"
3- from google logo goes to android animated logo.
Nexus toolkit still showing "waiting device" and no other action there.
may the brute force or persistent attempts have any different effects on that massive issue?
thanks
erico.albino said:
Hi Everyone.
After look up for a 2nd hand phone works for one hours, and just dead. the google logo bootloop.
after a ton of google, i choose Nexus root toolkit to understand if that is really a "hardware fail" as everyone says, or just another OS issue.
i saw that was nothing happening after some tries (google logo still looping) to re-flash, and left the phone and goes for lunch, when i´m back suddenly i have a few different screens randomly:
1- from google logo goes for the 4 animated dots.
2- from google logo goes to "encrypt unsuccessfull"
3- from google logo goes to android animated logo.
Nexus toolkit still showing "waiting device" and no other action there.
may the brute force or persistent attempts have any different effects on that massive issue?
thanks
Click to expand...
Click to collapse
The common denominator of the BLOD is not being able to get into recovery mode at all. Are you able to get into recovery mode, and are you using a custom recovery (TWRP) or stock recovery? If stock have you tried doing a factory reset? The first boot will take a long time while it is encrypting.
Sounds like you are unlocked and maybe ADB debugging is enabled? Next method would be to get ADB/Fastboot installed on your PC and flash the stock Google image using the flash-all. bat file. But.... since you already have NRT running, you could open "Advanced Utilities" and fastboot format cache, system and userdata (check all 3 boxes). Then go back to the main menu and run "Flash Stock and Unroot". Use the "bootloop/semi-bricked" option. For now, don't root or install a custom recovery. Just see if you can boot into the OS.
v12xke said:
The common denominator of the BLOD is not being able to get into recovery mode at all. Are you able to get into recovery mode, and are you using a custom recovery (TWRP) or stock recovery? If stock have you tried doing a factory reset? The first boot will take a long time while it is encrypting.
Sounds like you are unlocked and maybe ADB debugging is enabled? Next method would be to get ADB/Fastboot installed on your PC and flash the stock Google image using the flash-all. bat file. But.... since you already have NRT running, you could open "Advanced Utilities" and fastboot format cache, system and userdata (check all 3 boxes). Then go back to the main menu and run "Flash Stock and Unroot". Use the "bootloop/semi-bricked" option. For now, don't root or install a custom recovery. Just see if you can boot into the OS.
Click to expand...
Click to collapse
i tried with the adb sideload the Stock one and it keeps o loop. no changes on the screen.
i'm not unlocked at all, its shows on the recovery screen. i will re-try some root and another windows7 and mac for this.
as you say, if BLOD consist to not get in to recovery, i'm safe for now, just need to figure out how to make it works.
thanks a lot so far.
erico.albino said:
i tried with the adb sideload the Stock one and it keeps o loop. no changes on the screen.
i'm not unlocked at all, its shows on the recovery screen. i will re-try some root and another windows7 and mac for this.
as you say, if BLOD consist to not get in to recovery, i'm safe for now, just need to figure out how to make it works.
thanks a lot so far.
Click to expand...
Click to collapse
You said "i'm not unlocked at all" So do you mean your bootloader is LOCKED? Also, the status of bootloader is shown in BOOTLOADER MODE not recovery mode. Perhaps you need to research the difference and answer whether your bootloader is locked (yes/no) and whether you are able to access RECOVERY MODE, or not (yes/no). And whether that is stock recovery? I have no problem with English being your second language, but you need to try to be clear in your answers so we all understand where you are so we can help you. Cheers.
How to enter Recovery Mode: https://www.youtube.com/watch?v=wq_gzT-fV2E
v12xke said:
You said "i'm not unlocked at all" So do you mean your bootloader is LOCKED? Also, the status of bootloader is shown in BOOTLOADER MODE not recovery mode. Perhaps you need to research the difference and answer whether your bootloader is locked (yes/no) and whether you are able to access RECOVERY MODE, or not (yes/no). And whether that is stock recovery? I have no problem with English being your second language, but you need to try to be clear in your answers so we all understand where you are so we can help you. Cheers.
How to enter Recovery Mode: https://www.youtube.com/watch?v=wq_gzT-fV2E
Click to expand...
Click to collapse
thanks for all the word, V12...!
dont have english as my mother language is complicated. specially when you need help on some topics that is not available or dont have good places to go here! (brazil).
anyway, i'm following your first suggestions, and i'm going to share the results soon.
the nexus screen on recovery mode shows:
Console:NULL
Battery OK
Device is LOCKED
Qfuse status ENABLED
off-mode Chager ENABLED
download mode DISABLED.
on my first attempts, i was able to enter on ADB upload menu as you indicate on the video, was able to load the stock rom but stop on the boot loop.
the second shot was my main topic status, using nexus root toolkit with "flash stock+unroot" selecting "softbrick+bootloop". three different screen results on loop.
thanks a lot for the help, bro!
:good:
erico.albino said:
thanks for all the word, V12... Device is LOCKED.... on my first attempts, i was able to enter on ADB upload menu as you indicate on the video, was able to load the stock rom but stop on the boot loop. the second shot was my main topic status, using nexus root toolkit with "flash stock+unroot" selecting "softbrick+bootloop". three different screen results on loop.
Click to expand...
Click to collapse
Because your bootloader is locked, the only real option is to sideload an OTA from the stock recovery. Not possible to flash a full image. You will need to find an OTA that is newer than your current build. If it won't boot, try a factory reset and boot again. If that doesn't work, try fastboot formatting (only) userdata and cache partitions and try the OTA again.
ps: encryption unsuccessful keeps on 7.1.1 NUFK26Kversion, after 30min google bootloop. will give a try with another versions, but my default built is NRD90T 7.0. that is what is showing on the recovery screen (the second one, on the power+volume up on recovery mode). runnning the nexus root toolkit and flash+unroot.
ps: i',m supposed to be almost there, just need to figure out
erico.albino said:
ps: encryption unsuccessful keeps on 7.1.1 NUFK26Kversion, after 30min google bootloop. will give a try with another versions, but my default built is NRD90T 7.0. that is what is showing on the recovery screen (the second one, on the power+volume up on recovery mode). runnning the nexus root toolkit and flash+unroot.
ps: i',m supposed to be almost there, just need to figure out
Click to expand...
Click to collapse
Firstly, NRT doesn't work flashing for you because your bootloader is locked (it even tells you this) and you need to be sure you are using an OTA image. You cannot flash a full stock image. The Flash Stock + Unroot option in NRT downloads the full image. You are supposed to use the ADB side load option from your phone's recovery and send it from your PC. Not that it makes a huge difference, but you are also using the wrong image for Verizon only in the U.S... You need N4F26O not NUFK26K. What happens when you do a factory reset from recovery mode? There is another update out next week (March Security Update) you can try that OTA when it is posted to the link above.
v12xke said:
Firstly, NRT doesn't work flashing for you because your bootloader is locked (it even tells you this) and you need to be sure you are using an OTA image. You cannot flash a full stock image. The Flash Stock + Unroot option in NRT downloads the full image. You are supposed to use the ADB side load option from your phone's recovery and send it from your PC. Not that it makes a huge difference, but you are also using the wrong image for Verizon only in the U.S... You need N4F26O not NUFK26K. What happens when you do a factory reset from recovery mode? There is another update out next week (March Security Update) you can try that OTA when it is posted to the link above.
Click to expand...
Click to collapse
-Factory reset/wipe data goes OK. if i restart the system, it back to bootloop.
-for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)
-adb devices works and show my current device on prompt.
-NRT sideload option is aborted as "verification filed" after some steps and pointing to factory image or automatic img from NRT.
-at NRT, adb sideload device is been recognized, fastboot device recognized but adb recovery device not found status its showing up in the end.
i'm sure i'm doing something wrong, just cant figure out where..... =(
erico.albino said:
-
-for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)
-adb devices works and show my current device on prompt.
-NRT sideload option is aborted as "verification filed" after some steps and pointing to factory image or automatic img from NRT.
-at NRT, adb sideload device is been recognized, fastboot device recognized but adb recovery device not found status its showing up in the end.
i'm sure i'm doing something wrong, just cant figure out where..... =(
Click to expand...
Click to collapse
What is the name of the file you are trying to sideload, and is it an OTA? (angler-ota-n4f26o-6a853f19.zip)
What happens when you follow the method #1 on this page? You will have to "adb push" the OTA file to your phone. If you can't do this, you may not have the correct drivers installed or not have adb installed correctly.
Not sure what you mean by "for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)"- can you elaborate?
v12xke said:
What is the name of the file you are trying to sideload, and is it an OTA? (angler-ota-n4f26o-6a853f19.zip)
What happens when you follow the method #1 on this page? You will have to "adb push" the OTA file to your phone. If you can't do this, you may not have the correct drivers installed or not have adb installed correctly.
Not sure what you mean by "for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)"- can you elaborate?
Click to expand...
Click to collapse
OTA file name: angler-n4f26o-factory-c53f0a50 (1).zip
download page/link: https://developers.google.com/android/images
i cant access internal storage. so i cant run step 1 on that page.
if i hit "adb sideload angler-n4f26o-factory-c53f0a50 (1).zip" on command prompt on windows, i receive this:
R:\Desktop\nexus\Fastboot\Fastboot>adb devices
List of devices attached
84B7N15C21000379 host
R:\Desktop\nexus\Fastboot\Fastboot>adb sideload angler-n4f26o-factory-c53f0a50.z
ip
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
here some images: https://goo.gl/photos/zLZ9CEh1dtpgPJf17
erico.albino said:
OTA file name: angler-n4f26o-factory-c53f0a50 (1).zip
download page/link: https://developers.google.com/android/images
i cant access internal storage. so i cant run step 1 on that page.
if i hit "adb sideload angler-n4f26o-factory-c53f0a50 (1).zip" on command prompt on windows, i receive this:
Click to expand...
Click to collapse
You are not flashing the OTA. You are attempting to sideload the full image. I'm still reading through the rest of your post, but go ahead and download the correct file.
https://developers.google.com/android/ota#angler
v12xke said:
You are not flashing the OTA. You are attempting to sideload the full image. I'm still reading through the rest of your post, but go ahead and download the correct file.
https://developers.google.com/android/ota#angler
Click to expand...
Click to collapse
forget the long post, i was missing the quotes on the image file name.
i'll run your suggestion now...
erico.albino said:
i cant access internal storage. so i cant run step 1 on that page.
Click to expand...
Click to collapse
You can use adb push to move transfer the file over to your phone. "adb push ota.zip /sdcard/ota.zip" then use the "apply update from sdcard" option in recovery. To avoid typos/syntax errors, simply rename the file you are using to ota.zip first. I still think you might have issues with your adb/driver installation.
v12xke said:
You can use adb push to move transfer the file over to your phone. "adb push ota.zip /sdcard/ota.zip" then use the "apply update from sdcard" option in recovery. To avoid typos/syntax errors, simply rename the file you are using to ota.zip first. I still think you might have issues with your adb/driver installation.
Click to expand...
Click to collapse
thanks at all for all the help. unfortunately, after successfully sideload the OTA file, boot loop still here
Sorry to hear that. See if you are allowed to fastboot FORMAT userdata and cache from your PC and try the OTA again. You may get an error formatting userdata. Remember, next week brings a new March security update, and if you haven't given up on your device you can try to flash that OTA when it is posted by Google. You can now get back to your math homework...
Before you go, does your Recovery screen still say NRD90T or did it update to N4F26O?
i can see 7.1.1 N4F26O on recovery screen.
you can bet i will not git it up on this, lol. it was a very good deal based o the value of the device here in brazil.
i'll keep this post up to date about this and let you know about any news.
thanks again for all the help bro, much appreciate it!
cheers from brazil!
erico.albino said:
i can see 7.1.1 N4F26O on recovery screen.
Click to expand...
Click to collapse
March Security Update OTA's posted on Google. Boom!
v12xke said:
March Security Update OTA's posted on Google. Boom!
Click to expand...
Click to collapse
no chanfes unfortunately
There is any specific variant of nexus that can be down for this kind of brick?
Sent from my iPhone using Tapatalk
Related
I'm stuck right here as far as download mode goes.
I installed TWRP on a d800 rooted with stock 4.2.2. The TWRP install went ok but it never booted afterward.
I can get into twrp, but can't sideload anything because the computer does not connect to the device, I hear the connection noise the computer makes but nothing in the device manager.
any ideas?
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
Thanks, I get
error: closed
I was wrong about my computer not seeing my device, it's in the device manager under Android and the adb drivers are installed.
I also renamed the rom to "update" to make it simpler
What's up now ?
Sorted it out or still issues there ?
I also tried the adb shell method.
I also tried this method through TWRP terminal and nada.
If I did something wrong here let me know, hopefully I can get it up and going
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Gabriel51 said:
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Click to expand...
Click to collapse
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
bender_007 said:
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
Click to expand...
Click to collapse
I moved the file to the root of my C drive changed the name to "rom.zip"
Copied the command you supplied and got this result
I know my phone is connected because I can reboot it by using the command " adb reboot"
I used this;
adb push C:\Android\sdk\platform-tools\rom.zip
And it is now ready to install through TWRP!
Hold your breath.......
Edit;
Failed but at least it's in the twrp list
"unable to open zip"
I think I got it, I was able to access the firmware update screen.
Sorry fir these incomplete responses, I don't want you to keep looking for a resolve while I do this.
If your still here?
I'll be back!
Success!
After nothing would work except for loading the rom through adb I decided to wipe the whole thing.
I reloaded the rom and when selected for install it opened instead of preparing for install so I thought I would reboot and when I did I was prompted by su that my device may have lost root and gave me the option to reinstall it, I chose yes and when rebooting it hung (normal) at the LG logo, however this time the charge light was flashing! I attempted to access "download" and was successful in loading the stock rom.
In the end it looks like TWRP was the culprit, it used to be my favorite but not for this device
All is well, thanks for your help...
Hi folks!
I wanted to install Cyanogenmod as described in Cyanogenmod Wiki.
So I downloaded ioroot, rootet my phone via adb and used AutoRec to install TWRP (version 2.7.0.0).
Then I rebooted into recovery mode, wiped EVERYTHING and wanted to sideload the CM image via adb.
So in TWRP I selected Advanced/ADB Sideload and swipe to start sideload but all that happens is the notification "Starting ADB sideload feature...".
Consequently the phone is not recognized by adb on my PC.
What can I do to make the sideload feature work?
BTW: TWRP tells me that my devices doesnt appear to be rooted when I want to leave TWRP (reboot). Moreover when i want to enter TWRP again (by pressing POWER + VOLUE DOWN) I first get a screen that asks me if want to do a factory hard reset! Only if I agree (by pressing the power key) I get into TWRP.
Contrary when I enter the Download Mode (VOLUME UP when when connecting the powered off phone to the USB port) I am told that the phone is rooted. Moreover the LG Mobile Support Tool is able to detect the device and tells me that the installed software is up to date.
Thx!!
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Make sure you're in the proper folder in prompt and the device name will be sideload if you do, adb devices.
Sent from my LG-D800 using Tapatalk
meangreenie said:
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Click to expand...
Click to collapse
Thanks but this doesnt help either. Same error message "error: device not found"
boot into twrp, don't start sideload
try adb devices, if you get not find you need to change the usb drivers
when you have it working, type, adb push /sdcard/ rom.zip .. check the syntax on that command, but i think that's right from memory
Hello, folks.
I'm still new to all this and I'm completely stuck trying to get TWRP installed. Gone through all the steps, and everything I could find on Google as well, yet fastboot won't do anything for me.
What I've been trying is: adb devices shows device, reboot bootloader boots into download mode, fastboot devices returns nothing, fastboot flash recovery twrp.img(4.4, hopefully the right one?) returns waiting for any device.
Rooted and bootloader is unlocked, twrp file is in same folder as adb and fastboot which is where admin cmd prompt is open to.
I've downloaded the samsung and google drivers.
Confirmed device is recognized in device manager.
Tried different USB ports.
Tried installing via the TWRP manager app, get an error installing any version.
Feels like I must be missing something stupid. Just trying to get a new ROM to hopefully speed this thing up.
Thanks for any advice!
EDIT - skip to bottom
The use of fastboot to interact with bootloader firmware is NOT universal among Android handset makers.
In particular, Samsung. Fastboot hasn't worked with Samsung android devices for a long time (it possibly never did).
The nearest analagous equivalent is Samsung's "Odin" software (for Windows PCs).
There is also "heimdal" for *nix machines which attempts to replicate the behaviors of Odin.
The handset boot mode most closely corresponding to "fastboot" is Samsung's "Download" (or "Odin") mode. On the Note 3 you enter that mode from a cold start with a three-finger salute: Vol-Down+Home+Power. A splash screen will show up allowing you to "Cancel" (normal boot) or "Download" mode.
It is harmless to enter that mode if you want to look at what the screen looks like, but you might have to pull the battery to get out of it if you don't use Odin.
Search XDA for "Odin" ( or heimdal), you will find plenty of posts
Flashing TWRP:
The TWRP images are not filesystems, but just a large (bootable) binary blob file (containing a kernel, ramdisk, and device tree).
That means you can simply use the "dd" command (as the root user) to write the .img blob into the recovery partition, using a shell/ terminal. Could be using either adb or a terminal emulator app. You just need to have a root prompt.
Obviously you need to be cautious about this, making sure you are blasting bits into the correct partition (the recovery partition).
e.g. see
ls -ld /dev/block/platform/msm_sdcc.1/by-name/*
bftb0 said:
EDIT - skip to bottom
The use of fastboot to interact with bootloader firmware is NOT universal among Android handset makers.
In particular, Samsung. Fastboot hasn't worked with Samsung android devices for a long time (it possibly never did).
The nearest analagous equivalent is Samsung's "Odin" software (for Windows PCs).
There is also "heimdal" for *nix machines which attempts to replicate the behaviors of Odin.
The handset boot mode most closely corresponding to "fastboot" is Samsung's "Download" (or "Odin") mode. On the Note 3 you enter that mode from a cold start with a three-finger salute: Vol-Down+Home+Power. A splash screen will show up allowing you to "Cancel" (normal boot) or "Download" mode.
It is harmless to enter that mode if you want to look at what the screen looks like, but you might have to pull the battery to get out of it if you don't use Odin.
Search XDA for "Odin" ( or heimdal), you will find plenty of posts
Flashing TWRP:
The TWRP images are not filesystems, but just a large (bootable) binary blob file (containing a kernel, ramdisk, and device tree).
That means you can simply use the "dd" command (as the root user) to write the .img blob into the recovery partition, using a shell/ terminal. Could be using either adb or a terminal emulator app. You just need to have a root prompt.
Obviously you need to be cautious about this, making sure you are blasting bits into the correct partition (the recovery partition).
e.g. see
ls -ld /dev/block/platform/msm_sdcc.1/by-name/*
Click to expand...
Click to collapse
Took some further research, but I now have TWRP successfully installed!
Thank you kindly
Few notes for future searchers: from your adb folder run 'adb shell' then 'su' to get the root prompt, then enter the above command. Also the /sdcard/ folder is internal storage, actual sdcard path is /storage/extsdcard/
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
I just received a system update for build PPR1.180610.091 but I am rooted with a custom kernel.
I think it should be ok to take the system update if I restore my /boot to a stock image but I want to make sure before I take the update.
The rom is stock and has Magisk and ElementalX. Bootloader and Critical are unlocked.
Would it be ok if I restore my boot.img to the stock one and then accept the update via the system updater? or is there something else I need to do?
xNotta said:
I just received a system update for build PPR1.180610.091 but I am rooted with a custom kernel.
I think it should be ok to take the system update if I restore my /boot to a stock image but I want to make sure before I take the update.
The rom is stock and has Magisk and ElementalX. Bootloader and Critical are unlocked.
Would it be ok if I restore my boot.img to the stock one and then accept the update via the system updater? or is there something else I need to do?
Click to expand...
Click to collapse
Just reboot to stock recovery, apply update from adb, in terminal on pc, adb sideload, then drag and drop the ota zip from essential site, hit enter, it will update and u keep data
jacksummers said:
Just reboot to stock recovery, apply update from adb, in terminal on pc, adb sideload, then drag and drop the ota zip from essential site, hit enter, it will update and u keep data
Click to expand...
Click to collapse
If I sideload the Ota, do I need to flash the stock boot first?
xNotta said:
If I sideload the Ota, do I need to flash the stock boot first?
Click to expand...
Click to collapse
Nope. After the flash and reboot, u gotta re root though
jacksummers said:
Nope. After the flash and reboot, u gotta re root though
Click to expand...
Click to collapse
I just did the sideload but I got an error:
Code:
adb> adb sideload .\PH1-OTA-PPR1.180610.091.zip
opening '.\PH1-OTA-PPR1.180610.091.zip'...
connecting...
serving: '.\PH1-OTA-PPR1.180610.091.zip' (~94%) * failed to read command: No error
but the recovery said it was completed successfully. My phone booted fine and is running Pie.
Is this a normal error?
xNotta said:
I just did the sideload but I got an error:
Code:
adb> adb sideload .\PH1-OTA-PPR1.180610.091.zip
opening '.\PH1-OTA-PPR1.180610.091.zip'...
connecting...
serving: '.\PH1-OTA-PPR1.180610.091.zip' (~94%) * failed to read command: No error
but the recovery said it was completed successfully. My phone booted fine and is running Pie.
Is this a normal error?
Click to expand...
Click to collapse
I got the same error, but haven't had any issues.
I have been using this thread as my reference for how to take updates so I wanted to add some instructions and links that I found useful/necessary for completing the process.
Hopefully someone else can find this useful.
IMPORTANT! Remove screen lock pin before continuing!
TWRP will prompt for a password if you do not remove your lockscreen pin/pattern! There is no password!
This is caused due to Android encrypting the /data/ partition.
Settings > Security & Location > Device Security section > Screen Lock. Set it to None.
You can also search in settings for "Screen Lock"
Stock boot images:
https://drive.google.com/drive/folders/1iayS6YHYZvqkD1Y8oYV3ewzW5aAPe8C2
TWRP (twrp-mata_11.img) images:
https://download.invisiblek.org/mata/
Essential Phone downloads:
Download the OTA file for Sideloading
https://www.essential.com/developer/current-builds
Sideloading using stock recovery(my preferred method):
Ensure USB debugging is enabled on your Essential Phone. To do so, follow step four above.
Plug your Essential Phone into your computer with a USB cable.
Open a command window in the folder where you have ADB and fastboot installed.
In your command window, type adb devices and press enter. Your device’s serial number should appear in the command window.
If you see a notice on your phone asking if you’d like to allow USB debugging on this computer, check the box and select OK.
Reboot your phone into recovery mode. To do so, type adb reboot recovery into your command window. Your phone will reboot into recovery mode. You should see a little green bugdroid with a caution symbol. Despite your gut reaction, this is good.
Open the recovery menu on your Essential Phone. To do so, hold the power button and press the volume-up button once.
Scroll down to Apply update from ADB with your volume-down button, then press the power button to confirm.
Ensure that your phone is still being recognized by your computer. To do so, type adb devices in your command window and press enter. Your device’s serial number should appear in the window.
In your command window, type adb sideload update.zip (or whatever you named your file).
Source: https://www.androidauthority.com/how-to-install-android-p-essential-phone-863668/
Sideloading using TWRP:
Reboot your Essential Phone into Fastboot mode by restarting the phone and pressing and holding volume down and the power button at the same time. Once you’re in Fastboot mode, flash TWRP with the following ADB command: fastboot flash boot twrp.img
From within the Fastboot menu, select and boot into “recovery mode.” Once TWRP has booted up, type in: adb shell twrp sideload
Then type in: adb sideload magisk.zip
Once Magisk finishes installing completely, reboot back to Fastboot. You can do this via: adb reboot-bootloader
When you’re back in Fastboot mode, grab the modified boot.img (making sure to select the right one) and flash it via fastboot flash boot boot.img
Now reboot! You should now have root via Magisk!
Source: https://www.xda-developers.com/how-to-root-essential-phone-ph-1/