Related
Welcome to the original thread, of Beatsleigher's Root Helper!!
This program is completely free, with no Xtra options for donators...
What this program will do:Well this program is designed for beginners, and advanced users. It has several modes; If you like to do everything yourself, then Ok, you can. If however you want Windows to do everything, it will.
If you need to setup ADB drivers, then follow the steps, in the ADB -> Help menu!!
List of features:Several Reboot options,
Backup/Restore
Unlock bootloader (fastboot)
Relock bootloader (fastboot)
Root (ADB+fastboot)
Flash recovery (fastboot)
All-in-one solutions
Complete make over, now using a GUI!
Very explicit detailing of what the program is currently doing!
Install drivers - (USB + ADB/fastboot drivers)
List of ROMs/kernels
Help menus
What's to expect:In-program E-Mail subscription, to get notified about updates.
Better IE Engine for XDA Link.
Context menus, for faster checking of radiobuttons.
Maybe adding an advert or two. Because I am now slowly but surely needing more money, for phones, so that I can program programs like this, for them.
Maybe re-add the main menu music. But, with music, that is a bit more calming... And not House ^^
A fully functional fastboot menu.
A user experience program, so I can collect feedback!!
Working progressbars.... (-.-")
FAQ:Q:When installing the drivers, why do I need to change my system configuration?
A:You need to configure your machine, to notice the device, but to leave it alone, instead of looking for, and downloading drivers for it. This just confuses the computer, meaning you can't do anything in the bootloader, because Windows Update doesn't yet have the needed drivers...
Q: Why have you gone over to making a GUI? The batch files, were just fine...
A: I'm going over to making a GUI, because it is easier to use, less work. And I have the option, to just, drag & drop a button, write two lines of code, to make the button functional and then it's just a matter of creating the batch file, converting it to an EXE. Easy as pie. Whereas, with the batch files, to create one more option, you have to write 6 lines of code, then the batch file, and then half of the stuff doesn't work properly, because you didn't debug... If you know, what I mean...
Q: Why are there so many files???
A: This program needs so many files, so it can perform different processes/options/tasks
. But it isn't hard, to find out, what file, does which job
Q: Why is there only a version for windows??
A: I am working on a version, for Mac users, but it will take some time. I'm glad to be nearly finished, with the Windows version
Q: I want to donate to you, but you won't allow it. Why?
A: I don't accept any donations, because I only wrote the program to flash files on to your phone... I don't want to take credit for things, that other people did.
Instead of trying to donate to me, donate to chainfire, ChainsDD, and Kousik Dutta; for creating such brilliant recoverys, Apps (like superuser and ROM Manager) and ROMs...
BTW: If you really want to donate (which you won't ), you can send me some albums ^^ I need house music, to work.. And all my songs/albums have been listened dead -.-
Q: Do you mind if I use this program for commercial use, and post videos(tutorials) on Youtube?
A: As long as you DO NOT create mirrors, and let me know, I'm not that fussed... But then please post the link of the video to me, so that I can tell you if I like the way you did it, or not.
Q: When are you gonna stop talking about things, that don't interrest anyone (the FAQ)??
A: Now, but still thx for reading, other good questions will be posted here, aswell...
Thanks:Many thanks to Kouschik Dutta for creating the recoveries for near-to all Android phones. Yo the man!
And not to forget the awsome app: ROM Manager ^^
Thanks to my good friend Accendare (baddinski), for creating the splashscreen. I appreciate it much
Thanks to Google, for creating the AOSP, for the great developers, to create even greater ROMs, for us!
Also, thanks to Google, for buying Android, and making suh a (rather) bug-free OS!!
If I forgot anyone, please let me know immediatly!!
Downloads:
If you want to flash stock firmware, you will need to install this. This contains all the neccessary files/folders you need:
GSM: to be downloaded, by clicking this...
CDMA: to be downloaded here...
Ok, we've done it!! (I've done it...) We've gone out of Alpha.
We beat the beta!
Now, I'm proud to present; Beatsleigher's Root Helper... VERSION 3.0.0.8!!!!!!!!!!!!!!!!!!
Each and every script, has been either re-written, or has just gotten a makeover!!
Everything unneeded, has been removed, It's more compatible, with Windows XP, loading time has gone down!!
I've added a few options, but not that many, to make a big changelog...
To upgrade/update, please, copy ALL the files, you created/copied/moved there, to a safe place, on your hard drive. Then, delete "C:\Beatsleigher_root_helper"
Run the installer (It's contained in an ISO image, so, download PowerISO, should you not ahave an image mounting system...) and done!!
Download here
Screenshots:View attachment 967846 View attachment 967847
View attachment 967848 View attachment 967849
View attachment 967850 View attachment 967851
View attachment 967852 View attachment 967853
View attachment 967854 View attachment 967855
View attachment 967856 View attachment 967857
View attachment 967859 View attachment 967860
View attachment 967861 View attachment 967862
View attachment 967863 View attachment 967864
If you want to see more, download it
Installer:The installer will install to your C:\ drive. Some older scripts, are still working with "%homedrive%" so, to make sure, that everything is working, please make sure, that your homedrive is your C:\ drive. Or, if you have a seperate C:\ drive (like me), copy a copy, of the "Beatsleigher_root_helper" folder, to your homedrive. Then it should do the trick. By the tiome, the program is released properly (full) all scripts should be working with "C:\".
Should you have NOT got a C:\ drive, because your homedrive is named differently/you deleted the C:\ partition, see: installation help.
EDIT: The installer has been split in two!! They are both in an ISO image... Once mounted, the secondary installer will run (setup.exe). Just open the virtuall CD-ROM, and run "Install.exe"
Requests:If you have any requestes (features, etc.), please PM me, or send me an E-Mail!!
Or, visit: This page
Please read!!:Sorry for not updating this thread, as much, as the GSM thread. If you want to stay up-to-date, then click here every now and then
Changelog:
Version 3.0.0.8:
Full release, no BETA, anymore...
Two installers, instead of one...
All scripts have been re-written or have had a makeover...
Version 2.6.5.7 [Minor 3]:
Some tweaks and additions... Mostly hidden...
Some preparations, for full release.
Next version will be 2.7
Version 2.6.5.5 (BETA) [Minor 2]:
Added some juicy developer features! (Using the ADB shell)
A few options, for n00bs, are in there, aswell...
Added options, to the ADB menu.
Added a complete new form. (Dev. options)
Added a few more scripts. Making the update zise about 6MB, on your HDD
Removed some buggy code.
When navigating, from ADB menu to Dev. Menu, ADB menu closes, but can be re-opened from the "File" menu.
Dev. menu has also got CPU/RAM usage detector!
Download, for more changelog
Version 2.6.5.4 (BETA) [minor]:
Working progressbars (!!!)
ADB menu got a makeover.
Added CPU/RAM usage detection
Added option to enable/disable CPU/RAM usage detection in fastboot menu.
Fixed bug in ADB help menu.
Added options to the m,ain menu...
The rest has been forgotten, or you're ment to download the program, and check for yourself...
NOTE:
If you are interested in downloading this product, please download version 2.6.5.3, install and then download/install 2.6.5.4.
Then you can be rest assured, that everything is working as good, as it should in the BETAphase, of a program
Version 2.6.5.3 (BETA):
Removed bug that caused phone crash, whilst prompting device name.
Cleansed the code.
Removed two un-used forms.
Repaired the menustripbutton.
Added scripts, to update package.
Removed other scripts, from update package.
Compressed some, of the files (drivers, executables)
Using traditional installer, again.
Installation path set to: C:\Beatsleigher_root_helper\
Version 2.6.5.2 (BETA):
Fastboot menu fully working.
Fastboot help menu, is popping up/has been created, though it has no content.
ADB help menu is working/all buttons have a task.
Some unneeded code has been removed.
A complete list of ROMs & kernels is present (CDMA + GSM).
No change in the IE engine...
All messages giving a tone/sound.
Options have ben added to the ADB menu.
New all-in-one solutions for ADB menu.
Scripts have been edited, for more friendliness
More tooltips.
Progressbars still not working ( )
Maximization has been disabled in ALL windows.
Better usage of RAM, whilst opening other exe - files
Version 2.6.5.1 (BETA)
Added update check-support.
Changed file hoster to mediafire (updates coming from there)
Added ADB reboot options.
Fastboot reboot options working.
Added (hidden) features.
Using a proper installer.
Can be installed anywhere on HDD, will work anyway
Two packages are to be downloaded, not one. This ensures, that updates are working, as planned.
(Hidden features will be released, when version is 2.6.5.3 (next update) )
Version: 2.6 D:
Everything you see, down the bottom is working.
You can now flash a recovery via fastboot menu!!
Kernel and ROMs, I have decided, to take them back out. They were a bit buggy...
The size of the EXE itself, has gone up to, ca. 2.4 MB.
Option to flash stock ROM (LTE + GSM) has been enabled, for fastboot.
Looks a bit more friendly
Icons have been added!
You'll have to find the rest out, yourself
Version 2.6C:
ADB menu has been carried on. You are now able to flash a kernel (LTE & GSM)
It will open the Explorer for you, when you need to copy the file!!
LTE menu is finally working!! It had problems opening, due to a minor type-error.
Though the LTE menu is working, you will only be able to use one button, in about an hour. Once I've completed doing the ADB menu...
(See: "What's to expect", for more info's on what's coming!!)
Version 2.6:
New GUI!
Complete new code.
In-program help.
Direct link to thread.
Seperate fastboot and ADB menus!
More explicit details...
Removed the music, that pops up, upon start. (To many house haters )
All batch files converted to executables... (This prevents tampering with the code)
Fully compatible with 64x machines. Doesn't use as much RAM, but therefore shows up as a process.
Installation help:
Not much can go wrong, when install9ing this program.
Mostly, the reasons, of failure, to use this program, are due to:
Not having a C:\ drive.
Not copying a copy of the root folder, to hamedrive, if C:\ is not the homedrive, of your windows machine.
Tutorial 1:
Problem: I installed the program, but my homedrive is not C:\. I installed to C:\, but I can't use half of the program.
Well, first of all; sorry, for this. I could of said this earlier... I forgot to edit the scripts, to use ONLY the C:\ drive, so it useshalf the C:\ drive, and half your homedrive. But, that's why I posted this tutorial.
It's quick & easy ^^
Tutorial:
Install the program, to your C:\ drive. Close the installer, and re-open it.
Once back in the installer, set the installation path to your homedrive (Where Windows is installed).
Install to that directory, and done
It should now work ^_^
Tutorial 2:
Problem, I don't have a C:\ drive, and the ROM-Full/Less version, isn't available for download... What to do??
This is also no problem!! With a few, simple clicks of your mouse, we will fix this minor problem
Tutorial:
Type following key-combination, on your keyboard; START(WIN)+R.
The "Run" prompt should now pop up.
In the RUN prompt, type: "diskmgmt.msc" and it enter.
Once the disk manager pops up, shrink your homedrive(or, if you have unalocated disk space, which is 3GB or more, right click on that)
Shrink your homedrive, about 3GB. If you can, allocate more space, because you will need quite some space, because of stock ROMs/custom ROMs/kernels and backups.
To shrink, right-click on the partition and select "Shrink Volume". Enter this amount, to shrink: 3072 MB, that should be 3GB. Like I said, feel free to allocate more space.
Now you should see a black field. This is unallocated disk space. Right click on this space and select" Create simple partition" Make sure, you create the exact space, you shrunk, other wise, you will have some unallocated space, on your HDD and this can cause problems, if unnoticed.
Name the partition : C:. Wait, for the Diskman. to create the partition (can take up to 5 Minutes, for that amount of space, depending on size of HDD, CPU clock speed and amount of RAM).
Now, just install Beatsleigher's Root Helper to your C:\ drive and again, to your homedrive. Done! You can now use Beatsleigher's Root Helper.
If you should notice any other problems, please let me know, so I can solve them.
EULA:Please read the EULA, should you not have, during installation. Or, you are interested in installing the prgram.
There is vital information, in this text document!
This post will be used for announcing updates and changelogs!
The first update, to be announced here, will contain some CDMA kernels and ROMs... They will all get QR-Codes, so you can download them directly on to your Android, if neccesary!
Only use this package to root your phone and flash recovery!!
The other images/ZIPs are on their way!! Before I get told off, for not telling you this.... I am making a package, that will delete all GSM files!
This reduces size, and no one gets confused!!
Cool. 400mb is the reason I wouldn't download it. Opinions:
Remove the extra crap. Include just your code.
Create a folder /flash and instruct people to just throw stuff in there. Then code your app to read and list the contents of that folder (If that's even possible).
Your program can't be more then a meg or two itself. This way people can just download your tool and flash whatever. It then won't ever be "outdated" with old files. Streamline it and it'll catch on.
EXT LTE Galaxy Nexus 4.0.3
Transformer TF101 ICS
player911 said:
Cool. 400mb is the reason I wouldn't download it. Opinions:
Remove the extra crap. Include just your code.
Create a folder /flash and instruct people to just throw stuff in there. Then code your app to read and list the contents of that folder (If that's even possible).
Your program can't be more then a meg or two itself. This way people can just download your tool and flash whatever. It then won't ever be "outdated" with old files. Streamline it and it'll catch on.
EXT LTE Galaxy Nexus 4.0.3
Transformer TF101 ICS
Click to expand...
Click to collapse
That's a good idea
I'll try and do something like that
player911 said:
Cool. 400mb is the reason I wouldn't download it. Opinions:
Remove the extra crap. Include just your code.
Create a folder /flash and instruct people to just throw stuff in there. Then code your app to read and list the contents of that folder (If that's even possible).
Your program can't be more then a meg or two itself. This way people can just download your tool and flash whatever. It then won't ever be "outdated" with old files. Streamline it and it'll catch on.
EXT LTE Galaxy Nexus 4.0.3
Transformer TF101 ICS
Click to expand...
Click to collapse
Have done Even though it took a bit longer, to get here... Sorry, about that...
I just kept on forgetting, to update this thread. But it will be different, from now on
Post One: Unlocking and Rooting
Post Two: Installing Roms / Kernels / Tweaks
Post Three: Panic Section / FAQ / Miscellaneous
Unlocking The Bootloader And Obtaining Root
*This part of the tutorial is geared towards Windows users. I have a windows machine and will post instructions only on methods I personally have tested. This guide will assist other users. Once we unlock and root your device: this guide will be relevant to everyone.*
Time required:
20-40 minutes.
Setting up ADB for our device:
Download the AndroidSDK onto your computer.
Note: Google changes their mind every other week as to if this will be distributed as a .zip or an .exe. If you get an .zip file, simply extract the contents to your C:\ drive. For an .exe install it like you would any other program, but set the path directly to the C:\ drive when the installer asks.
Or...you can use this page to download the "ADB for Dummies AIO App."
This will automatically install ADB for you to your C:\ directory. It's very very simple this way.
If your platform-tools folder doesn't have a fastboot.exe, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder.
Now you have ADB installed! Congratulations.
Unlocking the Bootloader:
***NOTE***
This will perform a factory reset on your device. You'll lose all applications. You'll lose everything. Even the data on your SD Card! Backup your SD to your computer BEFORE performing this. There is a method for backing your applications up, detailed HERE.
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
Samsung's website has a download here under "Manuals & Downloads > Software."
Option Two: Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
While that is downloading, on your Galaxy Nexus: turn USB debugging on.
This can be found in Settings>Developer Options>USB Debugging
Once the drivers are installed, navigate to the C:\android-sdk-windows\platform-tools folder on your computer.
Hold shift and right click. Select "Open Command Window Here."
On your phone: turn USB Debugging On. This can be found in Settings>Developer Settings.
Plug your phone into the computer. Now in this command window type:
Code:
adb reboot bootloader
(Hit Enter)
Your phone should now boot into a screen with a green android with his chest exposed.
Type this:
Code:
fastboot oem unlock
(Hit Enter)
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Your phone will ask if you want to unlock it. Select "Yes" by using the volume keys and use power to select it.
Now, navigate to "Recovery Mode" with the volume keys. Use power to select.
A screen with another Android will pop up. Press Volume Up and Power at the same time.
Select Factory Reset. This process may take a few minutes. Be patient and let it work.
Once finished, select "Reboot."
Your phone is now unlocked!
Obtaining Root Access and Custom Recovery:
Turn on USB Debugging in Settings>Developer Options>USB Debugging.
Download the following:
SuperSU (CWM .zip)
CWM (Pick the version for your device [GSM/SPRINT/VERIZON])
Place the recovery-clockwork-VERSIONNUMBER-toro.img (or the recovery-clockwork-VERSIONNUMBER-toroplus.img if you're a Sprint user. Or the recovery-clockwork-VERSIONNUMBER-maguro.img if you're a GSM user) file into your C:\android-sdk-windows\platform-tools folder.
Put the SuperSU.zip on your phone.
Open another Command Prompt if it isn't still open. (Navigate to C:\android-sdk-windows\platform-tools and shift + right click. Select "Open Command Window Here.")
With your phone plugged in type:
Code:
adb reboot bootloader
(Hit Enter)
And wait for your phone to boot into the android again.
Now type:
Code:
fastboot flash recovery IMAGENAME.img
(Change the file name to the correct file name and Hit Enter)
Once that is finished: select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the SuperSU.zip that you transferred earlier and select "Yes" to installing.
Navigate back to "Reboot" and reboot your phone.
You're now rooted!
However, ClockworkMod Recovery won't continue to load after this.
To fix this, find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option.
If your recovery still doesn't stick around after a reboot, you have another couple options. Find a file explorer that allows root access, such as Root Explorer. Use this program to rename /system/etc/install-recovery.sh to /system/etc/install-recovery.bak. You'll need to mount the system as r/w to do this. Root Explorer provides a button at the top to do so.
Or, you can do this completely manually by firing up ADB again and running a few commands:
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
(Hit Enter)
Congratulations!
Your phone is now unlocked, rooted, and has a custom recovery!
Continue reading the next posts for info on getting custom roms, kernels, tweaks, and more!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Thanks:
Google, for making Android a reality.
VanillaTbone, for the ADB AIO app.
Droid-Life, for a previous guide that I used as an outline while writing this one.
Efrant, for posting about a bootloader locking utility without USB.
ClockworkMod team, for being a part of making our phones as awesome as they are.
The assorted developers, who continue to push out amazing material for us to use.
The awesome community, for endlessly supporting both Android itself and its users.
Installing Custom Roms Kernels and Tweaks
All of the instructions below require your bootloader to be unlocked. Please follow the guide above and return here when you're done.
Backing Your Files Up:
Time required:
15-25 minutes.
Making a Nandroid
The first thing you're going to want to do is back up your phone's entire system. This is done by making a "nandroid."
To do this, boot into ClockworkMod Recovery. To accomplish this: Turn your phone off. Once it is completely off: hold both volume buttons and the power button until the Android with his chest exposed is displayed. Navigate to the "Recovery Mode" option and select "backup."
This will take some time. Be patient and let it finish. This process is important! You should always have a recent nandroid available on your device.
Backing Your Applications Up
Install Titanium Backup from the market.
Open Titanium Backup. A Superuser request should pop up. Allow it. Note: if Titanium Backup then says it failed to obtain root access; press the menu button and select more>reload application.
Press menu>batch. Select "Backup all User Apps." Select all and "Run the Batch Operation."
Let the process complete. This may take quite some time: depending on how many applications you have installed.
You can now backup your Text Messages, Bookmarks, and WiFi addresses with Titanium Backup as well.
Press Menu>Backup Data To XML to do so.
Backing Your Contacts Up
Note: This process may or not be useful to you. The Google servers should automatically import any contacts you have stored back whenever you install a new rom. Also note that Facebook/Google+/etc contacts will need to be synced again through their respective applications.
Open the Contacts application.
Press the Menu button.
Select import/export.
Export to storage.
Installing A Rom (Or Kernel/Radios/Tweaks/Themes/etc.)
Time Required:
5-10 minutes.
Note:
Follow the guide above about backing your phone up before attempting!
This guide will also work for flashing kernels/radios/themes/tweaks/etc. Simply ignore the part about wiping data and wipe whatever the thread says you should. You only need to restore data after a rom install.
Find a Rom You'd Like To Try:
Verizon Galaxy Nexus
Sprint Galaxy Nexus
GSM Galaxy Nexus
Download the rom you'd like to try on your device.
Most roms also require you to install "gapps" as well.
You can find the correct ones for the rom you're using in the rom thread.
Make sure the Rom and Gapps are on your SD card.
Now, open Google Wallet (if you have it installed) and press Options>Settings>Reset Google Wallet. This will prevent the "Secure Element" errors some users have experienced.
Boot into ClockworkMod Recovery by turning your device completely off. Hold volume up, volume down, and power until the green Android with the open chest is displayed. Navigate to "Recovery Mode" with the volume buttons and select using the power button.
Remember to have a recent nandroid before continuing!
Navigate to "wipe data/factory reset" and select it. Select "yes."
Wait for the process to complete. This may take some time. Be patient!
Once complete: Navigate to "Install Zip from SD card" and "Choose zip from SD card."
Find the rom's .zip and install it. Once that completes install any applicable gapps' .zip.
Select the "Reboot" option.
Congratulations! Your phone should now boot into the custom rom!
Follow the prompts to re-activate your phone.
Restoring Your Applications / Contacts / Nandroid
Time Required:
5-15 minutes.
Restoring Your Applicaions
Install Titanium Backup. Note: you may want the pro key. If you have it, you won't have to manually click "install" on each application. The process is completely automated. Open Titanium Backup (grant root access. If titanium says it failed to obtain root access, press menu>more>reload application). Press menu>batch>restore missing apps with data. Now, here you have a choice to make. Do you want a completely clean install? Select "app only" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). Do you want all of your application data (saved games/settings/etc)? Select "app+data" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). This MAY cause you problems or it may not. Personally, I often restore application data and seldom run into any trouble. If you do find that restoring data caused problems, follow the guide above to re-install your rom and restore without data. This process will take some time. Be patient (I'd suggest turning your screen off so the screen doesn't burn, but that's just me.) It will vibrate upon completion.
You can now restore your Text Messages, Bookmarks, and WiFi addresses if you backed them up by pressing Menu>Restore Data From XML.
Note:
Overclocking/CPU tweaking applications should never be restored with data. Simply deselect it from the list.
Facebook/Haxsync/Google+ may have problems restoring your contacts when installed through Titanium Backup. Simply uninstall and reinstall through the market (and be sure to log in and select to sync your contacts again).
Also, if you have NFC Task Launcher successfully launching Tasker tasks with your stickers: they may not immediately work.
Through my testing, it's as simple to fix as uninstalling NFC Task Launcher and Tasker. Restore Tasker first. Then restore NFC task launcher.
Restoring Your Contacts
If google fails to restore your contacts (not facebook/haxsync/google+/etc) you may import them manually if you backed them up.
Open the contacts application and press menu>import/export>import from storage.
Restoring A Nandroid
If your phone is acting funny or won't boot...restore a nandroid from a previous rom or working set-up.
You may also use a Nandroid to switch back to a previous rom if you decide you don't like the one you're on.
Do this by booting into ClockworkMod Recovery (hold volume up, volume down, and power while your phone is off and navigate to "Recovery Mode").
Simply select "restore" and find the most recent (or relevant) backup.
This process will take some time. Be patient and let it complete! Once done, select "Reboot."
Note:
Nandroids are stored in the "clockworkmod" folder on your SD card. They take up quite a bit of space. ALWAYS have at least one recent one on your SD card. However, since these are huge files: you may like to delete old ones to save space. You must delete backups by booting into CWM and navigating to Backup and Restore>Delete.
Important Notes About Restoration
I outline the method of using Titanium Backup above for a reason. Restoring system applications and data is the most common cause of problems on custom roms. For this reason, always ONLY restore "missing applications" from "user applications" that were backed up when restoring onto a new rom. Every time you restore system data or applications a narwhal sodomizes your favorite childhood cartoon. This is FACT.
Installing Alternate Custom Recoveries
If you find a custom recovery (such as the touch-recovery options) that came as a .img file:
Use these instructions to flash. Plug your phone into the computer. Open up ADB. Move the .img to the C:\android-sdk-windows\platform-tools folder.
Type the following:
Code:
adb reboot bootloader
(Hit Enter)
You can also manually boot to the bootloader by powering off and holding volume down, volume up, power buttons until the green Android with his chest exposed is displayed.
Then type:
Code:
fastboot flash recovery FILENAME.img
(Replace the file name with whatever the .img is called and Hit Enter).
Wait for the process to complete and reboot.
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu). Navigate to recovery and select it with the power button.
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Code:
adb push NAMEOFZIP.zip /sdcard/NAMEOFZIP.zip
(Hit enter)
You may have to reboot recovery to get the file to show up. Now follow the guide above for flashing a rom to get you booting again.
Did you install a tweak that modified only a file or two on your phone? (Find this out by opening the .zip and looking in the folders (ignore META-INF). Good news! We MAY be able to recover you completely. If this doesn't work...you'll have to follow another method.
Get your phone into fastboot (the boot-menu that allows you to select recovery/reboot/etc). Navigate to recovery and select it. Start up ADB. Pull the files that were modified out of the stock rom's .zip (using whatever tweak you were installing as reference to find what was changed) that you're on into the C:\android-sdk-windows\platform-tools folder. Now we're going to push these files onto your phone...replacing the tweaked ones and hopefully getting you booted again. Use this code, but change the values of the file name and where it should reside. This is only an example!
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
This will mount your system so you can write to it.
Code:
exit
(Hit Enter)
This should exit shell and allow the use of adb commands again. You may need to type it a couple of times (until the #_ changes back to the platform_tools> prompt).
Code:
adb push framework-res.apk /system/framework/framework-res.apk
(Press enter after each file that you need to replace).
Note: This last option probably won't work. I'd just skip over it unless you're absolutely adamant about restoring your current setup and want to try everything possible.
Q: I want my SDcard files from my phone...but I'm in a situation where I need to flash stock images! This will erase my SD content. What can I do to save it?
A: Do you have a custom recovery installed? If not, download a custom recovery from post one in this guide and flash it using those instructions. You'll need to be in a custom recovery in order to obtain ADB access without booting your phone. Boot into recovery (With phone turned off: hold Power and Volume+ and Volume- until the bootloader pops up and navigate to "Recovery"). Run the command:
Code:
adb pull /sdcard/ /SDCARD/
(Hit Enter)
This will put all of your files into a folder called "SDCARD" in your C:\ drive. Keep in mind that this will take a LONG time. Maybe a couple of hours.
To restore once you're booting again:
Move the "SDCARD" folder you created from your C:\ drive to the platform-tools folder. Then input:
Code:
adb push SDCARD /sdcard/
(Hit Enter)
Q: How do I make an "ADB Backup?"
A: An ADB Backup will backup your phones data (applications and their settings). Follow the guide HERE about ADB Backups.
Q: My phone gets really sluggish and often turns off or reboots on its own.
A: Without knowing anything about your situation...I'd say you either have severely bad data somewhere or some bad kernel tweaks. Use the rom install guide above, paying close attention to the part about backing up and restoring if you haven't already. In the case of a kernel problem, you're likely undervolting too low. Restore the stock kernel values and see if your problems subside.
Q: My phone screen won't turn on! This requires a battery pull to fix.
A: This is called a "Black Screen of Death" or BSOD. This is generally due to using a governor such as InteractiveX or HotplugX or possibly undervolting your device too low. Change governors or up your slots a bit.
Q: My phone is doing really weird things. Regardless of kernel/rom and even if I don't restore any data at all! Either that or I simply cannot boot up! My phone is possessed no matter what I do!
A: Razorloves has made a wonderful guide on restoring your Verizon phone back to stock. You can find it Here.
Shabbypenguin made an ODIN guide for Sprint users located Here.
Evostance made one for the GSM users, found Here.
Verizon/GSM images can always be found Here in the case that the above guides aren't updated.
Change the file names in the above guides, and you'll be good to go. *At the time of writing: Sprint images not available directly from Google.*
Q: My USB port is broken. How can I return to stock and re-lock my bootloader?
Follow the instructions in THIS post.
FAQ
Roms/Kernels
Q: What is the best rom?
A: The "best" rom is a matter of opinion. Do you like a certain customization and can't live without it? Use a rom that has that option.
Q: What is the best rom for battery life?
A: Roms themselves really shouldn't impact your battery all that much. They can have an impact, but if you're really looking for better battery I'd suggest swapping kernels or tweaking yours.
Q: What is the best rom for stability?
A: All of the roms out are "stable." They may have options that don't work correctly, but generally: this is user error. If you follow my advice on installing a rom, you'll end up with MUCH fewer bugs.
Q: What is the best kernel?
A: The best kernel is a matter of opinion. Some users may love one, while others swear by another. Find one you like and tweak it accordingly.
Q: How do I tweak a kernel for better battery?
A: Generally, you'll want to either change your governor and or undervolt and or underclock your kernel. This is done either by using SetCPU or similar apps, or with an option in your rom (usually labeled "performance" or something similar). Take note: extremely high/low voltages may cause instability. Never "set at boot" until you've thoroughly tested the options you've set. Testing includes low strain (like turning your screen off for an hour) and high strain (like playing a game for an hour) scenarios. To be extra safe: run the values for a couple days before setting them at boot. Follow the users ideas in the kernel's threads for some guidelines. However, remember that not all values will play nicely with all phones.
Miscellaneous
Q: Why does my phone perform so bad on benchmarking tests?
A: This depends on what you define as "bad." Does your phone feel fine? Ignore it. If your phone is really sluggish...you're running bad kernel settings or have bad data somewhere. That being said: our phones aren't going to be FANTASTIC with these benchmark tests. Sorry, but they aren't. We have a huge screen. And huge pixel density. And our GPU isn't the greatest of greats. This isn't bashing on the nexus at all. I'd rather have a phone that performs in every day use than a phone that gets a "FANTASTIC" benchmark but feels groggy when I perform simple tasks.
Q: How can Verizon users get Google Wallet?
A: Scan this with Google Goggles. Open the link with the Play Store.
Q: Why isn't Google Wallet working at [store]?
A: I'm not sure if it's a Google Wallet problem, or a problem with the terminal. But I personally struggle to find a terminal that consistently works in my area. Something that has generally worked for me is to open wallet and go to Options>Reset Google Wallet. You must then re-add any cards you had.
Q: Does my ass look good in these shorts?
A: Yes.
Neat Ideas / How to Show Off the Galaxy Nexus
-Get some NFC stickers. Tagstand has them available.
You can use these to make your phone perform certain tasks when you touch the sticker. Use NFC Task Launcher to define the tasks. These are capable of doing simple things like muting your volume to the more complex like turning on Tasker tasks that do things like auto-reply to text messages while you're at work.
-Do you have any suggestions? Submit them below!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Thanks for the great guide!
I have a few questions. What are kernels? What do they do? Can I have a bad kernel and ROM combination? I'm currently using AOKP build 27. What are some good kernels you would suggest? Should I save my current kernel? How would I go back to my current kernel?
Are BAMF and CM9 only for the CDMA GNex? They both say Toro and isn't that the CDMA version and Maguro is the GSM?
Tks man it was easy and smooth, now i´m rooted rocking cm9 on my Galaxy Nexus!!
3bs11 said:
Thanks for the great guide!
I have a few questions. What are kernels? What do they do? Can I have a bad kernel and ROM combination? I'm currently using AOKP build 27. What are some good kernels you would suggest? Should I save my current kernel? How would I go back to my current kernel?
Are BAMF and CM9 only for the CDMA GNex? They both say Toro and isn't that the CDMA version and Maguro is the GSM?
Click to expand...
Click to collapse
Kernels are the base of your phone.
They are the "engine" as far as software is concerned.
Bad Kernel/Rom combinations...kind of.
Some features may be removed from kernels. Like the ability to use the color control built into CM9. But generally, no. Other than hard-linked features built for the rom and supported by the kernel, no. I've yet to find any other than the CM9 reference I made.
Going back is as simple as re-flashing your kernel.
Remember: turn of any CPU changing apps like SetCPU or Rom-specific "performance" features before switching. You can then re-evaluate your settings.
Bamf is toro only still, I believe.
http://download.cyanogenmod.com/?device=maguro
Maguro cm9 (gsm).
Oh...
And bump for ze sake of easy access.
Wish I could get this stickied <_<
agreed this should be stickied...an a read this 20 times should be applied before posts can be made.....Oh and thanks for this it will be a one stop shop as it progress's.....
Awesome guide. Needs to be stickied. Also, I agree, my ass does look good in these shorts...
Sent from my GSM Galaxy Nexus using XDA Premium
beans_p_ said:
Awesome guide. Needs to be stickied. Also, I agree, my ass does look good in these shorts...
Sent from my GSM Galaxy Nexus using XDA Premium
Click to expand...
Click to collapse
Le' bump.
Huge props, this is fantastically written and very in depth. If I had never flashed before this would be brilliant. Thank you for your work mate excellent job
J
Sent from my Galaxy Nexus - AOKP M4 - Franco M1
Thanks sir!
Another bump.
And I'll continue to do this until this is stickied.
It's straight stupid to not even have ONE stickied thread about the basics...
Can't describe how fantastic this guide is; it should be stickied in both the general and the development section.
If it isn't too much trouble, it would be awesome if you could put the steps to renaming the recovery.sh so the clockwork mod sticks and perhaps to reverse it (if I remember this right).
SovereigN7 said:
Can't describe how fantastic this guide is; it should be stickied in both the general and the development section.
If it isn't too much trouble, it would be awesome if you could put the steps to renaming the recovery.sh so the clockwork mod sticks and perhaps to reverse it (if I remember this right).
Click to expand...
Click to collapse
Actually, I would include that...
But flashing recovery through rom manager works as well.
And I'd rather keep it noob-friendly.
I follow a forum where they said to rename that...and there are like 15 pages of people asking the same questions as to why terminal/adb aren't working.
Fixed wording of "shift" showing as "****" lol.
And...le bump.
@Jubakuba You might want to add the link for the recovery image for maguro as well. Your instructions only have toro in there! Beginners may get stuck on that.
ankushkatari said:
@Jubakuba You might want to add the link for the recovery image for maguro as well. Your instructions only have toro in there! Beginners may get stuck on that.
Click to expand...
Click to collapse
Look again, it's there.
Thanks though!
Edit:
Upon checking to make sure I wasn't wrong...
The link should have appeared next to the CDMA for simplicity.
So I updated.
This was initially a RootzWiki CDMA forum post...
Had to be edited for here a bit...and the merged CDMA/GSM forum here makes it a bit hard.
Thanks!
Awesome job on this Jubakuba, thank you for sharing it. Stickied it is.
(You can quit bumping it now )
xHausx said:
Awesome job on this Jubakuba, thank you for sharing it. Stickied it is.
(You can quit bumping it now )
Click to expand...
Click to collapse
Lol, sorry
And thanks!
thanks, I had no clue about tags, wish they worked with phone off.
That is a very good guide by the way. Wish I had that when I did my phone but I had a great guy help me out. So I was lucky. Thanks for this!
GALAXY NEXUS - SUPPORTS ALL AVAILABLE VERSIONS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.4.1 [05th Oct 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
ChangeLog:
ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
Manual Rooting Instructions for Galaxy Nexus
UPDATES:
VIDEOS:
Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Google Nexus 4 Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct Toolkit being used.
You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.
thnx man!
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Much recomended for all users. Easy and all the options and extras you'll need. Then just flash away..............
dangambino said:
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Click to expand...
Click to collapse
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
mskip said:
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
Click to expand...
Click to collapse
Works for me. Flashed it perm and the first thing i did was do a backup. No issues thus far. About to flash Team Win's to see what its all about. But yeah, its working.
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Anon9mouz said:
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Click to expand...
Click to collapse
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
adb-toolkit shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-old
Click to expand...
Click to collapse
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Skip I just sent you a message regarding the radio pull CMD
mskip said:
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Click to expand...
Click to collapse
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Anon9mouz said:
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Click to expand...
Click to collapse
I think people just prefer using fastboot I know I certainly do.
Mark.
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
LAYGO said:
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
Click to expand...
Click to collapse
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
mskip said:
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
Click to expand...
Click to collapse
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
LAYGO said:
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
Click to expand...
Click to collapse
Plus one on no sd
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Will be doing this when I get home from work! I was glad I picked my GNex up yesterday...it was the only one my store received! So I was quite happy...can't wait for more support on the sprint side.
I couldn't wait, I rooted after lunch. Getting Swype installed, first thing, EVERY time. I needs my Swype!
Then to get some apps on there. Connection sucks at work though.
Can someone please pull the radio for the sprint galaxy nexus
I did a n00b mistake and restored a google factory image for VZW on my Sprint Galaxy Nexus...
Any help would be greatly appreciated!!!
I may have spoke so soon. I'm getting error 7 assert fail when flashing a twrp recovery zip. Is that an issue with the recovery on the toolkit or the zip. I flashed a teerom and kernel with no issues though.....
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Rabs_1976 said:
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Click to expand...
Click to collapse
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
wocko1 said:
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
Click to expand...
Click to collapse
BUMP
I have this Tablet as-well and having the same problem.
any ideas on the best way to root this thing?
wocko1 do you have any more details on how to got that far?
Thanks guys.
Rabs_1976 said:
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Click to expand...
Click to collapse
was it released in any other countries as another device?
even if we got root on it what can we do for a custom ROM if noone can dev for it
Madaz2 said:
was it released in any other countries as another device?
even if we got root on it what can we do for a custom ROM if noone can dev for it
Click to expand...
Click to collapse
We as owners/users of T-Hub 2 devices require sensible answers to important questions.
We need usb drivers for the T-Hub 2, either from Telstra or from Technicolor the manufacturer of the device so that we can attain " ROOT ACCESS" via a usb cable connection to a computer.
Unless we can get "ROOT ACCESS" we cannot move applications to an external SD card (32 GB in my case) or use Titanium Backup or certain Antivirus programs that require "ROOT ACCESS".
Please accept the undeniable fact that 1 Gigabyte of storage on the internal SD card is totally insufficient and pathetic, almost as pathetic as the fact that we are still stuck with "Gingerbread" which puts us three versions behind on Android which is now up to "JellyBean" v2.
The fact is, I believe the Android operating system running on the T-Hub 2 is, like all other versions of Android, based on the Linux kernel which is software using the GNU General Public License, which allows people to see, copy, use, and modify for their own needs.
If indeed I am correct in my assumption then Telstra/Technicolor could be in breach of a world standard which would mean that the proprietary blocks and gates that they have built to prevent access to the kernel on the T-Hub 2 are illegal.
Download Mode discovered...and more...
I thought this:
Hold "Volume-" and "Volume+" and "Power Button" boots into download mode. This is incorrect.
This gets you to recovery mode (which shows the Android robot fallen over).
Help!
wocko1 said:
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
Click to expand...
Click to collapse
Have been looking for the drivers everywhere, and so far none of them have worked. Even tried wireless adb to no avail. Also tried gingerbreak but still nothing. Sick of looking at the bloatware. Someone please help!
anyone had more success now that it has ICS 4.0.4
Yes, it can be rooted, but...
Hi,
Yes, much more progress. I've gained ADB root access using the restore method (i.e., restoring a backup which has been modified to install a file to a strange path, e.g,: ../../../system/bin/su), I recommend creating your own restore file rather than using one of the many out there and using it to install the necessary SU software to the appropriate locations.
If your device isn't detected by ADB, check that the device ID has been added to the ADB config file. The Thub2 ID is not recognised automatically. Also, when using fastboot remember to specify this ID or it won't find your THub.
The biggest issue with the THub2 is that Telstra have (in an oddly intelligent move) adopted SquashFS for the root file system; this is the FS used on things like linux liveCD's, and it's 100% RO (well, 99% RO . I have gotten around this in a number of ways. 1: I copied the SquashFS partition using DD to an Ext4 partition, then forced a dirty unmount of the SquashFS partiition chained to a mount of the new Ext4 partition to /system. RW access no problems, SU installs OK, but no persistence without forcing the dirty unmount each boot. 2: I copied the SquashFS partition to my ~ using DD, mounted and edited the partition, then re-flashed to the thub. worked much better, persistence across reboots, but dangerous and dodgy method that could risk many NANDs. 3: I cross-compiled a busybox containing UnionFS to Android.
Option 3 is by far the best option. UnionFS provides a transperent RW layer for SquashFS filesystems, writing the updates that couldn't be written to a RO system like squash to another partition (e.g., Ext4 on SD card). Mount a UnionFS system over /system to enable write access to the system. Maybe a better idea to mount it at /, but that raises other problems I couldn't be bothered dealing with.
I mentioned above that SquashFS is on 99% RO (in all my other experiences, it has been well and truly 100% RO, so this indicates something else a-going on that we should be able to use; I haven't looked into it yet.). For some reason, files installed to the Thub2 using the Restore method are persistent. Very useful, and should lead to a cleaner method.
So rooting so far:
Root with Restore method to install (1 & 2., SU bins, or 3., UnionFS Busybox)
Remount / as RW
-->Path 1 & 2
Dirty unmount /system && dirty unmount /system2 && mount /dev/block/etc.. NOTE: Once you dirty unmount /system, you will need to reference the location of the Ext4 partiition using the absolute (real) name of the device. You will also need to invoke busybox from a fully qualified path, eg. /data/local/tmp/busybox, as the internal /bin applications are no longer available (eg., mount).
-->Path 3
No need to umount /system, just mount the UnionFS system over the top.
Finally, for Paths 1 & 3...
Install Superuser application and be free!
So to sum up; I have easily rooted the Thub2 to root over ADB using a number of methods, however the Restore method works 100% of the time. I have mounted an Ext4 system to /system in order to have RW, but this isn't persistent. I have re-flashed the SquashFS with modified content, and this works a treat, but is RO and dangerous to NAND. I have mounted a UnionFS system over the SquashFS system, and this seems to provide the best all round performance.
I also wrote a short and nasty .apk to mount the UFS system without terminal, so that's a go as well.
Have fun pulling it all apart; I don't read these message boards, so I probably won't se any questions. More than enough to get rooted though.
THub Drivers and ADB Access
THUB 2 DRIVER INSTALLATION AND ADB ACCESS
This method sets out how to install drivers for the THub 2 and access ADB (Android Debug Bridge).
Access to ADB is the usual way that you use to Root an Android device.
Please note that not all ADB versions work. If you download and try a root method, you may have to copy the ADB.exe and support files across so that the root method can at least have a chance of working.
INSTALLING GOOGLE UNIVERSAL ANDROID DRIVERS
1. Ensure that Debugging has been enabled – Settings Developer options USB debugging and make sure the box is checked
2. The following is for Windows 7, other versions will be similar
3. Unzip the file and copy contents to a folder on the C: drive. I copied it to a folder I named THub
4. Plug the THub into your PC and it will try to find suitable drivers – some drivers may load and install but at least one will come up with “No driver found”
5. Open “Computer”
6. Click on “System properties”
7. Click on “Device Manager”
8. Under “Other devices” you will see T-Hub2 with an icon with a yellow exclamation mark.
9. Right-click the device and select "Update Driver"
10. Select "Browse my computer for driver software"
11. Select "Let me pick from a list of device drivers"
12. Click “Show All Devices”
13. Click “Have disk …”
14. Browse to where you put the extracted files
15. Select and open “Android_winusb.inf”
16. Select “Android Composite ADB Interface”
17. Click “Next” and then Click “Yes” (Ignore warning)
18. Wait until the software installs
19. You should now have Android Composite Interface” under the “Android Phone” listing
If you have problems, ensure Debugging is selected and try unplugging the THub and reconnecting it
ACCESSING ADB
1. Ensure that Debugging has been enabled – Settings Developer options USB debugging and make sure the box is checked
2. The following is for Windows 7, other versions will be similar, It also assumes that the file has been down loaded, unzipped and installed in a folder called THub on you C: drive
3. Connect the THub to your PC
4. Click in the “Start” icon, lower left icon on your PC Desktop
5. In the entry box type in “CMD” and push “Enter”
6. You will be at the “Command Prompt”
7. You need to navigate to the “THub” folder, the following are my entries, and yours should be similar.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Terry>cd .. and “Enter”
C:\Users>cd .. and “Enter”
C:\>
C:\>cd THub and “Enter”
C:\THub>
8. At the THub folder type in “ADB devices” and “Enter”
9. You should get an output similar to this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
01545CAB0B015004 device
C:\THub>
10. You now have ADB access
11. Try “adb shell” and “Enter” to enter ADB and then “ls” and “Enter” to get the THub Root folder listing
What next, I don’t know but at least we have ADB access?
I have been trying to copy system files to my SD card to have a look at them but have no success.
Does anyone know how?
Here is the site I uploaded the files to:
"You can fill in the missing bits"
xxx.mediafire.com/download/voku3wnuff5s2ef/THub.zip
NOTE: There is also a file called “UniversalAdbDriverSetup6.msi”.
I don’t know what it is for, but I installed it anyway. It MAY be necessary for the above method.
Firstly, I understand this is an old thread but quite a lot of us Australians have this THub 2 now because Telstra seem to basically be handing them out like shots at a party.
As far as I know this thing still has no root access. You can get into ADB with it without too much trouble.
But what I really want to know is how I can get root access with SuperSU so I can install something like AdAway to remove the seemingly ridiculous amount of advertisements that apps and etc. come with.
In addition to that, after installing just TWO small apps. It seems the device's internal memory is already full and it cannot install any more apps.. I need root access in order to run Apps2SD so I can move some apps to the SD card that I have purchased for it.
Does anyone, and I mean anyone have any ideas about how to root this thing? There has to be some Australian who has a rooted version with SuperSU running.
I tried 'towelroot' but the device just rebooted (meaning it failed) and then when I ran the .apk again it said that the device was unsupported.
It's one thing to be able to get access to the root partition (which is possible over ADB) but it's another to be able to run apps with root privileges.
For any information.
The specs are:
Manufacturer - Technicolor
Operating System - Ice Cream Sandwich 4.0.4
Processor - 1 GHz dual core
Screen - 7″ (1024 x 600 pixels)
Camera - 1.9 MP rear camera, 1.2 MP HD front camera
RAM - 1GB
Storage - 2 GB Internal with an expandable Micro SD card slot (1GB internal usable)
Battery - 6000 mAh (non-removable)
I know it's nothing amazing, but if I could root the device and change the DPI, remove advertisements and install a few hacks. I'd get so much more out of the device.
I picked it up in almost perfect condition second-hand off eBay for only $15. They're worth $360 AU brand-new.
If anyone has any information at all, please do post something. My apologies again for bumping a super old thread but otherwise I was going to just start my own.
Possible to restore system partition
Hi Guys,
I done goofed.
I killed my T-Hub by flashing a corrupted system partition and now the device wont boot and only displays the Telstra logo at the boot loader. I do have a backup of my system partition however I cant work out how I would perform the restore. The boot loader will not allow an ADB connection so no luck there.
Im thinking JTAG may be my only option. I have experience with this on other devices but i cant find the JTAG terminals on this thing? I must have tapped about 60 different combinations of testpoints now and have only been able to get console out of the radio module which is obviously no good for talking to the kernel.
Any help would be greatly appreciated.
Cheers,
Swamp
SwampCrack1210 said:
Hi Guys,
I done goofed.
I killed my T-Hub by flashing a corrupted system partition and now the device wont boot and only displays the Telstra logo at the boot loader. I do have a backup of my system partition however I cant work out how I would perform the restore. The boot loader will not allow an ADB connection so no luck there.
Im thinking JTAG may be my only option. I have experience with this on other devices but i cant find the JTAG terminals on this thing? I must have tapped about 60 different combinations of testpoints now and have only been able to get console out of the radio module which is obviously no good for talking to the kernel.
Any help would be greatly appreciated.
Cheers,
Swamp
Click to expand...
Click to collapse
I'm completely new to this. What ROM would i look for to install on the THUB if any? And if i could install it?
clearburn said:
I'm completely new to this. What ROM would i look for to install on the THUB if any? And if i could install it?
Click to expand...
Click to collapse
sorry but no one has developed a ROM for this device, there is no demand
Madaz2 said:
sorry but no one has developed a ROM for this device, there is no demand
Click to expand...
Click to collapse
Thanks. I thought there might have been a rom from the basic device that didn't have all of the Telstra stuff on it.
It is currently a brick
if you can root it then you could install Titanium backup and uninstall the bloatware off of it
Some moderate success
I have had some moderate advancements of late.
I can get temporary ADB root using the directory traversal exploit
.
While the above method gets you a root terminal session, as it screws with some settings the device is nearly unusable due to screen flicker and general lag. I guess the exploit breaks some settings. Does anyone know how to leave the exploit in place and restore the settings file to eliminate the flickering and lag?
I have been able to export the system partition, edit it (add su.bin and SuperUser.apk) then swap the system mount so the device uses my edited system partition as described by malleus. When I try to flash my partition the device reboots and is in a semi brick state (reboot loop, stuck on boot loader Telstra logo).
I was able to obtain the OTA update files by getting an old 2.3.7 device, rooting it then grabbing the OTA files using ADB once it had downloaded them. These OTA's can be flashed from an SD card (ext4 format) in 3e recovery. This was a good bit of progress as it means I can restore from a bricked state. If anyone needs them, the files I have are:
Product_4.0.4_3.38-FOTA
Product_4.0.4_3.48-FOTA
This is all new territory for me but i think I am getting close to achieving full, persistent root in 4.0.4.
Any help would be appreciated.
I would be very interested in your progress as I have one of these but in default state it is only usable as a phone on the DECT base.....
Having some useful apps running off an SD card would help no end (like multimedia remote for my home theatre system)
Cheers,
Alex B
SwampCrack1210 said:
I have had some moderate advancements of late.
I can get temporary ADB root using the directory traversal exploit
.
While the above method gets you a root terminal session, as it screws with some settings the device is nearly unusable due to screen flicker and general lag. I guess the exploit breaks some settings. Does anyone know how to leave the exploit in place and restore the settings file to eliminate the flickering and lag?
I have been able to export the system partition, edit it (add su.bin and SuperUser.apk) then swap the system mount so the device uses my edited system partition as described by malleus. When I try to flash my partition the device reboots and is in a semi brick state (reboot loop, stuck on boot loader Telstra logo).
I was able to obtain the OTA update files by getting an old 2.3.7 device, rooting it then grabbing the OTA files using ADB once it had downloaded them. These OTA's can be flashed from an SD card (ext4 format) in 3e recovery. This was a good bit of progress as it means I can restore from a bricked state. If anyone needs them, the files I have are:
Product_4.0.4_3.38-FOTA
Product_4.0.4_3.48-FOTA
This is all new territory for me but i think I am getting close to achieving full, persistent root in 4.0.4.
Any help would be appreciated.
Click to expand...
Click to collapse
Has anyone made any progress on this?
I have two of these tablets that have sat unused since I got them from Telstra. I really just want to update it to at least 4.1, but there's no official release from Telstra for the T-Hub, and I don't think there will be. Are ports entirely unfeasible?
Do you think I could contact Technicolor? What should I say?
P.S. there is a recovery mode, because I've booted into it.
hxxp://imgur.com/O0uq4Uk
How to unbrick your ouya as long as adb is on and you have a clockwork mod recovery installed
I bricked my ouya recently so i just thought i would share this,it's going to work even if you completely erased all data and all caches in your clockworkmod recovery,this includes erasing sd card and even if you have boot menu and it won't show your nand as green lit but red lit,the nand is the chip that has the firmware on it if your not sure what it is.
This is for xp but i think it will work in other windows versions but don't quote me?It took 48hrs of perseverance for me to figure this out, And then to write this, i had to flit from page to page online copying links and reading it all over again,some comes from memory,other bits of the tutorial i made up my self and sussed it out on my own with no help,i had to click rename and copy file names in places in this tutorial.But it works and it rebuilds the ouya no mater what you did.
You could have erase the memory in clockworkmod completely,even if you wiped the dalvick cache and/or thesd card patition at the same time and/or clicked full factory reset after, no matter what you erased or how you did it even if you used the whole lot of every erase option applied from clockworkmod recovery on your ouya,
This restores it to factory,it even removes the boot menu software that i added and found [email protected] up my ouya completely after trying to add a boot img for the cynagenmod i put on over the top of my system by accident, then killed all data caches erasing them all i even erased my sd card data leaving my ouya completely bare of anything.
This is for others like me that only have the OUYA? next to device in the device manager in windows xp,i had so much trouble getting it going and i found a very quick easy couple of click fix for it,i could then adb command the ouya over a micro usb cable and rebuild it,You need to have the adk bundle for windows installed and the sets of tools needed for the current platforms this maybe api's not sure? just have the ones i use which are 14,16,17,18,19 and the google usb driver you may not need them all i may have more than needed but i don't know so best use what i have as it works for me,i am not going in depth on adding this but you can look here https://devs.ouya.tv/developers/docs/setup for info on the sdk install procedure just get the platforms i have as well as the guides listed platforms to install you'll see a picture of the sdk on this page so just use that as a guide.
So on with the guide then:
STEPS
STEP 1.Turn on ouya and go into clocklworkmod recovery menu and select install from zip then select sideload adb option and leave the console running in this mode please.Go here http://visualgdb.com/UsbDriverTool/ copy and paste that link in a new tab into the address bar and head down the page a little to the bit that says Downloading click the link that says UsbDriverTool-sfx.exe,you then get a page asking to save the file so save it where you can remember.Leave the page open and move onto step 2.
STEP 2. Open a new tab in the browser and paste this link: http://visualgdb.com/tutorials/android/ouya/ into the address bar and hit enter (return key).Now connect the ouya to the pc via micro usb cable and follow step 2. and step 3. from the current webpage you are on.You should now have Ouya ADB device or similar in the device manager meaning it works now.
STEP 4.install powertoy for windows xp don't ask me for a link this is going to be something you have to do as can't remember,it allows command on right clicking a folder this is a much needed thing for this job.
STEP 3. open a new tab in the browser and go here http://forum.xda-developers.com/showthread.php?t=2266629 and download the file named 1.0.68-r1 Download Changelog click the orange changelog writing to download and copy the downloaded file called RC-OUYA-1.2.995-r1_ota.zip by opening c:/ adt-bundle-windows-x86-20140321 or simlarily named folder residing in c: drive and then go into sdk folder then go into platform tools folder and paste the RC-OUYA-1.2.995-r1_ota.zip file in there, return to the c: drive ,then go to the folder called adt-bundle-windows-x86-20140321 or similarily named folder againand then into sdk folder again then highlight the platform tools folder with right click and click on open command window here leave this window open now.
STEP 4. Provided the command window is now open and the ouya was correctly set and enabled from STEP 1 and STEP 2. earlier,and STEP 3.. is completed you should now have the ouya on micro usb with the adb mode enabled and showing up as such in device manager, and you should now be sitting in the clockworkmod recovery in adb sideload mode on your ouya console ,go to the command window you left open in STEP 3. and simply type adb sideload RC-OUYA-1.2.995-r1_ota.zip ,this should now install the zip and after it is done you reboot the console from restart option in clockworkmod recovery and you should boot up fine and will have successfully repaired (unbricked) the ouya.
JOB DONE PHEW!
PHYSC-1 said:
How to unbrick your ouya as long as adb is on and you have a clockwork mod recovery installed
I bricked my ouya recently so i just thought i would share this,it's going to work even if you completely erased all data and all caches in your clockworkmod recovery,this includes erasing sd card and even if you have boot menu and it won't show your nand as green lit but red lit,the nand is the chip that has the firmware on it if your not sure what it is.
This is for xp but i think it will work in other windows versions but don't quote me?It took 48hrs of perseverance for me to figure this out, And then to write this, i had to flit from page to page online copying links and reading it all over again,some comes from memory,other bits of the tutorial i made up my self and sussed it out on my own with no help,i had to click rename and copy file names in places in this tutorial.But it works and it rebuilds the ouya no mater what you did.
You could have erase the memory in clockworkmod completely,even if you wiped the dalvick cache and/or thesd card patition at the same time and/or clicked full factory reset after, no matter what you erased or how you did it even if you used the whole lot of every erase option applied from clockworkmod recovery on your ouya,
This restores it to factory,it even removes the boot menu software that i added and found [email protected] up my ouya completely after trying to add a boot img for the cynagenmod i put on over the top of my system by accident, then killed all data caches erasing them all i even erased my sd card data leaving my ouya completely bare of anything.
This is for others like me that only have the OUYA? next to device in the device manager in windows xp,i had so much trouble getting it going and i found a very quick easy couple of click fix for it,i could then adb command the ouya over a micro usb cable and rebuild it,You need to have the adk bundle for windows installed and the sets of tools needed for the current platforms this maybe api's not sure? just have the ones i use which are 14,16,17,18,19 and the google usb driver you may not need them all i may have more than needed but i don't know so best use what i have as it works for me,i am not going in depth on adding this but you can look here https://devs.ouya.tv/developers/docs/setup for info on the sdk install procedure just get the platforms i have as well as the guides listed platforms to install you'll see a picture of the sdk on this page so just use that as a guide.
So on with the guide then:
STEPS
STEP 1.Turn on ouya and go into clocklworkmod recovery menu and select install from zip then select sideload adb option and leave the console running in this mode please.Go here http://visualgdb.com/UsbDriverTool/ copy and paste that link in a new tab into the address bar and head down the page a little to the bit that says Downloading click the link that says UsbDriverTool-sfx.exe,you then get a page asking to save the file so save it where you can remember.Leave the page open and move onto step 2.
STEP 2. Open a new tab in the browser and paste this link: http://visualgdb.com/tutorials/android/ouya/ into the address bar and hit enter (return key).Now connect the ouya to the pc via micro usb cable and follow step 2. and step 3. from the current webpage you are on.You should now have Ouya ADB device or similar in the device manager meaning it works now.
STEP 4.install powertoy for windows xp don't ask me for a link this is going to be something you have to do as can't remember,it allows command on right clicking a folder this is a much needed thing for this job.
STEP 3. open a new tab in the browser and go here http://forum.xda-developers.com/showthread.php?t=2266629 and download the file named 1.0.68-r1 Download Changelog click the orange changelog writing to download and copy the downloaded file called RC-OUYA-1.2.995-r1_ota.zip by opening c:/ adt-bundle-windows-x86-20140321 or simlarily named folder residing in c: drive and then go into sdk folder then go into platform tools folder and paste the RC-OUYA-1.2.995-r1_ota.zip file in there, return to the c: drive ,then go to the folder called adt-bundle-windows-x86-20140321 or similarily named folder againand then into sdk folder again then highlight the platform tools folder with right click and click on open command window here leave this window open now.
STEP 4. Provided the command window is now open and the ouya was correctly set and enabled from STEP 1 and STEP 2. earlier,and STEP 3.. is completed you should now have the ouya on micro usb with the adb mode enabled and showing up as such in device manager, and you should now be sitting in the clockworkmod recovery in adb sideload mode on your ouya console ,go to the command window you left open in STEP 3. and simply type adb sideload RC-OUYA-1.2.995-r1_ota.zip ,this should now install the zip and after it is done you reboot the console from restart option in clockworkmod recovery and you should boot up fine and will have successfully repaired (unbricked) the ouya.
JOB DONE PHEW!
Click to expand...
Click to collapse
Quick follow up,you can sideload over adb if it's turned on,this applies to standard recovery as wel.So you can unbrick using the adb sideload method above even with a stock ouya to unbrick it guys/gals.