Database Users

[GUIDE] Backup of your BCT AND Partition with NVFLASH on the gtab

** UPDATED WITH .BCT saving, include USB as well as NVFLASH just copy in
** 1 dir, run the batch and keep those you may need them one day
** Read the batch file for more info
It is clear for me is that it is not a perfect solution to use nvflash with images that you do not know the source.
The tegra S.O.C. use the information from a file stored in partition#2 to configure some low level setting like flash memory chip speed, total memory installed, video memory installed, flash type etc. As an example, if for some reason a batch of tablet is built with more memory then the .bct files will need to be changed accordingly
It is already confirmed that there's at least 2 different type of hardware. (2 different images by bekit do not use the same .bct configuration)
When flashing after a full wipe after using the create command, nvflash read the .bct configuration files and store it in the partition #2 on the tablet, bct files are created by the manufacturer using a tool from nvdia called buildbct. They are not writen during regular nvflash (where the partition are not re-created)
This also mean it is MUCH safer to NOT replace the partition 2 when nvflashing a device... (the hardware configuration would not be touched).
This batch files will work under windows and will not modify your tablet in anyway
please make sure you use the nvflash tools that is 151K there's an older and smaller one in some package, it will output binary inside the partition.txt instead of plain text. The version 2 include everything you need to backup the device under windows
Thanks to the various poster of thread about nvflash for the correct command THEY did the hard work not me !
To Restore individual partition the command is
"nvflash.exe" --bl bootloader.bin --download X partX.img
where X is the partition number you wish to flash, as stated you can also use your backup from clockwork mod for partition 11 restore.
this will not work for partition below 4
P.S.
I am not trying to start a debate on the validity of the current recovery (thumb-up to the guy who offered those!) They are valid for MOST device however
if you do have a different device this will alleviate any issue that may happen with nvflash restore.
see 2 post below for full restore info

Hi,
I know that the partitiontable shows a partition named "BCT", but is there also something else, perhaps flashed into the SOC itself that is referred to as "the BCT"?
The reason for the question is that nvflash has a setbct and a getbct command, separate from the read and download commands, which work with the partitions.
Jim

Reserved
(will be completed a bit later)

so, we possibly share more internals with the 10s than previously expected? maybe... can we get this thing to dual boot in the future??

10roller said:
so, we possibly share more internals with the 10s than previously expected? maybe... can we get this thing to dual boot in the future??
Click to expand...
Click to collapse
My guess is yes, the platform of the ac100 laptop by toshiba is tegra based and they do it!

P00r said:
The set bct command probably write the 4080 byte to the partition named bct in the cfg, I have yet to test flashing a dummy FF filled partition with the command to confirm the flash.bct get writen there
So in fact when you restore with the nvflash restore images from bekit I think you are actually writing it twice... (it is in the image and you telling the nvflash to create it) but I have not confirmed this yet
Once the bct info is there, the SOC read his configuration there, as well as the ODM info, I have not found a way to use --getbct that reads back the BCT from mass storage yet...
I am not sure either why there's so many section being flashed it should work with only a few of those (I plan to test this) since nvflash is simply puting those one after the other. It make sense only sense for a dual booting unit
Click to expand...
Click to collapse
Hi,
I was able to get --getbct to output a 2048 byte file awhile ago. I think I had posted about it, but, sorry, I don't remember which thread. The only thing I vaguely remember was that I had to use some unobvious combination of parameters. Also, I think that it only worked right after pushing the bootloader.bin. If I find my post, I'll provide a link.
Jim

Thanks OP, I like the idea of being able to back up the partitions directly from my tablet so I know I'm restoring the proper thing should I ever have to resort to that.
Just starting to get into modding this thing after it showed up from Woot yesterday, been planning on buying one for quite some time to compliment my Epic 4g and when the woot sale dropped I had to jump on it. So far all I have done is flash clockwork, and make a nandroid backup with that. Also doing this backup method now.
So have you actually done a successful restore using this method?

so is it possible to back up your original hardware configuration and restore it when you got problems???

Yes and NO, I have error reading partition #11 (system) on my tablet (bad block)
if I use it as is for restore, it doesn't restore and boot, however replacing this partition with clockwork system.img backup give me back a full working tablet.
I can also reboot into recovery and restore from there.

Letters and numbers oh my
I ran the backup on my new replacement GTab yesterday. I had a size mismatch on partition 5, everything else backed up properly. Also, my partition 7 is BLO and partition 6 is MSC. Thanks for the script and capability.
Mike

P00r said:
This also mean it is MUCH safer to NOT replace the partition 2 when nvflashing a device... (the hardware configuration would not be touched). I will post later on how to flash back those if someone request it...
Click to expand...
Click to collapse
Instructions on how to flash back using this would be great. I'd like to have the option to do so if I need to, but haven't gotten familiar enough with nvflash yet to figure it out on my own.

iamchocho said:
Instructions on how to flash back using this would be great. I'd like to have the option to do so if I need to, but haven't gotten familiar enough with nvflash yet to figure it out on my own.
Click to expand...
Click to collapse
You can flash back the partition using
"nvflash.exe" --bl bootloader.bin --download X partX.img
where X is the partition number you wish to flash, as stated you can also use your backup from clockwork mod for partition 11 restore.
If needed you can use the nvflash format kit prior to restoring however it would be better to use your own .bct with that option

Getting stuck at partition 7.

xkwwwx said:
Getting stuck at partition 7.
Click to expand...
Click to collapse
What is the error you are getting ?

stock recovery image
Thank you very much for the sharing this.
Now I have 10 img files (part-2 to part-11)... wich one is the stock recovery image? I did this before installing clockwork mod...
Thanks!

