Database Users

Gearing up for some Gingerbread cookies...

saw some articles about this but they weren't this specific...
so I have a Nexus One 2.2.1 stock, rooted with rageagainstthecage thing...
will my phone update to 2.3 as-is, or will I have to unroot the rageagainstthecage method first?
from 2.2 to 2.2.1 I had to uninstall Universal Androot (useless anyways) and reinstall some missing APKs that I had deleted (Amazon MP3 and GenieWidget)

Don't quote me on that, but I'm pretty sure that you will not get OTA automatically. However, as soon as it's out, it will be posted here and you can flash it manually. You will loose root though.

thanks, I hope you're right. Losing root is no biggie (hopefully a nice easy root method will come up shortly)

If anything it will be here before you get the OTA anyway.
Atleast that's what happened with Froyo.
Someone will logcat the address then DL it, then it will get mirrored all over XDA

Once it's here on XDA the flashing will begin long before the OTA arrives

question
I had CM6.1 Nightlies on my N1 with Clockwork, now I went back to stock recovery, stock FRG83 and I have my bootloader unlocked.
I'm wondering if the OTA will come automaticaly (probably gonna install the "XDA" version before OTA even starts going around)?
And I'm wondering if anybody knows what is supposed to be the criteria for the OTA to come automaticaly?

I was rooted with 2.2 and got the OTA for 2.2.1.
As far as I know you need a stock rom (rooted or otherwise) with a locked bootloader.
Sent from my Nexus One using XDA App

are you certain about the locked bootloader?

Its kinda pointless to go back to stock and such if you like the CM nightlies, its what I run, because the first phones to receive the OTA will be the "Holiday" Nexus one, based on imei. It will be up on xda with many mirorrs and versions shortly after! If you remener froyo it will be like that. So just look here for the update.zip
Just my two cents
Sent from my Nexus One using XDA App

Yeah I know I was just wondering about the update process, requirements, etc.
I love CM6.1, I'll probably go back to it when I'm fed up with Ginger there was another reason to go back to stock and that's that I still had ere27 stock backup and it was time to update the stock ROM to frg83 and back that up for the future

It doesn't matter if you have an unlocked bootloader or not, nor does it matter if you have rooted. You must have a stock recovery as the ota will use it to install, if it doesn't find it the installation will fail. Previous updates were available here for rooted users before the update went ota

i also was rooted but had a stock bootloader and recovery... got the 2.2.1 OTA. lost root though.
now for my question... i dont care if i lose root for gingerbread but since i rooted.. SU is in my rom and i cant delete it. i just dont want something on my phone that i cant use.
will the gingerbread update bring me to full stock gingerbread? or would SU be still stuck there. just asking since i rooted after i got froyo so im not sure.

If memory serves, with an OTA su will be removed, but Superuser.apk will remain.
Anyways, if you try this app, you should be able to regain root with ease, even if it's only to bin the files you don't want.

Rusty! said:
If memory serves, with an OTA su will be removed, but Superuser.apk will remain.
Anyways, if you try this app, you should be able to regain root with ease, even if it's only to bin the files you don't want.
Click to expand...
Click to collapse
yeah i got root back because of that app! my main grip was superuser.apk was still in the phone without SU access. now im back to rooted i just left it there.
so basically if i get gingerbread and lose root superuser.apk will still be left in the phone? any thoughts? if so ill just delete it then install it back somewhere i could delete it if i lose root again.

I believe so, yes.
Bin it before updating to be 'safe', I guess.

Rusty! said:
I believe so, yes.
Bin it before updating to be 'safe', I guess.
Click to expand...
Click to collapse
is there an easy way to do it... say just delete it via astro file manager? this is the tutorial i used to root in the first place..
http://forum.xda-developers.com/showthread.php?t=736271
.. lost root then i used the "one click root" that first appeared in the market, then lost root again after 2.2.1 then used visionary.
theres a lot more in the phone that was put in there by rooting (like busybox right?)... but i guess superuser.apk is the visible one since it shows on the app drawer so i wanna remove it from the phone and just install it via the market.

ASTRO can't do it as far as I'm aware, but it's easy from ADB shell or a terminal:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
rm /system/bin/su
rm /system/app/Superuser.apk
rm /system/bin/busybox
and it's goodbye root (and busybox since you mentioned it).

Rusty! said:
ASTRO can't do it as far as I'm aware, but it's easy from ADB shell or a terminal:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
rm /system/bin/su
rm /system/app/Superuser.apk
rm /system/bin/busybox
and it's goodbye root (and busybox since you mentioned it).
Click to expand...
Click to collapse
thanks will give it some thought

krabman said:
It doesn't matter if you have an unlocked bootloader or not, nor does it matter if you have rooted. You must have a stock recovery as the ota will use it to install, if it doesn't find it the installation will fail. Previous updates were available here for rooted users before the update went ota
Click to expand...
Click to collapse
I think that the latest Amon RA will flash an update, regardless of signature verification.

GldRush98 said:
I think that the latest Amon RA will flash an update, regardless of signature verification.
Click to expand...
Click to collapse
You're right, same as the latest ClockworkMod recovery...they disable signature check

[HOWTO] Restore to stock for root users and non-root users UPDATED 5/17/2011

Stop, listen. Follow my directions, if you fail to follow directions I will no longer help you. Don't PM me and ask. If you screw up ask in the thread.
Rooted Users (Non - Root Users scroll down below):
MR1 RUU
http://www.multiupload.com/KU7GSF2EY0
PG05IMG_MR1_no_hboot.zip - c64b4367086fff4f51ec3d5d766a0456
Bootloader (FLASH THIS LAST) FLASHING THIS WITHOUT SUCESSFULLY FLASHING THE ABOVE FILE WILL CAUSE A SECURITY WARNING
http://www.multiupload.com/26WG1UZCXR
abda920f3e159fb05c00d8c54a5b8768 - PG05IMG_hboot_1.4.0000.zip
Flash the above PG05IMG_MR1_no_hboot.zip to restore everything to stock + OTA BUT still will have the s-off bootloader.
Rename PG05IMG_MR1_no_hboot.zip as PG05IMG.zip, and flash through hboot (like in the root guide).
To restore the bootloader, rename PG05IMG_hboot_1.4.0000.zip as PG05IMG.zip and flash through the bootloader. DO NOT FLASH THIS unless you are absolutely sure PG05IMG_MR1_no_hboot.zip flashed to your device, without issue.
Now you are done, enjoy. If you screwed up, and got a security warning contact me, don't stress. Then again, don't screw up.
Non root users wanting to return to 1.12.605.6 (Stock, pre OTA) can continue below:
NOT FOR ROOT USERS
Taken from AndroidPolice: [Tutorial] How To "Un-Root" The HTC ThunderBolt And Return It To Stock. Please check the site out.
One of the most popular questions about rooting the ThunderBolt is how to undo the process and return to stock, which renews your eligibility for customer support. Well, here you go:
Instructions:
Please read the whole tutorial first, and pay attention to every detail. Note that your battery needs to be charged to at least 40% at the beginning of the process, and remember to check the MD5 sums of all downloaded files before diving in. As always, neither Android Police nor Team AndIRC are responsible for any damage this may cause to your phone, and, needless to say, returning to stock means you will no longer be able to use root apps like ShootMe and Titanium Backup.
First, download the following files:
Stock firmware (MD5 sum: 7141f5620f6128af77d50587e341f4b0)
exploits.zip (MD5 sum: 3b359efd76aac456ba7fb0d6972de3af)
Next, push exploits.zip and misc.img.
Code:
adb push misc.img /data/local/
adb push busybox /data/local/
adb shell chmod 777 /data/local/busybox
To gain root and flash misc.img:
Code:
adb shell
su
/data/local/busybox md5sum /data/local/misc.img
If the output is anything other than "c88dd947eb3b36eec90503a3525ae0de," stop and start over again.
Now let’s write misc.img:
Code:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
Rename "PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_
release_174685_signed.zip" to "PG05IMG.zip" before placing it on your SD card.
Finally, reboot into bootloader mode by entering the following command. Allow the stock firmware to flash.
Code:
adb reboot bootloader
You’re done – your phone should now be stock, S-ON.

