I rooted the phone and installed the recovery image using nvflash,
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: ----- removed --------
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.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery-star-test2.img
\ 4306944/4306944 bytes sent
recovery-star-test2.img sent successfully
After that I try to boot into recovery and I get /!\ and andriod logo, I dont see the CWR menu. Can some one please help. I repeated the nvflash process a few times and I get the same result. But I am able to boot into the stock Andriod (2.2) just fine.
I have also tried the ext4 version
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: --- removed ---
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.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: p999-4.0.0.2-external-recovery.img
| 3565568/3565568 bytes sent
p999-4.0.0.2-external-recovery.img sent successfully
and when I go to ROM Manager and select boot to recovery, I see the new splash screen, and then /!\ with green logo. No CWR menus.
With phone off, hold volume down and power. Keep holding until you get past the initial LG boot screen then let go. It should drop you into CWM.
Btw, forget about Rom Manager.
Related
Hey guys,
I was tired and on accidentally put the most recent clockwork recovery onto my G-tab when i was reinstalling the Vegantab 5.1 Rom.
After the install it rebooted into a black screen that said "Magic Number Mismatch:" in red.
I have used NVflash before and I went ahead and reinstalled clockwork v08 Bekit.
I got this message:
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvflash --bl boot
loader.bin --download 9 clockwork.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x171440424380b1d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: clockwork.img
| 3862528/3862528 bytes sent
clockwork.img sent successfully
Even after this the device still gives me the "Magic Number Mismatch:" message.
I read the other threads and none of those solutions worked, nor did most of them apply to me since I can't even boot into clockwork.
any help would be appreciated
You will need to flash the "recovery partition" using nvflash.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Thanks man! That did the trick.
From there i was able to reflash the older version of clockwork and my ROM.
Hi,
If anyone has tried, but had problems retrieving the BCT (boot configuration table) from their Gtab, FYI, I was able to use nvflash to get the BCT from my Gtab! When I had tried previously, I kept getting an error saying that the command didn't exist.
I think that the "trick" is that you HAVE TO do it on the same/FIRST command line where you send the boot loader to the Gtab, i.e., it looks like --getbct doesn't work when you do a --resume/-r. Here's my outputs:
Windows:
=======
E:\Ziptemp\Viewsonic-BEKIT-RESTORE\Windows>nvflash --bl bootloader.bin --getbct --bct jl-bct-win.bct --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714404641e0f5d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
retrieving bct into: jl-bct-win.bct
jl-bct-win.bct received successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
E:\Ziptemp\Viewsonic-BEKIT-RESTORE\Windows>dir
.
.
01/29/2011 03:08 PM 4,080 jl-bct-win.bct
Ubuntu:
======
[email protected]:/nvflash# ./nvflash --bl bootloader.bin --getbct --bct jl-bct.bct --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714404641e0f5d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
retrieving bct into: jl-bct.bct
jl-bct.bct received successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
[email protected]:/nvflash# ls -al
.
.
-rw-r--r-- 1 root root 4080 2011-01-29 11:56 jl-bct.bct
.
.
You'll notice that the .bct files in both cases are 4080 bytes, so I think it's the "real" BCT (not the partition that is labelled as "BCT" in the partition table). That (4080 bytes) is the same size as the ones in Bekit's dropbox.
For the above, I used the nvflash/nvflash.exe from Bekit's dropbox in both cases. I'm assuming it'd work the same with the nvflash from the Nvidia SDK also...
[Note: per another thread:
1) nvflash.exe --getpartitiontable using nvflash.exe from Bekit's dropbox outputs binary
2) nvflash.exe --getpartitiontable using nvflash.exe from the Nvidia SDK outputs text
1) (Linux) nvflash --getpartitiontable using nvflash.exe from Bekit's dropbox outputs text
]
The bootloader.bin was also the one from Bekit's dropbox.
FYI, how to get this working was actually "hinted at" by tcrews in a thread (search for "guidance" in this forum). I had seen it, but hadn't paid much attention, but I noticed this morning that he had the --bl on the same command line, so figured I'd try that.
Jim
I am a Venezuelan citizen and in my country buy a (GEO-ecopc) tablet.
The tablet data are:
Processor: nVidia Tegra-2 250 1 GHz (T20)
DRAM: 1 Gb DDR2 (H5PS2G83AFR-S6C (DDR2 256Mx8))
Hard Disk: 16 Gb emmc-nand (Kingston KE4BT4B6A)
Screen: 10.1" Capacitive Multi Touch (1280x800)
Android: v2.2 (Kernel: 2.6.32.9)
Name: Ventana
Model: N10G
MCU: 1.70.2
Please I need help.
When I use the nVFlash get this error:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 2
chip sku: 0x8
chip uid: 0x170061844300e257
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: GEO_ecopc.bct
- 4080/4080 bytes sent
GEO_ecopc.bct sent successfully
odm data: 0x360d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
\ 906888/906888 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
failed executing command 17 NvError 0x120002
command failure: create failed (bad data)
bootloader status: BCT is full; no more bootloaders can be added (code: 16) message: nverror:0x4 (0x4) flags: 0
I love my tablet but, I can not unbrick. Please helpme...
keep getting messages like===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
EXT4 Internal SD Support by TeamWhiskey
Version 4.0.1.5
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x037c710643412257
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.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
===============================================================
===============================================================)
have attempted several variants 20 times or so each. same result. Am I straight up root blocked at this point or is there some other evil magic I could perhaps attempt>? -Cheers, -G
Are you holding the volume buttons down the whole time or letting them go after the computer recognizes the device as a nvidia boot device?
Also, what version of Windows are you on?
Also, have you tried installing the 5.0.2.0 version of CWM?
Also, try using volk's Batch Cleanup Tool. I've had success with it when regular nvflash didn't work.
Sent from my LG-P999 using xda app-developers app
Moved to proper forum.
Hello
I have a ZTE Grand X.
Last night I wanted to get it out of standby (just press te power button) but that didn't work.
When I connect it to my computer it sais 'Unknow XPA Device'.
I tried all the button combinations already. NVFlasher detects the device but says that it can't find the bootloader.
(I got the drivers from here: modaco[dot]com /topic/335416-nvflash-setup-instructions-drivers-links-active/ (Sorry, not enough posts to make a link)
Any help?
Thank you!
Help?
Anyone who has a clue?
I'm getting nothing out of this phone, except the information about the chip and stuff (when I run 'nvflash --sync').
I have experience with a whole lot of flashing, but not with NVFlasher...
Help, please?
Thanks in advance!
bootloader.bin
Alright, after some searching I think I've found out how to flash the whole thing.
Not sure if it's going to work and if it does, if it's going to fix my problem.
I just need the bootloader.bin for my device (ZTE Grand X (V970)).
I hope someone responds now.
Bump... I really don't want to just throw my phone away.
Bump
bump bump bump
I've been on this forum for a long time (just surfing, not posting) and know there are a lot of talented/smart people here.
Why isn't anyone helping?
Hello, i have more problems with that phone.
I can provide the bootloader.bin, but i will not take any responsibility for it.
My problem is this, Grand X ofc stuck in APX mode, and can not download bootloader at all ! Cannot repartition memory to, can not do nothing, except sync
Here are the posts from nvflash, can someone HELP ?! Can it be helped at all ?
Code:
C:\NVFLASH\nvflash>nvflash --sync
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x04507204405fc157
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 1
command failure: no bootloader was specified
Code:
C:\NVFLASH\nvflash>nvflash --bct flash.bct --setbct --odmdata 0x80098011 --confi
gfile flash-v0901.cfg --create --bl bootloader.bin
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x04507204405fc157
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 1
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
command failure: bootloader download failed (bad data)
bootloader status: device failure (code: 2) message: flags: 0
having the same problem , need help please am stack in the APX MODE