yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] fallonjp:
Based off of all of the Green Lantern / Firerats compatability problems, would I be better of flashing 2.5.0.7? If I did that would I have any issues doing firerats mod and then restoring a nand that was made using Green Lantern? Or should I flash new recovery, create a new nand, then run firerats mod?

Thanks.
[Hero CDMA Android Development] 24601:
Interesting observation. I may just try deleting firerat and see if it really is the recovery that my phone doesn't like. I'll let you know.

I am able to restore nands across versions of CWM. You just have to make sure your backup is in the CWM>backup folder of your sdcard. That is where CWM whatever version looks for a backup to restore. Pls don't read anything into my issues with CWM 3.0.2.4. My problems are clearly related to my phone and not the recovery. I strongly recommend ninja's version of CWM over 2.5.0.7, if for no other reason than the script at the top of mounts and storage screen to help you not wipe something you don't want wiped. Give it a go and report back your findings.
[Hero CDMA Android Development] R7i1c3K:
Is there a way to enable alphabetical sorting when doing something like "flash zip from SD card" on this recovery? I really don't know why that's not enabled by default, or even an option. Aside from that, I haven't had any problems with it.
[Hero CDMA Android Development] 24601:
1. Wiped everything

2. Reflashed 2507

3. Wiped again

4. Flashed GL 3024

5. Wiped again

6. Nand restore (no firerat installed)

7. Wipe cache and dalvik

8. Reboot

9. Bootloops

Wiped everything again, reflashed 2507, booted fine. Reinstalled firerat with 2507, booted fine. My phone hates the green lantern, and for that, I hate my phone :( I'm going searching for how to modify 2507 to include the script at the top that shows what you're about to format.
[Hero CDMA Android Development] il Duce:
Well the only other thing I can think of (and it's a looooong shot) is the "mainver" number inside the android-info.txt that you are using in hboot does not match your newly RUUed phone. I have seen both mainver 2.27.xxx and 2.31.xxx (thanks to c00ller for the tip that got me thinking) and I think for the longest time, we s-off types were probably on mainver 2.27.xxx and flashing accordingly. Now if you have recently RUUed then *MAYBE* your phone only likes things flashed with the new mainver (2.31.xxx). I have been thinking about this for a few days now, and since I don't have any issues and we've basically duplicated everything else, maybe that's the key? I have not RUUed like you and many many others, vayman for instance is having issues even flashing hboot zips anymore since RUU, even though he reflashed hboot. I am at a loss. If you feel like continuing this surely annoying testing, please try a HERCIMG.zip with an android-info.txt that contains the newer mainver number and rename the .img for fun to just recovery.img (though we now know that doesn't seem to matter). The zip I use for GL has 2.27.651.5 and it works and no errors or loops or issues :confused: Let us know, and thanks for banging your head against the wall :)
[Hero CDMA Android Development] 24601:
Thx for the thought; I am intrigued. Before my sojourn begins, let me postulate this: I am using your HERCIMG.zip to flash green lantern (with the 2.27.xxx android-info.txt). I am using my HERCIMG.zip to flash back to 2507. My HERCIMG.zip also has the 2.27.xxx .txt file. Given the fact my 2507 HERCIMG.zip works, does this mean the version of .txt may not matter? Shoot, I may try it anyway for something fun to do :)

*EDIT* Well, howdeedo, went into my android-info.txt file and this is what I've got:

So, I am wrong about all the HERCIMG's I've created. Duce, I'm gonna create a new HERCIMG.zip with your version of green lantern and my .txt and see what happens. Although, I believe when I first flashed GL I was using a HERCIMG I created.
[Hero CDMA Android Development] primerib:
This seems weird..but how do i launch into recovery mode.

when I hold menu+power key

nothing happens.it boots as normal...and i have to down volume+powerkey and then home to get to recovery
[Hero CDMA Android Development] il Duce:
from powered off state: hold home then press power (or from on state long press endcall, select reboot, recovery)
[Hero CDMA Android Development] il Duce:
let me reiterate "looooooong shot" lol.
[Hero CDMA Android Development] 24601:
Yeah, this is just testing now. I zipped up the op .img with my .txt and got repeated E: errors. I am in the process of zipping up the .img in your zip with my .txt.
[Hero CDMA Android Development] oldjackbob:
@Duce, I never flashed it, I just put it on the sd card for "just in case".

After reading the thread for the last few pages, I'm not able to competently keep up because I'm not that clear on naming rules, etc., so in a nutshell is the copy I got a good copy, or is it fubar?

Edit: I went back and re-checked post #105, and it appears the link to the zip has been removed, so I'm presuming I should prolly toss the file I have, no?

Edit #2: Or can I just rename some specific object in the zip file I have and I'll be good to go?
[Hero CDMA Android Development] 24601:
There was some concern my HERCIMG had incorrect file naming convention plus some ghost mac files floating around that may be causing my issues. I pulled the file just in case. It may be alright, but I still would use duce's. It's known to work.
[Hero CDMA Android Development] il Duce:
you can just grab the one I linked, I made it, and flashed it, and I'm fine.

EDIT: 24601 wins

EDIT2: unless we discover some hboot devilry based on the "MainVer" number inside of the android-info.txt, which 24601 is testing I think.
[Hero CDMA Android Development] 24601:
As I'm typing, I'm in a bootloop. I zipped duce's .img with my .txt (2.31.xxx). So, I'm back to square one. Thx.
[Hero CDMA Android Development] oldjackbob:
Thanks Duce, and 24601. :)

It occured to me to just test it myself, but then I realized that I'm already running GL 3.0.2.4 so I wouldn't be able to tell if the zip works correctly or not, lol!

Edit: I know I could flash another recovery and then the test would be valid, I was just admitting to being lazy.
[Hero CDMA Android Development] il Duce:
DAMNIT! Well, idk if the RUU killed GL or what, cuz it works for me fine (but ONLY with a higher FR cache as noted, and system is 103 used 110 avail) :confused: thanks for banging you head against the wall for days lol :)
[Hero CDMA Android Development] 24601:
No, really, thank you for working this through with me. Like I said before, I've made my Hero ingest so many techno drugs, I'm sure I've borked something that makes it just not like some things. Oh well, 2507 still works for me fine. I just really like that script at the top. of 3024!!
[Hero CDMA Android Development] il Duce:
LOL. To me it seems like at some point or another, my phone became a tweaked out meth head shivering in a dark corner, crying, screaming at passers by out of fear, and DEMANDING more drugs and tonics to soothe the pain.....

