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
Hi. Been out the loop for a while and struggling to find the answer to my question.
I'm on 4.4.4 no custom revovery but with root.
I have an OTA notice to go to lollipop, which should be fine, as I have stock evetything?
How do I simply get root back afer the update?
So many posts with options, I'm struggling to find the right answer.
Unlock bootloader, and then either use cf-autoroot or flash latest SuperSU BETA through twrp.
beekay201 said:
Unlock bootloader, and then either use cf-autoroot or flash latest SuperSU BETA through twrp.
Click to expand...
Click to collapse
Thanks, bootloader is already unlocked. I don't really want to install any custom recoveries, so the cf-autoroot sounds like the way to go.
Do you have a link for how to use this method?
Here you go http://autoroot.chainfire.eu/
Sent from my Nexus 5 using Tapatalk
teapea said:
Thanks, bootloader is already unlocked. I don't really want to install any custom recoveries, so the cf-autoroot sounds like the way to go.
Do you have a link for how to use this method?
Click to expand...
Click to collapse
to use a custom recovery you don't need to flash it.. just boot it.
'fastboot boot whatever_custom_recovery_you_want.img'
I just bought this tablet and it seems to have updated itself overnight (that or my kid did it) I want to root it , but it says it's running 5.0.1 now.. if it's possible, could someone walk me through this? I've been reading thru the various root threads, and having no luck-I'm on Ubuntu latest and have adb and fastboot installed..anyone feel like helping me out?
unlock bootloader, flash TWRP, then flash SuperSU
Bogdacutu said:
unlock bootloader, flash TWRP, then flash SuperSU
Click to expand...
Click to collapse
I did the above but with a slight change. I just booted CWM instead of flashing it so till running stock recovery but rooted.
I did this from 5.0.1 after unlocking the bootloader which was a piece of cake. There is a great guide on this forum.
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.
Greetings.. I have problem rooting latest firmware g920fxxs4dpge. Is there any working root method? I wanna flash custom rom to improve battery life. Cf Auto root cause error in Odin. Thank you
Flash the latest TWRP recovery onto your phone and install supersu from the recovery.
I think there isn't stable supersu.zip file for my firmware.
Mpongr33 said:
I think there isn't stable supersu.zip file for my firmware.
Click to expand...
Click to collapse
It's universal;
http://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Yes, ok... but after flash twrp trough Odin .11, process pass but remain stock recovery on smartphone.
I think that problem is locked bootloader. How to check it if is it locked or unlocked?
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
From https://twrp.me/devices/samsunggalaxys6.html