I'll tell short version.
First I flash s9+ with ArrowOS based on android 12. I won't liked it and decided to flash something else. Then I noticed that I can't downgrade bootloader so I could't go back to stock rom (android 10).
Therefore I flashed LineageOS with TRWP. Flashing was going fine before phone decides to boot itself right after I entered google account.
Now phone won't boot anymore in recovery mode because frp lock is on and I can't flash stock rom with Odin because bootloader was updated when installing ArrowOS. Also Windows won't regocnise phone because usb debugging is off.
Now I can only enter download mode where I can't install anything. Is there any way to bypass hardbrick and flash OS? Thanks.
You could flash a recovery using ODIN.
How to Install TWRP Recovery using Odin on Samsung Android devices
Odin is a PC software used internally at all Samsung service centers for updating/flashing Firmware to Samsung devices. This software was never meant to go public but thanks to the growing world of…
nerdschalk.com
mcxurxo said:
You could flash a recovery using ODIN.
How to Install TWRP Recovery using Odin on Samsung Android devices
Odin is a PC software used internally at all Samsung service centers for updating/flashing Firmware to Samsung devices. This software was never meant to go public but thanks to the growing world of…
nerdschalk.com
Click to expand...
Click to collapse
I can't flash twrp with odin because frp lock. In download mode it says that "Custom binary(RECOVERY) Blocked by FRP lock" when I try to flash it and ODIN fails.
juuko12 said:
I'll tell short version.
First I flash s9+ with ArrowOS based on android 12. I won't liked it and decided to flash something else. Then I noticed that I can't downgrade bootloader so I could't go back to stock rom (android 10).
Therefore I flashed LineageOS with TRWP. Flashing was going fine before phone decides to boot itself right after I entered google account.
Now phone won't boot anymore in recovery mode because frp lock is on and I can't flash stock rom with Odin because bootloader was updated when installing ArrowOS. Also Windows won't regocnise phone because usb debugging is off.
Now I can only enter download mode where I can't install anything. Is there any way to bypass hardbrick and flash OS? Thanks.
Click to expand...
Click to collapse
I think that you could try reinstalling the official stock rom. Doing so you should be able to boot and unlock the bootloader again.
Flashing the latest official stock rom fails. The result is "sw rev check fail (bootloader) device 17, binary 15. I think that bootloader was updated when flashing ArrowOS.
juuko12 said:
I'll tell short version.
First I flash s9+ with ArrowOS based on android 12. I won't liked it and decided to flash something else. Then I noticed that I can't downgrade bootloader so I could't go back to stock rom (android 10).
Therefore I flashed LineageOS with TRWP. Flashing was going fine before phone decides to boot itself right after I entered google account.
Now phone won't boot anymore in recovery mode because frp lock is on and I can't flash stock rom with Odin because bootloader was updated when installing ArrowOS. Also Windows won't regocnise phone because usb debugging is off.
Now I can only enter download mode where I can't install anything. Is there any way to bypass hardbrick and flash OS? Thanks.
Click to expand...
Click to collapse
Flash first with odin only Ap file from firmware oficiale,after that normal installation with all files,good luck.
I'm sorry for my bad EnglishI hope you understood me
adryan_coco said:
Flash first with odin only Ap file from firmware oficiale,after that normal installation with all files,good luck.
Click to expand...
Click to collapse
It ended with the same error than before.. Only this time it fails to recovery "kernel rev check fail: device 17, binary 15 (bootloader)".
I think that I really can't flash the stock firmware. Is there a way to do combined file and flash it with odin?
juuko12 said:
It ended with the same error than before.. Only this time it fails to recovery "kernel rev check fail: device 17, binary 15 (bootloader)".
I think that I really can't flash the stock firmware. Is there a way to do combined file and flash it with odin?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/convert-twrp-img-to-tar-for-odin-easy.3355944/
Give it a try!
All attemps fails the same way: binary error: device 17, binary 15. I'm out of ideas.
Have you tried asking help on ArrowOS about this one?
I think that only way to revive this phone is to flash stock rom with Odin. Only problem is the binary error that came from arrowOS based on android 12.
If some knows how to do bypass biary error, let me know.
I finaali got it work. From the day one the reason was the wrong stock rom. I still don't know how I got it wrong at first place.
Binary 17 is rev H. With that version I flashed the phone with Odin and everything worked normally.
{
"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"
}
juuko12 said:
I finaali got it work. From the day one the reason was the wrong stock rom. I still don't know how I got it wrong at first place.
Binary 17 is rev H. With that version I flashed the phone with Odin and everything worked normally.
View attachment 5577225
Click to expand...
Click to collapse
My device also says device 17 binary 7 when flashing stock android 10 stock rom. Pls help
Google the AP version in the picture and check that rev version is H. And of course the region also.
Download Galaxy S9+ SM-G965F (SEB) G965FXXSHFUJ2 in Samfw - Samsung firmware download
Galaxy S9+ SM-G965F (SEB - Baltic) G965FXXSHFUJ2 Q(Android 10) samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅
samfw.com
juuko12 said:
Google the AP version in the picture and check that rev version is H. And of course the region also.
Download Galaxy S9+ SM-G965F (SEB) G965FXXSHFUJ2 in Samfw - Samsung firmware download
Galaxy S9+ SM-G965F (SEB - Baltic) G965FXXSHFUJ2 Q(Android 10) samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅
samfw.com
Click to expand...
Click to collapse
Thanks. Appreciate that. I will try . This website is better than Sammobile. It provides better instructions
juuko12 said:
G
Click to expand...
Click to collapse
juko hey i have sm-g965u1 i cant find any root method if you know something please help me
when I could not unlock the bootloader, I put the phone into airplane mode (disconnected from all networks) then moved the date forward a month and rebooted the phone. Then in the developer options, I got the option to enable the bootloader. After using SmartSwitch on the computer, I restored the phone through the "Disaster Recovery" mode
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
Hi everyone. Last week I tried to root (successfully) my Tab S2 to make it work with Samsung Gear Smartwatch. Using an application I changed the "model-name" of my tablet from SM-T719 to SM-N910F (Note 4) to make it recognizable by Gear.
My father accidentally disabled "OEM unlock" and then, when I've rebooted it, it was written "Custom binary blocked by FRP lock".
I tried to install the stock ROM (different versions of it) using Odin, but it didn't work (it have always stuck at "system.img.ext4")
Besides, I cannot install TWRP Recovery because when I try to install it via Odin the phone says "SECURE CHECK FAIL: recovery" and "Custom Binary (recovery) Blocked by FRP Lock"
My recovery mode doesn't let me install anything ("Update from external storage is disabled")
So, I'm not able to install the OS. Can anyone help me?
Are you under warranty?
No, I'm not because of having rooted it. The repair center says that I have to change the Motherboard. I'm not sure of this, is it possible?
Dondruma12 said:
No, I'm not because of having rooted it. The repair center says that I have to change the Motherboard. I'm not sure of this, is it possible?
Click to expand...
Click to collapse
Post a screen shot of odin.
It seems like you also rooted. FRP is reporting a modified binary, either custom recovery or modified boot image.
Either way its not necessary to flash the system image to remove the FRP lock.
However it will fail dm-verity checks if you've modified the system partition.
Boot and recovery can be flashed without the system image.
Do that first and report back.
{
"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"
}
"Boot and recovery can be flashed without the system image."
How can I flash boot and recovery without system img?
P.S. My recovery mode doesn't work, debug and fastboot neither. I'll send a screenshot of Odin
Dondruma12 said:
"Boot and recovery can be flashed without the system image."
How can I flash boot and recovery without system img?
P.S. My recovery mode doesn't work, debug and fastboot neither. I'll send a screenshot of Odin
Click to expand...
Click to collapse
Which firmware build number are/were you running?
ashyx said:
which firmware build number are/were you running?
Click to expand...
Click to collapse
I don't know how to find the number
https://ibb.co/e0731m
I've flashed both recovery and boot using Toolkit, it seems to be just like before
Dondruma12 said:
I don't know how to find the number
https://ibb.co/e0731m
I've flashed both recovery and boot using Toolkit, it seems to be just like before
Click to expand...
Click to collapse
You are no longer FRP locked according to your screen shot. Binary is now official.
However as said previously system is modified and likely won't boot due to dmverity.
You should be able to boot to stock recovery.
Can you post a screen shot of odin when trying to flash the stock firmware.
https://ibb.co/cXGAWm
Dondruma12 said:
https://ibb.co/cXGAWm
Click to expand...
Click to collapse
It's failing because you are using the wrong ODIN version.
3.07 doesn't support meta data.
https://drive.google.com/uc?export=download&id=0B6pQCizpnzoEdEtVeW42dGVGcXc
Well i am having a similiar Problem.
I am running Lineage 14.1 with TWRP and Magisk/Root.
Yesterday i flashed the latest Lineage nightly, reboot worked without problems.
This morning i started my S2 and i also got the message "Custom Binary blocked by FRP - Secure Fail: Kernel".
I only can get into Download mode. Trying to go into recovery mode i get the message again but with... Secure Fail: Recovery.
Any solution without flashing the Stock Rom?
Thomas_BA said:
Well i am having a similiar Problem.
I am running Leonage 14.1 with TWRP and Magisk.
Yesterday i flashed the latest Leonage nightly, reboot worked without problems.
This morning i started my S2 and i also got the message "Custom Binary blocked by FRP - Secure Fail: Kernel".
I only can get into Download mode. Trying to go into recovery mode i get the message again but with... Secure Fail: Recovery.
Any solution without flashing the Stock Rom?
Click to expand...
Click to collapse
You will at least have to flash stock boot and recovery images.
ashyx said:
You will at least have to flash stock boot and recovery images.
Click to expand...
Click to collapse
I feared so
Lets see where i can find stock boot and recovery..if not i have to download the whole ROM. Slow!!
Any idea where this problem came from? Havent changed anything in the developer settings (OEM, etc)
https://ibb.co/edBxSR
It always stops there, I let it continue for one hour but nothing happened.
I don't know, is it possible that "FRP Lock: On", "Warranty Void: 0x1 (4)" or "Qualcomm secureboot: enable (CSB)" are responsible of this?
Dondruma12 said:
https://ibb.co/edBxSR
It always stops there, I let it continue for one hour but nothing happened.
I don't know, is it possible that "FRP Lock: On", "Warranty Void: 0x1 (4)" or "Qualcomm secureboot: enable (CSB)" are responsible of this?
Click to expand...
Click to collapse
Non of that will be the issue.
Have you tried a different firmware?
ashyx said:
Non of that will be the issue.
Have you tried a different firmware?
Click to expand...
Click to collapse
Yes I did, everyone does the same thing
Dondruma12 said:
Yes I did, everyone does the same thing
Click to expand...
Click to collapse
Are you using an original cable?
Don't use long USB cables either as these cause issues.
I've just tried with the original one, unfortunately nothing changed
Then I tried to flash TWRP recovery and this is what I got
https://ibb.co/cqNYK6
Dondruma12 said:
I've just tried with the original one, unfortunately nothing changed
Then I tried to flash TWRP recovery and this is what I got
https://ibb.co/cqNYK6
Click to expand...
Click to collapse
You can't flash a custom recovery or kernel while FRP is on.
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
ashyx said:
You can't flash a custom recovery or kernel while FRP is on.
Click to expand...
Click to collapse
I'd try flashing the stock firmware with repartition ticked.
ashyx said:
You can't flash a custom recovery or kernel while FRP is on.
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
I'd try flashing the stock firmware with repartition ticked.
Click to expand...
Click to collapse
This is what happens
https://ibb.co/hGOFGm
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?
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
{
"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"
}
I would like to thank TeamWin for their amazing work!
I saw that the newer Samsung MediaTek phones were not getting any sort of love, so I bought one myself to kick start the development.
TWRP is the obvious choice as it is reliable and trustworthy with frequent updates and patches.
INSTALLATION:
Odin Method (Windows):
Step 0: Unlock Device Bootloader by toggling the OEM Unlock option in Developer Options. Device will reboot to Odin mode and will prompt you to long press volume up, device will then unlock bootloader and perform a complete factory reset so make sure to backup any data.
Step 1: Download the unofficial TWRP image from the link attached below.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Select the downloaded recovery.tar in AP slot and vbmeta_disabled_R.tar in USERDATA slot, connect the device to PC, go to options and untick "Auto-Reboot"
Step 4: Click START and the Device will get flashed, Odin will say SUCESS!.
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your M32 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
Heimdall Method (Linux):
Step 1: Install heimdall tool on linux , google it.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Open up terminal in the downloaded TWRP directory, extract twrp image from recovery.tar
Step 4: Enter the command "heimdall flash --RECOVERY recovery.img --no-reboot" where twrp.img is name of the downloaded image
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your M32 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
COMPATIBILITY:
TWRP Recovery is compatible with latest Android 11 firmware
tested on:
M325FXXU3AUK1, M325FXXU4AVB1 as well
First time you boot into TWRP, don't forget to backup your EFS, Secondary EFS and NVRAM! Go into Backup and select "EFS,", "Secondary EFS" and "NVRAM" and backup to preferably MicroSDcard and copy it to your PC in case you need it if IMEI corrupts.
DON'T IGNORE THIS STEP!
All kernel source and device tree below!
Device Tree: TWRP Device Tree
Kernel Tree: TWRP Kernel Tree
DOWNLOADS:
VBMETA DISABLED FOR R: MEGA LINK
TWRP TAR: MEGA LINK
@Akhil99 please check your inbox, you have an important PM
Samsung Galaxy M32 | OFFICIAL
Official Discussion group for ➤
Samsung Galaxy M32
Official Channels & Groups ➤
• Updates : @SamsungGalaxyM32Updates
Samsung Galaxy M32 | OFFICIAL
Official Discussion group for ➤ Samsung Galaxy M32 / M32 Prime Official Channels ➤ • Updates : @SamsungGalaxyM32Updates
t.me
Thank you so much... I lost all my hope, I thought there was no developer in the Samsung community.
Lihas Demhai said:
Thank you so much... I lost all my hope, I thought there was no developer in the Samsung community.
Click to expand...
Click to collapse
No worries, I will try and do whatever possible for this device.
I wanna encrypt my device but it keeps stuck on android icon when I do so, I have installed magisk btw. please help
I messed up. I didn't backup EFS, Secondary EFS and NVRAM.
Now, I can't use the sim.
I don't know what to do now.
dekisugihidetoshi said:
I messed up. I didn't backup EFS, Secondary EFS and NVRAM.
Now, I can't use the sim.
I don't know what to do now.
Click to expand...
Click to collapse
if you find any way to recover it then let us know please
dekisugihidetoshi said:
I messed up. I didn't backup EFS, Secondary EFS and NVRAM.
Now, I can't use the sim.
I don't know what to do now.
Click to expand...
Click to collapse
[SOLVED] suddenly unknown imei
ok so, i was using my phone normally yesterday, but out of nowhere, my SIM card stopped working and i couldn't use mobile internet/calls anymore. So i checked my settings and i saw my IMEI was marked as unknown, the same with baseband. The A32...
forum.xda-developers.com
[fixed] rooted a325m suddenly no imei, no sim
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now...
forum.xda-developers.com
well i found these fixed, try them and let us know
Tharki-God said:
[fixed] rooted a325m suddenly no imei, no sim
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now...
forum.xda-developers.com
Click to expand...
Click to collapse
this one worked for me
any way to root m32 without messing up imei?
im on android 12 latest security update. does this twrp work with my phone? this is my first time rooting so i dont have much knowledge about rooting
Kevin_6769T said:
im on android 12 latest security update. does this twrp work with my phone? this is my first time rooting so i dont have much knowledge about rooting
Click to expand...
Click to collapse
No, this is for only android 11
When will this project be compatible to latest kernel?
Thank you for your work Akhil99! It's very much appreciated.
I had no trouble installing it, following your guide. Gonna wait installing the Android 12 update till a new TWRP version is available for it.
I'm flashed this recovery on my M32 with Android 12... And after this I can't enter anything but download mode. Stuck in boot loop.
I can lock and unlock the bootloader, but it doesn't help.
I'm soooo stupid, but how can I make my phone work again?
EDIT:
I managed to recover my device. I've downloaded the firmware from samfrew.com and flashed it through Odin3.
i can't install GSIs with this TWRP ;-; help someone?
ijin menyimak..
dari Mlebu