Tried searching for a recent thread but I couldn't find one. So I got an S7 from T-Mobile today and was able to successfully root, I flashed it with ODIN but then saw it didn't have TWRP recovery. I tried flashing it, but unfortunately now I can't reboot into recovery/download mode. Is there any fix to this? Also any fix to reboots forgetting wi-fi passwords?
Any help is appreciated.
Have you tried installing a terminal emulator from the PlayStore and tried booting into recovery that way? If not open terminal app up on the phone and try type in reboot recovery to get into recovery or reboot download to reboot into download mode.
TWRP is not supported for the us devices, as the bootloader is still locked. You could backup, revert to stock and reroot. You can use flashfire to flash zips, backup, and restore. For wifi change ro.securestorage.support to false in the build.prop.
Related
I have the Samsung Galaxy S4, jflteatt, SGH-I337, AT&T, rooted, and I tried to install TWRP from a IMG file using the TWRP Manager app because nothing else was working. I can go into detail if you want but that is the summarized version. I used a DD file from the twrp website and I downloaded it to my phone, then selected it and selected install in the TWRP Manager app. It said flash successful but when I rebooted to recovery using the app my phone went into download mode. It said "Could not do normal boot" ODIN Mode. On Knox Kernel it says "Lock" Does that mean that my boot loader is locked? I think when I tried to install TWRP incorrectly it did this because my boot loader is locked. Is this true? I know I when I tried to flash TWRP from a DD file that I did it incorrectly now. Didn't do my research and tried to flash a file in the TWRP manager app that was meant to be flashed in Terminal Emulator. Dumb move on my part.
Well anyway now that Flashify is working again I tried to install TWRP from there but it just goes into Download mode every time I try to reboot to recovery even though it said "Successful". I can't even get to my stock recovery since I messed up my phone. It just goes into download mode no matter what I try. I know that TWRP will be correctly installed on my phone if I use Flashify because it has worked for everybody else but I don't know if the fact that my bootloader could be potentially locked that it could be messing it up and not allowing the custom recovery to be installed. How to I make it stop going into download mode every time I try to go into recovery mode?
Could unlocking my bootloader any trying to flash TWRP again solve my problem?
hello i have flashed twrp multiple times to my device after witnessing this and it just hasn't worked. I have tried re downloading and flashing that but no look. Basically what is happening is when i boot into my recovery the twrp logo/ boot screen comes on and keeps flashing on and off, can you tell me how to fix this please
ahuby09 said:
hello i have flashed twrp multiple times to my device after witnessing this and it just hasn't worked. I have tried re downloading and flashing that but no look. Basically what is happening is when i boot into my recovery the twrp logo/ boot screen comes on and keeps flashing on and off, can you tell me how to fix this please
Click to expand...
Click to collapse
1. Are you rooted?
2. If so, are you installing it via TWRPManager app or fastboot?
3. Make sure update recovery is unchecked in developer options.
4. If all of these are good to go, I would recommend a clean flash, booting into Android, turn on adb reboot to bootloader, fastboot flash recovery enterimgfilehere. Root after this, and install TWRP manager app. Install the write patch. Make sure update recovery is unchecked in dev. options.
5. If all of this fails, download a toolkit (with correct drivers) and let it do the work for you.
Hope this helps.
How long have you had the device? If it is new, unlock the device.
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
Hi
This is really frustrating. I own many Samsung devices and never had any issue installing twrp, so I am not a noob when it comes to firing up Odin and flashing the image however I am stuck with this device.
I used couple guides with no success. ;( I cant get rid of the Samsung recovery and replace with TWRP. Odin says success but that is just a lie.
I tried both the lollilop bootloader and the older one then TWP with various versions (3.1x , 2.8.x) No luck.
Can anyone please provide me "working files" with "simple steps" in case I am missing out on some minor details. This is SM-P900 Kitkat 4.4.2 version.
- I flash the bootloader using the BL slot in dl mode
- I reboot to downloader again and and install TWRP
- I type adb revoot recovery
Boom, I am back to frigging Samsung recovery
Hi ,
This is a follow up
The only guide that worked for me is this one. It might be helpful to others.
https://forum.xda-developers.com/ga...guide-install-official-lollipop-p900-t3154362
I had trouble getting TWRP to take at first too. It seems Samsung overwrites the recovery upon rebooting so even though TWRP flashed successfully it just gets overwritten when the system restarts. The simple solution for me was to disable the Reboot option in Odin, install TWRP, manually shut down and then enter Recovery mode. Hope that helps. I came across this suggestion either in the thread linked to above or while googling.
Im installing into properly rooted and I have twrp 2.8.7. I want 3+ TWRP.
I flash with PDA/AP and with "autoreboot" unchecked. I power off and power+home+volUP for recovery.
Tablet enters a "enttering recovery" bootloop which can be only disrupted by going into power+home+volDWN to enter Download, and than I can flash with ODIN 2.8.7.
2.8.7 is the latest I can boot into. WHAT IS WRONG?!!!!!!!!! I lost hope, with flashing 100x
Did you try updating TWRP from inside TWRP?
Sent from my Samsung SM-P900 using XDA Labs
try do a full wipe from stock recovery . after that flash twrp selecting the ap and bl in ODIN twrp3.1....tar booth of them (AP & BL)
no no no i tried everything. but than I found out this post : https://s4.postimg.org/s3pel2ekd/this_guy.png and that solved the day!!
With p900 work perfect, but install hard. With this twrp 3.1 i install lineage 14.1, all works good.
Is there any way I can grab files? I have very important data on this phone and wasn't expecting it to brick itself without warning.
I can get into flash mode and fastboot. Fastboot mode does report the phone.
It was bricked upon reboot by the recent SuperSU bug.
I cannot get into CWM/TWRP anymore, so I don't have ADB.
I have reflashed same ROM using Flashtool without wiping USERDATA. Installed newest cracked SuperSU 2.82 and disabled automatic update.