So I'm running into a wall on this.
https://play.google.com/store/apps/details?id=com.square_enix.ff7g_bike Updated a week ago to 1.2.0, and prior to that it would run fine (if a bit laggy at times). But since installing the update (required to play) it won't run. I'll tap on the icon, it'll load and show in the background with other running apps, but just won't run proper? I even updated to Android 4.4.4 cm-11-20141112-SNAPSHOT-M12-d2lte, from 4.4.2), used the Triangle Away app to reset things so the phone wouldn't appear to be custom/flashed, and still doesn't work.
I tested the update on a friend's S4 (un-rooted) and haven't had the same issue.
Is my phone (SGH-T999) just too old/no longer supported? The S3 is still on the device list: http://help.finalfantasy7-gbike.com/model but perhaps it wasn't updated.
So the last update to 1.4.0 at the end of April took care of the problem, which was great.
However..... they've updated to 1.5.0 today, and I'm experiencing the same exact problem I had prior to that update.
I don't know what to do, if there's anything that CAN be done.
Help, please.
Probably because you are using an aftermarket rom. Only thing I can suggest is to use a TouchWiz rom, or update cm. That zip is extremely old. Try the latest nightly. In case you didn't know, cm12 is available for the s3 under d2tmo in case you want to try it
It's possible.... so far unrooted/stock-rom devices are fine. However my friend let me root their S4 and that didn't cause an issue.
As for updating CM, I'll give that a try. I hadn't checked since March (and CM updater didn't give me any indications of a newer version oddly).
*edit* Ok I used TWRP 2.8.6.0 and updated to cm-12.1-20150614-NIGHTLY-d2tmo (along with gapps-5.1-2015-04-20-15-56-24), during the "Android is upgrading" screen (after a very long time on the CM splash) the phone rebooted.... currently back on CM splash screen... will edit in more details once beyond that screen.
*edit2* Past the CM splash, on "Android is starting".... optimizing apps 3 of 108.... and again with reboot.
*edit3* Again at "Android is starting" now optimizing app 198 of 199.... *fingers crossed*
*edit4* Finishing boot.... ok looks like I need to use a newer gapps... ok, updated to gapps-5.1-2015-06-02-15-19...
*edit5* Well everything appears to be working.... though the G-Bike game still won't load once updated to 1.5.0... it does at least switch to the horizontal position and the screen goes dark longer before returning to the homescreen... but that's about it. :crying::crying: Switching to TouchWiz may have no change either, correct?
*edit6* I've always used the default messaging app, but when I opened it it's seemingly stuck on "loading conversations", I read elsewhere that it may take a very long time to load if you have a lot of texts... which I guess given that one contact has 4,000+ texts saved in that thread, perhaps it's just a matter of time before all previous texts load?
A rooted rom shouldn't affect it. I mean aftermarket like cm or aosp. It could work fine on TouchWiz, especially since it's listed as a supported device. Yes, texts may take long time to load if you have many
Texts finally did load. I'm about to install CM on the S4, to see if the game no longer loads then. If that's the case, then I'll switch to TW on my S3 and hope that the game works afterwards.
Unfortunately I'm under a bit of some time constraint, the 1.5.0 update was for an event to gain a new support character, and that ends in exactly 1hr....
Given the time-frame, is there a "quick & easy" method to flash a TW rom without having to do various app data backups/nandroid backup (I will have to factory wipe, yes?), and not lose much/any data? I unfortunately don't have a high capacity SD Card (4GB, my 64GB one in the S3 stopped allowing write access a few days ago, seems to be an issue with that particular card), and 4GB isn't nearly enough to backup everything from the S3 to SD.
*edit* Well well..... 1.5.0 will not run on the CM rom on the S4!
You can back up to your internal memory. As long as you factory reset with custom recovery, you won't lose anything stored on it, except apps and settings
Great! One further question, is there any possibility that by switching ROMs, the game might think I'm on a different phone/new user (and if so, is there a way to fix this?)? Despite all the un/re-installs, I've never lost my progress most likely due to it being saved on their servers... but I'd hate to appear as a new user and lose month's worth of progress.
Yeah there's always that possibility. That's why you should always back up your apps with data so you can restore it in case
Thanks again. I wish I knew exactly what was being changed from version to version, that makes the game not work on an aftermarket rom. If it never worked from the beginning, that'd be one thing... but it's a yes/no/no/yes/no type of deal here. Shame I can't just take what works in the 1.4.0 version and compile it into the 1.5.0 ver... Or figure out what it's checking, and make it think it's a stock rom instead.
Related
The UK 3.4.2-117 froyo showed up not to be as stable as first seen, some apps crash all time and the phone to from time to time, especially the screens keeps to timeout alot and sometimes freezing the phone totaly when doing it.
Anyway, when trying to install the sbf rom with eclair 2.51 with RDS i am able to install it but not able to make the phone to start after that. Any suggestions to why, is this due to the current 2.51 eclaire version beeing branded? I started out with a 2.21 version before going to the new gb froyo rom. Pherhaps not downgradable meant exactly what it said
Thanks for suggestion...!
I have had no problems whatsoever with the UK Froyo release. In fact, I find it to be the smoothest release yet, as I have mentioned in its respective thread; Even without overclocking, it is a lot smoother than the Chinese Froyo and 2.34.1 and 2.21.0 before that. Ofcourse the quadrant 'score' is lower, but as I do not use my phone mainly for benchmarking, I do not mind in the slightest.
Anyway, before I go off-topic too far..
Have you made any modifications to the release after you put it on your phone? Did you perhaps not wipe the data/cache? Is it possible that you are overclocking your phone to such an extent that it is no longer stable?
And for some specifics - which applications crash all the time for you?
And indeed - you can not downgrade unless you've followed the instructions in this thread by Higgsy, but I doubt you have.
Incidentally, nor have I, but I have no problems whatsoever with this release and since we have the same phone, I suspect you have changed or installed something to cause your problems.
Hi!
Yes basically i got a new defy, UK retail, it was never rooted or anything and i just applied the new ROM with RDS. So no, I had not done any changes to the version what so ever and i reinstalled it twice, always making sure to offcoures wipe it also.
My main issue is actually that the screen times out alot, and sometimes locks the phone so i need to take the battery out. Also a music app (spotify) crash inevitably all time, it comunicates with the memory card as it catch up the music as you listen so thinkning that it may be some issue there. Have seen some of my other apps also force close, and this has never happen to me on this or my second (my gf's) defy i had had for some months now.
I to however are supprised about this as I can see that no other is experience this issue, espeically the screen timeout issue wich is very annoying and happens alot especially when using the browser
Will try to find a new microSD card later tonight to see if my memory card pherhaps have been somehow dammaged during the ROM installation... (dont belive at all this would have happend but worth a try i guess)
Thanks
Hm. That is quite the pickle you are in.
Can you install Catlog, filter on Errors, and tell us what it reports? You can run the application after you start the phone and have it log to file - you can put the file in
Code:
tags here to make it easier on the eyes. There may, or rather - should be a clue in there.
Alternatively, you can use 'adb logcat' from a command prompt in the Android SDK/platform-tools to get the log files to display outside the phone.
another reinstall of sbf did the trick! Will try to run the logcat to later to figure out what the app problem could be (maybe sd card read write issue I think as sameprobkem with second card) but now the phone works otherwise perfect, many thanks...
Good to hear - enjoy the shiny new release
Same problem help.
Hi I flashed the UK 3.4.2-117 froyo ROM with RSD.
My Defy was T-Mobile UK, 2.51 ROM.
After flashing the phone starts but I only get a black screen.
The softkeys are not responding but I can tap down the notification bar and open a task manager program that I had pre-installed which allows me to switch through applications. I can open various applications and the phone seems to be working like this.
I rooted successfully and then I tried to reboot into recovery using Clockwork Mod but the phones stays at the motoblur logo.
Is there anyway to downgrade or at least make this rom working?
Michalis
I have experienced some things like you sayed; some apps get closed, and frozen phone and can't even turn off the phone
so i uninstall some apps that i don't need, and get a app name SystemPanel that monitorize the CPU use to see whats going on
Since then, i don't see more those things. I'm watching see whats going on
As of recent, I've been having a ton of stability problems on my S2 across all ROMs. It will often get sluggish and randomly shut down, the WiFi will completely drop and I won't be able to connect unless I restart my entire phone, and various other problems. I've done a full wipe when installing any ROM and problems only came up when I installed cwm 6.0.4.3 and I was wondering if that may have been the issue. Either way, I was wondering if there was a way to completely wipe my phone and bring it all the way back to factory and how it came in the box so I can completely start over to try to fix these problems. Any other suggests would be greatly appreciated, too.
Currently running BeanStalk 4.4+, last "stable" build was with Cyanogenmod 10.1 nightly.
Thank you to everyone in the XDA Developer community, you certainly are amazing and thank you to the developers of the search function, I may not know how to use it to it's greatest potential but it's certainly helped me a TON. This is the first time I've felt I've actually need to make a post for something going wrong, sorry if the problem has happened in the past and I missed a post.
Dude i had a similar problem a while back switching from TWRP to CWM. Somehow I corrupted my Dalvik partition. I couldn't even get back to recovery.
So I went here. Followed the instructions and completely went back to stock.
Quick Note that I don't see mentioned enough, YOU WILL LOSE YOUR APPS AND SETTINGS, (hopefully thy're all backed up with Titanium), BUT YOU WILL NOT LOSE YOUR STUFF ON YOUR INTERNAL OR EXTERNAL SD CARDS. The first time I went back to Stock I was scared s***less because I thought I was losing all my pics.
When I booted up the first time, I got the "repairing" Android Icon, it rebooted and I was back in business.
Then I had previously grabbed the TWRP odin flashable 2.5.0.0. tar file from over here. I got 2.5.0.0 because I planned to flash a 4.2.2 ROM after all is said and done. I flashed that with Odin from Download Mode.
I didn't even bother logging into Google on the stock 4.1.2 ( I just can't go back TouchWiz after Cyanogenmod). I just rebooted right into TWRP 2.5.0.0 manually with Volume up and Power button.
From there I factory wiped everything, then superwiped and cachewiped ( both can be found http://forum.xda-developers.com/showthread.php?t=2235141), just to be on the paranoid side.
And finally I flashed Cl3Kener's latest 4.2.2 version of his BlackLiquid and his latest 4.2.2 stable Uber Kernel. I personally think this is the most stable, and as close to perfect ROM thats going to come out for this phone. Of course that is just my opinion after my own experiences with 4.3, 4.3.1, and 4.4.
This is a completely streamlined version of the complete cluster f** I did researching, trial and error, and starting over, while I was in the middle of actually doing it. One last tip I can give, is to get all the files you think you might possibly need and put then on your external SD if you got it, or internal SD. Its a real pain stopping and starting cause your missing a zip you forgot.
Hope this helps
Huge thanks to the Developers threads I Linked to.
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!
Hello! Pretty new in XDA forum and I have a couple of questions and concerns. I was browsing through some threads and I was wondering if I could get some opinion/help from other members.
I have a second phone that I want to mod and I need some help.
Device: Samsung Galaxy S4 (ROOTED)
Model#: SGH-M919
Android Version: 4.4.4
Baseband: M919UVUFNK2
It's an old phone and lately, it's been running really slow and if possible, I'd like to make it run as if it was brand new or at least somewhat close. So the question is, are there any recommended stable roms/mods I could use and if there are/is, will I be able to use it with my rooted phone or do I have to completely factory reset it before I apply the mods/roms?
Thank you!
Hi @Mr.LinK,
Just yesterday I finally got sick of my M919 slow/battery drain/old stuff and decided it was time for a reset. I was running SlimKat from over a year ago and while it was a great ROM, I had accumulated so much crap that it was getting really bogged down. This just happens over time no matter what OS, no fault to Slim. But I was also looking to move to Lollipop. Here's what I did:
1. Backed up using several methodologies (full backup with TWRP just in case, then from Android I backed stuff up with Helium, and used Backup My Mobile for SMS/MMS etc., an EFS backup just in case, etc..)
2. From within Android, did a factory reset. This sent the phone into recovery, and it formatted the data partition.
3. Rebooted to recovery again, and used TWRP to manually format the media section, just in case something was left there. Then wiped everything except the external SD.
4. Used ODIN to flash the OH3 firmware onto my MDL M919, without letting reboot after (unchecked the reboot checkbox). Pulled battery, rebooted back into download mode again, and flashed OH3 a second time... this gets around some instance people have reported about incomplete upgrades of firmware and all sorts of issues... better safe than sorry.
5. Let phone boot into now 100 % stock OH3 Android 4.4.4. YEEEUKKK. Some part of me thought I would just root the thing and get rid of Samsung crapware, but just the sheer annoyance of the T-Mobile boot animation was enough to remind me why I left stock long ago. Anyway, I let it boot, and set it up minimally with just 1 Google account, not restoring from backup. To my surprise it found the ATT network (I'm an ATT user, not T-Mobile... I just prefer T-Mo phones because they have unlocked bootloaders) and APN no problem no effort from me. Usually I have to enter an APN.
6. I tested the phone out to make sure all systems were working. GPS, WIFI, Bluetooth, etc.. To my surprise, first time I ran the camera app, it applied a firmware patch. Sweet. I'm glad I went through this step. Coming from ancient MDL, I figured there might be some kinks like this. I let it sit on stock for a few hours while I did stuff with my kids.
7. Back home, I did a factory reset from within Android. Then I flashed the latest TWRP tar file (2.8.7.0) using ODIN, and in TWRP did a full wipe of everything again.
8. At this point I flashed Danvdh's GPE edition of Lollipop from here.
http://forum.xda-developers.com/showthread.php?t=2539361
Installation went smoothly. It's a very basic set of apps that it comes with (Google play is there, but you have to download email/messaging apps from the store such as Gmail and Messaging, Maps, etc). I like this approach!
I've been gradually setting things back up, and am very happy with things so far. Haven't run into any problems yet. The nice pure GPE android experience is refreshing.
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Mr.LinK said:
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Click to expand...
Click to collapse
Good luck and let us know how it goes!
Frankenscript said:
Good luck and let us know how it goes!
Click to expand...
Click to collapse
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Mr.LinK said:
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Click to expand...
Click to collapse
I'm pretty sure we can change the reported model number by modifying the build.prop file. I just haven't poked around with it yet... I did ask the question in the thread and am waiting for a reply. I haven't had to do this kind of thing for over a year, and I forget the build.prop key that does it. But I had some concern that it might bork something else down the road so I decided to wait a bit. IT's just a cosmetic thing and I'm SOOO enjoying the experience right now.
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Still, these are all minor things to sort out. Really, I think I'm very sold on GPE editions now thanks to Danvdh's work.
Marc
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Mr.LinK said:
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Click to expand...
Click to collapse
Haven't seen random reboots. I think I got maybe one reboot since installing the ROM. Then again, I haven't put NF on the phone. I do know that Netflix app had some issues on my Shield tablet, and the manufacturer (Nvidia) came out with a patch... maybe it's something general in Lollipop?
Frankenscript said:
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Click to expand...
Click to collapse
Both if those can be fixed with Xposed modules.
Sent from my SGH-M919 using XDA Free mobile app
Will look into doing this in a week or so. Thanks
Sent back in time via Android 9.0 TimeText feature.
So I recently found an old Galaxy SII Epic 4G Touch lying around and I thought I would play around with it a little bit.
Little did I know it was gonna be a complete hell
So in all of the confusion of simply not being able to flash whatever the heck I wanted (since the kernel and recovery are apparently both within one monolithic binary), I have now run into a different issue.
So, on this phone so far, I have somehow managed to crash, break, and soft brick my way into successfully installing CyanogenMod 11 (4.4.4 KitKat), CWM 6.0.5.1(I think yeah totally), and the pico loadout for 4.4.4 gapps. I reeeaaally enjoy taking these phones that manufacturers destroy with preloaded launchers, bloat, etc. and fixing them up nice to look like they just rolled off the Google showroom with a fresh installs of all stock gapps, and silky smooth android. But here's where my issue comes in. I spent the good part of today just looking for a full gapps package with all stock gapps that would work on this thing. I sifted through unsafe websites, dead links, and throughout (what i think is) most of this forum to find something that would work, but couldn't. Thought it was issues with not being able to install PA packages onto Cyanogenmod. But that wasn't my issue. (the recovery kicked out error after error each time I tried. So it was an issue for sure. I realize that. Just not the issue I want to solve here and now) So then, I decided to simply run another factory reset, do another fresh install of the OS, and cave in, and use the nano app package. This package was the only one to give me some kind of response. It essentially said that my /system/ partition was too small to accept all of the apps on it. And then it dawned on me. The internal storage on this phone is separated into 2 partitions. 16gb. 1.97gb for system use, and the rest for downloaded apps, media, etc.etc. . I want to know if there is a process - for this phone specifically - to merge those two partitions together so that I can get a stock looking gapps install on this guy. I don't plan on using this phone for anything in particular. Just doing this for fun.
Anyone got any answers? I've seen similar situations floating around here and other places with other devices. And it's doable(????????), but all of the methods shown are for those specific devices, and I would rather not try and replicate them here if somehow something is critically different.
Thanks for any response at all. Seriously. If it's just to tell me I'm a big stupid and this won't and can't work, I will still appreciate it.