hlw please anyone help me i have frp lock in my sma800f it wont boot up and says custom binary blocked by frp lock and i cannot flash kernels through odin also .will i be able to flash official firmware through odin or not ?
THANK IN ADVANCE
You would be able to flash the stock rom from odin and then every thing will be fine....
Download stock rom and flash it by using odin.
Moved
skippedreality said:
hlw please anyone help me i have frp lock in my sma800f it wont boot up and says custom binary blocked by frp lock and i cannot flash kernels through odin also .will i be able to flash official firmware through odin or not ?
THANK IN ADVANCE
Click to expand...
Click to collapse
Hello,r u able to flash stock firmware with odin, since frp blocked?
Proton Pig said:
After it boots up, go to settings -> Developer -> OEM unlock and tap it to disable OEM
Click to expand...
Click to collapse
Enable
Proton Pig said:
OEM is what we want to DISABLE, since it has stuff like FRP, which is the problem here.
Click to expand...
Click to collapse
ENABLE.
It's called OEM *UNLOCK*
http://www.androidexplained.com/how-to-enable-oem-unlock/
Please try OEM unlock and frp bypass which is described in the two links below;
http://www.samsungsfour.com/tutoria...ock-on-samsung-galaxy-android-smartphone.html
http://www.samsungsfour.com/tutorials/how-to-perform-oem-unlocking-on-samsung-galaxy-smartphone.html
Hope this helps.
Related
Friends please be careful about OEM lock in an unlocked bootloader.
Since lollipop , google introduced an option in developer menu
'Allow OEM unlock'
It allows fastboot unlock.
Also it prevent unlock while it disable.
The problem is we can't unlock second time after OEM lock.
It makes device bootloop.
My advice is
Don't lock bootloader after unlock.
Don't lock bootloader if your device rooted and/or custom recovery installed.
My phone is in service centre now
samysimbu said:
Friends please be careful about OEM lock in an unlocked bootloader.
Since lollipop , google introduced an option in developer menu
'Allow OEM unlock'
It allows fastboot unlock.
Also it prevent unlock while it disable.
The problem is we can't unlock second time after OEM lock.
It makes device bootloop.
My advice is
Don't lock bootloader after unlock.
Don't lock bootloader if your device rooted and/or custom recovery installed.
My phone is in service centre now
Click to expand...
Click to collapse
So Bad Dear to hear, that your Device now in Service Center
can anyone please give me the stock recovery file of lava pixel v1
sayan123 said:
can anyone please give me the stock recovery file of lava pixel v1
Click to expand...
Click to collapse
Download stock rom from this link
http://firmwarefile.com/lava-pixel-v1
U have to flash STOCK ROM immediately after u relock Oem
Plz Help.........!!!
samysimbu said:
Friends please be careful about OEM lock in an unlocked bootloader.
Since lollipop , google introduced an option in developer menu
'Allow OEM unlock'
It allows fastboot unlock.
Also it prevent unlock while it disable.
The problem is we can't unlock second time after OEM lock.
It makes device bootloop.
My advice is
Don't lock bootloader after unlock.
Don't lock bootloader if your device rooted and/or custom recovery installed.
My phone is in service centre now
Click to expand...
Click to collapse
I was trying to root my phone so i unlock the oem in setting but i typed fastboot unlock bootloader in cmd promt while installing TWRP because it was not taking this but now its stucked in a bootloop showing TEAMWIN logo and flashing in couple of seconds....... plz help me what to do....
.
.
and what happen to your device in service center plz tell me in detail......
i need help i cant use odin cuz OEM not unlock and formating not changing anything
Flash a March security patch firmware and after try to flas engineering bootloader for it and your phone will boot.
Regards
mariolcela said:
Flash a March security patch firmware and after try to flas engineering bootloader for it and your phone will boot.
Regards
Click to expand...
Click to collapse
thnx man odin keeps getting stuck in initialization too i just changed my usb to the other one and odin works now
Were can i find this engineering bootloader?
d0ct0ru said:
Were can i find this engineering bootloader?
Click to expand...
Click to collapse
A quick search with your specific model number would help you.
Just search for engineering bootloader (your model number)
I have twrp installed but i just typed fastboot oem lock now my bootloader is locked but i m on twrp how can i unlock bootloader.... since i m blocked from asus fota server so i cant unlock by signed unlock tool..... plz help me i think i need the oem unlock code...... or if any one can provide me the same models oem unlocked image file and i may flash that to unlock boot loader.... plz help guys.....
And does any of the auto root tool works for asus zenfone max android 6
Please reply to this post, someone
same problem here , have you found the solution?
I too have the same problem. I even bricked my phone dong os, ended up flashing using flash tool. Now, the bootloader is locked and unlock tool is not working. Someone help
[email protected] said:
I have twrp installed but i just typed fastboot oem lock now my bootloader is locked but i m on twrp how can i unlock bootloader.... since i m blocked from asus fota server so i cant unlock by signed unlock tool..... plz help me i think i need the oem unlock code...... or if any one can provide me the same models oem unlocked image file and i may flash that to unlock boot loader.... plz help guys.....
And does any of the auto root tool works for asus zenfone max android 6
Click to expand...
Click to collapse
use Fastboot oem unlock command via csc/fastboot mode
debadri1995 said:
use Fastboot oem unlock command via csc/fastboot mode
Click to expand...
Click to collapse
ot doesnt work bro.... it says command fails..... i want a way to know what is the default code for oem unlock of my device
Me too same case. Someone please help. The unlock tool does not help either. Please help.
Someone please help us, we are so helpless
i hv a same prob too.... someone help please...
volte lost and bootloader locked
Hey everyone, i recently flashed the cleanmax rom and i lost my volte for ever.
So after this incident, i thought i must flash the stock rom using fastboot. :it didnot work:
so i deep flash the rom using edl mode and guess what i lost the imei,serial no. and my bootloader got locked again.and i got the lollipop rom.
i somehow manage to write the imei and serial no. and updated my rom to mm.But now i cannot unlock my bootloader again.And volte is still not working anybody please help i am a broke person and i cannot buy a new phone.please please help
[email protected] said:
I have twrp installed but i just typed fastboot oem lock now my bootloader is locked but i m on twrp how can i unlock bootloader.... since i m blocked from asus fota server so i cant unlock by signed unlock tool..... plz help me i think i need the oem unlock code...... or if any one can provide me the same models oem unlocked image file and i may flash that to unlock boot loader.... plz help guys.....
And does any of the auto root tool works for asus zenfone max android 6
Click to expand...
Click to collapse
There is no way u can re unlock the bootloader,but there is a workaround.Flash the beta marshmallow rom for 8916,watch the youtube video and check description,its a trick how to flash the beta.then simply flash twrp.the beta rom allows to flash twrp through fastboot.I found this method by myself over a month time
What will happen if I relock bootloader .. because I hate the pop up "your device has been unlocked .." while it boots.. does after relocking bootloader stops twrp to work ?
dhenewar said:
What will happen if I relock bootloader .. because I hate the pop up "your device has been unlocked .." while it boots.. does after relocking bootloader stops twrp to work ?
Click to expand...
Click to collapse
If you relock your bootloader with TWRP or anything else non stock, you'll likely boot loop until you unlock again. It's likely you'll trip the verification checks -performed by a locked bootloader - with TWRP, which means you need to be fully stock for a successful locked bootloader. If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues as you can't then unlock.
If you want to, you can flash a custom logo.bin (plenty of links in the Mods section) which will hide the warning, won't shorten the delay but it'll be nicer to look at.
echo92 said:
If you relock your bootloader with TWRP or anything else non stock, you'll likely boot loop until you unlock again. It's likely you'll trip the verification checks -performed by a locked bootloader - with TWRP, which means you need to be fully stock for a successful locked bootloader. If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues as you can't then unlock.
If you want to, you can flash a custom logo.bin (plenty of links in the Mods section) which will hide the warning, won't shorten the delay but it'll be nicer to look at.
Click to expand...
Click to collapse
Ok bro thanks for the info ..will SuperSu be as same as twrp causing bootloop?... luckily I have got stock recovery n firmware .. as u said "If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues " .. I am having the problem in other device(Samsung Galaxy grand prime G531H .. Cuz of my careless n rush.i forgot to enable oem n then flashed custom rom in Odin .. then it got bricked.. searched alot in internet for solution..also .. i have created post here.. still no solution .. and Now my device is just waste ..gave up on it ... RIP :angel: ..
dhenewar said:
Ok bro thanks for the info ..will SuperSu be as same as twrp causing bootloop?... luckily I have got stock recovery n firmware .. as u said "If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues " .. I am having the problem in other device(Samsung Galaxy grand prime G531H .. Cuz of my careless n rush.i forgot to enable oem n then flashed custom rom in Odin .. then it got bricked.. searched alot in internet for solution..also .. i have created post here.. still no solution .. and Now my device is just waste ..gave up on it ... RIP :angel: ..
Click to expand...
Click to collapse
I think so, a locked bootloader, as I understand it, checks the integrity of your recovery, kernel and system, and if it detects a break in the chain of trust (e.g. if there's a custom modification that changes the signature expected), then as a security measure the device just won't boot/bootloop. SuperSU or any root, custom kernel, or TWRP or even if you've allowed TWRP to make modifications may result in bootloops thus.
Therefore, if you wish to re-lock your device, you'll want to re-flash the stock firmware and then lock. You can only lock your device with the same firmware or newer than the version your device was updated to (including OTA updates). The latest version we have is the June fastboot ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Of course, flashing this will wipe TWRP, root and possibly your data from your device, so back up and keep the backups off your device. Alternatively, you may just wish to flash the custom logo.bin as mentioned previously, which would hide the bootloader warning.
About your Galaxy Grand Prime, ouch - that's a horrible situation to be in; unless there's a potential bootloader exploit, you're caught in the nasty situation where you can't unlock your bootloader (because of the OEM unlock) and because the security's been tripped, won't allow you to boot to get to the OEM unlock Are there any Samsung service centres or repair shops that could help you recover? You could have a look around the Galaxy Grand Prime forum, see if there's anything that could help: https://forum.xda-developers.com/grand-prime
echo92 said:
I think so, a locked bootloader, as I understand it, checks the integrity of your recovery, kernel and system, and if it detects a break in the chain of trust (e.g. if there's a custom modification that changes the signature expected), then as a security measure the device just won't boot/bootloop. SuperSU or any root, custom kernel, or TWRP or even if you've allowed TWRP to make modifications may result in bootloops thus.
Therefore, if you wish to re-lock your device, you'll want to re-flash the stock firmware and then lock. You can only lock your device with the same firmware or newer than the version your device was updated to (including OTA updates). The latest version we have is the June fastboot ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Of course, flashing this will wipe TWRP, root and possibly your data from your device, so back up and keep the backups off your device. Alternatively, you may just wish to flash the custom logo.bin as mentioned previously, which would hide the bootloader warning.
About your Galaxy Grand Prime, ouch - that's a horrible situation to be in; unless there's a potential bootloader exploit, you're caught in the nasty situation where you can't unlock your bootloader (because of the OEM unlock) and because the security's been tripped, won't allow you to boot to get to the OEM unlock Are there any Samsung service centres or repair shops that could help you recover? You could have a look around the Galaxy Grand Prime forum, see if there's anything that could help: https://forum.xda-developers.com/grand-prime
Click to expand...
Click to collapse
Thanx bro I will try it out .. yep bro I got it in service center n they told me .. No way of fixing it .. Aahh n that's it ? .well there was option change of hardware price was half of the phone cost ..better to buy new one ?
I have a problem guys i rebrand my phone from PRA-AL00 TO PRA-LA1 then i format the system by mistake
So when i try to unlock the phone it says
Command not allowed
The code is correct 100%
Either you use DC Phoenix tool or you should have a running system to first...relock the bootloader and then disable frp lock from the developers options or you use the rescue package for your device...
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
Either you use DC Phoenix tool or you should have a running system to first...relock the bootloader and then disable frp lock from the developers options or you use the rescue package for your device...
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
When i update the system form erecovery its says
Getting package info failed
Abdala2307 said:
When i update the system form erecovery its says
Getting package info failed
Click to expand...
Click to collapse
Can you still boot up and use firmware finder to upgrade? I think this is the only way to rescue apart from erecovery.
Or if you can access twrp, then you can easily use that.
I had my device go into frp lock when rebranding, used erecovery to somehow rescue my system and then got a NRD90M-testkeys version, no gapps included. I couldn't unlock oem in dev options and I couldn't update through official system. I used firmware finder to upgrade(full firmware) to the last confirmed version of Nougat(B220) and turned on oem unlocking in dev options, then relock-unlock again to remove the frp lock.
I also got into frp lock when formatting and then having a Google account, but the gapp service keeps crashing after factory reset. eRecovery would say getting package info failed. I used dc unlocker to remove the frp lock, upgraded to B220, and oem relock-unlock again.
I had stock recovery on both occasions so I was lucky enough to get out of it.