Hey there,
Picked up my N7 this evening from futureshop and ever since unlocking the phone I haven't been able to do much else with it. All I can do is flash it back to stock, however I can't lock it, root it, or do anything else as I get stuck with the ADB Status looping and never connecting. When i run adb start-server manually it never finds the device. I have driver all of the drivers on my Win 7 machine. The default ones included, the pdanet ones, even the universal naked driver. It successfully install as an samsung ADB or now with the UND ones as a Nexus 7 ADB but still no luck.
I've deleted/cleaned out all of the drivers several times, though what if anything do we point the MTP at, as in debug mode it never comes up with valid drivers for it.
At the bootloader here is what I have:
Product Name - grouper
Variant -not defined yet
HW Version - ER3
Bootlader Version -3.34
Baseband Version - N/A
Signing - not defined yet
Lock state - unlocked
Now I can still use the phone normally, I haven't bricked it (at least hard brick anyways) however I can't do anything else as stated above.
One not related to trying to root or get working ADB drivers going is that it seems the bluetooth can't connect to my galaxy s (running CM10 ICS), Now I've used the work around of pdanet and foxfi I was just wondering if there is an way to do it without using 2 apps.
Can you flash Clockwork recovery? I just had similar problems getting my new Galaxy Nexus rooted. I could get to fastboot and temp flash cwm. From there I couldn't get root because it was overwriting the cwm on boot. So what I did was temp flash cwm, then flashed a pre-rooted deodexed stock jb rom.
I believe I have been able to flash clockwork recovery 6 onto it. Let's see where I can go from there.
Yep, got CWM to install now. I'm finally going places.
And I just rooted using superoot or whatever it's called. Now just to select a flavour of the ROM
Related
Bought a new Nexus 7 because my wife and I have them and love them. We had bought our daughter a cheap 'funtab' from walmart just so she could play a few games she loves and hopefully leave ours alone, the funtab was a complete POS so it was returned to WM and just bought her a N7 instead.
When booted, the tablet it immediately notified me of the update from 4.1.2 to 4.2.1. Each time it tried to update it would fail partially through, not sure why. So I thought I'd download and use the toolkit to force the update. After unlocking, rooting, installing busybox and so on. I choose the option to flash stock image. The update process started OK there but part way through gave an error, something about needing to be 'X' but is instead 'x' before going back to the home screen. Now the tablet is stuck in fastboot mode, and cant boot to either recovery or android. I think I may be in trouble here.... Any suggestions?
#1 reason why people shouldn't use tool kits to root. You have no idea what went wrong or where the problem occurred.
I'm assuming that your tablet is unlocked so you need to download a custom recovery and install it via fastboot.
Then download the Stock 4.2.1 ROM from the Android development section and flash it in the recovery.
This should give you an idea of how to do it.
http://www.androidcentral.com/how-unlock-bootloader-and-root-your-nexus-7
Sent from my Nexus 7
I've done more research and I'm currently working on getting the android sdk going. I've downloaded it, jdk, the proper factory image (i think I f'd up by accidentally downloading the factory image for the hspa model). My question now is can the factory image be flashed from what appears to be fastboot mode, or do i need to flash custom recovery first (via the sdk)? I can confirm that the bootloaded is unlocked.
Ok so I was able to flash the stock image using the instructions found at http://forum.xda-developers.com/showthread.php?t=1907796
This process went extremely well once I had all my ducks in a row. Thanks for the help.
I have two Nexus 4s. Both were running 4.2.2, rooted, with custom recovery and the Franco Kernel. On a Mac, using the command line, I flashed stock recovery and the stock kernel in preparation for taking the 4.3 OTA.
First, on the newer N4, which has far less thing loaded on it and doesn't have a SIM card...
I tried to install the OTA letting the device/OS do it via the prompt after it was downloaded. But though it tried to start the process, it failed.
So I tried to install the full OS using the command line on a Mac following efrant's instructions in http://forum.xda-developers.com/showthread.php?t=2010312. Fastboot commands have always worked there, but I've never been able to execute adb.
Code:
./fastboot-mac flash system system.img
This is something I've done successfully before. But not this time. I flashed recovery and the radio, but when I tried to flash the system, I got an error message (usb_write failed with status e00002be or something about a partition not existing). So I took the phone to a Windows machine and used Wugfresh's tool. I couldn't successfully set up the drivers, but fastboot worked. So I did the return to stock and root thing. And it worked, getting me back to 4.2.2 in an out of the box state. I ran the OTA right away and easily got to 4.3.
Then, since I was already on the Windows machine, I used Wug's tool to try and root. No success. I can't seem to install custom recovery, either temporarily or permanently. I don't get an error message, but I can't boot into it, either. I just get the dreaded lying down Android icon with the red exclamation point.
Any ideas why I couldn't install system.img on the Mac command line? And why can't I get custom recovery? And what I can do to get it right?
Now, the older N4, which is my main phone. I have a current Titanium Backup, but not a Nandroid, at least not a current one. I haven't tried, yet, to update it to 4.3. But as mentioned, I did try to go back to the stock kernel and recovery in preparation. The problem there is that I also get the lying down Android instead of stock recovery and even worse, occasionally slow and laggy performance, which I hadn't had to begin with. Otherwise, it's 4.2.2 with that radio and kernel.
Any thoughts or help on this would be much appreciated.
I'm still hoping someone can offer me some sort of insight on this.
Dev Options and USB Debugging have been enabled on these N4s. I also want to say that I'm not trying to do anything I haven't done a bunch of times before both with NRT and from the command line with N4s and N7s. But I'm stuck in ways I haven't been before and I don't understand why or what to do about it.
I dont know exactly what you mean but the android laying down is the stock recovery.
Sent from my Nexus 4 using xda app-developers app
Hmm. I thought there was another, simple, volume key driven recovery interface from prior experience with this. I'm probably confusing a non-touch version of CM Recovery. Thanks for clarifying.
I finally got drivers working on the Windows 8 machine (the Universal Naked Driver that I found here at XDA). I was able to use the command line through NRT to get custom recovery onto the first of the N4s I described. I couldn't do that on the Mac via the command line or through the NRT interface before that. It just didn't work. Once that was in place, rerooting was easy. But it was a long road to get there with obstacles I hadn't encountered on earlier rooting and updating adventures.
I haven't tried to update my daily driver, yet. I may wait until things stabilize more with 4.3 and the various ROMs. Since I may have little choice other than to start over, I might do something other than the stock ROM.
One thing I've discovered is that running a more recent version of fastboot and adb helps. I can do some things on the Mac from the command line that I couldn't do with versions a few month older. (April, 2012 vs. November, 2012).
I still can't successfully run the OTA on one of my N4s, though. Maybe I need to unroot first, though I never have before.
I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...
If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck
stats;
n7,
unlocked,
rooted
running JB
user level: android noob, but have a good grasp of comp stuff (I used to kill my own viruses when limewire was the defacto way to get download)...
comp, Win 7, old athlon dual core 64 4600, 3gb ram...
My n7 hasnt loaded kitkat, and I was getting annoyed with the constant "update ready".
I tried several times to install it, but each time it turned up an error....
Today I thought I would force an update with Skipsoft toolkit.
All seemed to go well, then....
things froze.....both comp and tablet and toolkit
I walked away, I didnt touch anything...for 2 hours. I literally went outside to do some errands, hoping things would "fix themselves".
I came back and disconnected, the tablet but the computer was still frozen...so I waited a few then, restarted the comp...
Now my tablet was stuck on the "google" screen.
I figured out how to get into the fastboot screen,
then the CWM screen.
from there, Ive tried,
Skipsoft toolkit,
Nexus Root Toolkit,
ADB manager (still not sure what this does except for downloads files, none of the apps in the toolkit file do anything)
fastboot.exe,
pdaNet drivers...
a couple of various tutorials (http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/) this one requires the tablet to be awake, but Ill be darned if I can get it to do anything...
On the good side of things, the Skipsoft toolkit, recognizes it, it displays the serial so theres hope. I hope.
But its never recognized in my computer, it did make the beep boop, when ever its dis/connected, until the I was trying the nexus root kit (they ask to remove drivers etc).
99% of the tutorials ask for the debugging to be activated. well it was but now...who knows.
with the skipsoft I get:
insecure boot image found
stock recovery image found
cwm image found
twrp image found
^^^^^^^^^^^^^^are these on the tablet or the comp?
once Im into the cwm screen, Ive cleared cache, and partition etc, nothing seems to help.
can someone help me before I brain my damage?
fixed it..wooooohoooooo
Vishnuisgod said:
stats;
n7,
unlocked,
rooted
running JB
user level: android noob, but have a good grasp of comp stuff (I used to kill my own viruses when limewire was the defacto way to get download)...
comp, Win 7, old athlon dual core 64 4600, 3gb ram...
My n7 hasnt loaded kitkat, and I was getting annoyed with the constant "update ready".
I tried several times to install it, but each time it turned up an error....
Today I thought I would force an update with Skipsoft toolkit.
All seemed to go well, then....
things froze.....both comp and tablet and toolkit
I walked away, I didnt touch anything...for 2 hours. I literally went outside to do some errands, hoping things would "fix themselves".
I came back and disconnected, the tablet but the computer was still frozen...so I waited a few then, restarted the comp...
Now my tablet was stuck on the "google" screen.
I figured out how to get into the fastboot screen,
then the CWM screen.
from there, Ive tried,
Skipsoft toolkit,
Nexus Root Toolkit,
ADB manager (still not sure what this does except for downloads files, none of the apps in the toolkit file do anything)
fastboot.exe,
pdaNet drivers...
a couple of various tutorials (http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/) this one requires the tablet to be awake, but Ill be darned if I can get it to do anything...
On the good side of things, the Skipsoft toolkit, recognizes it, it displays the serial so theres hope. I hope.
But its never recognized in my computer, it did make the beep boop, when ever its dis/connected, until the I was trying the nexus root kit (they ask to remove drivers etc).
99% of the tutorials ask for the debugging to be activated. well it was but now...who knows.
with the skipsoft I get:
insecure boot image found
stock recovery image found
cwm image found
twrp image found
^^^^^^^^^^^^^^are these on the tablet or the comp?
once Im into the cwm screen, Ive cleared cache, and partition etc, nothing seems to help.
can someone help me before I brain my damage?
Click to expand...
Click to collapse
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im updating with kitkat and it updating to 4.4.2
Vishnuisgod said:
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im updating with kitkat and it updating to 4.4.2
Click to expand...
Click to collapse
thank you for the tips ! the tool kit actually worked i had no os (deleted everything).
and used the 9 option (flashing stock) it worked !
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
zaft1 said:
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
Click to expand...
Click to collapse
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
mnb91 said:
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
Click to expand...
Click to collapse
Hey sorry, I haven't been on the site for a couple days.
I used the flashtool to go back to stock. Had to enter download mode and work from there. The big issue I was having was a driver issue. Uninstalled every driver related to android and then reinstalled after a restart and that did the trick. For some reason android phones are giving me a lot of driver issues on windows 8.1
follow these steps here but make sure you read a chunk of the thread as the steps in the main post are not complete
http://forum.xda-developers.com/showthread.php?t=2432476