Database Develop

[TWRP][J5 Pro 2017] twrp recovery j5 pro 2017

Unofficial release -TWRP recovery for the Galaxy SM-J530F, Exynos7870
{
"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"
}
this version just tested in J5 pro 2017 (android 7).
use latest kernel source from opensource.samsung.com
device tree : github
mtp not work in linux.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
http://www.mediafire.com/file/qpxypf08usashe4/twrp_v3.1.1_SM-J530F.tar
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/app...2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
http://www.mediafire.com/file/ln38z3q9c6iz3ny/patched-boot.tar

just putting my 2 cents in, this TWRP does not work with J530Y, it installs and boots to system after being installed but trying to reboot when you enter causes a boot loop incase any 1 comes across this and has the same model as me, my only complaint is the, debug? text in the terminal, but thats just a small gripe of mine

work in j530f duos 2GB RAM? no pro version?

twrp working fine.But when i rebooted i lost root.Super su not found installed .Should i reflash super su and boot image
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
akaluptos21 said:
work in j530f duos 2GB RAM? no pro version?
Click to expand...
Click to collapse
i installed on pro version.2017 sm530f/fd version

work fine thks

and now?
any custom rom for j530f?

akaluptos21 said:
and now?
any custom rom for j530f?
Click to expand...
Click to collapse
Recovery came out yesterday and you already expect a rom to be ready ?? lol

what would happen if I flashed this on a frp locked SM-J530F? I assume that the OEM Unlocking is disabled, is it worth a shot or is it just a waste of time?

Can't moun data on SM-J530F (J5 2017) (non Pro)
Dont forget Point 2.(Format Data)
Now boot.img is taking a long time to flash. Trying to flash it in AP slot of Odin.
There is not an option in TWRP to install image.

Adlbert said:
There is not an option in TWRP to install image.
Click to expand...
Click to collapse
I dont understand, TWRP dont see boot patch file. In odin i cannot do anything

davidescion said:
what would happen if I flashed this on a frp locked SM-J530F? I assume that the OEM Unlocking is disabled, is it worth a shot or is it just a waste of time?
Click to expand...
Click to collapse
Waste of time

CeloxX said:
I dont understand, TWRP dont see boot patch file. In odin i cannot do anything
Click to expand...
Click to collapse
Mine could not see it as well. Maybe you should convert .tar to .img? After some research i found out TWRP can't flash .tar.
Although, recovery works fine without patching boot.

i did the same but end up well.Its working !!.Mine was both OEM and FRP locked .i did clean install of stock rom and disabled oem lock and installed twrp and rooted aswell.
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
davidescion said:
what would happen if I flashed this on a frp locked SM-J530F? I assume that the OEM Unlocking is disabled, is it worth a shot or is it just a waste of time?
Click to expand...
Click to collapse
Adlbert said:
Mine could not see it as well. Maybe you should convert .tar to .img? After some research i found out TWRP can't flash .tar.
Although, recovery works fine without patching boot.
Click to expand...
Click to collapse
if u unzip that patch u would get .img and use that in twrp .

served in j5 Pro Sm-J530G?

FerXray13 said:
served in j5 Pro Sm-J530G?
Click to expand...
Click to collapse
check the model of the device according to the year

I root mine J530F yesterday and install twrp afterwords. It's working, but no 2/3/4G network anymore after flashing one of both.
Not possible to install boot image from twrp app. Also sound problems and brightness troubles.
I am going back to stock rom and wait for a while for a better later version.

Great news! :good:
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
bockywocky said:
I root mine J530F yesterday and install twrp afterwords. It's working, but no 2/3/4G network anymore after flashing one of both.
Not possible to install boot image from twrp app. Also sound problems and brightness troubles.
I am going back to stock rom and wait for a while for a better later version.
Click to expand...
Click to collapse
I think you have to do the inverse process. Flash twrp and after supersu

