• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root It's time to unleash the beast!

I am running into the same problem as Gink with all the force closes but now my phone wont boot into recovery, it bypasses recovery and goes back to all the force closes... any ideas on how to get past the loop?
 
Robo1007 said:
I am running into the same problem as Gink with all the force closes but now my phone wont boot into recovery, it bypasses recovery and goes back to all the force closes... any ideas on how to get past the loop?
Click to expand...

Hi Robo. I had to boot into recovery manually, wipe data and dalvik cache and then flash velocity that I manually downloaded.
 
I am having a heck of a time with this rooted Ally. Not sure if it's the ROM or the device or what. Here's the deal:

After working with Trident above I was able to manually flash this ROM and it installed just fine. Problem was neither the phone key nor the home key worked. I wiped data and dalvik cache and rebooted and then both keys worked.

I then used Titanium to restore all my data and I got a ton of force closes. I decided to wipe again and install everything manually and I still got random force closes.

I'm trying to download the stock ROM from ROM Manager right now to see if I have problems with it but it keeps stopping in the middle of the download. I'm so frustrated.

I've even tried unrooting with Universal Androot but that doesn't wipe the ROM.

On top of all that I think the microUSB port on the phone is wonky.

I'm about ready to scream and go back to my crappy Eris until something better comes along.
 
I wish I could reboot into recovery but I can I tried the volume down+home+power and nothing any other way to boot into recovery would be greatly appreciated, I just get a force close when I power it up or when I try to go into recovery mode, it skips that and back to force closes. I was trying to use clockwork mod and have the same problem as you Gink. If i can get mine up and working I can try and help you too :-)
 
You reboot into recovery by turning the phone on by holding SEND MENU and END, I have no idea where all of you got this Volume down business
 
Use the ALLY RR tool or if your phone can be detected in ADB open command prompt and navigate to folder adb is [Ex. C:\android\sdk\tools] type
Code: 
 adb devices
if you see a device listed type
Code: 
 adb reboot-bootloader
which should boot the phone into fastboot. once in fastboot makesure you have one of drellisdee's recovery image 1.2.2 in the tools folder then in the command window type
Code: 
fastboot recovery recovery-RA_GNM_v1.2.2.img
this should boot you into recovery.

Use Ally RR tool before the command prompt. its easier. but if it cant be detected use the instructions i typed that use adb
 
Thanks death2all110 I am going through the command prompt and my phone is connected but it says device not connected any other help would be great thanks.
 
Robo1007 said:
Thanks death2all110 I am going through the command prompt and my phone is connected but it says device not connected any other help would be great thanks.
Click to expand...

Make sure if you use pdanet you do not have that running. Also make sure USB debugging is on

Goto Settings > Applications > Development > Check the box "USB debugging".
 
I can't access usb debugging, my phone powers up and constantly just force closes and won't do anything else until I remove the battery. It also won't boot into custom recovery, so if that's the problem I don't think I can't get any further... thanks for the help though I am open to anything at this point.
 
flick159 said:
Faster with an overclock? Or should I keep your included kernel?
Click to expand...

I would like to echo Flick's Question. Would it be prudent to use drellisdee's overclock kernel? Or is gridlock's kernel more beneficial to this Rom? Is there some way to marry gridlock's "Deadline" kernel with drellisdee's overclock tables? (Obviously, we as users can't do that ourselves).

TYIA!
 
Jace417 said:
What about swap on SD?
Click to expand...
It's already configured in V0.2..
SuperMerg said:
I would like to echo Flick's Question. Would it be prudent to use drellisdee's overclock kernel? Or is gridlock's kernel more beneficial to this Rom? Is there some way to marry gridlock's "Deadline" kernel with drellisdee's overclock tables? (Obviously, we as users can't do that ourselves).

TYIA!
Click to expand...

I guess that's really up to you. I personally didn't gain much of a performance increase with an overclocked kernel. See what works best for you I guess..

Also, an overclocked kernel with deadline enabled has already crossed my desk. You'll just have to wait I guess.
 
Installed 0.2 earlier today, first ROM flashing I've ever attempted with my Ally. Luckily no brick or puffs of smoke coming from my phone. I like it a lot so far.
 
Flashed clockwork (Although it took about 4 force closes before it worked). Cleared catch and data only. Did not decide to go with the android stock theme. Rebooted. Works like a charm, but I don't have any use for that Office App and a couple other unnecessary ones there. But nice job.
 
Robo1007 said:
send + menu + end
I also tried volume down + home + end to factory reset which does not work. I am stumped.
Click to expand...
From off point hold Volume Up, Home, Send once LG screen shows up let go of all three buttons immediately, it should load nandroid/clockwork mod recovery, assuming you have backups stored there go to clear cache and clear data and go to restore. If this helps lemme know.

*Edit 11:11 9/15/09 Also, when the phone reboots after restoring your backup you may have to manually choose reboot phone once or twice. I have to do it twice after every restore.
 
Cjohn8792 said:
From off point hold Volume Up, Home, Send once LG screen shows up let go of all three buttons immediately, it should load nandroid/clockwork mod recovery,
Click to expand...

I don't think that is correct, IIRC the keys for recovery are SEND+MENU+END.
 
I worked with robo for a few hours...he gets a bunch of force closes on boot up. will not boot recovery, usb debugging is off so adb is out of the question so cant fastboot either unless there is a key combo. factory restore by Vol Down + Home + End also does not work. Safe Mode still sees the FCs he is recieving when powered normally. LG mobile updater cant see his phone since debugging is off. same for Ally RR. any ideas folks? we literally tried everything in the book that we know of. i even snatched the official v8 update zip file and we tried seeing if the phone would load it on boot from stock recovery or something, but nothing. he is getting a refurb from verizon but its still bugging me. there has to be some sort of way. any ideas?
 
flick159 said:
I don't think that is correct, IIRC the keys for recovery are SEND+MENU+END.
Click to expand...
I just did it on my phone (vol up, Power, home,not sent[i was wrong on that part]), Send menu and end may be another variation or a factory reset, but it shouldn't put you in clockwordmod recovery I flash roms and do recoveries daily.
 
You must log in or register to reply here.
Back
Top Bottom