After installing Super user through TWRP, my Phone: Galaxy Grand Prime 4G Dual SIM, SM-G531H encountered a problem in recovery mode
and says "Custom Binary Blocked by FRP Lock" and it is not booting.
1. Tried to flash using ODIN v3.10, while flashing it stucks at FRP Lock and fails the flashing process.
2. Tried Kies3, but it cannot identify my S/N
Please help me
Thanks you
pradeep.sl said:
After installing Super user through TWRP, my Phone: Galaxy Grand Prime 4G Dual SIM, SM-G531H encountered a problem in recovery mode
and says "Custom Binary Blocked by FRP Lock" and it is not booting.
1. Tried to flash using ODIN v3.10, while flashing it stucks at FRP Lock and fails the flashing process.
2. Tried Kies3, but it cannot identify my S/N
Please help me
Thanks you
Click to expand...
Click to collapse
The G531H is a dual sim model yes, but it is NOT 4G, it is a 3G only model.
FRP lock can be solved by reflashing to stock firmware (You'll need to make an account: https://samsung-firmware.org/download/GALAXY GRAND Prime/t1s5/UPO/G531HUBU0APE2/G531HUUB0APE2/ -Download an older one if that doesnt work. Also thats the uruguay firmware so double check for your country too)
- Use ODIN to flash this, it should work fine with v3.10. Click PDA or AP (Depending on ODIN) and add the firmware.
Then after setting up your phone, go to settings->about-> tap build number 7 times to activate developer options.
press the back key->developer options->enable manufacturer unlock. (NEVER UNTICK THIS UNLESS YOUR RUNNING UnROOTED STOCK)
Flash TWRP as normal, then flash flash the supersu.zip thats available here on the forums.
Hope it helps!
u0aol said:
The G531H is a dual sim model yes, but it is NOT 4G, it is a 3G only model.
FRP lock can be solved by reflashing to stock firmware (You'll need to make an account: https://samsung-firmware.org/download/GALAXY GRAND Prime/t1s5/UPO/G531HUBU0APE2/G531HUUB0APE2/ -Download an older one if that doesnt work. Also thats the uruguay firmware so double check for your country too)
- Use ODIN to flash this, it should work fine with v3.10. Click PDA or AP (Depending on ODIN) and add the firmware.
Then after setting up your phone, go to settings->about-> tap build number 7 times to activate developer options.
press the back key->developer options->enable manufacturer unlock. (NEVER UNTICK THIS UNLESS YOUR RUNNING UnROOTED STOCK)
Flash TWRP as normal, then flash flash the supersu.zip thats available here on the forums.
Hope it helps!
Click to expand...
Click to collapse
It worked Thank you So much (Y)
pradeep.sl said:
It worked Thank you So much (Y)
Click to expand...
Click to collapse
Your very welcome, I'm glad it helped!
SM-G530T does not support initialization from my end.
Don't know what else i must do to get this done.
Can anyone help me out with this?
Nao passa disto , alguem sabe ajudar
It is not system. img i started the cable at the time because it was taking a while and i went to reboot the installation
, Version: G531BT Grand Prime
Do not pass this, someone knows how to help.
Igor ShakiroNeo said:
It is not system. img i started the cable at the time because it was taking a while and i went to reboot the installation
, Version: G531BT Grand Prime
Do not pass this, someone knows how to help.
Click to expand...
Click to collapse
FRP Lock is enabled when you have a google account on your phone and if you modified your boot or recovery. To disable FRP, either remove the google account or restore the stock boot.img and/or the recovery.img if you modified it.
Nemirtingas said:
FRP Lock is enabled when you have a google account on your phone and if you modified your boot or recovery. To disable FRP, either remove the google account or restore the stock boot.img and/or the recovery.img if you modified it.
Click to expand...
Click to collapse
this I make it hangs and it does not go on. I get a 10 minute wait and it stopped in system.img. I already installed recovery.img or boot.img. when it arrives in system.img it is stopped
Igor ShakiroNeo said:
this I make it hangs and it does not go on. I get a 10 minute wait and it stopped in system.img. I already installed recovery.img or boot.img. when it arrives in system.img it is stopped
Click to expand...
Click to collapse
Then if you flashed recovery, can you boot into recovery ? If you can, then try to use sideload from recovery and restore your system.
If Odin stop when flashing system.img, check your USB wire, download an up to date Odin & Stock firmware, maybe your Firmware is corrupted somewhere.
I've been installing the frp locked twrp I do not know what the correct name is. AND
* I found an original cable there at home Samsung I do not know I'm believing it's cable I'll try to do it now. This Side load I'm afraid that it works the same twrp by and frp does not accept frp official program is blocking!
Does it work if I try to install it by the memory card or SD card?
Igor ShakiroNeo said:
I've been installing the frp locked twrp I do not know what the correct name is. AND
* I found an original cable there at home Samsung I do not know I'm believing it's cable I'll try to do it now. This Side load I'm afraid that it works the same twrp by and frp does not accept frp official program is blocking!
Does it work if I try to install it by the memory card or SD card?
Click to expand...
Click to collapse
If you have access to your phone, you can zero you PERSISTENT partition (that's how its called on my phone), its where android saves the FRP blocking infos. By zeroing it, you can run anything like before till google play service rewrite it again. I just do dd if=/dev/zero of=/dev/block/platform/soc.2/by-name/PERSISTENT, and I can boot to TWRP, but if I start phone to system, PERSISTENT gets rewritten again and then FRP lock turns on again, but I just made a script that runs when I shutdown phone that zero this partition so I don't have FRP anymore. :good:
No meu caso aqui eu preciso só instalar um Android que não está sendo restaurado ele trava no quando eu fecho ele ele não trava ele fica parado e não anda mais. Eu abro o Odin instalar boot recovery chegar na System link ele não passa ele fica parado carregando eu acho que é o cabo será
In my case here I only need to install an Android that is not being restored it locks in when I close it it does not lock it it stops and it does not walk anymore. I open Odin install boot recovery get on the System link it does not pass it stands still loading I think it's the cable will be.
Aqui eu só tenho acesso ao recovery e modo download no meu caso aqui tem alguma chance? e não tem depuração ativado não tem root eu tenho chance de restaurar conseguir salvar meu celular?
Here I only have access to recovery and download mode in my case here has any chance? and does not have debugging enabled does not have root do i have chance to restore able to save my cell phone?
Igor ShakiroNeo said:
No meu caso aqui eu preciso só instalar um Android que não está sendo restaurado ele trava no quando eu fecho ele ele não trava ele fica parado e não anda mais. Eu abro o Odin instalar boot recovery chegar na System link ele não passa ele fica parado carregando eu acho que é o cabo será
In my case here I only need to install an Android that is not being restored it locks in when I close it it does not lock it it stops and it does not walk anymore. I open Odin install boot recovery get on the System link it does not pass it stands still loading I think it's the cable will be.
Aqui eu só tenho acesso ao recovery e modo download no meu caso aqui tem alguma chance? e não tem depuração ativado não tem root eu tenho chance de restaurar conseguir salvar meu celular?
Here I only have access to recovery and download mode in my case here has any chance? and does not have debugging enabled does not have root do i have chance to restore able to save my cell phone?
Click to expand...
Click to collapse
You last chance may be the QCOM Tools to reflash your phone at very low Level.
Nemirtingas said:
You last chance may be the QCOM Tools to reflash your phone at very low Level.
Click to expand...
Click to collapse
Where do I find this? It's for samsung!
Igor ShakiroNeo said:
Where do I find this? It's for samsung!
Click to expand...
Click to collapse
Ha G531BT is a Marvell SoC, my bad x). Your only chance is to update your samsung drivers, Update Odin, download a fresh firmware and flash your phone. Don't touch the wire while flashing.
I give up I'm going to leave here, even if it's an hour to 5 hours, if I'm not going to sell the pieces
Related
Good morning people. I'm using google translator, I hope you understand my problem.
Was wearing that rom, XtreStoLite 2.2 to G900M.
The problem I'm facing is this:
1. My system does not have the reativaction lock menu.
2. I can not access the recovery because a message appears saying "Fail Secure: Recovery".
3. I can not install anything at ODIN concerning PDA. Only BL, CSC, etc. Message appears saying "secure check fail recovery"
How do I reinstall this menu to be able to log in and release the Samsung recovery?
:crying:
flash via recovery stock based rom
How?
Flash a stock KitKat ROM using ODIN, log into all accounts, disable reactivation lock
*Detection* said:
Flash a stock KitKat ROM using ODIN, log into all accounts, disable reactivation lock
Click to expand...
Click to collapse
Essa mensagem, "secure check fail: recovery", aparece sempre que tento fazer algo pelo PDA|AP. Só testei com arquivos de recovery, mas não acham que vá aparecer pra firmware também? =[
*Detection* said:
Flash a stock KitKat ROM using ODIN, log into all accounts, disable reactivation lock
Click to expand...
Click to collapse
This message, "secure check Fail: recovery" appears whenever I try to do something for PDA | AP. Only tested with recovery files, but do not think that goes to show firmware too? = [
It worked. I have no words to thank you. Thank you for hand. You are the best.
:good:
Hello,
I'm french, this message is translated by reverso :
I had cyanogenmod and I wanted to return to the stock. For that purpose, I just put the update.app in the file(case) / dload / of the card(map) sd then I am to remain pressed on 3 buttons to install(settle) him(it), instalation with no problem at all, but the démmarage lasts infinitely.... I can reinstall but it's always the same, I do not manage to go in the bootloader or in the recovery
Please help me !
RESOLVED ! THANKS
Thanks
If you need more information, ask me
-----
Original message :
J'avais cyanogenmod et j'ai voulu retourner au stock. Pour cela, j'ai juste mis le update.app dans le dossier /dload/ de la carte sd puis je suis rester appuyé sur les 3 boutons pour l'installer, instalation sans problème, mais le démmarage dure infiniment .... Je peut réinstaller mais c'est toujours pareil, je n'arrive pas à acceder au bootloader ou au recovery
----
I'm not an expert, but I think that you have to install the stock recovery first.
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Try to boot in recovery, then wipe data/factory reset
Potato997 said:
Try to boot in recovery, then wipe data/factory reset
Click to expand...
Click to collapse
Yes but how ?
The fastboot mode simply reboot the phone (don't appear)
The recovery install directly the update, and if i remove the sdcard, he say "Software update failed, please redownload the file (Normal because there is not any more the file update.app)
And i can't shutdown my phone
I waits that it is no more battery
;(
Is your bootloader unlocked? If yes you can try to flash TWRP
Potato997 said:
Is your bootloader unlocked? If yes you can try to flash TWRP
Click to expand...
Click to collapse
The bootloader is relocked, but i can't boot in fastboot mode
If i can boot in fastboot mode, All my problems are settled.
I have booted in huawei recovery
I do i wipe data/factory reset
I tell you if its work
Its boot with the sound *
It booted and it work
Thanks
I have hold the vol+ and power button with no sd
I had the same problem but I managed to boot in fastboot simply by having the phone plugged to the pc (power+vol down)
So apparently I bricked my phone while trying to root it and now the only thing to save it is through reflash of rom. I tried doing the adb update and sd card and it seems like it wont work anyone here knows how to completely reprogram the unit? or atleast via spf flash method
fjgeronimo23 said:
So apparently I bricked my phone while trying to root it and now the only thing to save it is through reflash of rom. I tried doing the adb update and sd card and it seems like it wont work anyone here knows how to completely reprogram the unit? or atleast via spf flash method
Click to expand...
Click to collapse
What method of rooting u made? Hiw do u brick the phone?
I don't think scatter file is available.
Sent from my ASUS_X00DDA using XDA-Developers Legacy app
Not trying to hijack the thread but apparently I've just bricked my ZC553KL as well.
Battery consumption was a pain in the ass so I decided to try and downgrade to Marshmallow since it was much better. Came across a Google+ post about using ADB Fastboot (which I've never done before) and gave it a shot.
My steps were:
1 - downloaded the ROM directly from Asus (UL-ZC553KL_ASUS_X00DD-WW-13.0.0.187-user.zip) and put it in the SD card.
2 - downloaded the ADB folder from drive . google.com/open?id=0B9Rp_y4wGHhxMzNTM0h6X0pIN28
3 - copied the boot.img file from the ROM to the ADB folder. Since there was no recovery.img in the ROM, this was skipped.
4 - rebooted the phone in fastboot (while debugging mode active) and plugged the USB cable from my PC to the phone.
5 - went to the ADB folder, fired up command prompt and used the following commands:
5.1 fastboot devices
5.2 fastboot flash boot boot.img
5.3 fastboot flash recovery recovery.img (this resulted in error because there was no recovery.img file)
6 - Unplugged the cable, rebooted in Recovery Mode and tried to Update from SD Card. Now I'm getting this message:
"Warning: No file_contextsT This package is for "ASUS_X00DD" devices; this is a "".
E:Error in /sideload/package.zip
(Status 7)"
I'm completely clueless about what to do and would appreciate any help you could give me.
poltz said:
6 - Unplugged the cable, rebooted in Recovery Mode and tried to Update from SD Card. Now I'm getting this message:
"Warning: No file_contextsT This package is for "ASUS_X00DD" devices; this is a "".
E:Error in /sideload/package.zip
(Status 7)"
I'm completely clueless about what to do and would appreciate any help you could give me.
Click to expand...
Click to collapse
If you're 100% sure you have the correct firmware, edit the update script, see this
thread, part 1, step 2-4
I'm curious if you even needed to update the bootloader beforehand since when you flash the firmware it'll flash the bootloader anyways.
wang1chung said:
If you're 100% sure you have the correct firmware, edit the update script, see this
thread, part 1, step 2-4
I'm curious if you even needed to update the bootloader beforehand since when you flash the firmware it'll flash the bootloader anyways.
Click to expand...
Click to collapse
Just tried those 3 steps in the link, but no luck.
I've opened the ROM zip, edited the updater-script file and saved .
In the beginning of the update process, it verifies the file but doesn't let me go further, giving me the following error message:
""E:failed to verify whole-file signature
Update package verification took 78.9s (result 1).
E:Signature verificaton failed
E:error: 21
Installation aborted"
Was I supposed to extract, modify and save a new zip?
Replace stock recovery with TWRP.....might be a corrupted download but I doubt it if you were able to extract the update script and save it back. Try redownloading it first.
Might want to create your own thread if it doesn't work, even though it doesn't seem like the OP is coming back.
wang1chung said:
Replace stock recovery with TWRP.....might be a corrupted download but I doubt it if you were able to extract the update script and save it back. Try redownloading it first.
Might want to create your own thread if it doesn't work, even though it doesn't seem like the OP is coming back.
Click to expand...
Click to collapse
I have already downloaded multiple ROMs, all with the same results. Even tried using different browsers (Chrome and Firefox).
Also, no luck finding TWRP for my device. Google only shows results for the lower end Max, code ZC520TL.
After testing multiple solutions online only to find that it was impossible to make my phone operational again, I've decided to send it to Asus for repair. It is now back and working perfectly, even with the ROM I've wanted to install in the first place.
Just a quick update to anyone who was quietly following this thread or may happen to stumble upon it while looking for help.
poltz said:
After testing multiple solutions online only to find that it was impossible to make my phone operational again, I've decided to send it to Asus for repair. It is now back and working perfectly, even with the ROM I've wanted to install in the first place.
Just a quick update to anyone who was quietly following this thread or may happen to stumble upon it while looking for help.
Click to expand...
Click to collapse
did they have to factory reset the device?
I believe they did.
Please help.. What Flashtool can we use in zen maxx 5.5??
All that i downloaded doesnt include the unit o iis??
Olá, alguma novidade de como ressuscitar o aparelho? Meu aparelho esta ascendendo apenas ao led vermlho quando conectado ao Desktop. Meu Windows 10 identifica o aparelho como QDLoader 9008 Qualcomm HS-USB, o problema é que quando tento instalar um Room pelo QFIL, ele apresenta o seguinte erro: Download Fail: FireHose Fail: FHLoader Fail: Process fail
Alguém poderia me ajudar por favor?
Tenham todos um excelente dia!
Isaac Castanha said:
Olá, alguma novidade de como ressuscitar o aparelho? Meu aparelho esta ascendendo apenas ao led vermlho quando conectado ao Desktop. Meu Windows 10 identifica o aparelho como QDLoader 9008 Qualcomm HS-USB, o problema é que quando tento instalar um Room pelo QFIL, ele apresenta o seguinte erro: Download Fail: FireHose Fail: FHLoader Fail: Process fail
Alguém poderia me ajudar por favor?
Tenham todos um excelente dia!
Click to expand...
Click to collapse
Translated, sorry.
Hello, any news on how to resuscitate the device? My device is only ascending to the red led when connected to the Desktop. My Windows 10 identifies the device as QDLoader 9008 Qualcomm HS-USB, the problem is that when I try to install a Room through QFIL, it presents the following error: Download Fail: FireHose Fail: FHLoader Fail: Process fail
Could someone help me please?
Have a great day everyone!
Isaac Castanha said:
Olá, alguma novidade de como ressuscitar o aparelho? Meu aparelho esta ascendendo apenas ao led vermlho quando conectado ao Desktop. Meu Windows 10 identifica o aparelho como QDLoader 9008 Qualcomm HS-USB, o problema é que quando tento instalar um Room pelo QFIL, ele apresenta o seguinte erro: Download Fail: FireHose Fail: FHLoader Fail: Process fail
Alguém poderia me ajudar por favor?
Tenham todos um excelente dia!
Click to expand...
Click to collapse
Asus ZenFone 3 Max (ZC553KL) became X00DD Unbrick. It only sees the QFIL program. Or can you make a rom that I can install in QFIL.
Asus ZenFone 3 Max (ZC553KL) became X00DD Unbrick. It only sees the QFIL program. Or can you make a rom that I can install in QFIL.
hi
during a firmware update i have a error message
since i can't start my p9lite
this phone stay at the huawei logo's
i have no access to the erecovery but i have access to fastboot rescue mode
ihave green phone locked and frp lock
i can't unlock my bootload with my code i have systematicaly failed info
do you have a solution for me?
ps i'm french so excuse me for my bad english
regard's
ced43 said:
hi
during a firmware update i have a error message
since i can't start my p9lite
this phone stay at the huawei logo's
i have no access to the erecovery but i have access to fastboot rescue mode
ihave green phone locked and frp lock
i can't unlock my bootload with my code i have systematicaly failed info
do you have a solution for me?
ps i'm french so excuse me for my bad english
regard's
Click to expand...
Click to collapse
Dload or rollback package then rom
you need indicate your build number, if is a NOUGAT or a MARSHMALLOW
Jinclaudio said:
you need indicate your build number, if is a NOUGAT or a MARSHMALLOW
Click to expand...
Click to collapse
That's why I said " rollback package or just ROM via dload "
ced43 said:
hi
during a firmware update i have a error message
since i can't start my p9lite
this phone stay at the huawei logo's
i have no access to the erecovery but i have access to fastboot rescue mode
ihave green phone locked and frp lock
i can't unlock my bootload with my code i have systematicaly failed info
do you have a solution for me?
ps i'm french so excuse me for my bad english
regard's
Click to expand...
Click to collapse
Salut,
Ton code pour déverrouiller le bootloader n'est pas bon?
Quelles manipulations as-tu faites et quel message d'erreur as-tu ?
J'imagine que tu es en VNS-L31C432Bxxx, mais quel "B" exactement?
La première chose serait de déverrouiller ton bootloader, ensuite flasher TWRP pour ta version (dépend de ta version B), ensuite flasher l'oeminfo pour ton tel (si tu as un C432 europe, je te donnerais un lien).
Pour finir tu le mettra en B160 FULL grâce au dload, puis tu feras les maj en OTA et ensuite tu pourras installer une custom rom.
------------------------------------------------------
Your unlock code is not good?
what have you done and what's error message you got?
What's your model variant (VNS...)
-unlock bootloader and flash TWRP for your variant (MM or N)
-flash the good oeminfo for you
-use dload methode to flash B160 full update
-update on last version with OTA update
-you able to install a custom rom
Je peux pas déverrouiller mon bootloader
Je suis en vns l31c900b160 de mémoire j'ai pas mon téléphone sous les yeux
Having the same problem.
Hello,
I'm Having the same problem. dload and rollback method not working. Keeps hanging at 5% then reboots, see the huawei logo and black screen. This all happened after installing Elite rom v6 https://forum.xda-developers.com/hu...elite-rom-v1-0-nougat-builds-cxxb3xx-t3625599
Hopefully someone knows a solution.
Greetz
hey board,
i have the same problem here... :crying:
i only can start fastboot&recovery mode... phone locked, FRP locked
dload will NOT work... the phone vibrates 2 times and hangs in the logo screen
my problem is, that i dont have a code, no SN, no IMEI etc.... (is there an option to get this info out of the fastboot screen?)
what i have done....
upload huawei image c432B130 (before: c900b130 - 10/2016) via dload
after reboots my phone hangs in a boot loop....
thx in advance!
I have been trying to root my J7 Pro, however, I have been hindered by many obstacles. The first one was trying to install TWRP (i know it isn't necessary). When I tried, I was greeted with a fail on Odin and the error message "Only official released binaries are allowed to be flashed".
I tried to get around this by trying to unlock the bootloader through fastboot. When I tried to do so, the computer would just outright not detect the phone while in fastboot mode. Nothing will show up in the command prompt, nothing will show up in Device Manager, and I've tried to use all USB ports, which means both USB 2.0 and 3.0.
My next step is to flash the ROM to Nougat (phone is currently in Oreo) and try to get OEM unlock from there. This is where I started this post. Should I go ahead with downgrading my phone, then trying to flash TWRP, or is there another method?
Where I'm heading: https://forum.xda-developers.com/samsung-a-series-2017/how-to/guide-root-install-twrp-samsung-t3747535
P.S Yes, RMM is set to Prenormal.
Thanks!
Edit 1:
Literally found this 5 minutes ago, would this work for this particular case?
cara, vc conseguiu algo?
fiz o root e deu tudo certo! mas tive que reiniciar o celular e agora vejo a mensagem: "Only official released binaries are allowed to be flashed" no meu J7. O que fazer? Alguma forma de voltar? pode me ajudar?
Dude, you did it?
my root worked!... but I had to reboot the phone and now I see the message: "Only official released binaries are allowed to be flashed" in my J7.
What to do? Any way to get back? can you help me?