Database Users

[Q] best way to root 4.1.2?

Hello, my girlfriends new Nexus 7 for some reason wont update to 4.2, its stuck on 4.1.2. So whats the best way to root it on 4.1.2? And afterwards, its possible to flash 4.2 on it, correct? Ive rooted a couple of different phones and customized them, but I want to make 100% sure I dont screw up her second love lol. Thanks for the help!:cyclops:

What is 4.3?
Sent from my Nexus 7 using xda app-developers app

dparrothead1 said:
What is 4.3?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
sorry, meant 4.2 LOL

Try Wug's Nexus Root Toolkit. It does a great job and walks you through each step.

thats the one I was looking at! I wasnt sure if I should use that one, or the other Toolkit, but the other one seemed a little more confusing. Thanks!

Wugfresh worked great for me this weekend.
The only unexpected headache was having to deal with device driver issues since I was rooting the n7 on a laptop that I used to root my Galaxy tab a year ago. There were 6-7 Samsung drivers that I had to remove and then reboot the laptop.
Still an easy process but the driver situation made the process take longer than expected (maybe an hour total).
Still, a lot faster and more newb friendly than rooting in 2009
Sent from my HTC Sensation using XDA Premium App

Toolkits are fail. Learn to use adb and fastboot. That way you can be sure of exactly what your doing to your phone and fix it if necessary. It may sound daunting at first but in the long run it's much better.
Sent from my Nexus 4 using Tapatalk 2

zidane1341 said:
Hello, my girlfriends new Nexus 7 for some reason wont update to 4.2, its stuck on 4.1.2. So whats the best way to root it on 4.1.2? And afterwards, its possible to flash 4.2 on it, correct? Ive rooted a couple of different phones and customized them, but I want to make 100% sure I dont screw up her second love lol. Thanks for the help!:cyclops:
Click to expand...
Click to collapse
dr.m0x said:
Toolkits are fail. Learn to use adb and fastboot. That way you can be sure of exactly what your doing to your phone and fix it if necessary. It may sound daunting at first but in the long run it's much better.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Completely agree with this...
-----------
Hi, zidane1341...
Rooting is really simple.
(You will need an unlocked bootloader for this).
Get a custom recovery .img for your device...
Either CWM - http://www.clockworkmod.com/rommanager
...or TWRP - http://www.teamw.in/project/twrp2/103
...it matters little which.
-----------
fastboot flash it.
-----------
Get Chainfires SU .zip package here http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Flash it using the custom recovery you've just fastboot flashed...
Reboot... and you're rooted.
-----------
Having said all that though, I don't see how root will facilitate an upgrade of your girlfriends N7 from 4.1.2 to 4.2...
For that you will need the factory stock image for your device, available here http://developers.google.com/android/nexus/images.
There is a thread here http://forum.xda-developers.com/showthread.php?t=1907796, that details how to flash factory stock images.
-----------
On a final note... it's kind of puzzling why your girlfriends N7 isn't being automatically upgraded to 4.2.
When I flash back to stock, (as I do, from time to time), I use JOP40C (4.2) and as soon as I get a WiFi connection, I get 'nagged' about upgrading to JOP40D (4.2.1), which I always allow. And it does so without problems.
If your girlfriends N7 is running (even at the slightest level) a modified version of JellyBean, then the automated update procedure from Google's servers will fail.
Rgrds,
Ged.

Well I know from personal experience, after I rooted my optimus I could upgrade to a newer version of android, I can just flash 4.2 after rooting correct? I called Asus and they said to send it in, but they didn't know what was wrong. My girlfriend is pretty mad about that, so I was thinking I could bypass that by doing it myself.

4.4, stuck on circle google logo

as the title.. i already tried the 2 different release, tried to make wipe data/factory reset, still doesn't work.. i search around and i can't ind anything..

Were they custom Roms? If so, what radio do you have. If all else fails, use the factory images to reset.
Sent from my Nexus 7 using XDA Premium 4 mobile app

I'm trying with stock......... not with custom
Inviato dal mio Galaxy Nexus utilizzando Tapatalk

nothing, i can only use 4.2.2 stock, if i try to update via ota i can't boot the phone, same for 4.4, can someone please help me?

