Related
Can I root z1 on kitkat??anyone can help me?
Yes,
First, ask QUESTIONS in the Question and answer section.
Now, read the several guides in the general and/or development section on how to root.
In brief
Either, unlock your bootloader and flash an insecure kernel
or
flash stock 4.2, root, install recovery and flash a prerooted 4.4 rom.
Alll instructions are in their relevant threads so I will not reproduce them here.
Eigth time and counting I have written this today
Anyone can explain why there is not an straight forward method to root Z1 directly on kitKat and we need to downgrade to do it ?
SrMoure said:
Anyone can explain why there is not an straight forward method to root Z1 directly on kitKat and we need to downgrade to do it ?
Click to expand...
Click to collapse
Because sony has patched the known exploits and made it hard for the devs to find any expoit.
avveMeetU said:
Can I root z1 on kitkat??anyone can help me?
Click to expand...
Click to collapse
Best way to do is it to downgrade to 534 using flashtool, grab the FTF file needed from the mega collection thread.
Use vroot to root the device, install a custom recovery, flash the rom that you want to install (Monx, ihacker, romaur) then don't reboot, but re-enter flashmode and flash everything (without wipe) from an FTF of the same base, do not flash TA and System.
Reboot and youre done.
I wrote a more in depth tutorial which can be found in this thread, second post.
http://forum.xda-developers.com/showthread.php?t=2709585
dladz said:
Best way to do is it to downgrade to 534 using flashtool, grab the FTF file needed from the mega collection thread.
Use vroot to root the device, install a custom recovery, flash the rom that you want to install (Monx, ihacker, romaur) then don't reboot, but re-enter flashmode and flash everything (without wipe) from an FTF of the same base, do not flash TA and System.
Reboot and youre done.
I wrote a more in depth tutorial which can be found in this thread, second post.
http://forum.xda-developers.com/showthread.php?t=2709585
Click to expand...
Click to collapse
No that's not the best way
1) Vroot sends your IMEI number to china for no known reason. They have been asked to change this but gave no response to XDA about it.
2) The point of downgrading to a .534 FTF is that you can install recovery without rooting first. So install dualrecovery, then flash SuperSU.zip from chainfire, then flash a 4.4 rom of your choice.
avveMeetU said:
Can I root z1 on kitkat??anyone can help me?
Click to expand...
Click to collapse
It's real easy to relock the bootloader using Flashtool, so don't sweat unlocking it to root.
KarimSalloum said:
It's real easy to relock the bootloader using Flashtool, so don't sweat unlocking it to root.
Click to expand...
Click to collapse
But how do you backup your TA that way.
You need to root first then backup TA. Relocking with flashtool does not restore your TA.
Once you have your backup then that is always possible, but not for a first time root.
gregbradley said:
No that's not the best way
1) Vroot sends your IMEI number to china for no known reason. They have been asked to change this but gave no response to XDA about it.
2) The point of downgrading to a .534 FTF is that you can install recovery without rooting first. So install dualrecovery, then flash SuperSU.zip from chainfire, then flash a 4.4 rom of your choice.
Click to expand...
Click to collapse
I didn't know you could do it that way, the way that i've mentioned is what was written on all the tutorials that i've seen so i'm literally going from what other people have said, including monx.
The IMEI thing is a bit creepy but I wasn't aware of that either.
another one bricked...sigh how to fix?
Hey all,
Successfully unlocked my c9603 with latest kitkat and installed cwm 6 with these instructions
How to Install CWM 6 Recovery on Xperia Z1:
Download Doomlord’s Advanced Stock Kernel with CWM Recovery
Copy the downloaded.zip file to your phone’s sd card.
Extract the downloaded .zip folder on your PC, you will get a Boot.img file.
Place the extracted Boot.img file in the Minimal ADB & Fastboot folder that you created using our ADB & Fastboot Quick Setup Guide.
If you are using Android ADB & Fastboot full package, you can place the downloaded Recovery.img file in the Fastboot folder or in the Platform-tools folder.
Open the folder where you placed the Boot.img file. E.g Minimal ADB & Fastbootor Fastboot or Platform Tools.
Press and hold the shift key and right click on an empty area within the folder, and click on “Open Command Window Here”.
Turn off your Xperia Z1 completely.
Now press the Volume Up Key and while keeping it pressed plug in the USB cable.
You should see a blue light in the notification light of your phone, that means your device is now connected in Fastboot mode.
Now type the following command: Fastboot Flash boot Boot.img
Hit Enter and it will quickly flash CWM 6.0.4.6 recovery in your Xperia Z1
Once recovery is flashed, now issue this command “Fastboot Reboot”
Your device will reboot now, as soon as you see the Sony logo, and the pink LED, press Volume Up key to enter recovery.
Congrats! You should now see the custom recovery.
Once in CWM recovery, flash the zip file you copied to your phone in step 2. To do so, select “install zip > choose zip from sd card > doomlord advanced stock kernel.zip > yes” and flash it.
Once flashed the zip file, reboot your device.
That’s all.
ok so I did all of the with success now when I turn my phone on I get what I think is a bootloop mode...it gives me the sony logo and the pink led to boot in cwm then re loops over and over.
I can get into cwm but thats it.
So how do I go about fixing my bricked phone now? Kinda need it lol
appreciated guys
WOW, I misread that...
If you flash doomkernel you already have recovery.
Please link to where you found those instructions, they seem way out of date.
and have you unlocked your bootloader?
96329992 144
gregbradley said:
WOW, I misread that...
If you flash doomkernel you already have recovery.
Please link to where you found those instructions, they seem way out of date.
and have you unlocked your bootloader?
Click to expand...
Click to collapse
http://techbeasts.com/2014/02/19/in...ng-latest-14-2-a-1-136-firmware-how-to-guide/
thats the link I used.
and yes I unlocked the bootloader via adb and fastboot using this guide
http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
and I think I just maybe spotted my mistake, I probably should hvae used this link instead but due to sleep deprivation I didnt
http://techbeasts.com/2014/03/20/install-cwm-6-recovery-xperia-z1-android-4-4-2-kitkat-681/
anyway I went ahead and download that boot.img file, renamed it copied it across and tried to flash and I get this error
error: cannot load 'boot.img': No error
antiskeptic said:
http://techbeasts.com/2014/02/19/in...ng-latest-14-2-a-1-136-firmware-how-to-guide/
thats the link I used.
and yes I unlocked the bootloader via adb and fastboot using this guide
http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
and I think I just maybe spotted my mistake, I probably should hvae used this link instead but due to sleep deprivation I didnt
http://techbeasts.com/2014/03/20/install-cwm-6-recovery-xperia-z1-android-4-4-2-kitkat-681/
anyway I went ahead and download that boot.img file, renamed it copied it across and tried to flash and I get this error
error: cannot load 'boot.img': No error
Click to expand...
Click to collapse
Those non xda guides are crap...
If you have unlocked your bootloader (Did you make a TA backup first?) then just flash doomkernel
Doomkernel has recovery in it.
Once you have done that you are rooted and have recovery
gregbradley said:
Those non xda guides are crap...
If you have unlocked your bootloader (Did you make a TA backup first?) then just flash doomkernel
Doomkernel has recovery in it.
Once you have done that you are rooted and have recovery
Click to expand...
Click to collapse
No, I didnt back up the ta as I didnt have root in the first place.
I have doom kernal installed and can access cwm.
It is stuck in bootloop mode...how do I just get my phone to boot normally for now instead of bootlooping?
---------- Post added at 06:51 PM ---------- Previous post was at 06:39 PM ----------
i just tried all of this from xda university, still no luck at all, still boot looping
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
antiskeptic said:
No, I didnt back up the ta as I didnt have root in the first place.
I have doom kernal installed and can access cwm.
It is stuck in bootloop mode...how do I just get my phone to boot normally for now instead of bootlooping?
---------- Post added at 06:51 PM ---------- Previous post was at 06:39 PM ----------
i just tried all of this from xda university, still no luck at all, still boot looping
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Click to expand...
Click to collapse
Ok, flash SuperSU.zip from chainfires website (Google it)
Then flash a new rom of your choice.
gregbradley said:
Ok, flash SuperSU.zip from chainfires website (Google it)
Then flash a new rom of your choice.
Click to expand...
Click to collapse
Cool, ill get onto that. Ive noticed a cpl of roms floating around xda. Any suggestions on a good one or run with the
http://forum.xda-developers.com/showthread.php?t=2687275&page=8
option?
lol....might as well pick a good rom since i have stuffed my stock one.
I still will achieve my root! haha
thanks for the help so far, its always appreciated!
You do not need root to flash that.
Its a stock FTF, just flash it in flash tool
gregbradley said:
You do not need root to flash that.
Its a stock FTF, just flash it in flash tool
Click to expand...
Click to collapse
sorry I wasnt saying do i need root for this? i know i currently dont have root and can flash ftf anyway.
what i was saying was, once i have my phone back up, I will achieve root status on it...
so if I am correct flash the phone with supersu from sdcard via cwm6 then flash
[FTF] Xperia Z1 C6903 14.3.A.0.681 Commercial&Journalist
which I am downloading from http://forum.xda-developers.com/showthread.php?t=2687275
My phone should boot up now with root access, but I am only trying to fix it currently.
Cant see why I wouldnt have a working phone with root following these steps?
thanks , ill keep posting updates, might even help someone else in the process
But why are you insistent on backing up a system that is in bootloop? Why would you ever want to restore a bootlooping system?
I would just do a fresh system install and forget about backing up a non working system
Just flash the FTF of your choice, then the appropriate DooMKerneL version.
Then you are rooted and have CMW installed. 2 easy steps, I really don't understand your need to backup first, especially when your phone is bootlooping.
---------- Post added at 11:13 AM ---------- Previous post was at 11:07 AM ----------
antiskeptic said:
then flash
[FTF] Xperia Z1 C6903 14.3.A.0.681 Commercial&Journalist
which I am downloading from http://forum.xda-developers.com/showthread.php?t=2687275
My phone should boot up now with root access,
Click to expand...
Click to collapse
No, once you flash a FTF you lose root. You will need to reflash the appropriate DooMKerneL again
but I am only trying to fix it currently.
Cant see why I wouldnt have a working phone with root following these steps?
Click to expand...
Click to collapse
Because once you flash a FTF you lose root
thanks , ill keep posting updates, might even help someone else in the process
Click to expand...
Click to collapse
gregbradley said:
But why are you insistent on backing up a system that is in bootloop? Why would you ever want to restore a bootlooping system?
I would just do a fresh system install and forget about backing up a non working system
Just flash the FTF of your choice, then the appropriate DooMKerneL version.
Then you are rooted and have CMW installed. 2 easy steps, I really don't understand your need to backup first, especially when your phone is bootlooping.
---------- Post added at 11:13 AM ---------- Previous post was at 11:07 AM ----------
No, once you flash a FTF you lose root. You will need to reflash the appropriate DooMKerneL again Because once you flash a FTF you lose root
Click to expand...
Click to collapse
im not trying to backup the bootloop, i just want to fix my phone. I did not realise you were saying fresh install then start from scratch with the root process.
So I will flash the NEW ftf to my phone. Once phone is working I will flash doomlord kernel and supersu. thanks for the help. do you happen to know a link for the correct instructions for this, so I get it right this time.
Hi, everyone this is my first post.
Though I am not new to rooting, but earlier i used to do one click root..so unrooting was also that damn easy.
Recently i rooted my moto x 2nd gen xt1092 by unlocking bootloader and after flashing TWRP and later using SuperSu.
But here is the catch I didn't take nandroid backup before rooting.
So my question is
1 If I take backup now , will this backup be a rooted backup , means that if in future I flash this backup my phone will be directly boot in rooted mode..?
2 If I unroot using supersu are there chances I may stuck in bootloop?
3 now as I alreday have Twrp flashed how can I get to my original OS I once had? 9(system recovery image)
Plz let my doubts get cleared.
thanks in advance
saumyadip said:
Hi, everyone this is my first post.
Though I am not new to rooting, but earlier i used to do one click root..so unrooting was also that damn easy.
Recently i rooted my moto x 2nd gen xt1092 by unlocking bootloader and after flashing TWRP and later using SuperSu.
But here is the catch I didn't take nandroid backup before rooting.
So my question is
1 If I take backup now , will this backup be a rooted backup , means that if in future I flash this backup my phone will be directly boot in rooted mode..?
2 If I unroot using supersu are there chances I may stuck in bootloop?
3 now as I alreday have Twrp flashed how can I get to my original OS I once had? 9(system recovery image)
Plz let my doubts get cleared.
thanks in advance
Click to expand...
Click to collapse
1. yes, you can do a full backup of system, data, recovery, boot, etc (default configuration of backup) and when you do a restore you have the same root system.
2, sometimes, you have a 50% of possible failure, the best option is flash the stock system files and after do a ota update or similar (never do a downgrade, can kill your phone(hardbrick))
3. Via bootloader (down volume button when you turn on the phone)
Write or copy this lines on bootloader mode (in the same folder where you have execute the command for your unlock code for the unlock of boot loader)
fastboot flash recovery recovery.img
fastboot reboot
The recovery is on image of StockRom.
Sorry my English, I`m Chilean.
cyker31 said:
1. yes, you can do a full backup of system, data, recovery, boot, etc (default configuration of backup) and when you do a restore you have the same root system.
2, sometimes, you have a 50% of possible failure, the best option is flash the stock system files and after do a ota update or similar (never do a downgrade, can kill your phone(hardbrick))
3. Via bootloader (down volume button when you turn on the phone)
Write or copy this lines on bootloader mode (in the same folder where you have execute the command for your unlock code for the unlock of boot loader)
fastboot flash recovery recovery.img
fastboot reboot
The recovery is on image of StockRom.
Sorry my English, I`m Chilean.
Click to expand...
Click to collapse
Thanks cyke31.
My two doubts are absolutely clear.
I have a doubt regarding the 3 point.
where I will find that recovey.img file?
And after flashing that recovery.img file will I get back to my stock rom, that I had before TWRP was installed ?
Can I take OTA updates?
Will TWRP get uninstalled ?
your english is pretty good..
I am Indian ....so don't worry . I'm not grammar NAZI..
saumyadip said:
Thanks cyke31.
My two doubts are absolutely clear.
I have a doubt regarding the 3 point.
where I will find that recovey.img file?
And after flashing that recovery.img file will I get back to my stock rom, that I had before TWRP was installed ?
Can I take OTA updates?
Will TWRP get uninstalled ?
your english is pretty good..
I am Indian ....so don't worry . I'm not grammar NAZI..
Click to expand...
Click to collapse
I recommend downloading the stock rom and do a clean install , because any change you've made in system, will generate bootloop...
Here the links to the Rom (you must download The xt1092 version)
Firmwares 4.4.4 hasta 5.0.X: https://mega.co.nz/#F!TkIwRTjR!m7W1V35qfLBiiUargAx1vg
Firmwares 5.1 y 6.0: https://mega.co.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
And them install via guides on xda.
cyker31 said:
I recommend downloading the stock rom and do a clean install , because any change you've made in system, will generate bootloop...
Here the links to the Rom (you must download The xt1092 version)
Firmwares 4.4.4 hasta 5.0.X: https://mega.co.nz/#F!TkIwRTjR!m7W1V35qfLBiiUargAx1vg
Firmwares 5.1 y 6.0: https://mega.co.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
And them install via guides on xda.
Click to expand...
Click to collapse
so its better to flash system files than flashing recovery.img
though I'm in no mood to unroot my device. just wanted to know the consequences. I'll do normal backup of my current rooted rom. If in case anything happens I'll flash stock system files from motorola website.
Thanks for the info.
Xposed is the reason I rooted my device. Heard that is better to take nandroid backup before installing Xposed.
saumyadip said:
so its better to flash system files than flashing recovery.img
though I'm in no mood to unroot my device. just wanted to know the consequences. I'll do normal backup of my current rooted rom. If in case anything happens I'll flash stock system files from motorola website.
Thanks for the info.
Xposed is the reason I rooted my device. Heard that is better to take nandroid backup before installing Xposed.
Click to expand...
Click to collapse
Yes, but xposed is a thing, and the modules are totally different thing,Xposed by itself does not cause any problems...
yeah know that but...wanted to be sure..... as there is no service center in my state
Well, as you can read in the title, I somehow f*cked up my device after flashing the EliteKernelV3 onto AOXP1.4.2
Thing is, I can't get into system, nor the bootloader, but at least I got into flashmode + fastboot.
So can anyone suggest me what to do next?
I'm trying to flash a stock Sony .ftf via flashmode next, so maybe it works again after that. Gonna update this thread when done.
#update1:
ooookaaay I flashed the .ftf and now it's starting to boot again (luckily :3 ), got into system finally <3
if someone could explain me: how could this happen? I've read multiple times that there ain't no problem flashing the kernel onto AOXP. Could it be that I've restored the DRM via BackupTA and flashing EliteKernelV3 afterwards result to such a bug?
Yeah just try flashing the ftf,and if that doesn't work then you can temporarily install FreeXperiaProject Android 7.0 through fastboot because that is the only ROM I know that installs through fastboot
Dinkec27 said:
Yeah just try flashing the ftf,and if that doesn't work then you can temporarily install FreeXperiaProject Android 7.0 through fastboot because that is the only ROM I know that installs through fastboot
Click to expand...
Click to collapse
gonna keep that in mind, thanks!
devil188 said:
Well, as you can read in the title, I somehow f*cked up my device after flashing the EliteKernelV3 onto AOXP1.4.2
Thing is, I can't get into system, nor the bootloader, but at least I got into flashmode + fastboot.
So can anyone suggest me what to do next?
I'm trying to flash a stock Sony .ftf via flashmode next, so maybe it works again after that. Gonna update this thread when done.
Click to expand...
Click to collapse
You could flash TWRP using fastboot and reboot to recovery using Power + Volume down when the phone is off. I'm using EliteV3 with AOXP 1.4.3. without problems.
---------- Post added at 21:03 ---------- Previous post was at 20:55 ----------
devil188 said:
gonna keep that in mind, thanks!
Click to expand...
Click to collapse
I'm late to answer, you must not restore your TA partition as that will lock your bootloader and that means no custom kernel. If you want to use Elite you must leave BL unlocked. However you have flashable DRM fix in Cross Sony section, so you can leave it unlocked.
Cirra92 said:
You could flash TWRP using fastboot and reboot to recovery using Power + Volume down when the phone is off. I'm using EliteV3 with AOXP 1.4.3. without problems.
---------- Post added at 21:03 ---------- Previous post was at 20:55 ----------
I'm late to answer, you must not restore your TA partition as that will lock your bootloader and that means no custom kernel. If you want to use Elite you must leave BL unlocked. However you have flashable DRM fix in Cross Sony section, so you can leave it unlocked.
Click to expand...
Click to collapse
Yeah makes sense, so TWRP probably tried to flash the kernel but ultimately failed and corrupted the data in the original kernel.
Well, onto Round 2, luckily I've done a Nandroid Backup ~
When you restore a TA backup it re-locks your bootloader and when you tried to flash EliteKernel it flopped because you re-locked it,as @Cirra92 said,you can find the DRM fix on the forums
Cirra92 said:
You could flash TWRP using fastboot and reboot to recovery using Power + Volume down when the phone is off. I'm using EliteV3 with AOXP 1.4.3. without problems.
---------- Post added at 21:03 ---------- Previous post was at 20:55 ----------
I'm late to answer, you must not restore your TA partition as that will lock your bootloader and that means no custom kernel. If you want to use Elite you must leave BL unlocked. However you have flashable DRM fix in Cross Sony section, so you can leave it unlocked.
Click to expand...
Click to collapse
Oh one more question, do I need to flash the DRM fix again, as the kernel already includes it right?
devil188 said:
Oh one more question, do I need to flash the DRM fix again, as the kernel already includes it right?
Click to expand...
Click to collapse
Prior to flashing DRM fix, whether it's included in kernel zip, or in a standalone zip, you have to wipe /data partition, otherwise it won't work. But as you are starting from scratch, that won't be a problem. In other words, Factory reset, flash ROM and kernel, that's it
Cirra92 said:
Prior to flashing DRM fix, whether it's included in kernel zip, or in a standalone zip, you have to wipe /data partition, otherwise it won't work. But as you are starting from scratch, that won't be a problem. In other words, Factory reset, flash ROM and kernel, that's it
Click to expand...
Click to collapse
OK I have no clue what happened, but the status of the bootloader is locked, and still the kernel is installed successfully, and my drm keys also seem to be intact. Very strange
Hey guys, here are the modified rootable kernels for the Xperia XZ [F8331 & F8332] 7.1.1 fw
Kernel F8332
Kernel F8331
Thanks to tobias.waldvogel for his awesome resources.
Don't forget to flash the recovery. Here's the link
Recovery
Also, recovery can be accessed only through the official way i.e.
Power off >> Press the power key and the volume down key simultaneously >> As soon as the SONY logo appears, release ONLY the power key, don't release the volume down key >> After 20-30 seconds the device will enter recovery mode.
arjun.arora said:
Hey guys, here's the modified rootable kernel for the Xperia XZ Dual 7.1.1 fw
Kernel
Thanks to tobias.waldvogel for his awesome resources.
Don't forget to flash the recovery. Here's the link
Recovery
Also, recovery can be accessed only through the official way i.e.
Power off >> Press the power key and the volume down key simultaneously >> As soon as the SONY logo appears, release ONLY the power key, don't release the volume down key >> After 20-30 seconds the device will enter recovery mode.
Click to expand...
Click to collapse
Thank you
Working fine
DRM Fixed and RIC enabled
karrouma said:
Thank you
Working fine
DRM Fixed and RIC enabled
Click to expand...
Click to collapse
Glad it worked for you..
thanks a lot
Can someone please upload the same kernel for F8331 (NOT dual)? Thanks.
Papanik said:
Can someone please upload the same kernel for F8331 (NOT dual)? Thanks.
Click to expand...
Click to collapse
same kernel works with both single and dual
karrouma said:
same kernel works with both single and dual
Click to expand...
Click to collapse
OK thanks a lot.
Papanik said:
OK thanks a lot.
Click to expand...
Click to collapse
I'm not quite sure of that buddy.. Has someone tested it on the single sim version..
Extract and share the kernel.sin from the ftf file.. I'll modify it..
arjun.arora said:
I'm not quite sure of that buddy.. Has someone tested it on the single sim version..
Extract and share the kernel.sin from the ftf file.. I'll modify it..
Click to expand...
Click to collapse
No different between F8332 and F8331 kernel or fota-kernel (recovery)... Only difference are system.*.sin cach.*.sin userspace.*.sin oem.*.sin
please give me some detail instruction to install it!
my Knowledge: backup TA -> unlock bootloader -> flash this kernel -> flash recover -> flash SuperSU -> done??
after that, if i want to roll back to stock, i must do that: push TA back to phone by recovery -> reflash stock rom by flashtool.??
is this right?
and one more question : is this kernel use for stock rom and all thing will work fine??
link_it said:
please give me some detail instruction to install it!
my Knowledge: backup TA -> unlock bootloader -> flash this kernel -> flash recover -> flash SuperSU -> done??
after that, if i want to roll back to stock, i must do that: push TA back to phone by recovery -> reflash stock rom by flashtool.??
is this right?
and one more question : is this kernel use for stock rom and all thing will work fine??
Click to expand...
Click to collapse
I don't know much about the ta backup part, please make a search..
link_it said:
please give me some detail instruction to install it!
my Knowledge: backup TA -> unlock bootloader -> flash this kernel -> flash recover -> flash SuperSU -> done??
after that, if i want to roll back to stock, i must do that: push TA back to phone by recovery -> reflash stock rom by flashtool.??
is this right?
and one more question : is this kernel use for stock rom and all thing will work fine??
Click to expand...
Click to collapse
Are you on FW41 (android 7.1.1)?
If "YES" you must downgrade to MM rom and not patched "dirty-cow" vulnerable for backup TA partition (if you don't backed up later. If you have ta backup skip this step)
Then update to N 7.1.1
After update to 7.1.1:
1- unlock bootloader (backup data and internal sd, device wiped all data!)
2- go to "fastboot mode" (power off phone, when hold volume up plug your phone to pc, blue light led must be on)
3- flash that image for drm-fix and disable dm-verify with this code
Code:
fastboot flash boot boot.img
4- reboot phone complete
Code:
fastboot reboot
5- again power off and go to fastboot mode. And flash recovery now:
Code:
fastboot flash recovery twrp-***-kagura.img
fastboot reboot
6- now go to recovery and install supersu zip package.
If you want go to complete stock you need TA.img (save that several place in your PC and better save on cloud storage like google drive)
If you need, flash TA.img and flash FTF stock rom and phone back to theirs factory state.
** and for knowledge: this is not custom kernel!!!
This is custom boot.img. The kernel inside that file is completely stock. Only "ramdisk" patched for allow you to root your device and fix drm.
completery understand
GenomeX said:
Are you on FW41 (android 7.1.1)?
If "YES" you must downgrade to MM rom and not patched "dirty-cow" vulnerable for backup TA partition (if you don't backed up later. If you have ta backup skip this step)
Then update to N 7.1.1
After update to 7.1.1:
1- unlock bootloader (backup data and internal sd, device wiped all data!)
2- go to "fastboot mode" (power off phone, when hold volume up plug your phone to pc, blue light led must be on)
3- flash that image for drm-fix and disable dm-verify with this code
Code:
fastboot flash boot boot.img
4- reboot phone complete
Code:
fastboot reboot
5- again power off and go to fastboot mode. And flash recovery now:
Code:
fastboot flash recovery twrp-***-kagura.img
fastboot reboot
6- now go to recovery and install supersu zip package.
If you want go to complete stock you need TA.img (save that several place in your PC and better save on cloud storage like google drive)
If you need, flash TA.img and flash FTF stock rom and phone back to theirs factory state.
** and for knowledge: this is not custom kernel!!!
This is custom boot.img. The kernel inside that file is completely stock. Only "ramdisk" patched for allow you to root your device and fix drm.
Click to expand...
Click to collapse
many thanks for your guide. Since Z3, i've never unlock bootloader yet, so i have a bit confused because of TA partition
i'll do it on next week, after my holiday
I tried but it didn't boot.
Pedimento said:
I tried but it didn't boot.
Click to expand...
Click to collapse
Working fine with my xz dual
karrouma said:
Working fine with my xz dual
Click to expand...
Click to collapse
Mine is XZ , not dual.
Pedimento said:
Mine is XZ , not dual.
Click to expand...
Click to collapse
Same kernek. It should works
Followed the guide but it didn't boot. The problem is boot.img i think.
karrouma said:
Same kernek. It should works
Click to expand...
Click to collapse
Me too. It stuck on Sony logo. Xperia xz single sim
djgigi94 said:
Me too. It stuck on Sony logo. Xperia xz single sim
Click to expand...
Click to collapse
Share the single sim kernel.sin from the firmware..
I rooted my phone 2 weeks ago. While backing up and restoring Dem keys, I broke something I don't kno. Now every custom rom I install boots and gets stuck at Phone is starting and then reboots. Tried LOS 16, 17.1 and Pixel experience rom. But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
GOrMHATRe said:
But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Click to expand...
Click to collapse
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
GOrMHATRe said:
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
Click to expand...
Click to collapse
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
SXUsr said:
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
Click to expand...
Click to collapse
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
I have already use flashtool and newflasher. That's how I rooted my phone. Both of them are successful in flashing stock sony firmware. But the custom roms are in zip file. Don't kno of its possible to flash those using flashtool.
GOrMHATRe said:
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
Click to expand...
Click to collapse
Steps :
Remove your screen lock (set it to swipe up or none) and remove all your fingerprints registered.
Download the zip above and extract the boot, system and vendor images
Make sure you have Android 10 TWRP as mentioned above with link
Go to recovery > wipe and wipe system, cache and data nothing else.
Then go to install and flash boot.img as boot image, system.img as system image and vendor.img as vendor image.
Click to expand...
Click to collapse
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
SXUsr said:
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
Click to expand...
Click to collapse
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
GOrMHATRe said:
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
Click to expand...
Click to collapse
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
SXUsr said:
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
Click to expand...
Click to collapse
I tried this but the result was same. Rom boots upto the lock screen. Then when I swipe it shows: phone is starting and goes into bootloop. I even tried an older version of PE Rom whic contain s only img files but again same result.
You kno initially, after I unlocked the bootloader I just installed stock rom and installed LOS on top of it as per guide. It worked well. I coud go into menu and see apps.
But I panicked that I had forgotten to restore drm keys. Instead of first checking camera, I went back and restored the Ta partition and repeated the steps after it upto installation of rom and since then I have faced problems . Restoring ta partition and flashing stock rom after it is where I have made a mistake and broken something. Can this be fixed with twrp. I kno there are options in twrp to format & repair partitions. Coud that help to repair what ever that was broken?
GOrMHATRe said:
Coud that help to repair what ever that was broken?
Click to expand...
Click to collapse
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
SXUsr said:
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
Click to expand...
Click to collapse
Which kernel are you speaking about? I had backed up Ta image using renoroot exploit and restored it using:
adb pull /data/local//tmp/TA-unlocked.img
adb push TA-locked.img /data/local/tmp
Then in window with temp root prompt:
cd /data/local/tmp
de if=TA-locked.img of=/dev/block/bootdevice/by-name/TA
sync
sync
Reboot phone
But actually, when I checked my phone just now and that tmp directory seems empty. So, does that mean TA didn't get restored properly? Is that why I am facing problems? Stock roms seem to be working fine.
As for sony's own flashtool, I have it installed. But thought it doesn't offer any different functionality than newflasher or old flashtool? Woud sony flashtool help me go back to square 1 and make my phone as it was before rooting so that I can do everything again properly?
GOrMHATRe said:
Which kernel are you speaking about?
Click to expand...
Click to collapse
The kernel of the rom. Check your service menu for drm status.
SXUsr said:
The kernel of the rom. Check your service menu for drm status.
Click to expand...
Click to collapse
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
GOrMHATRe said:
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
Click to expand...
Click to collapse
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
SXUsr said:
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Click to expand...
Click to collapse
I will try this but after some time. I have experimented on my phone a lot in recently. Need it to be stable for work for some time now. My secondary phone is not setup to work with gmail etc. Thanks for all the advice you have provided though.
On another note, now that Android 11 is out, do you think we will get a rom based on it for Xz1 compact? I even had a thought of skipping 10 and going for 11 based rom.
thefelineofaveb said:
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
Click to expand...
Click to collapse
I have not touched drm keys after I backed up and restored them for the 1st time.