Oke I start from scratch again...
Flashed the stok ROM first.
Enable OEM and USB debugging
Flashed TWRP twrp_v3.1.1_SM-J530F with Odin3 v3.12.7 and disable Auto Reboot option.
Important: Reboot my phone holding Vol down, Home button, Power button AND when vibrate, Imminently pushed Vol up, Home button, Power button to go directly into TWRP.
Install Magisk-v14.0 (it fails, but just do it instead of installing SuperSU)
Boot my phone and restore al my apps from the play store include root checker. It has already root acces now
Install MagiskManager-v5.3.0.apk and dowload inside this app Magisk-v14.0.zip and choose Update (recommended)
With MagiskManager you are now able to disable root checking apps like SnapChat from root access. So my Snapchat is still working now
Hope this will help you.
If so than let me know with :good:
Bocky Wocky

bockywocky said:
Oke I start from scratch again...
Flashed the stok ROM first.
Enable OEM and USB debugging
Flashed TWRP twrp_v3.1.1_SM-J530F with Odin3 v3.12.7 and disable Auto Reboot option.
Important: Reboot my phone holding Vol down, Home button, Power button AND when vibrate, Imminently pushed Vol up, Home button, Power button to go directly into TWRP.
Install Magisk-v14.0 (it fails, but just do it instead of installing SuperSU)
Boot my phone and restore al my apps from the play store include root checker. It has already root acces now
Install MagiskManager-v5.3.0.apk and dowload inside this app Magisk-v14.0.zip and choose Update (recommended)
With MagiskManager you are now able to disable root checking apps like SnapChat from root access. So my Snapchat is still working now
Hope this will help you.
If so than let me know with :good:
Bocky Wocky
Click to expand...
Click to collapse
Hey
Do you Wipe Data before u Flash The Stock rom

Do I have to install on J5 2017 (no PRO)?

[ROOT][SM-T580/585&all Tabs A][CF-AUTO-ROOT][Simplest method to get ROOT & TWRP ]

[ROOT][SM-T580/585&all Tabs A][CF-AUTO-ROOT][Simplest method to get ROOT & TWRP ]
This is old method, not actual now. Please don't use it. Try to install magisk via TWRP.
For owners SM-T585 and SM-T580 : you can use this method https://forum.xda-developers.com/galaxy-tab-a/themes/mod-twrp-odin-t3650215
Hi folks . Dear @Chainfire update your CF-Auto-Root base and now we get opportunity to have root with the simplest method ! It works now on 6.0 and 7.0 stock firmwares . Sorry but knox is tripped .
Now this works on SM-T580 , SM-T585
Complete list you can see on https://autoroot.chainfire.eu/ .
HOW INSTALL :
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as AP.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin file, press the AP button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
After it, TWRP is installed via the official application https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl= very easy.
DOWNLOADS:
For 7.0 OS :
SM-T580
SM-T585
For 6.0 OS :
SM-T585 Not links , only my archiv
SM-T580 https://desktop.firmware.mobi/device:752
Update
Dear @Chainfire updated his thread CF-AUTO-ROOT and moved his repository to the new Firmware mobi site. Now you can configure your cf-auto-root for a specific firmware. More details and exactly on the site itself.
New links from firmware.mobi
For all OS.
For SM-T580
For SM-T585
Guide is inside archive. Read necessarily.

I only found 5 files inside the archive (CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip), no guide. It would be necessary for me

Ohto said:
I only found 5 files inside the archive (CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip), no guide. It would be necessary for me
Click to expand...
Click to collapse
Old guide is above in OP. CF-AUTO-ROOT have the new site now https://desktop.firmware.mobi/ .

Sorry I do not know what you mean by OP, but I found this and is exactly what I needed: https://android.gadgethacks.com/how-to/android-basics-root-with-cf-auto-root-0167401/

Update
Dear @Chainfire updated his thread CF-AUTO-ROOT and moved his repository to the new Firmware mobi site.
Click to expand...
Click to collapse
I tried with this image, but rooting did not happen. What am I doing wrong?
https://desktop.firmware.mobi/device:754/firmware:13433/download/boot_recovery.zip/landing
{
"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"
}

Ohto said:
I tried with this image, but rooting did not happen. What am I doing wrong?
https://desktop.firmware.mobi/device:754/firmware:13433/download/boot_recovery.zip/landing
Click to expand...
Click to collapse
Tick on checkbox autoreboot

I ticked it, Odin Passed, tablet rebooted, but "Root access is not properly installed".

Ohto said:
I ticked it, Odin Passed, tablet rebooted, but "Root access is not properly installed".
Click to expand...
Click to collapse
What the zip-archiv you tried? More little size.

samsung_sm-t585_gtaxlltexx_nrd90m.t585xxu2bqi9_boot_recovery.tar.md5
37,1 MB (38*994*019 bytes)
From here>
https://desktop.firmware.mobi/device:754/firmware:13433

https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip

https://desktop.firmware.mobi/device:754/firmware:13433/download/t0.cfar

Some kind of authentication failure. Device wants to restore original system.
---------- Post added at 06:00 PM ---------- Previous post was at 05:58 PM ----------
This time I did get the "installing supersu" text, but rooting did not go cleanly.
---------- Post added at 08:15 PM ---------- Previous post was at 08:00 PM ----------
Got it now, thanks!

hello? is samsung tab pro SM-P905 rootable? i tried several times rooting my tab and ended up in recovery error(bricked).

Weegang1911 said:
hello? is samsung tab pro SM-P905 rootable? i tried several times rooting my tab and ended up in recovery error(bricked).
Click to expand...
Click to collapse
This forum is for the Tab A. You need to post in the Galaxy Note Pro forum.

Can I load this with Heimdall instead of Odin. I'm running Ubuntu so Odin isn't an option for me. Thanks. I have a T-580.

repey6 said:
Hi folks . Dear @Chainfire update your CF-Auto-Root base and now we get opportunity to have root with the simplest method ! It works now on 6.0 and 7.0 stock firmwares . Sorry but knox is tripped .
Now this works on SM-T580 , SM-T585
Complete list you can see on https://autoroot.chainfire.eu/ .
HOW INSTALL :
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as AP.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin file, press the AP button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
After it, TWRP is installed via the official application https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl= very easy.
DOWNLOADS:
For 7.0 OS :
SM-T580
SM-T585
For 6.0 OS :
SM-T585 Not links , only my archiv
SM-T580 https://desktop.firmware.mobi/device:752
Guide is inside archive. Read necessarily.
Update
Dear @Chainfire updated his thread CF-AUTO-ROOT and moved his repository to the new Firmware mobi site. Now you can configure your cf-auto-root for a specific firmware. As I understand it, now when using cf-auto-root, there is no need to use patch no-verity-no-encrypt_ashyx after installing the TWRP. More details and exactly on the site itself.
Click to expand...
Click to collapse
I am a newcomer,
What is ODIN?
What is AP button?
Fffff I have no idea what everything here is
I really need some help../.

skerry2006aj said:
I am a newcomer,
What is ODIN?
What is AP button?
Fffff I have no idea what everything here is
I really need some help../.
Click to expand...
Click to collapse
Please read here https://samsungodin.com/
And Google help you

Ohto said:
Some kind of authentication failure. Device wants to restore original system.
---------- Post added at 06:00 PM ---------- Previous post was at 05:58 PM ----------
This time I did get the "installing supersu" text, but rooting did not go cleanly.
---------- Post added at 08:15 PM ---------- Previous post was at 08:00 PM ----------
Got it now, thanks!
Click to expand...
Click to collapse
i have the same problem. how did you solve it?
edit: I tried the procedure again and then all ok..

My question is, if in my developer options I do not have the OEM Unlock toggle but I still have a CF-AutoRoot that works for my device, is it actually unlocking my bootloader? I'm talking about the T-350 in this instance.
Because I have a T-560 which which does run the same MSM8916 board, yet still shipped with an unlocked bootloader. The size difference between the tablets is the only real difference I've seen between the 560 & 350.

Delgoth said:
My question is, if in my developer options I do not have the OEM Unlock toggle but I still have a CF-AutoRoot that works for my device, is it actually unlocking my bootloader? I'm talking about the T-350 in this instance.
Because I have a T-560 which which does run the same MSM8916 board, yet still shipped with an unlocked bootloader. The size difference between the tablets is the only real difference I've seen between the 560 & 350.
Click to expand...
Click to collapse
The T350 doesn't have a locked bootloader and neither does OEM UNLOCK unlock the bootloader on any Samsung device.

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 )

[RECOVERY][ROOT]TWRP 3.2.3-1 Galaxy A7 2018/A750

Unofficial release -TWRP recovery for the Galaxy A7 2018 - SM-A750F EXYNOS 7885
{
"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"
}
TWRP 3.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 25/12/2018
Beta build released.
Current status - (Tested working)
Treble supported
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot, uncheck AUTO-REBOOT and hit start.
twrp_3.2.3-1_a750_251218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
5. Reboot to TWRP (Do not boot to the OS yet)
*****OREO ROOT INSTRUCTIONS:*****
NOTE: To mount data it is necessary to first *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
Continue with the instructions below to prevent the data partition becoming re-encrypted.
1. To root I suggest downloading and installing the latest Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Copy the Magisk zip to a Micro sd card then install with TWRP.
3. Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @BlackMesa123 for RMM bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

158 views, 20 downloads and not one reply.
Smashing guys. :good:

4. перепрограммируйте обходной zip- архив rmm.можно поподробнее?
Mod edit: English please!
Google translation:
4. reprogram the rmm bypass zip archive. can you be more specific?

Odin shows Failed !! Tried 3 Times ? Had to Flash the Firmare Again.
Help !!

notoriouschyld said:
Odin shows Failed !! Tried 3 Times Had to Flash the Firmare Again.
Help !!
Click to expand...
Click to collapse
Sorry about that, build error on my end. Fixed now.

It will not work on SM-A750FNXXU1ARIC?

Sfuj24 said:
It will not work on SM-A750FNXXU1ARIC?
Click to expand...
Click to collapse
Is that a statement or question?

Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?

powermen27 said:
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
Click to expand...
Click to collapse
No matter how complete an instruction is, if you don't bother reading it in the first place it's not going to make any difference.
As clearly posted in the OP:
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Click to expand...
Click to collapse

sorry

ashyx said:
Sorry about that, build error on my end. Fixed now.
Click to expand...
Click to collapse
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!

notoriouschyld said:
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
Click to expand...
Click to collapse
Can you tell me which firmware build number you are running and if possible a screen shot of your device screen while booted to download mode?

Stuck in bootloop after flashing twrp
A750FXXU1ARK7

A7whatever said:
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
Click to expand...
Click to collapse
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
https://androidfilehost.com/?fid=11410963190603874542

ashyx said:
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
Click to expand...
Click to collapse
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number

A7whatever said:
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
Click to expand...
Click to collapse
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?

ashyx said:
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
Click to expand...
Click to collapse
Flashed the old sboot.bin however got the same bootloop

A7whatever said:
Flashed the old sboot.bin however got the same bootloop
Click to expand...
Click to collapse
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?

ashyx said:
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
Click to expand...
Click to collapse
Yes

A7whatever said:
Yes
Click to expand...
Click to collapse
Hmm looks like I'll have to take another look at the twrp config or kernel build.
If I pack the kernel into a boot image would you be willing to test if it boots?

Lenovo Z5s Update to ZUI 11.5 (Android 10)

Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.

Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.

{
"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"
}

carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier

jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!

links not works

vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.

Thank you very much

Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.

thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number

sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?

galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!

vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one

Install global via fastboot, all is included or in qfil ROM is all in zip file

vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again

i tired and failed again

galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably

carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it

hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?

galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot