Hey there, so I have attempted to root my Samsung S7 edge through TWRP, only to get to the stage where i flash my files, Magisk and no verity, and get an error. I searched around and found out I needed to flash a stock boot.img, so I found on, flashed it and got stuck on the startup screen. After this, I found a new, S7 Oreo one and used that, now i can hear the volume buttons when I press them but have a red screen. All i can do on my phone is access TWRP, the downloading screen and the red screen, any ideas would be amazing. By the way im not very good with this kind of stuff (As you can probably tell).
TheAquarius said:
Hey there, so I have attempted to root my Samsung S7 edge through TWRP, only to get to the stage where i flash my files, Magisk and no verity, and get an error. I searched around and found out I needed to flash a stock boot.img, so I found on, flashed it and got stuck on the startup screen. After this, I found a new, S7 Oreo one and used that, now i can hear the volume buttons when I press them but have a red screen. All i can do on my phone is access TWRP, the downloading screen and the red screen, any ideas would be amazing. By the way im not very good with this kind of stuff (As you can probably tell).
Click to expand...
Click to collapse
Why in the actual hell did you flash some random stuff without asking.You never flash a boot img without confirming the version and the type of boot.img it is.For example you can't flash AOSP boot.img or kernel on Samsung.Or flash Samsung on AOSP.Similarly you don't flash Nougat on Oreo or Oreo on Nougat.You should have made a backup before messing things up.More Importantly you should've converted to Lineage OS immediately after TWRP for easiness.And Most Importantly magisk is only stable for Lineage and Does kinky stuff with Samsung's Version of Android.Your best bet is to get the current running OS with exact same build no date and all specification and extract the boot img and flash it.Or you can ask in S7 forum to provide one with same build and name.Along with OS version
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Why in the actual hell did you flash some random stuff without asking.You never flash a boot img without confirming the version and the type of boot.img it is.For example you can't flash AOSP boot.img or kernel on Samsung.Or flash Samsung on AOSP.Similarly you don't flash Nougat on Oreo or Oreo on Nougat.You should have made a backup before messing things up.More Importantly you should've converted to Lineage OS immediately after TWRP for easiness.And Most Importantly magisk is only stable for Lineage and Does kinky stuff with Samsung's Version of Android.Your best bet is to get the current running OS with exact same build no date and all specification and extract the boot img and flash it.Or you can ask in S7 forum to provide one with same build and name.Along with OS version
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Alright mate thanks ill have a look.
TheAquarius said:
Alright mate thanks ill have a look.
Click to expand...
Click to collapse
Can I just watch a video on how to flash my phones original firmware through twrp?
Related
Hello all,
I am receiving tomorrow my new Samsung S6 and i want to know some things.
- Unlocking bootloader (how to and link?) - have searched a bit and you need ODIN. but what is the best version etc
- Installing TWRP3.0 (how-to) - where to find the latest TWRP for samsung s6
And than one of the most important question, is there a stock android that doesent have any buys and fc's????
Bootloader is not locked on S6 (except AT&T variant)
You can get latest ODIN from here;
http://dl.sammobile.com/Odin3_v3.10.7.zip
If you want to install TWRP on it;
1- Update it to Marsmallow if you haven't
2- Install this TWRP via ODIN;
http://arter97.com/browse/S6/kernel/13.1/g920fi/arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5
3- Boot up to TWRP and flash this ZIP before do anything on TWRP;
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
forumber2 said:
3- Boot up to TWRP and backup your unmodified stock ROM before do anything on TWRP;
4- flash this ZIP
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Click to expand...
Click to collapse
Wouldn't this order make more sense so he had a backup in case something goes wrong?
Also, here are the threads for TWRP and SuperSU for the S6 on XDA:
http://forum.xda-developers.com/galaxy-s6/orig-development/twrp-t3080940
http://forum.xda-developers.com/galaxy-s6/orig-development/cf-auto-root-t3056630
djbosanac said:
And than one of the most important question, is there a stock android that doesent have any buys and fc's????
Click to expand...
Click to collapse
No, and there probably won't be any for a long time, but there are lots of TouchWiz-based custom ROMs.
so basicly i dont need any customezation? because you telling me there will not be released a custom stock rom? Even a CM13 rom
thats poor services!
Uhm
djbosanac said:
so basicly i dont need any customezation? because you telling me there will not be released a custom stock rom? Even a CM13 rom
thats poor services!
Uhm
Click to expand...
Click to collapse
Correct. The only custom ROMs availability now and the foreseeable future are based on TouchWiz, not AOSP Android or CyanogenMod.
CafeKampuchia said:
Wouldn't this order make more sense so he had a backup in case something goes wrong?
Click to expand...
Click to collapse
He need dm-verity disabled boot image for working TWRP backups. That's why I suggest him to install this ZIP.
While reading topics on the internet (google)
If you THE smartphone update to 6.0 you do not need to unlock the bootloader. is this correct?
For now i will not use TWRP because there isent a proper ROM for the S6. is this because the exynoss CPU? because QSD cpu's have always the better support for CM..
djbosanac said:
While reading topics on the internet (google)
If you THE smartphone update to 6.0 you do not need to unlock the bootloader. is this correct?
For now i will not use TWRP because there isent a proper ROM for the S6. is this because the exynoss CPU? because QSD cpu's have always the better support for CM..
Click to expand...
Click to collapse
As I said before, there's no bootloader unlock because bootloader is factory-unlocked on Samsung devices.
If you want root, you should to use TWRP for install the latest SuperSU.
Yes, there's no CM ROM for Exynos 7420 right now. Maybe in future? Who knows...
is there a twrp that works because the original twrp that i download form twrp.me isent working getting a weird issue: recovery is not seandroid enforcing
djbosanac said:
is there a twrp that works because the original twrp that i download form twrp.me isent working getting a weird issue: recovery is not seandroid enforcing
Click to expand...
Click to collapse
It is not an issue, it is just a warning. I wrote what you need to do at first reply;
forumber2 said:
Bootloader is not locked on S6 (except AT&T variant)
You can get latest ODIN from here;
http://dl.sammobile.com/Odin3_v3.10.7.zip
If you want to install TWRP on it;
1- Update it to Marsmallow if you haven't
2- Install this TWRP via ODIN;
http://arter97.com/browse/S6/kernel/13.1/g920fi/arter97-recovery-g920fi-13.1-twrp_3.0.2-0.tar.md5
3- Boot up to TWRP and flash this ZIP before do anything on TWRP;
https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Click to expand...
Click to collapse
i tried to install it, used the AP method in Odin.
But when i want to go in TWRP recovery i get the stock recovery! How to solve this issue
I'm having this issue as well on the T-Mobile variant. I have tried the unchecking auto reboot option in Odin and manually going to recovery. When I successfully flash according to Odin, I can't not get past the Recovery is not Seandroid enforcing boot.
SuddenGun007 said:
I'm having this issue as well on the T-Mobile variant. I have tried the unchecking auto reboot option in Odin and manually going to recovery. When I successfully flash according to Odin, I can't not get past the Recovery is not Seandroid enforcing boot.
Click to expand...
Click to collapse
where you able to figure this out? same problem. I can flash the twrp via ODIN, but get stuck on the "recovery is not seandroid enforcing" message. It just freezes on that.
help anyone? what should I be looking at? BL, Modem? I flashed original MM .tar file already...
I have a 920t (galaxy s6 non-edge tmobile)
piotrus22 said:
where you able to figure this out? same problem. I can flash the twrp via ODIN, but get stuck on the "recovery is not seandroid enforcing" message. It just freezes on that.
help anyone? what should I be looking at? BL, Modem? I flashed original MM .tar file already...
I have a 920t (galaxy s6 non-edge tmobile)
Click to expand...
Click to collapse
I did figure this out, check this post for how I did it.
This is a ROM that I put together because Verizon Galaxy S5 locked boot-loader phone has very little support, and we cant experience the stock Android Experience.
Any developer could customize this ROM and post their own version.
Whats included in this ROM:
-Google Apps instead of Samsung apps.
-Gravity Box
-Xposed
-Build.prop performance X tweaks
-Pixel Launcher
-Pixel Boot Animation
-Removed Verizon Bloatware
AOSP/Goodlock System UI - Customizable
Bugs:
Fingerprint to unlock- please disable fingerprint lock -++ if u want to use fingerprint install C locker pro and disable lockscreen++
Instructions:
Move to SD card, install - pretty much
to have system UI mods xposed; gravity box is recommended
Unlocked Phones.
Remove boot.img in the Flashable zip. and place any other kernel
XDA:DevDB Information
AOSP-Touchwiz , ROM for the Verizon Samsung Galaxy S5
Contributors
emeka1999
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: Touchwiz
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2018-11-12
Last Updated 2019-01-16
Download Link
https://mega.nz/#!VMBQwSQB!ARlWmnzOyDsHIAJZuL_6RUYFGrLVb4R1tIRMkuBaODI
Thanks for the work. I'm probably going to give this a shot tomorrow and will let you know what I think.
The title says "Unlock/Locked Bootloader"—is this to say I could flash this on my unlocked bootloader G900V without any trouble? I'd like to test ride this for a friend whose S5 whose bootloader may not be unlockable.
any way to root or install magisk in this rom_??
zihar said:
any way to root or install magisk in this rom_??
Click to expand...
Click to collapse
Depends. If you're using a bootloader locked S5, then no. If you have the unlockable bootloader S5, then yes.
Edit: Apologies, it just occurred to me that this only applies if the ROM doesn't mess with the bootloader status, which it very well might, given @zihar's troubles.
J-Lindo said:
Depends. If you're using a bootloader locked S5, then no. If you have the unlockable bootloader S5, then yes.
Click to expand...
Click to collapse
As in flashing a Magisk-vXX.X.zip in TWRP, correct?
chaos_jockey said:
As in flashing a Magisk-vXX.X.zip in TWRP, correct?
Click to expand...
Click to collapse
i have unlocked bootloader... but after flashing magisk the rom stuck at samsung Galaxy s5 logo but no past to the second splash and have the boot led on (blue blinking)....
chaos_jockey said:
As in flashing a Magisk-vXX.X.zip in TWRP, correct?
Click to expand...
Click to collapse
Correct.
zihar said:
i have unlocked bootloader... but after flashing magisk the rom stuck at samsung Galaxy s5 logo but no past to the second splash and have the boot led on (blue blinking)....
Click to expand...
Click to collapse
Now that's strange. My first thought would be maybe a corrupted Magisk .zip? Try flashing the Magisk uninstaller, see if it boots normally, then try again with a fresh downloaded .zip.
On the other hand, since the OP hasn't answered my question yet, it could be that the ROM re-locked your bootloader. Flashing Magisk in that case, which messes with the boot.img, would definitely mess with your system. In that case, I would hope flashing the uninstaller would solve the problem. I think you'll have to go through the process of unlocking the bootloader all over again too.
J-Lindo said:
Correct.
Now that's strange. My first thought would be maybe a corrupted Magisk .zip? Try flashing the Magisk uninstaller, see if it boots normally, then try again with a fresh downloaded .zip.
On the other hand, since the OP hasn't answered my question yet, it could be that the ROM re-locked your bootloader. Flashing Magisk in that case, which messes with the boot.img, would definitely mess with your system. In that case, I would hope flashing the uninstaller would solve the problem. I think you'll have to go through the process of unlocking the bootloader all over again too.
Click to expand...
Click to collapse
after some try i cant get root in this rom :c its look graet but i cant live without root
zihar said:
after some try i cant get root in this rom :c its look graet but i cant live without root
Click to expand...
Click to collapse
I''ve got the emmc 15. I got magisk 17.1 to 'work'.
This is what I've tried; after flashing the rom extract the boot.img from the aosp-touchwiz zip, install magisk manager and patch the boot.img, reboot to twrp and install, install image and select the patched_boot.img, swipe and pray. Had mine lock up at boot, flashed magisk uninstaller, installed the image again and it worked. Although, magisk states it's in core mode only, I tried to have it do its thing to run normally by unchecking the box but it wound up locking up the rom, so rinse and repeat. So, it's root but not through and through? Because I can't seem to move an app to system/priv-app when I do it fails to find the package, I've tried root explorer, es file manager, link2sd, lucky patcher, and TWRP (mounting system); either locks the rom, kills the app, or somehow removes root entirely.
I just want a rom with magisksu and that won't throw a fit when I move an app to system.
---------- Post added at 02:42 AM ---------- Previous post was at 02:31 AM ----------
J-Lindo said:
I think you'll have to go through the process of unlocking the bootloader all over again too.
Click to expand...
Click to collapse
Personally I've only gone through the process of unlocking the bootloader once on my emmc 15, TWRP is also installed as recovery.
My emmc 11 on the other hand is touchy and if you're not careful it'll lock up and you'll have to start over. The emmc 11 (locked bootloader) is touchy in general when dinking around with root/safestrap but the guides here are thorough, a bit more than the emmc 15 threads it seems.
Does installing a ROM like this one, in which bloatware was removed, result in more useable space from the phone's internal storage? Specifically, does it result in more storage for installing apps?
this thread needs to be deleted
After installing from rooted lollipop via safestrap its just stuck on the colored dots loading
Hey everyone,
i usually don't post questions but i've been on pretty much every forum the web has to offer and am still stuck so i'll try my luck here.
i'm currently running lineage 7.1 on my mi4c, i've used another phone for a while but now that my mi4c has a new battery i wanted to start using it again, is also decided this would be the time to update it to android oreo or pie, this however seems to be impossible.
i can only use twrp up to 3.1.1.1, all higher (and unofficial versions) will not boot via fastboot 'dtb not found' or when flashed via older twrp will freeze on boot screen.
whenever i try to install a new rom it tells me 'error code 7', when i remove the 'assert' lines in the update it gives me 'error code 6'
my device is unlocked, i have checked this in fastboot.
do i have to install miui again before installing another rom? do i have to go back to the standard recovery? i'm currently running out of ideas and hope you guys might be able to help me. maybe i'm overlooking something simple.
kind regards,
Monstreys
Hi! I don't know if this is a coincidence or not, but I was about to start a similar thread.
I try to do exactly what you are doing. I want to install LineageOS 16, unofficial ROM.
For this you need a newer TWRP, like 3.2.3.0, but it doesn't work 'dtb not found' like you said. I found out that this doesn't work because you need to have nougat bootloader. Most probably you have lollipop bootloader like I have, and thats why newer versions of TWRP are not working. I think the only way to update your bootloader to a nougat one is to flash the latest MIUI ROM. But, unfortunately, when you do that the bootloader gets locked, and I can't unlock it via MiUnlock due to Error:20091 when I try to link the phone to the Mi account. In MiUnlock it gives me the "this account cannot unlock the phone" or something like that.
Now I removed the "assert" lines from my rom and flashed it without the error 7 or 6. Some error still apears, but it also apears when I flash LineageOS 14.1, and that version is working even with those 2 errors I can't remember during flash.
After I flashed LineageOS, I flashed gapps and then superSU, and now my mi4c is stuck on mi logo for about 20 minutes, and I think it will remain that way.
So, there are 2 things we need to solve. We need to find a way to install latest MIUI without relocking the bootloader because I can't unlock it via MiUnlock, or to find out why after I flashed LineageOS 16 it gets stuck on MI logo.
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
i
i was unable to install the patch file, this nonetheless fixed my problem, thanks!!
if above not working, another method to do it based on my method.
https://forum.xda-developers.com/showpost.php?p=81573941&postcount=199
makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
My MI4C has been successfully flushed into lineage-17.1-20200220-UNOFFICIAL-libra.zip. It has been updated on TWRP 3.1.1 and keeps reporting error 7, and then abandoned TWRP3.1.1 and flashed into OrangeFox-R10.0-1-Stable-libra.zip After brushing libra-aqua_firmware_7.2.9.zip on this REC, you can flash lineage-17.1. I do n’t think it will be impossible to refresh because of partition problems. If you only need to upgrade lineage-17.1, you can refer to this method.:good::good:(Translation is not easy to use)
celrau said:
There is a 3.2.x around. If you don't want to bother go in the zip, /META-INF/com/google/android/ and delete the first lines (the ones starting with "assert") from updater-script, save and flash again.
Click to expand...
Click to collapse
rianawirawan said:
Right now, i'm using 3.1.1 -1 btw
It's latest twrp ver from official
Click to expand...
Click to collapse
TWRP-20190418-3.3.0.0-libra.img for the Xiaomi Mi 4c, by GuaiYiHu :
https://androidfilehost.com/?fid=1395089523397945946
Latest firmware for the Xiaomi Mi 4c libra :
https://github.com/XiaomiFirmwareUp...iui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip
Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?
OEM unlock toggle in Developer's Options
Hi ¡...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers
Been researching how to root this beast and it seems there are no "easy" solutions with this phone. I bought this A51 outright at TechSource (Toronto, Canada) after noticing the Spanish language text on the box, assuming it to be Exynos... verified by checking the phone's vitals in its config menu. Laid out 500+ CDN for it on the spot. In the past, there was an assumption that anything Exynos could be easily bootloader-unlocked and rooted. Hmmm.... Bootloader is indeed easily unlockable however, the root not so much so. Any root solutions found so far are insanely convoluted and downright dangerous for most ppl to consider. I have run rooted and Lineage OS'ed on a Sammy S4 and a Sony XA2-U without too much difficulty however that seems to be childs-play compared to this A51 beast! Patching pieces of a downloaded stock rom with Magisk and flashing to the recovery partition? Hmmm.... and no Lineage OS in sight?
Here's hoping someone out there has a simpler more elegent solution which doesn't carry so much risk. I'm sure there are many of us who would appreciate a little help from some kind dev who might take the time to sort this out... and here's hoping there will be Lineage OS for this beast down the road! I'm dying to unleash the full potential of this great beastie!
Oh, BTW, too many restrictions in Android 10/Q... errr... thats a discussion best left for another day. ;-))
Regards...
-[ Hummer ]-
BTW, Above post sent via Firefox v52.9.0 ESR, the last usable XUL browser...
i can send you a AP recovery image if you have standard Firmware. or i can Give you the links to a working twrp and linage os both root are from magisk
danofaster said:
i can send you a AP recovery image if you have standard Firmware. or i can Give you the links to a working twrp and linage os both root are from magisk
Click to expand...
Click to collapse
Bro pls do send link for the working twrp, been trying for days to install a custom rom on my A51, but whenever I boot into the twrp it fails to mount system, vendor, data, cache. Please i need help on this
https://build.lolinet.com/file/lineage/a51/
Has linage and a working twrp and all.
the boot.img u wring that into the zip and it will give you a mejestic root.
and it wont whipe system. either its something to do with the drm thingy
put the recovering into a *.tar compression copy the lineage os onto a sd stick
danofaster said:
https://build.lolinet.com/file/lineage/a51/
Has linage and a working twrp and all.
the boot.img u wring that into the zip and it will give you a mejestic root.
and it wont whipe system. either its something to do with the drm thingy
put the recovering into a *.tar compression copy the lineage os onto a sd stick
So when it comes to system whipe just makesure u have the latest firmware downloaded flash that on then go with the put recovery.img ova and then flash with the lineage os zip. in recovery
Click to expand...
Click to collapse
Hello
you can look in this video
How to installed TWRP Recovery and Root your Galaxy A51 device
Hi danofaster,
Thanks for the link to a Lineage source...
That source is a directory tree with the following
file being the latest revision:
lineage-17.1-20201010-EXPERIMENTAL-a51.zip
hummer2238 said:
Hi danofaster,
Thanks for the link to a Lineage source...
That source is a directory tree with the following
file being the latest revision:
lineage-17.1-20201010-EXPERIMENTAL-a51.zip
Click to expand...
Click to collapse
Note... there is a "TWRP" dir listed there however there is no file for the A51. Do you have a link to
a working TWRP for the A51? If so, please post it so
that we can finally get this AWESOME A51 beastie set
for flashing Lineage.
Thanks / Regards...
-[ Hummer ]-
hummer2238 said:
Note... there is a "TWRP" dir listed there however there is no file for the A51. Do you have a link to
a working TWRP for the A51? If so, please post it so
that we can finally get this AWESOME A51 beastie set
for flashing Lineage.
Thanks / Regards...
-[ Hummer ]-
Click to expand...
Click to collapse
Ho! Found one...
twrp-a51-3.5.0_10-1_ianmacd.tar
at { https://androidfilehost.com/?fid=17248734326145708114
Rooting was quite easy for me (Android 11, One Ui 3.1), the thing you should worry about is getting into KG Prenormal state and SafetyNet (ctsProfile fail, basicIntegrity success).
FBE is on by default, I don't suggest flashing multidisabler because it makes SafetyNet worser (ctsProfile and basicIntegrity fails) and fingerprint unlock no longer work.
I have rooted my A51F CSC Bahamas. I don't know if that helps anyone, if it can help let me know and I will try to answer questions or send you copies of the files I used. I installed Magisk and TWRP however I am unable to make a TWRP Backup as I keep getting the 255 error. Attached are some screenshots from TWRP. Any feedback is much welcome.