Database Info

1.55.531.3 rom?

Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.

I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU

M9x3mos said:
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
Click to expand...
Click to collapse
yeah, what you are looking for doesn't exist at the moment. i too thought about making a nandroid of the the new ROM for people to flash, but since the new setup comes with a new radio, new kernel, new HBOOT, etc., i'm not sure how it would fly if someone just flashed the nandroid?

Hboot n radio would be the only thing missing... Kernels sits in recovery....
rooted 1.55.531.3 with clockwork recovery and SU

I know I made a flashable package out of the Google Talk apk file, and either did or meant to make some out of the other apps in it - I'm not sure which thread it's in.
I can check later and link it. Not sure what else anyone did with it, if wifi calling wasn't pulled forward from it I'll have a package for that sometime soon anyway.
I also never did get a chance to check what the gps changes were I remember being in it.
Edit:
Link to Gtalk flashable zip package from that update.
Sent from my Bulletproof_Doubleshot using xda premium

nlarge said:
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Do you have the stock rom for 1.55.531.3 that I can flash on my mt4gs? I would really appreciate it

http://forum.xda-developers.com/showthread.php?t=1484679
http://forum.xda-developers.com/showthread.php?t=1433805

It would be flashed as if restoring a nandroid. I would flash the above link. If you really want it I can send it
rooted 1.55.531.3 with clockwork recovery and SU

