I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Morthawt said:
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Click to expand...
Click to collapse
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
LS.xD said:
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
Click to expand...
Click to collapse
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Morthawt said:
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Click to expand...
Click to collapse
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
LS.xD said:
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
Click to expand...
Click to collapse
Oh I will read everything before trying anything serious like this. I felt as if I was smashing my phone into the ground when I rooted it lol, so dangerous :S, even though I was following a guide. But now that I have all the tickboxes ticked and backed up and I have also copied that backup to 2 different hard drives... I should be safe with that.
So for my additional questions.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
Thanks so much for answering my questions, it is really making me feel more confident with the whole process. I don't like going into things blind, I'm a computer techie and like to know what I am doing and why I am doing it. This phone customization business is entirely new to me beyond changing settings and themes lol.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
--> You could flash a wrong zip containing a recovery (Probably you will not do)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
--> Yes
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
--> Every rom has an updater-script that (normally) checks the compatiblity before TWRP installs it
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
--> Stable means NO BUGS, Nightlies are updated nearly every day with the latest commits as they are in development status. May or may not contain bugs. Check out the specific rom thread on xda. Stability of the rom / bugs are discussed there by the users every day. So you can check out which version will work.
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
--> Restore the phone to fully stock firmware. Such official firmware can be found at SamMobile.com
And most important: Press "thanks" at the botom of my posts
(had to remove quotes due to outside links preventing my posting.)
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
Thanks button pressed on them, because truly your information is extremely helpful.
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
LS.xD said:
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
Click to expand...
Click to collapse
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
EDIT: Should I wipe Preload?
Morthawt said:
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
Click to expand...
Click to collapse
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
LS.xD said:
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
Click to expand...
Click to collapse
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Morthawt said:
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Click to expand...
Click to collapse
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
LS.xD said:
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
Click to expand...
Click to collapse
I am on the latest CM11 snapshot Amazing! Although I am confused by some of the options. Is there any documentation on the OS? I see for Network modes things like "2G | 3G", or "2G | 2G + 3G" and "2G | 3G | 2G + 3G" . I pretty much can assume I know that 2G | 3G means 2 or 3G but when it comes to ones with +'s that is just confusing. 2G and 3G at the same time? No idea lol.
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Morthawt said:
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Click to expand...
Click to collapse
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
SlimKAT is a fast, lightweight rom and should be working.
LS.xD said:
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
Click to expand...
Click to collapse
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Morthawt said:
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Click to expand...
Click to collapse
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
LS.xD said:
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
Click to expand...
Click to collapse
Those exist in the TWRP zip format? Where can I find those?
Morthawt said:
Those exist in the TWRP zip format? Where can I find those?
Click to expand...
Click to collapse
I should have read before I answered Seems not to exist for your phone. I don't know the reason.
Hello,
I have 2 Mi4i phones and i have to encrypt them for my work (and my wife's work).
With Miui i can encrypt them, but i don't want to use this.
I want CM13 or Lin14.1
Problem is that on both custom rom's, i can choose to encrypt.
After that it shows the Android robot for a second or 2, then reboot's the phone.
After the restart the phone is not encrypted and every time i try it, i get the same result.
Both rom's are clean installed, no extra's are installed (no kernel etc.)
Is this a bug, or do i have to change something to get it to work?
Anybody any idea what is going wrong?
elot01 said:
Hello,
I have 2 Mi4i phones and i have to encrypt them for my work (and my wife's work).
With Miui i can encrypt them, but i don't want to use this.
I want CM13 or Lin14.1
Problem is that on both custom rom's, i can choose to encrypt.
After that it shows the Android robot for a second or 2, then reboot's the phone.
After the restart the phone is not encrypted and every time i try it, i get the same result.
Both rom's are clean installed, no extra's are installed (no kernel etc.)
Is this a bug, or do i have to change something to get it to work?
Anybody any idea what is going wrong?
Click to expand...
Click to collapse
Yes this is a bug :|
Anyway, aosp custom rom based on miui 6.6.10
Which have encryption bug too .-.
So this feature ( encryption ) won't work for now
Is there any ROM available, where I can encrypt the system using the built-in option for encryption?
I tried a couple of ROMs, but it doesn't work with them. It just restarts and nothing happens.
It has become a must-have feature for me, and I don't really want to go get a firmware from sammobile and flash it, and then be able to encrypt my phone... I will, if I have to, but I'd rather not. Does encryption even work on rooted devices? I just realized I don't know that...
Is there a ROM here, on which this feature works? Doesn't matter what Android version, or whether it's stock or AOSP, either is fine.
Hi !
If you are talking about encryption that you enable in settings and need a password for your phone to boot, you can check the AOSP Extended ROM (Android 8.1).
I'm currently using since a while now and works pretty good (but sometimes the camera don't work you need to reboot the phone) and the option for encryption works ! But be careful, when downloading the ROM (if you download this one) use the v.5.3 and not the v.5.5 since it's very unstable.
That is exactly what I meant. Thank you, I'll check it out!
Hello all! Long time lurker and user of LOS 14.1 on my osprey. COM13 before that. I'm not a tech wizard like most of you, but I'd say I'm fairly good at navigating this stuff. Hope someone out there can help me out with MMS issues.
I'm on 14.1-20190220-Nightly with squid's kernel and my service provider is T-mobile. I can't pinpoint exactly when but at some point in the last month, I stopped receiving MMS messages. I can send them, but when I try to receive, I get the "check your APN settings" message. APN settings have not changed and I have confirmed they are correct. I've wiped the cache partition and that did nothing. I don't know what else to try.
A possible related issue: sometimes SMS doesn't come through either until I turn off WiFi, or reboot. This is a difficult thing to reproduce, it seems intermittent.
Any direction or advice would be greatly appreciated! Thanks!
In the settings find the option to reset the Network settings.This section can get munged.I'm not on the Stock rom on my 2015 X1541(Osprey) I've recently installed Lineage's 16.1,"Pie" .Absolute dream rom.I didn't think anyone would bother making PIE for such and old phone but Lineage have done it proud
R1ffR4ff said:
In the settings find the option to reset the Network settings.This section can get munged.I'm not on the Stock rom on my 2015 X1541(Osprey) I've recently installed Lineage's 16.1,"Pie" .Absolute dream rom.I didn't think anyone would bother making PIE for such and old phone but Lineage have done it proud
Click to expand...
Click to collapse
How long ago did you install 16.1? Any issues at all with it? I might just go that route
I recently did the Network Settings Refresh to try and solve an issue with constant dropped Bluetooth connections. But I will give it another try! Thanks!
I installed PIE a few days ago.Not had one single problem with it.
I got it from here,
http://www.droidthunder.com/android-9-0-pie-on-moto-g3/
and I think it's compatible with your phone if.....
This Android 9.0 Pie based Lineage OS 16 ROM is compatible only with Motorola Moto G3 (Moto G 2015) with model numbers XT1540, XT1541, XT1542, XT1543, XT1544, XT1548 and XT1550. So do not try to flash this unofficial custom ROM on any other phone as it may cause permanent damage or even brick your phone. So its always better to confirm your device before moving ahead.
I made and kept a Nandroid backup of the Stock rom on my Laptop just in case.I now keep a Nandroid backup the PIE install with all my apps installed and the phone setup on my Laptop as well.
So many great features in PIE.I've even been able to swap my Return and Recent apps buttons from Left-to-Right as I'm right handed and hated having the Return button on the left
Tip:
If you do install any Custom rom wait for it's first boot to normal screen(Usually takes quite a while) then reboot to Recovery and do a Factory reset before you set up the phone.I've done this with every Custom rom I've installed on Android phones and it seems to prevent many problems.
I think some people also do a Factory reset before installing Custom roms as well.I can't remember if I did but most likely did .
R1ffR4ff said:
I installed PIE a few days ago.Not had one single problem with it.
I got it from here,
and I think it's compatible with your phone if.....
This Android 9.0 Pie based Lineage OS 16 ROM is compatible only with Motorola Moto G3 (Moto G 2015) with model numbers XT1540, XT1541, XT1542, XT1543, XT1544, XT1548 and XT1550. So do not try to flash this unofficial custom ROM on any other phone as it may cause permanent damage or even brick your phone. So its always better to confirm your device before moving ahead.
I made and kept a Nandroid backup of the Stock rom on my Laptop just in case.I now keep a Nandroid backup the PIE install with all my apps installed and the phone setup on my Laptop as well.
So many great features in PIE.I've even been able to swap my Return and Recent apps buttons from Left-to-Right as I'm right handed and hated having the Return button on the left
Tip:
If you do install any Custom rom wait for it's first boot to normal screen(Usually takes quite a while) then reboot to Recovery and do a Factory reset before you set up the phone.I've done this with every Custom rom I've installed on Android phones and it seems to prevent many problems.
I think some people also do a Factory reset before installing Custom roms as well.I can't remember if I did but most likely did .
Click to expand...
Click to collapse
Interesting. Have you tested MMS and Bluetooth? If those are working, I might just do this.
Thanks for the tips, I keep full nandroid backups too, just in case. I hadn't heard about performing the factory resets during the process but I will do that this time. Is the sequence: factory reset, then boot the ROM, then reboot back into TWRP, then wipe and flash as normal, then boot into new ROM, then reboot into TWRP, factory reset, then finally boot the ROM and setup as normal?
It seems strange that droidthunder instructs you to copy the zip file to internal memory, then wipe the internal memory and then try to flash the zip. Doesn't seem like that would work. Why not just copy the zip to the SD card and flash from there?
Cheers!
I think I just copied mine to the SD card.
I don't use MMS much as WhatsApp etc is way better and normal phone calls/Networks are getting old now but I've just tested MMS and working fine.
I don't use Bluetooth much but it works between my Moto G3 and my DooGee Chinaphone running Android Mokee custom rom.
PIE rocks!!!!!!!
Better battery management.Super slick and as said great features.I don't use the new Gesture system as I've always used,"Holo Launcher" instead of stock launchers and use it's Gesture options but PIE has loads of features but they have been moved around a bit just a bit of a new learning curve but nothing too hard.
R1ffR4ff said:
I think I just copied mine to the SD card.
I don't use MMS much as WhatsApp etc is way better and normal phone calls/Networks are getting old now but I've just tested MMS and working fine.
I don't use Bluetooth much but it works between my Moto G3 and my DooGee Chinaphone running Android Mokee custom rom.
PIE rocks!!!!!!!
Better battery management.Super slick and as said great features.I don't use the new Gesture system as I've always used,"Holo Launcher" instead of stock launchers and use it's Gesture options but PIE has loads of features but they have been moved around a bit just a bit of a new learning curve but nothing too hard.
Click to expand...
Click to collapse
Cool! Thanks for the feedback! I'll assume I have the factory reset sequence correct. I dig Holo Launcher too. Been using it for many years now
emanresutseb said:
Cool! Thanks for the feedback! I'll assume I have the factory reset sequence correct. I dig Holo Launcher too. Been using it for many years now
Click to expand...
Click to collapse
One word of warning.If you do a Factory reset after installing the Custom Rom it unroots the phone but I wanted that as one of my Banking apps won't run on a Rooted phone.I could just leave it rooted and use the Banking web page but the apps are more convenient
R1ffR4ff said:
One word of warning.If you do a Factory reset after installing the Custom Rom it unroots the phone but I wanted that as one of my Banking apps won't run on a Rooted phone.I could just leave it rooted and use the Banking web page but the apps are more convenient
Click to expand...
Click to collapse
Ah yes, good point. I do like some rooted apps like Titanium and Greenify. :good:
emanresutseb said:
Ah yes, good point. I do like some rooted apps like Titanium and Greenify. :good:
Click to expand...
Click to collapse
You don't need Titanium as TWRP Nandroid backup saves everything on the internal memory and everything else I want to keep is on the cloud or copied via USB to my PC/Latop.
As for Greenify those kind of apps are useless.You don't need battery savers in Android and even less since Marshamallow.PIE has awesome Battery management and even learns your usage.
FYI. I tried so many different things and nothing worked. Factory reset, no. Clean wipe and reflashed 14.1, no. Called service provider and they refreshed my connection, no. Then I installed squid2's 15.1 beta and it is working very well. Solved a lot of different annoying issues I was having. Hope it keeps working!!
emanresutseb said:
FYI. I tried so many different things and nothing worked. Factory reset, no. Clean wipe and reflashed 14.1, no. Called service provider and they refreshed my connection, no. Then I installed squid2's 15.1 beta and it is working very well. Solved a lot of different annoying issues I was having. Hope it keeps working!!
Click to expand...
Click to collapse
Glad you found something that works
So far, so good. Loving this ROM. It is as close to perfectly functional as any I have ever tried.
emanresutseb said:
So far, so good. Loving this ROM. It is as close to perfectly functional as any I have ever tried.
Click to expand...
Click to collapse
I feel the same about the PIE rom on my G3.It makes the old phone feel like a Brand new one :laugh: