Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}
Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom
Related
Heya XDA - I have no idea WTF happened to my tab. Received notification of a OTA upgrade yesterday, taking me to one of the most recent 3.1 builds (.10 if I remember) - this morning woke up to another OTA update message offering me to go to .11 - accepted, downloaded, tablet hung up during the OTA process.
Now here's where it gets tricky. No matter what I do, when powering up my tablet I get the "Power Off - Shutting down" screen, and a endless spinning circle as the tablet claims to be shutting down. I cannot access any part of the system - all on screen commands are dead, except for the Settings icon in the lower right hand corner - i can click it, enter settings - but the moment I try to select a catagory or change any setting, the system goes right back to the "Power off - Shutting down" screen.
I am way outside the 30 days I can get a trade in - really don't want to have to mail this thing off to Acer.
Here's what I have tried:
One of Vache's full ROM images for my Region - flashed via power and vol process- fails about 1/4 of the way through.
Clearing cache/data - managed to get the vol/power+rotation lock combo going that clears cache and data. Still cannot boot - once I power on no matter what I do I get the "Power Off - Shutting Down" screen.
Tried to do the factory reset via USB keyboard + "Home"??? button? Heard mention this opens up a menu of some sort that I can factory reset from, I have two different USB keyboards and cannot manage to make this happen. Anyone able to explain this? Can this help me?
What's so weird about this - once I power up, I get the "Power Off - Shutting Down" screen no matter what I do. During this time, my battery shows up as %15 - this a500 has been on the charger for hours and hours, overnight last night, was 100% this morning before I applied the OTA update. Even with tablet plugged in, the battery shows as only 15%. What's even weirder - with tablet power off and plugged in, I do not get the red or blue charging light from the power button.
Totally freaking out here, no idea what to do. Anyone able to help?
Edit: When trying to manually flash a update.zip - I am getting the Clockwork Mod (I think?) flash screen - a green droid guy with gears turning. This fails about half way through. I have installed ClockWorkMod before this problem - but cannot enter the clockwork menu by the normal vol/power combo - I am so confused
Edit again: From browsing other posts - seems I am not the only one with this problem. The most recent OTA update failed, every single reboot since then is useless - all I can get is the "Shutting Down.." screen. Trying yet another update.zip via MicroSD to see if I can actually restore my tablet
Edit Yet once more (Problem Resolved!) - no idea how - but after a lot of searching I found a full package with build number 4.010.40_COM_GEN1 - this update.zip flashed with no problems, and my Iconcia is UNBRICKED! Sorry for the panic, everyone
OTA .13 Failure
I have the same problem, but got there by a different path. After many attempts to upgrade to .11 from .7, I downloaded the full file .02 to .11, decrypted and moved update.zip into the external sd card. Used the power / vol- combination and the update to version .11 went on without a hitch. Shortly after that, I received a notice that .13 OTA was available. It appeared to install without a hitch but after it rebooted (automatically) the tablet came back and immediately displayed the never ending Power Off screen described above. I would add that a two gears with a belt icon is sitting in the top left corner and "Android System" is noted beside that icon. I have tried every trick I have found in the forums to fix this:
1. Removed the SD card and shut down the tablet
2. Used power / vol- with portrait rotation lock turned on
3. Put the SD Card (with the .11 update.zip file ) back in and tried 1 and 2 again (no change: never ending power Off)
4. Tried power / vol+ with rotation lock. Saw the cach clear and looked very promising. Came back up with the rotating gears guy, but still went back to Power Off.
As soon as the power button is pressed the power icon goes red and stays there. Looks like the .13 update fools the device into thinking the battery is dean and it tries to shut down but never completes the cycle.
Acer A500
Rooted
Acer Recovery installed
.11 last successful update
US (Texas)
Failed .13 OTA
alamotx said:
I have the same proble,, (trim) I would add that a two gears with a belt icon is sitting in the top left corner and "Android System" is noted beside that icon. I have tried every trick I have found in the forums to fix this:
1. Removed the SD card and shut down the tablet
2. Used power / vol- with portrait rotation lock turned on
3. Put the SD Card (with the .11 update.zip file ) back in and tried 1 and 2 again (no change: never ending power Off)
4. Tried power / vol+ with rotation lock. Saw the cach clear and looked very promising. Came back up with the rotating gears guy, but still went back to Power Off.
As soon as the power button is pressed the power icon goes red and stays there. Looks like the .13 update fools the device into thinking the battery is dean and it tries to shut down but never completes the cycle.
Acer A500
Rooted
Acer Recovery installed
.11 last successful update
US (Texas)
Failed .13 OTA
Click to expand...
Click to collapse
Exact same problem here. Downloading update.zip files like mad trying to find one that will work. Anyone have any idea what the hell is going on?
Moving to Q&A.
PS: Every Q? thread should be posted in Q&A.
Thanks for that - sorry for mispost. Again, as noted in my original post - question answered, issue resolved. Total panic this morning
entropy.of.avarice said:
Exact same problem here. Downloading update.zip files like mad trying to find one that will work. Anyone have any idea what the hell is going on?
Click to expand...
Click to collapse
Me too... Ive tried 104.02, 4.010.22, 141.07, 141.02 none of them are getting me back... I can boot the tablet, but I now have no launcher icons for back, tabs, and home, and of course no clock and settings tab at the bottom. I have no root, and no CWM now. HELP!!!!
entropy.of.avarice said:
Thanks for that - sorry for mispost. Again, as noted in my original post - question answered, issue resolved. Total panic this morning
Click to expand...
Click to collapse
Please share your solution for the rest of the community.. if the solution is in a different thread, could you put a link here to the other thread with your solution?
Thanks
Euclid's Brother said:
Please share your solution for the rest of the community.. if the solution is in a different thread, could you put a link here to the other thread with your solution?
Thanks
Click to expand...
Click to collapse
For sure - sorry about the delay on that, was just so excited to be unbricked after a day of futile effort, I needed a break.
Anyway - here's what I have figured out. Somehow during the ota update I received this morning something failed - the tablet rebooted, and regardless of what I did the moment I booted up I would get the powering down notification. System access was not possible. This was on a 100% stock official 3.1 version - even unrooted before letting the update run.
Tried one of the full ROMS from Vache's thread in the dev section, as well as a bunch of other backup images I was able to find. Every single one failed at about 25%.
After a lot of fail - I gave this thread a try:
http://forum.xda-developers.com/showthread.php?t=1187578
"Bricked Tablet...help!"
I used the link on the bottom of page one - the unencrypted update.zip user kjy2010 was kind enough to upload - here is the direct link - http://www.multiupload.com/WCT2FYLMQC
This one worked - put on MicroSD card and flashed via vol/power method - result - 4.10.40_COM_GEN1 - and I am unbricked! Iconiaroot 1.3 worked for getting root after install - slowing getting my tab back to normal now
Hi All,
OK, I am both new and stuck, I have read every page in the unlocking Atrix thread and the one click root thread but I still do not know what is wrong.
I started off by running the one click root listed here, the root went fine and seemed to work, so I proceeded to install ROM Manager but when I tried to back up my phone the process failed.
I googled the error and it turned out that I did not unlock the Boot Loader, so I followed all the instructions that explained how to do it and nothing worked.
Thinking something must have gone wrong I went back to the one click root tool and unrooted my phone, I checked and everything was working and the phone seemed fine.
So then I started down the longer process of unlocking/rooting here , following the steps to the letter and here is where I come unstuck.
I have a UK carrier free phone so after downloading and installing the RSD Lite software I used the SBF_Flash file but when I selected this file the “Start” button remained greyed out.
I researched this issue and found the international flash called intl-fix-try1.sbf, this file looked like it was going to work, the start button became clickable and the process looked ok.
Once I clicked start the flashing started and percentage done went straight up to 98% in a matter of seconds, then as per the instructions the phone reboots but starts to reboot fully, the process % resets and starts from zero going up in increments of 3%, by the time the process is at 65% my phone has fully booted and is sitting at the lock screen, if I leave it there the process will go up to 100% but the status will still say "in progress" until I swipe the lock screen and then it says complete.
I was doubtful that the root had worked but just to make sure I proceeded to move the phone into Fastboot mode and go through the OEM Unlock process but once I have typed in fastbook oem unlock and hit enter the command prompt just comes up with a message waiting for device to respond and nothing more.
Please help as I am really stuck, I followed your guide to rooting my Galaxy tab 10.1 and had it sorted in minutes, my ICS rom installed and everything backed up via ROM Manager so I am not a total dummy.
Any suggestions?
Kind Regards
Chris
when you tried to flash the sbf on rsd lite did you have the phone pluged into the pc and have it put into rsd lite mode
prolly not if you still seen the lock screen
turn phone off then turn on by holding power button down and volume down
when u see fastboot word on the atrix use volume down to scroll to rsd mode then hit volume up and proceed with rsd lite and the sbf
Here might explain it little more..
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
That is exactly what I did, I have just done it again now . . . .
I clicked start
The console/flash starts,
The phones screen goes black,
Then the Red Motorola M appears
The flash progress jumps to 98%
Console Status says something about USB Pass through/phone rebooting
Then reboots and the Red Motorola M appears again
Then progress carries on and goes up and at 16% by now the phone is now fully in its boot process and by 26% it is at the swipe screen
I have the phone in USB debug mode and the usb connection set to mass storage. Could I be using the wrong SBF file?
Thanks
I have tried that method as well as it is uses a different sbf file called zomgunocklite.sbf when I use that file I an error saying sec_exception: febe, 35, 35 I googled that and it came up with a similar issue but it did not help.
So since my first post I have been speaking to ltdanno360 on here, I just wanted to take the time out to say a MASSIVE THANK YOU.
He has taken me through getting my phone back to a usable state and then all the way through fixing up with the latest bits and pieces.
I have taken up a good few hours of his time and I am now a very, very happy Atrix owner.
It is people like ltdanno360 that make this forum and the internet community such an amazing place. Just imagine driving home from work one day and you car breaks down on the freeway, a stranger stops and spends two hours of his day fixing your car before sending you on your way.
Things like that do not happen often in the real world but people like Danno are great examples of what humanity often misses.
Big Thanks Bro
Awesome guy, awesome forum.
Two days ago my wifes 1st generation Nexus 7 refurb started giving the "Unfortunately, NFC service has stopped" error. You click OK and the error instantly pops up again. There is a moment to click on something if you're fast and I've been able to click on settings but when settings opens it's nothing but a black screen with no options. This means that I can not enable usb debugging. I have tried quite a few different processes, ADB sideload, going through the bootloader, but they all seem to require usb debugging and the tablet is never recognized. The tablet is stock but I have no way of knowing what version of android it is currently running with the blank settings window (unless you can give me a tip on that). Have done two wipe/factory restores on it and the error comes up right at the first boot screen. I am willing to pursue any option to get this tablet in working order. Rooting, flashing, whatever but I am a novice in the world of android rooting. It was purchased off groupon (won't make that mistake again) and the 14 days are past so If I have to send it in, it's cash money out of our pockets.
Do I have any options? Thank you for your time!
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
notnorm said:
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
Click to expand...
Click to collapse
If the tablet has never been rooted, and the factory reset procedure seemed to complete successfully, then your symptoms suggest that something is wrong with the /system filesystem - which, for stock devices is never modified (always mounted read-only).
So that in turn suggests *perhaps* flaky hardware - probably the flash memory chip - that has gone awry and is the root cause of the problem.
It is conceivable that you could go through the process of unlocking the bootloader and re-flash a Google-provided "factory image", and that the problem will go away. But if the root cause is really a flaky flash memory chip, it will very likely return with a vengeance, and your efforts will be for naught.
There is something missing in your narrative, however - if the appearance of the "NFC Service has stopped" dialog on-screen prevents you from interacting with your (intended) foreground apps, how were you able to perform a factory reset and then follow that up with a tablet configuration? (e.g. to get Google credentials on the tablet so you could push apps to it by using a PC Web browser from the Google Play market).
If you are unfamiliar with rooting but still want to proceed with reloading the factory images, you will have to follow the Stock Recovery tutorial threads. Many users - especially those with Windows machines - seem to get stuck at this step, although truth be told that has nothing to do with Android, and everything to do with Windows Driver Installation Hell.
Note - specific to your situation.. You do not need to enable USB debugging to re-flash factory stock images. You only need to communicate with the device (booted into bootloader mode) with the "fastboot" program. For this you only need working USB hardware - not "adb".
good luck
BTW, note that you can perform a factory reset in the stock recovery without launching it from the O/S. The sequence is:
1) Turn the tablet off (not screen off, but powered completely off)
2) Boot into bootloader mode by holding Power+Vol-Down together (hold them down until android lying on its' back shows up - about 4 seconds)
3) Using the vol-up/vol-down button, select "Recovery Mode" on screen and press the power button
At this point the screen will go black. Wait about 10-13 seconds. The screen will remain black even though the stock recovery is now running. To get the screen to show the (stock) recovery menu,
4) press and release the Power & Vol-Up keys simultaneously.
The stock recovery menu should show now up. If it doesn't, try again. (After 60 seconds if you have done nothing, the tablet will reboot to the "normal" OS).
5) Use the on-screen menu to perform a factory reset (follow the directions on-screen for key usage).
Thank you so much for your response! The unanswered question is that I managed to put in the network info and what not during setup by hitting OK on the error and tapping the letter in the moment before the error popped up again. Not a fun task!
I've been trying to flash and after installing the google usb drivers it's still doing the <waiting for device> for infinity. I think I will have to bite the bullet and send it in. You saying that it might be a flash chip is kind of comforting because I think I might have bashed my skull against this issue forever before giving up!
Chris
flashed the wifi fix for the TMObile us version (from the X Note rom page)and was able to get out of the loop.
Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.
same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.
Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911
So, my tablet shut itself off.
I turned it back on, and it started up the activation process / new device walkthrough that you get when i first got the device. All my apps were gone. Play Store crashed if I opened it. Restarted device, and it started up the activation process again. Attempted a factory reset from the settings menu. Nothing happened. I dont mean nothing changed, but literally nothing happened. Selected reset, said yes on cofirmation, and nothing happened. Held down the volume down and power buttons, let go of power button, then held all three to get to the alternate factory reset option. Selected it and got a series lines of "failed to mount". Restart device, nothing has changed.
Any ideas on what exactly has happened?
Any suggestions on what to do, with detailed instructions?
UPDATE:
Tried a variety of rooting options, which are apparently very limited for the v410, to see if I could fix my issues.
Purpledrake brought me to the recovery mode screen which ended in the same results: "failed to mount"
OneClickRoot and KingRoot both just got hung up at 0%.
Would really appreciate some insight into what the issue is, and wether it is something I can fix myself.
Kingo Root hangup
Did the same thing to me when using it from the PC, but I just rebooted my V410 and ran it again. It worked the second time. Didn't do me much good, though. Can't get into recovery, can't unlock bootloader, can't find a way to install CM on this thing.
I still have this device sitting around. I would love to be able to fix it. Hoping someone out there can help me out. It seems to me that its a memory issue, since in settings under storage, it says there is only 100mb of available space, and that 15 of the 16 total gb being used is system data.