Hi,
I've been trying to root my nexus 7 all day. I saw a few posts on this, but I had one additional wrinkle: My nexus was encrypted. My company put in a Google Device Policy that made us encrypt the devices to get email. Encryption wasn't working properly, but I was able to use the device. When I tried to root + flash a new recovery, I had all kinds of issues. Was running 4.2.2.
The device never came up on the top half of the Toolkit tabs. It did appear under ADB devices though. When I tried some of the toolkit's fastboot options, like #8, it just hung on < waiting for device >.
Fastboot would not work. It just refused. I was trying on a Windows 7 box as admin, in all the different USB ports, with Camera mode USB debugging, and everything suggested.
Here's how I finally got it to work:
- Used Windows XP. Pathetic that we still have to go back to a 12 year old OS, right?
- Erased everything, boot loader, cache, recovery, user data, everything, using ADB and these very thorough instructions:
AndroidCentral > Forum > Google Branded Android Devices > Google Nexus 7 Tablet >Nexus 7 Rooting, ROMs, & Hacks > [GUIDE] Nexus 7 - Factory Image Restore
(Sorry I'm new to this forum and can't post links yet)
That set it back to factory stock. I'd used Helium (formerly known as Carbon) to backup my apps so wasn't worried about losing my data.
After going back to stock, I was able to get the fastboot prompts working.
Hope this helps somebody. When the device gets encrypted, I think it locks up /data and makes it quite difficult to flash over it. Gluck.
Related
Hello there everyone.
First off, I know this might seem like a subject that's already been covered. Trust me, I've spent the last few days going through every thread I could find on here trying everything out as well as other threads on tips on the net. So I'm posting this because I've tried everything and run out of troubleshooting methods to have a go with. The experts here may relish the challenge of solving this one. Or tear their hair out just like I'm doing. Hence my username. I'm worn out after countless hours of doing this.
Background:
I had a rooted Nexus 7 with superuser and TWRP. Jellybean 4.2.1 update would never work, always got an assert failed or some other error when it tried to do so. I then decided to go back to a previous backup in case something had gone wrong since in order to get on with installing the update.
Previous backup loaded fine. Unfortunately WiFi was not working and just kept on searching forever. After lots of googling and trying all the fixes with my router and so on which failed to solve anything, took the advice of going back to a factory reinstall.
Reinstalled, booted up, selected language on Google Welcome Screen then onto Wifi screen. Stuck on seaching forever. More googling and took advice. Decided to do Nexus Root Toolkit's flash stock+unroot to get back to clean state. After install there's an issue that just won't go away and that is:
Problem:
Google Nexus 7 (Wifi model) won't go past Google screen (this is not the coloured logo, just the word "Google" in white).
Associated problems:
Going into recovery just shows the same screen or sometimes an android lying on its back with a red triangle.. So no stock recovery available. Using fastboot to lock and unlock the bootoader as a recommended fix has no apparent effect with the result just being the same Google screen (padlock icon unolocked or locked depending upon locking status) even after a long wait.
Flash stock+Unroot in Nexus Root Toolkit has the same result. I left the thing on for a long time each time after a factory install because of advice saying to wait and still the same screen all that time. Longest time was 6 hours left on due to frustration and waiting to see if anything at all would happen. It didn't.
I can't access ADB in bootloader. I can only access ADB when the device is in TWRP or CWM menus. (In other words Nexus Root Toolkit complains it can't connect when I'm in the bootloader for example if I want to do any operation that requires ADB, but doesn't complain when in in those two recovery menus). Nexus Toolkit will quite happily do the Flash stock+ unroot and get to the screen where it says wait a while for device to reboot and you can press any key to exit.
I have wiped system, cache, boot, recovery, userdata using both fastboot and JROM Flasher. I can install TWRP or CWD using the Nexus Toolkit and wipe stuff using those but still no joy. I have gone through every permutation many times step by step. I have even used different Jellybean factory images from 4.1.0 to 4.2.1 as well as past backups with the same result each time.
Have used soft bricked and device is on options in Roolkit. No joy.
I have also disconnected the battery as part of the troubleshooting process.
Basically, nothing I can do using the information I've been able to get hold of can get past that screen.
Other quirks:
I have also noticed when installing a factory image a message comes up:
writing bootloader FAILED (remote: (invalid state))
It continues with the rest of the installation however as normal.
Also PdaNet comes up with the message:
Wrong WinUSB Pipes found
If I try Connect Internet (USB) option.
I have downloaded Nexus 7 tablet USB driver revision R06 and tried to use them but my PC will only recongise the device as an MTP device with failed driver install when the tablet is in that endless Google screen.
With the install of the Naked Universal Driver it only recognises the device in the Device Manager as Google Nexus 7 Bootloader Interface.
Driver tests in Nexus Root Toolkit fail. It advises enabling USB debugging as one of the fixes which of course I cannot do as I can't boot up to reach those options.
From this I surmise there is some problem with the drivers. I have tried on two different PCs as well.
Software I have used in all my efforts: Nexus Root Toolkit 1.6.2, Gnex, JROMFlasher, TWRP, CWM, PdaNet, SDK Manager, Nexus 7 tablet USB driver revision R06, Naked Universal Driver 0.72 .
I'd appreciate any advice (apart from sending the thing back), epescially if it's in a step by step easy to follow format. So basically, my question is, how do I fix this? Is it possible to fix?
Many thanks in advance!
I just thought I'd update this, mainly to let people know what to do if they find they have a similar problem to the above.
Basically, as said before none of the fixes worked. I spent a huge amount of time trying everything. So in order to save people massive amounts of time who have pretty much the same problems as I had and spending hours upon hours trying fixes like I did, then the best thing to do is to return your Nexus 7 to where you bought it for a return.
Mine was subsequently discovered to have a hardware fault so I was basically trying to fix the impossible. If you find yourself in the same boat after trying the fixes, and they don't work after a couple of tries, don't do it multiple times like I did. It's just easier, less frustrating and will save you much hair loss, anger and general irritation to let Asus fix it.
Yes, I know some of us get a bee in our bonnet about fixing it ourselves and see returning it as the last resort (like me), but anyway, trust me, just send it back, and save yourselves the trouble in a case like the above.
My tablet has arrived back repaired and works again. The hardware fault was covered by the warranty.
I hope anyone who encounters the same issues as I have manages to find this of use in the future!
I've got a bit of a problem with my Nexus 10, I want to do a factory reset to remove encryption, but the factory reset fails every time. I've tried the stock one via the menus, and the clockwork one via recovery, but neither works. I thought I'd have a go at re-rooting it to see if I could force the issue, but the recovery isn't able to mount the SD, so I can't get to the file to flash. The unit is spoofing a Galaxy Nexus for SkyGo purposes, which seems to be causing the adb drivers to not work on my PC, as it's obviously not seeing it as a Nexus 10 when I connect. I can't remove the spoofing, as it needs to be rooted, which brings me full circle.
It's a right pickle!
Any ideas what I might be able to do to get the unit rooted again?
mcwildcard said:
I've got a bit of a problem with my Nexus 10, I want to do a factory reset to remove encryption, but the factory reset fails every time. I've tried the stock one via the menus, and the clockwork one via recovery, but neither works. I thought I'd have a go at re-rooting it to see if I could force the issue, but the recovery isn't able to mount the SD, so I can't get to the file to flash. The unit is spoofing a Galaxy Nexus for SkyGo purposes, which seems to be causing the adb drivers to not work on my PC, as it's obviously not seeing it as a Nexus 10 when I connect. I can't remove the spoofing, as it needs to be rooted, which brings me full circle.
It's a right pickle!
Any ideas what I might be able to do to get the unit rooted again?
Click to expand...
Click to collapse
Custom recoveries don't deal with encryption, if I'm remembering things correctly. If your stock recovery's not working either, then that's a serious cause for concern (and is likely why factory reset isn't working for you). To be honest, you may be kind of hosed on this install around. I'd recommend that you boot up, back up your data using Titanium Backup, offload it (connect it to a PC/cloud service while device is on), then plonk into fastboot and just reinstall (or RUU).
Rirere said:
Custom recoveries don't deal with encryption, if I'm remembering things correctly. If your stock recovery's not working either, then that's a serious cause for concern (and is likely why factory reset isn't working for you). To be honest, you may be kind of hosed on this install around. I'd recommend that you boot up, back up your data using Titanium Backup, offload it (connect it to a PC/cloud service while device is on), then plonk into fastboot and just reinstall (or RUU).
Click to expand...
Click to collapse
Therein lies the problem though, for whatever reason my PC won't recognise the nexus 10, despite the drivers being installed from the ADK etc.
Because of that, I can't use fastboot or anything PC based. I suspect it's because the device is spoofed as a Galaxy Nexus.
The device is currently unrooted too, so that also limits my options.
My data isn't really a problem, I'm happy to wipe everything, it's all backed up on my NAS anyway.
Isn't there any sort of physical reset button anywhere that will force a factory reset?
Managed to get the drivers working on my gf's laptop, not sure why my PC wasn't playing ball, but this is all fixed now.
Ta!
Hello,
Apologies if this has been answered elsewhere - I've searched extensively and can't find the answer.
My 2012 Nexus 7 wifi has been rooted and unlocked and I have played about with various OS's such as CyanoGenMod to try to get it to run smoothly without lag. The last one I tried was a fairly standard build of 7 (I Think), but after 18 months or so it slowed enough that I decided to take the nuclear option of reverting back to 4.4.4.
I downloaded a build of 4.4.4 called omni on my mac, transferred it to the Nexus 7 via USB and also included a package of Gapps.
When I'd flashed from clockworkmod the system kept rebooting, wouldn't let me turn on wifi and wouldn't show up when connected to the mac. I downloaded a factory 4.4.4. image but couldn't transfer this to the Nexus, so had to install and use ADB. I installed ADB via homebrew, which works, but I can't find the installation folder by browsing to it.
I got the Nexus 7 to reboot, but couldn't transfer the new stock image (nikasi) across. Now the Nexus 7 won't boot into recovery mode - I get a message saying that the boot failed.
All the guides I've read have advised me to reinstall the rootkit using a software package for windows (which I don't have) or to enable USB debugging on the device, which I can't access.
Any ideas? There's nothing urgent about this - I don't need the Nexus 7 for work or anything, but I would like it to work. It was great when I first got it, but lollipop ruined it and it's never been satisfactory since
Thanks
Nexus Player stuck on " Can't Load Android System. Your Data may be corrupt"
Hi, my Nexus Player is stuck on " Can't Load Android System. Your Data may be corrupt. If you continue to get this message you may need to perform a factory data reset......."
When I do the factory reset it brings me back to this screen. My son told me it happened after an update.
I can't get it to do anything else.
Is there a solution?
I’m experiencing this same issue now. Stock Oreo, unrooted. Anybody have any ideas?
Same happening here. Unrooted, Stock Oreo. Happened after an update.
Have attempted to get USB connected in recovery to ADB push the factory image with no luck.
Device not showing up on windows or mac.
ratmandu said:
Same happening here. Unrooted, Stock Oreo. Happened after an update.
Have attempted to get USB connected in recovery to ADB push the factory image with no luck.
Device not showing up on windows or mac.
Click to expand...
Click to collapse
So Google is hard-bricking our devices with no replacements in sight? This is crazy. This isn't the only thread about this.
taino211 said:
So Google is hard-bricking our devices with no replacements in sight? This is crazy. This isn't the only thread about this.
Click to expand...
Click to collapse
I wouldn't quite go so far as to imply that they are doing it on purpose. It is most likely lack of testing of updates going out, since it is an old, and now unsupported device.
This happens to my nexus player too, after update push from google.. Apparently google pretty much bricking all nexus player by pushing bad firmware update. I can see class action lawsuit coming if google doesn't fix this soon
Successful restoration of factory image into nexus player
Andy Jawa said:
This happens to my nexus player too, after update push from google.. Apparently google pretty much bricking all nexus player by pushing bad firmware update. I can see class action lawsuit coming if google doesn't fix this soon
Click to expand...
Click to collapse
Update, I did follow the direction posted on another forum and was successful on restoring my nexus player. Here's the procedure that I found working for me. I had to flash it couple of times since the latest image doesn't seem to fix it. Also the usb driver tool doesn't seem to work properly on my windows 7 laptop, but works in windows 10, but it may just be my Win7 laptop that has too much security restriction.
Here's the procedure.. good luck. Sorry, since I'm newbie, xda won't let me post actual link, I have to remove the http, but it is a good link, you just have to paste it into browser
1. Download Google USB driver from : developer.android.com/studio/run/oem-usb
2. Download and unzip ADB and Fastboot tools: developer.android.com/studio/releases/platform-tools
3. Download and unzip Nexus Player Factory Image: developers.google.com/android/images#fugu
I tried the lastest one : 8.0.0 (OPR2.170623.027, Nov 2017) , but it crashed again. I then loaded the 8.0.0 (OPR6.170623.021, Sep 2017), and it seems to work so far. I disabled the auto-update on the play store just to be safe, but not sure if this would prevent the OTA.
4. Open command prompt window and go to the unzipped folder for the fugu image
5. Add path to the ADB/fastboot tool into system PATH, example:
PATH=%PATH%;D:\Dnload\platform-tools_r28.0.0-windows
6. Get into bootloader of Nexus player using this procedure:
- unplug power of NP
- Press the button on the bottom of NP, keep it pressed and plug-in power
- keep it pressed for about 8 sec, and release, it would go into fastboot mode, showing you the current setting and boot option with default of "normal boot"
- press button one time to stop it from doing normal boot
7. Plug microUSB cable between NP and your PC, and install driver (unzipped in step 1) if asked.
8. Back on your command prompt, type "fastboot devices", it should show the nexus device, if nothing is listed, there's still driver issue that need to be fixed.
9. Now we can follow the instruction to flash the factory image from developers.google.com/android/images. I will summarize the step below that work for my nexus player (pre 2015 device)
- unlock bootloader by issuing command: "fastboot oem unlock". You should see the status updated on the screen to unlocked.
- Execute the "flash-all" script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
You should see the activity on screen, like downloading state. While the script is running, it would also reboot the nexus player into bootloader, and waiting for the NP to come back up into bootloader. Once it comes back up, the script would resume. In case the player doesn't go back into bootloader, do step 6 to manually get into bootloader
- After the script completes, for security you should lock the bootloader again, by going back into bootloader (see step 6) and issuing command: "fastboot oem lock"
Mine started doing this also, it sits at the GOOGLE screen for a while, flashes/reboots once in a while and then eventually goes to the NO COMMAND screen.
I flashed it back to 7.0.0 NRD90R and it booted up fine, setup things and it worked fine even after the OTA to 8.0, but something else updates soon after that and fails again.
I just flashed the 8.0.0 OPR2.170623.027 before I left for work so we'll see what state it's in when I get home.
My second one is fine so far.
Mines dead too, stock, no root.
I will try flashing older version and see.
Wow, WTF is happening to the Nexus Player?
My Nexus Player have been unused for the last few months (I think I just upgraded it Oreo to test it when it went out), what can I do to save it from the sudden death?
Can I power it up without WiFi and block updates or something?
Just saw this on the google forum.
Can't load Android System (https://productforums.google.com/for...us/Ski0fFZ0pZM)
Quote:
GEL1966 via Nexus Help Forum
I was encouraged by a reddit user to open this: https://issuetracker.google.com/114276277 He suggested I get as many people I could to "star" the issue. Hopefully it yields something other than an "escalation". Will post any news.
My Nexus Player has been at Android 8.0.0 for a while.
I hope I didn't jinx it by posting here
If it quits working, I still have a Roku and a fireTV.
Sent from my SM-G930T using Tapatalk
So I'm by no means a pro at this but I have never had to reach out for help when playing with my android OS. I mainly use that nexus root toolkit for things I need and it is what I know best.
nexus flo (second gen wifi)
So I put lineage 16 on my tablet. This was following this guide.
https://www.reddit.com/r/Nexus7/comments/esy39y
all went well. Then I wanted to update to 18 and that also went well. I noticed the play store was missing so I tried to re install from the gapps zip in wtrp. That didn't work and following some apparently stupid advice. I selected wipe->format data. My os lost its debug option (can't get it back) and trp was busted (bootloops when entering it). So I tried to use the wipe data factory reset and start over but it blew out half way in to that and now I have no os. If I try to install my stock os I get an error 1 missing a binary. Advice there was to manual flash bootlimg and that didnt do jack. I can not flash lineage 18 as it claims I'm not a flo device. Anything I flash for that matter gives me one type of error or another.
I do not care about what is on the device I just want the device back so I can continue to enjoy learning and playing.
current issues:
1, can not boot in to recovery
2. can not boot in to OS
3. can not boot into bootloader
current options that I know of
1. I can use NRT and get in to wtrp
2. run fast boot commands
3. run abd
4. I do have an extra nexus 7 (2013) with a bad screen that I can get in to.
Any advice?
So turns out the bulk of my issues was I some how got a older twrp on there. Though still trying to get version 18.1 on there and currently bootlooping. Does anyone have a "current" guide for this?
So tried installing gapps, and figure maybe I need to run that clamor repartition. That seem to go ok, I did the modify command like it said to. And now it looks like I have nothing. I can even get the sdcard to show up on a pc. Do I need to mount my partitions somehow?
I'm still able to send files via adb but I'm not able to figure out what I need to fix this.
er,, ok nm, I fixed it by making the system xf4. Wiped everything and its back to clean. So what is the best way to get this done?
Going to move me issue to.
[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0]
LineageOS 20.0 lineage-20.0-20230507-UNOFFICIAL-flo.zip lineage-20.0-20230507-UNOFFICIAL-deb.zip Known issues: - We are still Permissive (SELinux) - Encryption is not working .. Pls do NOT encrypt your /data partition! - Camera is not fully...
forum.xda-developers.com
I think I need to resize system but not sure the best way .