I have checked the OEM Unlock under developer features and had USB debugging enabled as well before flashing the philz custom recovery.
It rebooted correctly into the stock rom but after booting into the custom recovery and rebooting again I have been stuck in a bootloop.
I am able to boot into recovery or download mode successfully, however an ODIN to both an N928F and N928T have failed.
Any ideas on how to get back to a working rom?
Have you tried tge g928w8 firmware, happened to me sloved the loop. Also for me me, when flashing the custom recovery i tick no auto reboot, and boot to custom recovery first.
re: bootloops
OmarxGx said:
I have checked the OEM Unlock under developer features and had USB debugging enabled as well before flashing the philz custom recovery.
It rebooted correctly into the stock rom but after booting into the custom recovery and rebooting again I have been stuck in a bootloop.
I am able to boot into recovery or download mode successfully, however an ODIN to both an N928F and N928T have failed.
Any ideas on how to get back to a working rom?
Click to expand...
Click to collapse
If you flash @jovy23's stock modified kernel you will no longer have boot loops.
Here is the link to his kernel:
http://forum.xda-developers.com/tmo...ernel-stock-modified-kernel-touchwiz-t3229557
Good luck,
Have a great day!
Misterjunky said:
If you flash @jovy23's stock modified kernel you will no longer have boot loops.
Here is the link to his kernel:
http://forum.xda-developers.com/tmo...ernel-stock-modified-kernel-touchwiz-t3229557
Good luck,
Have a great day!
Click to expand...
Click to collapse
It was fixed by flashing the N928W8 firmware through ODIN as suggested. The N928W8 firmware was unavailable when the issue first occurred but was later released.
Thank you for the suggestion though.
Related
I tried to unroot my phone after getting stuck in a cyanogen bootloop a while back. I managed to get into recovery and install stock firmware via Odin. I did not however install the stock kernel or stock recovery. I am now in a stock t-mobile bootloop. I'm not sure what to do, I have been unable to get into recovery thus far, but I can keep trying. What can I do?
lasabrjotur said:
I tried to unroot my phone after getting stuck in a cyanogen bootloop a while back. I managed to get into recovery and install stock firmware via Odin. I did not however install the stock kernel or stock recovery. I am now in a stock t-mobile bootloop. I'm not sure what to do, I have been unable to get into recovery thus far, but I can keep trying. What can I do?
Click to expand...
Click to collapse
Can you get in Download mode? To work with Odin you must be in Download mode, not recovery.
If you can get in Download mode, then start Odin and flash a TWRP Odin flashable recovery:
http://teamw.in/project/twrp2/101
Then at least you should have a functional recovery. From there you could either try to flash your stock ROM again, or any another ROM.
Are you 100% sure what you flashed was a good stock ROM for the T989 ?
Dont you have a nandroid you could restore?
Ok, I made a mistake when using another ROM, and had to flash stock firmware mentioned above because I had OEM unlocking turned off at the time.
The problem is, now when I install TWRP or unikernel for root through odin, it says, depending on which I try to boot,
KERNEL IS NOT SEANDROID ENFORCING
or
RECOVERY IS NOT SEANFROID ENFORCING
Using odin.
and the touch screen is completely disabled. The only way to get touchscreen working again is to flash stock firmware again.
What do I do? OEM unlocking is turned on. What am I missing?
Does it have something to do with installing a ROM and choosing that Samsung option of security/remote locking or whatever during setup?
I cannot figure out what to do. As soon as you use kernel or recovery that is not seandroid enforcing, the touchscreen becomes unusable.
---
Also, as I try to fix this, is there a way to just extract only the kernel from this firmware so I can reflash just it if this happens again? I tried just extracting boot and recovery via odin but recovery doesnt resolve the kernel error and boot just makes it reboot in a loop.
H0wdy said:
Ok, I made a mistake when using another ROM, and had to flash stock firmware mentioned above because I had OEM unlocking turned off at the time.
The problem is, now when I install TWRP or unikernel for root through odin, it says, depending on which I try to boot,
KERNEL IS NOT SEANDROID ENFORCING
or
RECOVERY IS NOT SEANFROID ENFORCING
Using odin.
and the touch screen is completely disabled. The only way to get touchscreen working again is to flash stock firmware again.
What do I do? OEM unlocking is turned on. What am I missing?
Does it have something to do with installing a ROM and choosing that Samsung option of security/remote locking or whatever during setup?
I cannot figure out what to do. As soon as you use kernel or recovery that is not seandroid enforcing, the touchscreen becomes unusable.
---
Also, as I try to fix this, is there a way to just extract only the kernel from this firmware so I can reflash just it if this happens again? I tried just extracting boot and recovery via odin but recovery doesnt resolve the kernel error and boot just makes it reboot in a loop.
Click to expand...
Click to collapse
---
UniKernel-v6-920P-072915.tar
this one worked.
After that, using twrp manager from google play then letting it install twrp worked.
Hello,
I was trying to flash the newest version of TWRP on my Note 4 by flashing the image within TWRP(as the instructions suggested). What I did not notice was that I had an older version of TWRP installed than the one recommended in the instructions. After flashing the image and reboots the phone enters the download mode, and I am not able to proceed into recovery mode.
I downloaded the newest version of odin and flashed TWRP using the AP mode. By utilizing the auto-reboot setting I was able to boot into the OS, and everything seems to work fine. However when trying to reboot into recovery I still get the download mode. Is there any way to fix this?
All answers are greatly appreciated.
Sorry for bump.
Anyone?
fezken said:
Sorry for bump.
Anyone?
Click to expand...
Click to collapse
Are you Rooted, or are you trying to root using this method? If you're rooted download flashify and download TWRP, or CWM, or Philz for the device and it should be successful. If it's not, please reply back and i can see what's going on.
Thank you for the reply. Yes, I am indeed rooted. I tried flashing TWRP through flashify, but my phone still enters download mode when rebooting after flash. "Could not do normal boot" in the top-left corner. To make the phone boot into the OS I have to flash TWRP through Odin. This solves the "booting into the OS"- part,but when I try to boot into recovery I get the download mode aswell. I am thinking that I might have to wipe everything and re-install TWRP and the custom ROM(emotion rom MM). What is the best way of doing this?
Jonas
My phone is stuck on twrp recovery bootloop after i ****ed up and tried to install an OTA update help ?
yakujana said:
My phone is stuck on twrp recovery bootloop after i ****ed up and tried to install an OTA update help ?
Click to expand...
Click to collapse
Reboot to bootloader and flash stock recovery
Yep and if it works flash blu-spark twrp it should be fine.
Yeah, I went through a lot of steps, but basically install stock recovery v2 and let it restart. Once it succeeds or fails, it will go back to normal, and you can flash whichever recovery/rom combination you prefer. I don't have the official url, but this one seems legit:
https://www.androidfilehost.com/?fid=385035244224403547
Hi, i'm having trouble flashing back to stock.
I've got the latest stock firmware from sammobile.
Using twrp to install it says missing META-INF as the firmware zip isn't made the same as custom firmware.
Adding the tar.md5 to ap in odin flashes the boot and recovery but goes extremely slow when it starts flashing system (left it 2 hours and it hadn't even got half way) I'm guessing that's not normal.
I took a backup with twrp before I started flashing in twrp which flashes fine but I get endless boot loop when trying to start it.
I've tried fastboot but it doesn't detect the tablet.
I've tried different usb ports, cables, different versions of odin and different stock firmware. I'm ready to throw it out the window.
One thing to note is the [P600][Touchwiz] Marshmallow Rom 20170622 works great but also boot loops when I turn it off and on again, I have to boot into twrp then choose reboot in there and then it boots ok, that doesn't work with my twrp backup though.
Anything I'm doing wrong?
Thanks.
Well for some reason after installing marshmallow rom again then installing my backup it boots fine, havn't a clue why it failed to boot the other 4 times.
Nope
Back to continuous boot loop after second reboot.
All I did was turned developer options off and it's boot looping again.
Flashed original stock boot.tar.md5 and recovery.tar.md5 then factory reset and wiped cache but still boot loops.
Is it because I flashed a Marshmallow custom rom so it so you can't downgrade to a lolipop rom even though it's stock? Boot loader changed? Kernel?
Mazert said:
Is it because I flashed a Marshmallow custom rom so it so you can't downgrade to a lolipop rom even though it's stock? Boot loader changed? Kernel?
Click to expand...
Click to collapse
I'm not quite sure what your problem is but you should be able to downgrade, I've done it before.
Try this guide first. I've had success with it.
If all goes well you can then try to flash your stock ROM. The one I've flashed successfully in the past is the one in this post.
Good luck!
You may need to repartition your system. Tick the repartition in Odin. **All data will be lost**
Sent from my SM-N915G using Tapatalk
Thanks, I followed the guide in that post and it flashed ok then I finally managed to flash the latest stock!