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?
Related
Unofficial original release -TWRP recovery for the SM-A800I, Exynos5433
UPDATE 5/4/2016: TWRP 3.0.2-0 released
SEANDROID warning fix.
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
TWRP is now v3.0.2-0
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.
UPDATE: 12/3/2016
New feature available in TWRP 3.0.0-0 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
F2FS support added.
Internal SUPERSU root option removed. This is to prevent boot loops on 5.11/6.0 devices
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
NOTE: ON SOME 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.
twrp_3.0.2-0_sm-a800i
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the SuperSU zip below with TWRP.
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS OR YOU WILL BOOT LOOP, ONLY USE THE FILE BELOW:
http://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip
GUIDE
https://boycracked.com/2016/04/23/h...2-0-root-samsung-galaxy-a8-sm-a800i-sm-a800f/
DEVICE TREE: github.com
{
"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"
}
Credits: Me, Teamwin and my tester - abhinavparasher
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
.
Rooted/Custom recovery installed successfully
Please refer to the attachments.
are you flash a800f????
davod84 said:
are you flash a800f????
Click to expand...
Click to collapse
This version is only for sm-A800i. Do not flash it on any other model.
Do NOT flash it on A800F
does it work with a800iz ? i will try it now
edit : no , it's not working , it's get restart but no root, recovery working but its stick at bootloop
A . S said:
does it work with a800iz ? i will try it now
edit : no , it's not working , it's get restart but no root, recovery working but its stick at bootloop
Click to expand...
Click to collapse
You let supersu root your device which is why you have bootloop. ONLY use the file provided for root.
ashyx said:
You let supersu root your device which is why you have bootloop. ONLY use the file provided for root.
Click to expand...
Click to collapse
Your right ; my device is rooted now
Just do not twrp install supersu!
Sent from my SM-N910C using Tapatalk
Hello Everyone!. i experienced an issue with my rooting process. Now its stuck at the Samsung Galaxy A8 Logo with Red caption on top that says. Custom Binary Blocked by FRP lock. i tried flashing twrp that i downloaded from this thread but it failed with an error on my phone that says. Custom Binary(RECOVERY) Bloced by FRP Lock. I need your guidance, please help me.
ashyx said:
You let supersu root your device which is why you have bootloop. ONLY use the file provided for root.
Click to expand...
Click to collapse
Hi,
I sent you a DM. Coukd you take a look at it??
Thanks in advance.
Sent from my SM-A700F using XDA Free mobile app
rissered said:
Hello Everyone!. i experienced an issue with my rooting process. Now its stuck at the Samsung Galaxy A8 Logo with Red caption on top that says. Custom Binary Blocked by FRP lock. i tried flashing twrp that i downloaded from this thread but it failed with an error on my phone that says. Custom Binary(RECOVERY) Bloced by FRP Lock. I need your guidance, please help me.
Click to expand...
Click to collapse
u need to enable usb debugging & oem unlock from devlper option on phone setting first before start flash root file with odin..
Sent from my SM-A800I using Tapatalk
ryez88 said:
u need to enable usb debugging & oem unlock from devlper option on phone setting first before start flash root file with odin..
Click to expand...
Click to collapse
Yeah. That's what I did wrong. I turned the OEM Unlock off after a successful root. that was yesterday, but today after restarting my phone the frp lock triggered.
---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------
I guess what i need to do is to download the firmware from sammobile. when i go there i only see China and HongKong as country choices. my country isnt there and my fone says its from Vietnam.
rissered said:
Yeah. That's what I did wrong. I turned the OEM Unlock off after a successful root. that was yesterday, but today after restarting my phone the frp lock triggered.
---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------
I guess what i need to do is to download the firmware from sammobile. when i go there i only see China and HongKong as country choices. my country isnt there and my fone says its from Vietnam.
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/download/59917/A800IXXU1AOJ1_A800IOLB1AOJ1_XXV/
Hi @ashyx. i downloaded the firmware file that i need, while extracting it is giving me a WinRar error that the file is corrupted. I know the downloaded completed properly because i was checking the whole time.
Additionally i believe i do need the latest Samsung USB Drivers that will work for my phone. I can't find it here.
Any tips would be great. and again, thanks a lot for the help
rissered said:
Hi @ashyx. i downloaded the firmware file that i need, while extracting it is giving me a WinRar error that the file is corrupted. I know the downloaded completed properly because i was checking the whole time.
Additionally i believe i do need the latest Samsung USB Drivers that will work for my phone. I can't find it here.
Any tips would be great. and again, thanks a lot for the help
Click to expand...
Click to collapse
Was the file in .rar/.zip format or did it end in .tar/.tar.md5?
Also, usb drivers can be found on samsungs official website for your country.
Most of the times, usb drivers do not need to be downloaded seperately if you are using an updated windows system.
Plug in your phone in download mode and start up odin. If the "com port" turns green, your phone is detected successfully.
Thanks for replying @abhinavparasher it was in zip file but when i extract it its in tar.md5. even when the error stating that the file is corrupted appears the whole extraction process still completes itself. and i already downloaded the USB driver and hope this works
rissered said:
Hi @ashyx. i downloaded the firmware file that i need, while extracting it is giving me a WinRar error that the file is corrupted. I know the downloaded completed properly because i was checking the whole time.
Additionally i believe i do need the latest Samsung USB Drivers that will work for my phone. I can't find it here.
Any tips would be great. and again, thanks a lot for the help
Click to expand...
Click to collapse
Use 7zip to extract it not Winrar.
If it says corrupted again then the download is not complete.
USB driver: http://developer.samsung.com/technical-doc/view.do?v=T000000117
Also you say your phone is made in Vietnam.
Samsung manufacturer their devices in Vietnam and Korea so that doesn't mean that's the firmware you need.
If you are from the Philippines then download the firmware for the Philippines.
www.sammobile.com/firmwares/database/SM-A800I
There is an app called Samsung phone info that will tell you everything you need to know about your device.
@ashyx thanks! i pre downloaded the Stock Firmware from the Philippines. i chose Openline since it is indeed openline. That is also the file that says it is corrupted when i try to extract it. I am downloading 7zip right now. I'll update you as soon as i get somewhere with this.
I would lie to try the Samsung app you're talking about but right now the only thing happening to my phone is go to logo screen then turn off again.
hi i flashed the twrp .do i flash supersu with odin? my phone:a800i/5.1.1
mohannad22 said:
hi i flashed the twrp .do i flash supersu with odin? my phone:a800i/5.1.1
Click to expand...
Click to collapse
TWRP.
Sent from my HTC One_M8 using XDA Free mobile app
https://github.com/ashyx/TWRP_Samsung_Galaxy_a8hplte/pulls
Please accept those changes
Unofficial release -TWRP recovery for the Galaxy J7- SM-J700T/T1, Exynos7580
{
"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"
}
Update 20/11/2017
TWRP 3.1.1-1 NN build released.
Update 20/2/2017
TWRP 3.0.3-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
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.
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.
NOUGAT DOWNLOAD:
twrp_3.1.1-0_sm-j700t_201117
MARSHMALLOW DOWNLOAD:
twrp_3.0.3-1_sm-j700t_23217
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage /DATA:
(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
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, @slipk487, Teamwin
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
.
.
Bootlooped on my j700t1
slipk487 said:
Bootlooped on my j700t1
Click to expand...
Click to collapse
Is your firmware up to date, the kernel is built using the latest sources?
i believe im fully updated
slipk487 said:
i believe im fully updated
Click to expand...
Click to collapse
Seems so, would you be willing to be contacted via PM?
I'm fairly sure this is a kernel issue and would like to PM you links to test builds.
ye no problem. that was the stock kerenrl i have yet to try it on mira kernel.
slipk487 said:
ye no problem. that was the stock kerenrl i have yet to try it on mira kernel.
Click to expand...
Click to collapse
Shouldn't really matter which boot kernel is being used. P.M sent
Thank you for this! Can't wait for the working build.
vekenti said:
Thank you for this! Can't wait for the working build.
Click to expand...
Click to collapse
We have it working, hopefully there will be an update at some point today.
Thanks for being involved in this. I hope to donate soon.
Just updated to this phone on metropcs prepaid 4 days ago..from a Samsung galaxy s4..
I like it, but I'm noticing some things I still need.
I'll message you soon ash, just to let you know I've donated via paypal
I'll test for you ash.
Metabolic12 said:
I'll test for you ash.
Click to expand...
Click to collapse
I will also test. J700T.
Metabolic12 said:
I'll test for you ash.
Click to expand...
Click to collapse
Dustinsk22 said:
I will also test. J700T.
Click to expand...
Click to collapse
Fixed build up: https://forum.xda-developers.com/ga...y-galaxy-j7-sm-j700t-t1-t3560342/post71151450
.
ashyx said:
Fixed build up: https://forum.xda-developers.com/ga...y-galaxy-j7-sm-j700t-t1-t3560342/post71151450
.
Click to expand...
Click to collapse
Darn in have to wait until I'm home to flash. Unless flashfire will work? If I had my other phone I would just do it.
Dustinsk22 said:
Darn in have to wait until I'm home to flash. Unless flashfire will work? If I had my other phone I would just do it.
Click to expand...
Click to collapse
You can extract the recovery.img from the tar archive and flash with twrp or flash the tar archive with flashfire.
ashyx said:
You can extract the recovery.img from the tar archive and flash with twrp or flash the tar archive with flashfire.
Click to expand...
Click to collapse
I'm booting to recovery now. If I'm not back in 10 or less, assume this J7 turned into a radioactive tornado and wiped Indiana off the planet.
Metabolic12 said:
I'm booting to recovery now. If I'm not back in 10 or less, assume this J7 turned into a radioactive tornado and wiped Indiana off the planet.
Click to expand...
Click to collapse
Oh gee, looks like Indiana got wiped
ashyx said:
Oh gee, looks like Indiana got wiped
Click to expand...
Click to collapse
If only it was that easy, I even put my full body suit on :cyclops:
Full boot running on bootloader APK6. TWRP boots and mounts all available partitions. I'll test USB in a little bit when I get home. Congrats brother and thank you.
We have twrp and good boot. Thnx for this again and again.
I dont suppose someone could post a recovery log from TWRP so I can look it over?
ADVANCED>SAVE RECOVERY LOG
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
Hi Guys!
Since there is no deeptest.apk available for our device to unlock bootloader, we came up with another method to unlock bootloader unofficially!
In this guide I'll tell you how to unlock bootloader, root with magisk and flash TWRP on your Realme 8i/Narzo 50 (RMX3151/RMX3286)
Code:
/*
* This Guide is tested and working
* However I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about unlocking and flashing TWRP
* before flashing it! YOU are choosing to make these modifications.
*/
1. UNLOCKING BOOTLOADER:
Requirements
PC or Laptop
Internet connection
Realme 8i/Narzo 50
USB cable
Working Brain
Take a backup of your data since it'll be wiped
Go to About phone > Version and tap build number 7 times
Go to Settings > advanced settings > Developer options and turn on OEM unlocking and USB debugging
STEPS
Install Python from windows store
Install USBDk
Download this and extract : https://github.com/bkerler/mtkclient/archive/refs/heads/main.zip
Download vbmeta and patched boot image (Download for your respective version) in copy to the mtkclient-main folder
Now open command prompt or powershell in that folder
{
"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"
}
Now type pip3 install -r requirements.txt and hit enter
Now type python mtk e metadata,userdata,md_udc hit enter - This command wipes data
Then power off your phone and hold both volume buttons and connect usb cable (DON'T LEAVE THE BUTTONS, KEEP THEM HOLDING THROUGHOUT THE PROCESS) - This boots device into BROM mode
Now type python mtk da seccfg unlock This will unlock the bootloader (If you face waiting for device issue then unplug the device and plug in the device again with holding volume buttons, also don't leave the buttons)
After this unplug your phone and turn it on (It'll show your device dm verity corrupted and first boot might take 20-25 mins, don't panic)
Now your bootloader is unlocked
Due to realme's limitations you still can't access fastboot after unlocking via this method
2. ROOTING YOUR DEVICE:
Install This Magisk apk
Now in pc type python mtk w boot,vbmeta boot.patched,vbmeta.img.empty hit enter
Then power off your phone and connect usb while holding both volume buttons (and don't leave them)
Now disconnect and reboot phone
Now open magisk
3. FLASHING TWRP RECOVERY:
Download TWRP - From here
Download and install Flashify app
Open Flashify and grant root permission
Select Recovery image and install the twrp you have downloaded
After flashing is done click reboot now or you can reboot to recovery via magisk app
"Congrats Now we have working TWRP in our Realme 8i/Narzo 50"
Credits:
Me (@pritish1998) for TWRP, Unlock and Flashing guide
B Kerler fot MTKClient
Rohit for testing
Stock boot Images (to revert root)
If you face any issues contact me here
Thanks for the detailed guide, hope we get kernel sources soon..
sany.svenson said:
Добрый вечер.А как теперь заблокировать загрузчик,подскажите пожалуйста.
Click to expand...
Click to collapse
English is required, you can use your native language too, adding it to your post.
Inside the tool is provided a README.md file with basic instructions and usage. To relock bootloader you can use python mtk xflash seccfg lock just be careful to not relock it while running custom binaries, you have to return completely back to stock prior to do that.
After using boot.img from this topic wifi is dead! Now I need original boot to patch it. My firmware is A20. Somebody help!
DimaS_EKB said:
After using boot.img from this topic wifi is dead! Now I need original boot to patch it. My firmware is A20. Somebody help!
Click to expand...
Click to collapse
The provided boot image is from A30... Why are u still using A20?
I didn't know about A20 or A30 or anything. You should have mentioined this! Better off dump user's own boot.img and patch it with magisk. Now I have problems. It is good that I've found A20 firmware but it was not easy, I've lost a lot of time to read about firmwares, patching etc.
DimaS_EKB said:
I didn't know about A20 or A30 or anything. You should have mentioined this! Better off dump user's own boot.img and patch it with magisk. Now I have problems. It is good that I've found A20 firmware but it was not easy, I've lost a lot of time to read about firmwares, patching etc.
Click to expand...
Click to collapse
Download stock boot image from here I've saved them https://mega.nz/folder/BvpwibLB#lDDAbRG5SMKS4ucdj1dELg
Also there is nothing to mention at the time of making this guide almost everyone was updated to A.30, but no problem now I've updated the link for all patched boot images
recovered, thanks
now I'm updating to A32
what's next?
download your patched boot image for A32? and that's all?
DimaS_EKB said:
recovered, thanks
now I'm updating to A32
what's next?
download your patched boot image for A32? and that's all?
Click to expand...
Click to collapse
Yes
pritish1998 said:
Yes
Click to expand...
Click to collapse
Sorry but it appears I cannot update. I tried original and modified boot.img, also I installed original recovery. It doesn't help. The phone downloads the A32 firmware, reboots and cannot start recovery mode to update the firmware.
DimaS_EKB said:
Sorry but it appears I cannot update. I tried original and modified boot.img, also I installed original recovery. It doesn't help. The phone downloads the A32 firmware, reboots and cannot start recovery mode to update the firmware.
Click to expand...
Click to collapse
Flash stock boot, vbmeta and recovery then format data then reboot
If I flash stock vbmeta it cannot boot. Is that ok? Should I erase data anyway?
DimaS_EKB said:
If I flash stock vbmeta it cannot boot. Is that ok? Should I erase data anyway?
Click to expand...
Click to collapse
Yes
pritish1998 said:
Yes
Click to expand...
Click to collapse
Format data
Thanks! Now everything works fine!
pritish1998 said:
Download stock boot image from here I've saved them https://mega.nz/folder/BvpwibLB#lDDAbRG5SMKS4ucdj1dELg
Also there is nothing to mention at the time of making this guide almost everyone was updated to A.30, but no problem now I've updated the link for all patched boot images
Click to expand...
Click to collapse
how to flash stock boot image?
bobongros said:
how to flash stock boot image?
Click to expand...
Click to collapse
python mtk w boot boot.img
pritish1998 said:
python mtk w boot boot.img
Click to expand...
Click to collapse
can i dm you? please help me my phone is bricked
bobongros said:
can i dm you? please help me my phone is bricked
Click to expand...
Click to collapse
How did your phone brick?
{
"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"
}
Disclaimer:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
I am not the developer.
Developer: @naz664
Changelog:
Spoiler: View
Changelog :-
- Souls recovery with latest A12 support (Jan 2023)
- Updated kernel
- This recovery won't work on older stock version
So don't flash this unless you are running latest jan 2023 stock rom
How to install?
Spoiler: ODIN (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + Bixby key + USB cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this, Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
TWRP Source: GitHub
Credits:
Soul reaper
Nazim
Lmao
Max B
Darshana & Encrypted for testing
Important:
This version only works on the latest update of stock rom (M215FXXU3CWB1) and above. If you are running an older version, use the previous build of TWRP.
Download: Link
И что делать ?
w1nk1 said:
И что делать ?
Click to expand...
Click to collapse
Different device?
Hi Fredin friend,
I Recently upgraded SM-M215G device to OneUi5.1 (M215GDDS3CWD1-20230522142126) Binary 3 and TWRP (twrp-3-5-2-m21-v3-1-a12-tar)but anything I am flashing is either bootlooping or stuck on Rom Logo, I flashed (Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip) still only Rom Logo showing, how to boot the GSIs? Any help appreciated.
OldNoobOne said:
Hi Fredin friend,
I Recently upgraded SM-M215G device to OneUi5.1 (M215GDDS3CWD1-20230522142126) Binary 3 and TWRP (twrp-3-5-2-m21-v3-1-a12-tar)but anything I am flashing is either bootlooping or stuck on Rom Logo, I flashed (Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip) still only Rom Logo showing, how to boot the GSIs? Any help appreciated.
Click to expand...
Click to collapse
Hi
If you had unencrypted data (if you could see files in internal storage) and flashed the latest stock rom, but you didn't flash encryption/multi disabler before the first boot into OneUI, it will probably cause problems.
So try formatting data and flash encryption/multi disabler (although I believe dm verity disabler also disables encryption by default, but it won't hurt flashing them). Or you can format data and not flash anything to let data stay encrypted, but then you won't be able to use the internal storage in TWRP.
Fredin_ said:
Hi
If you had unencrypted data (if you could see files in internal storage) and flashed the latest stock rom, but you didn't flash encryption/multi disabler before the first boot into OneUI, it will probably cause problems.
So try formatting data and flash encryption/multi disabler (although I believe dm verity disabler also disables encryption by default, but it won't hurt flashing them). Or you can format data and not flash anything to let data stay encrypted, but then you won't be able to use the internal storage in TWRP.
Click to expand...
Click to collapse
Hi friend Fredin,
Thanks for the reply.
I used (twrp-3-5-2-m21-v3-1-a12-tar) and it is smooth (just like previous Soulr-A11 twrp) but sideload did not work while the other recovery (TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) by Dev Ravindu Deshan works great too but Reboot to Recovery does not work properly all the time, so sometimes instead of Reboot to Recovery the changes happen when manually reboot to recovery using usb cable also sometimes it does not recognise pen drive. Till now I only managed to boot Tuki1.2 and the other Lineage 20 zip had Oplist error 1 issue. Hoping for GSI boot too later. Thanks for recovery
OldNoobOne said:
Hi friend Fredin,
Thanks for the reply.
I used (twrp-3-5-2-m21-v3-1-a12-tar) and it is smooth (just like previous Soulr-A11 twrp) but sideload did not work while the other recovery (TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) by Dev Ravindu Deshan works great too but Reboot to Recovery does not work properly all the time, so sometimes instead of Reboot to Recovery the changes happen when manually reboot to recovery using usb cable also sometimes it does not recognise pen drive. Till now I only managed to boot Tuki1.2 and the other Lineage 20 zip had Oplist error 1 issue. Hoping for GSI boot too later. Thanks for recovery
Click to expand...
Click to collapse
I'm not the dev btw, @naz664 is
Fredin_ said:
I'm not the dev btw, @naz664 is
Click to expand...
Click to collapse
Hi Friend,
Naz Roms great also
sidetalk: Do you know how to unlock CWD1 Stock Rom bootloader? my bootloader isnt unlocked fully? And in Shaomi phones which model would you recommend, it has fastboot so.
OldNoobOne said:
Hi Friend,
Naz Roms great also
sidetalk: Do you know how to unlock CWD1 Stock Rom bootloader? my bootloader isnt unlocked fully? And in Shaomi phones which model would you recommend, it has fastboot so.
Click to expand...
Click to collapse
What do you mean by it's not fully unlocked? iirc the toggle stays like that once the bootloader is unlocked.
Fredin_ said:
What do you mean by it's not fully unlocked? iirc the toggle stays like that once the bootloader is unlocked.
Click to expand...
Click to collapse
Hi Friend,
When I had unlocked the bootloader of the same device while it had A11 loaded in it, the oem unlock button was TOTALLY GREYED OUT (I swear I'm not lying), I mean even the toggle button was greyed out but in above picture you can see toggle buttons are Blue color and oem-unlock toggle button is light-blue but not fully greyed out, I didnt relock my bootloader before flashing A13 Stock CWD1 update
Now I cant flash GSI they refuse to boot always stuck on bootlogo.
OldNoobOne said:
Hi Friend,
When I had unlocked the bootloader of the same device while it had A11 loaded in it, the oem unlock button was TOTALLY GREYED OUT (I swear I'm not lying), I mean even the toggle button was greyed out but in above picture you can see toggle buttons are Blue color and oem-unlock toggle button is light-blue but not fully greyed out, I didnt relock my bootloader before flashing A13 Stock CWD1 update
Now I cant flash GSI they refuse to boot always stuck on bootlogo.
Click to expand...
Click to collapse
Don't think there is any in between state. If you can flash stuff, your bootloader is unlocked. If the GSI is not booting, that's some other issue. Try the new AOSP ROMs instead.
A51 Builds by Royna - Browse Files at SourceForge.net
sourceforge.net
Fredin_ said:
Don't think there is any in between state. If you can flash stuff, your bootloader is unlocked. If the GSI is not booting, that's some other issue. Try the new AOSP ROMs instead.
A51 Builds by Royna - Browse Files at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
Thanks Friend,
It looks like Royna's ROM zips (Lineage 20 & evolution_m21-ota-tq2b.230505.005.a1-06050648-community-unsigned.zip & crDroidAndroid-13.0-20230427-m21-v9.4.zip) not flashing, reason - TWRP error : 1 Assert failed : update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list") and repartition issue even while sideloading. The only one that boots is TukiRom1.2, I havent tried Tuki1.3 yet. I tried Roynas' TWRP files too but after boot to recovery they get stuck, the other TWRP files (TWRP-3.5.2-m21-v3.1-A12.tar & TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) boot and work with some issues though.