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!
Related
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 .
[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.
If your stupid like me :silly: and you blindly follow the [HOW-TO] The Nexus 6 All-In-One Beginner's Guide you may be trying to figure out how to fix your phone.
The beginner guide linked above is amazing to say the least but the OP has not updated it yet to reflect the 6.0 update. If your phone has Marshmallow 6.0 and you follow the instructions you will render your Nexus 6 unusable. Not bricked, just not functional. You will get an error that states Your device is corrupt. It can't be trusted and may not work properly. (seen below) Followed by a blank screen. But don't worry, its very easy to fix with just a few extra steps. :fingers-crossed:
{
"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"
}
If you are here, it is assumed that you have already done the following steps:
Step 0.1 Download and install the Android SDK tools (adb and fastboot), as well as the Google USB drivers. This is step 2 in the beginner guide and there is a great write up here on these tools. [noob-read] adb and fastboot. What is it? How can it help you?
Step 0.2 Unlocked the Bootloader.
Step 0.3 Ran the CF-Root tool. The file name is CF-Auto-Root-shamu-shamu-nexus6.zip
If you watched the CMD window closely this is where the problem happened. There will be a couple errors thrown. You will wait to see the big red Android on your phone but instead you will see the above warning message flash briefly followed by a black screen. If this is the case, proceed to step 1
Please Note: Parts of these steps are copied and pasted from other instructions. Consider this a grouping of other instructions for the purpose of simplification.
Step 1 - Install a Custom Recovery (taken from the original guide)
Go HERE to download the latest TWRP recovery for the Nexus 6. At the time of this write-up, I used 2.8.5.0
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img
Move the recovery.img file to C:\Program Files (x86)\Android\android-sdk\platform-tools
Open command prompt and run the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it.
After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Power off the phone
Step 2 - Install the Modified boot.img (Original steps HERE)
Download the modified boot.img from http://downloadmirror.co/android/sx/shamu-mra58k-boot.zip
Unzip the file and move it to C:\Program Files (x86)\Android\android-sdk\platform-tools
Boot the phone back into bootload mode using Power + volume down.
Open a command prompt and enter the following commands:
Code:
cd C:\Program Files (x86)\Android\android-sdk\platform-tools
Code:
fastboot flash boot boot.img
Power off the phone
Step 3 - Flash the SuperSU zip via TWRP Recovery v2.56 beta (original steps HERE)
Downlaod SuperSU x2.56 from http://downloadmirror.co/android/u1/SuperSU-v2.56-20151030013730.zip
Boot your phone into the bootloader mode with Power + volume down
Enter recovery mode. This will open TWRP Recovery
After TWRP Recovery is open, connect your phone to your computer.
Open My Computer where youc an see the C: drive, and other connected drives. You should see your Nexus 6 listed. Open it.
Move the SuperSU zip onto your phone. I placed mine in the TWRP folder.
On your phone, select Install, then navigate to the folder that contains the SuperSU zip. Click on the zip file.
Swipe to Confirm Flash and begin the flash.
Once SuperSU is flashed, select the Reboot System option.
And that's it, your phone should now boot back up to your fresh rooted copy of Android Marshmallow 6.0. You can download a root verification app to confirm the root. :victory:
all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine
simms22 said:
all i did was flash a twrp flashable stock marshmallow, then a custom kernel and supersu(in twrp). no odd message, everything booted fine
Click to expand...
Click to collapse
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
For those of us who have been down this road a time or two, this guide will not help them at all. Its really just directed to newbie's who are now stuck because of the beginner guide above.
K!ngpen said:
You followed the correct instructions haha. That is basically what those 3 steps above entail, but broken down well enough they could be followed by someone who has not rooted a phone in the past. You also have to consider that if they followed that original beginner guide they can no longer boot into android, which kind of induces panic in most of us newbies and it makes it hard to search for and find the right answers. So basically this guide picks up right at the point where you realized "oh crap my phone didn't boot up like the instructions said it would, and now it won't turn on" :crying:
Click to expand...
Click to collapse
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:
simms22 said:
key word, that gets very many in trouble afterwards.. "panic".
yea, i remember those days. but i was very lucky, as i never paniced. when i first rooted my g1(beginning of 2009), there were not very many people that knew about android, nor much info about it. so most of what we did back then was lots of trial and error :angel:
Click to expand...
Click to collapse
I'm right there with you. My first rooted device was a motorola xt720 sometime in 2010 I think. It was a company phone and like most very young IT folk I was curious lol. New versions of Android started rolling out but the phone wasn't going to get the update. So i was suck on Eclair. I stayed after work and tried the root, and it didn't work to say the least... I stayed at work until 2am trying to get that darn thing to work. 3 days later I got it to flash cyanogen. It was buggy as hell but i didn't care because I didnt have to explain to my boss that I broke my phone by trying to "hack" it lol. That was a win in my book. I later worked up the courage to get it back on a rooted version of Froyo. Pretty bumpy start to my rooting career to say the least. Now I'm a die hard Nexus follower just looking for an excuse to root the next device.
K!ngpen said:
You followed the correct instructions haha...
Click to expand...
Click to collapse
Everyone who is trying to help other users earns respect.
Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?
Noopguy said:
Thanks for this. it got me 98% there but SuperSU says i need to update the binary. Its gives me the option to update normally which fails or to update through twrp. Im not sure how to update through twrp. Any suggestions?
Click to expand...
Click to collapse
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?
K!ngpen said:
Just to confirm, your phone now boots back up correctly, but you get the popup stating that the binaries for SuperSU are missing?
Click to expand...
Click to collapse
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt
Noopguy said:
Not missing but needs updating. My phone boots up and everything seems to fine otherwise. I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp. I tried to post a screen shot but XDA wont let me post a link since im a new user. imgur.com/a/Jgwpt
Click to expand...
Click to collapse
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?
K!ngpen said:
And this was an unrooted nexus 6 with android 6.0 when you started? It wasn't already rooted on a lower version of android or anything like that?
Click to expand...
Click to collapse
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.
Noopguy said:
No i had it rooted on 5.1.1 this morning and updated to 6.0 with a factory image. I ran into problems rerooting after the update and I came here. I used your guide and everything works except i cant figure out how to update the binaries for SuperSU.
Click to expand...
Click to collapse
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Noopguy said:
I tried updating with the normal option but it fails and going into twrp does nothing. I just cant figure out how to update the binaries with twrp.
Click to expand...
Click to collapse
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).
sjgore said:
Flash SuperSU 2.52 Beta (not 2.56), then boot into Android and select "Update SuperSU Binaries" and select "TWRP/CWM" option rather than "Normal". Worked for me.
I still needed to.
I'm on MRA58R, BTW (the third and latest factory image for Nexus 6).
Click to expand...
Click to collapse
That's strange, I sideloaded that for MRA58K, MRA58N and MRA58R and I don't think I was ever prompted to update the binaries. I'm not sure you are being asked to.
alryder said:
If you sideload this through TWRP you shouldn't need to update the binaries. It has the latest included.
Click to expand...
Click to collapse
Thanks guys, this really helped. Flashing 2.52 did the trick and i didnt need to update the binaries after i flashed it. I am also on MRA58R
I was going to say as well, SuperSU v2.52 is what needs to be installed via TWRP, not v2.56. I believe v2.56 is for the new systemless root option but it sounds less stable and buggy.
Does this wipe any data? I have been looking to root and actually followed that guide myself, got the same issue and fixed by reflashing a factory image.
EDIT: I'm assuming I don't have to break my phone again to do this correct? Can I just pick up from step 1 to flash the recovery and go from there?
Something weird happened to me after flashing TWRP and I thought I'd share. So my N6 wasn't corrupted at all, but I decided to root my phone and I started by flashing TWRP. I went into boot loader and then recovery to make sure it worked and it did. When I went to reboot the system, I got the the "your device is corrupt screen." I pressed the power button and the screen turned black for a few seconds and then it rebooted normally. I went back into recovery to try and reproduce this and it happened again, Not sure why this happened but everything is functional.
New to rooting and I want to root my Nexus 6
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help
atvisic said:
I have a Verizon Nexus 6 with the build number "MRA58R." I haven't unlocked the bootloader or ran CF-Root tool like Steps 0.2 and 0.3 say. To root my phone, should I try and purposely break it by following the All-In-One Beginner's Guide and then follow the steps you put? Or is there another way I should go about rooting it? Thanks for your help
Click to expand...
Click to collapse
Lol why break it first. I didn't read through the op here but all you need to do is unlock the bootloader. Flash twrp with fastboot. Reboot to recovery without booting the phone, if you boot the phone before going into twrp it will get overwritten and you will need to reflash it. Flash a custome kernel in twrp, flash SuperSU 2.52 or higher in twrp.
The instructions in the op are more complete naturally. But when it has you flash the boot.img, you can use a custom kernel instead.
*** 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.
Update - Dec. 15th, 2018: Recently I attempted a couple of freshest ROM installs (update-kindle-37.6.0.5_user_605485120.bin and update-kindle-37.6.2.6_user_626533320.bin), and the device bootloops with the 5.1.2 bootloaders (cycling through the "Amazon" logo - looks like the newest kernel is incompatible with the older bootloaders). Using recovery, I had to sideload 5.1.2 again (which older bootloaders allowed me to do!), and re-root it using these instructions via Kingoroot. As such, the most recent version that I recommend here is update-kindle-37.5.7.9_user_579279320.bin (FireOS 5.4.0.1).
News : The update file for 5.3.1.0 is posted on the Amazon site, so time to upgrade! Note that you cannot get root by downgrading 5.3.1 to 5.1.2 (& Kingroot), because the 5.3.1.0 bootloaders will brick if rolled back (so stay put for now ...) :
http://forum.xda-developers.com/amazon-fire/help/installing-custom-rom-fireos-5-3-1-0-t3418541
Rootless in Seattle ...
[Updated July 16th, 2016]
Flashfire almost replicates TWRP functionality, thus I've significantly re-written this post to include branches for people who managed to keep TWRP from the old days of 5.0.1, and those who have to use Flashfire because of newer bootloaders (and thus lacking TWRP ...). If you want to quickly upgrade (or downgrade ?) your *rooted* FireOS while avoiding potential bricking issues, the post is for you (if you are not rooted yet, and have stock 5.3.1.0, do not attempt to downgrade, it'll brick the Fire !!!).
Before proceeding, remember these IMPORTANT points :
Take a note of your current bootloaders, this will be important later on. If you forgot what version you have, please follow this post to identify it:
http://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
If you disabled the stock launcher via "pm hide", please re-enable it again before the procedure, or install some other launcher as the user app. For example, if you converted Nova or other launcher to a system app, it will disappear upon upgrade, so you need some other launcher operational. Until I fixed Nova, the tablet would freeze at the end of the "optimizing applications" stage because at this stage there was no working launcher (can be fixed by adb command line, but still a bit of a mess)
Turn on Airplane mode, so that you don't "catch" an update right after this upgrade (and before you have a chance to disable it)
A : TWRP Install instructions [if you still have the "good" 5.0.1 bootloaders]
0) install ADB and Fastboot drivers on your PC, and boot into TWRP ( http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548 ):
Code:
adb reboot-bootloader
fastboot boot TWRP_Fire_2.8.7.0.img
1) boot into TWRP and:
do factory reset (skip if don't want to),
flash whatever ROM you want from this post, for example, 5.3.1.0 ( rename *bin to *zip such that TWRP can recognize it):
update-kindle-37.5.7.9_user_579279320.bin
(Previous recommendation - update-kindle-global-37.5.5.2_user_552153420.bin)
flash the attached fire_boot_53820.zip . The objective of this file is to overwrite all the problematic bootloaders after 5.1.x update back to 5.0.1 version (53820 variety). This will allow to go into fastboot and then TWRP just like before.
flash Supersu.zip ( SR5-SuperSU-v2.82-SR5-20171001224502.zip; previous recommendation - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip )
flash Xposed for Lollipop 5.1 (if you want it for misc modules, highly recommended to do this just in case)
http://forum.xda-developers.com/showthread.php?t=3034811
(version xposed-vXX-sdk22-arm.zip )
flash Pico (Uni) GAPPS for 5.1 :
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
B: Flashfire Install instructions [Note that you will have 5.1.2 (or 5.1.1) bootloaders after this procedure]
Given that FlashFire is no longer supported, I recommend version v0.51 with the date hack in order to pass the date check (adb shell; su; busybox date -s "201509221745"). Copy all the necessary files to the local Fire storage, such as /sdcard/upgrade. In Flashfire, chain the following files as ZIP or OTA flashes in one batch (same options in each case, no R/W for /system partition by default):
the OTA file you want renamed to zip, such as this one update-kindle-37.5.7.9_user_579279320.bin
the attached fire_boot_5.1.2-5.4.2_542168620.zip (or fire_boot_5.1.1-5.4.1_541112720.zip). This will replace whatever bootloaders the OTA file has with those from 5.1.2 (or 5.1.1), in order to allow upgrades/downgrades without bricking. Preserving 5.1.2 bootloaders may seem a bit pointless now, but it's still good to freeze these as some hackable bugs may be discovered in the future, so the older bootloaders one has - the higher the chance they have useful bugs ! Again, if you still have 5.1.1 bootloaders, do use fire_boot_5.1.1-5.4.1_541112720.zip here !!! (thanks to Kramar111 for reminding of the rooting trick that works with 5.1.1 bootloaders [fastboot oem append-cmdline "androidboot.unlocked_kernel=true"]
flash Supersu.zip ( SR5-SuperSU-v2.82-SR5-20171001224502.zip; previous recommendation - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip )
Xposed for Lollipop 5.1 (if you want it for misc modules, highly recommended to do this just in case)
http://forum.xda-developers.com/showthread.php?t=3034811
(version xposed-vXX-sdk22-arm.zip )
Pico (Uni) GAPPS for 5.1 :
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
After you've verified everything, hit the "FLASH" button.
See the screenshot below as an example of how the Flashfire screen should look. Note that Flashfire gives no margin of error because it reboot immediately, so if you are flashing a bricking FireOS (relative to your bootloaders), make sure that fire_boot_5.1.2-5.4.2_542168620.zip (or the 5.1.1 version !) is flashed immediately after !!! I've carefully followed this procedure, and verified that the bootloaders do get restored to 5.1.2 version regardless of what was in Amazon's OTA file.
2) reboot to FireOS 5. Verify that SuperSu works.
3) if step 2) fails, you get into working recovery by pressing "Pwr & Vol+". If you still have 5.0.1 bootloaders (getting rare by now ...), then sideload the old 5.0.1 update and root it: http://kindle-fire-updates.s3.amazo...ZjK/update-kindle-37.5.2.2_user_522054520.bin If you have 5.1.2 bootloaders, sideload 5.1.2 instead (the last rootable version as of now) : https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin If you have 5.1.1 bootloaders, sideload 5.1.1 !
4) block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
Want to say thanks by clicking the "Thanks" button ?
{
"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"
}
For clarity, this is for a person that is currently on 5.0.1, correct? This is to go from 5.0.1 to 5.1.1 while retaining root/TWRP, but this will not allow someone that is on 5.1.1 to access TRWP, right?
TallGrassShort said:
For clarity, this is for a person that is currently on 5.0.1, correct? This is to go from 5.0.1 to 5.1.1 while retaining root/TWRP, but this will not allow someone that is on 5.1.1 to access TRWP, right?
Click to expand...
Click to collapse
Indeed, you have to have 5.0.1 so that you can boot into TWRP
copied update to AFH:
https://www.androidfilehost.com/?fid=24269982087012932
MD5: 8dfcc416a0b2c47fe384dd28f2ef18ed
So once we're on this, they cant OTA us to 5.1.1 because we're already on it right? Now 5.1.2 ...
julianpaul said:
So once we're on this, they cant OTA us to 5.1.1 because we're already on it right? Now 5.1.2 ...
Click to expand...
Click to collapse
the last step is to block OTA updates.......sooooo....
So does anyone know what 5.1.1 offers over 5.0.1?
hp420 said:
the last step is to block OTA updates.......sooooo....
Click to expand...
Click to collapse
No i meant even if ota is left enabled, there's no immediate risk.
I will try to make a edited stock 5.1.1 ROM with Root, No Lockscreen Ads, etc.
Sent from my KFFOWI using Tapatalk
TallGrassShort said:
So does anyone know what 5.1.1 offers over 5.0.1?
Click to expand...
Click to collapse
I was wondering that
julianpaul said:
No i meant even if ota is left enabled, there's no immediate risk.
Click to expand...
Click to collapse
Yeah but you had that cliffhanger 5.1.2 ending...
Vlasp said:
I will try to make a edited stock 5.1.1 ROM with Root, No Lockscreen Ads, etc.
Click to expand...
Click to collapse
Sounds very useful
bibikalka said:
With the capture of the new FireOS 5.1.1, these the instructions to install 5.1.1 and keep root and TWRP access.
Click to expand...
Click to collapse
Will this work direct from 5.0.0? I see no reason it shouldn't but just checking.
I'm also curious, does this also work for an unrooted/stock 5.0.0? (a brand new device) Has anyone tried?
sina6002 said:
I'm also curious, does this also work for an unrooted/stock 5.0.0? (a brand new device) Has anyone tried?
Click to expand...
Click to collapse
Seen someone mention on another thread that they've done it.
Which is handy as I've got to talk someone through this on skype later in the week when theirs arrives.
bibikalka said:
With the capture of the new FireOS 5.1.1, these the instructions to install 5.1.1 and keep root and TWRP access.
Install instructions.
0) install ADB and Fastboot drivers on your PC, and boot into TWRP ( http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548 ):
Code:
adb reboot-bootloader
fastboot boot TWRP_Fire_2.8.7.0.img
1) boot into TWRP and:
do factory reset (skip if don't want to),
flash the update from this thread (update-kindle-full_ford-37.5.4.1_user_541112720.bin.zip, unpack bin.zip, rename *bin to *zip such that TWRP can recognize it, say thanks to the poster):
http://forum.xda-developers.com/showpost.php?p=64184649&postcount=46
flash the attached fire_boot_53820.zip
flash Supersu.zip ( https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip )
flash Pico (Uni) GAPPS for 5.1 :
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
2) reboot to 5.1.1. Verify that SuperSu works.
3) if step 2) fails, you get into working recovery by pressing "Pwr & Vol+". You can boot TWRP again, and sideload the old update : http://kindle-fire-updates.s3.amazo...ZjK/update-kindle-37.5.2.2_user_522054520.bin
4) block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
Click to expand...
Click to collapse
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?
sina6002 said:
I'm also curious, does this also work for an unrooted/stock 5.0.0? (a brand new device) Has anyone tried?
Click to expand...
Click to collapse
The new devices seem to be coming with 5.0.1 not 5.0.0.
87racer said:
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?
The new devices seem to be coming with 5.0.1 not 5.0.0.
Click to expand...
Click to collapse
Mine came with 5.0.0 which i bought on black friday. I didn't open the other boxes, but i assume they are the same.
What benefits will I get with an 5.1.1 upgrade?
I have a 5.0.0 version (from before the black friday). Would be grateful to know if the instruction above works for it, cause I can't upgrade to 5.0.1 first anymore.
gad42000 said:
Mine came with 5.0.0 which i bought on black friday. I didn't open the other boxes, but i assume they are the same.
What benefits will I get with an 5.1.1 upgrade?
Click to expand...
Click to collapse
From the release notes on a 5.1.1 tablet:
Blue Shade - Makes everything ugly by removing blue (supposed to be better at night)
FreeTime Web Browser - Browser for kids (limits, curated content, tracking, etc)
Activity Center - More kid stalking, track what the are spending their time on
Curfew - Restrict kids from using tablet even when FreeTime is not in use
bibikalka said:
4) block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
Click to expand...
Click to collapse
How do you find the system directory in Explorer? All I'm seeing is the internal "sd card" and the actual micro sd card.
Not that I'm expecting a new update in the time it takes me to let it online and download a file browser on the tablet, but seems I'm missing something that could be handy in future. Thanks.
---------- Post added at 08:48 PM ---------- Previous post was at 08:46 PM ----------
87racer said:
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?
Click to expand...
Click to collapse
Having just done it. Yep, sat in twrp atm.
Pond-life said:
How do you find the system directory in Explorer? All I'm seeing is the internal "sd card" and the actual micro sd card.
Not that I'm expecting a new update in the time it takes me to let it online and download a file browser on the tablet, but seems I'm missing something that could be handy in future. Thanks.
---------- Post added at 08:48 PM ---------- Previous post was at 08:46 PM ----------
Having just done it. Yep, sat in twrp atm.
Click to expand...
Click to collapse
interesting so the 5.0.1 preloader and uboot work just fine with the 5.1.1 system image just not the other way around...think I will just RMA that tablet rather than get SP Flash Tools to work.
sina6002 said:
I have a 5.0.0 version (from before the black friday). Would be grateful to know if the instruction above works for it, cause I can't upgrade to 5.0.1 first anymore.
Click to expand...
Click to collapse
Well you can as you could download the 5.0.1 and install it through twrp, but if it's not needed it's somewhat pointless.
87racer said:
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?
The new devices seem to be coming with 5.0.1 not 5.0.0.
Click to expand...
Click to collapse
I received one on October 21st that came with 5.0.0, I received one a week October 26th later that came with 5.0.1. That's from Amazon, I suppose ymmv if you got them at BestBuy or elsewhere.