Develop Bugs

[Q] TWRP not available in recovery

Had my Tab S 8.4 wifi (t700) rooted and working but decided I didn't like the custom rom I was on so went back to stock.
Now I can't seem to get TWRP working properly. Everytime I try to use it to install a rom or make a backup the tab reboots but only into stock recovery which then throws up E: Footer errors when I try to use it.
Anyone seen this before and have a solution? I am currently stuck on stock

hefilump said:
Had my Tab S 8.4 wifi (t700) rooted and working but decided I didn't like the custom rom I was on so went back to stock.
Now I can't seem to get TWRP working properly. Everytime I try to use it to install a rom or make a backup the tab reboots but only into stock recovery which then throws up E: Footer errors when I try to use it.
Anyone seen this before and have a solution? I am currently stuck on stock
Click to expand...
Click to collapse
You will see E: Footer errors at stock recovery mode because stock recovery allows only samsung signed archive to sideload.
Or did you mean something different with E: Footer? You sentence is inaccurate.
For stock recovery image, I prepared a patched[/] stock recovery image, which will allow unsigned archives to sideload.

I was actually trying to find out why TWRP recovery is no longer available on my tablet. It was working but since loading a stock rom I no longer get the TWRP recovery only the stock one.
I have tried lots of combinations to try and get TWRP recovery working but nothing appears to work - I just get stock recovery.
I am using:
T700XXU1ANF9_T700BTU1ANG1_BTU stock rom
CF_AutoRoot_Port_T700_BeansTown106.tar.md5 to get root access with Super SU
TWRP 2.7
TWRP Manager from Play store with the recommended Busy Box installed
I am sure I am missing something but cannot see what it is - I obviously got it right before as I had it working but I have missed a step somewhere.

Try using Flashify from the playstore and flash the TWRP .img or .zip
The "dd" method is the most flawless method if your familiar with using terminal
http://teamw.in/project/twrp2/238
Nexus 5 via Tapatalk

Finally got things working. It would appear that it is all about the sequence you do things in.
1. Use odin to load stock rom
2. Set up tablet and let everything download and update
3. Use odin to get root
4. Ensure that root is working and up to date
5. Use odin to add TWRP
6. Install TWRP manager from play store
7. Install Busybox from play store and run installation in busybox
If you deviate from this sequence TWRP does not appear to work in recovery. Have now made successful backup and can start playing with custom roms again.
Thanks for all the advice.

Not to much excitement I hope. Limited to a couple Roms
Nexus 5 via Tapatalk

Just FYI twrp IS recovery, when u restore to stock twrp is overwritten by the stock recovery. Twrp is not overwritten when you flash custom roms because recovery is not packaged in the zip file. But remember stock firmwares overwrite your recovery. Also please remember not to take ota's if you are using a custom recovery like twrp

Urgent Help Needed Flashing CM13 On a GT-I9195 LTE

Hi people.
I'm in the process of flashing my friend's Samsung Galaxy S4 Mini LTE.
Here's some details:
TWRP version: 2.6.3.0 (The one some dude here made himself)
ROM: cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx
SuperSU installed
Rooted using CM AUTO ROOT
Used Odin 3.09 to install TWRP
Everything is working fine but i'm having an issue flashing GAPPS.
9195 has a Krait 300 - which is an ARM processor so i downloaded the ARM 6.0 Micro package from OpenGapps.
Wiped all partitions, queued up the ROM and GAPPS in TWRP and flashed.
The process goes by fast and smooth, but the phone doesn't boot up after that.
The first time it took 25 or so minutes to boot up and ALL the GAPPS crashed after that.
What should i do?
I tried the following alternatives as well:
Bliss-v6.3-serranoltexx-UNOFFICIAL-20160521-1003
Slim_mini_gapps.BETA.6.0.build.0.x-20160516-2250
benzo-gapps-M-20151011-signed-chroma-r3

@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.

noppy22 said:
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
Click to expand...
Click to collapse
This worked!
I thought the old TWRP version was the only version compatible with the SGS4Mini.

