Related
I haven't found any solution with this. About 3 or 4 weeks ago my Evo went crazy so I rebooted and was missing many apps. I did a nand to another sense rom and every time I tried to install an app (either download or from sd card) it would reboot. The odd thing is, it only does it with sense roms. I can use CM 6 or 7 fine and install whatever I want. I was originally one Myn's rls5, I also tried the Fresh roms. I have non clue what's causing this, tried googling and all said clear the market cache or try an older market, which I've done both. Any help would be greatly appreciated.
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Don't use a backup. Flash a sense ROM and install everything manually.
Sent from my PC36100 using XDA App
shogun26 said:
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Click to expand...
Click to collapse
I haven't tried a stock rom yet, once I get things back up I'll find one and try it.
gqstatus0685 said:
Don't use a backup. Flash a sense ROM and install everything manually.
Click to expand...
Click to collapse
I can't install anything. period. as soon as I try to install any apk from my sd card or anything from the market that doesn't come installed in the rom, as soon as it "finishes" the installation part it will reboot, but not a full reboot, it will go out to the boot screen (but not all the way to the htc screen).
Since going from AOSP to Sense what was your procedure for flashing? Just want to make sure your starting with a clean slate.
- What steps to you take?
- Full wipe? Data, cache, sd-ext?
- SD format?
The more info you can give the better and maybe we can help you track it down.
Ive done the standard full wipe, data, cache, dalvik. I do that everytime between roms. Not sure what the ext does and in haven't formatted my sd card since then
Sent from my PC36100 using XDA App
Update - I flashed the stock rooted 3.70 and was able to install. This was after formatting my sd card. Then tried to flash Myn's rls5 again and had the same problems as before. Only difference is with the 3.70 I forgot the flash the radios, but still had a fine signal. I flashed the radio updates with Myn's. Any help/advice is greatly appreciated.
At this point all I can think of doing is unrooting your device and getting it completely back to stock, then try re-rooting and make a nandroid of your rooted, stock sense rom.
Maybe you can root through a different methods than what you did originally.
After that, try another sense rom, make sure the md5 checks out too.
Sent from my PC36100 using XDA App
What recovery are you using and what version? I thought there were known issues with ClockWork 3.x.x.x version of recovery not wiping cache correctly? If you are using ClockWork you might want to try switching to Amon_RA 2.2.1. to see what happens. There is also a zip floating around (which I have attached) that can be used to wipe everything, you may want to give that a shot then reinstall the ROM. I have not used this zip, so use it at your own risk as I cannot guarantee the results. I have read about others using this and it working just fine.
Hi all,
Have anyone experienced memory corruption before? (I think that is what is it, or maybe it is mount point failure?)
The symptoms:
1) Every processes in the background force-close: Google Framework services, Titanium Backup etc.
2) Launching a program that saves anything will force-close.
3) Launching a program will ask you to reconfigure its settings again.
The fix is to reboot the phone, and everything will be working again.
I am running the latest custom ROM from cowithgun (w/o OC).
What kind of system log file I can view to see what actually happens?
Any help/clue is appreciated. Thanks.
before thinking your phone is broke I would suggest, take the latest stock Rom ,do a full wipe (also Dalvick cache) flash it and see if your problem is gone.
good luck
AdliHebat, do you have any info for us? Did you solve it? What was the culprit?
No. But i have not yet have a chance to revert stock rom yet. I am living with it right now. Need a reboot every day.
Sent from my GT-I8150 using XDA App
_jis_ said:
AdliHebat, do you have any info for us? Did you solve it? What was the culprit?
Click to expand...
Click to collapse
It has now become very irritating to me. I suspected corrupted memory card or something like that. The custom ROM is using swapped sdcard, and I guess my sdcard is not very good.
So I have:
1) Create Titanium backup
2) Copy back files i needed to my PC from my sdcard
3) flash back stock 2.3.6 ROM
4) Format Sdcard, format internal usb
5) Root using update.zip method
6) flash CWM
7) Clear cache, clear data, clear dalvik through CWM
8) Remove unnecessary apps and restore my apps/data from Titanium backup.
Seem stable so far.
If you suspect SD card corruption, you can use Mini-Tool to do surface test, it's free and can be used for loads of useful stuff.......
http://www.partitionwizard.com/free-partition-manager.html
Just some update.
I have tried
1) latest oc-COW ROM with sdcard swap -- problem still there. USB Storage unexpectedly removed.
2) latest oc-COW ROM with sdcard not swapped -- no longer USB Storage unexpectedly removed, but apps will start force close, and in some apps it is telling you database read-only.
3) Go back to stock ROM -- rooted of course. Stable for 2 days.
4) Flash only oc-kernel from latest COW ROM to my stock ROM. Starts to have apps force close after 2 hours.
5) Restore back my nandroid backup of step 4, so supped to be the same like step 4. Hopefully this will last..
So no luck for me on running custom ROM so far. (I did make my own custom ROM without tweaks--remove and add apps and seems stable, but what the point)
Waiting for my class 10 micro-SDcard...
AdliHebat said:
Just some update.
I have tried
1) latest oc-COW ROM with sdcard swap -- problem still there. USB Storage unexpectedly removed.
2) latest oc-COW ROM with sdcard not swapped -- no longer USB Storage unexpectedly removed, but apps will start force close, and in some apps it is telling you database read-only.
3) Go back to stock ROM -- rooted of course. Stable for 2 days.
4) Flash only oc-kernel from latest COW ROM to my stock ROM. Starts to have apps force close after 2 hours.
5) Restore back my nandroid backup of step 4, so supped to be the same like step 4. Hopefully this will last..
So no luck for me on running custom ROM so far. (I did make my own custom ROM without tweaks--remove and add apps and seems stable, but what the point)
Waiting for my class 10 micro-SDcard...
Click to expand...
Click to collapse
Hi Dude..
I'm not going to make you afraid but i want you aware this issue
Did your phone doing force close to for only STOCK ROM ?
My friend phone have same characteristic as you..
Suddenly the phone had brick
It's not cause by flashing but by hardware also
I post in this thread
Regards
Rio Saputro said:
Hi Dude..
I'm not going to make you afraid but i want you aware this issue
Did your phone doing force close to for only STOCK ROM ?
My friend phone have same characteristic as you..
Suddenly the phone had brick
It's not cause by flashing but by hardware also
I post in this thread
Regards
Click to expand...
Click to collapse
No, mine only happens on custom ROM. Stock ROM is stable.
And it never restart.
I restart myself after those apps force close.
AdliHebat said:
No, mine only happens on custom ROM. Stock ROM is stable.
And it never restart.
I restart myself after those apps force close.
Click to expand...
Click to collapse
Ok that fine..
You use Titanium back up after flashing custom ROM right..
Probably it cause by not complete back up before
If you wanna try,
Just do factory reset after you flashing Custom ROM and install all apps without titanium backup..*homework
Regards
Rio Saputro said:
Ok that fine..
You use Titanium back up after flashing custom ROM right..
Probably it cause by not complete back up before
If you wanna try,
Just do factory reset after you flashing Custom ROM and install all apps without titanium backup..*homework
Regards
Click to expand...
Click to collapse
No, I full wipe from recovery (I use CWM recovery) and install everything fresh on every flash session nowadays. I don't trust Titanium backup anymore.
Yeah n in recovery wipe every single folder...system...data....under mount n storage (CWM)
Sent from my GT-I8150 using xda premium
andynroid said:
Yeah n in recovery wipe every single folder...system...data....under mount n storage (CWM)
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Now that you mentioned it, i never use the format/wipe menu under the mount and storage option.
Maybe next week...i want to convince myself the phone is stable.
I downloaded the Vision ROM and used ROM manager to flash 7.2. For one, it only found 10 of my apps in the market. But when I tried to install Titanium (or any other app), I got an error. I tried rebooting once and then clearing market data, but it was of no use. Any suggestions?
Someone suggested that it is gapps issue and that the previous 613 worked fine. How does gapps work? Are there more features in the later versions of gapps? Should I flash the ROM and gapps back to back in Recovery?
ashwinmudigonda said:
Should I flash the ROM and gapps back to back in Recovery?
Click to expand...
Click to collapse
You can try that, if it fails delete the Vending apk from /system/app or overwrite it.
ashwinmudigonda said:
.... But when I tried to install Titanium (or any other app), I got an error. I tried rebooting once and then clearing market data, but it was of no use. Any suggestions?
Click to expand...
Click to collapse
you can try going to the android market website, logging in and try installing the apps remotely. Sometimes if this works after a few hours the install from the phone starts working also.
What ROM were you running before you flashed 7.2 ? Was it an earlier CM or a different ROM ? Because if it was a different ROM you should have wiped before you flashed.
Sent from my Desire Z running CM7.
steviewevie said:
What ROM were you running before you flashed 7.2 ? Was it an earlier CM or a different ROM ? Because if it was a different ROM you should have wiped before you flashed.
Sent from my Desire Z running CM7.
Click to expand...
Click to collapse
I was on CM7.1 Stable.
I had a weird problem with the market (google play) too where it just force closed each time i opened it. To fix that, i just went to app management in settings and i uninstalled all the updates for the market, i then opened the market, went to the homescreen, waited a few minutes and google play was back. Since doing that, i haven't had any problems.
Maybe doing the same on your phone could fix the issue.
I tried doing this again. This time I went into CWM and did all the cache wipes and did a factory reset. Same error. I even tried to flash gapps 613 version and that also would not let me download apps.
I am trying to understand how the market works. It shows me all my purchased apps on the new ROM. What about my free ones? I know I can get it back from Titanium, but is that the only way?
ashwinmudigonda said:
I tried doing this again. This time I went into CWM and did all the cache wipes and did a factory reset. Same error. I even tried to flash gapps 613 version and that also would not let me download apps.
I am trying to understand how the market works. It shows me all my purchased apps on the new ROM. What about my free ones? I know I can get it back from Titanium, but is that the only way?
Click to expand...
Click to collapse
maybe try fixing permissions (had a guy come to #g2root having some problems with the market, and fixing permissions worked for him)
Ok got it to work! I flashed the ROM, went straight to Manage Applications and deleted App data under market. It works now. I wonder why.
ashwinmudigonda said:
Ok got it to work! I flashed the ROM, went straight to Manage Applications and deleted App data under market. It works now. I wonder why.
Click to expand...
Click to collapse
That's pretty much what i did when i had problems with the market and it fixed it for me.
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Do you by chance have a refurbished s2?
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app
es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.
es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...
I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.
DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.
Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte
my new HTC Desire Eye appears "Unfortunately, Google Play services has stopped" alot
i figure out i was flashed Gapps 4.4.4 yesterday to my stock Lollipop version and it's failed "BTW i though i selected the ROM cuz i'm newbie"
can anyone help me to make google play services back again in normal situation i can't use my device now
hiroxzima said:
my new HTC Desire Eye appears "Unfortunately, Google Play services has stopped" alot
i figure out i was flashed Gapps 4.4.4 yesterday to my stock Lollipop version and it's failed "BTW i though i selected the ROM cuz i'm newbie"
can anyone help me to make google play services back again in normal situation i can't use my device now
Click to expand...
Click to collapse
What rom are you using? Did you try a factory reset or going back to stock rom?
JuanArg said:
What rom are you using? Did you try a factory reset or going back to stock rom?
Click to expand...
Click to collapse
i still not using any custom rom yet it's the same rom come with device from HTC
yes i tried factory reset from Cyanogen Recovery and the problem still there
please help guys i'm bagging you i won't try anything i don't know again
If you're not using a custom rom why did you flash a custom recovery and gapps?
Make a factory reset from settings and not from recovery. See if that helps.
Do you have a backup?