yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] VanillaG0rilla:
My wife let her nexus 7 sit for months without a charge. Now it won't boot passed the Google screen. I tried using this toolkit to restore the stock rom but it fails. It does get recognized by adb and fastboot.

It still has the 4.18 bootloader. Anyone have any suggestions?
[Nexus 7 Android Development] keneth_c:
Have u tried doing with same with another USB port on the machine & by using another USB cable? Stick to USB 2.0 ports.

You mentioned it fails... But what is the exact error it gives? That would be helpful.

--
[Nexus 7 Android Development] davk50:
Nexus 7

Do not know if this will help but my granddaughter had the 2012 Nexus 7 with I think the same problem.

Try this link and see if it helps.

https://support.google.com/nexus/troubleshooter/3337561?hl=en&ref_topic=3415522
[Nexus 7 Android Development] keneth_c:
Good one [MENTION=4594683]davk50[/MENTION]

I remember doing this once a lot time ago... It's supposed to be some sorta issue with the Nexus 7 (2012).

Hope this tip helps [MENTION=4546172]VanillaG0rilla[/MENTION]

--
[Nexus 7 Android Development] VanillaG0rilla:
I'll check it out again today and post a screenshot of errors. It seems to take a charge just doesn't boot passed the Google screen.

When the toolkit tries pushing the rom to the device, every step says failed. Like I said I'll post a screenshot so you can see.
[Nexus 7 Android Development] pkelly517:
Glad it worked out.
[Nexus 7 Android Development] hazwheel:
I have to uninstall/reinstall the drivers and reboot my pc each session I use wugfresh for my device to be recognised, a pain but worth it :) try that maybe
[Nexus 7 Android Development] keneth_c:
Just used your toolkit again after a couple of months. Just wanted to do a full cleanup... Mannn... It's such a pleasure using your toolkit. Can't thank you enough.

Much appreciated [MENTION=3110798]WugFresh[/MENTION]

--
[Nexus 7 Android Development] memphisuklf:
tring to use the toolkit to restore my nexus 7 2012. For some reason when updating rom I have lost recovery and custom recovery and can't start the existing rom(4.42) already on the device, just keep getting booting failed in fastboot mode. Can someone talk me through my best options as have had tried the soft-bricked option and it failed.

Flash Stock + Unroot...

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

erasing 'boot'...

OKAY [ 0.024s]

finished. total time: 0.025s

******** Did you mean to fastboot format this partition?

erasing 'cache'...

OKAY [ 0.089s]

finished. total time: 0.090s

erasing 'recovery'...

OKAY [ 0.024s]

finished. total time: 0.025s

******** Did you mean to fastboot format this partition?

erasing 'system'...

OKAY [ 0.115s]

finished. total time: 0.116s

******** Did you mean to fastboot format this partition?

erasing 'userdata'...

OKAY [ 4.950s]

finished. total time: 4.951s

sending 'bootloader' (3911 KB)...

OKAY [ 0.513s]

writing 'bootloader'...

FAILED (remote: (InvalidState))

finished. total time: 0.748s

rebooting into bootloader...

OKAY [ 0.020s]

finished. total time: 0.020s

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

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

Bootloader Version...: 4.13

Baseband Version.....: N/A

Serial Number........: 015d324924180611

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

checking product...

OKAY [ 0.040s]

checking version-bootloader...

FAILED

Device version-bootloader is '4.13'.

Update requires '4.23'.

finished. total time: 0.202s

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.

NOTE: If this process was too quick and your device

is still in bootloader mode, then flashing stock may

have failed or been incomplete. Simply check the

log above: if you notice it skipped steps because it

didn't meet certain requirements, like the bootloader

or baseband version, then consider enabling 'Force Flash'

mode in the toolkits options menu and trying the

'Flash Stock + Unroot' processs again. Cheers.

Press any key to exit...

Is this thing dead?

Update

Sorted it thanks to this piece of kit. Thank you.
[Nexus 7 Android Development] broncop3t3:
Ok. So here is what I have done. Tried four different cables and two different USB ports on two different computers. I always get the same error at about 83 s (remote: (filewritefailed)) Is there a way to get past this or to know why it is hanging up at about the same time when I flash via fastboot. I was able to flash everything except the system.img

---------- Post added at 02:13 PM ---------- Previous post was at 02:11 PM ----------
[Nexus 7 Android Development] MiguelM600:
Back to stock - It finally worked

Hi wugfresh,

