Related
i have an unlocked bootloader tf700t waiting for spare cable to install twrp
can someone please answer these questions
will i brick my tablet if i update?
do i update through manual or OTA?
should i install twrp first?
will i lose unlock?
if you could tell me then it would be great. the last thing i want is a brick
hasrussian said:
i have an unlocked bootloader tf700t waiting for spare cable to install twrp
can someone please answer these questions
will i brick my tablet if i update?
do i update through manual or OTA?
should i install twrp first?
will i lose unlock?
if you could tell me then it would be great. the last thing i want is a brick
Click to expand...
Click to collapse
If you do everything correctly, you won't brick your tablet.
Since your bootloader is unlocked, you won't get the OTA update, so you'd have to install it manually. AFAIK you need root to manually install an OTA update (by copying the dlkpkgfile to /cache and creating the corresponding command file), so it's easier to install TWRP first.
The bootloader stays unlocked when you do all this.
thanks
_that said:
If you do everything correctly, you won't brick your tablet.
Since your bootloader is unlocked, you won't get the OTA update, so you'd have to install it manually. AFAIK you need root to manually install an OTA update (by copying the dlkpkgfile to /cache and creating the corresponding command file), so it's easier to install TWRP first.
The bootloader stays unlocked when you do all this.
Click to expand...
Click to collapse
cable arrived and i now have twrp installed
thanks anyway
It started when I tried to install a CM11 update. I did not see that was only for KK BL, then I tried to revert to stock rom(using RSD lite) and install the old version for the JB BL again, but my wifi still not working(or working only when it wants lol).
Anyone could help me?
I tried to flash a lot of different roms, even reset with RSD, but the issue stills. I don't know what more I can do
Thx for the att and sorry for my horrible english...
Carcass.br said:
It started when I tried to install a CM11 update. I did not see that was only for KK BL, then I tried to revert to stock rom(using RSD lite) and install the old version for the JB BL again, but my wifi still not working(or working only when it wants lol).
Anyone could help me?
I tried to flash a lot of different roms, even reset with RSD, but the issue stills. I don't know what more I can do
Thx for the att and sorry for my horrible english...
Click to expand...
Click to collapse
im having the same issue... my step dad said there was a patch somewhere but i think its a patch from verizon thats going to be an ota so... we will lose root
derpyherp said:
im having the same issue... my step dad said there was a patch somewhere but i think its a patch from verizon thats going to be an ota so... we will lose root
Click to expand...
Click to collapse
lose root? your bootloader is not unlocked?
ncsuwolfs said:
lose root? your bootloader is not unlocked?
Click to expand...
Click to collapse
I thought you loose root when you take ota's??
derpyherp said:
I thought you loose root when you take ota's??
Click to expand...
Click to collapse
If you are rooted, the OTA will fail, so you have to flash back to stock before taking OTAs.
If you are locked and you take an OTA, you will lose access to whatever exploit was patched. In the case of going from JB to KK, the original root (Saferoot I believe) won't work. However, Towelroot will work for those that have locked bootloaders.
However, if you are rooted and on the latest official KK, then you can unlock your bootloader and then, no matter what OTA comes out after that, you will still be able to root your phone without the use of an exploit like Towelroot. Instead, you take .zip image of the SU app you are using and flash it in TWRP or CWM recovery. No exploit needed.
Towelroot is only for those that don't have an unlocked bootloader and it's an exploit (a security issue) within the specific version of the Android OS. OTAs patch these as they are released, which means another exploit has to be discovered in order to achieve root for locked bootloaders.
So, right now, if you are not unlocked, you better unlock on the initial KK release because the latest soak test does patch Towelroot and the bootloader exploit. You've been warned.
hi, i have a noob question. I'm not a true noob but i never had a "nexus".
Today i unlocked bootloader, installed twrp recovery and rooted my device. Then i flashed only franco kernel to try new screen firmware update.
So i'm stock with cm11s without kernel.
When an update will be released,unchecked CM recovery update, can i update or i have to unlock bootloader again before?
after updated iìll be with bootloader lock or unlock?
Thanks to everyone
The OnePlus One is not a nexus device but it is very close to being one.
No you do not have to relock your bootloader, leave your bootloader unlocked. There is no point in relocking it unless you're doing warranty.
Just untick "Update CM Recovery" in Developer Options if you haven't already. You can flash the new OTA with TWRP.
Hi guys.
I'm also having some questions about the OTA updates and the root/bootloader.
Currently i'm still having the 25R, i unlocked it, rooted it with TWRP, all fine.
I've been using Nexus 4 before, and after lots of Roms i kept using CM for a very long time, so normally i just updated it, and i was still rooted and everything.
But now i keep reading that you will lose root and bootloader if you update the CMs (with OTA?).
So then i have to unlock and root again, so i will need to wipe all data again?
Or is there a simple method to just update and still keep all root etc?
greetings
GirlKillu said:
Hi guys.
I'm also having some questions about the OTA updates and the root/bootloader.
Currently i'm still having the 25R, i unlocked it, rooted it with TWRP, all fine.
I've been using Nexus 4 before, and after lots of Roms i kept using CM for a very long time, so normally i just updated it, and i was still rooted and everything.
But now i keep reading that you will lose root and bootloader if you update the CMs (with OTA?).
So then i have to unlock and root again, so i will need to wipe all data again?
Or is there a simple method to just update and still keep all root etc?
greetings
Click to expand...
Click to collapse
Nothing will happen to the bootloader. If root is lost after applying OTA, just reflash SuperSU. You can apply OTAs using TWRP.
No wipe needed.
Hello !
I recently bought a used Z3 6603, and wanted to update it to lollipop.
But it seems it has a unlocked bootloader (according to service menu) and when i recieved it, it was factory reset, but some 3rd party apps were still installed.
One of them Super SU, so it was rooted.
I was told that i could update the firmware if i just used the Full Uninstall feature in Super Su, so i did that.
I still can't update using sony companion, becouse it knows the software is not the original one.
And i cant reinstall super su, its saying that there is no SU binary installed and the program cant install it.
I have flashed phones before, but it was really a long time ago, so im asking for some help to fix this.
Its running 4.4.4 build 23.0.1.A.5.77 and stock rom i think.
Please tell me what to do, and what info you might need !
I want to have the phone in lollipop, but everything stock, no root, no bootloader etc.
And somewhere I read something about DRM keys. Please help me with fixing that aswell thank you.
Regards ImmoralCore
ImmoralCore said:
Hello !
I recently bought a used Z3 6603, and wanted to update it to lollipop.
But it seems it has a unlocked bootloader (according to service menu) and when i recieved it, it was factory reset, but some 3rd party apps were still installed.
One of them Super SU, so it was rooted.
I was told that i could update the firmware if i just used the Full Uninstall feature in Super Su, so i did that.
I still can't update using sony companion, becouse it knows the software is not the original one.
And i cant reinstall super su, its saying that there is no SU binary installed and the program cant install it.
I have flashed phones before, but it was really a long time ago, so im asking for some help to fix this.
Its running 4.4.4 build 23.0.1.A.5.77 and stock rom i think.
Please tell me what to do, and what info you might need !
I want to have the phone in lollipop, but everything stock, no root, no bootloader etc.
And somewhere I read something about DRM keys. Please help me with fixing that aswell thank you.
Regards ImmoralCore
Click to expand...
Click to collapse
Your DRM keys are lost forever.
TheTeslaCoil said:
Your DRM keys are lost forever.
Click to expand...
Click to collapse
Ok, so they are lost even if I use the first backup that was made by the person I bought it from ?
DRM=Hardcoded=Once unlocked, always DRM free, even if you use the recovery image ?
And the rest of the questions, what am I supposed to do to get stock lollipop?
In the matter of fact it does not matter if its unlocked or locked, I just want legit lollipop, with the possibility to update regularly. (But if root is possible at the same, it can still be rooted)
Thanks for your reply !
You need the TA backup. Not system backup.
And careful not to restore some other TA.
If the previous owner backed up TA, good. If not, no chance to recover them.
Download your specific firmware in ftf format and flash it with Flashtool.
Make a clean install.
You cannot recieve OTA with an unlocked bootloader, only if you relock, but there is no point in doing that if the DRM keys are lost.
So, from where you stand, keep it rooted and unlocked, because you can do much more with it : Custom ROM' s [at the moment stock is best]...custom kernels with recovery...mods...etc.
After you flash the ftf, flash via adb a custom kernel with recovery and from recovery flash SuperSU update, as a flashable zip, that will root the phone and install SuperSU.Search also for busybox flashable zip.
TheTeslaCoil said:
You need the TA backup. Not system backup.
And careful not to restore some other TA.
If the previous owner backed up TA, good. If not, no chance to recover them.
Download your specific firmware in ftf format and flash it with Flashtool.
Make a clean install.
You cannot recieve OTA with an unlocked bootloader, only if you relock, but there is no point in doing that if the DRM keys are lost.
So, from where you stand, keep it rooted and unlocked, because you can do much more with it : Custom ROM' s [at the moment stock is best]...custom kernels with recovery...mods...etc.
After you flash the ftf, flash via adb a custom kernel with recovery and from recovery flash SuperSU update, as a flashable zip, that will root the phone and install SuperSU.Search also for busybox flashable zip.
Click to expand...
Click to collapse
Ok, I will try that then, but if I use flashtool to update to lollipop, will I still be able to root easy, or should I reinstall 4.4.4 clean, then root, fix recovery kernel and everything, and then lollipop or what goes first?
Does flash/kernel etc affect the fact that it has an unlocked bootloader ? do i need to do anything with that, or do it stay unlocked?
ImmoralCore said:
Ok, I will try that then, but if I use flashtool to update to lollipop, will I still be able to root easy, or should I reinstall 4.4.4 clean, then root, fix recovery kernel and everything, and then lollipop or what goes first?
Does flash/kernel etc affect the fact that it has an unlocked bootloader ? do i need to do anything with that, or do it stay unlocked?
Click to expand...
Click to collapse
If you have unlocked the bootloader it is always a trivial matter to root.
Just flash an insecure kernel.
If one does not exist use [NUT]'s online kernel builder to make one with recovery incorporated in it. Its very straightforward and an automated process.
So, update using flashtool, flash your custom kernel, and you have root and recovery.
gregbradley said:
If you have unlocked the bootloader it is always a trivial matter to root.
Just flash an insecure kernel.
If one does not exist use [NUT]'s online kernel builder to make one with recovery incorporated in it. Its very straightforward and an automated process.
So, update using flashtool, flash your custom kernel, and you have root and recovery.
Click to expand...
Click to collapse
1. Sorry for my noobish question, but define insecure kernel?
2. Did I get it right? I read about ppl downgrading their phones to 4.4.4 and then installing stuff. And for me it does not matter wich version it is, becouse the unlocked bootloader makes it easy to flash, even what version you are running?
ImmoralCore said:
1. Sorry for my noobish question, but define insecure kernel?
2. Did I get it right? I read about ppl downgrading their phones to 4.4.4 and then installing stuff. And for me it does not matter wich version it is, becouse the unlocked bootloader makes it easy to flash, even what version you are running?
Click to expand...
Click to collapse
1) a rooted kernel.
2) If you have unlocked there is no need to follow any of the locked bootloader guides, they are a waste of your time. One of the points point of unlocking the phone is to easily get root. You just flash a custom kernel to gain root.
If you have a locked bootloader then you have to go through all the fuss of downgrading etc etc.... but with an unlocked bootloader its so easy and straightforward
gregbradley said:
1) a rooted kernel.
2) If you have unlocked there is no need to follow any of the locked bootloader guides, they are a waste of your time. One of the points point of unlocking the phone is to easily get root. You just flash a custom kernel to gain root.
If you have a locked bootloader then you have to go through all the fuss of downgrading etc etc.... but with an unlocked bootloader its so easy and straightforward
Click to expand...
Click to collapse
Ok, thank you very much for your answers both of you!
I understand everything much better, now its just some flashing to do, c ya ! :good:
ImmoralCore said:
Ok, thank you very much for your answers both of you!
I understand everything much better, now its just some flashing to do, c ya ! :good:
Click to expand...
Click to collapse
Good luck.
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
????.?? said:
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
Click to expand...
Click to collapse
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Droidriven said:
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Click to expand...
Click to collapse
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
????.?? said:
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
Click to expand...
Click to collapse
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Droidriven said:
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Click to expand...
Click to collapse
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
I dont know guys with that phone but there should be a tool that bypass auth and unlock the bootloader in any case. I ONLY knows MTK devices, not sure about that samsung i use a .Bat file.
????.?? said:
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
Click to expand...
Click to collapse
No, I said that after the update, it could cause the bootloader to be locked and then may not be unlockable from that point on. It depends on the bootloader in the update. If this happens, you will be unable to install TWRP or root via Magisk. That is why you need to confirm whether or not flashing the update will relock the bootloader during the flashing process and, if it does, whether or not it can be unlocked again after the update.
In other words, look at exactly what you are about to jump into before you make the jump because you might land in the one place that you absolutely do not want to land.