cannot root S10e - Samsung Galaxy S10e Questions & Answers

Hi all,
I used to have my S10e rooted, at some point root was lost, I've never figured out why. So today I tried to obtain root again.
My bootloader is (still) unlocked, (greyed out, says already unlocked). I've tried 4 or 5 different methods or guides. I've tried downloading the latest Q firmware, installing it, copying the AP to device, patching that with Magisk, then install the patched AP.
I've tried several guides of installing TWRP first, from crDroid and lineage, but nothing works.
Whenever I try to install either TWRP or an rom with root, Odin either stops without any message, or just says "failed". I've seen "only official released binaries are allowed to be flashed" on my phone in download mode screen while trying to install patched ROMs. I've been able to install something, but then got "invalid kernel length" while booting.
I've been really strict with following the guides. but none of them gave me rooted phone.
Is there anyone who can give me a pointer into the right direction? I'd like to install crDroid, but I'm not able to get TWRP running, which is one of the first steps.
Thanks in advance!

which TWRP version did you try

Related

[SOLVED] Passing SafetyNet

I've been using an E6653 for the last few months with the Customized UK firmware (32.2.A.0.253). I was initially using it unmodified with Android Pay, then about a month ago Magisk was developed that allowed you to use root and Xposed and still pass SafetyNet checks so I could still use Android Pay. Due to the cat and mouse game with Google, I didn't think having root/Xposed was worth it any more so I decided to flash the stock ROM again which should have wiped everything. I've reflashed the firmware 3 times, but I can't seem to pass SafetyNet checks anymore.
In addition to flashing the stock firmware with Flashtool, is there something else I should be doing? Any help would be appreciated.
Devo7v said:
I've been using an E6653 for the last few months with the Customized UK firmware (32.2.A.0.253). I was initially using it unmodified with Android Pay, then about a month ago Magisk was developed that allowed you to use root and Xposed and still pass SafetyNet checks so I could still use Android Pay. Due to the cat and mouse game with Google, I didn't think having root/Xposed was worth it any more so I decided to flash the stock ROM again which should have wiped everything. I've reflashed the firmware 3 times, but I can't seem to pass SafetyNet checks anymore.
In addition to flashing the stock firmware with Flashtool, is there something else I should be doing? Any help would be appreciated.
Click to expand...
Click to collapse
I found the answer to my own question. Apparently Google updated SafetyNet yesterday to detect an unlocked bootloader. If you have an unlocked bootloader then your device fails SafetyNet checks. I guess I'm never going to be able to use AndroidPay.
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
Hi,
Noobish question but do you mind telling me how you got magisk installed?
I'm rooted, unlocked bootloader and restored DRM keys bu honestly, that was hectic.
Should I simply flash the lastest FTF from flash tools and then install TWRP then flash Magisk, OR do I have to go into much more steps such as create boot img etc. Also, will I lose my DRM keys? how would I replace them? If u don't mind, just give me bullets of the step, I think i can manage to find the files.
I'm really looking for clarity and assurance. As clear as the forums are, or supposed to be, I find it noisy and sometimes it's hard to filter through all the dialogues.
Devo7v said:
I found the answer to my own question. Apparently Google updated SafetyNet yesterday to detect an unlocked bootloader. If you have an unlocked bootloader then your device fails SafetyNet checks. I guess I'm never going to be able to use AndroidPay.
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
Click to expand...
Click to collapse
inteltecra1700 said:
Hi,
Noobish question but do you mind telling me how you got magisk installed?
I'm rooted, unlocked bootloader and restored DRM keys bu honestly, that was hectic.
Should I simply flash the lastest FTF from flash tools and then install TWRP then flash Magisk, OR do I have to go into much more steps such as create boot img etc. Also, will I lose my DRM keys? how would I replace them? If u don't mind, just give me bullets of the step, I think i can manage to find the files.
I'm really looking for clarity and assurance. As clear as the forums are, or supposed to be, I find it noisy and sometimes it's hard to filter through all the dialogues.
Click to expand...
Click to collapse
It sounds like you're on a fully functioning stock ROM with an unlocked bootloader. If that is the case, then it's pretty easy to get Magisk up and running. The first thing you need to do is get TWRP on your phone, to do that you need to flash a kernel that supports entering TWRP recovery from boot. There are a few kernels that allow you to do that, I am using AndroPlus v38. There is a newer version of AndroPlus, but there have been mixed reports of being able to enter TWRP.
To Flash a new Kernel and TWRP:
Download the latest kernel from https://kernel.andro.plus/ and place the <boot.img> within the zip file in the same folder with the fastboot.exe
Download the version of TWRP from https://dl.myself5.de/ and place the <recovery.img> in the same folder with the fastboot.exe
In the the folder with fastboot.exe, shift+right click and run cmd as admin
Reboot phone in to fastboot mode (hold down the volume up while plugging in usb)
Once the phone is detected type 'Fastboot devices' to make sure you device is detected.
If it's detected flash the kernel by typing the following command 'Fastboot flash boot <boot.img>' (without <>)
Then type 'Fastboot flash recovery <recovery.img>' (without <>)
Once done flashing type 'Fastboot reboot', and make sure you press volume up when the yellow led is showing
Once you've made sure that you can enter TWRP, things will be much easier from here on out. To get Magisk up and running:
Head over to the official Magisk thread and download both the Magisk Manager v2.1 apk and the Magisk v8 zip file to your phone (http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Reboot your phone and enter TWRP by pressing the volume up key when the yellow led is showing
Flash the Magisk v8 zip file. This will patch Magisk into your kernel (boot.img), so if you ever want to get rid of Magisk and it's mods, just reflash your kernel either by using Fastboot or by flashing the kernel zip file through TWRP.
Once Magisk has been successfully flashed, reboot your phone
When you phone has booted up install the Magisk Manager v2.1 apk that you downloaded earlier. If everything went right, the Magisk Manager should show that everything is installed and up to date.
I hope that helps, let me know if you have any other questions.
When I used to above procedure I get an error 'Response payload validation failed'. I have searched a lot in the internet and have seen a lot of people with the same bug. But I couldn't find a solution to this problem. Any ideas?
piet3r said:
When I used to above procedure I get an error 'Response payload validation failed'. I have searched a lot in the internet and have seen a lot of people with the same bug. But I couldn't find a solution to this problem. Any ideas?
Click to expand...
Click to collapse
Google has added more checks to SafetyNet and the procedure above no longer works. The issue is the AndroPlus kernel does not pass SafetyNet so anything you do after that will pass either. Maybe @AndroPlus will get some time to look into it and add some fixes. In the meantime I need to find another kernel that will pass SafetyNet, but I haven't had time to try.
Maybe you could try some other kernels and let us know if you find anything that works.

Can't Update renovate firmware

Hey guys,
Hopefully someone can help me with my problem. So i did the following:
To get rid of the 7 day Block of oem-unlocking on my s8+ i downgraded back to Nougat. From here on I flashed TWRP + rooted my device with magisk. After That i flashed the RENOVATE_ICE_G95X-7.5 rom + the Flashable_G95xF_FD_Firmware_TWRP_AQL5_r8 Firmware. I've let my Phone start up and went back to TWRP To Update the rom to RENOVATE_ICE_G95X-10.1. To this point everything Worked fine, the Phone Boots completely fine. Now to my problem: im Sitting on the actual stable rom but with the Baseband-version of Nougat which is AQL5. When i try to Flash the actual Firmware (CRC7 or CRD7) via TWRP my Phone gets stuck on the first Samsung Logo and Shows the following red Message: "Only official released binaries are allowed to be flashed". I would be glad for any help.
If you can find a standalone modem file from the ROM you mentioned you should be able to flash it in TWRP recovery. Last time I did this was on a Note 3. I think that the process should be the same with S8.
Can't seem to find one, but i found out that the same error occurs when installing other custom-roms like the King Oreo Rom which installs the newest Bootloader and Modem via Aroma installer. Only solution after that is to Flash Nougat again via Odin.

Question about RMM State (Only official released binaries are allowed to be flashed)

Hello comunity! I'm not getting this thing clear so i wanted to ask some questions.
I followed the steps from this guide: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-install-twrp-root-galaxy-t3752492
I decided to install Magisk then when i booted into System i could see that the device was succesfully rooted, but here comes the problem...
I rebooted the device and then after that, the boot screen appears with the message "Only official released binaries are allowed to be flashed"
I flashed an official Nougat ROM with Odin and then i could boot to system again (I was really worried about having the device as a brick haha), now i waited for the 7 days to have the OEM unlock setting, but i also updated again to Oreo with the official OTA's.
Now my main question is: What i have to do in order to root the device and be able to reboot whenever i want without having this trouble?, I saw that there was a RMM State Bypass that i need to flash after doing all the rooting process but after doing that, will i be able to reboot and not get the message "Only official released binaries are allowed to be flashed" anymore? I saw that you need to edit de build.prop file also, but i dont know when.
Thanks in advance!
Stock in boot
I got the same problem today, with the ROM G950FXXS3CRG1 ZTO, I tried so many times but I can't do root in TWRP mode. I need help too.
same problem in A320F
petrucioSneto72 said:
I got the same problem today, with the ROM G950FXXS3CRG1 ZTO, I tried so many times but I can't do root in TWRP mode. I need help too.
Click to expand...
Click to collapse
Same exact problem on my S9.

TWRP will not installan ROM that I give it on OP7 P

I have been trying unsucessfully tryiing to install Havoc OS on my phone for 2 days now and I believe the common theme seems to be TWRP.
I have tried to install different versions of Havoc, and then other Roms too and all fail in the same place.
There is no error code.
I have also tried to install different versions of TWRP going from 3.4.0.0 to 3.3.1.79 to 3.3.1.70 and none of these work
The steps are not complex and I have followed them to the letter
the bootloader is unlocked and magisk got installed although not needed for this part.
I also tried to install the rom via USB OTG and didnt work
please assist I am having so many issues with stock OS that i would like to try something else
TIA Bart
This can be closed I found it a much older version on the TWRP site itself and that actually allowed me to to flash the ROM

Cant re-root OnePlus8T.

I accidentally let the last OTA auto install. Naturally, I lost root access. I still get the "device is unlocked" screen when phone boots and was able to flash TWRP so I'm assuming the bootloader remains unlocked. Before the update I was on KB05AA to KB05DA, if that's at all relevant. What I have tried: Extracting boot.img with payload dumper and flashing with canary magisk then fastboot booting the patched boot.img file. Upon hitting install in magisk there was no option for "Direct Install" was not there. I also tried booting the adb twrp and extracting boot-a.img and boot-b.img with the same results. I also tried flashing magisk24.zip in twrp which resulted in an invalid zip format error(downloaded different ones, repacked, made no difference). One of the magisk zips i flashed was successful but no root access. Any help would be GREATLY appreciated. Please TIA
Try flashing the magisk.apk itself!
thanks, it worked without a hitch. so, i take it, theres not a apk file and a zip anymore? Just a flashable apk? anouther question is xposed just dead on android 11? i tried and and tried and tried to get edxposed going, magisk wouldnt install it despite several versions of riru being installed. i really appreciate the help with the seemingly stupid root question.
also ive read from a not so good source that the modded play store through lucky patcher is dead on android 11 is this true?
paxcow86 said:
thanks, it worked without a hitch. so, i take it, theres not a apk file and a zip anymore? Just a flashable apk? anouther question is xposed just dead on android 11? i tried and and tried and tried to get edxposed going, magisk wouldnt install it despite several versions of riru being installed. i really appreciate the help with the seemingly stupid root question.
Click to expand...
Click to collapse
Lxposed works great for me. There are both a riru and zygisk variant depending on what you prefer.

Categories

Resources