I seem to have a bit of an issue, recently i installed Pure Nexus on my Galaxy S4 Active.
The other day I rebooted my phone and it seemed to have gotten stuck in a bootloop. To fix this I wiped cache and dalvik but not factory reset. The phone booted up however all of my internal files were gone, but my apps remained. I also lost access to the hardware keys and camera. I have two theories
1.The phone somehow deleted all of my files for no reason
2. Safestrap booted my phone into a rom slot and refuses to boot to stock
I checked safestrap and it said that it was on stock, however I had installed pure nexus on one of the rom slots but never deleted it
The reason i believe my second theory to be true is because I am now missing a lot of total system memory which i should normally have.
any and all help is appreciated in finding out how to recover my files
Usually with a new ROM, it will format /Data and your internal SD. Try to format /Data with your recovery. *MAKE A BACKUP* and as far as the camera and keys go, re flash the ROM, and Google for the camera master patch for your phone model. Regarding the i537, we are stuck on a locked bootloader. Meaning, no custom kernels or recoveries. No custom kernels means only touchwiz based roms. I don't know how in the actual h*ll you got an aosp ROM on there. But a majority of your problems are due to the kernel.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
bjeastin said:
Regarding the i537, we are stuck on a locked bootloader. Meaning, no custom kernels or recoveries. No custom kernels means only touchwiz based roms. I don't know how in the actual h*ll you got an aosp ROM on there. But a majority of your problems are due to the kernel.
Click to expand...
Click to collapse
Back on KitKat, there was a ROM called pure nexus (original s4 thread link and our i537 version link) that worked for our phone. It was based off the Google Play Edition S4 ROM, so even though it was technically touchwiz, it looked, felt, and acted like an AOSP ROM (i.e. it was way more than just an AOSP theme or skin). Unfortunately the dev moved on to the Nexus scene by the time we finally got 5.0.1 for the i537. But long story short, this ROM can, should, and does work for the i537, at least on KitKat.
I tried for a few months to port the 5.0.1 edition to our i537 with no luck, it seems I don't know enough about ROM development
thisisapoorusernamechoice said:
Back on KitKat, there was a ROM called pure nexus (original s4 thread link and our i537 version link) that worked for our phone. It was based off the Google Play Edition S4 ROM, so even though it was technically touchwiz, it looked, felt, and acted like an AOSP ROM. Unfortunately the dev moved on to the Nexus scene by the time we finally got 5.0.1 for the i537. But long story short, this ROM can, should, and does work for the i537, at least on KitKat.
I tried for a few months to port the 5.0.1 edition to our i537 with no luck, it seems I don't know enough about ROM development
Click to expand...
Click to collapse
That explains a lot. I actually heard of someone porting the "pure" s4 to our phone, and then it seemed to fall off the face of the earth. That actually explains a lot.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
thisisapoorusernamechoice said:
Back on KitKat, there was a ROM called pure nexus (original s4 thread link and our i537 version link) that worked for our phone. It was based off the Google Play Edition S4 ROM, so even though it was technically touchwiz, it looked, felt, and acted like an AOSP ROM. Unfortunately the dev moved on to the Nexus scene by the time we finally got 5.0.1 for the i537. But long story short, this ROM can, should, and does work for the i537, at least on KitKat.
I tried for a few months to port the 5.0.1 edition to our i537 with no luck, it seems I don't know enough about ROM development
Click to expand...
Click to collapse
That explains a lot. I actually heard of someone porting the "pure" s4 to our phone, and then it seemed to fall off the face of the earth.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Related
Has anybody been able to find any ROMs for the S4 Active? Preferably, the i537, but I'm willing to try anything for the GT-I9295. I know it's early, as the Safestrap method is fairly new, and the kernel can't be touched right now, so a 4.3 ROM is out of the question. I'm using the ROM listed here:
http://forum.xda-developers.com/showthread.php?t=2406177
I'm loving stock, but I have Cyanogenmod on my Nexus and love the customization. Does anybody know of anything close to that available for the Active?
Yea I believe its ported from the International version...they call it google edition I think! If I helped ya..it dosent hurt to hit the thanks button! :good:
Actually there is a pre-release 4.3 ROM available, it's the MI2 build for the I537 and yes it's a leak from AT&T (thanks to designgears and you can find it here). Two issues with that one if you choose to use it:
1) You may not be able to update to the official OTA 4.3 expected sometime later this month (according to rumors, that is)
2) There's no working root so if you must have that, don't bother with this build just yet
There is a third issue that appears to be the most common problem with the MI2 build and that's the screenshot feature which isn't working, it's covered in the thread for the MI2 build.
Because it's a pre-release similar to the MF1 pre-release leak, it appears to not allow an OTA but since there hasn't been any 4.3 OTA updates from AT&T as of yet nobody really knows what's going to happen.
Also, if you flash that MI2 build, your only alternative will be to fall all the way back to the MF1 build since no ODIN One-click exists for the MF2 or MF3 builds, but you can switch between the MF1 and MI2 builds (confirmed by others and I've done it several times in the past week myself).
Aside from that "official" ROM leak, the only other current working option is using Safestrap on MF1/MF2/MF3 (with the appropriate kernel modules) along with the AOSP ROM provided by LeJay which you can find here.
That's pretty much it. I have the I537 as noted so I don't muck with the I9295 ROMs but I think there's at least the one CM10.2 build for it, and no, it doesn't work on the I537 even with Safestrap.
EDIT: DOH, forgot about the ROM from d8389 he just released yesterday, also made from the MI2 build and you can find that one here - that's for the I9295, btw.
br0adband said:
Actually there is a pre-release 4.3 ROM available, it's the MI2 build for the I537 and yes it's a leak from AT&T (thanks to designgears and you can find it here). Two issues with that one if you choose to use it:
1) You may not be able to update to the official OTA 4.3 expected sometime later this month (according to rumors, that is)
2) There's no working root so if you must have that, don't bother with this build just yet
There is a third issue that appears to be the most common problem with the MI2 build and that's the screenshot feature which isn't working, it's covered in the thread for the MI2 build.
Because it's a pre-release similar to the MF1 pre-release leak, it appears to not allow an OTA but since there hasn't been any 4.3 OTA updates from AT&T as of yet nobody really knows what's going to happen.
Also, if you flash that MI2 build, your only alternative will be to fall all the way back to the MF1 build since no ODIN One-click exists for the MF2 or MF3 builds, but you can switch between the MF1 and MI2 builds (confirmed by others and I've done it several times in the past week myself).
Aside from that "official" ROM leak, the only other current working option is using Safestrap on MF1/MF2/MF3 (with the appropriate kernel modules) along with the AOSP ROM provided by LeJay which you can find here.
That's pretty much it. I have the I537 as noted so I don't muck with the I9295 ROMs but I think there's at least the one CM10.2 build for it, and no, it doesn't work on the I537 even with Safestrap.
EDIT: DOH, forgot about the ROM from d8389 he just released yesterday, also made from the MI2 build and you can find that one here - that's for the I9295, btw.
Click to expand...
Click to collapse
I'll keep playing the waiting game then... Maybe I can submit a request for Cyanogenmod to be made for this device.
Until the bootloader is unlocked, it's most likely not going to happen at all. It's possible that someone with enough talent can put together a CM10.1 ROM which uses the current kernels (I think, I'm not 100% sure on that), but the MI2 4.3 build now is pretty locked down as it is (no known root at the moment and it looks like Safestrap may be a no-go as well for that or future builds).
The honest truth is the GS4A is simply not popular enough to get any reaction from the CM crowd at all, unfortunately, and it's entirely possible it may not even be available for much longer given that unpopularity. It's not selling well, and the few of us that do have them are just that: few and far between.
It's sad because it's a great device; it IS an S4 with a lower resolution camera and the water-resistant aspect as well as the LCD panel (not AMOLED like the S4) which is just fine by me, I can see it better in daylight than an AMOLED anyway. But the locked bootloader basically ensures the level of interest is negligible at best, not much can be done about it unless a miracle comes along at this point.
I'm very happy with mine for many reasons, not just 'cause I got it so cheap.
br0adband said:
Until the bootloader is unlocked, it's most likely not going to happen at all. It's possible that someone with enough talent can put together a CM10.1 ROM which uses the current kernels (I think, I'm not 100% sure on that), but the MI2 4.3 build now is pretty locked down as it is (no known root at the moment and it looks like Safestrap may be a no-go as well for that or future builds).
The honest truth is the GS4A is simply not popular enough to get any reaction from the CM crowd at all, unfortunately, and it's entirely possible it may not even be available for much longer given that unpopularity. It's not selling well, and the few of us that do have them are just that: few and far between.
It's sad because it's a great device; it IS an S4 with a lower resolution camera and the water-resistant aspect as well as the LCD panel (not AMOLED like the S4) which is just fine by me, I can see it better in daylight than an AMOLED anyway. But the locked bootloader basically ensures the level of interest is negligible at best, not much can be done about it unless a miracle comes along at this point.
I'm very happy with mine for many reasons, not just 'cause I got it so cheap.
Click to expand...
Click to collapse
I think our best hope is for @Hashcode to get kexec working with SafeStrap. Then we will be able to use ROMs with any kernel. Until then we're stuck with GPE 4.2.2.
Hashcode made a post or two at his blog/site stating that things are becoming incredibly tough to make such workarounds viable anymore, even to the point where it's not even worth the time and trouble to make the effort at all in some situations. I think with the GS4A, more specifically the AT&T I537 model, we could just have a device that simply isn't going to get itself cracked wide open without some small miracle happening.
Come on, someone working at Samsung... have some pity on us and drop us something to help out, will ya?
I've started a request forum here:
http://forum.cyanogenmod.com/topic/80004-cyanogenmod-for-the-s4-active/
If anyone would like to back me up, it'd be much appreciated.
Decided it wasn't worth the BS of heading back to Best Buy so I'll stick with MF1 for now. I did make a reply at the CM forum about the potential of someone building CM10.1 as a flashable zip for us and provided the link to the kernel source for the I537, maybe someone with some spare time might be able to create something.
I really wish I'd spent more time learning how to do that; if I had the necessary skill set I'd build it myself I suppose but I've never been into that side of the device firmware/ROM stuff.
But who knows...
I'm running Shostock v2.3 on my I537 with one of my rom slots in safestrap. i'm on MF2. of the S4 ROMs, i've only tried Shostock and Goldeneye, but i'm sure other S4 ROMs will work too. when you install one, you also have to install the modules pack and camera fix from the ported google edition thread. the only other problem is the menu and back buttons don't work out of the box with an S4 ROM because our buttons aren't capacitive. thankfully, Darkman was kind enough to show me how to fix those so they work like normal.
hokeymcf said:
I'm running Shostock v2.3 on my I537 with one of my rom slots in safestrap. i'm on MF2. of the S4 ROMs, i've only tried Shostock and Goldeneye, but i'm sure other S4 ROMs will work too. when you install one, you also have to install the modules pack and camera fix from the ported google edition thread. the only other problem is the menu and back buttons don't work out of the box with an S4 ROM because our buttons aren't capacitive. thankfully, Darkman was kind enough to show me how to fix those so they work like normal.
Click to expand...
Click to collapse
Can you share how to edit ROMs to add the physical back and menu buttons? Thanks
GT-i9295(i537) running SafeStrap
yankeesfan714 said:
Can you share how to edit ROMs to add the physical back and menu buttons? Thanks
GT-i9295(i537) running SafeStrap
Click to expand...
Click to collapse
well, i don't edit the ROM before flashing it. after flashing the ROM, any updates for it, the modules pack, and the camera patch, i go into /system/usr/keylayout using a file explorer, and add:
key 139 MENU
key 158 BACK
to gpio-keys.kl with a text editor. after that, reboot and they work like they should.
hokeymcf said:
well, i don't edit the ROM before flashing it. after flashing the ROM, any updates for it, the modules pack, and the camera patch, i go into /system/usr/keylayout using a file explorer, and add:
key 139 MENU
key 158 BACK
to gpio-keys.kl with a text editor. after that, reboot and they work like they should.
Click to expand...
Click to collapse
Is it possible to add this to either the modules zip or the camera fix to make it easier for users? Ideally this would be added to the camera fix since I think @Hashcode is going to automate the modules in SafeStrap eventually.
On another note, I had no idea we could flash regular GS4 ROMs, this opens up a world of possibilities. I assume we can only flash 4.2.2 ROMs though?
Devo7v said:
Is it possible to add this to either the modules zip or the camera fix to make it easier for users? Ideally this would be added to the camera fix since I think @Hashcode is going to automate the modules in SafeStrap eventually.
On another note, I had no idea we could flash regular GS4 ROMs, this opens up a world of possibilities. I assume we can only flash 4.2.2 ROMs though?
Click to expand...
Click to collapse
i have no idea. i could try, but it's probably a job better suited to someone who really knows what they're doing, since i'm only as good as the tutorials i find on the internet.
once again, i dunno. i'm on MF2, but shostock is MF3. so since that's different but still works, it might be possible to flash a 4.3 ROM, but the fact that i read that there's no going back once you do flash it, i haven't tried it.
i agree that it's awesome we can actually use regular s4 ROMs.
yankeesfan714 said:
Can you share how to edit ROMs to add the physical back and menu buttons? Thanks
GT-i9295(i537) running SafeStrap
Click to expand...
Click to collapse
So in theory any stock based s4 4.2.2 ROM will run with this buildprop modification?
GT-i9295(i537) running SafeStrap
It's not a build.prop edit, but yeah, I think any S4 4.2.2 ROM would work.
S-Beam
Set them next to each other and use S-Beam, it's what it was designed for. Or even Bluetooth would work.
Just so everybody is aware @my-blue-snog-box has created a flashable zip file that will edit the keyboard file and get the hard keys working. It can be found here. If you try any S4 ROMs please post the functionality of them so we can create an index of ROMs working with SafeStrap.
I've posted over there that I got Hyperdrive ROM working, you just need to be careful during setup.
CM Unofficial 2013 10 10 fkosa's reply
I am running CM 20131010 Unoffical - jactiveltxxx from, ofcourse it is 4.3 and it is running smothly.
Havn't found any anoying errors yet.
http://forum.xda-developers.com/showthread.php?t=2395242&page=11
I tried to make some roms for myself and found out the following:
from: CM 20131017 Nightly - jltxxx - was a bit slow, and it felt like the touch was a bit delayed verry anoying
from: CM 20131021 Nightly - jltxxx - here there was something wrong with the screen.
But then again the nightly builds tends to a bit unstable from time to time.
Any Galaxy S4 Rom
I just recently got the galaxy note 2 and loving everything about it inside and out. But I was just wondering if there are or will be any rom or ports of a galaxy s4 rom to our galaxy note 2? Ive look in the android forums but did not see anything besides the hawkish rom which I am now currently using...
Hello Active-Users,
i think this might have been discussed earlier but i didnt find any specific thread about it.
In general i am really happy with my s4 active (international version). but the custom rom support is actually really poor. There are Ports for AOSP 4.2.2 and CM10.2, but i wonder, if and when we will get any "official" AOSP or CM-Support? Most of the Hardware is known because auf the s4 (9505) and it has official support because auf the "google edition". Differences are 1) Camera 2) Screen and two sensors, that are not there in the active. so for me (i am no developer at all!) it should be possible, to patch official s4 roms for our s4 active. but who has knowledge about these thinks? could we ask for support of some good developers, maybe do some donations or something like that...
its so sad to see the s4 community having tons of roms to try and we didnt have any official support.
so, what must happen for an official aosp/cm-support?
Thank you for answers,
greetings, moviecut
As far as I know, that's 2 stated differences between I9505 and I9295: 2 physical buttons and camera, not sure about other internal parts. Waiting for months for a good developer to have some minor tricks so that all I9505 is portable to I9295.
gtchuah said:
As far as I know, that's 2 stated differences between I9505 and I9295: 2 physical buttons and camera, not sure about other internal parts. Waiting for months for a good developer to have some minor tricks so that all I9505 is portable to I9295.
Click to expand...
Click to collapse
Since nobody has responded to this, I guess I will. To answer your question, yes you can more or less easily flash regular S4 ROMs onto our phones. Be aware that this has only been done in SafeStrap thus far. You could possibly make your phone unusable if you flash S4 ROMs as your only ROM without using SafeStrap.
To use a regular S4 ROM in SafeStrap:
Flash your desired regular S4 ROM into a new slot in SafeStrap. Currently you can only fash 4.2.2 TouchWiz based ROMs due to a kernel limitation with SafeStrap. I believe @Hashcode is still working on this and hopefully we will eventually be able to use any kernels with SafeStrap.
Without rebooting, flash the MOD file of your stock ROM. So if your stock ROM is MF1, then flash the MF1 MOD file. MF2....flash MF2 MOD file, and MF3...flash MF3 MOD file. The MOD files can be found here.
Again without rebooting, flash the camera fix that was put together by LeJay. The camera fix can be found here.
Make your new ROM slot the active ROM slot and reboot your phone.
Once in the new ROM you need the key layout file in order to use the hard menu and back keys that the Active has. Go into /system/usr/keylayout using a file explorer, and add:
key 139 MENU
key 158 BACK
to gpio-keys.kl with a text editor. after that, reboot and they work like they should. (thanks to @hokeymcf for posting these instructions)
If any of this information is wrong please let me know and I will update this post so people don't brick phones. Please note that this has only been reported to work in SafeStrap so far, flashing regular S4 ROMs as your stock ROM could brick your device and has not been tested yet.
Devo7v said:
Since nobody has responded to this, I guess I will. To answer your question, yes you can more or less easily flash regular S4 ROMs onto our phones. Be aware that this has only been done in SafeStrap thus far. You could possibly make your phone unusable if you flash S4 ROMs as your only ROM without using SafeStrap.
Click to expand...
Click to collapse
Safestrap is only for the i537 - the AT&T S4 Active - this thread is about the i9295 which doesn't according to the safestrap post have that option. Flashing the roms directly won't work simply because without safestrap we run into the kernel issue of not having the right display drivers, and so the phone just won't work.
Im desperately in search of a way I can flash a GPE Rom onto the ATT (i537) variant s4active. I HATE the whole touchwiz UI. and I have tried removing it manually, by replacing stock TW apps with google apps and uninstalling TW apps. But I want the whole enchilada. The SystemUI and interface of the Google Play edition s4 active. I know they have roms for the international version. but is there anyone out there that knows how I can get a stock google android rom onto my device.
im running 4.4.2 NC9 rooted and with safestrap.
I know theres like a kernel difference in aosp roms so idk how it all works. I would just love to take off touchwiz completely. any help would be greatly appreciated.
sorry if I offend anyone on here. since it seems like everyones so touchy about things posted here... so if I put this question in the wrong place or something, sorry.
jeredrh said:
Im desperately in search of a way I can flash a GPE Rom onto the ATT (i537) variant s4active. I HATE the whole touchwiz UI. and I have tried removing it manually, by replacing stock TW apps with google apps and uninstalling TW apps. But I want the whole enchilada. The SystemUI and interface of the Google Play edition s4 active. I know they have roms for the international version. but is there anyone out there that knows how I can get a stock google android rom onto my device.
im running 4.4.2 NC9 rooted and with safestrap.
I know theres like a kernel difference in aosp roms so idk how it all works. I would just love to take off touchwiz completely. any help would be greatly appreciated.
sorry if I offend anyone on here. since it seems like everyones so touchy about things posted here... so if I put this question in the wrong place or something, sorry.
Click to expand...
Click to collapse
The short answer to your question is that you can't, you're stuck with TouchWiz until the bootloader is unlocked. The reason for this is that the bootloader checks files you try to flash to the phone to make sure they are signed by Samsung. In order to use something other than a TouchWiz rom on the i537, you need to flash a different kernel. And since other kernels aren't signed by Samsung it will fail to flash.
The GPE for 4.2.2 that you are referring to was able to use the existing Samsung stock kernel, so it seemed that you were using an AOSP ROM, but it was still using Samsung's kernel. The newer GPE roms (4.3 and 4.4.2) can no longer utilize the stock Samsung kernel so they are non-functional. Unfortunately since you're on 4.4.2 you have the new bootloader and there is no way to downgrade back to 4.2.2 and use the GPE rom. Your only option at this point is to use the stock rom or find a compatible rom that you can live with until somebody figures out how to unlock the bootloader (hopefully in August).
Go Dan Rosenberg
Alright, so I've enjoyed modding my Android devices since I got my first Android running on 2.2, especially because of the options to tweak CPU usage, and just (from what I have noticed) better general usage with all of my devices. I purchased this phone because of it's similar power usage to the S4 and it being water & dust resistant. However, most of the development that I have seen for this forum has been for the i9525, which is the international version. I have the i537, and have been going crazy with battery drainage issues, and I think only a custom kernel/new ROM can fix this. Could somebody point me in the right direction of where to go? I've heard talk that after MF2, installing Safestrap right now is essentially not possible, due to bootloader issues.
I'm running the Stock ROM v 4.2.2
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
QuentinX5 said:
Alright, so I've enjoyed modding my Android devices since I got my first Android running on 2.2, especially because of the options to tweak CPU usage, and just (from what I have noticed) better general usage with all of my devices. I purchased this phone because of it's similar power usage to the S4 and it being water & dust resistant. However, most of the development that I have seen for this forum has been for the i9525, which is the international version. I have the i537, and have been going crazy with battery drainage issues, and I think only a custom kernel/new ROM can fix this. Could somebody point me in the right direction of where to go? I've heard talk that after MF2, installing Safestrap right now is essentially not possible, due to bootloader issues.
I'm running the Stock ROM v 4.2.2
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Click to expand...
Click to collapse
SafeStrap works for every version of firmware for the i537, you just need to use the proper version. If you're on ML2 I think you need 3.71, but please check to make sure because I could be wrong. As for a custom kernel or tweaking the CPU, it's not going to be possible on the i537 because the bootloader is locked and you are forced to use the stock kernel. You can try a custom ROM through SafeStrap, but I don't think it's going to help much. You might be better off upgrading the NE3 or NH3 and trying a custom ROM through SafeStrap there.
Devo7v said:
SafeStrap works for every version of firmware for the i537, you just need to use the proper version. If you're on ML2 I think you need 3.71, but please check to make sure because I could be wrong. As for a custom kernel or tweaking the CPU, it's not going to be possible on the i537 because the bootloader is locked and you are forced to use the stock kernel. You can try a custom ROM through SafeStrap, but I don't think it's going to help much. You might be better off upgrading the NE3 or NH3 and trying a custom ROM through SafeStrap there.
Click to expand...
Click to collapse
So essentially until we get the bootloader unlocked and can install a custom recovery (Like CWM or TWRP, instead of using SafeStrap), no "real" custom ROMs? More just ROMs based off of the stock kernel/modem/etc.?
QuentinX5 said:
So essentially until we get the bootloader unlocked and can install a custom recovery (Like CWM or TWRP, instead of using SafeStrap), no "real" custom ROMs? More just ROMs based off of the stock kernel/modem/etc.?
Click to expand...
Click to collapse
Correct, and most of the people who were leading the development and research of unlocking the bootloader have decided to move on to other things within the last week. At this point it looks like the bootloader will never be unlocked. There's always a slim chance but it's not looking good.
Is there a bare bones ROM available for 4.4.4? I recall some being available for previous devices and those seem to have to have the best performance and most popular. Basically just the stock ROM debloated and flashable via TWRP. And if so, would this have working touchless control/active display?
thanks!
The reason it probably isn't there is that most people just root and delete the 10-20 apks manually. Takes pretty much the same amount of time for the same end result.
Sent from my Moto X
Here you go. http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-2-v1-3b1-6-9-2014-t2716657 You can always remove more.
I'm using Epsilon Project ROM on my XT1060 Verizon Dev edition running AT&T Sim card. It's very minimalist, has working active display and touchless control, and reduces battery consumption considerably compared to stock (DU Battery Saver estimated battery time jumped from 18 hours to 28 hours from full).
Here's the link to the ROM http://forum.xda-developers.com/moto-x/development/rom-epsilon-project-v1-0-09-03-clean-t2866450
thanks for the feedback y'all, looks like I've got some reading/research to do.
IMNUTS - agreed, but from my experience, I think it's best to start with a clean slate rather than trying to debloat various apps - as those could have left other files on the system that could hinder performance.
Make sure to look into Krypton(blur/stock based), Eclipse(same):good:. Honestly I've only ran Krypton but I went back to stock rooted... + xposed etc... had some lag here and there in Krypton, stock is noticiably snappier for me:/ *shrugs
bothgoodandbad said:
Make sure to look into Krypton(blur/stock based), Eclipse(same):good:. Honestly I've only ran Krypton but I went back to stock rooted... + xposed etc... had some lag here and there in Krypton, stock is noticiably snappier for me:/ *shrugs
Click to expand...
Click to collapse
Went with krypton. Will report later this week.
Sent from my XT1060 using XDA Free mobile app
Do you guys (or anyone) know if I would be able to downgrade to a stock 4.4.2 after upgrading to 4.4.4 on Krypton (or any custom ROM, for that matter)? I know there's been a lot of talk about how you shouldn't downgrade... I've always been a little unclear as to whether that applies to stock ROMs only or both stock and custom.
Also, what happens if the install doesn't work? Can I flash a downgraded ROM? I tried installing the latest CM11 for my phone, but it failed, and I reinstalled a stock 4.2.2, and just reading through the forums... I feel like that was a big freakin' no-no.
Travisdroidx2 said:
Here you go. http://forum.xda-developers.com/moto-x/development/rom-krypton-v1-2-v1-3b1-6-9-2014-t2716657 You can always remove more.
Click to expand...
Click to collapse
TheBoiledDogs said:
I'm using Epsilon Project ROM on my XT1060 Verizon Dev edition running AT&T Sim card. It's very minimalist, has working active display and touchless control, and reduces battery consumption considerably compared to stock (DU Battery Saver estimated battery time jumped from 18 hours to 28 hours from full).
Here's the link to the ROM http://forum.xda-developers.com/moto-x/development/rom-epsilon-project-v1-0-09-03-clean-t2866450
Click to expand...
Click to collapse
cxwong1 said:
Do you guys (or anyone) know if I would be able to downgrade to a stock 4.4.2 after upgrading to 4.4.4 on Krypton (or any custom ROM, for that matter)? I know there's been a lot of talk about how you shouldn't downgrade... I've always been a little unclear as to whether that applies to stock ROMs only or both stock and custom.
Also, what happens if the install doesn't work? Can I flash a downgraded ROM? I tried installing the latest CM11 for my phone, but it failed, and I reinstalled a stock 4.2.2, and just reading through the forums... I feel like that was a big freakin' no-no.
Click to expand...
Click to collapse
Roms don't flash bootloader and other certain things, so... The rule is really, don't downgrade official firmware, ever. Once you flash 4.4.2 or higher, you cannot downgrade. Roms are not included, as they don't touch the bootloader. So yes, if you were on official 4.4.2 firmware, flashed a 4.4.4 custom rom, and want to flash 4.4.2 official firmware again.... That's fine.
But if you flash 4.4.4 firmware with fastboot or RSDLite, that's it.... No going back to 4.4.2.
Now, my disclaimer.... You SHOULD be OK. There's no guarantees in life, especially on phone flashing.... Anything can go horribly wrong anytime and doing anything. So do all this at your own peril. ?
Thanks!
Darth said:
Roms don't flash bootloader and other certain things, so... The rule is really, don't downgrade official firmware, ever. Once you flash 4.4.2 or higher, you cannot downgrade. Roms are not included, as they don't touch the bootloader. So yes, if you were on official 4.4.2 firmware, flashed a 4.4.4 custom rom, and want to flash 4.4.2 official firmware again.... That's fine. But if you flash 4.4.4 firmware with fastboot or RSDLite, that's it.... No going back to 4.4.2. Now, my disclaimer.... You SHOULD be OK. There's no guarantees in life, especially on phone flashing.... Anything can go horribly wrong anytime and doing anything. So do all this at your own peril. ?
Click to expand...
Click to collapse