hello im currently on an older build of the aokp. ive decided to update to the newest build, but i see that it says i would have to update my kernel as well to use the new rom. Ive never done this and would appericate some help. I opened up the q & a forum and searched for kernel but it didnt tell me anything. thanks, step by step instructions would be awsome thanks.
The kernel is packaged with the rom. Download the rom and gapps. Wipe and flash them both in recovery. If you hold on another week or so, they're releasing a 4.2.2 milestone (supposedly)
Naruto101 said:
hello im currently on an older build of the aokp. ive decided to update to the newest build, but i see that it says i would have to update my kernel as well to use the new rom. Ive never done this and would appericate some help. I opened up the q & a forum and searched for kernel but it didnt tell me anything. thanks, step by step instructions would be awsome thanks.
Click to expand...
Click to collapse
If you are flashing a new version of Tasks aokp from an old version just wipe cache, wipe dalvik, flash newest version, flash gapps ( there is a newer version linked on his op). Kernel is built into the ROM.
If you are flashing from a different rom you need to factory reset and format system as well as wipe cache and dalvik.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
If you are flashing a new version of Tasks aokp from an old version just wipe cache, wipe dalvik, flash newest version, flash gapps ( there is a newer version linked on his op). Kernel is built into the ROM.
If you are flashing from a different rom you need to factory reset and format system as well as wipe cache and dalvik.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
perfect thanks guys
okay i got another problem here im already on aokp build, when i try to wipe dalvik it says E: uknown volume for path [/sd-ext] dalvik cache wiped. (not too sure if it worked or not) then when i try to flash the rom it says finding updaet package... opening update package .,... installing update ....
assert failed: getprop("ro.product.device") == "d2att"
E: error in /emmc/0/download/aokp_JB_4.2.2._d2att-
ota-eng. task650-4.9.2013.zip
(status 7)
Naruto101 said:
okay i got another problem here im already on aokp build, when i try to wipe dalvik it says E: uknown volume for path [/sd-ext] dalvik cache wiped. (not too sure if it worked or not) then when i try to flash the rom it says finding updaet package... opening update package .,... installing update ....
assert failed: getprop("ro.product.device") == "d2att"
E: error in /emmc/0/download/aokp_JB_4.2.2._d2att-
ota-eng. task650-4.9.2013.zip
(status 7)
Click to expand...
Click to collapse
Hit thanks instead of quote. You need to update your recovery version. That's what a status 7 means.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Hit thanks instead of quote. You need to update your recovery version. That's what a status 7 means.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh I have never heard updating recovery before any help would be awesome!
Naruto101 said:
Oh I have never heard updating recovery before any help would be awesome!
Click to expand...
Click to collapse
If you are using clockworkmod download ROM manager and update recovery. If you are using twrp install goo manager and update recovery script.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
And if you got far enough into wiping that you can't boot into the phone, follow the link in my signature. Near the bottom of post #2, in the must have toolkit part, there are links to recovery flashable cwm and twrp zips. Cheers
Related
I\ve downloaded the d2att CM9 zip file transfered to sd card, factory wiped then tried to install zip from sd card but keep getting the error after it starts installing update
"assert failed: get prop ("ra.product.device) =="d2att get prop (ra.build.product == "d2att E:error in sd card/cm-9-20120722-nightly -d2att.zip (status 7) install aborted
Any suggestions?
Are you using the right recovery?
Sent from my SAMSUNG-SGH-I747 using xda premium
I had to buy the new Rom manager on the playstore and flash my first nightly through there.
Otherwise you have to change some lines of code.
It's discussed in the T-Mobile cm9 nightly thread.
Sent from my SGH-T999 using xda premium
On the second page of the thread in android development. Not the original development thread
Sent from my SGH-T999 using xda premium
still no go
I purchased Rom Manager premium this morning and tried again to flash from that and now the error reads unknown volum for path [sdcard:-9-20120702cannot mount sdcard zip install aborted. Grrr Argg I'm feeling really kinda noobie
could it be my recovery?
When i try to flash CWM recovery my phone doesn't appear in the list
tried download directly from rom manager
ok so it's still not working I've downloaded CM from Rom Manager flased from there wiped date and Davik error reads :
installing update...
assert failed : getprop (ro.product.device") =="sgh-t989 II get prop E; error in sd card/clockworkmod/download/cms3.clockworkmod.com/release9.0.0-rc2-hercules/cm9.0rc2-hercules.zip
please help
ecliff said:
ok so it's still not working I've downloaded CM from Rom Manager flased from there wiped date and Davik error reads :
installing update...
assert failed : getprop (ro.product.device") =="sgh-t989 II get prop E; error in sd card/clockworkmod/download/cms3.clockworkmod.com/release9.0.0-rc2-hercules/cm9.0rc2-hercules.zip
please help
Click to expand...
Click to collapse
T989? Isnt that the galaxy s2?
Sent from my SAMSUNG-SGH-I747 using xda premium
ecliff said:
ok so it's still not working I've downloaded CM from Rom Manager flased from there wiped date and Davik error reads :
installing update...
assert failed : getprop (ro.product.device") =="sgh-t989 II get prop E; error in sd card/clockworkmod/download/cms3.clockworkmod.com/release9.0.0-rc2-hercules/cm9.0rc2-hercules.zip
please help
Click to expand...
Click to collapse
Make sure you downloaded the right version for your device; that's a buildprop error saying the device you're flashing to doesn't match the buildprop inside the file.
defnow said:
T989? Isnt that the galaxy s2?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Yeah that's why I'm confused. I download directly from Rom Manager I didn't have a list of CM9 variants to choose from it just downloaded it
I'm wondering if my Rom Manager thinks I have a diffrent phone and how to change it
might have got this one cased
I didn't have the right verison of recovery. I have 5.8.1.3 and need to flash 5.8.4.7 I have the file but it a img file how to i get the img file from my comp to my phone. I tried just placing it in the phone. not sure i should update sd card in recovery or not please some one help !!!! I really want to get rid of my stock rom
omg i think it might have worked but i can't get past the bootimage
so you flashed the new recovery?
defnow said:
so you flashed the new recovery?
Click to expand...
Click to collapse
Yeah i found a zip file and downloaded that its 5.8.4.5 but it seemed to work but now i can't back up my rom because my sd won't mount in recovery and a couple of things arn't workking like facebook contact sync, swype, might switch back to stock rom not sure yet
Ok, (obvious newbie here)
I'm rooted with SU
I just attempted to install most recent CM10 Nightly and when trying to install it i get "Verifying update package... E: Signature verification failed...Installation aborted.
So um...I also tried this with the 2nd newest CM10 build just to see if anything different would happen and I got the same error.
Any ideas??
Get newest cwm
Sent from my SAMSUNG-SGH-I747 using xda premium
6012
JB calhoun said:
Get newest cwm
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm using 6.0.1.2 isn't that the newest cwm?
is it because i did not select wipe data/factory reset & wipe cache partition before trying to install it?
*Update*- I just retried this after wiping factory data and cache and it gave me the same error with both CM10 and AOKP....frustrating
theinvid said:
I'm using 6.0.1.2 isn't that the newest cwm?
is it because i did not select wipe data/factory reset & wipe cache partition before trying to install it?
*Update*- I just retried this after wiping factory data and cache and it gave me the same error with both CM10 and AOKP....frustrating
Click to expand...
Click to collapse
This is from September and there's still not a solution? Ugh, just my luck.
Having exact same error when trying to update through the built in process. Mine also says "location does not exist" as well as the signature verification error.
Please help if you can!
Thx,
-AJ
theinvid said:
Ok, (obvious newbie here)
I'm rooted with SU
I just attempted to install most recent CM10 Nightly and when trying to install it i get "Verifying update package... E: Signature verification failed...Installation aborted.
So um...I also tried this with the 2nd newest CM10 build just to see if anything different would happen and I got the same error.
Any ideas??
Click to expand...
Click to collapse
And did you try team win recovery project? Here's the link with all installation infos you'll need.
http://teamw.in/project/twrp2/104
Sent from my SGH-I747 using xda app-developers app
FIX
theinvid said:
Ok, (obvious newbie here)
I'm rooted with SU
I just attempted to install most recent CM10 Nightly and when trying to install it i get "Verifying update package... E: Signature verification failed...Installation aborted.
So um...I also tried this with the 2nd newest CM10 build just to see if anything different would happen and I got the same error.
Any ideas??
Click to expand...
Click to collapse
Very easy fix. After it "fails", go to "Install from SD card". Click the "Toggle Signature Verification" option. Then go back and try to install it again. I've found I have to do this every single time to successfully install the Nightly updates that are pushed OTA. Works like a dream afterwards tho.
when trying to install a new rom i get the same error (status 7: some symlinks failed) with the cm10 and eclipse ROMs. I don't seem to have any trouble with Buglessbeast and euroskank. I have googled and searched XDA but none of the other threads are for the toroplus.
Edit: Thanks for all the help guys. I'm still having this problem.
Things i have tried: go into mounts and remove the top X on the list.(TWRP)
flashing a stock kernel gets me stuck in a boot loop.
I am using the franco kernel and had this same issue using CWM before switching to TWRP.
You can try this...
simms22 said:
try booting out of recovery into the bootloader, then back to recovery to reflash.
Click to expand...
Click to collapse
If you do a Google search you should find some information on it. Its something with the Franco kernel changing the sdcard. Have to download And move the original back into it's correct place
Sent from my Galaxy Nexus using xda premium
qbanlinxx said:
If you do a Google search you should find some information on it. Its something with the Franco kernel changing the sdcard. Have to download And move the original back into it's correct place
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Huh?
Op never even made mention to the word "kernel" in his post.
Not to mention kernel is not even running in recovery (which itself is a small os).
Sent from my i9250
natheist411 said:
when trying to install a new rom i get the same error (status 7: some symlinks failed) with the cm10 and eclipse ROMs. I don't seem to have any trouble with Buglessbeast and euroskank. I have googled and searched XDA but none of the other threads are for the toroplus.
Click to expand...
Click to collapse
Are you using TWRP recovery? If you are that's the issue. The latest update has a flaw, you have to go into recovery, go into mounts and remove the top X on the list. They said they where working on releasing a correction for it. If your not on TWRP then I don't know what's going on.
Sent from my Galaxy Nexus
I was using cwm but switched to TWRP to retry. Same issue.
Sent from my Galaxy Nexus using xda app-developers app
natheist411 said:
I was using cwm but switched to TWRP to retry. Same issue.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Try it when you get into recovery, go to mounts, remove the X on the top option on the list then flash the rom see if it works.
Sent from my Galaxy Nexus
I had this same issue yesterday, and it was related to flashing a kernel. Sorry for trying to help
bk201doesntexist said:
Huh?
Op never even made mention to the word "kernel" in his post.
Not to mention kernel is not even running in recovery (which itself is a small os).
Sent from my i9250
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using xda premium
qbanlinxx said:
I had this same issue yesterday, and it was related to flashing a kernel. Sorry for trying to help
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have also seen something similar. What most people don't realize is the some kernels, including Franco, change things in /system as well, which messes with some things.
Sent from my Galaxy Nexus using Tapatalk 2
Okay, thanks. I was not aware of this. Will checkout some kernel zips to see what's going on.
edfunkycold said:
Try it when you get into recovery, go to mounts, remove the X on the top option on the list then flash the rom see if it works.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I tried this. Still the same outcome. Thanks anyways.
Has this been fixed? I cant install any ROM!
I have exactly the same problem! I am using stock kernal, was using franco kernal before that.
Milamber said:
Has this been fixed? I cant install any ROM!
I have exactly the same problem! I am using stock kernal, was using franco kernal before that.
Click to expand...
Click to collapse
no one here was help but i think i figured it out myself.
try this and see if it works.
when you go to install the rom, before doing so wipe data (factory reset) three times.
i was so frustrated about it i finally said **** it and didnt care if i lost everything, but i didnt loose anything so all is well.
let me know if that works
(status 7) some symlinks failed
I'm fixed this problem, PLEASE ADD THIS POST TO FAQ . Just install Android Commander and copy ROM to phone via it, now i'm on JellyBam android 4.1.2.
1.Install root+busybox.
2.Install via stock recovery siyah 5.0b2
3.In siyah recovery do factory reset
4.Flash any custom ROM
5.Do factory reset, wipe cache, wipe Dalvik cache.
6.Be happy, enjoy.
I'm tryied many recoveryes and kernels, but the problem is in copying process(now all zip's have good CRC, and MD5). . Give me a beer
JeyLo said:
(status 7) some symlinks failed
I'm fixed this problem, PLEASE ADD THIS POST TO FAQ . Just install Android Commander and copy ROM to phone via it, now i'm on JellyBam android 4.1.2.
1.Install root+busybox.
2.Install via stock recovery siyah 5.0b2
3.In siyah recovery do factory reset
4.Flash any custom ROM
5.Do factory reset, wipe cache, wipe Dalvik cache.
6.Be happy, enjoy.
Click to expand...
Click to collapse
Huh? What is siyah 5.0b2???
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Milamber said:
Huh? What is siyah 5.0b2???
Click to expand...
Click to collapse
He's on a different device.
Sent from my i9250
chrisjenx2001 said:
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Click to expand...
Click to collapse
Wipe/Factory reset does not touch the system partition at all. This is normal. It only wipes the userdata partition.
chrisjenx2001 said:
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Click to expand...
Click to collapse
Had a bad download and on initial install I formatted system however it failed. Went back and formatted system and cache manually and worked for me.
I'm not sure if this is related, but I read in the MMuzzy's Jelly Bean 4.2.1 thread (http://forum.xda-developers.com/showthread.php?t=1762846, first post specifically) that unmounting /system fixes this problem, and sure enough it solved the problem for me when I tried to flash that ROM.
Hi all. I'm going absolutely crazy over here. I have an i747 and I rooted it, no problem. The problem that I am having is that I'm currently running 4.1.2 and for the life of me, cannot figure out how to get it to 4.2. I've tried installing CM10, but every time I try and flash it in CWM, I get a E: Error in /emmc/cm10.zip (Status 7). I've tried installing other 4.2 ROMs like Paranoid Android etc, but get the same/similar error. I can flash other custom ROMs, like Alliance and such. I'm sure I'm over thinking this and just need a fresh set of eyes on the issue and a point in the right direction here. Your help is much appreciated.
What version of cwm are you running?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
jon_yarbrough said:
Hi all. I'm going absolutely crazy over here. I have an i747 and I rooted it, no problem. The problem that I am having is that I'm currently running 4.1.2 and for the life of me, cannot figure out how to get it to 4.2. I've tried installing CM10, but every time I try and flash it in CWM, I get a E: Error in /emmc/cm10.zip (Status 7). I've tried installing other 4.2 ROMs like Paranoid Android etc, but get the same/similar error. I can flash other custom ROMs, like Alliance and such. I'm sure I'm over thinking this and just need a fresh set of eyes on the issue and a point in the right direction here. Your help is much appreciated.
Click to expand...
Click to collapse
Status 7 is an out of date recovery, so make sure that's updated.
Also the newest cm10 and aokp and Pac man need updated bootleggers. Check the cm10 thread for the links to the Odin files.
http://forum.xda-developers.com/showthread.php?p=41535366
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I'm running cwm 5.5.0.4
Sent from my SAMSUNG-SGH-I747 using xda premium
jon_yarbrough said:
I'm running cwm 5.5.0.4
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Read up on what the status 7 error means. Also, I would recommend switching from CWM to TWRP.
jon_yarbrough said:
I'm running cwm 5.5.0.4
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Cwm is up to 6.0.2.8
Just needs an update.
http://forum.xda-developers.com/showthread.php?p=38962585
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Cwm is actually sitting currently at 6.0.3.1. Here is the latest cwm flashable zip: http://forum.xda-developers.com/attachment.php?attachmentid=1888710&d=1366136727
Flash this in cwm, go to advanced, select reboot recovery. Once back in, make a new backup.
Before you flash a 4.2 rom from 4.1, wipe everything. Save everything you want to an sd card or your PC. Place your desired rom and gapps on a micro sd card. Wipe data, wipe cache and dalvik. Format /system and /data. Flash rom and gapps.
xBeerdroiDx said:
Cwm is actually sitting currently at 6.0.3.1. Here is the latest cwm flashable zip: http://forum.xda-developers.com/attachment.php?attachmentid=1888710&d=1366136727
Flash this in cwm, go to advanced, select reboot recovery. Once back in, make a new backup.
Before you flash a 4.2 rom from 4.1, wipe everything. Save everything you want to an sd card or your PC. Place your desired rom and gapps on a micro sd card. Wipe data, wipe cache and dalvik. Format /system and /data. Flash rom and gapps.
Click to expand...
Click to collapse
Lol I did the same thing last time.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Lol I did the same thing last time.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hahaha. I thought that was you. Cheers, KorGuy!
Thanks all. I just went into ROM Manager and updated CWM to the current version of 6.0.3 and it worked like a freakin' charm. I will be sure to hit THANKS for you all. Thanks again.
xBeerdroiDx said:
Cwm is actually sitting currently at 6.0.3.1. Here is the latest cwm flashable zip: http://forum.xda-developers.com/attachment.php?attachmentid=1888710&d=1366136727
Flash this in cwm, go to advanced, select reboot recovery. Once back in, make a new backup.
Before you flash a 4.2 rom from 4.1, wipe everything. Save everything you want to an sd card or your PC. Place your desired rom and gapps on a micro sd card. Wipe data, wipe cache and dalvik. Format /system and /data. Flash rom and gapps.
Click to expand...
Click to collapse
It's actually 6.0.3.2 now, but you have to build it yourself to get it as the latest released version is still 6.0.3.1.
https://github.com/CyanogenMod/andr...mmit/6f8d24d326258f2293436c50caca1c50eccab329
klin1344 said:
It's actually 6.0.3.2 now, but you have to build it yourself to get it as the latest released version is still 6.0.3.1.
https://github.com/CyanogenMod/andr...mmit/6f8d24d326258f2293436c50caca1c50eccab329
Click to expand...
Click to collapse
:laugh:
It's not a release until it's released.
Cheers, klin
I want to try this LiquidSmooth ROM from this thread http://forum.xda-developers.com/showthread.php?t=2295554
but when I just flash it after wipe all data/cache/dalvik etc.. I got this error
Creating Symlinks...
symlink: some symlinks failed
Error status 7
schnichiz said:
I want to try this LiquidSmooth ROM from this thread http://forum.xda-developers.com/showthread.php?t=2295554
but when I just flash it after wipe all data/cache/dalvik etc.. I got this error
Creating Symlinks...
symlink: some symlinks failed
Error status 7
Click to expand...
Click to collapse
did u wipe it properly?
-wipe cache,
-wipe factory
-format sys/cache/data/sdcard (not external sdcard)
-wipe dalvik
-flash the rom
I tried 3 ROM before and wipe it properly, but for this one it showing error..
so I using other ROM now..
maybe I will try this ROM later when there is an update...
schnichiz said:
I tried 3 ROM before and wipe it properly, but for this one it showing error..
so I using other ROM now..
maybe I will try this ROM later when there is an update...
Click to expand...
Click to collapse
That's not the rom's problem. That's mean the zip file maybe not properly download. Maybe it was not complete download or something similar like that. Did you check the md5sum?
Sent from my CM10.1 Wonder using xda premium
geniusboy93 said:
That's not the rom's problem. That's mean the zip file maybe not properly download. Maybe it was not complete download or something similar like that. Did you check the md5sum?
Sent from my CM10.1 Wonder using xda premium
Click to expand...
Click to collapse
Maybe..
I haven't check the md5sum yet..
I'll try download it again..
thanks for the reply