I'm a Newb sure, but fairly sure this isn't my fault....
Hello, I have spent the past 2 days working on this flash you've stated as well and I can't understand for the life of me what I am doing wrong. You mentioned that TWRP may not have supported the mini but it seems that it does - odin just isn't installing it right? I am hoping people on here have already hashed this out on both ODIN and TWRP for this device and after spending 24 hours figuring this out i'm wondering if it's just some stupid thing i'm doing wrong. I've put the full stuff below which you may largely be able to ignore but what i need to figure out is how to install TWRP 3.0 or higher on my device, and how to keep ODIN from crashing. Can you help?
1. where I started and my goal:
My homestay mother in New Zealand who works for the tech firm Datacom provided me with a Galaxy S4 mini (GT-I9195 spark edition) that she had left over because she got a new phone for her work. I had a galaxy note 2 running default controls due to its setup on KNOXED up verizon, so i thought this was a good opportunity to switch to cyanogen since i've used the service before (someone else went through all this trouble for me and I am eternally grateful). So I am trying to install Cyanogen mod 13 with GAPPS package nano on to it.​
2. The file repretoires and guides I used:
TWRP 2.8.1 (originally) and it's accompanied manager
Trying to upgrade to TWRP 3.0.2.0 or 3.1.0
GAPPS arm 6.0 mini/nano/pico (I've tried all three)
Odin 3.12.3 with requisite drivers (shows blue on status bar)
Default Bootloader for Android devices
CMD ADB systems with requisite drivers
CyanogenMod 13 (cm-13.0-20160820-ZNH5YAO0J7) (currently installed and working san-GAPPs)
3. What I've done Start to current:
starting with the phone locked, unrooted, and factory resets not working (company KNOX settings)
Installed Kingroot, superSU, RootChecker, TWRP manager and official ap, P-uninstall = Obtained Root
Attained root on the phone, deleted all KNOX and KGNT protection. = obtained unlocked sim/recovery loader
Installed TWRP 2.8.6 (any more recent installs failed as I will explain below in problems) Attempted to flash it = read success
Failed to boot into TWRP recovery - provided default recovery instead.
downloaded and installed ODIN. Used default boot loader and attempted to install TWRP directly through ODIN = Works
placed CM13 zip file and GAPPS 6.0 - ARMS Nano on SD card.
Created recovery on SD card
Wiped cash, devalk cache, and internal storage = clean partition
Installed BOTH CM13 and GAPPs 6.0 as zip files using TWRP 2.8.6 = worked
rebooted system into new OS
OS got stuck in boot cycle due to GAPPs package. after some googling i found out that Gapps requires TWRP 3.02 or higher (but i couldn't get those to download onto my phone at all. [here enlies the ROOT of my problem - you're allowed to kill me now]
Returned to TWRP and installed JUST CM13 on the device = works great! just no GAPPs! and no ability to download apps
Used Odin, TWRP manager, the official TWRP app, and CMD ADB sideloader to attempt to install all 3.0 and higher TWRP files = all of them failed
now I cannot access a bootloader at all, but can access my OS just fine. It refuses to accept any TWRP bootloaders but without them i cannot install GAPPS
4. Where I am Currently & Problems I'm running in to:
Right now CM13 is on and stable for my device. My Recovery loader is refusing to come up AT ALL. Attempting to install both .img and .tar files of TWRP read as succeeding in the apps but don't come up.
ODIN can't load anything on the device. Either it keeps freezing and crashing any time I touch it or when it does go through the device still can't bring up TWRP. Even when flashing 2.8.6 which originally worked as a recovery file it fails as well. I can't get back to TWRP working at all.
ADB sideloading just results in <waiting for device>. I am clearly using "fastboot" instead of ADB during the point in which i am flashing the recovery file on to it.
5. What I need Help with:
I need to know why TWRP is freezing any time i attempt to install it regardless of version and how to get it properly installed
if someone could point me to a reason odin freezes regardless of what options I tick on or off, file I upload, or whatever i'd love to know
I see 2 ways out of my predicament and i'm not sure which one I should spend more time on: 1) get TWRP 2.8.6 to work again and then find an older GAPP partition to load on to it. or 2) Get TWRP 3.0 or greater to work on it, and then use current GAPP packages. which would be best?

Oneplus 5T root problem

Hello all If any one can help me ,
I was rooted running rooted stock oxygen os before on my Oneplus 5T
after flashing Oxygen OS 5.1.4 Full Zip my phone is not rooting it gets in initial oneplus logo and freeze there without loading OS
Phone is working fine after Flashing Oxygen OS 5.1.4 Full Zip without any issue its not booting after flashing either SuperSu or Magisk
Steps which I follow are
1 Flash custom recovery I have tried both Codeworkx TWRP | Blu_Spark
2 after flashing recovery boot in to recovery flash Supersu or magisk
3 reboot
when I reboot if i Flash supersu it stuck on oneplus logo, If i flash magisk it reboot itself to fastboot so Os is not loading at all.
I have to flash full Zip again every time to get it working but then I dont have root access.
I have tried at least 10 times with different even old versions of magisk and supersu with out any success.
Is there any particular recovery or different version of magisk or superuse I need to flash?
your help will be really appreciated.

Try a different approach. Instead of installing recovery, just get phone rooted first. There is a way where you can boot into twrp (without installing it), and then flash magisk/supersu zip. If your phone is rooted, then you can install twrp later (or keep oem recovery)
This is how you boot into twrp (or any recovery): fastboot boot recovery recovery.img
Let me know how it goes.

As you said boot to recovery without installing it.
One problem currently I am installing recovery and flashing root. After that phone is not booting up in to OS it stuck on oneplus logo. Then I have to force off phone boot in to recovery and flash full os zip to get it working. I can boot in to TWRP because my os didn't load. Now if I use your method and flash root file and if phone won't boot to os that means I won't be able to boot in to TWRP again to flash full os zip to get phone working atleast without root. Any idea?

Huh, frankly I have no idea why you are facing this menace. I can just give two suggestions.
1. Try with older, more stable versions of TWRP and Magisk
2. Get yourself a custom ROM, most ROM's will work flawlessly after flashing root files
Hope for the best!

I usually switch from OpenBeta to LOS and back again. Here's how I switch back to OpenBeta (steps should work for official OOS):
1) Back everything on internal storage up. This one's important
2) Boot into official OOS recovery
3) Wipe EVERYTHING (this is why you need to follow Step 1)
4) Sideload the version of OOS you want. The instructions will be right there on the recovery screen
5) Boot into Fastboot and flash TWRP
6) Flash Magisk and (optional) Xposed

