yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] SavageCore:
After the downgrade it would ask for the sim settings? PB99IMG?

So need to add the steps for getting through that?
[Desire Android Development] teppic74:
After the downgrade the phone is wiped, so it insists on going through the settings screen. This is what I get on mine:

First screen, 'choose carrier' - O2 postpay/O2 prepay/Tesco. So you could just scroll down lots of times to get to the next button (it doesn't matter if you scroll down too much) and click button.

Second screen, 'select your language'. It defaults to English (UK), but then there's a huge list of languages below it. The only way to get to the next screen is to keep scrolling down (50 times? 100 times?).
[Desire Android Development] :
I did mine without a simcard. Forgot to mention that.
[Desire Android Development] Myshkinbob:
Blimey, this thread has been busy since last night!

I'll test the procedure on my stock froyo SLCD after dinner here.

If anyone else has a go and gets confused about which screen they're on, rather than pull the battery to reset, you can either use adb to power down, or...

short press the power button to light up the keys, swipe down to unlock the touchpad, long-press the power button, press the joypad button once, then i pressed the left-center of the screen for the power down confirm dialog. Leaving the usb cable in while trying to power down means the green LED will blink off for a couple of seconds when power down happens.

I have a few questions about step 11, once you've exited the setup wizard.

I'm trial running on my working 2.2 screen, and bringing up the apps list via the menu button, your steps are written as down x2 and right x3, ie the bottom right item in the 3x2 grid, but in 2.2 this is Settings, and to reach All Apps in 2.2 you just scroll up and to the left to reach All Apps, ie the top left position. Is the All Apps option in the menu a different position in 2.1?

Once you're in the apps menu i found another issue, the optical joypad likes to scroll more than one item at a time, fairly often. Do you think you could screenshot/photograph/describe the position of the Settings app in 2.1, once the apps menu has been touch-screen scrolled to the very bottom?

My idea is once the apps menu is up, you can blind-scroll the apps list to the bottom with the touchscreen, from there the OJ will activate on the top-left item of the bottom of the apps list, and this should be fairly near to Settings, reducing the chances of missing it with down x10 etc.

Similarly, if you enter the settings menu in 2.1, and touchscreen scroll it to the bottom, is the topmost item on your screen Applications? In which case you can just OJ click to enter it straight away.

much appreciated. :)

Oh one final question, is it possible to just spam click the bottom-right of the touch screen for next-next-next through the entire setup menu, that is, are there any confirmation prompts in the center of the screen?
[Desire Android Development] SavageCore:
You don't want to be in the all apps menu.

Settings is correct. Then you scroll down 10 times to get to Applications.

Look forward to your results, I don't have to be the tester then! ;)
[Desire Android Development] Myshkinbob:
i'm retarded, excuse me :)

I always thought the settings option when you press menu on the homescreen took you to the homescreen preferences!

My bad, got the phone on saturday so the menus are a little new to me still.
[Desire Android Development] Bicklp:
has anyone tried this yet...

im very tempted

are your steps definite now?

what about the setup screens people are on about...

and in this section

---------------------------

Press vol-down x1

Press the optical joystick x1

Press vol-up x4

Press the optical joystick x1

Wait 60 seconds

Press the optical joystick x1

is it definitely press optical joystick and not power button?

I tried on my normal boot menu and the optical button does nothing. you have to move with volume up down and then select using the power button?

are we talking about a different recovery menu?
[Desire Android Development] Myshkinbob:
I'm testing it now, PB99IMG is just flashing currently, i'll update this post when i get to enabling usb debug.

Currently i'm trapped in the setup menu, no idea which screen other than the phone vibrated briefly once, and i'm not on any text input field because the screen gives no haptic feedback.

small update, i restarted the phone with short power, slide down screen, long power (short vibration), oj up, oj click, oj click. Restarted the setup wizard, get a short vibrate at...

beginning of part 11...

I get a short vibrate on that last oj click before the right scroll x1.

Can anyone check what this refers to in a working screen setup? I suspect it relates to the wifi setup.
[Desire Android Development] SavageCore:
Yes I assume this is power instead unless custom recovery's allow joystick...
[Desire Android Development] teppic74:
I expect the language selection screen is the problem (on my test run you would have need to scroll down a huge number of times), or you may be on a sim selection screen.
[Desire Android Development] teppic74:
This is what I would do on mine, assuming that there is no sim selection screen at the start:

Language screen: flick the touchscreen up quickly to scroll down, at least 10 times. Scroll down using the trackpad about 10 times. Press for next.

Keyboard screen: scroll down, then right, then press.

Internet screen: press, scroll down twice, scroll right, then press.

Wifi screen: scroll down several times, then right, then press.

Google screen: down several times, then right, then press.

Accounts: down several times, then right, then press.

Social networks: down several times, then right, then press.

Time: down several times, then right, then press.

Learn mode: down several times, then right, then press.

You're now out of setup.

It's several times because it doesn't matter if you scroll down too much, as you're going to the bottom of the screen.

edit: it should be safe to scroll down and right and press even if you are out of set up, as this does nothing in HTC sense.
[Desire Android Development] Myshkinbob:
Cheers for those instructions teppic, got me out of setup. :)

From there i waited for the screen lock to engage, then i did

short power (activate screen)

slide finger down screen (unlock screen)

home (ensure we're on the home screen)

menu (bring up menu)

OJ right x3 (move selection to far right)

OJ down x2 (move selection down)

OJ click (select settings)

slide finger up screen quickly (scroll settings)

tap top inch of screen (enter Applications, alternatively this could be done with a short down on the OJ to activate OJ selection, then an OJ click)

OJ down many time (select dev settings)

OJ click (enter dev settings)

OJ click (enable usb debug)

OJ click (ok on usb debug confirm dialog)

edit:

and i just almost bricked my phone, certainly bricked my pants, lol...

With debug enabled, i ran unrevoked 3, used the slcd image, it rebooted the phone, spent forever waiting on the phone to reboot. At this point i remembered PB99IMG was still on the SD, so i hit down to choose no on the update. Only then would unrevoked continue the bootloader update. I advise people remove their SD card before using unrevoked.

The reason i got worried was the phone was dead after unrevoked finished. That is, screen unresponsive. Removed the battery, popped it back in, no power button response. Removed the battery for a minute, put it back in, boots back to the home screen. Phew!

From there i just tried voldown+power to boot to bootloader, and that's still a blank screen even tho i have ClockworkMod v2.5.0.1 SLCD flashed?
[Desire Android Development] teppic74:
So you're now rooted with unrevoked3?
[Desire Android Development] teppic74:
Your HBOOT is not SLCD compatible, so when you start it up in the bootloader you'll see nothing. But if you press vol down then power, it should start up custom recovery, and hopefully the screen will come on.
[Desire Android Development] :
I am flashing stock 1.21.405.2 again. Listing all the steps again. Will just try again.
[Desire Android Development] teppic74:
For pretty much every set up screen (except the language one), the same thing works - scroll down 5-6 times, scroll right, press the button. That does the equivalent of pressing next/skip on each stage of setup.
[Desire Android Development] Myshkinbob:
That's a fine question, unrevoked reported success flashing clockworkmod (SLCD version) onto the phone, but i still don't get a working screen with voldown+power at boot up.

Bearing in mind i've had an android phone since saturday, and never rooted one, so i'm essentially a total noob, which screen does clockworkmod replace?

am i right in thinking...

voldown+power = bootloader, still stock

back+power = fastboot, still stock

voldown+ power then press volume down once to highlight recovery, press power once to select = recovery, which is now clockworkmod

is that correct?

Particularly i need confirmation on the position of recovery in the hboot menu, it's 2/4, second option down, right?
[Desire Android Development] teppic74:
To get to recovery:

1. Insert battery.

2. Hold vol down and power together for about 5 seconds (press vol down first).

3. Wait 20 seconds while it searches for update files.

4. Press vol down once to go to recovery.

5. Press power once to start recovery.

6. The phone will vibrate. If it doesn't, you are not in recovery.

7. Wait 20-30 seconds. If no screen appears, either unrevoked3 didn't properly install or the updated image file doesn't help with HBOOT 0.80.

edit: you can test if custom recovery is running by plugging the phone in by USB and running 'adb devices'.
[Desire Android Development] SavageCore:
Correct 2/4. Need to wait about 10 seconds until it's selectable.
[Desire Android Development] Myshkinbob:
Ok i'm into recovery, still no screen visible, right now i'm following part 25 of the instruction post, replacing the oj clicks with power button clicks for selection tho, right?

That is, clockworkmod 2.5 supports selection with power button like the original recovery menu?
[Desire Android Development] teppic74:
Have you confirmed you're in recovery by using adb? The phone vibrating means it's trying to start recovery, it doesn't mean you've actually got it working.

In custom recovery you do use the trackpad button to select things.
[Desire Android Development] Bicklp:
Good to know thanks
[Desire Android Development] Myshkinbob:
ok i cocked that up then, i saw some discussion of whether the oj clicks in recovery were supposed to be power button presses.

I checked with adb yup..

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
**********86 recovery

obscured my S/N.

since i used power button selections but did the volume presses, i'm a bit lost as to where i am in the recovery menu, assume it's safe to do a battery pull when the recovery menu is in standby?

Or if power button doesn't select items, i can vol up to the top of the menu and start over the instructions without rebooting the phone?
[Desire Android Development] teppic74:
You can pull out the battery, yes. In custom recovery the power button switches the screen off, it doesn't select.

So it seems that HBOOT 0.83 or higher is necessary to initialise the display, in addition to the drivers in the updated clockworkmod image.
[Desire Android Development] Myshkinbob:
Ok followed part 25 exactly this time, with oj clicks for selection, and the misc fix applied, phone rebooted back to home screen, still hboot 0.80 and blank screening of course.

Applying the 0.83 RUU right now, it got past the mainver check and updated the hboot fine, updating system currently, i'll update this post when it finishes to confirm the 0.83 applies successfully and the screen is alive once more.

Confirmed, it's possible to downgrade an SLCD from 'unrooted with hboot 0.93' to the 'hboot 0.83 android 2.1' oficial RUU and then root the 0.83 hboot with unrevoked.

Anyone else wishing to try it, i suggest you replace step 11 in post #22 with teppic's instructions to escape setup in post 44, and my instructions to enable usb debug in post 45.

Big, big thanks to lollylost100 and teppic74 for the instructions and fast feedback when i was testing this out. :)
[Desire Android Development] teppic74:
Once you're past the version check, it's done, your screen will be working in a minute or two. Congratulations ;)
[Desire Android Development] SavageCore:
Did your steps differ from the originals at all?

Lets get a final write up done
[Desire Android Development] Bicklp:
Nice one mate...good job

If you get it going can you re-write the post with all the steps you followed start to finish

Including corrected button presses and scrolling etc
[Desire Android Development] Myshkinbob:
See my post above (#58), only difference from the guide in post 22 is at step 11.

I made a bit of a goof at step 25, but anyone else should be in recovery at that point, and not need to remove their battery like i did.

Now i'm just going to test the recovery menu is visible in clockworkmod 2.5 SLCD with an 0.83 hboot. Editing this post with the results shortly.

Edit:

hboot 0.83 RUU + unrevoked flash of clockworkmod 2.5 SLCD = rooted 0.83 hboot with visible clockworkmod menu in the recovery screen. Result. :)

Again, huge thanks to lollylost100 and teppic74 for the help. If you're wondering why a noob would test all this out first, well, i still have 10 days of 14 left to return the phone, hehe.
[Desire Android Development] teppic74:
It won't be long before unrevoked3 is updated to include SLCD support, but it seems that this doesn't make any difference unless you're on HBOOT 0.83 or higher. At least it'll remove one of the steps, I suppose. Having a working screen for the final section would have made it a bit easier.
[Desire Android Development] Myshkinbob:
Read up one post, i edited after testing it, clockworkmod recovery menu is fine once you're on 0.83 hboot. :)
[Desire Android Development] teppic74:
Now you're ready to install rooted froyo. Thankfully that is easy and won't break anything.
[Desire Android Development] Jarua:
Going to give this a try shortly, I've got a feeling the optical trackball moves are going to be the most challenging part.
[Desire Android Development] :
I am amending the tutorial right now. Get ready for release.
[Desire Android Development] Myshkinbob:
Speaking of which, hehe...

My requirements for a rooted froyo are a bit particular, i'd like to keep HTC-sense and the apps stock, but replace the kernel with one that supports SLCD, CIFS and VPN.

