Database Info

is there an alternate method to root this tablet?

I've searched everywhere and it seems that the only method is to root is debugsf. For some reason it doesn't work. I've ran the tool 50 times and failed with different results. I'm on stock 4.03 and I already unlocked, but i don't see how that will effect it as I've tried to root before the unlock. Why does it not work? How can I root a different way?

If you're unlocked, then you can flash a custom recovery via fastboot. Check out the all-in-one thread in the general section...

If you do not want to unlock just yet, you can downgrade using the .30 ICS update from Asus.com than you can root, use OTA rootkeeper to backup the root, and update to .18 again. There are several posts on this forum, explaining how to do exactly that in great detail.

Firebrazer said:
If you do not want to unlock just yet, you can downgrade using the .30 ICS update from Asus.com than you can root, use OTA rootkeeper to backup the root, and update to .18 again. There are several posts on this forum, explaining how to do exactly that in great detail.
Click to expand...
Click to collapse
The OP is on version 4.03 and already unlocked.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Well, guess I should have read the OP more carefully then ˆˆ

I took a look at the fast boot option and went to the thread you pointed me out to and the instructions are not clear at all. Its says that I have to put the twrp.blob in the same directory as fastboot.exe. Well where the hell is the fastboot.exe directory? I tried to update to the official jb so I use that rooting method, but noooo the stock recovery is retarded and can't find the internal sd, so I only have the option to factory reset, wipe cache or reboot. Can anyone help me? WTF am I doing wrong? I've rooted 5 android devices so far and this is the only time where it seems impossible.

Iandv said:
I took a look at the fast boot option and went to the thread you pointed me out to and the instructions are not clear at all. Its says that I have to put the twrp.blob in the same directory as fastboot.exe. Well where the hell is the fastboot.exe directory? I tried to update to the official jb so I use that rooting method, but noooo the stock recovery is retarded and can't find the internal sd, so I only have the option to factory reset, wipe cache or reboot. Can anyone help me? WTF am I doing wrong? I've rooted 5 android devices so far and this is the only time where it seems impossible.
Click to expand...
Click to collapse
Maybe I could give some insight.
Just went thru this recently.
For myself I used fastboot while connected to a Windows PC.
A PC will need to have Google SDK installed (might be best to search Google for the SDK installion procedure)
You can also get what you need in something called Platform Tools.
Fastboot from the stock recovery connects via USB to the Advanced Developer Bridge thru a command window.
Once this command window (ADB) on the PC is open boot to stock recovery on the tablet.
Select the USB option using the volume button.
The PC bridge window should show device available with the serial number of the tablet (if I remember correctly)
From the prompt you can type the appropriate command to write or flash things to the tablets system.
Hope other smarter guys chime in here because I really don't want to lead you in the wrong direction...
http://forum.xda-developers.com/showpost.php?p=30147660&postcount=1
This link is kind of intimidating, yet it may be of some use...it refers to another device.
SDK works for all Android phones and tablets tho...

Yay I finally got twrp on here and I'm about to flash clean rom. Searched the pc for fastboot.exe and there it is. I had to install twrp through fastboot and it took 3 times before I realized I needed to update my sdk tools. Tried again with profit.

Iandv said:
Yay I finally got twrp on here and I'm about to flash clean rom. Searched the pc for fastboot.exe and there it is. I had to install twrp through fastboot and it took 3 times before I realized I needed to update my sdk tools. Tried again with profit.
Click to expand...
Click to collapse
Excellent!

[5.0] Nexus 5 Refuses To Flash OTA or Different ROM's

Hello,
So I just discovered this while trying to flash the 5.0.1 OTA from 5.0. I'm rooted on LRX21O via the Nexus Root Toolkit 1.9.9 (which is what I've always used in the past with no issues).
1 Tried flashing the OTA via Google notification push. It reboot, and no changes occur.
2 Fine - I try to use the Root Toolkit again. Boots into bootloader, appears to flash the radio and other necessary components. Reboots - no changes occur.
3 I then tried to just download the 5.0.1 package and flash everything manually via adb. Everything appears to go smoothly, and upon bootup Android updates all of its apps - still nothing. I appear to be completely stuck on LRX21O without any way to reflash stock or OTA's.
Anyone have any clue why this is occurring or have heard of such an issue before?
Thanks all.

