I've looked at multiple forums, not just galaxy 3, and I can't find an answer to this problem. I keep getting the "symlinks: some symlinks fail - status 7" error when I try to flash certain roms. First of all, I'm rooted and unlocked. I have flashed CM10 and Synergy before (couple weeks ago,) but now I can't install any of the synergy nightlies or JB roms. I've tried to install from internal and external sd, and failed on both. I've flashed CWM touch and non touch 6.0.1.2 as well as twrp with the same error message. I've flashed the cwm recoveries through Rom Manager and Odin with no change. I loaded the latest Modem through Odin to see if that would fix the problem somehow, and that didn't work either. (Wasn't expecting it too.) Has anyone run into this issue and come out with a fix? I think I've done some pretty in depth research on this, but maybe I've missed something. I don't want to create a brick if someone has a fix. Thanks for the help.
I just bought a S3 last night. I immediately went through all of the steps for root,unlock,and tried to load a custom rom. After about 5 hours worth of research and trial and error I gave up and am probably going to return it for something different. No one has answers for this issue, but it seems a decent amount of people are getting this. I believe it has something to do with the phones memory / storage. Be sure to share anything that might fix this issue.
Related
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
This has happened to me several times and I am seeing that other people are running into this problem with no fix found.
Everytime I try to install CM10.2 onto my xt926 I can never get past the unlocked bootloader warning screen after a reboot. I can still access CWM which is the recovery I'm using. I have tried clearing cache, data, factory reset, fixing permissions, reflashing the rom. The only way to get a working phone again is to flash stock 4.1.2 using RSD.
Then I remembered seeing an article a while ago saying that their were two versions of an OTA update for Razr HDs because for some reason their were slight differences between some phones, hardware wise.
Could this be the reason for these random phones not accepting CM10.2 installs?
Also if anyone has any ideas to get past this. I read someone had luck toggling bluetooth on and off for some reason but it didn't help me. I'm at a loss here and would love to play with Android 4.3 but I guess its just not in the cards...
ive got the same problem to i finally decided to get rid of safestrap and unlock my phone. now im stuck on stock rom because no roms will work after a reboot. theres two diferent stock 4.1.2 firmware files. one says mr4 the other one says mr2 anyone know the diference?
Not sure. I just use the RazrHD Utility 1.21 for that, its a lot easier. Also I have heard that 10.1 may work for us, just not 10.2 for whatever reason
Im sorry if there is a thread for this already(if so plz direct), but Im having some trouble flashing CM onto my phone. I unlocked it, rooted it, and flashed CWM(then later on TWRP) without any issues. but as soon as I tried flashing CM onto it, it kept giving me errors, generally error 7, which i looked up and found a workaround by deleting the asserts out of the script on the ROM. but still no luck, even after doing this I still get errors everytime. Im pretty stumped and not sure what else to do. any help would be MUCH appreciated!
Okay so I've been all over this site and linked to many other articles to proceed and hope to fix my issue but nothing seems to be working for me. To get you guys up to speed it's a SGH-T959V and I started out with having jelly bean 4.0 on it then upgraded to 4.2.2 which I occurred an issue with that and had to revert to getting gingerbread flashed back on. It's been a little while since I've done so and kinda forgot how I did it. I've read about using odin and heimdall but no luck getting my phone to connect with either of those programs.
Recently upgraded to 4.4.2 slimkat which was working good (still some bugs, since it's weekly) and had TWRP recovery on it. Problem started as I was starting the process to flash the new update of 4.4.2 and I created a back up and recovery for it prior to flash but now its gone. During the flash of the new update it had occurred some error and now went to Semaphore CWM Recovery v6.0.4.5 and has a bunch of errors to it and I cant even format or mount an sd card. I've tried using a couple different sd cards same issues. I can boot into download mode no issues.
Anyone be able to help me out? I am pretty stumped on this one and have tried many things to get it to work. Also are there any programs I could use besides odin and heimdall to flash a different version of CWM or TWRP via usb?
Thanks guys let me know if I left anything out or if you have questions to help me out better.
Hey guys, here are a couple of pictures of what it looks like while in CWM and what its saying.
Hey guys never mind, I already figured out what I was doing wrong. All I needed to do what open a file I downloaded in this thread to get it back to stock gingerbread. Now I am going to do some more flashing to get it back to 4.4.2 slimkat. Thanks
Hello, using my husband's old skyrocket as main driver, pleasantly surprised with how much I'm enjoying using it...thought there'd be more lag etc. And was thrilled to find continued development. (Couldn't find my old sign in info BTW) Anyway apparently I'd rooted and unlocked it and put a gingerbread debloated stock rom on it when he first got it, as that was there...tried candy 5, loved, but needed more app space. Tried app2sd and just messed that up...Tried cyanogen, read instructions, did things a little differently (unintentionally) at first, somehow not registering the fact that the official twrp was for virtually repartitioning, tried to repartition it in the modified version, of course it didn't work, finally gave up and flashed ROM anyway and gapps (tried both nano and pico from link. )
I'm not sure how but it did install and basically seemed tp work, the only issue seemed to be keyboard force closing and later the browser and root issues. I wondered if something I had done originally with phone contributed to why it installed if it shouldn't have been able to. MMS (cricket) won't work on this or candy5, tried several radios and apns.
Anyway I saw what I did wrong with twrps, figured that would fix things, virtually partitioned correctly, seemed to have same issues and intact kept adding more... tried many times: wiping reformatting, clean install, dirty, reflashing whatever...it just seemed worse every time...everything force closing including settings.
I have no clue what happened, what I was doing wrong, gapps I read should have a script added to the ROM to prevent the force closing, and Im assuming it is there....also though a couple times offered to have rooted in twrp it never seemed to do it, never worked right if I tried anything manually instead, caused more shutdowns. Something abt pit file in instrutions makes me wonder if something i had done before could cause issues? Cant remember what that was specifically though. Thanks! And I apologize if this is hard to follow or or makes no sense. Probably. BC it really doesn't haha....BTW I did read anything I could find so if I a missed something obvious I apologize.
T.Leela said:
Hello, using my husband's old skyrocket as main driver, pleasantly surprised with how much I'm enjoying using it...thought there'd be more lag etc. And was thrilled to find continued development. (Couldn't find my old sign in info BTW) Anyway apparently I'd rooted and unlocked it and put a gingerbread debloated stock rom on it when he first got it, as that was there...tried candy 5, loved, but needed more app space. Tried app2sd and just messed that up...Tried cyanogen, read instructions, did things a little differently (unintentionally) at first, somehow not registering the fact that the official twrp was for virtually repartitioning, tried to repartition it in the modified version, of course it didn't work, finally gave up and flashed ROM anyway and gapps (tried both nano and pico from link. )
I'm not sure how but it did install and basically seemed tp work, the only issue seemed to be keyboard force closing and later the browser and root issues. I wondered if something I had done originally with phone contributed to why it installed if it shouldn't have been able to. MMS (cricket) won't work on this or candy5, tried several radios and apns.
Anyway I saw what I did wrong with twrps, figured that would fix things, virtually partitioned correctly, seemed to have same issues and intact kept adding more... tried many times: wiping reformatting, clean install, dirty, reflashing whatever...it just seemed worse every time...everything force closing including settings.
I have no clue what happened, what I was doing wrong, gapps I read should have a script added to the ROM to prevent the force closing, and Im assuming it is there....also though a couple times offered to have rooted in twrp it never seemed to do it, never worked right if I tried anything manually instead, caused more shutdowns. Something abt pit file in instrutions makes me wonder if something i had done before could cause issues? Cant remember what that was specifically though. Thanks! And I apologize if this is hard to follow or or makes no sense. Probably. BC it really doesn't haha....BTW I did read anything I could find so if I a missed something obvious I apologize.
Click to expand...
Click to collapse
You need to flash stock GApps. Dunno why, but for some reason it just works.
And with the repartition, you have more than enough space for that.
By the way, the Settings FCs are from a bad update. Flash 12/6 and you're good.
Sent from my SGH-I727 using Tapatalk