[Q] Error mounting sd card in CWM - Samsung Galaxy S (4G Model)

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

Related

[Q] NexusS (i9020T) hard bricked, at which step did I go wrong?

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.

Htc one S. Time of the month.

Hi need a bit of help with this one if possible.
start the top..
went to flash leedroids rom..flashed boot image but forgot to pull rom over.
so had various issues getting over in the end had to mess around with recoverys and totally wipe my sd for it to be recognized.
so i solved all this then..now the issue is..of everything i push over..only one rom boots up and installs fine..and that is a cm9 test without sd mounting..so it solves nothing.
any ideas of how to get a rom on there where i can mount the sd..download a rom and put it on..
ill be honest..htc+internal sd card=not happy
ive pushed leedroids..virtuous..utbs rom but nothing.
i tried aokp but it didnt even push.
with these also some get corrupted by a protocol failure..
many questions. currently has cm9 on..but no mounting..so great
Did you already try a factory reset after flashing the stock recovery (e.g. from MoDaCo)?
-
Hi rootrider, yeah i followed a post i found..
basically i used the one click toolkit to flash the stock recovery..then cleared storage and all data etc.then installed clockwork back..it doesnt like the working roms though
cm9 is the only one i can boot up..at least it sees the sd card again in clockwork though
Had your problem as well... I don't remember exactly what I did to get out among many other things (sh..).
Had some trouble as well flashing stock recovery with the one click tool kit. It didn't work as expected. So I did it with adb. Just keep on trying, there is a way out.
-
My next course of action is, to flash the stock recovery, clear everything,reinstall clockwork then install aokp..if its something with the type of rom.maybe that will work..i can mount..get a rom on the sd and resume business as usual..
debatebale whether itll work lol
If this doesn't help get Thor's hammer and flash your appropriate RUU (again).
Easiest method would be to run an RUU and start over again. I see your vodafone UK so try this one
http://dl.dropbox.com/u/69014495/RU..._2_10.23.31501S.10L_release_258386_signed.exe
It also includes the new radio too !
Just relock bootloader before running it, After its finished unlock and fastboot flash cwm..
easy peasy !!
--
thanks people, im running leedroids rom now, seemed my issue was is after pushing the file over i just tried to install immediatley..after a couple of reboots just for the hell of it,untouchables rom started installing...phew..
sadly all my sd contents have gone..very dissapointed with the sd card business!
still least its working again!
thankfully azzle didnt need to go back to ruu
Aye, captain. Glad to read this.

Jellybean update stuck

Hi Guys,
I have been searching for a solution to my problem, but have come up empty handed so far, thought i would post to see if anyone can help me here.
I have a Xoom EU 3G, it currently has a EOS ICS Rom on it.
I am trying to flash it to the EOS Jellybean ROM.
I am copying the rom, and gapps to the SD card, and rebooting to the clockworkmod Recovery V3.2.0.0, and perform the wipes and resets as the guides tell you.
I then select the install from zip option, and choose the new rom, how ever it kinda get stuck on "opening update package" spends ages there, and eventually goes back to the recovery screen. I thought it finished, so i installed the GAPPs, but after rebooting it was still running ICS..... any ideas where I am going wrong?
Thanks
Try flashing eos recovery and then try it
i'll see if I can get that recovery on it, i was trying all sorts of things yesterday, and now the tablet is stuck on the motorola logo :/
I may need to use the computer to flash it now
Well I managed to change the recovery rom to the EOS recovery touchrom, and i downloaded the nightley 101 onto my sd card, but when i go on the step install from SD card it still get stuck on opening update package..... i left it for over a hour and eventually it just returns to the main menu, and doesn't flash it... i'm a bit lost on this.... any ideas?
Must be a bad download, try downloading a new one.
Sent from my Xoom using xda premium
well thats what I thought, so i tried the 99, 100, and 101 nightly, and no luck with any of them, the md5 check is ok too... so confused with this one!
hi guys, finally managed to sort this issue, turns out my SD card was on its way out, it still worked, but i was trying to copy the update off it, and it gave me a cyclic error, so changed the card, and now I am running Jelly bean
I do have just 1 more question tho, I installed the GAPPS, however it did not install google maps for me... is this normal? also when i try install maps manually, it tells me its not available for my country :S but i have it on my phone, and had it on my xoom before.... any ideas on this one?
BTW i live in malta

Status 7 Symlinks Fail

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.

[Q] Flashed 4G recovery onto 3G phone

Okay.
So, I have tried to UTSE on this and found a thread that directed me to flash a new radio (http://forum.xda-developers.com/showthread.php?t=1116884) which I have done but the fastboot is still not letting my phone respond.
So...
My phone is a GT 19023.
I'd updated to jelly bean awhile ago but was having some serious performance problems and wanted to flash back down to ICS or GB. Of course, the recovery wasn't working so I went to Nexus Hacks and downloaded his recovery files, stupidly I didnt notice it was 4G specific (crespo4g), just that it was for ICS and JB. The recovery seemed to work ok, had the new touchscreen version, but then I tried to install a stock GB ROM from my SD card. At the end it seemed stuck on writing radio. Wasnt doing anything so assumed it was ok to reboot. When it rebooted every process was failing so I tried to do the fastboot flash recovery again and the phone just wouldnt respond.
Tht's where I am at now.
Saw another thread and got directed to the link above to flash the radio.
Did that, used the UCKF1 radio, no problems installed fine but the phone still won't respond to fastboot flash recovery using recovery-clockwork-3.0.2.4-crespo.
Can anyone point me in the right direction PRETTY PLEASE! I'm not a techie guy and its my only phone :crying:
You did a lot wrong here. NEVER DO SOMETHING UNTIL YOU HAVE COMPLETE KNOWLEDGE OF IT
Also you flashed the wrong radio. I would suggest you to stop as where you are right now.
You need to go complete stock first, by flashing the factory image.

Categories

Resources