[Q] Galaxy s i9000 stuffed as update of rom failed using odin - General Questions and Answers

HI Guys.......i have galaxy si9000 and while updating the custom rom i wrongly selected the files using odin and the update failed...it was still in download mode but i removed the battery to retart the phone and to see if anything happened..........and then it doenst start at alll......kindly help how to start or how to reset the phone to get in download mode.
The reason while i was trying to do was ...few days back i loaded Ice Cream Sanwich on the phone and the phone went really slow so i decided to revert back to Ginderbread.....which was done successfully but then i decided to change to custom rom and this happened......

Related

Help returning my Captivate back to stock rom from CM7

Hi guys,I am new to this forum and I guess to android as well.Really need your help. I decided to flash CM 9 and everything went smoothly.But after a few hours I discovered that it is not for me.So I decided to back to the stock rom Gingerbread 2.3.3 which I had previously.So I thought that using Odin will do the trick.I have the original rom in my computer.For reference when I connected the phone I only clicked on PDA to select the rom, but after the upgrade finished nothing happened.I had to disconnect the phone to reboot it.And after that the phone tries to boot but nothing happens.It only goes to the Rogers logo and then restarts itself over and over again.What am I doing wrong or not doing at all.It would be very helpful of you to help me go back to Gingerbread again.Can you please provide me with details how to do that.Should I download more stuff like boot loader or anything or just use a different software.
Moved to General Q&A.

[Q] Galaxy S2 Soft Bricked after root....

Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
Try flash a stock firmware by using flashtool, it will work 100%:angel:
revernwe therefore
addamT989 said:
Hi everyone!! New here, but not new to Forums in general. I searched around and couldn't find my exact issue, so I figured I’d start a new thread. This is gonna be kinda long, but I wanna give as many details as I can to keep things accurate.
My wife and I both have the Galaxy S2 T989 (T-Mobile). Both purchased like new off eBay. When I got hers a couple months ago, as soon as I got it I factory reset and wiped the caches, upgraded to JB via Kies, and then turned right around and rooted it via Odin using the instructions found on galaxys2root.com. Everything went flawless, took me less than a half an hour total for everything. I got mine a couple months later and did the exact same process as soon as I got it in the mail. However after rooting on Odin and getting the green pass just like hers, it got stuck in a boot loop when it rebooted. It would go as far as the "galaxy S2" splash screen, and sometimes past that to where the Android takes off, then reboot, or freeze. It then became unresponsive to any button pushes and I had to pull the battery to get it to shut off (The battery is a new OEM Samsung battery incidentally). I ultimately had to unroot, re-install ICS and re-upgrade back to JB via Kies again to get out of the loop. I did this whole process 3 times to make sure it wasn’t something I did. So I’m still running unrooted with JB on it now.
The only thing I noted that was kinda odd was that when I open Rom Manager in my current non rooted state, it shows that I already have CWM and TWRP installed on it. Even though when I go to recovery mode it's the standard OEM Samsung menu. I never installed TWRP, and CWM was only on it for a bit when I was in the boot loop. Could this be my issue? Are they both still somewhere on my phone interfering with each other and I can only see them via ROM manager?
Sorry for such a long first post, and thanks in advance!
Click to expand...
Click to collapse
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
brandonarev said:
I would flash a complete bone stock Rom using Odin and start over. Also rom manager was highly discouraged on the AT&T version of the s2 so I don't know what the stance is on T-Mobile's version
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
Thanks for the advice! Should i flash it back to ICS then try to root again via Odin before i upgrade back to JB? I'm guessing there's something that isn't getting wiped. Since i can run CWM and Root with Odin without a hitch. it's the initial reboot after all that is done that I go into the boot loop.
tainiun rioters
pierm said:
hi,
can 'be that your device has some residual old. Do as you have advised. install a stock rom and firmware, so it becomes a new cell phone. After odin starts TWRP (much better) and root.
Click to expand...
Click to collapse
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
addamT989 said:
Sorry for my ignorrance, what exactly is TWRP, and is it now on there because i used Odin and it installed it automaticly? And do i want to use this vice CWM?
Click to expand...
Click to collapse
addamT989 said:
One more question...before i try all this, can i backup everything on Kies just like i would be able to with CWM and reinstall if my root fails again? I've only used Kies for firmware upgrade, never to reinstall a backed up copy of my phone.
Thanks!
Click to expand...
Click to collapse
Hi
TWRP and the 'one touch recovery, better than CWM.
The backup kies can not recover from CWM
steps:
install odin, after recovery, nandroid backup, ROM, and root.
hi
Flash the stock firmware using odin!!..it will work!
Sent from my GT-N7100 using xda premium
freezes then booted
Hello I have this problem with my galaxy s2 i9100. After reboot the phone wasn't booting something like "boot loop" so I re flashed the firmware and now the phone boots up but after the boot it freezes immediately. So I decided to install clock work mod recovery and install cyanogen mode 11 with cyanogen mode the phone boots up and are able to be used again until the screen goes to sleep mode or the power button is pressed then the screen goes black and doesn't turn on after long pressing the power button it reboots. So I don't know what else to do I have tried kernels, operating systems re flashing reseting and nothing helps. No need to tel me to do resettings. Also my galaxy s2 i9100 chip has insane chip bug but I don't know if it has to do something with my problem.

[Q] Stuck In bootloop/Factory Reset not working

hey guys i recently tried to customize my notification bar using metamorph, applied a change and now im stuck in a bootloop. i made a nandroid backup but idk how to go into recovery mode. i tried a factory reset and it didnt work, still bootlooping. (im running a kyocera hydro c5170 android 4.0.4)
this is my only phone and id love some help! but if worst comes to worst ill just buy a new phone.
Flash original firmware via odin
Sent from my Galaxy Note II using xda premium
Does anybody know where to find the original firmware, what version of Odin to use, and how to put the Hydro in to Odin mode?

[Q] Samsung P5113

I think my daughters tablet has been soft bricked but im unsure of how to fix it.
It was running ICS i believe. We had two of the tablets(both bought at exactly the same time). I went to update them both and the first one downloaded and installed an update absolutely fine without any issues. The second one (the one in question) downloaded it but wasnt able to install the update. It just failed and reset the clock every time i tried.
I decided to reset it completely and was then going to flash the latest jelly official rom( onto it which i found here
http://forum.xda-developers.com/showthread.php?t=1704668
So i booted into recovery and wiped it and did a factory reset but then the thing just got stuck in a continuous boot loop.
So i wiped it again and now everytime it boots it just boots into recovery unless i specifically hold power and volume up to boot into download mode.
So i thought that was odd but i would just go ahead and put the rom on and maybe that would fix the issue. So i used odin and the jelly bean rom shown in that thread above
P5113UECLK7 (4.1.1) - Cellular south November 2012 (Official)
It all went fine it passed and i thought it would now work. I had to unplug the cable and it turn the thing on as it just started charging after completing instead of restarting and it did come up with a status loading bar as if it was going to do something but then it just turns itself off again after a few seconds and again when you try to turn it on it just goes straight into recovery.
The tablet is charged up to 100% but i cant get it to do anything else.
I tried using ICS instead P5113UEBLI1 (4.0.4) - Singapore September 2012 (Official)
but still the same. Not sure what else to do? Any suggestions would be much appreciated.
In Odin did you have the auto reboot option selected? I'm asking because I was in the situation as you..I flashed wrong cm10 ROM and it was just in a boot loop.. I let the battery run out and then I charged it while it was off. I downloaded the stock jb firmware(mine came with jb preinstalled) and flashed with only auto reboot checked nothing else and it worked..
Sent from my GT-P5110 using xda app-developers app

Samsung Galaxy S5 SM-G900P Bootloop

Hey guys, so I'm up for a new phone (had this phone for 2 years) and I remember having a friend root + flash me the cyanogenmod on my Samsung Galaxy S3
I decided to root/flash my current phone (Galaxy S5) and i ended up ****ing in on several fronts.
The following is what I did and where I ended up
Rooted phone through Odin - was successful but I got a feeling it was outdated as I got the Seandroid kernal thing in red
Got ROM Manager and flashed recovery to TWRP - successful
Flashed ROM to Cyanogenmod nightly 7/14/16 - used the wrong version so i couldn't use my phone to call
Flashed Rom to the correct version - successful
Installed Gapps zip so i can use the app store and etc - experienced issues as it was always saying the store failed and etc
Now where I am currently
I ended up wiping all the data and etc so I can flash back to the Stock ROM/firmware since I couldn't get the Gapps to work.
I tried to flash the firmware but everytime I flash it and it boots to the stock recovery and says "installing android update" it gets to 1/3rd where it says "Erasing" and boots up to the Sprint Logo where the Blue notif is on and it is stuck.
I'm assuming its soft bricked and on a bootloop and I am trying to see if I can salvage this phone.
I tried flashing different version of the firmware (my brother has the same phone his version is G900PVPS3CPE2) and i tried that and G900PVPU3CPA. Both times its says its successful on odin but upon booting it only gets 30% before it says erasing and returns to get stuck on the boot.
Can I salvage this phone and if so can someone guide me through the proccess (links to proper firmware download/etc)
I do not care if any data/apps is lost (i have important stuff backed up on my gmail), I just want my phone to work.
That being said, my phone is salvageable instead of guiding me to repairing my phone to stock, if they can guide me to set my phone to a custom ROM (cyanogenmod or anything they suggest assuming they can get the googleapps to work on it) can someone please guide me through that.
Thanks again for reading.
Edit: All info in a TLR format incase my wall of text was messy
Phone: Samsung Galaxy S5 SM-G900P (SPR) Android 6.0.1
problem: ****ed up with flashing now phone is stuck in bootloop
What I want: Find a solution to make my phone work, ideally to make it work using a custom rom(any works) that has a working google apps installed.

Categories

Resources