Database Info

How do I prepare my phone for roms?

I need to root, unlock, and install CWM right? How exactly do I do this? I tried to locate a how to without any luck.

The dev section is filled with all the info you need to know.
Also, not trying to be a **** but saying you searched when it is obvious that you didn't will get you nowhere.

OK I've read some more and had a couple more questions...
I noticed that the roms I've looked at don't require an unlocked phone. What's the point of unlocking the phone then? Can I just root and install CWM?
Some roms say "needs the 1.85 base." What does this mean and how do I get it before flashing a rom?
Thanks!

johnl199 said:
OK I've read some more and had a couple more questions...
I noticed that the roms I've looked at don't require an unlocked phone. What's the point of unlocking the phone then? Can I just root and install CWM?
Some roms say "needs the 1.85 base." What does this mean and how do I get it before flashing a rom?
Thanks!
Click to expand...
Click to collapse
Some of the roms, prior to the unlock discovery, were executable as an RUU. All the updated versions require recovery which you need the bootloader unlocked to get in to. It's a painless process and there's even a 1-Click script method for those who dont want to take chances.

Will I be able to get the phone back to COMPLETELY stock should I decide to sell it in the future?

From what I know it will say relocked or tampered but maybe I'm wrong
Sent from my HTC One X using xda premium

After unlocking your phone, there will be no way to get back to 100% stock unless we can get S-OFF (which hopefully may be in the near future due to a few devices already being S-OFF).
However, you can root your device and not unlock it (1.82 and prior as of now) and still be able to revert to 100% stock as if it came right out of the box.
Most of the ROMs currently do not require an unlocked bootloader.
However, this will definitely change as we begin to see custom kernels (hopefully soon with the release of the source by HTC Dev) and more complex ROMs (such as those based on AOSP, such as CM9 and AOKP).
So in short, you can still use most of the ROMs in the dev section. Just be aware however that if you do not unlock then you cannot install CWM (limiting the number of ROM options) and also if you update past 1.82.502.3 then you cannot root (at this time, other root exploits are being explored).

Is unlocking your bootloader the same as carrier unlocking your phone?
Does this mean that say, AT&T phones could be used on Tmobile?

lamenramen said:
Is unlocking your bootloader the same as carrier unlocking your phone?
Does this mean that say, AT&T phones could be used on Tmobile?
Click to expand...
Click to collapse
Nope. You are thinking of SIM unlock.
Bootloader unlock lets you load custom ROMs and change recovery, that's all.

[Video Guide] How To Root Galaxy S4 I337 / I337m Easy & User Friendly

Hey folks. It's me again :victory: So I've got another super easy video guide on how to root your shiny new Samsung Galaxy S4 I337 or I337m.
This guide is using djrbliss's Motochopper tool. This tool has made it easier than ever to root a device! So BIG thanks goes out to him!
Links to everything can be found in the video description.
Enjoy

Here is a couple of more. I figure its better to keep them all in one place so people can decide which guide they want to use.
http://forum.xda-developers.com/showthread.php?t=2257039
http://forum.xda-developers.com/showthread.php?t=2257058
I think there might be a couple more out there but this should help people to answer any possible question about rooting that they could ever have.
If you have the AT&T OTA (MF3) for the SGH-I337 S4, the method in the OP does not work. Here is a method for rooting MF3:
http://forum.xda-developers.com/showthread.php?t=2387577
For Canadian MG1 Firmware, try CF Auto-Root download for the SGH-I337M:
http://forum.xda-developers.com/showthread.php?t=2293800

Just sold my Rogers S2 LTE because I upgraded to the S4. My quick question, if I ROOT and retain the original Samsung Recovery will I be able to still get and do official firmware upgrades? This is the only thing stopping me from going forward with rooting.

You can still get updates, but you will loose your root access with each update.

thanks: im now rooted and sim unlocked for free!

Slade8525 said:
thanks: im now rooted and sim unlocked for free!
Click to expand...
Click to collapse
Hey, how did you sim unlock it for free, do you mind sharing?

