HTC G1 Soft Brick can access bootloader screen - G1 Q&A, Help & Troubleshooting

Hey guys I attempted to breathe some life into my old HTC G1 and after failed attempts I was successful in installing the CM6 but this runs Froyo and I couldn't get certain apps to work, more recent apps just would not install so being new to Android I tried installing the CM7 unofficial but that failed giving me a STATUS 7 so I assumed I needed another kernel so I tried doing that but still STATUS 7 so I installed spl saphire signed and then that went through but phone got soft bricked so now I know I can unbrick my device because I can still access FASTBOOT and I can flash a recovery image and I tried that but also my home button gives trouble so I have to fiddle with it to get it to work and that's the only way I know how to get into recovery. Is there another way for me to get into recovery so I can whipe and flash stuff over as fresh?
BOOTLOADER INFO
DREAM PVT 32B ENG S- OFF
HBOOT-1.33.2003 (DREA10000)
CPLD-4
RADIO-2.22.19.261
Marc 26 2009,23:25:49

adb reboot recovery, but need to be in os for that
Just erase partitions and flash ROM through fastboot
fastboot erase system -w
fastboot flash update ROM.zip
fastboot reboot
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
adb reboot recovery, but need to be in os for that
Just erase partitions and flash ROM through fastboot
fastboot erase system -w
fastboot flash update ROM.zip
fastboot reboot
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I did a little searching and found the library of "bricked" phones where I tried this solution
As I said I did it.
FYI, I write this msg for somebody has same problem.
I did "flash_image recovery /sdcard/cm-recovery-1.2.img".
After the reboot, it stucked on the second boot screen, it looped forever and ever and never stopped.
So I Alt+w and then Alt+s but it said can't find update.zip
But it was there.
And I tried some of the builds on this fourm.
I got some other messages, but I don't remember, sorry.
Anyway I coudn't fix it with the way.
I also tried to use another SD card.but it also didn't work.
unfortunatry, I didn't have nandroid backup, cos I didn't care much about the backup.
Then I got signed-dream_devphone_userdebug-img-148830.zip from ****
and I did like this.
C:\bin>fastboot update signed-dream_devphone_userdebug-img-148830.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: XXXXXXXXXXX
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2005'.
Update requires '1.33.2004' or '1.33.0004' or '0.95.3000' or '0.95.0000'.
Then I got this error...
Then I unzipped the file, and I did like this.
C:\bin>fastboot flash boot boot.img
sending 'boot' (1604 KB)... OKAY
writing 'boot'... OKAY
C:\bin>fastboot flash system system.img
sending 'system' (54823 KB)... OKAY
writing 'system'... OKAY
C:\bin>fastboot flash userdata userdata.img
sending 'userdata' (2 KB)... OKAY
writing 'userdata'... OKAY
C:\bin>fastboot reboot
rebooting...
Then I got G1 back!
I hope it can help somebody.
Cheers!
So I got the phone to work and it retained the same bootloader and I got recovery back but now I'm trying to install a stable Gingerbread like EzGingerbread and I still get status 7

Change to amonra 1.7 recovery
Change to 2708 radio
Change to .13d bootloader
Now go back making to recovery and flash ezginigerbread
Now you will be happy
Status 7 can mean a few different thing, but for the most part its incompatibility. If you follow the above you will meet all requirements for the "newer" roms
Sent from my Nexus 7 using Tapatalk 2

demkantor said:
Change to amonra 1.7 recovery
Change to 2708 radio
Change to .13d bootloader
Now go back making to recovery and flash ezginigerbread
Now you will be happy
Status 7 can mean a few different thing, but for the most part its incompatibility. If you follow the above you will meet all requirements for the "newer" roms
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I appreciate the help. These files are kind of tough to find though, I'm searching still
I believe I found them here on XDA so I assume I'm flashing with recovery first the radio then bootloader.

Best to use fastboot to flash, recovery, then radio, then SPL
Look for ezterry's 2708+ update thread in the dev section
Sent from my Nexus 7 using Tapatalk 2

