Database Develop

Temp root for apps required root access (for s-on IS)

Psneuter exploit is working on IS, but because /system is locked on s-on phones, we can't copy su and superuser.apk into /system, apps required root access can't work.
The following procedure uses psenuter exploit to gain adb shell root, and then copy su (without privilege control ) and busybox into /sbin (which is on rootfs and in the global PATH list) to gain root access for apps.
The procedure:
1. Unzip the attached .zip into a directory (like c:\adb)
2. Open a command prompt and cd to the directory where you extracted the .zip (like cd \adb)
3. run pushroot.bat (simply type pushroot)
4. adb shell /data/local/tmp/getroot
5. adb shell
6. you are now in # prompt. Type /data/local/tmp/pushroot
You have to redo steps 4,5,6 once you reboot your phone.
The procedure will have all apps gaining root access.
!!USE ON YOUR OWN RISK!!
Known working programs: Root explorer, Titanium backup, gscript lite, trasproxy 2.04, ...
Some apps check existence of su in /system/xbin , and reject to proceed if the su binary is not exist (like transproxy 3.08). For this kind of apps, this procedure won't help.

Nice but old news mate...
Sent from my HTC Incredible S using XDA Premium App

Good job...thanks

Thanks for writing this up, might quell the thirst for S-OFF a little longer

/system/ is writeable btw, if you remount it, but after reboot everything u done will be changed to the way it were before.
so a temp root in xbin is possible also, only it will be gone afterwards (atleast i never tried this, but should work also...)

Yes. /system could be remount in rw with root. However, the files you wrote will be gone after you remount ro, and then you won't be able to copy the same filename into the same location again before next reboot ( I don't know why, actually!!). This is why I put su in sbin instead of /system/xbin.

thanks to your files 非常感谢你的工作。

Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?

faf said:
Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?
Click to expand...
Click to collapse
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk

pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....

itandy said:
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Definitely, this is the way to go.
Unfortunately, the root exploit I know could run on device itself, including
rageagainstthecage (ratc) and local root exploit (hotplug) both failed on IS.
The solution will be nearly perfect if we can get temp root on IS without a computer link.
Any input will be welcome.

sky1212 said:
pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....
Click to expand...
Click to collapse
Please then type adb shell.
If you see # but not $, do
cd /data/local/tmp
rm ./cp
ln busybox cp
./pushroot
Then you finished the install.
If you see $, please do all over again.

You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work

l0st.prophet said:
You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work
Click to expand...
Click to collapse
Adfree is working for me. Are you getting some type of error message?
MetaMorph, screenshot and MyBackup Root are also working.
I had to mount system, then push su to /system/xbin. Then install BusyBox Installer from Market.

No erro, still got the ads. I've tried rebooting & rerooting, still no luck

l0st.prophet said:
No erro, still got the ads. I've tried rebooting & rerooting, still no luck
Click to expand...
Click to collapse
What site/app are you going to so I can see if I get the ads.

the anti-ads actually tries to modify the current host file... which is not allowed in your state as far as i know
what you can do is replace it by pushin it to the right spot
but after reboot gone,but sure u know

Adfee is working for me, you can also add Droidwall.

@eddycyf, did you test adfree with apps? Since it aint working for prophet...
Sent from my HTC Incredible S using XDA Premium App

Mhm AdFree isnt working for me. The App states that everything is okay, and that my hosts file is up to date, but I see ads everywhere.
But I am kinda happy now, because i can use Titanium Backup

4X extremely slow after rooting/reboot

So, I followed the guide we all did here:
http://forum.xda-developers.com/showthread.php?t=1818502
And before someone asks: I have deleted the Backup app (IS11LG_SystemBackupTest.signed.apk) we had to install during rooting after the phone was rooted.
The phone then happily ran, rooted. SUpersu was installed/updated, the phones root check said it's all perfect, I was a happy camper. But today I had to reboot it. I can't say if it was the first reboot after rooting, sadly. The phone boots up, arrives at the lockscreen (some colorful defaultthing, before I get to see my GO Locker screen after login), and then stops being responsive, it basically at first feels like it's not reacting at all. Some things are responsive, strngely ... I get accurate sounds when touching the screen for instance. If I then wait, I eventually get to the SIM Unlock ... which is also totally unresponsive, it will maybe show two digits, then freezes up. Strangely, I could type the remaining digits and hit OK and the SIM would unlock ... but the screen no longer showed what I typed. I then arrive at GO locker, can unlock it (sluggish and slow again) and finally am properly logged in, but still totally sluggish and slow. Needles to say it's a pseudobrick that way, unusable.
What's going on and what could I check?

Please try the following:
alexp999 said:
REALLY SLOW AFTER ROOT?
Remove the "SystemBackupTest" app, if you haven't already.
On your phone, go to "Settings -> Developer options" and make sure "USB debugging" is TICKED
Connect your phone via USB to your computer.
Open a command prompt (may need admin privelages, right click, run as administrator)
Type without quotes "cd C:\o4xr" and press enter.
Type without quotes "adb shell rm /data/local.prop" and press enter.
Type without quotes "adb reboot" and press enter.
Click to expand...
Click to collapse

alexp999 said:
Please try the following:
Click to expand...
Click to collapse
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?

voon said:
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
Click to expand...
Click to collapse
I'm not entirely sure, I just know it gives us temp root for the rest of the root script to run.

Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS

voon said:
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
Click to expand...
Click to collapse
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.

alexp999 said:
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
Click to expand...
Click to collapse
I see, I might have done that ... good to know. Anyway, great that it works again, thanks again

laggy phone
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa

66aaaa said:
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
Click to expand...
Click to collapse
It looks like you have either plugged in more than one android device, or you have an android emulator (from the SDK I guess) running. Unplug all USB devices (except keyboard and mouse) and then try again. Good luck!

If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)

Dexxon said:
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Click to expand...
Click to collapse
I still don't understand and hope you do it...
THX for your help!

As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.

Dexxon said:
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Click to expand...
Click to collapse
This is the result...what to do know?
THX

The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.

Maybe you have an emulator running or Bluestacks installed... Uninstall Bluestacks...

I don't think that this is the case as the device shows up with a serial number in the "adb devices" list.
To be sure it is the correct phone you could compare the serial number shown in the list with the serial number of your phone (you might find this information in settings -> about phone).

Dexxon said:
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Click to expand...
Click to collapse
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX

66aaaa said:
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
Click to expand...
Click to collapse
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this

no one raised this question to confirm or did this info was provided anywhere
What version of ROM? ICS V10x? JB V20x? User could had used the wrong guide.
Best way out is to do a reflash and retry rooting if all fails.

Dexxon said:
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
Click to expand...
Click to collapse
I dont't have this Bluestacks emulatur, sure...
I have Superuser working properly on JB V20 stock ROM. The only thing it is very slow sometimes, Thats why I tried to make the process above...
I made the root few month ago...and rebooted many times since than...
Any idea what to do now?
THX

Droid 4 "root checker" from Verizon/Motorola?

I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?

So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2

The Magician Type 0 said:
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Has anyone try to format the entire phone, and then fast boot back?

Someone mentioned trying that, but I never heard the results.
Sent from my DROID4 using Tapatalk 2

Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk

Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2

jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
It's almost like Motorola has us all figured out! This and the unrootable Atrix HD... I think we just have to get better. I'm sure there is a root check somewhere in nvram or something
Sent from my Nexus 7 using Tapatalk 2

jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Whoa. I mean, it probably just writes a value somewhere we can't touch (yet?), but still.

repeated shell auto-granted permissions
fade_to_red said:
I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
Click to expand...
Click to collapse
highlandsun said:
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse

Morlok8k said:
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
Click to expand...
Click to collapse
After doing this, here is what i did in a terminal emulator:
Code:
su
mount -o remount,rw /system
chmod 644 /system/bin/dumpstate
i had to do the "644" instead of "a-x" because i kept getting an error message "Bad mode 10|"

When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.

No such file??
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.

No such file???
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.

It's /system/bin/dumpstate not /sys/bin/dumpstate

removing execute permissions does not do anything.

Should I or shouldn't I?
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"

supraket said:
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
Click to expand...
Click to collapse
I say.....
You should:
unlock tether, free apps, better phone, harder to replace if something goes wrong (worth it to me)
You shouldn't:
warranty risk, stock performance, easy replacement

je2854 said:
removing execute permissions does not do anything.
Click to expand...
Click to collapse
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?

intellitek said:
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
Click to expand...
Click to collapse
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes

je2854 said:
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
Click to expand...
Click to collapse
Okay, well, let's say, hypothetically-speaking, somebody was willing to experiment with this.
When exactly does this "rootchecker" run? I guess I'd need to rename/replace it before it runs, but after I've rooted. Or somehow before, although I believe that's currently not possible. I'll try and see if the bin is signed.. not sure how to check if it's actually verifying it on exec, though, without rooting.
EDIT: Nevermind, it looks like it's built into the boot and recovery .img files?

Removing System Apps

I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?

System is protected: you can't modify it while the phone is booted. You'll have to make a zip or whatever to delete it in recovery.

You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly

fkofilee said:
You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly
Click to expand...
Click to collapse
It seriously took you all day to root? What went wrong?