I think this is fantastic. Gives us a chance to backup our gtab before deciding to try a new rom. I tried this today in the hopes to backup and then install the flashback HC rom. But unfortuntaly it stopped on image 7, as xkwwwx has also mentioned. The message seemed to be a issue with the size expected of the image as to what was received. Ill try and copy the message.
"nvflash.exe" -r --read 7 part-7.img
nvflash started
[resume mode]
receiving file: part-7.img, expected size: 16777216 bytes
/ 131072/16777216 bytes received
At that point it stops, and i have to control c to exit the batch file. Id love to be able to backup with this pls, so i can try another rom, and know i can use this to return to this rom if i dont like the new one, any chance this can be resolved pls ?
Was also wondering if some form of GUI maybe of benifit, i know alot of people feel wary of NVFlash, perhaps with a GUI people would feel more comfortable using it. Maybe a simple screen with a backup and restore set of buttons ?

P00r, any chance you can help mate ? Cant use this unfortunatly because of the image size issue.

Icedvoco said:
P00r, any chance you can help mate ? Cant use this unfortunatly because of the image size issue.
Click to expand...
Click to collapse
This mean you probably have a bad block in this section, try skipping it to get the other parts first. this is not a major issue, you may also encounter one in the last data section (my tablet has a few byte less than the regular one)
For the data partition you can substitute the cwm images
Also try using a different bootloader and nvflash this can help even shorter usb cable or a different one can help
The part that you can read is probably usable for a restore anyway
Bad block are not unusual in flash and I have seen a few with this, ideally and usually it's located at the end, you could try using the format image a few time it could be a stuck byte and writing different data can revive it (format write FF all over)

P00r said:
This mean you probably have a bad block in this section, try skipping it to get the other parts first. this is not a major issue, you may also encounter one in the last data section (my tablet has a few byte less than the regular one)
For the data partition you can substitute the cwm images
Also try using a different bootloader and nvflash this can help even shorter usb cable or a different one can help
The part that you can read is probably usable for a restore anyway
Bad block are not unusual in flash and I have seen a few with this, ideally and usually it's located at the end, you could try using the format image a few time it could be a stuck byte and writing different data can revive it (format write FF all over)
Click to expand...
Click to collapse
Bad blocks may be common, but bad blocks in the exact same spot probably not. I get the exact same thing:
"nvflash.exe" -r --read 7 part-7.img
Nvflash started
[resume mode]
receiving file: part-7.img, expected size: 16777216 bytes
/ 131072/16777216 bytes received
Any other thoughts on this?

Maybe someone here knows,
So with NVflashing, I've found only one file that has the alternative BCT (it's a tnt1.0 rom on BL1.1) and no other NVflash file sets work without causing a APX bootloop.
This is the NVflash file set that works for me http://db.tt/FvSeAZj
Ive read it was made when someone was trying to configure for the hardware variations.
Now is it possible to take my backup and insert just the files needed into another NVflash file set?

[Q] How to recover Acer a500 without any backup? NEED HELP!!

My husbands Acer a500 screen froze when he was playing Zimga a poker game when this happened.
He believes he had ICS but he is not sure of anything speciffic.
He doesn't have any type of backup.
He never had it connected to the computer.
We tried the factory reset.
We tried the hard reset.
We cleaned the cache & whatnot...
Nothing helps.
I've tried to use the GUIDE: Recovering Recovery/Obtaining SKB
Of course we only option we have, because nothing was ever back up, connected to a computer. I downloaded unbumtu 12.04 and installed it onto my laptop.
The requirements:
-ubuntu 12.04
-micro USB cable
-paper clip ....
I also made sure I installed gcc, lsusb, libusb-1.0-dev, & libusb-1.0.x
I get it to show on the desktop ...
I type in: sudo su
Then: gcc apx.c -o apx -lusb-1.0
I end up with an errors.
If I remember correctly it says that line 4 and line 5 of EPPE code was in errors.
The another time it states...
Then it stats su: invalid option -- 'o'
I am by all no means a computer code writer, and hope someone will help me solve this issue.
I just can't afford sending the tablet back to Acer to be fixed.
I even tried flashing the information on the micro SD card, but I believe since his tablet wasn't connected ever to a computer things aren't running as smoothly as I would like.
I've downloaded nvFlash, blackthud3r, and many Roms.
I.ve even tried to flash a few with no luck. Mister Android has fallen and can't get up with the RED triangle and all.
I can get the tablet in Apx mode.
Also I can get the screen with the Fastboot...
I've tried all the tricks with the volume up and power button and toggle switch, AND/OR the volume down button and toggle.
But without the UIP or CPUID those items aren't doing me any good.
The tablet was only updated the old fashioned way. No customized anything.
Hubby mainly used it to get email and play pocker over the internet with it.
Not sure what other information you need, but I hope someone could get me out of this MISERY!
Been messing with it for over a week trying to read and get as much information about others having simular situations.
Thank you in advance & Hope to hear from you SOON!
We've even tried doing things in different computers...:crying:

radarbill said:
My husbands Acer a500 screen froze when he was playing Zimga a poker game when this happened.
He believes he had ICS but he is not sure of anything speciffic.
He doesn't have any type of backup.
Click to expand...
Click to collapse
Well, seeing it a stock tab, not a lot of options.
I would try this, here is a link where I gathered 4 500 ICS updates. Note that I named them with build numbers to keep things in order.
Rename one of the files to only "update.zip" (remove the build number in other words).
With the tab off, hold VOL+ and PWR until you see the update start to install, then release both.
Now, if one of them doesn't complete, then try the other. Hopefully one of them completes the install and boots the tablet.
Here's the link;
http://forum.xda-developers.com/showpost.php?p=31323893&postcount=8
MD

