Database Users

[SOLVED][HELP] Wrong rooting went down to boot fail (Pics and Video)

First of all I want to tell everybody I work as a WebDeveloper and designer. Last year I had rooted and changed my rom on HTC HD2 (to know i am not a newbie to this area) not a big deal. Me and my brother decided we can root our ACER ICONIA A500 because we.. just wanted it, but I guess we mess it up hard. Here is what we have done:
1.Find a SD card - Format it to FAT32 - Upload the GingerBreak.apk - USB Debugging (ON) - Original thread - http://forum.xda-developers.com/showthread.php?t=1055354 - DIDNT WORKED
2.Format the SD card for second time on FAT32 and run the files on PC from this thread http://forum.xda-developers.com/showthread.php?t=1546593 (ofcourse following all steps one-by-one) - and guess what -> IT DIDND WORKED
So we tought rooting for this device wont work, we have to try something else and I uploaded "update.zip" (this ZIP was from http://forum.xda-developers.com/showthread.php?t=1633907 ) into my formatted SD card and run the tablet with Power btn and Vol- it started to load it everythig seemed OK till it restarted by itself and showed me this VIDEO
So where I am now?
{
"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"
}
on the second pic it says "boot verified failed..."
The version before I bricked it was with Android 4.0.3
Kernel version: 2.6.39.4+
Image version: Acer _AV041_A500_RV03RC01_WW_GEN1
Build number: Acer_AV041_A500_1.031.00_WW_GEN1
P/N: FM.S14A0.00U
What can I do now?
EDIT: I've got it running back by putting stock "Acer_AV041_A500_1.031.00_WW_GEN1" into SD card naming it update.zip and booting by Pwr btn and vol-
But Now... How to root it?

If u never root or unlock bootloader so maybe your a500 still on hc bootloader n u just doing upgrade it into ics rom woth hc bootloader with unsigned version update. Zip,maybe u can find how to push the honeycomb rom update. Zip into root of sdcard using adb and doing flash again pwr+vol -
Sent from my HTC Desire VC

oregorn said:
But Now... How to root it?
Click to expand...
Click to collapse
Go to the dev section.
a. NVFlash Unlocked Bootloader
b. Install CWM recovery
c. Flash a rooted ROM

Moscow Desire said:
Go to the dev section.
a. NVFlash Unlocked Bootloader
b. Install CWM recovery
c. Flash a rooted ROM
Click to expand...
Click to collapse
This is like step 1 then step 2 or just three different methods I can get my tablet rooted?
Could you please help me with some links? Thank you

oregorn said:
Thats the options like step 1 step 2 or just methods i can get root?
Could you please help me with some links? Thank you
Click to expand...
Click to collapse
The ONLY way to get root with full system RW, is to go to this thread;
http://forum.xda-developers.com/showthread.php?t=1622425
There are several ways to do this (unlocked bootloader and CWM) You HAVE to do the bootloader, and you HAVE to install a CWM. And you HAVE to install a pre-rooted rom. The thread offers different methods to do this via an application run from PC.
Root, is just allowing access to view the hidden system files. Most root apps, demand to do writes to the /system. Example, is SU. It does remounts so it can install SU binaries. Just having the Superuser app doesn't mean anything without /system RW. And the only way you get that, is by running an insecure kernel. And the only way you get an insecure kernel on ICS/JB, is via CWM. And of course the only way all this works, is via unlocked bootloader.
That's why we have the package in that link.
You "might" get by with doing the bootloader and CWM. Afterwards, Flash one of the kernels in the dev section (just look), then install SU and Busy Box from the market. This might probably keep your current rom intact. Or, just install a custom rom.

Ok. I think I unlocked my bootloader successfully. But I find it difficult to actually Install CWM recovery! I know that i have to have root before installing CWM recovery actually, am I right?
These are videos from what happens when I launch the tablet on normally and with vol + & -
tinypic.com/player.php?v=33u4lzo&s=5 - Normally
tinypic.com/player.php?v=2cy41fq&s=5 - Vol-
tinypic.com/player.php?v=2s82zdj&s=5 - Vol+
Question: What is full system RW ?
I even dont know how to flash a kernel.
It may be hard, but I will keep trying till its done.

oregorn said:
Ok. I think I unlocked my bootloader successfully. But I find it difficult to actually Install CWM recovery! I know that i have to have root before installing CWM recovery actually, am I right?
These are videos from what happens when I launch the tablet on normally and with vol + & -
tinypic.com/player.php?v=33u4lzo&s=5 - Normally
tinypic.com/player.php?v=2cy41fq&s=5 - Vol-
tinypic.com/player.php?v=2s82zdj&s=5 - Vol+
Question: What is full system RW ?
I even dont know how to flash a kernel.
It may be hard, but I will keep trying till its done.
Click to expand...
Click to collapse
Can't see anything from yr links for some reason BUT to clarify.
No you are not right!
If you want root to install a recovery, it doesn't work like that with the acer, you must unlock the bootloader.
The unlocked bootloader AND custom recovery are 1 package - if the flash is successful you will already have cwm.
The link Moscow provided you with gives you everything you need.
Which ever method you choose (manual nvflash or auto tools) you must follow each step to the letter!!!
Run the bootloader package again.
Choose yr recovery.
Flash.
Boot DIRECTLY to recovery.
Wipe data/media and cache
Flash yr rom
Reboot.
Done.
If you really only want r/w access use blackthund3r's ICSRoot tool...in the link Moscow posted.
Also if you are on stock rom be sure to read that post regsrding boot.p file.
All of this information is in that post, please take some time to read thru it so u know exactly what is involved. ...if u need further help there are guides in my sig as well.
dibb
Sent from my GT-I9300 using Tapatalk 4 Beta

dibb_nz said:
Run the bootloader package again.
Choose yr recovery.
Flash.
Boot DIRECTLY to recovery.
Wipe data/media and cache
Flash yr rom
Reboot.
Done.
Click to expand...
Click to collapse
This is the word i was missing all time.
What i have done?
Installed TWRP, Wiped off SYSTEM,Factory, Dalvik Cache, Cache and finally installed stock rom with full root.

LG Spirit H440n general thread

Welcome to the general thread for LG Spirit H440n/H420 and it's other variants.
Feel free to share any information you have about this device. I will include everything important at the op.
{
"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"
}
Specifications
You can find LG Spirit specs here.
USB Drivers:
You can find drivers for your device through LG mobile support tool.
Also, there are the universal LG USB drivers.
Stock kdz files
You can find the stock firmware for LG Spirit variants here.
Root
You can root any Lollipop version with KingRoot.
Here is how to replace KingRoot with SuperSU.
You can root any version (Lollipop or Marshmallow) by unlocking the bootloader and installing a custom recovery first.
Bootloader Unlock
You can unlock the H440n bootloader with the method provided here.
For unlocking the H420/H422 bootloader (patched uboot) refer to the Notes section of this post.
Custom Recoveries
CWM H440n
TWRP H440n thread, maintained by @Fobos531
Refer to the Notes section of this post for H420/H422 custom recovery flashing.
Notes
Note1: You can install the Lollipop kdz files with LG Flash Tool. Also, here are some details on how to install the Marshmallow kdz.
Note2: LG Spirit source code can be found here.
Note3: It seems that in order to use ADB you have to set the USB connection type to:
1. MTP in windows
2. PTP in linux
Note4: LG H422 users, find everything about your device in detail here (4pda thread) and here (xda thread). You can find infromation on how to unlock the bootloader (uboot patch), root, flash a custom recovery and stock or custom roms.

screen on
hello there, just bought this phone. It's fine. But why doesn't it switch the screen on when a notification arrive? do you have any solution or suggestion? thanks!

giamanto said:
hello there, just bought this phone. It's fine. But why doesn't it switch the screen on when a notification arrive? do you have any solution or suggestion? thanks!
Click to expand...
Click to collapse
Hello. You' re right I notice it too. I think you can try the app "Screen notifications" from the Play Store but I haven't tested it yet.

polfrank said:
Note 4: It seems like our device's source code can be found here: http://opensource.lge.com/osSch/list?types=ALL&search=h440 (Correct me if I'm wrong). I wish I knew how to build Cyanogenmod..
Click to expand...
Click to collapse
I'll check it out when I get to my work computer. No linux at home...
At least CWM Recovery would be nice to have.
Edit:
http://pastebin.com/06QGsZgh

polfrank said:
Hello. You' re right I notice it too. I think you can try the app "Screen notifications" from the Play Store but I haven't tested it yet.
Click to expand...
Click to collapse
thank you! it works PERFECTLY!

If I have done everything right, I have extracted the kdz file (T-mobile Croatia) and here we have recovery.img and boot.img attached to this post!
I post them because someone may be able to build CWM recovery for us, so I would like to make his life easier if he decides to do so.

polfrank said:
If I have done everything right, I have extracted the kdz file (T-mobile Croatia) and here we have recovery.img and boot.img attached to this post!
I post them because someone may be able to build CWM recovery for us, so I would like to make his life easier if he decides to do so.
Click to expand...
Click to collapse
Buddy you are my hero! Now I can get some stuff done with syncing CM12 sources to build CWM and after that hopefully TWRP with one buddy from BUG Forums. For now on, priority is CWM and hopefully CM12(.1 is optional). I tested out with extracting boot.img and recovery.img directly from phone and didn't had success with it (failed to do some stuff with creating .mk files for phone).
Also thanks to OP for .kdz file, it shall work on any other network because it is very much clean ROM (Croatian T-Mobile, only have few apps which can be uninstalled without root).
Peace from owner which had this phone rooted.

midzan21 said:
Buddy you are my hero! Now I can get some stuff done with syncing CM12 sources to build CWM and after that hopefully TWRP with one buddy from BUG Forums. For now on, priority is CWM and hopefully CM12(.1 is optional). I tested out with extracting boot.img and recovery.img directly from phone and didn't had success with it (failed to do some stuff with creating .mk files for phone).
Also thanks to OP for .kdz file, it shall work on any other network because it is very much clean ROM (Croatian T-Mobile, only have few apps which can be uninstalled without root).
Peace from owner which had this phone rooted.
Click to expand...
Click to collapse
Nice! If you compile a working cwm for a start, YOU are a hero! Feel free to ask for anything else I can do to help you with (but I know only little stuff).
I just want to mention that the thanks for the .kdz file goes to the guys I mention at the credits!

Seems that bootloader is locked. Fastboot oem unlock didn't work and didn't have luck with loki or bump either.

manakeri said:
Seems that bootloader is locked. Fastboot oem unlock didn't work and didn't have luck with loki or bump either.
Click to expand...
Click to collapse
You mean you wanted to flash recovery and the locked bootloader prevented you? If this is the case try the app "flashify" from Play Store.
If you just mention it, well, it's good to know. :good:

I flashed the recovery, that's not the problem, booting into it is.
Someone else with more experience about unlocking bootloaders (and time) could have a try.
I'll upload the CM device files to the github tomorrow.

manakeri said:
I flashed the recovery, that's not the problem, booting into it is.
Someone else with more experience about unlocking bootloaders (and time) could have a try.
I'll upload the CM device files to the github tomorrow.
Click to expand...
Click to collapse
Actually there isn't problem with booting in recovery you just need to do this button combination
Power + vol down and when lg logo apears press combination again
This is how LG G3 goes to recovery and it should work here too
Edit: I should upload also CM device files and kernel to my github next week at collège so we should have all files on one github

You can reboot to recovery with apps that offer an advanceed reboot menu, too. Like Link2sd.
Though, I don't know if @manakeri is talking about something else like: try boot to recovery but the locked bootloader prevents you..

polfrank said:
Though, I don't know if @manakeri is talking about something else like: try boot to recovery but the locked bootloader prevents you..
Click to expand...
Click to collapse
Exactly that. There is verification that the recovery's certificate matches original or something like that.

Here is new firmwares
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW79RCO032ESAYF6BB4BMEM/H440n10e_00.kdz - LG H440N 10E HUNGARY
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW48UI40323XARJB234BLAO/H440n10b_00.kdz - LG H440N 10B Poland PLUS

Well seems that our bootloader isn't locked if I look via this app. Would give a try with CWM (currently building up from stratch, need some time to compile it) and see would it boot up somehow (key combo and this app)

http://www.mediafire.com/download/51nnmacvkqm5df9/recovery.img

manakeri said:
http://www.mediafire.com/download/51nnmacvkqm5df9/recovery.img
Click to expand...
Click to collapse
That is CWM you built or it is TWRP?

CWM

Working? How instaled this?

Root Xperia Z1s C6916 14.5.B.0.236 Android 5.0.2 Locked bootloader

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 .

[HELP THREAD][Noob Friendly] Moto X Play Ask any question

[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.

TWRP for Z3 compact ; Unlocked Bootloader - GUIDE

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