Related
My Mi 4c arrived yesterday. I bought it using donations that I received from various project (Samsung Galaxy Tab 2, Tab 3, Tab 4, OnePlus One, Xiaomi Redmi 2). It's seems for Chinese market: a lot of Chinese apps, incomplete English translation, no Google services. Fortunately, TWRP port already available for this device, so rooting and installing GApps is easy. Somehow I still want to keep the original recovery.
1. Boot to fastboot mode (VOL DOWN + POWER) to fastboot TWRP:
Code:
fastboot boot twrp.img
2. Flash SuperSU in TWRP
3. Flash Open GApps nano in TWRP
As you know, loading touchscreen firmware need times in TWRP. Just do other thing while waiting for it :laugh: The possible cause is firmware "ping-pong" issue when in kernel touchscreen firmware different between recovery and normal boot. But why loading a firmware so that long?
My device come with MIUI 7.1.4.0, unlocked bootloader. I just upgrade it to 7.2.1.0 without firmware update to keep the bootloader unlocked but use 7.1.6.0 kernel to boot it because no go with the new kernel (incompatible firmware?), MIUI logo forever. BEWARE: Don't upgrade your device to 7.2.1.0 using a standard method, your bootloader will be locked!
Attached Hardware Info report for my future reference if I decide to develop custom ROM/kernel.
@emfox, I'm with you :laugh:
MIUI 7.2.1.0 without firmware update.
how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....
tuanhung303 said:
how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....
Click to expand...
Click to collapse
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.
I hope you can make modified rom 7.2.1.0 without bootloader.
ahmaman said:
I hope you can make modified rom 7.2.1.0 without bootloader.
Click to expand...
Click to collapse
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.
welcome aboard, my dear friend!
Looks to me, we got another developer. Good
ketut.kumajaya said:
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.
Click to expand...
Click to collapse
omg... is that English? (j/k)
btw, welcome onboard , Xiaomi will release some kernel sources soon, looks like we will have more stable rom in future :laugh:
ketut.kumajaya said:
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.
Click to expand...
Click to collapse
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them
Logic_ said:
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them
Click to expand...
Click to collapse
yes, the version 2.8 does not have that bug, the version 3.0.0.2 has
Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!
wind99 said:
Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!
Click to expand...
Click to collapse
Still slowly check Xiaomi changes line by line https://github.com/kumajaya/android_kernel_xiaomi_msm8992/commits/libra-l-oss-kumajaya :laugh:
RO2T - Stock, SELinux Permissive Kernel For Samsung SM-G550FY (On5)
How to install + root on LL 5.1.1:
Enable USB Debugging & OEM Unlock from Settings > Developer Options.
Flash kernel, recovery via ODIN.
Install SuperSU from recovery.
Click thanks, and enjoy!
Note: The TWRP is actually from SM-J200G (j2lte) which shares the same chipset (Exynos 3475), with RO2T kernel & device-tree from stock kernel. I didn't test all features, but the SuperSU installation just did work as it should. Use at your own risk.
Download:
Kernel: https://www.androidfilehost.com/?fid=24499762636000430
TWRP: https://www.androidfilehost.com/?fid=24499762636000429
Sources:
Kernel: https://github.com/ro2t/o5lteswa
You saved my life
You are great. My months long research finally ended in this small post of yours. I have a samsung galaxy on5 chinese model sm-g5500 and I was trying to install gapps on it with no success. I have almost given up searching since its a rare model and there are no custom recovery or custom roms for this model available. But this twrp worked and i am able to flash gapps. Thank you very much. I had to pull the cable and battery immediately after odin shows 'pass' message otherwise it will replace the same old stock recovery after reboot. Not sure mine will be replaced after the next reboot but that doesn't matter because my job is done.
tomo444 said:
You are great. My months long research finally ended in this small post of yours. I have a samsung galaxy on5 chinese model sm-g5500 and I was trying to install gapps on it with no success. I have almost given up searching since its a rare model and there are no custom recovery or custom roms for this model available. But this twrp worked and i am able to flash gapps. Thank you very much. I had to pull the cable and battery immediately after odin shows 'pass' message otherwise it will replace the same old stock recovery after reboot. Not sure mine will be replaced after the next reboot but that doesn't matter because my job is done.
Click to expand...
Click to collapse
@tomo444, does On5 have theme center like J5?
Azhero said:
@tomo444, does On5 have theme center like J5?
Click to expand...
Click to collapse
Yes, same design
need ROOT for glaxy on5 marshmallow updated
you are really great i tried your method and succesfully rooted. but recently i updated to marshmallow. which means it is now GALAXY ON5 PRO. can u try to root thst too please, i hope you wil do it . thanks in advance
re1th said:
you are really great i tried your method and succesfully rooted. but recently i updated to marshmallow. which means it is now GALAXY ON5 PRO. can u try to root thst too please, i hope you wil do it . thanks in advance
Click to expand...
Click to collapse
see this thread: http://forum.xda-developers.com/android/development/requests-team-win-recovery-project-t3420007
join #twrp on freenode IRC and I will work with you to make Galaxy On5 TWRP official.
@vaibhavpandeyvpz, do you live in India? Does your SM-G550FY has Theme Store on 5.1.1?
I don't have the device but my colleague has one. The 5.1.1 did not have a theme store, but the 6.0.1 update does.
I also have the Galaxy on5 with MM. Will wait for a root.
cooltranier13px said:
I also have the Galaxy on5 with MM. Will wait for a root.
Click to expand...
Click to collapse
I also wait plz healp me
Nikup4253 said:
I also wait plz healp me
Click to expand...
Click to collapse
Just wait, a root will come eventually.
tomo444 said:
You are great. My months long research finally ended in this small post of yours. I have a samsung galaxy on5 chinese model sm-g5500 and I was trying to install gapps on it with no success. I have almost given up searching since its a rare model and there are no custom recovery or custom roms for this model available. But this twrp worked and i am able to flash gapps. Thank you very much. I had to pull the cable and battery immediately after odin shows 'pass' message otherwise it will replace the same old stock recovery after reboot. Not sure mine will be replaced after the next reboot but that doesn't matter because my job is done.
Click to expand...
Click to collapse
Did you install both the kernel and twrp? I also have the Chinese G5500. Thanks!
tomo444 said:
You are great. My months long research finally ended in this small post of yours. I have a samsung galaxy on5 chinese model sm-g5500 and I was trying to install gapps on it with no success. I have almost given up searching since its a rare model and there are no custom recovery or custom roms for this model available. But this twrp worked and i am able to flash gapps. Thank you very much. I had to pull the cable and battery immediately after odin shows 'pass' message otherwise it will replace the same old stock recovery after reboot. Not sure mine will be replaced after the next reboot but that doesn't matter because my job is done.
Click to expand...
Click to collapse
I'm hoping someone could help me out. I have the same problem and I don't know how to install these things on my chinese sm-g5500 but I desperately need gapps. Spent months trying to figure this out. I hope somebody can be of assistance
Thanks
Custom kernel
Please upload custom kernel for sm-g550fy 6.0.1
My ON 5 SM-G550FY is not opening
Hi,
I have flashed the kernels and twrp file through odin
But after flashing my phone is simply opening, showing the logo of galaxy on 5 and getting switched off again and it is continued.
i think I have loaded the files in wrong sections .
I loaded the kernel in BL and TWRP file in AP section.
.
please help me out
:crying::crying::crying::crying::crying:
SM-G5500 - Installing Gapps
vaibhavpandeyvpz said:
RO2T - Stock, SELinux Permissive Kernel For Samsung SM-G550FY (On5)
How to install + root on LL 5.1.1:
Enable USB Debugging & OEM Unlock from Settings > Developer Options.
Flash kernel, recovery via ODIN.
Install SuperSU from recovery.
Click thanks, and enjoy!
Note: The TWRP is actually from SM-J200G (j2lte) which shares the same chipset (Exynos 3475), with RO2T kernel & device-tree from stock kernel. I didn't test all features, but the SuperSU installation just did work as it should. Use at your own risk.
Download:
Kernel: https://www.androidfilehost.com/?fid=24499762636000430
TWRP: https://www.androidfilehost.com/?fid=24499762636000429
Sources:
Kernel: https://github.com/ro2t/o5lteswa
Click to expand...
Click to collapse
I have a SM-g5000 which I want to install Gapps on.
The Kernel file is infected by virus. Can you provide the file again here please?
Cheers,
Sathish
Are kernels as tricky as ROM's? What I'm asking is will this work for an SM-G550T?
please teach n how to install gapps on my samsung g5500 to.
---------- Post added at 07:30 AM ---------- Previous post was at 07:27 AM ----------
you should put them both in ap section.
not working on this version G5520ZCU1AQB2
@vaibhavpandeyvpz sir, I have a kind request, please build Lineage OS (with HAL3) for Samsung Galaxy ON5 Pro (SM-G550FY), Codename : o5prolte....
TWRP device tree : https://github.com/jcadduono/android..._samsung_o5lte
Kernel Source Tree :
https://github.com/jcadduono/android.../tree/twrp-6.0
Device Tree :
https://github.com/abhi2121/android-...msung-o5prolte
Attachment - build.prop and default.prop from Stock Android 6.0.1 ROM
I do not have a super fast internet connection, and I don't know how to build it....
This message is for Anyone & Everyone...
Please build Lineage Weeklies for Galaxy ON5 Pro...
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.
According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
The current software update gives you the most up to date Android security patches on your device.
Click to expand...
Click to collapse
This is basically the same thing they are doing with other devices. Since Samsung never released their September Security patch due to them addressing the BlueBorne problem, they have been re-releasing the QH* updates as QI* but they include the BlueBorne patch. For some reason, Verizon didn't include the BlueBorne patch in the changelog like they have been for every other phone.
For example. The Galaxy S6, Galaxy S8, and Galaxy S8+ updates all say
Includes: Blueborne security patch
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
Who knows why they chose to include the exact same changelog as the prior update with the same security patch. Whatever. Verizon sucks. We all know it.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
so its safe to say that the new modem ql2 is pretty much the same sa the previous update?
Updated to this build from QH2, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. If you do end up leaving, this will just be another loss for this model as no one else is updating the stock images anymore.
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Dudash said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
Click to expand...
Click to collapse
For the record, this loses root, and loses safestrap. I'm too dumb to know how to root this since I can't get TWRP on this phone, so I'm going to hope the way back to root and safestrap is get back Kitkat and then up to PB1 starting over using these steps.. This will probably be better for someone who knows what they're doing or just wants to upgrade for the security updates and doesn't care about root.
androidman807 said:
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Click to expand...
Click to collapse
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
You will also have to re-flash TWRP via Odon.
kevin98208 said:
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
Click to expand...
Click to collapse
HolyHog said:
You will also have to re-flash TWRP via Odon.
Click to expand...
Click to collapse
I too followed the instructions in the thread above for a CID 15 eMMC.
I was unable to flash the "G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip" from the OP using TWRP, but was able to do it no problem using Odin 3.12 (AP option).
After flashing that I then used Odin again (AP option) to flash the latest TWRP (https://dl.twrp.me/klte/twrp-3.1.1-0-klte.img.tar.html). I then did another factory reset on the phone (since I had already just wiped my data following the bootloader instructions) and reinstalled Magisk from TWRP and MagiskManager.
Everything looks great so far. Thanks for this update OP and for those of you providing guidance.
I have G900VVRU2DPD1 with unlocked bootloader and twrp 3.0.0-0.
Can I flash the
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip ?
If yes, after flashing, will my bootloader remain PD1 unlocked? Is it OK to have unlocked PD1 bootloader with DQI2 firmware?
Will the TWRP and root be lost? And how I can get back TWRP? Using ODIN? If root is lost then can not use flashify to flash TWRP.
If using odin to flash TWRP, then I can just flash supersu zip in zip to get root back, right?
Thanks.
I guess this is slightly off topic since it's not about this specific firmware version, but here goes ~
How do you guys go about extracting firmware/modems from stock ROM updates?? It boggles my mind lol. I'm running a OP3T now, but am working on an old device (and I still have my old S5 too). Over the years it appears people are now able to do this process for most devices and make it flashable one way or another.
I wish I understood how this gets done (and possibly figure out how to do it myself). Would love a guide / video / brief explanation with terms I could look up if it's long & involved??
Thanks for the work!
purplepenguin said:
How do you guys go about extracting firmware/modems from stock ROM updates??
Click to expand...
Click to collapse
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
bbsc said:
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
Click to expand...
Click to collapse
Hmmm and then to make flashable??
purplepenguin said:
Hmmm and then to make flashable??
Click to expand...
Click to collapse
Just pack what you want into tar archive and it will be flashable.
No need to attach checksum.
But it's possible too.
Say, this tar-file is flashable:
Missing apps
TraderJack said:
and reinstalled Magisk from TWRP and MagiskManager.
Click to expand...
Click to collapse
Can I reuse the same Magisk from the "EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip" file from the other thread on how to unlock bootloader and root, or should I download the latest Magisk and MagiskManager?
Edit 1: Okay, I installed Magisk after updating to the latest QI2 and am rooted. However, I found that I'm missing busybox and safestrap. Do I have to reinstall both of those as well or can I just reinstall busybox?
Also, QI2 lost tether/hotspot capability as it reverted back to asking to purchase the service (I'm also on the old grandfathered unlimited plan)...is there a way to get it back as when on rooted QB2?
Edit 2: Did some more research while hiding at work...so now I know, having TWRP recovery is enough and just need to reinstall busybox.
Now still need to find a way to get hotspot capability back like when on the rooted magisk QB2...
Thanks
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.