Develop Bugs

[STOCK] Partition corruption?

I've always been stock since it's a work phone but...
I was using it like normal and it randomly rebooted (it does this occasionally).
Halfway through the startup sequence it complained about encrypting the file system and needing a reboot or something.
So I click the little "reboot" button (the only option) and now it shows some green text at the top about being unable to find the boot screen png.
After that it boots into recovery where it shows a bunch of red error text below failing to mount /system, /cache, /data, etc...
So I got ODIN and the stock full ROM TAR file. I was able to boot into recovery and it's flashing FACTORYFS right now.
It's been flashing it for nearly 30 minutes without the progress bar moving.
I did not use the PIT file since the instructions with ODIN said it was unnecessary and put the TAR in the PDA slot.
Is it normal to take this long? Is there something else I should try?

Heres the ODIN log so far:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.FF18_CL663858_ROM_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!

Almost an hour and still no more bar movement.

Ok, I reset the phone... booted back into download mode and now I'm using the FF18 rooted one click.
I also changed USB cables for good measure.
<ID:0/006> 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/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.bin
<ID:0/006> hidden.img
<ID:0/006> boot.bin
<ID:0/006> Sbl.bin
<ID:0/006> param.lfs
<ID:0/006> cache.img
<ID:0/006> zImage
<ID:0/006> factoryfs.img
If flashes recovery, hidden, boot, Sbl, parak, cache, zImage... But still gets stuck on factoryfs.
:/

Although your first flash of the tar didn't need the pit file (see your log in post two, as is had the Pit for mapping), try flashing the individual stock tars in pc odin. (kernel, modem then rom)
If you want to have the pit, see the below thread.
Pit File Thread

What does the PIT do anyway?
Regardless... Now when I try to boot into download mode the blue light comes on, goes off momentarily, then comes back on and stays solid.
Black screen... No download mode...
:/

Damn man. Sorry to hear that.
And partition information table. What's/where..
Sent from my SPH-D710 using Xparent ICS Tapatalk 2

It's ok... Hopefully they will repair it or something.
If not I'll just swap back to my Epic 4G (the old sliding keyboard... oh yeah!) until November

PIT is a file that partitions the filesystem on your device. Think of it like a script version of something like partition magic or partition manager along those lines only its preset to the volume sizes, locations and names instead of you controlling those
Sent from my SPH-L900 using Xparent ICS Tapatalk 2

orb360 said:
It's ok... Hopefully they will repair it or something.
If not I'll just swap back to my Epic 4G (the old sliding keyboard... oh yeah!) until November
Click to expand...
Click to collapse
They should.. or send in to Samsung if under warranty and Sprint doesn't for some reason.
Sent from my SPH-L900 using Tapatalk 2

[Q] Help! stuck at splash screen!

Hello, I recently acquired a note 2 n7100 and I have been trying to restore it. However, every time I try using odin, it gives me the that I the frimware upgrade encountered an issue error. I used the pit, but now it goes to the splash screen but nothing after that... Just a black screen. What should I do? I have been at this for hours and I am losing my mind!

Anyone have a solution? I am dying here!
EDIT: I got to the screen with the android on it and the little spinning ball in him, but then it just keeps booting to the android figure with the spinning globe. Any ideas?

You ll need to be more specific with your problem. Did you aquire the phone in working state? What were you trying to do. What did you do to achieve that? What was the results. What did you do to compansate that ? Etc....
Sent from my GT-N7100 using xda app-developers app

Try rebooting recovery (vol up+home+power)
wipe cache and data
if not works, input full details with complete odin log
and which ROM and pit file you have used

dr.ketan said:
Try rebooting recovery (vol up+home+power)
wipe cache and data
if not works, input full details with complete odin log
and which ROM and pit file you have used
Click to expand...
Click to collapse
Hello doc! I used the n7100 16gb pit you made and I am using the united arab stock rom, that is the only one that allows me to get to the android screen instead of a black screen. I tried the recovery button combo but that did not let me get into recovery.
I can update with my odin log when I get home. It all passes, nothing fails... So I guess I really dont know what is wrong with it.

Ok, try flashing stock recovery (get from here )
if you can flash it correctly then try rebooting in recovery and wipe cache and data.
otherwise post log of odin

dr.ketan said:
Ok, try flashing stock recovery (get from here )
if you can flash it correctly then try rebooting in recovery and wipe cache and data.
otherwise post log of odin
Click to expand...
Click to collapse
Thank you! Where do I find the log? Also if I can get this working I will definitely donate!

minnieman said:
Thank you! Where do I find the log? Also if I can get this working I will definitely donate!
Click to expand...
Click to collapse
The area which shows getting pit for mapping in odin application and all.
Sent from my GT-N7100

Ok, I tried flashing the recovery but that didn't work. I tried flashing the stock rom via odin again and it came up with the connect to kies error until I put the 16gn pit in and now it is back to the android figure with the spinning orb... Enclosed is the log, any other ideas? I am at a loss for words here.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB5_N7100OJVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB5_N7100OJVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!

UPDATE: nevermind, it officially bricked so I am sending it in to be resurrected. Thanks for the help anyways doc!

Well it is flashing normally. Find a rom that will factory reset your phone.
Sent from my GT-N7100

[Q] Help please odin keeps failing

for some reason while trying to return to stock, odin keeps failing while trying to flash sboot.bin. any info on a work around would be helpful.

yavimaya401 said:
for some reason while trying to return to stock, odin keeps failing while trying to flash sboot.bin. any info on a work around would be helpful.
Click to expand...
Click to collapse
Write a radio from before ma7 so like a ljc or whatever radio and then try again ....
Sent from my SPH-L900 using Xparent BlueTapatalk 2

yavimaya401 said:
for some reason while trying to return to stock, odin keeps failing while trying to flash sboot.bin. any info on a work around would be helpful.
Click to expand...
Click to collapse
I'm having the exact same problem, I tried everything I could i'm still failing at the sboot.bin
Is this what you're screen looks like?
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-L900_L900VPALJ1_L900VPALJ1_L900SPTALJ1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.img
<ID:0/011> NAND Write Start!!
<ID:0/011> cache.img
<ID:0/011> hidden.img
<ID:0/011> modem.bin
<ID:0/011> param.bin
<ID:0/011> recovery.img
<ID:0/011> sboot.bin
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<ID:0/011> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Removed!!

Download an official release from samfirmware.con
Sent from my SPH-L900 using xda app-developers app

Sboot.bin won't downgrade the normal way from ma7 back to lk8/ljc etc. Garwynn has a work around for it somewhere in the dev section. I believe you need to use billards all in one revert to ljc with flash counter reset to downgrade the bootloader. This is why I didn't flash the bootloader with ma7 I just flashed the rom and modem. That way I wouldn't need to hassle around with downgrading it if I wanted to one click back to ljc instead of ma7
☆SoA: Son's of Android™☆
I like to break stuff!

Thanks for help and suggestions.
All systems are go on my phone now, I downloaded the stock file from Samsungupdates.com, then installed it thru Odin and it worked like a charm.
I did have to install it twice and it passed both time, It took to long the first time to reboot, so I deleted and did a factory reset then reinstalled the TAR.
I'm good to go

[Q] Soft Brick: NAND write failed, Missing system/build.prop

TLDR: My phone is softbricked, I've tried ODIN flashing Stock, I've tried flashing ROMS I've used before in TWRP... Nothin' workin'
fI was using Task's AOKP with no issues. Yesterday my phone was taking way longer to boot, but eventually made it, but my battery was draining like crazy... I rebooted my phone and it was stuck in boot loop. I tried reflashing the ROM/GAPPS but got an error during the GAPPS install that told me that system/build.prop was missing. I figured I should just try to revert to stock through ODIN and start from scratch. Here's what ODIN gives me when I try to flash the latest Samsung firmware:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? Are all soft-bricks eventually recoverable? I'm a phone addict...

Uggo said:
TLDR: My phone is softbricked, I've tried ODIN flashing Stock, I've tried flashing ROMS I've used before in TWRP... Nothin' workin'
fI was using Task's AOKP with no issues. Yesterday my phone was taking way longer to boot, but eventually made it, but my battery was draining like crazy... I rebooted my phone and it was stuck in boot loop. I tried reflashing the ROM/GAPPS but got an error during the GAPPS install that told me that system/build.prop was missing. I figured I should just try to revert to stock through ODIN and start from scratch. Here's what ODIN gives me when I try to flash the latest Samsung firmware:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? Are all soft-bricks eventually recoverable? I'm a phone addict...
Click to expand...
Click to collapse
The exact error I get when I try to flash GAPPS is:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error executing updater binary in zip '/external_sd/pa_gapps-stock-4.4.4-20140916-signed.zip
Error flashing zip '/external_sd/pa_gapps-stock
Updating partition details...
It's also worth noting that flashing the ROM (I'm going with the latest CM nightly) takes way too short of a time to complete

Sounds like your recovery may not like the binary used by the package.
For Odin though, do you have kids on your computer? If so uninstall it, reboot and try again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Sounds like your recovery may not like the binary used by the package.
For Odin though, do you have kids on your computer? If so uninstall it, reboot and try again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks, but it didn't help. I'm still getting the same problems.

Try a different version of twrp, or try cwm or philz recoveries too.
For that Odin flash, how big is the firmware you're trying to flash? I just noticed the "single download" line. Also, which version of Odin are you using and where are you putting the firmware? Looks like you might be putting it in the bootloader slot?
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Try a different version of twrp, or try cwm or philz recoveries too.
For that Odin flash, how big is the firmware you're trying to flash? I just noticed the "single download" line. Also, which version of Odin are you using and where are you putting the firmware? Looks like you might be putting it in the bootloader slot?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks for all the help. I'm not sure what the issue was, but I ended up solving it by using the latest CWM recovery to install a flashable version of stock. I'm not a huge fan of stock, but I'm up for an upgrade in January so I'm going to just have to cool it on the ROM front to ensure I have a working phone.

[Q] i317M bricked. Can't flash. Recovery mode not working.

I updated my i317M (Telus) via OTA and the next day it rebooted and went into boot loop.
I've tried flashing the phone with 4 different stock roms (from 4.1.2 to 4.4.2) but they all fail.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLBMA3_I317MOYABMA3_I317MVLBMA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried flashing Philz Touch recovery but that fails as well.
I've tried to boot it into recovery mode but it shows a dead Android with error logs like "E:failed to mount"
Help?

goyagoyago said:
I updated my i317M (Telus) via OTA and the next day it rebooted and went into boot loop.
I've tried flashing the phone with 4 different stock roms (from 4.1.2 to 4.4.2) but they all fail.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLBMA3_I317MOYABMA3_I317MVLBMA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried flashing Philz Touch recovery but that fails as well.
I've tried to boot it into recovery mode but it shows a dead Android with error logs like "E:failed to mount"
Help?
Click to expand...
Click to collapse
Try flashing with odin again but before flashing open the tar and remove the bootloader out of it.

Hi, thanks for the reply cnote.
Would the bootloader be sboot.bin or boot.img or both?
thanks again
edit: or rather, how do you remove the bootloader and remake the tar file?

goyagoyago said:
Hi, thanks for the reply cnote.
Would the bootloader be sboot.bin or boot.img or both?
thanks again
edit: or rather, how do you remove the bootloader and remake the tar file?
Click to expand...
Click to collapse
I believe it;s both. Just retrieve the tar file only.

sboot is the bootloader boot.img is the kernel .Have you tried the latest NH2 for your phone also maybe try using a pit file
The nh2 you will have to get from sammobile and the pit file can be found here http://forum.xda-developers.com/showthread.php?t=2609871
Also after odin is finished go into factory recovery and do a factory reset or its just going to sit at the boot screen

flashing pit file also gives an error :S