yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] X0LARIUM:
hey [MENTION=3110798]WugFresh[/MENTION] I got the 1.9.4 update and it also updated some modified boot image of Lollipop? Can I unlock and root it then?

EDIT: I can confirm the 1.9.4 can SUCCESSFULLY ROOT and FLash Custom Recover y on the official image flashed on 2012 Nexus 7, Grouper/nakasi.
[Nexus 7 Android Development] wfm_de:
There is a lollipop-version of TiBu awailable. Search the Internet.

---------- Post added at 09:46 AM ---------- Previous post was at 09:26 AM ----------

A short description of my long way to lollipop on my nexus 10:

I tried to install the OTA with TWRP. The script told me, it seems,I have 4.3 android installed, while 4.4 was running since it was available.

I installed stock-recovery with nrt and tried to install the OTA. After patching several things the script ended with error telling me /system is full. My nexus 10 was now bricked. I could only boot into bootloader or recovery. Tried factory-reset, did not help.

I booted into bootloader-mode and installed the factory-image with the factory-install-procedure.

Went well. Then I rooted with cf-autoroot and restored my apps with nrt.

Now all is OK !

This was my long way to lollipop.
[Nexus 7 Android Development] Stransky:
Just flashed Android 5 Lollipop using the Toolkit and then rooted and installed TWRP. Brilliant program.

Stransky
[Nexus 7 Android Development] 2ma:
Is your bootloader 3.something? I think you ran into this problem: http://xdaforums.com/showthread.php?t=2417097

Just flash the bootloader from the topic I linked, since the one in the factory image version is not correctly signed as far as I can understand. Then flash the factory image again and it should work.

At least that worked for me!
[Nexus 7 Android Development] dimbo33:
I also just flashed 5.0 using the toolkit. Many thanks to wugfresh.

Went without a hitch, although got the invalid state message when the kit tried to install the bootloader. In any case was already running v 4.23 so no further action needed.

Fortunately I had read from previous posts that it takes the 2012 wifi model an age to boot up after the flash so no panic, I just let it take its time (around 10 minutes in my case).

Rooting went without a hitch via the toolkit. Titanium Backup as already pointed out needs an independent installation to work currently with 5.0 edit: this seems to now be sorted on the play store after an update to TiBu.

One thing that puts me off starting from scratch again with a factory reset/new firmware is the amount of time it takes to re-install all the apps/data, but TiBu has an amazing feature that I used for the first time today where you create a flashable zip of all your apps plus data and then re-install them from recovery. So all apps plus data were installed in one shot from my previous installation. Excellent.
[Nexus 7 Android Development] X0LARIUM:
Big big thanks to Wug and his team(if he has one :P)
[Nexus 7 Android Development] RainGater:
I tried to root with v1.9.4 and still not able to do it. It installs BusyBox but SuperSU is missing. Don't know why it works for some and not for me.

It's a clean flash from 4.4.4 after wiping everything out.
[Nexus 7 Android Development] dimbo33:
Did you update the tool kit so it knows you're running 5.0 now? Mine was set to any build as I came from cm11.

I had to update it to reflect the fact that the unit is now running 5.0. After this the toolkit downloaded a modified boot image an a kernel relating to 5.0. After that the rooting worked perfectly.
[Nexus 7 Android Development] Shinare:
I used NRT to flash 5.0 on my N7 yesterday,and the on my wife's N7 last night and on both tablet I got this same error while flashing stock. Not sure if its a prblem or not as it seems to have laded 5.0 just fine. But I thought I would throw in my 2 cents that this also happened to me, twice on separate N7 tablets.
[Nexus 7 Android Development] dimbo33:
I think there's something wrong with the bootloader included in the factory image. It wouldn't be the first time.

For me and I'm guessing for you too this is not a problem as we were already running the 4.23 bootloader in question.
[Nexus 7 Android Development] ghalalb:
I've used NRT to flash factory and root. The only problem is root won't grant to all root apps. For example flashify gained root, busybox hasn't. All apps are showing in the granted list though don't have root access
[Nexus 7 Android Development] dimbo33:
That may well be to do with the apps not being 5.0 compatible yet.
[Nexus 7 Android Development] mkiker2089:
Still not working for me

