[SLIMICS 4.2+Semaphore] Boot loop, can I reflash? - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi
I have had Slim ICS 4.2 working ok for a month or so. Yesterday it suddenly started to give FC to all apps, so I rebooted it. The only thing that changed was that, when trying to update the Adaway lists, it gave me an error and could not do it. From that moment, it was stuck in the Slim logo for three reboots. After that, it started a reboot loop, showing the semaphore logo and rebooting back again. I have managed to enter Recovery by connecting it to a USB cable, after some reboots it gets into it. Three button combo was working for Download Mode but not for Recovery.
Can I simply reflash Slim ICS, without doing a wipe? I don´t want to lose my apps, at least not before backing the data conveniently. It would suffice to be able to boot and do a Titanium Backup, then move on to Slimbean or something. I still have the original zips I used to install it.
Thanks!

Related

[Q] Stock restore fails, but I won't give up! (Help please)

So I'm trying to get my VZN Galaxy Tab back on its feet. After trying to get Gingerbread in it so I can use Netflix - and failing - I'm going through a lot of motions.
Okay. First I rooted it with Super One Click. I should have been happy with that, but noooo. Then I tried flashing GB on it (I wish I can remember which ROM I started with...it's a mess. I think the pit file was gt-p1000_mr? Does that sound right?).
When that didn't work, I went to the much-cross-posted procedure for returning it to stock using Heimdall and SCH-i800_VZW_stock. Tried it five times. Each time, it booted into the Galaxy Tab/Samsung logos, then a fast glimpse of scrambled letters for a second followed by twinkly music, then black nothingness. It would then bootloop. I attempted to boot into recovery to wipe data/cache, but I couldn't get there. Vol-Up/Pwr just brought up the logo and scrambled video again.
Since I was still able to get into download mode, I tried flashing another ROM...this one the "P1000XXJQ1_P1000XXJQ1_P1000XXJPZ" method. With this, I was able to also flash CWM so I have SOME recovery mode. Sadly, booting brings up the GT/SAMSUNG logos and I get the spacey animation, but after that, again - blackness. This time, however, the Menu/Home/Back/Search buttons light up, so something's happening in there.
Also, booting into CWM, I cannot get my sdcard to be recognized. I tried different cards, so there's something goofy with the slot itself, I'm guessing.
So nothing is really working, but since I can get into CWM and also download modes, I'm holding out hope that this is not completely bricked.
I just need to find the right method of getting it back to a functioning tablet. If anyone has any suggestions, I'm all eyes. Thanks so much.
UPDATE: I tried reflashing stock using the tried and true method. But this time, I went in and flashed CWM replacing the stock recovery which never worked for me. I got the Galaxy Tab/Samsung logo, and at long last, the animated VZW logo. Then it would bootloop there. I booted into CWM recovery and wiped the data/system and the cache from the first page. It still booted and bootlooped the same. This time, I booted into recovery, went to the mounts and storage section and formatted the system, data and cache. Opening logo only. CWM again, and got a whole bunch of "cache missing" messages. But I think I'm getting closer. Back to work.
UPDATE II: So the farthest I can get is the animated VZW logo using the combo of the stock flash through Heimdall, then flashing CWM with Odin. Still no sdcard access. Anything I should try here? Thanks.
same question here
Did anyone figure out how to restore Verizon tab?

[Q] Constant Rebooting after trying to flash to gingervolt

After trying the update(made cwm backups btw) the phone is in a reboot loop cycle. However, I can't get back into CWM in order to restore the backup i made or even the revo_stock or the stockrooted zip. I can get into the OS to the point where it wants me to select a language then it tries to find the SIM and fails completely and reboots. If i pull the battery and try to boot from the power on the USB it will reboot to the LG logo then instantly reboot again... Ideas anyone?
cliffs:
-backed up in cwm
-tried to install gingervolt
-stuck in reboot mode
-cannot access cwm to restore
Did you wipe data both times MT said? Maybe try wiping again?
Did you try flashing from a froyo ROM?
Wiped date both before and after the flash of gingervolt. I was using the decrapped rom 1.1
I would happily go back and try to clear the data again, however i cannot access CWM in order to do so after the gingervolt flash... Even using the power button+volume down i get no access...
SomeFknGuy said:
After trying the update(made cwm backups btw) the phone is in a reboot loop cycle. However, I can't get back into CWM in order to restore the backup i made or even the revo_stock or the stockrooted zip. I can get into the OS to the point where it wants me to select a language then it tries to find the SIM and fails completely and reboots. If i pull the battery and try to boot from the power on the USB it will reboot to the LG logo then instantly reboot again... Ideas anyone?
cliffs:
-backed up in cwm
-tried to install gingervolt
-stuck in reboot mode
-cannot access cwm to restore
Click to expand...
Click to collapse
I had the same thing happen to me. Although once it rebooted i was able to bypass the setup process and just manually do it from the home screen.
If you can't even get past the LG logo without it rebooting, I also had that happen to me on my last phone a few months ago. I called Verizon and they said that they had reports of other phones doing that too. Unfortunately I never figured out how to fix it. The problem was that it never stayed on long enough for the computer to recognize it.
Flashing Gringerbread ROMS from froyo breaks this phone. I did that same thing
restoring a back up is what you need how to get there idk
I haven't had much luck getting the phone to do anything, it will stay turned on for ~2-3 minutes then instantly reboot...
SomeFknGuy said:
I haven't had much luck getting the phone to do anything, it will stay turned on for ~2-3 minutes then instantly reboot...
Click to expand...
Click to collapse
Hope on IRC I'll see if I can help
Ok this is how i fixed this i pulled the battery then holding power and volume down button at the same time turn your phone on hold it until you get a black screen asking to wipe hit the power button to.confirm now it will reboot back to cwm and go to back up and restore then go to restore and restore one of your backups deck stock back up does not work it must be one you made.
Sent from my VS910 4G using xda premium
CWM reboot loop
Use this zip from thecubed it works wonders.
My phone would not go past reboot option in CWM
Search fast boot loop thread for further instructions on how to use it.
I pulled the SD card from my Revo and used it in my old win mobile Omnia so it would mount on my PC then I copied the zip onto the stuck Revo card.
Well after a few hours of tinkering i got her working... CWM never wanted to register but finally after about 100 tries of power on+vol it actually caught and booted into cwm. from there it was a cake walk until i got into gingervolt and it refused to allow the phone to come out of airplane mode(why this was even on is beyond me). after about 4 reboots the phone is working flawlessly...

[Q] Reboot Loop, Trying to Restore to Factory

I was running CM 9 nightly builds for the last year, and decided to upgrade to CM10. In my system settings there was a handly little "upgrade" button which I mistakenly used- and my phone got stuck in a reboot loop. I booted into recovery mode, and tried to restore the phone, but it did not work. It kept sticking at the blue circle boot image for over 20 minutes.
I tried recovery mode again, and every time I went to CW recovery I would get several lines saying can't mount SD card. OK, I broke it.
I then downloaded the factory firmware from samsung-updates.com - and flashed with Odin- just to get my phone to work. It's been 2 hours where I cna't get anything up. After rebooting (from factory firmware) I have the regular samsung s repeatedly coming up, and I'm still in a reboot circle.
Any suggestions or ideas? I need my phone for work, so I really just want to get it up at this point, with whatever will work.
I found the EZBase recovery kit thread, fixed myself Of course, it's the 101th thread I read in my search!
http://forum.xda-developers.com/showthread.php?t=2095519
Sorry, next time will keep searching. Worked to get my phone up and running,w ill now attempt CM10 again...

[Q] Boot lopp w/ AP, Plz help.

Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.

Stuck in an odd bootloop, can't get out of it (SGH-T599N)

Hello all. I have been in the Android root community for a little over three years, and even after tinkering with the various devices I've owned since, I cannot get my T599N to come out of its current bootloop.
A background: I had been checking some things in my settings app (running stock, rooted), and I ended up just force closing the settings app to get out of it quickly. Well, this action deleted all of my text messages, and later on it removed my notification bar and made my wallpaper go black. I ended up booting into recovery mode to try and clear the cache. After it cleared, I rebooted, and bam, the bootloop started.
Now, here's what's interesting. The phone is in a bootloop where it displays the first boot message (SGHT599N Galaxy Exhibit or whatever), and then it tries to boot into cwm recovery, displays the loading screen for that for 2 seconds, and just reboots again. I've tried installing a stock rom from ODIN with no success. The rom apparently loads onto the device but it's still in the bootloop. After this, I tried to install philz recovery to try to install a zipped rom to get the device to somehow boot. I tried to factory reset it for installing purposes, and it just reboots. The device will literally clear everything but /data, so that makes me think that it may be a file system problem. I really need to get it to work, as I am out of a phone right now.
Does anyone have any suggestions? I've tried everything I know.

Categories

Resources