Sooo... I had a rom installed and decided for the giggles to another one. I wiped everything and it. It worked fine for about an hour, and then it rebooted randomly, i did not think much of it until i tried to unlock the phone. As soon as I entered the pattern it rebooted. I tried it a couple times and it happened every time. Thinking it was a bad rom I wiped everything and flashed my old one back on. Guess what, it kept happening. So I "figured" I must have screwed something up badly. Decided to do a full factory wipe using kdz and lgup. Once that finished I flashed the newest twrp which I believe is 3.0.2, then i flashed the old one back on. Same thing happened, worked for a bit then rebooted randomly and then kept rebooting every time I tried to unlock the phone. (Also flashing the newest gapps package each time, and I redownloaded both gapps and both roms multiple times) I just did another kdz wipe but tried flashing twrp 2.8.7.1. Will flash the old rom again and let you know how it goes in the morning. In the meantime, any ideas of why this might be happening?
Related
Good morning.
first of all, I've already read most of the posts that concern recovering the mobile, but here's the thing:
I flashed other ROMs a while ago, the ICS one iirc, then gave up and changed back to stock froyo, followed by an update to gingerbread via Kies, so my SGS already has the stock ROM. Everything worked fine, as expected, but once in a while when i turned the phone off and back on again, it got on a bootloop, and after many attempts it started ok. It also used to crash and turn itself off sometimes, but since it rarely happened, I wasnt bothered by that.
This time, I had to turn it off, and it just doent start back. I can access download and recovery mode, but since I have some things in its memory that I dont have backup, I really wanted to avoid the hard reset.
Do someone has any idea of how to proceed?
Thanks very much.
zanettirafa said:
Good morning.
first of all, I've already read most of the posts that concern recovering the mobile, but here's the thing:
I flashed other ROMs a while ago, the ICS one iirc, then gave up and changed back to stock froyo, followed by an update to gingerbread via Kies, so my SGS already has the stock ROM. Everything worked fine, as expected, but once in a while when i turned the phone off and back on again, it got on a bootloop, and after many attempts it started ok. It also used to crash and turn itself off sometimes, but since it rarely happened, I wasnt bothered by that.
This time, I had to turn it off, and it just doent start back. I can access download and recovery mode, but since I have some things in its memory that I dont have backup, I really wanted to avoid the hard reset.
Do someone has any idea of how to proceed?
Thanks very much.
Click to expand...
Click to collapse
do you have clockworkmod recovery? if so then wipe cache, dalvik cache and fix permissions.
if not boot to download mode and flash cwm. then do same as above :good:
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 guys
I have a problem with my Note. I have installed several roms over the last year without any problems. Recently though I had a problem. I had been using about a week or two the ROM SuperNexus but a few days ago the powerbutton started not to work. It would at some moments work and some other moments it wouldn't. Very frustrating. I reinstalled the ROM, still didn't help. Then I installed a different ROM. It worked but not for long. Now it also started to reboot itself every 5 minutes or so. No idea why. I decided then to flash a new kernel. Abyss didn't work like I wanted so I installed Speedmod kernel and then installed the stock JB rom. Now that worked all fine and well. No problems at all, but the weird thing is when it gets to about 20-30% on battery, it reboots and then gets stuck at the bootscreen.
Why would this be? I'm afraid there is something really wrong with the phone. Does anyone have an idea what this could be or how I may be able to fix it?
Thanks in advance
Daniel
Edit: Also should not when it gets stuck at boot, wiping data/reset factory helps. Also when it's stuck at the bootscreen, it does get warm I find.
I just did a test with the App eMMC BrickBug Test and it said that Yes. Insane chip.
DanielG27 said:
Hi guys
I have a problem with my Note. I have installed several roms over the last year without any problems. Recently though I had a problem. I had been using about a week or two the ROM SuperNexus but a few days ago the powerbutton started not to work. It would at some moments work and some other moments it wouldn't. Very frustrating. I reinstalled the ROM, still didn't help. Then I installed a different ROM. It worked but not for long. Now it also started to reboot itself every 5 minutes or so. No idea why. I decided then to flash a new kernel. Abyss didn't work like I wanted so I installed Speedmod kernel and then installed the stock JB rom. Now that worked all fine and well. No problems at all, but the weird thing is when it gets to about 20-30% on battery, it reboots and then gets stuck at the bootscreen.
Why would this be? I'm afraid there is something really wrong with the phone. Does anyone have an idea what this could be or how I may be able to fix it?
Thanks in advance
Daniel
Edit: Also should not when it gets stuck at boot, wiping data/reset factory helps. Also when it's stuck at the bootscreen, it does get warm I find.
Click to expand...
Click to collapse
1. Boot your phone in recovery and flash the latest kernel from here
http://forum.xda-developers.com/showthread.php?t=1789397
2. Restart and allow some time to settle.
3. reboot and do wipe data /factory reset, wipe cache, wipe dalvik
4. Use pc Odin to flash stock ROM from sammobile.com
5. Check if it works and update...
I was having a few problems with CM11, so I figured I'd start over from stock 4.1.2. flashed (as I have done many times before) via Odin 3.07. On reboot, it went into a boot loop. I never had one before. I re-flashed and got the same result. So, on a hunch, I went into stock recovery, cleared the cache (again) and made a factory reset (again), flashed the root.zip file, flashed CM10.2 and the 4.3 apps, and now it is running.
I'd like to know if anyone can say why the 4.1.2 bootup went into a loop and how to overcome that in the future. I think I might have disconnected from Odin slightly early. It said Reset, but I didn't wait for the beep. Later, I did it again, waited for the beep and now I am back on 4.1.2.
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.