Just flash factory images. With fastboot/flash-all script.
https://developers.google.com/android/nexus/images

You flash these in fastboot not adb
Sent from my Nexus 5 using Tapatalk

Did you not understand? I did flash in boot loader USING adb on my computer. All that bat script does is just automate the flashing of each image for you (system, radio, etc) so this is not helpful. I know how to flash, but flashing seems to have no effect despite successfully flashing via manually installing or just using the script

Sane116 said:
Did you not understand? I did flash in boot loader USING adb on my computer.
Click to expand...
Click to collapse
You use fastboot in bootloader, not adb.

I'm not the one asking for help. Anyways, carry on.

Your device's /system partition is tampered (you say you rooted it) and thus the OTA fails. Flash the 5.0 factory image (LRX21O) WITHOUT rooting/flashing kernels/whatever and then use the OTA zip to do adb sideload in the stock recovery to update to 5.0.1 LRX22C.

Manually use fastboot commands to flash system.img and boot.img of the full 5.0.1 factory image (not script). post the output please

I'm not the one asking for help. Anyways, carry on.
Click to expand...
Click to collapse
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?

Sane116 said:
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Click to expand...
Click to collapse
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.

Sane116 said:
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Click to expand...
Click to collapse
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?

sideloading an OTA update from stock recovery
Hello, to make it work you will need to use the Google USB drivers you downloaded when you go into stock recovery then press the power button and volume up once then you will see a menu option with the "install update from adb option select this and plug in your phone to the computer. After this is done you will need to go to device manager and install the USB drivers from the Google USB drivers you downloaded. at this point after that is done you then go into the folder that has ADB installed and use adb sideload filename.zip
at this point your phone will accept the ota update package and you wont lose any data, I hope this helps..
-cs

Sane116 said:
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
Click to expand...
Click to collapse
When you get the dead android you need to press vol up and then press and release power. That'll get you into the stock recovery. It's stupid and I don't know why they made it that way
Sent from my Nexus 9 using XDA Free mobile app

thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?

Sane116 said:
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Click to expand...
Click to collapse
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.

Sane116 said:
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Click to expand...
Click to collapse
If you're trying to flash the update.zip to 5.0.1 you need to do that in the stock recovery. It will not work in twrp or cwm. I'm not sure what you're trying to do right now
Sent from my Nexus 9 using XDA Free mobile app

my apologies.
so originally i wanted to just flash the OTA. ended up performing a fresh install and un-rooted. but there's a few unsigned zips i like to have installed.
So I think I'm going to re-root, flash twrp, install my zips, and leave it at that. i'll just flash stock recovery whenever I need the OTA which should be quick now that I know what to do.
hope that sounds correct. thanks for all the help!

OPO can't boot into custom recovery CM11.0

Hello all!
Newly registered here, has been lurking around for some time though.
I just received my replacement OnePlus due to the death of the first one and wanted to do a custom recovery and install Oxygen or Carbon for a little better battery life and back up possibilities.
My problem is: I can't get the phone to boot into recovery.
I did some research and people mentioned trying TWRP and PhilZ's recoveries - those had no result for me.
I have followed official video from OnePlus and also tried C4ETech's way for those two mentioned above.
The ones I tried were PhilZ's 6.50.2 and 6.58.8, for TWRP I used 2.8.5.1 and 2.8.4.1
Tried to do it with OPO toolbox and that didn't work either (TWRP, CWM, PhilZ tested)- all the functions would work, but once I flash the phone - it would boot into stock CM11.
When I try to boot it into recovery, it would stay on the first logo for 7-8 seconds, after that vibrates again and goes into stock CM11.
The same would happen if I go to advanced boot and boot into recovery.
I have changed the options under Developers folder as required already.
I have tried flashing the phone on two computers - win7 x64 and Win 8.1 x64.
Any help would be appreciated.
I have the phone for almost two weeks already and still can't ring myself to setting it up because of previous experience of data loss. (not worried about pictures - those are on Gdrive )

