Okay, heres an ADVANCED tutorial for flashing your elocity a7 tablet with factory firmware software manually using the nvidia apx flash tools. The intention of providing this information is so you don't have to google to get it all in one place, w/ details pertaining to the elocity a7. YOU SHOULD always attempt to flash from android recovery FIRST before attempting these instructions. they are intended for advanced users only. please use extreme caution.
to obtain the nvidia apx flash tools follow @5[Strongino]'s instructions;
1.
3.1 Getting Nvidia Tools
- Go to http://developer.nvidia.com/tegra/devkit-250tango and download "Android 2.2 (Froyo) for Tegra 250 & Tango ONLY" (one or both Windows/ Linux)
Speedlinks (NVidia updated tools 7 feb 2011, so links would change in future)
Windows:
Code:
http://developer.download.nvidia.com...o_20110207.msi
Linux:
Code:
http://developer.download.nvidia.com...0110207.run.gz
- [WIN] the default installation location is
Code:
C:\Program Files\NVIDIA Corporation\tegra_froyo_20110207
Click to expand...
Click to collapse
okay, you have the software. i'm assuming you did this from windows; i did as there was more reported instructions for use from windows.
2
if you don't already have it, you should download the latest factory firmware for the elocity a7;
Code:
http://www.elocitynow.com/support_downloads.shtml
the latest firmware update is date February 24, 2011, and the build version is PBJ8000.2.0133.
3
what i did to setup is made a folder titled;
Code:
C:\Program Files\NVIDIA Corporation\tegra_froyo_20110207\tegrabackup
i then moved the follows files from the tegra_froyo_20110207 folder to the new \tegrabackup folder;
boot.img
bootloader.bin
recovery.img
system.img
you may wish to also move flash.bct (i did not do this step) as well, as all 5 files are factory software for a tegratablet (not the A7, don't ask me to go into details right now).
4
i then extracted the latest update.zip from elocity's website to the;
Code:
C:\Program Files\NVIDIA Corporation\tegra_froyo_20110207
folder for convenient, so that i can run the nvidia apx flash tool w/ our software in the same directory.
5
i pulled the elocity a7 partition information (so we know what partition numbers to flash our software to).
Code:
nvflash -r --getpartitiontable partitiontable.txt
6
i then updated the flash.cfg file in the same folder we're working in using that information.
download link here;
Code:
http://www.mediafire.com/?rgzshkvw369dfdr
7
i'm missing the instructions i used to format the cache partition using nvflash, but this may not be necessary; will update later.
8
i flash the new recovery.img from the update.zip provided by elocity support.
Code:
nvflash --bl bootloader.bin --download 6 recovery.img
--
thats it for flashing the latest factory recovery. i did this, and formatted the cache partition using nvflash. afterwards, when i booted to recovery it still had the recovery.c error at the bottom, but the buttons were responsive instead of flakey, and i was able to wipe cache, factory reset and apply the update.zip from my sdcard.
--
notes; partition #'s for the elocity a7, 12 partitions total, starting w/ id#2;
2 BCT - Boot Configuration Table
3 PT - Partition Table
4 EBT - Bootloader
5 NVC -
6 SOS - Recovery Kernel - recovery.img
7 LNX - System Kernel - boot.img
8 MBR - msdos partition table for the rest of the disk
9 APP - OS root filesystem - system.img
10 CAC - Cache partition (?)
11 MSC
12 ER1
13 UDA
i loosely created the flash.cfg file using the partition information available, the examples present, and calculate the partition size by multiplying the number of sector by bytes per sector in the partitiontable.txt. some details about non pertinent partitions (for me) may be incorrect in the flash config, the important thing for me is that the partition numbers are correct for our use, and the sizes should be correct so the partitions get put in the right order. i will note that there is much more space available for system, it would appear that when flashing w/ android recovery that the system partition created seems to be just the size for the system files and nothing more.
i'm wondering if one were to do a full format of the apps partition and created an zipped /system file system w/ install script if the full space would be available.. future tests.
--
dangerous experiments for those w/out sdcard access after this, as i have not read any report that flashing the system.img worked yet.
if you want to try;
Code:
nvflash --bl bootloader.bin --download 9 system.img
if you're REALLY BRAVE, try flashing the whole update.zip (extract the the nvflash folder) using this command;
Code:
nvflash --bl bootloader.bin --download 6 recovery.img --download 7 boot.img --download 9 system.img
this will flash the factory recovery, boot(kernel+ramfs), and system. until some brave soul tests these options out, we won't know for a fact its safe. in theory it should be.
my theories come with no warranties.
--
i would still suggest reading in depth (google), and studying backing up your devices partitions using nvflash. i didn't post instructions for this, as i was not able to get this to work, and was the least of my concerns w/ an already bricked tablet.
--
additional apx commands available;
Code:
Nvflash started
nvflash action [options]
action (one or more) =
--help (or -h)
displays this page
--cmdhelp cmd(or -ch)
displays command help
--resume (or -r)
send the following commands to an already-running bootloader
--quiet (or -q)
surpress excessive console output
--wait (or -w)
waits for a device connection (currently a USB cable)
--create
full initialization of the target device using the config file
--download N filename
download partition filename to N
--setboot N
sets the boot partition to partition N
--format_partition N
formats contents of partition N
--read N filename
reads back partition N into filename
--getpartitiontable filename
reads back the partition table into filename
--getbit filename
reads back BIT into filename
--getbct
reads back the BCT from mass storage
--odm C Data
ODM custom 32bit command 'C' with associated 32bit data
--go
continues normal execution of the downloaded bootloader
options =
--configfile filename
indicates the configuration file used with the following commands:
--create, --format_all
--bct filename
indicates the file containing the BCT
--sbk 0x00000000 00000000 00000000 00000000
indicates the secure boot key for the target device
--bl filename
downloads and runs the bootloader specified by filename
--odmdata N
sets 32bit customer data into a field in the BCT, either hex or
decimal
--diskimgopt N
sets 32bit data required for disk image convertion tool
--format_all
formats all existing partitions on the target device using the config file,
including partitions and the bct
--setbootdevtype S
sets the boot device type fuse value for the device name.
allowed device name string mentioned below:
emmc, nand_x8, nand_x16, nor, spi
--setbootdevconfig N
sets the boot device config fuse value either hex or decimal
--verifypart N
verifies data for partition id = N specified. N=-1
indicates all partitions
Intended to be used with --create command only.
--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
--sync
issues force sync commad
--rawdeviceread S N filename
reads back N sectors starting from sector S into filename
--rawdevicewrite S N filename
writes back N sectors from filename to device starting from sector S
--updatebct <bctsection>
bctsection should refer to the section of the bct we are updating.
Curently we suport updates for following sections
<SDRAM> updates SdramParams and NumSdramSets fields
<DEVPARAM> updates DevParams, DevType and NumParamSets
<BOOTDEVINFO> updates BlockSizeLog2, PageSizeLog2 and PartitionSize
Very good information to learn more about these tablets.
But I would be far from surprised if this thread helps create enough bricks to build a wall
Knowledge in the hands of few is power, knowledge in the hands of many is dangerous lol.
the information is provided from personal experience from myself and other users on the xda forum. i just put it all in one place so folks can gain some insight on the subject in one thread w some continuity instead of fragments googled and lost when the browsers closed.
otherwise i think i put blunt cautions at the beginning and end of the OP.
Sent from my X10i using Tapatalk
Wonder when the Honeycomb image is going to show up on that page...
I don't think it will.
I want to try honeycomb with that. Is there anyway I can test it without briking my tablet ? Even if some parts don't work, I want to test it, at least we could get a first taste of Honeycomb on our tablet.
yeah.. actually, if you look at the nvidia ventana sdk, there is a gingerbread sdk for tegra2, just the ventana is the next generation board. not a perfect fit, but a sloppy chef job could possibly be done.
lotta folks bringing the subject of os upgrades up in every thread. almost to the point of desperate spamming.
..you could try yourself instead of waiting for others.
EDIT; my bad. you said honeycomb. none the less, youre only detracting from existing threads. please, start a new thread.
Sent from my X10i using Tapatalk
I'll try 2.3 too, why not !
Flash updated recovery using APX
Hi, bestialbub. The capacitive buttons in my Elocity A7 are flakey, both within Recovery and within the Android OS itself. The affected buttons are the Menu and Back buttons, sometimes they're responsive, other time no response at all. I'm wondering if flashing an updated Recovery via APX will remedy this (as it did in your case). BTW, I can't seem to download the Flash Tools even after creating an nVidia account. You, mentioned flashing from Windows. How did you connect your A7 to the PC for flashing, as there's no included Data Cable with the package? Thanks.
racesurg said:
Hi, bestialbub. The capacitive buttons in my Elocity A7 are flakey, both within Recovery and within the Android OS itself. The affected buttons are the Menu and Back buttons, sometimes they're responsive, other time no response at all. I'm wondering if flashing an updated Recovery via APX will remedy this (as it did in your case). BTW, I can't seem to download the Flash Tools even after creating an nVidia account. You, mentioned flashing from Windows. How did you connect your A7 to the PC for flashing, as there's no included Data Cable with the package? Thanks.
Click to expand...
Click to collapse
Found post by 5[Strogino]. Got nVidia Flash Tools and saw pic of cable. Thanks.
I have try and it get stoped at usb and android logo
my tablet is a compal 7
some help please
mira presiona el boton de encendido por unos 15- 20 seg. con eso bastara.
hextor_dark said:
mira presiona el boton de encendido por unos 15- 20 seg. con eso bastara.
Click to expand...
Click to collapse
esto solo me reinicia la maquina y ahi se queda otra vez en el logo
If you ever run into trouble and can't decrypt your phone, but still have the image and password of the encrypted file system, you can use this tool to mount the encrypted file system on your PC.
My i9300 display and touchscreen broke, but I managed to dump /dev/block/mmcblk0p12 via recovery. This partition contains the encrypted /data file system on my device.
So I took the AOSP code and wrapped a small command line tool around it to decrypt and mount the device on Linux.
I hope this is useful and that this is the right forum for such things.
This is a low-level backup comes from an WP8.1 test machine made by Nokia- Microsoft, codenamed D2FR - ID326 - RM1071 by Mass Storage Mode and Win32Disk image application
Full 4gb emcp system backup file
FFU flash file
GPT backup file
UEFI backup file
Emergency Payload file
all in here: https://mega.nz/#F!GR8gCA5Z!YUjZAh0jN0edOyTcVArzmw
Android 4.4 buggy file : https://mega.nz/#!PJtRzAaA!5g9wKyIq9zcsw5vpjkBT8_lKT6fYz_Q65xRuFZgaOW0
Android is unstable. If try run android, display is wrong driver
I will upload Emergency Payload file can work for this device.. No display Flashapp but command work
I installed android. Use EDL cable to force go to Qcom 9008 mode. Flash Emergency payload and it work. Now it restoring my backup
this is emergency payload i used to reborn it from dead: 1147.edp and ede.ede, 1147 not show display. maybe 1140 can show flashapp display
Adnroid test will available after few hour. Just for fun. Dont blam me ???
Hi to all! Like the title said, i'm trying to extract from 7T product partition img, then i want to edit it and re-flash it back.
Which is the fastest way to do so?
to get to the image you can use the payload dumper and unpack the payload.bin contained in the firmware pack then you have the produckt.img whether you can edit this or whether it also has write protection I cannot tell you unfortunately .
Maybe you can do this using the edl.py script that's available on GitHub.
This script allows you to use some of the qualcomm sahara protocol commands for stuff like reading and saving partition from the phone to your computer, or to write a partition from the computer to the phone internal memory.
Also with msm tool, you can enable the readback mode that allows you to backup single or multiple partitions (you just have to check the ones you want).
I hard bricked an LG G7 ThinQ G710EAW by flashing the wrong firmware (T-Mobile) onto it via LGUP. It now goes into EDL mode after shorting test points, but I'm unable to revive it by following this unbrick thread. Loading up the partition images via Partition Manager in QFIL "succeeds", but it doesn't revive my phone. Doesn't get me to fastboot. Still nothing on screen.
I also tried the rawprogram*.xml option using the XMLs in that thread, but QFIL keeps erroring out that the partition sizes defined in the XML are different from what it sees on the device.
The OP for the thread seems to not be active any longer.
Can someone here please help me understand how to recover my phone?
Anyone? Happy to donate for help as well.
Bumping up this thread.
If I had another EAW motherboard, would it help unbrick my motherboard? Wondering how I can fix my phone
So, I was able to finally figure this all out, recover my LG G710EAW and bring it back to life! It was a mix of information from many threads. No boxes, and no payment to anyone. All free.
The OP of this thread is active but has completely stopped responding to his thread and to his DMs - he's likely uninterested in a 4-5 year old phone at this point. In his first post he mentioned creating rawprogram* XMLs by hand, and it taking hour+ to do so. However, I'm unsure why it took him that long and in the end the files don't even work for QFIL since the sector size in the XMLs (512B) is different from device sector size (4096B). Nevertheless, I was able to flash these via command line 'edl' which ignored the sector size, but it didn't recover the device.
Generating rawprogram XMLs is easy if you can figure out how to run this Python program mentioned in this thread. However, the files attached there no longer work in 2022, the links are dead, and Python 2.7 is a dinosaur. Someone in that thread mentioned a different, fixed, repo but it didn't work with Python 2.7 for the 'undz' part. After a lot of head banging, I tried Python3 and 'undz' worked.
Here are the steps:
- Download the firmware for your model in KDZ format
- Install QPST
- Install Python3.x
- Run: pip3 install setuptools zstandard
- Download ZIP for kdztools from the repo: https://github.com/ErickG233/kdztools (or the attachment)
- Unzip kdztools and CD into that directory kdztools-master. This version is bug-fixed and also generates rawprogram files for us.
- Copy the firmware KDZ into kdztools-master directory
- Run: python3 unkdz.py -f G710EAW30e_00_0916.kdz -x. This creates a DZ file in a new `kdzextracted` folder
- Move the extracted DZ file from the kdzextracted folder back one level up, into kdztools-master dir
- Run: python3 undz.py -f G71030q_00_user-signed-ARB0_OPEN_ESA_DS_OP_0916.dz -c
- This creates a dzextracted folder here with all the files needed to recover your phone. Now all we need are the rawprogram XMLs.
- Run: python3 undz.py -f G71030q_00_user-signed-ARB0_OPEN_ESA_DS_OP_0916.dz -r. This will create all the rawprogram XMLs you need to flash. No patch files are created, but that is OK.
- In my case, QFIL complained it couldn't find file "PrimaryGPT_0.bin", so I copied file gpt_main0.bin_0 and renamed the copy gpt_main0.bin_0_copy > PrimaryGPT_0.bin
- Load your phone into EDL mode. If you want to use test points, see the image in this thread.
- Load QFIL. Use the ELF programmer file from any of the threads linked thus far. Select flat build. Load all rawprogram XMLs generated previously. Hit cancel when it asks for patch file XMLs.
- Hit Download.
This will recover your phone so it's able to boot and all. However, in my case, the phone had lost serial number and IMEI numbers (dual SIM) as well.
- To restore your IMEI numbers, you will need your QCN file or a backup of your FSG (fsg.img) partition from before bricking. In my case, I had flashed, via LGUP, T-Mobile firmware on my Indian phone. I then dumped all the partitions using command line EDL. I have not used QCN method since it seems to require a lot of steps to put the phone into diagnostics mode. I had a backup of the FSG partition, so I used that instead.
- If you have a backup of your FSG partition, load QFIL > Partition Manager. Erase modemst1 modemst2 and fsg partitions. Then, load the backup FSG.img file onto FSG partition. Restart phone.
- Now, if you have the serial number from your bill or box, see this thread to restore it. Pay extra attention to the Firehose configuration section, or else, it may create some issues. It's best to restore S/N after restoring IMEI in my experience, but this could just be some randomness or bad Firehose config during S/N restore.
This happiness was short-lived. When I was flashing all these KDZ via QFIL and LGUP trying to get my IMEIs back, I once saw "This phone is permanently locked and cannot be unlocked". That seems to have taken out my second SIM slot.
Now, after a fresh QFIL flash (with erase before download), my first SIM slot is also dead.
Neither of the SIM slots work now.
This has been so frustrating!
urover said:
This happiness was short-lived. When I was flashing all these KDZ via QFIL and LGUP trying to get my IMEIs back, I once saw "This phone is permanently locked and cannot be unlocked". That seems to have taken out my second SIM slot.
Now, after a fresh QFIL flash (with erase before download), my first SIM slot is also dead.
Neither of the SIM slots work now.
This has been so frustrating!
Click to expand...
Click to collapse
Any luck in recovering the phone ??