Bookmarking this, just in case. Thanks, Jcase!

Looks like I'll be going back to Froyo for now. I believe the Sense in GB leak is older than the stock on the device.. plus.. camera doesn't work, weather in clock widget doesn't work.. quadrant score is pretty low.. As for now.. I don't see any solid reason to upgrade to GB.. (though I wish I did).. sigh!

http://forum.xda-developers.com/showthread.php?t=1082114
Follow that to return to stock from gingerbread

I am getting No Image or Wrong Image Error In Final Step. I downloaded Stock Firmware Twice but same issue!

Can anyone help me out? I am not able to return to stock. I have BAMF remix 1.6.3 installed and trying to get back to stock as i have to send this device back to Verizon for replacement. I tried everything..file name is correct....md5 sum is correct however in final step when i tried to load the stock FW the boot-loader says wrong image!!
i downloaded stock FW from every possible source but no different!
Please Help!

If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?

spjoneser said:
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
Click to expand...
Click to collapse
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.

jcase said:
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
Click to expand...
Click to collapse
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?

spjoneser said:
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
Click to expand...
Click to collapse
Yes, because some radios seem to cause the files to flash in different orders, doing it like this keeps me from having to make multiple versions.
Sent from my LG Revolution

Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.

Androidfreakz said:
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Click to expand...
Click to collapse
You need to consult the author of the program, because I don't know what it did, I can't support their application.
Sent from my LG Revolution

This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?

AnalyzeFaith said:
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
Click to expand...
Click to collapse
Reverts everything back to stock + OTA

Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?

i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?

Droid_ALM2ND said:
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
Click to expand...
Click to collapse
yes
1234567890

droidrev71 said:
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Click to expand...
Click to collapse
Of course you lost root, this is for restoring to stock. It removes root.

jcase said:
Of course you lost root, this is for restoring to stock. It removes root.
Click to expand...
Click to collapse
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?

droidrev71 said:
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
Click to expand...
Click to collapse
if you are S-off, you can just flash the MR1 upgrade from the root guide, otherwise you have to do a complete re-root.

Lost root on as I updated to 2.3.4 on my Nexus S

After getting assert_failed errors since forever on 2.3.2, I finally downgraded my radio to fix them and without even thinking installed 2.3.4 OTA. The install went fine but I lost my root.
Now, I haven't unlocked my bootloader. To root, I have to unlock the bootloader which will wipe my phone clean. To take a nandroid/full backup of phone I need root. So, kinda stuck in a catch-22 here.
I still have ROM Manager installed and when I used backup feature in it, it created a new backup. However I am not sure if its a full phone backup or just the ROM. Is there anyway to verify?
Also, any solution to gain my root back with all my data? I am fine with unlocking the bootloader as long as my data is safe.
Edit:
This just struck my mind. If I modify the update file and put in su binaries repackage it and reinstall it on my phone, would it work? Can I even reinstall an update?
Edit2:
Can I just create my own update.zip containing su binaries, sign it and install it?

dpacmittal said:
Edit2:
Can I just create my own update.zip containing su binaries, sign it and install it?
Click to expand...
Click to collapse
You can create it, of course, but I doubt you could install it with a locked bootloader, since you are unlikely to have the private key google uses to sign its updates.

How much can I back-up without rooting my phone? I'll backup the SD partition. I just want all my application settings (eg; Angry birds data) with all the applications, messages and contacts. Is it possible to back all these up without root?
I have titanium installed, if its any good?

[Guide] Install ClockworkMod Recovery image after updated to 2.3.4 (GRJ22).
I hope this will able to help you
http://forum.xda-developers.com/showthread.php?p=13800735#post13800735

My bootloader is locked, mate. Your method won't work for me. Thanks, anyways

Rooting without flashing custom recovery

Is it possible at all to root my Nexus 7 (on Android 4.2 JOP40C) without having to flash a custom recovery or something else that would cause me to lose all of my data, and would allow me to continue to receive normal OTA updates? I understand that an OTA update would likely remove my root, that's a non-issue if I can re-root in a similar way.

Skyline969 said:
Is it possible at all to root my Nexus 7 (on Android 4.2 JOP40C) without having to flash a custom recovery or something else that would cause me to lose all of my data, and would allow me to continue to receive normal OTA updates? I understand that an OTA update would likely remove my root, that's a non-issue if I can re-root in a similar way.
Click to expand...
Click to collapse
It's not the rooting part which erases the data., it's unlocking the boot loader which does that. But an unlocked boot loader is necessary to root.
My advice is that you create a backup using one of the toolkits or using TitaniumBackup and then go ahead and begin the rooting process. After that's complete you can just restore the backup.
Sent from my Nexus 7

veeman said:
It's not the rooting part which erases the data., it's unlocking the boot loader which does that. But an unlocked boot loader is necessary to root.
My advice is that you create a backup using one of the toolkits or using TitaniumBackup and then go ahead and begin the rooting process. After that's complete you can just restore the backup.
Sent from my Nexus 7
Click to expand...
Click to collapse
Titanium backup requires root in the first place.
Unlocking boot loader does a factory reset so save any personal pictures etc you have, copy them to your PC using one of the many methods available.
The apps you can just red-download but you will loose the data from them, whether that's a concern depends what data you have in your apps that you can't manage to save or recreate.
Once the bootloader is unlocked then flash a custom recovery, I use twrp. Then you can do a nandroid backup before you flash the files needed for root just in case it screws up.
If an OTA removes root then you can just reflash the root files.

My Backup Pro is a backup program that works without being rooted. It's also dead easy to use and its free.
Sent from my Nexus 7 using xda premium

I was curious about this too.
I don't care about losing data when unlocking the bootloader.
BUT I would like to know if it is possible to root the nexus 7 but not have a custom recovery?
I just want to be able to use apps that require root access but I remember from my old phone that with custom recovery there were a whole lot of things (like doing a factory reset using the settings) that couldn't be relied upon. I would like to avoid this if possible. For the moment I have no interest in custom roms.
But every time I search for this no one can give a clear answer.
So Yes or No? Can I have a rooted nexus 7 but stock recovery?
And if possible do you know how? I'm on a mac so a non-toolkit method would be amazing

Will rooting remove any data from an unlocked bootloader?
I reflashed my device and accidently left it unlocked... well seems like it was lucky maybe, since I want to root now

Unlocking bootloader wipes ALL data.
Flashing custom recovery does not wipe any data.
Rooting, ie flashing root files, does not wipe any data.
You must have an unlocked bootloader to install custom recovery.
You must have an unlocked bootloader to root.
You can have have a custom recovery and root.
You can have a custom recovery and no root.
You can have root and no custom recovery.
NOTE NOTE NOTE
The easiest way to obtain root is by flashing root files via custom recovery.
If you have an unlocked bootloader then you may as well flash a custom recovery and take a full backup of the device via the custom recovery before you root in case you mess something up. There is no reason to not have a custom recovery. It allows you to also perform a 'factory reset' by wiping certain parttitions and makes rooting MUCH easier as you flash the root files via the custom recovery.