{GUIDE} - fix for being stuck at samsung boot screen due to rollback protection

Hi all I have been tinkering away and destrying my setup left right and centre to sort this process out but if you're unable to run the latest TWRP for your note from Ian and get stuck at SAMSUNG screen on boot then this process will fix that if followed correctly. This is due to the device's roll back protection.
This process will reset everything back to current date and get everything working on the new Oneui 2.1 base
Process for getting round SAMSUNG screen issue - please read through first and get the files you need before starting. I did this on my N976B but in theory it should work for other 10-range devices, notes indeed!
UNLESS YOUR RUNNING CRUEL KERNEL OR A SPIN OFF, YOU'LL NEED VOL UP AND POWER TO ACTIVATE MAGISK ON EACH BOOT
Needed:
Stock firnware
Magisk app
Twrp image
Pc and odin also patience and a brain lol
-Return to stock by flashing AP/BL/CP&CSC in odin
-Reboot and confirm oem unlocking greyed out, install magisk app and patch twrp image from Ian, also patch your ap file.
-reboot to download, meanwhile get the magisk_patched.tar and insert TWRP renamed as recovery.img in place of the stock patched recovery (keep this one for later)
-In download mode and with auto reboot off in odin, flash BL, Magisk_patched.tar(with the TWRP from Ian in), CP & HOMECSC.
-When flashing is complete exit download mode and immediately hold power and vol up and hold until on TWRP slider screen. swipe to allow modifications, format internal storage and flash multidisabler.
-Reboot TWRP and backup your current patched stock rom. FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER AND THEN FLASH MULTIDISABLER (THIS IS IMPORTANT AS YOU WILL THEN BE ABLE TO INSTALL TWRP VIA THE APP WITHOUT HAVING TO REFORMAT INTERNAL)
-Reboot straight to stock recovery (reboot from TWRP and hold Vol up and power until in stock recovery) and factory reset then reboot.
-You should now boot up as normal, setup your device, in particular have TWRP app and Magisk set up and running.
-Flash the Unpatched TWRP for your device in the TWRP app - reboot TWRP and check the box to kill that annoying swipe to allow modifications and then you are good to flash whatever rom or kernel you want for your device!

