Develop Bugs

[Q] First Time Flashing and Bricking It!

Right please forgive my noobishness (is this even a word?) but Im really worried about flashing my phone for the first time.
I have partitioned my card, titanium backed up and created a nandroid back up now all thats left is flashing.
Im planning to flash this rom: http://forum.xda-developers.com/showthread.php?t=768703
What I am worried about is bricking it without lack of knowledge of radio files and how to properly do it. Something about GSM and CDMA?
Plus I saw in the thread this: "Use either Amon RA or clockworkmod Recovery < also available via rom manager from the market"
Why do I need to use them?
Help please preferably with a step-to-step guide?
Thanks in advance.

Read this:
http://forum.xda-developers.com/showthread.php?t=696189

Do I need to switch S-off?
Do I need to flash the radio files and what is the difference if I do or not?
Plus should I use ROM Manager to install the new ROM?

Wait just noticed my current baseband version is one you can download from the Leedroid site, so does that mean I dont have to flash a radio file?

you never MUST flash radios, it is only a possibility
my advice, since you are obviously new to this, dont change radio, i used the radio that came with the phone since december and it worked OK.
usually you should consider upgrading your radio if it doesnt work well e.g. bad reception, data or wifi problems etc.
when you are more confident with flashing, go S-OFF (which is super easy, seriously) and learn to use FASTBOOT which is the safest method of flashing radios or recoveries

[Q] Questions about flashing radios

Hi,
I just flashed a 2.3.3 stock-rooted ROM and well, as everyone is saying, the battery is draining way too fast!
On the actual post where i got the ROM, they provide a radio, but im a little curious about this who radio thingy.
1- I have a nandroid, restoring will bring back old radio?
2- is there a way to backup the radio if the answer to question1 is NO
3- what are the risks, and does it happen alot?, or is it a rare case?
4- they say it can brick the phone, is there any possible way to get out of that state?

1- I have a nandroid, restoring will bring back old radio?
No
2- is there a way to backup the radio if the answer to question1 is NO
Download your original radio from this thread
3- what are the risks, and does it happen alot?, or is it a rare case?
Just read the Radio Thread.
4- they say it can brick the phone, is there any possible way to get out of that state?
Once it is bricked, just send it for warranty. Most probably, they will change with a new one since they can't really know what you have done to the phone.

Hmmm, if it gets bricked, then i wont have my phone for MONTHS! since im in a different country than where i brought it, and i dont have HTC support here.
anyway, i couldnt find my radio type in the link you gave me - mine being:
12.28b.60.140eU_26.03.02.15_M3
but ofc this is the one that came with the 1.32 FW when i was degrading, so can i just extract the radio.img from the PD98IMG.zip file and the flash it? or will it cause problems?

You don't (can't) flash radio's in the same way as a ROM. Read the radio thread.
PD98IMG or the safer method IMO is fastboot (search if unsure what fastboot is).
Sent from my Ericsson T39m

na, i know what fastboot is....
but what im saying is...say i update to a new radio, and its worse than the last, can't i just take the radio.img from the 1.32 PD98IMG.zip file and use fastboot to flash it back?
Or say i found the 12.28b.60.140eU_26.03.02.15_M3.zip radio file, can i flash that?
OR is the only way to go back to the radio by flashing a RUU?(because i heard that installs a new radio).
i have radio and eng S-OFF.

CodeNameUnknown1 said:
but what im saying is...say i update to a new radio, and its worse than the last, can't i just take the radio.img from the 1.32 PD98IMG.zip file and use fastboot to flash it back?
Click to expand...
Click to collapse
Not tested that method sorry.
CodeNameUnknown1 said:
Or say i found the 12.28b.60.140eU_26.03.02.15_M3.zip radio file, can i flash that?
Click to expand...
Click to collapse
Yes.
The great thing about Radio S-OFF and ENG S-OFF is it allows you to play with radio's.
Just to clarify, and this is aimed at others new to all this, the term "flash" in this case is referring to using fastboot command (think of it like adb but with phone in HBOOT - put very simplistically) to push the file to the phone.

kol man, thanks, ...
i think the 1st method would work, cuz at the end of the day, when flashing the whole PD98IMG.zip it flashes the radio along with other stuff ... so just taking it out would, i presume, would work ...
i'll update my radio soon, maybe, and if its bad, then i'll try the method! ...

No worries.
In theory method one should be ok as the zip is essentially a bundle of files and scripts. The only reason for hesitation is some .img files are slightly modified specifically for us with PD98IMG files.
But if it does work (and hopefully if not you don't get a brick) that would be good news as I often hunt down non PD98IMG versions of things and it would save me some effort.
Please, if not too much trouble, do keep us updated (no pun).

wait .... by doing that i can get it bricked?!!?!?!?!? loool
then i guess im not doing it!, lol, im still in love with my desire hd!!!

IF, a BIG IF, the radio.img file within a ROM PD98IMG file has been tweaked in some way there could be a risk that pushing the file through fastboot could brick the phone. Doing anything with Radio files is possible the most dangerous thing you can do (certainly it's the only thing I do frequently that still makes me hold my breath).
My advice would be, if there is a "normal" zip file of the radio I'd take that and push it via fastboot (after checking the md5hash).
That may be an answer, see if the md5hash of the radio.img is the same from both sources.

i cant find my original exact radio.
i have found some radio near my current one( 12.28b.60.140eU_26.03.02.15_M3) but they have a difference in the letters (i.e. Radio_12.28b.60.140e_26.03.02.26_M - without the 'U' and its .26_M, no M3 or .15)
whats the difference, and what do they mean? -- i googled this but couldnt find an answer.

I have a question for radio.
(will borow these theme, if you dont mind)
I have ship s-off (i read that i can't flash radio becouse of this)
my Radio is 26.03.02.15_M3
This is an old version, and i would like to have a new version, becouse i have a lot of problems by flashing newer custom roms, wich have other radios recomended i quess :? ?
1. question: Is possible that i have problems flashing new rooms becouse i have an old radio ?
2. question: how to get from ship s-off to eng s-off? The standard root procedure dont work :s
Thanx for answers

gagi´d hype said:
I have ship s-off (i read that i can't flash radio becouse of this)
Click to expand...
Click to collapse
You NEED Radio (ship) S-OFF (as a start)
gagi´d hype said:
1. question: Is possible that i have problems flashing new rooms becouse i have an old radio ?
Click to expand...
Click to collapse
No. But some ROM's work better with more up to date radio. What ROM are you wishing to try?
gagi´d hype said:
2. question: how to get from ship s-off to eng s-off? The standard root procedure dont work :s
Click to expand...
Click to collapse
Follow the guides in the development forum.
http://forum.xda-developers.com/showthread.php?t=855403

Mr_JMM said:
You NEED Radio (ship) S-OFF (as a start)
No. But some ROM's work better with more up to date radio. What ROM are you wishing to try?
Follow the guides in the development forum.
http://forum.xda-developers.com/showthread.php?t=855403
Click to expand...
Click to collapse
I have tryed a lot of rooms, at the and i have an Revolutin HD with adw louncher and density on 180 (the best screan for me)
I flashed then Revolution HD with GB, i think its an 5.1.3 version, and the rom dont work properly.. I have load again the adw louncher and do the density, but there was a looot of bugs, with people app, with screen (lot of freezes) etc..
i dont know what is the problems, is it the radio or just GB room don't allow the unsense louncher and desity settings..

CodeNameUnknown1 said:
i cant find my original exact radio.
i have found some radio near my current one( 12.28b.60.140eU_26.03.02.15_M3) but they have a difference in the letters (i.e. Radio_12.28b.60.140e_26.03.02.26_M - without the 'U' and its .26_M, no M3 or .15).
Click to expand...
Click to collapse
Honest answer is I am unsure other than various protocols by various networks / manufactures (The "U" ROM I believe was provided by a specific network). There is something in there that determines if it is specific to HSDPA vs EDGE etc. but again, my memory fails me.
If you're willing to go on say so alone go for the second one as that's been tested thoroughly however, it is old so if you feel your signal, wifi, GPS isn't as good as it should be and when you're feeling more confident it could be worth trying some of the more recent ones
[EDIT]
Going back to something I said earlier, a PD98IMG file can be JUST a radio. If you don't want to use fastboot commands then here is a thread that contains PD98IMG versions of the radios.

gagi´d hype said:
I have tryed a lot of rooms, at the and i have an Revolutin HD with adw louncher and density on 180 (the best screan for me)
I flashed then Revolution HD with GB, i think its an 5.1.3 version, and the rom dont work properly.. I have load again the adw louncher and do the density, but there was a looot of bugs, with people app, with screen (lot of freezes) etc..
i dont know what is the problems, is it the radio or just GB room don't allow the unsense louncher and desity settings..
Click to expand...
Click to collapse
Not every ROM (and with it the Kernel) and especially home launcher apps are happy with resolution changes. Whenever you experience bugs like this the first step is reset things like resolution and then if still bugs remove any launcher you have added the ROM.
ARHD (Revolution) is a fantastic ROM and should be bug free.
Try LeeDroids as that is my favourite and I've never had a problem with it.

Mr_JMM said:
Not every ROM (and with it the Kernel) and especially home launcher apps are happy with resolution changes. Whenever you experience bugs like this the first step is reset things like resolution and then if still bugs remove any launcher you have added the ROM.
ARHD (Revolution) is a fantastic ROM and should be bug free.
Try LeeDroids as that is my favourite and I've never had a problem with it.
Click to expand...
Click to collapse
I have flash to the eng s-off now
I see taht a lot of rooms have problems with resolution settings, (i am a litlle angry becouse the resolution on standard sense display is like the people are blind )
That is why i use an adw louncher, and on 2.2 ARHD everything work perfect..
i hope that i will solve the problem with radio, (if not i wil goo to standard density)
ok, thank you very much for the help..

gagi´d hype said:
i hope that i will solve the problem with radio, (if not i wil goo to standard density)
Click to expand...
Click to collapse
The radio has nothing to do with your bugs.
The radio controls mobile signal, wifi, gps and bluetooth.

[Q] Should I s-off my phone?

I have a HTC Desire, (PVT4 SLCD, Erasesize 40000)
I have rooted my phone for almost 4 months. I already know a lot about flashing etc, but never researched s-off. It seems kind of risky to me, as i have the latest desire. Correct me if i'm wrong. I have a few questions.
1.Is it worth to s-off my device
2.If so why?
3.How big is the chance of bricking my phone
4.If i s-off which rom should i be on, as i saw that heavy sense 3.0 roms can make it difficult, AOSP like oxygen or just stock 2.2
Thanks in advance.

1. Yes
2. you can modify system files while booted, not just via ADB. Also you can change HBOOT partitions - so you can use the NAND memory efficiently.
3. If you follow all instructions for the procedure, then there is 1% chance of bricking it. just stick to the info/guide.
4. Some of those ROMs do have problems with s-off. I managed to S-OFF mine on insertcoin's Froyo data++ ROM (2.0.1). But literally most of the ROMs should work. I'd go with something lighter with - e.g. CM7/MIUI/Redux/GV/Oxygen

I'm going to try it today, i think..
Wish me luck

TopGear63z said:
I have a HTC Desire, (PVT4 SLCD, Erasesize 40000)
I have rooted my phone for almost 4 months. I already know a lot about flashing etc, but never researched s-off. It seems kind of risky to me, as i have the latest desire. Correct me if i'm wrong. I have a few questions.
1.Is it worth to s-off my device
2.If so why?
3.How big is the chance of bricking my phone
4.If i s-off which rom should i be on, as i saw that heavy sense 3.0 roms can make it difficult, AOSP like oxygen or just stock 2.2
Thanks in advance.
Click to expand...
Click to collapse
re 4.
after you're done with S-OFF you can run your favourite ROM again, it is just that while you're doing this, you need a "simple ROM". what I did:
* nandroid backup (so you keep your favorite ROM, settings etc)
* flash pre-rooted stock ROM
* S-OFF your device
* nandroid restore (restore the backup you made before).
hope this helps.

With revolutionary one will get rooted and s-off in step.
Swyped from Oxygen with Transparent XDA App

You can follow this guide at http://wiki.rootzwiki.com/index.php/HTC_Desire for S-OFFing with Revolutionary. It's better detailed than Revolutionary's own wiki.
You may not have to do the Installing Superuser and su step if you're rooted already, mine stayed rooted when I S-OFF'd today.
Big advantage of S-OFFing is I could start using the Oxygen r2 HBOOT from Alpharev.nl site, making the system partition drastically smaller (250mb is wasted space for custom roms that aren't bloated Sense) that way I could use more of /Data for apps. It's apparently better for battery life not having apps load off the sdcard with the various apps2sd and dalvik2sd workarounds when using an sd-ext partition.
I did need to move fastboot.exe to the folder adb.exe is in in order to flash a new partition image (instructions on alpharev.nl; scroll down to "modified partition tables") as I got an error about AdbWinApi.dll being missing. They've changed things around in the Android SDK installer so adb.exe needs an additional download via SDK Manager.
p.s. Also I restored my backup of Sense before S-OFFing, just to be on the safe side, Alpharev.nl recommended this but the other guides made no mention of it. It was probably best as my current ROM, Oxygen, has apps2sd implemented and apparently this can interfere with the flashing process.

Another thing, i don't have time this week because of a wedding, but is it crucial to make a nandroid as i can't restore one(amonra 2.0.0), i'll try revolutionary when i do it.

Should I flash a new HBoot?

Hey, guys!
I'm considering whether or not I should flash the CM7r2 HBoot on my Desire. It's already S-Off, currently running coolexe's Cool3D Aces v3. As this will be my first time flashing a new HBoot, I have a couple of questions:
1. What are the advantages of flashing a different HBoot? I already know it changes the partitions layout, so I'll get more space for data/apps, but are there any other differences, like more stability/speed in CM7r2 ROM versions?
2. What's the easiest/safest way to flash? I plan on using the PB99IMG method or the Android Flasher as I'm not really familiar with adb commands and stuff.
3. I realize there's always a risk involved, but in the event that something goes wrong, will the phone be permanently bricked or is there still a chance I might be able to get it working again?
Sorry for the noob questions and thanks to anyone who takes the time to answer.

1)Most devs seem to use CM7r2 as their standard hboot of choice. So what you'll find is that there will be more rom's available for you to flash, giving you more choice of what you want. Another big advantage is that in most cases it'll save you from having to flash another stock hboot zip over the rom, which seems to be a way some devs overcome the stock hboot issue.
2)I have no clue how to use adb, but Android Flasher has always worked well for me, and as a bonus it's an easy way to flash splash screens, boot animations, radio's etc.
3)Like you said there's always a risk involved with messing with the systems in your phone. But your pretty much golden if you do your research before hand and follow the guides that have been posted (http://forum.xda-developers.com/showthread.php?t=1016084 is a good one).
And in the unlikely event that something does go wrong there's loads of great guys on here who can help with pretty much any problem.

1) Not for speed or stability, no
2) They're all easy. PB99IMG.zip is my least favourite as you have to remember to remove the zip from SD or you'll be prompted to install it again every time you go to hboot. I use fastboot commands (nothing to do with adb at all - See FAQ in my signature) and android flasher is just a gui for fastboot commands
3) Ensure you get and check the MD5 checksum of the hboot before flashing to ensure it matches. Dont do anything stupid like pulling power or connection whilst flashing and you should be fine. Flashing a corrupt Hboot can cause brick (all bricks are permanent, anything that calls itself a brick and is fixable is not a brick)

rootSU said:
2) They're all easy. PB99IMG.zip is my least favourite as you have to remember to remove the zip from SD or you'll be prompted to install it again every time you go to hboot.
Click to expand...
Click to collapse
I rename them to like pb99img-stock.zip and pb99img-cm7.zip so that I don't get that prompt everytime I want to change, I just rename it back.... I find it the easiest method(probably because i was without pc for over a month ) but fastboot is the safest. Always double check (if not triple) the Md5
Ps. You can check it through phone too... Using hash Droid from the market
...aes eht rednu
peed morf tneS

Thanks a million, guys!
I Just flashed CM7r2 HBoot using PB99IMG.zip, worked like a charm in a matter of seconds, currently restoring ROM and apps

Sweet, it were the same for me
Im getting really used to this now

I cant go without my cm7 hboot lots of storage

what's the /system /data /cache ratio on hboot 6.93.0002

[Q] Complete noob humbly asking for help

Hey guys,
I've been around the Defy forum for quite a while now; however, my Desire is back from the dead and now my beloved
Motorola Defy is retired, which means that I'll be getting to know this forum instead!
Right now I have absolutely nothing. Just a TELUS Desire GSM on 2.2 stock froyo. Can someone point me in the right
direction for rooting and S-OFF? Do I need to unlock my bootloader as well for most ROMs?
I have this ROM in mind:
http://forum.xda-developers.com/showthread.php?t=1980122
Everything is pretty straightforward except for a few things:
Someone PLEASE help me, but I'm not going to be demanding or anything. So help me if you can.
1. How the hell did you guys end up with, like, 10 different recoveries and HBOOTs? I've heard CM7R2, stock, Amon RA, among others.
Someone can clarify this?
2. I don't get the partition things at all. For the above ROM what do I need?
3. And just how to root and S-OFF and unlock BL if I need to...
4. A simple procedure for all this maybe?:silly:
5. A simple explanation on how HBOOT and recovery and custom recovery work? On the Defy, we had a 2nd-init and 2nd-boot that basically
launched a custom ROM and kernel on top of stock because the bootloader was locked down. The CWM recovery was accessible from the bootmenu, which was in turn launched by pressing volume-down at the blue LED halfway through boot.
6. Last and not most important does the ROM above (Cooldroid Revolution 9.0) have working Wifi? It says it's "fast, smooth and stable" but...
Thanks so much.