format c:\ said:
Hello all!
Newly registered here, has been lurking around for some time though.
I just received my replacement OnePlus due to the death of the first one and wanted to do a custom recovery and install Oxygen or Carbon for a little better battery life and back up possibilities.
My problem is: I can't get the phone to boot into recovery.
I did some research and people mentioned trying TWRP and PhilZ's recoveries - those had no result for me.
I have followed official video from OnePlus and also tried C4ETech's way for those two mentioned above.
The ones I tried were PhilZ's 6.50.2 and 6.58.8, for TWRP I used 2.8.5.1 and 2.8.4.1
Tried to do it with OPO toolbox and that didn't work either (TWRP, CWM, PhilZ tested)- all the functions would work, but once I flash the phone - it would boot into stock CM11.
When I try to boot it into recovery, it would stay on the first logo for 7-8 seconds, after that vibrates again and goes into stock CM11.
The same would happen if I go to advanced boot and boot into recovery.
I have changed the options under Developers folder as required already.
I have tried flashing the phone on two computers - win7 x64 and Win 8.1 x64.
Any help would be appreciated.
I have the phone for almost two weeks already and still can't ring myself to setting it up because of previous experience of data loss. (not worried about pictures - those are on Gdrive )
Click to expand...
Click to collapse
Are you checking the md5 of the recovery files after downloading to ensure that they haven't become corrupt during the download? Exactly which recoveries have you flashed (full filenames please)? Also, is the flash with fastboot definitely succeeding? I'd suggest not using a toolkit because they inevitably cause problems.

Heisenberg said:
Are you checking the md5 of the recovery files after downloading to ensure that they haven't become corrupt during the download? Exactly which recoveries have you flashed (full filenames please)? Also, is the flash with fastboot definitely succeeding? I'd suggest not using a toolkit because they inevitably cause problems.
Click to expand...
Click to collapse
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.

format c:\ said:
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.
Click to expand...
Click to collapse
Forgot to add philz_touch_6.50.2-bacon and philz_touch_6.58.8-bacon were used.

format c:\ said:
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.
Click to expand...
Click to collapse
Is there any reason you're flashing older versions of TWRP? They're pretty outdated now. Grab the latest version from here:
https://dl.twrp.me/bacon/twrp-2.8.7.0-bacon.img.html
As long as it says it's successful in the terminal window it should have flashed ok. What build of CM is currently on your phone?

Heisenberg said:
Is there any reason you're flashing older versions of TWRP? They're pretty outdated now. Grab the latest version from here:
As long as it says it's successful in the terminal window it should have flashed ok. What build of CM is currently on your phone?
Click to expand...
Click to collapse
It did work! Now I'm a happy camper Trying to install Oxygen right now.
It was on 11.0. My old phone was running that OS as well, but it was having issues with screen artifacts I have upgraded to 12.0 and system was running fine for 2 day, after that screen died completely. Buttons at the bottom of the phone were working, but it looked like just the back light was on.
Huge thanks to you, Heisenberg!

I was flashing older versions, because I found only those from the official video link. It sent me to techerrata page and the latest one over there was and still is 2.8.5.1

format c:\ said:
It did work! Now I'm a happy camper Trying to install Oxygen right now.
It was on 11.0. My old phone was running that OS as well, but it was having issues with screen artifacts I have upgraded to 12.0 and system was running fine for 2 day, after that screen died completely. Buttons at the bottom of the phone were working, but it looked like just the back light was on.
Huge thanks to you, Heisenberg!
Click to expand...
Click to collapse
format c:\ said:
I was flashing older versions, because I found only those from the official video link. It sent me to techerrata page and the latest one over there was and still is 2.8.5.1
Click to expand...
Click to collapse
Awesome, very glad to see you got it working. I realised after my post that your current CM version is in the title of the thread, lol, oops. That Techarrata site doesn't get updated anymore as they have a new site now, so the latest builds can always be found here:
https://dl.twrp.me/bacon/

Essential Bootloader Unlock - Official Advice

Links attached for those interested from Essential Web Site, and source.android.
https://support.essential.com/hc/en-us
https://source.android.com/source/running

The real question is kernel source. Not much reason to unlock the bootloader without that.

