Aloha guys,
I was trying to install Xposed and, regrettably, I didn't look into it as much as I should've before trying to install it; I'm inexperienced with all this.
Long story short, I installed the apk, went to install the framework through TWRP and then when I tried to restart the phone afterwards, it will show the Samsung screen and then a pulsating Blue LED light with a pitch black screen. From there, I am able to get it back into Odin mode and TWRP but I havent been able to get the phone to actually restart. I have no clue, but maybe I didnt install the correct framework? I just chose the most recent version in Arm64 v. 86. Super worried here that I ruined my phone and would appreciate any suggestions!
Mahalo
Model: SMG92P
Build: F2
Firmware: 6.0.1
APK from here: http://forum.xda-developers.com/showthread.php?t=3034811
http://forum.xda-developers.com/showthread.php?t=3180960
Sent from my SM-G920W8 using Tapatalk
DarryDoo said:
http://forum.xda-developers.com/showthread.php?t=3180960
Sent from my SM-G920W8 using Tapatalk
Click to expand...
Click to collapse
Okay, I appreciate the link. Are you saying my solution is the "adb logcat" ? Is my issue considered a bootloop?
Really appreciate it.
I'm saying you installed the wrong version of Xposed.
There's a flashable zip to uninstall Xposed in the link I provided. Flash it, then flash the correct Xposed zip, and hope for the best.
Sent from my SM-G920W8 using Tapatalk
---------- Post added at 06:53 ---------- Previous post was at 06:52 ----------
Actually, use the uninstaller from your original link.
Sent from my SM-G920W8 using Tapatalk
black screen
Managed to do the same thing to my S6 trying to install Xposed for the first time, phone was rooting using Odin3
CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar
Installed XposedInstaller_3.0_alpha4.apk & TWRP via Flashy, restarted and used xposed-v86-sdk23-arm64.zip but black screen with bluelight on reset, managed to enter recovery mode after learning how to do it but it's the default samsung one it seems, no idea where TWRP went?
Any idea what to do?
Tried clearing the cache and formatting with the default recovery thing still won't load please don't tell me i bricked this thing
Edit* Managed to fix it by using Odin3 to restore original firmware but i'm not sure what i did wrong in the first place to cause it to hang if anyone can glance at the filenames above it's all correct right? perhaps it's because i didnt uhh, deodox or whatever it's called? seems so hard just to get this framework running ugh!
And how do i make it so TWRP stays, seems i had to keep flashing it to use it? seems i triggred my KNOX void status to 1 also messing with Odin3 ah well!
you need to use ODIN to restore the phone, after that it should boot. As for twrp, install via ODIN and boot into recovery immediately. if you install twrp then boot to android it will automatically replace it with the stock recovery. On first boot TWRP patches the phone so it doesn't get replaced.
And use the S6 version of Xposed that Wanam created. See my link above.
Sent from my SM-G920W8 using Tapatalk
Thanks guys, ended up going with "XtreStoLite-ROM-3.3.1-DPDP.zip" because i didn't know if "CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5" was deodoxd or whatever
was able to boot with this, but "xposed-v86-sdk23-arm64.zip" created a bootloop, uninstalling with TWRP and running "xposed-uninstaller-20150831-arm64.zip" solved it
"xposed-v86.0-sdk23-arm64-custom-build-by-wanam-20160709.zip" didn't cause a bootloop and i finally managed to get onto the phone!
Sorry for the long file names just hoping it helps someone else it appears i voided my KNOX warranty thing by using Odin, oops it's not even a very old phone either i'm just hoping now the above stuff doesn't comprimise my phone and contain anything like keyloggers ect!
Hi gents.
Few minutes ago I managed to perform same mistake here.
Now,my phone displays only SAMSUNG label and blue LED is on.
Both of those are slowly "breathing" repeatedly.
I am not able to switch the phone off,in order to enter recovery or download.
How did you managed to get into download mode?
Very long power hold doesn't work.
Thank you,Tomas.
Edit>
Nevermind,I managed to power it off.
Here are some tips:
1. Simulated battery removal:Hold Vol.Down+Power
2. Entering download mode: Hold Vol.Down+Home+Power,confirm by Vol.Up
3. Recovery: Hold Vol.Down+Home+Power to get into download mode,don't confirm download by Vol.Up button. Then hit the Vol.Down button(Cancel) and immediately hold Vol.Up+Home+Power
In recovery,there is an option to turn off the device,what stops to drain the battery.
Hey there,
i managed to get the same error on my phone
Yesterday i installed xposed, now its stuck with a blackscreen and the blue LED, or sometimes with the Samsung Sign and blue LED.
I tried to flash the stock firmware with Odin 3.12 but it fails with a write error after a few seconds. I already tried to wipe and clear cache in recovery.
So can you guys give me any idea how i can get my phone to boot again? :/
Thanks:fingers-crossed:
Related
Hello,
I had a rooted verizon galaxy s3 (CM10) and I recently got stuck in a boot loop. So I connected to Odin and flashed both MD5 files and the root66.tar file, booted into recovery and tried to do a factory reset.
The problem is my power button won't work in recovery mode, so I can not select anything in the menu. The volume buttons work I just cant select anything.
I've searched all over for 2 days now and I can't find anything about my problem, am I screwed or is there something I haven't thought of yet?
Thanks preemptively for the help.
bump please help
Maybe possible to send commands to phone via adb?
Sent from my SCH-I535 using xda app-developers app
Which recovery you are using? Try twrp which recognises touch so no need of power button to select any option. I think class cwm also has touch based recovery.
Thanks doesn't hurt....
Thanks for the replies, I tried to run adb but just runs a lot of code then closes out. I tried to re-download and the same thing happened.
I was using the stock.vzw.root66.tar and BOOTLOADER_I535VRALF2.... I flashed them many times and nothing has changed it still just gets stuck on the 4G LTE screen. Where would I go about finding the recovery files you mentioned? I'm willing to try anything at this point.
Thanks again for the replies.
TotallyAGG said:
Thanks for the replies, I tried to run adb but just runs a lot of code then closes out. I tried to re-download and the same thing happened.
I was using the stock.vzw.root66.tar and BOOTLOADER_I535VRALF2.... I flashed them many times and nothing has changed it still just gets stuck on the 4G LTE screen. Where would I go about finding the recovery files you mentioned? I'm willing to try anything at this point.
Thanks again for the replies.
Click to expand...
Click to collapse
If it's stuck at the LTE logo, boot into recovery and factory reset.
Edit: to Odin flash CWM or TWRP, you can find both files in Open1your1eyes0's root thread in the dev section. Use either once you're rooted.
Sent from my SCH-I535 using xda app-developers app
If you just want this to be fixed quickly, you could always flash a Full-wipe rom that contains the bootloader, etc. Then after your back in the stock rom you could always re-unlock the bootloader, install custom recovery , re-root and flash whatever rom you wanted.
Surge1223
Thanks for the replies, I've searched the internet for a full-wipe rom and I cannot seem to find one, can you point me in the right direction?
Also sorry for the delayed response, I actually graduated college yesterday.
EDIT: Now I can't get the phone to boot into download mode or recovery mode, the Samsung logo comes up and the screen goes black. I'm pretty sure my phone is ****ed.
What was the last change you made? Also are you using the oem cable? Also, heres the link scroll down to section 5. http://forum.xda-developers.com/showthread.php?t=1762709
Surge1223
I was trying to update TWRP so I can install a 4.4 ROM and I installed Flashify (I read this was the easiest way) then flashed TWRP 2.6.3.1 and when I rebooted it went right to a black screen. When it boots I see the Samsung screen for just a sec and tiny blue words in the left corner that says something like 'recovery booting'. I've tried a hard boot (volume ^ + home then power on, right?) Well the phone buzzes, SAMSUNG flashes for a millisecond then blaxk, Maybe I'm not doing the hard boot correctly? But it's hard to tell. I'm trying to get back to TWRP to restore a backup image!
Please help and thank you.
Mixmode said:
I was trying to update TWRP so I can install a 4.4 ROM and I installed Flashify (I read this was the easiest way) then flashed TWRP 2.6.3.1 and when I rebooted it went right to a black screen. When it boots I see the Samsung screen for just a sec and tiny blue words in the left corner that says something like 'recovery booting'. I've tried a hard boot (volume ^ + home then power on, right?) Well the phone buzzes, SAMSUNG flashes for a millisecond then blaxk, Maybe I'm not doing the hard boot correctly? But it's hard to tell. I'm trying to get back to TWRP to restore a backup image!
Please help and thank you.
Click to expand...
Click to collapse
Try to hold volume up + home + power until you see the blue text. Let go of the power button but keep holding volume up + home until it Boots into recovery.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Try to hold volume up + home + power until you see the blue text. Let go of the power button but keep holding volume up + home until it Boots into recovery.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'm doing that, or trying to but I'm still getting nothing. Problem is, I cant tell when the phone is on or off, I've done it by pulling the battery and by long pressing the power. I'm holding vol ^ + home + power, as soon as the blue text shows, I release only power and nothing, black screen. UUUUGH
I'm trying it over and over but still not getting anywhere.
Mixmode said:
I'm doing that, or trying to but I'm still getting nothing. Problem is, I cant tell when the phone is on or off, I've done it by pulling the battery and by long pressing the power. I'm holding vol ^ + home + power, as soon as the blue text shows, I release only power and nothing, black screen. UUUUGH
I'm trying it over and over but still not getting anywhere.
Click to expand...
Click to collapse
Hmm, you only have access to Odin mode right?
Download the latest recovery and try to flash it with Odin:
http://techerrata.com/browse/twrp2/d2vzw
I have a feeling this isn't going to work, but it might let you boot into recovery. And do you have your backups on the internal or external SD card?
Edit: I forgot to mention to make sure to use the.Tar.Md5 file, not the .img file.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Hmm, you only have access to Odin mode right?
Download the latest recovery and try to flash it with Odin:
http://techerrata.com/browse/twrp2/d2vzw
I have a feeling this isn't going to work, but it might let you boot into recovery. And do you have your backups on the internal or external SD card?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I just got it into ODIN mode. says Downloading dont turn off. I plugged in USB and it installed properly but it's not shown in 'My Computer'. I haven't used ODIN in a long time, what do I do now? Do I DL the TWRP .img or .tar?
SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
OK I have the .TAR file downloaded. It seems to be frozen on this Downloading dont turn off screen.
Mixmode said:
I just got it into ODIN mode. says Downloading dont turn off. I plugged in USB and it installed properly. I haven't used ODIN in a long time, what do I do now? Do I DL the TWRP .img or .tar?
SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Click to expand...
Click to collapse
Download the .tar and extract the tar.md5 file.
Put the tar.md5 file into the pda slot, make sure your phone is connected, and it'll reboot by itself.
If it doesn't reboot properly, try to pull the battery and force it into recovery again like before.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:40 PM ---------- Previous post was at 07:35 PM ----------
Mixmode said:
OK I have the .TAR file downloaded. It seems to be frozen on this Downloading dont turn off screen.
Click to expand...
Click to collapse
It's supposed to do that.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Download the .tar and extract the tar.md5 file.
Put the tar.md5 file into the pda slot, make sure your phone is connected, and it'll reboot by itself.
If it doesn't reboot properly, try to pull the battery and force it into recovery again like before.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
So weird... the phone seemed to be stuck in the Downloading screen so I rebooted it and it went right to my last backup image so I was gonna reboot to recovery so I can wipe any junk away and restore my most recent image and it went back to the black screen. OK I downloaded ODIN again and its coming back to me. I'll report back in just a few.
Mixmode said:
So weird... the phone seemed to be stuck in the Downloading screen so I rebooted it and it went right to my last backup image so I was gonna reboot to recovery so I can wipe any junk away and restore my most recent image and it went back to the black screen. OK I downloaded ODIN again and its coming back to me. I'll report back in just a few.
Click to expand...
Click to collapse
If you can get into a rom, it's better just to use that to update a recovery, just don't use flashify this time.
We'll see how this goes.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Download the .tar and extract the tar.md5 file.
Put the tar.md5 file into the pda slot, make sure your phone is connected, and it'll reboot by itself.
If it doesn't reboot properly, try to pull the battery and force it into recovery again like before.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:40 PM ---------- Previous post was at 07:35 PM ----------
It's supposed to do that.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Ok I think that fixed it. I am on TWRP 2.6.3.1 restoring a backup I made earlier as we speak. THANK YOU!
Btw, what caused all of this was I flashed the Dirty Unicorn 4.3 and lost my mobile data. I went on to mobile providers and its a crap shoot when picking one that works consistently...
CDMA/EvDo auto
LTE/CDMA/EvDo
LTE/CDMA/EvDo/GSM/WCDMA
each on of those have worked before but none work every time and sometimes I will have tried to use them all several times before one finally kicks on. But if I reboot or even shut off data then back on it farks everything up again.
So I was trying to go to a 4.4... is there anything else I need to do to flash a 4.4 rom? I was thinking of trying the Cyanfox. Liquid Smooth became buggy so I went to Dirty Unicorn. But I gotta have mobile data
Mixmode said:
Ok I think that fixed it. I am on TWRP 2.6.3.1 restoring a backup I made earlier as we speak. THANK YOU!
Btw, what caused all of this was I flashed the Dirty Unicorn 4.3 and lost my mobile data. I went on to mobile providers and its a crap shoot when picking one that works consistently...
CDMA/EvDo auto
LTE/CDMA/EvDo
LTE/CDMA/EvDo/GSM/WCDMA
each on of those have worked before but none work every time and sometimes I will have tried to use them all several times before one finally kicks on. But if I reboot or even shut off data then back on it farks everything up again.
So I was trying to go to a 4.4... is there anything else I need to do to flash a 4.4 rom? I was thinking of trying the Cyanfox. Liquid Smooth became buggy so I went to Dirty Unicorn. But I gotta have mobile data
Click to expand...
Click to collapse
I really have no idea what caused it. I've never flashed anything other than 4.1 TouchWiz roms, but I know it's an intermittent issue with aosp roms.
You probably had a bad twrp image when you flashed it, or did something incorrect in flashify. I'm glad you got it working again though.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I really have no idea what caused it. I've never flashed anything other than 4.1 TouchWiz roms, but I know it's an intermittent issue with aosp roms.
You probably had a bad twrp image when you flashed it, or did something incorrect in flashify. I'm glad you got it working again though.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Me too man. Thx again for the help.
Same thing just happened to me. For me I would avoid Flashify. Not worth the hassle. JMO of course.
I used flashify to flash twrp
and now my phone wont boot at all doesnt respond at all
any help please
my model GT-I9300
azouzi.simohamed said:
and now my phone wont boot at all doesnt respond at all
any help please
my model GT-I9300
Click to expand...
Click to collapse
This is a forum for the VZW S3 not the international version of the S3
Sent from my Nexus 5
Hi everybody,
I have installed TWRP on my SM-P601 galaxy note 10.1 using odin on this link teamw.in/project/twrp2/206. It's succesfully installed but i couldn't get into recovery mod, i've tried all the button combinaisons but couldnt!
But i tried to get in using this app's com.koushikdutta.rommanager by clockworldmod, with the option (Reboot into Recovery) and now i'm stuck in a kind of bootloop when i turn it on, there is just the logo "samsung galaxy note 10.1 2014 edition".
Without the charger it stays on this until the battery runs out! and when i put the charger it runs and get stuck in the bootloop again. is there away to fix this wit
having to take off the battery? i can get in download mode !
Thank you a lot for your help
zakaria1193 said:
Hi everybody,
I have installed TWRP on my SM-P601 galaxy note 10.1 using odin on this link teamw.in/project/twrp2/206. It's succesfully installed but i couldn't get into recovery mod, i've tried all the button combinaisons but couldnt!
But i tried to get in using this app's com.koushikdutta.rommanager by clockworldmod, with the option (Reboot into Recovery) and now i'm stuck in a kind of bootloop when i turn it on, there is just the logo "samsung galaxy note 10.1 2014 edition".
Without the charger it stays on this until the battery runs out! and when i put the charger it runs and get stuck in the bootloop again. is there away to fix this wit
having to take off the battery? i can get in download mode !
Thank you a lot for your help
Click to expand...
Click to collapse
I have exactly the same problem now. I tried to update a kernel via TWRP and now boot loop. I can't even get into download mode, let alone recovery mode, just reboots automatically when hold the power button down.
mattdb said:
I have exactly the same problem now. I tried to update a kernel via TWRP and now boot loop. I can't even get into download mode, let alone recovery mode, just reboots automatically when hold the power button down.
Click to expand...
Click to collapse
I don't get into download mode at the first try i keep trying many times, maybe it's the same thing for you too. apparently i need to flash stock rom with odin on download mode, that's what you should do too if you get to download mode.
I have same problem...
Sent from my C6833 using Tapatalk
mattdb said:
I have exactly the same problem now. I tried to update a kernel via TWRP and now boot loop. I can't even get into download mode, let alone recovery mode, just reboots automatically when hold the power button down.
Click to expand...
Click to collapse
Noobie here, and not sure if I know enough to make much sense.
I had a similar situation occur today.
New to me but a 2nd hand p600 which rooted today and then I used Odin 3.10.6 to flash TWRP and found myself in a boot loop similar to the description.
I panicked bigtime and feverishly googled my way to to this message thread and my hopes were raised when I read the OPs message and then got dashed to find no solution posted .
After perhaps 20 attempts of getting combined button pushes and releases correct. (it never happened ) I was desperately trying almost anythiing and then got to TWRP File manager, then Reboot, then System, then Normal Reboot and finally Success! I got the regular reboot. Phew!
Hope it helps
Well, I let it sit over the weekend and the battery complete depleted. I was then able to get into TWRP and Download mode when I applied power, I have since flashed a new rom and whewwww, up and running again. Before the battery went dead, it wouldn't do anything but reboot.....
Before you read my problem plz note that i am only 16 and i have very little knowledge about anything related to rooting.
I rooted my phone a month ago because i wanted to use Xmod for Clash of Clans. I tried using Kingroot but it didnt work so i installed TWRP using Odin through my pc. After that i flashed SuperSU and the phone got rooted.
I didnt want xmod anymore so i decided to unroot my phone. I wanted to install the stock recovery and i read that i can do this by flashing the recovery.img file using Flashfy. So when i flashed it the app said that i need to reboot my device. So i pressed reboot and the screen went blank. But it didnt reboot. The screen that says Samsung Galaxy J7, which comes whenever i reboot or restart my phone, shows up but doesnt change. It also says "recovery is not seandroid enforcing" on top of the screen. It started coming when i installed TWRP. Nothing happened when i long pressed the power button. So i took out the battery, put it back and did 3 things:
1) Switching it on using the power button,
2) Directly going to recovery, and
3) Putting it for charging without switching it on.
The same screen comes everytime. PLEASE tell me what has gone wrong as soon as possible and if there is a way to fix this. Thanks a lot in advance.
XDA Visitor said:
Before you read my problem plz note that i am only 16 and i have very little knowledge about anything related to rooting.
I rooted my phone a month ago because i wanted to use Xmod for Clash of Clans. I tried using Kingroot but it didnt work so i installed TWRP using Odin through my pc. After that i flashed SuperSU and the phone got rooted.
I didnt want xmod anymore so i decided to unroot my phone. I wanted to install the stock recovery and i read that i can do this by flashing the recovery.img file using Flashfy. So when i flashed it the app said that i need to reboot my device. So i pressed reboot and the screen went blank. But it didnt reboot. The screen that says Samsung Galaxy J7, which comes whenever i reboot or restart my phone, shows up but doesnt change. It also says "recovery is not seandroid enforcing" on top of the screen. It started coming when i installed TWRP. Nothing happened when i long pressed the power button. So i took out the battery, put it back and did 3 things:
1) Switching it on using the power button,
2) Directly going to recovery, and
3) Putting it for charging without switching it on.
The same screen comes everytime. PLEASE tell me what has gone wrong as soon as possible and if there is a way to fix this. Thanks a lot in advance.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
There are no specific forums for your device on XDA.
However, if you create an XDA account, you can post your question here:
Android Q&A
You'll receive expert advice there.
Good luck and welcome to XDA!
Thanks for answering.
I have already asked the question on Q&A but there has been no reply. I will keep checking. Thanks again
Hey guys,
I flashed DARKLORD's S8 port yesterday evening. Everything was perfect. However, I noticed that the ROM was rooted with SuperSU system-less and thus didn't pass SafetyNet. I wanted to install Magisk in order to get Magisk Hide and pass SafetyNet. So I checked which kernel the ROM used. It was SuperStock 2.5.0.
I downloaded a clean, non-rooted SuperStock 2.5.0 kernel and flashed it through the recovery in order to get rid of SuperSU. The next reboot took really long. I went to bed after waiting for 30min, leaving the phone plugged in and on the Samsung boot logo with the typical blue notification LED that shines when the phone powers on. When I woke up the next morning, I noticed that the notification LED had turned off, but the Samsung logo was still there. I force rebooted the phone with the power-volumedown-homebutton combination. I noticed that it took quite long for the phone to turn back on again after the screen went black (10 seconds or so). I went into recovery and flashed DARKLORD's ROM again in order to get the original, working kernel back. Halfway through the flashing process the phone turned off and now it's dead.
I plugged it in for an hour, nothing. Not even the notification LED turns on when plugging it in. I can't get into download mode or recovery, I can't do anything.
Is my only option to send it to Samsung or is there any other way to get it to work again? Thank you in advance!
Kikill3r said:
Hey .... Thank you in advance!
Click to expand...
Click to collapse
Can you Boot into Download Mode or TWRP Recovery? If Recovery isn't working for you - Boot into Download Mode and use Odin to Flash the Stock Firmware - And extracted then Flash TWRP img.tar with Odin and go from there.
Edit: just re-read your post and you are certain that you can't get into Download Mode? Have you tried to only Press Power and Volume Down as well?
Sent from my SM-G930W8 using Tapatalk
shaggyskunk said:
Can you Boot into Download Mode or TWRP Recovery? If Recovery isn't working for you - Boot into Download Mode and use Odin to Flash the Stock Firmware - And extracted then Flash TWRP img.tar with Odin and go from there.
Edit: just re-read your post and you are certain that you can't get into Download Mode? Have you tried to only Press Power and Volume Down as well?
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
I tried everything. Nothing worked, it did nothing. As I said, not even the LED turned red when I plugged it in. In the end, I went to a Samsung support center and they replaced it. Apparently it was so broken that they couldn't even find out that it had Knox 0x1....
Kikill3r said:
I tried everything. Nothing worked, it did nothing. As I said, not even the LED turned red when I plugged it in. In the end, I went to a Samsung support center and they replaced it. Apparently it was so broken that they couldn't even find out that it had Knox 0x1....
Click to expand...
Click to collapse
Hmmm sounds like a plan :good: when something happens to knox 0x1 device hard brick it to still have warranty.