[Android Head-Units] pdanders11:
I think I found a reliable way to get adb in normal mode. Your buuld.prop matches mine and new lines do the job when push at the right time which wasn't clearly documented.

So here is what seems to works for me. I may be wrong but first time I've had shell in awhile.

1 - Do a clean install of Firmware 1.5. Don't mess with pushing build.prop or anything.

2 - Running a clean 1.5 should give you the Kenwood USB device over OTG but (but no devices will show as USB debugging is off).

3 - edit the build.prop from the zip and add the lines as DonaldTa says in post ?? or use the one [MENTION=2301266]aplusmiami[/MENTION] posted.

now this seems the easiest for me. Faster then a whole flash sequence

4 - take firmware 1.3 and corrupt the zip. IE pull out build.prop and edit a single character and drop it back in the zip

5 - load the 1.3 Firmware files with the corrupted/tampered zip/kw on a thumb drive.

6 - put the drive in radio and for whatever reason the 1.3 firmware kicks off the update just plugging it in so no menu stuff.

7 - Radio will reboot and start updating. Use a USB stick with a LED to see it is transferring. So here is "window 1". the radio is scanning the drive for modified files (which it will find but it takes a bit), adb is open.

7 a - adb root

7 b - adb push build.prop /system

7 c - wait for dead Android guy on screen indicating the signature check failed. I've seen the device go adb offline or stay online here. Anyway you have to push before the Android guy pops up and dies.

8 - time for the radio to reboot and do rebuild 1 of 2.

8 a - After the Android guy shows at your leisure (unless the radio timeouts at some point) pull the thumb drive. I think chances of brick here are near 0 but I like seeing the LED on the drive being off

8 b - pulling the drive will cause a reboot (if you try this with FW 1.5- the radio auto reboots making it a little scary when to pull the drive - if it reboots and starts another upgrade DON"T PULL THE drive. just stick with 1.3. No auto reboot. Pulling the drive has little risk.

8 c - you pulled the drive. radio reboots and starts rebuild 1 of 2

8 d - Here is window # 2 when ADB is open. This is the critical one

this time

adb root

adb remount

adb push build.prop /system

Your done.

Let the rebuild finish. The radio will reboot and do rebuild 2 of 2. ADB is not open here so just wait. When it's all done adb over OTG should be 'good to go' in normal mode.

If you just push in "Window 1" you get wierd stuff like we've posted. Disappearing devices. Unknown devices. etc. a push in "Window 1" may not even be needed. What has been hanging me up is not pushing in "Window 2". Not pushing in window 2 will show USB debugging menu in the radio but adb is dead so you think your build.prop must be good so you blame everything else (like the cable :)

The key is the push in "Window 2" and the "adb remount" as the NAND is Read only.

Not sure that makes sense but it's not only what you push it's when you push it. The two "rebuild" steps deal with the build.prop differently. Seems like rebuild one breaks somethig but leaves some adb intact to confuse you so you have to push again before rebuild 2.

So normal a normal 1.3 corrupted firmware update looks like this

1 - drive scan - radio

2 - signature fail - radio

3 - green man - radio

4 - you pull the stick - you

5 - rebuild #1 - radio

6 - rebuild #2 - radio

Back to 1.5

Key points in time

- step 1 - ADB open

- Step 5 - ADB open

Adb will be available if you push build.prop during rebuild 1. not sure if push a step 1 is needed but doesn't hurt.