Database Develop

Question about Bootstrapper and Clockwork Mod

I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.

Lyxdeslic said:
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Click to expand...
Click to collapse
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App

erismaster said:
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?

I think he's saying to not use rom manager at all. You can flash roms from cwm recovery.
Edit: just to clarify I mean by booting into recovery using the bootstrapper and flashing a rom from there to avoid any issues caused from the rom manager
Sent from my rooted xt860

Lyxdeslic said:
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
Click to expand...
Click to collapse
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App

erismaster said:
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.

Lyxdeslic said:
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Click to expand...
Click to collapse
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App

erismaster said:
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info man.

just rooted

using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1323946
i would like to install that faster rom everyone os raving about because my phone is dog slow. what rom comes with this method that i just did? can i install that gingervolt rom using this root or do i have to re-root using another method?

onlyoneromeo said:
using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1323946
i would like to install that faster rom everyone os raving about because my phone is dog slow. what rom comes with this method that i just did? can i install that gingervolt rom using this root or do i have to re-root using another method?
Click to expand...
Click to collapse
root is root. as long as you have root and CWM you can flash Gingervolt no problem.

onlyoneromeo said:
using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1323946
i would like to install that faster rom everyone os raving about because my phone is dog slow. what rom comes with this method that i just did? can i install that gingervolt rom using this root or do i have to re-root using another method?
Click to expand...
Click to collapse
If that is the root method you used, you do not have cwm recovery yet. You either need to run the newest version i posted earlier (yes it is ok to run the root.bat even if you already have root!), use RevoToolkit, or install manually. Then you can install the rom.

Ok I'm going to go do that now . I'm going to use the revotoolkit. So basically what that tool kit does is allow you to install custom roms? I hope that ginger volt can speed my phones processes up. I really don't want to ask for another htc device and my only two choices to swap for was the charge and this phone. Ugh I'm so frustrated...

ok so used revtoolkit and installed it and then downloaded the gingervlt zip file to my sd card. i rebooted the phone while pressing the power and vol down key an it came up w a screen asking if i wanted to erase everything. i watched a youtube vid that said to proceed with that and nothing would be erased and it did erase everything. how do i get into that screen to exract that zip file?

onlyoneromeo said:
ok so used revtoolkit and installed it and then downloaded the gingervlt zip file to my sd card. i rebooted the phone while pressing the power and vol down key an it came up w a screen asking if i wanted to erase everything. i watched a youtube vid that said to proceed with that and nothing would be erased and it did erase everything. how do i get into that screen to exract that zip file?
Click to expand...
Click to collapse
The root method you used is out dated and does not remove the files to make clockwork stick. Reuse revotoolkit to reinstall cwm, after confirmed to have worked, while still in revotoolkit press menu and hit reboot recovery.
Sent from my VS910 4G using xda premium

ok i reinstalled the cwm and when i click on the reboot option the screen on the phone is on but blank. am i missing something?

so if i use the all in one package root and unroot method you posted in the other board i should be able to install the rom i want without all the problems im having now?

onlyoneromeo said:
so if i use the all in one package root and unroot method you posted in the other board i should be able to install the rom i want without all the problems im having now?
Click to expand...
Click to collapse
Yep
Sent from my VS910 4G using xda premium

[Solved] SuperSU binary not updating, temporarily losing root

I've seen one or two threads that were in the same vein as this, but no clear resolution. Every time I open SuperSU, I get the message, "The SU binary needs to be updated. Continue?" I select "Continue," and am given the message to install it normally or through TWRP/CWM. If I try through TWRP, the phone restarts into TWRP, but does nothing. If I select "Normal," I get the "Installation failed!" message. I tried uninstalling/reinstalling SuperSU, but that didn't do anything.
In a related problem, I only have root access pretty much immediately after I reboot. Only immediately after I restart the phone can I use apps like WiFi Tether or Titanium.
I'm on stock, rooted 4.1.2. Any help would be great, thanks!

http://d-h.st/0du
Go into twrp and reflash supersu.
Sent from my HTC One using xda premium

