Develop Bugs

[PATCH] Install Superuser, Busybox and Rooted Kernel (For Use After Obtaining S-OFF)

The first thing anyone is going to want to do once AlphaRev's S-OFF process is complete will be to get your device properly rooted within Android. I have created a simple update zip which will take care of the following for you:
Re-install the stock kernel, using a rooted ramdisk (credit jcase).
Install the Superuser app and su binary in /system/xbin.
Install and setup Busybox in /system/xbin.
Simply install this patch via CWM and reboot. From there you can proceed to run any root apps you need (such as Titanium).

rmk40 said:
The first thing anyone is going to want to do once AlphaRev's S-OFF process is complete will be to get your device properly rooted within Android. I have created a simple update zip which will take care of the following for you:
Re-install the stock kernel, using a rooted ramdisk (credit jcase).
Install the Superuser app and su binary in /system/xbin.
Install and setup Busybox in /system/xbin.
Simply install this patch via CWM and reboot. From there you can proceed to run any root apps you need (such as Titanium).
Click to expand...
Click to collapse
This the same file on Rootwiki? Or is it the same minus the kernel?
http://rootzwiki.com/showthread.php?587-ROOT-Gaining-root-after-s-off

rmk40 said:
The first thing anyone is going to want to do once AlphaRev's S-OFF process is complete will be to get your device properly rooted within Android. I have created a simple update zip which will take care of the following for you:
Re-install the stock kernel, using a rooted ramdisk (credit jcase).
Install the Superuser app and su binary in /system/xbin.
Install and setup Busybox in /system/xbin.
Simply install this patch via CWM and reboot. From there you can proceed to run any root apps you need (such as Titanium).
Click to expand...
Click to collapse
THANK YOU SO MUCH YOUR THE BEST lol

That's the method I used. Worked a treat when I found it at rootzwiki last night. Many thanks!
Sent from my ADR6350 using XDA App

Is busy box already on cm7?
Sent from my Incredible 2 using XDA Premium App

Superuser keeps force closing when I use ROM Manager or Wireless Tether.

knipp21 said:
Is busy box already on cm7?
Sent from my Incredible 2 using XDA Premium App
Click to expand...
Click to collapse
I think so. I was told not to install this patch after cm7.

MotorcycleMike said:
Superuser keeps force closing when I use ROM Manager or Wireless Tether.
Click to expand...
Click to collapse
Try going into the application menu and clear the data for superuser. Fixed my fc problems on my phone.
Sent from my ADR6350 using XDA Premium App

The attached zip goes on the root of the sd card correct? then boot into CWM and install zip?

dobosininja said:
Try going into the application menu and clear the data for superuser. Fixed my fc problems on my phone.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
Fixed mine as well. Thanks!

bluedegeon said:
The attached zip goes on the root of the sd card correct? then boot into CWM and install zip?
Click to expand...
Click to collapse
that is correct

ltredbeard said:
that is correct
Click to expand...
Click to collapse
Thanks!

Sorry maybe this is a stupid question.. How can we use CWM to flash this .zip if CWM won't work without a root first???

demersk89 said:
Sorry maybe this is a stupid question.. How can we use CWM to flash this .zip if CWM won't work without a root first???
Click to expand...
Click to collapse
AlphaRevX patches CWM for your recovery during the S-OFF process. And even if it fails you can follow a guide posted on this forum on how to fastboot it.

I flashed this .zip through CWM and Titanium backup won't work. It's telling me that it is unable to find root. I clicked the "Problems?" button and still nothing happened. I remember with the Eris it would run the busybox after you pushed that button. I might just try to install busybox manually as described on Titanium's wiki.
Any other thoughts before I do that?

I flashed this file on my stock but rooted/soff incredible 2, and i seem to have lost root privileges. Luckyily I made a backup before I flashed this so now I'm back to my original problem, of not being able to fix permissions via rom manger because it doesn't see root.

Hey, I have S-Off and patched CWM, but when I hold down the volume button and try to power on, it goes straight to the HTC screen. What am I doing wrong? Does fastboot need to be turned off?

Sithben24 said:
Hey, I have S-Off and patched CWM, but when I hold down the volume button and try to power on, it goes straight to the HTC screen. What am I doing wrong?
Click to expand...
Click to collapse
Turn off fast boot in settings>applications. Turn off. Keep down held while powering on.
Sent from my ADR6350 using Tapatalk

