Develop Bugs

[Q] (status 7) some symlinks failed when installing ROMs.

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.

[Q] Doing something wrong trying to flash JB

I've installed ROMs before so I'm not a complete noob, but I'm clearly doing something wrong and would like some help.
I've tried installing 3 different JB ROMs (Kobridge tweaked FL04, Jellyverse0.3, JB Black Bean) and everytime I boot up into the Sprint animation and it hangs every single time at the big 4G. I'm coming from BluKuban which I return to every time after flashing EL29 direct boot through pc Odin.
This is what I've been doing:
Installed EL29 direct boot or EL26 stock
cleared cache, davlik and run Format_All_X2
Installed JB modem
installed ROM
run Format All X2 again
A couple of files might be different depending on the ROM instructions, but that's what I've been doing.
Any ideas what I'm doing wrong?

flamand said:
I've installed ROMs before so I'm not a complete noob, but I'm clearly doing something wrong and would like some help.
I've tried installing 3 different JB ROMs (Kobridge tweaked FL04, Jellyverse0.3, JB Black Bean) and everytime I boot up into the Sprint animation and it hangs every single time at the big 4G. I'm coming from BluKuban which I return to every time after flashing EL29 direct boot through pc Odin.
This is what I've been doing:
Installed EL29 direct boot or EL26 stock
cleared cache, davlik and run Format_All_X2
Installed JB modem
installed ROM
run Format All X2 again
A couple of files might be different depending on the ROM instructions, but that's what I've been doing.
Any ideas what I'm doing wrong?
Click to expand...
Click to collapse
Don't flash format all zip after flashing rom zip.
You are wiping system right after flashing rom so there is no system and thus you don't boot.
Sent from my SPH-D710 using xda app-developers app

Thanks for the suggestion, but format_all_x2.zip just wipes data, cache and dalvik, doesn't it? I use it all the time when reflashing Ruj's BluKuban.
BluesRulez said:
Don't flash format all zip after flashing rom zip.
You are wiping system right after flashing rom so there is no system and thus you don't boot.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse

flamand said:
Thanks for the suggestion, but format_all_x2.zip just wipes data, cache and dalvik, doesn't it? I use it all the time when reflashing Ruj's BluKuban.
Click to expand...
Click to collapse
It wipes system, not dalvik.

flamand said:
Thanks for the suggestion, but format_all_x2.zip just wipes data, cache and dalvik, doesn't it? I use it all the time when reflashing Ruj's BluKuban.
Click to expand...
Click to collapse
Its not a suggestion. Its your FIX. It wipes system. I hope you are not confusing format all x2 zip with modified_format all zip. The modified zip wipes only the caches.
As such there is NO need to wipe after flashing the ROM..

Are you following the directions on the OP of each ROM?
If not... do it, that is how you fix your problem.
Sent from my SPH-D710 using xda premium

Yes I am, unless I'm misunderstanding something. That list is what seemed to be in common to all three.
I'll try to do it again tomorrow when I have a few hours.
Mattix724 said:
Are you following the directions on the OP of each ROM?
If not... do it, that is how you fix your problem.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse

[Solved] Flashed cyanogenmod, stuck on boot screen

