Related
I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.
ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery
ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery
Anyone? Bueller?
cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.
This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.
I've searched the forums and have not found a situation that really matches mine.
I've been running on a Cyanogen nightly build for probably two months with no problems. Out of nowhere this morning my phone reboots itself (while it was idle; I wasn't even touching it) and then gets stuck in a boot loop. I get the White HTC Evo 4G screen, then it powers off and comes back up to the white screen again. Over and over.
All I can get do is hboot. Even telling hboot to go into the recovery mode puts my back into the boot loop. Fastboot, clear storage, and hboot usb all seem to work though. I've tried downloading the PC36IMG.zip file (http://forum.xda-developers.com/showthread.php?t=780141) in that thread, but hboot loads it and tells me that it is older than my current version, and only gives me the option to reboot, or not to reboot. Doesn't load the image.
Here is the information on my hboot screen:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:08
Anybody have any ideas? Thanks!
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
NewZJ said:
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
Click to expand...
Click to collapse
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
luck has been wished
Kuhmo said:
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
Click to expand...
Click to collapse
This didn't work. Everything is still the same, except that my hboot version is now 2.10.0001. Any other thoughts?
still won't not into any rom? did you get errors?
NewZJ said:
still won't not into any rom? did you get errors?
Click to expand...
Click to collapse
No, the app on the PC said everything was successful. The progress bar on the phone progressed without errors too.
what happens when you reboot the phone not going into bootloader?
Just the HTC EVO 4G splash screen. Over and over and over...
does it show the boot animation or just stuck on splash?
Just the splash. No animation.
pull the battery, remove your sdcard, put the battery back in, see if it gets to the animation
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Wrong button..
xHausx said:
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I asked my wife to check this thread from the car on the way to dinner. Saw the response. So I took my laptop inside with us and used the RUU one more time. No luck. I decided that it must be a hardware issue. I took the SD out and removed the evidence that the phone had been rooted, then took it to the sprint service center up the road. They just replaced it for me. Thanks for your time! I DO want to root my phone again, the ROMs are just so much better than the stock installation. Should I not install the OTA updates if I'm going to root it? Which guide should I follow for rooting?
never do OTA when rooted, use unrevoked to root, unrevoked.com
NewZJ said:
never do OTA when rooted, use unrevoked to root, unrevoked.com
Click to expand...
Click to collapse
Not when rooted. I meant should I update to the latest OTA UNTIL I decide to do the root again? Is the latest OTA unrootable?
Same deal.
Here is the post that I put in the wrong forum that I was about to post here until I saw this thread...
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
run the ruu to s-on then trade for another
NewZJ said:
run the ruu to s-on then trade for another
Click to expand...
Click to collapse
Ack, sorry... didn't mention in previous post. I fired up windows to run the RUU (I don't trust wine to that stuff) but it couldn't detect the device.
Hey all,
***ISSUE*** I can only boot into recovery or a ROM once. ***ISSUE***
I recently replaced my EVO through Sprint, and rooted. (unsuccessfully with unRevoked, but successfully with AutoRoot). After I used unRevoked (but before using AutoRoot) this issue started popping up.
I can flash a recovery image via Bootloader/Hboot or PARTICULAR ROMs, Sprint Lover's seems to be the most reliable, CM7 does not seem to work at all, and be able to access them once, and upon reboot I get the white "htc EVO 4G" screen and it hangs there until I reboot. Once that happens I cannot access recovery or boot into the ROM until I reflash from a PC36IMG.zip in Hboot/bootloader.
Here's my hardware info:
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Hardware Revision #3
My Evo was originally on HBOOT 2.10, but I flashed an eng-PC36IMG.zip that let me install the ENG bootloader on it, which has made it so things flash more reliably.
Anyone have any advice? It seems really odd to me that software would work once and not again. Any suggestions would be appreciated.
There could be something from the rooting process that's affecting your phone somehow, although that's really strange. I would suggest unrooting, getting fully back to stock, & rooting again. If you're not going to be able to reboot your phone without reflashing, which seems like a pain, it might be best to redo it.
Other than that, I'm baffled :/
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App
Thanks for the reply, plainjane!
I am in the process of unrooting now to see if that works. I installed the unrevoked-son via ClockworkMod Recovery 3.0.0.5, but I still had S-OFF when I went to HBoot. I'm not sure, but I think I remember somewhere that the ENG bootloader does that.
Regardless, I'm installing the latest (3.70) RUU now and will see what that does.
RandomViolence said:
Thanks for the reply, plainjane!
I am in the process of unrooting now to see if that works. I installed the unrevoked-son via ClockworkMod Recovery 3.0.0.5, but I still had S-OFF when I went to HBoot. I'm not sure, but I think I remember somewhere that the ENG bootloader does that.
Regardless, I'm installing the latest (3.70) RUU now and will see what that does.
Click to expand...
Click to collapse
Yea, im pretty sure the. 76 eng hboot is permanently s off. Also, I was unaware that hboot version 2.1 was downgradeable, I thought it wasn't able to be changed. Interesting. Maybe that's part of your problem, im really not sure. Sounds annoying though. Hopefully unrooting and starting fresh will help.
Sent from my PC36100 using XDA App
Thanks for the reply k2buckley!
I've now run the S-ON tool and used the 3.70 RUU to unroot my Evo. After the RUU completed its process my EVO rebooted and has not left the white "HTC EVO 4G" screen. (EDIT: I checked in Hboot and am now S-ON and on the 2.10 bootloader.) I've let it run for about ten minutes now and I'm not hopeful.
Now that I have it in a state where I can return it to Sprint I don't think I'm going I'm going to mess with it any more. It's such a shame. My first Evo was wonderful until an odd software glitch bricked it, and now this. It's been a really frustrating couple of weeks.
After this experience I don't think I'll be using unrevoked again. I loved having the speed and features of CM7 on my first Evo, but I'm debating rooting at all at this point.
RandomViolence said:
Thanks for the reply k2buckley!
I've now run the S-ON tool and used the 3.70 RUU to unroot my Evo. After the RUU completed its process my EVO rebooted and has not left the white "HTC EVO 4G" screen. (EDIT: I checked in Hboot and am now S-ON and on the 2.10 bootloader.) I've let it run for about ten minutes now and I'm not hopeful.
Now that I have it in a state where I can return it to Sprint I don't think I'm going I'm going to mess with it any more. It's such a shame. My first Evo was wonderful until an odd software glitch bricked it, and now this. It's been a really frustrating couple of weeks.
After this experience I don't think I'll be using unrevoked again. I loved having the speed and features of CM7 on my first Evo, but I'm debating rooting at all at this point.
Click to expand...
Click to collapse
If you do, root it manually - save yourself from all these headaches of the autoroot programs.
Thanks for the advice Heaterz16!
I'd love to root manually to ensure everything goes well. The guide that I saw indicating how to manually root was taken down and linked to AutoRoot as the way to go. Could you point me towards a guide for manual rooting?
Take it back to Sprint. I had one that would rarely boot, it would take 20 or so tries. When it finally did boot, the screen would freeze up & I'd have to pull the battery. They gave me a new one, no questions asked & I had it the next day. That phone was never rooted, it was only two weeks old. I have insurance, so all of my replacements have been free. I had the one before that 3-4 weeks before the usb port gave out. I got my third one three months ago, rooted it, and have had no problems since. I hated the Evo for about a month when mine kept breaking.
I would also suggest manually rooting. The "one-click" methods are easy to do but difficult to troubleshoot. Manual methods are a little more difficult to do but cause far less problems.
Just remember to delete any evidence of rooting from your sd card or just remove it entirely before taking the phone to Sprint. I hope everything works out for you!
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App
plainjane said:
Take it back to Sprint. I had one that would rarely boot, it would take 20 or so tries. When it finally did boot, the screen would freeze up & I'd have to pull the battery. They gave me a new one, no questions asked & I had it the next day. That phone was never rooted, it was only two weeks old. I have insurance, so all of my replacements have been free. I had the one before that 3-4 weeks before the usb port gave out. I got my third one three months ago, rooted it, and have had no problems since. I hated the Evo for about a month when mine kept breaking.
I would also suggest manually rooting. The "one-click" methods are easy to do but difficult to troubleshoot. Manual methods are a little more difficult to do but cause far less problems.
Just remember to delete any evidence of rooting from your sd card or just remove it entirely before taking the phone to Sprint. I hope everything works out for you!
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App
Click to expand...
Click to collapse
Thanks for the advice. I plan to just go to Sprint without my SD card and tell them the situation.
If you could point me towards a good guide for manual rooting I'd be grateful. After this last experience I'd much rather just do it myself and ensure it goes correctly.
Unrevoked gives issues like this. Try to start with autoroot this time.
Do not try to downgrade your bootloader this time. Make sure you nandroid back up and flash different ROMs and ensure things are working before you set anything up. Also make sure you are wiping everything. I suggest using Caulkin's Format All and flashing that in recovery.
sekigah84 said:
Unrevoked gives issues like this. Try to start with autoroot this time.
Do not try to downgrade your bootloader this time. Make sure you nandroid back up and flash different ROMs and ensure things are working before you set anything up. Also make sure you are wiping everything. I suggest using Caulkin's Format All and flashing that in recovery.
Click to expand...
Click to collapse
Thanks for chiming in, sekigah84.
The reason I tried downgrading my bootloader last time was that the issue appeared consistently with the 2.10 bootloader (tried flashing various recoveries, ROMs, radio versions, etc, over four days on that bootloader) and I thought reverting to ENG 0.76 might help correct the problem. I was very careful about doing nandroid backups and wiping cache, dalvik before installing ROMs, etc. when I could access recovery. Restoring from a backup was never possible because upon reboot I'd simply get the white HTC screen.
The problem seemed to start immediately after using unrevoked and didn't go away regardless of what I flashed or how many times I RUUed.
I definitely won't use unrevoked again. I'd consider using AutoRoot, but I'd prefer just to do a manual root process, or maybe not root at all.
RandomViolence said:
Thanks for the advice. I plan to just go to Sprint without my SD card and tell them the situation.
If you could point me towards a good guide for manual rooting I'd be grateful. After this last experience I'd much rather just do it myself and ensure it goes correctly.
Click to expand...
Click to collapse
Here's a link for you. As you said, this post has been retired, and it links you to xhausx's autoroot, however it still contains all of the info and instructions, and that method will still work for you. It's not outdated yet. So if you want to run it manually, follow Zikronix's instructions within the first post of this thread. Have fun!
http://forum.xda-developers.com/showthread.php?t=829045&highlight=root
I'm trying to return a MyTouch Slide to stock but it seems who ever rooted it before did a sloppy job. I do not own the device and have only done this with an Inspire 4G and a Galaxy S2 so this device is a bit new.
The device at this point has CyanogenMod 7, non S-OFF and ADW.Launcher. There is not recovery on it (Got a red triangle when tried getting into it from HBOOT). My laptop wont recognize it to run the FroYo update from HTC.
Please help me fix this phone.
So far I have downloaded AlphaRev which I will try, as well as the CWM update.zip
If i understand correctly this should get me Recovery so I can then flash a new ROM and be on my way to getting it back to stock, correct?
I hate to be the noob in a forum but thats where I'm at.
Edit:
http://forum.xda-developers.com/showthread.php?t=798168
If I flash the ESPRIMG.zip under "Still Having Problems", will that load the phones as if new from the box?? It says it wipes everything and returns to stock, root, rom, etc.
Yup, that's all you have to do. Flash the esprimg.zip and you're good to go.
The fix was successful. Phone is back to factory eclair and running solid
Sent from my SAMSUNG-SGH-I777 using Tapatalk
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 ?