If you want to root, you have to unlock the bootloader first (as said before):
> fastboot oem unlock
After that, you can boot a custom recovery (not flash, the normal recovery will be back again after a restart)
> fastboot boot [recovery.img]
And when the recovery has started, you can mount /system and push the necessary files:
> adb push su /system/xbin
> adb push Superuser.apk /system/app
After that, you should set the correct permissions:
> adb shell
(now you are in your device's shell)
> chmod 06755 /system/xbin/su
> chmod 0644 /system/app/Superuser.apk
> exit
And now just reboot:
> adb reboot
Enjoy
Edit:
The custom recovery can be found here: http://clockworkmod.com/rommanager
The su and Superuser.apk files can be found here: http://forum.xda-developers.com/showthread.php?t=1538053 (just extract the two files from the .zip, I dont like those installer scripts )

Interesting thread. I also posted something similar but was ignored, so never got a answer.
So, to anyone with the answer, PLEASE,
Is there ANY way to backup the WHOLE device, apps included, BEFORE any bootloader unlocking + rooting is done ?
I have googled this question for the past week and cannot get a definitive answer, some saying yes with xx-app, some saying it's not possible because the hidden folders are not accessible to a non-rooted device.
I have purchased many apps on google play store, I don't mind downloading most of them again but I am worried if I wipe the device whether I will be allowed to download from the play store, or whether I will get asked to pay for them again - don't want this.
Plus, most of my games are HUGE, GTAIII, NFS Most Wanted, Asphalt 5,6,7, etc.. and these take a very long time to download again via wifi.
So please, a simple yes or no would suffice. If I have to bite the bullet then so beit, but I have quite a lot to lose if I do, so you can see why I need to get a definitive answer and then do some thinking. Would have rooted 2 weeks ago when I bought the Nexus 7 32Gb, but hindsight is a good thing when you know how.

JohnRM said:
Is there ANY way to backup the WHOLE device, apps included, BEFORE any bootloader unlocking + rooting is done ?
Click to expand...
Click to collapse
Yes, there is the adb backup command:
> adb backup –apk –shared –all –f C:\path\to\backup.bak
However, this will not backup your SMS&MMS. But there is the tool SMS Backup & Restore, which can do this job
Edit:
Here is another Thread with a more detailed description:
http://forum.xda-developers.com/showthread.php?t=1420351

kroegerama said:
Yes, there is the adb backup command:
> adb backup –apk –shared –all –f C:\path\to\backup.bak
However, this will not backup your SMS&MMS. But there is the tool SMS Backup & Restore, which can do this job
Edit:
Here is another Thread with a more detailed description:
http://forum.xda-developers.com/showthread.php?t=1420351
Click to expand...
Click to collapse
Many thanks. :good:

JohnRM said:
Many thanks. :good:
Click to expand...
Click to collapse
You can re-download from the playstore again without repaying. Just as you would re-download if you were using a new device and/or additional device.
You can download one app to multiple devices, is have an app installed on multiple devices at the same time, but you only pay once.

kroegerama said:
And when the recovery has started, you can mount /system and push the necessary files:
> adb push su /system/xbin
After that, you should set the correct permissions:
> adb shell
(now you are in your device's shell)
> chmod 06755 /system/xbin/su
Click to expand...
Click to collapse
Thank you so much for the info! this helped me a lot. Except one thing didn't work for me. Did you mean "adb push su /system/bin" and "chmod 6755/system/bin/su"??? I tried what you said and discovered that /xbin is not a directory.
BTW if you can't be bothered doing it manually, CMW recovery has a nice "install from sideload" feature.

DPI Changes with Locked Bootloader?

Hello fellow XDAers,
Here's my dilemma: when I get my 6P I want to keep my bootloader locked for security reasons. However, I also want to change the DPI, preferably in build.prop. The only way to do this is to unlock, edit, and relock. Which is fine until I have to flash a new stock system image. Is it possible to do that with a locked bootloader and modified system? I was thinking I may be able to keep it rooted, flash TWRP from terminal emulator when I need it, then flash the image from recovery.
Sent from my Nexus 6 using Tapatalk

I'm not at all sure about this, but does adb or fastboot allow copy-pasting to the system partition over non-rooted devices? I don't really think so, but just going to guess..
Code:
adb pull /system/build.prop
Modify the file via Notepad++ and save.
Code:
adb push build.prop /system
adb shell
cd system
chmod 644 build.prop
Again, I'm not a hundred percent sure of this method, and I don't have any non-rooted devices laying around to check.. :silly:
If I recall correctly, I saw someone do something like this here on XDA itself.. I forget who posted it and where the post is but lemme know if it worked for you?

GuitarGuy96 said:
I'm not at all sure about this, but does adb or fastboot allow copy-pasting to the system partition over non-rooted devices? I don't really think so, but just going to guess..
Code:
adb pull /system/build.prop
Modify the file via Notepad++ and save.
Code:
adb push build.prop /system
adb shell
cd system
chmod 644 build.prop
Again, I'm not a hundred percent sure of this method, and I don't have any non-rooted devices laying around to check.. :silly:
If I recall correctly, I saw someone do something like this here on XDA itself.. I forget who posted it and where the post is but lemme know if it worked for you?
Click to expand...
Click to collapse
I don't think that'll worked with a locked bootloader. Can anybody confirm?
The real issue is that I wouldn't be able to apply OTAs without unlocking, because system would be modified. I need a way to return to stock (flash with TWRP?), apply the OTA (do I need stock recovery?), and keep TWRP so I can edit build.prop again with adb. That seems like it would work, but the OTA might replace TWRP with stock so I'd be screwed.
Sent from my Nexus 6 using Tapatalk

GuitarGuy96 said:
I'm not at all sure about this, but does adb or fastboot allow copy-pasting to the system partition over non-rooted devices? I don't really think so, but just going to guess..
Code:
adb pull /system/build.prop
Modify the file via Notepad++ and save.
Code:
adb push build.prop /system
adb shell
cd system
chmod 644 build.prop
Again, I'm not a hundred percent sure of this method, and I don't have any non-rooted devices laying around to check.. :silly:
If I recall correctly, I saw someone do something like this here on XDA itself.. I forget who posted it and where the post is but lemme know if it worked for you?
Click to expand...
Click to collapse
how can you push files to a read-only partition? you need to gain RW privileges to the folder, which in this case is ROOT (or ADMIN). the only way to root is to flash the recovery. the only way to flash the recovery is to unlock the bootloader.
you can re-lock the bootloader post root. you can even remove root and the custom recovery after modifying your system files. just remember, any OTA you receive will bomb because key files don't match and you'll have to redo everything you did to secure your phone.
i'm curious as to what exploits are out there that depend on an unlocked bootloader. if you're not flashing ROM data, what's the concern? avoid malicious sites, lock/encrypt your device and find a good tracker. that's about all you can do.
---------- Post added at 11:17 AM ---------- Previous post was at 11:14 AM ----------
one more thing. in general, OTAs don't typically replace your recovery.img (that i recall). it's called recovery so that you can RECOVER. flashing that ROM store seems like it would cause problems should the OTA fail. plus, don't most OTAs need the recovery partition to install anyway?

Cheater912 said:
Hello fellow XDAers,
Here's my dilemma: when I get my 6P I want to keep my bootloader locked for security reasons. However, I also want to change the DPI, preferably in build.prop. The only way to do this is to unlock, edit, and relock. Which is fine until I have to flash a new stock system image. Is it possible to do that with a locked bootloader and modified system? I was thinking I may be able to keep it rooted, flash TWRP from terminal emulator when I need it, then flash the image from recovery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Everything you want to do starts with unlocking the bootloader, you can't write to something without write access, Sorry. I see what you want to do, but it's not possible.

Big Cam said:
Everything you want to do starts with unlocking the bootloader, you can't write to something without write access, Sorry. I see what you want to do, but it's not possible.
Click to expand...
Click to collapse
I'd unlock the bootloader to root the phone, then lock it again. Everything is writable with a locked bootloader as long as it's done on the phone, not through adb/fastboot.
Sent from my Nexus 6 using Tapatalk

Cheater912 said:
I'd unlock the bootloader to root the phone, then lock it again. Everything is writable with a locked bootloader as long as it's done on the phone, not through adb/fastboot.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
this is the correct answer. the countless #s of exploits found to gain root, without unlocking the bootloader supports this. the reason unlocking the bootloader to gain root is the "only method" to do so is because in other cases you're relying on an exploit that gives you a back door to getting elevated privileges within the system. most of these are or do get closed, so exploits are NOT the correct method for gaining root.
so i reiterate - can someone please provide a case study where having an unlocked bootloader provides system privilege to malicious apps, etc., that would cause a security concern from within a device?
as far as i understand, the "only" reason to lock the bootloader is to preserve the system ROM image (for recovery, troubleshooting, experience, etc.). as a user, you become the responsible party for flashing non-OEM-approved images, exposing yourself to the risk. translation - if you download something that requires you to flash a partition from within the phone, you are the one putting yourself at risk.

640k said:
this is the correct answer. the countless #s of exploits found to gain root, without unlocking the bootloader supports this. the reason unlocking the bootloader to gain root is the "only method" to do so is because in other cases you're relying on an exploit that gives you a back door to getting elevated privileges within the system. most of these are or do get closed, so exploits are NOT the correct method for gaining root.
so i reiterate - can someone please provide a case study where having an unlocked bootloader provides system privilege to malicious apps, etc., that would cause a security concern from within a device?
as far as i understand, the "only" reason to lock the bootloader is to preserve the system ROM image (for recovery, troubleshooting, experience, etc.). as a user, you become the responsible party for flashing non-OEM-approved images, exposing yourself to the risk. translation - if you download something that requires you to flash a partition from within the phone, you are the one putting yourself at risk.
Click to expand...
Click to collapse
You can't boot the phone without decrypting the data partition. That stops an exploit in the OS.
Sent from my Nexus 6 using Tapatalk

You can easily do it following these steps:
Enable ABD Debugging,
Using the CMD window in platform tools (same areas you use for flahsing)
adb devices
adb shell
wm density xxx && reboot
The xxx will be your new density and its as easy as that. I use it all of them time this way because its easier when you don't want to root

Pilz said:
You can easily do it following these steps:
Enable ABD Debugging,
Using the CMD window in platform tools (same areas you use for flahsing)
adb devices
adb shell
wm density xxx && reboot
The xxx will be your new density and its as easy as that. I use it all of them time this way because its easier when you don't want to root
Click to expand...
Click to collapse
That always screws with Hangouts pictures, SwiftKey, and random stuff in the Play Store. Does it not for you? What do you set it to?
Sent from my Nexus 6 using Tapatalk

Cheater912 said:
That always screws with Hangouts pictures, SwiftKey, and random stuff in the Play Store. Does it not for you? What do you set it to?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Nope it works fine for me. I set it to 485 usually and don't have any issues
Edit: I forgot to mention that Android Pay won't work with custom dpi settings for some reason. I contacted Google about that issue and they are looking into fixing it.

btw is there a risk now to re-lock your device if you are not 100% stock because you could be stuck in a bootloop ?
I don't have a N6 or N9 but I read a few threads about the "enable OEM unlock" in Developer options that could lead to a lot of troubles if you re-lock your device....

Matrix_19 said:
btw is there a risk now to re-lock your device if you are not 100% stock because you could be stuck in a bootloop ?
I don't have a N6 or N9 but I read a few threads about the "enable OEM unlock" in Developer options that could lead to a lot of troubles if you re-lock your device....
Click to expand...
Click to collapse
That's true. I'd lock it with TWRP installed, then flash stock recovery with flashify once safely booted.
Sent from my Nexus 6 using Tapatalk

Cheater912 said:
That's true. I'd lock it with TWRP installed, then flash stock recovery with flashify once safely booted.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Cna you flash a recovery from a locked BL in TWRP? Call me old fashioned but i didn't think that's was possible

All this playing around with locking and unlocking the bootloader is going to cause someone to wipe some data.
You wipe the phone when you unlock the BL. This is why it is suggested to just go ahead and do it.
There is no real security risk unless you flash something malicious. Don't flash stuff from unknown sources.. DUH!
Unless you have root, you cannot write to anything but data partitions and even then security keeps you boxed in.
There will be no exploit to gain root with a locked BL Who is going to spend the time when root access is a couple of adb command and two file flashes away?
Anyway that's just MHO.

Pilz said:
Cna you flash a recovery from a locked BL in TWRP? Call me old fashioned but i didn't think that's was possible
Click to expand...
Click to collapse
Yes, you can do whatever you want with a locked bootloader as long as it's done on the phone (not through adb/fastboot).
Sent from my Nexus 6 using Tapatalk