yeah sure!
similar method worked for my GS III; havent tested the GS IV with different sim just yet but GF's old GS III is working just fine for her sister in Canada (Bell i think). GF found it actually, and did it to hers 1st. ill know if it works when we leave for work in Montreal next week or if i bum a t-mobile cell from a friend.
http://forum.xda-developers.com/showthread.php?t=2282683

Stoneyguy said:
You can still get updates, but you will loose your root access with each update.
Click to expand...
Click to collapse
WRONG, I am unable to update my device, it says that my phone has been modified, and yes, I have rooted it with this video.

Whenever I try this method, when it goes to push the exploit, it says error multiple devices or something. when I only have the S4 plugged in. Followed step by step.

Dragosmp said:
WRONG, I am unable to update my device, it says that my phone has been modified, and yes, I have rooted it with this video.
Click to expand...
Click to collapse
My phone is rooted and still shows official in phone status. There is a post on how to regain that status while still maintaining your root.

Stoneyguy said:
My phone is rooted and still shows official in phone status. There is a post on how to regain that status while still maintaining your root.
Click to expand...
Click to collapse
Could you post a link to where it shows how to regain the status will maintaining the root?

rsarwar said:
Could you post a link to where it shows how to regain the status will maintaining the root?
Click to expand...
Click to collapse
The link has already been posted on the first page.

thanks worked great just rooted min in 5 min

Safe to root?
Excuse my ignorance, but on another thread it was suggested that in the absence of recovery and a backup image rooting might be premature. Is the general consensus now that it is safe to root? There seems to be some backup images around thought I don't know if they have been tested, and I haven't heard about recovery.
sblevine

Newbie here... couple of questions
I have the same concern as the member above... is it already possible to restore the phone if something goes bad? Is there instructions anywhere around this forum? where?
Also, once you root the phone you can proceed to download a ROM and install it... when a new ROM version is available and I download and install it, do I lose the root?
What is the best (if more than one is already available) for the ATT S4?
Thank you all and sorry for the "newbieness"....
Cheers:good:

speed2001 said:
I have the same concern as the member above... is it already possible to restore the phone if something goes bad? Is there instructions anywhere around this forum? where?
Also, once you root the phone you can proceed to download a ROM and install it... when a new ROM version is available and I download and install it, do I lose the root?
What is the best (if more than one is already available) for the ATT S4?
Thank you all and sorry for the "newbieness"....
Cheers:good:
Click to expand...
Click to collapse
No, rooting gives you certain superuser privileges. You can use Titanium Backup to freeze and restore bloatware, AdBlock to block advertisements, etc. Some phone tracking software and remote desktop control software requires root as well.
You cannot modify the basic operating system (ROM) until the bootloader is unlocked. You can overwrite the files, but that will brick your device since the bootloader checks signatures.
There is a bootloader exploit for the ATT S4 that will be released within the next week. The developer was waiting until the Verizon version of the S4 was available so more people would be able to use the exploit before it was patched.
Do not accept an OTA update for your device as that is how they will patch the bootloader exploit.
1. Root your device.
2. Carrier unlock your device.
3. Install custom ROM when bootloader is exploited later this week.

Relys said:
No, rooting gives you certain superuser privileges. You can use Titanium Backup to freeze and restore bloatware, AdBlock to block advertisements, etc. Some phone tracking software and remote desktop control software requires root as well.
You cannot modify the basic operating system (ROM) until the bootloader is unlocked. You can overwrite the files, but that will brick your device since the bootloader checks signatures.
There is a bootloader exploit for the ATT S4 that will be released within the next week. The developer was waiting until the Verizon version of the S4 was available so more people would be able to use the exploit before it was patched.
Do not accept an OTA update for your device as that is how they will patch the bootloader exploit.
1. Root your device.
2. Carrier unlock your device.
3. Install custom ROM when bootloader is exploited later this week.
Click to expand...
Click to collapse
Cool, thanks for the reply. I was under the impression that the bootloader was already exploited. Pure BS those protections that always end up broken like the IOS ones. What I would like is to have the S4 as factory released and load a good ROM without any problems and no bloatware. If not for the warranty I would buy an unlocked phone elsewhere.
Well, let's wait for the exploit next week. I don't want to brick my phone and not able to restore it. I will keep checking back.
Cheers and thanks again
Speed

Relys said:
No, rooting gives you certain superuser privileges. You can use Titanium Backup to freeze and restore bloatware, AdBlock to block advertisements, etc. Some phone tracking software and remote desktop control software requires root as well.
You cannot modify the basic operating system (ROM) until the bootloader is unlocked. You can overwrite the files, but that will brick your device since the bootloader checks signatures.
There is a bootloader exploit for the ATT S4 that will be released within the next week. The developer was waiting until the Verizon version of the S4 was available so more people would be able to use the exploit before it was patched.
Do not accept an OTA update for your device as that is how they will patch the bootloader exploit.
1. Root your device.
2. Carrier unlock your device.
3. Install custom ROM when bootloader is exploited later this week.
Click to expand...
Click to collapse
Regarding the bold above, I am honestly not that interested in the Custom ROMS right now, only rooting and with this method it does not install any custom recovery, right? As well, if I root via this method will I be able to still do the OTA updates since Samsung recovery is untouched? I know and understand that I will likely loose root, but I can always re-root, right?
I am itching to root and this is the only thing stopping me as there seems to be much confusion about this.
BTW I am on Rogers (Canada) i337M if it makes a difference

rsarwar said:
Regarding the bold above, I am honestly not that interested in the Custom ROMS right now, only rooting and with this method it does not install any custom recovery, right? As well, if I root via this method will I be able to still do the OTA updates since Samsung recovery is untouched? I know and understand that I will likely loose root, but I can always re-root, right?
I am itching to root and this is the only thing stopping me as there seems to be much confusion about this.
BTW I am on Rogers (Canada) i337M if it makes a difference
Click to expand...
Click to collapse
I've been a bit confused as well despite reading hundreds of posts and watching referenced videos (I've also been hesitant to ask questions given the culture of this board). Here is what I hope is accurate, please correct where I am wrong:
We can root I337 now.
Doing a simple root now is reversible, ie, can be un-rooted.
The bootloader unlock is needed primarily for custom roms.
If one does not desire a custom rom, there is no reason to wait to root.
And, a few questions:
Does rooting wipe out apps, settings, and/or data?
Will an AT&T android system update remove the root?
If so, can we just root again?
Thank you for clarifications. I'm sure there are many that are not posting with some of these questions. I will be glad to put together a noobie's guide if I can get a handle on all of this. It is all out there somewhere, but very fragmented, and often one post is contradicted by another.

zekeblue said:
I've been a bit confused as well despite reading hundreds of posts and watching referenced videos (I've also been hesitant to ask questions given the culture of this board). Here is what I hope is accurate, please correct where I am wrong:
We can root I337 now.
Doing a simple root now is reversible, ie, can be un-rooted.
The bootloader unlock is needed primarily for custom roms.
If one does not desire a custom rom, there is no reason to wait to root.
And, a few questions:
Does rooting wipe out apps, settings, and/or data?
Will an AT&T android system update remove the root?
If so, can we just root again?
Thank you for clarifications. I'm sure there are many that are not posting with some of these questions. I will be glad to put together a noobie's guide if I can get a handle on all of this. It is all out there somewhere, but very fragmented, and often one post is contradicted by another.
Click to expand...
Click to collapse
Your assumptions are correct:
1. Yep.
2. Yes, you can delete busybox and su in your system directory to get your phone switch your phone from "Custom" to "Official" status. If you install SuperSu and remove Superuser you can have root while keeping "Official" status.
3. Correct.
4. If you **** up while messing around with root you can recover to stock ROM via Odin or Kies. There is no reason to wait for root.
To answer your questions.
1. No, nothing changes. You just enable superuser privileges.
2. Typically yes. Don't accept OTA's until your know they're safe.
3. It depends if they patch the exploit or not.

[Q] Technical question(s) on bootloaders

(As a foreword, I've been searching and trying to find these answers myself but I haven't had much luck. If there are resources out there covering my questions, please direct me there. Thanks!)
Could someone please inform me of the specific difference(s) between the VRALEC and VRALE6 bootloaders? Also any background info would be interesting to know as well (order in which they were leaked, timeframes, circumstances etc).
Next question: I was able to successfully ODIN the VRALEC bootloader (only) to my stock phone on VRBMF1. When I tried to do the same with VRALE6 it failed with a signing-related error. However I was able to flash the VRALE6 directly using the CASUAL utility and that worked fine. I don't understand why/how the phone will allow itself to boot from that file, but wouldn't allow it to be ODIN'd. Could somebody enlighten me? Also, if I were to have tried ODIN'ing the entire VRALE6 bootchain, would that have succeeded?
Also, is there any rationale for using any other bootloader(s)? There appear to be at least 10 different bootloader and/or bootchain version varients out on the web in different places. From what I can gather though, only the two listed above are significant since they are 'unlocked'.
Lastly, which bootloader does the Developer Edition phone use? Does it come unlocked, or is it unlock-able via some web site or something? If it has its own 'special' unlocked bootloader, why could we not simply get a copy and use that on retail phones rather than the old/leaked version widely used now?
B

pluto01 said:
(As a foreword, I've been searching and trying to find these answers myself but I haven't had much luck. If there are resources out there covering my questions, please direct me there. Thanks!)
Could someone please inform me of the specific difference(s) between the VRALEC and VRALE6 bootloaders? Also any background info would be interesting to know as well (order in which they were leaked, timeframes, circumstances etc).
Click to expand...
Click to collapse
Well, for the longest time the VRALEC was titled the "boot chain" and I'm seeing now in Invisiblek's awesome thread over on Rootz, that's not the case anymore. So, I'll preface this by saying referring to both VRALEC and VRALE6 terms as "bootloaders" sounds weird now because VRALEC was originally titled "VRALEC.bootchain.tar".
VRALEC file should be a "tar" and the VRLE6 file should be a "zip." Cool? Here's how to differentiate, the VRALEC.bootloader.tar needs to be flashed in Odin to allow you to install a custom recovery. It is essentially just the first step of several to unlock the bootloader, it is not unlocked at this point. Someone of a more technical background can explain this better but its like this file is hijacking the boot sequence and telling the phone everything is still recognized as official firmware. There's no trigger that prompts the phone to give you the yellow triangle warning. Once a custom recovery is installed, you need to flash in recovery the VRLE6.zip to unlock the bootloader. Both of these files come from a pre-release VZW GSIII that were so graciously provided to AdamOutler by an African-Canadian Sock Monkey. Seriously, check post #317. This also serves to answer your question about times, leaked, etc. Moving on!
Next question: I was able to successfully ODIN the VRALEC bootloader (only) to my stock phone on VRBMF1. When I tried to do the same with VRALE6 it failed with a signing-related error. However I was able to flash the VRALE6 directly using the CASUAL utility and that worked fine. I don't understand why/how the phone will allow itself to boot from that file, but wouldn't allow it to be ODIN'd. Could somebody enlighten me? Also, if I were to have tried ODIN'ing the entire VRALE6 bootchain, would that have succeeded?
Click to expand...
Click to collapse
As I said above, VRALE6 should be a zip file and needs to be flashed in custom recovery NOT Odin. That's the key difference.
Also, is there any rationale for using any other bootloader(s)? There appear to be at least 10 different bootloader and/or bootchain version varients out on the web in different places. From what I can gather though, only the two listed above are significant since they are 'unlocked'.
Click to expand...
Click to collapse
Nope. Idk what you mean by "at least 10 different bootloader and/or bootchain version varients." Maybe there is a "bootloader" per each OTA that we have received? But honestly, every OTA thus far has been rooted/unlocked via almost the exact methods so this is a moot topic. There are only two unlock files of significance for any root/unlock method for the VZW GSIII: VRALE6.zip and VRALEC.tar
Lastly, which bootloader does the Developer Edition phone use? Does it come unlocked, or is it unlock-able via some web site or something? If it has its own 'special' unlocked bootloader, why could we not simply get a copy and use that on retail phones rather than the old/leaked version widely used now?
B
Click to expand...
Click to collapse
Well, AdamOutler actually received some help and got this phone unlocked well before the dev edition was released last year so there was never a need to look towards that device for bootloader unlock help. I have no clue about how to unlock that device and there's been no reason to think about having (at the time) a $650 dev edition GSIII when the retail one was officially unlocked. No clue on compatibility with bootloaders between either device.