I was busy for almost 4 hours, after screwing up my device, but I finally was able to set my device back to stock and re-locked.

I couldn't have done it if your tool was not so complete, so I decided to donate to you.

Many thanks and keep up your awesome work!:good::good::good:
[Nexus 7 Android Development] WugFresh:
Maybe go a different route since you keep hitting the same problem.

Grab yourself a compatible custom ROM (download it to your computer), then temp boot TWRP and try to sideload it:

http://teamw.in/ADBSideload

You can also try using TWRP to wipe and format system first.

Let me know if that works for you.

{{ WugFresh }}
[Nexus 7 Android Development] dtothesquare:
I'm having the same decryption problem. Tried to restore stock 4.4.2 and got that so tried doing 4.2.0 and got the same problem. Went through your FAQ and couldn't find a solution. Any help?

***able to fix it. Needed to update by bootloader and was able to reflash back to a stock image in fastboot and that seemed to have cleared the problem.
[Nexus 7 Android Development] Mordar:
hi guys, will this work with the recent NExus 5? I am from venezuela, so aqduiring any phone is impossible, so a friend of mine will probably get a locked version (either from verizon or AT&T or whatever) to bring it here to my country, so is imperative I manage to unlock the phone so I can use it with any simcard here in my country, thanks in advance for any answer
[Nexus 7 Android Development] keneth_c:
Read this...

http://xdaforums.com/showthread.php?p=28616745

--
[Nexus 7 Android Development] sandinos:
Very good work. When I have tablet I'll test it. :good:
[Nexus 7 Android Development] broncop3t3:
Ok. I was able to install TRWP via fastboot. I thought I'd start by trying to format the "system" and it is taking a long time. Like more than a half hour. Should it be taking this long? Is there something else that I should do first. I am not familiar with TWRP, so I am not sure what works best.

Thanks
[Nexus 7 Android Development] keneth_c:
Nope. Formatting system shouldn't.

--
[Nexus 7 Android Development] broncop3t3:
TWRP reports internal storage as 0MB. Any ideas on the next step?

Trying to format
[Nexus 7 Android Development] keneth_c:
What exactly are you trying to do? Is your sdcard mounted in the first place?

--
[Nexus 7 Android Development] broncop3t3:
It's my nexus 7. Trying to get it back. Tried to factory reset a few weeks ago, stuck on the "google" screen. Now I have TWRP installed. Not sure where to go next.
[Nexus 7 Android Development] lotherius:
Restore FAILED.... (EDIT: RESOLVED ... Kindof...)

I did a backup of my Nexus 7 2012 using WUG. Reset. Now I'm trying to restore apps, and it refuses to actually do it.

It claims "Rebooting your device".... but it does not actually reboot. Then when I tell Wug OK, and it says it is going to restore... within about 3 seconds it claims "Process Finished" and never actually did a single thing. A bit peeved because this means I've lost quite a bit of app data. I did not use Titanium Backup this time (as I normally do) because somehow I expected Wug would actually be able to... you know... restore the files. The .ab file is around 550mb and I had received a successfully finished message when making the backup.

EDIT:

Turns out the problem was that WUG's toolkit wasn't actually connecting to the Nexus 7 at all... it was connecting to.. get this.. Bluestacks Emulator... on my PC.... wtf?

EDIT 2: ....

So... in addition to all the other issues, the actual backup file itself is CORRUPT... it restores about 10 apps and the aborts .... TiBu won't even open the archive either.
[Nexus 7 Android Development] keneth_c:
Did you format /system or something?

If you have a Nandroid backup (TWRP backup)... You could restore your Nandroid back.

Else use the toolkit to flash stock image and get your device working again. You'll end up losing all your apps and app data though.

--
[Nexus 7 Android Development] broncop3t3:
I have tried doing that. The flash doesn't complete. I was glad to get TWRP installed, but I feel like I am back against a brick wall again. failed to mount errors when I try to flash.
[Nexus 7 Android Development] bubba949:
Have you tried the force flash option?
[Nexus 7 Android Development] keneth_c:
Can you check and see if /system, /data & /sdcard is mounted via recovery or of it can be mounted via recovery.

I know that option is available in CWM. I recently moved to TWRP and totally loving it. But can't seem to remember if that option exists. Pretty sure it does though somewhere.

Bootloader still unlocked right? Have you tried flashing stock with current status in toolkit saying "soft bricked/bootloop"?

--
[Nexus 7 Android Development] corruption:
new to nexus 7 community

hey all, I just got my nexus today, traded in my galaxy tab 3 for it and I'm sooo happy to be free from samsung!!! anyway i was curious if i could get a mirror link to this toolkit the site the link takes me to is poop. thanks
[Nexus 7 Android Development] WugFresh:
Yikes. Didn't realize my site was down. Here is a mirror: http://www.softpedia.com/dyn-postdownload.php?p=213077&t=4&i=1
[Nexus 7 Android Development] corruption:
thanks
[Nexus 7 Android Development] broncop3t3:
No I can't get system, cache, or data to mount. via TWRP.
[Nexus 7 Android Development] keneth_c:
Since u have TWRP now... Have u tried to install a custom ROM?

--
[Nexus 7 Android Development] broncop3t3:
I tried to install a ROM and it wouldn't install. The mounting errors kept it from loading. There are no partitions listed on the Nexus. 0 MB is the response I get from TWRP
[Nexus 7 Android Development] keneth_c:
This is a real weird situation mate... And I feel your pain...

Stupid thing to ask you...

But did you try to format /system, /data & /sdcard?

I'm guessing it would give you an error since u are facing mounting issues.

Am wondering if there is a way for you to go back to complete stock... Or at least go back to stock recovery and then see if the partitions can be mounted.

Can you do a more thorough search on XDA for mount issues?

--
[Nexus 7 Android Development] salutcemoi:
Stupid question :

I dont want to flash custom ROMS on my Nexus 7 (1st gen , 4.4.2), just install Xposed framework + modules

Do I need to install CWM in orderto install any Xposed module ?

Thanks
[Nexus 7 Android Development] :
Hello wugfresh I wanted to thank you and contribute to your project!

On step 4 on nexus 7, 5 and 4 devices, after installing the universal drivers on step 3, you need to disable mtp and enable camera from storage options, if none of them are selected or just mtp it won't be succesfully detected

it has happened on all of my nexus devices on both windows 7 64 bits and windows 8 64 bits, I am the only one? if not I think it would be great to include it in step 4 as a clarifying note!
[Nexus 7 Android Development] marf28101995:
No you don't need.. But I recommend because if something goes wrong.. You can use the xposed script to remove xposed ;)

Slimkat + Art + Franco Kernel r45
[Nexus 7 Android Development] salutcemoi:
Thanks.

Yeah I rooted it this afternoon, didn't install recovery.

However it said it flashed temporary TWRP, lol.

As for Xposed, it's installed. I added a couple of modules.

I just need to find a module that adds a kill-all button to the app switcher
[Nexus 7 Android Development] marf28101995:
You've quote the other person's question and thanked to him for my answer... Not bad :D

Slimkat + Art + Franco Kernel r45

---------- Post added at 10:59 PM ---------- Previous post was at 10:58 PM ----------

And for the module.. Try gravity box.. I think it has that kill all button ;)

( bref c'est trop facile (;)

Slimkat + Art + Franco Kernel r45
[Nexus 7 Android Development] keneth_c:
Nope. You needn't.

Just download the apk for Xposed Framework and install that. Xposed modules are installed from within Xposed framework (just incase u didn't know).

You need to be rooted however.

Recommend installing custom recovery... So as to take a Nandroid before u install and start messing around with Xposed. Moreover u'll need custom recovery to flash the zip file to disable Xposed framework completely.

--
[Nexus 7 Android Development] salutcemoi:
Merci ! :good:

Gravity Box does have the kill all button

And sorry about thanking the wrong post .... XDA on Android has been acting up , IDK why

Thanks for the advice :good:

However is it possible that the toolkit installed TWRP temporarily?
[Nexus 7 Android Development] kywildcat:
WugFresh Tool Kit is amazing

Knew nothing about rooting, and successfully rooted my Nexus 7 via the Nexus Root Toolkit.

Now running CyanogenMod 11, never going back to unrooted.

Up next my Nexus 10, but will probably wait until Android 4.4.3, but its so tempting. Just going to root it and flash TWRP, for right now. But I'll probably flash CyanogenMod 11 on it eventually, and probably sooner rather than later.

Thanks WugFresh such a wonderful tool kit
[Nexus 7 Android Development] :
If I manage to unroot and relock my bootloader will I be able to receive the official OTA software updates in future?
[Nexus 7 Android Development] marf28101995:
If you've stock ROM.. Yes you'll

Slimkat + Art + Franco Kernel r45
[Nexus 7 Android Development] pkelly517:
No need to relock bootloader.
[Nexus 7 Android Development] DroidArt:
Life Saver

Thank you Wugfresh, you saved my Nexus 7 2012 from the rubble.:good:
[Nexus 7 Android Development] ichigo_kurosaki:
Waiting for the Kitkat 4.4.3 for my grouper and the expiration of my warranty before i mess with my n7. :D

Sent from my Tensa Sensation XE using Ban Kai
[Nexus 7 Android Development] Benjamin1966:
Hey wug, can you tell me how I would root/unlock a Samsung Tab 4 ? It's on KitKat
[Nexus 7 Android Development] hazwheel:
Well, you would head over to the samsung threads :-p

Pushed from me to thee
[Nexus 7 Android Development] ichigo_kurosaki:
Yep. Coz obviously this is for Nexus 7, both the tool and the thread. :D

Sent from my Tensa Sensation XE using Ban Kai
[Nexus 7 Android Development] a4apple:
Can I use this toolkit for my nexus 7 which running on 4.4.2?:confused:
[Nexus 7 Android Development] keneth_c:
Yes indeed.

For both the 2012 & 2013 versions.

--
[Nexus 7 Android Development] pkelly517:
And, for the unaware, the Nexus 4, the Nexus 5, Nexus 10 and other Nexus devices.
[Nexus 7 Android Development] brainvision:
so we should select 4.4.0 from the dropdown menu if we are running a stock 4.4.2, shouldn't we?

I was going to try like that but then I prefer to use the old classic and manual method.. when in doubt, always the best one!! ;)
[Nexus 7 Android Development] mertzi:
Hello! It seems that wugfresh.com is down. Can't access the install files.

edit: found the softpedia-link. Maybe you should update first post?
[Nexus 7 Android Development] hazwheel:
Um.. If you want 4.4.2, why would you not select that?

Pushed from me to thee
[Nexus 7 Android Development] brainvision:
'cause it is not available, at least for me.. the last build I can pick is the 4.4.0 KRT16S..
[Nexus 7 Android Development] hazwheel:
Odd, its defo there for me :/

Pushed from me to thee
[Nexus 7 Android Development] brainvision:
mmm.. I downloaded and installed it time ago, but it also check the update every time I launch the toolkit.. I think I will download the new version if any.. mine is v1.7.9.. let's see if there are new versions..
[Nexus 7 Android Development] WugFresh:
Yeah 1.8.2 is currently the latest. The lists should still have updated for you but I can't think backwards to v1.7.9... Too many code changes. Lol. Always try and use the latest version of my software. I am usually (try to be) pretty quick to update it to support new android releases.

Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] brainvision:
ok mate, thanks a lot for your help and for your suggestion (not to mention the entire toolkit! :) it's great! ;) ) but to be honest I thought it would have update everything when needed.

atm I already downloaded the last 1.8.2 version and it works like a charm now. btw sometimes it's good to do some manual mod and

fastboot

things, so that I will never forget how to do it! ;)

thanks for paying attention, see ya! ;)
[Nexus 7 Android Development] keneth_c:
[MENTION=3110798]WugFresh[/MENTION]

The only thing I've noticed is that... After the toolkit updates... Settings to the toolkit like the preferred custom recovery (CWM or TWRP) and preferred SuperUser (Koush or Chainfire) don't stick.

Any idea why that would be? Or is that just a bug?

Edit:

Not only when updating to latest version 1.8.2 but I've noticed the same when updating to previous versions in the past as well...

--
[Nexus 7 Android Development] WugFresh:
Not so much a "bug" - just the way it's currently programmed. New updates come with a new Settings.ini file (overwriting the old), this made sense in the past when I was overhauling lots of major changes in each release.. But now its not needed and is just a bad way to do it.

I am well aware of this flaw and plan on rewriting the updater to retain previous settings. That said, this change will be implemented into v1.8.3.. But you probably won't get the benefits until v1.8.4.. Because it requires updating the updater... If that makes sense.

So yes.. the next release will be last time this ever happens (unless I can think of a clever workaround.. In which case, this will never happen again). Cool?

{{ WugFresh }}
[Nexus 7 Android Development] lennydude:
FYI...............

Bought a new desktop that came with Windows 8. All was well and the toolkit worked very well.............UNTIL I updated to Windows 8.1 :(

I messed and messed with the drivers and FINALLY got things to work.

Once again this toolkit is an amazing accomplishment for idiots like me. I could never do this or want to do this stuff manually. Toolkits like this allow peeps like myself to do all the things that make phones such as the N5 awesome.

Many kudos to you and your team. Great stuff indeed :):)

