Related
Alright, so I've seen this error before and done plenty of searches and tutorials, and here is where I'm left off:
I have an HTC Thunderbolt and I was getting tired of Das BAMF RC 4.9, so first I wanted to flash BAMF's SoaB to check Sense 3.5, but the OS felt laggy even after waiting for everything to update. So from that point forward I was gonna go with CM7, but it wouldn't flash. I tried both versions in the XDA forums, and no luck, always got the (bad) and then installation aborted.
I flashed the RUU and figured I'd update Verizon's OTAs and then root again. (mistake I'm sure). I had to follow a new root process from the Windows side of my Macbook Pro. The root went fine, but once again, nothing I had downloaded would flash. After finishing a wipe and rebooting, my screen popped up to the infamous "security warning".
Seeing guides online I attempted to flash:
-my original MR1 RUU
-AndroidPolice_PG05IMG_Mecha_2-1.11.605.3
-AndroidPolice_PG05IMG_Mecha_2-2.11.605.3
-AndroidPolice_PG05IMG_Mecha_2-3.11.605.3
No dice, it would get to "checking PG05IMG.zip", load up, then return to main screen. Unplugging the TBolt made the ***Security Warning*** go away, but still no RUU's would flash. So here I am, none of the RUU's, old or new, will flash to my device and it won't boot to anything but hboot.
Fixing would be nice to grab money for it, but at this point, I'm thinking about waiting for Galaxy Nexus. Any suggestions?
First of, Am terribly sorry about your ordeal. secondly, I am unable to comment on a possible fix for resolving your issue. Since you did state that you're waiting for the GNexus to come out, May I suggest checking out this site for "possibly" the Baddest android to come out maybe early next month..Check out this site (http://www.releasedates.co/product/motorola-droid-razr-release-date-0)..Again, sorry about your issue. RUUs scare the crap out of me and I keep my distance!! I rooted correctly the first time around and that was scary enough. Hope it all works out for you. PM a "Known" dev within TB's forums and am sure you'll get a quicker answer rather than waiting for one to discover your Thread
Thank you for the condolences. lol.
I looked at the RAZR a bit, but I with my current fiasco, I don't really want to root for a while (because I just don't need it), I'm super stoked for ICS, and the Nexus is supposedly nearly bloatware-free. Given that RAZR is such a running Verizon name, I almost expect it to have even more Bloatware out of the box, and the Bionic hype, release, and quick fall from grace makes me a little leery of Motorola right now. I figure I had a MotoDroid X, then an HTC TBolt, so now I'll give Samsung a shot. But I suppose someone may attempt to sell me on the RAZR, so I say "give it your best shot".
Great minds do think a like and Am not completely sold on it yet either.. for most of the reasons you've stated. The specs however, are given me "Tunnel" vision though and I hope I can wait till the first batch and any major issues get ironed out before my "Non Patient" self decides to get it..Bionic was definitely a "BIG" hype and I personally didn't even think of getting it and I don't regret one bit getting my TB. Am kinda a sense guy but CM7's latest got me trippin now cuz I've got it setup so damn nice and its Blazing Fast and smooth ..I guess I didn't do a good job selling you on DR and I wouldn't try it cause that would be "Hypocritical" of me..LOL
Haha, don't worry. I've got the "tunnel vision" for the GN. I heard the words "ICS" "Bloatware-free" and "Dual-core optimized" and I was sold. You seem like you know your technology very well. Don't suppose you have a Google+ I could add you on?
In fact, I am on G+ but to be honest, Am not much for the social apps and not exactly sure on using it..I haven't given it much effort. I may be the only one in this world not on FB LOL
Please see this thread for a possible fix. Fix is on Post # 5. Please share your results.
http://forum.xda-developers.com/showthread.php?t=1051998
Sent from my ADR6400L using XDA App. Hit thanks if I helped you in any way.
Unfortunately, those were the first two RUU's I attempted to flash :/ no dice
You said you flashed an ruu and then gained root.
1. Which ruu did you flash?
2. And which root method did you use?
3. When you boot into bootloader does it say locked or unlocked?
4. And which bootloader version does it show?
5. Are all your root applications working?
Sent from my ADR6400L using xda premium
I'm thinking that you have a HBOOT lower than the version 1.04
Sent from my ADR6400L using XDA App
I'll attempt to answer the questions as best I can:
1. I don't recall the actual last RUU that I flashed (sorry, I know that doesn't help)
2. forums.androidcentral.com/thunderbolt-rooting-roms-hacks/71919-mac-procedure-how-root-htc-thunderbolt(DOT)html I started with this root method, but for some reason couldn't get passed the second hboot process, so I ended up running forums.androidcentral.com/thunderbolt-rooting-roms-hacks/123060-guide-how-root-unroot-thunderbolt-revolutionary(DOT)html <<that one, but it told me i was rooted. (odd, I should have realized)
3-4. the screen is as follows:
MECHA XD SHIP S-ON
HBOOT-0.95.0000
MICROP-/
RADIO-1.02.00.0103_2r
eMMC-boot
Dec 16 2010,22:29:58
5. I cannot boot into Android, so I can't really answer that last question.
((sorry about the links))
xxx4rch4ng3lxxx said:
I'll attempt to answer the questions as best I can:
1. I don't recall the actual last RUU that I flashed (sorry, I know that doesn't help)
2. forums.androidcentral.com/thunderbolt-rooting-roms-hacks/71919-mac-procedure-how-root-htc-thunderbolt(DOT)html I started with this root method, but for some reason couldn't get passed the second hboot process, so I ended up running forums.androidcentral.com/thunderbolt-rooting-roms-hacks/123060-guide-how-root-unroot-thunderbolt-revolutionary(DOT)html <<that one, but it told me i was rooted. (odd, I should have realized)
3-4. the screen is as follows:
MECHA XD SHIP S-ON
HBOOT-0.95.0000
MICROP-/
RADIO-1.02.00.0103_2r
eMMC-boot
Dec 16 2010,22:29:58
5. I cannot boot into Android, so I can't really answer that last question.
((sorry about the links))
Click to expand...
Click to collapse
Is there anyway you can hit me up on chat somewhere. You have the bootloader used before the phone was released 0.95.0000. This is why you are getting the security warning. The released version was 1.04.0000. From my understanding, you are not supposed to downgrade the bootloader lower than that released version. PM me your IM info and I'll gladly try to help you.
Sent from my ADR6400L using XDA App
I added you on messengers. Thank you for any and all help you can offer!
I've recently rooted and had some issues with my personal phone, which I've cleared up with help from this board and members, and have actually enjoyed messing with my phone, its been fun learning about android and the possibilities with these phones. But with a bit of hesitation on going at it again with my phone, and how screwed I was when I couldn't get it going for a while, I thought I'd browse for a spare phone, anything, something old to screw around with and really practice on.
well, don't I find a 'bricked' amaze in my local classifieds! so $50 later I have myself a spare amaze to mess with! This phone powers on and goes straight to hboot, and I thought sweet, a factory rom upgrade and away we go. but it wasn't so easy.
this phone is a telus, and was relocked, but the one thing I noticed on this one that I didn't on mine when I flashed the telus rom is that this one has a 'security warning' under the relocked banner at the top of hboot. For the life of me I can't seem to get an oem rom to upgrade this phone. I've tried 3 different sd's, formatting etc. downloading the telus ruu zip from lots of different sites, trying with sd out then installing it when hboot loads, with and without usb plugged in, you name it I've tried it, and I cant' seem to get a stock rom to load.
hboot checks for ph85diag, then ph85img, finds it, checks it, then checks it again and back to hboot. No matter what I do, it won't ask to upgrade, and even trying out other ruu's it'll at least tell me that its the wrong file. Funny thing is in all of this I've already done this on my fully working amaze, and it worked right away, the only thing I'm thinking is that security warning banner, if that's in any way preventing the install.
any thoughts?
andy55 said:
I've recently rooted and had some issues with my personal phone, which I've cleared up with help from this board and members, and have actually enjoyed messing with my phone, its been fun learning about android and the possibilities with these phones. But with a bit of hesitation on going at it again with my phone, and how screwed I was when I couldn't get it going for a while, I thought I'd browse for a spare phone, anything, something old to screw around with and really practice on.
well, don't I find a 'bricked' amaze in my local classifieds! so $50 later I have myself a spare amaze to mess with! This phone powers on and goes straight to hboot, and I thought sweet, a factory rom upgrade and away we go. but it wasn't so easy.
this phone is a telus, and was relocked, but the one thing I noticed on this one that I didn't on mine when I flashed the telus rom is that this one has a 'security warning' under the relocked banner at the top of hboot. For the life of me I can't seem to get an oem rom to upgrade this phone. I've tried 3 different sd's, formatting etc. downloading the telus ruu zip from lots of different sites, trying with sd out then installing it when hboot loads, with and without usb plugged in, you name it I've tried it, and I cant' seem to get a stock rom to load.
hboot checks for ph85diag, then ph85img, finds it, checks it, then checks it again and back to hboot. No matter what I do, it won't ask to upgrade, and even trying out other ruu's it'll at least tell me that its the wrong file. Funny thing is in all of this I've already done this on my fully working amaze, and it worked right away, the only thing I'm thinking is that security warning banner, if that's in any way preventing the install.
any thoughts?
Click to expand...
Click to collapse
unlock it done
you're kidding, its that easy? I thought about it too and didn't try that. First thing I'll be doing when I get home
what I was screwed by was I did the exact same thing to my good phone, I re-locked it, and loaded the telus rom and it went easy, no problems, and I tried the same with this phone, and no dice
did the unlock trick work
I'll let you know in a couple hours, the dud's at home and I'm stuck at work with computers that encrypt everything connected to them no screwing around (to a certain degree) at work
yup worked, had issues with wifi/bluetooth but bulletproof fixed that issue, all is working again, thanks, I can't believe I didn't think that would work before!
Ok so I apologize for my lack of knowledge on this subject in advance, but essentially I followed steps a year ago or so to get my phone rooted, everything went fine - I believe I had a stock rooted rom. A couple weeks ago people started complaining about having trouble hearing me clearly on the phone, like I was cutting in and out. A week ago apparently my mic died completely because all I hear now is a high pitched noise when I try to do a voice recording, and no one can hear me when I make or answer phone calls. So I'm trying to get my phone fixed by sprint, but I believe they can tell my phone was rooted.
I used RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10.0530_NV_NV_SPCS_1.16_release_198109_signed.exe to get my phone rom back to stock, but when I hold the vol down button and power I get to a menu that says this:
shooter xc ship s-off rl
hboot 1.40.0000
radio-0.97.10.0530
eMMC-boot
Jun 8 2011, 17:20:22
Any know what I need to do now to get my phone completely back to stock? I know that s-off is a red flag (and I'd like to know how to get that back on), but is there anything else I need to do? Thanks so much.
Personally, I'd leave it just how it is. It's stock enough. They probably won't even check hboot. If they do check it, they probably won't care since you have a hardware issue. I would only turn s-on if sprint told me they won't work on it until I did.
Edit.. if you're determined to get s-on, the command is
Code:
fastboot oem writesecureflag 3
Only use that command if you have an official hboot, like 1.4, 1.5, 1.58 (which you do, according to your post).
im not new here but today i made an account because not only do i love this place its the best place for rooting and troubleshooting. i have a few tricks to share in one of those troubleshooting forums that could be useful.
I'm not a noob and im very comfortable with flashing roms and kernels. Though my phones a unique case.. before i ever rooted or even tampered with the phone the audio cut out. not a single sound comes out the speaker, headphone jack, and even bluetooth. when i did have stock sense anytime i got a call or wanted to play some music my phone would freeze then reboot. every single time. for awhile roms fixed it, to be more specific cyanogenmod fixed it. Even with no sound it causes some other smaller issues too. The phone wont auto rotate, any app that requires sound like games and youtube will either quit instantly or i will have to force close them. Its been going on for about 7months now (stuck in a contract with sprint and they won't honor the TEP).Today i tried using ViperRUU to return to fresh stock and try again to solve the audio problem and everything went as it should except it just won't boot into android. I thought it might be the kernel but that wasn't it. I tried flashing another sense rom and its kernel and the same thing happens it just sits there with a black screen. those who have HTC's newer phones, i tried holding the power button to restart the phone and thats all it will let me do. While on the black screen i connected it to my computer and it knows it there so i guess its not totally bricked, i think the right term is Softbricked? i looked in other posts to see if anyone had the same issue as me and i apologize if i didnt look hard enough to find one. I'm clueless on what to do. if its not the rom, kernal, or recovery what could it be? even trying to restore from a sense backup gets the same results. It just sits there with a black blank screen.
I apologize if this is the wrong place to post this as I am new to posting here,I Also marked this as question because if im understanding this right that is right? Thank you everyone in advance for the help
Some more information would be useful. If you can get to your bootloader, what is your Hboot version, radio (baseband) version, are you S-on or S-off, and what's the status of the bootloader (locked, unlocked, relocked)? What recovery are you using?
Also, when you connect to your computer, what does your phone show up as?
Sent from my HTC EVO 4G LTE
And is there water damage at any point? That sounds like faulty hardware, like a broken/melted chip. Do you overclock?
_______________________________________
Phone: HTC EVO 4G LTE
Stock, S-On (Returning to Sprint)
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
my phone info
FinZ28 said:
Some more information would be useful. If you can get to your bootloader, what is your Hboot version, radio (baseband) version, are you S-on or S-off, and what's the status of the bootloader (locked, unlocked, relocked)? What recovery are you using?
Also, when you connect to your computer, what does your phone show up as?
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Jewel PVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.12.11.1210
OpenDSP-v31.1.0.45.0815
eMMC-boot
bootloader status: *** TAMPERED ***
*** UNLOCKED ***
TWRP Version v2.6.3.0
I used htc dev to unlock it but fastboot says its unlocked, I got an ota update several months ago. I wasn't thinking and updated it and ever since it has never said S-OFF.
TWRP says theres an os on the system partition 880 something megabytes.
it has a bit of history
aarsyl said:
And is there water damage at any point? That sounds like faulty hardware, like a broken/melted chip. Do you overclock?
_______________________________________
Phone: HTC EVO 4G LTE
Stock, S-On (Returning to Sprint)
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
after like a month of owning the phone, i was in gym class one day. Felt my phone vibrate, went to the drinking fountain so my phone wouldn't be confinscated. i pressed the sleep button and BAM screen cracked. Not the glass just the screen. long story short, sprint wouldn't honor the warrenty and i don't have a lot of money so im not paying $200 for another phone when I already paid an extra $60 a month for a TEP plan witch i gladly removed. over a year I replaced the screen twice ($140 total still under the $200). I don't do the over-clocking stuff because my battery is bad enough already. I talked to htc about my phones audio problem and they have no record of any other customers with this issue i love my phone but having no sound is extremely fustrating.
So....last week, Verizon weirdly reported that my phone (rooted) used 3.5 gigs of data during the night while my phone was connected to wifi. The phone data usage screen, however, only reported 298 kb of usage. I called Verizon, we went back and forth, they finally decided that my phone was screwed up, and sent me a warranty replacement. I then began the tedious process of unrooting.
Once I finally got my phone back to the 1.08 HBOOT and S-On and stock recovery...finally.....the phone now says "RELOCKED" at the top instead of "LOCKED."
I posted about it on Infected. I was told that I could edit the hex file but it was not recommended. I have until Friday to package it up and send it in, and I'm a little worried. One user says that he has returned warranty replacements rooted and whatnot without incident, but I'm afraid that the techs might take an extra look at my phone because of the strange data issue I called them about last week that produced a "diamond tech support ticket". If they do, they will see a big, red "RELOCKED" at the top of the bootloader, which will be a dead giveaway. They won't be able to prove that I rooted it and flashed custom roms, but unlocking the bootloader is enough to void the warranty.
I did see some people with similar issues on the Rezound, and one person swore that if they used fastboot usb and typed in "fastboot oem lock" and then flashed a RUU in the boatloader, it was fixed, but I can't figure out how to make my command prompt to connect to my phone (I know, for someone who has flashed roms for a few years now, and Windows Mobile roms a few years back too, it seems like a total noob move).
Anyway, between that and the fact that we don't have a real ICS RUU, only the one that Santod put together (which worked beautifully for me otherwise), I'm not sure what else I can do. I tried flashing the .19 RUU, but it recognizes that it contains an older version of the bootloader, and won't flash. It's that one dang "RELOCKED" that has me nervous about sending it in. I'm about to just keep it and send back the warranty replacement complaining about the power button or something just to buy some time.
Any ideas?
arizonaomnia said:
So....last week, Verizon weirdly reported that my phone (rooted) used 3.5 gigs of data during the night while my phone was connected to wifi. The phone data usage screen, however, only reported 298 kb of usage. I called Verizon, we went back and forth, they finally decided that my phone was screwed up, and sent me a warranty replacement. I then began the tedious process of unrooting.
Once I finally got my phone back to the 1.08 HBOOT and S-On and stock recovery...finally.....the phone now says "RELOCKED" at the top instead of "LOCKED."
I posted about it on Infected. I was told that I could edit the hex file but it was not recommended. I have until Friday to package it up and send it in, and I'm a little worried. One user says that he has returned warranty replacements rooted and whatnot without incident, but I'm afraid that the techs might take an extra look at my phone because of the strange data issue I called them about last week that produced a "diamond tech support ticket". If they do, they will see a big, red "RELOCKED" at the top of the bootloader, which will be a dead giveaway. They won't be able to prove that I rooted it and flashed custom roms, but unlocking the bootloader is enough to void the warranty.
I did see some people with similar issues on the Rezound, and one person swore that if they used fastboot usb and typed in "fastboot oem lock" and then flashed a RUU in the boatloader, it was fixed, but I can't figure out how to make my command prompt to connect to my phone (I know, for someone who has flashed roms for a few years now, and Windows Mobile roms a few years back too, it seems like a total noob move).
Anyway, between that and the fact that we don't have a real ICS RUU, only the one that Santod put together (which worked beautifully for me otherwise), I'm not sure what else I can do. I tried flashing the .19 RUU, but it recognizes that it contains an older version of the bootloader, and won't flash. It's that one dang "RELOCKED" that has me nervous about sending it in. I'm about to just keep it and send back the warranty replacement complaining about the power button or something just to buy some time.
Any ideas?
Click to expand...
Click to collapse
the bootloader status is controled by a flag in another partition. it is well know with dual core and quad core snapdragon 3/4 devices,but i do not believe anyone has looked much into it for the older single core devices. the flag being in a block that is not touched by OTAs or RUUs is what makes hboot retain the same status regarless of hboot version,ruus run,etc.
with the newer phones,hboot looks at the flag,display locked if it finds 00 00 00 00,or .... and unlocked if it finds "HTCU" and relocked if it finds "HTCL". obviously,it comes from the factory 00 00 00 00,and htcdev sets it to HTCU when you first unlock. entering fastboot oem lock changed to HTCL.
the value is easily cahnged with adb,or with a dumped partiton and hex editor with a radio s off device,making the device out of the box stock.
the values may or not be the same in the older device,and they are defiantely in a different location. there is also the question of if youd even be able to change the flag,or is it blocked by write protection. while the eng hboot,and revolutionary patched hboot are eliminating signiture checks and ignoring the radio on things flashed in the bootloader,they are not able to override write protections in place as the phone boots.
i have been wanting to search for this flag,for S&Gs,but havent gotten to it yet. i would help you if time wasnt a factor... but ive got a fair amount on my plate this weekend. also, i dont want to get your hopes up,as the logical location is in mmcblk0p7,where the radio secure flag lives. if this is the case,that block is protected and you wont be able to change it anyway,even if we find the flag and its values.
i dont know if that helps,but its what i know about the "lock status" flag
Santod made him a faux locked s on hboot. Good writeup on the locked status though.
Sent from my HTC6500LVW using Tapatalk