Develop Bugs

[Q] BL locked on Xperia ZL. 4.4.4 - 0.292 - What are my options?

Hello,
I have a Xperia ZL C6506 with a locked bootloader. I would like to unlock it, or at least root the phone.
Bootloader unlock allowed: No
Android 4.4.4
Kernel version: 3.4.0-perfg1bb39c2
Build Number: 10.5.1A.0.292
Country: Canada
Flashtool will not root the phone, even trying Towelroot V3.
Seems like every answer I find on XDA says something about my phone is always stopping me. Either 4.4.4 is a problem, or BL locked, or 0.292, I can't root... What am I missing?
Do I have to flash a new kernel or rom? Is it even safe to flash anything, even if it is stock, on a phone with a locked bootloader? I do not want to brick.
Thanks in advance for your help!

I found this forum: http://forum.xda-developers.com/xperia-zl/help/rooting-xperia-zl-t2994781
But,
I read this: http://forum.xda-developers.com/xperia-z1/development/newroot-z1-t2807092 it says: "Newroot work with all kitkat firmwares but doesn't work with latest kitkat *after 108) .133, .157... firmware or with old JB firmwares!!!"
This is the only thing that I have found that I have not tried, but I am hesitant to try and flash an old kernel on a phone with a locked bootloader. Is it safe to flash anything on a locked bootloader?

Himura357 said:
I am hesitant to try and flash an old kernel on a phone with a locked bootloader. Is it safe to flash anything on a locked bootloader?
Click to expand...
Click to collapse
Yes, it is safe, as long as you know what you are doing. Put it this way: flashing the downgraded kernel will not screw you up, but doing things the wrong way might.
1. Download this. It's NOT a flashable zip! Just unzip it, and use FTF files to flash the appropriate kernels.
2. Read my post that you linked. It gives you all the steps of the process. Installing recovery is optional, but highly recommended (very useful). Use the kernels you downloaded from my link above.
That's it! A couple of notes...
- I am assuming you know how to use the FlashTool. Not the original one from Sony, but the the one by Androxide. Make sure you are familiar with it before flashing!
- Newroot DOES work with .230 kernel. I have done it many times while playing with different ROM versions, works perfectly. Make sure you enable USB debugging, and watch your phone for prompts to grant access. Your phone should reboot after successful rooting. If for some reason it doesn't work, just try again.
- When you flash .230 kernel, you may have some weird issues with your phone. You will lose WiFi. Your phone may start vibrating for no reason (mine did). Maybe something else, I dunno... Don't worry, it's only temporary. Everything will get back to normal once you flash .292 kernel after rooting. Again, tried and proven fully working many times.
- If you decide to upgrade to LP afterwards, this will also be your procedure to recover, if you screw something up in the process (been there, done that). Just flash your .292 stock ROM, then repeat the rooting process, then start with LP over again.
Happy rooting!

Thanks so much. It is crystal clear now. Always good to get some advice from someone who has done it before on the same phone.

Trying to flash and I got this error (attached pic)
I am running the newest flashtool. I didn't have any problem with the older flashtool in the past when I used to flash my older phones. Also, the older one installed completely in one folder, this one installs in 2 folders, one in C: and the other in C:/users/Me for some reason.
I installed the V1.5 driver package. Not sure what else is wrong. I unzipped the zip file, put the kernel.only.ftf into the firmwares folder, I clicked flash, selected the .ftf file and connected the phone in flashmode. No dice.

Ok, tried it again, this time it didn't get a red error, I got a different one, and my build number is still 10.5.1.A.0292...
Installed recoveries.
Pic is attached.

Okay!
So, after the first flash, the build number didn't change, but the kernel was applied. I just tried using newroot and it worked, superuser is there. Just like you said, the wifi stopped working with the new kernel. I flashed the 0.292 kernel and the wifi came back, and the phone is still rooted.
Thanks for you help kt-Froggy!

Himura357 said:
Okay!
So, after the first flash, the build number didn't change, but the kernel was applied. I just tried using newroot and it worked, superuser is there. Just like you said, the wifi stopped working with the new kernel. I flashed the 0.292 kernel and the wifi came back, and the phone is still rooted.
Thanks for you help kt-Froggy!
Click to expand...
Click to collapse
Good to know! Cheers!

Need help/suggestions on how to flash ArchiDroid on an untouched/stock XperiaM

Hi guys, been following this awesome community for a while now. I got a OnePlus One and I managed to unlock/root it thx to a thread on this forums (even if I'm not that "pro" with phones), but now I have my father's Xperia M (which has never been unlocked/rooted/flashed or anything) that is updated to Android 4.3 and I need help on how to proper install a custom ROM on it (I'm interested in the ArchiDroid one in particular). I don't like Sony's stock ROM, it's acting badly on some things (video recording for example) and in general it just sucks imho, so I want to upgrade to a custom Lollipop one (ArchiDroid). Can someone kindly explain me all the initial steps I have to take to, at least, install a custom recovery on the phone (possibly the TWRP since I used it for the OPO aswell)? Do i need to unlock the bootloader or something? Thx a lot!

Yes, u need to unlock your bootloader.U can do it through fastboot mode.Detailed information is available on Official Sony's Developer world page. Then flash custom recovery like cwm or twrp.Finally download the zip file and start flashing it.

Yep I managed to do all the stuff just yesterday, but thx anyway! Although it was not easy AT ALL, took me all day and was just a nightmare lol. The phone went immediately in bootloop after unlocking the bootloader, so I had to flash an appropriate firmware with flashtool, and I even had a problem at the very end of the process while trying to install the ROM itself (I choosed the official stock CM 12.1 nightly btw), because CWM was giving a stupid error. Thank god a guy here on the forums reported that CWM has problems with some SDs and posted a method to solve them all (by doing a total format of the SD with a program called SDFormatter).

3ullit87 said:
Yep I managed to do all the stuff just yesterday, but thx anyway! Although it was not easy AT ALL, took me all day and was just a nightmare lol. The phone went immediately in bootloop after unlocking the bootloader, so I had to flash an appropriate firmware with flashtool, and I even had a problem at the very end of the process while trying to install the ROM itself (I choosed the official stock CM 12.1 nightly btw), because CWM was giving a stupid error. Thank god a guy here on the forums reported that CWM has problems with some SDs and posted a method to solve them all (by doing a total format of the SD with a program called SDFormatter).
Click to expand...
Click to collapse
yes, cwm recovery for now is not good for daily use. because they still have old commit. i suggest you to change to TWRP recovery, try look at here http://forum.xda-developers.com/showpost.php?p=61626285&postcount=1 we've got official support for this recovery:laugh:

Recoveryproblems after Android 6.0 Update

Hello,
some days ago I've installed Android M.
If i try to boot recovery now i just get the dead droid.
~5 Mins later it just reboots to normal mode.
Flashing TWRP didn't help
Any suggestions - never had something like this before?

J3n50m4t said:
Hello,
some days ago I've installed Android M.
If i try to boot recovery now i just get the dead droid.
~5 Mins later it just reboots to normal mode.
Flashing TWRP didn't help
Any suggestions - never had something like this before?
Click to expand...
Click to collapse
did you installed Android M on Verizon device?

ajeevlal said:
did you installed Android M on Verizon device?
Click to expand...
Click to collapse
No. updated with LG Bridge (h815)

J3n50m4t said:
Hello,
some days ago I've installed Android M.
If i try to boot recovery now i just get the dead droid.
~5 Mins later it just reboots to normal mode.
Flashing TWRP didn't help
Any suggestions - never had something like this before?
Click to expand...
Click to collapse
TWRP requires an unlocked bootloader which the VS986 (Verizon G4) has not been able to do. I saw a thread somewhere about installing MM on any G4, but figured I could wait a while and be happy with 13B. What software version were you BEFORE installing 6.0 MM? Can you not go back to 13B by placing a system image on your phone and flashing that in recover/command mode? I have not read much about what MM does with your kernel/bootloader, so DEFINITELY check that before you think about going back to 5..1 LG has anti-rollback stuff backed in that can brick your phone if you try going to a previous version, but not sure how the 6.0 MM flash handles that.
Edit: Well, that answers that question, not a Verizon phone. lol.
Which H815 version do you have? VERY IMPORTANT because not all H815 are made the same. Depending on the region is what determines if you can actually unlock your bootloader.

woozzy101 said:
TWRP requires an unlocked bootloader.
Click to expand...
Click to collapse
Bootloader is unlocked. Had 5.1 before with TWRP & Co. working.
The CM Wiki is exactly what I did. Installing Android 6 and then flashing recovery with adb.
Can't link due newbie but cyanogen wiki /w/Install_CM_for_h815

Now tried to boot directly into recovery after flashing.
I'm just getting the Stock recovery after a sucessful flash of twrp?

Z5 e6883 root

Hello all
I've been watching the forum for years now and I admit there are plenty of nice guides ( I even rooted my z3 dual first try using the guides)
Now I have purchased Z5 premium dual e6883 model and it's been sitting in the box for almost 2 months now, waiting on a root guide
Most of the guides are either for different models like e6853 or for experts who are into testing and experiencing options
I know there are successful attempt to root this model so I ask if there is any comprehensive (complete) guide on how to get the root for this device?
I would appreciate if anyone can refer to a post or even a guide that I can follow
Model 6883
Android 5.1.1
Build 332.0.A.6.170
Karnel 3.10.49-perf-g9a3c9a8-04532-g75e6207
Many thanks for all the support

Any help please?

I think the first thing that you want to know is, currently you can't root without your bootloader unlocked.
(Please Google search for more details regarding the "side effects" of the unlocked bootloader Sony smartphones, though tobias.waldvogel has created the DRM functions restoration mod.)
My advice, why don't you wait until Android 6 rolls out? Maybe more developers would focus on the latest ROM and bring out various ROOT methods (for unlocked bootloader and locked bootloader maybe?)
I wanted to ROOT my Z5 premium dual since the first day I bought it, but it is a sad thing to lose the DRM keys (my opinion), and unless the DRM functions restoration mod becomes "better", I will not unlock my bootloader just yet...

Novioo said:
Hello all
I've been watching the forum for years now and I admit there are plenty of nice guides ( I even rooted my z3 dual first try using the guides)
Now I have purchased Z5 premium dual e6883 model and it's been sitting in the box for almost 2 months now, waiting on a root guide
Most of the guides are either for different models like e6853 or for experts who are into testing and experiencing options
I know there are successful attempt to root this model so I ask if there is any comprehensive (complete) guide on how to get the root for this device?
I would appreciate if anyone can refer to a post or even a guide that I can follow
Model 6883
Android 5.1.1
Build 332.0.A.6.170
Karnel 3.10.49-perf-g9a3c9a8-04532-g75e6207
Many thanks for all the support
Click to expand...
Click to collapse
keep waiting.. I received 6.0.1 ota on an amazon z5p e6883. The phone worked famously.. .loved it.
Some compulsive and sick part of me wanted to root the phone.. no good reason.. the phone worked perfectly.
I didn't research enough to know that unlocking the bootloader wipes drm keys.. (my hastiness there, no one to blam)
I unlocked the bootloader -
Followed a few guides on this site (full of some knowledgeable folks, but most are tards.. including the site designer who decided to fill the site with shockwave flash ads..WTF)
I can safely say, NONE of the guides worked on this model.
So I've got no rooted phone, but lost DRM keys, so lost phone functionality.
Here's my understanding of the procedure, asuming the obvious.. you have fastboot, flashtool and adb all working
1. unlock bootloader
2. get modified 'premissive' kernel (there are a couple flying around.. I tried both Z5PDual_AndroPlusKernel_v5b.zip, and E6883_MM_ROOTABLE_PERMISSIVE_boot.img during different attempts..
3. get twrp (I tried both twrp-2.8.7.0-E6883-20151130_material.img and twrp-3.0.2-0-E6653-20160504.img. on different runs)
4. flash boot with permissive or andro plus
6. flash recovery with 2.8 or 3.0 twrps
7 reboot and watch You'll see the sony banner then yellow led... Press and hold vol down during yellow led)..
8. Blam. you're in twrp.. All good right.. time to install su.zip or su and drm repair zip...
gravy right..
not for me..
my phone doesn't boot at any point after this point. The OS starts, but I get either a continuous animated 'sony waves' banner OR Android is Starting.. starting apps. (I've waited a long time for this to progress but did not make it to OS..
My recovery..
Flash tool 9.0.22
Sony Xperia Z5 Premium(E6883). FW release : 32.2.A.0.224_R6C. Customization : India Generic_1299-6238
After this, I'm back in business, but without unlocked bootloader and no DRM keys or patch..
during debugging I tried several combinations and found that the OS will not boot after these two modified kernels are pushed
AND twrp won't install without the modified kernel
Would be appreciate if someone could guide me through this, without saying "did you unlock your boot loader..?"
Otherwise, I'd suggest taking that phone out of the box and using it stock.. it's a great phone.
giz

I'm going to side with Giz on this one. Take the phone out of the box and use it without trying to unlock the bootloader. It is a nice phone and the camera is pretty awesome as long as your DRM keys are intact. I'd love to unlock my bootloader too so I could root the phone but I'm not willing to loose some functionality to do so. One thing that really annoys me is those 2 worthless SIM card icons in the tray. They are worthless. All we need are the signal icons. Anyway that's my .02.

foopy said:
I'm going to side with Giz on this one. Take the phone out of the box and use it without trying to unlock the bootloader. It is a nice phone and the camera is pretty awesome as long as your DRM keys are intact. I'd love to unlock my bootloader too so I could root the phone but I'm not willing to loose some functionality to do so. One thing that really annoys me is those 2 worthless SIM card icons in the tray. They are worthless. All we need are the signal icons. Anyway that's my .02.
Click to expand...
Click to collapse
Pardon the pun, but I think I found the "root" of the problem ... at least for myself anyway..
this is for those who *HAVE* unlocked the boot loader.
I couldn't get my 6.0.1 phone (32.2.A.0.224) rooted. I've got the E6883 Dual Sim.
To recap:
I've Unlocked
I've downloaded E6883 MM Permissive Kernel
I've Downloaded E6533 TWRP
What happens after this is that my phone will not ever boot. It just hangs on the animated xperia waves screen.
My Fix is to reflash with flashtool
During Flash AFTER installing the permissive kernel I noticed that the flash tool detected a .163 build number. I thought this was odd because I just flashed to .224
I believe the issue is that the 6883MM permissive boot loader (required to install twrp) was built from a 163 kernel AND the boot loader is not compatible with the system flash that loads up.
I believe all that is required for root on 6.0.1 is a new 6883MM permissive (built using a .224 parent).
Does any of this theory hold any water?

This thread has helped me for E6853 http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
The procedure supports E6833/E6853/E6883 models.

try to downgrade to backup TA, with firm .209 5.1.1 china and had problems,i not to wipe downgrade .. I used xperi firm for download.the cell begins with many errors , xperia z5 premium e6883, i found firm .209 Malaysian but flashtools show firm Z5 normal to flash, I downloaded and blog xperia same name e6886

@Novioo , i have E6833, on 6.0.1 ,,,, build .224
when you were on 5.02 and 5.1.1, KINGROOT can root it EASILY,
however 6.0 , 6.0.1 onwards there is no known xploit (yet)
so i rooted via replacing stock kernal with MODIFIED KERNAL
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
if you are ready to UNLOCK you BOOTLOADER then download your modified kernal from
https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!ngpAhbSL
---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------
danilo_scala said:
try to downgrade to backup TA, with firm .209 5.1.1 china and had problems,i not to wipe downgrade .. I used xperi firm for download.the cell begins with many errors , xperia z5 premium e6883, i found firm .209 Malaysian but flashtools show firm Z5 normal to flash, I downloaded and blog xperia same name e6886
Click to expand...
Click to collapse
downgrading did not work with me also,,,,, malaysian version keeps crashing

YasuHamed said:
@Novioo , i have E6833, on 6.0.1 ,,,, build .224
when you were on 5.02 and 5.1.1, KINGROOT can root it EASILY,
however 6.0 , 6.0.1 onwards there is no known xploit (yet)
so i rooted via replacing stock kernal with MODIFIED KERNAL
http://forum.xda-developers.com/z5-premium/general/32-1-1-185-stock-modified-kernel-t3355369
if you are ready to UNLOCK you BOOTLOADER then download your modified kernal from
https://mega.nz/#F!KwZhjLIK!uNbDzR6lCXMaaW7jKFS1WQ!ngpAhbSL
---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------
downgrading did not work with me also,,,,, malaysian version keeps crashing
Click to expand...
Click to collapse
@YasuHamed you downgrade wipe all?, i no and have problem with firm china .209, malaysian i found to my xperia premium e6883 but in flashtools show to z5 normal, strange I was afraid to flash, i dont no if bug flashtools

giz02 said:
Pardon the pun, but I think I found the "root" of the problem ... at least for myself anyway..
this is for those who *HAVE* unlocked the boot loader.
I couldn't get my 6.0.1 phone (32.2.A.0.224) rooted. I've got the E6883 Dual Sim.
To recap:
I've Unlocked
I've downloaded E6883 MM Permissive Kernel
I've Downloaded E6533 TWRP
What happens after this is that my phone will not ever boot. It just hangs on the animated xperia waves screen.
My Fix is to reflash with flashtool
During Flash AFTER installing the permissive kernel I noticed that the flash tool detected a .163 build number. I thought this was odd because I just flashed to .224
I believe the issue is that the 6883MM permissive boot loader (required to install twrp) was built from a 163 kernel AND the boot loader is not compatible with the system flash that loads up.
I believe all that is required for root on 6.0.1 is a new 6883MM permissive (built using a .224 parent).
Does any of this theory hold any water?
Click to expand...
Click to collapse
I haven't unlocked my bootloader or attempted to root the phone so I don't have any experience to go on for this particular phone. I do know that sometimes you have to do a factory reset even though you have just flashed a new kernel and/or system image. If you haven't done so you might try that. Also keep in mind after a factory data reset the phone usually takes considerably longer to boot up than normal the first time so be patient. There is a thread that contains a modified .224 kernel so make sure you are using that one and not the .163. After flashing everything and BEFORE first boot perform a factory data reset in recovery and see if that makes a difference.

danilo_scala said:
@YasuHamed you downgrade wipe all?, i no and have problem with firm china .209, malaysian i found to my xperia premium e6883 but in flashtools show to z5 normal, strange I was afraid to flash, i dont no if bug flashtools
Click to expand...
Click to collapse
@Novioo i tried downgrading but could not find right version for E6833. Malaysian version kept crashing.
later i found stock modified roms for E6833 so i made deal with the devil and gave up my DRM KEYS by unlocking the boot loader,,,, but since the stock modified kernal has DRM Stimulation it works fine...
in my views, sooner or later, with or without DRM KEYS restored, you will be unlocking your boot loader anyway!
Z5 deserve to be FREED

i found this firm but in flashtools show to z5 and no premium, i dont no if bug http://www.xperiablog.net/forum/res...dual_e6883_32-0-a-6-209_malaysia_generic.519/

foopy said:
I haven't unlocked my bootloader or attempted to root the phone so I don't have any experience to go on for this particular phone. I do know that sometimes you have to do a factory reset even though you have just flashed a new kernel and/or system image. If you haven't done so you might try that. Also keep in mind after a factory data reset the phone usually takes considerably longer to boot up than normal the first time so be patient. There is a thread that contains a modified .224 kernel so make sure you are using that one and not the .163. After flashing everything and BEFORE first boot perform a factory data reset in recovery and see if that makes a difference.
Click to expand...
Click to collapse
Just wanted to say thanks for taking the time for the response.
I did try the factory reset, then let the phone sit overnight on one occasion, but to no avail.
It turns out that there was a parallel thread using the modified 224 kernel that got me much futher along, but I had other issues with is, so I ended up rolling back to the 163 build on 6.0.0 with root and drmfix. I'll look again once in a few weeks I think. I took the time to get my phone set up again, at least this time I have root and the luxury of running titanium.. such a pain to get everything manually installed and configured.

Warranty problem: Flashing to stock Nougat from a custom Pie rom

Hi folks,
I searched the forum and did not find a suitable thread that answered my question.
My Moto G5 has a charging problem and I want to give it back for a repair - it still has warranty.
I have read that flashing a custom rom does not necessarily invalidate the warranty, but to ensure that Motorola will repair the phone I would like to flash a stock (nougat) rom.
Is it possible without the risk of losing IMEI or other stuff?
Or do you recommend to send it back to Motorola with the custom rom installed?
Thank you VERY MUCH in advance!!!
Kind regards
Wolf

They will be able to see you have unlocked the bootloader regardless of whether you re-lock it
Just download the latest stock firmware and flash it via fastboot
If your base firmware is already oreo you can skip flashing gpt and bootloader to avoid risking hard brick
Don't downgrade your base firmware eg if it's oreo don't flash nougat (base firmware is stock firmware not custom rom)
I would flash it back to stock rom so at least they can't blame custom rom

Thanks!! I'm not sure, if it was delivered with Android 7 or 8. But I can flash 8 in any case, because its no downgrade?
And a last question: can I flash it also with TWRP? It's installed anyways...

moped2000 said:
Thanks!! I'm not sure, if it was delivered with Android 7 or 8. But I can flash 8 in any case, because its no downgrade?
And a last question: can I flash it also with TWRP? It's installed anyways...
Click to expand...
Click to collapse
Yes flash android 8 - note if it was never updated to android 8 you will also have to flash gpt and bootloader as well the rest of the firmware
You will need to flash the firmware via fastboot
Flashing via twrp is just like flashing a custom rom with no modifications & you will still have twrp installed and not stock recovery & still have a modified system partition etc

Thanks! Android 8 was definitely installed, only possibly not as stock firmware, but only as custom rom.
But I guess it's okay if I just flash all the files to make sure?

Motorola says, I have lost my warranty because I have opened the bootloader. They won't even fix it for money ****.

moped2000 said:
Motorola says, I have lost my warranty because I have opened the bootloader. They won't even fix it for money ****.
Click to expand...
Click to collapse
Depends what country you are in
In America or Europe you can argue and would most likely win in court that if your issue is totally unrelated to the unlocking of the bootloader they must repair it
Eg if the camera doesn't work because of a faulty component they must fix it
However if the camera stop working because you unlocked the bootloader & did some modifications causing it to no longer work then you're not covered
This would be the same for boot issues - If your phone no longer boots and you have unlocked the bootloader they can claim you have done a modification that now stops it booting
The general rule is if you unlock the bootloader than software/firmware booting issues are not covered but hardware faults unrelated to a bootloader unlock are
Again it varies depending on your country but the above is true for USA & the majority of Europe (EU)