Develop Bugs

[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

[EXPLANATION] Rom Update Utility

Hello guys,
in this thread i will explain, how a RUU (Rom Update Utility) works.
What does a RUU contain?
Yeah, really important for some guys. A normal RUU contains following files:
- AdbWinApi.dll (for use of adb.exe)
- adb.exe (for adb commands)
- ARUGlobal.dll (for the executable file)
- ARUWizard.exe (the RUU executable)
- ARUWizard.ini (basic configuration for the RUU)
- some language files for the RUU
- some bmp-files for the recovery fail (solutions)
- one PHONE.bmp shown in the RUU
- fastboot.exe (for fastboot commands)
- rom.zip (a signed HTC Rom)
- ReadMe-files in different languages
- some other unimportant files
Normaly the RUU is provided in a executable. This exe-file is a compressed, self-extracting InstallShield archive. If you start the file, the InstallShieldWizard extract the contents in the temp-folder of your current User and starts the ARUWizard.exe which is the "real" RUU.
Click to expand...
Click to collapse
What does the RUU while updateing the phone?
Well, its much easier as you think. First the RUU check which version is installed in phone. This is basicly done with following adb-command:
Code:
adb -s {phones adb name} shell getprop ro.build.description
The return is the version number of the phone.
If the phone is started in fastboot mode the RUU run following command and become the same return like with the adb-command:
Code:
fastboot -s {phones fastboot name} getvar version-main
If the version of the RUU rom.zip is higher as the version of the Rom installed on the phone, the RUU give you the option to update your phone.
Click to expand...
Click to collapse
The Update process
Some of you maybe think now, the RUU begins to do magic things. But the next thing is very easy. The RUU restarts the phone into fastboot RUU mode:
Code:
adb reboot-bootloader
fastboot oem rebootRUU
The next command is easily to send the rom.zip to the phones fastboot:
Code:
fastboot update {full path to the update package (rom.zip)}
The rest will do by phones fastboot, not by the RUU self. The RUU return and give out the actual state of the installation only, and gives you the error message if anything go false, or the message, that the phone is updated successfully. After this the RUU will restart the phone.
Click to expand...
Click to collapse
That is basicly what the RUU did, not more

Thx especially for the adb/fastboot commands.
Now everyone can see why modifying the ruu will not give us full access

Yeah, thats the BIG reason why i created this thread

ONeill123 said:
Code:
adb -s {phones adb name} shell getprop ro.build.description
Click to expand...
Click to collapse
does that mean i can change my version in build.prop ro.build.description and we can reinstall a rom from other country ????
ONeill123 said:
CODE]adb reboot-bootloader
fastboot oem rebootRUU[/CODE]
The next command is easily to send the rom.zip to the phones fastboot:
Code:
Code:
fastboot update {full path to the update package (rom.zip)}
The rest will do by phones fastboot, not by the RUU self. The RUU return and give out the actual state of the installation only, and gives you the error message if anything go false, or the message, that the phone is updated successfully. After this the RUU will restart the phone.
Click to expand...
Click to collapse
in ths way giving the comands manually can we falsh ny rom.zip ?? is it possible.? my wfs is with my bro he is gone out of town.. so cant try it.. will surely do it when he gets back.. but still very exited to know. is it possible?

You misunderstood all i think
To the ro.build.description:
The RUU check this only to get the current version and prevent a unuseful restart of phone and to give you the information. Not more.
And you can change the build.prop only with unlocked BL or s-off, and then you can install the system.img of another country self without a RUU.
To the rom.zip:
The RUU sent the rom.zip to fastboot only. The signature check do the fastboot/bootloader of the phone. So you can change the rom.zip, but the bootloader will say "signature error" or something else.

ONeill123 said:
You misunderstood all i think
To the ro.build.description:
The RUU check this only to get the current version and prevent a unuseful restart of phone and to give you the information. Not more.
And you can change the build.prop only with unlocked BL or s-off, and then you can install the system.img of another country self without a RUU.
To the rom.zip:
The RUU sent the rom.zip to fastboot only. The signature check do the fastboot/bootloader of the phone. So you can change the rom.zip, but the bootloader will say "signature error" or something else.
Click to expand...
Click to collapse
hehehe actually i have radio probs.. with my wifi n data pack.. so thought that i might be able to update the radio like this hehehe nvm ty oneil

[Q] cant update firmware 3.28.401.6 help

cant update firmware 3.28.401.6
cant seem to figure it out what am i doing wrong i have htc m8 S-on cant get s-off everytime i try it says htc patched it using firewater. so i read up as much as i could downloaded the file 3.28.401.6 try to install but i get an error which i found out means my cid an mid dont match my current CID IS TMOB010 AND MY MD IS 0P6B13000 im running on ARHD 11.2 and i need the firmware installed before i jump to arhd 20.1

xjaycjr27x said:
cant update firmware 3.28.401.6
cant seem to figure it out what am i doing wrong i have htc m8 S-on cant get s-off everytime i try it says htc patched it using firewater. so i read up as much as i could downloaded the file 3.28.401.6 try to install but i get an error which i found out means my cid an mid dont match my current CID IS TMOB010 AND MY MD IS 0P6B13000 im running on ARHD 11.2 and i need the firmware installed before i jump to arhd 20.1
Click to expand...
Click to collapse
CID/MID is wrong you can clearly see that, so why ask Get S-OFF with Sunshine S-OFF $25 for it, then you can change your cid/mid as you need(Convert device to and from...)