EDIT: that may be my new sig :)
[Hero CDMA Android Development] 24601:
LMAO, not that's a sig to which I can relate :D
[Hero CDMA Android Development] Drunkpilot:
Now that is an interesting observation. I used the lantern a lot today with no "E:" issues. I think I saw it displayed once at the top until I began wiping. I actually ran into problems when changing mtd, then flashing 2.5.0.7. I tried to back up, but no go. Then tried to restore an got stuck on splash for every nandroid. It turns out my mtd text disappeared and I had to redo them. I was able to finally put DH on my 4/21 rom. I used Duce's edify zip for that. Thanks Duce!

Sent from my Hero CDMA using the XDA App
[Hero CDMA Android Development] fallonjp:
Flashed ninja's 3.0.2.4, created a new nand backup. Flashed all of the firerats stuff, restored my nand backup and it worked like a charm. Thanks for the help.

Did you ever have any luck getting FR and GL to work together?
[Hero CDMA Android Development] 24601:
No. I've tried every combination and come up with bootloops no matter what. I've given up. I'm goin' with ranger's wisdom - if it ain't broke, don't fix it. My 2.5.0.7 flashes anything, so that's where I am. I looked into how to edit a recovery .img so I could modify 2.5.0.7 to get ninja's script at the top that shows me what partition I'm about to wipe; but what I found is about six flights of stairs over my head :p
[Hero CDMA Android Development] il Duce:
Have you tried the one aosp put up? It's 3.0.2.4 and compiled around 4/21 so it *should* have the script fix...
[Hero CDMA Android Development] 24601:
No *eyebrows raise in desperate anticipation*. I did try ninja's 4/11 version in the op. Is aosp's version different than that?

*EDIT* Y'know duce, I've never tried flashing one of these with adb or through TE; I've only tried flashing with HERCIMG *embarrassed* Lemme give that a try first with the GL.
[Hero CDMA Android Development] il Duce:
I too have become s-off arrogant, or Hboot dependant.... LOL let us know :)
[Hero CDMA Android Development] DJB628:
You can also rename it and flash through Rom Manager, simple and easy
[Hero CDMA Android Development] aiwetir:
GL ?

10 characters
[Hero CDMA Android Development] il Duce:
green lantern (green theme recovery 3.0.2.4

http://dl.dropbox.com/u/5669105/HERCIMG.grn3024rec.zip

thats my hboot zip, rename to HERCIMG.zip and flash in hboot :)
[Hero CDMA Android Development] 24601:
Uh, oh. Went ahead and flashed aosp's newest recovery from his GB thread - CWM 3.0.2.8 - using adb. Recovery flashed fine. Tried to make a backup and process stuck on Backing up system . . . Progress bar shows in the background, but nothing is happening. Waited 5 minutes and battery pull. Tried just turning phone back on and splash screen bootloops once then reboots back into recovery. Went back into recovery and flashed back to 2.5.0.7 with HERCIMG, but now same thing happens with 2.5.0.7 - stuck on backing up system and splash screen bootloops into recovery. I can smell an RUU . . .
[Hero CDMA Android Development] Drunkpilot:
Are you trying to back up the same thing? I think you will need to go back to a nandroid that works, do whatever you need to do, then try backing up again. Maybe That's what you were doing though.

I was having the same type of issues and found that my mtd.text had been erased (the actual text in the file). Put back and was able to finally flash again AND using GL with no weirdness.

Aosp's is the newest version I believe. I too am on the Hboot train. I'm ridin' the green horse I guess. We need a purple like Donnie Osmond's socks. Weren't they purple?
[Hero CDMA Android Development] 24601:
I went back to 2.5.0.7 and restored a known working backup. Wiped everything and flashed aosp's 4/29 version - everything working fine now. Just can't seem to make any CWM 3.xxx version work for me no matter how I flash it. Oh well, for now everything feels like . . . you asked for it . . . .
[Hero CDMA Android Development] Drunkpilot:
Now that's a lot rock n roll, not a little.
[Hero CDMA Android Development] jasonmaloney:
Bump.

Updated to 3.0.2.8; includes the following patch:

Change I474a5117: recovery: display mount point when confirming format

Thanks Jaybob!
[Hero CDMA Android Development] dpeeps74:
Nice. Does anyone else have a ton of lag when choosing to wipe dalvik? Sometimes it takes almost a full minute to get the confirm screen. I'm using .4. None of the other choices seem to do this. It works once it gets there just tests my patience a little.

~maybe I set it too high...
[Hero CDMA Android Development] c00ller:
It's about time :D

I've never waited anywhere near a full minute, but yes sometimes I have to wait maybe 20 seconds or so.
[Hero CDMA Android Development] jasonmaloney:
When you select the option to wipe dalvik-cache, the recovery must mount data, cache, and sd-ext (if available), and run "rm -rf dalvik-cache" against each of these partitions. This takes time.
[Hero CDMA Android Development] dpeeps74:
Ok, cool, thanks for the explanation jm. I had used RA for the longest time, avoiding CWM at all costs till about a month or 2 ago (at least as far as my everyday recovery) and that's been the main thing I've noticed different. Sometimes it even seems to be nearly instantaneous, but I haven't figured out a pattern to that yet.

~maybe I set it too high...
[Hero CDMA Android Development] Pyr0TeK:
Green Lantern 3.0.2.4 that I am running now already has the jaybob fix (i think) so in essence, this is the same?
[Hero CDMA Android Development] oostah:
im making a backup of Sensible Gingerbread 0.9 and its hung on backing updata......

for 5min is there some thing i can do not to lose any thing.
[Hero CDMA Android Development] dpeeps74:
Restart. Sometimes my phone hangs backing up data. I've seen times where after the restart I started backup again and it went through fine, and I've had a couple times it just wouldn't complete the backup. Either way, backing up shouldn't negatively impact what you have running.

~maybe I set it too high...
[Hero CDMA Android Development] oostah:
i tried from shell reboot it did nothing . trying to find a command to restart
[Epic 4G Q&A, Help & Troubleshooting] FFighterCo02:
Flashing this syndicate rom has been a total nightmare for me... phone always boot loops while tether is running. Now 3days into the install number 6, now it FC nonstop apps and services... Anyone help?
[Epic 4G Q&A, Help & Troubleshooting] Esteway.619:
U should just odin back to stock eb13 and re root and re install the rom. U should also redownload the rom cuz u might have a bad download
[Epic 4G Q&A, Help & Troubleshooting] MysteryEmotionz:
+1 the reason your getting fc is do to data corruption. The reason you have data corruption is cause of the teather causing you to reboot. I have titnaum backup scheduled to back everything up at 3am just for this reason. I get corruption I restore the backup from the night before and all is good.

