[Q] Can't get tablet rooted - Acer Iconia Tab A100

[Q] Can't get tablet rooted - Acer Iconia Tab A100

Bought an A100 off Ebay and donated a battery to it. Tried several ways (like ADB method and Terminal Emulator) and many times to root, but no go.
The ROM is Acer_AV041_A100_1.015.00_PA_CUS1
The results with Terminal Emulator working with root.sh in /mnt/sdcard are:
/system/xbin/su: No such file or directory
When I type in the commands for ADB:
adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch ‘`cat /mnt/sdcard/su >/system/xbin/su`’
adb shell /system/bin/cmdclient ec_micswitch ‘`chmod 6755 /system/xbin/su`’
I get no response in the command window. I then go to Superuser, and the info menu says "su binary not found"
ADB and Fastboot seem to work OK. It returns the device number 20710676216.
adb shell cat /proc/partitions shows nine partitions
It looks like a permissions problem, but I don't know what to do next.
Who can help me figure this out?

http://forum.xda-developers.com/showthread.php?p=23285307 have you tried this?
Alao is that ICS or HC I can't ever remember by the stock firmware title?
Sent from my SCH-R760X using xda app-developers app

Working on it
chicinwang said:
http://forum.xda-developers.com/showthread.php?p=23285307 have you tried this?
Alao is that ICS or HC I can't ever remember by the stock firmware title?
Sent from my SCH-R760X using xda app-developers app
Click to expand...
Click to collapse
It is ICS. Yes, I tried the simple method earlier, but got error about no mempodroid.
I just added the precompiled version to the subfolder 'tools' and got past that error.
Now, when I run runit-win.bat, it successfully passes the preparation stage, says executing the main script, then remote object /system/bin/su doesn't exist... file su isn't created... not getting root! Error
By the way, PS#2 of the simple method says: Command "Mount ro/rw" for directory /system (partition) - works perfectly!
Is that a command I have to execute in ADB for the simple method to work at all?

One of the Droid razor maxx easy root works.
Sent from my Nexus 4

Got it fixed
myturbo1 said:
One of the Droid razor maxx easy root works.
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks for the reply. I got it fixed by reverting to HC, rooting, custom recovery, and then flashing Kebbersrom Shellshock.

WVHdls1 said:
Thanks for the reply. I got it fixed by reverting to HC, rooting, custom recovery, and then flashing Kebbersrom Shellshock.
Click to expand...
Click to collapse
How do you get back to HC?
Where can i find the HC stock file?
Can you post (link/file) please?
I have the same problem to root my a100 with ics stock :silly: .

frischeis said:
How do you get back to HC?
Where can i find the HC stock file?
Can you post (link/file) please?
I have the same problem to root my a100 with ics stock :silly: .
Click to expand...
Click to collapse
Are you using the easy root method?
Sent from my Nexus 4 using xda premium

myturbo1 said:
Are you using the easy root method?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes of course:
When i want to root my device i get this message:
Device connected. Preparation for executing of the main script.
push: tools/su -> /data/local/tmp/su
push: tools/runit.sh -> /data/local/tmp/runit.sh
push: tools/mount.sh -> /data/local/tmp/mount.sh
push: tools/getroot.sh -> /data/local/tmp/getroot.sh
push: tools/delroot.sh -> /data/local/tmp/delroot.sh
push: tools/busybox.sh -> /data/local/tmp/busybox.sh
push: tools/busybox -> /data/local/tmp/busybox
7 files pushed. 0 files skipped.
1452 KB/s (803082 bytes in 0.540s)
Unable to chmod /data/local/tmp/mempodroid: No such file or directory
remote object '/data/local/tmp/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
What is wrong and what can i do?
I have ICS stock rom 4.0.3.

frischeis said:
Yes of course:
When i want to root my device i get this message:
Device connected. Preparation for executing of the main script.
push: tools/su -> /data/local/tmp/su
push: tools/runit.sh -> /data/local/tmp/runit.sh
push: tools/mount.sh -> /data/local/tmp/mount.sh
push: tools/getroot.sh -> /data/local/tmp/getroot.sh
push: tools/delroot.sh -> /data/local/tmp/delroot.sh
push: tools/busybox.sh -> /data/local/tmp/busybox.sh
push: tools/busybox -> /data/local/tmp/busybox
7 files pushed. 0 files skipped.
1452 KB/s (803082 bytes in 0.540s)
Unable to chmod /data/local/tmp/mempodroid: No such file or directory
remote object '/data/local/tmp/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
What is wrong and what can i do?
I have ICS stock rom 4.0.3.
Click to expand...
Click to collapse
From that log it never pushed what its trying to run, may need to push it manually then run the script again.
Tapatalked from my HTC DNA - PAC v22.1.1

