Database Users

Back to stock gone wrong

In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien

jfpesant said:
In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien
Click to expand...
Click to collapse
I'm in the same boat as you. I've tried 6 computers. 1 detects it and I can unlock/lock bootloader but fails when I try to flash stock image.The other 5 computers, when I plug it in it freezes my tab in fastboot. WTF

logan_izer10 said:
I'm in the same boat as you.
Click to expand...
Click to collapse
Welcome aboard !

in the toolkit make sure you have the right model number in the "change" section,in the back to stock section check the "cant boot up"bit,then click flash stock + unroot,works all the time for me

jfpesant said:
In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien
Click to expand...
Click to collapse
As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn. The following instructions assume some basic Windows command prompt skills.
Read all the directions before you begin and perform the steps at your own risk.
I want to assume that you have the correct drivers installed, but I wont. This and any following verbosity is not to be condescending, but rather not to assume anything. If you're certain the adb and fastboot drivers are correctly, skip to step 7.
To obtain the tools and drivers needed, download the Android SDK - http://developer.android.com/sdk/index.html
Run the SDK installer that you downloaded and follow the on-screen instructions.
Make note of the install location which defaults to: C:\Users\<user name>\AppData\Local\Android\android-sdk this is where the tools and drivers will be downloaded to. This will be referred to as your sdk directory
Note: Java SE JDK is required by Android SDK. Download and install the Java SE JDK from Oracle
Run SDK Manager.
Under Tools, check the box labeled "Android SDK Platform-tools" - this provides adb and fastboot
Under Extras, check the box labeled "Google USB Driver"
Press the "Install # Packages..." button and follow the on-screen instructions.
Install the abd driver - detailed instructions can be found at http://developer.android.com/tools/extras/oem-usb.html
Note: in order for your device to be detected, USB debugging must be enabled on the device
Once the driver is installed open a command prompt and change directories to <your sdk directory>\platform-tools (see #2). From the command prompt run "adb devices". This will list any adb-capable devices that are attached to the computer by their serial number assuming your drivers are installed correctly. Recap:
Code:
> cd \Users\<user name>\AppData\Local\Android\android-sdk\platform-tools
> adb devices
# the following output should be returned
List of devices attached
<device serial number> device
Use adb to boot the device to the bootloader:
Code:
> adb reboot-bootloader
The device should now be in fastboot mode and Windows should be attempting to install the fastboot driver. You can verify that the driver has been installed by running the following command:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
Download the factory image for Nexus 7 from https://developers.google.com/android/nexus/images#nakasi. The resulting file will have the extension .tgz. You will need something that can reliably decompress and extract files from this archive. If in doubt at all, use 7-Zip http://www.7-zip.org/download.html.
Open the archive with 7-Zip you should see a single .tar file. Open the .tar file with 7-Zip as well.
Inside the .tar file is a directory that will resemble "nakasi-jro03d". Open that directory.
Extract the contents of the "nakasi-jro03d" directory to <your sdk directory>/platform-tools. The extracted files should be as follows: bootloader-grouper-3.34.img, image-nakasi-jro03d.zip, flash-all.sh, flash-base.sh
The flash-all.sh file is a shell script that contains all the commands required to flash the factory image using the fastboot command. In order to use fastboot, we need to boot the device to fastboot mode. This can be done with adb:
Code:
> adb reboot-bootloader
In order to do anything useful, the bootloader must be unlocked. Do that like so:
Code:
> fastboot oem unlock
Follow the directions on the device, using the volume and power buttons to select "Yes".
In fastboot with your device's bootloader unlocked, run the commands listed in flash-all.sh in sequence, waiting for each command to finish. For convenience I have them here:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-3.34.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jro03d.zip
# optionally re-lock the bootloader.
# You may want to do this if you're returning the device for warranty work.
> fastboot oem lock
# finally, reboot
> fastboot reboot
That should do it.

tonybhoy said:
in the toolkit make sure you have the right model number in the "change" section,in the back to stock section check the "cant boot up"bit,then click flash stock + unroot,works all the time for me
Click to expand...
Click to collapse
Worked for me !!! Thanks bro !
(I previously have tried this, but didn't choose the right model number... so it didn't work)

comminus said:
As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn. The following instructions assume some basic Windows command prompt skills.
Click to expand...
Click to collapse
Thanks a lot for the insight. I'm all about DIY so I'll definitely give this a try next time I have to play in android.
Julien

jfpesant said:
Thanks a lot for the insight. I'm all about DIY so I'll definitely give this a try next time I have to play in android.
Julien
Click to expand...
Click to collapse
No worries, I'm glad the simpler route worked!

[GUIDE] Flashing a Factory Image with fastboot / return to stock

Notice: If you are going to flash the nakasi android 4.3 JWR66Y factory image, you will need to download the bootloader from JWR66V and replace the one from the factory image. The bootloader in JWR66Y will fail flashing with a signature mismatch error on the device and InvalidState on fastboot.
The objective of this thread is to provide detailed instructions on flashing a factory image using fastboot rather than a toolkit. As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn about the process. The following instructions assume some basic Windows command prompt skills.
Read all the directions before you begin and perform the steps at your own risk.
Overview
This will restore your Nexus 7 to it’s factory state. All user data will be deleted, so now is a good place to stop and backup anything you don’t want to lose.
This guide is in three parts - basic knowledge and obtaining the required software, driver installation, and flashing the factory image. This and any following verbosity is not to be condescending, but rather not to assume anything.
Basic Knowledge
This guide assumes some basic Windows command prompt skills - changing directories, etc and is written primarily for Windows users. Make sure that you have file extensions enabled in Windows Explorer.
Software Requirements
Android SDK - adb, fastboot, usb drivers
Java SE Development Kit - required by Android SDK
A Nexus 7 factory image
7-Zip - used to extract factory images from a .tgz file
Download and install 7-Zip - http://www.7-zip.org/download.html
Download the Nexus 7 factory image - https://developers.google.com/android/nexus/images#nakasi and save it somewhere you can easily retrieve it.
Make sure to download the correct image for your device variant (Wi-Fi vs GSM/HSPA+; nakasi vs nakasig)
Download and install the Java SE JDK - http://www.oracle.com/technetwork/java/javase/downloads/index.html
Download and install the Android SDK - http://dl.google.com/android/installer_r21-windows.exe
NOTE: Notice the install location. This defaults to C:\Users\<user name>\AppData\Local\Android\android-sdk the platform tools (adb, fastboot) and usb drivers will be downloaded to this location. This will be referred to from here on as your sdk directory
Run the SDK Manager
Under Tools, check the box labeled "Android SDK Platform-tools" - this provides adb and fastboot
Under Extras, check the box labeled "Google USB Driver"
Press the "Install # packages..." button and follow the on-screen instructions.
The platform tools will be installed at <your sdk directory>\platform-tools and the usb drivers will be in <your sdk directory>\extras\google\usb_driver
Driver Installation
This seems to be the most confusing part for many people. Be patient and thoroughly read all the instructions.
Huge thanks to @tetakpatak for taking the time to put together a video showing this process! http://www.youtube.com/watch?v=bhA5CN4335U&feature=player_detailpage..
Enable usb debugging on your device (found under Settings > Developer Options)
NOTE: Since Android 4.2 the Developer Options are hidden by default.
To enable them, go to Settings > About Phone, and tap on build number around seven times. A small dialog will appear letting you know "You are now a developer!"
Install the abd driver - detailed instructions for installing or upgrading and existing driver on your version of Windows can be found at http://developer.android.com/tools/extras/oem-usb.html
Once the driver is installed open a command prompt and change directories to <your sdk directory>\platform-tools (see #2). From the command prompt run "adb devices". This will list any adb-capable devices that are connected to the computer by their serial number assuming your drivers are installed correctly. Recap:
Code:
> cd \Users\<user name>\AppData\Local\Android\android-sdk\platform-tools
> adb devices
# the following output should be returned
List of devices attached
<device serial number> device
Use adb to boot the device to the bootloader:
Code:
> adb reboot-bootloader
The device should now be in fastboot mode and Windows should be attempting to install the fastboot driver. NOTE: if you had drivers previously installed, you may need to upgrade them. This is the same procedure described at http://developer.android.com/tools/extras/oem-usb.html
You can verify that the driver has been installed by running the following command:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
Do not proceed further if fastboot can not recognise your device. You are in driver hell and this must be resolved before continuing.
Extract the Factory Image
In order to extract the necessary files from the factory image archive, we will use 7-Zip because it can do this reliably. At this point you should have already installed 7-Zip and downloaded the factory image archive.
Use 7-Zip to open the factory image .tgz file. You should see a single .tar file. Open this file with 7-Zip as well.
Inside the .tar file is a directory that will resemble “nakasi-jwr66y”. Open that directory and extract the contents to <your sdk directory>\platform-tools.
The extracted files should be as follows: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh
Flashing the Factory Image
Put the device into fastboot mode by running the following adb command:
Code:
> adb reboot-bootloader
In order to do anything useful in fastboot, the bootloader must be unlocked. To do this, run the following fastboot command:
Code:
> fastboot oem unlock
Follow the directions on the device, using the volume and power buttons to select "Yes". NOTE: this will wipe all personal data.
In fastboot with your device's bootloader unlocked, run the commands listed in flash-all.sh in sequence, waiting for each command to finish.
Follow the commands for your device variant - Wi-Fi (nakasi) or GSM/HSPA+ (nakasig). For convenience I have them here:
NOTE: you will see some messages about the archive not containing boot.sig, recovery.sig and system.sig. That is normal, dont worry.
Wi-Fi devices (nakasi)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-4.23.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jwr66y.zip
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.23.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jwr66y.zip
After the final command completes, the device will reboot.
If you are sending the device in for warranty work, you may want to re-lock the bootloader
Code:
> fastboot oem lock
Finally, reboot the device
Code:
> fastboot reboot

Fantastic work!

Thank you for this tutorial! It allows us to learn how to do things via adb and learn how not to depend on a toolkit. I hope everyone that does not know how to flash things manually read this thread! Thank you for taking the time to help us learn!

comminus said:
Overview
This will restore your Nexus 7 to it’s factory state. All user data will be deleted, so now is a good place to stop and backup anything you don’t want to lose.
This guide is in three parts - basic knowledge and obtaining the required software, driver installation, and flashing the factory image. This and any following verbosity is not to be condescending, but rather not to assume anything.
Click to expand...
Click to collapse
Could I suggest adding a fourth section to you guide that you only alluded to. Backing up and restoring "anything you don’t want to lose." Detailed as your guide is, you've started with the assumption that a user knows how it back and reinstall the data they would likely want to save.
I don't even know how to do this so I'm stymied even before starting your guide.

Pariah3000 said:
Could I suggest adding a fourth section to you guide that you only alluded to. Backing up and restoring "anything you don’t want to lose." Detailed as your guide is, you've started with the assumption that a user knows how it back and reinstall the data they would likely want to save.
I don't even know how to do this so I'm stymied even before starting your guide.
Click to expand...
Click to collapse
You can always hook your phone up to your PC and copy your folders before this process. You can also make a nano back up and copy it to your computer and then drag it to the SD of your replacement phone and restore it after you get set up and rooted. Titanium back up is another good app to save your apps and data but you will still need to copy that folder to your pc before performing this and then re root your phone so you can restore from titanium back up. Best bet if you are happy with your set up is do a nano back up save that to your PC and now you have a back up to get back to where you were before.

Pariah3000 said:
Could I suggest adding a fourth section to you guide that you only alluded to. Backing up and restoring "anything you don’t want to lose." Detailed as your guide is, you've started with the assumption that a user knows how it back and reinstall the data they would likely want to save.
I don't even know how to do this so I'm stymied even before starting your guide.
Click to expand...
Click to collapse
The backup and restore of user data was intentionally left out because it is out-of-scope for this guide. You bring up a valid point about users needing direction for backing up and potentially restoring user data and files. I'd be more than happy to link to some existing guides that cover this topic in detail. I'll take a look around to see what I can find.
Sent from my Nexus 7 using Tapatalk 2

Thank you very much for this! Worked perfect and this gave me the confidence to do it manually and stay away from toolkits. Back to stock and locked bootloader ready to go back to the store.

sikagoon7 said:
I'm surprised this is just coming up. Thanks though!
Click to expand...
Click to collapse
I know I read your thread sorry about your loss. These tutorials help us learn how to do things manually and safe from making mistakes. Thanks again to the OP.

Excellent work comminus.... very well written!

Help help help!!! Lol
im running into problems..... fastboot wont work.... i have unlocked using fastboot no problem and can also use erase commands no problems.
however when it comes to " flash" or "update" commands, all i get is sending data and the size of what it is sending, but nothing happens. it just hangs there and nothing flashes up on my tablet either. the device hasnt hung as can still use vol keys to change options.
can anybody help me out with a solution here because im going insane!!
---------- Post added at 02:46 PM ---------- Previous post was at 02:31 PM ----------
im running into problems..... fastboot wont work.... i have unlocked using fastboot no problem and can also use erase commands no problems.
however when it comes to " flash" or "update" commands, all i get is sending data and the size of what it is sending, but nothing happens. it just hangs there and nothing flashes up on my tablet either. the device hasnt hung as can still use vol keys to change options.
can anybody help me out with a solution here because im going insane!!

Thanks for this guide I am following it for installing stock image. I'm getting until the last stage but when doing the fastboot -w update xxx.zip file I'm getting error messages saying 'image does not contain recovery.sig, image does not contain system.sig, image does not contain boot.sig' and then it fails to install.
Any idea what I'm doing wrong here?
Thanks
Edit: got it to work using a different windows machine - probably a driver issue somehwere it must have been

Glad to hear you got it working. Those sort of issues are almost always related to drivers.
Sent from my GT-I9100 using Tapatalk 2

Thanks for the excellent explanation. Got my N7 working again. (messed up the upgrade to 4.1.2)
Also got the error 'image does not contain recovery.sig, image does not contain system.sig, image does not contain boot.sig' but installation still worked.

Eeprom78 said:
Thanks for the excellent explanation. Got my N7 working again. (messed up the upgrade to 4.1.2)
Also got the error 'image does not contain recovery.sig, image does not contain system.sig, image does not contain boot.sig' but installation still worked.
Click to expand...
Click to collapse
I will update the instructions to mention that this is normal. Glad to hear you were able to get you N7 working again!

Great Sticky..
Thanks for the work on this.. my N7 was acting strange with one of the installed ROMs and
this guide helped me restore the device easily. :good::good::good::good::good::good:

This guide is great, I did a factory flash some weeks ago just to see how the procedure works and it is pretty easy if you know this stuff, but as a galaxy S3 owner I wonder why there's nothing equivalent to odin for the nexus 7? Afaik odin works for the gnexus. Odin makes reflashing stock images ridiculously easy.
Sent from my Nexus 7 using xda app-developers app

mertzi said:
This guide is great, I did a factory flash some weeks ago just to see how the procedure works and it is pretty easy if you know this stuff, but as a galaxy S3 owner I wonder why there's nothing equivalent to odin for the nexus 7? Afaik odin works for the gnexus. Odin makes reflashing stock images ridiculously easy.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the comments. Once someone has their computer set up to work with fastboot the process is just as simple as using Odin. The factory image archive contains batch and shell scripts which allow you to flash the images in one command - arguable just as easy as using Odin or Heimdall. But then, it's all personal preference anyway

do i have to do the erase commands before the flashing

I suppose its not technically required but I recommend you follow the steps as they've been laid out.
Sent from my GT-I9100 using Tapatalk 2

What if I can't go to fastboot because my nexus now only can be booted in cwr . Do you have any solutions regarding my matters?
Thanks,

[Q] Stuck in Bootloader

Hi all,
my nexus wont start after (failed?!) flashing with factory image. bootloader and recovery mode are accessable. i have no backup so i need to flash a new img, but my tablet wont be recognized by my computer anymore(adb drivers not working?!). i tried to deinstall and reinstall the adb drivers alrdy. Device manager shows nexus 7 as Android Phone with "Android Bootloader interface" i cant install adb drivers while in bootloader. in recovery mode i succeeded installing the adb drivers and the tablet is shown correctly in device manager... i need help dont know what to do :crying: .. any suggestions ?

ADB and fastboot drivers are different.

Pirateghost said:
ADB and fastboot drivers are different.
Click to expand...
Click to collapse
yes .. what are u trying to tell me? dont get it.. i used nexus root toolkit to help me apply those drivers.. but it wont work for bootloader/fastboot mode.. i cant flash my tablet because my device wont be recognized by my pc.. im stuck at the bootloaderscreen/fastbootmode....

http://bit.ly/Zqk7pm

and what do u want me to type in there ? i alrdy used google for the last 7 hours ?

oads said:
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
Click to expand...
Click to collapse
SMH
i filled it in for you.....

Pirateghost said:
SMH
i filled it in for you.....
Click to expand...
Click to collapse
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..

no. ADB and fastboot require separate drivers. just install the drivers required for n7 fastboot. there was a link in that list.
there are tutorials here on xda, as well as youtube videos and tutorials on other sites. take a little initiative and learn the ropes. it will help you out later on.

oads said:
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
Click to expand...
Click to collapse
Just relax and take your time.
If your tablet can go into fastboot mode, it is fine and will get better; the only thing standing between it's current state and being brought back to life is a little learning on your part.
Now you see what the problems are with using a toolkit - because they hide all the gory details from you, when the smallest thing goes wrong you are totally helpless due to a lack of understanding about what things are going on underneath the hood. And as it turns out, what "goes on under the hood" isn't really all that complicated either if you do things the full manual way.
Which is not to say that you can not simply just use the toolkit again; if you previously successfully installed drivers that allowed you to talk to the tablet in all of these modes:
- fastboot
- adb w/ custom recovery booted
- adb with Android booted
then it is not evident that you need to be fooling with drivers.
I suggest you read this thread, from start to finish
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Then, go over to your toolkit thread and read it from start to finish. You will see that there are & have been plenty of people in circumstances nearly identical to yours.
good luck

hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?

oads said:
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
Click to expand...
Click to collapse
that does not sound like a problem to me at all.
You communicate with the device using the "fastboot" program when it is in bootloader/fastboot mode, and with the "adb" program when it is in custom recovery boot.
What you see in the device manager appears to be completely normal - In different modes it shows up in different places. It's not supposed to show up with the same driver in different modes.
Code:
fastboot devices
will show you whether you are communicating successfully with the device when it is in bootloader/fastboot mode, and
Code:
adb devices
will show you whether you are communicating successfully with the device in recovery mode.
I suppose your toolkit has some stoopid menu or buttons someplace that will allow you to test for exactly the same thing. Now all you need to do is stop posting here and read a little bit.
good luck

bftb0 said:
Now all you need to do is stop posting here and read a little bit.
good luck
Click to expand...
Click to collapse
well i did read quite a lot today :crying: i cant find my device when i type in adb devices, im pretty sure i have the right drivers installed since i followed the instructions step by step.
this guy seems to have the same problem: http://forum.xda-developers.com/showthread.php?t=1808076
could someone tell me if this could be a possible solution :http://stackoverflow.com/questions/...e-over-usb-via-adb-devices-from-windows-7-x64
also would it be possible to just get into the bootloader (since thats the purpose of adb drivers and i can do this) and just proceed with fastboot commands ? if i type in fastboot devices the tablet will show up...

In your first post, you indicated that you couldn't connect to the tablet that was in bootloader mode with adb.
And then you were told - once vaguely and once quite specifically - that *nobody* can communicate with the tablet using adb when the tablet is in bootloader/fastboot mode.
As stated previously, use the "fastboot" program when the tablet is in bootloader mode, and use the "adb" program when the tablet is booted to the custom recovery (or the regular android boot if USB debugging has been enabled).
You can use either one of these modes to effect a rescue so long as they are working correctly - they don't need to both be working. Eventually you would want that to be the case, but for the moment why don't you just stick with what is working for you.
If you get a device ID printed when you execute "fastboot devices" when the tablet is in boot loader/fastboot mode, that is all you need to reinstall a factory ROM, using nothing but fastboot.

thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g

oads said:
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
Click to expand...
Click to collapse
Well, I can't see what instructions you are following, and there is a possibility of sensitivity to an exact sequence. In particular, is a
fastboot reboot-bootloader
performed after the bootloader is flashed, but before the radio is flashed? It might be important that you are performing the radio flash from one bootloader vs. the other. Just a guess. (Along the same lines, do you see something unexpected happening, such as a boot to the recovery after the radio flash command?)
There are some other threads on this I think. (I have a grouper device not tilapia) But I thought that those threads were about problems with radio flashing when a custom recovery (rather than a stock recovery) was on the phone, but that was for applying the OTA package for tilapia rather than flashing directly from fastboot.
-------------------------------------------------------
[Edit] whoops, wait a minute.... "cannot load"
When you run fastboot from the command line, the file names you give are relative to the current directory. Did you move those image files into the same directory that you are executing the "fastboot" command from?
Alternately you can specify the full pathname to wherever you unpacked the files, for instance
fastboot flash radio C:\myfolder\unpacked\googlen7\4.2.2\radio-tilapia-1231_0.17.0_1025.img

hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?

oads said:
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
Click to expand...
Click to collapse
I would complete the rest of the steps first and see if everything is still working. Your device *should* still work just fine with an old radio firmware. (Boot it up and see what radio firmware the OS reports on the Settings... about device... status page).
I'll pull down the tilapia image and tell you what MD5 I observe for the radio image.

just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio

Pirateghost said:
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Click to expand...
Click to collapse
yes

SHA1
0798439d363beb145d9223a42ed9edf3de1a30f4 nakasig-jdq39-factory-0798439d.tgz
bb824d449f44d2ad43c5d2a463fe1244d2faf525 nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
f406ae9133c56200306d5c7d64d151f21e0be3c4 nakasig-jdq39/image-nakasig-jdq39.zip
MD5
ee8db1ed6ff1c007fe12136d4bc65cd8 nakasig-jdq39-factory-0798439d.tgz
276cb738e5b9e18a088b6a3eef8155ad nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
4cfa996b6513a7fa53db7cbfd1134396 nakasig-jdq39/image-nakasig-jdq39.zip
radio image is 16,777,216 bytes long
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
the google - provided instructions (flash-all.sh) have 10 second sleeps after the bootloader resets - are you waiting long enough?
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.17.0_1205.img
fastboot reboot-bootloader
sleep 10
Also - something to check since you are rebooting the bootloader - does the device show up correctly in the Windows device manager? (Sometimes with soft reboots I have found the need to pull the USB cable and plug it back in to the PC).

[Q] How to manually apply Android 4.4 update frm official factory image on to nexus 4

Hello,
I have recently bought the Nexus 4. Its running on official stock 4.3 JB, bootloader locked i.e. everything is stocked and never rooted.
As 4.4 update is not available OTA as of now(not in the coming few days), so how can i update my nexus 4 to 4.4???
I have downloaded the official factory image from google dev website. When i try to update it through adb, its not showing my device in the list when i issue adb devices command....please help me...!!
Your replies will be much appreciated if you help me solving my issue or if you can suggest me any other alternative method....!!

vinay28761 said:
Hello,
I have recently bought the Nexus 4. Its running on official stock 4.3 JB, bootloader locked i.e. everything is stocked and never rooted.
As 4.4 update is not available OTA as of now(not in the coming few days), so how can i update my nexus 4 to 4.4???
I have downloaded the official factory image from google dev website. When i try to update it through adb, its not showing my device in the list when i issue adb devices command....please help me...!!
Your replies will be much appreciated if you help me solving my issue or if you can suggest me any other alternative method....!!
Click to expand...
Click to collapse
Make sure you use the Google SDK drivers and not the default drivers Windows installs....that was my issue may work for you,

nnorton44 said:
Make sure you use the Google SDK drivers and not the default drivers Windows installs....that was my issue may work for you,
Click to expand...
Click to collapse
As mentioned in the screenshot, my nexus 4 is connected with USB debugging ON. As far as drivers are concerned, phone is geting detected in device manager, with USB debugging ON and OFF, both the ways.
After that when i open command prompt window, no adb command seems to work. When i run "adb devices" command(without using quotes), it doesn't show me my phone. I am using the google SDK drivers only, downloaded from google dev website. Kindly suggest.

But were those the drivers that windows installed for you when you plug the phone in, or did you manually choose the appropriate drivers?
It has been a while since I've been on Windows, so I'm not familar with the process. But what he is saying is important.

N1029676 said:
But were those the drivers that windows installed for you when you plug the phone in, or did you manually choose the appropriate drivers?
It has been a while since I've been on Windows, so I'm not familar with the process. But what he is saying is important.
Click to expand...
Click to collapse
Well i did some searching on various xda posts...found this cool and nice tutorial for nexus 4. Followed the exact procedure step by step.
Running Android KITKAT 4.4 ...Big Kudos to the senior moderator efrant for his excellent tutorial http://forum.xda-developers.com/showthread.php?t=2010312
Do check it out. I manually installed the drivers. But sadly adb is still not working.

Steps required to install 4.4 factory steps
@vinay28761
Here You are :
I would fully recommend unlocking your bootloader for this purpose, unlocking has many advantages and one disadvantage, that your waranty will be void, but if you do these steps correctly, you should be fine with it
1) Download the SDK from here : http://developer.android.com/sdk/index.html
2) Extract the folder to an appropriate location . I prefer C:/adt-bundle-windows-x86_64 , you will see sdk folder> platform-tools. This is the main folder, here u will get your fastboot and adb
3) Now when you first download the facctory image, it will be in .tgz file, Use 7-zip software (Google it) and extract it to the same folder where you have downloaded your factory image.
4) After extracting you will get .tar file, extract it again using 7 zip . All files will be extracted to a folder called occam-krt160o and you will get img files like bootloader-mako-makoz20i and radio img's . Now Copy these files namely : bootloader-mako-makoz20i , radio-mako-m9615a-cefwmazm-2.0.1700.84 and image-occam-krt16o.zip
5) Now copy the img files that i mentioned from the occam-krt160o folder and paste into platform-tools folder present in your adt bundle
For the connection part :
1) On the nexus 4 go to settings > about phone and tap on build number 2-3 times , it will say now you are a developer, now you should see a developer option in your setting menu, go into developer options and enable USB debugging.
2) Now go to storage option in the nexus 4 and tap on sought of options button present there it will say connection option or something like that when u tap it will ask MTP or PTP (basically two connection modes for your N4 when connecting to the PC), uncheck MTP
3) Now On your PC, go to device manager on you PC (Google it) and look for Nexus 4 , right click it and click uninstall and if a option is there to delete the drivers put a check on it or if there is no option just uninstall the phone.
4) Connect your phone via a USB cable it will say installing driver (It should install ADB by default).
For Unlocking bootloader connecting Fastboot and installing images.
* You will lose all data on the internal memory that is films,music, apps (Back it up )
1) Switch off your phone.
2)Hold the pwerbutton and volume down to enter into fastboot ( Phone should be connected to PC)
3) You will see a start button on top and droid icon like a repair tool ) . You will also see bootloader lock status
4) Now on your PC , browse to your platform-tools folder . hold shift-rightclick and open a command prompt.
5) Now type fastboot oem unlock on your command prompt . Now your bootloader is unlocked and all your data is wiped.
6) Now reboot your bootloader by : pressing volume down/up and press the power-button to select (when u browse by volume up/down it will show resrat bootloader or reboot bootloader)
7) After N4 comes back to your bootloader, Type in your command prompt :
fastboot flash bootloader bootloader-mako-makoz20i
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84
fastboot reboot-bootloader
fastboot -w update image-occam-krt16o
fastboot reboot-bootloader
Note: I recommend restarting the bootloader manually after flashing each image.
Now you should have a android 4,4 running on your nexus phone.
To install recovery on the N4 , Go to ClockWorkMod homepage ( Google it ) and choose N4 touch recovery download it and rename it as recovery and paste in to into platform-tools folder.
To flash type on your command prompt fastboot flash recovery recovery,img
You should have a CWM recovery now.

Abhiheart said:
@vinay28761
Here You are :
I would fully recommend unlocking your bootloader for this purpose, unlocking has many advantages and one disadvantage, that your waranty will be void, but if you do these steps correctly, you should be fine with it
1) Download the SDK from here : http://developer.android.com/sdk/index.html
2) Extract the folder to an appropriate location . I prefer C:/adt-bundle-windows-x86_64 , you will see sdk folder> platform-tools. This is the main folder, here u will get your fastboot and adb
3) Now when you first download the facctory image, it will be in .tgz file, Use 7-zip software (Google it) and extract it to the same folder where you have downloaded your factory image.
4) After extracting you will get .tar file, extract it again using 7 zip . All files will be extracted to a folder called occam-krt160o and you will get img files like bootloader-mako-makoz20i and radio img's . Now Copy these files namely : bootloader-mako-makoz20i , radio-mako-m9615a-cefwmazm-2.0.1700.84 and image-occam-krt16o.zip
5) Now copy the img files that i mentioned from the occam-krt160o folder and paste into platform-tools folder present in your adt bundle
For the connection part :
1) On the nexus 4 go to settings > about phone and tap on build number 2-3 times , it will say now you are a developer, now you should see a developer option in your setting menu, go into developer options and enable USB debugging.
2) Now go to storage option in the nexus 4 and tap on sought of options button present there it will say connection option or something like that when u tap it will ask MTP or PTP (basically two connection modes for your N4 when connecting to the PC), uncheck MTP
3) Now On your PC, go to device manager on you PC (Google it) and look for Nexus 4 , right click it and click uninstall and if a option is there to delete the drivers put a check on it or if there is no option just uninstall the phone.
4) Connect your phone via a USB cable it will say installing driver (It should install ADB by default).
For Unlocking bootloader connecting Fastboot and installing images.
* You will lose all data on the internal memory that is films,music, apps (Back it up )
1) Switch off your phone.
2)Hold the pwerbutton and volume down to enter into fastboot ( Phone should be connected to PC)
3) You will see a start button on top and droid icon like a repair tool ) . You will also see bootloader lock status
4) Now on your PC , browse to your platform-tools folder . hold shift-rightclick and open a command prompt.
5) Now type fastboot oem unlock on your command prompt . Now your bootloader is unlocked and all your data is wiped.
6) Now reboot your bootloader by : pressing volume down/up and press the power-button to select (when u browse by volume up/down it will show resrat bootloader or reboot bootloader)
7) After N4 comes back to your bootloader, Type in your command prompt :
fastboot flash bootloader bootloader-mako-makoz20i
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84
fastboot reboot-bootloader
fastboot -w update image-occam-krt16o
fastboot reboot-bootloader
Note: I recommend restarting the bootloader manually after flashing each image.
Now you should have a android 4,4 running on your nexus phone.
To install recovery on the N4 , Go to ClockWorkMod homepage ( Google it ) and choose N4 touch recovery download it and rename it as recovery and paste in to into platform-tools folder.
To flash type on your command prompt fastboot flash recovery recovery,img
You should have a CWM recovery now.
Click to expand...
Click to collapse
Thanks for your steps.....I already followed the tutorial http://forum.xda-developers.com/show....php?t=2010312 and running Android KitKat 4.4 now

vinay28761 said:
Thanks for your steps.....I already followed the tutorial http://forum.xda-developers.com/show....php?t=2010312 and running Android KitKat 4.4 now
Click to expand...
Click to collapse
i am golad you are now running KitKat but to be honest searching for the instructions that you found should of been the first thing you did prior to starting a thread. There are a few tutorials out there. Hopefully your next venture into android you will take a moment to search...
Glad you are now on 4.4 enjoy my friend

Hi can you not just use the flash all.bat file contained in the factory image files instead of flashing the images separately?
Sent from my Nexus 4 using Tapatalk

(Solved) Error while flashing 4.4 - failed to allocate memory
Tried installing KitKat on Nexus4. The package was downladed from google's page, the checksum verification was also fine. But when I tried to flash the the new firmware got the below error.
E:\kitkat\occam-krt16o>fastboot -w update image-occam-krt16o.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 717312552 bytes
error: update package missing system.img
If any of you have seen this before, let me know how to overcome this.
Thanks in advance!
EDIT: The issue was with the PC - It had low memory and thus failed to allocate memory. My initial thought was that it failed to allocate memory on the phone!

[GUIDE]LG G Pad 8.3 GPE (V510)(ROOT)(Recovery)(4.4.4 Sideload)(ROM)(GENERAL INFO)

