Related
Unofficial release -TWRP recovery for the Galaxy A5 - SM-A510F/FD/Y/M, Exynos7580
UPDATE 2/8/2016:
TWRP 3.0.2-1 MM build released.
Now working on Marshmallow
MTP working
ADB working
Update 5/4/2016 - TWRP 3.0.2.-0
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
TWRP is now v3.0.2-1
SEANDROID warning fix
UI colour fix
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
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.
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.
GUIDE:
https://dottech.org/193481/how-to-install-twrp-recovery-on-samsung-galaxy-a5-sm-a510-2016-guide/
LOLLIPOP:
twrp_3.0.2-1_sm-a510
MARSHMALLOW:
twrp_3.0.2-1_sm-a510_mm_1816
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the latest Supersu beta below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
DEVICE TREE: soon
Credits: Me, 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
.
.
ashyx said:
Unofficial release -TWRP recovery for the SM-A510F/FD, Exynos7580
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.
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.
twrp_3.0.0-0_sm-a510F
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
https://download.chainfire.eu/921/SuperSU
DEVICE TREE: soon
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.
Credits: Me, Teamwin and my tester - franzerelli
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
.
.
Click to expand...
Click to collapse
Thank pro. I have already rooted my phone a510fd in vietnam.
nhthiencp said:
Thank pro. I have already rooted my phone a510fd in vietnam.
Click to expand...
Click to collapse
Root được rồi hả bạn?
Reserved.
cant download from androidfilehost. when u will give it free again?
....
wildalan said:
....
Click to expand...
Click to collapse
sry, i already asked him for the file.
@ashyx please help me
Deleted
ashyx said:
Unofficial release -TWRP recovery for the Galaxy A5 - SM-A510F/FD/Y/M, Exynos7580
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.
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.
twrp_3.0.0-0_sm-a510
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
https://download.chainfire.eu/921/SuperSU
DEVICE TREE: soon
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.
Credits: Me, Teamwin and my testers- iNTER5LOve and franzerelli
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
.
.
Click to expand...
Click to collapse
why my device can't get rooted? a510fd 5.1.1 version.
i pass the odin flash,but when entering recovery,it said : recovery is not seandroid enforcing
and it didnt pass the root checker as well...
Please help
clows said:
why my device can't get rooted? a510fd 5.1.1 version.
i pass the odin flash,but when entering recovery,it said : this device is not seandroid enforcing
and it didnt pass the root checker as well...
Please help
Click to expand...
Click to collapse
You didn't need to quote the OP.
Wait 60 secs.
ashyx said:
You didn't need to quote the OP.
Wait 60 secs.
Click to expand...
Click to collapse
it works..Thanks a lot dude..:good:
clows said:
it works..Thanks a lot dude..:good:
Click to expand...
Click to collapse
I'm going to be working on a fix for the load time when I get chance.
In the mean time can somebody send me the recovery.log.
My phone went into bootloop after dead battery. Fashed it with twrp_3.0.0-0_sm-a510 couple weeks ago. now my phone restarted and I receive always "Custom binary blocked by FAP lock"... Is there a chance to get it back up?
etrax2 said:
My phone went into bootloop after dead battery. Fashed it with twrp_3.0.0-0_sm-a510 couple weeks ago. now my phone restarted and I receive always "Custom binary blocked by FAP lock"... Is there a chance to get it back up?
Click to expand...
Click to collapse
Flash stock Firmware then enable OEM unlock in developer settings.
It's all stated in the first post.
great job ashyx ... it works
can someone pleas post a complete Guide step by step with pictures and all,kinda lost do i have to copy super user zip into an sd card or just in the internal phone memory ?
Gattsu21 said:
can someone pleas post a complete Guide step by step with pictures and all,kinda lost do i have to copy super user zip into an sd card or just in the internal phone memory ?
Click to expand...
Click to collapse
Doesn't matter where you put it. Just follow the instructions given.
ashyx said:
I'm going to be working on a fix for the load time when I get chance.
In the mean time can somebody send me the recovery.log.
Click to expand...
Click to collapse
Here you go:
https://www.dropbox.com/s/y95kcrsmtns46ce/recovery.log?dl=0
Hi,
I want to ask, is the firmware of sm-a510f/fd same?
Im looking firmware for sm-a510fd but no luck...
Thank you before,
Sory my bad english
There is a custom rom for A5 2016? what is without a custom rom?
Inviato dal mio SM-A510F utilizzando Tapatalk
Unofficial release -TWRP recovery for the Galaxy A7 - SM-A710F/FD/Y/M Exynos7580
UPDATE 14/4/2016: TWRP 3.0.2-0 released.
https://twrp.me/site/update/2016/04/...-released.html
TWRP is now v3.0.2-1
SEANDROID warning fix
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
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.
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.
twrp_3.0.2-1_sm-a710
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
https://download.chainfire.eu/969/SuperSU/
DEVICE TREE: soon
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.
Credits: Me, Teamwin and my testers - nhthiencp
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
.
works like a charm 100%
thank u so much :good:
flash supersu error signature
haohoa2308 said:
flash supersu error signature
Click to expand...
Click to collapse
Redownload.
Hi Ashyx,
Saw that you posted TWRP for both A510F and A710F, any chance you could compile for the A310F too?
It would be very much appreciated!
Cheers
thomekh said:
Hi Ashyx,
Saw that you posted TWRP for both A510F and A710F, any chance you could compile for the A310F too?
It would be very much appreciated!
Cheers
Click to expand...
Click to collapse
I suppose one more won't hurt. If you've got the stock recovery, post it up.
ashyx said:
I suppose one more won't hurt. If you've got the stock recovery, post it up.
Click to expand...
Click to collapse
Wonderful, I've attached the stock recovery img (zipped).
Many thanks in advance
I have flashed this version of TWRP on my Samsung Galaxy A7 2016 SM-A710Y device. Many thanks.
Note: Downloads have been blocked until i remove supersu from twrp due to people incapable of reading instructions!
thomekh said:
Wonderful, I've attached the stock recovery img (zipped).
Many thanks in advance
Click to expand...
Click to collapse
Posted in the General section.
From where can I get stock recovery for A710FD...?
new and noob
wanna root my phone but i want to download stock rom first in case anything goes wrong. problem is i don't know which rom should i download. I've attached my phone's software info. thanks in advance
done! it works. I tried it even without backups. thanks button hitted
Many thanks, It works. now i can cheat offline game in my phone ^^.
Xposed installer
In this cell A7 2016 xposed installer running or not
Which modules are support please suggest me
Because i want to buy this cell
From where can I get stock recovery for A710FD...?
please
valiforu said:
From where can I get stock recovery for A710FD...?
please
Click to expand...
Click to collapse
The stock firmware, but why would you?
Incase the mobile has boot loop
For safety i want the stock recovery
From twrp recovery installed xposed installer some times mobile will be in boot loop for that i want the stock recovery
How is stock recovery going to rescue you from a bootloop?
For that you need a custom recovery like twrp to simply make a backup first.
Kk thank u
Can we install xposed installer in A710FD
Please suggest me its working or not
Unofficial release -TWRP recovery for the Galaxy A7 - SM-A700FD - Qualcomm msm8939
UPDATE 4/8/2016:
TWRP 3.0.2-1 MM build.
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.
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 POWER + HOME.
You should now see TWRP recovery.
MARSHMALLOW:
twrp_3.0.2-1_sm-a700fd_mm_4816
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
https://download.chainfire.eu/969/SuperSU/
DEVICE TREE: soon
NOTE: ON SOME ANDROID 5.1.1/6.0.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.
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
.
.
Reserved
Will it work with Lollypop? On my SM-a7100 (also Qualcomm msm8939) it installs file with odyn, but when i try to reboot in TWRP - sams bootscreeen + error
P.s. Really like your work!
@ashyx
Thankss ! :good:
mur4ello said:
Will it work with Lollypop? On my SM-a7100 (also Qualcomm msm8939) it installs file with odyn, but when i try to reboot in TWRP - sams bootscreeen + error
P.s. Really like your work!
Click to expand...
Click to collapse
Marshmallow only I'm afraid.
having No OS installed / device isn't rooted and error error executing updater binary in zip when trying to install custom rom in twrp.
Tried to re-flash CF auto root and TWRP but yet it only boot loops. Also tried to flash the firmware from sammobile but failing.. any help? :/ TIA
Set Warranty Bit: kernel
Bootscreen shows "Set Warranty Bit: kernel" in yellow font and booting into recovery shows the Seandroid warning. This happened after flashing twrp and rooting the phone. That's the only problem though because twrp and supersu are working properly. How to fix this? tia!
nieohl said:
having No OS installed / device isn't rooted and error error executing updater binary in zip when trying to install custom rom in twrp.
Tried to re-flash CF auto root and TWRP but yet it only boot loops. Also tried to flash the firmware from sammobile but failing.. any help? :/ TIA
Click to expand...
Click to collapse
Sorry for this. It was my unlocked device in my pocket. Please delete
OEM issue
Im using this sm a700fd device but in my developer mode i dont have OEM option thats the reason my 4 is not getting root not installing Twrp not even cf auto root working plz help .......
thnk u vry mchhhhhhhhhhhh.........................
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
neoquor said:
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
Click to expand...
Click to collapse
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
bober10113 said:
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
Click to expand...
Click to collapse
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
neoquor said:
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
bober10113 said:
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
Click to expand...
Click to collapse
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
neoquor said:
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
Click to expand...
Click to collapse
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
bober10113 said:
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
Click to expand...
Click to collapse
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
neoquor said:
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
Click to expand...
Click to collapse
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
bober10113 said:
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
Click to expand...
Click to collapse
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
i really dont know. im on exynos device. people with n9600 will have to help you as i have no experience with snapdragon.
sorry
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob! Just like @neoquor, I am using a Snapdragon Note 9 (SCV40/SM-N960J) from the carrier au. I was able to successfully boot with the firmware of another Japanese carrier variant SM-N960D/SC-01L (carrier DoCoMo) and @klabit87 's N9600 klabit kernel.
Following the Magisk installation instructions from @topjohnwu 's GitHub, my installation was a bit windy (trial-and-error), but I (1) launched Odin and flashed my Magisk-patched SC-01L AP binary along with BL, CP, and CSC; and (2) after falling into the bootloop, I flashed klabit's official N9600 TWRP build, and (3) flashed klabit's N9600 kernel.
After that, success--finally! Dekita!
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
neoquor said:
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
Click to expand...
Click to collapse
Dear NeoQuor, did you find any solution ?
I have the same problem I I flashed patched magisk with boot.img file it is flashed 100% but I'm not able to boot to android. it keeps restarting on the boot loop.
I just found one source this guy he is able to root SCV40
https://support.halabtech.com/index.php?a=downloads&b=folder&id=77034
i look forward to a solution for my phone to be rooted.
regards,
Sher
I also have SCV40, and the only reason I need to root my SCV40 because I need to edit and rewrite ro.confiq.tima=1 to 0 so that I'll be able to use S-Health, but in the end I can't root my SCV40, It is impossible, but I did rooting my friend's Note9 and it work well. I guess there's still no one can root SCV40 Until today.
I'm thinking of getting a 30 Ultra the next week, as I'm very disappointed with my OnePlus 10 Pro and the way OnePlus is heading.
I've been an OnePlus user since the 6 and never had a Motorola before, but the 30 Ultra really fascinates me.
Before I buy it I only wanted to ask how the modding community for motorola is.
Is Magisk easily installable with Motorola devices? Anything I should keep in mind with unlocking the bootloader / rooting of a motorola?
Thank's in advance
I didn't have any problems rooting my edge 30 ultra. I had to wait about 2-3 days for the OEM unlocking option to be activated in the developer options, but other than that it was smooth sailing.
Unlock bootloader, obtain stock boot image by for example using the Lenovo Rescue and Smart Assistant, patch the boot image in the magisk app, and then flash it.
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Killuminati91 said:
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Click to expand...
Click to collapse
Yes, it's true.
But i big problem in poland, because customer write to unlock bootlader code = warranty is out.
I this method broken my Moto G82
Killuminati91 said:
You should keep in mind that it's extremely dangerous if not impossible to relock the bootloader again. In theory you have to flash the stock firmware and thoroughly delete all data and custom settings but a lot of people end up with bricked devices.
Click to expand...
Click to collapse
Ok so once I root my Motorola, I can't go back to unrooted, right? Surely not ideal but I rarely unroot my devices once I rooted. But thanks for mentioning!
I'm guessing custom rom/kernel support for this device isn't really a thing right?
No, you can unroot at any time if you uninstall magisk and flash the stock boot.img. But you can't / shouldn't relock the bootloader. I think times are over when a lot of people developed kernels / Roms / TWRP for specific phones. We need more people to take matters into their own hands, the market is flooded with too many different models.
@Killuminati91 any news on twrp for this phone yet?
_Hinnie_ said:
I didn't have any problems rooting my edge 30 ultra. I had to wait about 2-3 days for the OEM unlocking option to be activated in the developer options, but other than that it was smooth sailing.
Unlock bootloader, obtain stock boot image by for example using the Lenovo Rescue and Smart Assistant, patch the boot image in the magisk app, and then flash it.
Click to expand...
Click to collapse
I'd be very thankful if you could share a guide for this
memocatcher said:
Ok so once I root my Motorola, I can't go back to unrooted, right? Surely not ideal but I rarely unroot my devices once I rooted. But thanks for mentioning!
I'm guessing custom rom/kernel support for this device isn't really a thing right?
Click to expand...
Click to collapse
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
memocatcher said:
I'd be very thankful if you could share a guide for this
Click to expand...
Click to collapse
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
_Hinnie_ said:
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
Click to expand...
Click to collapse
Thanks a lot!!
TF1920 said:
@Killuminati91 any news on twrp for this phone yet?
Click to expand...
Click to collapse
No success yet and I currently don't have the time to try, sadly. Device tree can be generated with helpers but the whole Linux compiling part is still gibberish to me.
TF1920 said:
@Killuminati91 any news on twrp for this phone yet?
Click to expand...
Click to collapse
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
arellewen said:
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
Click to expand...
Click to collapse
I also tried myself to setup a device tree, but haven't been able to extract the prebuilt kernel. That's also why I asked for the kernel source on their github that will hopefully soon be published.
I'll try in a bit and edit this post to see if the recovery boots.
EDIT: Nope, it doesn't boot. After the usual motorola animation the screen goes black, and afterwards boots into system.
logandavid said:
sorry for an off-topic question: What did you hate about Oneplus 10 Pro in particular?
Click to expand...
Click to collapse
I just don't like the way OnePlus is heading, like many users with the 10 Pro. It feels like using an Oppo device honestly and they made it impossible to unbrick your device by encrypting the popular MSM Tool.
After 5 years with OnePlus it's time for me to try something different
_Hinnie_ said:
I also tried myself to setup a device tree, but haven't been able to extract the prebuilt kernel. That's also why I asked for the kernel source on their github that will hopefully soon be published.
I'll try in a bit and edit this post to see if the recovery boots.
EDIT: Nope, it doesn't boot. After the usual motorola animation the screen goes black, and afterwards boots into system.
Click to expand...
Click to collapse
Yes it didn't work for me either
Nope !! , stay where you are, I had One Plus 9 Pro before, the Edge 30 Pro is much better in all aspects, One plus = Oppo, very bad phone.
A few questions;
Do you need to have a sim card installed in the phone during the 7 day wait period until the oem unlock button is available? Can I just connect the phone to wifi and let it sit for a week?,
Do you need some sort of unlock code from Motorola? I read the unlock directions, but to go any further it's asking for an email address and the need to register and account.,
Also what is the main difference between the pro and the ultra? Is it only the 200MP camera?
_Hinnie_ said:
Custom roms / kernels isn't a thing at the moment. It is confirmed however that Motorola will soon release the kernel source code of the Edge 30 Ultra, which can help with custom rom and kernel development (https://github.com/MotorolaMobilityLLC/kernel-msm/issues/445).
1. Go to Settings -> Developer Options -> Enable OEM Unlocking
2. Reboot the phone to the bootloader, for example using adb reboot bootloader
3. Follow the steps from here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
To root your phone:
1. Install the Magisk app from here: https://github.com/topjohnwu/Magisk/releases
2. Download the boot image from the official firmware, make sure the firmware corresponds with your device (or grab your own using the Lenovo Rescue and Assist tool) https://forum.xda-developers.com/t/...cn-to-edge-30-ultra-eu.4491699/#post-87424851
3. In Magisk: Home -> Install -> Select and Patch a File ->Select the boot.img -> Click LET'S GO
4. Copy the patched boot image from /storage/emulated/0/Downloaded/magisk_patched-xxxx.img to your computer
5. Boot the phone to the bootloader
6. Flash the patched boot image with fastboot flash boot magisk_patched-xxxx.img, or alternatively, if you want to be sure that the boot image boots before flashing it, use fastboot boot magisk_patched-xxxx.img and if it works fine, repeat from step 5.
7. Reboot
Click to expand...
Click to collapse
It works for me, thanks~
And is there any way to remount /system or /vendor directory with r/w permission?
solsolhh said:
It works for me, thanks~
And is there any way to remount /system or /vendor directory with r/w permission?
Click to expand...
Click to collapse
This but for me dosn't work if write something there is 0 bytes, if you make it work let us know
Tools:
- Universal Mount System RW (Guide)
-> Fix for Android 12
arellewen said:
I did a tentative build, here are the results: img / zip
This was built with OrangeFox, using my device tree. Feel free to contribute to the repo, I can rebuilt if it doesn't work out of the box.
A disclaimer: I am a noob, and I don't have the device yet to test it, it is quite unlikely that this recovery works on the first attempt.
The prebuilt kernel I am especially unsure about.
Click to expand...
Click to collapse
Kernel Sources now available, if you got the time:
Release MMI-S3SQ32.16-16-28 · MotorolaMobilityLLC/kernel-msm
eqs-g push for android 12
github.com