Custom recovery apart from twrp for Samsung j710f - General Questions and Answers

Hi.
My mobile is pattern locked and I forgot the pattern.
I don't have had activated usb debugging or OEM unlocking .
I tried flashing it with twrp recovery but no luck.
I don't want to lose my data from the mobile.
Is der any other custom recovery apart from twrp for Samsung j710f?
Thanks

gshanbhag525 said:
Hi.
My mobile is pattern locked and I forgot the pattern.
I don't have had activated usb debugging or OEM unlocking .
I tried flashing it with twrp recovery but no luck.
I don't want to lose my data from the mobile.
Is der any other custom recovery apart from twrp for Samsung j710f?
Thanks
Click to expand...
Click to collapse
I don't think there is, and even if there was you would still have to enable OEM unlock before flashing it.
Sent from my Moto G5 using Tapatalk

So this OEM unlocking is mandatory for flashing any custom recovery?

Yes. It has to be enabled to allow flash of binarys not signed by samsung, otherwise you will be forced to download mode to flash back stock firmware.
Sent from my Moto G5 using Tapatalk

Related

GPE HTC ONE has a weird Issue

Hi guys!I have a weird problem on my HTC one.which is Google Play Edition.First of all,I was updating my htc to 5.0.1 lollipop which is official via OTA.It took a lot of time and I shut down the phone.And then everything is going to worse.It stuck bootloop unfortunately usb debugging is off ,and the phone is completely stock.(stock recovery,s-on,locked bootloader) I cant do anything due to this problem.I tried "adb push" and flash ruu but they also didnt work.How can I do?Thanks for helping.
reset?
what's the sound like on it?
i know on the ones with htc sense it is hit and miss call quality (with an audible hissing sound).........
fatihlale said:
Hi guys!I have a weird problem on my HTC one.which is Google Play Edition.First of all,I was updating my htc to 5.0.1 lollipop which is official via OTA.It took a lot of time and I shut down the phone.And then everything is going to worse.It stuck bootloop unfortunately usb debugging is off ,and the phone is completely stock.(stock recovery,s-on,locked bootloader) I cant do anything due to this problem.I tried "adb push" and flash ruu but they also didnt work.How can I do?Thanks for helping.
Click to expand...
Click to collapse
You could try to erase cache using fastboot and see if it can boot. If not try a factory reset.
If factory reset still doesn't work you'll have to unlock your bootloader, flash a custom recovery and resotre a nanadroid backup or flash a stock rom of 5.0.1.
alray said:
You could try to erase cache using fastboot and see if it can boot. If not try a factory reset.
If factory reset still doesn't work you'll have to unlock your bootloader, flash a custom recovery and resotre a nanadroid backup or flash a stock rom of 5.0.1.
Click to expand...
Click to collapse
It doesn't work. How can I unlock boot loader while usb debugging is off. Is there any method?
fatihlale said:
It doesn't work. How can I unlock boot loader while usb debugging is off. Is there any method?
Click to expand...
Click to collapse
you don't need usb debugging. Usb debugging is only needed to have adb connectivity when the phone is booted in android.
for gpe device you should be able to unlock it using fastboot from the bootloader.
Code:
fastboot oem unlock
If this method doesnt work you'll need to use HTCdev.com to unlock it.
Don't forget that unlocking your bootloader will wipe everything on your phone.
alray said:
you don't need usb debugging. Usb debugging is only needed to have adb connectivity when the phone is booted in android.
for gpe device you should be able to unlock it using fastboot from the bootloader.
Code:
fastboot oem unlock
If this method doesnt work you'll need to use HTCdev.com to unlock it.
Don't forget that unlocking your bootloader will wipe everything on your phone.
Click to expand...
Click to collapse
It doesn't work bro because off usb debugging is disable. I tried many times but It doesn't work look at the attachmentView attachment 3059584
fatihlale said:
It doesn't work bro because off usb debugging is disable. I tried many times but It doesn't work look at the attachmentView attachment 3059584
Click to expand...
Click to collapse
It have nothing to do with usb debugging! Like I said above, the only purpose of usb debugging is to enable adb connectivity when the phone is booted in android.
Even if usb debugging is turned off, you still have the ability to use fastboot commands from the bootloader (like you have tried) and to use adb commands from a custom recovery (which you don't have access to because of your locked bootloader)
With that said, I'm sorry to tell you that what you are seeing after doing "fastboot oem unlock" (PG_ERROR) is typical of the infamous GPE bootloader bug. This bug make impossible to unlock your bootloader from using oem unlock or by using HTCdev.com method. So your phone is bricked sorry.
you are not alone, see this thread: http://forum.xda-developers.com/showthread.php?t=2547894
fatihlale said:
It doesn't work bro because off usb debugging is disable. I tried many times but It doesn't work look at the attachmentView attachment 3059584
Click to expand...
Click to collapse
so my device is going to rubbish am I right?
fatihlale said:
so my device is going to rubbish am I right?
Click to expand...
Click to collapse
Maybe keep it in a drawer and hope that HTC will release a 5.11.1700.3 or higher version official RUU so you'll be able to flash it with s-on and a locked bootloader.
or maybe you could ask the guys at fonefunshop if they are able to s-off it using their method which doesnt require to boot in the rom.

Stuck at Google logo :(

EDIT: so i tried a couple of things.. Everytime i unlock the bootloader and reboot it starts locked again (as if i never unlocked it), i tried to flash factory image using fastboot but gives me "flash write failure", tried flashing custom recoveries (both cwm and twrp) they flash fine but when i boot into recovery mode the stock recovery appears, so i tired sthg new : booting from the custom recovery without flashing... Cwm boots fine..fails to factory reset (it just gives error and reboots the phone especially when i try anything with the cache partition) so i went to boot twrp.. It takes half an hour to open twrp after its "teamwin" screen... But it helped me as it showed that : system and firmware partitions are working well (format /mount) but cache, persist and data partitions don't (no mounting and error while formating) plus data partition shows zero Mb size.... Basically any change i do either gives an error or dissappears on reboot..... Please helppp! ?
Old post:
Hey all,
My hammerhead is stuck at Google logo, the problem is that bootloader is locked and usb debugging is disabled... Can't boot to enable it, can't flash new rom.. What can i do with no usb debugging and locked bootloader? Thanks in advance
Gofersamy said:
Hey all,
My hammerhead is stuck at Google logo, the problem is that bootloader is locked and usb debugging is disabled... Can't boot to enable it, can't flash new rom.. What can i do with no usb debugging and locked bootloader? Thanks in advance
Click to expand...
Click to collapse
You can boot into recovery and do a factory reset. It'll wipe your data. Or you can unlock the bootloader, it'll wipe your data, and flash the factory image.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You can boot into recovery and do a factory reset. It'll wipe your data. Or you can unlock the bootloader, it'll wipe your data, and flash the factory image.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
As far as i understand unlocking the bootloader would require enabled usb debugging right?
Gofersamy said:
As far as i understand unlocking the bootloader would require enabled usb debugging right?
Click to expand...
Click to collapse
No. fastboot oem unlock - http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
Gofersamy said:
As far as i understand unlocking the bootloader would require enabled usb debugging right?
Click to expand...
Click to collapse
No, you'd don't need usb debugging enabled to unlock the bootloader. You just need fastboot on your pc. Google 15 second adb install xda. That'll setup fastboot. Then boot into your bootloader and from a command window on your pc run the command
fastboot oem unlock
Sent from my Nexus 5 using XDA Free mobile app

Custom binary locked by frp error-solution?

I recently rooted my samsung j700f android marshmallow device 6.0.1.i got "custom binary blocked by frp"error. I managed to install stock rom from samsung website with help of odin.is there any success rooting method for this device without any error?.if i enable oem unlocking after rooting my device resolves restart problem or my mobile brick again?.adding gmail account into playstore cause for "custom binary blocked by frp error"? Pls explain
Sent from my SM-J700F using Tapatalk
flash stock rom through odin
D
OEM unlock must always be ticked if you are using diffrent recovery to root. Or else you will be FRP locked.
id_866 said:
I recently rooted my samsung j700f android marshmallow device 6.0.1.i got "custom binary blocked by frp"error. I managed to install stock rom from samsung website with help of odin.is there any success rooting method for this device without any error?.if i enable oem unlocking after rooting my device resolves restart problem or my mobile brick again?.adding gmail account into playstore cause for "custom binary blocked by frp error"? Pls explain
Sent from my SM-J700F using Tapatalk
Click to expand...
Click to collapse
flash stock rom , always leave enable oem unlock enabled
Flash official rom with Odin, don't worry previous setting ,app & data is not lost. After flash reboot go to developer option enable "usb debugging" and "OEM unlock" (don't forget..) before flash custom rom/recovery again
Aredtama said:
Flash official rom with Odin, don't worry previous setting ,app & data is not lost. After flash reboot go to developer option enable "usb debugging" and "OEM unlock" (don't forget..) before flash custom rom/recovery again
Click to expand...
Click to collapse
Will this method successful one without any error?
Sent from my SM-J700F using Tapatalk
Sure it will.., I have same problem like you after i disable oem unlock in dev option. My device SM J700F is rooted and use twrp recovery can't boot (bricked) because frp locked in reboot .Just download official rom and flash with ODIN and be sure only Auto Reboot and F. Reset Time option is selected so your data is not wipe when flashing .
Disabling oem unlock make device permanent brick?
Sent from my SM-J700F using Tapatalk
Yes, if we want using custom recovery and root kernel we must enable oem unlock and usb debugging, disable it may cause bootloop and bricked (custom os blocked by frp lock) :good:
Suppose i am enabling oem unlock and developer options. Root and add gmail account.will boot loop or custom lock by frp error come? Samsung added patches to prevent rooting mobiles? Has anyone successfully rooted this mobile j700f?
Sent from my SM-J700F using Tapatalk
I am rooted, J700F on MM. On top of oem unlock and usb debugging, I always setup Google LAST.
Sent from my SM-G903M using XDA-Developers mobile app
dodo2244 said:
I am rooted, J700F on MM. On top of oem unlock and usb debugging, I always setup Google LAST.
Sent from my SM-G903M using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you restarted your mobile?.any bootloop or frp error after setting up gmail account?
Sent from my SM-J700F using Tapatalk
No problems at all. I flash a new rom like every 10 days. Our Devs are keeping me busy ?
Sent from my SM-G903M using XDA-Developers mobile app
I used 3 google accounts ,added in my J7 that's it doesn't make the frp lock,, the only cause frp lock in samsung is oem unlock, just enable the usb debugging and oem unlock. Rooting and custom rom will work.. on that

