Database Develop

[Q] Galaxy Note bricked? No. Problem solved.

This is the situation:
Windows XP 32bit
Galaxy Note with LA4
Odin V1.85
KIES latest version
Latest Android SDK
I tried today to downgrade to a directly rootable stock ROM. It failed?
My Note stucks on the bootscreen.
I can put the Note in the downloadmode. When I start Odin, I see a yellow box under ID:COM with 0:[COM7], so my computer sees the Note. I want to flash the rootable stock ROM as described in many threads, especially following Dr. Ketans Guide
But it fails, it stucks at Initialzation..
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_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..
I tried the LA4 stock ROM, same problem.
After this I have putted the Note in recovery mode and this is what I see:
"E:failed to mount /sdcard (Unknown error: 0)"
"E:install_application_for_customer:Can't mount /sdcard"
" your storage not prepared yet. please use UI menu for format and reboot actions."
"copy application failed"
In the recovery mode I tried Factory reset and Wipe cache...no effect.
Since 4pm I have tried many things, read threads and posts, but nothing has solved my problem. By the way I have not seen a problem as described above no where. Is there a genius who can solve this/my problem?
Or is my Note bricked?

The only thing i can see is that it can't mount the SD. Other than that, i don't know. And you know i had my own problems yesterday, so i'm not in the position to know what might be wrong. But one thing is sure, it's not bricked since you can enter download mode.
I know it's frustrating, but you'll have to wait for somebody that knows some things about Odin. I used it myself for the first time yesterday since the Note is my first Samsung device.
Sent from my iPad GT-N7000 using xda premium

see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.

dnyc said:
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
Click to expand...
Click to collapse
Connect to Kies and see if your phone is beeing recognized. If not reinstall the usb drivers. Reboot the phone and pc afterwards and try again. ENABLE USB DEBUGGING in settings also.
Hope it helps

I think this is related to SD card.(Internal)
Have you try using repartition?
I think it may work, NOTE THIS is just my thinking, I can't take any guarranty, you may use at your own risk, if other measures failed
Flash with repartition selected, n selecting pit file
here attached it (extract before use)for note 16GB (routine, not for 32GB)

Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium

dnyc said:
see if you can turn off the note. press and hold volume + power and home to get to cwm.. do a data factory reset. then flash with odin in download mode. also make sure you put the correct files in odin when flashing. i had the same problem with my sg2 a few months back when i was fresh with android os. i spent 4 hours figuring it out when it only took 5 mins to fix lol.
Click to expand...
Click to collapse
As you can read I did trie data factory reset, after flash with Odin it didn't work. Thanks for your help.

gee2012 said:
Connect to Kies and see if your phone is beeing recognized. If not reinstall the usb drivers. Reboot the phone and pc afterwards and try again. ENABLE USB DEBUGGING in settings also.
Hope it helps
Click to expand...
Click to collapse
As you can read I can't ENABLE USB DEBUGGING, because I can't start my Note up normally. Thanks for your help.

Loftus said:
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Thanks, but no effect.

dr.ketan said:
I think this is related to SD card.(Internal)
Have you try using repartition?
I think it may work, NOTE THIS is just my thinking, I can't take any guarranty, you may use at your own risk, if other measures failed
Flash with repartition selected, n selecting pit file
here attached it (extract before use)for note 16GB (routine, not for 32GB)
Click to expand...
Click to collapse
With the pit-file it showed PASS!:
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/006> Added!!
At my screen the following:
Firmware upgrade encountered an isseu.
Please select recovery mode in Kies & try again
If I open Kies to select recevory mode it asks for a recovery code. I tried some codes like 0000,1234 and others, but no good...
Then, I entered the download mode of the Note and tried a flash with KK9 (one file) it shows PASS:
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
....and it works now for me!!! I thought it was wipe, but I have now with KK9 the same apps and configuration as before on the LA4. Weird but good for me!
All of you thanks for your help, especially dr.Ketan

Note not bricked.
Problem solved.

