Related
Phones speaker, yet again, went out.
Took phone to best buy, rooted with a custom rom on it. Think it was Fresh 4.2 or something I don't remember tbh.
Get phone back and it's all manufactured and has latest update.
From what I've read, no root for it yet.
What do?
Well, if we can get HTC to roll another small update out for us for the bad timezone and other small bugs... maybe they'll unlock the boot loader for us. :-D Send HTC saying your timezone is messed up. :-D
Nrre said:
Phones speaker, yet again, went out.
Took phone to best buy, rooted with a custom rom on it. Think it was Fresh 4.2 or something I don't remember tbh.
Get phone back and it's all manufactured and has latest update.
From what I've read, no root for it yet.
What do?
Click to expand...
Click to collapse
If it happens again, just buy a new speaker off eBay. They're really easy to swap out and cheap as hell. Just look on you tube for a walk-through.
not terribly worried about it. i plan on switching to the BB Bold 9930 when it comes out to Sprint in a couple months.
I got my Evo4g, because my previous job had hours upon hours of down time. So SNESoid and many other games filled that void and made my work day enjoyable. New job...can't even take my phone into the building, at all =( So all I need my phone now is just text and email. I could probably just get a dumb flip phone really. But I couldn't do that after having a smartphone for a few years now.
Nrre said:
Phones speaker, yet again, went out.
Took phone to best buy, rooted with a custom rom on it. Think it was Fresh 4.2 or something I don't remember tbh.
Get phone back and it's all manufactured and has latest update.
From what I've read, no root for it yet.
What do?
Click to expand...
Click to collapse
Is it your same phone? Check your bootloader to see if it is still s-off. You may get lucky and still be able to install a custom recovery.
Sent from my PC36100 using XDA Premium App
Rem3Dy said:
Is it your same phone? Check your bootloader to see if it is still s-off. You may get lucky and still be able to install a custom recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
ha, not sure why I didn't think of that.
i jsut assumed it was a new phone, sticker under battery now says 'remanufactured' and the screen doesnt have the scratch it had before and the camera lens is brand new looking.
welp, S-ON hboot 2.16.000
What disadvantages do I have by rooting? Had my n4 since friday
Sent from my Nexus 4 using Tapatalk 2
Have you unlocked the bootloader yet?
There are no disadvantages to root, think of it like having admin permission of your system.
Unlocking the bootloader will wipe your device, as a safety feature. On a nexus, since it's only one command to unlock, it's recommended to do that straight away if you even think you might start down the road to custom town in the future.
Sent from my Nexus 10 using xda premium
Yup...as far as I'm concerned, everyone should ALWAYS root. A - it's part of what's truly awesome about Android, B - it will more than likely come in handy at some point and C - there really isn't any reason NOT to do it.
Just do it soon after getting the device (I had my N4 for about 30 min before I started the process...within an hr of getting it, the bootloader was unlocked, it was rooted, had a custom kernel and it was ROMd) since, as stated, a wipe is usually required. And, even still, some know how with titanium can even soften that blow.
Disadvantages? Potentially void your warranty, less secure device (malicious apps that ask for SU permission), rom flashing addiction, spending too much time on XDA.
The occasional app won't run rooted - TWC TV, for example.
Sent from my Nexus 4 using xda premium
So what happens if I don't root right away? That's what makes me nervous
Sent from my Nexus 4 using Tapatalk 2
ridearoundsolo said:
So what happens if I don't root right away? That's what makes me nervous
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Well, nothing. It's not a requirement.
You won't be able to use apps that need SU permission, that's all.
Unlocking your bootloader is not the same as rooting, you should do that asap if you plan on ever mucking around with your device.
lwfb said:
Well, nothing. It's not a requirement.
You won't be able to use apps that need SU permission, that's all.
Unlocking your bootloader is not the same as rooting, you should do that asap if you plan on ever mucking around with your device.
Click to expand...
Click to collapse
Why is required to unlock asap? I know about rooting its just the first time I've heard to unlock boot loader asap like does something get ruined if I hold off on unlocking the bootloader?
Sent from my Nexus 4 using Tapatalk 2
ridearoundsolo said:
Why is required to unlock asap? I know about rooting its just the first time I've heard to unlock boot loader asap like does something get ruined if I hold off on unlocking the bootloader?
Click to expand...
Click to collapse
It is not required to do it asap.
Some just recommend doing it quick because unlocking the bootloader wipes the phone. So you lose the data on there.
Story time:
Personally I always use the device for a while before I go near rooting and all the fun that comes with it, just to make sure I have a good product and stable device.
I had a Desire Z before, and had the motherboard replaced once because it had failed. When I got it back I tried it for maybe a day or two. I noticed it was a bit unstable and blamed it on the HTC software just being crap. So I rooted and flashed CM to it.
That turned out to be unstable as wel... Phone would just randomly reboot.
Unrooting and returning that Z to stock was a bit of a challenge. A guy on IRC helped me out tremendously and I'm still thankful for it, because together we succeeded.
And I could RMA once more...
So that's why I tend to wait a bit and confirm my device is solid before I go rooting.
stejoo said:
It is not required to do it asap.
Some just recommend doing it quick because unlocking the bootloader wipes the phone. So you lose the data on there.
Story time:
Personally I always use the device for a while before I go near rooting and all the fun that comes with it, just to make sure I have a good product and stable device.
I had a Desire Z before, and had the motherboard replaced once because it had failed. When I got it back I tried it for maybe a day or two. I noticed it was a bit unstable and blamed it on the HTC software just being crap. So I rooted and flashed CM to it.
That turned out to be unstable as wel... Phone would just randomly reboot.
Unrooting and returning that Z to stock was a bit of a challenge. A guy on IRC helped me out tremendously and I'm still thankful for it, because together we succeeded.
And I could RMA once more...
So that's why I tend to wait a bit and confirm my device is solid before I go rooting.
Click to expand...
Click to collapse
I agree about testing the device to see if it can hold on its own before rooting, my last phone the HTC one s was a nightmare with rooting and flashing, but I know this is much easier because I own a nexus 7 which is rooted and running codefirex
Sent from my Nexus 4 using Tapatalk 2
Hello I just receive my Nexus 4 and I Rooted 5 minutes later
Now I have a question If the Nexus 4 is Rooted it will continue receiving Android Os Updates directly from Google?
Thanks
Marioaguado said:
Hello I just receive my Nexus 4 and I Rooted 5 minutes later
Now I have a question If the Nexus 4 is Rooted it will continue receiving Android Os Updates directly from Google?
Thanks
Click to expand...
Click to collapse
Yes as long as it is stock and the kernel is stock you can receive OTA (over the air) updates. You might/will probably lose root though when the update is installed but that is not a problem, just reflash it.
Yea...you will possibly void the warranty. You can usually flash back to stock if need be and, if you break your screen or something and just want to use insurance or something, just dip it in water for an hr or so...they'll never know what you did to it other than dip it in water.
And yes, you do open the door to malware, possibly. Gotta be careful about what you install and what you grant permissions to.
The reason I say to do it soon, as was said, unlocking, (sometimes) rooting and romming will usually wipe your device. If you do all this as soon as you get the device, it doesn't matter. If you use the phone for however long, you'll lose all that data. That's the logic behind it.
I've had the phone for little over a month now and I just rooted it yesterday. I had no intention of rooting, but I got myself a Moga controller and to get the most out of that controller, it requires root.
Of course, by that time I already had all my apps & such configured exactly as I like them, so it was a bummer to have to re-download and reconfigure everything. ESPECIALLY the internal "sdcard"s contents. I was used to being able to restore and wipe without losing my personal files because all my prior phones had sdcard slots. It completely slipped my mind that the Nexus 4 "sdcard" is pretty much just its internal memory so I lost a handful of pics and other things. For these reasons, I would recommend that even if you thitnk you MIGHT want to root in the future, you might as well do it now and save yourself the time of further redownloading and reconfiguring everything a month from now.
This was a question I had so the responses have been interesting. I've rooted my previous non-Nexus devices (Mytouch 4G, HTC Sensation 4G) mostly so I could get an aosp like ROM. I had a Nexus One but never rooted it. Still trying to decide if I'm going to root my Nexus 4 because I haven't really experienced a ROM that comes without minor issues (Picasa, GPS/Navigation, etc.) The custom ROMs do have a lot of cool features though.
Sent from my Nexus 4 using xda app-developers app
The features and theming is tempting but I'm a bit worried if there's a performance drop, are there Roms that completely surpass stock speed and without bugs?
Sent from my Nexus 4 using Tapatalk 2
phon00b said:
I've had the phone for little over a month now and I just rooted it yesterday. I had no intention of rooting, but I got myself a Moga controller and to get the most out of that controller, it requires root.
Of course, by that time I already had all my apps & such configured exactly as I like them, so it was a bummer to have to re-download and reconfigure everything. ESPECIALLY the internal "sdcard"s contents. I was used to being able to restore and wipe without losing my personal files because all my prior phones had sdcard slots. It completely slipped my mind that the Nexus 4 "sdcard" is pretty much just its internal memory so I lost a handful of pics and other things. For these reasons, I would recommend that even if you thitnk you MIGHT want to root in the future, you might as well do it now and save yourself the time of further redownloading and reconfiguring everything a month from now.
Click to expand...
Click to collapse
Always backup your apps and data with Titanium Backup or with adb before unlocking your bootloader =/
ridearoundsolo said:
The features and theming is tempting but I'm a bit worried if there's a performance drop, are there Roms that completely surpass stock speed and without bugs?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
If you're only worried about performance, CyanogenMod is as stable if not better than stock roms. If you're looking for optimization, I would suggest ParanoidAndroid. Most roms out there are pretty stable, except for a few hiccups, and I think the best advice is that you should try it personally and have a feel at it. :good:
I would say do it if you are interested constantly flashing ROMs. The only reason I've flashed my S2 because of the T-Mobile bloat. But then I messed more until I bricked.
The N4 is very clean and good as it is and I keep it that way.
I rooted my optimus s but all the roms for it sucksuck
Sent from my LS670 using xda app-developers app
So I ended up rooting and tried pa but am liking xylon stable a lot and about to give rasbean a try
Sent from my Nexus 4 using xda app-developers app
Will google know if i rooted my phone? or unlocked bootloader. I was think of rooting it but then again i dont want to lose the warranty on it.
teddytales66 said:
Will google know if i rooted my phone? or unlocked bootloader. I was think of rooting it but then again i dont want to lose the warranty on it.
Click to expand...
Click to collapse
If you unroot it, I don't think they would know. But as in Google, I'm assuming that's the manufacturer because Google doesn't process warranties, it's the manufacturer, even if you have a nexus.
Sent from my Nexus 7 using Tapatalk HD
teddytales66 said:
Will google know if i rooted my phone? or unlocked bootloader. I was think of rooting it but then again i dont want to lose the warranty on it.
Click to expand...
Click to collapse
You can always unroot, but, to be honest, I don't think it matters, a lot of urban legend when it comes to rooting. I mean, the nexus 4 is a developer phone, what would a developer do with an unrooted phone with a locked bootloader? Root it, wipe it then flash it!
Sent from my Nexus 4 using xda app-developers app
Google won't know you're rooted until you send your device back for to them for repairs in case of a broken phone.
So, let's say you want to have the screen replaced. Before you RMA your unit, it's wise to lock the bootloader again and un-root your phone. THIS thread provides all the instructions for that. Even if your screen is broken, you can still return to a locked bootloader and an unrooted phone. For a little more information about this all, you could also search the forums for something along the lines of "RMA bootloader unroot". I'm sure there are other people who have wanted to return to stock before returning their devices.
So Google won't know unless you send the device to them. So if you're ever sending it back, don't forget to lock the bootloader, and unroot your device.
Yup, you can always unroot. BUT, if Google really wanted to it could figure out what phones are rooted and what phones aren't. Think about when you go into the Wallet app with a rooted device. The app knows and tells you it is unsupported. I really don't think they care that much though..
Not unless you put a billboard sign up near Google's headquarters!
At some point (I don't know if this is still the case) Google didn't allow rooted phones to upload photospheres to GMaps as they could fake their location and essentially end up doing something like placing the Colosseum in the middle of New York. It's not difficult for them to figure out which devices are rooted and block them for certain things but in most cases it won't make a difference.
Nope as long as you unroot, return to stock and lock the bootloader, they will not know.
Sent from my Nexus 4 running the latest PA ROM 3+ and Franco's M1 kernel
I know its not out yet but most phones are getting rooted before released. On top of that, the korean version is already rooted.
So thats why I ask when you guys think we will have root? Is the verizon version that different from the Korean version (Lock bootloader)?
Just wanted an idea before i pick the phone up next week.
Thx
In 18 hours, give or take a couple.
From your lips to God's ears
Sent from my XT926 using Tapatalk 4
i'll take the over.
FynxSyndct said:
i'll take the over.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2440163&page=9
As of right now, LG has no drivers that support the vzw LG G2 as far as anyone on this forum has found. If we had proper drivers we may be able to root right now using the same method the ATT variant used.
emplox said:
As of right now, LG has no drivers that support the vzw LG G2 as far as anyone on this forum has found. If we had proper drivers we may be able to root right now using the same method the ATT variant used.
Click to expand...
Click to collapse
I don't have the G2 yet. But someone should call LG support for a link to the drivers. Just say your pic isn't reading the MTP or something.
800-243-0000
I will tomorrow morning if nobody else does.
Sent from my VS980 4G using Tapatalk 4
I called, they sent me to lgforums.com and clicked on drivers and resources and it has the 2.7.1 driver. That is all that's available
Sent from my VS980 4G using Tapatalk 4
Coming from a GNex, this device is nothing but improvement other than not having an unlocked bootloader and root. If at the minimum they(developers) can not get the Verizon version rooted during my 14 day return period, this device will be going back. Too much BS loaded on this thing, but I do want to love it. Is there a bounty yet for root and unlock??
Lesser Version said:
Coming from a GNex, this device is nothing but improvement other than not having an unlocked bootloader and root. If at the minimum they(developers) can not get the Verizon version rooted during my 14 day return period, this device will be going back. Too much BS loaded on this thing, but I do want to love it. Is there a bounty yet for root and unlock??
Click to expand...
Click to collapse
I also came from a GNex, so same here. Love the new G2 phone, but I am not sure why Verizon always seems to go through the added effort of obfuscating root for power users.
Root is the absolute bare minimum for me. For now, I am in a two week holding pattern... I can't get too attached to the device because if there's no root, the phone is worthless.
DeaconBoogie said:
I also came from a GNex, so same here. Love the new G2 phone, but I am not sure why Verizon always seems to go through the added effort of obfuscating root for power users.
Root is the absolute bare minimum for me. For now, I am in a two week holding pattern... I can't get too attached to the device because if there's no root, the phone is worthless.
Click to expand...
Click to collapse
Exactly!! Root is bare minimum, unlock will be better.....:good:
Nothing is going to happen on the vzw g2 until usb debugging works properly. As far as it looks right now there is nobody on a vzw g2 that has it actually working. It's able to be checked, but when you plug it in there is no notification in the notification bar that says it's working....and not a single person has been able to get the phone detected by adb.
Lesser Version said:
Exactly!! Root is bare minimum, unlock will be better.....:good:
Click to expand...
Click to collapse
DeaconBoogie said:
I also came from a GNex, so same here. Love the new G2 phone, but I am not sure why Verizon always seems to go through the added effort of obfuscating root for power users.
Root is the absolute bare minimum for me. For now, I am in a two week holding pattern... I can't get too attached to the device because if there's no root, the phone is worthless.
Click to expand...
Click to collapse
emplox said:
Nothing is going to happen on the vzw g2 until usb debugging works properly. As far as it looks right now there is nobody on a vzw g2 that has it actually working. It's able to be checked, but when you plug it in there is no notification in the notification bar that says it's working....and not a single person has been able to get the phone detected by adb.
Click to expand...
Click to collapse
Agreed just left my Gnex also. I think I will stick it out past the 14 days. VZW doesn't have anything else to offer even close to the G2. The S4 doesn't interest me at all.
Lesser Version said:
Coming from a GNex, this device is nothing but improvement other than not having an unlocked bootloader and root. If at the minimum they(developers) can not get the Verizon version rooted during my 14 day return period, this device will be going back. Too much BS loaded on this thing, but I do want to love it. Is there a bounty yet for root and unlock??
Click to expand...
Click to collapse
I'm in the same boat. on a GNex for 2 years and this is the first device that's coaxed me to switch. If we don't have (at least) root by 2 weeks it's going back and I'm back to the drawing board. I'm okay with waiting on the bootloader but that could also be a risk given the current status for other devices still not being unlocked.
Part of the reason I've stuck with the GNex so long is the custom ROM scene - and specifically Paranoid Android which is fantastic on that device. G2 has me happy so far but getting rid of the VZW turn on/off sounds and animations is the first thing that has to go.
mouf32 said:
Agreed just left my Gnex also. I think I will stick it out past the 14 days. VZW doesn't have anything else to offer even close to the G2. The S4 doesn't interest me at all.
Click to expand...
Click to collapse
I picked up an s4 for my wife when I got my g2, after using both, g2 is much better imo
Sent from my VS980 4G using Tapatalk 4
p2im0 said:
I'm in the same boat. on a GNex for 2 years and this is the first device that's coaxed me to switch. If we don't have (at least) root by 2 weeks it's going back and I'm back to the drawing board. I'm okay with waiting on the bootloader but that could also be a risk given the current status for other devices still not being unlocked.
Part of the reason I've stuck with the GNex so long is the custom ROM scene - and specifically Paranoid Android which is fantastic on that device. G2 has me happy so far but getting rid of the VZW turn on/off sounds and animations is the first thing that has to go.
Click to expand...
Click to collapse
We are truly in the same boat like you said. The rom scene is what kept the GNex shortcomings(battery life/radios) in check. You are right about the current rate at which bootloaders are being unlocked. Nexus devices may be the only way to go. Does anyone know LG's history for having devices unlockable( bootloader), dev support, and receiving android updates? My relationship with this phone so far is like that hot girl at the bar who's got it all, but something just doesn't seem right.....
Lesser Version said:
We are truly in the same boat like you said. The rom scene is what kept the GNex shortcomings(battery life/radios) in check. You are right about the current rate at which bootloaders are being unlocked. Nexus devices may be the only way to go. Does anyone know LG's history for having devices unlockable( bootloader), dev support, and receiving android updates? My relationship with this phone so far is like that hot girl at the bar who's got it all, but something just doesn't seem right.....
Click to expand...
Click to collapse
The thing that doesn't seem right is that it's on Verizon (read: mental issues). I really want to nab this thing, but with the way the GS4 was handled, along with the HTC One, I don't know if I can bring myself to do it.
Verizon G2 just got rooted. I believe
Root achieved
http://forum.xda-developers.com/showthread.php?p=45564780&posted=1#post45564780
I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Are you S-Off? Does your computer see it?
@dottat
acbrocksit said:
I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Click to expand...
Click to collapse
Try charging with oem stock charger and cable overnight.
If it starts to take a charge, prepare a blank SDcard with
2PS6IMG_PERFUME_WL_M60_SENSE80GP_VZW_VERIZON_WWE_1.85.605.8_Radio_1.0.C010141xxxx.zip or similar. Rename it 2PS6IMG.zip with only one .zip at end. Try and boot with volume down and power.
With any luck, you'll get enough charge on it to allow you to do this software install.
Hard Brick
I did ask Santod and he said it is hard bricked. I flashed the wrong aboot image and now the phone does nothing, no power, no response from any combination of button presses, the computer does not see it. I don't know of anything else that might work.
I'm going to try to see if HTC can fix it, if not then I may use it for parts because the phone looks great. So I may try to get a beat up phone with a busted screen and swap out the guts.
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Bricked / aboot
dottat said:
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, I read your info and warning about it after the fact.
acbrocksit said:
Yeah, I read your info and warning about it after the fact.
Click to expand...
Click to collapse
Yep...Moreso posting for anyone who sees this as further warning.
Sent from my HTC6545LVW using Tapatalk
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Spinkness said:
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Click to expand...
Click to collapse
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
acbrocksit said:
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
Click to expand...
Click to collapse
They didn't even ask why Verizon wouldn't warranty it?
Sent from my m8wl using Tapatalk
Evocm7 said:
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Spinkness said:
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Click to expand...
Click to collapse
No problem. I called Verizon and even though it was dead, they were still able to communicate with the phone while I was talking to them on another phone. The power led was flashing red and then she said the phone wasn't under warranty because there was custom software. I ended up sending it to HTC where they sent me a refurb with a bad mic then the second one I have now is fine. So after a month and $40 worth of shipping charges, I have a working 10 again. I honestly don't think HTC cares about rooted phones and the time it would take to diagnose what actually happened in our down grade brick wouldn't be worth it for them.
Sent from my HTC6545LVW using Tapatalk
If it's under warranty, make a claim. Verizon will tell you to ship it back to another location where all they do is refurbish the phones for subsequent resale. You will likely get a replacement refurb. The refurbisher has absolutely no clue what you have done; they handle these things in bulk and I have not once ever heard of a phone under warranty being "refused" because an end user did something stupid. Which, as @dottat says, is what flashing an edited aboot to get rid of the red text is, by the way. Stupid.
I *like* the red-text, frankly. It reminds me whether I'm running pure stock boot and recovery or not while I'm flashing updates, etc.