Develop Bugs

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

[Acer A200] GUIDE FOR ICS OTA ROOT

Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or getting flammed because you re-rooted your phone instead of your tablet because you forgot to unplug your phone from the computer while the tablet was plugged in...
Please do some research if you have any concerns about rooting your device! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Ok, this was a pain in the arse!
I hope I can remember the steps I took in order to get this done.
By the way, I'm using windows
adb push mempodroid /data/local
adb push su /data/local
adb shell
$ chmod 777 /data/local/mempodroid
Click to expand...
Click to collapse
Then I went to here as directed,
http://rkeene.org/projects/info/wiki/210
but didn't follow the steps as they were shown because I got stuck many times and had to start over.
So here are my steps.
1.
$ /data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
which then should turn the $ into a #
2.
# mkdir /data/x-root /data/x-root/bin
Click to expand...
Click to collapse
3. Download this,
http://www.rkeene.org/projects/info/resources/diatribes/root-toshiba-thrive/busybox
and then move the file to where you have mempodroid and su so you can adb push them easier
4.
adb push busybox /data/x-root/bin/busybox
adb push su /data/x-root/bin/su
adb shell
Click to expand...
Click to collapse
5. This is where it got tricky. If you don't pay close attention, you will most likely do what I did and put files where they aren't supposed to go. So please, PAY ATTENTION!
If you still have the # in the shell, move forward. Otherwise,
/data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
and then move forward once # is confirmed.
# cd /data/x-root/bin
# chmod 755 busybox
# ./busybox bash
Click to expand...
Click to collapse
Now, there is no doubting it, you will get the "bash: precmd: not found" error.
# unset PS1 PROMPT_COMMAND
# ./busybox bash
# for tool in $(./busybox --list); do ln -s busybox $tool; done
# PATH="${PATH}:/data/x-root/bin"; export PATH
Click to expand...
Click to collapse
6. AGAIN, PAY CLOSE ATTENTION HERE!!
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
Click to expand...
Click to collapse
7. This is where I ran into another problem, so pay attention.
# cd /
# mkdir /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
You will see nothing as the steps describe. This is because we skipped a step. Why? Because mount -o ro -t ext4 /dev/loop0 /dev/tmpdir for some strange reason wouldn't unmount so I could mount the next step. So instead, we move on and then check again.
Here is the removed step
# mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
# umount /dev/tmpdir
Click to expand...
Click to collapse
You can try this but I advise not to or you could very well run into the same issue I had where you can't unmount in order to move on with the root process
# mount -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
And now you will see /system mounted.
8.
# cp /data/x-root/bin/su /dev/tmpdir/bin/
# chmod 4555 /dev/tmpdir/bin/su
# umount /dev/tmpdir
# losetup -d /dev/loop0
# sync
# reboot
Click to expand...
Click to collapse
9. Now once your A200 reboot and displays the home screen, we will confirm.
adb shell
[email protected]:/ $ su
Click to expand...
Click to collapse
If the $ doesn't turn into a #, you did something wrong...
Thank you hexmare, for opening this thread and giving the guidance.
Thank you d10369319, for "/data/local/mempodroid 0xd9f0 0xaf47 sh", I would have never figured this out.
Thank you RKeene, for writing out the guide to Root the Toshiba Thrive
And Thank you Saurik along with zx2c4, for mempodroid

Ok, for some reason, /system still refuses to mount with "mount -o remount,rw /system"
So my solution is this,
$ su
# cd /data/x-root/bin
# chmod 755 busybox
# unset PS1 PROMPT_COMMAND
./busybox bash
# PATH="${PATH}:/data/x-root/bin"; export PATH
# cd /
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
# mount -t ext4 /dev/loop0 /dev/tmpdir
Click to expand...
Click to collapse
You will have to go to /dev/tmpdir in order to do anything with /system but it is the secret passage way for now...

Why is there still no A200 forum?

agentfazexx said:
Why is there still no A200 forum?
Click to expand...
Click to collapse
Maybe there will be now that we have made some progress...

agentfazexx said:
Why is there still no A200 forum?
Click to expand...
Click to collapse
+1 A200 Forum