Goronok said:
The real question is kernel source. Not much reason to unlock the bootloader without that.
Click to expand...
Click to collapse
Exactly.
I'm not holding my breath.
I think I'm jumping ship.

thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol

gqukyo said:
thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol
Click to expand...
Click to collapse
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.

drocny87 said:
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.
Click to expand...
Click to collapse
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition

graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
Some people got the update today. If you happen to get it can you try to pull the boot?

I have the update waiting to be installed.

graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
in the build thread, a user was able to capture the OTA url. the only issue, the boot.img is stored in the payload.bin file. Are you familiar with this file and how to extract it?

So is this phone rootable?
Sent from my SM-G950U using XDA-Developers Legacy app

canynballa said:
So is this phone rootable?
Click to expand...
Click to collapse
At this time no. Hopefully soon that will change.

In the Andy Rubin AMA, the official Essential reddit account posted that the kernel and factory images would be released to the public "in the next few days". That probably means next week, business days and all, but it looks like they fully intend to support external development of this phone, and soon. Makes sense--why else would they allow a bootloader unlock from the get-go?

In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help

Sarzeck said:
In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help
Click to expand...
Click to collapse
You need to select correct driver in device manager, maybe even install different drivers
See
https://forum.xda-developers.com/es...nofficial-usb-drivers-essential-ph-1-t3678231
Sent from my PH-1 using Tapatalk

Thanks buddy! It worked

i love unlocking bootloader on mine but for now until no ROM's mod i will stay locked mode. im a Android Pay dude lol

Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.

Yeah, try another computer. Seriously, my main PC just didn't want to work with the phone. Used my laptop, worked fine. Can't think of anything different, both are Win10, both have the same drivers and sdks. Both work for my other phones, just not this one. Didn't hurt to try. Of course you'll need access to another computer but if you have one or more extras, worth a try. Worked for me.

oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
Did you reboot the computer? I've seen that help alot when device is not recognize

I'm having same issue, flashing unlock command do not work. I am on the oreo beta version. Someone help please.

Cannot Boot/Install TWRP On New Pixel 3

So I just picked up a Pixel 3 while on sale to replace my failing Nexus 5 that was literally falling apart. I managed to unlock the bootloader easily. Used a USB C to USB A cable from my Nintendo Switch used for charging the controller for unlocking the bootloader. Next step was to install TWRP and eventually Magisk.
So I followed the instructions to install TWRP from the TWRP website and grabbed the latest image and zip. Initially when I ran the command to boot the image, I would get a "too many links" error. Everything I found in relations to this said I needed a better cable. Odd but okay. I had planned to pickup a new one anyways for transferring music and pictures and such. Got it today, reboot into fastboot and now the command completes successfully with no error. Unfortunately instead of booting into TWRP temporarily as per the instructions, to then install the ZIP for TWRP, the phone boots straight into Android. I have tried the following commands. The first being from the official TWRP guide, and the second being from another guide I had found.
fastboot.exe boot twrp-3.2.3-0-blueline.img
fastboot.exe boot recovery twrp-3.2.3-0-blueline.img
Obviously both result in the same issue. Namely the phone simply reboots right into Android. I am using the latest Platform SDK tools from google, and am using the most up to date drivers for the phone. I am at a loss of what I might be missing. I do see info about boot slots A and B (My phone is B), but nothing in relation to that as far as installing TWRP is concerned. Any help would be appreciated!

What Android version is your Pixel 3 device running?

BobPony said:
What Android version is your Pixel 3 device running?
Click to expand...
Click to collapse
Android 10. Latest OTA.

Ultratails42 said:
Android 10. Latest OTA.
Click to expand...
Click to collapse
Twrp doesn't work on 10. Maybe it will some day but not now.

jd1639 said:
Twrp doesn't work on 10. Maybe it will some day but not now.
Click to expand...
Click to collapse
Yeah. I see that now. Looked it up after they asked the android version. Here's hoping they update it soon to work with 10.

Ultratails42 said:
Yeah. I see that now. Looked it up after they asked the android version. Here's hoping they update it soon to work with 10.
Click to expand...
Click to collapse
If you want, you can downgrade to Android 9 using the factory images with the flash-all script. But, it requires to have the bootloader unlocked.