Related
I have not rooted my phone yet and previously come from using nexus devices.
I'm on stock lollipop rom and was wondering how I should proceed.
step one would be backing up the TA partition.
following that, unlock the bootloader. After that I was wondering if I need to downgrade to kitkat to continue or if I could flash a kernel with twrp and try to get into twrp, wipe everything and flash cm12.1 + gapps + supersu and proceed from there.
My question is, do I need to downgrade to kitkat stock to proceed or is there a way for me to gain recovery and flash a rom without downgrading?
you will need to downgrade to KK to get root access then install a stock rom that had been pre-rooted for lollipop, you don't have to unlock the bootloader but if you do then you can use a kernel that has recovery built in
Richy99 said:
you will need to downgrade to KK to get root access then install a stock rom that had been pre-rooted for lollipop, you don't have to unlock the bootloader but if you do then you can use a kernel that has recovery built in
Click to expand...
Click to collapse
But to flash a rom one does not need root, just recovery, or am I wrong there? Wouldn't it be possible to flash a kernel using fastboot just to gain access to twrp (I know that would cripple the stock rom), and then wipe everything and then just go ahead and flash cm12.1 using a microsd card?
I might be totally wrong. If there is not other way I guess I need to downgrade.
Oh and my end goal is to flash cm12.1.
Arju007 said:
But to flash a rom one does not need root, just recovery, or am I wrong there? Wouldn't it be possible to flash a kernel using fastboot just to gain access to twrp (I know that would cripple the stock rom), and then wipe everything and then just go ahead and flash cm12.1 using a microsd card?
I might be totally wrong. If there is not other way I guess I need to downgrade.
Oh and my end goal is to flash cm12.1.
Click to expand...
Click to collapse
But you cannot flash a kernel with a locked bootloader, and you cannot backup the TA without root...
So, you need to root before unlocking the bootloader.
So, downgrade to KK FW .93, root, backup TA partition (If you are going to unlock the boot, otherwise there is no point), install recovery, flash a pre-rooted lollipop rom.
No need for unlocking the boot at all unless you want a custom kernel
But if you want CM12,
downgrade to KK FW .93, root, backup TA, unlock boot, install a recovery of your choice either by a LB way (e.g. dual recovery) or by fastboot a boot.img, flash CM12.1
gregbradley said:
But you cannot flash a kernel with a locked bootloader, and you cannot backup the TA without root...
So, you need to root before unlocking the bootloader.
So, downgrade to KK FW .93, root, backup TA partition (If you are going to unlock the boot, otherwise there is no point), install recovery, flash a pre-rooted lollipop rom.
No need for unlocking the boot at all unless you want a custom kernel
But if you want CM12,
downgrade to KK FW .93, root, backup TA, unlock boot, install a recovery of your choice either by a LB way (e.g. dual recovery) or by fastboot a boot.img, flash CM12.1
Click to expand...
Click to collapse
Ah I see, root is needed to backup TA partition.
I know my bootloader needs to be unlocked as I flash Cyanogenmod 12.1 on it. I fell more secure using fastboot soo I'll probably go that way.
So to downgrade, do I use flashtool and find a kk fw .93 ftf file to flash? If I understand correct, this can be done without unlooking the bootloader.
Then from there I'll have to root with looked bootloader, backup TA partition and then unlock bootloader, and then flash kernel with twrp and then proceed to flash cm12.1 or anyother custom rom.
(Sorry If my question is a mess).
Arju007 said:
Ah I see, root is needed to backup TA partition.
I know my bootloader needs to be unlocked as I flash Cyanogenmod 12.1 on it. I fell more secure using fastboot soo I'll probably go that way.
So to downgrade, do I use flashtool and find a kk fw .93 ftf file to flash? If I understand correct, this can be done without unlooking the bootloader.
Then from there I'll have to root with looked bootloader, backup TA partition and then unlock bootloader, and then flash kernel with twrp and then proceed to flash cm12.1 or anyother custom rom.
(Sorry If my question is a mess).
Click to expand...
Click to collapse
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
gregbradley said:
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
Click to expand...
Click to collapse
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
There are plenty of reasons to flash it, only one of them is if it is stable....
gregbradley said:
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
Click to expand...
Click to collapse
Thank you! Makes much more sense now.
ondrejvaroscak said:
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Well there are unofficial builds with fixes from members who has the Leo build. The official one does not have all fixes as of yet. There are cm12.1 unofficial builds out now. Being able to test out the latest and greatest is the beauty of it.
gregbradley said:
There are plenty of reasons to flash it, only one of them is if it is stable....
Click to expand...
Click to collapse
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
For some its a first step into something new, it is always a learning curve. Some just like to have the "latest" version.
ondrejvaroscak said:
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Coming from a different device does not mean that one does lack basic knowledge. I previously used lg g2 and prior to that I used nexus 5, nexus 4 and older devices. All could be managed using fastboot. Those phones does not have drm keys that needs to be backed up. Hence I did not need that knowledge.
Either way, thank you for enlightning me. I felt to ask here in Q&A section rather than being sorry about not asking.
Arju007 said:
Coming from a different device does not mean that one does lack basic knowledge. I previously used lg g2 and prior to that I used nexus 5, nexus 4 and older devices. All could be managed using fastboot. Those phones does not have drm keys that needs to be backed up. Hence I did not need that knowledge.
Either way, thank you for enlightning me. I felt to ask here in Q&A section rather than being sorry about not asking.
Click to expand...
Click to collapse
OK. Sorry for being a bit too sceptical. Sometimes it is frustrating here with all the same questions and stories of ignorance seems not your case.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
OK. Sorry for being a bit too sceptical. Sometimes it is frustrating here with all the same questions and stories of ignorance seems not your case.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
That's fine, I totally understand you! Hope to be pro xperia user soon haha :silly:
@gregbradley Had a noob moment here and now I'm stuck. I tagged you incase you would know how to help me.
So I downgraded to .93 kitkat. All worked well.
Then I managed to root it using giefroot. All worked well.
Then I installed xzdualrecovery. It booted into twrp, I wiped everything beside internal storage and tried to flash cm12.1. I received an error.
I forgot to unlock the bootloader (ofcourse).. which is the mistake I did.
So now I'm stuck. When I turn on the phone the sony bootsplash screen comes on and it does not go past that, due to my device not having a rom.
I tried holding down the volume key and plugging in the device to my computer. My computer does not recognize what device it is but it does make a notification sound saying that I have connected a device to my computer. Fastboot doesn't work on lockedbootloader as far as I know. The flashtool recognizes the device as a flash device for around a minute when connected to the computer using volume down. After a minute my device just turns off and on leaving flash mode. So that's the current status.
Do you or anyone else have any suggestions to how I can revive my phone?
and yes I know, I feel like a noob!
Never mind, I gave it another go with flashtool and managed to get it boot!
and yes, I feel like a pro!
Don't forget to backup the ta patition before unlocking the bootloader.
Also no need to wipe system when flashing
gregbradley said:
Don't forget to backup the ta patition before unlocking the bootloader.
Also no need to wipe system when flashing
Click to expand...
Click to collapse
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
Use NDRUtils app to boot to a different recovery
Or just press volume up when the phone vibrates twice when you are booting it to get to CMW
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
/edited
i would wipe really everything despite usb otg and external sd card in advanced wipe of twrp before succeeding.
tell me if that works for you
um, i read you already had that issue again even after unlocked bootloader, try flashing a rooted lollipop .zip in recovery.
and then try wiping and flashing cm12.1 again if a full wipe (also sdcard) doesn't work
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
well, as you wrote me in pm you did mount "system", just do nothing in the mount menu after entering recovery. i also never did that.
Hi Guys,
So I managed to get my Z3 - D6603 to a state that I wanted: Lollipop, root and working Xposed. Only thing left to do was restore TA (Relock bootloader) so that I had all DRM functionality back - Perfect Device would result. I used Devshaft's tool to restore the backup I had taken before unlock of BL.
The fun started after the tool finished the restore and reboot the device, or rather, tried to reboot the device. The device was practically dead with only red LED visible with USB connected or a short vibrate when power button pressed. Nothing else (Very scary). Eventually managed to get the device to flash with flashtool in flashmode, no wipe. Device booted fine and on inspection I see the bootloader is infact relocked.
My question now is, what caused the 'Brick'? I would like to obtain root again by unlocking bootloader again, flashing Androplus and SuperSU, restore TA and relock. This time without getting the fright of my life thinking I had bricked my new and very expensive device. Any tips? Don't really want to data wipe again to go the PFCreator route.
Ch33rz,
Custom kernel and locked BL
Hey !
Relock bootloader (result of TA restore) with a custom kernel (Androplus,...) will soft brick the device. You can't boot a device with a locked bootloader and a custom kernel.
Don't panic, you can't hardbrick your device (but if you unplug your device during TA restore, you will brick it) !
DJPops said:
Hey !
Relock bootloader (result of TA restore) with a custom kernel (Androplus,...) will soft brick the device. You can't boot a device with a locked bootloader and a custom kernel.
Don't panic, you can't hardbrick your device (but if you unplug your device during TA restore, you will brick it) !
Click to expand...
Click to collapse
Thanks for the reply, man.
Okay, that makes sense. However, when I did the restore I had this "Stock" kernel flashed and not Androplus. Is this still not an acceptable kernel? What criteria does the kernel need to fulfil to allow a successful restore without a soft brick?
Kyle07 said:
Thanks for the reply, man.
Okay, that makes sense. However, when I did the restore I had this "Stock" kernel flashed and not Androplus. Is this still not an acceptable kernel? What criteria does the kernel need to fulfil to allow a successful restore without a soft brick?
Click to expand...
Click to collapse
No, that kernel has been modified so it is not stock
When on a locked bootloader you need the completely stock kernel, if it has been decompiled and recomiled (even with no changes) your phone will not boot on it.
Flash a FTF file or force a repair using PCComapnion to fix it
gregbradley said:
No, that kernel has been modified so it is not stock
When on a locked bootloader you need the completely stock kernel, if it has been decompiled and recomiled (even with no changes) your phone will not boot on it.
Flash a FTF file or force a repair using PCComapnion to fix it
Click to expand...
Click to collapse
Thank you. That clarifies it nicely.
Some sort of integrity check at play here?
Kyle07 said:
Thank you. That clarifies it nicely.
Some sort of integrity check at play here?
Click to expand...
Click to collapse
The fact is we do not know Sony keys, without them a locked bootloader will only boot a stock kernel
gregbradley said:
The fact is we do not know Sony keys, without them a locked bootloader will only boot a stock kernel
Click to expand...
Click to collapse
In hindsight that was a silly question. Appreciate your patience.
Still getting accustomed to modifying a Sony. Initially quite different to other Androids I've modded - mostly Samsungs.
Hi,
Currently i'm on KitKat 4.4.4 with Unlocked Bootloader and no DRM keys/function.
I would like to upgrade to any version of lollipop and use the DRM restore function to improve my camera quality, whilst being able to use Xposed with no boot loops.
Does anyone know of a configuration of Kernels/ROM/DRM patch that will allow me to do this?
As far as I know the DRM restore will only work on stock based roms, which require a stock kernel.
Thanks
diazlol said:
Hi,
Currently i'm on KitKat 4.4.4 with Unlocked Bootloader and no DRM keys/function.
I would like to upgrade to any version of lollipop and use the DRM restore function to improve my camera quality, whilst being able to use Xposed with no boot loops.
Does anyone know of a configuration of Kernels/ROM/DRM patch that will allow me to do this?
As far as I know the DRM restore will only work on stock based roms, which require a stock kernel.
Thanks
Click to expand...
Click to collapse
DRM restore only works if you have previously backed them up from the same phone. You can backup and restore while being on either Kitkat or Lollipop given that you back them up before unlocking the bootloader. Don't try to restore keys from another phone, you will end up with permanent bricked phone.
DRM restore only works if you have previously backed them up from the same phone. You can backup and restore while being on either Kitkat or Lollipop given that you back them up before unlocking the bootloader. Don't try to restore keys from another phone, you will end up with permanent bricked phone.
Click to expand...
Click to collapse
I don't intend on actually restoring the DRM keys, only restoring the function such as the Camera's noise cancellation.
I haven't backed up anything specifically, all I've done is UL bootloader and flash XPOSED & TWRP.
Am I screwed?
diazlol said:
I don't intend on actually restoring the DRM keys, only restoring the function such as the Camera's noise cancellation.
I haven't backed up anything specifically, all I've done is UL bootloader and flash XPOSED & TWRP.
Am I screwed?
Click to expand...
Click to collapse
No. Well, you lost your DRM.And remember. Never flash someone else' s TA partition.
TheTeslaCoil said:
No. Well, you lost your DRM.And remember. Never flash someone else' s TA partition.
Click to expand...
Click to collapse
Ok so I'll definitley not do that then. I lost my DRM on unlocking the bootloader.
However can I use this thread to restore functionality AFTER installing this ROM?
diazlol said:
Ok so I'll definitley not do that then. I lost my DRM on unlocking the bootloader.
However can I use this thread to restore functionality AFTER installing this ROM?
Click to expand...
Click to collapse
Did you backed up your TA before unlocking?
TheTeslaCoil said:
Did you backed up your TA before unlocking?
Click to expand...
Click to collapse
When I bought the phone?
No
if you did not backup the TA partition BEFORE unlocking the bootloader then you have lost your drm keys forever
Hello,
Is it possible to Root my Sony Xperia Z3 D6603 which is currently running Android 5.0.2 without losing the DRM keys?
I don't want to have to roll back to 4.4.4, or lose any of my files.
I have a pretty slow internet so i'm not a big fan of downloading stuff, I'm just psyched to check out Xposed if it exists.
No, you must roll back to a FW ending in .93 which is KK, then root, then install recovery, then update via a pre-rooted flashable zip
I would not hold my breath for a lollipop exploit. The main reason to find one has gone (i.e there already is a way to get root on lollipop with a locked bootloader)
Hussain_Salam said:
Hello,
Is it possible to Root my Sony Xperia Z3 D6603 which is currently running Android 5.0.2 without losing the DRM keys?
I don't want to have to roll back to 4.4.4, or lose any of my files.
I have a pretty slow internet so i'm not a big fan of downloading stuff, I'm just psyched to check out Xposed if it exists.
Click to expand...
Click to collapse
rooting has nothing to do with the DRM keys
you have to downgrade.
you will lose your data.
you have to download a kitkat stock rom.
No way around this if you want root.
android404 said:
rooting has nothing to do with the DRM keys
Click to expand...
Click to collapse
It does if you root by unlocking the bootloader. Doing this wipes the TA partition where the DRM keys are kept
you will lose your data.
Click to expand...
Click to collapse
Not if you do not wipe the data partition of flash the data partition from the FTF. You will get a lot of FC's when downgraded but this is not an issue as you will be upgrading immediately to Lollipop anyway
gregbradley said:
It does if you root by unlocking the bootloader. Doing this wipes the TA partition where the DRM keys are kept
Not if you do not wipe the data partition of flash the data partition from the FTF. You will get a lot of FC's when downgraded but this is not an issue as you will be upgrading immediately to Lollipop anyway
Click to expand...
Click to collapse
Of course... Thanks for correcting me.
gregbradley said:
It does if you root by unlocking the bootloader. Doing this wipes the TA partition where the DRM keys are kept
Not if you do not wipe the data partition of flash the data partition from the FTF. You will get a lot of FC's when downgraded but this is not an issue as you will be upgrading immediately to Lollipop anyway
Click to expand...
Click to collapse
But why revert if he is unlocking?
If he is unlocking he can flash a kernel with recovery and root via TWRP.
Before back up TA.
And after restore the DRM keys.
Easy.
TheTeslaCoil said:
But why revert if he is unlocking?
If he is unlocking he can flash a kernel with recovery and root via TWRP.
Click to expand...
Click to collapse
Please read the OP, he does not want to lose DRM keys, hence he needs to root without unlocking the bootloader first.
Also, if you have a custom kernel installed you cannot have DRM keys running, once you restore them using a TA partition restore you relock the bootloader and cannot boot on a custom kernel.
gregbradley said:
Please read the OP, he does not want to lose DRM keys, hence he needs to root without unlocking the bootloader first.
Also, if you have a custom kernel installed you cannot have DRM keys running, once you restore them using a TA partition restore you relock the bootloader and cannot boot on a custom kernel.
Click to expand...
Click to collapse
The DRM can be restored.
I rest my case.
TheTeslaCoil said:
The DRM can be restored.
I rest my case.
Click to expand...
Click to collapse
sigh,,,
No they cannot unless you have taken a backup before unlocking the bootloader.
There is a thread about restoring some functionality but it does not restore to 100% stock compared to when people have a stock ROM with DRM keys installed, and like I said, READ THE OP, he asked for a way not to lose his DRM keys, not to have the functions associated with them.
If you unlock without backing them up, you cannot restore them, FACT!
I really do not want to get into an online fracas with you, but this is the second time today you are jumping in and not giving exactly 100% correct answers to the questions asked.
android404 said:
Of course... Thanks for correcting me.
Click to expand...
Click to collapse
No worries
gregbradley said:
sigh,,,
No they cannot unless you have taken a backup before unlocking the bootloader.
There is a thread about restoring some functionality but it does not restore to 100% stock compared to when people have a stock ROM with DRM keys installed, and like I said, READ THE OP, he asked for a way not to lose his DRM keys, not to have the functions associated with them.
If you unlock without backing them up, you cannot restore them, FACT!
I really do not want to get into an online fracas with you, but this is the second time today you are jumping in and not giving exactly 100% correct answers to the questions asked.
Click to expand...
Click to collapse
But I already said, if you back up TA.
Check again.
And you appear to be a person that doesn' t like to be contradicted.
So...see you later.
TheTeslaCoil said:
But I already said, if you back up TA.
Check again.
And you appear to be a person that doesn' t like to be contradicted.
So...see you later.
Click to expand...
Click to collapse
Please tell the user how to back up his TA then without rooting first...
You need to back it up before unlocking the bootloader and you need root to back it up....
From now on I think me and you should only talk via PM.
Regards.
Root, backup TA. Save it on your laptop.
Unlock bootloader.
Enjoy a rooted unlocked device with endless possibilities.
If you ever want to have your phone as it was when you bought it, restore TA, unroot etc.
Easy peasy japanesey.
TheTeslaCoil said:
Root, backup TA. Save it on your laptop.
Unlock bootloader.
Enjoy a rooted unlocked device with endless possibilities.
If you ever want to have your phone as it was when you bought it, restore TA, unroot etc.
Easy peasy japanesey.
Click to expand...
Click to collapse
OK, so we are back at the situation the OP asked, how does he root without losing the DRM keys...... Your method said to unlock the boot to flash a custom kernel... That wipes the TA partition and the DRM keys BEFORE you have had a chance to back them up.
PS, as I said lets keep this via PM, I already sent one before you replied here.
gregbradley said:
OK, so we are back at the situation the OP asked, how does he root without losing the DRM keys...... Your method said to unlock the boot to flash a custom kernel... That wipes the TA partition and the DRM keys BEFORE you have had a chance to back them up.
PS, as I said lets keep this via PM, I already sent one before you replied here.
Click to expand...
Click to collapse
Just to follow up with this discussion. I am currently on a locked bootloader but rooted and installed recovery using the method mentioned in the other thread. How can I back up my TA partition? I can't find a tutorial link on TA partition backup.
mf1tym said:
Just to follow up with this discussion. I am currently on a locked bootloader but rooted and installed recovery using the method mentioned in the other thread. How can I back up my TA partition? I can't find a tutorial link on TA partition backup.
Click to expand...
Click to collapse
You have already done the "hard" part. Do some reading on this thread http://forum.xda-developers.com/showthread.php?t=2292598 ,will be short , download zip within OP ,extract and run. After you created backup store it safely I think I have mine on 4 locations (cloud and local) although I doubt I will be unlocking bootloader anytime soon.
gregbradley said:
OK, so we are back at the situation the OP asked, how does he root without losing the DRM keys...... Your method said to unlock the boot to flash a custom kernel... That wipes the TA partition and the DRM keys BEFORE you have had a chance to back them up.
PS, as I said lets keep this via PM, I already sent one before you replied here.
Click to expand...
Click to collapse
I said backup TA.
So...I' m right.
schetz said:
You have already done the "hard" part. Do some reading on this thread http://forum.xda-developers.com/showthread.php?t=2292598 ,will be short , download zip within OP ,extract and run. After you created backup store it safely I think I have mine on 4 locations (cloud and local) although I doubt I will be unlocking bootloader anytime soon.
Click to expand...
Click to collapse
Schetz, thanks mate. I saw this link before. It said it's unmaintained and the devices capatable is only to Z2 so I thought it did not work on the Z3. But I will re-read it again.
TheTeslaCoil said:
I said backup TA.
So...I' m right.
Click to expand...
Click to collapse
You said to root by unlocking the bootloader first, then backup the TA so you are wrong. Editing your post after the fact does not change this, adding the line "Before backup TA" does not make you correct as you have to root to backup the TA.. so when you say "why revert when he can just unlock", that's why.
And finally, restoring the DRM keys after unlocking means you get a locked bootloader, so you cannot boot a custom kernel so you lose root...
The point is now moot, and you need to remember my advice on this, keep it in PM's
Hey everyone
I first time use Google phone.
This time I bought pixel 3.
I want to ask what will happen to I root and unlocked my phone?
Will it lose its warranty?
Or something can't work?
Because I take Sony phone before
If Sony's phone unlocked then it's camera can't work and lose warranty.
So I want to know what I will lose after unlocking?
Or just relock it and it's ok
Sorry my English is bad.
Root will not void warranty. To get root,. You need to unlock bootloader. Unlocking bootloader resets phone to fresh state. Do that prior to setup. Everything works like normal with root.
noxqzs said:
Root will not void warranty. To get root,. You need to unlock bootloader. Unlocking bootloader resets phone to fresh state. Do that prior to setup. Everything works like normal with root.
Click to expand...
Click to collapse
So if I flash new kernels it's all ok?
And
I flash kernels have to in unlock mode
Then can I relcok after flash custome kernel?
Edemilorhea said:
Then can I relcok after flash custome kernel?
Click to expand...
Click to collapse
Do not relock your phone if it isn't 100 percent stock. You will probably brick it and won't be able to flash it. Why would you want to relock it afterwards?
TonikJDK said:
Do not relock your phone if it isn't 100 percent stock. You will probably brick it and won't be able to flash it. Why would you want to relock it afterwards?
Click to expand...
Click to collapse
Uhh because I just root my phone before when I use Sony phone.
So I can flash custome kernel and not relock and it not make me any trouble？
Is it the same as normal?
If I really want to relock, I have to flash back to original kernal then can be relock?
Sorry I long time haven't do this.
Edemilorhea said:
Uhh because I just root my phone before when I use Sony phone.
So I can flash custome kernel and not relock and it not make me any trouble？
Is it the same as normal?
If I really want to relock, I have to flash back to original kernal then can be relock?
Sorry I long time haven't do this.
Click to expand...
Click to collapse
The only issue with unlocked is that will break Google Pay if you use that. However, almost all custom kernels hide the unlock and Google Pay will be fine. Or if you root with Magisk that will also fix Google Pay
Yes, flash back to stock before you relock it.
Unlocking or relocking will wipe your data, there is no way around that.
TonikJDK said:
The only issue with unlocked is that will break Google Pay if you use that. However, almost all custom kernels hide the unlock and Google Pay will be fine. Or if you root with Magisk that will also fix Google Pay
Yes, flash back to stock before you relock it.
Unlocking or relocking will wipe your data, there is no way around that.
Click to expand...
Click to collapse
Oh I will use Google pay but kernel or magisk can fix, i think that is well, let me backup my files then to try
TonikJDK said:
The only issue with unlocked is that will break Google Pay if you use that. However, almost all custom kernels hide the unlock and Google Pay will be fine. Or if you root with Magisk that will also fix Google Pay
Yes, flash back to stock before you relock it.
Unlocking or relocking will wipe your data, there is no way around that.
Click to expand...
Click to collapse
hello,I have one more question.
is a I flash custom kernel then if I flash Original factory, kernel is original? or still is a custom kernel?
Edemilorhea said:
hello,I have one more question.
is a I flash custom kernel then if I flash Original factory, kernel is original? or still is a custom kernel?
Click to expand...
Click to collapse
You will be back to factory kernel.
TonikJDK said:
You will be back to factory kernel.
Click to expand...
Click to collapse
Oh so i can direct flash original OS, it's all will back be original.
No need to flash back google kernel first.
Question 2
Can I flash out the custom kernel and then directly Flash other custom kernels?
Question 3
Pixel can use xposed?
Really thank you very much.
Give me a big hand
Edemilorhea said:
Oh so i can direct flash original OS, it's all will back be original.
No need to flash back google kernel first.
Question 2
Can I flash out the custom kernel and then directly Flash other custom kernels?
Question 3
Pixel can use xposed?
Really thank you very much.
Give me a big hand
Click to expand...
Click to collapse
1. Yes. Fastbooting the factory image will return you to the stock google kernel. Or, you can just fastboot the boot.img as well.
2. On some of the kernels you can, check with the kernel Dev first. It's always good practice to return to the stock kernel before flashing another custom one.
3. Nope. It's not even working on the P2XL on pie.
Badger50 said:
1. Yes. Fastbooting the factory image will return you to the stock google kernel. Or, you can just fastboot the boot.img as well.
2. On some of the kernels you can, check with the kernel Dev first. It's always good practice to return to the stock kernel before flashing another custom one.
3. Nope. It's not even working on the P2XL on pie.
Click to expand...
Click to collapse
Oh thank you and thanks everyone
But where can i find stock kernel? In the stock.zip?
Edemilorhea said:
Oh thank you and thanks everyone
But where can i find stock kernel? In the stock.zip?
Click to expand...
Click to collapse
Once you extract the factory image, you will see another zip file that has the vendor, system, boot, and other images. The boot.img is the stock kernel and recovery combined.