[GUIDE] UNLOCK - ROOT - RETURN TO STOCK and/ or UNBRICK your Nexus 7 3G “Nakasig- Tilapia” v4.2.2
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -
Requirements:
1. You must have the sdk (ADT Bundle for Win) installed on your Pc and you are able to access, and use adb and fastboot.
NOTE: Notice the install location. This defaults to C:\Users\<user name>\AppData\Local\Android\android-sdk the platform tools (adb, fastboot) and usb drivers will be downloaded to this location. This will be referred to from here on as your sdk directory
But in case you haven't install all SDK, you can use only fastboot by the easy way.(Go here if you want to use the easy way to fastboot)
2. You must have ticked USB Debugging mode in your Nexus 7 3G
3 You must download and install - USB DRIVERS r_06 for Windows 7 & 8
4. Download one of both root-tool
CF- Auto-Root by Chainfire - Download link for Version Tilapia - Nakasig
or the Superboot r4 by Paul O’Brien - Actually I'm not sure if Superboot is functionnal for version 4.2.2 - I tested with my Grouper v4.2.2 and I stayed in Google screen with bootloop.
5. Download your recovery special for your Tilapia - Nakasig
CWM (Touch version or not)
TWRP - latest versions
ClockworkMod - Google Nexus 7 (GSM) - Superuser (fixed) for Android 4.2.
and rename your select with the name of the recovery image you chose to download.
6. The factory image for the Nexus 7 3G => 4.2.2 (JDQ39) - nakasig-jdq39-factory-0798439d.tgz - md5: ee8db1ed6ff1c007fe12136d4bc65cd8- size: 279.9MB - The Version Zip if you prefer
Click to expand...
Click to collapse
AND DON'T FORGET THAN IT'S BETTER FOR YOUR SPECIAL N7 3G+
TO USE THE SPECIAL RECOVERIES "TILAPIA - NAKASIG"
and NOT "GROUPER" WHICH ARE DIFFERENTS
Click to expand...
Click to collapse
**********************************************************************************************************************************************************************
Pre-Steps
To make this easier,
1 - you should put the root-tool.zip selected on the folder “fastboot” (if you use the easy way - Goto post #2)
2 – You should put the recovery.img selected on the folder “fastboot”
UNLOCK YOUR NEXUS 7 3G+
Click to expand...
Click to collapse
To unlock your device, you must go to your bootloader. To do that, you have possibilities;
1. Turn your device on while pressing volume down
or
1. Connect your device and go to cmd terminal
Code:
> cd \Users\<user name>\AppData\Local\Android\android-sdk\platform-tools (it's common localization for an auto install)
> adb devices
# the following output should be returned
List of devices attached
<device serial number> device
2. Boot to the bootloader by use adb
Code:
adb reboot bootloader
or
2 Bis. Boot to the bootloader by use fastboot
Code:
fastboot reboot-bootloader
3. Unlock your device* by
Code:
fastboot oem unlock
*You will have to accept and erase all of your data on the tablet.
You are unlocked :good:
By Fastboot only easy way - Unlock you device
Code:
C:\Users\Username>cd c:\fastboot
Code:
c:\fastboot>fastboot oem unlock
**********************************************************************************************************************************************************************
FLASH THE RECOVERY
Click to expand...
Click to collapse
You can choose one of both recoveries - CWM or TWRP
Flash ClockworkMod Recovery as Permanent recovery
Click to expand...
Click to collapse
(You're still inside the bootloader and connected through the usb cable)
1. Flash CWM especially for your N7 3G
Code:
fastboot flash recovery recovery-name of your recovery.img
To make CWM Permanent recovery
2. Boot into recovery by pressing “volume up” and when the menu says ‘recovery mode’ press the power button
3. Go to “Mounts and Storage” menu
4. select “mount system”
5. Type in cmd terminal
Code:
adb shell
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
exit
If you having trouble gaining shell, try
Code:
adb kill-server
then
Code:
adb start-server
. And restart the lines command above
* For some people, it has been reported that you don't have to replace recovery-from-boot.bak. The flash is enough to make the recovery stick.
**********************************************************************************************************************************************************************
Flash TWRP as Permanent recovery
Click to expand...
Click to collapse
(You're still inside the bootloader and connected through the usb cable)
1. Flash TWRP especially for your N7 3G
Code:
fastboot flash recovery recovery-twrp-tilapia-2.4.4.0.img
To make TWRP Permanent recovery
2. Boot into recovery by pressing “volume up” and when the menu says ‘recovery mode’ press the power button
3. Go to “Mounts and Storage” menu
4. select “mount system”
5. Type in cmd terminal
Code:
adb shell
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
exit
**********************************************************************************************************************************************************************
FOR THE ROOT
Click to expand...
Click to collapse
- [2013.02.20][N7 WiFi | N7 3G] CF-Auto-Root
Click to expand...
Click to collapse
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file (you will see - 2 folders=> images & tools and 3 files: root-windows // root-mac // root-linux)
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
Code:
Run root-windows.bat
- Linux
Code:
chmod +x root-linux.sh
Code:
Run root-linux.sh
- Mac OS X
Code:
chmod +x root-mac.sh
Code:
Run root-mac.sh
- [ROOT] Superboot - Nexus 7 WiFi / 3G root solution
Click to expand...
Click to collapse
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files,
and type
Code:
chmod +x superboot-mac.sh
followed by
Code:
./superboot-mac.sh
- LINUX - Open a terminal window to the directory containing the files,
and type
Code:
chmod +x superboot-linux.sh
followed by
Code:
./superboot-linux.sh
**********************************************************************************************************************************************************************
RETURN TO STOCK and/or UNBRICK your N7 3G+
Click to expand...
Click to collapse
Before you begin, please make sure you have ADB and Fastboot drivers installed and working.
1. Download the factory image for the Nexus 7 3G=> 4.2.2 (JDQ39) - nakasig-jdq39-factory-0798439d.tgz - md5: ee8db1ed6ff1c007fe12136d4bc65cd8- size: 279.9MB - The Version Zip if you prefer
2. Extract the factory image into the same directory as your ADB and Fastboot executables (e.g. "\android-sdk\platform-tools")
3. Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type:
Code:
adb reboot bootloader
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
4. Type:
Code:
fastboot flash bootloader bootloader-tilapia-4.18.img
5. Type:
Code:
fastboot reboot-bootloader
6. Now type:
Code:
fastboot -w update image-nakasig-jdq39.zip
7. Optional: If you would like to relock your bootloader for warranty or security purposes, make sure you are in your bootloader screen again and type:
Code:
fastboot oem lock
8. If your tablet hasn't already rebooted automatically, you can type
Code:
fastboot reboot
Well done. You should now be back on stock Android 4.2.2
**************************************************************************************************************************************************************************************
These root tools are actually the easy way for rooting your device, so you can use them without problems.
IF YOU NEED MORE ABOUT THE NEXUS 7 3G+ "NAKASIG - TILAPIA" YOU MUST GO HERE
=> [Index]- 29 Dec 2012 - All for NEXUS 7 - "Nakasig/Tilapia" - (GSM/HSPA+)
and
=> NEXUS 7 3G-"nakasig"-For all Your Jelly Bean Discussions, Problems and Solutions
Click to expand...
Click to collapse
For my part I’ve used
the easy way by my fastboot guide for unlock my device,
Adb lines command for flash TWRP as permanent recovery,
Thanks for @mateorod, @Chainfire, @paulobrien and all members who helps for the development about the Nexus 7 3G+
The EASY WAY TO USE FASTBOOT LINES COMMAND
HELP FOR FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Reserved in case
Hello, this is my first post on xda.
When i tried use "adb fastboot bootloader" cmd say to me : no device. Where is problem?
piski93 said:
Hello, this is my first post on xda.
When i tried use "adb fastboot bootloader" cmd say to me : no device. Where is problem?
Click to expand...
Click to collapse
Try the easy way on first
Use the post 2.
You can use it for all the install, except for for the permanent recovery where you will have to use ADB line command.
The best you can do, it's to use fastboot easy way and when you have finished, you learn and install correctly your sdk and check all your parameters. And when you will be ready you will be able to use adb lines command easily to install your recovery in a permanent way.
It's too long for a course about sdk, the best you can do it's to to search and read. Go to my index, and read the General guides
Gonna try this later today. Though something is a bit fishy. When I use adb from the fastboot.zip it can't find my device but from the platform-tools dir it seems to work fine. Are they different versions? How big risk is it to brick the device while unlocking/rooting and installing recovery? Pls tell me its unbrickable. cheers
Skickat från min GT-I9300 via Tapatalk 2
znejk said:
Gonna try this later today. Though something is a bit fishy. When I use adb from the fastboot.zip it can't find my device but from the platform-tools dir it seems to work fine. Are they different versions? How big risk is it to brick the device while unlocking/rooting and installing recovery? Pls tell me its unbrickable. cheers
Click to expand...
Click to collapse
I can't says it's unbrickable !!!
The differences between these versions is:
If you use sdk/platform tools it's the more complete install and the easy way for fastboot, that just if you need to use fastboot line command, but it's not more complete for using with adb lines command.
If you go to the post 2, you will see all the lines command for fastboot.
If your sdk install is correct, you can use it without problems.
The easy way by fastboot is just a shotcut
philos64 said:
I can't says it's unbrickable !!!
The differences between these versions is:
If you use sdk/platform tools it's the more complete install and the easy way for fastboot, that just if you need to use fastboot line command, but it's not more complete for using with adb lines command.
If you go to the post 2, you will see all the lines command for fastboot.
If your sdk install is correct, you can use it without problems.
The easy way by fastboot is just a shotcut
Click to expand...
Click to collapse
I tried and everything seemed to work fine ... i Unlocked/flashed twrp then "mv recovery-from-boot.p recovery-from-boot.bak" didnt work cause it couldnt find the file... :/ i continued and flashed superboot and it seemed to work fine. Downloaded latest cm and gapps rebooted inte recovery and flashed them. Now I only have bootloop with cm10.1...
I know it aint bricked cause I think I can get into bootloader.
Edit: After a factory reset it worked! :>
znejk said:
How big risk is it to brick the device while unlocking/rooting and installing recovery? Pls tell me its unbrickable. cheers
Click to expand...
Click to collapse
The Nexus7 is very difficult to brick. It still is possible, but as far as I know there is only one way to do it - remove or destroy the bootloader.
Under normal circumstances, the only time you do anything with the bootloader is unlocking/locking it, which simply does a minor modification. That's perfectly fine. And the normal custom-recovery/root process doesn't touch it, so that's fine too. Doing system updates (even legit OTA ones) might upgrade the bootloader, as might flashing custom roms. But as long as you don't interrupt the process during that critical step, it should be OK.
So outside of erasing the bootloader or flashing a completely incompatible bootloader and rebooting, your N7 should be safe.
adb command line Linux support
Hi All,
Am new to this forum and also to my newly bought N73G. So I am unsure about the complete process though explained step by step. One thing that i wanted to confirm was Does ADT Bundle for linux work the same as that of windows? Cause I run the same on my PC; these command line instructions would they work the same way on Linux terminal?
It's not the same as Windows. You can download the ADT Bundle for Linux.
Sent from my N7 3G between sky and earth
Is there any solution for unlock and root Nexus 7 3G only with Apple Mac assistance? Thank you in advance!!!
foxstam said:
Is there any solution for unlock and root Nexus 7 3G only with Apple Mac assistance? Thank you in advance!!!
Click to expand...
Click to collapse
Can you explain what do you think by Apple Mac Assistance ?
If it's for SDK Tools, you will find here the Apple version => DOWNLOAD FOR OTHER PLATFORMS
I'm not sure which recovery images should be downloaded.
Is this one correct? - recovery-twrp-tilapia-2.3.2.1.img
what does this mean? "rename your select with the name of the recovery image you chose to download."
quote:
Requirements:
...
4. Download:
CWM (Touch version or not) or TWRP and rename your select with the name of the recovery image you chose to download.
thanks
elelab said:
I'm not sure which recovery images should be downloaded.
Is this one correct? - recovery-twrp-tilapia-2.3.2.1.img
what does this mean? "rename your select with the name of the recovery image you chose to download."
Requirements:
4. Download:
CWM (Touch version or not) or TWRP and rename your select with the name of the recovery image you chose to download.
Click to expand...
Click to collapse
Yes, you can use the recovery-twrp-tilapia-2.3.2.1.img without problem
and when I writes "rename your select with the name of the recovery image you chose to download", I mean that you can rename the IMG file by "recovery" simply. It's more faster.
minimum steps to root Nexus7(3G) - for beginners
confused by too much info. on how to root Nexus 7
can this be as simple as:
1 unlock
2 root
question:
1. unlock step - erase all of your data on the tablet
If I don't care my data (I just bought it), after unlocking, can Nexus start as normal?
2. Why do we need flash the recovery?
"Pre-Steps
To make this easier,
1 - ...
2 – You should put the recovery.img selected on the folder “fastboot” (if you use the easy way - Goto post #2)
" fastboot flash recovery recovery-twrp-tilapia-2.3.2.1.img"
does "recovery-twrp-tilapia-2.3.2.1.img" mean the "recovery.img"?
thanks
elelab said:
confused by too much info. on how to root Nexus 7
can this be as simple as:
1 unlock
2 root
question:
1. unlock step - erase all of your data on the tablet
If I don't care my data (I just bought it), after unlocking, can Nexus start as normal?
2. Why do we need flash the recovery?
Click to expand...
Click to collapse
Answers:
1 - Yes, the advert is clear, all of your data will be erased !
2 - If you want to flash a rom custom, you need a recovery
elelab said:
"Pre-Steps
To make this easier,
1 - ...
2 – You should put the recovery.img selected on the folder “fastboot” (if you use the easy way - Goto post #2)
" fastboot flash recovery recovery-twrp-tilapia-2.3.2.1.img"
does "recovery-twrp-tilapia-2.3.2.1.img" mean the "recovery.img"?
Click to expand...
Click to collapse
Yes, it's correct. it's more faster to write: "recovery.img" than "recovery-twrp-tilapia-2.3.2.1.img".
It's the same file, just rename.
This has no effect on the recovery flash
Can I root my device (4.2.2) using Superboot yet ?
Re: [GUIDE] - Updated 08 Feb - Unlock and Root a Nexus7 3G “Nakasig- Tilapia”
I received 4.2.2 update today. I haven't installed it for fear of losing root. Should i repeat the procedure to root again after updating my n7. Will i again loose my data? Or the bootloader will remain unlocked? Please help
Sent from my Nexus 7 using xda app-developers app
sukhjit_bhullar said:
I received 4.2.2 update today. I haven't installed it for fear of losing root. Should i repeat the procedure to root again after updating my n7. Will i again loose my data? Or the bootloader will remain unlocked? Please help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can flash UPDATE-SuperSU-v1.04.zip in CWM/TWRP recovery to get root after update from 4.2.1
You will not loose any data.
Your bootloader will upgrade to 4.18 and still unlocked.
I am doing R&D on FOTA(Firmware Update Over the Air) using Nexus 7-Wifi(grouper). For which I followed the following steps.
1. Downloaded the android source from source.android.com for v 4.2.2_r1 and v 4.3_r1
2. Downloaded the binaries for grouper, extract it to my source folder.
3. Then I compiled the source code using following commands.
i. source build/envsetup.sh
ii. lunch full_grouper-userdebug
iii. make -j8 dist
4. After few tries, I had success in compiling the source for Nexus 7(grouper).
5. I got following files in $out/source_4.2.2/dist folder
-----------------------------------------------
adb*
android-common-carousel.jar
android-common.jar
android-info.txt
android-support-v13.jar
android-support-v4.jar
android-support-v7-gridlayout.jar
build.prop
com.android.nfc_extras.jar
fastboot*
full_grouper-apps-eng.root.zip
full_grouper-emulator-eng.root.zip
full_grouper-img-eng.root.zip
full_grouper-ota-eng.root.zip
full_grouper-symbols-eng.root.zip
full_grouper-target_files-eng.root.zip
gpl_source.tgz
guava.jar
installed-files.txt
jsr305.jar
mkbootfs*
mkbootimg*
mkyaffs2image*
mp4parser.jar
package-stats.txt
ramdisk.img
signapk.jar
vendor_owner_info.txt
-----------------------------------------------
6. Then I generated my own keys using /development/tools/make_key tool for media, testkey, releasekey, shared, platform.
Assume my keys are locate at /keys folder.
7. Then I created a signed target zip file using following command.
/source/build/tools/releasetools/sign_target_files_apks -v -p ../host/linux-x86 -d /keys full_grouper-target_files-eng.root.zip signed_target_files.zip
8. From signed target zip file I create
/source/build/tools/releasetools/img_from_target_files -v -p ../host/linux-x86 signed_target_files.zip signed_img_from_target_files.zip
9. Then I flashed the signed_img_from_target_files.zip using fastboot command using the following script:
----------------------------------------------------------------------
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
sleep 10
fastboot -w update signed_img_from_target_files.zip
----------------------------------------------------------------------
10. The device gets flashed well and is working, but I am getting an log while flashing in which it is unable to find boot.sig, system.sig and recovery.sig
11. Now the otacerts.zip file contains a testkey which is not the one that I signed it with.
file located at "/system/etc/security/otacerts.zip" on device.
12. Now since the otacerts.zip is signed with the default key it gives a mismatch error which I tried to flash an OTA update which is signed by the my custom key.
Now my doubt is:
How can I add boot.sig, recovery.sig and system.sig to signed_img_from_target_files.zip?
Is there anything I am doing wrong?
Does the recovery checks the current ROM keys from "/system/etc/security/otacerts.zip"?
What is the correct procedure to sign the OTA update?
Late answer
I know that it's dead thread but may be somebody tries to solve this problem: you should use
Code:
-o or --replace_ota_keys
flag with
Code:
sign_target_files_apks
Hello all,
I haven't really seen any options for restoring our Nexus 7's using Linux and terminal commands....
SO I made one!
This guide is the simplest I could make it and it only uses a few commands to get your Nexus 7 back up and running in the event of a brick or loss of data.
AS long as you have access to the Bootloader option of the device, this tool should work.
INSTRUCTIONS
1.Make sure that you have ADB and Fastboot installed
Open Terminal (CTRL+ALT+T)
Just type what's in the quotation marks, do not include the marks
Type "sudo apt-get update"
Type "sudo apt-get install android-tools-adb android-tools-fastboot"
2. While in Terminal, browse to location of downloaded files (boot.img , system.img)
ex. Type something like "cd ~/Downloads/NexusRestore"
3. Connect your Nexus 7 to your computer with USB cable and make sure that the device is in bootloader mode
HINT: type "fastboot devices" and it should show a set of random characters and then the word "Fastboot" to the right
4. Type these commands to restore your device to a stock rooted Jellybean ROM
fastboot devices
fastboot flash system system.img
fastboot flash recovery recovery.img (ONLY use this if you DO NOT want to kep your original recovery or if you lost it due to your situation)
fastboot flash boot boot.img
fastboot -w
fastboot reboot
5. Profit
You may now go back to recovery and flash the ROM of your choice or do whatever your heart desires
DOWNLOADS
Dev-Host: http://d-h.st/KaZ
Extract the ZIP file and work from that directory.
Happy Restoring!! Let me know if you have any questions or need more Help :laugh:
Not to be nit picky but the instructions you gave are for Debian based distros (most likely Ubuntu/Mint- since android-tools are a backport in Debian Wheezy), IMHO it would be better to specify that this is a Ubuntu/Mint (Debian) Guide, since other distros use different package managers.
Once you have android tools installed there is an easier method.
Download factory image, extract the tar archive, run flash-all.sh
(optionally edit flash-all and remove the -w switch to preserve user data)
oldsoldier2003 said:
Not to be nit picky but the instructions you gave are for Debian based distros (most likely Ubuntu/Mint- since android-tools are a backport in Debian Wheezy), IMHO it would be better to specify that this is a Ubuntu/Mint (Debian) Guide, since other distros use different package managers.
Once you have android tools installed there is an easier method.
Download factory image, extract the tar archive, run flash-all.sh
(optionally edit flash-all and remove the -w switch to preserve user data)
Click to expand...
Click to collapse
I appreciate the info, I've only ever used Ubuntu Linux and every method that I had found so far was super in depth and not exactly simple. I've been doing this stuff for a while, so it's no big deal for me, but I wanted to provide something for people who don't do this kind of stuff every day. Just trying to contribute to the "cause" i guess. lol
Good tutorial
Help
Zesty01 said:
Hello all,
I haven't really seen any options for restoring our Nexus 7's using Linux and terminal commands....
SO I made one!
This guide is the simplest I could make it and it only uses a few commands to get your Nexus 7 back up and running in the event of a brick or loss of data.
AS long as you have access to the Bootloader option of the device, this tool should work.
INSTRUCTIONS
1.Make sure that you have ADB and Fastboot installed
Open Terminal (CTRL+ALT+T)
Just type what's in the quotation marks, do not include the marks
Type "sudo apt-get update"
Type "sudo apt-get install android-tools-adb android-tools-fastboot"
2. While in Terminal, browse to location of downloaded files (boot.img , system.img)
ex. Type something like "cd ~/Downloads/NexusRestore"
3. Connect your Nexus 7 to your computer with USB cable and make sure that the device is in bootloader mode
HINT: type "fastboot devices" and it should show a set of random characters and then the word "Fastboot" to the right
4. Type these commands to restore your device to a stock rooted Jellybean ROM
fastboot devices
fastboot flash system system.img
fastboot flash recovery recovery.img (ONLY use this if you DO NOT want to kep your original recovery or if you lost it due to your situation)
fastboot flash boot boot.img
fastboot -w
fastboot reboot
5. Profit
You may now go back to recovery and flash the ROM of your choice or do whatever your heart desires
DOWNLOADS
Dev-Host: http://d-h.st/KaZ
Extract the ZIP file and work from that directory.
Happy Restoring!! Let me know if you have any questions or need more Help :laugh:
Click to expand...
Click to collapse
First link in "Dowload" is dead !
Thanks for this simple tuto !
In introduction of your thread, you can put this link : http://developer.android.com/tools/device.html
Basically, this is a copy-paste thread from this thread.
THIS GUIDE IS FOR LINUX (AND OS X ?) ONLY! Windows version here
Download file here: https://mega.nz/#!wooAGJYA!Hr7VUkPRt1Xx9QxaRSIX-r7u9R8OtBhcpb8W5FdwHS8
Open a terminal (Ctrl + Alt + T) and go to your "~/Downloads" directory (or basically where you download your files):
Code:
cd ~/Downloads
Now, unzip the archive you just download:
Code:
unzip FixOOS3-TWRP.zip
You should now have a folder called "FixOOS3-TWRP". Go into this folder with "cd" command :
Code:
cd FixOOS3-TWRP.zip
Get sudo access (script won't run if not in root):
Code:
sudo -s
and then:
Code:
./fixoos.sh
.
The script will flash all necessary files to your device, and after 3 seconds. it will automatically reboot onto new TWRP.
From this TWRP you'll be able to flash newest CM 13 ROMs and OOS 3.x.x.
If there is no ROMs present on your phone, you can still push it with (be sure to stay in the current directory to use "./adb") :
Code:
./adb push <name_of_the_ROM>.zip /location/on/the/device/
of you can sideload it:
Code:
./adb sideload <name_of_the_ROM>.zip
(Be sure to be in "sideload mode" in TWRP).
For more pictures, check out original thread by @djsubterrain : fastboot outputs are pretty much the same, beside the fact that you are on Windows and Linux.
Extracting ramdisk image to change fstab.tenderloin to make system read and write allowing permanent root access using any ROM ever created for the HP Touchpad.
I am using Ubuntu 18.04.1 LTS 64-bit (All the software is open source and free, you can get the packages necessary for your distro)
Create a folder in /home (root) name it hpboot ( on the PC ) all work is done on the PC.
Open the custom ROM zip file and extract boot.img to the created directory hpboot
Open Terminal in the hpboot directory, all the commands needs to be enter there.
Text beginning with –>># are for information only. Do not paste into the Linux terminal window.
–>># The following will extract images from boot.img file located in the hpboot direcory.
–>># Copy and paste each individual line in the Terminal window one by one and wait until each command finish processing.
dumpimage -i boot.img kernel.uImage
dumpimage -i boot.img -p 1 ram
dd if=ram of=ramdisk.img.gz bs=64 skip=1
gunzip ramdisk.img.gz
mkdir ramdisk; cd ramdisk
cpio -i < ../ramdisk.img
–>>#The ramdisk files are uncompress in the hpboot/ramdisk directory
–>>#Open file fstab.tenderloin using (text editor) change mnt_flags of/system ext4 from ro to rw
–>>#Look like this when change from (ro ) read only to ( rw ) read and write.
–>>#<src> <mnt_point> <type> <mnt_flags and options>
–>>#/dev/store/cm-system /system ext4 rw,errors=panic
–>># Save and close the fstab.tenderloin file
–>># The next 3 steps will repack the files into the ramdisk and merge Kernel to create the finish boot image.
find . | cpio --create --format=’newc’ | gzip > ../ramdiskRW.img
cd ~/hpboot
mkimage -A arm -O linux -T ramdisk -C none -a 0x00000000 -n “TENDERLOIN RW SYSTEM RAMDISK” -d ./ramdiskRW.img ./ramdisk.uImage
mkimage -A arm -T multi -C none -n “Tenderloin RW System” -d kernel.uImage:ramdisk.uImage uImage.Android_RW
–>>#Boot the touchpad into TWRP, connect to PC, copy uImage.Android_RW to the external Micro SDCard.
–>>#Select MOUNT and touch Boot, go back, touch Advanced, File Manager, touch external_sd, select uImage.Android_RW, touch Copy File, touch boot, touch select Current Folder.
–>>#You should have free space on your boot for both images. At the boot screen you will have the option of Android (with no permanet ROOT access) and Android_RW (RW System), you need to install SuperSu. You can use any of the two options or delete uImage.Android and then rename uImage.Android_RW to uImage.Android for one boot option.
You do not need to re flash the ROM, you can add this boot file and use it with your current installed working ROM.
The process works for all boot.img created for the HP Touchpad. If you have a ROM and would like to have system read and write access then you can do this.
Hopefully a Linux Guru will create a script for this, which will automate the process to 3 seconds!
I like tinkering with my TP but I am running @Windows 7 on a 32 bit.. any suggestions?
Android is base on Linux OS.
Install vmware player and run ubuntu as a virtual machine, both are free.
--SNIP--
Hopefully a Linux Guru will create a script for this, which will automate the process to 3 seconds!
Click to expand...
Click to collapse
Here's a shell script that automates the process (rename the extension from .txt to .sh). Put the script and boot image file in any directory and type
Code:
./rwcreate.sh
If it doesn't execute, it probably needs its permissions changed.. Right click the file you created, select 'properties'. In the properties window, select "Permissions" and check "allow executing as ..." or type
Code:
chmod +x rwcreate.sh
in a terminal window
Thanks for your help and dedicating your time to make it easier for others.
I made suggestion to the script on correcting an error, on DU forum.
Now is just a click to get it done, but if we were in a perfect computer world, it could be even easier as to connect the HP Touchpad to PC using USB.
Then run the script and everything is complete!
Using adb pull command to get (boot.uImage) from hp boot directory, to PC.
Changes are done as per script.
adb push command new boot.uImage to hp boot directory, all done!
But making it easier, will make it more complicated and having to install more software and confusing!
HP_TOUCHPAD said:
Thanks for your help and dedicating your time to make it easier for others.
I made suggestion to the script on correcting an error, on DU forum.
Now is just a click to get it done, but if we were in a perfect computer world, it could be even easier as to connect the HP Touchpad to PC using USB.
Then run the script and everything is complete!
Using adb pull command to get (boot.uImage) from hp boot directory, to PC.
Changes are done as per script.
adb push command new boot.uImage to hp boot directory, all done!
But making it easier, will make it more complicated and having to install more software and confusing!
Click to expand...
Click to collapse
Done. Thanks.
shumash said:
Done. Thanks.
Click to expand...
Click to collapse
The script on this forum is correct, but in the DU the file was wrong, corrected now.
Thanks for the fix and help!