Related
I have a problem with mounting my phone in Windows (see here; http://forum.xda-developers.com/showthread.php?t=841645) and I need to return it for testing.
How can I flash it back to stock without a USB connection?
E.E.
Assuming you're rooted and on a custom ROM
You will need unlimited data to try this.
Not sure if this will work, but please do try.
1. Make sure your phone is juiced up.
2. Download the Stock RUU you want from the internet - save to your sdcard
3. Download another sense based ROM that you has no issues with the USB cable - check the post and changelogs.
4. Perform rom backup with ROM manager (get from android market)
5. Wipe and flash new Sense based ROM on your phone.
6. Once your phone is booted, the USB SHOULD WORK.
7. Move RUU to your PC. Link to HTC sync - phone should be set to sync.
8. Install RUU.
And once it is one, you have unrooted and are back to stock ROM.
Should your USB fail at stage 6, you should try a different custom ROM.
If it's still not working, you might want to search how to USB unbrick (i think there's something like that on the forums).
Unfortunately its not a rom problem. The USB issue seems to be a hardware problem.
I have flashed multiple different backups from CM6 to myvery first backup I made of the newly rooted rom.
I just need to put a stock rom on it so that I can get warranteed service. Otherwise I'm pretty sure they'll just shoot it back to me, marked warranty void.
E.E.
Have you tried this?
It's to unbrick your usb
http://forum.xda-developers.com/showthread.php?p=7616115#post7616115
I had also problems with mounting USB, can't tell if they were the same as I don't use windows and can't tell how it behaves. My problem was solved after I flashed the rooted vodafone FroYo. Maybe this could help you, too.
I haven't tested it yet but it may be as simple as downloading the zip from shipped-roms.
(http://shipped-roms.com/download.ph...35.21_release_130330_signed.zip&send_file=yes)
Renaming it to update.zip and flashing it from Recovery.
Can anyone confirm?
E.E.
Actually the best solution I've found yet is this one here from the CM forums.
This using the .img files from the zip I downloaded from Shipped-Roms earlier
Instructions
---------------
1. Boot n1 to fastboot mode
2. Extract the FRG33 files to your tools directory in PC (you need system.img and boot.img)
3. In your tools directory, fastboot the following commands
fastboot flash system system.img
WAIT
fastboot flash boot boot.img
WAIT
Reboot
Alternative method
------------------------
Rename the stock file to passimg.zip
Now you need to use ADB to get it on the SD card, or just copy file to sd card root directory
Command: adb push passimg.zip /sdcard
Now get into the bootloader and it should detect the passimg.zip file and ask if you want to install it.
Click to expand...
Click to collapse
Since I have Fastboot available to me, this seems the most hopeful method.
Can anyone confirm is this not just hopeful thinking?
E.E.
http://forum.sdx-developers.com/index.php?topic=7108.0
On the original post by inxane he says to 2. Download the recovery and put it in C:\Program Files (Program Files (x86) if you are on 64 bit)\Samsung Electronics\SWUpgrade\Models\Binary. DELETE THE FILE ALREADY IN THERE OR YOU MAY PERMA-BRICK YOUR INTERCEPT...
Is the recovery just the cm01 tar file at the top because this link >http://www.sdx-downloads.com/devs/inxane/intercept/recoveryv14.tar can no longer be found.
sorry first time working with the intercept, i was going to try adb method but i heard the recovery goes away after you reboot.
From my experience, the CM01.tar file needs the recovery.rfs extracted. When you download SWUpgrade, you want to delete the file inside the Binary Folder and replace it with the recovery.rfs which happens to be Inxane's CM Recovery. The latest should be 2.5.1.0.
The reason it exists as a .tar file is becuse CM Recovery recognizes system files as .tar extensions. So if there was a case you wanted to reflash CM Recovery for some reason, you can do it inside CM Recovery so long as it's in the .tar container. Otherwise, you need the recovery.rfs file on the PC side.
From my experience, If you move CM01.tar to the Binary folder and run SWUpgrade, the upgrade won't start and it'll just hang.
alpha-niner64 said:
...the upgrade won't start and it'll just hang.
Click to expand...
Click to collapse
THANK YOU!!! I was wondering why it was hanging/just rebooting...
[Wrong link! My bad!]
I read that the Intercept can re-install it's stock recovery after rebooting the phone.
Recovery
Read this too
Basically someone is suggesting to just flash a root kernel (SlapKernel) with SW Upgrade. I'm going to try it out right now.
[EDIT] Flashing SlapKernel worked fine (and I wasn't rooted before...), and it's way more responsive so far. I suggest you follow these instructions
Hello XDA Developers! Last time I was here I was hacking a HTC Blue Angel..That was a long time away....I digress
I have this phone which is currently running a 2.3.4 rom and I have ClockworkMod Recovery v2.5.0.5, and when I download any of the 2.3.7 roms this is what happens:
I drag the recovery zip to my phone with no extraction at all and select install zip from recovery menu. It does nothing.
I extract the zip file and end up with recovery.img and a zip file. I drag both to the root of my memory card and then select install zip from my phone. I then get the following error:
i.imgur.com/xlHip.png
I have absolutely no idea what to try from here, the biggest problem i've dealt with thus far was a md5 mismatch...
Kevin
normankev said:
Hello XDA Developers! Last time I was here I was hacking a HTC Blue Angel..That was a long time away....I digress
I have this phone which is currently running a 2.3.4 rom and I have ClockworkMod Recovery v2.5.0.5, and when I download any of the 2.3.7 roms this is what happens:
I drag the recovery zip to my phone with no extraction at all and select install zip from recovery menu. It does nothing.
I extract the zip file and end up with recovery.img and a zip file. I drag both to the root of my memory card and then select install zip from my phone. I then get the following error:
i.imgur.com/xlHip.png
I have absolutely no idea what to try from here, the biggest problem i've dealt with thus far was a md5 mismatch...
Kevin
Click to expand...
Click to collapse
Try toggling script asserts, or re-download the file.
Also, I suggest updating your recovery to 2.5.1.8.
Thanks for the quick reply!
I toggled script asserts so it was enabled, for the raw unmodified zip file nothing happened, and for the extracted zip file I got an Error seven again
I've tried redownloading the file multiple times, even getting earlier versions of the rom to try.
How would I go about updating recovery? I don't have a functional usb cable at the moment unfortunately but if absolutely neccessary I can hack one up.
normankev said:
I toggled script asserts so it was enabled, for the raw unmodified zip file nothing happened, and for the extracted zip file I got an Error seven again
Click to expand...
Click to collapse
I think you should have the asserts disabled to get past the error. (use the extracted zip, which gave you the error 7)
If this does not help, probably best way to go forward is to get a usb cable and try flashing using fastboot
1. Place the superuser.zip file attached at the end of the post on your sd card.
2. Flash recovery in bootloader with "fastboot flash recovery <filename>.img". I recommend CWM 5.0.2.3 found in this thread - http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
3. Go to recovery, in "mounts and storage" select "mount system" and then flash su-install.zip (EDIT : Mounting system not necessary, the script does it automatically while flashing the zip, but just in case)
4. Fix Permissions and reboot system.
5. Use any root explorer (i recommend ROM Toolbox, free in market) and go to /etc and either rename "installrecovery.sh" to "installrecovery.sh.old" or just delete it (its not needed).
6. There it is - Rooted ICS with a recovery that sticks.
EDIT -- IF, by any chance, after following the above steps, you find that you're stuck without a recovery (android exclamation screen), just flash a recovery via fastboot and you'll be fine. This time the recovery WILL stick. I think its something to do with the su-install.zip. I dont know for sure because I found it off the internet, its not mine.
Also, I did the superuser market update and I DID NOT lose root. I have an I9020T. So others with the same can safely update, imo.
Thanks to ab.grafix for being a part of the team.
IMPORTANT -- The su-install.zip posted previously is NOT mine. I didnt know who made it but just found out. All credit to dzo binary and Chamb'. I just made a guide coz it worked for me and I thought it might help others too.
Tested on I9020T and I9023
Don't forget to click on that thanks button if this helped.
UPDATE -- Superuser was updated by ChainsDD to support ICS 4.0.3. Thank you ChainsDD! Updated zip is now attached.
So now that we have root we need a overclocked kernel...
Sent from my Nexus S using XDA App
works great but very old cwm
Worked as described. Thanks !
Old cwm? Wich version? Is it possible to flash the latest one with rom manager?
So I am on ICS alpha13.
I9023
- wipe everything and Flash Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader via clockworkmod
- Reboot in stock recovery and flash stock ICS
- Boot in ICS enable debug mode
- Run the bat follow instruction?
Is it ok?
Thanks
Hi will it work on the rogers i9023a? Can someone tell me which stock ICS to flash?
Thanks
Thanks, it worked and nothing was wiped since I was already unlocked. With apps that require root you no longer get asked for root permission nor do they show in app list in superuser but it seems to have root for now
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
when in BL i dont have Unlock option :|
Thanks for your effort.
But I'm curious about the flashable zip file.
What's the difference of the zip file between the orignal superuser ?
And did the recovery do some magic which CWM can't do?
After reading the script , I just see the zip is important ,maybe the recovery is doing some magic too.
I'll just flash the zip and see what happen.
ro_explorer said:
For the guys using linux (like me ) , just download the archive in the first post , retrieve from there 2 files: root.zip and recovery.img and use them with your current ADB setup.
HOW-TO:
Prerequisites: you have installed Android SDK, fastboot and you have set-up correctly the udev (ubuntu).
1. Place the above mentioned 2 files in the working directory
2. reboot in bootloader mode (vol-up + power)
3. connect USB cable
4. run "./fastboot-linux-i386 flash recovery recovery.img"
5. reboot bootloader
6. reboot recovery
7. mounts and storage -> usb mass storage
8. copy root.zip in the phone storage
9. go back -> install zip from sd card -> root.zip
DONE !
I just tested and is working fine.
If there are newbies out there trying to understand the nonsense I wrote, try following the rooting guide for Gingerbread and just use the 2 files I mentioned in this post instead of the ones in the archive for gingerbread.
Click to expand...
Click to collapse
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
I've done it, thanks a lot. I've also replaced the recovery.img file with the last cmw and all went well.
Now the rom doesn't show the root permission request toast but it works however.
I'd ask if its possible to manually update the superuser.apk or its better to mantain this one?
sakisds said:
In fact, you can use any recovery image you want, including the latest clockwork for example. I used TWRP to do this and it worked just fine. On linux, just flashed root.zip.
Click to expand...
Click to collapse
Great .. I'll do that because I miss my "old" cwm
EDIT: it worked, thanks!
thanks, working here on 9023. warning for other users - do not update superuser from the app itself, or it'll stop working. at least it did for me, when i updated it to 3.0.3
confirmed working I9020a...
[INFO] Working root for ICS 4.0.3
Credits to Chamb'.
Flash via CWM and you're done.
Tested working for ICS 4.0.3 I9020T.
Enjoy!
Source: http://forum.xda-developers.com/showpost.php?p=20394635&postcount=4
It seems to have worked like a charm, thank you!
I was even able to flash the latest CWM Recovery using ROM Manager
can I flash stock 2.3.6 with cwm?
Im on ics alpha13
Anyone got a download link for the stock 2.3.6?
bratfink said:
Anyone got a download link for the stock 2.3.6?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1063664
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Stinger2300 said:
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Click to expand...
Click to collapse
I have a rooted/unlocked Nexus 10, I used wugfresh's kit also. I got the OTA update last night. it installed. CWM never came up or did anything. During one of the boots after the green droid bot was saying "installing" the boot finished, but my green bot is now on his side. stomach open and it says "Error" in red bold letter.
I had to go to work, so I couldnt trouble shoot, but power off/on and soft reset (power+volume up select reset) didnt help. always comes to that "error".
I have data that is also not currently backed up with TBpro. hindsight I should have made sure I turned the scheduler on.
So I'm stuck also. not sure how to proceed. Got one recommendation to flash stock back on. But I think that will for sure wipe all my data. And beyond that, I dont know how, unless WUGs kit will do that.
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
jetguat said:
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
Click to expand...
Click to collapse
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Wow, this seems about 3 miles over my head but I guess I'll dive in and try it. Thanks for the info. I'm sure I'll be back with problems/questions.
planet_x69 said:
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Click to expand...
Click to collapse
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Stinger2300 said:
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Click to expand...
Click to collapse
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
planet_x69 said:
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
Click to expand...
Click to collapse
OK, downloaded that and will hold it for later. Hopefully after the questions I just asked are answered, I'll have enough info to proceed. Thanks for the help so far.
Stinger2300 said:
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
Click to expand...
Click to collapse
Correct - if you SIDELOAD the OTA it will UPGRADE and retain all data and application settings etc...
If you run the 4.4 update from the factory image it will WIPE ALL. So do not do that ....just pull the recover.img from it and get rid of the rest.
If you downloaded this: http://downloadandroidrom.com/file/N...10RootNew.zip#
and extracted it to a new folder - do this first!!!
then copy the recovery.img you just extracted from the factory 4.4 rar to the same folder as the adb and fastboot commands
copy the OTA file to same folder and rename it ota.zip to make your life easier
>fastboot reboot-bootloader to validate your computer can see the device and that the next steps will go as planned
If you are now back bootloader then:
>fastboot flash recovery recover.img
wait till its done..will take about 15 seconds tops
>fastboot reboot-bootloader again and go to recovery using the volume buttons
select and enter recovery mode
wait for dead droid to appear
press both Volume UP and Power at same time and you should get the load menu
select "apply updated from adb" and press power after selecting
orange colored type will now appear at the bottom of the screen
on your PC
>adb sideload ota.zip
wait till you see its completed successfully
then reboot
(you can also apply the smaller ota (1.7MB) this same way)
If all went well you have now booted up successfully and see that your ass has been saved from eternal hell from your wife's wrath...
reboot and fastboot flash your favorite custom recovery reboot again to recovery and apply the su update for root access
I hope this helps
You can also read this: http://www.androidpolice.com/2013/1...-download-and-install-android-4-4-now-krt16o/
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Stinger2300 said:
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Click to expand...
Click to collapse
not sure i follow you but from the 4.4 factory image you will need the recovery.img file thats it. You will also need the OTA upgrade that takes you from 4.3 to 4.4. You need the OTA so that you wont lose your wifes data and will upgrade only and not image the device.
I have to leave and wont be back on till later this weekend.
Going well so far...had an issue but figured it out.
Got to sideloading ota.zip, then after it got to 100% it started verifying the update package. Got an error:
'/system/app/BasicDreams.apk" has unexpected contents
E:Error in /tmp/update.zip
(status 7)
Installation aborted.
Now what?
I found this in the Nexus 7 section but not sure if it applies here or if there is a better way, if it's guaranteed to not wipe data, etc.: http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26
Did you try this solution? I'm stuck on the "Error in /tmp/update.zip" as well. Having the same issues, and I hope to update without loosing data.
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
have well
Stinger2300 said:
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
Click to expand...
Click to collapse
I just tried it. And it worked. Didn't loose any data.
Flashing the img files, and then proceeding to sideload the OTA zip. Booting didn't take too long, Android then started upgrading ("Optimizing app..."), and booted successfully. It took a while to open de app drawer though... But everything was still there.
Regaining root access is something I'll try later. I'm just happy to have my N7 booting again.
Just a small disclaimer. I don't really know what I'm doing (I kinda like messing around with my device, it's only way to learn something), so I cannot guarantee it will work for you.
Glad it worked for you, it didn't work for me. I got another error after doing the following commands:
Then, run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
then I rebooted back to bootloader, then "apply updated from adb" and then from the command line: >adb sideload ota.zip
It again loaded 100% and then started verifying the package. Then I got this error:
Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT160/907817:user/release-keys; this device has google/mantaray/manta:4.4/KRT16S/920375:user/release-keys.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What a F***ing nightmare...
Why do I apparently have the wrong version?
Hmm, might be the wrong OTA zip idd...
I downloaded mine from here: http://www.droid-life.com/2013/11/2...ial-update-for-nexus-7-2012-and-nexus-7-2013/