How to recover Acer a500 without any backup? Need Help?
Moscow Desire said:
Well, seeing it a stock tab, not a lot of options.
I would try this, here is a link where I gathered 4 500 ICS updates. Note that I named them with build numbers to keep things in order.
Rename one of the files to only "update.zip" (remove the build number in other words).
With the tab off, hold VOL+ and PWR until you see the update start to install, then release both.
Now, if one of them doesn't complete, then try the other. Hopefully one of them completes the install and boots the tablet.
Here's the link;
http://forum.xda-developers.com/showpost.php?p=31323893&postcount=8
MD
Click to expand...
Click to collapse
I appreciate you getting back so quickly.
I've already tried these.
I also tried most of these from this web page.
http://forum.xda-developers.com/showthread.php?t=1816560
Nothing seems to work.
There was a couple of them that would install about 25% but then android would keel over and the red triangle of death took over.
I would appreciate if you had any other suggestions, or if anyone else did.
There has to something I can do?!?

Well, without having the UID number, I think NVFlash is out of the question. Usually we get these quite simply when the tab is operating.
There is a Linux solution, to get UID, but I'm not a linux guy. There's a thread about UID, I think in the dev section. In there are steps to get it through Linux I believe.
With the UID, I think we can run TimmyDeans rollback tool. But as far as I know, you have to have the UID number.
MD

radarbill said:
I type in: sudo su
Then: gcc apx.c -o apx -lusb-1.0
I end up with an errors.
If I remember correctly it says that line 4 and line 5 of EPPE code was in errors.
The another time it states...
Then it stats su: invalid option -- 'o'
Click to expand...
Click to collapse
Please post the the commands you run and the exact result you get, it is hard to tell what went wrong without knowing exactly what you did and exactly what results you got.
Just a copy of the terminal buffer as it is would be good.
Moscow Desire said:
There is a Linux solution, to get UID, but I'm not a linux guy.
Click to expand...
Click to collapse
I have posted code for two Windows variants as well, one using libusb-win32 and one using the winusb driver delivered by Acer.
It can be found in the [GUIDE] Recovering Recovery/Obtaining SKB thread.

solved thankyou all
eppeP said:
Please post the the commands you run and the exact result you get, it is hard to tell what went wrong without knowing exactly what you did and exactly what results you got.
Just a copy of the terminal buffer as it is would be good.
I have posted code for two Windows variants as well, one using libusb-win32 and one using the winusb driver delivered by Acer.
It can be found in the [GUIDE] Recovering Recovery/Obtaining SKB thread.
Click to expand...
Click to collapse
well we ended up getting a new mobo and that did the trick. so thankyou one and all

[Q] TF101 has 16GB after flashing instead of 32GB

Hi Everyone,
after experiencing the reboot problem and then acceidentaly bricking the tablet I managed to unbrick my tablet (or better a friend managed).
Now though, the storage is 16GB instead of 32GB
My question now: how can I get the tablet back to 32GB?
Thanks for the help

