Database Info

[E6853][TWRP] Root with unlocked bootloader [ABANDONED]

I created TWRP and custom kernel for Z5 Premium E6853.
I won't update this kernel since I don't have Z5P.
NOTE: This kernel is not for people who don't read official instruction at Sony Developer World!
This note is ridiculous, but some people don't read long instruction even if it has risk.
Download:
https://dl.androplus.org/Xperia Z5 Premium_E6853/
NOTE: You should search how to setup adb and fastboot.
You can find how to for unlocking bootloader on Sony Developer World.
1. Download Z5P_AndroPlusKernel_v4a.zip and twrp-2.8.7.0-E6853-20151122_material.img
You also need SuperSU from this thread
2. Enter into fastboot mode and run these commands in same folder you downloaded 1.
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp-2.8.7.0-E6853-20151122_material.img
fastboot reboot
3. Press volume key when LED is on
4. Install SuperSU zip
5. Reboot and rooting is done
If TWRP didn't work, you can alternatively do this:
Code:
adb shell
rootsh +p
./SuperSU_files/install_SuperSU.sh
reboot
Source:
Kernel -
https://github.com/AndroPlus-org/android_kernel_sony_msm8994_kitakami_r2
Device tree -
https://github.com/AndroPlus-org/android_device_sony_kitakami
https://github.com/AndroPlus-org/device-sony-satsuki

AndroPlus said:
I created TWRP and custom kernel for Z5 Premium E6853.
I won't update this kernel or create one for Dual since I don't have Z5P.
Download:
https://dl.androplus.org/Xperia Z5 Premium_E6853/
NOTE: You should search how to setup adb and fastboot.
You can find how to for unlocking bootloader on Sony Developer World.
1. Download Z5P_AndroPlusKernel_v4a.zip and twrp-2.8.7.0-E6853-20151122_material.img
You also need SuperSU from this thread
2. Enter into fastboot mode and run these commands in same folder you downloaded 1.
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp-2.8.7.0-E6853-20151122_material.img
fastboot reboot
3. Press volume key when LED is on
4. Install SuperSU zip
5. Reboot and rooting is done
If TWRP didn't work, you can alternatively do this:
Code:
adb shell
rootsh +p
./SuperSU_files/install_SuperSU.sh
reboot
Source:
Kernel -
https://github.com/AndroPlus-org/android_kernel_sony_msm8994_kitakami_r2
Device tree -
https://github.com/AndroPlus-org/android_device_sony_kitakami
https://github.com/AndroPlus-org/device-sony-satsuki
Click to expand...
Click to collapse
Hi androplus
You do awesome work I have used your kernel on the z3 before. So happy to see you helping us out. Is there any changes or things you have added to this kernel or is it just rooted?
Thanks
Sent from my E6853 using XDA Free mobile app

rx7boy22 said:
Hi androplus
You do awesome work I have used your kernel on the z3 before. So happy to see you helping us out. Is there any changes or things you have added to this kernel or is it just rooted?
Thanks
Sent from my E6853 using XDA Free mobile app
Click to expand...
Click to collapse
Some changes are added, see changelog:
https://kernel.andro.plus/kitakami_r2.html

AndroPlus said:
Some changes are added, see changelog:
https://kernel.andro.plus/kitakami_r2.html
Click to expand...
Click to collapse
Thanks, yeah I should have guessed it will be based off the z5 changlog cause basically the same except for the screen.
Sent from my E6853 using XDA Free mobile app

Thanks again

WIth the newest files worked like a charm. Thanks!

I get this
FAILD (remote: Command not allowed)
What does that mean??

Thanks for the great job, did you have any side-effect ?

Have anyone guys the S1 Fastboot driver for my Z5P and me
---------- Post added at 03:09 PM ---------- Previous post was at 02:49 PM ----------
Ok, i Found the S1 driver and download it, but when i will install the driver, aborts the installation( installtion error)
My Os is Windows 10 64 bit

Jacob_Bentzen said:
I get this
FAILD (remote: Command not allowed)
What does that mean??
Click to expand...
Click to collapse
you have to unlock your bootloader first

I really need that first? I didn't need that with my LG G4

Ok i have install S1 driver, but i have the same problem as Jacob_Bentzen(FAILD (remote: Command not allowed))

You really should read instruction on Sony developer world...
If you don't read carefully, your device will be bricked.
Please don't use my kernel and TWRP if you don't want to read long instruction.

Great stuff - Followed Exactly and I have an unlocked BL, am rooted with TWRP! Yes, hopefully some development occurs...

Works great! Thanks!

Amazing been waiting to root for so long
This is cool thanks a massive bunch
I will be rooting and flashing the recovery after work.
One question, will I still get Xperia updates for the sony rom after I have rooted and will my phone be wiped after u locking bootloader and flashing recovery ?

Unlock
Hi
to unlock Sony Z5 bootloader go to: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Follow ALL instructions carefully!
Cheers
Aussie

Is there a way with closed BL to root??
I will not lost my DRM Keys

get2easy said:
Is there a way with closed BL to root??
I will not lost my DRM Keys
Click to expand...
Click to collapse
Not yet

Gentle Jesus said:
This is cool thanks a massive bunch
I will be rooting and flashing the recovery after work.
One question, will I still get Xperia updates for the sony rom after I have rooted and will my phone be wiped after u locking bootloader and flashing recovery ?
Click to expand...
Click to collapse
Any one know ?

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?

[ROM] MCG24.251-5 100% Stock

Flash using TWRP. This will flash all files in the MCG24.251-5 update except for recovery.
New features in this update that I've noticed:
-Marshmallow, aged to perfection in Verizon's own servers. Only one major release version obsolete, and with outdated security patches!
-WiFi calling (woooooo! Those custom roms just got another carrier-specific, unportable feature to compete with)
-The command center widget has been replaced with the Droid Turbo 2 version
Get it here: https://mega.nz/#!G1xg1aYa!fm2hUL7hDDVaxTAj_iPbtY61P-8VrQEvoOJiVsDtdho
Here's the stock recovery image if you want it: https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Flashing this rom updates the bootloader to a version that can communicate with the kernel to tell SafetyNet that it is unlocked, causing it to fail. Fret not, however, as there are two options to fix this:
OPTION 1: Flash the SU4TL-49 bootloader using the following TWRP package: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
OPTION 2: Flash this patch made by @bhb27: https://www.androidfilehost.com/?fid=745425885120696423
Wipe cache and dalvik/art cache after either of these options.
NOTE that these options only fix failures due to SafetyNet checking the bootloader status. It will still fail due to root, xposed and the like. There are no known consequences or side effects to either of these options, so just pick whichever one you feel like.
If you notice weird things after you flash this rom (long boots other than the first one which is supposed to be long, random reboots, etc.) try flashing the stock recovery image and factory resetting.
If you want root, flash this version of SuperSU first, then flash whatever newer version you want: https://download.chainfire.eu/751/SuperSU/
If you have trouble flashing this, try TWRP Mod 3 instead of Mod 4.

Ouch, you have almost full flash inside archive, with bootloader too... Who is the most brave, introduce yourself ))
+ mirror

I can confirm that it works on old bootloader.
I had SULT-49 5.1 installed before and I just flashed this via TWRP. I haven't taken the OTA. It works perfectly. Thank you.
PS: My bootloader now is moto-apq8084-70.95 (2016-06-29). Do you have same version after taking OTA?

Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk

Thanks OP

rickyblaze13 said:
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
When in doubt, always wipe.

Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.

rickyblaze13 said:
have to wipe the system, data and cache first
Click to expand...
Click to collapse
It works w/o, but, IMO, better wipe, than not. You don't need extra bugs, right )

It's completing setup now, I did a wipe after I backed up my phone. It's unlocked and rooted before I flashed the zip
Sent from my QMV7A using Tapatalk

Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...

Crowick said:
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Click to expand...
Click to collapse
My google drive is full and I don't have Dropbox. But if you wanted to mirror it, I will gladly add the link to the OP.

Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg

Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
thanks for gdrive mirror

Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
I don't. I don't know how I would get it since I need root access to get it, and I can't get root access without TWRP, and I have to overwrite the stock recovery to get TWRP.

TheSt33v said:
I have to overwrite the stock recovery to get TWRP.
Click to expand...
Click to collapse
fastboot boot TWRP.img

s5610 said:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Nice! Good call.
https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8

Is anyone else having exceptionally long reboot/start times for their phone after flashing this rom?

Just the first boot after flashing
Sent from my XT1254 using Tapatalk

Thanks for that! Did anybody try to install it right over SU4TL-44? Just in case, I'm rooted, using xposed and twrp.

TheSt33v said:
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
Click to expand...
Click to collapse
Perhaps this:
https://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
I just tried using AP a few hours ago and it failed with the screen in the article. OTA with unlocked bootloader.

SM-S550TL - Recovery, Testing, Misc

This thread is for whoever wishes to contribute to the development of this particular model, (Galaxy On5), Any and all help is appreciated!

