Hi!
I have a Nexus 7, unlocked and with custom rom (Omni). The process I did was the standard:
-Unlock the bootloader (so I can change the recovery)
-Flash TWRP
-Flash room
So, I was wondering if it is possible to lock it again without breaking everything. It is just curiosity: Since when you are unlocking it, you are forces to format all internal data, it seems that locking it (while preserving TWRP, root and custom ROM) would slightly increase the security. Would that work? Or I would get a dead Nexus 7?
Thanks!
dayr said:
Hi!
I have a Nexus 7, unlocked and with custom rom (Omni). The process I did was the standard:
-Unlock the bootloader (so I can change the recovery)
-Flash TWRP
-Flash room
So, I was wondering if it is possible to lock it again without breaking everything. It is just curiosity: Since when you are unlocking it, you are forces to format all internal data, it seems that locking it (while preserving TWRP, root and custom ROM) would slightly increase the security. Would that work? Or I would get a dead Nexus 7?
Thanks!
Click to expand...
Click to collapse
If you lock it using fastboot oem lock, it won't break it, but if you wanted to flash something (kernel, su, xposed, a new rom, etc) again, you would have to fastboot oem unlock (and wipe everything again which will wipe all your work), what you'd probably prefer, is use something like bootunlocker which can lock and unlock the bootloader from within the OS.
I just leave my device unlocked, much more convenient that way. I've had no issues with it being unlocked.
mdamaged said:
If you lock it using fastboot oem lock, it won't break it, but if you wanted to flash something (kernel, su, xposed, a new rom, etc) again, you would have to fastboot oem unlock (and wipe everything again which will wipe all your work), what you'd probably prefer, is use something like bootunlocker which can lock and unlock the bootloader from within the OS.
I just leave my device unlocked, much more convenient that way. I've had no issues with it being unlocked.
Click to expand...
Click to collapse
There are a number of solutions.
The risk is that somehow when you were flashing something, the battery died, so you can't unroot now (for sending back to Asus. And I have a bad usb charging port right now, so i am having a lot of problems).
BootUnlocker works but I don't know if CWM works with BootUnlocker locking the
What I do know is that I rooted my nexus with Towelroot, which does not unlock the bootloader (The unlock sign does not appear.). I had succssfully installed TWRP, Xposed, Su, Game Killer, etc... and had later discovered BootUnlocker.
Thanks for your answers.
Not that I was planing to do it, but it is always good to know!!
Related
Hi all....
2 quick questions....
My Nexus LTE is rooted
when I try to boot into recovery......either with ROM Manager or fastboot...I get the Android with the red triangle.....is it because I have my bootloader locked???
Even though I unlocked it to root...I locked it just in case I have to bring it back to Verizon...
also......If I do have to unlock it to get to recovery.........after I unlock it...would I lose all my data and apps?
1. If you've not unlocked it yet then unlocking it will delete everything
2. You need to unlock it and then flash ClockworkMod to be able to flash a new ROM
I'm about to do this also.
Unlock, root.
I think what the OP is asking is once you unlock and root... can you relock the bootloader without messing up root?
Also when you unlock and it wipes your phone, does it erase everything I've copied over to the internal SD card? I have like 10gb's of music, files, pics, etc.
I think the answer to the above is YES. But just want to make sure. That would really suck as I normally wipe my phone often when crackflashing. Sometimes I'll flash a rom but find out mid-day that it sucks and it'll require a wipe and reload an older version.
Anyway, rooting seems easy enough. Push some files. I'm just curious about how the internal SD card plays its role in all this... as I've always had an SD Card.
hogowner said:
Hi all....
2 quick questions....
My Nexus LTE is rooted
when I try to boot into recovery......either with ROM Manager or fastboot...I get the Android with the red triangle.....is it because I have my bootloader locked???
Even though I unlocked it to root...I locked it just in case I have to bring it back to Verizon...
also......If I do have to unlock it to get to recovery.........after I unlock it...would I lose all my data and apps?
Click to expand...
Click to collapse
I am no expert - but I am pretty sure you are correct.
1. You re-locked your bootloader. So - no custom recovery.
2. Unlocking your bootloader is going to wipe everything. Including your "sd card partition" (whatever you want to call it). So if you have pictures or other important files you need - transfer them before you unlock your bootloader.
3. I would just leave it unlocked. If you need to lock it for warranty issues it is very easy to re-lock. Right? Isn't it something like...
Code:
reboot into bootloader
enter the fastboot command
fastboot oem lock
done
hope that helps. maybe someone will chime in.
So unlocking the bootloader will Kill your sd card files. What about normal wipes from CWM?
I rooted...(no custom rom...leaving it stock)...then relocked my bootloader.....
I then installed all the apps I wanted........
I also was able to get into CWR and make a backup...
now if I try to go into CWR I get the android with the red triangle
why? Is it because I locked the bootloaded? Is that why I get the red trianlge? because bootloader is locked? I can't even get into stock recovery and if it is...if I unlock the bootloader...It will wipe data..and I dont feel like doing that right now.....unless there is another way to get the red triangle fixed
EDIT::::::::::::::::::::: I went to my Rom Manger app...and I reinstalled CWR...and lo and behold.....I was able to boot into Recovery with no problem.....even with my bootloader locked.......
I understand that bootloaders are a set of codes that run on the boot of a device. It is specific to the hardware in the phone. I also understand that in order to flash custom ROMs,an unlocked bootloader is neccesary.
Now for my questions. I've already unlocked my bootloader, installed TWRP, S-Off'd, and installed the custom ROM I'm more than happy with (ViperOne). I'm considering relocking my bootloader to (maybe) redeem my Google Drive storage. Questions:
If I relock, can I:
1. Stay rooted
2. Keep S-Off (for Xposed, etc)
3. Keep TWRP
4. Redeem Google Drive storage
Thanks for the answers!
That's yes times 4.
Since you're S-Off, you should able to issue fastboot commands to lock and unlock, all without losing any data.
I'm sure that's what I did with my M7.
Keep a nandroid backup off your phone storage just in case.
I had a Nexus 5X with stock Android 6 software. Android Pay was working fine.
I was having a few lag issues and noticed the final Nexus factory image was available for Android 7 so I decided to unlock my bootloader and install the factory image. After I installed it, Android Pay was still working fine.
Then I received an OTA update for the monthly security hotfixes which I installed. Since doing this, Android Pay doesn't work. It says something about my phone being rooted/unlocked and that Android Pay does not support this.
Can anyone tell me why this is happening? I don't need to keep my bootloader unlocked so if locking will allow me to resolve the issue without losing data then I can do this. Can anyone guide me please?
Try flashing a kernel from The Flash or Franco.
Both have a line of code that should stop the bootloader error in safetynet
Thank you but I don't want to put on any custom stuff. I just want to go back to a stock Android 7.0 ROM that works with Android Pay. I don't need root, or an unlocked bootloader. How can I go back to stock?
You can use something like wugs nexus tool.
Although some have mentioned you can brick your device trying to lock the bootloader.
Personally I have never done it. Others might have more experience.
It may or may not be easier to lock than to use a custom kernel. YMMV.
One benefit of the kernel is increased performance on your phone.
Oh and if you lock your bootloader it will completely wipe your phone. E.g. You will lose your data.
Edit.. Root isn't needed for a kernel either
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Source: https://developers.google.com/android/nexus/images
Ah okay, thanks for the info. What I should have done originally was re-lock the bootloader straight after I flashed the ROM. Unfortunately, I setup the device after flashing the ROM and kept the bootloader unlocked which is why I'm stuck right now. Okay, time to backup my stuff up and re-lock the bootloader. Thanks everyone.
Hi, I recently unlocked bootloader, than flashed a kernel which gave me root also, and then installed some apps than need root.
Since I unlocked the bootlader, every time I turn on the watch, a waring error appears and booting time has largely increased.
1) If if follow the same procedure to unlock, is it possible in the menu to lock it again?
2) If n.1 is possible... is it safe with a watch rooted and a custom kernel? Or do I brick something?
3) Will root and kernel still work if I lock again the watch?
Thanks
titomax82 said:
Hi, I recently unlocked bootloader, than flashed a kernel which gave me root also, and then installed some apps than need root.
Since I unlocked the bootlader, every time I turn on the watch, a waring error appears and booting time has largely increased.
1) If if follow the same procedure to unlock, is it possible in the menu to lock it again?
2) If n.1 is possible... is it safe with a watch rooted and a custom kernel? Or do I brick something?
3) Will root and kernel still work if I lock again the watch?
Thanks
Click to expand...
Click to collapse
It's completely safe. If the watch runs properly before lock, it will run properly after lock. The only thing that will change is your ability to flash unsigned images using fastboot. Keep in mind though that it will automatically factory reset if you choose to unlock it again.
Lock it using the command fastboot oem lock
If it will reset, this won't realize what I need. Thanks for this useful advise!
Hi,
Long story short:
is it possible to install customROM without root and to (re)lock the bootloader, and are there experiences with a similar situation where Apps check for closed bootloader and root (and stop working if detected)?
=> Goal: activate WiFi-Calling as my provider tuned down 2G-transmitpower due to the 5G-advances (without having enough 3G-coverage to make calls on UMTS-net)... BUT: I'm using two banks; one uses a PhotoTAN-App, that stops working if it detects an open Bootloader, the other Bank-App checks for Root & open Bootloader, and likewise stops working if detected. I have no idea about the PhotoTAN and Magisk, but the 2nd bank confirmed they checked rooted devices with Magisk, and that it does not work with it....
Thus, if I go for a CustomROM, I need to be sure that I can run it unrooted and with a locked bootloader....
Is there a way to install a CustomROM on the 5X with (re)locked bootloader and without root?
(or, if not possible: is there a way I can activate WiFi-Calling on StockROM if said one does not have the Carrier-Entitlements?)
Thanks for the help
@theunlucky: you don't need root to flash a custom ROM, only an unlocked bootloader. IMO you can lock it after flashing ROM.
rp158 said:
@theunlucky: you don't need root to flash a custom ROM, only an unlocked bootloader. IMO you can lock it after flashing ROM.
Click to expand...
Click to collapse
Are you sure about locking the bootloader after flashing a CustomROM? I've read several threads now, and it seems a locked BL only works with StockROM?
Not sure, therefore IMO IMO a locked BL prevents flashing CustomROM, not running. Try. If it doesn't work, you unlock BL again (triggers factory reset). In the worst case you've to flash latest firmware for a clean base..