Sithben24 said:
Hey, I have S-Off and patched CWM, but when I hold down the volume button and try to power on, it goes straight to the HTC screen. What am I doing wrong?
Click to expand...
Click to collapse
Menu/settings/power/uncheck fastboot

Perfect. Thanks guys!

Superboot - Rooting Galaxy Nexus

Found this over on MoDaCo forums -- they have obtained temporary root on the Galaxy Nexus: 03 Nov r1: Superboot - rooting the Galaxy Nexus - Android @ MoDaCo
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Click to expand...
Click to collapse

Great news, but shouldn't we let the author post it if he wants to release it here?

FISKER_Q said:
Great news, but shouldn't we let the author post it if he wants to release it here?
Click to expand...
Click to collapse
I guess you are right -- probably should have put it in General Discussion and let author of this make his own thread for support.
I'll let the mods decide what they want to do with this.

FISKER_Q said:
Great news, but shouldn't we let the author post it if he wants to release it here?
Click to expand...
Click to collapse
The OP did link to the site instead of posting the download. I use XDA primarily and would have never found that link had someone not posted it. I don't see why the dev would be disgruntled.
Sent from my HTC ThunderBolt using Tapatalk

joshw0000 said:
The OP did link to the site instead of posting the download. I use XDA primarily and would have never found that link had someone not posted it. I don't see why the dev would be disgruntled.
Sent from my HTC ThunderBolt using Tapatalk
Click to expand...
Click to collapse
Oh yeah, i don't think he'll mind at all.
More for purposes of keeping the forums a bit cleaner for when he does post here

I don't see why this is a big deal, nexus devices have the ability to have the bootloader unlocked out of the box.
Simply 'oem unlock' download su and busybox from the market, job done.
Sent from my LG-P990 using Tapatalk

spences10 said:
I don't see why this is a big deal, nexus devices have the ability to have the bootloader unlocked out of the box.
Simply 'oem unlock' download su and busybox from the market, job done.
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
I've never had a Nexus device before -- didn't know it was that easy.
You can download SU and busybox right from the market, install them and you have root access after a 'fastboot oem unlock'?

Stigy said:
I've never had a Nexus device before -- didn't know it was that easy.
You can download SU and busybox right from the market, install them and you have root access after a 'fastboot oem unlock'?
Click to expand...
Click to collapse
I may be wrong but while it is easy(Being that google considers these devices as developer platforms), it's not that easy.
Even with the bootloader unlocked, you won't be able to write to the relevant directories (as those require root permissions), and as such you still need root unlocked before you can install those from the market.

FISKER_Q said:
I may be wrong but while it is easy(Being that google considers these devices as developer platforms), it's not that easy.
Even with the bootloader unlocked, you won't be able to write to the relevant directories (as those require root permissions), and as such you still need root unlocked before you can install those from the market.
Click to expand...
Click to collapse
Right its almost that simple though. The typical procedure is:
Fastboot OEM unlock
Fastboot flash recovery clockwork.img
Boot into recovery, flash superuser zip
Sent from my Nexus S using XDA App

FISKER_Q said:
I may be wrong but while it is easy(Being that google considers these devices as developer platforms), it's not that easy.
Even with the bootloader unlocked, you won't be able to write to the relevant directories (as those require root permissions), and as such you still need root unlocked before you can install those from the market.
Click to expand...
Click to collapse
Well technically you need the su binary installed before Superuser app is useful. You don't need root before you can install Superuser lol

_hyperdude said:
Well technically you need the su binary installed before Superuser app is useful. You don't need root before you can install Superuser lol
Click to expand...
Click to collapse
Yes, of course, i meant the actual installation of the su binary

FISKER_Q said:
I may be wrong but while it is easy(Being that google considers these devices as developer platforms), it's not that easy.
Even with the bootloader unlocked, you won't be able to write to the relevant directories (as those require root permissions), and as such you still need root unlocked before you can install those from the market.
Click to expand...
Click to collapse
Ah, think you may have a point there so actually what POB has done is enable root without CWMR [as you would need to flash the super user binary from recovery] which is quite handy thinking about it because it may be a while before someone manages to compile a compatible recovery
So I stand corrected, it is quite a big deal

spences10 said:
Ah, think you may have a point there so actually what POB has done is enable root without CWMR [as you would need to flash the super user binary from recovery] which is quite handy thinking about it because it may be a while before someone manages to compile a compatible recovery
So I stand corrected, it is quite a big deal
Click to expand...
Click to collapse
Yup. And the new SuperUser has the option to fully download and install the SU binary. So temp-root means super fast real root.

Why is flashing a boot image preferable to flashing a recovery image?

matt2053 said:
Why is flashing a boot image preferable to flashing a recovery image?
Click to expand...
Click to collapse
I don't think it's flashing a boot image, I think it's just booting off that image which then modifies the system partition to include the su binary and the relevant changes. Then you restart and boot your regular boot image, but this time you've got the su binary.

Understood, thanks.

FISKER_Q said:
I may be wrong but while it is easy(Being that google considers these devices as developer platforms), it's not that easy.
Even with the bootloader unlocked, you won't be able to write to the relevant directories (as those require root permissions), and as such you still need root unlocked before you can install those from the market.
Click to expand...
Click to collapse
Yea, root access is only relevant when the phone is booted up. When in recovery, to write to any partition, root access is not needed and doesn't matter.
Sent from my SCH-I500 using Tapatalk

Hmm...it seems superboot is using a modified boot image from a dump of the GSM Galaxy Nexus. I guess this won't work with the LTE Galaxy Nexus?

Chirality said:
Hmm...it seems superboot is using a modified boot image from a dump of the GSM Galaxy Nexus. I guess this won't work with the LTE Galaxy Nexus?
Click to expand...
Click to collapse
Hmm.....well, even if it won't, root won't be a problem. I guarantee koush will have a recovery for the VZW nexus on day 1.
Sent from my SCH-I500 using Tapatalk

So this means its not rootable like the nexus s? (ie fastboot oem unlock)?

[Q] Is it possible to get root on primoc without flashing a kernel?

I know it's required to unlock the bootloader in order to gain root on primoc, but the directions call for flashing a kernel, and I'd like to keep my phone as close to stock as humanly possible. Is there a way to keep the stock kernel and get root, or is it the act of flashing the kernel that gets you root? The reason I ask is that I'd like to be able to use root apps, but I don't want to flash kernels/ROMs.
Sorry if this is a n00b question.
-------------------------
For any poor unsuspecting soul who finds this thread through the almighty Google... The procedure in the next post works. Apparently, if you get the latest and greatest TWRP recovery it will root for you, but the version of TWRP I found did not do that.

meaninglessvanity said:
I know it's required to unlock the bootloader in order to gain root on primoc, but the directions call for flashing a kernel, and I'd like to keep my phone as close to stock as humanly possible. Is there a way to keep the stock kernel and get root, or is it the act of flashing the kernel that gets you root? The reason I ask is that I'd like to be able to use root apps, but I don't want to flash kernels/ROMs.
Sorry if this is a n00b question.
Click to expand...
Click to collapse
Follow the instructions and flash the recovery file and not a kernel. You should now have TWRP recovery installed. Download Superuser.zip from the official website and place it in your sd card. Reboot and go into Bootloader and then into Recovery. From there press the first button and go to where you left the Superuser.zip. Select it and let it finish. Now reboot and you should be rooted.
Sent from my One V using xda premium

woohoo!
reV17 said:
Follow the instructions and flash the recovery file and not a kernel. You should now have TWRP recovery installed. Download Superuser.zip from the official website and place it in your sd card. Reboot and go into Bootloader and then into Recovery. From there press the first button and go to where you left the Superuser.zip. Select it and let it finish. Now reboot and you should be rooted.
Sent from my One V using xda premium
Click to expand...
Click to collapse
I'm so going to try that. Thanks a million!

meaninglessvanity said:
I know it's required to unlock the bootloader in order to gain root on primoc, but the directions call for flashing a kernel, and I'd like to keep my phone as close to stock as humanly possible. Is there a way to keep the stock kernel and get root, or is it the act of flashing the kernel that gets you root? The reason I ask is that I'd like to be able to use root apps, but I don't want to flash kernels/ROMs.
Sorry if this is a n00b question.
Click to expand...
Click to collapse
If you install twrp as the recovery it will promot you and root the Rom. With the stick kernel.
Sent from my HTC One V using xda app-developers app

robaho said:
If you install twrp as the recovery it will promot you and root the Rom. With the stick kernel.
Click to expand...
Click to collapse
That wasn't my experience. I had to flash the superuser.zip from recovery to get the su binary and then install the superuser app to get root to work. The general approach does work though!

meaninglessvanity said:
That wasn't my experience. I had to flash the superuser.zip from recovery to get the su binary and then install the superuser app to get root to work. The general approach does work though!
Click to expand...
Click to collapse
I am talking the later versions. Check the twrp change log.
Sent from my HTC One V using xda app-developers app

I just used the superboot for primoc that I found on one of the stickied threads in general. one click and it roots it. I've used it on all three of the virgin updates.
Sent from my One V using xda premium

demi_fiend said:
I just used the superboot for primoc that I found on one of the stickied threads in general. one click and it roots it. I've used it on all three of the virgin updates.
Click to expand...
Click to collapse
Superboot does work, but it installs a kernel as part of the directions, which is what I did not want to do.

meaninglessvanity said:
Superboot does work, but it installs a kernel as part of the directions, which is what I did not want to do.
Click to expand...
Click to collapse
Just use twrp...
Sent from my HTC One V using xda app-developers app

[HOW-TO] Guide to Debloated, S-OFF'd, Rooted HTC One with Wireless Tether Support

I'm writing this short little post to give an idea of a good starting point for the HTC One as it stands right now. There are a lot of threads and they get out-of-date quickly (just as this one will). I just picked-up my new HTC One on Tuesday of last week from a Verizon store. This just gives a fresh idea of what can be done to get started on it.
Obviously you're running these instructions at your own risk. I'm not responsible for you bricking or otherwise damaging your phone. Doing these things may (will) void your warranty and may prevent you from being able to return your phone. Run these things at your own risk.
AN IMPORTANT PUBLIC SERVICE MESSAGE: When you get your phone out-of-the-box, it's probably going to offer you an OTA update. I recommend that you do not accept an OTAs as this usually makes this process even harder than it has to be. Verizon hates having us enjoy our devices!
First, let me describe my goals here:
Unlock the bootloader and obtain S-OFF
Install a custom recovery (CWM)
Install a "cleaned-up" stock ROM (debloated but still a stock experience)
Get wireless tether working without jumping through tons of hoops.
I'll go through the list and just describe what I did:
Unlock the bootloader and obtain S-OFF
This was fairly straightforward. Rumrunner has an excellent package that does this very easily. I checked my phone's ROM version and saw that I was running 1.10.605.15. I grabbed the Rumrunner package from here for that level.
In looking over the requirements for Rumrunner, it wanted 32-bit Linux and I run 64-bit. The easiest way to solve this problem for me was to just boot to a Xubuntu 12.10 32-bit ISO that I had on my system. If you have it burned, just boot to it. If you don't (like me), use grub2 (if you have it) and boot the ISO directly. Either way, get yourself into a live environment.
Once the ISO was booted, I got it on the network and installed adb and fastboot from the Ubuntu repositories (after I did apt-get update, of course). Connect the phone via USB and enable USB debugging:
Go to Settings -> About -> Software Information -> More
Tap the Build number field 7 times
Back up to the Settings screen again and you'll now see Developer options
Enable USB Debugging under the developer options
Verify that you can see the device on your system using adb (this should result in a device being listed by serial number):
Code:
sudo adb devices
Follow these instructions for executing Rumrunner. It worked perfectly as described. Once complete, the phone was unlocked and S-OFF with a stock ROM.
Keep the live environment up as it will just make life easier to do the next steps.
Install a custom recovery (CWM)
I pretty much always use CWM if I can. I saw that there were no issues with doing that on this phone (like there are on other phones like the Rezound). I grabbed version 6.0.4.7 of CWM (non-touch) for the HTC One from here. If I recall correctly, the device is booted back into the stock ROM at this point. Make sure your device is still connected USB and has USB debugging enabled.
Reboot into the bootloader from the command prompt:
Code:
sudo adb reboot bootloader
Once the phone comes up, it should be at the Fastboot screen (it should actually show Fastboot USB). Verify that you can see your phone with fastboot (should get your device serial number again):
Code:
sudo fastboot devices
Now you can flash CWM recovery using this command from the directory where you stored the CWM file you downloaded (such as the one I provided a link to):
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.7-m7vzw.img
After the flash is successful, reboot back into the bootloader:
Code:
sudo fastboot reboot-bootloader
Now you can choose BOOTLOADER and then RECOVERY to get access to CWM. If you really want to, you can take a backup of the stock ROM at this point. I did not because I thought it was a waste of space. I just booted back into the stock ROM and disabled USB debugging so I could stick a real ROM on the system.
Install a "cleaned-up" stock ROM (debloated but still a stock experience)
I really wanted to give this HTC Sense 5.0 a run. I've used Sense before and it wasn't awful. This seemed less annoying than previous versions (plus, there are some nice camera features which are important to me). For that reason, I selected the stock 2.10.605.1 rooted, deodexed, debloated ROM from this thread. I also opted to do the firmware upgrade at the same time, so I grabbed the firmware for the 2.10.605.1 as well.
The instructions in this thread are easy to follow so just use those. Just a note though: Flash the firmware and ROM at the same time if you're going to do firmware at all. Instructions are in the second post on that thread.
Once the ROM was up, I did my typical setup of accounts and such. The last thing I needed was Wireless Tether support.
Get wireless tether working without jumping through tons of hoops.
I don't particularly care how I get wireless tethering (infrastructure mode) as long as it works on my phone reliably. I first tried the stock tethering as this sometimes works because the authors of "stock" ROMs sneak hacks into their ROMs. It did not work. I then tried messing around with the WiFi Tether TrevE Mod that I saw recommend a few times but this didn't pan out on the 2.10.605.1 ROM (I temporarily went to 1.10.605.15 and it worked; I went back to 2.10.605.1 when someone recommended the solution below):
http://forum.xda-developers.com/showthread.php?t=2576548
I flashed this package onto my system and, without a problem, built-in wireless tether started working. I've seen no problems.

Getting my one today. I guess I will give this a go tonight. Thanks. Anything else to look for? Thanks.
Sent from my HTC Rezound.

Rumrunner worked perfectly fine for me on Ubuntu 12.1 64 bit both times I ran it. I would try it first before downloading s 32 bit distro if 64 bit is already installed.
Sent from my HTC6500LVW using Tapatalk

I have 2.10.605.1 on this phone out of the box and dont see a Rumrunner for it. Does that mean I am just going to have to sit tight and wait?

onthehole said:
I have 2.10.605.1 on this phone out of the box and dont see a Rumrunner for it. Does that mean I am just going to have to sit tight and wait?
Click to expand...
Click to collapse
It is firewater now. Go to firewater-soff.com
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
It is firewater now. Go to firewater-soff.com
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Thanks.

No problem.
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
No problem.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
may not have time to do this today. Can I just keep pushing the ota off? I delayed it already but will it prompt me before trying to install?

onthehole said:
may not have time to do this today. Can I just keep pushing the ota off? I delayed it already but will it prompt me before trying to install?
Click to expand...
Click to collapse
Yeah just keep delaying it. If you take it you're screwed. 4.4.2 can't be unlocked and rooted at the moment.
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
Yeah just keep delaying it. If you take it you're screwed. 4.4.2 can't be unlocked and rooted at the moment.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
thanks. Looks like firewater uses some sort of temp root method? I will look into it. Firewater does s-off and root, correct?
And unlocks bootloader?

onthehole said:
thanks. Looks like firewater uses some sort of temp root method? I will look into it. Firewater does s-off and root, correct?
And unlocks bootloader?
Click to expand...
Click to collapse
It does unlock and s off. You will have to get a recovery and flash super user in recovery but that isn't until after you're unlocked and s off.
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
It does unlock and s off. You will have to get a recovery and flash super user in recovery but that isn't until after you're unlocked and s off.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So just flash TWRP or Clockwork, then go back in and flash super user. Thank you.
edit: I realized I am in the wrong forum asking these questions.

onthehole said:
So just flash TWRP or Clockwork, then go back in and flash super user. Thank you.
edit: I realized I am in the wrong forum asking these questions.
Click to expand...
Click to collapse
Yeah. Make sure you use cwm version 6.0.4.6 not .7 or twrp 2.6.3.4.
Sent from my HTC6500LVW using Tapatalk

