Database Info

[Q] Rooting Xoom without bootloader unlock?

Hi there, I had a look at universal xoom boot at http://forum.xda-developers.com/showthread.php?t=1242241 and I think it works with the UK model of the Wifi only xoom.
I noticed that you have to unlock the bootloader which involves wiping the device. I don't want to do that as I have tons of stuff I want to keep and stuff I can't lose.
I was thinking could you flash it through recovery mode by using the adb command
Code:
adb reboot recovery
When it rebooted in recovery there were three options, apply update from SD card, factory reset/wipe and wipe cache. If I put the zip onto an SD card and applied update in recovery will it work? I mean the zip on the universal xoom root page that says to flash cwm.
Has anyone tried this and does it work?
Thanks for any guidance in advanced
Chris

Anyone know?

You have to unlock. this is why people recommend the day you get the Xoom unlock it, even if you don't plan to root.
Sent from my Galaxy Nexus

Thanks for replying .i don't see why that won't work though, but I can't risk trying it, I was hoping for someone who has tried it say if it has worked. Thanks anyway

cwilkinson1998 said:
Thanks for replying .i don't see why that won't work though, but I can't risk trying it, I was hoping for someone who has tried it say if it has worked. Thanks anyway
Click to expand...
Click to collapse
Don't think it'll work because the locked bootloader/recovery should verify that an update has been created and signed by motorola. If you unlock, your bootloader won't check such signatures if you flash through fastboot, and the modded recoverys will do just about whatever they want
However, there may be a way to root your xoom without unlocking, there are enough devices out there that cannot be unlocked at all and are still able to be rooted. As far as I know, no one has tried finding a security flaw in the xooms software so far, though, as it's easy as pie to just unlock the device

back up then unlock
bwcorvus said:
You have to unlock. this is why people recommend the day you get the Xoom unlock it, even if you don't plan to root.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
You have to do OEM unlock do back up to your SD card then adb reboot bootloader then fastboot OEM unlock then flash your recovery.img

[Solved] [Q] New TF300T user unlock/recovery/root (only HTC exerience)

What do I have to do to install a custom recovery and get root?
Where do I get the ASUS specific drivers for all of normal, recovery
and boot-loader modes, for adb, fastboot and 'disk drive'?
I can use ADB and fastboot SDK utilities from the Win7 console prompt.
the appropriate dll's and exe's are in windows path.
Are there special things to do like HTC's hboot unlock procedure?
I saw an apk file on ASUS's website for unlock, how does that work?
I found 1-click root script that is supposed to install an CWM
custom recovery and get root for you. Do I need to do anything prior
to running that to unlock the boot loader, so it will accept the fastboot
commands? Besides setting usb debug and any allowing any apk?
I don't know how to interact with the ASUS boot loader for
loading updates. For HTC I only needed a specially named zip
file on the root of the ext sd card and push buttons to start
the process. Is it similar? :fingers-crossed:

Try reading this.
http://forum.xda-developers.com/showthread.php?t=1697227

All of your questions and answers have been posted a long time ago and is readily available for your reading enjoyment. At least make an attempt to research on your own. Reading is your friend....
Sent from my SGH-I777 using Tapatalk 2

OK -- RTFM *sigh*
Can I flash cwm via fastboot w/o unlocking? I just want to root
to be able to run Titanium backup and Root Explorer tools.
Stock ROM is fine, only need cwm to get root.
The device was purchased a few days ago, (waiting for it
to arrive), so its probably .29 or .30 from factory.
I discussed the issues with ASUS and they kept reading
the text of the warning message about unlocking
instead telling me how / what to do to root.
If I understood correctly, after turning off 'fast boot'
and turning on 'USB debugging', I should be able to get the
stock boot loader into fastboot USB mode following the power on
volume button presses, then use fastboot flash recovery to
store the cwm recovery.img in the recovery partition.
I'm unsure what it is that unlock boot loader apk actually does ?
With HTC it was the hboot software version that determined
if fastboot commands were accepted. Perhaps when I actually
have the device, I'll understand better.
With that done, flash the root-signed.zip from cwm to root?