Thanks. Okay, this is where I am:
Unlocked bootloader with htcdev
s-on
hboot 1.45.0013
software 1.55.531.3
Would like to achieve root so that I can flash custom roms/use titanium backup. From what I can tell, nlarge was able to accomplish this. (http://forum.xda-developers.com/showthread.php?t=1474933&page=6). However, couldn't post on that thread because I have less than 10 posts....sorry.
Cannot use temproot (FR3VO) method because says needs s-off and/or adb mount issue:
An error occurred while running the exploit (-1) (errno: 22)
c:\Android>adb wait-for-device
c:\Android>adb remount
remount failed: Operation not permitted
c:\Android>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
c:\Android>adb shell mount -oremount,suid /dev/block/mmcblk0p23 /data
mount: Operation not permitted
c:\Android>adb shell mkdir /vendor/bin
mkdir failed for /vendor/bin, Read-only file system
c:\Android>adb shell chown root.shell /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb push ./sqlite3 /vendor/bin
cannot stat './sqlite3': No such file or directory
c:\Android>adb push ./su /vendor/bin
cannot stat './su': No such file or directory
c:\Android>adb push ./busybox /vendor/bin
cannot stat './busybox': No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell chmod 6555 /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chmod 4555 /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell busybox --install -s /vendor/bin
busybox: permission denied
c:\Android>adb shell sync
c:\Android>adb shell chmod 6555 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb install ./Superuser.apk
can't find './Superuser.apk' to install
c:\Android>pause
Press any key to continue . . .​
So, I understand, permission denied/operation not permitted, I assume because I don't have root.
When I look at superuser, it says "su binary voutdated" and when I tap to check for updates, automatic update fails and error message "su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Can't boot into recovery mode, phone just sits on mytouch 4g slide screen. Again, I assume because no root. Same thing happens if I try to factory reset, just stays on the mytouch 4g slide screen.
Anyone have any suggestions? I am going crazy trying to get this phone to work. I would really appreciate the help!

Flash clock work recovery... I think I linked it somewhere... Or Google will help
rooted 1.55.531.3 with clockwork recovery and SU

Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU

nlarge said:
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!

Put your phone in fastboot. Pull battery, hold down and power then try again
rooted 1.55.531.3 with clockwork recovery and SU

How to fastboot flash recovery
Return to Contents Page - doubleshot Developers Reference
Boltinghouse said:
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Click to expand...
Click to collapse
(hah, thanked but meant to hit quote)
What you need to do is go here: http://clockworkmod.com/rommanager
Scroll down the list and find the recovery for our device (5.0.2.7 for the myTouch 4G Slide) - download this.
Put it in the same folder as 'fastboot.exe' on your computer. Rename it to recovery.img
On your phone, turn off 'fastboot' in power options.
Power off the phone.
Now, give it a minute to power off - then hold the volume down button and press power.
Now it will boot up to the hboot menu. The list presented will have you highlighted on the word 'fastboot' - press power to choose this.
Now you are presented with the fastboot menu. It should say fastboot with a red highlight around it near the top.
At this time you should plug the USB cord from your computer into the phone. It will update to say fastboot USB in red highlight now.
-okay-
We have the phone booted up in fastboot, attached to the computer, and ready to work with.
Open up your command prompt, and navigate to the folder where you have the fastboot command. This is the same folder that you have the new clockworkmod recovery.img in from before.
In your terminal now type:
Code:
fastboot devices
This will come back with your device, serial number, and show you it is connected and ready to go. (if it is not something is wrong)
Now type:
Code:
fastboot flash recovery recovery.img
Let's break this down:
fastboot = activates the fastboot.exe command, and says that what's typed next uses the definitions in that fastboot.exe file.
flash = command that says write to
recovery = destination (name of partition) being written to
recovery.img = file written to previously defined location.
----
Since you have the new clockworkmod recovery file in the same folder as fastboot.exe, and you renamed it to recovery.img, then the previously shown command will overwrite your stock recovery with the new image you are providing it.
At this point you should have clockworkmod recovery in place of your stock recovery when you boot the device to hboot menu and select recovery.
Let us know if you have any other problems.

Good explanation blue.... It sounded like he knew what he was doing, hence my quick correction...
Hate typing a lot out from phone!
rooted 1.55.531.3 with clockwork recovery and SU

OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~

Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
Boltinghouse said:
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Click to expand...
Click to collapse
rooted 1.55.531.3 with clockwork recovery and SU

nlarge said:
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
It's all good, I know being a chick I'm in the minority here. Either way, thank you so much.

So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?

it depends on what you want to do with your phone...
If you just want to be able to make recovery and flash ROMS than you dont need s-off
If you want to play with other stuff(radios and mounts) then you need s-off.
I personally like doing things to my phone so I would like to get to s-off. I am ok with it for now, but S-off will give me the full control I want.
qwerty3656 said:
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
Click to expand...
Click to collapse

I have bricked my phone I think please help.

Hello I have a HOX from att with the 1.85 software number.
I attempted to use this method to root my phone. http://forum.xda-developers.com/showthread.php?t=1709296
I proceeded with the instructions as followed and was sucessfully able to run these commands:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
adb shell ls -l /data/local.prop
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
The command prompt indicated a successful remount. (At this point on the phone only the notification bar was working and nothing else was on the screen and right now that is where my phone is stuck, but i proceeded on)
I entered this command adb push su /system/xbin/su
and recieved a error
failed to copy 'su' to '/system/xbin/su': Read-only file system
At this point I did not know what to do I proceeded to reboot and then remount again.
Now I am stuck with just the notification bar responding and the settings not opening.
I am hoping anyone can help me also please PM me. I would appreciate any help with my situation.
If possible could someone g chat with me as typing and waiting for replies is taking to long.
Sorry if I come off as needy but the possiblity of losing the phone I recently bought is scaring me

sunny342 said:
Hello I have a HOX from att with the 1.85 software number.
I attempted to use this method to root my phone. http://forum.xda-developers.com/showthread.php?t=1709296
I proceeded with the instructions as followed and was sucessfully able to run these commands:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
adb shell ls -l /data/local.prop
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
The command prompt indicated a successful remount. (At this point on the phone only the notification bar was working and nothing else was on the screen and right now that is where my phone is stuck, but i proceeded on)
I entered this command adb push su /system/xbin/su
and recieved a error
failed to copy 'su' to '/system/xbin/su': Read-only file system
At this point I did not know what to do I proceeded to reboot and then remount again.
Now I am stuck with just the notification bar responding and the settings not opening.
I am hoping anyone can help me also please PM me. I would appreciate any help with my situation.
If possible could someone g chat with me as typing and waiting for replies is taking to long.
Sorry if I come off as needy but the possiblity of losing the phone I recently bought is scaring me
Click to expand...
Click to collapse
I ended up just turning off the phone and then opening hboot and doing a factory reset. It got me back to stock so at least I can use my phone

sunny342 said:
I ended up just turning off the phone and then opening hboot and doing a factory reset. It got me back to stock so at least I can use my phone
Click to expand...
Click to collapse
When you try and mount your phone, since you factory reset through Hboot, you'll need to reformat your SD card because you corrupted it. Just some information for you.

Factory reset in bootloader, plug it in to comp, bring up "my computer" on your computer. Right click removable storage and choose "format"
Sent from my One X using Tapatalk 2

[Q] Thinkpad 1838 25U Bricked

I have a Thinkpad 1838 25U tablet that is stuck at the boot screen after attempting to flash it with closckworkmod. I cannot access the internal storage files to restore the operating system and when I contacted Lenovo they suggested that I reinstall the operating system. When I try to do that in recovery mode all I get is an error that states "file_getprop: failed to stat "/system/build.prop" No such directory E:Error in /tmp/sideload/pack.zip (status 7) Installation aborted. Is there a way to access the internal storage files or a way to re-install the system when the tablet is soft bricked?
What happen was I rooted my tablet with RootDebugfs.bat and then I followed the directions to How to Install ClockworkMod Recovery on the Lenovo Thinkpad Tablet on the UnLocker site. Where I messed up was changing the command that was given in the directions. I opened the command prompt and entered each command:
adb push A2109_CWMrecovery-6.0.1.9c.img /mnt/sdcard/
adb shell
su
mount -o rw,remount /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
dd if=/mnt/sdcard/A2109_CWMrecovery-6.0.1.9c.img of=/dev/block/mmcblk0p1
After trying that several time with no luck I changed the last command and file or directory to mmcblk0p5 instead of mmcblk0p1
dd if=/mnt/sdcard/recovery.img of=/dev/block/mmcblk0p5
After doing that my screen went blank and when I restarted it, it will not go past the boot screen.
I did back up my system as a backup.ab file. My OS is ICS 4.03 but when I try to re-install the updates on the Lenovo site I get the error message "file_getprop: failed to stat "/system/build.prop" No such directory E:Error in /tmp/sideload/pack.zip (status 7) Installation aborted."
Can anything be done to fix it. I am presently getting ready to start my 2nd semester of college in computer programming and I let my inexperience of commands get the best of me. And caused a big mess.
Is my tablet ruined. Lenovo service dept. said that since my warranty has expired I will have to pay $575 up front to have it repaired.
Any suggestions will be of great help.

[Q] will need help with instructions

So i got instructions from ganship about how to fix my phone, but he hasn't replied and i need it fixed by tmr because my friend needs his laptop back
So let's say all my adb files are in also
C:\Users\MosiMan\Desktop\Android stuff\One_S_All-In-One_Kit\Data
my rom: cm-10-20130109-bruce2728-pyramid
is also in the same folder
Ganeship told me to
"imp steps :
you need to push the rom.zip to data partiton
how you do that ?
adb push <name_of_the _rom.zip> /data
so if i were to run that cmd in my postion would it be
C:\Users\MosiMan\Desktop\Android stuff\One_S_All-In-One_Kit\Data>adb push cm-10-20130109-bruce2728-pyramid.zip /data
after running this command I got
1663 KB/s <155280218 byes in 91.168s>
then he also told me to follow http://forum.xda-developers.com/showpost.php?p=27679108&postcount=4651
so is
adb shell "echo 'boot-recovery ' > /cache/recovery/command"
adb shell "echo '--update_package=ROM_Folder:name_of_ROM.zip' >> /cache/recovery/command"
adb reboot recovery
in my situation,when i punch it in cmd is it
adb shell "echo 'boot-recovery ' > /cache/recovery/command"
adb shell "echo '--update_package=C:\Users\MosiMan\Desktop\Android stuff\One_S_All-In-One_Kit\Datar:cm-10-20130109-bruce2728-pyramid.zip' >> /cache/recovery/command"
adb reboot recovery
or is it
C:\Users\MosiMan\Desktop\Android stuff\One_S_All-In-One_Kit\Data>adb shell "echo 'boot-recovery ' > /cache/recovery/command"
C:\Users\MosiMan\Desktop\Android stuff\One_S_All-In-One_Kit\Data>adb shell "echo '--update_package=C:\Users\MosiMan\Desktop\Android stuff\One_S_All-In-One_Kit\Data:cm-10-20130109-bruce2728-pyramid.zip' >> /cache/recovery/command"
C:\Users\MosiMan\Desktop\Android stuff\One_S_All-In-One_Kit\Data>adb reboot recovery
Update 2
So i reboot recovery and ran
adb shell "echo 'boot-recovery ' > /cache/recovery/command"
adb shell "echo '--update_package=C:\Users\MosiMan\Desktop\Android stuff\One_S_All-In-One_Kit\Datar:cm-10-20130109-bruce2728-pyramid.zip' >> /cache/recovery/command"
adb reboot recovery
and it rebooted and all i got was
Finding update package...
E:unkown volume for path [C:\Users\MosiMan\Desktop\Android_stuff\One_S_All_In-One_Kit\Data:cm-10-20130109-bruce2728-pyramid.zip]
E:Can't mount C:\Users\MosiMan\Desktop\Android_stuff\One_S_All_In-One_Kit\Data:cm-10-20130109-bruce2728-pyramid.zip
Installation aborted.
So I don't know what im doing wrong, like do i need special settings to be on in recovery?
Update 1
i tried running adb shell "echo 'boot-recovery ' > /cache/recovery/command"
and i got
/sbin/sh: can't create /cache/recovery/command: nonexistent directory
oh and do I include those quotations too? and do i run those cmds in my adb folder?
I'm very sorry but i really need to fix this phone by today, last time i tried to do all of this it said error on 4ext, so yeah i need precise instructions for my situation

sorry for the vagueness
here are the proper commands
adb shell "echo 'boot-recovery ' > /cache/recovery/command"
adb shell "echo '--update_package=/data/cm-10-20130109-bruce2728-pyramid.zip' >> /cache/recovery/command"
adb reboot recovery
to simply explain:
first you pushed the cm zip file to /data right? (using adb push command)
you need to link that pushed cm zip ...for the recovery to find it not the one on your desktop (obviously phone recovery wasnt going to fetch the zip file from your PC/laptop )

ganeshp said:
sorry for the vagueness
here are the proper commands
adb shell "echo 'boot-recovery ' > /cache/recovery/command"
adb shell "echo '--update_package=/data/cm-10-20130109-bruce2728-pyramid.zip' >> /cache/recovery/command"
adb reboot recovery
to simply explain:
first you pushed the cm zip file to /data right? (using adb push command)
you need to link that pushed cm zip ...for the recovery to find it not the one on your desktop (obviously phone recovery wasnt going to fetch the zip file from your PC/laptop )
Click to expand...
Click to collapse
intresting...because it said
Finding update package....
Opening update package...
E:Can't open /data/cm-10-20130109-bruce2728-pyramid.zip
(no such file or directory)
Installation aborted.
I guess i'll format all partition and redo part 1
redid the whole thing
same results... but i notice it would show a triangle for less than a second but that's all...could this be because it recovery has no sd card so it says boot in safemoode because that's all i know about

Ohh are you pushing the cm zip file with phone connected from recovery?
Then push the zip file to just "/" (root directory) and make the necessary change in recovery command too (Rom path)
Edit: I forgot to subscribe to this thread. That's why the reply was late sorry
Sent from my HTC Sensation 4G using xda premium

Wait... I'm confused
Sent from my GT-I9300 using xda premium

ganeshp said:
Ohh are you pushing the cm zip file with phone connected from recovery?
Then push the zip file to just "/" (root directory) and make the necessary change in recovery command too (Rom path)
Edit: I forgot to subscribe to this thread. That's why the reply was late sorry
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
are you talking about the very first step? aren't i suppose to push the cm zip when it's in recovery,.... isn't that the only way
so whats the command and when do i do it?

anthonyly said:
are you talking about the very first step? aren't i suppose to push the cm zip when it's in recovery,.... isn't that the only way
so whats the command and when do i do it?
Click to expand...
Click to collapse
Yeah pushing from recovery would do
And you push it to just "/" path not "/data"
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Yeah pushing from recovery would do
And you push it to just "/" path not "/data"
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
so shall i format when i get the laptop back and do
C:\Users\MosiMan\Desktop\Android stuff\One_S_All-In-One_Kit\Data>adb push cm-10-20130109-bruce2728-pyramid.zip /
and the rest is the same right?

Here are the rest
adb shell "echo 'boot-recovery ' > /cache/recovery/command"
adb shell "echo '--update_package=/cm-10-20130109-bruce2728-pyramid.zip' >> /cache/recovery/command"
adb reboot recovery
Sent from my HTC Sensation 4G using xda premium

TWRP for the new cat flip phone?

The novel CAT S22 Flip was released in September, and is pretty much the only of its kind. It actually has an unlocked bootloader, and I was excited to try to root it. However, there's no version of TWRP designed specifically for it! Having never rooted anything before, does anyone know my options in this case to get TWRP for this phone? (Or another method of root I'm not aware of would also be fine.) Thanks!

