Nand write fail - odin - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi everyone,
I'm owner of a N9005 International on 5.0 with some problems of media processes. My Files doesn't open in your own app, only in File Explorer. Already Update and Hard Reset the same but problem remains.
I'll try to flash a custom ROM, but i found some problems to make root with CF Auto Root on my device. When i try do the root my odin (Versions 3.09 and 3.10) presents the message:
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
I have all drivers with Kies and Smartswitch.
USB Debbuging is on and Download Mode is on the screen.
I already reboot my PC, changed the cable and USB ports
Recently i Wipe and restore my Note3.
Anyone got an idea?
There's another way to do root without Odin?
Thanks!
Sorry for my poor english :/

Use supersu zip to root .
Its found under SEARCH or GOOGLE .

Have you tried flashing a stock ROM from sammobile.com? If flashing a stock ROM with Odin fails, try different USB ports and USB cables.

Use differnet ROMs, such as firmwares from sammobile , this sometimes happens when you have hardware failure , i mean cable . Try using another USB Cable , I had the same problem but no more with my current cable

audit13 said:
Have you tried flashing a stock ROM from sammobile.com? If flashing a stock ROM with Odin fails, try different USB ports and USB cables.
Click to expand...
Click to collapse
Huy Hyner said:
Use differnet ROMs, such as firmwares from sammobile , this sometimes happens when you have hardware failure , i mean cable . Try using another USB Cable , I had the same problem but no more with my current cable
Click to expand...
Click to collapse
Tks Guys,
Already tryi this. With no sucess,
but, reading some topics here in xda, one comment called my atention. I disabled the Reativation Lock and works. I don't know if this really was the problem. But, it works. Tks a lot. :good:

I had a note 3 bricked by erasing NAND in Odin. eventually I lost access to my phone and I was not able to download the firmware by odin through single file method.
but I searched for tried for 12 hours and found note 3 stock roms here.
You can do that un-brick to stock rom back by finding individually all essential file [AP, CSC, BL, CP] and installing by the odin.
I am very new to android world so if it look dumb to you. ignore. Thumbs for hard work.

Related

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] Bricked SM-G900W8 looking for partition file

Hello, I am relatively inexperienced when it comes to flashing and have managed to brick my s5(rogers(SM-G900W8)canadian). I have looked around and it seems as though in order to get my phone to work I need a pit file for my phone. Problem is, I can't find one. If anyone could help it would be greatly appreciated. Thanks. by the way I have rooted and enabled usb debugging prior to being bricked
http://forum.xda-developers.com/attachment.php?attachmentid=2800218&d=1402859206
so that should work?
Well that's the PIT file for your model phone, whether or not it unbricks it depends on what you did to brick it
I bricked it by attempting to flash philz touch recovery in odin 3.09 and it failed. Now I have the message:"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." on my phone, I tried doing exactly that but kies detects my phone but never finishes loading it up. So I tried flashing the stock firmware for my device model and got the same issue I did when attempting to flash the recovery. As far as i know I didn't do anything wrong as i was very careful to select the right files, etc. but clearly I did.
Well you've got nothing to lose by trying the PIT file
Not flashed PIT before so read up on exactly how to do it first, this is the thread I got the link for your phone from
http://forum.xda-developers.com/showthread.php?t=2737448
Tried flashing the file and that failed as well... not looking too good.
I guess my phone's useless now.
Did you check the "Re-Partition" in ODIN?
Are you using the latest version of ODIN3 (3.10.6) ?
Try ODIN3 version 3.0.7 too
(Obviously) Got phone in download mode
Tried just flashing a stock ROM from sammobile
Tried flashing the stock ROM along with the PIT file & Stock ROM together?
tried it all, when trying to flash the pit file as well though it gives me "SECURE CHECK FAIL : PIT" on my phone. whenever I try to flash it it always fails at system.img.ext4 with Complete(Write) operation failed.
I think I know the issue now, I'm using VMware, which apparently doesn't work. Will try on a windows pc in a while. thanks
Ah right, yea always best from a native PC
Let us know if you get it working
It worked and then I installed the newest cyanogenmod.

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

flashed worng kernel - stuck a download mode

