Hello. I am currently in hold of a soft-bricked Galaxy S Plus smartphone, and i've been encountering several problems during my 'Rom' expedition. I'm not quite sure if there is any thread out there that presents a similar issue such as mine, and if it is, i couldn't find it, therefore i apologize in advance for any misunderstanding. My smartphone currently won't boot and gets stuck on the Samsung Logo - Along the way i have managed to make the recovery mode work, somewhat, and the download mode works flawlessly.
It all started when i first acquired my Galaxy S plus and stumbled upon an article on how i could simply upgrade my android version to Android 4.0.4 ICS via CyanogenMod 9, aka Ice Cream Sandwich and to be honest, it startled me and i was eager to try it out. After spending a couple of hours into informing myself on this procedure, because yes, i was pretty scared to even consider it. Clockworkmod gave me several headaches during the way, and so did Odin, before i got used to it, but in the end i made a Nadroid backup and i successfully installed the rom and could gladly enjoy my new Ice Cream Sandwich. However, the rom had it's issues(Other than that, it worked amazingly), and some people pointed them out( I'm not the brightest man when it comes to phone performance ), so i decided to look further into it. I found the xda forums, and browsed them for a couple of hours, in search for the perfect rom and decided to try out the CM10. I thought it would be a piece of cake, since the last installation went briefly, but i was oh-so-wrong.
I backed up my Sms, contact history and such, and simply turned on the recovery mode, with the intention of wiping the data and cache -- And boom! Clockworkmod froze and the phone shut down, just for me to realise that it was now impossible to go past the logo. I panicked and spent most of my time into searching for a solution, but there were couple of things which i simply couldn't do! First, the clockworkmod (I used CWM 5 when installing the first rom) wouldn't allow me to wipe the data and cache; Second, odin would simply get stuck when trying to install a stock rom (I tried a couple of gingerbread roms before that); I even let the PC open the whole night, just to let odin do it's work, but it still couldn't work. A stock rom that /worked/, though, was the I9001BUKP2 / CNXKP1 - Romania(Vodafone) Android 2.3.5 which i came across on another forum post. After installing the gingerbread rom, i booted into the recovery mode(original one) and tried wiping the data - But it would only freeze and shut down.
- I must add, that the clockworkmod gives me errors on mount cache (Command) and whenever i try to restore my original firmware(backup) it would just freeze on the data restore. (I had issues with several other roms when using Odin multidownloader, since they simply wouldn't get past the "System.img.ext4")
I honestly don't know if i missed out on anything, and/or if i missed out on any thread that could simply smack the answer right in my face, but once again, i'm sorry. If anyone could provide help to my issues, i would be grateful - Thank you very much !
edit: I have just now tried to install a firmware[ I9001 XEN I9001XXKF8 ], and after odin did it's job, and the SGS+ booted into recovery mode to finish the installation, i have noticed something very interesting - It gets stuck at "Formating /data..." - I can only assume this is perhaps a primary issue.
Related
OK guys I really badly need some help. My phone is in a non-workable state and I am starting to run out of options.
I did some mistakes but I will try to take out the details to list mostly the fact, hoping someone will take the time to give me directions.
- I have a galaxy s I9000 (switzerland/orange)
- I had upgraded to 2.2 via Kies.
- I got tired of the phone becoming increasingly slow. I found out about voodoo lag fix. I read 3000 forum posts, documentation and stuff, and when everything seemd easy enough, I installed voodoo via Odin.
- Here problems started. After installing voodoo, the phone booted, but the robot voice said "convert data partition. Not enough space on partition". Then again. And again. It was stuck in a boot loop. This problem doesn't seem to be documented anywhere i could find. The only instructions I could find on how to disable voodoo were to create some files on the disk, not very helpful when you can't boot the phone.
- I found a couple of threads with people who had the same message, and the advice their were given was to flash another rom.
- So I went to samfirmware.com and downloaded 2.2.1 for I9000 (JS8). I installed it through Odin. The phone booted, showed me the Galaxy S screen, then went black. Then it would vibrate every 20 seconds or so. Once, then 3 times in a row. I waited 30 minutes because in some places it said that may take long, but the situation didn't change. I rebooted, tried again after taking about the battery, wiped data, reset factory settings etc. The phone state wouldn't change, and I started to get a little desperate, because this was a stock rom, and if that didn't work...
- I read 3000 more threads, and phone a guy who had been in this situation, and got out of it by first installing "Eugene's JK2 froyo that never bricks" and then after wards reinstalling the stock rom.
- So I installed Eugene's rom. I knew it was trouble that it was a vibrant's rom, but I figured, I had read everywhere that as long as your phone supported download mode you could still always re-flash a new rom, so I decided give it a try.
- And the phone booted. Asked my pin, loaded stock android and all. I was happy at first, but then new trouble came. Now, whenever I plug in the USB, the phone's screen goes black after 4-5 seconds. When I unplug it, phone reboots. No charging battery appears when I plug the turned off phone on the charger.
- And worst of all, the buttons got mixed up. Vol up is vol down now. But more of a problem, 3 button recovery and 3 button download mode don't work anymore. I couldn't find a way to get them back. So I can't flash a new rom with Odin :-/.
- My latest was to install rom manager since I can access the market. I downloaded the tedgy rom. Installed the "clockwork recovery mode" from Rom Manager. It asked me if I had I9000 or vibrant, wasn't sure what it expected since I have now a vibrant rom on an I9000, but I put in I9000. Then I reboot telling rom manager to install Tedgy. I get a recovery mode screen which offers to reboot/reinstall packages/wipe data, then does a couple of operations, and finally gets stuck on :
can't open /cache/update.zip
(bad)
installation aborted
So there I go, with a vibrant rom on my I9000 (rooted, at least), a phone that can boot a half-functionnal android, but with a useless cable plug, an unchargeable battery, and a download mode I couldn't find... And waiting for my wife to get back with her phone so I can charge my battery again...
Any help or lead to help me get another rom installed on this phone again would be *greatly* appreciated. What other ways do I have to access download mode ? Or is there a way to get to it despite my buttons being messed up ? Maybe the rom manager issue can be fixed ?
OK well I got out of it somehow.
In case someone else had this same issue, here's how I got out of it :
1) Install ADB.
2) launch Odin
3) go to adb folder in command line and type "adb reboot download" but no enter just yet.
4) plug the usb cable on the phone.
5) type enter in the adb shell in the small window of opportunity you have before the screen goes blank. This reboots the download mode and allows new flashing via odin.
Any answer for this thread?
Did you fix the problem?
I'm stuck with the same case...
[SOLVED -- Read my last post]
Posting on forum was my last resource, but I've tried literately almost everything I can possible find.
I already bricked my phone and had to unbrick, do everything (update firmware etc) all over again.
I am at a point where I am afraid to do something new to my phone now without knowing what they are...
Please bare with me, I am not familiar with exactly what flashing is or whatnot, I just followed the instructions and got where I am....
K, recently I decided to wipe my phone CLEAN and update to new CyanogenMod 9 from factory mode.
So, I have Captivate, I897. It was ECLARE with 2.1 firmware.
I have updated to 2.3.5 (Gingerbread [I897UCKJ2]), Rooted.
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
I installed Clockwork mod (Free version).
My goal is to install CyanogenMod 9, and part of the process requires me to enter the CMW Recovery Mod.
I dont even know what this looks like, but all I know is whenever I boot my phone, after the AT&T logo animation it seems to go into this "messed up" screen, where as if my phone is broken. Stays there for 3 seconds and then continues to boot back to its OS.
In ROM manager, it says Flash ClockworkMod Recovery (You must have the clockworkmod recovery installed to flash and restore ROMs!)
Another option within ROM manager is, Reboot into Recovery (Boot into Recovery mode for manual management.), which if I do access it, it takes me back to that AT&T logo animation and that "messed up" screen again, but this time it stays there. Where all kinds of colored pixels are on my screen as if my screen is broken. It will only continue to boot back to my OS if I press power button or some sort.
Im guessing that's my Recovery Mod, which my phone for some reason cannot see?
So I tried "Download ROM (Upgrade to ROM Manager (premium) to access the full list of ROMs!", hoping this may cure that messed up screen effect, which I think is the Recovery Mod for all I know... When I click to install, it gives me Confirm Phone Models. None are my phone model for me to install.. (It only gives me Google Nexus S / Google Nexus S 4G / Samsung Epic4G / Samsung GalaxyS i9000).
Earlier, I was looking at this, http://forum.xda-developers.com/showthread.php?t=1127578
which is a way to fix recovery mod(?) But I have NO idea how to even install those files... Maybe not the .tar file but the other one.
Please help? Am I the only one experiencing this kind of problem? Couldnt find anywhere else on youtube / google / forum..
Thank you VERY much in advance, really appreciate it..
-Dan.
danroh said:
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
-Dan.
Click to expand...
Click to collapse
This is your likely problem right here. The Kernel that is installed during the rooting process and typically when you install custom roms is what is responsible for installing and therefor you being able to access the CWM recovery. Flashing back to the stock kernel likely messed things up for you.
http://forum.xda-developers.com/showthread.php?t=1300843
Now if you follow that link it will take you to several one click options for flashing your phone to stock gingerbread but with a kernel containing CWM. Also keep in mind that it is possible you could have wifi issues if you've had them in the past, but if your goal is to get to CM9 just ignore the wifi for the time it shouldn't be an isuse in the end.
Hey OP,
See this.... TRusselo's Flashing Guide
Sent from my SAMSUNG-SGH-I897 using xda premium
You need Gingerbread bootloaders.
Thanks guys! I figured out the problem and solved it!
Like you guys said, I didnt have the bootloader. The gingerbread I installed was the no bootloader version. After reinstalling to the one with bootloader, I was able to access the recovery mod and that "rainbow screen" glitch was no more.
Thank you!
Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter
Hi everyone, I spent all day trying figuring this out, even if probably the solution was really stupid, so I thought of doing a little post for future reference. If you have no time for my babbling, feel free to go to the short version (I wanted to put a link here, but I still have to learn how to do it and it's almost dinner-time...). If this post happens to be a duplicate feel free to remove it.
=== Whole story ===A week ago I got a Galaxy SIII mini N (GT-I8190N) and just kept it that way because I didn't had a win pc to use Odin. Yesterday I finally came back to my parents, powered up the win machine and followed an awful lot of different guides to manage to install the Macław CM 10.1. So, for short: installed CWM touch trough Odin, installed the root zip trough CWM and finally installed CM 10.1 & Gapps trough CWM. Here I did my first mistake: the first thing I did after installing CM was formatting internal and external SDs. Where the Nandroid backups of the working Samsung firmware were.
After some experiments I decided to go back to Samsung stock (reason 1: no gtalk, only hangouts, reason 2: NFC support still in development, reason 3: trying to restore SMS from a SmsContactsBackup I (luckily) had I messed up the SMS DB so much the app couldn't start). NOTE: Macław's ROM is amazing, I'm surely going to try it again when NFC support comes up. Sadly, I am an idiot who thinks he knows better so I ignored all the warnings of doing a wipe of data/cache and restoring the Samsung original recovery. I just went to Kies for a "Firmware upgrade and initialization" instead.
The result was a disaster. The phone rebooted but hanged at the Samsung animated logo. After a lot of hanging I decided to redo a Kies firmware upgrade. Obviously I had no luck. So I switched to Odin, took the image Kies downloaded (since I didn't want to wait an hour and an half to the download from unofficial sites) and flashed. And flashed. And flashed. Always without success. After a little bit I decided to try changing Odin options (repartition, NAND erase etc). Still nothing. So I started trying all the guides out there (here?): repartitioned with a PIT file, reflashed a CWM, reflashed stock recovery, various combinations in different orders of all the "solutions" above... You guessed right: nothing worked.
Since I read somewhere that there are Galaxy have 25 partitions (what the ****???) and saw that Odin was flashing only 8 or so I decided that something some the other partitions was missing, so I switched to Heimdall. Since the Win version didn't want to start, I did a fresh Ubuntu 13.04 install (lucky for me I happened to have an empty HD waiting to be installed on the server that I could use for an afternoon ), installed Heimdall, started figuring out how it works, realized I needed a custom-made package (nowhere to be found, apparently), started looking into the partition scheme to understand where the problem could have been... Finally I realized my skills are a tiny little bit inadequate for that and found a reference somewhere to a "hard reset".
In all this it never occurred to me to try and enter Samsung recovery. The first thing I noticed was that it didn't start right away with VolUP + Home + Power, but I had to keep them pressed a lot longer than what it's needed to go in download mode. In practice the SIII mini logo went up two times before showing the android with the open belly. Then finally the recovery appeared, I navigated to wipe data and cache with the volume buttons, accepted with the power button and rebooted. Thus I finally had a Samsung animated logo that was followed shortly by an "installing applications" loading bar and the first start configuration tool.
So, what I learned today:
1) Samsung tools are not necessary evil
2) if you don't understand what you're doing and you're doing it anyway, be prepared to suffer
3) we probably need a unified guide/troubleshoot the whole community can edit (wiki-like). Threads are great, but it's really easy to miss the obvious (for the whole time I was sure it was a bootloader problem, never occurred to me that there could have been some data left... also because I did a NAND wipe through Odin and I thought that was supposed to wipe personal data...) and often propose a solution without explaining the rationale behind it. I'm sorry if there's something like that out there somewhere, I wasn't able to find it
Thanks to you that bore my babbling
And now it's time for:
=== The short version ===
Problem: I messed up doing a Kies reset after installing a custom rom (CM10.1) without the dues precautions; the result was a phone caught in an endless loop at the Samsung logo. Installing firmware with Odin didn't solve a thing.
Solution: I booted in recovery (volume up + home + power) and wiped data and cache. After that I rebooted and waited a little bit, a progress bar appeared and everything was fine (well phone was at factory default but at least now it's working ).
I hope all of this could be useful to someone
Hello all before I describe my issue lemme tell you how I got there.
First of all, new phone, couldn't install pixelexperience and flashing stock android was being a pain with all methods (read not working), only managed to install stock android with pitch black recovery.
After a while it auto updated to android 9 and I started having wifi issues that people told me were android's fault so I waited for an update. Update came but android was unable to install it, giving errors after errors every time it downloaded the update.
My solution to all of this was to flash another rom, either stock or custom, and pray it works. It was scheduled to happen in 2 days, when I had free time.
Today, when trying to change the permission for a text file for an app from read only to write, some random process crashed, and it triggered a crashing cascade, including the settings app, homescreen launcher, etc until the phone restarted and got stuck in TWRP logo screen.
No key press, combination, resets, etc would fix it. So I got into fastboot and tried a few things with no luck. Flash stock rom again and phone seemed to be working.
Magisk manager couldn't install magisk and root the phone so I went into stock recovery/twrp and every time I did it I got a black screen message saying something like this:
"Your phone/system is corrupt and won't boot ever again *evil laugh*. Oh btw, go to this link in another device to cry more"
and the link redirects to a google page with some non-useful info.
So here I am, unable to root, unable to go into recovery, phone boots though. I force-stoped updates for a while, as android 9 wifi issues were terrible, and I don't know how to proceed.
Do I flash a stock image again, a custom one, try another rooting method?
I don't want to brick a 6month old phone, really sucks.
Btw, is there a reliable way to back up everything in the phone ?(not only google stuff, but app configs and files/folders) Long time ago I read something about Titanium backup but never looked into it further and now with this crash that lost me everything I wanna prepare for the future.
Thanks for all the help and for reading my boring story.
Even I am facing same problem.. In my case my phone is rooted and I cnt flash TWRP and I cnt get into fastboot mode.. I alwys endup with black screen..