Shoitah said:
The novel CAT S22 Flip was released in September, and is pretty much the only of its kind. It actually has an unlocked bootloader, and I was excited to try to root it. However, there's no version of TWRP designed specifically for it! Having never rooted anything before, does anyone know my options in this case to get TWRP for this phone? (Or another method of root I'm not aware of would also be fine.) Thanks!
Click to expand...
Click to collapse
Hey. I'm in the same boat. I need to add su binary but looks like the only way to do it is with TWRP. Have you succeeded? I keep trying to find a way to do it, so far no luck.

TWRP isn't needed at all to push ( suitable ) SU binary onto Android's filesystem: you achieve this by means of ADB, too

jwoegerbauer said:
TWRP isn't needed at all to push ( suitable ) SU binary onto Android's filesystem: you achieve this by means of ADB, too
Click to expand...
Click to collapse
Sweet!!! How does it look like?
I just tried adb sideload <file.zip> while in recovery mode and i'm getting this
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
When check adb devices its shows that device is unauthorized. But it's only unauthorized in recovery mode.

Actually looks like I have a problem with recovery mode. Instead I'm getting "No command" screen. It's not even getting into recovery

To perform a ADB Sideload - what is used to flash a Stock ROM - phone must get booted into Sideload mode at 1st
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP>
adb reboot

