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 everybody
This is my first post & thread .I'd like to thank all the developers .I'm trying to install the Revolution ROM & I managed to download the rom but failed to download super wipe for it !! I'd like to download the super wipe if link avail.
Thanx :good::highfive:
BTW I forgot to mention that my device is rooted ,shall I unroot it ?
Nobody can answer me :crying:
Here u are: http://www.sendspace.com/file/nzyx1n
Hit thanks if it helped!:good:
So what about rooting or unrooting ?
why unroot
You have to be rooted and have CWM recovery to flash a custom rom mate.
For wiping:
Wipe cache and dalvik cache
Data/factory reset
Format system and cache in mounts and storage.
Skip all the other wipes (also in Aroma installer)
He said he's rooted
Sent from my GT-N7100 using xda app-developers app
Sadly the super wipe script is not working :crying:
A failure message is appearing
Signature verification failed
BRNGTO said:
Sadly the super wipe script is not working :crying:
A failure message is appearing
Signature verification failed
Click to expand...
Click to collapse
Are you sure you are rooted with custom recovery ?
locx said:
Are you sure you are rooted with custom recovery ?
Click to expand...
Click to collapse
It's rooted with toolkit
Anyone can help me with that ?
It works for me. Try to update to the latest cwm
Sent from my GT-N7100 using xda app-developers app
locx said:
Are you sure you are rooted with custom recovery ?
Click to expand...
Click to collapse
Rooted again and the rom installed :victory: on trial :laugh:
I have CWM touch 6.0.2.8. when i am doing Dalvik cache wipe, it tells me
E:unknown volume for path [/sd-ext]
Dalvik Cache Wiped
Does that mean i did not perform Dalvik cache successfully? is there anything i could do to fix it?
Rogers i747m 16GB SDcard inside
thanx in advance.
h3nyr said:
I have CWM touch 6.0.2.8. when i am doing Dalvik cache wipe, it tells me
E:unknown volume for path [/sd-ext]
Dalvik Cache Wiped
Does that mean i did not perform Dalvik cache successfully? is there anything i could do to fix it?
Rogers i747m 16GB SDcard inside
thanx in advance.
Click to expand...
Click to collapse
When you boot into the phone, does it start initializing all your apps? If so, dalvik is being wiped
h3nyr said:
I have CWM touch 6.0.2.8. when i am doing Dalvik cache wipe, it tells me
E:unknown volume for path [/sd-ext]
Dalvik Cache Wiped
Does that mean i did not perform Dalvik cache successfully? is there anything i could do to fix it?
Rogers i747m 16GB SDcard inside
thanx in advance.
Click to expand...
Click to collapse
Happened to me as well. And no if its Giving you a error no matter what it says afterwards isn't actually done. I switched fro CWM to TWRP. Much better ui for a recovery, and it fixed it for me, if you really love CWm im guessing reflash and also reflash cwm as well.
xBeerdroiDx said:
When you boot into the phone, does it start initializing all your apps? If so, dalvik is being wiped
Click to expand...
Click to collapse
After reboot it doesn't initializing all my apps ..... Uh oh
Sent from my SGH-I747 using xda premium
h3nyr said:
After reboot it doesn't initializing all my apps ..... Uh oh
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Try reflashing 6.0.2.8 again or download and flash 6.0.2.3. Might clear the issue
amzi said:
Happened to me as well. And no if its Giving you a error no matter what it says afterwards isn't actually done. I switched fro CWM to TWRP. Much better ui for a recovery, and it fixed it for me, if you really love CWm im guessing reflash and also reflash cwm as well.
Click to expand...
Click to collapse
Is there any compatibility issues with certain ROMs ? I am using task650.
Sent from my SGH-I747 using xda premium
h3nyr said:
Is there any compatibility issues with certain ROMs ? I am using task650.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
No. The only compatability issue you would see would be if your recovery wasn't up to date. Then you would get a status 7 error and it wouldn't flash a rom.
I would reflash recovery within recovery, reboot into recovery and try wiping dalvik again
In recovery mode twrp 2.6.0.0 to be exact. When I wipe caches I get an error that says data/lost+found can't be found and it makes it kind of hard to flash new roms because of this and I'm wondering if there's a fix for this
Sent From My Anakonda-bitten SPH-L710 Using Tapatalk 4 Beta
Shadefactor said:
In recovery mode twrp 2.6.0.0 to be exact. When I wipe caches I get an error that says data/lost+found can't be found and it makes it kind of hard to flash new roms because of this and I'm wondering if there's a fix for this
Sent From My Anakonda-bitten SPH-L710 Using Tapatalk 4 Beta
Click to expand...
Click to collapse
They posted new recoveries in the general section to fix an unrelated problem. Have you tried to format your internal drive? You'll lose stuff, but it may fix your problem
I am getting this message when my phone starts ... "Unfortunately, andriod.process.acore has stopped." after I did a factory reset.
I tried to odin stock but im stuck.
What can I do?
I also got this message in the past. I did a battery pull and haven't gotten it since. I'm surprised that Odin back to stock didn't work.
Sent from my T Mobile Note 3
Heff66 said:
"Unfortunately, andriod.process.acore has stopped." after I did a factory reset.
I tried to odin stock but im stuck.
Click to expand...
Click to collapse
bryanthomas007 said:
I also got this message in the past. I did a battery pull and haven't gotten it since.
Click to expand...
Click to collapse
Just a guess but maybe you need to wipe the cache partition again.
Frank
Frank Westlake said:
Just a guess but maybe you need to wipe the cache partition again.
Frank
Click to expand...
Click to collapse
I got it when I updated to the new update. Wiped cache and dalvik, and all is well now.
Sometimes incorrect GAPPS packages can cause this.