[Q] Nexus 7 Newb would like feedback on plan for setting up my device - Nexus 7 (2013) Q&A

I recently picked up a Nexus 7, unlocked it, and loaded KitKat yesterday with the factory image. I have set the device up now and would like to use a custom backup to take an image of the 7 and then store that image off of the device on an external drive since I only have a 16gb 7.
I have downloaded Clockworkmod ROM Manager to do this. Is it easily feasible to make a stock image and then transfer the image to an external drive? I'm having an issue installing the Clockworkmod Recovery tool, but I posted a question about that in a different forum.
Any advice would be appreciated.
Thanks,
Rick

I presume you have a custom recovery installed in addition to the ClockWorkMod Manager? If not, use the WugFresh Nexus Root Toolkit to install that, then boot into the recovery and select the backup option. It will create a folder on the root of your device called clockworkmod which will contain your backups. Just copy that to your PC, and transfer it back to the device when you need it.

C5Longhorn said:
I recently picked up a Nexus 7, unlocked it, and loaded KitKat yesterday with the factory image. I have set the device up now and would like to use a custom backup to take an image of the 7 and then store that image off of the device on an external drive since I only have a 16gb 7.
I have downloaded Clockworkmod ROM Manager to do this. Is it easily feasible to make a stock image and then transfer the image to an external drive? I'm having an issue installing the Clockworkmod Recovery tool, but I posted a question about that in a different forum.
Any advice would be appreciated.
Thanks,
Rick
Click to expand...
Click to collapse
I've used ROM Manager a fair amount for creating backups. It works well, but like was said previously, you'll need to flash a custom recovery. The two main choices are Clockworkmod (CWM) and Team Win Recovery Project (TWRP). CWM works well with ROM Manager in my experience on another device.
I've found TWRP much easier to use though. It features a touch interface. You'll be able to customize the backup file name if you initiate a backup in recovery mode. The file name will also allow spaces, while CWM doesn't.
Check it out at teamw.in/project/twrp2. I think the recoveries are the same, but make sure you select the correct Nexus 7 model (LTE or Wi-Fi). You can flash the image in the bootloader using fastboot. Instructions are avalaible on the TWRP website.

Wrngway said:
I've used ROM Manager a fair amount for creating backups. It works well, but like was said previously, you'll need to flash a custom recovery. The two main choices are Clockworkmod (CWM) and Team Win Recovery Project (TWRP). CWM works well with ROM Manager in my experience on another device.
I've found TWRP much easier to use though. It features a touch interface. You'll be able to customize the backup file name if you initiate a backup in recovery mode. The file name will also allow spaces, while CWM doesn't.
Check it out at teamw.in/project/twrp2. I think the recoveries are the same, but make sure you select the correct Nexus 7 model (LTE or Wi-Fi). You can flash the image in the bootloader using fastboot. Instructions are avalaible on the TWRP website.
Click to expand...
Click to collapse
TWRP will also allow you to backup, restore, and flash from a USB drive if you get a USB OTG cable.
Sent from my SM-P600 using XDA Premium HD app

nrage23 said:
TWRP will also allow you to backup, restore, and flash from a USB drive if you get a USB OTG cable.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick

C5Longhorn said:
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
Click to expand...
Click to collapse
TWRP working fine here..

C5Longhorn said:
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
Click to expand...
Click to collapse
Just backed up stock KitKat to a thumb drive and flashed newest 4.4 Omni Rom from thumb Drive. Use the WugFresh Nexus Toolkit to flash recovery. It makes it much simpler.

C5Longhorn said:
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
Click to expand...
Click to collapse
From what I've read, the stock recovery for KRT16S is the same as KRT16O. I'm running the latest TWRP on KRT16O without issue.
Assuming your bootloader is unlocked, you shouldn't have an issue. Can you list the steps you're using to flash recovery? Maybe you're missing something.
If you have the correct driver on your computer and you're using fastboot, the command should be "fastboot flash recovery [insert recovery file name].img" from the fastboot directory.

Wrngway said:
From what I've read, the stock recovery for KRT16S is the same as KRT16O. I'm running the latest TWRP on KRT16O without issue.
Assuming your bootloader is unlocked, you shouldn't have an issue. Can you list the steps you're using to flash recovery? Maybe you're missing something.
If you have the correct driver on your computer and you're using fastboot, the command should be "fastboot flash recovery [insert recovery file name].img" from the fastboot directory.
Click to expand...
Click to collapse
Ok, maybe I was doing something wrong. The command line indicated it was installing correctly when I flashed it. However, when I rebooted to recovery it was never TWRP.
I just installed Clockworkmod Recovery so it was probably an error on my end.
Now, since I have made a backup, how can I identify where it is stored? I would like to move it to my computer since I only have a 16gb 7.
Thanks for all the replies,
Rick

I can't remember the default location. I think it's sdcard/clockworkmod/backups.
If you remember the file name, you can just search for that using ES File Explorer or a similar app.

Wrngway said:
I can't remember the default location. I think it's sdcard/clockworkmod/backups.
If you remember the file name, you can just search for that using ES File Explorer or a similar app.
Click to expand...
Click to collapse
great, thanks for all the help. I will probably reflash back to stock and then rebuild my device and backup. I have OCD about making sure I've got the cleanest install and right now don't know that for sure since it's been trial and error.

They are saved in /mnt/shell/emulated/clockworkmod/backup
They are hidden from other apps, so you need a file explorer with root to move them.

Great, thank you for the reply. The help from folks on the forum has been fantastic and really helps a newb.
Rick

Related

[Q] Nexus doesnt let me do anything

Hello
I have purchased a second hand Nexus. It is rooted and has got custom rom. Also Teamwinner or so is installed. When i boot into recovery to install some other rom it exits with error 7. Same when i try to update the teamwinner to the newest version.
Any idea what to try?
dosada said:
Hello
I have purchased a second hand Nexus. It is rooted and has got custom rom. Also Teamwinner or so is installed. When i boot into recovery to install some other rom it exits with error 7. Same when i try to update the teamwinner to the newest version.
Any idea what to try?
Click to expand...
Click to collapse
i remember seeing error 7 before on a rom i tried to flash.. i was using CWM so its not the recovery's fault. turns out there was a problem with the rom...
so find another rom to flash would be my answer for now.
The problem is that i get this error whatever i tried to flah. Even cwm or some other rom result in same error
dosada said:
The problem is that i get this error whatever i tried to flah. Even cwm or some other rom result in same error
Click to expand...
Click to collapse
What procedure are you using to flash? What file are you trying to flash and where did you get it from?
I start up the phone using volume down and power. Then in teamwinner i chose install zip and then the file
so far have tried, all downloaded from here or linked from here, those files
CWM-Touch-6.0.2.5-DJ
Hellybean-20130405-crespo
TWRP-2.4.4.0-DJ
jellyshot_crespo-v3.3
nothing works. all of them exist with error 7
dosada said:
I start up the phone using volume down and power. Then in teamwinner i chose install zip and then the file
so far have tried, all downloaded from here or linked from here, those files
CWM-Touch-6.0.2.5-DJ
Hellybean-20130405-crespo
TWRP-2.4.4.0-DJ
jellyshot_crespo-v3.3
nothing works. all of them exist with error 7
Click to expand...
Click to collapse
.....
This is the Galaxy Nexus forums, that firmware aka ROM is for crespo aka Nexus S
Sent from my Nexus
Fair enough about the roms, but why cant i even install cwm? This shows me just the error 7 too
I wouldn't be surprised if your recovery is either not for your device or not even a flash able zip.
dosada said:
Fair enough about the roms, but why cant i even install cwm? This shows me just the error 7 too
Click to expand...
Click to collapse
Where did you get that CWM? http://www.clockworkmod.com/rommanager? If so those are img files, for flashing from fastboot. But I have no idea what "DJ" is for. To flash from recovery it needs to be packaged in a flashable zip.
Or you can install CWM from the ROM Manager app. Or TWRP from GooManager.
quite frankly i wouldnt use CWM. The UI is annoying as hell, and it tends ot be a lot slower, at least from my own experience.
I recommand TWRP, http://www.teamw.in/project/twrp2/90 latest version here for maguro.
if you have adb set up, installing twrp is cake, simply open adb and type:
1) adb reboot bootloader
2) fastboot flash recovery TWRP.img <-----assuming you are in the directory of that img file you just downloaded, and TWRP is just the name of the img file, its usually attached with version, so i would rename it for easier access.
3) after you flashed it just boot into recovery and start flashing your new rom.
If all else fail.....use the toolkit and flash factory image for a fresh start, i havnt failed with factory image yet

[Q] Clockworkmod ROM Manager Question

I'm new to Android and recently picked up an 2013 Nexus 7. I unlocked the device and flashed 4.4 Kitkat yesterday. Today I downloaded Clockworkmod Rom Manager so I could make a backup image.
After installing ROM Mgr version 5.5.3.0, I launched the app and received the message that I needed to install the custom recovery. I followed the steps given in the app below:
1) Identified device as Nexus 7
2) Selected "Install Recovery ClockworkMod Recovery"
3) Selected 'Flash Clockworkmod Recovery'
A download overlay appeared and the download completed. After doing this, I rebooted the device into recovery mode (power + Volume UP), but the stock recovery was still there. I tried the download again using the steps above, but still no luck. When I select "Reboot into Recovery", I receive the error message "An error occurred while attempting to run privileged commands".
Question:
1) Where are these Clockworkmod Recovery downloaded files going and how can I get rid of them? If I do a full wipe of the device to clear out these junk files that I may have downloaded?
Any input would be much appreciated. My goal is to set up my device, and take a base image that I can store off of the device on an external drive.
Thanks,
Rick
Cliffs: Installed Clockworkmod ROM Manager and am doing something wrong setting up Clockworkmod Custom Recovery
Haven't used ROM manager in a long time but there should be a ROM manager folder downloads should be there. Also fastboot either cwm or twrp and you can make a back up.
shane1 said:
Haven't used ROM manager in a long time but there should be a ROM manager folder downloads should be there. Also fastboot either cwm or twrp and you can make a back up.
Click to expand...
Click to collapse
Thanks Shane. I will check for the files. I basically flashed Kitkat and now just want to make a Nandroid backup. I assume since the device is unlocked that means I'm rooted.
In order to root you have to flash supersu in recovery.
shane1 said:
In order to root you have to flash supersu in recovery.
Click to expand...
Click to collapse
Thanks, I now think I may not be rooted but rather just unlocked which was required to flash Kirkpatrick from a command line.
After you flash a recovery, http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip flash that in recovery and you'll be rooted.
shane1 said:
After you flash a recovery, http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip flash that in recovery and you'll be rooted.
Click to expand...
Click to collapse
Thanks, it makes sense now. All I did really was unlock, and flash in the bootloader and then the 4.4 image file. So, I'm not rooted, but just unlocked.
Is it necessary to root the device to take a Nandroid backup?
Rick
I just read your new to android make sure you read directions of anything you plan on flashing. Also its good to read entire threads if you have any issues cause your probably not the first to have an issue. Enjoy.
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Not necessary to root but you do need to flash a recovery IMO tarp is the easiest
C5Longhorn said:
Is it necessary to root the device to take a Nandroid backup?
Rick
Click to expand...
Click to collapse
No, you do not need to root to make a nandroid.
meekrawb said:
No, you do not need to root to make a nandroid.
Click to expand...
Click to collapse
It seems like most of the custom recoveries like Clockworkmod recovery and TWRP require you to be rooted.
C5Longhorn said:
It seems like most of the custom recoveries like Clockworkmod recovery and TWRP require you to be rooted.
Click to expand...
Click to collapse
Nope. You need a custom recovery to root. And to make backups. You do not need to be rooted to make backups. That is how it is on the devices I own, anyways.

Root for Stock 6.0.1

From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Root works with supersu version 2.62-3. Thanks
sam298 said:
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
Click to expand...
Click to collapse
That wasn't my experience. I took the 6.0.1 update and it failed. So I ran
Code:
fastboot flash system system.img
fastboot flash boot boot.img
using the system and boot images from the 6.0 update. And then I waited for the OTA again. It installed ok.
Using TWRP I installed SuperSU 2.60 for a systemless root of the boot image. Everything is fine.
i can't even get pass installing twrp. every time i flash twrp in fastboot mode it works but it wipes my entire device. booting into twrp shows "NO OS INSTALLED' and even the sd card storage is wiped. the only way to get it to boot is to flash back 6.0.1 full stock rom. any help???
Try nexus root toolkit.
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
WugFresh did not work for me, after booting into TWRP and looking for the SuperSU and BusyBox they don not show up. Below is a post I have over on WugFresh Forum.
I’m having the same problem as everyone else. I’m using 6.0.1 MMB29K. It goes through the motions but when TWRP launches the /sdcard directory is empty. However, when I reboot and look at the files using an app called File Manager, I see them in /storage/emulated/0/!ReadyToFlash/Root_Files/. However, if I use a app called Root Browser I see a directory called sdcard and in there is !ReadyToFlash/Root_Files/ so they are being copied to the tablet but when you go into TWRP to install them they can’t be found. I tried to use the app Root Browser and make a directory called kiledl, this failed, probably because I do not have root access. Kind of a catch 22 here. I was just going to copy the files in sdcard to my directory and then try again. NO go!!! Anyone else have any ideas? I seems like this is some sort of permissions issue with the files but only from TWRP. I sure hope someone comes up with an answer, WugFresh and ideas?
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
same result. twrp installed but can't detect my sd card or any files on the device
Download latest SuperSU 2.62-3.
Root via Nexus root toolkit.
Then copy SuperSu to nexus and flash, supersu not from NRT but downloaded latest 2.62-3, busybox and last rar.
Sorry for my English.
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
dlkile said:
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
Click to expand...
Click to collapse
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
aiiee said:
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
aiiee said:
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Correct only when using TWRP. However, I was using WugFresh NRT and it does a temporary install of TWRP then you install the SuperSU and BusyBox files. However, with the wrong version of TWRP you would not see the files in the SDCard folder, it would be empty. However, booting back to Android and using File Explorer the files where there. Using the modified version of TWRP would correct this.
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
r.sorujlall said:
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
Click to expand...
Click to collapse
Yes, here is the link you need to select the LTE or WiFi version depending on you device. I do not have enough post to be able post links, so try removing the "*" from the link below.
forum*.xda-developers*.com/nexus*-7-2013/nexus*-7-2013-qa/mount*-recovery*-t3064562
dlkile said:
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
Click to expand...
Click to collapse
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
aiiee said:
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
Click to expand...
Click to collapse
You most have the same unit as I do. I just got mine a week ago from GroupOn as well.
i bought mine about a week ago off amazon. i had a gift card and had nothing to buy so i decided to get the N7 and give it a try

How do I backup my stock recovery?

I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
tcmoffitt said:
I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
v7 said:
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
Click to expand...
Click to collapse
HTC One m8 Tmobile
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Which T-Mobile ?
If it is T-Mob US .. there's a dedicated section for T-Mob US and you can find any info there.
tcmoffitt said:
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Click to expand...
Click to collapse
This is not possible to backup your stock recovery. When you need that you can download it simply (base on your phone's build number). Also you can extract stock recovery frome your ota zip update(the file with img format inside of firmware folder)
Arsinn said:
This is not possible to backup your stock recovery.
Click to expand...
Click to collapse
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
redpoint73 said:
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
Click to expand...
Click to collapse
Hi, redpoint73...
Maybe I'm missing something here, but I'm not seeing an option to backup the Recovery in TWRP 2.8.7.0... Just Boot, Cache, System, Data and Android Secure are available (see attached screenshot). I remote booted TWRP from my laptop, as I did when I rooted Marshmallow around a fortnight ago, in order to keep the stock recovery intact.
It would certainly be useful to be able to backup the stock recovery via TWRP... I just haven't found a way of accomplishing it .
-----
But a possible option to backup the stock recovery would be to use the Flashify app...
Remote boot TWRP from your PC, acquire root, and then run Flashify...
Flashify PlayStore link...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
XDA discussion thread...
http://forum.xda-developers.com/showthread.php?t=2349847
This app uses <dd=if/of> commands to backup and potentially restore the boot and/or recovery images.
Although it does require root to work.
I've used Flashify on my Nexus 7 and Nexus 9 in the past, but never on my M8, except to backup... never to restore, so I cannot personally vouch for it's safety on the M8.
-----
What I'm unsure of about Flashify...
@redpoint73, @ckpv5, maybe you guys could shed some light on this...
Would such a <dd=if/of> created backup of stock recovery be flashable via fastboot?
And would it be safe to do so?
I know that TWRP uses <dd=if/of> commands, having looked through TWRPs logs... but I'm not quite sure how fastboot works when it comes to flashing stuff, and I'm very wary about doing it myself or recommending it for others.
Normally, you'd just use the Flashify app to restore any recovery/boot.img backups you've previously made...
But Flashify requires root to work, and with an unrooted system, this is isn't viable. So could one use fastboot in the normal way to flash such a previously made backup of the stock recovery?
-----
Anyhow, it's not critical at the moment for me, because I've not flashed TWRP to my M8, my stock recovery remains intact.
-----
I would recommend anybody reading this seeking to root their Marshmallow M8 to just remote boot TWRP from their PC with fastboot boot twrp.img (ie., don't actually flash it), perform an unrooted Nandroid backup first...
...and then flash Chainfire in the usual way.
This leaves the stock recovery intact, which will be required for future OTAs.
And there still might be some...
My Nexus 9 receives monthly security patches from Google (probably after the StageFright debacle of last year), and it may well be that the M8 will also continue to receive security patches, despite it being nearly two years old.
So you need to be ready... with an unrooted/untouched Nandroid of your own creation and the stock recovery.
I know that Chainfires systemless root method is supposed to address this issue, but if you're going to mess with system, you should have a Nandroid backup anyway...
...just in case.
Rgrds,
Ged.
Funny, I use the fastboot boot option to boot into TWRP saving my original recovery.

Installing TWRP over CWM?

Hello,
I am wondering if it is possible to install TWRP over top of CWM? When I initially rooted my phone CWM was installed, however to install a new rom I need TWRP. Is this possible?
Thanks,
Skyty said:
Hello,
I am wondering if it is possible to install TWRP over top of CWM? When I initially rooted my phone CWM was installed, however to install a new rom I need TWRP. Is this possible?
Thanks,
Click to expand...
Click to collapse
Yes. It's been a loong time. Best I can recall, I did the following:
1. Flash'd a ZIP of an old TWRP (couldn't find latest in ZIP file)
2. Rebooted into Recovery
3. Used old TWRP to flash IMG file of new TWRP
Just to make sure I understand (as it's been a while since I rooted a phone or done anything like this).
1.) When you say flashed, do you mean in the TWRP app on the screen where you select your phone model?
2.) So if I flash TWRP (in the manner I described above assuming that's what you meant) and reboot into recovery it will overwrite Clockworkmod and then I'll be in TWRP recovery?
3.) If I do this with the most recent TWRP version I'm assuming this step will be unecessary?
My apologies if I misunderstood what you were trying to say! Thanks for taking the time to respond!
Skyty said:
...
1.) When you say flashed, do you mean in the TWRP app on the screen where you select your phone model?
2.) So if I flash TWRP (in the manner I described above assuming that's what you meant) and reboot into recovery it will overwrite Clockworkmod and then I'll be in TWRP recovery?
3.) If I do this with the most recent TWRP version I'm assuming this step will be unecessary?...
Click to expand...
Click to collapse
Quick answers: No, no, and maybe.
It appears that you may be confusing the TWRP app (which is basically useless bloat) with the actual TWRP recovery. You need to find and download the latest TWRP recovery for your device model. If you can find a ZIP of it, great; because CWM can then install TWRP recovery for you (so that when you reboot into recovery, you'll see TWRP instead of CWM). In my case, there was no ZIP available for the latest TWRP; it was available only as an IMG file. An old version of TWRP recovery, however, was and likely still is available in a ZIP file. So use CWM to install that ZIP of older TWRP, which can then install newer TWRP as an IMG file. I'm just a struggling noob myself, but I'm pretty sure CWM is not able to install an IMG file. Good luck!
MrGoodtunes said:
Quick answers: No, no, and maybe.
It appears that you may be confusing the TWRP app (which is basically useless bloat) with the actual TWRP recovery. You need to find and download the latest TWRP recovery for your device model. If you can find a ZIP of it, great; because CWM can then install TWRP recovery for you (so that when you reboot into recovery, you'll see TWRP instead of CWM). In my case, there was no ZIP available for the latest TWRP; it was available only as an IMG file. An old version of TWRP recovery, however, was and likely still is available in a ZIP file. So use CWM to install that ZIP of older TWRP, which can then install newer TWRP as an IMG file. I'm just a struggling noob myself, but I'm pretty sure CWM is not able to install an IMG file. Good luck!
Click to expand...
Click to collapse
Ahhhh, okay that makes sense. I think I follow. Now in another thread you mentioned that if I need to go back and restore I'd use TWRP to flash CWM, hen I can use CWM to recover my old nandroid backups.
A couple final questions. Will I need to do a wipe when I flash the old TWRP zip (side note, do you know a good place to find those)? If I need to go back to CWM is there any place I can find it to flash with TWRP?
Thanks for all your help!
Skyty said:
... if I need to go back and restore I'd use TWRP to flash CWM, hen I can use CWM to recover my old nandroid backups ...
Click to expand...
Click to collapse
Correct. That is IF you can find TWRP and CWM as ZIP files. I used to switch back and forth frequently, but that was years ago. TWRP is so much more useful, I no longer have anything CWM related nor the ZIPs; and can't even find where I got them. I'm pretty sure they were here on XDA. Spent some time searching, no luck. Then I tried Google. The first snippit nail'd it, here:
https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207
Skyty said:
.... Will I need to do a wipe when I flash the old TWRP zip...
Click to expand...
Click to collapse
I never wiped. I seem to recall that when installing to the recovery partition, one of the steps I saw in the log was a wipe or maybe even a reformatting of that partition taking place along the way.
Skyty said:
.... (side note, do you know a good place to find those)? If I need to go back to CWM is there any place I can find it to flash with TWRP?
Click to expand...
Click to collapse
They're both in the link (above).
Skyty said:
.... Thanks for all your help!
Click to expand...
Click to collapse
That's what the [Thanks] button is for, here on xda.
MrGoodtunes said:
Correct. That is IF you can find TWRP and CWM as ZIP files. I used to switch back and forth frequently, but that was years ago. TWRP is so much more useful, I no longer have anything CWM related nor the ZIPs; and can't even find where I got them. I'm pretty sure they were here on XDA. Spent some time searching, no luck. Then I tried Google. The first snippit nail'd it, here:
https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207
Click to expand...
Click to collapse
I appreciate the link, however, I think those zips are for a different model of phone than mine. However, I think I possibly found versions that will work for me... Is there any real way to confirm?
The serranoltexx CWM Zip
https://forum.xda-developers.com/showthread.php?t=2364980&page=99
The serranoltexx TWRP Zip
https://androidfilehost.com/?fid=24052804347768468
However, I'm not 100% certain either of these will work, and I'm not sure how I'd figure that out.
MrGoodtunes said:
That's what the [Thanks] button is for, here on xda.
Click to expand...
Click to collapse
Done!
Skyty said:
... those zips are for a different model of phone ...
Click to expand...
Click to collapse
OMG! You're right, those are for the Value Edition. I completely miss'd the "ve" in them. Sorry.
Skyty said:
... I think I possibly found versions that will work for me..
The serranoltexx CWM Zip
https://forum.xda-developers.com/showthread.php?t=2364980&page=99
The serranoltexx TWRP Zip
https://androidfilehost.com/?fid=24052804347768468 ...
Click to expand...
Click to collapse
I remember using that very CWM zip version 6.0.5.1, so it should work okay. Good find.
I'm not familliar with that particular TWRP zip. It does clearly indicate being for the i9195 model; I'm just not sure about what "open" means at beginning of zip's filename. Still, worth a try. (If it fails, you can more easily find a TAR file of the most recent TWRP and use Odin to install it.)
MrGoodtunes said:
OMG! You're right, those are for the Value Edition. I completely miss'd the "ve" in them. Sorry.
I remember using that very CWM zip version 6.0.5.1, so it should work okay. Good find.
I'm not familliar with that particular TWRP zip. It does clearly indicate being for the i9195 model; I'm just not sure about what "open" means at beginning of zip's filename. Still, worth a try. (If it fails, you can more easily find a TAR file of the most recent TWRP and use Odin to install it.)
Click to expand...
Click to collapse
So, just thought I'd let you know that I'm up and running with LineageOS and I tested reverting back and forth to CWM and TWRP. Eveything seems in working order! I appreciate you help and have clicked the thanks button on your messages! All the best!
Skyty said:
... I tested reverting back and forth to CWM and TWRP. Eveything seems in working order!
Click to expand...
Click to collapse
That's excellent. It's really amazing how much we can do with this little S4mini device; thanks to the work of devs, several of whom are still providing updates. After all there's never been a more powerful device (other than S4mini VE) that weighs under 4 oz.
MrGoodtunes said:
That's excellent. It's really amazing how much we can do with this little S4mini device; thanks to the work of devs, several of whom are still providing updates. After all there's never been a more powerful device (other than S4mini VE) that weighs under 4 oz.
Click to expand...
Click to collapse
Yeah, its amazing! I've been able to breath new life into my old phone, I'm shocked at how well it runs on the S4; not as well as my newer phones, but better than before. Funnily enough, its actually running a newer version of Android than my S8 and S10e haha. Now onto those phones... been trying to get them both rooted but it's looking like a no go haha.

Categories

Resources