yashsingh1/xdaforums huggingface dataset:
[Android Themes] jcarrz1:
this zip isn't signed, hence the "CWM" label (cwm doesn't check signature by default). You're probably using a recovery that checks signature. So downloading the ttfs and using font changer should work, I've never used it personally but others have successfully applied this font with that.

the gmail problem sounds like it's not font-related, the app chooses whether to bold or unbold the text...
[Android Themes] thebeardedchild:
Thanks for the installation help!

As for the Gmail thing, I didn't really think it made sense that a font could do that...but the weird thing is that it doesn't happen with any other font I've tried. Someone claimed it happened with Helvetica too, which is a similar font to Roboto
[Android Themes] arzbhatia:
Didn't work for me..

Edit : Installed the ttfs with Font Changer from Android Market, works now :) Thanks!
[Android Themes] jcarrz1:
Glad it's working for everyone, some way or the other :)
[Android Themes] jcarrz1:
updated OP a bit :)
[Android Themes] dcarr622:
I love this font! thanks
[Android Themes] Vintos:
This font is amazing . It uses the available space much better. Typo magic!

I used both methods: (1) adb push ......ttf /system/fonts and (2) the flashable zip. both worked as expected. for the flashable zip i just mounted system partition before flashing as it was mentioned here(I use CM rom).
[Android Themes] jcarrz1:
Thanks for your feedback!
[Android Themes] magicman0:
I can confirm mounting system partition before flashing works on captivate running cm 7.1
[Android Themes] jcarrz1:
Nice, good to hear!
[Android Themes] hmstx:
I first used the ttf pack and the font changer app but also wanted to replace the lockscreen font, so it had to be a flashable zip thru CWM. Worked a charm the way you described.

(Desire CM7.1)

edit : reflashed a CM7 nightly, flashed the font pack without mounting system manually and it still worked.
[Android Themes] The Unnamed Time Lord:
An update from earlier in the thread. Just mounted system and flashed the zip.

Works perfectly!

HTC Vision (T-Mobile US G2)

Cyanogenmod 7.1 Stable
[Android Themes] jcarrz1:
thanks everybody!
[Android Themes] anisbombaywala:
Hey jcarrz1.. thank you for your excellent work. I REALLY love this font.

Earlier I used your flashable zip on a KI4 rom. And it flashed fine.

Now I am on a rom with a different base. And the zip does not work from recovery as it did on the previous rom. It does not give any error. Just that the font does not change.

So I thought of changing the updater script in the zip to make it compatible with my rom base. but the line in the script where we make the change is missing. Can you please advice what can I do here? For now I have simply replaced the three TTFs in the system fonts folder and the font has changed as i wanted.
[Android Themes] jcarrz1:
you were too vague... what does "the line that we change is missing" mean?
[Android Themes] anisbombaywala:
What I meant was.. that the updater script of few other mods that I use have the the initial lines like this:

ui_print("");

ui_print(concat(getprop("ro.build.PDA"), " detected!"));

assert(getprop("ro.build.PDA") == "I9100XXKI4");

show_progress(0.100000, 0);

So I easily change the PDA version in the third line here to whatever base I am using. Like if the base of my new rom is XDXDX then I would just change it to:

assert(getprop("ro.build.PDA") == "I9100XDXDX");

But the updater script in your mod does not contain have this line.

I am sorry for any noobness here. I do not know much about the updater script. Just that I love your mod and I want to continue with the convenience of applying it regardless of the base that I am using.
[Android Themes] jcarrz1:
you should be able to flash it regardless of the base rom you're using. in addition, those lines look fine in edify code, so you can add them to the top of my script if you like.
[Android Themes] cr0wnest:
Its a bug with gmail and custom fonts i think. Ive tried installing other fonts like tahoma, ubuntu, and basically any font that isnt the default font will get that bolded fonts in gmail.
[Android Themes] mr_wrong_0:
I am getting this too. Anybody find a fix yet?
[Android Themes] jcarrz1:
I think this happens to people whose clockworks are too old. try editing the updater-script and removing all "ui_print" lines. You also may have to copy the "format system"-related lines from another script for your device.

It's hard to be universal these days...
[Android Themes] stevehkim:
no I'm using the most recent CWM and I get this message as well. I know it's the most recent because I just installed it last week:) any other ideas?
[Android Themes] El Brillantinas:
Roboto is a nice font. But what if I want to go back to Clocktopia in the lockscreen? Im sure that it isn't necessary to flash back to my latest backup.
[Android Themes] jcarrz1:
you can pull it from your rom, in the system/fonts directory and use

