- 02-11-2011, 06:29 PM #51
- 02-11-2011, 09:25 PM #52
- 02-11-2011, 09:27 PM #53
- 02-12-2011, 02:38 PM #54
- 02-13-2011, 12:10 AM #55
- 02-21-2011, 03:48 AM #56
I wish I know how you all are able to do an adb shell connection..
I have yet to get my phone connected as of yet..
I have even disabled and enabled the 4 driver's that are used with the phone
(GPS,MODEM,COMPOSITE & the SERIAL driver)..
Im sure the serial driver is what is needed (as I dident pay attention to witch driver was used when doing the ROOT earlier this month..
I know all files are up to date as I was in adb shell 2 days ago and had no issue's..
Must be an issue with the "Debuging" driver on the phone side is not activated..
- 02-21-2011, 04:06 AM #57
Do you have USB debugging enabled? Sometimes in various resets and restores it gets disabled and you don't realize it.
The particular interface you care about is listed under "ADB Interface" for devmgmt.msc
It'll say Android Sooner Single ADB Interface.
If you don't see that when you connect your phone, then something is not configured correctly, likely either the drivers or the USB debugging setting.
- 02-21-2011, 02:04 PM #58
I have flashed and re-flashed stock Nand's as well as some backups I have made where I know USB Debuging was on..
Still a no go...
When ever I plug in my phone to the PC while in recovery the USB is stated to be using "LGE Android Platform USB Modem #2"..
Also SuperOneClick just hangs at "waiting for device" promp..
I just do not get it..
Plus if its any help Im running on Windows 7 (x86) with a LG Optimus V
- 02-21-2011, 02:35 PM #59
- 02-21-2011, 02:58 PM #60
Im in a constant recovery loop and Im not able to access the main OS to change such settings..
I have tryed all my Nand flashes and even used a stock Nand flash thats found here for my Opti V:STOCK OPTI V Nand BACKUP
& within "Mounts" on the recovery menu the only thing thats mounted seems to be the "/cache"...
Im rather new to this so bear with me if you could please..
In short though thats my main issue as the phone doesn't seem to have the debugging mode enabled..
Thought that setting would be set within the Nand backup witch I know the first backup I had done had the USB debugging mode on..
Any further help would be greatly appreciated..
- 02-21-2011, 04:26 PM #61
If you are in a boot loop, you need to fix that first.
Your phone isn't going to be recognized as an adb-capable device until it gets into Recovery or into Android.
Try looking in the Unbrick some forms of brick thread if you haven't already.
- 03-04-2011, 06:39 PM #62
- 03-14-2011, 09:53 PM #63
well, I like a dumbass went ahead and forgot that I had flashed back to recovery-RA-GNM-thunderc-s-1.1.0.img from clockwork recovery, I was trying to fix my inability to update my prl by doing a ##786# and made a big mess of things. I followed the unbricking thread, rerooted, then got everything back to VD and back on thunderom, but now I have no data, and hands free activation will not work. Do I need to unroot once more and do the ##rtn# again? I am so mad at myself right now!!! Had to go messing around with things when everything was working fine except for prl update.
I will be updating this in a second with the exact steps I took
edit: I've made a big F'ing mess of this. I used the unroot thread, went back to stock recovery and software, did ##RTN# then it just kept trying to reboot all the time. I am hoping that it was because of the VD baseband with the V9 software, so I tried to force flash using kp500 to V9 baseband....which stopped the rebooting but I still wasn't able to activate data. I just thought about it and I did not try to do the ##rtn# again after I got to the point where it wasn't rebooting every 10 seconds, so I am going back through this all again, and going to force flash V9 once I can get it to not reboot long enough to run the tool, then I will try ##72786# as recommended by a sprint employee in the chat, then hopefully it will friggen activate.
I love gadgets but god do I hate when they malfunction due to my stupidity!!!
edit: I force flashed back to V9, then just let it sit for a few. Data seems to work again! Moral of the story is EVERYONE PAY ATTENTION TO WHAT YOU'RE DOING!!!
- 03-14-2011, 10:37 PM #64
Based on what ##SCRTN# says it is supposed to do, it should clear out your NVRAM like ##786# (which adds factory reset of /cache /data)
I didn't actually try it as I don't have the time to deal with any issues that might arise from my own stupidity right now
So you had stock V9 recovery and stock V9 android and ##786# caused a boot loop? That's the first I've seen of that. Usually it loops because of the custom recovery (except CWMA that intercepts and passes stuff to LG recovery)
Also keep in mind if you have too many failed data profile attemps, sprints system can lock you out for some time from logins.
This can lead to red-herring theories.
- 03-14-2011, 11:07 PM #65
No, I had recovery-RA-GNM-thunderc-s-1.1.0.img but at one point I had CWM and I forgot that last time I was messing around when the VD update first came out, I had flashed back to recovery-RA-GNM-thunderc-s. I knew that RTN would work with CWM but unfortunately I didn't have CWM!
Yeah I've got it all figured out finally. Boy what a hassle. so ##SCRTN# only clears NVram and leaves everything else alone? That might be better to try for those on custom roms, because ##786# just seems to cause everything to force close when you're not running a stock rom, and especially messes stuff up if you're not on the newest CWM recovery.
When I used the nandroid (and followed instructions to a T!) from the unroot and back to stock stickied thread, my phone would boot up, go to the sprintID screen, then just reboot, then go to the sprint ID screen etc. etc. then every 4th reboot maybe it would stay on long enough for me to turn on USB debugging, then I'd have to go through the reboots again untill it would stay on long enough to force flash V9.
- 03-14-2011, 11:15 PM #66
The background text when you enter ##SCRTN# claims to reset that data, which I took to mean that data only.
I normally only run ##786# from stock ROM and stock recovery. That is the combo I feel most safe with because I know Sprint tests it. I also recently tested CWMA with stock ROM and it works fine.
I am guessing that ##SCRTN# + wipe data/cache is equivalent to ##RTN# reset.
So I know if you do a ##RTN# reset it will fix the can't update profile/prl problem. However I don't know if the solution is purely in NVRAM or if the reset NVRAM causes stuff at the Android level to run through initialization routines that repair the Android portion. So basically I don't know if the "fix" is in NVRAM, NVRAM+Android, or just Android (triggered by NVRAM reset) I know that ##RTN# reset has all the bases covered.
- 03-14-2011, 11:17 PM #67
- 03-14-2011, 11:23 PM #68
- 03-17-2011, 08:43 PM #69
Just a Question. You sau you know that sprint tests it, do you mean they check for SW version before activating?
I could see them checking firmware when setting you up for data, but do you think I'd be fine if I just go back to a stock nandroid, do ##72786# then nandroid back, or will the custom recovery somehow prevent everything being written to NVRAM?.
Edit: Eh, I just took the plunge and did it anyways! I still have been having trouble my phone would not recognize that there is a newer PRL out there, I thought maybe it was just not available at my tower, but just for fun I decided that now that I have CWM loaded I will go ahead and nandroid back to my stock VD and just do a ##72786# and see what happens. To start, hands free activation hung on "connecting to server". I canceled out of that, but my data seemed to work fine when i opened the browser to get it to try and activate again. Update PRL kept saying it was up to date when it wasn't so I then did a full ##786# and once it rebooted and was in the setup, hands free activation worked like a charm and then my PRL updated! Weird. guess the NVRAM was pretty messed up that it took me 3 ##786# and a ##72786# to get my dumb prl to update.
- 03-17-2011, 11:35 PM #70
When I said Sprint tests it, I meant I know Sprint tests the functionality of ##786# reset with the stock recovery before releasing an update. It is core functionality that they must have working. I didn't mean they test (as in check for) something on your phone.
- 03-18-2011, 02:18 AM #71
- 03-19-2011, 02:22 PM #72o_O
- 1,971 Posts
Woo, ugly. My second near-bricking of this phone.
After an oops, duh, I did an LG style factory reset from clockworkmod xionia_cwma_12518.4_virgin.img; (yes, factory reset with custom recovery is a known horrible idea and I should've known better,) and after that:
phone keeps booting to LG logo a couple times, then "Android system recovery>formatting data,cache...>reboot", then repeat.
My instructions assume you have set up/know how to use adb, and have the fastboot tool as well. Not a guide for newbies.
I finally broke the loop...
using adb, which would only connect for a couple seconds while the recovery was active.
command line:adb reboot bootloader
So, I copied an older clockwork recovery (recovery-clockwork-22.214.171.124-ov-20110220.img) to the .../android.../platform-tools directory on my desktop PC where adb lives since I put fastboot there with the other phone tools,
note:(it looks like any other recovery which would normally function on the phone works for this)
command linefastboot boot recovery-clockwork-126.96.36.199-ov-20110220.img
This next step may not be required, but it's what I did. It looks like the recovery isn't really gone, just has some stupid flag set which forces it to do the factory wipe every time it's started up, so a re-install probably doesn't do anything. Made me feel better, though. The next step after this is the important one... restore your last backup!Then, re-install xionia_cwma_12518.4_virgin.img (from here) custom recovery with adb (it appears this custom recovery is deactivated by the boot loop, it's still there but won't respond, only does the "Android system recovery blah blah reboot" instead of running the recovery properly, even after breaking the loop by rebooting into another recovery and restoring the last backup)
I assume flash_image is still set up on your phone for this. Copy the xionia_cwma_12518.4_virgin.img to your SD card while still in custom recovery. Make sure to remount the sdcard in the mounts menu after this or flash_image won't see the file.
command lineadb shell
flash_image recovery /sdcard/xionia_cwma_12518.4_virgin.img
If you don't flash the xionia_cwma_12518.4_virgin.img back into the phone it only boots into whatever custom recovery you put on it to break the loop.
I'm still unable to get into this recovery, it just does the stupid "Android...formatting...rebooting" thing, but at least it just does it once and then I can use the phone.
Other recoveries I've tried only boot into recovery, not into Android, after this style near-bricking... but at least in those you can do your backup/restore and then flash xionia_cwma_12518.4_virgin.img back into the device so it'll start up.
I'll be looking for a better solution for this, but at least I can use my phone again!
It was down for almost a WHOLE HOUR! AGGGHHH!
Though I'd share my experience to maybe give others some hope or at least a different thing to try for unbricking the lg-lg-recovery-reboot loop.
- 03-19-2011, 05:02 PM #73
- 03-19-2011, 05:13 PM #74o_O
- 1,971 Posts
It'll get figured out. The data/cache partition wipes at boot remove all my saved settings every time I reboot. grr.
<edit> just tried the newest .6 version from zefie's custom-recovery-xionia-clockwork-cwma thread and it also will not run itself, just that factory wipe which I seem to be stuck with for the moment. If I press the power button while it's doing the 'formatting...' thing, I can see the CWMA version at the bottom of the screen briefly.
Haven't figured out how to dodge that bullet except maybe unrooting/returning to stock (again) and re-rooting. I've formatted everything, swapped ROMs, swapped kernels, swapped recoveries, and nothing seems to overwrite the setting forcing the format on boot. Digging through the custom-recovery-etc thread now to see if there's a solution or maybe someone else has ended up with their handset where mine is now (not bricked, but weird and annoying.) I've bothered zefie enough already, so I'm not gonna ask him for a solution as I'm sure he's quite busy.
<editx2>tried the .3 version, it let me click the fix recovery boot loop option but did not get rid of the format-on-boot.
this post here in the custom-recovery... thread did it.
Cleared the blasted /dev/mtd/mtd8 which had the recovery flag in it with adb. the timing had to be as quick as when I got it into the bootloader the first time from the reboot loop.
- 03-30-2011, 01:45 AM #75
and they gave me a new phone*no cost since i have insurance* (which i have now rooted and am running ThundeRom