yashsingh1/xdaforums huggingface dataset:
[Legend Android Development] bryanqjx:
Hmm... yah I did what u stated, except this part

I typed adb shell then su straight away but when I ran step 2.windows bat, it still doesn't work. SHowed a couple of quick errors in the cmd and my phone just stays in the "!". My phone is run android 2.2, (build number: 3.15.708.2 CL291292 release-keys)
[Legend Android Development] helldroid04:
do you have the visionary app installed?..
[Legend Android Development] bryanqjx:
Yes, it is installed. Or else how can I access adb shell, su.
[Legend Android Development] helldroid04:
are you done rooting your device?.. double check your gold card if its really working first..
[Legend Android Development] bryanqjx:
Ok but one thing is that when I am done creating my goldcard using the goldcard tool 0.07, there wasn't any files in the disk drive except this same three files(LOST.DIR, android.secure and another file which I can't remember) but is it supposed to be like that?
[Legend Android Development] helldroid04:
yeah.. that's the only files that would be there.. (after patching the goldcard.img to your mmc) so you don't have to worry..

if you're sure that you have a working goldcard on your device proceed to the following steps..

credits to Chirag Vadhia
[Legend Android Development] bryanqjx:
Yes! That's what I did. But when I ran RUU, it gives me an error 140 saying that there was a wrong bootloader version. :(
[Legend Android Development] helldroid04:
i guess those are the only thing i can do for you.. since i haven't encountered that type of error code :mad:

sorry..
[Legend Android Development] bryanqjx:
OK then its alright, tks for ur help.:)
[Legend Android Development] bryanqjx:
WOW! I just tried everything again and it worked I am rooted with software number 1.31 and with android 2.1! I don't know what happened but I do know that I redid the steps and also redownloaded RUU and retried it and it worked!:) Tks for ur help! Oh not to forget, aelsharawi and maffuzer as well. I will always remember u kind developers. Thanks once again!

EDIT: What if I flash a "not working" rom and when my phone doesn't boot, what do I do?
[Legend Android Development] ranger4740:
I guess the best advice is to download a known working rom, as an example OGOs gingerbread which works pretty good, or blayos froyo, both are htc sense based, or you can go for cyanogen 7.10 (Latest stable) these all are working roms for the legend.

best advice is to always keep copies of the clockworkmod (fakeflash) recoveries in the root of your SDcard and backed up on your PC this way you should never have the issue of not being able to boot, the booting clockwork mod (Fakeflash) is always named update.zip.
[Legend Android Development] bryanqjx:
So if I have a bad flash in the future, I just have to run the update.zip file then I will be back to a rooted 2.1 right?
[Legend Android Development] ranger4740:
No, the update.zip is clockworkmod fakeflash recovery, IF you flashed a non working rom or a damaged rom zip file you can boot up into recovery mode and flash something else.

What you can do is flash a working rom, use clockworkmod recovery to do a nandroid backup of that working rom, then you can experiment till the cows come home, when finished playing, all you need to do is then boot up in recovery and restore your backedup working rom.
[Legend Android Development] bryanqjx:
Ok got it! Tks for ur help man!
[Legend Android Development] ranger4740:
Your Welcome! ;)
[Legend Android Development] Kueste1:
HTC Legend HBoot 1.00 no works.
[Legend Android Development] bryanqjx:
Hi

FOr Hboot 1.00, go to this link and follow the guide.:)

http://chrg.zxq.net/htc-legend-root.html
[Legend Android Development] roos_t:
links not working

some of the links are not working... e.g.the goldcard link. can you please update with a working link? thanks
[Legend Android Development] muks11:
Edit 05Jan12: Solved. Mangaed to root using a laptop with XP.

Hi,

I am also getting an error on step 18. The ! is shown but when I open “step2-windows.bat” the error below is shown and the system window dissapears pretty quick so it took a few goes to capture using print screen. I tried disconnecting and reconnecting the USB cable but it does not help. Cant get out the ! screen unless I pull the battery. Tried following the guide twice but its still the same.

Will using Visionary R14 make any difference?

All apps used from links provided in the Guide

Phone is unbranded on Froyo 2.2

Running Win 7.

Any help much appreciated.

edit 24dec11:

I tried updating the USB driver from the link below but still cant the 2nd bat to work. I also noticed an error whilst running the 1st bat file, somthing about "42 device id check fail"

http://androidforums.com/incredible...ivers-adb-bootloader-disk-drive-htc-sync.html
[Legend Android Development] linux150:
Hi !

Tnx for you guide !

How long to wait on step 16 ?

I´m standing

Nothing happens ?

Only htc logo on the handy ....

pse help

Im using Windows7 x64

linux150
[Legend Android Development] linux150:
[solved]

my second partition with win xp did make my day :D
[Legend Android Development] JurrePs3:
After trying for such a long time trying you helped me really well with this tutorial, i made it!
[Legend Android Development] benbad:
Megaupload mirror

Can anyone post a new link for the Legend Rooting Tools and HTC Sync version? I can't find a link anywhere that doesn't point to Megaupload which appears to be shut down.

Edit: The Rootzwiki page for the Legend has a link, they have it hosted on their site.
[Legend Android Development] whpsnp:
Few questions

Thanks for a great guide!

I succesfully rooted a friend's Legend last night. However, there's a little problem.

Recovery is not accessible as it should be. FIrst when I booted the phone into recovery it was fine. I then put the install .zip file for CM7 on the SD card and rebooted into recovery but instead got the exclamation mark.

Thinking maybe recovery was corrupted I was able to flash CWM as an update.zip.

I was then presented with CWM and could flash CM7 and gapps. But when rebooting into recovery it I again get the exclamation mark. Sometimes it is possible to access CWM by holding volume up + power but mostly not.

If someone has any suggestions as to how I can get CWM accessible every time I would be very thankful. It is not crucial as all my friend wanted was a lighter ROM to get his phone running more stably - I would still like it to work properly, though.

Also, am I right in thinking that hboot 1.01 can not get s-off? My friend's phone is still s-on after following the guide.
[Legend Android Development] ranger4740:
My understanding is you can only get s-off with xtclip.

When you get red exclimation mark you press volume up and power button, then you wait for menu to load update.zip.
[Legend Android Development] whpsnp:
Thanks, I have already done that and CWM is installed but only occasionally accessible. Any suggestions why this is happening?

The phone is running CM7 and everything is as it should be otherwise.

EDIT: Solved it by unlocking bootloader and flashing CWM for s-off.
[Legend Android Development] illysmanx:
THANK YOU!

I can't tell you how many other things I've done to try and get CWM installed, after a mistaken update from HTCdev. Such a relief! Thank you so much! <3:good:
[Sony Ericsson XPERIA X10 Mini] achyut:
2nd gen mini "theme chooser" port for the x10 "Mini"???....Sonybread fr mini pro has

the mini pro has it thanks to the sonybread ROM....can any developer port it to the mini to work with gingerbread builds?????.....sorry if i posted a duplicate....didn't mean to
[Sony Ericsson XPERIA X10 Mini] Snusdus:
Now I understand
[Sony Ericsson XPERIA X10 Mini] LKnight:
Yeah because the dev 's already made a v4 ^^...
[Sony Ericsson XPERIA X10 Mini] achyut:
by theme chooser, i din't mean the "gingerbread" theme chooser.NO!!!

the 2nd gen mini's (xperia mini nd the xperia mini pro) has a handy tool to switch between the framework.res backgrounds (the 1st generation mini only had the "BLUE" version). it changes the "general background" of the phone. :cool: :cool:

it's already ported to work in the x10mini pro in the sonybread ROM, i was wondering if it could be ported to work with our mini. :rolleyes:

the pic of the "theme chooser" is attached. see for yourself :)
[Sony Ericsson XPERIA X10 Mini] BPaul:
No! No port sonybread on X10 Mini ;)
[Sony Ericsson XPERIA X10 Mini] achyut:
:( :( :(

am just asking for the rip off of the "theme chooser" from the ROM....da ROM is awesome :) :) great work man!!!!!

but please think about it.am not asking for the ROM, just the "SE theme chooser" port to the mini with your kind consideration :)
[Sony Ericsson XPERIA X10 Mini] deeck:
Where do I find more themes for xperia pro
[Sony Ericsson XPERIA X10 Mini] *boy*racer*:
http://xdaforums.com/showthread.php?t=1167075

Some real good ones here that I found
[Galaxy S I9000 General] filiptc:
While I was on CM7 I kept asking myself whether the time was right to switch to "stock" gingerbread in order to get rid of the few CM7 nasties (such as battery life, FM radio, lack of BLN support,...) without giving up too many of the goodies (performance, performance, performance). I hoped there was some insight into objective comparisons, i.e. people who had tested both and could give some "neutral" feedback. Well, I couldn't find it.

So I now find myself on samsung's gingerbread for the first time and these are my findings*:

Performance**:

CM7

The best I've tried so far. No doubt.

Number of installed apps does not affect performance.

JVR

Acceptable, but after getting used to CM7 there is noticeable lag (lapse between gesture and screen reaction) and hiccups when scrolling down menus. Tested with rfs and ext4 ("lagfix"). All in all, performance is noticeably worse than CM7.

Battery***:

CM7

Improves greatly with GB bootloaders [BL] (custom kernel has to support it) but it only affects standby drain (lowers to about 1~3 %/hr).

Usage drain is ridiculous (20~50 %/hr depending on type of use and connectivity).

Typical average battery life has been about 10~24hrs.

JVR

Standby drain is about the same as with CM7 & GB BL (about 1~3 %/hr).

Usage drain is about 10~30% (general feeling about half as draining).

Typical average battery life is being about 15~36hrs.

Android system process shoots CPU usage up to 99.9% while charging (reboot fixes this). Not sure if this is actually a bug.

Miscellaneous:

CM7

No BLN support (as of custom kernels on Aug 15th). No blinking led notification support.

No FM radio (as of #80)

Voodoo sound/color support is kernel dependent

Minor BT car system (A2DP) bugs. Not reproducible with BT dongle.

Horrible Wifi reception and timeouts with WPA2 + hidden SSID (might be custom kernels).

No TV-out support.

No 720p recording (?)

JVR

BLN support is kernel dependent

Voodoo sound/color support is kernel dependent

I might have overseen a bug or been inaccurate at some point. Please feel free to fill the voids or correct any imprecisions.

*I was on CM7 #80 with Zach's Neo kernel v16 r2 (GB BL!). Have also tried Glitch's.

I am now on JVR Simplicity v0.31 (Semaphore kernel 1.5).

**No OC/UV for the sake of fairness of this test (improves performance about 30~50%).

***Battery findings are merely subjective appreciations I have made on a daily usage basis. No scientific mA/h tests or benchmarks have been made. I apologize for that...

This thread should serve for everyone who has tried both ROMs to give their feedback and for those weighing to make the switch to ask questions and have more info.

Cheers!
[Galaxy S I9000 General] ccrows:
Nice job on writing this up. :)

For me CM7 on the SGS is out of the question, because battery and BLN are two of my most importing things that I need daily.

I even went as far as getting the Samsung Armani Battery 1650Mah battery (same physical size as the stock battery) to give me the extra battery life I need.

As for CM7, I may throw that on my Atrix down the road. Some people that have used the beta of it say they think battery life is better than stock. Time will tell, but battery life is an absolute must on my phones which sadly rules CM7 out for me at least on the SGS... :(
[Galaxy S I9000 General] profalbert:
Problems I have with CM7:

* Battery drain (obviously), but since #86 I usually get through the day without recharging.

* Random reboots

* sometimes suddenly loses reception (comes back after some time)

* broken 2g/3g-toggle (don't know if it's fixed yet, didn't dare to try)

Problems I have with stock-ROMs:

* often Launcher-redraws

* no USB-tethering on Linux

Problems I have with all GB ROMs:

* GPS-performance is bad. It's usable after applying hardware fix, but when comparing with Froyo ROMs (e.g. Darky 9.5), they always win.
[Galaxy S I9000 General] madd0g:
You can get led notifications with Neo's kernel, v17r5 currently. No need for BLN app. :]

Otherwise, CM7 is just smoking the stock ROM, specially if many apps are installed. I can compare the phone to AOSP Desire experience, before I exchanged it for SGS a month ago.

Btw, Green battery saver app helps alot, it turns off wifi/mobile for specified intervals, so less drain when idle and you don't need to manually toggle it. Same **** as iPhone does.
[Galaxy S I9000 General] alinescoo:
I have messed both with CM7 #80 and JVR. Now I am back to stock JVR because CM7:

- does not support 720p recording

- I had a lot of issues with calling, the other person couldn't hear me. This seems to happen randomly to many users and makes it for me unusable.
[Galaxy S I9000 General] madd0g:
There's HD recording @ 30fps on 2 recent nightlies I tried.
[Galaxy S I9000 General] alinescoo:
I was wondering, in CM7 does flash performance is still as low as in stock roms ? Most of the video websites I visit work awfull on JVR.
[Galaxy S I9000 General] filiptc:
In my experience there is a great improvement in flash performance in cm7 (and decline in samsung's gb). Especially in flash video playback. Beware though not to expect anything similar to computer-like performance in this field. :)
[Galaxy S I9000 General] jbdroid:
You want a fast, smooth UI and not expect a drawback in battery use? There has got to be a sacrificial lamb in there. The fact that idle drain is already comparable with stock roms means there is no more "battery drain" issue in CM7. ;)
[Galaxy S I9000 General] jaju123:
I left CM7 with fugumod kernel overnight, I lost 2% battery in 9 hours.

I left Simplicity overnight. I lost 10% in 9 hours.

Just my findings off of one test :)
[Galaxy S I9000 General] johnhagi:
Nice Job

Thank you for your interesting info
[Galaxy S I9000 General] Galaid:
for me, flash is crazy good since jvq and flash update. 720p fluid in the browser. silky smooth scrolling, gpu helps a lot.
[Galaxy S I9000 General] Red_Vex:
Quite accurate but:

-wifi for me is horrible on stock and cm7...compared the galaxy s my old iphone 3gs was much better.

-battery when phone is on use is same on cm7 and stock... 'till you use data connection. When using 2g/3g on cm7, battery goes down like a hell.

This because samsung driver are closed source i suppose.

Imho Gingebread is not a great update respect froyo.
[Galaxy S I9000 General] vertigoct:
Just switched back to stock rom from cm7 nightly. I really liked cm's features but after a while the battery drain was too much.
[Galaxy S I9000 General] Necrolust:
I was just about to post a thread like this! The last samsung rom i tried, jvq, was for lack of a better word, **** compared to CM7. I wondered if JVR was better but its probably not much better than jvq. For me, i think i can live with the 'drawbacks' of CM7 as it just makes the phone as good as it should be - fast as hell.

Interestingly enough, as you can see from my sig im posting from a galaxy tab. The stock sammy firmware on this is much better on this than most stock sgs roms.
[Galaxy S I9000 General] kar200:
I have to say that I was the same (and I still like to switch roms) but JVR is like from a different dev team at Samsung. I am talking about stock JVR. Give it a try and you will see that it is the perfect stock rom.

My issue with CM7 are the colours. Both on stock and Voodoo. There is something about it that I can't get right even after following a few guides here.

Having said that, CM7 is a very good, features rich, fast rom. I don't think any stock rom would get to that speed due to the filesystem difference.

K.
[Galaxy S I9000 General] alinescoo:
It's interesting that nobody mentions the problem during calls. Is this an isolated problem, happening to only a few of us ?
[Galaxy S I9000 General] Dr. Strange:
I am very very impatient when it comes to responsiveness so I'm on CM7 for a while. Hoever, most likely, I will go back to stock because of:

-problems during calls (other person can't hear me - hold-unhold call sometimes fixes this, sometimes not)

- headset controlls not working (can't answer calls, can't control music); very annoying, this was introduced when a fix for FM radio was tried. FM radio still does not work but it managed to screw up the headset controls

- no 720p recording - well, you CAN record but the frames skip a lot and audio is not synced

- when using 3g/h battery goes down REALLY fast and phone heats up a LOT

- last but not least devs are concentrating on SGS2, so any fixes will probably take a long while to be implemented (if there's gonna be any fixes); the development has slowed a lot (still, my thank to the devs for their hard work)
[Galaxy S I9000 General] frankhart:
The grass is always greener on the other side, is it? I love CM for its pure android experience, its speed and the control. But yes, there are bugs and that's to be expected if you have to work with closed source blob's and pretty weird hardware (search for atinm's post in the CM7 thread). I'm willing to live with the remaining bugs because the advantages of CM7 are just to big. But my next phone is going to be a Nexus one for sure. That's the only way I'm guaranteed a real android phone without any of the OEM crap.
[Galaxy S I9000 General] xchasa:
Jvr odexed with a few fixes is best for me. Camera, colours, no radio and battery drain just not good enough on cm7 for my needs.

Stock Samsung jvr is better than my cm7 2.2.4 nexus one.
[Galaxy S I9000 General] lcampori:
tried CM7 only once a couple of months ago - so maybe things have improved a bit - and got back to stock a week later because of absurd battery drain. I am now on odexed stock jvr with cf-root 4.1, and fixed phone.apk and browser, just a little icon theming, launcher pro. Phone is about as fast as it should be, no fcs, reliable, smooth, and with good battery life. I really see no reason to go back to CM7, or try miui.

btw, my wife's htc desire is on CM7, I really like it but on that phone it runs flawlessly. Really really not the same on sgs.
[Galaxy S I9000 General] Red_Vex:
See the changelog of SGS and SGS2 and see what is more supported.
[Galaxy S I9000 General] serega43:
The only reason I don't use CM7 anymore is its poor battery life, everything else was fine. I hope battery drain will be fixed soon.
[Galaxy S I9000 General] Necrolust:
I think ill make a nandroid and try jvr. Odexed or deodexed? I know the deodexed one had issues but that's been fixed hasnt it?
[Galaxy S I9000 General] kar200:
Stock JVR Odexed if you ask me. I have been using it lately and I cannot fin any issue with it. I know people talked about FC's somewhere but I suppose I do not use the phone that much to be able to get this FC.
[Galaxy S I9000 General] xchasa:
I've added Milkys jvh modded phone apk and not one fc on phone since. Its on his Rom thread as a single apk file.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Shahpur.Azizpour:
Hi All,

is there an easy way of flashing vanilla honeycomb on the transformer? i'm not interested in any cooked roms, just the pure google experience.

I don't like the additional apps and the slight ui changes that acer did, so i wonder if there is any stable vanilla android rom out there to be flashed?
[Eee Pad Transformer Q&A, Help & Troubleshooting] Lawliet:
If you mean one built from AOSP, I'm guessing there is none out there because the Source Code for Honeycomb is not released.
[Eee Pad Transformer Q&A, Help & Troubleshooting] CrazyPeter:
Acer?

From what I can tell, the Asus Transformer comes with stock Honeycomb. The only changes are to support the keyboard, and addition of crud like Kindle and some other bundled apps (which can be removed if you have root).

This is also the reason why we get updates so soon after Google release them, as there is not too much to tweak.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Shahpur.Azizpour:
yes of course i meant asus. well they changed icons like the default home, back and apps icons from bluish tron style to white. This can't be stock honeycomb.

i know this is nitpicking, but i don't understand why they changed the icons, they just don't fit in, especially since asus left all the other ui elements unchanged...
[Eee Pad Transformer Q&A, Help & Troubleshooting] JaiaV:
Before I flash the Prime roms I always pull the SystemUI.apk out of the /system folder in the rom and exchange all the dock button images for the ones from the default buttons.
[Eee Pad Transformer Q&A, Help & Troubleshooting] david279:
It's stock honeycomb with some buttons changed. That's it. Bam. As stock as it gets.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ryan stewart:
Just root, flash the stock UI and delete the other apps and its stock honeycomb. Ive been running that for a while, mainly its OCD. I didnt like that the UI of the buttons didnt match everything else in android so I swtiched to one extracted from the XOOM. Then deleted all of the myCrap and bought Splashtop HD (prefer having updating versions from market anyway.

I can see why asus changed the buttons. They are more cartoonish than the futurist versions of the stock Honeycomb UI. Nerds like us prefer the TRON theme but joe consumer probably prefers the softer UI (more like the ipad). Im sure its for those people, not us. Im betting they would have gone further if they could but the notification system seems to be pretty locked down, Ive installed phone apps and their notifications immediately become like honeycomb so something in honeycomb is changing their icons/text.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Shahpur.Azizpour:
Yeah ill probably get an transformer over the acer iconia tab cause it already has 3.2 in Germany while iconia still is at 3.1...
[Eee Pad Transformer Q&A, Help & Troubleshooting] Shahpur.Azizpour:
Ok sounds good enough for me. At least I'm not the only one who doesn't like the new icons...so as long as flashing a xoom build is possible that's perfectly fine...
[HTC EVO 3D] dodgeboy:
Does anyone know of a working tun.ko module for the 3D? It's difficult to search for because this site won't let you search for something that is only 3 letters long (very helpful).

Preferably, I'd like to be able to run it with the stock kernel, but I don't know if that's possible. I'm currently running the stock rooted rom.

Any input would be greatly appreciated.

Dave
[HTC EVO 3D] wbchristmas:
Just received a notification that there is an update available for the Evo 3D:

System Upgrade 2.08.651.2 (45.67MB) - FOTA Update

Anyone know about it yet? What is it supposed to fix?
[HTC EVO 3D] joeykrim:
yea, everything is answered in the other thread. i linked to the specific post which answers your question. i'd copy/paste but its a screenshot of the description for this OTA.

http://xdaforums.com/showpost.php?p=16766467&postcount=13

hope that helps!
[HTC EVO 3D] 84guy:
Biggest thing is that its 2.3.4
[HTC EVO 3D] neopolotin75:
wrong post.........removed
[HTC EVO 3D] bambamishere:
I am rooted with viper rom,do I get the ota update?
[HTC EVO 3D] deathtech:
Also...

I Too am curious if this will replace the ROM (Sounds logical that it would) , or potentially bork it.
[HTC EVO 3D] fuzion22:
If you are currently Rooted, don't take the update, just wait and the Dev's will update their roms with the new OTA. You don't want to lose root.
[HTC EVO 3D] fuzion22:
Doh here is the link in the dev section to the rooted OTA, 2.3.4

http://xdaforums.com/showthread.php?t=1223979