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

Root Ally Pseudo-Brick

I tried that earlier and i got nothing, but i just tried it and it decided to work. The android system recovery screen is up with the triangle and the droid and a buncha options
 
It still says device not found.. and everytime i plug my phone in, a window pops up saying windows was unable to install LG USB Mobile Modem
 
But i did install the drivers (the links you gave me) unless those were different drivers. I tried to get it to install the driver it was notifying me about but it says it can't find one
 
I thought those drivers were iffy with vista? Because vista sucks. You would have a better chance on linux or mac. Just dont use clockwork mod recovery for the ally or rom manager. It will suck.
 
Use the windows 7 one and you should be able to do it pretty easily. You can use rom manager its just best to flash alternate recovery. Clockwork and the ally dont mix so well from my understanding. But using rom manager on a stock rom leaves you prone to your recovery getting replaced with the stock one and shit like this happening. Youve got everythng you need so using the lite zips on windows 7 should get ya set up right.
 
I tried it again on windows 7, phone was in the recovery screen. I got another error at the command prompt though. "error: closed". Do you think i could take the phone into verizon and let them check it out?
 
Did you try it while it was bootlooping? Or just in the stock recovery? Try it while it bootloops first, then when in the stock recovery try
Code: 
adb shell
before trying to reboot into fastboot. if it shows a "$" then you may need to enter
Code: 
su
if it shows a "#" then you can just try the reboot command.

I mean you CAN take it into verizon, as long as it is showing the verizon splash screen and not velocity. Technically your warranty is void and doing so is fraud of some sort, but the vzw reps wont probably wont know that and you could play dumb and get a refurb. But first try the above. I think itll work.
 
I tried it at both. In the bootlooping it said device couldn't be found, and in stock recovery it said closed. I'm about to go to the Verizon store in a few minutes so I might just go buy a new phone
 
KingOfGreen said:
Did you try it while it was bootlooping? Or just in the stock recovery? Try it while it bootloops first, then when in the stock recovery try
Code: 
adb shell
before trying to reboot into fastboot. if it shows a "$" then you may need to enter
Code: 
su
if it shows a "#" then you can just try the reboot command.

I mean you CAN take it into verizon, as long as it is showing the verizon splash screen and not velocity. Technically your warranty is void and doing so is fraud of some sort, but the vzw reps wont probably wont know that and you could play dumb and get a refurb. But first try the above. I think itll work.
Click to expand...

I got the "#" and tried the reboot command and it said
Code: 
/sbin/sh: adb: not found
 
It would just be
Code: 
reboot bootloader
after you got the "#" because you are now in a shell w/ the phone. My bad i should have caught that.
 
thanks d2a! i had no idea.
He should still be able to get it while it bootloops. But im guessing by now he got it figured out or took it back to verizon.
 
If its boot-looping at the very beginning of the VZW animation, or before the animation starts, then no because the adbd (android debugging bridge daemon) (adb daemon) service isn't running yet.
 
I did go to Verizon, and got the Droid Incredible 2. Still have the Ally, still bootlooping. I actually need to get rid of it, and get a Verizon basic non-smartphone for the new line i added. If someone wants to trade or something
 
You must log in or register to reply here.
Back
Top Bottom