Soooo...
Welcome to the Desire forums.
You should start by ignoring anything that has to do with the Defy. You don't need to unlock the bootloader.
Now, let's start with s-off.
Follow this tutorial Long link, and ignore step 2.
After you're s-off, you should install 4ext recovery. It's the best recovery for the Desire.
In this guide, you will install 4ext, and create an ext partition on your sd-card. The partition is allocated for more internal memory (more apps).
http://forum.xda-developers.com/showthread.php?t=2125513
Read every guide carefully. You will learn a lot.
After you did those things, you can install a custom ROM. I don't recommend you use the one you mentioned as a daily one. It's still a work in progress, and has a lot of bugs.
There are many hboots. When you change hboot, you change the way the internal memory is partitioned.
For example, the cm7r2 hboot has a smaller system allocated space than the stock hboot.
You usually change hboots to get more app space.

Thanks!
But what about root? What tool should I use?
Edit: never mind, I saw the guide link in your signature
I'll get back to you when I'm done rooting. Fingers crossed.

You will root it when you either install a custom rom, or install the supersu zip.

So I read up on some guides that told me to use unrevoked, so I have this reflash_package.exe ready to go. I've uninstalled HTC sync because unrevoked tells me to.
Just one question: I can only use CWM recovery if using unrevoked? That's the default, and only recovery available with it. Can I just download the 4EXTRecoveryUpdater.apk later and change it to 4ext recovery?
If I end up somehow with a ROM that does not boot, how do I fix it? Flash an original RUU?