And the problem was?
Sent from my GT-N7000 using xda premium

Read my first post...

got the same problem, did all you did, but get "fail" after is starts working.
any suggest?
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKK9_N7000OXAKK9_N7000XXKK5_HOME.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> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
thanks

Caesarea038 said:
With the pit-file it showed PASS!:
....and it works now for me!!! I thought it was wipe, but I have now with KK9 the same apps and configuration as before on the LA4. Weird but good for me!
All of you thanks for your help, especially dr.Ketan
Click to expand...
Click to collapse
Really glad to hear.
It is really painful when some one say bricked lovely device.
its ok now, congratulation.
it is advisable once you format internal SD card. Not in hurry, but at least before next update.
Sent from my GT-N7000 using xda premium

shaharda said:
got the same problem, did all you did, but get "fail" after is starts working.
any suggest?
<ID:0/005> Added!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
...........................
<ID:0/005> factoryfs.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
thanks
Click to expand...
Click to collapse
Can you tell me exactly the problem and what you did step by step?

Loftus said:
Reflash stock rom with a different usb port and cable
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Today I figured something out:
If you encounter problems with rooting/flashing try another or original USB cable, maybe a different USB port....
My problem as described in my first post was a combination of a fail USB cable and a software problem.

thanks for the help.
i'll try to replace my cable and try a new port.
what i did is trues to flash xxla4 from criskelo with Odin.
while doing that yhe action was breaked an since than i get the massege "an issue encountered...".
i tried almost everything (all i knew and mange to find in the net): tried again with odin, tried to flash 5 different roms from the list in dr.ketan thread.
tries to boot into recovery (no success), tried to recover with kies (it is not being identified by it).

