Related
Ok guys, I'm having a problem with install this rom.
I'm trying to install: http://forum.xda-developers.com/showthread.php?t=715180
I believe my device is rooted, I followed this guide: http://forum.xda-developers.com/showthread.php?t=702973
After following it, I did get superuser, and I did the terminal test, it worked. Even have root only applications working.
So, When I'm trying to install the rom, I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=704865 The download link to the update.zip is down, so I used the one from when I did the"How to root" guide. Not sure if it's the same or not.
So I put both zips on the sdcard (slideme.zip, and update.zip). I go into recovery mode, when I click apply update.zip, the green bar goes like 30%, then I get:
-- Install from sdcard..
Finding update package..
Opening update package..
Verifying update package..
E:failed to verify whole-file sidgnature
E:signature verfication failed
Installation aborted.
Click to expand...
Click to collapse
Anyone might be able to describe what's going wrong, and able to help me?
Rickmasta said:
Ok guys, I'm having a problem with install this rom.
I'm trying to install: http://forum.xda-developers.com/showthread.php?t=715180
I believe my device is rooted, I followed this guide: http://forum.xda-developers.com/showthread.php?t=702973
After following it, I did get superuser, and I did the terminal test, it worked. Even have root only applications working.
So, When I'm trying to install the rom, I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=704865 The download link to the update.zip is down, so I used the one from when I did the"How to root" guide. Not sure if it's the same or not.
So I put both zips on the sdcard (slideme.zip, and update.zip). I go into recovery mode, when I click apply update.zip, the green bar goes like 30%, then I get:
Anyone might be able to describe what's going wrong, and able to help me?
Click to expand...
Click to collapse
You need to either install the engineering rom (which will allow you to enter clockwork from now on the way you are trying) or get back in to clockwork using the same method you used when you rooted the device.
K, thanks. I'll check it out.
Hey guys i'm pretty new to this. I rooted my phone yesterday and i stuck on today Open Desire-4.0.15. I want to try another rom but when i try to apply the update.zip i get the message E:signature verification failed Installation aborted.
I hope you guys can help me and let me know if you need any more information
tribute said:
Hey guys i'm pretty new to this. I rooted my phone yesterday and i stuck on today Open Desire-4.0.15. I want to try another rom but when i try to apply the update.zip i get the message E:signature verification failed Installation aborted.
I hope you guys can help me and let me know if you need any more information
Click to expand...
Click to collapse
thats because the rom you are trying to flash has no signature, all you have to do is use a recovery that lets you flash unsigned .zip's, the latest version of clockworkmod recovery that comes with the unrevoked flash tool lets you do this
I did what you said and it worked from what i can tell and it loaded on AuraxTSense. The problem is at start up now it just says loading, this may take a few minutes to complete and just hangs there. I can't do anything with it and i can't change the rom from the recovery menu so now i'm even more stumped.
tribute said:
I did what you said and it worked from what i can tell and it loaded on AuraxTSense. The problem is at start up now it just says loading, this may take a few minutes to complete and just hangs there. I can't do anything with it and i can't change the rom from the recovery menu so now i'm even more stumped.
Click to expand...
Click to collapse
at witch part is it saying please wait? has the rom booted? did you do a full wipe before flashing? try doing a full wipe from the partitions menu in recovery and re flashing the rom
rebooted it and this time it just loaded up properly. Strange but hey.
Thanks for you help on my previous problem. It's basically the same issue but i've also tried deleting the partitions in the recovery menu. I've tried changing the rom from clockworkmod, nothing is working. It just puts AuraxTSense back to default.
Hey guys, first of all I'm a complete n00b to all of this stuff, so please bear with me and consider using layman type language with me. Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.
Here's the bullet-point run-down of what happened:
- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.
- Read through a thread on here on how to flash to "yakju". Did so successfully.
- I then wanted to root since my device was already wiped from unlocking bootloader or flashing some partition or something
- Followed this thread (http://forum.xda-developers.com/showthread.php?p=19583168#post19583168)
- Rebooted, saw the "Superuser" app and thought I nailed it.
- Saw an update for Jellybean, it requested a reboot before install
- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.
- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading around, downloaded SU Update Fixer from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.
So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.
** One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery on my phone just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assumed it was since I got the Superuser app.
Another thing that felt kind of wrong is that, when I flashed to yakju, it wiped my phone clean. I expected rooting to do the same thing, but it didn't (I think because my bootloader was already unlocked?). So I'm not sure if that has anything to do with it either.
Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing files from a directory, etc.
Thank you in advance.
BryMerc said:
Hey guys, first of all I'm a complete n00b to all of this stuff, so please bare with me and consider using layman type language with me. Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.
Here's the bullet-point run-down of what happened:
- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.
- Read through a thread on here on how to flash to "yakju". Did so successfully.
- I then wanted to root since my device was already wiped from unlocking bootloaderor or replace some partition or something
- Followed this thread (http://forum.xda-developers.com/showthread.php?p=19583168#post19583168)
- Rebooted, saw the "Superuser" app and thought I nailed it.
- Saw an update for Jellybean, it requested a reboot before install
- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.
- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading downloaded SU Update fixed from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.
So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.
One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assume it was if I got the Superuser app.
Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing .img files from a directory, etc.
Thank you in advance.
Click to expand...
Click to collapse
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
you can also install the OTA manually, heres my method
1) grab the link for yakju IMM76i > 4.1.1 from here: http://forum.xda-developers.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.
2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, press vol down twice in the bootloader and go straight into the recovery.
3) install the OTA zip you downloaded and placed in your sdcard
4) clear cache and fix permissions (might not be necessary but you can do it just incase)
5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.
6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.
7) reboot. should be all sorted now
JaiaV said:
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the fast response.
So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot?
Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?
Thanks.
BryMerc said:
So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot
Click to expand...
Click to collapse
Yes.
BryMerc said:
Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?
Click to expand...
Click to collapse
JaiaV said:
OTAs do not care if you are rooted or have an unlocked bootloader.
Click to expand...
Click to collapse
They only care that the recovery and /system are stock, and even then (as I said) don't care if you're rooted. Rooting doesn't matter. Having a custom recovery does. They are not the same thing. Also, read through ||Nexus|| response.
IINexusII said:
you can also install the OTA manually, heres my method
1) grab the link for yakju IMM76i > 4.1.1 from here: http://forum.xda-developers.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.
2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, but dont reboot this time, press vol down twice in the bootloader and go straight into the recovery.
3) install the OTA zip you downloaded and placed in your sdcard
4) clear cache and fix permissions (might not be necessary but you can do it just incase)
5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.
6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.
7) reboot. should be all sorted now
Click to expand...
Click to collapse
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
BryMerc said:
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
Click to expand...
Click to collapse
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.
edit: yes itll just be replacing the recovery, nothing else
IINexusII said:
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.
edit: yes itll just be replacing the recovery, nothing else
Click to expand...
Click to collapse
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
BryMerc said:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
Click to expand...
Click to collapse
in clockwork mod recovery there should be a "Wipe Cache" option, and for fixing permissions go to "advanced" and "Fix Permissions"
BryMerc said:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
Click to expand...
Click to collapse
Wait, actually I don't think the JB installed now that I'm staring at the screen properly.
It went Installing update...
assert failed: file .........blah blah
Installation aborted.
Also, the drivers I thought I had for my phone seem to be messing up and in device manager it says "Full" with an exclamation point. I'm not sure why.
Sorry for the late responses as a n00b I'm stuck with 5 minute intervals here.
which country are you from?
IINexusII said:
which country are you from?
Click to expand...
Click to collapse
Canada.
I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
BryMerc said:
Canada.
I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
Click to expand...
Click to collapse
After selecting "Install zip from sdcard" I see an option "apply /sdcard/update.zip". Is that anything maybe I need to do or something?
check your PM
I recently installed cm10 on my fathers S3 and everything went smooth until root checker said I did not have root access. I dont see how I missed it, I used the steps from the guide on androidauthority.com as well as the steps from the links the guide provided to install clockworkmod and cm10. My S3 is rooted with cm10 with no issue. but my fathers isnt after the install when i used the same guide. Is there a way to root on cm10 without having to wipe and install the stock rom and then root?
simba33 said:
I recently installed cm10 on my fathers S3 and everything went smooth until root checker said I did not have root access. I dont see how I missed it, I used the steps from the guide on androidauthority.com as well as the steps from the links the guide provided to install clockworkmod and cm10. My S3 is rooted with cm10 with no issue. but my fathers isnt after the install when i used the same guide. Is there a way to root on cm10 without having to wipe and install the stock rom and then root?
Click to expand...
Click to collapse
Just reflash the CM10 zip, its pre-rooted. I don't know why its saying you're not rooted in the first place really. Do you see the "Superuser" app in the app drawer?
prscarp said:
Just reflash the CM10 zip, its pre-rooted. I don't know why its saying you're not rooted in the first place really. Do you see the "Superuser" app in the app drawer?
Click to expand...
Click to collapse
thats the weird part! haha I see super user, it opens and everything but it never pops up when i open apps that require root, and root checker says it isnt rooted. Ive wiped and installed CM10 twice, as well as the superuser.zip file the guide says to install with clockworkmod.
In the superuser app, try updating the su binary. Maybe that will fix it.
prscarp said:
In the superuser app, try updating the su binary. Maybe that will fix it.
Click to expand...
Click to collapse
I dont know why it fails but it doesnt like me getting root access. failed at: "gaining root access.... Fail!" when i clicked update
everything is green and says okay until gaining root access then i get the red fail! I took a screenshot but I dont have enough posts to insert the image
What recovery did you install?
I would redownload the CM10 zip, put it on your sd card, reboot into recovery, make a nandroid if you prefer, wipe system, dalvik, and cache, then flash the newly downloaded CM10 zip and gapps again.
This is definitely a strange problem lol
tonymtl said:
What recovery did you install?
Click to expand...
Click to collapse
the zip file says cm-10-20120925-NIGHTLY-d2att.zip
prscarp said:
I would redownload the CM10 zip, put it on your sd card, reboot into recovery, make a nandroid if you prefer, wipe system, dalvik, and cache, then flash the newly downloaded CM10 zip and gapps again.
This is definitely a strange problem lol
Click to expand...
Click to collapse
dang it didnt want to but oh well I'll give it a shot in a few. and yes very strange i never have the normal problems -__-
simba33 said:
the zip file says cm-10-20120925-NIGHTLY-d2att.zip
Click to expand...
Click to collapse
Thats the CM10 zip. Are you using clockwork mod recovery? or TWRP? I haven't had any issues with TWRP.
simba33 said:
dang it didnt want to but oh well I'll give it a shot in a few. and yes very strange i never have the normal problems -__-
Click to expand...
Click to collapse
As long as you dont wipe data you won't lose anything. The only effect this will have is, hopefully, fix root.
prscarp said:
Thats the CM10 zip. Are you using clockwork mod recovery? or TWRP? I haven't had any issues with TWRP.
As long as you dont wipe data you won't lose anything. The only effect this will have is, hopefully, fix root.
Click to expand...
Click to collapse
I'm using Clockworkmod recovery as advised by the guide.
ok i'll give it a shot in a few minutes
Did you flash any custom recovery ??? That cm10 doesn't install it. Also get a more recent cm10 at get.cm
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
What version of cwm?
prscarp said:
Thats the CM10 zip. Are you using clockwork mod recovery? or TWRP? I haven't had any issues with TWRP.
As long as you dont wipe data you won't lose anything. The only effect this will have is, hopefully, fix root.
Click to expand...
Click to collapse
ok well i get an error:
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
E:Error in /sdcard/cm-10-20121009-NIGHTLY-d2att.zip
(status 7)
installation aborted
I downloaded the 2nd latest which was added to the site yesterday from the other guys site he suggested. I got this same error on my phone and somewhere when googling someone said download notepad++ and erase the top line within the zip file and it installed for me. but i shouldnt have to do that. whats going on? i wiped everything you told me except factory/data
tonymtl said:
Did you flash any custom recovery ??? That cm10 doesn't install it. Also get a more recent cm10 at get.cm
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
What version of cwm?
Click to expand...
Click to collapse
Yes i ave clockworkmod recovery and I downloaded that cm-10 a couple of weeks ago and I have root. its the same zip. but I downloaded the more recent, (2nd most recent on the site you referred) and it wont install as i stated in my previous post
simba33 said:
ok well i get an error:
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
E:Error in /sdcard/cm-10-20121009-NIGHTLY-d2att.zip
(status 7)
installation aborted
I downloaded the 2nd latest which was added to the site yesterday from the other guys site he suggested. I got this same error on my phone and somewhere when googling someone said download notepad++ and erase the top line within the zip file and it installed for me. but i shouldnt have to do that. whats going on? i wiped everything you told me except factory/data
Click to expand...
Click to collapse
That has also never happened to me lol. Right before you flash the zip, select the "Toggle script asserts" option then try to flash.
A little explaination: When you go to flash the zip, it checks your current build.prop to make sure you're flashing the right rom to the right device. Since we wiped system before flashing, the build.prop is gone and it is unable to check. TWRP might not check which is why it has never happened to me. I don't know for sure that this is the case but I am just guessing.
You need to update recovery.
prscarp said:
That has also never happened to me lol. Right before you flash the zip, select the "Toggle script asserts" option then try to flash.
A little explaination: When you go to flash the zip, it checks your current build.prop to make sure you're flashing the right rom to the right device. Since we wiped system before flashing, the build.prop is gone and it is unable to check. TWRP might not check which is why it has never happened to me. I don't know for sure that this is the case but I am just guessing.
Click to expand...
Click to collapse
I tried the toggle idea and it didnt work, can you link me to a TWRP download? this is getting annoying lol I appreciate the help so far though
lol well this is annoying.
http://www.teamw.in/project/twrp2/104
Here is the link to TWRP for the AT&T SGS3. Grab the .img file near the bottom and flash it with fastboot. I assume you are familiar with fastboot?
fastboot flash recovery openrecovery-twrp-2.2.2.0-d2att.img
I love this recovery btw, so much easier to use than CWM
prscarp said:
lol well this is annoying.
http://www.teamw.in/project/twrp2/104
Here is the link to TWRP for the AT&T SGS3. Grab the .img file near the bottom and flash it with fastboot. I assume you are familiar with fastboot?
fastboot flash recovery openrecovery-twrp-2.2.2.0-d2att.img
I love this recovery btw, so much easier to use than CWM
Click to expand...
Click to collapse
uhm actually no im not familiar with it. ive heard of it but not sure how it works, i just tried doing my own research on it for about 20 minutes and still not sure how it works. can you point me in the right direction here?
You will need to get the android sdk, run it and install the tools. You should then have a platform-tools folder that includes fastboot.exe. place the recovery img in that directory, open a command prompt to that directory, put your phone in fastboot mode and run the command I wrote above.
Sorry about being brief about it, I'm on my phone right now. I can help more later when I'm at a pc.
prscarp said:
You will need to get the android sdk, run it and install the tools. You should then have a platform-tools folder that includes fastboot.exe. place the recovery img in that directory, open a command prompt to that directory, put your phone in fastboot mode and run the command I wrote above.
Sorry about being brief about it, I'm on my phone right now. I can help more later when I'm at a pc.
Click to expand...
Click to collapse
what is fastboot mode? is that download mode? lol sorry but I havent messed with fastboot at all. Ive rooted a bunch of phones and flashed quite a few but never worked with fastboot
Alright, so I honestly have no Idea what to do now. I've got an Xperia Play R800X, and a TON of questions. First, what causes your bootloader to Re-Lock? I want to make sure that doesn't happen. Next, how do I get Jelly Bean on my Play? I'm not sure what the best Kernel and Rom to use are. Next, HOW do you flash kernels and ROMs? Any help is appreciated!
jrk190 said:
Alright, so I honestly have no Idea what to do now. I've got an Xperia Play R800X, and a TON of questions. First, what causes your bootloader to Re-Lock? I want to make sure that doesn't happen. Next, how do I get Jelly Bean on my Play? I'm not sure what the best Kernel and Rom to use are. Next, HOW do you flash kernels and ROMs? Any help is appreciated!
Click to expand...
Click to collapse
the only way to re-lockyour bootloader that I know of is to flash a re-lock bootloader.zip file.
For the kernel you'll have to search for one that's compatible with JB, then flash the rom. Read this.
http://forum.xda-developers.com/showthread.php?t=1808289
That helps, but, say, in FXP, there's a folder that has boot.img, system, and META-INF. What do I do with those. Which is the ROM, which is the Kernel...
The rom is the zip itself, the kernel is the boot.img in the zip. The kernel must first be extracted, then flashed in fastboot with the command "fastboot flash boot boot.img"
jacklebott said:
The rom is the zip itself, the kernel is the boot.img in the zip. The kernel must first be extracted, then flashed in fastboot with the command "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Alright, I'll try that. Last time I got stuck in a bootloop, because I flashed the ROM and never did the Kernel. So, let me get this straight:
1) Drag the Zipped FXP ROM/Kernel Folder into CWM Backup folder.
2) Restore from that Folder.
3) Go into Fastboot
4) Go into Flashtool and Flash the Boot.img
That's what I know to do. Anything I should change first? I'll be waiting for a reply before I actually do it.
Did I get that all right? I'm about to try this...
No. Flash the kernel first. Boot into ClockworkMod Recovery by following the directions on FXP's details page (should be either a volume button or the left shoulder button for most kernels). Put the zip file on your SD card, then flash the zip from inside clockwork mod. Please look around, there are some REALLY simple tutorials on this already posted here. They're even stickied at the top of the forum
I flashed the kernel and booted. I can't get into CWM and get a bootloop...
Edit: I went into Recovery, and never saw an option to flash. Just restore from a backup. Im using the CWM installer v5.
jrk190 said:
I flashed the kernel and booted. I can't get into CWM and get a bootloop...
Edit: I went into Recovery, and never saw an option to flash. Just restore from a backup. Im using the CWM installer v5.
Click to expand...
Click to collapse
should be under restore if yo placed it on the sd card.
I did. It says Installation aborted. I didn't get to read it, I'll try to recreate the error.
The option is called "install from SD card" it should be the second option from the start screen
Nope, that's Apply update from SD Card. Now, I'm getting a MD5 Mismatch. This just isn't my day...
Then choose apply update from sd card. How the hell do you get an md5 mismatch when installing a rom? That only happens when restoring a backup.
Short Answer: I have no Idea what I'm doing.
Long Answer: I had no idea what I'm doing, but I might have a slight understanding now. I'll try again...
This time it says error in /sdcard/update.zip
(Status 7)
Installation aborted.
Maybe try deleting the boot.img from the zip file. I don't know if it can install correctly if the boot.img is still in the zip, because I've always removed it before flashing
I'll give that a go...
Same Error as before.
jrk190 said:
This time it says error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
wait a second, is your zip file called "update.zip" or something else?
EDIT: If it's called something else, then choose "install zip from sdcard" which is a few lines below "apply update from sdcard". Then in that menu, select "choose zip from sdcard". Then pick your zip file
The first time I renamed the file update.zip. I'll try again in the morning, I'm tired, and a bit frustrated with all of this. I wish someone could do it for me... Though there is an Android dev at school. I'll let him take a look at it, if I have time.