• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [CLOSED]root A75

Status
Not open for further replies.
ninadchaudhari

ninadchaudhari

What's up !
Here is how i see it !



PLZ PROCEED TO THIS THREAD FOR FURTHER DEVELOPMENT


any ways like many other developments this way does not support those Windows systems use Linux or Mac ( tested on OS X Lion)

1.) extract the system.img from the zip of mmx
now we are unpacking system.img
2.) got to unyaffs - unyaffs is a program to extract files from a yaffs image - Google Project Hosting
3.) in download section , download all three "unyaffs", "unyaffs.c", and "unyaffs.h"

4.) put them a folder ( i use a75/projects/root )
5.) type ( in terminal )
Code: 
cd path/to/ur/directory
6.) type :
Code: 
 type gcc -o unyaffs unyaffs.c
7.) once it's done doing it's thing, type
Code: 
 sudo chmod +x /complete/directory/path/to/unyaffs
8.)
Code: 
cd /complete/drectory/path/to/unyaffs
9.) keep th system.img in the same directory then
Code: 
./unyaffs system.img
10.) download the superuser zip and binary then paste the contents in /app and /bin as in that zip


Questions for experts



1.) now there is a file if you notice in the zip : installed-files.txt
what are these nos. before the apps !
attached the same txt file i think that is just useless !
2.) :( any one try any way to repack . i know way to pack the boot.img and have doe it many times successfully but this is system.img ... .
3.) approach correct ?
4.) confirm on Ubuntu ...

SECOND WAY -- BETTER FOR NOW !
contact a dev i will recommend this dev he has created many recoveries !!!! : also he gives a amazing guide just pm that dev many times !!! more just provide the images from the zip to him !! : http://androidforums.com/getitnowmarketing/339920-how-submit-new-device-recovery-creation.html#post2728057

this dev is also very responsive and will certainly help more over he has done many recoveries : note he builds a custom recovery not CWM but even that recovery is equally good and same except the hat icon ;)
 
kumar abhishek said:
I am not able to extract that in my windows 7. Tried unyaffs.exe 32bit but error comes img extract failed
Click to expand...

oh i never knew that there exists unyaffs32.exe also :)
well for that i think just instead of using cd always use the full location path may be that helps ! else i am clue less for i have not tried it on windows but works charm on lion
but btw if there exists unyaffs.exe also it will be there for win also !!
 
ninadchaudhari said:
oh i never knew that there exists unyaffs32.exe also :)
well for that i think just instead of using cd always use the full location path may be that helps ! else i am clue less for i have not tried it on windows but works charm on lion
but btw if there exists unyaffs.exe also it will be there for win also !!
Click to expand...


It reaches the location but the error is about extraction failed
 
I think this must THEORETICALLY root your device...

NOTE : due to my exams i did not devote time for this but now just logged in got reference of mkfs tool from XDA-DEVELOPERS some thread like how to create a yaffs2 something ...

look its 5:45 and i hav'nt slept ...
i am uploading the rooted system.img but its 5:45 and i need to sleep now + it is like 200 mb
i do not know when it was 5 like today :(


so it very simple
for n00bs just flash the system.img i am providing
from fastboot system system.img
or use the same zip given by mmx replace rooted system in it and then flash.

exerts:
i have decompiled the system.img then pushed su , busybox binaries
given apt permissions and then rebuild

the only thing i think i should not have done is : i have copied the su binaries at system.bin and system.xbin so that must not create probs ... that has also increased the size of your img by 22kb :p if any one cares lol

i will update the link tomorrow like after 1 or 2 pm ( when i will wake up )
for those in hurry just use the instructions in my first post and then use mkfs.yaffs2 from internet in linux( i used backtrack) give permissions of 667 to mkfs.yaffs2 and excute like
[NOTE FOR THIS TOOL SEARCH ON XDA i got it from there :p I THOUGHT THAT THAT TOOL WILL HELP IN MY PROJECT ..]
Code: 
 mkfs.yaffs2 decompile/ system.img

NOTE: i am Indian hence have that general tendency of playing safe handed !
if you cannot boot the system for more than 15 mins just extract the mmx zip and flash it !! :)
 
