Database Users

please help before I brick it

good evening
I am in a bit of tight spot
and before a srew it up (more) I wonder if you could help
I have a SM-G900V which is rooted and I had TWRP working just fine
I tried to flash a rom (project infinity) with aroma which freezed on installing aroma
the developer replied to me that the problem was from TWRP which had a bus and that I should instal CWP
I tried to install CWP on top of TWRP through ODIN and got a failure message
as of now I have neither TWRP or CWP or any rom flashed in mydevice
once I go into recovery mode and try to flash the previous rom that I had through the sdcard it says "footer is wrong signature fail" an reboots and gets stuck with no rom
just tried to reinstall TWRP through ODIN and got the failure message again
with the folowing message:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
please help

Hey man,
Sounds like you're in a bit of a pickle. Not sure if this would be a bit extreme, but I'd download the stock firmware and flash it through Odin. After that, reflash recovery and retry your rom.
I kind of see flashing back to stock a 'fail safe' in most cases, so it's always handy to have the stock firmware stored somewhere anyway. ?
Sent from my SM-G900I

..

fffft said:
Don't flash anything until someone discerns what went wrong..
being impatient at this point will put you at high risk of bricking or worse.
The phone boots normally up until the footer error?
What is the exact error message that you see?
What version of TWRP did you have?
Any backups? If so, do they include your baseband, EFS & PIT?
16 GB ROM?
Did you have a Verizon ROM when this happened?
Rooted?
.
Click to expand...
Click to collapse
let me start by thank you for your time!
I am a bit new to all this, I have flashed some roms in the past so I am also familiar with some stuff...
The phone doesn't boot it gets stuck like the attached picture, the OS doesn't start.
I don't see any message as it is stuck like I mentioned before, I just saw a message of "FAIL!" in Odin when I tried to install CWM on top of TWRP
my version of TWRP was 2.7.1.0
I had a backup on TWRP but as I dont see TWRP working anymore I dont know if its still available
my phone is 16GB
my SM-G900V is rooted and at the moment I had working perfectly SpeedROM v1 Rev2
if you would like to contact me through chat let me know, and again thank you very much!!

Try this
..

fffft said:
Okay, on the positive side there isn't anything to suggest that your bootloader is corrupt which would make this a lot harder. Probably the failed aroma install just messed your kernel up. But I don't want to recommend messing around with shortcut solutions e.g. just flashing the kernel that may or may not work, but would put you at unnecessary further risk.
The earlier suggestion to flash a full stock image is generally sound advice, but it does not apply to all situations. My questions were basically aimed at getting a sense of whether you have corrupted the bootloader or partitioning which has a bearing on how to best recover your phone.
First, I am assuming that you do not have the Dev (unlocked bootloader) version S5. If you have the Dev edition with the unlocked bootloader, do not proceed with the rest of this post until we discuss that.
On the assumption that you have a regular 16 GB Verizon SM-G900V S5, then I would like to see you Odin flash a full stock S5 Verizon image that has been rooted. Unfortunately I couldn't find anyone who has made and posted a stock rooted Verizon S5 image like that. I don't mean a stock rooted (custom) ROM.. I mean the full stock firmware image, including the bootloader, but rooted.
That's fine. The rooted part would just be a little extra insurance put against theoretical possible snags i.e. Knox issues. So I will suggest that you use Odin to flash a full stock Verizon S5 image, with an explicit partition table. Normally we don't touch the partition information (PIT) in Odin, but in your case we need to.
Download the files below from this thread
Unless you already have the file on your PC
Verizon S5 Retail Tar 4.4.2 NCG baseband and Mar 31 kernel
MD5: 699a949b57c771b00db9f3ed675c7a5e
NCG Pit
MD5: 3dd82f91a02c82e60e0a1f9964fdb5c0
Odin 3.09
MD5: 810ad286967d0a33881fd8181d35959f
You should thank the OP in that thread for collating the files that you need in one place.
Particularly that all important PIT file.
Start Odin and check these three boxes only: Auto reboot, Re-Partition, F. Reset Time
Choose the PIT file in the PIT window. Note that the PIT file needs to be extracted. Do not leave it zipped.
Choose the stock firmware tar.md5 file in the PDA window. The tar.md5 file needs to remain tarred i.e. tar.md5 or .tar
Put your phone into download mode. Ensure that your phone is off, remove the battery for a few seconds if necessary, then press volume down + home + power until you see the android robot screen come up. If it doesn't go into download mode, repeat these steps. And in the very unlikely event that you can't get into the download mode at all, stop and post that information
Connect your phone to your PC, Odin should say that it has detected your phone
Press start and let Odin flash your phone
Basically we are replacing all of the system files and assuring that your partitioning has not been corrupted
When Odin finishes with a success message your phone should be back to normal. Do a normal reboot to confirm
If you did not backup your phone, your user files in the /data partition might still be accessible
Decide if you wish to back them up or not. Do so if you need them. Then do a factory reset from the Settings menu
You will need to re-root and reinstall your apps, etc
If you run into any difficulties:
If the Odin write fails, note the error message and double check that your Odin settings were correct
Do not close Odin. Pull the battery from your phone for ten seconds.
Then replace the battery and go into download mode again (vol down + home + power)
Note whether Odin detects the phone
Then try flashing with Odin again. Note that you are not closing the Odin program if the first flash attempt fails
Odin can be a bit picky and it is not unheard of to have to reset the phone like this and run the session a second time
Odin is also picky about USB cables. If you still continued trouble, try a different USB cable and USB port
Don't despair if anything goes astray. There is almost always an alternate way to go about something.
Let us know your results so that we can (hopefully) celebrate. Or at least regroup.
.
Click to expand...
Click to collapse
you senior member??? pppffffffff
you should OWN this forum!!! thanx a lot for your extended time in this explanation mate, I will proceed and let you know

