Hi guys..
"just check again in fastboot, ENG HBOOT version has changed to 6.98.2000 iirc. After running the RUU it should be 0.98.0000 again as ENG HBOOT can be overwritten in contrast to the AlphaRevX HBOOT. If you only want ENG HBOOT don't flash the RUU obviously"
This is what I read over at the thread on how to restore to default Rom and s-on...
But I don't get it...
I am currently on hboot 6.xxxxx and have the latest virtuous unity Rom installed.
I want to return to stock Europe Rom and the update to the latest sense 3 its from HTC. I don't want custom ROM anymore Which hboot do I need to flash? Can I flash the enghboot over my curent alpharevx hboot? Is there a risk of bricking? thanks
Just flash the coresponding RUU it will bring everything to stock, including hboot.
If the 6.xx.xxxx hboot really cannot be overwritten then flash this HBOOT
reboot to fastboot with debbuging ON
connect to PC
extract the hboot from the archive
rename it to hboot.img
open cmd
go to the folder where you have fastboot executable (android-sdk\...)
put the hboot there
type
Code:
fastboot devices
if the device is listed type
Code:
fastboot flash hboot hboot.img
fastboot reboot-bootloader
check the new version it has to be 0.98.2000
start your RUU on the PC
Wow thanks! +1
amidabuddha said:
Just flash the coresponding RUU it will bring everything to stock, including hboot.
If the 6.xx.xxxx hboot really cannot be overwritten then flash this HBOOT
reboot to fastboot with debbuging ON
connect to PC
extract the hboot from the archive
rename it to hboot.img
open cmd
go to the folder where you have fastboot executable (android-sdk\...)
put the hboot there
type
Code:
fastboot devices
if the device is listed type
Code:
fastboot flash hboot hboot.img
fastboot reboot-bootloader
check the new version it has to be 0.98.2000
start your RUU on the PC
Click to expand...
Click to collapse
tried this and got :
sending 'hboot' (1024 KB)...
OKAY [ 0.210s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.016s]
finished. total time: 0.226s
and my phone says : can not roll back hboot
my hboot version is 6.98.1002
i tried your guide through fastboot usb mode.
what am i doing wrong ? sorry for being noob or talking bad english :/
oLf06 said:
tried this and got :
sending 'hboot' (1024 KB)...
OKAY [ 0.210s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.016s]
finished. total time: 0.226s
and my phone says : can not roll back hboot
my hboot version is 6.98.1002
i tried your guide through fastboot usb mode.
what am i doing wrong ? sorry for being noob or talking bad english :/
Click to expand...
Click to collapse
It seems that your bootloader cannot be downgraded to the old version. So try to flash this one. Flash only the hboot.img, not the kernel and lib images that are in the same zip in this thread. I flashed a RUU on it without a problem. Let me know is it working
so i dont need to do the nandroid backup, just flash the hboot.img as described above?
oLf06 said:
so i dont need to do the nandroid backup, just flash the hboot.img as described above?
Click to expand...
Click to collapse
yes make a backup of course it will not harm You have to do backup before every eventually dangerous alteration of your system
okay... didnt made a backup ( because im not able to / different error, dont mind ) but i flashed the hboot.img from the thread using the above method. same output on my phone and in cmd. "(bootloader) image update is bypassed! " etc....
oLf06 said:
okay... didnt made a backup ( because im not able to / different error, dont mind ) but i flashed the hboot.img from the thread using the above method. same output on my phone and in cmd. "(bootloader) image update is bypassed! " etc....
Click to expand...
Click to collapse
Hey what errors?
Can you please explain, because the thread opener was asking for a guidance to return to stock. He has no errors and my method is for him.
If you have different situation please explain in details before doing anything on you device...
My problem is that i have the eMMc error :
E:cant mount cache etc....
i made the test and got no errors so the chip is not broken.
now i tried your method :
mke2fs /dev/block/mmcblk0p27
reboot recovery
. that runs without erros but clockwork still says "e:cant mount ..."
now i wanted to flash the hboot to 0.98 so i can use RUU ( with my hboot version it gets stuck at " restarting bootloader" or something like that.
But i am still not able to do that.
I spend the last 2 hours trying to flash the 4extrecovery without any success :/ can't flash with OneClick, installing the zip through recovery runs without errors but dont take effect. and the last 10 minutes i am watching the cmd window because i tried to flash the recovery using fastboot flash all i get is " writing 'recovery' "
edit: i am able to install a new rom ( virtous unity ) but my phone still stucks at the white HTC screen
do you have output on adb command? Try to flash the 2.00.2002 bootloader like in the linked thread I gave you above
EDIT: when you run the RUU there is a temp folder created on your C: drive. Open the Windows Explorer and search for the file rom.zip. Copy the file to another location. Extract it and try to flash the hboot included there
tried to flash the hboot from RUU ... still getting :
sending 'hboot' (1024 KB)...
OKAY [ 0.199s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.287s
oLf06 said:
tried to flash the hboot from RUU ... still getting :
sending 'hboot' (1024 KB)...
OKAY [ 0.199s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.287s
Click to expand...
Click to collapse
have you tried the adb command shell from recovery???
a) copy STOCK hboot.img from RUU to sdcard
b)reboot into recovery
b1)In cmd run the following commands (after each command press enter):
adb devices
adb shell
su
c)backup your hboot dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
d) flash new hboot dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
reboot to hboot and check your hboot version
tried this method and getting:
~ # dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.034664 seconds, 28.8MB/s
~ # dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 10.633719 seconds, 96.3KB/s
got this hboot.img from "RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe"
hboot version still : 6.98.1002
edit : i cannot flash the 2.00.2002 bootloader like in the link you gave me because according to the instructions i have to make a nandroid backup. this is not possible for me because of the error " cant mount/data" . I cannot find this error at google.
sorry for my bad english by the way.....
oLf06 said:
hboot version still : 6.98.1002
edit : i cannot flash the 2.00.2002 bootloader like in the link you gave me because according to the instructions i have to make a nandroid backup. this is not possible for me because of the error " cant mount/data" . I cannot find this error at google.
sorry for my bad english by the way.....
Click to expand...
Click to collapse
It seems that your partition table is messed up and the system cannot find the necessary partitions. A bit dangerous suggestion but maybe you can try skipping the backup. And the RUU that you are using is quite old, try the 1.47.401.4 - it worked for me
format ALL your partitions in recovery.
Then go here http://forum.xda-developers.com/showthread.php?t=1113820
download the PG88IMG file from the 1st post.
open it on your pc and extract the hboot.img file to your desktop, then copy it to the root of your sd card.
connect phone vie adb again and enter the following commands, after each line press enter!
adb shell su
adb shell dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
adb shell dd if=/data/local/tmp/hboot.img of=/dev/block/mmcblk0p18
adb reboot bootloader
Then you are on OLD ENG HBOOT!
Eclipse_Droid said:
format ALL your partitions in recovery.
Click to expand...
Click to collapse
sorry about this noob question but what do you mean with ALL my partitions ?
wipe data/factory reset ?
wipe cache partition ?
format /cache ?
format /data ?
format /sdcard ?
format /system ?
should i do everything i mentioned above or am i missing something ?
oLf06 said:
sorry about this noob question but what do you mean with ALL my partitions ?
wipe data/factory reset ?
wipe cache partition ?
format /cache ?
format /data ?
format /sdcard ?
format /system ?
should i do everything i mentioned above or am i missing something ?
Click to expand...
Click to collapse
format in this order,
system
data
cache
then select wipe data factory reset.
then follow the rest of my guide
on some point this starts to be personal...
error formatting /system
error formatting /data
error formatting/cache
now i am making the factory reset,
trying to flash the hboot tomorrow.... but dont have much hope :/ Thank you guys for now for your great help ... maybe you have some more hints for me ..
general question here.. i am typing the commands when i am in recovery ( clockwork ) because this is how i can see my device when i type " adb devices " .. is this right or am i doing something generally wrong ?
EDIT:
adb shell dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
adb shell dd if=/data/local/tmp/hboot.img of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
am i right that this doenst make sense ? because "/data/local/tmp/hboot.img" doenst exist?
however ... it is not working again
EDIT 2 : okay.. i searched a bit on google and found out that there is a hboot driver i didnt install .. but my device still cant get listed... dont know why... maybe because usb debugging is not enabled ? how do i enable it in bootloadeR?
Related
a friend of mine sent me an hboot and radio image to update on my g1. he's got a dev phone, and he was able to use fastboot to flash these images...i've got a t-mobile g1 with JFv1.41 and the Engineering SPL, but fastboot will not flash these images on my phone...i've also tried this with HardSPL - no dice. also, i've made sure to install the USB drivers, and my g1 is being recognized by my pc in fastboot mode...here are the errors i get when i run fastboot:
C:\G1\fastboot-files>fastboot -p dream flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... FAILED (remote: partition does not exist)
C:\G1\fastboot-files>fastboot -p dream flash radio radio.img
sending 'radio' (512 KB)... OKAY
writing 'radio'... FAILED (remote: partition does not exist)
I've done quite a bit of searching but nothing seems to come up regarding the "partition does not exist" error. is there a way for me to resolve this, or is it simply that i have a t-mobile g1 and not a dev phone?
thanks
kup22r said:
a friend of mine sent me an hboot and radio image to update on my g1. he's got a dev phone, and he was able to use fastboot to flash these images...i've got a t-mobile g1 with JFv1.41 and the Engineering SPL, but fastboot will not flash these images on my phone...i've also tried this with HardSPL - no dice. also, i've made sure to install the USB drivers, and my g1 is being recognized by my pc in fastboot mode...here are the errors i get when i run fastboot:
C:\G1\fastboot-files>fastboot -p dream flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... FAILED (remote: partition does not exist)
C:\G1\fastboot-files>fastboot -p dream flash radio radio.img
sending 'radio' (512 KB)... OKAY
writing 'radio'... FAILED (remote: partition does not exist)
I've done quite a bit of searching but nothing seems to come up regarding the "partition does not exist" error. is there a way for me to resolve this, or is it simply that i have a t-mobile g1 and not a dev phone?
thanks
Click to expand...
Click to collapse
don't use -p dream
just use fastboot flash
didnt work
andonnguyen said:
don't use -p dream
just use fastboot flash
Click to expand...
Click to collapse
I am having the same problem, i am still getting the same error without the -p dream.
I'm getting this for fastboot flash hboot as well
a few weeks ago I used fastboot to flash a radio image and it worked just fine.
Bump. I'm having this issue as well and can't find any hints about how to fix it.
I'm having the same problem with adp1
co-sign...
did anyone ever figure out what the problem here was?
If so, they haven't shared...
same prob
I had this same problem several months ago. I was able to solve it myself using the search function. But in case anyone is interested it has to do with a perfected spl. You have to flash at least an engineering spl with S=Off in order to fastboot flash.
bkmo said:
I had this same problem several months ago. I was able to solve it myself using the search function. But in case anyone is interested it has to do with a perfected spl. You have to flash at least an engineering spl with S=Off in order to fastboot flash.
Click to expand...
Click to collapse
Um no, I could fastboot flash radio, blah blah, just not hboot.
vincom2 said:
Um no, I could fastboot flash radio, blah blah, just not hboot.
Click to expand...
Click to collapse
I'm having the same problem, but I'm trying to flash the radio
That is because the 0.95.x000 SPL's do not have the hboot partition mapped.
You need to do one of two things;
1) first recovery-update to 1.33.2003 (note the "3". This is NOT a "5".) -- the "2003" spl has the hboot partition mapped.
2) ERASE your recovery partition (and test that it is erased by trying to boot into recovery -- it should boot into FASTBOOT), and then recovery-update to whatever SPL you prefer. I know, this sounds impossible -- just how do you boot recovery if your recovery is empty? By "fastboot boot recovery.img".
Either of these approaches should be fine.
lbcoder said:
That is because the 0.95.x000 SPL's do not have the hboot partition mapped.
You need to do one of two things;
1) first recovery-update to 1.33.2003 (note the "3". This is NOT a "5".) -- the "2003" spl has the hboot partition mapped.
2) ERASE your recovery partition (and test that it is erased by trying to boot into recovery -- it should boot into FASTBOOT), and then recovery-update to whatever SPL you prefer. I know, this sounds impossible -- just how do you boot recovery if your recovery is empty? By "fastboot boot recovery.img".
Either of these approaches should be fine.
Click to expand...
Click to collapse
Is that the same problem and solution if I get the error when trying to flash the radio?
D:\sdk\tools>fastboot flash radio radio.img
sending 'radio' (21504 KB)... OKAY
writing 'radio'... FAILED (remote: partition does not exist)
Click to expand...
Click to collapse
Stryder5 said:
Is that the same problem and solution if I get the error when trying to flash the radio?
Click to expand...
Click to collapse
What do you think?
It sounds logical enough, but I thought HardSPL should be able to flash the radio without any issues?
That's what I was following in the Cyanogen wiki:
(HardSPL/Engineering Spl Users) Radio installations can be had by fastboot flash radio radio.img after extracting radio.img from the .zip
Click to expand...
Click to collapse
I'm rooted and already on CM 4 with HardSPL installed. I remember using fastboot to flash something a while back but it's been a long time since I've played with modding my G1.
EDIT: I went ahead and just used recovery to install the radio. Thanks anyways!
I have downlaoded the fastboot binary for my mac from here:
http://developer.htc.com/adp.html
because It never turned up in my android sdk
# ./fastboot-mac flash splash splash1.img
sending 'splash' (750 KB)... OKAY
writing 'splash'... FAILED (remote: partition does not exist!)
-------------------------
EDIT: worked out it was a typo! that splash should be splash1.
anybody can tell me please the commands to mount sdcard and unmount sdcard via fastboot or adb please.... i unmount my sdcard and have a brivked phone, and i cant flash nothing thru adb or fastboot . please.
leo_hacker82 said:
anybody can tell me please the commands to mount sdcard and unmount sdcard via fastboot or adb please.... i unmount my sdcard and have a brivked phone, and i cant flash nothing thru adb or fastboot . please.
Click to expand...
Click to collapse
You can find a compatible dreaimg.nbh, put it on sdcard, and flash that through bootloader, but other than that, you can't do anything with a bricked phone, aside from jtag.
Hi Guys.
Before i start i want to mention that i searched everywhere and basically all these technical guide's and terms makes me even more confused and i don't really know what to do with this problem i have.
Ok here we go, last night i S-Off and Rooted my cousin's HTC Desire S with (revolutionary-0.4pre4 and Superuser-3.0.7-efghi-signed).
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
So far so good, this all worked fine. No problems.
After that i installed the "RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed"
It was successfully flashed but here is where the problems started, after this i got the famous "stuck on white background with green HTC Logo"
Now to make things worse, i cannot access SD Card from the phone and it will not recognize my phone anymore from my PC (with ADB drivers installed).
The only thing that does work and recognize my phone is the "Fastboot USB" mode on my phone along with the "
ROM Upgrade Utility (RUU) - Aruwizard.exe"
I got a tons of errors and problems.
1. HBOOT gives
SD Checking...
Loading... [PG88DIAG.zip]
No image!
Loading... [PG88DIAG.nbh]
No image or wrong image!
Loading... [PG88IMG.zip]
2. in Recovery menu the following problems occur
E:Can't open /cache/recovery/command
Wipe data/factory reset gives
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Apply update from sdcard gives
-Invalid Operation-
Also i seem to have lost a few options in recovery after the RUU like "install zip from sd card" etc
My question is : Is there anything that can fix this or did the RUU bricked it completely?
I believe before flashing you were supposed to do a downgrade HBOOT using ENG HBOOT
Atleast thats what i did!
Revolutionary hboot has protection to prevent it from being overwritten, the way to change the hboot is to write it through recovery, but you also need to flash a recovery option (if none is available), through fastboot.
Basically, check if CWM or EXT4 are installed, if yes flash hboot through recovery (see the last 10 pages of the ENG HBOOT thread), if no, flash recovery through fastboot (see google), once recovery is installed, flash hboot, then proceed with RUU.
I tried this as well
http://forum.xda-developers.com/showthread.php?t=958968
But no luck either
fastboot oem rebootRUU (Gives grey HTC Logo on my phone)
C:\android>fastboot flash zip HTC_DESIRE_S_2.3.5-2.10.401.4.zip
sending 'zip' (337560 KB)...
OKAY [ 55.123s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 65.056s
Click to expand...
Click to collapse
Most other commands just give a "(bootloader) [ERR] Command error !!!" so i just ended it with "fastboot reboot"
So my guess is that is must have something to do with that HBOOT thing yes.
"adb devices" will not find any devices at all.
C:\android>fastboot flash hboot hboot.img
< waiting for device >
sending 'hboot' (1024 KB)...
OKAY [ 0.196s]
writing 'hboot'...
(bootloader) image update is bypassed! (cannot roll back hboot version)
OKAY [ 0.026s]
finished. total time: 0.222s
Click to expand...
Click to collapse
I don't know if i can put the other eng hboot back
"Fastboot devices" still gives me a serial number in cmd prompt so that still works.
Where can i find a recovery.img for the Desire S?
I found a whole list here but i don't know which one to pick?
download.clockworkmod.com/recoveries
i tried "recovery-clockwork-2.5.0.7-desirec.img"
C:\android>fastboot flash recovery recovery-clockwork-2.5.0.7-desirec.img
sending 'recovery' (2766 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 1.261s]
finished. total time: 1.727s
Click to expand...
Click to collapse
Problem now is, when i select "Recovery" from the hboot menu.. it gets stuck also at the White background / green HTC Logo screen. so now my recovery part is broken also?
Its all working now, i used the wrong recovery image at first.
I got clockwork recovery to work and from there i could do the HBOOT ENG and a pre-rooted RUU
xAutobot and Zeekiz, thanks for your help. Much appreciated!
wut?
Trackah123 said:
Its all working now, i used the wrong recovery image at first.
I got clockwork recovery to work and from there i could do the HBOOT ENG and a pre-rooted RUU
xAutobot and Zeekiz, thanks for your help. Much appreciated!
Click to expand...
Click to collapse
i have exactly the same problem but i do not understand what you did to fix it...
do i need a program for my pc? what recovery did you use? just a simple explanation of what you did because im worried i cant get my phone to work again and im not necessarily a tecnitian... please
I can't remember anymore tbh its been a long time since i did this.
But it had something to do with the right recovery file for your phone i think.
at the clockworkmod rom manager website you can download it.
tehpwnrer said:
i have exactly the same problem but i do not understand what you did to fix it...
do i need a program for my pc? what recovery did you use? just a simple explanation of what you did because im worried i cant get my phone to work again and im not necessarily a tecnitian... please
Click to expand...
Click to collapse
What you need is, first:
- change the revolutionary hboot for an engineering hboot to allow RUU to overwrite it.
--> https://www.box.com/s/8a14444cd1dc4c91f077
This file contains both original and overalpharevx .img (6.98.2000) you should use this one first. You could use fastboot, android flasher or the PG88IMG.zip (the easy way) included to do that.
when it's done you can safely run the RUU and go back to stock (s-on)
or
you can flash 4ext or clockworkmod using fastboot and enjoy your custom rom.
--> https://www.box.com/s/70a0d0608bf3f90b9a3a
hi all new to this ..so my problem is i did the S off with the wire trick it worked but before it could completely reboot and do its thing em i lost my adb drivers so i had delete em and reinstall so unplugged phone before whole process and now im having worst time flashing recovery been at this for 6 hours now and no luck my fast-boot is working but cant flash Ive tried super utility, flashing thru fast-boot and installing zip on SD card with card reader nothing works help please i hope i made sense in this thread
yambo62274 said:
hi all new to this ..so my problem is i did the S off with the wire trick it worked but before it could completely reboot and do its thing em i lost my adb drivers so i had delete em and reinstall so unplugged phone before whole process and now im having worst time flashing recovery been at this for 6 hours now and no luck my fast-boot is working but cant flash Ive tried super utility, flashing thru fast-boot and installing zip on SD card with card reader nothing works help please i hope i made sense in this thread
Click to expand...
Click to collapse
okay try to download 4ext app the link is here:
http://www.4ext.net/get.php?apk
this will give you a recovery without flashing through adb
---------- Post added at 12:34 AM ---------- Previous post was at 12:32 AM ----------
or maybe you have not enabled usb debugging its under developer on the settings
As the post above says you can get 4EXT Recovery on your device , but first you will need an eng Hboot cause I think that is the cause of your problem. Got to the Unlimited.io website and click on downloads and down load the Hboot version for the pyramid and the version or Android you are using. Then use the following fastboot commands.
Code:
fastboot erase cache
fasboot rebootRUU
fastboot flash zip jb_hboot.zip
This should fix any fasboot issues or other ADB issues because all commands are usable with the eng Hboot.
well im stuck in the bootloader how would i use an .apk sorry if im a rookie and cant get to debug cuz i have nothing to boot off dam im not explaining it well i think lol
thx
T-Macgnolia said:
As the post above says you can get 4EXT Recovery on your device , but first you will need an eng Hboot cause I think that is the cause of your problem. Got to the Unlimited.io website and click on downloads and down load the Hboot version for the pyramid and the version or Android you are using. Then use the following fastboot commands.
Code:
fastboot erase cache
fasboot rebootRUU
fastboot flash zip jb_hboot.zip
This should fix any fasboot issues or other ADB issues because all commands are usable with the eng Hboot.
Click to expand...
Click to collapse
thx you i will try that .... having bad day cant even type or even get buy the image verification lol
almost
T-Macgnolia said:
As the post above says you can get 4EXT Recovery on your device , but first you will need an eng Hboot cause I think that is the cause of your problem. Got to the Unlimited.io website and click on downloads and down load the Hboot version for the pyramid and the version or Android you are using. Then use the following fastboot commands.
Code:
fastboot erase cache
fasboot rebootRUU
fastboot flash zip jb_hboot.zip
This should fix any fasboot issues or other ADB issues because all commands are usable with the eng Hboot.
Click to expand...
Click to collapse
well did what you said when i get to last step it gives me an error cannot load jb zip should i be placing the zip in my fastboot tools folder or something
yambo62274 said:
well did what you said when i get to last step it gives me an error cannot load jb zip should i be placing the zip in my fastboot tools folder or something
Click to expand...
Click to collapse
yes!!!
hboot
T-Macgnolia said:
As the post above says you can get 4EXT Recovery on your device , but first you will need an eng Hboot cause I think that is the cause of your problem. Got to the Unlimited.io website and click on downloads and down load the Hboot version for the pyramid and the version or Android you are using. Then use the following fastboot commands.
Code:
fastboot erase cache
fasboot rebootRUU
fastboot flash zip jb_hboot.zip
This should fix any fasboot issues or other ADB issues because all commands are usable with the eng Hboot.
Click to expand...
Click to collapse
not sure if matters my hboot is 1.27 S-OFF- LOCKED
asad510 said:
yes!!!
Click to expand...
Click to collapse
put the zip in folder now i get this error
C:\Program Files\Android\android-sdk\tools>fastboot flash zip jb_hboot.zip
sending 'zip' (353 KB)...
OKAY [ 0.274s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.614s
yambo62274 said:
not sure if matters my hboot is 1.27 S-OFF- LOCKED
Click to expand...
Click to collapse
Yes this means it does not allow all ADB and fastboot commands, this is why I mentioned the eng Hboot. It will say JuonutBear where it says LOCKED when you flash the eng Hboot.
---------- Post added at 07:45 PM ---------- Previous post was at 07:42 PM ----------
yambo62274 said:
put the zip in folder now i get this error
C:\Program Files\Android\android-sdk\tools>fastboot flash zip jb_hboot.zip
sending 'zip' (353 KB)...
OKAY [ 0.274s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.614s
Click to expand...
Click to collapse
Are you doing all three commands in the order I put them? Please don't take me being rude by asking just covering the bases.
T-Macgnolia said:
Yes this means it does not allow all ADB and fastboot commands, this is why I mentioned the eng Hboot. It will say JuonutBear where it says LOCKED when you flash the eng Hboot.
---------- Post added at 07:45 PM ---------- Previous post was at 07:42 PM ----------
Are you doing all three commands in the order I put them? Please don't take me being rude by asking just covering the bases.
Click to expand...
Click to collapse
so sorry misread your post i will try that thx you for your help sure youll hear from me again lol need a smoke been on this all day no lie UGHHHHH
T-Macgnolia said:
Yes this means it does not allow all ADB and fastboot commands, this is why I mentioned the eng Hboot. It will say JuonutBear where it says LOCKED when you flash the eng Hboot.
---------- Post added at 07:45 PM ---------- Previous post was at 07:42 PM ----------
Are you doing all three commands in the order I put them? Please don't take me being rude by asking just covering the bases.
Click to expand...
Click to collapse
yes i am and i know your not being rude i appreciate it very much you helping me but your telling me there is something else i have to download other than the jb hboot which is the eng hboot sorry for my inexperience lack of knowledge
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. should i be using any of those commands ???
No you just need to download the Ub_hboot.zip, then place it in the tools folder or what ever folder your fasboot is in. Then boot uourdevice to bootloader and select fastboot and connect your device via USB to your computer. Then use the fastboot commands I posted.
T-Macgnolia said:
No you just need to download the Ub_hboot.zip, then place it in the tools folder or what ever folder your fasboot is in. Then boot uourdevice to bootloader and select fastboot and connect your device via USB to your computer. Then use the fastboot commands I posted.
Click to expand...
Click to collapse
k so once i see juopuntbear at top i can flash 4ext img fastboot methdood ?
yambo62274 said:
k so once i see juopuntbear at top i can flash 4ext img fastboot methdood ?
Click to expand...
Click to collapse
Yes that meansyou have the eng(engineered) Hboot which means it is UNLOCKED. You have to have a unlocked Hboot to use all the ADB and fastboot commands. But you have to be S-Off to flash the hboot, you are S-Off right? I ask cause some how you have missed installing it if you S-Offed with JuopunutBear S-Off.
T-Macgnolia said:
Yes that meansyou have the eng(engineered) Hboot which means it is UNLOCKED. You have to have a unlocked Hboot to use all the ADB and fastboot commands. But you have to be S-Off to flash the hboot, you are S-Off right? I ask cause some how you have missed installing it if you S-Offed with JuopunutBear S-Off.
Click to expand...
Click to collapse
nice finally did it thank you so much for your help i will buy you a beer tomorrow when my funds are deposited you have my word thank you so much i am S off and juopunutbear at top now just to flash the image fastboot i suppose
yambo62274 said:
nice finally did it thank you so much for your help i will buy you a beer tomorrow when my funds are deposited you have my word thank you so much i am S off and juopunutbear at top now just to flash the image fastboot i suppose
Click to expand...
Click to collapse
Yep just flash your recovery and you are good to go. Glad you got it worked out.
loving it
T-Macgnolia said:
Yep just flash your recovery and you are good to go. Glad you got it worked out.
Click to expand...
Click to collapse
thanks again buddy im loving this rom im running ***pegasus*** from Team Elegancia shout out to them for there great rom .....ill hit you up to buy you a beer soon
It all started yesterday where i was trying to update (InsertCoin) which for some reason made my phone shut down mid-way through the installation process...
I had to reboot my phone back into recovery to wipe system/cache/data to reinstall...For some reason this wiped/damaged everything but the bootloader ofc.
(Bye go all my pictures, whatsapp conversations etc...)
This made me not being able to boot into my recovery aswell
I still can't get back into my recovery, and i've tried flashing the recovery over and over again via fastboot flash recovery twrp.img
When i try to flash the recovery, it succeeds but when i try to boot into it, it blinks the splash screen with odd intervals, i dont know if this means that its trying over and over again...I'm sort of desperate here...any help?
sidenote here: I'm in linux
you should've updated firmware to hboot 2.22 needed for IC, then you need to install the latest recovery 2.7.1.1 from twrp website
twrp here: http://techerrata.com/browse/twrp2/m4ul
new firmware here :http://forum.xda-developers.com/showthread.php?t=2759131
I have not updated it, will go and do that now,
Code:
[email protected]:/media/leon/*censor*/Android/ROMS/Millium$ sudo fastboot flash zip firmware.zip
[sudo] password for leon:
target reported max download size of 800227328 bytes
sending 'zip' (19549 KB)...
OKAY [ 2.466s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 4.305s
Right.....!?
I really don't want to reboot to bootloader at the moment...since the update failed...
Apparently i am S-ON and therefor need to obtain s-off, but i don't have an android system installed..how
s-off required to flash firmware or if s-on, bootloader needs to be re-locked, sorry i assumed you knew that! maybe create a signature giving details of your device for future, it does help.
If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
`leon said:
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
Click to expand...
Click to collapse
not work ?? ok, then you will need to s-off the device, unlock first,you need SUPERCID also
Braddison said:
not work ?? ok, then you will need to s-off the device, unlock first
Click to expand...
Click to collapse
It did, sorry, didnt edit the post quick enough
`leon said:
Code:
FAILED (remote: 12 signature verify fail)
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
Click to expand...
Click to collapse
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Braddison said:
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Click to expand...
Click to collapse
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
well you've done everything that i done when i tried out Insertcoin rom for a few days and never had any of your issues. so not sure whats going on.
- unlocked bootloader
- get s-off
- get supercid
- update firmware
- get latest twrp recoverry
- install Insert Coin
use the fix miniwhooper posted on her firmware thread ....Flash stock recovery and factory reset from boot loader. It will fix you /data partition.. then flash custom recovery and it should be fixed
`leon said:
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
Click to expand...
Click to collapse
Make sure you are in the folder your rom zip is located.
Run the command...
adb push filename.zip /sdcard
Wait around 10 minutes as it will not give you progress
go back to TWRP main page and install, choose SDcard and the zip file you just uploaded should be there.
hello @AnGrY sCoTsMaN
i have the exact same problem but i flashed cm.12.1 cant boot in recovery or flash anything using adb
hboot os 2.22 it says unlocked but it seems not
can you please help me out
Edit: problem solved without doing anything
HBOOT 2.16 Installation guide
Requirements before installing
Back up your files, your SD Card will be WIPED!
Charge your phone to AT LEAST 30%
Your bootloader MUST be unlocked
You NEED to be S-OFF or else it won't work
You need basic knowledge of Fastboot commands
Windows 10/8/7/Vista/XP: You need drivers installed
Windows 8.1: You need drivers installed AND update kb2967917 from Microsoft
Linux: You need "51-android.rules" or "99-android.rules" configured
Mac: Nothing needed that I know of
I am NOT responsible if you break your phone
This guide will be from a Windows point of view
Installation Guide
Download the HBOOT 2.16 firmware file from here: Download from Mega.co.nz
Place it in your adb and fastboot folder. For example C:\Users\(Your Username)\Fastboot
Now open a Command Prompt window and then type in:
Code:
cd C:\(Location of your Fastboot folder)
Now take your phone and connect it to your computer (with USB Debugging ON) and type in:
Code:
adb reboot bootloader
Once you are in the bootloader and it displays "Fastboot USB", type in:
Code:
fastboot oem rebootRUU
Once your computer recognizes your phone type in:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
You will then get an error:
Code:
"FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
Don't worry, this is normal. DO NOT unplug your phone. Simply type in once again:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
Then wait until the Command window says "finished" and type in:
Code:
fastboot reboot-bootloader
Next we need to download TWRP recovery. You can download it from MDMower's website and MAKE SURE to get TWRP for "/data/media storage (HBOOT 2.16.0000)" and TWRP 2.8.0.1 or above.
Now we must go back to the command window with your phone still plugged in displaying "Fastboot USB" on the screen
Then we type:
Code:
cd C:\Users\(Your Username)\Downloads
or if the TWRP Recovery file isn't in the above location just direct it to the folder its stored in
Now we type:
Code:
fastboot flash recovery twrp-2.8.x.x-ville-dm.img
just replace the "x" with the numbers on the file. e.g. - 2.8.0.1
Once it flashed successfully press the power button and use the volume buttons to scroll down to recovery and to boot into it, simply press the power button
Now go into "Mounts" and select Enable MTP if it isn't already.
Now copy a ROM of your choice (That supports HBOOT 2.16) and flash it. If MTP doesn't work, simply sideload the ROM
That's it, now you just reboot after installing your ROM.
Hope this helps anybody having difficulty with HBOOT 2.16
Getting a different error when flashing.
c:\adb>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)...
OKAY [ 2.598s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 4.304s
urlyisis said:
Getting a different error when flashing.
c:\adb>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)...
OKAY [ 2.598s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 4.304s
Click to expand...
Click to collapse
You need to change your cid
To change it go into bootloader, then fastboot, connect it to your computer and type
Code:
fastboot oem writecid 11111111
that is eight 1s
If that didnt work then type instead
Code:
fastboot oem writecid HTC__001
that is 2 underscores after HTC
I get this:
Code:
Z:\One_S_All-In-One_Kit_v1.1\Data>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)... OKAY [ 6.507s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 8.020s
No matter how often I attempt it. Redownloaded the zip to make sure it is not corrupt...
Any pointer?
Ah, damn, because I followed the instructions to the end despite the HBOOT not flashing I can also now not access recovery anymore. It seems the new version of recovery was properly flashed, but as it relies on higher HBOOT I can't get into it anymore. It is still in HBOOT 1.03.
Can anyone help me to get this phone ready for Cyanogenmod?
I was able to load the hboot, but now the bootloader is locked again and I can't flash the recovery.
FAILED (remote: not allowed)
Walter_White said:
I get this:
Code:
Z:\One_S_All-In-One_Kit_v1.1\Data>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)... OKAY [ 6.507s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 8.020s
No matter how often I attempt it. Redownloaded the zip to make sure it is not corrupt...
Any pointer?
Ah, damn, because I followed the instructions to the end despite the HBOOT not flashing I can also now not access recovery anymore. It seems the new version of recovery was properly flashed, but as it relies on higher HBOOT I can't get into it anymore. It is still in HBOOT 1.03.
Can anyone help me to get this phone ready for Cyanogenmod?
Click to expand...
Click to collapse
Get s-off change your cid to HTC__001 as shown above and run this ruu, then follow the instructions above
urlyisis said:
I was able to load the hboot, but now the bootloader is locked again and I can't flash the recovery.
FAILED (remote: not allowed)
Click to expand...
Click to collapse
It looks like your s-on
UPDATE: I had to unlock the bootloader via the HTC unlock. RESOLVED
dd98 said:
It looks like your s-on
Click to expand...
Click to collapse
Actually, the bootloader shows the following.
***** Tampered ******
Locked
VLE PVT SHIP S-OFF RL
CID-HTC__001
HBOOT-2.16.000
dd98 said:
HBOOT 2.16 Installation guide
Requirements before installing
Back up your files, your SD Card will be WIPED!
Charge your phone to AT LEAST 30%
Your bootloader MUST be unlocked
You NEED to be S-OFF or else it won't work
You need basic knowledge of Fastboot commands
Windows 10/8/7/Vista/XP: You need drivers installed
Windows 8.1: You need drivers installed AND update kb2967917 from Microsoft
Linux: You need "51-android.rules" or "99-android.rules" configured
Mac: Nothing needed that I know of
I am NOT responsible if you break your phone
This guide will be from a Windows point of view
Installation Guide
Download the HBOOT 2.16 firmware file from here: Download from Mega.co.nz
Place it in your adb and fastboot folder. For example C:\Users\(Your Username)\Fastboot
Now open a Command Prompt window and then type in:
Code:
cd C:\(Location of your Fastboot folder)
Now take your phone and connect it to your computer (with USB Debugging ON) and type in:
Code:
adb reboot bootloader
Once you are in the bootloader and it displays "Fastboot USB", type in:
Code:
fastboot oem rebootRUU
Once your computer recognizes your phone type in:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
You will then get an error:
Code:
"FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
Don't worry, this is normal. DO NOT unplug your phone. Simply type in once again:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
Then wait until the Command window says "finished" and type in:
Code:
fastboot reboot-bootloader
Next we need to download TWRP recovery. You can download it from MDMower's website and MAKE SURE to get TWRP for "/data/media storage (HBOOT 2.16.0000)" and TWRP 2.8.0.1 or above.
Now we must go back to the command window with your phone still plugged in displaying "Fastboot USB" on the screen
Then we type:
Code:
cd C:\Users\(Your Username)\Downloads
or if the TWRP Recovery file isn't in the above location just direct it to the folder its stored in
Now we type:
Code:
fastboot flash recovery twrp-2.8.x.x-ville-dm.img
just replace the "x" with the numbers on the file. e.g. - 2.8.0.1
Once it flashed successfully press the power button and use the volume buttons to scroll down to recovery and to boot into it, simply press the power button
Now go into "Mounts" and select Enable MTP if it isn't already.
Now copy a ROM of your choice (That supports HBOOT 2.16) and flash it. If MTP doesn't work, simply sideload the ROM
That's it, now you just reboot after installing your ROM.
Hope this helps anybody having difficulty with HBOOT 2.16
Click to expand...
Click to collapse
Whatever which recover i choose, my internal storage was always 48mb, i can not push rom, can not sideload rom,
ad346544521 said:
Whatever which recover i choose, my internal storage was always 48mb, i can not push rom, can not sideload rom,
Click to expand...
Click to collapse
You need the hboot 2.16 specific recovery, you can download it here
Never mind, I found what I needed...
Hi, do you have the firmware for t-mobile to downgrade to 2.15? I tried https://mega.co.nz/#!s54F3YqK!QrNjMlieIG65jsaGWS8eXDdLc5FcYM7IEmqTk_pHbFA but doesnt work. I think because is not for tmobile. I cant downloade the full RUU because the download always fails and my internet is so slow.
EDIT: I dont need it anymore, a friend download the file for me. Just a question. in hboot 2.16, gave me more space for my data, i like that, there is no way to make old roms to work on hboot 2.16?
Cannot get this method to work. I'm unlocked and S-OFF. But whenever I try to flash the firmware*.zip I get the message
FAILED (remote: not allowed)
I'm about ready to give up on HBoot 2.16.
confused on twrp for hboot 2.16
Hi thanks a lot for this very clear tuto that help me successfully upgrade to hboot 2.16 without any error issue. everything followed attentively and step by step .
However i am a littlee confused at the step bellow.
When i reached the download section of specified url , concerning TWRP , there is only twrp 2.7 concerning hboot 2.16
But in the tuto you talk about twrp 2.8.. or above. So please can you clarify me on this ?
Thanks
dd98 said:
HBOOT 2.16 Installation guide
[*]Next we need to download TWRP recovery. You can download it from ......and MAKE SURE to get TWRP for "/data/media storage (HBOOT 2.16.0000)" and TWRP 2.8.0.1 or above.
Click to expand...
Click to collapse
delacosta4526 said:
Hi thanks a lot for this very clear tuto that help me successfully upgrade to hboot 2.16 without any error issue. everything followed attentively and step by step .
However i am a littlee confused at the step bellow.
When i reached the download section of specified url , concerning TWRP , there is only twrp 2.7 concerning hboot 2.16
But in the tuto you talk about twrp 2.8.. or above. So please can you clarify me on this ?
Thanks
Click to expand...
Click to collapse
Sorry, this is an old tutorial. Go to this link, download the latest file and flash it in fastboot mode by typing: fastboot flash recovery twrp-2.8.x.x.img (or whatever the file name is)
thanks..but
dd98 said:
Sorry, this is an old tutorial. Go to link, download the latest file and flash it in fastboot mode by typing: fastboot flash recovery twrp-2.8.x.x.img (or whatever the file name is)
Click to expand...
Click to collapse
thanks that is what i did.
But i though this would have help fix wifi, bluetooth not working since stock rom before i flash with "LIBERTY ROM - The Sixth Element" (that did not fix the problem)
Did you anything that can help ? My phone is Htc one s (actually : hboot 2.16 , TWRP 2.8.0.5, radio 1.20, unlocked, s-off, rooted, and with LIBERTY ROM - The Sixth Element" .
delacosta4526 said:
thanks that is what i did.
But i though this would have help fix wifi, bluetooth not working since stock rom before i flash with "LIBERTY ROM - The Sixth Element" (that did not fix the problem)
Did you anything that can help ? My phone is Htc one s (actually : hboot 2.16 , TWRP 2.8.0.5, radio 1.20, unlocked, s-off, rooted, and with LIBERTY ROM - The Sixth Element" .
Click to expand...
Click to collapse
No the recovery version will NEVER affect anything that does/doesn't work on the rom. Since you are using Liberty rom, make sure you are using the 4.4.2 version because the 4.4.3 version is very buggy
of course
dd98 said:
No the recovery version will NEVER affect anything that does/doesn't work on the rom. Since you are using Liberty rom, make sure you are using the 4.4.2 version because the 4.4.3 version is very buggy
Click to expand...
Click to collapse
Yes surely . i am using 4.4.2. I have carefully read i lot of things including that.
Thanks
Guys can someone please help me?
I am on Windows 10 desperately trying to find a solution on the ''WAITING DEVICE'' response after I type
fastboot oem rebootRUU
I have tried installing a bunch of drivers , driver updates on device manager etc with no luck.
The device is just not responding.
Thanks
File Offline
Unfortunately the HBoot 2.16 file is offline. Can someone please reupload it?
Thank you!