I think you probably need to update either the transformer.bct file or odmdata for the 32gb version. I *believe* that these set things like memory size and other hardware parameters, although I'm not sure which one controls what. Unfortunately, I don't know where you would find these either. Maybe if you ask nicely and ask the right people at ASUS, they might send it to you.
EDIT- It's probably the bct. I forgot there is a getbct command in nvflash- you could ask someone who has a working 32gb version to extract theirs and see if it works for you. Note there are no guarantees that this will work since nvflash might not be fully implemented on the tf. You'll probably need to get comfortable with the command line. Prepackages scripts and one click solutions will probably not work in this case.
Code:
--getbct
reads back the BCT from mass storage
--setbct
updates the chip specific settings of the BCT in mass storage to
the bct supplied,used with --create, should not be with --read,and
--format(delete)_all,format(delete)_partition,--download, and--read
http://androidroot.mobi/technical/tf-secure-boot-key/
Code:
In order to get a working (e.g. --create) nvflash, we need a few bits of information as well as some files:
Secure Boot Key
[B] BCT file (boot device setup, ram configuration and a bit more)[/B]
ODM data (board-specific bit-field specifying various board settings. *Needs* to be correct
flash.cfg (e.g. list of settings and names/identifiers of partitions.

So I can't just re-flash nvflash with the proper settings? just seems a bit easier
On another note, does anybody have a working bct file? :fingers-crossed:

I think the proper settings are in the bct file.

Thanks for the help. I have found in other sources that it seems to be indeed in the bct file, so that is confirmed
Unfortunatly, that is all I could find out till now
I am sort of stuck on now getting a bct file for a TF101 with 32GB. Either that, or I am not copying it over properly. I am sort of at a lost here. I would appreciate any help

Bricked my LG G2 D802, please someone help me, I have no idea what to do next.

Hello!
I have rooted my phone today. i wanted to install some rom but first I tried to install TWRP so I can back it up. I tried a few different methods and tools, but nothing worked. Eventually I followed this tutorial: http://www.android.gs/install-twrp-recovery-lg-g2/ (I don't know if I'm allowed to posts links here...) about 5 times because everytime I forgot something. It still didn't work so I just give up. I re-booted my phone and I noticed some error in upper left corner, along with LG logo. But I still could boot it if I keep pressing power button. After that, some update showed up (I don't know which... :/) so i installed it and re-booted. And then there was error "secure booting error boot certification verify" and nothing works. I tried every combinations possible but I still cant boot it. The only thing that shows up is that error and LG logo and then it goes black (but it's still on). When I connect it to my PC it creates 12 empty 'local disk' and one 63,9 mb local disk (with folder 'image' and files in it). I tried this already: http://forum.xda-developers.com/showthread.php?t=2582142 using VirtualBox + Unbuntu but i'm stuck at the beginning. When I type "ls /dev/sd*" it only shows me the first " /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 " and nothing else...
I'm seriously pissed off at me right now, last time I bricked my phone 2 years ago and I promised myself not to ever play with any of this stuff and now I got my new phone and screw it up next day. Yeah I got it for one day and I screwed it up already.
I'm freaking out, can someone please help me?

It might be you have sent the recovery Image to the wrong partition, in the mean time you will have to read what you have done, and maybe see if you selected something incorrectly, you may have to get another phone while you see if you can fix the broken one. I take it you have tried all boot options and no reset is available ?
I recently broke a working phone it is annoying, but you live and learn.
Sent from my Nexus 7 using XDA Free mobile app

prophice said:
Hello!
I have rooted my phone today. i wanted to install some rom but first I tried to install TWRP so I can back it up. I tried a few different methods and tools, but nothing worked. Eventually I followed this tutorial: http://www.android.gs/install-twrp-recovery-lg-g2/ (I don't know if I'm allowed to posts links here...) about 5 times because everytime I forgot something. It still didn't work so I just give up. I re-booted my phone and I noticed some error in upper left corner, along with LG logo. But I still could boot it if I keep pressing power button. After that, some update showed up (I don't know which... :/) so i installed it and re-booted. And then there was error "secure booting error boot certification verify" and nothing works. I tried every combinations possible but I still cant boot it. The only thing that shows up is that error and LG logo and then it goes black (but it's still on). When I connect it to my PC it creates 12 empty 'local disk' and one 63,9 mb local disk (with folder 'image' and files in it). I tried this already: http://forum.xda-developers.com/showthread.php?t=2582142 using VirtualBox + Unbuntu but i'm stuck at the beginning. When I type "ls /dev/sd*" it only shows me the first " /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 " and nothing else...
I'm seriously pissed off at me right now, last time I bricked my phone 2 years ago and I promised myself not to ever play with any of this stuff and now I got my new phone and screw it up next day. Yeah I got it for one day and I screwed it up already.
I'm freaking out, can someone please help me?
Click to expand...
Click to collapse
Will your phone enter download mode? While it's fully powered down, hold the volume down and plug in a usb cable that's plugged into your pc. If you can get there, you're OK, there are options.
Sent from my LG-D800 using Tapatalk

After you do the dvb and it gives out 5 partitions, have you tried typing the name of the largest which would be 5 and seeing what happens
Sent from LG-G2 D800 on AEONFLEX 4.4.2

fatcarrotcake said:
It might be you have sent the recovery Image to the wrong partition, in the mean time you will have to read what you have done, and maybe see if you selected something incorrectly, you may have to get another phone while you see if you can fix the broken one. I take it you have tried all boot options and no reset is available ?
I recently broke a working phone it is annoying, but you live and learn.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
One thing that comes to my mind is that maybe the recovery image is not comptabilite with my phone. I know that when I tried to install TWRP with TWRP Manager it gave me an error when I chose g2d802 in device name so I didn't do it. The first link (tutorial I used) I posted, I used "openrecovery-twrp-2.7.0.0-d802" but I'm 99% it's the right one for my phone?
Jank4AU said:
Will your phone enter download mode? While it's fully powered down, hold the volume down and plug in a usb cable that's plugged into your pc. If you can get there, you're OK, there are options.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Unfortunately it doesn't enter download mode...
XxZombiePikachu said:
After you do the dvb and it gives out 5 partitions, have you tried typing the name of the largest which would be 5 and seeing what happens
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
You mean that "/dev/sda /dev/sda1 /dev/sda2 /dev/sda5" thing? I did that but it doesn't do nothing.

PLEASE can someone else reply? I seriously don't know what to do.

prophice said:
PLEASE can someone else reply? I seriously don't know what to do.
Click to expand...
Click to collapse
Try this method
Then boot from the usb stick(don't install ubuntu..just boot)
open terminal
copy and paste this - line by line (enter)
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount False
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount_open False
Then follow the instructions

prophice said:
The only thing that shows up is that error and LG logo and then it goes black (but it's still on).
Click to expand...
Click to collapse
At that point, press and hold the power button for 30 seconds to make sure its off completely. Then try download mode again. If you've already been doing that, disregard.

bender_007 said:
Try this method
Then boot from the usb stick(don't install ubuntu..just boot)
open terminal
copy and paste this - line by line (enter)
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount False
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount_open False
Then follow the instructions
Click to expand...
Click to collapse
I used that tutorial and Im in ubuntu atm, but i dont think it is detecting my lg at all. When using -ls /dev/sd*- its now showing -/dev/sda /dev/sda1 /dev/sda2 /dev/sdb /dev/sdb1- And when using -gdisk -l /dev/sdb- it gives me
[email protected]:~$ sudo gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb: 15630336 sectors, 7.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): AB4CD8FE-B964-4DCD-8AF2-43C5051BC71D
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15630302
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 15630335 7.5 GiB 0700 Microsoft basic data
Click to expand...
Click to collapse
and
[email protected]:~$ sudo gdisk -l /dev/sdb1
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Exact type match not found for type code F400; assigning type code for
'Linux filesystem'
Exact type match not found for type code 1000; assigning type code for
'Linux filesystem'
Exact type match not found for type code 7400; assigning type code for
'Linux filesystem'
Warning! Secondary partition table overlaps the last partition by
3454418421 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb1: 15628288 sectors, 7.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): A3BCA950-18FB-4E37-9B41-0F662D454416
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15628254
Partitions will be aligned on 1-sector boundaries
Total free space is 15628221 sectors (7.5 GiB)
Number Start (sector) End (sector) Size Code Name
1 3223366752 3470046675 117.6 GiB 8300 Linux filesystem
2 378192737 710426324 158.4 GiB 8300 Linux filesystem
3 225603442 225603451 5.0 KiB 8300 Linux filesystem
Click to expand...
Click to collapse
And also now when conected lg the ecran is flashing between black and very black,
And I used the lines you gave me obviously but I dont think it did anything,

Any messages popping up?
Sent from my LG-D802 using XDA Premium 4 mobile app

Nope, nothing.

OK it works!!!! I guess all I had to do is get some sleep and think fresh. =) Now that I'm in TWRP i'd like to install a rom, Am I safe to do it? I was thinking about Pardus HD but I have 2 questions.
1. I'm in TWRP but the computer doesn't detect my phone, how i am supposed to copy PardusHDC_7.1.zip to my phone?
2. it says "Upgrade your Recovery to TWRP 2.7.0.0 or Latest Philz Recovery" in installation guide, I have v2.6.3.2, will that make any difference?

Adb push pardushdc...zip /sdcard/pardus.zip
Sent from my LG-D802 using XDA Premium 4 mobile app

Ok I got it but before I start installing Id still like to know if im safe to do it with my current TWRP version?

prophice said:
Ok I got it but before I start installing Id still like to know if im safe to do it with my current TWRP version?
Click to expand...
Click to collapse
I think you need to update recovery or else install will just fail because of outdated files
Sent from LG-G2 D800 on AEONFLEX 4.4.2

It didn't work on v2.6.3.2 but it did on v2.7 and oh god I flashed that rom and it works!!!!! This is awesome, I don't know how I can thank you for all that help!!

please now make a backup and put it somewhere ie pc,usb stick,meenova safe, im glad you got it sorted and i know exactly how you felt as ive been in that situation a few times!!

prophice said:
OK it works!!!! I guess all I had to do is get some sleep and think fresh. =)
Click to expand...
Click to collapse
How do you make it? Please, I am stuck on this.

Please help dude....
prophice said:
OK it works!!!! I guess all I had to do is get some sleep and think fresh. =) Now that I'm in TWRP i'd like to install a rom, Am I safe to do it? I was thinking about Pardus HD but I have 2 questions.
1. I'm in TWRP but the computer doesn't detect my phone, how i am supposed to copy PardusHDC_7.1.zip to my phone?
2. it says "Upgrade your Recovery to TWRP 2.7.0.0 or Latest Philz Recovery" in installation guide, I have v2.6.3.2, will that make any difference?
Click to expand...
Click to collapse
Hi, I am facing the exact same issue as you described. I am using a LG G2 D802 international version. I did everything I could find on the internet. Could you please help me by telling how you got it working?? I am using a bootable USB of ubuntu and lsusb is showing my phone as Qualcomm 9006 but when I type ls /dev/sd* it is not giving me the device due to which I could not push the partition files. Please dude help me it has been 5 days since I am trying. You can PM me on my email [email protected]
Thanks in advance
---------- Post added at 11:07 AM ---------- Previous post was at 10:57 AM ----------
bender_007 said:
Try this method
Then boot from the usb stick(don't install ubuntu..just boot)
open terminal
copy and paste this - line by line (enter)
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount False
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount_open False
Then follow the instructions
Click to expand...
Click to collapse
Hi,
I saw your reply on the post which is related to the same issue I am facing since last 5 sleepless nights . I have a LG G2 D802 international variant and it had kitkat 4.4.2 earlier which I have successfully rooted. I recently received an OTA which I clicked to update [worst day of my life ] after that my phone is stuck in boot loop and rest you know. I trying to use ubuntu to push the partition files and recovery, but my phone is not detectable in ubuntu. lsusb is showing my phone as Qualcomm 9006 but when I type ls /dev/sd* it is not showing my phone. I saw your method in the quote and tried this also but it is still not working . Could you please let me know how can I solve this? Also by using the commands above does the phone needs to be connected or not ?? Please help me . You can PM me on [email protected].
Thanks is advance

Hello, i suggest to download vmware and slax ISO and run slax inside vmware. Then try the instructions. I can assist you but on monday , sorry
Poslano sa mog LG-D855 koristeći Tapatalk

QD 9008 FIX!! Tested on LG-V410(G Pad 7.0 US ATT)

I am beyond ecstatic, after 3 months of research, trial and error, I fixed my tablet!!
I am pleased to announce a fix to the dreaded QDLOAD 9008 brick! I've written this tutorial on the one tablet experimented on (LG-V410 aka Gpad 7.0 LTE US ATT), but I'm pretty certain others may find this helpful to other qualcomm msm based devices.
Background: I maintain that I can fix anything I break so I did the worst thing and corrupted the data on my LG GPAD LTE 7.0 (V410). As a result the tablet wouldn't go into any mode, no lights, even when charging, no screen image or light, nothing. When I plugged it into my computer, it wasn't even recognized, windows told me the device was having a problem. After a little experimentation I got it recognized (held power while connected to power cycle) by the computer as "QD BULK". Further research I found some drivers for Qualcomm devices and got the computer to recognize it as "QDLOADER 9008". I thought this was great news but from there got no where. I tried qpst, qfuse, hyperterminal, LG B2C, LG SUPPORT TOOL, EFS Professional, miflash, blankflash, etc... everything I tried got me nowhere. After 3 months, It is now fully operational and apparently CARRIER UNLOCKED, talk about a pot of gold at the end of a rainbow!!
WORD OF WARNING: This is not a simple matter, 9008 most likely means your Grand Partition Table is corrupted, and the poor thing doesn't have a clue how to function. My method is NOT GUARANTEED in any way, I will not be responsible if you turn your paper weight of a device into permanent paper weight or half functioning paper weight etc...PROCEED WITH CAUTION, this is not for the feint of heart nor a simple fix!! You've been warned!
PreRequisites:
-Windows (for expanding the KDZ) (there may be a linux alternative to LGFirmwareExtract)
-Linux and some basic experience with dd and navigating the terminal (I used ubuntu) --(again, nearly everything I'm about to explain can probaly be translated to another os.)
-KDZ for your device. http://forum.xda-developers.com/g-pad-10/general/kdz-lg-g-pad-7-0-v410-t3224867
-Replacement aboot and boot (see attached)
-KDZ Extractor ---http://forum.xda-developers.com/showthread.php?t=2600575
-TWRP http://forum.xda-developers.com/g-pad-10/development/recovery-twrp2-8-5-0lgv400-410-t3049568
-Fasboot and ADB http://forum.xda-developers.com/showthread.php?t=2588979
-A modified rom like Cyanogen mod etc... http://download.cyanogenmod.org/?device=v410
-16GB microsd card + a way of directly writing to it (i.e. usb card reader etc..) a second one is helpful but not required.
-Most important, Patience, beer, more patience, and more beer...
To teach a man to fish, some pertinent understanding: First thing to understand is how your main board works. Personally I disassembled my device and cross referenced every chip to do this, Good news is you don't have to. When power goes to the device, the SoC (system on a chip) looks to built in storage media for booting instructions (think low level here) and that in turn fires up everything else and then loads your kernel etc... You may be aware, there are two different types of computer systems out there, the old method used a BIOS, and the current uses UEFI. Older machines, when power was given to the system, the BIOS was responsible for firing up peripherals and finding the bootloader etc... UEFI (Unified Extended Firmware Instruction) however, relies on firmware on storage media to do all that.
For example, an x86 PC with a bios, when power is given to the board, the bios runs the show, testing equipment and waking up devices, then when it's ready, it looks to external media for a little magic byte at the end of the first sector of that media to indicate that it is bootable and in turn will boot (let those instructions take over). This style of booting media is called MBR or Master Boot Record.
Modern machines and most mobile devices use GPT or global partition table. There are quite a few advantages to GPT one primary being the possibility of many many more primary partitions, (MBR was very limited). The GPAD 7 LTE has 34 partitions to put things in perspective. When your device is stuck in 9008 mode, it is because it doesn't have a clue how to boot, most likely your GPT is corrupted. Fortunately, at least with the Gpad 7.0 this information does not have to be on the onboard internal memory chip. For this fix we will be constructing an sdcard to have all this info to get into a mode capable of writing to the emmc.
Without Further Ado, Here are the steps:
]PLUG THE TABLET INTO A CHARGER while you do the following (you may think it's been off and fully charged, but in reality it's probably been trying to boot over and over again while looking lifeless)
1.) Get the KDZ for your device (stock firmware)
2.) Extract the DZ using LGFirmwareExtractor
3.) Extract all the .bin files from the DZ using LGFirmwareExtractor
3b.) V410 US LTE ONLY - Replace aboot and boot with the files I attatched --I was fortunate enough to back them up before I hosed my tablet and they proved invaluable as the ones in the KDZ I linked to were causing strange graphic issues.
4.) open a terminal in linux and dd the sdcard with the file you extracted called "PrimaryGPT...."
I.E. "sudo dd if=/PATHTODZFILES/PrimaryGPT_0.bin of=/dev/sdx" (BE CERTAIN of the of= path, you can find yourself with more problems if you get that wrong) (run "sudo fdisk -l | less" first to verify what your sdcard's path is.)
This is where it gets tedious...:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
7.)Unmount your sdcard and put it in the tablet
8.) Press and hold power and volume up...If all went well, there is suddenly life to your paperweight!! Congratulate yourself and prepare for more fun... If nothing happened, revisit the above steps, more than likely something got flashed to the wrong partition.
9.)Now that you have fastboot, plug your tablet into the computer and use the following command: "fastboot boot TWRP.img" (or whatever the name or path is for your downloaded TWRP image.
10.) You should now be in TWRP and now your device is ADB ready, we are close to the home stretch...
11.) Now we need to load up an sdcard with all those dz files (except for laf and system images) and the custom rom like cyanogen mod. (if you only have the one sdcard you can unmount it and remove it while the table is in TWRP...crazy right?, if you opt for this, reformat the sdcard to ext or fat or whatever you please so the tablet can see all the bin files) Then put the sdcard into the tablet. You may need to remount the card in twrp before proceeding...
12.) Now from your computer type the following command "adb shell".
13.) now just like you did with the sd card dd PrimaryGPT_0.bin to the internal memory card, with the following command: dd if=/sdcard/PrimaryGPT_0.bin of=/dev/block/mmcblk0
14.) Grab the paper you wrote all the partitions down on and start doing the same thing you did to the sdcard to your tablet. You'll adjust the following command accordingly: "dd if=/sdcard/PARTITIONNAME.bin of=/dev/block/mmcblkpX (X being the partition number)
(again skip all system bin's and laf_xxxx.bin. Flashing laf disables fastboot on LG devices.)
15.) now time to install your custom rom, go through the prompts, clear your cache, and delvik cache and choose power off.
If all went well, you now have a tablet again, that's unlocked too!!!!! If not, don't lose faith, revisit the steps and ensure you didn't mistype or overlook something, this is so tedious it's easy to do. For instance, if you mistype your of=xxx it will create the file instead and give no error.
Post with your success stories, questions or difficulties and I'll try to help.
Yours Truly,
TheKiln
UPDATE/WARNING: Do not at any time under any circumstances dd directly from your host computer to the internal memory on your tablet, only do this via the asb shell. This may render a mode that I have not yet found a fix to, I will be working on it soon but from initial observation may be more complicated then the above instructions. With any invasive hacks like this tutorial there is always the possibility of making matters worse, so exercise caution and patience.

Quick Update/Revision : I am actively experimenting with this device and wanted to share that if your sbl1 and sbl1b partition is corrupt I have confirmed it will also cause 9008 mode. Therefore, it may be best to determine if the table is corrupt (try "parted /dev/block/mmcblk print"), and if not instead of wiping rewriting mmcblk0 try restoring sbl1 and sbl1b first. The V410 boots in the following order from what I can tell slb1->aboot->boot->system. So far I haven't found a downside to my prior instructions but to be less invasive just in case it might be wise to try this amendment.

I know my grand partition is corrupt, because after doing fastboot erase, basically everything, it came up as /dev/sdb. In a panic, I had deleted all the partitions, so now obviously my emmc storage is one big formated 16gb HD that cannot be seen in windows or linux no longer.
I just tried your method, found this post by doing a google search for:
sudo dd if=PrimaryGPT_0.bin
Had been doing just this, including the laf and many other ways. Am still getting the same thing though when putting the sdcard in the tablet, shows a 0% battery.
with the sdcard in the tablet I do get:
Bus 003 Device 063: ID 05c6:f006 Qualcomm, Inc.
Then after a few minutes, leaving it plugged into the USB I get:
Bus 003 Device 058: ID 1004:61a1 LG Electronics, Inc.
Also, with the sdcard in I do get KDZ_FW_UPD_EN to start updating but then get a perimeter error.