Did you try just freezing the app instead?

Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2

afilopou said:
Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So you can no longer go into ES explorer, mount root/system go to system > apps and delete whatever you want ?
Sent from my HTC Incredible S using Tapatalk 2

The recovery flashed but wouldnt boot , managed to get round it when i discovered POB with his superboot Thank god for the desire C
Then i realised that i couldnt flash anything because I manged to install 6.0.2.8 as a boot img, and 6.0.3.0 as a proper recovery.
Then i didnt have any files on the device to flash boohoo so i managed to get ADB sideload working through the AIO One Toolkit... And managed to flash AHRD finally getting a working device,
As you see Im a seasoned vet at these things but the HTC One has been the first device that has stumped me....
----------------------
The apps issue is not unkwown for HTC however they havent done this for a while.... Back with the G2 they did exactly the same thing and yes ive frozen them but there should be away to remove system apps for us through root.... But i cant remember how, Throwing it into ADB Shell and requesting SU along with a Remount works fine but still would like to remove the apps.
Im also looking for someone with a locked phone... (Sim Locked) i have a theory and it worked on the Desire C Anyone wanna help?

fkofilee said:
I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?
Click to expand...
Click to collapse
Delete the apps with titanium and power off the phone. Don't do a restart.

Already tried that ^_^

You need to flash a custom kernel with a modified ramdisk to disable system protection Without doing that you're like deleting an app on windows with deepfreeze on it

Is that the only solution?
There are so many bloated useless and intrusive (cr)apps on this phone it's unbelievable.

Other solution is boot in recovery and delete it there. Either thru adb while in recovery mode, flashable zip or through file manager(if you're using TWRP). Other than that nope

Hmmm I'm thinking adb through recovery here but how do I got about doing this?

fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");

The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk

the simple way is ROM CLEANER, but isn't available yet for the One.
cheers

fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>

Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful

ogdobber said:
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");
Click to expand...
Click to collapse
MacHackz said:
The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk
Click to expand...
Click to collapse
limx said:
the simple way is ROM CLEANER, but isn't available yet for the One.
cheers
Click to expand...
Click to collapse
Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
issak42 said:
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful
Click to expand...
Click to collapse
All Wonderful Ideas folks, however i had a go at this last night, it was a fricking nightmare even mounting ADB through recovery

adb advice

Hi,
Before I repair my phone and set it up again someone may be able to help me with this.
I was modifying the bootanimation and when I sent my new bootanimation to the phone and rebooted it gets stuck at the initial image and does not continue to boot up.
I have a copy of the stock bootanimation but using
Code:
adb push bootanimation.zip system/media/bootanimation.zip
gives the error that the system is read only.
However when I try
Code:
adb shell
su
adb remount
adb push bootanimation.zip system/media/bootanimation.zip
I get an error saying cannot find device, its like it does connect once I have remounted the system...
Any ideas? I can flash my FTF backup, its just going to be a pain to set everything back up
Thanks in advance

You could try running ADB as root and see if that helps. Other than that, you can just uncheck the "DATA" option in flashtool, that way you won't lose your data, thus you won't have to set everything up again. Worked for me last time I was messing around. Also, are you sure your bootanimation.zip is correct? The right folders, the settings in the text file right etc.

B1nny said:
You could try running ADB as root and see if that helps. Other than that, you can just uncheck the "DATA" option in flashtool, that way you won't lose your data, thus you won't have to set everything up again. Worked for me last time I was messing around. Also, are you sure your bootanimation.zip is correct? The right folders, the settings in the text file right etc.
Click to expand...
Click to collapse
yes I tried as root
Code:
adb shell
su
Yes, I forgot about excluding data...thanks.
I think the fact it froze at boot said the bootanimation was not correct, I am just playing around and will fix it later

gregbradley said:
yes I tried as root
Code:
adb shell
su
Yes, I forgot about excluding data...thanks.
I think the fact it froze at boot said the bootanimation was not correct, I am just playing around and will fix it later
Click to expand...
Click to collapse
I mean like this
Code:
adb root
Then it'll say something about rebooting the ADB service as root. Not sure if it works though, may be disabled in production builds.
You're welcome.
Ah good, well you should be fine.

B1nny said:
I mean like this
Code:
adb root
Then it'll say something about rebooting the ADB service as root. Not sure if it works though, may be disabled in production builds.
You're welcome.
Ah good, well you should be fine.
Click to expand...
Click to collapse
ok, I see what you mean, I will try it later but I flashing my FTF now, I thought I might as well as I only need to push my systeUI.apk back to get transparent notification background to get the phone as I want it.