Re: [BeanStalk][1.179] Phone freezes after call
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
bretcb said:
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
qkster said:
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
Click to expand...
Click to collapse
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
bretcb said:
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
Click to expand...
Click to collapse
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
qkster said:
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
Click to expand...
Click to collapse
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
bretcb said:
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
Click to expand...
Click to collapse
yeah...for the most part, while in cwm, factory reset, wipe system, data, cache, dalvik and then flashing a new rom work very well.
occasionally, for what ever reason that i'm not sure, going back to stock..changing file system back to rfs and then changing back to ext4 may be needed to fix certain problems...not common and not routine practice, but is needed...at least imo
OK, fair enough. I will read up more on going back to stock so I'm not unfamiliar with it. Which tool do you prefer?
For completeness of troubleshooting info for anyone else who may be reading, I received a phone call yesterday while the lock screen was disabled, and the phone still froze after the caller hung up. I received another call today, and made sure I hung up first, and no freeze, my phone was fine.
Sent from my SGH-I997 using xda app-developers app
bretcb said:
I will read up more on going back to stock..
Which tool do you prefer?
Click to expand...
Click to collapse
Everyone has their own prefs...I prefer heimdall. It doesn't matter. Whatever it takes to get the job done. You prolly should buy a usb jig too.
http://forum.xda-developers.com/showthread.php?t=1437548
Related
I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernals...
Is anyone else having this problem? This kind of makes sense for me.
TeldenW said:
I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernals...
Is anyone else having this problem? This kind of makes sense for me.
Click to expand...
Click to collapse
That should not be the case. The only difference in a refurbished handset is the model number. Other than that, and the fact is is previously used but everything reflashed to stock by LG or TMO, the ROMs should work the same as a DW model phone.
jboxer said:
That should not be the case. The only difference in a refurbished handset is the model number. Other than that, and the fact is is previously used but everything reflashed to stock by LG or TMO, the ROMs should work the same as a DW model phone.
Click to expand...
Click to collapse
I'm all out of ideas then... Do you have any idea why I'd have so much trouble loading other ROMs?
Like I mentioned, I'm no pro, but I've Flashed enough ROMs to think that I'm "good" at it.
I'm completely stumped.
TeldenW said:
I'm all out of ideas then... Do you have any idea why I'd have so much trouble loading other ROMs?
Like I mentioned, I'm no pro, but I've Flashed enough ROMs to think that I'm "good" at it.
I'm completely stumped.
Click to expand...
Click to collapse
Before flashing a new ROM did you do a factory data reset, format the system partition and clear the Dalvik cache? If not you will have problems as you described. You need to wipe the phone clean between flashing different roms. If upgrading to a new version of the same rom you might get away without a wipe. But if you are changing roms the steps I mentioned above are essential or you will often get bootloops or the phone will lock up during boot.
jboxer said:
Before flashing a new ROM did you do a factory data reset, format the system partition and clear the Dalvik cache? If not you will have problems as you described. You need to wipe the phone clean between flashing different roms. If upgrading to a new version of the same rom you might get away without a wipe. But if you are changing roms the steps I mentioned above are essential or you will often get bootloops or the phone will lock up during boot.
Click to expand...
Click to collapse
JBoxer, I make SURE to Reset/Wipe/Format/Clean everything EVERYTIME.
That's what I can't get figured out. I've been meticulous about it!
And I still get the frozen bootscreens and the lock ups.
Any other ideas?
Are you using rom manager because mine does that unless I use the cwm I installed from my computer
Sent from my LG-P999 using xda premium
monte666 said:
Are you using rom manager because mine does that unless I use the cwm I installed from my computer
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I'm using the NVFlash method.
Best ROM I found with the least problems
TeldenW said:
I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernels...
Is anyone else having this problem? This kind of makes sense for me.
Click to expand...
Click to collapse
the Best I've found if you want gingerbread style is Hellfire phoenix
or if you want ICS style is Hellfire sandwich v1.6 (which is what I am using for a while now)
the only problem that I found is the video camera but other than that everything else works fine on my G2X. they update couple times a month for the last 4 months so they are always trying to make things better for their users. if you have problems they are more than willing to try to help you with it. if you are using with a simple mobile setting it has a funny setup but it work very good (better wifi & phone signals)
adeptustech said:
the Best I've found if you want gingerbread style is Hellfire phoenix
or if you want ICS style is Hellfire sandwich v1.6 (which is what I am using for a while now)
the only problem that I found is the video camera but other than that everything else works fine on my G2X. they update couple times a month for the last 4 months so they are always trying to make things better for their users. if you have problems they are more than willing to try to help you with it. if you are using with a simple mobile setting it has a funny setup but it work very good (better wifi & phone signals)
Click to expand...
Click to collapse
Second that but i'm on the GB til video can work good
Sent from my LG-P999 using xda premium
My original g2x could handle oc and UV big time, anything the devs put out . My replacement can only handle kernels with stock voltage and oc is unstable anything past 1.1ghz. So to answer your question, may be a coincidence or may just be bad luck on our part. Remember, not every processor is created equal despite being the same phone. I get tempted to get an additional replacement every once in a while but laziness tells me otherwise.
Sent from my LG-P999 using xda premium
TeldenW said:
JBoxer, I make SURE to Reset/Wipe/Format/Clean everything EVERYTIME.
That's what I can't get figured out. I've been meticulous about it!
And I still get the frozen bootscreens and the lock ups.
Any other ideas?
Click to expand...
Click to collapse
Possibly cleaning and wiping everything soo good that you clean the new rom right off your sd card?? lol. just a thought. ive done that when i 1st started flashing roms. or possibly flashing gapps on roms that dont require you to?
edit: i just realized how old this post is. lol
the reason refurbs night have worse luck is because of all the people who send their phones back because of that, they make up a reason to tell Tmobile and get a nice shiny new one. The old one is reset and passes all the "official" stability tests and gets sent out again.
Sent from my LG-P999 using Tapatalk 2
I am unlocked and have the recovery of twrp 2.3.3.0. I'm having problems with about every single rom I flash. I wipe everything as you are suppose to and the flash appears to go well but usually right away after the rom boots up the system becomes unresponsive. I have to hold my finger over a button for a couple seconds for it to acknowledge a touch and things just don"t run right.
Its like either the system is almost locked up or the touchscreen just hardly works.... one of the two. I made a backup of my original asus setup and if I restore it the tablet works just fine. I've tried hydro, cm 10.1, blackbean 7, and one or two I'm forgetting. AOKP RC1 is the only custom rom that gives me no problems at all in this regard, unfortunately its an unfinished rom, no camera and my battery dies like crazy with it...
The 2nd best running rom that I really like from what I have seen is blackbean 7. Runs great for first few minutes but after playing a game for a bit or doing some other things and having it run just great all the sudden the dreaded problem occurs and the only fix is a reboot for it to work for a while longer. So frustrated at this point as I have flashed so many roms and resetup so many things just to find myself doing it again trying to fix this and find a rom that works for me.
Any ideas at all on what could do this? Is the difference in the kernels the reason why AOKP RC1 and Asus original work but none of the others? Or does it have to do with my recovery? Fairly certain I have the correct most recommended one with twrp 2.3.3.0 and the process went fine. Any ideas greatly appreciated. I really just want to be able to run blackbean. And knowing that most all roms will not work for me is rather disturbing in regards to the future. Really wanting to like my new tf300t but its making it hard:silly:
Try to downgrade your recovery.
Use this : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
and take a feedback after, thanks
I really appreciate that you took the time to give me something to try but I'm afraid it didn't work. Process went fine I'm on 2.3.1.0 twrp but same problem. First rom I've tried instant non-responsive. Any other ideas?
I've been using ClockWorkMod Recovery on my TF300T, and it's been great. (Used it to upgrade my ROM to CM 10.1.) No issues at all.
If you need instructions for getting it installed on a TF300T, check out my second-to-last post on thoughtsontechnology.com. (NONE of the work is mine, I just compiled the instructions and links in one spot for easier access. Most of the work came from XDA contributors, they've been really great.)
Most roms need 5 to 10 mins to stabilize after a new install, usually as they are building media storage files, etc. Are you giving them enough time?
Failing that I can only think your microsd has something corrupt on it. Boot with it out.
Well I tried cwm again flashed it no problem installed rom no problem but no fix. So guess we have established it definitely isn't the recovery at this point...
Yes I've given roms several reboots and lots of suffering them working for 10min to only fail again for another reboot... So its not that. Still the only Rom that will work is my backup of the original asus and the AOKP RC1. Trying it without the external sdcard right now.
Well no joy on the removal of the external sdcard
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
sbdags said:
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
Click to expand...
Click to collapse
Not sure what a full wipe is? I wipe cache/dalvik system format data and have even tried formatting the sdcard once several roms ago. One thing I have noticed since I am trying so many roms all the time is the sdcard file structure seems odd as I have at the root of the sdcard a 0 directory that continues to be added to. Currently it goes sdcard/0/0/0/0 to actually get to where I have things stored like music, downloads. Is this normal? Its strangely repetitive.
Personally I think you should stop using TWRP if you're having all these issues. Just flash CWM and have fun
touchscreen
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Showme1 said:
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Click to expand...
Click to collapse
Sounds like you have a hardware fault if the issue persists across multiple firmwares.
Also, OP said his SD card directory structure was strange. I'd format both internal and external SD in recovery (in addition to wiping and factory reset) before you flash.
Thanks! Wiping internal has seemed to do the job. Still would like to know what the issue was. I was thinking it was the touch panel firmware, but thought that would be in /system
Sent from my SGH-I747 using xda app-developers app
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
That's pretty much it
Unfortunately that's pretty much it. Your phone information should eventually stick (dunno why, but it does eventually) but if it doesn't then try another clean install. (btw have you made a backup of your imei, that might help a little as well.) I've had this problem many times and these work for me pretty much every time.
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
IamMark70 said:
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
Click to expand...
Click to collapse
ive been having this issue when i tired both roms so i ended up on cleanrom and then went over to beans for now due to it been base off of clean rom and having the asop look and feel of a aosp rom and the features of touchwiz and the stabilizability of it
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
IamMark70 said:
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
Click to expand...
Click to collapse
yep its pretty good rom i like it. im kinda having a issue with my picture messages though but probably had a dirty flash when i chose the aosp mms. if you like touchwiz also check out cleanrom its a great stock rom best stable rom and pretty great battery life as well and beans rom i think is based off clean well your welcome hope you enjoy the beans rom aslo i had issues with the sim card to so your not alone
IamMark70 said:
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
Click to expand...
Click to collapse
I downloaded Liquid Smooth 2.4, and it finally addressed the issue of the activation screen popping up after every reboot. So I'm extremely happy and loving the ROM!
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
I see that I have the Cyanogenmod Kernel installed currently which I suppose either is installed with Slimbean or it may have been installed because I tried the CM10 rom first, but it wouldn't boot.
what are you doing before flash the new rom?
juancaperez2000 said:
what are you doing before flash the new rom?
Click to expand...
Click to collapse
Wiping the device. Always best in the long run.
Sent from my Nokia RinGo far far away...
Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.
Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
Restore your stock rom format internal memory and flash clean rom ASAP brother you will be straight !!!
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------
And all the necessary wipes of course
Sent from my SCH-I535 using xda app-developers app
Cobinator said:
Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.
Click to expand...
Click to collapse
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash
andybones said:
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash
Click to expand...
Click to collapse
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.
Cobinator said:
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.
Click to expand...
Click to collapse
in theory AOSP ROMs should load faster than a Touch Wiz ROM as TW ROMs are around 1 gig for the ROM.zip and AOSP ROMs are about half that, but still I've had ROMs take over 15 mins to load, I know one time I thought it was the phone, but then I wiped fully again, and waited 20 mins and it loaded. I would say anything after 20 mins though, then it's definitely something wrong.
Ok backing stuff up then going to flash back to stock then try LiquidSmooth and see if it will let me boot up. Will let ya know how it goes.
So I install stock un-rooted rom. Then installed a stock rooted rom, then installed liquidsmooth and all I get is the Samsung symbol flashes then it goes black. Then it vibrates and the Samsung symbol flashes then blackness. Just repeats this over and over =(
I noticed you said that you're wiping cache and dalvik, but make sure you're also wiping data and system too.
Sent from my SCH-I535 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
My apologies moderator.
Anyways. I wiped everything on the phone before every rom installation. System restore, dalvik, and cache. The custom rom still won't boot.
I have an XT926 running KKBL CM11 nightlies and have been updating through Cyandelta since Towelroot gave me an unlocked bootloader (thanks Geo). I have been updating without issue until the 11/07 nightly. Ever since then, Cyandelta shows no updates but if I go through the CM Updater, it shows all of the updates released for the moto_msm8960. If I try to apply any of these updates outside of Cyandelta (either through CM Updater or flashing full zip through recovery), I can boot my phone but will start getting a persistent error saying "There's a problem with com.android.phone process and it has to close" or something to that effect. I have tried wiping both caches and even doing factory resets but the process crashing starts back within a few minutes of getting everything set up. I did notice that even though I did a factory reset, all of the apps I have installed still had data from before the wipe so I feel like the wipe is missing something that is causing the crash(?). I've been using custom ROMs for a while on a few different devices but this is the first time I've ran across this. Any advice?
Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.
CWGSM3VO said:
Nuke and pave.
Something is stuck and vaguely familiar to me but at this point, if it were me, that's what I would do. Just time consuming.
Click to expand...
Click to collapse
I've never had to go further than a factory reset before. Which partitions should I format?
I'd format system, data, cache and dalvik. Definitely time to flash clean.
When I had my XT926, I also found that after so many updates via Cyandelta, that I would get the same issue. I would then go back, clean flash the latest update and things would be good. I eventually stopped using Cyandelta altogether. It's a nice idea, but I just don't know if I completely trust its abilities in determining what to bring down and what not to. I'd rather go with the CM updater instead. Yeah, it means longer downloads, but which is longer: downloading the full update from CM and having it work, or downloading via Cyandelta and then having to wipe clean, install and then restore all your backups?
iBolski said:
When I had my XT926,
Click to expand...
Click to collapse
You did abandon ship!
lloydsw said:
You did abandon ship!
Click to expand...
Click to collapse
Yup, but I stated in my post (where I said my goodbyes), that I would still hang around and help out. I know there are a lot of people still on this phone, especially with CM12 now running on it.
But, loving my G3. Still on stock, though (4.4.2), but I have no reason to go to anything else right now. Runs smooth, but it is rooted so I can run TiBu and also enable SD writing. But, I have no other reason to go to CM12 at this time.
I can get at LEAST one day if not more. Usually, after 24 hours, I'm right around 50% on battery. I probably could go even longer, but definitely I get more battery life out this phone than I did on the XT926 (non-MAXX), but I was able to do the same on my non-MAXX, but only if I didn't use it much. With the G3, I can do quite a lot and make it through the day without having to recharge during the day. I love that!
In any case, I'm still lurking about these forums to see if anyone needs help.