Hi everyone! Longtime lurker here at XDA but now I have really run into a problem.
I have been running lollipop on my S3 for the past 2-3 months without problem and yesterday I decided to install Xposed Framework again since I had it on Kitkat and stupid as I was I didn't read too much into it and just flashed it through recovery and then my phone started bootlooping.
When I try to get into recovery I get two short vibrations and then it starts bootlooping.
So I decided to flash stock rom kitkat with Odin and everything went well but now it wont start, I know the first start takes a long time but I left it for an hour and nothing happened.
Flashed kitkat again still nothing.
So now I am here hoping for a way to fix this, I'm pretty experienced in flashing roms, kernels and so on so don't take for a newbie or idiot, just hoping there is a way to get my phone working again, What should I do? Flash another Stock rom? Is my phone totally dead?
Thanks in beforehand!
Related
Hi there,
Have been using ICS on my galaxy s for a couple of months. However this is the second time out of the blue it's decided not to boot for me.
The first time I thought it was because I dropped it and reinstalled gingerbread through Odin, then went back to ICS which was a very lengthy process.
I haven't installed anything, and now after just using the phone as per normal and it's decided to stop working? Any tricks I can do?
Basically it boots up, gets to the loading screen and just does that forever. I can boot into recovery but not sure what I should be doing next.
You could try reflashing your rom from recovery .
I think it's necessary to know which ICS-rom, for example slim ICS 2.8 needs to flash kernel first and then the rom ...
Sent from my GT-I9000 using XDA
Thanks imgibby123, if that is the last resort I may as well try it.
I've actually forgotton which one it is, I flashed ages ago and was very stable it just literally broke itself (a number of apps where crashing this mornign (reader, gmail etcc), so I held down the power button, turned it off as per normal, now the phone won't get passed the loading boot animation).
It was cynogen something, team platypus - I feel stupid I can't recall the details. But the ROM is still on there so I'll try reflashing from recovery.
Edit: It's ICS 4.0.3 RC3.1, so obviously still a RC but still! It worked flawlessly for months before
Thanks for the help.
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:
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...
Hey all, hopefully someone can help me out. Ill post the full story and the tl;dr version at the end.
So, my Xperia TL (LT30at) has been rooted for over a year and a half. Since i rooted it it never charged when turned off. I did research and couldnt figure out why, so i left it and have lived with it for the last year and a half. However, i just updated my phone to JB 4.3 by Dark Lord (Ultimate Pure XT ROM) so the model number is actually Xperia T (LT30) Anyways, the phone dies a lot quicker than before so the other day it died and because it wont charge when it is off i usually wrap a rubber band over the power button so itll charge enough to turn on and then charge by itself after that. However, it would only charge enough this time to boot, but then turn right back off. I did this for well over a day and got sick of it not working so i tried messing with things. In the process, I was in recovery (it was philz cwm or something like that, by the way im quite a noob when it comes to all of this, hence why im having problems) and i flashed the xposed disabler zip, thinking it would get rid of cwm because i didnt know what I was doing. It did end up getting the phone to turn on, and its charging great. However, the system UI crashes, and the "unfortunately the system UI has stopped working" pops up repeatedly so you cannot physically do anything on the phone. I tried going back into recovery to flash my backup to fix everything, but it was downgraded back to an older version of cwm, the version i origonally had on it before the 4.3 update. its like 6.0.3 or something, by david marcos or something. Anyway, itll go into recover but a bunch of error messages come up, like unknown volume path, no etc/recover.fstab, stuff like this. There is no way to flash any recoveries because it basically says it cannot find the paths. It will not backup, restore, wipe anything, flash from sideload, nothing. Ive tried all i can think of. Basically cwm comes on but i cant use it for anything. Instead i tried reinstalling cwm to try to fix it, but when i do it says "system cannot find path specified" so it wont download.
tl;dr version, cwm wont work at all after flashing xposed-disabler.zip. i cannot flash any recoveries or install anything through the usb. What do i need to do to fix this? because the system ui keeps crashing my phone is basically useless. thanks for dealing with a numskull..thanks in advance.
You can flash a stock rom with kernel using flash tool and then flash recovery and restore your backup.
Sent from my Xperia T using cm12
arniks8 said:
You can flash a stock rom with kernel using flash tool and then flash recovery and restore your backup.
Sent from my Xperia T using cm12
Click to expand...
Click to collapse
why i didn't think of that, i dont know.
This worked as far as getting the phone to boot and whatnot, however the phone died and because it doesnt charge when it is off, i cant turn it on. it will boot and itll get all the way to the home screen but it immediately shuts back down, even though it is plugged in. Is there any way to fix this charging bug? i did some research and found it is linked to cwm, however now that i flashed the stock rom i no longer have cwm on the phone, so why does it still not charge when off? Thanks for the help by the way..
Hello there:
I used to be a happy SM-N910T user until something went wrong and the device got hard bricked. Does not turn on, doesn't get into recovery mode neither download mode. It had DOK2 rooted, but started to restart by itself and then I tried to flash another ROM, I chose DOK2 N5 by RMarinella. Worked fine for a couple of days but then started again to suddenly restart more often in a daily basis. I tried last night to flash again the same ROM and after Odin when it was supposed to get into recovery ............... nothing happened. Now I have an expensive paper holder.
I have been reading about how to solve this situation but didn't find anything. Any help/guidance or prayer?
kharlosan said:
Hello there:
I used to be a happy SM-N910T user until something went wrong and the device got hard bricked. Does not turn on, doesn't get into recovery mode neither download mode. It had DOK2 rooted, but started to restart by itself and then I tried to flash another ROM, I chose DOK2 N5 by RMarinella. Worked fine for a couple of days but then started again to suddenly restart more often in a daily basis. I tried last night to flash again the same ROM and after Odin when it was supposed to get into recovery ............... nothing happened. Now I have an expensive paper holder.
I have been reading about how to solve this situation but didn't find anything. Any help/guidance or prayer?
Click to expand...
Click to collapse
Wait, did you try and use Odin to flash rmarinellas rom the second time around or were you going back to stock DOK2 ? Recovery for flashing custom roms, Odin for stock firmware and custom recovery installation.
I tried to re-flash rmarinellas ROM, I used Odin to flash the stock ROM and then I was supposed to flash the N5 Express 3.4D from recovery. Between those two steps the nightmare started. I am not saying that rmarinellas ROM is not working or was responsible for this malfunction. My Note 4 was acting weird lately, freezing and restarting randomly and I thought I did something wrong the first time I used rmarinellas ROM and that is why I tried to re-do the whole process again.