Related
Hi,
i have recently bought an HTC desire Z (G2) device, and downloaded a 163MB .zip rom. what do i have to do to install it??
i searched every where and could not find an answer!!
thanks
Look here:
http://forum.xda-developers.com/showthread.php?t=801206
You shall find all answers to your questions there
Razorless said:
Look here:
http://forum.xda-developers.com/showthread.php?t=801206
You shall find all answers to your questions there
Click to expand...
Click to collapse
Flash the ROM via recovery. I realize that's vague but you need clockworkmod recovery and to do that you need to have s-off. And to get s-off is a whole new thing all together because you need perm root
To root it, s-off it and rom flash it, you have to be willing to accept the consequences if you don't read enough and if you make a mistake!
And, that's the key, read everything and keep reading until it makes sense to you. Then follow the instructions to the "T" make sure you know your builds and then it's a leap off faith.......if you don't understand something, ask a question or two. There is all the info that you need right in the threads. Good luck and don't be in a hurry . Happy New Year.
thanks all, i really appreciate your fast response.
actually i just want to enable arabic support on my htc desire z, and i downloaded the arabic files from
http://ardoid.com/?p=189
and installed visionary and done the perm root with su permissions and get a # after typing su in terminal
i copied the zip files to the sd, rebooted and selected recovery, then applied update.zip, the phone rebooted but without any success of arabizing.
my kernel is 2.6.32.21-gd2764ed older according to wiki
http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF
my question is, do i need to s off to get the files installed? do i have to remove visionary as a second step with removing rooting?
the status is that my phone has permaroot, and what i understood is that i am a step away from s off using gfree, i downloaded the file to my mac, and copied to the sd card.
i have super user
su
#
i have understood adb, and terminal, and copied the script but resulted with errors, script used
cd /data/local
chmod 777 gfree
./gfree
sync
error result on phone after chmod 777 gfree
unable to chmod gfree:no such file or directory
#
i have copied gfree.zip to sd card via mounting the phone via usb. and then changed the mode to charging mode automatically and enabled usb debugging.
again, i would appreciate your efforts, since this thread is closed;
http://forum.xda-developers.com/showthread.php?t=857390&page=15
Microzift said:
i have understood adb, and terminal, and copied the script but resulted with errors, script used
Click to expand...
Click to collapse
The error you are receiving means you don't actually have gfree on your phone (at least not in the right location). Did you receive any errors from ADB when you pushed the gfree file? Also, be sure you pushed the actual gfree file and not the zip (you need to extract it from the zip first).
Microzift said:
i have copied gfree.zip to sd card via mounting the phone via usb. and then changed the mode to charging mode automatically and enabled usb debugging.
Click to expand...
Click to collapse
Are you saying you tried this as well? Or did you not actually use ADB? If you are trying to accomplish this without ADB, you might want to take a look at this thread for instructions: http://forum.xda-developers.com/showthread.php?t=903152. And again, you will need to use the contents of the zip file, not the zip itself.
ianmcquinn said:
The error you are receiving means you don't actually have gfree on your phone (at least not in the right location). Did you receive any errors from ADB when you pushed the gfree file? Also, be sure you pushed the actual gfree file and not the zip (you need to extract it from the zip first).
Are you saying you tried this as well? Or did you not actually use ADB? If you are trying to accomplish this without ADB, you might want to take a look at this thread for instructions: http://forum.xda-developers.com/showthread.php?t=903152. And again, you will need to use the contents of the zip file, not the zip itself.
Click to expand...
Click to collapse
thanks for your reply, i checked the thread and more questions!
actually i am confused, i do the steps without getting the point of it, i installed astro, visionary 14, terminal emulator on phone, and adb on mac.
i dont know what adb is for, and i kind of understand that its for copying files from sd to phone internal memory? is that right? or does it have other functions,
its also not easy to understand astro, can it copy files from sd to internal memory?
do i have to drag adb to terminal every time for adb to run?
shall i use gfree or gfree_2 on my sd?
does terminal with su be enough or i have to use adb?or copying gfree to sd would be enough via usb mounting? where is data\local?
after my current understanding, i have decided to not use adb, and i have reached this step,after writing this script in the terminal,
got superuser for terminal emulator (ON PHONE)
su
cd /sdcard
chmod 777 the GFREE
./gfree
permission denied!
please let me know if i have misunderstood anything or if i am on the wrong track to s off.
i apologize for the long questions,
thanks again
Microzift said:
i dont know what adb is for, and i kind of understand that its for copying files from sd to phone internal memory? is that right? or does it have other functions,
Click to expand...
Click to collapse
ADB stands for Android Debug Bridge. It allows you to do a number of functions to your phone from your computer. The most common commands are push and pull (copies files on your computer to/from your phone) and shell (starts a shell terminal on your phone---basically the exact same as running the Terminal app on your phone, only you can type all of your commands on your computer instead). It also allows you to do things like install APKs stored on your computer directly to your phone and viewing log files.
Microzift said:
its also not easy to understand astro, can it copy files from sd to internal memory?
Click to expand...
Click to collapse
Astro is simply a file manager for your phone. It allows you to do basic file management (copy, move, delete, create new directories, etc.). Some directories are read-only by default however (rooting the phone will allow you to, among other things, mount these directories as read-write---once rooted, Root Explorer is a popular file manager like Astro that will allow you to manipulate these directories).
Microzift said:
do i have to drag adb to terminal every time for adb to run?
Click to expand...
Click to collapse
No, this is not ADB should be used (it is a command line tool). Check out the various guides on setting up/using ADB.
Microzift said:
shall i use gfree or gfree_2 on my sd?
does terminal with su be enough or i have to use adb?or copying gfree to sd would be enough via usb mounting? where is data\local?
after my current understanding, i have decided to not use adb, and i have reached this step,after writing this script in the terminal,
got superuser for terminal emulator (ON PHONE)
su
cd /sdcard
chmod 777 the GFREE
./gfree
permission denied!
Click to expand...
Click to collapse
See my next post for instructions on rooting without using ADB.
Permanent Root without using ADB
Extract the contents of gfree_temp-root.zip to your SD card (located on the Wiki). Also extract the gfree file from gfree_02.zip to your SD card. Note, you need to extract these files, not simply copy the entire zip to your SD card. Also, if you copied these files to your SD card by mounting your phone over USB, be sure to unmount it again prior to starting the remaining steps (i.e., turn off USB storage). Your SD card should now contain the following files: busybox, gfree, rage, root, su, and Superuser.apk.
Start Terminal on your phone (download from Market if you don't already have one) and type the following commands exactly as shown.
Code:
cp /sdcard/rage /data/local/tmp
cp /sdcard/busybox /data/local/tmp
cp /sdcard/root /data/local/tmp
chmod 755 /data/local/tmp/*
Then run the following command if you need temp root (so not needed if already temp rooted with Visionary). It is recommended that you uninstall or disable Visionary though and use this method however (some people have had problems when using Visionary). If you want to use Visionary for your temp root, skip this step and just right to the permanent root commands further below.
Code:
/data/local/tmp/rage
You should see a message similar to "Forked #### childs." Hit Menu and select Reset Term (the app will close). Launch Terminal again (it may force close). Launch it one more time (you now have temp root).
Now to achieve permanent root, run the following commands:
Code:
cp /sdcard/gfree /data/local
chmod 777 /data/local/gfree
/data/local/gfree -f
sync
Make sure there are no errors from the gfree output.
Lastly, run the following commands (the root script will install Busybox and set up the su apps for you):
Code:
/data/local/tmp/root
sync
If you have no errors, reboot your phone. You should now have permanent root.
ianmcquinn said:
Extract the contents of gfree_temp-root.zip to your SD card (located on the Wiki). Also extract the gfree file from gfree_02.zip to your SD card. Note, you need to extract these files, not simply copy the entire zip to your SD card. Also, if you copied these files to your SD card by mounting your phone over USB, be sure to unmount it again prior to starting the remaining steps (i.e., turn off USB storage). Your SD card should now contain the following files: busybox, gfree, rage, root, su, and Superuser.apk.
Start Terminal on your phone (download from Market if you don't already have one) and type the following commands exactly as shown.
Code:
cp /sdcard/rage /data/local/tmp
cp /sdcard/busybox /data/local/tmp
cp /sdcard/root /data/local/tmp
chmod 755 /data/local/tmp/*
Then run the following command if you need temp root (so not needed if already temp rooted with Visionary). It is recommended that you uninstall or disable Visionary though and use this method however (some people have had problems when using Visionary). If you want to use Visionary for your temp root, skip this step and just right to the permanent root commands further below.
Code:
/data/local/tmp/rage
You should see a message similar to "Forked #### childs." Hit Menu and select Reset Term (the app will close). Launch Terminal again (it may force close). Launch it one more time (you now have temp root).
Now to achieve permanent root, run the following commands:
Code:
cp /sdcard/gfree /data/local
chmod 777 /data/local/gfree
/data/local/gfree -f
sync
Make sure there are no errors from the gfree output.
Lastly, run the following commands (the root script will install Busybox and set up the su apps for you):
Code:
/data/local/tmp/root
sync
If you have no errors, reboot your phone. You should now have permanent root.
Click to expand...
Click to collapse
thanks, i could not find busybox, gfree, rage, root, su, and Superuser.apk on my sd after copying and extracting the zip files, the folders i unzipped did not also have the above files (gfree_temp-root.zip & gfree_02.zip from wiki, i do not have the above busybox etc files) i also kept them in separate folders on sd card; gfree and gfree_verify_v01
i think i have permanent root via visionary, i receive a # after typing su in terminal on phone. so i dont need rage i guess.
and after trying perm root as explained
cp /sdcard/gfree /data/local
i receive
cp: omitting directory '/sdcard/gfree'
where did i go wrong again!
Microzift said:
i think i have permanent root via visionary, i receive a # after typing su in terminal on phone. so i dont need rage i guess.
and after trying perm root as explained
cp /sdcard/gfree /data/local
i receive
cp: omitting directory '/sdcard/gfree'
where did i go wrong again!
Click to expand...
Click to collapse
If "su" is giving you a # prompt after a reboot then you have permanent root, yes.
Possibly a silly question, but you do have an SD card in the phone, right ? And it's mounted on the phone, not on the PC when you're trying these commands ?
steviewevie said:
If "su" is giving you a # prompt after a reboot then you have permanent root, yes.
Possibly a silly question, but you do have an SD card in the phone, right ? And it's mounted on the phone, not on the PC when you're trying these commands ?
Click to expand...
Click to collapse
thanks for asking, and thanks for clarifying the perm root.
regarding the sd, yes i am ok with mounting and charging mode, and i make sure that the phone is always in charge mode when using adb or terminal on the phone automatically when using usb. and only convert to pc mounting mode when i need to copy a file (like gfree or gfree veryfy) to phone sd card.
although i still keep the usb connected to mac in charge mode when i try terminal on phone (and adb is running). i disconnected to try and received the same error.
Microzift said:
thanks for asking, and thanks for clarifying the perm root.
regarding the sd, yes i am ok with mounting and charging mode, and i make sure that the phone is always in charge mode when using adb or terminal on the phone automatically when using usb. and only convert to pc mounting mode when i need to copy a file (like gfree or gfree veryfy) to phone sd card.
although i still keep the usb connected to mac in charge mode when i try terminal on phone (and adb is running). i disconnected to try and received the same error.
Click to expand...
Click to collapse
When you are getting that error with the "cp", try "ls /sdcard" and see if you get a big list of files, which should include whatever you tried to "adb push" there (e.g. gfree).
You don't have to use adb to copy adb to the phone, that's just one way of getting it there. You could mount the SD card from your phone onto your PC and copy it there that way. You just need to get the gfree binary onto your phone somehow, then copy it to /data/local
I just thought - you are running that "cp" command on the phone in Terminal Emulator, right ? Not on your Mac ?
steviewevie said:
When you are getting that error with the "cp", try "ls /sdcard" and see if you get a big list of files, which should include whatever you tried to "adb push" there (e.g. gfree).
You don't have to use adb to copy adb to the phone, that's just one way of getting it there. You could mount the SD card from your phone onto your PC and copy it there that way. You just need to get the gfree binary onto your phone somehow, then copy it to /data/local
I just thought - you are running that "cp" command on the phone in Terminal Emulator, right ? Not on your Mac ?
Click to expand...
Click to collapse
great now i get why i need to mount and copy gfree to phone sd, so that i can copy from sd to internal phone memory using terminal (on phone) or adb on mac.
yes i am running cp on terminal emulator on phone.
after ls /sdcard i receive
/sdcard
#
Microzift said:
thanks, i could not find busybox, gfree, rage, root, su, and Superuser.apk on my sd after copying and extracting the zip files, the folders i unzipped did not also have the above files (gfree_temp-root.zip & gfree_02.zip from wiki, i do not have the above busybox etc files) i also kept them in separate folders on sd card; gfree and gfree_verify_v01
Click to expand...
Click to collapse
Do not keep them in separate folders on the SD card. The files need to be on the root of the SD card in order for the commands I gave you to work.
Microzift said:
great now i get why i need to mount and copy gfree to phone sd, so that i can copy from sd to internal phone memory using terminal (on phone) or adb on mac.
yes i am running cp on terminal emulator on phone.
after ls /sdcard i receive
/sdcard
#
Click to expand...
Click to collapse
That is showing no files in your SD card folder. It sounds like it is actually mounted on your PC when you are running that, rather than being mounted on the phone itself.
steviewevie said:
That is showing no files in your SD card folder. It sounds like it is actually mounted on your PC when you are running that, rather than being mounted on the phone itself.
Click to expand...
Click to collapse
i have disconnected the usb from my pc, and still get the same message.
this is my understanding; mount sd on pc; means i can access the sd as a hard disk via the phones usb cable on my mac desktop.
unmounting; means i gain access of the sd on my phone only?
i found an option on phone, unmount sd card, should i do this every time i use terminal? i think this is for to unplug the sd card from the phone.
how can i get the sd mounted on my phone? i can see the same files via astro on my phone.
i still receive /sdcard
thanks guys, i just rebooted
my desire z is S OFF now.
and installed the recovery
thanks for all of your efforts
Is there something I'm missing? I was trying to use adb push and adb shell to move/copy a bootanimation to system/media. Every time I would be confronted with a permission error or cross-link device problem. When I use Root Explorer, it's fine. What gives?
ADB doesn't have root permissions on your rom or kernel.
RW or not, it must have these.
CM9 Nightly Builds currently support ADB root access and the ability to toggle it, if you're interested
I have rooted my HTC One X and want to copy files in /system/xbin folder. My phone shows S-ON. And Eclipse is not able to copy files to /system and adb push from shell is also not working. Is there a way I can copy files to /system/xbin?
I am running stock ROM.
My phone is NOT associated with any vendor.
adb remount
adb push filename /system/xbin
Sent from my HTC One X
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
realunited123 said:
adb remount
adb push filename /system/xbin
Sent from my HTC One X
Click to expand...
Click to collapse
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Additional Question
treebill said:
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
KillerTheLord said:
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Click to expand...
Click to collapse
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
KillerTheLord said:
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
Click to expand...
Click to collapse
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
realunited123 said:
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
Click to expand...
Click to collapse
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
KillerTheLord said:
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
Click to expand...
Click to collapse
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
realunited123 said:
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
Click to expand...
Click to collapse
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I think this app does exactly what you want :
http://forum.xda-developers.com/showthread.php?t=1687590
realunited123 said:
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
Click to expand...
Click to collapse
Well this didn't work either. I hope to switch to some other ROM in future(I hate HTC Sense ). But as of now Root Explorer did the job. I mounted my sdcard and copied files to it and used Root Explorer to move files to /system and then changed permissions.
Thanks for help it really made it easy .
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
NikMel said:
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
Click to expand...
Click to collapse
The problem was not accessing the device using ADB. The problem was I was not able to write to root system. ES Explorer and Root Explorer both did the job for me. I will be putting the final instructions for the process(detailed ones) soon.
Instructions onw how to copy files to root file system on HTC One X with S-ON
1) Unlock and Root your phone. Follow instructions below
http://www.youtube.com/watch?v=gIeq8Jx28cs
and then
http://www.youtube.com/watch?v=80lMHUgxwww
2) Install ES Explorer(File Manager) Link :- https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3) Connect device to computer(even if it is not recognized by ADB/Computer)
4) In Phone select Disk drive option. Now the phone's storage will be mounted on your computer as removable device.
5) Copy the files you want to send to phone's root system to any folder here.
6) Change phone's mode to charge only and wait for 2-3 secs(let phone remount sdcard)
7) Open ES Explorer and open menu(those 3 dots at bottom and select Settings)
8) Tick the following options
Up to Root
Root Explorer
Mount File System
9) A dialog box for permission will open Grant it.
10) Now copy files from /sdcard/<Folder where u put files> to where ever you want o copy files to.
11) Long press on file to change permissions and stuff.
Post here if you are stuck someone will surely help you.
Hi Everyone,
I was pissed of when I've realized that LedMeKnow app is not working on my favorite ROMs. So I've started to dig around this issue and finally managed to workout the way to fix it. And here it is...:cyclops:
Description
With the upgrade to GingerBread (and Ice Cream Sandwich) the permissions on leds have changed forbidding write access for every one except root. The way to work it around was to gain root privileges every time writing to brightness file in leds directory. However this option work, it tends to be very slow because of slowness of Superuser or SuperSU applications.
My workaround changes the permissions of brightness files located in leds directory to 666 allowing every one to write. As those permissions have to be set every time phone is rebooted I've created init.d script that will do it automatically.
Used commands
Code:
busybox chmod 666 /sys/devices/platform/leds-microp/leds/amber/brightness
busybox chmod 666 /sys/devices/platform/leds-microp/leds/blue/brightness
busybox chmod 666 /sys/devices/platform/leds-microp/leds/green/brightness
busybox chmod 666 /sys/devices/platform/leds-microp/leds/button-backlight/brightness
Declaimer
I take no responsibility for any issues connected with usage of my script.
Installation
Easy way
1. Download LedMeKnow-fix-Beta1.zip from this thread.
2. Flash it under CWM.
3. Reboot your phone.
4. Enjoy...
Less easy way
1. Download 91LedMeKnowFix.zip and unpack the script.
2. Push it into your phone.
3. Using ADB or Root Explorer move 91LedMeKnowFix to /system/etc/init.d/
4. Using Root Explorer set permissions to readwrite and execute for everyone or using ADB execute
Code:
su
chmod 777 /system/etc/init.d/91LedMeKnowFix
5. Reboot your phone.
6. Enjoy...
:cyclops: IF YOU LIKED IT DON'T FORGET TO THANK :cyclops:
hi guys, a friend of mine is asking me if there's something i can do to make her cp a bit faster/ smoother running stock rom (gb 2.3.6) since he don't want to use any custom rom. her cp
searching the thread, i was able to read some info that some was able to flash mod/ tweaks on stock roms to at least improve its performance. so i'm planning to install andrenaline engine or crossbreader on it but, as far as i know, flashing them requires ur rom, aside from of course being rooted, have cwm, etc., to support init.d which stock roms don't have. (corect me if i'm wrong)
i'm a bit in doubt doing this in the fist place, so any guide/ help or suggestions to make this init.d thing work is really really much appreciated. thnx in advance!
info i got (xda forum) about making stock rom support init.d Enable Init.d for Any Phones w/o Need of Custom Kernels
here, this link provide init.d support;
http://forum.xda-developers.com/showpost.php?p=32716432&postcount=3
flash zip_init.zip.
copy zip_init.zip to sd-card,
boot to cwm, mount /system, mount /data then flash zip_init.zip
check for test.log in /data if it is there or not, no test.log not working.
it work on my stock rom.
also flash adrenoboost v0.7 will boost perfromance from stock 5000 to 7000 (antutu benchmark).
adrenoboost link;
http://forum.xda-developers.com/showthread.php?t=2167228
saintsoh said:
here, this link provide init.d support;
http://forum.xda-developers.com/showpost.php?p=32716432&postcount=3
flash zip_init.zip.
copy zip_init.zip to sd-card,
boot to cwm, mount /system then flash zip_init.zip
check for test.log in /data if it is there or not, no test.log not working.
it work on my stock rom.
also flash adrenoboost v0.7 will boost perfromance from stock 5000 to 7000 (antutu benchmark).
adrenoboost link;
http://forum.xda-developers.com/showthread.php?t=2167228
Click to expand...
Click to collapse
thnx for the reply bro. about the adrenoboost, i think its main purpose is to boost the performance of Adreno 205 GPU or similar gpu but my friends device doesn't have gpu.
i didnt know tat.
anyway i think after mount /system, u should also mount /data (just in case).
it work on my sgw without mount /data but then i saw check /data for test.log which makes it necessary or not?
i'm not sure, just be on the safe side mount /data.
saintsoh said:
i didnt know tat.
anyway i think after mount /system, u should also mount /data (just in case).
it work on my sgw without mount /data but then i saw check /data for test.log which makes it necessary or not?
i'm not sure, just be on the safe side mount /data.
Click to expand...
Click to collapse
okay, i'll try that and hope it'll work
EDIT: sad, it didn't work
just learn something new when i reverted back to stock and re-install zip-init for init.d support.
when flash zip_init.zip and reboot, cwm will ask to "disable recovery flash" - select "NO".
(note: if select "yes", it will give a false positive, 'install-recovery.sh' will not have execute permissions and init.d support will not work).
after troubleshoot found out the install-recovery.sh is not in execute permission (rwxr--r-- instead of rwxr-xr-x).
by correcting the 'install-recovery.sh' permission, init.d support will work again.
ps;
must install busybox app (do a normal install).
saintsoh said:
just learn something new when i reverted back to stock and re-install zip-init for init.d support.
when flash zip_init.zip and reboot, cwm will ask to "disable recovery flash" - select "NO".
(note: if select "yes", it will give a false positive, 'install-recovery.sh' will not have execute permissions and init.d support will not work).
after troubleshoot found out the install-recovery.sh is not in execute permission (rwxr--r-- instead of rwxr-xr-x).
by correcting the 'install-recovery.sh' permission, init.d support will work again.
ps;
must install busybox app (do a normal install).
Click to expand...
Click to collapse
i got busybox installed, but i'm having status 0 error in CWM. in troubleshooting guide, it says replace the update-binary in zip-init.zip with a working update-binary of your phone and i don't how to do it
dec0der said:
i got busybox installed, but i'm having status 0 error in CWM. in troubleshooting guide, it says replace the update-binary in zip-init.zip with a working update-binary of your phone and i don't how to do it
Click to expand...
Click to collapse
update-binary is in the zip file, just download the latest which is the v2 and re-flash again.
if still doesn't work, try get help from init.d support thread.
i didn't get it working on the first time twice but somehow get it work again again.
saintsoh said:
update-binary is in the zip file, just download the latest which is the v2 and re-flash again.
if still doesn't work, try get help from init.d support thread.
i didn't get it working on the first time twice but somehow get it work again again.
Click to expand...
Click to collapse
it was v2 of zip_init that i use and i think i re flashed it 5x already and still getting that error anyways, thnx 4 ur help bro, godbless!
dec0der said:
it was v2 of zip_init that i use and i think i re flashed it 5x already and still getting that error anyways, thnx 4 ur help bro, godbless!
Click to expand...
Click to collapse
superusers app needed for terminal emulator, fx explorer(root access), busybox and script manager apps installed for root access.
use script manager, look for install-recovery.sh in /etc or system/etc (both r the same directory).
touch su n boot icon, su will turn green n boot will turn blue. reboot.
or
use fx explorer to set file permissions if u do not know linux commands.
google play search for fx explorer app and fx root addon (enable root access).
use root folder, look for install-recovery.sh in system/etc.
touch tool menu below and mount read-write then u can change file permission.
or
if u r familiar with linux commands, u can use terminal emulator to change file permission.
check install-recovery.sh permission is rwxr-xr-x, not other like rwxr--r--.
how2check in emulator, type n press enter:
ls -l etc/inst* ↵
how2change file permission, type n press enter:
su ↵
cd etc ↵
mount -o remount rw /system ↵
chmod 755 install-recovery.sh ↵
exit ↵
exit ↵
done, there shouldnt be any error, reboot.
if not re-flash zip_init.zip, reboot, select "NO" to disable flash recovery.
saintsoh said:
superusers app needed for terminal emulator, fx explorer(root access), busybox and script manager apps installed for root access.
use script manager, look for install-recovery.sh in /etc or system/etc (both r the same directory).
touch su n boot icon, su will turn green n boot will turn blue. reboot.
or
use fx explorer to set file permissions if u do not know linux commands.
google play search for fx explorer app and fx root addon (enable root access).
use root folder, look for install-recovery.sh in system/etc.
touch tool menu below and mount read-write then u can change file permission.
or
if u r familiar with linux commands, u can use terminal emulator to change file permission.
check install-recovery.sh permission is rwxr-xr-x, not other like rwxr--r--.
how2check in emulator, type n press enter:
ls -l etc/inst*
how2change file permission, type n press enter:
su
cd etc
mount -o remount rw /system
chmod 755 install-recovery.sh
exit
exit
done, there shouldnt be any error, reboot.
if not re-flash zip_init.zip, reboot, select "NO" to disable flash recovery.
Click to expand...
Click to collapse
busybox was installed correctly as i can see the folder bin/ xbin. it's rooted already so superuser was in there and i used root explorer file manager. i can't find install-recovery.sh in /etc or system/etc which maybe means that it was not working
dec0der said:
busybox was installed correctly as i can see the folder bin/ xbin. it's rooted already so superuser was in there and i used root explorer file manager. i can't find install-recovery.sh in /etc or system/etc which maybe means that it was not working
Click to expand...
Click to collapse
1) phone is rooted,
2) superuser app installed,
3) busybox app installed,
4) root explorer file manager app installed,
5) no install-recovery.sh in /etc or system/etc?
6) no test.log in /data?
7) re-flash zip_init.zip, reboot, select 'NO' to disable flash recovery?
8) no init.d directory in /etc?
9) in etc/init.d directory, there should have two files 00test n 08setperm. in /etc should have install-recovery.sh file.
10) u dont have these three files?
flashing cant write on system directory, means manufacturer locked the system.
unless u can find way to break the lock.
saintsoh said:
1) phone is rooted,
2) superuser app installed,
3) busybox app installed,
4) root explorer file manager app installed,
5) no install-recovery.sh in /etc or system/etc?
6) no test.log in /data?
7) re-flash zip_init.zip, reboot, select 'NO' to disable flash recovery?
8) no init.d directory in /etc?
9) in etc/init.d directory, there should have two files 00test n 08setperm. in /etc should have install-recovery.sh file.
10) u dont have these three files?
flashing cant write on system directory, means manufacturer locked the system.
unless u can find way to break the lock.
Click to expand...
Click to collapse
1-4 yes, all done
5-10 don't have those files coz i got status 0 error flashing zip_init.zip v2 in CWM
if thats the case, maybe i'll try to flash different stock firmware 1st
dec0der said:
1-4 yes, all done
5-10 don't have those files coz i got status 0 error flashing zip_init.zip v2 in CWM
if thats the case, maybe i'll try to flash different stock firmware 1st
Click to expand...
Click to collapse
try manually put in those files in their respectively directories.
unzip n try putting those files in their respective order.
create a init.d directory in /etc then put those two files 00test n 08setperm into it.
put the install-recovery.sh in /etc, set all permissions to rwxrwxrwx.
(upload manager doesnt allow .sh file, rename install-recovery.sh.txt to install-recovery.sh)
done, reboot n see it works or not.
saintsoh said:
try manually put in those files in their respectively directories.
unzip n try putting those files in their respective order.
create a init.d directory in /etc then put those two files 00test n 08setperm into it.
put the install-recovery.sh in /etc, set all permissions to rwxrwxrwx.
(upload manager doesnt allow .sh file, rename install-recovery.sh.txt to install-recovery.sh)
done, reboot n see it works or not.
Click to expand...
Click to collapse
okay, i'll try that. thnx