Hello I have a G928F and yesterday I flashed a wrong kernel by mistake, a kernel for G920F by arter97
Then I couldn't boot and only could go into download mode, where odin found my phone.
However I couldn't flash ANYTHING with odin. I tried the stock rom for my device with odin to get full unroot and also philz recovery just in case works so I can flash the proper kernel through recovery. All these failed, I attach two images from the most recent fails - please advise next step thanks
edit I think not the problem may be
<ID:0/003> Can't open the serial(COM) port.
panast said:
Hello I have a G928F and yesterday I flashed a wrong kernel by mistake, a kernel for G920F by arter97
Then I couldn't boot and only could go into download mode, where odin found my phone.
However I couldn't flash ANYTHING with odin. I tried the stock rom for my device with odin to get full unroot and also philz recovery just in case works so I can flash the proper kernel through recovery. All these failed, I attach two images from the most recent fails - please advise next step thanks
edit I think not the problem may be
<ID:0/003> Can't open the serial(COM) port.
Click to expand...
Click to collapse
Oh. I think your usb drivers arent installed properly. I search it now.
Ed.: http://downloadcenter.samsung.com/c...NG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe install this and try again.
Ed.2: Firstly, try flash recovery and proper kernel if doesnt work then flash firmware please.
guys sorry to break your nerves the problem with the
<ID:0/003> Can't open the serial(COM) port.
was because of the usb extension that I was using to connect my phone, then I plugged the usb directly to motherboard and I got success flashing my rom
and the strange thing is that I rooted my phone 2 weeks ago via odin and the same usb extension
I will try everything slowly now I am at a stage with flashed rom but lost root privileges
panast said:
guys sorry to break your nerves the problem with the
<ID:0/003> Can't open the serial(COM) port.
was because of the usb extension that I was using to connect my phone, then I plugged the usb directly to motherboard and I got success flashing my rom
and the strange thing is that I rooted my phone 2 weeks ago via odin and the same usb extension
I will try everything slowly now I am at a stage with flashed rom but lost root privileges
Click to expand...
Click to collapse
Lol. No problem. Glad to know you succeed. Flash philz recovery then kernel.

Soft bricked Samsung Galaxy s4 GT-I9505 won't let me flash stock firmware on it.

Hello everyone I'm having a problem, I'm trying to put the stock firmware back on my Samsung but Odin keeps failing.
Saying '' Complete write failure'' What do I need to ?
Thanks for the help everyone!
I have the same problem. I've downloaded and tried many firmware, i even tried to use Heimdall to flash firmware, but aboot.mbn fails to flash. Please help what to do...
john.reyes.jmr said:
I have the same problem. I've downloaded and tried many firmware, i even tried to use Heimdall to flash firmware, but aboot.mbn fails to flash. Please help what to do...
Click to expand...
Click to collapse
extract the tar package and make another tar package with only system, boot and recovery related content from that original tar . It worked for me. I too was failing on aboot.mbn .IT will most likely work unless you are trying to upgrade/downgrade your phone. Downgrading is not going to work for sure. About upgrading I am not sure.
adarshadhungel1 said:
extract the tar package and make another tar package with only system, boot and recovery related content from that original tar . It worked for me. I too was failing on aboot.mbn .IT will most likely work unless you are trying to upgrade/downgrade your phone. Downgrading is not going to work for sure. About upgrading I am not sure.
Click to expand...
Click to collapse
Same problem occurs the system fails to download
don't know if you have already fixed the device or not but maybe flashing 4 files firmware can help you. I was able to flash all without any problem.
use samfirm with "binary nature" enabled.
adarshadhungel1 said:
don't know if you have already fixed the device or not but maybe flashing 4 files firmware can help you. I was able to flash all without any problem.
use samfirm with "binary nature" enabled.
Click to expand...
Click to collapse
I just tried this but still failed in aboot.mbn
john.reyes.jmr said:
I just tried this but still failed in aboot.mbn
Click to expand...
Click to collapse
Aboot.mbn is the bootloader. If Odin fails when flashing this file, you need to try a different USB cable, different USB port, the boot loader is not made for your phone, or you are trying to flash an older bootloader over a newer bootloader.

Categories

Resources