Cavsoldier already advised you to do your own research. All your questions have been answered, both for your first post and your second.
I'm not entirely sure why you seem so determined to flash CWM for root. They are completely unrelated. You only flash CWM when you unlock the bootloader. You do not have to unlock your bootloader to root the device. Just use this thread.
Also not sure why you're asking Asus how to root their product. That's a big no no. Companies don't like when you root their products. Even if the CSR knows how to root the device, they're not allowed to tell you. They'll just read from a script like they did to you.
Honestly, I'm not sure why I'm bothering to answer this. All the info you could possibly need is in the thread that was linked in the second post. All of it, for every question you've asked in both of your posts in this thread. Anything root or ROM related is in that thread. It links to several rooting methods, most of which do not require CWM, let alone an unlocked bootloader. So, basically, why haven't you clicked the link in the second post? Do it.

*sigh* sorry for being dumb
Alright -- I admit I couldn't find the search forum
button on the phone interface. After I looked via a
laptop (so I had the desktop view) it was where I
thought it was.
In any case, I found the utility script debugfs-root-v1.8
which uses all adb commands so it doesn't need to be able
to run fastboot boot loader commands. It looked like the
tricky stuff was being run on the tablet via adb shell
commands and adb control commands. If I understood
it, it leaves the tablet rooted without unlocking the boot
loader. So if I can live without nandroid backups, I can just
leave the OEM stock recovery alone.
Is there more to unrooting than removing superuser.apk
and restoring the stock su?
Would installing the current official firmware work
similar to HTC's RUU's and replace everything?

fuzzynco said:
*snipped*
Is there more to unrooting than removing superuser.apk
and restoring the stock su?
Would installing the current official firmware work
similar to HTC's RUU's and replace everything?
Click to expand...
Click to collapse
To unroot, there's an option in superuser. Installing the new firmware will not wipe data.
Sent from my Incredible 2 using Tapatalk 2 Beta-5

Thank you.....:good:

Post unlocked bootloaded

