Fail To Root Device - Galaxy Tab 3 Q&A, Help & Troubleshooting

I am Trying to Root my TAB p5210 But when i use Odin it stops at PIT File =(
I have tried downloading Pit Files but nothing helps .
ODIN error Code :
<ID:0/008> Added!!Device Not Detected
Device Connected
/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/ElevateScript.sh: line 2: export: `download-pit': not a valid identifier
/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/ElevateScript.sh: line 2: export: `--output': not a valid identifier
/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/ElevateScript.sh: line 2: export: `/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/part.pit': not a valid identifier
Usage: heimdall <action> <action arguments>Action: close-pc-screenArguments: [--verbose] [--no-reboot] [--resume] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Attempts to get rid off the "connect phone to PC" screen.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.Action: detectArguments: [--verbose] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Indicates whether or not a download mode device can be detected.Action: download-pitArguments: --output <filename> [--verbose] [--no-reboot] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Downloads the connected device's PIT file to the specified output file.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.Action: flashArguments: [--<partition name> <filename> ...] [--<partition identifier> <filename> ...] [--pit <filename>] [--verbose] [--no-reboot] [--resume] [--stdout-errors] [--usb-log-level <none/error/warning/debug>] or: --repartition --pit <filename> [--<partition name> <filename> ...] [--<partition identifier> <filename> ...] [--verbose] [--no-reboot] [--resume] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Flashes one or more firmware files to your phone. Partition names (or identifiers) can be obtained by executing the print-pit action.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.WARNING: If you're repartitioning it's strongly recommended you specify all files at your disposal.Action: helpDescription: Displays this dialogue.Action: infoDescription: Displays information about Heimdall.Action: print-pitArguments: [--file <filename>] [--verbose] [--no-reboot] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Prints the contents of a PIT file in a human readable format. If a filename is not provided then Heimdall retrieves the PIT file from the connected device.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.Action: versionDescription: Displays the version number of this binary.
/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/ElevateScript.sh: line 2: export: `download-pit': not a valid identifier
/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/ElevateScript.sh: line 2: export: `--output': not a valid identifier
/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/ElevateScript.sh: line 2: export: `/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/part.pit': not a valid identifier
Usage: heimdall <action> <action arguments>Action: close-pc-screenArguments: [--verbose] [--no-reboot] [--resume] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Attempts to get rid off the "connect phone to PC" screen.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.Action: detectArguments: [--verbose] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Indicates whether or not a download mode device can be detected.Action: download-pitArguments: --output <filename> [--verbose] [--no-reboot] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Downloads the connected device's PIT file to the specified output file.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.Action: flashArguments: [--<partition name> <filename> ...] [--<partition identifier> <filename> ...] [--pit <filename>] [--verbose] [--no-reboot] [--resume] [--stdout-errors] [--usb-log-level <none/error/warning/debug>] or: --repartition --pit <filename> [--<partition name> <filename> ...] [--<partition identifier> <filename> ...] [--verbose] [--no-reboot] [--resume] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Flashes one or more firmware files to your phone. Partition names (or identifiers) can be obtained by executing the print-pit action.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.WARNING: If you're repartitioning it's strongly recommended you specify all files at your disposal.Action: helpDescription: Displays this dialogue.Action: infoDescription: Displays information about Heimdall.Action: print-pitArguments: [--file <filename>] [--verbose] [--no-reboot] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Prints the contents of a PIT file in a human readable format. If a filename is not provided then Heimdall retrieves the PIT file from the connected device.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.Action: versionDescription: Displays the version number of this binary.
/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/ElevateScript.sh: line 5: export: `download-pit': not a valid identifier
/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/ElevateScript.sh: line 5: export: `--output': not a valid identifier
/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/ElevateScript.sh: line 5: export: `/var/folders/xt/qwf7hw0d353bxx3r65109gp80000gn/T/CASUALlarsjhonatankyllo-2020-10-31-13.33.57/part.pit': not a valid identifier
Usage: heimdall <action> <action arguments>Action: close-pc-screenArguments: [--verbose] [--no-reboot] [--resume] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Attempts to get rid off the "connect phone to PC" screen.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.Action: detectArguments: [--verbose] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Indicates whether or not a download mode device can be detected.Action: download-pitArguments: --output <filename> [--verbose] [--no-reboot] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Downloads the connected device's PIT file to the specified output file.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.Action: flashArguments: [--<partition name> <filename> ...] [--<partition identifier> <filename> ...] [--pit <filename>] [--verbose] [--no-reboot] [--resume] [--stdout-errors] [--usb-log-level <none/error/warning/debug>] or: --repartition --pit <filename> [--<partition name> <filename> ...] [--<partition identifier> <filename> ...] [--verbose] [--no-reboot] [--resume] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Flashes one or more firmware files to your phone. Partition names (or identifiers) can be obtained by executing the print-pit action.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.WARNING: If you're repartitioning it's strongly recommended you specify all files at your disposal.Action: helpDescription: Displays this dialogue.Action: infoDescription: Displays information about Heimdall.Action: print-pitArguments: [--file <filename>] [--verbose] [--no-reboot] [--stdout-errors] [--usb-log-level <none/error/warning/debug>]Description: Prints the contents of a PIT file in a human readable format. If a filename is not provided then Heimdall retrieves the PIT file from the connected device.Note: --no-reboot causes the device to remain in download mode after the action is completed. If you wish to perform another action whilst remaining in download mode, then the following action must specify the --resume flag.Action: versionDescription: Displays the version number of this binary.

Did you fix it?

Related

hboot

Aloha
Any way to execute the commands hidden in the hboot.nb0 file ?
When i look in it with a text editor i see things like:
Usage: savemem2sd <memory offset> <length> <file name>
ex: savemem2sd 85cd0000 2c000 mem.bin invalid parameters!
<addr> is invalid!
unsupported <width>
failed to write. <addr> must be aligned
failed to write. <value> is invalid
memory dump
%X: - %X: %B %B | %s
%B %X: %H %H | %s
%H %X: %X %X | %s
%X | %s
Usage: saveprt2sd <partition name> <-n> <file name> <-a>
<partition name> - Partition name want to save
<-n> <file name> - File name to store in(optional)
<-a> - Save whole blocks even read empty page(optional)
ex: saveprt2sd hboot hboot.bin
(use listpartition command get all partition name)
-a -n
Click to expand...
Click to collapse

completely screwed terminal

i was ****ing around with terminal trying to get it to recognize my phone and i created a bash profile but now when i open terminal i get
-bash: {PATH}:: command not found
when i was copying/pasting **** from the tutorial i hit enter too soon and now i just get errors all the time when i try to do **** in terminal. anyway to revert terminal back to the way it was?
Code:
Last login: Sun Jul 25 00:08:05 on ttys000
e-bash: {PATH}:: command not found
new-host:~ videinfra$ echo $path
new-host:~ videinfra$ /Users/videinfra/sdkfolder/tools
-bash: /Users/videinfra/sdkfolder/tools: is a directory
new-host:~ videinfra$ /Users/videinfra/sdkfolder/tools/adb
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
new-host:~ videinfra$ adb devices
-bash: adb: command not found
new-host:~ videinfra$ adb usb
-bash: adb: command not found
new-host:~ videinfra$ -d
-bash: -d: command not found
new-host:~ videinfra$ $path
new-host:~ videinfra$ cd /Users/videinfra/sdkfolder/tools
new-host:tools videinfra$ adb devices
-bash: adb: command not found
new-host:tools videinfra$ -bash delete
-bash: -bash: command not found
new-host:tools videinfra$ .bash
-bash: .bash: command not found
new-host:tools videinfra$

Lg g-slate/docomo l-06c unbrick !!!

My LG Docomo L-06C (Android 3.0) had been bricked by format all partitions, it just connected to PC with APX mode. I want to share steps that i did to unbrick it:
STEP 1:
- You must have all partitions backup files: (Notice: Those files restore for Android 3.0 with ./nvflash)
http://www.mediafire.com/file/6v2sct03t6fhgcp/lg_gslate_stock_image.part1.rar
http://www.mediafire.com/file/wvn4x3xujudmt1w/lg_gslate_stock_image.part2.rar
http://www.mediafire.com/file/61cub2by19lqo6m/lg_gslate_stock_image.part3.rar
password: 30071982
https://www.mediafire.com/folder/9b...s1jg2i,eg263xw7e6ok3jf,qbypf2ug4zp5985/shared
Restoring: (I used Urbuntu)
-Put those backup files in a directory include nvflash and open a terminal to there.
-Plug it into your computer via USB.
-Running "lsusb" should show an entry "0955:7820 NVidia Corp."
Run the command "sudo su" to get a root shell. Running "ls" should still show the four files.
./nvflash --bl bootloader.bin --getpartitiontable ptable.txt
View attachment ptable.txt
In the ptable.txt, you should see following pattern (you need the highlighted values for each partition you want to restore):
PartitionId=[PartitionId]
Name=...
DeviceId=18
StartSector=[StartSector]
NumSectors=[NumSectors]
BytesPerSector=2048
Open a terminal and change to the following directory: linux4tegra/nvflash (you can download them in http://code.google.com/p/lg-v909/wiki/Restore_to_Stock and fastboot.bin file in http://www.mediafire.com/file/6v4si33olrt5x9o/linux4tegra_10.9.3.rar)
Reload the vanilla bootloader using the following command:
# LD_LIBRARY_PATH=. ./nvflash --bl fastboot.bin --go
For earch part-[PartitionId].img you want to restore, execute the following command:
# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite [StartSector] [NumSectors] part-[PartitionId].img
- Do it from part2 to part18 (part9, 10, 11 not to need restore)
- part8.img in lg_gslate_stock_image.rar file is t-mobile system. If your pad is Docomo L-06C, you can use my docomo_system.img to replace part8.img
http://www.mediafire.com/file/7g18k95m5w4ombg/docomo_system_part8.part1.rar
http://www.mediafire.com/file/4hbpboatbarbot9/docomo_system_part8.part2.rar
./nvflash -r --sync
Reboot your device.
STEP 2: If gslate show password screen after boot:
- Boot the slate into fastboot mode by turning it off, then holding the volume button and power button down untill it says "entering fastboot protocol"....
- Then open a terminal or cmd prompt (folder include fastboot) on your PC and with the slate pugged into USB type:
fastboot oem unlock
fastboot -w (format all userdata)
Reboot and your all set
** With G-Slate runing Android 3.1, the bootloader.bin is locked (so you can't use ./nvflash). I'm not sure can use "dd method" to restore it, i'll post this then and you can try
You can join: irc.freenode.net / #g-slate (mIRC) to ask questions about it !
GOODLUCK !
Thank you!
Thank you for the tip!! I will try it.
give me some advice please..
[email protected]:~$ cd ~/download/gs/linux4tegra/nvflash
[email protected]:~/download/gs/linux4tegra/nvflash$ sudo su
[sudo] password for dryasdust1:
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash --bl ../prebuilt/fastboot.stock.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x02804086433fb457
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: ../prebuilt/fastboot.stock.bin
| 936016/936016 bytes sent
../prebuilt/fastboot.stock.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 0 1536 part-[2].img
Nvflash started
[resume mode]
sending file: part-[2].img
/ 3145728/3145728 bytes sent
part-[2].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 11536 256 part-[3].img
Nvflash started
[resume mode]
sending file: part-[3].img
/ 524288/524288 bytes sent
part-[3].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 1792 2560 part-[4].img
Nvflash started
[resume mode]
sending file: part-[4].img
/ 5242880/5242880 bytes sent
part-[4].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 4352 512 part-[5].img
Nvflash started
[resume mode]
sending file: part-[5].img
/ 1048576/1048576 bytes sent
part-[5].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 4864 2560 part-[6].img
Nvflash started
[resume mode]
sending file: part-[6].img
/ 5242880/5242880 bytes sent
part-[6].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 7424 512 part-[7].img
Nvflash started
[resume mode]
sending file: part-[7].img
/ 1048576/1048576 bytes sent
part-[7].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 7936 204800 part-[8].img
Nvflash started
[resume mode]
sending file: part-[8].img
/ 419430400/419430400 bytes sent
part-[8].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 15570176 2560 part-[12].img
Nvflash started
[resume mode]
sending file: part-[12].img
/ 5242880/5242880 bytes sent
part-[12].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 15572736 2560 part-[13].img
Nvflash started
[resume mode]
sending file: part-[13].img
/ 5242880/5242880 bytes sent
part-[13].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 15575296 1024 part-[14].img
Nvflash started
[resume mode]
sending file: part-[14].img
/ 2097152/2097152 bytes sent
part-[14].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 15576320 2048 part-[15].img
Nvflash started
[resume mode]
sending file: part-[15].img
/ 4194304/4194304 bytes sent
part-[15].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 15578368 49152 part-[16].img
Nvflash started
[resume mode]
sending file: part-[16].img
/ 100663296/100663296 bytes sent
part-[16].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 15627520 2560 part-[17].img
Nvflash started
[resume mode]
sending file: part-[17].img
/ 5242880/5242880 bytes sent
part-[17].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite 15630080 256 part-[18].img
Nvflash started
[resume mode]
sending file: part-[18].img
/ 524288/524288 bytes sent
part-[18].img sent successfully
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash# ./nvflash -r --sync
Nvflash started
[resume mode]
[email protected]:/home/dryasdust1/download/gs/linux4tegra/nvflash#
-----------------------------------------------
all done.
but my pad still use only apx boot mode.
thanks bro!!
finally succeed !!
thanks..
Congratulation !
I'm stuck on "rawdevicewrite"!!! Pls advise.
I have G-Slate from T-Mobile (LG-V909DW)
I did the same but under WinXP OS.
fastboot.stock.bin loaded succesfully!!!
c:\tmp\LGV909DW\nvflash>nvflash --bl fastboot.stock.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0280404040a05297
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.stock.bin
| 936016/936016 bytes sent
fastboot.stock.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
But then the device freezes when rawdevicewrite.
c:\tmp\LGV909DW\nvflash>nvflash -r --rawdevicewrite 0 1536 part2_bct.img
Nvflash started
[resume mode]
Pls help!!!
Finally my G-Slate has been restored!!!
Many thx for the instruction.
BTW. If somebody needs, I may share how to restore partitions.
Congratulation ! Your wellcome
Sent from my L-06C using XDA Premium App
thanks for this...
just a question.. are you guys familiar with supercharge v6? it says that it works also for tablets, maybe true but not with our slate because its bootloader is locked?
im not encouraging Gslate owners to try it without confirming with a developer that it will work guaranteed..
---------- Post added at 09:23 PM ---------- Previous post was at 09:21 PM ----------
i think I need to pull my device's partition for future reference, just in case hehe..
Holy Moses, I had mega-bricked mine too (APX-only). Thank god these directions were here, but they were confusing because they're slightly off, at least for me. I followed the instructions like 3 times before I realized it wasn't doing anything.
Since I HATE searching and finding and finding threads that end with "Figured it out!" or "Fixed it!" but without an explanation, here's how I made it work for me (Gslate) (if the OP doesn't work for you either):
(G-Slate V909)
-Download and extract the 3 .rar files (from mediafire) into a directory. I named mine 'img' so I didn't have to type much
-Download and extract the 'linux4tegra_10.9.3.rar' file (from mediafire) to a separate folder. Open /linux4tegra_10.9.3/nvflash/ and copy 'nvflash' to your 'img' folder.
-Download and extract the contents of the 'gslate_root.zip' file (from the lgv909 wiki on Google Code) to your 'img' folder.
-”Boot your Gslate into APX mode” If you're boot-looping like me, or another form of bricks-ville you can put it in APX mode by holding down the Volume Up and Volume Down buttons while you press the reset button with a paperclip. Count to 6 then let go of the Volume buttons.
-Open Terminal, and type 'sudo su' (without quotes), and your password to get root shell
-Type 'lsusb' to verify you're connected (like in the OP).
-Type './nvflash --bl bootloader.bin --getpartitiontable ptable.txt' and follow the op regarding the information in the text file created. (mine was the exact same as the hosted version)
-Type './nvflash --bl fastboot.bin –go' (vanilla bootloader, no library-stuff)
-For the image files, the string in the OP is a little different, type ./nvflash -r --rawdevicewrite [StartSector] [NumSectors] part[PartitionId]_[name].img (no brackets, no library stuff). The files are named differently now.
-Type './nvflash -r –sync'
-Press the reset button on the back with a paperclip
-Yay the light! Yay LG logo! Yay bootloader! Yay bootloader, again!
-If you bootloop like me, do this:
-Holding the Volume Up button, press the reset button on the back with a paperclip, to enter fastboot mode.
-Type './fastboot oem unlock' then './fastboot -w' (like in the op) to wipe userdata and cache
-Type ./fastboot reboot
-Welcome to Un-bricks-ville
i have g slate and bricked
when type ./nvflash -bl bootloader.bin then comes
comes "0x4" error
and usb disconnected..
any solution plz for that ..
malak_1239 said:
i have g slate and bricked
when type ./nvflash -bl bootloader.bin then comes
comes "0x4" error
and usb disconnected..
any solution plz for that ..
Click to expand...
Click to collapse
yeah im in the same boat.
The links are locked with password
Can you provide it?
And would it unlock the master password i accidentally locked it with a password after i did factory reset... its stuck/bricked
guys gslate forum so you can place all your stuff in one plac e
http://android-dev.us/viewforum.php?f=48
Mediafire.com password
tuananhnt said:
My LG Docomo L-06C (Android 3.0) had been bricked by format all partitions, it just connected to PC with APX mode. I want to share steps that i did to unbrick it:
STEP 1:
- You must have all partitions backup files: (Notice: Those files restore for Android 3.0 with ./nvflash)
http://www.mediafire.com/file/6v2sct03t6fhgcp/lg_gslate_stock_image.part1.rar
http://www.mediafire.com/file/wvn4x3xujudmt1w/lg_gslate_stock_image.part2.rar
http://www.mediafire.com/file/61cub2by19lqo6m/lg_gslate_stock_image.part3.rar
Restoring: (I used Urbuntu)
-Put those backup files in a directory include nvflash and open a terminal to there.
-Plug it into your computer via USB.
-Running "lsusb" should show an entry "0955:7820 NVidia Corp."
Run the command "sudo su" to get a root shell. Running "ls" should still show the four files.
./nvflash --bl bootloader.bin --getpartitiontable ptable.txt
View attachment 764776
In the ptable.txt, you should see following pattern (you need the highlighted values for each partition you want to restore):
PartitionId=[PartitionId]
Name=...
DeviceId=18
StartSector=[StartSector]
NumSectors=[NumSectors]
BytesPerSector=2048
Open a terminal and change to the following directory: linux4tegra/nvflash (you can download them in http://code.google.com/p/lg-v909/wiki/Restore_to_Stock and fastboot.bin file in http://www.mediafire.com/file/6v4si33olrt5x9o/linux4tegra_10.9.3.rar)
Reload the vanilla bootloader using the following command:
# LD_LIBRARY_PATH=. ./nvflash --bl fastboot.bin --go
For earch part-[PartitionId].img you want to restore, execute the following command:
# LD_LIBRARY_PATH=. ./nvflash -r --rawdevicewrite [StartSector] [NumSectors] part-[PartitionId].img
- Do it from part2 to part18 (part9, 10, 11 not to need restore)
- part8.img in lg_gslate_stock_image.rar file is t-mobile system. If your pad is Docomo L-06C, you can use my docomo_system.img to replace part8.img
http://www.mediafire.com/file/7g18k95m5w4ombg/docomo_system_part8.part1.rar
http://www.mediafire.com/file/4hbpboatbarbot9/docomo_system_part8.part2.rar
./nvflash -r --sync
Reboot your device.
STEP 2: If gslate show password screen after boot:
- Boot the slate into fastboot mode by turning it off, then holding the volume button and power button down untill it says "entering fastboot protocol"....
- Then open a terminal or cmd prompt (folder include fastboot) on your PC and with the slate pugged into USB type:
fastboot oem unlock
fastboot -w (format all userdata)
Reboot and your all set
** With G-Slate runing Android 3.1, the bootloader.bin is locked (so you can't use ./nvflash). I'm not sure can use "dd method" to restore it, i'll post this then and you can try
You can join: irc.freenode.net / #g-slate (mIRC) to ask questions about it !
GOODLUCK !
Click to expand...
Click to collapse
Can you please let us know what the Mediafire.com password is to access the backup partitions?
stuck on waiting for bootloader to initialize
malak_1239 said:
i have g slate and bricked
when type ./nvflash -bl bootloader.bin then comes
comes "0x4" error
and usb disconnected..
any solution plz for that ..
Click to expand...
Click to collapse
Please append --sbk paramete and try again .
and I will told you the SBK value is
--sbk 0xe3baffc6 0xa9585c23 0xe21b497b 0x793d1932.
we have a locked pad, hope the sbk value can help you unbricked successfully
But my pad(l06c) still stuck on 'waiting for bootloader to initialize' via nvflash. Who can help me?
thank you
Please help restore the stock firmware.
Last time I figured Andorid 3.1 in this version of bootloader.bin is locked and can't use ./nvflash,
but how to restore "Restore to stock" h..p://code.google.com/p/lg-v909/wiki/Restore_to_Stock necessarily to execute:
nvflash-bl-bootloader.bin-getpartitiontable-ptable.txt
nvflash-r-format_partition-8
nvflash-r-8-download system.img
nvflash-r-sync
Unfortunately on the first step nvflash-bl-bootloader.bin-getpartitiontable-ptable.txt
generates an error:
Nvflash started
rcm version 0X4
The send Command failed (usb write failed)
tell me please how can I solve this problem please help revitalize the g-slate!!!!!
now it won't boot and hangs at boot, can see only the icon "LG"
PLEASE HELP!!!!!!
taren said:
Please help restore the stock firmware.
Last time I figured Andorid 3.1 in this version of bootloader.bin is locked and can't use ./nvflash,
but how to restore "Restore to stock" h..p://code.google.com/p/lg-v909/wiki/Restore_to_Stock necessarily to execute:
nvflash-bl-bootloader.bin-getpartitiontable-ptable.txt
nvflash-r-format_partition-8
nvflash-r-8-download system.img
nvflash-r-sync
Unfortunately on the first step nvflash-bl-bootloader.bin-getpartitiontable-ptable.txt
generates an error:
Nvflash started
rcm version 0X4
The send Command failed (usb write failed)
tell me please how can I solve this problem please help revitalize the g-slate!!!!!
now it won't boot and hangs at boot, can see only the icon "LG"
PLEASE HELP!!!!!!
Click to expand...
Click to collapse
Hi, Please reconnect APX mode then type "--sbk 0xe3baffc6 0xa9585c23 0xe21b497b 0x793d1932" append to you nvflash command.
wHuibo said:
Hi, Please reconnect APX mode then type "--sbk 0xe3baffc6 0xa9585c23 0xe21b497b 0x793d1932" append to you nvflash command.
Click to expand...
Click to collapse
Hi i need this script if existe to run on XP dont have linux instaled thanks
Br
E:\nvflash>nvflash --bl bootloader.bin --sbk 0xe3baffc6 0xa9585c23 0xe21b497b 0x
793d1932 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0288414940004457
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
---------- Post added at 05:45 AM ---------- Previous post was at 05:27 AM ----------
how backup L-06C stock

[Q] S4 Root on Mac

I just got the S4 brand new and now im trying to root it.
Ive tried the mottochopper and it installs Super user but when I open it, it says the superuser binary (su) must be updated. and when I click install it says that there was an error installing.
So what should I do now?
I made a tutorial for this: http://forum.xda-developers.com/showthread.php?t=2442262
theexel said:
I made a tutorial for this: http://forum.xda-developers.com/showthread.php?t=2442262
Click to expand...
Click to collapse
Thanks for the reply.. Ive tried this too and in terminal i get this:
Chases-MacBook-Pro:~ ChasePierce$ sudo heimdall flash --recovery untitled \Users\chasepierce\Desktop\recovery.img--cache untitled\Users\chasepierce\Desktop\cache.img.ext4
Password:
Sorry, try again.
Password:
Invalid argument: UserschasepierceDesktoprecovery.img--cache
Action: flash
Arguments:
--repartition --pit <filename>
--<partition name>|--<partition identifier> <filename> [...]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
or:
--<partition name>|--<partition identifier> <filename> [...]
[--pit <filename>]
[--verbose] [--no-reboot] [--stdout-errors] [--delay <ms>]
[--usb-log-level <none/error/warning/debug>]
Description: Flashes one or more firmware files to your phone. Partition names
(or identifiers) can be obtained by executing the print-pit action.
WARNING: If you're repartitioning it's strongly recommended you specify
all files at your disposal.
Run this:
sudo heimdall flash --RECOVERY Users/chasepierce/Desktop/recovery.img --CACHE Users/chasepierce/Desktop/cache.img.ext4
Or I'd be more than happy to help you out over TeamViewer as I myself have a mac.
theexel said:
Run this:
sudo heimdall flash --RECOVERY Users/chasepierce/Desktop/recovery.img --CACHE Users/chasepierce/Desktop/cache.img.ext4
Or I'd be more than happy to help you out over TeamViewer as I myself have a mac.
Click to expand...
Click to collapse
That would be rad!
ChaseSTi said:
That would be rad!
Click to expand...
Click to collapse
PM sent.
theexel said:
PM sent.
Click to expand...
Click to collapse
Thank you soo much!

The truth and misunderstanding about how to build Odin .tar.md5

The truth and misunderstanding about how to build Odin .tar.md5
Cygwin "md5sum -t" command is not text mode. But it's binary mode and doesn't display * in front of the filename.
Gnuwin "md5sum" or "md5sum -b" commands will append \r (carriage return) to the output.
Odin accept * or without * in front of the filename. But md5sum must be binary mode.
Odin doesn't accept \r (carriage return) at the end of file.
No need to use "tar -H ustar" option.
The valid commands are:
Code:
tar -cvf rom_name_v69.tar rom_name_v69.img
md5sum -b rom_name_v69.tar | tr -d '\r' >> rom_name_v69.tar
mv rom_name_v69.tar rom_name_v69.tar.md5

Categories

Resources