Every now and then I see around the edge of my phone a red border flashes, I looked it up and it said it had something to do with strict mode in developer settings. I went in and strict mode was not checked, I tried Turing it on and leaving it on for a minute or so and turned it back off, it is still doing it. Any suggestions? Model: xt1644 Android version: 6.0.1 ROM: Dirty Unicorns DU version: Dirty-deeds-v10.6
Hmm, you have probably flashed an -eng build on your device. Use a -userdebug build.
Related
Hi Everyone,
I am going straight to the point:
- Rogers Galaxy S4 (I337m)
- when purchased couple of months ago, it was on factory firmware - I337MVLUAMDJ
- I decided to read about the running i9505 roms as per posting here - http://forum.xda-developers.com/showthread.php?t=2295557 - I am not a newbie to any rooting & tools used - e.g. ODIN, TWRP, CF-AUTOROOT, etc. etc. I started with the CF-AUTOROOT and all went well.
- it had the latest TWRP installed via ODIN - openrecovery-twrp-2.6.3.0-jfltecan.tar - as per: http://techerrata.com/browse/twrp2/jflteca
- last night, the phone was perfectly running Omega v12 Jelly Bean 4.2.2 (Based on firmware ZHUDMI1 Android 4.2.2 (Date: 12/09/2013)),
- it was running with Kernal from: http://forum.xda-developers.com/showthread.php?t=2289140 (Ktoonsez Touchwiz JELLYBEAN 4.2.2 VERSION)
- everything was working perfectly - WiFi, Data, Calls, etc.
- overnight the phone's battery drained , and when I went to charge it and boot it this morning - it was stuck on the Samsung Galaxy S4 logo - weird right?
- so I tried the following:
- tried to boot into TWRP - no luck
- the phone does boot in Download Mode , which is great
- because the phone boots into Download Mode, I downloaded the factory (non-rooted) ROM - I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar
- MD5 was verified and ODIN completed without any issues
- The phone is still stuck in Samsung Galaxy S4 logo screen, it doesn't go anywhere else?
- What to do? Please help?
P.S. When ODIN is finished, it reboots and initially it loads the factory recovery and you see the android with the gearbox circling (lol), and then you see under the android image a blue bar - going across (indicating something was completed) and it reboots - at this point, it gets stuck on Samsung Galaxy S4 logo screen.
Also, when it is in download mode: it says the following -
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: Enable
Please help, & thanks in advance!
I have the same problem recently. I flashed through Odin. It says passed, but still the bootloop and not able to get into recovery.
You should try Kies firmware emergency recovery, or firmware update. It worked for me. Weird.
Did you do a factory reset in recovery after Odin?
Figured It Out...
Hi Guys!
This is going to sound funny and weird, but the problem is ... overheat/overload battery issue!
I realized the USB cable that comes with S4 accidently had a splice on the cable (I believe it could be because of my near-sharp corners around my desk, whereby, my cable makes contact). For whatever reason, when I charge using this faulty cable, the battery gets very hot and the battery percentage fluctuates. (was at 60% then drops to 20% then goes to 40% ... all within few minutes of each other...weird)
I am sure the battery itself has a circuit board, I was thinking it could have been damaged.
Anyways, I threw that spliced cable in the garbage and replaced with another OEM USB cable and the phone started to work fine.
Also note, I was reading another thread about someone flashing the wrong ROM, and they kept the battery separate from the phone for approx. 5 mins - 10 mins, and it resolved the issue.
So, basically that's what I did, keep the battery separate from the phone for that long and it worked.
But I will definitely change the battery with a fresh new OEM, I am not going to take any chances.
Thanks again all for your ideas. I am sure I would have resorted to that if this didn't work.
Hello.
I have an S5 SM-g900m from claro DR.
This phone was working perfectly until it got messed up by its own.
The phone was turned on and working, i went to check the time but the screen wouldn't turn on.
removed the battery put it back inside and tried to turn it on. I got samsung logo after a few seconds it vibrates shows a thin line and reboots, samsung logo again. it's stuck on that.
tried to reboot into recovery mode and it wouldn't let me. i get the same problem. reboots. I can get to download mode.
Problem #2:
Most of the time, the screen wont turn on. when it doesn't turn on the phone boots normally. from what i guess i can get into recovery mode. I have confirmed that i can get into download when the screen doesn't turn on.
Things that i've tried:
Flash the stock firmware: 5.0
Flash stock firmware for the same model but other region: 6.0.1. With screen turned on, it wont boot. with screen off it boots normally.
Downgrading: no luck.
Don't know whats wrong or what to do.
Hello,
So i was using my phone in a very normal usage, i dont recall installing any third party app or anything on that night. I last used my phone at arround 3am on Tuesday, woken up at about 5am and found it completely black with the blue led lighting up. It didnt respond to any kind of buttons combinations, it stayed like that until the battery was dead. For now I tried EVERYTHING, from flashing custom roms to downgrading or upgrading stock roms from sammobile. While flashing a rom, the phone reboots then gets stuck in erasing screen, forcing a reboot will make it return to its previous status only..
I have to signal here that i have frp lock OFF , and i guess that it is the main issue here is that the automatic update to oreo failed, i tried the solutions given on this tread : https://www.google.com/url?hl=fr&q=...870000&usg=AFQjCNEcdRjZySPCbnAulqAEIQDrHLWGRQ, but my phone wont reconnect after flashing the boot file, just gets stuck on the s7 edge screen again.
I have the exynos variant of the model and I live in Morocco !
UPDATE :
When i get to flash with a stock rom using odin , without the auto reboot option, i get the green pass and when I restart the phone manually it reboots normally and gets stuck on the samsung logo then reboots again to a black screen and the blue led again just like it was before the flash .... please help
Hi
I am stuck with Pulsing blue LED and the "Powered by Android" screen,
have access to both the recovery and the download Mode,
I also have Odin (version 3.13) on my computer along with TWRP (3.1.1 trlte and 3.2.1 version)
My device is a Samsung Galaxy Note 4 N910F bought in shop, no special carrier. It was bought in the Netherlands.
I have tried everything that I have read. The furthest that I can go is the Second Samsung Logo with the Flashing Light
Whenever I try to Flash the stock Firmware for my N910F, everything goes well in Odin but then when the phone reboots, it (sometimes) install the system update until 30% then shows erasing then either crashes right there and then or load the system update bar, completes it then shuts down.
I have tried multiple firmwares, even recovery firmwares. All the same problem. I can see the firmware is flashed, because when I enter recovery mode after I flashed a different ROM, it shows the version I flashed.
I cannot seem to install TWRP because it was never rooted.
Whatever I do, at some point, my phone either gets stuck in a bootloop, freezes with the LED light or shuts down.
And I have also proceeded to use different batteries.
Do you have any options?
Thank you
Heat????
I'm far from an expert here, but I've just experienced a similar problem where my N910F started boot looping / freezing within 15s to 2 min after unlocking. Unfortunately my micro Sd (SanDisk 256GB) was corrupted a week ago, so before doing anything else I did some research (XDA/YouTube) and probably found pretty much what you've found. I frequently change batteries so I could discount that as an issue. Someone suggested using the Samsung Smart switch here https://www.samsung.com/uk/getting-started/smart-switch/, but I haven't used it (yet) so I can't tell. I presume you had the latest firmware from Sams https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/.
My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilà! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1.
Good luck and hope this may be of some help.
I've got this problem, too, when using the unofficial Lineage 15.1 rom. SIM death and boot loop. After flashing the latest stock rom through odin, it passed but the screen was black and no system was installed. The blue notification light was constantly stuttering, though. And I couldn't even go to recovery!
When flashing, a 910F can get hot - use a cool temperature room and/or a fan blowing onto the device.
If it's not too late...
I ran CRDroid 7.x on this phone for a while and got quite used to having a charger connect / disconnect vibration (and sound) which lets me know i accidently pulled out the cable or didn't put it in all the way.
Now, I had some issues with CRDroid and some apps not playing nice plus my auto brightness was flickering very bad so I decided to just go back to stock for the time being.
So, I MSMTool / Unbricktool / EDL installed the EU 11.0.3.3 ROM, updated it to 11.0.4.4 through OTA, OEM Unlock again, rooted it with Blu_Spark R87 kernel (which I used on CRDroid as well, it supports both custom and OOS) and set everything up again. However, I noticed that in the settings for sound and vibration and also battery settings I cannot find a single option allowing me to turn on the charger notifications.. Does that not exist in OOS or something?