Related
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...
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
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.
Taken from the inital forum thread
Posted in this forum so that it is correct forum
There is already a 'how to root' thread going, suggest you post there for help.
27/05/2011:
-------------------------
Modified the Iconia Tab GB's xml files to remove the need for portrait mode and change the name so not as to be confused with the original ginger break.
File attached.... signedGBIconiaTab1.20.apk (296.8 KB)
good luck
Older Details:
-------------------------
Root based on Chainfire's gingerbreak
Usual rules apply, if you break then best efforts but in the end it's was up to you to click 'root'
Thank you for your tools and time:
apkmanager; Daneshm90
apktool; brutall
Superuser honeycomb; j4mm3r
gingerbreak initial version ; Chainfire (Please review this for all the requirements)
The Android Exploid Crew for the exploit
Thanks you people for your help and input:
lou0611,dc13,maddler,nycbjr,seraphimserapis, it2steve, thor2002ro, rmgold & of course all of the team xda-developers
Special thanks to maddler for pointing us to the exploit
Chainfire for his apk version and work on gingerbreak
More Details
What we done to gain inital root:
turned on usb debugging & unknown sources
leave usb connected between tablet and pc
must have microsd card in the device (you may loose all the data on the card, read Chainfire thread)
split open chainfire's gingerbreak.apk with apktool
hex edited the gingerbrake.png change HONEY to HRI66 (see this link after reading the exploit)
added the updated su from xoom (thanks guys for coming to help me!)
recreated the apk with apktool
resigned with apkmanager
pushed to /data/local
launched apk install using oi file mananger entering the whole path to apk
set tablet in portrait mode and locked rotation
run the gingerbreak tool (it installs the root, updates SU and installed superuser.apk) waited about 4-5 tense minutes
confirmed root in terminal
install busybox
There are other method (which maybe easier) please check the 'How To Root An Acer Iconia A500' thread
Step by Step Root Guide [Long Method]
As with most instructions read completely before starting...
based off gingerbreak's instructions
usual rules apply, if you break then best efforts but in the end it's was up to you to click 'root'
Install Applications from market:
oi file manager
busybox installer (or Titaium Backup)
From your setting menu:
settings/applications
check Unknown Sources box
setting/Development
check USB Debugging
On the PC and Acer a500: Using ADB (I needed to download the usb driver from acer & sdk for adb):
(from the folder where the apk & adb is...)
connect your micro usb cable make sure usb debug comes up !
copy the apk to storage
On the Acer A500:
insert micro SD card if you have not done this yet
Rotate display to Portrait mode
Lock the screen its the little button under the VOL up/down (just incase)
Launch file manager
find and install <Gingerbreak>.apk (name will be different depending on version)
Install the application 'GingerBreak' (name will be different depending on version)
Return to apps menu
Find and launch 'Gingerbreak' [you must be in Portait or it will FC]
Select root device
Wait for it to reboot (2-10 mins, if you want monitor it with aLogcat or Logcat)
--- after reboot ---
Remove the rotate lock
Disconnect the usb cable
Uninstall Gingerbreak
Launch busybox app which will install busybox !
Install your root apps (my first are Titainum Backup and Cpu Master for me)
enjoy your Iconia a little bit more...
Regards and Best of Luck
Bugs? Troubleshooting?
Post any Bug for inital version
Issues
Hardcoded to HRI66
Features
Requires SD Card...
Why repost this method when the actual method is as simple as check debug, unknown sources, make sure sd is in slot, install app and run app?
Just asking. Thanks.
Reply
Probably for people like me that are new to rooting a device, detailed instructions can help others to understand and maximize success.
Placing the SD card in the slot was (for me) unclear per the original instructions, I just decided to try it since I was at a loss and it worked.
Details = Maximize Success & Minimize Failure
added new version of the Gingerbreak Mod, stops the FC if device is not portrait
monki-magic said:
added new version of the Gingerbreak Mod, stops the FC if device is not portrait
Click to expand...
Click to collapse
U.B.D.Man.....
a500 gingerbreak ??
I am trying to install gingerbreak 1.20. I am running android 3.2. it stays on the screen rooting this my taks a few minuter? I have let it run for hours and has not changed? Can anyone help me out
djbeach said:
I am trying to install gingerbreak 1.20. I am running android 3.2. it stays on the screen rooting this my taks a few minuter? I have let it run for hours and has not changed? Can anyone help me out
Click to expand...
Click to collapse
gingerbreak NOT WORKS on HC 3.2
HC 3.2
do you know of anyone coming out with a gingerbreak for honey comb 3.2?
djbeach said:
do you know of anyone coming out with a gingerbreak for honey comb 3.2?
Click to expand...
Click to collapse
I think no one for HC 3.2
You should revert to HC 3.0.1 and install a custom ROM HC 3.2 already rooted.
See other threads in this forum.
Hello xda
this is my first post as member in xda but i was in touch with everything here without an account before
i dont know if this is the right place to type my question so correct me if i am wrong
i wanted to know is there a way to record the screen in the recovery mode using adb or any other means cause i want to make recorded tutorials for friends o flashing roms , kernels etc.
Thanks in advance
Questions belong in the question & answer section
Edit - thread moved
Yes there is but not all kernels support adb in recovery so you will have to try
Make sure adb debugging is switched on in your phones settings & you have installed the Samsung USB drivers & maybe also the Android sdk
Although you can possibly capture video I can only find guides for KitKat so I don't know if our recoveries would support this but it uses adb shell commands - you can search for that
It maybe easier just taking screenshots try
http://forum.xda-developers.com/showthread.php?p=50029759
you can try android sgy but need a proper adbd