Related
i have Slim's latest on my I777. i am having constant shutdowns & SOD's, like every few minutes. the twist is that i have had the same release of Slim on the phone before, several times in fact, and i had the occasional SOD, but not constantly like now. i have installed Slim a number of times because i like to try new ROMs, and i keep coming back to Slim cus i like JB.
this must be diagnosed, because i believe now that something was messed up a bit along the way of flashing ROMs, mods, and kernels, but our awesome ROM supporters in their threads have their limits they have told me, and i should ask here since this is a general question about the phone & system. i am seeking help here relating to the rest of the phone and system that may become damaged somehow, and i want to clean up my system to end this problem. logcat & last_kmssg linked below.
to be clear: i am rooted correctly, am running the right software for the I777, always check my MD5's from the phone before flashing, clear my caches when needed, wipe dalvik before flashing kernels, etc etc.
interestingly, i fully wiped/factory reset, formatted system, dalvik, wiped batt stats, and fixed permissions, then reinstalled stock Slim last night because i thought maybe my settings were trouble, so i decided to run an out-of-the-box Slim, changing only the dpi and launcher. no change.
i've tried Siyah's latest after running Jkay's kernel cleaner as well. no change. something is making my phone shutdown/SOD constantly, and it may not be the ROM. others don't seem to be having this issue. i have little running on the phone. just accuweather, Date in Tray Pro, and Apex Pro. no overclocking/voltage changes... nothing fancy at all. so i'm just perplexed.
here's the latest logcat: http://davidb.net/logcat_and_device_info(1).zip
here's the latest last_kmssg: http://davidb.net/last_kmsg
if any of you guys can help with this, then thank you in advance.
VR32 said:
i have Slim's latest on my I777. i am having constant shutdowns & SOD's, like every few minutes. the twist is that i have had the same release of Slim on the phone before, several times in fact, and i had the occasional SOD, but not constantly like now. i have installed Slim a number of times because i like to try new ROMs, and i keep coming back to Slim cus i like JB.
this must be diagnosed, because i believe now that something was messed up a bit along the way of flashing ROMs, mods, and kernels, but our awesome ROM supporters in their threads have their limits they have told me, and i should ask here since this is a general question about the phone & system. i am seeking help here relating to the rest of the phone and system that may become damaged somehow, and i want to clean up my system to end this problem. logcat & last_kmssg linked below.
to be clear: i am rooted correctly, am running the right software for the I777, always check my MD5's from the phone before flashing, clear my caches when needed, wipe dalvik before flashing kernels, etc etc.
interestingly, i fully wiped/factory reset, formatted system, dalvik, wiped batt stats, and fixed permissions, then reinstalled stock Slim last night because i thought maybe my settings were trouble, so i decided to run an out-of-the-box Slim, changing only the dpi and launcher. no change.
i've tried Siyah's latest after running Jkay's kernel cleaner as well. no change. something is making my phone shutdown/SOD constantly, and it may not be the ROM. others don't seem to be having this issue. i have little running on the phone. just accuweather, Date in Tray Pro, and Apex Pro. no overclocking/voltage changes... nothing fancy at all. so i'm just perplexed.
here's the latest logcat: http://davidb.net/logcat_and_device_info(1).zip
here's the latest last_kmssg: http://davidb.net/last_kmsg
if any of you guys can help with this, then thank you in advance.
Click to expand...
Click to collapse
Nothing jumps out at me but you need to backup your data and SDCARD to a PC, flash back to stock..... when stock boots up perform a factory reset and test with the stock firmware... if it work fine.... root and install the ROM fresh and clean and test without installing anything else. If it again is fine then install every app from the Market. if you want to restore your recent data afterwards that is up to you but There are so many variables that could be causing your issue and you need to step back and try to find the cause one step at a time.
shoman94 said:
Nothing jumps out at me but you need to backup your data and SDCARD to a PC, flash back to stock..... when stock boots up perform a factory reset and test with the stock firmware... if it work fine.... root and install the ROM fresh and clean and test without installing anything else. If it again is fine then install every app from the Market. if you want to restore your recent data afterwards that is up to you but There are so many variables that could be causing your issue and you need to step back and try to find the cause one step at a time.
Click to expand...
Click to collapse
thanks shoman. much appreciated for the tips.
You wouldn't happen to be using an aftermarket phone charger would you? I was working on a phone behaving like that and it was the charger. If you lifted up on the plug a little while plugged in, it would wake the phone from sleep and constantly restart it. It also did something to the ROM or possibly the Kernel cause it started restarting while not plugged in and the power button quit working. I used a known good Samsung charger and installed AOKP JB with the kernel that came with and it fixed everything. I replicated this problem with two different chargers. It is possible that the USB port on the phone was worn. However, no matter how I moved the cable with a Samsung charger, nothing bad would happen.
beaverslayer said:
You wouldn't happen to be using an aftermarket phone charger would you? I was working on a phone behaving like that and it was the charger. If you lifted up on the plug a little while plugged in, it would wake the phone from sleep and constantly restart it. It also did something to the ROM or possibly the Kernel cause it started restarting while not plugged in and the power button quit working. I used a known good Samsung charger and installed AOKP JB with the kernel that came with and it fixed everything. I replicated this problem with two different chargers. It is possible that the USB port on the phone was worn. However, no matter how I moved the cable with a Samsung charger, nothing bad would happen.
Click to expand...
Click to collapse
no I've never used one.
but it appears this was all caused by the app Screen Off And Lock by Katecca. I had the donate version. its always worked for me on every ROM up through ICS, but it seems to wonk out JB. I changed to Lock Screen App by Kenneth Cheng and have had zero problems in days now, which is a first.
Sent from my SGH-I777 using xda premium
Ok, I know some other people posted about black screen but all the other threads seem to be about it happening after a call.
Mine happens when the phone been sitting for a while with the screen off (and it's not all the times) it seems more prone to it if the screen been off for longer times.
I tried two different roms with two different kernels both have the cpu idle speed setup at 384 or more. As soon as I flash they seem to work ok but after a day or so the freaking black screen comes back. I also have pimp my rom installed with the "no black-screen after a call" tweak ticked.
I've went through the process of unrooting going all the way back to stock and start from the beginning all the way from unlocking the bootloader to S-off.
Downloaded fresh copies of the roms zip files
I don't think it's any of the apps since this does not start right away it takes a day or so after everthing been runing (but I might be wrong).
Obviously it's not the rom or the kernel since it does it with two different ones, what else is there that can be messing with my phone???
It's driving me crazy!!!!
Can it be hardware related????
I'm lost with this, and started thinking on a new phone already but I can't buy it until mid 2013 so I don't want to give up yet (actually can't).
This been working just fine up until a month ago or so, it's just now that the black screen started harrasing me.
Edit: It just happened again and since I could not get the screen up, I decided to pull the batt and when I turned the phone on again I got the vibration but the screen didn't light up during booting at all until I pressed the button few times.
Could my screen be dying?
ferincr said:
Ok, I know some other people posted about black screen but all the other threads seem to be about it happening after a call.
Mine happens when the phone been sitting for a while with the screen off (and it's not all the times) it seems more prone to it if the screen been off for longer times.
I tried two different roms with two different kernels both have the cpu idle speed setup at 384 or more. As soon as I flash they seem to work ok but after a day or so the freaking black screen comes back. I also have pimp my rom installed with the "no black-screen after a call" tweak ticked.
I've went through the process of unrooting going all the way back to stock and start from the beginning all the way from unlocking the bootloader to S-off.
Downloaded fresh copies of the roms zip files
I don't think it's any of the apps since this does not start right away it takes a day or so after everthing been runing (but I might be wrong).
Obviously it's not the rom or the kernel since it does it with two different ones, what else is there that can be messing with my phone???
It's driving me crazy!!!!
Can it be hardware related????
I'm lost with this, and started thinking on a new phone already but I can't buy it until mid 2013 so I don't want to give up yet (actually can't).
This been working just fine up until a month ago or so, it's just now that the black screen started harrasing me.
Edit: It just happened again and since I could not get the screen up, I decided to pull the batt and when I turned the phone on again I got the vibration but the screen didn't light up during booting at all until I pressed the button few times.
Could my screen be dying?
Click to expand...
Click to collapse
have you ever considered its the tweaks your doing to your phone.. have you tried just flashing the rom and running it without doing the tweaks... not every phones hardware is identical so not all tweaks might work... ive flashed a rom recently that experienced some boot loops after doing some tweaks to the rom, and now im running that rom flawlessly without any tweaks...
---------- Post added at 12:01 AM ---------- Previous post was at 12:00 AM ----------
you might also want to try the rom with the default kernel that comes with the phone not faux which i'm assuming your using
To be honest, no I haven't thought of that.
I just re flashed everthing, if the problem starts again I'll remove all the tweaks.
But the thing is the phone was working well and one day without changing anything it started with this. But I'll try removing the tweaks if this persist
Thanks,
Nope, it wasn't the tweaks.
Fresh flash, no tweaks and I still have to press the on button many times to get the screen to turn on
which rom are you using again?
I'm on NRG blue but I tried the Bulletproof for a while and it did it too that's why I'm thinking that is not rom related. It has to be something deeper than the rom.
Phone was working great until last month that I travelled abroad.
As soon as I got to the country I was visiting I put a local sim card and it took me a while to be able to boot, to the point that I had to restore from a backup.
Then during the time I was there I had several random reboots (like once or twice a day).
When I came back I swapped the sim again and no more reboots but after a week or so I started with this black screen problem, it was really bad to the point when sometimes I needed to pull the battery off to see if that helped and the rom got really screwed (I think sense got screwed because the screens were doing weird things). So I reflashed, it fixed all the weird things but not the black screen.
Now it's not as bad (I only need to press 3 or 4 times the button) and it's not alway, only if the screen been off for a while but my previous experiencest tells me that it will get worse in few days time...
okay i have a few suggestions.. do you do a full wipe when you flash a rom? wipe data/factory then format system then wipe cache partition's then wipe delvik cache.. and you should try going back to stock completely then trying a different rom and see.. its about testing all possibilities before coming to the conclusion your phone is damaged somehow
yes I always do a full wipe and/or the 4ext wipe and clear dalvik and cache. Not sure about the factory reset since I wasn't sure where that would take me.
you should try going back to stock completely
Click to expand...
Click to collapse
Do you mean relock, S-ON and goall the way to GB? or to ICS T-mous stock??? I did go to ICS (this one) http://d-h.st/3VD but I can do it again (I can alway use some practice with these procedures...)
I
you dont have to S-ON again i mean Stock ICS from your carrier.. and stock Ruu's are located in my signature if that link is one you got from there go right ahead... and try and flash back to stock, if you need instructions let me know
Ninjistix said:
you dont have to S-ON again i mean Stock ICS from your carrier.. and stock Ruu's are located in my signature if that link is one you got from there go right ahead... and try and flash back to stock, if you need instructions let me know
Click to expand...
Click to collapse
I did that yesterday and yes the ruu Iused is the same as the one listed there as most recent.
I just found an interesting discusion on the faux kernel thread about a problem, with the earlier version (which is the one I was running when the whole thing started) and that happened to me before this black screen.
This is the thread http://forum.xda-developers.com/showthread.php?t=1359951&page=232 and it's mentioned in the quote on post #2316 and ahead.
I PM'd AJ to see if he thinks this could be related since in one of his posts he said something like reverting to stock won't help (for some reason)
but overall from what i just read... the issue seems to be related to the faux kernel.. i only flashed it once but ii didnt do any tweaks,, i mostly use the stock kernel that comes with most of the rom's i flashed... here's what to try... in 4ext wipe all partitions except sd card, then wipe both sd card partitions internal and external.. toggle usb storage and flash this super wipe script in recovery.. then flash a different rom and don't flash faux.. test the rom out to see if your problem occurs again.. or flash the super wipe then place the ruu on the SD card then attempt to flash back to stock
Try this thread and see if it will help your situation.
http://forum.xda-developers.com/showthread.php?t=2070438
Double0EK said:
Try this thread and see if it will help your situation.
http://forum.xda-developers.com/showthread.php?t=2070438
Click to expand...
Click to collapse
I'll try it.
Thanks,
Tried that and didn't help, but thanks for the suggestion.
What I noticed today is that since Icouldn't get the screen on no matter how many times I pressed the darn button I pulle dhte batt out and then rebooted the phone to see if that helped and even though I got the little vibration confirmation when the phone boots up there was no white HTC splash screen or bootanimation whasoever, anyway since I could still not get the screen on I tried the same thing a few time and then once I finally managed to the the screen on I said int the bottom left corner SAFE MODE (never seen that one before). I'm running Bulletproof reloaded now.
Oh and the batt was kind of low (may be 20%).
Wow!!!! I do own a very messed up phone!!!
Today this piece of crap threw a total temper tantrum.
Would nos turn the screen on no matter what. I removed the batt and not even rebooting to the point that when I finally got it to boot it had an internal SD error. It didn't allow me to format, wipe or partition it from bootloader or recovery.
Now I'm at home so I flashed stock RUU (again) and it seems like its running one more time but I was really close to throw it over the cliff where I was Flying my RC gliders.
We'll see if I can make it last a bit longer...
so its working once again, cuz you said you flashed back the stock ruu right?
Yes,it's alive (will for how long this time). I flashed stock a couple of times , I unlocked once again, flashed 4ext, flashed JP hboot, superSU, NRG rom, supersu again (since IO wasn't sure in which order I should have done this) flash rom 2nd time, flashed Faux's v 24 (twice) and Downloaded most of the apps clean from Gplay.
I'm getting a lot of practice with this, who knows, may be one day I become good at it
its good your practicing now, but don't forget to do backups before you flash anything to your phone, this this way you'll have a stable install to restore back to incase anything goes wrong again
I been doing more tests and yesterday I run it on stock most of the day with no apparent issues, then I restored the NRG rom from a backup and still no issues so I started to think it was something I messed up flashing the JB Hboot, I moved to a bulletproof rom and decided to do another test.
I sat on the phone as to block signal and the issue came back.
Now I'll try the same with NRG, yep it seems like it's when the phone loses signal the screenwon't come back afterwards.
I'll try the same in stock rom next...
Yes, it did it in stock too but not so bad, it seems like after few attempts the screen worked againgvs. on bulletproof didn't
Ok, I found this in some other thread...
[QUOTE8. Black Screen - Phone will not wake-up
I'm accidentally find out and solved the problem of Black Screen during in-coming call (BulletProof 2.2.0). By replacing the service.jar from the previous version (BulletProof 2.1.0) with the intention to get rid of the CRT file in my system, by doing this I am also discovered that the black screen problem is gone. However, this problem can be easier solved by simply dis-able the screen-on/off animation setting instead of replacing the service.jar with the one from previous build which doesn't have CRT.
It's worth to be note that during my old days with the HTC HD2 running Nandroid I've encountering similar problem of black screen when waking up the phone and it was caused by the CRT as well. This, at least happened to me with more than 3 Rom, including the famous AmeriCanAndroid, HyperDroid and Tytung's ...
So if you are experiences Black Screen problem, please check to see if you did flashed the CRT and/or enable it? ][/QUOTE]
Can somebody tell me to how do I check this?
Thanks,
OK guys I got a question and I hope that someone can help me out here. I've been google-ing, looking for a similar issue and asking this question in couple of threads and after not getting an usable answer I decided to make a thread about my issue. My S3 emmc is the unfamous SDS affected one and I've been experiencing some lag and freezing so here's what I did with my phone at first:Flashed 4.1.2 XXELLA firmware, Rooted with-CF-Autoroot, flashed PhilZ Recovery v.4.35, Stock kernel.To get a clean installation I flashed the 4 file rescue firmware including PIT file and everything was working perfectly fine...no more freezes or random reboots just EVERY 2-3 days my notification bar used to get totally stuck/gone. Doing no matter what-restarting systemUI...etc,etc I couldn't pull the status bar down anymore until reboot.Tried stopping touchwiz home, clearing cache and dalvik, fixing permissions but it happens again in 2 days of mild-moderate use(web, games, texting, voice calls) Flashed again the XXELLA 4.1.2 firm.from sammobile.com.Changed the kernel as suggested by someone here on xda and it was ok for a while when using Siyah kernel v1.8.9+ until the next day when it happened again. It comes out of the blue just after doing whatever...at first I thought that is somehow related with the Triangle Away app that I used to reset the flash counter but it happened again even after I deinstalled the app. 2 days ago I wiped cache and dalvik, factory reseted the phone and updated it with the new I9300XXEMB1 uk firmware. It was running flawless until today when I faced the same frustrating issue. Out of nowhere after unlocking the screen I tried to pull down the notification bar to turn on wi-fi when..whoa!-there is no notification bar!again. I contacted Samsung U.S since there I got the phone this summer but they told me they don't have any tech support fot the I9300. It is driving me insane...what else should I try..tried hard resetting the device couple of times, tried different roms, different kernels all that is within my range of knowledge and this is my only hope that someone out there will give me an answer or suggestion. Any help will do good, thanks in advance.
Anyone?
Anyone out there please?
I experienced a similar issue, but it haa an explanation, Iwanted a black status bar, not the std dark gray one, then flashed a themed statusbar, when I rebooted, the status bar was gone, Ihad to reflash the rom (crdroid v 11), to recover the statusbar, finally found a theme with black background and white not light gray indicators, (LLC_XXEMA1_2_Jkay_framework_14_9blk statbar), and this one runs perfect, I now our problem is differnt, but give it a try, flash a statusbar theme, maybe, it will work for you, Im not giving you links, because it depends of your rom an framework, luck
Thanks I'll give it a try if I cannot stick to stock as close as possible then I'll try another custom rom like CM 10.1 or a themed status bar...For now the only "solution" to get back the notification bar is to use ROM Toolbox and with the rebooter to restart SystemUI-then it comes back. Uninstalled Dolphin Browser since I noticed that is the only app that I use prior losing the status bar (I might be just guessing idk for sure)
Finally I found a solution for my issue with the phone - SOLD IT! It was driving me insane with the constant status bar loss, no matter what stock firmware after the 4.1.2 jb update or kernel it used to run. Here on the forum I got no answer addressing the exact issue and I think that was the only solution. Bought a Nexus 4 and I really like it. Faster, smoother, better build quality, and I think I can live without the expandable memory and removable battery. Probably that was the last Samsung device I`ll ever buy until they start to manufacture a real quality products and start acknowledging and fixing the issues that follow them. Thanks to everybody here on this site for the help....
I think
I think it's the Custom ROM's SystemUI.apk problem reflashing with the same ROM would not help, i suggest to reflash the device to it's stock ROM and flash it again to your Desired ROM.
iAlexander said:
I think it's the Custom ROM's SystemUI.apk problem reflashing with the same ROM would not help, i suggest to reflash the device to it's stock ROM and flash it again to your Desired ROM.
Click to expand...
Click to collapse
Tried everything my friend...reflashed to stock million times, flashed recovery firmware with pit file. Reverted back to stock with kies, downgraded, upgraded, changed different stock ROMs - nothing helped, felt disappointed and started to hate the phone cause it was driving me nuts so I sold the device and got myself a Nexus 4. I never regret of doing so, much happier, more satisfied overall with this beautiful device. Faster, no bugs,no lag, more quality materials used...now what is left is to convince my girlfriend to follow my steps as she started to experience the very same issue on the newest XXEMB5 firmware on her SGS3.
After flashing a new version of CM11, i found myself in a loop upon startup where many of the core applications of android stopped working. When i reverted back to the old version that worked(I didn't have a backup saved but rather i flashed the older nightly of the rom again), I noticed that my home button, lock screen, and notification bar/toggle screen wasn't working any more. I looked into it and looked at my apps, and saw an unnamed app with the description "com.android.keyguard". upon looking this process up, i found out that when people disabled this process their home button, lock screen, and notification bar stopped working (coincidental eh?), and decided that this was the source of the problem.
Is there any way to load on a new, fresh version of "com.android.keyguard" or should i just do a factory reset? I would prefer to save my local data, but if i must do it in order to have a phone that does anything useful, i obviously will.
If I need to do a factory reset, what is the cleanest and smartest method of doing so? I know titanium backup can cause a lot of problems (and in this case i'm worried it will duplicate com.android.keyguard), but I assume there is some sort of method that makes a factory reset while retaining the bulk of user data very easy. am i correct?
Do a full wipe and flash again, check the md5 of your download.
Only use titanium for use apps, never system apps or settings. There is no easier way to change rom.
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Jahid4 said:
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Click to expand...
Click to collapse
Flash back to stock and start over.
Beamed in by telepathy.
For those who want to get in on CM12 pronto, here is a straight-from-CM-source build. The usual disclaimers: I'm not responsible for anything going wrong, including but not limited to bricking your tablet, requiring reflashes, or the NSA spying on you.
I will update this post with new builds as I create them every day or two, depending on what changes are merged: http://review.cyanogenmod.org/#/q/status:merged+branch:cm-12.0,n,z
If something doesn't work, I doubt I can help you, I'm not developer. I just ran the build and installed it on my Nexus 7 to see if it works (it does!). No cherry picks, just merged CM ROM/Kernel. However, if something doesn't work, post it.
What works: Everything stock plus a few CM features.
What's broken: Some people report data connection problems
What's here (1/03+):
Battery % indicator in notification bar, choosable icon
A bunch of behind the scenes stuff
Trebuchet
Status bar brightness control
Single-down swipe for settings panel for swipes on the right side of status bar
Privacy Guard (including Privacy section in settings)
CM File Manager
Advanced Reboot
CM Superuser controls
Double-tap status bar or lockscreen slider to sleep
Notification light controls (including custom lights for individual apps)
Codec enhancements
Option not to have the screen wake on plug
ADB over network
Voice wakeup
Lots of CM app Material design changes
Requirements:
Latest bootloader installed via fastboot
The ROM from here: 1/06 - https://www.androidfilehost.com/?fid=95887005526787409
Old versions:
1/05 - https://www.androidfilehost.com/?fid=95887005526786861
1/04 - https://www.androidfilehost.com/?fid=95887005526786862
1/03 - https://www.androidfilehost.com/?fid=95864024717074739
12/31 - https://www.androidfilehost.com/?fid=95864024717072947
12/29 - https://www.androidfilehost.com/?fid=95864024717071892
12/24 - https://www.androidfilehost.com/?fid=95864024717069216
12/22 - https://www.androidfilehost.com/?fid=95864024717068185
12/21 - https://www.androidfilehost.com/?fid=95864024717067734
12/19 - https://www.androidfilehost.com/?fid=95864024717066366
12/17 - https://www.androidfilehost.com/?fid=95857557620393232
12/18 - https://www.androidfilehost.com/?fid=95857557620393643
GAPPS: http://d-h.st/l6z
Latest TWRP
Instructions:
The usual: Backup, Wipe, Flash Zips.
If you have problems downloading files after you flash this, follow the steps listed here: http://forum.xda-developers.com/showpost.php?p=57295498&postcount=89
I DID NOT DO ANY OF THIS WORK. ALL THE CREDIT GOES TO:
The CM Team
Chainfire
TheMuppets
The testers: nazafalas, skynet11
Cheers
I tried the 12/17 build but got bootloop city even though I had already been running a Lollipop ROM. I was grilling some buffalo wings (woohoo!) at the time so I had waited well over 20 minutes. I'm trying again so I can try to grab a logcat if it doesn't boot this time.
Edit: Oh snap! This time it booted! Thanks for your hard work to everyone involved ��
The LTE radio seems a bit wonky, being disabled until I toggle airplane mode on and off again (after which it seems to work fine). Also, it gives some 5-digit number for my carrier as opposed to saying "Verizon Wireless." I tried to grab a logcat but it didn't contain anything useful. Sorry ?
bootloop
lolo696 said:
bootloop
Click to expand...
Click to collapse
Flash again. Someone else had the same problem. Let me know if it persists.
skynet11 said:
The LTE radio seems a bit wonky, being disabled until I toggle airplane mode on and off again (after which it seems to work fine). Also, it gives some 5-digit number for my carrier as opposed to saying "Verizon Wireless." I tried to grab a logcat but it didn't contain anything useful. Sorry ?
Click to expand...
Click to collapse
Carriers have unique ID codes. Apparently matching up those codes to their respective carriers hasn't been done yet.
Thanks for the heads up on the radio.
Wipe cache and dalvik is needed for first install, then no problem with boot.
Works good, thanks
Working fine. Thanks for supporting DEB
Working VERY fine. No radio issues for me, German APNs seem to be in order, as well.
deb build
Full wipe works best from km 4.04. Great so far with everything working to plan. Not used cm since my Xoom days.
First of all, THANK YOU for supporting deb! :fingers-crossed:
I tried to dirty flash over an existing AOSP install first (I know, bad Ambious) and obviously it didn't boot very well (it actually started deodexing, then stuck at 'Starting apps').
So then I went back to recovery, full-wiped, flashed clean.... and nothing. Endless boot (people throw the term 'bootloop' around where it's actually just a boot hang).
Tried clearing cache, dalvik, fix permission even - to no avail.
I also can't logcat because the CM default requires manual authorization... :/
(I have everything backed up so it's no biggy, I just really wanted to try it).
Any tips?
Ambious said:
First of all, THANK YOU for supporting deb! :fingers-crossed:
I tried to dirty flash over an existing AOSP install first (I know, bad Ambious) and obviously it didn't boot very well (it actually started deodexing, then stuck at 'Starting apps').
So then I went back to recovery, full-wiped, flashed clean.... and nothing. Endless boot (people throw the term 'bootloop' around where it's actually just a boot hang).
Tried clearing cache, dalvik, fix permission even - to no avail.
I also can't logcat because the CM default requires manual authorization... :/
(I have everything backed up so it's no biggy, I just really wanted to try it).
Any tips?
Click to expand...
Click to collapse
flash your previous ROM again, flash CM12 over it, and if it gets stuck on "starting apps" again just do a normal reboot. It's really weird how a simple reboot after one of these lockups works better than starting over from scratch. I've only rarely ever seen this be the case, and I've been flashing custom ROMs since the Eclair days.
Bum, now stuck in boot whatever, I'll try a reflash later.
skynet11 said:
flash your previous ROM again, flash CM12 over it, and if it gets stuck on "starting apps" again just do a normal reboot. It's really weird how a simple reboot after one of these lockups works better than starting over from scratch. I've only rarely ever seen this be the case, and I've been flashing custom ROMs since the Eclair days.
Click to expand...
Click to collapse
Amazing how the simplest of solutions sometimes pass by us.
It actually worked
Thanks!
Can some people test GPS for me? Thanks!
Worked fine for me last night even indoors.Not got round to a reflash today though so on kk at the moment, not sure why it wouldn't boot up this morning even with a soft reboot.
Clean flashed 19 build and gapps, all working as it should,no issues with 3g,GPS or videos so far.????
GPS works great for me ?
Mmmm battery stats saying 4hours left o 82%, better watch that.
As soon as you turn it off and back on it goes into bootloop or sticks on upgrading app.