[Tutorial] backup nvram or flash a new recovery etc

[aus9]

THIS IS NOW OBSOLETE DUE TO THE WONDERFUL CTR V 2.5 FROM CARLIV
see
[Only registered and activated users can see links Click here to register]


I assume you are a Windows PC user. Try at own risk. Please read or skim read all my links except distrowatch.

Credits
vampirefo for adb and dumchar_info and great advice
snowdream for his udev rule
chainfire for his abdb insecure playstore app
roberts @ tinycorelinux.net for his root id test

Reasons to use include:
A) The Windows USB driver can not be found, maybe a clone
B) You are not quick enough to associate the Windows driver
c) The Flashtool instructions fail for your device.

Why Linux?
[Only registered and activated users can see links Click here to register]

Android Preparation
Go into system settings --> Developer Options -> Tick or turn on----USB debugging mode. If you fail to do this, adb command won't work correctly!

Which Windows user are you?
First we need to separate you into 3 main camps

Camp 1 = no working cd/dvd burner or no optical drive. You need to use Windows to image Linux onto an USB stick or install Linux into a virtual machine running on your PC ---not discussed further otherwise this becomes a novel. You can google the answer if you like.

If you lack a burner and optical drive works you could loan a library Linux mag that comes with a cd/dvd or buy one and see if the cd/dvd boots up

Camp 2 = W8 or UEFI enabled with secure boot on. You need to find out if your motherboard will boot an UEFI aware Linux distro. Trouble is, I don't own UEFI bios. You need a 64 bit recent Linux live cd or dvd. Google to see if its UEFI aware please.

Camp 3 = Windows users with UEFI already turned off or an old bios
From now on I will assume you are in Camp 3. With a working burner.

INSTRUCTIONS
Please read all the instructions before starting anything.

1) Find out how to burn an iso image in your version of Windows
google it if not sure. I suggest you buy an dvdrw or cdrw ---depending on size, so if you make a mistake, you don't turn the cd/dvd into a coaster.

eg W7 users may try


2) Download a live Linux cd or dvd. There is lots to choose from. Please choose a debian/Ubuntu/LinuxMint or derived from Debian ---I don't want to show every package management system from the others.

distro=a distribution of Gnu/Linux also known as Linux

So download any you like or if not fussed try this 64 bit distro about 511 Mb
[Only registered and activated users can see links Click here to register]

Its system requirements like RAM and video card are shown here
[Only registered and activated users can see links Click here to register]&func=display&sid=39
click on Download mirrors left hand pane if you wish to download from another country or choose KDE which is much larger download.

You may notice my iso download suggestion says amd64 and you may have an intel processor, such as me, its just a name tag. Remember if size of iso is greater than 700 Mb then use a dvd blank please.

Do NOT install this distro please. I want you to consider using only as a live cd.
I use debian sid on my internal hard drive but I don't have time to explain
why you should choose other Linux distros. Its safe to use as a live cd. All factors being equal.

3) Change your bios boot order to boot up the live cd or dvd. Check your motherboard how to do this. Some modern PC have a bios splash screen which tells you which button or button combinations to push.

eg my ECS mobo ---press the delete key.........---my old Dell mobo --press the F2 key.

4) When Linux boots up
(4) What kind of root (superuser) does your Linux use?
[Only registered and activated users can see links Click here to register]

(5) Can you see your Andoid device?
Use the Linux menu to open a web browser and view this file ----or Windows users and their browser
[Only registered and activated users can see links Click here to register]

Clones not found according to my eyesight. If you can see your device, then jump to step (6) please

If you can not see your device, then we need to show you how to make up a rule
that Linux can use.

5a) Plug your USB data cable into PC and Android.
5b) On Android enable USB storage thru the notifications menu.
5c) Some Linux distros will automatically mount your SD card
and internal storage......while others have a pop box asking you what to do.

mount = make readable a certain device in Linux speak.

For this part of the instructions press cancel if asked to mount your Android device. If you see no popup...don't worry it about....it won't affect the instructions.
5d) In Linux, open a terminal and use what ever method above to get root,
probably sudo su

Code:

sudo su
tail -n 15 /var/log/messages

---> you will get 15 lines of a log.
Do not close the terminal we will use it again shortly.

5e) Now we look at those 15 lines and hope to find a line that will show a different
device to mine (iOcean) but we are looking for the id of the Vendor = maker id
For example one of my output lines is this:
Jun 25 17:22:31 box kernel: usb 3-7: New USB device found, idVendor=0bb4, idProduct=0c03
so we know manufacturer id = 0bb4

5f) Now open a text file in Linux, you may find more than one.
It defaults to a new page. Copy and paste this into the text editor

#iocean
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="666", GROUP="plugdev"

# symbols indicate nothing on that line is to be actioned by the operating system
---just like Andoid.

Now you change 0bb4 to "something" where something is to the right of idVendor from our command above. The 666 means, when active, that the local user or non-root can use Linux commands to interact with their Android device.

This is different from Flashtool instructions so do not try to mix up my instructions with whatever you read in the past please!

Now click on file, save as.....just like MS word etc and save the file to your home folder as 55-android.rules

Filename is case sensitive, meaning do not use capitals please.

BUT your file will have a formula like this

#myphone name
SUBSYSTEM=="usb", ATTRS{idVendor}=="string-found-from-commnd", MODE="666", GROUP="plugdev"

If you want to add a second phone you need to follow the same discovery process and edit the same file.

5g) Now back to terminal. It should have opened to the live cd's default home user account ----which is /home/somename. AND you have saved a file under that local name. Lets check with a list command which is "ls" without the quotes

Code:

ls
---> results should include 55-android.rules
(now we do command, copy and paste this to make it easier)
cp 55-android.rules /etc/udev/rules.d/

5h)

Code:

chmod 644 /etc/udev/rules.d/55-android.rules

5i) Ubuntu/LinuxMint users need to refresh this new rule by

Code:

service udev restart

Debian users try

Code:

udevadm control --reload-rules

Other users try

Code:

systemctl restart udev

Let me know if either method fails as your distro may be using some other service management system. Now leap to (7)....do not reboot.

(6) Your device was showing in link
If this section confuses you, use the manual method in section (5).

6a) Now a download of a zipped package
[Only registered and activated users can see links Click here to register]

unzip under Windows, or the super quick way under Linux is
a) open terminal
b) run command

Code:

unzip pack.zip

Here is LinuxMint action in image

It will be the same fast result in Ubuntu or Debian.

There are a heap of graphical unzippers in Linux but they are slower to use,
if interested here is one in the link
[Only registered and activated users can see links Click here to register]

After unpack, contents are:
55-android.rules (modified from the 51-android link)
license to re-distribute the 51-android link
and three scripts: --root-checks --nvram --recovery
Which are discussed in Tutorial later.

6b) Now follow the root commands as shown in 5g then 5h and one of the commands ----from 5i to refresh the new rule.

### If you have got to here, well done.
Ideally you now have a Linux USB rule that should work with your device.

7) Now to get the latest adb command
Live cd/dvd are by their nature out-of-date. So we need to update
our package manager.....in Android terms that means sync.
Then we can download the adb command which is in a Linux package.

Code:

apt-get update
apt-get install android-tools-adb

This might take a while.

8 USB stick and internal drive discussion
[Only registered and activated users can see links Click here to register]

To keep it simple I suggest you have your recovery image on a fat32 USB stick. And use root powers to save your nvram backups to the same fat32 stick,
then copy to Windows and cloud storage.

[aus9]

Next we check to see what kind of Android you have. Mine came rooted but the system was read only and the kernel was secure mode locked.

Why all the testing?
Anyone can take a copy of something. At that point you have a backup of something. But, if you can not truly overwrite a part of the flash device with your backup, or someone's files etc.......only testing will reveal the truth.

abdb insecure which is an app from playstore allowed me to break the secure mode setting. YMMV To run the check, open a terminal and run the command

Code:

sh root-checks.sh

Do not run this as root. You may need to run it more than once, depending on your error conditions. Each exit from script should tell you why it exitted. I suggest you read the next link which is the proof I have tested this script for good and bad results. YMMV

Images of good result and errors now a link
[Only registered and activated users can see links Click here to register]

[aus9]

nvram backup
First we need to backup our existing nvram, the command to run as non-root is

Code:

sh nvram.sh backup

Note that your hex value may differ from mine. If yours is not showing in my script output then use the converter please
[Only registered and activated users can see links Click here to register]

Below image shows its safer to copy and paste. How?
Use your mouse if PC to highlight the correct value, go to the input area and press down on the wheel button.....or press down both the left and right mouse buttons. But I can not be sure you got it correct and you may have input it manually.


Therefore I give you first chance to get tell me you got it right.


Then one last chance to bork or exit script. And the backup starts


The action continues but no images supplied. Finally we have the end of backup


If you wish to see what happened then you could do this


However, the most important thing to do is now put in your fat32 USB stick and use root powers to move those files onto your storage media.

As I don't know what distro you are using, open your file manager as non-root and click on help.....then click on "about" and it tells you the name of the app.
Then in the terminal you have open get root file manager by either

Code:

sudo su  (or su and password)
pcmanfm (or name of file manager)

Now copy the entire folder = data and the file nvram.bin to your backup media.
Then copy again to your Windows PC and I suggest cloud mode as well.

To give you a idea that your backup may be successful or not
my size of nvram.bin is 5 Mb
my size of data folder is 4 Mb on disk, that is the full uncompressed size

So they easily fit onto USB stick

If you are struggling on how to use or how to find your file manager, I urge you to upload your files to cloud storage.

Start a new thread on your issue in this sub-forum and we will try to help.

(trivia) As I used my real hard drive for images, I did the script under folder=Downloads to hide all my other stuff

[aus9]

nvram restore

Please take as much care as possible in reading this tutorial page. Restoring a bad backup is just as bad as not following the script instructions. I took as much care as I could but it is still up to you to be alert.
The command to run is

Code:

sh nvram.sh restore

Its restore assuming you have a backup. Its restore even if you have no backup and are using some trusted files from a person with your exact make and model.

Below image shows a test for 2 errors, script checks for the actual source files that you backed up earlier.


Next image actually contains TWO TESTS. I passed the first test of matching byte size and md5 sums and then we check for second line. In my output.....which may differ from yours, we are talking about this line

-rw-rw-rw- root root 5242880 2014-06-29 15:48 nvram.bin

The script attempted to write to Android and we need rw rw root root .....sound familar?
Yes we are talking about a root-check test. I can not shout loud enough this is important......as a number of Windows users may refuse to do the root test and so I still had to test it here.

The next image is almost the same as the backup input screen where you see your hex value and input a decimal number which happens to be the same number you used in the backup.


Now the flashing begins


But this time I show more of the end of the flashing


###########
If you also turned on USB storage, now eject the media in Linux before doing a full reboot and test your phone please.

good luck

[aus9]

Get your dumchar info first
Before we start on recovery, we need to discuss the decimal size of your Android flash device reserved for the recovery image.

I can not assume you have just completed the the nvram script so lets do this manually on your Linux PC (live or installed)

Code:

adb kill-server
adb start-server
adb devices -l  (if result is your device then we do next line)
adb shell cat /proc/dumchar_info > dumchar.txt

I suggest you now upload a copy of that file directly into cloud storage. Lets have a look at mine, even though mine is not a clone.
[Only registered and activated users can see links Click here to register]
That is difficult to read so we need just the recovery line

Code:

cat dumchar.txt | grep recovery

Your result may differ from mine
recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0

Now we take YOUR first hex value and convert it to decimal using the online converter.

But we know we can view the contents of the nvram script which has some values already converted.....they are:

Code:

Here are some outputs
hex value             value to be input

0x0000000000100000.........1048576
0x0000000000200000.........2097152
0x0000000000300000.........3145728
0x0000000000400000.........4194304
0x0000000000500000.........5242880
0x0000000000600000.........6291456
0x0000000000700000.........7340032
0x0000000000800000.........8388608
0x0000000000900000.........9437184
0x0000000000A00000........10485760

A=10, B etc up to F=15

so my size converts to 6291456

This means what ever recovery image you download off the internet must NOT exceed YOUR byte size. You have been warned!

Now I was able to find 2 for my device and I use the

Code:

ls -al

command in each download folder to get the byte size
-----> gives me
-rw-r--r-- 1 gordon gordon 6035456 Jan 30 15:17 recovery.img
-rw-r--r-- 1 gordon gordon 5746688 May 22 14:03 recovery.img

How did I get those dates?
I downloaded various recoveries from needrom.com that tend to come in zip format or sometimes in rar format. The decompressed file reveals the creation date.

OK so also use root powers to put a copy of that dumchar.txt onto your USB stick please. And save to cloud mode please.

Now go and search for recovery images for your make and model that when unzipped do not exceed your byte size please.

[aus9]

Flash a new recovery onto to your device
Ok the script also has an option to backup your existing recovery.img
Here, I assume you arrived here not interested in backups and so we attempt to place an known to work image onto your device using Linux. but if you want to backup see link
[Only registered and activated users can see links Click here to register]

The command to run is

Code:

sh recovery.sh flash

I changed to word to flash instead of nvram's restore to focus your mind that this is dangerous and may brick your phone.

First an error image


Lets start with below image


Lets move on to some input


PAY ATTENTION to what you are inputting. My scripts are simple and will take your input as face value. You must input a decimal number and if you input a larger than correct number you risk bricking device. OK it might be retrievable but less likely if you can't use Windows Flashtools.

Finally some more tests, but again I assume you have true root. I have not included the test for you to exit unless you can see
rw rw root root /system/recovery.img

I hope by now, after the nvram checks, your choices or decisions is clear? If unsure you do not proceed.

Start a new thread in this sub-forum with
make and model of device
the download page for your recovery.img
Whether you had any true root errors
Whether you had any nvram errors
If possible screen images of the terminal or most Linux distros offer screenshots
---I prefer screenshots but will take photos movies etc.

I don't claim to solve or resolve anything. The license exempts me, but we can at least have a look?


Now the next bit is just as important as all the other bits.

You have an Android booted up. You have just flashed a replacement recovery.img onto it. It is possible, while adb is running to use a command to reboot into recovery. I prefer you don't.

In playing around, I take more risks as I am not an Android developer. (equals stupid as well heh heh) But playstore app mobileuncle allowed me to flash a "wrong" recovery. mobileuncle allows you to reboot into recovery
-----and when it failed for wrong recovery......my phone did a full reboot.

mobileuncle is available from the playstore but may not install on your device.
It expects to find a Mediatek CPU chipset.

I am hoping the same will happen to you.

Its also possible by removing the battery and then doing a normal reboot you can still get into normal boot up. But Mobileuncle seems to automate it?

good luck!