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

Root Ally Pseudo-Brick

B

Broseph7

Newbie
So yesterday i rooted my LG Ally (2.2.2) via GingerBreak and i tried to get Velocity as well. Long story short i did a lot of stuff i read about and now my phone is rebooting as soon as it reaches the Verzion screen after the LG turn on. (Someone told me it was a pseudo-brick). If anyone has any info on how i can fix this that would be wonderful
 
Well do you have fastboot? Did you downgrade or do you have a old phone? If so theres no need to try lgnpst, but if you dont then its your only shot. I saw your posts in the root guide. If you went through with that you have fastboot and can manually flash the recovery with it and reflash velocity in a few minutes.
 
KingOfGreen said:
Well do you have fastboot? Did you downgrade or do you have a old phone? If so theres no need to try lgnpst, but if you dont then its your only shot. I saw your posts in the root guide. If you went through with that you have fastboot and can manually flash the recovery with it and reflash velocity in a few minutes.
Click to expand...

I'm not sure if i have fastboot or not, but i did go through with what i said in that post, and when i finally went to reboot my ally it started this turn on then off spasm thing.
 
Ok, well did it downgrade?? Go to a red yellow and whitescreen that said "lg downloading do not unplug" did you use lgnpst?? More info my friend!
 
KingOfGreen said:
Ok, well did it downgrade?? Go to a red yellow and whitescreen that said "lg downloading do not unplug" did you use lgnpst?? More info my friend!
Click to expand...

It didn't go to a red yellow and white screen. It was on the recovery screen then i wiped everything, got velocity, and rebooted. I don't know really what i was doing, i had someone giving me instructions on what to do.
 
Did you let it do the OTA updates all the way up to getting 2.2.1 or 2.2.2? If you flashed velocity 1.0 or 1.1 on top of 2.1 then you will have boot loops. Hopefully you made a nandroid before flashing.
 
xtcvapor said:
Did you let it do the OTA updates all the way up to getting 2.2.1 or 2.2.2? If you flashed velocity 1.0 or 1.1 on top of 2.1 then you will have boot loops. Hopefully you made a nandroid before flashing.
Click to expand...

OTA updates all the way to 2.2.2. I'm guessing i have boot loops (fits what my phone is doing). I do remember seeing something about nandroid
 
Well if you took a bunch of ota updates then you have fastboot. If you downgraded then you probably have adb and fastboot set up on your pc. But this will ONLY work if you downgraded and got fastboot. If after trying the reboot bootloader command you just reboot. You gotta use lgnpst

open windows command prompt type
Code: 
cd c:\froyo\androidsdk\tools
this is only the directory of you downloaded froyo.zip from the 2.2 root guide. If you didnt find adb.exe and fastboot in the android sdk directory and put that directory after the cd command.

Once the active line shows the directory where adb and fastboot are enter
Code: 
adb start-server
then while the phone is bootlooping plug it in and enter
Code: 
adb reboot bootloader
the phone will reboot into fastboot, blue screen. This may take a few tried to catch it in the right spot, you can usually do it towards the end of the red vzw splash

If it just reboots then you didnt downgrade or you updated wuth lgmu, but it sounds like you DO have fastboot.

Now download the latest amonra recovery and move it to the same directory as fastboot and adb. I would rename it recovery.img to save you some typing in command but if not you would just use whatever its named. Now enter
Code: 
fastboot flash recovery recovery.img
to flash the recovery OR
Code: 
fastboot boot recovery.img
to boot straight into recovery and flash velocity from there which will then flash amonra recovery to the phone.
 
KingOfGreen said:
Well if you took a bunch of ota updates then you have fastboot. If you downgraded then you probably have adb and fastboot set up on your pc. But this will ONLY work if you downgraded and got fastboot. If after trying the reboot bootloader command you just reboot. You gotta use lgnpst

open windows command prompt type
Code: 
cd c:\froyo\androidsdk\tools
this is only the directory of you downloaded froyo.zip from the 2.2 root guide. If you didnt find adb.exe and fastboot in the android sdk directory and put that directory after the cd command.

Once the active line shows the directory where adb and fastboot are enter
Code: 
adb start-server
then while the phone is bootlooping plug it in and enter
Code: 
adb reboot bootloader
the phone will reboot into fastboot, blue screen. This may take a few tried to catch it in the right spot, you can usually do it towards the end of the red vzw splash

If it just reboots then you didnt downgrade or you updated wuth lgmu, but it sounds like you DO have fastboot.

Now download the latest amonra recovery and move it to the same directory as fastboot and adb. I would rename it recovery.img to save you some typing in command but if not you would just use whatever its named. Now enter
Code: 
fastboot flash recovery recovery.img
to flash the recovery OR
Code: 
fastboot boot recovery.img
to boot straight into recovery and flash velocity from there which will then flash amonra recovery to the phone.
Click to expand...

I plug in the phone and type adb reboto bootloader and it tells me "error: device not found"
 
Did you have it plugged into the pc with usb debugging on before?? Do you have the drivers installed? the phone boots up, first thing you see is the lg bootsplash, then the red vzw one (or velocity one) towards the end of that is when the phone and pc can interface, you have to issue it then.

If you get the error press the up arrow to bring to command back and hit enter again to try to catch it.
 
USB debugging was enabled when my phone was plugged in before, not sure if the drivers are installed. Is there a way i can verify their installation?
 
Got to control panel>add/remove programs and they should be listed there. If you downloaded the froyo guide you can run drivers.bat if you dont see them there.

And if they are there you may want to uninstall, reinstall and reboot the pc.
 
Hmmmm give me a minute and ill get you a link.
I think this is the adb drivers, ill link to the usb drivers too

http://db.tt/5563YCd
http://db.tt/Ja3hDka


Now the fastboot drivers will be tricky, if you get the phone into fastboot ill help you with that. Just dont wanna get into that without knowing you have fastboot. Also you COULD just go to the 2.2 root guide download the froyo LITE zip and follow thos instructions. Itll have the sdk and correct fastboot drivers. Also the original guide is where i got these drivers.
 
First reinstall the drivers and reboot the pc, then try to get into fastboot.

Option A, i think would be easiest. . ..
If you get the blue screen, use the froyoLITE zip from the 2.2 root guide,this will flash velocity 1.0 or stock 2.2.1, if you want velocity 1.1 you will have to flash in recovery manually. The benefit to this, is the fastboot drivers are in that package and itll help you set them up. All directions are in the 2.2 root guide. Downside is the 200mb download.

Option B, pretty much the same but you will need to get the fastboot drivers and recovery.img yourself (i can help).. . . .
manually flash recovery as i stated above and then flash velocity 1.1, you will have some trouble with the fastboot drivers which i have and could help you get set up. This way WOULD be easiest if you had previously set up fastboot and would be the way to go in the future. If you decide to go this route, PM me and ill help you get the files without downloading the big zips from the root guide.

Option C, if you dont have fastboot. . .
if you just reboot, then no fastboot and your best bet and as far as i know only chance is LGNPST which usually works as far as i know.
 
KingOfGreen said:
open windows command prompt type
Code: 
cd c:\froyo\androidsdk\tools
this is only the directory of you downloaded froyo.zip from the 2.2 root guide. If you didnt find adb.exe and fastboot in the android sdk directory and put that directory after the cd command.

Once the active line shows the directory where adb and fastboot are enter
Code: 
adb start-server
then while the phone is bootlooping plug it in and enter
Code: 
adb reboot bootloader
the phone will reboot into fastboot, blue screen. This may take a few tried to catch it in the right spot, you can usually do it towards the end of the red vzw splash
Click to expand...

If you get into a blue screen you have fastboot, if you just reboot, no fastboot and you gotta try LGNPST.
 
What screens are you seeing in the bootloop? If you cant get this to work, lgnpst cant see the phone either. You can also try holding end+menu+send to get into recovery, the stock recovery will displat an error/warning triangle and a android. If you hit home at the right time itll bring up the stock recovery menu and you can issue the reboot bootloader command there. Its a bitch to hit home at the right time, gotta hit it a few times and hope you catch it, you miss it or do it too many times you gotta pull the battery and try again.
 
Try getting into recovery with end+menu+send youll either get fastboot screen, stock recovery, or amonra racovery. Fastboot would be sweet, i think you said the amonra recovery isnt there but you can work with the stock recovery, check my edited post above.
 
You must log in or register to reply here.
Back
Top Bottom