[Q] Unlock bootloader on XT926 rooted after JB OTA update 9.30.1

I've successfully rooted my Droid RAZR MAXX HD with stock firmware version 9.30.1, but I can't seem to figure out how to unlock the bootloader.
The one catch with my phone being rooted is that it always ends up in fastboot when it boots. A simple
Code:
fastboot continue
fixes the problem, but I was wanting to flash CWM Recovery to install CM.
I have a working su/Superuser.apk, but I can't seem to fix the bootloader dilemma.

The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app

Jhall8 said:
The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Okay... I also have another wonderful problem: my phone consistently gets into fastboot mode upon startup, with my current workaround of doing fastboot continue. Is there any way to fix my currently locked bootloader?

impinball said:
Okay... I also have another wonderful problem: my phone consistently gets into fastboot mode upon startup, with my current workaround of doing fastboot continue. Is there any way to fix my currently locked bootloader?
Click to expand...
Click to collapse
As Jhal said, you can't "fix" your bootloader, it's locked since you're on the newest OTA and it can't be unlocked. With that being said, your phone is not booting into fastboot because you're rooted. It's booting into FB because you tried to flash something that didn't work. What other things have you done or attempted to do, besides rooting? This will help us help you, the info you provided is pretty vague.

RikRong said:
As Jhal said, you can't "fix" your bootloader, it's locked since you're on the newest OTA and it can't be unlocked. With that being said, your phone is not booting into fastboot because you're rooted. It's booting into FB because you tried to flash something that didn't work. What other things have you done or attempted to do, besides rooting? This will help us help you, the info you provided is pretty vague.
Click to expand...
Click to collapse
I have done absolutely nothing beyond rooting it, installing Superuser & SuperSU (both through a script I can attach, but I'm on the wrong computer), and backed up a slew of apps.
This first begun when I modified the script to fix a bug in it (ash in JB 4.2 doesn't have a -f switch in rm, and the script had a 'rm -f'). If that bug didn't exist, then it would've still happened the first of several times (I attempted it about 4-5 times, but only the last caused this). The rm -f was actually doing effectively (with successful root privileges) 'rm -f /system/install-script-2.sh', but the script actually had another script to be put into it at the location /system/install-script.sh.

???
Start by detailing steps in your 2nd paragraph.
Your boot is locked if it was never unlocked before you upgraded to ...79 or later

what a coincidence i just got a xt926 and im at the same spot.. 9.30.1 rooted but locked ... iguess we're screwed huh

impinball said:
I've successfully rooted my Droid RAZR MAXX HD with stock firmware version 9.30.1, but I can't seem to figure out how to unlock the bootloader.
The one catch with my phone being rooted is that it always ends up in fastboot when it boots. A simple
Code:
fastboot continue
fixes the problem, but I was wanting to flash CWM Recovery to install CM.
I have a working su/Superuser.apk, but I can't seem to fix the bootloader dilemma.
Click to expand...
Click to collapse
Looks like you either flashed a fastboot or used a tool that used the command "fastboot oem fb_mode_set" which causes the phone to boot directly into fastboot mode. It can usually be fixed with the command "fastboot oem fb_mode_clear".

skeevydude said:
Looks like you either flashed a fastboot or used a tool that used the command "fastboot oem fb_mode_set" which causes the phone to boot directly into fastboot mode. It can usually be fixed with the command "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Didn't work. It is still booting there on its own upon start-up.
Also, I will mention that I did commit an act of stupidity: trying to flash against a bootloader that I couldn't verify was unlocked yet. I stupidly ran the command when I wasn't even 50% sure that it was unlocked yet (and is likely the cause of all my problems):
Code:
fastboot flash recovery <cwm-file>.zip
I'm trying my hardest to avoid sending this to Motorola just for them to charge me for the replacement, saying I've voided any warranty that exists with the phone. I have the original firmware to flash just in case, but I don't have the Motorola fastboot (for the dev editions).

impinball said:
Didn't work. It is still booting there on its own upon start-up.
Also, I will mention that I did commit an act of stupidity: trying to flash against a bootloader that I couldn't verify was unlocked yet. I stupidly ran the command when I wasn't even 50% sure that it was unlocked yet (and is likely the cause of all my problems):
Code:
fastboot flash recovery <cwm-file>.zip
I'm trying my hardest to avoid sending this to Motorola just for them to charge me for the replacement, saying I've voided any warranty that exists with the phone. I have the original firmware to flash just in case, but I don't have the Motorola fastboot (for the dev editions).
Click to expand...
Click to collapse
First, there is no Dev Edition Fastboot....the closest would be Bell ICS since Bell shipped unlocked/unlockable Atrix HD's.
You don't flash zip files with fastboot flash.....Why is this becoming an issue these days?* The kernel is "fastboot flash boot boot.img"
*just thinking out loud
EDIT: Just realized that this was the RAZR HD forums.....just replying to quoted posts this morning....Not sure about RAZR HD Dev Edition fastboots....

Jhall8 said:
The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The shame is, I never cared about unlocking the bootloader, as I prefer to stick to OTA's, but I do require root. So that's all I've ever done. I'm successfully rooted with the locked bootloader on 9.30.1, but it seems (at least as far as I've read on here) that I'm stuck there as I can't go anywhere else and maintain root. Would love kitkat, but root is essential.

Um, you can unlock the bootloader and still stick to OTAs.
Being able to root at any time and use custom recovery is reason enough for me.

killrhythm09 said:
Um, you can unlock the bootloader and still stick to OTAs.
Being able to root at any time and use custom recovery is reason enough for me.
Click to expand...
Click to collapse
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.

crazifuzzy said:
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.
Click to expand...
Click to collapse
Talk to Verizon. They're the ones preventing the bootloader from being unlocked.
Sent from my Nexus 7 using Tapatalk

iBolski said:
Talk to Verizon. They're the ones preventing the bootloader from being unlocked.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
This. It's no coincidence that the xt925 can be unlocked through Motorola. Carriers are always the problem here in the US.

crazifuzzy said:
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.
Click to expand...
Click to collapse
Well, in actual reality, the XT926 was never meant to be unlocked. It was only unlockable via an exploit, just like obtaining root for locked devices is an exploit in the security of the OS/device.
So, there never really was a "sunset" for unlocking this device as it wasn't meant to be. Only after the exploit was found did a patch come out to stop that exploit from being utilized on any remaining unlocked phones, current or future.
So, when there is an exploit to unlock a device, your best bet is to take advantage of it immediately.
When I got my RAZR HD, it was as a warranty replacement for my OG RAZR MAXX. When I fired it up, it stated there was an OTA available. I immediately told it no and then went straight to the forums here and on another site to investigate what my options were. When I found out that there was the possibility of my unlocking the bootloader, I immediately went to where the tool was and downloaded it. I then proceeded to read and then ask questions on if my phone couldn't unlock, would it hurt it. SamuriHL helped me out a great deal and that is how I found all his tools and how much help he provides. If it weren't for him, I wouldn't have discovered that I could unlock my bootloader.
Usually, I investigate the phone I'm interested in to see if:
1. Can the bootloader be unlocked (or is it already unlocked)?
2. Is there a known root exploit IF the bootloader cannot be unlocked?
3. What are the ROM options (safestrap, cwm, twrp recovery)?
It's definitely something I normally would look into, but I didn't know that I was going to receive the RAZR HD. Once I discovered the possibility of unlocking the bootloader, I was hoping beyond all hope that it could happen and it did. How I received a replacement phone that wasn't patched to the latest OTA was beyond me, but that is the reason I refused the OTA when I first fired up the phone. I had already read about other "horrors" of people taking an OTA and then finding they couldn't root or do other things with their phones.
Lesson learned is, NEVER take an OTA until you've fully researched what it does and what it might prevent.

Advice on Rooting & a clean ROM for Verizon M8

Hi All,
I've had the M8 from Verizon for over a year. I bought this unlocked from the US but am using it in Europe (Denmark) with another service provider. However, as you know Verizon has its bloatware on it and various restrictions that do not let me use the wifi hotspot, USB tethering, etc. Apart from various nagging issues, the most annoying is that I haven't been able to upgrade the ROM (due to another Verizon restriction). And I'm still stuck with OS - 4.4.2.
The questions I need advice on:
1) I want to have a clean ROM and still have the facility to update my OS OTA every time google releases an upgrade.
2) I understand this requires root on my device. If so, what is the best root method for this device? There were a lot of methods around and I'm honestly confused.
I have attemted to root my last HTC One X and succeded after a while. But then when I tried tranferring the phone's data via the built in transfer data app..the phone froze and bricked itself in a way. As I had this device with me by then, I did not spend time to recover the One X, yet. Therefore, my apprehension to get a ROM that I will not need to worry about too much and it would be clean and let my phone function efficiently and without any nags.
Any and all advice will be appreciated!
Thank you.

rubendayal said:
Hi All,
I've had the M8 from Verizon for over a year. I bought this unlocked from the US but am using it in Europe (Denmark) with another service provider. However, as you know Verizon has its bloatware on it and various restrictions that do not let me use the wifi hotspot, USB tethering, etc. Apart from various nagging issues, the most annoying is that I haven't been able to upgrade the ROM (due to another Verizon restriction). And I'm still stuck with OS - 4.4.2.
The questions I need advice on:
1) I want to have a clean ROM and still have the facility to update my OS OTA every time google releases an upgrade.
2) I understand this requires root on my device. If so, what is the best root method for this device? There were a lot of methods around and I'm honestly confused.
I have attemted to root my last HTC One X and succeded after a while. But then when I tried tranferring the phone's data via the built in transfer data app..the phone froze and bricked itself in a way. As I had this device with me by then, I did not spend time to recover the One X, yet. Therefore, my apprehension to get a ROM that I will not need to worry about too much and it would be clean and let my phone function efficiently and without any nags.
Any and all advice will be appreciated!
Thank you.
Click to expand...
Click to collapse
are you S-OFF? check in bootloader. turn off device. hold volume down and power to enter bootloader and it will say S-ON or S-OFF.
If you are not S-OFF you the only way to get root is using Sunshine - http://theroot.ninja/ - it costs a very fair $25.
After that you can flash custom recovery and then flash ROMs that have tethering unlocked in the ROM.
you can also without root or anything and being S-ON flash the latest Verizon RUU and get your phone up to date instead of being on KK, we now have MM. - http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

