Ok so is it worth risking this happening again. I see more and more threads pop up with this problem and everyone says its a Qualcomm issue but why does it only happen on rooted phones? Can it be safe to say that maybe Unrevoked forever doesn't work well? There is an issue with how it unlocks the phone? Just putting it out there cause i had this problem and now i have been holding on to my new incredible and of course this phone SUCKS stock and i want to root but not looking forward to brick and spend more money.
This post makes no sense to me what so ever. All I can get from it is that you somehow lost root on a previous phone and your saying its a known issue with the processor? Or that somehow rooting it caused the problem? Who knows your very vague about your precise issue. I've had no issues what so ever with my Inc since getting it in November and rooting it in December.
Same here no problems with unrevoked
sent from my re-engineered dInc
Im not posting an issue if u look around u will read plenty of posts dealing with people loosing S-on, phone vibrates 3-5 times then blinking light not able to turn phone on, not able to access the SD card, USB not working... From my exprienace this is all caused from the S-on being mysteriously turned on.
From what i read people are blaming the Qualcomm diagnostics mode. Im just asking could it possibly be something that Unrevoked Forever is doing that sets this to happen down the road? I ask becuase if it was a Qualcomm issue then why dont other Incredible users (non rooted) have this issue?
I had my Incredible since they first came out and i never had an issue till i routed but even then i ran roms for 6 months with no problems. So why is it all of a sudden doing this?
kzoodroid said:
This post makes no sense to me what so ever. All I can get from it is that you somehow lost root on a previous phone and your saying its a known issue with the processor? Or that somehow rooting it caused the problem? Who knows your very vague about your precise issue. I've had no issues what so ever with my Inc since getting it in November and rooting it in December.
Click to expand...
Click to collapse
I was all happy to for 6 months and then one morning my phone was working fine until i simply unlocked the unlock screen and she rebooted and that was it... i wish u luck and hope u dont run into this issue
ancora76 said:
Im not posting an issue if u look around u will read plenty of posts dealing with people loosing S-on, phone vibrates 3-5 times then blinking light not able to turn phone on, not able to access the SD card, USB not working...
Click to expand...
Click to collapse
ancora76 said:
I was all happy to for 6 months and then one morning my phone was working fine until i simply unlocked the unlock screen and she rebooted and that was it... i wish u luck and hope u dont run into this issue
Click to expand...
Click to collapse
What, you just contradicted yourself?
Wow!!! did i really or did u only read the last post? ok how about this if u havent had this problem then move on becuase obviously you have no clue what i am saying...
ok let me use the same language i use with my kids.... since there is a problem that nobody knows how to fix or how it even starts.... is it worth rooting and risking buying another phone if u cant un root to send in to verizon?
When u root u can do anything even unroot, and the s-on problems are only occuring because people are stupid so they do random stuff that leads to s-on like factory reset
Sent from my ADR6300 using XDA App
I don't read every thread on here so I don't know what you were first talking about. I got a newer SLCD screen Inc with s-on and had to wait for a newer version of unrevoked to be made before I could root. One of the things the new unrevoked 3.21 did was set phone to s-off automatically. The older version, the one that you had to have used originally did not do the s-off trick, that was a seperate program that you had to download (unrevoked forever). So no I don't think that unrevoked did something to your phone that latter caused the s-off problem. You might have flashed some ROM or zip file that did this, who knows what these people are posting on here and I am some what cautious when I flash a zip file. I wait a while and see if any one is posting problems in the thread before I pull the trigger. Or as the poster above said maybe you tried a factory reset or flashed a PB31img file who knows.
I want to add something here. S-off and rooting are two seperate things. You can root your phone and still have s-on, you just cant use fastboot if something goes wrong. So there are advantages to s-off but its not necessary to have. Are you absolutely sure that you even had s-off to begin with? You would have had to have run Unrevoked Forever to get it if you rooted before December of last year. Unrevoked 3.21 was the first version to incorpoarte the s-off feature into the rooting program iteslf.
Yes i had S-off.. Yes i ran unrevoked forever... now i tried unrevoked3 and yes that does set it to S-off. No i didn't do any flashing what so ever... the last time i flashed was when warm 2.2 came out and ran it for 2 months or so with no problems.... one day i woke up went to work made a few phone calls and texts put phone away picked it up maybe an hour later and she restarted and that was it.. do some research and u will find a ton of posts with the same problem. Believe it or not this isn't my first, second nor third phone that i have rooted so i do have a pretty good idea what i am doing. This is something i have never seen nor heard about until it happened to me. I wish all those people that had the same problem could update what happened or what they did to either fix the problem or possible way of avoiding it.
unrevoked forever = Android phone's security level to S-OFF
The security level is a flag stored on the radio; when the flag is S-OFF
Unrevoked forever change is stored in the radio's NV memory
Knowing this is there someone with programming skills or something out there who could explain if it is possible for an app or maybe some kind of upgrade or anything i dont know that could be the reason why some phones are just switching on their own? Maybe the factory reset done with a new Rom might set it to S-on? Or maybe an over the air upgrade? Even though that is not what i did im just trying to find a starting point to possibly help tackle this issue which i feel we are going to see more and more of. One last thing i can say is that when my phone restarted i was able to power it on once but was having issues with the SD-card being read so i restarted it again and that was the last time i was able to fully boot my phone.
ancora76 said:
Yes i had S-off.. Yes i ran unrevoked forever... now i tried unrevoked3 and yes that does set it to S-off. No i didn't do any flashing what so ever... the last time i flashed was when warm 2.2 came out and ran it for 2 months or so with no problems.... one day i woke up went to work made a few phone calls and texts put phone away picked it up maybe an hour later and she restarted and that was it.. do some research and u will find a ton of posts with the same problem. Believe it or not this isn't my first, second nor third phone that i have rooted so i do have a pretty good idea what i am doing. This is something i have never seen nor heard about until it happened to me. I wish all those people that had the same problem could update what happened or what they did to either fix the problem or possible way of avoiding it.
unrevoked forever = Android phone's security level to S-OFF
The security level is a flag stored on the radio; when the flag is S-OFF
Unrevoked forever change is stored in the radio's NV memory
Knowing this is there someone with programming skills or something out there who could explain if it is possible for an app or maybe some kind of upgrade or anything i dont know that could be the reason why some phones are just switching on their own? Maybe the factory reset done with a new Rom might set it to S-on? Or maybe an over the air upgrade? Even though that is not what i did im just trying to find a starting point to possibly help tackle this issue which i feel we are going to see more and more of. One last thing i can say is that when my phone restarted i was able to power it on once but was having issues with the SD-card being read so i restarted it again and that was the last time i was able to fully boot my phone.
Click to expand...
Click to collapse
Oh and yes i formatted the card properly and tried other SD-cards.
Yes over the air updates will unroot the phone and can reset the security back to s-on. Most custom ROMs have the update feature disabled for this reason. Same thing with some of the PB31img files out there as that is what people are using to unroot there Incs to send back to Verizon. If say you had an old PB31img file on your sdcard and the phone rebooted itself into recovery somehow it could have launced that update and unrooted the phone. Stranger things have happened. When I had my Eris the leaked versions of Android 2.0 changed the hboot on the Eris which made them impossible to root for a very long time. People were then using the leaks to unroot their phones to ship back to Verizon. My Eris bricked, wouldn't even turn on though you could feel it get warm, for no known reason and I just sent it back in and got another. I was actually trying to run a method to turn the s-off when it happened. Which I then immediately tried again on the replacement without any problems.
ancora76,
I too have noticed the rash of threads with phones that won't boot, vibrating 3 or 5 times, and mysteriously going back to s-on. If memory serves me though, seems some people were messing with their sdcard at the time, flashing a rom, or restoring a nandroid.
I think we're seeing it on rooted phones just because we're always changing things, and flashing updates. There's a lot more potential for error. The regular stock phone user is only installing apps. Their phones are locked, thus protecting them from risk of all the things we do.
My guess is, some of the problems are actual hardware issues, and others are just user error and/or people flashing downloads with bad md5's.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01
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.
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 know theres probably a thousand topics on this but none of them seem to have the same exact problem or they do and dont have a solution. I can boot my ROM and i cant boot recovery. the only thing i can get to is HBOOT. I have tried many of the PB31IMG.zip files but none of them work. i have also tried the RUU exe program but that did not work either. im kinda graspin at straws here cuz i dont have a phone right now. im also wondering if i should just take it to verizon, but with that im worried about them finding out its rooted, because it still says "S-off" on the HBOOT menu. Any suggestions on what to do?
To my knowledge if you are in a bootloop with no secondary recovery such as Amon-Ra or CWR, the only other option is the RUU downgrade your Inc through the Android HBOOT Recovery. Use these guides here:
http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
I have tried that exact process, both options, to no avail...thanks though. Is there any way to revert S-Off back to S-on through HBOOT?
gdaysoccer said:
I have tried that exact process, both options, to no avail...thanks though. Is there any way to revert S-Off back to S-on through HBOOT?
Click to expand...
Click to collapse
For whatever it's worth, my phone was s-off when I took it in to Verizon. (I was having the vibrations-of-death)
They saw the phone wasn't booting up, and even saw my unrevoked splash screen, and that was good enough for them to send me a new phone.
Honestly, I don't think a majority of those sales reps would even know how to get into hboot, and really don't know a whole lot about Android. I'm not saying it'd be impossible to get someone that lurks XDA in their spare time, but... it's unlikely.
And if they did lurk xda they probably wouldn't make an issue of you being rooted
Sent from my ADR6300 using XDA App
I actually just had the same issue as you and spent around 21 hours trying to get things fixed with a few devs and we had no luck. basically the phone would act as if it would take the ruu flash and claim it did and update the hboot like it did but made no change in order to complete a boot cycle. I had no recovery no rom just hboot and fastboot worked. every other option failed. we chalked this up to a hardware failure of some sort. I flashed the lastest Ruu and called *611 explained the problem and they overnighted me a new inc. I still have S-off on the phone but every other item radio/hboot/kernal is all stock. I doubht they wil lreally notice the S-off. all in all the phone is back to stock full wipe. Good luck.
I ended up taking it to the Verizon store today and the rep thought it might have been the battery so he tried a new one of those, but that wasnt the issue. I'm pretty sure he booted into HBOOT because he was playing around with the power and volume buttons, but he didnt ask me anything about it being s-off or rooted or anything and so theyre sending me a new phone, because unluckily they didnt have any in stock at the store i went to, and i have to send this one back. So, so far, it looks like no one really cares or even knows where to check for it being rooted.
Ok, a few users here have offered advice/assistance, but I fear this problem has been forgotten.
I am stuck with an S-ON, 2.3.4 Droid Incredible, and am looking for a way to acquire root again.
This happened a few weeks ago, with the leak of the 2.3.4 OTA. Flashed S-ON via CWM (not aware I would permanently lose Root), then flashed the OTA as PB31IMG.zip in HBOOT.
Now, Unrevoked no longer roots the device. HBOOT will not allow downgrading to a 2.2 IMG, nor will it flash any downgraded Radio/HBOOT versions. I've tried them all from Dougpiston.com, even the signed ones.
I've attempted to contact the folks at Unrevoked about this issue on IRC, but I can't ever get a reliable dialogue going with anyone, and I believe they are busy working on Revolution, for Incredible 2/S & Newer devices.
Throwing my hands up, I even called Verizon, gave them an excuse to send me a replacement, just so I could start fresh with a 2.2 phone, but I am out of warranty.
I really want to enjoy Sense 3.0/MIUI, even Cyanogenmod, but the outlook is not so good.
Is there any solution I haven't tried yet? Please help.
Unless Unrevoked or someone else finds a new root method you're pretty much out of luck.
Sent from my Droid Incredible 3D using XDA App
Yep, same situation here, nothing will re-root if you did the GB OTA with S-ON bootloader. just have to wait and see if somebody comes up with something new or Unrevoked comes up with a new method.
EDIT: and I'm willing to bet if you get one from Verizon it might already be 2.3.4
resyek83 said:
Yep, same situation here, nothing will re-root if you did the GB OTA with S-ON bootloader. just have to wait and see if somebody comes up with something new or Unrevoked comes up with a new method.
EDIT: and I'm willing to bet if you get one from Verizon it might already be 2.3.4
Click to expand...
Click to collapse
That's most likely true. 2.3.4 is being pushed out to the Incredible now, so they would probably run the newest RUU on their Incredible devices.
I feel your pain deadsoulboy, and I've seen your posts lamenting your situation on other threads. Only solace I can offer you is that generally the source code and RUU are made available within 30 days of the OTA, at which point the developers are completely free to tear into them with reckless abandon and hopefully the folks at unrevoked figure things out.
It's also distinctly possible that HTC will unlock the bootloader the way it has with others of its handsets, in which case you'll be back in business.
Until then, my friend, I believe you are rootless.
i have the same problem. its been a couple months.... am i still hosed?
Have you tried this? http://forum.xda-developers.com/showthread.php?t=1306400
I used Scotty1223's instructions a few weeks ago and it worked like a charm.
So I burnt out my Cpu on my original rooted Dinc and got a replacement however after playing around on my replacement Dinc verizon pushed the update to 2.3.4 onto my phone. I would've stopped it but I figured I would just downgrade and root again however the new HBOOT 92 didn't let me downgrade i tried the unrevoked method anyway and i got a custom recovery so i restored MIUI on my current Dinc however i seem to still be unrooted? for example Titanium Backup can't delete system apps. i still have S-on and the new HBOOT 92 however i also have a mac so i am a little stuck and confused on how to regain full root access with s-off again any hep would be greatly appreciated.
alexyaz said:
So I burnt out my Cpu on my original rooted Dinc and got a replacement however after playing around on my replacement Dinc verizon pushed the update to 2.3.4 onto my phone. I would've stopped it but I figured I would just downgrade and root again however the new HBOOT 92 didn't let me downgrade i tried the unrevoked method anyway and i got a custom recovery so i restored MIUI on my current Dinc however i seem to still be unrooted? for example Titanium Backup can't delete system apps. i still have S-on and the new HBOOT 92 however i also have a mac so i am a little stuck and confused on how to regain full root access with s-off again any hep would be greatly appreciated.
Click to expand...
Click to collapse
Check this out. http://androidforums.com/incredible-all-things-root/427344-2-3-4-root-downgrade-s-off.html
Well, I've come across an embarassing situation. My problem is in the title, and for those with a keen eye, yes, I'm a Sprint tech so laugh about that if you will, don't care. Gotten that on several other forums and no help. Apparently people hate us lol. Point is, telling me I need to take the phone in isn't really much help since I'm the person you'd normally go see. Anyway on to the issue.
A while ago I came across a phone that the owner didn't want anymore, and lo and behold it turns out the reason for that was a soft brick (I can't think of what else to call it.) I'll boot the phone, it loads up to the splash screen, and at different points will just flash grey and stop loading, then after a while of being left alone try and boot up again and then freeze up. I've pretty much exhausted the range of my knowledge (Owned samsung all my life, my rooting journey has been pretty much strictly that), so I come to you guys. Below I'll list what I've tried and my specs, hopefully I don't have a paperweight with a kickstand on my hands.
Things I've tried:
RUU's out the ass, had trouble getting them to even connect to the phone (triggered it at certain points during the boot til I found the sweet spot), and when it did its thing, simply gave me Error 132 (Signature Verification failed), which apparently is fixed with s-off. Leading me to...
Revolutionary. This I did really not expecting it to work, since the last time I've used this for someone else I had to enable USB debugging and everything, meaning I need to boot into the OS. No dice here.
ADB push I'm pretty new to this particular bit, so I tried to push a custom recovery onto the device, which failed due to S-ON. (At my wits end at this point, figured, "what the **** maybe I'll get lucky.")
Specs:
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.10.0001
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
And the date and time, which is incorrect so here
Oct 15 2010, 12:07:00
I don't think I need to point out yes, I've tried hard resetting and all the basic BS most normal users are surprised to find out they can do themselves. I'm fresh out of ideas, so before I begin the painstaking process of using other peoples solutions to other problems and hoping it works for mine, I've come for some direct advice/help. I think ADB might be my best bet at this point, but I have no real idea how, and after 7 hours reading through other peoples' stuff, you can imagine I'd rather just be told if it is or isn't going to work.
tl;dr, bricked evo, pls help.
Since ur the techy guy take a old evo that might have been smashed or something but the mother board still works swap the mother board and ur good to go I guess bcuz the other evo is now just trash
Sent from my PC36100 using xda premium
lreyes15 said:
Since ur the techy guy take a old evo that might have been smashed or something but the mother board still works swap the mother board and ur good to go I guess bcuz the other evo is now just trash
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Easier said than done; phones i send in have to match the ESN on the sticker as well as on the board, so no luck with that. ALso bump.
Have you tried unlocking it with unrEVOked?
EDIT: Well that won't work if you can't get the phone to boot up. Will the phone stay on in Bootloader or Fastboot modes? You cam flash an RUU while in Fastboot. If it stays on, either that or a PC36IMG.zip might work.
Captain_Throwback said:
Have you tried unlocking it with unrEVOked?
EDIT: Well that won't work if you can't get the phone to boot up. Will the phone stay on in Bootloader or Fastboot modes? You cam flash an RUU while in Fastboot. If it stays on, either that or a PC36IMG.zip might work.
Click to expand...
Click to collapse
It'll stay on in either of those two modes. I've tried a PC36IMG as well as the RUU for the phone's Radio, and neither works. I get error 132 for the RUU and PC36IMG doesn't get detected, unless I'm doing something wrong. It's in the root of the SD card and when I boot into the bootloader it tells me nothing's there on that initial check.
psych0r3bel said:
It'll stay on in either of those two modes. I've tried a PC36IMG as well as the RUU for the phone's Radio, and neither works. I get error 132 for the RUU and PC36IMG doesn't get detected, unless I'm doing something wrong. It's in the root of the SD card and when I boot into the bootloader it tells me nothing's there on that initial check.
Click to expand...
Click to collapse
Try a newer PC36IMG, like the one from the 4.54.651.1 ROM.