ninadchaudhari said:
yup that is why i deleted it !!!
after noticing boot.img has no ramdisk ROFL!!! :D
amazing boot.img !!
Click to expand...
I think this must THEORETICALLY root your device...

NOTE : due to my exams i did not devote time for this but now just logged in got reference of mkfs tool from XDA-DEVELOPERS some thread like how to create a yaffs2 something ...

look its 5:45 and i hav'nt slept ...
i am uploading the rooted system.img but its 5:45 and i need to sleep now + it is like 200 mb
i do not know when it was 5 like today


so it very simple
for n00bs just flash the system.img i am providing
from fastboot system system.img
or use the same zip given by mmx replace rooted system in it and then flash.

exerts:
i have decompiled the system.img then pushed su , busybox binaries
given apt permissions and then rebuild

the only thing i think i should not have done is : i have copied the su binaries at system.bin and system.xbin so that must not create probs ... that has also increased the size of your img by 22kb if any one cares lol

i will update the link tomorrow like after 1 or 2 pm ( when i will wake up )
for those in hurry just use the instructions in my first post and then use mkfs.yaffs2 from internet in linux( i used backtrack) give permissions of 667 to mkfs.yaffs2 and excute like
[NOTE FOR THIS TOOL SEARCH ON XDA i got it from there I THOUGHT THAT THAT TOOL WILL HELP IN MY PROJECT ..]
Code:
mkfs.yaffs2 decompile/ system.img
NOTE: i am Indian hence have that general tendency of playing safe handed !
if you cannot boot the system for more than 15 mins just extract the mmx zip and flash it !!
Click to expand...


your method may work ....

and they have removed ramdisk from boot.img and made it a spearate file named ramdisk.img
and we cannot extract ramdisk.img also...
 
@ninad
The first method too wont work.
Bcoz adding a superuser app and su binary is not enough bcoz we need unsecured boot.img to root completely.
That's why z4root has 2 options that is temporary root and permanent root.
In temporary root it adds binary and app(it can b reversed that's why called temporary root)
And permanent root adds binary and app plus it unsecures boot.img that's why permanant root needs a reboot of handset(its not reversible so called permanant root)
So jus adding app and binary to system.img wont help.
 
varun.chitre15 said:
@ninad
The first method too wont work.
Bcoz adding a superuser app and su binary is not enough bcoz we need unsecured boot.img to root completely.
That's why z4root has 2 options that is temporary root and permanent root.
In temporary root it adds binary and app(it can b reversed that's why called temporary root)
And permanent root adds binary and app plus it unsecures boot.img that's why permanant root needs a reboot of handset(its not reversible so called permanant root)
So jus adding app and binary to system.img wont help.
Click to expand...
once we get a temporary root then we can use adb and extract the boot.img with ram-disk then ..we can mod it...
 
Well let me clear some facts here .
Z4root ,gingerbreak,soc all use OS exploits.
The exploits are brought by the android exploit crew
These are named as
Rageagainstthecage(ratc),psneuter,gingerbread,zergrush and so on
When an exploit is run ,the OS breaks to gives you temporary access to root popularly known as shell root.
After the temp.access you can push the su binary and fix the required permissions in /system.
The su binary is. Required to acquire complete root at will hence it is known as perm root.
Superuser.apk manages the su binary
And busybox is required since it is OS of its own .

No operating system likes exploits.thereby they are patched and ffixed time to time.
The current latest exploit is zergrush and it was also patched .
If zergrush doesn't work then no current exploit will work.

The only alternative rooting is either pack a su binary in the file system(system.img)
and or flash an unsecured kernel/recovery (ro.secure〓0)

So ninads method should give you perm root.

Also that bloody ramdisk.img is not a gunzip nor another format I know of
I can see it in hex editor but dumping each file will take a shit loadd of time which I don't have lately .
 
@ A75 users now you just need to download this file
and flash it , i do not know if any one of u guys are aware of what is fastboot method,


you can also use any other flashing tools you can use !


just tick usb debugging and go to adb and type
Code: 
adb reboot bootloader
note : you also need drivers for fastboot mode drivers for windows but then i think those are generic and must work from the cd with A75 or internet , (not for MAc and Linux users)
after
Code: 
adb reboot bootloader
wait and keep that phone connected ! and then type
Code: 
 fastboot-windows devices
report if atleast you get till this step

even some other methods will do but not recommended though :p

then
Code: 
 fastboot-windows system system.img
I will suggest more than one person to try the same and report as there seems no harm in this method as you simply need to flash the system from mmx again more over even if u brick guarantee MAY help u as mmx does not know what is root !
but as usual :
I AM NOT RESPONSIBLE FOR YOUR EXPENSIVE DEVICES GETTING CONVERTED TO EXPENSIVE PAPERWEIGHTS ANY THING HAPPENS IS NOT MY RESPONSIBILITY , THOUGH THEORY SAYS THAT THIS SHOULD WORK FINE PRACTICALS ARE NOT ALWAYS SUCCESSFUL AS IT INVOLVES YOUR SKILLS IN APPLYING

IF you agree to above disclaimer then the link is here:

Code: 
http://www.sendspace.com/file/qwgctm

SHA512 check sum :CE 7D 9B D7 50 5C A7 65 46 85 09 57 7B 24 96 4F 6E 45 59 E5 28 E0 86 5F 71 C3 45 0D 1B 2F 8D 2D 2B 75 EC 83 52 CB B7 5F C3 59 7E C2 61 B3 DF 29 92 20 AE EF 04 FB F2 C3 33 18 D8 DB 4D 82 53 63

GET the mini sdk for windows here :
http://androidforums.com/faqs/443072-adb-guide-updated-12-05-2011-a.html

these things seem difficult ( i mean fastboot and stuff) but believe me they are like tos after you get root as you need them again and again !

SOme windows user plz refer if i am wrong in some fastboot method for drivers .
 
@karan the only thing i think i have done wrong is like i have kept su binaries at system/bin and system/xbin

but permissions are correct for both the places -- will that create some problem?
 
not really :p
The problem is bin folder is too long to navigates .
xbin folder is just for the ease of the purpose of deleting su and busybox and keep busybox symlinks away from bin to avoid confusion .

the only problem you may face is the native toolbox symlinks are destroyed after you extract an system image and repack it .
Thereby creating just duplicates and making the shell redundant .
you will need to delete those files and symlink it to toolbox again .
then again it's just a theory :rolleyes: :D :p
Amusing yaffs is still used .Isnt ext4 default for Gingerbread onwards :D
 
@karan i read in XDA that there was no prob in the way i did it for system.img .
the person over there used this method to decompile and then do modifications ( it was a project of new ROM creation btw.) and then rebuild !!!
hence i do not think that will be a problem.

the biggest problem as i think is that no one has yet tried and reported for this method lol ! :)
ext4 ---> sorry(to device) for the date till s.code is not available. Till then the poor device has to use yaffs !!!!!
 
:p
Android is supposed to have phased out yaffs after 2.3

There are some methods to enable ext4 without the source but well you guys dont have adb shell ,what can I say :p .
 
karandpr said:
Check the leov3 thread and flash the latest zip and a stock kernel over it . :p
Click to expand...

Yup i really do not know y ppl left Leo v3 alone...
amazing concepts ...
none tried and reported ??
I reported abt it but then from the first day my phone had debugging probs and now i cannot even try any ROM :p
leave aside ext4 even ext2 is way better than that freaking yaffs2
 
I think its DONE!! :)

I have flashed your system.img successfully:)
zjw9rb.png

25g6s06.png



:):):):):):):):):):):):):):):):):):):)
 
Status
Not open for further replies.
Back
Top Bottom