Finally caught up! 4.2.2 (JDQ39)
- Thread starter chram893
- Start date
http://forums.androidcentral.com/ve...s-root-toolkit-v1-6-2-updated-12-29-12-a.html
try wugs tool kit.
I used it to flash a new stock 4.1.1 since mine was some how borked. then I manually sideloaded the update via stock recovery.
and fyi when your in stock recovery (android with the red triangle) you just need to hold power and vol up for about 30 sec then let go. if nothing happens hold power+volup for a little longer then let go
try wugs tool kit.
I used it to flash a new stock 4.1.1 since mine was some how borked. then I manually sideloaded the update via stock recovery.
and fyi when your in stock recovery (android with the red triangle) you just need to hold power and vol up for about 30 sec then let go. if nothing happens hold power+volup for a little longer then let go
RushNFour
Active member
- Mar 1, 2012
- 35
- 5
- 0
Wugs is what I used to flash back to stock, I was using Mmuzzys a while back. I've tried just about every solution I've seen online but I'm starting to think my flash to stock did not actually return me to true stock.
Sent from my Razr Maxx, which means I've probably bricked my Nexus....again!
Sent from my Razr Maxx, which means I've probably bricked my Nexus....again!
only1canoli
Well-known member
- Feb 6, 2012
- 239
- 3
- 0
Noob here, Im thinking of trying to install 4.2.2 and saw this on android community
Instructions:
? This zip requires you to be completely stock running the last OTA update, which is Android 4.1.1 (JRO03O). This is not a ROM that can be flashed over other custom ROMs, this is an official OTA update file that needs to be flashed in a custom recovery.
Download Link
1. Download file from above
2. Boot into custom recovery (using CWM or by holding volume up/down and power at same time)
3. Install update zip from SD card
4. Reboot, enjoy more Jelly Beans!
Question is Im complety stock and NOT rooted, can I do this and is it easy?
Instructions:
? This zip requires you to be completely stock running the last OTA update, which is Android 4.1.1 (JRO03O). This is not a ROM that can be flashed over other custom ROMs, this is an official OTA update file that needs to be flashed in a custom recovery.
Download Link
1. Download file from above
2. Boot into custom recovery (using CWM or by holding volume up/down and power at same time)
3. Install update zip from SD card
4. Reboot, enjoy more Jelly Beans!
Question is Im complety stock and NOT rooted, can I do this and is it easy?
BlkWolf03
Well-known member
- Apr 20, 2011
- 88
- 2
- 0
I have tried Wugs and the Gnexus Toolkit from XDA ( found here Galaxy Nexus > [GNex TOOLKIT V10.1] Drivers Backup Unlock > XDA )
Ive soft bricked my GNex a couple of times but Ubuntu screwed it up royally this last time and the the Toolkit from XDA got me back up and running in minutes - might want to give it a try
dmmarck
Retired Moderator
- Dec 28, 2011
- 8,348
- 2,594
- 0
It's easy peasy to use fastboot on Ubuntu. It's the method I personally recommend, and it will save your tail more often than not.
every update on my nexus 7 I have to re flash the stock kernel. Using fastboot is very easy once you do it a time or 2 for sure.
Apparently the status 7 I'm getting may have something to do with my version of adb. I'm running 1.0.29, the most current appears to be 1.0.31. Is there an adb guide somewhere? Trying to figure out how to install 1.0.31..
Xanth269
Well-known member
- Dec 5, 2011
- 511
- 26
- 0
Ok folks that have followed my BT issues well it works now and NOT and AOKP issue.
I feel soooo low...
I figured out my problem tonight...
it seems in the AOKP ROM there is a signal toggle, well I had that on the pull down and it was "grey-d" out, so I was getting little to no VZ service on my signal bar and it stayed Grey unless connected to Wi-Fi, so I hit it and it turned on, my VZ signal bars lite up. So I tried BT, it found the device but would not pair. Got home and tried wife's BT and it paired no issue. Seems having that signal toggle off was part of the issue but not knowing why the BT device died is strange. It wont find my wife's phone either.
Sorry for doubting AOKP.
So what is that toggle for?
I feel soooo low...
I figured out my problem tonight...
it seems in the AOKP ROM there is a signal toggle, well I had that on the pull down and it was "grey-d" out, so I was getting little to no VZ service on my signal bar and it stayed Grey unless connected to Wi-Fi, so I hit it and it turned on, my VZ signal bars lite up. So I tried BT, it found the device but would not pair. Got home and tried wife's BT and it paired no issue. Seems having that signal toggle off was part of the issue but not knowing why the BT device died is strange. It wont find my wife's phone either.
Sorry for doubting AOKP.
So what is that toggle for?
Thanks. Does this get installed to my phone in any way though? I'm not seeing how that would be what caused the status 7. All I did was download the update, transfer it to my phone and attempt to flash the zip in CWM.
No. adb and fastboot are on the computer you are interfacing your phone with.
Download and extract the SDK onto your computer. adb.exe and fastboot.exe are in the platform-tools subfolder.
dss2000
Well-known member
- Jan 21, 2012
- 727
- 4
- 0
I've been having problems with my radio with 4.2.2 (JDQ39). The known 4G dead spots have gotten much bigger. Also sometimes after going through dead spot signal meter will just stay grey and won't re-aquire a signal. Have to cycle through airplane mode to re-acquire a signal. At work where the signal is week it seems like my phone is just eating up battery trying to pull in a signal. Phone gets warm and burns through a 2100 mAh battery in 2 hours. I doubt this is what Verizon will release OTA.
I flashed back to the 4.1.1 radios, which of all the radios have worked the best for me. I hope Verizon doesn't release these newer radios in the OTA. You really notice it where the signal is weak. They are probably fine where the signal is strong.
That's what I thought. So if I'm just pulling the update on to the phone and flashing in CWM, the version of adb shouldn't have any bearing on the status 7 I'm getting when I attempt to flash, right?
Oh well, guess I'm just waiting for OTA since this won't install over stock 4.1.1 for me for whatever reason.
I don't know much about a status 7 error. Here is an older thread on the error.
http://forums.androidcentral.com/verizon-galaxy-nexus-rooting-roms-hacks/229002-status-7-error-when-flashing-any-rom.html
Do you have the latest version of the recovery? Also, try bumping the older thread up by responding to it with your problem and maybe you can get someone more knowledgeable to respond.
The update will fail also if you modded anything from the original Google image of 4.1.1...to avoid the error just download the Google factory image and fastboot the flash all file...you will be factory stock 4.1.1 which is exactly what the update is looking for and radios here are big improvement with holding 4g signal
Sent from my Galaxy Nexus using Tapatalk 2
Sent from my Galaxy Nexus using Tapatalk 2
Interesting. I am going to switch back and forth between the 4.1.1 and the 4.2.2 and do speedtests comparing the 2 to figure out which one I like best just in case there were network problems the days I had the 4.2.2 radios on my phone.
Last edited:
I seems to hold on to the signal way better rather than just go straight to 3g and the switch time from 4g/3g is a huge improvement. But I do notice sometimes if the 4g signal is bad..and I get a phone call the reception is horrible..I have to hang up then call back and never had that before and doesn't happen on my RAZR m
Sent from my Galaxy Nexus using Tapatalk 2
Sent from my Galaxy Nexus using Tapatalk 2
Similar threads
Trending Posts
-
PreOrders May Be Live- Started by Katrina White1
- Replies: 20
-
What did you think of the live event and Jimmy Fallon?- Started by Snareman
- Replies: 0
-
This might be my favorite foldable phone.- Started by TheAngryToaster
- Replies: 1
-
Facebook
Twitter
Instagram