How to Unlock, Root, Update, Install Custom Recovery, and ROM your LG G Pad 8.3 GPE (V510) ​
First off if you aren't already familiar with ADB and FASTBOOT, please take some time and read over this post (thanks @ricky310711 ).
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Drivers
Windows 7 -- MTP Installs automatically, ADB Bridge requires Google USB Driver
Windows XP -- MTP needs LG Drivers, ADB Bridge requires Google USB Driver
LG United Mobile Driver (from G2) -- Will install drivers to access G-Pad as MTP device
Google USB Debug Driver
Installing ADB Drivers
Windows
Right click on the device with the triangle (Probably named "LG V510") in device manager
Choose "Update Driver"
Choose "Browse My Computer for driver software"
Locate where the Google USB drivers extracted with the "Browse" button
Choose "Next"
You computer should pick the drivers up and install
Linux (Thanks @sleekmason )
This guide assumes you are in root for the commands, and have a basic understanding of the terminal. Use sudo if you wish. Part of this comes from this guide: http://avedo.net/773/install-adb-and-fastboot-under-linux/ part from this guide: http://bernaerts.dyndns.org/linux/75-debian/280-debian-wheezy-android-tools-adb-fastboot-qtadb and partly from this forum. I'm using i386 AntiX (debian pure), if you are using amd/64 bit you will need some dependencies:
Code:
dpkg --add-architecture i386
Code:
apt-get update ; apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
you will need to go into developer options to enable debugging on your device.
You will need to create the udev rules for your phone on your computer. use "lsusb" to find the manufactures code. it will show up as a nexus 4 device...interesting.
Create a folder /etc/udev/rules.d/99-android.rules you can use gedit if you like:
Code:
gedit /etc/udev/rules.d/99-android.rules
Put this inside and save, changing the manufactures code as neccesary, and changing "your-login" to your login name.
Code:
# Google Nexus devices
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", OWNER="your-login" # Google Nexus devices
## restart udev## #
Code:
service udev restart
I'm keeping this simple, so here we go! Use the above links as reference as neccesary.
1.
Code:
apt-get purge android-tools-adb android-tools-fastboot
##You shouldn't use adb from the repositories##
2. Down load the latest adb bundle from here: http://developer.android.com/sdk/index.html
3.
Code:
unzip adt-bundle-linux-x86-20131030.zip
4.
Code:
mv adt-bundle-linux-x86-20131030 /opt/android-sdk-linux-x86-20131030
## (other google products reside here. Also, this takes a minute or so on slow machines)##
5.
Code:
ln -s /opt/android-sdk-linux-x86-20131030/sdk/platform-tools/adb /usr/bin
##(this links to /usr/bin to make life easy)##
6.
Code:
ln -s /opt/android-sdk-linux-x86-20131030/sdk/platform-tools/fastboot /usr/bin
##(same)##
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
How-To
---------------------------------------
How to sideload the 4.4.2 Update
This should be quite simple:
Download the 4.4.2 OTA (Stolen from: This Thread)
Make sure you have USB Debugging enabled in Developer Options
Connect the device to your computer and make sure the drivers are installed
Code:
adb devices
Command your device to reboot into the recovery
Code:
adb reboot recovery
When the recovery loads you will see a red exclamation point, press and hold the power button, press the Vol. Up button, release both buttons
Make sure your device is connected
Code:
adb devices
You should see a list;
-Reboot System
-Apply Update from ADB
wipte data/factory reset
-wipe cache partition​
Choose "Apply Update from ADB"
Sideload the Update ZIP
Code:
adb sideload a0bd45922b5958a38acef76f577f527268ef90db.signed-KRT16O.L004_user-KOT49H.L004_user_update.zip
You should get a progress indicator and Status when complete
---------------------------------------
How to sideload the 4.4.4 Update
If you are running TWRP you can skip the steps below and simply restore this backup thanks to @djkinetic!
@cam30era reports problems sideloading this in the stock recovery, if you have problems try booting into TWRP to sideload the update:
Download the 4.4.4 OTA (Stolen from: This Thread)
Make sure you have USB Debugging enabled in Developer Options
Connect the device to your computer and make sure the drivers are installed
Code:
adb devices
Command your device to reboot into the recovery
Code:
adb reboot recovery
When the recovery loads you will see a red exclamation point, press and hold the power button, press the Vol. Up button, release both buttons
Make sure your device is connected
Code:
adb devices
You should see a list;
-Reboot System
-Apply Update from ADB
wipte data/factory reset
-wipe cache partition​
Choose "Apply Update from ADB"
Sideload the Update ZIP
Code:
adb sideload ff3c360e108c52aac952f10c3dd4c6c5ce66a3ce.signed-KOT49H.L004_user-KTU84P.L002_user_update.zip
You should get a progress indicator and Status when complete
---------------------------------------
How to Unlock Your Bootloader
(Note for Linux users: fastboot commands must be issued using sudo. Thanks: @akshunj )​
Make sure you have USB Debugging enabled in Developer Options
Connect the device to your computer and make sure the drivers are installed
Code:
adb devices
Command your device to reboot into the bootloader
Code:
adb reboot bootloader
Make sure your device is connected
Code:
fastboot devices
Command your device to unlock the bootloader
Code:
fastboot oem unlock
IMPORTANT:You WILL softbrick your device if you don't allow the device to fully reboot before flashing a custom recovery
If you didn't pay attention and loaded custom recovery before a full reboot:
Download the Stock Recovery(Thanks @autoprime)
Make sure your device is connected
Code:
adb devices
Reboot into the bootloader
Code:
adb reboot bootloader
Make sure your device is connected
Code:
fastboot devices
Boot the stock recovery live
Code:
fastboot boot C:\android\17-recovery.img
Let the stock recovery do its thing and then reboot
---------------------------------------
How to root the Stock ROM (Maintaining Stock Recovery for OTAs)
(Note for Linux users: fastboot commands must be issued using sudo. Thanks: @akshunj )​
Unlock the Bootloader
Reboot
Download the SuperSU ZIP from Chainfire to your SDCard
Connect the device to your computer and make sure the drivers are installed
Code:
adb devices
Reboot into the bootloader
Code:
adb reboot bootloader
Make sure your device is connected
Code:
fastboot devices
Boot a Custom Recovery live (TWRP; no cwm yet)
Code:
fastboot boot PALMAN.img
Press Install
Select the SuperSU ZIP file
Swipe to Confirm Flash
Reboot System
Have Fun!
---------------------------------------
How to Install Custom Recovery
IMPORTANT:You WILL softbrick your device if you don't allow the device to fully reboot after unlocking the bootloader.
(Note for Linux users: fastboot commands must be issued using sudo. Thanks: @akshunj )​
Download a custom recovery (TWRP; no CWM yet)
Unlock the Bootloader
Reboot
Connect the device to your computer and make sure the drivers are installed
Code:
adb devices
Reboot into the bootloader
Code:
adb reboot bootloader
Make sure your device is connected
Code:
fastboot devices
Flash the custom recovery of your choice
(Note: Some people have had issues flashing the recovery with the file named "PALMAN.img" if you have a problem rename it to "recovery.img") ​
Code:
fastboot flash recovery PALMAN.img
Reboot
---------------------------------------
Roll Your Own Kernel... BY @sleekmason
http://forum.xda-developers.com/showthread.php?t=2628951
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
General Info
---------------------------------------
LG G Pad 8.3 GPE Partitions
Per the KRT160 stock firmware released by @autoprime
0 - PrimaryGPT
1 - Modem
2 - sbl1
3 - sbl2
4 - sbl3
5 - rpm
6 - tz
7 - aboot
8 - sbl1b
9 - sbl2b
10 - sbl3b
11 - rpmb
12 - tzb
13 - abootb
14 - imgdata
15 - persist
16 - boot
17 - recovery
---------------------------------------
LG G Pad 8.3 GPE OTAs
KOT49H from KRT16O - http://android.clients.google.com/pa...ser_update.zip (thanks @oldblue910 and @munchy_cool)
I don't believe there are any custom ROMs available for the V510 yet, I'll keep adding things to this as they come up! This is my first guide, so if you have suggestions please feel free to message me!
THANKS TO:
@autoprime (for the stock partition images)
@Dees_Troy and TWRP for the custom recovery
@Chainfire for SuperSU
@ricky310711 for the great post on ADB and FASTBOOT
@sleekmason for teaching us how to roll our own kernel
The Whole Dev Community!
Mom And Dad
Santa Claus
The Toothfairy
Global Cooling
Free Market
Christopher Colombus