demkantor said:
Best to use fastboot to flash, recovery, then radio, then SPL
Look for ezterry's 2708+ update thread in the dev section
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I followed your instructions and I was successful. New life is now in my old HTC G1 Thank you for your patience.

that was easy bro,
RenaldoTT said:
Hey guys I attempted to breathe some life into my old HTC G1 and after failed attempts I was successful in installing the CM6 but this runs Froyo and I couldn't get certain apps to work, more recent apps just would not install so being new to Android I tried installing the CM7 unofficial but that failed giving me a STATUS 7 so I assumed I needed another kernel so I tried doing that but still STATUS 7 so I installed spl saphire signed and then that went through but phone got soft bricked so now I know I can unbrick my device because I can still access FASTBOOT and I can flash a recovery image and I tried that but also my home button gives trouble so I have to fiddle with it to get it to work and that's the only way I know how to get into recovery. Is there another way for me to get into recovery so I can whipe and flash stuff over as fresh?
BOOTLOADER INFO
DREAM PVT 32B ENG S- OFF
HBOOT-1.33.2003 (DREA10000)
CPLD-4
RADIO-2.22.19.261
Marc 26 2009,23:25:49
Click to expand...
Click to collapse
If you want you can unbrick your devices by downgrading it to android 1.0 then apply the official update for the G1 from Google. It will bring you back to the stock HTC G1 1.6 but you can repeat the rooting procedure. That's what I'm doing before, specially if I flashed faulty roms or messing up with the radio and spl combos. Hope that help you.

My sd card does not read.
Then what???
Sent from my SGH-M919 using xda app-developers app

Either its not named properly, not on root of SD, SD isn't formatted to fat32, or sdcard or sdtray is bad
Sent from my Nexus 4 using XDA Premium 4 mobile app

please describe how did you>>> flash_image recovery /sdcard/cm-recovery-1.2.img
RenaldoTT said:
I did a little searching and found the library of "bricked" phones where I tried this solution
As I said I did it.
FYI, I write this msg for somebody has same problem.
I did "flash_image recovery /sdcard/cm-recovery-1.2.img".
After the reboot, it stucked on the second boot screen, it looped forever and ever and never stopped.
So I Alt+w and then Alt+s but it said can't find update.zip
But it was there.
And I tried some of the builds on this fourm.
I got some other messages, but I don't remember, sorry.
Anyway I coudn't fix it with the way.
I also tried to use another SD card.but it also didn't work.
unfortunatry, I didn't have nandroid backup, cos I didn't care much about the backup.
Then I got signed-dream_devphone_userdebug-img-148830.zip from ****
and I did like this.
C:\bin>fastboot update signed-dream_devphone_userdebug-img-148830.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: XXXXXXXXXXX
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2005'.
Update requires '1.33.2004' or '1.33.0004' or '0.95.3000' or '0.95.0000'.
Then I got this error...
Then I unzipped the file, and I did like this.
C:\bin>fastboot flash boot boot.img
sending 'boot' (1604 KB)... OKAY
writing 'boot'... OKAY
C:\bin>fastboot flash system system.img
sending 'system' (54823 KB)... OKAY
writing 'system'... OKAY
C:\bin>fastboot flash userdata userdata.img
sending 'userdata' (2 KB)... OKAY
writing 'userdata'... OKAY
C:\bin>fastboot reboot
rebooting...
Then I got G1 back!
I hope it can help somebody.
Cheers!
So I got the phone to work and it retained the same bootloader and I got recovery back but now I'm trying to install a stable Gingerbread like EzGingerbread and I still get status 7
Click to expand...
Click to collapse
I have the same problem you had. please describe how did you>>>>> flash_image recovery /sdcard/cm-recovery-1.2.img

This would be putting a recovery on root of SD card and naming it cm-recovery-1.2.img
Then booting into the os and running the command in a terminal emulator, that's it
This will only work if your ROM supports the flash_image binary but more than likely yours does.
If you need further help, please explain your problem fully and give all info about your phone
Sent from my Nexus 4 using XDA Premium 4 mobile app

