Database Info

Technical Think Thank for Bricked Sapphire

Just like the bricked G1 thread, I want to start this thread which hopefully can be a place to share our story, get answer/feedback and be a compilation of "lesson learned" and "don't do this".

Originally from this thread, I have tried so many things and decided that my Google ION is semi-bricked.
It's not bricked because I can still go to recovery, fastboot, normal boot, etc and everything is working. Yet I considered it bricked because I no longer can do anything "hacky" with it. My problem is: sd card is no longer recognizable. There is no way for me to flash any image, do nandroid restore because the sd card stop working. If its a hardware failure, I would be gutted but accept it. But since its stop working when I'm flashing a new recovery, I have myself to blame.

lawrencegs, did you have test "fastboot update update.zip" in fasboot mode ?

kiltaiga said:
lawrencegs, did you have test "fastboot update update.zip" in fasboot mode ?
Click to expand...
Click to collapse
I dont think I've tried that. I will try it on my home computer later, because I can't see my device on fastboot when I try it on my laptop (adb devices). I can access my device on hardboot & normal mode though.
C:\android\android-sdk-windows-1.5_r2\tools>adb devices
List of devices attached
C:\android\android-sdk-windows-1.5_r2\tools>fastboot update update.zip
error: failed to load 'update.zip'
C:\android\android-sdk-windows-1.5_r2\tools>
Click to expand...
Click to collapse

Could you move this, please?
Move this post.
This is not the correct section. Thanks.
Oh, and best of luck to you fellas.

lawrencegs said:
I dont think I've tried that. I will try it on my home computer later, because I can't see my device on fastboot when I try it on my laptop (adb devices). I can access my device on hardboot & normal mode though.
Click to expand...
Click to collapse
should be
fastboot devices
when you are in fastboot.

lifeflayer said:
should be
fastboot devices
when you are in fastboot.
Click to expand...
Click to collapse
Oh ok, thanks... Still doesn't work though. Any idea?
C:\Users\lawrence>fastboot devices
HT959LV00680 fastboot
C:\Users\lawrence>fastboot update update.zip
error: failed to load 'update.zip'
Click to expand...
Click to collapse
Btw, where should this thread move? I thought since this is technical (and copying the g1 brick thread), this thread should be on sapphire android development.

lawrencegs said:
Oh ok, thanks... Still doesn't work though. Any idea?
Click to expand...
Click to collapse
Try to see if you can get your hands on the original RUU update from HTC.

I installed a 3g rom on wifi

Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks

Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk

nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?

BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support

nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.

nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.

znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks

root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568

nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.

Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least

stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.

znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.

stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.

Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface

nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/

Can I get the stock boot image
I just want to try that last option

I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much

nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.

I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.

jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.

With JB installed: CWM Recovery causes a hang when I try to load into it.

Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Edit: Forgot to also ask, am I just an idiot?

badfontkeming said:
Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Click to expand...
Click to collapse
I have the same issue, no fix yet.

untermensch said:
I have the same issue, no fix yet.
Click to expand...
Click to collapse
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.

I have the exact same problem so I right there with ya
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.

badfontkeming said:
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.
Click to expand...
Click to collapse
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.

EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
I've noticed the same issue, it exists with the latest TWRP flashed via fastboot as well.
The problem with flashing via the terminal is that we don't have root yet, and need a recovery to get it. Looks like the only option is to wait for a fix.

EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
Yeah... the issue is, the reason I'm trying to flash CWM is so I can get root.

krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?

sparky28000 said:
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?
Click to expand...
Click to collapse
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265

krhainos said:
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265
Click to expand...
Click to collapse
Now there is atleast 3 people since I bricked mine also

krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
just curious how are you able to get in APX mode it seems I cant even do that

Drgravy said:
just curious how are you able to get in APX mode it seems I cant even do that
Click to expand...
Click to collapse
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.

krhainos said:
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.
Click to expand...
Click to collapse
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient

Drgravy said:
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient
Click to expand...
Click to collapse
I used the reset hole in place of the power button when fiddling with button combinations. Hold down VOL+, and poke the reset hole with a paperclip and that'll get you in APX mode -- not like it does any of us any good.

I thought I had bricked mine...
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim

I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.

jdeatsch said:
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim
Click to expand...
Click to collapse
Not working for me at all...

untermensch said:
I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.
Click to expand...
Click to collapse
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
---------- Post added at 10:46 PM ---------- Previous post was at 10:40 PM ----------
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse
Weird. When I try to edit this post, I only get 3/4 of the quote and none of my actual post to edit. Anyway...
Just wanted to clarify: not asking for directions. If the file is what I think it is, I know what I'm doing. I just want to know that the file is what I think it is.

It is the Jelly Bean recovery kernel and the ClockWorkMod ramdisk repacked with mkbootimg, then blobpack,
then I added the "-SIGNED-BY-SIGNBLOB-" header with a hex editor. it seems like ADB does not work but I
was able to root with an update.zip
I installed this with fastboot and erased and re-flashed 4 time's before posting to make sure
it would not cause instant brick.
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse

[DEV] Looking for Nexus Player Owner with ADB/Fastboot Knowledge

I'm in search of a Nexus Player owner with sufficient ADB/Fastboot knowledge that would be able to run a few commands for me and test a few things. If that person happens to be you, please leave a reply in this thread so we can get started developing for the Nexus Player!

ProfessorAnomaly said:
I'm in search of a Nexus Player owner with sufficient ADB/Fastboot knowledge that would be able to run a few commands for me and test a few things. If that person happens to be you, please leave a reply in this thread so we can get started developing for the Nexus Player!
Click to expand...
Click to collapse
I might be willing to help. What is it you are wanting to do?

peppy6582 said:
I might be willing to help. What is it you are wanting to do?
Click to expand...
Click to collapse
I'd like somebody to test the custom recovery I've compiled, and to make sure it works properly.

ProfessorAnomaly said:
I'd like somebody to test the custom recovery I've compiled, and to make sure it works properly.
Click to expand...
Click to collapse
I don't intend to be rude, but what is your comfort level of non-brickage?

peppy6582 said:
I don't intend to be rude, but what is your comfort level of non-brickage?
Click to expand...
Click to collapse
There is no risk in bricking your device. You simply just have to boot the recovery.img and make sure it works.

Code:
fastboot boot recovery.img
7778c713fe675747fc4ce937fd40fe2e recovery.img
Download retracted for the time being.

ProfessorAnomaly said:
There is no risk in bricking your device. You simply just have to boot the recovery.img and make sure it works.
Click to expand...
Click to collapse
Yes, I will try. You have a pretty good track record! I had to check first, because I really like this thing!

Simply boot the image with fastboot and make sure that ClockworkMod Recovery is displaying properly on your TV. This way when you reboot your device nothing will have been changed, so there is no risk involved.

peppy6582 said:
Yes, I will try. You have a pretty good track record! I had to check first, because I really like this thing!
Click to expand...
Click to collapse
I appreciate your help! I have experience, so if you do encounter problems along the way I am available to help.

ProfessorAnomaly said:
I appreciate your help! I have experience, so if you do encounter problems along the way I am available to help.
Click to expand...
Click to collapse
I can see the device (adb devices), but when I do the fastboot command, it says waiting for device.

peppy6582 said:
I can see the device (adb devices), but when I do the fastboot command, it says waiting for device.
Click to expand...
Click to collapse
You must run this command first:
Code:
adb reboot bootloader
Followed by:
Code:
fastboot boot recovery.img

ProfessorAnomaly said:
You must run this command first:
Code:
adb reboot bootloader
Followed by:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Had to unlock it first. Nevermind. It booted into Android system recovery <3e>

peppy6582 said:
Had to unlock it first. Nevermind. It booted into Android system recovery <3e>
Click to expand...
Click to collapse
Alright, I will check my source again and recompile. I must have made a mistake along the way. If you're interested I'm also working on an auto-root that will be ready here shortly.
Do you have a gmail so that I could correspond with you via Hangouts? (If so, could you private message it to me?)

