[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto X Play
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
Please keep discussion focused, on questions pertaining to this Device
List of supporters@pijes
@Art Vanderlay
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Device Thread link
Index for Device Thread Link
Please look for a similar [HELP THREAD] when visiting another device forum.
If you would like to create a similar [Help Thread] please Click Here.
Guides, roots, recoveries and more
Guides
How to unlock your bootloader
[GUIDE] How to flash a factory image | Return to stock
Stock firmware
Official stock firmwares added for xt1562,xt1563
Root and recovery
Root
TWRP Recovery
Tools
WinDroid Universal Android Toolkit | Unlock | Root | Flash | Moto X Play
Interesting
So, I'll be the first to ask "noob" questions:
My X Play is stock. My bootloader is locked also. I wanna root my phone, but I want to be able to update for Android 6.0 and further via OTA. I already know that this is just possible if I have a backup of stock recovery and obviously stock rom. I read on this topic, the user "ephumuris" on post #25 gave me an idea of what I want to do. Considering that I just want to root my phone and use stock Moto rom, and also preserve my stock recovery to be able to update in future to android 6 (as It's a little bit hard to find those things to moto devices), I'm planing to do:
- Unlock my bootloader;
- Temporary boot TWRP recovery (using "fastboot boot TWRP-lux...img" comand);
- Root;
- Do a Nandroid backup just in case;
- Since the recovery will back to original, I'll backup it using Flashify app.
So, doing this, I can perfectly be able to update my XPlay in the future to receive official Android 6, right?
I have also a noob question. Is it possible to get your warranty back after rooting? I mean complete back to stock and lock bootloader again.
Totemic_tHiRp said:
So, I'll be the first to ask "noob" questions:
My X Play is stock. My bootloader is locked also. I wanna root my phone, but I want to be able to update for Android 6.0 and further via OTA. I already know that this is just possible if I have a backup of stock recovery and obviously stock rom. I read on this topic, the user "ephumuris" on post #25 gave me an idea of what I want to do. Considering that I just want to root my phone and use stock Moto rom, and also preserve my stock recovery to be able to update in future to android 6 (as It's a little bit hard to find those things to moto devices), I'm planing to do:
- Unlock my bootloader;
- Temporary boot TWRP recovery (using "fastboot boot TWRP-lux...img" comand);
- Root;
- Do a Nandroid backup just in case;
- Since the recovery will back to original, I'll backup it using Flashify app.
So, doing this, I can perfectly be able to update my XPlay in the future to receive official Android 6, right?
Click to expand...
Click to collapse
If anything, you'd have to make the nandroid before you root. If the system is modified at all, the ota won't take. Honestly though, I'm still not 100% sure if that would work.
PanOptikum said:
I have also a noob question. Is it possible to get your warranty back after rooting? I mean complete back to stock and lock bootloader again.
Click to expand...
Click to collapse
No.
dictionary said:
If anything, you'd have to make the nandroid before you root. If the system is modified at all, the ota won't take. Honestly though, I'm still not 100% sure if that would work.
Click to expand...
Click to collapse
I guess using the "unroot" option on SuperSU would be the same thing, I guess.
I'll try exactly how I thought and see what happens when 6.0 comes. I think It will work. If anything, I'll have to flash the "new" rom using fastboot and should work, considering that I don't have to use TWRP at the moment and will have the stock recovery on it.
As a ex-S3i9300 user, these primary things on Moto devices are hard to do compared to my deadS3. I mean, I don't know if it's hard here on Moto devices, but on Sammy devices this was muuuch more easier to do.
Totemic_tHiRp said:
I guess using the "unroot" option on SuperSU would be the same thing, I guess.
I'll try exactly how I thought and see what happens when 6.0 comes. I think It will work. If anything, I'll have to flash the "new" rom using fastboot and should work, considering that I don't have to use TWRP at the moment and will have the stock recovery on it.
As a ex-S3i9300 user, these primary things on Moto devices are hard to do compared to my deadS3. I mean, I don't know if it's hard here on Moto devices, but on Sammy devices this was muuuch more easier to do.
Click to expand...
Click to collapse
Yeah, we've been spoiled by one click flashing and rooting. Once you learn this though you'll find it easy and the same method works on a lot of other devices.
I unlocked my bootloader, boot temporary TWRP recovery, made a backup of stock rom (didn't found where this backup is, but i'll find - TWRP folder on internal storage is empty) and now have my phone rooted and with xposed framework working (Just to clarify to other users, I installed xposed version xposed-v75-sdk22-arm). Very fast and easy to do with adb indeed. Thanks
Now I'll just wait when Marshmallow arrives to X Play and probably I'll update it via OTA because my recovery is stock and I can remove root in SuperSU app :fingers-crossed:
I think there'l be no way to update OTA with framework modified (exposed or any other way).
Sent from my Moto X Play using Tapatalk
Someone correct me if I'm wrong but:
Using Xposed Framework as a example:
1. Uninstall modules being used in Xposed
2. Uninstall Xposed
3. Unroot (using what ever method)
4. Get your OTA update
5. Reverse the above steps
6. Enjoy the update
bobyn said:
I think there'l be no way to update OTA with framework modified (exposed or any other way).
Sent from my Moto X Play using Tapatalk
Click to expand...
Click to collapse
It sounds logical. BUT I have tried exactly the same on NEXUS 4 and it didn't work for me. IMO Xposed makes some changes that stay even after uninstalling modules being used.
bobyn said:
I think there'l be no way to update OTA with framework modified (exposed or any other way).
Sent from my Moto X Play using Tapatalk
Click to expand...
Click to collapse
Of course it won't. That's why I made a nandroid backup of stock rom before installing Xposed. I mean, I have a backup of stock rom with root. It's "wrong", but before I root, I made a backup on TWRP. Considering that the backup was successful, in the same temp boot on TWRP I rooted the device. After booting up, I saw on my PC that the backup on non-rooted stock rom wasn't there. Instantly I do a backup of the rom with root, and it worked...
So, I guess that I can update via OTA by wiping the whole rom and restore my backup. If anything, probably I'll have to use the "unroot" option on SuperSU
Tim3tripp3r said:
Someone correct me if I'm wrong but:
Using Xposed Framework as a example:
1. Uninstall modules being used in Xposed
2. Uninstall Xposed
3. Unroot (using what ever method)
4. Get your OTA update
5. Reverse the above steps
6. Enjoy the update
Click to expand...
Click to collapse
I would say the same as bobyn says: "Xposed makes some changes that stay even after uninstalling modules being used."
I'm not 100% sure about this, but it might be.
I guess unrooting is the only thing that really works and brings the rom back to stock.
obs: I almost forgot, but other requirement to update via OTA is having Stock Recovery. So, when you need to use TWRP, just boot temporarily
Hi, I've been trying to use Windroid toolkit to flash a different logo.bin to get rid the unlocked bootloader message but I haven't been able to do so successfully. I've already found the logo_mod.zip in another post and any tips would be appreciated.
dukespaw said:
Hi, I've been trying to use Windroid toolkit to flash a different logo.bin to get rid the unlocked bootloader message but I haven't been able to do so successfully. I've already found the logo_mod.zip in another post and any tips would be appreciated.
Click to expand...
Click to collapse
If you're not familiar with fastboot I highly recommend that you use that method for flashing. Then flash the logo.bin with this command
fastboot flash logo logo.bin
Sweet! Thanks! it worked. I'll have to familiarize myself with those commands.
Can somenone do a tutoriales of how to root this phone without losing ota updating
Enviado desde mi XT1563 mediante Tapatalk
eliday15 said:
Can somenone do a tutoriales of how to root this phone without losing ota updating
Enviado desde mi XT1563 mediante Tapatalk
Click to expand...
Click to collapse
Not an expert, but if memory serves correctly...
Since Lollipop any system change will always break OTA compatibilty. Also after undo mods like root. Some different type of file integrity check for security Android update does. Not updating files individually anymore, but directly a system block as a blob.
So now in case of root and other mods always necessary to reflash latest stock image and then (if not already in newest factory image) the Ota. Reflashing firmware can be done without wiping user-data btw. After can reflash SuperSu, etc, but then again next OTA same procedure.
In past I always after flash clean and/or OTA do a factory reset. Otherwise always little or big bugs and less battery life. After flash with temperary booted (not flashed) TWRP re-root, flash logo, xposed, etc. And restore apps and settings with Titanium like flashing and factory reset never happened . So new situation for me is hardly any more work. Still 30-45 min. total.
Verstuurd vanaf mijn XT1562 met Tapatalk
How can I access the backup folder in twrp on the internal sd card from my pc? I can access the twrp folder but it's empty. The only way I can copy the backup is to use the file manager in twrp to copy it over to my external sd, connect my phone to my pc and then copy it over. It works but is seems to be a few more steps then needed. I guess I could always just create the backup to my external sd card to begin with but what do people do if they don't have an external sd card?
Thanks for the help.
Related
Hi,
Is there any reasonably safe way to root LG D802 (international ANEUBK version) with latest 220H update installed ? The phone was never rooted before. I know how to use ADB, etc.
Thanks !
Cst79 said:
Hi,
Is there any reasonably safe way to root LG D802 (international ANEUBK version) with latest 220H update installed ? The phone was never rooted before. I know how to use ADB, etc.
Thanks !
Click to expand...
Click to collapse
Towelroot
azher98 said:
Towelroot
Click to expand...
Click to collapse
Doesn't work, it sais "phone is not supported". I understand that towelroot exploits a Linux kernel loophole that was patched around June 3.
Ioroot by side loading in stock recovery, or stump root, the only two ways for rooting 20h, powered by codefire team members (those who made Bump! )
http://forum.xda-developers.com/showthread.php?t=2448887
http://forum.xda-developers.com/showthread.php?t=2850906
6ril1 said:
Ioroot by side loading in stock recovery, or stump root, the only two ways for rooting 20h, powered by codefire team members (those who made Bump! )
http://forum.xda-developers.com/showthread.php?t=2448887
http://forum.xda-developers.com/showthread.php?t=2850906
Click to expand...
Click to collapse
Sorry, but I just gave up on it. Everything is such a mess regarding tools, versions, download locations...I will probably just wait for the official Lollipop update (the reason why I wanted to root was to install CM12 eventually).
Cst79 said:
Sorry, but I just gave up on it. Everything is such a mess regarding tools, versions, download locations...I will probably just wait for the official Lollipop update (the reason why I wanted to root was to install CM12 eventually).
Click to expand...
Click to collapse
It's very simple:
1) download ioroot:
http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip
2) extract datroot.zip from the archive just downloaded (from bts folder)
3) on the G2 enable dev option (Settings - About Phone. Then go to the bottom and you should see Build Number. This needs to be pressed a total of seven times. You should get a message at the fourth press. On the seventh, you'll get another message saying that Developer Options are unlocked.)
4) enable usb debug on the phone (Development Settings Enable USB Debugging)
5) plug the phone in usb with the pc and accept yhe RSA Fingerprint message.
6) reboot your phone in recovery with adb cmd (tape cmd: adb reboot recovery)
7) choose 'apply update from adb' in the phone recovery menu (navigate with vol down and valid with power)
8) in the pc tape cmd: adb sideload c:\datroot.zip
9) reboot et enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6ril1 said:
It's very simple:
Click to expand...
Click to collapse
Thank you, I figured these steps but:
- On one ioroot post (old post - first in thread I think) , they say that I cannot easily install custom recovery without some modified kernel ?? Are you sure I can install TWRP after rooting in order to ensure a way to flash images ?
- Also, can I revert to 100% stock after this (including baseband, bootloader, etc.), if I want to ? If so, with what tools and steps ? This information is very valuable to me.
- Right now I cannot enter recovery mode pressing the Vol Down + power then waiting for LG logo then pressing them again or power button 3 times, no matter what. I can only do this with "adb reboot recovery". Why is this ?
Thanks !
Cst79 said:
Thank you, I figured these steps but:
- On one ioroot post (old post - first in thread I think) , they say that I cannot easily install custom recovery without some modified kernel ?? Are you sure I can install TWRP after rooting in order to ensure a way to flash images ?
- Also, can I revert to 100% stock after this (including baseband, bootloader, etc.), if I want to ? If so, with what tools and steps ? This information is very valuable to me.
- Right now I cannot enter recovery mode pressing the Vol Down + power then waiting for LG logo then pressing them again or power button 3 times, no matter what. I can only do this with "adb reboot recovery". Why is this ?
Thanks !
Click to expand...
Click to collapse
The bootloader is locked. Untill recently, there was only one way to work around it, loki patch.
Only JB bootloader was lokiable, LG patched the KK one and loki doesn't work on it.
So, with loki, you had to downgrade bootloader for being able to apply loki. KK kernel must be patched too for being able to boot behind the downgraded bootloader. All the method for installing a custom recovery with this system was automated by the app autorec.
Recently, Bump was made. it permits to stay with kk booloader. It inject in the kernel (custom recovery and custom kernel) LG authentic Key.
You can easily revert to stock by flashing kdz, or even flashing zip that contains original partition.
I don't understand you last question.
6ril1 said:
The bootloader is locked. Untill recently, there was only one way to work around it, loki patch.
Only JB bootloader was lokiable, LG patched the KK one and loki doesn't work on it.
So, with loki, you had to downgrade bootloader for being able to apply loki. KK kernel must be patched too for being able to boot behind the downgraded bootloader. All the method for installing a custom recovery with this system was automated by the app autorec.
Recently, Bump was made. it permits to stay with kk booloader. It inject in the kernel (custom recovery and custom kernel) LG authentic Key.
You can easily revert to stock by flashing kdz, or even flashing zip that contains original partition.
I don't understand you last question.
Click to expand...
Click to collapse
Sorry, but you lost me here. I can't map your answers to my simple questions. My simple questions are:
- Can I revert to 100% factory stock, if I mess with rooting and install CyanogenMod 12 ? If yes, how ?
- After rooting with ioroot (what's the difference between ioroot and ioroot25 ??) what is the simplest way to install CyanogenMod 12 ? I don't really care about TWRP and such if I don't need to.
I'm really not a noobie, but not living in this world of phone hacking I can't figure out the names, versions, etc.
Thanks !
Cst79 said:
Sorry, but you lost me here. I can't map your answers to my simple questions. My simple questions are:
- Can I revert to 100% factory stock, if I mess with rooting and install CyanogenMod 12 ? If yes, how ?
- After rooting with ioroot (what's the difference between ioroot and ioroot25 ??) what is the simplest way to install CyanogenMod 12 ? I don't really care about TWRP and such if I don't need to.
I'm really not a noobie, but not living in this world of phone hacking I can't figure out the names, versions, etc.
Thanks !
Click to expand...
Click to collapse
No offense, but I tried to answer you on technical aspects, but I perceive me that your questions are more general order.
it takes time to explain what is custom recovery, and there are already tons of readings that relate to this topic.
I answered to your principal question, how to root 80220H.
As i said in my previous edited answer, you can go back to stock if you need.
I also realize that this thread should instead be placed in question/answer section, not in a dev section.
6ril1 said:
No offense, but I tried to answer you on technical aspects, but I perceive me that your questions are more general order.
it takes time to explain what is custom recovery, and there are already tons of readings that relate to this topic.
I answered to your principal question, how to root 80220H.
As i said in my previous edited answer, you can go back to stock if you need.
I also realize that this thread should instead be placed in question/answer section, not in a dev section.
Click to expand...
Click to collapse
Hello,
No, my questions are not generic, I want to find out:
- How do I install CyanogenMod 12 after I root the phone.
- What are the steps to revert to 100% stock after I root the phone and install CM12; Can I just use the LG flash tool and flash the kdz with no complains from the LG software if I have CM12 installed ?
Thanks.
Do you loss data with this metod?
Thanks
When I saw that I could upgrade to Lollipop I was interested. Then I realized there probably was no root for this yet. So I went about figuring out a way to root it before going to it. Technically this isn't a root once you have already gone to Lollipop.
THIS WILL ONLY WORK IF YOU ARE STILL ON KITKAT, ROOTED, WITH RECOVERY (TWRP is what I use via NUT's Dual Recovery for the Z1).
Requirements:
PRFCreator - Creates pre-rooted firmware - Click Here to Download
Flashtool - Allows you to flash the FTF - Click Here to Download
The FTF for the upgrade - C6916_14.5.B.0.236_T-mobile_US.ftf - Click Here
The latest SuperSU zip from ChainFire - Click here to Download
I'm assuming you have adb, drivers installed and a general understanding of how to navigate the tools above, if not read up on how they work.
Create a pre-rooted flashable firmware with PRFCreator. Install/Download PRFCreator and put the FTF and the latest SuperSU binary zip in the spot labeled SuperSU Zip. Make sure to check the box next to kernel in the include box on the top right side. See screenshot below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Congrats you have just created a flashable zip with SuperSU loaded into it. You might ask why you're not gonna add NUT's XZDualRecovery into there. Reading on the forms at the time of this post and it apppears that PRFCreator and/or Nut's recovery doesn't play well with Lollipop and causes bootloops. So run NUT's Z1xzdualrecorvery installer via bat or sh after the fact and not during via PRFCreator until they can work it out.
Make sure you have the original C6916_14.5.B.0.236_T-mobile_US.ftf in the firmwares folder either C:\Flashtool\Firmwares or C:\User\[username]\.flashtool\firmwares
Now take the flashable zip you created via PRFCreator and put it on your phones internal storage, sdcard etc.
Now that you have the flashable zip with SU preinstalled and ready to fire, reboot your phone into recovery. adb reboot recovery etc.
Once your phone has rebooted into recovery you will need to flash the flashable zip you created with PRFCreator.
After flashing the zip I'd suggest wiping the cache/dalvik. And then you will want to go to the reboot screen and power off the device.
Once the device is powered off open Flashtool.
After it loads and syncs the devices (takes a second) you'll want to double click C9XX from the list (Z1).
Next click the BOLT icon in the top left navigation that has a tooltip that says "Flash"
When the flash screen comes up select the right firmware based on the FTF location, check SYSTEM and BASEBAND under the exclude section and uncheck DATA under the wipe section, I unchecked APPSLOG but you don't have to uncheck it (to be honest I think it slowed my initial bootup by upgrading my apps) via this screenshot:
Now click the "Flash" button with your device disconnected and powered off. Follow the directions. For your Z1s you'll want to hold the "DOWN VOLUME" button and then plug the USB connector into it.
Next you will see Flashtool flashing away. Once it's complete you can unplug your phone and then power it up.
Your device is now rooted and running Lollipop. In terms of installing a custom recovery, again all of that is untested and you'll need to play around with the latest XZdualrecovery from NUT to see how it works.
REMINDER: This doesn't solve killing ric etc. Which is important to note for being able to mount the system etc. You can kill ric via tasker and an .sh script like I do or via a flashable kill ric (seen a few floating around) if you get recovery installed after the fact etc.
Thanks to:
Chainfire for his SUPERSU
zxz0O0 for his PRFCreator tool
Androxyde for keeping flashtool going
greatremix for posting up the FTF
I'll be uploading the flashable zip that I made from PRFCreator. It's over a gb obviously so it might be just as easy for you all to create it yourself.
Reserved
To solve most issues with not being able to write to the system which most root apps need. Install NUT's latest xzdualrecovery which can be found at this address under xzdualrecovery. I installed 2.8.15 via the installer (not the flashable)
http://nut.xperia-files.com/
I update rom using sony companion and rooted by king root, i tried to unlockbootloader with flashtool a minutes ago and its say :
can i flash some rom ?
Lavievn said:
I update rom using sony companion and rooted by king root, i tried to unlockbootloader with flashtool a minutes ago and its say :
can i flash some rom ?
Click to expand...
Click to collapse
Whoah whoah whoa... Let me make sure I got this straight... You... have a Z1S (Not a Z1, but Z1S) and you actually managed to root it on lollipop AND unlock the bootloader?!!!?!... Please tell me you are not joking. Or am I just not understanding correctly...
THE BOOTLOADER UNLOCKED?!!!?! If you did that... that is amazing. Do you know how long people have been trying to unlock the bootloader for this dam thing? But.. before I jump to conclusions. I'll wait for your reply.
Yazuken1 said:
Whoah whoah whoa... Let me make sure I got this straight... You... have a Z1S (Not a Z1, but Z1S) and you actually managed to root it on lollipop AND unlock the bootloader?!!!?!... Please tell me you are not joking. Or am I just not understanding correctly...
THE BOOTLOADER UNLOCKED?!!!?! If you did that... that is amazing. Do you know how long people have been trying to unlock the bootloader for this dam thing? But.. before I jump to conclusions. I'll wait for your reply.
Click to expand...
Click to collapse
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Lavievn said:
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Click to expand...
Click to collapse
That is the reason why the bootloader is locked. It might say you have unlocked the bootloader but you really haven't. It's still locked hence the inability to flash a custom ROM. I would suggest against anyone trying flashtool to unlock the bootloader, it will not work.
Best to get root, recovery and xposed if it works.
joedeveloper said:
That is the reason why the bootloader is locked. It might say you have unlocked the bootloader but you really haven't. It's still locked hence the inability to flash a custom ROM. I would suggest against anyone trying flashtool to unlock the bootloader, it will not work.
Best to get root, recovery and xposed if it works.
Click to expand...
Click to collapse
i'm stuck now, do you have a C6902 stock kernel, or any way to change phone infomation by flashtool ?
it's show that my phone is C6902 in flash tool now, so i can't flash any rom or back to stock now
@joedeveloper I'm currently on 4.4.4, rooted with baseband .59, but noticed by your directions with "prfcreator" that you do not have us "check" modem when building the flashable zip. Would it hurt to include the modem so as to get the updated baseband to .69?
Also being deodexed, will that cause issues?
Thanks for the help
Not to distract from joedevelopers hard work, but I think its important for me to inform you guys that if you have already upgraded to lollipop through sony pc companion, or ota, King root does in fact work just fine. It will give a screen saying that it could not find that xperia z1s is rootable, but it will also give an option to try to root anyway. After pressing it, it will tell you the device was sucessfully rooted. And if you check with root verifier it will let you know root was successful. So you're still good if you upgraded to lollipop.
@joedeveloper Settings>About Phone reports baseband .69 after update, so that answers that.
I went back to tft .37 and did a fresh install so I have no information if one with a deodexed phone will be effected.
Many thanks to this update method.
SOLVED
Anyone get xposed to work after this update?
Can you clarify the ric thing?
So far so good, got recovery installed, now im going to try to install the audio mod, cause i desperately need that lol
SO I finally got it to where i got a flash able zip and it worked phone says its rooted , but it won"t let me install adblocker , edit file with root explore and busybox they all say failed , please help
throonis said:
SO I finally got it to where i got a flash able zip and it worked phone says its rooted , but it won"t let me install adblocker , edit file with root explore and busybox they all say failed , please help
Click to expand...
Click to collapse
This is what I'm referring to as the issue with sony ric being enabled. It's sony's way of preventing you from writing to the system, and most root apps need this. If you were to run:
adb shell
then
su
then
mount -o remount,rw /system
What does it tell you? "Denied"?
In order to prevent sony ric from blocking it, try installing NUT's xzdualrecovery version 2.8.15. Z1-lockeddualrecovery2.8.15-RELEASE.installer.zip
http://nut.xperia-files.com/
It has a built in ric killer and will solve your issues.
So all I have to do is flash the zip on my z1s to have.recovery correct I have root supersu
Got root, thanks.
Okay, got root. Thank you. The trick is to keep doing the ADB root until it works. It doesn't work the first couple of times. I gave it 20 minutes each time before trying to install again.
Jellybean
I tried your steps from Jellybean but got no root on lollipop but I can't get root from 4.4.4. Is there a 4.4.2 firmware floating around and could that be the problem? I did the steps twice and followed it exactly. The only difference is 4.3.
Lavievn said:
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Click to expand...
Click to collapse
HOW TO INSTALL CWM AND ROCKZ1L KERNEL ??? STEP BY STEP ! MY Z1S IS ON STOCK 5.0.2, BOOT LOADER UNLOCKED : YES.
SORRY , MY ENGLISH IS VERY BAD ! THANKS SO MUCH .
*** Spoiler ****
If you are looking to flash custom ROMs or Xposed Modules, then this is absolutely inappropriate method for you. Installing Xposed without unlocking bootloader is absolutely bad idea it is always safe to unlock bootloader and then do mods and stuff bc if you messed up with it without unlocking, most of the times, it is difficult to clean it. For installing ROMs, Xposed etc., I suggest you should unlock your bootloader, then flash TWRP. The correct way to install ROM is Unlock bootloader -> Flash custom recovery -> Flash rom. Rooting won't help you there. For unlocking bootloader and install TWRP, I suggest you to follow this guide.
Before you start rooting with this method, I suggest you read what KingRoot is in this thread. Bc there are several opinions regarding the KingRoot, do a google search about what actually KingRoot is.
Warning: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try.
Let me get few things straight one by one since there are too many questions targeted to this method.
1. I have posted this method so that people can root OPX without unlocking bootloader.
2. Using ADB via PC needs so much trouble like having drivers and so. Hence I found something pretty easy that will give easy access to root.
4. Kingroot needs internet access to root your device. Though it's safe root with this method.
4. Anyways kingroot will be uninstalled as soon as SuperSu is pushed into the system. :good: :good:
Still anyone has doubts about KingRoot, stop rooting with this method NOW.
Once you root your phone with this method, you will not be able to install OTAs directly. However there is a way out to install OTAs at the bottom of this post.
Precaution: Make sure your phone has enough charging to make things proceed everything without draining all juice. Min 50% charging will be recommended.
I was finding a easiest way to root Oneplus X, cz ADB and such tools are pretty hectic. Finally I found a way to root OnePlus X without TWRP or any custom recovery and without even unlocking bootloader.
So all we going to do is root our device with KingRoot and then then will replace it with our favorite SuperSU app. So here we go.
Rooting your OnePlus X:
1. Download KingRoot and install it from here.
2. Once KingRoot is installed, open it and root OnePlus X with just one click. Process of rooting will take 2 - 5 mins. One done, Download Root Checker from play store and check if device is rooted. It has to be, congratulations.
Ok, hold your horses, we still have to Install SuperSu to replace KingRoot.
1. Download Terminal Emulator for Android from play store.
2. Download and unzip Replace_Kingroot_With_SuperSU.zip which contains SuperSU installation stuff.
Steps to install SuperSu.
1. Copy the downloaded Replace_Kinguser_with_SuperSU-v2.0 to your phone and extract it, extracted folder will contain "mrw" folder. Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files. This should be the path for your mrw folder. "/sdcard/mrw"
2. Open Terminal emulator and type
Code:
su
this will ask for super user permissions for terminal app, allow it.
3. Type :
Code:
sh /sdcard/mrw/root.sh
It might display some error, at the end it will launch supersu or open supersu manually.
Update su binary normal, then reboot.
Viola, your OnePlus X is fully rooted without needing the TWRP or even a cable or PC. [emoji14]
You can now uninstall KingRoot and Purify apps.
Cheers :good::good:
How To Install OTA's after rooting with this method
1. Download OnePlusOxygen_14_OTA_008_all_201601221550.zip .
2. Just flash it.
3. You'll be on OxygenOS 2.2.0 without any other files to flash. Don't wipe data and cache to retain your apps and data.
Re-rooting again after OTA's?
FOLLOW SAME GUIDE. \0/
Credits:
Kingxteam for KingRoot app
Unknow guy who made Replace_Kinguser_with_SuperSU-v2.0 zip file.
Let me know if your name should be here.
Looks good, will try when some custom roms come out
StraightEdgeKid said:
Warning: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try.
Precaution: Make sure your phone has enough charging to make things proceed everything without draining all juice. Min 50% charging will be recommended.
Well, I read the method CafeKampuchia's method to root OnePlus X, I even had some interaction with him, his method is good, though a obstacle later one can face will be installing OTA's. Our device, OnePlus X received 2 updates in a time of one week, which forced me to think that there will be more updates coming soon to fix things. (Like we can't move apps to sd after updating from OTA, though there is a option to do so). Hence I tried different things to root this device. first I tried installing SuperSU.zip from stock recovery, and I failed in it. Well XDA has lot of options to try it. Finally I found a way to root OnePlus X without TWRP or any custom recovery and I think we will be able to install OTA updates with having root too.
So all we going to do is root our device with KingRoot and then then will replace it with our favorite SuperSU app. So here we go.
Rooting your OnePlus X:
1. Download KingRoot and install it from here.
2. Once KingRoot is installed, open it and root OnePlus X with just one click. Process of rooting will take 2 - 5 mins. One done, Download Root Checker from play store and check if device is rooted. It has to be, congratulations.
Ok, hold your horses, we still have to Install SuperSu to replace KingRoot.
1. Download Terminal Emulator for Android from play store.
2. Download and unzip Replace_Kingroot_With_SuperSU.zip which contains SuperSU installation stuff.
Steps to install SuperSu.
1. Copy the downloaded Replace_Kinguser_with_SuperSU-v2.0 to your phone and extract it, extracted folder will contain "mrw" folder. Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files. This should be the path for your mrw folder. "/sdcard/mrw"
2. Open Terminal emulator and type
Code:
su
this will ask for super user permissions for terminal app, allow it.
3. Type :
Code:
sh /sdcard/mrw/root.sh
It might display some error, at the end it will launch supersu or open supersu manually.
Update su binary normal, then reboot.
Viola, your OnePlus X is fully rooted without needing the TWRP or even a cable or PC.
You can now uninstall KingRoot and Purify apps.
Cheers :good::good:
Credits:
Kingxteam for KingRoot app
Unknow guy who made Replace_Kinguser_with_SuperSU-v2.0 zip file.
CafeKampuchia for beginning the topic of rooting (And my warning section is copied from his post. ).
Let me know if your name should be here.
Click to expand...
Click to collapse
Bro i tried kingo root before this post n it dosnt work
mohammedtabish said:
Bro i tried kingo root before this post n it dosnt work
Click to expand...
Click to collapse
Well, try this. I have rooted my OnePlus X with this method, tested it and then I have wrote this big post.
and yes, avoid quoting whole OP post, specially when it's too big.
Rossyyy said:
Looks good, will try when some custom roms come out
Click to expand...
Click to collapse
For sure
StraightEdgeKid said:
Well, try this. I have rooted my OnePlus X with this method, tested it and then I have wrote this big post.
and yes, avoid quoting whole OP post, specially when it's too big.
Click to expand...
Click to collapse
Okay sir am new on xda actually i used to follow just read posts but now when i buyed opx i created an account...and i have rooted with twrp so i will try later when i will go back to stock..
Working in my OnePlus X with the latest firmware version! Thank you for all.
Mie said:
Working in my OnePlus X with the latest firmware version! Thank you for all.
Click to expand...
Click to collapse
Well, Thanks button is up there. Hehe
Thanks, for confirming that this stuff is working for others too.
Did you lose IMEI partitions (modem files) while rooting?
Can you confirm they're still there via screenshot on Partitions Backup app?
Also, does it require Unlocked bootloader?
it works perfectly! thanks from portugal!
ota
will rooting avoid getting updates for one plus x
Calvin2394 said:
Did you lose IMEI partitions (modem files) while rooting?
Can you confirm they're still there via screenshot on Partitions Backup app?
Also, does it require Unlocked bootloader?
Click to expand...
Click to collapse
Nope, it does not need unlocked bootloader. IMEI partitions are still there, no worries, attaching screen just to clear your doubts.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONE E1003 using Tapatalk
vinay7 said:
will rooting avoid getting updates for one plus x
Click to expand...
Click to collapse
Nope, I rooted with this method this afternoon, and received no update since, hence not sure about it. But according to me this method does not make any changes to stock recovery, hence it will not affect OTAs, you will be able to install OTAs.
Sent from my ONE E1003 using Tapatalk
Works fine, thanks dude !
StraightEdgeKid said:
Nope, I rooted with this method this afternoon, and received no update since, hence not sure about it. But according to me this method does not make any changes to stock recovery, hence it will not affect OTAs, you will be able to install OTAs.
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
And even if it would change the stock recovery, by now we should be able to re-flash the stock recovery and therefore get the updater (and then use this method again), right?
Thx mate, this method works best I think. I was worried about kingroot being some shady app, but was relieved when reading that I should replace it with supersu
From here I could even install TWRP with flashify don't I?
Thx in advance.
Works flawlessly on my E1003 on the first try. Thanks a ton for this.
David1one said:
Thx mate, this method works best I think. I was worried about kingroot being some shady app, but was relieved when reading that I should replace it with supersu
From here I could even install TWRP with flashify don't I?
Thx in advance.
Click to expand...
Click to collapse
Yes, you will be able to install TWRP with flashify without any trouble. Just remember you will not be able to install OTAs after installing TWRP.
Sent from my ONE E1003 using Tapatalk
FYI @StraightEdgeKid: OTA would fail regard less of stock or twrp recovery until you have root and system would detect it and warn at OTA screen, you would have to unroot in order to install the OTA. Thanks for the tutorial though i prefer TWRP anytime over stock.
StraightEdgeKid said:
Yes, you will be able to install TWRP with flashify without any trouble. Just remember you will not be able to install OTAs after installing TWRP.
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
How is this possible without unlocking your bootloader?
Funk Wizard said:
FYI @StraightEdgeKid: OTA would fail regard less of stock or twrp recovery until you have root and system would detect it and warn at OTA screen, you would have to unroot in order to install the OTA. Thanks for the tutorial though i prefer TWRP anytime over stock.
Click to expand...
Click to collapse
^^^ True. Any change to system (including root) will cause the OTA to fail.
Update2, Feb 13, 2016: Great news!!! FireOS 5.1.1 has been captured, upgrading from 4.5.5.1 to 5.1.1 with root works fine (already tested by fizz1234). For people coming from 4.5.5.1 the keyword is 5.2.2u3_stock_recovery_uboot.zip , this is what you use with the update instructions : http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Just competently follow fizz1234 lead and you won't risk any bricking:
http://forum.xda-developers.com/showpost.php?p=65311612&postcount=233
Original post
There are great news out there that the latest Kingroot can acquire root on 4.5.5.1 :
http://forum.xda-developers.com/showpost.php?p=65208545&postcount=280
http://forum.xda-developers.com/showpost.php?p=65211912&postcount=282
http://forum.xda-developers.com/showpost.php?p=65212042&postcount=283
This most likely can also root 4.5.4 and 4.5.5 (if anybody still has those).
After you get root, disable OTA : [ in ES Explorer rename /system/priv-app/DeviceSoftwareOTA.apk to *apk_ ]
To get TWRP after rooting, please follow the guide below, once in TWRP, you are done, reboot back to system :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
(if you have rooted 4.5.5.1, only try this if you still have warranty, since we don't know if 4.5.3 bootloaders would run after 4.5.5.1)
( thanks to tolchuk , this way to install TWRP is now tested, and works!!!)
A note on TWRP. Do not keep updates open with installed TWRP [i.e. unblocked /system/priv-app/DeviceSoftwareOTA.apk], what will happen is that the new OS will install, but the recovery will remain un-updated (now unbootable TWRP), and so you'll get a working device but with no way to do any OS upgrades or downgrades.
For 4.5.5.1, there are no upgrade paths yet to Lollipop due to the bricking issues until we capture 5.1.1 (it's possible that the oldest update files might work without bricking [5.2.0, early 5.2.2], but it's generally recommended to wait ):
http://forum.xda-developers.com/fire-hd/general/psa-fireos-5-1-1-wild-t3304133
If you want to hang out @ 4.5.5.1 (while waiting for Lollipop), please follow this guide after step 2b (after TWRP is working) :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
woot
Sent from my d2spr using Tapatalk
TWRP Successfully installed 4.5.5.1
Hi bibikalka,
I have successfully installed TWRP on 4.5.5.1 using your instructions from your thread.
I did it manually using Option B:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm going to install GAPPS next. (edit: removed question about upgrading after further reading)
Thank you for all your help.
tolchuk said:
Hi bibikalka,
I have successfully installed TWRP on 4.5.5.1 using your instructions from your thread.
I did it manually using Option B:
I'm going to install GAPPS next. (edit: removed question about upgrading after further reading)
Thank you for all your help.
Click to expand...
Click to collapse
OK, excellent news !!! So 4.5.3 + TWRP are confirmed !!! Thanks for daring !
Now stay put until 5.1.1 is captured since there is no reason to risk bricking with the earlier Lollipop versions.
Root confirm working on my HD6 running 4.5.5.1
I'll try flash GApps now, what package of GApps are you recommended?
thanks for the tut
I can add another confirmation that TWRP does work from OTA 4.5.5.1 after rooting via kingroot 4.8 and flashing TWRP via method B using ADB.
Maybe later I will use some of my horrible Java knowledge to automate the ADB method. Will give me another project instead of my lightweight HTTP server.
kenshin1388 said:
I can add another confirmation that TWRP does work from OTA 4.5.5.1 after rooting via kingroot 4.8 and flashing TWRP via method B using ADB.
Maybe later I will use some of my horrible Java knowledge to automate the ADB method. Will give me another project instead of my lightweight HTTP server.
Click to expand...
Click to collapse
What's wrong with the automation via Gscript as proposed in that TWRP post ? It works really well, I am using it all the time!
Nothing, I just know people like their options. As well as I would love to expand my knowledge in programming little by little.
I've worked on a simple chat room for the past 2 years simple because I've had no project ideas lol.
Edit: Okay just looked and it seems you must put all files in place for gscript and such. I was talking about a simple pre-packaged program simple to automate the entire process of placing the needed files and flashing everything for you. Something you can start up, it will check comparability, then if able you can click "flash TWRP" to start the process.
kenshin1388 said:
Nothing, I just know people like their options. As well as I would love to expand my knowledge in programming little by little.
I've worked on a simple chat room for the past 2 years simple because I've had no project ideas lol.
Edit: Okay just looked and it seems you must put all files in place for gscript and such. I was talking about a simple pre-packaged program simple to automate the entire process of placing the needed files and flashing everything for you. Something you can start up, it will check comparability, then if able you can click "flash TWRP" to start the process.
Click to expand...
Click to collapse
Ok, thanks! I just was not sure why it seems that Gscript looks scarier to people than other options. Indeed, a PC script could do the same thing, if one desires (I believe DoLooper was looking at something similar). Another idea is to have the script preserve the bootloaders that are on the device, and make a flashable zip out of those. Then it's super easy to return to what the device had before everything was replaced by 4.5.3 bootloaders + TWRP.
Guys, I am on 5.01 dev preview by following this guide http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408
I wanted to try to downgrade to OS4 and see if I can get 5.1.1, after requesting downgrade from my amazon account what do I need to do?
When you say downgrade to OS4 using TWRP,which zip file am I exactly flashing ?
After flashing OS4 where do I request OS5 update? from amazon account or by hitting "update" in the system update screen on the fire tablet ?
TIA
Hey, I know it is risky, but I really want to update to Fire OS 5, so could you suggest the safest way to flash? Thank alot.
Sent from my D6653 using Tapatalk
Antonntminh said:
Hey, I know it is risky, but I really want to update to Fire OS 5, so could you suggest the safest way to flash? Thank alot.
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
If you insist ...
There a slight chance that the earliest 5.2.0 bootloaders won't brick after 4.5.5.1 . On the other hand, they may brick just the same as the 5.2.2u2 bootloaders.
So follow instructions from here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
But, in Step 1).3 flash 5.2.0_stock_recovery_uboot.zip from post #2 instead of 5.2.0_stock_recovery_only.zip
This will replace the bootloaders with 5.2.0 version, which may (or may not) take off after 4.5.5.1
Please ensure that you have valid warranty !!! You've been warned
Thanks, I will save this for later if no guide for safe update to OS 5,
Btw, do we have any eta for the flash guide from 4.5.5.1 to 5.x?
Thanks
I just want to clarify something. If I'm currently on 4.5.5.1 and want to root my device, do I then NEED to disable OTA updates and install TWRP to proceed with installing OS 5? Or can I just leave on auto updates so I can get updated to OS 5 via OTA? Or will doing the OTA to OS 5 remove root? If I want to install Gapps do I need TWRP?
jleonard711 said:
I just want to clarify something. If I'm currently on 4.5.5.1 and want to root my device, do I then NEED to disable OTA updates and install TWRP? Or can I just leave on auto updates so I can get updated to OS 5 via OTA? Or will doing the OTA to OS 5 remove root?
Click to expand...
Click to collapse
Well, 5.1.1 has been already captured, so no need to try to grab it anymore :
http://forum.xda-developers.com/fire-hd/general/psa-fireos-5-1-1-wild-t3304133
If you auto-update, you'll get Lollipop, but without root. You'll have to downgrade to 4.5.3 to root, but you already have a rootable 4.5.5.1, so why no start here ? Therefore you actually do want to install TWRP, since that's how you install Lollipop with root :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
FireOS 4 is really resilient about OTA, once it starts downloading, it'll continue even after the OTA program is disabled. I recommend you do a factory reset to kill that right now. Then you root, install TWRP, and install Lollipop manually.
bibikalka said:
Well, 5.1.1 has been already captured, so no need to try to grab it anymore :
http://forum.xda-developers.com/fire-hd/general/psa-fireos-5-1-1-wild-t3304133
If you auto-update, you'll get Lollipop, but without root. You'll have to downgrade to 4.5.3 to root, but you already have a rootable 4.5.5.1, so why no start here ? Therefore you actually do want to install TWRP, since that's how you install Lollipop with root :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
FireOS 4 is really resilient about OTA, once it starts downloading, it'll continue even after the OTA program is disabled. I recommend you do a factory reset to kill that right now. Then you root, install TWRP, and install Lollipop manually.
Click to expand...
Click to collapse
Okay, so the only way to retain root while upgrading to Lollipop is to use TWRP? And I did already do a factory reset after I saw that 5.0.1 had started downloading because I wanted to root and then capture the file, but then literally right after I posted here I saw that someone else posted a few hours earlier that they had just captured it.
I have tried. Installing twrp with flashify says it flashed but won't go into recovery.king root worked fine. I am lost a little running 4.5.5.1 .there are a lot of tutorials not sure which one to follow any help appreciated. Thanks
Teilky said:
I have tried. Installing twrp with flashify says it flashed but won't go into recovery.king root worked fine. I am lost a little running 4.5.5.1 .there are a lot of tutorials not sure which one to follow any help appreciated. Thanks
Click to expand...
Click to collapse
You are not follow the guide properly, it use a different method to get twrp after rooting using kingroot, does not use flashify. Read the guide again and you will know.
Sent from my D6653 using Tapatalk
Teilky said:
I have tried. Installing twrp with flashify says it flashed but won't go into recovery.king root worked fine. I am lost a little running 4.5.5.1 .there are a lot of tutorials not sure which one to follow any help appreciated. Thanks
Click to expand...
Click to collapse
Antonntminh said:
You are not follow the guide properly, it use a different method to get twrp after rooting using kingroot, does not use flashify. Read the guide again and you will know.
Click to expand...
Click to collapse
Indeed! The problem with Flashify in 4.5.5.1 is that the bootloaders have not been replaced with the 4.5.3 version. That's what post #2 is for in the guide below! Follow the guide, and you will do fine :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
bibikalka said:
Indeed! The problem with Flashify in 4.5.5.1 is that the bootloaders have not been replaced with the 4.5.3 version. That's what post #2 is for in the guide below! Follow the guide, and you will do fine :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
So I was thinking for unrooted newbies coming from OS 4.5.4, 4.5.5 (if rootable without downgrading) and 4.5.5.1 it would be safer to go ahead and install TWRP on rooted device so if there's any problem with bootloader files, they can back out and still have TWRP.
But sounds like to install TWRP they must downgrade to 4.5.3 for the bootloaders. So that means either use post #2 method (no TWRP on device) or do extra step of downgrading. IDK. I worry about them. (I heart newbies)
Obviously, the brain's a little mushy tonight. The same is true for 4.5.4/.5 if they're rootable with latest kingroot, right? TWRP can't be installed on those with Flashify either cuz of need for 4.5.3 bootloaders. Thanks!EDIT @bibikalka: NVM. Just lost it for awhile. Guess I'll let them take their lives in their hands and dd 4.5.3 bootloaders and TWRP, hoping they got the right recovery_only or recovery_uboot on board with the update. (Dang, Amazon does not make this easy! It's like they have no sympathy for us at all!)
EDIT2: OH, COOL! Missed this crucial line: "To get TWRP after rooting, please follow the guide below, once in TWRP, you are done, reboot back to system." Works nicely. All's well!
Hey guys! Here is how to get recovery for your Z3 Compact without losing any files or flashing any kernels, as this could usually be a pain in the butt if you need a kernel for a custom rom...
I do not take credit for any of the resources in this guide and neither do i take any responsibility for bricked phones,dead SD cards or death
Click to expand...
Click to collapse
Prerequisites
1. Unlocked Bootloader (Its fairly easy to do, a simple google would suffice)
2. TWRP image- Get it Here
3. Flashtool installed with all required drivers
4. ADB and Fastboot (Here)
5. Patience
How to Install
1. Make sure you have an unlocked bootloader or this will, and shall not work.
2. Make sure you are running the latest firmware (.291). If not, use flashtool to update to the latest firmware.
3. Copy the downloaded TWRP image to your adb/fastboot folder and rename it recovery.img for ease.
4. Click shift+right click in any empty space in your adb/fastboot folder and click open command window here.
5. switch off your z3c. press the vol up button and insert USB cable to boot into fastboot mode
6. Make sure everything is working by typing
Code:
fastboot devices
in the cmd window. If all is well, then it should show your device's serial along with fastboot written beside it.
7. Time to flash the recovery:
Type in this command
Code:
fastboot flash recovery recovery.img
Congrats! You now have a recovery
8. To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.
You can now flash any rom or zips you want with this recovery, for root, flash the latest SuperSu Zip from chainfire.
I would also recommend flashing DRM fix zip.
If you want a better version of the stock rom, i will recommend installing SliMM Rom by Wajk
Note: This TWRP can get uninstalled in some cases, for example flashing a rom with twrp built in. But repeat the same process to get TWRP back without losing any data!
Thanks!
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
dansan691 said:
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
Click to expand...
Click to collapse
No, you can install SliMM directly. To get root, you should be using armv23 version... Try this. Also, you should use a DRM restore zip to get back camera quality
Clarification
Should I have to flash DRM Fix every time I flash TWRP?
andry360 said:
Should I have to flash DRM Fix every time I flash TWRP?
Click to expand...
Click to collapse
No need. But if you change reflash ROM, you might need to
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
epiii_nephrine said:
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
Click to expand...
Click to collapse
Can you please give me the error you get?
panzerox123 said:
Can you please give me the error you get?
Click to expand...
Click to collapse
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
epiii_nephrine said:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
Click to expand...
Click to collapse
Alright... I know what's up. If you can wait till 9PM IST today, I will create another guide. Thanks!
To Get Root
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
panzerox123 said:
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
Click to expand...
Click to collapse
Thank you so much sir! will be testing this version.. i'll let you know :good:
epiii_nephrine said:
Thank you so much sir! will be testing this version.. i'll let you know :good:
Click to expand...
Click to collapse
Sure! If this does not work, I have another method.
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
smahio said:
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
Click to expand...
Click to collapse
Doesn't make any sense... It would so that only if you flashed to boot partition. Download EliteKernel V3 , extract the zip, keep the boot.img in your minimal adb folder and do
Fastboot flash boot boot.img
Then try again
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ewjy said:
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
Click to expand...
Click to collapse
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
panzerox123 said:
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
Click to expand...
Click to collapse
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
ewjy said:
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
Click to expand...
Click to collapse
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
panzerox123 said:
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
Click to expand...
Click to collapse
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
ewjy said:
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
Click to expand...
Click to collapse
Funny... It works very well for me... In fact it's much more stable than previous versions