[ROOT][UNROOT][CWM RECOVERY][STOCK KERNEL][STOCK RECOVERY] Google ADT-1 Android TV

[Dees_Troy]

Well, TWRP didn't have mouse/keyboard support last I checked. So I'll work with it. But Philz Touch recovery or cannibal open touch should be both cool and doable.

Edit: TWRP has mouse & keyboard support and is possible, but requires a bit more work than is worth it right now.

CWM also has iffy support for OTA's I am finding, hit or miss, try at your own risk.

CWM also has the ADB sideload ability...... that's how you have to flash the SuperSU mentioned in the OP

TWRP has had mouse support since 2.7.0.0 and keyboard support for even longer.

Supporting OTA updates has little to do with the custom recovery and more to do with the fact that any modification that you make to your device can break the OTA process. It's gotten worse in 5.0 where even the act of mounting the system partition as read/write can "break" the OTA process.

 

[npjohnson]

TWRP has had mouse support since 2.7.0.0 and keyboard support for even longer.

Supporting OTA updates has little to do with the custom recovery and more to do with the fact that any modification that you make to your device can break the OTA process. It's gotten worse in 5.0 where even the act of mounting the system partition as read/write can "break" the OTA process.

That's what the edit was for [emoji14]

When I wrote that post, I knew a considerable bit less about building android/recoveries than I do now. Haha.

 

[halfluck]

Hey Guys,

Does anyone have Stock boot.img for ADT-1 LRX22G 5.0.2?

Cheers Rob.

 

[npjohnson]

Hey Guys,

Does anyone have Stock boot.img for ADT-1 LRX22G 5.0.2?

Cheers Rob.

PM Me this weekend and I can get one.

 

[EvgeniX]

Hi,

Can some one re-upload Stock Recovery Image LPX13D pls?

 

[toebee76]

Hoping someone can help me out. I fear I may have turned my adt-1 into a brick. I was in the process of rooting. I did the Fastboot boot process and my unit has been stuck on the android logo ever since. I went back and downloaded the image again and it is a different file size than the first one I flashed. I think I flashed a bad image. Now it will not recognize it as an adb device. Am I screwed?

Also tried holding down the button on the back but it just sits on the android logo.

 

[mskip]

Hoping someone can help me out. I fear I may have turned my adt-1 into a brick. I was in the process of rooting. I did the Fastboot boot process and my unit has been stuck on the android logo ever since. I went back and downloaded the image again and it is a different file size than the first one I flashed. I think I flashed a bad image. Now it will not recognize it as an adb device. Am I screwed?

Also tried holding down the button on the back but it just sits on the android logo.

You haven't hard bricked it. You need to reboot directly to fastboot mode and flash the stock image back to your device. Even flashing just the system image should fix it so you could extract the system image from the stock file and then fastboot flash system system.img whilst in the fastboot screen.

Mark.

 

[toebee76]

You haven't hard bricked it. You need to reboot directly to fastboot mode and flash the stock image back to your device. Even flashing just the system image should fix it so you could extract the system image from the stock file and then fastboot flash system system.img whilst in the fastboot screen.

Mark.

Hi Mark thanks for taking the time to reply. I appreciate it. I don't know how to get back to fastboot mode. It will no longer show up as an adb device. Is there another way to get into fastboot mode?

 

[npjohnson]

Hi Mark thanks for taking the time to reply. I appreciate it. I don't know how to get back to fastboot mode. It will no longer show up as an adb device. Is there another way to get into fastboot mode?

Unplug and replug whilst holding the button on the back.

 

[toebee76]

Unplug and replug whilst holding the button on the back.

Thank you so much for this. Much appreciated. I am able to get to the bootloader which makes me feel somewhat better. However I still can't connect via adb. My pc shows it is connected to fastboot but adb detects no devices. If I use the button on the back of the device I can scroll down to fastboot protocol and select it. Then it says its "erasing" before just going to a black screen. After that it just stays like that. The lights still on but no video output to the TV. I tried re-installing drivers but it didn't help. I don't know how I can flash anything from here without adb. Any suggestions? Thanks again.

**More info**
If I adb "fastboot devices" it shows it's connected.

If I try to "fastboot flash boot boot.img" I get a "Failed <command write failed<no such device or address>>

 

[mskip]

Thank you so much for this. Much appreciated. I am able to get to the bootloader which makes me feel somewhat better. However I still can't connect via adb. My pc shows it is connected to fastboot but adb detects no devices. If I use the button on the back of the device I can scroll down to fastboot protocol and select it. Then it says its "erasing" before just going to a black screen. After that it just stays like that. The lights still on but no video output to the TV. I tried re-installing drivers but it didn't help. I don't know how I can flash anything from here without adb. Any suggestions? Thanks again.

**More info**
If I adb "fastboot devices" it shows it's connected.

If I try to "fastboot flash boot boot.img" I get a "Failed <command write failed<no such device or address>>

When the device is in fastboot mode you do not use adb for any commands you use fastboot. Adb is for when your device is booted in to Android.

