[DEAD PROJECT] beta project closed

[aus9]

Hi

this takes over any discussion started in a nvram Linux script from here
[Only registered and activated users can see links Click here to register]

Firstly I have a failed test of this script.
so let me explain.

The beta script, based on the nvram script attempts to either extract your current recovery.img from your Android device or (NOT TESTED) installs a recovery image.

Trying to be smart, I already know I can use mobileuncle on my mediatek device without any Windows stuff....to install either CWM or my precious TWRP

I just ran the script in extract mode, and ran a md5sum against the resultant image and compared it to my original PC file version.

Its NOT a match.

This means this project is on the back burner until I work how where I went wrong.

Here is the mis-match

Code:

md5sum /a/1build/1ANDROID/1ROMS-STUFF/twrp-recovery/recovery.img
560a3936b1f7ca3673feb14cd3b11e15  /a/1build/1ANDROID/1ROMS-STUFF/twrp-recovery/recovery.img

md5sum /a/1build/1recovery/recovery.img
9c1e240b8af103a2ad9fbb836be4019a  /a/1build/1recovery/recovery.img

#### CHECK SIZE
-rw-r--r--  1 gordon gordon 6285312 Jun 20  2013 recovery.img
-rw-r--r--  1 gordon gordon 6291456 May  9 17:01 recovery.img

they are both 6 Megs and running strings against both show strings value are the same at top and the end.

EDIT.....script removed as it was wrong

cheers


If anyone can spot my error let me know, its a doozy to add you to credits

---

ok so I ran strings against both recovery images but called one file a and the b
then I ran a graphical diff program against both

verdict.....press N to go to next change claims there is none. hmmmm



I might take a risk later. but will retest after injecting CWM onto phone.

##############
EDIT
used mobileuncle to flash CWM onto phone

extracted image = recovery.img while original I call cwm.img gives

Code:

gordon@box:~/Downloads$ md5sum *
09ace826ad1f8934d4fa0a3785a18562  cwm.img
2602a502d6209cffd29b0426d27969b6  recovery.img
gordon@box:~/Downloads$ ls -al
total 11916
drwxr-xr-x  2 gordon gordon    4096 May  9 20:58 .
drwx------ 25 gordon gordon    4096 May  9 20:26 ..
-rw-r--r--  1 gordon gordon 5900288 Apr 11 07:32 cwm.img
-rw-r--r--  1 gordon gordon 6291456 May  9 20:56 recovery.img

recovery is bigger .....not tested strings as its getting late....but I seem to have a value or error on input issue

###############

AAAAH I just noticed something

something is good

Each extracted image is the same size as the other extracted image.......I tested CWM would boot up and it does
maybe I have it correct all along?

Maybe this shows my lack of Android skills?

Each image has to fit into those hex values as defined, so some recovery images are smaller but still work.

If I am right, when I try to flash TWRP back onto my phone tomorrow, using the script .....I won't brick

legs and arms crossed of course.

[aus9]

This project is now dead. I have made a nice mistake and got a wonderful boot loop no matter whether I try factory/meta/recovery/normal

[aus9]

This project restarts as my new phone has 2 recovery images so I will able to tell if I can install one over the other.

I will attempt this over the weekend.

first post script link removed I will use a non-interactive script to keep movie short, if I don't brick it

EDIT
I have split off all my root testing stuff into a separate script or tutorial here
[Only registered and activated users can see links Click here to register]

[vampirefo]

2 recovery? your phone has two different recoveries, post dumchar_info

[aus9]

vampirefo
my bad communication skill

what I meant was needrom now has 2 available recovery ROMs for me to play with. I am aware we can only have only one flashed.

b) I have successfully flashed both onto my phone at various times using mobileuncle.

c) I may have done more bad things to that phone so appreciate your help but I may have bricked it more.

also.....but mildly related.....I have added a photo test for true root. My new device had a faulty su APK which meant IMHO that prompt was not changing to root@phonename prompt

I did not keep any notes on whether I had the same scenario for the bricked phone.

I am not asking for help to unbrick it........BTW....I accept my punishment for being a naughty boy on a learning curve for Android........grins sheepishly

cheers

[aus9]

Modest update to myself mainly

Instead of tidying up this post and putting out a tutorial, I have just tested a hard drive install of a tiny Linux distro which uses udev (rough Windows translation= USB drivers for most Android devices are good).
edit
nope taking too much time have stopped this project

[aus9]

due to some recent posts by Window users, I have restarted a look at using Linux but not here
but constructing a tutorial using an existing live cd.

Takes longer to get the packages but at least I don't have to maintain them
---upload the source
---comply with licenses etc

Tutorial will evolve but in my puny mind.....it may help some with clone Andoid devices
or struggle with Flashtool instructions

Notes to myself mainly