Database Users

[TUTORIAL]ClockworkMod Recovery Easy Install

Since people are obviously having trouble installing CWM, I thought I'd make this topic since the other one doesn't seem that it will be updated anytime soon. This does require root.
Step 1: Rooting your phone-Follow the link that's labeled "Superoneclick Root." Download the file and follow instructions. Works on ALL Vibrant Froyo (KA6/KB5) and Eclair. Reboot.
Step 2: Flashing CWM-Download ROM Manager from the market. Open the app, and choose the very first option. It should say "FLash ClockworkMod Recovery." Choose vibrant.
Step 3: Getting into CWM
a. Use the link below that's labeled "Modified 3e REcovery." DOwnload file and follow directions. IF it succeeds, reboot into recovery via 3 button combo and hit rreinstall packages. The phone should reboot into recovery. Hit reinstall packages again and voila.
**Note** this did not work for me.
-OR-
**PRE-POST NOTE** Odin will WIPE ALL APPS AND DATA. Use Titanium Backup from the market to backup apps.
b. If the 3e fix didn't work for you, I suggest using Odin to flash back to stock. Follow either links labeled "Odin Back to Stock" for detailed, step-by-step guides on how to flash back to stock. If it succeeds, reboot to recovery, and you should see "2e recovery" instead of 3e. Hit reinstall packages. It will reboot back into recovery, hit reinstall packages again and voila.
-OR-
c. If those don't work, you can try downloading and flashing a voodoo integrated kernel to access the "red" clockwork recovery via ODIN or SGS Kernel Flasher. I recommend you flash a "stock + voodoo" kernel first however, and then flash your kernel of choice (Overstock, Bali, w/e). MAKE SURE IT'S COMPATIBLE. Follow link down below for stock kernels + voodoo. Find the flasher at the market. This will patch your system with ext4 and is a pretty nice addition. Now, this might take a long time, depending on the amount of apps that you have. You might and probably will hear "linda" which is just a voice that tells you what's happening.
**Note** I have tried SGS kernel flasher multiple times and multiple times it has failed to flash properly---soft brick--boot loop. I'm not saying that you will too, I'm just stating my experiences.
**Disclaimer** I am not responsible for bricked and/or damaged phones, you did it, it was your choice. Although the chance of a hard brick is pretty low.
I do recommend looking at s15274n's guides below if you intend on flashing ROMs. If you don't intend to, might I recommend that you add that to your to do list as well? It might just be a worthwhile experience.
Modified 3e Recovery
http://forum.xda-developers.com/showthread.php?t=833423
Superoneclick Root
http://forum.xda-developers.com/showthread.php?t=803682
Odin Back to Stock + Flashing ROMs
http://forum.xda-developers.com/showthread.php?t=1047087
http://forum.xda-developers.com/showthread.php?t=849028
Stock + Voodoo All Except KB5
http://forum.xda-developers.com/showthread.php?t=870480
Stock + Voodoo KB5
http://forum.xda-developers.com/archive/index.php/t-1036725.html
Hope this helps. Feel free to help me 'perfect' these steps.

Appreciate the effort... I feel (obviously biased) my Noob Root Guide is a little more detailed.. and easier (again, bias), perhaps you want to link to that too in case people are questioning things.
I am NOT a fan of superoneclick OR the modified 3E (like you said it didnt wok for you), just my personal stance. Nice to have options for people though, so thanks!!

I'm running KB5 having Kies'd form the original 2.1 ->2.2 -> 2.2 (KB5). I've also tried the modified 3e recovery without signature check, and it failed to update to CWM for me too.
I'm very reluctant to ODIN to 2.1 stock without getting a real backup. Some questions:
1) Is there nothing I can run from the PC side that can pull a full image from the phone that could be restored if necessary?
2) If I go with the Titanium backup, what exactly will I lose, after ODIN (phone history, settings,..)?
3) If I do ODIN back to 2.1 and install CWM, can I Kies back to KB5 without losing CWM?

kmandel said:
I'm running KB5 having Kies'd form the original 2.1 ->2.2 -> 2.2 (KB5). I've also tried the modified 3e recovery without signature check, and it failed to update to CWM for me too.
I'm very reluctant to ODIN to 2.1 stock without getting a real backup. Some questions:
1) Is there nothing I can run from the PC side that can pull a full image from the phone that could be restored if necessary?
2) If I go with the Titanium backup, what exactly will I lose, after ODIN (phone history, settings,..)?
3) If I do ODIN back to 2.1 and install CWM, can I Kies back to KB5 without losing CWM?
Click to expand...
Click to collapse
1. As far as I know, no.
2. Everthing goes stock...out of the box stock. Import your contacts to your sim card or back it up with AVG or something. SD Card will not be wiped however
3. I believe so, yes.

updated OP!

[HOWTO] Update to 4.0.3 OTA ICS from any version with Root access (For I9020T/I9020A)

Okay First of all download the following files
a)http://android.clients.google.com/packages/ota/google_crespo/VQ8PQk_V.zip (4.0.3 OTA)
b)http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip (2.3.6 Official I9020T Build)
c)http://bit.ly/su2361ef (SU flashable)
d)http://forum.xda-developers.com/showthread.php?t=988686 (Grab recovery form this thread)
e)http://developer.android.com/sdk/index.html (Grab the android SDK installer)
f)http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429 (Radio file only required for I9020A)
Okay so when done with all that proceed as follows
1) Backup your current apps using Titanium Backup (Optional/Recommended)
2) Backup(Nandroid) your rom using backup option in CWM (Optional/Recommended)
3) Do a full wipe, wipe sdcard, system, data, cache Transfer a,b,c,f to your phone.
4) Flash the 2.3.6 Official I9020T Build you had downloaded using the install zip option in CWM (IMP-DO NOT REBOOT RIGHT NOW)
5) Flash the flashable SU file you had downloaded and then reboot.
6) Once your phone is on, continue to set up your account or skip it as you wish. (Optional)
7) Open up market, download the latest SU app, Voodoo OTARootKeeper, Titanium Backup and any other app you use that requires root.
8) Open the updated SU app, hit menu button and click preferences, go all the way down, click on su binary(tap to check for updates) , and make sure it updates to v3.0.3
9) After that is done, open and allow root permissions to all your root apps. (This is important)
9.5) Run Voodoo OTARootKeeper and click on protect root, make sure all options get checked.
10) Turn off phone, keep volume up and power pressed to boot into fastboot.
11) Select recovery with volume buttons and use power to launch.
12) Once you see a android bot image and an arrow image, keep volume up pressed and press power once, then you'll see some options appear.
13) Select apply update option and find the official 4.0.3 OTA file you had downloaded and flash. Reboot.
14) Once you have booted into ICS, go to Voodoo OTARootKeeper and select resture Root, all options should now be ticked, if not something went wrong.
15) Voila, you have root. Now to get back CWM recovery you can follow this -
i) Place the recovery img file in the android sdk platform-tools folder
ii) Switch to the directory where you unzipped the Android SDK & go to "tools"
iii) Then type "fastboot flash recovery yourfilename.img" & hit enter
iv) That should do it.
v) Optionally you may do it form Rom Manager too, if it works.
16) (ONLY FOR I9020A) Reboot phone, turn it off, boot into fastboot, select recovery, CWM should launch, flash the radio file you had downloaded to get radio working on I9020A (ONLY FOR I9020A)
Root only works for the apps that were installed while on 2.3.6
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip , use this root file, flash it in cwm, everything works, permissions etc.
This might work for other variants, tested on I9020A and I9020T, I take no responsibility for anything that might go wrong with your device. I take no credit for any links or procedures provided in this guide, I just tested and compiled.
Thanks and best of luck.

..........

Good guide but first two links are broken.

bajansurfer said:
Good guide but first two links are broken.
Click to expand...
Click to collapse
Thanks, fixed.

Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?

poging22 said:
Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?
Click to expand...
Click to collapse
Might not work, though you can try, if it fails, do it my way, also its impossible to get any kind of root that way.

Link for the ATT Radio doesnt seem to be working

Great work!
wipe SD card?
Is this necessary?

I don't think it's necessary to wipe the SD card, I followed the procedure in http://forum.xda-developers.com/showthread.php?t=1396913 and although it said my SD card would be wiped, everything was still there after I was done!

Anyone on a i9023 tried this?

Hmm...does "any version" includes M200(Korean Nexus S)?
Sent from my Nexus S using Tapatalk

http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429
I think he meant that for the 9020A radio

Link fixed, sorry for that, SD wiping might not be necessary, but I suggest as it makes it cleaner. Might work for I9023 and M200, I have no clue, maybe some experienced developer can answer that better.

Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.

Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?

little hiccup at step 12. im getting the android bot with exclamation mark but i press volume up with power and nothing happens. menu doesnt show up....
Edit: NVM... i pressed it 3 or 4 times and it finally worked

Michie23 said:
Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?
Click to expand...
Click to collapse
You should post it in questions, I cannot answer this.

fromthestars said:
Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.
Click to expand...
Click to collapse
Many ways of doing it, I just am suggesting one, the flashable zip for ics isn't available as yet, what did you flash?

i9020 keeps getting status 7 aborted and my padlock is still unlocked on t-mobile 2.3.6

Has any tried this on an i9023? Thank u
Sent from my Nexus S using xda premium

[Q] Getting latest CWM onto Droid X - help!!

This phone is about to cause me to start mainlining some serious drugs. I just do not understand what I'm doing wrong.
I have read and read and read and downloaded and downloaded and downloaded. At one point I think I had about 10 Firefox tabs open, madly switching between them trying to figure this beast out. So, I have tried to do the necessary homework before posting here.
I received a Verizon Droid X (MB810 model) and was wanting to install a 2nd-init ROM. It came with .621, which I know has been problematic in the past, but seems not to be a terribly big obstacle anymore. Here are the steps I've taken:
o I rooted the phone via the Slitaz ISO.
o Via adb, I pushed the Droid 2 (D2) reboot recovery and ROM manager (RM) APKs.
o I choose boostrap recovery in the D2 application. Superuser grants the appropriate permission.
o Within RM, I download and flash the latest CWM (5.0.2.0) based on the 2nd-init Droid X option.
o RM says that the flash is successful and Superuser rights are granted.
o From within RM, I choose the reboot into recovery option.
o The phone reboots...right back into the operating system, completely bypassing CWM. Redoing the above steps and holding down the home key just boots into the stock recovery.
Now, I can reboot into CWM from the D2 application, but I'm then confronted with the old version of CWM. I've also read where this method will screw-up the boot process to the point that installing 2nd-init ROMs won't work. I've (somewhat) verified this by trying to install the latest AOKP with the D2 version of CWM, which just endlessly loops the unicorn animation. In fact, in a thread detailing this problem on another forum, it was advised to stay far, far away from the D2 application altogether and just use RM.
I've also had to SBF back to .621 on several occasions using RSDLite 4.9.
This has been nightmarish. I spent almost the entire weekend trying to get this phone to boot into the latest CWM. Do I have to SBF the Milestone ROM in order for this to work? Is that even necessary anymore?
Any help would be GREATLY appreciated, as I'm out of ideas at this point. Thanks a bunch.
- Fred

did you wipe data before/after flashing SBF?
if not, that could cause issues

sd_shadow said:
did you wipe data before/after flashing SBF?
if not, that could cause issues
Click to expand...
Click to collapse
Yes, I forgot to mention I did that in my OP.
I just don't understand what's going on. It's almost as if RM is lying to me about having successfully flashed the newest CWM. I say this because, when I immediately do the flash procedure after booting the phone, nothing shows up in /preinstall/recovery/ using Root Explorer (RE). It's only after I do the D2 bootstrap recovery option that /preinstall/recovery/ is populated with the CWM files. The problem is that these files represent the 2.0.5.8 version, not the 5.0.2.0 update.
To even deepen the mystery, after I did the above, I then went back into RM and reflashed to the latest CWM. I then looked at /preinstall/recovery/ again and all of the original 2.0.5.8 files were still there. There was no evidence that I could determine that RM installed anything anywhere.
I'm at a total loss.

