Hello!
I have installed TWRP using Odin.
Next, I have installed Super SU from my SD card.
My phone constantly boots into TWRP and I cannot perform a "normal" boot.
Any idea on how to solve this?
Thank you!
Related
Hello guys,there is a problem with my tab Lets hope you can help to me
I decided to root my tablet (T210) as i did on my other androids. I went to this thread There was no problems with odin. (I have experience about odin and everything ) Then i get in to recovery. There was no problems. I decided to boot up. Then a message appeared. Do u want to root blahblah. I said yes. Then it stuck at keeping booting to recovery. I flashed philz touch recovery too and i have same problem now. I cant reach my external sd with any of this recoveries. I can reach download mode and im downloading rooted firmware. BTW i used adb push option to push a rom to my tablets internal sd. But when i flashed it in recovery it says done and says reboot device. But its still booting to recovery.
Thanks who will help meh
This is what I get for trying to do this before I need to get some sleep. I s-off'd my M8 just a few minutes ago, and installed TWRP. Now I can't get out of twrp. If I reboot it reboots right into twrp. So I tried flashing CWM in fastboot mode, and it still boots into TWRP. However if I go into twrp and select reboot into recovery, it reboots into CWM. So if I go into CWM and select reboot system, it goes to TWRP. Somehow I have two recoveries on here. I'm really tired and would love to get some sleep.
Never mind, just installed a new rom
Lol. I'm glad that you got it figured out, it would have been hard for anyone to help in this case though.
Sent from my HTC One_M8 using Tapatalk
Just flashed a rom in cwm since it appeared to be the dominant recovery.
Sounds like you managed to flash TWRP to the system partition instead of the recovery partition.
Don't really know how, just flashed using the adb/terminal method. After that flashed CWM using the fastboot method.
Dear All,
Here's the problem:
The Goal: To Install CM-12.1 Custom ROM
What I have done:
1. Installed TWRP Recovery Manager and no matter how many times I tried, was unable to install TWRP Recovery
2. Installed Flashify, not possible to install TWRP, CWM or any other recovery!
3. Installed Rashr and finally was able to get PhilZ Touch 6 Recovery installed on the phone.
Rebooted to recovery and it's working! Great!
Now, I have the CM-12.1 zip file on the external SD card but can't flash the ROM no matter how many times I try. Yes, I did wipe factory reset and all the wipes possible, NOT ABLE TO INSTALL the Custom ROM.
The real problem now is that before I tried installing the custom ROM, I accidentally made a mistake, a really bad one too.
When my phone was starting normally, in Flashify (or Rashr, I don't remember now) I selected the downloaded TWRP recovery image for Kernel and rebooted the phone. Yes, a dumb move, I know, but for some stupid reason I did that! And now the phone won't start!!!
Getting this msg:
Set Warranty Bit: kernel
Plus, when I boot into Philz Touch 6 recovery, not able to install ROM or do anything else either.
I managed to install Aroma File Manager, and deleted some of the twrp recovery images, but still getting the kernel error.
Also, in Philz Touch recovery, I have done something wrong and I think I may have lost ROOT access. Tried several times to Re-Root Super SU but it says now install Super SU from the Market. How can I install Super SU from market if I cannot get the phone to start in the first place.
Anyway, if anyone knows how to fix these issues or has experienced similar problems, please share the steps you took to solve the problem.
All the help is appreciated!
Thanks vey much in advance!!!
P.S. Please write in comments if any screen capture is needed.
BOOTLOOP!
If anyone can, please help, I can't use my phone for over a week now!!!
the phone is stuck in bootloop!
the recovery I was using apparently wasn't the right version for my gt-i9192 and for some stupid reason it thought that my phone is gt-i9190!!! i was using twrp 3.0.0.0 serrano3gxx by the way. and i could not install the custom rom, the right rom for gt-i9192... because the recovery thinks my phone is gt-i9190... stupid right
so i installed openrecovery-twrp-2.8.7.0-serranodsxx-STABLE-signed zip file using the twrp recovery itself. and now i can't even go to recoery mode!!! WOW!! I think i ****ed up this phone big time!!!
i know there was a warning to not install the recovery using the recovery itself, but i didn't have a choice.
i did that because Odin is not working for my phone!! can't install anything with odin...
it just gets stuck and never finishes the flash. can't install anything with odin, nothing at all. just gets stuck!!
so now the problem is this stupid bootloop and on top of that i can't even get the phone to start the recovery, when I try, it goes back to this bootloop problem. by the way this is the bootloop msg:
Set Warranty Bit : kernel IN YELLOW COLOUR and the phone logo: Samsung Galaxy S4 mini GT-I9192
Hi all,
after I had a full crash while I was trying to update 4.0.0 -> 4.0.1 I now installed all from the scratch.
I now try to get root for it. I installed TWRP (twrp-3.0.2-1.28-oneplus3.img) ... opening it it asks me to bring in a PIN. every PIN I enter is wrong. If I choose cancel I am in. But System is accessable.
Anybody can post a real HowTo for getting root (SuperSU) in OxygenOS 4.0.1
Thanks in advance
After you flash the rom, flash SuperSU immediately. Then reboot to recovery, NOT to system.
If the phone stuck, force reboot by pressing power& vol.- . Reflash recovery, reboot to recovery, reboot to system.
Adb Sideload SuperSu via TWRP
Harish_Kumar said:
Adb Sideload SuperSu via TWRP
Click to expand...
Click to collapse
This worked for me!
@all: does anybody have the Stock Recovery .img for "OxygenOS 4.0.1"?
I always get this "the dm-verfiy ..." message. And after booting I have to type in the unlock PIN ... booting again ... ready to use. I think is is because TWRP
How did you do?
Skickat från min ONEPLUS A3003 via Tapatalk
null0seven said:
After you flash the rom, flash SuperSU immediately. Then reboot to recovery, NOT to system.
If the phone stuck, force reboot by pressing power& vol.- . Reflash recovery, reboot to recovery, reboot to system.
Click to expand...
Click to collapse
can you explain me what the purpose of rebooting into recovery after flashing supersu and not to system?
On some roms, you have to instal SuperSu, before first boot. Or you will not have root.
Some rooms will mess up recovery if youre first boot it's in system & not to recovery. You reboot, to recovery, first, to be shure that you have a working recovery.
This is how I did: upgraded to OOS 4.0.1, flashed the latest TWRP (3.0.3-0), copy & paste SuperSU to internal storage then flashed it through TWRP. Everything works fine.
Now I'm trying to figure out how to decrypt this phone because OOS 4.0.1 converts the Data partition file system to F2FS. I'm a heavy user of MultiROM, that's the reason for decrypting.
***EDIT***
Solved. Not sure what I did right, but installing SuperSU 2.82 via TWRP and wiping the cache twice seems to have done the trick. No pulling card or battery - ran through one bootloop and then settled down after a minute.
So I'm trying to set up a backup phone after successfully rooting my primary phone using 5.1.1 (BPA1) and having some problems. First phone went OK and is stable. This one is giving me fits.
Downgraded from 6.0.1 to 5.1.1 using Odin.
Used Kingroot and ADB to get root.
Installed TWRP 3.0.2.
Made backup before I did anything else.
Download mode shows DEVELOPER
The problem starts when I try to install SuperSU. If I install it from TWRP the phone goes in to bootloop on restart. I've pulled the SD card, re-partitioned it, reformatted it, etc.
Tried different versions of SuperSU (2.71, 2.74, 2.78) and all result in bootloop. Tried the SuperSU directly from TWRP - same thing.
RootChecker reports not rooted.
I can restore the backup with TWRP and that stops the bootloop, so I don't have a bricked phone or anything.
Any ideas how to install SuperSU and eliminate the bootloop? Or am I at some point in the process which requires something else?
Even though I was successful on the primary phone, that still doesn't mean I really understand what I was doing.
Thanks,
Spumco