Hey guys, I'm really new to rooting, flashing roms, and Android in general (I've used iOS since 2007 until a month ago... please have mercy on my soul). I have an AT&T GN2 that I would like to remove the bloatware from, hence why I began investigating rooting, but it's snowballed into my desire to try out some of the amazing ROMs that the developers here have produced. Since the Note 2 uses the Exynos 4, I rooted using the ExynosAbuse exploit and downloaded Titanium Backup to freeze the AT&T apps. So far, so good.
However, I am wanting to get into how to flash custom ROMs, like CyanogenMod, so I downloaded the CWM RomManager and flashed the CWM Recovery. I downloaded the CyanogenMod 10.1 release for the i317 model (here: http://forum.xda-developers.com/showthread.php?t=2024495) and the latest gApps package (for 4.2.1), and flashed both from CWM RomManager. When it rebooted, it showed the CyanogenMod boot screen, but it appears to be stuck there. I'm not sure what to do at this point, and am hoping I didn't brick my phone. Is there anything I can do at this point?

Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium

Have you changed kernel???
Sent from my MT11i using xda app-developers app

id10terrordfw said:
Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
When I booted into recovery, I got the CWM recovery (which is a good thing, I suppose). I wiped the cache, and then installed the CM 10.1 zip and gApps zip. However, I think I still need to wipe data/factory reset, right?
So, at this point, I've:
1. Rooted the device using Chainfire's ExynosAbuse apk (super easy).
2. Installed RootChecker (success) and TI backup (froze bloatware apps).
3. Downloaded CWM RomManager.
4. Flashed CWM Recovery.
5. Downloaded CM 10.1 port for i317 (the AT&T GN2 model) and the 4.2.1 gApps zips.
6. Chose to install ROM from SD card in RomManager, added both CM 10.1 and gApps, and only selected install (did not wipe cache or user data at this point).
7. Received blue CyanogenMod boot screen... excited... but it remains on the boot screen. Sad face.
8. Removed battery to power the device off, placed battery back in, and then booted into recovery mode (CWM recovery).
9. Installed the CM 10.1 zip and gApps zip from SD, then wiped cache.
10. ???

Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Peleus16 said:
Have you changed kernel???
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
This is a great point, at no point op has mentioned kernel.
Sent from my SAMSUNG-SGH-I317 using xda premium

cdshepherd said:
Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...

NowhereOutThere said:
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...
Click to expand...
Click to collapse
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

cdshepherd said:
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.

NowhereOutThere said:
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.
Click to expand...
Click to collapse
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

cdshepherd said:
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?

NowhereOutThere said:
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?
Click to expand...
Click to collapse
Plug it into your computer and see if you can mount your internal sd. If you can download a new rom to your computer and transfer it to sd. Did you make a backup before flashing?
Im just running stock rooted for now.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Well, I'm downloading CleanROM right now. I also downloaded another cm 10.1 file just in case, perhaps it's because I downloaded it on the mobile Chrome browser that I'm having problems? I also downloaded a kernel from the thread to help with performance. However, if I can't get these on the phone, it doesn't matter. Since I'm on a Mac, I have to use Android File Transfer, and it isn't registering my phone, unfortunately. I may have to go out and buy a cheap SD card and throw the files on there. It may not hurt to have one around, anyways.

Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

cdshepherd said:
Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
No... I thought that a backup of the original ROM was made when flashing CWM recovery, but I am a noob and that did not happen. Unfortunately, the browser doesn't even work! So I cannot text myself the link for the download. I should be able to flash a zip file from a micro sdhc, right?

Flash the right GAPPS, the crashing keyboard is a symptom of incorrect GAPPS. The December one is for 4.2.1 only, which is what CM10.1 is based on. Make sure you flash the right GAPPS with the right CM version.
Sent from my GT-N7105 using xda premium

The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs

ManelScout4Life said:
The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs
Click to expand...
Click to collapse
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.

Just grab goo manager from the market and dl the correct gapps to your phone. Either that or use your phones browser. No need for a pc. Boot in recovery, wipe cache and dalvik and flash correct gapps. Should be gtg.
Edit: just saw your browser isn't working. Goo manager's your best bet. Could always try another browser from the market as well. Good luck.

NowhereOutThere said:
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.
Click to expand...
Click to collapse
While in recovery plug usb into computer (make sure drivers are installed) in recovery menu navigate to mount usb storage. See if that works
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

[Q] Don't Understand

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

[Q] Can't flash the pa 4.4 gapps. Help!

I just recently tried to flash Omni Rom's new 4.4 kitkat rom. I manage to flash the rom, but everytime I try to flash the new pa 4.4 gapps, it doesn't go through. I've done factory reset, wipe cache, wipe dalvik cache (also tried without wiping dalvik), using triangle away to reset the counter, tried updating ClockWorkMod, and even tried to flash pa 4.3 gapps, but nothing seems to work. It always brings up the (files name) "bad". Anyone know what I can do to get it to go through or a possible alternative 4.4 gapps file i could try? Link to the Omni Rom thread is below.
Using the T-Mobile Note 2 (SGH-T889)
Using ClockWorkMod with the latest version (6.0.4.3)
Currently Have cyanogenmod 10.2
Have a 64gb SD card (thought maybe it might have trouble finding the file or something cause it's a big SD card).
http://forum.xda-developers.com/showthread.php?t=2493905

File(s) are on the root directory of your SD? Is it the non-touch version of CWM?
Sent from my SGH-T889 using xda app-developers app

PhxDroid86 said:
File(s) are on the root directory of your SD? Is it the non-touch version of CWM?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
No, it's the touch version of ClockWork, but finally figured out the problem. I guess it was my SD card as i tried a 4gb memory card and it went through without a hitch.