I don't know to much about this kind of things, but I think I bricked my phone. So basically I had an old Samsung Galaxy Y Duos (GT-S6102) laying around I decided to try installing a custom ROM to it. The problem is that I think a flashed the wrong version of CWM and now the phone is stuck at the first boot screen. I'm still able to go back in recovery and when I do that, it says at the bottom that there was an error mounting /system. I tried multiple times wiping the data and the cache, but I had no luck. This is not a great problem because it was just an old phone, but it would be great if it was still fixable. Do you have any suggestions?
Related
New to Droid os. I need help reformating to factory. I recently updated my vibrant to 2.2, with the 2.3 interface i believe? Anyways after the update my phone was working fine. Then things went down hill when i tried to over clock my phone. As it was going into recovery mode I accidently hit reboot. then i tried deleting data, and cache. But when i tried to reinstall things from recovery mode. It told me nothing could be found. So then I tried flashing factory rom with Orin, but it said unable to flash.
Now my phone just turns on all the way to the galaxyS logo and then shuts off. Please any help would be great. I already tried looking through the forums but nothing seems to work.
PLEASE HELP, with a cherry on top
why dont you send for warranty
Hello
Today I was upgrading to the latest starburst rom...this was not the first time I upgraded roms and i did the exact same thing I had done in the past which included wiping data wiping cache wiping dalvik and then flashing....
when i did this and restarted my phone it wouldnt load past the boot screen...after the boot animation the phone stayed black...i repeated steps 1-3 again hoping i just did something wrong...but still nothing
i went back to look at the directions and i say that the developer said to format the system under mounts and storage...in bolded font...i thought maybe thats why it wasnt working so i did just what he said...
now when i load my phone it doesnt load at all and when i open cwm i get a string if e: errors basically saying that it cannot find the drive
if anybody has any advice on how to recover from this I would be extremely greatful
Im having the same problem cant figure out how to fix it.
So I had a problem where I had issues getting a ROM onto my phone after entirely formatting it.
Some kind members helped me to get the phone running again and then getting TWRP 2.6.3.1 on it with the 4.1.2 build.
This was flashed to the phone using Odin after using E-Z Unlock 1.2 to unlock the bootloader and install TWRP 2.6.0.0.
I saw some random issues when I would reboot or power off and on with it locking on the Samsung Galaxy S III logo... but the phone rebooted eventually and I was able to continue use.
Fast forward to today -- for the first time in awhile, my battery fully discharged. When I got home, I plugged in and tried to power on my phone. Locked at the Samsung Galaxy S III logo... EVERY. TIME.
So I go into recovery... I find that the first thing that greets me is a message asking me for a password. This is odd, since I never put a password on anything... I try to mount the system/cache/external partitions. I try to factory reset to try a different rom. I'm told it works but there's a failure message because of E: cannot decrypt data. I try to flash a different rom anyway. It says it was successful. I flash the gapps, more success messages. I try to reboot and again I'm locked at the Samsung Galaxy S III logo.
Random side note -- sometimes my Samsung Galaxy S III logo has a blue android cat of some sort on it... not sure where that came from (one of the CMR flashes when I was trying to fix the phone, methinks).
It's so strange -- because I was obviously able to load a custom ROM with the current bootloader and recovery -- and now after my phone's battery drained, I'm back to being dead in the water... I really need to get to the bottom of having my phone boot into a ROM reliably.
Previous ROM was Gummy Nightly 01-06-14.
New flashed ROM is CyanFox 2.0.2.
Please help. I need my phone up and working as soon as possible here, I'm expecting important calls in the morning, so this is horrible timing.
corrosivefrost said:
So I had a problem where I had issues getting a ROM onto my phone after entirely formatting it.
Some kind members helped me to get the phone running again and then getting TWRP 2.6.3.1 on it with the 4.1.2 build.
This was flashed to the phone using Odin after using E-Z Unlock 1.2 to unlock the bootloader and install TWRP 2.6.0.0.
I saw some random issues when I would reboot or power off and on with it locking on the Samsung Galaxy S III logo... but the phone rebooted eventually and I was able to continue use.
Fast forward to today -- for the first time in awhile, my battery fully discharged. When I got home, I plugged in and tried to power on my phone. Locked at the Samsung Galaxy S III logo... EVERY. TIME.
So I go into recovery... I find that the first thing that greets me is a message asking me for a password. This is odd, since I never put a password on anything... I try to mount the system/cache/external partitions. I try to factory reset to try a different rom. I'm told it works but there's a failure message because of E: cannot decrypt data. I try to flash a different rom anyway. It says it was successful. I flash the gapps, more success messages. I try to reboot and again I'm locked at the Samsung Galaxy S III logo.
Random side note -- sometimes my Samsung Galaxy S III logo has a blue android cat of some sort on it... not sure where that came from (one of the CMR flashes when I was trying to fix the phone, methinks).
It's so strange -- because I was obviously able to load a custom ROM with the current bootloader and recovery -- and now after my phone's battery drained, I'm back to being dead in the water... I really need to get to the bottom of having my phone boot into a ROM reliably.
Previous ROM was Gummy Nightly 01-06-14.
New flashed ROM is CyanFox 2.0.2.
Please help. I need my phone up and working as soon as possible here, I'm expecting important calls in the morning, so this is horrible timing.
Click to expand...
Click to collapse
At this point I would take the phone back to factory stock, are you able to boot into Odin mode?
buhohitr said:
At this point I would take the phone back to factory stock, are you able to boot into Odin mode?
Click to expand...
Click to collapse
Yeah -- I can boot everywhere, pretty much.
I ended up formatting everything... I tried CyanFox again, but after install, it was throwing errors all over the place (not sure why).
I then formatted everything again and loaded up Gummy... it seems to be working relatively well.
I'm not sure what caused TWRP to think it was encrypted, but I'm guessing that had something to do with the issue?
Is there anything I can do to try to prevent this type of issue from happening in the future?
corrosivefrost said:
Yeah -- I can boot everywhere, pretty much.
I ended up formatting everything... I tried CyanFox again, but after install, it was throwing errors all over the place (not sure why).
I then formatted everything again and loaded up Gummy... it seems to be working relatively well.
I'm not sure what caused TWRP to think it was encrypted, but I'm guessing that had something to do with the issue?
Is there anything I can do to try to prevent this type of issue from happening in the future?
Click to expand...
Click to collapse
I know for a fact that there has been issues with the flashing of 4.4 and encryption. The best bet is to turn encryption on then off again. Now you said you never encrypted it but the Turn it on then off again approch might work here. I also know for a while TWRP had issues flashing 4.4 so it might be worth it to run CWM.
[Q] Stuck on TWRP/System Recovery. Need help.
Hello, first time posting here.
So like the title says, my phone is stuck on System Recovery. I have a Samsung Galaxy A5 (A500F model), rooted, and with TWRP installed.
The phone was running fine for 3 months without problems, so I guess it must be from recent installs, but I haven't installed anything since last week. The last action I did prior to this problem was going to System Recovery via Link2SD app, since the usual button combination didn't work. So I guess the fault lies there? At this point I have tried everything I can do, like restarting, rebooting, wiping, factory resetting, and I even restored a backup but it still goes to System Recovery after every restart.
This is my first problem on Android phones, so I hope you can help me.
If you need more information, I'd gladly provide.
Cheers.
....bump.
Okay backstory time....
I have the Samsung Tab 3 Lite, T110 something and I decided to root it.
I used Odin to flash CWM and root it.
Well it was a bit laggy, so I installed this rom.
http://forum.xda-developers.com/showthread.php?t=2780068
It worked for awhile.
Later on, SuperSU said it needed to be updated, so I clicked update and it restarted the entire device and I got stuck on CWM-based recovery v6.0.4.8 and everytime I tried to reboot it kept going back to this recovery screen.
Well I tried flashing it again.
No dice.
Then I tried flashing ANOTHER rom from a different device (which I didn't realize at the time) and I'm still stuck.
To make matters worse my laptop doesn't detect the device, though it makes the noise like it's connected.
Well it DOES detect it, but it calls it an unspecified SAMSUNG_ANDROID.
I've tried updating drivers, turning pc off and back on, letting tablet die and plugging it in, different cables, everything.
It also says this weird thing when I try factory resetting in CWM: E: unknown volume for path [/sd-ext]
Not a darn thing works.
I'm frustrated and I'm sorry if I posted this in the wrong place but I'm at my wits end.
Bro try flashing stock ROM or any other custom ROM meant for your device from you device's recovery. And wipe data and dalvik cache before doing this ,and this can be done from recovery
Sent from my Aqua Trend using Tapatalk