Database Users

Before I scrap my phone...

Hi All,
I just bought a new Hero two days ago. Since then I performed the following steps:
1.) downloaded the kernel source from HTC
2.) Compiled a kernel.
3.) As root:
a.) adb push newBoot.img /sdcard
b.) # cat /dev/zero > /dev/mtd/mtd2
c.) #flash_image boot /sdcard/newBoot.img
I did not install a recovery image unfortunately.
So.. after doing those steps the phone reboots, and displays
"HTC". It doesn't progress past there.
things i've tried.
1.) Installed a known .img that works. Renamed Recovery-RA-1.5.2.img to /sdcard/newBoot.img
2.) Copied other images that might work to /sdcard/newBoot.img
3.) renamed an image to HERC[DIAG|IMG].zip
Any other ideas I can try? I can boot to fastboot screen. Just not sure what else to do before I scrap it.
Any suggestions welcome.

how long did you wait at the HTC screen? it can take up to 10 minutes after the first boot.

hmm.. I didn't wait more than 5 minutes... I'll give that a try and see what happens. Hopefully that's all there is to it....

or you can just download a stock RUU and flash that.. Will atleast get you back to stock.

OK I tried that.. but since I can't boot into linux, I cannot get any adb commands to respond.
Between the "htc" screen that goes nowhere and the
the fastboot screen, I'm not sure how to install it.
I keep getting a USB 170 error.
still waiting at the HTC screen.

Sitting at the "HTC" screen for over 20 minutes now.. So I'm assuming that it's not going to boot. I'll let it go for a few more minutes.
Is there a way to install the RUU image from the fastboot screen?

fred43 said:
Sitting at the "HTC" screen for over 20 minutes now.. So I'm assuming that it's not going to boot. I'll let it go for a few more minutes.
Is there a way to install the RUU image from the fastboot screen?
Click to expand...
Click to collapse
The phone just needs to be on and connected to the pc when you run the RUU.

I'm assuming by "on and connected" that adb commands need to work?
Unfortunately my phone has 2 states. fastboot, and "HTC" screen that I mentioned above. I am unable to run any adb commands in HTC screen mode ( NO USB device is detected.)
The only way I can detect a USB device is when the phone is in fastboot mode.

fred43 said:
I'm assuming by "on and connected" that adb commands need to work?
Unfortunately my phone has 2 states. fastboot, and "HTC" screen that I mentioned above. I am unable to run any adb commands in HTC screen mode ( NO USB device is detected.)
The only way I can detect a USB device is when the phone is in fastboot mode.
Click to expand...
Click to collapse
If you can get in to fastboot then you should be able to run RUU while booted up in to fastboot. If not then you should be able to flash either a boot.img or RA's recovery img while in fast boot. At that point you should be able to boot the phone or boot in to a recovery image and flash a rom.
Option 1) Copy Recovery-RA-1.5.2.img to your sdcard and do: fastboot boot /sdcard/Recovery-RA-1.5.2.img
Option 2) Download fresh rom (or any rom) and then extract the boot.img from the zip and copy it to your sdcard. And then fastboot boot /sdcard/boot.img
Option 3) You can TRY actually flashing an img through fastboot but I'm pretty sure it's disabled on our phones. fastboot flash recovery /sdcard/Recovery-RA-1.5.2.img
FYI - The kernel source available from HTC is for the GSM Hero, not CDMA. That's why you are having problems.
You can PM me if you have questions.

flipzmode said:
Option 1) Copy Recovery-RA-1.5.2.img to your sdcard and do: fastboot boot /sdcard/Recovery-RA-1.5.2.img
Click to expand...
Click to collapse
Ok this option looks promising. The problem I have is :
"cannot load '/sdcard/boot.img'"
running the command:
"fastboot boot /sdcard/boot.img" ( AS root on my linux machine )
Note: I can see the usb device with fastboot devices
I think this error is happening from the linux machine. I tried this command as a non-root user and got the same response.
flipzmode said:
FYI - The kernel source available from HTC is for the GSM Hero, not CDMA. That's why you are having problems.
Click to expand...
Click to collapse
Ah.. That is why. My original goal was to create a kernel module for the phone... looks like this could be challenging without the correct sources.

Ok this option looks promising. The problem I have is :
"cannot load '/sdcard/boot.img'"
running the command:
"fastboot boot /sdcard/boot.img" ( AS root on my linux machine )
Note: I can see the usb device with fastboot devices
Click to expand...
Click to collapse
Ok try running it off of your computer then. fastboot boot /home/user/boot.img (wherever you actually have it)
Ah.. That is why. My original goal was to create a kernel module for the phone... looks like this could be challenging without the correct sources.
Click to expand...
Click to collapse
Yup. That's our exact problem and why we are somewhat limited on what we can do for modifying stuff.

