I realize this has been mentioned before but, I couldn't find a solid answer specific to my problem.
As it currently stands, my Note 5 bootloops or so it seems with the SEANDROID and FRP Binary errors appearing with the Note 5 logo, and fade to black. Rinse, repeat.
I'll back up a little bit, my friend got me a Note 5 on his plan with Bell last November. After just 30 days he was fed up with the service and went to epic ends to cancel and return both his phone and mine, of course this didn't work. So, after a litany of calls and driving to different stores for various credits. He effectively was left with our phones and a bill total of around $800 after everything said and done. Somewhere in this mix though Bell, decided or someone he was laying into to blacklist both his phone and my beloved Note 5.
I was using the phone for work at the time and suddenly it didn't work!? So he told me his wasn't working either and alas we set off to figure out some circumvention around this, which ended up with some nerdy guy in a Tim Horton's changing the IMEI's of my Note 5, which had it's own issues itself.
First we had to root the phone, then he used an octoplus box to unlock it and pop another IMEI in there. I remember after the rooting portion though he had me remove my fingerprint, my google account and my samsung account. This was back in mid December. I, yesterday after all this time finally began to re-add my accounts. I added my google account and fell asleep after a old friend stopped by and smoked me up on a spliff which I haven't touched in years. For obvious reasons, I passed out to wake up to my phone dead, so I plug it in and BOOM I have the above errors popping up above my logo. For note though, the one error "SEANDROID" was present after the IMEI change. Now, I'm just bootlooping. I did read that I can flash a different kernel or another ROM, my biggest issue is I have client's files stored on my phone along with a bunch of sexy pictures of my girlfriend
So, I ask my fellow XDAer's what steps can I take to remedy this without losing my internal storage.
A happy footnote more to those that may think I'm a wily thief or some petty criminal looking to break a code or do something illegal with the phone. I am not and in an ironic twist my friend the account holder actually got both phones off the blacklist after yet another tear into Bell. Doesn't help me now but, it does show that had I waited I wouldn't have been in this predicament or even had a reason to go onto Kijiji and find a seedy IMEI guy.
Thanks anyone for reading this entirely too long post and I appreciate any help!
More info:
Galaxy Note 5
Bell - Unlocked
Android 5.1.1 - I never updated it if that helps.
Just flash stock rom on it. It happens when someones tried to root it without turning oem unlock on
---------- Post added at 07:07 PM ---------- Previous post was at 07:06 PM ----------
It wont touch your data partition.
Recently I got caught in a downpour and my phone was in my pocket. My work email requires security restrictions that wipe the phone after 6 failed unlock attempts. The water caused the phone to think it was trying to be unlocked which then initiated the wipe. During that, the phone then shutoff completely mid wipe. Now, the phone turns on but more often then not there is no display. I can tell it's booting because it will disconnect and reconnect to odin, and I can flash stock firmware but there is no display. What I don't understand is, randomly the screen comes back. But as soon as the device is turned off, it won't come back.
The phone is disassembled and I have access to the battery if needed.
Primary question: Is there anything firmware related that can cause the display not to function at all or is it more likely a hardware issue?
Any tips or suggestions?
I also hv almost same problem with galaxy s6. But in mine case it just don't display anything for some hour. After that it works like charm. During weakend when i'm home there is no problem but elese when i'm at work problem happens.
---------- Post added at 10:19 AM ---------- Previous post was at 10:18 AM ----------
Your case looks to me water damage.. some components on Morherboard are fride or something like that.
Hi,
This morning my idol 4s 6070O -up to date MM from alcatel- suddenly rebooted and since then its keeping on rebooting showing the alcatel logo then idol 4s logo and sometimes the blue alcatel animation and sometimes not.
i went to master / Hard reset from recovery menu by pressing power key along with the volume up key and then wiped both cache partition and wiped data / format system
Also, tried the SUGAR QCT tool But after more than once, all in vain
still looping and never startup the launcher.
The rebooting does only happen when trying to start the launcher but never during using recovery menu. So, this is probably is NOT a battery problem but instead it is a software issues.
Would you recommend any sequence to fix my firmware to help?
Any suggestions would be highly appreciated.
Kindly advise
Thank you
Same problem twice with two Alcatel idol 4s since november 2016... They send me a new one in february but the problem just got back And this time even the hard reset doesn't boot...
still no solution to this problem ??
---------- Post added at 12:32 AM ---------- Previous post was at 12:27 AM ----------
my phone shuts down suddenly and goes bootloop but when in recovery mode it doesn't
and when i plug the charger it also works well
any advise ?
Abdel Kayoum said:
still no solution to this problem ??
Click to expand...
Click to collapse
No solution so far ya abdo.
You need to send it back where you have purchased it to get a replacement, cuz akeed you have not buy it from egypt.
Seems a problem with the motherboard so you get a new device, at least i did so
Alcatel idole 4s android model bricked
My friend from Portugal gave me one Alcatel idol4s, now it stuck on android logo. It can only enter into download mode. Is there any Qfil rom for this one? to use qpst or xiaomi flash tool need qfil rom... please help
I realize this is a bit old of a thread but I found a youtube video with a guy that had the exact same problem. He shipped it back to Alcatel's reparation service since it was still within the warranty and they said it was a motherboard issue. If it is the same thing it'll be very difficult to fix yourself so it would be best to see if your phone is still within the one year warranty period.
Boot loop of evil!
I Have the exact same problem, and came here to see if someone had it fixed.
Can anyone help us fix this brick of metal and glass?
ZeFMendes said:
I Have the exact same problem, and came here to see if someone had it fixed.
Can anyone help us fix this brick of metal and glass?
Click to expand...
Click to collapse
I fix it! This is so easy to repair. This morning I had same Bootloop issue with my Idol 4S its keeping on rebooting showing the alcatel logo only. To repair this issue we must get straight to the Recovery and select Wipe Cache option then reboot the phone.
To open Recovery you must feel the moment when the phone restarting by Power On/Offbutton and not automatically (Note: by pressing this combo your phone sometimes load the logo one second later...) When you feel the moment then fast release both buttons (Power & Volume Up) and if you're done it right you will see Recovery Menu.
That's it.
I've found in my line of work that the battery can cause this issue. I've fixed two Idol 4S' by changing the battery. The battery voltage should be 3.7/3.8v, whereas I've recorded 4.2v on an idle battery not being charged.
Same issues
Do you think it's worth it if the battery is not the problem, then you've spent 65 bucks or more, for new battery in a broken phone.
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
B1G7r33! said:
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
Click to expand...
Click to collapse
What's the REAL difference between what you did today and what we did days ago.? Is the same thing we came up with 3 days ago.. Just your version of the same thing..
Three days ago?
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
B1G7r33! said:
Three days ago?
Click to expand...
Click to collapse
actually starting on 14th November 2018, 07:17 PM and ending about 4 days ago.. with ptballers solution.
post 118 was the beginnings of it on the thread: https://forum.xda-developers.com/ga...10-02-2018-t3747564/post78159074#post78159074
but even THAT came from earlier works that weren't detailed enough and reconstructed.
the builds seem to be way different here in the solution, i had luck with what we came up with but have only done that once so far.
I am using build NMF26X.T380DXU1ARB3 myself, what about you?
we need to figure out what ptballer is using and everyone else too as we confirm stuff so we know what to do with tablets based upon builds.
seems there is no single solution yet, and that's what we really need too keep confusion cut down to a minimum.
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
Evul1 said:
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
Click to expand...
Click to collapse
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
capriorn1971ad said:
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Click to expand...
Click to collapse
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Evul1 said:
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Click to expand...
Click to collapse
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
B1G7r33! said:
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
Click to expand...
Click to collapse
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
capriorn1971ad said:
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
Click to expand...
Click to collapse
It shouldn't be that much work at all if your method to get OEM Unlock to display actually works, as your bootloader will then be unlocked and you can immediately re-root, re-flash TWRP, and restore a nandroid backup. Rooting this tablet [flashing TWRP and su and/or magisk and/or a nandroid image] is actually quite simple and can be done in 5 minutes once you have OEM Unlock displayed.
You certainly wouldn't need a whole day just to try this. But I understand. Samsung's security nonsense makes the initial root of this tablet rather fragile if you don't know all the potential roadblocks beforehand. And a comprehensive root guide that explains all of this would certainly help people looking to root this tablet, so I don't want to rush you.
capriorn1971ad said:
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
Click to expand...
Click to collapse
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
B1G7r33! said:
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
Click to expand...
Click to collapse
don't think we can really.
trial and error..
thought i was on the right path earlier, but if it didn't work for you then it isn't the solution, cause the solution will work for everyone.
has to be some small thing were overlooking i would assume.
I worked for Metricom through Verso Technologies back in the late 90's, the first coast to coast wireless provider, had dealings with the big wigs and all, but they always opted for less security and more accessibility in most everything pertaining to networking, always afraid to give up backdoors.
i need to go back to what you said too and see what slight differences there are, did you have any luck this time around? was it repeatable?
sucks to know i am going to have to root to cause a failure to try to bypass and root again only to cause a second failure to verify, and to get it right it is going to take that really, the bypass has to be repeatable, i think setting the date back before the systems restore is key to it, but i could be wrong.
if you would lose root and be able to get it pass the first 7 days OEM unlock then your good, because even if you can't get the second, and something goes wrong to where you need it, your gonna have to wipe anyways, which means you just wipe, set date back and then do the factory reset, not being able to reboot afterwards until the OEM unlock appears and not being able to advance it through the last 7 days means little so long as the root is good and right, funny thing really, took me a while to realize that, there is no real need to rush the second 7 days, only the first 7, but it would be nice to be able to reboot it again afterwards, the same day, and not have to worry about it anymore, but like i said earlier, i got detected somehow and lost root still., wish i knew how.
that's alot of my problem though, i do things and try to document them afterwards rather than as, and i am not 20 years old anymore with a mind like a razor, it's just a serrated steak knife now at almost 50, wish i wasn't like that, because i lose bits and pieces as i go.
so if my tablet auto updates to Oreo 8.1 ... then i'm SOL huh?
Hello, I have a Note 8 that I have previously rooted a few months ago, then came back to stock OS. I have been wanting to install a custom rom now, but the OEM unlock switch is not in settings despite waiting a week. I rebooted into download mode, and there it shows OEM lock: off, along with RMM: Normal. I attempted to install TWRP to it, but it gets blocked with "Custom binary blocked due to remaining installment payment". I've also noticed that there is a entry in about phone > status that shows "Installment payments: Outstanding". Does that mean I have to pay off my phone fully, or pay the current balance on the carrier account? Does CRHA have the same issue? Or is there a workaround that I don't know off?
Edusa said:
Hello, I have a Note 8 that I have previously rooted a few months ago, then came back to stock OS. I have been wanting to install a custom rom now, but the OEM unlock switch is not in settings despite waiting a week. I rebooted into download mode, and there it shows OEM lock: off, along with RMM: Normal. I attempted to install TWRP to it, but it gets blocked with "Custom binary blocked due to remaining installment payment". I've also noticed that there is a entry in about phone > status that shows "Installment payments: Outstanding". Does that mean I have to pay off my phone fully, or pay the current balance on the carrier account? Does CRHA have the same issue? Or is there a workaround that I don't know off?
Click to expand...
Click to collapse
Not familiar with this message, but just based on the wording alone it sounds like your carrier blocked it until it's paid off. Maybe part of an update somewhere along the way? I would probably phone them for more info and then go from there.
sefrcoko said:
Sounds like your carrier blocked it until it's paid off. Maybe part of an update somewhere along the way? Suggest phoning them for more info.
Click to expand...
Click to collapse
It was only happening in the recent updates when the installment payment showed up in settings, but I doubt the customer service will even know what a bootloader is. Otherwise I would have to wait 2 more years to be able to unlock it, and by then I'll probably have a Note 11 or whatever is out by then. Did the CRHA firmware have that feature?
Edusa said:
It was only happening in the recent updates when the installment payment showed up in settings, but I doubt the customer service will even know what a bootloader is. Otherwise I would have to wait 2 more years to be able to unlock it, and by then I'll probably have a Note 11 or whatever is out by then. Did the CRHA firmware have that feature?
Click to expand...
Click to collapse
Hmm I googled the error message and found a bunch of sites and posts describing the issue. Seems like it's actually another message related to RMM state, which would also explain why you don't see the OEM unlock toggle at the moment. I never had this particular message before, but if I did my next step would likely be trying a factory reset and reflashing latest original stock firmware for the device and seeing if OEM toggle appears in 7 days (or using the date-change trick to speed it up, if that still works). Maybe someone else has other suggestions too.
sefrcoko said:
Hmm I googled the error message and found a bunch of sites and posts describing the issue. Seems like it's actually another message related to RMM state, which would also explain why you don't see the OEM unlock toggle at the moment. I never had this particular message before, but if I did my next step would likely be trying a factory reset and reflashing latest original stock firmware for the device and seeing if OEM toggle appears in 7 days (or using the date-change trick to speed it up, if that still works). Maybe someone else has other suggestions too.
Click to expand...
Click to collapse
I'll try it during the weekend then. Odd that it happens even with a unlocked CSC (BTU)
Same problem
Bought my phone off of Swappa, which they claimed was good.
To date - I have installed 2 different factory firmwares to no avail. Have the same message and same status. Get stuck on Factory Binary screen trying to run combination ROM.
Bought this phone specifically to root and use on AT&T. Glad I paid little more than 1/2 of new...and tried calling Samsung support but they are of no help!
Definitely looking forward to any suggestions on what to do, to help determine what the problem is.
Thanks in advance, as well.
---------- Post added at 09:39 PM ---------- Previous post was at 09:35 PM ----------
sefrcoko said:
Hmm I googled the error message and found a bunch of sites and posts describing the issue. Seems like it's actually another message related to RMM state, which would also explain why you don't see the OEM unlock toggle at the moment. I never had this particular message before, but if I did my next step would likely be trying a factory reset and reflashing latest original stock firmware for the device and seeing if OEM toggle appears in 7 days (or using the date-change trick to speed it up, if that still works). Maybe someone else has other suggestions too.
Click to expand...
Click to collapse
The RMM state is listed as off, not prenormal, which is what I am guessing you are referring to.
Flashing latest firmware takes this to V4 bootloader which may/may not be something OP is interested in.
Might be a bit of a bump
On the Android Pie betas for the Note8, the OEM unlock button shows, and it toggles as expected, and the installment balance entry also does not show anymore in settings. However, it still won't let me flash TWRP or any binary, showing the exact same message as above. Has a fix been found for this issue, or am I stuck unrooted? Could the S10 have the same issue?