Develop Bugs

Xperia S soft brick

Hi all, I hope you can help me with my problem. Today I decided to modify the toggles on my Xperia S, wich is on latest stock Jellybean with DoomKernel, with this http://forum.xda-developers.com/showthread.php?t=2072757 but then, too late because I had already flashed the .zip package, I realised that it was for ICS stock. Luckily I have a twrp backup, but when I try to restore it I get stuck (also if the blue bar keeps on going) on "Formatting system using make-ext4fs" and then it turns off automatically, but nothing about a successful restore appears. I know I can flash the stock image using Emma, I did it before, but since I won't access to a strong wi-fi connection till the end of the holidays, I would prefer to avoid that and use my twrp working backup. Thanks in advance to you all.
Best regards
Alessandro

Super98:) said:
Hi all, I hope you can help me with my problem. Today I decided to modify the toggles on my Xperia S, wich is on latest stock Jellybean with DoomKernel, with this http://forum.xda-developers.com/showthread.php?t=2072757 but then, too late because I had already flashed the .zip package, I realised that it was for ICS stock. Luckily I have a twrp backup, but when I try to restore it I get stuck (also if the blue bar keeps on going) on "Formatting system using make-ext4fs" and then it turns off automatically, but nothing about a successful restore appears. I know I can flash the stock image using Emma, I did it before, but since I won't access to a strong wi-fi connection till the end of the holidays, I would prefer to avoid that and use my twrp working backup. Thanks in advance to you all.
Best regards
Alessandro
Click to expand...
Click to collapse
The mod You used was for Sony Xperia Ion, not Sony Xperia S. So You messed up on many levels. Do following instructions only if You have Sony Xperia S.
It seems Your TWRP has run into some troubles. For it, We need to remove TWRP entirely, from kernel and fotakernel and install it again.
Download the DoomKernel from here. Also download this carbon kernel file. Then connect Your phone in fastboot mode, and run the following command:
Code:
fastboot flash boot DoomKernel.elf
This will remover any TWRP installed, Then without disconnecting Your phone, run the following command:
Code:
fastboot flash boot boot_carbon_3-11-14.img
. This will install the TWRP on Yor phone and You will be able to restore Your TWRP backup then.

Mirhawk said:
The mod You used was for Sony Xperia Ion, not Sony Xperia S. So You messed up on many levels. Do following instructions only if You have Sony Xperia S.
It seems Your TWRP has run into some troubles. For it, We need to remove TWRP entirely, from kernel and fotakernel and install it again.
Download the DoomKernel from ... Then connect Your phone in fastboot mode, and run the following command:
Code:
fastboot flash boot DoomKernel.elf
This will remover any TWRP installed, Then without disconnecting Your phone, run the following command:
Code:
fastboot flash boot boot_carbon_3-11-14.img
. This will install the TWRP on Yor phone and You will be able to restore Your TWRP backup then.
Click to expand...
Click to collapse
Ok I followed all the steps, now my phone is booting with the sony logo and a purple led, what do I have to do to trigger the recovery?
Thank you very much
EDIT: Don't worry, I understood, now I'm restoring, I hope all will be ok and I will post results ASAP, thank you very much again. After that will I be able to flash again Doomkernel? Since its twrp has some problems, can I update it? Or should I only use cmw?

Super98:) said:
Ok I followed all the steps, now my phone is booting with the sony logo and a purple led, what do I have to do to trigger the recovery?
Thank you very much
EDIT: Don't worry, I understood, now I'm restoring, I hope all will be ok and I will post results ASAP, thank you very much again. After that will I be able to flash again Doomkernel? Since its twrp has some problems, can I update it? Or should I only use cmw?
Click to expand...
Click to collapse
All went ok, thank you very much

Super98:) said:
Ok I followed all the steps, now my phone is booting with the sony logo and a purple led, what do I have to do to trigger the recovery?
Thank you very much
EDIT: Don't worry, I understood, now I'm restoring, I hope all will be ok and I will post results ASAP, thank you very much again. After that will I be able to flash again Doomkernel? Since its twrp has some problems, can I update it? Or should I only use cmw?
Click to expand...
Click to collapse
Super98:) said:
All went ok, thank you very much
Click to expand...
Click to collapse
After You restore Your backup, if You had taken backup with DoomKernel earlier in Your TWRP backup, then Your DoomKernel willbe restored. Yo don't need to flash it again. Use TWRP version 2.8.0.1 only, the further updates do not work on Our phone. If You want got cwm and want TWRP again, follow the procedure here.

Mirhawk said:
After You restore Your backup, if You had taken backup with DoomKernel earlier in Your TWRP backup, then Your DoomKernel willbe restored. Yo don't need to flash it again. Use TWRP version 2.8.0.1 only, the further updates do not work on Our phone. If You want got cwm and want TWRP again, follow the procedure here.
Click to expand...
Click to collapse
DoomKernel has already twrp installed, does the procedure you linked update it? Can I use it or do I have to uninstall the twrp inside DoomKernel before?
Thank you very much again.

Super98:) said:
DoomKernel has already twrp installed, does the procedure you linked update it? Can I use it or do I have to uninstall the twrp inside DoomKernel before?
Thank you very much again.
Click to expand...
Click to collapse
If You already have a TWRP and it performs normally,then I wouldn't recommend changing it. And if Your TWRP version is 2.8.0.1, the You have the latest TWRP. Btw, which DoomKernel are You using? DoomKernel usually has cwm.

I have got v6 doomkernel for xperia s, it carries both cmw and twrp, but the latter didn't work when I tried to restore a backup, do you remember? So I was wondering if I should update it...
Thanks again

Super98:) said:
I have got v6 doomkernel for xperia s, it carries both cmw and twrp, but the latter didn't work when I tried to restore a backup, do you remember? So I was wondering if I should update it...
Thanks again
Click to expand...
Click to collapse
Ah yes, forgot that it has TWRP too. You can try updating by the method I mentioned earlier, but do keep the DoomKernel and backup in handy if anything goes wrong. Also, You will loose CWM by updating TWRP.

Flashable TWRP v2.8.7.0 for Sony Z3+ E6553 Ivy_Kitakami

Introduction
Disclaimer: While this TWRP has been tested by myself on my own device to flash, wipe and backup, I make no warranties as to it's performance. Use at your own risk.
WARNING: flashable version contains a kernel boot image which will be flashed to your device along with the recovery image.
Click to expand...
Click to collapse
Installation instructions
This recovery image is for the E6553 single SIM Z3+. Do not use it on another model.
This recovery image requires an unlocked bootloader. You will lose some functionality on your phone if you unlock your bootloader
Do your research and make sure you're using the latest version of the relevant tools if you do decide to unlock.
DO NOT enable MyXperia functionality if you've unlocked your bootloader. You will brick your device.
This first download of this recovery image CANNOT be flashed to your phone and must be used in fastboot mode only
The second download is a flashable recovery
Use the first version to flash the second dual-boot.zip version
Unzip the recovery.zip file to extract the recovery.img file to use in fastboot mode
Code:
C:\>adb reboot bootloader
C:\>fastboot boot recovery.img
C:\>adb push dual-boot.zip /sdcard/dual-boot.zip
C:\>adb push dual-boot.zip.md5 /sdcard/dual-boot.zip.md5
Click to expand...
Click to collapse
Now use the TWRP install feature to install dual-boot.zip. Follow the prompts of the Aroma graphical installer.
CAVEAT: this extends the boot time by about 5 - 10 seconds as ramdisk images need to be unpacked and there's a wait on a keypress to determine whether to enter recovery mode. In order to boot into recovery, press power on. When you see the yellow LED come on then press the down volume button once or twice. You will then boot into TWRP.
NOTE: the dual-boot.zip installs a new 28.0.A.8.251 kernel. If you're using the autoroot kernel from Devries you will need to flash SuperSU to re-root your device
This dual boot/recovery works by flashing the recovery image to the FOTAkernel partition. A custom ramdisk image contains the normal boot image. If the down volume keypress is detected, then the recovery ramdisk is automatically extracted from the FOTAKernel partition and flow of control switches to recovery. If no keypress is detected then the normal ramdisk is extracted and normal android boot ensues.
Those of you who installed version 1.0 please download and install this version 1.1 to fix the error with the startup of the trim area daemon
Download
Binary
Fastboot TWRP Recovery Image v2.8.7.0-e6553-1.0 for Z3+ E6553
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 (MD5: 52d4b7d406308dbd457e8b94210b7c87)
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 - MD5
Sources @ github
device_sony_kitakami
device_sony_ivy
Click to expand...
Click to collapse
Changelog
Code:
Current changelog: -- 29 September 2015
[new] v1.1 fix up problem in combined ramdisk preventing trim area daemon from starting correctly
[new] Flashable recovery - 28 September 2015
[new] Fixed various sys/class issues so that CPU temperature and LED / backlight control work correctly
[new] Updated to use 28.0.A.8.251 kernel (as opposed to the AOSP kernel)
[old] Initial release - 10 September 2015
Click to expand...
Click to collapse
Thanks To
The regular contributors to the Z3+ forum, among others @[NUT], @ChrisJ951, @DHGE, @Devries, @zxz0O0, @Venkat Kamesh, @AndroPlus, @Sacktreter who pass on knowledge and who make the forum a lively and cooperative place
Click to expand...
Click to collapse

People who installed version 1.0 of the Flashable TWRP must please update to version 1.1 to correct a bug.

Awesome work.
Glad you were able to get the screen working for it! Boots up fine w/o issue for me

This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+

AMoosa said:
This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+
Click to expand...
Click to collapse
I'd venture to suggest that it's highly unlikely that locked bootloader recovery could work. The DM_VERITY is almost a guarantor of that. Just search for CONFIG_DM_VERITY or Verity in the Z3+ forums for more info.
Even if an exploit works, the second it modifies the system partition, the kernel panics and refuses to boot. The only way of preventing that is to flash a new kernel or edit the ramdisk to remove the verity key. And the only way to flash a new kernel / edit the ramdisk is to unlock the bootloader.

Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
This is correct behaviour. You're not actually flashing the recovery image, just temporarily booting a recovery kernel and associated ramdisk. Sony Xperia devices don't have a recovery partition, or more accurately, they don't have a bootloader than can check and load a boot image from a recovery partition.
Technically it's possible to make the boot image check for a ramdisk on another partition and use this instead of the normal ramdisk, but this is step two. Sony should be releasing an open recovery bootloader fairly soon for the Z3+ which will allow this recovery image to be flashed. It's already been released for other devices.
Until Sony releases open recovery for Z3+ or I spend the time trying to implement a feature that probably only has days or weeks of utility (until Sony releases the open recovery for Z3+) , you're stuck with a TWRP that you need to launch every time in fastboot mode.

On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
New version now flashable so that you can boot into recovery...read top post carefully before using.

serrin85 said:
On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot
Click to expand...
Click to collapse
Fixed in latest version

http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..

deecept said:
http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..
Click to expand...
Click to collapse
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.

dl12345 said:
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.
Click to expand...
Click to collapse
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!

deecept said:
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!
Click to expand...
Click to collapse
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks

dl12345 said:
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks
Click to expand...
Click to collapse
HI dl12345,
this recovery support Dual model? E6533

hi.question...i get remote: dtb not found error when trying to boot the recovery..any ideas?

didnt get a thing... how do i install?

please, release TWRP for 6533 too
we need custom recovery so bad

Dathrex said:
please, release TWRP for 6533 too
we need custom recovery so bad
Click to expand...
Click to collapse
Pleaseee ????

Brother, please, help us with twrp to E6533, please.
Enviado de meu E6533 usando Tapatalk

Another TWRP 2.8.7 for Fota Partition with working brightness

TWRP updated to 2.8.7.2 including latest commits. Download at the bottom (see Dec25 file). Selinux permissive is set, so, should work on all roms. Remember, unzip and flash in fastboot.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
I know there is a bunch of different TWRP recoveries for our Z1, including the official one. Well. This one is for Fota. It was compiled in Z1 build environment with all the appropriate flags. And brightness is working fine. Why brightness is important? Because at maximum brightness your phone will overheat to over 65 degrees during flashing. And thanks to previously wrong value, the brightness level in other TWRPs is 15 times the maximum one.
You can flash this one in fastboot like this: fastboot flash recovery recovery.img. Just make sure that your kernel does not have inbuilt TWRP, because 2 identical recoveries will conflict with each other. Unzip first...
For those who would like to know what's new, look here: https://gerrit.omnirom.org/#/q/project:android_bootable_recovery
In this build, I have also reduced default vibration to 28/28/28, but you can set in Settings to whatever you want.

can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !

hawkeyexp said:
can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !
Click to expand...
Click to collapse
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe

ok will try it out if it works with my tree

Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk

Gawis said:
Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
That's right, but I am planning to update Jaguar's kernel. So, when it is done, I will
post it without recovery, so this one can work.
But it really makes no difference...

optimumpro said:
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe
Click to expand...
Click to collapse
Is working fine - thx !

Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk

swa100 said:
Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Try, but there is a separate branch for TWRP for M. And anyway, M is not usable yet and won't be for a long time...

Thanks for this one!
I do however seem to experience an issue when trying another ROM like CM.
With your ROM I can reboot into this recovery but with CM I get a black screen. When using another older TWRP recovery I used when rooting both ROMS boot fine into recovery.
Sent from my Z1 using Tapatalk

@optimumpro is there any chance to make a flashable zip with it? Thanks

matcho13579 said:
@optimumpro is there any chance to make a flashable zip with it? Thanks
Click to expand...
Click to collapse
Use Rashr app to install this...

Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<

Snowblond said:
Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<
Click to expand...
Click to collapse
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.

optimumpro said:
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.
Click to expand...
Click to collapse
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
I don't know why it is not working for you. If you post your boot.img, I can put recovery in it..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.

drakonizer said:
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.
Click to expand...
Click to collapse
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-

Snowblond said:
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-
Click to expand...
Click to collapse
Did you try with another kernel? If it worked then, you can trace the problem to the kernel itself, and not the device or your flashing methodology.

Recovery updated to 2.8.7.2. See OP for download...

[HOW-TO] How to SuperSU the Moto G5 Plus (Rooting Guide)

Hey guys,
Thanks to @vanche for the modified kernel and twrp recovery and @fayiaz for the guide on how to root and @Johny Cipel for the original guide and everyone else like
@topjohnwu
@santhosh
@abdyasar
For the original twrp, root and other stuff.
Now thats out of the way
Requirements:
-Unlocked Bootloader (Moto G5 Plus with offers from Amazon won't have unlockable bootloaders but if you buy the standard model from them then you'll be fine)
-Vanche's Modified TWRP from here (http://cloud.vache-android.com/Moto/potter/TWRP/twrp-3.1.0-0-potter.img)
- Vanche's Modified Boot Kernel from here (http://cloud.vache-android.com/Moto/potter/root/potter_boot_test7.img)
- Vanche's Wifi Patch because wifi will stop working after flashing the modified boot kernel (http://cloud.vache-android.com/Moto/potter/root/wlan_custom.zip)
- Chainfires Root http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
--- If you already have TWRP on your phone, the one by Santosh, you must flash the one made by Vanche or it wont work and you can just download the recovery image and flash it via twrp by toggling the flash zip button on the twrp recovery install menu.
1.. Download all the three files then boot your phone into bootloader mode by holding Volume Down + Power
2. Connect your phone to your PC and then open the adb terminal wherever adb is located open command prompt at that folder
3. Place the recovery image and boot image where the adb terminal folder is located
4. Fastboot flash recovery first and then boot into recovery at least once then reboot into bootloader fastboot flash boot the modified boot image.
5. Boot into the system (May take a while for the first time after flashing the boot image).
6. Place the wlan_custom.zip into your phones internal storage
7. Boot back into recovery and then flash the zip this time
8. Then download and flash the SR3 Super Su from above using recovery and you should have root!!
Safety net may break so if you wanna use Snapchat or any other apps that use safety net make sure you login first then root. You can't logout or else you'll have to unroot and log back in.

wiping?
do we need to wipe storage in this process?

yourtitan said:
do we need to wipe storage in this process?
Click to expand...
Click to collapse
It shouldnt, But if you cant boot then you need to flash the no-verity crypt zip once

Awesomeslayerg said:
It shouldnt, But if you cant boot then you need to flash the no-verity crypt zip once
Click to expand...
Click to collapse
thanks for the reply. but i have several data in my phone. can i just unlock bootloader and root as instructed above without wiping my storage? its a task to take backup of everything. thanks in advance.

wifi not working after supersu root
wifi not working mate.. Flashed custom zip .. No use..

Dhan... said:
wifi not working mate.. Flashed custom zip .. No use..
Click to expand...
Click to collapse
Did you correctly flash vanche TWRP and boot image? Because you're supposed to do that first and then flash the wifi zip..

yourtitan said:
thanks for the reply. but i have several data in my phone. can i just unlock bootloader and root as instructed above without wiping my storage? its a task to take backup of everything. thanks in advance.
Click to expand...
Click to collapse
The phone will wipe as soon as you unlock the bootloader so best to back up first.

Sorry but what's the differences beetwen this method and magisk?

Awesomeslayerg said:
Requirements:
-Unlocked Bootloader (Amazon bought Moto G5 Plus dont have unlockable bootloaders so your out of luck)
Click to expand...
Click to collapse
Only the 'Prime Exclusive - With Offers and Ads' Amazon models don't have an unlockable bootloader, while the 'Standard Version' models can definitely be unlocked. You probably should clarify that or some will think that they can't buy from Amazon and unlock/root the phone.

Dahenjo said:
Only the 'Prime Exclusive - With Offers and Ads' Amazon models don't have an unlockable bootloader, while the 'Standard Version' models can definitely be unlocked. You probably should clarify that or some will think that they can't buy from Amazon and unlock/root the phone.
Click to expand...
Click to collapse
Will do thanks

The "Magisk method" didn't give me privileges on /system, there are some things I can do and others do not, this method gave me full root access like in the other MotoG devices? And the safetynet check fails too?
Anyway thank you very much!!

What's going to be different than magisk root?

Videon Tutorial [SuperSu]
Guys I Found This Video Tutorial For This Thread On Roting Moto g5 Plus With Super Su ------- And Worked Great For Me----- link:-
https://www.youtube.com/watch?v=TV78iWxQrRE

gr8 work mate.....I'm rooted with Magisk...wanna go with super su........do i need to
gr8 work mate.....I'm rooted with Magisk...wanna go with super su........do i need to reflash above said recovery?
will it wipe my current data on both storage?
Pls guide..........How is Moto app working with super su?
Shamith08 said:
Guys I Found This Video Tutorial For This Thread On Roting Moto g5 Plus With Super Su ------- And Worked Great For Me----- link:-
https://www.youtube.com/watch?v=TV78iWxQrRE
Click to expand...
Click to collapse

Thank you so much! This worked! Why would WiFi stop working with this boot image?

I'm
donjuro said:
Thank you so much! This worked! Why would WiFi stop working with this boot image?
Click to expand...
Click to collapse
I don't know why but you have to flash WLAN in order to get it to work

Twrp backup can't worked
I successfully rooted my moto g5 plus mobile. And TWRP INSTALL Latest supersu via. But sdcard card backup can't worked. Why can't work sdcard in twrp? I think this twrp unofficial so not supported sdcard process. Please help me. How to work sdcard backup twrp. I try mount sdcard. But can't mount sdcard. Totally I'm very tired. Please help me.

Does someone have the img file for G5/Cedric?

Awesomeslayerg said:
...Safety net may break so if you wanna use Snapchat or any other apps that use safety net make sure you login first then root. You can't logout or else you'll have to unroot and log back in.
Click to expand...
Click to collapse
Do you think that will be fixed soon with a newer version of SuperSU, or some "root hider" apps? The idea of running a phone without root is absurd/offensive/rediculous IMO, but I don't want to be denied the ability to run certain apps because the developers have the rediculous idea that running without root should be "OK" to ordinary users? This idea is extremely offensive to me!!!

Guys, I wonder why the OP is "Account currently disabled"? I hate running without root, but, it seems a bit early and not all the problems have been worked out yet, such as TWRP not accessing SDCARD yet - I think I was a little premature buying my Moto G5 Plus as we don't really have "stable" release custom ROMs or fully functioniong TWRP and to even root we have to rely on some not well known sources for kluged files to make SU work?

Issue -Wipe while boot 4.4

I want to boot rooted kitkat 4.4 (tft) for getting the root function but every time i flash and boot it i getting in a wipe and the boot loading appears again and again.
what is the problem? I mentioned that after every boot the old data dont get deleted . maybe the old data is the problem. how can i delete everything like the partition?

moby.dog said:
I want to boot rooted kitkat 4.4 (tft) for getting the root function but every time i flash and boot it i getting in a wipe and the boot loading appears again and again.
what is the problem? I mentioned that after every boot the old data dont get deleted . maybe the old data is the problem. how can i delete everything like the partition?
Click to expand...
Click to collapse
How did you get a rooted ftf? I think that might be the problem. Unless you mean a prf... Best way to root KK is just flash stock ROM and use doomlord rootkit.

levone1 said:
How did you get a rooted ftf? I think that might be the problem. Unless you mean a prf... Best way to root KK is just flash stock ROM and use doomlord rootkit.
Click to expand...
Click to collapse
what is a prf?
Well probably i dont mean a rooted tft but that is what the guy in the guide was talking about but i also tryed a normal stock rom 4.4 and got the same problem, that my loading screen was repeating the whole time
how can i delete the partition?

moby.dog said:
what is a prf?
Well probably i dont mean a rooted tft but that is what the guy in the guide was talking about but i also tryed a normal stock rom 4.4 and got the same problem, that my loading screen was repeating the whole time
how can i delete the partition?
Click to expand...
Click to collapse
Are you using Flashtool or recovery? If you can get into recovery, just use 'wipe' option.

levone1 said:
Are you using Flashtool or recovery? If you can get into recovery, just use 'wipe' option.
Click to expand...
Click to collapse
no i dont get into recovery because i cant boot 4.4

moby.dog said:
no i dont get into recovery because i cant boot 4.4
Click to expand...
Click to collapse
If you want to be on 4.4, use Flashtool and flash a stock 4.4 ftf, then root with Doomlord. If you want to be on LP, use Emma, it will download and flash firmware for you.
Flashtool - http://www.flashtool.net/index.php
Emma - https://developer.sonymobile.com/open-devices/flash-tool/how-to-download-and-install-the-flash-tool/
KK ftf - https://forum.xda-developers.com/so...f-xperia-z1-compact-d5503-14-4-0-157-t3118047

how i described .. 4.4 is not loading after flashing! Doesnt matter which kind of 4.4
so i ask how can i delete everything?? bcs i think its matter of some data that still on my smartphone

moby.dog said:
how i described .. 4.4 is not loading after flashing! Doesnt matter which kind of 4.4
so i ask how can i delete everything?? bcs i think its matter of some data that still on my smartphone
Click to expand...
Click to collapse
When you flash with Flashtool, there is a box that says 'wipe'. Check the 'userdata' option.

thanks that worked!
When i do it like here with doom: https://forum.xda-developers.com/showthread.php?t=2620794
i cant boot after booting the boot.img

moby.dog said:
thanks that worked!
When i do it like here with doom: https://forum.xda-developers.com/showthread.php?t=2620794
i cant boot after booting the boot.img
Click to expand...
Click to collapse
Did you unlock bootloader? KK version 442 or 443? Add debugging enabled in settings? If all yes, I'm not sure why it wouldn't work. You could try different options, there are a few for KK - pimped kernel, Great devs kernel, and you could root with easy rootkit.
BTW - to restore your phone without flashing whole ROM again, check boxes under 'exclude' options for everything but kernel.

levone1 said:
KK version 442 or 443?
Click to expand...
Click to collapse
That version which you posted. 14.4.A.0.157
Bootloader is unlocked.
Usb Debugging is enable.
Is it the right doom version for my tft ? Can you please show me which doomversion i should boot? Because that one i showed you couldnt boot.

moby.dog said:
That version which you posted. 14.4.A.0.157
Bootloader is unlocked.
Usb Debugging is enable.
Is it the right doom version for my tft ? Can you please show me which doomversion i should boot? Because that one i showed you couldnt boot.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2784900

I installed succesfully EasyRootTool v12.4 then i tried to install the lockeddualrecovery 2.8.26 choosed 2. and it tells me "Installation failed!"
Step 3: Setup of dual recovery. /system/bin/sh: su: not found
and this thing all the time: "adb server is out of date. killing..."

moby.dog said:
I installed succesfully EasyRootTool v12.4 then i tried to install the lockeddualrecovery 2.8.26 choosed 2. and it tells me "Installation failed!"
Step 3: Setup of dual recovery. /system/bin/sh: su: not found
and this thing all the time: "adb server is out of date. killing..."
Click to expand...
Click to collapse
Do you have root access when you turn on the phone? Did you make sure USB debugging is enable in settings, and also check 'allow USB debugging' pop-up when you connect to computer? If yes to all, just restart computer and/or phone, and reconnect and try again. XZDR is solid. If you have root, it will work. BTW - is bootloader unlocked or locked?

levone1 said:
Do you have root access when you turn on the phone? Did you make sure USB debugging is enable in settings, and also check 'allow USB debugging' pop-up when you connect to computer? If yes to all, just restart computer and/or phone, and reconnect and try again. XZDR is solid. If you have root, it will work. BTW - is bootloader unlocked or locked?
Click to expand...
Click to collapse
Bootloader unlocked: Yes
Rooting status: "here is nothing" i guess not
i restared everything still not work but i guess its because i dont get the root acces thats my main problem when should i have got it ?
Another Idea: When i install the EasyRootTool v12.4 it ends with "creating vm <loljavasucks>" is that what it supposed to write when its finished? When i keep that Easyroot window open and start the dual recovery installation, the easyroot tells me "done, checking if device is rooted... error: its not"
So i guess the problem is that i still not rooted my device but i thought that is what i am actually trying to do with easyroot..?

moby.dog said:
Bootloader unlocked: Yes
Rooting status: "here is nothing" i guess not
i restared everything still not work but i guess its because i dont get the root acces thats my main problem when should i have got it ?
Another Idea: When i install the EasyRootTool v12.4 it ends with "creating vm <loljavasucks>" is that what it supposed to write when its finished? When i keep that Easyroot window open and start the dual recovery installation, the easyroot tells me "done, checking if device is rooted... error: its not"
So i guess the problem is that i still not rooted my device but i thought that is what i am actually trying to do with easyroot..?
Click to expand...
Click to collapse
Ok, try this - download this zip https://mega.nz/#!lh9i0AYI!iH3Vw5keSNo66CHvq3c6V9HMCWAWJ5FIYcZZ35U254g It contains 2 files, one is a kernel and one is a recovery. Also download supersu 246 zip from here https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 and put it on your phone somewhere. Then connect in fastboot mode and flash the 2 IMG files:
'fastboot flash boot [name of kernel file].img'
'fastboot flash recovery [name of recovery file].img'
Then unplug and power on. When you see colored led, press volume key and you should get into recovery. When in recovery, flash supersu zip. Then power off, and connect in flash mode. Open Flashtool and flash the stock kernel from your ftf. Reboot and you should be rooted.

Thanks that worked! And now i flash the 4.4 stockrom and after that a prerooted version?

moby.dog said:
Thanks that worked! Can i flash the latest stockrom now?
Click to expand...
Click to collapse
You can flash whatever you want now. If you want stock 5.1, you can use Flashtool / Xperifirm to download ftf and flash, or use Emma. You will lose root, but you can get it back the same way you just did. If you want to root 5.1 that way, you can extract boot img from advanced kernel and download latest twrp img, and just fastboot those, and no need to reflash stock kernel afterwards.
Advanced kernel - https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060
Twrp 3 for Z1c - https://www.androidfilehost.com/?fid=529152257862711713
Alternately, you could flash a prf, or any custom ROM you want

Ah okay i will try do you know how i can change my Lockbutton with my autofocus button? my lockbutton is broken and i never used the autofocus button before
edit: its actually dont worked after i booted kitkat again i lost my root and recovery mode its like i can only have the recovery mode or unrooted stock..

moby.dog said:
Ah okay i will try do you know how i can change my Lockbutton with my autofocus button? my lockbutton is broken and i never used the autofocus button before
edit: its actually dont worked after i booted kitkat again i lost my root and recovery mode its like i can only have the recovery mode or unrooted stock..
Click to expand...
Click to collapse
What did you flash?