Flash the stock patch recovery as boot??

orbital_71 said:
Flash the stock patch recovery as boot??
Click to expand...
Click to collapse
yes then immediately flash multidisabler before you reboot to set up

i have just helped someone through this on TG so it defo works :good::good::good:

It can also confirm this is working. Just followed this guide on my Note 10+ (N975F with CTD1) and happy flashing now.

drexxie1962 said:
It can also confirm this is working. Just followed this guide on my Note 10+ and happy flashing now.
Click to expand...
Click to collapse
Excellent, thanks for testing!!!!!!!

@askmydas
you may find this useful - follow this to get your sec date reset then follow the process spelt out in the thread of the rom you want to use as you may need a different TWRP depending on what sec date the chef of your chosen rom uses.

Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?

KiwiNote+ said:
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
Click to expand...
Click to collapse
I worked it out, I was trying to install "recovery.img" to boot partition, "recovery.img" needs to be installed to RECOVERY partition. Silly me. Fixed it now, but have a new issue:
After I flash unpatched twrp image through the app, now my phone will only boot into TWRP. I don't even boot with recovery button presses, but it will still boot into TWRP only. Any ideas?

I know this is an old thread, but it may be that my solution could help someone who is locked on the outside of the device (softbrick)
TD,DR: If you have softbrick and you can't boot the device at all, try flashing via Odin the BL, CP, CSC from a stock rom and the AP of another completely different stock rom.
I had an IMEI 0000 issue on my Galaxy Note 8 (SM-N950F), using Hades Rom (custom), and I needed to install the stock rom. As I was on the F(15) binary, there were only two roms (SamMobile and Stockrom.net) available for my country (Brazil) with this binary:
N950FXXUFDUD6_N950FOXMFDUD6_ZTO
stockrom.net_N950FXXUFDUG5_N950FOXMFDUG4_ZTO
And a via Frija:
SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And no Combination Rom for that binary
After flashing these roms several times, I was always stuck on the “Powered by Google” screen, even doing cache wipe and factory reset through stock recovery several times. So I flashed the N950FOXMFDUD6, flashed the CF-Auto-Root and was able to boot the device. Once inside I noticed that it didn't solve the problem of IMEI 0000. I tried a few more procedures, ended up restarting to install TWRP, and the OEM is closed!!! (OEM OFF, Prenormal). I start getting the message “only official binaries are allowed to be flashed(recovery)”. I flash the stock rom, but it gets stuck on “Powered by Google” again. I tryed to install CF-Auto-Root and I get the message “only official binaries…” I can't log into the device anymore. So after four days of desperation, trying every technique possible, trying to create the Combination Rom by unzipping the AP file from the stock Rom and modifying the files inside, without success, I finally try a procedure I haven't seen anywhere else: I go to the modified Odin: Odin3_v3.14.1_3B_PatcheD, I selected the BL, CP, CSC files from the N950FOXMFDUD6 rom and the AP file from the rom SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And it worked! I can boot the device

stuck in bootloader/recovery, can't flash ROMs.

Hello,
i'm stuck in a particular situation: i can use fastboot and i can flash recoveries but none of them can succesfully flash a rom. i want to go back to the stock Realme UI, my device is RMX1993.
i tried to follow the guide (https://forum.xda-developers.com/realme-x2/how-to/to-stock-rom-howto-t4014773) but the last recovery (rmx1993-sde20-stock_recovery-c05) can't flash neither RMX1993EX_11_OTA_1040_all_tSZ3Sf5A77NS nor RMX1993EX_11_OTA_1050_all_loALrMDyMrbs.
tried to flash trough orangefox or the last twrp that support ozip decription but the result is a "succesful flash" but a phone that does not go over the boot screen and it reboot.
i succesfully installed color os trough the proper old stock recovery and it said the installation was succesfull, but the problem was the same.
someone know where could be the problem?

You need to successfully flash Android 10 (Realme UI 1.0) before you can flash custom Android 10 roms.
Have you tried this guide: https://forum.xda-developers.com/realme-x2/help/how-to-flash-q-firmware-based-roms-t4115987
As for why your colorOS back up is not working i'm not quite sure...have you wiped your cache before booting to the color os backup?