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

Root Changing hboot

C

cashmere_cat

Well-Known Member
It looks like I am going to need to change my hboot if I am going to give mildwild a fair try. Is there a particular one that most people use, that is versatile enough to use with the majority of roms? This doesn
 
Hboot and recovery are separate. You flash hboot using fastboot (Android Flasher being just a GUI for fastboot), and it doesn't matter what recovery you are using.

I'm currently using 4EXT touch with the 65MB dGB hboot and it's just fine.

However, 65MB is definitely not going to work with MildWild. If you want something flexible, Alpharev's CM7r2 is big enough for any AOSP ROM (including MIUI ROMs), so should fit the bill.
 
Command line. hmm. Is this not valid? (from the alpharev site, where the hboot tables are downloadable from)

" download the corresponding PB99IMG zipfile, put it on your sdcard, and rename it to PB99IMG.zip. Then start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC."
 
Its "valid", yes. But *if* you wanted my advice (for whatever that would be worth), I would recommend command line.
 
Yup, of course I want your advice. :)
Was just hoping there was a way around it...im not much of a command line kinda gal..
But I will read through the Greek tonight and see what I can decipher. ty.
 
cashmere_cat said:
Yup, of course I want your advice. :)
Was just hoping there was a way around it...im not much of a command line kinda gal..
But I will read through the Greek tonight and see what I can decipher. ty.
Click to expand...


I know why you would feel like that, but its really easy actually. And you learn something, which can come in useful as fastboot can get you out of scrapes.... To have it set up and to have used it before comes in beneficial at times

imagine your hboot is called hboot.img and its on your c drive...

The command then is literally:
fastboot flash hboot c:\hboot.img

You just do that from a windows command prompt. Of course you need to do the fastboot set up first....
 
I tried the way of renaming it and moving the file to the SD card, and for me it didn't work and nor did Android Flasher.

In the end, I read the FAQ a few times, built up the courage and used command line, and it was done in seconds, don't know why it took me so long to do
 
I think I have my computer set up for this now, but here's where the guide gets a bit fuzzy for me...
Here's my thoughts on where to go next...
Find the hboot table from alpharev, save it to my C drive.
boot into Fastboot.
Connect phone to PC (or connect first, then into fastboot? does it matter?)
Open command prompt, run adb shell.
then type: fastboot flash hboot c:\hboot.img

am i on track?

I guess the phone will do some 'stuff'... and reboot... and voila - done? :confused::confused:
 
cashmere_cat said:
I think I have my computer set up for this now, but here's where the guide gets a bit fuzzy for me...
Here's my thoughts on where to go next...
Find the hboot table from alpharev, save it to my C drive.
boot into Fastboot.
Connect phone to PC (or connect first, then into fastboot? does it matter?)
Open command prompt, run adb shell.
then type: fastboot flash hboot c:\hboot.img

am i on track?

I guess the phone will do some 'stuff'... and reboot... and voila - done? :confused::confused:
Click to expand...

You just boot the phone to fastboot and connect usb. The screen will then change to fastboot usb.

Then you type what I said in command prompt. Notice how I didn't say anything about adb? That's because adb is nothing to do with fastboot at all. At all, at all. The only similarity is that its command.line. you cannot do anything for fastboot in adb or vice versa.
 
cashmere_cat said:
" 'fastboot' is not recognized as an internal or external command, operable program or batch file" :(
Click to expand...

That means either there was an error in the line you put into the environment variables window in windows, or that the file location of fastboot does not match the line that you put into the environment variables window.
 
C:\Program Files\Common Files...<snip>...System\;C:\android-sdk-windows\tools

this ^^ is whats in environment variables -- seems fine to me.
And not sure I understand "file location of fastboot does not match the line that you put into the environment variables window."
arghh! you sure android flasher wasnt designed for someone dense like me?? lol
 
Just wanted to say that I've been using MildWild 3.2 Oxygen with Stock HBoot A2SD and Dalvik moved to SD without any issues.)
 
cashmere_cat said:
wait - making progress. maybe.
' error: cannot load c:bravo_alphaspl-cm7r2.img'
Click to expand...

Try "C:\bravo_" etc

Make sure you've taken a nandroid first.

Once you've got it going, the syntax of fastboot commands is pretty simple. Basically it's:

fastboot operation target file

where the last argument is only used by some operations (typically when flashing a file) . So for example:

fastboot erase cache
fastboot format system
fastboot flash recovery recovery.img

Also "fastboot devices" is a good one, as that let's you check that the computer detects your phone (useful for trouble shooting - I generally do it before other fastboot commands).
 
Bradden said:
Just wanted to say that I've been using MildWild 3.2 Oxygen with Stock HBoot A2SD and Dalvik moved to SD without any issues.)
Click to expand...

how did you move the dalvik? I have S2E going, but it still seems to be taking up a fair chunk of /data
How many apps do you have installed?
 
hmm. I tried with the new syntax hadron suggested..
got:
sending 'hboot'(512k)....ok [0.090s]
writing 'hboot'....ok [0.160s]
finished. total time 0.265s

thats it?? can't be......
 
I would consider myself fairly intelligent... but somedays this smartphone makes me feel like a dolt lol. That was so easy, once it happened. Now...what else can I flash?? haha, noooo nooo... no more flashing!!
 
Somethings with android are very intuitive. Other things, not so much. There's no substitute for actually doing the things you read about.

Hopefully now, you will have fewer space issues now :)
 
cashmere_cat said:
hmm. I tried with the new syntax hadron suggested..
got:
sending 'hboot'(512k)....ok [0.090s]
writing 'hboot'....ok [0.160s]
finished. total time 0.265s

thats it?? can't be......
Click to expand...
It's amazing isn't it :)

That's the thing I like most about flashing hboot - no nervously watching it happen, it's over the moment you start.
 
Does hboot flash wipe the ROM? What about the recovery? Will I need to flash Recovery and ROM after hboot flash. Sorry if this is a dumb question but am asking as I am thinking of hboot flash as changing partition in SD card. Which obviously wipes everything in it.

Also is there any other img files available apart from the Alphrev table. I was thinking of something like : System: 100, Cache: 45, Data: rest.

I think I am finally going to settle down with dGB and this will be my last few flashing. Then I am going to pass the phone on to my wife and move on to Samsung Galaxy S2.
 
You must log in or register to reply here.
Back
Top Bottom