disconnecktie said:
Yeah. Make sure you use cwm version 6.0.4.6 not .7 or twrp 2.6.3.4.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
will do. thanks.

onthehole said:
will do. thanks.
Click to expand...
Click to collapse
Hello:
I just gained S-OFF on stock 4.3 out of the box.
If I want to go to Stock/Rooted I am guessing I should take the OTA, then Clockwork or TWRP and SSU? Thanks.

onthehole said:
Hello:
I just gained S-OFF on stock 4.3 out of the box.
If I want to go to Stock/Rooted I am guessing I should take the OTA, then Clockwork or TWRP and SSU? Thanks.
Click to expand...
Click to collapse
Do not take the ota. Just flash the firmware in Santod's stock ROM thread and then flash the stock ROM from the ota.
Sent from my One using Tapatalk

disconnecktie said:
Do not take the ota. Just flash the firmware in Santod's stock ROM thread and then flash the stock ROM from the ota.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I was already S-Off and actually good to go. Took the OTA, flashed SuperSU after Clockwork and I am banging. Root/Soff, nailed it. Thank you for your help.

onthehole said:
I was already S-Off and actually good to go. Took the OTA, flashed SuperSU after Clockwork and I am banging. Root/Soff, nailed it. Thank you for your help.
Click to expand...
Click to collapse
The only reason I don't suggest taking ota is because sometimes the results can be less than desired.
Sent from my One using Tapatalk

disconnecktie said:
The only reason I don't suggest taking ota is because sometimes the results can be less than desired.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
understood. I will flash fresh if things aren't up to par.

[fxz] 4.4.2 183.46.15

WARNING: You REALLY need to UNDERSTAND and read EVERYTHING or you MAY brick your phone!
IF YOU HAVE NOT UNLOCKED, THIS BUILD WILL PERMANENTLY PREVENT YOU FROM DOING SO. STOP NOW and GO UNLOCK!
Purpose of this thread:
To get you, the locked or unlocked RAZR M xt907 owner, from any version to 4.4.2 (KDA20.62-15.1).
Things you will need:
FXZ KDA20.62-15.1 thanks @stras1234 as always!
Instructions:
Use the RSD Flasher with KEEP DATA to flash this on your phone with RSD.
OR
Use the House of Moto with KEEP DATA to flash this to your phone with fastboot.
OR
Use RSD Lite to flash it, but, you will lose data unless you modify the XML file manually.
This will get you a clean OTA install. You will lose root.

Thanks! I was hoping this would leak soon.

Is it worth it... I have to go through a lot to use a PC... Anyone on the update notice any pro's to this update
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
Is it worth it... I have to go through a lot to use a PC... Anyone on the update notice any pro's to this update
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
No. I dont think its worth it. My phone actually feels laggy now, it shudders during transitions and scrolling. Very annoying. YMMV.

hi, i'm now using factory rom 183.46.10
my xt907 is locked, can i flash/update this rom?
thanks,

You can but I'd personally unlock first.
Sent from my SM-P600 using Tapatalk

UuN said:
hi, i'm now using factory rom 183.46.10
my xt907 is locked, can i flash/update this rom?
thanks,
Click to expand...
Click to collapse
Quick, unlock the bootloader first because it's now or never!!!
As for updating, FXZ packages are suitable for all phones regardless of lock status, though you will lose your app data AND internal storage content in the process - please make backups.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

You won't lose data if you use my tools to flash it. Nor does the current version of the FXZ have the erase data line. When the official one gets posted to sbf it may have the erase data line in it, but that will literally be the only difference.
Sent from my SM-P600 using Tapatalk

My girl got the update notification for this update. We rooted her device with towelroot. No unlocked bootloader or custom ROM or recovery is installed. My question is should she unroot her device and if so will she be able to reroot with towelroot after the update?? Any help would be welcomed. Thank guys.

x.0ni.x said:
My girl got the update notification for this update. We rooted her device with towelroot. No unlocked bootloader or custom ROM or recovery is installed. My question is should she unroot her device and if so will she be able to reroot with towelroot after the update?? Any help would be welcomed. Thank guys.
Click to expand...
Click to collapse
All of your questions are answered here > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
All of your questions are answered here > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Awesome thank you!! Now my next question is...her phone already downloaded the update but she hasn't implemented it yet. Can it be removed and prevented from updating PERIOD? She doesn't want to update it becuz She'll lose her root and she doesn't want to unlock her bootloader becuz she is still under warranty.