adb remount
adb push clocktopia.ttf /system/fonts

for the guy with the script problems, try and copy and paste the system format line from a rom for your device.

jcarrz1
[Android Themes] Jirv311:
Totally not the place for this, I know, but what status bar theme is that? :D
[Android Themes] ktmbikerman:
Does anyone know what the ICS clock font is called. Replacing it with Roboto does not look correct.

Sent from my superfly Defy
[Android Themes] Kekoh:
Did anyone find a way to do this? It would be nice to have the lockscreen look the same as ics.

EDIT: nvm, did it with FontChanger
[Android Themes] babywarez:
I loved that font I think that all the cookers should replace the oldone including this by default.
[Android Themes] Pickx:
The Clockopia posted here isn't the actual lockscreen clock font (like in this screenshot), instead it uses the Roboto digits

Attached zip contains a ttf with the actual ICS digits. It also contains a modified DeskClock.apk that uses this ICS font instead of the ugly pre-ICS font.

Note: I take no credit for this! Just spreading it around.
[Android Themes] dcarr622:
thanks! 10char
[Android Themes] :
Worked great on my Gio

The .apk worked great on my Samsung Galaxy Gio. Thanks.
[EVO Shift 4G Android Development] qbking77:
Figured I'd make a new thread so anyone coming here with a device updated to 2.3 OTA can downgrade to 2.2 and root and clockworkmod their phone and have an easy guide!

(Links to various XDA threads are in the description of the video)

Video:

http://www.youtube.com/watch?v=mcp2x7poHdw

Hope you guys like it :D
[EVO Shift 4G Android Development] fallnSaint:
Hopefully Scary will throw up a link in the stickied thread.
[EVO Shift 4G Android Development] FdxRider:
Thanks for this brother,without guys like you there would be a lot of people not rooted. Keep it up! :D:D Fdx
[Nexus S Q&A, Help & Troubleshooting] YourMainDude:
How Much Should I Sell It For =D

Sent From In between Your Moms Boobies
[Nexus S Q&A, Help & Troubleshooting] Klk450:
What makes you think, it's going to be launched on yours first?
[Nexus S Q&A, Help & Troubleshooting] tekkitan:
I think he means because he has a white Nexus S.

How much should you sell it for? *shrug*
[Nexus S Q&A, Help & Troubleshooting] YourMainDude:
=_= geez man

Sent From In between Your Moms Boobies
[Nexus S Q&A, Help & Troubleshooting] Klk450:
Ok, I get that the White Nexus S was given to developers but i doubt it would get ICS before any other Nexus S....
[Nexus S Q&A, Help & Troubleshooting] 063_XOBX:
The white wasn't given to developers and in fact the OP was pretty clearly just asking how much a White NS with ICS was worth.
[Nexus S Q&A, Help & Troubleshooting] tekkitan:
No one said the white one was getting it first...
[Nexus S Q&A, Help & Troubleshooting] valtonray:
having ICS isn't going to add anymore value to it, since most nexus s will have it at the same time. now the white color may make it a tad more desirable but current prices range from $150 for moderate wear to $300 for NIB. of course in 2 months, the realistic time window it will take for ICS to hit our phones that will drop to probably $100-$200 depending on condition. In fact i dropped mine today leaving a hairline crack in the screen and have decided to just hold out for the inevitable price drop coming when the Galaxy Nexus arrives.
[Nexus S Q&A, Help & Troubleshooting] YourMainDude:
Lol mine is in perfect condition.. had it since June and I never dropped it. As for the 2 month wait... I think Google already confirmed that as soon as the Galaxy Nexus Is Launched ... ICS Source Code Will Be Available Within 2 Weeks... but who knows. They sometimes take forever. Maybe this time they'll keep there promise =]

Sent From In between Your Moms Boobies
[G2 and Desire Z Q&A, Help & Troubleshooting] pvalery00:
my "t" key is missing from my g2 keyboard

dont know where it went or what got it loose

any idea where i can get a replacement key?
[G2 and Desire Z Q&A, Help & Troubleshooting] EndOfSource:
I would try HTC support or my phone vendor.
[General Questions and Answers] mattinui:
OK Ill try to shorten this post as much as I can.