=( i'm keeping trying for nothing, i can use the phone only with 4.2.2, i try to manually flash bootloader and radio of 4.4, and the rom, nothing.. i also try with wugfresh tool, nothing, i try with purity and nexus 5 port rom, nothing.. please, i can't figured out

so.. same problem of this guys: http://forum.xda-developers.com/showthread.php?p=48218254#post48218254
now i flashed 4.3 with 4.2 radio and it's working, but for us is impossible to use 4.4

It sucks that such a problem should happen to a phone that was Google's flagship.So many people suffering from this problem and not a single working solution.Flashing factory images via fastboot or old modems does not fix this at all nor any toolkit. I have made two threads about this and still nothing. I am stuck on Android 4.2.2 without radio and can't even RMA in my country so I am using it like a tablet without phone till I sell it at a loss. i wont recommend this phone to anyone especially in my country where it is not available via Play store. Money is hard earned and mine has gone down the drain. How I wish I had never bought this phone never in my wildest dreams could have known that it would suffer from such a pathetic unfixable bug just because the 4.3 update mysteriously breaks something in a few devices that renders them useless as a phone and to be updated. Hell whats the use of a non updatable nexus that cant make one puny call? Thumbs down.

what? try to put 4.3 and flash .48 radio, it work and you can use it as normal phone..

Hi
I was stuck at 4 circles when my phone got upgraded to 4.4
I then flashed 4.3. It was again stuck at 4 circles
I then flash 4.2.2. Now i was able to restart the phone but it is not connecting to any network
Can anyone help me out

my solution: sell the phone.

icedzed said:
what? try to put 4.3 and flash .48 radio, it work and you can use it as normal phone..
Click to expand...
Click to collapse
As per you, atleast my phone should work after flashing 4.2.2
But i am not able to connect to any network after flashing 4.2.2

mine too working with 4.2.2 perfectly and also 4.3(you have to flash the radio of 4.2.2) i don't have problem with network, but you can't update the phone, and i buy the nexus 4 for kitkat

[Q] D800 - No recovery - Unable to flash in DL mode

So I'll start by saying I made a boo boo and this is 100% my fault.
I rooted my stock D800 and flashed TWRP. I flashed Cyanogenmod but where I messed is up when I flashed the D802 ROM and not the D800. I figured I'd just boot into recovery again using the hardware buttons, but all that happens is the screen turns on but nothing actually displays.
After that, I figured I'd just flash a stock ROM and basically start over using Download Mode and FlashTool. Unfortunately, I can't flash the stock firmware because the phone is NOT identifying itself as a D800, it's identifying as a D802, so FlashTool will not allow me to flash the proper files.
What I don't understand is why was I able to get into TWRP that one instance and flash the ROM but now whenever I attempt to get into recovery again the screen just turns on but recovery doesn't show. Makes no sense to me. I've tried getting into recovery using the hardware buttons a million times after but no dice.
I know it's not much, but I'm willing to throw in 10 bucks via PayPal for whoever can help me fix this.

bbeaulieu said:
So I'll start by saying I made a boo boo and this is 100% my fault.
I rooted my stock D800 and flashed TWRP. I flashed Cyanogenmod but where I messed is up when I flashed the D802 ROM and not the D800. I figured I'd just boot into recovery again using the hardware buttons, but all that happens is the screen turns on but nothing actually displays.
After that, I figured I'd just flash a stock ROM and basically start over using Download Mode and FlashTool. Unfortunately, I can't flash the stock firmware because the phone is NOT identifying itself as a D800, it's identifying as a D802, so FlashTool will not allow me to flash the proper files.
What I don't understand is why was I able to get into TWRP that one instance and flash the ROM but now whenever I attempt to get into recovery again the screen just turns on but recovery doesn't show. Makes no sense to me. I've tried getting into recovery using the hardware buttons a million times after but no dice.
I know it's not much, but I'm willing to throw in 10 bucks via PayPal for whoever can help me fix this.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2582845 This ROM is compatible with both d800 and d802 variants. You can try flashing this just to get your phone up and running

Art Vanderlay said:
http://forum.xda-developers.com/showthread.php?t=2582845 This ROM is compatible with both d800 and d802 variants. You can try flashing this just to get your phone up and running
Click to expand...
Click to collapse
Unfortunately I can't do that because I can't get into recovery mode

Im in the same situation as you bro. Tried to use LG flash tools to flash my sprint back to stock and its detecting my phone as a d801. No help yet

same here from 2 weeks..

EVERYONE! I have found a resolution for this.
First, visit this thread.
Download the DLL from this post and flash with a normal stock ROM. I used this combo and it flashed WITHOUT issue. Hope it helps you guys out as well.

bbeaulieu said:
EVERYONE! I have found a resolution for this.
First, visit this thread.
Download the DLL from this post and flash with a normal stock ROM. I used this combo and it flashed WITHOUT issue. Hope it helps you guys out as well.
Click to expand...
Click to collapse
Yeah this should Definitely be in a FAQ somewhere
Sent from my LG-D800 using xda app-developers app

afrojoc said:
Yeah this should Definitely be in a FAQ somewhere
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
No you guys just need to slow down.
Sent from my SCH-I545 using XDA Premium 4 mobile app

JCBiznatch said:
No you guys just need to slow down.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So it doesn't need to be in FAQ somewhere?Lol it would've helped me out dramatically! It's not my fault that there are recoveries that mess up your phone. Coming from Samsung phones I didn't think that someone would release faulty software that would render your phone unusable.

Screen discoloration and weird zoom after trying to flash CM-11

Hi all,
Today has been a disastrous day for me. My Nexus 4 decided to update itself and got stuck at "Android is updating.... Starting apps.." screen. It is rooted and the bootloader is unlocked. Fastboot recognized my phone but not adb and I couldn't figure my way out of that so I basically reset my phone, flashing the stock version of Android 4.4.2.
It worked fine for a few minutes, so I tried flashing the latest snapshot version of CM-11, but that failed. I believe it was after I restarted my phone that everything became discoloured and the screen was zoomed in and repeated.
I tried flashing the stock ROM again in hopes of fixing the discolouration and zooming, but it didn't help. I've attached a picture of what my phone's display looks like. The colours of the bootloader are normal and unaffected.
Can anybody help me with this? I've been using Android Toolkit 1.2.8 and Nexus Root Toolkit on my Windows 8.1 x64 laptop. My Nexus 4 currently has the stock version of Android 4.4.2.
I'm inexperienced at this, so please let me know if more information is required.

you are using a kernel that support AOSP rom with a CM11, you should use a compatible kernel

Svarion said:
you are using a kernel that support AOSP rom with a CM11, you should use a compatible kernel
Click to expand...
Click to collapse
Thanks for the fast response,
Sorry, could you be more specific? I not QUITE sure what that means, but could it not be an issue if I've flashed the stock 4.4.2 onto my phone?

Thank YOU!
I guess I kind of remember flashing the stock 4.4.2 failed (I think it said too many connections), but I retried it just now after restarting my computer and the display is back to normal.
In terms of kernels, how will I know which kernel(s) is/are compatible?

n4helpneeded said:
I guess I kind of remember flashing the stock 4.4.2 failed (I think it said too many connections), but I retried it just now after restarting my computer and the display is back to normal.
In terms of kernels, how will I know which kernel(s) is/are compatible?
Click to expand...
Click to collapse
if you are using cm11 or any rom based on cm11 you should use a compatible kernel, if you are using stock/aosp rom you can use almost all kernels like franco.kernel, ak, hellscore

Nexus 4 Touchscreen Issue With 4.2.2

I have a Nexus 4 and it came to me with Android 4.4.4, and I tried to install roms based/required Android 4.2.2. However, when I use any rom that isn't based on 4.4 or 5, the touchscreen will not register touches. I reinstall android 5, and it works. I install Firefox OS, it works. Ubuntu Touch works. LuneOS, CM 10.2 and ColorOS, however, do not because they are based on 4.2. Has anyone else had this issue or know of a solution?

achunt2143 said:
I have a Nexus 4 and it came to me with Android 4.4.4, and I tried to install roms based/required Android 4.2.2. However, when I use any rom that isn't based on 4.4 or 5, the touchscreen will not register touches. I reinstall android 5, and it works. I install Firefox OS, it works. Ubuntu Touch works. LuneOS, CM 10.2 and ColorOS, however, do not because they are based on 4.2. Has anyone else had this issue or know of a solution?
Click to expand...
Click to collapse
Try to flash the bootloader that came with 4.2.2
Sent from my Nexus 4 using Tapatalk

Warbuff said:
Try to flash the bootloader that came with 4.2.2
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
That didn't work. Cyanogenmod 11 had the same issue last night, but I went and fixed permissions and that helped, but fixing the permissions isn't working with 4.2.2.

I can confirm that every other version of android I have used on this phone, and I just tried 4.4.4, 4.4.2, 4.4, 4.3, all respond to touch. 4.2.2 still does not work.

Could it have something to do with the bootloader being unlocked?
Sent from my SM-G900P

achunt2143 said:
Could it have something to do with the bootloader being unlocked?
Sent from my SM-G900P
Click to expand...
Click to collapse
It shouldn't matter whether it's unlocked or not. Unfortunately i don't know what else you can try.
Sent from my Nexus 4 using Tapatalk

Well thanks for trying. Hopefully I'll get a solution and will be able to share
Sent from my SM-G900P

I tried just disconnecting and reconnecting the touchscreen connection and it worked, but that has to be done after every reboot.