With HBOOT-1.41.0000, the boot option is disabled apparently...
sudo ~/android/android-sdk-linux_86/tools/fastboot boot ./boot.img
downloading 'boot.img'... FAILED (remote: not allow)

Yea I knew that with our hboot the option to flash via fastboot was disabled, but I have been able to successfully boot through it. That's how I test my boot imgs. Other than trying the RUU while you are in fastboot it seems like it's pretty dead.
What happens if you boot in to the recovery partition? The stock one. Does adb see the phone then?

Well I just tested the RUU, 1.29 version. I got this error:
ERROR[140]: BOOTLOADER VERSION ERROR
The recovery partition ( default one) apparently doesn't exist just shows an
X or something with a phone. ( The default image ?)
What version of fastboot are you using? That seems to be my only hope at this point.

Is this a "with google" branded phone?
The fastboot I have is the one that came with the sdk for windows. It doesn't provide me with any type of version number.

Ok, I got it to boot off of one of the later fresh.zip's boot.img.
The default version of hboot has most options of fastboot disabled.
However, there is a way of getting around it.
1.) boot into fastboot mode
2.) fastboot -s $DEVICEID oem rebootRUU
3.) fastboot whatever, upgrade, boot etc all seem to work.
Still waiting on the boot... still stuck at the "HTC" screen. hopefully it will boot up eventually.

fred43 said:
2.) fastboot -s $DEVICEID oem rebootRUU
Click to expand...
Click to collapse
I knew that command worked with adb (that's how you do a manual RUU) but I didn't think it worked in fastboot. Good to know.
See if you can adb now that it's running off a proper boot.img.

Well looks like I spoke to soon. The boot option apparently ignores the file argument while in oem mode.

OK. so I'm back at square one. IN RUU mode, is there anything I can do?
Can I get a stock image later than 1.29 somewhere? Something that will
pass the security check of the installer.

fred43 said:
OK. so I'm back at square one. IN RUU mode, is there anything I can do?
Can I get a stock image later than 1.29 somewhere? Something that will
pass the security check of the installer.
Click to expand...
Click to collapse
Not that has been made available, no. You didn't answer me earlier. Is your phone stamped "with google" on the back cover?

Fastboot

How do you guys boot to fastboot if you have turned your phone off? I mean the actual fastboot ("black Huawei logo") not the recovery and not the pink bootloader. I can get to it if I reboot my phone if I press reboot and then bootloader, but is it possible without it?

Seems like there is no other way. Right now I can start it in fastboot mode with "adb reboot bootloader" and the custom ROM I have on right now. If anyone wants details, post here.
-e-
Weird discovery I made. While trying to flashall it says the device is "swordfish"... If I flash system.img separately it says "no partition table exists". Anyone has used fastboot before?

Nice. With the new Android version, the product shows MSM7630_SURF. It now properly boots to fastboot without going to charging too, so thats an update.

Blefish said:
Seems like there is no other way. Right now I can start it in fastboot mode with "adb reboot bootloader" and the custom ROM I have on right now. If anyone wants details, post here.
Click to expand...
Click to collapse
Thanks! I was trying to set up my UDEV (51-android.rules) and your post helped me boot into the bootloader mode to get the right idVendor & idProduct codes.

Blefish said:
Seems like there is no other way. Right now I can start it in fastboot mode with "adb reboot bootloader" and the custom ROM I have on right now. If anyone wants details, post here.
-e-
Weird discovery I made. While trying to flashall it says the device is "swordfish"... If I flash system.img separately it says "no partition table exists". Anyone has used fastboot before?
Click to expand...
Click to collapse
I tried fastboot, but I just get a black screen with huawei logo. No any function, no adb connection, no menu entries or anything and no buttons work. And I can exit only by remove battery. Is this right?

dancer_69 said:
I tried fastboot, but I just get a black screen with huawei logo. No any function, no adb connection, no menu entries or anything and no buttons work. And I can exit only by remove battery. Is this right?
Click to expand...
Click to collapse
There's an external tool called fastboot which handles that. There you can reboot or even continue the boot.
Fastboot is broken as far as I know, no partition table exists.
Sent from my U8800

You mean the fastboot from adb tools which can used from command line? This cannot work because there isn' t adb connection on bootloader mode.
Or is another tool which can be flashed or something to device?

dancer_69 said:
You mean the fastboot from adb tools which can used from command line? This cannot work because there isn' t adb connection on bootloader mode.
Or is another tool which can be flashed or something to device?
Click to expand...
Click to collapse
I think you are confusing pink screen with fastboot/bootloader. The fastboot is the node where it stays in the Huawei logo.
Sent from my U8800

No, I know the difference. I get this screen, but nothing else. On my previous device, fastboot has some functions included flash rom, reboot and some else that I don't remember. I also could from adb to use fastboot command.
On X5 I just get this screen.

Maybe they disabled that in B522 too, I am not sure. It was bugged anyway. I only tested it on B138 and B518.

Yes, I have 522 and I thought this too. I've tried on B138 1-2 times and was the same huawei logo screen only too. I didn' t tested it more because I thought that just this mode is disabled and used pink mode only. In B138 sould appear something else on screen, or only commands from adb work?

[Q] No USB debugging, can I adb?

Back story: Nexus 7 2012 WiFi, unlocked, rooted, TWRP, ROM'd
Tried to stock to 4.3. Power + volume down = Android on his back. can scroll Start, Restart Bootloader, Recovery Mode, Power Off. Select anything but Power Off and "booting failed" pops up in top left corner.
Anyone.....Anywhere.....Any IDEAS?
Without access I can't turn on USB debugging. I am no pro, but I'm not new. I have spent days trying to breathe life into this dude and I am at my end.

You don't need debugging to use fastboot. Look at the sticky at the top that says how to restore a factory image or something like that.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
You don't need debugging to use fastboot. Look at the sticky at the top that says how to restore a factory image or something like that.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
Exactly, fastboot has absolutely nothing to do with a switch within Android such as that of USB debugging. You have two courses of action; either flash stock images as suggested or proceed to flash a custom recovery, from which you can flash any custom ROM.

let me try again...
Via terminal: adb finds no devices; fast boot returns with a number for a device found, but when you flash from fast boot... nothing actually happens. I assumed that USB debugging was a moot point, but it seems most of the direction's you read a always start with "turn on USB debugging". When I go through and type in erase this, reboot that it say failed. Is there any caveman way of replacing fast boot? As I said, the cable is good, the USB port is good, I have gone at it through both Windows 7 Pro 64bit and Linux Mint 15 and I believe I have tried every suggestion I could find on the web. I will check the sticky above as suggested but I am stumped.

Fastboot and adb are not cross compatible. You cannot expect adb commands to work work in fastboot just as you should not expect fastboot commands to work in adb.
You have not actually stated WHAT you have tried in fastboot. What commands are you typing and what files are you using? You ask how to replace fastboot yet that is not possible nor is it sane to even think to replace it. Fastboot is there for a reason.
Sent from my Galaxy Nexus

boot into recovery TWRP
goto advanced > adb sideload
on your pc command prompt goto adb (where ever your sdk is installed) and push the rom image to root directory
after that's done, cancel out of adb sideload and go back to main. do a wipe (factory reset, cache, dalvik cache, system) and go back to main.
click install and find the rom image (click internal storage on top)

Open Source Paul said:
Via terminal: adb finds no devices; fast boot returns with a number for a device found, but when you flash from fast boot... nothing actually happens. I assumed that USB debugging was a moot point, but it seems most of the direction's you read a always start with "turn on USB debugging". When I go through and type in erase this, reboot that it say failed. Is there any caveman way of replacing fast boot? As I said, the cable is good, the USB port is good, I have gone at it through both Windows 7 Pro 64bit and Linux Mint 15 and I believe I have tried every suggestion I could find on the web. I will check the sticky above as suggested but I am stumped.
Click to expand...
Click to collapse
Let us try, AGAIN. ADB and FASTBOOT are 2 DIFFERENT programs. Stop trying to use ADB to reinstall the OS. At the top of this page there is a sticky that literally holds your hand through the FASTBOOT command process. Read that. Forget for the time being that ADB exists. Think of it as ADB ONLY exists if you have a working OS. You currently don't so you NEED to use FASTBOOT.
Flashing a factory image using fastboot/restore to stock
> 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-jwr66v.zip

Stock Nexus 7 (2012) soft bricked

Hello all this is my first post here, please be nice
I have absolutely no knowledge of computing/ IT, but after tearing my hair for the past two days (and a lot of googling) I have come here hoping for a solution
I have a stock nexus (see I have learnt new terms) which is now soft bricked and stuck on the X screen
Been looking for solutions including nexus root kit but none have really helped
eg one solution says step 1: install latest android SDK (and in the process of installing I have to ensure usb debugging is turned on, too late already soft bricked)
I am assuming that I have failed because
I have not rooted the device
I have not enabled usb debugging
I have not enabled changes previously eg unlocking
I am however able to enter bootloader mode
I have cleared cache partition and also tried to factory reset but to no avail
Could some one please please help me as it is out of warranty

docians said:
Hello all this is my first post here, please be nice
I have absolutely no knowledge of computing/ IT, but after tearing my hair for the past two days (and a lot of googling) I have come here hoping for a solution
I have a stock nexus (see I have learnt new terms) which is now soft bricked and stuck on the X screen
Been looking for solutions including nexus root kit but none have really helped
eg one solution says step 1: install latest android SDK (and in the process of installing I have to ensure usb debugging is turned on, too late already soft bricked)
I am assuming that I have failed because
I have not rooted the device
I have not enabled usb debugging
I have not enabled changes previously eg unlocking
I am however able to enter bootloader mode
I have cleared cache partition and also tried to factory reset but to no avail
Could some one please please help me as it is out of warranty
Click to expand...
Click to collapse
flash factory image via fastboot, since you can access bootloader and already install adb debugging.. follow step 6 (6.you can verify...) onward from this post http://forum.xda-developers.com/showthread.php?p=32075129
Sent from my Nexus 7

usb debugging
dexviajiboy said:
flash factory image via fastboot, since you can access bootloader and already install adb debugging.. follow step 6 (6.you can verify...) onward from this post http://forum.xda-developers.com/showthread.php?p=32075129
Sent from my Nexus 7
Click to expand...
Click to collapse
Unfortunately I do not have usb debugging enabled
And my tablet is soft bricked
Is there a way around this?
Please any help is appreciated
thanks

Try this from youtube. I have also softbrick my nexus when ota to kitkat. Use this methods and it works. Also before flash the factory image, unlock your bootloader first. I think this method did not required to enable usb debuging.
http://m.youtube.com/watch?v=-E-EF0QC0Gc
I hope this will help
Sent from my Nexus 7 using xda premium

You don't need usb debugging enabled to flash images via fastboot -- you just need to be able to get into the bootloader screen.

unlock bootloader
deny_kei said:
Try this from youtube. I have also softbrick my nexus when ota to kitkat. Use this methods and it works. Also before flash the factory image, unlock your bootloader first. I think this method did not required to enable usb debuging.
I hope this will help
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the video
I have followed everything until it (the video) tells me that the process will only work if I unlock my bootloader
Now I can access my bootloader but it states Lock State- Locked
My difficulty is how do I unlock my bootloader as my nexus is stuck at boot loop
I have tried the unlock function on Rootkit, but it says I have to enable usb debugging
To summarise my understanding:
My nexus will get out of bootloop if I flash the ROM
To flash the ROM I have to unlock the bootloader (as per the video)
To unlock the bootloader I have to enable usb debugging (as per nexus root kit)
To enable usb debugging I have to get out of bootloop
To get out of bootloop I have to flash the ROM............
Any simple way of unlocking the bootloader on a soft bricked nexus?
Any help appreciated thanks

like jfmcbrayer said.. if you can access bootloader, you can flash via fastboot either you enabled or not usb debugging, the important thing fasboot can verify your device before start flashing..
Sent from my Nexus 7

bootloader locked
dexviajiboy said:
like jfmcbrayer said.. if you can access bootloader, you can flash via fastboot either you enabled or not usb debugging, the important thing fasboot can verify your device before start flashing..
Sent from my Nexus 7
Click to expand...
Click to collapse
Absolutely agree
However when I try to follow your instructions
> fastboot devices
# the following output should be returned
<device serial number> fastboot
I do not get a device serial number
I suspect it is because the bootloader is locked, the device will not be recognised
Happy to be proven wrong because I need a means to get my nexus working

docians said:
Absolutely agree
However when I try to follow your instructions
> fastboot devices
# the following output should be returned
<device serial number> fastboot
I do not get a device serial number
I suspect it is because the bootloader is locked, the device will not be recognised
Happy to be proven wrong because I need a means to get my nexus working
Click to expand...
Click to collapse
seen like you got problem with adb driver on you pc..
Sent from my Nexus 7

adb driver
dexviajiboy said:
seen like you got problem with adb driver on you pc..
Sent from my Nexus 7
Click to expand...
Click to collapse
Indeed! Perhaps because the first step in installing an adb driver in my pc is this:
1. Enable usb debugging on your device (found under Settings > Developer Options)
As I have been saying from the start
My nexus is stuck in boot loop
I do not have usb debugging enabled
Is there anyone who can help me with unlocking my bootloader (on my soft bricked stock nexus) so I can flash rom
Thanks in advance

docians said:
Indeed! Perhaps because the first step in installing an adb driver in my pc is this:
1. Enable usb debugging on your device (found under Settings > Developer Options)
As I have been saying from the start
My nexus is stuck in boot loop
I do not have usb debugging enabled
Is there anyone who can help me with unlocking my bootloader (on my soft bricked stock nexus) so I can flash rom
Thanks in advance
Click to expand...
Click to collapse
goodluck ?
Sent from my Nexus 7

bricked
dexviajiboy said:
goodluck ?
Sent from my Nexus 7
Click to expand...
Click to collapse
thanks bud
I will need all the luck in the world now that I have to deal with Asus/ google now that the tablet is out of warranty

docians said:
thanks bud
I will need all the luck in the world now that I have to deal with Asus/ google now that the tablet is out of warranty
Click to expand...
Click to collapse
dont you try flash factory with guide from this thread http://forum.xda-developers.com/showthread.php?t=1907796
pm me with part you stuck.. I'll try assist you

soft brick
dexviajiboy said:
dont you try flash factory with guide from this thread http://forum.xda-developers.com/showthread.php?t=1907796
pm me with part you stuck.. I'll try assist you
Click to expand...
Click to collapse
just to be absolutely sure were on the same page I've copied all the instructions from your link
[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
1.Download and install 7-Zip - http://www.7-zip.org/download.html
2.Download the Nexus 7 factory image - https://developers.google.com/androi.../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)
3.Download and install the Java SE JDK - http://www.oracle.com/technetwork/ja...ads/index.html
4.Download and install the Android SDK - http://dl.google.com/android/installer_r21-windows.exe
5.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
6.Run the SDK Manager
7.Under Tools, check the box labeled "Android SDK Platform-tools" - this provides adb and fastboot
8.Under Extras, check the box labeled "Google USB Driver"
9.Press the "Install # packages..." button and follow the on-screen instructions.
10.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=bhA5C...yer_detailpage..
1.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!"
2.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
3.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
4.Use adb to boot the device to the bootloader:
Code:
> adb reboot-bootloader
5.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
6.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
7.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.
1.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.
2.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.
3.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
1.Put the device into fastboot mode by running the following adb command:
Code:
> adb reboot-bootloader
2.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
3.Follow the directions on the device, using the volume and power buttons to select "Yes". NOTE: this will wipe all personal data.
4.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.
5.If you are sending the device in for warranty work, you may want to re-lock the bootloader
Code:
> fastboot oem lock
6.Finally, reboot the device
Code:
> fastboot reboot
Click to expand...
Click to collapse
Following the thread this is precisely where I get stuck
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=bhA5C...yer_detailpage..
1.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!"
Will pm you with the same as I need your help in Driver Installation

docians said:
Following the thread this is precisely where I get stuck
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=bhA5C...yer_detailpage..
1.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!"
Click to expand...
Click to collapse
You're welcome, mate....
Installing drivers is not difficult, you must read the post by comminus carefully.
I tought it is too a boring part to film it....
@docians take your time to read step by step mate, that guide can help you to unbrick.
Guys, just be aware, that the drivers will have to be instaled two times: once for normal boot mode in OS, another time in fastboot mode.
What might confuse you: the ADB drivers get installed within the SDK and not as usual with downloaded drivers from the website of the manufacturer.

Did this end up being solved?
In the same situation where my Nexus 7 (2012) 4.4.4 is soft bricked and stuck in a bootloop.
Not sure how to go about installing the drivers. Just lost. :silly:

deanomalino said:
Did this end up being solved?
In the same situation where my Nexus 7 (2012) 4.4.4 is soft bricked and stuck in a bootloop.
Not sure how to go about installing the drivers. Just lost. :silly:
Click to expand...
Click to collapse
Yes, solved
You will find them in google, search for "google USB drivers for Windows"
Download the zip, unzip it and run the install/setup.exe
After that, boot your N7 into the bootloader mode and connect your tab with the USB cable and wait for 1 minute until it gets installed.
After that you will can execute all fastboot commands. Then just follow the guide by comminus how to flash factory image with fastboot.
tetakpatalked from N7100

tetakpatak said:
Yes, solved
You will find them in google, search for "google USB drivers for Windows"
Download the zip, unzip it and run the install/setup.exe
After that, boot your N7 into the bootloader mode and connect your tab with the USB cable and wait for 1 minute until it gets installed.
After that you will can execute all fastboot commands. Then just follow the guide by comminus how to flash factory image with fastboot.
tetakpatalked from N7100
Click to expand...
Click to collapse
Awesome, thanks.
Have run into another problem now.
Got to the part "fastboot flash bootloader bootloader-grouper-4.23.img"
And I get a message in cmd saying "FAILED <remote: <Invalid State>>"
Then on the tablet it says "Signiture Mismatch".
I'm using the 4.4.4 (KTU84P) from the Factory Images website if that's any help....

deanomalino said:
Awesome, thanks.
Have run into another problem now.
Got to the part "fastboot flash bootloader bootloader-grouper-4.23.img"
And I get a message in cmd saying "FAILED "
Then on the tablet it says "Signiture Mismatch".
I'm using the 4.4.4 (KTU84P) from the Factory Images website if that's any help....
Click to expand...
Click to collapse
Doesn't 4.4.4 image need a KitKat bootloader? Ver 4.23 was used for Jelly Bean 4.3 AMAIK
tetakpatalked from Nexus 7 flo

tetakpatak said:
Doesn't 4.4.4 image need a KitKat bootloader? Ver 4.23 was used for Jelly Bean 4.3 AMAIK
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Hmmm
Well that was the bootloader that was in the 4.4.4 download when I unzipped everything. :/
Is there meant to be another one?
Should I maybe just try and flash a Jelly Bean image onto the tablet then?
Thanks again for your help.

I softbricked my LS980 and cannot escape fastboot. Assistance Requested.

Had a problem with audio playback (volume always high no matter what). Decide to flash. PAC for my Sprint LS980. I see this:
Seems to be a lot of confusion so I'll clear things up..
ZV7->ZV8->ZVA is how the ota history goes, with ZVB on the way.
If you're on stock ZVA, your aboot (bootloader) may not be downgraded, in that case, use FreeGee from Play Store to install a recovery, it will automatically downgrade your aboot.
if you have the ZVA Radio, just flash furnace or dr87's kernel after you flash an AOSP ROM, all done.
Click to expand...
Click to collapse
Sorce: http://forum.xda-developers.com/showthread.php?t=2669074
Seeing the last sentance, I think that if I flash ZVA Radio, SlimKat ROM (the one that causes me problems) and then dr87's kernel I could try a ZVA experience. I flashed SlimKat again becuase I was going to change anyway, I wanted to try it with ZVA.
Tell myself why not, I do it.
Fails but I didnt pay much attention. I reboot.
Stuck in fastboot mode and cant escape. Recovery is a no-go.
Tried flashing both ZV7aboot.img and twrp2.6.3.0.img into their appropriate partitions (boot and recovery).
Still having problems, but now I cant do any button combination (except DownloadMode. Cant turn off) after ZV7aboot.img flash.
I dont want to erase my memory (~26GB of valuable data). Is there a way to flash a ZV8Radio.zip from fastboot? I think thats my problem, but Im not too sure. Just access to recovery would allow my to fix my problems.
Thanks anyone for any help! I think I really screwed myself over this time. Thanks everyone!
Edit: Anyone know where to get a boot.img and system.img for the Sprint LS980?

zv7_aboot.img isn't a boot.img, it's the bootloader. Use FreeGee to install twrp, it will handle the aboot for you. Then you can take advantage of the last sentence.

Savoca said:
zv7_aboot.img isn't a boot.img, it's the bootloader. Use FreeGee to install twrp, it will handle the aboot for you. Then you can take advantage of the last sentence.
Click to expand...
Click to collapse
I am stuck in fastboot. No recovery. Download mode is also accessable.
Which of the following would help:
* System.img and Boot.img (where to find em?)
* A kernel .img (Do they exist?)
* Flashing the ZV7 or 8 aboot.img oncemore with twrp.img again?
Thanks for coming to help! It means a lot.

RevolcFael4 said:
I am stuck in fastboot. No recovery. Download mode is also accessable.
Which of the following would help:
* System.img and Boot.img (where to find em?)
* A kernel .img (Do they exist?)
* Flashing the ZV7 or 8 aboot.img oncemore with twrp.img again?
Thanks for coming to help! It means a lot.
Click to expand...
Click to collapse
If you can boot into a rom, use FreeGee to install twrp. If you can't boot into rom and recovery, you need to flashtool.

Savoca said:
If you can boot into a rom, use FreeGee to install twrp. If you can't boot into rom and recovery, you need to flashtool.
Click to expand...
Click to collapse
Flashtools is asking for login and password. ?
Does this mean I have to wipe all user data in order to use it?
Edit: Do you know where System.img and Boot.img could be downloaded? I think its my only hope.

RevolcFael4 said:
Flashtools is asking for login and password. ?
Does this mean I have to wipe all user data in order to use it?
Edit: Do you know where System.img and Boot.img could be downloaded? I think its my only hope.
Click to expand...
Click to collapse
You didn't read the tutorial.
http://downloads.codefi.re/autoprime/LG/LG_G2

Savoca said:
You didn't read the tutorial.
http://downloads.codefi.re/autoprime/LG/LG_G2
Click to expand...
Click to collapse
Thanks for the link! That was extremely helpful.
What I did to gain access to twrp again was:
Download boot.img from the link.
Download aboot.img from link.
Download twrp.img (but this isnt necessary, file is already available on phone. No need.)
* Enter command 'fastboot flash boot boot.img'
* (If you hold power it starts showing LG Logo.)
* Go back to Fastboot. Enter command 'fastboot flash aboot aboot.img'
* Now TWRP access is regained! Phone doesnt boot normally, must flash ROM and stuff again.
Thanks a lot! This was an okay first fastboot experience.

Soft Bricked Sprint LS980?
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
---------- Post added at 02:59 AM ---------- Previous post was at 02:06 AM ----------
x_lord said:
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
Click to expand...
Click to collapse
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!

x_lord said:
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
Click to expand...
Click to collapse
Sorry for not replying, but I see you managed to fix your problem. All you needed to do was download .img files, then enter commands through fastboot. Although it is slightly more complicated than that, its the rough outline of what needs to be done to fix it. Nice work fixing your problem. I came back to this thread to remind myself of the commands that need to be entered (My comments help myself).
I think I am just going to copy-paste the quoted box above if anyone needs instructions how to do this. Thanks for the quick guide I can use to help others!

bricked , simple fix?
x_lord said:
Hello, I'm having a similar problem. I haven't had a phone for a couple years since tinkering with my Evo and thought I still knew what I was doing with my new G2. That proved to be incorrect.
I had it semi rooted. (I followed the instructions using Ioroot and Kingo) I wasn't able to change APN and use GSM for Metro PCS
After reading up about the spark patch I followed a tutorial (not very well obviously) and managed to get the phone will it will no longer boot.
I can get it into bootloader, and a frozen in download mode. otherwise it just hangs at the LG logo.
Is there a way to recover from bootloader?
I copied twrp-2.6.3.2-g2spr.img and zv7-aboot.img to the phone and did the following.
Here are the commands I used with the guide. I looks like I was using 2 different guides at once..... :/
Originally Posted by darkpoe View Post
This phone does not use Mass storage mode, it uses MTP, you will see it as a phone inside windows explorer and when you click into it you will see "internal storage" this internal storage is what I am referring to as the root of the sdcard (as they are as well)
Also, dont blame me if your phone dies, all this stuff will void your warranty of your phone and your toaster!
Hit the build number under about phone --> software until developer mode is enabled
goto developer mode turn on mtp mode
go download twrp from there site http://www.teamw.in/project/twrp2/197
I used kingo but cant link on xda ,, google it .. its on cnet as well
get http://koush.com/post/universal-adb-driver install (works on all windows)
get http://www.xda-developers.com/androi...oot-installer/has good quick adb install it
copy the downloaded openrecovery for sprint onto the phone directly into the "root" folder (root folder being like when you look at yoru C: drive in windows explorer that is the root folder under linux), when you plug into the pc, make sure in mtp mode
with phone still plugged in run kingo and root it
it will reboot
with phone plugged in run "adb usb" from command prompt on pc (from the link for adb that it installed, it will open a command prompt for you in the proper folder when you click it)
approve adb connection on phone
then run "adb shell" from command prompt on pc
type su, approve it on phone
paste this next line exactly at the prompt
********** this is the line I used from a different guide ***** dd if=/sdcard/zv7-aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/openrecovery-twrp-2.6.3.2-g2spr.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
let it flash
it will say bytes copied and you will be good
type reboot inside the shell
the phone will reboot
I use goo manager from play store to boot into recovery, I dont even know the key combo for it yet.
Any help would be appreciated, thank you.
---------- Post added at 02:59 AM ---------- Previous post was at 02:06 AM ----------
Found this: Worked like a charm.
–]rdsqc22 2 points 23 days ago
Alright, sorry to comment on something 3 months old, but I just had this problem and managed to solve it.
When in the mode described above, you are still able to use Fastboot. Get a linux computer and install fastboot.
Then, go here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zvc_partitions
Download the images for laf, aboot, boot, and recovery.
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-aboot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
This fixed the problem for me. Good luck!
Click to expand...
Click to collapse
this process (which i got from a different thread originally)
bricked my phone Lg G2 (Ls 980 sprint 32 gb)
i was on remote connection with my friend attempting all kinds of flashes (mostly custom roms and recoveries)
what he did
he FIRST flashboot erase aboot
and then erased all the other files
foolishly he then used fastboot reboot BEFORE reflashing the necessary images
this leaves me with a device that is practically 100% empty all hardware no software
i have no response no life not even a backlight EXCEPT
i can plug into windows and see Qdloader9008 is connected comport 3
and i can communicate with the device on ubuntu terminal although im not too farmiliar with terminal syntax so im not having much luck
im convinced it is as simple as reflashing at least a working recovery or download mode from which i can install everything else i nee
between QPST, Terminal, and or some other method
sorry for Noob ish ness
any help would be appreciated even if just help with a better understanding of what to do next
payment is possible

True2This said:
this process (which i got from a different thread originally)
bricked my phone Lg G2 (Ls 980 sprint 32 gb)
i was on remote connection with my friend attempting all kinds of flashes (mostly custom roms and recoveries)
what he did
he FIRST flashboot erase aboot
and then erased all the other files
foolishly he then used fastboot reboot BEFORE reflashing the necessary images
this leaves me with a device that is practically 100% empty all hardware no software
i have no response no life not even a backlight EXCEPT
i can plug into windows and see Qdloader9008 is connected comport 3
and i can communicate with the device on ubuntu terminal although im not too farmiliar with terminal syntax so im not having much luck
im convinced it is as simple as reflashing at least a working recovery or download mode from which i can install everything else i nee
between QPST, Terminal, and or some other method
sorry for Noob ish ness
any help would be appreciated even if just help with a better understanding of what to do next
payment is possible
Click to expand...
Click to collapse
Sorry, I barely understood what to do originally. What you have to do next is to reflash the aboot/boot/ whatever partitions but getting to that position might be difficult. Maybe some sort of command would allow you to connect to it oncemore?
Sorry, try to look into it more and see if a dev could help. Try posting something in /r/lgg2 but then again I cant be certain anything would happen. Good luck!

Easy guide
Since the problem keeps happening to people heres a quick tutorial I made.
Download and install this (PC only?)
Now go here. (D802) (D800) (LS980) (VS980) (D803) (Device tree/others)Download the images for laf, aboot, boot, and recovery.
Place the 4 .img files in the same folder. Control right click in that folded and open terminal. If this isn't how you open terminal in a folder search"how to open terminal in a folder".
(NOTE: Commands below will differ from the file names. Change the values in the parenthesis to match the files, HOWEVER, do not type the parenthesis into the terminal prompt! It will not work if you do.)
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot (6-boot.img)
fastboot flash aboot (4-aboot.img)
fastboot flash recovery (10-recovery.img)
fastboot flash laf (11-laf.img)
fastboot reboot
You should be fine now!

Unbrick Ls980 formatting partitions
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing

RevolcFael4 said:
Since the problem keeps happening to people heres a quick tutorial I made.
Download and install this (PC only?)
Now go here. (D802) (D800) (LS980) (VS980) (D803) (Device tree/others)Download the images for laf, aboot, boot, and recovery.
Place the 4 .img files in the same folder. Control right click in that folded and open terminal. If this isn't how you open terminal in a folder search"how to open terminal in a folder".
(NOTE: Commands below will differ from the file names. Change the values in the parenthesis to match the files, HOWEVER, do not type the parenthesis into the terminal prompt! It will not work if you do.)
type the following commands in fastboot:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot (6-boot.img)
fastboot flash aboot (4-aboot.img)
fastboot flash recovery (10-recovery.img)
fastboot flash laf (11-laf.img)
fastboot reboot
You should be fine now!
Click to expand...
Click to collapse
i tried this with almost all model files but still on fastboot any other option?>

I want to say thank you so much for this thread. Just got a new (refurb) G2 switching carriers to T-Mo and my idiot self used the wrong root program and soft bricked to fastboot. 4 .img files later and a few commands and I don't think I've ever been so happy to see a download screen on a phone...

juancho8207 said:
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
Click to expand...
Click to collapse
GREAT, You are a life saver :laugh:

juancho8207 said:
Do this: (only for LS980)
1. Download the adb.zip file
2. Unzip in you computer the adb.zip file
3. Connect your phone LS980 to your computer
4. Run "particiones lg g2.bat"
5. Enter in download mode and flash the phone
6. enjoy your phone
Link of download
https://drive.google.com/file/d/0B6VmAym2TGdIRGJmSXFqdm84NU0/view?usp=sharing
Click to expand...
Click to collapse
wow.. worked flawlessly... thank you very much :good::good::laugh::laugh: