A friend found a Droid Eris on the side of the road. It would only boot to HBOOT. I am trying to fix the phone.
When I started working on it the bootloader was 1.47.0000 S-ON
I followed this Q and A thread to flash 1.29.2000 S-OFF
I can not get it to boot Amon's recovery. It freezes at the three skateboarding androids. It always boot to fastboot even if I have other buttons held down.
I have tried fastboot erase, flash, and boot.
I know how to use adb and fastboot.
In summary I have never been able to get the phone to boot fully but was able to flash the root rom with S-OFF. Now I need help booting to recovery.
Thanks in advance
This post has both a version of Amon_RA Recovery that can work with a broken trackball, plus instructions on how to flash with fastboot with the S-OFF bootloader (see scenario 4 toward the bottom): http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
Hi Everyone. '
I have been trying everything to get a custom rom on my HTC View. I tried the multi tool, which was unsuccesful at downgrading. I also tried no sense roms both would go to a black screen after flashing.
This Time i tried flashing dexters JB rom. The aroma installer worked fine but it says succesfulley installed, however the last line on the aroma installer says
-> Flashing Kernel
assert failedackage_extract_file("boot.img", "/dev/block/mmcblk0p22")
It then gives me the option to select next or save logs.
I select next and go and flash the 1.6 patch.
next i flash google apps.
then power off.
Next power on,
White HTC screen, then a black screen. nothing.
This happened to every rom i Installed. I am using Clockwork mod recovery to flash these. Is there something else I have to do?
here is my bootloader screen
***Unlocked***
express PVT SHIP S-ON RL
HBOOT- 1.140005
MICROP- 0656
RADIO-1.05.01.1006_3
eMMC-BOOT
OCT 25 2011, 16:35:13
From there I would select recovery and the revolutionary CWM would come up, I will then wip everything, install zip from sd card.
If you're HTCDev unlocked you cannot flash a different boot.img in recovery. Extract the boot.img from the ROM you are trying to flash and place it in your android-sdk/platform-tools folder then use the following commands in a terminal.
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
Hello everybody.
Before posting this thread I have read lots of similar threads, but no answer...
My evo was running fine on Mwakious3D rom v.15.3, I was s-off, 4ext recovery, Hboot 1.49.1107, kernel coolexe (integrated in Mwakious rom).
Yesterday night I had network connection problems, so I tried to switch from GSM only to GSM/CDMA auto and back.
My device freezed and I could not get back it responding, so I pulled the battery out.
Then I put back the battery in and tried to turn it on.
From that moment, when I try to turn it on, it shows the HTC splash screen, then after about 10 seconds it turns off by itself and starts bootlooping.
I tried to enter recovery trough Hboot, but even recovery gets stuck on HTC splash screen and the device gets very very hot, then a bootloop starts. I have to pull the battery out because I fear I can damage it.
So I tried to flash again the boot.img from the rom I was on, through Fastboot in command line. The operation succeeded, but when I tried to reboot, I always got bootloop.
So I tried to fastboot flash a new recovery becaue I thought mine was broken. I tried to flash 4ext, cwm and twrp.
Even this didn't fix the problem: I can't get past HTC splash screen either in normal rebooting nor recovery.
So I tried to flash the P86img.zip contained in this thread at letter E: ht_tp://forum.xda-developers.com/showthread.php?t=1743466 (sorry, I can't post URLs).
Even after flashing that, no way I can get past the HTC splash.. I can't access recovery, even if I try to boot it from fastboot.
I don't know what to do anymore.
Please help!!!
My configuration at the moment:
Hboot 1.49.0007 s-off
Radio: 10.13.9020.08_2m
Recovery: 4ext
Please, help me as soon as possible, you are my only hope to unbrick my Evo 3D!!!
Another information: I try to access the device also via adb.
It returns me empty devices list.
If I run adb usb, it returns me error:no device connected.
I have the HTC drivers v.3.007 installed. I tried both on XP x86 and W7 x64.
Fastboot instead recognizes the device, so that I can flash *.img.
relock hboot and run an RUU. then flash recovery and rom again.
EM|NEM said:
relock hboot and run an RUU. then flash recovery and rom again.
Click to expand...
Click to collapse
Thanks a lot... i'm trying in a couple of hours...
I will feedback if it's working.
Bad news dude!!!
I relocked hboot then ran the latest RUU.
Flashing process proceeds well and completes, but after it the phone keeps bootlooping. Always stuck to HTC splash logo.
In the bootloader menu "recovery" is still there. I can't boot into recovery either because I get the usual bootloop.
Any further ideas?
At the moment I am on
Hboot 1.53.0007 relocked s-on
radio -11.25.3504.06_m
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
when I run adb usb it still responds error: device not found
Now I unlocked back Hboot and succeeded in flashing recovery (4ext).
Anyway that f***ing bootloop is still there... I can't access recovery...damnit:crying:
Take out your sdcard and see if you can boot into recovery, taking a shot in the dark but could be a corrupt sdcard
(Don't ask me for help as I couldn't care if your phone explodes, eh!
try "fastboot boot recovery.img" in cmd. but the real problem is that running RUU didnt work. are you sure it flashed completely? I'd say run it again
Sorry, friends, I tried both methods without success...always that bootloop after... Even trying fastboot boot recovery.img... I can't get into recovery menu. Only hboot menu... Maybe I could try once again to flash the RUU.exe after relocking bootloader...any better ideas than mine? I'm starting to lose hope...
Hi,
I have nearly the same issue.
i played to much with reroot and unroot.
Now my evo gsm austria is:
shooter_u pvt shp s-off rl
hboot 1.53.0007
radio 10.13.9020.08_2m
eMMC boot
I can access recovery, but it doesn't matter which rom i flash i always have the bootloop. I even flashed different recoveries and the extracted boot,img from the roms (via fastboot). But i'm stuck in the Bootloop.
When i try to flash an RUU as PG86IMG i get the message CID incorrect.
CID is VODAP120
I hope someone has the answer.
thanx michael
---------- Post added 9th December 2012 at 12:05 AM ---------- Previous post was 8th December 2012 at 11:37 PM ----------
I changed my CID now:
fastboot oem writecid HTC__01
moved a non branded pg86img to the root of my sdcard and it ran through
now my phone is back to hboot 1.49.0007
looks good at the moment
i want to get back to full stock, to get original ICS
but i can't get updates, they always fail during the installation . even when i was locked and s-on
It runs again - back to life
So what did i do next.
The official OTA Update to ICS came down!
But wouldn't install
So i extracted the firmware.zip moved to PG86IMG.zip and flashed over the bootloader.(just 24MB - Boot,Bootloader)
It installed rebooted and at the moment a very long black screen, lets see how long
---------- Post added at 06:45 AM ---------- Previous post was at 06:27 AM ----------
No bootloop, but nothing else too
Next step
extract the rom.zip from "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed"
moved as PG86IMG.zip to root of SDCARD
and flashing over Bootloader
lets wait
---------- Post added at 06:53 AM ---------- Previous post was at 06:45 AM ----------
YEAH
Android 4.0.3
Sense 3.6
Software
3.28.401.1
And its running
Still S-OFF and unlocked
with H-BOOT 1.53.0007
Radio 11.25.304.06_M
I hope the 12hrs i invested the last 3 days will repay
gianborrello said:
Sorry, friends, I tried both methods without success...always that bootloop after... Even trying fastboot boot recovery.img... I can't get into recovery menu. Only hboot menu... Maybe I could try once again to flash the RUU.exe after relocking bootloader...any better ideas than mine? I'm starting to lose hope...
Click to expand...
Click to collapse
Extract the rom zip file and rename it to PG86IMG.zip , put in root of sdcard and flash in bootloader.
I'm running out of ideas here. Running an RUU is a last failsafe method of restoring your phone to stock but that isnt working for you. Maybe try another ruu(the one which was on your phone when you purchased it)
I'm having some issues aswell.
I flashed 4ext because some roms would get stuck on the htc logo screen for half an hour..
Flashed the NonSense rom, worked fine, made a backup of it.
Then i wanted to test Viper's latest rom with sense 4.0, flashed it with 4ext, successful.
I found NonSense better in my opinion so i went to backup, and restored the ROM. After that i couldn't get any further than the htc logo screen.
I switched to clockwork, twrp but no result. I tried even other ROMs but i still can't get pass that cursed splash screen.
And yes, i deleted cache and dalvik etc..
The only thing i haven't tried is getting the stock rom and flashing it to see if it works.
Also, would some of you be kind enough to give me the recovery.img of the latest version of 4ext? I can't find it anywhere, not even on my sd card.
Thanks, looking forward to your answers.
my advice would be to do a clean install of nonsense rom. Wipe data+factory reset, wipe dalvik cache, install rom.
btw are you s-off or s-on? be sure to turn on smart flash in case you're s-on.
I've attached 4EXT RC5
EM|NEM said:
Extract the rom zip file and rename it to PG86IMG.zip , put in root of sdcard and flash in bootloader.
I'm running out of ideas here. Running an RUU is a last failsafe method of restoring your phone to stock but that isnt working for you. Maybe try another ruu(the one which was on your phone when you purchased it)
Click to expand...
Click to collapse
Alredy tried also this method... always that bootloop...
I'm starting to lose my hopes.
flash boot.img in fastboot again and try
EM|NEM said:
flash boot.img in fastboot again and try
Click to expand...
Click to collapse
I tried... I'm s-on and hboot relocked.
That's what I get:
Code:
C:\Android>fastboot flash boot boot_signed.img
sending 'boot' (4310 KB)...
OKAY [ 0.883s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.466s
Code:
Damnit!!!
you need to unlock bootloader again before flashing boot.img or recovery
EM|NEM said:
you need to unlock bootloader again before flashing boot.img or recovery
Click to expand...
Click to collapse
done...unlocked, flashed boot_signed.img and tried to boot. Always bootloop.
Then flashed recovery_signed.img and tried to boot... again that f***ed bootloop. Starting to hate HTC splash screen!!!!
do you still get the "FAILED (remote: signature verify fail)" error? If so theres something wrong here. And do flash a custom recovery like 4EXT. it should then be recovery.img not the signed one
right, i recently purchased a htc one x plus, and decided to unlock bootloader and root it. there was no problem with unlocking the bootloader, but when i rooted it, my phone was stuck on airplane mode. i then (stupidly) decided to try and upload a custom rom without flashing the boot image first, and now when i try and boot my phone it is stuck on the splash screen. i have tryed restoring my nandroid backup, and flashing the custom rom image then reinstalling the rom, but still stuck on the splash screen. please help !!!
here is what is displayed on my bootloader screen;
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.35.0000
CPLD-NONE
MICROP-NONE
RADIO-3.1204.168.32
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW secure boot: enabled
MODEM PATH: off
i am a noob, and now realise this.............
You must flash the correct boot.img from your custom rom in bootloader.
fastboot erase cache
fastboot flash boot (name).img
fastboot erase cache
skdubg said:
You must flash the correct boot.img from your custom rom in bootloader.
fastboot erase cache
fastboot flash boot (name).img
fastboot erase cache
Click to expand...
Click to collapse
i did flash the boot.img before installing the custom rom, but no luck !
the custom rom i am trying to install is maXimus v4.0 alpha 2.
i will try again, but if that doesnt work, can i get the boot.img for the stock rom that i have backed up, as i cannot switch the phone on to get access to the boot.img that is saved in the backup
thanks !
SOLVED
Hey, I have htc evo 3d gsm (shooteru). I unlocked the bootloader using htcdev.com and installed clockworkmod recovery. Then I changed cid to HTC__001 and tried to flash a gingerbread ROM in preparation for using the flashmaniac tool to downgrade my hboot (1.53.0007 -> 1.49.0007).
But when I tried to flash the gb rom the recovery said that installation finished but the phone did nothing after reboot. So I took out the battery and went into bootloader and everything looked the same as before the flash attempt. So I tried once again with same result. Then I powered off the phone and now when I turned it on again it only shows the HTC logo for a few seconds and then nothing (the buttons at the bottom have their lights turned on though).
Any ideas?
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Yes, hboot version not compatible with gb rom, and or boot partition didn't get flashed. Unlocked but s-on doesn't let boot partition have write if booted into recovery in a normal way.
So yoy can get boot.img from install zip and flash with fastboot
fastboot flash boot boot.img
Or you can reinstall from recovery if booted from fastboot command.
fastboot boot recovery.img
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
randomguyhtc said:
Somehow got it at least to bootloader, no idea how, just tried taking out battery a few times and charging it a bit and it worked.
Thanks for the advice, didn't realize there was a difference between these flashing methods.
Click to expand...
Click to collapse
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Power + volume down when turning on will get you into bootloader
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I know , it just didn't work for some reason before.
So I flashed the boot.img and now it's stuck in a boot loop. Tried going to cwm recovery and wiping various caches etc and flashing again, and flashing boot.img again but it still goes into boot loop.
I would just use the flashmaniac's tool anyway because I don't care about any data on the phone or anything, but it seems that it requires the phone to be booted before it can start the downgrade.
What should I do? Try to flash other roms maybe? The one that I have now is EU_Shooter_U-1.20.401.8_ROOTED.
So I extracted a rom.zip from a RUU but it won't flash from cwm "Can't open /sdcard/rom.zip (bad)", should I try to flash it with adb/fastboot? I'm worried that the zip may be broken (even though archive manager integrity check says its fine).
Would this work with shooteru/GSM?
[TOOL] Ultimate Recovery Tool 3.1 (Unbrick, Downgrade, VM Radio Fix/Reset)
I'm thinking it might be a way to sidestep the boot loop problem that I have now, just relock the bootloader and follow the instructions until I get HBoot 1.40.something like the guy in the video?
Do I need some special drivers when using the RUU executables on Windows?
So I've got it to work. The problem was what jcfunk said (both of the things he mentioned, actually), I was trying to flash a GB rom when I should have tried an ICS rom instead (lol). After going to ICS RUU, I did the wire trick (unlimited.io) and now everything works nicely and I can get the latest roms.
Glad to hear.