eyeisdasteve said:
http://d-h.st/0du
Go into twrp and reflash supersu.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks for responding! Just to clarify, should I follow that readme file’s instructions, even though I’m already rooted and have TWRP? If simply choose “install” in TWRP and select this zip, will I have the option to just install SuperSU, or should I extract one of the following 3 zips in that file first?
SuperSU-v1.41.zip
superuser.zip
Superuser-3.2-RC3-arm-signed.zip
I assume this won’t wipe my phone, but of course, I’ll do a nandroid backup first. 

Well, I went into TWRP, went to "install," and selected the whole .zip, but it didn't look like it was going to give me the option to flash just SuperSU.
Agh... I should do this stuff more often so I'm not so clueless each time I need to do stuff in recovery...

SOLVED!
I figured I just needed one of those SuperSU zips found in the file linked above, but first, I decided to first see if there was a more up-to-date version. I wound up downloading the updated version from here: http://forum.xda-developers.com/showthread.php?t=1538053
After flashing "UPDATE-SuperSU-v1.41.zip" in TWRP, my root access is much more robust (i.e., not losing root after one app successfully requests access) and I am no longer being prompted to update my binaries!
Thanks again!

SuperSU
subhumanderelict said:
SOLVED!
I figured I just needed one of those SuperSU zips found in the file linked above, but first, I decided to first see if there was a more up-to-date version. I wound up downloading the updated version from here: http://forum.xda-developers.com/showthread.php?t=1538053
After flashing "UPDATE-SuperSU-v1.41.zip" in TWRP, my root access is much more robust (i.e., not losing root after one app successfully requests access) and I am no longer being prompted to update my binaries!
Thanks again!
Click to expand...
Click to collapse
Glad U got it working. I on the other hand am hosed. I wish the thing worked like everything else. I consider this to be a near
fatal weakness with the product. I at this point won't update until I get a clear understanding of what the heck is up with it.
Also Kyocera does not seem to be well supported. I got a Kyocera Hydro from a family member who was going to throw it
away. Guess I should have let him

rwilcher said:
Glad U got it working. I on the other hand am hosed. I wish the thing worked like everything else. I consider this to be a near
fatal weakness with the product. I at this point won't update until I get a clear understanding of what the heck is up with it.
Also Kyocera does not seem to be well supported. I got a Kyocera Hydro from a family member who was going to throw it
away. Guess I should have let him
Click to expand...
Click to collapse
So er.. what's your problem exactly? I could try to help you out.

not updating
Hi, I'm here about SuperSU not updating, but I have a normal rom, not TWRP or thecother one. Every time I go on SuperSU, it tells me there's an update. I click continue, then Normal, because that's the rom I have, but then it says the update failed. What do I do? Please help!

limehedd21 said:
Hi, I'm here about SuperSU not updating, but I have a normal rom, not TWRP or thecother one. Every time I go on SuperSU, it tells me there's an update. I click continue, then Normal, because that's the rom I have, but then it says the update failed. What do I do? Please help!
Click to expand...
Click to collapse
TWRP is a recovery not a ROM. If Normal doesn't work, select the other one. Assuming you have a custom recovery (I recommend TWRP for this phone), it should restart into recovery and flash the update there.

Hello, im new here and if you can please answer me on German
My problem is when i start to update SuperSU Binary it is failing on Normal mode and TWRP is happening nothing.
When i rooted first everything was glad, but there was no button to update the Binary and when i used apps like Xmodgames it says, my root is maybe no succesfull, so i rooted again without deinstalling the SuperSU blabla. And now is nothing working, if i go in Root Checker it cant find my root. Pls Help, sry for bad Grammar etc.

still have the problem
I did the flashing of the latest su update zip on my recovery reboit and ny supersu still prompts me to update binary just like before...HELP!!

my samsung galaxy s duos 2 is not updating binary in any modes
what should i do please help me

Is there any other way to update the binary other than through TWRP or CWM. I can't for the life of me find a CWM or TWRP recovery for my Hannspree Titan.

