So. I'm rooted using the beta custom twrp recovery. Been using it and setting around for months now. I've softbricked twice and got out of it. But now I'm having a stupid stupid issue.... I've been having indicator issues all day. Tried lots of stuff.... reverting to recovery. Uninstall happy reinstall. Etc. It will update when I restart and remove battery. It will stay at whatever it starts at though. It indicates charging when plugged in but the number refuses to update. The hidden menu shows the same number as does any batt app I have tried. I will try whatever you genies suggest. Thank you.
Related
So I flashed jts kernel last night everything worked great...woke up this morning and stuck on boot logo...my phone has the lag fix enabled...can I use a stock rom without kernel to fix the issue??
Sent from my SCH-I500 using XDA Premium App
Re.
Great post, I'm having the exact same problem. When I turn my phone on I get Samsung for 30 minutes non-stop. If i plug into wall or computer the charging batter shows up with no juice and the wheel to check battery life but this time its not moving. I tried to reflash my kernel but it didn't boot. Instead I got the connect to computer logo im not sure what to do. Please help. Also I was in the process of restarting for the new update but it just got stuck on Samsung and here we are
I used this method below to force the device into downloading mode
http://forum.xda-developers.com/showthread.php?t=929326
then i flashed the odin package below
http://forum.xda-developers.com/showthread.php?t=1116867
then it works now
I also had lagfix enabled when something happened and I was stuck on the Samsung logo. I looked for a ROM that has the Voodoo lagfix properties (Altered Beast) and flashed that. On first boot it went into recovery, so I disabled the lagfix. Then when it booted I flashed the rooted ED1 so I could flash the EE4 OTA (for the radio).
Note: During the EE4 upgrade, it will look like it hangs at the middle point. Just wait it
out and it'll finish on its own.
I used Odin (in a VM) for the downgrade since I was unsuccessful with Heimdall (I only have Macs).
So yeah, I flashed the rooted ED1 and Voodoo within 9 hours after getting the phone. Everything was going fine until I got the EE4 update notice this morning. Without thinking (I had just woke up) I tried to install it. It rebooted and was stuck in Samsung several tries for as long as I would wait it out. I finally ran Odin again and reflashed the rooted ED1 image and Voodoo again.
My only issue now is that I cant get anything from the Market to download. It says Starting Download then immediately disappears from the notification bar and wont install/update anything. Same results downloading straight from the Android Market website. So Im just trying to figure out this now. Installing new market versions hasnt solved the problem, and neither has the clearing of cache and any other trick.
i had the same issue, cache did not mount in none voodoo system, voodoo never converted it back. flash with this odin package in the form it corrected my issue
http://forum.xda-developers.com/showthread.php?t=1116867
jami2976 said:
So I flashed jts kernel last night everything worked great...woke up this morning and stuck on boot logo...my phone has the lag fix enabled...can I use a stock rom without kernel to fix the issue??
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Re enable voodoo lag fix and system fix then try Again
Sent from my SCH-I510 using XDA Premium App
weird....
well as weird as it sounds i was still able to get into download mode even though it was stuck on the samsung logo....what i did was flash the yellow cwm because i hadnt flashed it, after it installed i was able to get into recovery...i tried to disable the lagfix via cwm and nothing happened it just booted like normal only difference was the the low battery sound went off continuously for like 3-5 mins as it booted up..and the battery was like at 75%.... then i walked away from the phone for maybe 5 mins cause i had a customer walk in and when i returned it had rebooted itself into the triangle with the android in it...did a battery pull and rebooted like normal then randomly like 20 mins later did the same thing...reflashed jts kernel to see if that would fix it and it was a no go....still same issue...i know its a lot of stuff to take in, my main concern however would be how to force disable voodoo so that i can just try and start from scratch..any takers?? and thanks for the replies earlier guys I was beginning to think it was only me with these issues..I appreciate all the help and feedback
EDIT* just though about it..could I just take out the memory card and load it into my computer and do the whole disable-lagfix thing in the voodoo folder to achieve my goal??? then just start from scratch?
So two days ago i restarted my phone and after that my home button did nothing.
it would still wake the phone if it was locked. but other than that nothing.
all my settings for the status bar were reset too. (things like which toggles are there and indicator color etc,)
they were all reset to the default. (this includes the data connection getting turned on)
Since then i have tried two different roms and both of them ended up with the same problem.
It always happened on a random reboot. (i.e. it doesn't happen on the 1st reboot, but at a random reboot)
Anyone know what the problem is?
I dont know why this happens and there is no other way then to flash a new rom.
Wipe everything in recovery and flash a new rom thats the only solution!!
rr0yy said:
I dont know why this happens and there is no other way then to flash a new rom.
Wipe everything in recovery and flash a new rom thats the only solution!!
Click to expand...
Click to collapse
i know that what i have been doing,
but its kinda annoying when i have to reflash every day or two.
Dont OC much.. it causes random reboots!!
rr0yy said:
Dont OC much.. it causes random reboots!!
Click to expand...
Click to collapse
I haven't been,
usually i my max is 729 which has always worked fine.
but after this problem started i did go down to stock (600)
but the problem still occurs
729 is ok.
It might be due kernel or some app with root access.
Someone who cook Roms could explain the reason!!
Edit: Btw Which rom and kernel are you using??
Take provision.apk from the ROM's zip and put it in /system/app/
After that, set it's permissions to rw-r--r--(644) and reboot
Sent from my LG-P500
I had this the other week, along with a couple of other little problems, ended up being that only factory reset would fix it. Don't know why it keeps coming back for you though.
Ramis93 said:
So two days ago i restarted my phone and after that my home button did nothing.
it would still wake the phone if it was locked. but other than that nothing.
all my settings for the status bar were reset too. (things like which toggles are there and indicator color etc,)
they were all reset to the default. (this includes the data connection getting turned on)
Since then i have tried two different roms and both of them ended up with the same problem.
It always happened on a random reboot. (i.e. it doesn't happen on the 1st reboot, but at a random reboot)
Anyone know what the problem is?
Click to expand...
Click to collapse
i also had a same problem ,and found working after changing the rom
Hello Peeps,
I was trying to flash a rom yesterday and had something strange happen to me.
The rom featured Aroma installer and I had flashed this particular rom roughly 5 or 6 times with no issues.
Yesterday, I did a full wipe and tried to do a new install of this rom.
There was an option screen in aroma that allows you to choose your own mods and features or use the developers defaults.
I was on this screen trying to choose the developers defaults option and Aroma simply froze up.
It would not let me choose with version to flash.
The touch screen wouldnt respond and I didnt know what to do.
I searched google and found nothing.
I decided to do a battery pull.
I know that a batter pull during a flash is something we should never do as it will brick our phones.
In this case, as the flash had not actually started yet I decided to try it.
I pulled battery and booted into recovery and was able to restore a nanroid.
I am just curious if anyone else has had this issue?
How dangerous was it to pull my battery?
Could I have bricked my phone?
Phone has been working just fine, I am just wondering if there is another way to resolve an issue with Aroma like that?
Thank you,
I never had that problem as for the pull battery it is fine as long as you're not flashing.
I was installing a ROM on my sister's s3 when the aroma installer completely froze. I pulled the battery and it boot looped but wouldn't go into recovery until around the 10th or so time (vol up + home + power). Flashed it again and it worked fine...really weird.
As for bricking your phone I agree with above poster, it should be fine if you aren't flashing anything.
Sent from my SCH-I535 using Tapatalk 2
I've had this same issue happen a couple of times. It usually happens when I try to install the Jelly 'Beans' rom...sometimes it will work, sometimes it will freeze. I usually have to do a battery pull and recovery will come right back up. I've noticed this seems to happen the most when the phone has grown hot...so maybe it has something to do with RAM, etc.
One day, I got tired of the lame and boring Kindle interface, so I decided to use CyanogenMod to fix that problem. The Kindle Model I had was the 2012 HD Kindle "Soho" model, the one they had a warning on not to mod. So I previously rooted my tablet, and after unknowingly installing the wrong TWRP version, I got Recovery Reboot from the Google Play .apk I got. The first time I used the app, it gave me a red triangle saying I should reset to factory default or reboot. Each time I rebooted got the same triangle, but factory resetting fixed that problem. I logged my Amazon account back in and got all my apps back, then re-rooted and got the Google Play .apk from before. I saw the warning about the Soho models after going back to the CyanogenMod wiki to see what I did wrong, and I gave up and stayed with the boring interface. BUT, my Kindle ran out of battery, and it automatically shut down, and when I charged it, it rebooted into the familiar red triangle. I rebooted again a couple times, didn't work, factory reset didn't work either, and leaving it on for a few hours to completely drain the battery didn't work. I think the TWRP files were still hidden in the system files after I reset it the first time, and rebooting with charging the tablet activated the reboot into recovery, which triggered the TWRP files into action, but it was the wrong version, leading to this brick. How do you fix this? Do I need a fast boot cable?
bootloader unlocked
MIUI 9.5.19 global ROM installed
Magisk 16.4
Have been using the phone for 2 weeks now it's the second time that the phone shut down because of battery to low. OK so far but it then only is booting into TWRP. Also deleting DALVIK and CACHE i can see it booting and then the black screen with the navigation arrows are visible for a second. It's seems that there is something preventing the system to come up properly. After 5 short attempts with black screen and navigationbar visible it boots into TWRP.
Also re-flashing Magisk is not solving it.
OK I could now re-flash the Global ROM again but it won't fix the general issue why the phone get's stuck once it shuts off because of empty battery and again I would loose all my data.
Anyone with ideas how to fix it or what could be the root cause?
EDIT: It seems that there is really a problem with the system itself. If I instantly hold the power button once booted until the black screen I could keep it running and I see the restart, shutdown, airplane buttons but nothing more.
In Windows I would say it's not starting the explorer.exe
anyone who had something similar?
Have you tried re-flashing with MiFlash?
Bootloop after weeks of normal use is pretty misleading considering that you are using a custom recovery that isn't even official plus Magisk and possibly other mods. You should flash the official stable ROM with the MI Flash Tool and then run the phone without any mods to see if you still experience the same problem. And if you decide to use TWRP again you are better off using it through fastboot so the stock recovery remains installed on the phone.
THx for your replies... I think I've figured it out:
It seems that the alternative launcher is the root cause. I've been using Microsoft Launcher since moths across all my devices (light+fast+sexy). Without it (replaced by Nova now) it seems that the problems are fixed