[Q] CM7 works, CWM stuck on recovery key detected - G Tablet Q&A, Help & Troubleshooting

So, I didn't flash this originally, and it still boots into CM7 just fine. ROM Manager is installed, it says CWM is successfully flashed and all, but any attempt to boot into recovery will just sit at "Recovery key detected. Booting recovery kernel image."
Obviously the current ROM itself is actually working fine, so what would you suggest be my next step?
Trying to put Flashback 10.3 on it.
Current Recovery: 2.5.1.8
Current ROM: CyanogenMod-7.0.3-Harmony

---

1. Never use ROM Manager on the gTab.
2. You're on a 1.1 bootloader. Flashback is for 1.2 only. If you want HoneyComb for 1.1, try GtabCombOver or GtabComb.
3. To get CWM back, you'll have to use nvflash. Use bekit's original CWM 2.5.1.1-bekit-0.8 or CWM-4.0.1.5 images (ie. not the flashable zip files). See the OP in this thread for the nvflash cmd line to use.

---

Thanks for the advice. I'm just now coming to terms with this company not having a Micro-USB cable... >.<

---

Okay, so my screen is blank when in APX mode, it seems. I'm running NVFlash though, and I just have:
Nvflash started
_
It's been that way over an hour now. Tablet doesn't seem to be doing anything, neither does Command Prompt... just a blinking underscore.
Canceled it... retried it... worked quickly (bootloader and recovery "sent succesfully", not sure why it hung up last time. Doesn't look like it's booting into recovery though, it's just hanging on the Viewsonic screen with the "Booting recovery kernel image" like before.
Are you sure I have the 1.1 bootloader? Without stock, how can I tell?

---

ocdtrekkie said:
Doesn't look like it's booting into recovery though, it's just hanging on the Viewsonic screen with the "Booting recovery kernel image" like before.
Click to expand...
Click to collapse
What's the nvflash command you typed in and which recovery image did you flash?
Are you sure I have the 1.1 bootloader? Without stock, how can I tell?
Click to expand...
Click to collapse
Like this.

---

nvflash --bl bootloader.bin --download 9 recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img
^- that one.
Not sure if I have a way to get a terminal emulator on this thing. And I don't have ADB here. Lemme see what I can manage.

---

That command line is correct. Put the tablet back into APX mode and run this command:
Code:
C:\> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go[/B]
The ``--go'' flag will cause bootloader to try to boot into the ROM; otherwise it will just wait for further commands and you'll have to power off the tablet.
If you lose the initial splash screen (the VS birds), then run the same command with a `6' instead of `7'.

---

Partitions formatted successfully, Go didn't seem to tell it to do anything, still had to turn it off. Still have birds, still won't boot into recovery.
Command prompt paste:
c:\Users\jweisz\Desktop\nvflash>nvflash --bl bootloader.bin --download 9 recover
y-clockwork-4.0.1.5-smb_a1002_bl1.1.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144040411fa297
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: recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img
\ 3524608/3524608 bytes sent
recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img sent successfully
c:\Users\jweisz\Desktop\nvflash>.\nvflash --bl bootloader.bin --format_partition
7 --format_partition 12 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144040411fa297
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
Formatting partition 7 please wait.. done!
Formatting partition 12 please wait.. done!

---

Questions:
1. Did the initial splash screen vanish?
2. Can you boot into the ROM?
3. What's the output of the ``dmesg | fgrep ...'' command? CM-7.0.3 should have everything you need to type that command in a Terminal Emulator window and find out the bootloader version.

---

CM7 has a terminal? Probably shoulda checked for that! LOL!
Yeah, it's gotta be that I have 1.2
<7>[ 5.794813] Shmoo: s_CpuShmoo.ShmooVmaxIndex = 8

---

Alright, now I have recovery. See, you got me lost here:
rajeevvp said:
2. You're on a 1.1 bootloader. Flashback is for 1.2 only. If you want HoneyComb for 1.1, try GtabCombOver or GtabComb.
Click to expand...
Click to collapse
So... Flashback it is then, I guess.

---

Did you flash a customized CM-7.0.3 for the 1.2 bootloader because the standard one from cyanogenmod.com is 1.1 only?
Anyway, nvflash the 1.2 version of CWM-4.0.1.5.

---

I didn't flash the CM7 that was on here. Couldn't tell you.
Flashback works well on here. Thanks for all your help. Most of the time if I get a question reply from someone, they give one answer, then never come back to follow up. You're awesome.

---

ocdtrekkie said:
I didn't flash the CM7 that was on here. Couldn't tell you.
Click to expand...
Click to collapse
Then yours is a one-off. There are 1.2 versions of both CM-7.1.x and CM-7.2.x on the board here, but, I never encountered CM-7.0.3 on a 1.2 bootloader till today. Looks like somebody upgraded to the 1.2 bootloader and then flashed a 1.2 pershoot kernel before handing the tab over to you.
Flashback works well on here. Thanks for all your help.
Click to expand...
Click to collapse
Good luck with your new ROM.