As per request, I unpacked the stock recovery, repacked it, and attempted to flash it through odin. The result was "failed", on the odin side, but the device did not say anything, (This was in download mode).

hydroman202 said:
This thread is for whoever wishes to contribute to the development of this particular model, (Galaxy On5), Any and all help is appreciated!
Click to expand...
Click to collapse
Upload the boot image so I can compile it.

[email protected] said:
Upload the boot image so I can compile it.
Click to expand...
Click to collapse
I would, but all I have is the recovery img. How I got that was from another user who got the firmware. I will ask him to see if he can send me the boot img.

hydroman202 said:
I would, but all I have is the recovery img. How I got that was from another user who got the firmware. I will ask him to see if he can send me the boot img.
Click to expand...
Click to collapse
OK I have not compiled TWRP with a recovery before so just to be safe I use a boot image. I just split it with Mkboot tools and replace the images in the device tree source code made for the T-Mobile/Metro version.
---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------
hydroman202 said:
As per request, I unpacked the stock recovery, repacked it, and attempted to flash it through odin. The result was "failed", on the odin side, but the device did not say anything, (This was in download mode).
Click to expand...
Click to collapse
The build prop has to match in order for it to work. Upload the boot image and I can work on it.

Deleted

[email protected] said:
https://www.mediafire.com/folder/u6vvauz8i30z0/SM-S550L
Test image. Make sure to backup your recovery before you flash this. Use Odin and in the options tab uncheck auto reboot. Once flash is complete pull out the battery and put it back in. Holding volume up button and the home button and power until you get into recovery. Only people who knows what they are doing so we don't have bricks. I used the device tree source code made for T-Mobile/Metro and used the DT image and kernel from an extracted boot image.
Click to expand...
Click to collapse
It's pointless at the moment even compiling custom recovery for this device as it won't flash.
It seems this device has a locked bootloader.

Well it compiled with no problem with the Metro version all you do is enable development settings and select OEM unlock and USB debugging. I didn't have to use ADB for "fastboot OEM unlock". So I don't know. Thanks for the heads up.

[email protected] said:
Well it compiled with no problem with the Metro version all you do is enable development settings and select OEM unlock and USB debugging. I didn't have to use ADB for "fastboot OEM unlock". So I don't know. Thanks for the heads up.
Click to expand...
Click to collapse
Compiling isn't the issue, it's the fact the image is unsigned. There are no special headers I can see in the stock recovery image, which could cause the issue, so it seems purely down to the bootloader being locked down.
Also regarding OEM unlock and USB debugging.
It isn't and never has been required to enable usb debugging to flash a recovery.
I know this is incorrectly posted all over the Internet, but usb debugging is purely an OS dependent operation and has no use outside of a booted OS.
We are looking at alternative ways, but options are extremely limited.

I took the link down. Thanks.
---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------
Also check out the boot image. It's identical to the T-Mobile Metro version. Would you be able to test it out?

[email protected] said:
I took the link down. Thanks.
---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------
Also check out the boot image. It's identical to the T-Mobile Metro version. Would you be able to test it out?
Click to expand...
Click to collapse
I dont own the device I'm just chipping in.
Where did you get the boot image, is it for the S550TL?

ashyx said:
I dont own the device I'm just chipping in.
Where did you get the boot image, is it for the S550TL?
Click to expand...
Click to collapse
Yes it's for the S550L @hydroman202 gave it to me so I split it with Mkboot tools and compiled.

[email protected] said:
Yes it's for the S550L @hydroman202 gave it to me so I split it with Mkboot tools and compiled.
Click to expand...
Click to collapse
That was the recovery image I sent him wasn't it?

It said boot image so I split it and compiled it as on5ltetfntmo

Does anyone know how to perform "oem unlock" without fastboot? Every time I try to access it, it reboots back into the normal os.

hydroman202 said:
Does anyone know how to perform "oem unlock" without fastboot? Every time I try to access it, it reboots back into the normal os.
Click to expand...
Click to collapse
You need to enable it in developer settings.
What was the image you sent to [email protected]?

