hi
Ive just installed Cleanrom, and it seems slower than the stock rom i used before.
I wonder if i should have done a system format in cwm, as doing this for Slimbean on my SGS helped quite a bit...
thanks
geoslake said:
hi
Ive just installed Cleanrom, and it seems slower than the stock rom i used before.
I wonder if i should have done a system format in cwm, as doing this for Slimbean on my SGS helped quite a bit...
thanks
Click to expand...
Click to collapse
Format system is when you delete your ROM, if you want a clean install, yeah you should format system. This also depends on what ROM you want to flash. If you're going to flash stock, format system is good. I do it all the time when I flash stock
But I can also do it whatever the rom, right ? I mean if I upgrade from Cleanrom from 3.03 to 3.04, I cannot go wrong doing that ? (although they don't talk about formatting system in the guidelines).
Thank you
Format system is when you delete your ROM, if you want a clean install, yeah you should format system. This also depends on what ROM you want to flash. If you're going to flash stock, format system is good. I do it all the time when I flash stock
Click to expand...
Click to collapse
format system basically deletes all your system apps, which really isn't worth to do in an update from v3.0.3 to 3.0.4 - if it's a big update with many more apps included maybe it's worth, but otherways it's waste of time...
-angel* said:
format system basically deletes all your system apps, which really isn't worth to do in an update from v3.0.3 to 3.0.4 - if it's a big update with many more apps included maybe it's worth, but otherways it's waste of time...
Click to expand...
Click to collapse
System app? When I use twrp it said wipe system removes ROM, I guess on cwm is called format system.
Well, I guess "format system" should format system (=wipe the os i guess), not remove apps...
geoslake said:
Well, I guess "format system" should format system (=wipe the os i guess), not remove apps...
Click to expand...
Click to collapse
Hmmm why don't you use twrp. It's much better haha
Tamaskan said:
Hmmm why don't you use twrp. It's much better haha
Click to expand...
Click to collapse
Guess so, I guess its no problem to overwrite CWM with TWRP (as long as I load the right version, that is, JB as im on Cleanrom Inheritance 2.7.2)...
Format system on twrp and cwm means the same thing.
When you flash any ROM, all it does is place everything in the /system partition, and sometimes a kernel is also flashed.. this partition contains all files that make up android. All the apps that come with roms, all mods, themes, framework.. everything is here.
When /system is wiped, it deletes all these files to make way for a new rom. Most roms wipe system automatically when they get flashed anyway :good:
However, I think that cleanrom 3.0.3 is a dependancy for 3.0.4, this means that 3.0.4 requires the 3.0.3 system files to work properly. Check the cleanrom changelog or install instructions
Sent from my GT-I9100
Nothing happens, it just clears your data.
Tamaskan said:
System app? When I use twrp it said wipe system removes ROM, I guess on cwm is called format system.
Click to expand...
Click to collapse
I'm sorry, I was thinking of /system/app lol
I think the updates should rule that themselves that they delete the unnecessary things of an old version, so it's only recommended if you change your ROM or update to a ROM based on a later Android Version (4.1 to 4.2 or vice versa) or from AOSP to stock...
Otherwise it's just waste of time I think, I never used it and never had problems, so I think it's pretty good ruled in the updater scripts of the ROMs
Can i install roms on System 1, who and how? pls help, i dont want to break my phone, i 've LiquidSmooth but on System 3, i need more space and the only way its installing on system 1..
Who other roms can i install on system 1, and who are requirement? thx for your help :good::cyclops:
Yes, you can. In fact, I am using just System 1 (AOSB) as my daily ROM.
I don't know if this is required, but I'm always doing the following:
1. Format /system, /data, /cache
2. Wipe System, Cache, Dalvik Cache
3. Install ROM
4. Install GApps
I never had any problems since.
Goodluck mate!
Cheers,
Rae
I have never used any other system other than system 1 as daily driver..i don't know y ppl are so scared to flash..same time two years back we didn't even have a recovery on boot and still used to flash roms courtesy rdavisct, alteredlikeness, jimbridgman n co..this whole concept of multiple systems has made things more complicated than before it seems
Sent from my MB865 running CaRbOn 4.4.3 source built by dmroeder!!
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
devilhunter47 said:
I have never used any other system other than system 1 as daily driver..i don't know y ppl are so scared to flash..same time two years back we didn't even have a recovery on boot and still used to flash roms courtesy rdavisct, alteredlikeness, jimbridgman n co..this whole concept of multiple systems has made things more complicated than before it seems
Sent from my MB865 running CaRbOn 4.4.3 source built by dmroeder!!
Click to expand...
Click to collapse
To the steps mentioned above
Wipe battery stats
After installation go to system keeper option
Install bmm to main system
Reboot
Safer this way
Sent from my MB865 using Tapatalk 2
Raeshabu said:
Yes, you can. In fact, I am using just System 1 (AOSB) as my daily ROM.
I don't know if this is required, but I'm always doing the following:
1. Format /system, /data, /cache
2. Wipe System, Cache, Dalvik Cache
3. Install ROM
4. Install GApps
I never had any problems since.
Goodluck mate!
Cheers,
Rae
Click to expand...
Click to collapse
Thaankss..! bro im gonna try it now..! i did a back up of stock 4.0.4
devilhunter47 said:
I have never used any other system other than system 1 as daily driver..i don't know y ppl are so scared to flash..same time two years back we didn't even have a recovery on boot and still used to flash roms courtesy rdavisct, alteredlikeness, jimbridgman n co..this whole concept of multiple systems has made things more complicated than before it seems
Sent from my MB865 running CaRbOn 4.4.3 source built by dmroeder!!
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
To the steps mentioned above
Wipe battery stats
After installation go to system keeper option
Install bmm to main system
Reboot
Safer this way
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
ohhh i'm really thankful , i was nervous but with this steps i'm sure of wait i'm going to do..
saga02 said:
Thaankss..! bro im gonna try it now..! i did a back up of stock 4.0.4
Click to expand...
Click to collapse
Good luck mate! :good:
@devilhunter47
Thanks for the additional info.
Anyways, I never install BMM after flashing ROMs because it auto-installs after you press back from Install from Zip. Or maybe we just have different experiences regarding this.
Thank you again! :highfive: :good:
Raeshabu said:
Good luck mate! :good:
@devilhunter47
Thanks for the additional info.
Anyways, I never install BMM after flashing ROMs because it auto-installs after you press back from Install from Zip. Or maybe we just have different experiences regarding this.
Thank you again! :highfive: :good:
Click to expand...
Click to collapse
Sometimes it fails to and i had to fxz
Sent from my MB865 using Tapatalk 2
171
devilhunter47 said:
Sometimes it fails to and i had to fxz
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
guys i've a problem, when the installations finish i did "system keeper option", and then show me a mistake, saying "BBM will not start after reboot", and now the phone dont show me BBM and only restart and restart :/ i dont know what to do now, because i can enter to bbm and fix this :S.. I can not even go to android, is happening and I did wrong? : ( And how to fix this please help ..!
Raeshabu said:
Good luck mate! :good:
@devilhunter47
Thanks for the additional info.
Anyways, I never install BMM after flashing ROMs because it auto-installs after you press back from Install from Zip. Or maybe we just have different experiences regarding this.
Thank you again! :highfive: :good:
Click to expand...
Click to collapse
Heelpp..! BMM not appear, and the phone stayed restarting does nothing but nothing out of the motorola logo screen goes black for a minute and not start, should show BBM but no longer does, and prior to the reboot when installation is complete and I gave keeper system option "Install bmm to main system" not only told me BBM started after reboot and so did not know what to do now ..: S can not access the system 3 is where I have q my other system: (help please
saga02 said:
Heelpp..! BMM not appear, and the phone stayed restarting does nothing but nothing out of the motorola logo screen goes black for a minute and not start, should show BBM but no longer does, and prior to the reboot when installation is complete and I gave keeper system option "Install bmm to main system" not only told me BBM started after reboot and so did not know what to do now ..: S can not access the system 3 is where I have q my other system: (help please
Click to expand...
Click to collapse
Sorry to hear that.
So, are you saying that after you installed a ROM in System 1, you force-installed BMM again through System Keeper?
I think you need to FXZ back to stock ICS, then root, then install BMM from the market again.
I think I had the same experience back when I first got this phone and was still experimenting on stuffs.
Anyways, do you know how to FXZ back to stock ICS? There's a guide on how to do that here:
forum.xda-developers.com/showthread.php?t=1937112
Click to expand...
Click to collapse
You SHOULD follow every step mentioned on the thread, and also download the correct FXZ for your phone.
Or you could check my post here:
forum.xda-developers.com/showthread.php?p=53305693#post53305693
Click to expand...
Click to collapse
Just ignore the part where I insist you should download the AT&T FXZ for your phone. That part is for my phone only.
Raeshabu said:
Sorry to hear that.
So, are you saying that after you installed a ROM in System 1, you force-installed BMM again through System Keeper?
I think you need to FXZ back to stock ICS, then root, then install BMM from the market again.
I think I had the same experience back when I first got this phone and was still experimenting on stuffs.
Anyways, do you know how to FXZ back to stock ICS? There's a guide on how to do that here:
You SHOULD follow every step mentioned on the thread, and also download the correct FXZ for your phone.
Or you could check my post here:
Just ignore the part where I insist you should download the AT&T FXZ for your phone. That part is for my phone only.
Click to expand...
Click to collapse
Ready brother could fix all that I did just now was able to install in system 1 and so far everything is fine, the problem was the gapps and they made the bootlooping, I am LiquidSmooth 3.1 (4.4.3) that I can recommend another rom this stable and fast ... thank you very much for your help really'm super grateful to you ..
saga02 said:
Ready brother could fix all that I did just now was able to install in system 1 and so far everything is fine, the problem was the gapps and they made the bootlooping, I am LiquidSmooth 3.1 (4.4.3) that I can recommend another rom this stable and fast ... thank you very much for your help really'm super grateful to you ..
Click to expand...
Click to collapse
Hey, I'm glad that you fixed your phone. :highfive:
Cheers,
Rae
saga02 said:
Can i install roms on System 1, who and how? pls help, i dont want to break my phone, i 've LiquidSmooth but on System 3, i need more space and the only way its installing on system 1..
Who other roms can i install on system 1, and who are requirement? thx for your help :good::cyclops:
Click to expand...
Click to collapse
Dude you can flash ROM's on System 1 but please be careful as it will delete all other data on the other systems.
One more thing if your using altreds CM 11 use the BaNkS minimal gapps, It's not a problem to flash on the system 1, the thing is a failed flash can sometimes lead to you needing a FXZ, so just be careful on which ROM your flashing. :good:
I have little bit confusion. Please guide if these steps are correct:
1. Using BMM, format system 1 partition, data, cache.
2. Clean/wipe data, cache, battery, dalvik
3. Install ROM and GAPPs in system 1
4. system keeper > keep/install BMM
Are these steps correct?
Another question is if I want to install only one ROM in system 1 and want to use all available space for this setup then how to setup the partitions with maximum available space? Or I don't need to setup partitions?
Jack Sparrow xda said:
I have little bit confusion. Please guide if these steps are correct:
1. Using BMM, format system 1 partition, data, cache.
2. Clean/wipe data, cache, battery, dalvik
3. Install ROM and GAPPs in system 1
4. system keeper > keep/install BMM
Are these steps correct?
Another question is if I want to install only one ROM in system 1 and want to use all available space for this setup then how to setup the partitions with maximum available space? Or I don't need to setup partitions?
Click to expand...
Click to collapse
No need to set partition sizes on system 1, that's solely for multi-booting ROMs on systems 3-6. Everything else is good though.
1BadWolf said:
No need to set partition sizes on system 1, that's solely for multi-booting ROMs on systems 3-6. Everything else is good though.
Click to expand...
Click to collapse
Thanks for the info, that was really helpful
But one confusion, I use BMM for flashing ROMs. And in case of BMM, we have to set partitions for system, data and cache. How to do that partitioning step in case if we want to flash ROM in the system 1 ? Won't we have to specify the sizes for all of those partitions?
Another question is, how to fully clean up the system 1 and free up whole ROM space before starting system 1 setup? I mean can I clean everything which came from factory before flashing on the system one to get as big as possible size of internal ROM for the system 1 setup? How much space we can get by doing that? Right now it shows around 2 GB available for user (apps and data) in the 4GB ROM of the Atrix 2, how much would it show in case of custom ROM flashing by freeing up whole space?
Jack Sparrow xda said:
Thanks for the info, that was really helpful
But one confusion, I use BMM for flashing ROMs. And in case of BMM, we have to set partitions for system, data and cache. How to do that partitioning step in case if we want to flash ROM in the system 1 ? Won't we have to specify the sizes for all of those partitions?
Another question is, how to fully clean up the system 1 and free up whole ROM space before starting system 1 setup? I mean can I clean everything which came from factory before flashing on the system one to get as big as possible size of internal ROM for the system 1 setup? How much space we can get by doing that? Right now it shows around 2 GB available for user (apps and data) in the 4GB ROM of the Atrix 2, how much would it show in case of custom ROM flashing by freeing up whole space?
Click to expand...
Click to collapse
System 1 gets partitioned by flashing the FXZ so it's not necessary to do it with BMM. The best way to clean up system for flashing is to flash the FXZ first, then root and install BMM, etc. You can also use BMM to format system, data, cache and dalvik cache if you haven't created partitions for other systems. The only reason you will ever need to create partitions with BMM is to flash on systems 3-6.
1BadWolf said:
System 1 gets partitioned by flashing the FXZ so it's not necessary to do it with BMM. The best way to clean up system for flashing is to flash the FXZ first, then root and install BMM, etc. You can also use BMM to format system, data, cache and dalvik cache if you haven't created partitions for other systems. The only reason you will ever need to create partitions with BMM is to flash on systems 3-6.
Click to expand...
Click to collapse
Oh, I thought BMM will do it on sys 1 as well. I used sys 3 & 4 just to try out various ROMs without risking the stock system so that I can know which ROM suites me and later I can cleanup the whole system and put that ROM of my liking in the main system.
I am not familiar with FXZ method and it seems more complicated to me. isn't there any way to flash ROM on sys 1 and deleting the other partitions?
I am noob in this flashing thing and its been just 10-12 days since I started it up. the bmm method looked easy to me and I would prefer it if its possible to use for this purpose.
Sent from my MB865 using Tapatalk
Jack Sparrow xda said:
Oh, I thought BMM will do it on sys 1 as well. I used sys 3 & 4 just to try out various ROMs without risking the stock system so that I can know which ROM suites me and later I can cleanup the whole system and put that ROM of my liking in the main system.
I am not familiar with FXZ method and it seems more complicated to me. isn't there any way to flash ROM on sys 1 and deleting the other partitions?
I am noob in this flashing thing and its been just 10-12 days since I started it up. the bmm method looked easy to me and I would prefer it if its possible to use for this purpose.
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Flashing the FXZ is actually pretty simple. The main thing to know is which FXZ is the correct one for your phone. (Also it's a really good idea to find THAT out BEFORE you need it.) BMM is far more complicated and confusing IMHO.
Anyway, it's still possible to do a clean flash via BMM if that's what you're more comfortable with, though, so no worries. Just do a factory reset, which will format data, cache, and dalvik. Since that formats the data partition you will lose everything on any other existing systems. (though it may not always be necessary I normally format the system as well. DO NOT reboot at this point or you'll have no choice but to FXZ.) Then you just flash the zip plus gapps and whatever other mods you want. Personally I like to reboot between flashing each zip. In other words, I flash the ROM then reboot. Then gapps and reboot, etc. No repartitioning is necessary for flashing on system 1 and might actually be detrimental so just skip that.
Thanks a lot @1BadWolf, your post clears all doubts in my mind
1BadWolf said:
No repartitioning is necessary for flashing on system 1 and might actually be detrimental so just skip that.
Click to expand...
Click to collapse
Thanks for letting me know about no need of partitioning sys 1. If I wouldn't have been in this discussion with you, I would have ended up creating partitions on system 1 as well like what I have learnt to do on other systems and there would have been a thread by me on getting stuck in bootloop, you saved me from that.
To be bit on more safer side, let me put what I have understood so far:
1. Boot in BMM.
2. Factory reset on system one. (I have two other custom ROMs on system 3 and 4. will it also clear all the other ROMs installed on other systems also?
3. Format partitions on system one.
4. Clear system, data cache etc
5. Install ROM and GApps on system 1
6. Keep BMM in main system
7. Reboot and done
Is there anything broken or wrong in that chain?
One more query, can I keep continue installing ROMs on other systems like what I am doing right now in case of retaining stock ROM?
Hey guys, I'm rather new to the world of customising Android devices. I just have SO MANY QUESTIONS right now. And I'm sure I'm not the only one, which is why I created this thread to help myself and other people.
Basically, I'll be asking a bunch of questions related to the topic, and this can help other people who are new to all this too.
So, I've got a rooted device. It's on lollipop 5.0, has an unlocked bootloader, TWRP recovery, and Xposed framework.
A few questions to start off with:
1) Can I flash multiple .zip/.img files one after another? Or do I need to always wipe my phone's cache after each flash?
2) Say I wanna update TWRP recovery. Do I have do something before flashing it? CAN I flash a newer version over the previous one?
3) Same question as 2) but for Xposed framework instead.
4) I have Xposed framework installed with some modules running on my phone. Should I disable these modules before updating my Xposed?
5) The latest version of Xposed is v86 as given here: http://forum.xda-developers.com/showthread.php?t=3034811
Can v86 work for lollipop?
6) Similarly, can one download any TWRP version and flash it for their device? Or do each build have a different, specific version of TWRP?
7) Are the latest recovery mods and Xposed frameworks always guaranteed to be stable? Or is it safer to stay on the older ones? Which ones would you recommend?
8) Now, the custom ROMS. What are the necessary things to do before flashing one of these?
9) After flashing a custom ROM, can you flash another on top of it? Or do you have to restore back to your original stock ROM?
10) Does flashing and switching between custom ROMs cause any damage to the phone? Or is there any such potential?
11) Since backing up is a must, I'll ask some about that too. Which would you suggest to be the best backing up method?
12) Does creating a NANDroid backup or a backup from within custom recovery(TWRP in my case) equal to creating a backup of stock ROM?
13) Do I need to copy that backup into PC(to restore later), or will it be safe in my phone's memory after flashing a custom ROM?
I guess that's about it for now. Everyone, please answer if you have done these before. And of course, add your own questions too. This can save a lot of time for a lot of people. I could add more questions in if people request it.
**Answer mentioning the question number for simplicity of searching.
Answers!
1) Can I flash multiple .zip/.img files one after another? Or do I need to always wipe my phone's cache after each flash?
Click to expand...
Click to collapse
You can, but it is more recommended to wipe cache and dalvik cache with each flash.
2) Say I wanna update TWRP recovery. Do I have do something before flashing it? CAN I flash a newer version over the previous one?
Click to expand...
Click to collapse
You'll have to wipe dalvik cache and cache and just flash it normally. It might be stuck at 90% but a force reboot fixes it. It is because you are already in recovery. If it is stuck, leave it for 15 mins and come back. This is just to ensure that it really is stuck.
3) Same question as 2) but for Xposed framework instead.
Click to expand...
Click to collapse
Yep, works, except you wont be stuck.
4) I have Xposed framework installed with some modules running on my phone. Should I disable these modules before updating my Xposed?
Click to expand...
Click to collapse
No need
5) The latest version of Xposed is v86 as given here: http://forum.xda-developers.com/showthread.php?t=3034811
Can v86 work for lollipop?
Click to expand...
Click to collapse
Yup, just flash it via recovery
6) Similarly, can one download any TWRP version and flash it for their device? Or do each build have a different, specific version of TWRP?
Click to expand...
Click to collapse
Each build is different for each device, so for example, I can't flash a TWRP for s7 edge on my s4.
7) Are the latest recovery mods and Xposed frameworks always guaranteed to be stable? Or is it safer to stay on the older ones? Which ones would you recommend?
Click to expand...
Click to collapse
In example, xposed and supersu framework and binary lets you choose if you want a stable file or a test one for developers. TWRP and other stuff have (what I know) different versions and as stated, these versions behave different on different device. During testing with my S4, I found that TWRP 2.8.7.0 is the most stable build for my device.
8) Now, the custom ROMS. What are the necessary things to do before flashing one of these?
Click to expand...
Click to collapse
Make a nandroid backup of your whole device and back it up on you computer. Then wipe everything except your external sdcard and either store it on an sdcard or "adb sideload" it.
9) After flashing a custom ROM, can you flash another on top of it? Or do you have to restore back to your original stock ROM?
Click to expand...
Click to collapse
Not on top of it, you'll have to do as the answer to question 8, make a backup, wipe everything and then flash. No need to go back to stock ROM and then flash it
10) Does flashing and switching between custom ROMs cause any damage to the phone? Or is there any such potential?
Click to expand...
Click to collapse
There is always the risk of bricking but as far as software, it is always revertable. As long as you have a backup of course.
11) Since backing up is a must, I'll ask some about that too. Which would you suggest to be the best backing up method?
Click to expand...
Click to collapse
Nandroid backup is the best one.
12) Does creating a NANDroid backup or a backup from within custom recovery(TWRP in my case) equal to creating a backup of stock ROM?
Click to expand...
Click to collapse
It creates a backup of your current state, lets say, you are in Cyanogenmod 13, making a Nandroid backup will backup everything on cyanogenmod so that if you flash another ROM and still want to go back, you'll have everything restored, including app data and apps.
13) Do I need to copy that backup into PC(to restore later), or will it be safe in my phone's memory after flashing a custom ROM?
Click to expand...
Click to collapse
It will take up a lot of space on your device (since it is a backup of your whole device) so it is recommended to copy it to your computer and remove it from the phone. But, as always, make sure you copy the whole "BACKUPS" folder because the folder inside that folder has your device ID and it is required by TWRP to have the folder the exact ID of your phone to prevent anything bad from happening (bricks).
Hope, I answered all the questions as you wanted and if you have a new question, post it here and I'll reply as soon as possible
Hey, thanks a lot for answering. It helps a lot.
A few other questions I have:
14) So if I were to get CM13, and then create a backup of it, and then get another rom, say ASOP, create a backup of that too, and then switch to yet another rom, say Resurrection Remix, create a backup of that too.
Now, is it possible for me to be able to SWITCH between multiple roms, with ALL my data saved individually on each rom perfectly the way I wanted?(of course, wipe cache and data before restoring the backup)
If so, then I could just keep Nandroids of my favorite roms, can keep switching between them, never having to flash and start from scratch ever again!
Sent from my ASUS_T00J using XDA-Developers mobile app
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
16) Suppose I flashed CM13, and it's really buggy. Can I switch back to the previous rom whose nandroid I had just by restoring it? Is it really that simple?
Sent from my ASUS_T00J using XDA-Developers mobile app
ShinraTensei04 said:
Hey, thanks a lot for answering. It helps a lot.
A few other questions I have:
14) So if I were to get CM13, and then create a backup of it, and then get another rom, say ASOP, create a backup of that too, and then switch to yet another rom, say Resurrection Remix, create a backup of that too.
Now, is it possible for me to be able to SWITCH between multiple roms, with ALL my data saved individually on each rom perfectly the way I wanted?(of course, wipe cache and data before restoring the backup)
If so, then I could just keep Nandroids of my favorite roms, can keep switching between them, never having to flash and start from scratch ever again!
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
14) You can, but you would need tons of space.
Sent using a ks01lte (gt-i9506) running cm 13
---------- Post added at 05:59 AM ---------- Previous post was at 05:56 AM ----------
ShinraTensei04 said:
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
You do not have to have an sdcard reader to view your sdcard on your PC. You know how when you make a backup it is stored in /sdcard/TWRP/BACKUPS/CERIALNM/nameofbackup? Well, connect your phone to your pc and move the "backups" folder, then, when you need to restore it, add it to the twrp folder and restore it.
Sent using a ks01lte (gt-i9506) running cm 13
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
ShinraTensei04 said:
15) Since I don't have otg cable, nor an sd card reader, I'm gonna have to keep the nandroid on my sd. Which means a lot of space is needed.
Can this workaround be possible:
- I use TWRP to backup only system and boot data. I save this on sd card.
- I use Titanium backup to save only user app and data. I save this on PC.
So now, when my device crashes while flashing something, I can restore backup from TWRP(do I clear cache and data before this as well?), and once my system rom is back, I can copy titanium backup via USB and restore it.
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
Also, on the titanium backup part, not a bad idea... You can then copy the data and system or boot to your pc and bam.
Sent using a ks01lte (gt-i9506) running cm 13
What I meant was: Let's say I bricked my phone. Now, according to you, I place backup on pc. Okay. But now, how do I place this backup onto the sd on my phone when my pc can't even detect the phone(cuz it's dead yo). Doesn't this impose on me to keep the backup in sd(as I don't have reader or otg).
About the titanium, so you're saying I can do that? Backup only user apps+data and restore after restoring only system+boot.
Another question:
16) Can the backup of user apps+data made on, say, 'X' rom, be restored on 'Y' rom via titanium, on condition they are same Android version(suppose 5.0), without ANY chance of incompatibility. More importantly, can it have any chances of leading to a brick/bootloop.
* I read somewhere that if you backed up system apps of 'X' rom, then changed to 'Y' rom, and restored the system apps of 'X' rom onto 'Y' rom, it bricks the phone.(which is why I ask this question)
17) "Backing up 'system' in TWRP is completely different from backing up 'system' on titanium. This is because TWRP backs up entire system with system apps, while titanium only backs up the apps." This is true, right?
Sent from my ASUS_T00J using XDA-Developers mobile app
ShinraTensei04 said:
What I meant was: Let's say I bricked my phone. Now, according to you, I place backup on pc. Okay. But now, how do I place this backup onto the sd on my phone when my pc can't even detect the phone(cuz it's dead yo). Doesn't this impose on me to keep the backup in sd(as I don't have reader or otg).
About the titanium, so you're saying I can do that? Backup only user apps+data and restore after restoring only system+boot.
Another question:
16) Can the backup of user apps+data made on, say, 'X' rom, be restored on 'Y' rom via titanium, on condition they are same Android version(suppose 5.0), without ANY chance of incompatibility. More importantly, can it have any chances of leading to a brick/bootloop.
* I read somewhere that if you backed up system apps of 'X' rom, then changed to 'Y' rom, and restored the system apps of 'X' rom onto 'Y' rom, it bricks the phone.(which is why I ask this question)
17) "Backing up 'system' in TWRP is completely different from backing up 'system' on titanium. This is because TWRP backs up entire system with system apps, while titanium only backs up the apps." This is true, right?
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
You adb sideload a functioning ROM and once you boot you copy the backup you can flash it via twrp. As for the second question, I have not tested it but it sounds possible.
16) You should not be in a bootloop if you backup like that, the fact that it is even the same android version is making it more likely to work and what I know, you can even switch the backup via phones. I don't use titanium because I always do nandroid backups.
17) Yup, that's true, twrp sees "system as the partition system while titanium sees it as the whole phones software, hence why it is called " system".
Thanks for asking these question and hopefully some day, you can teach others.
RAZERZDAHACKER said:
You adb sideload a functioning ROM and once you boot you copy the backup you can flash it via twrp. As for the second question, I have not tested it but it sounds possible.
16) You should not be in a bootloop if you backup like that, the fact that it is even the same android version is making it more likely to work and what I know, you can even switch the backup via phones. I don't use titanium because I always do nandroid backups.
17) Yup, that's true, twrp sees "system as the partition system while titanium sees it as the whole phones software, hence why it is called " system".
Thanks for asking these question and hopefully some day, you can teach others.
Click to expand...
Click to collapse
Hm... so whenever I brick my phone, I MUST adb sideload to a working rom first, and only then restore the backup I made? Even if I already have a backup saved onto the sd card of my bricked phone? Can I not restore that via TWRP instead? I ask this because if I were to adb sideload first, I'd lose root, unlocked bootloader, and yes, TWRP. So, I'd have to get ALL that done again, and only then restore my backup.
18) Does restoring a backup I made(when I had root access, unlocked BL, custom recovery, xposed) RETAIN all that? Meaning after I restore to that backup, I will still have all that.
Thanks for answering, I'm learning quite a bit. And yeah, I'll make sure to help others with this information too.
ShinraTensei04 said:
Hm... so whenever I brick my phone, I MUST adb sideload to a working rom first, and only then restore the backup I made? Even if I already have a backup saved onto the sd card of my bricked phone? Can I not restore that via TWRP instead? I ask this because if I were to adb sideload first, I'd lose root, unlocked bootloader, and yes, TWRP. So, I'd have to get ALL that done again, and only then restore my backup.
Click to expand...
Click to collapse
You won't lose TWRP or unlocked bootloader, but I will try today by making backup of "cache" and flash it via my sdcard as soon as possible.
18) Does restoring a backup I made(when I had root access, unlocked BL, custom recovery, xposed) RETAIN all that? Meaning after I restore to that backup, I will still have all that.
Click to expand...
Click to collapse
Yup, it makes a backup of every little part of the system (if you include cache and dalvik, I don't, but some do).
Thanks for answering, I'm learning quite a bit. And yeah, I'll make sure to help others with this information too.
Click to expand...
Click to collapse
Okay, made a backup of "cache and the flashing went fine, my hypothesis is that you have to make the backup on the sdcard and not on the phone and move it to the sdcard.
RAZERZDAHACKER said:
You won't lose TWRP or unlocked bootloader, but I will try today by making backup of "cache" and flash it via my sdcard as soon as possible.
Click to expand...
Click to collapse
Actually, when you adb sideload, you need to flash stock fastboot and recovery .img files(at least for my phone), and the bootloader does in fact get locked again, along with losing root. I know cuz I already have done adb sideloading before. So, doesn't that make flashing backup via sd card and TWRP without sideload the only thing I can do? I'm just trying to keep a backup without losing root, unlocked BL, TWRP, even if I gotta give up some space... Just wanna make sure it's safe to do it like that.
RAZERZDAHACKER said:
Yup, it makes a backup of every little part of the system (if you include cache and dalvik, I don't, but some do).
Click to expand...
Click to collapse
I only have "System(1125 mb)", "Data(3480 mb)", and "Cache(0 mb)" listed in TWRP. My cache is 0 mb.... nothing to backup on there?
19) Do I have to unlink my linked apps before creating a Nandroid, or will creating one while linked allow me to retain the link even after wiping data and then restoring the Nandroid?
ShinraTensei04 said:
Actually, when you adb sideload, you need to flash stock fastboot and recovery .img files(at least for my phone), and the bootloader does in fact get locked again, along with losing root. I know cuz I already have done adb sideloading before. So, doesn't that make flashing backup via sd card and TWRP without sideload the only thing I can do? I'm just trying to keep a backup without losing root, unlocked BL, TWRP, even if I gotta give up some space... Just wanna make sure it's safe to do it like that.
Click to expand...
Click to collapse
You wont lose anything during a complete nandroid backup, and, apparently, some devices loose stuff during adb sideload.
I only have "System(1125 mb)", "Data(3480 mb)", and "Cache(0 mb)" listed in TWRP. My cache is 0 mb.... nothing to backup on there?
Click to expand...
Click to collapse
Nothing....... Yet.
19) Do I have to unlink my linked apps before creating a Nandroid, or will creating one while linked allow me to retain the link even after wiping data and then restoring the Nandroid?
Click to expand...
Click to collapse
Unlink? What do you mean? (Not quoting Justin Bieber)
RAZERZDAHACKER said:
Unlink? What do you mean? (Not quoting Justin Bieber)
Click to expand...
Click to collapse
There's this thing you can do where you move your apps from internal storage to sd card COMPLETElY, thereby saving a lot of space on internal memory. It works because a 'link' is created between the app+data(now in sd) back to it's internal location counterpart(where it would have been otherwise). This way, the apps and system think your apps are in internal, but in fact are in sd(you can see that more internal is free by checking space used up via any file manager though).
In order to do this, a second partition on the sd card is to be made with an ext2/ext4 format, and use a linking app( like Apps2sd).
ShinraTensei04 said:
There's this thing you can do where you move your apps from internal storage to sd card COMPLETElY, thereby saving a lot of space on internal memory. It works because a 'link' is created between the app+data(now in sd) back to it's internal location counterpart(where it would have been otherwise). This way, the apps and system think your apps are in internal, but in fact are in sd(you can see that more internal is free by checking space used up via any file manager though).
In order to do this, a second partition on the sd card is to be made with an ext2/ext4 format, and use a linking app( like Apps2sd).
Click to expand...
Click to collapse
Yea I've used one of those, I first thought the app used the "MV" Unix command but yea you need a sec. Partition to do that on the sdcard, but you don't have to do that on your nandroid backup.
RAZERZDAHACKER said:
Yea I've used one of those, I first thought the app used the "MV" Unix command but yea you need a sec. Partition to do that on the sdcard, but you don't have to do that on your nandroid backup.
Click to expand...
Click to collapse
So can I backup linked apps with their links' data saved, so when I install the linking app again, they can be relinked automatically?
Sent from my ASUS_T00J using XDA-Developers mobile app
Thanks for those questions and answers. I posted this before but appearantly in the wrong place. It seems to be quite right here. Thanks to helping people!
Hi XDA experts
I am newly registered in the forum, but experienced in modding (more or less). But I am (for now) strictly a user, not developer.
So far I got along very well, with my beloved Galaxy S4 jfltexx. I got from stock to rooted stock, from there to cm, instantly back to stock, used it for a long time and am just now on cm13 nightly, which is truly awesome!
It is so awesome that I would really like to help other people out, even if they have no idea about this. Meaning I wish to modify other peoples phones for them. However, when it comes to other peoples property I can't really fight my way through technical terms I don't understand anymore, hoping that the outcome will be as I wished. I pretty much know what most of all these technical terms mean, but I don't always understand how they are related to each other. I know, explaining this will take a while, but I would REALLY appreciate it if someone would take the time...
1) The bootloader, can it be replaced? What would be the purpose of that? UNLOCKING does not mean REPLACING, does it??
What do custom ROMs typically consist of? An entire working system? Parts of a working system? Sometimes this sometimes that?
I'm asking the question because I got the impression that some custom ROMs require the user to have a certain (usually stock) ROM in order to flash it. For example, if I had a Galaxy S6 edge running 5.1.1, could I upgrade to noble ROM Marshmallow?
I also have the feeling that the ROM or system or whatever is somewhat seperate from the kernel. What is this relation? Do custom ROMs not always come with a compatible kernel? Is there only one kernel compatible to the rest of the system, or is there a chance to run a system with a kernel not particularly designed for it? How to get a 'wrong' kernel?
Where to get stock ROMs and who provides them? If I wanted to upgrade from Lollipop to Marshmallow, but am rooted and don't get OTA updates, what do I do? Assuming that Nandroids are bound to a single device (e.g. MY phone) who can provide a stock ROM that runs on my device and how does he get it?
Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Is there ANY phone SOLD with open bootloader and root? A phone that actually wants its users to play with the system?
Thanks guys
NoBullsh1t said:
Thanks for those questions and answers. I posted this before but appearantly in the wrong place. It seems to be quite right here. Thanks to helping people!
Click to expand...
Click to collapse
It happnes alot that people post in wrong section
Hi XDA experts
I am newly registered in the forum, but experienced in modding (more or less). But I am (for now) strictly a user, not developer.
So far I got along very well, with my beloved Galaxy S4 jfltexx. I got from stock to rooted stock, from there to cm, instantly back to stock, used it for a long time and am just now on cm13 nightly, which is truly awesome!
Click to expand...
Click to collapse
Yup, kinda same, excpet im ks01lte but I moved from stock to rooted stock (5.1.1) then cm13, then stock + xposed 4.4.2 then cm11 and now back to cm13 nightly
It is so awesome that I would really like to help other people out, even if they have no idea about this. Meaning I wish to modify other peoples phones for them. However, when it comes to other peoples property I can't really fight my way through technical terms I don't understand anymore, hoping that the outcome will be as I wished. I pretty much know what most of all these technical terms mean, but I don't always understand how they are related to each other. I know, explaining this will take a while, but I would REALLY appreciate it if someone would take the time...
Click to expand...
Click to collapse
1) The bootloader, can it be replaced? What would be the purpose of that? UNLOCKING does not mean REPLACING, does it??
Click to expand...
Click to collapse
The bootloader can be replace, however, if you fail here, there is no comming back (you'll need a complete board replacement because the bootloader acts as a BIOS), the purpose of replacing it is various reasons, change of splash screen during boot etc. Some bootloaders are locked to only be able to flash certain ROMs (OEMs do this to not allow people to tinker with their devices) but it is nearly always un-lockable (except for some devices, I own an Acer tablet that has a locked bootloader that cant be un-locked) and no, unlocking it does not mean changing it.
What do custom ROMs typically consist of? An entire working system? Parts of a working system? Sometimes this sometimes that?
Click to expand...
Click to collapse
Yea, sometimes this sometimes that, in example, ported marshamllow touchwiz ROMs rely on some files in the stock ROM so the "update" doesn't take up much space.
I'm asking the question because I got the impression that some custom ROMs require the user to have a certain (usually stock) ROM in order to flash it. For example, if I had a Galaxy S6 edge running 5.1.1, could I upgrade to noble ROM Marshmallow?
Click to expand...
Click to collapse
That is because of the bootloader (again lol), from my experience with the s4, before flashing cm13, I had to go to 5.1.1 because of the bootloader was changed during the OTA, so as stated before, it only allowed a certain type of ROMs to be flashed.
I also have the feeling that the ROM or system or whatever is somewhat seperate from the kernel. What is this relation? Do custom ROMs not always come with a compatible kernel? Is there only one kernel compatible to the rest of the system, or is there a chance to run a system with a kernel not particularly designed for it? How to get a 'wrong' kernel?
Click to expand...
Click to collapse
The kernel tells the system what to do, some kernels are specified for battery optimization, so the kernel tells the cpu to slow down and save juice, while some other kernels offer the ability to overclock the device (mostly used on older devices to make it faster, but it drains more juice and can result into app crashing), the kernel, is not separated from the system, in fact, you can't even compile a ROM without a kernel. There is not only one kernel for lets say cm, you can flash another kernel, just make sure it is compatible with your android version. To get a wrong kernel, flash one that isn't for your device or android version.
Where to get stock ROMs and who provides them? If I wanted to upgrade from Lollipop to Marshmallow, but am rooted and don't get OTA updates, what do I do? Assuming that Nandroids are bound to a single device (e.g. MY phone) who can provide a stock ROM that runs on my device and how does he get it?
Click to expand...
Click to collapse
Your OEM provides them, samsung has a website called sammobile and uploads all the stock ROMs there. If you want to upgrade, just flash it via recovery or in your case, odin (for samsung phones). To give your backup to someone else, the other person must have the exact same phones, in example, you (jfltexx) can't give it to me (ks01lte), I must have jfltexx and then (assuming you did the backup on twrp) I'd have to change the serial number to my device.
Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Click to expand...
Click to collapse
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features.
Is there ANY phone SOLD with open bootloader and root? A phone that actually wants its users to play with the system?
Thanks guys
Click to expand...
Click to collapse
There are a few devices like that, one plus was a company that wanted to do that, it came with root, unlocked bootloader and cyanogenmod running, they separated unfortunatly and evolved to using "oxygen os" and does nor provide a un-locked bootloader but provides a simple tool to root and unlock. I don't know any companies that have unlocket bootloaders because they don't want the average consumer to mess up their device and blame it on the OEM.
"Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features."
I mean is there like a website from google where I can dowoad a non device specific aosp and flash that to my S4 to make it run? Wouldn't there be for example drivers missing? Isn't that what I have to be greateful to Cyanogenmod for, making up to date android compatible with older devices?
---------- Post added at 07:49 PM ---------- Previous post was at 07:42 PM ----------
So I can actually make a jfltexx Nandroid and install it on another jfltexx by easily changing the serial number???
NoBullsh1t said:
"Can I run pure Android on any phone, or is it (always?) necessary to adjust it? I understand that my hardware buttons of the S4 would probably not work on pure Android, but the rest?
Your hardware buttons will work on pure android (aosp), I don't see why not, you said you are running cm13, that is altered pure android and it works fine, see pure android as cm withou all the features."
I mean is there like a website from google where I can dowoad a non device specific aosp and flash that to my S4 to make it run? Wouldn't there be for example drivers missing? Isn't that what I have to be greateful to Cyanogenmod for, making up to date android compatible with older devices?
Click to expand...
Click to collapse
Yes, be greatful, it is free, open source and full of active devs and memebers. I'm still not sure what you mean, do you mean on-screen navigation bar? Because you can change that in cyanogenmod settings.
---------- Post added at 07:49 PM ---------- Previous post was at 07:42 PM ----------
So I can actually make a jfltexx Nandroid and install it on another jfltexx by easily changing the serial number???
Click to expand...
Click to collapse
Yea, you know how your backup is located in /sdcard/TWRP/BACKUPS/SERIALNO? The device you want to flash it to should make a backup of the tiniest partition (usually cache, it's 5mb) and youll get acces to the serial number, then you just swap it and delete the tiniest partition.