bethnesbitt said:
I know my grand partition is corrupt, because after doing fastboot erase, basically everything, it came up as /dev/sdb. In a panic, I had deleted all the partitions, so now obviously my emmc storage is one big formated 16gb HD that cannot be seen in windows or linux no longer.
I just tried your method, found this post by doing a google search for:
sudo dd if=PrimaryGPT_0.bin
Had been doing just this, including the laf and many other ways. Am still getting the same thing though when putting the sdcard in the tablet, shows a 0% battery.
with the sdcard in the tablet I do get:
Bus 003 Device 063: ID 05c6:f006 Qualcomm, Inc.
Then after a few minutes, leaving it plugged into the USB I get:
Bus 003 Device 058: ID 1004:61a1 LG Electronics, Inc.
Also, with the sdcard in I do get KDZ_FW_UPD_EN to start updating but then get a perimeter error.
Click to expand...
Click to collapse
Ive seen the exact mode you are referring to. Three possibilities:
1.) unplugged, hold down the power button for 30 seconds (or less if fastboot comes up)
2.) your sd card does not have all the necessary partitions to boot (which i just confirmed are specifically rpm, rpmb, tz, tzb, sbl1, sbl1b, PrimaryGpt(has to be done first), aboot and abootb)
3) They didn't dd quite right. from my active testing Ive found if you script the dd'ing it doesn't quite flash right, unless you add a delay after each step.
Its actually a very good sign you are seeing the 0% battery logo, sounds like you are almost there. Let me know what happens. Ill be happy to help guide you. Ive dedicated my v410 as a dev board so Im constantly running tests and reverse engineering it.

The 0% only shows up with the sdcard in, after I remove it, nothing. Tried wall charging it all night, that did nothing.
My theory is that if there was some way to mount the raw emmc and dd the primarygpt.bin to the raw emmc hd then the rest would be not problem.
I deleted the original EMMC partitions in gparted under linux after doing an erase fastboot -w laf, system, etc... something like that. After that the tablet did not show up again in gparted as soon as I unplugged it.
Right now I'm zero dd'ing my 16gb sd card, dang dd'ing seems to glue the partitions to the sdcard, If I try to fdisk the sdcard or delete the partitions using gparted, as soon as I dd the primarygpt.bin the old files reappear. Need to start fresh with 0s to the card.
In windows I can actually install specific lg drivers while in qualcomm hs_usb 9008 mode. The interesting thing with the sdcard in I can install the LG Android Net USB serial driver, which will not work while in 9008 mode.

bethnesbitt said:
The 0% only shows up with the sdcard in, after I remove it, nothing. Tried wall charging it all night, that did nothing.
My theory is that if there was some way to mount the raw emmc and dd the primarygpt.bin to the raw emmc hd then the rest would be not problem.
I deleted the original EMMC partitions in gparted under linux after doing an erase fastboot -w laf, system, etc... something like that. After that the tablet did not show up again in gparted as soon as I unplugged it.
Right now I'm zero dd'ing my 16gb sd card, dang dd'ing seems to glue the partitions to the sdcard, If I try to fdisk the sdcard or delete the partitions using gparted, as soon as I dd the primarygpt.bin the old files reappear. Need to start fresh with 0s to the card.
In windows I can actually install specific lg drivers while in qualcomm hs_usb 9008 mode. The interesting thing with the sdcard in I can install the LG Android Net USB serial driver, which will not work while in 9008 mode.
Click to expand...
Click to collapse
The 0% comes up when your sdcard is inserted because you are close to getting it done. You're going to have your computer running all night on the zero'ing but I can assure you that will be in vein. The whole point of this tutorial is so you can get into a mode in which you can flash the emmc. I can tell you are a little lost in the steps so pm me and I'll help you out. Also a word to the wise, you can try all you want with windows and the 9008 drivers, but seriously there is nothing out there specific to the v410 thats going to help you "engage" the 9008 mode. Not being stubborn I've just literally tried it all. If it's any credit I am clinically OCD. I can't sleep till I figure things out.

Finally, I see a hope is shining here!
I bricked my LG VK810, when I was trying to flash twrp, I refered to v500 pad instead and I flashed wrong img files (aboot, boot, sb1, sb2, sb3, tz & twrp.img) "only those 6 files" so I only need to replace those with the correct files, which I downloaded now.
I do not have Ubuntu, however I have CentOS, which i have not used for couple of years, so I forgot how to use it. also do I still need to use the LG Firmware Extractor?
please help

thekiln said:
This is where it gets tedious...:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
Click to expand...
Click to collapse
Please please please help, how to do those steps!

