• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [AT&T] No Developer Warning text after S_OFF

sharksfan7

Android Enthusiast
Aug 8, 2011
286
62
San Diego, CA
I just S-OFF'd my One using Firewater and the temproot method. Flashed TWRP and installed SuperSU. I was fully expecting to see the red text Developer Warning every time I boot the phone. But I'm only seeing it when I boot to recovery. When I boot normally there is no indication at all that the phone has been modified. Is this how it normally is? HBOOT version is 1.55 and is unlocked. Still running the stock ROM. Will that warning start popping up every time after I flash a custom ROM or custom splash screen? I know I would have to flash a custom HBOOT to remove the warning, but I'd like to avoid doing that if I can. And if that warning only pops up when I go into recovery, I can live with that.
 
On mine I get it on every boot, and I think I did even before I moved to custom ROMs (long time ago though, so can't be sure). Maybe it's different with the way you did it (I used revone, which tells you it was a while ago ;)).

Personally I live with the warning anyway - doesn't seem worth flashing a custom hboot to remove it.
 
Upvote 0
You're not seeing it because you're still running the stock rom and kernel. I'm 100% stock as well,and don't see the red text either on normal boot.

Im with hadron,I've never run a custom hboot to avoid the text. I honestly don't understand why its such a big deal to some folks,and personally think its rediculous to risk installing a modified bootloader to get rid of that 2 seconds of text that only shows on boot. :thinking:
 
Upvote 0
On mine I get it on every boot, and I think I did even before I moved to custom ROMs (long time ago though, so can't be sure). Maybe it's different with the way you did it (I used revone, which tells you it was a while ago ;)).

Personally I live with the warning anyway - doesn't seem worth flashing a custom hboot to remove it.

I got a HBoot 1.44 device even though I got mine in December :eek:
 
Upvote 0
You're not seeing it because you're still running the stock rom and kernel. I'm 100% stock as well,and don't see the red text either on normal boot.

Im with hadron,I've never run a custom hboot to avoid the text. I honestly don't understand why its such a big deal to some folks,and personally think its rediculous to risk installing a modified bootloader to get rid of that 2 seconds of text that only shows on boot. :thinking:

Thanks for the clarification, Scotty. I'll admit I'm one of those types that would want that text gone, but I'm also very hesitant to do something that could potentially kill my phone. Especially since I've only had it for a week. When I get around to flashing a custom ROM, I'll just learn to live with it. I'll just close my eyes when I reboot. ;)

BTW, you helped me a lot over on the Inspire4G forum. Nice to see you're over here too. Thanks again.
 
  • Like
Reactions: scotty85
Upvote 0
No prollem,glad to help. :)

If the bootloader is properly modified,the risk honestly is minimal if precautions are followed. However,anytime a new bootloader is flashed(stock or modified),there is a certain amount of risk,since without a bootloader your phone won't boot :eek:

The one is a wonderful phone with a ton of support and a lot of options. Just holler if you have questions! :)
 
Upvote 0
If you do use a custom hboot to remove the text, the main thing is never to switch to S-On without restoring a stock hboot first.

Admittedly I can't think of a good reason for reverting to S-On anyway! But if you turn security on when running a custom hboot, whose signature will not be valid, you will have a brick on your hands (the bootloader will be denied access, and without the bootloader you can't do anything. This then needs specialist hardware to fix it).

As long as you never forget that you should be ok.
 
Upvote 0
A few months back I updated the firmware in my my Inspire by extracting the radio & HBOOT images from an RUU and using a PD98IMG.zip to flash it. (Scotty, you actually tested the zip for me to verify it was good.) All the methods I seen for flashing a modified HBOOT for the One involve flashing through fastboot. And I don't recall seeing any mention of using PD**IMG.zip for flashing anything (radios, custom splash screens) through HBOOT on the One. Is that functionality just not available on this device?
 
Upvote 0
With the newer,non-sd card devices,its a bit differently to flash files via hboot. It can be done,with a correct USB OTG adapter,but placing a PxxxIMG(PNG07IMG for the one) onto internal does not work. The common method is to use fastboot and RUU mode wich may seem complex at first,but is actually pretty quick and easy once you do.it a couple times.

This is actually has been my favorite means of installing those files with all phones(even the inspire :) ) as It does not reply on proper name or sd.format,and the command.window gives you more info when a file fails to flash. Plus,I find it tedious to have to transfer files on and off of the sd card. I used it to install your firmware file on my inspire :)

I agree 100% with hadron. Once you've got s off,there is never a good reason to go back! Just keep in mind the responsibility of having a device that does no security checks,as it will happily let you brick it :eek: just make sure to know what you're flashing,don't flash things unnecessarily,and make sure to double check the integrity of anything you flash by verifying its md5 sum.
 
  • Like
Reactions: sharksfan7
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones