• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root How do I install Android 4.4 on a rooted Nexus 10 Using Android 4.2.2....

S

Sithtiger

Newbie
Hi, I currently have a Nexus 10 that is already rooted to Android 4.2.2 using a TRWP custom ROM. Now I want to upgrade to Android 4.4. I don't have the info I used to root it to 4.2.2 and installed the custom ROM. I need a detailed instruction list so I don't brick this puppy. I went here to try to do it: Root Nexus 10 on Android 4.4 KRT16S KitKat and Install CWM/TWRP Recovery [How to] - IBTimes UK , but when I tried to run the fastboot recovery, I received an error stating that fastboot wasn't an external program or command or something on those lines. So I decided to stop and ask for help before I brick it.

I don't have to use TRWP again for the custom ROM, just something that works and is liked. I just need to download Android 4.4 and install it and a new ROM if that's what's needed. Thanks in advance!
 
You need to download the Android SDK then copy all your files to [Unzipped directory]/sdk/platform-tools, then run the commands from there. You'll need the N10's LATEST CWM/TWRP recovery.

Shameless self plug- use my ROM! >_>
 
Thanks. I have those things already. So what do I do once I have those files? See I ran those files and got some weird error for fastboot stating it wasn't a command to run that way.
 
Were you in the same directory as fastboot in your command prompt /terminal? You shouldn't be getting that error. What Operating System are you using?
 
Windows 7 x64. Isn't this the command you use? fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img

Of course the image file name changes if it's a different image file, but it starts with the command fastboot flash recovery.....right?
 
Question. Do I need to root it again if I already rooted it with Android 4.2.2.? I did that, but I didn't update to Android 4.3, but I am doing 4.4.
 
You'll have to root again, yes, if you're using the factory images.

That IS the command... Did you "cd" to the directory with the Fastboot executable?
 
I would suggest to use Wugg's Nexus Root Toolkit, makes the process really easy and such.

Just make sure to flash the newest version of CWM or TWRP, like dibble said, otherwise you won't be able to flash any 4.4 ROMs over to your device.
 
It sounds like you aren't running the terminal commands from the same location as your fastboot tools

An easy trick for windows 7 is to shift+right click in the folder containing fastboot and your recovery, and then in the drop down menu select "open command window here"

Edit: DC ninjas me :D Wugs toolkit is another good option.
 
a.) please run fastboot devices command to verify connectivity and paste the output.
b.) please take a screenshot of any errors incurred after positively running fastboot devices yet still having problems/errors.

With those two bridges crossed, and dealing with a Nexus, I guarantee we can point you in the right direction. We just need to know all the issues you are facing to sort this.
 
iowabowtech said:
a.) please run fastboot devices command to verify connectivity and paste the output.
b.) please take a screenshot of any errors incurred after positively running fastboot devices yet still having problems/errors.

With those two bridges crossed, and dealing with a Nexus, I guarantee we can point you in the right direction. We just need to know all the issues you are facing to sort this.
Click to expand...

Thanks guys. OK, here's where I'm at now. I was able to update it manually using adb sideload to 4.3. Since that worked, I'd figure I'd try to install 4.4 the same way, right. Well, it didn't work, but when it rebooted I noticed that it still wanted me to download 4.3 even though I already had it. I checked it and it was running 4.3 for sure. Anyway I decided to go ahead with the update it wanted to use and I did and it updated just fine. So I saw it wanted to update to 4.4 like it did with 4.3. So that's awesome, but it did the same thing the others did when I tried to update manually and though it varies a bit, this is what it said earlier. I wasn't able to capture the error when it was doing it automatically since it didn't give me time to take a screen shot, it just rebooted. This is from earlier, but I'm pretty sure it said the same thing I believe.

Restarting adbd...
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of goodle/mantary/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT16S/920375:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys.
E:Error in /tmp/update.zip
(status 7)
Installation aborted
 
Rxpert83 said:
It sounds like you aren't running the terminal commands from the same location as your fastboot tools

An easy trick for windows 7 is to shift+right click in the folder containing fastboot and your recovery, and then in the drop down menu select "open command window here"

