Hi! I've been all day trying to install a recovery on my Xperia S, but to no result. At least, I'm always able to flash the stock kernel back.
I've tried a lot of methods (DoomLord's modified kernel, TWRP, RecoverX,...), but in the end, the result is the same. The installers/flashers report an OK, i boot the phone and start tapping the screen on the Sony logo. In some cases it ignores me and goes on to the Xperia logo (a normal boot), or in other cases the Sony logo disappears and all I get is a black screen.
Can anybody help me?
If you are root ;
http://forum.xda-developers.com/showthread.php?t=2634382
Xavali7 said:
Hi! I've been all day trying to install a recovery on my Xperia S, but to no result. At least, I'm always able to flash the stock kernel back.
I've tried a lot of methods (DoomLord's modified kernel, TWRP, RecoverX,...), but in the end, the result is the same. The installers/flashers report an OK, i boot the phone and start tapping the screen on the Sony logo. In some cases it ignores me and goes on to the Xperia logo (a normal boot), or in other cases the Sony logo disappears and all I get is a black screen.
Can anybody help me?
Click to expand...
Click to collapse
On most custom kernels, you need to keep on pressing the volume buttons when you see the Sony logo (or doom kernel logo) instead of tapping on the logo. For doom kernel -
Volume up - Cwm
Camera - TWRP
Sent from my Xperia S using Tapatalk
Zorbeyd said:
If you are root ;
http://forum.xda-developers.com/showthread.php?t=2634382
Click to expand...
Click to collapse
I follow the Method 3th, but it doesn't work. There is no Blue or any other LED appear.
My Device: Sony Xperia S lt26i, JB4.1.2, 6.2.B.1.96, rooted.
Code:
[email protected]:/system/bin # ls -l *.tar
-rwxr-xr-x root shell 3041280 2014-02-25 01:43 cwmrecovery.tar
-rwxr-xr-x root shell 5314560 2014-02-25 01:43 recovery.tar
[email protected]:/system/bin # md5sum *.tar
0beb12af614c79b17ddf10ff368e8d30 cwmrecovery.tar
e7ea2e3f8154ca88d0993119daf67188 recovery.tar
[email protected]:/system/bin # cd ../etc/
[email protected]:/system/etc # ls -l pre_hw_config.sh step2.sh
-rwxr-xr-x root shell 801 2014-02-25 01:46 pre_hw_config.sh
-rwxr-xr-x root shell 3397 2014-02-25 01:46 step2.sh
[email protected]:/system/etc # md5sum pre_hw_config.sh step2.sh
665738dead1c009c4cb3b2d5af400d4b pre_hw_config.sh
aa2990c79269ae335dee8aab5875b978 step2.sh
[email protected]:/system/etc # uname -a
Linux localhost 3.4.0+1.0.21100-313065-g1ccebb5-00193-gcbc50fc #1 SMP PREEMPT Tue Jul 23 15:55:38 2013 armv7l GNU/Linux
Nothing, no blue LED appears, and wether I press volume up or down, it goes from the SONY logo to the XPERIA logo and boots normally... :S
yorks.yang said:
I follow the Method 3th, but it doesn't work. There is no Blue or any other LED appear.
My Device: Sony Xperia S lt26i, JB4.1.2, 6.2.B.1.96, rooted.
Code:
[email protected]:/system/bin # ls -l *.tar
-rwxr-xr-x root shell 3041280 2014-02-25 01:43 cwmrecovery.tar
-rwxr-xr-x root shell 5314560 2014-02-25 01:43 recovery.tar
[email protected]:/system/bin # md5sum *.tar
0beb12af614c79b17ddf10ff368e8d30 cwmrecovery.tar
e7ea2e3f8154ca88d0993119daf67188 recovery.tar
[email protected]:/system/bin # cd ../etc/
[email protected]:/system/etc # ls -l pre_hw_config.sh step2.sh
-rwxr-xr-x root shell 801 2014-02-25 01:46 pre_hw_config.sh
-rwxr-xr-x root shell 3397 2014-02-25 01:46 step2.sh
[email protected]:/system/etc # md5sum pre_hw_config.sh step2.sh
665738dead1c009c4cb3b2d5af400d4b pre_hw_config.sh
aa2990c79269ae335dee8aab5875b978 step2.sh
[email protected]:/system/etc # uname -a
Linux localhost 3.4.0+1.0.21100-313065-g1ccebb5-00193-gcbc50fc #1 SMP PREEMPT Tue Jul 23 15:55:38 2013 armv7l GNU/Linux
Click to expand...
Click to collapse
Did you set permissions of scripts to 755?
Zorbeyd said:
Did you set permissions of scripts to 755?
Click to expand...
Click to collapse
Yes. Please see the code section I POST.
rwx -->7
r-x --> 5
Code:
[email protected]:/system/bin # ls -l *.tar
-rwxr-xr-x root shell 3041280 2014-02-25 01:43 cwmrecovery.tar
-rwxr-xr-x root shell 5314560 2014-02-25 01:43 recovery.tar
[email protected]:/system/etc # ls -l pre_hw_config.sh step2.sh
-rwxr-xr-x root shell 801 2014-02-25 01:46 pre_hw_config.sh
-rwxr-xr-x root shell 3397 2014-02-25 01:46 step2.sh
yorks.yang said:
Yes. Please see the code section I POST.
rwx -->7
r-x --> 5
Code:
[email protected]:/system/bin # ls -l *.tar
-rwxr-xr-x root shell 3041280 2014-02-25 01:43 cwmrecovery.tar
-rwxr-xr-x root shell 5314560 2014-02-25 01:43 recovery.tar
[email protected]:/system/etc # ls -l pre_hw_config.sh step2.sh
-rwxr-xr-x root shell 801 2014-02-25 01:46 pre_hw_config.sh
-rwxr-xr-x root shell 3397 2014-02-25 01:46 step2.sh
Click to expand...
Click to collapse
Oh sorry.
Can you put this " busybox " to /system/xbin folder with 755 permissions?
Link : http://d-h.st/LU0
Zorbeyd said:
Oh sorry.
Can you put this " busybox " to /system/xbin folder with 755 permissions?
Click to expand...
Click to collapse
Good, it works!
is the busybox problem? I had install it from google play, the latest version.
yorks.yang said:
Good, it works!
is the busybox problem? I had install it from google play, the latest version.
Click to expand...
Click to collapse
Hell yeah! :fingers-crossed:
When busybox version changes, i guess some busybox commands change occured. So, some codes on pre-hw and step2 scripts belongs this version of busybox.
Will that fix my problem too?
Xavali7 said:
Will that fix my problem too?
Click to expand...
Click to collapse
This only about installing recovery,
How can be able to fix it?
Whats your problem?? We need more details with it..
Well, I can't say much more than what I already did on the first post. I've tried a lot of methods to install the recovery, but none of them work. I even tried what Zorbeyd posted here, but it didn't work neither.
The results are always similar. Either the phone boots normally (ignoring any key combination I press), or it goes to a black screen after the Sony logo. I'm always able to go back flashing the stock rom with Flashtool, but I wanted to try KitKat, and not having a recovery prevents me from doing that...
PS: I tried method 1 on the thread Zorbeyd linked. Should I try method 3? I didn't, because I don't know how to hange those permissions on the folders. Could you give me some direction?
Okay, I looked it up, and did method 3. It doesn't work, the phone boots normally, and no blue LED appears...:crying:
Xavali7 said:
Well, I can't say much more than what I already did on the first post. I've tried a lot of methods to install the recovery, but none of them work. I even tried what Zorbeyd posted here, but it didn't work neither.
The results are always similar. Either the phone boots normally (ignoring any key combination I press), or it goes to a black screen after the Sony logo. I'm always able to go back flashing the stock rom with Flashtool, but I wanted to try KitKat, and not having a recovery prevents me from doing that...
PS: I tried method 1 on the thread Zorbeyd linked. Should I try method 3? I didn't, because I don't know how to hange those permissions on the folders. Could you give me some direction?
Click to expand...
Click to collapse
If you share logs about Method 1 , we can help you.
I guess electronics work that way sometimes... I did the same steps again, and now it's working!
Thanks guys, problem solved! Admins, you can close the thread now! :good:
Zorbeyd said:
Oh sorry.
Can you put this " busybox " to /system/xbin folder with 755 permissions?
Link
Click to expand...
Click to collapse
thank you man so much i had same problem and this solved it thank again
Related
As everybody knows, Motorola and most of other android phones have locked the bootloader,
so repacking boot.img will not boot.
I see the init.xxx.rc files are modified in Cyanogenmod series ROMS, but I checked they
did not repacked boot.img( files are not from boot.img)
can somebody tell me how did they do that?
I am making a programm that works like bootmenu but I don't want replace logwrapper, I wish
I could add an exec command in the rc file
well, I saw there's 2nd-init. answered by myself..
~ # ls -l /init.rc
ls -l /init.rc
-rw-r--r-- 1 root root 17507 Dec 14 14:26 /init.rc
~ # ls -l /system/bootmenu/2nd-init/init.rc
ls -l /system/bootmenu/2nd-init/init.rc
-rw-r--r-- 1 root root 17507 Aug 1 2008 /system/bootmenu/2nd-init/init.rc
~ #
========
seems I can't make easier than the way bootmenu does..
This really do not know,but deliberately over the top with your Google Translation。。。
[Acer _AV041_A100_1.037.00_ww_gen1]
root
Can be successfully???
alexsec said:
[Acer _AV041_A100_1.037.00_ww_gen1]
root
Can be successfully???
Click to expand...
Click to collapse
ZN's method still works just fine.
http://forum.xda-developers.com/showthread.php?t=1531646
i can't root!
i can't root!
Verify the device is showing under the device manager, usb debugging is turned on, and that it is being run as administrator.
What OS are you using?
i have the same problem. Can't root after the recent update. using W7, executing it with and without administrator rights. Executing with administrator rights it says something of ADB.
alexsec said:
i can't root!
Click to expand...
Click to collapse
Updating script. Try once again.
rooted!! thanks!!
How to Updating script. Try once again.
@ ZeroNull, can you confirm whether ICS_rooting_A10x_A5xx works for the latest build?
Build number
Acer_A100_2.001.01_COM_GEN2
I have been unsuccessful so far:
==========================================
Preparation is finished.
-
Executing of the main script.
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!
I can confirm that I successfully rooted my A100 using ZeroNull's simple method (http://forum.xda-developers.com/showthread.php?t=1531646)
Build number: Acer_AV041_A100_1.037.00_WW_GEN1
I didn't even use the new script, I'm still using the old one (ICS_rooting.zip)
Unfortunately I can also confirm problems with recent updates of the SuperUser APK (It did not assign the correct Group ID), but apparently they were fixed in the latest update (v3.1.3)
Good Luck.
---------- Post added at 10:30 AM ---------- Previous post was at 10:05 AM ----------
alexsec said:
i can't root!
Click to expand...
Click to collapse
alexsec said:
How to Updating script. Try once again.
Click to expand...
Click to collapse
Hi alexsec, did you try with the new script, it creates a different directory than the old script did, and it uses the mkdir -p option so it creates any parent directories it needs:
Code:
adb shell "mkdir -p /data/local/tmp"
adb push tools /data/local/tmp
adb shell "chmod 0755 /data/local/tmp/mempodroid"
And it does a better job by waiting longer for the tablet to reboot:
Code:
rem Wait reboot tablet
for /L %%i in (1,1,7000000) do @rem
I even modify the getroot.sh script just to change back to the old su command and modify its permissions:
Code:
cd /data/local/tmp
echo >/data/local.prop
toolbox mount -o remount, rw /system/
cat su >/system/bin/su
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su
sync ; sync ; sync
reboot
Good Luck...
Hello,
After flashing the most recent TuchMi ROM on my galaxy s3, trying it out and restoring to my nandroid backup of kyanrom I have a TuchMi folder I cannot delete. I have tried ES Fileexplorer and Root Explorer both. There are three zip files in the TuchMi folder that cannot be deleted, tells me file permissions cannot be changed.
That said, the timestamp on the /TuchMi folder is 8 March 1970. I am wondering if this is causing something to fail in deleting or being able to change permissions. I don't know if this is right place to ask this question but I can't ask in the TuchMi thread because I am too new. Anyone have an idea on what I can do to fix this?
Thanks
JMD
rezin44 said:
Hello,
After flashing the most recent TuchMi ROM on my galaxy s3, trying it out and restoring to my nandroid backup of kyanrom I have a TuchMi folder I cannot delete. I have tried ES Fileexplorer and Root Explorer both. There are three zip files in the TuchMi folder that cannot be deleted, tells me file permissions cannot be changed.
That said, the timestamp on the /TuchMi folder is 8 March 1970. I am wondering if this is causing something to fail in deleting or being able to change permissions. I don't know if this is right place to ask this question but I can't ask in the TuchMi thread because I am too new. Anyone have an idea on what I can do to fix this?
Thanks
JMD
Click to expand...
Click to collapse
Run "fix permissions" from recovery, and then try again.
(One of the most common reasons you can't delete something, even as root, is that its file attributes are set to "immutable" (which under linux often means you've been hacked, but no worries here))
Thanks for the quick reply but that didn't seem to fix it. I am at a loss, the folder is only 32meg so I am not too concerned but it is a little annoying. If there's another thing you can think of I'd appreciate it.
Sent from my SGH-I747M using Tapatalk 2
rezin44 said:
Thanks for the quick reply but that didn't seem to fix it. I am at a loss, the folder is only 32meg so I am not too concerned but it is a little annoying. If there's another thing you can think of I'd appreciate it.
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
Nuke it (rm -rf somedir) from an adb shell, so you can see the actual error.
zmore said:
Nuke it (rm -rf somedir) from an adb shell, so you can see the actual error.
Click to expand...
Click to collapse
Here's what it says.
Code:
[email protected]:/ $ cd sdcard
cd sdcard
[email protected]:/sdcard $ ls
ls
Alarms
Albums
Android
Application
DCIM
Download
EVA
Evernote
GOLauncherEX
GoStore
Library
Movies
Music
Notifications
Pictures
PlayerPro
Podcasts
Ringtones
SpeedSoftware
TuchMi
ba-superkeyboard
backups
data
ivona
mdm
media
rootz
svox
temp
[email protected]:/sdcard $ rm -rf TuchMi
rm -rf TuchMi
rm failed for -rf, No such file or directory
255|[email protected]:/sdcard $ rm TuchMi
rm TuchMi
rm failed for TuchMi, Is a directory
255|[email protected]:/sdcard $ cd TuchMi
cd TuchMi
[email protected]:/sdcard/TuchMi $ ls
ls
Stock_SystemUI.zip
Voice_Reinstall.zip
XXBLG1_AndroidGX-MOD_NexusBattery.zip
[email protected]:/sdcard/TuchMi $ rm Stock_SystemUI.zip
rm Stock_SystemUI.zip
rm failed for Stock_SystemUI.zip, Permission denied
255|[email protected]:/sdcard/TuchMi $ ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Nex
usBattery.zip
[email protected]:/sdcard/TuchMi $
and these are the permissions of the subject directory.
drwxrwxr-x root sdcard_rw 1970-03-08 01:48 TuchMi
Thank you for taking the time to respond to this.
JMD
I had to delete it while plugged into my pc. Was just driving me crazy that I couldn't get rid of it.
Well, I've resigned myself to failure deleting these three files and the folder they're in. I've tried 8 or 9 different file managers. I downloaded and installed adb, learned enough to really screw up my phone, but that didn't work either. I tried deleting them through windows and debian too.
That said, I'm just going to live with things as they are now. In the future when a more mature JB rom comes out I'll try that but my question is this, can I just format (wipe) my sdcard partition and restore the stock at&t/Samsung rom using Odin?
Sent from my SGH-I747M using Tapatalk 2
rezin44 said:
Well, I've resigned myself to failure deleting these three files and the folder they're in. I've tried 8 or 9 different file managers. I downloaded and installed adb, learned enough to really screw up my phone, but that didn't work either. I tried deleting them through windows and debian too.
That said, I'm just going to live with things as they are now. In the future when a more mature JB rom comes out I'll try that but my question is this, can I just format (wipe) my sdcard partition and restore the stock at&t/Samsung rom using Odin?
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
I noticed in your terminal output, that you weren't root (# vs $). "su" to root, and try again.
zmore said:
I noticed in your terminal output, that you weren't root (# vs $). "su" to root, and try again.
Click to expand...
Click to collapse
Yeah, I caught that before you mentioned it yesterday but I thought I'd try it again as this is very new to me and I am using cheat sheets with adb common commands to navigate through this. Here is the output though. Still no bueno..
Code:
drwxrwxr-x root sdcard_rw 1970-03-08 01:48 TuchMi
drwxrwxr-x root sdcard_rw 2012-09-04 08:05 ba-superkeyboard
drwxrwxr-x root sdcard_rw 2012-09-04 09:45 backups
drwxrwxr-x root sdcard_rw 2012-09-05 02:05 clockworkmod
drwxrwxr-x root sdcard_rw 2012-09-03 20:09 data
drwxrwxr-x root sdcard_rw 2012-09-04 14:24 ivona
drwxrwxr-x root sdcard_rw 2012-08-31 09:00 mdm
drwxrwxr-x root sdcard_rw 2012-08-14 17:39 media
drwxrwxr-x root sdcard_rw 2012-09-03 21:31 rootz
drwxrwxr-x root sdcard_rw 2012-09-04 23:14 temp
[email protected]:/sdcard # rm -rf TuchMi
rm -rf TuchMi
rm failed for -rf, No such file or directory
255|[email protected]:/sdcard # cd TuchMi
cd TuchMi
[email protected]:/sdcard/TuchMi # ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Nex
usBattery.zip
[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
rm Stock_SystemUI.zip
rm failed for Stock_SystemUI.zip, Permission denied
255|[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
rezin44 said:
Yeah, I caught that before you mentioned it yesterday but I thought I'd try it again as this is very new to me and I am using cheat sheets with adb common commands to navigate through this. Here is the output though. Still no bueno..
Code:
...snip...
[email protected]:/sdcard/TuchMi # ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Nex
usBattery.zip
[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
rm Stock_SystemUI.zip
rm failed for Stock_SystemUI.zip, Permission denied
255|[email protected]:/sdcard/TuchMi # rm Stock_SystemUI.zip
Click to expand...
Click to collapse
Weird. As root, you normally only see that for immutable files, so, try:
lsattr foo.zip
and if you see an "i" flag for immutable, do a:
chattr -i file.zip
zmore said:
Weird. As root, you normally only see that for immutable files, so, try:
lsattr foo.zip
and if you see an "i" flag for immutable, do a:
chattr -i file.zip
Click to expand...
Click to collapse
Code:
D:\android-sdk\platform-tools>adb devices
List of devices attached
b41c0497 device
D:\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # cd sdcard/TuchMi
cd sdcard/TuchMi
[email protected]:/sdcard/TuchMi # ls -l
ls -l
-rw-rw-r-- root sdcard_rw 1280043 2008-08-01 07:00 Stock_SystemUI.zip
-rw-rw-r-- root sdcard_rw 29694315 2008-08-01 07:00 Voice_Reinstall.zip
-rw-rw-r-- root sdcard_rw 2582686 2008-08-01 07:00 XXBLG1_AndroidGX-MOD_Ne
usBattery.zip
[email protected]d:/sdcard/TuchMi # lsattr Stock_SystemUI.zip
lsattr Stock_SystemUI.zip
lsattr: reading Stock_SystemUI.zip: Function not implemented
[email protected]:/sdcard/TuchMi # lsattr Voice_Reinstall.zip
lsattr Voice_Reinstall.zip
lsattr: reading Voice_Reinstall.zip: Function not implemented
[email protected]:/sdcard/TuchMi #
It kicked out those "Function not implemented" errors, I did some searching and some of the sites that popped up were fedora and ubuntu and they hinted at maybe I have the wrong file system for lsattr to work? In windows it shows the file system on both sdcards, int and ext, as 'generic hierarchical'.
I have had this issue with a couple of folder where I could NOT delete them on my i777 no matter what/how I tried. The files/folders I had were some that I extracted. Then when I was done with it I couldn't delete it. After I had two folders I couldn't delete as it too was bugging me was I connected up my phone via ums to my PC and transfered everything I wanted/needed from my sdcard (internal unremovable). Then when I had it all backed up I went into recovery and formatted my internal sdcard (I removed my external sdcard first to be safe). Then I booted up phone and saw it was all clean. Then I reconnected to PC and transferred all my needed files/folders back onto phone.
I THINK what happened was somehow it was a corrupted file and caused my issues. Completely wiping my sdcard fixed it though. Good luck to you.
Sent from My SGH-I777 Running Red Reaper Rom
RockRatt said:
I have had this issue with a couple of folder where I could NOT delete them on my i777 no matter what/how I tried. The files/folders I had were some that I extracted. Then when I was done with it I couldn't delete it. After I had two folders I couldn't delete as it too was bugging me was I connected up my phone via ums to my PC and transfered everything I wanted/needed from my sdcard (internal unremovable). Then when I had it all backed up I went into recovery and formatted my internal sdcard (I removed my external sdcard first to be safe). Then I booted up phone and saw it was all clean. Then I reconnected to PC and transferred all my needed files/folders back onto phone.
I THINK what happened was somehow it was a corrupted file and caused my issues. Completely wiping my sdcard fixed it though. Good luck to you.
Sent from My SGH-I777 Running Red Reaper Rom
Click to expand...
Click to collapse
Thanks, Im gonna give this a try
Well, it's beat me. After trying all the above things I still cannot delete the TuchMi folder. I tried formatting the sdcard partition from windows, CWM, and fedora. All three did format and manage to wipe everything from that partition except the TuchMi folder.
All I can say is be wary of that ROM.
Sent from my SGH-I747M using Tapatalk 2
This guide was tested on my samsung galaxy [email protected] gt-B5330 and it worked.
WARNING: this can brick your phone, used on your own risk (both eyes wide open).
The idea behing can be ported on any phone that allows you to upload custom firmware (most samsungs with odin).
The idea is that you escalate to superuser by setting suid on /system/bin/toolbox executable.
By duing that you can run most of the unix commands on android as a superuser.
I is enought for you to copy su utility somewhere where there is not a nosuid option on mountpoint. and make it a suided executable then execute su and get the #.
It's all down hill from here.
I cannot verify for every ics rom out there, but it seems that now ics uses ext4 filesystem for the system partition.
I have made a script that inspects a stock rom firmware isolate the permissions for the toolbox executable and add to them SUID,SUIG.
After that it pachs the firmware back and you can flash it to your device and have a easylly rootable device. (I will post the stept to take to get a standard rooted device).
What you need:
a linux/gnu (it will not work with cygwin because we have to mount the ext4 partition).
simg2img utility (you can get it from xda site it is in ext4_utility packet).
su, busybox and superuser.apk binaries for android (you can take them from a rooting package).
heimdal (for linux) xor odin (for windows and if you cannot flash the firmware on your phone form linux).
I've put all untilities that are not standard into the tar.
just unpack and you have the universal-patch.sh to run over an .tar.md5 firware stock rom.
And post-firmwareUpdate.sh to run after you flash in order to make the root a standard android root.
This was not tested on any other phone (was tested only on GT-B5330) and do it on your own risk.
This rooting does not exploit any weakness (or flaw) in kernel or any thing, it just modifies the stock firmware to make it more flexible so it should be forward compatible with any version of android after ics.
I assume this would exclude HTC's since you meed to be s-off to flash a firmware. I would probably verify that and edit the title if necessary. Other than that, this looks like it could be helpful.
Help to understand the procedure
Hi ETTT,
first of all thanks for your job and effort in finding a solution to this issue.. it has been driving me crazy till now.. but thanx to you i see the light :good: I see it but i cannot really understand the procedure.. Could you please write a step by step explanation of what i need to do. (I am not what we could call a genius with linux).
Thanks in advance.
The First said:
Hi ETTT,
first of all thanks for your job and effort in finding a solution to this issue.. it has been driving me crazy till now.. but thanx to you i see the light :good: I see it but i cannot really understand the procedure.. Could you please write a step by step explanation of what i need to do. (I am not what we could call a genius with linux).
Thanks in advance.
Click to expand...
Click to collapse
If you are refering to the procedure that the script is doing here is the version of step by step (with-out the script):
http://forum.xda-developers.com/showthread.php?t=1956653
If you want to know the step by step with the script, here (I will not respond to more basic than this, like how to boot ubuntu and stuff.):
mkdir -p /tmp/foo
sudo mkdir /mnt
cd /tmp/foo
tar -xzf universal-patch.tar.gz
export PATH=./:$PATH
{get the firmware here and unzip it, it should have a file with .tar.md5 suffix}
./universal-patch.sh {the name of the firmware including the .tar.md5 suffix}
wait a while. you should have by the way about 10 times the size of the zip as free space.
if all goes well you will have a myfrm.tar.md5 rady for flashing.
flash the firmware, and after boot enable usb debuging, hook the phone to pc
sudo adb devices
./post-firmwareUpdate.sh
you should have a rooted phone.
you cannot go any more basic than that.
Have fun.
Thanks for your effort, I'm already have my XWALH3 patched, btw you should to check the patch on line 19, you've misstype something there
Sent from my GT-B5330 using xda app-developers app
The file after qa
phyxar said:
Thanks for your effort, I'm already have my XWALH3 patched, btw you should to check the patch on line 19, you've misstype something there
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
Thanks for testing and input.
phyxar said:
Thanks for your effort, I'm already have my XWALH3 patched, btw you should to check the patch on line 19, you've misstype something there
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
XWALH3 i've produce from your universal-patch cannot being flashed to my phone, odin crash each time open those files
phyxar said:
XWALH3 i've produce from your universal-patch cannot being flashed to my phone, odin crash each time open those files
Click to expand...
Click to collapse
I'm puting the xdelta to the XWALH3
here are the md5s for the original and patched firmware.
cfe3ca545c4a2c8d453e02cd549655a1 B5330XWALH3_B5330OJVALH1_B5330XXLH4_HOME.tar.md5
624f63943bff54941e4042a39d7928f2 myfrm.tar.md5
Now I have some question in order to debug:
does the patching you have done yeild the same file as I have here?
have you use the same imput? (that's why I've give you the md5 of my imput).
Hey you have rooted you b5330 then do you notice any performance upgrade
Sent from my GT-B5330 using xda premium
Can I patch the firmware using windows??
Because I'm on win
I don't really understand using linux
Or can you make single click batch file that I can use it to patch my firmware???
I really appreciate it if someone provide it
Thanks
Sent from my GT-B5330 using xda app-developers app
byboyz said:
Can I patch the firmware using windows??
Because I'm on win
I don't really understand using linux
Or can you make single click batch file that I can use it to patch my firmware???
I really appreciate it if someone provide it
Thanks
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
I don't know windows that much to make a batch clone of the script. so you need linux.
But you can use a live cd (maybe from ubuntu) to run the script.
ETTT said:
I don't know windows that much to make a batch clone of the script. so you need linux.
But you can use a live cd (maybe from ubuntu) to run the script.
Click to expand...
Click to collapse
Thx for ur reply
How can I open XWALH3.patch that u give earlier??
Bcause I don't know anything about linux
Sent from my GT-B5330 using xda app-developers app
byboyz said:
Thx for ur reply
How can I open XWALH3.patch that u give earlier??
Bcause I don't know anything about linux
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
that patch is an xdelta patch.
There is an xdelta application on windows, don't know if it works, but it should work.
ETTT said:
If you are refering to the procedure that the script is doing here is the version of step by step (with-out the script):
http://forum.xda-developers.com/showthread.php?t=1956653
If you want to know the step by step with the script, here (I will not respond to more basic than this, like how to boot ubuntu and stuff.):
mkdir -p /tmp/foo
sudo mkdir /mnt
cd /tmp/foo
tar -xzf universal-patch.tar.gz
export PATH=./:$PATH
{get the firmware here and unzip it, it should have a file with .tar.md5 suffix}
./universal-patch.sh {the name of the firmware including the .tar.md5 suffix}
wait a while. you should have by the way about 10 times the size of the zip as free space.
if all goes well you will have a myfrm.tar.md5 rady for flashing.
flash the firmware, and after boot enable usb debuging, hook the phone to pc
sudo adb devices
./post-firmwareUpdate.sh
you should have a rooted phone.
you cannot go any more basic than that.
Have fun.
Click to expand...
Click to collapse
hi there, I'm stuck at last point/step: ./post-firmwareUpdate.sh
my terminal respond many error about busybox
the code like this:
2684 KB/s (91980 bytes in 0.033s)
4016 KB/s (996704 bytes in 0.242s)
4491 KB/s (1085140 bytes in 0.235s)
.//busybox: 1: .//busybox: Syntax error: word unexpected (expecting ")")
.//busybox: 1: .//busybox: Syntax error: word unexpected (expecting ")")
dd if=/data/local/tmp/su of=/mnt/obb/su # copy the su binary to a place that can be sudoed
chown 0.0 /mnt/obb/su # modify the owner
chmod 6755 /mnt/obb/su # set SUID flag.
/mnt/obb/su # becomes root !!
mount -o remount,rw /system # remount the system partition as readwrite.
dd if=/data/local/tmp/su of=/system/xbin/su #copy su in path
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chmod 755 /system/bin/toolbox # close the security hole (toolbox is nolonger with SUID)
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk # copy the superuser application
chown 0.0 /system/app/Superuser.apk
chmod 666 /system/app/Superuser.apk
#now this is done for busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown 0.0 /system/xbin/busybox
chmod 755 /system/xbin/busybox
cd /system/xbin
for k in
nt/obb/su # copy the su binary to a place that can be sudoed <
/mnt/obb/su: cannot open for write: Permission denied
1|[email protected]:/ $ chown 0.0 /mnt/obb/su # modify the owner
Unable to chmod /mnt/obb/su: No such file or directory
10|[email protected]:/ $ chmod 6755 /mnt/obb/su # set SUID flag.
Unable to chmod /mnt/obb/su: No such file or directory
10|[email protected]:/ $ /mnt/obb/su # becomes root !!
/system/bin/sh: /mnt/obb/su: not found
# remount the system partition as readwrite. <
mount: Operation not permitted
/system/xbin/su #copy su in path <
/system/xbin/su: cannot open for write: Read-only file system
1|[email protected]:/ $ chown 0.0 /system/xbin/su
Unable to chmod /system/xbin/su: No such file or directory
10|[email protected]:/ $ chmod 6755 /system/xbin/su
Unable to chmod /system/xbin/su: No such file or directory
# close the security hole (toolbox is nolonger with SUID) <
Unable to chmod /system/bin/toolbox: Read-only file system
er.apk of=/system/app/Superuser.apk # copy the superuser application <
/system/app/Superuser.apk: cannot open for write: Read-only file system
1|[email protected]:/ $ chown 0.0 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
10|[email protected]:/ $ chmod 666 /system/app/Superuser.apk
Unable to chmod /system/app/Superuser.apk: No such file or directory
10|[email protected]:/ $ #now this is done for busybox
10|[email protected]:/ $ dd if=/data/local/tmp/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Read-only file system
1|[email protected]:/ $ chown 0.0 /system/xbin/busybox
Unable to chmod /system/xbin/busybox: No such file or directory
10|[email protected]:/ $ chmod 755 /system/xbin/busybox
Unable to chmod /system/xbin/busybox: No such file or directory
10|[email protected]:/ $ cd /system/xbin
[email protected]:/system/xbin $ for k in
Click to expand...
Click to collapse
smhybrid said:
hi there, I'm stuck at last point/step: ./post-firmwareUpdate.sh
my terminal respond many error about busybox
the code like this:
Click to expand...
Click to collapse
Ok it seams busybox has a thing against ")" in comments.
Here is the script without comments, so try this.
ETTT said:
Ok it seams busybox has a thing against ")" in comments.
Here is the script without comments, so try this.
Click to expand...
Click to collapse
no good, it's still have same error...
maybe the problem is in busybox?
and i don't know why I'm unable to do chmod
smhybrid said:
no good, it's still have same error...
maybe the problem is in busybox?
and i don't know why I'm unable to do chmod
Click to expand...
Click to collapse
give this command:
adb shell ls -l /system/bin/toolbox
and let's see if the toolbox has suid.
ETTT said:
give this command:
adb shell ls -l /system/bin/toolbox
and let's see if the toolbox has suid.
Click to expand...
Click to collapse
what i get is
-rwxr-xr-x root shell 99068 2012-08-09 11:59 toolbox
how to get suid?
smhybrid said:
what i get is
-rwxr-xr-x root shell 99068 2012-08-09 11:59 toolbox
how to get suid?
Click to expand...
Click to collapse
have you flash the patched firmware?
ETTT said:
have you flash the patched firmware?
Click to expand...
Click to collapse
well, I've just do all of Your step, except this:
flash the firmware, and after boot enable usb debuging, hook the phone to pc
Click to expand...
Click to collapse
because I don't know the meaning of flash the firmware. How to do that?
So I skip that and hook the phone to pc with usb debugging enabled
i'm new at linux, but I want to try this method for my galaxy chat
Hi,
I was about to start the PurpleDrake-Lite shell script in my distro, phone plugged in and configured thoroughly following the tutorial, but the output gave an error message right at start so I Ctrl+c'd to stop the script. Here is the issue:
In purpledrake_linux.sh, on line 17:
Code:
chmod -R 755 ./assets/linux/
of course, the error says "no such file or directory", because in the 'assets' directory there is:
Code:
$ ls -l
drwxr-xr-x linux32
drwxr-xr-x linux64
drwxr-xr-x osx
-rw-r--r-- permaroot.bin
-rwxr-xr-x purpledrake_main.sh
-rw-r--r-- start_restore
-rw-r--r-- temproot.bin
drwxr-xr-x windows
(I stripped the unnecessary bits from the output,) but no 'linux' directory.
I don't know if I should report it as a bug, and if so, where exactly?
Else, it seems even pointless to quit the process right at this stage, because the second script called, purpledrake_main.sh might well find it's way to the relevant directory? (In linux32 or in linux64, depending on the architecture of the machine, right?) and they all have the right 755 permissions anyway as it appears from the output.
What do you think?
Best regards,
Mélodie
meylodie said:
Hi,
I was about to start the PurpleDrake-Lite shell script in my distro, phone plugged in and configured thoroughly following the tutorial, but the output gave an error message right at start so I Ctrl+c'd to stop the script. Here is the issue:
In purpledrake_linux.sh, on line 17:
Code:
chmod -R 755 ./assets/linux/
of course, the error says "no such file or directory", because in the 'assets' directory there is:
Code:
$ ls -l
drwxr-xr-x linux32
drwxr-xr-x linux64
drwxr-xr-x osx
-rw-r--r-- permaroot.bin
-rwxr-xr-x purpledrake_main.sh
-rw-r--r-- start_restore
-rw-r--r-- temproot.bin
drwxr-xr-x windows
(I stripped the unnecessary bits from the output,) but no 'linux' directory.
I don't know if I should report it as a bug, and if so, where exactly?
Else, it seems even pointless to quit the process right at this stage, because the second script called, purpledrake_main.sh might well find it's way to the relevant directory? (In linux32 or in linux64, depending on the architecture of the machine, right?) and they all have the right 755 permissions anyway as it appears from the output.
What do you think?
Best regards,
Mélodie
Click to expand...
Click to collapse
Hi,
The header of the script contains this information:
# PurpleDrake root for LG G3 - Linux launcher
# - A collaboration between @autoprime , @thecubed (iomonster) , and @teamandirc (jcase)
Click to expand...
Click to collapse
Is there a specific place in this forum dedicated to bug reports? If so, where?
Now, what if I would start directly with the script which is inside the assets/ sub-directory: the file having for name "purpledrake_main.sh"? Would this have a chance to work directly? Or perhaps, should I reather use the first script, and just ignore the first error message and continue?
up! \o/
meylodie said:
Hi,
The header of the script contains this information:
Is there a specific place in this forum dedicated to bug reports? If so, where?
Now, what if I would start directly with the script which is inside the assets/ sub-directory: the file having for name "purpledrake_main.sh"? Would this have a chance to work directly? Or perhaps, should I reather use the first script, and just ignore the first error message and continue?
up! \o/
Click to expand...
Click to collapse
It looks like there is a Q&A forum for purpledrake here: http://forum.xda-developers.com/tmobile-lg-g3/help/qa-root-twrp-tmo-g3-purpled-t2926609 maybe ask the question there and you will get a faster response.
justmpm said:
It looks like there is a Q&A forum for purpledrake here: http://forum.xda-developers.com/tmobile-lg-g3/help/qa-root-twrp-tmo-g3-purpled-t2926609 maybe ask the question there and you will get a faster response.
Click to expand...
Click to collapse
Hi,
I don't think so, the topic contains "D851 only". I would risk being struck by lightning if I would not obey the rules?!
meylodie said:
Hi,
I don't think so, the topic contains "D851 only". I would risk being struck by lightning if I would not obey the rules?!
Click to expand...
Click to collapse
Hi,
Solved here:
http://forum.xda-developers.com/lg-...purpledrake-lite-t2821000/page78#post58280432
The script needs '*' at the end of the string "linux". Line 17:
Code:
chmod -R 755 ./assets/linux*/
instead of
Code:
chmod -R 755 ./assets/linux/
Thanks to tzvi.