R-W Permissions? - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

Hiya,
Just rooted my Turbo, but I seem to not have RW permissions on the system file. Is this normal? Is there a work around or fix?
Thanks,
NJ

As long as the bootloader remains locked its read only.

Ahhh. OK. Thanks. I am presuming that the bootloader has not been successfully unlocked yet?

nijohnson said:
Ahhh. OK. Thanks. I am presuming that the bootloader has not been successfully unlocked yet?
Click to expand...
Click to collapse
Correct.

Related

[Q] Possible to re-lock bootloader?

Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
bootloopz said:
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
Click to expand...
Click to collapse
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
I know this is an older post but I've been unable to find the instructions for re-locking the bootloader. Any help would be appreciated.
I had the electrify m, the RAZR m for us cellular, and I unlocked it through Motorola. I was giving it to someone else and wanted to relock it and never found any instructions to do so. I contacted Motorola and they said once it was unlocked the was no way to relock. I would guess it's the same with the moto x.
Sent from my XT1055 using Tapatalk
fastboot oem lock doesn't work?
It does. Fastboot OEM lock. Just go back to signed software before, m Kay ? Else you won't boot
Sent from my XT1058 using xda app-developers app
I tried it with my electrify m and it wouldn't work.
Sent from my XT1055 using Tapatalk
https://plus.google.com/110773150384694258853/posts/XUF8UP9iVfi
Here's how from p3droid
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
Has anyone tried re-locking a non-dev Moto X? If so, does it get rid of the "bootloader unlocked, warranty void" message that you get every time u boot ur phone?
mschumacher69 said:
Has anyone tried re-locking a non-dev Moto X? If so, does it get rid of the "bootloader unlocked, warranty void" message that you get every time u boot ur phone?
Click to expand...
Click to collapse
Makes no difference, even when you flash the sbf firmware the logo warning still pops up, so you're best just flashing a new logo.bin file . you'll find them in the themes section, fastboot flash logo (name).bin and your done. If you need to rsdlite at any time in the future, just remove the line flash logo bin from the XML file
Sent on my Moto X
flashallthetime said:
Makes no difference, even when you flash the sbf firmware the logo warning still pops up, so you're best just flashing a new logo.bin file . you'll find them in the themes section, fastboot flash logo (name).bin and your done. If you need to rsdlite at any time in the future, just remove the line flash logo bin from the XML file
Click to expand...
Click to collapse
Even if u re-lock the bootloader?
bootloopz said:
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
Click to expand...
Click to collapse
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
planktoid said:
It does. Fastboot OEM lock. Just go back to signed software before, m Kay ? Else you won't boot
Click to expand...
Click to collapse
Has anyone tried re-locking the bootloader of their Moto X??
mschumacher69 said:
Has anyone tried re-locking the bootloader of their Moto X??
Click to expand...
Click to collapse
Does not work for me. I get:
No valid PIV block in SP for system
chaoslimits said:
Does not work for me. I get:
No valid PIV block in SP for system
Click to expand...
Click to collapse
Did u try re-locking on your model/carrier stock rom, a stock rom from another model/carrier or a custom rom?
Thanks
mschumacher69 said:
Did u try re-locking on your model/carrier stock rom, a stock rom from another model/carrier or a custom rom?
Thanks
Click to expand...
Click to collapse
Went back to stock 4.4 via RSD Lite then tried to relock.
chaoslimits said:
Went back to stock 4.4 via RSD Lite then tried to relock.
Click to expand...
Click to collapse
Which model/carrier do u have?
mschumacher69 said:
Which model/carrier do u have?
Click to expand...
Click to collapse
Vzw Dev Edition
chaoslimits said:
Vzw Dev Edition
Click to expand...
Click to collapse
Have u tried this?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
mschumacher69 said:
Have u tried this?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
Yes. That (minus userdata removal) is what RSD Lite does. I tried with fastboot and mfastboot as well.
chaoslimits said:
Yes. That (minus userdata removal) is what RSD Lite does. I tried with fastboot and mfastboot as well.
Click to expand...
Click to collapse
Weird. So is ur phone bricked now or it just did not lock?

Invalid info????

Does anybody know whats wrong here??
DruoGaby said:
Does anybody know whats wrong here??
Click to expand...
Click to collapse
what did you do to your device to end up here?
neudof said:
what did you do to your device to end up here?
Click to expand...
Click to collapse
its in bootloader mode...just wanna know why the info is invalid
DruoGaby said:
Does anybody know whats wrong here??
Click to expand...
Click to collapse
Interesting, do you have service at the moment? Just by coincidence, a friend of mines sent me a screenshot with this exact issue just this morning. He said the device had to be exchanged since he wasn't getting any service.
themuffinman said:
Interesting, do you have service at the moment? Just by coincidence, a friend of mines sent me a screenshot with this exact issue just this morning. He said the device had to be exchanged since he wasn't getting any service.
Click to expand...
Click to collapse
everything works fine...nothing is wrong with it once i power up...
DruoGaby said:
everything works fine...nothing is wrong with it once i power up...
Click to expand...
Click to collapse
All my friend did was root and s-off but didn't flash or mod anything else. What all have you done to your device?
I've got the same thing. I'm htc-dev unlocked and running Captain_throwback's stock rooted rom. But when I go into the bootloader I get the same invalid info.
Can't run firewater s-off against it either, just says it isn't supported on my device.
When booted, mine works fine, data / voice / everythings perfect, but just shows the invalid info in the bootloader.
ffttgghh said:
I've got the same thing. I'm htc-dev unlocked and running Captain_throwback's stock rooted rom. But when I go into the bootloader I get the same invalid info.
Can't run firewater s-off against it either, just says it isn't supported on my device.
When booted, mine works fine, data / voice / everythings perfect, but just shows the invalid info in the bootloader.
Click to expand...
Click to collapse
guess we gotta wait...i do see in other bootloaders the date is feb..mines is april

deleted

disregard
doitinthedirt said:
Anyone done this? http://www.unlockriver.com/
disregard.. i see it says no verizon.....
Click to expand...
Click to collapse
You do realize that is for sim-unlock, right? Has absolutely nothing to do with bootloader.
Verizon X's are already sim-unlocked....

Re locking boot loader.

Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.
H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.
-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.
Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.
Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.

Can I install an update without having the bootloader unlocked?

So I am the prime v6. 5 rom. I have twrp, I'm rooted and I have xposed. Would installing the 6.6 update brick the phone? I just don't have the bootloader unlocked. Any help is appreciated!
I thought you had to have an unlocked bootloader in order to install TWRP and root. Are you sure your bootloader is locked?
ytsejam1138 said:
I thought you had to have an unlocked bootloader in order to install TWRP and root. Are you sure your bootloader is locked?
Click to expand...
Click to collapse
Is there a way to check this?
Remix245 said:
Is there a way to check this?
Click to expand...
Click to collapse
I got twrp and root without unlocking the bootloader.
I ended up doing that later by running rootjunky's script. It will wipe your data. So you would know if your bootloader was unlocked. If you look on his thread, he has a way for you to check.
Of course this all assumes you aren't on 6.6.
jacewt said:
I got twrp and root without unlocking the bootloader.
I ended up doing that later. Of course this all assumes you aren't on 6.6.
Click to expand...
Click to collapse
Coltondrg has an update for 6.6 to side load. Has anyone side loaded it.?
Remix245 said:
Is there a way to check this?
Click to expand...
Click to collapse
adb reboot bootloader
fastboot getvar all

Categories

Resources