Database Info

[Q] Tmo One S (stock) Bootloader tampered

First i apologize if this is was already posted,
I just got the 1.84 ota update installed. And i just want to check the h boot . And its says Tampered and Locked.
My issue is i never unlocked the bootloader or tried to root this phone. Bought phone new from T-mobile.
Is this normal for stock phone to say tampered?
If it is not then i will want to root since its tampered, but is there a way to root for 1.84 .

blkfire50 said:
First i apologize if this is was already posted,
I just got the 1.84 ota update installed. And i just want to check the h boot . And its says Tampered and Locked.
My issue is i never unlocked the bootloader or tried to root this phone. Bought phone new from T-mobile.
Is this normal for stock phone to say tampered?
If it is not then i will want to root since its tampered, but is there a way to root for 1.84 .
Click to expand...
Click to collapse
Go exchange it if you're plan to use stock. If not go root it
Sent from my HTC VLE_U using Tapatalk 2

You could exchange it, but if you plan to root instead, there's 2 sticky threads in development specifically devoted to rooting and they work for the 1.84 update as well. However, there's also a "one click" rooting option in the One X (AT&T version) development section that was recently updated and MIGHT work on the 1.84 update without having to unlock the bootloader through HTC. The last one click for the AT&T X worked for the S as well before the 1.84 update.
Sent from my H1S using XDA Premium.

Thanks ,
Last thing is it normal to see tampered on a completely stock device thats never been rooted

Absolutely not.
Sent from my H1S using XDA Premium.

Mine was listed as "tampered". I didn't think much of it as I was planning on unlocking/rooting anyway.
blkfire50 said:
First i apologize if this is was already posted,
I just got the 1.84 ota update installed. And i just want to check the h boot . And its says Tampered and Locked.
My issue is i never unlocked the bootloader or tried to root this phone. Bought phone new from T-mobile.
Is this normal for stock phone to say tampered?
If it is not then i will want to root since its tampered, but is there a way to root for 1.84 .
Click to expand...
Click to collapse

[Q] Question about UNLOCKING BOOTLOADER while ROOTED and S-OFFed

I've been using my Sensation XE for almost 9 months now, and on the 2nd month i decided to Root it. I went through the steps: unlock bootloader (Juopunut), s-off and root. For some reason after a week or two from ROOTING the phone, i noticed that the bootloader reverted back to LOCKED. It was still S-offed and rooted, no problem with that. I was just wondering why it went back to LOCKED state.
I didn't mind the bootloader being locked and proceed to flashing a custom rom. I've been shifting from one rom to another and they were really buggy. I checked the forums and read the section about known bugs. Yes, the bugs were existent, but there are tons of bugs happening in my phone that we're not mentioned. I shifted to another custom rom and the same things happened. Some of my bugs and glitches are not on the list of known bugs.
I started to ask if it's the LOCKED BOOTLOADER who's making this issue on my custom roms. END OF STORY
QUESTIONS:
Do issues with custom roms happen if BOOTLOADER is LOCKED?
Is it safe to attempt to unlock the bootloader again even if it's rooted and s-offed?
If it's because of the LOCKED BOOTLOADER, is it permanent? Can it still be undone?

czyre04 said:
I've been using my Sensation XE for almost 9 months now, and on the 2nd month i decided to Root it. I went through the steps: unlock bootloader (Juopunut), s-off and root. For some reason after a week or two from ROOTING the phone, i noticed that the bootloader reverted back to LOCKED. It was still S-offed and rooted, no problem with that. I was just wondering why it went back to LOCKED state.
I didn't mind the bootloader being locked and proceed to flashing a custom rom. I've been shifting from one rom to another and they were really buggy. I checked the forums and read the section about known bugs. Yes, the bugs were existent, but there are tons of bugs happening in my phone that we're not mentioned. I shifted to another custom rom and the same things happened. Some of my bugs and glitches are not on the list of known bugs.
I started to ask if it's the LOCKED BOOTLOADER who's making this issue on my custom roms. END OF STORY
QUESTIONS:
Do issues with custom roms happen if BOOTLOADER is LOCKED?
Is it safe to attempt to unlock the bootloader again even if it's rooted and s-offed?
If it's because of the LOCKED BOOTLOADER, is it permanent? Can it still be undone?
Click to expand...
Click to collapse
Hi,
If you are s-off,DO NOT try to use HTC to lock/unlock your phone.
It will cause problems for you.
Did you flash a version of the 3.33 firmware?
This has been known to lock people's bootloader.
The only thing a locked bootloader will do,is prevent you using all the fastboot commands.

malybru said:
Hi,
If you are s-off,DO NOT try to use HTC to lock/unlock your phone.
It will cause problems for you.
Did you flash a version of the 3.33 firmware?
This has been known to lock people's bootloader.
The only thing a locked bootloader will do,is prevent you using all the fastboot commands.
Click to expand...
Click to collapse
Yeah, I kinda have updated the firmware after the root process.
Have any idea why i get extra bugs from roms?
Thanks for the reply BTW. Appreciated it.

czyre04 said:
Yeah, I kinda have updated the firmware after the root process.
Have any idea why i get extra bugs from roms?
Thanks for the reply BTW. Appreciated it.
Click to expand...
Click to collapse
Hi,
Sorry,I have no idea why your phone is suffering all these bugs.
My suggestion would be to keep searching for a ROM/kernel combination that works for you.

[Q] Razr Maxx HD w/ unlocked Bootloader

Just purchased an HD MAXX from Ebay and the seller said it has a permanently unlocked bootloader and a custom ROM flashed. I'm upgrading from a Bionic that I rooted, installed SafeStrap and tried a few custom ROMs in the slots. I'm going to have the phone flashed over to Page Plus and the person doing the flashing told me it has to be on stock. The seller told me that the bootloader is permanently unlocked. The seller also told me how the bootloader was unlocked and I read something similar here that if it were unlocked at a certain point, or before a certain update was pushed out, it would be permanently unlocked,
I just don't want to screw anything up trying to flash it back to stock. It's running the TWRP custom recovery. I've flashed ROM's before, I've rooted phones before but from what I understand having a Razr with an unlocked bootloader is something special and I wouldn't want to screw that up. Thanks

SkyRocker_58 said:
Just purchased an HD MAXX from Ebay and the seller said it has a permanently unlocked bootloader and a custom ROM flashed. I'm upgrading from a Bionic that I rooted, installed SafeStrap and tried a few custom ROMs in the slots. I'm going to have the phone flashed over to Page Plus and the person doing the flashing told me it has to be on stock. The seller told me that the bootloader is permanently unlocked. The seller also told me how the bootloader was unlocked and I read something similar here that if it were unlocked at a certain point, or before a certain update was pushed out, it would be permanently unlocked,
I just don't want to screw anything up trying to flash it back to stock. It's running the TWRP custom recovery. I've flashed ROM's before, I've rooted phones before but from what I understand having a Razr with an unlocked bootloader is something special and I wouldn't want to screw that up. Thanks
Click to expand...
Click to collapse
The seller is correct. May 25 is dday for the ...79 build that locks the boot.
You do not state your build.
Get the latest twrp 2632 for a pocket proof noob recovery but for a successful cm 11 flash you need philz newest & philz 6079 for some flashes that err 7 on the 619 ver.
926 philz only comes in .img. Get recovery tools to load the img from homescreen. Philz is in the orig dev section.
When in doubt backup.
See my 907 stuff for lots similar things/guides that apply to the 926 as well.

SkyRocker_58 said:
Just purchased an HD MAXX from Ebay and the seller said it has a permanently unlocked bootloader and a custom ROM flashed. I'm upgrading from a Bionic that I rooted, installed SafeStrap and tried a few custom ROMs in the slots. I'm going to have the phone flashed over to Page Plus and the person doing the flashing told me it has to be on stock. The seller told me that the bootloader is permanently unlocked. The seller also told me how the bootloader was unlocked and I read something similar here that if it were unlocked at a certain point, or before a certain update was pushed out, it would be permanently unlocked,
I just don't want to screw anything up trying to flash it back to stock. It's running the TWRP custom recovery. I've flashed ROM's before, I've rooted phones before but from what I understand having a Razr with an unlocked bootloader is something special and I wouldn't want to screw that up. Thanks
Click to expand...
Click to collapse
as long as you have the drivers installed on your pc all you have to do is grab one of the utilities from the dev forum and flash it back to stock. there is also an option in there to put the stock recovery back on. its all plug and click.

