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 ?
Related
i have installed the gingerbread keyboard file on my sd card and have rooted my phone using the visonary method but now i cant seem to get into recovery mode. I have rom manager installed and have flashed clockwork recovery mode. it said that it had sucsessfully installed.
I then flashed it again as i read somewhere that i might need to do it twice as sometimes it dosent work.
when i now click on the recovery option in rom manager all i get is the red triange with the ! in the middle.
any ideas what im doing wrong?
Have tried reading the threads but with 30 plus pages i am now completley confused
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
just done the hboot hing and at the top of screen it says
vision pvt ship s-on
hpsauce37 said:
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
Click to expand...
Click to collapse
It's a bit confusing because there is more than one way to do this. But by far the safest way is to follow the guide at http://forum.xda-developers.com/showthread.php?t=857390
Have a good read, then if you're not sure, ask questions in that thread on the process.
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Click to expand...
Click to collapse
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
steviewevie said:
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
Click to expand...
Click to collapse
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Click to expand...
Click to collapse
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
steviewevie said:
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
Click to expand...
Click to collapse
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
Click to expand...
Click to collapse
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
hpsauce37 said:
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
Click to expand...
Click to collapse
Have you tried my guide on adb ? http://forum.xda-developers.com/showthread.php?t=865685
OK, I can use some help too
I have a DZ with stock ROM, root and s-off and CWR.
In my enthusiasm that I knew how to flash rom updates with clockwork (I am running the Godspeed 1Ghz) I downloaded the Gingerbread keyboard rom update from the G2 forum. I think I jumped off a bit too fast...
And now I am stuck in an infinite boot loop. I can get into Clockwork recovery but it just loops the "HTC Quietly Brilliant" forever including the annoying boot sound...
I tried some suggestions to download and reflash a second time, no effect.
I tried to mount /system before flashing, no effect.
Am I forced to go back to factory now?
Also, I found 2 gingerbread keyboards, one in the G2 forum and one over here.
Anyone know what the difference is? They have a different filesize..
Any help is welcome...
*edit*
OK so now I read that it is only to be flashed on a non-stock ROM... so I am now flashing Cyanogen 6.1
try wiping all the caches...
Lennyuk said:
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
Click to expand...
Click to collapse
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Click to expand...
Click to collapse
S'alright.
HTC really ramped up the security on these new phones, as Lenny said, with this hardware write-protection on certain partitions. But even given that, I was amazed by just how quickly the guys on the #G2ROOT IRC channel, especially Scotty2, managed to crack it !
It also looks like they've opened the phone even wider than many others before, with the "true" radio S-OFF that they achieved.
You can read up all about it in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
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.
I was Flashing the OTA 2.2 Froyo Leak a while ago and it just didnt finish for some reason. Now when I try to turn it on it Vibrates 5 times and has a green blinking light.
Also it is S-ON now for some reason as well.
I have looked everywhere and cannot find a solotion.
Any help is appreciated.
Edit* I have tried flashing other roms and still nothing, (I can access HBOOT but not Recovery) and I cannot flash recovery either. Everything but Hboot is gone. And i tried flashin Ruu and it says main system too old.
5 Vibrates is usually some kind of hardware issue, where-as 3 vibrates is usually a software issue.
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
carngeX said:
5 Vibrates is usually some kind of hardware issue, where-as 3 vibrates is usually a software issue.
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
Click to expand...
Click to collapse
How can I get S-OFF then? I can access Recovery but it doesnt do me any good it wont read my sd card.
I have no idea what I did, but it rebooted itself and its working
this is EXTREMELY weird. I had the phone plugged in because I wanted to root, but i was first getting the SD Card files off and when I unplugged the phone the same thing happened already....
So then I plugged the phone on again, went into HBOOT and ran the image until it told me it cant be read, and rebooted and back to normal....
Any idea what happened? I just wanna get opinions out of curiosity.
cvbcbcmv said:
cool. But no you don't want to be s-off for flashing the RUU back to stock, then you actually flash a s-on image first.
Click to expand...
Click to collapse
He said he was trying to flash recovery and other ROMs to try and get it to work though too... You can't flash custom recovery without being S-Off.
If you want to flash back the RUU, and go back to complete unrooted stock... then yeah, you want S-On.
carngeX said:
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
Click to expand...
Click to collapse
Untrue, you can flash ROMs without being S-OFF. I was rooted and flashing ROMs before unrevoked released "forever."
Sent from my Droid Incredible running a random CM7 nightly.
it seems the problem is more serious then i imagined... I cant seem to use my phone.. when i connect it to the computer its unrecognizable and I cant do anything with it
SteveG12543 said:
Untrue, you can flash ROMs without being S-OFF. I was rooted and flashing ROMs before unrevoked released "forever."
Sent from my Droid Incredible running a random CM7 nightly.
Click to expand...
Click to collapse
So were the images previous to Unrevoked's S-Off patch just signed properly? I didn't get a DINC and root it until after Unrevoked had released their patch.
eljean said:
it seems the problem is more serious then i imagined... I cant seem to use my phone.. when i connect it to the computer its unrecognizable and I cant do anything with it
Click to expand...
Click to collapse
Like I said previously, 5 vibrates is usually a hardware issue, meaning you're most likely going to have to send it in for replacement. There's been a few people to recover from a 5-vibrate brick, but they had gotten lucky. You can search the forums and try to find how they fixed it (can't remember the thread off hand, just do a search for 5 vibrates and you'll get lots of results).
carngeX said:
So were the images previous to Unrevoked's S-Off patch just signed properly? I didn't get a DINC and root it until after Unrevoked had released their patch.
Click to expand...
Click to collapse
I guess so, idk tbh lol. I've had my Inc since day one, and rooted it rather early.
Sent from my Droid Incredible running a random CM7 nightly.
yeah except i bought off ebay so i cud flash to boost. and i did but then i got too curious and ended up with bad nv items on the phone fixed it, then my meid came as <not available> (which still remains and i believe is the problem) and now this... i cant unplug my fone or it will die on me...
i need to get S-OFF and i might be able to fix it... any ideas on how to do this through HBOOT
i need to flash a rom thats what i need to do, because ihave no drivers.., thats the hardware issue and my meid but thats not importatn
Try using unrevoked while the phone is plugged in and in fastboot/hboot?
k_nivesout said:
Try using unrevoked while the phone is plugged in and in fastboot/hboot?
Click to expand...
Click to collapse
How can this be possible? Can you just show me a quick summary and show me links to this method of rooting
Sent from my ADR6300 using XDA App
Just google unrevoked and download the unrevoked tool. I thought it did its thing in fastboot, but I could be wrong. Its worth a shot.
And BTW, its not really necessary to be posting multiple threads in multiple forums, it would be easier for you to just check one thread.
fixed it
http://forum.xda-developers.com/showthread.php?p=14440621
k_nivesout said:
Just google unrevoked and download the unrevoked tool. I thought it did its thing in fastboot, but I could be wrong. Its worth a shot.
And BTW, its not really necessary to be posting multiple threads in multiple forums, it would be easier for you to just check one thread.
Click to expand...
Click to collapse
Oh no is I bought 2 bricked phones from ebay as a wholesale and im trying to fix both of them which have different issues.
eljean said:
fixed it
http://forum.xda-developers.com/showthread.php?p=14440621
Click to expand...
Click to collapse
oh **** theres a fix for this lol i never knew
JoelZ9614 said:
oh **** theres a fix for this lol i never knew
Click to expand...
Click to collapse
Yeah the guide was released last month
Sent from my ADR6300 using XDA App
Incrediblec XD ship S-On
Hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Hello, first thank you for an amazing and current forum, I'd been researching my issue for a while, but most things are dated around 2010. I've experience rooting and ROMing a Droid X with multiple ROMS, but I use the original Incredible as my main phone because I still love it. Well, I originally rooted my Inc with Unrevoked3 I believe. I left the ROM as stock up until a couple months ago when I put CM7.2.0 on it.
About a week ago, the phone would always have working mobile data. Yet, if I received or tried to make a call, I couldn't and then I would lose texting ability. Then, a couple days ago, I was using the Inc for wifi tethering when suddenly it went into an Incredible bootloop. I tried booting to the cyanogen recovery, but it will quickly loop out of it as well.
I went to pvillecomp.com/ and downloaded all the stock Inc software. I individually renamed files to PB31IMG.zip and tried to have HBoot pick up on them. Hboot will see the files, but then do nothing. Except, the originally ROM will get checked and come back and say that the current version is older and can't be flashed.
I've always tried the RUU software for hboot and the original ROM. I either get a usb error or a low battery error even if the battery is charged. Granted, I'm trying the RUU from the phone's bootloader screen.
Does anyone have some support they could throw this way? I use my phone for internet and everything. Thank you all.
-Nevin
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
did you flash any radios? Flashing radios always ends up bad.
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
123421342 said:
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
Click to expand...
Click to collapse
Btw, no I didn't flash the radio. That was the only thing I didn't attempt to flash. Yet, when attempting to flash anything else, nothing worked. Still wondering about getting S-off before using TWRP, but hopeful to still get it working. Thank you again.
NevinInc said:
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
Click to expand...
Click to collapse
BUMP/UPDATE:
Yes, I'm still at it trying to get my Dinc out of it's bootloop and up/running. It's difficult at this point to say what all I've tried. At one point I wanted to use htcdev.com to ensure the bootloader was unlocked/etc. I've had much trouble trying to get fastboot to work correctly on my pc. I've seem to get stuck on "waiting for device" which appears to be a driver error.
I gave up on that and started focusing on the RUU process. I've tried to install the entire Gingerbread 605.3 file. I fixed the error usb 170 by updated or changing htc sync software. Now I'm left with error 140 bootloader error.
I've also updated hboot using the ruu process for version 605.2. This worked on my pc and got me partially excited. Now my hboot shows up as "Locked" now at the top. I also downloaded a different Stock.img file. Hboot detected this and begun the install process. Everything came up as complete and upon reboot went right back into the white screen/incredible bootloop.
So since posting before I've updated htc sync on my pc and have officially relocked my bootloader. I don't mind RUU'ing things to stock, but now gotta get past the Error 140. Any ideas?
So I'm not sure how many are looking at this or have had ideas, but I was able to use htcdev to unlock the bootloader.
Before unlocking the bootloader I was able to RUU to image .15. After this is when I unlocked the booloader. The RUU said it was complete, but I still only bootloop on the incredible white screen. Now, some of the pb31img.zip files I've come across don't even try to install. This includes signed and unsigned .15 img files. Currently these are the new settings to the phone:
Bootloader: unlocked, s-on
hboot 1.07.0000
radio - 2.15.10.12.20
Image version: 4.08.605.15
The last option I can think of is to try using fastboot, but won't that essentially do the same thing? If you think fastboot is the way to go, can u link me or give me some basics on using it. Obviously I used it for unlocking the bootloader so it can't be that complicated.
Are there any other ideas or should I give up on my Dinc? Looking forward to hear what you think. Thanx.
-Nevin
somebody recommended you install TWRP and install a stable Jellybean ROM. Did you try that?