Why? I'd like to vpn into my home network and mount my tv/movies share via CIFS so that i can stream them, that is, essentially access my shows as if they were on the phone already. I'm aware of smb-capable file manager apps, but sadly they have to copy files to the local filesystem to access them. That's the beauty of cifs, it makes the phone treat the windows share as -part of- the local filesystem. :)

So far as i'm aware i need some sort of bastard mix of one the rooted stock HTC froyo roms combined with one of the CM6 kernel nightly's built after the 8th of august (when SLCD support was commited). Correct?
[Desire Android Development] teppic74:
It'd be best to read through some of the custom rom threads. Since you're rooted with custom recovery you can now easily backup and install different roms to find what suits you best. If you want to give stock froyo (rooted, of course) a go then I use this one:

http://android.modaco.com/content/h...-froyo-pre-rooted-no-hboot-with-radio-deodex/
[Desire Android Development] Bicklp:
using this routine

how can you tell when usb debugging is enabled....
[Desire Android Development] Myshkinbob:
Here's the rub, all of the stock htc froyo roms + su +busybox are using the 2.6.32 kernel i think, and i can't quite track it's origin. Some might be the plain OTA kernel, and some look like custom built kernels that have modules for ext4 and vpn in lib/modules/ but i can't find one with the cifs module. Aside from this, any of the rooted OTA releases not using the OTA kernel are likely to be lacking the SLCD driver that i think was only added to custom kernels on the 8th?

A couple of more heavily customised roms have newer kernels and the cifs module present, such as opendesire and cm6, but i don't really want to replace my UI.

I've played with Kitchen briefly but i'm not terribly confident with it, so, possibly one of the rooted stock htc froyo authors would be approachable about doing a version with an updated kernel which contains the SLCD driver and the cifs module?
[Desire Android Development] :
Everything is now in this thread: http://xdaforums.com/showthread.php?p=7602850#post7602850

I will change topic title from [DEV] to [FIXED]. Thread can be locked.
[Desire Android Development] Myshkinbob:
Load up unrevoked3 and add the custom image, then when you want to check if usb debug is enabled, you can just plug in the phone.

If you see any activity from unrevoked3, you know usb debug is enabled, and for the love of god leave the cable plugged in at that point! :)
[Desire Android Development] teppic74:
The Froyo official kernel definitely supports SLCD, so any custom ROM based on it will do (it will be kernel 2.6.32.15).

Remember that you can easily restore your phone with nandroid if a ROM doesn't work or you don't like it.
[Desire Android Development] Myshkinbob:
Sorry i think i worded that a little badly, sense-ui roms with the official kernel have SLCD but lack CIFS, and sense-ui roms with custom kernels lack SLCD and CIFS but do have VPN.

Only a couple of none-sense-ui roms with kernels built in the last two days have SLCD and CIFS and VPN.

I posted asking in one of the sense-ui rooted froyo rom threads a couple of days ago, with no response, but then i'm a little new to the community here.

So i guess what i'm really asking is should i just spam the request in all of the sense-ui froyo rom threads, or is there a particularly approachable dev i could ask about it?
[Desire Android Development] Jarua:
Just started up my PB99IMG.zip downgrade. A few tips from the last time I lost my screen:

- To get through the first time setup stage I just tap the bottom right of the screen a lot to get through all the stages. Easier than doing it with the optical trackball.

- An easy way to be sure you're past the lock screen and the setup is to press the search button, and feel for the keyboard feedback. Then hit back to get back to the home screen.

- For enabling USB debugging, I made a note of where the Applications bar sits after scrolling to the bottom so I can select it instead of 10x scroll movements. Should make it easier.
[Desire Android Development] :
At the point the tutorial was created we had no idea if the touchscreen was working.
[Desire Android Development] Jarua:
Ah, right - it definitely does. :)
[Desire Android Development] teppic74:
Once USB debugging is enabled the rest is pretty easy, since unrevoked3 gives feedback as it works. Getting through the set up may be a bit easier by using the touchscreen - you risk going into the camera at the end, but if you just press back a few times you should end up on the home screen.
[Desire Android Development] Jarua:
How can I confirm that USB debugging is enabled? Just by attempting unrevoked?
[Desire Android Development] :
The phone should make a sound when connecting USB and you will be able to do step 18.
[Desire Android Development] Bicklp:
Another way to check for USB debugging that i found works well

