This is not for my phone, but a friends...
Got an HTC EVO 3D with HBoot 1.5 that was unlocked with the HTC Unlocker Tool (from the HTC website). User had clockworkmod touch installed and tried to install ViperROM. Getting an error message (status 1) that looks like it is due to the ClockWorkMOD Touch version. He tried to downgrade the version to 5.0.2.0 and in doing so (did it from ROM Manager), he can no longer get in CWM. When booting to recovery via hboot, ROM Manager or Quick Boot, it shows the white HTC screen, then a plain black screen, then just reboots his phone back to the white HTC screen again.
Now he can't get into any CWM recovery. He's tried several different versions and can't get anything to work. I tried to flash the recovery 5.0.2.0 via fastboot and it says it was successful but it still won't boot into it.
Not sure where else to look for this one.
Just tried to flash via fastboot TWRP and no dice either. It said it was successful too.
Did you check to see if 'fastboot' is unchecked. Its in settings, power.
We're comin from a pure power source.
metalfan78 said:
Did you check to see if 'fastboot' is unchecked. Its in settings, power.
We're comin from a pure power source.
Click to expand...
Click to collapse
It is unchecked. I had todo that first. Fastboot sdes seem to be working.
Code:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery y:\recovery-clockwork-5.0.2.0-shooter.img
sending 'recovery' (4726 KB)...
OKAY [ 1.187s]
writing 'recovery'...
OKAY [ 1.687s]
finished. total time: 2.875s
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery Y:\recovery-twrp-shooter-1.0.3.img
sending 'recovery' (5068 KB)...
OKAY [ 1.203s]
writing 'recovery'...
OKAY [ 1.703s]
finished. total time: 2.937s
Are u trying to get into recovery after starting fast boot and it not working? Or just rebooting the phone into recovery? Since there is still no s off for 1.5 the only way to get to recovery is through fastboot
Sent from my ADR6400L using Tapatalk
dachef3184 said:
Are u trying to get into recovery after starting fast boot and it not working? Or just rebooting the phone into recovery? Since there is still no s off for 1.5 the only way to get to recovery is through fastboot
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I'm not sure that's correct.
He had CWM 5.0.2.0 that worked fine and he had the Touch CWM and it worked minus flashing ViperROM (possibly more, we did not try). He was able to launch CWM with a recovery reboot in ROM Manager, PowerButton and Quick Boot.
Holy crap this guy's phone sucks ass...
So, he flashed CWM back on 09/11/11 (which i think he was on hboot 1.4 or 1.3). He then flashed Synergy via CWM. He then tried to take an OTA update which failed but updated his hboot to 1.5. He hasn't flashed another ROM until just now.
He had the old CWM from before, and he is able to get the touch version (but it's usage is limited due to S-ON).
I'm just going to get him to flash a new ROM through fastboot and use 5.8.0.1 CWM Touch for nandroids, which still do work. I was able to get that CWM installed back on his device without a problem.
See the Guide/Flashing notes in my signature, i think it will help you out. Fyi, I've found only a few specific recovery versions work on my Hboot 1.50, Unlocked, S-On Evo3d.
I have hboot 1.5 and the only CWMs I've been able to get to boot properly are 4.0.1.4 and 5.8.0.1...the others I have tried always failed the same way yours did.
Please try the attached CWM or TWRP (both old versions/no touch screen) and tell if they work for you.....
OR
Try the touch CWM from here -> http://www.clockworkmod.com/rommanager
OR touch TWRP 2.0 from here -> http://teamw.in/project/twrp2
Related
Hey all,
so i had cleanrom ics installed on my 3vo. i installed it without freizas firmware.
anyways, due to pink camera issues, i needed to get the phone replaced, so i tried downgrading with the 1.13 pg86img (this was before i learned about the downgrade issues).
the system part of the update failed, which made my phone not able to boot past the initial HTC screen.
i then tried installing freizas pg86img to get my phone in working order again. the installation worked, but i still cant boot past the htc screen.
i can boot into the bootloader and access recovery (although its the stock htc recovery so i cant use it), and still have s-off.
any help would be greatly appreciated
alexjzim said:
Hey all,
so i had cleanrom ics installed on my 3vo. i installed it without freizas firmware.
anyways, due to pink camera issues, i needed to get the phone replaced, so i tried downgrading with the 1.13 pg86img (this was before i learned about the downgrade issues).
the system part of the update failed, which made my phone not able to boot past the initial HTC screen.
i then tried installing freizas pg86img to get my phone in working order again. the installation worked, but i still cant boot past the htc screen.
i can boot into the bootloader and access recovery (although its the stock htc recovery so i cant use it), and still have s-off.
any help would be greatly appreciated
Click to expand...
Click to collapse
Use adb to push a recovery.img to your phone then boot into it and flash a nandroid back up.
ehurt152 said:
Use adb to push a recovery.img to your phone then boot into it and flash a nandroid back up.
Click to expand...
Click to collapse
after trying to push the latest clockworkmod with fastboot, i got this:
sending 'recovery' (4726 KB)...
OKAY [ 1.118s]
writing 'recovery'
FAILED (remote:not allowed)
finished. total time: 1.151s
im stuck
If your s-off try running an ruu with the same hboot you have. If it boots up go check usb debugging. Then try to push the recovery via adb or fastboot flash one.
#Root-Hack_Mod*Always\
laie1472 said:
If your s-off try running an ruu with the same hboot you have. If it boots up go check usb debugging. Then try to push the recovery via adb or fastboot flash one.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
will an ruu run if i cant boot into the system? if so what should i boot into to get it working
edit: after doing lots of flashing, i was able to boot into the system with the 2.08 ruu. it upgraded my hboot to 1.5 and locked my bootloader, but i still have s-off. i was unable to change the recovery image, it kept failing, so i tried flashing an older ruu to unlock my bootloader. again i got the hboot back to 1.4, but the system part of the update still failed.
any help would be greatly appreciated
You should just flash a recovery threw hboot. Here's the latest twrp hboot.zip
http://db.tt/Zw4KCyW2
Drop it on your sd. Then power the phone off. Then press and hold the volume up button. Then tap/press the power button. Continue to hold the volume up button untill you see a white screen. Then wait you phone should recognize the zip. Follow the on screen instructions from there.
#Root-Hack_Mod*Always\
Resolved: I had mistaken the stock recovery screen for an error screen. Noob error.
Hey there,
New ATT One X+ user here. First off, wanted to say great job to all the devs! Exciting to see so much progress.
Anyway, I successfully unlocked my phone, flashed TWRP, and installed Elegancia ROM using hasoon2000's tool. Now I would like to revert to the stock recovery, since offmode charging doesn't work for the ATT TWRP yet. However, I'm having an issue: I can't flash a stock recovery back onto my device! (When I try to boot into stock recovery, the red triangle with a "!" pops up)
Here's an outline of what I tried:
1) grabbed the ATT stock recovery from http://forum.xda-developers.com/showthread.php?t=2064295
2) renamed the recovery "recovery.img" and put it in the folder where my fastboot is
3) flashed the recovery using "fastboot flash recovery recovery.img". It looks like it's successful; here's the output:
" sending 'recovery' (7142 KB)... OKAY [ 0.922s]
writing 'recovery'... INFOFormat partition SOS done
OKAY [ 0.389s]"
4) tried booting into recovery, but it shows the red triangle error screen
Now, if I follow the above steps using the TWRP recovery image, I am able to boot back into TWRP. It's odd that the flashing works with TWRP but not with the stock recovery...
Other potentially useful troubleshooting info
- I tried using hasoon's tool to flash the stock recovery, but it has the same results
- my bootloader still says it's "UNLOCKED"
- I also tried running "fastboot erase recovery" before flashing, and it fails with the message: "erasing 'recovery'... FAILED (remote: not allowed)" (nevermind, command doesn't work in S-ON state)
Thanks in advance for any help!
kproto said:
- I also tried running "fastboot erase recovery" before flashing, and it fails with the message: "erasing 'recovery'... FAILED (remote: not allowed)"
Click to expand...
Click to collapse
does not work at S-ON state
skdubg said:
does not work at S-ON state
Click to expand...
Click to collapse
Had a feeling that was the reason, but thought I'd include it just in case it was relevant to the problem. Thanks, will edit original post
Iam wondering too... So how to make this? Any special procedure? To flash back stock recovery?
Wysyłane z mojego HTC One X+ za pomocą Tapatalk 2
kproto said:
Hey there,
New ATT One X+ user here. First off, wanted to say great job to all the devs! Exciting to see so much progress.
Anyway, I successfully unlocked my phone, flashed TWRP, and installed Elegancia ROM using hasoon2000's tool. Now I would like to revert to the stock recovery, since offmode charging doesn't work for the ATT TWRP yet. However, I'm having an issue: I can't flash a stock recovery back onto my device! (When I try to boot into stock recovery, the red triangle with a "!" pops up)
Here's an outline of what I tried:
1) grabbed the ATT stock recovery from http://forum.xda-developers.com/showthread.php?t=2064295
2) renamed the recovery "recovery.img" and put it in the folder where my fastboot is
3) flashed the recovery using "fastboot flash recovery recovery.img". It looks like it's successful; here's the output:
" sending 'recovery' (7142 KB)... OKAY [ 0.922s]
writing 'recovery'... INFOFormat partition SOS done
OKAY [ 0.389s]"
4) tried booting into recovery, but it shows the red triangle error screen
Now, if I follow the above steps using the TWRP recovery image, I am able to boot back into TWRP. It's odd that the flashing works with TWRP but not with the stock recovery...
Other potentially useful troubleshooting info
- I tried using hasoon's tool to flash the stock recovery, but it has the same results
- my bootloader still says it's "UNLOCKED"
- I also tried running "fastboot erase recovery" before flashing, and it fails with the message: "erasing 'recovery'... FAILED (remote: not allowed)" (nevermind, command doesn't work in S-ON state)
Thanks in advance for any help!
Click to expand...
Click to collapse
To be polite I would not flash the recovery he linked, While he may have good intentions all of his other posts I have seen and tried to help deal with have shown a lack of understanding and experience with android. For all I know he is hosting the same file I gave him earlier but incase he isn't please download this recovery: https://www.asuswebstorage.com/navigate/s/665115AABBFA49E783795815A6E5666F4 Go into fastboot and flash it using command prompt with "fastboot flash recovery (recoveryname).img" Please note stock recovery should a picture of a phone down with an alert signal above it. Please note this is for AT&T ONLY
Oh! Well, I feel foolish now -
I had thought the screen with the phone down and a red alert over it was an error screen. I assumed there would be some menu options or something on there; are there not supposed to be?
Just to confirm, I've attached a picture of my phone booting into the stock recovery you posted. Is this how it's supposed to look?
kproto said:
Oh! Well, I feel foolish now -
I had thought the screen with the phone down and a red alert over it was an error screen. I assumed there would be some menu options or something on there; are there not supposed to be?
Just to confirm, I've attached a picture of my phone booting into the stock recovery you posted. Is this how it's supposed to look?
Click to expand...
Click to collapse
That is standard recovery menu.......
Kraizk said:
That is standard recovery menu.......
Click to expand...
Click to collapse
Fantastic. I guess I should have checked out what the recovery looked like initially before flashing TWRP over it. Anyway, thanks for all your help!
Any news on S-OFF?
no s-off for Tegra devices....
At all...for sure?
Sent from my HTC One X+ using xda premium
yes!!!!
Today I buy HTC Evo 3D CDMA
In "About phone" it has Android revolution ROM
I restart phone in HBOOT (vol down+power) and when I press @[email protected] it restart and now it always bootloop.
I don.t know what to do...hlp me pls.
It:
UNLOCK
1.58
S-ON
ZiViTi_13 said:
Today I buy HTC Evo 3D CDMA
In "About phone" it has Android revolution ROM
I restart phone in HBOOT (vol down+power) and when I press @[email protected] it restart and now it always bootloop.
I don.t know what to do...hlp me pls.
It:
UNLOCK
1.58
S-ON
Click to expand...
Click to collapse
Is it HTC unlocked?
If so, RELOCK it through ADB and then RUU it, then HTC unlock it again, then root and put new rom back on.
Yes it UNLOCK with HTC official method
I RELOCK it, install RUU...it's ok. Then I try install recovery(twrp, cwm) with fastboot flash recovery recovery.img..it say's "OKAY" but when I click on recovery from hboot my phone restart and bootloop...
C:\Users\CUHOHUM\Documents\HTC Evo 3D\rootevo3dnew>fastboot flash recovery recov
ery.img
sending 'recovery' (6912 KB)...
OKAY [ 1.690s]
writing 'recovery'...
OKAY [ 1.968s]
finished. total time: 3.658s
C:\Users\CUHOHUM\Documents\HTC Evo 3D\rootevo3dnew>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.691s]
booting...
OKAY [ 0.003s]
finished. total time: 1.694s
Click to expand...
Click to collapse
Recovery install, but wwhen I boot it, phone go bootloop. How to fix this?
dont install recovery, just run RUU and then see if it boots. And i believe u need to unlock it again to flash custom recovery
Ok. I install RUU from HBOOT(PG86IMG.zip).
ROM boot, but when I unlock it it stay bootloop...
Maybe 1.58.0000 it doesn't unlock?
I just went through the same problem here. First I was rooted s on and I tried to restore and got bootloop. Fixed it by relocking and ruu'ing. Then I unlocked flashed recovery and supersu then attempted the jbear s off. Apparently I failed at the wire trick and that lead my phone into bootloop. I relocked then ran the ruu and still bootlooped. I ran it a few more times and got it to boot. Now, whenever I power down and remove the battery, my phone bootloops and the I have to boot into bootloader and slecet recovery. The phone does its thing and reset my phone to stock then booted. I don't wanna pull my battery cause I think it'll happen again. Anything that can fix? I'm complete stock.
Sent from my PG86100 using xda app-developers app
I was running the latest TRON ROM from Neo with no issues for several days. Tonight, I went to use the camera and it FC'd. It kept doing it so I tried rebooting. It flashed the white screen with the green HTC logo and thats it, it won't go any farther.
I can get to recovery by pulling the battery and using the hard buttons, but recovery is not able to mount the internal or external memory. I cant backup, restore, flash a zip, or do anything really. How could this have happened? Am I bricked?
HELP!
If the phone does anything at all, it is not bricked. (The state it's in is sometimes called a soft brick, though). I believe there are two things you can do: either get an RUU (PH98IMG.zip) onto your SD with a computer (and an SD card reader EDIT: Or the Incredible you mentioned in the ROM thread), then boot up to hboot and let it flash, or try flashing a kernel (boot.img), ROM, or RUU using adb/fastboot.
If you have questions about the first of these processes, I may be able to answer them, but I probably won't be too helpful about the latter since I haven't flashed anything with adb/fastboot in quite a while.
HERE is the latest RUU, by the way.
Thanks, I'll try this out tomorrow.
s-on? Can you boot into the bootloader? Try reflashing the kernel via fastboot.
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
trud9340 said:
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
Click to expand...
Click to collapse
Did you re-unlock after running the RUU?
trud9340 said:
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
Click to expand...
Click to collapse
download this zip and place it on the root of your sd card. it will flash Amon RA through hboot. no need for fastboot commands.
http://androidfilehost.com/?fid=9390248398092764223
mjones73 said:
Did you re-unlock after running the RUU?
Click to expand...
Click to collapse
Just realized that, after doing some research...DOH!
Unlocked and good to go. Thanks!
Hello all, I recently started the process of rooting my HTC One X+ and it all went smoothly until it came time to flash a recovery.
I used Windroid Universal toolkit to get started, thinking it would make things easier (not that I haven't rooted a phone before).
I unlocked the bootloader just fine, in the bootloader it gives "*unlocked*".
Next, I tried flashing TWRP with the toolkit, it brings me to bootloader, but when going to HBOOT and hitting recovery, it just brings me back to bootloader. Hmm, weird. So I decide to do it manually, download latest TWRP for evitareul (2.8.5.0), reboot into fastboot.
Execute: fastboot flash recovery twrp-2.8.5.0-evitareul.img
and it gives me this:
"sending 'recovery' (8224 KB)...
OKAY [ 1.115s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0xa)
finished. total time: 1.153s"
I don't know whether it matters, but when going into HBOOT it pops up with some errors saying something along the lines of unable to access SD or something. It goes too fast to really write it down.
So I think maybe deleting cache would help, and to no avail. I look up online for the error code and nobody seems to have an answer for it. I apologize if this has been answered elsewhere on the forums, I looked for quite some time before posting a new thread. I'm not sure what is going wrong.
My end goal was to flash recovery, make a back up, then flash superSU but if I can't flash recovery then I'm not going to do anything else and risk a brick.
Does anyone know what's up with this error and how to fix it?
You're flashing a wrong recovery.
Coolgoly said:
You're flashing a wrong recovery.
Click to expand...
Click to collapse
What recovery should I be flashing then? My device is Evitare_UL, and I am getting img files from
HTML:
https://dl.twrp.me/evitareul/
.
I have tried other versions to no avail.
Evitareul should only have 2.5 TWRP out....