Related
[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)
UPDATE #2 - Fitchman has reported successful root and rom flash without unlocking the bootloader by using Ginger Break. Full details in this post: http://forum.xda-developers.com/showpost.php?p=13236136&postcount=135
UPDATE - IMPORTANT: This method does not work with Android 2.3.3. Search the forum or this post in this thread for a way to update to 2.3.3 and root without unlocking if you haven't updated yet.
Alternatively, use this method on 2.3.2 and lower, then use titanium to back up everything, store it on your laptop (along with all your sdcard's data), then do the oem unlock step first and then continue from there with the rest of the guide.
Not my original idea, but a consolidation of a discussion between inakipaz and shrivelfig and myself in another thread and being posted here for easier finding by future root-seekers.
Shrivelfig's tested the method to re-root a previously rooted pone with a re-locked bootloader, and inakipaz has done it on a phone that's never had the bootloader unlocked.
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Download these two files:
clockwork recovery v3.0.0.5 or clockwork recovery v3.0.0.5 mirror if above not working
su-2.3.6.1-ef-signed.zip
Koush's blog for the latest clockwork updates (find Nexus S in the list).
Also, if you don't already have the necessary android sdk and drivers on your computer, get them from here: http://developer.android.com/sdk/index.html and install them. Some Windows users report better luck just installing pdanet. There's a decent guide for Windows users on installing the sdk here.
Place the recovery file on your laptop where you can access it while using the sdk fastboot commands.
Place the su zip one in the top level folder of your sdcard.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the excellent instructions that Allgamer gives in this GUIDE, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps below.
To navigate in the clockwork recovery, you use the volume keys to scroll up/down through the menus, and the on/off button to select what's highlighted.
(note: some report success without these first 3 steps, others don't get a succesful root without, I recommend doing them)
select mounts and storage.
select mount /system
select go back
select install ZIP from sdcard
select choose zip from sdcard
select su-version#-signed.zip file you downloaded earlier
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
After the phone reboots, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
This method doesn't install busybox, so go to the Market and download/install busybox directly, or get Titanium Backup and check it's "problems?" button and let it install busybox for you. There's also an app called root checker that supposedly verifies you have a working root on your phone.
Once you have a successful root installed, I'd suggest getting back into clockwork recovery and running a nandroid back up from clockwork's backs and restore menu. Then copy that file from your sdcard (in the /clockwork/backups folder) to your laptop for safe-keeping and an easy full system restore to a known working config.
Usual disclaimers about I'm not responsible for damage to your phone or loss of data apply. Use any rooting method at your own risk.
Thanks and all the real credit go to inakipaz, shrivelfig and allgamer, and of course to koush, and ChainsDD for the superuser apk.
Worked perfectly. I used fastboot from my Mac (outlined in the stickied Mac Root thread). Root checker verifies that I have root.
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
yeah! good work!
Srsly. Awsom.
Someone sticky this....
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
I would think this method also gives you a way to back up before unlocking the bootloader.
1) fastboot boot into Clockwork as described here
2) Full nandroid backup from Clockwork
3) Mount "SD" from Clockwork over USB, copy everything to computer (since it wipes everything)
4) Go back and unlock the bootloader as usual, resulting in a full wipe
5) Flash Clockwork Recovery again through whichever method
6) Mount "SD" from Clockwork over USB, copy the backup back to phone
7) Restore nandroid
And now you've unlocked the bootloader without amnesia =)
ravidavi said:
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
Click to expand...
Click to collapse
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!
Also, the fact that you're able to boot into Clockwork using "fastboot boot" - that also means you can install a ROM .zip file right from there.
cmstlist said:
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
Click to expand...
Click to collapse
"fastboot boot" only launches the recovery no unlock needed. "fastboot flash" flash the recovery
cmstlist said:
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!.
Click to expand...
Click to collapse
It worked! Here's the process I used, starting from a completely unmodded Nexus S.
1: Use the method detailed here to gain root access without unlocking the bootloader.
2: Using a root-enabled file explorer (I used Super Manager), rename install-recovery.sh (in /etc) to install-recovery.sh.old . You'll need to remount as r/w to do this. NOTE: You don't *have* to do this step, but if you don't, then you can only use clockwork once after which it will be erased on reboot.
3: Using ROM Manager, install Clockwork Recovery.
4: Pleasure yourself, because your bootloader is still locked and nothing was erased.
I have yet to try actually flashing a custom ROM. Does this mean that it can also be done without unlocking bootloader?
Well damn, whaddaya know. I just flashed MoDaCo r10 without unlocking the bootloader, and without losing any personal data on /sdcard.
I figure someone at XDA should like this.
Pretty much followed distortedloop's advice. Starting from a fully stock Nexus S with Android 2.3.2 (GRH78C):
* Root using the method on this thread.
* Rename install-recovery.su to install-recovery-old.su. (in /bin)
* Install Clockwork Recovery from ROM Manager.
* Download whatever ROM you want (compatible with Clockwork), rename to update.zip, and copy to sdcard.
* Reboot into Clockwork.
* Wipe cache, reset to factory (IF REQUIRED BY NEW ROM). This was my first install of MoDaCo, and that requires it. This step does NOT erase your personal files on sdcard, just all android-related files.
* Install update.zip from Clockwork.
* Continue self-pleasuring ... you now have a custom rom without touching your bootloader or wiping your personal sdcard data.
Maybe it's just because I'm a noob here, but it seems to me that this is a BIG deal. All root/ROM installation methods that I've seen so far have required an unlocked bootloader. This seems to be the first time a Nexus S has been unlocked and custom-ROM'd without unlocking the bootloader and wiping the entire /sdcard.
Ravi
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
What's really odd is now we have to wonder what's the purpose of the oem unlock erasing your sdcard? Speculation was that it was a security feature to keep people from accessing your data if they stole your phone; they couldn't flash something on the phone to get access, but clearly they can. Fastboot into a custom recovery and you own the phone.
Perhaps this is a security hole Google will try to fix some day?
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
distortedloop said:
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
...
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
Click to expand...
Click to collapse
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
ravidavi said:
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Click to expand...
Click to collapse
I'm thinking that something like Superboot might need to have the bootloader unlocked, since it replaces the boot image, right? But I'm not sure.
ravidavi said:
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
Click to expand...
Click to collapse
There's only a page and a half of posts in the development section right now, so it's not likely to disappear any time soon, but you could ask a mod (theimpaler747 is ours) via PM to sticky it. I thought about asking myself, but seemed a bit tacky to ask for my own thread.
Meanwhile, I'd been linking people to various posts I'd made in other threads suggesting this might work, but once inakipaz and shrivelfig confirmed it, I'm just now pointing people here. I just hope people see this before wiping their phones unnecessarily.
Really, the other guides should just be updated to skip the oem unlock step. That's really the only different thing we're doing here.
i'm just waiting for more people "newbies" to confirm this actually works for them, before making it a sticky
In theory if you really really screw up your phone, you might need fastboot flash in order to recover it. But if fastboot also lets you boot into an img recovery... then you still have a recovery route that doesn't require unlocking.
Sent from my Nexus One using XDA App
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
qreffie said:
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes because you still have the original recovery installed
distortedloop said:
Perhaps this is a security hole Google will try to fix some day?
Click to expand...
Click to collapse
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
shrivelfig said:
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
Click to expand...
Click to collapse
I can confirm that the Nexus One does not allow this "fastboot boot" on a locked bootloader. Maybe this was just an oversight?
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
I can confirm that this method works, without unlocking the BL or erasing the SD part.
This is pretty cool. I wish I new about this before I unlocked the bootloader days after I received my phone. I too wonder if this was intentional or an oversite. Google did want this phone to be for developers, but like other's said, this is also a bit of a security hole. The wiping of the sd card on unlock would protect the person if the phone was stolen, like if there was confidential corporate stuff on there. Even if you password protect your phone, someone could fastboot clockwork, mount the sd card and retrieve all the information that was on there.
cmstlist said:
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
Click to expand...
Click to collapse
It's also been done by Samsung with some versions of the Galaxy S line (some of the "leaked" roms, and even one official kies push (IIRC) changed the bootloader, causing people the ability to use 3 button mode for Odin access, and causing others to lose it.
Hi,
I know this has been requested before for a bunch of other devices and in other forums, but the request was never answered, mainly because other devices had other holes to plug...
basically, my request is to mod the clockwork recovery image in order to protect it with a password. Why, you ask? Simple. The Nexus S has a good protected bootloader (when "oem locked" -- which you can lock while mantaining a custom recovery and/or rooted ROM). When someone steals my rooted phone, the only way to break in is:
- Use the phone normally - PATCHED - I use a pattern lock code;
- Use ADB on the phone via USB access the phone - PATCHED - I disabled usb debugging on the system image;
- Use the bootloader to reflash a new system/recovery image - PATCHED - I "oem locked" the phone so the phone does not accept unsigned images, and also a "fastboot oem unlock" wipes the phone, protecting my private data;
- Boot into recovery - NOT PATCHED - There is no way to password protect a recovery image, as of now.
So, can anyone please attempt this? I'm thinking of trying it myself, but I have very little experience developing for android, and I don't know the source code.
My suggestion is to create a customizable password (maybe a simple 4 to 6 digit PIN code input via the volume keys) on first boot of the recovery image. Then, in subsequent boots, ask for the code before turning on ADB and before giving access to the other recovery options.
If you forget the code, well... you still can reflash a new recovery via the system image. Also you can still fully wipe the phone, so you'll never brick it or anything.
What you guys think? I personally am very sad with this situation. When you root you basically lose all physical security with regards to the data on your phone, I think we can do better.
Sounds like a good idea.
lgrangeia said:
Hi,
"oem locked" -- which you can lock while mantaining a custom recovery and/or rooted ROM
Click to expand...
Click to collapse
How do you do this?
EDIT: This is how ... http://forum.xda-developers.com/showthread.php?t=931865&highlight=oem+lock
I'll second this request. It will save me the pain of doing the following:
To secure my phone between "maintenance" events, I flash back the stock recovery image while I'm not actively performing "maintenance". Do this via adb while the phone is booted with:
flash_image recovery /sdcard/recovery.img
You'll obviously need to put a copy of the stock recovery on your sdcard, along with a copy of clockwork for when you need to do some "maintenance". Note that the flash_image binary isn't present in all ROMs. I know CM7 has it, and in the early days I copied one over from my old Nexus One ROM.
Then turn off USB debugging, OEM lock and password protect your phone.
bubbahump said:
I'll second this request. It will save me the pain of doing the following:
To secure my phone between "maintenance" events, I flash back the stock recovery image while I'm not actively performing "maintenance". Do this via adb while the phone is booted with:
flash_image recovery /sdcard/recovery.img
You'll obviously need to put a copy of the stock recovery on your sdcard, along with a copy of clockwork for when you need to do some "maintenance". Note that the flash_image binary isn't present in all ROMs. I know CM7 has it, and in the early days I copied one over from my old Nexus One ROM.
Then turn off USB debugging, OEM lock and password protect your phone.
Click to expand...
Click to collapse
And you also need one more thing: To be running a rooted ROM. I might want to be running a totally stock rom and use a custom recovery, in order to take advantage of nandroid backup/restore.
If you are running a stock system rom, you cannot reflash recovery from system.
Does anyone know where's the best place to reach the main dev of clockwork mod? is it koush? I might try to tweet him directly to this thread.
I've been thinking about the security of these phones lately as well and it seems there's a lot of holes that a tech-savvy thief could utilize on Android phones... especially one that has custom ROMs.
This suggestion sounds pretty good, but I might be a bit confused. Do you use a terminal emulator on the phone to type in that command to flash between clockwork and stock recovery? Also, if you do a fastboot oem lock when you have a custom ROM, do you have to wipe the whole phone again when you want to fastboot oem unlock to put on another ROM?
bubbahump said:
I'll second this request. It will save me the pain of doing the following:
To secure my phone between "maintenance" events, I flash back the stock recovery image while I'm not actively performing "maintenance". Do this via adb while the phone is booted with:
flash_image recovery /sdcard/recovery.img
You'll obviously need to put a copy of the stock recovery on your sdcard, along with a copy of clockwork for when you need to do some "maintenance". Note that the flash_image binary isn't present in all ROMs. I know CM7 has it, and in the early days I copied one over from my old Nexus One ROM.
Then turn off USB debugging, OEM lock and password protect your phone.
Click to expand...
Click to collapse
dinan said:
This suggestion sounds pretty good, but I might be a bit confused. Do you use a terminal emulator on the phone to type in that command to flash between clockwork and stock recovery? Also, if you do a fastboot oem lock when you have a custom ROM, do you have to wipe the whole phone again when you want to fastboot oem unlock to put on another ROM?
Click to expand...
Click to collapse
Dinan, I'm not 100% sure, but I think the bootloader lock/unlock only prevents you from flashing from the bootloader stage. So you can reflash a custom recovery from the system rom while "oem locked", but you cannot do that from the bootloader.
I thought a bit about this, and pluging this hole in the recovery will make the Nexus S very well protected against physical security attacks (especially since it doesn't even have a SD card slot).
So if I had flashed CM7, then reflashed the stock bootloader and did fastboot oem lock, in order to nandroid or flash a new ROM I would have to first flash clockwork recovery back? If that's the case, would I have to flash it through the terminal from the device or can it be done through adb (or ROM manager)?
lgrangeia said:
Dinan, I'm not 100% sure, but I think the bootloader lock/unlock only prevents you from flashing from the bootloader stage. So you can reflash a custom recovery from the system rom while "oem locked", but you cannot do that from the bootloader.
I thought a bit about this, and pluging this hole in the recovery will make the Nexus S very well protected against physical security attacks (especially since it doesn't even have a SD card slot).
Click to expand...
Click to collapse
dinan said:
So if I had flashed CM7, then reflashed the stock bootloader and did fastboot oem lock, in order to nandroid or flash a new ROM I would have to first flash clockwork recovery back? If that's the case, would I have to flash it through the terminal from the device or can it be done through adb (or ROM manager)?
Click to expand...
Click to collapse
CM7 does not flash your bootloader. Maybe you meant recovery?
you can have an "oem locked" handset and still flash your recovery (or your system) image via both recovery or system, if you have any of those customized/rooted.
What "oem lock" means is that you cannot flash directly from the bootloader (fastboot flash), thats all.
PS: I really have no idea why this was moved to the general forum... this is a development request thread.
In short, what we need is a password protected bootloader which will require password for booting into fastboot or download mode or recovery.
Use Cerberus. Track, remote wipe, take photo, etc. It is embedded into /system and can't be removed with wipe data factory reset. Its all the security you need.
Sent from my Nexus S 4G using xda premium
lgrangeia said:
Hi,
I know this has been requested before for a bunch of other devices and in other forums, but the request was never answered, mainly because other devices had other holes to plug...
basically, my request is to mod the clockwork recovery image in order to protect it with a password. Why, you ask? Simple. The Nexus S has a good protected bootloader (when "oem locked" -- which you can lock while mantaining a custom recovery and/or rooted ROM). When someone steals my rooted phone, the only way to break in is:
- Use the phone normally - PATCHED - I use a pattern lock code;
- Use ADB on the phone via USB access the phone - PATCHED - I disabled usb debugging on the system image;
- Use the bootloader to reflash a new system/recovery image - PATCHED - I "oem locked" the phone so the phone does not accept unsigned images, and also a "fastboot oem unlock" wipes the phone, protecting my private data;
- Boot into recovery - NOT PATCHED - There is no way to password protect a recovery image, as of now.
So, can anyone please attempt this? I'm thinking of trying it myself, but I have very little experience developing for android, and I don't know the source code.
My suggestion is to create a customizable password (maybe a simple 4 to 6 digit PIN code input via the volume keys) on first boot of the recovery image. Then, in subsequent boots, ask for the code before turning on ADB and before giving access to the other recovery options.
If you forget the code, well... you still can reflash a new recovery via the system image. Also you can still fully wipe the phone, so you'll never brick it or anything.
What you guys think? I personally am very sad with this situation. When you root you basically lose all physical security with regards to the data on your phone, I think we can do better.
Click to expand...
Click to collapse
Here's a simple workaround for you, althought less convenient. Once you've made a nandroid backup, move it off your phone. Archive the image with a password and file name encryption on a computer. Extract the image from the archive when you want to restore it, then copy the extracted image to the phone to perform restore.
bubbahump said:
I'll second this request. It will save me the pain of doing the following:
To secure my phone between "maintenance" events, I flash back the stock recovery image while I'm not actively performing "maintenance". Do this via adb while the phone is booted with:
flash_image recovery /sdcard/recovery.img
You'll obviously need to put a copy of the stock recovery on your sdcard, along with a copy of clockwork for when you need to do some "maintenance". Note that the flash_image binary isn't present in all ROMs. I know CM7 has it, and in the early days I copied one over from my old Nexus One ROM.
Then turn off USB debugging, OEM lock and password protect your phone.
Click to expand...
Click to collapse
You can extract flash_image from the ROM Manager app. Unzip the apk file and you'll find it in there. Any rooted ROM can then have this file moved into /system/bin for example.
Rem3Dy said:
Use Cerberus. Track, remote wipe, take photo, etc. It is embedded into /system and can't be removed with wipe data factory reset. Its all the security you need.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
The OP is talking about the security issue, not about the data surviving oem unlock. At the moment, anyone who gets the phone can go into CWM, mount the internal storage, get the image off the phone and extract data from it. The OP is concerned about this security hole.
Rem3Dy said:
Use Cerberus. Track, remote wipe, take photo, etc. It is embedded into /system and can't be removed with wipe data factory reset. Its all the security you need.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Nice. It turns out from little research that both Cerberus and "Theft Aware" have /system support. Call it "root" support if you will.
Now, Theft Aware is far more advanced in this regard in that it also hides the app as a system app with a custom name that you choose. Note that it requires some complexity if you want to uninstall (delete some files manually and stuff).
Theft Aware is also more polished and it seems more effort has been put into the 2.0 version.
Cerberus is more simpler and it feels I can trust them.
mightyiam said:
Nice. It turns out from little research that both Cerberus and "Theft Aware" have /system support. Call it "root" support if you will.
Now, Theft Aware is far more advanced in this regard in that it also hides the app as a system app with a custom name that you choose. Note that it requires some complexity if you want to uninstall (delete some files manually and stuff).
Theft Aware is also more polished and it seems more effort has been put into the 2.0 version.
Cerberus is more simpler and it feels I can trust them.
Click to expand...
Click to collapse
So theft aware is a flashable zip that you flash from recovery?
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
So theft aware is a flashable zip that you flash from recovery?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It has a "setup app" which you install which in turn installs the actual app. If you have writable /system it can install the app there or if you have ram FS then it can install using what you said.
Sent from my Nexus One using XDA App
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
you will need to unlock to flash custom zip, but u can relock after
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
Question - why? What do you want to root your phone for if not to use the wonderful tools of root. Why do you think fully rooting your phone will harm something. Locked or unlocked bootloader is not going to affect your phone. Rooted stock rom with recovery will not make it act funny.... Sorry not putting you out there but just asking why? Feel free to ignore me if you must...
Edit: Sorry to answer your question like the post above said you can root and then lock it right back up if that is your preference
playya said:
Question - why? What do you want to root your phone for if not to use the wonderful tools of root. Why do you think fully rooting your phone will harm something. Locked or unlocked bootloader is not going to affect your phone. Rooted stock rom with recovery will not make it act funny.... Sorry not putting you out there but just asking why? Feel free to ignore me if you must...
Edit: Sorry to answer your question like the post above said you can root and then lock it right back up if that is your preference
Click to expand...
Click to collapse
I have come from an HTC Desire, which I rooted and had a custom rom (Cyganonmod) on and was very happy with it.
I am still not sure of what I would gain by doing the same with my Nexus 4 ?
any advice is much appreciated.
Is this new Cyganonmod installer the best way to go?
gjjh25 said:
I have come from an HTC Desire, which I rooted and had a custom rom (Cyganonmod) on and was very happy with it.
I am still not sure of what I would gain by doing the same with my Nexus 4 ?
any advice is much appreciated.
Is this new Cyganonmod installer the best way to go?
Click to expand...
Click to collapse
This phone is built for rooting and modding. You wont know what benefit you have until you either read up and see if the mods are ones you want or actually flash a rom. Sure try the CM installer but if you dont toolkits or just basic knowledge of android can get this phone roooted in minutes.
the CM rom on your HTC will give you the same benefits on your Nexus 4
playya said:
This phone is built for rooting and modding. You wont know what benefit you have until you either read up and see if the mods are ones you want or actually flash a rom. Sure try the CM installer but if you dont toolkits or just basic knowledge of android can get this phone roooted in minutes.
the CM rom on your HTC will give you the same benefits on your Nexus 4
Click to expand...
Click to collapse
Thanks, what do you recommend for the easiest way to unlock and root then?
gjjh25 said:
Thanks, what do you recommend for the easiest way to unlock and root then?
Click to expand...
Click to collapse
I used a toolkit but honestly you can unlock manually by just booting into bootloader mode. Go into development and try Wugs Toolkit.... Rooting the phone is easy and all methods are relatively the same.
I do not see anything wrong with giving CM a try as well
gjjh25 said:
Is it possible to just root my phone?
if so how do i do it?
All the posts I have seen go into unlocking and then rooting
Click to expand...
Click to collapse
I recommend you to stick to your original plan, its your phone, do what you like, you don't need to flash custom roms if you don't want to. I am using stock kernel and stock KitKat right now and the performance is excellent.
Follow these instructions to unlock bootloader, install latest kitkat factory image, install custom TWRP recovery, and root. http://forum.xda-developers.com/showthread.php?t=2010312
The links to fastboot package and driver required is in my signature.
Link to download factory image: https://developers.google.com/android/nexus/images
Link for latest TWRP: TWRP recovery
Link for latest SuperSU package: SuperSU package
After you do all that, in bootloader menu, you can flash back the stock recovery (recovery.img), which is location in the "image-occam-******.zip" of the factory image. (fastboot flash recovery recovery.img)
Then lock your bootloader by "fastboot oem lock". You can also use BootUnlocker to lock and unlock your bootloader on the fly while in the phone, without losing your data, since everytime you do fastboot oem unlock, it will wipe the entire device.
By using stock rom, stock recovery, stock kernel and temporarily unroot (SuperSU) or hide root (SuperSU paid version), it allows you to receive future OTA updates from Google. If you want to modify your phones more while staying with stock, read up on Xposed Framework and its module Gravity Box, which is not yet compatible with Android 4.4 but will be eventually.
Just remember if you don't have custom recovery, once something goes wrong and your phone can't boot, its very hard to save the data inside. Once you have custom recovery like TWRP, you can make a backup of your stock image (which also backup your stock kernel) and try out other custom roms and easily go back to stock, then you can flash stock recovery again to receive OTA updates.
Thanks for advice everyone.
I rooted and unlocked with Wugfresh over the weekend. A lot easier than I thought it would be
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
Hello friends
My phone is HTC One m8w
There isn't "update" in
Setting
About
Android version,
5.0.1
Software number
1.0.0.m8w
Build number
4.19.1402.15 CL458284 release-keys
Please help me for this problem
How can I update my phone?
Thanks a lot
Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps
Ta3miyyasandwich said:
Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps
Click to expand...
Click to collapse
There isn't any update for my build number
Sent from my HTC_M9pw using Tapatalk
if you are willing to, just root your phone and flash the marshmallow rom on to your phone and use titanium backup to backup everything before you do so.
you can root your phone,flash twrp recovery,flash Marshmallow rom.
lmentor said:
you can root your phone,flash twrp recovery,flash Marshmallow rom.
Click to expand...
Click to collapse
That's exactly what I just said
justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom on to your phone
Click to expand...
Click to collapse
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.
redpoint73 said:
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.
Click to expand...
Click to collapse
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone. Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.
justinchao740 said:
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone .
Click to expand...
Click to collapse
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
justinchao740 said:
Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.
Click to expand...
Click to collapse
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.
redpoint73 said:
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.
Click to expand...
Click to collapse
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access
justinchao740 said:
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access
Click to expand...
Click to collapse
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.
redpoint73 said:
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.
Click to expand...
Click to collapse
Agreed plus my post never stated anything about rooting.
justinchao740 said:
Agreed plus my post never stated anything about rooting.
Click to expand...
Click to collapse
While my intent is not to be the guy that always has the last word; I also can't let you state a complete falsehood.
justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom
Click to expand...
Click to collapse