Enjoy your ICS A200 owners. I just saw a tweet from AcerAmerica that ICS is being rolling out to A200

Hello to all,
My A200 has been upgraded today 'OTA' , to ICS (V: 4.0.3) , so Europe/France seems to be available, now.
Applying this procedure, all goes fine, and my A200 is rooted.
I'm very happy
A lot of thanks to people having discovered this procedure, particularly mempodroid which set all of this possible.
Greetings

the last time when you do losetup -d /dev/loop0
returns No such device or address?????
ive been through it twice now
*EDIT* Nevermind I figured out my problem...I was typing in reboot instead of using the hardware power button. Got root now, sweet!

I am sooo glad we can now root the a200, but I cannot get mine to work. I have went through the steps 3+ times and had issues each time. I thought I had it twice and then tried Titanium backup root and it said it didn't work.
I can't see at all where I've gone wrong..

That's very strange because Titanium Backup works just fine for me...

rom toolbox pro doesnt work when changing numbers in kernel tweaks...numbers dont stick
titanium works though

ran into a mounting issue
i was attempting to root my A200 with the OTA ICS
first attempt i ran into an issue were i am unable to mount
# mount -t ext4 /dev/loop0 /dev/tmpdir
mount: invalid argument
so i then replaced ext4 to EXT4 and i then received error
# mount -t EXT4 /dev/loop0 /dev/tmpdir
mount: No such device
could some one please tell me where i went wrong thank you in advance

what i do wrong when i try adb push mempodroid /data/local i get evertime this here :/
D:\android-sdk-windows\platform-tools>adb push mempodroid /data/local
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Ghorn

ghorn222 said:
what i do wrong when i try adb push mempodroid /data/local i get evertime this here :/
Ghorn
Click to expand...
Click to collapse
Go download the drivers from Acer's website for this device

johnsonj067 said:
i was attempting to root my A200 with the OTA ICS
first attempt i ran into an issue were i am unable to mount
# mount -t ext4 /dev/loop0 /dev/tmpdir
mount: invalid argument
so i then replaced ext4 to EXT4 and i then received error
# mount -t EXT4 /dev/loop0 /dev/tmpdir
mount: No such device
could some one please tell me where i went wrong thank you in advance
Click to expand...
Click to collapse
You have to follow the guide to the T or you will run into numerous problems and stop signs. Try again

daimerion said:
rom toolbox pro doesnt work when changing numbers in kernel tweaks...numbers dont stick
titanium works though
Click to expand...
Click to collapse
That's because we don't have a custom kernel yet. Just wait a little while.

Unfortunate the root isn't 100% cool my boot loader Is unlocked though.
Droid 3 bldr is locked down however changing numbers in rom toolbox works w/o custom kernals or modules.
http://www.acertabletforum.com/foru...iscussions/3649-how-unlock-boot-loader-4.html
^this Does work

su file?
This may be a stupid question, but where does one get the su file they're supposed to push to the tablet in the first step? I searched and searched, and finally found one that I downloaded, but when I tried this method with that su file, everything seems to work perfectly, but when I reboot and type su I get a segmentation fault. This is feels like something everyone knows but me, because every guide I can find that has anything to do with rooting from adb it seems the possession of an the su file is just assumed.

shwilson24 said:
This may be a stupid question, but where does one get the su file they're supposed to push to the tablet in the first step? I searched and searched, and finally found one that I downloaded, but when I tried this method with that su file, everything seems to work perfectly, but when I reboot and type su I get a segmentation fault. This is feels like something everyone knows but me, because every guide I can find that has anything to do with rooting from adb it seems the possession of an the su file is just assumed.
Click to expand...
Click to collapse
Did u use reboot command or the power button on the tab? It only worked for me when I used the power button to turn off then on

daimerion said:
Did u use reboot command or the power button on the tab? It only worked for me when I used the power button to turn off then on
Click to expand...
Click to collapse
I tried using the power button. Same result. Where did you get the su file from?

[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

[SOLVED] Bootloop after Bootanimation

i think i chose a wrong bootanimation.
i am in bootloop now in this animation.
connected via adb it recognized my stick but have only read rights.
rm not possible.
any tips?
/e: solved with pc version of kingo root.

Xperience Z said:
i think i chose a wrong bootanimation.
i am in bootloop now in this animation.
connected via adb it recognized my stick but have only read rights.
rm not possible.
any tips?
Click to expand...
Click to collapse
If you use the fire stick:
I wouldn't know how to solve your exact problem but im sure my full guide will sort you out:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298

sconnyuk said:
If you use the fire stick:
I wouldn't know how to solve your exact problem but im sure my full guide will sort you out:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
Click to expand...
Click to collapse
Code:
X:\>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ cd /sdcard/
cd /sdcard/
[email protected]:/sdcard $ ls
ls
Alarms
Android
DCIM
Download
FireStarterUpdates
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
amazonmp3
backups
[COLOR="DeepSkyBlue"]downgrade.bin[/COLOR]
edid.hex
image_cache
[email protected]:/sdcard $ cp downgrade.bin /cache/
cp downgrade.bin /cache/
cp: /cache/downgrade.bin: Permission denied
1|[email protected]:/sdcard $mv downgrade.bin /cache/
mv downgrade.bin /cache/
mv: /cache/downgrade.bin: Permission denied
1|[email protected]:/mnt/sdcard $ rm -f /cache/*.bin
rm -f /cache/*.bin
[email protected]:/mnt/sdcard $ rm -f /cache/*.zip
rm -f /cache/*.zip
1|[email protected]:/mnt/sdcard $ cp ./downgrade.bin /cache/
cp ./downgrade.bin /cache/
cp: /cache/downgrade.bin: Permission denied
then i tried to delete the bootanimation.zip from /system/media/
Code:
[email protected]:/mnt/sdcard $ rm -f /system/media/bootanimation.zip
rm -f /system/media/bootanimation.zip
rm: /system/media/bootanimation.zip: Read-only file system
it didn't work. fullbrick?

Hi,
Sorry to hear about your bootloop, hopefully you can still recover from it though
Are you sure the device is correctly rooted?
after running the su command it should return:
[email protected]:
and in your logs above it still shows
[email protected]
Also if you do have root and you want to delete the bootanimation.zip file you need to remount the system partition as rw before it will allow it to be deleted.

Xperience Z said:
Code:
X:\>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ cd /sdcard/
cd /sdcard/
[email protected]:/sdcard $ ls
ls
Alarms
Android
DCIM
Download
FireStarterUpdates
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
amazonmp3
backups
[COLOR="DeepSkyBlue"]downgrade.bin[/COLOR]
edid.hex
image_cache
[email protected]:/sdcard $ cp downgrade.bin /cache/
cp downgrade.bin /cache/
cp: /cache/downgrade.bin: Permission denied
1|[email protected]:/sdcard $mv downgrade.bin /cache/
mv downgrade.bin /cache/
mv: /cache/downgrade.bin: Permission denied
1|[email protected]:/mnt/sdcard $ rm -f /cache/*.bin
rm -f /cache/*.bin
[email protected]:/mnt/sdcard $ rm -f /cache/*.zip
rm -f /cache/*.zip
1|[email protected]:/mnt/sdcard $ cp ./downgrade.bin /cache/
cp ./downgrade.bin /cache/
cp: /cache/downgrade.bin: Permission denied
then i tried to delete the bootanimation.zip from /system/media/
Code:
[email protected]:/mnt/sdcard $ rm -f /system/media/bootanimation.zip
rm -f /system/media/bootanimation.zip
rm: /system/media/bootanimation.zip: Read-only file system
it didn't work. fullbrick?
Click to expand...
Click to collapse
Dont look like your properly rooted.
Plug your stick into Windows pc and run Windows version of Kingo root.
When its finished follow the guide I linked you to.
Let me know how you get on.

this was not the first restart.
kingo root und firetv showed rooted.
i gave root with superuser rights for busybox and other apps

Xperience Z said:
i think i chose a wrong bootanimation.
i am in bootloop now in this animation.
connected via adb it recognized my stick but have only read rights.
rm not possible.
any tips?
Click to expand...
Click to collapse
This is why I said on many occasions that it is not recommended to use Xposed modules or mess with bootanimations on your Fire Tv Stick without a working Recovery system, I also semi bricked my Fire Tv 2 box by putting the wrong bootanimation (non working or wrong resolution on it), but because I had a recent back up & a working recovery I was ok, it even wouldn't find my system via ADB so I was lucky. I won't be doing any modding on my stick until I have a Recovery & can backup my System.

deanr1977 said:
This is why I said on many occasions that it is not recommended to use Xposed modules or mess with bootanimations on your Fire Tv Stick without a working Recovery system, I also semi bricked my Fire Tv 2 box by putting the wrong bootanimation (non working or wrong resolution on it), but because I had a recent back up & a working recovery I was ok, it even wouldn't find my system via ADB so I was lucky. I won't be doing any modding on my stick until I have a Recovery & can backup my System.
Click to expand...
Click to collapse
Im just wondering, where has he said anything about xposed?
All he has to do is root with Kingo root on a PC then follow the guide I put up to downgrade/upgrade/same and fix the bootloop.
As the bootanimation package will be replaced with the new system update if im not mistaken.

He didn't.... did you not understand what I said? I did not quote his post I made my own comment which covered Xposed & bootanimations when it comes to modifying the system files any slip ups without a recovery can cause bricks, this is common sense but not always common knowledge to everyone. Believe it or not I am here to help in this forum not to troll or upset anyone, I have always acted politely & try to go above & beyond to help, if you feel I am trolling please report me to the admin, this may have come across as a little abrupt but I feel like I can't mention it could brick forum members devices without someone moaning at me? Sorry for trying to help out
Sent from my SM-G900F using Tapatalk

@deanr1977
I cant understand why you would want to make a comment like that in this thread, when the op is clearly asking for help with an issue caused by changing the boot animation.
I cant see anywhere in your comment that your 'trying to help out'.
Whatever he chose to do with his device he has already done it, wether you explain to him that moddifying system can cause a brick I think he knows that because he has a brick!
If you feel you need to get the message out about moddifying system files why don't you make a new thread explaining this and link your new thread in the guides thats on here?
I for one won't take offence even though I clearly state the obvious in the 2 guides I put together about risks aswell as other guides on here by other members.
Cant say if other users would like that as they might see it as trolling.
Just saying.

funny. unpossible.
kingo root with pc works.
it's unbricked
thanks
weird. after a restart bootloop again because of the wrong bootanimation.
can somebody updoad me /system/media/bootanimation.zip please?
i don't have a backup. but with kingo root (pc) i'll come into the normal system.
i think i can change it.

Xperience Z said:
funny. unpossible.
kingo root with pc works.
it's unbricked
thanks
weird. after a restart bootloop again because of the wrong bootanimation.
can somebody updoad me /system/media/bootanimation.zip please?
i don't have a backup. but with kingo root (pc) i'll come into the normal system.
i think i can change it.
Click to expand...
Click to collapse
Here you go :
Fire Stick bootanimation.zip os version 5.0.5
http://s000.tinyupload.com/index.php?file_id=86378985064921441797

thanks
#unbricked
on my fire tv box i'll install recovery
but no xposed. for what?
on mobile it makes sense

Xperience Z said:
thanks
#unbricked
on my fire tv box i'll install recovery
but no xposed. for what?
on mobile it makes sense
Click to expand...
Click to collapse
Good to hear !!
Glad my advice is helping
Dont quite get what you mean mate. ?
Elaborate..

It's crazy your bootloop was caused by the bootanimation.zip file alone though because I tested plenty of incompatible files and it only showed a blank screen for about 20 seconds and then loaded the Amazon home screen.
I also just deleted the file and this time there was a different boot animation that just said "fire".
I was testing these in case of boot loop risks before I posted my guide and literally couldn't brick it while I was trying them.
Glad you did get it fixed though, I did try and help but I responded to your post on the custom boot guide where you stated you had a bootloop as I figured it may help anyone else who may come across this issue in the future.

Substratum not working

I have substratum working on 2 other modded moto devices but can't get it to work on this XT1952-4. I am running Descendant-4.0.1_a64_ab Pie. The substratum version is one thousand twenty two. My device is successfuly rooted using @Spaceminer modded phh root. I have Magisk on the other 2 devices. If anyone has any ideas on this I would appreciate it. Thanks

Motomizer said:
I have substratum working on 2 other modded moto devices but can't get it to work on this XT1952-4. I am running Descendant-4.0.1_a64_ab Pie. The substratum version is one thousand twenty two. My device is successfuly rooted using @Spaceminer modded phh root. I have Magisk on the other 2 devices. If anyone has any ideas on this I would appreciate it. Thanks
Click to expand...
Click to collapse
I think that I have a solution if you can run a command from termux or adb for me.
Code:
ls /system/bin | grep .sh
Give me the output of that. I'll probably need you to send me a file afterwards, but I need to get the name of it first. I'll recognize it when I see it. If you get a special character error, drop the dot off of sh.

Wow, I wasn't expecting the legend himself replying. I don't have termux so I will get on the computer and do adb

It says cannot access '/system/bin'

I installed termux and got the following result:
crash_dump32
lshal
phh-on-boot.sh
rw-system.sh
twrp.sh

Motomizer said:
I installed termux and got the following result:
crash_dump32
lshal
phh-on-boot.sh
rw-system.sh
twrp.sh
Click to expand...
Click to collapse
Rename phh-on-boot.sh to phh-on-boot.txt and send it to me. Use the paperclip to attach it. Use a root explorer to copy it to your sdcard first. Or from termux...
Code:
su
cp /system/bin/phh-on-boot.sh /sdcard/phh-on-boot.sh
You can also concatenate it and pipe the output to a text file like this...
Code:
su
cat /system/bin/phh-on-boot.sh > /sdcard/phh-on-boot.txt

Spaceminer said:
Rename phh-on-boot.sh to phh-on-boot.txt and send it to me. Use the paperclip to attach it. Use a root explorer to copy it to your sdcard first. Or from termux...
Code:
su
cp /system/bin/phh-on-boot.sh /sdcard/phh-on-boot.sh
You can also concatenate it and pipe the output to a text file like this...
Code:
su
cat /system/bin/phh-on-boot.sh > /sdcard/phh-on-boot.txt
Click to expand...
Click to collapse
Ok, I copied and renamed the file easily with a file manager. I can't find a paperclip symbol anywhere to attach it. Is there a post quota to allow attachments?

Motomizer said:
Ok, I copied and renamed the file easily with a file manager. I can't find a paperclip symbol anywhere to attach it. Is there a post quota to allow attachments?
Click to expand...
Click to collapse
I believe there is a quota. 10 if I'm not mistaken. Just use the code button "#" and paste the text of it in a reply.

Spaceminer said:
I believe there is a quota. 10 if I'm not mistaken. Just use the code button "#" and paste the text of it in a reply.
Click to expand...
Click to collapse
[#!/system/bin/sh
[ "$(getprop vold.decrypt)" = "trigger_restart_min_framework" ] && exit 0
if [ -f /vendor/bin/mtkmal ];then
if [ "$(getprop persist.mtk_ims_support)" = 1 ] || [ "$(getprop persist.mtk_epdg_support)" = 1 ];then
setprop persist.mtk_ims_support 0
setprop persist.mtk_epdg_support 0
reboot
fi
fi
#Clear looping services
sleep 30
getprop | \
grep restarting | \
sed -nE -e 's/\[([^]]*).*/\1/g' -e 's/init.svc.(.*)/\1/p' |
while read -r svc ;do
setprop ctl.stop "$svc"
done
if grep -qF android.hardware.boot /vendor/manifest.xml || grep -qF android.hardware.boot /vendor/etc/vintf/manifest.xml ;then
bootctl mark-boot-successful
fi
]