Agreed. I use a Dell and sometimes I have problems with odin using the front usb. I have to use the read usb and then no problems.

Hi Guys!!
I am back, back with my phone completely restored
A special THANX to fffff for your help!!

..

[Q] Re-partition System

Hi Guys
After trying out ART I realized that my System Partition went up from 5.5gb (Approx) to 7.2gb(Approx). At the time, I thought that as soon as I returned to Dalvik the System Partition would restore itself to normal but it has not.
I have done a lot of research but have not been able to work out how I can get my 1.5gb back now that i have returned to Dalvik full time.
I was wondering if there is a way to restore the system partition back to its stock size via re-partitioning or some other method. Is this what the Re-partition check box is for in Odin? If so, does this mean I need to flash a fresh stock rom and go from there?
Thanks in advance for any help!
Ed

Try re-flashing the stock firmware for your device via Odin with the PIT file.
You can obtain a PIT file from another device in its original state.

vndnguyen said:
Try re-flashing the stock firmware for your device via Odin with the PIT file.
You can obtain a PIT file from another device in its original state.
Click to expand...
Click to collapse
Thanks mate.
Will give it a try tonight.

Never use a pit file unless a firmware requires it.
The safest way is to use kies and do software restore from settings. It will flash the latest file for your S/N.

Just remember to add the pit file before you check the repartition box in Odin lol
I've heard of a few people being told to repartition, so they've just ticked the repartition box, but not added a pit file. If you do that, your phone is hard bricked, and only a JTAG box will fix it..
But it's a safe procedure if you do it properly, I've done it many times.

[Q] [Urgent] Can't unroot i337 MDL version via Odin

I have the AT&T Samsung Galaxy S4 i337 with MDL firmware and I needed to flash back to the stock ROM to bring to AT&T to fix an unlocking issue. I googled and found two top guides and a video where they all did the same thing so I thought it was safe to follow it--the guides did not specify that I needed to use a specfic firmware even if it's an AT&T variant (I assumed all AT&T variants had the same firmware and so did the guides apparently) so I think I used the wrong PDA on Odin 1.85 and now I get the issue "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I can no longer boot the device even to my custom ROM.
How do I fix this and then be able to flash back to stock so I can return it to AT&T? Some guides required a PIT file along with the PDA, some required both PIT and bootloader along with the PDA, and some just required PDA. Which ones am I required for my purpose and where do I get them? (I went to several sources after googling and they offered different ones).
Here's my Odin 3.07 output:
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
I will be checking back on this thread every chance I can get--this problem needs to be fixed by Monday because I desperately need it for work. Thank you!

I'm going to try to help you out. Bear in mind that I do not currently have this phone, and have very little actual experience with it.
I don't know you experience level. Did you perform a wipe data/factory reset from within recovery before the first time you flashed the stock firmware? If not, can you now enter recovery? If so, perform a wipe data/factory reset and see if the phone will then boot into system. If you can boot into recovery, but the wipe data/factory reset does not resolve the issue, please make note of the details of the recovery. It will tell you which version and we need to know that.
The MDL firmware is the second stock firmware distribution on the SGH-I337 (MDB was first) and was able to be cracked with Loki, by-passing the bootloader to allow installation of custom kernels. All subsequent stock firmware distributions, MF3, MK2, MLD, NB1, NC1, NI1, NJ4, or OC3 are locked, allowing only the stock kernel. So the first important question is what exactly did you flash onto the phone on the first try?
If you flashed the stock MDL firmware, it would be something like I337UCUAMDL, then your boot loader is still by-passable. However, if you flashed any of the subsequent stock distributions, then you will have a locked boot loader. So it's very important to know exactly what was done so far so that the recovery attempt can be done correctly.
I'll need this information, and anything else you can think to tell me, to give you further advice.