If you

- have a stock recovery

- got the update live from google

Then the NRT doesn't work. I tried todays fresh update 1.9.4 and it does the same thing, claims it's rooted but when I open SU it says "no binary installed."

Any advice what to try next? Is there a difference between SU programs? Installing quick boot? I hate to change settings but I don't know why it's failing.

---------- Post added at 02:54 PM ---------- Previous post was at 02:28 PM ----------

Is this the problem

http://www.androidorigin.com/google-nexus-5-7-root-lollipop-update-android-5-0/
[Nexus 7 Android Development] todivefor:
I didn't do that and root/SU works fine. My version was 1.93 (yesterday). I came from CM 11, so had my setup as Nexus 7 WIFI and any android version. I did "Flash stock + root." I booted up and signed into Google. I then did "Root and also flash custom recovery (TWRP)." I actually went through this procedure twice as Tibu would not work (said not rooted). After second I found that I needed a test Tibu. Installed it and all is working fine. I also installed Busybox as directions indicated.
[Nexus 7 Android Development] mkiker2089:
Right, but you reflashed your tablet as well. I'm trying to keep stock recovery and have updated to 5 instead of wiping it and starting over.
[Nexus 7 Android Development] RandyboY:
Anyone knows whan I'm missing when this happens when clicking the "Download + Update ....." button? It happened on *.9.4 earlier today also.
[Nexus 7 Android Development] mkiker2089:
You'll have to re-install. Something broke which killed the updater.

---------- Post added at 07:04 PM ---------- Previous post was at 07:03 PM ----------

Root still isn't working though unless you are willing to wipe and re-flash.
[Nexus 7 Android Development] havensed:
Well now I don't know why it didn't work out for you, but worked out correct for me, my nexus 7 2012 WiFi edition rooted first time and super su was there join completion.
[Nexus 7 Android Development] ichigo_kurosaki:
It does. Trust me. after flashing the factory image using it i immediately rooted as [MENTION=3110798]WugFresh[/MENTION] released the modified lrx21P kernel and it went through just fine. Haven't installed busybox as i have doubts of its compatibility and i found a busybox x in the playstore which claims "the only busybox compatible with lollipop"
[Nexus 7 Android Development] mkiker2089:
No, as has been said by many, it doesn't "root."

It will re-flash and root but for those who don't need to wipe their tablet this toolkit does not install root binaries or the icon to control them.
[Nexus 7 Android Development] havensed:
I always wipe and reflash so I get a true update, and I don't have the lag or root issues because of it. I did have the titanium backup issue. But downloaded new version from link here in xda. Works fine now.
[Nexus 7 Android Development] WugFresh:
There were previously issues. They should be resolved in the latest version. And root should be no problem.
[Nexus 7 Android Development] WugFresh:
I will look into the busybox stuff, so we can get some clarification. I will reach out to the dev of the new X one, and ask the dev of the current installer.

{{ WugFresh }}
[Nexus 7 Android Development] Stransky:
Hi

Currently on Lollipop via WUGs NRT and rooted. Running like a dream. Apps downloaded from Google auto after sign-in with some exceptions that are not yet compatible. I.e. ROM Toolbox Pro. Have emailed dev regarding updating for Lollipop.

Stransky

Edit:

Downloaded Busybox Pro and installed and appears to be running OK.
[Nexus 7 Android Development] ichigo_kurosaki:
neh..i think it's not necessary anymore bro.:D see, the stericson busybox packaged into your root files had an update aerlier today and it seems to have support for Lollipop now. and so i guess, i was just in time to install it. But can you please explain to me what is the role of busybox in the root stuff? i really don't get it but i have had come across that busybox things on custom roms i have used on my sensation in the past.:D
[Nexus 7 Android Development] RASTAVIPER:
My thanks and respect to Wug for the fast update of his toolkit.

I upgraded with dirty flash over stock 4.4.4 and rooted, with only one small problem.

After flashing boot.img, my phone wasn't rebooting and toolkit couldn't do anything,like restart phone etc.

So, I manually entered recovery and then I decided to continue by flashing system.img. After that rebooted normally to new Os.

Any idea why it got stuck then?

Unleashed by my Nexus 4
[Nexus 7 Android Development] Scipizoa:
When I flashed I got the 4.04 boot loader. With the images. Was that not what I supposed to get?

Sent from my Nexus 7
[Nexus 7 Android Development] Paulikid:
Flashing the 4.23 bootloader and flashing Android 5.0 worked like a charm. I have one little problem: After rebooting my device shows just 8GB internal memory. Wiping the N7 doesn´t help. Anny suggestions?

Edit: Nevermind, Factory reset must be made BEFORE rooting, everything is okay now.
[Nexus 7 Android Development] X0LARIUM:
2 things I want to tell people who can't get it to work: make sure you are running the latest NRT, in my case 1.9.4. Also, make sure to check your downloaded image's MD5s. This is a very important step and usually gets ignored.
[Nexus 7 Android Development] Scipizoa:
Glad to hear your issues resolved :)
[Nexus 7 Android Development] Bradleyd444:
Stuck at Google screen after 5.0 update

After using NRT to update to 5.0 I am stuck at the Google screen before the booting screen. I looked back at the log and noticed a few thing.

At "writing Bootloader" it failed for invalid state

at "sending System" it failed for unknown error

at "rebooting to bootloader" directly after sending system failed for unknown error

at "sending user dater" it failed for invalid argument

then failed at "rebooting Bootloader for unknown error after that.

now i am stuck, I cannot boot, I obviously cannot get into TWRP to restore. I have tried doing it multiple times and even when back to 4.4 and 4.2. all failed for various reasons.

Any ideas?
[Nexus 7 Android Development] pkelly517:
Did you have the right device selected when you flashed?

If you did, there's always a way back with a nexus. If not...
[Nexus 7 Android Development] Bradleyd444:
pretty sure I did select the right one. but still cant get it fixed.
[Nexus 7 Android Development] zedmarcus:
OK, I've got the same as you, low internal memory after flashing. I didn't factory reset before flashing. How did you fix it? Did you have to factory reset then flash again?
[Nexus 7 Android Development] Paulikid:
I did the factory reset (Settings - Backup & Restore - Factory Reset - Delete everything) after flashing. I don´t know if I named it right, because my menu is in german. ;)

After reboot everything was fine. It´s important that you don´t root the N7 before, otherwise it boots into TWRP when you try to do the factory reset. The factory reset has to be dont from the stock recovery.
[Nexus 7 Android Development] Bradleyd444:
Finally got it back to a point that I could flash a Rom, I went back through to "Flash Stock + Unroot" and it did it again. I am now working on restoring my backup. Any ideas why when I Flash Stock + Unroot it bricks it?
[Nexus 7 Android Development] mkiker2089:
Still no good. Root just is not installed. The app is missing and if I go to the play store and install it the binaries are missing. It seems that people who got the update live and did not wipe / re-flash aren't able to get root with the toolkit based on others comments as well as my experience

Information: Waiting for your device...

Information: Device Detected

Information: Checking ADB Status

adb devices

List of devices attached

015d172c9a50140d	device

ADB Status: Device Connected

Information: Rebooting your device into bootloader mode...

adb reboot bootloader

Information: Checking Fastboot Status

fastboot devices

Information: Checking Fastboot Status

fastboot devices

015d172c9a50140d	fastboot

Fastboot Status: Device Connected

Information: Booting modified boot.img to enable running privileged commands...

fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Modified_Boot\modified_boot_nakasi_5.0.0_LRX21P.img"

Information: Waiting for your device...

Information: Device Detected

Information: Pushing root files to your device...

adb push "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\busybox-signed.zip" "/sdcard/!ReadyToFlash/Root_Files/busybox-signed.zip"

adb push "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\BETA-SuperSU-v2.19.zip" "/sdcard/!ReadyToFlash/Root_Files/BETA-SuperSU-v2.19.zip"

adb push "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\openrecoveryscript" "/cache/recovery/openrecoveryscript"

Information: Rebooting your device into bootloader mode...

adb reboot bootloader

Information: Checking Fastboot Status

fastboot devices

015d172c9a50140d	fastboot

Fastboot Status: Device Connected

Information: Flashing Root Kernel...

fastboot flash boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\root_kernel_nakasi_lrx21p.img"

Information: Booting TWRP Temporarily...

fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\openrecovery-twrp-2.8.1.0-grouper.img"

Information: Rooting...

Information: Waiting for your device...

Information: Device Detected
[Nexus 7 Android Development] ichigo_kurosaki:
So those who updated via ota are not able to root? Coz in my case i flashed the factory image (i had a hellish experience of trying and retrying juat because of .tar format not accepted on the toolkit 1.9.3) and rooted afterwards without running into problems.:D
[Nexus 7 Android Development] Stransky:
Hi

Don't understand why people are having so much trouble updating to 5 with the Toolkit. I used the "download and update stock" option and the toolkit done the rest. Same with rooting' selected root with custom recovery and away it went. Only problem I have is, as stated previous post, some apps currently not compatible and will not install. Error '505' appears.

Stransky.
[Nexus 7 Android Development] hazwheel:
Well, flashed stock and unroot on my n4 , still got the spinning dots after 30 minutes, safe to say it didn't work.... Had no problems with my n7, never had a problem before. Toolkit said successful too, darn it
[Nexus 7 Android Development] CBers:
My Nexus 7 has been rooted since just after it was released and I have used this toolkit many times since it was released, so I am not a novice., but I can't update my Nexus 7 2012 WiFi.

I select Flash Stock + Unroot for Lollipop, but get error messages:

Flash Stock + Unroot...
------------------------------------------------------------------

erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.050s]
finished. total time: 0.051s
erasing 'recovery'...
OKAY [ 0.054s]
finished. total time: 0.054s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.076s]
finished. total time: 0.078s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.477s]
finished. total time: 1.478s

sending 'bootloader' (2100 KB)...
OKAY [ 0.269s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.410s
rebooting into bootloader...
OKAY [ 0.019s]
finished. total time: 0.020s

sending 'boot' (5146 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.003s

sending 'recovery' (5682 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.003s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.003s

sending 'system' (648787 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.003s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.004s

sending 'userdata' (104289 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
rebooting...

finished. total time: 0.001s

Booting up your freshly flashed stock device...
------------------------------------------------------------------

Wait for your device to finish booting up...

- It may appear to be boot looping; just wait...

- It could take 5-10 minutes; please be patient...

When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.

Press any key to exit...

All I get in the Live log is:

Live log initiated.

Information: Checking Fastboot Status
fastboot devices
xxxxxxxxxxxxxxxx	fastboot

Fastboot Status: Device Connected
Launching flashstock.bat

Any ideas please ??

Thanks.
[Nexus 7 Android Development] Rafosky:
Thank you man!!! It was that. It's working now!!!

---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------

Probably you are running the same problem I had. Check the link in a post over this one.
[Nexus 7 Android Development] CBers:
Yes, just realised by bootloader is 4.03 - will have to update it I guess.
[Nexus 7 Android Development] negruv1:
On Nexus 4, using force flash the update passes ok, but i get stuck at the spinning dots. Disabling force flash gets me this error:

Flash Stock + Unroot...

------------------------------------------------------------------

sending 'bootloader' (2264 KB)...

OKAY [ 0.075s]

writing 'bootloader'...

OKAY [ 0.307s]

finished. total time: 0.387s

rebooting into bootloader...

OKAY [ 0.004s]

finished. total time: 0.005s

sending 'radio' (45537 KB)...

OKAY [ 1.441s]

writing 'radio'...

OKAY [ 2.589s]

finished. total time: 4.035s

rebooting into bootloader...

OKAY [ 0.002s]

finished. total time: 0.003s

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

failed to allocate 829072920 bytes

error: update package missing system.img
[Nexus 7 Android Development] RandyboY:
This was solved in v.1.9.7. I did not do anything else but let the program update itself as i was away for the weekend.

All good now, thanks :)
[Nexus 7 Android Development] hazwheel:
[MENTION=3110798]WugFresh[/MENTION] OK, tried to install lollipop on my n4, no errors reported, but bootloops at the spinning dots. Thought I'd try to go back to KitKat instead, exactly the same problem now, now matter which android version I try, bootloops with no errors during the flashing process. Any ideas? Can't do anything with the phone now. I flashed twrp manually, and was able to get into it but obviously the phone has been wiped during the numerous flashing attempts and I don't see any way of getting a nandrojd or zip back on the n4 to try and flash. Any ideas?
[Nexus 7 Android Development] Mr-Glass:
Have you tried to do a wipe in TWRP, not complete but similar to a system reset... Also not sure with N4 but with my N5 and N7 if I am in TWRP I am able to copy over a backup... just thoughts
[Nexus 7 Android Development] hazwheel:
Tried to wipe in twrp, no go, can't mount cache etc. errors. And no , not able to copy files over in twrp
[Nexus 7 Android Development] negruv1:
FOR EVERYONE STUCK IN BOOTLOOP on Nexus 4:

Flash flash everything normally. When the phone is stuck on the spinning circles after 15-20 minutes, power off.

Boot into fastboot by hitting the volume volume down+power buttons and navigate to Recovery, press power.

You'll be greeted with the image of a dead Android. Press Volume Up and Power at the same time (a couple of times; the timing is finicky). Once in Recovery, select "Wipe data/factory reset" and execute. Once it's done, reboot and let it load.

Your Nexus 4 should boot normally this time, but give it about 10 minutes.

Instruction by Hexykins from Androidpolice.com
[Nexus 7 Android Development] hazwheel:
Got this method in another thread, but yes, it worked, rather pleased, although it cost me a new phone when she realised I'd got my n4 going again! Darn it
[Nexus 7 Android Development] WugFresh:
To deal with this, I think I am going to add another check box in the flash stock options to do a "Post-Flash Factory Reset" that will simply issue the:

fastboot erase data

fastboot erase cache

Cmds at the end of the flash which is equivalent to a factory reset.

Users can then chose to enable this setting.
[Nexus 7 Android Development] hazwheel:
Yes, good idea, that was a worrying 24hours [emoji27]
[Nexus 7 Android Development] joelbon:
Dumb move

I just used this tool on my new N6. That was really stupid! It looks like it installed the root kernel and now the phone won't boot. Does anyone have the files that I will need in order to fix this?

On the bootloader logs screen it just says boot up failed. When I got the phone, I received an update and installed. So I am on the latest software of Lollipop 5.0.

Will someone please help me? Thanks

Oh forgot that I entered the phone as a Nexus 5. I really don't know what I was thinking. I am an idiot.
[Nexus 7 Android Development] gerardo87:
Unzip the factory image of your phone and then flash permanent the only boot.img using the advanced options of toolkit [emoji6]
[Nexus 7 Android Development] joelbon:
The problem is there isn't a factory image right now. I looked on Google's site for it and there isn't any listing for the Nexus 6 yet.
[Nexus 7 Android Development] WugFresh:
It's not the end of the world, but your device will be out of commission until there is a stock/custom boot.img available for your N6. Google will hopefully roll out the factory packs soon, and kernel devs are already working on cool things for N6. If there are any OTA.zips available for the device you can strip the boot.img from that as well, but I don't think there are yet.

Regards

{{ WugFresh }}
[Nexus 7 Android Development] djkinetic:
Not trying to be mean but I'm laughing so hard right now...only thing you can hope for is the factory image or another user pulling their boot.img for you. I would do it if I had the phone already.
[Nexus 7 Android Development] joelbon:
Thanks, that is what I was hoping for, but I know they are just now trickling out. I will just wait and hope either someone is nice enough to do that or Google posts the Factory image in a pretty quick fashion.

It is sort of like having to wait for the phone in the mail after you order it, but I can look at it pick it up, but can't really play with it. I think this is worse than waiting for it in the mail. lol
[Nexus 7 Android Development] Deeco7:
Does NRT now support root for lollipop on the N5?