Lenny
[Nexus 7 Android Development] bitemeoftn:
I'm on to the root part and I've gotten it to reboot and install, but now it's still stuck on waiting for your device even though it's fully booted. Where should I go from here? Thank you all in advance for any suggestions.
[Nexus 7 Android Development] WugFresh:
Remember to tick "Always allow from this device" on the RSA security prompt that comes up when you enable USB debugging the first time. Toggle USB debugging off/on to get the prompt.
[Nexus 7 Android Development] Exelzior:
flash stock + unroot problem

Hi ,today I wanted to flash stock ROM + unroot via Nexus Root Toolkit ,but it ended at writting of new bootloader with error "FAILED bla bla bla something with bootloader "invalidState". I was running on old Android 4.3 (JWR66Y) ,M-Kernel A61 and TWRP 2.6.0.0 recovery.

I found on web ,that Google somehow fu**ed up bootloader in JWR66Y (ty Google...),so it usually ends up with this "invalidState" error when you try to flash it manualy. Solution for that was flashing an older stock ROM (for example JWR66V or the last one with Android 4.2.2).

So I downloaded the one with Android 4.2.2 and used "Flash stock + unroot" option again to flash and finally I managed to flash the bootloader ,which downgraded to 4.18 from 4.32 (i think) and now when it should be followed with bootlader reboot ,it does nothing ,it ends with "writting bootloader... OKAY [1.280 s] finished. total time: 1.567s" and thats all ,no more progress ,even if I reboot the bootloader manualy. Is the .bat file ,which does flashing + unrooting broken or what?

I tried to flash the never one (JWR66V) ,which should work and also it ended up at writting the bootloader.

From CMD I read it erased: boot ,cache ,recovery ,system and userdata.

From now I cant boot into system or recovery ,only bootloader and fastboot works.

What Im suppose to do now? Im quite noob at solving these problems...

Device: Asus Nexus 7 16GB (grouper aka wifi tablet)

Drivers: all installed

Backups: none

Nexus Root Toolkit ver.: 1.8.2
[Nexus 7 Android Development] WooHooGuy:
May have a minor issue with the N7 and NRT.

I downloaded a fresh copy of NRT as I just upgraded to Win7, it's fully updated. I want to try the PhilZ recovery added to NRT but for the life of me I cannot get PhilZ recovery to flash using NRT / Adnanced Tools.

No errors, everything appears to go normally but when I reboot the N7 it goes back to TWRP.

I was running the multirom version of TWRP so just for ****s and giggles I tried flashing the regular version of TWRP and it flashed successively as the multirom menu is now missing from TWRP.

Any ideas or suggestions?

Edit -

Output of logging in NRT

Live log initiated.

Information: Checking ADB Status

adb devices

List of devices attached

015dxxxxx	device

ADB Status: Device Connected

Information: Rebooting your device into bootloader mode...

adb reboot bootloader

Information: Checking Fastboot Status

fastboot devices

015dxxxxxx	fastboot

Fastboot Status: Device Connected

Information: Flashing ...

fastboot flash recovery "C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\PHILZ\"

Information: Rebooting your device...

fastboot reboot

Information: Waiting for your device...

adb wait-for-device

Information: Device Detected

............................

Edit 2 - Just checked that location in the NRT folder and it's empty.. that probably explains why it wont flash.

:lol:

Edit 3 - Just went into the NRT settings and changed the default recovery to PhilZ, NRT finally noticed the recovery wasn't downloaded yet and prompted to do so. May need to add the same file check when someone uses the flash (permanent) recovery option under advanced utilities.

PhilZ recovery has successfully flashed.

Hope this info helps you out Wug, great toolkit you have and I really appreciate your work.
[Nexus 7 Android Development] WugFresh:
Thanks for reporting this. I overlooked some things when integrating philz. I am aiming to get v1.8.3 out within the 3-5 days. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] WooHooGuy:
Glad I could help, I really love your toolkit even though I am comfortable with ADB and recommend it to everyone I assist with Nexus devices.

I am not sure if I should feel sad or honored that I discovered this bug.. Am I the only one that has attempted to try PhilZ's recovery!!??

:o

It really is a great recovery now that I have messed around with it, Im looking forward to making a current nandroid of my Nexus 7 in TWRP, nuke it, then see if PhilZ recovery can successfully restore a TWRP backup as I thought I read somewhere it could..

:silly:

Happy flashing folks, Ill report back the results when I try it.