Related
Anyone knows how to install busybox?
I've tried to follow some guides but ends up with:
Code:
215:Desktop ricardo$ adb push busybox /data/local
580 KB/s (1083568 bytes in 1.823s)
215:Desktop ricardo$ adb shell
$ su
# cd /system/xbin
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cat /data/local/busybox > busybox
cannot create busybox: not enough memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# dd if=/data/local/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Out of memory
or
$ su
# cd /data/local
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# ./busybox cp /data/local/busybox /system/xbin
cp: can't create '/system/xbin/busybox': Cannot allocate memory
same here. cannot write to rw-mounted /system.
sucks
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
I have the same problem
ricardoft said:
Try my zip file. Woked for me
The only thing that I want to change and I can't is the init.rc file. I tried to mount the / (rootfs) with rw, but every time I restart my device the file is copied, again, from the ramdisk image.
Click to expand...
Click to collapse
What should I do with your files?
Nobody has a solution to this?
I don't think this is a memory issue though, .. added 512mb swap and still it claimed to be out of memory, ..
also I figured maybe hd space .. however when i ln /data/local/tmp/busybox to /system/xbin it had the same error.
I both tried ln from the system and ln from busybox both had same result.
It's not a memory problem! In order to install it you have to be in recovery mode.
Try:
While in recovery mode use adb to connect to our phone. Now transfer the zip file (busybox.zip) to your phone and install it via clockwork recovery -> install zip file -> select my zip file.
can anyone post the proper busybox file cause for some reason the file signature verification failed.
adb push busybox-signed.zip /sdcard/busybox-signed.zip
rebooted phone held down volume button while booting ..
choose recovery, ..
choose install zip from sdcard..
then i see a lot of no and one yes .. so i choose yes but the installation is aborted.
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
it has error during installation at line 4 with your busybox.zip
somethinf like can not chmod
(rooted buzz with stock rom)
Elibongo said:
Just install titanium backup and click on 'problems?' at the bottom. It will install BusyBox for you.
Click to expand...
Click to collapse
Do what this guy said.
titanium install in /sdcard busybox, not in /system/bin (xbin) , so it is not usuable by other apps
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
kevin2516 said:
Do what this guy said.
Click to expand...
Click to collapse
you have read my mind especially since that isn't free software.
hellysmile said:
i have installed it in during recovery mode in /system/xbin
how now to specify PATH for using commands from it?
Click to expand...
Click to collapse
i think you need to create aliases however why install it in xbin anyways then, .. if you need to create aliases or links in bin.. ?
example
$ ln -s /data/local/tmp/busybox ls
$ ./ls
if it is in a path that is included in PATH executing a command will auto look for it in all directories defined in PATH env so basicly you could just create all the directories under /data/local/tmp/bin
and just then append that to PATH env echo $PATH then append :/data/local/tmp/bin to it and busybox should work as well.
Ofloo said:
you have read my mind especially since that isn't free software.
Click to expand...
Click to collapse
titanium backup is free software... look on the market, there's a free version and a donate version.
i have aliases in /system/xbin
they was created after busybox --instal -s
but in system allready exists some commands like ls => i want to use ls from busbox, not from system
and terminal emulator dont anderstand ^[ likes bindings
is there a definitive way to do this. There seems to be no clear way of doing it.
matpol said:
is there a definitive way to do this. There seems to be no clear way of doing it.
Click to expand...
Click to collapse
Maybe this helps:
fang0654 said:
To install:
1) extract and push busybox to your sdcard, reboot into recovery
2) mount /system
3) if you don't have /system/xbin (you should), create it
adb shell:
# mkdir /system/xbin (if necessary)
dd if=/sdcard/busybox of=/system/xbin/busybox
cd /system/xbin
chmod 755 busybox
./busybox --install .
4) reboot and done
OPTIONAL - before rebooting replace the busybox installed by the root process in /system/bin
1) mv /system/bin/busybox /system/bin/busybox.bak
2) cp /system/xbin/busybox /system/bin/busybox
Click to expand...
Click to collapse
from this site: http://forum.xda-developers.com/showthread.php?t=702634
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
matpol said:
The above is pretty straightforward. The only thing is you need to download the zip in the other thread and 'busybox' refers to the binary in the zip rather than the whole directory - as I understand it. Correct me if I am wrong but trying the dd command on the dir will not work.
Click to expand...
Click to collapse
You dont have to extract the binary into a folder, just extract the busybox file direct on your sdcard. Than the dd command should work, on my phone it works fine.
But if not, does the command cat in the adb shell work?
If so, try istead of the dd comand:
Code:
mount /sdcard
cat /sdcard/busybox > /system/xbin/busybox
And remember to start your wildfire in the recovery mode, that was the mistake I had done...
HTC Vision // Desire Z Temporary Rooting
1. Download this package: MegaUpload
2. Copy the content of the package in a folder called "temproot" in your SDCard root.
3. Execute this script:
Code:
#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/
cd /data/local/tmp/
chmod 755 *
./rageagainstthecage-arm5.bin
ps
4. Restart Terminal Emulator
5. Execute this script:
Code:
#!/system/bin/sh
/data/local/tmp/busybox killall rageagainstthecage-arm5.bin
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
/data/local/tmp/busybox cp /sdcard/temproot/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /sdcard/temproot/su /system/bin/su
/data/local/tmp/busybox cp /sdcard/temproot/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
Now your phone is temporairily rooted and you can even get root on adb.
Thanks to:
*- C-Skills for the exploit
*- Guys in G2 section for testing it.
Sweet
but what do we do to get full root access?
There is no full root yet for either this device or g2. You will see that later
M9x3mos said:
There is no full root yet for either this device or g2. You will see that later
Click to expand...
Click to collapse
excited
wonder if the "z" and G2 can use the same Recovery image and Roms..or wil it be like htc magic and My touch ?
G2 and Z are the same device.... HTC Vision.
Radio ROMs and BootLoaders should be compatible, we only need someone that can verify, but AFAIK a G2 owner flashed a full Desire Z ROM and worked without problems.
kholk said:
G2 and Z are the same device.... HTC Vision.
Radio ROMs and BootLoaders should be compatible, we only need someone that can verify, but AFAIK a G2 owner flashed a full Desire Z ROM and worked without problems.
Click to expand...
Click to collapse
any idea if the G2 is a test unit or retail unit? i want senseui (sad i know, but im a sucker for nice graphic)
Correction. The Desire Z rom currently be flashed to G2 but the PC10IMG.zip original G2 rom does work on the Desire Z
I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"
Anyone try overclocking it yet?
waiting89 said:
I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"
Click to expand...
Click to collapse
Are there any errors?
Please provide more details, it's only a file copy...
kholk said:
Are there any errors?
Please provide more details, it's only a file copy...
Click to expand...
Click to collapse
Link is down kind sir. I found this one Droid2Root.rar from another forum.
waiting89 said:
I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"
Click to expand...
Click to collapse
It gives you an axxs denied when you try that. says "cp: permission denied." I can't ls inside of /data either.
do changes persist?
If I do this temp root and install busybox or tether, will the changes be wiped out on restart?
"cp: permission denied." Yes this is the error code I get.
"export PATH=/data/local/bin:$PATH
$ $ #! /system/bin/sh
$ cp -R /mnt/sdcard/temproot/* /data/local/tmp/
cp: permission denied
$"
That's exactly what it appears on the terminal.
I read this on androidspin :
If you root your new G2 phone, HTC has embedded a chip that will detect this and return the phone back to its original factory settings. So much for open source!
They can do this?
The file is no longer available. Can someone repost it?
Thanks
Hmm, yep same problem, cp gives me a permission denied, and the folder /data is a system file seems like we don't have any access to it. on the example, seems like there's # instead of $ which means it has admin access, how did you get to that state? sorry android noob here :-\
stian230 said:
I read this on androidspin :
If you root your new G2 phone, HTC has embedded a chip that will detect this and return the phone back to its original factory settings. So much for open source!
They can do this?
Click to expand...
Click to collapse
Actually no, and its covered in many threads, and I'm sure the op doesn't want the discussion started again.
There isn't any chip that will magically transform your HTC Vision in an airplane / automobile / house / cigarette industry.
script?
Could somebody help with packaging this as a script so we could re-root simply?
I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA updated T-mobile G2.... either for temp-root or permanent root..I have tried the ADB/Rage/gfree method of rooting and I getting an ERROR on the last part instructions.... ""## mkdir failed for /system/xbin, File exists"
My main question is if anyone could check to see if their version of the Visionary app is the version 7 or r7...if so could you please used titanium backup to send me a copy of the file....
thank you so so much...
Not sure why a specific older version of Visionary would work if the newer (or older) versions would not.
Regarding your error message, is that when you run the command:
/data/local/tmp/root
Click to expand...
Click to collapse
If so you will note that the instructions on the wiki state immediately below that: You may see an error message along the lines of "mkdir: /system/xbin already exists", but if so you can ignore that, the rest of the script should still run ok.
If you boot into the bootloader (press volume down while powering on device) do you have S-OFF? If so you know that the GFREE part at least did work.
sammd301 said:
I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA updated T-mobile G2.... either for temp-root or permanent root..I have tried the ADB/Rage/gfree method of rooting and I getting an ERROR on the last part instructions.... ""## mkdir failed for /system/xbin, File exists"
My main question is if anyone could check to see if their version of the Visionary app is the version 7 or r7...if so could you please used titanium backup to send me a copy of the file....
thank you so so much...
Click to expand...
Click to collapse
As has been explained in the Development section, be VERY CAREFUL with Visionary as it is known to brick phones.
When I first got my DZ I was eager to Root and uses V14 to obtain root but remember that this is not a 'Real' S-OFF. GFREE is the best and safest method to use. I was a lucky newbie who didn't end up with a brick!
raitchison said:
Not sure why a specific older version of Visionary would work if the newer (or older) versions would not.
Regarding your error message, is that when you run the command:
If so you will note that the instructions on the wiki state immediately below that: You may see an error message along the lines of "mkdir: /system/xbin already exists", but if so you can ignore that, the rest of the script should still run ok.
If you boot into the bootloader (press volume down while powering on device) do you have S-OFF? If so you know that the GFREE part at least did work.
Click to expand...
Click to collapse
yes you are exactly right...when I input in this command " /data/local/tmp/root" then I got back this error "mkdir failed for /system/xbin, File exists" you see the difference, instead of "already exits" I did ignore the error message but when I tried to used a root required app like root explorer...It states the phone needs to rooted before the app can work....Lastly when I enter into the boot loader "I indeed notice that S-OFF" the problem is that the phone is not rooted not even temporary...as far as visionary r7 goes I recall after the OTA, it did work on my phone for temporary rooting...it is when I attempted to used visionary r14 to obtain permanent root that visionary r7 was overwritten by r14...which doesn't work even for temp rooting thanks for your input
gbarayah said:
As has been explained in the Development section, be VERY CAREFUL with Visionary as it is known to brick phones.
When I first got my DZ I was eager to Root and uses V14 to obtain root but remember that this is not a 'Real' S-OFF. GFREE is the best and safest method to use. I was a lucky newbie who didn't end up with a brick!
Click to expand...
Click to collapse
right now...neither method works not the "visionary r14 or ADB/RAGE/GFREE" I wouldn't mind using either method, the problem is that ADB/Rage/GFREE METHOD keep giving this error message "mkdir failed for /system/xbin, File exists" which I have done a ton of research and still can find a fixed,
sammd301 said:
yes you are exactly right...when I input in this command " /data/local/tmp/root" then I got back this error "mkdir failed for /system/xbin, File exists" you see the difference, instead of "already exits" I did ignore the error message but when I tried to used a root required app like root explorer...It states the phone needs to rooted before the app can work....Lastly when I enter into the boot loader "I indeed notice that S-OFF" the problem is that the phone is not rooted not even temporary...as far as visionary r7 goes I recall after the OTA, it did work on my phone for temporary rooting...it is when I attempted to used visionary r14 to obtain permanent root that visionary r7 was overwritten by r14...which doesn't work even for temp rooting thanks for your input
Click to expand...
Click to collapse
Crap I typed up this response but I guess I didn't submit it because it's gone...
OK what you are saying is actually good news, it means you had temp root at one point or gfree would not have worked (you would not have S-OFF now)
If you can get temp root to work even one more time you can flash ClockWorkMod recovery and then load a custom/pre-rooted ROM.
I do suspect that you have messed up your system with your various attempts at rooting (especially the fact that you used visionary and other deprecated root methods) and you need to wipe your system and start over with either a custom ROM or a pre-rooted stock ROM.
I would start by running this section of the root process:
ON YOUR PHONE:
1. Launch Terminal Emulator
2. Execute /data/local/tmp/rage
3. Wait for the message: "Forked #### childs."
4. Menu > Reset Term - Terminal Emulator will exit.
5. Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
Click to expand...
Click to collapse
If you have a # prompt that means you have temp root, from there I would use flash_image to flash ClockWorkMod 3.0.5 to the phone (see guide)
Get ClockWorkMod here
Once you have CWM installed you can basically ignore your current OS and flash whatever you want, you can go with a custom ROM or if you don't want to do that you can go with a pre-rooted stock ROM (see this thread). In any case I would definitely wipe first (from within CWM)
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
ianmcquinn said:
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
Click to expand...
Click to collapse
Right now I going to try to use this command to fix the error and if it doesn't work, I will then try to flash a custom and see how that goes...Update will be posted as I go along....thanks for the kind help....
raitchison said:
Crap I typed up this response but I guess I didn't submit it because it's gone...
OK what you are saying is actually good news, it means you had temp root at one point or gfree would not have worked (you would not have S-OFF now)
If you can get temp root to work even one more time you can flash ClockWorkMod recovery and then load a custom/pre-rooted ROM.
I do suspect that you have messed up your system with your various attempts at rooting (especially the fact that you used visionary and other deprecated root methods) and you need to wipe your system and start over with either a custom ROM or a pre-rooted stock ROM.
I would start by running this section of the root process:
If you have a # prompt that means you have temp root, from there I would use flash_image to flash ClockWorkMod 3.0.5 to the phone (see guide)
Get ClockWorkMod here
Once you have CWM installed you can basically ignore your current OS and flash whatever you want, you can go with a custom ROM or if you don't want to do that you can go with a pre-rooted stock ROM (see this thread). In any case I would definitely wipe first (from within CWM)
Click to expand...
Click to collapse
I will attempt to flash ClockWorkmod, once I try out "ianmcquinn" suggesting in trying to fix the rooting error...thanks for the help
ianmcquinn said:
Yeah, flashing a pre-rooted custom ROM is probably your cleanest solution at this point. If you want to try and fix what you have though, you can try the following steps:
1. Follow the instructions to get temp root with rage again.
2. In Terminal, try these commands and look for an error at any point (this is what the root script is actually doing, with the addition of the deletion of the xbin file/directory since that seems to be what is messing up):
Code:
# /data/local/tmp/busybox killall rage
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
# rm -rf /system/xbin
# mkdir /system/xbin
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
# chmod 4755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/bin
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
# cp /sdcard/su /system/bin/su
# chmod 4755 /system/bin/su
Flashing a custom ROM is probably easier though.
Click to expand...
Click to collapse
Yes I used the wiki instruction to gain temporary root on the phone and proceeded to tryout the above command...I got mostly error with the command below is what I en-counted as I enter the command....
# /data/local/tmp/busybox killall rage
No error here just # prompt
# mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
No error again just # prompt
# rm -rf /system/xbin
Error "rm failed for -rf, Read-only file system"
# mkdir /system/xbin
Error "mkdir failed for /system/xbin, File exists"
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
Error "cp: can't stat '/system/xbin/busybox': Not a directory"
# chmod 4755 /system/xbin/busybox
Error "Unable to chmod /system/xbin/busybox: Not a directory"
# /system/xbin/busybox --install -s /system/bin
Error "/system/xbin/busybox: not found"
# cp /sdcard/Superuser.apk /system/app/Superuser.apk
Error "cp: not found"
# cp /sdcard/su /system/bin/su
Error "cp: not found"
# chmod 4755 /system/bin/su
Error "Unable to chmod /system/bin/su: No such file or directory
I am now going to attempt the Clockwork custom rom flash..
Folks victory is mine....No, VICTORY IS OURS, I sincerely like to thank all of you all, who replied with helpful suggesting...especially the following members "raitchison" from West Hill, CA and "ianmcquinn" a true senior member of xda-developer.
This is what I did to finally get the phone rooted....
I took "Raitchison" advice by trying to use flash_image to flash ClockWorkMod recovery... but during the process I could not get pass copying file to the phone root system folder usind android terminal emulator ...so I input this command "chmod 777/system" to gain write access to the folder...after doing that I manually moved busybox file to system folder and attempted a rooting the phone using the rooting instruction from the HTC G2/DESIRE Z wiki site...at...
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
And this time around, everything went as normal after rooting the phone I open root required app and Wa La...no error message...
Guys I once again wants thank you all for the support....I also looked forward to help out others facing the same issue...so if anyone has encounter the same or similar issue please feel free to post here and I will response....
Can any one help me I am trying to close this thread...How do I go about doing it....thanks
There is no need to close the thread, if anyone has a similar problem and finds it via search they can come in here and bring the discussion back up, otherwise if there is no activity it will naturally fall to the bottom of the thread list.
It works for me I just did it yday using visionary and gfree all on my phone weird that it doesn't work for you?
Sent from my Liquid Metal using XDA Premium App
I'm a stock kind of guy. If I want to change things like launchers or whatever I can do it myself once I get root. Plus I like quickoffice and a lot of ROMs like to remove it. Here's what I did.
You can download the stock firmware from samfirmware.com. Flash using Odin. Do this if you want to return to stock 2.3.5. If you are an AT&T customer, you can get the 2.3.6 OTA at this point. I'm still working on pulling the OTA for non AT&T customers.
If you can't get the OTA because you have a custom recovery flashed, see the bottom of this post for the stock recovery. Unrar it and flash using the PDA mode in Odin.
Once you're on 2.3.6, flash CWM from this thread http://forum.xda-developers.com/showthread.php?t=1458153
At this point, there is no need whatsoever to find an exploit in the system in order to try to "root" this phone. CWM provides root access using adb.
Boot into CWM by holding the down volume and the power button. At this point your phone already has root. The only things missing are to push the su and busybox binaries and the superuser.apk. Go into mounts and storage and mount /system
Since I'm lazy, I downloaded DooMLoRD's rooting script here http://forum.xda-developers.com/showthread.php?t=1321582. Note the script does not work on our phone and we don't need the zerg exploit. All we need are the binaries and a way to push them to our phone. DooMLoRD also handily includes an adb shell
In the same folder as runme.bat, make runme2.bat in notepad and paste in the following:
Code:
@echo --- creating temporary directory
@files\adb shell "cd /data/local && mkdir tmp"
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/ && rm *"
@echo --- pushing busybox
@files\adb push files\busybox /data/local/tmp/.
@echo --- correcting permissions
@files\adb shell "chmod 755 /data/local/tmp/busybox"
@echo --- copying busybox to /system/xbin/
@files\adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/xbin/busybox"
@echo --- correcting permissions
@files\adb shell "chmod 04755 /system/xbin/busybox"
@echo --- installing busybox
@files\adb shell "/system/xbin/busybox --install -s /system/xbin"
@files\adb shell "rm -r /data/local/tmp/busybox"
@echo --- pushing SU binary
@files\adb push files\su /system/bin/su
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/bin/su"
@echo --- correcting permissions
@files\adb shell "chmod 06755 /system/bin/su"
@echo --- correcting symlinks
@files\adb shell "rm /system/xbin/su"
@files\adb shell "ln -s /system/bin/su /system/xbin/su"
@echo --- pushing Superuser app
@files\adb push files\Superuser.apk /system/app/.
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/; rm *"
@echo ALL DONE!!!
@pause
One more final note, after you reboot, update the superuser apk from Google Play. Reboot again before trying to update su or it will fail. Update busybox with the stericson app if you want but it's not necessary.
This method will work on stock 2.3.5 as well. To unroot, just open an adb shell and delete busybox, su, and superuser.apk
Hi Nardholio,
One quick clarifying question: if I flash back to stock 2.3.5 using Kies, will all my apps and personal data get wiped?
Thanks!
I've only had this phone for 2 days, but it looks like Kies will only flash a version you already have (that's not an upgrade) if you force it to initialize the phone. So yes. Hopefully someone will pull the stock recovery in a flashable package for us eventually. If you really want to do this and save your data in the meantime, flash a rooted 2.3.5 ROM (or if you installed CWM on top of non-rooted stock 2.3.5 you could use this same script to root it), then back up your data with Titanium to a safe place (external SD) before wiping the phone and getting the OTA.
Note, installing CWM doesn't appear to increase your flash counter so if you're currently on stock 2.3.5 and for some reason can't OTA to 2.3.6 AND you want to save your data and you care about your flash counter, rooting your 2.3.5 to save your apps seems to be the way to go.
Nardholio said:
I think you have to be an AT&T customer to get this.
Click to expand...
Click to collapse
So it's not enough to have the AT&T version of the phone, you actually have to have a valid AT&T SIM as well? About phone shows 2.3.5 and my phone is just telling me I'm up to date.
worked like a charm! thanks! this was the one thing that annoyed me, having to downgrade to be able to have root. i prefer to have 2.3.6 mainly because of the ability to have video chat on google talk.
Ahhhh, I wish I'd seen this thread before I flashed a custom kernal. Now I'm running ardatdat on the stock rom.
roothorick said:
So it's not enough to have the AT&T version of the phone, you actually have to have a valid AT&T SIM as well? About phone shows 2.3.5 and my phone is just telling me I'm up to date.
Click to expand...
Click to collapse
I have the same problem. Hoping someone will post a stock or rooted 2.3.6 ROM, or ICS will come out soon.
oldnoob said:
I have the same problem. Hoping someone will post a stock or rooted 2.3.6 ROM, or ICS will come out soon.
Click to expand...
Click to collapse
is there a way to create a flashable rom from a nandroid backup? or can someone flash another persons nandroid backup? i can go back to untouched stock and do a backup and post it if it could be used...
I'm sure there's a way to do it, I just don't know how. At this point it might be better to just wait for ICS to drop.
Wat does it matter having a certain build number? As long as everything works fine who cares
Sent from my SAMSUNG-SGH-I927 using XDA
http://db.tt/LbIu6LTv
Try this one, it's called megatron root. It's the only root that worked on lg thrill on gingerbread maybe it will work here.
Sent from my HTC One X using xda premium
deleted post
Will flashing CWMR prohibit the OTA ICS Update?
Nardholio said:
I'm a stock kind of guy. If I want to change things like launchers or whatever I can do it myself once I get root. Plus I like quickoffice and a lot of ROMs like to remove it. Here's what I did.
You can download the stock firmware from samfirmware.com. Flash using Odin. Do this if you want to return to stock 2.3.5. If you are an AT&T customer, you can get the 2.3.6 OTA at this point. I'm still working on pulling the OTA for non AT&T customers.
If you can't get the OTA because you have a custom recovery flashed, see the bottom of this post for the stock recovery. Unrar it and flash using the PDA mode in Odin.
Once you're on 2.3.6, flash CWM from this thread http://forum.xda-developers.com/showthread.php?t=1458153
At this point, there is no need whatsoever to find an exploit in the system in order to try to "root" this phone. CWM provides root access using adb.
Boot into CWM by holding the down volume and the power button. At this point your phone already has root. The only things missing are to push the su and busybox binaries and the superuser.apk. Go into mounts and storage and mount /system
Since I'm lazy, I downloaded DooMLoRD's rooting script here http://forum.xda-developers.com/showthread.php?t=1321582. Note the script does not work on our phone and we don't need the zerg exploit. All we need are the binaries and a way to push them to our phone. DooMLoRD also handily includes an adb shell
In the same folder as runme.bat, make runme2.bat in notepad and paste in the following:
Code:
@echo --- creating temporary directory
@files\adb shell "cd /data/local && mkdir tmp"
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/ && rm *"
@echo --- pushing busybox
@files\adb push files\busybox /data/local/tmp/.
@echo --- correcting permissions
@files\adb shell "chmod 755 /data/local/tmp/busybox"
@echo --- copying busybox to /system/xbin/
@files\adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/xbin/busybox"
@echo --- correcting permissions
@files\adb shell "chmod 04755 /system/xbin/busybox"
@echo --- installing busybox
@files\adb shell "/system/xbin/busybox --install -s /system/xbin"
@files\adb shell "rm -r /data/local/tmp/busybox"
@echo --- pushing SU binary
@files\adb push files\su /system/bin/su
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/bin/su"
@echo --- correcting permissions
@files\adb shell "chmod 06755 /system/bin/su"
@echo --- correcting symlinks
@files\adb shell "rm /system/xbin/su"
@files\adb shell "ln -s /system/bin/su /system/xbin/su"
@echo --- pushing Superuser app
@files\adb push files\Superuser.apk /system/app/.
@echo --- cleaning
@files\adb shell "cd /data/local/tmp/; rm *"
@echo ALL DONE!!!
@pause
One more final note, after you reboot, update the superuser apk from Google Play. Reboot again before trying to update su or it will fail. Update busybox with the stericson app if you want but it's not necessary.
This method will work on stock 2.3.5 as well. To unroot, just open an adb shell and delete busybox, su, and superuser.apk
Click to expand...
Click to collapse
Thanks for all of your info.
I have gotten myself back to bone stock ATT 2.3.5 using samfirmware and then Kies updater to wipe and reload and then used the OTA updater to get me to 2.3.6. As far as the OTA system says, I am up to date. The problem is I can't use Titanium Backup to get all my apps back if I am not rooted or use this flashable CWMR you linked to. (or any other apps that depend on root.
I have no technical issues with doing this but I am scared that I will have to start over, and go back square one when the ICS drops if i have CWMR on my system. What do you think about this? Should I wait here with stock 2.3.6 and just check the OTA updater every 24 hours or go ahead and flash CWMR?
Thanks,
Mac
macwhite1 said:
Thanks for all of your info.
I have gotten myself back to bone stock ATT 2.3.5 using samfirmware and then Kies updater to wipe and reload and then used the OTA updater to get me to 2.3.6. As far as the OTA system says, I am up to date. The problem is I can't use Titanium Backup to get all my apps back if I am not rooted or use this flashable CWMR you linked to. (or any other apps that depend on root.
I have no technical issues with doing this but I am scared that I will have to start over, and go back square one when the ICS drops if i have CWMR on my system. What do you think about this? Should I wait here with stock 2.3.6 and just check the OTA updater every 24 hours or go ahead and flash CWMR?
Thanks,
Mac
Click to expand...
Click to collapse
You might as well just wait should be any day now. That way you could get the update when it is available.
Sent from my SAMSUNG-SGH-I927R using xda app-developers app
You should be able to flash the stock recovery on top of CWM and you'll be good to go for OTAs, although there isn't much point in *just* flashing CWM if you aren't going to deviate from stock otherwise.
One more thing, I found an even easier root method. If you download the CWM flashable version of superuser from http://androidsu.com/superuser/ and flash CWM, and then flash Superuser, bam, instant root!
Hi I have used odin and CWMR_recovery.tar.md5 flashed ok, but how do I flash superuser apk etc. I have the file runme2.bat ?? but how do I use it ?
This bit for me is unclear, can anyone assist and make this bit a little clearer for "simple is as simple does."
Thanks
pgunning1 said:
Hi I have used odin and CWMR_recovery.tar.md5 flashed ok, but how do I flash superuser apk etc. I have the file runme2.bat ?? but how do I use it ?
This bit for me is unclear, can anyone assist and make this bit a little clearer for "simple is as simple does."
Thanks
Click to expand...
Click to collapse
You dont flash an apk file you only flash zip files. if you go into the ROM zip/system/app just drop the superuser apk into there and then flash that rom. When you boot up the apk file you put in the ROM will turn into an app on your phones app drawer. Or you could just install superuser in market.:fingers-crossed:
Thanks for the quick reply, Ive just installed superuser and busybox and supersu ? superuser installed as did the other two, superuser opens but busybox says it cannot install as root is not complete/accessible. the flash of cmw by odin went ok and have rebooted no probs, I have not change operating system just trying to root 2.3.6 gingerbread ! any help appreciated so close yet so far LOL
ATB
pgunning1 said:
Thanks for the quick reply, Ive just installed superuser and busybox and supersu ? superuser installed as did the other two, superuser opens but busybox says it cannot install as root is not complete/accessible. the flash of cmw by odin went ok and have rebooted no probs, I have not change operating system just trying to root 2.3.6 gingerbread ! any help appreciated so close yet so far LOL
ATB
Click to expand...
Click to collapse
just by installing superuser doesnt root your phone, you have to flash the zip file to root your phone.
hi, quick question .
im trying to remount the system folder to R\W , but seems like no luck .
adb remount
*permission denied
adb shell
Code:
C:\android sdk\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]:/ #
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\android sdk\sdk\platform-tools>adb push C:\Users\HOME\Desktop\build.prop /sys
tem
failed to copy 'C:\Users\HOME\Desktop\build.prop' to '/system/build.prop': Permi
ssion denied
shell - fail
normal remount -fail
whats next.any suggestions?
cant do that yet, you need kernel with unsecure adb .
Helloworld294 said:
cant do that yet, you need kernel with unsecure adb .
Click to expand...
Click to collapse
Means I can't tweak my phone safely? (1 bootloop and I'm on stock again? )
subwoffer13 said:
Means I can't tweak my phone safely? (1 bootloop and I'm on stock again? )
Click to expand...
Click to collapse
You bootloop you're on stock again, with formatted /data/media of course.
EDIT: So I downloaded adb insecure from playstore by chainfire and it seems to work actually. Its $2 though.
Sent from my LG-D852 using Tapatalk
Helloworld294 said:
You bootloop you're on stock again, with formatted /data/media of course.
EDIT: So I downloaded adb insecure from playstore by chainf
ire and it seems to work actually. Its $2 though.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Well, just bought it too.going to slepp right now, tomorrow hopefully I'll be able to push and pull files with adb.
subwoffer13 said:
Well, just bought it too.going to slepp right now, tomorrow hopefully I'll be able to push and pull files with adb.
Click to expand...
Click to collapse
Before pulling/pushing anything from system
run 'chmod 777 /system'
And before pushing/pulling any file chmod 666 the file and after dont ever forget to chmod 644 any system or data file after pushing or else you gonna end up in bootloop.
Sent from my LG-D852 using Tapatalk
Helloworld294 said:
Before pulling/pushing anything from system
run 'chmod 777 /system'
And before pushing/pulling any file chmod 666 the file and after dont ever forget to chmod 644 any system or data file after pushing or else you gonna end up in bootloop.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
.ok , i am a bit confused .i understand that every time im pulling or pushing i should fix the permissions. Bit what is the exact order ?
Shouldn't i just make sure the file im only pushing is 644 (rw-r-r)?
Lets say for example , i want to push stock "build.prop" to system .
What are the steps?
subwoffer13 said:
.ok , i am a bit confused .i understand that every time im pulling or pushing i should fix the permissions. Bit what is the exact order ?
Shouldn't i just make sure the file im only pushing is 644 (rw-r-r)?
Lets say for example , i want to push stock "build.prop" to system .
What are the steps?
Click to expand...
Click to collapse
Mount everything and do su and all that then chmod 777 /system
Then do the push "adb push 'source file location' /system/build.prop
Then do chmod 644 /system/build.prop
All done.
Sent from my LG-D852 using Tapatalk