Related
I tried to do a factory reset on my A500 and ended up getting a "Unrecoverable bootloader error (0x19000008)" error. I read various threads and ended up at this very helpful thread and tried to flash an update but didn't get anything to work after trying several and then decided to flash a new ROM and the third version I tried seemed to take but now I get a password prompt from something that looks like the screenlock screen. I tried as many generic factory passwords as I could think of but can't get past the screen. Any hints as to what to do? I may try flashing a different version of the ROM to see that helps but I thought I would ask here first. If you're curious, the ROM file I used was Acer_A500_7.006.03_COM_GEN1.
Hi all,
My sister's Defy+ was stuck in bootloop, she tried the usual wipe cache, wipe data/factory reset but it didn't work. When I got it I tried it again and the data wipe never actually finished (the battery got empty after half an hour)
I charged it and tried to flash Retail French SBF from sbf.droid-developers.org / umts_jordanplus / list.php
After a while, during "Flashing Code Group 39", it just fails with the following error:
Code:
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xBFA54800 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=39
The phone is now stuck in bootloader with "code corrupt". I tried to flash it again but I always get the same error, with a different address but still in code group 39.
Do you know anything I could try ?
I am afraid it is a hardware failure -- to me it looks like the flash memory is corrupted or something, what do you guys think ?
Anne-Laure said:
Hi all,
My sister's Defy+ was stuck in bootloop, she tried the usual wipe cache, wipe data/factory reset but it didn't work. When I got it I tried it again and the data wipe never actually finished (the battery got empty after half an hour)
I charged it and tried to flash Retail French SBF from sbf.droid-developers.org / umts_jordanplus / list.php
After a while, during "Flashing Code Group 39", it just fails with the following error:
Code:
ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE003003F Address: 0xBFA54800 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=39
The phone is now stuck in bootloader with "code corrupt". I tried to flash it again but I always get the same error, with a different address but still in code group 39.
Do you know anything I could try ?
I am afraid it is a hardware failure -- to me it looks like the flash memory is corrupted or something, what do you guys think ?
Click to expand...
Click to collapse
Yes, I'm afraid you might be right, it is mostly a hardware failure.
Sent from my Nexus 7 using Tapatalk
Also before giving up, try flashing dfp231 (any region). I was getting this error on a different group, and that helped my phone get back to life. Otherwise, it's gone
Sent from my MB526 using Tapatalk 4
I checked and the one I tried to flash was actually dfp231... so I guess it's time to give up .
Thanks to both of you for your input, I wanted a second opinion before anouncing the bad news to my sister.
Anything I should do to mark the thread as answered ?
Not really, though you could change the thread title to add solved to it
Sent from my MB526 using Tapatalk 4
I remember similar faults when corrupting a Defy in the past, the reason was an inconsistant SBF.
In may case the SBF was curruptedt within the download network.
I tried one SBF, I tried a socond one, a third. Three or four SBFs were faulty.
You can try another download channel with another hardware and you can try several SBFs.
But always confirm a loaded battery, maybe your battery doesn't funtion very well and caused partition faults.
You may try a battery from a working Defy.
bianchifan said:
I remember similar faults when corrupting a Defy in the past, the reason was an inconsistant SBF.
In may case the SBF was curruptedt within the download network.
I tried one SBF, I tried a socond one, a third. Three or four SBFs were faulty.
You can try another download channel with another hardware and you can try several SBFs.
But always confirm a loaded battery, maybe your battery doesn't funtion very well and caused partition faults.
You may try a battery from a working Defy.
Click to expand...
Click to collapse
Code corrupt in bootloader usually means a damaged eMMC.
My Sons Moto X Play (UK sim free XT1562) this morning was showing a bootloader screen with "Start Up Failed" then "Your device didnt start up successfully. Use the Software Repair Assistamt on computer to repair your device". Then further down it says "hab check failed for boot / failed to verify hab image boot / failed to validate boot image". I'm guessing an update occured overnight which failed somehow?
Anyway, found a copy of the image file "X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip" and popped it on a SD card. Started boot loader, changed to recovery mode (stock UPD23.118-10), choose "apply update from sdcard" but get the message "Internal and external memory cannot be mounted". Trying it again gives "E:error opening /sdcard: Permission denied". Tried a wipe data/factory reset and wipe cache then repeat, but get the same messages.
I'm at a bit of a loss now. Any help would be much appreciated. Thanks
I would flash stock rom with RSDLite from the computer. If you dont want it to wipe everything make sure to edit the flashfile.xml and servicefile.xml and remove <step operation="erase" partition="userdata"/> and <step operation="getvar" var="max-sparse-size"/>
You will lose root and custom recovery after that though.
This message appears to me once and I reflashed with RSDLite, and until now, everything is ok
Thanks guys. Couldn't get RSDLite to recognise the phone though.
Then noticed that the image I'd downloaded was an older version (5.1.1) of android. Managed to find a new 6.0.1 version here. Still not working with flash from SDcard, but got reading about ADB, installed it and flashed each part of the rom seperately and now it works. Hooray!
Got another problem now - the phone is insisting on using a google account previously used on the phone. I know my sons email address and password which I verified works on the PC, but the phone just loops round and asks for it again each time I enter it. Doesn't seem to be an option to skip for now either - very weird!
bacus said:
Thanks guys. Couldn't get RSDLite to recognise the phone though.
Then noticed that the image I'd downloaded was an older version (5.1.1) of android. Managed to find a new 6.0.1 version here. Still not working with flash from SDcard, but got reading about ADB, installed it and flashed each part of the rom seperately and now it works. Hooray!
Got another problem now - the phone is insisting on using a google account previously used on the phone. I know my sons email address and password which I verified works on the PC, but the phone just loops round and asks for it again each time I enter it. Doesn't seem to be an option to skip for now either - very weird!
Click to expand...
Click to collapse
Make sure to install the moto x play drivers prior to opening RSDLite. You also have to be in download mode in the recovery options.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Clearly your rom has a problem explaining why the email security loops unless you arent connected to internet...
Did install the moto drivers when I tried RSDLite but no good. Anyway, that's not a problem now since I've got firmware on the phone and it now boots.
The issue with it not accepting the password for the google account has probably been made worse by me. In my frustration, I changed the google password. I've now read that after you do this, you have to wait 72 hours before you can re-auth a phone with that account. Shame. Will now wait and see what happens after that.
Thanks again
Update - after waiting the 72 hours, the phone has now accepted the new google account password so we're back in business.
My son was very happy to get his phone back.
Thanks all
(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
Samsung S8-SM-G950F custom binary blocked by FRP locked, i saw so many theards about this and i read them, and i still don't know what to do, so my question is if i download firmware with "SamFirm" and then use oddin will i get my phone unlocked from that ? As i had custom rom for year and half and today i got that error for the 1st time , also if the "SamFirm" is not good for that can someone give me link for firmware for my phone as updato and all other sites download soo slow at 15 kb/s and i can't use them it will take 20hours to download that (
Similar situation, I broke my S8 screen, so never got it fixed, and was recently without a laptop, so thought id use the S8 thru Dex, it all worked no probs, however, I used to unlock bootloaders to install custom firmware and os's but didnt think id done it on my S8 as it was still under warranty, so upon looking in the developer options, i saw that OEM Unlock was on, so i switched it off, not remembering rooting the phone, now i get same error it bootloops and says custom binary frp lock. Did u ever get yours sorted? I know my google account to login 2 it if i ever get the official rom back working, but trying odin and smartswitch restore im still stuck, just keeps failing, saying frp lock. Cant even get into recovefry mode to factory reset, didnt thiunk i had TWRP installed on it, but i must have. Anyway, if anyone can pls help me pls contact me here or at dcillusionz at proton dot me. Thanks.
PS - I tried downloading from SamFW and using Odin, but FAILED. Hoping u had some luck?