Database Users

[Q] Bricked and now in constant boot loop

To start I was coming from a HTC thunderbolt where I was flashing new roms every other day. To make a long story short a continuum fell in my lap so I sold my thunderbolt while I could still make some money on it.
So I decided to flash a rom on my continuum. I used one of the instructions here on xda, and in the middle of using odin my computer crashed. I tried reloading though odin but I get this error:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried every .tar file out there, but get the same error message above.
So now my phone is stuck is a bootloop with the following upon booting:
lfs done open fail
--wiping data...
formatting fota...
FOTA WIPE FAILED
Formatting data...
FORMATTING DATA FAILED
Formatting Cache...
FORMATTING CACHE FAILED
Formatting DBDATA...
DB data wipe failed
It does this then reboots to the samsung logo and repeats.
I can get into the downloading menu by holding down the volume and power. But I can not get into recovery, it goes through the same boot loop process when I try.
Any help would be very appreciated as I am without a phone.

Swing nto irc, in about 30 minutes. Just learned how to fix this one today... I'm looking o put the knowledge to use.
Channel is #samsung-continuum
Webchat.freenode.net
I'm at war with the world, cause i ain't never gonna sell my soul. No matter what, I can't be bought or sold. - Skillet

Txwolf1980 said:
Swing nto irc, in about 30 minutes. Just learned how to fix this one today... I'm looking o put the knowledge to use.
Channel is #samsung-continuum
Webchat.freenode.net
I'm at war with the world, cause i ain't never gonna sell my soul. No matter what, I can't be bought or sold. - Skillet
Click to expand...
Click to collapse
Thanks I am on my way there now.

samsung devices are almost impossible to brick if u can get to download mode just get the stock dL17 and .pit files and flash them via odin once u do that youll be back to stock

This is actually a pretty easy fix, haha... I would try to flash just the original recovery with heimdall that is usually the solution for that problem
Sent from my SCH-I400 using xda premium

Thanks everyone, txwolf was able to fix me up. Heimdall is the way to go.

heimdall help
can somebody walk me through this process as well? I am having a similar issue.

OFDorchester said:
can somebody walk me through this process as well? I am having a similar issue.
Click to expand...
Click to collapse
I'll probably be in irc the better part of the day. Let me know when you swing in there with a pm
I am not a fly, i am levitation. I represent an entire generation. - Niki Minaj

