Related
I was trying to reset the whole device because I've uninstalled some stock apps by accident using Titanium backup. So I tried to recover my device through the recovery mode and start fresh. The stock apps was still gone...
So I figure I can use Odin3 v1.87 to flash the whole device with the firmware from http://www.sammobile.com/firmware/
I thought that would most likely get me back to the factory settings with everything and start fresh. But then Odin needs PDA, PHONE, CSC to run and the firmware only gave me one P6800OZSLP7_P6800ZSLP7_HOME.tar.md5 I was like how can I use this...
Then I found a guide in XDA how to separate it out into the three sections.
http://forum.xda-developers.com/showpost.php?p=24278264&postcount=9
I was like finally i can start this fresh. Things got worse.... every time it flashes to modem.bin it got stuck. It can never go through that part of the flashing. I then want to give up and use CWM to recover it back. Now i dont have 3g anymore on my tablet. Can someone teach me how to reset the whole thing back to stock?
As you can tell from the firmware i used is an HK Galaxy Tab 7.7 in ICS.
Thank you so much!
This is the P1000 forum not P6800.
[edit] Topic moved.
You can flash your firmware with mobin odin pro( on the play store)
You can flash with odin pc with pda' s choice
micger21 said:
You can flash your firmware with mobin odin pro( on the play store)
You can flash with odin pc with pda' s choice
Click to expand...
Click to collapse
I tried it with odin but it fails to write at the end.
naihochow said:
I tried it with odin but it fails to write at the end.
Click to expand...
Click to collapse
Basically this is what I get when I try to flash it with odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6800OZSLP7_P6800ZSLP7_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> boot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006> factoryfs.img
<ID:0/006> hidden.img
<ID:0/006> param.lfs
<ID:0/006> recovery.img
<ID:0/006> Sbl.bin
<ID:0/006> zImage
<ID:0/006> modem.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
use odin to flash it with rootloader mode,maybe can work
yangdliu said:
use odin to flash it with rootloader mode,maybe can work
Click to expand...
Click to collapse
you mean like checking the bootloader checkbox in odin?
btw do any of you guys know how to just flash the whole device back to factory settings other than using odin? does kies emergency firmware recovery work? do you guys know the device code?
naihochow said:
you mean like checking the bootloader checkbox in odin?
btw do any of you guys know how to just flash the whole device back to factory settings other than using odin? does kies emergency firmware recovery work? do you guys know the device code?
Click to expand...
Click to collapse
I realized what happened i must have click repartition earlier now my device only has like 44mb hence the reason why it wouldnt finish flashing b/c it ran out of space. Do any of you know how to repartition the device back to the correct size?
naihochow said:
I realized what happened i must have click repartition earlier now my device only has like 44mb hence the reason why it wouldnt finish flashing b/c it ran out of space. Do any of you know how to repartition the device back to the correct size?
Click to expand...
Click to collapse
You should use the correct .pit file and re-flash your device. Or you can also use adb shell and repartition yourself with parted utility. But that requires some unix expertise.
Pit file for 6800
https://www.box.com/shared/320b827fc7674a3ef5b9
Sent from my GT-P6800 using xda premium
kishd said:
Pit file for 6800
https://www.box.com/shared/320b827fc7674a3ef5b9
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Thanks, I made a very noobish mistake and didnt wipe the cache and i may have flashed the wrong partition file. But everything works now. Thanks for all you guys helping me out.
HEllo, IS so nessesary to flash Tab with PIT-file. I have the same problem just boot.bin not modem. CWM flashes as well? but my native (SEK) ROM from SM - not!
Hi All,
I've attempted to root my SM-900, using Odin 3.09 and followed all the usual steps.
Suddenly I got different coloured horizontal lines on screen and that probably means my attemp didn't go that well...
I've read I should go back to the original firmware using kies, and then try again.
So how do I restore the original firmware?
I have an image (.img) and understand I need samsung Kies.
Question: Do I use Kies or the new KIES3?
How to go from there?
Or is there another way to restore the firmware?
Thanks in advance!
I figured it out already....
I un-tar-red the recovery file. Leaving it as .tar solved the issue.
bricked
my tablet is stuck,tried different usb ports,different odins,different cables .gets stuck on set up connection,now all i get on screen is FIRMWARE UPGRADE ENCOUNTERED AN ISSUE
wolverinex66 said:
my tablet is stuck,tried different usb ports,different odins,different cables .gets stuck on set up connection,now all i get on screen is FIRMWARE UPGRADE ENCOUNTERED AN ISSUE
Click to expand...
Click to collapse
Please describe what is showing on tab's screen
Sent from my GT-S7562 using XDA Premium 4 mobile app
fixed
I was able to flash the stock recovery thanks
Had the same issues. Solved it by reinstalling the USB drivers. Via Kies 3, under the Tools menu. Worked perfectly after that. (Edit. ...for CFautoroot)
Sent from my SM-P900 using Tapatalk
Man that's gotta be a scary moment...
Sent from my SM-P900 using Tapatalk
Need advice
Frank_H said:
I figured it out already....
I un-tar-red the recovery file. Leaving it as .tar solved the issue.
Click to expand...
Click to collapse
I have the same problem... root failed with several colored line. and doesnt start anymore.
Can you explain to me what do you mean by "I un-tar-red the recovery file. Leaving it as .tar solved the issue." ?
Thank you
wilsto said:
I have the same problem... root failed with several colored line. and doesnt start anymore.
Can you explain to me what do you mean by "I un-tar-red the recovery file. Leaving it as .tar solved the issue." ?
Thank
Since the recovery image was downloaded as aan .tar file, which is a container file like .zip or.7z, I thought that I needed to unzip it.
You can mount the .tar file in Odin as it is, without unzipping it first.
You can find the recovery download location in the CF-root thread.
Click to expand...
Click to collapse
wilsto said:
I have the same problem... root failed with several colored line. and doesnt start anymore.
Can you explain to me what do you mean by "I un-tar-red the recovery file. Leaving it as .tar solved the issue." ?
Thank you
Click to expand...
Click to collapse
Mine did that after flashing a different firmware and trying to root. I solved it by first flashing the stock recovery in chainfires thread then rooting.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Duly.noted said:
Mine did that after flashing a different firmware and trying to root. I solved it by first flashing the stock recovery in chainfires thread then rooting.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep me too..
I'm having this same problem. I downloaded CF-Auto-Root-v1awifi-v1awifixx-smp900.zip from download.chainfire.eu. I extracted the zip file, leaving me with a tar.md5 file. I try to flash that file, and end up with multicolor bars across the screen, exactly like if the video card dies on a mobile.
Here's what Odin has output as of when the error occurs. It flashes up a big red failed in the upper left box.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I flashed the original recovery from http://forum.xda-developers.com/showpost.php?p=50492301&postcount=234 and got a working but unrooted tablet. And I flashed CF with both 3.09 and 3.07, with a flash back to stock before each. Same thing every time-picture of a dying video card, except display is fine once flashed back to stock. Pic of the display added, on the off chance it helps.
Install Kies 3, then go into the Tools menu and reinstall the USB drivers. Reboot. Try auto root again. Should work on the first try.
Sent from my SM-P900 using Tapatalk
dodo99x said:
Install Kies 3, then go into the Tools menu and reinstall the USB drivers. Reboot. Try auto root again. Should work on the first try.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I am having the same issue tried different computer with xp same result. Did you ever get it working or no? and if you did get working how?
---------- Post added at 08:39 AM ---------- Previous post was at 08:35 AM ----------
heldc said:
I'm having this same problem. I downloaded CF-Auto-Root-v1awifi-v1awifixx-smp900.zip from download.chainfire.eu. I extracted the zip file, leaving me with a tar.md5 file. I try to flash that file, and end up with multicolor bars across the screen, exactly like if the video card dies on a mobile.
Here's what Odin has output as of when the error occurs. It flashes up a big red failed in the upper left box.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I flashed the original recovery from http://forum.xda-developers.com/showpost.php?p=50492301&postcount=234 and got a working but unrooted tablet. And I flashed CF with both 3.09 and 3.07, with a flash back to stock before each. Same thing every time-picture of a dying video card, except display is fine once flashed back to stock. Pic of the display added, on the off chance it helps.
Click to expand...
Click to collapse
I am having the same issue tried different computer with xp same result. Did you ever get it working or no? and if you did get working how?
paulskerr said:
I am having the same issue tried different computer with xp same result. Did you ever get it working or no? and if you did get working how?
Click to expand...
Click to collapse
I did. I did the uninstaller for the USB drivers several times, with no luck. So finally I just deleted the Samsung folders in program files and program files x86. I did not reinstall Kies, just the USB drivers from samsung.com. I used odin 3.09, and it went flawlessly. Well, mostly-wifi took a *long* time to reconnect the first time after boot, but I'd also installed the update just before rooting, so dunno if it was the rooting or the update.
heldc said:
I did. I did the uninstaller for the USB drivers several times, with no luck. So finally I just deleted the Samsung folders in program files and program files x86. I did not reinstall Kies, just the USB drivers from samsung.com. I used odin 3.09, and it went flawlessly. Well, mostly-wifi took a *long* time to reconnect the first time after boot, but I'd also installed the update just before rooting, so dunno if it was the rooting or the update.
Click to expand...
Click to collapse
I finally go also. I did exactly what you did. Thank you
Frank_H said:
Hi All,
I have an image (.img) and understand I need samsung Kies.
Click to expand...
Click to collapse
Where do I get this image?
How many are remembering to unhide developer options and then select usb debugging? The moment I did that everything worked
Whwre did you find the USB drivers on samsung.com? When selecting the SM-P900 it does not offer any for download.
heldc said:
I'm having this same problem. I downloaded CF-Auto-Root-v1awifi-v1awifixx-smp900.zip from download.chainfire.eu. I extracted the zip file, leaving me with a tar.md5 file. I try to flash that file, and end up with multicolor bars across the screen, exactly like if the video card dies on a mobile.
Here's what Odin has output as of when the error occurs. It flashes up a big red failed in the upper left box.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I flashed the original recovery from http://forum.xda-developers.com/showpost.php?p=50492301&postcount=234 and got a working but unrooted tablet. And I flashed CF with both 3.09 and 3.07, with a flash back to stock before each. Same thing every time-picture of a dying video card, except display is fine once flashed back to stock. Pic of the display added, on the off chance it helps.
Click to expand...
Click to collapse
So this happened to me, and this is my first time rooting. I have the tar file for recovery. How do I proceed? I haven't unplugged my note pro, can I just put in the new file in the pda and start, or do I need to restart odin? Really kind of worried...
Hy guys.
I need help to flash my Samsung SM-G900F. I've downloaded an official Rom and I tried to to flash it whit Odin v3.09, but every time i get the same error at the end of the process and my phone display's the same message: "Some thing went wrong. Please connect to Keis " or something like that. Android vresion: G900FXX1ANG8. And another strange thing is that I can't enter the Recovery Mode, when I press volume up+power+home nothing happens. Please help me flash an official rom.
AlexTavi86 said:
Hy guys.
I need help to flash my Samsung SM-G900F. I've downloaded an official Rom and I tried to to flash it whit Odin v3.09, but every time i get the same error at the end of the process and my phone display's the same message: "Some thing went wrong. Please connect to Keis " or something like that. Android vresion: G900FXX1ANG8. And another strange thing is that I can't enter the Recovery Mode, when I press volume up+power+home nothing happens. Please help me flash an official rom.
Click to expand...
Click to collapse
so you are still able to get into download mode? also give us a picture of what ODIN says, you should try to connect it to kies which would install stock rom itself for you, ODIN is basically already inside kies and we ripped it from it.
Trozzul said:
so you are still able to get into download mode? also give us a picture of what ODIN says, you should try to connect it to kies which would install stock rom itself for you, ODIN is basically already inside kies and we ripped it from it.
Click to expand...
Click to collapse
Yes, I can still acces the dowload mode. Odin fails at the end of flashing after writing the modem the box at the top turns red and FAIL appear. The phone remains in download mode, and when I try to start it shows this message “Firmware Upgrade Encountered an Issue”
AlexTavi86 said:
Yes, I can still acces the dowload mode. Odin fails at the end of flashing after writing the modem the box at the top turns red and FAIL appear. The phone remains in download mode, and when I try to start it shows this message “Firmware Upgrade Encountered an Issue”
Click to expand...
Click to collapse
“Firmware Upgrade Encountered an Issue” yeah i would try to use kies then, are you sure you are using the correct firmware for your model? where did you get the firmware? i would recommend sammobile.com
Trozzul said:
“Firmware Upgrade Encountered an Issue” yeah i would try to use kies then, are you sure you are using the correct firmware for your model? where did you get the firmware? i would recommend sammobile.com
Click to expand...
Click to collapse
I tried Keis but it doesn't work. I have two software's one from sammobile and one from samsung-updates but it gives the same error.
AlexTavi86 said:
I tried Keis but it doesn't work. I have two software's one from sammobile and one from samsung-updates but it gives the same error.
Click to expand...
Click to collapse
can you tell me exactly what odin says in the little text box? copy paste please.
Trozzul said:
can you tell me exactly what odin says in the little text box? copy paste please.
Click to expand...
Click to collapse
I will try again and post here all the text.
Trozzul said:
can you tell me exactly what odin says in the little text box? copy paste please.
Click to expand...
Click to collapse
I can't post images. But here is the text form Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANH6_G900FPHN1ANH1_G900FXXU1ANG8_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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<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)
deepfreez86 said:
I can't post images. But here is the text form Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANH6_G900FPHN1ANH1_G900FXXU1ANG8_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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<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)
Click to expand...
Click to collapse
I get exacly the same problem.
@AlexTavi86 @deepfreez86 do you both remember the last Offical version of samsung firmware you had? (Android version) and the custom rom android version you had before? i need to know them both. also what version of windows? windows 8 might be the problem if thats whats up.
Trozzul said:
@AlexTavi86 @deepfreez86 do you both remember the last Offical version of samsung firmware you had? (Android version) and the custom rom android version you had before? i need to know them both. also what version of windows? windows 8 might be the problem if thats whats up.
Click to expand...
Click to collapse
Windows 7 x64
Android version: G900FXX1ANG8
AlexTavi86 said:
Windows 7 x64
Android version: G900FXX1ANG8
Click to expand...
Click to collapse
i meant the android version like :Kit kat 4.4. or 4.4.2/4.4.3/4.4.4, but i did try to search up G900FXX1ANG8 on sammobile and i didn't see any firmware with that name, i think you might be flashing the wrong firmware. can you pop the battery and tell me what the model number there?
Trozzul said:
i meant the android version like :Kit kat 4.4. or 4.4.2/4.4.3/4.4.4, but i did try to search up G900FXX1ANG8 on sammobile and i didn't see any firmware with that name, i think you might be flashing the wrong firmware. can you pop the battery and tell me what the model number there?
Click to expand...
Click to collapse
SM-G900F is the model number
G900F official firmware
AlexTavi86 said:
SM-G900F is the model number
Click to expand...
Click to collapse
Curious, what is your phone's country of origin (and service provider).
This can help identify the correct firmware.
r35gtr said:
Curious, what is your phone's country of origin (and service provider).
This can help identify the correct firmware.
Click to expand...
Click to collapse
I bought the phone from Spain an now i'm using it in Romania and the carrier is Orange Romania. When i tryed to reset ot from settings it remained stuck a boot loop.
Hello @ all
I got a new Samsung Note Edge SM-N915FY, with 4.4.4 Stock Rom from factory.
I install CWM recovery and have root. All went fine. I did a good Backup and so I can start to play with.
I try Mickey fast and famous Rom and works also good and I tried other stuff around. Some of them are good and some of the offered stuff is not booting, but no problem, it is only for playing around.
I install with Odin Lollipop 5.0.1 and give this Beta a try.
For me is important I can use XPosed Framework with a SkyModul with HDMI out, ( I know this is still in development) so I decide to go back to 4.4.4 Rom.
And this is not working. I can try to install the factory 4.4.4 rom or other stuff which works before and right now after install the Phone starts with sign "Samsung Note Edge" and shuts down again and so on. No Booting possible.
I tried the Factory Stock Rom with Odin and after downloading the ROM the Download Mode said "Filesize is too big"
Backup from 5.0.1 lollipop works everytime.
Any Ideas??
Regards
Panic Brothers
Panic Brothers said:
Hello @ all
I got a new Samsung Note Edge SM-N915FY, with 4.4.4 Stock Rom from factory.
I install CWM recovery and have root. All went fine. I did a good Backup and so I can start to play with.
I try Mickey fast and famous Rom and works also good and I tried other stuff around. Some of them are good and some of the offered stuff is not booting, but no problem, it is only for playing around.
I install with Odin Lollipop 5.0.1 and give this Beta a try.
For me is important I can use XPosed Framework with a SkyModul with HDMI out, ( I know this is still in development) so I decide to go back to 4.4.4 Rom.
And this is not working. I can try to install the factory 4.4.4 rom or other stuff which works before and right now after install the Phone starts with sign "Samsung Note Edge" and shuts down again and so on. No Booting possible.
I tried the Factory Stock Rom with Odin and after downloading the ROM the Download Mode said "Filesize is too big"
Backup from 5.0.1 lollipop works everytime.
Any Ideas??
Regards
Panic Brothers
Click to expand...
Click to collapse
ii know with other phones the upgrade was a one-way proposition. Once the new bootloader was flashed you were essentially stuck on the newer firmware. Downgrading, even official firmware, resulted in bootlooping... Note 3, S4 had this little "feature" and it caused mass hair pulling...
After couple tests I think the Note Edge has this kind of "feature"
No chance to get back to 4.4.4
it caused mass hair pulling...
Click to expand...
Click to collapse
No Hairs here since couple of years but for sure this is a feature for massive Hair pulling
I just try all OdIn Versions and still I get this Message.
Is there no chance to get a Downgrade to 4.4.4??
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<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! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
The Phone said:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image
Is it possible to get a valid PIT File for SM-SN915FY to download? I just searched around and it seems that other Note4 Owner had the same problem and it was solved with a valid PIT File.
Panic Brothers said:
I just try all OdIn Versions and still I get this Message.
Is there no chance to get a Downgrade to 4.4.4??
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<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! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
The Phone said:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image
Is it possible to get a valid PIT File for SM-SN915FY to download? I just searched around and it seems that other Note4 Owner had the same problem and it was solved with a valid PIT File.
Click to expand...
Click to collapse
I had exact the same problem with the galaxy note 4. When i put another custom rom on the phone with odin, it works good. Then i go back to the original rom till so far no problem.Then i put a new rom on it from outside my country. Then the problems starting, everytime i get exact the same problem as you have. The Phone said:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image. So after i can only download the official rom from my country. very strange. Till so far no problem with my Note Edge.
On NOTE 4 was possibility to downgrade STOCK ROM (from 5.x to 4x) with Mobile ODIN. Did You try this way? But I'm not sure, if Mobile ODIN is compatible with EDGE...
@phablet
Jumbo78 said:
On NOTE 4 was possibility to downgrade STOCK ROM (from 5.x to 4x) with Mobile ODIN. Did You try this way? But I'm not sure, if Mobile ODIN is compatible with EDGE...
@phablet
Click to expand...
Click to collapse
THX for this hint ... this I did not tried out but I just checked and load the mobile ODIN and the Edge is not supported in the actuall Version. Maybe later.
So it is only chance to wait for Xposed on Samsung Stock ROM :crying:
I'M back on 4.4.4 Now !!!!
This are the steps that worked on my rooted Edge SM-N915FY
- Boot to recovery mode wipe all Data/Cache
- Boot to download mode
- Start Odin 3.09 and load (AP) the original 4.4.4 from SamMobile (N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4)
- After press start all will be loaded and You get errormessage on screen Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image (Your Phone will not boot up now)
- Remove Battery and go again in the download mode
- Reset ODIN and load (AP) the custom recovery File (n915f-cwm-recovery-6.0.5.1)
After I load the recovery file the Phone starts again correct and shows 4.4.4 Version
Panic Brothers said:
I'M back on 4.4.4 Now !!!!
This are the steps that worked on my rooted Edge SM-N915FY
- Boot to recovery mode wipe all Data/Cache
- Boot to download mode
- Start Odin 3.09 and load (AP) the original 4.4.4 from SamMobile (N915FYXXU1ANK4_N915FYDBT1ANK1_N915FYXXU1ANK4)
- After press start all will be loaded and You get errormessage on screen Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image (Your Phone will not boot up now)
- Remove Battery and go again in the download mode
- Reset ODIN and load (AP) the custom recovery File (n915f-cwm-recovery-6.0.5.1)
After I load the recovery file the Phone starts again correct and shows 4.4.4 Version
Click to expand...
Click to collapse
my N915FY is already updated with lollipop (via KIES)
i never rooted the phone...
i want to go back to 4.4.4, is there any chance to do that? can i root now the phone anf follow the same steps that worked for you?
Goofy-Goober said:
my N915FY is already updated with lollipop (via KIES)
i never rooted the phone...
i want to go back to 4.4.4, is there any chance to do that? can i root now the phone anf follow the same steps that worked for you?
Click to expand...
Click to collapse
Sorry...but this I don't know. The first thing I do for my new devices is the "root" procedure and delete google apps and crapy stuff.
But why not? I think Odin and the Download Mode are possible without a rooting a device.
"Try and error" or maybe it works.
Good luck
*Edit*
you need a custom recovery like CWM oder TWRP and you must activate USB debugging in your developer options.
this is very strange that is happening to you guys, i have the tmobile version edge, used to have kitkat when i bought it, ROM from trinidad and tobago, decided to download lollipop from tmobile, did not like it, went back to trinidad and tobago kitkat, everything flashed ok, just a bootloop that resolved after i wiped cache
my phone has never been rooted, no custom recovery, no custom rom
hope this helps you out
I have 915g and to downgrade to 4.4.4 all i had to do was turn off auto reboot in odin, flash stock kitkat, boot into stock recovery, wipe data/cache and it booted.
I am trying to restore my phone to stock because only stock modified rom works with VR, but doesn't play nice with android wear.
So back to stock I go, however when I put it in download mode load up AP with the file, and hit start it says "FAIL!" I have team win installed and that is how I get to download mode. I only had Auto Reboot and F. Reset time selected as well.
Can anyone advise me on what I may be doing wrong?
Here 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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Download the stock firmware again the one you're using might be corrupt, also make sure drivers are installed
I have the drivers installed, also tried 2 firmwares, trying one more now.
Was following this guide:
http://www.droidviews.com/restore-t-mobile-galaxy-note-5-sm-n920t-to-stock-5-1-1-lollipop-firmware/
no firmware seems to be working. I also tried a new cable and a few ports. No change.
tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.
Are you using 3.10.7?
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Drachnem said:
tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.
Click to expand...
Click to collapse
How are you entering download mode?
Sent from my SM-N920T using Tapatalk
I've done it by using teamwin, also by holding pwr + home + volume down
guaneet said:
Are you using 3.10.7?
Click to expand...
Click to collapse
tried two...3.10.6, and 3.10.7
audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
You have to pay 10.00 to download the files
Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
Last time I checked you donated if you wanted, not forced to
Drachnem said:
Last time I checked you donated if you wanted, not forced to
Click to expand...
Click to collapse
Donated to try this fix, hope it works...
Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
As I recollect the fee is for the latest PAC, the others are free.
So it got further with the files and the pit file, but it didn't seem to fully work and I want to understand what may be wrong. It said failed in the first box but continued then the next box said pass.
The phone is now booted in setup mode but I wanted to understand what i may run into with this error or if I am fine...
Here is the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_TMB_N920TUVS2COKC_N920TTMB2COKC_CL5966591_QB7480468_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/004> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:1/004> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:1/004> File analysis..
<ID:1/004> SetupConnection..
<ID:0/005> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Set PIT file..
<ID:1/004> DO NOT TURN OFF TARGET!!
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> SingleDownload.
<ID:1/004> sboot.bin
<ID:1/004> NAND Write Start!!
<ID:1/004> param.bin
<ID:1/004> cm.bin
<ID:1/004> boot.img
<ID:1/004> recovery.img
<ID:1/004> system.img
<ID:0/005> Can't open the serial(COM) port.
<ID:1/004> modem.bin
<ID:1/004> cache.img
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)
audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
I don't often have an answer, but after being the benefactor of the knowledge and kindness of others through the years, I'm glad to help when I can.
Drachnem said:
I've done it by using teamwin, also by holding pwr + home + volume down
Click to expand...
Click to collapse
That's the problem you are using twrp enter download mode by volume up+pwr+home
Sent from my SM-N920T using Tapatalk
Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
Are you able to post the files here (if that doesn't violate an XDA rule)? Trying to get the old ones and they seems to be gone and really don't want to have to pay, but I guess I will if I have to.
Hey Guys,
Having an issue getting one of my Galaxy Note 5 (SM-N920T) back to stock. I am able to flash stock firmware in Odin 3.10.7 but the phone is bricked. When I flash any stock firmware the phone reboots and is stuck at the Note 5 Splash Screen. If i reboot into recovery and try to do the factory wipe it tells me it can't find "E:" and fails. Only way I can get the phone to boot is if I flash a rooted kernel. Then I noticed it says the Baseband is unknown in settings. I was going to try flashing through ADB but it tells me ADB is disabled, same with flashing from external storage. I cant even get it to reboot into bootloader. I am starting to think the phone needs IMEI repair..