So, I have a rooted 1st gen FireTV (aka bueller). I have no recollection what I did to it long time ago when I rooted it, other than it worked fine but was stuck on old software (5.0.x?). So I wanted to run newer apps on it, and I updated it with 5.2.7.3 rooted image. It reboot, went through the 10 min "system storage and applications" and was working, new UI and everything.... but when I tried updating the apps, it complained that the app store is too old. A few minutes later it rebooted.....and did the same "optimization" gig for like 10 mins.... then it rebooted, and now it reboots over and over, sometimes doing optimization, sometimes not, and sometimes I see the UI come up a second before it reboots again. TWRP bootloader works, so I can try flashing it back with older FW, I but I really would rather go forward. Any way to find out what is happening? I tried ADB, but it does not seem to connect when "optimization" is running
Thanks
hichhiker said:
So, I have a rooted 1st gen FireTV (aka bueller). I have no recollection what I did to it long time ago when I rooted it, other than it worked fine but was stuck on old software (5.0.x?). So I wanted to run newer apps on it, and I updated it with 5.2.7.3 rooted image. It reboot, went through the 10 min "system storage and applications" and was working, new UI and everything.... but when I tried updating the apps, it complained that the app store is too old. A few minutes later it rebooted.....and did the same "optimization" gig for like 10 mins.... then it rebooted, and now it reboots over and over, sometimes doing optimization, sometimes not, and sometimes I see the UI come up a second before it reboots again. TWRP bootloader works, so I can try flashing it back with older FW, I but I really would rather go forward. Any way to find out what is happening? I tried ADB, but it does not seem to connect when "optimization" is running
Thanks
Click to expand...
Click to collapse
FWIW, Several more re-flashes back and forth and a wipe, and it is now working
Related
I've recently started having trouble with my N7100 freezing/locking up.
I bought it shortly after launch, so it's a little over 1 1/2 years old. I had flashed one of the first rooted 4.1.2 firmware that was available, and never bothered updating because it was stable and got great battery life and I didn't feel like dealing with ROM stuff. But recently with the official 4.4.2, I decided to finally update, and decided on trying out DN3. So I flashed the latest TWRP, did the usual backing every thing up, flashed the MJ5 bootloader, and flashed it. It kept bootlooping, so I figured something went wrong, so I restored my 4.1.2 backup. This was where the freezing began. It was to the point where I couldn't use it. Tried rebooting a few times, but every time it would freeze as soon as it booted or shortly after. I assumed something just went wrong with the backup, so I tried flashing DN3 again. This time it booted successfully, but would occasionally freeze, most often when loading an app, but sometimes just randomly. After a couple days it seemed to subside. Then I decided to try out OmniRom. Same thing -- it would occasionally freeze up, then after a while would be fine. (Note: these were both clean installs.) Seems like every time I'd flash an updated version of Omni, the freezing issue would flare back up. Just now, I flashed the latest homemade build, and the freezing was really bad again, to the point where I can't even use it. Sometimes it'll freeze the instant it finishes booting, sometimes it'll freeze a few seconds after, sometimes it'll finish booting and will be fine until I load an app, then would freeze, and sometimes it would be fine for a couple minutes and the just freeze randomly. What's odd about it is that the screen is still responding to touch. Every thing's locked up, but when I touch the screen, the capacitive buttons light up as though it's still working fine, but nothing else works. I've even had a couple times where I let it sit for about 10 minutes and then it started responding again.
What's really frustrating is that I can't find a common cause here.Started on 4.1.2 (which had never had any issues beforehand), continues on a clean install of DN3, and continues on a clean install of OmniRom. Disabling Xposed and removing my SD card had no effect. It boots fine into recovery and download modes.
Does anyone know what the issue could be here?
EDIT: And now I've done a complete wipe, again, and reflashed DN3, again, and it appears to be working fine. Go figure.
It's not suddenly death?
see this: http://forum.xda-developers.com/showthread.php?t=2093599
sorry my english
Just recently my LG G4 H815, rooted, bootloader unlocked, v10b, has been acting strange.
I installed boot manager a couple of months ago and it has been running fine, but a couple of days ago I noticed pop up notifications saying a variety of apps were "added to boot manager"
I dont know where these apps are installing from and I cant find them in any folders.
Yesterday my phone crashed and after starting up again showed a "android is starting... optimizing apps 1 of 233" which seems a lot more than i have seen before. This made my boot time about 6 minutes
Today at work my battery died, (this is was because I fell asleep before charging my phone the night before) and when I charged my phone back up it showed "...apps 1 of 244". My phone was then on the "Starting apps..." Screen for 3 minuets. This made the boot time around 8-9 minutes.
I hadn't installed any apps between now and then and I did not see any pop up notifications.
At the moment I am scared to turn of my phone in fear of it taking even longer so I have 2 questions,
What is happening?
Do you need any further information to help me resolve this?
Thanks!
Best shot would be to factory reset your phone
roobns said:
Best shot would be to factory reset your phone
Click to expand...
Click to collapse
if only it were that easy.
more in this thread
Update: I seem to have gotten past the problems after updating to 10n. Now running stock debloated 10n rom with no reboot issues (so far)
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
So I have a T-Mobile LG G4 that like every other G4 had the bootloop problem when I got it. I sent it to LG and they promptly fixed the issue. My current issue has nothing to do with the bootloop I believe.
Because the G4 wasn't getting the Android N update fast enough and also because I wanted to play around with Android's full potential, I decided to root the phone a little over two weeks ago. The process worked and I decided to install a custom ROM. That also worked. I have installed four or five custom ROMs built on Android 7.1 without issue, or at least without any major issue.
However last night I decided to flash Genysis ROM on Android 6.0 because I wanted to play with Xposed. I made a full Nandroid backup of the CRdroid ROM it had been running and then wiped and flashed it using TWRP. When I installed the ROM it didn't work for whatever reason, freezing up and frequently becoming unresponsive. Over about 30 minutes I managed to enable USB debugging and reboot it to recovery (why I didn't shut factory wipe it from bios I'm not sure).
Now any ROM I try to install doesn't boot up. It never gets past the OS loading screen with the ROM logo. On 6.0 ROMs it says it has optimized the apps but gets stuck on starting them. The Nandroid backup I made does the same thing, even ones I made early that day and one from several days ago.
The backups had that one app installed that shows the logcat while booting up and while I'm no expert it seems to get a loop loading the audio drivers. I don't know if that's the cause or if it's just coincidental, as I've never heard of audio drivers preventing a boot, albeit my experience is with Windows PCs.
If it would help I can attempt to take a picture of the screen while stuck, although the text moves very fast. I can access the TWRP recovery just fine but don't know how to/if you can dump logs.
Any help would be much appreciated! I can attempt to supply an information that may be needed as well.
merger3 said:
So I have a T-Mobile LG G4 that like every other G4 had the bootloop problem when I got it. I sent it to LG and they promptly fixed the issue. My current issue has nothing to do with the bootloop I believe.
Because the G4 wasn't getting the Android N update fast enough and also because I wanted to play around with Android's full potential, I decided to root the phone a little over two weeks ago. The process worked and I decided to install a custom ROM. That also worked. I have installed four or five custom ROMs built on Android 7.1 without issue, or at least without any major issue.
However last night I decided to flash Genysis ROM on Android 6.0 because I wanted to play with Xposed. I made a full Nandroid backup of the CRdroid ROM it had been running and then wiped and flashed it using TWRP. When I installed the ROM it didn't work for whatever reason, freezing up and frequently becoming unresponsive. Over about 30 minutes I managed to enable USB debugging and reboot it to recovery (why I didn't shut factory wipe it from bios I'm not sure).
Now any ROM I try to install doesn't boot up. It never gets past the OS loading screen with the ROM logo. On 6.0 ROMs it says it has optimized the apps but gets stuck on starting them. The Nandroid backup I made does the same thing, even ones I made early that day and one from several days ago.
The backups had that one app installed that shows the logcat while booting up and while I'm no expert it seems to get a loop loading the audio drivers. I don't know if that's the cause or if it's just coincidental, as I've never heard of audio drivers preventing a boot, albeit my experience is with Windows PCs.
If it would help I can attempt to take a picture of the screen while stuck, although the text moves very fast. I can access the TWRP recovery just fine but don't know how to/if you can dump logs.
Any help would be much appreciated! I can attempt to supply an information that may be needed as well.
Click to expand...
Click to collapse
why not start from 0 and flash latest KDZ with LGUP.
https://forum.xda-developers.com/tmobile-g4/development/h811-kdz-file-t3607807
For sure I'll try that. I'll let you know if it works, thanks!
Follow up- I eventually found the free time to work on this and flashing the kdz worked! I actually had to use LG Bridge as LGUP only found my device as unknown.
Thanks for the help! Back to flashing ROMs for me.
So about a few years ago, I tried to root my galaxy note 4 (n910aucu2doi3), but I guess it rejected the root because it instantly bricked my phone, to the point where I had to completely wipe it using android recovery. The only way to get my operating system back was to download it online and install it through my PC (I had to find the exact version for my phone as well, 5.1.1 at the time, because it rejected every single other version).
Everything seemed to be working fine, except that I couldn't install software updates on my phone anymore. It was permanently stuck on 5.1.1. It was a bit of an annoyance but I didn't think much of it at the time.
Fast forward to now, and I'm getting several signs that my OS may be corrupted. My phone is constantly freezing, crashing and restarting. Maneuvering through applications causes the phone to freeze for a few seconds before either restarting or crashing the app. I want to say it's definitely a software issue, but I did install a new battery recently and it was working fine for a few weeks, could that be the issue?
If not, I want to start over, but I'm not sure how, and I don't know if it's safe to do a factory reset on this OS. Is there anyway I can get a fresh stock version of an android OS that can also update?
Any help is appreciated, I'm pretty much desperate.
I manually updated to 6.0.1 with the help of this thread https://forum.xda-developers.com/note-4-att/general/updates-thread-t3663943
It seems to have fixed the issues so far, and my phone can automatically update again