Database Info

[Completed] Note 4 recovery capped

I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0

I figured it out
planb234 said:
I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
Click to expand...
Click to collapse
I fianlly figured out the deal with TWRP not flashing.
The change between file systems is what TWRP won't flash.
To flash into the new, the old, or back up property check the file type.
Ext 2, Ext 4, F2FS, etc ...
To get recovery to load install from odin with auto boot disabled, remove battery, than vol + - menu and power.
the steps below..
1. Power off (complete) boot to download.
2. Load Odin, uncheck auto reboot, PDA TWRP. after it installs pull battery to exit.
3. Boot to recovery - wipe- advanced wipe -Repairor Change File System - Check System (go thruough each)
4. Repair and change each to the file type you want to flash
5. repair and or change the files for the zip you are going to flash
6. you have done all the rest before ....

Issue resolved, thread closed, thanks.

[HELP] Soft-bricked Galaxy S6 G920F [Solved]

Hello everyone. So, let's start by explaining what I have did.
For a while I had the XtreStolite Odex 2.0 edition and I wanted to try out other ROM. I have factory reset-ed when I was installing the ROM using TWRP and I somehow managed to delete all the phone's internal stuff, but I can still boot to TWRP or download mode.
I have tried to flash stock firmware using Odin 3.10.6 ( running as administrator too ) and when it gets to sboot.bin it fails right away. I have tried using Samsung Smart Switch PC Software, tells me my device is unsupported. If I try to manually find my model using the S/N, the software fully downloads then gives me an error.
I have tried to ADB sideload from TWRP Advanced menu, whenever I want to flash for example xtrestolite odex zip ( named rom.zip for short ) it goes "serving:... 21%" and gets stuck. If I try to push a zip it says "error:closed". I am no big expert in ADB, I don't know how to install the latest version, and I can't download the full Android SDK because my internet is very slow. I had Bootloader and Modem 5.1.1
I am looking for a way to move the XtreStolite ROM zip into the phone's memory so I can boot to TWRP and install the ROM. I've seen something with OTG Cable and USB but I have no real knowledge of these. If it comes as a last resort, if someone could briefly explain me how would I manage to repair the phone using the OTG Cable and USB stick.
I also have a Nandroid Backup on my PC but I don't know how to move it to the phone's storage, because it's well, bricked. When I'm trying to copy files over Mount option in TWRP, it says that it cannot copy the file, the device may be disconnected.
I had Bootloader and Modem 5.1.1, also Windows 10. I can go back to 7 or 8.1 anytime it's needed.
Much appreciations.
EDIT: I actually repaired it by flashing a stock firmware downloaded from xda ( God bless you whoever linked the mega.co.nz stock fw link ) . Thread can be deleted.

You can also flash these via odin.
http://www.sammobile.com/firmwares/database/SM-G920F/

Bricked my T-Mobile Galaxy S7! [Fixed]

I've successfully rooted some of my previous androids, and currently have a rooted LG tablet, today I was trying to root my Galaxy S7 and I bricked it and can't unbrick it. I was following this guide devs-lab. com/root-samsung-galaxy-s7-s7-edge.html. Everything looked like it worked Odin said pass but my phone got stuck in a boot loop. I tried to root it with a tar.md5 from a different site but it fails. When I put it into recovery mode it shows the droid with a red caution sign and says "No command". From there I can get into the recovery menu and I've tried wiping the cache and that didn't work, I then tried the factory reset and that didn't work. I then downloaded the "Stock_DeOdexed_Debloated" ROM from here and tried to sideload it using adb but that fails saying "E:footer is wrong. E:Signature verification failed" I tried to install it from the SD card but get the same message. In the recovery menu it says "No Support SINGLE-SKU, Supported API:3, # MANUAL MODE #, -- Appling Multi-CSC..., Applied the CSC-code : TMB, Successfully applied multi-CSC., Successfully verify for dmverity hash tree". I'm currently downloading a stock firmware zip file I found on a different site. Is there any way I can unbrick it or is it permanently bricked? Any help would be greatly appreciated.
I flashed the files that were inside the zip using Odin and fixed it, I can’t figure out how to attach files so I've included links to the stock firmware I used as well as the version of Odin I used.
Stock firmware - downloadmirror. co/Urs/G930TUVU4APK1_G930TTMB4APK1_TMB.zip?download_token=20ae1b122f8519d6cfc69c0ef013b3f4c6856d15149bdc46bc3bcfecfb91ee1f
Odin - dropbox. com/s/go43hspdcbg9rld/Odin3_v3.12.5.rar?dl=0

It sounds like you have only soft bricked. As long as you flash the same firmware you had before everything got borked, it should work. Search the threads here at xda for links to the firmware you need or download from sammobile to be safe.
Also make sure you have the latest version of Odin, and all the Samsung drivers are installed. Hope this helps and good luck.

Bootloop

