Related
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.
I hope you reply as soon as possible
iam tried to download a zip file from recovery to change the lock screen then i killed the phone
cause i tried many times to open it and every time freeze on the samsung logo
i get to try another ROM many ROMs
but actually its the same
and when iam in the recovery mode
i get this message #
E: canot amount/efs
so
i dont know what i have to do more
to get my phone back
best regards
THE LEGEND L said:
I hope you reply as soon as possible
iam tried to download a zip file from recovery to change the lock screen then i killed the phone
cause i tried many times to open it and every time freeze on the samsung logo
i get to try another ROM many ROMs
but actually its the same
and when iam in the recovery mode
i get this message #
E: canot amount/efs
so
i dont know what i have to do more
to get my phone back
best regards
Click to expand...
Click to collapse
Hey Did you try To Flash An official firmware in download mode???
THE LEGEND L said:
I hope you reply as soon as possible
iam tried to download a zip file from recovery to change the lock screen then i killed the phone
cause i tried many times to open it and every time freeze on the samsung logo
i get to try another ROM many ROMs
but actually its the same
and when iam in the recovery mode
i get this message #
E: canot amount/efs
so
i dont know what i have to do more
to get my phone back
best regards
Click to expand...
Click to collapse
Do a factory reset that will get things going.
رد: A very big problem in the Galaxy Note2
Yes i do wipe data and wipe cache
And formot data
Sent from my GT-I9300 using xda premium
try this
THE LEGEND L said:
Yes i do wipe data and wipe cache
And formot data
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
try flashing the stock firmware via odin...this may be your best solution!
Do a factory reset and dalvik and system wipe from recovery.
Then flash stock rom.
Sent from my GT-N7100 using xda app-developers app
I think there's a command line to input through ADB on your pc to your phone, search it. Your best bet is to use toolkit 3.0 for note 2.
Sent from the rabbit hole.
Ok guys, these are modded versions of TDJ's tools to add the preload partition. This should allow you to wipe cache and dalvik without jacking up the symlinks. Also for you guys having issues installing a ROM, the superwipe should fix that. First flash the ROM and reboot (important), then if you are having issues flash the super wipe and then the ROM again. Reboot and you should be good.
Thanks again TDJ!!! You rock bro.
Note to other developers: Feel free to link here from your thread, just don't re-upload them please. Thanks
Everyone else: if you see these uploaded anywhere else please let me know. I have no problem with others linking to these but do not want them uploaded anywhere else.Thanks
Saved. . . . . . .
One more. . . . . .
I'm awesome
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
thx for this, i was annoyed by the preload problem.
Is this for CWM recovery or TWRP as well?
Sent from my SGH-T989 using xda app-developers app
Will work for both.
Thanks Jamison this will solve alot of headaches!
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
euklid said:
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
If on a TMo based 4.1.2 ROM, yes.
Whats the difference between the two downloads?
inpherknow said:
Whats the difference between the two downloads?
Click to expand...
Click to collapse
One is cache/dalvik, superwipe is data/factory reset.
Well before using the scripts ROM would not boot but after super wipe no problems, TWRP 2.5.0.0 :thumbup:
Sent from my SGH-T989 using xda premium
Jamison-does the cache wipe also fix permissions?
Sent from my SGH-T989 using xda app-developers app
Yes it does.
Sent from my dark hole called an office.
I used these scripts installing a ROM and I am having very serious issues. I was using Clockwork and when I rebooted I got stuck in a boot loop. I booted back into recovery but I was not getting fully back into recovery. I tried several times. I finally ODINed back to stock but I can't get the ****ing phone to boot up. It gets toa popup that says ""unfortunatley google partner setup has stopped" and then if I clear that "Google account manager has stopped", "google calender storage has stopped""unfortuantely the process com. android.phone has stopped". ****. I have tried ODIN to 3.5 stock and 4.0.3 both having similar issues.
Anyone have any idea, may have absolutley nothing to do with these scripts but any ideas would be very much appreciated.
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Jamison904 said:
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Click to expand...
Click to collapse
I was running CWM 6.0.2.9 touch and trying to flash the StockWalk ROM. I don't know if you have seen something like this before but it seems like I am totally unable to install any GAPPS even when flashing stock ROM in ODIN. I had flashed the same ROM before attempting to use the scripts, the reason was that I was unable to add my google account (may be a defect in the ROM but others are saying they have not had issue).
*when I say install GAPPS I am just refering to the ones that install on TW ROMS, I am not flashing a GAPPS file of any kind
ArcticFish said:
thx for this, i was annoyed by the preload problem.
Click to expand...
Click to collapse
blackangst said:
If on a TMo based 4.1.2 ROM, yes.
Click to expand...
Click to collapse
OK so I thought I knew enough to not feel like a noob, but here I am with three questions.
First question is what is a "preload problem"?
Second question is this will only work on 4.1.2, and not 4.2.2 (CM 10.1)?
And the third question is will using the original DS wipes mess something up?
T mobiles 4.1.2 loads a preboot partition. Wiping cache with anything but these scripts also wipes these partitions. This script is modified to not do that. No preboot partition = boot loop.
Thus, if you're on anything BUT Tmobiles 4.1.2 you don't need this script and there's no advantage to using it.
Sent from my SGH-T989 using xda app-developers app
Hi guys how come evertime I try to install a custom rom its gives me the Error 7 (Status 7 Error). Have anyone encountered this before? How do I fix it? I tried updating my CWM but still, nothing works, I tried to install Cyanogenmod 10.1 and DarthStalker but it gives me that error. Help please, Thanks in advance :thumbup:
What version of CWM are you using? Number, please.
Do you currently have a ROM on the phone? If you go into About phone from the system settings, what phone model does it say you have?
Its says I have SGH-T999
Sent from my SGH-T999 using xda app-developers app
Are you updating CWM with ROM Manager?
Factory reset, wipe cache, and you should be able to install any ROM without any issues.
Sent from my SGH-T999 using xda app-developers app
Yes I updated my CWM using Rom Manager
Sent from my SGH-T999 using xda app-developers app
I've had this happen many many times. Check the MD5. Its more than likely a bad download. Try re downloading it again.
Try transferring the download from PC to your phone. And try to flash again.
Sent from my SGH-T999 running Chihuahua v1 ROM
re: error 7 issues
CooLoL1999 said:
Hi guys how come evertime I try to install a custom rom its gives me the Error 7 (Status 7 Error). Have anyone encountered this before? How do I fix it? I tried updating my CWM but still, nothing works, I tried to install Cyanogenmod 10.1 and DarthStalker but it gives me that error. Help please, Thanks in advance :thumbup:
Click to expand...
Click to collapse
Most likely you tried to flash some rom which was not 100% compatible with your phone.
If you can get into CWM or TWRP recovery just do a factory reset/wipe cache/wipe dalvik cache.
Do NOT wipe or format SYSTEM . This should allow your phone to boot completly.
Be sure NOT to try flashing the same rom which gave you the error 7.
If you are still having problems then continue reading...
If you have a cwm/twrp backup (nandroid) of your previous rom go back into cwm or twrp
and restore your nandroid backup.
If you don't have a nandroid backup but you do have a proper zip file custom rom saved to your sdcard
then you can flash the rom making sure you first do a factory reset/wipe cache/dalvik and system.
After that you can start over again but be sure to make a nandroid backup first.
If you still have problems after doing the above you will need to ODIN flash the stock-rooted
Samsung Galaxy S3 T999 Jellybean v4.1.1 firmware.
P.S. You would NEVER get an ERROR 7 if you would only flash stock based "Samsung Galaxy S3 T999 Jellybean v4.1.1 custom roms"
instead of those CM/AOKP/AOSP or Ported roms.
Good Luck!
CooLoL1999 said:
Hi guys how come evertime I try to install a custom rom its gives me the Error 7 (Status 7 Error). Have anyone encountered this before? How do I fix it? I tried updating my CWM but still, nothing works, I tried to install Cyanogenmod 10.1 and DarthStalker but it gives me that error. Help please, Thanks in advance :thumbup:
Click to expand...
Click to collapse
First of all, make sure that you redownload the ROM, check that the MD5's match, and that you are indeed on the latest CWM recovery.
Secondly, I've heard of these status 7 errors, even when on the latest CWM recovery. There's times when installing certain ROMs where these errors occur, which usually happens when the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing and this portion of the script are called “asserts”. with this it prevents you from accidentally flashing a ROM intended for a different model.
Normally you can fix the issue by installing TWRP recovery but there's another possible solution for this if the TWRP method doesn't solve it but take some serious precaution. You need to be very careful and do this at your own risk.
Follow this step by step guide
http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android/
Following this will remove the asserts thus removing protection upon flashing the wrong ROM. Do if you choose to follow this make absolutely sure that the ROM you're flashing is for the T999.
Sent from my SGH-T999 using xda premium
---------- Post added at 01:57 AM ---------- Previous post was at 01:40 AM ----------
Status 7 errors can very well still occur through CWM recovery on stock based ROMs.. It mostly all depends on the ROMs updater script and if the dev accidentally made an error within that, which is why the asserts would normally correct that error by forcing the ROM to be flashed regardless.
Sent from my SGH-T999 using xda premium
Everyone, Thanks for helping me out, I flash back to stock firmware, I found out that I rooted my phone the wrong way (Qbking's Video). I tried rerooting but I used a different method and updated CWM, now works completely fine, Thanks for all your help!! :thumbup::thumbup:
Sent from my SGH-T999 using xda app-developers app
Hi all, this is my first post here. Unfortunately it is an issue, but I have been flashing roms for a while now.
So last night after flashing Ditto Note for my note 2 on att, I decided I didn't like it and wanted to revert back to my previous rom. However, when I am trying to format data in recovery it just hangs. I have tried both on CWM and TWRP... twrp says: "error too many open files"
And obviously this issue has caused many other issues for me such as being unable to flash anything else as anything else will just get stuck on the bootscreen.
I remember somewhere that there is a flashable zip that will specifically format everything for you, but I dont remember what this was called.
But any help would be great
Flashed stock 4.3 via Odin and it still doesn't boot past samsung screen
Just tried using zoot's super wipe
http://forum.xda-developers.com/showthread.php?t=1983489
and once again it is stuck on data wipe
xsnes said:
Hi all, this is my first post here. Unfortunately it is an issue, but I have been flashing roms for a while now.
So last night after flashing Ditto Note for my note 2 on att, I decided I didn't like it and wanted to revert back to my previous rom. However, when I am trying to format data in recovery it just hangs. I have tried both on CWM and TWRP... twrp says: "error too many open files"
And obviously this issue has caused many other issues for me such as being unable to flash anything else as anything else will just get stuck on the bootscreen.
I remember somewhere that there is a flashable zip that will specifically format everything for you, but I dont remember what this was called.
But any help would be great
Flashed stock 4.3 via Odin and it still doesn't boot past samsung screen
Click to expand...
Click to collapse
Did you make a backup or anything you can try to just do to maybe fix the bad files that didn't wanna delete
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Yes I have tried doing a restore.
IN specifics this is the exact log I am getting from as soon as i start it up TWRP:
E:error opening '/data/data/com.google.android.marvin.talkback////////////////
//////////////////////
////////////////////
////////////////////
//////////////////
//////////////////
////////////////
//////////////////
////////
////
//
//
/
E: error: Too many open files
I tried deleting this folder from twrp file manager and the phone just reboots
In twrp try just deleting just that file maybe if you haven't already
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
I've tried TWRP and Aroma file manager now. Aroma file manager detected over 998 files in that folder until it froze... I've also tried moving the folder into my external SD card in which case there also happens to be 335 files until it froze as well.
How does a rom manage to install thousands of blank folders??
Are you able to flash a rom or you stuck at the recovery?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
terpin32 said:
Are you able to flash a rom or you stuck at the recovery?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes. I have flashed and booted into a Rom a couple times while having this 'data wipe' issue. However i feel like it is the luck of the draw because sometimes it boots, other times it hangs at the samsung screen lol
Should I go ahead and try to install a rom?
Is the "wipe" command issued by the recovery simply "rm -rf" or an actual format command with mkfs.ext4?
Darkshado said:
Is the "wipe" command issued by the recovery simply "rm -rf" or an actual format command with mkfs.ext4?
Click to expand...
Click to collapse
The logs say that it uses "make_ext4fs function"
Can I just go through the data folder with file explorer and delete everything else there?
OR is there another super wipe style zip that I don't know about ?
It probably won't let you
Sent from my GT-N7105 using XDA Premium 4 mobile app
solved
Issue has been solved. Wiped phone with a script? (i think) from a flashable zip contained from ANDROID HD rom for the note 2
for those that might need it: http://forum.xda-developers.com/showthread.php?t=2040941 (3rd post down)
This script does not use AROMA which has crashed for me everytime I tried to wipe with it. Really useful
Now currently running aosp rom cause I hate the new TW in 4.3 and 4.4 lol