Hey,
so I tried to flash Xposed Frameworks on my S6 6.0.1 with TWRP, sadly now after the Samsung Logo the Screen Stay Black and the blue Light keeps on, I cant shutdown the PHone just reboot it.
Is there anyway to fix this? I think I might overread the Part that TWRP need a different Kernel. If so, would be nice, if someone can show me a Kernel I can use.
Did you install the version specifically for the S6? In that thread, there's an uninstall zip you can flash from TWRP.
Sent from my SM-G920W8 using Tapatalk
Related
Hi everyone, I just bought a N5 yesterday (i was using a N4 for almost 2 years) and I unlocked my device using the Nexus Root Toolkit, flashed the latest TWRP, installed ParanoidAndroid as my main OS and everything was fine untill the next step...
I was an avid user of MultiRom on my N4, so I flashed MultiRom on my N5 and everything was fine, I even tried to flash the official MiUI as a secondary OS but i got some errors and I just deleted that listed rom, no biggies... after that I booted into PA and flashed a custom kernel.
First, I flashed Franco's using his tool, and everything went smooth. I even restarted the device like 2 or 3 times while i was installing the usual apps (xposed, changed the font etc), the problem started when I downloaded the HellsCore kernel app from the playstore and flashed the kernel, after that, every time I try to boot my device it gets stuck on a black screen, it doesnt even show the Google logo with the unlocked icon at the beginning, it just gets stuck at that point.
My guess was that the Hellscore kernel had some issues with Multirom, and I started the fastboot recovery via ADB and flashed Franco's Kernel again... nothing happened, I still got a black screen.
I tried flashing the entire rom again (PA) and the same, black screen.
I also tried installing the original TWRP (not the MultiRom modded TWRP) and guess what??? I stilll got the same black screen.
The only way to get past thu it is to disconnect my device from USB, press power for 10 secs and after that i have to press power+volup+voldown.
That gets me to the fastboot. If I try to boot to the OS from there, i get a black screen. If I try to boot into the recovery, it boots ok.
The only way to boot into ParanoidAndroid is using the Nexus Root Toolkit and using the Franco's Kernel (r57) to boot TEMPORARY into the OS.
I dont know what else can I try, can someone please give me some advice??? Please. D=
Thanks in advance!!!
Return to stock. Links via signature.
Sent from my Nexus 5 using Tapatalk
My phone is rooted and still running 4.4.2 with bloat removed. The other day I decided to install TWRP Manager and upon opening it up, it gave me an option to install TWRP v2.8.5.0. So I installed it and my phone would not boot back up, just stuck in TWRP. So I found this zip file LG_G3_Flash2FixStuckRecovery.zip on XDA that allowed my phone to boot back up. But now at least once a day it reverts back to TWRP and is stuck there until I install the zip again. Anyone know how to stop it from doing this?
Ive been having similar issues with my d852 and find it helps bigtime to stay away from the newest versions of twrp until they are bug free. I installed 2.8.6 yesterday and my Phone would not restart at all or it would do what yours is doing. I'm not saying that it is definitly a TWRP issue, but I am saying that once I installed 2. 8.4 the issue was gone completely. If you try going back a couple updates to an older version and it helps let me know as I'm kind of curious
HOW did you get into recovery. I got 2.8.6.1 & I do the power + vol down button thing and it doesn't take me to recovery.
Sent from my LG-D850 using xda premium
I have the sprint variant of the note edge running 5.1.1
I understand it cant be rooted with cm-autoroot unless the beastmode kernal is flashed.
The edge is currently stock. In the sprint note edge development thread, it was mentioned that it was possible to odin twrp, then flash the kernal and custom rom. I tried to odin twrp and it passed, but when i booted into recovery, the stock recovery still boots. Can this not be done on a non-rooted phone?
Guess you'll have to pull battery and pull the USB cable when the first boot screen comes, right after the recovery is flashed. It's when the status window in odin says reset and is blue. At least it is blue if you're using one of the newest odin.
Otherwise the system will overwrite twrp recovery and exchange it with stock recovery.
When the phone is off just boot into twrp recovery with the 3 button push method.
Sendt fra min SM-N915FY
Cundis said:
Guess you'll have to pull battery and pull the USB cable when the first boot screen comes, right after the recovery is flashed. It's when the status window in odin says reset and is blue. At least it is blue if you're using one of the newest odin.
Otherwise the system will overwrite twrp recovery and exchange it with stock recovery.
When the phone is off just boot into twrp recovery with the 3 button push method.
Sendt fra min SM-N915FY
Click to expand...
Click to collapse
I tried this on SM-N915P to NO AVAIL didn't boot TWRP after I pulled battery & cable after 1st bootscreen, 'Samsung Galaxy Note Edge Powered' by 'Android' ( this is the 1st boot your talking about rite) ???
the screen in Odin 3.07 & Odin v3.10.5 both said 'Pass' & was Blue
So what am I doing wrong here
Ickyz said:
I tried this on SM-N915P to NO AVAIL didn't boot TWRP after I pulled battery & cable after 1st bootscreen, 'Samsung Galaxy Note Edge Powered' by 'Android' ( this is the 1st boot your talking about rite) ???
the screen in Odin 3.07 & Odin v3.10.5 both said 'Pass' & was Blue
So what am I doing wrong here
Click to expand...
Click to collapse
Yes this is the screen I'm talking about. But you gotta be really fast. As soon as you see it boot into this screen pull the cable and battery. Otherwise it will overwrite with stock recovery.
Sendt fra min SM-N915FY
I'll give it another shot after work!
No go,
Can someone post the md5 they used for TWRP (Sprint or Tmobile) plz
so I can try it
Worked!
I tried to root with chainfire, while one 5.1.1 and it didn't let me boot, but i flashed twerp and SSU and its still not rooted but it booted and have Twrp Recovery...
it was absolutely terrifying! but it ended up all good.
Links : https://www.youtube.com/watch?v=mYw77M2jRHg
I have and att note3 with NC2 build. Busybox, superuser, and safestrap hlteatt-nc2-3.75 is installed. The phone is also rooted. Safestrap recovery is installed. The problem is that when the phone is rebooted whether manually or through safestrap I never get the splash screen for safestrap. You get the samsung screen with the custom logo at the bottom and then the phone goes to the normal bootup. Any suggestions?
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
timsmooth said:
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Uncheck auto reboot in Odin and Odin twrp.
Reboot straight from download mode into twrp and flash either smoar rom or the deodexed rom by tdunham. Did you make sure you oem lock is off ?
Sent from my SM-N920P using Tapatalk
djxn40 said:
Uncheck auto reboot in Odin and Odin twrp.
Reboot straight from download mode into twrp and flash either smoar rom or the deodexed rom by tdunham. Did you make sure you oem lock is off ?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I already helped him get back to stock so he's at least up and running.
timsmooth said:
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Use the twrp 3.0.2.0 tar.tar found via @tdunham moar for mm threads note 5 recoveries link. I had same issue until using it.
This thread can be closed. Mrmike2182 helped me fix my issue in another thread.
Please help me!
MrMike2182 said:
I already helped him get back to stock so he's at least up and running.
Click to expand...
Click to collapse
I have the same exact problem with my phone. Same model and everything. I can make it to Odin mode but when I try and boot the phone I'm stuck on the boot screen with kernel is not seandroid enforcing in red.
N_MBU said:
I have the same exact problem with my phone. Same model and everything. I can make it to Odin mode but when I try and boot the phone I'm stuck on the boot screen with kernel is not seandroid enforcing in red.
Click to expand...
Click to collapse
Download one of these for your phone. .
http://www.sammobile.com/firmwares/database/SM-N920P/
Make sure you uncheck auto reboot in Odin and as soon as it's done and says success disconnect the phone and immediately press and hold the volume down button and the power button at the same time and when the screen comes back up you HAVE to select factory reset wipe if you don't you'll be stuck again just let the little android dude install the update and then the phone will reboot and you'll be ok.
Unzip the md5 you get from the sammobile site and flash only the .tar
This is what he told me that got my phone up and working again. Be warned it is the nuclear option. All of your data will be lost upon recovery good luck.
I hate bringing old posts back to life....But I'm stuck in a series of boot loops that I can't get out of.
I was rooted on MM, decided to go back to stock for a Gallery error I was having.
Downloaded the PD2 from Sammobile, Odin'd it, appears successful.
Reboot
I get to the stock ROM setup screens and the boot loop occurs. I can't complete setup.
I've tried unticking the reboot in Odin and going directly into system recovery...then I do a Factory reset which appears successful.\\Reboot phone, back into the stock ROM Welcome screen....start the setup, and usually after adding WiFi or during Activation reboot.
Any help??
hotspace said:
I hate bringing old posts back to life....But I'm stuck in a series of boot loops that I can't get out of.
I was rooted on MM, decided to go back to stock for a Gallery error I was having.
Downloaded the PD2 from Sammobile, Odin'd it, appears successful.
Reboot
I get to the stock ROM setup screens and the boot loop occurs. I can't complete setup.
I've tried unticking the reboot in Odin and going directly into system recovery...then I do a Factory reset which appears successful.\\Reboot phone, back into the stock ROM Welcome screen....start the setup, and usually after adding WiFi or during Activation reboot.
Any help??
Click to expand...
Click to collapse
It's extremely common and has one simple solution. Let the battery completely die and then charge it up a little and you won't loop anymore
Thanks for the reply. Earlier today I visited my local Sprint store and gave them a crack at it. After about 30 minutes in the store, the tech suggested I leave with it them and they were going to completely wipe it and load the stock image.
After about an hour I went back to the store and he gave me the bad news that he was unable to get it out of the boot loop as well. They've ordered me a new device.
I really trust what you say about letting the phone battery die...but I fear that would fix it and I'd be out a new replacement device.
954wrecker said:
It's extremely common and has one simple solution. Let the battery completely die and then charge it up a little and you won't loop anymore
Click to expand...
Click to collapse
Dude!! It worked. I put the phone in download mode and just let it sit until it died.
Booted it back up and it went straight into hands free activation. And no reboots.
Why does this work?