Related

[Q] Flashing the latest and brightest

Hello guys,
I've bought my G1 a couple years back, it's still a functioning machine (although becoming a bit of a heavyweight in the smartphone-division), but I want it to do a little more than what it's capable of now. In other words: I want to update to a newer android version.
I'm still running a rooted cupcake.
In order to update to the latest ROMs, I need a new radio and SPL.
Problem is: I can't seem to flash them through fastboot.
This is the error I keep bumping into:
c:\androidsdk\tools>fastboot flash radio radio-2.22.27.08.img
sending 'radio' (21120 KB)... OKAY [ 6.333s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.661s
Click to expand...
Click to collapse
My current fastboot screen reads:
DREAM PVT 32B SHIP S-ON
HBOOT-1.38.0000 (DREA20000)
CPLD-4
RADIO-2.22.16.19
Feb 28 2009, 18:40:30
I had a lot of trouble trying to flash a custom recovery as well, but was finally able to pull that one off (installed the recovery app, flashed cyagonmod custom recovery and from inside that one I was able to flash RA's 1.7 custom recovery).
So now I'm running RA's custom recovery. I've been pulling my hair over this signing problem for two days now, the few threads I seem to find about it on this forum don't bring me any further either...
My question is: how do I flash my new radio? Can I flash them from recovery?
Many thanks in advance!
The Radio I'm trying to flash is:
http://forum.xda-developers.com/showthread.php?t=831139
I had this issue as well.
My fix was re-rooting (hence both of our phones were S=ON and not S=OFF), installing the Engineering SPL, then following the fastboot commands given in the 2708 kernel installation guide you linked us to.
I believe that was my issue, but I did do the whole process of reverting back to the RC29 version, then doing the normal process of rooting and installing the recovery screen, bootloader, etc.
I believe that'll fix it, and if not, just say so and we'll figure it out!
Just to make sure everything is going on correctly,
Root: http://forum.xda-developers.com/showthread.php?t=442480
SPL: http://forum.xda-developers.com/showthread.php?t=455860
Thank you, that was a very useful suggestion!
I flashed HardSPL through recovery and then tried fastboot flashing the radio and hboot again.
This time I bumped into the following error:
c:\androidsdk\tools>fastboot flash radio radio-2.22.27.08.img
sending 'radio' (21120 KB)... OKAY [ 7.954s]
writing 'radio'... FAILED (remote: partition does not exist)
finished. total time: 7.961s
Click to expand...
Click to collapse
Does this mean I need to format my SD card through recovery first?
Sorry for the few day delay, been busy.
I don't think that you need to wipe your SD card.
The HardSPL is 10.95.3000. You must first flash the the 1.33.2003 SPL.
Make sure it is the 2003 and not 2005, because I do not think that the 2005 is compatible.
Here,
Download this
http://www.mediafire.com/?jmt4nnzttnm
hboot: 1.33.2003 - SPL both in update.zip and img format
hboot: 1.33.2005 - in img format
radio: 2_22_23_02 in img format
1. I'd recommend that you flash back down to RC29 (just to be sure everything is done correctly),
2. Throw all the files included in the g1boot.zip onto your sdcard.
3. Root as you normally would, but use Amon Ra 1.7.0 in stead 1.5.2.
http://files.androidspin.com/downlo...OVERY/&file=recovery-RA-dream-v1.7.0-cyan.img
4. Flash the spl_1_33_2003.zip from the recovery screen.
5. After that is complete, your phone will reboot.
6. Then you want to fastboot flash radio radio-2_22_23_02.img.
7. If that works, which it should if everything was done properly, you will fastboot flash hboot hboot-1_33_2005.img.
8. If everything goes as planned, you should be safe to flash your ROM now.
And just for the record, I believe I actually did mine of the Engineering SPL. If those steps don't work, I'd recommend trying that instead.
Keep me posted on how it works.
This worked like a charm! Thanks for all the help. I'm now on the radio, hboot & ROM I wanted to be
I tried doing the engineering SPL first. That didn't work. Then I went for the 2003 version, through that I was able to fastboot flash the radio and hboot. Then in recovery I first partioned my SD card and then flashed the Biffmod 2.1 ROM.
Testing it out right now Really slow first boot though, not sure if this will be fast enough.
First boots always take a while.
Hows it working for you?
Sent from my HTC Glacier using XDA App

[Q] Unable to update hboot

HI
Im trying to upgrade my nexus to gingerbread stock according to the guids in the dev section
I understand that u need hboot 35 in order to do so.
im currently using hboot 0.33.0012
and stock rooted froyo 2.2.2 with unlocked bootloader
as i enter fastboot on my phone and try the command
fastboot flash hboot hboot.img
I get the following output
sending 'hboot' (512 KB)... OKAY [ 0.085s]
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 0.279s
does anyone know why do I get "remote : not allowed"?
thanks!
edit: can I skip this step or do I must upgrade hboot?
and can I upgrade it with a zip through the latest amon ra recovery?
edit2: I found an update zip containing only the hboot ver 35 and when I try to flash it
it says its unsigned and installation aborted...
should I try cancelling sign checking through recovery or is it too risky?
come one guys I really need some help here...
I have the same issue, never been able to solve it.
You can find a zip to the .37 hboot, I think in one of the GB 2.3.3 threads. (IIRC, it was craigacgomez's) If you are getting an unsigned error, turn off the signature verification in your recovery. I used the same zip, and all was fine. If you can't find the zip file, let me know. I most likely still have it.
UPDATE: here is the link craigacgomez provided for the flashable, zip hboot. http://android.clients.google.com/packages/ota/passion/d6096cac5e9f.signed-hboot-0.35.0017.zip
If it still fails, turn off signature verification.
Are you sure your bootloader is unlocked? People usually get those errors when it is locked, or they are trying to flash a .zip file instead of an.img file.
Using recovery is fine to flash HBOOT. Link to the .zip is in my signature.
Solved
I managed to solve the problem by finding a flash zip file. like mentioned above, before the comment was written.
and I took off the signature check myself, without knowing that itll go through fine
except from that the radio upgrade, and gingerbread installation went fine, finally I have 2.3.3 on my phone!!
thnks a lot anyway. I still wonder what is the cause for this error, as my bootloader is unlocked for sure, and I even tried
fastboot oem unlock
one more to be sure (which failed, as it stated that it is already unlocked)
I was getting the same error trying to flash to the .37 hboot from fastboot. My bootloader has been unlocked since I took the phone out of the box.
You guys were at the fastboot screen, right?
Sent from my Nexus One using XDA Premium App
Yea, I have used fastboot a few thousand times. Was found by fastboot devices. Just gave errors every time I tried to flash it. The zip worked fine though. Never had any problems flashing anything else through fastboot.
Yeah, I figured I was grasping at straws, but thought I'd ask anyway...
Sent from my Nexus One using XDA Premium App

Flashing System : "data length is too large" problem

I have been trying to flash an old GB image from an RUU provided in the Shipped ROMS thread.
I flashed my boot and recovery OK, but flashed system failed somehow. Now, am stuck on HTC logo. When I flash my system image, it gives an error:
sending 'system' (917504 KB)... FAILED (remote: data length is too large)
Please help.
roc_vader said:
I have been trying to flash an old GB image from an RUU provided in the Shipped ROMS thread.
I flashed my boot and recovery OK, but flashed system failed somehow. Now, am stuck on HTC logo. When I flash my system image, it gives an error:
sending 'system' (917504 KB)... FAILED (remote: data length is too large)
Please help.
Click to expand...
Click to collapse
Which recovery and boot did you flash? Also this post should have been created in the general section.
Sent from my HTC PH39100 using XDA
megatronisabeast said:
Which recovery and boot did you flash? Also this post should have been created in the general section.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Sorry for wrong section. Maybe a moderator can move this to General section plz
Also, I flashed the RUU_Holiday_Cingular_US_1.63.502.4 from this http://forum.xda-developers.com/showthread.php?t=1338919 thread
roc_vader said:
Sorry for wrong section. Maybe a moderator can move this to General section plz
Also, I flashed the RUU_Holiday_Cingular_US_1.63.502.4 from this http://forum.xda-developers.com/showthread.php?t=1338919 thread
Click to expand...
Click to collapse
What rom were you coming from? Were you already on gingerbread or on ics?
megatronisabeast said:
What rom were you coming from? Were you already on gingerbread or on ics?
Click to expand...
Click to collapse
No, I had not upgraded to ICS. I was using stock GB with a modified kernel
First thing you shouldve done was relock the bootloader to flash back to stock....hopefully you didnt bork your phone.....IF you can get into hboot relock the bootloader and re run the ruu
WC
http://forum.xda-developers.com/showthread.php?t=1416836
Go to the second post and follow all of the steps. It should get you back to where you need to be.
Guys, I did see that post earlier, but the problem is I cant boot my phone. Am stuck on HTC logo while booting(I mentioned it in my first post). Now, how do I run the RUU? I can get into HBOOT.
Also, fastboot update rom.zip gave following error:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.83.0014
Baseband Version.....: N/A
Serial Number........:
--------------------------------------------
sending 'boot' (3580 KB)... OKAY [ 0.796s]
writing 'boot'... OKAY [ 1.202s]
sending 'recovery' (6438 KB)... OKAY [ 1.312s]
writing 'recovery'... OKAY [ 2.280s]
sending 'system' (917504 KB)... FAILED (remote: data length is too large)
finished. total time: 5.622s
Does the bootloader say locked or unlocked? IF locked connect phone to computer with fastboot enabled and run the ruu. If it says unlocked you have to run fastboot oem lock and see if it will lock....IF it does lock and says relocked then follow " IF locked connect phone to computer with fastboot enabled and run the ruu"
WC
roc_vader said:
Guys, I did see that post earlier, but the problem is I cant boot my phone. Am stuck on HTC logo while booting(I mentioned it in my first post). Now, how do I run the RUU? I can get into HBOOT.
Also, fastboot update rom.zip gave following error:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.83.0014
Baseband Version.....: N/A
Serial Number........:
--------------------------------------------
sending 'boot' (3580 KB)... OKAY [ 0.796s]
writing 'boot'... OKAY [ 1.202s]
sending 'recovery' (6438 KB)... OKAY [ 1.312s]
writing 'recovery'... OKAY [ 2.280s]
sending 'system' (917504 KB)... FAILED (remote: data length is too large)
finished. total time: 5.622s
Click to expand...
Click to collapse
Wild Child said:
Does the bootloader say locked or unlocked? IF locked connect phone to computer with fastboot enabled and run the ruu. If it says unlocked you have to run fastboot oem lock and see if it will lock....IF it does lock and says relocked then follow " IF locked connect phone to computer with fastboot enabled and run the ruu"
WC
Click to expand...
Click to collapse
It was relocked. And the thread you mentioned did not seem to work. But following thing worked:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Anyways, Am on ICS now!!!! Thnx a lot for ur help!!
Glad you are on ics. Thanks for sharing your steps!
Sent from my HTC PH39100 using XDA
The error reason?
Hi,
My BL is unlocked with htcdev.
I have the same when trying to flash with fastboot.
Can someone tell me whats the reason of the error?
Thanks
roc_vader said:
It was relocked. And the thread you mentioned did not seem to work. But following thing worked:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Anyways, Am on ICS now!!!! Thnx a lot for ur help!!
Click to expand...
Click to collapse
Yes Bro you are right it worked for me too happy right now wnjoy buddy live more have a good day .
If some one is still on this problem, I had the issue Where upon boot the device said "Decrption Unsucessful" so i thought i should give it a factory reset which the device also prompts to but can't since the Partitions are Corrupted or just a Partition in my case, So flashed TWRP 3.0.2.-0 [Older i know], tried to Wipe Data and Cache but couldn't, so thought i should give it a Full Flash, upon doing so i stumbled on many problems, like the one OP has here, others like 'Device Haulted" [The one you get when you try to update via a SDCard], so been wasting my brain cells since yesterday, So a thought struck to my mind "Did i try to Wipe the System and Data via TWRP?" [Actually you just need to wipe the Data Partition] , So tried again and it couldn't said [Couldn't mount data/] so Google and Struck on a Video by usmanalitoo [ youtube.com/watch?v=Rs4zcryNt5Y ] in which he said to Format the Data partition to ext2 then back to ext4 which did wonders, See the video yourself. if you can't flash or other stuff. Before you do other wierd **** to you innocent device.

ICS upgrade - boot loop - can't fix - bricked?

I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)​
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip​
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>​
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
jcr67 said:
I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)​
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip​
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>​
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
Click to expand...
Click to collapse
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED?
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
tpbklake said:
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED? .
Click to expand...
Click to collapse
yep
tpbklake said:
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
Click to expand...
Click to collapse
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
jcr67 said:
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
Click to expand...
Click to collapse
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s​
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
jcr67 said:
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s​
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
Click to expand...
Click to collapse
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Drugzy said:
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Click to expand...
Click to collapse
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s​
jcr67 said:
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s​
Click to expand...
Click to collapse
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
tpbklake said:
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
Click to expand...
Click to collapse
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s​
HBOOT now says:
*** RELOCKED ***
*** Security Warning ***
jcr67 said:
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s​
Click to expand...
Click to collapse
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Reinstall the HTC ruu
Sent from my HTC Raider X710e using xda app-developers app
tpbklake said:
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Click to expand...
Click to collapse
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
jcr67 said:
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
Click to expand...
Click to collapse
Yes you should be ok.
tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
yep he will be , during my downgrade i had to relock with security warning and ruu fixed it all
tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
Thanks very much. The stock ICS RUU has now installed successfully. I guess when I originally tried to reinstall it, I had left out the 'RELOCK' step, which is why it failed.
So now I am back to the start (stock ICS + HBOOT 2.02 S-ON), and want to get S-OFF and install your ROM zip. ,What I originally intended to do to get S-OFF was:
1) Unlock the bootloader, flash CWM Recovery, flash SU
2) Run downgrade GB RUU
3) S-off with Revolutionary
4) Install Blackrose HBOOT
5) Install your vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But step 2) failed with an unknown error. (I then tried to install your zip, and the rest is the sad history.....).
So what caused step 2 to fail? Did I need to relock the bootloader first?
Many thanks for your help, tpbklake
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly.
Sent from my HTC Incredible S using xda app-developers app
Drugzy said:
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly. p
Click to expand...
Click to collapse
That's it. HBOOT is remaining at 2.02.0002 after runme.cmd
Is the device rooted?
y OR n:y
Waiting for device to connect
Device found
Pushing misc_version
2455 KB/s (367096 bytes in 0.146s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Cleaning temp files​
Any ideas anyone?
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Sent from my HTC Incredible S using xda app-developers app
Drugzy said:
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Click to expand...
Click to collapse
No, I'm unlocked and rooted
Does the stock ruu have superuser installed? If it does I'm outta ideas.
Sent from my HTC Incredible S using xda app-developers app
---------- Post added at 07:58 PM ---------- Previous post was at 07:40 PM ----------
One more thing, I would try flashing another ROM, i came from Niks Sense 4a rom, and the script worked with no issues.
Remember you will need to manually flash the boot.img of the rom as you are S-ON.
jcr67 said:
No, I'm unlocked and rooted
Click to expand...
Click to collapse
Open a command window and then type in the command:
adb shell
If you get a # prompt then your ROM is rooted correctly and the script should run. If it doesn't then the ROM isn't properly rooted and the script will fail.

Help htc butterfly s , iam an expert in android but i failed :(

hii ...
i have HTC butterfly s phone is boot looping ,,,
issue :
when entering OS i can see the lock screen for 3 seconds then reboot.
solutions tried :
1- tried to wipe from TWRP recovery when it reaches /data >>> reboot.
2- tried to install another ROM without wiping >>>> reboot
3- tried to install CWM recovery , it says completed in fastboot (CMD) but recovery is not changing.
4- tried to lock the boot loader again , it says no such file or directory .
5- tried to boot in safemode but i see the lock screen for 3 seconds then reboot
iam stuck ... please help
thank you
hello
it happened to me the same, I just download it stock rom that is here, you have to see the version of your phone to know which is for yours.
greetings and good luck
all credits to the creator of the post
http://forum.xda-developers.com/showthread.php?t=2663295
GAVANA said:
hello
it happened to me the same, I just download it stock rom that is here, you have to see the version of your phone to know which is for yours.
greetings and good luck
all credits to the creator of the post
http://forum.xda-developers.com/showthread.php?t=2663295
Click to expand...
Click to collapse
hi .. thanks for reply ,,,
i downloaded stock rom 2.21 and tried to flash it from recovery when it tries to install the rom when it reaches to writing /data phone reboots
you mean something else ?
thanks ...
i want to add one thing ,,,
i have TWRP recovery 2.6.0.0 and i want to change it to CWM , i try to install from fastboot and it says successful but when i go into recovery its not changed !!!!!!
recovery recovery.img
sending 'recovery' (12364 KB)... OKAY [ 1.794s]
writing 'recovery'... OKAY [ 0.983s]
finished. total time: 2.777s
hwoarang626 said:
i want to add one thing ,,,
hello
at first I was the same with the recovery, but install this and it worked well, and use that version of android stock for now
but if you want to upgrade later (OTAS), you would have to have stock recovery and unroot your device, saludos
http://forum.xda-developers.com/showthread.php?t=2730482 .
i have TWRP recovery 2.6.0.0 and i want to change it to CWM , i try to install from fastboot and it says successful but when i go into recovery its not changed !!!!!!
recovery recovery.img
sending 'recovery' (12364 KB)... OKAY [ 1.794s]
writing 'recovery'... OKAY [ 0.983s]
finished. total time: 2.777s
Click to expand...
Click to collapse
hello
at first I was the same with the recovery, but install this and it worked well, and use that version of android stock for now
but if you want to upgrade later (OTAS), you would have to have stock recovery and unroot your device
regards
http://forum.xda-developers.com/showthread.php?t=2730482
its the same ,,, i tried to install the recovery you gave me but it did not install the recovery , Iam still stuck with a recovery that is not doing anything .
thanks
one more point ,,, i noticed that my /system is empty ...
hwoarang626 said:
one more point ,,, i noticed that my /system is empty ...
Click to expand...
Click to collapse
Since no one else is really helping you I will.
So what I gathered is your Rom bootloops and you've tried installing stock Rom but still no luck so you want to switch recoveries but you can't get twrp to flash...?
1. Are you S-Off or S-On? If you are s-on you must flash boot.img with this command
Code:
fastboot flash boot boot.img
2. To flash a recovery made for your device you must place it in fastboot and enter this
Code:
fastboot flash recovery recovery.img
3. Place Rom on internel storage if you choose cwm because it doesn't support external sdcard like twrp. For latest twrp, message @kairi_zeroblade... If you can't place on internal with cwm then you must do a sideload with the Rom same goes for twrp.
Want to support InsertCoin? Just get our donate key
xXminiWHOOPERxX said:
Since no one else is really helping you I will.
So what I gathered is your Rom bootloops and you've tried installing stock Rom but still no luck so you want to switch recoveries but you can't get twrp to flash...?
1. Are you S-Off or S-On? If you are s-on you must flash boot.img with this command
Code:
fastboot flash boot boot.img
2. To flash a recovery made for your device you must place it in fastboot and enter this
Code:
fastboot flash recovery recovery.img
3. Place Rom on internel storage if you choose cwm because it doesn't support external sdcard like twrp. For latest twrp, message @kairi_zeroblade... If you can't place on internal with cwm then you must do a sideload with the Rom same goes for twrp.
Want to support InsertCoin? Just get our donate key
Click to expand...
Click to collapse
thank you for your help ,,,
im S-ON
fastboot flash boot boot
.img
< waiting for device >
sending 'boot' (6104 KB)...
OKAY [ 0.830s]
writing 'boot'...
OKAY [ 0.590s]
finished. total time: 1.420s.
fastboot flash recovery
cwm6.0.4.5.img
sending 'recovery' (12364 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 0.990s]
finished. total time: 2.420s
i did what you said but nothing changed im still on TWRP recovery 2.6.0.0 and my room is boot looping
hwoarang626 said:
thank you for your help ,,,
im S-ON
fastboot flash boot boot
.img
< waiting for device >
sending 'boot' (6104 KB)...
OKAY [ 0.830s]
writing 'boot'...
OKAY [ 0.590s]
finished. total time: 1.420s.
fastboot flash recovery
cwm6.0.4.5.img
sending 'recovery' (12364 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 0.990s]
finished. total time: 2.420s
i did what you said but nothing changed im still on TWRP recovery 2.6.0.0 and my room is boot looping
Click to expand...
Click to collapse
Not sure if you can enter this command without a-off but try
Code:
fastboot erase cache
Then repeat the previous post....
If that doesn't work I'd try firewaters universal s-off tool and obtain s-off and try that command or see if it fixes your issues with your device. if that fails your best bet would be to ruu.. if you can't do that either you got a useless device till s-off exploit Is found if that's the reason why it's messing up.... Or donate it to someone who could fix it (me)
Want to support InsertCoin? Just get our donate key
xXminiWHOOPERxX said:
Not sure if you can enter this command without a-off but try
Code:
fastboot erase cache
Then repeat the previous post....
If that doesn't work I'd try firewaters universal s-off tool and obtain s-off and try that command or see if it fixes your issues with your device. if that fails your best bet would be to ruu.. if you can't do that either you got a useless device till s-off exploit Is found if that's the reason why it's messing up.... Or donate it to someone who could fix it (me)
Want to support InsertCoin? Just get our donate key
Click to expand...
Click to collapse
i tried this and no luck ,,,
actually i tried every thing but the problem is that the data does not change in the phone ,, i even formated (real format fsck) to /data and it was showing its empty but after reboot everything went back ,,, iam fixing android phones since htc desire but never faced anything like this ,,,
thank you for your help ,, and what you mean by donate and get it fixed ?
hwoarang626 said:
i tried this and no luck ,,,
actually i tried every thing but the problem is that the data does not change in the phone ,, i even formated (real format fsck) to /data and it was showing its empty but after reboot everything went back ,,, iam fixing android phones since htc desire but never faced anything like this ,,,
thank you for your help ,, and what you mean by donate and get it fixed ?
Click to expand...
Click to collapse
Seem like you fried your "/data" partition from what you just mentioned above. The only way I could see you fix is ruu. Cause HTC won't fix it if you send it in with a custom recovery at which you can't change.
And what I meant is since the device is rendered completely useless, unless you can get a run to ruu. You'd donate it to me this way i could try and fix it...
Sent from my HTC0P4E1 using Tapatalk
xXminiWHOOPERxX said:
Seem like you fried your "/data" partition from what you just mentioned above. The only way I could see you fix is ruu. Cause HTC won't fix it if you send it in with a custom recovery at which you can't change.
And what I meant is since the device is rendered completely useless, unless you can get a run to ruu. You'd donate it to me this way i could try and fix it...
Sent from my HTC0P4E1 using Tapatalk
Click to expand...
Click to collapse
i think im facing the same problem here, do u know where we can find the RUU, I searched the whole internet and i could not find, im ready to donate if u fix my problem and provide me with the RUU.
Regards
mr_wehbe said:
i think im facing the same problem here, do u know where we can find the RUU, I searched the whole internet and i could not find, im ready to donate if u fix my problem and provide me with the RUU.
Regards
Click to expand...
Click to collapse
There is no RUU for this phone, as far as I know. The closest thing to RUU is flashing everything by hand, but this seems to have failed in this case, unfortunately.

Categories

Resources