Database Users

Froyo ROM

Hi there,
I made a preliminary port of Froyo for the Liquid.
It needs the Donut radio rom, so it won't work on LiquidE.
You can test it on an Eclair radio, but usb and GSM/3G won't work.
IHMO, It works fine for daily use (I do use it daily.), current known bugs:
-Random lines appearing on the screen on refresh
-No wifi
-Wiping data kills radio
-No tethering
-Unsigned
Hint: to enable App2SD to all apps (by default, only some apps accept it), do
Code:
pm setInstallLocation 2
This will install all apps to SD, you can move them back to phone.
Please use http://code.google.com/p/acer-liquid-froyo/issues/list as bugtracker
(Donate link in my sig also works for my Liquiid's work )
Here's the downlink link:
http://code.google.com/p/acer-liquid-froyo/downloads/detail?name=Froyo.zip
Update:
Full: http://www.megaupload.com/?d=S9P799GO
Update: http://www.megaupload.com/?d=UPAF7YD8
-880MHz
-ramzswap
-USB OTG (seems not fully working)
-working iptables (droidwall works)
-usbnet (tethering kind of works)
-changed H264 resolution limit to 720p
To get tethering working, do echo 1 > /sys/class/usb_composite/rndis/enable
Then go in the appropriate menu and tick the usb tethering option.
The results are random, I don't know why yet. The released sources might help understanding that.

How can I enable apps2sd? Where have I to insert code? I'm a noob and don't understand, I need a step by step sequence.
Thanks.

akira.pwr said:
How can I enable apps2sd? Where have I to insert code? I'm a noob and don't understand, I need a step by step sequence.
Thanks.
Click to expand...
Click to collapse
Install connectbot
Launch it on the "local" protocol, do
su
(the su manager will ask for permission, allow it)
pm setInstallLocation 2
And it's done.

Ok, i'm doing it, it create a partition for apps?
After doing what you posted above, all apps go in my sd automatically?
Connectbot asked me a nickname, i put su, then un screen i writed pm setInstallLocation 2, then i saw the word "killed", is normal?
Superuser never asked me permissions.
Edit: retried more times and finally su requested permissions, i allowed but after insert the code, i read "killed"...

akira.pwr said:
Ok, i'm doing it, it create a partition for apps?
Click to expand...
Click to collapse
Apps go to the normal vfat partition
After doing what you posted above, all apps go in my sd automatically?
Click to expand...
Click to collapse
It should
Connectbot asked me a nickname, i put su, then un screen i writed pm setInstallLocation 2, then i saw the word "killed", is normal?
Superuser never asked me permissions.
Edit: retried more times and finally su requested permissions, i allowed but after insert the code, i read "killed"...
Click to expand...
Click to collapse
You must put su on the console, not as a nickname, the nickname doesn't mean anything.

sorry, but i'm not good, i don't understand how to do it, i put code, but when i put "2", i read proces denied. I give up...

akira.pwr said:
sorry, but i'm not good, i don't understand how to do it, i put code, but when i put "2", i read proces denied. I give up...
Click to expand...
Click to collapse
Giving up is always a lot easier than to keep on trying, \0/(stole the emote from phh lol)

rafyvitto said:
Giving up is always a lot easier than to keep on trying, \0/(stole the emote from phh lol)
Click to expand...
Click to collapse
But i'm a real noob, i tried and retried, but connectbot tells me action denied, any suggestion? When/where have i do su? It never ask me permission.

akira.pwr said:
But i'm a real noob, i tried and retried, but connectbot tells me action denied, any suggestion? When/where have i do su? It never ask me permission.
Click to expand...
Click to collapse
Weird..check on malex recovery to see if your device is rooted, without root you cant run superuser command's, but since your running phhfroyo it should come already rooted...

Problem with adb

Im tring to push a bootanimation.zip through adb but when i type adb remount is says operation failed
Can any help?

Did you try
adb kill-server
adb start-server
If that doesn't work try rebooting the phone.
If that doesn't fix it, Google it. I think that's the fix though.
Sent from my Burnt EVO via the XDA app.

I always use Pushboot. Its a simple batch file that does everything for you.
http://forum.xda-developers.com/showthread.php?t=701295

Hey thanks for the help...the pushboot killed my bootscreen but i got it back. Ill have to see what i can find out googleing it.....i know i have full root since im running the wireless tether and i get the # when i su.

trizzcuitt said:
Hey thanks for the help...the pushboot killed my bootscreen but i got it back. Ill have to see what i can find out googleing it.....i know i have full root since im running the wireless tether and i get the # when i su.
Click to expand...
Click to collapse
There's 2 pushboot files in the folder. Did you use Pushboot2?

Yup i used pushboot 2 since im rooted.....unless i read the instructions incorrectly.

Terminal Emiulater

Does anyone know if this works on HD2 Android:
http://www.android-devs.com/?p=33
I did all the steps and have downloaded the Terminal Emulater from the market, but when i type SU in it nothing happenes,Im trying to install Armenian Language pack on it.
BTW Im using Mdeejay Froyo Sense v.23 clean #15.

If you type in su, at first it looks exactly like this $ su.
After you hit the enter key, there should be only a hash #.
If there's only a hash, you're now working with root rights.

on the Devs web site its mentioned>(then wait for the superuser screen and press yes)
this phrase is confusing me since no Superuser screen is coming up.

hagba said:
on the Devs web site its mentioned>(then wait for the superuser screen and press yes)
this phrase is confusing me since no Superuser screen is coming up.
Click to expand...
Click to collapse
That is no problem because are phones are already rooted so you don't need any superuser. If your terminal look like I described it, just go on. I'm pretty sure your phone will give out errors if it doesn't work.

ok thanks I will give it a try as soon as get back from the work.

I see just $, No #.

Just try it, no matter what key it shows.

ok I will thanks again

desire z root : " su permission denied"

hello !
I'm new here and newbie in general. What is more, I'm french !
My desire z and I would like a root, but the uberroot method, using visionary, stops for me at the temroot step with this message : su permission denied
So i'd like to use the "clean" method ( http://forum.xda-developers.com/showthread.php?t=843014 )
but it's a bit difficult to understand why it doesn't work either !
Aaargh !

This works for just about any phone, give it a try...
http://forum.xda-developers.com/showthread.php?t=803682

Xanaki said:
This works for just about any phone, give it a try...
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
G2 is not one of them
try this
http://forum.xda-developers.com/showthread.php?t=801206
there are like 2 or 3 methods
pretty straight forward.

thanks, let's read that.

The most up-to-date method is in the Wiki - http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
However, you don't have the 1.72 ROM do you ? Because that needs a different procedure, due to HTC closing down some of the previously-exploited security loopholes - http://forum.xda-developers.com/showthread.php?t=905261

I carefully avoided installing the 1.72 !
I'm still "su permission denied" right now, and try to multisearch the website before asking more questions.

Well, it seems like I won't solve this by myself.
Thanks, Steviewevie
I installed sdk and usb drivers on my computer. Now, the question is : why does nothing happen when I use the cmd and write : " adb push su /sdcard/su " ?!!!!

I'm finally root and s-off, thanks to the "bad" visionary method !
What's the risk exactly with visionary ?

antoinoid said:
I installed sdk and usb drivers on my computer. Now, the question is : why does nothing happen when I use the cmd and write : " adb push su /sdcard/su " ?!!!!
Click to expand...
Click to collapse
Were you typing that command from your PC's command prompt ? What error message did you get ? Some people do an "adb shell" first and then run that adb, and that's not right because then you're running it on your phone and you'll get an error.
antoinoid said:
I'm finally root and s-off, thanks to the "bad" visionary method !
What's the risk exactly with visionary ?
Click to expand...
Click to collapse
Well, it seems to have a much higher chance of ending up stuck in a boot loop compared to other methods. But if you are back up and working again then it was obviously fine for you !

Visionary and Z4root ...or any root app is harmless. S-off is when you may find a few thin ice moments.... but that's what backups are for. Rom manager or titanum backup work just fine for me.
G2 CM6.1.1 (free)

ok. if I understand, as I'm alive, let's rock then !

so how did you get past permission denied?
damn, i am stuck at the permission denied phase in terminal emulator after typing su then hitting enter.
its seems like the person above figure it out and posted back to say they figured it out, but neglected to give any insight as to how they resolved the issue, save for:
"I'm finally root and s-off, thanks to the "bad" visionary method !
What's the risk exactly with visionary ?"
so anybody can help please?
i don't know what is meant by the "bad" visionary method. i'm pretty sure i used visionary r14 and the instructions found at:
the unlockr site for the how to get permanent root issue
i did seem to have s-off indicated when i held down the volume down button and the start button. i am never quite sure how to restart the phone when i get to that point, i think i just held the power button down, then an option for restart or shut down or something appeared and i toggled the volume switch down to that and pressed the start button and the phone restarted.
one other thing, when i go back into visionary and attempt to follow the last instructions:
"Open Visionary and Uncheck TempRoot on Boot and click Temproot Now.
12. Then select Attempt Perm Root Now and the phone should reboot.
13. Once the phone reboots, open Terminal Emulator on the phone and type su and hit enter. If you get the # symbol, you have permanent root access and S-OFF, enjoy!"
i don't know where i should leave the "set system r/w after root" item checked (which it is) the subheading for that option reads:
"system partiion will be mounted r/w after root process completes
by the way, I am using a fat32 formatted microsd card that is class 4 or so and 32gb that i got off walmart.com for about 100 bucks.
peace

I am new at this and I try VisonaryPlus and my phone keep hanging when I do temproot and I get permission denied. I try almost all the option I found online including the one user the Terminal Emulator and still cannot root. Can some please help.

AdAway fails on rooted stock

Anyone know why AdAway does not work on rooted stock B29? It works in systemless mode but not sure if that's the same thing. Anyone know how to fix this? Tried changing the path to data/data/hosts but then get another error. Saying a sibling is needed. Then it tells me to create something in recovery. Is this normal?

Here are the other errors after changing the path

macboss said:
Here are the other errors after changing the path
Click to expand...
Click to collapse
You have write protection enabled mate.
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE
This is how you disable it:
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
Source: http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/

Iam using this on Axon G
https://forum.xda-developers.com/showthread.php?t=1916098

great thank you. -- do you think I accidently enabled this for first time I tan TWRP? i dont recall but i might have selected keep system read only to keep getting system updates. is that was we are referring to here about this write protection?
nfsmw_gr said:
You have write protection enabled mate.
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE
This is how you disable it:
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
Source: http://androidforums.com/threads/zte-write-protection-for-zmax-and-other-zte-phones.1040331/
Click to expand...
Click to collapse

macboss said:
great thank you. -- do you think I accidently enabled this for first time I tan TWRP? i dont recall but i might have selected keep system read only to keep getting system updates. is that was we are referring to here about this write protection?
Click to expand...
Click to collapse
I'm not really sure actually, although I think ZTE phones have write protection enabled by default.
It's 50/50 really.

macboss said:
great thank you. -- do you think I accidently enabled this for first time I tan TWRP? i dont recall but i might have selected keep system read only to keep getting system updates. is that was we are referring to here about this write protection?
Click to expand...
Click to collapse
Write protection is enabled by default.

ok no big deal but i accidently ran this command through terminal on my mac and the computer rebooted. everything is fine it booted back normally but im not sure what just happened? what should i do?

OK so I'm trying to run this on my phone I'm terminal emulator and I'm getting this
what am i doing wrong?
macboss said:
ok no big deal but i accidently ran this command through terminal on my mac and the computer rebooted. everything is fine it booted back normally but im not sure what just happened? what should i do?
Click to expand...
Click to collapse

I tried a different emulator. All I'm getting is found. How should I do this?
macboss said:
ok no big deal but i accidently ran this command through terminal on my mac and the computer rebooted. everything is fine it booted back normally but im not sure what just happened? what should i do?
Click to expand...
Click to collapse

OK. i got it to work. Write protection is off on my Axon. It rebooted. I was create a symlink with adaway. Not having to use systemless mode. I think we did it. Thank you for your help.
Im just not sure about the mac thing though

macboss said:
I tried a different emulator. All I'm getting is found. How should I do this?
Click to expand...
Click to collapse
On that first terminal emulator you showed, type "su" and press enter. Then write "reboot disemmcwp" and tap enter. Your phone will reboot immediately.
That's how I did it.

ok. i just did it through terminal on the mac "./adb reboot disemmcwp" and that worked.
what do you think happened when I disabled write protection on my mac? I typed "sudo reboot disemmcwp" and the machine just rebooted...? Everything looks and works fun but im not sure if what I did was bad or not. Or if I need to turn it back on?? Note sure. But hey, adaway works!!

The checkbox in AdAway preferences to use systemless mode works well for me, without having to remove write protection.

macboss said:
ok. i just did it through terminal on the mac "./adb reboot disemmcwp" and that worked.
what do you think happened when I disabled write protection on my mac? I typed "sudo reboot disemmcwp" and the machine just rebooted...? Everything looks and works fun but im not sure if what I did was bad or not. Or if I need to turn it back on?? Note sure. But hey, adaway works!!
Click to expand...
Click to collapse
Lol it just rebooted and didn't disable anything. diseemcwp is ZTE specific.