Oh cool. Didn't know that I could reboot stratight to sideload and bypass initial recovery menu. Thank you!
As for my previous issue with "No command" error on recovery boot, I managed to resolve it. When It's gets to "No command" screen, you need to hold Power + Volume Down just long enough to tap Volume Up. And then recovery menu will appear. So Press Power + Volume Down and then tap Volume Up.
When I tried to sideload su binary with
Code:
adb sideload <file.zip>
On the mobile screen i'm getting this error
Code:
E:failed to verify whole-file signature. Update package verification took 0.5 s ( result 1)
E:Signature verification failed
E: error: 21
Looks like recovery not allowing to install unsigned packages. Is there a way around it? Do I need to source another su binary or there is a way to sign it?

Ok. I think I'm getting closer to the core issue. I thought that I rooted the device, but I only unlocked the bootloader. So device is not rooted. As per original thread topic, looks like there is still no TWRP yet and boot.img is not accessible to modify. Tried to get boot.img directly from the device, but getting - permission denied.
Any other walkarounds i should try?

SU binary isn't a signed package. It's a ~110KB file you have to push onto Android OS, preferred to /data/local/tmp directory and afterwards have to make it executable.

I've downloaded Chainfire SuperSu Zip packages, unpacked it and got a su file from arm64 folder. As you mentioned, su file is 108.5KB =)
I've pushed it to /data/local/tmp and made it executable
Code:
S22FLIP:/ $ ls -la /data/local/tmp
total 114
drwxrwxrwx 2 shell shell 3488 2022-12-22 09:36 .
drwxr-x--x 4 root root 3488 1970-01-01 12:15 ..
-rwxrwxrwx 1 shell shell 108496 2008-02-29 03:33 su
Maybe I'm missing something, I still get
Code:
S22FLIP:/ $ su
/system/bin/sh: su: inaccessible or not found

