Related
Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!
Flash the stock firmware with ODIN
Envoyé de mon SM-G935F en utilisant Tapatalk
Thanks for the reply,
Sorry but I'm new. How do i do that?
pr0cupid said:
Thanks for the reply,
Sorry but I'm new. How do i do that?
Click to expand...
Click to collapse
What model? Country
Sent from my Blackberry Bold
Model : SM-G935FD
Country : Singapore
frp lock s7 edge
pr0cupid said:
Hi Guys,
I'm sure some of you may have heard about this error before.
Well, here's my sad sad story.
After trying to root my s7 edge,
Everything seems fine.
One day when i re-format my phone, and after which downloaded a few apps, there wasn't any issue at all
However when i restarted my phone, i saw the error msg : Custom Binary block by FRP Lock
And after which it can't boot up anymore.
Anyone of you guys able to help me ?
It'll be much appreciated!
Click to expand...
Click to collapse
i have same issue here, did you find any solutions ?
AFAIK when you factory reset your phone etc. if rooted you must remember to go back into Developer Options and re enable OEM Unlocking. This depends on the method you used to root, if you flashed dm-verity then you "May not" have this issue but cannot say for sure.
If it is already too late for you then I think you need to flash stock via Odin, plenty of threads out there on where to find the firmware (SamMobile) and how to do it. Even a quick google of the error gave me plenty of results...
One thing I have read is that you may have to keep trying to get your phone into download mode as the timing is much stricter with this error message.
I've the same problem with my g935x blocked on FRP when ii treid to root if any one can help .plz
https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.
djluisbento said:
https://drive.google.com/file/d/0B4sLrKlVs0CPQTBaamduLXdNYW8/view?usp=sharing
wHEN THE PHONE INICIALIZES PUT THIS FILE IN A OTG pendrivve install and do the reset by the menu of the phone.
Click to expand...
Click to collapse
@djluisbento This method seems to be interesting. But would you please clarify more about it. How to install the apk file on official recovery? Or it's enough to have the pendrive connected? And if yes, when this step should take place, after flashing the official ROM or when?
I'm stuck in a boot loop into recovery mode with dm-verity error, and unfortunately I have the FRP locked, so I can't install TWRP to flash the no-dm-verity.zip file to skip it.
Appreciate your suggestions.
I have the same issure. stock firmware wont install either. im just stuck on the FRP screen, cant even get into recovery
Same issue here, please help
Everything was fine with rooting and installing TWRP. after that did a restart/ attempt to goto twrp recovery, from then the s7 edge is stuck at "Custom Binary Blocked By FRP" and doesnt boot. please help!!
Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Click to expand...
Click to collapse
just quoting from the original thread by jcadduono.
Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.
maxkento said:
Have you do a Wipe then Format Data.
Then flash the no-verity-opt-encrypt zip in TWRP
just quoting from the original thread by jcadduono.
Click to expand...
Click to collapse
taiseer999 said:
Had that problem with a brand new phone, just wanted to get into download mode to see if the phone was tampered with and boom, flash screen with the red warning, flashed stock KSA (phone original CSC) , worked and phone was formatted, another surprise was faced, google did not accept my gmail account, had to shut down phone for 72 hours as read in my google search for people encountering same issue, once the 72 hours passed I was able to sign in and using my phone again.
Click to expand...
Click to collapse
Yes, flashed both Zips in recovery. I used my regular google account during the initial set up. If i wait for 72 hours, will the phone just boot back online just fine? Still, how do i make sure it wont goto the FRP lock again while trying to reboot or reboot to TWRP?
Solved,
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.
anoopgopalpt said:
Flashed with stock firmware, logged in with same google account, rooted with TWRP, installed Zubi's sound mod. Made sure to keep the 'OEM Unlock' stay turned on.
Click to expand...
Click to collapse
Helo
But U did this after 72 hours?
There are several methods depending on firmware version installed on your phone. Basically you have to enter in your phone, launch chrome, install an app which gives you the possibility to log into your google account from chrome and not set-up program.
I used successfully the Bluetooth method. Search for with google. You need a bluetooth headset and follow the steps described on youtube.
BTW. My phone was brand new and I flashed different official samsung firmware ( csc). I had to change google password in between and that resulted in FRP lock....
The wait time is 24 hours as is stated in google docs from site
Sent from my SM-G935F using XDA-Developers mobile app
Hello I have a related problem, opened a new thread, but my thread was closed, because my problem is related to this one, but more complicated. I have the same problem with FRP lock as described here, I can turn on the download mode but it wont be recognized by my computer. I tried different usb cables, drivers, even computers, it wont help. I cant flash it with odin, smartswitch, kies, no matter what I try. If I go to recovery mode it says `dm-verity verification failed...`and if I choose `apply update from ADB or SD card` it says `update from external storage disabled`. I dont know what to do anymore Its a new phone
FRP Block - no Dev Tools enabled
Hey guys,
you're my last resort, I've tried everything I happened to come across, to no avail.
First off, I did something incredibly stupid, don't even ask me why, as I have no idea what the heck drove me to do this in the first place.
Anyways, I was using the stock ROM on my S7 Edge, not tweaked or tinkered with besides the usual CF-Auto_Root. It never caused any trouble whatsoever. But for no reason at all this morning I decided to disable USB debuggin and OEM unlock. A short while later I rebooted my phone, which ended up in "Custom binary blocked by FRP Lock".
I gave a factory reset a try, but that obviously didn't change a thing. So I went to sammobile.com and downloaded the latest official stock ROM for my device and tried flashing it with Odin. Unfortnately Odin always fails with "Complete(Write) operation failed.", which I assume is because I messed with the settings in dev mode.
Next stop: ADB. I've never used that thing before, but I thought I should possibly be able to get it done following a simple guide. Unfortunately ADB won't even list my device when typing "adb devices". It's just an empty list.
So please guys, give me some tipps on how I can bring my phone back to life.
(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!
Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.
Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.
JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously
Good luck.
Deleted
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.
sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you
Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082
Excellent news and a solution i havent found anywhere else yet!
Follow up from - https://forum.xda-developers.com/galaxy-s8/help/restore-imei-attempt-stock-rom-flash-t3802527
TL;DR attempted to re-root as soon as the bootloader unlocked. It all seemed to stick again, and got the big red message of doom again.
"Official Binaries Only" - Last time i was able to restore to at least switch on the phone to run down the rmm state timer to zero to flash again.
Tried the several methods of flashing through a locked bootloader (old BL file, quickly restart download mode and spam start on odin, etc) - literally nothing would allow me to flash anything that included the BL file. IMEI and baseband remained unknown. Phone went in drawer for a few days.
Just went and downloaded the latest XSA (Australia, Unbranded) build - https://www.sammobile.com/firmwares/galaxy-s8/SM-G950F/XSA/ and guess what boys and girls?
This sucker flashes straight away with Odin 3.13.1
It has completely restored my IMEI and baseband, i now have full Cell connectivity again, and its all back and working again. OEM unlock is still disabled, Samsung Pay still locked out which is fine, but otherwise, i have gone from brick to fully working Exynos S8 again.
TL;DR IF YOU HAVE ISSUES WITH A BRICKED PHONE BECAUSE IT WONT LET YOU FLASH ANY STOCK ROMS TRY THAT ONE.
Thanks for the replies to my other threads trying to help out with this. Much appreciated.
Peace out.
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
kratosjohn said:
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
Click to expand...
Click to collapse
Ive had a few cracks at this now but the date keeps resetting itself when you reset the phone despite having the automatic update option switched off.
Thanks for the info tho ill keep trying.
kratosjohn said:
For heads up for other after this, how to get OEM unlock to pop up again.
Go-to date and time, change the date to 8 days prior, disable automatic update of time.
Reboot phone and it may take a few tries, but OEM unlock should pop up again in developer settings.
Just went through all this without any help and it sucked lol. Thanks for making this thread for everyone.
Click to expand...
Click to collapse
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Ah I should have also mentioned I also did the same, flashed the same firmware when I was desperate and after some bit I also noticed prenormal change to official in download mode (the tell tale). I had OEM unlock on always, just was stuck in prenormal mode and couldn't flash anything.
To speed up the OEM unlock trial and error process do this as well:
1. After setting time/date back 8 days (and auto update time off). Go-to updates in settings, select manual update and check the server (it will error probably but that sets a check on their server to allow the RMM state to change next time it's connected properly).
2. Do this quite a few times, with reboot and constantly fighting the date auto update.
3. Flash the CRED firmware mentioned, boot it and setup once. Then reboot and go-to download mode.
4. You should see official as the RMM state now and you can happily OEM and flash away!
kratosjohn said:
Ah I should have also mentioned I also did the same, flashed the same firmware when I was desperate and after some bit I also noticed prenormal change to official in download mode (the tell tale). I had OEM unlock on always, just was stuck in prenormal mode and couldn't flash anything.
To speed up the OEM unlock trial and error process do this as well:
1. After setting time/date back 8 days (and auto update time off). Go-to updates in settings, select manual update and check the server (it will error probably but that sets a check on their server to allow the RMM state to change next time it's connected properly).
2. Do this quite a few times, with reboot and constantly fighting the date auto update.
3. Flash the CRED firmware mentioned, and reboot and go-to download mode.
4. You should see official as the RMM state now and you can happily OEM and flash away!
Click to expand...
Click to collapse
Have just flashed TWRP, used the Comsy version to be safe (3.13.1 fine for the stock rom flash) - I used comsy as it is mentioned in hte post OREO S8 update. It allows TWRP to be flashed but maybe thats whats breaking everything else. Ill try magisk next.
Fire up TWRP and enable system changes. FIRST - Advanced wipe and format system (Im 99% sure this is what screwed my last couple of roots), hit yes and do it. Reboot into recovery again.
Flash no-verity, then SuperSU (or your preferred root, i use Aroma installer first, THEN you have to flash the SuperSU binary with that)
Wipe dalvik etc. Reboot into system. As i type this its now in the 'Welcome' screen. Gimme a minute and ill check all is good.
UPDATE - Everything restored installed titanium backup root held. Rebooted phone aaaaaaaaand - "Only official released binaries are allowed to be flashed" - Back to square one. Will attempt same reflash now, but the root procedure kills everything. Back in download mode again. RMM State: Prenormal returned.
It is now succesfully flashing the stock rom in Odin 3.13.1 - Accidentally started it with Comsy and it DID NOT WORK. You MUST use the normal version to flash the rom im using.
Looks like we def have a stable way to refire up the phone again, and get around RMM state prenormal nice and quickly, so ill go ahead now and try and find whats going on with things breaking afterwards!
Thanks again guys.
Did nearly the same as you, dejavu.
I use magisk though. Be sure to flash a rom or kernel with RMM state fixed lol, or you'll be back here soon.
Funkmonkey said:
Have just flashed TWRP, used the Comsy version to be safe (3.13.1 fine for the stock rom flash)
Fire up TWRP and enable system changes. FIRST - Advanced wipe and format system (Im 99% sure this is what screwed my last couple of roots), hit yes and do it. Reboot into recovery again.
Flash no-verity, then SuperSU (or your preferred root, i use Aroma installer first, THEN you have to flash the SuperSU binary with that)
Wipe dalvik etc. Reboot into system. As i type this its now in the 'Welcome' screen. Gimme a minute and ill check all is good.
Click to expand...
Click to collapse
Someone should clean this up and get it stickied.
I imagine there are alot of users here with this same issue, after the CRED update we can't downgrade our bootloader, and in a panic you can get stuck here.
kratosjohn said:
Did nearly the same as you, dejavu.
I use magisk though. Be sure to flash a rom or kernel with RMM state fixed lol, or you'll be back here soon.
Looks like that wont be an issue any more to be honest this phone is now a backup thankfully so i can play around with it to my little hearts desire.
Im about to try the magisk install. SuperSU/Aroma definately breaking something somewhere. Or verity. I dont know but rooting the phone at the moment is killing it again.
Also, i have NOT lost IMEI or baseband this time. At the very least for Australian SN-G950F phones, this is a 100% flashable stock rom regardless of your RMM or phone status. I cannot say this for any other model in any other country on any other carrier, but this is all working for a carrier free Exynos S8.
Maybe y'all better archive the actual stock somewhere before someone realises theyve made a mistake somewhere and it gets pulled. Im definantly backing it up.
I just got that oem unlock trick to happen in 2 shutdown/restarts NOT reboots. BUT. I did NOT enable developer mode until i had disabled automatic time updates and turned the date back 8 days. The option came up instantly. Is something comparing a hardware clock deep in the system to a software clock in the os to and developer mode comparing something in between? Either way, on to reflash TWRP again now. This is a good day.
Click to expand...
Click to collapse
Hokay so - From a factory refresh, to the OEM unlock trick -
Flashing TWRP with 3.13.1 and allowing the phone to reboot - Phone will reboot as normal, TWRP doesnt stick. Shutdown and reboot into recovery gives you stock recovery.
Flashing but ensuring phone reboots directly into recovery gives you TWRP. A format data and reboot directly into twrp again lets me install no-verity.
- AFTER DOING THIS I AM GETTING THE RED LINE OF DEATH - Something in the system isnt letting the modifications stick.
Reflashing with the Home_CSC still seems to work as normal and i havent had to go through the welcome stuff this time...
Funkmonkey said:
Hokay so - From a factory refresh, to the OEM unlock trick -
Flashing TWRP with 3.13.1 and allowing the phone to reboot - Phone will reboot as normal, TWRP doesnt stick. Shutdown and reboot into recovery gives you stock recovery.
Flashing but ensuring phone reboots directly into recovery gives you TWRP. A format data and reboot directly into twrp again lets me install no-verity.
- AFTER DOING THIS I AM GETTING THE RED LINE OF DEATH - Something in the system isnt letting the modifications stick.
Reflashing with the Home_CSC still seems to work as normal and i havent had to go through the welcome stuff this time...
Click to expand...
Click to collapse
Have you found and used this after getting your phone setup right (w/twrp)?
I think you should flash magisk, then this after.
After I had this "panic" I flashed the custom rom I was aiming for (once RMM: Official). That rom has a kernel with the RMM state fixed/locked.
Maybe look for a custom kernel if you want root, I believe this is the fight we have to put up even on stock w/root.
Download the Australian stock rom and install it but do not recover IMEI or coverage. I think it's because my G950F (singlesim) cell phone thinks it's G950FD (double sim). This causes the cell phone to get confused and not recognize any imei or sim. Does anyone know how to fix it?
Funkmonkey said:
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Click to expand...
Click to collapse
Do we need to factory rest or just reboot phone after we change date?
Funkmonkey said:
Sunuva....
I havent been inside since i replied to you before. Gave up trying to fix that and was doing other things. Just reset both the s8 and s8+ to look at download mode... noticed the rmm flag was GONE rebooted and sure enough OEM Unlock is done.
You genius.
So - Anyone actuallly reading this -
Lost root, reflashed and cant install TWRP etc, "OFFICIAL BINARIES ONLY" crash, cant replace bootloader, missing IMEI/Unknown baseband -
TRY FLASHING XXU2CRED stock rom from 18/6/18 or later. This will flash despite a locked bootloader.
Once up and running set up the phone for use. Reboot as normal. Then turn off automatic time and date set date to 8 days prior, reset phone a couple of times. Get annoyed because you keep having to reset the date backwards. Reboot phone again and set automatic tin me and date again. Reboot. Bamf unlocked and completely restored SN-G950F.
Courtesy of Funkmonkey and @kratosjohn (the little legend)
Click to expand...
Click to collapse
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Smartphones13 said:
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Click to expand...
Click to collapse
I was stuck here too, flash the latest CRED firmware he linked.
Then boot it one time (setup til you see launcher).
Do the OEM unlock method.
You can follow the steps after if you want root.
I suggest magisk and a custom ROM, that had RMM state fixed (so you won't get locked again).
Good luck!
Smartphones13 said:
Can you please help me? so when you say reset phone you are talking about restarting it? I have tried this a few times and not working for me. My oem has always been unlocked, but still have prenormal
Click to expand...
Click to collapse
Sorry i missed your reply i hope you got it fixed if not post again and ill see if i can help. Ive definantly gotten that oem unlock trick working which is awesome but its fiddly. I dont think it works if you turn on flight mode and you have to let the phone fight you between 'no automatic date and time' and the network forcing the time.
Of course now i cant get the oem unlock trick working...
RE the dual sim issue... i think you would need the stock rom specific to your model try sammobile, see if there is a CRED release for your model. I cant guarantee it will work tho.
kratosjohn said:
I was stuck here too, flash the latest CRED firmware he linked.
Then boot it one time (setup til you see launcher).
Do the OEM unlock method.
You can follow the steps after if you want root.
I suggest magisk and a custom ROM, that had RMM state fixed (so you won't get locked again).
Good luck!
Click to expand...
Click to collapse
Thank you for your help, I am on the latest firmware now and into my Google and Samsung accounts. I am a little confused on the wording in the oem steps. I have tried it a bunch of times. Prenormal is still there, I already have the OEM unblocked, I can toggle OEM on and off but it doesn't change my rmm status. I am not sure what I am doing wrong.
Smartphones13 said:
Thank you for your help, I am on the latest firmware now and into my Google and Samsung accounts. I am a little confused on the wording in the oem steps. I have tried it a bunch of times. Prenormal is still there, I already have the OEM unblocked, I can toggle OEM on and off but it doesn't change my rmm status. I am not sure what I am doing wrong.
Click to expand...
Click to collapse
Thats exactly what im now struggling with. It absolutely did work twice but i cant get it to go now.
Heres the thing - both times i did it before, i would turn off automatic time and date and set the date backwards, then reboot the phone, when it reboots, automatic time and date were rechecked, and the date reset to now (hence the 'fighting with the date' comments) ... i think thats important, because now when i try it, automatic time and date stay OFF, the date does not reset, and i cant get the trick to work anymore. No amount of wifi/airplane/mobile data on/off seems to change owt.
If anyone reading has any ideas it would help.
Funkmonkey said:
Thats exactly what im now struggling with. It absolutely did work twice but i cant get it to go now.
Heres the thing - both times i did it before, i would turn off automatic time and date and set the date backwards, then reboot the phone, when it reboots, automatic time and date were rechecked, and the date reset to now (hence the 'fighting with the date' comments) ... i think thats important, because now when i try it, automatic time and date stay OFF, the date does not reset, and i cant get the trick to work anymore. No amount of wifi/airplane/mobile data on/off seems to change owt.
If anyone reading has any ideas it would help.
Click to expand...
Click to collapse
I see, so you suppose to set date back 8 days and turn off auto time and date and restart phone? When it comes back on to and set the date back to 8 days again? I thought you have to check the software? And then do those steps? So after I change the date back after that first restart, then what? Do I just turn OEM lock on and check download mode to see what the status is? I am not trying to be a pain o am just confused a little on the steps. Thank you for all your help
Smartphones13 said:
I see, so you suppose to set date back 8 days and turn off auto time and date and restart phone? When it comes back on to and set the date back to 8 days again? I thought you have to check the software? And then do those steps? So after I change the date back after that first restart, then what? Do I just turn OEM lock on and check download mode to see what the status is? I am not trying to be a pain o am just confused a little on the steps. Thank you for all your help
Click to expand...
Click to collapse
I think we might be looking at different issues.
This is to fix a semi bricked phone that has locked up its bootloader. In the past to resurrect a samsung all you had to do was flash twrp and your new rom but since Oreo some funkiness has been added to the system which only lets you flash a stock rom, (i.e. restoring a phone to factory settings and software) via ODIN/HEIMDALL then it locks up the bootloader for a week so you CANNOT flash anything into the phone that modifies the bootloader (i.e. TWRP OR *any* rom) until its timer runs out. This is most likely an anti theft feature esp with samsung and google pay use as it means there is no way to easily break into a stolen phone and use it as normal, and reflashing breaks all of the security features of the phone (e-fuse) - no knox no samsung or google pay no samsung pass as your device is insecure and could spoof false banking details etc.
The rom i linked to is important as it is a new AUSTRALIAN unbranded STOCK rom, that for some reason you can flash OVER a locked bootloader, meaning you can resurrect (australian at the very least) SN-G950F phones (exynos)
If you already have a working phone and can get to your developer settings then most of this thread is irrelevant to you.
Now - OEM unlock - You just bought a brand new galaxy from samsung (or youre me and you bought a MINT second hand one from cash converters for $700 less) - your phone is factory standard and schmicky. THE BOOTLOADER IS LOCKED. THE RMM STATE SHOULD NOT be triggered. If right now you went to flash something it would fail.
So you go to about phone - software information and you tap 'build number' seven times to unlock developer mode. Hit back twice and developer mode will be at the bottom of settings.
Click into this and you should see without swiping down 'OEM UNLOCK' - If you enable this, you can then reboot straight into download mode (power vol down and bixby) and flash twrp or whatever rom.
If you dont see this option, you either have a snapdragon model (youre **** outta luck permanently) or RMM is PRENORMAL and you either have to try the unlock trick(s) or leave your phone SWITCHED ON for 1 week and it will unlock itself.
The biggest issue at the moment is that i keep breaking something after i attempt to root so not sure whats happening there so use major caution.
Now as i said the trick posted above to unlock without having to wait a week (which i think youre asking about) im now not sure how it works because i cant get it to work any more.
Automatic time and date off, set date back 8 days, reset the phone. Do this a couple of times, then turn on automatic date and time again. HERE THERE BE ISSUES. When i first did it - i switch off time and date and change then reset, when the phone came on, auto date and time was on again. Turn off, change date, reset. Again, its back on. Turn off, change date, reset. Its back on. I give up and leave it, and notice later the option was available, so it worked. I broke the phone, reflashed again, did the trick in ONE reboot. Fcked something again, reflashed, now auto time and date stays off and the trick wont work so i cant help you with that until someone comes up with more info im sorry! Its a bit zarbis.
Im not going too nuts trying to fix it as i now have a fully working stock backup phone that sits on DeX plugged into my bedroom tv full time and im not into custom roms, root keeps breaking the phone, and ive sonce replaced it with a mint S8+ that im not even THINKING about considering rooting until its replaced maybe next year. Its not as easy to get around anymore and thankfully a) picasa and hangouts are no longer stock apps and can be banished and b) you can now disable all the other built in apps natively so its now a lot more bearable with a totally stock phone.
Hi All,
I'm trying to update the p9 lite VNS-L31C432B414 dual sim to the latest version B416.
The phone is always officially updated, but i tryed all 3 versions from firmware finder, with the *#*# 2846579#*# *
Select Project Menu > Software upgrade > SDcard upgrade method.
But when the phone restarts it begin to update and after a little progress it failed.
The same thing happens when i try it with the firmware finder app from playstore with erecovery, or dns method.
Any help would be appreciated, thanks!
Davidoff80
Davidoff80 said:
Hi All,
I'm trying to update the p9 lite VNS-L31C432B414 dual sim to the latest version B416.
The phone is always officially updated, but i tryed all 3 versions from firmware finder, with the *#*# 2846579#*# *
Select Project Menu > Software upgrade > SDcard upgrade method.
But when the phone restarts it begin to update and after a little progress it failed.
The same thing happens when i try it with the firmware finder app from playstore with erecovery, or dns method.
Any help would be appreciated, thanks!
Davidoff80
Click to expand...
Click to collapse
Firmware Finder
DNS/VPN method should be the best way to try this update.
The other only method that i know is to use Huawei Recovery Updater
but you should unlock the bootloader and flash a custom recovery first.
In the end it will be a bit difficult to re-lock the bootloader, never tried to do such a thing,
but you can keep it unlocked...
Good luck dude.
Cheers
Hi Dadditz,
Thank's for your response.
Last night i have tryed with a extra wifi router to change the dns number but even when the Firmware Finder app giving me the message that the B416 is registered for my phone, when booting in erecovery it installs the B414 FULL package again.
And with in the app proxy and dns method with firmware finder, the system update app from huawei gives me the sign that a update is ready to B416 with the release notes and all but when it starts it shows a checksum error or download fail.
I have registered the IMEI but do you know if it's maybe the problem with that its a dual sim so there a 2 IMEI numbers? or is the first one enough to register?
The tip for unlocking the bootloader i have searched on, but huawei has taking the unlock service down i understand, so the dc-unlocker2client program for 4 euro is the only option i think?
The main reason that i want to try the latest firmware is that people can't hear me good with this phone, i send the phone 2 times for repair and contacted the provider but the signal looks good.
Now i have factory reset the phone for the tenth time, i was thinking maybe the eset virusscanner interferes with the build in huawei/avast scanner but im not sure if that could cause it.
Thanks and have a nice day.
Hi all
I just unroot and unlock BL my phone yesterday. First i make downgrade (rollback 6.0) via dload method. Everything going very smooth and when my phone was version VNS-L31C432B160, then i'll get all newer updates via OTA (Finland), now my phone is B416
Davidoff80 said:
Hi Dadditz,
Thank's for your response.
Last night i have tryed with a extra wifi router to change the dns number but even when the Firmware Finder app giving me the message that the B416 is registered for my phone, when booting in erecovery it installs the B414 FULL package again.
And with in the app proxy and dns method with firmware finder, the system update app from huawei gives me the sign that a update is ready to B416 with the release notes and all but when it starts it shows a checksum error or download fail.
I have registered the IMEI but do you know if it's maybe the problem with that its a dual sim so there a 2 IMEI numbers? or is the first one enough to register?
The tip for unlocking the bootloader i have searched on, but huawei has taking the unlock service down i understand, so the dc-unlocker2client program for 4 euro is the only option i think?
The main reason that i want to try the latest firmware is that people can't hear me good with this phone, i send the phone 2 times for repair and contacted the provider but the signal looks good.
Now i have factory reset the phone for the tenth time, i was thinking maybe the eset virusscanner interferes with the build in huawei/avast scanner but im not sure if that could cause it.
Thanks and have a nice day.
Click to expand...
Click to collapse
Hey dude it's like you somehow downloaded B414 firmware and putted into
the internal memory or the SD card.
Check if you have that files and delete them, then try again with the update.
Don't know about your two IMEI, you have to check by yourself wich one would work...
About unlocking the bootloader, yes it is possible with the tip you wrote (dc-unlocker).
Before attempting to do anything try first with another sim and see if is the same as now
because if nothing changes maybe it's a hardware issue...
As suggested by @oltsuboy it's possible to downgrade to MM and re-upgrade
to N android version, you only need the correct packages..
I'm here to help you...
Have a good day..
Cheers
Hi guys,
I have tryed to downgrade to android 6, and that works, and then i get OTA to B370 and then B380 so i am android 7.0 again.
But now the OTA update find nothing, it stays on B380.
Before when i checked system update with HiSuite it says B414 is the latest official firmware, but now it says B380 is??
As far as i know i used only official updates with this phone, and i have wiped partion and system a lot of times.
And mostly there where 2 sim cards in it, i only put in SD card formatted first for the update.app
So i don't think B414 is floating somewhere, but i don't understand where it went wrong.
It's a non provider linked phone with a sim only abbo from the netherlands, i already asked a new sim card from the provider to test if the voice quality improves but it makes no difference.
I'm gonna wait a little maybe a update comes, when i put the B416 update on the sd card now and do force update VL+ VL- PW. the update fails after ten procent.
Maybe tommorow im gonna look to unlock the phone for 4 euro.
Thanks for the help!
Update: I have tried the DC Unlocker program.
And obtained the bootloader code, but what do do with it now?
Something says i did something wrong, because the options where:
Read unlock codes
Read bootloader code
Lock Bootloader
Erase Huawei ID
But no unlock bootloader, so i did read bootloader and copied the code.
Davidoff80 said:
Hi guys,
I have tryed to downgrade to android 6, and that works, and then i get OTA to B370 and then B380 so i am android 7.0 again.
But now the OTA update find nothing, it stays on B380.
Before when i checked system update with HiSuite it says B414 is the latest official firmware, but now it says B380 is??
As far as i know i used only official updates with this phone, and i have wiped partion and system a lot of times.
And mostly there where 2 sim cards in it, i only put in SD card formatted first for the update.app
So i don't think B414 is floating somewhere, but i don't understand where it went wrong.
It's a non provider linked phone with a sim only abbo from the netherlands, i already asked a new sim card from the provider to test if the voice quality improves but it makes no difference.
I'm gonna wait a little maybe a update comes, when i put the B416 update on the sd card now and do force update VL+ VL- PW. the update fails after ten procent.
Maybe tommorow im gonna look to unlock the phone for 4 euro.
Thanks for the help!
Update: I have tried the DC Unlocker program.
And obtained the bootloader code, but what do do with it now?
Something says i did something wrong, because the options where:
Read unlock codes
Read bootloader code
Lock Bootloader
Erase Huawei ID
But no unlock bootloader, so i did read bootloader and copied the code.
Click to expand...
Click to collapse
Hi dude,
DLOAD aka three button method won't anyway work on android 7 versions...
Sorry did you tried with your brother/sister/friend sim and seen if it's the same behaviour ? ( about the weird quality voice ).
Keep your unlocking code safe and before attempting any unlock re-try to update via Firmware Finder, checking this way...
Obviously turn on and connect with the WIFI...
After installing the app open it and add your variant (VNS-L31C432).
Find the firmware you're looking for (VNS-L31C432B416 FULLOTA-MF 2,2GB) and tap on it.
Now check the availability, register it with IMEI for the update and use the dns change / vpn method.
Once the vpn started, check repeatedly into the stock inbuild updater for a update and the B416 version should come. If will be disponible tap and download your update (should be approssimatively 2,2GB).
When it'll be at 5% pause it for a while and stop the vpn service.
Go back and re-active the download of the B416.
If all will go well you'll have the latest firmware.... :laugh:
Let me know how it went.
Cheers
Hi Dadditz,
No i don't have tryed another sim yet, the provider has said that if i give to more telephone numbers from the same provider they can do a scan for the quality.
So maybe that's something to try.
Later at night there came 3 more updates and the latest is now B414, so i am back on the same build
Yesterday i have unlocked the bootloader, with this guide: https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
Yes sorry i couldn't wait so i think let's try
When i was at the TWRP part, when i must reboot to recovery mode it stays on the screen that the phone was not safe.
So that part i still want to proceed.
So i rebooted and go to sleep.
I just have tryed your tips, but i see the same behaviour, the download fails, the extra wifi router which i changed the dns to was not more in my network, so i tryed without it.
With my own wifi router at home, they don't allow the change of the DNS, can that be the problem? or if you put a extra wifi router to it it's no problem?
I attached some screenshots, do you see that the buildnumber is displayed 2 times after a row?
I maybe think that's because i tryed to register both the IMEI? so maybe that's a problem?
Sorry i don't know how to attach the screenshot's below.
So i put them in a album called B414 with my profile, i hope you can see them, sorry this is the first forum i post on.
Thanks a have a nice day :good:
Davidoff80 said:
Hi Dadditz,
No i don't have tryed another sim yet, the provider has said that if i give to more telephone numbers from the same provider they can do a scan for the quality.
So maybe that's something to try.
Later at night there came 3 more updates and the latest is now B414, so i am back on the same build
Yesterday i have unlocked the bootloader, with this guide: https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
Yes sorry i couldn't wait so i think let's try
When i was at the TWRP part, when i must reboot to recovery mode it stays on the screen that the phone was not safe.
So that part i still want to proceed.
So i rebooted and go to sleep.
I just have tryed your tips, but i see the same behaviour, the download fails, the extra wifi router which i changed the dns to was not more in my network, so i tryed without it.
With my own wifi router at home, they don't allow the change of the DNS, can that be the problem? or if you put a extra wifi router to it it's no problem?
I attached some screenshots, do you see that the buildnumber is displayed 2 times after a row?
I maybe think that's because i tryed to register both the IMEI? so maybe that's a problem?
Sorry i don't know how to attach the screenshot's below.
So i put them in a album called B414 with my profile, i hope you can see them, sorry this is the first forum i post on.
Thanks a have a nice day :good:
Click to expand...
Click to collapse
Hey mate,
you're such as educated guy and i really apprecciate that !
Well... i saw inside your profile the B414 album and maybe i found the mistake...
damn ... seems you didn't read carefully what i wrote !!!
Look in previous post, you need the FULLOTA-MF package 2,2gb !!!
not the OTA-MF (incremental) one !!
Repeat again the procedure, register one only IMEI, hope this time
you'll be able to update correctly
Let me/other members know.. :fingers-crossed:
note: if the update will end correctly, it will re-lock the bootloader too.
Cheers
Hi Dadditz,
Thanks i didn't even finished my school so my english is not good, but i hope u understand.
I always tryed to install the full package mf B416 2.2gb but when i was testing it with the extra router it always shows a checksum error or download fail, tonight im gonna try that again, and let you know how it went and describe the steps that i tryed so maybe you can see where it goes wrong.
I also tryed the firmware finder windows version to register the IMEI, so maybe i make a mistake there.
This afternoon i was trying to attempt to proceed with the TWRP installation, but when i was booting with VL+ and power it won't go to recovery mode, on the xda forum i was reading more people with the same problem, the phone stays on booting
But the phone is working now so im glad i can whatsapp and watch netflix, so i will not try to go further with that, and focus on the B416 full update.
Thanks:good:
Davidoff80 said:
Hi Dadditz,
Thanks i didn't even finished my school so my english is not good, but i hope u understand.
I always tryed to install the full package mf B416 2.2gb but when i was testing it with the extra router it always shows a checksum error or download fail, tonight im gonna try that again, and let you know how it went and describe the steps that i tryed so maybe you can see where it goes wrong.
I also tryed the firmware finder windows version to register the IMEI, so maybe i make a mistake there.
Can you describe maybe how i can insert screenshots in a post?
When i try to insert a image in a post it is asking for a link, can i upload pictures at XDA or do i must use another image upload server?
This afternoon i was trying to attempt to proceed with the TWRP installation, but when i was booting with VL+ and power it won't go to recovery mode, on the xda forum i was reading more people with the same problem, the phone stays on booting
But the phone is working now so im glad i can whatsapp and watch netflix, so i will not try to go further with that, and focus on the B416 full update.
Thanks:good:
Click to expand...
Click to collapse
Dude,
sorry if i wrote something that someway hurted you,
english isn't my main language too...
Attachments aren't allowed to junior member, you need to post many times
in order to be authorized.
Let's go to the main problem...
If you want to try to flash the B416 version with the TWRP
you first need the correct TWRP version...
If you followed the link you posted above,
you tried to install the marshmallow version,
that's because it won't boot.
Your device are running android 7 ( nougat ) and you need a working recovery
in order to use Huawei Recovery Updater ( HuRu ) and flash that B416 firmware.
All files ( firmware apart ) you need are present on XDA, so just download and install
what i wrote you here.
Be sure you have installed Hisuite on your PC and it works.
Be sure you have enabled developer options then open it and
disable screen lock, enable oem-unlock and usb-debugging.
HERE to download and install Minimal ADB & Fastboot on your PC.
Connect the device to the PC, make sure PC recognize it allowing permissions if needed.
Then on the PC open a prompt (CMD) with admin rights and type "adb devices".
Below you should see your device as a serial of numbers and characters like
THIS screenshot. If that worked go next step.
Type "adb reboot bootloader" and it will reboot into fastboot/bootloader mode.
Now type "fastboot devices" and you should see your device as a serial of numbers and characters like
the screenshot i posted above except you'll see authorized/unauthorized section.
If your device are now authorized you're ready to go.
Type "fastboot reboot" and it will reboot into system.
HERE the link to download HassanMirza01's 3.1.1-1 EliteTWRP, flah it with fastboot command
( past a copy of TWRP into the adb & fastboot main folder )
( into fastboot mode ( see above ) type "fastboot fash recovery name_of_recovery_you_downloaded.img" )
When finished type "fastboot reboot recovery" or reboot with vol+ and power buttons.
Once you'll have a working TWRP installed reply me here
and i'll indicate the next steps.
note: with CMD prompt write without quotes " "
Cheers
Dadditz said:
Dude,
sorry if i wrote something that someway hurted you,
english isn't my main language too...
Attachments aren't allowed to junior member, you need to post many times
in order to be authorized.
Let's go to the main problem...
If you want to try to flash the B416 version with the TWRP
you first need the correct TWRP version...
If you followed the link you posted above,
you tried to install the marshmallow version,
that's because it won't boot.
Your device are running android 7 ( nougat ) and you need a working recovery
in order to use Huawei Recovery Updater ( HuRu ) and flash that B416 firmware.
All files ( firmware apart ) you need are present on XDA, so just download and install
what i wrote you here.
Be sure you have installed Hisuite on your PC and it works.
Be sure you have enabled developer options then open it and
disable screen lock, enable oem-unlock and usb-debugging.
HERE to download and install Minimal ADB & Fastboot on your PC.
Connect the device to the PC, make sure PC recognize it allowing permissions if needed.
Then on the PC open a prompt (CMD) with admin rights and type "adb devices".
Below you should see your device as a serial of numbers and characters like
THIS screenshot. If that worked go next step.
Type "adb reboot bootloader" and it will reboot into fastboot/bootloader mode.
Now type "fastboot devices" and you should see your device as a serial of numbers and characters like
the screenshot i posted above except you'll see authorized/unauthorized section.
If your device are now authorized you're ready to go.
Type "fastboot reboot" and it will reboot into system.
HERE the link to download HassanMirza01's 3.1.1-1 EliteTWRP, flah it with fastboot command
( past a copy of TWRP into the adb & fastboot main folder )
( into fastboot mode ( see above ) type "fastboot fash recovery name_of_recovery_you_downloaded.img" )
When finished type "fastboot reboot recovery" or reboot with vol+ and power buttons.
Once you'll have a working TWRP installed reply me here
and i'll indicate the next steps.
note: with CMD prompt write without quotes " "
Cheers
Click to expand...
Click to collapse
Hi Dadditz,
No problem mate , i'm new to this phone flashing and was insecure if my english was good enough to communicate on the xda forum.:good:
I was just to let you know that my second try with the second router is maybe succesful for the B416 FULL update part.
I now connected my pc to it and when i changed the DNS i changed the second DNS to 1.2.3.4 and when the firmware app says registered to this ip:......, i took that ip in the second router.
And then boot in to huawei Erecovery and now the B416 2gb is downloading, why the DNS and PROXY in the app only provide the 700mb update all the time even if i registred the 2gb version i don't know.
Maybe the DNS or ip setting had something to do with it, my understanding of network settings is limited.
The download is 42 procent after a hour but it's a old wifirouter.
So i was now about to ask if it's succeed i could undo the TWRP and lock the bootloader and just read your message, so i don't know if it hurt's anything if i let the update install
I wait and see :good:
edit: i did see you message that the update will relock the bootloader but i was asking because i was not sure because i messed up the TWRP part. edit
The update to B416 was succesfull! :good:
I haven't see the warning that the device isn't save when booting and Netflix appears in Google Play store again, so i guess i don't have do anything more to disable TWRP and locking the bootloader
Thanks for the help Dadditz and sorry that i was impatient to wait on your message, in the future i ask and wait patiently, but hey i didn't bricked the phone
If the voice quality improves i now must test, and the next step is to ask a network scan from the provider on 2 more telephone number in my town.
Thanks :good:
Davidoff80 said:
The update to B416 was succesfull! :good:
I haven't see the warning that the device isn't save when booting and Netflix appears in Google Play store again, so i guess i don't have do anything more to disable TWRP and locking the bootloader
Thanks for the help Dadditz and sorry that i was impatient to wait on your message, in the future i ask and wait patiently, but hey i didn't bricked the phone
If the voice quality improves i now must test, and the next step is to ask a network scan from the provider on 2 more telephone number in my town.
Thanks :good:
Click to expand...
Click to collapse
I suggested, you did. :good:
All is well that ends well.
If you had TWRP recovery installed,
you wouldn't be able to update with Firmware Finder,
as you would have needed stock recovery ...
And yes now the device is 100% stock.
Thanks for your feedback dude.
All the best
Sm-t590 on android 9 bought online and it's Google locked tried a few methods but cant seem to get around it...any help would be great.
https://drive.google.com/file/d/1XpSZC865lOFpf-7ClmUBu59XhWns-kQN/view?usp=sharing
mindlery said:
https://drive.google.com/file/d/1XpSZC865lOFpf-7ClmUBu59XhWns-kQN/view?usp=sharing
Click to expand...
Click to collapse
Hi! I've inherited a SM-T590 (among various other devices) from a deceased relative and try to figure out how to unblock them. I flashed the engineering image and turned on ADB but I don't see how to get rid of the FRP from there. What would be the next steps to disable the FRP entirely?
Thanks!
Once you flash the eng ROM, which you have, go into developer options and enable OEM unlock. Then factory reset within the settings. After that you can flash stock and frp will be disabled.
That worked! Thanks a lot!
Hello,
I know this thread is old. I have almost the same problem, except this is a familly kid who forget his lock screen password, and he used a dummy email adresse to create google account... And android version is 10, not 9.
So we did a factory reset from the recovery menu. But, now, we have to enter the google account, and of course, he doesn't remember.
I tried some (non trusted) tools as samsung frp tool, but not working. I tried a combination rom (i don't know if this is the good one), but in the download mode, the device tells me that :
frp is enabled, ignore pit download.
I tried to flash latest version 10 stock rom, but no change.
Is it worth to try to flash with a stock rom version 8 or 9 ? But to get these roms, i have to pay, but no garantie that this will work...
The device is not in debug mode, of course, and oem locked.
In the second post of this thread, there was a google drive link, but it's dead.
Do i have to put this galaxy tab a tm-t590 to the trash, or is there some hope to unlock it?
Finally did it.
I downgraded using odin in Android 9 using a stock rom, for 2.99$.
https://samfrew.com/fr/download/Galaxy__Tab__A__/gi1r/XEF/T590XXU3BSG3/T590OXM3BSG3/
I tried again samsung frp tool that I trust now .
I followed this video:
But the step *#0*# didn't work. So i tried to launch some apps from the web launcher.
I didn't remember exactly how I did it, but I succeded to create a new google account.
I restarted the device, and and i'm now in android. I activated debug mode and disabled oem mode.
I will try to flash something new and maybe alternative firmware.
I don't know which, but I will search here