I bought a desire (used) and upgraded it from official Froyo to official Gingerbread via RUU, now i decided to install any custom rom on it, for this i downloaded all necessary files (revolutionary etc.), following is the information of my desire;
BRAVO PVT4 SHIP S-OFF
HBOOT-1.02.0001
MICROP-051D
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
JULY 22 2011, 16:19:16
I was surprised to see it was already S-OFF, my questions are;
1) why is it already S-OFF? (it was not rooted before upgrade)
2) Tell me the steps for gaining root or installing custom recovery? (in my case where i am already s-off)
3) Do i have to run revolutionary or just start by installing amon-ra recovery by android-win-tools method?
I am new to this thing and never rooted or installed custom rom before, but went through a lot of threads in this forum and did not find any clue relating to my case.
Thanks in advance.
Ashar said:
I bought a desire (used) and upgraded it from official Froyo to official Gingerbread via RUU, now i decided to install any custom rom on it, for this i downloaded all necessary files (revolutionary etc.), following is the information of my desire;
BRAVO PVT4 SHIP S-OFF
HBOOT-1.02.0001
MICROP-051D
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
JULY 22 2011, 16:19:16
I was surprised to see it was already S-OFF, my questions are;
1) why is it already S-OFF? (it was not rooted before upgrade)
2) Tell me the steps for gaining root or installing custom recovery? (in my case where i am already s-off)
3) Do i have to run revolutionary or just start by installing amon-ra recovery by android-win-tools method?
I am new to this thing and never rooted or installed custom rom before, but went through a lot of threads in this forum and did not find any clue relating to my case.
Thanks in advance.
Click to expand...
Click to collapse
I don't think this s-off is as "thorough" as revolutionary. I tried to get someone else who had this but his English was not too good so didn't get very far. It would be nice to know the limitations of this factory S-off though.
Have you got a recovery in mind? As you are PVT4, you need to be aware that you cannot use clockworkmod 2.5.0.7 if you are erase size 40,000. Which means you need to use a newer CWM (Bah) or AmonRA.
To find out, download a terminal emulator from the market:
Code:
cat /proc/mtd
(note space between cat and /)
Then you need to fastboot flash recovery. Follow link in my signature for an adb and fastboot faq. Also be aware adb and fastboot are different things. adb has nothing to do with this.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
rootSU said:
I don't think this s-off is as "thorough" as revolutionary. I tried to get someone else who had this but his English was not too good so didn't get very far. It would be nice to know the limitations of this factory S-off though.
Have you got a recovery in mind? As you are PVT4, you need to be aware that you cannot use clockworkmod 2.5.0.7 if you are erase size 40,000. Which means you need to use a newer CWM (Bah) or AmonRA.
To find out, download a terminal emulator from the market:
Code:
cat /proc/mtd
(note space between cat and /)
Then you need to fastboot flash recovery. Follow link in my signature for an adb and fastboot faq. Also be aware adb and fastboot are different things. adb has nothing to do with this.
Click to expand...
Click to collapse
Thanks for your quick reply. Please note some of results for MTD and ROOT Check.
$ export PATH=/data/local/bin:$PATH
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00040000 "misc"
mtd1: 00480000 00040000 "recovery"
mtd2: 00340000 00040000 "boot"
mtd3: 0fa00000 00040000 "system"
mtd4: 02800000 00040000 "cache"
mtd5: 096c0000 00040000 "userdata"
$
It means my erase size is 40,000 and i need latest CWM, or AmonRA recovery?
Root Checker Advanced Root Access Results
Superuser.apk - com.noshufou.android.su - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your HTC Desire device by Root Checker version 3.7 from joeykrim in the Android Market - http://goo.gl/GgWae
May be you can extract limitations of this factory s-off from above technical data.
Now may i do the following?
1) run revolutionary and do not install recovery from therein.
2) flash fastboot recovery by android-win-tools method.
3) flash su-2.3.6.3-efgh-signed from within custom recovery
4) flash any custom rom.
or may i skip step 1 and follow the rest?
thanks in advance
rootSU said:
I don't think this s-off is as "thorough" as revolutionary. I tried to get someone else who had this but his English was not too good so didn't get very far. It would be nice to know the limitations of this factory S-off though.
Click to expand...
Click to collapse
Well it is exactly, as s-off as if you did it using revolutionary. So the bootloader won't check signatures(which is the definition of s-off), but you won't be able to use fastboot commands, as those are not included in the stock hboot.
To be able to flash a recovery using "fastboot flash recovery" He must first flash a custom hboot with fastboot commands enabled. Do the following:
1. download this zip file: http://alpharev.nl/PB99IMG_stock.zip
2. Rename it to "PB99IMG.zip"(make sure it's not PB99IMG.zip.zip, as windows may hide the ending)
3. Place this file on the root of your sd-card.
4. Shut down your phone and boot up by holding "vol-down" and pressing power While keeping "vol-down" pressed until you enter hboot.
Your phone should now flash the image, and you should be able to flash a recovery using fastboot commands.
(This means you don't need to use revolutionary, but you cannot just flash cwm before doing the above steps either)
Thanks for the info, I wasn't aware of fastboot.
So the signature checking is also in nvram?
Sent from my HTC Desire using XDA App
mortenmhp said:
Well it is exactly, as s-off as if you did it using revolutionary. So the bootloader won't check signatures(which is the definition of s-off), but you won't be able to use fastboot commands, as those are not included in the stock hboot.
To be able to flash a recovery using "fastboot flash recovery" He must first flash a custom hboot with fastboot commands enabled. Do the following:
1. download this zip file: http://alpharev.nl/PB99IMG_stock.zip
2. Rename it to "PB99IMG.zip"(make sure it's not PB99IMG.zip.zip, as windows may hide the ending)
3. Place this file on the root of your sd-card.
4. Shut down your phone and boot up by holding "vol-down" and pressing power While keeping "vol-down" pressed until you enter hboot.
Your phone should now flash the image, and you should be able to flash a recovery using fastboot commands.
(This means you don't need to use revolutionary, but you cannot just flash cwm before doing the above steps either)
Click to expand...
Click to collapse
Thanks for your reply, please answer these questions ( i am so careful because i m doing it for the first time)
1) what will be my hboot version after flashing PB99IMG.zip? (right now my hboot is 1.02.0001 and i am on stock gingerbread 2.3.3)
2) if i just want to gain root access and dont want a custom rom, do i need to flash hboot and recovery or just flash su-2.3.6.3-efgh-signed?
(i just want to uninstall adobe flash player 10.1 and google maps 5.2 from system preinstalled in 2.3.3 to gain some space for installing latest versions 10.3 and gm 5.10)
thanks in advance
It'll be 6.093 or something. You can't flash su without flashing recovery. You can't flash recovery until you do PB99IMG.zip
Removing pre installed apps just makes space in system, which is not where you install apps so doing that alone will not give you more space.
Have a read of the root memory faq in my signature
Sent from my HTC Desire using XDA App
rootSU said:
So the signature checking is also in nvram?
Click to expand...
Click to collapse
Well not exactly, but the stock hboot allows for skipping signature check if the flag in nvram is set AFAIK.
rootSU said:
It'll be 6.093 or something. You can't flash su without flashing recovery. You can't flash recovery until you do PB99IMG.zip
Removing pre installed apps just makes space in system, which is not where you install apps so doing that alone will not give you more space.
Have a read of the root memory faq in my signature
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
After doing PB99IMG.zip my phone info is as follows;
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002 (it was 1.02.0001 before)
MICROP-051d
RADIO-5.17.05.23
Aug 10 2010, 15:52:18 (it was July 22 2011, 16:19:16 before)
Now please recommed me the recovery (CWM or AmonRA) and a custom rom (fast, stable, more user space, more battery) to flash, thanks again for your kind help and guidance
mortenmhp said:
Well not exactly, but the stock hboot allows for skipping signature check if the flag in nvram is set AFAIK.
Click to expand...
Click to collapse
Yes, alpharev hboots "ignore" the NVRAM flag. But I am unsure how these factory hboots with s-off work. I don't understand why they would implement an ignore via hboot, when they have the flag in NVRAM. I would expect them to turn the flag of at source instead of using the same work around as alpharev, which is what I am confused about.
Thats kind of why I wanted someone to investigate, but the fastboot commands make sense. I suppose the Nexus one haas embeded fastboot commands as it's a developer phone. Although, why HTC would release an S-OFF version of the desire but ommit fastboot is beyond me. I thought the whole reason they did this was due to petition pressure not to lock it down too much
Related
I want to flash userdata.img, system.img, recovery.img, boot.img files via ADB to my Desire in order to unroot my 2.1, then make it able to upgrade to 2.2 via OTA.
I am using rooted HK 2.1 ROM, have downloaded Asia WWE 2.1 RUU and extracted those .img files.
How can I disable the signature checking? I've got below errors when I tried to flash the img file to my Desire.
C:\r5>fastboot flash userdata userdata.img
sending 'userdata' (2 KB)... OKAY
writing 'userdata'... INFOsignature che
FAILED (remote: signature verify fail)
If you are using a custom recovery like clockwork mod or Amon ra. There is an option called "Toggle Signature".
txitxi2004 said:
If you are using a custom recovery like clockwork mod or Amon ra. There is an option called "Toggle Signature".
Click to expand...
Click to collapse
thanks, but ADB is unable to connect to the device if it is in recovery mode, can only be in fastboot mode. So that I need to disable signature checking in fastboot mode.
scott4 said:
thanks, but ADB is unable to connect to the device if it is in recovery mode, can only be in fastboot mode. So that I need to disable signature checking in fastboot mode.
Click to expand...
Click to collapse
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
kekojan said:
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
Click to expand...
Click to collapse
i've tried flashing the original recovery.img to Desire, still can't solve the signature check problem. I also have tried doing below:
push flash_image and mtd0.img (what should be the CID of HK 2.1 official rom?) to Desire through ADB, the execute like: flash_image misc mtd0.img
however the upgrade still couldn't pass the signature check... sigh..
kekojan said:
I'm looking the answer for the same problem. I get "signature verification failed" when using fastboot flash method. Any instructions got how to disable signature check?
Click to expand...
Click to collapse
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
st0kes said:
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
Click to expand...
Click to collapse
So, is there any way I can flash the images I build for Desire? (I have rebuild the froyo platform for desire)
Can I flash them via sdcard using for e.g clockwork or similar recovery method?
kekojan said:
So, is there any way I can flash the images I build for Desire? (I have rebuild the froyo platform for desire)
Can I flash them via sdcard using for e.g clockwork or similar recovery method?
Click to expand...
Click to collapse
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
I zipped system.img and boot.img and toggled off the signed files in clockwork and flashed the zipped (50Mb) package. All were installed really way too fast and without errors. After reboot nothing was updated. Next steps? Any ideas?
eh.. delete me
Update to previous post. I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing (clockwork) was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
kekojan said:
I zipped system.img and boot.img and toggled off the signed files in clockwork and flashed the zipped (50Mb) package. All were installed really way too fast and without errors. After reboot nothing was updated. Next steps? Any ideas?
Click to expand...
Click to collapse
st0kes said:
Pack the contents of out/product/target/bravo/system into a zip fille (just the system directory) along with the boot.img, and flash it using clockwork recovery. Toggle signed files to off to allow this or sign the file using testsign.jar (you can find it on the board here somewhere).
You will have to remove the symlinks in out/product/target/bravo/system/bin and symlink them again during the flashing process using an update-script or you will have a lot of broken stuff (like dhcp), check inside an existing rom like CyanogenMod to see how the update-script is constructed and how get the syntax right.
Click to expand...
Click to collapse
Now I did as per the instructions except the update-script part.
I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
kekojan said:
Now I did as per the instructions except the update-script part.
I did zip the system directory + boot.img. Actually, in a second try I also zipped system.img to same package. And I also removed the symlinks from ../bin directory. And then flashed. I got no errors but again installing was really quick and after reboot nothing changed. The weird thing is that I do not get any errors no matter what I'm zipping.
What can I try next?
Click to expand...
Click to collapse
The corresponding part of the recovery log below.
- Installing: SDCARD:images_new.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:images_new.zip
Opening update package...
I:Update file path: /sdcard/images_new.zip
Installing update...
I:Trying update-binary.
I:Trying update-script.
Starting recovery on Fri Sep 3 13:03:42 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Set boot command "boot-recovery"
Command: "recovery"
What do you think what is wrong?
st0kes said:
You can't do that with the bootloader on the desire. Our version of fastboot is "S-ON" (security enabled). You need an engineering bootloader (S-OFF) to flash images using fastboot. Hopefully we will get this one day.
Click to expand...
Click to collapse
technically, that is incorrect.
S-ON or S-OFF is a flag that's being interpreted by fastboot/hboot.
The engineering bootloader you talk about, ignores this flag and exposes developer options like flashing through the fastboot protocol directly, without a signature.
scott4 said:
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
Click to expand...
Click to collapse
I like the theory, but you would probably have to fool the RRU so that it thinks your img files have the same checksums as the original img files. I've never heard of anyone being able to repack and flash an RRU file.
kekojan said:
Starting recovery on Fri Sep 3 13:03:42 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v2.5.0.1
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Set boot command "boot-recovery"
Command: "recovery"
What do you think what is wrong?
Click to expand...
Click to collapse
I think something is wrong with your update-script.
Btw, forget about your system.img, you can't use it .. you have to work with the contents of the system directory instead
ieftm said:
technically, that is incorrect.
S-ON or S-OFF is a flag that's being interpreted by fastboot/hboot.
The engineering bootloader you talk about, ignores this flag and exposes developer options like flashing through the fastboot protocol directly, without a signature.
Click to expand...
Click to collapse
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
st0kes said:
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
Click to expand...
Click to collapse
unrevoked 3.2 seems to be able to set to S-OFF!! but waiting it release
st0kes said:
Are you sure about that? I had always thought that S-OFF meant it was an engineering bootloader.
I didn't think you could get an engineering bootloader that was also S-ON.
Click to expand...
Click to collapse
Bootloaders are either ship or eng.
The latter ignores secuflag and allows extended fastboot commands.
So bootloader or s-off are two separate things.
S-off is mainly for unsigned flashing and nand writelocks.
scott4 said:
unrevoked 3.2 seems to be able to set to S-OFF!! but waiting it release
Click to expand...
Click to collapse
only on cdma desire.
For gsm desire you will need to wait for our s-off/eng hboot 0.93 release.
This is a patched hboot to ignore security, and allow extended fastboot commands.
So essentially S-OFF and eng.
scott4 said:
Currently in order to unroot Desire, is to push flash_image and mtd0.img to Desire through ADB, and then execute like: flash_image misc mtd0.img, then is able to run any RUU to unroot Desire. Since we still do not have RUU 2.1 or 2.2 for official HK rom (not test rom), we have no way to unroot our HK Desire.
I am thinking if there is any trick can mimic a RUU .exe file which is able to change back the CID or signature file to an official Hong Kong one. Then OTA can be done as it check signature during OTA upgrade. Do you think it is workable?
Click to expand...
Click to collapse
Flashing the misc partition allows you to bypass (fake, really) version checks with an RUU flash, nothing more. It doesn't affect root nor does it have anything to do with signature checking (which is currently impossible to disable on the GSM Desire).
hi guys
i have installed custom rom and then again installed stock rom
now i can see ACE PVT SHIP S-ON in bootloader first line
i am permrooted using visionary and installed rom manager
and also radio s-on
i have a fota update
but i am unable to update because i still have clockwork mod recovery
if i press recovery in bootloader then clockworkmod recovery will be opened
how to go to stock recovery i,e a picture of cellphone and a red traingle
i think update will only work only if there is stock recovery
i have tried many ways but i have not succeded
like
---------------
adb shell
su (if you get permission denied, you have to do Visionary temproot)
getprop ro.cid (this will tell you your stock CID, we will use that later, so write it down. It has eight digits.)
busybox dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21 (it will replace clockworkmod with original recovery)
sync (wait 10 secs after that, then you can close the adb shell window)
i see 7490+files in
7490+files out
and i type sync and wait for 1 min but no use
------------------
from terminal emulator
su
flash_image recovery recovery.img
i see "flash_image" not found
------------------
i have used fastboot method
downloaded fastboot.zip and extracted
and placed recovery.img in extracted folder and in run cmd as admin
and type c:\fastboot
flash recovery recovery.img
but i got fastboot.exe is not valid win32 application
---------------------
please guide me
thank u
Try this link, it might prove to be useful, especially the link by dr.m0x he has outlined some steps, I found it useful for myself. You will find the post at the end of the thread.
How to completely remove clockwork
Tried as said by.Dr.m0xd but I am getting an error "fastboot.exe is not a valid win32 application" I am using win 7 64bit home premium
Please some.one guide me
Thank-you0
Pls some one help me
karthik_vit07 said:
Pls some one help me
Click to expand...
Click to collapse
I assume you have the SDK installed.
From where you downloaded the fastboot.exe, Download it from http://developer.htc.com/adp.html
It is working fine for me on the same setup...copy the file on to the tools folder in the SDK...
Fastboot will not work because you have SHIP bootloader.
Busybox DD does not work because you do not have S-OFF. So get Radio S-OFF, reboot, replace the recovery using that dd command and then go back to S-ON.
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
Hello,
I've encountered one stop point in my way to Jelly Bean. I'm playing with Desire HD, Android 2.3.5, HBOOT-2.00.0027. I've managed to get root by SuperOneClick, but I'm not able to flash the recovery. While I have root privs, I've downloaded "recovery-clockwork-touch-5.8.1.5-ace.img" and put it do sdcard as "recovery.img". Then I've tried to boot to hboot and through the fastboot run the following command:
fastboot flash recovery recovery.img
sending 'recovery' (3554 KB)...
OKAY [ 0.610s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.220s
As you can see without success. Second try was updating the recovery partition with shell root privs through adb shell:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21
7108+0 records in
7108+0 records out
3639296 bytes transferred in 2.905 secs (1252769 bytes/sec)
I've got no error, but partition wasn't updated. It still contains the same data as I wouldn't run dd command at all. Is the partition in some kind of read only mode or ? I don't understand how it it possible. I thought that with the root I can do everything.
Is there any other way how I can move image data to recovery partition with the dd?
Are you S-Off or is your bootloader unlocked? If you don't know, paste the contents of hboot here.
The bootloader is locked with security on. Doesn't it matter actually? I thought that if you havethe root privileges, you can flash custom recovery with no problems. Apparently not.
I prefer not to use the htcdev unlocker. So what to do?
Root is software; it has nothing to do with flashing to hardware partitions. You flashed root somehow; did you unlock and then relock your bootloader? How did you root? At this point the best S-Off tool is retired. Unless you want to doc it manually, you need to unlock the bootloader with HTCDEV.
bananagranola said:
Root is software; it has nothing to do with flashing to hardware partitions. You flashed root somehow; did you unlock and then relock your bootloader? How did you root? At this point the best S-Off tool is retired. Unless you want to doc it manually, you need to unlock the bootloader with HTCDEV.
Click to expand...
Click to collapse
I know linux a little bit. Simply as I have written already I've got the root by running SuperOneClick application. Not sure what exploit it uses (perhaps ZergRush).
>did you unlock and then relock your bootloader?
No. As I said, I thought that I can simply move data to eMMC partition while I'm root by dd command. I dunno why I need to unlock and lock the bootloader again.
>How did you root?
Run the SuperOneClick application and clicked the "Shell root" button, then connect to phone through the adb connection, wrote "adb shell" and voila got "#".
>At this point the best S-Off tool is retired. Unless you want to doc it manually, you need to unlock the bootloader with HTCDEV.
Mmm, could tell me how the bootloader blocks the "dd" command from rewriting data on the eMMC partitions?
Can I download the S-Off tool somewhere, or unlock bootloader somehow else, why the root privileges are not enough here?
I'd like to know more about that.
I don't know anything about SuperOneClick. If it S-Offs your phone you should be fine just fastboot flashing a recovery. Can I see what your hboot says? If your phone in fastboot mode?
It helps that you know Linux. The closest Linux analogy is UEFI v. su rights. Root gives the ROM partition su rights in software. However, the bootloader won't let you flash other stuff to the partitions in hardware. They're separate issues.
EDIT: I just reread your OP. You need to have the recovery.img on your computer, not your phone. Then run fastboot from the folder where that recovery.img is saved.
SuperOneClick is here: http://forum.xda-developers.com/showthread.php?t=803682
Bootloader:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
etc...
Er, you are S-On and your bootloader is locked. Are you sure you have root?
SuperOneClick does nothing for HTC devices, AFAIK its simply designed for root and go Motorola and LG phones... same applies for Gingerbreak v1.20 or 1.5...i cant remember if its 1.2 or 1.5.... S-off is hard to obtain now that AAHK is retired, but there are advanced instructions on the developer of AAHK on his/her webpage
Sent from my Inspire 4G using xda premium
> Er, you are S-On and your bootloader is locked. Are you sure you have root?
Well, I have written already that I have security on and my bootloader is locked.
> SuperOneClick does nothing for HTC devices
why I got shell root with it then?
As I understand the issues:
Root - 'root' is linux super user that has all the privileges, if you are the root you are not limited by OS to do everything you want.
Bootloader lock - you can't flash custom ROMs in the fastboot mode, probably because of the fact that the custom ROM or the custom recovery are not signed
- what does it mean actually that the bootloader is unlocked? That it is rewrited by hacked version of bootloader where sign check is jumped? or I am wrong...
S-ON - hardware lock, probably you can't write to partitions ???
- probably that eMMC is set to be in read only mode by registry settings directly in eMMC chip? Am I right? And it is done in every boot when hw is initialized
As I said, I've got root privileges, so I am root in the Android and I can read from and write to everything in the Android. I've got it by some exploit (ZergRush / Gingerbreak). I'm not sure because it was set to "Auto" in the SuperOneclick app.
My situation:
Ok, I am able to obtain root privileges and I can rewrite eMMC partitions, but it has no effect probably because of S-ON (not sure here, nobody wants to tell me ).
I can't flash recovery through fastboot, probably because clockworkmod recovery is not signed by HTC.
As I understand, I can only follow the AAHK. It means downgrade to lower Android version where it is to possible get S-OFF and then it is possible to get root and rewrite eMMC.
I thought that obtaining the root is enough to rewrite the eMMC without S-OFF and/or unlocked bootloader, simply by rewriting block device in Linux.
AAHK is retired, but you can unlock your bootloader.
Ok.
I used AAHK to downgrade, S-OFF and root. Currently I'm running JellyTime 4.2...
Hey Folks!
After the dead of my desire (7 buzzes / vibrates -> indicates a broken soc/motherboard) and the new rising (got a motherboard of a desire with a broken screen) the old lady worked again!
I got the s/n and system from the one with the broken screen - this is normal because it's stored on the mainboard. It was a CM v7 as I remember.
Here as a list of things I did and where I stuck now:
flashed an up-to-date recovery TWRP -> worked
tried to install a new rom with a new hboot which -> didn't worked out
Since here I only can access the recovery
All attempts to flash something (via recovery or fastboot) -> doesn't work
also tried to use revolutionary (even it's already unlooked and s-off) -> but the app stucks
I could only flash the boot logo via fastboot the rest results in different errors like:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?
Here is an other error message i get when running this fastboot command
Code:
fastboot getvar all
getvar:all FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm realy appreciate any help!
BTW: I'm not a robot!
Des!re said:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?
Click to expand...
Click to collapse
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.
eddiehk6 said:
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
Click to expand...
Click to collapse
Thanks for your reply. Some things I forgot to mention in the thread above.
I successfully rooted, s-off, and flashed a new hboot & rom to my old desire.... all before she died. I remembered I needed some tries for the hboot... but it worked out fine in the end.
I also need to say that I tried (with the new/repaired one) different clients (hardware and os, win & linux) and different cables. Just to be sure.
I also went sure that fastboot is working (fastboot devices) and there always was my serial -> so it's good for sure
I read something about that the Alpharev hboot (with the repaired phone there was also the bootsplash with 'alpha-rev s-off / why so serious?' before I flashed it away to the stock 'htc') is somehow write-protected itself which can cause issues???
I tried to flash the "Alpha Jelly (250/5/182) hboot" to be able to install CarbonRom 1.0 (4.4.4) by spezi77 (http://forum.xda-developers.com/showthread.php?t=2658853). But I didn't succeeded at all.
eddiehk6 said:
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
Click to expand...
Click to collapse
I think I flashed the recovery via fastboot, it just worked once. When I tried to flash CWM it didn't worked anymore.
eddiehk6 said:
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
Click to expand...
Click to collapse
I did checked the md5sum's and I tested a couple of Roms (more than 3)
eddiehk6 said:
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
Click to expand...
Click to collapse
My old devices was a PVT4 and the repaired one is a PVT1 - there should be no difference for the hboot i guess?
eddiehk6 said:
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
Click to expand...
Click to collapse
This I should have done straight after I repaired the hardware and I was able to boot in CM7.... To late for now but if I have a working state I definitely do this!! :good:
eddiehk6 said:
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
Click to expand...
Click to collapse
I don't have a booting system yet so I need to postpone this. To be able to do the pb99img.zip method i formatted the whole sd-card with one partition as fat32. But when I have (hopefully) soon a working system I need to partion it correctly - easy!
eddiehk6 said:
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.
Click to expand...
Click to collapse
I'm the resarcher! I'm going down to reasearch - I will report!
Thanks for your help so far!
I'm the resarcher! I'm going down to reasearch - I will report!
Click to expand...
Click to collapse
I went down to research!
I tried to flash hboot 'Bravo Stock' by Alpharev.
Code:
fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)...
OKAY [ 0.104s]
writing 'hboot'...
OKAY [ 0.160s]
finished. total time: 0.264s
looks good for me!
the bootscreen changed from
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
to
Code:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
so first and third line changed!
And because it's so nice to flash hboot i also flashed AlphaRev Jelly successfully!!
I try flash a rom now :fingers-crossed:
After I successfully flashed my hboot (twice!)....
I'm not able to wipe or install stuff....
Team Win Recovery Project v2.7.1.0
WIPE -> Factory Reset (Wipe Data, Cache and Dalvik)
Code:
Factory Reset Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
E:Unable to recreate and-sec folder.
Updating partition details...
E:Unable to mount storage
E:Unable to mount /sdcard during GUI startup.
Full SELinux support is present.
E:Unabke to mount /sdcard/TWRP/.twrps when trying to read settings file.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Updatting partition details...
E:Unable to mount storage.
### FAILED ###
Team Win Recovery Project v2.7.1.0
Install -> ZIP
Code:
Zip Install Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
Installing '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Could not create file for updater extract in '/tmp/updater'
Error flashing zip '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'
Updatting partition details...
### FAILED ###
Maybe there is something "broken" with the filesystem?
As always I appreciate any help
Did a 'clear userdata' in the boot menu and then a wipe via TWRP.
Now it was successful but with this errors in the console:
Code:
Factory Reset Complete
Successful
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Wiping Android Secure
Formatting SD-Ext using make_ext4fs function.
Updating partition details...
But I wonder where are these errors from
Installing a rom still doesn't work. I think the problem is this line:
Code:
E:Could not create file for updater extract in '/tmp/updater'
There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
You have to do the following steps to flash any files :
- boot into recovery mode
- choose 'Advanced'
- choose 'Terminal Command'
- You're now on the '/' (root of the file system). Choose 'Select'
- Type : 'mkdir tmp' without quotes, then Hit the enter key of your keyboard.
- Return to the main screen (Go back 3 times)
- Choose 'Install' and select the file.
Click to expand...
Click to collapse
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046
Des!re said:
There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046
Click to expand...
Click to collapse
I've personally never used TWRP on the Desire.
I recommend trying with 4EXT Recovery, never had any issues with it.
If you can successfully flash an hboot, you should be able to flash the recovery.img using the same method.