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...
Related
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?
I've tried repeatedly to install CM7.2 and keep getting stuck on a blank screen. I'll see a "CyanogenMod" then "loading..." right below that. Then it goes blank and nothing ever happens after that.
Some background info. I've had CM7 installed on this in the past without problems. Months ago I went back to a rooted stock. Then yesterday I decided to try CM9 alpha. That installed perfectly. But it was too slow, so I decided to try CM7.2.
I used the same CWM 1GB boot SD, copied "encore_CM72-MiRaGe-02012012.zip" along with the Gingerbread Gapps and CWM. Installed in the same order and wipe data/factory reset.
So I got stuck on that blank screen after the CyanogenMod loading... message. I then decided restore to stock. Installed the 1.01 stock image. It also wouldn't boot up, but I powered it on and off 8 times and it did a factory reinstall and then it booted up normally.
Once back at a factory fresh system. I powered it off and tried installing CM7.2 again. Unfortunately I'm having the same problem again. Ugh, why won't it load now.
Hang on... I might be in the process of making a newb mistake. MD5 didn't match on my SD card, probably the ROM.ZIP is corrupted. Trying again with a good copy.
That was it. It's working now. Please disregard my idiot on the Internet moment. Thank you.
You always figure it out five minutes after you finally give up and post for help/venting.
Been there.
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!
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
Phone has been in the ****ter for the past day. Stuck on boot loop. I tried flashing the most recent stock firmware. It would not do it and kept throwing auth failed signs at me. I tried other stock firmwares for tmobile with no sucess. I Tried throwing them on my sdcard and installing through there in TWRP, but I keep getting md5 auth failures. I have wiped, factory reset, and cleaned house many times. Nothing works. Im at my wits end. Someone please help
I'm a guest to this forum..but same thing happened to me about 5 days ago. Last thing I remember seeing is the 5. update trying to take place and I was just about OUT of Internal memory (with NO microSD card). Phone just kept rebooting. I was able to do a Factory Wipe (Both in the OS and in the Recovery Mode)....Neither worked even though they appeared to be successful. Phone just came back with ALL of my data still intact. The other weird thing...I had about 60 seconds before phone decided to reboot each time. During those 60 seconds I was able to delete files, pictures, etc. to save space. As soon as the phone rebooted those same files were back! Very frustrating. Still having the issue.
im not sure what states either of you guys are in, but you can look on craigslist for people that do flashing. you make need to do a odin rebuild because the partitions are ****ed.
you can repair it yourself but with pure caution.
Have you tried flashing in download mode with your computer through ODIN? If twrp doesn't work, that's what I go to next.
You could also try flashing the firmware without the MD5 file and I believe twrp will skip the check. (not positive on this one)
Figured it out on my own. Flashed CF autoroot. Then flashed 5.1.1 which is the most up to date firmware. Im not sure if the issue was because I was doing 5.1.0 and didnt realize that was the most UTD version, or if CF to 5.1.1 was the trigger. Either way, it worked.