I successfully rooted my old Note 9 last night. First success since rooting 15 years ago... It seems to be a matter of whether TWRP's download mode flashing works or not. In the case of the Note 9, after entering the download mode, the TWRP installation was successful at once, and the TWRP screen was displayed immediately after entering the recovery mode... I chose a rom and installed it well and it works well...
I am urgently waiting for when the normal TWRP and ROM of S918N will come out...urgently...And my ultra, which was in a terrible loop last time and could not be used due to the detection of rooting machines as all gold meat apps and Samsung apps, is currently somehow recovered and still has a warning message at the bottom, but the app has been recovered to a state where it can be used,.ㅠ ㅠㅠ
[RECOVERY][UNOFFICIAL] TWRP for Galaxy S23 Ultra
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Related
Hello
i tried many times Easy Magic TWRP installer/Easy Magic PhilZ Touch installer both, auto & manual both not working, on auto when it near to finish my tablet auto disconnected from pc & Easy Magic PhilZ Touch installer says port successfully but on recovery mood same old stock recovery, when i try to do manual it gave error in the last, Aborting, Ported recovery.img is too large & causes region overlap! i tried to use 7mb partition way to fix it but no success.
my tablet is some chinese unknown company tablet with mt6580 (MT8752) chipset & running android lollipop 5.1, i already rooted just want to install custom recovery, any help will be highly appreciated.
Regards
Edit: I ported TWRP successfully, i used google nexus 7 2012 tablet TWRP 3.0.2.0 to port , now everything working fine but the screen is flipped, I mean the TWRP screen showing menu & buttons etc on portrait but the touches input act like the TWRP screen is landscape which is a headache! so can you please help me what need to do to fix this issue.
Thanks
Regards,
I flashed a MARSHMALLOW v014 on my COOLPAD NOTE 3 mobile phone , then flashed twrp 3.0.1 and supersu 2.4 in order to root my device to open it for large scope but unfortunate occurred. Initially when I flashed supersu in twrp recovery it installed and device was rooted as shown in root checker but later after 10 min of doing this suddenly my hardware power and volume button stopped working and even my device was not charging when charger was Connected I don't know what went wrong in OS, bootloder whatever but how to tackle with these kind situation in order to save my device, as when it's gets off after draining battery totally neither I can't charge after turning off nor can boot using power button and not even I can enter in recovery mode how to save my ANDROID
:crying:
My Nook HD+ bootloader won’t launch the installed OS, CM 13. The Nook screen appears, and then gives way to the Cyanogenmod Universal Bootloader. After a bit the blue android image appears. It pulses normally at first, then the pulsing pauses, and finally the process starts all over … and over, and over, and over!
At first I thought there was a problem with the OS, so I booted into recovery (TWRP 3.1.1-0) and tried to flash CM 13 for ovation. That didn’t work, so I tried flashing other ovation ROMs. None will install. They all report an ERROR 7. I’ve attempted to work around that error, but none of the methods I’ve found made any difference.
It seems that I may have to reinstall the factory/stock ROM, and I’m okay with that. But it seems I can’t do that either. The stock rom download is in a CWM backup format, and I have TWRP, not CWM. So I tried to flash CWM with TWRP, but in order to make that work one has to reboot into recovery via TWRP, The problem here is that the TWRP boot menu has just two options … System and Power Off. The Recovery option that is supposed to be there isn’t!
So I tried to replace TWRP with CWM via ADB. I can sideload a CWM zip without a problem. I then issue an ADB Reboot Recovery command. But, instead of rebooting into recovery, the bootloader launches instead. As a result, when I go into recovery it’s still TWRP. I’ve also tried powering on with the CWM bootable image file on an sd card, but no matter how many times I power off and back on, my tablet never recognizes that the file is there and my problem persists.
Is there a way to boot into CWM or swap CWM for TWRP in a situation like this? I’ve seen postings that suggest fastboot may the be solution, but that requires that debugging be enabled, and it was not enabled when my problems began. Apparently there is no way to enable debugging without launching the OS.
Help!
Update:
My Nook HD+ has not rewarded my attempts to bring it back to life Perhaps I’ve made things worse. I certainly haven’t made things better. Here’s the latest.
When booted up, little or nothing has changed. At bootup the Nook screen is followed by the Cyanoboot Universal Bootloader screen. Sometimes it gets no further, and reboots. More often the android image appears with a halo pulsing in the background. Sometimes the halo pulses a couple of times before the device reboots. Sometimes is pulses a bit longer before rebooting. Sometimes it never stops pulsing (until I press and hold the power button to shut the bloody thing down, that is).
Thinking the problem was related to the OS (I had been running android 7.1.1 (an unofficial HD+ release, but from a very reliable source), I've tried in vain to flash another OS. I've tried multiple android releases, from 7.1.1 down to 4.4.4. I've also tried flashing several versions of the HD+ factory stock OS. I’ve done all this using TWRP, and also by booting CWM from an sd card. No matter which recovery I've used or which OS I've attempted to install, the process always ended with an ERROR: 7.
So, I got my hands on a good Nook HD+ running android 5.1.1. I made unbundled TWRP backups of the System, Boot, and Apps partitions using release 3.1.1-0. The System and Boot partitions each restored without a problem. The Apps would not restore, ending with “extractTarFork() process ended in ERROR: 255." That error probably isn’t related to my problem, which is that I can’t get the system to boot up. More telling is the fact that after successfully restoring the System and Boot partitions using the backup from a good HD+, when I power up the device appears to be launching 7.1.1, not 5.1.1. The android image displays in portrait mode on the good HD+ running 5.1.1, but displays in landscape mode on my HD+ ... and the boot loop continues, of course.
At this point, at the $7.25/hour minimum wage rate I’ve spent enough time that I could have earned many times the original cost of the HD+. So, am I giving up? HELL NO! Now it’s personal!!
My HD+ boots into TWRP flawlessly, so I still have that going for me. My HD+ is not rooted and did not have USB Debugging enabled when it crashed, so any solution requiring SU or flashboot is a non-starter. Otherwise, I’m willing to give anything a try. Maybe I should be looking for an exorcist?
Thanks for reading this, and for your suggestions, words of encouragement, and expressions of sympathy.
I installed stock Android 10 Q (from 9 P) via Odin on my galaxy tab s6 LTE, then i unlocked the bootloader and rooted with magisk (manager 7.5.1, zip 20.4) following the magisk git site installation instructions (which are a bit more complicated than from some third party sites.)
Everything ok, but then when i power off it reboots. It's not in a bootloop: it boots up normally, but if i can't power off then that's not good when I'm not using it. I tried patching again and checked i got the the same md5.
Eventually i found that if i booted to recovery mode and there i choose reboot, it reboots to unrooted, but it does power off.
To get root access again i start with the recovery key combination but let go at the splash screen before it enters stock recovery mode. This means that i have to reboot each time i want to either switch it off or have root (but not both.) It's good enough for now, so I'm posting this in case anything else has the same problem.
Hi Fols
completely stuck - have had pixel experience on Xiaomi Note 5 PRo for 6 monts no issues have just tried to OTA update - it seems it was doing it but stopped at the TWRP screen - there are NO BUTTONS or prompts available just the TWRP initial screen - NO interactive elements - it doesnt matter whether i Power off / Power OFF while hoding UP or Power off while Holding DOWN - it ALWAYS shows MI logo / bootloader unlocked and then Teamwin screen appears nothing happens - simply not good enough by the Pixel Experience team to advertise as capable of doing OTA updates without testing it works first - HELP !! Please if you can - as it stands ive lost all my Data
Anyone ?
Fastboot boot recovery.img
When the answer is to short then look here
✏ How to use TWRP without flashing it (e.g. for Backup)
I already posted it here, but I’m pretty sure many people aren’t aware of this 😉 I found a way to boot TWRP without flashing it, so you only boot it from your computer, do what you want and as soon as you shutdown your phone, it’s just as it was before. 🙂 TWRP is a great tool for many things...
forum.fairphone.com
Test the orangefox img
hi folks thank you - got it sorted with Orangefox - but not until i i ballsed up the first attempt by trying to set filesystems to that new f2fs one , but got it done and didnt lose my photos in the end - (thank heavens for the Google ecosystem and Android) - thanks @joke19 for posting
joke19 said:
Fastboot boot recovery.img
Click to expand...
Click to collapse
I have exactly the same issue on my Redmi note 5, after auto rebooted by the update, the system stucked at the TWRP inital screen;
I tried to force shut it down by holding power button, then holding volume down botton, fastboot screen appeared, but nothing changed or happened in windows device manager, so fastboot commands are not available.
I also tried to drained the battory by leaving it alone until the TWRP initial screen off, after charging it for a few minutes, it auto powered on, loaded into TWRP initial screen, stucked again, even I booted it into fastboot mode again, windows device manager had no any android device or unrecognised device appeared. I guess that the usb interface was disabled during the OTA update.
My cell phone now is an iron brick...plz help...
dumbledon said:
hi folks thank you - got it sorted with Orangefox - but not until i i ballsed up the first attempt by trying to set filesystems to that new f2fs one , but got it done and didnt lose my photos in the end - (thank heavens for the Google ecosystem and Android) - thanks @joke19 for posting
Click to expand...
Click to collapse
It's good for you.
The Orangefox didn't adapted it to Redmi note 5, my cell phone is going to be a brick 4ever...