What happens if I disable OEM-Unlock in developer settings?

I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Maik_ said:
I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Click to expand...
Click to collapse
Turned it off once by accident but turned on again.. Nothing changed
I don't think anything changes unless u relock it via fastboot, which at that point as long as u can boot back into the OS, u can always unlock it again, relocking bootloader will format ur data and u will no long be rooted or have twrp installed
locking your bootloader with root etc installed can cause major problems so before doing that you should flash a stock firmware otherwise you will be locked out
Why would you want to do this? There is no benefit to it if you plan to stay rooted.
Need to find something to do. You bored
iElvis said:
Why would you want to do this? There is no benefit to it if you plan to stay rooted.
Click to expand...
Click to collapse
I want to disable developer options, but if I do that OEM-Unlock automatically turns off and I don't want to reboot because I dont want that I lock myself out.
Your cat will get knock up..........again!
Maik_ said:
I want to disable developer options, but if I do that OEM-Unlock automatically turns off and I don't want to reboot because I dont want that I lock myself out.
Click to expand...
Click to collapse
Just turning off Developer Options won't relock your bootloader. You can only do that manually in fastboot. But you'll also lose USB debugging, which means adb won't work anymore in case something goes wrong. (But leaving USB debugging on all the time isn't the best idea anyway.)
Hello everyone
I think I did that mistake
I have twrp installed on my phone Samsung SM-G532F . my phone was working just fine but I have locked the oem for no reason .
now when I turn off the device and tried to turn it on it shows { Custom binary blocked by FRP. (boot. img) }
and when I open recovery mode it shows { Custom binary blocked by FRP. (recovery. img) }
the download mode is working and shows that the FRP lock is on .
I tried to flash the stock recovery with odin but since the FRP is locked it failed .
the adb is not working because the device cannot boot , even the battery symbol when I plug my phone with a charger is not displayed and shows the error { Custom binary blocked by FRP. (boot. img) }
any ideas will help a lot .
omer123137 said:
Hello everyone
I think I did that mistake
I have twrp installed on my phone Samsung SM-G532F . my phone was working just fine but I have locked the oem for no reason .
now when I turn off the device and tried to turn it on it shows { Custom binary blocked by FRP. (boot. img) }
and when I open recovery mode it shows { Custom binary blocked by FRP. (recovery. img) }
the download mode is working and shows that the FRP lock is on .
I tried to flash the stock recovery with odin but since the FRP is locked it failed .
the adb is not working because the device cannot boot , even the battery symbol when I plug my phone with a charger is not displayed and shows the error { Custom binary blocked by FRP. (boot. img) }
any ideas will help a lot .
Click to expand...
Click to collapse
You cannot boot with a custom recovery and a locked bootloader. As to how to fix this, you need to ask in the Samsung forums. This is for OnePlus 6.
If you have a oneplus look in the forum for msmdownloadtool and follow the steps, you can revive your phone.
If your phone its a samsung, search in samsung forums for a tool to unbrick your phone.
iElvis said:
You cannot boot with a custom recovery and a locked bootloader. As to how to fix this, you need to ask in the Samsung forums. This is for OnePlus 6.
Click to expand...
Click to collapse
I was finally able to solve this issue with flashing the official firmware with odin . now I will never touch the oem unlock button ever again :laugh: . but thank you for your reply .
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
Toni Moon said:
If you have a oneplus look in the forum for msmdownloadtool and follow the steps, you can revive your phone.
If your phone its a samsung, search in samsung forums for a tool to unbrick your phone.
Click to expand...
Click to collapse
I downloaded and flashed the official firmware with odin and it worked . thanks for the reply
I did this once on my OnePlus X, disabled oem unlocking in developer options. phone and recovery worked fine. I did a backup. Flashed a new rom to test it. The rom had AOSP recovery in the zip, overwriting twrp (opx has separate recovery partition). I flashed gapps affter the rom and the setup wizard was crashing so I could not boot in the home screen. Tried TWRP, its gone. Tried to boot to twrp via fastboot, oem locked. Had to do hard brick reset. Backup and data, gone.
TLDR, you should leave it on, unless you are on stock firmware.
After flash a rom you must flash twrp recovery again, restart in recovery and flash gapps and magisk
First of all you have to flash combination file associated with your device model through ap slot of odin.
Then your phone will turn on and you can access settings through which you can turn on oem unlock.
Then you can install your desired rom into your device
Sinankhan.official said:
First of all you have to flash combination file associated with your device model through ap slot of odin.
Then your phone will turn on and you can access settings through which you can turn on oem unlock.
Then you can install your desired rom into your device
Click to expand...
Click to collapse
This isn't a Samsung device.
Maik_ said:
I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Click to expand...
Click to collapse
I also accidentally turned off oem in rooted phone , Does my bootloader locked or I can safely reboot
I restored the stock firmware using Odin, but now I see that the bootloader is still unlocked.
When try to lock it again the system says: "If OEM unlock is turned off, your phone will be reset to factory default settings after restart. This will erase all of your data... " etc.
My question is: will the firmware be still in place? I don't mind everything being wiped, because most of it will be restored anyway when I login to Google and Samsung again.
SamarSS123 said:
I also accidentally turned off oem in rooted phone , Does my bootloader locked or I can safely reboot
Click to expand...
Click to collapse
No

Question Allow oem unlocking option missing in developer options

So, i recently flashed arrow os 12.1 on my poco x4 pro (veux) using twrp. Flashing the rom removed twrp and now i cant flash it back because fastboot says that my bootloader is locked...
Of course, it isn't and the problem is that allow oem unlocking isn't on... I really would appreciate some help because i've been stuck on this rom for a day.
Gonna wait for some answers, thank you.
In the first place, flashing the rom shouldn't relock your bootloader. Can you please reboot to fastboot mode and use mi unlock tool with the same account you used to unlock bootloader first time.
Soma Das said:
In the first place, flashing the rom shouldn't relock your bootloader. Can you please reboot to fastboot mode and use mi unlock tool with the same account you used to unlock bootloader first time.
Click to expand...
Click to collapse
Thank you for your response. Sadly i already tried that and the tool says that the phone is unlocked.
I'm trying to reflash stock rom via EDL mode, but i always get some error.
By the way, when using fastboot getvar command, it says that my bootloader is locked.
So, i recently bought a poco x4 pro (veux) and flashed a custom rom using twrp. Sadly, the rom's recovery managed to overwrite twrp and when i tried to flash twrp back, i could not flash it because fastboot said my bootloader wasn't unlocked. When i tried to unlock the phone again the xiaomi tool said that the bootloader was already unlocked. So, i used the getvar command which said that my bootloader was locked. So, i remembered that i didnt turn on allow oem unlocking in developer options. Sadly, when i looked for it the setting wasn't there. I tried using Edl mode to go back to stock but with no success. I always get some failed to read hello packet error. Can someone give me any help? Im kinda getting desperate...
WhyisAethertaken said:
So, i recently bought a poco x4 pro (veux) and flashed a custom rom using twrp. Sadly, the rom's recovery managed to overwrite twrp and when i tried to flash twrp back, i could not flash it because fastboot said my bootloader wasn't unlocked. When i tried to unlock the phone again the xiaomi tool said that the bootloader was already unlocked. So, i used the getvar command which said that my bootloader was locked. So, i remembered that i didnt turn on allow oem unlocking in developer options. Sadly, when i looked for it the setting wasn't there. I tried using Edl mode to go back to stock but with no success. I always get some failed to read hello packet error. Can someone give me any help? Im kinda getting desperate...
Click to expand...
Click to collapse
Go to service centre if it is critical. I have never seen such case so i couldn't help. I am afraid that you would have to pay the service centre people money for reflashing your device.
Also have you tried flashing fastboot ROM (MIUI) through fastboot? Also try to flash stock recovery rom via the recovery you have now currently.
Another thing you could try is using the Xiaomi official flashing utility (which is not unlock tool) to flash stock rom which does not require OEM unlock.
Soma Das said:
Go to service centre if it is critical. I have never seen such case so i couldn't help. I am afraid that you would have to pay the service centre people money for reflashing your device.
Also have you tried flashing fastboot ROM (MIUI) through fastboot? Also try to flash stock recovery rom via the recovery you have now currently.
Another thing you could try is using the Xiaomi official flashing utility (which is not unlock tool) to flash stock rom which does not require OEM unlock.
Click to expand...
Click to collapse
Thanks for the reply, i will try what you said.

Categories

Resources