i'll try to be brief:
-if i root my phone (s3 mini), will samsung updates cause problems? would you suggest that i also flash the ROM (to smth custom like cyanogenMod)
-does the utility to root the phone provide a full backup of the stock firmware and data? so, if smth goes wrong i can revert back to stock (with my apps and settings. at worst, default factory settings).
-if i flash the ROM, will i lose anything? -say- will i lose proprietary stuff like touchwiz?
-do custom ROMs use the latest android version (that's one of the reasons that i wanna root & flash: to be up to date to latest android version)?
-can custom ROMs update to newer android versions automatically? or do i have to flash again and again everytime there is a new android update?
When I rooted my Galaxy S3 the status of the phone (visible in the preferences/device info) changed to "modified" and I stopped getting updates from Samsung (when checking for updates it said that I had a modified system so I wouldn't be able to get any updates). If you flash a ROM you will indeed loose everything, including Touchwiz, but if you backup your personal data then loosing Touchwiz could be a good thing, at least it was for me. I prefer Cyanogenmod.
Flashing ROMs is frequently done because you actually want to loose all that proprietary bloatware. Custom ROMs also can give you access to the latest Android version right away, wich is a lot faster than waiting months to get last year's version through Samsung. This is one of the main reasons why I decided to flash my phone. I don't use all the "features" that Samsung implements and with Cyanogenmod 10.1 my phone feels faster and has longer battery life.
As for updating, each ROM has different ways of handling it. Cyanogenmod has OTA updates which you can access through your phone "Settings/About phone" section and it will automatically flash them for you.
wtx1033 said:
i'll try to be brief:
-if i root my phone (s3 mini), will samsung updates cause problems? would you suggest that i also flash the ROM (to smth custom like cyanogenMod)
-does the utility to root the phone provide a full backup of the stock firmware and data? so, if smth goes wrong i can revert back to stock (with my apps and settings. at worst, default factory settings).
-if i flash the ROM, will i lose anything? -say- will i lose proprietary stuff like touchwiz?
-do custom ROMs use the latest android version (that's one of the reasons that i wanna root: to be up to date to latest android version)?
-can custom ROMs update to newer android versions automatically? or do i have to flash again and again everytime there is a new android update?
Click to expand...
Click to collapse
hcengar said:
When I rooted my Galaxy S3 the status of the phone (visible in the preferences/device info) changed to "modified" and I stopped getting updates from Samsung (when checking for updates it said that I had a modified system so I wouldn't be able to get any updates). If you flash a ROM you will indeed loose everything, including Touchwiz, but if you backup your personal data then loosing Touchwiz could be a good thing, at least it was for me. I prefer Cyanogenmod.
Flashing ROMs is frequently done because you actually want to loose all that proprietary bloatware. Custom ROMs also can give you access to the latest Android version right away, wich is a lot faster than waiting months to get last year's version through Samsung. This is one of the main reasons why I decided to flash my phone. I don't use all the "features" that Samsung implements and with Cyanogenmod 10.1 my phone feels faster and has longer battery life.
As for updating, each ROM has different ways of handling it. Cyanogenmod has OTA updates which you can access through your phone "Settings/About phone" section and it will automatically flash them for you.
Click to expand...
Click to collapse
thank you
the replies were as i hoped i am gonna root and flash soon.
but i am still looking for a reply to this one:
does the utility to root the phone also provides a full backup of the stock firmware and data? so, if smth goes wrong i can revert back to stock (with my apps and settings. at worst, default factory settings).
wtx1033 said:
thank you
the replies were as i hoped i am gonna root and flash soon.
but i am still looking for a reply to this one:
does the utility to root the phone also provides a full backup of the stock firmware and data? so, if smth goes wrong i can revert back to stock (with my apps and settings. at worst, default factory settings).
Click to expand...
Click to collapse
Yes. You can use clockwork mod (cwm) to backup everything. Its recommended to take your backup using cwm before flashing a custom Rom. So that whenever you want your stock back or something with your new rom goes wrong you can revert back. You can use cwm to restore or use Odin which will make your device like when you bought it. You can restore the data alone using advance restore and your device will be like before flashing custom rom.
haridevil99 said:
Yes. You can use clockwork mod (cwm) to backup everything. Its recommended to take your backup using cwm before flashing a custom Rom. So that whenever you want your stock back or something with your new rom goes wrong you can revert back. You can use cwm to restore or use Odin which will make your device like when you bought it. You can restore the data alone using advance restore and your device will be like before flashing custom rom.
Click to expand...
Click to collapse
i guess, if smth goes bad during rooting i cannot revert back. since for backup one needs to root the device beforehand. is this right?
wtx1033 said:
i guess, if smth goes bad during rooting i cannot revert back. since for backup one needs to root the device beforehand. is this right?
Click to expand...
Click to collapse
I dont think cwm needs root access to take a backup. And you can rely on odin always if you got stock rom. So something goes wrong, Odin to the rescue.. So try taking backup with cwm first then root. Anyway if the root update was made for your device then its very very rare for things to go wrong.
Hi everyone. I'm new to XDA, so I'd like to take the time in advance to tell all of you developers and contributors how much I appreciate what you do. XDA has some of the brightest minds in the world. The information contained here has already saved me (and my Nexus 7) quite a few times.
With that said, I'd like to know more about the ins and outs of flashing ROMs (and kernels) and how to do it properly without losing everything (music, pics, etc). Also, how flash updates to ROMs: do I need to wipe and reload everything with each update, and and can I flash the LATEST update or do I have to go back and flash each and every update in order of their release? If anyone could direct me to the proper thread(s) I'd greatly appreciate it. There's so much info here that its easy to get lost. I truly appreciate any help and/or direction.
phys_of_ex said:
Hi everyone. I'm new to XDA, so I'd like to take the time in advance to tell all of you developers and contributors how much I appreciate what you do. XDA has some of the brightest minds in the world. The information contained here has already saved me (and my Nexus 7) quite a few times.
With that said, I'd like to know more about the ins and outs of flashing ROMs (and kernels) and how to do it properly without losing everything (music, pics, etc). Also, how flash updates to ROMs: do I need to wipe and reload everything with each update, and and can I flash the LATEST update or do I have to go back and flash each and every update in order of their release? If anyone could direct me to the proper thread(s) I'd greatly appreciate it. There's so much info here that its easy to get lost. I truly appreciate any help and/or direction.
Click to expand...
Click to collapse
Hi, I'm glad you're happy with XDA.
I'm not a developer but I can tell you about flashing ROMs.
When flashing the latest version of a ROM/kernel you don't have to flash all previous versions
When flashing a new ROM (E.g CyanogenMod) over your stock/current ROM (That isn't CM) you must perform a data wipe/factory reset and wipe the cache. To save data use Titanium backup to backup all your apps, copy all files available to PC and make a Nandroid backup incase the flash fails.
When flashing an update (E.g Cyanogen M6 over M5) most of the time you don't have to backup all apps etc but most people do incase something goes wrong (which it can), however when flashing a nightly/experimental over a M-build you must wipe data and cache.
When flashing a kernel the same rule applies as flashing a new ROM (Backup, Wipe, Restart)
Hope I could help and good luck exploring ROMs and Kernels
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.
I have a stock unrooted Motorola Droid Razr M xt907
4.4.2 OTA OS, but I DID remove a few stock items.
Sys Ver: 182.46.15.XT907.Verison.en.US
Kernel is: July 29 2014
I have never owned or worked with a smartphone before, but have OC exp dating back to MS Dos 1.x-2.1 and have some Linux exp using OpenSuse
If I understand correctly I need to back upi the system files BEFORE ROOTING the device to protect myself in the event I go to far while rooted and bootloop or brick the device.
I am trying to understand how to create a Nandroid backup without rooting, but I'm not understanding quite enough to have any great success.
I''d rather not wipe all the installed apps, but if I need to I'd like to know if I can
- back up apps and settings using a utility that does not require root access
- do a reset
- then back up the virgin unrooted 4.4.2 system files
- Then root
- Then install CM11 (KitKat 4.4.4 based)
- The restore the apps and settings fromt eh (non Nandroid) backup I need to do a real OTA reset because I killed some of the stock apps already. (At least, that's my understanding)
I really appreciate you all being here to help folks! Many thanks in advance!
XDA Visitor said:
I have a stock unrooted Motorola Droid Razr M xt907
4.4.2 OTA OS, but I DID remove a few stock items.
Sys Ver: 182.46.15.XT907.Verison.en.US
Kernel is: July 29 2014
I have never owned or worked with a smartphone before, but have OC exp dating back to MS Dos 1.x-2.1 and have some Linux exp using OpenSuse
If I understand correctly I need to back upi the system files BEFORE ROOTING the device to protect myself in the event I go to far while rooted and bootloop or brick the device.
I am trying to understand how to create a Nandroid backup without rooting, but I'm not understanding quite enough to have any great success.
I''d rather not wipe all the installed apps, but if I need to I'd like to know if I can
- back up apps and settings using a utility that does not require root access
- do a reset
- then back up the virgin unrooted 4.4.2 system files
- Then root
- Then install CM11 (KitKat 4.4.4 based)
- The restore the apps and settings fromt eh (non Nandroid) backup I need to do a real OTA reset because I killed some of the stock apps already. (At least, that's my understanding)
I really appreciate you all being here to help folks! Many thanks in advance!
Click to expand...
Click to collapse
Unlock your bootloader.
Flash the latest TWRP recovery in fastboot.
Make a backup with TWRP.
THEN flash SuperSU to gain root using the TWRP Recovery.
It's actually a great idea to hold onto a non-rooted backup, in case you want to return to stock one day to get an OTA update.
Okay, in looking for directions to unlock the bootloader, I'm jsut finding a lot of hits that begin y saying the phone needs to be rooted first, so I could use a push in the right direction there.
The forum linked here:
http://forum.xda-developers.com/showthread.php?t=2226729
should give you all of the info that you need.
xunholyx said:
The forum linked here:
http://forum.xda-developers.com/showthread.php?t=2226729
should give you all of the info that you need.
Click to expand...
Click to collapse
I'm so confused. The first instruction in the first post is to root the phone, but then how can I get an unrooted Nandroid backup?
I believe the answer I need may be covered here, but I'm not sure I follow how to flash this properly BEFORE rooting the phone. I intend to make a walkthrough on another forum once I get this all sorted, and would be happy to plug XDAD and you for the help.
There is a broken link in the guide you linked me to. I just wanted to make you aware. I have the motorola driver loaded on my Win 7 Ultimate Retail 64 bit driven PC, so I'm good, but the link for the drivers is returning a 404
I'm the one who is confused.
Sorry, I should have read the OP in that link better.
You can backup all of your data using ADB: adb backup -apk -shared -all -f C:\Users\NAME\backup.ab
And restore it using this command: adb restore C:\Users\NAME\backup.ab
Replace "NAME" with your Windows username of course.
There is a more comprehensive guide here.
Read the OP, then go to the last 10pgs or so to see if there is new info (didn't read that far, but the thread is still active).
Okay, I suspect this last link is probably more what I'm after, but before I do that, I'm HOPING it is possible to back up the installed apps and their respective settings first. The reason for this is that I really do want a squeaky clean, uprooted Nandroid backup of the last OTA update supported which, (no surprise), is 4.4.2, which includes the handy Heartbleed bug "feature" and makes the Razr M all but useless.
Of course, as we know, 4.4.4 runs very well on the Razr M and the Heartbleed bug is easily solved by it, but Motorola prefers you buy a new phone, so they introduce a bug, load it on everyone's 1-1/2 year old devices, and they refused to fix it by not allowing users access to the "new" unbroken OLD KitKat platform! You can only run that LAST version of the OLD KitKat on NEW HARDWARE!
The other tactic used on consumers by Motorola and others is not allowing customers to purchase new factory fresh batteries for their devices, whether "non-replaceable" or not. These are two strong-arm tactics adopted that now dominate cellular and other technologies.
I digress.
I am going to HAVE to restore this phone before making the Nandroid because I pulled some stock 4.4.2 Motorola firmware bloat out of it, adn now I need iot back for that backup to be truly virgin. :/
Soooooooo . . . .
The first order of business is to determine if I can add the stock stuff back, or if I have to actually do a reset on the phone. I fear adding the stock items back MAY still leave changes in the system folder, which is not acceptable to me. *IF* I CAN successfully add the stock bloat back in and get a clean Nandroid, I'd be happy about that, though I'd be concerned about it working properly none-the less.
This is why I ask if I can back up apps and app data and later successfully restore that stuff that was backed up under 4.4.2 once I have successfully loaded the (KitKat 4.4.4 based) CM11 Mod.
If the backup of apps and app settings WILL restore to 4.4.4, I'd like to:
- > back up all apps, app data adn user data > reset the phone loading the 4.4.2 OTA BONE STOCK > make my Nandroid of the bone stock unrooted 4.4.2 > Root > Load CM11 MOD ROM > Restore my apps and user data.
I will work on learning to make the unrooted Nandroid some while I wait for a reply, as I'm going to have to do that as a later step.
Giving this a try. I'm about to crash. I'm pretty zonked out.
If all that you want is to save apps and app data, and not system and boot partitions, then use the ADB commands that I posted. That will do exactly what you want.
Oh no no, that's not all I want to do by any means. I am going to load the KitKat 4.4.4 based CM11 ROM, but before I do that I want a clean OTA backup of the stock unrooted KitKat 4.4.2 so I have that to fall back on.
To that end, in preparation for the new ROM I'd like to back up all apps that are currently loaded along with the current app data, and also to back up all personal data.
Once that is done, I need to do a reset to get 4.4.2 back into it;s stock trim as this will be my original 4.4.2 OTA Nandroid.
THEN I will root and install CM11
Then, if it's possible, I'd like to restore all of my current apps and app data.
I've been working on understanding the steps needed to make that unrooted 4.4.2 Nandroid while awaiting suggestions about how to do the app/app data and personal data backup., as well as a yea or neigh about if the app backup can even be successfully restored under the new (4.44 based) os.