Thanks guys!
Appreciate the replies and info. My main concern was doing something to possibly "re-lock" the bootloader. From what you're saying I shouldn't have any problems, flash it back to stock, flash it to page plus, flash custom recovery, start trying out ROM's lol
Thanks again!

Once the fuse is blown it cannot be "rearmed". But I've heard that there are couple of those in our RAZR. But I don't think vz or moto are interested in making our phones inoperable.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app

I can attest to the fact that once you unlock the bootloader, it won't get relocked since it's a physical change (blown e-fuse as others have mentioned).
I have flashed back to a previous stock, took the OTA and the bootloader was still unlocked.
However, never say never and when KitKat comes out for this phone, I will not be quick to install it. I will wait and see what everyone says before I accept it. No way I take an OTA that somehow finds a different way to lock the bootloader.

Unlocked booloader?

I bought Razr Maxx HD about two months ago. I asked seller is booloader unlocked and he said NO and never have been. Also he flashed latest official rom (9.30.1.XT926.Verizon.en.US). So I just get to use to it.
Half hour ago I chat with my friend (he has Razr too) about unlocking and he told me to boot into fastboot, "fastboot oem unlock" and check result. For my surprise I've got Device is UNLOCKED. Status code: 3 (check attachment).
Double, triple check. Am I really lucky to have unlocked bootloader?

Did you actually check if it was unlocked before trying this, or did you just take the previous owner's word for it?
Also, what did the command line say after you did the fastboot oem unlock?

You unlocked your unlocked phone! Lol.

I just believed to previous owner. It's funny for me too Even more funny is that he told me that he used safestrap. Safestrap and latest stock convinced me that bootloader is locked.
I didn't run fastboot oem unlock because should be unlocked already. I can do it today or just try to flash custom recovery. I didn't read much topics for unlocked bootloader.
Any recommendation for custom recovery and full functional rom?

IMO TWRP is the best recovery. You can get the newest copy of it here:
http://androidhosting.org/Devs/Dhacker29/msm8960/
Grab the bottom one. Should be xhdpi.
Best ROM depends on what you like. CM 11 is pretty stable at this point (they just released an M5 build for it).

I like rom without unnecessary features, fast and reliable. I read that CM11 has some problems, for example with compass. I'll try it (of my phone is really unlocked) and latest CM10.x
I use TWRP on three of four my devices. Thx for link and recommendations.

I couldn't resist and flashed TWRP few minutes ago. It works! Happy

Latest info on AT&T S4 I337

I was given an AT&T I337 that had been operator unlocked by a friend. I took it back to NF1 ROM using Heimdall, acquired root with Towelroot and then used Safestrap to boot custom recovery. However, it seems that there is still no way to unlock the bootloader and install other than TW ROMs fully utilizing the phone? I came across an old thread where someone hinted that he had cracked the bootloader encryption but it seemed to fizzle out into nothing.
Am I correct in the understanding above? If so, I will put the phone away since this will not meet my needs.

hga89 said:
I was given an AT&T I337 that had been operator unlocked by a friend. I took it back to NF1 ROM using Heimdall, acquired root with Towelroot and then used Safestrap to boot custom recovery. However, it seems that there is still no way to unlock the bootloader and install other than TW ROMs fully utilizing the phone? I came across an old thread where someone hinted that he had cracked the bootloader encryption but it seemed to fizzle out into nothing.
Am I correct in the understanding above? If so, I will put the phone away since this will not meet my needs.
Click to expand...
Click to collapse
The bootloader is locked and cannot be unlocked. You are stuck with custom TW ROMS only. There was an exploit for the Android 4.2.2 jelly bean firmware that allowed custom ROMS and recovery, but the flaw was patched in later firmware builds and if you try to roll back to the 4.2.2 firmware you will brick your phone.

StoneyJSG said:
The bootloader is locked and cannot be unlocked. You are stuck with custom TW ROMS only. There was an exploit for the Android 4.2.2 jelly bean firmware that allowed custom ROMS and recovery, but the flaw was patched in later firmware builds and if you try to roll back to the 4.2.2 firmware you will brick your phone.
Click to expand...
Click to collapse
Thank you, then the information I gleaned was indeed correct. I will have to put this phone aside since I wanted to run LineageOS on it and it needed to be encrypted as well...