nmnm4alll said:
Please please please help, how to do those steps!
Click to expand...
Click to collapse
I am not certain exactly which partitions have to be flashed, the attached note I made was from what I can tell so far. I was simply noting that it may be best to try one partition at a time vs doing them all at once, it is at your own descretion. So as far as listing the partitions, I'm not familuar with the centos distro but in Ubuntu it is something to the effect of fdisk /dev/sdb -l or gdisk /dev/sda then p. I hope that answers your question, If not please be more specific to your exact question.

thekiln said:
I am not certain exactly which partitions have to be flashed, the attached note I made was from what I can tell so far. I was simply noting that it may be best to try one partition at a time vs doing them all at once, it is at your own descretion. So as far as listing the partitions, I'm not familuar with the centos distro but in Ubuntu it is something to the effect of fdisk /dev/sdb -l or gdisk /dev/sda then p. I hope that answers your question, If not please be more specific to your exact question.
Click to expand...
Click to collapse
Thank you very much for your response, I am sorry I have never flashed partitions before, sbut I noticed gparted is not on CentOS, so I downloaded Puppy precise Linux as I was able to find gparted and I tried using it as shown in this video, https://www.youtube.com/watch?v=6z1Tu9l8WNc
But I am confused now about how big and what are the formats for the 34 partitions which need to be created?

nmnm4alll said:
Thank you very much for your response, I am sorry I have never flashed partitions before, sbut I noticed gparted is not on CentOS, so I downloaded Puppy precise Linux as I was able to find gparted and I tried using it as shown in this video, https://www.youtube.com/watch?v=6z1Tu9l8WNc
But I am confused now about how big and what are the formats for the 34 partitions which need to be created?
Click to expand...
Click to collapse
Flashing PrimaryGPT_0.bin will automatically create the partitions. Flashing the individual partitions will give each partition the data needed. There should be no need to manually create partitions, if no partitions show up in gparted, the problem goes back to primarygpt, as that is the partition table.

I am not quite sure what you mean by:
thekiln said:
5.) Do some hand stretches and start charting all 34 partitions on paper. Your sdcard is now partitioned with GPT and you need to know the name of each partition and its path. I.e. ("Partition name: LAF Located at /dev/sdXx")
Click to expand...
Click to collapse
how to can I get the Partition names?
Edit: I finally was able to get Ubuntu installed on my computer, so please instruct accordingly, sorry I have been googling everything you have mentioned in your OP with no luck!
Thanks in advance.

nmnm4alll said:
I am not quite sure what you mean by:
how to can I get the Partition names?
Edit: I finally was able to get Ubuntu installed on my computer, so please instruct accordingly, sorry I have been googling everything you have mentioned in your OP with no luck!
Thanks in advance.
Click to expand...
Click to collapse
For the names I like to use "parted /dev/sdb" then "print" (sdb being the location of the sd card, might be sdc, sdd, etc..)

thekiln said:
For the names I like to use "parted /dev/sdb" then "print" (sdb being the location of the sd card, might be sdc, sdd, etc..)
Click to expand...
Click to collapse
Thanks for the command line, I came up with this 36 partitions
https://www.dropbox.com/s/bw8nj317y3v7pw6/VirtualBox_Ubunto_05_01_2016_08_59_03.png?dl=0
now how do I know each partition's path?
you have mentioned "I.e. ("Partition name: LAF Located at /dev/sdXx")"
so do I type for example: "modem: LAF located at /dev/sdb1" (sdb1 is my sdcard's path)?
thekiln said:
6.) now for the fun part: dd every .bin to the corresponding partition EXCEPT: laf.bin and any of the system_xxxxx.bin files. (laf disables fastboot and the next step will bring you to a useless LG firmware download mode)( I.e. sudo dd if=/PATHTODZFILES/laf_xxx.bin of=/dev/sdXx) If some fail out, don't fret too much, I'm currently uncertain which ones are required and don't feel like corrupting my tablet again to figure that out. If the next step doesn't work you may need to revisit this step and ensure everything was accurate. It's easy to write down the wrong location for a partition and throw everything off
Click to expand...
Click to collapse
Those are the files got extracted from the DZ file
https://www.dropbox.com/s/z3ebiy4vvnsy9oo/Untitled.png?dl=0
and this is a screenshot in Ubuntu after copying the file on a 64 memory stick and mounting it
https://www.dropbox.com/s/gqn35n1npklq8ld/VirtualBox_Ubunto_05_01_2016_09_30_15.png?dl=0
Do I just type: "sudo dd if=/media/mike/MEMORY/aboot_153600.bin of=/dev/sdb1" and so on for all .bin files?
Please try to write command lines as I do not have experience with Linux

I'll be honest and blunt, if you do not have experience with linux, a simple keystroke mistake could wipe your entire computer. I can't in good conscience recommend touching dd if you're not familiar with it. Not trying to be condescending or anything just really dangerous tools we are working with here.

it have problem
wow !!! i can see the LG logo in my tablet !!!
but i can't run next step !!!
pushed power + volume up button but i never changed screen !!
This is written on the screen.
"boot certification verify"

please help me i copy 34 partition on SDcard after that what can i do? please answer , this does not work (( 8.) Press and hold power and volume up...If all went well, there is suddenly life to your paperweight!! Congratulate yourself and prepare for more fun... If nothing happened, revisit the above steps, more than likely something got flashed to the wrong partition.

Issue
Hello, I've successfully followed the tutorial until step 9. When i flash TWRP it reboots and comes back to the fastboot screen.
If I hold the vol+ button when it is booting, the download mode screen flashes for a second and then it comes back to the fastboot.
I haven't been able to to anything else and would be very grateful if someone could help me with this.
Apparently there is no bootloader so it is stuck
I attached a picture of my screen

LG G Pad 7.0 V400
Is there a way to unlock Qualcomm 9008 from LG V400?

Finally my dead tablet went into fastboot mode.
Except windows cannot find a fastboot driver and fastboot command can't locate the device either. Any suggestions?