Edit: DC ninjas me :D Wugs toolkit is another good option.
Click to expand...

Yeah, I figured that out as well. I couldn't believe I was in the wrong directory, but I get this error no matter how I try to update to 4.4.

Restarting adbd...
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of goodle/mantary/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT16S/920375:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys.
E:Error in /tmp/update.zip
(status 7)
Installation aborted
 
Digital Controller said:
I would suggest to use Wugg's Nexus Root Toolkit, makes the process really easy and such.

Just make sure to flash the newest version of CWM or TWRP, like dibble said, otherwise you won't be able to flash any 4.4 ROMs over to your device.
Click to expand...

I should have done a multi quote reply....sorry guys. I'm going in reverse in reply to these posts. So you can read what I put down in posts before this one, but I did download Wugg's Nexus Root Toolkit.

**EDIT**

Looks like when I did the OTC update that updated automatically to 4.3, it unrooted my device. I'll have to root it again.
 
OK, here's another update. Turns out when I did the update from Google, it did indeed unrooted my device, so I had to go back and root it. This time I used Nexus Root Toolkit from WugFresh. That worked just fine. After that I decided to try to update to 4.4 using this filename: 279e5e2396480cbffd97943a5db5bbc743ef7e77.signed-mantaray-KRT16O-from-JWR66Y.279e5e23.zip. I tried to update using adb sideload again and then I got this new error.

Installing update...
Verifying current system...
"EMMC: /dev/block/platform/dw_mmc.0/by-name/boot:4753408:1adedb8161f94667a9ccec68f290b921ea287736:489678:cbbf1d5f269c49b72b6cf43315767da32f733a63" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.

I mean what the heck? I'm starting to think the only way I'm going to get 4.4 on is to wipe the whole thing and start from scratch, but I don't want to do that unless absolutely necessary. Just gonna wait for you guys now....sigh.

I know this isn't that hard to do, but for some reason something is wrong, now that I figured out I was in the wrong directory. I'm not a n00b with tech and especially computers, but I am with Android devices.
 
Sorry for the length, but I've really been trying here.

OK, I think the problem is that the updates that I've downloaded don't think my device is a Manta device, and it is of course. I've looked at sites that have told me to remove the line starting with “assert” to next semi-colon in updater-script that is located in the META-INF/com/google/android directory in the zip file. Well I don't see the 'assert' line anywhere but I did see this in the updater-script:

