Database Users

What ROM ?

Hello,
I've a liquid with 2.00016 ROM
What is for you the best ROM for the Liquid ?
For best I mean faster and that work well without crash.
Thanks a lot

Well, if it comes to stability, I would recommend ACR 1.5.1
But now I'm using eVil 1.8.1 and I love it

Piter1225 said:
Well, if it comes to stability, I would recommend ACR 1.5.1
But now I'm using eVil 1.8.1 and I love it
Click to expand...
Click to collapse
ACR 1.5.1, is pretty stable..unless you are really into the liquid tweaking modding, i don't recommend upgrading to 2.1 leaked version..
i had lots of random reboots, phone getting stuck on standby issues and reverted back to ACR 1.5.1, really happy with it.
Flash the ACR on 2.000.16 and you have a pretty satisfied liquid with you..

a question
hello guys.
there's something I don't understand in the rooting process.
when I go to superboot and double click install-superboot-windows.bat
all I get is <waiting for device>
it stays there for hours then nothing happens!!
I was trying to update to 2.1
I downloaded the acer download tool 3.10
then the 2.1 firmware BIN file.. all that was done successfully.
then I went to the third step where I have to do the superboot i got stuck there..
can someone help me please?

Thanks ..
I've see that now there is LCR 1.2
Maybe I trial this rom ...
Thanks

Ninlour said:
hello guys.
there's something I don't understand in the rooting process.
when I go to superboot and double click install-superboot-windows.bat
all I get is <waiting for device>
it stays there for hours then nothing happens!!
I was trying to update to 2.1
I downloaded the acer download tool 3.10
then the 2.1 firmware BIN file.. all that was done successfully.
then I went to the third step where I have to do the superboot i got stuck there..
can someone help me please?
Click to expand...
Click to collapse
Type cmd: adb reboot bootloader
after run .bat file.

anzo said:
Type cmd: adb reboot bootloader
after run .bat file.
Click to expand...
Click to collapse
even if the characters don't show?
should I press enter after typing?

Ninlour said:
even if the characters don't show?
should I press enter after typing?
Click to expand...
Click to collapse
PC/Andriod-sdk-windows/tools/ run cmd type "adb reboot bootloader" if liquid change bootloader after run .bat file PC.

anzo said:
PC/Andriod-sdk-windows/tools/ run cmd type "adb reboot bootloader" if liquid change bootloader after run .bat file PC.
Click to expand...
Click to collapse
sorry forgive me for being such a noob.. so i understand that it requires me to download android sdk tools software?
it wasn't mentioned in the instructions for rooting though.

Ninlour said:
sorry forgive me for being such a noob.. so i understand that it requires me to download android sdk tools software?
it wasn't mentioned in the instructions for rooting though.
Click to expand...
Click to collapse
You have to make sure you are in the bootloader mode in order to flash the recovery and boot roms.
For that you can enable debugging on your liquid and then navigate to the sdk directory as mentioned earlier for running the adb command.
Also make sure that you have the drivers installed.

umair9001 said:
You have to make sure you are in the bootloader mode in order to flash the recovery and boot roms.
For that you can enable debugging on your liquid and then navigate to the sdk directory as mentioned earlier for running the adb command.
Also make sure that you have the drivers installed.
Click to expand...
Click to collapse
ok let me put everything from the beginning because it's still not working and you guys tell me where did I do wrong.
I got the acer brand new. opened the box. used 1.6 android, and didn't like it.
so after surfing the web i was able to know that my rom was
ROM 1.001.05 AAP CSL.
so I used alternate superboot to root it the one provided in this pagehere
I followed the steps just like it was described but i have no small idea that it went successfully because I didn't see any confirmation of any kind that I had root.
well I don't know if there's any anyway
then I followed these steps here
I downloaded the drivers on my desktop.
then flash tools, and the 2.1 firmware liquidE "whatever it was provided in the link."
then I downloaded superboot and unzipped it.
I was able to find install-superboot-windows.bat I would get a window says flashing superboot
<waiting for device>..
and stays like that forever.
so I decided to take an action by turning off the device and tried to do the following:
removed battery
unplugged cable
re plug cable
put battery back
press camera+power then nothing happened I just got a regular boot.
so I did it one more time and this time I did
volume down+camera+power
still nothing happened ..normal boot.
I tried the same thing but volume up.. still nothing. so i gave up.
but after contacting you guys.
I downloaded SDK tools for windows
I opened android SDK windows folder then tools folder but I can't find any CMD file that I can run and type my commend in it.
I honestly don't know what this Android SDK is for.
so I got stuck with a liquid E rom without doing any recovery or anything.
I don't even know how to get the bootloader mode to run.
what should I do?
no I have ROM LiquidE.0.004.01 EMEA GEN1
it seems to run fine though..
but I don't know if there's anything missing
why am i not able to do the recovery step and flash system.img ??