As far as teather causing problems have you flashed the fix?
[Epic 4G Q&A, Help & Troubleshooting] FFighterCo02:
No I didn't know there was a fix
[Epic 4G Q&A, Help & Troubleshooting] MysteryEmotionz:
Check the op
[Epic 4G Q&A, Help & Troubleshooting] inthewayboy:
I applied the tether fix, still had FC issues...ended up uninstalling it and re-installing the Wired Tether For Epic from another post (Dont' have the link handy) to finally get it working...but other than that (And the rather bobo bootanimation {Which can be replaced!}) I've not had a single issue so I agree with the other...Odin back to stock and re-download and try again, cause it surely does work. Best ROM out there at the moment!
[HD2 Android Q&A, Help & Troubleshooting and Genera] scottcrotch:
Basically i installed the the RAFDROID HD 4.0.2 onto my HD2, everything is working perfectly fine except for the marketplace. I open it up and click on any app, click okay for the permissions and click on the install button, the apps download, but gets stuck on the installing.... part and wont go away. Ive restarted the phone, ive searched around to see if anyone has had the same problem, but have come up short.
[HD2 Android Q&A, Help & Troubleshooting and Genera] blacksxe:
I get the same thing
[HD2 Android Q&A, Help & Troubleshooting and Genera] maxtap:
i've got the same problem.

i can't install apps either. and i love the rom but without my apps i'll have to go back. any help would be appreciated
[HD2 Android Q&A, Help & Troubleshooting and Genera] Richy99:
what version of the hd2 are you using?

i am assuming you have an ext partition on your sd card if you have a eu device
[HD2 Android Q&A, Help & Troubleshooting and Genera] ic3fox:
i have the same. i can´t install any app of the market and when i try to download an app with the web browser.

it´s only downloading and then it says "installing" but nothing happens.

is there any update to fix is?
[Wildfire General] edgarasm:
hello i just wanted to see if i still could get help with my useless device

Ok so yesterday ive rooted the phone and today i tried to install cyanogen mod 7 rom

i used rom utility which i ve downlaoded from android marketplace

now sometimes my phone boots and gets to the logo loop

ive heard that clearing cache and settings would work but i cant access these menus as my hboot is not reacting to my key presses , i tried to reflash the phone but nothing came with success.

I used android sdk and RUU but nothing with success .

maybe anyone would teamview me or give me step by step tutorial how to get this phone alive again would be appreciated

You will be rewarded :)
[Wildfire General] B0RI5:
You rooted the Phone with a App from the Market?

You need if your HBoot is lower then 1.* the unrEVOked Tool.

If its 1.* there is no way to flash it.

Okay, maybe it worked with yout root app from the market, dunno, but i dont think so.

So you cant access while pressing volume down (keep holding) and switching on the phone the bootmanager? oO thats no good.

The Logo will stay up to "15minutes (<-?)" after flashing a new Rom. In this time its possible, that you Phone restarts automaticly. its normal. Switch it on an wait up to an half hour. If it keep staying in the boot sequence while showing the logo you got a problem :rolleyes: .

I think there isnt a more unsave way than a "Flash by teamviewer". You have also pay attention to the phone while flashing. on TV you cant keep an eye on it.

But how can you reflash your phone without getting access to the bootmanager/ HBoot? I think you habe to access the clockwork to flash cm7 *thinking*.
[Wildfire General] daddyspud:
If u nowhow to use adb try n get a adb logcat if possible
[Wildfire General] edgarasm:
Hi borris and daddyspud thanks for your reply ,i cant move around in hboot ,my hboot version i 0.80.0003

Ive rooted it using unrevoked with clockwork mod on it.

now even when i get it to boot it just loops in cyanogen animation,should i leave it for 15 minutes to do its thing?

also im new to this so i dont know anything about sdk and adb,all i did is saw the tutorials using it ,so i thought i would use it just to give it a go
[Wildfire General] B0RI5:
HBoot 0.8 is rootable, so its okay.

If there is still an animation while you see the CM Logo everything is fine.

If it freeze for some minutes is there a problem. The Animation shows you "i am working / installing".

Yes, let him do his thing for some Minutes.

I think everting should be okay and after some minutes it will work like normal.

It reboots sometimes it self, but this is also okay.

I dont know... does the new CM7 also install a new HBoot? So its possible why you cant move around in it.

Do you wait about 10 seconds before you try to move around in it? Because in the first seconds it looks like it freezed an then it start a test or something. this takes about 10seconds then you can use it.
[Wildfire General] Michealtbh:
Its not bricked if its turning on.

Can you get into recovery? If you can try flashing the 4.1 kernel.

If that doesnt help, go into recovery and do a full wipe. Clear cache and dalvik, and under partitions menu format everything except SD card. Then flash CM7, then the 4.1 kernel

Remember first boot will take 10-15 minutes. Be patient. If youve done everything right you shouldnt have any problems
[Wildfire General] edgarasm:
Hi and thanks for cooperation ,i left my phone on cyanogen animation for an hour and nothing is happening just animation loop constantly.

I've just tried hboot and it searches for the PC 49 DIAG and says not found after that it freezes and i cant use any menu navigation buttons . in hbot and fastboot.:(

I dont even know what to do next :(

Much help appreciated guys
[Wildfire General] B0RI5:
oO

thats weird.

the PC49DIAG is a part of the rom it self. So i think you have to try to re-flash it. Did you try it with or without a goldcard?

before you flash your phone whipe ALL datas on it!!!

If i start in bootloader mode i get also all the "missing" errors but i can still use the vol up/down buttons to navigate around.

That should help.

I think you did something wrong while flashing.

the root failed?

you got an error while flashing?

goldcard?

Try to flash a RUU from shipped roms. DONT flash a Froyo rom, you will get the HBoot 1.* if you do this.

Recoverymode doesnt work in the hboot?

If you try recoverymode you will get a blackscreen with an triangle.

most say "press the power button" to enter the recovery mode. if this doesnt work press the "volum up button (hold it) then the power button" this should enter recovery mode.

**EDIT**

http://shipped-roms.com/index.php?category=android&model=Buzz use a www-rom its without a branding. and use a RUU rom.. and pls dont use a froyo rom. after flashing this your root is gone i think but your phone will be alive again.

dont try the cm7 this time. use a stock rom.
[Wildfire General] B0RI5:
is it alive again? :D

i talked today to someone who hat exactly the same problem like you.

it was simple to fix the problem... he (you also?) didnt

whipe the phone before he flashed the cm7. thats why it wont stop looping

in the cm7 animation.

after whiping and reflashing everything was fine.

... did you whipe it b4 flashing? :D
[LG Optimus 2x] djmcnz:
Okay, so I'm working on modding the fonts app on the 2x (Settings|Display|Display font) to get some custom fonts in there. I can't believe the ones they included.

Update: APK for Root Users

If you're rooted then you can still use this method but you may also want to have a look at this thread.
​

In the meantime here's how you can add *any* TrueType font you want as a system font to the 2x. It's quite easy and doesn't require root.

First of all, the fonts available via the above menu are stored in '/system/app/Fonts.apk' which is quite a tricky app and they're cached to '/data/data/jungle.app.fonts/tmp/'. To replace a font all you need to do is swap out a font file in the cache directory with an alternative TrueType font. This is a work-around until I can mod the app and as a result you can not yet change the name of the font.

** DO NOT REPLACE DroidSans or Jungle Gothics **

To replace a font follow these instructions:

1. Decide on a font you do not want:

Love = SJlover.ttf

Playful = SJplayful.ttf

MyHeart = SJmyheart.ttf

Ballerina = TDballerina.ttf

Display = TDdisplay.ttf

2. Decide on a font you want to include:

You can use any TrueType font (*.ttf) from any Windows or Mac or any font web site. I use LuxiSans for my ROM for the Nexus One (Kang-o-rama) and think it also works great on the 2x.

3. Rename your chosen font to the one you want to replace:

For example, you would rename the font linked above from 'LuxiSans.ttf' to 'SJmyheart.ttf'. Note that this is case sensitive.

Use the list above to determine the correct file name.

4. Copy the new font over the old font:

This is not permanent, this is reversible.

Settings|Display|Display font -> DroidSans

Reboot

Use any file manager, explorer or ADB to copy your replacement font

ADB commands (example only, use your chosen font name!):

adb push [COLOR="blue"]SJmyheart.ttf[/COLOR] /sdcard/
adb shell
cp /sdcard/[COLOR="blue"]SJmyheart.ttf[/COLOR] /data/data/com.jungle.app.fonts/tmp/
reboot

5. Select new font:

Settings|Display|Display font

Font will display correctly but will have old name (until I mod the app)

*. To Revert:

Delete '/data/data/jungle.app.fonts/*'

Reboot

*. Remember:

Don't 'say' thanks, 'click' thanks... :)
[LG Optimus 2x] atkhobby:
This is great!

Can I use this to get a smaller system font that will fit more lines into menues and notifications?

Will it shrink that pesky oversize (personal opinion) watch font in the right corner?

Also, I read that this change also applies to the browser when rendering web pages, is this the case and can this lead to pages having misalligning in pages made for a specific font size?