yashsingh1/xdaforums huggingface dataset:
[About XDA developers] jonasb:
I am getting annoyed of many ROM threads here, because they are

stating "speed improvements, minor fixes, stable" - if you cant name it exactly, i call bull****.

ROMs being based on the same RUU as other ROMs but not stating what is different. please stop wasting my time. i dont want to go sherlock holmes on your ROM. when you just spend 2h, to make a ROM that is basically the same like most other (just differeing in the point above) - thats fine, you can play around and share it here - but PLEASE tell us.

incomplete list of what is working or not. listing only BT as not working and then reading on the third page "animations and browser download dont work" and then a reply "they dont work on any sense 4.0 ROM". Or stuff like "bugs: you tell me". could you please take 10minutes to test against a checklist?!

so whats my point:

I am no ROM developer, but a software developer. And I see all the wonderfull work done here. But i hate the lazy "you all probably know what im talking about" attitude around here. I feel a bit scammed by either the very shiny threads with custom logos and artwork, listing as many points as they can - whats the purpose - you dont sell anything here. Or on the other hand the very short threads that omit the most important points, making the ROMs incompareable - are you hiding something?

so i propose:

an enforced thread layout, that is composed by the community.

some points i would like to see in it:

name

version

based on (RUU revision number, link)

android revision(, sense revision)

type (a coarse classification: stock, themed, bloatfree, desensed, ported, testrelease, AOSP. multiple selection possible)

changes to base (the 5 main topics of this ROM. at least kernel, bootscreen, keyboard, launcher, theme)

dependencies: firmware etc.

screenshot (i know mostly there is no difference, but i personally am a visual type and need them :))

a bug checklist (also community build, most usual bugs, states: ok, minor, broken, untested)

a tweaks checklist (e.g. rooted, deodexed, zipaligned, crt, recent apps, APM, battery, /etc/hosts, beats etc.)

APK versions (also a community build checklist, maybe a script for that)

changelog (for each old version a download, for each change a source link, not just "thanks xyuser" - having the ROM in github etc. would be awesome)

I bet there are some more points - i think the non-developers should unite and demand a bit of quality. Develop and enforce a standard. Use this thread to gather ideas.

And inb4 "be gratefull and take what you get" - no, I think chefs have a responsibility to be transparent, they get lots of testers and glory in return. XDA is a central reference for everyone who roots his device. Mods have taken some good steps to clean up the mess. Now its time for the next.

I think the more detailed the information gets, the faster the development will become and users can build trust in what they flash.

Mods, would something like this be possible?
[About XDA developers] MOVZX:
Yes, it will make everything easier for the users too compare one with another.
[About XDA developers] jonasb:
thats what I think. any other oppinions?
[About XDA developers] azzledazzle:
I also agree, There are way to many roms out there, I couldnt possibly flash them all and test them, My phone would be outdated by the time i managed that.

The majority are exactly the same, except with the occasional different theme /tweak /app but other than that i think they are similar...

I also get the feeling that the ROMs are a pretty much copy & paste job (with the exception of the devs that build from scratch)

I would like to see some sort of organization in the development thread.. I have nothing against these ROM Makers, But if the first post pointed out what exactly makes THIS ROM different than any others. i think it would be less confusing to people..
[About XDA developers] mugetsu666:
I am so for this. I am tired myself of all the crap too. I would like to know what I'm getting and how stable it truly is. I mean saying it's stable but then u find our in post number 400, that one the newest release there are some bugs which don't make it go for every day use. And if it's kanged, tell us, some do tell us but then same get someone else and make it theirs with some changes but nobody finds out till later. I'm also tired of ppl causing problems for others, whenever they follow rules more than others, and tell them this is such & suches place u better leave. I that's y some really good ppl leave here and sometimes the mods allow it cause they're friends. It's total bs, but this is just how I feel!
[About XDA developers] azzledazzle:
+ 1 ^^^

I get belittled sometimes in them threads, Im just trying to ask a simple question and the replies are 'dude.. this was asked ten times already.. look at post 862816745 and you will see....' The damn threads change so fast i cant keep up.. Im not a noob... maybe a novice to the sensation but i know what im doing in general.

People expect everyone to know how to do things - because they have done it themselves so many times... Id rather help someone with the simplest question than shout at them for not asking for help and bricking their phone...

C'mon guys, play nice :D

Rant over lol

EDIT: Good Idea

l

l