ProfessorAnomaly said:
Alright, I will check my source again and recompile. I must have made a mistake along the way. If you're interested I'm also working on an auto-root that will be ready here shortly.
Do you have a gmail so that I could correspond with you via Hangouts? (If so, could you private message it to me?)
Click to expand...
Click to collapse
I pm'ed you

I am also willing to assist if needed. I am comfortable with adb and fastboot.

I'm pretty comfortable with ADB and Fastboot. I wouldn't mind testing some stuff if you need me to.
Google already posted the factory images for the Nexus Player, so I don't mind. I'm interested in seeing what is possible with this little hockey puck.

Please add me to your list of candidates. I'd be very interested in checking out what you've got. Thanks.

ProfessorAnomaly said:
I'm in search of a Nexus Player owner with sufficient ADB/Fastboot knowledge that would be able to run a few commands for me and test a few things. If that person happens to be you, please leave a reply in this thread so we can get started developing for the Nexus Player!
Click to expand...
Click to collapse
willing to help, should you still need.

If you still need another tester tell me.
I've already worked with headless CWM during my work on the ADT1 (controlling CWM entirely via adb, I have no keyboards that work with it)
I've been trying to avoid compliling CWM myself as I dont want to have rebuild my dev vm just to compile CWM
(I've built CWM 6.0 in the past, but it was years ago)
Currently need access to a booting (doesn't matter if the CWM parts work, all I need is a root shell) image to dump the initial rom.
Fortunately, since we already have factory images, at least I/someone wont need to prepare a flashable zip for it to restore.

TheManii said:
Currently need access to a booting (doesn't matter if the CWM parts work, all I need is a root shell) image to dump the initial rom.
Fortunately, since we already have factory images, at least I/someone wont need to prepare a flashable zip for it to restore.
Click to expand...
Click to collapse
What are you trying to dump that's not in the factory images?

Bricked Verizon One M8

Tried converting to GPE edition by following htc-one.wonderhowto.com/how-to/convert-your-htc-one-m8-into-google-play-edition-0154471/ and using this file: RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5_rooted.zip. (I don't have 10 posts yet, so I can't post URLs.)
During the process, I edited android-info.txt to include my phone's mid and cid. Everything seemed to go fine, but now it only boots to the bootloader screen where I can choose fastboot or recovery or whatever, but recovery doesn't work. Also, my laptop is no longer detecting my phone on USB so I can't use ADB commands.
Please help... Don't know what to do from here.

darkhelmet46 said:
Tried converting to GPE edition by following htc-one.wonderhowto.com/how-to/convert-your-htc-one-m8-into-google-play-edition-0154471/ and using this file: RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5_rooted.zip. (I don't have 10 posts yet, so I can't post URLs.)
During the process, I edited android-info.txt to include my phone's mid and cid. Everything seemed to go fine, but now it only boots to the bootloader screen where I can choose fastboot or recovery or whatever, but recovery doesn't work. Also, my laptop is no longer detecting my phone on USB so I can't use ADB commands.
Please help... Don't know what to do from here.
Click to expand...
Click to collapse
If you are still in this situation install team viewer and pm me the Id and passcode so I can take a look.

dottat said:
If you are still in this situation install team viewer and pm me the Id and passcode so I can take a look.
Click to expand...
Click to collapse
Yep, still am. However, this morning I rebooted my laptop and now it is able to detect the phone on USB so hopefully it is now fixable. I'll PM you after I get TeamViewer installed, thanks very much!

darkhelmet46 said:
Yep, still am. However, this morning I rebooted my laptop and now it is able to detect the phone on USB so hopefully it is now fixable. I'll PM you after I get TeamViewer installed, thanks very much!
Click to expand...
Click to collapse
Actually, I take that back... It makes the "ding" noise like it's connected, but ADB complains "device not found" when I try to run commands...

Forgot to update this. dottat helped me out earlier this week and he is indeed the man! I'm good to go!