I have Soft-Bricked my s5, and tried almost everything. what to do?

Hello there xdadevelopers!
Today I made the brilliant descision to root my Samsung Galaxy S5 ( SM-G900F ) with a tool called KINGO ROOT.
Aware of the fact that there is a risk while rooting your phone, I procceed forward and now im left with a useless, expensive piece of electronic..
The tool i used said root was successfully installed, but my phone got stuck on the "samsung loading screen". after 40 minutes i decided to remove the battery and try again, same thing happend. I tried to use the "remove cahce/factory" setting ( or what ever its called) and that did not help. I have also tried to install the standard firmware through ODIN, but that failed over and over again at "img.ext4"..
I've also looked through this forum to find a solution, but nothing matches my problem it seems.
I really have no idea what to do anymore. :crying: I really hope someone could help me out with this problem, im sure there is others that would benefit from the same help aswell

Really should have done some research here on XDA first, but let's try and get you back up and running
You downloaded the stock ROM from sammobile .com for the G900F ?
Download and extract this PIT file
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Put the phone in Download Mode from a powered off state: (Volume Down & Home & Power) release when text appears, and hit Volume Up to enter download mode
Make sure samsung drivers are installed
Connect phone to PC > USB
Ensure ODIN 3.10.7 says connected and shows the COM port at the top
Add the PIT file to the PIT section
Add the ROM (Extracted to .MD5) to the AP or PDA section
Hit Start
--
All being well, it should begin the flashing process, and complete successfully, rebooting the phone back into Android
--
To root - extract and flash CF Auto Root for the G900F with ODIN in download mode again (Some G900Fs need a different method, but try this first)
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
Delete Kingo Root

*Detection* said:
Really should have done some research here on XDA first, but let's try and get you back up and running
You downloaded the stock ROM from sammobile .com for the G900F ?
Download and extract this PIT file
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Put the phone in Download Mode from a powered off state: (Volume Down & Home & Power) release when text appears, and hit Volume Up to enter download mode
Make sure samsung drivers are installed
Connect phone to PC > USB
Ensure ODIN 3.10.7 says connected and shows the COM port at the top
Add the PIT file to the PIT section
Add the ROM (Extracted to .MD5) to the AP or PDA section
Hit Start
--
All being well, it should begin the flashing process, and complete successfully, rebooting the phone back into Android
--
To root - extract and flash CF Auto Root for the G900F with ODIN in download mode again (Some G900Fs need a different method, but try this first)
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
Delete Kingo Root
Click to expand...
Click to collapse
Hello and thanks for answering that quickly!
I have now downloaded the stock rom from sammobile, along with the PIT file and ODIN 3.10.7 which you directed me to.
However I did not manage to get the flashing completed.
I added the .md5 file to the AP section in ODIN, and the PIT file was added to the PIT section. I left the options untouched ( Auto reboot ticked, re-partition ticked and F. reset time ticked aswell. everything else was unticked )
It did start the flashing and it kept going for a couple of minutes, but at the very end it failed at 99% completion this is the log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> NON-HLOS.bin
<ID:0/004> rpm.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea what this log means, but Im sure you do.
What did i do wrong? I tried it several times and i ended up with the same result..

I also had this problem but got out of it By downloading an earlier firmware for my phone. This is a tips guide I donei after I soft bricked due to me leaving the activation lock on! http://forum.xda-developers.com/galaxy-s5/general/read-flashing-rom-t3145703 hope this helps?

Along with the above ^^, when you put your phone in download mode, does is also say the model is the G900F ?
Some S5s have conflicting info about exactly which model they are, the section you need to trust, is download mode, double check it says G900F in download mode

*Detection* said:
Along with the above ^^, when you put your phone in download mode, does is also say the model is the G900F ?
Some S5s have conflicting info about exactly which model they are, the section you need to trust, is download mode, double check it says G900F in download mode
Click to expand...
Click to collapse
It says " Product name: SM-G900F "
deanr1977 said:
I also had this problem but got out of it By downloading an earlier firmware for my phone. This is a tips guide I donei after I soft bricked due to me leaving the activation lock on! http://forum.xda-developers.com/galaxy-s5/general/read-flashing-rom-t3145703 hope this helps?
Click to expand...
Click to collapse
Im downloading some earlier firmwares for my phone now. hope it works !

*Detection* said:
Along with the above ^^, when you put your phone in download mode, does is also say the model is the G900F ?
Some S5s have conflicting info about exactly which model they are, the section you need to trust, is download mode, double check it says G900F in download mode
Click to expand...
Click to collapse
I have now tried a 4 different firmwares, some older than the other to see if it would flash correctly.
I tried to flash only the firmware, then i tried firmware+ the PIT file you suggested in your first answer.
I also tried the PIT file all by itself, this worked , after that i tried the firmware, but that did not work..
I keep getting the same " FAIL!" over and over again when I try to flash the firmware.
At the end of the log it says " <ID:0/004> FAIL! (Size) " no matter what firmware i try to flash.
Any Ideas ?

