Develop Bugs

[Q] Stuck at HTC green boot after attempt perm-root w/Visionary r12

I seem to be stuck on the "boot loop" of the HTC green logo. I tried doing the perm-root option in Visionary r12 and have been here ever since.
A few things:
- I can get into the HBOOT
- I have done a factory reset from bootloader
- I have done a reset from fastboot
- I attempted to do the flash of PC10IMG, but received the "main version is older"
- I can't change version because ADB won't connect for some reason, maybe because i'm in HBOOT?
I can't seem to get ADB to recognize my device, but when I did a factory reset from the bootloader, ADB did finally show the device, but it said "offline"
I'd be happy if I could get this G2 functioning, root or no root.
Anyone have any ideas what I can do to fix this?
thanks!

I also need to add that I did a FACTORY RESET from HBOOT and let it sit for about 2 hours, didn't move off the HTC green logo screen.
If anyone out there can get me up and running i'd gladly pay them $25 for their trouble!!

Zaldor said:
I also need to add that I did a FACTORY RESET from HBOOT and let it sit for about 2 hours, didn't move off the HTC green logo screen.
If anyone out there can get me up and running i'd gladly pay them $25 for their trouble!!
Click to expand...
Click to collapse
is your g2 showing s-on or s-off at the HBOOT screen?

It has S-ON

So am I screwed? Is there no way to get this back up? I don't think I ever had S-OFF, when I rebooted from Visionary r12, it stuck right on the HTC boot, so I didn't so anything else. When I went to HBOOT, I think it said "S-ON" then and has always said "S-ON"....

Probably screwed. Seems like you did exactly what you werent supposed to do, as posted in this thread http://forum.xda-developers.com/showthread.php?t=838484

Zaldor said:
It has S-ON
Click to expand...
Click to collapse
that wasnt a very smart choice buddy..

I have this exact problem EXCEPT MINES S-OFF.....any tips?
edit** fixed http://forum.xda-developers.com/showthread.php?p=9330530#post9330530

Im having the same problem. after perm root attempt I get stuck at the htc screen unless i pull the battery. I am able to get into h-boot and fast boot but have no clue what to do from there. everything I research assumes that i have other stuff installed here such as third party recovery or hex editor. I wasn't attempting to change Roms or anything like that until I felt a little more comfortable but now im stuck.

Flashing the pc10img was not a good move. Happened to me back in september. I was one of the first to get the g2. Fortunately I was s-on also. That is good in the fact you can return it and get a new one like I did. The second time around I read..read and then I read. Then rooted without a problem. Tell tmo the phone just got stuck and they will give you one for free. Always read the entire thread and links on those threads. I found out the hard way also. There has been stories of that being fixed though. Good luck bro
Sent from my HTC Vision using XDA App

help!!!!
ratchetrizzo said:
is your g2 showing s-on or s-off at the HBOOT screen?
Click to expand...
Click to collapse
What if its S-OFF?

[Q] Visionary broke my Tmobile G2 phone - PLEASE HELP !!

I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38

boyfrom75 said:
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
Click to expand...
Click to collapse
Try the following link:
http://forum.xda-developers.com/showthread.php?t=842495

I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?

boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
1) Just to clarify: VISIONary is a complete fail. Root using the rage method, then you can actually control what's happening to your device.
2) Did you ever flash clockwordmod recovery?
If you can boot into clockwork recovery you just need to flash another ROM.

Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.

tehseano said:
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
Click to expand...
Click to collapse
this guy is obviously new cut him some slack.....
just follow the instruction on the link carefully
idk why people are having trouble with VISONary i used it to root my phone n it worked....
im new on the forums but i know a thing or two about rooting

That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom

boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
Ok, this is a snip from the link in the second post, it sounds like your are stuck in a boot loop with s-on, if so then this part is the part you need to try:
"*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on."
So now you are gonna have to install Andriod SDK to your computer and the drivers for the G2, there is gonna be a lot of reading and some downloading on your part to do this. Next your gonna have to download cwm recovery.img and wpthis.ko in your sdk folder and then follow the instructions above to recover your phone. Unfortunatly there is no one click fix. Its gonna take a lot of reading and understanding to do this on your part. Gonna have to learn to use ADB there a guide for that and run some basic command promts. Im no Dev or anything but I taught myself by doing a lot of reading, watching videos and a lot of searching. Hope you find the will to do it and recover you phone. Plus we are here to help walk you through some of it but your also gonna have to do some leg work to. GOOD LUCK.

I don't think the OP knows what adb is... you gotta do some more reading get over your fear of using your computer to fix your phone. Its really nothing to be afraid of and its not at all complicated.
Sent from my HTC Vision using XDA App

I'm gonna assume he knows what ADB is and if that's the case, your only option is using one of the full updates...from tmobile. It would have to be a new version of course, for your recovery to allow it. Trying reading through thr RUU threads, perhaps something or someone there can help.
Goodluck, and sry.
Sent from my HTC Vision using XDA App

android602 said:
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
Click to expand...
Click to collapse
Brah its not even rooted yet
Sent from my T-Mobile G2 using XDA App

Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying

omarsalmin said:
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
Click to expand...
Click to collapse
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).

blackknightavalon said:
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
Click to expand...
Click to collapse
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.

omarsalmin said:
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
Click to expand...
Click to collapse
actually all the older guides (including the one I used to root my phone) said you ran perma root first then do s-off.
the perma root method in visionary was made before we even had s-off (only like a day before, but still before).
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.

Lennyuk said:
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Click to expand...
Click to collapse
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).

steviewevie said:
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
Click to expand...
Click to collapse
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
I have a feeling the perma root process is corrupting roms on newer devices, not sure on the why though.

Lennyuk said:
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
Click to expand...
Click to collapse
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.

steviewevie said:
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
Click to expand...
Click to collapse
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.

Lennyuk said:
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Click to expand...
Click to collapse
Sorry you took it that I was asking you to prove yourself. I wasn't, I was just asking for information, because I'm interested in the subject.
I'd seen those threads but do you know for certain they didn't try Visionary first, find it didn't work properly, then try rage ?
I could of course be wrong, but I don't see how rage can cause corruption because it doesn't do a lot, it just fires up a bunch of processes to exploit a way to get root. It's so much simpler than Visionary, which does a whole load of RAM disk stuff and other things that could be more risky if it goes wrong.
I suspect in those two cases that something else had already messed with their phones to cause the boot problem.

[Q] MAJOR PROBLEM. Cannot S Off or Radio S-Off. BOOTLOADER CORRUPT

Hi everyone
I was advising somebody on rooting their Desire HD.
We got as far as installing the 1.32 stock ROM and I stupidly (and now I regret it so damn much) forgot about radio S-offing the device first so we tried Eng-S-Off. That said do not turn off the device because the bootloader is corrupt.
Then we tried the Radio S off tool and that said Unknown error, possibly connection.
How can we fix this?
EDIT: Will installing an RUU fix it?

raze599 said:
Hi everyone
I was advising somebody on rooting their Desire HD.
We got as far as installing the 1.32 stock ROM and I stupidly (and now I regret it so damn much) forgot about radio S-offing the device first so we tried Eng-S-Off. That said do not turn off the device because the bootloader is corrupt.
Then we tried the Radio S off tool and that said Unknown error, possibly connection.
How can we fix this?
EDIT: Will installing an RUU fix it?
Click to expand...
Click to collapse
Ya it will just do that way and do the rooting again after following these steps.....
find the stock splash screen here: http://forum.xda-developers.com/showthread.php?p=15430340&highlight=stock#post15430340
Uncompress that and put the .img file in the same folder as your fastboot file (in the Android SDK, it used to be in the Tools folder but nowadays they put it in the Platform-Tools folder), then open a CMD window, (Make sure the file is called splash1.img) and type:
fastboot flash splash1 splash1.img
That will restore the stock splash screen.
To restore the software you have to:
1: Find a 1.32.405.6 RUU that matches the original state of your phone. 2: Flash that RUU 3: Use Visionary R14 to Temproot and then Permroot 4: The Jkoljo's Easy Radio Tool to change the CID back to stock (If you phone was unbranded it will be HTC__001)
Now its ready to root again...
Hope that helps.

No I'm saying because the bootloader is corrupt, will installing an RUU restore the original bootloader?
There is no custom splash screen. We got as far as installing the 1.32 ROM.

raze599 said:
No I'm saying because the bootloader is corrupt, will installing an RUU restore the original bootloader?
There is no custom splash screen. We got as far as installing the 1.32 ROM.
Click to expand...
Click to collapse
I honestly think people are just copying and pasting stuff they've read somewhere without thinking about what they're saying. The bulk of that is nothing to do with the query you asked (apart from maybe the line about the RUU); I mean, replacing the splash image?! How's that going to help with a corrupted bootloader? Let alone telling you to download the full Android SDK just for that
On topic: the RUU should do it, but I've never tried it myself so you're probably safer waiting for someone with some actual experience to confirm before you flash. I have seen that error mentioned in one of the guides I used back when I rooted (January time), so I'll see if I can dig that out.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
---------- Post added at 08:07 AM ---------- Previous post was at 07:42 AM ----------
Okay, found it: a few people were having "bootloader corrupt" issues using the One-click ENG S-OFF tool.
Try the advice in that post (or maybe search that thread a bit further for mentions of "corrupt") before you waste time flashing a RUU. IIRC you can do Radio S-OFF & ENG S-OFF in any order (the ENG S-OFF tool has a box to tick whether you have Radio S-OFF or not); I don't think that's the problem here.

Thanks I will try that later. It seems like from the thread that if you didnt get a superuser message on the phone, nothing actually happened to the bootloader. We didnt get a superuser message on the phone. So could it be a false alarm and safe to reboot?
EDIT: By the way what the other user copied and pasted, I wrote originally lol but I didnt want to say that then in response.

raze599 said:
Thanks I will try that later. It seems like from the thread that if you didnt get a superuser message on the phone, nothing actually happened to the bootloader. We didnt get a superuser message on the phone. So could it be a false alarm and safe to reboot?
Click to expand...
Click to collapse
Yeah, that should be fine. If you didn't allow it root access when you ran it then it's not going to have been able to do anything. Reboot, clear the request in your superuser app and start again.
You don't mention it, but I assume you've already used Visionary to permroot before you tried the S-OFF tool? Just a thought when you mentioned you didn't get the su request on the phone.
raze599 said:
EDIT: By the way what the other user copied and pasted, I wrote originally lol but I didnt want to say that then in response.
Click to expand...
Click to collapse

Lol this is quite funny. I was actually instructing him over skype and then when I left Skype last night he did something and it worked lol THANK GOD!
I have no idea what he did but wierd things happen when I'm not looking lmao
Still though, since we have had some major problems, do you recommend that we install an RUU and start again from scratch? Just to avoid any future problems?
EDIT: Yes it was Permrooted, the superuser came up when he tried it himself and it worked.

I wouldn't bother personally; as long as you're s-off it doesn't matter how you got there. It's not like the phone's going to be left half s-on or something.
Besides, why let him waste time redoing that when he should be using that time to flash a load of new ROMs
//sent from my Desire HD using Tapatalk; all errors entirely intentional.

Thanks very much

Droid Incredible 1 - No Recovery Mode

Ok I'm going to try to explain this as simply as I can. First let me start by stating that I have searched high and low through XDA and about a dozen other websites in two hours with NO luck.
First, I downloaded CM7 and installed ClockWorkMod Recovery.
Second, I had it reboot in to recovery only to find myself staring a black screen with white bars. Upon further research I come to find that this panel type (slcd) is incompatible with recovery console (RLY?!) and that I am looking at the recovery console, its just blocked by a huge black image.
Third, I take it upon myself and figure I can just use ADB/SDK to flash this friggin' thing through the CMD prompt. But Ha-Ha this is not possible as I have S-ON listed in the HBOOT Menu
Fourth, I found a way to switch to S-OFF but come to find two things. One, this requires use of the recovery console which is inaccessible to me. Secondly, under the "Compatibility" list for the Droid Inc1 on Unrevoked Forever's site, it does not have the most recent Radio listed (Mine is currently 2.15.10.10.07.07 and theres no way in hell I'm attempting this with that said)
Does anyone have any suggestions or should I just give up?

Since your s-on you will need to do an ruu.exe, the one with your pc. (http://pvillecomp.com/?page_id=22) This will get you back to stock recovery. If you then want to go s-off you will need to downgrade with scottys downgrade tutorial found in the general section i believe, and then use unrevoked to gain s-off and root.

Thank you sir
I already had root through Unrevoked 1-click, I'll try this and see if I can flash Cyanogen through the ADB Shell.
Thanks!

Nechen said:
Thank you sir
I already had root through Unrevoked 1-click, I'll try this and see if I can flash Cyanogen through the ADB Shell.
Thanks!
Click to expand...
Click to collapse
I am not sure what you mean by having root and CM7? You mention in the OP that you still have S-ON? Not sure how you rooted and flashed an alternate ROM with S-ON...
Sent from my Dell Streak 7 using Tapatalk

WookieFan said:
I am not sure what you mean by having root and CM7? You mention in the OP that you still have S-ON? Not sure how you rooted and flashed an alternate ROM with S-ON...
Sent from my Dell Streak 7 using Tapatalk
Click to expand...
Click to collapse
I think you might be confusing S-off with Root, the two are not synonymous.

I had s-on the entire time, I just realized it about a month ago, I still had recovery, custom roms, ect.

simi brick?

I have hw 003 hboot 2.10. I can enter hboot but not recovery. during normal boot phone just shows evo boot screen and boot loops. same thing when I try to enter recovery. I was s-off but after trying some methods in other brick threads I ended up with s-on.
I was using miui 2.2.3 when I turned it rebooted into recovery to make a nand and that is when the loops started. I have tried several ruu's with no luck on getting it to boot. was going to try the lastest ruu but not sure if I should.
I am flashed for cricket so there is not the option of bricking and returning to sprint for a replacement.
Edit: was not using twrp. Ar 2.3 was my recovery. As stated earlier I tried several ruu's in pc36img.zip.

If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.

sitlet said:
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
Click to expand...
Click to collapse
You can be bricked and still get in hboot Twrp2.0 did it to a few phones, the partitions end up screwed up and you can boot to hboot but no recovery or system not sure which partition gets borked but I think its the misc partition
We are legion, for we are many

Where is Captain_Throwback to save the day and another evo once again

Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?

stevovanburen said:
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
Click to expand...
Click to collapse
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App

You weren't using twrp2.0 were u? If you were more than likely SOL that's one of the main reasons twrp for the evo is no longer supported even tho it works great on other devices like the kindle fire and 3vo I use it on the KF which I have running cm9 which I just got running on the evo as well now I gotta get my kernel fixed for this thing, have you tried reflashing your recovery? Or using adb to push a boot.img
Sent from my PC36100 using xda premium

evo4gnoob said:
Where is Captain_Throwback to save the day and another evo once again
Click to expand...
Click to collapse
I know. Captain has become the shaman of the Evo. He needs a special title, like Honorary Genius, or something.
sent from AOKP heaven

You guys flatter me .
I don't have any experience with MIUI, though. It's the one ROM I've never tried, but if it's an AOSP ROM, then the bootloop of death is always a possibility.
We haven't had any success rescuing anyone in that scenario, unfortunately. Flashing the ENG HBOOT will allow you to run fastboot commands, though, so that's probably the first step if you want to flash stuff through fastboot.
If you can't get adb working, then there probably isn't much hope. Since you ended up S-ON, and now without a custom recovery, I don't think there's much you can do. Perhaps others with a similar issue can chime in, but as far as I know, there's no current solution. The only way I'd know for sure is having the phone in my hands personally, but I doubt that's a possibility. I haven't personally experienced this bootloop thing, but it sounds scary .

jlmancuso said:
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
Click to expand...
Click to collapse
Ok so I have unlocked the bootloader from the htcdevelopers site and i can now use fastboot commands and have tried flashing the recovery. I see it load and write to the phone only thing is that it makes no difference. I still just get the boot loop.

Hate to say it, my friend, but I think it's the end of the road for that phone

HipKat said:
Hate to say it, my friend, but I think it's the end of the road for that phone
Click to expand...
Click to collapse
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.

jlmancuso said:
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
Click to expand...
Click to collapse
I assume you're referring to this thread: http://forum.xda-developers.com/showthread.php?t=1480630
Have fun trying! Many have tried, and I think only 1 ever succeeded.

thanks captain.

capn, thanks for the link! I've had that README_EVO.docx file on my SD for god-knows-how-long and have always wondered where in the hell I got it lol (and 'why').
@jlmancuso
Good luck, but condolences as well. My $ says, if Cap'n can't fix it, it likely can't be fixed (on Evo). Seems that guy has explored every RUU, Hboot, recovery, NV, Radio, kernel etc. He could probably BUILD an Evo, HW and SW lol.
sent from AOKP heaven

Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??

fatalfury said:
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
Click to expand...
Click to collapse
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
EDIT: This is the thread - you'll probably want to read the whole thing, and if you have issues, maybe you can PM the guy that got it working.
The potential problem I see for you is that you're S-ON and bootloader is locked. You're probably going to have to unlock your device with HTCDev.com before you can make any headway. How were you able to write NV items to the phone? Don't you have to be S-OFF to do that?

Captain_Throwback said:
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
Click to expand...
Click to collapse
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?

evo4gnoob said:
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
Click to expand...
Click to collapse
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.

Captain_Throwback said:
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Click to expand...
Click to collapse
use HTC dev to unlock then use your guide to downgrade then root with revolutionary then downgrade hboot ?