I began with the thread http://forum.xda-developers.com/showthread.php?t=1833212
I intended to unlock the bootloaded( completely successfully) , root( not attempted) , install nvflash (since I read its a must have) and install a rom, because the stocks lags horribly
After unlocking I found my way to http://androidroot.mobi/t3_nvflash/ to attempt getting nvflash.
Two things stopped me. For starters the website says the only version is Transformer TF700: 9.4.5.30r01. Now I have seen on the xda thread referenced above "If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE"
So does that mean I cannot get nvflash.
Secondly, the second prerequisite "Working fastboot binary & all necessary drivers" ????? Maybe I missed it but I didn't see any How-To's on fastboot.
Most important to me is understanding what I am doing. Coming from a galaxy s3, the process here seems different.Now I know samsung and asus are different companies. Its just on the S3, I completely understood, that to root for example....I could flash a rooted stock rom, i could use ODIN for example to flash CWM. Then once I had CWM I could back up, restore, install roms at will
With this tablet i still see there is a place for CWM, but I don't see any mention of ODIN. Then there i fastboot. What is it?
If a BIOS is to a windows PC as a bootloader is to my tablet.(I think that's a fair analogy) Then where does fastboot come in
Thanks for any help

Tjisana said:
After unlocking I found my way to http://androidroot.mobi/t3_nvflash/ to attempt getting nvflash.
Two things stopped me. For starters the website says the only version is Transformer TF700: 9.4.5.30r01. Now I have seen on the xda thread referenced above "If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE"
So does that mean I cannot get nvflash.
Click to expand...
Click to collapse
The AndroidRoot bootloader is a hacked version of 9.4.5.30 and it can only be installed if your current bootloader is older than 9.4.5.30, e.g. 9.4.5.26. If you didn't upgrade past 9.4.5.26, you can still get nvflash access.
Tjisana said:
Secondly, the second prerequisite "Working fastboot binary & all necessary drivers" ????? Maybe I missed it but I didn't see any How-To's on fastboot.
Click to expand...
Click to collapse
Fastboot is part of the Android SDK, which everyone who is into hacking, rooting and installing custom ROMs should have installed on their PC. If you are running Windows, you also need some USB drivers.
Tjisana said:
Most important to me is understanding what I am doing.
Click to expand...
Click to collapse
Right. Don't do anything before you understand what you are doing. Helps tremendously to avoid stupid bricks due to known reasons. One of these is: Never choose "wipe data" from the bootloader menu if your recovery is broken, it's known to cause trouble.
Tjisana said:
With this tablet i still see there is a place for CWM, but I don't see any mention of ODIN. Then there i fastboot. What is it?
If a BIOS is to a windows PC as a bootloader is to my tablet.(I think that's a fair analogy) Then where does fastboot come in
Click to expand...
Click to collapse
Yes, BIOS and bootloader are roughly comparable in their role, at least in their role to initialize hardware and to load the operating system. Fastboot is a tool to install an operating system kernel. You can't insert a CD or USB stick into this device to (re)install Android.
Maybe you already know that an Android device has two such kernels - it can boot either into regular Android, or into a small recovery system that is used to upgrade or maintain the main system. The recovery, as well as the Android boot image, can be flashed using fastboot. The most popular recovery for the TF700 seems to be TWRP, but CWM is also available.
NVFlash is lower level, it can do everything that fastboot can do (in a slightly different way), and it can read or write any partitions or raw blocks on your device. It even works if your bootloader is broken - fastboot in contrast communicates with the bootloader.

TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader

TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader
TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader error 0x00000000"
bootloader error is 0x00000000
I can gain access to fastboot and atx mode. No recovery though. Need someone to help me. Give me a tutorial if this is possible to fix. Am moderately familiar with fastboot but prefer instructions with the code so I can just copy and paste. I think if I could get a kernel on it I'd be good. And maybe there is hope since the computer sees it. Windows vista x86. tf700t firmware 10.6.1.14.1-20130329 A03.
Thank you in advance.
Cole:crying:

33colburn said:
TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader error 0x00000000"
bootloader error is 0x00000000
I can gain access to fastboot and atx mode. No recovery though. Need someone to help me. Give me a tutorial if this is possible to fix. Am moderately familiar with fastboot but prefer instructions with the code so I can just copy and paste. I think if I could get a kernel on it I'd be good. And maybe there is hope since the computer sees it. Windows vista x86. tf700t firmware 10.6.1.14.1-20130329 A03.
Thank you in advance.
Cole:crying:
Click to expand...
Click to collapse
Reading is your friend
http://forum.xda-developers.com/showthread.php?t=1926286
Seriously though, you can use those directions to flash the recovery. Replace the recovery-jb-touch.img with twrp or whatever recovery you want to use.

Tried Fastboot Kernel/Recovery but Failed
dasunsrule32 said:
Reading is your friend
http://forum.xda-developers.com/showthread.php?t=1926286
Seriously though, you can use those directions to flash the recovery. Replace the recovery-jb-touch.img with twrp or whatever recovery you want to use.
Click to expand...
Click to collapse
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole

33colburn said:
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole
Click to expand...
Click to collapse
Tell us what you did that cause this issue?? make sure you stated what software version, bootloader/cwm version during the incident.

33colburn said:
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole
Click to expand...
Click to collapse
I had this too, when flashing with the 700 attached to a back USB port (which is the primary set, should be fine in tiself), but via an extension cable (apparently NOT OK). I really recommend playing around with your ports and cables -- it gained me my NvFlash blobs after an evening of hair-pulling.
What driver(s) shave you been using/trying?

Thank you.
MartyHulskemper said:
I had this too, when flashing with the 700 attached to a back USB port (which is the primary set, should be fine in tiself), but via an extension cable (apparently NOT OK). I really recommend playing around with your ports and cables -- it gained me my NvFlash blobs after an evening of hair-pulling.
What driver(s) shave you been using/trying?
Click to expand...
Click to collapse
I exchanged the tablet for a new one. I still think I could have brought it back from the dead. One of the questions I asked in another thread was "would it be possible to make a blob with my device specific code from a TWRP backup"? I also understand that nvflash can only be used with the 9.x.x.x bootloaders but those are not compatible with Jelly Bean 4.2. Kinda stinks since I would have liked to stayed on a 9.x.x.x bootloader but, AFAIK you have to update the bootloader to 10.x.x.x in order do install Jelly Bean.
I am only asking for the sake of knowledge as I am one who does not like not being able to solve a problem. Also maybe the infromation contained in a TWRP backup file does not go deep enough to rebuild a blob from it to restore your device?
Thanks for the help.
Cole:good:

33colburn said:
"would it be possible to make a blob with my device specific code from a TWRP backup"?
Click to expand...
Click to collapse
You mean a blob for wheelie&nvflash that contains your bootloader? No.
33colburn said:
I also understand that nvflash can only be used with the 9.x.x.x bootloaders
Click to expand...
Click to collapse
Not true. You can only create the blob file for wheelie with a hacked 9.4.5.30 bootloader, and to install that, you must be on a <= 9.4.5.26 bootloader. After you have this blob and the other backup files, you can upgrade to whatever bootloader you want and still use nvflash with your saved blob. Just don't ever lose it, it's your unique key to nvflash.

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.