Hey, guys, I got a problem here, it's weird because I wasn't trying to flash when it started, the phone was ok, then froze, I tried to power off, but it didn't work, so I took off the battery. I put it on again, and the screen was freezing on the Samsung Galaxy Note GT-N7000 screen, I decided to flash to a stock rom with Odin, I put in the download mode, Odin recognized the phone but when I started to flash, Odin stuck at the end of the process, I tried in all different usb ports of my laptop, I killed all the Kies processes, but it keeping sticking at the same point of the flashing. Please, somebody give me a hand here.
ps: I tried more than one rom, and it happens the same all the time.
I also uninstalled the usb ports and reinstalled, but nothing changes..
If pc odin get stuck at the factoryfs part and gives a write error then most probably the emmc bug has struck yet another SGN.
Search for forest's guide on uggie's thread about reviving a bricked note. If you are comfertable with loosing about 3gb of you internal sd card then repartitioning is an option. Else if you are on the stock kernel, your binary count is zero and your phone is in warranty, get it to the service center. They should replace the MoBo under warranty.
You can at least mention what rom/kernel were you on and to what are you flashing to....
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Related
Hi I'm fairly new at this and I've a few questions. I bricked my phone and tried to fix it with kies recovery. Which failed. But obviously from that I got the knox thing. So I fixed it with a PIT file and then I flashed a PDA file via odin from Sam mobile that said I wouldn't be able to downgrade from it, but it works. But when I try run a game or bench mark test my device it will restart and then keep looping on the boot screen. If I take out the battery and then try boot it again it works. I know I've voided my warranty. How would I fix it from restarting? Also would I be able to install a custom rom still or have I blown that by getting the OTA updates?
Sent from my GT-I9505 using xda app-developers app
Boot-loop could also be a faulty battery..? Maybe that causes your device to restart in the first place! You can get a new one from Samsung for free without sending in your phone, they just need serial, IMEI and serial number from battery. I called them 2 days ago to fix this I would do a check just to be sure!
Also see: My phone also hang at the Samsung logo, then rebooted. When I plugged in my charger it suddenly did work. Battery seems to be faulty, waiting for a new one to arrive now!
See: http://forum.xda-developers.com/showthread.php?t=2513767
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
KalarAzar said:
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Repulsa said:
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Click to expand...
Click to collapse
Hi and thanks for your reply,
I can boot into download mode - one of the only things I can do! - and it says 0x1 under KNOX WARRANTY VOID, so yes it is showing Knox void.
Just in case you need it, the full information shown on the screen in download mode is as follows:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thanks again..
KalarAzar said:
Thanks again..
Click to expand...
Click to collapse
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Repulsa said:
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Click to expand...
Click to collapse
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
KalarAzar said:
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
Click to expand...
Click to collapse
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Repulsa said:
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Click to expand...
Click to collapse
Yes, I'm afraid it does, and I have already done the wipe cache and factory reset, but no joy. I did it again anyway and on reboot it went back into the bootloop again, I'm afraid..
KalarAzar said:
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Acer4605 said:
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Click to expand...
Click to collapse
Ah FFS. My battery serial does start with BD and I was wondering if it was a battery issue, but didn't want to replace it if the fault was wider spread. I guess I may have to try this then..
I'm just flashing to MJ7 right now, but if it reboots again I will see about a new battery from where I bought it on Monday
And, as I forgot to say in the last post: thanks for your reply. If this fixes it, much kudos, my friend..
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
KalarAzar said:
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
Click to expand...
Click to collapse
you can get passed the samsung logo if you boot while your charger is connected to the phone, the battery might swell as well or is already bigger then it originally was
My phone has been randomly shutting down over the past couple of days and the only way I can get it to boot is to connect a charger/cable to pc. I've tried different ROMs and returning to stock. No joy.
I guess my battery could well be the problem
---------- Post added at 11:33 AM ---------- Previous post was at 11:28 AM ----------
My phone has randomly started shutting down over the past couple of days and the only way I can get it to boot is to connect charger/cable to pc. When it dies, it also loses all of my wifi passwords. It's a bit of a head scratcher. Any help appreciated
Definately the battery, dude
I was experiencing the same problems, and I observed that the battery swollen. So I replaced it and now the phone is functioning properly. Do not wait for the battery to modify its volume because you are risking to put pressure on the display and crack it. Beware.
Was, indeed, the battery
Hey everyone,
Just to let you know that I went back to Phones4u with the receipt from September (when I bought the new phone) and they filled out a form to request a new battery from Samsung and replaced mine their and then in the shop with a new battery from another Samsung Galaxy S4.
My old battery did, indeed, have a serial number that started with BD and the new one starts with AA so hopefully I am now sorted.
Massive thanks to everyone who replied and hopefully this thread will save someone else the time and lost data that flashing ROMs can incur.
Cheers,
A very happy Steve :laugh:
I'm pretty sure I've ended by bricking my Note 4 N910G.
1. On stock, the phone started becoming very slow / unresponsive. Not the things a
2. I decided to take the "if it's broken flash it" solution. Flashed to stock but got stuck with a "ODIN flash write failure" message.
3. Have tried multiple approaches including installing TWRP / CWM without any luck. Can't flash a thing through ODIN. I've tried more options than I should have.
Taking it to the service center today. Any advice would help.
Please note:
1. I did not make a mistake with the stock ROM version. It's N910G
2. Not an expert, but have had a Galaxy S and Note 2 before this - so know my way around here. At least, that's what I thought till now.
Took it to the service center today. They're not servicing it since its rooted. Asking for USD 300 to replace the motherboard. SOS - PIT file for N910G is the last resort.
Nothing flashes at all with odin ? I think you may need to flash a pit file.
Have you tried kies emergency firmware restore or mskips toolkit? Mskip usually has an emergency firmware rescue as well. Also if you can connect through adb someone more advanced than me might be able to help you
Sent from my SM-N910F using Tapatalk
Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Bro something similar happened to me as well .. even I did purchase new battery as everyone and also repair service guy said it's due to battery but that didn't solved the issue ..
Kindly check this xda post by me , it may help you.
https://forum.xda-developers.com/note-4/help/weird-white-bar-booting-sm-n910g-t3529413
adrscu said:
Hey guys!
I'm posting here in hopes someone could help me with my issues.
First and foremost, the phone is behaving erratically since the latest official update.
Phone was unrooted and untouched, only by official OTA updates.
-After the latest official OTA update, the phone hangs, reboots, sometimes when I try to unlock my phone it just doesn't respond to commands, sometimes it doesn't get past the first screen that shows when you power up the phone.
-I tried flashing a custom ROM for the first time and I got "mmc write error". I couldn't flash any other ROM, neither using Odin or by trying to restore the phone through Kies. The phone encountered the MMC write error with anything I tried to flash (this was happening at system img).
-I then tried the "fix mmc write error" guide here on XDA which promised to fix the error, but it didn't work. I followed all the steps and even used the repartition option with the provided .PIT file.
-Then I flashed the Philz touch recovery, rooted, and I formatted every partition besides the most important ones like EFS.
-Now I was able to restore the phone with Kies and afterwards I was able to flash any custom ROM (tried a bunch and the phone behaves bad (the same) on any ROM. Some ROMs don't even boot).
-I don't remember where, but I've read that the latest official update for the N910F screws something in the bootloader, and makes the phone behave eratically. Is there any known fix for this? Is there any bootloader I can flash so that the phone will work fine as before? And if so, what version should I use?
-I've read around and it was suggested that the battery might be causing these issues. So I went out and bought a new genuine note 4 battery and replaced it.. Sadly it didn't fix the issue.
I'm now on the custom RamRom with their custom RamKernel (for the 910F variant) and sometimes it works perfectly, other times it just hangs and is unresponsive until I pull the battery out and do a fresh boot.
I would of returned the phone in a heartbeat, but it's out of warranty, and it's such a shame it worked perfectly fine before the latest update. I feel it's Samsung's fault for the bad behavior of the phone but there's no way I can hold them responsible now, with the phone out of warranty and with the knox counter tripped.
Sorry for posting this big block of text and thanks to anyone reading it / shedding some light on my problems
Thanks!
Click to expand...
Click to collapse
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Hey guys and thanks for the replies.
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
adrscu said:
Hey guys and thanks for the replies.
While this might seem plausible, it is very hard for me to accept, because prior to having these problems, I never flashed anything to the phone, apart from official OTA updates. I find it really hard to accept that the part of the MMC - internal memory which is assigned to the operating system has been written so many times as to cause failure..
Click to expand...
Click to collapse
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Amar.B said:
Your facing emmc failure *your internal storage is corrupted* After a certain amount of read/writes, it ends up crapping out.
short note you may find a workground for this problem but at the end changing the motherboard is the only solution for you..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Amar.B said:
Believe me i use to feel the same but now i am all careful not to loose my warranty i am on stock rom too knox is not triggered.. Emmc failure is a time bomb lots of people are having the same problem it's a hardware defect doesn't matter if you're custom rom or stock rom.. my phone is almost new 8 month old and am having a problems with phone already. phone shutting down at 20% and going into bootloop i have to charge the phone so it could boot up normally now i found many users are facing the issues..
The weird part is only the snapdragon variants are facing emmc failure while exynos don't
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
adrscu said:
Thanks for your help, Amar! I've put some thought into it and I'm considering looking for a new motherboard. Maybe even an exynos one if it fits.
I'm very puzzled as I own other phones too and it's the first time something like this is happening.
Thanks again!
Click to expand...
Click to collapse
All the best mate and it's my pleasure.. cheers
Sent from my SM-N910G using Tapatalk
Some background... this phone was bought back in the day when Note 4 was about to be released. I have been the unique owner and I have treated the device with an abnormal amount of care and respect. Updates were about to come up but for my device... the bloody thing was getting said updates way too late (2-3 months later than everybody else such as UK or Poland). I grew tired of waiting so I did it, I force updated my own device using an image from sammobile.com with Android 4.4.2 using ODIN. It worked. The phone updated flawlessly in around 3 minutes it started the boot up sequence but the only difference was that the software inside was for UK not my European region which was Romania.
Fast forward... I rooted the device, did a lot of firmware tests (even after 5.0 came out, I still installed a ton of firmwares on it and they all functioned properly even if I was dealing with Android 6.0 or even 7.0) and the phone generally functioned very very well.
Now my **** up was that I wanted to reformat the phone to a 100% stock image (which I could do with ease at any given moment) and for some strange reason I ticked "Nand Erase All" and the reformat went trough... the software fully installed. My phone booted up and what do you know? I suddenly have 16 GB of storage instead of 32. I panic a little... I try to firmware upgrade a normal stock image for the romanian version of the Note 3. Stock Romanian based software for SM-N9005. Fails mid update 100% of the time me trying it well over 20 times. A bit of research, I end up realizing I ****ed up the phone seriously bad. So one guy saves me with a "repair firmware" which is named: N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware. I manage to flash the whole thing onto the phone and it works... but things are off. Apps are crashing at random, the phone is laggy at times... heck, there's a "android.media has stopped working" popping up every 2-3 minutes or even faster if I use internal storage. I can barely do anything... it also destorys the SD Card. As in, I gotta connect it to a micro SD reader to repair the micro SD from within Windows to be able to copy what's on it or even copy something on it... internal storage is zippy but again, it stops working once this android.media crashes. A few months pass, my girlfriend gives me a chance to repair the phone one hopeful last time. So I said "**** it" and I tried flashing again, the latest RO ROM for the phone. It fails mid way. I try restarting the phone and... it's bricked. It says that the software update failed and I need to connect it to Kies to update. Did just that and I find out Samsung doesn't allow the Note 3 to be emergency software updated anymore.....
I have the repair software, and another 2 different softwares. I have tried so many times to update the device using different cables and ports. Heck, I even installed Windows 7 to see if it works (until one guy told me I can install it trough VMWare and I will get the same exact result as if I were to have Windows 7 directly installed on the PC)... nothing works. My main error message is the one attached as a picture.
I tried every ODin, port and cable I could. I just... don't know what to do anymore. The phone is great but do I really have to buy a secondary display broken phone and transfer the mainboard from that phone to this one to have a "functioning" phone again or are there other options I missed out on?
Thanks for your message! I shall try to respond as soon as possible.
Search Nand Erase .
My guess is you need a service centre with a Rif box .
Sent from my SM-N930F using XDA-Developers Legacy app
I'm not sure but is it possible to flash the phone with a 32 GB pit file?
fogoticus said:
Some background... this phone was bought back in the day when Note 4 was about to be released. I have been the unique owner and I have treated the device with an abnormal amount of care and respect. Updates were about to come up but for my device... the bloody thing was getting said updates way too late (2-3 months later than everybody else such as UK or Poland). I grew tired of waiting so I did it, I force updated my own device using an image from sammobile.com with Android 4.4.2 using ODIN. It worked. The phone updated flawlessly in around 3 minutes it started the boot up sequence but the only difference was that the software inside was for UK not my European region which was Romania.
Fast forward... I rooted the device, did a lot of firmware tests (even after 5.0 came out, I still installed a ton of firmwares on it and they all functioned properly even if I was dealing with Android 6.0 or even 7.0) and the phone generally functioned very very well.
Now my **** up was that I wanted to reformat the phone to a 100% stock image (which I could do with ease at any given moment) and for some strange reason I ticked "Nand Erase All" and the reformat went trough... the software fully installed. My phone booted up and what do you know? I suddenly have 16 GB of storage instead of 32. I panic a little... I try to firmware upgrade a normal stock image for the romanian version of the Note 3. Stock Romanian based software for SM-N9005. Fails mid update 100% of the time me trying it well over 20 times. A bit of research, I end up realizing I ****ed up the phone seriously bad. So one guy saves me with a "repair firmware" which is named: N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware. I manage to flash the whole thing onto the phone and it works... but things are off. Apps are crashing at random, the phone is laggy at times... heck, there's a "android.media has stopped working" popping up every 2-3 minutes or even faster if I use internal storage. I can barely do anything... it also destorys the SD Card. As in, I gotta connect it to a micro SD reader to repair the micro SD from within Windows to be able to copy what's on it or even copy something on it... internal storage is zippy but again, it stops working once this android.media crashes. A few months pass, my girlfriend gives me a chance to repair the phone one hopeful last time. So I said "**** it" and I tried flashing again, the latest RO ROM for the phone. It fails mid way. I try restarting the phone and... it's bricked. It says that the software update failed and I need to connect it to Kies to update. Did just that and I find out Samsung doesn't allow the Note 3 to be emergency software updated anymore.....
I have the repair software, and another 2 different softwares. I have tried so many times to update the device using different cables and ports. Heck, I even installed Windows 7 to see if it works (until one guy told me I can install it trough VMWare and I will get the same exact result as if I were to have Windows 7 directly installed on the PC)... nothing works. My main error message is the one attached as a picture.
I tried every ODin, port and cable I could. I just... don't know what to do anymore. The phone is great but do I really have to buy a secondary display broken phone and transfer the mainboard from that phone to this one to have a "functioning" phone again or are there other options I missed out on?
Thanks for your message! I shall try to respond as soon as possible.
Click to expand...
Click to collapse
20 days later it happens to another guy (me)
help me save me from this mess, please, im desperate
neeharv said:
20 days later it happens to another guy (me)
help me save me from this mess, please, im desperate
Click to expand...
Click to collapse
I have tried myself. You have a chance of actually flashing it if you have the original cable that came with the phone. If not, the service is the only spot that can help.
I went to a shop and using an NS Pro box thr phone flashed problemlessly. Found out about my bad usb cable and here we are. The phone cost me 35 euros but it functions again.
fogoticus said:
I have tried myself. You have a chance of actually flashing it if you have the original cable that came with the phone. If not, the service is the only spot that can help.
I went to a shop and using an NS Pro box thr phone flashed problemlessly. Found out about my bad usb cable and here we are. The phone cost me but it functions again.
Click to expand...
Click to collapse
will this work: https://forum.xda-developers.com/showthread.php?t=2610757
it said it will fix partition corruption (like what happens when you do nand erase all without pit file)
neeharv said:
will this work: https://forum.xda-developers.com/showthread.php?t=2610757
Click to expand...
Click to collapse
Probably. Try it.
Here's the fix, it is the proper way to use "nand erase all" and to fix problems encountered while trying to use it:
https://forum.xda-developers.com/showthread.php?t=2610757
You can find the you the PIT files you need for it
https://www.sammobile.com/forum/showthread.php?t=30482
(make sure you download the one coresponding to the stock firmware just in case)
For other devices just google it.