now the battary won't charge. need to send it to the Lab.
thanks anyway. (i'll as them what they did)

shaharda said:
thanks for the help.
i'll try to replace my cable and try a new port.
what i did is trues to flash xxla4 from criskelo with Odin.
while doing that yhe action was breaked an since than i get the massege "an issue encountered...".
i tried almost everything (all i knew and mange to find in the net): tried again with odin, tried to flash 5 different roms from the list in dr.ketan thread.
tries to boot into recovery (no success), tried to recover with kies (it is not being identified by it).
Click to expand...
Click to collapse
Can you enter DOWNLOAD MODE?

[Q] What happened to my Note? Revival ideas?

Hi guys, I am desperate and in need of help ...apparently my Note decided to die on me and I think I just made it worse. Please whoever has any suggestions please help me.
For a good while now I had been running Paranoid Android without any problems whatsoever until last friday my phone woke up stuck on the start screen (the one that says GT-N7000). Please note that NO changes were made to the system nor were any new apps installed. Rebooting the phone resulted in the same situation.
After noticing that it was stuck, I figured I would go into recovery and try clearing cache as that sometimes will help, to my surprise the phone was unable to go into recovery, it would just present a blank screen.
I could still go into download mode, so I thought I would go back to stock through ODIN eand re-root and re-flash, when i tried this ODIN hanged at this point:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA4_N7000OXALA4_N7000XXLA4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> factoryfs.img
<ID:0/007> NAND Write Start!!
I tried several GB and two JB stock ROMs, both ended up with the same results. I also tried flashing this through ODIN 1.83, 1.85 and 3.07 with no luck.
Then I got worried that my phone had somehow gotten bricked (overnight with no change which I know does not make sense), and I found forest1971 thread on how to revive a bricked Note. Following this thread I tried all PIT files from 2.0 up to 2.5 and ODIN hanged at this point:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
After this I got really desperate, so I went ahead and tried the manual method, and tried flashing Speedmod kernel in order to be able to access recovery again as is instructed in the thread. ODIN hangs during this process as well, thus not installing the Kernel but it did give me the yellow triangle and increased my binary flash count. I had managed to avoid this throughout my whole 10 months of owning the phone by doing things correctly, and now I cannot send it to Samsung even though I would still have 2 months worth of warranty eliminating the possibility of sending it back to them.
So in summary I can't access recovery, I can't flash a stock ROM, I can't flash kernels and now I have the yellow triangle. Please also note that I have tried with several USB cables, updated drivers and several PCs.
What can I do about this? Is there still some sort of hope for my phone? Can the triangle be somehow removed without access to recovery or the ROM? and finally how on earth could my phone do this from one night to the other without me installing or doing anything to it?
Thank you very much, any ideas will be greatly appreciated.

[Q] Upgraded to Jellybean, phone dies on boot.

Hi
I did an OTA update to Jellybean yesterday which Three (3) put out and it all went smoothly. I was making a phone call today and the phone suddenly died. Now every time I turn it back on it loads and stays on for about 30 seconds at which point it dies again.
I've tried it with/without charger and SD card but it's the same result each time. Tried using Kies to re-install the firmware but the phone doesn't stay on long enough for me to.
Is there anything I can try before giving it to Three for a month?
Thanks.

Download a stock firmware from sammobile and flash it using odin

_McShane_ said:
Hi
I did an OTA update to Jellybean yesterday which Three (3) put out and it all went smoothly. I was making a phone call today and the phone suddenly died. Now every time I turn it back on it loads and stays on for about 30 seconds at which point it dies again.
I've tried it with/without charger and SD card but it's the same result each time. Tried using Kies to re-install the firmware but the phone doesn't stay on long enough for me to.
Is there anything I can try before giving it to Three for a month?
Thanks.
Click to expand...
Click to collapse
Maybe when u did the update, the file was corrupted. This could be happened if your internet connection was not stable.
So, to make sure u get the right update. Just download it from sammobile...u can find the right rom for your region...there.
After the download completed, just install it through odin. U can find how to use odin from internet. Just google it
Sent from my GT-N7000 using Tapatalk 2

Hi
Thanks for the replies, I downloaded and installed the firmware and I believe it all went well.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000OXXLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> factoryfs.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> zImage
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Unfortunately it still dies on boot. I'm thinking it could possibly be the battery?

Just to let you know I got a new battery and the phone is now fine.
Thanks for the help.

[Q] I9305 doesn't boot, Odin fails at flashing boot.img

Galaxy SIII I9305 shows up with not booting, getting stuck at the SIII logo.
Does the same when trying to get into recovery, so I tried to flash it with Odin.
Flash screen says:
Odin Mode
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWREV: A2
Click to expand...
Click to collapse
I tried to flash it with the latest packages from Sammobile, but no matter what I try, Odin always fails right away when flashing boot.img... any idea what the problem might be, or what I'm doing wrong?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUENE4_I9305H3GENE1_I9305NEUEML2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse

Centrumgsm said:
Galaxy SIII I9305 shows up with not booting, getting stuck at the SIII logo.
Does the same when trying to get into recovery, so I tried to flash it with Odin.
Flash screen says:
I tried to flash it with the latest packages from Sammobile, but no matter what I try, Odin always fails right away when flashing boot.img... any idea what the problem might be, or what I'm doing wrong?
Click to expand...
Click to collapse
stupid question, but did you go in to download mode when flashing? thats by pressing menu button + volume down button + power button. then press volume up to agree with download mode and then flash with odin. And make sure you have all drivers installed

klemen241 said:
stupid question, but did you go in to download mode when flashing? thats by pressing menu button + volume down button + power button. then press volume up to agree with download mode and then flash with odin. And make sure you have all drivers installed
Click to expand...
Click to collapse
I did. As far as I can tell, I did everything according to the guides.
[edit] I also managed to flash a different I9305 without problem, so I'm sure it's not driver or flash file related. There is something with this specific phone that prevents flashing.
I've seen a "rescue firmware" for the I9300 with separate PDA, MODEM and CSC (+.pit) files for when the regular stock firmware wouldn't flash, and I was wondering if such a thing exists for the I9305 or if there is a guide on how I could make one.

Try to get a PIT file for the i9305 and add it to ODIN. If you don't do this, ODIN extracts the PIT from the device, and that might be corrupted.

daedric said:
Try to get a PIT file for the i9305 and add it to ODIN. If you don't do this, ODIN extracts the PIT from the device, and that might be corrupted.
Click to expand...
Click to collapse
Can't brick the device much more than it already is, right? I tried it, but it just gets stuck here:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Click to expand...
Click to collapse
I got bored after 15 minutes, turned off the target, turned on the target, no change, still the same error when flashing.
Thought about the Knox bootloader preventing me from updating it, but that usually gives me some kind of error message right on the flash screen. Plus I'm using the latest images, and the other I9305 also says "SWREV A2", so that shouldn't be a problem.
This looks more and more like a motherboard replacement...

All i have to say is, good luck. Things don't look good.
Try to flash just a recovery via ODIN. You'll kiss knox goodbye, but we're out of options.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9305/

daedric said:
Try to flash just a recovery via ODIN. You'll kiss knox goodbye, but we're out of options.
Click to expand...
Click to collapse
Tried it, no go. Same error, still won't boot into recovery. On the upside, it didn't trip Knox either

Ok, just for good measure, let's get down to the basics.
Questions:
1. What type of USB cable are you using? Can you try another?
2. Is the USB cable connected directly to the computer , or via HUB / Front ports ?
3. Have you tried cleaning the usb port on the device ?

I've covered all the basics, even tried another computer. Same results.
I couldn't find a solution, ended up sending the phone for a motherboard replacement. Thanks for the suggestions, everyone!

Loop reboot after the "FIX Ram Management"

Hi
My S6 is in loop reboot after i edit the build.prop... I have the original build.prop on my pc but how to restore it ??? Please help!

master-i said:
Hi
My S6 is in loop reboot after i edit the build.prop... I have the original build.prop on my pc but how to restore it ??? Please help!
Click to expand...
Click to collapse
If you have TWRP installed, you can just ADB the file over. Easy.
If you only rooted and want to preserve your KNOX flag, you need to ODIN back to stock and then re-root. It's not destructive, so it's not nearly as bad as it sounds

I don't have twrp for now but can i Install it on download mode ? I just tried to install it and it stop on Start upload (on odin)

Follow these instructions. Download ODIN from that link too
http://forum.xda-developers.com/tmo...irmware-sm-g920t-firmware-odin-guide-t3077706

Do i lose my data? and where Can I find the [Unified Driver Installer] on step 2?

No you won't lose your data at all, you will lose root, but all you need to do is re-root the phone.
http://developer.samsung.com/technical-doc/view.do?v=T000000117

I think it's easier to flash only the build.prop no? is it possible?
Thanx to help me bro!

No at this point, IMO, this is the easiest way to get you back to where you were. I assume you're on the stock ROM just rooted.

Yes, I were on the stock room just rooted by PingPong. Hope it will not make my phone slower or make it crash more often... :/

Yeah just ODIN back to stock, then re-root using PingPong, it's really not as bad as it sounds. All of your apps and user data including all settings will still be there.

@se1000
Please look this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Have you had your phone in download mode for a while? If so, try rebooting the phone

se1000 said:
Have you had your phone in download mode for a while? If so, try rebooting the phone
Click to expand...
Click to collapse
Of course I just retried again same error... I can't understand because I see the 0:COM3 on Odin...

Are you using the ODIN from the link? I had problems with other versions

se1000 said:
Are you using the ODIN from the link? I had problems with other versions
Click to expand...
Click to collapse
Yes the V3.10

Were you trying to run ADB earlier? Try rebooting the PC

I closed and reopen Ondin on Administrator and now it's blocked with: <ID:0/003> SetupConnection..

Try a different USB cable or different USB port. Seems ODIN can get a bit finicky

I rebooted PC and my Phone and unplugged and still the same
maybe it's because i tried to install twrp?

Shouldn't matter, as long as you're in download mode and ODIN shows light blue it should work