frischeis said:
How do you get back to HC?
Where can i find the HC stock file?
Can you post (link/file) please?
I have the same problem to root my a100 with ics stock :silly: .
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=33859034&postcount=20

pio_masaki said:
From that log it never pushed what its trying to run, may need to push it manually then run the script again.
Tapatalked from my HTC DNA - PAC v22.1.1
Click to expand...
Click to collapse
Can you tell me how get it manually rootet please?
Would be very nice and it is my last chance....to root.

Open the script that you run. I did mine in Linux, and I needs root to run, so maybe try running as admin? You can copy and paste the commands from the script into the command prompt once your into your adb directory.
So
Adb push blahblah /blah/blah/blah
Kinda like that pretty simple. Good luck!
Sent from my SPH-L710 using xda app-developers app

I try it on a other pc to root the device with easy root method from ZeroNull :
http://forum.xda-developers.com/showthread.php?t=1531646
So now i have root and works like charm!!!!!!!!!!!!!!
Thanks guys :good: !!

Related

[TUTORIAL] Error 190 Fix (Works with 2.13.401.3)

Hi, here's an tutorial how to Fix the "ERROR[190]: ROM IS NOT UPDATED"
mphi said:
Warning: You could probably brick your phone if you flash an invalid misc partition. So follow these steps carefully (or not at all)!
Click to expand...
Click to collapse
Android Tool's what you will need : Click
Confirmed: http://forum.xda-developers.com/showthread.php?t=1444512&page=2
1. Be sure u got all drivers.
2. Connect your phone via USB and select the HTC sync option when prompted. Also ensure that USB debugging is enabled (this is the default).
3. Unzip my pack somewhere. I suggest like (x:\folder)
4. Start cmd. Be sure u are in the ADB folder with CMD.
5. Write those commands carefully, be sure you wrote them correctly.
adb push flash_image /sdcard/flash_image
adb push zergRush /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/zergRush
Click to expand...
Click to collapse
Enter Shell by using
adb shell
*You should notice $*
Click to expand...
Click to collapse
Execute zergRush
./data/local/tmp/zergRush
*zergRush will kill adb, start it again with*
adb shell
*You should notice that $ changed to #*
Click to expand...
Click to collapse
Get the misc.img
cat /dev/mtd/mtd0 > /sdcard/misc.img
exit
Click to expand...
Click to collapse
Copy misc.img from sdcard to current directory
adb pull /sdcard/misc.img misc.img
Click to expand...
Click to collapse
6.Run HxD.exe, select "OK" at the prompt then File -> Open and locate misc.img (which is in the current directory). On the 11th line you should see the version number of your current ROM. I set my version number to 2.13.401.2 since this was the version number. The changes made will be highlighted in red. File -> Save As and name it misc2.img.
Pictures!
1. Find your version my was 10.13.401.2
http://i.imgur.com/xfltH.png
2.Write currect Version (Dont worry if something will left, we will get off this soon)
http://i.imgur.com/yHp9W.png
3.Change the Selected number what left, for me it was 2. Then in this BIG table of weird things, there will be selected an value for me it's 32, just change it to 00, and save file. Should look like this:
http://i.imgur.com/3omav.png
Click to expand...
Click to collapse
If your version of misc.img match the required version of the RUU you can complete the tutorial (this is not a problem to which this guide will help you). If the versions are different, set the version that is required, and continue the tutorial from step 7.
7. Back to adb window. Copy the misc2.img to sdcard. (no # or $)
adb push misc2.img /sdcard/misc2.img
Click to expand...
Click to collapse
Flashing time
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 777 /data/flash_image
*Flash Command, it depends your life, be sure you wrote this correctly*
/data/flash_image misc /sdcard/misc2.img
Click to expand...
Click to collapse
ALL CREDITS TO mphi, i just edit it to zergrush...
Click to expand...
Click to collapse
After those steps you should be able to install RUU from htcdev to unlock bootloader.
Reply if something went wrong.
If it helps just click THANKS
If you use zergRush again, clean dump's from zergRush via
Code:
adb shell
rm /data/local/tmp/boomsh
rm /data/local/tmp/sh

My version was 10.13.401.2 I've changed it to 2.13.401.2 so now I should go on from step 7?

Yes, go to step 7 edit it to good one and flash it.
I edited the red text so it will be easier to undestand good luck

Hi Unkheq,
Came back to hit thanks!
It totally worked for me, it was showing version 10.13.401.2 and i edited to 2.13.401.2, followed all your steps exactly and all went fine.
RUU ran succesfully.
Thanks for the tut!

adb shell
*You should notice $*
Click to expand...
Click to collapse
done ok I get $
Execute zergRush
./data/local/tmp/zergRush
*zergRush will kill adb, start it again with*
adb shell
*You should notice that $ changed to #*
Click to expand...
Click to collapse
Fail.. I get premission denied.
What should I do now?

hi gusta1,
Did you give zergrush full permissions with this command: adb shell chmod 777 /data/local/tmp/zergRush ? it's under step 5.

yes I did and all went well till executing zergrush... here I get a premission denied

are you sure u copied zergrush in good directory, or try giving chmod again

Unkheq said:
are you sure u copied zergrush in good directory, or try giving chmod again
Click to expand...
Click to collapse
I write code a several times and allways stuck at that point... i don't know what to do anymore.. what could be wrong? My WFS is S-ON and it is not rooted yet

gusta1, be sure you are in the directory where you put the files. For example, if you extracted them in D:\WFS\APPS then in CMD you need to type command: chdir D:\WFS\APPS and after that start with step 5 from tutorial.

I have the same problem as gusta1 even I'm in proper folder I've got following message:
$ ./data/local/tmp/zergRush
./data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[-] Cannot copy boomsh.: Permission denied
$
Click to expand...
Click to collapse
I run cmd as admin (Vista), repeated prcedure and restarted phone several times, but with the same result.
But my history is different. I have S-off my Wildfire S successfuly at the begining when I was on 2.3.3. However I put phone to my wife and once phone asked for update to 2.3.5 she allowed it and S-off was gone. Since that I can not move, everywhere is some error.

Anorien said:
gusta1, be sure you are in the directory where you put the files. For example, if you extracted them in D:\WFS\APPS then in CMD you need to type command: chdir D:\WFS\APPS and after that start with step 5 from tutorial.
Click to expand...
Click to collapse
I tried again and I got same result... I am in good directory,Any idea?

Hi,
Try this:
After entering "adb shell":
run these commands in adb shell:
rm /data/local/tmp/boomsh
rm /data/local/tmp/sh
Then continue with the step to execute zerg rush.

Anorien said:
Hi,
Try this:
After entering "adb shell":
run these commands in adb shell:
rm /data/local/tmp/boomsh
rm /data/local/tmp/sh
Then continue with the step to execute zerg rush.
Click to expand...
Click to collapse
Thanks!! You are the best!! I made it with your advice!

Oh i forgot about cleaning commands if x times zergRush, will add ^^

gusta1 said:
Thanks!! You are the best!! I made it with your advice!
Click to expand...
Click to collapse
You welcome, glad I could help!

Worked with orange romania wildfire S phone.
Thanks

Thank you very much it worked fine for me>>> all the thanx

Hi
I've got an UK T-mobile S_ON WFS with
HBoot 0.90.000
Android 2.3.3
Rom 1.34.11.03
HTC unlock bootloader fails with error 190 and tip http://forum.xda-developers.com/showthread.php?p=21120374 fails with Hboot bypassed.
Am I likely to have any major problems? Don't want to brick my phone.
Thanks

Help
* bump *

Mod please delete thread thanks

I'm totallt stock 2.3.6 EK02. I'm ready to risk rooting, but I have no idea what to do. There's 5 dozen methods, modems, kernels, basebands etc. Coming from HTC and unrevoked it's a lot to swallow with odin. So i gues i kind of need a step by step to 1st get root
2nd a back up of my stock ek02,
3rd update to el29...i think??? modems? I read the forum daily but I'm completely lost honestly. To many basebands and modems and methods of doing this. Need help want to do this today

Sfhubs automated root thread in the sticky.
Run for root, then run option c for clockwork mod, backup, then flash the ROMS of your choice. Super easy, no Odin necessary
Sent from my Blazing ET4G
Edit: read twice, do the steps once
Also, look for qbking77's how to videos for complete walkthroughs

tkemack said:
Sfhubs automated root thread in the sticky.
Run for root, then run option c for clockwork mod, backup, then flash the ROMS of your choice. Super easy, no Odin necessary
Sent from my Blazing ET4G
Edit: read twice, do the steps once
Also, look for qbking77's how to videos for complete walkthroughs
Click to expand...
Click to collapse
I've actually tried this a few times now and SU never installs? Debugging checked drivers installed and still no luck yet...have ran it several times now.

Optimal Carnage said:
I've actually tried this a few times now and SU never installs? Debugging checked drivers installed and still no luck yet...have ran it several times now.
Click to expand...
Click to collapse
Use Option F on the main menu to enable the scroll buffer, then rerun Option A and post the log between BEGIN LOG and END LOG.

sfhub said:
Use Option F on the main menu to enable the scroll buffer, then rerun Option A and post the log between BEGIN LOG and END LOG.
Click to expand...
Click to collapse
---- BEGIN LOG ----
...Proceeding to copy necessary files...
push: copy2tmp/install-zerg.sh -> /data/local/tmp/install-zerg.sh
1 file pushed. 0 files skipped.
43 KB/s (447 bytes in 0.010s)
push: copy2sd/000root/Superuser.apk -> /sdcard/000root/Superuser.apk
push: copy2sd/000root/su -> /sdcard/000root/su
push: copy2sd/000root/install-unroot.sh -> /sdcard/000root/install-unroot.sh
push: copy2sd/000root/install-root.sh -> /sdcard/000root/install-root.sh
push: copy2sd/000root/install-otachk.sh -> /sdcard/000root/install-otachk.sh
push: copy2sd/000root/install-otachk-eg30-ek02.list -> /sdcard/000root/install-o
tachk-eg30-ek02.list
push: copy2sd/000root/install-cleanup.sh -> /sdcard/000root/install-cleanup.sh
push: copy2sd/000root/install-ciq-on.sh -> /sdcard/000root/install-ciq-on.sh
push: copy2sd/000root/install-ciq-off.sh -> /sdcard/000root/install-ciq-off.sh
push: copy2sd/000root/install-boot-zImage.sh -> /sdcard/000root/install-boot-zIm
age.sh
push: copy2sd/000root/install-boot-el29.sh -> /sdcard/000root/install-boot-el29.
sh
push: copy2sd/000root/install-boot-el29-cwm.sh -> /sdcard/000root/install-boot-e
l29-cwm.sh
push: copy2sd/000root/install-boot-el29-cwm-rogue.sh -> /sdcard/000root/install-
boot-el29-cwm-rogue.sh
push: copy2sd/000root/install-boot-el26.sh -> /sdcard/000root/install-boot-el26.
sh
push: copy2sd/000root/install-boot-el26-cwm.sh -> /sdcard/000root/install-boot-e
l26-cwm.sh
push: copy2sd/000root/install-boot-el26-cwm-rogue.sh -> /sdcard/000root/install-
boot-el26-cwm-rogue.sh
push: copy2sd/000root/install-boot-el13.sh -> /sdcard/000root/install-boot-el13.
sh
push: copy2sd/000root/install-boot-el13-cwm.sh -> /sdcard/000root/install-boot-e
l13-cwm.sh
push: copy2sd/000root/install-boot-ek02.sh -> /sdcard/000root/install-boot-ek02.
sh
push: copy2sd/000root/install-boot-ek02-cwm.sh -> /sdcard/000root/install-boot-e
k02-cwm.sh
push: copy2sd/000root/install-boot-eg31.sh -> /sdcard/000root/install-boot-eg31.
sh
push: copy2sd/000root/install-boot-eg31-cwm.sh -> /sdcard/000root/install-boot-e
g31-cwm.sh
push: copy2sd/000root/install-boot-eg30.sh -> /sdcard/000root/install-boot-eg30.
sh
push: copy2sd/000root/install-boot-eg30-cwm.sh -> /sdcard/000root/install-boot-e
g30-cwm.sh
push: copy2sd/000root/install-boot-common.sh -> /sdcard/000root/install-boot-com
mon.sh
push: copy2sd/000root/func.inc.sh -> /sdcard/000root/func.inc.sh
push: copy2sd/000root/busybox -> /sdcard/000root/busybox
27 files pushed. 0 files skipped.
1214 KB/s (2001448 bytes in 1.609s)
...Running Zerg exploit...
Unable to chmod zergrush: No such file or directory
/data/local/tmp/install-zerg.sh: ./zergrush: not found
---- STATUS of ZERG on PREVIOUS few lines ----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Installing persistent root... mount: Operation not permitted
install-root.sh: cannot create /system/app/Superuser.apk: read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
install-root.sh: cannot create /system/xbin/su: read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
link failed Read-only file system
install-root.sh: cannot create /system/xbin/busybox: read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
install-root.sh: /system/xbin/busybox: not found
Done
Waiting for filesystem to sync... Done
---- END LOG ----

Ok thanks for looking into the log but I got it figured out...I'm pretty sure my virus protection was blocking the write. It's all good now rooted ek02 stock now to figure out how to get to el29 from here

Flash a ROM that comes with EL29 kernel and you're done. You can also flash the EL29 modem separately (no rom comes with a modem, they are separate) look at the wiki for all modem downloads. Good luck
Sent from my Blazing ET4G

[Acer _AV041_A100_1.037.00_ww_gen1] root？

[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...

[GUIDE] Universal rooting to any ics that you have the stock firmware.

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

Has anyone successfully gotten s-off via Tacoroot method after accepting the recently

Sent from my ADR6350 using xda app-developers app

Do you mind finishing that sentence? I'm s-off via tacoroot and revolution
Sent from my Pac Inc2 using xda app-developers app

Gotten s-off using tacoroot after accepting the latest OTA
Sent from my ADR6350 using xda app-developers app

I did it when I was running 2.3.4,

I was also 2.3.4. Just follow the instructions exactly and you'll be fine. If it has an error at the radio portion just move on to the revolutionary step and go back to the radio later by putting it in your SD card and going into your boot loader.
sent from my incredibly paranoid inc2

I've been trying all morning and I don't know if my issue is related to the update, but I keep getting hung up on...
"
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
"
here's what I'm getting.
C:\Users\Doug\Desktop\android>adb push tacoroot.sh /data/local/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Users\Doug\Desktop\android>adb shell chmod 755 /data/local/tacoroot.sh
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /data/local/tacoroot.sh: No such file or directory
Any suggestions? Or is my noob showing?

I'll have to look at the instructions when I get home. Did you verify that you downloaded the adb files completely
sent from my incredibly paranoid inc2

I just did a nearly-bricked DI2 rescue & restoration/root - worst than the recent VZW update as it somehow got the leaked China Telecom OTA rom on it - using tacoroot method earlier this month, everything should work as I had to do a few extra steps to restore WiFi & call in to reset the security key coding ...
The likely cause of your error messages about "out of date" is incompatible matches between Android SDK (ADB) and HTC Sync - find & uninstall it, reboot & reinstall your ADB using the latest files. Make sure you downloaded & unzipped the referenced file folders - http://d-h.st/yJQ - along with other files needed for adb to run
With those long line-by-line commands, it's easier for newbies to do & cut-n-paste at the C:\command prompt - check & then hit [Enter] key and match the results
Use the latest HTC drivers & uninstall other usb device drivers, reboot and turned off your anti-virus/firewall temporary, running Windows 8 or 7/Vista?? Try a different USB 2.0 port and/or OEM micro-usb cable ...

I failed
I failed hardcore with tacoroot

jd1ezal said:
I failed hardcore with tacoroot
Click to expand...
Click to collapse
Well, we need more info to help. Are you comfortable with command prompt? If not, I could see how its difficult.
---------- Post added at 10:47 PM ---------- Previous post was at 10:42 PM ----------
skijunkie said:
I've been trying all morning and I don't know if my issue is related to the update, but I keep getting hung up on...
"
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
"
here's what I'm getting.
C:\Users\Doug\Desktop\android>adb push tacoroot.sh /data/local/
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Users\Doug\Desktop\android>adb shell chmod 755 /data/local/tacoroot.sh
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /data/local/tacoroot.sh: No such file or directory
Any suggestions? Or is my noob showing?
Click to expand...
Click to collapse
What do you get when you type the following
Code:
adb kill-server
adb start-server
adb devices
You will need to be in your android directory and as administrator.

wondering if it is possible to root and s-off with verizons latest update 6.04.605.07 710RD ?

boffster99 said:
wondering if it is possible to root and s-off with verizons latest update 6.04.605.07 710RD ?
Click to expand...
Click to collapse
Yes it is. Just follow the Tacoroot instructions.

do you have to downgrade?

jncryer said:
do you have to downgrade?
Click to expand...
Click to collapse
Yes. Revolutionary only supports hboot .97
Sent from my SCH-I535 using Tapatalk 2

Develop Bugs

welcome