V
[About XDA developers] k0zmic:
Maybe there should be a forum for 'Original Development' for projects that aren't a variation of another project. I've seen this for other devices' forums.
[About XDA developers] MOVZX:
Looks like I was never enjoyed my phone even just for 1 day. Today I've installed a ROM, adding many apps from Market which took many hours to setup & configure.

While I've become comfortable with the ROM, something freaked Me ouy: "Oh, there is even better and way more stable ROM available than this current ROM." Downloading, it takes about 1 to 2 hours. Then booted the ROM, but I caught myself disappointed with the news, "This new one has just another clone of the first ROM I've ever tried." Oh no, it has different theme and feels! "All of them are on the same base, same kernel, same etc, etc, etc."

Then, my final decision should be restoring the first ROM through Recovery, but again it takes minutes to complete.

And yet, I fooled with Battery Calibration placebo/myth which actually doesn't exist. Do I need to recalibrate my battery on s ROM changes? No, Google Official has just stated it's just a myth and placebo.

This is what I feel, sorry I mean no offense to any Devs.
[About XDA developers] mugetsu666:
Dude I am so with u. Some threads r just so damn long that to every little post would take to long and I would probably never be able to flash a rom. As far as noobs go, we were all noobs at one point. I get most to get me on gtalk so I can help them without some as telling them off. Yeah sometimes it takes me some time but hell I've been able to save quite a few phones.
[About XDA developers] azzledazzle:
Its a much better feeling knowing you have helped someone and saved a phone from the horrible stock ROM or possible brick..

Ive done my fair share of helping noobs to help other noobs... Ive also saved a few phones from the trash too :)

XDA is a community - not a place to rant at people for being a noob - Although there are some hopeless people out there who do not follow the rules, But the majority of us just need some guidance..

The worlds best android developer wasnt born the best... he / she was obviously a noob who learnt from someone else...

The way i see it is that noobs are the future of development :D so dont hate us :D
[About XDA developers] mugetsu666:
I so agree and am getting ready to learn the cooking game from a friend and great deveolper. He's also getting ready to aquire a sensation and is going to port some of his awesome work from the 3d to the sensation, but make it with ics. Don't know if it'll every see xda because of the drama but it'll be on our teams site. It might make since he does have stuff in evo on xda but I don't know yet.
[About XDA developers] rawrfische:
I'll probably get flamed for this, but that's xda.

The devs don't do this for our convenience. As users who don't pay them a salary, I don't think we're in a position to tell them how they should share what they do. They use their spare time to make something and then choose to share with the masses, which they really didn't have to do. How they choose to present their work should really be up to them IMO.

Besides, if you stick around long enough and read the threads now and then, you'll be able to tell which devs are doing real work versus someone who just forks another person's ROM and throws in some personal tweaks.

Yes most of the ROMs are similar in looks or function, but that's too be expected since everything comes from whatever HTC releases. Each one has its own flavor since each dev has different priorities. Want something totally different? Try one of the WIP AOSP/CM9 builds or maybe MiUI v4.
[About XDA developers] mrg02d:
I think the real question is, WHY are the devs doing it at all? There are motives. I think this thread is basically asking them to spare us. If they decide to pack their ball up and go somewhere else, no big deal. The REAL devs will always stick around.

This thread isn't directed at our "patron devs" but all the no names that pop up with these ridiculous, and misleading, clones while asking for donations.

All in all, no one is forcing us to flash their ROM. It would be nice to have several layers to the dev forum. We need a place to easily see what the pro devs are up to without all the mess in the way. Or, how some genuine developing is coming along...

Matt
[About XDA developers] azzledazzle:
I can see it from both sides, All the devs good or bad are still great in their own way.

But some tidying up in the development section wouldnt do any harm... Its like a jumble sale in there, Rummaging around to see whats what. Its ridiculous
[About XDA developers] broncogr:
Thread cleaned.

Now, you watch your attitude and language or simply face the consequences...
[About XDA developers] jonasb:
yaddamean, I understand what you mean but I would say the opposite: devs that dont care to be transparent, can host their ROMs on their servers elsewhere. I know this is a quite fundamental difference in views. But i dont get what should be the advantage of being the silent majority.

Good things never come easily.

I bet we would not loose one good dev.
[About XDA developers] broncogr:
Moved to the about Xda-developers forum as such discussions are not device specific but rather site specific
[About XDA developers] mugetsu666:
I agree with u and because of yaddamean and others like him who like to just jump in and flamming ppl. As soon as someone stands up to those kinda ppl, the real supporters of this Site and it's Real dev, get in trouble. That's y ppl leave here too!
[About XDA developers] jonasb:
this will get us less viewers but more mods hopfully :)

is there any chance of changing the current practice?
[About XDA developers] mugetsu666:
That's y it was moved less attention.
[G1 Q&A, Help & Troubleshooting] u2020bullet:
I rooted my G1 using the AndRoot app and i can't seem to flash recovery.

I copied recovery.img to my sdcard root, started the terminal emulator and typed in "flash_image recovery/sdcard/recovery.img" but that usually get's me "access denied", sometimes after i press enter or in the middle of typing.

So i tried to to type in "su" before i typed everything else but then the terminal emulator has to force close. I am seriously about to give up on this. I've been doing it since last night. Can someone please help me?

PS: my build number is "DRC83"
[G1 Q&A, Help & Troubleshooting] demkantor:
well ive never tried to use androot, always just the old fashion way of rooting for me.

which by the way wont take you all night so maybe you could try that?

http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting

to answer your question you dont seem to have super user permissions so nothing needed su will work

out of curiosity, if your on windows and typing .img at the end of the file dont, just name it recovery
[G1 Q&A, Help & Troubleshooting] u2020bullet:
That's the first thing i tried since it's the most fun way to root a phone but i got "not allow" and "serial0" in fastboot.

Yes i'm on windows but i got my extensions showing so that's not the problem.

PS: the goldcard method doesn't work either. Forgot to mention that.
[G1 Q&A, Help & Troubleshooting] demkantor:
Well let's start from the begining, what's your radio/spl, well go from here
[G1 Q&A, Help & Troubleshooting] u2020bullet:
Here's all the info i have in fastboot:

DREA110 PVT 32b

HBOOT-0.95.0000

CPLD-4

RADIO-2.22.19.26I
[G1 Q&A, Help & Troubleshooting] demkantor:
Download the dreaming.nbh file and put it on the root of your sd card. Then boot the phone holding the camera button. Your hboot will load the image and flash it to your phone it takes about 5min or so. Once it says complete you @ android 1.0 and will need to sign in. This is easier if you have a data plan if you don't you will need to turn on wifi via adb. Once there download telnet from the market.

When telnet is downloaded, from home screen, open keypad and hit the enter button twice

Then type telnetd

Then hit home and open telnet, hit enter

then type flash_image recovery /sdcard/recovery.img

(Forgot to say have the appropriate recovery downloaded to sd card and renamed recovery)

Now you can reboot into recovery holding the home button

You know have amonra and can begin with downloading a new rom, radio, and spl. Start slow here and flash the radio in the cyanogen wiki then danger spl then let's say cyanogen5 - eclaire

Once all this is confirmed working we can move on to the 2708+ radio spl
[G1 Q&A, Help & Troubleshooting] u2020bullet:
When i boot it with the camera button i get the "not allow" error and then back to the rainbow screen where it shows "serial0".
[G1 Q&A, Help & Troubleshooting] demkantor:
Then either there is something wrong with sdcard, the dreaming.nbh image, the way you named the image or you got a bad download. Make sure sd card is fat32 and the dreaming image is a fresh/proper download and you name it dreaming.nbh.

Pay attention to the file extentions dreaming will probably be all you need to name it
[G1 Q&A, Help & Troubleshooting] u2020bullet:
I renamed it from "dreaimg.nbh" to "dreaming.nbh" and i also tried "dreamimg.nbg" but all those 2 gave me was a millisecond of text which i couldn't read.

I'll try a different memory card.
[G1 Q&A, Help & Troubleshooting] demkantor:
Sorry I misstyped

Dreaming.nbh. or try

Dreaming
[G1 Q&A, Help & Troubleshooting] u2020bullet:
Can it even load it without the .nbh extension?

PS: i tried a different memory card and two other dreaimg.nbh files and still "not allow" and "serial0".

I swear i'm begining to think it's unrootable...
[G1 Q&A, Help & Troubleshooting] demkantor:
I've rooted over 40 g1s and never have I found one that works but is unrootable. Did you download the .nbh file from the wiki? Also when you boot the phone is the splash screen htc or rogers or g1 or what does it say
[G1 Q&A, Help & Troubleshooting] u2020bullet:
One of them was from the wiki but since that didn't work i downloaded a few others i came across but they didn't work either.

It's a T-Mobile G1. German judging by the qwertz keyboard.

EDIT: Thought i'd throw in some additional info:

Firmware version: 1.6

Baseband version: 62.50S.20.17H_2.22.19.26I

Kernel version: 2.6.29-00479-g3c7df37 android-build@apa26 #19

Build number: DRC83
[G1 Q&A, Help & Troubleshooting] demkantor:
And you said you tried the goldcard method?
[G1 Q&A, Help & Troubleshooting] u2020bullet:
Yeah, same exact result. I can try again.
[G1 Q&A, Help & Troubleshooting] demkantor:
The unlocker has a great video explaining how to do the goldcard method. I only tried it once along time ago just to see how it works, so I won't be too much of a help on that when I'm not in front of a computer
[G1 Q&A, Help & Troubleshooting] u2020bullet:
Actually i have been using their tutorials. But now that you mentioned it, i watched the VIDEO instead of reading the text and it's quite different. So it's updating right now.

Now i'm moving to "Rooting the HTC Dream" step.

I really appreciate your patience and assistance :)
[G1 Q&A, Help & Troubleshooting] demkantor:
No problem, slow day @ work :)

Good luck, let me know if you get stuck
[G1 Q&A, Help & Troubleshooting] u2020bullet:
ok i'm about to flash radio 2.22.19.26i from the wiki.

After that i want to flash Froyo by laszlo. Can i do that straight after that wiki tutorial or do i need to do something else before i flash it?
[G1 Q&A, Help & Troubleshooting] demkantor:
Yeah you need the latest radio and spl. Did you flash the danger spl yet?
[G1 Q&A, Help & Troubleshooting] u2020bullet:
Nope. Where can i find all of those?

i found some here: http://code.google.com/p/android-roms/downloads/list?q=label:SPL

But i'm kinda terrified of messing something up. Which one am i suppose to use?
[G1 Q&A, Help & Troubleshooting] demkantor:
After your radio flash the danger spl found in the wiki link I sent. Then flash cm5 and the gapps. Start your phone and make sure all is well. Then we will move to the 2708 radio spl and get you froyobylaszlo
[G1 Q&A, Help & Troubleshooting] u2020bullet:
Done flashing all of that and now i'm waiting for it to boot, the cyanogen logo is coming up :)
[G1 Q&A, Help & Troubleshooting] demkantor:
Awesome play around a bit, see what cm7 is all about. When your ready to move on let me know
[G1 Q&A, Help & Troubleshooting] u2020bullet:
Ooops, i flashed cm5...

Still waiting for the huge colourful X to stop looping.

EDIT: booted up and running well :)

Now where can i find the radio you mentioned? Can't really see it on the wiki or the google page if found.
[G1 Q&A, Help & Troubleshooting] demkantor:
I ment cm5 your good. Hold camera and boot so we can confirm your radio/spl
[G1 Q&A, Help & Troubleshooting] u2020bullet:
DREAM PVT 32B ENG S-OFF

HBOOT-1.33.2005 (DREA11000)

CPLD-4

RADIO-2.22.19.26i

APR 20 2009, 15:30:43

That's all the info. :)
[G1 Q&A, Help & Troubleshooting] demkantor:
Ok now check out ezterrys thread on the 2708+ .

Read it very carefully and come back if your lost or have questions

Once updated go to laszlos thread for fbl

Let me know your progress
[G1 Q&A, Help & Troubleshooting] frankdrey:
http://xdaforums.com/showthread.php?t=831139

You'll need fastboot

If you don't have it i'll upload it for you

Aw, I'll upload a .bat file to flash this for you if you want xD

Warning: I didn't test this or anything.

If you don't trust my script(which even i don't know if it's good), do it yourself, just use my fastboot.exe. Oh and drivers are included.

cd into the directory with the fastboot.exe and do the commands on the above link i gave

Except change them to match my renamed imgs.

Egh, i'm scared now xD

Do it manually. Please.

http://d-h.st/1q2

Extract it somewhere

the .bat file is the automatic one, but it may screw up

If it does, don't reboot the phone

Do the things the manual way and it should be fine

Or do them the manual way in the first place.

My file will provide fastboot and drivers if you do it manually
[G1 Q&A, Help & Troubleshooting] u2020bullet:
What do i need the fastboot for? it sayd "To be able to use fastboot, you need to be running either an ADP1 or the Engineering Bootloader on your G1. " From the wiki.

EDIT: From ezterry's thread: To Start you will need a fastboot enabled SPL such as 1.33.2003 or 1.33.2005 or 1.33.2010 or 1.42.2000 as I'm not distributing the new radio/SPL in a update.zip ..

I have the 1.33.2005 spl :)

So i'm suppose to flash hboot-1.33.0013d.img and radio-2.22.27.08.img?

Still reading btw.

EDIT2: i'm kinda stuck on reading "Any Kernel installer". How would i flash it without bricking the thing? since i don't understand that thread all too well.

Just got done reading and yeah, i'm definitely gonna need instructions...
[G1 Q&A, Help & Troubleshooting] demkantor:
Well technicaly you can do it w/out fastboot but there's a better chance for a brick. So fastboot is the way.

Ok, do you understand fastboot? Or have you used it at all?
[G1 Q&A, Help & Troubleshooting] u2020bullet:
just follow frankdrey's instructions to flash fastboot? And then we move on to the radio?

And no, i don't think i've ever used fastboot.

EDIT:

hmmm..i can see the radio and spl file..but how do i use fastboot?

PS: been reading this: http://wiki.cyanogenmod.com/wiki/Fastboot

So basically it's like using cmd when making a goldcard. Ok but how do i use it and for what?
[G1 Q&A, Help & Troubleshooting] demkantor:
Phone has to be in fastboot mode, have it connected power on while holding back arrow. Should load driver and say fastboot usb. Now open cmd and change directories to fastboot or if changed variable you can just type fastboot and it will go into fastboot mode. Have the files you need where you open cmd or if you didn't change variables then have the files in same folder as fastboot. You will want recovery, new radio, new spl and make sure you download orange.nbh incase you get stuck without a recovery
[G1 Q&A, Help & Troubleshooting] u2020bullet:
what i have so far: G1 in fastboot mode connected via USB.

Then i unzipped the contents from the zip i downloaded from frankdrey's post and right click+shift, inside that folder. Than i clicked "open command window here"

Then i typed fastboot in that command window and it showed commands that i can use.

How do i proceed from here?

PS: just realized i had fastboot in my sdk folder (had to use it to activate the phone using wifi since i have no data plan)
[G1 Q&A, Help & Troubleshooting] demkantor:
Yeah have fastboot and all the files in the same folder, open cmd there, type fastboot devices to make sure you're connected yo will see a string of letters and numbers

Flash recovery, then radio, then spl,

Once finnished boot into recovery and flash froyobylazslo

You are done!
[G1 Q&A, Help & Troubleshooting] u2020bullet:
flash it like i would usually flash it or through the cmd? sorry if it's a dumb question but i just want to make sure since it's my only phone.
[G1 Q&A, Help & Troubleshooting] demkantor:
Flash the recovery then radio then spl through fastboot then reboot into recovery and flash fbl
[G1 Q&A, Help & Troubleshooting] u2020bullet:
EDIT: nevermind flashed it.

here's my new info:

DREAM PVT 32b SHIP S-ON

HBOOT-1.33.0013d (DREA11000)

CPLD-4

RADIO-2.22.27.08

OCT 21 2009, 22.33.27

So now all i got left is to flash fbl and gapps? or just fbl?

EDIT: flashed fbl. Should i use the google apps from the cm wiki?
[G1 Q&A, Help & Troubleshooting] demkantor:
No gapps are packed in with the rom, only flash rom and then you're done!

Congrats I hope you enjoy it!
[G1 Q&A, Help & Troubleshooting] u2020bullet:
Thanks a lot for the help :)

It works perfectly :)
[G1 Q&A, Help & Troubleshooting] JacobGreen:
Thanks, this works well.
[G1 Q&A, Help & Troubleshooting] demkantor:
I like when I see people use the search option :-)
[G1 Q&A, Help & Troubleshooting] bustmybrain:
HTC Rogers Dream

I am envious as hell.

Hi Demkantor,

Do you think the procedure on this thread would work on an HTC Rogers Dream?

I've rooted my phone via Androot a couple months back but could not move on from there :(
[G1 Q&A, Help & Troubleshooting] frankdrey:
You can use flash_image from a terminal on the phone

First of all, what recovery do you want?

I think amon_ra is the only one that supports rogers

Make sure you download the rogers version

Put it at the root of your sd

Open a terminal on the phone and type "flash_image /sdcard/nameofyourrecoveryimage.img"

Replace "nameofyourrecoveryimage" with the file name.

If it gives errors about something like no space or similar, try again.

There, you now have a custom recovery.

Although if you're looking for a good rom most of them require a newer radio/spl also.
[G1 Q&A, Help & Troubleshooting] bustmybrain:
Many thanks. I will give this a try when i get a break from work.

Wish me luck. I'm gonna need all I can get :p