andybones said:
are you S-OFF? check in bootloader. turn off device. hold volume down and power to enter bootloader and it will say S-ON or S-OFF.
If you are not S-OFF you the only way to get root is using Sunshine - http://theroot.ninja/ - it costs a very fair $25.
After that you can flash custom recovery and then flash ROMs that have tethering unlocked in the ROM.
you can also without root or anything and being S-ON flash the latest Verizon RUU and get your phone up to date instead of being on KK, we now have MM. - http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
Hi andybones,
Thank you. Sorry for the delay.
The bootloader says S-On.
Do you suggest flashing a stock ROM? What about the bloatware and the restrictions from Verizon?
Secondly, will it be possible to get the OTA updates if I have a clean ROM? If so, any suggestions on a clean and efficient ROM that would get me the OTAs automatically and not have the hassle to flash new ROMs as quite simply I hate having to add my google and other account details keyed in each time I flash and have a new ROM.
Thank you for your reply.

rubendayal said:
Hi andybones,
Thank you. Sorry for the delay.
The bootloader says S-On.
Do you suggest flashing a stock ROM? What about the bloatware and the restrictions from Verizon?
Secondly, will it be possible to get the OTA updates if I have a clean ROM? If so, any suggestions on a clean and efficient ROM that would get me the OTAs automatically and not have the hassle to flash new ROMs as quite simply I hate having to add my google and other account details keyed in each time I flash and have a new ROM.
Thank you for your reply.
Click to expand...
Click to collapse
If s-on and locked you can't flash anything until you do sunshine
Sent from my HTC6545LVW using Tapatalk

dottat said:
If s-on and locked you can't flash anything until you do sunshine
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Hi Tapatalk,
Thanks.
I still haven't received a clear answer on if after completing the Sunshine, will it be possible to get the OTA updates if I have a clean ROM? If so, any suggestions on a clean and efficient ROM that would get me the OTAs automatically and not have the hassle to flash new ROMs as quite simply I hate having to add my google and other account details keyed in each time I flash and have a new ROM.