So I've bought myself a new Nexus 7 and to my surprise the version of android out of the box was 4.2. After about an hour it asked me to download the "new update". I pressed on it and it said, install the new Android 4.2. I was a bit confused here, why it wanted to update to the same version but I let it anyway since it started asking. Now of course my android version is 4.2 still and it won't update to 4.2.1 or 4.2.2, I am clicking check for updates but nothing happens, it says it's "up to date" which can't be true...
Not sure what I did wrong, but I would appreciate some guidance, thank you!
Settings -> About tablet.
What "Build number" is reported? Should start with a J
bftb0 said:
Settings -> About tablet.
What "Build number" is reported? Should start with a J
Click to expand...
Click to collapse
It says JOP40C
N7 WiFi-Only : http://www.randomphantasmagoria.com/firmware/nexus-7/nakasi/
N7 3g : http://www.randomphantasmagoria.com/firmware/nexus-7/nakasig/
You want the JOP40C -> JOP40D OTA
Manual install is possible w/stock recovery
Get it to /sdcard , rename to update.zip
Charge battery well
Power off, boot to bootloader/fast boot mode
Select Recovery
When droid lying on back appears, press power+Vol-up, recovery menu should appear
Select update.zip, press power.
Repeat entire process for JOP40D -> JDQ39
Gotta go to sleep, no spoon feeding tonight.
bftb0 said:
You want the JOP40C -> JOP40D OTA
Manual install is possible w/stock recovery
Get it to /sdcard , rename to update.zip
Charge battery well
Power off, boot to bootloader/fast boot mode
Select Recovery
When droid lying on back appears, press power+vol-down, recovery menu should appear
Select update.zip, press power.
Repeat entire process for JOP40D -> JDQ39
Gotta go to sleep, no spoon feeding tonight.
Click to expand...
Click to collapse
Erm, thanks ? But why isn't my device updating by default ? Is this some sort of bug or ?
Xandon said:
Erm, thanks ? But why isn't my device updating by default ? Is this some sort of bug or ?
Click to expand...
Click to collapse
In my experiences with other android devices, if you attempt an OTA patch and it fails, the OS which launched the patch (by booting the recovery) has no means to know whether the OTA suceeded or not - it merely assumes that it has... and will no longer offer you a second chance.
If that is the case, only manual updates are possible.
There is possibly a flag somewhere that could be cleared - perhaps via factory reset - that would allow you another go. I don't know where it is, or whether it is reachable on a non-rooted phone without a factory reset.
good luck
PS If you perform it again and get an error, WRITE DOWN THE ERROR MESSAGE.
bftb0 said:
In my experiences with other android devices, if you attempt an OTA patch and it fails, the OS which launched the patch (by booting the recovery) has no means to know whether the OTA suceeded or not - it merely assumes that it has... and will no longer offer you a second chance.
If that is the case, only manual updates are possible.
There is possibly a flag somewhere that could be cleared - perhaps via factory reset - that would allow you another go. I don't know where it is, or whether it is reachable on a non-rooted phone without a factory reset.
good luck
PS If you perform it again and get an error, WRITE DOWN THE ERROR MESSAGE.
Click to expand...
Click to collapse
Thanks but the weird thing is, after it prompted me to update to 4.2 from 4.2 and I did it, it was successful. It's why I find it odd
I do have to mention that I have the Nexus 7 32 GB 3G Version if that's any help to anyone..
So I did this : http://www.reddit.com/r/Nexus7/comments/18hp5p/tip_for_anyone_who_hasnt_gotten_the_422_update_yet/
And now my device is updated to 4.2.2 , how odd
Xandon said:
So I did this : http://www.reddit.com/r/Nexus7/comments/18hp5p/tip_for_anyone_who_hasnt_gotten_the_422_update_yet/
And now my device is updated to 4.2.2 , how odd
Click to expand...
Click to collapse
Well, there you go - that's where the state data is located - good find! As to the why of the original failure, one speculation is an incomplete download. In contrast with cwm/twrp, the stock recovery does a crypto signing check over the whole archive. If it was a couple bytes short, it might unpack correctly, but it won't pass the signing check.
If you had made note of the error, you wouldn't be saying "how odd"; you would be saying "here's the exact error that occurred to me".
Glad things worked out - thanks for posting that link.
I got my nexus 7 wifi onlu (4.1) and it shows an update available of 4.2.
I just want to save my Wifi Data Traffic ... So wished to update manually ....
googled and found solutions ...
http://www.androidauthority.com/how...nexus-7-and-nexus-10-to-android-4-2-2-156784/
but the recover mode method confused me , i thought it need adb .... is the above link specifies an update rather than a complete ROM flashing
So my question is this
1.
can i update using the Downloaded Zip using recovery mode in nexus?
2.
The link i gt my net has two different size one
http://r2---sn-o3o-itqe.c.android.c....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (47mb)
https://dl.google.com/dl/android/aosp/nakasi-jdq39-factory-c317339e.tgz (275 Mb)
Why the File size differs ? is the first one an Update Zip and second One a complete ROM ?
3. Do i need adb installed to update from recovery ?
I dont wanna root and install CMW now ... will try later ... im using a DEFY for last 2 years and flashing many ROMS ...so i know basic android terminologies ... thanks in advance ... please reply ...
For a pure stock device with a locked bootloader, the only upgrade path is via OTA file bundle if you insist on keeping the bootloader locked. The large (complete) factory images can only be used with fastboot and an unlocked bootloader.
To do the OTA manually, rather than via automatic WiFi download , I recall that the stock recovery no longer has a "update.zip" menu choice, but instead has a menu choice for ADB sideload*. This implies that you need to get ADB working ahead of time to manually apply the OTA.
You are correct about the two file types - the smaller one is a differential patch set (OTA), and the larger a complete factory ROM for use with fastboot as mentioned above.
Because the OTAs are patch sets they are tightly matched to the version of software on your tablet... and you said something vague about your current software version. For instance, you mentioned the OTA file
6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
... but said that you have "4.1"
4.1.2 would be JZO54K, not JOP40D (which is 4.2.1; JDQ39 is 4.2.2)
So, please state your exact software version number you currently have - and the version you want to go to. And have a look at the OTA thread
*might depend on which version of stock software you have on the tablet.
thanks ....... i dnt have nexus 7 with me now (my wife took it for some office works)and so cant verify the version .... But i remember its 4.1 and it no updates was done after i gt it ....
and thanks for pointing the mistake that 47mb zip was for 4.2.1 to 4.2.2 and not for 4.1 to 4.2.
i got http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JZO54K.da55f917.zip link from XDA Link ...
Now tell me can i use this file ??
i cant directly Update using recovery menu .... ???
and i need to unlock bootloader to use ADB ??
bftb0 said:
For a pure stock device with a locked bootloader, the only upgrade path is via OTA file bundle if you insist on keeping the bootloader locked. The large (complete) factory images can only be used with fastboot and an unlocked bootloader.
To do the OTA manually, rather than via automatic WiFi download , I recall that the stock recovery no longer has a "update.zip" menu choice, but instead has a menu choice for ADB sideload*. This implies that you need to get ADB working ahead of time to manually apply the OTA.
You are correct about the two file types - the smaller one is a differential patch set (OTA), and the larger a complete factory ROM for use with fastboot as mentioned above.
Because the OTAs are patch sets they are tightly matched to the version of software on your tablet... and you said something vague about your current software version. For instance, you mentioned the OTA file
6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
... but said that you have "4.1"
4.1.2 would be JZO54K, not JOP40D (which is 4.2.1; JDQ39 is 4.2.2)
So, please state your exact software version number you currently have - and the version you want to go to. And have a look at the OTA thread
*might depend on which version of stock software you have on the tablet.
Click to expand...
Click to collapse
v2dare said:
thanks ....... i dnt have nexus 7 and so cant verify the version .... But i remember its 4.1 and it no updates was done after i gt it ....
Click to expand...
Click to collapse
The EXACT version is needed in order to choose the correct OTA file, there have been five different versions of "4.1" for nakasi. See here.
v2dare said:
i got http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JZO54K.da55f917.zip link from XDA Link ...
Now tell me can i use this file ??
Click to expand...
Click to collapse
Only if you have JZO54K on your tablet. As I noted, there was more than one version of "4.1"
v2dare said:
i cant directly Update using recovery menu .... ???
Click to expand...
Click to collapse
Depends on what version you have.
v2dare said:
and i need to unlock bootloader to use ADB ??
Click to expand...
Click to collapse
No. You only need to unlock the bootloader in order to flash partitions or boot arbitrary images with fastboot. ADB sideload does not need an unlocked bootloader.
I can't help further until you know the exact version number. (I'm going to bed now anyways)
gudnyt :victory: will update after getting the exact version..
i updated nexus from 4.1.1 to 4.2.2 when i gt wifi in my office ....
Now should i clear data and dalvinik cache for better performance ??
You can update to 4.2.2 with fast boot... Don't need root or a custom recovery to do that
Press thanks if I helped ~ Nexus7/Stock4.2.2/MKernel
v2dare said:
i updated nexus from 4.1.1 to 4.2.2 when i gt wifi in my office ....
Now should i clear data and dalvinik cache for better performance ??
Click to expand...
Click to collapse
4.1.1 = one of JRO03C, JRO03D, or JRO03S (but not JZO54K). How did you use the tablet for so long without getting the update already? (Perhaps you just ignored the update messages?)
Clearing the dalvik cache probably won't change anything, but certainly can not hurt. On the other hand though, wiping /data is essentially the same thing as a "factory reset".
(To be clear, "factory reset" in Android-speak does not mean "return to the original firmware" - it means instead "wipe away all traces of user customization".)
good luck
Like i said i gt nexus 7 last week only and while using wifi i noticed some lag in internet speed ... then i checked OS version and found its updating in background....
So i stopped update by clearing the cache and didnt checked for "update available" thereafter as i know it will again start updating the OS....
now gt a Wifi connection, downloaded the 102mb patch and now its 4.2.2
bftb0 said:
4.1.1 = one of JRO03C, JRO03D, or JRO03S (but not JZO54K). How did you use the tablet for so long without getting the update already? (Perhaps you just ignored the update messages?)
Clearing the dalvik cache probably won't change anything, but certainly can not hurt. On the other hand though, wiping /data is essentially the same thing as a "factory reset".
(To be clear, "factory reset" in Android-speak does not mean "return to the original firmware" - it means instead "wipe away all traces of user customization".)
good luck
Click to expand...
Click to collapse
I have a Nexus 7 (Wi-Fi only) stuck on 4.1.1. Build is JRO03S. I got this as a gift for XMas and haven't been able to update it at all OTA. It's stock. I'm able to download the 4.2.2 update just fine, but the problem comes when I'm installing the update. The progress bar gets to about 20-25%, then it stops; this is signified with the android mascot falling down dead with a red exclamation triangle popping out of it's opened chest. Help?
Same problem
anorton02 said:
I have a Nexus 7 (Wi-Fi only) stuck on 4.1.1. Build is JRO03S. I got this as a gift for XMas and haven't been able to update it at all OTA. It's stock. I'm able to download the 4.2.2 update just fine, but the problem comes when I'm installing the update. The progress bar gets to about 20-25%, then it stops; this is signified with the android mascot falling down dead with a red exclamation triangle popping out of it's opened chest. Help?
Click to expand...
Click to collapse
I've got the same problem as this guy. My nexus has been "trying" to update for well over a year and nothing has worked. I cant find much info on the problem outside of suggestions to clear the cache and do the reset but that doesnt help....
Hi everyone,
I'm using QBKing77's tutorial to manually upgrade my Nexus 7 to Kit Kat 4.4 (and up) but haven't been able to with ClockworkMod Recovery installed.
The video I'm using is on YouTube, titled: "Manually Update the Nexus 7 to Android 4.4 KitKat" and at the step at 3:38 I don't know what to do.
(sorry I'm unable to post links bc I'm a new user:crying
CWM doesn't have the 'Apply update from ADB' option that stock Recovery has (or at least I'm not sure what to do in its place).
If anyone knows how I can continue the upgrade process it would really help!
Thanks in advance :good:
hennimore said:
Hi everyone,
I'm using QBKing77's tutorial to manually upgrade my Nexus 7 to Kit Kat 4.4 (and up) but haven't been able to with ClockworkMod Recovery installed.
The video I'm using is on YouTube, titled: "Manually Update the Nexus 7 to Android 4.4 KitKat" and at the step at 3:38 I don't know what to do.
(sorry I'm unable to post links bc I'm a new user:crying
CWM doesn't have the 'Apply update from ADB' option that stock Recovery has (or at least I'm not sure what to do in its place).
If anyone knows how I can continue the upgrade process it would really help!
Thanks in advance :good:
Click to expand...
Click to collapse
Hi, hennimore...
From your post, I assume you have already CWM installed... if so, then upgrading is pretty straightforward. Assuming further, that you can boot your Nexus 7 into Android normally, you can flash an OTA .zip directly from the Nexus 7 itself... without recourse to ADB or a PC.
The first thing to do is to determine the build number of the currently installed version of Android you're running. This is found in SETTINGS>>ABOUT TABLET>>... and at the bottom, will be the build number.
Next, go here where you will find an archive of all currently known OTA .zips for the Nexus 7 (2012)... listed by build number.
Using Chrome (or whatever Android browser you're currently using) download to your Nexus 7, the correct OTA .zip(s) appropriate to your situation. Depending on how old your current version of Android is, you may have to download more than one.
For example... if you're currently running Jellybean 4.2.2, build JDQ39 on a WiFi only 'nakasi/grouper' Nexus 7, the 'update path' is as follows... and the OTA .zips you'll need are...
----------------------------------------------------
JWR66Y from JDQ39
Updates Jellybean 4.2.2 TO Jellybean 4.3
KOT49H from JWR66Y
Updates Jellybean 4.3 TO KitKat 4.4.2
----------------------------------------------------
Keeping in mind this is just an example (your situation maybe different), these should be flashed IN THE ORDER GIVEN ABOVE... slowly bringing your Nexus 7 up to date. From Jellybean 4.2.2 through Jellybean 4.3 and finally arriving at the latest build of Android, KOT49H - KitKat 4.4.2.
It's important you download the OTA's relevant to the type of Nexus 7 you have... so for a WiFi only model, you need 'nakasi/grouper' OTA's... if it's a WiFi/3G model, then you need 'nakasig/tilapia' OTA's.
Now to flash...
Once you've downloaded the OTA zip (or zips) to your Nexus 7... shut down the device completely. Reboot it into the bootloader, with the VOL DOWN+hold, POWER ON key press sequence. Once in the bootloader, and using the VOL BUTTONS, navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. Your device should now boot into CWM.
Once there, select the INSTALL ZIP option, followed by the CHOOSE ZIP FROM /SDCARD option. Navigate (via the 0/ folder) to the /download folder on the internal storage of the Nexus 7... where you should find the OTA .zip(s) you previously downloaded via Chrome or other Android browser. Select NO, YES or GO BACK accordingly.
I'm not sure it matters, but if you have to flash more than one OTA .zip to bring your Nexus 7 up to date, then I recommend booting normally in between flashes... just to make sure everything is working OK.
Unless you're running a really old version of Android, say Jellybean 4.1.2, I can't see it taking more than a couple of reboots into CWM. And if you're currently on Jellybean 4.3, then it's just one OTA .zip flash.
A few caveats...
If you've modified system files in any way, these OTA's will fail, as they expect to find unmodified versions of stock Android system files. If they've been changed, say as a result of a Custom ROM or Custom Kernel flash... then they can't be 'patched', ie., updated... and the OTA will abort, with no changes made.
Root and having a Custom Recovery (CWM or TWRP) installed however, won't block an OTA... although you will loose both during the OTA update procedure.
If you're familiar with fastboot, then it's relatively straightforward to re-acquire them after the OTA update(s).
Hope this helps... and good luck.
Rgrds,
Ged.
Wow really appreciate and very useful for me Mr blake. Thanks a lot. One question, im in stock 4.4 krts160 with root and unlock bootloader with twrp cwm, i m going to flash the newest ota, will this step erase my root and relock my bootloader? Or i watch in youtube post by rootjunkies that twrp can handle ota. What would you suggest the better way. And thanks again for the information.
Sent from my MB855 using xda premium
deny_kei said:
Wow really appreciate and very useful for me Mr blake. Thanks a lot. One question, im in stock 4.4 krts160 with root and unlock bootloader with twrp cwm, i m going to flash the newest ota, will this step erase my root and relock my bootloader? Or i watch in youtube post by rootjunkies that twrp can handle ota. What would you suggest the better way. And thanks again for the information.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Hi, deny_kei...
You will loose root, and your Custom Recovery... whether that be TWRP or CWM.
I'm afraid it's unavoidable - it's always been that way with OTA's. You have to fastboot flash your Custom Recovery of choice again afterwards, and re-root... not difficult, but a bit of a nuisance nontheless.
Flashing an OTA, though, will NOT re-lock the bootloader.
The bootloader will remain unlocked until you purposefully choose to relock it with fastboot oem lock.
TWRP should be able to handle an OTA flash. I'm currently using CWM (with which I flashed the KitKat 4.4.2 OTA), but I've never had any problems myself applying OTA's with TWRP in the past.
Rgrds,
Ged.
GedBlake said:
Hi, hennimore...
From your post, I assume you have already CWM installed... if so, then upgrading is pretty straightforward. Assuming further, that you can boot your Nexus 7 into Android normally, you can flash an OTA .zip directly from the Nexus 7 itself... without recourse to ADB or a PC.
The first thing to do is to determine the build number of the currently installed version of Android you're running. This is found in SETTINGS>>ABOUT TABLET>>... and at the bottom, will be the build number.
Next, go here where you will find an archive of all currently known OTA .zips for the Nexus 7 (2012)... listed by build number.
Using Chrome (or whatever Android browser you're currently using) download to your Nexus 7, the correct OTA .zip(s) appropriate to your situation. Depending on how old your current version of Android is, you may have to download more than one.
For example... if you're currently running Jellybean 4.2.2, build JDQ39 on a WiFi only 'nakasi/grouper' Nexus 7, the 'update path' is as follows... and the OTA .zips you'll need are...
----------------------------------------------------
JWR66Y from JDQ39
Updates Jellybean 4.2.2 TO Jellybean 4.3
KOT49H from JWR66Y
Updates Jellybean 4.3 TO KitKat 4.4.2
----------------------------------------------------
Keeping in mind this is just an example (your situation maybe different), these should be flashed IN THE ORDER GIVEN ABOVE... slowly bringing your Nexus 7 up to date. From Jellybean 4.2.2 through Jellybean 4.3 and finally arriving at the latest build of Android, KOT49H - KitKat 4.4.2.
It's important you download the OTA's relevant to the type of Nexus 7 you have... so for a WiFi only model, you need 'nakasi/grouper' OTA's... if it's a WiFi/3G model, then you need 'nakasig/tilapia' OTA's.
Now to flash...
Once you've downloaded the OTA zip (or zips) to your Nexus 7... shut down the device completely. Reboot it into the bootloader, with the VOL DOWN+hold, POWER ON key press sequence. Once in the bootloader, and using the VOL BUTTONS, navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. Your device should now boot into CWM.
Once there, select the INSTALL ZIP option, followed by the CHOOSE ZIP FROM /SDCARD option. Navigate (via the 0/ folder) to the /download folder on the internal storage of the Nexus 7... where you should find the OTA .zip(s) you previously downloaded via Chrome or other Android browser. Select NO, YES or GO BACK accordingly.
I'm not sure it matters, but if you have to flash more than one OTA .zip to bring your Nexus 7 up to date, then I recommend booting normally in between flashes... just to make sure everything is working OK.
Unless you're running a really old version of Android, say Jellybean 4.1.2, I can't see it taking more than a couple of reboots into CWM. And if you're currently on Jellybean 4.3, then it's just one OTA .zip flash.
A few caveats...
If you've modified system files in any way, these OTA's will fail, as they expect to find unmodified versions of stock Android system files. If they've been changed, say as a result of a Custom ROM or Custom Kernel flash... then they can't be 'patched', ie., updated... and the OTA will abort, with no changes made.
Root and having a Custom Recovery (CWM or TWRP) installed however, won't block an OTA... although you will loose both during the OTA update procedure.
If you're familiar with fastboot, then it's relatively straightforward to re-acquire them after the OTA update(s).
Hope this helps... and good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks so much for the helpful response! I should have also mentioned that I currently have AOKP running on my N7
(Version: aokp_grouper_jb_build-2 Build number: aokp_grouper-userdebug 4.1.1 JRO03L eng.roman.20120916.095343 test-keys)
I'm not sure how this affects the update process, but would definitely appreciate any other help you can offer.
Thanks again!
hennimore said:
Thanks so much for the helpful response! I should have also mentioned that I currently have AOKP running on my N7
(Version: aokp_grouper_jb_build-2 Build number: aokp_grouper-userdebug 4.1.1 JRO03L eng.roman.20120916.095343 test-keys)
I'm not sure how this affects the update process, but would definitely appreciate any other help you can offer.
Thanks again!
Click to expand...
Click to collapse
Hi, hennimore...
As you're running a Custom ROM, you can pretty much forget about OTA's... as they are only designed to upgrade official stock firmware from Google. If you were to attempt to flash any OTA on your Nexus 7 as it currently stands, it would abort almost immediately during the verification phase of the OTA update process. Because nothing in /system would match what the OTA expects to subsequently 'patch' (update) in the second half of the OTA update process.
Your only option, if you wish to have official stock KitKat installed on your Nexus 7, is to fastboot flash back to factory stock.
For this, you will need the full factory stock image for your Nexus 7, available here.
(Currently, build KOT49H KitKat 4.4.2 is not yet available as a full factory image... just KRT16S KitKat 4.4... but that's not a problem...'cos once you have KitKat 4.4 installed, you can then use an OTA to bring it completely up to date... as detailed in my previous post).
Instructions on how to restore factory stock are available here.
This process is more time consuming than it is technically difficult... because fastboot flashing back to factory stock essentially wipes the device... so before you can begin, you need to backup all of your apps and associated app data with Titanium (requires root), and then backup the entire contents of the Nexus 7's internal storage to your PC... for later restore AFTER you've fastboot flashed KitKat.
Fastboot flashing back to factory stock resets the device, as though it where new. You'll need to set up your WiFi password again... and re-enter your Google Account (gmail) details... and restore all your data from your PC... fastboot flash CWM or TWRP in order to re-root. Once rooted, you can then use Titanium to restore all your apps.
Longwinded and tediously time consuming, it certainly is... but it's the only way to get official KitKat on your Nexus 7 if you're currently running a Custom ROM.
Rgrds,
Ged.
GedBlake said:
Hi, hennimore...
As you're running a Custom ROM, you can pretty much forget about OTA's... as they are only designed to upgrade official stock firmware from Google. If you were to attempt to flash any OTA on your Nexus 7 as it currently stands, it would abort almost immediately during the verification phase of the OTA update process. Because nothing in /system would match what the OTA expects to subsequently 'patch' (update) in the second half of the OTA update process.
Your only option, if you wish to have official stock KitKat installed on your Nexus 7, is to fastboot flash back to factory stock.
For this, you will need the full factory stock image for your Nexus 7, available here.
(Currently, build KOT49H KitKat 4.4.2 is not yet available as a full factory image... just KRT16S KitKat 4.4... but that's not a problem...'cos once you have KitKat 4.4 installed, you can then use an OTA to bring it completely up to date... as detailed in my previous post).
Instructions on how to restore factory stock are available here.
This process is more time consuming than it is technically difficult... because fastboot flashing back to factory stock essentially wipes the device... so before you can begin, you need to backup all of your apps and associated app data with Titanium (requires root), and then backup the entire contents of the Nexus 7's internal storage to your PC... for later restore AFTER you've fastboot flashed KitKat.
Fastboot flashing back to factory stock resets the device, as though it where new. You'll need to set up your WiFi password again... and re-enter your Google Account (gmail) details... and restore all your data from your PC... fastboot flash CWM or TWRP in order to re-root. Once rooted, you can then use Titanium to restore all your apps.
Longwinded and tediously time consuming, it certainly is... but it's the only way to get official KitKat on your Nexus 7 if you're currently running a Custom ROM.
Rgrds,
Ged.
Click to expand...
Click to collapse
Ah, I'm sad to hear that I must flash back, but I appreciate the information! Thanks again for all of you help, hopefully I can complete the process without any hiccups!
Thanks Mr Blake i will considered using ota, nevertheless my last ota i got stuck in the softbrick although my nexus is stock,unlock an unroot.
Thanks for this useful information
Sent from my MB855 using xda premium
I've been following your steps and seem to have hit a wall when I need to install the adb drivers. I went to the link included in your instructions and followed their tutorial for a Windows 7 PC. After coming back to your instructions, I continued to the step with the Command Prompt.
I entered the command correctly as written, however I get no results under the List of devices attached.
I'm not sure if this is related to the problem, but when I am in Device Manager trying to Locate Android Phone in the right pane, all that shows for me is 'Nexus 7' - which I would assume should work.
However, after Right-clicking on 'Nexus 7' (Android Composite ADB Interface doesn't appear) and selecting Update Driver, I continue through the steps to where I must manually update the driver, and I received a message stating, "The best driver software for your device is already installed"
Under that it says, "Windows has determined the driver software for your device is up to date. MTP USB Device"
I'm not sure if you can make anything of this, but I figured I'd ask since you've been so helpful thus far :angel:
Hi guys,
I've been having problems to update to 4.4 in the Nexus 7 wifi version, the only thing I done is unlock the bootloader and root, once I tried the OTA upgrade it starts the process and then it shows up the Android little guy with an error, and doesn't shows the error of installation. I tried once the flashing the zip file using TWRP and it just failed. After the first failed the tablet just started to lag horribly. Any suggestions on how to fix this?
Sent from my Nexus 7 using xda app-developers app
GedBlake said:
Hi, hennimore...
As you're running a Custom ROM, you can pretty much forget about OTA's... as they are only designed to upgrade official stock firmware from Google. If you were to attempt to flash any OTA on your Nexus 7 as it currently stands, it would abort almost immediately during the verification phase of the OTA update process. Because nothing in /system would match what the OTA expects to subsequently 'patch' (update) in the second half of the OTA update process.
Your only option, if you wish to have official stock KitKat installed on your Nexus 7, is to fastboot flash back to factory stock.
For this, you will need the full factory stock image for your Nexus 7, available here.
(Currently, build KOT49H KitKat 4.4.2 is not yet available as a full factory image... just KRT16S KitKat 4.4... but that's not a problem...'cos once you have KitKat 4.4 installed, you can then use an OTA to bring it completely up to date... as detailed in my previous post).
Instructions on how to restore factory stock are available here.
This process is more time consuming than it is technically difficult... because fastboot flashing back to factory stock essentially wipes the device... so before you can begin, you need to backup all of your apps and associated app data with Titanium (requires root), and then backup the entire contents of the Nexus 7's internal storage to your PC... for later restore AFTER you've fastboot flashed KitKat.
Fastboot flashing back to factory stock resets the device, as though it where new. You'll need to set up your WiFi password again... and re-enter your Google Account (gmail) details... and restore all your data from your PC... fastboot flash CWM or TWRP in order to re-root. Once rooted, you can then use Titanium to restore all your apps.
Longwinded and tediously time consuming, it certainly is... but it's the only way to get official KitKat on your Nexus 7 if you're currently running a Custom ROM.
Rgrds,
Ged.
Click to expand...
Click to collapse
Does anyone have any ideas? Thanks!
Hey again, so I was able to get beyond the point where I originally was at a standstill, and now have 4.4 installed on my N7 (Build KRT16S)
So now my question is, do I need to re-root my device, then upgrade to 4.4.2? Or am I currently rooted?
I don't see the option for USB debugging in my settings any longer...
Thanks!!!
I have tried updated ota on my nexus 7 root without unlocking bootloader on 4.3 update and it works fine but you will lost root . Is your nexus root ,unlock bootloader with twrp and stock rom? If thats the case try to update via ota. Ive just manage upgrade to 4.4.2 with ota 10 minutes ago with above situation. I only lost my root not the unlock bootloader. The twrp cwm can handled ota. Thats my advise .
Lets hear advise from others because i also noob in nexus 7
Thanks
Sent from my Nexus 7 using xda premium
hennimore said:
Hey again, so I was able to get beyond the point where I originally was at a standstill, and now have 4.4 installed on my N7 (Build KRT16S)
So now my question is, do I need to re-root my device, then upgrade to 4.4.2? Or am I currently rooted?
I don't see the option for USB debugging in my settings any longer...
Thanks!!!
Click to expand...
Click to collapse
Hi, hennimore...
Sorry it's taken me a while to respond... been busy with family issues (I don't seem to have the time these days that I used to, to focus on Android stuff).
Anyway... taking your questions in order...
hennimore said:
So now my question is, do I need to re-root my device, then upgrade to 4.4.2? Or am I currently rooted?
Click to expand...
Click to collapse
If you've just flashed a clean install of KRT16S, then you certainly won't be rooted. Nor will you have a Custom Recovery installed. You'll be runing 100% totally unmodified stock Android KitKat. The only difference between your Nexus 7 and the average Joe Bloggs' Nexus 7 (who just bought his yesterday)... is your bootloader will be unlocked.
With regard to applying the new update... KOT49H
Well, there are three routes you could go down...
1). Await for the OTA to appear normally in the notification bar, or go to SETTINGS>>ABOUT TABLET > > SYSTEM UPDATES... and tap on the 'check now' button. When the update appears (and sooner or later it will), it will be flashed automatically via stock recovery. This of course, is the standard method by which 99.9% of all Android users get their updates.
2). If you don't fancy waiting, fastboot flash a Custom Recovery, like TWRP or CWM, and then download the KOT49H OTA .zip directly to your Nexus 7. Boot into your Custom Recovery of choice (via the bootloader), and flash it manually.
3). If you haven't done much with your Nexus 7 (ie, installed lots of apps and copied lots of stuff over), since you flashed the full factory image of KRT16S, and you don't mind repeating the process... then the full factory image for KOT49H has now been uploaded by Google, and is available here. Download and flash it the way you did KRT16S. It goes without saying, that this will reset and wipe your device again.
*****
Addendum: It seems that Google have made a bit a mess (of some) of the KitKat 4.4.2 factory stock image download links... and when clicked upon, will give a 404 error message.
The corrected download links can be found here...
http://forum.xda-developers.com/showthread.php?t=2565531
*****
Whichever of these methods you use to upgrade to KOT49H from KRT16S... you'll need to fastboot flash a Custom Recovery afterwards if you wish to re-root.
With regard to USB debugging...
hennimore said:
I don't see the option for USB debugging in my settings any longer...
Click to expand...
Click to collapse
You won't... this is because Developer Options are hidden by default... presumably to prevent non-technically minded people from screwing things up.
To enable developer options (and by extension, USB debugging), go to SETTINGS>>ABOUT TABLET>>scroll down to BUILD NUMBER... on BUILD NUMBER, tap 7 times. You will see a 'toast' message that says something like "Congratulations, you are now a developer!". (If only it where that easy, eh).
Anyway, with Developer Options now enabled (which you should now find in SETTINGS), USB debugging can now be turned on.
Incidently, I've just seen a new option in Developer Options, called Process Stats - Geeky stats about running processes. I'm pretty sure this is new to KitKat, as I've never seen it before. Anyway, tapping on it does indeed yield some stats... which are interesting... Google however, consider them geeky. The implication being that anybody interested in such things is a geek. I just found it humorous, the use of the word geek by Google.
Humorous allusions aside about whether everybody on XDA is actually a geek...or not... I hope this helps.
Rgrds,
Ged.
Just wanted to say how grateful we are for having you gedblake here in n7 forum while this thread doesn't apply to me I still read it and was pleased to see the well written well explained replies.
Don't mean to hijack this thread or for it come over as all gushy etc but than you.:thumbup::beer:
Sent from my C5303 using xda premium
Meshe said:
Hi guys,
I've been having problems to update to 4.4 in the Nexus 7 wifi version, the only thing I done is unlock the bootloader and root, once I tried the OTA upgrade it starts the process and then it shows up the Android little guy with an error, and doesn't shows the error of installation. I tried once the flashing the zip file using TWRP and it just failed. After the first failed the tablet just started to lag horribly. Any suggestions on how to fix this?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hey Ged, do you know any about my issues or suggestions? The 4.4.2 ota upgrade showed up and it too failed to upgrade from 4.3
Sent from my LT26ii using xda app-developers app
Meshe said:
Hi guys,
I've been having problems to update to 4.4 in the Nexus 7 wifi version, the only thing I done is unlock the bootloader and root, once I tried the OTA upgrade it starts the process and then it shows up the Android little guy with an error, and doesn't shows the error of installation. I tried once the flashing the zip file using TWRP and it just failed. After the first failed the tablet just started to lag horribly. Any suggestions on how to fix this?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Meshe said:
Hey Ged, do you know any about my issues or suggestions? The 4.4.2 ota upgrade showed up and it too failed to upgrade from 4.3
Sent from my LT26ii using xda app-developers app
Click to expand...
Click to collapse
It could be a TWRP problem...
Hi, Meshe...
You don't state which version of TWRP you're using, and what (if any) errors where displayed when the OTA aborted. If, as you say, you have performed no significant modifications to your Nexus 7, other than unlocking the bootloader and flashing TWRP (and rooted it)... then the 4.4.2 OTA should flash...
...however, there seems to be something odd about the behaviour of TWRP v2.6.3.1.
To elaborate... there is a known problem using TWRP 2.6.3.1 when flashing franco's latest kernel. See here for details on this.
This problem seems to relate to TWRP v2.6.3.1 itself, and not to franco's kernel .zip. The kernel flashes without problems using an earlier version of TWRP, namely v2.6.3.0 and also with the latest CWM recovery...
Nobody seems to know why TWRP v2.6.3.1 fails to flash franco r76, but fail it does. It appears that something is 'broken' in TWRP v2.6.3.1.
So I'm suspecting that your difficulties flashing the KitKat OTA might be similarly related to whatever is broken in TWRP v2.6.3.1... assuming of course, that this is the version you're currently running.
-------------------------------------------------
Here's what I would do... flash either TWRP v2.6.3.0 (the previous version) or CWM v6.0.4.3 (links below), and try flashing the KitKat OTA again. (I used CWM when applying the KitKat 4.4.2 OTA and it flashed without problems).
TWRP Recoveries...
http://techerrata.com/browse/twrp2/grouper
http://techerrata.com/browse/twrp2/tilapia
ClockWorkMod Recoveries...
http://www.clockworkmod.com/rommanager
(It's important you get the correct version of CWM recovery for your Nexus 7, as there are four CWM recoveries listed for the Nexus 7; two for the first generation model, and two for the second generation model.)
You'd normally fastboot flash a custom recovery, but if you're already rooted, you can flash a custom recovery directly from the Nexus 7 itself, without going anywhere near a PC... by using the rather excellent flashify app.
To summarize...
1). Install flashify on the Nexus 7.
2). Download to your Nexus 7 any custom recovery other than TWRP v2.6.3.1.
3). Ensure the KitKat 4.4.2 OTA update .zip is located somewhere on the Nexus 7.
-----
4). Use flashify to flash the custom recovery (It will request root privileges).
5). Boot (via the bootloader) into your custom recovery.
6). Using that custom recovery, flash the OTA... again.
Finally, if the above doesn't work, and the OTA aborts again, write down any error messages that are displayed. They can sometimes prove invaluable in diagnosing the problem, in order to decide what the next step is to take. Whenever I embark upon some project, for which taking screenshots isn't an option, I always keep my camera handy, such that I can take photographs of the screen... affording me a complete photographic record of the process, errors included, that I can review later. Very useful when things go wrong... as sometimes they do.
Hope this helps... and good luck.
Rgrds,
Ged.
zolaisugly said:
Just wanted to say how grateful we are for having you gedblake here in n7 forum while this thread doesn't apply to me I still read it and was pleased to see the well written well explained replies.
Don't mean to hijack this thread or for it come over as all gushy etc but than you.:thumbup::beer:
Sent from my C5303 using xda premium
Click to expand...
Click to collapse
Wow, erm, I mean yes... thanks... @zolaisugly... not quite how to respond to that.(blushing/embarrassed).
But thank you for your kind words, they're hugely appreciated.
I just try to help as best I can... 'cos I know what it feels like when you think you're 'bricked' or otherwise have problems with your device, as I had last year, with my (the then new) Nexus 7....and it's a uniquely horrible feeling.
You can read about my fumbling efforts here.
But it was posts here on XDA that got me back on track... and got my Nexus 7 working again.
So now, I try to give something back to XDA... my way of saying thanks I guess... and always I remember the stress I went through back in November of last year with my Nexus 7... so I can empathise with those who might not be so knowledgeable, or confident, or sure of their own capabilities, as some of the more experienced XDA veterans. And I try to help... when and where I can. Nobody can know everything... and everybody begins somewhere.
--------------------------------------
To all...
The primary rule I've learned in this past year, is if you think you've bricked your Nexus 7, or have some other seemingly intractable problem, is...
--- DON'T PANIC ---
Panic is an emotional response, and is the enemy of logical, rational thought.
It clouds good judgement... and may lead you to make BAD DECISIONS. Which will likely lead you to make a BAD SITUATION... WORSE.
Don't make any rash, uninformed decisions. It's understandable you want to get your Nexus 7 working again... but do some research first. Review your options. Read... and understand what you're doing... before you do it.
Carpenters and people who work with wood, have an old saying...
~ "Measure twice, cut once." ~
This axiom, I feel, is just as true and applicable to technology as it is to making chairs, tables and putting up a set of shelves.
Use XDA... If you've got a given problem, chances are good, somebody has had it before you, or has it now. A solution may already have been posted.
Use the XDA search engine... or go to Google search, and type "XDA ..." followed by some keywords that distill the essence of your problem.
I've never known Google search to NOT display something that might be pertinent to an Android problem... and usually it's almost always XDA that comes at the top of the Google search results.
--------------------------------------
Right... I'll shut 'up now.. I've waffled on far too long. And I don't want to earn the ire of the moderators for taking this thread wildly off topic.
Rgrds,
Ged.
GedBlake said:
Wow, erm, I mean yes... thanks... @zolaisugly... not quite how to respond to that.(blushing/embarrassed).
But thank you for your kind words, they're hugely appreciated.
I just try to help as best I can... 'cos I know what it feels like when you think you're 'bricked' or otherwise have problems with your device, as I had last year, with my (the then new) Nexus 7....and it's a uniquely horrible feeling.
.
Click to expand...
Click to collapse
OK well if you don't mind I'd like to pick your brain too . I am without a doubt no stranger to Android, rooting, custom roms, and so on, however this is my first experience with the nexus 7 (or with tablets in general for that matter), so there's just a couple of things I'd like to clarify if possible. I recently got a great deal on a 2012 32gb Nexus 7 WiFi, but I guess one reason why it was a great deal is because it came with 4.1.2 lol. So I have successfully unlocked the bootloader, rooted it, and flashed cwm recovery to it using wugs toolkit (what a great tool by the way!), and I originally assumed from this point on that I'd just be flashing custom roms like normal. After reading around for awhile I guess I must've confused myself, because now I'm not really sure what the "best" route to take would be anymore. First of all would I really need to flash every ota and build all the way up to 4.4.2 like described earlier? I found another thread that shows how to extract the boot, system, and bootloader images from the 4.4.2 ota off of Googles site, and then you could use wugs toolkit to flash them without losing data, would that work though considering I'm only on 4.1.2? Or should I just do all of the ota updates that pop up until I'm up to 4.4.2? I guess what I'm asking is what would be the best and or easiest way to get from 4.1.2 all the way to 4.4.2? I'm not concerned about losing data whatsoever just to clarify because I just got this so I haven't done hardly anything with it yet. I'm just under the impression that I can't even flash a 4.4 custom rom considering how old the version is on this, but I'm not sure if that's even correct or not.Anyway I'd really appreciate any insight or suggestions you might have because the last thing I want to do is rush into something and cause twice the work for no reason lol.
jeep447 said:
OK well if you don't mind I'd like to pick your brain too . I am without a doubt no stranger to Android, rooting, custom roms, and so on, however this is my first experience with the nexus 7 (or with tablets in general for that matter), so there's just a couple of things I'd like to clarify if possible. I recently got a great deal on a 2012 32gb Nexus 7 WiFi, but I guess one reason why it was a great deal is because it came with 4.1.2 lol. So I have successfully unlocked the bootloader, rooted it, and flashed cwm recovery to it using wugs toolkit (what a great tool by the way!), and I originally assumed from this point on that I'd just be flashing custom roms like normal. After reading around for awhile I guess I must've confused myself, because now I'm not really sure what the "best" route to take would be anymore. First of all would I really need to flash every ota and build all the way up to 4.4.2 like described earlier? I found another thread that shows how to extract the boot, system, and bootloader images from the 4.4.2 ota off of Googles site, and then you could use wugs toolkit to flash them without losing data, would that work though considering I'm only on 4.1.2? Or should I just do all of the ota updates that pop up until I'm up to 4.4.2? I guess what I'm asking is what would be the best and or easiest way to get from 4.1.2 all the way to 4.4.2? I'm not concerned about losing data whatsoever just to clarify because I just got this so I haven't done hardly anything with it yet. I'm just under the impression that I can't even flash a 4.4 custom rom considering how old the version is on this, but I'm not sure if that's even correct or not.Anyway I'd really appreciate any insight or suggestions you might have because the last thing I want to do is rush into something and cause twice the work for no reason lol.
Click to expand...
Click to collapse
Hi, jeep447...
You're quite welcome to 'pick my brain', as you put it... but don't be too surprised if all you find in there is an oily rag, a half eaten sandwich and a dead D cell battery.
I'm by no means an Android expert; there are far more knowledgeable posters here on XDA... and they appear to be in possession of secret arcane Android knowledge, that is beyond my understanding.
However, I will try to help insofar as my knowledge allows. On to your question(s)...
First things first... if you're currently running Jellybean 4.1.2 on the device, then I think it would be a good idea to bring it up to date to KitKat 4.4.2 first... before you start flashing Custom ROMs.
Theoretically, it shouldn't make any difference if you where to flash a Custom ROM now, without bringing it up to date. But there might be an issue with the bootloader...
...which Custom ROMs WILL NOT update.
The bootloader can only (as far as I know) be updated by either...
-------------------------------------------------------
a) Allowing an Android update via the normal update route (or manually flashing the OTA yourself in recovery).
...or...
b) Fastboot flashing the full factory image that contains the new bootloader.
-- (however, see my Addendum toward the end of this post).
-------------------------------------------------------
I am not aware of any Custom ROMs that go anywhere near the bootloader partition. Which is probably a good thing actually, since a bad or incorrect bootloader flash has the potential for HARDBRICKING the Nexus 7.
My recollection is a little hazy... but I think with Jellybean 4.1.2, the bootloader was at version v4.13... since then, there have been two bootloader updates, v4.18, and the current version, which stands at v4.23.
You can check which bootloader you're currently on by booting into the bootloader as follows... shutdown the Nexus 7 completely. Press and hold the VOL DOWN button, whilst holding, press the POWER ON button. The Nexus 7 should now boot into the bootloader. On the lower left hand side of the screen, in a tiny font, you should find (amongst other things), the bootloader version number.
Now all of this detail about bootloaders might not matter... you could happily flash some new Custom ROM... and it might work without any problems with an old bootloader... but, on the hand, it might not.
So, I think, before you try tinkering around in the Custom ROM area... and If I where you, I would bring the Nexus 7 completely up to date, running Android 4.4.2 build KOTH49H (and the latest bootloader... v4.23).
The easiest and arguably the safest way of doing this, is to just allow the OTA updates normally, as and when they appear in the notification bar. Or, alternatively go to SETTINGS>>SYSTEM UPDATES > > and tap the CHECK NOW button. This is the method by which 99.9% of all Android users get their updates...
...and which is how I initially updated mine...in November of last year, when I first got my Nexus 7.
Running Jellybean 4.1, straight out of the box, once I connected it to mains power (updates won't occur if your battery is below a certain percentage), and acquired a WiFi signal... my Nexus 7 went through 3 or 4 reboots, upgrading from Jellybean 4.1 to Jellybean 4.1.1 to Jellybean 4.1.2 to Jellybean 4.2 (which introduced the world to Googles new and improved 11 month calender!). In December, Jellybean 4.2.1 was released, in time for Santa to arrive, which restored the missing month, December, in the date-picker.
Your succession of updates will be noticeably longer, as since then, we've had Jellybean 4.2.2, Jellybean 4.3, KitKat 4.4, and finally KitKat 4.4.2.
Along the way, with these updates, your bootloader will also be updated, silently and without you being notified of the fact. Most Nexus 7 owners are probably not even aware of the bootloader, much less if the latest OTA has updated theirs. So, the bootloader is not something you would need to normally flash directly yourself.
Of course there's nothing to stop you applying the OTA updates manually yourself, as I've written about here.
However you 'take' the updates, OTA's won't cause you to loose data... all your apps will still be there, as will your pics, videos and music files.
One last point concerning OTA updates... whether applied normally, or flashed manually... you will loose your Custom Recovery (in your case CWM)... and if you're rooted, you'll loose that as well... but it's easy enough to get both back after the update.
-------------------------------------------------------
Once your Nexus 7 is completely up to date, running KitKat 4.4.2, and before you do anything else, I recommend you make a Nandroid backup. I find it vaguely astonishing that so many people seem to miss this (IMHO) critical step.
Once you have a Nandroid backup under your belt... you can pretty much flash any Custom ROM or Kernel, safe in the knowledge that should anything go wrong with the flash, you can restore back to the point you where at before you flashed that ROM/Kernel or other 'mod'.
In fact, I don't think it would be a bad idea for you to create one now... whilst still running Jellybean 4.1.2... using your recently installed version of CWM.
Nandroid backups, whether created with CWM or TWRP, are a bit like 'restore points' in Windows... and I just think it's good practice and common sense, to have at least one good Nandroid backup stored on the device... before you start flashing stuff.
-------------------------------------------------------
Right... I think that covers most of your questions.
I'll try to keep an eye on this thread... in case you have any followup questions.
But I'm going to be pretty busy over the next week or so, what with Christmas on the horizon... so I may not respond immediately.
Good luck with your new Nexus 7... and, as ever... I hope this helps.
**********
Addendum
I've spoken at length about bootloaders and OTA updates. And I think this is your best and least risky way of bringing your Nexus 7 up to date.
Whist there is now available a full factory image for KitKat 4.4.2 build KOTH49 (see my sig for download links), I would avoid it at this time.
Apart from the fact it will completely wipe you're Nexus 7 (which is normal and to be expected) ... the STOCK FACTORY IMAGES, and the bootloaders that ship with them are currently in a bit of a mess. .. and may cause HARDBRICK.
See this thread for further details on this...
[WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google.
There are ways of working around this; (you need the bootloader from Build JWR66V)...
...but I suggest you stick with OTA's for now, to bring your device up to date...
Or at least until either Google sort out the 'dogs breakfast/pigs ear' they've made of the factory images... or until you've acquired sufficient knowledge and confidence in modifying a FACTORY STOCK image, such that it fastboot flashes a known GOOD BOOTLOADER.
Rgrds,
Ged.""
Hi.
So, a quick overview. My laptop suddenly stopped recognizing my Nexus 10 while in the midst of transferring some files over. I decided to finally root. I used the cf-autoroot tool for Nexus 10 Lollipop. The last step of the rooting involves an automatic reboot. Now my Nexus 10 is stuck in the boot.
Details:
theunlockr (DOT) com/2014/11/22/how-to-root-the-nexus-10-on-android-5-0/
That is the guide I used, including the linked cf-autoroot. Sorry for the formatting, I don't have enough posts to post links.
My Nexus 10 is stuck on the step where it shows the four circles moving around. Not sure if that's important.
The cf-autoroot appeared to work successfully except for a piece in the middle that reads:
Same problem. The procedure seemed to go well, except maybe the mounting failed? It says:
Mounting...
- System
- Cache
--- Fail
I tried using the tool several times on two computers, and did my best to update drivers directly from Google (it appears the drivers are all up to date).
My Nexus 10 was on Lollipop. As far as I know, it was up to date, so I think that means it was on 5.0.1
Help?
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Khaon said:
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
jsgraphicart said:
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
Click to expand...
Click to collapse
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
Thanks. I just wanted to double check before I went jumping into it. I'm looking forward to tinkering with it when I get home from work.
Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
So I attempted to do all this when I got home yesterday. I found that after unlocking the bootloader, I got stuck in a boot loop. After doing some research I found that this has been an issue with the Nexus 10. Is there a reason for this? I read that locking the bootloader again fixed it, which it did. But I didn't want it locked. So I researched more and found that a a factory reset in stock recovery would fix it. I still had a boot loop. I managed to somehow get everything straightened out with a series of random tries and after installing TWRP and rooting and, again, getting the boot loop I attempted to go back into recovery but accidentally did a simple restart. For some reason, it booted right up after the restart so now I think everything is fine. But why is the Nexus 10 being so difficult? I never had these issues with other Nexus devices. Maybe some of this info will help the OP as well.
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Khaon said:
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Click to expand...
Click to collapse
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
nexus 10 stuck on bootload up
jsgraphicart said:
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
Click to expand...
Click to collapse
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
tomistrouble said:
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
Click to expand...
Click to collapse
Once you get in recovery mode with the android and the red explanation mark, hit all three buttons (Vol up , down and power) until (It can be tricky keep trying) you get a menu. Then use the volume buttons to select "Wipe Data/Factory rest" let it do its thing and reboot. Allow it to boot for 5-10 minutes.
Good luck
I tried to use Yemenroot to root my phone and ended up stuck in a Boot recovery and no matter what I try I cant get out of it. What suggestions could anyone give me? Ive tried the factory reset option and the clear cache. neither helped. Thanks in advance!
Not sure exactly what you mean by "stuck".
Are you saying that every time it reboots it boots into the recovery?
If so, then:
- Pull the battery
- Reinsert the battery*
- Boot the phone by holding down Vol-Down+Home+Power*
When it asks you if you want to go into Download Mode, select Cancel (Vol-Down iirc)
The phone should boot into the regular ROM, albeit completely unconfigured, as you have already performed a factory reset (which wasn't needed btw).
If the Stock ROM won't boot you will have to flash the Stock ROM in Odin
*don't have the phone plugged in to a PC at this point or it will spontaneously reboot.
bftb0 said:
Not sure exactly what you mean by "stuck".
Are you saying that every time it reboots it boots into the recovery?
If so, then:
- Pull the battery
- Reinsert the battery*
- Boot the phone by holding down Vol-Down+Home+Power*
When it asks you if you want to go into Download Mode, select Cancel (Vol-Down iirc)
The phone should boot into the regular ROM, albeit completely unconfigured, as you have already performed a factory reset (which wasn't needed btw).
If the Stock ROM won't boot you will have to flash the Stock ROM in Odin
*don't have the phone plugged in to a PC at this point or it will spontaneously reboot.
Click to expand...
Click to collapse
Thanks for responding! Yes you are correct that it boots in recovery. Home+Power+Vol Down brings me up to a Warning screen, says if i want to download a custom OS to hit vol up, if I want to cancel press Vol Down. I press vol down and it puts me back into recovery boot again.
If you are familiar with YemenRoot maybe I just screwed up doing that and can still continue with that to fix it? I ran the program, choose Tar.1 in Oden and hit start. Went back to the command prompt and "pressed any key" to continue. It went to 2). Rooting, but never went any farther. The phone automatically rebooted but into recovery mode. That was where I thought something went wrong and stopped.
EDIT: I went back again and pressed vol up to see where it would take me. It takes me back to the downloading screen like it showed in one of the steps for the root. I ran tar.1 and tar.2 and was able to get the phone usable again. No luck with the YemenRoot though Tried going through to do it a second time and came up with the same issues. It just sits on (2) Installing root forever and the phone eventually reboots into Recovery again. Im not sure how to get Yemen to work correctly, and no one seems to respond in the yemenroot post that I found on here.
trizzypballr said:
Home+Power+Vol Down brings me up to a Warning screen, says if i want to download a custom OS to hit vol up, if I want to cancel press Vol Down. I press vol down and it puts me back into recovery boot again.
Click to expand...
Click to collapse
Well that's a little odd & unexpected.
[Edit] - Oops, I didn't initially see the part about you getting it working [Edit]
I can't help you out with Yemenroot, I've never used it. (But I suspect the stock ROM needs to be booting in order for it to work, so you are going to have to do the Odin Flash no matter what)
I can suggest that if you are going to keep trying w/ yemenroot, I would only minimally configure the (factory reset) stock ROM in case you end up back in the same spot again.
PS if you know how to create Odin .tar.md5 files, you could create a "reduced" stock flash for Odin containing only boot.img & system.img. That way you could "dirty flash" those two in Odin if you got in the same situation again... without needing to do a factory reset.
good luck
I flashed using odin N900VVRUEOF1_N900VVZWEOF1_VZW. It took the flash but is now stuck on RED Verizon screen. Ity is like it is doing something but not fully recovered?? Any suggestions?
bftb0 said:
I can't help you out with Yemenroot, I've never used it.
Click to expand...
Click to collapse
Then how in the world did you root your phone? I thought those were the only ways to get your device rooted?
RaaidR said:
Then how in the world did you root your phone? I thought those were the only ways to get your device rooted?
Click to expand...
Click to collapse
I used Kingo root when my phone was on MJ7 and I never upgraded thereafter.
Even now my phone is only on the MJE bootloader (it can be rolled back to MJ7).
The version of TowelRoot that I have (v3?) currently seems to work on all stock versions from MI9-NC4, but it wasn't yet released when I rooted.
I'm not planning on upgrading my bootloader past NC2 until such a time as I am going to sell the phone, or there is a way to upgrade only the bootloader components while preserving root in the ROM.* My motivation for that is quite frankly to avoid using the yemen root tool.
*So that the bootloader unlock can be performed immediately thereafter, to regain bootability of a custom recovery. IMO this should be trivial so long as OB6/OF1 bootloader will boot a rooted-stock kernel+ROM from 4.4.x (NC4, NJ6, NK1). Frankly I believe that to be more likely than a 4.4.x bootloader booting a 4.3.x rooted-stock kernel+ROM (MI9/MJ7/MJE).
bftb0 said:
I used Kingo root when my phone was on MJ7 and I never upgraded thereafter.
Even now my phone is only on the MJE bootloader (it can be rolled back to MJ7).
The version of TowelRoot that I have (v3?) currently seems to work on all stock versions from MI9-NC4, but it wasn't yet released when I rooted.
I'm not planning on upgrading my bootloader past NC2 until such a time as I am going to sell the phone, or there is a way to upgrade only the bootloader components while preserving root in the ROM.* My motivation for that is quite frankly to avoid using the yemen root tool.
*So that the bootloader unlock can be performed immediately thereafter, to regain bootability of a custom recovery. IMO this should be trivial so long as OB6/OF1 bootloader will boot a rooted-stock kernel+ROM from 4.4.x (NC4, NJ6, NK1). Frankly I believe that to be more likely than a 4.4.x bootloader booting a 4.3.x rooted-stock kernel+ROM (MI9/MJ7/MJE).
Click to expand...
Click to collapse
Why do you not want to use the yemen tool? The one for Windows 10 worked flawlessly for me.
RaaidR said:
Why do you not want to use the yemen tool? The one for Windows 10 worked flawlessly for me.
Click to expand...
Click to collapse
The ends don't justify the means.
No disclosure of method.
No prior or subsequent author activity on XDA
Use of a PC
No Windows 10 box that I am willing to expose to random executables from unknown authors on the internet.
bftb0 said:
The ends don't justify the means.
No disclosure of method.
No prior or subsequent author activity on XDA
Use of a PC
No Windows 10 box that I am willing to expose to random executables from unknown authors on the internet.
Click to expand...
Click to collapse
I for sure understand not wanting to risk it. I really didn't either but didn't have another choice other than to stay unrooted.
DjRenigade said:
I flashed using odin N900VVRUEOF1_N900VVZWEOF1_VZW. It took the flash but is now stuck on RED Verizon screen. Ity is like it is doing something but not fully recovered?? Any suggestions?
Click to expand...
Click to collapse
Use Jasmine ROM 6.1, it is based on OF1 and works fine.
Sent from my SM-N900V using Tapatalk