Database Users

[Q] Unable to Root after 4.2.2 update

Hey guys, my first post here. I signed up for this forum a little while ago and I've just been a lurker since today. Lots of great stuff on this forum!
I finally got my Nexus 4 phone when they went back on sale in late January, I came from an iPhone 3GS and I've been loving the switch every day since!
But now I have a problem that I hope you guys can help me with.
When I first got my phone the first thing I did was unlock the bootloader and root the device, I had 4.2.1 on my phone and forced the 4.2.2 update by clearing the cache/data of a few apps when it was mentioned on this forum (Bad mistake I think). I went to download titanium with root the other day to start to backup my apps/phone before I started messing with kernels and audio upgrades in case I messed something up and needed to reinstall. Unfortunately since this is my first Android phone I didn't know that upgrading would also remove my root access. Not a problem I though, I'll just go ahead and re-root the device, well that's where I started to see various problems.
I installed the SUser 1.0.4 zip on my phone (After I tried .98), booted up into the clockwork recovery option, extracted the zip from within clockwork to root my device again and nothing. I tried a couple of times, even tried the Nexus 4 toolkit but that didn't seem to work either. Rootchecker won't recognize that my phone is rooted.
In fastboot mode it shows my phone is
Secure boot - enabled (Green)
Lock State - unlocked (red)
When I was in the Nexus 4 toolkit I also noticed that it wouldn't recognize my phone's serial USB debugging mode even when I turned it on (Pressing the build number 7 times and checking the usb debugging box in developer options). When in fastboot mode my computer recognized my phone without a problem. I am still able to move stuff on and off of the phone through windows explorer, but only when it's NOT in debugging mode, my computer beeps like something is connected when in USB debugging mode but nothing shows up anywhere except in device manager. I tried installing the drivers that were posted for 4.2.2 and also tried installing the drivers through the toolkit but neither would fix that problem. Another thing I noticed was that I never got a prompt on my phone to allow my computer access to debugging mode like people mentioned that I should get.
Now either I messed something up somewhere along the lines, (good chance)
or I'm an idiot and i'm missing something really obvious (better chance)
Anyone have any suggestions as to what I can do or how I can get my root access back?
Thanks a bunch in advance for any help you guys can give me, and if I left some info out of here that you need let me know.

kelmino said:
Now either I messed something up somewhere along the lines, (good chance)
or I'm an idiot and i'm missing something really obvious (better chance)
Click to expand...
Click to collapse
Oh wow... yup I'm an idiot and missed something really obvious....
I just installed the SuperSU app from the playstore and I do have root access again and apps request access.
ugh I'm a moron, I spent hours on this yesterday and as soon as I post this I fix the issue
Sorry guys
Now my only problem is I can't see my phone from the playstore on my computer but I'm not worried about that, I think I can fix that as I see another post up here for that same issue.

perhabs this helps
http://forum.xda-developers.com/showthread.php?t=2159744

u dont need to extraxt su zip file....download drivers..use tool kit to unlock bootloader..then flash temporary clockwork recovery...flash su in recovery....download goo manager from playstore to flash permanent recovery
Sent from my Nexus 4 using xda app-developers app

dont use toolkit. do it the long way so you know what you're doing otherwise you're walking in a room blindedly hoping you'd get through the maze.
in the long run, it'll be worth it. very simple & easy to do.

4.3 installation and rooting are giving me trouble

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.

[Q] Tmobile D801 will not boot FIXED

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

[Q] Help needed, no fastboot/adb? Cannot use any options in Root Toolkity

Hey guys, so after hours of trying to figure out what i've done, i need some help
I had a fully working Nexus last night. I'd unlocked, rooted it and installed a custom rom a few weeks ago and everything was fine. Tonight for some reason i decided i wanted a fresh install, and stupidly deleted the entire internal storage off, and then wiped the Nexus before realising i hadn't put the zips back on to reinstall. So the Nexus is without an OS and completely empty. I can get onto bootloader, and into recovery, but i have nothing on the Nexus to use to recover or install anything. I have backups and fresh custom rom zips on my pc but i can't get them to the Nexus. I'm also struggling to be able to do anything using Wugs Toolkit, because it keeps saying it can't find fastboot or adb depending on what options i try. And i can't turn USB debugging on because i have no OS
I tried to reinstall the adb drivers and could see the nexus internal storage on my pc for a minute but it wouldn't let me copy anything onto it. Now i can't seem to see it again. As for fastboot, it keeps saying it can't be found. So at this point i'm clueless, and googling around is confusing me more and more as i have no idea about any of that stuff. The automatic toolkit is as far as my knowledge goes

Update: i tried using the SDK to use cmd prompt to put it back to stock, but it seems to be stuck on the screen with the red, yellow, green and blue circles now?
Update #2: used an updated adb/fastboot installer, after that my Nexus was actually being seen in Wugs Toolkit. Used the flash & unroot option, and i'm back on my device =) hoping i'll be able to re-root and reinstall my custom rom with no problems now *fingers crossed*
Update #3: Yay all fixed. No idea how i did that but thank goodness that's over with. Not sure how to delete my thread, sorry

For future reference try skipping the toolkits, if you do this manually there is far less likely to be communication issues or others at that
Glad it all worked in the end!

Moto X pure WILL NOT show up in device manager - Anniversary Update?

Hey, my moto bricked itself today, for unknown reasons (see my post in the RR thread) and after several failed attempts to get out of the bootloop I've accepted I'm just going to have to wipe it totally clean. But I've been trying for hours to get it to show up with
Code:
fastboot devices
and Windows is having none of it.
I installed the Motorola Device Manager which supposedly comes with the drivers, and when that didn't work I tried reinstalling the drivers in Program Files\Common Files\Motorola Shared\Motorola Drivers\Motorola Driver Installer.exe. Also installed the Universal ADB drivers and those didn't help. I read that the fastboot drivers are different from the adb drivers, (and since I can't actually boot my phone to use adb), I downloaded the 15-second ADB/fastboot drivers. This was the only one that actually brought up the Windows prompt to install a "new device" or whatever.
However there's still nothing in device manager. No "Android ADB devices" category and nothing under portable devices. Yet when I get into fastboot and plug in the USB, the text at the bottom changes to indicate "Transfer Mode: USB Connected". Is this a new thing with the Anniversary Update? I can't think of anything else because I think I've literally tried about everything. I'm honestly considering selling this phone, seems like I seriously can't use anything but stock without having major problems.
EDIT: nevermind. Tried a different USB cable and bingo. Go figure, lols.
But twrp still reboots after sitting for 5 seconds at the welcome screen. Any suggestions for that?

Not sure about TWRP rebooting. Anniversary update?

Have you tried wiping dalvik and cache?

Yeah I wiped the cache. Not dalvik though but I'm not sure it would have made a difference - when I used the back to stock tool, it still hung on the big M start screen (it just showed the M, but didn't animate the little stitches or anything).
Anyways after multiple hours of trying to get it out of the NEW bootloop, I finally flashed the stock rooted ROM (update 4) and although the radio didn't work I flashed the TruPure February update radio and at least the phone works now.
But man, that was an aggravating process. I was yelling at my computer last night, I was at my wit's end. Messing with this phone in any way has gotten progressively more on my nerves

jDally987 said:
But man, that was an aggravating process. I was yelling at my computer last night, I was at my wit's end. Messing with this phone in any way has gotten progressively more on my nerves
Click to expand...
Click to collapse
This phone and its problems got on my nerves so much that i actually bought an iPhone. I don't really regret it either.
Sent from my iPhone 6S Plus using Tapatalk