Ok, so here is a thing: i've unlocked my bootloaders, flashed TWRP, installed a Rom, have been using the ROM for 2 weeks now. The problem is, when i try to open recovory mode, it just gives me simple OEM recovery. As if TWRP was deleted. On one thread i've read that i need to install TWRP and without rebooting install supersu root. The dilema im having right now is wether flashing TWRP will delete my files. Can anyone help me?
Remygas said:
Ok, so here is a thing: i've unlocked my bootloaders, flashed TWRP, installed a Rom, have been using the ROM for 2 weeks now. The problem is, when i try to open recovory mode, it just gives me simple OEM recovery. As if TWRP was deleted. On one thread i've read that i need to install TWRP and without rebooting install supersu root. The dilema im having right now is wether flashing TWRP will delete my files. Can anyone help me?
Click to expand...
Click to collapse
No it won't. Flashing a custom recovery only affects the recovery partition. Your personal files (pics, vids, etc) are safe unless you manually wipe internal storage. You will know when you are wiping the phone because you have to read the action and allow it to happen.
Sent from my Nexus 5X using Tapatalk
Remygas said:
Ok, so here is a thing: i've unlocked my bootloaders, flashed TWRP, installed a Rom, have been using the ROM for 2 weeks now. The problem is, when i try to open recovory mode, it just gives me simple OEM recovery. As if TWRP was deleted. On one thread i've read that i need to install TWRP and without rebooting install supersu root. The dilema im having right now is wether flashing TWRP will delete my files. Can anyone help me?
Click to expand...
Click to collapse
After you flash-install recovery, while still in recovery, reboot to recovery. This should set it. Then flash supersu and reboot.
Related
Not sure what has happened. Rooted with Odin3.7/CF. Everything running great. Titanium Pro installed. Knox frozen.
Wanted to install CM ROM. Ran TWRP app to set custom recovery. Said nothing found. Ran install of latest image. Install unsuccessful. Only option after that was to reboot into download mode and reflash from the xda forum files linked above. Now it seems to be stuck as unrooted and I can't get SU/root back.
Is this thing trying to flash itself now? Anyone have a custom recovery image and settings to use with Odin? Or is this something else? Sorry for the n00b problems/questions. :'( Any help is greatly appreciated. I'm trying to get this set up for a friend, and obviously, Android/Linux is not my specialty.
Also:
Tried flashing to this and then tried running the CF-Root again. No root. No glory.
Not sure what else to do at this point. I had root before and then CM instructed to run a custom recovery before installing the ROM. So I tried that with TWRP and failed. Now it seems like it is unable to flash the CF-Root. It goes through the process then says restoring stock recovery before rebooting.
If anyone has any advice, that would be great. I'm sure it is something stupid, simple, and outside the scope of my knowledge. Thanks.
Also:
I booted into recovery mode after the TWRP failed. No custom recoveries were listed.
Originally, I tried this and rooting failed. I still ran the custom recovery with that package. Then I ran the files linked in the first paragraph above and got root. Those instructions never mentioned running a recovery after flashing to root. Is this where things got messed-up? Should I have run a recovery after that? Or was the recovery from the first attempt at getting root still on the partition? I'm so confused.
Did you manage to root it? What device is it?
Flash back to stock and start fresh
Sent from my SCH-R530U using Tapatalk
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Suren Manukyan said:
Guys here's the thing. Android N on my N5X. When trying to install TWRP 3.0.2.2 through Nexus Root Toolkit it first boots up the recovery then when I reboot to system and back there is no TWRP. But it remains there when I use the Root button which roots and installs custom recovery. So when I have root I have TWRP. Can't I have TWRP without root I wonder?
Click to expand...
Click to collapse
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
I'm experiencing this issue as well. I tried to install TWRP after installing that October security updates. I wonder if there's something in the update that is preventing TWRP from installing?
hilla_killa said:
Doesnt the toolkit have a check box to install a script or whatever to patch the system so the recovery wont be over written? Mine has it in flash recovery option!
Click to expand...
Click to collapse
It has something called perm.flash.recovery.zipor something which is described to do the thing you said but the problem is when the phone gets the" flash perm.flash.recovery.zip" it does nothing. It does nothing even when I try to flash it manually when I get the "trial" TWRP which disappears after rebooting.
Had the same problem. I solved it by using the old fashioned way, with fastboot commands found on the TWRP page: https://twrp.me/devices/lgnexus5x.html
Of course, I used the last image: twrp-3.0.2-2-bullhead.img
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
pax216 said:
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
Click to expand...
Click to collapse
Hello,
I will move your thread to the correct section, whereas experts there might be able to assist you.
Regards
Vatsal,
Forum Moderator.
pax216 said:
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
Click to expand...
Click to collapse
I find it odd that you would find a ROM that suggests CWM instead of TWRP, but the way I see it is you go back to Resurrection Remix or try to flash the new ROM you found with TWRP (2.8.7 is recommended)
You can download the .tar file for TWRP 2.8.7 here: https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
For clearer instructions, you can visit this post: https://forum.xda-developers.com/showthread.php?t=2672393
These are instructions to flash back to stock, root and install TWRP 2.8.7
I suggest right after doing this, you flash the ROM you want, that will guarantee a "cleaner" installation of the ROM
Good luck!
ShaDisNX255 said:
I find it odd that you would find a ROM that suggests CWM instead of TWRP, but the way I see it is you go back to Resurrection Remix or try to flash the new ROM you found with TWRP (2.8.7 is recommended)
You can download the .tar file for TWRP 2.8.7 here: https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
For clearer instructions, you can visit this post: https://forum.xda-developers.com/showthread.php?t=2672393
These are instructions to flash back to stock, root and install TWRP 2.8.7
I suggest right after doing this, you flash the ROM you want, that will guarantee a "cleaner" installation of the ROM
Good luck!
Click to expand...
Click to collapse
Thank you for your help. I did all the clear instructions from the thread. I couldn't get the CF auto root to stick. Also couldn't find a surfboard for TWRP 2.8.7, they only have 2.8.0 on the TWRP site, or TWRP 3.0. Ultimately I've got my original factory stock lollipop back. I'm no longer rooted. I had rooted before through KingRoot. I tried again and it says that I'm out on a list for root for my phone. So my phone works again. I guess I should be happy with that.
If you want to root, you could try flashing cfautoroot with Odin.
audit13 said:
If you want to root, you could try flashing cfautoroot with Odin.
Click to expand...
Click to collapse
I did try to flash CF auto root with Odin after I flashed back to the stock ROM. But it didn't work. It stayed stuck on the T mobile screen for a very long time. So I just gave up trying to root again and stayed with the stock ROM without root. Thanks. Maybe I'll try again and see if it'll work next time.
Flashing twrp with Odin and flashing supersu from twrp had always worked for me.
audit13 said:
Flashing twrp with Odin and flashing supersu from twrp had always worked for me.
Click to expand...
Click to collapse
Will that root my device?
Yes. When I want root with stock recovery, I use cfautoroot. When I want a custom recovery and root, I flash twrp and supersu.
audit13 said:
Yes. When I want root with stock recovery, I use cfautoroot. When I want a custom recovery and root, I flash twrp and supersu.
Click to expand...
Click to collapse
OK. Thanks. Also, which version of TWRP? I can't seem to find a download for 2.8.7.0, only for 2.8.0.0 and 3.0 on the official TWRP site. Also where can I find SuperSu? Do I flash SuperSU with TWRP once TWRP is on phone? I read somewhere that the best version for TWRP is 2.8.7.0, but I can't find it anywhere.
Twrp for T-Mobile note 3: https://dl.twrp.me/hltetmo/
Flash twrp using Odin. Olen Odin, do not check anything except f reset time. Flash twrp. When you see the word reset in the status window, remove USB cable from phone, remove battery, replace battery, use button combination to boot into recovery, connect to computer, copy supersu to phone memory, flash supersu from twrp.
Supersu: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
audit13 said:
Twrp for T-Mobile note 3: https://dl.twrp.me/hltetmo/
Flash twrp using Odin. Olen Odin, do not check anything except f reset time. Flash twrp. When you see the word reset in the status window, remove USB cable from phone, remove battery, replace battery, use button combination to boot into recovery, connect to computer, copy supersu to phone memory, flash supersu from twrp.
Supersu: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Click to expand...
Click to collapse
OK. Thank you. I will get to this next time my friend is available with the computer.
I can't get TWRP to install on my phone. I've tried manually fastbooting all three TWRP images that are available from the TWRP website. I tried installing TWRP using the Skipsoft Toolkit. Whatever I do I never get past the TWRP splash screen--no menus ever come up. Since no menus ever come up I can't install the TWRP zip or a custom ROM. I've been trying this for hours and it's driving me crazy. Is there a different procedure to boot into temporary TWRP if you are on the June bootloader? Is there another version of the TWRP image file that I'm missing? Am I supposed to let the TWRP sit there for a really long time? This is driving me completely batty.
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
I did. Will give that a try. Thanks.
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
That did the trick! Thanks.
jhs39 said:
That did the trick! Thanks.
Click to expand...
Click to collapse
Np
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
jhs39 said:
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
Click to expand...
Click to collapse
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
noidea24 said:
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
Click to expand...
Click to collapse
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
jhs39 said:
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
Click to expand...
Click to collapse
Booting into the rom, going back into temp TWRP and flashing the TWRP zip seems to have worked --TWRP actually stuck this time and I can boot directly into it now. It's a shame Google made the Pixel XL such a headache to flash on.
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Sent from my [device_name] using XDA-Developers Legacy app
androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list out what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I know it's a typo but condom kernel cracked me up. Does it automatically boot you to safe mode?
Sent from my Pixel 2 XL using XDA Labs
androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Vinnipinni said:
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Click to expand...
Click to collapse
What I' did to flash the rom was separate from rooting procedures . The phone been unlocked for months.
I did both separate times
I fastboot booted twrp.img then I installed magisk zip. I did not permanent flash twrp zip after . I only flashed the perm twrp zip after I wiped and flsahed the RR Rom . So another words I was on twrp temp boot only when I flashed the rom then I flashed twrp zip per the rom Dev instructions . But I can't make sense why you have to flash twrp after you flash a rom install .
I'm assuming it goes like this
Install latest magisk apk.
Fastboot boot twrp .img
Then perm flash twrp .zip
Then flash magisk .zip
Reboot into the O.S and check for root
Reboot into (permanent Twrp) swipe to allow modifications .
wipe stock rom with the swipe only method??
Install Rom of choice and reboot !
Or is it install Rom /flash twrp.zip for a second time then reboot
Sent from my [device_name] using XDA-Developers Legacy app
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I want to flash a rom but I'm not understanding how the pixel 2 xl works with twrp vs other devices .
If I reboot without first flashing a kernel then maybe that's the dilemma?
I just don't get why you need to flash permanent twrp .zip after you install Rom If you already had twrp permanent installed to begin with .
I' went over what I did in this thread and what I'm guessing I did wrong. So do I need special kernel for each and every rom listed . I never had to flash a kernel to get a rom to boot on any device and I've been flashing for years with T-Mobile phones on Galaxy devices and unlocked Google based phones.
Sent from my [device_name] using XDA-Developers Legacy app
I don't get why you would need to flash magisk before.
0. Make Backups and turn off security settings. Also make sure you're on the newest OTA
1. Boot into TWRP
2. Do a factory reset in Wipe settings.
3. Flash ROM
4. Flash TWRP of you want, not required but recommended
5. Reboot and set it up
6. Install magisk Manager and reboot to TWRP
7. Flash magisk and reboot
That's it.
CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
nein7three said:
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
Click to expand...
Click to collapse
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Badger50 said:
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Click to expand...
Click to collapse
Thanks a lot. Does changing kernels remove magisk?
nein7three said:
Thanks a lot. Does changing kernels remove magisk?
Click to expand...
Click to collapse
Some do, some don't. That's why you flash magisk after the kernel. But that's changing as well :good: