Related
I'm making this thread to try and solve issues and problems with cm7 for problems that you can probably solve instead of posting 10 times and making a repeated question in the official thread of cm7 development thread
If you have any issues we can help each other, to start with I got the blue then green light on my first restart, but after wiping data and cache AGAIN (I already did it before installing from zip) it worked!
I had problems with the notification widgets, but after a few restarts it didn't dissapeared. So that problem solved by itself
I currently have the flash notification widget not working (and it works on camera but not on video recording) I don't know if it is a common problem from the beta 3 version (If someone knows I would be thankfull***) but meanwhile you can get the flash to work with this widget https://market.android.com/details?id=com.advback.ledflashlight&feature=search_result
The Wifi is working OK but it seems like the refreshing time of signal is too low (I get close to the wifi router and maybe there are 1min. until the small widget at the top fills up) and viceversa I get away from signal and it is remained full until 1 min or so.
edit:
For Gps small fix you can find in the page 123 this from AkkiandDefy:
1.Search FasterFix in the market and install!
2.Open it and choose your region the
3.Now theprogramm will install the right Config
4.And then install GpsFix and let him search
Don't be afraid..let him search longer(till he tell the right adress). Once fixed he will find it always faster.
Admin or mods if there is any problem with my thread let me know, I'm just trying to help
good Idea
just trying to help hehe my idea is to get the important information in the first post just done the flashing of the test2 for gps going to try right now
I was installing this, and it was all going fine, used the recovery thing here, it booted up fine. I then rebooted again to put on the googleapps as an update.zip, updated and now it gets stuck at the Motorola boot screen?
EDIT: OK, so I tried another data/cache wipe and installing CM7 again as update.zip, but have to use the default bootloader now and it says "signature verification failed". :S
did you instal the nordic version? 3.4.3 11 (the last one) flash this, then install superuser (with superoneclick) afterwards instal the clockwork (I used the same one as you) then wipe data, cache install beta 3, gapps and gps test 2 and reboot it should work
Viridis said:
I was installing this, and it was all going fine, used the recovery thing here, it booted up fine. I then rebooted again to put on the googleapps as an update.zip, updated and now it gets stuck at the Motorola boot screen?
I had the same error - i reflashed the 3.4.3.11 sbf with rsd lite
after that, rooted , instaled clockworkrecovery and booted into recovery mode to instal CM7
After installing CM7, i allowed to boot itself (2init is set on automatic) then just reboot and enter into custom recovery via pressing vol down right after blue notification light appears - frome here you can acces custom recovery and install addons like gapps and gps fix.
Warning - entering from Clockwork recovery after CM7 installed will get you in bootloop and need to reflash the main sbf again.
Click to expand...
Click to collapse
really? I think I did it and it didn't happen that, but anyway my recomendation for those we don't know so much is to install from clockwork the beta, gapps and any fixes (gps etc) at the same time without rebooting so we don't have to use it anymore (in this logical order, 'cause maybe it doesn't mind but maybe it can prevent us from getting any error)
Thanks for the replies everyone.
Right now I've flashed 3.4.3.11 on with RSD Lite, that went fine. I've rooted with Superoneclick and installed the custom recovery app from before, and I can get into Clockwork recovery with that.
Now though when I try to do a wipe it says "can't mount /dev/block/mmcblk0p2 (File exists)" and "error mounting /sd-ext/!". I took out my SD card and formatted and partitioned it with 500mb ext, 50mb linux swap and around 1.5GB FAT to see if that would help, but it hasn't. I did this with my PC, however I did use the one on the recovery before that, which was probably a bad idea. I didn't think to much of it since it should have only affected the SD card.
I think now I need to use ADB or something to fix this, I've also unrooted and rooted again. I also tried installing cyanogenmod before the mount errors when only an "app2sd" error was coming up on the wipe, but it didn't actually do anything, it just started up with the stock 2.2 froyo again.
EDIT: I tried just wiping and installing cyanogenmod.zip and gapps.zip anyway, but it just comes reboots with stock blur/froyo. I don't have any "update.zip"s or anything.
try wipe from stock. do: vol down + power and then when the ! appears with the android guy press vol down + vol up
afterwards you will get stuck in the moto logo. get out the battery, put it again and flash the nordic version 3.4.3 11 then enable adb and with superoneclick install root
IMPORTANT: NOW GET OUT ADB AND REBOOT
after reboot install clockwork and get the beta 4 and gapps into the sdcard,
then wipe data and wipe cache
install from zip first beta then gapps (if an error of line X appears and says installation aborted just try again it will work, happened to me several times) and reboot!
Hey, thanks for the thread.
I have a problem with FasterFix. Mine asks for root permission but it just won't load. Remains in black screen and does nothing. GPSFix opens, but don't sync.
Any ideas?
@Quarx
Thank you for the CM7 mod, I'm loving it.
Will post it to the original forum post once I'm able to.
And will buy you a beer
you made a really good point, fasterfix worked in beta 2 and 3 (installed it several times with some wipes) now that I've read your post and tried installing it it installed granted permissions but it doesn't run so it seems to be a beta 4 problem that wasn't present before!
mariosanoguera said:
you made a really good point, fasterfix worked in beta 2 and 3 (installed it several times with some wipes) now that I've read your post and tried installing it it installed granted permissions but it doesn't run so it seems to be a beta 4 problem that wasn't present before!
Click to expand...
Click to collapse
I hope someone post this on the main thread.
I just applied the *.zip(s) and the am loading in for setup, it seems to be working so far. The boot screen is AWESOME as always... setup seems a bit twitchy but hopefully I'll get it to work here soon. *crossed fingers*
I think Im starting to have the earphone piece problem
Quarx posted another version to the main thread. Downloading now. Seems like it doesn't need to wipe. Lets see...
It seems a little buggy for those who have green lens. I'm waiting with 4.0.
Can I delete this post?
Problems to edit the contacts
Hello.
I've had problems to edit the contacts, in my phone book.
I syncronized my contacs with the Facebook contacts. Have all of then in my contact list, but when i need to add a phone number to the contact, it says that i can't edit Facebook contacts in that device. I need to create a new contact and put the phone number in that new one, and that pisses me cause i will need to have 2 contact from 1 person, duplicating my entire contact list. And all my contat that are in my SIM card don't show in the MOD. I have downgraded and all the contacts now have reapered.
Please, if someone knows how to help, since i was using the Blur, and had all my contacts from Facebook before, editing and merging then when they are duplicated.
It seems like the camera is not THAT working. When I zoom in too much it crashes and I lose access to the camera.
Is Quarx even knowing about this thread?
Edit: I was listening to a song in PowerAmp, opened an YouTube video and all sounds gone, some process forced close and no sound was played until restarted.
Edit2: it seems like that DSPmanager forced close when YouTube opened. Disabled for now.
I've updated to beta4 and the only issue I have is with GPS. Just tested camera, video and flash and all working.
Edit: also issue with video playback... it jumps.
Sent from my MB525 using XDA App
I can't play any videos at all. Guess I'll be back to froyo till this is fixed.
Sent from my MB525 using XDA App
Hello,
I've installed Hensemod a few times now, without any problems the first time I boot the phone.
Only after that, when restarting or turning the phone on again, it takes very long to start, like it's installing again and then the internal memory is suddenly full, even though I had about 100mb when turning the phone off. Also, all apps I installed are gone. In the applications list (in settings) they seem to still be there, but they're all 0kb and there's no shortcuts to them in the programs overview... Like I said, I've installed the Hensemod a few times now, and every time this happens.
Anyone knows how to solve this? I really like this rom, I can finally install and update all apps I want without the phone becoming unusable because of full internal memory! Thanks!
Carolien
I used HenseModv3 is a nice ROM, u must have to wipe all the data, cache and dalvick cache in the CWM recovery section, then install the HenseMod ROM.
If any other problem, plz share.
I followed all the steps stated in the development forum post, it works fine, just cant restart the phone because it will stop working...
My phone just continuesly restart...
Plug off ur battery, then go to CWM recovery, try to intall any other/different ROM.
I install each ROM by above method,i didn't use fastboot uncheck option.
Never mind I was just being stupid... I wiped the cache partition and not the dalvik cache. Sorry about that! Let's see if it will work now. Installing rom at the moment.
And again... first boot worked fine, after that I'm stuck in a bootloop now... Just like couldzxz. Too bad! I'll have to try yet another mod. Hope the next update of hensemod will solve this!
yes, u can try different custom ROM if any problems with a particular ROM
wait for next updates from Henry_01
I got stuck in bootloop too. I reqlly like the rom but well.. :/
Sent from my HTC Wildfire S A510e using xda premium
Okay, i've seen your problems.
I've tested latest build, but didnt rebooted it.
I suggest you all use a previous version (3).
Problem can be also kernel related.
I don't have time now (exams), I will make a proper working build after some weeks.
Don't hesitate to post here further, I want to know if it is ROM or phone related.
BIG EDIT: i will include link for version 3.
Thanks to djpc for a new hack which will solve reboot/kernel/overclock problems.
Expect a build and a proper test on friday or saterday.
I will change links now so that you will get a good version lol.
Somehow, the fifth time in installed the latest Hensemod rom, it worked like a charm. I can reboot, have installed and updated all apps I wanted and still got like 90mb remaining. Fantastic! Finally after 6 months I have the phone I wanted.
First and second install I couldn't reboot
Third install I got stuck in a bootloop
Fourth install gapps crashed every 2 seconds (due to calendar and contacts synchronization)
Fifth install = perfect!
I don't know how it happened, I just kept on installing this one so I could copy another rom on the sd card since I don't have an adapter or card reader for it.
Thanks!
So, last week or a bit past last week, i flashed aokp JB build 3 and then franco nightly. I have Clockwerk recovery and flashed gapps. (Tutorial)
So now yesterday , my phone was fine. Around sometime in the afternoon after i replied a text , then an hour later my phone was off. I thought that was weird, so i turned it on and after the google logo, i'm stuck on the aokp logo. And can't get past it. I played a 55 MIN dota 2 game with the boot logo on. I'm quite a noob. So help me please?
kevinzone said:
So, last week or a bit past last week, i flashed aokp JB build 3 and then franco nightly. I have Clockwerk recovery and flashed gapps. (Tutorial)
So now yesterday , my phone was fine. Around sometime in the afternoon after i replied a text , then an hour later my phone was off. I thought that was weird, so i turned it on and after the google logo, i'm stuck on the aokp logo. And can't get past it. I played a 55 MIN dota 2 game with the boot logo on. I'm quite a noob. So help me please?
Click to expand...
Click to collapse
Probably nothing wrong with your device. I would guess it has to do with a bug in either AOKP or your custom kernel. Flash back to stock and I bet your device will boot. (Link is stickied in General or look in my signature.) You have to expect issues like that when you are running custom roms and particularly custom kernels. If you don't want to deal with those issues, I would recommend to stay stock.
efrant said:
Probably nothing wrong with your device. I would guess it has to do with a bug in either AOKP or your custom kernel. Flash back to stock and I bet your device will boot. (Link is stickied in General or look in my signature.) You have to expect issues like that when you are running custom roms and particularly custom kernels. If you don't want to deal with those issues, I would recommend to stay stock.
Click to expand...
Click to collapse
will this make my files be deleted? I would rather not have that happen please
kevinzone said:
will this make my files be deleted? I would rather not have that happen please
Click to expand...
Click to collapse
Did you read the link I pointed out? Read it again, particularly note #5 on optional items...
efrant said:
Did you read the link I pointed out? Read it again, particularly note #5 on optional items...
Click to expand...
Click to collapse
Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused.
If this is the ONLY way , then can you please tell me how to do this, i'm confused.
If there is another way on to get out of this boot logo aokp thingy, without losing data , please tell me.
Note: i dont know if i'm doing anything, but i backed up via the recovery CWM
then after i deleted cache and dalvik, then flashed aokp,franco and then g apps. And nothing happened
Bump please. i really don't want to wipe my phone
Reflash AOKP, the Kernel and GApps, You could also jsut reflash AOKP and GAPPS with no custom kernel. that should pull you out of the bootloop. If it does not pull you out of the bootloop you will have to find another rom based off of what AOKP is and try flashing that. Most likely right now there is a problem with your boot.img file or AOKP rom its self. if you just reflash everything like you are flashing a nightly you should be fine unless something else is work. After you flash everything like you do with a new nightly make sure you wipe cache and dalvik. If non of the above works you might have to wipe and start all over again. You do not lose your internal SD card data just your user data and system data.
Prod1702 said:
Reflash AOKP, the Kernel and GApps, You could also jsut reflash AOKP and GAPPS with no custom kernel. that should pull you out of the bootloop. If it does not pull you out of the bootloop you will have to find another rom based off of what AOKP is and try flashing that. Most likely right now there is a problem with your boot.img file or AOKP rom its self. if you just reflash everything like you are flashing a nightly you should be fine unless something else is work. After you flash everything like you do with a new nightly make sure you wipe cache and dalvik. If non of the above works you might have to wipe and start all over again. You do not lose your internal SD card data just your user data and system data.
Click to expand...
Click to collapse
Uhh i reflashed aokp, kernel and gapps. Nothing really. Two questions.
1. Anything else?
2. for the reflashing, i want to flash another rom, how do i put the files on the phone? Gnex doesn't have an sd card slot and i dont know how to access it on the computer if it is in recovery mode. So confused
EDIT: not entirely sure what flashing means, so what i meant by flashing in my case, was that i just re ran the zips. then reboot. Nothing . waited 5-10 minutes ish. Never had long bootups on my first try.
Bump please!
kevinzone said:
Bump please!
Click to expand...
Click to collapse
Please do not bump a thread more than once every 24 hours (see rule 16). Thanks.
As for your issue, I will say it again: the link I provided you has all the information you need to return your device to stock without wiping the data on /sdcard. You just need to take some time and read it carefully a couple of times instead of rushing through it. If you don't understand something, just ask. (What you had said previously: "Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused." says to me that you did not read the entire post and the notes. And note, if your bootloader is already unlocked, you do not have to unlock it again...)
efrant said:
Please do not bump a thread more than once every 24 hours (see rule 16). Thanks.
As for your issue, I will say it again: the link I provided you has all the information you need to return your device to stock without wiping the data on /sdcard. You just need to take some time and read it carefully a couple of times instead of rushing through it. If you don't understand something, just ask. (What you had said previously: "Hi, okay so it says that flashing wont remove data, then above on the top of the thread it says that it will erase everything. I'm confused." says to me that you did not read the entire post and the notes. And note, if your bootloader is already unlocked, you do not have to unlock it again...)
Click to expand...
Click to collapse
But there is a problem. I cant access the phone. Since it won't boot up i can't access it from the computer.. Or can i? There's no sdcard slot either
I have installed the rom of cfx_ace-4.2-BR11 & cfx_ace-4.2-SR1 and install all my apps, change my wallpaper and stuff, butt when I reboot my phone it resets to first installation (lose my wallpaper, my apps, and settings). Can someone help me with this? I really like this ROM.
I use a HTC Desire HD.
Did you a Fullwipe before flashing the ROM?
L3moon said:
Did you a Fullwipe before flashing the ROM?
Click to expand...
Click to collapse
Yes I did full wipe, dalvek & cache
Download again. Flash rom. Reboot. Wait a few minutes. Do your settings, reboot, flash gapps, reboot.
Technically, it doesn't really matter in what order you do it (I believe it so), some people swear by x or y method. In short, you should be able to flash the rom and gapps without needing to reboot in between and without loosing anything. It's odd that you are. After flashing both of those then download your apps, that is, if you use gapps.
Sent from a dream.
Tworan said:
Yes I did full wipe, dalvek & cache
Click to expand...
Click to collapse
Dalvik and cache is not a full wipe. A full wipe is system, data, and cache.
Yes i know, tried it still doesnt work. Installed another rom that One Works fine, going to try and reinstal the rom this weekend.
Sent from my HTC Desire HD using xda app-developers app
i wonder why when certain features are working on one release, some of those features can get problem in the next release?
what happened during the firmware/rom writing process?
yauchildchew said:
i wonder why when certain features are working on one release, some of those features can get problem in the next release?
what happened during the firmware/rom writing process?
Click to expand...
Click to collapse
Things just break sometimes. It's not as easy as it seems to make a ROM with so many features by oneself. If you're talking about GPS not working since SR1, that specific issue was because synergye's source code hosting site BitBucket merged some of his code together and messed things up, and he had to sort that out to get it fixed. That's what I remember reading. GPS and Bluetooth will be working in the next release.
@OP -
Something is messed up in your wiping/flashing process. No one else has the issues you described, save for the wallpaper resetting on restart sometimes. Like Teichopsia said, wipe properly and reflash ROM and gapps. You might think you're wiping correctly, but you might be doing it all wrong. There are many guides on what constitutes a full wipe. Report back here if it still occurs after full wiping and re-flashing properly.
Sent from my Desire HD using xda premium
First time trying anything like this on a smart phone. So tonight I did a "back to factory" restart to get the phone like it was when I opened it out of the box. Then I read about this ROM, and thought why not. So I rooted my phone, then installed the ROM. Everything went fairly smooth, and got the ROM working. My problem is I dont have a google play store app now, and I didnt sync anything, so I dont have any of my apps, nor do I have the ability to download them again. Any help with this?
@gregkneitas said:
First time trying anything like this on a smart phone. So tonight I did a "back to factory" restart to get the phone like it was when I opened it out of the box. Then I read about this ROM, and thought why not. So I rooted my phone, then installed the ROM. Everything went fairly smooth, and got the ROM working. My problem is I dont have a google play store app now, and I didnt sync anything, so I dont have any of my apps, nor do I have the ability to download them again. Any help with this?
Click to expand...
Click to collapse
Flash gapps. Linked in cfX OP.
I do have the gapps file downloaded. I just dont know how to get it on my phone and working. I used a ROM manager app for the ROM file.
From recovery, same way you flashed the ROM (except for the full wipe part; don't wipe.)
bananagranola said:
From recovery, same way you flashed the ROM (except for the full wipe part; don't wipe.)
Click to expand...
Click to collapse
Like I said, I didnt flash the ROM, I used a ROM manager app.I dont know how to get to the recovery screen. Could someone please help me out with a step by step. Keep in mind vol down + power doesnt put my phone into recovery
You need to use "adb reboot recovery" from your computer. There are several good adb guides; check the Ace Think Tank link in my signature. Then, depending on your recovery, find the option that says something like "install zip from sdcard." Use it, navigate to your gapps, and select it.
bananagranola said:
You need to use "adb reboot recovery" from your computer. There are several good adb guides; check the Ace Think Tank link in my signature. Then, depending on your recovery, find the option that says something like "install zip from sdcard." Use it, navigate to your gapps, and select it.
Click to expand...
Click to collapse
Figured it out, thanks!
Next question is I downloaded Gmail App, and it wont sync with my account. I login, and everything but it just sits at the screen saying "Waiting for sync, your email will appear shortly" I've waited well over 10mins and no sync. Ideas?
Have you set up your account in Settings? If you reboot between flashing the ROM and gapps you need to do that manually; it doesn't show a first boot thing.
bananagranola said:
Have you set up your account in Settings? If you reboot between flashing the ROM and gapps you need to do that manually; it doesn't show a first boot thing.
Click to expand...
Click to collapse
It appears I didnt. You solved the problem! Thanks a bunch. Sorry for all the questions.
Ok last question, will adobe flash player work with this ROM? If so how can I get it. I search the market and the app isnt there. And its not on my phone either
4.2 in general doesn't support flash. You could try searching for the apk and sideloading it. Make sure you enable installation from unknown sources in Settings - Security.
sashank said:
Things just break sometimes. It's not as easy as it seems to make a ROM with so many features by oneself. If you're talking about GPS not working since SR1, that specific issue was because synergye's source code hosting site BitBucket merged some of his code together and messed things up, and he had to sort that out to get it fixed. That's what I remember reading. GPS and Bluetooth will be working in the next release.
@OP -
Something is messed up in your wiping/flashing process. No one else has the issues you described, save for the wallpaper resetting on restart sometimes. Like Teichopsia said, wipe properly and reflash ROM and gapps. You might think you're wiping correctly, but you might be doing it all wrong. There are many guides on what constitutes a full wipe. Report back here if it still occurs after full wiping and re-flashing properly.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
So, when fixing one thing, the process could probably break some working features.
Hey everyone,
Whenever I decide to step away from stock and try a new custom ROM (latest being cm11), my phone won't go a day(well, more like 5 hours) without rebooting and hanging at the boot animation. I'm not sure if its the number of apps i install (like 30 including gapps), or something I'm missing, but its not limited to just one rom. I've tried miui, dirty unicorns, revolt, paranoidandroid, all great ROMS, but they don't LAST!
I'm really sorry if I seem like I'm repeating an already-asked question, but I've researched this problem and tried suggestions such as going back to stock and retrying, using Darkside scripts to wipe, wiping cache and dalvik cache and rebooting, wiping android.secure or moving apps away from sd card, etc. Nothing works. So for now I'm back on stock and not enjoying it I just wanted to know if theres anyone that might have any idea how to fix this?
Thanks!
EDIT: To sum up the thread so far, now instead of wiping completely everytime this occurs, i just need to do a battery pull to fix it. However, its really annoying to do 3-4 times a day. Another thing I might note is that my device is refurbished(mentioned below). I did more research and found some fix perms script reccommended by Real_Pariah, which was supposed to fix the issue. It didn't. Also same problem does happen with stock, I've just never stuck with it long enough to find out. At UltimaniumX's suggestion, I did a logcat, which is attached on the last post. Thanks UltimaniumX for your help so far!
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
UltimaniumX said:
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
Click to expand...
Click to collapse
Yep, that's correct. As for exact process, usually I just full wipe everything but sd, then flash.
For my kitkat roms(paranoidandroid, cyanogenmod 11, beanstalk), i flashed used cwm recovery 6.0.4.3. For jelly bean i used either twrp 2.4.4.0 or cwm 5.x(this was in earlier attempts as that was the recovery a guide on galaxys2root instructed me to flash to root stock in the first place). All used radio UVMC6.
Even on stock it happened, but I was able to fix by wiping cache and dalvik plus removing external sd.
When I first rooted, my major issue was getting the rom to get past the animation screen while hanging, and that still occurs, though lately I've been having some success using rom manager from stock to get to cm11(without ext sd). However that does reboot eventually. The first time I was able to fix it by wiping system, android.secure, cache, and dalvik and then reflashing, but it just happened again and that method doesn't seem to be working...
It's interesting that it's happening to all different ROMS that you install. There's a possibility that it's hardware related and not software related. Though I may not be the best to offer advice (since I've only been here for about a year), I recently installed Beanstalk after going through several troubleshooting steps that I finally resolved.
I know that my friend and I both have an SG2. We installed Jedi Knight 6 (which is an older ROM now) but one of the most important steps that he missed, was that he didn't leave his phone idle for 10 minutes after booting it up for the first time. I recall he had issues with apps not working, force-closing, and irregular reboots on his phone. This may or may not been an issue for you, but for awareness sake I leave it here.
If you want you can give Beanstalk another try since I have some experience trying to get it to work. Beanstalk requires you to use a very specific recovery, and I used TWRP 2.6.1.0 straight from the author's post. I wouldn't suggest using a higher version just because KitKat is new.
- I used INFAMOUS wipe cache to clear everything, and then I did a full wipe (including preload) using TWRP.
- Install Beanstalk 4.4 and the 4.4 GAPPS
- Boot and let sit for 10 minutes.
Once you know for sure that it's been 10 minutes, run the "Android Terminal Emulator" and do a logcat. Here's how to do it:
- Type su
- Type logcat -d -f /sdcard/logcat.log , it will save a .log file where your sdcard is.
- At this point, I guess you would have to leave it running until your phone decides to reboot. Then take that file from your SD and examine it on your computer.
http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat
See if that helps. Fixing Permissions may also help reset some of your system settings. If it does the reboot loop, try rebooting into recovery, Fix Permissions, and reboot it again.
Alright I'll try Beanstalk, nothing to lose except my cookie clicker progress
Funny same thing happened in stock but was fixed in stock recovery with simple data wipe. I remember about hearing someone downgrading to ics because of "jelly bean bugs", so if beanstalk doesn't work out I'll try that!
(Couldn't straight reply/quote cause I can't post links yet)
EDIT: can't find beanstalk thread, at least cant find one mention twrp, so i wasnt sure if i was on the right one
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
avbluestar14 said:
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
Click to expand...
Click to collapse
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
avbluestar14 said:
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
Click to expand...
Click to collapse
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
UltimaniumX said:
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
Click to expand...
Click to collapse
yeah, stock works fine. about the logcat..I had restarted to try and fix that home button issue like an hour after starting the logcat, which means i inadvertently stopped terminal. whoops. so, i will try beanstalk again, making sure to keep terminal running i guess. sorry about that! might as well see whats in the current logfile for now. also, yes phone is rooted.
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
UltimaniumX said:
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
Click to expand...
Click to collapse
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
avbluestar14 said:
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
Click to expand...
Click to collapse
well beanstalk restarted on friday, can't find anything significant in logcat except for sometimes a long list of apps with perm issues,,,even stock has this reboot problem, but a battery pull+cache wipe fixes it(i hope). After googling, many have this problem with jb... maybe ill try an ics rom or something
hmm, back on cyanogenmod 11, and when it stuck at boot, a battery pull did the trick...running logcat overnight.
Well, here's the logcat, perused through, not sure if the errors I'm seeing are normal or not...honestly I wouldn't know what's contributing to the random reboot, and I'm not reporting it to cyanogenmod because I'm not sure if its a fault of their rom, my phone, or me lol
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
UltimaniumX said:
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
Click to expand...
Click to collapse
Yep, logat was running up to reboot. It is a SGH-t989, ordered straight rom tmobile site refurbished. I still think its weird how a simple battery pull fixes it though, is it corrupted memory? or partitions? or some hardware on the device?
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
UltimaniumX said:
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
Click to expand...
Click to collapse
Ah I saw that thread, new plan of action:
1. Hard reset, go to stock, try it for a day, see if it randomly reboots.
2. If it does, get a replacement after Christmas since 90-day warranty. If it doesn't, try AOSP 4.1.2.
3. If AOSP 4.1.2 doesn't reboot, go from there.
Well, I'll make sure to update after I get through. Thanks again!
Well, RMA'ed and now everything's working fine, running latest beanstalk, so i guess some partitioning or hardware issue? Oh well, thanks for your help!