Basically I was running 2.2 Froyo on my rogers (canadian) captivate today. I tried to upgrade to 2.3 using Samsung keis (officially released 2.3 in Canada/rogers). The update did not work at all and I was forced to recover with ODIN one click and it brought my phone to 2.1 (it was never at ANY point 2.1) and AT&T. I need to know how to bring it back to atleast 2.2 so I can try to upgrade to 2.3 again (I think I know what went wrong, I was rooted, probably screwed it somehow). Ive attempted alot of things to try and bring it back including factory reset but I dont want to screw with it any more myself. If anybody could post step by step instructions with links on how to get back to 2.2 short of sending it in (absolute LAST resort) then you have no idea how grateful I would be. I just want to be done with this phone modding nonsense.
[Xoom General] hammer4203:
I believe this is what everyone is looking for.

http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
[Xoom General] arrtoodeetoo:
It says it's for MZ602. Will this still work with our current XOOMs.

Furthermore, will it work with a 3G XOOM that has yet to be upgraded?
[Xoom General] hammer4203:
It says Verizon. It is the same file we updated to. Ours was the mz600, but after the upgrade it became mz602. You know of any other Verizon xoom with 4g? They are going to sell the same xoom, just has the lte card in it this time.
[Xoom General] dethrok:
Well, I'm having trouble with it.

I'm using RSDLite and trying to flash the .SBF and it's saying:

"Error validating image files" under status, before I even hit start.

Then afterwards, I get:

"Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI..."
[Xoom General] luismateos:
Thanks... Anybody knows if I flash one of the latinamerican image into a US 4G would brick the Xoom?
[Xoom General] hammer4203:
I think you have to extract it or unzip it.
[Xoom General] dethrok:
Extracted the .SBF from the .GZ file. It's just like.. RSDLite (v5.0) won't read some kind of .ini file. I have all the updated drivers, etc.
[Xoom General] dethrok:
Great. After using this, my Xoom won't go past the boot screen.

It won't even boot into recovery. I can still access Fastboot and RSD.

Even after trying different unbrick solutions. Even after flashing back to HRI66.

Can't even get my Xoom to turn off now.
[Xoom General] hammer4203:
You may need the other cable to flash it in rsd mode. There is a special cable that looks exactly like the normal usb cable. It's wired different.
[Xoom General] hammer4203:
You may need rsd lite on your PC and USB drivers to do it with the stock cable.
[Xoom General] dethrok:
Yeah.. That's what I'm doing it with. The stock USB cable included with the Xoom and RSDLite v5.4.4 with all the updated drivers.

My Xoom just sits there at the boot screen now, like I said, even after trying to flash back down to HRI66 afterwards to fix it.

I can still boot into Fastboot and RSD mode, but my Xoom stalls and doesn't enter recovery, even after trying another recovery img.

