Related
I need help, When I turn on my Nexus the screen stays stuck on the Google start up screen. My phone is rooted with JellyBean. I have the Verizon version of the phone. I was also wondering how can I unroot my phone back to stock ICS?
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
biscuitownz said:
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
Click to expand...
Click to collapse
Thanks.
Right now I'm still stuck at the google start-up screen which still won't load up. I don't know if I messed up my phone.
I'm not really tech savvy with the entire flashing and fixing, but I'll help you best as I can.
You're not in trouble even if the phone hangs on the google logo upon a boot up. If you can hold the volume up and then the power, you should have access to bootloader. You can boot cwm to install stock rom, which I believe will remove root (superuser) and return to stock ics or jelly bean depending on which stock rom you install. If you've unlocked the phone (which I assume you did), you can lock it again by using the command "fastboot oem lock," which will lock the device back to factory settings.
I've basically surmised the linked thread above. If you're still confused, look at this thread here. Cheers!
biscuitownz said:
http://forum.xda-developers.com/showthread.php?t=1626895
Follow that to return to stock.
Click to expand...
Click to collapse
My phone is facing same problem, but with a twist and need help.
I did not unlock, root, or install any bootloader before, no CWM.
But my phone is now in bootloop, after a hang for unknown reasons.
I tried recovery, reboot, even fectory reset, but it just goes into a continous loop of google word logo, flashing trapezoids, and then a glitchy stop, then loop.
Sometimes it will just loop at the google word logo.
So I thought my original ROM must be damaged, and wanted to flash a new rom, hoping to fix things.
Problem is, I managed to unlock, but cant get through to rooting as whenever I try to root, it will attempt to run, but will end up saying :
FAILED <status read failed<too many links>>
Also i did not have USB debug before my phone went into bootloop. So now during rooting and attempts to install CWM, there is supposed to be a reboot and a change of USB debug setting required, which can't happen in my case as it couldn't even reboot to stock android.
So I am stuck with a bricked phone currently, when I didn't do anything in the first place...
details of my phone when in fastboot mode:
Product name - tuna
Variant - maguro
HW Version - 9
BOOTLOADER VERSION - PRIMEKK15
BASEBAND VERSION - I9250XXLA2
CARRIER INFO - NONE
SERIAL NUMBER - sorry not disclosed
SIGNING - production
Please let me know what i should do next... Hope to recover my phone
Thanks.
Make sure before you start, you have the correct drivers for your phone. Use this for your driver, and put the phone on bootloader. Make sure when you type fastboot devices, it shows the device. You can then unlock, boot cwm, flash either stock or other roms from there.
Let me start by saying I'm new to the Samsung world, I've had HTC android phones ever since the first Hero. That being said, I was able to update my phone to 5.1.1 and use the mostly stock OF7 kernel my phone booted up the first time, starting installing some apps, then decided to reboot it. Now it just goes into the boot screen that say Samsung and in red letters up top it says "Custom Binary blocked by FRP lock". Looking back I know I should have unlocked the bootloader when I had it booted up, but I forgot. Every time I try to flash a stock kernel in Odin, it pops up with the same message, but just says "Custom Binary (Boot) blocked by FRP lock". Is there any way to get my phone to boot up again, or will I have to wait until it's possible to download the 5.1.1 firmware? Even when that download is available will I be able to fix it?
Thanks in advance.
Are you able to flash TWRP in Odin? If you can at least get to TWRP you should be able to flash a custom ROM like Sacs23.
leatherneck6017 said:
Are you able to flash TWRP in Odin? If you can at least get to TWRP you should be able to flash a custom ROM like Sacs23.
Click to expand...
Click to collapse
Thanks for the suggestion, but I've tried flashing TWRP in Odin and it fails and says "Custom Binary (Recovery) blocked from FRP lock".
Bummer. Are you using Odin 3.10.6? If so, then I'm stumped.
leatherneck6017 said:
Bummer. Are you using Odin 3.10.6? If so, then I'm stumped.
Click to expand...
Click to collapse
Sure am, I just hope that flashing the firmware download will work when it's available. Otherwise I guess I'm screwed
How about Kies? Long shot I know...
leatherneck6017 said:
How about Kies? Long shot I know...
Click to expand...
Click to collapse
Just tried Kies and still nothing, this sucks I hate how I can't leave my phones stock
i faced the same !steps you need to follow settings>search>reactivation lock>log in into Samsung account and disable
bhavstech said:
i faced the same !steps you need to follow settings>search>reactivation lock>log in into Samsung account and disable
Click to expand...
Click to collapse
Yeah that would work and I should have done that before I restarted, but I forgot, and now I'm unable to get past the boot splash screen, and can' t access the stock recovery, pretty much the screen I can get to is the Download screen
bbacon said:
Let me start by saying I'm new to the Samsung world, I've had HTC android phones ever since the first Hero. That being said, I was able to update my phone to 5.1.1 and use the mostly stock OF7 kernel my phone booted up the first time, starting installing some apps, then decided to reboot it. Now it just goes into the boot screen that say Samsung and in red letters up top it says "Custom Binary blocked by FRP lock". Looking back I know I should have unlocked the bootloader when I had it booted up, but I forgot. Every time I try to flash a stock kernel in Odin, it pops up with the same message, but just says "Custom Binary (Boot) blocked by FRP lock". Is there any way to get my phone to boot up again, or will I have to wait until it's possible to download the 5.1.1 firmware? Even when that download is available will I be able to fix it?
Thanks in advance.
Click to expand...
Click to collapse
bbacon said:
Yeah that would work and I should have done that before I restarted, but I forgot, and now I'm unable to get past the boot splash screen, and can' t access the stock recovery, pretty much the screen I can get to is the Download screen
Click to expand...
Click to collapse
Did you try the new TAT file of the 5.1.1. It's posted now on here. I had the same thing but I had Asurion insurance and they sent me a new device for $200 deductible.
Mig1234 said:
Did you try the new TAT file of the 5.1.1. It's posted now on here. I had the same thing but I had Asurion insurance and they sent me a new device for $200 deductible.
Click to expand...
Click to collapse
Yup I downloaded the firmware and flashed through ODIN and its all up and running great now. Thanks for the help
bbacon said:
Yup I downloaded the firmware and flashed through ODIN and its all up and running great now. Thanks for the help
Click to expand...
Click to collapse
sorry for the bother but am a bit new to all this. am faced with exactly the same problem. What TAT file are u guys talking about and where can i download it.
Saafir said:
They mean TAR and you can find it here as well as various other threads here on sammobile.com
Click to expand...
Click to collapse
Thanks for the clarification
i have the same problem too, frp lock. i cant do anything, stuck in logo
butterfan214 said:
i have the same problem too, frp lock. i cant do anything, stuck in logo
Click to expand...
Click to collapse
Which version were u on, 5.1 or 5.0
My sm-920T t-mobile Galaxy s6 is now stuck in a boot loop on splash screen
I flashed the new note 5 kernel and firmware that just came out to it and everything was working fine until I restarted my phone and now I'm stuck in just the Samsung Galaxy s6 boot screen can't access anything but download mode do any of you have any useful info or files I may be able to flash through odin to get through this because my phone is now essentially now a locked down brick that was working awesome right before I restarted it for the first time I forget the devs. name who put out the kernel and firmware for the note 5 to work on the s6 but this damned frp block/lock has made my fully paid for s6 I just got a doorstop now and I'm so frustrated anything I'm trying to flash on odin AP. is failing and I'm just so angry. Can someone please swoop in and give me some possibly useful advice so I can get my phone to boot because it was fine..... Till the restart because just one program was f/c but I would've eventually restarted anyway so I guess once I flashed it I was doomed. DEVS PLEASE. I know someone in here has to have had the same problem and conquered it. I've tried everything in my limited repertoire. Thanks alot for any responses. I was on normal 5.1.1 s6 firmware previous was just rooted with custom recovery
Getting the same frp error. Everthing I flash through ODIN fails. Even flashing stock 5.1.1 OF7 fails. I believe it's because I was on OGA so I have to wait until the tarball for that comes out I guess. Unless anyone else has some ideas?
Try using ODIN to reload the bootloader. Google the how, there are many posts.
Hope it helps. That's what I did to get mine to work.
same-ish stuffs
So I have a new s6 on a sprint plan. Was stuck in like a boot loop with the same message in nice red letters kept coming up on the load screen. I was on OGA and had just tried to implement TWRP via the playstore. This started the boot loop. after reflashing the original rootof7.tar i had managed to get it break-free with a factory reset on TWRP(which was now working), only to have the battery die before I had a chance to do anything. after I had got it on a charger it started with the charge battery icon and the red FRP lock message. It would basically just loop there going no further unless i tried to full reset(all buttons) or download mode. Could not flash anything via odin (only recieved error messeges). Took to Bestbuy and after some shuffling around(geeksquad is terribad) I managed to get the Samsung guy to flash a stock OF7 and it works fine now. No more root or twrp and the knox reads 0x1, bu the phone is working now
tupac unincorn said:
So I have a new s6 on a sprint plan. Was stuck in like a boot loop with the same message in nice red letters kept coming up on the load screen. I was on OGA and had just tried to implement TWRP via the playstore. This started the boot loop. after reflashing the original rootof7.tar i had managed to get it break-free with a factory reset on TWRP(which was now working), only to have the battery die before I had a chance to do anything. after I had got it on a charger it started with the charge battery icon and the red FRP lock message. It would basically just loop there going no further unless i tried to full reset(all buttons) or download mode. Could not flash anything via odin (only recieved error messeges). Took to Bestbuy and after some shuffling around(geeksquad is terribad) I managed to get the Samsung guy to flash a stock OF7 and it works fine now. No more root or twrp and the knox reads 0x1, bu the phone is working now
Click to expand...
Click to collapse
can you tell me which stock rom did you use please.
My friend's J2 Prime (SM-G532G/DS) happened to be stucked at Security Error (blue screen), no idea how it get there. Tried to flash stock firmware. But after flashing, the phone booted back into the same blue screen, now with a line of red text at the top saying, "Custom binary blocked by FRP. (recovery. img)". Tried many different stock firmware (with 4 files) but none of them solved the problem. Can't boot into recovery, only download mode. Can someone give me detailed step by step on how to fixed this.
If it help, I'm from Malaysia. So maybe the firmware might need to be from this region. Not sure about the origin of the phone though. Also, what could be the reason for this to happen? I'm assuming root. Could it even happen on its own, I mean without rooting or flashing?
also G532G/DS - ARH1 bootloader
i've been going thru lots of ROMs (including testing Lineages), this have never happened to me before.
Flashing stock firmware thru Odin though, require OEM Unlocking ON in Developer Settings.
^ I mean, did you/your friend turn it on before flashing? if not, it actually succeeded?
Only solution might be possible:
Go to stock recovery (POWER + HOME + VOL-UP), wait for it to load, then factory reset from there.
I suppose some images might help!
I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...
JEDAlive said:
I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...
Click to expand...
Click to collapse
+ OEM Unlock: if disabled, Odin should've failed straight away and no reboot stuff going.
+ Can't get into recovery:
Is it true that you cannot get into recovery? If left stock, It should be an Android with spinning stuff, text is "installing update" then no command for a while ~2min, and it will go to normal recovery.
I mean, it is supposed to do "recovery" :v
+ Images: post it on Imgur (or any online image service). Copy link here, add space between "https://" and all the stuff there. Wont be considered URL i guess (havent tried)
Hi,
I'm stuck on 'samsung' logo screen after flashing stock rom. Please see details below if you can assist.
1. I have sm-505fn from carphone warehouse uk with jan/feb 2020 update..
2. I did oem unlock and flashed twrp
3. this gave bootloader warnings, but eventually went into twrp.
4. I didn't do the dm verify installation and after couldn't get into twrp again. (not sure how to sideload this at this stage)
because i didn't do above step and rebooted, i think i tripped the knox and SG/RMM state became 'prenormal'.
kept getting error: "Only official released binaries are allowed to be flashed" if i tried installing twrp again.
5. tried installing stock rom btu for march 2019, but odin gave errors as couldn't install older stock.
6. then installed feb 2020 stock from sammobile rom A505FNXXS4ATB1 which is the btu version.
7. above worked fine with odin and everything succeeded.
8. On reboot the first warning vanished, and I only got the 2nd bootloader warning. phone went through a 5 second update screen, then rebooted.
9. then got samsung a50 logo and system started booting with plain samsung logo.
10. been stuck at plain samsung logo for 40 min. tried restarting but same problem.
Can you please advise what i should do?
Can't believe its such a headache to install twrp this device (and then later remove the bl warnings
Thanks
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
as it still gave the bootlocker warning, i turned oem lock on again via long press up on download mode. this fixed all warnings and i can boot now without warnings.
when i go into developer mode now, there is no option to oem unlock again.
if i go into download mode, there is no option to long press up and unlock again
on download mode it says:
KG State: prenormal
OEM Lock: ON (U1)
how can I turn oem lock off again, so I can try to install twrp?
Please assist.
thanks
SOLVED -
managed to turn oem unlock option again by turning off auto time update and setting clock back 10 days.
then on restart, the option appeared again and was set to oem unlock ticked.
went into download mode and i could see option again to unlock booloader.
long pressed up and it unlocked bootloader, erased data and restarted to system....
now... lets try to install twrp again and hope it doesn't give me 'unofficial binary' error due to SG prenormal state.
lol.. its KG STATE not SG fyi
Typo
lawmanukdc said:
Typo
Click to expand...
Click to collapse
lol id believe that in 1 comment but everywhere? oh well no biggie lol.. hope ur enjoyin ur phone now
How did you succeed to get the stock reinstalled ? Was it different version ?
lawmanukdc said:
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
Click to expand...
Click to collapse
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Try to flash latest rom
Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk