yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] b3n_:
Hi,

I've used NRT yesterday to update my 5.0.1 nexus 5 to 5.1. When I rebooted the device I got to the setup screen and then two errors kept popping up. "Unfortunately NFC has stopped working" and "Unfortunately phone has stopped working". They kept popping up then the phone rebooted and the same thing happened. Kind of like an extended boot loop. I have since flashed back to 5.0.1 which works fine. Any suggestions or ideas what went wrong?

Update: I have tried both 5.1 releases the result is the same.

Thanks.
[Nexus 7 Android Development] pkelly517:
I think this is why Android includes the logcat capability.

Try it. You may get a real solution.
[Nexus 7 Android Development] b3n_:
I can't even get android started so where would I get those logs from? As I need my phone for work I'm going to stick with 5.0.1 for now. I did some searching around and there seem to be other people having the same issue. I tried manually flashing the images but system doesn't flash due to the size being too large.
[Nexus 7 Android Development] pkelly517:
adb logcat
[Nexus 7 Android Development] b3n_:
I might try that again on the weekend. For now I need the phone and won't flash 5.1 again. Was just wondering if anyone else ran into the same issue.
[Nexus 7 Android Development] rabaker07:
All I know is that the wugfresh nexus root toolkit is the way to go. I discovered that windows application early on in my Nexus 5 ownership and haven't looked back. Sure, back in the day I would SDK and ADB and root and rom when it was cool and almost mandatory to bring in the cutting edge features on my incredible and galaxy nexus but there's just no need for it anymore with Lollipop having all the must-haves. And with the toolkit all I did was fire it up and the app put my N5 to sleep, poured it some warm milk, and rubbed its belly until it purred. 5 minutes later I'm up from 5.01 to 5.1 and I still have root, TWRP, and didn't even have to lose my ex-girlfriends phone number with a wipe. It even pre-downloaded 5.1 for me and checked md5. I really can't say enough good things about how painfree it is. Essentially 1 click.

If no-wipe turns out to be crap, I'll just click the OTHER button and be good to go. Thanks WUG!! You ROCK!
[Nexus 7 Android Development] WugFresh:
Google Changes New and Old Factory Packs for Nakasi and Nakasig

Quick heads up - for Nakasi/Nakasig (Nexus7 2012 Wifi/Mobile) owners, you should read this: http://www.wugfresh.com/google-changes-nakasi-and-nakasig-factory-packs/

Cheers,

{{ WugFresh }}
[Nexus 7 Android Development] 71baker:
Been struggling for a couple hours now. After updating to 2.0.5 i cannot download the twrp that NRT uses. Seems it cannot find the file and when i download manually the name doesn't match. If i rename the file it says md5 doesnt match.

There is something not working as intended here. I first thought it might be because i updated with the nrt updater but after installing again it still does not work...
[Nexus 7 Android Development] rmadrid20:
Same here
[Nexus 7 Android Development] rbnet.it:
Same here.
[Nexus 7 Android Development] paperjam252:
Hashcheck mismatch for me too. Tried downloading the most recent version from TWRP but the app won't recognize that either.
[Nexus 7 Android Development] ClintE1956:
I always download latest TWRP directly from their site then flash it using existing TWRP. I think if you have 2.8.4 or later you can flash latest version that way according to twrp instructions.
[Nexus 7 Android Development] 71baker:
The problem is that NRT uses the version it can't download for some things despite what you have installed.

I forgot to mention earlier that i am on Nexus 5.
[Nexus 7 Android Development] ClintE1956:
I didn't realize the kit needs a specific version of twrp installed on the target device for certain functions.

Aahh wish I would have bought the N5 before they quit selling them. Hopefully there will be a similar Nexus device in the next year or so. Beautiful phone, that N5. My son has the N6, he's quite pleased with it, but he has much bigger hands than me; I think he's around 6' 6" tall.
[Nexus 7 Android Development] WugFresh:
Sorry bout that earlier. Its been resolved, just hit update in the kit.
[Nexus 7 Android Development] japancakes:
I just ran into the exact same issue. Came from 5.0.1 with ElementalX and stock ROM. Currently going back to 5.0.1.

Solution would be greatly appreciated.
[Nexus 7 Android Development] SkOrPn:
Quick question to anyone using a Nexus 7 2012 Grouper. I used NRT 2.0.5 a few days ago to go back to full stock. Instead of using the previous images of KK, I selected the latest 5.1 image, that just seemed like the appropriate thing to do, lol. Anyway after getting the device back to full stock, I immediate flashed TWRP 2860 (using NRT) and then flashed Chroma 5.1_r3, latest gapps, latest SU 2.46. And although it runs great, I lost my entire 32GB storage space, well almost all of it. I only have 3GB free space and have not put anything on it yet. Since no one else in the Chroma thread has the same problem, I can only assume it is the Google 5.1 images that did this? I did a Factory Wipe and re-installed chroma 5.1_r3 and it did not bring back the storage space, although it runs fantastic.

Should I now try going back to stock yet again, but this time use KK instead? Any ideas why flashing back to stock would use up all my free space? One last thing, how do I factory wipe using the stock bootloader or stock recovery? The instructions to factory wipe via button combinations do not work on my device, so I need to probably do it via Fastboot commands?

Any tips on my next move? lol thanks guys...
[Nexus 7 Android Development] WugFresh:
http://www.wugfresh.com/faqs/incorrect-internal-storage-space/
[Nexus 7 Android Development] SkOrPn:
Thank you WugFresh, thank you very much for the info. After finishing off my new setup, I am down to 720 MB which kinda worried me. I will try and fix it now, thanks man :good:
[Nexus 7 Android Development] SkOrPn:
Hmm, OK well everything on that page did not resolve it. I had already done a Factory Reset, not once but twice, but decided to do it a 3rd time and that did not work. Then I tried the bottom part of that page "advanced utilities’ > ‘fastboot format’ > and then have it format system and userdata – then use “soft brick mode” to “Flash Stock + Unroot” one more time" and I did everything to the letter T. I only got back about 1gb of space, for a total of 1.7GB free.

So, all I can think of now after three factory wipes and two stock flashes, is that the 5.1 image that NRT is downloading does not agree with my device? I mean what else can explain it? I'm going to do it a 4th time, but this time I am going to try using one of the older images? Wug, anything else you think I should try? Thanks again for your help on this.

Oh, below are screenshots I just took.

This image is of the Windows Explorer Properties when I right click on the Nexus 7 device. Android see's a 28.6 GB device but Windows is seeing a 6 GB storage device. Now I'm even more confused.

EDIT: OK, I got it fixed YAY! However, I flashed 5.0 using NRT and that did not fix it. Then I Factory Wiped and flashed 4.4.4 and that did NOT fix it. Then I flashed 4.4.3 to stock and that did NOT fix it, then I Factory Wiped like a 7th time and that did not fix it, so then instead of using Fastboot or ADB, I booted into the STOCK recovery (after figuring out how to do that, which has been two years since the last time I seen the stock recovery mode) and did a Factory Wipe. When I booted stock 4.4.3 back up it was then back to normal storage size. So ONLY the Stock Recovery can fix it when these things happen? Not TWRP, not any Fastboot commands, only STOCK RECOVERY? I wasn't aware of that... I thought custom recoveries had the same exact abilities, yet TWRP could not get it done after like 7 tries. So now, I am wondering if its safe to go back to TWRP and restore my 5.1 backup? lol
[Nexus 7 Android Development] motorazrv3:
Congrats. Yeah had the same thing on my 16 GB grouper after using nrt to go from 5.0.2 to 5.1. If you had used Google for a search there are plenty sites that explain to enter stock recovery and do the factory reset there. Maybe you over red it and only saw the factory reset.

You solved it, now you can go on.
[Nexus 7 Android Development] SkOrPn:
Yeah, I just saw the Factory Reset part, which can be done even inside the ROM. And never in a million years would I think a TWRP or CWM Factory Reset was not identical to the Stock Recoveries Factory Reset. And yes, it was Google that pointed me to using the Stock Recovery ;) I just took too long to search for the problem, because I thought I had already done a Factory Reset, LOL. So if you think about it, it should be called doing a "Factory Factory Reset" haha
[Nexus 7 Android Development] WugFresh:
I will try to emphasize the stock recovery aspect on my site. I thought that's what I wrote but I will make it more clear.

Yes it is strange that TWRP doesn't behave the same, but that is what I experienced as well.
[Nexus 7 Android Development] WugFresh:
Also, there is a setting in the flash stock interface called "post flash factory reset" which walks you through the stock recovery reset.
[Nexus 7 Android Development] SkOrPn:
Ahh, no biggie Wug. For vets like me some of us just forget all about the stock stuff. I have not ran a device on stock anything since 2007, even my very first Android device, the original Nexus and then the 1 minute old Vibrant (I waited in line overnight for that device) all got custom roms as soon as the first custom ROM was released. I still have not tried a Stock ROM on my 2 year old N7 and as soon as I flash stock, I then flash something custom over it. However, thanks to Google acquiring XDA Developers, I might be forced to learn to run Stock, or just give up on Android altogether. I'm just not willing to be told how to run a device that I pay for. So, I have been busy downloading everything I can here in the forums before Google pulls all the best download links.

Anyway, thanks for your fantastic NRT software. It has saved me many times now... :good:
[Nexus 7 Android Development] arnarhelgi:
YES! version 2.0.5 fixed the download issues in 2.0.4. Thanks Wug!
[Nexus 7 Android Development] WugFresh:
FYI - this was an April's fools prank. Not gonna lie, it just tricked me after I saw your post and looked it up.
[Nexus 7 Android Development] ClintE1956:
I'm sure if Google forces xda to pull all the custom stuff, there will be some other site that will pick up the slack. Too many people out there, as you so aptly put it, not willing to be told how to use something that they paid for.
[Nexus 7 Android Development] WugFresh:
Lol. Its an april fools prank. Check the date of the XDA article.
[Nexus 7 Android Development] ClintE1956:
duh me they got me too grrr...
[Nexus 7 Android Development] SkOrPn:
Yeah, my friend just informed me of that too. Freggin 7 days later and they still got me REALLY good.... HAHAHAHA, and to think I spent the last 2 hours nearly in tears...
[Nexus 7 Android Development] WugFresh:
Newly released [N7 2012 Mobile] Nakasig LMY47D 5.1.0 added to the kit. Just hit update to get the new lists. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] AvgPhoneUser:
Hey Sir. I really appreciate your work and thanks to you I could unbrick my device. Can you please add the 5.1 stock images for the Nexus 7 2013
[Nexus 7 Android Development] WugFresh:
They don't exist https://developers.google.com/android/nexus/images
[Nexus 7 Android Development] yoavain:
Nexus 4 Android 5.1 images are up

Nexus 4 Android 5.1 images are up:

https://dl.google.com/dl/android/aosp/occam-lmy47o-factory-cae68e81.tgz
[Nexus 7 Android Development] jb.traveller:
They are up now.
[Nexus 7 Android Development] the_gunner:
Stuck on package extraction....

So I just downloaded the 5.1 factory image from Google for the N7 '13 Wifi, fired up NRT v2.0.5, and NRT is hanging at 'Extracting factory image package'. The extraction window reports (Not Responding). It's been about 30 minutes and it hasn't budged.

Any thoughts as to why this is happening?

Thanks,

Gunner
[Nexus 7 Android Development] WugFresh:
Your comp maybe just ran out of memory. Just force kill everything, (including instances of 7zip, which is doing the extraction) and try again.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Thanks. Will get this added shortly.

{{ WugFresh }}
[Nexus 7 Android Development] tamanaco:
Patiently waiting..................
[Nexus 7 Android Development] bovirus:
[MENTION=3110798]WugFresh[/MENTION]

Please update (if are not updated) TWRP 2.8.6.0 for Asus Nexus 7 2012 Wifi and 2013 Wifi.

How can just update the TWRP (from 2.8.5.0 to 2.8.6.0) with NRT?
[Nexus 7 Android Development] ClintE1956:
I just followed the instructions on the TWRP website concerning flashing latest TWRP in recovery:

http://twrp.me/devices/asusnexus72012wifi.html

and

http://twrp.me/devices/asusnexus72013wifi.html
[Nexus 7 Android Development] WugFresh:
Advanced utilities > Fastboot Flash > Recovery > Latest TWRP
[Nexus 7 Android Development] WugFresh:
All latest packs are supported and included now.
[Nexus 7 Android Development] AvgPhoneUser:
Well if you want to update TWRP just download TWRP manager from Playstore and press install. If it detects that you have an older version of TWRP then you just update it.
[Nexus 7 Android Development] saj2001ind:
can I use this to force non encryption on stock unrooted nexus 6 running 5.1 build LMY47I
[Nexus 7 Android Development] WugFresh:
Yes, you just have to unlock the bootloader first (which wipes data), and then do it with the kit:

Advanced Utilities > Fastboot Flash > Boot/Kernel > "No Force Encrypt" button. (which will wipe data again).

So just backup things first if you need to, and then go for it.

{{ WugFresh }}
[Nexus 7 Android Development] agentfazexx:
Having issues...

So since I can't get CM12.1 to boot I opted to go back to stock. After installing stock 5.0.2 and re-locking the bootloader, it prompts me for my decryption password before boot, which I was never decrypted. After entering anything as a password it says the password is right but data is corrupt so I have to do a factory reset. After erasing, it reboots and spins at the boot animation forever and never boots.

Now what?
[Nexus 7 Android Development] agentfazexx:
Now I can't get into TWRP, finally got stock 5.1 to boot. Selected root + custom recovery and it just reboots into the stock OS. When I reboot to recovery from the bootloader, I get the "dead" Android.
[Nexus 7 Android Development] pkelly517:
Someone's not following all the directions.

Okay, that's an assumption, but one I've seen more than once in this thread.

Let NRT create logs and link them. Don't make us guess what's happening.
[Nexus 7 Android Development] bovirus:
I downloaded the Asus Nexus7 2012 Wi-Fi Android updated (5.0.2. to 5.1.0) via System Update.

I select reboot and Install, start the TWRP but nothing else.

Why TWRP (instalede by NRT) is not compatible with official System update?

Can I run manually the system update? Where can I get the file downloaded by System update app?
[Nexus 7 Android Development] saj2001ind:
are you trying to install official OTA using TWRP ?
[Nexus 7 Android Development] bovirus:
No. The table found automatically the update. Ask to download. Then ask to reboot and install.

Then started TWRP in the main menu but didn't start automatically the update (loading and running).

It works if you have original stock recovery.
[Nexus 7 Android Development] agentfazexx:
Figured out my last issue...

Can't go back to stock.. Getting these errors while in the bootloader

Flash Stock + Unroot...

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

erasing 'boot'...

FAILED (command write failed (Invalid argument))

finished. total time: -0.000s

erasing 'cache'...

FAILED (command write failed (Invalid argument))

finished. total time: -0.000s

erasing 'recovery'...

FAILED (command write failed (No such device or address))

finished. total time: 0.011s

erasing 'system'...

FAILED (command write failed (Invalid argument))

finished. total time: -0.000s

erasing 'userdata'...

FAILED (command write failed (No such device or address))

finished. total time: 0.004s

sending 'bootloader' (2100 KB)...

FAILED (command write failed (No such device or address))

finished. total time: 0.016s

rebooting into bootloader...

FAILED (command write failed (Unknown error))

finished. total time: 5.005s

error: out of memory

rebooting into bootloader...

FAILED (command write failed (Unknown error))

finished. total time: 5.003s
[Nexus 7 Android Development] agentfazexx:
Anyone?
[Nexus 7 Android Development] Spades2006:
i have 32gig flo, i was running 4.4.4 with TWRP and ElementalX kernel. i tried to flash 5.02 with NRT and it all went wrong. first, while flashing it got stuck at the bootloader screen. - pics / screenshots here. then i realized the bootloader was locked, so i tried to unlock the bootloader with NRT and it got stuck in a boot loop. i pulled battery and tried the “Flash Stock + Unroot” feature to go back to stock 4.4 and the command prompt came up and said it was successful, but it's stuck in another bootloop, and now i can't even get back to the bootloader menu. i didn't use force flash mode and it said to try that but i can't get to that point. am i totally boned? :crying:

edit: got into bootloader menu, used force flash mode to go flash stock 4.4.4. and it's stuck in a boot loop again.

edit2: it's been half an hour, still looping at the scene with the blue, green, red, and yellow circles dancing around. i just want to get back to 4.4.4 which was working a few hours ago, help would be greatly appreciated. here's the log from the "successful" flash back to stock 4.4.4.

Flash Stock + Unroot...

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

sending 'bootloader' (3911 KB)...

OKAY [ 0.138s]

writing 'bootloader'...

OKAY [ 1.356s]

finished. total time: 1.499s

rebooting into bootloader...

OKAY [ 0.007s]

finished. total time: 0.008s

sending 'boot' (7050 KB)...

OKAY [ 0.237s]

writing 'boot'...

OKAY [ 0.442s]

finished. total time: 0.682s

rebooting into bootloader...

OKAY [ 0.007s]

finished. total time: 0.009s

sending 'recovery' (7598 KB)...

OKAY [ 0.261s]

writing 'recovery'...

OKAY [ 0.459s]

finished. total time: 0.723s

rebooting into bootloader...

OKAY [ 0.006s]

finished. total time: 0.008s

erasing 'system'...

OKAY [ 1.296s]

sending 'system' (736772 KB)...

OKAY [ 24.331s]

writing 'system'...

OKAY [ 32.407s]

finished. total time: 58.037s

rebooting into bootloader...

OKAY [ 0.006s]

finished. total time: 0.008s

rebooting...

finished. total time: 0.005s

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...
[Nexus 7 Android Development] WugFresh:
Try a standard factory reset from stock recovery https://support.google.com/nexus/answer/4596836?hl=en
[Nexus 7 Android Development] Spades2006:
just did this, still stuck at dancing circles screen. what next?

thanks.
[Nexus 7 Android Development] WugFresh:
Reflash stock again, tick the box for post flash factory reset this time so you preform that step before first boot.
[Nexus 7 Android Development] agentfazexx:
Can anyone help with this? My tablet is unusable.
[Nexus 7 Android Development] WugFresh:
Have you tried an alternate usb port?
[Nexus 7 Android Development] agentfazexx:
Not yet, I'll try that when I get home. That port does work fine though, and it sees the tablet.
[Nexus 7 Android Development] WugFresh:
Seeing your tablet is one thing. Successfully executing fastboot flash cmds is another. Not suggesting that the port is bad, just that your device isn't behaving well with it. Try a USB 2.0 port if available. Also try alternate usb cables.
[Nexus 7 Android Development] Spades2006:
perfect thank you!!! successfully back at 4.4.4.

when i get the courage to re-try lollipop, what is the recommended update order? i originally tried 4.4.4 -> 5.0.2 -> 5.1.0. i am not sure if it failed because of locked bootloader or other reasons. my bootloader is now successfully unlocked though.

should i go 5.0, 5.0.1., 5.0.2. to 5.1.0?
[Nexus 7 Android Development] agentfazexx:
Tried a port on the embedded USB controller. That worked. Dunno what's up with my front port.

---------- Post added at 06:16 PM ---------- Previous post was at 06:07 PM ----------

Still doesn't boot. Stuck at the Google logo. Starting to think my tablet might be borked.
[Nexus 7 Android Development] milski65:
I went right to 5.1. from 4.4. No issues. I'm not knowledgeable enough to say taking those additional steps will help. Making that jump worked fine for me. 2012 WiFi 7.
[Nexus 7 Android Development] agentfazexx:
Took a half hour to boot, but finally did.
[Nexus 7 Android Development] Link_of_Hyrule:
[MENTION=3110798]WugFresh[/MENTION] in case you weren't already aware the Nexus Player has a custom recovery now I'm not sure how compatible it would be with the operations of the program but it's worth looking into. http://xdaforums.com/nexus-player/development/cm-recovery-nexus-player-fugu-t3076646
[Nexus 7 Android Development] WugFresh:
Yes, I saw that. I actually just got a Nexus Player in the mail today to mess with. I probably won't utilize that recovery to perform certain operations but I will enable flashing it. I am going to script all the rooting and stuff to extend full support for the Nexus Player in the upcoming NRT release. Stay tuned.
[Nexus 7 Android Development] Link_of_Hyrule:
Awesome I just got my Nexus Player pretty recently and it's been awesome but I really haven't had a reason to flash a rom on it I did root it to try and install apps to external storage but so far have no idea how to actually do that. I might end up installing CM12.1 on it if it lets me do that and also do video calls in Hangouts.
[Nexus 7 Android Development] bovirus:
I have Asus Nexus 7 2013 Wifi with Android 5.02 installed.

Asus has boot loader unlock, boot.img unlocked and TWRP 2.8.5.0 installed.

I downloaded OTA uipdate (5.0.2 to 5.1) but when I tried to insytaòll I recive an error

package expect build fingerprint of google/razor/flo:5.02/LRX22G/1649326:user/rele3ase-keys or google/razor/flo:51./LMY47O/1783956:user/reelase-keys: this device has google/razor:flo:4.3/JSSS15Q/779366:/user/release-keys

Error executing updater binary in zip /cache/update.zip

Error installing file /cache/update.zip

I tried to load it also via adb sideload (selecting Adavnvecd -> adb sideload in TWRP and loading file via adb sideload command.,

The error is

mount failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: devive or resource busy

package expect build fingerprint of google/razor/flo:5.02/LRX22G/1649326:user/rele3ase-keys or google/razor/flo:51./LMY47O/1783956:user/reelase-keys: this device has google/razor:flo:4.3/JSSS15Q/779366:/user/release-keys

Insytalling /sideload/package.zip

I believe that should be some problem on previous update that did't write rihght the fingerprint about Android system.

I typed the command (with Nexus 7 in normal mdoe)

adb shell getprop ro.build.fingerprint

the answer is

google/razor/flo:5.0.2/LRX22G/1649326:user/release-keys

Why this difference between the value got form default.prop (google/razor/flo:5.0.2/LRX22G/1649326:user/release-keys) and value got from update script (google/razor:flo:4.3/JSSS15Q/779366:/user/release-keys)?

How can fix it? Thanks.