• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][AOSP]dGB v01_28_2012| 2.3.5| 375MB /data| 60MB /system |Mult-lang |Unlock |Reboot[28 Jan]

In principle you could do that yourself: take one of the existing alpharev PB99IMG hboot .zips and edit it, replacing the image that's in there with the dGB65 hboot image, then flash it from hboot. But at your own risk, because a bad hboot flash is likely to be the end of your phone: the only ways we can fix hboot are using fastboot or PB99IMG.zip, both of which rely on the hboot itself, so if the hboot is sufficiently corrupt then it's game over! Put it this way: I'm 99.9% confident that I could do this myself, and I have never for an instant been tempted to do it ;)

Personally I'd recommend setting up fastboot. You can then confirm the hboot image is good before flashing (md5 check) and be sure that it's safe. If you are mucking around with the phone at this level then fastboot's a useful tool to have available anyway.
 
Hi , I have Desire with dBG ver 2.3.5 Kernel 2.6.35-13-dBG-2.1-EViollet-GB-HAVS-AXI-128CFS, Mod version dGB-01282012

Everything works OK apart from my internal storage. It shows only 148MB total space, but should be 375MB.

What's wrong ? How could I fix it.

Thank you
 
Yes, that's the stock hboot. Like Nicka has said, you need to s-off and fastboot flash the dgb hboot (.img file)
Nandroid backup from recovery
fastboot flash the new hboot
nandroid restore from recovery
 
shauny13 said:
Yes, that's the stock hboot. Like Nicka has said, you need to s-off and fastboot flash the dgb hboot (.img file)
Nandroid backup from recovery
fastboot flash the new hboot
nandroid restore from recovery
Click to expand...

Yes, you're correct, the hboot was stock with S-ON. I followed your instructions, the phone now is S-OFF with hboot 6.93.1002
But I cannot flash the dgb hnoot img from fastboot.
What I do is to power on while keeping vol+. It gets me to whi9te screen with info and choise : fastboot recoveery etc.
If I choose "fastboot" there is only power down and reboot

or shoud I go to recovery ?

BTW I have clockworkmod installed
 
You have to set up fast boot and abd on your computer to be able to flash a new hboot.. I would suggest you read the relevant guide to fast boot and abd in the all about root sticky and go from there. I as it is not as simple as flashing rom. But you have managed to s-off and root so it is only a couple of more steps ;)
 
You need to re-read the root memory faq and the adb & fastboot faq.

There are 2 elements to fastboot: you put the phone in fastboot mode, connect to a computer, then use the fastboot program on the computer to flash the phone.

So you need to install fastboot on your computer. Then make sure you understand the steps to flashing hboot before trying - if at all unsure ask first. Remember to take a nandroid first, as you'll probably have to restore that after the hboot flash (rom and data will probably be corrupted and need reloading).
 
Continue flashing this morning....I had no problem rinning fastboot , but stuck on flashing hboot - tried bot 60MB and 65MB versions but keep receiving :

"
E:\PROGRA~1\Android\android-sdk\platform-tools>fastboot flash boot bravo_alphaspl_dgb65.img
sending 'boot' (512 KB)...
OKAY [ 0.094s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 0.094s
"
:confused:
Ideas ?
 
tanaki said:
Continue flashing this morning....I had no problem rinning fastboot , but stuck on flashing hboot - tried bot 60MB and 65MB versions but keep receiving :

"
E:\PROGRA~1\Android\android-sdk\platform-tools>fastboot flash boot bravo_alphaspl_dgb65.img
sending 'boot' (512 KB)...
OKAY [ 0.094s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 0.094s
"
:confused:
Ideas ?
Click to expand...

It should read fastboot flash HBOOT your only putting boot! Try this and I think you'll be fine!
 
Did it and works, but after nandroid restore from recovery cannot connect to WiFi access point . It hangs on obtaining IP address?!
 
Hey Guys,
This is a long query, please bear with me..

I have an HTC desire rooted running redux 1.2 since last year..I no longer use it as have bought a galaxy s2. Id like to flash this ROM now with the custom MTD layout..I am S-on for now..and also since the Redux ROM supported A2SD I had created an ext partition(not sure of version) on the sd card which is now formatted as FAT32...Will that affect this process in anyway?

Hence now as i start
I will use Revolutionary to S-off, I flash an Hboot to the phone using computer, flash the custom MTD dGB Hboot from fastboot,

Can someone please give me some steps to carry this out and finally to flash the ROM. This is sort of my R&D phone now so I'd like to experiment with everything possible until i brick it..

Thanks.
 
The root memory faq, linked from the All Things Root Guide sticky post, should explain the basics. Beware that there's a procedure called "custom mtd" which is different from the custom hboot, so try not to get these confused (custom mtd is slightly more flexible, custom hboot easier).

I assume you want to try dGB, as you'd need a different hboot for Redux. The ext partition won't matter, as dGB will just ignore it.

What I'd recommend is:

* S-Off
* Install dGB.
* Take a nandroid
* Install hboot
* Restore nandroid

Installing the hboot is just a fastboot flash (see adb and fastboot faq). Alpharev.nl also has instructions for changing hboot on their site.

Always check the md5 code of a hboot before flashing - a bad download is unlikely, but could be fatal to the phone.
 
Hadron said:
The root memory faq, linked from the All Things Root Guide sticky post, should explain the basics. Beware that there's a procedure called "custom mtd" which is different from the custom hboot, so try not to get these confused (custom mtd is slightly more flexible, custom hboot easier).

I assume you want to try dGB, as you'd need a different hboot for Redux. The ext partition won't matter, as dGB will just ignore it.

What I'd recommend is:

* S-Off
* Install dGB.
* Take a nandroid
* Install hboot
* Restore nandroid

Installing the hboot is just a fastboot flash (see adb and fastboot faq). Alpharev.nl also has instructions for changing hboot on their site.

Always check the md5 code of a hboot before flashing - a bad download is unlikely, but could be fatal to the phone.
Click to expand...
When I install dGB will it automatically change the MTD partition sizes so i have the 350MB /data and the others or do I have to manually change that by using the alpharev partition tables?.I want to change these sizes so I can take benefit of this ROM..

Also when you say install Hboot does it mean that I have to do that through the command prompt on the pc with the sdk folder downloaded?? Sorry for all the queries..just want it go right..
 
It won't automatically change the mtd or hboot you need to do this manually. Use fastboot for flashing the revised hboot which you can get from the dgb mini site but as hadron said check the md5 to ensure the download is right. Have fun oh and don't forget nandroid backup first ;-)
 
Paul8944 said:
It won't automatically change the mtd or hboot you need to do this manually. Use fastboot for flashing the revised hboot which you can get from the dgb mini site but as hadron said check the md5 to ensure the download is right. Have fun oh and don't forget nandroid backup first ;-)
Click to expand...
So there are 2 methods for this then.
I can either use the method for a custom MTD partition ([DEV][S-OFF] Custom MTD Partitions (resize data, system, and cache) - xda-developers I have to specify individual sizes in the .txt and follow the steps for CWM(I have CWM recovery) or I can flash the dGB Hboot through fastboot using my PC(I see a MD5 value but have no idea what thats supposed to mean)

Here are the steps Ill do(I am S-Off now)(
*Reboot into recovery take a Nandroid backup and wipe all system data and cache
*reboot to fastboot and flash the dGB Hboot via command prompt
*Reboot to recovery and flash the ROM
*Do all the wipes and reboot phone.

Is there anything I am missing? There is a mention of patching some values to the recovery and ROM in the custom MTD method.. Would I have to do that here?

Thanks
 
Yes there are two methods, but i have always used the hboot, (didnt fancy getting caught up with custom MTD's)
as for the MD5, you use this to check you dont have a corrupt download, if you go to the all things root sticky in the useful software / downloads section there is an md5 checker.
if you run this you can check that your download is not corrupt.

your steps seem correct but just to make sure here is how i understand it.

always take a nandroid of the current rom you are running as if this goes qrong you can always re-flash the stock hboot and flash the nandroid to get your phone working again.

1). do all the wipes and flash dgb rom.
2). boot into recovery and take a nandroid.
3). boot into fastboot and flash the dgb hboot, you should notice the top pink lettering change to su-dgb 60 / 65 or something similar, you may need to reboot the bootloader via fastboot to get the change to show.
4). reboot to recovery and either reflash the rom or run the nandroid (dgb one)

if you are flashing the hboot i would not worry about the MTD stuff it will only confuse you, (as it did me)

hope this helps and enjoy
 
Yes, I would install the ROM first, then nandroid, fastboot flash the hboot, restore nandroid. That way you change one thing at a time - first ROM, then hboot - rather than both at once.

Remember that once you flash the dGB hboot you cannot run any other ROM without changing hboot first (as no other ROM will fit). That includes nandroid restore - only a nandroid of dGB will work. That's another reason to do the ROM install first, check that is working, then change hboot.
 
Paul8944 said:
Yes there are two methods, but i have always used the hboot, (didnt fancy getting caught up with custom MTD's)
as for the MD5, you use this to check you dont have a corrupt download, if you go to the all things root sticky in the useful software / downloads section there is an md5 checker.
if you run this you can check that your download is not corrupt.

your steps seem correct but just to make sure here is how i understand it.

always take a nandroid of the current rom you are running as if this goes qrong you can always re-flash the stock hboot and flash the nandroid to get your phone working again.

1). do all the wipes and flash dgb rom.
2). boot into recovery and take a nandroid.
3). boot into fastboot and flash the dgb hboot, you should notice the top pink lettering change to su-dgb 60 / 65 or something similar, you may need to reboot the bootloader via fastboot to get the change to show.
4). reboot to recovery and either reflash the rom or run the nandroid (dgb one)

if you are flashing the hboot i would not worry about the MTD stuff it will only confuse you, (as it did me)

hope this helps and enjoy
Click to expand...
thanks..all worked fine with the flash and hboot...now to experiment..
 
so I'm back as well. I strayed to the dark side and tried Evervold's Jelly Bean build. It was really good considering that the Desire is 2 years old now. I created a Ext3 partition for space but how do I get rid of it now I'm back on dGB. I've tried through 4Ext and formatting in windows but I still seem to be missing space on my SD card. Windows disk management shows 7.4GB which is about right for a 8GB card. I had a 1Gb Ext3 partition during my JB time. But 'My Computer' shows 6.39Gb which is more like my 8Gb card with a 1Gb Ext3 partition. I've tried formatting in Windows but because it only sees the the fat32 partition formatting only formats that partition leaving me still at 6.39Gb. I tried to remove the partition in 4Ext but I must have done something wrong or can't see the wood for the trees. Seemed easy to create the partition but hard to get rid of it.
 
You must log in or register to reply here.
Back
Top Bottom