deanr1977 said:
I also had this problem but got out of it By downloading an earlier firmware for my phone. This is a tips guide I donei after I soft bricked due to me leaving the activation lock on! http://forum.xda-developers.com/galaxy-s5/general/read-flashing-rom-t3145703 hope this helps?
Click to expand...
Click to collapse
Ive tried this several times now. but the end result is always the same : FAIL! (size)
Maybe I have done this so many times that my phone simply dont have enough space to successfully do a flash ?
Is it any way to wipe the phone clear maybe ?

babydash123 said:
I have now tried a 4 different firmwares, some older than the other to see if it would flash correctly.
I tried to flash only the firmware, then i tried firmware+ the PIT file you suggested in your first answer.
I also tried the PIT file all by itself, this worked , after that i tried the firmware, but that did not work..
I keep getting the same " FAIL!" over and over again when I try to flash the firmware.
At the end of the log it says " <ID:0/004> FAIL! (Size) " no matter what firmware i try to flash.
Any Ideas ?
Click to expand...
Click to collapse
You could try flashing a specific version of TWRP Recovery with ODIN, version TWRP 2.8.7.0
https://dl.twrp.me/klte/twrp-2.8.7.0-klte.img.tar
Flash from AP / PDA again, without extracting this time
If that flashes, try booting into recovery, Volume Up & Home & Power
If that is successful, try flashing a custom ROM from TWRP

*Detection* said:
You could try flashing a specific version of TWRP Recovery with ODIN, version TWRP 2.8.7.0
https://dl.twrp.me/klte/twrp-2.8.7.0-klte.img.tar
Flash from AP / PDA again, without extracting this time
If that flashes, try booting into recovery, Volume Up & Home & Power
If that is successful, try flashing a custom ROM from TWRP
Click to expand...
Click to collapse
TWRP 2.8.7.0 did flash without a problem. and now I did manage to boot into recovery - and now i have alot of options from Twam Win Recovery Project , and i guess im going in the right direction here hehe.
However I have no idea how to flash a custom ROM from TWRP. Do you mind walking me through the steps ?

you need to sideload a rom to your device or push it to sdcard

babydash123 said:
TWRP 2.8.7.0 did flash without a problem. and now I did manage to boot into recovery - and now i have alot of options from Twam Win Recovery Project , and i guess im going in the right direction here hehe.
However I have no idea how to flash a custom ROM from TWRP. Do you mind walking me through the steps ?
Click to expand...
Click to collapse
Great, OK well this is a popular ROM
http://forum.xda-developers.com/showthread.php?t=2732110
Instructions on how to install are on the main post
Basically copy the ROM to the MicroSD Card, and flash it using TWRP, but follow the instructions on this thread
Format / wipe everything apart from external SD from TWRP wipe menu
Go to the Install menu, and flash that ROM
Flash Gapps (Google apps) not sure if included, but not needed for flashing the ROM initially
Reboot, hopefully into the new ROM

*Detection* said:
Great, OK well this is a popular ROM
http://forum.xda-developers.com/showthread.php?t=2732110
Instructions on how to install are on the main post
Basically copy the ROM to the MicroSD Card, and flash it using TWRP, but follow the instructions on this thread
Format / wipe everything apart from external SD from TWRP wipe menu
Go to the Install menu, and flash that ROM
Flash Gapps (Google apps) not sure if included, but not needed for flashing the ROM initially
Reboot, hopefully into the new ROM
Click to expand...
Click to collapse
How am I suppose to copy the ROM to my MicroSD card ?

babydash123 said:
How am I suppose to copy the ROM to my MicroSD card ?
Click to expand...
Click to collapse
Put it in an adapter and put it in your PC, copy the ROM, put it back in your phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you don't have an adapter, you`ll have to buy one, they're cheap as chips - or find another device that works, you can use to copy the ROM to it with
You could try mounting the external SD (MicroSD) in TWRP, and plugging the phone into the PC and see if it is recognised, but I haven't tried that

*Detection* said:
Put it in an adapter and put it in your PC, copy the ROM, put it back in your phone
If you don't have an adapter, you`ll have to buy one, they're cheap as chips - or find another device that works, you can use to copy the ROM to it with
You could try mounting the external SD (MicroSD) in TWRP, and plugging the phone into the PC and see if it is recognised, but I haven't tried that
Click to expand...
Click to collapse
YOU are my hero, my saviour, my new idol. it actually worked!
I really cant thank you enough!
But I have some questions aswell hehe. This ROM that i downloaded installed. its not the "original" firmware that samsung provided right? what are the benefits of this VS the normal samsung one ?

babydash123 said:
YOU are my hero, my saviour, my new idol. it actually worked!
I really cant thank you enough!
But I have some questions aswell hehe. This ROM that i downloaded installed. its not the "original" firmware that samsung provided right? what are the benefits of this VS the normal samsung one ?
Click to expand...
Click to collapse
Pleased its working
No, that is not original firmware, it comes with benefits such as customisation, overclocking if the kernel allows, better speed, debloated (No crapware), more free storage, probably can install Xposed Framework for loads of tweaks and hacks and mods
Basically just about anything you want to change about your phone, you should be able to with a custom ROM, or at least request that change to the dev in that ROMs thread
But now that you have TWRP installed, you can pick and choose any custom ROM you want to try by using the same method you used to get this one installed
World is your oyster now

*Detection* said:
Pleased its working
No, that is not original firmware, it comes with benefits such as customisation, overclocking if the kernel allows, better speed, debloated (No crapware), more free storage, probably can install Xposed Framework for loads of tweaks and hacks and mods
Basically just about anything you want to change about your phone, you should be able to with a custom ROM, or at least request that change to the dev in that ROMs thread
But now that you have TWRP installed, you can pick and choose any custom ROM you want to try by using the same method you used to get this one installed
World is your oyster now
Click to expand...
Click to collapse
Ive now used it for a couple of days. and its just amazing! However I have encountered some problems with apps not working correctly. Snapchat wont load stories, and I cant watch any snapchat movies - but normal images works great when sending to my friends, which is weird. I get this errer " could not connect to server, please try again later". have tried to reinstall, clear cache etc but it seems it wont work. Ill read through the Xtrestolite thread and see if i find a solution now as Im a little more familiar with the forum
If I decide to install another ROM, is it any way that i can backup my whole phone ? so if i mess up again I can just reflash the one thats backed up, and all my apps and stuff will be just like it was ?

Yea sure, just boot back into TWRP, goto the 'Backup' section, and create a full Nandroid backup, tick all the boxes other than the caches
Make sure you have enough room on your external MicroSD (Select that as the backup location)
Once that is done, you can wipe, flash etc etc, play about with any ROM you like, and if and when you want to go back to your backup, just wipe the old one, and restore the backup from TWRP again, and your phone should be exactly the way it was when you backed it up once it finishes first boot
Very powerful recovery is TWRP

*Detection* said:
Yea sure, just boot back into TWRP, goto the 'Backup' section, and create a full Nandroid backup, tick all the boxes other than the caches
Make sure you have enough room on your external MicroSD (Select that as the backup location)
Once that is done, you can wipe, flash etc etc, play about with any ROM you like, and if and when you want to go back to your backup, just wipe the old one, and restore the backup from TWRP again, and your phone should be exactly the way it was when you backed it up once it finishes first boot
Very powerful recovery is TWRP
Click to expand...
Click to collapse
Thanks alot again!
Im experiencing some problems with some apps while using the Xtrestolite.
- Snapchat, wont load Stories at all, and wont open private video snaps, but normal pictures sent to my friends works. ( states that there was a problem connecting to the server, but when i use my Samsung S3 it works just fine )
- Dropbox - unable to preview any pictures and videoes
- larger apps/games that requires extra download ( like 3-500 MB ) wont open/load/download at all.
To me it seems that there is a problem with the phone writing temp files, such as snapschats, dropbox preview pictures.
Do you see any pattern here, maybe even some suggestions?

babydash123 said:
Thanks alot again!
Im experiencing some problems with some apps while using the Xtrestolite.
- Snapchat, wont load Stories at all, and wont open private video snaps, but normal pictures sent to my friends works. ( states that there was a problem connecting to the server, but when i use my Samsung S3 it works just fine )
- Dropbox - unable to preview any pictures and videoes
- larger apps/games that requires extra download ( like 3-500 MB ) wont open/load/download at all.
To me it seems that there is a problem with the phone writing temp files, such as snapschats, dropbox preview pictures.
Do you see any pattern here, maybe even some suggestions?
Click to expand...
Click to collapse
Did you do a FULL WIPE? Sounds like something went wrong, try SuperWipe, but make sure you have the Rom.zip on your external SD Card & not on you phone memory or you will not have nothing to flash & you will have to start mucking about. Hope this helps
Sent from my SM-G900F using Tapatalk

S7 Edge Boot Loop and Unable to Boot in Recovery (Stock ROM Unrooted)