You must tell Android where the SU binary is located
Code:
cd /data/local/tmp & su
or
Code:
/data/local/tmp/su

jwoegerbauer said:
You must tell Android where the SU binary is located
Code:
cd /data/local/tmp & su
or
Code:
/data/local/tmp/su
Click to expand...
Click to collapse
Hi. I am trying to root the phone. I tried with QFIL to get the boot.img file with no luck.... I am trying now with su. I put the su binary where you said and execute it.
Now what should I do? If you can help me, I will be grateful

IMO you can't root a phone ( a conglomerat of hardware pieces ) but only enable Android OS to run system commands as root ( will say with elevated rights if those are required ) by means of su.
Knowing this you would open a terminal window in Android and type out
Code:
<FULLPATH-TO-SU-BINARY-HERE>/su -c "<SHELL-COMMAND-THAT-REQUIRES-ELEVATED-RIGHTS-HERE>"
Example:
Code:
/data/local/tmp/su -c "mount -o remount,rw -t auto /system"

jwoegerbauer said:
IMO you can't root a phone ( a conglomerat of hardware pieces ) but only enable Android OS to run system commands as root ( will say with elevated rights if those are required ) by means of su.
Knowing this you would open a terminal window in Android and type out
Code:
<FULLPATH-TO-SU-BINARY-HERE>/su -c "<SHELL-COMMAND-THAT-REQUIRES-ELEVATED-RIGHTS-HERE>"
Example:
Code:
/data/local/tmp/su -c "mount -o remount,rw -t auto /system"
Click to expand...
Click to collapse
Doesn't work. It looks like the su binary doesn't grant system commands root
I really don't know what to do......