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.
Related
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 sitting here a Samsun Nexus S from Fido in Canada. From what I can tell that makes it the 9020a.
It belongs to a friend and he really wanted CM7 on it after seeing CM7 on my Nexus One.
I helped him root and unlock the phone along with installing ClockWork Recovery.
I left before getting around to installing the ROM. He downloaded it through the ROM manager. After the phone restarted though he was just presented with the white Google logo and it never moved on.
I am trying to help fix this, but he wiped the sdcard and the backup that was done when ROM Manager did a backup.
Here is the problem though, I have installed about 5 or 6 different recovery ROM's trying to get this to work, even more ROM's themselves.
I have tried combinations of ROM's and recovery ROM's.
All of them end with me staring at a white Google logo.
I have access to fastboot and the recovery ROM still. So I decided to just go back to stock by flashing the partitions from fastboot. Some of them will flash, but others won't. I can flash the cache, but I can't flash the recovery, data, or system partitions. When I try I get
sending 'recovery' (8192 KB).
OKAY [ 1.029s]
writing 'recovery'...
FAILED (remote: Write Fail)
or this for Data
FAILED (remote: Unkown Partition)
or this for System
FAILED (remote: Write Fail)
Any and all help would be greatly appreciated. Right now the phone is basically bricked. I am going to sleep but will check back in the morning. If I left some information out please let me know.
Did you unlock the bootloader?
fastboot oem unlock
Then follow the on screen instructions. I had to do that to flash certain *.imgs. I think it has to do with the security checks....
Sent from my Nexus S using XDA Premium App
Does the white Google logo have a padlock symbol at the bottom of the screen? If not then the bootloader is locked. What root method did you use?
Sent from my Nexus S 4G using xda premium
And also what were the commands you used to flash the images.
Sorry for the late reply. Some stuff at work blew up and kept me out late.
atrixboy:
Yes, the bootloader is unlocked.
Rem3Dy:
Yes, there is a pad lock at the bottom of the screen.
suksit:
The commands run originally was just to unlock the phone (fastboot.exe oem unlock). The phone was then rooted and the OS was launched. Once in the OS RomManager was downloaded and installed. Through RomManager clockwork recovery was installed. After that CM7 was selected as the Rom to install. The phone rebooted, did its thing in recovery, then booted to this black screen with white Google logo which I have yet to get passed.
Since then though I have flashed several different recovery images trying to get this to work, right now the recovery is: CWM-based Recovery v4.0.1.4
If I install a Rom from zip through the recovery it says it was OK, but I still get the white logo and nothing else on boot.
I have been trying to just flash boot and system images at this point and am having no luck.
When I try the following:
C:\1>fastboot.exe flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 1.032s]
writing 'boot'...
FAILED (remote: Write Fail)
finished. total time: 1.039s
C:\1>fastboot.exe flash system system.img
sending 'system' (151459 KB)...
OKAY [ 19.073s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 19.078s
C:\1>fastboot.exe flash data data.img
sending 'data' (4 KB)...
OKAY [ 0.002s]
writing 'data'...
FAILED (remote: Unknown Partition)
finished. total time: 0.032s
If I boot the recovery and go into adb and try and mount the same 3 partitions I get the following:
mount /system - works fine
mount /boot - mount: can't find /boot in /etc/fstab
mount /data - this one runs for like 5 minutes and then fails with the following error: mounting /dev/block/platform/s3c-sdhci.0/by-name/userdata on /data failed
I just realized that there is some more information on the screen of the device while in fastboot and I try this. When I try "fasboot.exe flash boot boot.img" I get the following on screen:
Exceed blocks 0x00000020 > 0x0000001e (The exact number of zeros may be wrong, hard counting them at that size)
FASTBOOT STATUS - FAILWrite Fail
Fastboot also indicates at the top of the screen: FASTBOOT MODE - NO BOOT OR RECOVERY IMG
I am able to get into the recovery though...
Not sure what other information to include.
I have run out of ideas. Does anyone know where else could I go and get help with this?
are you flashing *.img files in cwm or bootloader mode?
In fastboot I am flashing .img files, from CWM I am trying to flash .zip. I downloaded a nandroid backup and tried restoring that from within CWM with no luck.
try formatting all memory locations except sd card in "mounts & storage" and fix permissions and then flash img files.
What exactly do you mean by "fix permissions" ?
Edit: Stupid question, found it under advanced.
So I formatted each of the partitions, did the fix permissions option, and then booted back into the bootloader and tried to flash the system.img file with fastboot. It failed.
C:\1>fastboot.exe flash system system.img
< waiting for device >
sending 'system' (151459 KB)...
OKAY [ 19.001s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 19.006s
Thank you in advance for trying to help, I really appreciate it.
Edit: I just realized at the bottom of the bootloader after trying to flash the system.img file it now says in bold orange text:
Invalid Magic Code! 0x00000003
When in CWM recovery, can you mount each of those partitions, or does it spit out an error? (mount /sdcard && mount /system && mount /data etc...)
On the subject of the model version, the model number should be on the sticker under the battery. Mine says "GT-i9020a" and in the bootloader it says my carrier is AT&T, even though my phone is from Telus.
did you try this? http://forum.xda-developers.com/showthread.php?t=884093
litanyoffail said:
When in CWM recovery, can you mount each of those partitions, or does it spit out an error? (mount /sdcard && mount /system && mount /data etc...)
On the subject of the model version, the model number should be on the sticker under the battery. Mine says "GT-i9020a" and in the bootloader it says my carrier is AT&T, even though my phone is from Telus.
Click to expand...
Click to collapse
I can mount:
/sdcard
/system
/cache
When I try and mount /data it takes 15 minutes and then fails. Says: Error mounting /data!
The model is most definitively i9020a, I just checked under the battery. Thanks for telling me where that is.
milesman said:
did you try this? http://forum.xda-developers.com/showthread.php?t=884093
Click to expand...
Click to collapse
I did, but I am trying it again now.
So, I tried that Nandroid backup again, and it says MD5 mismatch. I checked the MD5's myself and they match. The ones listed in the MD5 file, and the files match.
I tried flashing the *.img files from fastboot, and get that failed to write message I posted earlier.
install this in cwm su-2.3.6.1-ef-signed.zip
let me know if this lets you mount etc...
milesman said:
install this in cwm su-2.3.6.1-ef-signed.zip
let me know if this lets you mount etc...
Click to expand...
Click to collapse
Did this, still having the same problems.
Possible the bootloader unlock corrupted guys? Sounds to me like either a bootloader error else the nand may have died. Unlikely but possible. I read somewhere about loading a custom bootloader to the Nexus S. Maybe try looking for that, I know it was here on XDA, only place to get good help IMHO. The orange error codes are generally related to a corrupt bootloader/bad nand chip to the best of knowledge, feel free to correct me if I'm wrong.
Sent from my Nexus S using xda premium
If the nand was shot, data, SD and system wouldn't mount either. I had a busted nand on my nexus last month, had to send it in.
Seems like the bootloader is unlocked, but acting as if it is locked. Do fastboot devices, make sure the numbers match on your screen and your command prompt.
Something I noticed: If the fastboot flash recovery is failing, how did you get the multiple recoveries on prior to posting here?
Sent from my Nexus S
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?
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
here's what i did so far
factory reset on clockworkmod
phone will no longer boot
find out only solution is to flash stock ruu through fastboot
right ruu for my hboot and carrier not available
i have roger001 and hboot 1.13 bought from canada fido
i find out i can supercid to install ruu's from other countries
supercid procedure requires me to gain access to sd
i cannot access it (usb debugging not enabled im guessing, a i cant enable it because phone stuck in bootloop)
so now i cannot supercid
so i can not install any ruu without errors
i somehow broke clockworkmod cant get into it either
i need a way to install an ruu by just using the adp fastboot usb
help.... im kind of desperate
Seriously? Not even a single reply? Does that mean that there's absolutely nothing I can do? Give me SOME feedback please.
Can't you just fastboot flash a recovery, boot said recovery, mount usb storage in recovery and put a rom, and then flash that rom? Probably should clear data and system before flashing...
Sent from my HTC One S using xda app
lampel said:
Can't you just fastboot flash a recovery, boot said recovery, mount usb storage in recovery and put a rom, and then flash that rom? Probably should clear data and system before flashing...
Sent from my HTC One S using xda app
Click to expand...
Click to collapse
what recovery should i fastboot? i'm looking for something other than CWM
I use twrp. Never had an issue with it.
Sent from my HTC One S using xda app
lampel said:
I use twrp. Never had an issue with it.
Sent from my HTC One S using xda app
Click to expand...
Click to collapse
hmm it won't let me....
when i type into command and prompt "fastboot flash recovery twrp.img"
i get the following:
sending 'recovery' (8288 KB)... OKAY [ 1.474s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.158s
it won't even let me flash twrp
In your picture your bootloader is relocked. Did you re-unlock it?
sushiemaker said:
hmm it won't let me....
when i type into command and prompt "fastboot flash recovery twrp.img"
i get the following:
sending 'recovery' (8288 KB)... OKAY [ 1.474s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.158s
it won't even let me flash twrp
Click to expand...
Click to collapse
lampel said:
In your picture your bootloader is relocked. Did you re-unlock it?
Click to expand...
Click to collapse
wow, thank you so much, I forgot to re-unlock it...
now I have managed to get twrp installed, and I'm at the mounting stage, but my computer gives me the following message:
"You need to format this disk before you can use it. Do you want to format it?" and there is a "Format" or "Cancel" button I can press.
Should I click Format? I didn't want to act too hasty.
edit: ok i formatted it, now im in the process of finding a rom, any suggestions?
Trickdroid and energy are both great if you like sense roms.
Sent from my HTC One S using xda app