Why didn't you just listen to me? You don't need unrevoked.
Did you backup before flashing a rom? If you did, then restore it..
Flash another rom, or flash the 2.3 ruu.

abaaaabbbb63 said:
Why didn't you just listen to me? You don't need unrevoked.
Did you backup before flashing a rom? If you did, then restore it..
Flash another rom, or flash the 2.3 ruu.
Click to expand...
Click to collapse
I did it! Thank you so much for helping me, despite all my noobiness in this forum.
I'm running Cooldroid Revolution 9.0 now. Again, thanks so much. About 7 hours later after I started reading up
and working with my Desire, I've learned a lot of things about S-OFF and HBOOT and EXT4.
I did a nandroid backup of my original 2.2 ROM before I formatted my SD card and it's backed up on my new
fat32 and my desktop as well. I guess I'm safe for now.
Oh and one more thing, are RUUs like a last-ditch attempt to save your phone? I remember there was a 2.3 RUU upgrade
that came in the form of an .exe and you just needed to plug your phone in, the .exe would do all the upgrading stuff for you.

Yeah. Ruu's are usually the last things that can save your roms.

Even noobier
I am even more of a noob than anyone else I've seen on here.
I am a college student, and I'm considered the best programmer in my class, so I was hired by my school to develop a mobile app for the admissions department. One of my classmates already developed one for apple, but he graduated, so my job is to create one for Android. They are fully aware that mobile app development is not taught here, and none of the people I will be working with knows anything about it either, so it is going to be interesting, to say the least.
My best language is C#, so Java should be no problem, but I am completely at a loss as to where to start. All the app development information I've been able to find is geared toward Ice Cream Sandwich, but I want to make sure my app works on Gingerbread because of its huge market share, plus anything newer.
I've looked at the "beginners" threads on here but I don't understand even half of what people are saying (I speak geek but it's a completely different dialect lol). Is there a resource somewhere where a good C#, Visual Basic, and SQL programmer can teach herself something completely new, and do it right?

Try this guide:
http://developer.android.com/training/index.html

Thanks, I will look into that
Sent from my T-Mobile G2 using xda app-developers app