Please help
Followed instruction on flashing my continuum and got as far as flashing the phone using odin with ec07.tar. After I do the 3 finger reboot and I went to select update.zip (holding down softkeys) it told me it couldn't verify the zip file signature. Now when i boot it goes to the recovery utils and they softkeys no longer work to select update.zip. It also says update.zip gone on the bottom under #manual mode# please help I'm a noob.Right now I'm bricked -it just boots to system recovery and I can't select anything =(

deesnuts said:
Followed instruction on flashing my continuum and got as far as flashing the phone using odin with ec07.tar. After I do the 3 finger reboot and I went to select update.zip (holding down softkeys) it told me it couldn't verify the zip file signature. Now when i boot it goes to the recovery utils and they softkeys no longer work to select update.zip. It also says update.zip gone on the bottom under #manual mode# please help I'm a noob.Right now I'm bricked -it just boots to system recovery and I can't select anything =(
Click to expand...
Click to collapse
Your not bricked.
Flash stock via Odin.
Then reflash recovery.
And use update. Zip
Then flash whatever rom.
Sent from my SCH-I400 using xda premium

deesnuts said:
Followed instruction on flashing my continuum and got as far as flashing the phone using odin with ec07.tar. After I do the 3 finger reboot and I went to select update.zip (holding down softkeys) it told me it couldn't verify the zip file signature. Now when i boot it goes to the recovery utils and they softkeys no longer work to select update.zip. It also says update.zip gone on the bottom under #manual mode# please help I'm a noob.Right now I'm bricked -it just boots to system recovery and I can't select anything =(
Click to expand...
Click to collapse
Rereading your post on android furums, it's looking like you never got into cwm to begin with. Get a fresh copy of the cwm_adrynalyne_test4.tar, make sure the update.zip is on the root of your sd card, as per the tutorial, and reflash the test4 with odin. Make sure that nothing is checked except pda and autoreboot.

i9505 Softbrick Odin flash is failing [Resolved]

Hi All, I'm in desperate need of some help. For the past few days I've been going down the road of getting the latest Phoenix ROM working properly and I've been taking a step backwards with everything I've attempted, now I'm stuck at a soft-brick stage on my i9505
My current issue:
I can get into download mode. Not recovery, definitely not boot, only download mode.
Odin correctly identifies the phone but attempts to flash to the phone fail. It spits out the following:
Code:
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone then shows the progress bar completely stalled either at what looks like 99% for small writes (Like my attempt to flash TWRP), or at what looks like 1% (when I flash a full firmware). When I get home tonight I'll list the codes on the screen when it does it but I see a "START", and a "BBA" (I think), but I never get to the "END" command.
Has anyone experienced something similar?
What got me to this stage:
1. Flashed new Phoenix rom v10 upgrading from v9.4.
2. On sleep the cell dropped out constantly and so did WiFi so someone suggested I install a WiFi fix.
3. Installed the modem for XXUGNJ8 (I think). Combined package for LTE and GSM.
4. Every time the modem activated the phone had problems. Locked up when I open the phone app, reboot if someone called me, no sound when calls did "work", and the phone never sleeps and chews the battery after a simple text message.
5. Attempted to revert modem to XXUEMK4 (the other Galaxy S4 still on stock Android 4.3 had this modem). FAILED!
At this point my phone said the last firmware update failed and I was effectively in a softbrick scenario. I can still get into download mode.
6. Attempted to flash Optus carrier firmware 4.4.2 XXUGNH6. This failed, but the download screen changed now and says Samsung Official Firmware on it.
All other attempts to write to the phone have failed.
I've tried a different USB cable.
I've tried a different version of Odin.
I've tried flashing TWRP.
I tried installing Heimidall but have yet to get it working. (Visual studio runtime issues).
I installed Keis just to waste a bit of time.
I tried reinstalling drivers.
I just can't seem to write to the phone. Has anyone experienced anything similar and figured out a fix? When I get home tonight I'll post some pictures / screenshots of the errors I'm getting.
Cheers.

Are you trying to flash an older version of 4.4.2 that you had downloaded earlier?
Flash the LATEST 4.4.2 version for your phone.
"If someone helps, never forget to hit thanks ?"

Latest for my carrier? Or the latest version of stock there is?
By the way for the record here's some more info. Attached is a screenshot of my Odin after it fails. This was after attempting to install Philz recovery.
My phone has the following on the screen:
Code:
Odin MODE
Product Name: GT-i9505
Current Binary: Custom *note this said Samsung Official yesterday
System Status: Custom
Knox Kernel Lock: 0xfffffffc
Knox Warranty Void: 0xfffffffc
CSB-Config-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode: Enable
and then the bits from the actual download attempt:
Code:
START [224, 1448]
BAR [240,1440]
That's it. The progress bar is sitting at what looks like the 99% mark.

No sure if this will help but I solved my issues by running odin as admin and make sure usb debugging is ticked.

I don't see you tried a different usb port/different pc.
For using heimdall your don't need the frontend interface. You only need to make sure you use the correct drivers for heimdall and then use the terminal to flash the recovery.
"heimdall flash --recovery recovery.img --no-reboot" (it's case sensitive.)

Ok success.
I used the i9505 pit file and re-parition and with that I can successfully flash twrp or philz recovery. Which brought up an error saying non-official firmware detected.
I tried flashing XXUGNJ8 downloaded straight from Samfirmware but it failed. I tried it both with and without repartitioning.
So I tried twrp again and failed.
Then I tried XXUGNJ8 again and it failed but got all the way to the image stage.
I read about swapping cables, drivers, USB ports, well I did all of that to no avail.
Finally I took the entire mess to work and used a new computer there, fresh drivers, fresh everything, and everything worked just fine. I have no idea what's wrong with my computer, but it was not happy.
Thank god these phones are hard to brick. I'm willing to bet my USB connection dropped out while flashing which caused the issue to begin with.

[HELP] SM-G900F stuck in a recovery bootloop

Hi,
I'm from Singapore and I believe I have the international s5 (SM-G900F), at least that's what it says in download mode. My phone was running CM13 nightly and till last night it was working fine. Last night when I charged it, I woke up this morning and my battery was incredibly overheated. I changed my battery and tried booting, but now it gets stuck in a bootloop. I flashed stock 5.0 lollipop from sammobile via odin, but it still is stuck. I can boot perfectly into download mode with the android logo. Here are the details:
PRODUCT NAME: SM-G900F
CURRENT BINARY: Custom
System Status: Custom
Reactivation Lock (KK): OFF
KNOX WARRANTY LOCK: 0x1 (04)
QUALCOMM SECUREBOOT: ENABLE(CSB)
RP SWERV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I would really appreciate any help. Thanks!

Boot into recovery and factory reset, then try booting again
Sounds like the DATA partition got corrupted, or something installed to it did, flashing with ODIN doesn't wipe anything, so you'll still be bootlooped unless you wipe DATA / Factory Reset

When you go from cyanogenmod back to stock samsung firmware, a wipe data / factory reset is required in recovery or else the phone will be stuck in a boot loop or not boot up.

Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.

imbtrthanu said:
Hi, the problem is I cant access the recovery any more. Every time I hold power, volume up and the home button, it says recovery booting, warranty bit:kernel, kernel is not se android enforcing (the usual) but doesn't actually enter recovery.
Click to expand...
Click to collapse
Flash TWRP 3.0.0.0 with ODIN and wipe from there, then flash stock again
https://dl.twrp.me/klte/twrp-3.0.0-0-klte-klte.img.tar.html

Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.

Is there any other way I can do a wipe? Through adb or something? Or should I select a specific option in Odin (3.09) ? Like bootloader update, etc or something?

imbtrthanu said:
Hi I tried flashing twrp but that didn't work. It doesnt enter recovery, it still just restarts.
Click to expand...
Click to collapse
Uncheck "Auto Reboot" in ODIN, flash TWRP again, when it completes, disconnect USB and pull the battery to power off the phone
Replace the battery, and boot immediately into recovery with Vol Up & Home & Power

Hi that's not working as well. Should I reflash stock and then flash twrp in the way you suggested?

Try, but something seems wrong because you should be able to flash TWRP with ODIN
Have you got the drivers installed and does ODIN give you a COM port at the top when the phone is in download mode?
You are putting the phone in download mode to flash TWRP right?
Vol Down & Home & Power

Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up

imbtrthanu said:
Yes I'm using Odin 3.09. I'm flashing via the AP slot. I only have F Reset time checked. My S5 is definitely in downloading mode. Looks similar to this:
http://cdn.androidblog.gs/wp-content/uploads/2014/12/Samsung-Galaxy-S5-Stuck-In-Download-Mode.png
Also, I think the drivers may be the issue here. Could you advise me on how to check and how to fix it? Thanks so much! Also, yes, the COM port lights up
Click to expand...
Click to collapse
If the COM port lights up, the drivers are installed and working
Try ODIN 3.10.7, that's the latest version
Code:
https://mega.nz/#!vcIGmBTQ!Yr00OrGvUslQouU9E-zPf4SmpyVwL7mwIjeSG-0EAZg

Hi, that also didn't work. Any other advice?

Use a different PC / USB lead, everything you have tried should have worked fine on a G900F

Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so

imbtrthanu said:
Hi, I tried using a different PC and USB cable. Still nothing. Could it be because I flashed a different PIT file previously? There was a thread where someone suggested flashing a pit file, so
Click to expand...
Click to collapse
Didn't you flash the G900F PIT?
Flash this in the PIT section of ODIN along with the stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit first

Hi, I tried flashing the stock rom with the PIT you gave me but it gave me the following response:
<ID:0/005> FAIL! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas what I should do now? Also, which stock rom should I be flashing? KK or Lollipop?

I don't know what you've done to your phone, and from your main post, it is definitely a G900F if that is what it says in download mode
Which PIT did you flash the first time? And did it flash successfully?
Any stock ROM should work, but might as well go for Lollipop, I know 100% this one works
Code:
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
The only thing I can think of for now is to tell KIES3 to perform a firmware recovery
Code:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
If you already have KIES installed, remove it and try ODIN again, people have reported it interferes with ODIN
If not, install KIES3, go to the firmware recovery setting and see if it can fix your phone
Other than that, it looks like it's going to need someone with knowledge of manual partitioning via adb shell or something, if the phone can enter a mode the PC can use that with
EDIT - You are using a native PC running Windows 7 or later right? Not a mac running Windows? Macs don't install the drivers properly and fail

Yup I'm running Windows 10. I'll try KIES and see if that works!

Which PIT did you originally flash? And did it actually flash?

S7 Edge G935F // Faulty ODIN flash // Stuck in Bootloader [SOLVED]

Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"

Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.

fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?

Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!

Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.

SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.

Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?

suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.

Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally

suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.

Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model

SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?

Enable USB Debugging on Locked Phone

Phone stats:
6.0.1 (Samsung Galaxy S5)
G900VVRU2DQI2
Android Recovery (NO CWP, NO TWRP installed)
The Phone is NOT Rooted
USB Debugging was NOT turned on.
Password was forgotten and device is locked.
I have ADB installed on my PC.
End goal, I would like to be able to disable the lock screen without losing important data.
https://forum.xda-developers.com/sho....php?t=2620456
Method 7 wouldn't work as when trying to flash from a zip file in Android Recovery I received the following message (for multiple different zip files).
I get the following message:
E:footer is wrong
E: signature verification failed
Installation aborted.
My Next Approach:
Most methods for password reset require that USB Debugging be enabled, and I am unable to do that. I figured the best way to start again would be to go in and enable USB Debugging and then try some of the above mentioned Methods again...
I have tried downloading the firmware ,using ADB Automater to create a firmware file I can flash using AP in Odin 3. The process said it was successful ("PASSED") but the phone behaves the same and ADB debugging wasn't turned On.
I followed the following steps:
http://www.99mediasector.com/enable-usb-debugging-locked-phone-without-access-setting/
Any help, would be greatly appreciated. Maybe I'm missing a small step?

Does installing TWRP through download mode require usb debugging?
If not, install it, and then delete the .key files in the system folder.

tata811 said:
Phone stats:
6.0.1 (Samsung Galaxy S5)
G900VVRU2DQI2
Android Recovery (NO CWP, NO TWRP installed)
The Phone is NOT Rooted
USB Debugging was NOT turned on.
Password was forgotten and device is locked.
I have ADB installed on my PC.
End goal, I would like to be able to disable the lock screen without losing important data.
https://forum.xda-developers.com/sho....php?t=2620456
Method 7 wouldn't work as when trying to flash from a zip file in Android Recovery I received the following message (for multiple different zip files).
I get the following message:
E:footer is wrong
E: signature verification failed
Installation aborted.
My Next Approach:
Most methods for password reset require that USB Debugging be enabled, and I am unable to do that. I figured the best way to start again would be to go in and enable USB Debugging and then try some of the above mentioned Methods again...
I have tried downloading the firmware ,using ADB Automater to create a firmware file I can flash using AP in Odin 3. The process said it was successful ("PASSED") but the phone behaves the same and ADB debugging wasn't turned On.
I followed the following steps:
http://www.99mediasector.com/enable-usb-debugging-locked-phone-without-access-setting/
Any help, would be greatly appreciated. Maybe I'm missing a small step?
Click to expand...
Click to collapse
Have you solved your problem? I have the same problem..
Inviato dal mio SM-G950F utilizzando Tapatalk

Angel2k6 said:
Have you solved your problem? I have the same problem..
Inviato dal mio SM-G950F utilizzando Tapatalk
Click to expand...
Click to collapse
No, still no resolution. As I understand it, you need to have USB Debugging enabled in order to install TWRP.

You have to enable oem unlock to flash twrp afaik

kris_l said:
You have to enable oem unlock to flash twrp afaik
Click to expand...
Click to collapse
so the only way is to have access to the phone, than enable usb debugging? or there is another way yo oem unlock the s5?

tata811 said:
No, still no resolution. As I understand it, you need to have USB Debugging enabled in order to install TWRP.
Click to expand...
Click to collapse
i've succesfully managed to install twrp (just using odin 3.09, unchecked autoreboot, flashed last twrp and wait 3 mins and said "passed") .. so, i've unconnect the s5 from pc.. got out the battery to turn off the phone and without any reboot i've entered recovery and (after a backup) i've flashed a file ("rmpass.zip" or something similar) ..reboot without install any of twrp app (just click on "do not install") .. and done..

Angel2k6 said:
i've succesfully managed to install twrp (just using odin 3.09, unchecked autoreboot, flashed last twrp and wait 3 mins and said "passed") .. so, i've unconnect the s5 from pc.. got out the battery to turn off the phone and without any reboot i've entered recovery and (after a backup) i've flashed a file ("rmpass.zip" or something similar) ..reboot without install any of twrp app (just click on "do not install") .. and done..
Click to expand...
Click to collapse
Were you able to keep your data and info on the phone doing it this way?
Thanks,

Angel2k6 said:
i've succesfully managed to install twrp (just using odin 3.09, unchecked autoreboot, flashed last twrp and wait 3 mins and said "passed") .. so, i've unconnect the s5 from pc.. got out the battery to turn off the phone and without any reboot i've entered recovery and (after a backup) i've flashed a file ("rmpass.zip" or something similar) ..reboot without install any of twrp app (just click on "do not install") .. and done..
Click to expand...
Click to collapse
Okay, I have a SM-G900V (Verizon). I went here to download the tar file.
https://twrp.me/samsung/samsunggalaxys5qualcomm.html
I went into Odin, and disabled the auto reboot, but the file never shows as passed it always FAILS.

tata811 said:
Okay, I have a SM-G900V (Verizon). I went here to download the tar file.
https://twrp.me/samsung/samsunggalaxys5qualcomm.html
I went into Odin, and disabled the auto reboot, but the file never shows as passed it always FAILS.
Click to expand...
Click to collapse
Odin3 Log generated when trying to AP > TWRP:
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

If you can get into TWRP, try this?
"Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db"
Quoted from: https://forums.oneplus.net/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/
Also fully aware this is not for your specific device but nor was it when I used it on my Moto X Play.
It worked a treat
Also, are you experiencing any error codes or bootloader warnings/messages when in download/ODIN mode? (Top left)
If so report them back so people can potentially help.
It may be a mechanism that's put in place to stop flashing of files if lockscreen has been incorrectly disabled.
Not talking from experience here so take my words with a pinch of salt.
EDIT: Realised you may not be able to even get into TWRP...
Have a look round for people with similar problems, maybe someones built an unofficial version to solve the issue

CoreyOS said:
"Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db"
Quoted from: https://forums.oneplus.net/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/
Click to expand...
Click to collapse
This method WORKS on a locked bootloader, disabled USB debugging, forgotten pattern Xiaomi Redmi Note 3 (kenzo) with Qualcomm Snapdragon 650.
Simply:
Boot phone into bootloader / Fastboot Mode (Vol Down + Power)
Plug phone to PC using USB cable
Let Windows install drivers (make sure on latest Windows Update for fewer problems) or install drivers manually (Google "Xiaomi Drivers" or "Google Android Drivers")
Download "Portable Minimal ADB and Fastboot" and extract the archive to desktop or wherever using WinRAR or 7-Zip
Download the latest TWRP Recovery for your device, place it in the ADB folder and rename it to twrp.img
Open cmd.exe (Start button, type "cmd")
Navigate to your ADB folder ("cd YOUR_ADB_FOLDER")
Then type "fastboot devices" and "fastboot boot twrp.img"
The device will boot to TWRP, swipe to "Allow Modifications" (TWRP will ask on some devices) then go to Advanced>File Manager
From the file manager, go to data/system and delete these files: password.key, pattern.key, locksettings.db-wal, locksettings.db-shm, locksettings.db.
Go back to main TWRP screen. Go to Reboot>System to reboot the device. TWRP will ask to install itself to system app, chose Do Not Install.
The pattern will be gone.

Exactly TWRP is best
microdel said:
Does installing TWRP through download mode require usb debugging?
If not, install it, and then delete the .key files in the system folder.
Click to expand...
Click to collapse
Exactly TWRP is best, just make sure it doesn't require any usb debugging thing!