xjaycjr27x said:
cant update firmware 3.28.401.6
cant seem to figure it out what am i doing wrong i have htc m8 S-on cant get s-off everytime i try it says htc patched it using firewater. so i read up as much as i could downloaded the file 3.28.401.6 try to install but i get an error which i found out means my cid an mid dont match my current CID IS TMOB010 AND MY MD IS 0P6B13000 im running on ARHD 11.2 and i need the firmware installed before i jump to arhd 20.1
Click to expand...
Click to collapse
Get SunShine s-off. It costs $25, but it's worth it. After that you can go SuperCID.
Here are the steps to go SuperCID so that you can use firmware from any carrier.
1. Have adb and fastboot set up. There are guides all over xda and google
2. Connect phone to PC and open terminal
3. Type "adb devices" to make sure phone is connected to PC
4. Type "adb reboot bootloader"
5. Once in fastboot type "fastboot devices" to make sure fastboot sees your device
6. Type "fastboot oem rebootRUU"
7. Once in black screen that says HTC you are in ruu mode
8. Type "fastboot oem writecid 11111111"
9. After a successful cid overwrite type "fastboot reboot-bootloader"
10. Profit! You are now supercid!!

xunholyx said:
Get SunShine s-off. It costs $25, but it's worth it. After that you can go SuperCID.
Here are the steps to go SuperCID so that you can use firmware from any carrier.
1. Have adb and fastboot set up. There are guides all over xda and google
2. Connect phone to PC and open terminal
3. Type "adb devices" to make sure phone is connected to PC
4. Type "adb reboot bootloader"
5. Once in fastboot type "fastboot devices" to make sure fastboot sees your device
6. Type "fastboot oem rebootRUU"
7. Once in black screen that says HTC you are in ruu mode
8. Type "fastboot oem writecid 11111111"
9. After a successful cid overwrite type "fastboot reboot-bootloader"
10. Profit! You are now supercid!!
Click to expand...
Click to collapse
thank you

xunholyx said:
[...]
6. Type "fastboot oem rebootRUU"
7. Once in black screen that says HTC you are in ruu mode
8. Type "fastboot oem writecid 11111111"
9. After a successful cid overwrite type "fastboot reboot-bootloader"
10. Profit! You are now supercid!!
Click to expand...
Click to collapse
Why go into RUU mode to change to supercid?

BerndM14 said:
Why go into RUU mode to change to supercid?
Click to expand...
Click to collapse
It is the method I know. But if you know another way, please share! I always like to learn new stuff.

xunholyx said:
It is the method I know. But if you know another way, please share! I always like to learn new stuff.
Click to expand...
Click to collapse
No method, you just don't have to go into RUU mode for it. In fastboot/bootloader you can just use the command fastboot oem writecid 11111111
No need to mess around with RUU mode. Especially if that guy doesn't even know how to read the problem he has, it's a disaster in the making for him...

BerndM14 said:
No method, you just don't have to go into RUU mode for it. In fastboot/bootloader you can just use the command fastboot oem writecid 11111111
No need to mess around with RUU mode. Especially if that guy doesn't even know how to read the problem he has, it's a disaster in the making for him...
Click to expand...
Click to collapse
Nice to know. Thank you. This was the method I was taught though. Good to know RUU isn't necessary.

[Q]Installed Google Play Edition from RUU, now stuck at Fastboot?

Hi,
So after fighting for hours, I managed to successfully use fastboot flash zip command to RUU the google play edition rom to my phone. However, the tutorial I followed didn't say I needed to match my CID and MID, so now I am stuck at the GPE fastboot bootloader. I can flash a custom recovery (I put TWRP on after the RUU was finished). However, since my phone is stuck at fastboot, I can't transfer any files to it using adb.
What I have: Fastboot, and TWRP recovery. Booting normally brings up Fastboot. Booting to recovery brings up TWRP.
My goal: Change my CID and MID so I can properly RUU the GPE rom to my phone. I think I can change the CID from fastboot but I don't think I can change MID from there.
What do you think? Am I going in the right direction? Did I make a wrong assumption?

In fastboot, you should be able to change you CID running this command:
Code:
fastboot oem writecid GOOGL001
If your MID doesn't start with 0P6B, you need to open the RUU file with a zip explorer program and modify the android-info.txt file inside and add your MID to the list. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2708589

hellhawk741 said:
In fastboot, you should be able to change you CID running this command:
Code:
fastboot oem writecid GOOGL001
If your MID doesn't start with 0P6B, you need to open the RUU file with a zip explorer program and modify the android-info.txt file inside and add your MID to the list. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
Well I changed my CID and MID according to the thread (I edited the android-info.txt). However when I ran fastboot flash zip it failed with
FAILED (remote: not allowed)
Any ideas? It worked before, which confuses me as to why it's not working now.
EDIT: Nevermind I am an idiot. FAILED (remote: not allowed) means you need to reboot into RUU mode by using fastboot oem rebootRUU. However now I am back to where I started.
I successfully RUUed the Google Play rom, but now my phone only boots to the bootloader and fastboot.

I'm confused by flashing the RUU, if you have an ext SD card you can copy the image there rename it, boot and it will install itself. There is a rooted image available in the Android Development forum by GrafxNYC. I followed his instructions there and it worked perfectly.

Assuming the RUU file is not an exe file, move it to your SD card and rename it to match your MID exactly and reboot into bootloader. It should flash without a problem.

Ive been wrestling with this since last Saturday but I've finally got the GPE rom working. I couldn't tell you what I did, because I've gotten sidetracked and backtracked a bazillion times. I need to make a new thread though, the GPE rom is *extremely* unstable and crashes very frequently