Develop Bugs

Stuck in wrong build??

Several months ago I purchased the nexus 7 2013 wifi version. In my tiredness after a long day I unlocked, rooted then flashed a custom rom (aokp) my build numbers is KVT49L instead of KVT49H. I must have flashed the LTE version in error.
I'm trying to upgrade from 4.4.2 to 4.4.4. Wugfresh toolkit doesn't work, also unfathomables tool won't work either.
I have been rooting, swapping kernels, unlocking bootloaders and flashing custom since the Droid x days.
I assume I need to use ADB? I am having a hard time finding specific instructions on how to complete this minor upgrade to 4.4.4. In afraid to try anything being on the build for a different version of my device.
any suggestions are appreciated.
I apologize in advance if I left out any critical info regarding my situation.
Edit:
Also are the tool kits not working because I'm on the incorrect build?

K... so, does anyone have any thoughts about just flashing KVT49H rom over what I have?

mtnbst said:
K... so, does anyone have any thoughts about just flashing KVT49H rom over what I have?
Click to expand...
Click to collapse
Why isn't the toolkit working with flash stock and unroot? You should be able to select the option that says it is in a boot loop... And for current version, you can select anything you want - that is what it will flash when you do the flash stock and unroot.
If that doesn't work, where specifically does it fail?
Mike

It goes into bootloader mode and does not come out. Toolkits worked fine on N7 v1. I am attempting to un root and revert to stock.

mtnbst said:
It goes into bootloader mode and does not come out. Toolkits worked fine on N7 v1. I am attempting to un root and revert to stock.
Click to expand...
Click to collapse
Toolkit works on v2 as well. When you do the flash stock and unroot, you have to select the option that says your phone is soft bricked.
If that doesn't work, when you are in the bootloader, are you at least able to use the volume buttons and power to select recovery?

Thanks Mike, I'm going to try that
Thomas

Soft brick option did the trick!! I was also able to restore to KOT49H. Thanks my friend

Seriously need some help. At the end of my patience with trying to update this thing