x.0ni.x said:
Awesome thank you!! Now my next question is...her phone already downloaded the update but she hasn't implemented it yet. Can it be removed and prevented from updating PERIOD? She doesn't want to update it becuz She'll lose her root and she doesn't want to unlock her bootloader becuz she is still under warranty.
Click to expand...
Click to collapse
Using a root explorer, delete or rename
Code:
3c_ota.apk
Location
Code:
/ system / priv-app / 3c_ota.apk
Also delete the update in the /cache directory

ATTACK said:
Using a root explorer, delete or rename
Code:
3c_ota.apk
Location
Code:
/ system / priv-app / 3c_ota.apk
Also delete the update in the /cache directory
Click to expand...
Click to collapse
Thank you sir! Can the update file be deleted as well? And where is the location of the update file? Then my questions are done. Thanks for your help and patience brother.:highfive:

x.0ni.x said:
Thank you sir! Can the update file be deleted as well? And where is the location of the update file? Then my questions are done. Thanks for your help and patience brother.:highfive:
Click to expand...
Click to collapse
Yes, delete the update in the /cache directory

ATTACK said:
Yes, delete the update in the /cache directory
Click to expand...
Click to collapse
Brother it worked without fail. Thank you so much. My girl said respect to ATTACK and thanks from us both.:highfive:

x.0ni.x said:
Brother it worked without fail. Thank you so much. My girl said respect to ATTACK and thanks from us both.:highfive:
Click to expand...
Click to collapse
:good:

AndyYan said:
Quick, unlock the bootloader first because it's now or never!!!
As for updating, FXZ packages are suitable for all phones regardless of lock status, though you will lose your app data AND internal storage content in the process - please make backups.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
Hi Andy & Sam,
my bootloader just unlocked with motopocalypse,
and flash it using rsdlite with fxz new build (183.64.15),
this rom kinda speedy than before so far..
but i let you know later..
fyi, it is safe flashing this rom, my userdata still remain..
edit: i've lost root after update, and towel root is'nt working.. is there any other rooting tools?..
thx guys.. ?

Unlocked users do not use root exploits. They install custom recovery, flash supersu zip, and call it a day.

UuN said:
edit: i've lost root after update, and towel root is'nt working.. is there any other rooting tools?..
thx guys.. ?
Click to expand...
Click to collapse
Grab a KK-BL-compatible custom recovery from dhacker29's site and flash that. Then grab SuperSU flashable zip from chainfire.eu. You might wanna refer to the guide in General section for details. Follow part 3 for custom recovery and then part 1b for root.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

thx guys,
can you please guide me, this is what i want to perform this step as follow:
-----------------------------------------
1b. ROOT - Unlocked Bootloaders
-----------------------------------------
MUST HAVE CUSTOM RECOVERY
Download a Superuser flashable zip [SuperSU] [CWM Superuser]
Place on external SDcard
Enter Recovery
Flash Superuser.zip
Reboot
PROFIT
Click to expand...
Click to collapse
then,
-----------------------------------------
3. CUSTOM RECOVERY
-----------------------------------------
Custom recoveries built and provided by dhacker29 & nobe1976
Download your choice of custom recovery, then proceed to installation.
[TWRP - XDA] [TWRP - DROIDRZR] [CWM - XDA]
Click to expand...
Click to collapse
please tell me step by step in sequence, coz this ny first time replacing stock recovery, which one do you prefer? TWRP or CWM?
---------- Post added at 10:40 AM ---------- Previous post was at 09:59 AM ----------
SamuriHL said:
Unlocked users do not use root exploits. They install custom recovery, flash supersu zip, and call it a day.
Click to expand...
Click to collapse
AndyYan said:
Grab a KK-BL-compatible custom recovery from dhacker29's site and flash that. Then grab SuperSU flashable zip from chainfire.eu. You might wanna refer to the guide in General section for details. Follow part 3 for custom recovery and then part 1b for root.
Click to expand...
Click to collapse
guys, i just grab this 3 custom rec, from Attack's file link and supersu.zip from chainfire..
please guide me, thx..?