Help! How can I fix Encryption Unsuccessfull (Samsung Galaxy S Plus I9001) - Galaxy S I9000 Q&A, Help & Troubleshooting

Hello Guys,
I really hope there is someone who can help me out, because I think i've screwed up.
So, I tried my hand at rooting and flashing my old phone (the samsung galaxy s plus), but turns out, I'm more of a noob than I originally thought.
Okay, so here the problem: I tried installing Cyanogenmod 12.0 on my phone using TWRP. Eventually I thought I got it right when my phone finally started installing Cyanogenmod, but then after a while the installing broke of and there came a message saying: Encryption Unsuccessfull. Before I went ahead en pressed the reset phone button I researched what it meant, and there were threads saying, don't push that button and that I should try and re-install the original firmware using Odin. But when I tried to re-install the firmware Odin couldn't find my phone. And everytime I connect my phone to my pc it says that it can't connect because the thing is damaged. I also tried to connect with my phone using Kies, which also didn't work. I tried researching what to do, but nothing works.
So please someone help me!! I can't, for the life of me figure out what to do. And like I said I'm a complete and utter noob concerning this type of thing.

Related

[Q] GT-I9000 wont start...

Hi everybody.
I could use some really good help because i think i'm a step before samsung service. After flashing many times a new ROM (JPA), just to try out some new stuff, in my unbranded SGS i can't get it started now. More specifically, after the last flashing which was successful and nothing went wrong, i turned the phone off so i could put in the sim card and the sdcard. Then i tried to switch it on but nothing happens. The 3 button combo was working properly and now that won't work either. The weird stuff is that nothing went wrong during flashing. Do i have any chances, or should the phone go to samsung service?
Thank you
i have the same problem with you can anyone help ?

[Q] Galaxy S stuck in boot-loop

Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...

[Q] Very bad brick situation

Hi everyone,
I have in the past switched roms on my Galaxy S before, therefore the issue of bricking my phone is something that doesn't intimidate me too much. However, this time i'm really stumped, and I turn to the gurus here at the forums, hoping a solution can be found.
I had just gotten my phone back from getting its screen repaired (which makes this especially irritating), and my carriers had flashed my phone back to their stock version of android, meaning gingerbread with a lot of bloatware. I decided straight away that I wanted to root my phone today, although I was away from my PC. I had my laptop with me (Macbook Air), but I had never done any flashing from it before, not to mention ever using Heimdall before (I had always flashed with Odin). I downloaded everything, and then I made my first mistake: I flashed a speed mod kernel (I believe it was a froyo kernel), and after reboot my phone wouldn't go past the splash screen. I could still get into recovery and download mode. Then I decided to try playing it safe, and I downloaded stock firmware packages for Heimdall fro the forums here. I tried flashing JVS on my phone, going exactly by the instructions written in that same thread that I found the packages, but the flash didn't succeed. Instead, I got an error message saying the PIT file didn't reach the end of the transfer (or something like that...) and the phone rebooted. After that attempt, the phone went black. Nothing works anymore except for download mode. Now I thought that as long as download mode works, I'll be ok, so I tried flashing different packages through Heimdall, and eventually when I got home I tried using Odin on my PC. The problem is, my PC doesn't recognize my phone anymore (even though the drivers are installed and I never had an issue with that before), so I'm pretty much stuck with a brick for now.
I really don't want to go back to my carrier again, and hope to get my phone back in working order without paying too much. I still think there's hope as long as download mode works.
Does anybody have any suggestions what I might be able to do? Since my PC doesn't recognize my phone (and therefore Odin doesn't either), the only semi-working option left is using Heimdall somehow, but as to how to use it, I'm in the dark.
I would really appreciate any help you guys can give me. Thanks a lot!
Aaron
first try reinstalling the drivers and try again. if you can get download mode, should be repaired.
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
commandozzz said:
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
Click to expand...
Click to collapse
We are here to help.

Not booting past the "Galaxy S" screen...

Hey guys,
In a bit of a pickle at the moment. I grabbed an S1 off a friend to try and teach myself about rooting and flashing custom ROMs and such using Odin. With the final intent getting it to run ICS. Not a very hard challenge, but evidently it is for me.
I'll explain what I did, and if you can help without investing too much of your time I would be very grateful.
When I got it, it was running 2.3.3, all the tutorials I read told me to update it to 2.3.6 before doing anything more. I managed to root the phone easy enough, no issues there. But when I tried to put 2.3.6 on via Mobile Odin, (which I used to flash my S2 to ICS, long story) it had seemed to freeze on 'flashing flash kernel' for a good 15 or so minutes.
Being the daft monkey that I am, I exited the program...by removing the battery (don't judge me please). When I went to turn it on, it wouldn't load past the "Samsung Galaxy S" screen.
It goes into Download mode fine, and I've tried to flash an abundance of different Gingerbread ROMs onto the phone and Odin has just been getting stuck on the "setup connection" every time I've tried to flash.
I have tried using different USB ports which is readily suggested by most people and seems to work, using my laptop instead, different cords as well. No luck. Nothing happens when I press volume UP + home + lock like it used to, so I can't even factory reset or anything =\
I did find somewhere that suggested adding a PIT file to Odin and selecting repartition but every one yells at each other when 'repartition' gets mentioned, lol.
I hope this is in the right place, please bare with me if I used any wrong terminologies, I am relatively new to this.
Has anyone got some suggestions that may help me with my problem? =\
Thank you!
Taylor
sigh...here's my recovery kit, unzip, read .txt file, proceed
http://db.tt/MOGZx01S
Credits to nitr8 and chainfire
Thanks, sorry for being such a hassle...
Twinning92 said:
Thanks, sorry for being such a hassle...
Click to expand...
Click to collapse
No problems, was teasing ya! You will end up with root and custom recovery, if you then go to slim website and read and follow installation instructions you will then have lush ics

[Q] Admitted defeat, help required

Hello folks.
Had a go at rooting Samsung i9000. It's quite old, and clearly clogged up to the hilt with the apps very laggy and frequently crashing. I quite fancied getting rid of the bloatwear too and the bloody annoying splash screen at start up!
Needless to say, it's all gone belly up. I've tried a couple of things using the guides here, but I don't want to keep pushing my luck in case I completely brick the device.
I'm running an i9000 in the UK on the o2 (Well, giffgaff) network. It was running Gingerbread, 2.3.5 I think. As it stands, I can get into the download option, but nothing else. I had used Odin 3, but have since read that the highest level is 1.83, which I now have. This might have caused the initial problem, but it's "soft" bricked. I've tried to flash over a stock rom again, but I keep getting failure notices. I can't get past the "Can't open the serial (COM) port" error message on Odin. I've downloaded the drivers and they have successfully installed.
One thing I don't think I did beforehand was to enable USB debugging.
I also tried the guide on here which uses the pit method, and curiously enough, it went through without the COM port error. The only thing that did, however, was to remove the "Phone + PC" logo. I am still able to get into download though.
Help! I am due to get a new phone very shortly, but it would be very useful to get the phone working again in the meantime! Any help very much appreciated.
If Kies is running in background it will fail, Go into Kies, Tools -> Preferences, unselect "Run Samsung Kies automatically when a device is connected", save the change, close out of Kies, and then restart ODIN. Try flashing now.
Try uninstalling Kies and then reboot and install the Samsung Drivers. Try then.
PFFFFFFFFFFFFFFFFTTT, sent from my i9000

Categories

Resources