When I reboot my phone, before the home screen shows up, the display says "Android is upgrading". It happens on every reboot even though I'm not wiping dalvik cache. Then after my phone gets past that screen, my wallpaper gets erased and changes to a black wallpaper. I'm on stock rom 4.2.2, rooted, and franco Kernel 134. I already checked to see if I had scripts in init.d, but I don't. Wiped the entire phone and started fresh, but it still happens.
Sent from my Nexus 4 using Tapatalk 2
Related
I tried changing the font with font changer. When it turned back on, the touch screen was unresponsive. The tab would keep restarting itself, and when it booted to the lockscreen it would just stay unresponsive until it restarted again. I got into recovery and wiped data, cache, and dalvik and installed another rom (I was using AOKP M4 and tried going back to Build 26). About a minute after going through the gapps setup, the screen became unresponsive and the looping started again as usual. I tried going to M4, Build 26, and Build 27 countless times and wiped those three things repeatedly but I always get the same result. What do I do?
You probably need to restore using ODIN
might work
prinzmetal6 said:
I tried changing the font with font changer. When it turned back on, the touch screen was unresponsive. The tab would keep restarting itself, and when it booted to the lockscreen it would just stay unresponsive until it restarted again. I got into recovery and wiped data, cache, and dalvik and installed another rom (I was using AOKP M4 and tried going back to Build 26). About a minute after going through the gapps setup, the screen became unresponsive and the looping started again as usual. I tried going to M4, Build 26, and Build 27 countless times and wiped those three things repeatedly but I always get the same result. What do I do?
Click to expand...
Click to collapse
Clean out everything: cache, user data (if possible, wipe everything from the sdcard partition)and then try another rom N if that still doesn't work then I think ODIN will be your best friend!
Odin worked...thank you!
So i rebooted my phone today, because screen didn't shut of when in call, but after reboot, phone is stuck at 4 color dots. I tried all bunch of stuff, but to summarize, i did wipe everything with fastboot and flashed stock 4.4.2 and 4.4.0 with fastboot/toolkit/flash-all.bat....and while every flash seems to finish ok, i still can't boot device (i waited 30 minutes on 4 color dots)
Any idea what the problem could be?
tnx
teva said:
So i rebooted my phone today, because screen didn't shut of when in call, but after reboot, phone is stuck at 4 color dots. I tried all bunch of stuff, but to summarize, i did wipe everything with fastboot and flashed stock 4.4.2 and 4.4.0 with fastboot/toolkit/flash-all.bat....and while every flash seems to finish ok, i still can't boot device (i waited 30 minutes on 4 color dots)
Any idea what the problem could be?
tnx
Click to expand...
Click to collapse
When you said you wiped everything, did that include the system partition as well?
Sent from my Nexus 7 (2013)
Yes...everything cleared, with toolkit and manually with fastboot.
Funny thing...i just tried flashing stock 4.2.2 and everything went ok. Phone booted to OS and after some poking around i did OTA to 4.3. Now, i'm stuck again at X boot screen. I read some users have this problem, but i just don't understand why this happens on "empty/cleared" phone.
Try to mess arround with some app that changes screen values, like brightness, saturation, etc. Fauxclock has this feature and supports presets, such as Franco.kernel app.
I know one member that could run 4.2.2 but nothing higher because his imei was blank. Does your phone have a valid imei #?
teva said:
Yes...everything cleared, with toolkit and manually with fastboot.
Funny thing...i just tried flashing stock 4.2.2 and everything went ok. Phone booted to OS and after some poking around i did OTA to 4.3. Now, i'm stuck again at X boot screen. I read some users have this problem, but i just don't understand why this happens on "empty/cleared" phone.
Click to expand...
Click to collapse
Sounds a lot like the same problem I'm having here...
http://forum.xda-developers.com/showthread.php?t=2590357
teva said:
So i rebooted my phone today, because screen didn't shut of when in call, but after reboot, phone is stuck at 4 color dots. I tried all bunch of stuff, but to summarize, i did wipe everything with fastboot and flashed stock 4.4.2 and 4.4.0 with fastboot/toolkit/flash-all.bat....and while every flash seems to finish ok, i still can't boot device (i waited 30 minutes on 4 color dots)
Any idea what the problem could be?
tnx
Click to expand...
Click to collapse
When I flashed 4.3, I couldn't get past the "X" boot screen. I wiped cache using recovery, it worked for me.
Try this guide
http://forum.xda-developers.com/showthread.php?t=2010312
Short and sweet. I haven't used SetCPU for awhile and I've been using the ROM in my sig, which isn't entirely stable. Though I went to set the CPU to max 1890Mhz just before I went to use Titanium Backup to do a huge compressed backup. So it makes it a little faster. I accidentally (honest accident) swiped to the end of the list on available CPU frequencies.. I think the highest was like 2334 or something.. well the phone crashed at something like 2035. I rebooted it and it booted up fine, but there had been some noticeable changes. Some apps I had frozen had been unfrozen, some apps had lost their settings etc. I figured this was due to a bad shut down.
Today I was asleep and I left my phone like usual so the alarm would ring. When I woke up I dismissed the alarm and the phone hung for a good 20 seconds. Then 3 apps updated and the phone crashed whilst browsing the play store.
Now when I tried to boot I got that typical vibration that something had got unresponsive in the background and was crashing. (Whilst at boot logo) It was just doing a loop of that. Then I rebooted it myself again and now it does nothing. But it still was stuck at the logo forever.
So I went into PhilZ recovery and wiped everything. Dalvik, Cache and Wipe to Install a New ROM.
Now it won't even GET to the Booting Logo and just stays on the 'Samsung Galaxy S4 Gt-I9505' screen..
So gradually my phone is retreating into an even worse position.
Is there a chance I could have blown my CPU or something with overclocking by accident for a few seconds?
Nope, you shouldn't have blown a cpu, since it was working afterwards. Seems more like hangs due to some bad wipe.
What you can do is try to install any rom and make a full wipe. If that doesn't work apply a new kernel.
If that doesn't work. Try install stock samsung rom (no wipe)
If it's still in boot loop (do full wipe) however if you got any saved data do the last step if you're sure nothing else works.
[I'm helping to tell developers how they can protect their app from being pirated and how they can protect it, in that way you can consider to not worry about your app being patched. too many developers have a bad protection.]
I didn't set it to 'Apply on Boot' because it was only meant to be a temporary overclock.
I just took the MicroSD out now and I am going to put the latest release of the ROM I am using on it, flash it and see if it works and flash the modem too to try and get some more stability out of it. I'll see how that goes, if it doesn't get off the 'Galaxy S 4' screen I am going to have to assume there's a big problem...
Well then there can be something else, if you haven't sent it to apply at boot it can be some kernel issue or something got stuck. It seems like there's something that blocks you from booting the phone up. Interesting,
[I'm helping to tell developers how they can protect their app from being pirated and how they can protect it, in that way you can consider to not worry about your app being patched. too many developers have a bad protection.]
boot into recovery.. wipe /system, /data and /cache then install rom from external sd card
I was on paranoid android 4.44 and switched to art. The next day the phone restarted while I was taking panorama picture. I had never taken panorama pictures, so I don't know if it is the camera app or art. Eventually the phone would reboot and turn off. I did a wipe of data, dalvik, etc and that did nothing. I then reinstalled paranoid android ROM and reinstalled and the Same problem. I wiped again and this time I installed slimrom, and the exact same thing happens.
Tries to load ROM, for a couple of seconds it shows optimizing apps square and then turns off. If I turn device on again, the same happens. It doesn't matter which ROM I use. Any ideas? Prior to this, my paranoid android ROM ran flawless for about two weeks. Before that I was testing different roms .
Suggestions??? I searched the forum, but couldn't find this specific problem.
I have a nexus 4 and I use twrp 2.7.1
Sent from my SM-T320 using Tapatalk
Have you tried flashing factory image?
Yes. I figured what it was. If I connect the phone to the wall, it stays on. It is either the battery or something to do with getting energy from the battery.
I have a rooted Nexus 6P, on stock 6.0.1.
Before yesterday, I was running the newest Franco Kernel on Verizon.
Last night I switched to AT&T, and this morning realized that when I try to open the camera it stays on the black loading screen with the white camera icon,
I re-flashed boot, vendor, system and cache images but it's still doing it.
I deleted the camera app data and cache, but still no luck.
Any Ideas?
Lightshield said:
I have a rooted Nexus 6P, on stock 6.0.1.
Before yesterday, I was running the newest Franco Kernel on Verizon.
Last night I switched to AT&T, and this morning realized that when I try to open the camera it stays on the black loading screen with the white camera icon,
I re-flashed boot, vendor, system and cache images but it's still doing it.
I deleted the camera app data and cache, but still no luck.
Any Ideas?
Click to expand...
Click to collapse
Try a fresh factory image. If it still does it with that then you may have faulty hardware.
Sent from my Nexus 6P using Tapatalk