The #1 Nexus 7 News, Discussion and Fan Site!
2012 Nexus 7 Discussion Forums (1st Generation) => Nexus 7 Root, Hacks, Mods And Development => Topic started by: nexusNovice on March 01, 2013, 06:27:50 PM
-
I used the wug toolkit to root my Nexus 7, 4.2.2
When I clicked on SuperSU it said it needed to Update the binaries. After I said yes I got the attached screen
(http://img.tapatalk.com/d/13/03/02/uhasu3es.jpg)
I know wug used twrp but don't know if I have a "custom recovery" or what that means.
Which button should I click on next?
Thanks
Sent from my Nexus 7 using Tapatalk 2
-
TWRP is a custom recovery. I use TWRP as well. I like the touch UI and it just works for me. If you have Rom Toolbox you can flash recovery after the fact. Do you know how.to boot into.recovery to.check what is.installed? Hold Power /volume down from.off...
Sent from my Nexus 7 using Tapatalk HD
-
Pic wasn't loading for me. Choose normal
Sent from my Nexus 7 using Tapatalk HD
-
If you're rooted, you can let it install the binaries normally. If you've unrooted the other method might be used for the bin folder access. Htc is another phone/tablet.
-
I clicked normal and it updated.
Thanks.
I will now read more about TWRP.
Sent from my Nexus 7 using Tapatalk 2
-
Rom toolbox is really something! Wow!
I need to learn more before I use it and mess things up through ignorance.
Sent from my Nexus 7 using Tapatalk 2
-
Careful because not all of the tools are compatible. I would make sure you have a solid Nandroid backup before deciding to really dive in.
Sent from my Nexus 7 using Tapatalk HD
-
Definitely will. I'm a careful guy!
Sent from my Nexus 7 using Tapatalk 2
-
I agree with Barry. Rom toolbox can be dangerous if you get too curious and aren't certain about what you're doing. A Nandoid should be your best friend with this app. Some changes cannot be undone without it.
Sent From my Razr Maxx(stock .211, waiting for the MFN soak test) via Tapatalk 2
-
Okay, I got the message. I will uninstall it until I am much more knowledgeable.
I appreciate the wise advice.
Sent from my Nexus 7 using Tapatalk 2
-
I only use that app mostly to flash new versions of recovery. Used it once back in the day for changing my build prop for rotation. I read some horror stories about it bricking peoples devices when diving into it . Mostly phones.
Sent from my Nexus 7 using Tapatalk HD
-
Thanks for warning. Much appreciated.
-
New version of recovery? Simple. Download to PC and rename to recovery.img. Boot into fastboot mode.
fastboot flash recovery recovery.img
=ROM toolbox finds the trashcan.
I'm not badmouthing the app. There are some uses for it. Ever tried changing a font face with it or applying a incompatible boot splash screen? Frankly, it can be scary. I do use ROM Manager though. It will update Clockworkmod Recovery, but not the touch version without a fee. I have the Premium Version, but it still charges for some features. I used it the other day to manage my Nandroids. I couldn't locate the new directory.
By the way, ES File Explorer has an integrated .prop file editor.
-
It is pretty amazing how comprehensive it is. I guess that is one of the problems. Tough to get everything to work on every device and every new build.
Sent from my Nexus 7 using Tapatalk HD
-
New version of recovery? Simple. Download to PC and rename to recovery.img. Boot into fastboot mode.
fastboot flash recovery recovery.img
=ROM toolbox finds the trashcan.
I'm not badmouthing the app. There are some uses for it. Ever tried changing a font face with it or applying a incompatible boot splash screen? Frankly, it can be scary. I do use ROM Manager though. It will update Clockworkmod Recovery, but not the touch version without a fee. I have the Premium Version, but it still charges for some features. I used it the other day to manage my Nandroids. I couldn't locate the new directory.
By the way, ES File Explorer has an integrated .prop file editor.
So that will update TWRP or whatever custom recovery to the newest version? Embarrassingly enough, I still use apps instead of fastboot commands. Haven't learned it yet.
I think cwm touch is free with RT
Sent from my Nexus 7 using Tapatalk HD
-
Yes, this command will work with any custom recovery. Any version is renamed to recovery.img and flashed to the recovery partition. fasboot flash [partition] [local file name]. The fastboot flash command can be used to flash any partition. You can use a an [adb pul] command to pull a file off a partition from another device and flash it to any other compatible device. It you bork your boot partition, you can just fastboot flash it back. Same with recovery. Any toolkit uses the same commands. They just build a script that runs them and they put in the other commands to insert pauses like wait for device to boot or wait for user prompt.
-
Post moved to What can you do with "fastboot" and "adb" commands? (http://nexus7forum.com/nexus-7-root-hacks-mods-and-development/what-can-you-do-with-'fastboot'-and-'adb'-commands/)
-
quote by LoocidD
Just as an example, heres why it was easier for me to use the commands and not an app or toolbox. I wanted to restore my Nandroid to a completely reformatted stock device. If you use wugfresh, it installs TWRP. My Nandroids are the CWM blobs/dup version. So either way I would have to set up the account profile and wifi password on the device and enable the usb debugging to install the proper binaries for SU and go to the play store and dowload an app just to flash a compatible recovery. Or I can use [fastboot oem unlock] (unlocks the bootloader) then [fastboot flash recovery recovery.img](flash CWM) then [fastboot reboot-recovery]. From here its [adb push clockworkmod/ mmt/shell/emulated/clockworkmod] to push the Nandroid to the device. Once that completes, while still in recovery I can restore my already rooted Nandroid with all my apps and settings, all without booting the device and reentering the info.
This example should be stickied somewhere.
Sent from my Nexus 7 using Tapatalk HD
-
Yes, a separate adb/fastboot section. I believe the adb push/pull is called nandroid backup because each of the nand chips are copied this way. The first nand might=recovery, then system and others are each on a different chip or partition.
The newest version of adb now has a sideload command. It's not linux, more like dos commands.
The hardest part is typing the long name of an image file, which the toolkits automate with point and click gui.
-
I'll move it to a new thread in a bit. Good idea...
Sent From my Razr Maxx(stock .211, waiting for the MFN soak test) via Tapatalk 2