Download the stock image, open it with winrar, winzip, 7zip, then open the zip file inside and extract the system.img file to your pc (same folder that has adb and fastboot files).
Reboot the device manually to fastboot.
Open a command prompt from the folder that has adb/fastboot files (browse to the folder in windows explorer, hold shift and right click and select "open command prompt here".
Type fastboot devices and if you see a serial number then the device is connected.
Type fastboot flash system system.img to flash the system image to the device.
Wait for it to finish.
Type fastboot reboot to reboot the device and it should boot.

Mark.

 

[toebee76]

When the device is in fastboot mode you do not use adb for any commands you use fastboot. Adb is for when your device is booted in to Android.

Download the stock image, open it with winrar, winzip, 7zip, then open the zip file inside and extract the system.img file to your pc (same folder that has adb and fastboot files).
Reboot the device manually to fastboot.
Open a command prompt from the folder that has adb/fastboot files (browse to the folder in windows explorer, hold shift and right click and select "open command prompt here".
Type fastboot devices and if you see a serial number then the device is connected.
Type fastboot flash system system.img to flash the system image to the device.
Wait for it to finish.
Type fastboot reboot to reboot the device and it should boot.

Mark.

Thank you for the instructions Mark. I was reading about the difference of fastboot and adb this morning. I have a much better understanding now. I am having trouble finding a few files. First where is the stock image? I thought maybe you meant the files in the op or maybe the file here http://forum.xda-developers.com/har...t/adt1-stock-molly-images-unbricking-t2927888 however none of them have the contents you mentioned. Been googling but haven't found anything with the contents you mentioned. Also while trying to find my own solution last night I flashed the custom recovery in the OP, but could not flash SuperSu because adb still isn't working. Should I revert back to a stock recovery before flashing the system.img? If so where is the stock recovery? The link is no longer working in the op.

(I know it's not much but hopefully the donation will buy you a coffee or a beer)

 

[npjohnson]

Thank you for the instructions Mark. I was reading about the difference of fastboot and adb this morning. I have a much better understanding now. I am having trouble finding a few files. First where is the stock image? I thought maybe you meant the files in the op or maybe the file here http://forum.xda-developers.com/har...t/adt1-stock-molly-images-unbricking-t2927888 however none of them have the contents you mentioned. Been googling but haven't found anything with the contents you mentioned. Also while trying to find my own solution last night I flashed the custom recovery in the OP, but could not flash SuperSu because adb still isn't working. Should I revert back to a stock recovery before flashing the system.img? If so where is the stock recovery? The link is no longer working in the op.

(I know it's not much but hopefully the donation will buy you a coffee or a beer)

Get to this site and download this: http://coggy.euroskank.com/LatestADTSystem.zip

Then Download the CWM Recovery in OP, and boot it from fastboot by issuing "fastboot boot whateveryourrecoveryiscalled.img" OP

Then, use the HW button on the device (quick press move, long press select) to select install zip, then choose from adb, then adb sideload the first zip.

You'll be on Stock 5.0.2, and if you want root, just side load the SuperSU zip after using flashing the other zip (preferably before rebooting).

 

[toebee76]

Get to this site and download this: http://coggy.euroskank.com/LatestADTSystem.zip

Then Download the CWM Recovery in OP, and boot it from fastboot by issuing "fastboot boot whateveryourrecoveryiscalled.img" OP

Then, use the HW button on the device (quick press move, long press select) to select install zip, then choose from adb, then adb sideload the first zip.

You'll be on Stock 5.0.2, and if you want root, just side load the SuperSU zip after using flashing the other zip (preferably before rebooting).

Thanks for the link npjohnson. Unfortunately I have't gotten adb to work since I flashed the bad image. It is showing molly in my device manager under other devices like it has no drivers. I have tried installing the drivers again but no change. Is it possible that my adb isn't working because I flashed a bad image?

Download the stock image

Is this the stock image you mentioned? http://coggy.euroskank.com/LatestADTSystem.zip I tried to flash the system.img from it but it gave me the error "target reported max download size of 577100 bytes Invalid sparse file format at header magi"

---------- Post added at 04:33 PM ---------- Previous post was at 04:04 PM ----------

I think I have it guys. I flashed the stock boot then recovery and I just now got to the welcome screen! Man I thought this thing was dead thank you so much for the help!

 

[mskip]

Thanks for the link npjohnson. Unfortunately I have't gotten adb to work since I flashed the bad image. It is showing molly in my device manager under other devices like it has no drivers. I have tried installing the drivers again but no change. Is it possible that my adb isn't working because I flashed a bad image?


Is this the stock image you mentioned? http://coggy.euroskank.com/LatestADTSystem.zip I tried to flash the system.img from it but it gave me the error "target reported max download size of 577100 bytes Invalid sparse file format at header magi"

---------- Post added at 04:33 PM ---------- Previous post was at 04:04 PM ----------

I think I have it guys. I flashed the stock boot then recovery and I just now got to the welcome screen! Man I thought this thing was dead thank you so much for the help!

Glad you got it working again. Keep hold of the Stock image just in case you need it again.

Mark.

 

[rgill420]

You haven't hard bricked it. You need to reboot directly to fastboot mode and flash the stock image back to your device. Even flashing just the system image should fix it so you could extract the system image from the stock file and then fastboot flash system system.img whilst in the fastboot screen.

Mark.

Mark, i had a quick question. I have ADT-1 on 5.0.2 LRX22G... this process should work correct?

 

[KazeOne]

I followed the steps but something went wrong, I get bad command when it reboots with error, what can I do? I want to go back to 100% stock so I can update to 5.1.1

 

[zarthan]

The ADT-1 can not be updated to 5.1.1 It is no longer supported. If you are using a different device check the proper thread.

 

[darker_slayer]

The question was regarding the nexus player

 

[zarthan]

This thread is about the ADT-1 not the NP. The NP uses an X86 processor, while the other Android TV devices use ARM. Trying to use downloads or instructions meant for one device may cause irreparable damage to another.