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
Related
My tablet is running CM10.1 and TWRP is on it. Past a few common issues, nothing a bit of research hasn't fixed. I can't find what went wrong on this issue. Everything was peachy last week and all drivers worked. I rooted the tablet last month.
Now I can't see the tablet on (2 machines) Windows 7 64bit and I keep getting error code 10 while trying to get the MTP driver in. Both machines give the same error code. On all 18 USB ports, front and rear.
I suspect there is an EBKAC here, but everything I've tried has ruled that out.
Steps taken to fix the driver issue:
rollback via restore, both driver rollback and (wizard) full OS restore
Installed Android SDK - used the USB driver
found driver package on forums
allowed auto-find in Windows hardware wizard
Installed Asus Sync package
manually removed drivers in device store and edited the registry hives - Allowed to rebuild
created a voodoo doll for the ghost of Scooby Doo and danced nekkid in the snow
The tablet shows in device manager, while in camera mode. But not showing storage drives (in Explorer.) In MTP mode it fails to load driver - No drivers = nothing shows in Explorer..
An update, for those in the future users who may find this thread and seek a solution. Sorry about 2xposting. I feel a double post is best, instead of an OP edit.
I did get the issue resolved, but I wiped the device twice and it somehow started to work. Not sure of the cause, or giving an actual known solution. I'm pretty sure I got lucky, by trial and error. Following normal documented troubleshooting on xda. I will share the steps that I took. Which helped get it working.
Here is what I did:
I did all the wiping I could in the latest (contemporary) TWRP. Minus formatting anything.
Used my recovery image of choice, via TWRP and reinstalled it. Let the device settle for 20 minutes after it fully rebooted. (I connected via wireless [n300] @72mbps)
I confirmed it connected and detected.
I rebooted the device into recovery mode and entered TWRP again. Wiping everything I could. Minus formatting anything. I then installed the build I wanted, in this case: CM10.1, sans gapps.
I let the device settle for 20 minutes after it fully rebooted.
I was then able to successfully connect the device. Via the usual means of getting the Asus MTP driver in. Once this milestone was achieved. I then installed gapps. Explorer now shows as expected and I can resume on with other niggling issues for the device.
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.
I rooted my nexus 4 on 4.2 with no problems.
I then upgraded to 4.2.2 while temporary unrooting with voodoo OTA rootkeeper then restored root and everything worked ok.
Now recently my Nexus 4 does not show up anywhere on my laptop but charges ok.
I have downloaded the latest toolkit V2.0.0 and installed the drivers (option 1) and it says they install.
In device manager I have an exclamation mark next to both google nexus 4 ADB interface and also both BootLoader Interface tabs.
Im totally stuck and dont know what to do.
Usb debugging is on, MTP is checked
If i do a factory reset on my phone, will it take it back to 4.2 unrooted like when i bought it and give me no problems?
I would be grateful for any help
Doing factory reset doesn't erase root.
Sent from my Nexus 4 using Tapatalk 2
Paul203360 said:
I rooted my nexus 4 on 4.2 with no problems.
I then upgraded to 4.2.2 while temporary unrooting with voodoo OTA rootkeeper then restored root and everything worked ok.
Now recently my Nexus 4 does not show up anywhere on my laptop but charges ok.
I have downloaded the latest toolkit V2.0.0 and installed the drivers (option 1) and it says they install.
In device manager I have an exclamation mark next to both google nexus 4 ADB interface and also both BootLoader Interface tabs.
Im totally stuck and dont know what to do.
Usb debugging is on, MTP is checked
If i do a factory reset on my phone, will it take it back to 4.2 unrooted like when i bought it and give me no problems?
I would be grateful for any help
Click to expand...
Click to collapse
Even I had similar problem in my N4.
Try re-installing the drivers of N4. :good:
I also did that when my phone stops recognizing after flashing rom.
I have tried this but its still not working.
Can I roll back to 4.2 without connecting to PC?
Hi,
I am trying in vain to fix my friend's Nexus 4. She started having problems with a boot loop around the same time as 4.4.3 (I think) but it just went away. Two days ago it came back, possibly around the time of 4.4.4 seeding, however this time it won't go away. I have been looking at threads throughout XDA for help and tried this thread for help. I have a GS4 myself and very little experience with ADB/SDK.
All efforts have failed. As well as the boot loop issue, recovery is broken limiting my options. I tried the "not lose any data" method in the link above but this didn't work. Next the Nexus Root Toolkit, however most of the time the program fails as it says the download failed due to an MD5 mismatch. I have tried downloading the images directly from Google but still no luck - of all the 4.X images available only a couple will even allow me to try and install.
The first install didn't install, I noticed it mentioned the bootloader been locked several times - it recommended 'force flashing' providing I definitely have the right image. Several attempts later I managed to get the install working but it is still stuck on a boot loop (waited at least 15 minutes). Recovery is still broken. The only thing I have been able to do is unlock the bootloader.
So is there any hope? The device is pure stock, no alternative custom recovery or ROMs. Thanks.
I think half the problem is I can't the USB drivers installed properly as the device isn't showing in Device Manager. Without been able to turn on the phone or enable USB Debugging, it won't let me.
EDIT - I tried another toolkit and eventually managed to get 4.2.2 installed. I have just updated the phone to 4.3 but it's been on the Google X screen for a while now
EDIT 2 - Fixed the above. I needed to downgrade the radio. Updating to 4.4 - no doubt I will go through the same hurdles.
EDIT 3 - An error occurred during installation.
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 .