Updating to future USB updates from HC "User-Debug" leak

[killer4110]

This is what I heard yesterday, no names mentioned here.
The update was released yesterday to a small amount of boxes, today it will hit a large number of boxes, and it should finish by Saturday or Monday the latest,

In the conversation I was part of, there was no discussion of the leaked version boxes.
So if someone is going to grab the update off of the server's, today or tomorrow would be the day.

[parrotheadmjb]

In the conversation I was part of, there was no discussion of the leaked version boxes.

I remember reading about a month ago that the leaked releases wouldn't receive the OTA, I thought it was from a reputable source; but its been over a month, maybe longer so I don't remember. If the leaked releases don't get the OTA, it really doesn't matter much other than it being an inconvenience... for those of us on a leaked release, we know how the process works and we can update it on our own haha

In either case; Thanks for the update on update!

[hellasleeper]

Thanks for the response parrot. If the update isn't going to get pushed to debug boxes, then wouldn't you have to have a hw rooted box to pull the update.zip from? Just trying to know what to do if one pf my boxes gets the update soon I could probably upload it for the community.

[pbiancardi]

this should get you into recovery

$ adb connect <revueIPhere>
$ adb reboot recovery

So instead of doing the steps in the original post we can just do the above to boot into recovery and flash the posted update.zip?? As I understand it recovery is still there just not accessible from the GTV so this method might be quicker and cleaner??

[hellasleeper]

No those are the commands to run after you flashed recovery back into the box using the original post. This will access recovery for whenever the official is released as an update.zip

[EvgeniX]

do I was need to do this each restore?

[Discovered]

Well you should only need to use it one time.

[slackwaresupport]

im getting this:


adbd cannot run as root in production builds

[Discovered]

This is only for the user debug build.

[youjest]

I have enjoyed the previous leaks including the last 3.1 debug release. Thank you to all who contributed.

I was preparing my Revue so I could update to the official 3.1 and got stuck in adb. After following the directions and connecting the Revue IP, I get stuck at adb root. I get an error: device not found. What am I missing? Is there a driver for the pc? I have plenty of experience with adb on android phones. I am connecting via my network correct?

Thank you!