ashyx said:
You need to enable it in developer settings.
What was the image you sent to [email protected]?
Click to expand...
Click to collapse
The image i sent him was the boot img from my device, which i found somewhere on the internet, (i don't remember where, i had done A LOT of googling), but i was lucky enough to find it. sorry i cant remember the exact site.

hydroman202 said:
The image i sent him was the boot img from my device, which i found somewhere on the internet, (i don't remember where, i had done A LOT of googling), but i was lucky enough to find it. sorry i cant remember the exact site.
Click to expand...
Click to collapse
Just the boot.img you found or the whole firmware?

also, i have been trying to find ways to unlock the bootloader of this device, but all of the methods i have found require root or fastboot. Do you have any ideas on how i might achieve root?

ashyx said:
Just the boot.img you found or the whole firmware?
Click to expand...
Click to collapse
I wish i had the whole firmware, but it was just the boot img. I was pretty sure it was the right one, but i might have been mistaken.

November 2019 security update is now available

83.7MB
Installation without any troubles. No major changes. d2tw still not working.

Nothing to say

My device gives an error when i try to install.
Says: Failed to install update, tap here for more information.
When i tap, there is no 'more information' !
Stupid Android!

Install and nothing change, still have problem on sim1, when turn on data on sim1 i lost network.

perfect_ said:
My device gives an error when i try to install.
Says: Failed to install update, tap here for more information.
When i tap, there is no 'more information' !
Stupid Android!
Click to expand...
Click to collapse
Same Problem With My Device.
Anyways, Solution Is Here...
1st We Need To Unlock Bootloader Then Flash Currently Available Stock Rom Through MI Flash Tool.
Thanks,
MUHAMMAD Asif Qasim

perfect_ said:
My device gives an error when i try to install.
Click to expand...
Click to collapse
If the OTA fails, you can find out which partitions it doesn't like from the logcat. If you have a fastboot image, you can reflash the affected partitions. I have had to restore both system.img and vendor.img since 10.0.10.0 (the fact that I've been using a custom bootanim definitely does not help).
Code:
adb logcat | grep update_engine

a1291762 said:
If the OTA fails, you can find out which partitions it doesn't like from the logcat. If you have a fastboot image, you can reflash the affected partitions. I have had to restore both system.img and vendor.img since 10.0.10.0 (the fact that I've been using a custom bootanim definitely does not help).
Code:
adb logcat | grep update_engine
Click to expand...
Click to collapse
Hello Dear,
Can You Guide Stepwise How To Fix Partition ? I Do Not Want To Unlock The Bootloader Or Flashing The Stock ROM. I Just Want To Fix Issue That Causing The Update.
In Addition to That My Device Is Updated aon Last October.
Your Help Will Be Highly Appreciated In This Regards.
Thank You In Advance

aasiaasi said:
Can You Guide Stepwise How To Fix Partition ? I Do Not Want To Unlock The Bootloader Or Flashing The Stock ROM. I Just Want To Fix Issue That Causing The Update.
Click to expand...
Click to collapse
I'm used to flashing from fastboot but I'm pretty sure that only works with an unlocked bootloader. I've read that you can use miflash with a locked bootloader but you need a complete rom and the most recent one is 10.0.13.0
Sorry

a1291762 said:
I'm used to flashing from fastboot but I'm pretty sure that only works with an unlocked bootloader. I've read that you can use miflash with a locked bootloader but you need a complete rom and the most recent one is 10.0.13.0
Sorry
Click to expand...
Click to collapse
Thank You For Time And Reply.
OKay What Should We Do To Fix The (Partition) Problem. ? Complete Stepwise Guide Will Be Beneficial To Us.
One More Question.
Is There A Way To Get Every Month OTA Installed Without Interrupting (Unlock Bootloader , Rooted With Magisk) ? If Yes , So What Could Be The Steps/Guide.
Thanks.

aasiaasi said:
Is There A Way To Get Every Month OTA Installed Without Interrupting (Unlock Bootloader , Rooted With Magisk) ? If Yes , So What Could Be The Steps/Guide.
Click to expand...
Click to collapse
If you just have Magisk, this is all you should need to do.
https://forum.xda-developers.com/mi...ll-magisk-proper-support-ota-t3836952/page100
If you have other stuff that breaks that process (eg. Magisk + TWRP) then you need extra steps.
https://forum.xda-developers.com/mi...to-10-0-7-0-ota-keeping-magisk-t3916863/page9
---------- Post added at 12:23 AM ---------- Previous post was at 12:13 AM ----------
aasiaasi said:
OKay What Should We Do To Fix The (Partition) Problem. ? Complete Stepwise Guide Will Be Beneficial To Us.
Click to expand...
Click to collapse
Previously you said you did not have an unlocked bootloader, but you asked for OTA instructions with Magisk...
Since you don't have backups of the modified partitions, you should backup your data then install 10.0.13.0 from fastboot image. This is the only option if your bootloader is locked (I think that miflash allows this?)
If you are modifying your device I'd suggest backing up the partitions that were rejected by the upgrade (logcat). See the advanced guide I posted for details.
If you have backups you just need to restore the partitions the upgrade is complaining about (logcat).