Guys please help me out. I had a S7 edge which was just lying around for couple of months. I had taken out it's memory card and used in another phone (after format). Now I started S7 and it was very slow. I figured it was due to missing memory card as most apps were on card. I went into settings and set RESET in order to factory reset the device. It restarted slowly and since then it stuck in booth loop and does not turn off. I tried few things like booting into recovery by pressing Vol + Power and Home but nothing works. It shows error while going in recovery. Please see screens below. What do I need to do to restore it to original factory condition. It was totally stock and no modifications were made, I just wanted to factory reset it and ended up in this, don't want to to root it.
Also, is this condition called soft bricked ? Screenshot 4 tells me that recovery is also corrupted ?

Reflash with correct binary version firmware (the firmware which your phone was previously running) for your model in odin, if its not a hardware fault, it will get fixed.
Sent from my hero2lte using XDA Labs

shah22 said:
Reflash with correct binary version firmware (the firmware which your phone was previously running) for your model in odin, if its not a hardware fault, it will get fixed.
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
I think I missed 4th image of recovery black screen, uploaded it now. However, as I said, it was stock, I was also not trying to root or reflash anything. Still I need to flash firmware ? How will I find the version which I need to flash and what about OS, I will have to find and flash ROM too ?

lazers378 said:
I think I missed 4th image of recovery black screen, uploaded it now. However, as I said, it was stock, I was also not trying to root or reflash anything. Still I need to flash firmware ? How will I find the version which I need to flash and what about OS, I will have to find and flash ROM too ?
Click to expand...
Click to collapse
Yes, to get phone out of this condition, reflashing is an easy way, since I don't have phone in hand I can't guess the exact cause but reflashing mostly solves such issues (if its not a hardware fault)
Just to tell- you can only flash binaries with the same version number as the one which was running prior on your phone or higher. So if you don't know your current binary code, you would need to go in about section of your phone to see that info.
But since your phone won't boot anymore, just send a pic of your download mode (it has that info too) and tell me your csc/region and I will link you the correct binary firmware.
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
Yes, to get phone out of this condition, reflashing is an easy way, since I don't have phone in hand I can't guess the exact cause but reflashing mostly solves such issues (if its not a hardware fault)
Just to tell- you can only flash binaries with the same version number as the one which was running prior on your phone or higher. So if you don't know your current binary code, you would need to go in about section of your phone to see that info.
But since your phone won't boot anymore, just send a pic of your download mode (it has that info too) and tell me your csc/region and I will link you the correct binary firmware.
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
I will find the box (i have it somewhere) but mean while i have following information which was shown on download screen,
ODIN Mode
Product Name: SM-G935F
Current Binary: Samsung Official
System Status: Official
FRP Lock: Off
Warrant Void : 0 *(0x0000)
RP SWREV: B: 7 K: 5 S: 6
I dont remember if if had snapdragon or exynos. It is dual SIM.
Question: What about the softwares like samsung knows, health apps, will they be removed once if flash it with odin and then install a new OS. How to take back to just like stock

lazers378 said:
I will find the box (i have it somewhere) but mean while i have following information which was shown on download screen,
ODIN Mode
Product Name: SM-G935F
Current Binary: Samsung Official
System Status: Official
FRP Lock: Off
Warrant Void : 0 *(0x0000)
RP SWREV: B: 7 K: 5 S: 6
I dont remember if if had snapdragon or exynos. It is dual SIM.
Question: What about the softwares like samsung knows, health apps, will they be removed once if flash it with odin and then install a new OS. How to take back to just like stock
Click to expand...
Click to collapse
Yours is an exyos variant, not snapdragon.
No, flashing with odin doesn't effect anything if you just reflash a stock rom, only rooting/installing custom recovery will trigger knox and cause problems in samsung apps. Please read forums thorough because this is basic knowledge about flashing.
You don't install new os, you just reflash your stock rom. Your phone will be as it was previously. And please I say again, read forums for some general knowledge.
You can just tell me which country you're from or where you bought your phone from and I can link you to correct firmware.
And read flashing guides on odin before proceeding. And remember, we're just helping you get your phone fixed, no one is responsible if it gets in worse condition.
Sent from my hero2lte using XDA Labs

lazers378 said:
I will find the box (i have it somewhere) but mean while i have following information which was shown on download screen,
ODIN Mode
Product Name: SM-G935F
Current Binary: Samsung Official
System Status: Official
FRP Lock: Off
Warrant Void : 0 *(0x0000)
RP SWREV: B: 7 K: 5 S: 6
I dont remember if if had snapdragon or exynos. It is dual SIM.
Question: What about the softwares like samsung knows, health apps, will they be removed once if flash it with odin and then install a new OS. How to take back to just like stock
Click to expand...
Click to collapse
Ok the download mode says SM-G935F but the box says SM-G935FD. F is for global and FD is Southeast Asia and India
Phone is made in Vietnam but I am using it in Pakistan.
I tried using an older version of samsung smart switch -> Device emergency software recovery and initialization and it gives error that device does not support initializing. That was one way to go.

lazers378 said:
Ok the download mode says SM-G935F but the box says SM-G935FD. F is for global and FD is Southeast Asia and India
Phone is made in Vietnam but I am using it in Pakistan.
I tried using an older version of samsung smart switch -> Device emergency software recovery and initialization and it gives error that device does not support initializing. That was one way to go.
Click to expand...
Click to collapse
Well I asked where you 'bought' it, but assuming you bought it from pakistan, here's the link for your firmware :
https://samfw.com/firmware/SM-G935FD/PAK/G935FXXS7ESL6
Just to tell, smart switch doesn't work anymore for flashing, you'ill need to use odin. And F and FD both use same firmwares. Good luck
Sent from my Legendary Hero2LTE using Tapatalk

Thanks. Yes bought in Pakistan.

Ok, so it failed with message <ID:0/003> Complete(Write) operation failed.
I have the correct samsung drivers installed cause smart switch is also installed on that system. tried with odin version 3.13.1 as well as Odin3 v3.13.1_3B_Patched. Selected only AP file. It performs MD5 check and then tells the size and keeps on "SetupConnection..." and then fails with the message.
I remember USB debugging was already enabled on this phone.
What if my internal storage does not have enough storage to this 2+ GB file ? There is nothing i can do to make storage available since it wont boot.

lazers378 said:
Ok, so it failed with message <ID:0/003> Complete(Write) operation failed.
I have the correct samsung drivers installed cause smart switch is also installed on that system. tried with odin version 3.13.1 as well as Odin3 v3.13.1_3B_Patched. Selected only AP file. It performs MD5 check and then tells the size and keeps on "SetupConnection..." and then fails with the message.
I remember USB debugging was already enabled on this phone.
What if my internal storage does not have enough storage to this 2+ GB file ? There is nothing i can do to make storage available since it wont boot.
Click to expand...
Click to collapse
Make sure smart switch isn't running in background while flashing with odin.. also try the latest odin version. Links for it are posted in my essential guide below my signature.
Sent from my hero2lte using XDA Labs

Update: I downloaded files for Vietnam instead of Pakistan and maybe that made a difference. Now it starts initialization, goes till boot.img and then keeps on stuck on boot.img and ultimately fails with same write error. I tried odin 3.13, 3.13.1 and 3.14 but still same. I saw a video where people would extract AP file and then maybe rename and compress img file (have to see it completely). Any ideas ?
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3923 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

lazers378 said:
Update: I downloaded files for Vietnam instead of Pakistan and maybe that made a difference. Now it starts initialization, goes till boot.img and then keeps on stuck on boot.img and ultimately fails with same write error. I tried odin 3.13, 3.13.1 and 3.14 but still same. I saw a video where people would extract AP file and then maybe rename and compress img file (have to see it completely). Any ideas ?
Added!!
Removed!!
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1301)..
File analysis..
Total Binary size: 3923 M
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
NAND Write Start!!
SingleDownload.
boot.img
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Firmware region shouldn't make any difference as long as binary is correct (also you shouldn't flash different region firmware then your original purchase), also no need to compress any stock ap file because its intended for the same model.
I recommend to try with another pc and/or different usb cable/ports, delete and re-install samsung usb drivers and try with a different odin version (must be 3.13.1+)
Also reverify that you're flashing the firmware I provided. And you're not making any mistake in the process and smart switch isn't running in background processes..
If trying all above still gives failure, then you would need to get it checked in a repair shop, I fear it maybe some kind of hardware failure, sadly. But before you reach this conclusion try everything I mentioned in above paragraph. Good luck
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
Firmware region shouldn't make any difference as long as binary is correct (also you shouldn't flash different region firmware then your original purchase), also no need to compress any stock ap file because its intended for the same model.
I recommend to try with another pc and/or different usb cable/ports, delete and re-install samsung usb drivers and try with a different odin version (must be 3.13.1+)
Also reverify that you're flashing the firmware I provided. And you're not making any mistake in the process and smart switch isn't running in background processes..
If trying all above still gives failure, then you would need to get it checked in a repair shop, I fear it maybe some kind of hardware failure, sadly. But before you reach this conclusion try everything I mentioned in above paragraph. Good luck
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
One question, What if the phone does not have enough storage available ? The AP file is itself in GBs and even the recovery.image by itself is around 45 MB. What if there is not enough storage for this even, what will happen and what can be done in that scenario.
I am asking cause when all else failed, I only extracted the recovery lz4 file and then extracted to img file and only packed the recovery.img file to TAR file and tried to flash that. In this scenario it still failed with one striking difference. This time the progress bar on phone went to around 80 percent and in one case 100 percent, similarly the progress par on top on odin tool also went to 100 percent, but still the same error in the end. When i select the bigger AP file (containing sys and boot image), the progress bar on both remain at 0 percent. Could it be a space issue on phone and if yes then what ?

lazers378 said:
One question, What if the phone does not have enough storage available ? The AP file is itself in GBs and even the recovery.image by itself is around 45 MB. What if there is not enough storage for this even, what will happen and what can be done in that scenario.
I am asking cause when all else failed, I only extracted the recovery lz4 file and then extracted to img file and only packed the recovery.img file to TAR file and tried to flash that. In this scenario it still failed with one striking difference. This time the progress bar on phone went to around 80 percent and in one case 100 percent, similarly the progress par on top on odin tool also went to 100 percent, but still the same error in the end. When i select the bigger AP file (containing sys and boot image), the progress bar on both remain at 0 percent. Could it be a space issue on phone and if yes then what ?
Click to expand...
Click to collapse
No and yes,
Flashing via odin of the same model firmware, formats and wipes all storage and then rewrites the firmware.
The only case it doesn't wipes storage is when you select Home_CSC file, in that case it only flashes firmware while retaining your data.
It is recommended to always backup your data first and clean flash using normal CSC file (which wipes all storage) and NOT Home_CSC as it is known to cause issues.
But, even keeping your data and flashing via Home_CSC shouldn't prevent it from flashing even if your internal storage is not enough, because odin writes firmware to /system partition which has a fixed size according to the phone's hardware model. And it's a separate reserved partition not user manageable in unrooted phones. And free storage space shouldn't effect it in anyway.
Now, when could flash fail ?
1. You're using a wrong model firmware.
2. You're using a counterfeit/modified phone whose real hardware model is different then whats displayed.
3. Your phone's internal nand storage hardware got faulty and fails to write anything on it.
4. Odin's version is wrong.
5. Either your PC/Samsung usb drivers/Usb cables/Usb ports got some bugs/issues.
6. Smart switch is running in background and it is known to mess with odin flashing (often that's the culprit)
7. If you're rooted and have installed twrp recovery and you try to flash a custom rom which has /system partition size greater then that reserved for the phone's hardware model, it will fail at writing too (But this only applies to rooted users using twrp recovery to flash custom roms)
I hope I made it clear now.
Sent from my hero2lte using XDA Labs

shah22 said:
No and yes,
Flashing via odin of the same model firmware, formats and wipes all storage and then rewrites the firmware.
The only case it doesn't wipes storage is when you select Home_CSC file, in that case it only flashes firmware while retaining your data.
It is recommended to always backup your data first and clean flash using normal CSC file (which wipes all storage) and NOT Home_CSC as it is known to cause issues.
But, even keeping your data and flashing via Home_CSC shouldn't prevent it from flashing even if your internal storage is not enough, because odin writes firmware to /system partition which has a fixed size according to the phone's hardware model. And it's a separate reserved partition not user manageable in unrooted phones. And free storage space shouldn't effect it in anyway.
Now, when could flash fail ?
1. You're using a wrong model firmware.
2. You're using a counterfeit/modified phone whose real hardware model is different then whats displayed.
3. Your phone's internal nand storage hardware got faulty and fails to write anything on it.
4. Odin's version is wrong.
5. Either your PC/Samsung usb drivers/Usb cables/Usb ports got some bugs/issues.
6. Smart switch is running in background and it is known to mess with odin flashing (often that's the culprit)
7. If you're rooted and have installed twrp recovery and you try to flash a custom rom which has /system partition size greater then that reserved for the phone's hardware model, it will fail at writing too (But this only applies to rooted users using twrp recovery to flash custom roms)
I hope I made it clear now.
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
Thanks for all your help. One final thing. How can I get a PIT file specific to my phone model ? As per my understanding this PIT file also contains information about the phone internal memory.

lazers378 said:
Thanks for all your help. One final thing. How can I get a PIT file specific to my phone model ? As per my understanding this PIT file also contains information about the phone internal memory.
Click to expand...
Click to collapse
Pit file is already included in CSC file and so no need to get it separately as your phone will be already partitioned and formatted when using CSC file..
Note : Talking about CSC file NOT home_CSC... think i already explained it few posts earlier
Edit : what kind of internal memory information you're after? Pit file contains all android partitions info on your phone not just internal user-accessible storage .. some of those partitions shouldn't be messed with.
If you just want to see partitions info, you can use pit magic (search on xda) to view the information pit file contains

shah22 said:
Pit file is already included in CSC file and so no need to get it separately as your phone will be already partitioned and formatted when using CSC file..
Note : Talking about CSC file NOT home_CSC... think i already explained it few posts earlier
Click to expand...
Click to collapse
Cause I wanted to check by enabling the PIT option in Odin and see what happens. As I used Frija tool too to download firmware but it still fails. Now was thinking to use PIT to re-partition.