I've been searching for a custom recovery for this device, and I've come up with nothing. I'm rooted with magisk, and decided to try porting twrp myself.... Idk what I'm doing here. I have the aik module and followed a guide, flashed the end result and it didn't change anything. Still stock. Is there anyone more skilled at this then I that will port twrp to this device?
Here is stock recovery and the twrp img I was using to port
Related
Hi guys, I faced some trouble while installing xposed with my galaxy A500F.
Here are the problem, my phone keep on boot into recovery (twrp) when i flashed any zip files except the root file recommended by this thread. http://forum.xda-developers.com/samsung-a-series/development/recovery-samsung-galaxy-a52015-sm-a500f-t3360802 .
I have tried other TWRP and Cynogen Recovery which is still the same. This one from the link which at least let me boot into normal.
The only method for me to boot into normal is to flash to the stock firmware via odin which then I need to reroot, reinstall twrp and try to figure out is there any other method with.
Restoring backup are not working as well for twrp which still boot back to the recovery. Some flash files, which event better ( this refer to the deodex http://forum.xda-developers.com/sam...nt/deodex-deodexed-samsung-galaxy-a5-t3232134 ) which stuck in that samsung loding screen while booting.
Any help would be thankful
Jacker31 said:
Hi guys, I faced some trouble while installing xposed with my galaxy A500F.
Here are the problem, my phone keep on boot into recovery (twrp) when i flashed any zip files except the root file recommended by this thread. http://forum.xda-developers.com/samsung-a-series/development/recovery-samsung-galaxy-a52015-sm-a500f-t3360802 .
I have tried other TWRP and Cynogen Recovery which is still the same. This one from the link which at least let me boot into normal.
The only method for me to boot into normal is to flash to the stock firmware via odin which then I need to reroot, reinstall twrp and try to figure out is there any other method with.
Restoring backup are not working as well for twrp which still boot back to the recovery. Some flash files, which event better ( this refer to the deodex http://forum.xda-developers.com/sam...nt/deodex-deodexed-samsung-galaxy-a5-t3232134 ) which stuck in that samsung loding screen while booting.
Any help would be thankful
Click to expand...
Click to collapse
Hello:
- First, TWRP to use and it is the only one that does not give me trouble installing ROMs Marshmallow (as Resurrection Remix, AICP or CM13) is the v3.0.0.1 of mygalaxya (download here). Steps for install: here
- Second, if you are in ROM Stock 5.0.2 and just want TWRP to install Xposed, I recommend using the v2.8.7 (here) does not give problems at all, although no use to install ROMs Marshmallow.
- Third, it is not necessary deodex the ROM to install Xposed, since there is a modified version of Xposed that works perfectly both as Deodex and Odex ROMs, you can download it from here.
If after using TWRP 3.0.0.1 (or higher) and enters Recovery restart always, I recommend the v2.8.7 flash on it for a normal boot.
I hope the information is usefull. :good:
Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker
You have to flash another version of TWRP... But, dude, i'm on the exact same case, same preview, and i can't get it to work. TWRP doesn't seem to work :/ I always got the god damn "no command" even if i follow some of the tutorials here...
EDIT : Try flashing the 3.0.0 or 3.0.1, and when all will be working (if you achieve, tell me how xD) update it.
EDIT 2 : I may find something, i'll let you know !
TWRP doesnt work with the developer previews without modifying the boot image.
If you want to root, you can use CF-Auto root.
You will still have the stock recovery.
Taker18 said:
Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker
Click to expand...
Click to collapse
This is a known issue, Search the forum for the resolution. Basically TWRP won't work on the Android N on Encrypted device.
The solution is pretty simple. You need to decrypt your device's storage. TWRP currently doesn't work with encrypted N preview.
This could be easily done by flashing the modified boot image, that will disable forced-encryption. After that, you will need to format the current userdata partition to decrypt the storage.
Code:
fastboot format userdata
fastboot format cache
Once that is done, you can flash TWRP and then use SuperSU to root.
Another way to direct root is by using Cf-Auto-Root. But I am not sure about that specifically. While some users have succeeded, there are a few who have failed to root using Cf-Auto-Root.
Just use CF-Auto Root, it will do all the things.
Make sure you have unlocked your Bootloader and downloaded the good version of CF for your device.
Reboot your phone in bootloader mode, plug it to a computer, and just open the .bat (if you're on windows, or the equivalent for Mac / Linux). It will install SuperSU. When it's done, don't forget to download the TWRP Manager on the Playstore, and you'll have a working Recovery ! I did that, i know have a rooted nexus 6P on Android N preview 5
Also, lot's of Root's only apps will not work properly, because lots of changes took place on Android N. So make sure you follow some guide out there (exemple : Ex Kernel don't work if you don't tweak some things, same with Ad Away, so make sure you're googling)
I followed the premise of this thread here so all credits go to the OP http://forum.xda-developers.com/showthread.php?t=3410906 I flashed the latest Marshmallow vendor.img via fastboot, then flashed TWRP via fastboot. Booted into recovery from the bootloader then side loaded supersu using adb side load in TWRP. After that I rebooted to bootloader from TWRP and fastboot flashed the DP5 vendor.img and recovery.img. All is working well.
So i recently installed developer image 8.0 on my 2017 16gb shield, now i want to install twrp and then flash the kernel to increase cpu and gpu clock and mainly full fan control, i have read that there is no root available but with dev image which is already rooted is it safe to install twrp and the kernel and how do i do it, thank you.
https://forum.xda-developers.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079
There is root available, works with both the developer image but also the stock ota.
All the kernel's/modified boots there comes with magisk root.
If you have no idea how to do it, I wouldn't suggest you start doing it.
But there a plenty of guides here on the forum on how to root, flash images and boot into twrp.
I guess my question is as the dev edition is already rooted do i need to install magisk or just flash the kernel which is what i wanted to begin with. So just to twrp temporarily and then flash kernel but not install twrp, i am not entirely sure.
lingarajug said:
I guess my question is as the dev edition is already rooted do i need to install magisk or just flash the kernel which is what i wanted to begin with. So just to twrp temporarily and then flash kernel but not install twrp, i am not entirely sure.
Click to expand...
Click to collapse
You can boot into twrp from fastboot.
"fastboot boot twrp.img"
Magisk is included in the kernel, so if you flash the kernel, magisk will also be installed.
I understood that part, so do i have to flash twrp after flashing kernel with temporary twrp or just leave as it is with stock recovery for it to work.
lingarajug said:
I understood that part, so do i have to flash twrp after flashing kernel with temporary twrp or just leave as it is with stock recovery for it to work.
Click to expand...
Click to collapse
I would suggest just leaving the stock recovery there.
I tried flashing twrp and ended with a bootloop, so now I just boot into twrp instead.
Hey,
I flashed twrp and then flashed Magisk and SuperSu in MIUI 10.2.4.0, 10.2.5.0 and 11.0.7.0... After flashing and rebooting my phone was not rooted, I tried many versions of Magisk and many times. But didn't work, anyone have any working files?? And does custom rom/kenrel helps rooting the device.
Thank you..
you need to patch the boot img. you can find patched boot img for older roms like that
nvm i had 2 tabs looked the same
Hi,
Disclaimer:
First post here, sorry if opening a thread here instead of replying to, e.g.
https://forum.xda-developers.com/t/rom-official-gts4lv-gts4lvwifi-13-lineageos-20.4536203/
is not correct. I've read the forum rules, and searched for similiar issues with that device, but at a glance did not find something alike.
Appologies in advance if I did a mistake or overlooked something, I'll try to learn and do better next time.
Device: Samsung Galaxy Tab S5e LTE, SM-T725, gts4lv
Bootloader: unlocked
Aim: magisk rooted twrp in recovery, lineage20
Following these instructions, I'm able to root the latest stock rom with magisk, flash that via odin, and get a magisk-patched twrp recovery:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
https://twrp.me/samsung/samsunggalaxytabs5elte.html
(Details:
Get the current stock via frija, extract AP, patch via magisk on device, adb pull to host, flash stock with odin (magisk'ed AP,BL,CP,CSC).
Reboot device into stock, finish magisk app install. Reboot once. Device rooted. Installed TWRP app, granted root permissions to it, download twrp for device, patched image with magisk, flashed that to recovery via twrp app.
Sucessfully tested twrp, looks good.)
Trouble begins when I install lineage via twrp adb sideload, following
https://wiki.lineageos.org/devices/gts4lv/install#installing-lineageos-from-recovery
with the difference using twrp instead of lineage recovery.
Coming from the magisk-in-twrp-recovery rooted stock, I did a factory reset (wipe cache/dalvik cache/data), and twrp adb sideloaded the latest lineage20 for that device.
Console command outputs look good, no obvious errors. After the initial reboot, I got a recovery boot loop.
Going back to square one, reverting to magisk rooted stock using odin.
Then, I also tried sideloading lineage19, same result.
For the record: I initally started the lineage installation also flashing NikGApps or MindTheGApps (arm64), and the fdroid priviliged extension afterwards, but got the boot loop there.
I wiped system/data/cache/dalvik, went back to magisk-in-twrp-recovery rooted stock as described above and then tried with just lineage, but still a bootloop.
Do I maybe have to once again flash the AP with the VBMeta.tar via odin prior to moving from the rooted stock to lineage?
I am a bit hesitant to do so, because
https://topjohnwu.github.io/Magisk/install.html#important-notes says
"Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading."
Not sure if the VBMeta step is only required to initally unlock the device.
I am thankful for any advice how to narrow down the issue.
Best regards
I tried to install lineage+twrp+magisk/root at the same time without great result as well.
I was able to install lineage and twrp, but when I was there it was impossible for me to "activate" Magisk
So I switched back to custom rom + twrp + magisk/root. All good, but that's not what I was searching for.
I installed Lineage from Odin, then flashed twrp. https://wiki.lineageos.org/devices/gts4lv/install.
Try this guide, if you'll have success please let me know how you did it.
See my post here https://forum.xda-developers.com/t/rom-13-official-crdroid-9-4.4541563/post-88458655
Issue is with patching twrp with magisk it seems. Use either stock Lineage recovery or follow instructions I posted.