Database Develop

Soft bricked Nexus 6? - "Your device is corrupt. It can't be trusted and may not work

Soft bricked Nexus 6? - "Your device is corrupt. It can't be trusted and may not work
I unlocked the bootloader using the Nexus Toolkit (wugfresh) succesfully. However, while installing TWRP Recovery my device now appears soft bricked and I am unable to boot up nor get into Recovery mode.
This is the message I get:
{
"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"
}
It comes on briefly for a second or two, and then the phone shuts down. I attempted the suggestions listed here (
Dismiss the warning
The warning message should go away on its own after about 10 seconds and your device will continue starting up.
If you still see the warning message, you can choose to continue starting up your device by pressing the power button once.)
but they do not work. The phone will not continue to boot into System.
Help?
EDIT: I can get into Recovery Mode now. However, it wont go into TWRP (it did before), it now just has the Android on it's back with the red exclamation triangle reading "No command".

reflash twrp
flash a custom rom

Unlocking the bootloader shouldn't cause that message to show up. What were you expecting the toolkit to do? And do you know what it successfully did?

It happens whenever I try to root the device. I am able to get into the bootloader, and then reflashing to stock resolves the issue. But every time I try to root the device, it refuses to continue to boot into system after flashing the message. In summary, it successfully unlocked the bootloader but wont root/ flash TWRP.

Consult the guy who made the toolkit that ****ed up your phone. You clicked his button, rather then run a short list of well known commands we could help you with, so we have no idea what you did right or wrong... Maybe you didn't click hard enough.
Alternatively, read one of the many many many guides here, and use the single command needed, and if there are any errors copy and paste the console output (using code tags) here and we can sort you out in a minute or two.

Caebron said:
It happens whenever I try to root the device. I am able to get into the bootloader, and then reflashing to stock resolves the issue. But every time I try to root the device, it refuses to continue to boot into system after flashing the message. In summary, it successfully unlocked the bootloader but wont root/ flash TWRP.
Click to expand...
Click to collapse
What root are you using? That is probably the issue. If you use the older style root you need a modified boot image. I suggest the new systemless root.
So to fix this lets do this:
1 Use the toolkit to flash stock and unroot.
2 Flash TWRP
3 Copy the systemless root 2.65 to the !readytoflash folder. Delete the three files that are in there. The are from the old root way.
4 Reboot into TWRP and use it to flash the new root.
When you exit TWRP it will offer to root your phone. Say no. And stop after each step and make sure the phone is ok. So we can tell what went wrong if there are issues.

Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and worked like a charm on my Nexus 5. But I also understand that things might be different for the 6 and the toolkit may not be the best option anymore. My fault for that assumption.
I will try TonikJDK's suggestion and report back.

Hi,
Had the same thing...
Really DONT know what the hack with with these wonderful people who developet these tools that do not mention ANYTHING regarding the issu in the main page of their tools here.
I think that you should follow the instructions:
1) Download shamu-mra58k => extract => take bootloader + radio + boot + cache + recovery + system + userdata => compy to platform-tools folder (under SDK).
2) Open CMD (open command prompt...) from platform-tools folder.
3) Type: fastboot devices (to know that pc recognized your N6) & than type the commands as shown at the attached screenshot.

That looks like a Wugfresh NRT log...
But why not go the whole way and use the latest 6.0.1 MMB29K?
https://developers.google.com/android/nexus/images?hl=en#shamu

Caebron said:
Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and worked like a charm on my Nexus 5. But I also understand that things might be different for the 6 and the toolkit may not be the best option anymore. My fault for that assumption.
I will try TonikJDK's suggestion and report back.
Click to expand...
Click to collapse
Your not along in getting that message after using the Wugfresh Nexus Root Toolkit as I got the same message on my brand new Nexus 6. The toolkit installed TWRP fine, but somewhere in the three files it asked me to install in TWRP (beta superSU, busybox, and another file), there was a problem. I ended up clicking flash stock + unroot and I did this twice and it worked the second time. Then I locked the bootloader and did a factory reset. So far so good. I will root the device again, but by another method.
However do note that I have used that Toolkit for a Galaxy Nexus, Nexus 7 & very recently with a Nexus Player and its worked great every other time. I think it has something to do with Marshmallow, but I'm not sure.

thinkingbrian said:
Your not along in getting that message after using the Wugfresh Nexus Root Toolkit as I got the same message on my brand new Nexus 6. The toolkit installed TWRP fine, but somewhere in the three files it asked me to install in TWRP (beta superSU, busybox, and another file), there was a problem. I ended up clicking flash stock + unroot and I did this twice and it worked the second time. Then I locked the bootloader and did a factory reset. So far so good. I will root the device again, but by another method.
However do note that I have used that Toolkit for a Galaxy Nexus, Nexus 7 & very recently with a Nexus Player and its worked great every other time. I think it has something to do with Marshmallow, but I'm not sure.
Click to expand...
Click to collapse
Best and easiest method to root Marshmellow imo is to flash TWRP and CF`s latest systemless root zip 2.65.

dahawthorne said:
That looks like a Wugfresh NRT log...
But why not go the whole way and use the latest 6.0.1 MMB29K?
https://developers.google.com/android/nexus/images?hl=en#shamu
Click to expand...
Click to collapse
That's not the NRT log (just flahsed manually by fastboot without any script).
I think with up to 6.0.1 MMB29K(not included) there is no issues.

Just kidding...
I've been running MMB29K for a couple of weeks with no problems. I was just suggesting that if the OP was going to go to the effort of flashing then he/she may as wll use the most recent version. Or even hold off for a few days for the possible new one in January. Hey, that's today...

Caebron said:
Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and
Click to expand...
Click to collapse
... it bricks your phone. Unless you know exactly what you're doing. But then you don't really need it anymore.
People, Marshmallow is already past the toolkits. It has an update once a month, and the toolkits don't have time to be updated fast enough. You'll be bricking your phones constantly if you don't learn your stuff.

Caebron said:
I unlocked the bootloader using the Nexus Toolkit (wugfresh) succesfully. However, while installing TWRP Recovery my device now appears soft bricked and I am unable to boot up nor get into Recovery mode.
This is the message I get:
It comes on briefly for a second or two, and then the phone shuts down. I attempted the suggestions listed here (
Dismiss the warning
The warning message should go away on its own after about 10 seconds and your device will continue starting up.
If you still see the warning message, you can choose to continue starting up your device by pressing the power button once.)
but they do not work. The phone will not continue to boot into System.
Help?
EDIT: I can get into Recovery Mode now. However, it wont go into TWRP (it did before), it now just has the Android on it's back with the red exclamation triangle reading "No command".
Click to expand...
Click to collapse
This error is the consequence of a " feature " of marshmallow that checks if your system is modified and issues this error message.
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
One last thing, not to rub it in for the gentlemen who posted the question but for other who are considering the easy way of using a toolkit, and please don't get offended by this. No one is against convenience but if you are unable or unwilling to learn few simple commands to unlock and unroot your phone you probably are not the type of user who needs to root the phone and chances are that after using a toolkit something will go wrong and you will have to learn the steps the hard way after the effect. Toolkits are good intentioned tools that should be avoided at all cost.

najoor said:
This error is the consequence of a " feature " of marshmallow that checks if your system is modified and issues this error message.
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
One last thing, not to rub it in for the gentlemen who posted the question but for other who are considering the easy way of using a toolkit, and please don't get offended by this. No one is against convenience but if you are unable or unwilling to learn few simple commands to unlock and unroot your phone you probably are not the type of user who needs to root the phone and chances are that after using a toolkit something will go wrong and you will have to learn the steps the hard way after the effect. Toolkits are good intentioned tools that should be avoided at all cost.
Click to expand...
Click to collapse
No offense taken I've rooted quite a few phones although I'm far from being an "expert". The toolkit was really just for convenience, and I went back to using it because it worked like a charm for the Nexus 5. It really was the go-to handy tool. To be sure: As I've stated above, I was able to recover the phone on my own. Still not rooted though, but I'm getting there. Sure, M is good enough on it's own, but frankly I can't wait to get back on a Cataclysm ROM.

najoor said:
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
Click to expand...
Click to collapse
Just LOVE how you explain it!
Wish more users will explain these kinds of things in such an "user friendly" way

I used the Chain Fire method and ended up in the same place. I can still access TWRP and fastboot, I am in the process of downloading the stock image.

fyrmd said:
I used the Chain Fire method and ended up in the same place. I can still access TWRP and fastboot, I am in the process of downloading the stock image.
Click to expand...
Click to collapse
You have to flash back to stock first. Marshmallow is checking for system mods, so if you don't undo the previous changes it will trigger again. Flash stock, twrp then 2.65 chainfire.

Caebron said:
No offense taken I've rooted quite a few phones although I'm far from being an "expert". The toolkit was really just for convenience, and I went back to using it because it worked like a charm for the Nexus 5. It really was the go-to handy tool. To be sure: As I've stated above, I was able to recover the phone on my own. Still not rooted though, but I'm getting there. Sure, M is good enough on it's own, but frankly I can't wait to get back on a Cataclysm ROM.
Click to expand...
Click to collapse
... You don't need to root to install a rom.
In fact, while installing the rom you will likely wipe your /system partition and any other partition you mess with to root....
What is it you think rooting actually does? Why are you doing it? What part do you think it will actually play in you installing a rom? Don't just do random ****. Learn what things do, so you can do what you want. This is why people hate toolkits. They promote this kinda of mentality where you just do stuff you don't understand in the slightest.

[ROOT][MM][NO UNLOCKING REQUIRED][ZE550KL] How to root ZE550KL on latest marshmallow?

If you tried rooting you ZE550KL then you must tried unlocking your device using official unlocker tool and you may faced force close. So here is how to root you asus ZE550KL without unlocking bootloader..
Prerequisite:
Download Latest TWRP from twrp.me Download
Download latest SuperSu Binary Download
Install Adb drivers and proper setup adb and fastboot. If you dont know how search on Google.
Lil Presence of mind
Lets start...
1- Connect your phone and type these command.
Code:
adb devices
and if it shows your device then issue this command after that
Code:
adb reboot bootloader
your device will reboot in bootloader.
2- Go to the directory where you placed downloaded twrp.img. Open command prompt here (shift + right click).
3- Flash the downloaded recovery
Code:
fastboot flash recovery twrp.img
4- When it said "finished" and there is no error. Then type this and press volume - (down) before screen lit up.
Code:
fastboot reboot
5- If you did correctly then you will see the TWRP logo.
6- If not let device boot and when it finished boot type these commands
Code:
adb reboot recovery
7- When twrp boots first step is to make a full backup of all.
8- Then copy Update-SuperSu-*-*.zip to your sd card or internal memory via MTP (available when twrp boots n phone connected with pc). Flash it.
9- If twrp ask for su binary update say no. and reboot
10- Boom you're rooted!!
Screenshots: (Unfortunately I cant record so i am atleast giving ss)
{
"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"
}
Video to get idea if this works.. ( I will surely upload a good video very soon!)
https://www.youtube.com/watch?v=B7iYTGKmb-g
Helpful Links:
StockBoot.img(Lollipop)- Because if you messed up you need to flash this and then have to download stock lollipop firmware and then sideload firmware from stockrecovery to get you phone working

Yeah, I updated yesterday my ZE551KL to Android M and as I didn't like it (some minimal changes) I chose to install the CM13.
But the unlocker didn't work. Ocurred the problem described in this post.
I will try this method later and post my result.
Update: the root worked!
Question: can I flash the CM rom without backing up the system? Because I got no space available for it in my microSD. What are the risks?

LOL
This is not a place to fool people.
Method works. Apologies to OP

xactor said:
3- Flash the downloaded recovery
Click to expand...
Click to collapse
I'm pretty new at this. Doesn't flashing require an unlocked bootloader? Most of what I read seems to indicate so, but maybe not on some devices? Can someone clarify?

moo.marc said:
I'm pretty new at this. Doesn't flashing require an unlocked bootloader? Most of what I read seems to indicate so, but maybe not on some devices? Can someone clarify?
Click to expand...
Click to collapse
Flashing any non-stock .img or zip requires unlocked bootloader. This guide will never work. It seems this guy made two accounts, one for writing the guide and one for posting that it worked. The OP is just trying to fool people, or may be he himself got fooled by somebody and he posted that guide here. Mods, This thread should be deleted.
Edit : Sorry for updating too late. This method works on locked bootloader. The img files are provided by a genius shakalaka. They are patched to match Asus signed img files. Thanks for writing this useful thread

Also confirmed working on ZE-551KL on my phone and my wife's phone!
Thank You!
Please most definitely follow this step: 4- When it said "finished" and there is no error. Then type this and press volume - (down) before screen lit up.
Code:
fastboot reboot
Definitely do the "Press volume down button" right after you hit (Enter)
This was sticking point because I didn't read carefully....

Hi, just try your method it work. My is ZE550KL 6.0.1
Aloso work on build : 21.40.1220.1708 too.
flash recovery with twrp version twrp-3.0.2-3-Z00L.img
and flash with UPDATE-SuperSU-v2.65-20151226141550.zip
BTW first time SuperSU installed but cannot work. So I try to flash again and got it work correctly.
New user cannot post outside link pls add manual open my attachment.
imgur.com/a/Ue6a8

Hello sir can u make avideo iam urgent for root please

No idea how this works
I have no idea how, but it worked! I (mostly) agree with sziraqui that flashing a recovery image with the device locked shouldn't work: I tried it before and the device would not load the bootloader after flashing, forcing me to re-flash the stock bootloader.
As mentioned by the OP, after flashing the marshmallow firmware (UL-Z00L-WW-21.40.1220.1708-user.zip) the unlock app crashed when unlocking. After that, I tried to flash TWRP and to my surprise it DID work! I also managed to flash supersu and test it with TitaniumBackup.
Since I would be skeptic myself, I'm attaching a picture that show's twrp and my terminal showing the that the bootloader reports as being locked.

I'm using marshmallow on my ZenFone 2 laser user_21.40.1220.1877 the latest stock firmware I'm not able to unlock it when I enter this command "fastboot boot ze550kltwrp.img in command prompt keeping my device into fastboot mode it shows error "you need to unlock your device to use this command"
How to unlock it plzz help
---------- Post added at 04:12 AM ---------- Previous post was at 03:31 AM ----------
How to unlock ZenFone 2 laser running on marshmallow latest build?
Plz suggest

ryt i have too same issue
How to unlock bootloader

abhinavze550kl said:
I'm using marshmallow on my ZenFone 2 laser user_21.40.1220.1877 the latest stock firmware I'm not able to unlock it when I enter this command "fastboot boot ze550kltwrp.img in command prompt keeping my device into fastboot mode it shows error "you need to unlock your device to use this command"
How to unlock it plzz help
---------- Post added at 04:12 AM ---------- Previous post was at 03:31 AM ----------
How to unlock ZenFone 2 laser running on marshmallow latest build?
Plz suggest
Click to expand...
Click to collapse
Just try to flash it .. fastboot boot didn't work for me too

sziraqui said:
LOL
This is not a place to fool people.
Click to expand...
Click to collapse
Definitely not..
Watch the video n clear me !
I agree flashing images requires a unlock bootloader. But sure it did flashed on an unlocked one. Mind helping me out why it worked bro??

sziraqui said:
Flashing any non-stock .img or zip requires unlocked bootloader. This guide will never work. It seems this guy made two accounts, one for writing the guide and one for posting that it worked. The OP is just trying to fool people, or may be he himself got fooled by somebody and he posted that guide here. Mods, This thread should be deleted.
Click to expand...
Click to collapse
Not everyone is free as you're.. sorry just kidding :laugh:

I tried it on my zenfone and it works fine...thank you
Hi,
i was searching for this since lots of time and i found ur post that without unlocking bootloader we can
flash a recovery img and also root it. I tried it and it is working fine in my ze550kl marshmallow.
I just want to install a cm 14.1 rom. It is possible? Pl answer.
Thank u again.

I always get this help!
decompressing ramdisk
failure, abort

deepakt6699 said:
Hi,
i was searching for this since lots of time and i found ur post that without unlocking bootloader we can
flash a recovery img and also root it. I tried it and it is working fine in my ze550kl marshmallow.
I just want to install a cm 14.1 rom. It is possible? Pl answer.
Thank u again.
Click to expand...
Click to collapse
See this thread..
http://forum.xda-developers.com/zenfone-2-laser/development/rom-resurrection-remix-n-t3509698/page48

it works with ZE551KL in stock 6.0.1 marshmallow follow the steps . very important the volume key down to start the recovery after reboot and then install the super su. this is the easiest method that i've found ..thanks

yas i cant unlock my asus zenf2 laser ze550kl I'm using marshmallow on my ZenFone 2 laser user_21.40.1220.1877 the latest stock firmware plez help
tnx xda its work but sum probs

Not working on asusz00ld on mm
Now worked

Potentially bricked device...is it fixable?

Hey guys,
I'll be honest...I'm a noob at all of this. I thought I would experiment with putting a custom ROM on an old Android phone I had (the SP), so googled around to find some guides on how to do it and tried to follow them. I successfully got the phone into fastboot (after using the Windows 8 driver workaround on Windows 10), and all seemed good. However, from then the issues (or what looked like them) started:
1. When entering into the bootloader (correct me if I'm wrong, but that's when you hold down the up volume as you connect it to the PC), the blue light would come on, but nothing would show on the screen. The guides I was looking at would suggest that the bootloader would load onto the screen. Was I just not loading into the bootloader?
However, I was still able to interact with the phone through the Cmd.exe, so something right was happening, so I pressed on (probably a mistake!) to attempt to install TWRP, as this was the next step in the guide I was following. This was where I ran into my next problem:
2. When trying to flash the TWRP.img to the recovery partition, I would get an error back saying the recovery partition could not be found. As far as I was concerned, there was also no way to verify whether the recovery partition was there or not, as I couldn't seem to load the bootloader either
Having googled around, I found an article that suggested I'd flash it to the boot partition instead, which I did. From that point, the device would no longer boot at all. It would enter fastboot/bootloader with the blue light, but unplugging the device and holding down the power button did nothing. At this point I decided "screw it" and decided to push on and see if I could install a ROM (I'd settled on LineageOS), so started following the steps, and flashed the Boot.img to the boot partition. The other instruction was to "flash the LineageOS zip from recovery", which I did not know how to do, and presumed was not possible, seeing as I thought I'd somehow broken that partition. At this point, the phone would turn on, the bar would flash green then red, and the Sony splashscreen would show. However, that is that would happen - it would stay frozen at that point. That is the point I'm at now
I appreciate that I've probably royally messed up this phone, and that's okay with me if that's the case - it was a learning experience. However, if this is recoverable, I'd really appreciate some help! I may be new to this, and not know much at all, but I want to try it, so if there is a way to get to a position where I can install TWRP and then flash a ROM to the phone, then please share your knowledge! I'm open to anything
Thanks in advance,
Meeb

MrMeeb said:
Hey guys,
I'll be honest...I'm a noob at all of this. I thought I would experiment with putting a custom ROM on an old Android phone I had (the SP), so googled around to find some guides on how to do it and tried to follow them. I successfully got the phone into fastboot (after using the Windows 8 driver workaround on Windows 10), and all seemed good. However, from then the issues (or what looked like them) started:
1. When entering into the bootloader (correct me if I'm wrong, but that's when you hold down the up volume as you connect it to the PC), the blue light would come on, but nothing would show on the screen. The guides I was looking at would suggest that the bootloader would load onto the screen. Was I just not loading into the bootloader?
However, I was still able to interact with the phone through the Cmd.exe, so something right was happening, so I pressed on (probably a mistake!) to attempt to install TWRP, as this was the next step in the guide I was following. This was where I ran into my next problem:
2. When trying to flash the TWRP.img to the recovery partition, I would get an error back saying the recovery partition could not be found. As far as I was concerned, there was also no way to verify whether the recovery partition was there or not, as I couldn't seem to load the bootloader either
Having googled around, I found an article that suggested I'd flash it to the boot partition instead, which I did. From that point, the device would no longer boot at all. It would enter fastboot/bootloader with the blue light, but unplugging the device and holding down the power button did nothing. At this point I decided "screw it" and decided to push on and see if I could install a ROM (I'd settled on LineageOS), so started following the steps, and flashed the Boot.img to the boot partition. The other instruction was to "flash the LineageOS zip from recovery", which I did not know how to do, and presumed was not possible, seeing as I thought I'd somehow broken that partition. At this point, the phone would turn on, the bar would flash green then red, and the Sony splashscreen would show. However, that is that would happen - it would stay frozen at that point. That is the point I'm at now
I appreciate that I've probably royally messed up this phone, and that's okay with me if that's the case - it was a learning experience. However, if this is recoverable, I'd really appreciate some help! I may be new to this, and not know much at all, but I want to try it, so if there is a way to get to a position where I can install TWRP and then flash a ROM to the phone, then please share your knowledge! I'm open to anything
Thanks in advance,
Meeb
Click to expand...
Click to collapse
First of all don't worry, Sony's phone doesn't brick that easy ?
All you need to do first is to repair your phone using official Xperia companion (Google how to repair your phone using Xperia companion).. After that you'll need to root your phone and unlock the bootloader to be able to install custom recovery like TWRP and use it to install any custom ROM.
Sent from my Xperia SP using Tapatalk

OsGhaly said:
First of all don't worry, Sony's phone doesn't brick that easy
All you need to do first is to repair your phone using official Xperia companion (Google how to repair your phone using Xperia companion).. After that you'll need to root your phone and unlock the bootloader to be able to install custom recovery like TWRP and use it to install any custom ROM.
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice! I successfully got it to the point of being rooted (using towelroot) and the bootloader unlocked, using flashtool. All seemed good. I then downloaded TWRP Manager, and tried to install TWRP, but it failed, which was an issue I faced before. To confirm my theory, I tried doing it using the CMD fastboot, and, using "fastboot flash recovery twrp.img", and was met with the same error as before - recovery partition not found. How am I supposed to install TWRP to the recovery partition if I don't have a recovery partition?

MrMeeb said:
Thanks for the advice! I successfully got it to the point of being rooted (using towelroot) and the bootloader unlocked, using flashtool. All seemed good. I then downloaded TWRP Manager, and tried to install TWRP, but it failed, which was an issue I faced before. To confirm my theory, I tried doing it using the CMD fastboot, and, using "fastboot flash recovery twrp.img", and was met with the same error as before - recovery partition not found. How am I supposed to install TWRP to the recovery partition if I don't have a recovery partition?
Click to expand...
Click to collapse
You're more than welcome dear, glad to hear you've successfully did it :good:
Concerning TWRP flash, you can try one of these:
1- Use rasher tool to flash the TWRP img (the easiest way).
2- Adb Sideload:
AdrianDC said:
HOW TO INSTALL MANUALLY TO FOTA :
* Bootimage : Download the TWRP bootimage you want to flash
* File storage : Adapt the path and push the file to the device this way :
Code:
adb root
adb wait-for-device
adb push FullPathToTheRecovery.img /tmp/twrp.img
* Flash : Extract the TWRP image to the FOTA partition
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
* Reboot to recovery : adb reboot recovery
​
Click to expand...
Click to collapse
3- Using terminal emulator app such as $cripter:
Place twrp.img in the root of your /sdcard folder then run the following commands using $cripter app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
P.S. You can download the latest TWRP from here

OsGhaly said:
You're more than welcome dear, glad to hear you've successfully did it :good:
(Rest cut as I'm not allowed to post external links)
[/CODE]
Click to expand...
Click to collapse
Hmm, Rashr does not seem to work - I select it to flash recovery, select my twrp.img, it says flashing then nothing happens. When booting to recovery, nothing shows, and it goes through to a normal boot. When trying to flash TWRP using the official TWRP app, it says it has flashed successfully, but again, no luck when booting into recovery mode. I don't really want to try either of the other two techniques, for fear of breaking things again. I've seen talk elsewhere that this isn't possible on the stock Kernel, which I'm on. Is that correct?

MrMeeb said:
Hmm, Rashr does not seem to work - I select it to flash recovery, select my twrp.img, it says flashing then nothing happens. When booting to recovery, nothing shows, and it goes through to a normal boot. When trying to flash TWRP using the official TWRP app, it says it has flashed successfully, but again, no luck when booting into recovery mode. I don't really want to try either of the other two techniques, for fear of breaking things again. I've seen talk elsewhere that this isn't possible on the stock Kernel, which I'm on. Is that correct?
Click to expand...
Click to collapse
Ok then, you can't use custom recovery with the stock kernel ofc. but we don't want that!.. you will install the TWRP recovery then reboot to it and install the new ROM without booting to the stock ROM at all.
1- Download TWRP and the ROM you want to flash for example Lineage OS.
2- Use the second method mentioned in my previous post by Adrian DC to install TWRP then boot into recovery -> wipe all then install LineageOS ROM + GApps.
-----
Another workaround is to install XZDualRecovery to have Philz touch and TWRP recoveries working alongside with the stock kernel and use it to install LineageOS ROM.

Hi bro
neva mind wat happened to u ,do as wat i say
First search n find the proper (stock .tft) file as per your country and version.
Download FLASHTOOL
now paste ur stock.tft file (around 1-2 gb) in flash folder
open flashtool and connect ur sick brick SP-Xepria in fastboot
install ur stock onces it done successfullly u wil get ur phone as stock .
i too bricked now im on andriod 7
no worries bro
---------- Post added at 09:31 AM ---------- Previous post was at 09:24 AM ----------
Hi everybody welcome to my tutorial about Flashing with Flashtool. This thread is for those who want to reflash their device back to Sony Stock. See below for last details about this thread and the last build by Sony.
Note: I DO NOT OWN THIS DEVICE ANYMORE. PICTURES ARE REMOVED FROM MY DROPBOX AND THUS NOT VISEBLE. FOR NOW JUST RELY ON THE EXPLANATION PLEASE. ANY QUESTION CAN BE ASKED HERE. I DO NOT RESPOND TO TECHMAIL!
Created: 23-02-2014
Updated: 05-07-2014
Latest Android build released by Sony: 12.1.A.1.205
Let's begin shall we.. We shall!
First you need to download the correct ftf file for your device/operator or needs. This can be done here: http://forum.xda-developers.com/show....php?t=2311964 In there you can share and download firmware files in .ftf format..
You alsol need a program called Flashtool. You can download this here: http://forum.xda-developers.com/showthread.php?t=920746
For Windows 8 and 8.1 users I also recommend you to read this thread: http://forum.xda-developers.com/show....php?t=2095087 Microsoft has enhanced the security in Windows 8/8.1 and Windows won't install proper signed drivers.
When you are done with that you need to move your downloaded firmware file to the proper location for flashtool to be found:
C:\Flashtool\Firmwares
After that you are good to go, just remember the following:
Bootloader locked? If not you wont have BE2/OTA/PCC etc (for unlocking and relocking: http://forum.xda-developers.com/show....php?t=2354721 )
I've made backups of my important files that are stored on my phone?
Battery at atleast 50%?
I have patience?
I got something to do meanwhile?
The last two things are very important
Let's get started:
1: Open Flashtool:
Flashtool(.exe) for 32Bits systems and Flashtool64(.exe) for 64Bits systems
2: Press the Lightningbolt picture and select Flashmode
This will give another screen.
3: Select the downloaded ftf. (In this case 2.254)
Make sure that all the wipes are checked and the others are unchecked. This is to prevent any bootloops or other problems after downgrading.
4: Press Flash and the next two lines will be added to the flashtool log
The files are being prepared and checked. Have a bit of patience please.
5: Turn off your phone and turn it back on into Flashmode
After this the process will start.
After flashing you can disconnect your phone and boot it up.
Via Flashtool you can also reset your system after. For example:
You are running the latest ExistenZe ROM from our beloved Niaboc79 and you want to go back to stock for a reason WITHOUT losing data! Just flash the last Stock ROM and untick the following boxes:
Untick DATA and APPSLOG!! But keep CACHE to wipe the /cache (is the same as a wipe cache via CWM).
FAQ
- My Phone wont stay into flashmode
> Turn it off, wait a few minutes and turn it back into flashmode
- Flashtool wont recognise my phone
> Make sure you have the proper drivers installed. See C://Flashtool/Drivers
- Flashing failed
> Problem depends on the error code given by Flashtool. Post the problem here and perhaps we can help
- Got a bootloop
> Reflash again
- Even after reflash I got into a bootloop
> Turn off your phone via the small button behind the batterycover and wait a few minutes. Then try again. If that doesnt work you need to flash again.
- Booting takes ages
> This is normal. The entire cache needs to be rebuild. Patience my dear..
- After flashing and booting my phone is laggy.
> Reboot device and wait a bit. The phone needs to fully reset and boot itself. Have some patience dear.
- Do I need to unlock my bootloader to use flashtool
> NO!
- Can I unlock my bootloader with flashtool?
> NO!
- Can I relock my bootloader with flashtool?
> Yes

You too have Sony.yt procedure with s1boot in the last case...

OsGhaly said:
Ok then, you can't use custom recovery with the stock kernel ofc. but we don't want that!.. you will install the TWRP recovery then reboot to it and install the new ROM without booting to the stock ROM at all.
1- Download TWRP and the ROM you want to flash for example Lineage OS.
2- Use the second method mentioned in my previous post by Adrian DC to install TWRP then boot into recovery -> wipe all then install LineageOS ROM + GApps.
Click to expand...
Click to collapse
Oh, okay! I'm trying to do the command as stated, but (while rooted with SuperSU installed) I get the error about adb not being able to run root in production builds. So, I enter the shell with adb shell type su, but then when i type exit and then adb root I get an error saying device not found, even though it shows up when typing adb devices before entering into SU (suggesting I have the correct drivers installed). However, when looking in Device Manager there's a yellow triangle next to the device, with an option to update drivers. Any advice? If I need to update the drivers, what drivers are they and were do I find them?
Edit: Picture as described -
{
"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"
}

MrMeeb said:
Oh, okay! I'm trying to do the command as stated, but (while rooted with SuperSU installed) I get the error about adb not being able to run root in production builds. So, I enter the shell with adb shell type su, but then when i type exit and then adb root I get an error saying device not found, even though it shows up when typing adb devices before entering into SU (suggesting I have the correct drivers installed). However, when looking in Device Manager there's a yellow triangle next to the device, with an option to update drivers. Any advice? If I need to update the drivers, what drivers are they and were do I find them?
Edit: Picture as described -
Click to expand...
Click to collapse
Uninstall any driver installed + Xperia companion then install ADB drivers from here:
http://adbdriver.com/downloads/
Here you can find a guide how to install ADB drivers on Windows 8 or 10:
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
Also make sure you have enabled USB Debugging from Developer options menu on your phone before connecting it to PC.

OsGhaly said:
Uninstall any driver installed + Xperia companion then install ADB drivers from here:
http://adbdriver.com/downloads/
Here you can find a guide how to install ADB drivers on Windows 8 or 10:
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
Also make sure you have enabled USB Debugging from Developer options menu on your phone before connecting it to PC.
Click to expand...
Click to collapse
Thank you! We've done it! I initially managed to install LineageOS using the developer TWRP that could be flashed to boot partition, but after that wanted to have TWRP with LineageOS. Thanks to your advice I just managed to install TWRP using FOTA, so now I have TWRP and LineageOS. Hallelujah! I've given you all the thanks I can on this thread

MrMeeb said:
Thank you! We've done it! I initially managed to install LineageOS using the developer TWRP that could be flashed to boot partition, but after that wanted to have TWRP with LineageOS. Thanks to your advice I just managed to install TWRP using FOTA, so now I have TWRP and LineageOS. Hallelujah! I've given you all the thanks I can on this thread
Click to expand...
Click to collapse
You're welcome dear, glad to hear that you finally got lineage os and TWRP on your phone.. Well done
Sent from my Xperia SP using Tapatalk

[GUIDE] How to ROOT the HTC Desire 10 Pro

Hello Everybody !!
I'm not a developer but I successfully rooted my HTC Desire 10 Pro and since many people seem to have problems,I decided to make a guide. The computer OS I used was Windows 10 but if you use linux, I'm sure you can adapt to the method.
1. First install device drivers and download ADB fastboot from this thread
2. Dowload TWRP 3.1 for your phone variant from here and move it to the ADB fastboot folder and rename the img file to "twrp"
twrp-3.1.1-a56dj_pro_uhl.img Desire 10 Pro Single SIM
twrp-3.1.0-a56dj_pro_dugl.img Desire 10 Pro Dual SIM
3. Press shift + right click and select open command window here.
4. Go to developer options on your phone and select Allow USB debugging and Allow bootloader to be unlocked.
(Very important step)
5. Connect the phone to your PC and check the connection by typing the following in the command prompt.
adb devices
If it shows only one device, you're good to go!!
Otherwise remove any other connected phones/devices and disable any Android emulators if you have them. (Like Bluestacks)
6. Go to HTCDev website and unlock your bootloader, (HTCDev will give those instructions), the phone model isn't shown but select "other supported models".
(Warning - This will erase all your data so make a backup)
7. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
8. Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp
9. Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot
10. Download SuperSu latest version
SuperSu v2.82
11. Copy the SuperSu zip file to your phone internal storage
12. Then type this command to go to TWRP,
fastboot reboot recovery
13. Wait for TWRP to load and tap Install
14. Select the SuperSu zip file and flash it
15. After flashing finishes, tap on Reboot System
16. Congradzz !!! Your HTC Desire 10 Pro is rooted now.
Now you can further customize if you like by installing Xposed.
Thanks for following and please reply in the comments if I have made any mistake or if you need more help.
And I'm NOT responsible for any damages even though it's unlikely to happen.
Edit : This was confirmed to be working on version 1.18.400.20 and it doesnt seem to work on 2.13.709.20. Please have a RUU if you're trying on a version in between, just to be on the safe side.
Credit to
@sabpprook and @jemmini for the TWRP variants
@Snoop05 for the ADB Fastboot Installer
@Chainfire for SuperSu
And all of XDA for being awesome ?

Any chance on doing a full backup before installing TWRP, as I don't have a default recovery of 1.18.400.20 dugl dual sim and still hope for OTA?
I hoped for "fastboot boot recovery" but I think only with nougat firmware was reimplemented.
Thanks

I think HTC disabled remote recovery booting so you'll have to replace the stock recovery.img
But I think I saw the stock recovery.img for our phone in another thread. You can download it and flash in case of a new update.
And what do u mean nougat firmware was reimplemented? Did you get the Nougat update ?

FireStorm919 said:
I think HTC disabled remote recovery booting so you'll have to replace the stock recovery.img
But I think I saw the stock recovery.img for our phone in another thread. You can download it and flash in case of a new update.
And what do u mean nougat firmware was reimplemented? Did you get the Nougat update ?
Click to expand...
Click to collapse
Can u redirect me to that stock recovery, pls?
The nougat firmware for the m9 had implemented boot to recovery...

process failed
Hi everyone,
tried this process on a A56DJ_PRO_DUGL with system OS-2.13.709.20 and the last step (supersu 2.82) failed, it said unable to modify boot image and aborted.
Used magisk 15 and it was able to modify boot but it did not boot, always asked for password for encrypted data, even after factory reset. I tried to restore the backup I previously made with twrp 3.1.1.0 (boot + system) but now it does not boot. Download, bootloader and twrp works anyway.
I will try to fix it, hope it serves as guidance to anyone trying to root the same 10 Pro version.

david_montes said:
Hi everyone,
tried this process on a A56DJ_PRO_DUGL with system OS-2.13.709.20 and the last step (supersu 2.82) failed, it said unable to modify boot image and aborted.
Used magisk 15 and it was able to modify boot but it did not boot, always asked for password for encrypted data, even after factory reset. I tried to restore the backup I previously made with twrp 3.1.1.0 (boot + system) but now it does not boot. Download, bootloader and twrp works anyway.
I will try to fix it, hope it serves as guidance to anyone trying to root the same 10 Pro version.
Click to expand...
Click to collapse
Try flashing the uninstall zip for magisk.
Also, if u have a backup, try to wipe boot and system partitions before restoring.
Good luck

Fain11 said:
Try flashing the uninstall zip for magisk.
Also, if u have a backup, try to wipe boot and system partitions before restoring.
Good luck
Click to expand...
Click to collapse
I did try to uninstall magisk but it gets stuck in the boot process (only htc logo), the same thing happens with the backup I made with twrp (only htc logo), the best result so far is applying magisk to the boot, then the system starts but keeps asking me to decrypt the storage, the exact message is "The password you have entered is correct, but unfortunately your data is corrupt" I did factory reset but does not solve the problem, it keeps asking for the password.
Also RUU for my OS-2.13.709.20 is not available so I'm currently stuck.
These things get harder and harder every day

Desire 10 Pro recovered
Finally the last option was to fully stock flash with RUU 2.13.709.20, but now I am back to step one.
At least it works
---------- Post added at 04:20 PM ---------- Previous post was at 04:08 PM ----------
Been human means to keep trying, so I tried again, now I did full factory wipe before applying supersu 2.82 (not working) or magisk 15 (works but keeps asking for a password to decrypt storage).
So I can confirm this procedure does not work with OS-2.1.3.709.20.
If any of you is able to root this version I will be glad to try again in the future but by now I'm done with htc 10 pro.
Happy new year everyone!

thanks for the guide, I was waiting for it and just came in time
I am wondering if this method will work on a56dj_pro_dugl software number 1.18.401.20 ?
what software number did you tried it on ?
thanks for the help

thekingomar said:
thanks for the guide, I was waiting for it and just came in time
I am wondering if this method will work on a56dj_pro_dugl software number 1.18.401.20 ?
what software number did you tried it on ?
thanks for the help
Click to expand...
Click to collapse
It has been confirmed to be working on 1.18.400.20
Please make a backup before u try because this doesnt seem to work on newer ones like 2.13.709.20
Please leave a reply here if u get it working.
?

Fain11 said:
Can u redirect me to that stock recovery, pls?
The nougat firmware for the m9 had implemented boot to recovery...
Click to expand...
Click to collapse
Sorry for the delay,
I couldn't find that link either so I extracted it from a RUU for variant a56dj_pro_dugl
Here you go
https://drive.google.com/file/d/1FxKDDOXISNTf5uQJT90nlw6tuClJaX9o/view?usp=drivesdk
Hope this helps
???

thanks for the guide again,
after pulling my courage together I decided to do it on my a56dj_pro_dugl software number 1.18.401.20
everything worked fine from the top to step 14 but there is one problem, flashing the SuperSU zip file is failed,
I tried to re-download it and not renaming it but still the same, here is the log
{
"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"
}
any suggestions ?

never mind
just rooted it using Magisk , apparently SuperSU is not applicable on my device
I used the same method as SuperSU zip
downloaded the latest version of Magisk (v 15.3) zip file and install it using TWRP
and everything is fine ever since
thanks folks for being awsome developers :laugh:

Required Video
Hi Member,
Can you please upload step by step video for root the HTC Desire 10 pro.
waiting

warnning !!! htc desire 10 pro os 2.13.709.23 taiwan
Don't try to root,
it seem rooted but no , if you wipe your soft brick, and difficult or impossible,
to fine the stosk rom os 2.13.709.23 !!!!
No body can help !!!

Mykyzo007 said:
Don't try to root,
it seem rooted but no , if you wipe your soft brick, and difficult or impossible,
to fine the stosk rom os 2.13.709.23 !!!!
No body can help !!!
Click to expand...
Click to collapse
Did you manage to unbrick?

yes
dearbasheer said:
Did you manage to unbrick?
Click to expand...
Click to collapse
yes i manage to unbrick, i'am waiting to see the rom .
But i need help

Unable to flash recovery
When unlocking bootloader I selected any other supported since desire 10 pro isn't listed. Process went through but when flashing twrp I'm getting error. Commad not allowed whereas it shows unlocked

FireStorm919 said:
Hello Everybody !!
I'm not a developer but I successfully rooted my HTC Desire 10 Pro and since many people seem to have problems,I decided to make a guide. The computer OS I used was Windows 10 but if you use linux, I'm sure you can adapt to the method.
1. First install device drivers and download ADB fastboot from this thread
2. Dowload TWRP 3.1 for your phone variant from here and move it to the ADB fastboot folder and rename the img file to "twrp"
twrp-3.1.1-a56dj_pro_uhl.img Desire 10 Pro Single SIM
twrp-3.1.0-a56dj_pro_dugl.img Desire 10 Pro Dual SIM
3. Press shift + right click and select open command window here.
4. Go to developer options on your phone and select Allow USB debugging and Allow bootloader to be unlocked.
(Very important step)
5. Connect the phone to your PC and check the connection by typing the following in the command prompt.
adb devices
If it shows only one device, you're good to go!!
Otherwise remove any other connected phones/devices and disable any Android emulators if you have them. (Like Bluestacks)
6. Go to HTCDev website and unlock your bootloader, (HTCDev will give those instructions), the phone model isn't shown but select "other supported models".
(Warning - This will erase all your data so make a backup)
7. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
8. Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery twrp
9. Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot
10. Download SuperSu latest version
SuperSu v2.82
11. Copy the SuperSu zip file to your phone internal storage
12. Then type this command to go to TWRP,
fastboot reboot recovery
13. Wait for TWRP to load and tap Install
14. Select the SuperSu zip file and flash it
15. After flashing finishes, tap on Reboot System
16. Congradzz !!! Your HTC Desire 10 Pro is rooted now.
Now you can further customize if you like by installing Xposed.
Thanks for following and please reply in the comments if I have made any mistake or if you need more help.
And I'm NOT responsible for any damages even though it's unlikely to happen.
Edit : This was confirmed to be working on version 1.18.400.20 and it doesnt seem to work on 2.13.709.20. Please have a RUU if you're trying on a version in between, just to be on the safe side.
Credit to
@sabpprook and @jemmini for the TWRP variants
@Snoop05 for the ADB Fastboot Installer
@Chainfire for SuperSu
And all of XDA for being awesome
Click to expand...
Click to collapse
Could u do me a favor ?
I just need an .apk from a system app called "sangam IME" it's a keyboard & u can extract the .apk with lucky patcher or any other similar apps
I need it like hell , caused I removed it & then realised it's the only keyboard that pops up in encryption page at startup & not having it means I can only reset my phone when I have a physical keyboard connected with otg ! Thanks alot

Sangam IME
seyyed.april said:
Could u do me a favor ?
I just need an .apk from a system app called "sangam IME" it's a keyboard & u can extract the .apk with lucky patcher or any other similar apps
I need it like hell , caused I removed it & then realised it's the only keyboard that pops up in encryption page at startup & not having it means I can only reset my phone when I have a physical keyboard connected with otg ! Thanks alot
Click to expand...
Click to collapse
Hi!
Sorry for the delay, I havent checked my inbox for quite some time.
I searched around for this Sangam IME everywhere in,
/system/app
/system/priv-app
/data/app
/data/app-private
But I couldnt find it. I even tried using 3rd party apps like you suggested but it simply doesnt seem to exist.
Even a quick Google search didnt give me any leads.
So are you sure the name is correct ?
Or maybe any more ideas on where to look for the apk ?
Sorry I couldnt be of more help

help rooting device with oreo 8.1

Hello,
I have this phone (infinix note 4 x572) running oreo 8.1 , build number :X572-H5312CE-O-180531V117
I wish to root it but after a while of searching i'm overly confused and frustrated..
can you please guide me through rooting it?
thanks alot

btw, does local update help in any way ?
{
"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"
}

All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.

Didgeridoohan said:
All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.
Click to expand...
Click to collapse
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?

and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?

yazansayed said:
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?
Click to expand...
Click to collapse
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
yazansayed said:
and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?
Click to expand...
Click to collapse
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...

Didgeridoohan said:
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
thanks alot for the quick responses, i will try it and reply as fast as possible

okay, i downloaded the twrp recovery image for Note 4, flashed it using Fastboot method successfully,
the problem is when i try to boot into the twrp recovery mode, i tried holding the power menu+ vol.down buttons, it sends me into a black screen with "factory mode" upwards in yellow, no button is working.
i then tried
Code:
adb reboot recovery
the phone reboots and says "No command" under a red triangle.
i then tried to flash the twrp img using sp flash tools, and flashed it successfully but the same errors occur, i can't seem to be able to boot into recovery mode.

i looked up for a solution for the "no command" problem, here's one:
I faced the same problem with nexus 6p. It works when you root immediately after flashing the TWRP. Keep the superSU file in the storage. Get into bootloader. Flash TWRP via fastboot. Without restarting anything, just press volume up/down buttons while in the bootloader to select recovery. TWRP will open. Flash the SuperSU.zip. Then restart the system. Next time, if you open recovery, you won't get the "no command". If you don't flash SuperSU and you try to open recovery later, you will get the "No command".
Click to expand...
Click to collapse
what i understood is that i shouldn't reboot my device using "fastboot reboot" , he says i should get into recovery mode directly without restarting, idk how to do that since there are no option for it on the screen, i just have
Code:
=> FASTBOOT mode...
on the screen !

Didgeridoohan said:
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
unfortunately i never used the sp flash tool before, so i tried flashing a stock rom but the device is now dead with "dram failed" error, i'll try fixing this first

It's tricky trying to help with a device you don't have...
Did you manage to boot to recovery? Usually you use the volume buttons to select the options and then the power button to confirm. You could also just use the fastboot boot option command I wrote earlier. It'll boot straight into TWRP.
There are a few threads for your device around, so if you need help specific to your device, that's the place to go...

everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot

the twrp from the post you provided is for an older firmware, this is why i couldn't get into recovery after i flashed the provided twrp img,, there is no available twrp for the oreo version of the firmware, but i requested one from twrp builder project,, thanks alot, i've learnt alot in the last 24 hours

yazansayed said:
everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot
Click to expand...
Click to collapse
could you upload the boot.img pls (the stock and the patched if possible )