Motomizer said:
[#!/system/bin/sh
[ "$(getprop vold.decrypt)" = "trigger_restart_min_framework" ] && exit 0
if [ -f /vendor/bin/mtkmal ];then
if [ "$(getprop persist.mtk_ims_support)" = 1 ] || [ "$(getprop persist.mtk_epdg_support)" = 1 ];then
setprop persist.mtk_ims_support 0
setprop persist.mtk_epdg_support 0
reboot
fi
fi
#Clear looping services
sleep 30
getprop | \
grep restarting | \
sed -nE -e 's/\[([^]]*).*/\1/g' -e 's/init.svc.(.*)/\1/p' |
while read -r svc ;do
setprop ctl.stop "$svc"
done
if grep -qF android.hardware.boot /vendor/manifest.xml || grep -qF android.hardware.boot /vendor/etc/vintf/manifest.xml ;then
bootctl mark-boot-successful
fi
]
Click to expand...
Click to collapse
Try this and see if it works. Place the file on your internal storage, then open up termux and run the following commands.
Code:
mount -o remount,rw /
mv /sdcard/phh-on-boot.txt /sdcard/phh-on-boot.sh
cp -f /sdcard/phh-on-boot.sh /system/bin
chmod 0755 /system/bin/phh-on-boot.sh
reboot
After rebooting, see if substratum will work.
For future reference, the code brackets work like so on XDA...
Code:
The text goes here...[/CODE ← Close this with another bracket. "]"
[CODE]The text goes here...
The bracket was closed, so now it looks different.
This helps formatting when working with scripts.

Spaceminer said:
Try this and see if it works. Place the file on your internal storage, then open up termux and run the following commands.
Code:
mount -o remount,rw /
mv /sdcard/phh-on-boot.txt /sdcard/phh-on-boot.sh
cp -f /sdcard/phh-on-boot.sh /system/bin
chmod 0755 /system/bin/phh-on-boot.sh
reboot
After rebooting, see if substratum will work.
For future reference, the code brackets work like so on XDA...
Code:
The text goes here...[/CODE ← Close this with another bracket. "]"
[CODE]The text goes here...
The bracket was closed, so now it looks different.
This helps formatting when working with scripts.
Click to expand...
Click to collapse
I knew that file I sent you didn't look right, but didn't know how to fix it. Thanks for the code bracket lesson and your patience. Unfortunately the code you had me run in termux didn't get substratum working. So you know, when I first ran into problems on this g7 play I copied the substratum apk over to my z play to see if the package was corrupt but it works fine there. Same with the themes.

Motomizer said:
I knew that file I sent you didn't look right, but didn't know how to fix it. Thanks for the code bracket lesson and your patience. Unfortunately the code you had me run in termux didn't get substratum working. So you know, when I first ran into problems on this g7 play I copied the substratum apk over to my z play to see if the package was corrupt but it works fine there. Same with the themes.
Click to expand...
Click to collapse
Can you check the build number on substratum? Find it in your app list and check near the bottom of it's info. Should look something like the attached screenshot. I'll see what I can dig up about it.

Spaceminer said:
Can you check the build number on substratum? Find it in your app list and check near the bottom of it's info. Should look something like the attached screenshot. I'll see what I can dig up about it.
Click to expand...
Click to collapse
I was trying to send a screenshot of the app info but I guess I can't do that yet, either. Next to the i in a circle at the bottom it reads:
version one thousand twenty two
They spell it out instead of using numerical digits. I have seen it like that even on older versions.
There is more information at ApkMirror. It's even compatible with Android 10. I didn't know that.

@Spaceminer
Could it be that Descendant-4.0.1_a64_ab Pie doesn't have OMS support? I did a full xda search on that and got no results. When I have time I will install another gsi rom and see what happens.

Motomizer said:
@Spaceminer
Could it be that Descendant-4.0.1_a64_ab Pie doesn't have OMS support? I did a full xda search on that and got no results. When I have time I will install another gsi rom and see what happens.
Click to expand...
Click to collapse
It's been quite awhile since I've tested descendant. That could be the case but I doubt it. OMS should be baked into the source code. I have been wrong before though. I'll see what I can find about that.

Spaceminer said:
It's been quite awhile since I've tested descendant. That could be the case but I doubt it. OMS should be baked into the source code. I have been wrong before though. I'll see what I can find about that.
Click to expand...
Click to collapse
I was just at the descendant telegram group and asked about OMS support. Dil3mma4 himself answered and said that they never really cared about substratum, nor do they now.

Motomizer said:
I was just at the descendant telegram group and asked about OMS support. Dil3mma4 himself answered and said that they never really cared about substratum, nor do they now.
Click to expand...
Click to collapse
I think this is the answer. It looks like it's unsupported.