Hey guys, I have a problem here...
I had rooted my tablet and installed SuperSU, I choose the normal mode for binary update but it said it failed. Then I tried in TWRP/CWM but it just restarted my tablet and there it stayed.
When I power it on, it just keeps restarting every 5-7 seconds and it doesn't do anything else.
What should I do?

How to root I9305 DBT updated with OTA 4.4.4

Hello everyone. There are such topics after each official update for this device and many more.
I tried towelroot (with the secret code also) and Framaroot. No one succeeded. I couldn't root 4.3 with CF-Auto-root, so i didn't try this one. Anyone can help? Thanks!
Regards!

elektronchika said:
Hello everyone. There are such topics after each official update for this device and many more.
I tried towelroot (with the secret code also) and Framaroot. No one succeeded. I couldn't root 4.3 with CF-Auto-root, so i didn't try this one. Anyone can help? Thanks!
Regards!
Click to expand...
Click to collapse
install costum recovery via odin and flash supersu in costum recovery, thats it

9134
klemen241 said:
install costum recovery via odin and flash supersu in costum recovery, thats it
Click to expand...
Click to collapse
This is CF-auto-root, which as I said didn't work with 4.3

elektronchika said:
This is CF-auto-root, which as I said didn't work with 4.3
Click to expand...
Click to collapse
i did that after updating to 4.4.4. N version and it worked. Idk what can you do more

klemen241 said:
i did that after updating to 4.4.4. N version and it worked. Idk what can you do more
Click to expand...
Click to collapse
Hi, so if I understood well, the only thing I have to do to get rooted my S3 with 4.4.4 is to flash the CF-autoroot via Odin, isn't it? Then how can I install a new Superuser.apk if it brings me a force close trying to open the one already installed caused because of Knox?
Has anyone tried that method already? Does it actually work?

this works, but you have to untick "reset" in Odin and after flashing the recovery disconnect it, pull the battery, put it back and start the recovery manually, then flash supersu .zip and the other one that prevents the original recovery to be written back
If you let the phone reboot after flashing custom recovery, it will overwrite the custom one with stock one - tried that earlier today
---
sorry, misunderstand, if you update supersu just open knox and close after it shows you options to lock screen - then the supersu handles knox blocking properly
---
edit2: I tried with supersu by chainfire, didn't test with other party superuser.apk

adamuadamu said:
this works, but you have to untick "reset" in Odin and after flashing the recovery disconnect it, pull the battery, put it back and start the recovery manually, then flash supersu .zip and the other one that prevents the original recovery to be written back
Click to expand...
Click to collapse
This also doesn't work...

Try also Koush's Superuser.
Sent from my GT-I9305 using XDA Free mobile app

elektronchika said:
This also doesn't work...
Click to expand...
Click to collapse
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done

Thank you adamuadamu !!!
It works!
Regards Sonic76

adamuadamu said:
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Click to expand...
Click to collapse
you mentioned recovery disabler from CF root, can you point me where exactly do I find that file? Cheers!

sham79 said:
you mentioned recovery disabler from CF root, can you point me where exactly do I find that file? Cheers!
Click to expand...
Click to collapse
first attachment in the OP
direct link: http://forum.xda-developers.com/attachment.php?attachmentid=1680841&d=1359295479

Thanks for the explanation adamuadamu,
However, just to be sure, apart from the recovery disabler file, the other CF-Root file that I need to flash is the "update supersu2.02.zip"? I've read a lot of posts explaining the same procedure but no link to the actual files that need to be flashed, and sometimes the reference is to generic names like CF-root and when you search for it there is a lot of different files, etc.. I'm a newbie, so sometimes I don't know if any version of Philz will work or if it's better to use just plain CWM, if CF-auto-root is the way to go or just the old CF-Root (last version for i9305 says is for 4.1.1).
Thanks in advance for the reply and explanation.
Cheers,
Da Fig

Do you have to flash the custom recovery first and then SuperU? Is it possible to just flash SuperU and then using Triangle Away in order to root 4.4.4?
I want root but want to stay as stock as possible.

Da Fig said:
However, just to be sure, apart from the recovery disabler file, the other CF-Root file that I need to flash is the "update supersu2.02.zip"? I've read a lot of posts explaining the same procedure but no link to the actual files that need to be flashed, and sometimes the reference is to generic names like CF-root and when you search for it there is a lot of different files, etc.. I'm a newbie, so sometimes I don't know if any version of Philz will work or if it's better to use just plain CWM, if CF-auto-root is the way to go or just the old CF-Root (last version for i9305 says is for 4.1.1).
Click to expand...
Click to collapse
I remember using some older SuperSu (1.9xx) as the files were already on my SD Card
In case you need proper and updated files and you're a bit afraid of confusing them - google for skipsoft toolkit, choose your device, wait for the program to download appropriate files and then in order to get the files you need, you'd have to (all from my memory, in case you'd need more detailed info, let me know and I can check within couple of hours, as I'm not in front of my private PC now)
1. go to root options and use option to push supersu and recovery disabler to your card
2. let the program reboot your phone into download mode
3. contrary to the advice onscreen, use odin, but untick "Auto Reboot", flash your recovery (the program will show you the path to newest recoveries it downloaded upon first run)
4. wait for the recovery being flashed, disconnect the phone, pull the battery. DON'T CLOSE ODIN yet, you may need it if you fail to boot into recovery directly!
5. start the phone using 3-key combo into recovery. if you fail, you'll need to go back to step 2.
6. flash both files copied in step 1.
7. reboot into system
personally I stick with PhilZ touch, as it always checks for root when leaving recovery and offers to repair it
8. go to play store and download or update supersu by chainfire (whatever applies to you)
9. run SuperSU, agree to disable KNOX

Thanks for the reply adamuadamu, I'll try this and see. Apparently most supersu or the correspondent CF-auto-root will do the trick. I'll try your method first, otherwise I'll start playing with different files.
Cheers.

KennyMRos said:
Hi, so if I understood well, the only thing I have to do to get rooted my S3 with 4.4.4 is to flash the CF-autoroot via Odin, isn't it? Then how can I install a new Superuser.apk if it brings me a force close trying to open the one already installed caused because of Knox?
Has anyone tried that method already? Does it actually work?
Click to expand...
Click to collapse
SuperSU version 2.01 has the forced close problem on 4.4.4.
Download the SuperSU version 2.02 in following thread and install it. It will ask to disable KNOX. select YES.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
:good:

isn't there a way to instal just SU with towelroot installing an old samsung kernel without tripping knox like in this thread?
http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150

adamuadamu said:
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Click to expand...
Click to collapse
I installed Philz Touch Recovery and fix it all.

is there any way(apk) to root 4.1 under the system(touchwiz)?

I can't enter to the cwm, because my power on button is dont work.
i know an application what can restart in cwm but this application need to root
so i must root 4.1 under 4.1 system(under touchwiz)
is there any solution?
or is there any solution to root 4.1 under ODIN?

Probably by using Towelroot
google it, first site that comes up.
Click the labda and download the app. open it and click make it rain.
afterwards your phone should restart and you should be rooted. Then you van download Superuser from the playstore.
Sent from my Ghost

Ghost_Developer said:
Probably by using Towelroot
google it, first site that comes up.
Click the labda and download the app. open it and click make it rain.
afterwards your phone should restart and you should be rooted. Then you van download Superuser from the playstore.
Sent from my Ghost
Click to expand...
Click to collapse
after root is there any way to instal new cwm from menu?(touchwiz)
or install one file rom?

astron1985 said:
after root is there any way to instal new cwm from menu?(touchwiz)
or install one file rom?
Click to expand...
Click to collapse
This should probably be done using Odin on the PC. There are multiple tutorials on how to do this for your phone specifically, so I will not go in to much detail yet, but basically the way it works is that you flash a recovery using Odin and use the app on your phone to restart in the recovery.
The broken start button does make everything a bit more complicated, but it definately is possible.
Never forget, Google is your friend (And me to ofcource)
Sent from my Ghost