Related
CWM doesnt seem to work for me. Why do more cooks just do DFT?
Because its easier, and works for 99% of people if you follow directions,and also wrong section for this post.
actually just to thorw my thoughts there. i perfer DTF. i find it kind of disappointing that theres alot of CWM but not of DFT going on.
DEV's please do DFT along with your CWM!!! thank you
And to add to the posts above mine, flashing via cwm is standard on Android phones....
Cwm is way better imo. You need to use selected partitions with each build type. I say make em all flashable through cwm.
I don't get why some have issues with CWM. It's SO much simpler to use in long term operations or if you're a flashoholic. If you say it doesn't work for you, obviously you've done something wrong. Most of the time, it's all a question of having the right partition sizes. If you want ALL ROMs to be compatible, simply flash the 400Mb CWM partition layout and use App2SD+ if you have a leo. If you're a Gingerbread type of guy, flash the 150mb partition size and you're set! Personally what I do is 30mb cache, 120mb system and the rest for data.
Also, some people have issues with CWM because they most likely have issues with their flash. Easiest way to recover is to flash a stock WinMo ROM, restore SPL, format SD card and start all over again.
These forums have TONS of information on how to use CWM and get it up and running, so I don't get it...
yh I like CWM better. Just much neater I think.
Just my opinion
Plus you don't even need a computer. Also if your applying a theme and it messes up, you can just flash your recovery. Dft if you mess up you have to start over.
maybe the reason why i have not tried the CWM is beacuse of the partions stuff. i really dont get it.... and i have gotten fast at setting up ym phone. all my usefull apps are backed up on a box.net account just download and install. no problem. so yeah.
DFT all the way, until sooner or later all of them will be CWM and ill have to change over to it eventually... btu int he mean time DFT!
CWM..........it is!!
CWM is definatly easier. I will admit I was reluctant at first to switch from DFT. Old habits die hard I suppose. But now I can download a new rom and flash it from anywhere. And the backup is awesome to have!! Besides the roms are usually easier to put together for the dev's too. However, the one drawback, IMHO, is different roms require different partition sizes. If CWM were flashable from magldr, or a one size fits all standard were created this would eliminate the need for a pc connection all together.
Clockworkmod benefits=
1. You can make a FULL backup
2. You can make a FULL restore
3. You can wipe each individual part (data, system, sd-ext etc.)
4. You can flash other mods very easily
5. You can do EVERYTHING from your phone including download & flashing the ROM
6. You can wipe dalvik cache and normal cache to save space
7. You can format or partition your SD-card
8. You can store as many ROM's on your SD card to flash at a later time as you want
9. Which is most important!! you can update to a newer version of your favorite ROM without losing ONE THING!!
10. You can fix permissions and wipe battery stats
These are just 10 things I just thought of on the top of my head lol. I think most people don't like it because they haven't gave it long enough of a chance. If your coming from another Android device like me that had Clockworkmod then you couldn't live without it!! I can't think of ONE reason that MAGLDR builds are better than "flashable zips". This is just my opinion
@moto +1 - my man!
About partitions..... only thing u need to know about it is....
Look at the rom u want to flash. You need to know the size of it after it is unzipped. Think of your phone as a box. And your rom as what u want to get in the box. Your not going to fit a sense rom in a 150 mb. partition "box" because its just to big 200+mb. So get a bigger box. Use the 400mb box. If you have a non tmobile hd2 u will need more space to pack your apps and userdata into. Your rom is the first thing in the box and its already almost full, so once your phone starts packing your apps and userdata into the box it gets full really fast. This is where apps2sd and sdcard partitions come into play, think of it as strapping a smaller box ontop of your 400mb box and shipping for the same price. Basically make sure your box (partition) is big enough to fit all your **** in. Easy cheesy!!!!
Sent from my HD2 using XDA App
motoman234 said:
Clockworkmod benefits=
1. You can make a FULL backup
2. You can make a FULL restore
3. You can wipe each individual part (data, system, sd-ext etc.)
4. You can flash other mods very easily
5. You can do EVERYTHING from your phone including download & flashing the ROM
6. You can wipe dalvik cache and normal cache to save space
7. You can format or partition your SD-card
8. You can store as many ROM's on your SD card to flash at a later time as you want
9. Which is most important!! you can update to a newer version of your favorite ROM without losing ONE THING!!
10. You can fix permissions and wipe battery stats
These are just 10 things I just thought of on the top of my head lol. I think most people don't like it because they haven't gave it long enough of a chance. If your coming from another Android device like me that had Clockworkmod then you couldn't live without it!! I can't think of ONE reason that MAGLDR builds are better than "flashable zips". This is just my opinion
Click to expand...
Click to collapse
+1 Best explanation about CWM, DFT is good to start form scratch. Go with CWM and you never look back.
I just CAN'T believe it!!! People keep asking the same question everyday....
How disappointing...
Anyone left with working brain cells??
LOL
bigdookie said:
CWM doesnt seem to work for me. Why do more cooks just do DFT?
Click to expand...
Click to collapse
It's all a conspiracy, the devs all got togehter and said if they only build CWM builds then bigdookie won't be able to flash any of the builds LOL
Seriously though, CWM is so easy to use (besides the benefits pointed out by motoman) - especially if you're on magldr 1.13 - just decide what partition size you need for your zip rom (usually specified in the rom thread) and flash it - you even get to use DAF to flash the partition, so you shouldn't have any problem
To access CWM, in magldr menu go to AD Recovery and you are in Recovery mode.
I just started using CWM and love it,my main question is this. if i try a rom i like, get it all set up and working, and then make a backup in cwm, do i need to keep the copy of the zipped rom on my card, or is the backup enough?
along those same lines, if i try a second rom, and then get it set up and do a backup, can i just restore from the previous roms cmw backup file, or do i have to reflash the previous rom and then do the restore?
just curious, cuz i like trying different roms, but i want to keep a "safety" restore point no matter what rom i switch to.
I hope this makes sense?
Thanks in advance.
dezaras6 said:
I just started using CWM and love it,my main question is this. if i try a rom i like, get it all set up and working, and then make a backup in cwm, do i need to keep the copy of the zipped rom on my card, or is the backup enough?
along those same lines, if i try a second rom, and then get it set up and do a backup, can i just restore from the previous roms cmw backup file, or do i have to reflash the previous rom and then do the restore?
just curious, cuz i like trying different roms, but i want to keep a "safety" restore point no matter what rom i switch to.
I hope this makes sense?
Thanks in advance.
Click to expand...
Click to collapse
The backup will contain everything you need to do a full restore. You can trash the zip of the rom. If you need it again for some reason just download it again. You can have as many different backups as your sdcard can hold. They are saved in the clockwork folder by date and time. By the way your sdcard will fill up fast doing 4 or 5 backups so don't be alarmed when it is suddenly full, just go delete old ones. Or do like me and tape another 16gb sdcard under your battery cover(fits perfectly on top of the sim card with a lil hanging out over the battery). Flash away. Also...... we are all posting in a thread that is in the wrong section
Sent from my HD2 using XDA App
Sent from my HD2 using XDA App
Okay, so you all CWM fans jsut might have agained a new member to the fan club. But i got a question. I have a US HD2. which partion should be best for me?
Hi guys, I am trying to flash this ROM, I have to tell you that it is the first time I am doing it, but having problem. I have razr M rooted with supperSU, safestrep 3.11. I rebooted into SS3.11 and tried to create a ROM Slot, but it does nothing. I go to either rom slot out of 4 and see options, but nothing happens when I press create ROM button. I do message Space :0MB at the botom, although I have at least 10GB free on SD card and at least 2.5GB on the internal memory. Can you pelase help-Gene
gene.volchenko said:
Hi guys, I am trying to flash this ROM, I have to tell you that it is the first time I am doing it, but having problem. I have razr M rooted with supperSU, safestrep 3.11. I rebooted into SS3.11 and tried to create a ROM Slot, but it does nothing. I go to either rom slot out of 4 and see options, but nothing happens when I press create ROM button. I do message Space :0MB at the botom, although I have at least 10GB free on SD card and at least 2.5GB on the internal memory. Can you pelase help-Gene
Click to expand...
Click to collapse
I also replied to your question on DroidRzr.com.
When you create a new ROM slot in SS, all it does is setup the partitions for you to safely flash a new ROM. After the ROM slot is created, you need to choose the "Install" option for that ROM slot. Then, you will choose the "Energy ROM" zip from your SD. Make sure you only install aftermarket ROMs in one of the additional ROM slots, not in stock. Once you are comfortable with the new ROM, there are ways to install the ROM in the stock slot, but that will come in play later on
RikRong said:
I also replied to your question on DroidRzr.com.
When you create a new ROM slot in SS, all it does is setup the partitions for you to safely flash a new ROM. After the ROM slot is created, you need to choose the "Install" option for that ROM slot. Then, you will choose the "Energy ROM" zip from your SD. Make sure you only install aftermarket ROMs in one of the additional ROM slots, not in stock. Once you are comfortable with the new ROM, there are ways to install the ROM in the stock slot, but that will come in play later on
Click to expand...
Click to collapse
He nailed it. I will note that you say you have as 3.11. The latest for the RAZR M is 3.12. It can be found on droidrzr.com. Good luck!
timpohladthomas said:
He nailed it. I will note that you say you have as 3.11. The latest for the RAZR M is 3.12. It can be found on droidrzr.com. Good luck!
Click to expand...
Click to collapse
I installed V3.12, although in the applications view it says V3.12 and when I go to the safestrap recovery it says v3.11 (TWRP v2.2.2.1) strange ??
I go in Boot Options/ROM-Slot-1 chose wither 1GB, or 2GB or 3GB while System partition size of 1024MB and Cache partition size of 300 MB are already selected, at the bottom I see "Free Space:0MB (while I still have 10GB of SD and 3GB of internal free memory). Create ROM slot button does notv respond or does nothing when I press it.
Can you please help? Gene
gene.volchenko said:
I installed V3.12, although in the applications view it says V3.12 and when I go to the safestrap recovery it says v3.11 (TWRP v2.2.2.1) strange ??
I go in Boot Options/ROM-Slot-1 chose wither 1GB, or 2GB or 3GB while System partition size of 1024MB and Cache partition size of 300 MB are already selected, at the bottom I see "Free Space:0MB (while I still have 10GB of SD and 3GB of internal free memory). Create ROM slot button does notv respond or does nothing when I press it.
Can you please help? Gene
Click to expand...
Click to collapse
Safestrap must not be recognizing the free space on your internal sd card. I would recommend uninstalling safestrap, just to be safe confirm your root with root checker, and then install safestrap again. Just use a 1 gb rom slot to avoid any problems that may be occuring due to memory. Post back if the problem persists.
bgregs514 said:
Safestrap must not be recognizing the free space on your internal sd card. I would recommend uninstalling safestrap, just to be safe confirm your root with root checker, and then install safestrap again. Just use a 1 gb rom slot to avoid any problems that may be occuring due to memory. Post back if the problem persists.
Click to expand...
Click to collapse
Hi, I finally was able to install the ROM and power the phone up, but cannot really enjoy it, because cannot use company emails... My company requires storage formatting and wile this option exist on this ROM, it looks like it does not work, neither through the option provided via exchange remote service nor locally by going to settings\ security\format. Is there an option to do that? Also I am constantly running on the low memory. I wiped all apps from stock rom slot, did factory reset and wiped cashe etc, allocated 2gb to Rom slot1 and after installing rom there, before any apps installed, I only have 1.1gb free. Is there any way to increase storage? Last but not least camera with phosphere works even kind of in sphere mode, but the alignment movement is as slow as it could possibly be, it takes a min to move from first picture to the second. Did any guys experienced that?
Thanks a lot in advance for help---Gene
gene.volchenko said:
Hi, I finally was able to install the ROM and power the phone up, but cannot really enjoy it, because cannot use company emails... My company requires storage formatting and wile this option exist on this ROM, it looks like it does not work, neither through the option provided via exchange remote service nor locally by going to settings\ security\format. Is there an option to do that? Also I am constantly running on the low memory. I wiped all apps from stock rom slot, did factory reset and wiped cashe etc, allocated 2gb to Rom slot1 and after installing rom there, before any apps installed, I only have 1.1gb free. Is there any way to increase storage? Last but not least camera with phosphere works even kind of in sphere mode, but the alignment movement is as slow as it could possibly be, it takes a min to move from first picture to the second. Did any guys experienced that?
Thanks a lot in advance for help---Gene
Click to expand...
Click to collapse
As far as the email goes, I'm not sure. I'm not sure which ROM you're using now, but I believe that the 4.2 camera that is available on the ROMs for our phone isn't fully functional yet. Last I checked photoshpere doesn't work, but I could be wrong. The way I increased storage on my phone was to install my new ROM on to the stock partition. This is possible with safestrap, but you will want to make sure you have a backup of your stock ROM just in case something goes wrong. Once you make the backup of your stock ROM, download the custom ROM on to a different partition and set it up as you like. Then, make a backup of the custom ROM in recovery. Delete the partition that you created for the custom ROM and RESTORE the custom ROM backup on the stock partition. Restoring is important because installing does not work (I bricked my phone doing that). Then install safestrap on your new custom ROM and enjoy all the free space you had with your stock ROM!
bgregs514 said:
As far as the email goes, I'm not sure. I'm not sure which ROM you're using now, but I believe that the 4.2 camera that is available on the ROMs for our phone isn't fully functional yet. Last I checked photoshpere doesn't work, but I could be wrong. The way I increased storage on my phone was to install my new ROM on to the stock partition. This is possible with safestrap, but you will want to make sure you have a backup of your stock ROM just in case something goes wrong. Once you make the backup of your stock ROM, download the custom ROM on to a different partition and set it up as you like. Then, make a backup of the custom ROM in recovery. Delete the partition that you created for the custom ROM and RESTORE the custom ROM backup on the stock partition. Restoring is important because installing does not work (I bricked my phone doing that). Then install safestrap on your new custom ROM and enjoy all the free space you had with your stock ROM!
Click to expand...
Click to collapse
Okay, so here is the issue that I'm having. I have everything set up (SafeStrap, downloaded Eclipse v1.2 ROM, have it saved to my SD card), but when I go to actually flash the ROM, the screen says that it failed/unable to flash. I've tried removing the ROM slot, creating it again, and still getting the same issue. Also tried going into the stock recovery and clearing the cache partition from there, wiping the data, etc. Still got nothing. So now I'm really confused as far as what the problem is?
jase5273 said:
Okay, so here is the issue that I'm having. I have everything set up (SafeStrap, downloaded Eclipse v1.2 ROM, have it saved to my SD card), but when I go to actually flash the ROM, the screen says that it failed/unable to flash. I've tried removing the ROM slot, creating it again, and still getting the same issue. Also tried going into the stock recovery and clearing the cache partition from there, wiping the data, etc. Still got nothing. So now I'm really confused as far as what the problem is?
Click to expand...
Click to collapse
It's been a while since I've used SafeStrap so I'm not completely sure what the issue could be. Are you opposed to unlocking your bootloader? If not, there's a great selection of ROMs out there that are very amazing. Our phone has been receiving a lot of dev support lately and they have put much time in to some of these newer ROMs. I would recommend unlocking and installing a custom recovery to flash these with. There are many stock based ROMs out there that you can choose from if you prefer those, or there is a great deal of CM support as well. If you have any questions, don't hesitate to send me a message and I can walk you through the steps of unlocking and installing a custom recovery!
bgregs514 said:
It's been a while since I've used SafeStrap so I'm not completely sure what the issue could be. Are you opposed to unlocking your bootloader? If not, there's a great selection of ROMs out there that are very amazing. Our phone has been receiving a lot of dev support lately and they have put much time in to some of these newer ROMs. I would recommend unlocking and installing a custom recovery to flash these with. There are many stock based ROMs out there that you can choose from if you prefer those, or there is a great deal of CM support as well. If you have any questions, don't hesitate to send me a message and I can walk you through the steps of unlocking and installing a custom recovery!
Click to expand...
Click to collapse
Well here's the thing. I don't think that I can unlock my bootloader now. I've tried using the steps that were provided, but I guess that since I just got the phone a few days ago, it's downright impossible for me to do so. That's why I installed SafeStrap - because of that issue. If it was possible for me to unlock my bootloader now, I sure as heck would rather do that than go through the process I've gone through for the past couple of days. I will send you a message, and maybe you can help me out with unlocking the bootloader if it's possible?
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
This is the only way that Ive been able to unlock my bootloader, run this utility and if it says Status code: 3 you are in luck! Even if it doesnt have the Unlocked Bootloader Warning upon startup you still are unlocked.
Good luck!
Just got a GTab 2 7.0 a few days ago. A P3113, so only 8GB of storage, about half of which is the ROM and crap apps. I've rooted before (had a KF 1st gen when it came out), and just wondering about a few things with the GTab:
Right now, I don't mind the stock ROM so much. There are problem things that would be "nice to have", but right now, would like to generally stay as "stock" as possible. That being said, I'd still like to "de-crap" the ROM to free up some storage space, and I assume that might lead to it running a bit better, since so much seems to just pop-in while running other apps. So:
I know I need to root first, so my first question - how reliable is that? I'm on a Mac, but have access to a netbook running Win7, so could run Odin to "get things done". I'd hate to brick the thing, still having 51 weeks of warranty left. (I also understand that I might want to install something else to keep the flash count from showing it's been flashed).
Once root'ed, is it better to use one of the "de-crapped" ROMs floating around? And if so, which seems "best" (yeah, I know the moderators hate the "which is best" - I'm looking for stock - and STABLE)
Or, is it better to eliminate the apps myself? (Not sure if this is a wholesale "rm" to remove certain apps from a terminal app, using adb, or if they have some uninstallers embedded somewhere, or...) - so better to use one of the ROMs floating around?
Is the GTab 2 "stable", so even if you trash a ROM, you can still get into the ROM manager to restore a previously working, or stock, ROM?
I'll probably come up with a couple more questions, especially depending on the replies... TIA
Hi..
I can answer some of your questions. I hope that helps!
1- Rooting is easy and reliable. you may use "CF-Auto-Root" tool (search for it in XDA forum).
But you need to remember that rooting and custom ROMs void your warranty.
2- If you just need to free some storage space, you may use an app such as "Clean Master" to uninstall system apps and get rid of temp and junk files.
3- If you opt to use a custom ROM make sure it is very well supported and maintained.
aisais said:
Hi..
I can answer some of your questions. I hope that helps!
1- Rooting is easy and reliable. you may use "CF-Auto-Root" tool (search for it in XDA forum).
But you need to remember that rooting and custom ROMs void your warranty.
2- If you just need to free some storage space, you may use an app such as "Clean Master" to uninstall system apps and get rid of temp and junk files.
3- If you opt to use a custom ROM make sure it is very well supported and maintained.
Click to expand...
Click to collapse
Thanks - but prior to using Clean Master I assume I better either get a stock image to reload, or use CWM so I can make a backup of the ROM before messing something up?
tundrwd said:
Thanks - but prior to using Clean Master I assume I better either get a stock image to reload, or use CWM so I can make a backup of the ROM before messing something up?
Click to expand...
Click to collapse
Taking a backup is always good thing to do. I suggest you try clean master to know how it works and what does it do.
aisais said:
Taking a backup is always good thing to do. I suggest you try clean master to know how it works and what does it do.
Click to expand...
Click to collapse
Thanks - I plan to use Clean Master. Allows me to be selective about what I remove/move, instead of getting a ROM from someone and they removed the ONE THING I really wanted.
Ok, got it rooted and CWM installed.
HOWEVER, when I boot into CWM, I DON'T see an option to backup my ROM (I've used TWRP before on my KF, so the menu is different).
What I've got on my screen in CWM:
Android system recover <3e>
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
That's it. Where's the option to do a ROM backup? Oh, used file P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip Had CWM and Root all in one. I do have GT-P3113_ClockworkMod-Recovery_6.0.1.0.tar as well. Should I just go through procedure again to flash this CWM? Will it still retain SU?
nandroid backup ok to use? Seems it's just a wrapper for a backup script...
Ok - I'll reply to myself.
I don't know what was wrong with the CWM I installed via the aforementioned file (P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip), but I went to the CWM site, D/L'ed the latest touch enabled CWM for the P3113 (6.0.2.3, I believe), and installed it over the existing recovery image on the device (I had to create my own .tar.md5 - easy with *nix).
Anyway, I now have access to the backup options by scrolling down. The image from P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip, simply wouldn't scroll beyond what I listed earlier. Now can scroll down, make backups, etc.
Haven't tried yet to re-install the image I made with nandroid - I'm a bit leery of that - so I'll just get the stock 4.1.1 ROM from sammobile, and keep it around....
tundrwd said:
Ok - I'll reply to myself.
I don't know what was wrong with the CWM I installed via the aforementioned file (P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip), but I went to the CWM site, D/L'ed the latest touch enabled CWM for the P3113 (6.0.2.3, I believe), and installed it over the existing recovery image on the device (I had to create my own .tar.md5 - easy with *nix).
Anyway, I now have access to the backup options by scrolling down. The image from P3113_SAMSUNG_RECOVERY_SUPERSU-0.96_BUSYBOX-1.20.2.tar.md5.zip, simply wouldn't scroll beyond what I listed earlier. Now can scroll down, make backups, etc.
Haven't tried yet to re-install the image I made with nandroid - I'm a bit leery of that - so I'll just get the stock 4.1.1 ROM from sammobile, and keep it around....
Click to expand...
Click to collapse
That's exactly what I did today, grabbed the stock image for a backup, rooted with Odin and CWM then flashed a CM based 4.3 ROM. Piece of cake.
My apologies if this has been covered. I've successfully rooted and unlocked the bootloader. I've tried my best to do a lot of reading including going through item by item in the xda wiki glossary but I'm still a little confused/want clarification before I actually do anything with my phone.
My goals are:
1) To create a full .img backup of my current system so I can always go back to it if needed/worst case scenario
2) Create a list of all my installed apps. Backup a few select apps that contain data within them that does not get backed up in the cloud or appear in a copyable source anywhere when i browse the phone directories (an app called Pattrn specifically that stores favorited background images..)
3) wipe/clear the my current incarnation of kitkat and re-install it 'fresh' (possibly without the bloat?), then reload desired apps.
4) create a backup .img of this new instance.
-----------------
I'm generally pretty quick to learn technical content but I've honestly tried to fully grok the steps for the last two weeks and haven't gotten there/understand enough to be confident to do what I think I need to do.
can take this to PM if anyone has some patience to work with me. Gladly donate to any app you make or paypal a few bucks if you can help walk me through this..
My understanding is that I need to get TWRP or CWM installed in order to get a custom recovery (as opposed to a stock recovery process)---which will allow me to do step 3. But even getting TWRP going I'm confused..
Thanks
water- said:
My apologies if this has been covered. I've successfully rooted and unlocked the bootloader. I've tried my best to do a lot of reading including going through item by item in the xda wiki glossary but I'm still a little confused/want clarification before I actually do anything with my phone.
My understanding is that I need to get TWRP or CWM installed in order to get a custom recovery (as opposed to a stock recovery process)---which will allow me to do step 3. But even getting TWRP going I'm confused..
Thanks
Click to expand...
Click to collapse
can't help with everything..but with custom recovery..the easiest way is download flashify from play store and flash recovery image with itfrom here http://androidhosting.org/Devs/Dhacker29/msm8960/ you have a Razr M on kitkat use this one http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
copy it to sdcard or internal storage...open flashify and select recovery image then choose the downloaded file..flash it and restart
water- said:
My apologies if this has been covered. I've successfully rooted and unlocked the bootloader. I've tried my best to do a lot of reading including going through item by item in the xda wiki glossary but I'm still a little confused/want clarification before I actually do anything with my phone.
My goals are:
1) To create a full .img backup of my current system so I can always go back to it if needed/worst case scenario
2) Create a list of all my installed apps. Backup a few select apps that contain data within them that does not get backed up in the cloud or appear in a copyable source anywhere when i browse the phone directories (an app called Pattrn specifically that stores favorited background images..)
3) wipe/clear the my current incarnation of kitkat and re-install it 'fresh' (possibly without the bloat?), then reload desired apps.
4) create a backup .img of this new instance.
-----------------
I'm generally pretty quick to learn technical content but I've honestly tried to fully grok the steps for the last two weeks and haven't gotten there/understand enough to be confident to do what I think I need to do.
can take this to PM if anyone has some patience to work with me. Gladly donate to any app you make or paypal a few bucks if you can help walk me through this..
My understanding is that I need to get TWRP or CWM installed in order to get a custom recovery (as opposed to a stock recovery process)---which will allow me to do step 3. But even getting TWRP going I'm confused..
Thanks
Click to expand...
Click to collapse
Well, with TWRP, there is an option to back up your current system, data, and boot image.
So, let's say you make a backup your stock kitkat rom, you can wipe that, install a compatible rom. And if that fails or you do not like it, you can boot back into TWRP and restore the backup you made with the restore option.
I'm not too sure what you are asking about your apps, but with titanium backup, you can backup any app + their current data. For example, lets say you backup your favorite browser and it has everything just the way you want it, you can back it up with titanium backup, flash your rom, and restore it with titanium backup.
Not sure if that was what you were asking with #2, but if you have another question, ask away. I'm on a road trip so I have plenty of time.
Sent from my DROID RAZR M using XDA Premium 4 mobile app
crazy4android said:
can't help with everything..but with custom recovery..the easiest way is download flashify from play store and flash recovery image with itfrom here [link] you have a Razr M on kitkat use this one.. [link]
copy it to sdcard or internal storage...open flashify and select recovery image then choose the downloaded file..flash it and restart
Click to expand...
Click to collapse
thank you for your fast response, I appreciate it. I can do this--can you just clarify for me to define specifically what 'custom recovery' means?
I might be over-thinking it but I'm still trying to actually understand what custom recovery means-I assume it is in contrast to the current recovery which is still whatever shipped with the phone from verizon/motorola? So the above .img is a kitkat-base recovery (possibly without verizon bloat?)
Thanks
poppers162 said:
Well, with TWRP, there is an option to back up your current system, data, and boot image.
So, let's say you make a backup your stock kitkat rom, you can wipe that, install a compatible rom. And if that fails or you do not like it, you can boot back into TWRP and restore the backup you made with the restore option.
I'm not too sure what you are asking about your apps, but with titanium backup, you can backup any app + their current data. For example, lets say you backup your favorite browser and it has everything just the way you want it, you can back it up with titanium backup, flash your rom, and restore it with titanium backup.
Not sure if that was what you were asking with #2, but if you have another question, ask away. I'm on a road trip so I have plenty of time.
Sent from my DROID RAZR M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you too for your response!
So yes, I would like to use TWRP for that--make a backup of my current stock rom in all aspects, then start with a fresh instance. Does doing the step the above poster linked basically get TWRP installed as a custom recovery---which then gives me the options to create those backups in the bootloader menu? again sorry for my confusion, I've read the guides and how-to but I'm getting tripped up on some of the lingo/definitions.
On #2 Yes, that is basically what I wanted--I've got titanium backup installed and have backed up a few of these programs to my SD card already. Only have a handful of programs that have any customization that I care to retain.
water- said:
thank you for your fast response, I appreciate it. I can do this--can you just clarify for me to define specifically what 'custom recovery' means?
I might be over-thinking it but I'm still trying to actually understand what custom recovery means-I assume it is in contrast to the current recovery which is still whatever shipped with the phone from verizon/motorola? So the above .img is a kitkat-base recovery (possibly without verizon bloat?)
Thanks
Click to expand...
Click to collapse
you can do diff things like poppers162 mentioned you can backup ur entire rom with it...its very easy to flash nd very user friendly to navigate..no the above is a recovery img...you can boot ur phone into it once you flash it..then from there you can backup ur stock rom..and install/flash custom roms with bloat removed..
or another option is just freeze the apps you don't want with titanium backup..its almost as effective as uninstalling
Okay.. I've got TWRP going and creating a backup of my current system onto an external SD card. .. progress.
I've already backed up everything I desired in titanium.
Next up doing a 'clean' start in kitkat--or a slightly improved version. I realize at this point maybe things become more subjective to people's preferences.. I'm not looking to go to CM. I found some stock or a very-nearly-stock version of kitkat I can now 'start' fresh with--the google play edition? or do I need to download "Android 4.4.2 Blur_Version.183.46.10.XT907.Verizon.en.US"? I guess I need some more help at this point. Verizon is my carrier..
Thanks--do appreciate the help! :good:
water- said:
Okay.. I've got TWRP going and creating a backup of my current system onto an external SD card. .. progress.
I've already backed up everything I desired in titanium.
Next up doing a 'clean' start in kitkat--or a slightly improved version. I realize at this point maybe things become more subjective to people's preferences.. I'm not looking to go to CM. I found some stock or a very-nearly-stock version of kitkat I can now 'start' fresh with--the google play edition? or do I need to download "Android 4.4.2 Blur_Version.183.46.10.XT907.Verizon.en.US"? I guess I need some more help at this point. Verizon is my carrier..
Thanks--do appreciate the help! :good:
Click to expand...
Click to collapse
Android 4.4.2 Blur_Version.183.46.10.XT907.Verizon.en.US is complete stock with all the verison bloatware...as for the google play edition..i don't know if theres a flashable rom..the one in the Droid RAZR M Android Development is for fastboot i think..not sure and i myself havent looked into how to fastboot a fxz
water- said:
Okay.. I've got TWRP going and creating a backup of my current system onto an external SD card. .. progress.
I've already backed up everything I desired in titanium.
Next up doing a 'clean' start in kitkat--or a slightly improved version. I realize at this point maybe things become more subjective to people's preferences.. I'm not looking to go to CM. I found some stock or a very-nearly-stock version of kitkat I can now 'start' fresh with--the google play edition? or do I need to download "Android 4.4.2 Blur_Version.183.46.10.XT907.Verizon.en.US"? I guess I need some more help at this point. Verizon is my carrier..
Thanks--do appreciate the help! :good:
Click to expand...
Click to collapse
There's only a handful of roms compatible with the kitkat 3.4 kernel. I, personally, love cm11 test build. It's been going great. I would give it a try. If you don't like it, you have your backup!
Sent from my DROID RAZR M using XDA Premium 4 mobile app
Kitstalk ran pretty smoothly minus the speaker phone issues I like it but I've always been a fan of beanstalk... that was a few days ago when I flashed it so it may be fixed now I haven't checked on it...
Sent from my XT907 using xda app-developers app
success..95% or so
wanted to follow up here.. some of the terms finally clicked in my mind to understand the functions of recovery/fastboot/bootloader/flashing..etc. I wonder if there is a flow-chart type diagram available out there--that type of thing would have really helped to understand--being able to visualize where these different aspects interact and where files etc line up with them.
Short version: successfully running GPE rom smoothly and enjoyably on a 'clean' system.
needless to say I used TWRP to backup my system. And Titanium for specific apps. Used rsdlite to flash the GPE rom from the forum here. Then I factor reset the rom, then I think I formatted internal storage space?? --at that juncture I was a little less clear what the specific sequence should have been to 'start fresh'. Should I have factory reset my device before flashing the rom? Or maybe it really doesn't matter.
Thanks for everyone's help. One thing that didn't migrate over through gcloud backups--embedded images in text msging program. relatively small loss though
cheers
This is the first time I've ever rooted an Android device. The process has been fraught with uncertainty and misinformation from around the internet. I'd like to describe what I have come to understand is the current preferred method, and ask a few questions to hopefully get my S5 where I want it to be.
I don't want to do anything to crazy (yet, anyway). I just want to remove some bloat and get the notification panel as close to vanilla Android as possible.
So far, I have ran towelroot, which was incredibly simple.
I installed SuperSU from the Play Store. During installation, it got stuck at "Disabling KNOX...". I have since learned that this is common and a reboot usually fixes it. However, I have also learned that I probably don't want to disable KNOX yet anyway, since I am not going to flash a custom ROM until there is one that is known to be stable and is able to create the vanilla Android experience that I want. Some people said that I should have installed SuperSU from chainfire's page instead of the Play Store, but I think that was old information.
Edit: I'm editing these steps as I go along:
1. Install busybox and the Safestrap APK
2. Use Safestrap to set up a new ROM slot and use that slot from now on (consider the italics a strikethrough)
^Even though the instruction video on the Safestrap page said this, apparently that's not what most people do. They use Safestrap to make a nandroid backup, and then use only one slot, the stock ROM slot, to experiment or flash a new ROM.
3. Install Titanium Backup
Edit: I also had to install SD KitKat Fixer and then reboot afterward to allow TB to write to the SD card...
4. Use Titanium Backup to backup all apps and data to SD card
5. Use Titanium to freeze processes that I carefully choose
Edit: I froze everything from the list here.
6. Install Xposed framework
7. Find the modules to customize Android how I want
Does that sound right? Any tips/advice?
ergalthema said:
So far, I have ran towelroot, which was incredibly simple.
Click to expand...
Click to collapse
By doing this, you are rooted.
Even if you are not going to flash a custom rom, you can and probably should disable KNOX. Doing so will not trip the counter.
Install busybox and the Safestrap APK - This is indeed necessary if you want to install another ROM to customize. The whole point of safestrap is to flash ROMs and is not related to rooting itself. The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state.
Use Safestrap to set up a new ROM slot and use that slot from now on - This is fine if you want to switch between ROMs. I know some people like to do this, but I am not one of them.
Install Titanium Backup - absolutely
Use Titanium to freeze processes that I carefully choose - correct and there are threads with lists of APKs to freeze. You will also want to make sure you freeze SDM so that it doesn't prompt for security updates.
Use Titanium as a backup? (not sure about this) - this is to backup your apps, texts, things like that but NOT your ROM
Install Xposed framework
Find the modules to customize Android how I want
jcollier said:
Install busybox and the Safestrap APK - This is indeed necessary if you want to install another ROM to customize. The whole point of safestrap is to flash ROMs and is not related to rooting itself. The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state.
Use Safestrap to set up a new ROM slot and use that slot from now on - This is fine if you want to switch between ROMs. I know some people like to do this, but I am not one of them.
Click to expand...
Click to collapse
The first step in installing Xposed in this thread is to do a nandroid backup. I'm not totally sure what that is, but someone in another thread said implied that Safestrap essentially does the same thing. That is why I was planning to use Safestrap.
ergalthema said:
The first step in installing Xposed in this thread is to do a nandroid backup. I'm not totally sure what that is, but someone in another thread said implied that Safestrap essentially does the same thing. That is why I was planning to use Safestrap.
Click to expand...
Click to collapse
That is what I meant by this: "The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state."
A nandroid is a backup image of your system so that you can restore it if you screw something up. Safestrap isn't "essentially" doing the same thing, it is doing exactly that thing. Safestrap is a way to make a custom recovery work on our phone without an unlocked bootloader.
Good advice up to here, but you might want to hold off on using Exposed. As I understand it, Exposed lets you tinker with the existing stock ROM. I don't think I would want to do that, and I have rooted and ROM flashed several Android devices over the years. But its up to you.
With your being new to rooting, I'll offer this advice:
Titanium Backup (a.k.a. "TIBU") is a good way to back up all your apps. Here are some suggestions in using it:
--Buy the PRO version. It has more features, is not very expensive, and helps support a really cool app that is very handy.
--Set the Preferences/Backup folder to your REAL external SD Card. It will default to internal storage (also called "sd card"....don't get me started lol) which is IMO totally useless. If you lose internal storage due to corruption or whatever, you would lose all your backups. Having them on the REAL SD card you can also archive them to your PC.
--Set your Max Backup History to some number larger than the default "1". I use 7. Why? Well, have you ever seen the developer of one of your favorite apps suddenly screw it completely up in some update? Or, worse yet, sell out to some other vendor who now made it a PAY SUBSCRIPTION app?? I have. By keeping multiple backups you can roll back in time to previous versions that you know WORKED when those things happen. I have several apps I will never update, especially on the Store, for various reasons. (TIBU used to be able to disconnect the link to the Store so apps didn't try to update, but Google broke their ability to do that).
--When you do make TIBU backups, select "app and system data" which is IMO incorrectly worded and causes confusion. It should read "app and APP data". Because that is what it really does. Backs up the data IN your system that is associated ONLY with the APP. NOT any "system files". When you restore a backup, restore "app and system data" and you not only get the app installed, you get all your data it created, as well as all your customized settings restored! It is a real time saver. And you can "usually" even do this with a new device, using the TIBU backup folder on an SD card you had in some previous Android device. I've done it many times.
Safestrap installs a custom version of TWRP recovery. From that you can make the aforementioned "nandroid" backups of your complete system. (You won't see the word "nandroid" in TWRP while you are doing this. It just calls them backups). Couple of caveats with TWRP (and the Safestrap version):
--The date/time stamp used in both TWRP and its alternative, Clockworkmod Recovery (CW) will always be wrong. I've read (in short) there is no way for them to fix it. BUT........you most certainly CAN edit the backup file name to be whatever you like while setting it up to make the backup. So I recommend deleting the portion of the name that is the screwed up date it will generate, and putting in a date you can read, like my preferred format of 2014-07-10-1727 which is today at 5:27 PM, or whatever format you like.
--By default, TWRP recovery uses (in the Advanced settings) an inane "power saving" feature of the display, which will maddeningly keep turning it off and making you think the phone died while it is in the middle of making your backup. A - ALWAYS keep your phone on the charger when working in Recovery!! Don't even start unless it has at least 40% charge. B- Turn OFF the inane "power saving feature" and get some peace of mind. The screen will stay lit forever, until you reboot system when you are done.
--By default, TWRP will be set to use INTERNAL STORAGE as the place to keep your nandroids. Again, I consider that a very bad idea. Use a REAL External SD card and keep them there. And make regular backups to your PC of the SD card. I've seen a great many SD cards suddenly fail without warning. Your device will pop up and tell you the SD card is corrupt, and you need to format it. Usually, there is no way to recover the lost data on the card when that happens.
--On my Galaxy S5, making a nandroid of the stock OS via Safestrap took up over 4GB! That is almost 4 x what I normally see making a nandroid of a custom ROM on some previous device. So make sure you have plenty of room on whatever SD card you choose to use.
jcollier said:
Even if you are not going to flash a custom rom, you can and probably should disable KNOX. Doing so will not trip the counter.
Click to expand...
Click to collapse
I didn't know it wouldn't trip the counter. I'm curious why I should disable it though.
I followed the video exactly and when I get to the point of the first Restore (around 9:00), it says "Restore Complete - Failed". There is a button to Reboot System. When I tap that, the phone won't turn on. I have to pull the batter to get it back on. I guess I'll be uninstalling Safestrap. If I "Uninstall Recovery" from the stock ROM slot, will the space be freed up again and the phone be returned to the same state as before I tried using Safestrap?
ergalthema said:
I followed the video exactly and when I get to the point of the first Restore (around 9:00), it says "Restore Complete - Failed". There is a button to Reboot System. When I tap that, the phone won't turn on. I have to pull the batter to get it back on. I guess I'll be uninstalling Safestrap. If I "Uninstall Recovery" from the stock ROM slot, will the space be freed up again and the phone be returned to the same state as before I tried using Safestrap?
Click to expand...
Click to collapse
May I ask what it is that you are restoring? Have you already made a (nandroid) backup? That's what the restore function is made to restore. If you tried to use Restore on some other kind of file, then it would try to overwrite your ROM (OS) with it, and make the phone unusable. If that happens, I think your only fix would be to Odin back to stock and start over from scratch. I believe there is a link to do that in the thread telling how to root the S5.
Zoandroid said:
May I ask what it is that you are restoring? Have you already made a (nandroid) backup?
Click to expand...
Click to collapse
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.
ergalthema said:
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.
Click to expand...
Click to collapse
Oh, OK. Since there aren't any ROMs available yet, I did not pursue that aspect of Safestrap. So you have stepped outside my range of experience with it. Hopefully someone else can help you.
If you get to a point in your endeavors where you find a solution to apply ad-blocking to the S5, please let me know in a PM. I've had no luck so far. It appears this will be yet another issue that will only be solved with some creative developer work. Google has done something in KitKat to block not only apps like Ad-Aware and Adblock Plus from working, they also seem to have some kind of snooper utility that, if you try to search online with the S5 for ad blocking, will pop up a browser page saying Google "cannot access" the page! Pages which my PCs can see easily. Crafty little PITAs for sure! I thought it might just be Chrome doing this, so when I tried to get Firefox from the Store, I was stuck in an endless downloading loop. I had to kill that and restore a copy from TIBU. They are doing everything they can think of to lock down a smartphone and spoon feed us only what THEY want us to see. Including copious advertisements.
There was a time when Android meant "freedom". I guess that time has passed. Now it is time for someone else with very deep pockets to re-kindle a hassle-free smartphone OS. It is a shame. Android has so much potential.
ergalthema said:
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.
Click to expand...
Click to collapse
Why flash the stock ROM in a newly created ROM slot? You should only create a ROM slot if you decide to run a custom ROM. If not, you can use safestrap to create the backup (nandroid) and save it to your SD card so you always have a "safe" restore point essentially. I run a custom ROM in my stock slot. And for the record... There are several ROMs in the development section which are quite stable. Also, you can check out the Safestrap thread there as well. If you read through the thread you'll have a better understanding of how it works and what bugs there are right now.
The thing that I find great about XDA is that folks will always try to help each other out. Good luck!
Sent from my SM-G900V using XDA Premium 4 mobile app
Do we have a thread where folks are reporting having tried various versions of the available ROMs for the Verizon S5, and can make a simple statement about what works and what doesn't? I think that would be a really good idea. Without something like that, the only way to really know which ones are trouble free is to slog through and read each and every post on every ROM thread, most of which will usually be outdated information anyway.
Maybe it could be done as a Poll so it doesn't grow into something just as long to read as the above.
Zoandroid said:
Do we have a thread where folks are reporting having tried various versions of the available ROMs for the Verizon S5, and can make a simple statement about what works and what doesn't? I think that would be a really good idea. Without something like that, the only way to really know which ones are trouble free is to slog through and read each and every post on every ROM thread, most of which will usually be outdated information anyway.
Maybe it could be done as a Poll so it doesn't grow into something just as long to read as the above.
Click to expand...
Click to collapse
That would be great - especially for the people who aren't on this site all day and don't know what is good and current.
shoresteve626 said:
Why flash the stock ROM in a newly created ROM slot? You should only create a ROM slot if you decide to run a custom ROM. If not, you can use safestrap to create the backup (nandroid) and save it to your SD card so you always have a "safe" restore point essentially. I run a custom ROM in my stock slot. And for the record... There are several ROMs in the development section which are quite stable.
Click to expand...
Click to collapse
I'm realizing that's probably what most people do. In the instructional video posted on the main Safestrap OP, it instructed to keep the original stock slot intact, and use a new slot for experimenting with another ROM. I would love to know a stable ROM that gives the most vanilla Android.