I tried flashing TWRP to my device as I unlock the bootloader. But every time I reboot to recovery it does some funky stuff. How do I get TWRP to work m?
You unlocked the bootloader - right?
If so, get the latest TWRP for your device (that happens to be 3.3.1 HLTE), and flash it using the AP section of Odin. Either that, or from your rooted OS (your os is rooted, right?) you can flash it using the official TWRP app.
Related
Hi,
I have rooted G2 802 International version, with stock ROM V30B.
Now I try to install TWRP there.
Tried multiple image versions, including from TWRP download site,
last one from here http://techerrata.com/file/twrp2/g2d802/openrecovery-twrp-2.8.5.0-d802.zip
Installed through adb shell,
Code:
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
When I try to enter recovery mode I get a brief "Critical Error" message (in text mode), then promp to choose whether to reboot or enter download mode. No TWRP.
Any ideas ?
You're on LP bootloader which does not allow you boot custom kernel (locked bootloader). Downgrade to KitKat bootloader, custom recoveries and kernels are BUMPED (signed), and KK bootloader thinking these images are official, will pass it to boot.
Use AutoRec for LP from Google Play, it will do everything by one click. Because after flashing KK bootloader, official kernel of Lollipop cannot be booted too as i remember. Anyway AutoRec app will downgrade bootloader, flashes recovery TWRP and modded official kernel image, so will do everything you need.
AutoRec, you had one job...
PolishVodka said:
You're on LP bootloader which does not allow you boot custom kernel (locked bootloader). Downgrade to KitKat bootloader, custom recoveries and kernels are BUMPED (signed), and KK bootloader thinking these images are official, will pass it to boot.
Use AutoRec for LP from Google Play, it will do everything by one click. Because after flashing KK bootloader, official kernel of Lollipop cannot be booted too as i remember. Anyway AutoRec app will downgrade bootloader, flashes recovery TWRP and modded official kernel image, so will do everything you need.
Click to expand...
Click to collapse
AutoRec seems not to work. I installed the VS980 version for the Verizon variant of the phone, but all the app has is a picture of lollipops. Tapping the one at the bottom restores my (corrupted) backup, while tapping the one at the top does absolutely nothing. Any ideas?
UPDATE (8:42PM) -
Figured it out! In the SuperSU app, I disabled "mount namespace separation" and "tapjacking protection" before rebooting and trying AutoRec one more time. This enabled the hidden install button behind the lollipop icon in the app and allowed TWRP to be installed instantly. Hooray!
Hi, I tried to install TWRP using Autorec. But my phone stuck on fastboot mode. although the phone said it is d802 varient after I remove the back it says ls 980. I can run fstboot commands but not adb. Itried 5 different computers with win7/8/10. No good results. worse case is, no download mode at all. So I can not flash the phone. I tried to flash TWRP using fastboot but nothing changed. Can some one please help me
Hey everyone I just recently got a Moto X Pure with TWRP recovery already installed and the bootloader unlocked, unrooted. The phone was stuck on Marshmallow so I went to update and it would take me to TWRP recovery every time and when I reboot back into the system, I'm still stuck on Marshmallow. So I downloaded an app that would make me download OTA updates while still having TWRP recovery but it needed root access, which I didn't have. I tried all of the one-click root apps but non worked then I stumbled across an easy root method: ( oops it said I can't post links, but basically I downloaded a supersu zip and flashed it) which I followed very precisely and I'm pretty sure I did nothing wrong. But when I flashed the ZIP using TWRP and booted back into system it was stuck on the Motorola logo which I'm assuming is bootloop. I was going to download a stock recovery using fastboot but I discovered that it would relock the bootloader, which would render the device useless to me so I can't. I also tried wiping the Dalvrik Cache but it always failed. I'm new to all of this so please guys I'm desperate for help. Thanks in advance
You can flash with fastboot the newest stock(the same version or upper) without commands "...oem..." at start and the end.
Or
The newest downloadable without commands "..oem, bootloader, gpt, oem...". @Philo0o
BL will be still unlocked.
Do you have a tutorial on how to do that please?
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 @Philo0o
More accurately you need to flash boot.img which is the kernel , in the case where root was being installed using systemless mode.
Otherwise, if you tried an old SuperSU version (where systemless didn't existed or the ones that failed to detect to install using systemless method on this phone) you'll need to reflash the whole system partition (using Firmware system chunks or custom ROM zip file).
I recently downloaded the latest upgrades to the firmware. Need help with rooting this device now. It's running Oxygen OS 3.6.1 and Android 6.0.1.
u can use same methods .. like unlock boot loader and flashing any custom recovery!
You need to unlock your bootloader, then flash TWRP recovery through fastboot, and then flash Magisk or SuperSU through TWRP.
my oneplus 6t has the red ! warning and will not boot. i can get into the stock recovery menu and the fastboot menu. can someone please help me.
i unlocked my bootloader
installedd twrp (which i can only seem to get the stock recovery)
rooted
installed custom rom
and thats what i get when it rebooted.
am i just screwed or is there hope for my phone ?
skaroger867 said:
my oneplus 6t has the red ! warning and will not boot. i can get into the stock recovery menu and the fastboot menu. can someone please help me.
i unlocked my bootloader
installedd twrp (which i can only seem to get the stock recovery)
rooted
installed custom rom
and thats what i get when it rebooted.
am i just screwed or is there hope for my phone ?
Click to expand...
Click to collapse
Go to below link, download and flash latest fastboot ROM.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
If that does not work, use MS tool to recover phone to factory state.
Thanks this worked for me. Was freaking out a little. The scene has really changed since I've been here.
skaroger867 said:
Thanks this worked for me. Was freaking out a little. The scene has really changed since I've been here.
Click to expand...
Click to collapse
As an FYI, in order to root on this phone, assuming you are using Magisk (recommended) you will need to:
Unlock bootloader
Install custom rom (Optional step, but also recommended)
Then flash TWRP zip (This phone, TWRP is part of the boot.img)
Boot the phone
Reboot to recovery
Install GAPPS (OpenGAPPS Stock recommended personally, but any should work)
Then flash Magisk
sandix said:
As an FYI, in order to root on this phone, assuming you are using Magisk (recommended) you will need to:
Unlock bootloader
Install custom rom
Then flash TWRP zip (This phone, TWRP is part of the boot.img)
Boot the phone
Reboot to recovery
Install GAPPS (OpenGAPPS Stock recommended personally, but any should work)
Then flash Magisk
Click to expand...
Click to collapse
Custom rom is not required for root
bladestonez said:
Custom rom is not required for root
Click to expand...
Click to collapse
Correct. I edited my comment to reflect that, however since OP installed a custom rom, I put the step in since I figured he would have asked about it.
sandix said:
As an FYI, in order to root on this phone, assuming you are using Magisk (recommended) you will need to:
Unlock bootloader
Install custom rom (Optional step, but also recommended)
Then flash TWRP zip (This phone, TWRP is part of the boot.img)
Boot the phone
Reboot to recovery
Install GAPPS (OpenGAPPS Stock recommended personally, but any should work)
Then flash Magisk
Click to expand...
Click to collapse
Ok so my phone currently is bootloader unlocked and rooted with magisk. So if I want to install a custom rom I flash in twrp, then flash twrp (while still in twrp), boot phone, reboot to recovery, flash gapps then flash magisk?
read the OP in any custom rom you want to flash, and the dev will have the details on how to flash..
skaroger867 said:
Ok so my phone currently is bootloader unlocked and rooted with magisk. So if I want to install a custom rom I flash in twrp, then flash twrp (while still in twrp), boot phone, reboot to recovery, flash gapps then flash magisk?
Click to expand...
Click to collapse
Essentially. Each custom ROM is differrent, so make sure to read the OP of each custom ROM you try to confirm flashing instructions but that's the **general** flashing method I use. Magisk is overwritten with each flash because Magisk installs to the same partition as the kernel.
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.