Flashing new hboot without losing data? - Desire Q&A, Help & Troubleshooting

Hello
I'm running quite low on space on my Desire and I would like to get the CM7r2 hboot, but I can't seem to find any posts saying if it's safe to flash a new hboot without losing data?

Depends what ROM you're using, and whether it supports the hboot.

This might help:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything and restore.
This info was taken from AlphaRev's homepage:
alpharev.nl
Note, however, that AlphaRev's hboot utility has been deprecated and replaced by Revolutionary:
revolutionary.io

Related

[Q] insertcoin data plus V3 help

i have installed insertcoin dataplus v3 with partition of fat32 =6.40gb
and ext3=1gb ...still the internal memory appears low all the time ...can any1 help me with this .....
Thanx
Are you S-off? Did you flashed the CM7 HBoot partition table?
YES M S-OFF ..... I DIDNT FLASH CM7 HBoot partition table ...WHAT IS IT ???
Next time READ!!!
from the Insertcoin data++ thread:
1st things 1st, you need to flash Bravo CM7 Hboot. either from fastboot or from hboot.- goto alpharev.nl site - is there together with all the info how to flash it
Click to expand...
Click to collapse
From alpharev.nl (here you can find also the required files).
If you are already S-OFF, you can get our newest patched HBOOTs from here. (without going through the entire procedure again).
Please read the entire table and pick the partition table with the correct sizes for your ROM. One easy way to switch partition tables, is to nandroid backup,
and verify that the sizes of your backup are indeed the ones listed in the table (or smaller), and restore after flashing hboot.
1) Nandroid backup in recovery.
1a) Download This file.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything and restore.
Click to expand...
Click to collapse
More detailed instructions here:
http://forum.xda-developers.com/showpost.php?p=12699557&postcount=8
thanx davebugyi
gawwd .....i still cant get it still didnt understand the procedure wanted to use data++
1.Download the .img file from Alpharev's site. The BRAVO_CM7 one.
2. Download android SDK from official site, and run SDK Manager. When it is running, then install the platform-tools (revision 3 ATM), too.
3. Copy the CM7 file (.img) you downloaded into the android SDK folder, where fastboot.exe is located.
4. Reboot your phone into fastboot (holding down BACK+POWER keys when the phone is switched off) - it should show FASTBOOT USB.
4a. Make sure you have the USB drivers installed (for me HTC sync is not needed, i used the UNREVOKED USB drivers instead)
5. Fastboot flash. navigate to your android SDK directory in Command Promt (CMD.EXE) then run these commands:
a, fastboot flash hboot bravo_alphaspl.img (or whatever is the name of the file)
b, fastboot reboot-bootloader
c, fastboot erase cache
6. You have now the Partition table.
7. Just in case, go to the recovery, wipe EVERYTHING and Re-flash the ROM.
Alternative solution here: Did not try it myself, so don't ask, how to
http://forum.xda-developers.com/showthread.php?t=794638
finally did it .....
thanx alot davebugyi

[Q] Flashing Oxygen Partition Table CID error

Hi all, my phone stats at present:
HTC Desire - originally on O2.
Rooted and S-off'd
Running Oxygen 2.1.6
I'm trying to flash this partition table:
Bravo Oxygen r2.
I have renamed PB99IMG_oxygenr2.zip to pb99img.zip and put it on the root of my SD.
When I boot into fastboot I get:
CID Incorrect
Update Fail
Do you want to reboot device?
Click to expand...
Click to collapse
Now I'm not adverse to a bit of dev work - I have the and. SDK up and running.
Code:
fastboot getvar all
shows:
(bootloader) cidnum: O2___001
I gather this is the problem.
How do I change the CID? Is there a quick and easy command line or shell fix?
Cheers
Flashing hboot via pb99img.zip does not work very often. Better do it with fastboot:
Code:
fastboot flash hboot C:\bravo_alphaspl-oxygenr2.img
fastboot reboot-bootloader
fastboot erase cache
Comment is for the case, your hboot.img is stored on partition C and you used the oxygen r2 hboot from http://alpharev.nl
MAKE SURE YOU CHECK MD5SUM BEFORE FLASHING HBOOT!!!
To avoid cid error, you need to create goldcard and put it in your desire:
http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
Exactly, if you are comfy with the fastboot/adb there is no reason to use PB99IMG.
MatDrOiD - Danke!