SAVED

Can you post a system dump and kernel please?

In step 5 of "How to Unlock Your Bootloader", I suppose it should be "fastboot oem unlock" instead of fastboot oem-unlock". Newbies may get stuck right there.

jim380 said:
In step 5 of "How to Unlock Your Bootloader", I suppose it should be "fastboot oem unlock" instead of fastboot oem-unlock". Newbies may get stuck right there.
Click to expand...
Click to collapse
you are correct, yes. there is no hyphen between oem and unlock.

Can't install LG USB Drivers
I have V-510. I went to LG's website and downloaded their mobile suite and when I click on the "install usb driver" I get a list of carriers and I choose USA/LGV500 and then install the driver but once I connect the pad with USB debugging enabled and I get a message that the driver wasn't installed.
Can someone post a link for the usb driver?

I got my replacement GPE. Followed instructions here and have the GPE rooted and the boot loader unlocked thanks to directions here. After doing the OEM unlock it pays to be patient and count to 30 or something and let the tablet completely reboot. I also let it update to 4.4.2 first.
Now we need the ElementalX kernel .
Thanks for the guide and support.
Sent from my Nexus 7 using Tapatalk 2

Still having problem with having my windows 7 install the driver when I turn the USB debug on. There are 2 locations under device manager showing V510, one is the portable device with properly installed driver from MS and the other under other devices with yellow triangle and no driver could be found status for that. Any clue how to fix that?

leggy said:
Still having problem with having my windows 7 install the driver when I turn the USB debug on. There are 2 locations under device manager showing V510, one is the portable device with properly installed driver from MS and the other under other devices with yellow triangle and no driver could be found status for that. Any clue how to fix that?
Click to expand...
Click to collapse
Try deleting the driver with the triangle, then reboot, plug in the G Pad and see if it will reinstall properly.

USB Drivers
woody1 said:
Try deleting the driver with the triangle, then reboot, plug in the G Pad and see if it will reinstall properly.
Click to expand...
Click to collapse
I have tried a few different drivers with no success. I have an HTC phone that works fine but ADB does not see the Q Pad. It has to be a driver issue. I have installed/uninstalled them multiple times with no success. I even uninstalled the HTC drivers to see if that was the problem, nope...
Ever tried multiple usb cables (ones I know work) and tried every USB port on my laptop, nothing!
Win 7 Home, LG G Pad 8.3 GPE w/ Android 4.4.2

jaho_dev said:
I have tried a few different drivers with no success. I have an HTC phone that works fine but ADB does not see the Q Pad. It has to be a driver issue. I have installed/uninstalled them multiple times with no success. I even uninstalled the HTC drivers to see if that was the problem, nope...
Ever tried multiple usb cables (ones I know work) and tried every USB port on my laptop, nothing!
Win 7 Home, LG G Pad 8.3 GPE w/ Android 4.4.2
Click to expand...
Click to collapse
The driver with the triangle is probably the ADB Composite bridge. Download the Google USB Driver and install it. Then
Right click on the device with the triangle in device manager
Choose "Update Driver"
Choose "Browse My Computer for driver software"
Locate where the Google USB drivers extracted with the "Browse" button
Choose "Next"
You computer should pick the drivers up and install

Bingo! Thank You!

Mixinitup4Christ said:
The driver with the triangle is probably the ADB Composite bridge. Download the Google USB Driver and install it. Then
Right click on the device with the triangle in device manager
Choose "Update Driver"
Choose "Browse My Computer for driver software"
Locate where the Google USB drivers extracted with the "Browse" button
Choose "Next"
You computer should pick the drivers up and install
Click to expand...
Click to collapse
This worked thank you.
However, I am still unable to root the device. I even tried the Kingo root but it failed. I must have messed with my device a lot. Willl try to factory reset

I successfully unlocked the bootloader and rooted. Installed customer recovery as well but do not know how to boot to recovery. On my Galaxy S3 I used to go to custom recovery by holding the power which gives me the option to boot to recovery
Thank you everyone for the help.

I use quick boot from the play store to boot to recovery or you can power off and hold the power and volume down after powering off and select boot to recovery.
Sent from my LG-V510 using Tapatalk 2

Thank you
Sent from my VS980 4G using Tapatalk

Google Updates
leggy said:
Thank you
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
After sideloading the V510 stock rom, will the LG G Pad will show V510 and get regular updates OTA as LG G Pad Google play edition?
Thanks,
Jagdeep

jsethi3 said:
After sideloading the V510 stock rom, will the LG G Pad will show V510 and get regular updates OTA as LG G Pad Google play edition?
Thanks,
Jagdeep
Click to expand...
Click to collapse
No. The GPE firmware from the 510 isn't compatible with the 500.

PhilDX said:
you are correct, yes. there is no hyphen between oem and unlock.
Click to expand...
Click to collapse
Thanks for this guide. Yes, this newbie got hung up there for a minute. Why not edit the OP to be correct?

windfrenzy said:
Thanks for this guide. Yes, this newbie got hung up there for a minute. Why not edit the OP to be correct?
Click to expand...
Click to collapse
Whoops, sorry everyone! Fixed now!!