So you flashed the OTA update.zip with custom recovery...
Yeah that phone is toast. Sorry
[How-to] Guide to Rooting with software version LS670ZVC
- Thread starter drewwalton19216801
- Start date
- Status
So you flashed the OTA update.zip with custom recovery...
Yeah that phone is toast. Sorry
So you flashed the OTA update.zip with custom recovery...
Yeah that phone is toast. Sorry
really? even though it powers on somewhat? In the directions for going back to stock it wanted me to go to V8 then V9. Well I flashed the recovery "GNM's v1.1.0 Recovery Kernel" while in my stock nandroid. I figured my nandroid is already V9 so I flashed the OTA (renamed update.zip) directly.
Bricked?
Yeah permabricked. I discovered this by accident a while ago and been warning people to never try to update RADIO from custom recovery. Nothing you can do but call Sprint.
Edit: There is no 'unbricker' for the PC either if you plug it into your PC you will notice it doesn't even acknowledge the phone.
That sucks! Well that doesnt suck as much as the fact I bought this phone ought-right so they are not going to want to replace it for free. They will want me to use my upgrade, thats the reason I bought this to save my upgrade for a dual core one day next decade, LOL.
Bricks suck. I feel for you, mate. I accidentally bricked my dad's EVO a while back attempting to put Cyanogen on it. Still haven't heard the end of that one.
Anybody have any experience with sprint with a phone bought ought-right? Lame! I said earlier I miss HTC, I really miss HTC now! The PC will not recognize it, wont go into recovery, Its a sad sad day
No Gold Card action???
No Gold Card action???
Anybody have any experience with sprint with a phone bought ought-right? Lame! I said earlier I miss HTC, I really miss HTC now! The PC will not recognize it, wont go into recovery, Its a sad sad day
No Gold Card action???
Seeing as how it won't even boot, you could try going in to a Sprint store and asking for a replacement. Chances are the reps they have on hand won't know enough to be able to figure out exactly what happened to the phone.
No guarantees, but I think that's worth a shot.
Just tell them you got an update offer and it failed. Blame it on the OTA they are pushing.
True that. Just make sure you come off as someone who's new to Android and they should replace it no problem.
I had a similar experience with my Hero. It came from flashing a radio. I did everything that was outlined correct, but got bricked. However I could somewhat boot. I got to an HTC screen and would sit there. Someone figured out a method to boot using fastboot. So my phone kind of became usable. I finally returned mine, but then someone finally found a permanent fix. If it sounds like any of this might work, I could try and dig up the threads over on XDA.
we dont have fastboot
been on phone with sprint for 15 minutes now, heading to 3rd tech, lol.
best bet is to just take it to a store. i just bricked mine and am about to head down there now.
i don't know what i did lol. somewhere in the flash back to stock. flashed everything back to stock for like the 5th time and this last time when it rebooted after flashing radio it stuck at lg. can't get into recovery or anything.
i don't know what i did lol. somewhere in the flash back to stock. flashed everything back to stock for like the 5th time and this last time when it rebooted after flashing radio it stuck at lg. can't get into recovery or anything.
we dont have fastboot
been on phone with sprint for 15 minutes now, heading to 3rd tech, lol.
Forgot we don't have fastboot.
Looks like in the Hero permanent fix you did need fastboot and then everything was adb. Just in case any guru can make something of this. http://forum.xda-developers.com/showpost.php?p=6013606&postcount=2
Well the third tech support told me to bring it in to a sprint repair center, they have software to fix it (yeah right) unless they can JTAG the phone I doubt it will be fixed. She also told me if they can not fix it than I will get a free replacement. I have a upgrade on March 1st, they better not try some B.S. saying I "have" to use my upgrade!
What it seems like is happening is the phone is looking for recovery to complete the radio flash, but my recovery is not what the "update" is looking for. Therefor nothing happens, as protection the bootloader is not letting me boot into my recovery, or complete the radio flash as it does not see my recovery. Can we boot into bootloader, I know we dont have fastboot yet, but there is some sort of bootloader we can boot into, no?
So I followed the instructions on the first page.
I'm able to do all steps including run rageagainsthecage
I hear the USB unplug/plug sounds as rage kills off the processes and kicks me out of the adb shell. However the adb interface never comes back up (verified in windows device manager devmgmt.msc) so my subsequent adb shell to verify the adb server is in root never connects, producing an error of device not found.
Any ideas? I'm guessing after rage kills the adb server on the phone, it is having trouble starting up, but I can't really see what the error is, since adb won't connect.
I'm able to do all steps including run rageagainsthecage
I hear the USB unplug/plug sounds as rage kills off the processes and kicks me out of the adb shell. However the adb interface never comes back up (verified in windows device manager devmgmt.msc) so my subsequent adb shell to verify the adb server is in root never connects, producing an error of device not found.
Any ideas? I'm guessing after rage kills the adb server on the phone, it is having trouble starting up, but I can't really see what the error is, since adb won't connect.
sfhub: reboot and download superuser. when you adb shell su again it'll ask for permission on the phone. rereading your post, try adb killserver and then connect again if you haven't already.
took mine to sprint. picking up a new one on friday. they said they could swap the screens for me so i don't have to deal with zagg lol.
i also feel it is important to note that my bricking had nothing to do with the instructions in this thread or the rooting process.
took mine to sprint. picking up a new one on friday. they said they could swap the screens for me so i don't have to deal with zagg lol.
i also feel it is important to note that my bricking had nothing to do with the instructions in this thread or the rooting process.
did everything up to run rageinthecage, adb will then not reconnect to the device, restarting the adb server does no good, the phone has to be restarted and the rooting fails.
Same here. Step 10 yields "error: device not found" even after letting the phone sit for several minutes.
If it helps here is my method for rageagainstthecage:
When your phone disconnects after running rageagainstthecasge, simply unplug the USB from your phone.. wait about 5 seconds, plug it back in.
while your phone is unplugged from the pc run
adb kill-server
on your PC
Plug back into PC and hope for root. Start over if not.
Edit: It seems LG fixed whatever prevented the recovery kernel from updating so people who are updating to VC are having NO WAY TO ROOT OR REVERT as of yet.
Last edited:
- Status
Similar threads
Trending Posts
-
-
-
-
Question I have a new Android phone and want to find a keyboard that I like
- Started by Figgerty
- Replies: 6
-
Facebook
Twitter
Instagram