S-ON after Revolutionary S-OFF possible? [SOLVED]

I'm looking for a way to remove Revolutionary S-OFF...
I tried flashing several RUUs with different HBOOT versions but Revolutionary HBOOT is very persistant
I'd would love to return to HBOOT 0.93 since I have to return my device due to a possible hardware error.
anyone have a suggestion? tnx
Only to use RUU
name.vic said:
Only to use RUU
Click to expand...
Click to collapse
not sure what you mean exactly, but just flashing a stock RUU with NOT remove revolutionary HBOOT. I'll explain in next post.
SOLVED: just got THE answer from someone at #revolutionary
1. what: downgrade HBOOT using AlphaRev
how: go to http://alpharev.nl/, download (and always MD5-) check "bravo_downgrade.img", flash using fastboot
2. what: flash stock RUU
how:go to http://shipped-roms.com/index.php?category=android&model=Bravo and download RUU for your device and run the executable
(I chose "RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe " since it turned out to contain HBOOT 0.93 which I wanted)
3. done
Thank you thank you thank you thank you thank you !
Puff, i got a good scare after upgrading to GB.
I found out that after upgrading I cannot simply RRU my way back, installed revolutionary then I wanted to bring my Desire to service [reboots] and wanted to get rid of s-off and revolutionary hboot to make it "stock".
Once again, thanks to this great community !
hi.
Hope someone still watching these posts.
I tried your solution.
Flashed the hboot and it switched from Revolutionary to alpharev.
Then i flashed the phone with stock ruu RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
But still no luck.
The methods iv tried is:
All through command in windows, :
adb devices
adb reboot bootloader
fastboot devices
fastboot flash hboot bravo.img <-- i renamed the file i took from the ruu im using.
flash hboot - reboot to android os - stock ruu flash = no stock hboot
flash hboot 4 times - reboot to android os - stock ruu flash = no stock hboot
flashed hboot - still in hboot i ran stock ruu = no stock hboot.
am i missing any step?
My phone/hboot is:
Swedish unlocked HTC Desire.
Bravo pvt4 ship s-off
hboot 6.93.1002
radio 5.11.05.27
Why are you using adb? You must be on the fastboot screen not hboot screen
Sent from my HTC Desire using XDA App
rootSU said:
Why are you using adb? You must be on the fastboot screen not hboot screen
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hi and ty for your reply.
I think i have tried it in fastboot to.
Or on my phone it says fastboot usb marked in red collor.
Is that right or wrong?
could you give me a step by step?
I have the revolutionary drivers and uninstalled htc sync alredy.
The things iv tried so far is this list of commands in order:
cd c:\desire <--- where i have the files
adb devices
adb reboot bootloader
fastboot devices
fastboot flash hboot bravo.img
rootSU said:
Why are you using adb? You must be on the fastboot screen not hboot screen
Click to expand...
Click to collapse
how do you flash files in fastboot,if not with adb to my knowledge he was in the fastboot screen(when you adb reboot bootloader thats where it takes you)
we need more detail in step #2. after getting an "ok" flashing the downgrader image in step one,do you reboot to the OS,then run the executable from there? or do you run it while still in fastboot?
ive been helping him on another forum,and from what he describes,it looks like hes followed DXsl's steps,but it still hasnt worked.
thanks for any info
After flashing the downgrader, you cannot boot any rom, because the downgrader deletes all internal partitions. So after flashing the hboot downgrader successfully, just enter this
Code:
fastboot reboot-bootloader
When done, flash ruu. At the end you are on stock rom with stock hboot (s-on).
A little note at the end: If your phone is in fastmode mode, you cannot use adb (commands). If your phone is in hboot mode, you cannot use fastboot (commands). And fastboot can only be used if one is s-off. I know you are in this state, but this information is for the future.
MatDrOiD said:
After flashing the downgrader, you cannot boot any rom, because the downgrader deletes all internal partitions. So after flashing the hboot downgrader successfully, just enter this
Code:
fastboot reboot-bootloader
When done, flash ruu. At the end you are on stock rom with stock hboot (s-on).
A little note at the end: If your phone is in fastmode mode, you cannot use adb (commands). If your phone is in hboot mode, you cannot use fastboot (commands). And fastboot can only be used if one is s-off. I know you are in this state, but this information is for the future.
Click to expand...
Click to collapse
i see what you are getting at now. while you are in fastboot mode,you technically are using fastboot commands,not adb commands. kind of splitting hairs,but correct. when folks are in the CMD window and entering commands to the phone they broadly describe the experience as "using ADB".
while an engineering or patched hboot provides alot more functionality,there are limited commands for s-on in fastboot mode.
thanks for the info
This isn't working. RUU managed to flash HBOOT, Radio, Signature, but after that it gives error 140 and ends.
---------- Post added at 01:50 PM ---------- Previous post was at 01:29 PM ----------
So I tried to install it manually and the only component that failed to flash was system. Here is log:
Code:
********************************
###Calling fastboot with: flash system D:\Programy\Android\system\PB99IMG_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed\system.img###
sending 'system' (254219 KB)... FAILED (remote: data length is too large)
finished. total time: 0.004s
********************************
Is that with the downgrader flashed?
Sent from my HTC Desire using XDA App
Yes.
10char
How much total space do you have on system? (try a df -f on a terminal emulator)
Dunno, but I wiped entire phone and GB RUU runs fine.
Terepin said:
Dunno, but I wiped entire phone and GB RUU runs fine.
Click to expand...
Click to collapse
I think your partition size is somehow smaller than it should be. Did you flash the stock HBOOT after flashing downgrade HBOOT?
PS: also use command "fastboot erase cache" after flashing HBOOT and "fastboot reboot bootloader" too. Just to be sure
theGanymedes said:
I Did you flash the stock HBOOT after flashing downgrade HBOOT?
Click to expand...
Click to collapse
Nooo..If after the downgrader u flash the stock one, u are locked s-off again (downgrade protection)
the downgrader is already stock, and because this one has no protection, the ruu overwrite it before to flash the system partition
andQlimax said:
Nooo..If after the downgrader u flash the stock one, u are locked s-off again (downgrade protection)
the downgrader is already stock, and because this one has no protection, the ruu overwrite it before to flash the system partition
Click to expand...
Click to collapse
With custom MTD, we had to format system, cache and data so maybe it would be best practice to do that after flashing the downgrader if you still have recovery (i.e havent tried to run an RUU over CM7 hboot)
yes, u can't flash an ruu over the cm7 hboot, but u can over the downgrader
this damn downgrader is the stock hboot (with stock partitions size)with no protection..all the other hboots on alpharev have the downgrade protection (so an ruu can't overwrite it)
so for example, if u have the cm7 hboot, u dont need to flash the stock hboot and then the downgrader hboot (or viceversa)..only the downgrader is enough..the downgrader is an hboot with stock partition size
in addition, the first thing that the ruu does is to flash the hboot with stock size (only after the ruu flash the system)..but of course, it will successfully write the hboot only if u have the downgrader one

cant boot into rom after upgrate to CM7r2 hboot

i was on stock hboot 0.93.001, s-off with Runnymede rom and i wanted to install CM7r2 hboot
i put the file PB99IMG_cm7r2 file on root sd and i rename it to PB99IMG
i update it like it says on alpharev.nl but now i cant boot into the rom
i restore the nadroid but nothing.... i also flash again the Runnymede but nothing again
bootloader now is this
Uploaded with ImageShack.us
desire stack here
please some help
Uploaded with ImageShack.us
Because your nandroid is setup to work on a Stock Hboot is the reason it's not working. The system partition space is not enough for your nandbackup file.
did you wipe cache via fastboot after rebooting of bootloader?
fastboot erase cache
you need to wipe/format all partitions including dalvik except sdcard
then flash it again...
Nandroid back up will be not working because you changed system partition size as backup from stock hboot is way too big to fit onto cm7/r2 system partition
kotag82 said:
did you wipe cache via fastboot after rebooting of bootloader?
fastboot erase cache
you need to wipe/format all partitions including dalvik except sdcard
then flash it again...
Nandroid back up will be not working because you changed system partition size as backup from stock hboot is way too big to fit onto cm7/r2 system partition
Click to expand...
Click to collapse
ok i didnt the "fastboot erase cache" cause i cant find the erase cache under the fastboot menu
where is this "fastboot erase cache"?
thank you for your quick answers
You have to type this command in CMD. For installing / using Fastboot / ADB, check my guide.
MatDrOiD said:
You have to type this command in CMD. For installing / using Fastboot / ADB, check my guide.
Click to expand...
Click to collapse
trust me i did look your guide but i founded too much....
i was looking for easyest method to upgreat the hboot but now i will read your guide again ....i guess i have no choice
Easiest to flash things radio, recovery, bootloader or splash screen is IMHO Android Flasher:
http://forum.xda-developers.com/showthread.php?t=794638
EDIT: You use CM7r2-version of Runnymede, do you?
ok i did it more carefully and i flash the rom after upgrate ... so it booted ....
i just got scared i thought i broke it
thank you all

[Q] Boot loop and can't find appropriate boot.img

Hi
I've been given a One X (he bought an M8) and I thought I'd easily put on KK 4.4.4, but I have hit a brick wall.
It was running ViperX 2.6.0 with Hboot 0.95, and it's S-ON.
Well 4.4.4 needs a Hboot above 1.28, so the flashing failed.
So I did my homework and got the CID (it's HTC-023) to install the firmware so that I could update the Hboot via OTA.
So I installed the boot.img for the HTC-023 firmware and that (of course) was a an error as I didn't have a copy of the boot.img for the ViperX 2.6.0.
Then the firmware was a .rar file and didn't install anyrate.
So now it's in bootloop.
I have not been able to find a copy of ViperX 2.6.0 to extract the required boot.img
I've got TWRP with Sideloader installed, and ADB works fine.
So I am stuck (like my One X really) so any advice would be appreciated.
Thanks
Solution
I thought I should post the solution.
The essential problem was to get a Hboot 1.28 or higher so that a new version of Cyanogenmod could be installed.
On this page http://forum.xda-developers.com/showthread.php?t=1957376&page=189 is the following from ClydeB1
To flash you need to run the following commands: (It is advised to take a backup of your data and important files on your sd card)
1. Lock bootloader - fastboot oem lock
2. Boot to RUU mode - fastboot oem rebootRUU
3. Flash firmware - fastboot flash zip firmware.zip (if you get an error then rerun this command)
Note: The firmware will flash the new hboot, as well as a new stock boot.img and stock recovery.img.
To flash a custom rom you then need to do the following:
4. Unlock bootloader - fastboot flash unlocktoken Unlock_code.bin (you can use the same unlock_code file as you used previously, check your emails if you can't find it, or else reapply at htcdev.com)
5. Flash custom recovery - fastboot flash recovery nameofrecoveryfile.img
Note: If the unlock process wiped your sd card you may need to boot to recovery and mount usb storage to copy the rom file across again. If your phone won't boot into recovery then run command - fastboot erase cache and try again.
If you then wish to flash a JB custom rom:
6. Flash new boot.img from rom - fastboot flash boot boot.img
7. For good measure - fastboot erase cache
8. Boot to recovery and flash rom
I followed these steps exactly and it worked perfectly. I did need to use CWM as with TWRP the touch screen did not work.
and have more ease way to do this. You are with too low HBOOT and you can run RUU and then update the phone to latest JB because are you know witch HBoot you install to your phone

Categories

Resources