I messed up the build prop. Please help, thanks in advance give me the whole build prob values please.
abhimanyuz77 said:
I messed up the build prop. Please help, thanks in advance give me the whole build prob values please.
Click to expand...
Click to collapse
You can extract your own.....
Do you have a zip file for your device?
You can get desklunvr from development and run that to decrypt the file.
The file can then be extracted using your favourite zip program.
Then use ext2explore.exe to open the system.img and naviagte to system and right click the build.prop and select save.
The build props are different between regions. If you state your region someone may be able to help you out.
Stifilz
build prop
I imported it from USA newyork. To india. I used software update from within the tablet. So no zipfile. It's a nosim version, I don't think state do matter in my case.
abhimanyuz77 said:
I imported it from USA newyork. To india. I used software update from within the tablet. So no zipfile. It's a nosim version, I don't think state do matter in my case.
Click to expand...
Click to collapse
EDIT: What is your exact firmware? I will find prop
firmware
Android version
4.1.1 ( release 2)
Kernel version
3.1.10
[email protected]))
#1smp preempt fri jul 5 00:51 JST 2013
Build number
TJDS2010710 (US)
Thanks in advance..
abhimanyuz77 said:
Android version
4.1.1 ( release 2)
Kernel version
3.1.10
[email protected]))
#1smp preempt fri jul 5 00:51 JST 2013
Build number
TJDS2010710 (US)
Thanks in advance..
Click to expand...
Click to collapse
Please find attached build.prop from txs03_201 US. Please rename from build.prop.txt to build.prop also make sure it is the right file before copying over.
DON'T forget to chmod 644 after replacing build.prop or you will brick your device....
Infact if you haven't already then go to development thread and download All in One tool by condi.
Run the install-rescue back-door that way you can restore by installing a factory zip if all goes sour.
stifilz said:
Please find attached build.prop from txs03_201 US. Please rename from build.prop.txt to build.prop also make sure it is the right file before copying over.
DON'T forget to chmod 644 after replacing build.prop or you will brick your device....
Infact if you haven't already then go to development thread and download All in One tool by condi.
Run the install-rescue back-door that way you can restore by installing a factory zip if all goes sour.
Click to expand...
Click to collapse
Thanks a lot .
stifilz said:
Please find attached build.prop from txs03_201 US. Please rename from build.prop.txt to build.prop also make sure it is the right file before copying over.
DON'T forget to chmod 644 after replacing build.prop or you will brick your device....
Infact if you haven't already then go to development thread and download All in One tool by condi.
Run the install-rescue back-door that way you can restore by installing a factory zip if all goes sour.
Click to expand...
Click to collapse
By the way what is chmod, I am new at anroid, just flashed some roms and edited things in xperia u. Not well in other thins like you do.
Please give me steps to CHMOD 644 ??
stifilz said:
Please find attached build.prop from txs03_201 US. Please rename from build.prop.txt to build.prop also make sure it is the right file before copying over.
DON'T forget to chmod 644 after replacing build.prop or you will brick your device....
Infact if you haven't already then go to development thread and download All in One tool by condi.
Run the install-rescue back-door that way you can restore by installing a factory zip if all goes sour.
Click to expand...
Click to collapse
just compare the datas and edited it precisely. now tablet runs great!!! Boot menu manger works fine. Thank you/
abhimanyuz77 said:
By the way what is chmod, I am new at anroid, just flashed some roms and edited things in xperia u. Not well in other thins like you do.
Please give me steps to CHMOD 644 ??
Click to expand...
Click to collapse
Linux systems such as Android have special permissions. Windows does not have these.
If you were to adb pull /system/build.prop
and then delete build.prop from system and then
adb push build.prop /system/
Then the permission would be set to default and the tablet would not be able to read and it would not boot.
CHMOD is how to change the permissions.
i.e
adb shell
su
chmod 644 /system/build.prop
I am guessing that you user Root Explorer or similar to edit the file, so this is irrelevant to you
long story shot always edit the file on the tablet and make sure permissions are rw-r--r-- (644)
Stifilz
Related
hy everybody.
i try mod the system.img on ubuntu linux with unyaffs and mkfs.yaffs2, i "hacked" the symlinks(because the armv6 unyaffs doen't like) so now everything is ok, unyaffs works well. BUT:
when i flash the other sin files with flashtool, my x8 is restart after a green sony ball. i gave to all file in bin folder: rwx-rx-rx and the all other files got rw-r-r permissions.
so, i don't know what is the problem with this method.
//my system.img was flashed with a method in "clean and pre-rooted 2.1 rom" thread.//
in attachment the filesunyaffs and mkfs.yaffs2.x86)
unfortunately unyaffs-x86 does NOT preserve all file permissions if image is extracted and reassembled in Linux x86.
You have to extract/assemble on the phone to keep permissions.
Or, alternatively, you can fix permissions by using xRecovery tool, there's a menu "fix permissions".
To see why exactly your phone reboots, use adb logcat from PC.
racht said:
unfortunately unyaffs-x86 does NOT preserve all file permissions if image is extracted and reassembled in Linux x86.
You have to extract/assemble on the phone to keep permissions.
Or, alternatively, you can fix permissions by using xRecovery tool, there's a menu "fix permissions".
To see why exactly your phone reboots, use adb logcat from PC.
Click to expand...
Click to collapse
yess, thank you! now i found a mkfs.yaffs2 for arm processors for android. it's verry slow.
so i made my sdcard to ext2, and now i try to "extract" my img.
so ... It's used to ?
trapacska said:
hy everybody.
i try mod the system.img on ubuntu linux with unyaffs and mkfs.yaffs2, i "hacked" the symlinks(because the armv6 unyaffs doen't like) so now everything is ok, unyaffs works well. BUT:
when i flash the other sin files with flashtool, my x8 is restart after a green sony ball. i gave to all file in bin folder: rwx-rx-rx and the all other files got rw-r-r permissions.
so, i don't know what is the problem with this method.
//my system.img was flashed with a method in "clean and pre-rooted 2.1 rom" thread.//
in attachment the filesunyaffs and mkfs.yaffs2.x86)
Click to expand...
Click to collapse
i've created sh script to view your current permissions.
it could be useful to re-set the permission manually to create the ROM
how:
upload to root of sdcard
run
Code:
su
cd /sdcard
sh plist.sh
it will create folder "permissions" on your sdcard.
all files permission listed there
open with notepad++
propc said:
i've created sh script to view your current permissions.
it could be useful to re-set the permission manually to create the ROM
how:
upload to root of sdcard
run
Code:
su
cd /sdcard
sh plist.sh
it will create folder "permissions" on your sdcard.
all files permission listed there
open with notepad++
Click to expand...
Click to collapse
it's cool! thank you. now i try to debrand the oroginal x8 rom.
trapacska said:
it's cool! thank you. now i try to debrand the oroginal x8 rom.
Click to expand...
Click to collapse
you know what. i've found a better method to change permissions
1-mount original system.img
Code:
mkdir tmp/1
sudo mount -o loop /your/system.img/path /tmp/1
2-clone permissions from original system.img to your system folder
Code:
chmod -R --reference /tmp/1 /your/new/system/path
and the permission fix done!
EDIT: tested. and worked. I've finally created my own modified ROM (running on sdcard)
EDIT2: some problem with root permissions, will work on it
thank you i found a way to fix permissions too:
1. unyaffs original system.img
2. in busybox shell mount it to r/w
3. copy xrecovery and su and superuser to fresh rom.
(for me it works well without xrecovery fix permissions)
if there is some error, you can fix it with xrecovery
Hello,
Can you try to change the /system image with one from froyo ? You can find such image in the X10 forum. I thing that if we change the contents of the /system with such from froyo it should work. With the standard kernel from eclair.
Please try this and let me know.
bnight said:
Hello,
Can you try to change the /system image with one from froyo ? You can find such image in the X10 forum. I thing that if we change the contents of the /system with such from froyo it should work. With the standard kernel from eclair.
Please try this and let me know.
Click to expand...
Click to collapse
i tried it. no luck. too many files. where are the files that need to be edited?
/system/lib?
propc said:
i tried it. no luck. too many files. where are the files that need to be edited?
/system/lib?
Click to expand...
Click to collapse
/system/framework (for a skin)((but the all folder))
trapacska said:
/system/framework (for a skin)((but the all folder))
Click to expand...
Click to collapse
thanks. will try porting from htc legend 2.2 rom later.
Why?
init.d allows to run scripts at system startup (reboot) of Linux and Android devices. On the Sony Tablet S it is not supported on "stock" ROM. Therefore it is not possible to execute shell scripts at the boot process.
For what?
As mentioned above, primarily for startup scripts. It can be used for 'mounting ext.sdcard to int. sdcard' for example or it is also possible to integrate kernel modules or system tweaks boot time.
How?
This requires copying the files in the enclosed zip archive to the corresponding points and to change the permissions right. Firstyou must create the folder 'init.d' at '/system/etc'.
But now "Step-by-Step":
Requirements:
You need to use Root Explorer, adb or something else. I do not want to explain each step in detail. If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems.
Everything is done at your own risk.
Step-by-Step Instructions:
1. Create in '/system/etc' a 'init.d' folder
2. Change the access rights to '777'
3. Copy the file 'sysinit' into folder '/system/bin'
4. Change the access rights to '755'
5. Copy file 'install-recovery.sh' into folder / system / etc '
6. Change the access rights to '777'
7. Copy file 'run-parts' into folder '/system/xbin'
(If 'run-parts' already existing, you can skip Step 7 and 8. In my case it was already on the Tablet S)
8. Change the access rights to '777'
9. Copy file '99test file' into folder '/system/etc/init.d'
10. Change the access rights to '777'
Now finished .... it should work !
After next reboot take a look into the folder 'data/local/tmp'. You should find a file 'init.d_log_test.txt', created by the test script. If so, everything works fine and now you can put there your own scripts under 'init.d'. Now you can delete the test script or if you like adjust it for your own tests.
Have fun with the new 'init.d' support and apologize for my weak English !!
Special thanks to DooMLord for the idea and first implementation.
Source: http://forum.xda-developers.com/show....php?t=1431134
am I missing something here, or where is the zip-file?
the link doesn't work at the bottom.
Thanx for a nice "how-to"
Seems simple and straightforward enough
Sorry for that and thank you for the hint. I was 100% sure that I enclosed the zip ... but it looks like I am getting old. ;-)
Now you should find the zip on the end of first post.
Sorry - how do you gve the 777 file permissions?
SWFlyerUK said:
Sorry - how do you gve the 777 file permissions?
Click to expand...
Click to collapse
Via the chmod unix command, or if you are using root explorer just enable read/write/execute permissions for owner, group, and others. For 755 give owner all permissions and only read/execute to group and others.
Whoops, my device is in a bootloop lol
I hope you are joking ...
@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.
4=read
2=write
1=execute
I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.
What does it mean? Did you set wrong file permissions and reboots system? On all files or only on one specific? Did you changed build.prob and downloaded system update for boot loop prevention before?
obicom said:
I hope you are joking ...
@Rumball
Sorry, but you are wrong ...
755 give owner all permissions and only read/execute to group and others.
4=read
2=write
1=execute
Click to expand...
Click to collapse
Doh! Thanks
SWFlyerUK said:
I'm not joking, the permissions error is obviously the reason its in a bootloop then, fantastic.
Click to expand...
Click to collapse
Not permissions fault. Mine didn't bootloop
obicom said:
Special thanks to DooMLord for the idea and first implementation.
Click to expand...
Click to collapse
yep, DooMLord's great work.
got finished autoinstall tool for init.d as I said to you on thursday.
That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...
with a special thx for Condi ;-)
obicom said:
That sounds great ...
let us share your file ...
it makes it much easier for the other members ..
if you allow I could add it to the first post ...
with a special thx for Condi ;-)
Click to expand...
Click to collapse
hah not important, just good to see that there are some people who are working on making our devices better and better the more of us = more of cool tab stuff
auto-install up, try it, tested so far only on one device.
I changed nothing in the build.prop.
All I did was follow the instructions to your post and change the permissions as said by the chap above.
I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...
Can't follow your comment ...
Nothing is wrong with the information regarding permissions.
I did exactly the same on my Tab and one hour ago via Teamviewer on a second one.
I am not responsible if you did something wrong. Specially if you did not follow my hint to do first all regarding "boot loop prevention"
If you have not the necessary basic knowledge you should not do this because it is deeper system change, which could end with a brick or boot loop. That would not 'the end of the world', if you have previously prepared you system for this before and know what to do this case. I am not responsibility for damage or other any problems. Everything is done at your own risk.
Click to expand...
Click to collapse
SWFlyerUK said:
I changed nothing in the build.prop.
All I did was follow the instructions to your post and change the permissions as said by the chap above.
I'm now in a boot loop. My own fault for doing it but you don't expect posted information on permissions to be incorrect...
Click to expand...
Click to collapse
I wrote in many threads about 'rescue-backdoor', why havent you made it?
I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.
That was the background regarding 'did you changed build.prob' and not as a reproach. I can not understand why someone try something out, without a backup or rescue strategy. Oh damn !!
-- Edit --
Rolled the build.prop increment value back
Click to expand...
Click to collapse
Does it mean now you have the original value or the lower value?
If first case , that was a fault.
SWFlyerUK said:
I did condi ie got my ota firmware. Rolled the build.prop increment value back. But I get a verification cation error so everything was prepared.
Click to expand...
Click to collapse
The key to 'rescue' is to leave modified build.prop. It fakes that you've got older firmware than zip (zip=device the same versions). Then you get in recovery, and got opportunity to reflash the same version!
I've got a cheap Chinese tablet (WM8850-MID) running Android 4.0.3 based on WonderMedia 8850 processor.
It's not rooted.
Here's what i found:
/system/xbin/su is present:
-rwsr-xr-x 1 0 0 68528 May 14 11:07 su
But I can't run su in a terminal:
su uid 10064 not allowed to su
Using adb.exe I have the same problem with uid 2000.
There is a script /system/etc/init.sh which is called a boot time, but If I modify and push it via adb it won't execute (lost execute permission)
adb reboot-bootloader does reboot the device, but it does not stay in bootloader mode and just go straight to Android.
I'm not sure where to go from here. Is there a way to root that device ?
Try ./adb root to run as root.
Use oneclickroot.
Daniel120201 said:
Try ./adb root to run as root.
Use oneclickroot.
Click to expand...
Click to collapse
I forgot to mention "adb root" says I'm already root.
If I copy files with adb push, the owner is root, but If I use "adb shell" I'm user uid 2000.
This is a new tablet, but I'll give oneclick a try anyway. Thanks.
I've just tried SuperOneClick 2.3.1.0. It says it's already rooted because it can find /system/xbin/su, but I continued anyway. It can copy busybox (temp) but cannot change the permissions and it stops there.
Try resetting your tablet and if the su binary is stil there remove it. After resetting retry with superoneclick.
Sent from my MID7C using xda app-developers app
Daniel120201 said:
Try resetting your tablet and if the su binary is stil there remove it. After resetting retry with superoneclick.
Sent from my MID7C using xda app-developers app
Click to expand...
Click to collapse
Thanks, but how do I delete it since I don't have the permissions? In case it's possible, is it safe to remove the su binary? I have no way to recover my firmware...
Use ./adb root to remove it because you will be root.After removing it reset your tablet to factory settings. It is safe because the su binary is not part of the os.
Then try rooting with oneclickroot.
Hope it works for you.
i also bought wm8850 tablet in china..can you teach me how to root in detailed its my first android device....i dont understand the other terms u are using....
Hi jallaine12gil,
I think that you should first try to root with oneclickroot. Post if it worked or not. Oneclickroot is a rooting program for android devices.
download the firmware. then find the android4.0.tgz file open it with 7zip, add the su file to system/bin folder and system/xbin manually.... then put the superuser.apk in the system/app folder then save changes.... then flash firmware from sdcard
if camera is in the top centre of the wm8850 tablet: in txt file
if camera is in top right of the wm8850 tablet: in txt file
download the firmware. then find the android4.0.tgz file open it with 7zip, add the su file to system/bin folder and system/xbin manually.... then put the superuser.apk in the system/app folder then save changes.... then flash firmware from sdcard
Attachment is the links to firmwares
Hi i was brick my 8850 ekenw70 flashing this
WM8850_MID7_PuZhi_W01_8223_FT5206_W70_WMC1579
i was buy it here:
http://www.aliexpres...holesalers.html
can sugest something to debrick??
All what i have is one black screen, i try to reflash but no luck.
WM8850 RootBurner
How root the WM8850 tablet without firmware update :RootBurner on "nanospic.ro/?p=327" !
cnxsoft said:
I've just tried SuperOneClick 2.3.1.0. It says it's already rooted because it can find /system/xbin/su, but I continued anyway. It can copy busybox (temp) but cannot change the permissions and it stops there.
Click to expand...
Click to collapse
Hi friends,
I also used this device...any results ??...working or not ?..pls help guys..
Br
Zaki..
ellisondavid said:
download the firmware. then find the android4.0.tgz file open it with 7zip, add the su file to system/bin folder and system/xbin manually.... then put the superuser.apk in the system/app folder then save changes.... then flash firmware from sdcard
Attachment is the links to firmwares
Click to expand...
Click to collapse
Hi, friend
How to put manually ?? file read only!...any MOD..pls help..
RootBurner
basodiodoh said:
Hi, friend
How to put manually ?? file read only!...any MOD..pls help..
Click to expand...
Click to collapse
Hi!
why not use RootBurner for WM8850? The rooting procces is similary to firmware update!
Extract the archive into sd card and insert into tablet and Power ON!
ellisondavid said:
download the firmware. then find the android4.0.tgz file open it with 7zip, add the su file to system/bin folder and system/xbin manually.... then put the superuser.apk in the system/app folder then save changes.... then flash firmware from sdcard
Attachment is the links to firmwares
Click to expand...
Click to collapse
Hi, friend..this firmware compatible for version below??
Model Number : WM8850-mid
Build number : 4.0.3 ICS Ver. 1.2.0-20120824.044231
* camera - top right hand side*
Thanks.
How to get adb working on the wm8850?
Hi, sorry to interject with something semi-unrelated, but how did you guys get adb working with the wm8850? I've added the vendor id to the ~/.android/adb_usb.ini on mac, but adb still can't find the device. I used 0x0ea0, is this what you guys used?
Any advice would be great!
have the same tablet
i have the same tablet WM8850-mid ihave my rooted but i dont know haw to flash roms and what should i use CWM recovery version for this tablet pls help me thanks...
thank you XDA pls help..
how to root ??
MarionSabido said:
i have the same tablet WM8850-mid ihave my rooted but i dont know haw to flash roms and what should i use CWM recovery version for this tablet pls help me thanks...
thank you XDA pls help..
Click to expand...
Click to collapse
Hi, friend
Sorry, how do you root??
can anyone upload original build.prop from tablet s pls ?
thx
neimovirne said:
can anyone upload original build.prop from tablet s pls ?
thx
Click to expand...
Click to collapse
This is development. Not general section.
Anyway, download your stock Rom from the link in my signature. Then look in the development section for the tool to decrypt your own Rom then use ext2explore to extract system.img
Or give us more detail off model etc
Further more back up files before modding them
stifilz said:
This is development. Not general section.
Anyway, download your stock Rom from the link in my signature. Then look in the development section for the tool to decrypt your own Rom then use ext2explore to extract system.img
Or give us more detail off model etc
Further more back up files before modding them
Click to expand...
Click to collapse
it takes too much time ..
Use this: http://caftp.3owl.com/File_Upload_Admin/Files/build.prop
It will be in there temporarily so tell me when you have got the file or I will delete it at some point.
You may want to modify it since my device was in the UK and it is using release5a.
Next time try creating a backup, it uses your time for a reason.
If you want to backup in /system/ then you can copy the file in the directory renamed so you can just remove a character or something from the backup file to get it in use also you do need to delete the failed one or if you don't have one then find a way to get in and do it but you can't use ADB in recovery unless you have the release1a recovery.
If I did backup, my device is soft bricked, rooted and have such recovery then what I would do is:
cd /system/
su
rm build.prop
mv build.prop.bak build.prop
EDIT: You have till the 25th before the file gets removed from my website.
Sent from my Sony Tablet S using xda premium
andyabc said:
Use this: http://caftp.3owl.com/File_Upload_Admin/Files/build.prop
It will be in there temporarily so tell me when you have got the file or I will delete it at some point.
You may want to modify it since my device was in the UK and it is using release5a.
Next time try creating a backup, it uses your time for a reason.
If you want to backup in /system/ then you can copy the file in the directory renamed so you can just remove a character or something from the backup file to get it in use also you do need to delete the failed one or if you don't have one then find a way to get in and do it but you can't use ADB in recovery unless you have the release1a recovery.
If I did backup, my device is soft bricked, rooted and have such recovery then what I would do is:
cd /system/
su
rm build.prop
mv build.prop.bak build.prop
EDIT: You have till the 25th before the file gets removed from my website.
Sent from my Sony Tablet S using xda premium
Click to expand...
Click to collapse
thx! so much
u can remove it now
neimovirne said:
can anyone upload original build.prop from tablet s pls ?
thx
Click to expand...
Click to collapse
stifilz said:
This is development. Not general section.
Click to expand...
Click to collapse
As per the XDA rules All questions/requests threads go in the Q&A.
Thanks
my question is based on this thread
1th about modifying bin files.
if i want v10 versions i should modify the bin files like artit's post in this thread .the 6th step.
but if i want v20 versions i should modify the bin files like this thread
am i right?
2th is about uploading files to the phone.
artit has said "all files should upload to your phone" in this thread .i just wonder how to upload and when to upload?
well i think i should connect my phone to pc by cable and run the commands
cd C:\root
adb push su /data/local/tmp/
adb push busybox /data/local/tmp/
adb push Superuser.apk /data/local/tmp/
adb push rooting.sh /data/local/tmp/
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/rooting.sh
Click to expand...
Click to collapse
before flashing .then after flashing i should connect my phone to pc and run another commands
adb shell rm /data/local/tmp/rooting.sh
adb shell touch /data/local/tmp/rooting.sh
adb shell chmod 755 /data/local/tmp/rooting.sh
Click to expand...
Click to collapse
.
am i right ? if i am right .i can't understand can i upload files to the specific location on the phone by adb whitout rooting ? and will the files exist in the phone after flashing?(won't they be coverd?)
3th i can't find infomation in the 12th step of this thread about "CWM Recovery Installation on Jelly Bean" by the link.
can someone give me a guide of that?
4th the last question .about the 13th step of this thread about "BUSYBOX Re-Installation".
how can i do it like this ?
i am very very thankful to your answer!!!
1th about modifying bin files.
if i want v10 versions i should modify the bin files like artit's post in this thread .the 6th step.
but if i want v20 versions i should modify the bin files like this thread
am i right?
It's depend on what software version you are on.
For my V10D, I edit 5th .bin file.
For my V10E, I edit 6th .bin file.
You should search in hex edit for the file you should edit.
2th is about uploading files to the phone.
artit has said "all files should upload to your phone" in this thread .i just wonder how to upload and when to upload?
well i think i should connect my phone to pc by cable and run the commands before flashing .then after flashing i should connect my phone to pc and run another commands .
am i right ? if i am right .i can't understand can i upload files to the specific location on the phone by adb whitout rooting ? and will the files exist in the phone after flashing?(won't they be coverd?)
You can upload file (and more) with adb tool. And you can upload files to your phone without rooting if you have writing permission in that directory. Most rooting methods use /data/local/tmp to store rooting stuff because that directory is writable to all users. Please follow cmahendra guide, it has script that do most upload tasks for you.
3th i can't find infomation in the 12th step of this thread about "CWM Recovery Installation on Jelly Bean" by the link.
can someone give me a guide of that?
Um.. In that thread you just download and install .apk file. Make sure you enable "allow installation of non-market apps" in System Setting > security menu before install (to install just click that file in file explorer).
4th the last question .about the 13th step of this thread about "BUSYBOX Re-Installation".
how can i do it like this ?
The step is in http://forum.xda-developers.com/showpost.php?p=38948923&postcount=141
Open Play store and search for "busybox" and choose one that you like.
i am very very thankful to your answer!!!
http://forum.xda-developers.com/showthread.php?t=2173465
Also check 2th (Oops 2nd) post.
thanks very very much
artit said:
1th about modifying bin files.
if i want v10 versions i should modify the bin files like artit's post in this thread .the 6th step.
but if i want v20 versions i should modify the bin files like this thread
am i right?
It's depend on what software version you are on.
For my V10D, I edit 5th .bin file.
For my V10E, I edit 6th .bin file.
You should search in hex edit for the file you should edit.
2th is about uploading files to the phone.
artit has said "all files should upload to your phone" in this thread .i just wonder how to upload and when to upload?
well i think i should connect my phone to pc by cable and run the commands before flashing .then after flashing i should connect my phone to pc and run another commands .
am i right ? if i am right .i can't understand can i upload files to the specific location on the phone by adb whitout rooting ? and will the files exist in the phone after flashing?(won't they be coverd?)
You can upload file (and more) with adb tool. And you can upload files to your phone without rooting if you have writing permission in that directory. Most rooting methods use /data/local/tmp to store rooting stuff because that directory is writable to all users. Please follow cmahendra guide, it has script that do most upload tasks for you.
3th i can't find infomation in the 12th step of this thread about "CWM Recovery Installation on Jelly Bean" by the link.
can someone give me a guide of that?
Um.. In that thread you just download and install .apk file. Make sure you enable "allow installation of non-market apps" in System Setting > security menu before install (to install just click that file in file explorer).
4th the last question .about the 13th step of this thread about "BUSYBOX Re-Installation".
how can i do it like this ?
The step is in http://forum.xda-developers.com/showpost.php?p=38948923&postcount=141
Open Play store and search for "busybox" and choose one that you like.
i am very very thankful to your answer!!!
Click to expand...
Click to collapse
thank you very much！
and i have make the questions from 2th to 4th clear by your answer.
but about the 1th one . you have disunderstood me . i am not mean which file to modify but the strings by which i find the very bin file through searching in hex editor. is the strings different from every versions ？
thanks for your answer
cmahendra said:
http://forum.xda-developers.com/showthread.php?t=2173465
Also check 2th (Oops 2nd) post.
Click to expand...
Click to collapse
thank you very much
i have read your guide many times . and now i have made it clear .just a small detail question which i reply to artit.
and i want to modify bin files by myself.