Related
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.
Hello everyone.
I live in Brazil and I bought at the Aliexpress MI4C Xiaomi. I haven't received it yet, but I've already started researching ways to use it with another ROM than the original. The seller sends the device with google apps and multilanguage option. So, he makes some modification in the ROM, and says to not update the ROM officially on Xiaomi servers.
I see a lot of complaints about the Chinese bloatwares in ROM and so I wanted to install one that was good, but nothing with applications in Chinese or unnecessary ones.
My question is: in this case the bootloader is already unlocked?
In the meantime, I sent my request for unlocking bootloader to Xiaomi and received the SMS containing a link. As soon as I get the cellphone I intend to do the procedure. There is a risk of bricking the phone?
I’ll do appreciate good links with how-to and good ROM to daily use.
Thank you.
The seller shipping a modified ROM and telling you not to update the official would suggest your bootloader will not be locked. For now only flashing the latest official China dev builds will lock your bootloader.
Getting pre-approved for unlocking couldn't hurt though I guess.. just in case. You might need to have a working Xiaomi framework in your ROM to register your phone once though. If your ROM does not have the xiaomi services, I would suggest either Xiaomi.eu or sMiUI as a ROM, both are pretty much stock MIUI with some chinese bloat trimmed.
But most likely you will not need to unlock your bootloader anyway. You will need to check your bootloader through adb anyway before doing the steps to flashing a new ROM. You will best be flashing your recovery through adb, the instructions can be found through most ROM pages or simply searching TWRP Mi 4C. The command to check if it's unlocked is
Code:
fastboot oem device-info
A very extensive directory can be found in the INDEX thread, first in this forum.
Logic_ said:
The seller shipping a modified ROM and telling you not to update the official would suggest your bootloader will not be locked. For now only flashing the latest official China dev builds will lock your bootloader.
Getting pre-approved for unlocking couldn't hurt though I guess.. just in case. You might need to have a working Xiaomi framework in your ROM to register your phone once though. If your ROM does not have the xiaomi services, I would suggest either Xiaomi.eu or sMiUI as a ROM, both are pretty much stock MIUI with some chinese bloat trimmed.
But most likely you will not need to unlock your bootloader anyway. You will need to check your bootloader through adb anyway before doing the steps to flashing a new ROM. You will best be flashing your recovery through adb, the instructions can be found through most ROM pages or simply searching TWRP Mi 4C. The command to check if it's unlocked is
Code:
fastboot oem device-info
A very extensive directory can be found in the INDEX thread, first in this forum.
Click to expand...
Click to collapse
you cannot check the bootloader locked or not by that way. My phone when checking this, gets the input "bootloader unlocked: false" but I can flash other recovery freely.
in his case, he is using a modified rom, it means his bootloader is not yet unlocked. Right now, if he wants to come back to chinese rom, he should use Mi flash to flash his phone. If he wants other rom like CM13, he should download the latest TWRP and the rom, put the rom into his phone storage. Then try to go to fastboot to flash the recovery, then go to the recovery and flash the rom.
tuanhung303 said:
you cannot check the bootloader locked or not by that way. My phone when checking this, gets the input "bootloader unlocked: false" but I can flash other recovery freely.
in his case, he is using a modified rom, it means his bootloader is not yet unlocked. Right now, if he wants to come back to chinese rom, he should use Mi flash to flash his phone. If he wants other rom like CM13, he should download the latest TWRP and the rom, put the rom into his phone storage. Then try to go to fastboot to flash the recovery, then go to the recovery and flash the rom.
Click to expand...
Click to collapse
Ah, that might be incorrectly reporting indeed. In any case when trying to flash recovery, if you're locked it'll simply fail and won't be harmful.
But why would you think his bootloader is not unlocked? If he's using a modified rom, it was probably flashed through fastboot or a custom recovery, both require the bootloader to be unlocked.
But even if he was not on a modified rom, stock Mi 4c have always come bootloader unlocked. Someone would have to have gone out of their way to lock the bootloader and I doubt any reseller would do that, they would risk a lot of refunds from angry customers.
I strongly advise against using miflash to flash any official rom unless you have no choice, since then there's a chance you WILL lock your bootloader. For now only dev builds are locking it, but the next stable release might very well too.
The first step should be to flash TWRP
The second step to stay away from Official China build
The third step to keep away from Official China build
The fourth st...
^ sorry my bad.... I was not focused. Actually I mean his bootloader is unlocked .
The safest way is flashing via computer, using mi flash or flash twrp image. You are right
1. Ur phone not lock bootloader
2. U can flash custom recovery...(TWRP)
3. "MUST" Stay away from official MIUI ROM
4. Flash whatever u want...sMiui, CM13, etc,etc
5. Remember Point No.3
***Btw, download official Fastboot ROM and keep it to ur drive, for just in case if u want to sell it again
Hello. Thank you all. I just received my phone. Great, btw. I'll read again and again all instructions and try. Thanks again!
Cadimarco said:
Hello. Thank you all. I just received my phone. Great, btw. I'll read again and again all instructions and try. Thanks again!
Click to expand...
Click to collapse
Even as a last resort to getting your phone working if you did something wrong, please don't install the newer official roms, it's the mistake I did this weekend now I have a locked phone with a rom that has force-closes everywhere and absolutely no way back.
vletrmx21 said:
Even as a last resort to getting your phone working if you did something wrong, please don't install the newer official roms, it's the mistake I did this weekend now I have a locked phone with a rom that has force-closes everywhere and absolutely no way back.
Click to expand...
Click to collapse
yes, or the safer way is always flash the latest chinese rom via miflash. twrp does not like Chinese roms
tuanhung303 said:
yes, or the safer way is always flash the latest chinese rom via miflash. twrp does not like Chinese roms
Click to expand...
Click to collapse
No
No No
No No No
No No
No
No.
Don't flash the latest chinese rom.
No.
The only scenario where you would want to use miflash to flash a chinese rom would be as a last resort to flash the fastboot version of V7.1.6.0.LXKCNCK to restore your phone. Any later version will lock your bootloader.
If you don't care about locking your bootloader and the arduous process of unlocking it, you're easier off just taking all the latest updates OTA via the updater.
Hello everyone. Thanks for the help. In fact my bootloader was unlocked. I flashed twrp 3.0.0.3 and flashed the CM13 teamluminial, Android 6.0.1. Excellent. Thank you.
Hi!
Same scenario here..
I will receive Mi 4c with the Bootloader Unlocked, Rooted and the Multilanguage ROM.
But I have already received from Xiaomi after my request also the number for the official unlock procedure but now I'm a bit confused..
Do I have to unlock the bootloader once and for good with the official way?
Because I've read that the unofficial way isn't so secure in long term.
Do I have to install from the Updater the latest Cina Dev ROM and after that to proceed with the official unlock? Or it is better to use the Fastboot ROM?
Please could some one tell me in any case what to do ?
Thanks !
If you don't flash something that will lock your BL, no need to Unlock.
Ok first I must check the status of the bootloader to be sure that it is unlocked (via cmd control or cpu-z)
And after that can I choose an unofficial weekly miui.eu international ROM and install it?
Can I download and also update every week via Updater this ROM without issues?
At the moment my problem with flashing is that I don't have my pc (the one I have now runs win xp) and I don't want to stuck with the eventually malware or fully spammed modified rom of the reseller..
Which options do I have?
How does TWRP nandroid work with no sd card?
stillsober said:
How does TWRP nandroid work with no sd card?
Click to expand...
Click to collapse
TWRP works perfectly. The backup is simply stored in your internal storage。
6.0 Marshmallow with insecure modded kernel and TWRP recovery
This needs testing by someone else. It has been flashed on my own personal phone with no issues.
Requirements- Unlocked bootloader, Draken FX's Bootstack -the fixed version by Turbo2012 found in DrakenFX's thread for the flashable 6.0 update. Must be currently on an LG based ROM NOT CM. After install flash SuperSU install zip, post any issues. You will be able to ADB and Fastboot even if you can only boot splash screen with this kernel so you should be able to recover from almost anything multiple ways. When time allows I will put up a source built 6.0 along the lines of Game Theory's Katana ROM. Everybody is welcome to everything I post and I strongly encourage the young crowd to get involved, these phones don't support their selves.
Downloads:
Tested SuperSU
Working Bootstack for 6.0 MM
Update.zip
Instructions:
Flash Bootstack
Flash Update
Flash Beta SuperSU from link
New debloated version with insecure kernel and init.d support, rooted with Chainfire's Beta 2.71 SuperSU credit to SuperR for the help with the updater perms.
FIXED DOWNLOAD ALL APOLOGIES
Skinny Stylo Alpha version
Credits:
DrakenFX for his flashable zips and kdz files
Turbo2012 fixing and contributing
Chainfire for his SuperSU and he's been here since it started
Saved
Requirements- Unlocked bootloader
Click to expand...
Click to collapse
Does that mean a fastboot oem unlock, or the OEM unlock in the developers tools. If you mean fastboot oem unlock, is that available once you flash stock MM, since it is not in LP?
PS - thank you very much for taking the time to pick this up. Back in the days of the Galaxy S1, I had a build environment setup, and a lot more knowledge (it is amazing that if you don't use it, you lose it), but I have a son now, so I don't have the time to invest in all the hobbies that I want anymore. I will definitely be a guinea pig for you. I am not actually aware of a way to brick the Metro or TMO versions of this phone since we have a kdz -- it is not possible to blow up firmware download mode.
runningnak3d said:
Does that mean a fastboot oem unlock, or the OEM unlock in the developers tools. If you mean fastboot oem unlock, is that available once you flash stock MM, since it is not in LP?
PS - thank you very much for taking the time to pick this up. Back in the days of the Galaxy S1, I had a build environment setup, and a lot more knowledge (it is amazing that if you don't use it, you lose it), but I have a son now, so I don't have the time to invest in all the hobbies that I want anymore. I will definitely be a guinea pig for you. I am not actually aware of a way to brick the Metro or TMO versions of this phone since we have a kdz -- it is not possible to blow up firmware download mode.
Click to expand...
Click to collapse
@runningnak3d
I would prefer to be bootloader unlocked through fastboot oem unlock before doing any mods in 6.0. Every single time I did not I got secure boot error. If you make any system change on 6.0 with locked boot it will not boot.
Thank you for taking the time to do this.
:good::good:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Revenant Ghost said:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Click to expand...
Click to collapse
The main reason I made this was because I can never boot recovery or fastboot manually ( ex. w/hardware buttons) when you have the insecure kernel adb works when at the splash screen so it's easier to recover if you have any problems.
Sent from my LG-H631 using XDA-Developers mobile app
Revenant Ghost said:
So it's still not possible to update from Lollipop to rooted Marshmallow without unlocking the bootloader via fastboot? A secure boot error might as well be a brick to me. Oh well.
Click to expand...
Click to collapse
If you used Draken's guide to root and install TWRP on lollipop, your bootloader will be unlocked.
wrenchman76 said:
If you used Draken's guide to root and install TWRP on lollipop, your bootloader will be unlocked.
Click to expand...
Click to collapse
You only need a "soft" unlock (enable oem unlock in developer mode) to root / install TWRP on lolipop -- no PC required. MM however, requires a "hard" OEM unlock, and that requires a PC.
runningnak3d said:
You only need a "soft" unlock (enable oem unlock in developer mode) to root / install TWRP on lolipop -- no PC required. MM however, requires a "hard" OEM unlock, and that requires a PC.
Click to expand...
Click to collapse
I am currently on lollipop rooted and TWRP installed off of Draken's guide. Do I need to do something else to the bootloader before I flash this ROM?
wrenchman76 said:
I am currently on lollipop rooted and TWRP installed off of Draken's guide. Do I need to do something else to the bootloader before I flash this ROM?
Click to expand...
Click to collapse
Yes, you have to unlock your bootloader with fastboot oem unlock. If you flash this without unlocking your bootloader you will get a secure boot error, and you will have to flash a KDZ and start all over.
Lolipop doesn't come with fastboot. So you have to follow Draken's thread to get stock MM on your device. There is NO other way. Once you have stock MM you can unlock your boot loader with fastboot. Once you have an unlocked boot loader -- THEN you can flash this if you want.
Waiting on the debloated version.
Sent from my LGMS631 using Tapatalk
runningnak3d said:
Yes, you have to unlock your bootloader with fastboot oem unlock. If you flash this without unlocking your bootloader you will get a secure boot error, and you will have to flash a KDZ and start all over.
Lolipop doesn't come with fastboot. So you have to follow Draken's thread to get stock MM on your device. There is NO other way. Once you have stock MM you can unlock your boot loader with fastboot. Once you have an unlocked boot loader -- THEN you can flash this if you want.
Click to expand...
Click to collapse
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Revenant Ghost said:
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Click to expand...
Click to collapse
You didn't need to ship it back to LG. Firmware download mode is always available (hold vol up while plugging in USB cable -- just vol up, not vol up + power). Continue holding vol up until FW DL mode displays). Then just use the LG flash tool to flash a KDZ. It is a PITA when you have to go back that far, but you can't brick these phones, not with software at least -- they would need to be physically altered
-- Brian
Revenant Ghost said:
I can vouch for this. That's exactly what happened to me when I tried to flash this without unlocking the bootloader with fastboot. At least I finally managed to ship my device to LG for repairs today. I'll just chalk it up as another lesson learned.
Click to expand...
Click to collapse
You sent your device in for a soft brick? You should set up the flash tool for our phone with a 10j.kdz before doing anything. Hope you get it back soon.
Debloated version
Fixing some force close problems on a debloated version now, should be up later today or tonight.
@runningnak3d
Flashing the KDZ seems easy enough. But how could I fix it without unrestricted access to a computer? And my stock charger is broken without a USB cable. I had no choice but to send it in for repairs. Guess I'll be stuck on Lollipop for a while longer, at least.
Edubyah said:
6.0 Marshmallow with insecure modded kernel and TWRP recovery
This needs testing by someone else. It has been flashed on my own personal phone with no issues.
Requirements- Unlocked bootloader, Draken FX's Bootstack -the fixed version by Turbo2012 found in DrakenFX's thread for the flashable 6.0 update. Must be currently on an LG based ROM NOT CM. After install flash SuperSU install zip, post any issues. You will be able to ADB and Fastboot even if you can only boot splash screen with this kernel so you should be able to recover from almost anything multiple ways. When time allows I will put up a source built 6.0 along the lines of Game Theory's Katana ROM. Everybody is welcome to everything I post and I strongly encourage the young crowd to get involved, these phones don't support their selves.
Downloads:
Tested SuperSU
Working Bootstack for 6.0 MM
Update.zip
Instructions:
Flash Bootstack
Flash Update
Flash Beta SuperSU from link
Credits:
DrakenFX for his flashable zips and kdz files
Turbo2012 fixing and contributing
Chainfire for his SuperSU and he's been here since it started
Click to expand...
Click to collapse
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
JBoever said:
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
Click to expand...
Click to collapse
Can the bootloader be unlocked on the CDMA versions (ex. Boost, Sprint, Verizon)? If you can I will make a variant for it. But if you can't NO.
I just found out that the unlocked bootloader in 6.0 survives even the .kdz flashtool. So once you unlock your boot in 6.0 with fastboot oem unlock you never have to do it again even survived kdz downgrade to lollipop and update to 6.0 stayed unlocked.
JBoever said:
Can you post links to DrakenFx post and will this work with CDMA version (ie, Boost Mobile 770 version of hardware)
Click to expand...
Click to collapse
works great on metro ms631 just need wifi to stop turning its self off can you guys fix it! h631/ms631 mm kernel works find no errors help needed fixing wifi connection thanks
Hey guys,
I tried out the Android Concept MM when it first came out and i was a huge fan and insanely satisfied due to it's stock-like android experience, however the only thing keeping me away from using it is lack of root and xposed, however i was wondering can i just make a pre-rooted ftf with the ftf of the concept with recroot 4? like i would with a normal Marshmallow ftf or am i completely wrong?
I would appreciate the help thanks!
Concept ROM uses dm-verify, so it's unrootable on locked bootloader. However I've managed to root it on unlocked bootloader before somehow. I'll try to explain as best as I can:
1. Download and flash concept FTF http://forum.xda-developers.com/z3/...arshmallow-t3229030/post66825447#post66825447 (this is latest one I could find)
2. OTA update to the latest version if you want
3. Download Systemless SuperSU zip and place it on SD card https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
4. Flash recovery via fastboot (it needs unlocked bootloader) (for recovery I used this one) : http://forum.xda-developers.com/z3/development/z3-twrp-2-8-7-0-d6603-t3273996
5. Don't leave fastboot mode! Navigate with volume keys to "recovery mode" and click power button to enter it.
6. Flash SuperSu you downloaded earlier and then reboot.
7. Done, enjoy your rooted Concept.
Nojus33 said:
Concept ROM uses dm-verify, so it's unrootable on locked bootloader. However I've managed to root it on unlocked bootloader before somehow. I'll try to explain as best as I can:
1. Download and flash concept FTF http://forum.xda-developers.com/z3/...arshmallow-t3229030/post66825447#post66825447 (this is latest one I could find)
2. OTA update to the latest version if you want
3. Download Systemless SuperSU zip and place it on SD card https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
4. Flash recovery via fastboot (it needs unlocked bootloader) (for recovery I used this one) : http://forum.xda-developers.com/z3/development/z3-twrp-2-8-7-0-d6603-t3273996
5. Don't leave fastboot mode! Navigate with volume keys to "recovery mode" and click power button to enter it.
6. Flash SuperSu you downloaded earlier and then reboot.
7. Done, enjoy your rooted Concept.
Click to expand...
Click to collapse
Thanks but damn that sucks, i don't really wanna' lose DRM keys plus i still have 1 year of warranty left.
Also, (http://forum.xda-developers.com/z3/development/rom-zyxxos-5-1-1-v1-0-pure-stable-fast-t3229169) ZyxxOS requires a unlocked bootloader, however is there anyway i can replace the boot.img with one that's utilized on a locked bootloader ROM or will that not work
Salaminator said:
Thanks but damn that sucks, i don't really wanna' lose DRM keys plus i still have 1 year of warranty left.
Also, (http://forum.xda-developers.com/z3/development/rom-zyxxos-5-1-1-v1-0-pure-stable-fast-t3229169) ZyxxOS requires a unlocked bootloader, however is there anyway i can replace the boot.img with one that's utilized on a locked bootloader ROM or will that not work
Click to expand...
Click to collapse
Well, ZyxxOS has Sony's Concept based kernel. The developer itself at first thought it will work on locked bootloader, but it didn't. You could try to flash original Concept .2099 kernel, but I don't think it will work.
As for DRM, you can easily backup them before unlocking, but it's up to you.
Nojus33 said:
Well, ZyxxOS has Sony's Concept based kernel. The developer itself at first thought it will work on locked bootloader, but it didn't. You could try to flash original Concept .2099 kernel, but I don't think it will work.
As for DRM, you can easily backup them before unlocking, but it's up to you.
Click to expand...
Click to collapse
I'm confused with the effect DRM has but is there anyway to avoid them? Like if i backup do i just restore them after unlocking my bootloader?
Ideally, i wanted to run a AOSP like ROM and i hoped to remove all Sony stuff etc from Concept, However i'm just reluctant to unlocking my bootloader
This is probably the stupidest idea ever, I have close to no knowledge however what happens if i put Stock Sony 6.0.1 Kernel which has already obtained recovery without unlocking bootloader and flash SuperSU via that?
Alternatively, is there anyway to convert Our current Stock 6.0.1 into True Stock Android
Salaminator said:
I'm confused with the effect DRM has but is there anyway to avoid them? Like if i backup do i just restore them after unlocking my bootloader?
Ideally, i wanted to run a AOSP like ROM and i hoped to remove all Sony stuff etc from Concept, However i'm just reluctant to unlocking my bootloader
This is probably the stupidest idea ever, I have close to no knowledge however what happens if i put Stock Sony 6.0.1 Kernel which has already obtained recovery without unlocking bootloader and flash SuperSU via that?
Alternatively, is there anyway to convert Our current Stock 6.0.1 into True Stock Android
Click to expand...
Click to collapse
Maybe, but this is beyond my knowlege. Sorry.
EDIT: Or just use concept haha
Nojus33 said:
Maybe, but this is beyond my knowlege. Sorry.
EDIT: Or just use concept haha
Click to expand...
Click to collapse
Looking into Android 6.0 Complications from this article (http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/)
It states the following:
If you want root today, on Android Marshmallow (6.0), you’re going to need to use a modified boot image. While it remains to be seen if this remains true indefinitely, it looks likely to be the case for some time – SELinux changes make it much harder to get root access without modifying the boot image. And as modifying the boot image requires an unlocked bootloader
Click to expand...
Click to collapse
So i'm assuming Z3 Has SELinux thus preventing us from editting the boot image for Marshmallow Concept hence leaving us with the only option to unlock out bootloader?
Lastly: Is there a potential to convert Stock Sony ROM into an AOSP looking/feeling rom?
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.