Database Info

[Q] From where should I start? First root, unlock bootloader or what to do first?

Hey guys. I have a Sony Xperia L C2105
Build Number: 15.3.A.1.17
I am really confused about how to start. Whether should I root the phone first or unlock the boot loader or install any cwm or whatever it is.
I need to know the whole process in detailed instruction that what steps should I do to upgrade my phone to KitKat. I know that it will void my warranty but its okay with me. :silly: Thank you. I will appreciate if someone help me with detailed step by step.

Mustafa Jafri said:
Hey guys. I have a Sony Xperia L C2105
Build Number: 15.3.A.1.17
I am really confused about how to start. Whether should I root the phone first or unlock the boot loader or install any cwm or whatever it is.
I need to know the whole process in detailed instruction that what steps should I do to upgrade my phone to KitKat. I know that it will void my warranty but its okay with me. :silly: Thank you. I will appreciate if someone help me with detailed step by step.
Click to expand...
Click to collapse
1. root device use this: http://forum.xda-developers.com/xperia-l/general/rootkit-xperia-l-15-3-1-17-1-click-root-t2591290
2. back up TA partition
3. unlock bootloader
4. flash CWM or TWRP
5. back up ur current ROM and ur done

mizukage said:
1. root device use this: http://forum.xda-developers.com/xperia-l/general/rootkit-xperia-l-15-3-1-17-1-click-root-t2591290
2. back up TA partition
3. unlock bootloader
4. flash CWM or TWRP
5. back up ur current ROM and ur done
Click to expand...
Click to collapse
Can you link me to a tutorial on how to flash CWM ? I am done till the bootloader

Mustafa Jafri said:
Can you link me to a tutorial on how to flash CWM ? I am done till the bootloader
Click to expand...
Click to collapse
here u go:
http://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320

The above thread is for locked bootloaders only and you really can't install kitkat on a locked bootloader.
After unlocking your bootloader, you should download any kitkat rom and flash the kernel inside it.
Here are the steps :
1. Open the zip file you download. (The zip that contains the rom).
2. Copy the boot.img to the root folder of your adb installed directory. Like if your adb is at C:\adb then it should look like C:\adb\boot.img.
3.Power off your phone, press and hold the volume up key and connect the usb. A blue led should glow on your phone.
4.Right click on the empty space in the adb folder while holding down shift key. Then select 'Open command prompt here'.
5. You must have adb drivers installed properly. Now in the command prompt window, type fastboot flash boot boot.img.
6.If everything done as told, you will have a new kernel with recovery.
7.Now power on the phone and press volume down repeatedly when led glows.
You will enter recovery. Now you can flash zips.

abhi007.john said:
The above thread is for locked bootloaders only and you really can't install kitkat on a locked bootloader.
After unlocking your bootloader, you should download any kitkat rom and flash the kernel inside it.
Here are the steps :
1. Open the zip file you download. (The zip that contains the rom).
2. Copy the boot.img to the root folder of your adb installed directory. Like if your adb is at C:\adb then it should look like C:\adb\boot.img.
3.Power off your phone, press and hold the volume up key and connect the usb. A blue led should glow on your phone.
4.Right click on the empty space in the adb folder while holding down shift key. Then select 'Open command prompt here'.
5. You must have adb drivers installed properly. Now in the command prompt window, type fastboot flash boot boot.img.
6.If everything done as told, you will have a new kernel with recovery.
7.Now power on the phone and press volume down repeatedly when led glows.
You will enter recovery. Now you can flash zips.
Click to expand...
Click to collapse
dude re-read his title, his only asking for the process on how to root, install CWM or TWRP, he never mentioned to customize his phone or install/flash custom ROM, for he is a noob.

mizukage said:
dude re-read his title, his only asking for the process on how to root, install CWM or TWRP, he never mentioned to customize his phone or install/flash custom ROM, for he is a noob.
Click to expand...
Click to collapse
My friend I read the post too and not just the title. Nowhere it is mentioned that he ONLY wants to root or install CWM. He wants to try kitkat and did ask for step by step procedure. Please read the full post again if you want. I agree he's a noob thus asking how to start.

abhi007.john said:
My friend I read the post too and not just the title. Nowhere it is mentioned that he ONLY wants to root or install CWM. He wants to try kitkat and did ask for step by step procedure. Please read the full post again if you want. I agree he's a noob thus asking how to start.
Click to expand...
Click to collapse
Yeah I want to try KitKat on my phone. But confused at this point. Right now I have unlocked bootloader so now should I install CWM recovery or just directly flash Kitkat ROM ? and I want to backup my Original firmware 4.2.2 also.

Mustafa Jafri said:
Yeah I want to try KitKat on my phone. But confused at this point. Right now I have unlocked bootloader so now should I install CWM recovery or just directly flash Kitkat ROM ? and I want to backup my Original firmware 4.2.2 also.
Click to expand...
Click to collapse
You can find all kernel/recoveries and roms here, yet not updated..maybe..but it will help you..
Yes..I agreed with backup stock rom before proceed to kitkat..:good:

faizalotai said:
You can find all kernel/recoveries and roms here, yet not updated..maybe..but it will help you..
Yes..I agreed with backup stock rom before proceed to kitkat..:good:
Click to expand...
Click to collapse
Post increasers^
You didn't helped me in any way. Read what I asked and then see your answer :/

Mustafa Jafri said:
Post increasers^
You didn't helped me in any way. Read what I asked and then see your answer :/
Click to expand...
Click to collapse
LOL,see my post..

faizalotai said:
LOL,see my post..
Click to expand...
Click to collapse
Bro I asked what should I do after unlocking bootloader. Whether should I install cwm recovery first or should I directly upgrade to kitkat.

Mustafa Jafri said:
Bro I asked what should I do after unlocking bootloader. Whether should I install cwm recovery first or should I directly upgrade to kitkat.
Click to expand...
Click to collapse
In order to backup your stock JB 4.2.2,you'll need a recovery 1st and its come with JB's kernel..after that then you can go with kitkat by flashing boot.img inside kitkat roms via fastboot with flashtool..
You can see the method in mostly kitkat rom 1st page..

mizukage said:
1. root device use this: http://forum.xda-developers.com/xperia-l/general/rootkit-xperia-l-15-3-1-17-1-click-root-t2591290
2. back up TA partition
3. unlock bootloader
4. flash CWM or TWRP
5. back up ur current ROM and ur done
Click to expand...
Click to collapse
"flash CWM or TWRP"
Hi, What's the difference? What's changing?
Tx

Mustafa Jafri said:
Bro I asked what should I do after unlocking bootloader. Whether should I install cwm recovery first or should I directly upgrade to kitkat.
Click to expand...
Click to collapse
How could you upgrade to kikat without flashing???
In order to flash you need recovery. I don't think the stock recovery allows flashing zips.
First root your device BEFORE unlocking your bootloader.
Then backup your TA Partition using DevShaft's tool.
After that unlock your bootloader. and flash any JB kernel. I would recommend Phantom v7. Then reboot your phone and enter recovery.
Backup your current rom
I hope you got the answer. In order to flash a rom (Kitkat in your case) you need recovery. And that is why you need to flash a custom kernel. Remember there's a difference b/w kernel and rom.

abhi007.john said:
How could you upgrade to kikat without flashing???
In order to flash you need recovery. I don't think the stock recovery allows flashing zips.
First root your device BEFORE unlocking your bootloader.
Then backup your TA Partition using DevShaft's tool.
After that unlock your bootloader. and flash any JB kernel. I would recommend Phantom v7. Then reboot your phone and enter recovery.
Backup your current rom
I hope you got the answer. In order to flash a rom (Kitkat in your case) you need recovery. And that is why you need to flash a custom kernel. Remember there's a difference b/w kernel and rom.
Click to expand...
Click to collapse
Oh now I got it. These guys were confusing me. You made it clear. Thanks

Okay guys, I have unlocked bootloader and I have flashed Civic Kernel (Phantom Kernel and Thunder was not working for me I don't know why). So how should I backup my stock rom and how to flash custom rom I know how to go into cwm recovery.

There must be an option to backup.. Unfortunately I haven't used civic kernel so can't tell which recovery is it. Look for some option which says backup, or nandroid backup etc.
And if possible post screenshot.(or photo)

Okay I have backup the old one and now I am at Resurrections ROM. And it works perfect.
Sent from my C2105 using XDA Free mobile app

[WORK-IN-PROGRESS] Lets achieve root for E3-Almost there!!

Root status: Permission Denied
Lets keep this thread reserved only for discussion related to rooting this phone. We haven't achieved root yet but I know the way to do it.
You need to follow this guide in order to root your device: http://whiteboard.ping.se/Android/Rooting
So till now I have been able to:
-Build a new kernel
-Unpacked the kernel using kernel kitchen by championswimmer and flashtool(for the sin file)
-.Made the changes in ramdisk
But the next step requires packing it back again. And for doing that you need the cmdline from the kernel.
Its located in /proc/cmdline.
I tried to view it via adb but obviously the system denied the permission because of no root.
Usually you can easily obtain cmdline parameters from the boot.img itself, but in this case, Sony has done some shizz so that you cant obtain it directly. Plus this is my first Sony device so I dont have much knowledge regarding this..
I wont get much time to work on it becuz of my exams.. that's why this thread is here
If you can help/contribute in any way then you are surely welcome. But no noob posts here.

@InfinityShooter use archi's kitchen for unpacking boot.img
first convert stock kernel.sin file to boot.img(by just renaming it)
archi's kitchen will give you the cmdline and other parameters to pack the kernel..

k2wl said:
@InfinityShooter use archi's kitchen for unpacking boot.img
first convert stock kernel.sin file to boot.img(by just renaming it)
archi's kitchen will give you the cmdline and other parameters to pack the kernel..
Click to expand...
Click to collapse
It doesn't work. Sony uses a different kind of boot.img. I have tried dsixda kitchen also, it didnt work out.

InfinityShooter said:
It doesn't work. Sony uses a different kind of boot.img. I have tried dsixda kitchen also, it didnt work out.
Click to expand...
Click to collapse
oh !!! my old sony xperia m used have kernel .sin which used to convert to boot.img by renaming....
Hmmm... how about using a dd command to extract boot.img to sdcard and then unpack it in archi's kitchen????

k2wl said:
oh !!! my old sony xperia m used have kernel .sin which used to convert to boot.img by renaming....
Hmmm... how about using a dd command to extract boot.img to sdcard and then unpack it in archi's kitchen????
Click to expand...
Click to collapse
I don't know if this can help at all: http://forum.xda-developers.com/showthread.php?t=1659584.
It's been ages since I gave up on linux, even as an amateur, so my knowledge is quite limited and, to be honest, a lot of hunch is involved. That's why I am so hesitant at trying this myself.
Anyway I hope this helps a bit.
Also you can get the latest firmware for D2203 (18.4.C.2.12) from here: https://mega.co.nz/#!bMBg1Rqa!aqGcTv6ved0ifh867pbnVVsc-4t55lR9OOij1iSiNLA, which means that one can probably try without unlocking the bootloader...

I have already made the kernel but needs testing. Anyone here with unlocked bootloader and d2202 can try hotboot this using flash tool.
http://d-h.st/rx7e
Try at your own risk.
There is 0% chance of bricking if you hotboot it.
DO NOT FLASH IT

I've tried the kernel. But I do not know how to enter CWM, whether the kernel already include CWM?

No it is not cwm you have to use adb to mount /system as read/write then push su to /system/bin and you will get root. All you need is get superuser from playstore.
Sent from my D2212 using XDA Free mobile app

Report!
The boot.img which I had posted has been confirmed working.
We now have the correct command for packing the boot.img thanks to @jerpelea
I'll be looking forward to making a recovery from source.
If it works then root is not far away

InfinityShooter said:
The boot.img which I had posted has been confirmed working.
We now have the correct command for packing the boot.img thanks to @jerpelea
I'll be looking forward to making a recovery from source.
If it works then root is not far away
Click to expand...
Click to collapse
will, it work on xperia e3 d2212

android-vinay said:
will, it work on xperia e3 d2212
Click to expand...
Click to collapse
Not now.. only for d2202.

I don't know if this a noob question: in the tutorial InfinityShooter posted earlier it says that the phone must have an unlocked bootloader. Thing is that I am a bit confused in terms of whether the bootloader must be unlocked to obtain the system image or in order to fastboot the insecure image. If it is just to obtain the image then wouldn't it be possible to cook the insecure image using the ROM image that Sony distributed to developers, leading to a solution that doesn't interfere with the bootloader?

after I try the kernel, no bugs are found, everything works fine, like wifi and the other no problem, just given cwm to facilitate root...

CWM
Ok this is the second build of the cwm kernel
You can get it here: https://www.androidfilehost.com/?fid=95832962473396055 Doesnt work
You have to HOTBOOT this kernel
Tell me if it works or not.
Troubleshooting:
If you are stuck at black screen then dont worry. Just press and hold power+vol up keys together for 20 seconds to reboot it.
On rebooting the system will automatically revert to stock kernel which you were using earlier.
Congrats! Your phone is working again!

i must have unlock bl?
Wysyłane z mojego WT19i za pomocą Tapatalk 2

Unfortunately yes. Bad thing is that when we unlock the bootloader the TA partition is formatted leading to various problems with Sony apps.

Okay I need help here. My testers report this kernel as working but it fails to work on my device. Please let me know what happens with you..
Link: http://d-h.st/NFR
Here are the EXACT things I do to flash it:
1. Open flashtool
2. Connect my phone
3. I click on thunder icon in flashtool and choose fastboot mode.
4.I click on "Reboot into fastboot mode[adb]"
5.I click on "Select kernel to hotboot" and open the boot.img inside it.
I look at my phone,its all dark. The blue light goes away
6.I click on check current device status and it shows adb connected
7.Orange led comes up as my phone is connected to pc
I see no sony logo or anything like that.
The screen is still BLACK! One thing I notice is that whenever I press the power key, the screen backlight turns on little bit enough for me to notice the varaiation.
Please post your intruction set if it works out for u.

I can't test it myself since I have locked bootloader but did you try to get a working adb shell at this state? If shell works then you might be able to push su and supersu to the device.

cnagr said:
I can't test it myself since I have locked bootloader but did you try to get a working adb shell at this state? If shell works then you might be able to push su and supersu to the device.
Click to expand...
Click to collapse
Dude I cant see anything on screen and you are talking about pushing files -.-

Dude you said that the phone appears to be connected to the pc in adb state, regardless of the phone screen state. That's where that big if of my suggestion came from.

Mi4c Flash TWRP‘s recovery and CM’s ROW without unlock BL

Code:
Mi4c Flash TWRP‘s recovery and CM’s ROW without unlock BL
How：
1. From the high version down to a low version with root permission.
rom: libra_images_6.1.7_20151221.0000.11_5.1_cn
2. We can get root permission at the vertion of libra-6.1.7
a)So We can use dd command.
b)And the version can use fastboot command.
I tested it. It was ok.
Steps：
一．Prepare
1. Download miflash
bigota。d.miui。com/tools/MiFlash20150601_win10.exe
2.Download libra_images_6.1.7
bigota。d.miui。com/6.1.7/libra_images_6.1.7_20151221.0000.11_5.1_cn_b09dac70a0.tgz
3.Download recovery
www。teamsuperluminal。org/recovery
二．TODO
1. Goto 9008 : adb reboot edl
2. To flash libra_6.1.7 with miflash tool
3. Reboot; adb push recovery.img /storage/emulated/legacy/
4. 130|[email protected]:/ $ su
5. 130|[email protected]:/ # dd if=/storage/emulated/legacy/recovery.img of=/dev/block/bootdevice/by-name/recovery
6. Enjoy yourself.
BY Eismog

Thanks qimuzhi!
Is it recommended to backup the IMEI / efs before replacing the recovery?
If so, can you point to (or add) relevant instructions?
Thanks!

I have no idea what this is about. Is this a way to install TWRP on a rooted mi4c by dd even though bootloader is locked? Doesn't this work only when bootloader is unlocked?
What does qimuzhi want to tell us??

qtotter said:
What does qimuzhi want to tell us??
Click to expand...
Click to collapse
Basically, you can roll back to an older developer version with an unlocked bootloader and then install TWRP.

This is a complicated way for anyone with a working locked bootloader Mi4c to downgrade the rom and flash TWRP:
You need to reboot to EDL ( Emergency DownLoad) mode, you can only do this from adb with working phone
Then flash an old unlocked rom with MIflash Tool (not sure this work with locked BL)
Then boot the phone, gain su right, and flash recovery whit dd command
You can save time after flashing the rom with unlocked bootloader, simply shut down the phone and boot in fastboot before the rom inizialization
With an unlocked phone you can simply push recovery from fastboot with " fastboot flash recovery recovery.img" command then boot into recovery

I see. It was known that you can go back to unlocked bootloader by flashing the stable 7.0.16.0 over the latest locked dev ROM, but this is a way to roll back to an older dev ROM with unlocked bootloader from the latest dev ROM as long as it's working (not boot-looping or softbricked.)
Is my understanding correct?
---------- Post added at 08:04 AM ---------- Previous post was at 07:41 AM ----------
ice-it said:
This is a complicated way for anyone with a working locked bootloader Mi4c to downgrade the rom and flash TWRP:
Click to expand...
Click to collapse
So, it doesn't have to be dev ROM 6.1.7, and you can also use stable 7.0.16.0 ROM instead?

qtotter said:
I see. It was known that you can go back to unlocked bootloader by flashing the stable 7.0.16.0 over the latest locked dev ROM, but this is a way to roll back to an older dev ROM with unlocked bootloader from the latest dev ROM as long as it's working (not boot-looping or softbricked.)
Is my understanding correct?
---------- Post added at 08:04 AM ---------- Previous post was at 07:41 AM ----------
So, it doesn't have to be dev ROM 6.1.7, and you can also use stable 7.0.16.0 ROM instead?
Click to expand...
Click to collapse
I think the stable build is the only possible to use from updater app...
He is using dev rom because he need su right to flash recovery in his way...

Itamar01 said:
Is it recommended to backup the IMEI / efs before replacing the recovery?
Click to expand...
Click to collapse
The recovery partition is totally different from the area where efs is stored... You also asked the same question at miui.com, and someone already answered...
http://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599
---------- Post added at 09:25 AM ---------- Previous post was at 08:32 AM ----------
ice-it said:
I think the stable build is the only possible to use from updater app...
Click to expand...
Click to collapse
There are two kinds of ROM formats. One is recovery compatible ROM which you can flash from recovery or from updater app. You need to use full ROMs, not incremental ROMs (patch files) to switch between ROMs.
The other is what they call fastboot ROM which you can flash from bootloader or from miflash. Basically, fastboot ROMs are simply a zipped file containing all the partition images and scripts. miflash simply extracts images from a zipped file and automatically flashes the images in order. You can do it manually, using the bat or sh scripts in the same zipped file.
ice-it said:
He is using dev rom because he need su right to flash recovery in his way...
Click to expand...
Click to collapse
I think the point here is you can roll back to older ROMs using edl mode. Obviously, bootloader ignores the lock/unlock flag or ROM versions in edl mode at the moment until Xiaomi fixes this hole. (I suppose Xiaomi will disable edl mode soon...)
Once you are back on unlocked ROMs, I don't think you need su just for flashing recovery. You can simply go to bootloader and flash recovery by 'fastboot flash recovery recovery.img', can't you?

qtotter said:
There are two kinds of ROM formats. One is recovery compatible ROM which you can flash from recovery or from updater app. The other is what they call fastboot ROM which you can flash from bootloader or from miflash.
Click to expand...
Click to collapse
yeah sure, i was not clear before, i mean you cant roll back from updater app with an old dev rom, but you can move to stable and this will unlock your bootloader
fastboot version is useless because the locked bootloader
qtotter said:
I think the point here is you can roll back to older ROMs using edl mode. Obviously, bootloader ignores the lock/unlock flag or ROM versions in edl mode at the moment until Xiaomi fixes this hole. (I suppose Xiaomi will disable edl mode soon...)
Once you are back on unlocked ROMs, I don't think you need su just for flashing recovery. You can simply go to bootloader and flash recovery by 'fastboot flash recovery recovery.img', can't you?
Click to expand...
Click to collapse
I hope EDL will ignore the locked bl, but i cant verify with mi4c, in the past this worked with other manufacturer
like i said in a post earlier, if your phone is working there's no need to follow the procedure written by op, just flash stable through updater app and recovery from fastboot like you said
if they disable EDL mode then they could have trouble repairing phone in less than an hour like they do in china

ice-it said:
fastboot version is useless because the locked bootloader
Click to expand...
Click to collapse
No, it's opposite. Fastboot ROMs are useful because it was found that you can flash any fastboot ROMs locked or unlocked in edl mode at the moment!
Again, as you said, this method only works on a working phone. Not a savior for those who got their phones bootlooped...
---------- Post added at 10:10 AM ---------- Previous post was at 10:00 AM ----------
ice-it said:
like i said in a post earlier, if your phone is working there's no need to follow the procedure written by op, just flash stable through updater app and recovery from fastboot like you said
Click to expand...
Click to collapse
I saw some people got bootloop while switching from dev ROM to stable 7.0.16.0 by updater app in order to regain unlocked bootloader. This method seems safer to me...

Partitions Backup & Restore
qtotter said:
The recovery partition is totally different from the area where efs is stored... You also asked the same question at miui.com, and someone already answered...
http://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599
Click to expand...
Click to collapse
Thanks for the link! Partitions Backup & Restore looks like a very useful app!
BTW, I managed to run TWRP from fastboot and make a backup of the system but it did not have the option to backup the EFS and the Modems

Itamar01 said:
Thanks for the link! Partitions Backup & Restore looks like a very useful app!
BTW, I managed to run TWRP from fastboot and make a backup of the system but it did not have the option to backup the EFS and the Modems
Click to expand...
Click to collapse
TWRP does not always come with efs backup option. It's dev's choice whether it's included or not. The method is all the same as Partitions Backup & Restore, anyway.

qtotter said:
I saw some people got bootloop while switching from dev ROM to stable 7.0.16.0 by updater app in order to regain unlocked bootloader. This method seems safer to me...
Click to expand...
Click to collapse
Maybe it's because the rom version? I know people who use the 7.1.6.0 to roll back...
If it's working could be safer, we need someone who can try and report back

ice-it said:
Maybe it's because the rom version? I know people who use the 7.1.6.0 to roll back...
If it's working could be safer, we need someone who can try and report back
Click to expand...
Click to collapse
True. Personally, I'd stay away from any ROMs with locked bootloader, and only use fastboot to flash images. Flashing ROMs including bootloader (locked or unlocked) via recovery or updater app seems kinda risky to me.
It looks like too many people who don't know what they're doing are playing with ROMs and bricking their Xiaomi phones. There are guides introducing flashing dev ROMs only for rooting. It's rather shocking...

qtotter said:
It looks like too many people who don't know what they're doing are playing with ROMs and bricking their Xiaomi phones. There are guides introducing flashing dev ROMs only for rooting. It's rather shocking...
Click to expand...
Click to collapse
Yeah I know, people actually don't know what they're doing and why, they read but they can't understand what's written, and take all for absolute truth...
Then they open a post here and there, crying and complaining

I have my mi4c locked. There is any method to put the device in EDL mode? I only can put him in fastboot and I can't run adb commands.

n1k3z0n3 said:
I have my mi4c locked. There is any method to put the device in EDL mode? I only can put him in fastboot and I can't run adb commands.
Click to expand...
Click to collapse
Hello and welcome to XDA! ( I'm Fede91 from en.miui )
Sorry, but it seems that adb is the only way, I've searched the net for days but every method I tried doesn't work...
I think we need to tamper with the hardware to put the phone in edl...

ice-it said:
Hello and welcome to XDA! ( I'm Fede91 from en.miui )
Sorry, but it seems that adb is the only way, I've searched the net for days but every method I tried doesn't work...
I think we need to tamper with the hardware to put the phone in edl...
Click to expand...
Click to collapse
Hi Fede91 .
Yeah I did the same without any result :S. This is frustating . I allready created another account and I'm trying to get to diamond to see if I get an unlock code. I'm tired of waiting for another solution

Can you install a custom rom after doing this?
//EDIT:
Well this was to easy, I started out on 7.1.6.0 Global Stable (locked Bootlader), then I just flashed the 7.0.16.0 Global Stable, installed twrp via fastboot, then did "/fastboot oem unlock" which worked (don't know if it was necessary) and after all that installed sMIUI after doing a full wipe. sMIUI up and running!

二．TODO
1. Goto 9008 : adb reboot edl
2. To flash libra_6.1.7 with miflash tool
3. Reboot; adb push recovery.img /storage/emulated/legacy/
4. 130|[email protected]:/ $ su
5. 130|[email protected]:/ # dd if=/storage/emulated/legacy/recovery.img of=/dev/block/bootdevice/by-name/recovery
6. Enjoy yourself.
Can someone provide a step by step tutorial for this?

Rootable Stock Kernel [32.2.A.0.253] [E6883]

Hey guys, just compiled a rootable kernel for the Z5P (E6883) 6.0.1 dual sim version, FW 224.
Features:
1. Sony RIC is disabled.
2. TWRP recovery - press volume up while booting.
3. Busybox.
4. DRM fix.
Code:
fastboot boot boot.img
fastboot reboot
IMPORTANT:
1. Please don't flash any recovery after flashing this kernel as recovery is already present in it.
2. Press volume up to enter recovery, pressing volume down won't work and the phone will reboot.
The first version was having some root permission issues. Flash the new kernel and then flash SuperSU 2.65 via recovery.
Reboot to system and manually install SuperSU 2.74 beta. Update the binary and reboot.
Thanks to tobias.waldvogel for his resources and tutorials.
Please don't flash it on any other device.
I'll not be responsible if you damage your device, just make sure your bootloader is unlocked and you know how to flash using fastboot.​

Is it runs E6853 ?
edit ...

jarnsaxa said:
Is it runs E683 ?
Click to expand...
Click to collapse
Its only for the E6883 dual sim variant..

arjun.arora said:
Its only for the E6883 dual sim variant..
Click to expand...
Click to collapse
Hey man,
I've already put up the kernel for e6883 in the general section in the proper thread no offence

It work on e6833 it is the same kernel??

jarnsaxa said:
Is it runs E6853 ?
edit ...
Click to expand...
Click to collapse
karrouma said:
It work on e6833 it is the same kernel??
Click to expand...
Click to collapse
Well, in theory is should. You can give it a shot. If it doesn't, flash the stock kernel with flashtool to revert back. Don't flash it on single sim variants of the Z5P.

arjun.arora said:
Well, in theory is should. You can give it a shot. If it doesn't, flash the stock kernel with flashtool to revert back. Don't flash it on single sim variants of the Z5P.
Click to expand...
Click to collapse
I flashed it over custom rom RomAUR v4.0.1, on E6833. Unfortunately it says Baseband version Unknown and thus doesn't recognise the sim - plus the brightness slider doesn't function.

slayerz said:
I flashed it over custom rom RomAUR v4.0.1, on E6833. Unfortunately it says Baseband version Unknown and thus doesn't recognise the sim - plus the brightness slider doesn't function.
Click to expand...
Click to collapse
This is for stock firmwares buddy.. RomAur already has a modded kernel..

arjun.arora said:
This is for stock firmwares buddy.. RomAur already has a modded kernel..
Click to expand...
Click to collapse
It work with e6833??
Same kernel

what about E6653 ?

arjun.arora said:
Hey guys, just compiled a rootable kernel for the Z5P (E6883) 6.0.1 dual sim version, FW 224.
Features:
1. Sony RIC is disabled.
2. TWRP recovery - press volume up while booting.
3. Busybox.
4. DRM fix.
Code:
fastboot boot boot.img
fastboot reboot
The first version was having some root permission issues. Flash the new kernel and then flash SuperSU 2.65 via recovery.
Reboot to system and manually install SuperSU 2.74 beta. Update the binary and reboot.
Thanks to tobias.waldvogel for his resources and tutorials.
Please don't flash it on any other device.
I'll not be responsible if you damage your device, just make sure your bootloader is unlocked and you know how to flash using fastboot.​
Click to expand...
Click to collapse
Thanks. I'll try it later tonight.. I've had a pretty ****ty time this far with other boots. Nothing has worked with 6.0.1 224 for me, but I'm willing to try.
In sitting on the 6.0 Hong Kong 1.185 atm
Sent from my E6883 using XDA-Developers mobile app

slayerz said:
I flashed it over custom rom RomAUR v4.0.1, on E6833. Unfortunately it says Baseband version Unknown and thus doesn't recognise the sim - plus the brightness slider doesn't function.
Click to expand...
Click to collapse
korom42 said:
what about E6653 ?
Click to expand...
Click to collapse
I don't own a 6653 buddy. Do one thing, please share the kernel.sin of your fw, open the firmware in winrar and extract it.

giz02 said:
Thanks. I'll try it later tonight.. I've had a pretty ****ty time this far with other boots. Nothing has worked with 6.0.1 224 for me, but I'm willing to try.
In sitting on the 6.0 Hong Kong 1.185 atm
Sent from my E6883 using XDA-Developers mobile app
Click to expand...
Click to collapse
FAILED!
Attempt 1:
Procedure -
Flashed Customised MY 32.2.A.0.224
Dropped to fastboot flashed boot and recovery (twrp-3.0.2-0-E6653-20160417.img)
Rebooted.. to system
Couldn't update SU from OS. (Installation Failed)
Tried dropping recovery again so I could load su manually, but no file systems were mountable.
Attempt 2:
Procedure
Flashed Stock Customized IN 32.2.A.0.224
Rebooted to system
Dropped to fastboot
Flashed boot
Rebooted to System
Launched SU, couldn't update from OS (Installation Failed)
Dropped to fastboot
Flashed recovery (twrp-3.0.2-0-E6653-20160417.img)
rebooted to recovery so I could load su manually,
but no file systems were mountable. (Same as attempt 1)
You've wasted my time - NO workable root...
At least Xreality/DRM appears to have worked.
Going back to 6.0

giz02 said:
FAILED!
Attempt 1:
Procedure -
Flashed Customised MY 32.2.A.0.224
Dropped to fastboot flashed boot and recovery (twrp-3.0.2-0-E6653-20160417.img)
Rebooted.. to system
Couldn't update SU from OS. (Installation Failed)
Tried dropping recovery again so I could load su manually, but no file systems were mountable.
Attempt 2:
Procedure
Flashed Stock Customized IN 32.2.A.0.224
Rebooted to system
Dropped to fastboot
Flashed boot
Rebooted to System
Launched SU, couldn't update from OS (Installation Failed)
Dropped to fastboot
Flashed recovery (twrp-3.0.2-0-E6653-20160417.img)
rebooted to recovery so I could load su manually,
but no file systems were mountable. (Same as attempt 1)
You've wasted my time - NO workable root...
At least Xreality/DRM appears to have worked.
Going back to 6.0
Click to expand...
Click to collapse
You don't have to flash recovery after flashing this. It already has TWRP. Read the instructions carefully.

arjun.arora said:
You don't have to flash recovery after flashing this. It already has TWRP. Read the instructions carefully.
Click to expand...
Click to collapse
Bro. Read beyond attempt 1 procedure.. Carefully
I tried su binary upgrade os.. FAILED
Recovery didn't after this attempt .. held vol down after yellow LED but was greeted by flashing red LED, followed by black screen and reboot.
Flashed recover at this point.. permissions trashed.
Couldn't mount any fs..
Failed.
What are you saying anyway, that u can't flash recovery with your kernel?
I regardless, i recommend as a e6883 owner with device in hands to other e6883 owners that this kernel be avoided until fixed .
I'm guessing you guys didn't rebuild from scratch after your ran into your 2.65 su issues. The jump to 2.74 isn't working for me with your kernel fix

giz02 said:
Bro. Read beyond attempt 1 procedure.. Carefully
I tried su binary upgrade os.. FAILED
Recovery didn't after this attempt .. held vol down after yellow LED but was greeted by flashing red LED, followed by black screen and reboot.
Flashed recover at this point.. permissions trashed.
Couldn't mount any fs..
Failed.
What are you saying anyway, that u can't flash recovery with your kernel?
I regardless, i recommend as a e6883 owner with device in hands to other e6883 owners that this kernel be avoided until fixed .
I'm guessing you guys didn't rebuild from scratch after your ran into your 2.65 su issues. The jump to 2.74 isn't working for me with your kernel fix
Click to expand...
Click to collapse
You need to press volume up after flashing the kernel..

Working perfect for me..no issue at all..e6883
Sent from my E6883 using XDA-Developers mobile app

zams85 said:
Working perfect for me..no issue at all..e6883
Sent from my E6883 using XDA-Developers mobile app
Click to expand...
Click to collapse
Great

arjun.arora said:
You need to press volume up after flashing the kernel..
Click to expand...
Click to collapse
Yes..
flash using flashtool.
drop to fastboot (vol up)
flash boot image... reboot
I get into OS, and su tries to update from 265 to 274.. fails in os
reboot to recovery (vol down when yellow led comes on)
try installing su zip from but can't see file system.. can't mount.. busted permissions everywhere
to recover I revert to 6.0
flashtool (using customized HK .185 load)
after flash, drop to fast boot (vol up)
flash older 6883MM bin
flash recovery (3.0.2)
boot to os.
reboot to recovery
install SU (file systems mount without issue).
everything works normally at 6.0 again
---------- Post added at 09:22 AM ---------- Previous post was at 09:18 AM ----------
zams85 said:
Working perfect for me..no issue at all..e6883
Sent from my E6883 using XDA-Developers mobile app
Click to expand...
Click to collapse
When you say "Works perfectly" have you gone into recovery mode and attempted file system mount, OR;
did you flashtool, then flash boot and then use phone?
I'll say that the phone booted to OS fine with this kernel, and I was able to access xreality settings, HOWEVER I was not able to use recovery mode due to numerous permissions errors. (could not mount FS.)
you (ZAM): have you tested recovery mode? specifically mounting fs and and installing zips?

giz02 said:
Yes..
flash using flashtool.
drop to fastboot (vol up)
flash boot image... reboot
I get into OS, and su tries to update from 265 to 274.. fails in os
reboot to recovery (vol down when yellow led comes on)
try installing su zip from but can't see file system.. can't mount.. busted permissions everywhere
to recover I revert to 6.0
flashtool (using customized HK .185 load)
after flash, drop to fast boot (vol up)
flash older 6883MM bin
flash recovery (3.0.2)
boot to os.
reboot to recovery
install SU (file systems mount without issue).
everything works normally at 6.0 again
---------- Post added at 09:22 AM ---------- Previous post was at 09:18 AM ----------
When you say "Works perfectly" have you gone into recovery mode and attempted file system mount, OR;
did you flashtool, then flash boot and then use phone?
I'll say that the phone booted to OS fine with this kernel, and I was able to access xreality settings, HOWEVER I was not able to use recovery mode due to numerous permissions errors. (could not mount FS.)
you (ZAM): have you tested recovery mode? specifically mounting fs and and installing zips?
Click to expand...
Click to collapse
Yep no problem..before this i stay with stock rom..then decide to root and i use this kernel..flash using flashtool and go to recovery for backup stock rom because i want to use custom rom..so no problem with mount or unmount..stock rom backup perfectly..no issue
Sent from my E6883 using XDA-Developers mobile app

[ROOT] [MAGISK] (Without Recovery) Root your device with MAGISK Without Recovery

Hello Everyone,
This is my first tutorial here.
So, any mistakes should be reminded in the thread.
==================================================
Guide for rooting with MAGISK​==================================================
This guide is for those devices for which currently there is no custom recovery available. So, don't be sad instead have MAGISK Root for your device and and sleep well.:angel:
Note - USE THIS GUIDE ON YOUR OWN. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICES.
BETTER KNOW WHAT YOU ARE DOING AND ITS CONSEQUENCES.
==================================================
REQUIREMENTS -
1 - An Android 5.0+ device
2 - PC with working ADB
3 - Stock boot image (boot.img) of your device
4 - Magisk Manager app
5 - A good file browser like Mixplorer, Solid explorer etc..
6 - Active Internet connection
7 - Active mind and patience.
==================================================
Step 1: Patching the stock boot.img
- Install MagiskManager apk on your android device
- Copy the stock boot.img of your device to your phone's internal storage or SD card
- Launch Magisk Manager app
- If prompted to install Magisk, select NO THANKS
- If you are using a samsung device and wish to flash using Odin, then select Options > Settings > Update Settings > Patched Boot Output Format > img.tar )
- Select Install > Install > Patch Boot Image File >
Navigate to the location of the stock boot.img you copied earlier on, then Select it
-Magisk Manager should begin downloading the magisk zip file used for patching
-Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img[.tar]
Step 2: Flashing the patched boot.img
You have a variety of options to flash the patched boot.img depending on your chipset (e.g Mediatek MTK, Spreadtrum SPD, Qualcomm QLM etc ), the resources you have and your skills. Note that some flashing methods might require you to rename the file to boot.img
- For those using MTK devices and have the specific scatter file for their device, you can flash the patched boot.img using SP flash tool or Miracle Box
-For those using SPD devices and have the PAC file for their device, you can flash the patched boot.img using Research download tool by replacing the stock boot.img with your patched boot.img
- For those using Samsung devices and then use ODIN to flash.
-You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
-Setup adb and fastboot on your PC.
-Unlock the phone's Bootloader (if its not unlocked)
-Re-enable USB debugging on the phone
-Connect the phone to the PC via USB cord
-Boot into fastboot mode.
-Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
-Verify root using Root Checker
Credits goes to topjohnwu of XDA for Magisk
Also to X3non of Hovatek for original guide.

Does this work with lenovo vibe k4 note?

I think this thing would be risky to do.
Or what do you think?

Does the bootloader need to be unlocked still? I have a S6 Active (sm-g890a) that I would love to root with this method but I haven't wanted to try anything in fear of bricking. Sorry for the newb question but I'm a noob.
Sent from my SM-G900V using XDA Labs

2FrEsH99 said:
Does the bootloader need to be unlocked still? I have a S6 Active (sm-g890a) that I would love to root with this method but I haven't wanted to try anything in fear of bricking. Sorry for the newb question but I'm a noob.
Sent from my SM-G900V using XDA Labs
Click to expand...
Click to collapse
if the bootloader checks boot.img, it will fail since Magisk patches the boot.img and it will have an invalid signature.
This process is only useful for locked bootloaders that do not check boot.img or people who want stock or are stuck with stock recovery.

2FrEsH99 said:
Does the bootloader need to be unlocked still? I have a S6 Active (sm-g890a) that I would love to root with this method but I haven't wanted to try anything in fear of bricking. Sorry for the newb question but I'm a noob.
Sent from my SM-G900V using XDA Labs
Click to expand...
Click to collapse
Hi, the best way is to flash a custom recovery beforehand. But if you can't find you can go for this method but bootloader must be UNLOCKED. And also if anything goes wrong even if the bootloader is UNLOCKED , the phone will only be soft brick not hard brick. But the best thing will be a custom recovery method.

Cjoman said:
Does this work with lenovo vibe k4 note?
Click to expand...
Click to collapse
If your device bootloader is UNLOCKED, then you are good to go. But you should look for a custom recovery for your device and flash magisk.zip . Try this method only if you can't find one. Although every method is risky, you should play safe.

DE SEXIEST said:
I think this thing would be risky to do.
Or what do you think?
Click to expand...
Click to collapse
Of course this method is risky yet safe.
If you have a less secure device with UNLOCKED bootloader, you should try this.
But the best thing will be to find a custom recovery or try to port one.
This method should work on most devices.

Aquib132 said:
If your device bootloader is UNLOCKED, then you are good to go. But you should look for a custom recovery for your device and flash magisk.zip . Try this method only if you can't find one. Although every method is risky, you should play safe.
Click to expand...
Click to collapse
Okay thanks!
---------- Post added at 02:33 AM ---------- Previous post was at 02:03 AM ----------
Will this factory reset my phone?

does it work / may work with S9 plus G965U Qualcomm chipset?
as i didn't find any Oem unlock option in the developer menu.

A7 2017 (Android 8)
So i have an a7 2017 with android oreo or know as 8.0.0. So i want to flash the patched boot image with odin. How do i do that? Like i understand you need oem unlocked but where do you flash it specifically in odin?

Use ADB and the push command.. Be careful what you type.. This thing is a ***** to get the first time.. I wish you good luck
---------- Post added at 07:16 AM ---------- Previous post was at 07:10 AM ----------
Remember one other thing.. Sammy can not use Fastboot.. It's not that it's bad.. But it just won't in most cases.. Try CROM first to unlock the bootloader

Thanks, very helpful!

Well i tried to root my phone before with cf auto root and with twrp and it said device verification has failed or something. Will it happen for this device?

How do i copy the stock boot image onto my internal storage?

I'm having a question: does the new patched_boot.img file also contain my personal data? If not, then what's the best way to make a backup so that when I restore it my phone to be just like I didn't do anything to it(it should have all my apps, files,contacts, accounts etc untouched), but to be rooted? I have a Elephone a4 and I can't set up a custom recovery, that's why I want to follow this tutorial...

Pcarioca said:
I'm having a question: does the new patched_boot.img file also contain my personal data? If not, then what's the best way to make a backup so that when I restore it my phone to be just like I didn't do anything to it(it should have all my apps, files,contacts, accounts etc untouched), but to be rooted? I have a Elephone a4 and I can't set up a custom recovery, that's why I want to follow this tutorial...
Click to expand...
Click to collapse
Go to smart switch and create a backup.

Easy peezy
Works as advertised. One thing i would add to the guide is copying the patch boot img to where the command prompt window is opened. If i was using my noodle, it would be an unspoken, but i forgot and had to reboot once more. This would've saved me about 30 seconds, but i won't complain. I am on the moto z2 force sprint may 1 update with an unlocked bootloader

I think this thing would be risky to do.

emod0705 said:
Try CROM first to unlock the bootloader
Click to expand...
Click to collapse
Sir what is CROM?