Galaxy GIO S5660 - Can't access csc - Samsung Galaxy Gio GT-S5660

Hello,
I have a Galaxy Gio S5660 and I kinda soft bricked it. I've got it used, since my older phone got wrecked in work, so I bought this from a collegaue of mine - he gave it to me for almost free since I fixed his other phone. It had TWRP previously, and I think the internal memory was extended with Link2Sd. But SD card wasn't in the deal, also it had the original Android system on it.
I used ODIN to update Firmware, installed CWM and after that I tried to install CM 7 on it. I failed, since then I can only start in recovery mode and I'm kinda stuck with this problem of mine.
I'm not even sure that I am root, since when I want to run the Update.zip it gives back only error. I cannot wipe, and this is my major concern. When I want to use wipe data/format the phone sipmly freezes. At times I've got some hint like the screen changes to some colorful ant war but I left it to "work" on it for a whole night without results. I have tried to use the advanced options in CWM like mount /data - crash. Format /data crash...
No matter which Firmware I use with any "known to be working'" Rom I cannot move forward since I cannot format. When I udpate the firmware the original 3e recovery gives back an error message "cannot access csc" :S
I wasn't able to install any working root zip. Can anyone help me with this one?

Update
Still no luck, so looking forward to get some advice from tech wizzes

Bump, anyone please?
Show log from CWM:
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=gt-s5660v
ro.revision=10
init.svc.recovery=running
init.svc.adbd=running

So, no one seems to be interested but I'm not giving up hope yet.
I'm trough this csc problem and I found the real source of all my problems, the only problem that I do not know how to get around it....
Got CWM up and running, I tried to wipe data, format data or wipe dalvik cache but the phone crashes, restarts itself.
After connecting with ADB shell I tried to use recovery --wipe_data without luck, as above the phone restarted.
Flashed back official ROM, used ADB again - no root permission. Installing CWM and rooting - no luck here from now on I cannot su in shell.
So far I know that I cannot use Fastboot to reflash the whole system, so is there any possible way to restore my corrupted /data?
I think if I could wipe data I could restore my system and such but currently I'm sitting here tearing out my hair.
Any help would be much apprectiated!

Related

information on any Clockwork recovery that can load via extSD

USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
So far i got ahold of the previous Clockwork before the touch came out but it doesnt have options for external and internal im still allowed to mount externalSD card but whats the for if you cannot ADB with clockwork nor install from exernal SD?
Thanks for your time guys
xgp0006 said:
USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
Click to expand...
Click to collapse
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
B-Naughty said:
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
Click to expand...
Click to collapse
xgp0006 said:
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
Click to expand...
Click to collapse
If you're already running CWM, try the wiping and fix permissions before ODIN flash to stock with the TMobile image

[Q] DINC won't clear user data, after using every trick I know