"mount("ext4", "EMMC", "/dev/block/platform/dw_mmc.0/by-name/system", "/system");
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/mantaray/manta:4.4/KRT16O/907817:user/release-keys" ||
abort("Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT16O/907817:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
getprop("ro.product.device") == "manta" || abort("This package is for \"manta\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Verifying current system...");
show_progress(0.100000, 0);
apply_patch_check("/system/app/BasicDreams.apk","

This is just a small portion of the updater-script file, but then take a look at the error I get.
Installing update...
Verifying current system...
"EMMC: /dev/block/platform/dw_mmc.0/by-name/boot:4753408:1adedb8161f94667a9ccec68f290b921ea287736:489678:cbbf1d5f269c49b72b6cf43315767da32f733a63" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.

Notice the same line that is in the updater-script? I know this has something to do with it. This site here says you can either change recovery ROM's from Clockwork mod (which I had) to TWRP. I did that and still got the error, but there's got to be something else about this, otherwise this wouldn't be in the error. This site talks about how to get rid of status 7 errors, which is what I was getting. I don't actually see status 7 error since I switched back to TWRP, but I believe it's the same error. How To Fix Status 7 Error with CWM Recovery on Rooted Android! | HighOnAndroid.com

Is there a way I can install Android 4.4 from Googe's site? The thing is, it's a tgz file and that won't work in Windows. You can access it, but at least I can't update it through adb. Can anyone help me install the factor file from Google? BTW, my last error said: E:Error executing updater binary in zip '/data/media/0/sideload.zip'

EDIT

OK, last update tonight and I'll get back to it tomorrow so you guys can give me some input. I tried inputting a tgz file via sideload and it uploaded, but when it went to update, it said it was corrupted....sigh. Nite, or morning rather for me...later. I hope you guys can help me here. I've been trying for 3 days straight now, going on 4th tomorrow.
 
Does wug's toolkit have the option for flashing the factory 4.4 image for the n10? If so, that will probably be the easiest way. If it does not, then use the toolkit to flash the factory 4.3 image and then update with the OTA (over the air) update. (Settings>about tablet>system updates)
 
Lordvincent 90 said:
Does wug's toolkit have the option for flashing the factory 4.4 image for the n10? If so, that will probably be the easiest way. If it does not, then use the toolkit to flash the factory 4.3 image and then update with the OTA (over the air) update. (Settings>about tablet>system updates)
Click to expand...


It doesn't say what version it will flash back to. It just says flash stock + unroot. I'm afraid that will flash it back to 4.2.2. That's where I came from. Also, I did let me Nexus do the OTA update to 4.3 and in the process unrooted it. While it was unrooted, the 4.4 OTA update came up and I let it update and it came up with the same status 7 error, which from what I've seen says my Nexus 10 isn't made for this update, which it is of course since it's from Google.

Thank's, that's a good idea but that might wipe my system, but I'm thinking that may be the only way to go now. I backed up my apps using Titanium backup after I rooted it again and sent it to Google Drive. I think I'm just gonna wipe it and try it from there.
 
Sithtiger said:
It doesn't say what version it will flash back to. It just says flash stock + unroot. I'm afraid that will flash it back to 4.2.2. That's where I came from. Also, I did let me Nexus do the OTA update to 4.3 and in the process unrooted it. While it was unrooted, the 4.4 OTA update came up and I let it update and it came up with the same status 7 error, which from what I've seen says my Nexus 10 isn't made for this update, which it is of course since it's from Google.

Thank's, that's a good idea but that might wipe my system, but I'm thinking that may be the only way to go now. I backed up my apps using Titanium backup after I rooted it again and sent it to Google Drive. I think I'm just gonna wipe it and try it from there.
Click to expand...

Worst case scenario you'll lose data and will take 2 official ota's
 
iowabowtech said:
I use fastboot and then extract the images out of the official stock file whenever changing my OS on a Nexus. As outlined here:

http://androidforums.com/android-sy...nexus-factory-image-manually.html#post5702530
Click to expand...

Thanks iowabowtech, it worked!!! This scared the crap out of because as I was doing the steps, I noticed that I just erased the recovery and boot. I looked it over before, but it didn't really sink it. I had never used fastboot before and when I went to reinstall the bootloader and recovery after step 9, I received and error stating that it couldn't read the image. I tried it again with a different image....no dice. So I stayed calm as this tiny knot in my stomach started to grow with the realization that I most likely bricked my tablet and I don't have the money to get a new one. I was just out of luck. Then I kept going and then followed the directions where it says if you don't want to try flashing the individual images by themselves, you can try that and so I did. It worked! My problem was I didn't insert the boot command twice. I was using fastboot flash boot.img, instead of fastboot flash boot boot.img.

I have a question. What would have happened had I turned off my tablet after I erased everything including the bootloader and recovery? Is there a way to recover your system then, or do you just have an expensive paperweight?

Well, now that I know this trick, I'll use it if I have another problem updating. I just want to thank everyone for their help!
 
Sithtiger said:
I have a question. What would have happened had I turned off my tablet after I erased everything including the bootloader and recovery? Is there a way to recover your system then, or do you just have an expensive paperweight?
Click to expand...

I generally don't use the erase command. I just flash the components over top of one another via the flash command. Also, I usually don't flash the individual partitions (boot/system/cache/etc) but instead I just run the -w update zip command the OP referenced.

Anyway, I think you'd still be ok because you're erasing "boot" which is not the same as erasing the bootloader. As long as you have a working bootloader on a Nexus, you should be good to go.
 
I'd suggest staying away from erase commands as well.

An accidental boot loader erase is a ticket to brickville
 
You must log in or register to reply here.
Back
Top Bottom