i've backuped, but when I tried to restore, the md5 was gone..
Is there anyway I can cheat on cwm or make a md5 ?
You can copy the file on your computer and use tools like MD5summer to create the MD5 file and then copy the *.md5 to your phone.
I dont know for which file I need to make the md5.. there is 7 files..(boot, cache, system.. etc)
the MD5 file looks like this one:
XXXXXXXXXXXXXXXXXXXXXXXXXXX boot.img
XXXXXXXXXXXXXXXXXXXXXXXXXXX cache.yaffs2.img
XXXXXXXXXXXXXXXXXXXXXXXXXXX data.yaffs2.img
XXXXXXXXXXXXXXXXXXXXXXXXXXX recovery.img
XXXXXXXXXXXXXXXXXXXXXXXXXXX sd-ext.ext3.tar
XXXXXXXXXXXXXXXXXXXXXXXXXXX system.yaffs2.img
XXXXXXXXXXXXXXXXXXXXXXXXXXX .android_secure.vfat.tar
you have to calculate the MD5 for each img or tar file and the replace xxxx with the obtained MD5
---------- Post added at 02:50 PM ---------- Previous post was at 02:48 PM ----------
forget to tell that:
you can save the above text using notpad in a file named nandroid.md5 and put it in your backup folder
From a terminal emulator
Code:
cd /sdcard/clockworkmod/backup/backupname
Where backupname is the name of your backup and this is the location of your backup.
Then:
Code:
md5sum *img > nandroid.md5
I would like to share a collection of factory images. It contains the full packages, also the extracted .img files. I also included insecure boot image (adb shell gives root access) and deodexed system image for each of them.
full image packages are "tgz" files.
image files extension is .img
isecure boot images are *.unsec.img
deodexed system images are *.deodex.img
These are all to be flashed with fastboot. These all derived from STOCK (https://developers.google.com/android/nexus/images) with no changes except the insecure adb boot image and the deodexed system image.
Deodexed fs is exactly the same size as the original when mounted.
The collection contains:
mantaray_4.2-jop40c
mantaray_4.2-jop40c-factory-0d641789.tgz size: 326396069
mantaray-jop40c
image-mantaray-jop40c.zip size: 328044861
boot.img size: 4716544
boot.img.unsec.img size: 4716544
bootloader-manta-mantalj12.img size: 1310720
cache.img size: 10617136
recovery.img size: 5228544
system.img size: 541540212
system.img.deodex.img size: 499677904
mantaray_4.2.2-jdq39
mantaray-jdq39-factory-d79f489e.tgz size: 328019721
mantaray-jdq39
image-mantaray-jdq39.zip size: 329787974
boot.img size: 4718592
boot.img.unsec.img size: 4718592
bootloader-manta-mantalj12.img size: 1310720
cache.img size: 10621244
recovery.img size: 5230592
system.img size: 535248732
system.img.deodex.img size: 496339676
userdata.img size: 140778452
The files can be downloaded from: http://web.djodjo.org/?a=download:android:ROM_images:factory_images_gn_mantaray
if it helps you buy me a beer
there it is another collection of factory images. It contains the full packages, also the extracted .img files. I also included insecure boot image (adb shell gives root access) and deodexed system image for each of them.
full image packages are "tgz" files.
image files extension is .img
isecure boot images are *.unsec.img
deodexed system images are *.deodex.img
These are all to be flashed with fastboot. These all derived from STOCK (https://developers.google.com/android/nexus/images) with no changes except the insecure adb boot image and the deodexed system image.
Deodexed fs is exactly the same size as the original when mounted.
The collection contains:
mysid_4.0.4-imm76k
mysid_4.0.4-imm76k-factory-98d21321.tgz size: 201267095
mysid-imm76k
image-mysid-imm76k.zip size: 196838841
boot.img size: 4247552
boot.img.unsec.img size: 4247552
bootloader-toro-primela03.img size: 2363392
radio-cdma-toro-i515.fc04.img size: 3811968
radio-toro-i515.fc05.img size: 10748160
recovery.img size: 4587520
system.img size: 331943172
system.img.deodex.img size: 303179956
userdata.img size: 142534492
mysid_4.1.1-jro03o
mysid_4.1.1-jro03o-factory-f17426e6.tgz size: 250399358
mysid-jro03o
image-mysid-jro03o.zip size: 246331897
boot.img size: 4470784
boot.img.unsec.img size: 4470784
bootloader-toro-primelc03.img size: 2363392
radio-cdma-toro-i515.ff02.img size: 3813648
radio-toro-i515.fg02.img size: 10748160
recovery.img size: 4820992
system.img size: 413806488
system.img.deodex.img size: 374348532
userdata.img size: 142534492
The files can be downloaded from: http://web.djodjo.org/?a=download:android:ROM_images:factory_images_gn_toro
enjoy
So if the .tgz of 4.1.1 is flashed in fastboot, I will retain my root and custom recovery? All I need is the .tgz, right?
No.
The tgz package contains images(img) another zip file that contains more images and batch/shell scripts. You can download those separately if you wish.
If you unpackage this tgz and run "flash-all.bat/sh" you will have completely fresh factory setup, as if you just bought it. You will loose all the data, except the one on the sd card.
the script basically flashes the following:
fastboot flash bootloader bootloader-toro-primelc03.img
fastboot flash radio radio-toro-i515.fg02.img
fastboot flash radio-cdma radio-cdma-toro-i515.ff02.img
fastboot -w update image-mysid-jro03o.zip
the last one flashes:
boot.img
recovery.img
system.img
userdata.img
to retain your recovery you can delete "recovery.img" from the zip. Then after you flash the STOCK ROM you have to disable stock recovery from coming back (because it will overwrite the custom one on boot) from your custom recovery or otherwise(some options here: http://andwise.net/?p=292 )
The root(su) you have to do it again, you cannot keep that if you flash the new system.img.
RyanTX said:
So if the .tgz of 4.1.1 is flashed in fastboot, I will retain my root and custom recovery? All I need is the .tgz, right?
Click to expand...
Click to collapse
there it is another collection of factory images. It contains the full packages, also the extracted .img files. I also included insecure boot image (adb shell gives root access) and deodexed system image for each of them.
full image packages are "tgz" files.
image files extension is .img
isecure boot images are *.unsec.img
deodexed system images are *.deodex.img
These are all to be flashed with fastboot. These all derived from STOCK (https://developers.google.com/android/nexus/images) with no changes except the insecure adb boot image and the deodexed system image.
Deodexed fs is exactly the same size as the original when mounted.
The collection contains:
mysidspr_4.1.1-fh05
mysidspr_4.1.1-fh05-factory-8cb5208b.tgz size: 294108599
mysidspr-fh05
image-mysidspr-fh05.zip size: 290459409
boot.img size: 4861952
boot.img.unsec.img size: 4861952
bootloader-toroplus-primelc03.img size: 2363392
radio-cdma-toroplus-l700.fc12.img size: 3802016
radio-toroplus-l700.fc12.img size: 10748160
recovery.img size: 5212160
system.img size: 466894948
system.img.deodex.img size: 448302352
userdata.img size: 142534492
The files can be downloaded from: http://web.djodjo.org/?a=download:android:ROM_images:factory_images_gn_toroplus
enjoy
required:
!!!! YOU MUST KNOW WHAT YOU DO DO, BECAUSE YOU RISK TO BRICK YOUR SHIELD !!!!
Nvidia Shield 2017 PRO (Model numbre P2571) - Kernel 4.9.140-tegra, build foster_e_hdd et version 8.0.1
Very good cable USB -> MicroUSB, connect to PC USB3 -> Micro USB SHIELD TV PRO (500GB)
the shield is uptodate (last 8.0.1 ) - version bootloader: 32.00.2019.29-t210-352664f9 - production mode: fused
To start:
on your pc (Linux Distro) need ADB and FASTBOOT.
Debian buster: apt install fastboot android-tools-fastboot adb (add qemu and arm64 architecture if your are on PC x86_64 plateform)
Put shield in dev environment (go parameters of shield android interface), connect USB cable to PC to Shield first.
PREFERENCES -> ABOUT -> BUILD click until nvidia display you are in developper mode now.
after allow USB connection do not forget to allow your PC to manage shield (Mac address appears valid always allow this PC)
PREFERENCES -> DEV OPTIONS -> DEBUG USB (Allow)
From your PC :
sudo adb devices - > you must have now :
List of devices attached
0424X................c device
sudo adb reboot bootloader (go bootloader)
you must OEM unlock your shield ( ATTENTION ALL DATA WILL BE DESTROY) and need wait 2 HOURS.
sudo fastboot oem unlock ( I REPEAT ALL YOUR DATA WILL BE LOST)
When OEM UNLOCK is running, go developer.nvidia.com/gameworksdownload
download:
NVIDIA SHIELD ANDROID TV Pro Developer Only OS Image - 8.0.1 - 2019/11/27
you download: nv-recovery-image-shield-atv-pro-8.0.1-dev_rooted.zip
downloaded you unzip: sudo unzip nv-recovery-image-shield-atv-pro-8.0.1-dev_rooted.zip
nv-recovery-image-shield-atv-pro-8.0.1-dev_rooted - 11 files, 2,1Gb
android-info.txt recovery.img blob system.img boot.img tegra210-foster-e-hdd-cpc-p2530-0933-e03-00.dtb flash-all.bat tegra210-foster-e-hdd-p2530-0932-e02-00.dtb flash-all.sh vendor.img flash-base.sh
After oem is unlock rebbot shield in bootloader mode.
then
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
nothing error, only success ?
then fastboot reboot
the shield initialise new environment, follow instructions...
when shield is restarted in android environnement and developper mode must be/is active.
sudo adb shell -> foster:/ $ su
foster:/ # ls -l
total 2120
dr-xr-xr-x 21 root root 0 2020-02-15 09:30 acct
lrw-r--r-- 1 root root 11 2019-10-07 09:58 bin -> /system/bin
lrw-r--r-- 1 root root 50 2019-10-07 09:58 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
drwxrwx--- 7 system cache 4096 2020-02-09 18:34 cache
lrw-r--r-- 1 root root 13 2019-10-07 09:58 charger -> /sbin/charger
drwxr-xr-x 5 root root 0 1970-01-01 01:00 config
lrw-r--r-- 1 root root 17 2019-10-07 09:58 d -> /sys/kernel/debug
drwxrwx--x 38 system system 4096 2000-01-01 02:01 data
lrw------- 1 root root 23 2019-10-07 09:58 default.prop -> system/etc/prop.default
drwxr-xr-x 18 root root 2660 2020-02-15 09:31 dev
lrw-r--r-- 1 root root 11 2019-10-07 09:58 etc -> /system/etc
-rwxr-x--- 1 root root 2079664 2019-10-07 09:48 init
-rwxr-x--- 1 root root 1064 2019-10-07 09:45 init.environ.rc
-rwxr-x--- 1 root root 334 2019-10-07 09:47 init.qvs.rc
-rwxr-x--- 1 root root 29632 2019-10-07 09:45 init.rc
-rwxr-x--- 1 root root 7690 2019-10-07 09:45 init.usb.configfs.rc
-rwxr-x--- 1 root root 6149 2019-10-07 09:45 init.usb.rc
-rwxr-x--- 1 root root 511 2019-10-07 09:45 init.zygote32.rc
-rwxr-x--- 1 root root 875 2019-10-07 09:45 init.zygote64_32.rc
drwx------ 2 root root 16384 2019-10-07 09:58 lost+found
drwxr-xr-x 12 root system 260 2020-02-15 09:30 mnt
drwxr-xr-x 2 root root 4096 2019-10-07 09:45 odm
drwxr-xr-x 2 root root 4096 2019-10-07 09:45 oem
dr-xr-xr-x 327 root root 0 1970-01-01 01:00 proc
lrw-r--r-- 1 root root 15 2019-10-07 09:58 product -> /system/product
drwxr-x--- 2 root root 4096 2019-10-07 09:48 sbin
lrw-r--r-- 1 root root 21 2019-10-07 09:58 sdcard -> /storage/self/primary
drwxr-xr-x 4 root root 80 2020-02-15 09:31 storage
dr-xr-xr-x 12 root root 0 2020-02-15 09:30 sys
drwxr-xr-x 16 root root 4096 2019-10-07 09:58 system
-rw-r--r-- 1 root root 5272 2019-10-07 09:45 ueventd.rc
drwxr-xr-x 14 root root 4096 2019-10-07 09:47 vendor
end of PART 1.
What is this suppose to be? So far all you've done is show instructions to install the normal dev os firmware via fastboot?
elliwigy said:
What is this suppose to be? So far all you've done is show instructions to install the normal dev os firmware via fastboot?
Click to expand...
Click to collapse
yes, must install dev ROOTED firmware first. and after install Gnu/Debian Buster. i will finish second post.
bst regards
AldoReset said:
yes, must install dev ROOTED firmware first. and after install Gnu/Debian Buster. i will finish second post.
bst regards
Click to expand...
Click to collapse
Lol.. u dont seem to understand my previous post.. I was asking what this is even for since all u did in the OP was tell ppl how to install the dev firmware which is useless information as nvidia already provides the instructions and even provides scripts to automate this...
It's been a few weeks and u still havent posted "part 2" whatever that is...
elliwigy said:
nvidia already provides the instructions and even provides scripts to automate this...
Click to expand...
Click to collapse
Would you mind linking what you see? I was able to find access to the dev rooted file for my shield on Nvidia website, but it lacked quality instructions. Hence, coming back to xda, old faithful.
Care to shine a light in the right direction mate?
Okay, this is what I see for instructions for my Shield Pro running marshmellow or higher (I omitted directions for 6.0 or lower):
I think this is the way forward for me.
*******************************************************************************
SHIELD RECOVERY IMAGE FLASHING INSTRUCTIONS
*******************************************************************************
To follow the instructions in this guide, you require the "adb" and "fastboot
utilities. These tools are provided as part of the Android SDK:
- http://developer.android.com/sdk/index.html
To setup the tools, follow one of Google's guides:
- http://developer.android.com/tools/help/adb.html#Enabling
- https://developers.google.com/cast/docs/android_tv#adb-usb
If you are running Windows and the standard Google adb USB driver does not
detect the SHIELD device, you can use NVIDIA's driver:
- https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
*******************************************************************************
ENTERING FASTBOOT MODE
*****
To begin, connect your SHIELD via USB to the PC where you downloaded this recovery image.
- Insert a USB OTG cable and connect the other end to the host PC
- Setup adb using one of the guides above
Next, put your SHIELD into fastboot mode using one of the following methods:
Software Method:
- Boot the into Android
- Connect the device to the host PC
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" at the prompt
Hardware Method:
- Disconnect power cable
- Connect power cable to SHIELD
- As soon as the green LED turns on -BUT NOT BEFORE- hold down the power button
- Count to three, then immediately release the power button
- i.e. one-one thousand, two-one thousand, three-one thousand.. LIFT!
- You should now see the fastboot menu on the screen.
- If the standard boot process starts, disconnect the power cable and repeat
the process increasing the count in the previous step to 4.
NOTE: You should leave the HDMI TV connected to SHIELD at all times.
*******************************************************************************
FASTBOOT MENU NAVIGATION
*****
Once in fastboot mode, navigate the menus using the power button.
- Single tap the power button to move between menu items
- Hold down the power button for 4 seconds and release to select a menu item
*******************************************************************************
UNLOCKING THE BOOTLOADER
*****
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following command on the host PC:
- fastboot oem unlock
That command triggers a new page on the device headed '!!! READ THE FOLLOWING !!!'
- Read the warning on the screen
- To unlock the bootloader, select 'Confirm'
WARNING: Unlocking the bootloader securely formats the user data partition. This
process PERMANENTLY DELETES all data such as photos, music and downloads that
have previously been stored on the device.
NOTE: On the SHIELD Android TV Pro (500GB unit), the unlock process WILL take
around two hours (ie 120 minutes) due to the large size of the hard drive. This
is a security precaution and cannot be avoided.
*******************************************************************************
FLASHING THE DEVICE
*****
To flash the recovery image to your SHIELD, download and unpack the recovery
image package. From the unpack directory, execute the commands below for your
particular upgrade path.
If this is the first time you have done this procedure, you must unlock the
bootloader (see above step).
*****
* SHIELD UNITS WITH ANDROID MARSHMALLOW OR NEWER
*
If you are CERTAIN that your SHIELD device OS is currently running Android
Marshmallow or newer (i.e. the Android version is 6.0 or greater), follow
these intructions:
*** Prerequisites:
1. Ensure that the bootloader is unlocked (see above step)
*** Flashing instructions:
1. Execute these commands on the host PC:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Click to expand...
Click to collapse