I'm really frustrated. I've been trying to update this Galaxy S3 for days now with no success. Currently I am running on Slimkat 7.0. It's sometimes slow and buggy and needs some updating.
For reference, this is the phone at its current state:
- Bootloader: i747ucalh9 (literally taken from the fail message when trying to update to any other bootloader)
- Modem/firmware (?): I747UCLH9
Here's what has happened, greatly summarized (note I'm using CM6.0.4.7 for all of these operations, and when I say "update", I mean "flash"):
- I tried updating to Slimkat 9 but received no signal. I gave up on it entirely for a while
- I tried installing various LP ROMs, including CM12.1.
- I had 12.1 running for a bit, but I had no connectivity. LTE, 3G,H+ nothing.
- I tried installing a newer modem (this thread. Finally at MJB, I could actually get connectivity in some of the newer ROMs (including Slimkat 9)... but it was very erratic. It would just randomly oscillate between LTE and 3G and H+. This also broke CM12.1 entirely.
- Again, the above problem was always present. Most of the LP ROMs would just bootloop me, though. The only one that worked was Cyanide L... which I didn't really like.
- I thought maybe the issue was the bootloader. My bootloader is still i747ucalh9. So I tried updating it to various bootloaders from here, but none of the updates will work. Literally, they give me error 6 or 7 and pretty much essentially tell me that I can't do it.
- So after repeating the cycle of "let me try to update this" several times and having the update fail on me, I'm still stuck at Slimkat 7 as the only thing that worked on LTE (note the past tense). Worse yet, I tried simply downgrading my modem to match my current bootloader version, but that made things worse than better. I am now stuck at 3G... which just recently went back to LTE. Talk about erratic.
- I also tried going full stock by flashing this: http://forum.xda-developers.com/showthread.php?t=2363882 But it expects 5 arguments for format, and got 3... or something. Failed hard.
So, I'm pretty much at the end of my rope here. I really might just go and grab a new phone at this point. I just really don't want to because this thing still works fine.... I guess I got unlucky and am at a version of the bootloader that is difficult to update from. I can't seem to go anywhere with this thing. Anyone have any ideas? Do I need to use a different recovery?
Thanks...

First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.

jason2678 said:
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help! I actually did/tried a majority of this an hour or two before you posted that, except the latest firmware update link you supplied. I knew it existed and I had seen that thread before, but I couldn't dig up the link again before I had to go to work. Thing is I kind of wanted to avoid Odin for some reason but I finally gave up and used it. And yeah I already knew my bootloader version. The phone told me when it failed to update the bootloader lol.
Here's what happened thus far:
- I used Odin to flash the sammobile 4.1.1. The flashing worked just fine, but booting into it did not. It hung on the Samsung logo. So, OTA updates were out the window.
- I have no idea why, so I just used Odin to flash TWRP onto it afterwards (from here)
- I tried one of the ROMS. Data still didn't work.
- I used the thread you linked to update to MJB bootloader and whatnot. The update went fine.
- Tried another few ROMs. Data worked, but LTE was still erratic.
- Updated to NE4 and then grabbed the deoxed stock ROM.
- The deoxed stock rom failed to boot (stuck at ATT globe logo). For some reason my phone can't use stock ROMs.
- So again used Odin to put TWRP onto the phone
- Installed various LP ROMS. Again the data was erratic and plus the battery life was horrid.
- Tried getting the ktoonsez kernel. My service was murdered.
- Gave up on LP. Tried Slim 9.0. Erratic data.
- Tried Liquidsmooth 4.4.4 instead.
Currently that's kind of where I'm at. The LTE data works fine (takes a bit to get up and running after reboot though) and thus far everything is okay (though that can quickly change considering I haven't done much of anything), so I don't even know if I want to mess with it anymore. It looks like this specific ROM includes a custom kernel. So I'm guessing it's an incompatibility between the kernel and the firmware version on the other ROMs. It seems like most of the LP roms have horrible battery life (back of my phone feels like a furnace on them), so I'm not even sure if I want to do that last firmware update to use them.
It'd be kind of nice to use the OTA but apparently my ability to go stock in any form or fashion is just totally borked.
Thanks for the post though, that's pretty gold. I'm sure someone in a situation like me where they have a super old firmware will find this thread of some use as it has actual instructions and links to what you need to do to get up and running. Before you posted that, I had to go digging around pretty much everywhere figuring out what and where was going wrong.

Glad you've got it mostly working.
You might have been able to get that stock ROM to boot if you had booted into the stock recovery and run a full wipe. Touchwiz ROMs can be tough to get running after being on AOSP. As a general progression try to format internal storage with TWRP (the wipe where you have to type "yes" to confirm), if that doesn't work try a wipe with Philz, and if that doesn't work nothing, not even Odin, is effective as a wipe in the stock recovery.

Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app

mrkhigh said:
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Yep. You've got it. If you're on the latest and greatest firmware I think the towelroot exploit has been patched, unless geohot has retaken the lead in that arms race.
Easiest way to root on this phone since the bootloaders are unlocked is to just use Odin to flash a custom recovery then use the custom recovery to flash SuperSU. There's just a little trick to it. Store SuperSU.zip somewhere on your phone before flashing the custom recovery. Uncheck everything but f.reset time when you use Odin; don't let it auto reboot. Upon success pull battery. Replace battery and boot straight into recovery with vol up + home + power. If you mess up and boot into unrooted stock ROM with a custom recovery it will get overwritten with a stock recovery and you'll have to Odin custom recovery back onto it and try again.
I would do this to root your stock ROM just to execute this command in a terminal app or adb shell before any more serious flashing:
Code:
su
reboot nvbackup
That fixes a derp and gives you a working efs backup on a few backup partitions built into your phone instead of a blank one. Highly recommended before doing any ROM flashing. This will just look like a pretty normal reboot. You might see a quick flash of tiny blue text if you're watching for it.
Then you're ready to make a nandroid backup (just in case), wipe, and flash away. Take a look at LiquidSmooth if you're looking for a good lollipop ROM.

Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Thanks for the suggestion on the ROM but I think I'll stick to official cm12.1 it's not my phone and that should be a nice readily updatable bland flavor of lollipop.
Sent from my DROID RAZR M using XDA Free mobile app

mrkhigh said:
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Click to expand...
Click to collapse
At the Android 4.3 update it was noticed that flashing a custom recovery would be overwritten by the stock recovery on the initial reboot unless following the method Jason described. Another solution was to delete two lib or .so files. On devices still on stock recovery, stock recovery does not overwrite itself.
There is a blank EFS partition on the device intended for a backup. The nvbackup command populates that partition with an image which will rebuild your EFS if it is lost during a modem update or ROM flash. The loss of EFS does happen. I believe wanam, of the xposed module fame, created an EFS backup tool for Samsung devices. I don't believe he updates it any longer because he rolled the functionality into a partition backup tool, the later is in the PlayStore listed under a different creator name, yet it's still him.

So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..

coolwhipp420 said:
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
Click to expand...
Click to collapse
Since you are on LK3 you may want to considr applying the free sim/carrier unlock method before upgrading; that is if you are on stock LK3 and you have not previously carrier unlocked your device.
There was an OTA release for the MG2 stock ROM, I believe that was 4.1.2. You may want to go to that before MJB. Did you make the nvbackup suggested by Jason?

Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..

coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
There is a command to manually trigger the restore routine. I think it's
Code:
reboot nvrestore
but don't hold me to that. I'd never execute that command except if in dire need. The problem with this phone is there is an automatic routine that can be triggered in the event of a bad flash that will overwrite your nvram with the backup, even if the backup is blank. I don't think the backup stores anything modem specific, but I've never been able to confirm that. So I've always done it again after updating modems (only had to once).
Having the phone sim unlocked can be nice if you plan on traveling internationally. Otherwise, potential future carrier hopping or added resale value are the only reasons to do it.

coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
If you will never be switching carriers, nor ever sell/give/trade the phone to someone who will switch, then it is an unecessary step to do the carrier unlock.
I see Jason beat me to answering both of your questions.

[Q] Frustrated Xperia Z1C T-Mobile UK owner.

Hi,
I have the CDA 1280-7858 Sony Xperia Z1 Compact model. I have yet not been able to upgrade my phone to latest lollipop, since T-mobile UK have not released it yet.
My phone is carrier unlocked, but bootloader CANNOT be unlocked, this leaves no possible way for me to add a custom rom , right?
What are my options here? Sit and wait forever or just get a new phone?
As you can see in the attachment, only T-mobile remains on the 14.4.A.0.157 release in the UK carriers.

You can always flash stock or custom stock based lollipop from some other region. You don't need unlocked bootloader for that. There are a couple of them prerooted+dual recovery in general z1c forum.

templeka said:
You can always flash stock or custom stock based lollipop from some other region. You don't need unlocked bootloader for that. There are a couple of them prerooted+dual recovery in general z1c forum.
Click to expand...
Click to collapse
Ok, but this would erase my phone completely right? i would use flashtool to upgrade?
Is t here any reason why its taking so long to get the OTA update? I mean, optimally, i want that one and not really need to bother to reset the phone entirely for this update.

You can always make a backup in recovery (I'm thinking you have a recovery already) just in case you don't like lollipop (I didn't). You lose any app installed and preferences (for sms u can backup those and contacts you can sync with Google account) so you will have to reinstall those. If you want root for your phone you need one of those prerooted ones and those are flashed from recovery usually. Best thing is to read the instructions in those threads.

I don't have recovery mode i think. Since this comes with unlocking bootloader, which i CANNOT on my phone.. (its not possible, not even paid with jinx13).

You don't need unlocked bootloader for recovery. Just go here http://nut.xperia-files.com/ and browse to XZDualRecovery > XZDualRecovery 2.8.15 > Z1C-lockeddualrecovery2.8.15-RELEASE.installer.zip and install that from your PC (with the phone connected to your PC via USB). I think you need to enable USB debugging before doing this and you definitely have to be rooted. You should read around how to install stuff there are some guides and resource threads in General forum.
Edit: Also get the flashable version and store it somewhere safe on your phone. Anytime you flash a new ROM you need to also flash the recovery else you have to connect phone to PC and do the install version and that takes longer.

Thanks templeka, I have been unsuccessful in any attempt to root this phone also.. What would be the best way? it just seems to be locked in all ways possible for me to get this done.
edit: i tried the towelroot selection 3 from file you suggested.. it just stopped after libdvm opened (loljavasucks), and after reboot, i was unable to enter recovery mode. (pressed volume up or down, and there was no light on any diode, at any time)

You need to flash a stock .108 rom, root and install dual recovery.

Towelroot will not work on v157. Follow the guide here http://forum.xda-developers.com/showthread.php?t=2977774
In short you need to flash v108 kernel, root and flash v157 kernel back with Flashtool. Be sure to install the necesary drivers after installing Flashtool (they are in the folder where you installed it).

Sorry for being noob still.. But how do i enter flash mode now? I mean reboot and holding volume down will only enter Safe Mode of the phone. (i think its because i have the wrong kernel?)

Just when i was about to give up.. 14.5.A.0.270 just released on t-mobile.. FINALLY!

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.

Reverting from custom ROM to stock causes bootloops

Hi guys,
I have a problem I need some advice for. A year ago, I purchased my Amami for the purpose of GPS-navigation on my bicycle. It always worked fine and I was able to charge it with my dynohub without any issues. The charging is giving me a headache now though, and all troubleshooting points at the phone being the problem.
Now, a couple months ago I decided to ditch 4.4 and go for a custom ROM (I've tried Oreo and Pie) which worked fine, but the phone doesn't charge as well as it used to on my bike. I'd like to go back to stock to see if that's what is causing the issue and used the Xperia Flashtool to revert to a stock image, but the ones that used to work on the phone now give me bootloops after I've flashed TWRP and ResurrectionRemix and Lineage OS.
Is there anything I need to know before I flash a stock firmware with the tool? Any input would be appreciated.

Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.

jho55 said:
Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.
Click to expand...
Click to collapse
My bootloader is unlocked, I have TWRP installed and am currently running Lineage OS (Android 8). It doesn't matter if I flash Sony's original Kitkat or Lollipop; both will have bootloops. No offense, but I'm not sure you understood my original post: I'd like to go back to an old stock ROM, because 4.4 is the one that I'm sure have me no trouble with charging on my bike.

Proper BL relock:
https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907
If you use twrp in fotakernel partition maybe necassary to write back original fotakernel.sin (inside stock.ftf) before relock with flashtool. Remember! After relock with flastool the new BL unlock key here: DEVICESERIAL \ unlock.txt