when you think you are in debugging mode

turn off unrevoked

plug your phone in to the pc and it should show up in device manager as android usb device ... if USB debuggin is not enabled it just shows up as a portable device with a drive letter that does not work

keep running through the steps until it shows as an android usb device

you could also run adb devices from the sdk and it will show connected devices

d:\sdk\tools>adb devices

when youve confirmed you are in debugging mode, unplug your phone and jump back to part 16 here and then carry on

http://xdaforums.com/showthread.php?t=750852
[Desire Android Development] debully:
Congrats to those who fought there way through and discovered this, big respect.

Having just come back from a .92 to .80 brick exercise, and the few blind screen presses, the thought of all those new blind clicks to enable usb debug is mindblowing to me.

Is there any update on how alternative (non-blindfolded) methods are coming along?
[Desire Android Development] obscuredReality:
Hi debully,

Have you heard of any non blind-folded approaches yet?
[Desire Android Development] debully:
not as yet. I am going to attempt this on sunday. I have taken a quick video on my old touch pro 2 that shows where the screen presses are when enabling usb debugging - think this will be easier as my optical track is very hit and miss.

will report back and post the vid if its failsafe...
[Desire Android Development] obscuredReality:
Hope it works! Good luck.

Thanks
[Desire Android Development] obscuredReality:
Can't get into dubugging mode

I've tried the steps to get into debugging mode but can't seem to get into it. I'm definitely passed the setup wizard because my phone vibrates when I press and hold on a widget.

Would someone be able to provide screenshots for me?
[Hero CDMA Q&A, Help & Troubleshooting] chefthomas99:
since these roms are made both by Darch.. wondering how these two differ.. let me know your opinions... thanks!
[Hero CDMA Q&A, Help & Troubleshooting] BlaqkAudio:
Biggest difference is DD is Eclair and CM6 is Froyo
[Hero CDMA Q&A, Help & Troubleshooting] chromiumleaf:
CM6 is running Android 2.2 aka Froyo. DD 2.8 is still only using 2.1 Eclair.

On the surface, 2.2 is faster and smoother. Also see this article for new features/functions in Android 2.2: http://developer.android.com/sdk/android-2.2-highlights.html
[Droid Incredible Android Development] SR3TLAW:
Just saw it

"unrevoked: A warning: the SkyRaider for the inc has a higher then average chance of causing "USB bricked" devices, we will try to work on a fix."

--http://www.twitter.com/unrevoked/status/20736784251
[Droid Incredible Android Development] Jdawg183:
Sheesh man! That is scary! Makes me feel like one of those people who come home and find out that the bank they were at an hour ago got robbed ten minutes later!
[Droid Incredible Android Development] SR3TLAW:
I didnt know for sure what it meant. Just thought I'd share it. I havnt had problems connecting via usb
[Droid Incredible Android Development] SoccerCore11:
So don't use SkyRaider 2.2 from 8/5? I was literally seconds away from doing this...

Is this "USB Brick" something that can be reversed with a Nandroid restore if I decide to take my chances?
[Droid Incredible Android Development] Θmega:
It sounds to me like it's an issue with running Unrevoked after you've already installed SkyRaider. I haven't seen any posts in the 231 page SkyRaider thread that report their phone was USB-bricked.
[Droid Incredible Android Development] SoccerCore11:
How would that make sense though, like if you are running a ROM you are already rooted, why run unrevoked again?
[Droid Incredible Android Development] rpearl:
This is the opposite of true.
[Droid Incredible Android Development] execute_method:
Maybe we're finally getting s-off
[Droid Incredible Android Development] execute_method:
Any ideas on what the criteria would be for this to happen? Is it the process of flashing, our can this happen through a certain process while running the rom?
[Droid Incredible Android Development] Θmega:
Then why have so many people not had issues with SkyRaider bricking their phones? So far the only place I've heard this is from the unrevoked team and plenty of people are apparently not having the issue at all.

I'm certainly not saying you're wrong—you're more knowledgable than me—but a lot of us are curious as to why this is suddenly an issue even though unrevoked is the only one who's had it happen. If it's because of unreleased software by unrevoked then what was the point in tweeting, since everyone who has it would be able to be contacted personally?