I have a serieux problem with my phone and it is when i put in my phone charging cable into the phone.
I get fatal reboots and the phone hangs totally 10 times after putting em into the starting screen or the system.
Before i had a few custom roms on my phone and want to try em out for it´s functions
My story:
I had the CrisisCross Rom on my phone , then i flashed a 6.0 Android Custom Rom on my phone because i had problems with my Samsung Gear VR from a friend and i had not yet installed the Samsung VR Feature and had read about the leak issues from the custom roms.
Because i had an issue on the 6.0 Custom Rom with Viper4android ( don´t know which rom it was ) it only doesn´t work the programm./
Then i got back to another custom rom and Viper4android work again.Later on my system hang out when i put the charging cable on it and i have seen a few pixels and then later on the total crash of the system.i have then try out to make other custom roms on it but i made maybe a wrong DBT Code ( i choose the Germany Code ) .
But the problem stay on my phone.i had this now for 4 weeks , everytime my phone was empty it must be reflashed almost twice a day and i can´t put my phone charging cable on my phone even with that it hangs on reboots.
I tried then out to live with that as long as it works i know it´s hard to make that every time it was recharged but i don´t want to send it back to the factory for getting crushed with the invoice later
As it is and was rooted to much i have no chance that the garanty will get on for that.
A few days before this day i have made a fresh stock rom 6.0 firmware on my phone but the charging problem stayed ( pixxel issues / fatal hangouts / system problems like pixxels on the PIN sycreen )
Also everytime when the phone is off i get pixxels on the full screen ( many colours ) when i stuck the charging cable in.
My question is now if it´s worth to send it back to the factory to repair it and if that is a system problem or a problem with the hardware?
Greetz:highfive:
Can i get an answer please :crying:
If you you don't know which ROM you flashed earlier how can we help? We're not mind readers. You also haven't said which model phone you have. F/C/G? Something else? Are you sure you flashed the right firmware for your model?
If you have, it sounds like a hardware problem. It's extremely unlikely to be CSC-related. If you're rooted and have a custom recovery, I'd wipe everything including system (you will lose EVERYTHING on the phone unfortunately), then flash stock firmware via Odin. If it doesn't work then, it's hardware.
Drastic, but with the lack of info you've given.... Good luck!
It is the 928F Model
I'm from Luxembourg and i choose the CSC Code from Germany ( DBT )
I think its a chip burned inside and it reacts when i put the phone charging cable into the smartphone ( screen full of pixxels )
I have already put the Stock Firmware on the phone flashed with Odin and backed up everthing with TB.
After a restart when i put out the cable from the charger i must make really fast to go in an app or play music , still it hangs/freezes sometimes even when sonebody calls me it freeze and i must restart it manualy.
When i was in the PIN enter when it vibrates and had a freeze it vibrates till i pushed the power and Vol-Button 10 seconds
I was almost afraid that it can explode :/ ^^
Related
Hello everyone here:
I have bought a Cinglar 8525 about 3 month ago. Because enthusiasm of flashing rom, I start to flash rom one week after the purchase.
I flashed the hard spl v7,and flashed new OS rom image.
During the flashing, nothing special happened.
After two months usage, one time a software stopped responding, I thought it might be network failure or something like that and simply reset the device,then the nightmare began.
The device boot into bootloader automaticlly without the pressing of OK and Power button.I tried to reset the device by push the reset pin but it does not work, the device always boot into bootloader, after a few step of tring, it turns out the device maybe dead and I pull off the battery to make the device totally shut off, then install the battery again, and leave the device black screen.
After some time, I reset the device again , it boot into the OS this time. After some configuration that need reset , I reset the device ,but again ,it boot into bootloader.
So my device is very unstable now, even "fragile". Boot, maybe into OS, maybe into bootloader.
Can someone explain this? Or help me solve it?
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
You're running wm6.1, aren't you? Try wm 6 as its more stable or if you wanna stick with 6.1 try PDAViets roms (19701 or 19900). They're english though....
Please note the "unstable" I mentioned is not something like halt frequently,application auto close up,etc.It's the bootloader stuff.
But I thought the problem might be irrevelant to the OS version, the "crash" occur first time when I use a ROM of wm6.0 and "crash" second time when I use a ROM of wm6.1
do some reading on wm6.1, it causes stuff like what you are describing....
After deep search in my brain, the "crash" might be occured during two version of ROM and both with wm6.1 .
Can you provide some link describing this problem of wm6.1 ? I just wondering if it is my device hardware failure or not.Or due to my some improper operation during ROM flashing process. Thank you.
Use the search function. There are a heap of threads... Some people recommend flashing a stock rom THEN flashing the wm6.1 of choice. This DOES seem to fix the problem.. Cheers...
yinx said:
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
Click to expand...
Click to collapse
Please note this, I have done it before, I 'll do some search work.
Is there some evidence or something that the 6.1 rom of 19701 kernel has solved this problem ? I really like the thread function in SMS message in 6.1 so I want to stick in wm6.1 .
I have honestly only had problems with th 19919/19202 versions of wm 6.1. Tried 19900 with no problem and REALLY liked the speed. 19213 is SLIGHTLY faster and again no problems. Try ne of these if you MUST have wm6.1. The stability seems to get better and better as the chefs progress up the versions. Cheers...
Untill now I can't get my phone out of bootloader, I've flashed many ROMs including manufacture shipped ROM, but the phone still remain in one screen.Wondering if it can work out. Frustrated....
Start from 9:00 this morning I kept flashing my phone with different version of ROM, try to get out the bootloader,but still not working.
After a reset of frustrating "not working", I put down the phone,and do some other job,when I came back,I have transfered another ROM to the microSD and ready to flash the ROM.Before flash I thought "may I reset the phone again? may be the bootloader will go away", then I reset the phone as normal, after a while , the splash screen appear! I enter the OS, thinking the bootloader problem has go away. But when I complete some setting and reset the phone again, the phone finally fall in bootloader again.
So what ......
check for bad blocks using MTTY.... On upgrading section.
Cheers...
This I also have tried out. But I see no bad block on it, and I even do a forcibly fix to the NAND and with no avail.
I have sent the phone to a service center, it is said they might going to change a chip on the phone.
Wish my phone good luck.
Hi,
I'm one of the unlucky guys who got his galaxy s not turning on unless plugged in.
here is my story and how I fixed it.
I was using darky's rom 9.2 and one day my phone started turning off every 30sec and won't be able to turn it on unless plugged in to a power source (USB/AC). I tried flashing many different roms & erasing everything but none solved the problem.
Solution:
- format all partitions from CWM recovery. be careful....
- flash the original firmware (via odin) from samsungfirmware.
- upgrade to 2.2 via kies
- send it back for warranty
The cause: I got the phone back and it says on the service paper that they "replaced USB jack , chemically cleaned contacts & upgraded software".
so yeah, all good now and I just wanted to share my experience because a lot of people said that it's a software issue but it looks like it's not :S
conclusion: if u are one of the unlucky guys then just send it back for warranty coz it's a hardware issue
I was using darky's rom 9.2
The clue is above YET ANOTHER D ROM BROKE MY PHONE POST .
jje
so u got the same problem ?? did u fix it ?
I'm not sure how a custom rom can actually affect the USB jack !!! it sounds kinnda strange. could be a coincidence ??
I was actually considering rooting it again and install Darky's V10. I don't wanna break my phone again :SS
I've spent a lot of time now trying to fix my phone and i'm really quite worried.
It's a Samsung Galaxy S4 SGH-I337M (CSC I337MOYAAAMDJ, Baseband I337MVLUAMDJ, version 4.2.2).
I have had CM 10 on it running perfectly fine for about a year. I decided to update it though and didn't know that you could update CM right from the phone , so I downloaded the software from their site onto my phone and onto my PC. Followed the instructions installation froze and didn't move forward for over a day .... so I gave up.
I went looking for and downloaded the phone's stock firmware for both my carrier (Virgin Mobile, Canada) and for Bell's, so I installed TWRP with Odin 3.07 without issue. When I install the stock firmware my WiFi will not turn on.
So i've tried installing several rom's putting them on the SD card and using TWRP on my phone and i've found out that if I use Goldeneye and tell it my phone is an I9505, or hyperdrive (I9505) or at the moment Google Play Edition (JFLTE 5.01, kernel = Googy-Max3) that the WiFI DOES TURN ON as soon as the rom is loaded !!! So I thought I was good, but no
When flashed with either it's stock I337M firmware or these custom I9505 rom's my phone will play no audio. Chrome just crashes if I go to play any music or video. If someone call's, the ringer doesn't work but after several 'rings' my phone start's to vibrate indicating they called (aka the dialer lags out and then crashes). I can make calls too but when I talk the recipient can't hear me, nor I them.
It downloaded and re-installed all the app's of my google backup totally fine and using wi-fi. It play's games fine (but with no sound), i can txt fine, etc. It notices and connects to the network (Virgin Mobile) fine (I turned off wifi and tried downloaded stuff, txts go back and forth, and my phone labels Virgin)
I'm on a stupid 2 year contract and this phone cost $650 at the time I got it. It's knox 0x1 so no warranty to have it repaired. Does ANYONE have ANY idea what might be causing my phone not to play any sound's? I've tried pretty much everything I can think of.
I'd be willing to live with a totally cripples phone ... but it's got to at least work for receiving or sending phone calls and this sound issue crashes the dialer and even if I manage to pickup when it's vibrating before the other person has hung up there's no sound, neither of us can hear each other .
Does ANYONE have ANY idea what could be doing this or how to fix it? I'm so depressed and worried right now that I just a phone I spent a lot of money and am on a stupid contract on :/. I fixed the wifi problem by flashing with a rom that 'makes it' a GT-I9505G, baseband I337MUMUAMDL (v 5.0.1) (vs SGH-I337M, baseband I337MVLUAMDJ (v 4.2.2)), but the same sound and audio/media problem exist's no matter what firmware or version the phone ends up being .
I should have just left it with CM as it was but *sigh* here I am, please help.
masterof1010 said:
I've spent a lot of time now trying to fix my phone and i'm really quite worried.
It's a Samsung Galaxy S4 SGH-I337M (CSC I337MOYAAAMDJ, Baseband I337MVLUAMDJ, version 4.2.2).
I have had CM 10 on it running perfectly fine for about a year. I decided to update it though and didn't know that you could update CM right from the phone , so I downloaded the software from their site onto my phone and onto my PC. Followed the instructions installation froze and didn't move forward for over a day .... so I gave up.
I went looking for and downloaded the phone's stock firmware for both my carrier (Virgin Mobile, Canada) and for Bell's, so I installed TWRP with Odin 3.07 without issue. When I install the stock firmware my WiFi will not turn on.
So i've tried installing several rom's putting them on the SD card and using TWRP on my phone and i've found out that if I use Goldeneye and tell it my phone is an I9505, or hyperdrive (I9505) or at the moment Google Play Edition (JFLTE 5.01, kernel = Googy-Max3) that the WiFI DOES TURN ON as soon as the rom is loaded !!! So I thought I was good, but no
When flashed with either it's stock I337M firmware or these custom I9505 rom's my phone will play no audio. Chrome just crashes if I go to play any music or video. If someone call's, the ringer doesn't work but after several 'rings' my phone start's to vibrate indicating they called (aka the dialer lags out and then crashes). I can make calls too but when I talk the recipient can't hear me, nor I them.
It downloaded and re-installed all the app's of my google backup totally fine and using wi-fi. It play's games fine (but with no sound), i can txt fine, etc. It notices and connects to the network (Virgin Mobile) fine (I turned off wifi and tried downloaded stuff, txts go back and forth, and my phone labels Virgin)
I'm on a stupid 2 year contract and this phone cost $650 at the time I got it. It's knox 0x1 so no warranty to have it repaired. Does ANYONE have ANY idea what might be causing my phone not to play any sound's? I've tried pretty much everything I can think of.
I'd be willing to live with a totally cripples phone ... but it's got to at least work for receiving or sending phone calls and this sound issue crashes the dialer and even if I manage to pickup when it's vibrating before the other person has hung up there's no sound, neither of us can hear each other .
Does ANYONE have ANY idea what could be doing this or how to fix it? I'm so depressed and worried right now that I just a phone I spent a lot of money and am on a stupid contract on :/. I fixed the wifi problem by flashing with a rom that 'makes it' a GT-I9505G, baseband I337MUMUAMDL (v 5.0.1) (vs SGH-I337M, baseband I337MVLUAMDJ (v 4.2.2)), but the same sound and audio/media problem exist's no matter what firmware or version the phone ends up being .
I should have just left it with CM as it was but *sigh* here I am, please help.
Click to expand...
Click to collapse
try with this firmware
lets me see
k thanks i'll try it (once it's slow download is done) and update this post. Looks the same except I guess it's android v5.0.1 (well and it's a different CSC/PDA).
K well i've tried that firmware and it's given me some abnormal problems.
Odin typically just writes in like two minutes and boom done, but when I tried to flash with the firmware you suggested like every 15 seconds it would say ...
"Receive Response from boot -loader"
"Transmission Complete.."
"Now Writing .. Please wait about 2 minutes"
It kept cycling through those 3 messages until it FINALLY finished and it say's PASS but it took 9 min 53 seconds which is like 5 times longer then it's ever taken.
Wheather this is relevant or not i'm not sure just trying to give as much details as I can.
Anyways, after booting the phone the samsung logo came up as usual and usually it takes like 5-10 min sitting at this logo before the phone completes loading, presumably setting up the firmware I imagine.
It's been now sitting at that logo for over 20 minutes and i'm about to try wiping with TWRP the davlic cache/cache/data/internal and either trying again with odin (v3.07) OR
If that contines to not work I might put the tar.md5 on the external SD card and recover a saved backup I have on the SD card (with the stock firmware I had before that doesn't allow Wi-Fi to be enabled nor audio/media to play) and use Mobile Odin Pro .apk (I paid for the pro version) from within that restored recovery to flash the firmware you suggested to my phone again.
This is probably redundant but I just figure I might as well try absolutely everything I can possibly think of with your firmware.
If you have any idea why I might be experiencing these abnormal Odin flashing and/or initial loading conditions of the firmware you (or anybody ) suggested i'd appreciate any advice you can give.
I'm going to try and reflash with Odin on my PC again right now (i'm certain thing's like the USB cable are fine and my PC and phone can transfer data without issue .. but that's why i'm going to try mobile odin if after this next attempt doesn't work either).
I'll keep the thread updated, any and all advice is welcomed and highly appreciated
EDIT: OMG it made a like startup theme sound ... that's the first time it's outputted sound in 3 day's !!! It's at the Samsung screen loading the newly flashed firmware so hopefully that completes because wow my phone made noise finally !! Now to wait, and wait....
It won't go past the Samsung logo. So I guess i'll try Mobile Odin. I don't have much faith but it's worth trying.
Uh the backup of the stock firmware I made won't load ... but the hyperdrive rom did. Sound and the dialer work perfectly fine in this rom now, so I guess thing's are more or less fixed. Even though i've wiped the cache/davlic/internal/data in order to prepare to flash the other firmware or this hyperdrive rom (I wipe it every time) in this rom it's reporting my phone's baseband to be I337MVLUGOC4 which is that of the firmware you suggested ...
I'd still rather not use this rom, I thought it was ok at first but meh i'm going to try to go back to CM (after all this *rolls eyes*), trying to use Mobile Odin to install the firmware that you recommended and that appears to have ... somehow fixed the sound can't detect the model of my phone and is dumping, this is not something that has happened with the app before so I don't think i'll be flashing the firmware you suggested.
If it did something to globally fix the crashing when an app was instructed to play audio as it appears to have I guess i'm going to just go download the full CM now, put it on the SD card and install it with TWRP.
So uh, not 100% there yet but it does appear what you've suggested has solved my problem (because worst case scenario i'll just be stuck with the Hyperdrive rom ... but i'll have a working phone) so thanks so much bud I was quite upset and worried about what I was going to do still paying off a useless phone on a contract i'm stuck with for another year still.
I suppose there's no real need in continuing to update this thread as it appears my problems are solved and all that's left are things i'm doing not to fix anything but just because of personal preference over what rom to use but if you want to know anything more just ask, otherwise thank you so much you saved my ass and i'm very grateful.
Hello, im new to this forum
Ive bought a Samsung Galaxy A5 back in September 2015 to my girlfriend.
At the time i opened the case to see if it was everything ok with it before giving it to her. unfortunately i installed oficial updates in the phone after connecting the device to the internet.
Wanting to give the phone just like ive bought it, i started to making all things wrong. i tried to reset the phone back to the factory reset (using the volume up + home + power buttons) but after that the version that was still installed was the updated one and not the factory one.
Then i tried to download the factory version from here htt p://updato.com/firmware-archive-select-model?r=&v=&q=Galaxy+A5+205 using odin and this guide htt p://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
it was installed but when the phone restarted it never turned back on again. despite being the correct version for my region i believe i installed a variant version and not the factory reset version.
I tried turning the phone on, using recovery mode and download mode keys but the phone never gave any signal again. plugin in the usb in the pc didnt work either.
I ended up buying the same phone since i wasnt able to solve the problem and her anniversary was close and ended up with an extra but damaged phone.
i never tried to get the phone to the warranty because i knew that i was losing the it the moment i tried to use odin.
is there anything else i can try to solve the phones problem? or is this problem unrecoverable?
thanks in advance
I can't tell you if your phone is unrecoverable but I think you had flashed other variant's rom causing your mobile not turning on. I don't see any a500fu on the website you posted. If possible, could you tell me which variant you had flashed. I had ever experienced a hard-brick when my device was accidentally removed while odin was flashing aboot.mbn. The solution was changing the motherboard which didn't cost much. I would recommend you to flash firmware from sammobile and do NOT use 4.4.4 firmware as few friends on this forum had experienced hard-bricks. If you want, try a usb jig.
Try warranty, you can have the chance of getting it repaired.
akil777 said:
I can't tell you if your phone is unrecoverable but I think you had flashed other variant's rom causing your mobile not turning on. I don't see any a500fu on the website you posted. If possible, could you tell me which variant you had flashed. I had ever experienced a hard-brick when my device was accidentally removed while odin was flashing aboot.mbn. The solution was changing the motherboard which didn't cost much. I would recommend you to flash firmware from ="htt p://www .sammobile.com/"]sammobile and do NOT use 4.4.4 firmware as few friends on this forum had experienced hard-bricks. If you want, try a usb jig.
Try warranty, you can have the chance of getting it repaired.
Click to expand...
Click to collapse
It must have been other variant rom.
http s://gyazo. com/7ac9dfe107976eeb802cae50a23b23a1 - here is a screenshot
Samsung Galaxy-A500FU - to get there you need to go to "updato" site (first link), place on the search "Galaxy A5" and select Portugal as "region"
There are 7 options, 6 are for locked phones to the main Portuguese operators and one for unlocked phones (i assume), because it says "Porgugal TPH" - TPH means the phone house witch is a store that sells phones and other electronic equipment.
Despite the phone not being bought at the phone house i assumed it was this rom since there was no other one and the phone is not locked to a particular operator.
Ive checked the site you provided and it as almost the same rom´s as updato and the only one that is not locked to a particular operator is TPH one.
So my only option is to use a usb jig to force the phone into download mode? will that work with or without a motherboad change?
please have in mind that the phone does not respond to any other button or combination of buttons comand and trying to charge the phones battery only produces heat at the phone and charger, nothing else happens.
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.