So, I recently acquired an Incredible, the second one I've owned. The first one I rooted, turned S-off and installed CM7 with zero difficulties, after that I rooted/flashed my Xperia Play CDMA with all the issues that accompany that device. (after the ease with which I modded my first DINC, the hoops through which I had to jump to unlock my bootloader blew my mind)
This DINC, though, refuses to clear user data. Even after multiple wipes via CWM, and multiple updates using the PB31IMG method, user data remains. Attmepts to preform a factory reset via HBOOT result in a balck screen with a red triangle and exclamation point.
I tried to install MIUI, thinking maybe a fresh rom would fix it, but it gets stuck at the room splash screen.
I've even tried recovering a clean CM7 install from my old incredible, but it gets stuck in a bootloop at the rom splash, same story trying to flash the .zip in recovery.
I've seen a few threads that deal with a few of these symptoms, but not the issue as a whole
Thanks in advance for any answers you guys have!
Cheers
I found a solution, finally. Admittedly, it was a bit drastic, but it worked, nonetheless.
I ended up disassembling both DIncs and putting the motherboard of the working device (with the smashed screen) into the device that was unable to format /data.
It was a bit touch and go for a bit, but my new DIY refubished phone is up and running.
Thanks for the help guys!
What error do you get? Can you upload the logs from /cache/ recovery after trying to wipe?
Sent from my Galaxy Nexus using Tapatalk 2
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
mattdubuc said:
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
Click to expand...
Click to collapse
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
tiny4579 said:
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
The red triangle happens when you try to do a factory reset from hboot wile on cwm recovery. If you really need to do a factory reset, you will need to flash to the stock recovery first. http://dinc.does-it.net/Recoveries/Stock_4.08.605.15/PB31IMG.zip Then if it works or even if not flash back to cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.
The weird thing is, that even after flashing PBG31IMG via HBOOT I'm retaining all the previous user data. I've tried formatting the internal drive, using a few different versions of the image, even manual formatting of /data via CWM, which only gives me an error. the same error as when I tried to restore a nandroid from my functioning DINC.
tiny4579 said:
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
mattdubuc said:
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
Click to expand...
Click to collapse
That should be fine. Try to wipe data in cwm again just so it logs it.
Sent from my Galaxy Nexus using Tapatalk 2
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
zslashy said:
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
Click to expand...
Click to collapse
Same error if you flash stock GB sense and factory reset from recovery? You have the errors when booting and the apps are still there?
Sent from my Nexus 7 using Tapatalk 2
Thank you for reply, I solved reset issue by installing Amon Ra recovery. But the problem with apps still exists, it looks like system is restoring back up after reboot, I can do everything with system but after reboot it's like it was before with no changes made. Additionally, it seems that the problem is with emmc, just because when I delete EVERYTHING on it, after restart all files appear again!
I'm also getting an error when I try to manually format the data partition under >mounts and storage in CWM, I'm assuming that may be to blame for retained user data?
When I run show log after running only a manual /data format it displays:
6 black groups
32768 blocks per group. 32768 fragments per group
8112 inodes per group
superblock backups stored on blocks:
32768. 98304. 163840
The filesystem already has a journal,
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Failure while running mke2fs
Error formatting /data!
mtd: succesfully wrote block at 0
I:Set boot command ""
I have no idea what that means really, or even if it's pertinent.
I had to remove the user info (owner data, phone number, etc) from my inc after canceling my contract with verizon. After about 25 different attempts to wipe it, I finally found something that worked (at least for me)
Tried running the RUU, could not reboot into HBOOT (version error)
Tried the RUU again, this time starting it after manually booting the phone to HBOOT. Got a little farther than before, but still errored out. Did not work. Disconnected phone, pulled battery, rebooted to HBOOT.
Factory reset in HBOOT got me stuck on the stock recovery screen. Battery pulled, could not boot.
Flashed CWM in HBOOT (by renaming to PB31IMG.zip), was able to get into CWM recovery.
Tried to flash the 2nd GB OTA in CWM, did not take. Every option I clicked in CWM gave me about 7 errors after sitting on the logo for a moment. Battery pull, reboot. Boots into CM9. >.<
Booted to my rom, saw about 300 force closes. Tried to reflash CWM from Rom Manager, got a bunch of force closes. Updated Rom Manager from market, reflashed CWM, and this time it worked.
Rebooted to CWM, wipe data/cache/dalvik, reboot.
This time I booted in CM9, but to the initial ICS set up (click next to begin, wireframe pic of Andy)
After skipping thru initial setup, I checked Settings>About Phone>Status. My phone number was removed, network is Unknown, and all my data was removed. Activation prompt appears on each boot.
Not sure if this will help, but worth a try. I think that the HBOOT factory reset is what cleared my data, and then I just needed to fix CWM so I could get back to a working ROM.
Yeah that's what I did in june except I just got service on mine but I would think that would help getting your data out forever. If that does not work I wouldn't know what to tell u besides grab a magnet. Lol
Sent from my Droid Incredible using xda premium

[Q] Soft bricked my encrypted phone and I can't factory restore or flash new ROM

While installing the most recent update to my encrypted SG3-L710, the phone restarted and while booting up remained stuck on the blue/white Samsung logo.
-After removing the battery and attempting to get around this several times it appeared that the update had soft-bricked my phone. I was never prompted to put in my passcode to undo the encryption.
-I am able to access CWM Recovery and, being that the only significant thing I would lose are my contacts so I attempted to perform a factory restore which was unsuccessful. It appeared the error indicated it was the /sd_card and /data folders posing the problem.
-I attempted to mount and unmount the /sd_card and /data folders which was unsuccessful, formating them also did not work.
-I downloaded Odin and the PIT file as my last hope. I attempted to flash the stock ROM to the phone and hopefully wipe the old ROM from the system. Odin also encountered problems with the /sd_card and /data and was not able to progress past that point. Now I am attempting it a second time to obtain the specifics and it's stuck on "<ID:0/004> Send lock information...".
Any ideas on how to be able to bypass the encryption and wipe my phone so I can flash a new ROM on this?
I've been working on this problem for almost two days now and I would greatly prefer not having to send my phone into Samsung and spend $100 to do this for me! Thanks ahead of time, bear in mind I'm new to this and might be a bit slow.

E:failed to mount /efs (Invalid argument), Did I brick my tablet?

I bought a new never used Tab 3 for the intended purpose of using it as a universal remote. I wanted to strip it down and started right away with installing custom recovery, or at least I tried. No matter what I did I was not able to get Odin to properly load TWRP. It went through all the steps but I was not able to get into recovery other than stock.
Fast forward to the next day, I finally get it to work and somewhere in this process I somehow deleted or unmounted (I really am not sure) my efs folder/partition. If I try to reset deleting all cache and wiping everything including pulling the battery for a few minutes and flashing the stock ROM again I get hung up at the "SAMSUNG' logo. I have tried several ROMs and even tried using Odin to flash a new pit file with I found HERE. When I load both the pit file and my ROM into Odin it eventually says 'FAIL'. I can flash ROMs all day with no issue.
I can only assume that the error I am getting in recovery that says E:failed to mount /efs (Invalid argument) is my issue.
Adb is not really an option for me since I have little to none, more like none at all knowledge of using it. I assume since I have flashed several tries that USB Debugging is not enabled anyway and isn't enabling it key to using ADB anyway?
I have been at this for 2 full days searching everywhere and trying everything I see. I am at a loss and hate to think this new Tab is already junk.
Any help would be greatly appreciated!
The EMCC or something like that requires replacement
andynroid said:
The EMCC or something like that requires replacement
Click to expand...
Click to collapse
So I should junk it then? I only paid $80 for this Tab.
One trial you may try to flash a Cyanogenmod based ROM see if it can write out the partitions else if no luck time to replace that item as mentioned
I have tried flashing CM and still the same issues.
I have since found out what my issue is (or at least 99% sure), I somehow wiped out my efs partition completely. So running a new pit file with Odin does nothing because the partition is gone.
This is fixable and easy for someone who knows shell, but I don't. So now I am trying to figure it out. It's a matter of pushing the 6 following files to the phone using the adb push [file] /sbin/ command using adb which I have done, now I need to figure out the rest.
e2fsck
mke2fs
parted
resize2fs
sdparted
tune2fs
T
you can't do that in the way you think, it requires disassembling the recovery image, making modifications and repacking then reflashing the image.
If you are using an older recovery, namely twrp, install a newer recovery , check @nels83 's thread for a "modern" twrp build.
You can also try one of my philz builds.
Being as you have been abusing Odin, you may actually have damaged your tab.
BUT if you are connecting to wifi without a problem then it's unlikely that you have damaged your efs partition. It's more likely an error with the recovery build you are using, probably in the fstab.
m

How to repair Wileyfox Swift when I can get into TWRP but not bootloader

Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.

Categories

Resources