Is there a way to unroot Build JSS15J without unlocking the device first? All I want is root for some apps not a fulyl unlocked device yet, unless is there a way to unlock without wiping the device?
Sorry if this is a common question im just used to motorola phones where you root first then unlock (if there ever is one for the phone)
I am not exactly sure how they implemented the lock on Nexus.
On HTC when the unit was in S-ON lock, it would prevent you from booting or writing unsigned (custom) recoveries. Even if you had a root exploit to get root in the kernel, when you tried to write files to /system it would only be done in memory, and wouldn't survive a reboot.
I only verified that Nexus 7 lock won't allow writing or booting unsigned recoveries (and kernels). Not having a root exploit for 4.3 I couldn't tell you if you'd be able to write a root exploit that worked without unlocking. If locking is done the way HTC does it, then no. If you can still write to /system persistently even with locking, then you could theoretically root w/o unlocking, if you could find an exploit.
When you unlock through fastboot, the process will force a factory reset. This is to protect against somebody unlocking your tablet to access your user files.
I don't know if it is technically necessary for an unencrypted device, but it is enforced by Google's unlocking process. I also don't know if it is enforced by the bootloader or the fastboot program. If latter, you might be able to kill the process after the unlock is done but before the wipe gets sent, however you risk problems if the timing isn't correct, which will probably be difficult to do give how fast everything occurs.
So IMO the first thing you should do is unlock so you can just bite the bullet and do the factory reset when you have nothing installed. It doesn't change anything other than set a flag the you are unlocked and the factory reset. You can run stock like that forever if you wish.
When you are ready, you can boot custom recovery and install your root. You don't even need to flash custom recovery onto the tablet. You can just run it one time from memory.
Main thing is I only want root for a few random apps that allow more functionally with it. I'm never gonna use kernels roms or recoveries I've done it before and it's fun and all but to unstable and unreliable I need the tablet for school and already had my stuff on it before finding out its not like my phone. I have to unlock and wipe then root. On my DROID RAZR hd it's root and unlock no wipe required.
As I mentioned, the unlock is being enforced when you type the fastboot oem unlock command.
I would just bite the bullet and do the unlock as the first thing you do.
Related
So, I have been searching a bit on how to root the Nexus 7 2013. The process I have found seems pretty simple, even for me, as someone who never worked with a Nexus device before.
Unlock bootloader, flash recovery and flash the root.
But the first step, unlock bootloader, has a problem: it wipes all the user data (including SD Card data!!). As the tablet isn't mine (but I was asked to root it), I can't simply just clear all of its data and do the whole process. Thinking of that, I googled a bit on how to root without unlocking bootloader, but I have found nothing (all recent Sony phones, with a few tricks and the right tool, can do that) regarding the 2013 model.
I'm not sure if there is actually no way to do that or my search skills suddenly got horribe... So, the thing is: Is there a way to do that? Root without having to unlock bootloader (and, thus, wiping all data)? Or I have to unlock it?
EDIT: I found this Toolkit, but did a search and nothing regarding that in the 22 pages of the thread...
http://forum.xda-developers.com/showthread.php?t=2389107
Another few questions that I'm lost: I still haven't quite understood why I have to flash the stock ROM back after I do the whole process... So, why?
And, also, what do I lose unlocking bootloader? I mean, the tablet isn't mine (it's from my younger brother), so the easiest, the best, so keeping OTA updates for example are essential. Do I lose it? What else?
It sounds, for me, some silly questions, but I'm still confused... Seems like doing that kind of stuff is easier with my Sony phone. I don't know if it is due me being used to it, but Nexus is sounding to be WAY more hard than everyone keeps saying it is...
Thanks in advance...
Tell them what is going to happen if they want root. Backup as much of their data as you can, then unlock it. You should be able to get most data backed up one way or another.
At the moment you cannot unlock without wiping because the bootloader enforces that. There might be a way to get around that in the future, but not right now.
When you root, use SuperSU v1.55
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
Versions prior to that had an issue with preventing OTAs from completing.
1.60 may have some other issues with changes to OTA survival mode.
Not sure where you read you had to flash the stock rom, but it isn't necessary.
You don't really "lose" anything by unlocking it. Someone might bypass your lockscreen to get at your data, but there is a big inconvenience factor leaving it locked (because eventually you'll want it unlocked, at which point it become more painful to backup/restore your data), so you'll have to decide if it is worth the tradeoff.
The issues with stuff not working after unlocking don't have to do with the unlock itself. They have to do with folks rooting and then using their root power to install changes, which then start breaking things.
If you just install SuperSU 1.55 and don't install themes, APM mods, etc. etc. then everything should still work (except apps which specifically won't work, for security reasons, if they detect root)
@sfhub
Thanks for the answers. As I said, I have some Android knowledge, but still got confused with a new "kind" of device. Once again, thanks
I have an old HTC Incred running 2.3.4 and on it is an application (KakaoTalk for those who are familiar) that I would like to pull app data (messages) from. For those that don't know, once you activate this app on another phone any previously used phones will be locked out and have no access to the messages or export option on the old phone. Messages are saved on the phone not on a server, so I need access to my phone's data without wiping the memory in the process.
Is there any way to gain access to my Incred's data without clearing app data (messages)? I've seen it is possible on other phones, but I haven't seen something specific for the Incred.
I think so. If you follow the first part of the 'downgrade and s-off via htcdev' guide, you should be able to get root access without wiping data if I recall correctly. The basic steps would be:
1. Upgrade HBOOT to 1.02 or greater if it isn't that already.
2. Unlock the bootloader through the htcdev website.
3. Flash a custom recovery such as ClockwordMod or TWRP via fastboot.
4. Flash a superuser .zip from recovery.
At this point you have a rooted phone and should be able to get what you need.
musical_chairs said:
I think so. If you follow the first part of the 'downgrade and s-off via htcdev' guide, you should be able to get root access without wiping data if I recall correctly. The basic steps would be:
1. Upgrade HBOOT to 1.02 or greater if it isn't that already.
2. Unlock the bootloader through the htcdev website.
3. Flash a custom recovery such as ClockwordMod or TWRP via fastboot.
4. Flash a superuser .zip from recovery.
At this point you have a rooted phone and should be able to get what you need.
Click to expand...
Click to collapse
Thanks for the reply! I poked around on the htcdev website, however when I started the process I was warned that data would be erased. Since I've never unlocked through htcdev; is this always the case?
Yea pretty sure when you unlock the bootloader it does erase the phone.
Yep, that's my understanding too: when the bootloader is unlocked the phone is erased. However I have seen some threads on how to gain root without touching the bootloader. While these threads are for some newerish phones, I was wondering if there was a way to do it with the Incred.
Other than warranty issues, and possibly redeeming your Google Drive space, are there any practical ramifications to simply leaving the bootloader unlocked (or, conversely, locked?) on an S-off device? I'm inclined to leave it bootloader unlocked unless I have a warranty issue, as it seems the safest way to make sure I'm never locked out, but I'm curious to know if there are any reasons to lock it from a security perspective.
I say that because right now when I lose root due to an OTA, I just boot (but not install) philz touch recovery to re-root, which I am assuming is allowed because I am s-off. (because otherwise root would be trivial). It seems that as long as I can do that, the bootloader lock/unlock state is somewhat pointless.
You are allowed to flash custom ROMs because you have installed a custom recovery, which was allowed because you unlocked your bootloader. I would leave the bootloader unlocked until a relock is required (if it even comes to that). As far as I know, that poses no threat as long as you know what you're flashing on your device. Anyone with more experience with this may correct me, as I am quite new to the HTC world.
MrKhozam said:
You are allowed to flash custom ROMs because you have installed a custom recovery, which was allowed because you unlocked your bootloader. I would leave the bootloader unlocked until a relock is required (if it even comes to that). As far as I know, that poses no threat as long as you know what you're flashing on your device. Anyone with more experience with this may correct me, as I am quite new to the HTC world.
Click to expand...
Click to collapse
I actually only had TWRP installed briefly to "restore" the Dev Edition nandroid (and by briefly, I mean I booted it once). As soon as the Dev Edition ROM was up, I reverted to the stock DE recovery. Since then, I just "boot" Philz CWM to re-root (since TWRP fails when booted on 4.4.3 for some reason.)
I want to try some custom ROMs on my M8. Before I do this I want to do a full back up. From everything I've read Titanium is by a long shot the most popular so I see no reason not to go that route. However, from what I've read rooting the M8 will wipe my phone, but I can't use Titanium until I'm rooted. So it seems I'm stuck, and wondering what the best way is to proceed.
Thanks,
Ryan
Ryan_Mc said:
I want to try some custom ROMs on my M8. Before I do this I want to do a full back up. From everything I've read Titanium is by a long shot the most popular so I see no reason not to go that route. However, from what I've read rooting the M8 will wipe my phone, but I can't use Titanium until I'm rooted. So it seems I'm stuck, and wondering what the best way is to proceed.
Thanks,
Ryan
Click to expand...
Click to collapse
Rooting by itself won't reset your phone, using the HTC unlock token to unlock the bootloader will. However, if you can S-off, you can also unlock your bootloader without tripping the factory reset. Once your bootloader is unlocked, you can install a custom recovery and backup your (unrooted) OS image - then use that recovery to install su.
Unfortunately, the prerequisite to all of that is getting S-off. If you can't, or won't, do that, then yeah - as soon as you unlock the bootloader your /data partition will get nuked. It's a safety measure to prevent someone from stealing your phone, unlocking the bootloader, and bypassing the OS protections to get the data on it. Fortunately, it only happens when you unlock. If you subsequently leave the bootloader unlocked, it won't happen again.
I've successfully flashed my first ROM. My purpose in doing so was to get the monthly Android security updates, and more broadly have my phone as secure as practical. In that vein, can I safely relock the bootloader? Should I? I am aware that many (most?) people here choose to keep the bootloader unlocked, and I respect that choice, but I'm seeking maximum security.
Searching here at XDA I see conflicting guidance. Some folks say that re-locking the bootloader with a custom ROM installed is begging to be bricked, while others say they have re-locked with no trouble. So what is your advice, why is that your opinion, and do you speak from experience?
I have not rooted the phone, nor do I plan to. I'm running AICP 8.1 on Nextbit Robin and don't plan to make any changes other than receive OTA updates. Should I make future changes beyond that I would not be bothered by the very minor inconvenience of having to unlock then relock it.
I too want to simply flash the stock recovery and lock my bootloader, but from what I've read to update the ROMs we need an unlocked bootloader. So that needs to be unlocked again does that mean everytime I lock-unlock I will be wiping my data all over? Thats would be a pain.
So this is an experiment I want to run from quite long and might do it sometime next month maybe. I will be wiping-unlocking-flashing-locking and see again if I can unlock without wiping my data and lock again, this way I can know for sure if this is doable because most online answers are weirdly confusing.
javelinanddart found that locking the bootloader on the Robin results in similar behavior as on the Nexus devices. The phone will check and make sure that the key used to sign the recovery partition remains the same as it was when your device got relocked, so as a result, TWRP should still work, and updating to a new version of TWRP would work too since it's (presumably) signed with the same key. System partition checking is handled by the kernel itself (dm-verity), but all the custom roms for the Robin have that disabled, so that wouldn't be a problem.
I've also been running custom roms with my bootloader locked and haven't run into any issues with flashing roms with TWRP.
I will be honest though, since TWRP lets you do so much to your phone, relocking your bootloader wouldn't really help security wise. You can pull up a damn root shell right in TWRP, for crying out loud.
@jabashque
Wait so are you saying despite locking the bootloader I can still go in custom recovery? Whats the point then?
I mean for me why I a considering locking the bootloader is so that if I lose my phone no one can access my data. As of now with custom ROM anyone has free access to my data via TWRP/custom recovery.
/root said:
@jabashque
Wait so are you saying despite locking the bootloader I can still go in custom recovery? Whats the point then?
I mean for me why I a considering locking the bootloader is so that if I lose my phone no one can access my data. As of now with custom ROM anyone has free access to my data via TWRP/custom recovery.
Click to expand...
Click to collapse
I suppose you could flash Lineage recovery instead, which was designed to be an OEM-grade recovery and doesn't include the ability to pull up a root shell or use adb.
Grab that here: http://downloads.codefi.re/jdcteam/javelinanddart/ether/ether-lineage-recovery-20180310_170949.img
Personally, I locked my bootloader so that I could actually see my custom splash screen without having to press the power button to dismiss the warning message.
EDIT: the build of Lineage recovery I linked still has adb shell access enabled it seems; I was wrong on that. Also, I haven't tried flashing another rom's system partition that's been signed with different keys.
jabashque said:
I suppose you could flash Lineage recovery instead, which was designed to be an OEM-grade recovery and doesn't include the ability to pull up a root shell or use adb.
Grab that here: http://downloads.codefi.re/jdcteam/javelinanddart/ether/ether-lineage-recovery-20180310_170949.img
Personally, I locked my bootloader so that I could actually see my custom splash screen without having to press the power button to dismiss the warning message.
Click to expand...
Click to collapse
So for an OTA update do I have to wipe all data to unlock again? I am on Omni btw.
I only unlock my bootloader to flash a cool splash screen then relock it. Even if the bootloader is locked I can still flash custom ROMs using ADB sideload. Works like a charm every time. I'm running the AEX custom ROM with Android 8.1.0
akeemk said:
I only unlock my bootloader to flash a cool splash screen then relock it. Even if the bootloader is locked I can still flash custom ROMs using ADB sideload. Works like a charm every time. I'm running the AEX custom ROM with Android 8.1.0
Click to expand...
Click to collapse
But you still locking it while on TWRP isn't it? Which means anyone has access to shell via TWRP defeats the purpose of security provided by a locked bootloader, isn't it?
/root said:
But you still locking it while on TWRP isn't it? Which means anyone has access to shell via TWRP defeats the purpose of security provided by a locked bootloader, isn't it?
Click to expand...
Click to collapse
I guess that's why Nextbit never had a problem with us unlocking the phone's bootloader.