I thought I read something about needing a proper boot.img to go with the SBF file, but I even tried flashing AceXMachine's boot img and nothing.
[Xoom General] zone23:
So you guys haven't gotten this to work or are you just the lucky ones who had problems?
[Xoom General] hammer4203:
There is a stock version of sbf floating around that has 2 files in it one sbf and I can't remeber what the other one is. This is how they flashed ours for the 4g upgrade. It may be missing something. Can't the sbf be unpacked to the boot, system, recovery imgs? I read something along those linea in one of the dev forums. Not sure about that cable though. That's what worries me. It is suppose to activate something in the xoom so you can flash on rsd mode.
[Xoom General] zone23:
This is the issue I have. I do not have the official Xoom cable my dog ate it. Really it did. Looks like I will make a trip to Verizon and get one if necessary.
[Xoom General] dethrok:
Yeah, I think you're talking about this one. I downloaded that (from a mirror, as that link doesn't work) and everything I read said the smaller file (the one you're talking about) wasn't necessary.

And I haven't seen anything about using a special cable to flash your Xoom with RSDLite. Everything I've read just says the stock USB cable with updated drivers, so I have no idea.

Find and download RSDLite 5.4.4. That's what fixed it for me.
[Xoom General] hatxtrick:
dethrok, you've got most of it right >extract the .SBF (I've had issues on 64 bit Win 7 machine, unless I've place the file at either the root of C: or else under c:\users\<my username>\ (??-weird??))

> make sure you have the latest drivers

> (this is the gotcha) you need to use RSDLite v5.4.4

>>Note: Yes the HLK75D SBF works and was designed with the original MZ600

Hardware, since the MZ602 is just the MZ600 w/ LTE

This should do it for you, however for good measure, I aways run a short script that unlocks, erases (boot/sys/rec/uda & cache partitions), flashes HR166 back onto the device & then relocks it. I know this is probably a waste of time; it just seems to SBF with less issues.

Here's the text out of the .bat I wrote:

(!!!Please bear in mind this will erase/format your device, so please make sure you have all personal data backed up.!!!)

If your system is already powered up and has USB debugging enabled you can remove the 1st REM statement & just execute the .bat file, otherwise reboot the device by holding down the volume up and power button > release both and then hold down the volume down button until the "fastboot" screen appears.

Copy the below text into notepad and save as a .bat file

REM adb reboot bootloader

fastboot oem unlock

REM Press and hold the volume down button

pause

fastboot erase boot

fastboot erase system

fastboot erase recovery

fastboot -w

pause

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash recovery recovery.img

fastboot flash userdata userdata.img

fastboot erase cache

fastboot oem lock

If you want to use this, you need to d/l the HRI66 build .img files from MotoDEV as well as having the

adb.exe

AdbWinApi.dll

AdbWinUsbApi.dll

fastboot.exe

* you can also just REM out the fastboot commands that flash the HR166 image, so the device is completely blank and you can just load the HLK75D sbf via RSDLite, either way works........

** Remember after any OS flash, you should launch “Android recovery Mode” (press & release the down volume button after the red Motorola symbol appears when the device powers on) and reset the device to factory defaults.

Cheers,

Hat
[Xoom General] hammer4203:
That is the build number for our xoom. Why load the file if it can't be used to flash the xoom? There is something missing as to how it's done. I mean when the xoom came out they leaked an sbf file and it worked. This one just has to be unzipped first. Or does it?
[Xoom General] dethrok:
Now see, someone mentioned the other file included in that old .SBF, but no one ever answered as to what to do with it:

Actually, another person in that thread said they flashed the file first, rebooted, then flashed the .SBF. So I'm not sure anymore.
[Xoom General] zone23:
Thanks a lot guy that worked and I'm now back in business. Meaning my 3G is now operational. Don't have 4G in my area but I assume it works now as well. My device was unlocked and when I go into network now it shows CDMA/LTE.

Edit:

I did not have the official Xoom cable either.
[Xoom General] luismateos:
Zone, did you flash the HLK75D SBF?
[Xoom General] jadkar:
Agreed... point taken..... I'll try when I get home. Since I have no way to shut off my brick the battery is now dead :(
[Xoom General] dethrok:
So, is there a way KidJoe could pull his bootloader? He's sitting on v1.5.

I'm not sure on the steps, if any, to do that.
[Xoom General] tonesto7:
There is no way to pull it unfortunately... Its encrypted by the device itself when its installed... So even if we got it off it wouldn't work on a different device.
[Xoom General] KidJoe:
I was PM'd some info on doing it... I'm going to give it a try...
[Xoom General] hammer4203:
Here is the boot image off my xoom. See if after you get booted into the os you can return to fastboot and flash it. Hope this fixes it.

Boot img hlk75d - http://dl.dropbox.com/u/45070149/boot.img

Recovery img - http://dl.dropbox.com/u/45070149/recovery.img
[Xoom General] zone23:
C:\Program Files (x86)\Android\android-sdk\tools>fastboot getvar all

(bootloader) version-bootloader: 1045

(bootloader) product: xoom-cdma

(bootloader) secure: yes

(bootloader) model: MZ600

(bootloader) memory-info: 0x303:0x5454:0

(bootloader) mid: 001

(bootloader) version: 0.4

(bootloader) serialno:

(bootloader) version-baseband: N_03.1A.54P

(bootloader) version-baseband-2:

(bootloader) battery-status: 91%:8.91V:0.9838A:22.75C

(bootloader) unlocked: yes

(bootloader) iswarrantyvoid: yes

all: Done

finished. total time: 0.598s

C:\Program Files (x86)\Android\android-sdk\tools>
[Xoom General] dethrok:
Well, that's interesting.. did you flash back down or are you still on HLK75D?
[Xoom General] craigcrawford1988:
None of this can damage his device if he types this exactly (because he's only PULLING data from his device). Not sure if he'll need root for this.

Turn on USB debugging and then install android SDK and type in the following:

adb shell
cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
exit
adb pull /sdcard/boot.img
[Xoom General] zone23:
I flashed the HRI39 then updated OTA to where I am now. Everything works just waiting for Moto to give us a bootloader thats compatible.

---------- Post added at 03:53 PM ---------- Previous post was at 03:50 PM ----------

I believe that we don't have an issue with the boot.img that comes with the update. I think its all in the bootloader itself.

Hay heres a funny idea maybe I will get to do something else tonight besides play around with RDS and fastboot all night.. LOL

You know second thought maybe I'll go home and install android on my TouchPad maybe screw that up.. :)
[Xoom General] dethrok:
Talked to another Motorola rep just now.

"We have no particular troubleshooting steps for your problem. The only advice I can offer is to have you send in your Xoom and have our techs take a look at it."

So, they didn't know anything about a different bootloader, or at least they wouldn't provide information about it.
[Xoom General] tonesto7:
Yeah it seems that it is not understood that there is a difference between bootloader and Boot.img...

---------- Post added at 04:12 PM ---------- Previous post was at 04:10 PM ----------

Thats not surprising since I talked to a level 2 tech at motorola and he didn't even know there was an update to the xoom and that the latest software available was Android 3.2!

It makes me sick to call those tech lines...
[Xoom General] zone23:
Ya those guys don't have a clue my 8 year old daughter is more informed then they are. I guess in there defense they deal with a lot of different devices so its got to be hard to know about them all.
[Xoom General] dethrok:
Well, if they're going to "escalate my case" and have me call regarding this exact problem, I would think they would have me actually talk to someone who knows something.
[Xoom General] tonesto7:
Yea your right!

I'm getting so sick of the incompetence at Motorola... Don't they do any testing before they release this to the public...

Its been 2 weeks since i've been able to use my Xoom... And like you i spend all day trying different things to get it fixed.
[Xoom General] KidJoe:
Did that... here is the file -> boot.img
[Xoom General] tonesto7:
We need to try and find the updated bootloader.bin so we can try to update using that!
[Xoom General] Saintfyre:
So it looks like everyone is having issues with this, mainly due to RSD?. I'm currently on my LTE Xoom w/ the Tachi Kernal. I'm stucking on HLK75C and have intermittent issues with the Kernel.

I'm wondering if we're able to just take the System.img and Boot.img out of the HLK75D software image and place them in my SDK folder, then manually go into fastboot and just use:

fastboot flash boot boot.img

fastboot flash system system.img

My real goal is here is to get to HLK75D, Keep Root Access, and get the Stock Kernel back. Curious if anyone else has had success with this.
[Xoom General] zone23:
Final Edit:

Yes you should be able to RDS the update to your device. Once you verify that it still works (reboot). Then fastboot tiamats recovery and use there root rom thing. You should be good. Of course this all assumes that you are either unlocked or unlock at some point in the process.
[Xoom General] tonesto7:
Thats what I would recommend!

---------- Post added at 04:40 PM ---------- Previous post was at 04:34 PM ----------

Heres a positive note on one of my trials that allowed the 4G to work before a reboot:

This from Michigan
[Xoom General] zone23:
I don't even live in a 4G area and I'm probably going to shutdown 3G for the winter as soon as I get it fixed. Don't go outside much in the winter in Ohio you being in Michigan understand that.

---------- Post added at 04:49 PM ---------- Previous post was at 04:43 PM ----------

Of course with all this said you might just want to hang tight until we have a 100% full proof recovery in place. We do not have that at this time.
[Xoom General] jadkar:
So the reason nobody at Moto probably knows about this when we talk to them is because the 4G upgrade is probably being handled by some "team" of techs that is just handling this initative. Probably 5-10 of them and they have a SBF image with the bootloader as part of it. They flash the thing, put a SIM in it, put their cute little plastic protector on the screen and send it out. They are so specialized that nobody else except the dude that compiled the SBF probably even knows about that particular image. Maybe a couple team leads and a Manager who was told to just "get something made just we can update the machine to the current standard".

This bootloader will probably never be offered OTA because you either get it upgraded by Moto or you buy a new Xoom in the store with the new bootloader pre-installed.

Someone either has to get it leaked, or figure a way to extract it, and compile it into a flashable SBF....I don't mean pulling some code using ADB and making a boot.img that's not the bootloader update!
[Xoom General] hammer4203:
Hey isn't there an rsd 2 and rsd 3 on thr xoom.
[Xoom General] Jewremy:
Looking like a leak is the only option. Extraction has failed as far as I can tell. I compiled an extracted post-upgrade ebb partition into an sbf, still reads as 1045. On his xoom, it read as 1050. Best guess I can muster is that the bootloader somehow changed locations. In other news, the 1035 bootloader will let the xoom boot in 3.2.2 - no LTE or 3G access, though.
[Xoom General] REHolt218:
Just getting to HLK75D wont help much. I have the HLK75D zip file that I got ota after update to 4g. I installed it using CWM Recovery but I still have no 3g/4g. I don't have the boot issues some of the folks here do but I still don't have full use of my xoom.