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,
I want to change the first screen when I turn on my htc magic(HBOOT-1.33.0008, PVT 32A).
But when I using this command on my PC (Phone have entered fastboot mode):
---------------------------------------
fastboot flash splash1 mysplash.rgb565
---------------------------------------
I got a error, it say:
------------------------
sending 'splash1' (300 KB)... OKAY
writing 'splash1'... INFOsignature checking...
FAILED (remote: signature verify fail)
------------------------
I don't want to flash a modded SPL, so, is there a way to flash the splash1 partition by Recovery mode?
Thanks in advance!
You need an engeneering SPL or HBOOT to do this.
http://forum.xda-developers.com/showthread.php?t=529019
I have the same problem
I thought I had the eng SPL uploaded but stll the same error message. Could it be that im following the G1 method and its different to the G2/magic/sapphire?
HBOOT-1.33.0008 is not a modded or an engenieering SPL.
Cheesebaron said:
HBOOT-1.33.0008 is not a modded or an engenieering SPL.
Click to expand...
Click to collapse
#3 is not me
I know the HBOOT-1.33.0008 is a original SPL. I'd like to know if I can flash the splash1 partition by Recovery mode.
I think you can't apply any update.zip (like roms, recoveries...) unless you change your SPL but I'm not sure.
DBeCe said:
I think you can't apply any update.zip (like roms, recoveries...) unless you change your SPL but I'm not sure.
Click to expand...
Click to collapse
No, you can apply updates and flash recoveries without flashing SPL. You need the updated SPL to flash a nandroid backup, or presumably, the splash1 screen.
bcrook said:
No, you can apply updates and flash recoveries without flashing SPL. You need the updated SPL to flash a nandroid backup, or presumably, the splash1 screen.
Click to expand...
Click to collapse
You can use the pimped out recovery image to flash a nandroid backup, and just start the pimped out recovery image via fastboot. No flashing of SPL or recovery needed for restoring nandroid.
I have searched far and near to flash my splash screen and i get the same answer
Code:
fastboot devices
you should see your phone listed under the command you just typed. After that type the next command to flash the splash image
Code:
fastboot flash splash1 splash1.nb
Then you should see that it was successful and rebbot the phone and preview your new image by typing
Code:
fastboot reboot
thing is i am getting this error
c:\android\tools>fastboot flash splash1 evosplash.bmp
sending 'splash1' (1125 KB)... OKAY [ 0.477s]
writing 'splash1'... FAILED (remote: not allowed)
finished. total time: 0.478s
what am i doing wrong????
gslogen said:
what am i doing wrong????
Click to expand...
Click to collapse
Search is your friend. Try "white black evo splash" and "eng bootloader unrevoked".
Basically, you have to have/flash the .73 hboot to modify your splash screen, those threads will tell you how.
petemills8 said:
Search is your friend. Try "white black evo splash" and "eng bootloader unrevoked".
Basically, you have to have/flash the .73 hboot to modify your splash screen, those threads will tell you how.
Click to expand...
Click to collapse
ok ill do a little more searching thanks
ok, i read both of those, and now my phone shows up under the fastboot devices. however mine still reads failed <remote: not allowed>
HALP!
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
So i dont know what happend, i succesfully make my hox S-OFF, use the phone and everything was working fine, then a try to downgrade my bootloader with Jet but everything went wrong from there, the process didnt finish, i try to relocked my bootloader to install the 2.20 RUU thinking it would fix it but know the RUU procesos finishes with a 131 error because my cid is diferent, this is what i have:
******tampered*****
******relocked******
jewel pvt ship s-off rl
cid-spcs_001
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendsp-v29.1.0.45.0622
emmc-boot
I can put fastboot commands but its shows FAILED (remote: not allowed), i cant go into recovery, also on jet i cant go into QHSUSB_DLOAD anymore.
You really didn't need to downgrade being you were s-off.............
Sent from my HTC One X using Tapatalk 2
Did you try this command to unbrick?: sudo ./jet -u
Edit: hmm just noticed your cid changed to stock. Sorry idk where to go from there
Sent from my HTC One X using xda premium
Yes i did try the ./jet -u command but i cant get in to QHSUSB_DLOAD anymore that is the stock cid for the one x ? if thats the case maybe i can run de 1.85 RUU?
pikul said:
i cant get in to QHSUSB_DLOAD anymore
Click to expand...
Click to collapse
Did you try the hardware key way? Same as bootloader, but power and vol +
Practically gave myself a heart attack yesterday. Someone here was having trouble getting into bootloader, and mentioned power and vol +. I couldn't remember what that did (knew it wasn't bootloader) so I did it, and put the phone in Qualcomm download mode!
I was able to get back to bootloader, recovery, and reflashed the ROM that happened to be on my phone.
No. What I meant was your cid isn't supercid anymore. And I wouldn't use that RUU since your hboot is 1.14; wait till someone more experienced helps you out
Sent from my HTC One X using xda premium
redpoint73 said:
Did you try the hardware key way? Same as bootloader, but power and vol +
Practically gave myself a heart attack yesterday. Someone here was having trouble getting into bootloader, and mentioned power and vol +. I couldn't remember what that did (knew it wasn't bootloader) so I did it, and put the phone in Qualcomm download mode!
I was able to get back to bootloader, recovery, and reflashed the ROM that happened to be on my phone.
Click to expand...
Click to collapse
I guess i could run the ./jet -u command and press those keys, its that what you mean?
panda_mode said:
No. What I meant was your cid isn't supercid anymore. And I wouldn't use that RUU since your hboot is 1.14; wait till someone more experienced helps you out
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
ooooooooo :good: at least i can get into bootloader and put fastboot commands, i guess thats something
pikul said:
I guess i could run the ./jet -u command and press those keys, its that what you mean?
Click to expand...
Click to collapse
I've actually never used JET, and not quite sure how it works.
But power and vol + will put the phone in QHSUSB_DLOAD in most situations (nothing to do with JET), if that is all you are trying to do. Similar to how power and vol - boots into bootloader. Just curious if it would still worked in your "bricked" condition.
Are you able to get into fastboot? If so just use stock RUU to get back to stock,
thats the thing, i can get in to fastboot, try to run the 2.20 RUU starts and maybe 1 minute later it fails, and gives a ERROR [131] i google it and it seems to be because the cid its not the correct one anyone knows if there its a way to bypass the cid verification?
pikul said:
thats the thing, i can get in to fastboot, try to run the 2.20 RUU starts and maybe 1 minute later it fails, and gives a ERROR [131] i google it and it seems to be because the cid its not the correct one anyone knows if there its a way to bypass the cid verification?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/HTC_One_X
Try this thread. I think there is a way to use the stock recovery and the cid you used to unlock it. May give you some ideas.
AT&T HTC OneX
Andriod 4.1.1
ViperXL
i check all of them, but i just cant get to unlock my bootloader again or flash a different cid, not even flash the recovery, y guess its because i relock my bootloader
pikul said:
i check all of them, but i just cant get to unlock my bootloader again or flash a different cid, not even flash the recovery, y guess its because i relock my bootloader
Click to expand...
Click to collapse
Have you tried to get a new identifier token and unlock the phone to get TWRP again?
http://onexroot.com/one-x-root/how-to-unlock-bootloader-and-root-att-htc-one-xhtc-one-xl/
AT&T HTC OneX
Android 4.1.1
ViperXL
is it posible to get it in bootloader mode? cause thats all i can access :/
Everytime i try to flash a file in fastboot it shows FAILED (remote: not allowed)
pikul said:
is it posible to get it in bootloader mode? cause thats all i can access :/
Click to expand...
Click to collapse
download a ROM.. put it in your fastboot folder,
boot into fastboot and try this
fastboot flash zip name_of_rom.zip <-- this works with HTC RUUs, may work with an actual ROM.. Use at your own risk, I have never tried it with a custom ROM.
mirGantrophy said:
download a ROM.. put it in your fastboot folder,
boot into fastboot and try this
fastboot flash zip name_of_rom.zip <-- this works with HTC RUUs, may work with an actual ROM.. Use at your own risk, I have never tried it with a custom ROM.
Click to expand...
Click to collapse
I took the .img files from the rom.zip that you get from the RUU, but it doesnt work.
C:\Programas\Fastboot>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.966s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.000s
C:\Programas\Fastboot>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.309s
pikul said:
I took the .img files from the rom.zip that you get from the RUU, but it doesnt work.
C:\Programas\Fastboot>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.966s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.000s
C:\Programas\Fastboot>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.309s
Click to expand...
Click to collapse
If you have the RUU.zip, do this then:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip rom.zip
see if that works..
This is what i get:
C:\Programas\Fastboot>fastboot flash zip rom.zip
sending 'zip' (576544 KB)...
OKAY [ 24.368s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 26.975s
this sucks, i have to go to work and i dont have another cellphone :/
pikul said:
this sucks, i have to go to work and i dont have another cellphone :/
Click to expand...
Click to collapse
You can try to find the cidnum for the htc onexl and see if you can trick it by editing android-info.txt file to match cid num.
Example:
edited android-info file
modelid: PG3213000
cidnum: KT___901
cidnum: HTC__004(this edited file only)
mainver: 2.32.1010.1
hbootpreupdate:13
boot again into fastboot
AT&T HTC OneXL
Android 4.1.1
ViperXL