did you try deleting NFS Shift or Madden from the preinstall, then reflash CWM in RM?

sd_shadow said:
did you try deleting NFS Shift or Madden from the preinstall, then reflash CWM in RM?
Click to expand...
Click to collapse
I just did that. RE is showing 244MB free, which I'm assuming is more than enough for RM to do its thing. I then redid the steps I outlined above and /preinstall/recovery/ still isn't populating with the 5.0.2.0 update.
This is beyond bizarre. How can RM state that it successfully flashed to the latest CWM when it doesn't appear to do anything? If RM runs into an error in the file creation process, does it report that to the user or just acts as if everything is normal?

i don't think you will get an error
have you tried redownloading D2 bootstrap and rom manager, from market?
have you read this? http://rootzwiki.com/topic/31737-root-droid-x-root-method-for-234-45621-does-not-require-milestone-sbf/page__st__20#entry878745

Maybe this is a dumb question, but I'm not familiar with the Slitaz ISO.
So does that install a 2nd-init ROM? Or have you installed a 2nd-init ROM manually?
If you haven't, you shouldn't be selecting the 2nd-init recovery. Use the regular Droid X recovery, install the 2nd-init recovery only after flashing a 2nd-init ROM.

the link was to a post that
someone was having trouble updating cwm to 5.0, and some possible fixes
as for the Slitaz ISO, is just a linux program used to run the magic md5 root method

fleggett said:
I just did that. RE is showing 244MB free, which I'm assuming is more than enough for RM to do its thing. I then redid the steps I outlined above and /preinstall/recovery/ still isn't populating with the 5.0.2.0 update.
This is beyond bizarre. How can RM state that it successfully flashed to the latest CWM when it doesn't appear to do anything? If RM runs into an error in the file creation process, does it report that to the user or just acts as if everything is normal?
Click to expand...
Click to collapse
found a great work around, or Tomsgt123 shows how in one of his youtube videos
If updating to 5.0.0 with Rom Manager fails
using a file manager/root browser with root access go to
/preinstall/recovery select recovery.zip rename recovery.zip.bak
then go to sd card>clockworkmod>downloads>recoveries> copy the recovery.zip that has ‘shadow.zip’ in properties
go back to /preinstall/recovery and paste recovery.zip
as described in [VIDEO] How to update CWM Recovery on the Droid 2-by Tomsgt123

test test test

blindmanpb said:
Maybe this is a dumb question, but I'm not familiar with the Slitaz ISO.
So does that install a 2nd-init ROM? Or have you installed a 2nd-init ROM manually?
If you haven't, you shouldn't be selecting the 2nd-init recovery. Use the regular Droid X recovery, install the 2nd-init recovery only after flashing a 2nd-init ROM.
Click to expand...
Click to collapse
Slitaz ISO, is just a linux program used to run the magic md5 root method
no it does not install a rom
you only need to update cwm if you want to restore a nandroid backup of a 2nd init rom,
most 2nd init roms come with their own bootstrap, found in the reboot options
you shouldn't install bootstrap or update cwm unless the rom does not install bootstrap

Sorry for the previous "test test test". The forum wasn't letting me post anything until I realized I'm under the ten post threshold and I was trying to quote text that had links.
Thanks, sd_shadow, for the extremely helpful pointers. Unfortunately, I no longer have the phone in my possession, but I might be getting another one to play with soon. I'll let you know if I run into the same problems after applying your potential fixes. Thanks again!

I'm ecstatic to report that the this alternative method by Tomsgt123 worked! Here is what I wound-up doing, from start to 5.0.2.0 finish.
First the facts, all taken from settings -> About phone
System version: 4.5.621.MB810.Verizon.en.US
Model number: DROIDX
Android version: 2.3.4
Baseband version: BP_C_01.09.15P
Kernel version: 2.6.32.9-g1282440 ([email protected] #1)
Build number: 4.5.1_57_DX8-51
ERI version: 5
PRL version: 58012
Bootloader: 30.04
1. Obtain SliTaz GNU/Linux (3.0) root ISO in preparation to root phone. File I used is named Droid2_D2G_DX_DX2-RootCD-2012.iso.
2. Burn SliTaz ISO to bootable media.
3. Enter Windows and boot phone normally.
4. Ensure USB debugging is enabled via the settings -> Application settings -> Development -> USB debugging checkbox.
5. Connect phone to computer via USB cable.
6. Drag from top of phone and select the USB connection -> Charge Only radio button.
7. Boot computer via SliTaz.
8. Choose option 3 (Root Droid X) and follow onscreen directions to the letter, including putting phone in bootloader mode.
9. Boot phone normally and invoke Superuser. Immediately exit Superuser. (This step probably isn't necessary.)
10. Install Droid 2 Bootstrapper (D2B), ROM Manager (RM), and Root Explorer (RE) on phone (I used adb).
11. Invoke D2B and choose Bootstrap Recovery. When done, exit D2B.
12. Make sure phone is connected to internet.
13. Invoke RM and choose Flash ClockworkMod Recovery. Current Recovery should be 5.0.2.0.
14. Choose 3rd option, Motorola Droid X (2nd-init).
15. Tap Flash ClockworkMod Recovery. Wait until recovery files are downloaded and flashed, then exit RM.
16. Invoke RE and navigate to /preinstall/recovery.
17. Rename recovery.zip to recovery.zip.bak.
18. Still within RE, navigate to /sdcard/clockworkmod/download/download2.clockworkmod.com/recoveries.
19. Press and hold on recovery-clockwork-5.0.2.0-shadow.zip and copy the file.
20. Navigate back to /preinstall/recovery and paste the above file.
21. Rename the above pasted file to recovery.zip.
22. Exit out of RE and return to RM. Tap Reboot into Recovery and hit OK at the "Are you sure...?" prompt.
23. Phone should reboot into the 5.0.2.0 version of CWM.
Thanks again, sd_shadow. Without the above "manual" method, I would never have gotten the 5.0.2.0 version of CWM onto this phone. Now, time to play!
- Fred

And guess what? All those previous steps I carefully and deliberately outlined have been rendered obsolete by one, small apk:
http://rootzwiki.com/topic/25017-ro...workmod-flashable-updates-by-ky/page__st__190
(Still can't post links...yet.)
This is the Droid X Bootstrapper 621 MOD (DXB621). Functionally, it is the same as the old D2B except for two huge and critical features:
1. It contains CWM 5.0.2.0 out-of-the-box.
2. It works without having to do the aforementioned file manipulation inside RE.
Because of the above, it negates the need for RM (and D2B) entirely. I immediately installed DXB621 on my freshly SBF'd and rooted Droid X (see previous stats) and it worked flawlessly.
After all this, I'm convinced there is something wrong with RM as it relates to the Droid X with .621 already installed, whether via the OTA update or via SBF.
As a big bonus, after some finagling, I was also able to install HijackedBootMenu 1.1.5 621 1.1, which is a real gift, since it allows booting into CWM (or RZR) without having to first boot the phone to use either D2B, RM, or DXB621 itself.
So, the moral of this long and windy story is to simply use DXB621 for your recovery needs, don't mess with D2B and RM, and don't look back.
- Fred

nice find
I had seen that thread before, too bad the modified bootstrap isn't noted in first post, but page 20 of 110
I tried it on my D2 a955, and was able to to boot to cwm 5.0
so I will add it to my list.

sd_shadow said:
nice find
I had seen that thread before, too bad the modified bootstrap isn't noted in first post, but page 20 of 110
I tried it on my D2 a955, and was able to to boot to cwm 5.0
so I will add it to my list.
Click to expand...
Click to collapse
Yeah, getting any bootstrap to work on a Droid is the first step (after rooting) in doing much of anything, and using the most recent CWM seems to be required for all the latest and greatest ROMs, so it really should be somewhere on page 1 of that monster thread. I only stumbled across it via dumb luck.
I've run into a bizarre issue, though. With the phone connected to a running computer via USB, it won't boot into either CWM or RZR from Hijacked BootMenu (HB). Once you hit either recovery option, it just goes to a (slightly lit) black screen and stays there. The power button doesn't work at that point, so it requires a battery pull.
A clue as to what's going on might be that Windows recognizes the device when HB runs. It's only when I disconnect the cable before booting the phone that either recoveries invoke normally. Very strange.
I currently have CMKang.b3 loaded on the phone. I was pleasantly surprised to see that both the Camera and Torch apps work just fine, as I thought both were inoperable under CM9. This specific build is 9-20130120-UNOFFICIAL-shadow.
- Fred

sd_shadow said:
found a great work around, or Tomsgt123 shows how in one of his youtube videos
If updating to 5.0.0 with Rom Manager fails
using a file manager/root browser with root access go to
/preinstall/recovery select recovery.zip rename recovery.zip.bak
then go to sd card>clockworkmod>downloads>recoveries> copy the recovery.zip that has ‘shadow.zip’ in properties
go back to /preinstall/recovery and paste recovery.zip
as described in [VIDEO] How to update CWM Recovery on the Droid 2-by Tomsgt123
Click to expand...
Click to collapse
THANK YOU! I was having a similar problem as the OP, and this FINALLY fixed it!

also take a look at the modified d2 bootstrap that has been upgraded to cwm 5.0
will save a few steps if you have to reinstall
edit: I have rewritten my instructions here
[HOW TO] Install/Use Droid 2 Bootstrap

The modified Bootstrap is the trick. Straight to CWM 5.0. Took me a long time to figure out that ROM manager appears to update CWM but does not work. I found ROM manager to be of no use or value at all to me and don't install it or delete it.

Got 11 Open
Looking for an answer myself. Currently trying to install using Rom Manager then using button presses to get into Recovery. Will post update shortly.

[Q] trouble installing 4.2.2

I currently have "stock rom" and "franco kernel r72"...
i searched everywhere before getting 4.2.2 update and followed the instruction:
1. Download stock kernel from here:
http://forum.xda-developers.com/show....php?t=2024982
2. Flash it in recovery.
3. Boot into android.
4. Go from root explorer to system/lib/hw and*
i) Delete power.msm8960.so
ii) Remove .fkbak extension from power.msm8960.so.fkbak so it looks like, power.msm8960.so
iii) Fix the permissions to rw-r--r--
5. Reboot to recovery
flash the update from recovery and install the best kernel out there again.
Click to expand...
Click to collapse
but even after following all these instructions I continue to get error on "power.msm8960.so" file.
so I checked the file and the "power.msm8960.so.fkbak" turned out to be damaged by recent trial of Minco ROM...
(power.msm8960.so.fkbak's modified date turned out to be the same day I installed the minco rom)
simply saying: franco kernel backed up not the original but one that was edited by minco rom (correct me if im wrong)
now that Im back to stock rom but with a wrong backup file of power.msm8960.so, I'm stuck and need the original file...
can anyone (with a stock kernel) send me a original backup of "power.msm8960.so" located in "system/lib/hw" ???
so that I can replace my wrong backup.... thank youuuu

CF-Auto-ROOT, Odin success but phone appears to be unrooted.

Forewarning, I'm super novice at phones but am pretty good with computers (can program and such).
I recently tried to root my phone using CF-Auto-Root, I used odin and all appeared to be a success, I unplugged the phone from the pc and it went through a black screen white writing and a red android logo and did a few other things.
once rebooted there was an unusual blue screen and my phone came up with a message saying something wasn't recognised and I had to wipe all data and reset to factory.
once all this was done, my phone is showing as unrooted by SuperSU and Root Checker and I am now receiving a security notice about unauthorised actions.
I have since "installed"(please advise me of a better word) TWRP and used no-Verity-opt.... but when installing Magisk I get an Error 1
I am not sure where to go from here. Please help/advise or tell me my post is in the wrong spot.:good:

ElronVonSexbot said:
Forewarning, I'm super novice at phones but am pretty good with computers (can program and such).
I recently tried to root my phone using CF-Auto-Root, I used odin and all appeared to be a success, I unplugged the phone from the pc and it went through a black screen white writing and a red android logo and did a few other things.
once rebooted there was an unusual blue screen and my phone came up with a message saying something wasn't recognised and I had to wipe all data and reset to factory.
once all this was done, my phone is showing as unrooted by SuperSU and Root Checker.
I have since "installed"(please advise me of a better word) TWRP and used no-Verity-opt.... but when installing Magisk I get an Error 1
I am not sure where to go from here. Please help/advise or tell me my post is in the wrong spot.:good:
Click to expand...
Click to collapse
ONLY WORKS WHEN YOU HAVE TWRP INSTALLED (which you obviously have):
Either you download a recovery flashable SuperSu from here or a recovery flashable Magisk from here directly to your device.
Than you just boot to recovery(hold down volume up, bixby and power buttons while turned off) go to "Install" in TWRP and search for the file you just downloaded (usually /sdcard/Downloads/ or something) just wait till the flash process is done and reboot.

jaannnis said:
ONLY WORKS WHEN YOU HAVE TWRP INSTALLED (which you obviously have):
Either you download a recovery flashable SuperSu from here or a recovery flashable Magisk from here directly to your device.
Than you just boot to recovery(hold down volume up, bixby and power buttons while turned off) go to "Install" in TWRP and search for the file you just downloaded (usually /sdcard/Downloads/ or something) just wait till the flash process is done and reboot.
Click to expand...
Click to collapse
During the flash process using the flashable Magisk I get an error:
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v16.0.zip' "
This is where I'm stuck, I don't how how to solve this error.
it says above the error
! boot image patched by other programs ' Referring to CF-Auto-Root which didn't work
So I guess my question is how do I restore my stock boot image after using CF in order to flash Magisk instead.

ElronVonSexbot said:
During the flash process using the flashable Magisk I get an error:
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v16.0.zip' "
This is where I'm stuck, I don't how how to solve this error.
it says above the error
! boot image patched by other programs ' Referring to CF-Auto-Root which didn't work
So I guess my question is how do I restore my stock boot image after using CF in order to flash Magisk instead.
Click to expand...
Click to collapse
AFAIK you have two options now:
Flash stock TouchWiz (plenty of tutorials on the forum) and install twrp afterwards, then install Magisk via TWRP
Flash custom rom like Renovate ICE or any other from the forum directly via TWRP. I believe all of them are (at least have the option to) pre-rooted with either Magisk or SuperSu
As your SuperSu doesn't recognize your root you can't unroot with it and (someone please correct me if im wrong) not even a full wipe does unroot/does anything with boot.img

jaannnis said:
AFAIK you have two options now:
Flash stock TouchWiz (plenty of tutorials on the forum) and install twrp afterwards, then install Magisk via TWRP
Flash custom rom like Renovate ICE or any other from the forum directly via TWRP. I believe all of them are (at least have the option to) pre-rooted with either Magisk or SuperSu
As your SuperSu doesn't recognize your root you can't unroot with it and (someone please correct me if im wrong) not even a full wipe does unroot/does anything with boot.img
Click to expand...
Click to collapse
Thanks, I was going to custom ROM eventually anyway so I may as well bite the bullet, and Renovate ICE seems to be the best out there, thanks for the advice.
I think you are right, it was my thought that because I used CF-Auto-ROOT no backup of the original/stock Boot.img was ever created giving me no point of return. god knows what actually went wrong with the root. I shouldn't have been lazy and avoided the TWRP step in the first place.
Again, thanks for the help, I am Downloading Renovate ICE now, only 1.5 hours to go, yay Australian internet.