Getting into bootloader mode when liquidE rom installed
Do this and you will get into bootloader mode when liquidE bin installed:
1. turn off your phone (and unplug usb if plugged)
2. press "camera + volume up +power" together at the same time (phone will vibrate 2 times) then release buttons
3. take the battery out and put it back (don't touch any buttons on the phone)
4. connect the usb from your computer to acer liquid and you will see the acer logo and then bootloader will pop up

mhmm
what he said: I always run into issues when someone says run superboot as the next step then install lickon's recovery. I skip the install lickon's recovery b/c it never seems to work for me. I just go to recovery mode after superboot is installed and after I put the .zip rom file on root of sd. Once in recovery i wipe, wipe, install from any .zip and i'm good to go. I probably lose out on being able to hard reset to the rom i installed but i have no idea what lickon is for and no search came up with a decent answer. I'll keep reading.
BTW, i ditched the acer neotouch for s100 and couldn't be happier.

Well finally I figured it out.
You dont actually have to press any hard button combinations because that actually never worked out.
So here is what I did.
I just enabled the debugging mode by going to setting>application>development>enable debugging
By doing that superboot worked just fine
Now I have Evil 1.9
To be honest non of the 2.1 leaked seems to function completely. . But still trying

don't forget to restart
After installing 2.1 and playing around with it for a bit, don't forget to restart it. Its horribly laggy the first go around, but after you reboot it (once you sync and all that), its pretty quick (though nowhere near 1.6). I have an issue with evilD's 1.9 where after having downloaded like 20 apps from market, when i open an app from the launcher, sometime when closing the app i get a black empty unresponsive launcher pop up instead of the homescreen and i have to click home button. (high-five for the run-on sentence... yeahhhh). Probably b/c of the DL rampage i went on.
Either way, i'm happy with it so far. I wish there was a 1.6 version with voice input in all text fields or a 1ghz 2.1 but that will come once liquid e is released officially.

Having problem rooting nexus s

I'm following the [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9023 and i9020A) but I get stuck after step 13, I don't see any "android bootloader interface" so I can't select it.
Also the icon for "Android 1.0" on my device manager window has a yellow/black exclamation mark. Though I should mention that.
What do I do now?

Try This
I believe the yellow exclamation mark is to alert you that the driver is not working/installed properly. After clicking "Let me pick...", do you see a button marked "Have Disk..."? If so, click that, click browse and go to where you downloaded the google usb drivers and select "android_winusb.inf".
Hope that helps.

i've had the same issue when rooting my ns, what you need is "pdanet for android"
sorry im a newb, cant give you the url..
just google ,the first one is it. installing this fixes the driver problem, though this software is for something else.

ikika87 said:
I believe the yellow exclamation mark is to alert you that the driver is not working/installed properly. After clicking "Let me pick...", do you see a button marked "Have Disk..."? If so, click that, click browse and go to where you downloaded the google usb drivers and select "android_winusb.inf".
Hope that helps.
Click to expand...
Click to collapse
Thank you! This work, but now I'm stuck on "Part 4: Root" step 6. Every time I type in adb push su-2.3.6.1-ef-signed.zip /sdcard/su-2.3.6.1-ef-signed.zip it says device not found.
Thanks for all the help so far.

Allright I got it to work somehow. I got it stuck after when I would go to recovery and I'd see the android + exclamation mark. Turns out you lose the clockwork mod when you reboot?
How do I keep it clockwork mod? I tried the cmd commands, but it returns
device not found
for example if I type adb shell, it returns device not found.

I attempted to root my friends Nexus S this weekend and I had no idea what i was setting myself up for! This is crazy how much work has to be done to root this damn phone lol. I have an epic and its literally a few seconds and you are done.
I got stuck after it asked me to download a special java package and i did but it still didnt recognize it.

Ingeminiac said:
Allright I got it to work somehow. I got it stuck after when I would go to recovery and I'd see the android + exclamation mark. Turns out you lose the clockwork mod when you reboot?
How do I keep it clockwork mod? I tried the cmd commands, but it returns
device not found
for example if I type adb shell, it returns device not found.
Click to expand...
Click to collapse
if you are on stock , then yes you will lose the recovery.
follow the instructions i posted here.
http://forum.xda-developers.com/showpost.php?p=14076068&postcount=6
keep in mind you have to rename the update-recovery.sh cause on rebooting this file will cause the stock recovery to be flashed back.

goblue30093 said:
I attempted to root my friends Nexus S this weekend and I had no idea what i was setting myself up for! This is crazy how much work has to be done to root this damn phone lol. I have an epic and its literally a few seconds and you are done.
I got stuck after it asked me to download a special java package and i did but it still didnt recognize it.
Click to expand...
Click to collapse
it is nopt as hard as it looks like. i believe this guide is quite useless and complicates stuff. an example is that it says after flashing recovery. you should use adb to push ur su file to the sdcard. why complicate stuff when u could just from recovery , mount the sdcard and drag the file there with ur mouse!

Ingeminiac said:
I'm following the [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9023 and i9020A) but I get stuck after step 13, I don't see any "android bootloader interface" so I can't select it.
Also the icon for "Android 1.0" on my device manager window has a yellow/black exclamation mark. Though I should mention that.
What do I do now?
Click to expand...
Click to collapse
Forget this crap go to Nexus S Android Dev forum a new one click root method has been applied for 2.3.4. See me there
Sent from my Nexus S 4G using XDA App

[Q] Help I botched It!!!

Hi there i have a rotted kindle fire with burrito root.
I rooted it yesterday and everything was fine, then i turned it off and back on later it worked fine.
the next day it hangs on the boot logo (it is animated no triangle)
adb recognizes it yet i cant access adb root, remount etc Permission denied.
I cant install TWRP
What i wanted to do was go to the /sdcard directory and push the update.zip there. but i cant because it read-only. How do i change any of these? Ive read 6 other posts on possible fixes none of which work.

Have you tried pressing the power button for 20 seconds and then restarting it?

nope
Yes i did that does not help.
adb says it cannot be root in production builds. I looked up how to do it but its either vague or makes no sense or does not work. why is it a production buold? it didnt do that when i rooted my fire in the first place so why is it doing it now?

What i believed happened is that when i went to past the andoid market's vending.apk into the system/app folder it deleted all of the things in the folder and nothing worked not even the GUI. I hard reset and then i got stuck at the logo. Dont know if that would clarify anything

that clariefys a lot - if you messed up your /system this should help you:
http://forum.xda-developers.com/showthread.php?t=1414832
then you should be able to install twrp
hopefully ...

Thanks but that did not help. It isnt recognized in adb like that.

Can you get into recovery? When you boot it up do you see FireFireFire at all?

No it says KindeFire and its animated.

sorry but i think you'll need a factory cable to get in fastboot mode
you'r not the first one ...

I have a micro usb and it works to connect (well until i followed that link and followed the instructions )

melmantheman said:
No it says KindeFire and its animated.
Click to expand...
Click to collapse
Hi,
Did you have a look at this too:
http://forum.xda-developers.com/showthread.php?t=1356257
I had quite the same issue with mine ...Device was not recognizable at all on Windows (unknown drivers)
I used this guide and it just worked like a charm.
regards
mjay

melmantheman said:
I have a micro usb and it works to connect (well until i followed that link and followed the instructions )
Click to expand...
Click to collapse
i think you did'nt understand what a factory cable is
it's a special cable which forces the kf in fastboot mode
you can build or buy one
make a search for "factory cable" and you'll know ...

http://forum.xda-developers.com/showpost.php?p=21151545&postcount=118

Can't install clockwork recovery

Hello!
I'm trying to install clockwork recovery with the fastboot method.
But when i use this method: http://forum.xda-developers.com/showthread.php?t=1319257
The phone just freeze at the ZTE (white background) logo.
And the windows command prompt are telling me: < waiting for device >
I need to remove the battery to start it again.
Have also tried;
z4root + Rom Manager
OneClickRecovery (telling me exploit cannot be used trying su and launch the file explorer)
It's a Gen 2 phone with Android 2.3+
If nothing works cant i use Linux?
Big thanx! for everything.

You need to install drivers for the phone if you use Windows. Link is in the thread.
It'll work on Linux or Mac without any drivers, but you might need to be root if you don't set it up right.

wbaw said:
You need to install drivers for the phone if you use Windows. Link is in the thread.
It'll work on Linux or Mac without any drivers, but you might need to be root if you don't set it up right.
Click to expand...
Click to collapse
Yes, i have done that. I did try the drivers in the thread and those i did get with the phone (autorun). And Windows tells me all drivers work correct.
Thnx for the answer.

When you're in the bootloader, check device manager if it shows Android with a yellow exclamation.

Rapier07 said:
When you're in the bootloader, check device manager if it shows Android with a yellow exclamation.
Click to expand...
Click to collapse
Yes, when i do the
Code:
adb reboot bootloader
and the phone shutsdown and showing ZTE (white background) then device manager starts showing "android" with a yellow "!" behind it.
But it ain't there until i do that? And Win 7 shows a "can't find drive" i did try point it to the ZTE 3G instalation folder with the amd64 drives. But nothing happens.
Now i have tryed on my girlfriends laptop also. It also got the Windows 7 64bit. But it does not work there either. Same problem.
How long should it take until "Android" logo shows on the phone?
Thanx for all the help!

UPDATE
UPDATE!
I think i solved it.
Used: SuperOneClick
And when it started to root and downloaded all drivers i did the original ADB:
[GUIDE] How to root your ZTE Android device
And it started to install Clockwork Recovery. SuperOneClick shutdown (error) and the phone booted. And now i can boot into Clockwork Recovery with VOL-.
But Rom Manager does not find it and can't install it.
So i'm going for the traditional boot with VOL- and hit the ROM from there.
Big thanx for the help!

Can't root without recovery, can't install recovery without root

I've been going through quite a lot of headache just trying to root this old LG G2 (D801) of mine, and would really appreciate some help. First, I tried to go through the normal steps of ioroot. After having to perform some unknown button combination to access the stock recovery (which I could only do with random, continuous button mashing), I am greeted with an error about adb being outdated whenever I try to sideload the "datroot.zip" file. I eventually realized that, somehow, after trying to (and failing to) sideload adb is temporarily changed from 1.0.32 (as required) to 1.0.31, as I can see when I simply enter "adb" in the command prompt before and after attempting to sideload. Some Googling later eventually reveals that renaming adb.exe to something else (in this case I changed it to androiddb) fixes the problem, as it indeed does for that. I then, however, get it to sideload to what seems to be between 50-60% before it fails and the phone spits out the following:
"E: failed to verify whole-file signature
E: signature verification failed
Installation aborted"
On the command prompt's side, it says this at the same time:
"loading: 'datroot.zip' adb server is out of date. killing...
* daemon started successfully *
Total xfew: 1.22x"
After every attempt of Googling around for this, everyone seems to say that I need to use TWRP or CWM instead of the broken stock recovery, and from there just install the file as I've done before on different devices. The problem here is that, to my understanding, I actually need root in order to install a custom recovery, is that not the case? If so, how can I root in this situation if I can't install a recovery, which in turn requires me to root beforehand? If I could get any sort of guidance and hopefully regained sleep, I'd be greatly appreciative, as I'm sure you guys know far more about this kind of stuff than I do. Thank you.

try LG one click root .
Install latest adb drivers, enable USB debugging . connect USB to computer ,put the device on mtp interface. now click on the start button on LG one click root . If the tool stuck at 90% on computer (0% on firmware update screen on mobile) and if this happen couple of times just restart the phone by long pressing the power button while it's connected to the computer . It should then show 100% . After reboot look for supersu in device menu . It should get installed on your phone. If u cant then try the same procedure again. Use root checker to confirm .
And AUTOREC to install TWRP

rajkatiyar07 said:
try LG one click root .
Install latest adb drivers, enable USB debugging . connect USB to computer ,put the device on mtp interface. now click on the start button on LG one click root . If the tool stuck at 90% on computer (0% on firmware update screen on mobile) and if this happen couple of times just restart the phone by long pressing the power button while it's connected to the computer . It should then show 100% . After reboot look for supersu in device menu . It should get installed on your phone. If u cant then try the same procedure again. Use root checker to confirm .
And AUTOREC to install TWRP
Click to expand...
Click to collapse
I can't believe this actually worked! Thank you so much!

yami759 said:
I can't believe this actually worked! Thank you so much!
Click to expand...
Click to collapse
There is a thanks button in the bottom of my post too

rajkatiyar07 said:
There is a thanks button in the bottom of my post too
Click to expand...
Click to collapse
Done