I've tried flashing the Unknown (XAS) version of the N920PVPS3DRD1 firmware coming from the N920PVPS3DRD1 Sprint (cdma) Through odin. It got stuck on finding pit file, so I closed odin and now my device is stuck in a bootloop. It stays on samsung galaxy note 5 screen then restarts and goes to TWRP. When I go into download mode it doesn't display any information in the top left. I have a backup of the sprint version which I have tried restoring to (I haven't wiped any data in fear of losing the backup) However I have the backup on my PC too which I should be able to send to the device using ADB. This didn't work. And it is still stuck in a bootloop. Does anyone know how to solve the issue? Thanks.

Download the correct 4 file package(I like Android File Host) and reflash using Odin. Edit the Odin .ini file to unlock all of the options, and then make sure you check the boxes that say nand wipe, phone efs clear, and bootloader update. Also extract the .pit file and insert that into the pit section. If it doesn't flash fully the first time, uncheck all of the boxes, reboot Odin mode, and flash again. This almost always solves my flashing issues.

S7 lost /efs and with it imei on bootloader v8 - chances of repair?

I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?

pr10dr said:
I have a s7 G930F here in Germany were i lost /efs due to a wrong backup overwrite.
The phone was on stock oreo with bootloader 8 now is on lineage but ofcourse mobile data / calling wont work without propper imei or efs.
I tried to flash a factory image / combined image but that does not go through with odin as the phone checks boot loader versions and i havent found an image with b8 as a bootloader version which would restore my/efs.
What are my options?
Click to expand...
Click to collapse
You just need to flash the latest G930F for Germany. The firmware code is DBT, it's unbranded so no netweork provider bloatware.
I've attached Samfirm tool. It gets the latest firmware straight from samsung servers version 8.
1. Unzip
2. Run application as admin
3. Check auto box
4. SM-G930F in Model box
4. DBT in Region box
5. Check Update
6. Wait to finish
7. Flash files with Odin
8. New Phone.

I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6

Alright i think i resolved part of the issue as follows:
* i flashed the complete stock firmware as described above
* After flash was done i rebooted again into download mode and installed TWRP as recovery via odin
* I then booted into TWRP and copied the "no-verity-opt-encrypt" in the latest version to the phone
* The zip of "no-verity-opt-encrypt" i then installed with TWRP.
The phone booted up. Factory Samsung Android works but the imei is still shown as empty / unknown.
Some guides suggest to flash a factory combination image but i can not find one for bootloader version 8 which is on my phone.

pr10dr said:
I followed your instructions and downloaded Firmware.
After flashing the phone reboots, displays that its erasing and after another reboot stops at the screen with the yellow exclamation mark and displaying "no command".
From there it only loops: reboot -> installing system recovery displayed for a very short time -> no command.
I since flashed multiple times and got the same result everytime. I flashed BL AP CP CSC (both CSC and home CSC yield same result) . Odin shows no errors.
Firmware is G930FXXS8ETC6
Click to expand...
Click to collapse
Yes sometimes this happens, try a different firmware like United Kingdom BTU.
Does Odin say Pass?
The updating and erasing screen is normal after flash just leave it.
Once the phone boots on BTU you can either change language to German or flash DBT again.
It's worth checking / reinstalling Samsung drivers. Use different USB port. Odin should be version 13.
As long as you can boot into download mode the problem is fixable.

Thanks for your advice.
I will try the BTU firmware later. Just to check we are on the right track: If i understand you correctly you are saying the lost imei will be "fixed" by installing either the BTU or DBT stock firmware via odin?

Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.

pr10dr said:
Installed the BTU version. Same behaviour. The System does not start and hangs on the same position.
Click to expand...
Click to collapse
OK it sounds like the BL info on the EFS is missing or corrupt.
Just try one more thing before trying to repair the EFS.
Flash firmware again with Odin but uncheck "auto reboot"
When passed in Odin disconnect phone.
Hold volume down+home+power. As soon as the screen goes back move your finger to volume up while still pressing home +power. You want to boot into system recovery. It may take a few attempts.
Once in system recovery, wipe data/factory reset and reboot phone.

Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated

pr10dr said:
Managed to get into Recovery directly after flash. But recovery is not loading fully and is outputting some text like :
HTML:
failed to open recovery_cause /No such file or directly)
Blob verificatio failed 255
failed setting up dirty targets
failed to mount /system (bad file descriptor)
...
Any chance of reparing the efs? Someone here messaged my and told me i would in PM that i might need to connect to some server software to get efs back.
Any idea is appreciated
Click to expand...
Click to collapse
Anyone offering money to fix or connect to a server is a scammer, stay clear.
To repair the EFS you have to get the stock firmware back on there or flash someone esle's EFS back up file. You can buy a damaged S7, install TWRP, back up the EFS to the SD card, put that sd card in your phone then restore the efs. Your phone will then take on the identity of the phone the EFS file came from. Effectively you will have a new IMEI number and mac address. As long as the donor phone is not registered on the network your phone will work fine. You cannot have two phones with the same IMEI registered on the network, both will be blocked and black listed. Obviously the donor phone must be exactly the same model as yours.
However the method below should be tried first.
The error with the text "failed to open recovery" means the phone cannot find the partition where the stock recovery file is located.
Now to solve this we can install TWRP with ODIN and that will provide a way to install the stock firmware in .zip format direct from the sd card using TWRP as the recovery method instead of the inbuilt stock recovery which cannot be found.
You should then be left with a phone which has a restored EFS with your original IMEI and other data with TWRP as the recovery tool.
Which ever method you choose TWRP must be installed first.