I am just wondering if any one else has seen this I just busted out my old rezoned and went to flash the official ruu and my hboot says tampered Ive never unlocked or rooted this phone is the ***tampered*** from using the leaked ics img
tampered means that it was unlocked then relocked, i think.
I thought it was from flashing a custom recovery, either way not a big deal .
Sent from my ADR6425LVW using Tapatalk 2
Actually neither. When you flashed the leaked ICS RUU it changes your bootloader label to "tampered." You can get rid of it by s-offing.
Sent from my ADR6425LVW using xda app-developers app
Tampered means there is a custom recovery. For unlocked it displays locked unlocked or relocked.
Sent from my DROID RAZR using Tapatalk 2
mjh68 said:
I thought it was from flashing a custom recovery, either way not a big deal .
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Correct you get tampered when you flash a custom recovery, running a full ruu should remove it.. cuz it replaces the custom with stock recovery
Sent from my ADR6425LVW using xda app-developers app
+1 for it being due to a custom recovery. Relocking it and running an RUU will get rid of it, although it'll still say "relocked" instead of "locked"
scy1192 said:
+1 for it being due to a custom recovery. Relocking it and running an RUU will get rid of it, although it'll still say "relocked" instead of "locked"
Click to expand...
Click to collapse
But you can s-off and install a hex-edited HBOOT to one that says locked even if it's relocked.
Doesn't it also say "unlocked" underneath "tampered"? I don't think you can install a custom recovery without having unlocked the phone.
Or did you temp root?
Related
I have a phone I need to send back and I'm honestly not sure how to do it.
Sent from my ADR6425LVW using xda premium
Are you on ICS & leaked firmware or just GB and unlocked? Can't help too much until you provide more detail.
Sent from my ADR6425LVW
i'm assuming he's on stock since he wants to return it to VZW as close as he can, but i could be wrong, he could be one step behind
Re lock phone and run the ruu twice
Sent from my Dinc... I mean Rezound
yojoe600 said:
Re lock phone and run the ruu twice
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
i'm on the same boat. i'm on stock GB but need stock recovery but can't get it. The RUU says waiting for bootloader when my phone is connected and then it exits. it can't run all the way through. any ideas?
jackpot08 said:
i'm on the same boat. i'm on stock GB but need stock recovery but can't get it. The RUU says waiting for bootloader when my phone is connected and then it exits. it can't run all the way through. any ideas?
Click to expand...
Click to collapse
Try just relocking your bootloader.
GrayTheWolf said:
Try just relocking your bootloader.
Click to expand...
Click to collapse
I'm already relocked :/
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
jackpot08 said:
i'm on the same boat. i'm on stock GB but need stock recovery but can't get it. The RUU says waiting for bootloader when my phone is connected and then it exits. it can't run all the way through. any ideas?
Click to expand...
Click to collapse
Did you run the ruu from your phone ?
Sent from my Dinc... I mean Rezound
yojoe600 said:
Did you run the ruu from your phone ?
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
I ran the exe on my computer. My phone is in normally conected and it runs but then the setup says waiting for bootloader then it exits since it like can't find it
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
everyone runs the ruu from the phone.. you have to turn it into a PHXXXIMG and flash in boot loader.. thats the problem i think... look for scotts guide to running the ruu
I'm completely stock and unlocked with amon ra recovery, where is the ruu/ how do I flash it? I've never flashed any of the ruus before.
Slacker101 said:
I'm completely stock and unlocked with amon ra recovery, where is the ruu/ how do I flash it? I've never flashed any of the ruus before.
Click to expand...
Click to collapse
go here and flash the last one after naming it the right phimg that our phones use... i cant rember it right now
http://goo.im/stock/vigor/ruu
I did Bootloader unlock using the code fron HTEDev, and it showed "Unlocked" . Then I flashed 4Ext recovery and unrooted. However, when I did "S-off", the bootloader shows"Locked" again with the text "S-off".
Anyone have the same issue? Should I do the unlock again using the code? or I can just ignore it and go ahead install other custome ROM.
Edit: Educated by dark nightmare.
Sent from my HTC Vision using xda app-developers app
Just unlock it back using the unlock file you got.
Would unlocking again serve any real purpose?
Sent from my HTC Vision using xda app-developers app
death4u said:
Would unlocking again serve any real purpose?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Leave it locked and you'll see, .
sent from a galaxy you'll never see.
Dark Nightmare said:
Just unlock it back using the unlock file you got.
Click to expand...
Click to collapse
I have several questions here:
1. Is my bootloader re-locked after S-off, or it is still unlocked but just show a Irrelevant text " locked" ?
2. How could I check if the real bootloader's status: "Locked" or Unlocked", not just from the text show in the fastboot page?
2. If the "bootloader is relocked", it should show "Relocked", not "Locked", isn't it?.
3. If it IS re-locked and I don't re-unlock it, will it affect the installation of custom ROM?
If the "Locked" after S-off does not affect the installation of custom ROM, I would like to leave it that way which will be easy to roll back to complete stock for warranty.
Brightxda said:
I have several questions here:
1. Is my bootloader re-locked after S-off, or it is still unlocked but just show a Irrelevant text " locked" ?
2. How could I check if the real bootloader's status: "Locked" or Unlocked", not just from the text show in the fastboot page?
2. If the "bootloader is relocked", it should show "Relocked", not "Locked", isn't it?.
3. If it IS re-locked and I don't re-unlock it, will it affect the installation of custom ROM?
If the "Locked" after S-off does not affect the installation of custom ROM, I would like to leave it that way which will be easy to roll back to complete stock for warranty.
Click to expand...
Click to collapse
It is locked you need to un lock it again so you can flash custom recovery
sent from my NRGized Amaze,
powered by faux kernel v.16
aj_2423 said:
It is locked you need to un lock it again so you can flash custom recovery
sent from my NRGized Amaze,
powered by faux kernel v.16
Click to expand...
Click to collapse
If he had a custom recovery before s-off it's still there, but you see the thing about "locked" or "relocked" bootloaders people don't understand is that even with s-off, once it's locked, writing anything at all isn't possible via custom recoveries, that itself is the first level of security we bypass to customize our devices.
By the way to the op, it is currently locked the way it was before you unlocked via htcdev, not relocked, that text on the hboot is the verification.
sent from a galaxy you'll never see.
Dark Nightmare said:
If he had a custom recovery before s-off it's still there, but you see the thing about "locked" or "relocked" bootloaders people don't understand is that even with s-off, once it's locked, writing anything at all isn't possible via custom recoveries, that itself is the first level of security we bypass to customize our devices.
By the way to the op, it is currently locked the way it was before you unlocked via htcdev, not relocked, that text on the hboot is the verification.
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
Thank you all very much for clearing my questions. I will unlock it again.
One more question: How could it relocked during the S-off? Is it the normal thing for all of S-off or it just happens in a few cases?
Brightxda said:
Thank you all very much for clearing my questions. I will unlock it again.
One more question: How could it relocked during the S-off? Is it the normal thing for all of S-off or it just happens in a few cases?
Click to expand...
Click to collapse
It happens to all of us, once you don't install JB hboot after s-off it locks your bootloader, I guess the entire process resets a few security levels since it turns the main security lock off.
Dark Nightmare said:
It happens to all of us, once you don't install JB hboot after s-off it locks your bootloader, I guess the entire process resets a few security levels since it turns the main security lock off.
Click to expand...
Click to collapse
You are right. I skipped the last step, installing JB hboot during the S-off. I thought my Amazer came with the new ICS pre-installed which might not need other hboot. It should not be any problem, right?
Brightxda said:
You are right. I skipped the last step, installing JB hboot during the S-off. I thought my Amazer came with the new ICS pre-installed which might not need other hboot. It should not be any problem, right?
Click to expand...
Click to collapse
Na it's just a custom hboot, not needed, you can always flash that or the ENG hboot later if you wanna change your splash screen, that's probably the only thing it's useful for.
Dark Nightmare said:
Na it's just a custom hboot, not needed, you can always flash that or the ENG hboot later if you wanna change your splash screen, that's probably the only thing it's useful for.
Click to expand...
Click to collapse
Thank you again, I reunlocked the bootloader, flashed Energy™ ROM and it works great now.:victory:
I unlocked the bootloader on my Rezound a few hours ago, but ever since then it has been stuck in a bootloop. I wasn't on stock though, so did that have anything to do with it? I've tried reflashing the ROM, and that doesn't help.
How did you flash another ROM without unlocking your bootloader?
Agreed.. If you weren't on stock then your bootloader must have been previously unlocked.. what Rom are you using/trying to use.? You need to have a custom recovery installed after you unlock, you couldn't have flashed a rom from stock recovery..
Sent from my ADR6425LVW using xda app-developers app
famouscollin said:
Agreed.. If you weren't on stock then your bootloader must have been previously unlocked.. what Rom are you using/trying to use.? You need to have a custom recovery installed after you unlock, you couldn't have flashed a rom from stock recovery..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Bootloader was locked, but it was unlocked previously, and a custom recovery had been installed. When I got the phone, it was rooted, S-Off, and on the stock ROM. It had Amon Ra's recovery already installed, but again, as I said the bootloader was locked.
EDIT: Oh and the ROM I was using (successfully before the unlock) was CounterShrike.
swbf2lord said:
Bootloader was locked, but it was unlocked previously, and a custom recovery had been installed. When I got the phone, it was rooted, S-Off, and on the stock ROM. It had Amon Ra's recovery already installed, but again, as I said the bootloader was locked.
EDIT: Oh and the ROM I was using (successfully before the unlock) was CounterShrike.
Click to expand...
Click to collapse
Well first off if you were s-off why did you need to unlock your bootloader? What hboot are you using?
Sent from my ADR6425LVW using xda app-developers app
Collin is right.
All you really need to do is wipe everything and flash a ROM. Since you are s-off everything else will be taken care of.
GrayTheWolf said:
Collin is right.
All you really need to do is wipe everything and flash a ROM. Since you are s-off everything else will be taken care of.
Click to expand...
Click to collapse
Okay. I haven't really been using HTC devices so I didn't know what S-Off actually did. I went ahead and fixed it with the RUU.
Sent from my ADR6425LVW using Tapatalk 2
OK so I used the bootloader to flash the 3 option in Haus's thread and every thing is working. But....
Now on the bootloader screen it says locked tampered then S-off.
I was told the locked was just wat it was saying and didn't matter.
So do I have a locked boot loader? And does that even matter for anything or was it just required to get root plus S-off?
Did I mess up getting the newest hboot from the firmware? I was told I needed it to run meanbean.
Sent from my EVO using xda app-developers app
I'm not sure what u flashed but it sounds like you flashed the whole thing which means you have stock recovery now. Either fastboot flash recovery image or download thru goo manager.
Once you have a custom recovery installed your all set. Don't worry about the locked on your bootloader
Sent from my EVO using xda premium
mainstang said:
OK so I used the bootloader to flash the 3 option in Haus's thread and every thing is working. But....
Now on the bootloader screen it says locked tampered then S-off.
I was told the locked was just wat it was saying and didn't matter.
So do I have a locked boot loader? And does that even matter for anything or was it just required to get root plus S-off?
Did I mess up getting the newest hboot from the firmware? I was told I needed it to run meanbean.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You should have flashed the first file the one with no kernel,hboot, or stock recovery that would have updated everything you needed to be updated
So did I mess anything up? I was able to flash mean bean without any issues.
Sent from my EVO using xda app-developers app
mainstang said:
So did I mess anything up? I was able to flash mean bean without any issues.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
No you just did the same as taking the OTA as far as I can tell. As long as everything is working you should be fine
Hey guys, have to send in my phone in for a warranty replacement, but I've run into a few issues:
I'm s-on running ViperRez, and anon-ra. I went in and relocked the bootloader, but my phone would only boot into hboot. So I re-unlocked and got stuck after the viper rez splash boot animation.
So here's what I'm asking: right now my phone is s-on, unlocked, still on viper rez, and currently not booting. When I relock do I need to like get rid of amon-ra or something? Once I relock I plan on running the ruu tool for the ICS OTA. Am I in the clear so to speak? Any suggestions as to why my phone won't boot, and why when I relock it boots to hboot only?
Thanks, for the help, I have to send this thing in by Sunday so I'm slightly paranoid.
Sent from my ADR6425LVW using xda app-developers app
Just relock the boot loader and flash the latest RUU. You will be fine.
GrayTheWolf said:
Just relock the boot loader and flash the latest RUU. You will be fine.
Click to expand...
Click to collapse
Thanks, that's what I thought.
Sent from my ADR6425LVW using xda app-developers app