Related
Hi XDA!!
I am experiencing problems on my Samsung Galaxy S5 Exynos variant (SM-G900H).
It has been soft-bricked. I can clearly say so as it can boot into stock recovery and in download mode, but not in stock 4.4.2.....
It has been bricked due to following the steps mentioned in this thread : s health and xposed
Many videos on youtube ask the viewer to flash stock Samsung Firmware from sammobile.com using odin in download mode.
I have a problem even there.... all versions of odin get stuck on initializing......
Tried on all USB ports.... Kies closed..... basically done everything everybody wrote on XDA.
Any new bright ideas would be appreciated....
Thanks in advance!!:good::good:
skb_twiz said:
It has been soft-bricked. I can clearly say so as it can boot into stock recovery and in download mode,
Click to expand...
Click to collapse
You need to do more reading. A lot more.
You clearly haven't tried everything yet. Nor are you are bricked if you can boot into recovery mode. It sounds like you have messed up the system files preventing a normal boot.
Odin is the most common way of recovering. Use Odin 3.09, ensure that you have disabled anti virus, malware amd firewall software and do not have intensive programs running in the background. If necessary use a different computer.
Flash a full stock firmware, ideally the same version as the current firmware on your phone. But in any event, not an older version and matching your current CSC /carrier /baseband. And you ought to make the effort to find the correct PIT file and flash it at the same time. This insures that you don't have any lingering partition corruption. A forum search will explain all about PIT files. And someone probably has a thread with the actual files too.
It will work. In the worst case, you will just need to find a different PC.
.
fffft said:
You need to do more reading. A lot more.
You clearly haven't tried everything yet. Nor are you are bricked if you can boot into recovery mode. It sounds like you have messed up the system files preventing a normal boot.
Odin is the most common way of recovering. Use Odin 3.09, ensure that you have disabled anti virus, malware amd firewall software and do not have intensive programs running in the background. If necessary use a different computer.
Flash a full stock firmware, ideally the same version as the current firmware on your phone. But in any event, not an older version and matching your current CSC /carrier /baseband. And you ought to make the effort to find the correct PIT file and flash it at the same time. This insures that you don't have any lingering partition corruption. A forum search will explain all about PIT files. And someone probably has a thread with the actual files too.
It will work. In the worst case, you will just need to find a different PC.
.
Click to expand...
Click to collapse
You seriously think that I don't mean it when I said that I had tried everything?? All steps you mentioned have been tried before I read your reply... Anyways, going on a different PC helped... apparently Odin is quite moody.... If it decides it is not going to run on a PC, it simply will get stuck on initialization... hence the solution is to find a PC which has run Odin before... It will work on that PC definitely!!! If you can't find one, try running on all PC's in your vicinity (friend's, family etc). There will be one that can run Odin...
And by the way, I clearly said my phone is "soft-bricked"... It means that I can boot only into recovery or download... not android... so my friend, you are quite wrong in saying that my phone isn't bricked...
Sent from my SM-G900H using XDA Free mobile app
skb_twiz said:
You seriously think that I don't mean it when I said that I had tried everything?? All steps you mentioned have been tried before I read your reply... Anyways, going on a different PC helped... apparently Odin is quite moody.... If it decides it is not going to run on a PC, it simply will get stuck on initialization... hence the solution is to find a PC which has run Odin before... It will work on that PC definitely!!! If you can't find one, try running on all PC's in your vicinity (friend's, family etc). There will be one that can run Odin...
And by the way, I clearly said my phone is "soft-bricked"... It means that I can boot only into recovery or download... not android... so my friend, you are quite wrong in saying that my phone isn't bricked...
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
Did you try a data factory reset/clear the caches in recovery and reboot and go one from there?
gee2012 said:
Did you try a data factory reset/clear the caches in recovery and reboot and go one from there?
Click to expand...
Click to collapse
Yes... but to no avail... anyways... like I said above, flash the stock firmware in download mode again using Odin... If Odin gets stuck, try it on a different PC...
I will not recommend anyone to do data factory reset as
(1) It won't do anything that helps you
(2) If you don't reset your phone, you can still retain your apps and settings after flashing the stock firmware again!!
<i>LOL, here I am, posting solutions to my own problem!!</i>
same
skb_twiz said:
Yes... but to no avail... anyways... like I said above, flash the stock firmware in download mode again using Odin... If Odin gets stuck, try it on a different PC...
I will not recommend anyone to do data factory reset as
(1) It won't do anything that helps you
(2) If you don't reset your phone, you can still retain your apps and settings after flashing the stock firmware again!!
<i>LOL, here I am, posting solutions to my own problem!!</i>
Click to expand...
Click to collapse
I am an exynos man, and have fewer options and waiting for better prospects OR 6 months of purchase to pass before tinkering. Anyway I appreciate u posting the solutions you found for your own problem. See you have gained a THANKS point from me.
suchiqaz said:
See you have gained a THANKS point from me.
Click to expand...
Click to collapse
I have thanked you for thanking me...
For everyone else, this thread will remain open forever even though my S5 is back up and running...
This thread is now no longer limited to the Exynos variant... All are welcome...
Any problem regarding unbricking any S5 can be discussed here and I will try my best to help you...
Sent from my Reborn GALAXY S5
Ok. Im not even exactly sure where to start but im pretty sure someone tried to install a different rom on it and had no idea what they were doing. Here is what i know about the phone.
Galaxy S5
SM-G900F
G900F GSMH
Issues :
IMEI does not exist on the phone.
Volume down does not work (Cannot boot into recovery) I think its a firmware issue and not hardware (IE: the button works, but not detected, could be wrong)
SD Card not detected
Cannot connect to a PC to use ODIN (Doesn't detect it)
Dialer codes do not work, i think it has to do with the IMEI
Ok when i first got it i tried some program called EFS Backup and that is the only program i have got to interact with the phone (It restarted it, lol), also tried ADB, dont know much about it but tried to use it to boot into recovery.
It rebooted it.
Um. not really sure what else to include. Tell me and ill add it. ANY advice would be appreciated.
Of course my goal is to be able to activate and use the phone and install its original IMEI back on it. I know it will take quite a few steps but ANY help would be great.
You can boot into the phone right? Look in settings/general for developer options. If it isn't there scroll down to about phone. Click on baseband version until developer options are enabled and go in and make sure USB Debugging is turned on. That may be why Odin isn't recognizing the phone. It's worth a shot.
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
Actually I think it might be build number that you need to click on multiple times.
You can buy a jig from eBay , just search eBay for "galaxy s5 jig" I've done this on all my galaxy phones, but haven't tried it on my s5 since it's still behaving well. While phone is off, with the battery inserted, connect the jig for a couple of seconds and it will immediately boot the phone straight in the download mode.
Thats not real samsung s5, its a clone, like hdc s5 legend
If it is a clone then nothing on this site will do you any good.
Its easy to restore imei for mtk phone, no big deal
I've never done, all I know is that most programs and files here won't do any good on a clone.
Some answers to the help. Thanks!
Ok.
Metalfan78, i have tried that, but thanks for the advice.
Commodore 64, i looked into that, saw one for 5 bucks. I will probably order one to see if it works.
DaanIt, how can you tell a real Galaxy s5 vs a clone? i would love to know and would love to know whether this is real or not.
kalerido said:
Ok. Im not even exactly sure where to start but im pretty sure someone tried to install a different rom on it and had no idea what they were doing. Here is what i know about the phone.
Galaxy S5
SM-G900F
G900F GSMH
Issues :
IMEI does not exist on the phone.
Volume down does not work (Cannot boot into recovery) I think its a firmware issue and not hardware (IE: the button works, but not detected, could be wrong)
SD Card not detected
Cannot connect to a PC to use ODIN (Doesn't detect it)
Dialer codes do not work, i think it has to do with the IMEI
Ok when i first got it i tried some program called EFS Backup and that is the only program i have got to interact with the phone (It restarted it, lol), also tried ADB, dont know much about it but tried to use it to boot into recovery.
It rebooted it.
Um. not really sure what else to include. Tell me and ill add it. ANY advice would be appreciated.
Of course my goal is to be able to activate and use the phone and install its original IMEI back on it. I know it will take quite a few steps but ANY help would be great.
Click to expand...
Click to collapse
its a fake one ! in ABOUT > MODEL NUMBER it is supposed to show G900F not G900 only ! and secondly the imei sticker inside ...check the printing quality it clearily shows that its fake or clone one
ll_r1d0_ll said:
its a fake one ! in ABOUT > MODEL NUMBER it is supposed to show G900F not G900 only ! and secondly the imei sticker inside ...check the printing quality it clearily shows that its fake or clone one
Click to expand...
Click to collapse
LOL. i can edit the model number! I'm going to assume its not but i must ask anyway.. can anyone else edit that or just me? Also. How can i view the actual hardware specs in this phone to really see if its fake? it wouldnt have the exact processor and stuff in it would it?
Get an app called 'CPU Z'........
For my official 900F, it returns this information.......
If you can't get on to playstore, here's a link to the app from my Dropbox (don't worry, the app is free, so it's NOT warez)......
https://www.dropbox.com/s/jumgfr0n41v70lr/CPU_Z.zip?dl=0
Download it to pc/laptop, extract it (it's in a zip) copy it to a micro sd card, put the card in the phone and 'sideload' the app.....
i really think its fake. the main part of the phone i look at to tell its fake from the outside is the flash, if you see your flash it is a weird square orange flash. on other real Samsung phones the flash is a clear and little bit of orange inside. But its a very nice clone, if you want a note4 clone i can show you wear to buy one.
Install universal mtk drivers, use 'Mobileuncle mtk tools' from market for imei repair, use 'mtkdroidtools' for phone root, backup, etc.
Its easy to spot fake, clone led flash is different. Just compare it
kalerido said:
LOL. i can edit the model number! I'm going to assume its not but i must ask anyway.. can anyone else edit that or just me? Also. How can i view the actual hardware specs in this phone to really see if its fake? it wouldnt have the exact processor and stuff in it would it?
Click to expand...
Click to collapse
U cannot edit the model number and simply use CPU-Z to find the truth
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app
celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.
Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app
Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.
www.sammobile.com/firmwares/
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit
3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.
So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse
HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!
Ok so I'm not sure where to put this thread and please forgive my bad grammar and punctuation if I have any. I already read some threads on this forum about a problem like mine and tried to follow the instructions to get back into my phone, but none of it worked so....
I have a Samsung Go Prime that I bought from Wal-Mart for around $100. I rooted it, and got the message "unauthorized software has been found on your phone, please take it to nearest AT&T etc etc". So I did just that, took it to AT&T, called up Samsung customer care on the phone, and took the phone to some sort of Samsung representative or worker person in Best Buy and nobody seems to be able to help me. I downloaded Odin and Philz Touch and tried to flash that and I kept getting Nand fail. I tried Kies and evidently Sammobile website doesn't seem to have the firmware I need either.
Somebody plleeeaassee help me. I had to pay another $100 just to get another phone so now I feel like I wasted $100 for a phone that wont work now. Maybe I didn't use Odin or Philz Touch firmware properly or didn't follow a certain instruction correctly at some point?
Any help would be massively appreciated.
Kies does work, just go to Tools > Firmware Upgrade and Initialisation and enter the serial number, its gonna say not supported but it works Ive done it
Sent from my SM-G935T using Tapatalk
marioca said:
Kies does work, just go to Tools > Firmware Upgrade and Initialisation and enter the serial number, its gonna say not supported but it works Ive done it
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I tried that and after clicking for it to start it again said something like "please check the serial number" etc like I put in the incorrect number. I'm pretty sure what I put in was the correct serial number. It was on the sticker under the battery....
model: SM-G530A
SN: R28H30GVPCN
I'm pretty sure your phone is bricked, nand fail was the superbrick error on the i9100 (Galaxy S2 Int) if I'm remembering correctly.
If I'm right, sorry man :/
Anybody know how to fix the nand fail? Anything I can flash to fix it?
When I tried to flash Philz Touch I read in one of the threads that I had to do something like putting the file in some kind of folder (might have been called tar tool) and click a certain batch.bat file. i tried that and nothing happened, so I just loaded the Philz Touch file directly into Odin.
Did I make a mistake somewhere? Is there anything at all that I can do to fix this? If not, then how and where would I find the contact info and address of the manufacturer so I can send the phone in for fixing?
Hi guys!
I would just like to start by apologizing for making another thread about a bricked note4, however I have read about so much I don't know which advice to go with anymore. I'm also a complete novice when it comes to this.
So long story short, my note 4 started playing up and lagging, eventually not turning back on at all. After endless attempts using odin and flashing what I seemed to have thought was the right firmware, it whittled down to about 1 in 5 attempts of trying to enter download mode (using the buttons) on the phone actually working. Now its completely bricked...no power, no download mode, nothing!
Just like to reiterate, I'm a complete novice,sorry if I'm not making sense, my knowledge doesn't go further than articles and google!
I have tried using kies to recover my phone and it cant recognize it...
I have read about using adb to get my phone into download mode, but I couldn't understand the explanation given well enough to use it...
I bought a 16gb micro sd card and have tried writing an unbrick image to it but I get no response off my phone, also tried another file, possibly sdc? cdc? cant quite remember, but that failed too.
I don't even know if the files I'm using are correct, I got them from a forum on here.
I'm at a loss!
The only hope I have left is if someone is able tell me if any steps I have tried are correct, and possibly provide me with the correct unbrick image?
Also, when I plug my phone into my computer via usb, there is a noise that sounds but nothing else happens, don't know if these means anything. As far as I'm aware I also have correct drivers installed.
Sorry about the long explanation!
Any help is greatly appreciated!
Thanks in advance.
Lucy.
Only logical result from your explanation is you have a hardware problem.
I dont think you are gonna be able to solve it with software...
Time for service visit i guess..
Turkawa said:
Only logical result from your explanation is you have a hardware problem.
I dont think you are gonna be able to solve it with software...
Time for service visit i guess..
Click to expand...
Click to collapse
Thanks for the reply!
I hope that's not the case forgot to mention,when I plug my phone into a computer and go into device manager, it shows qhsusb_bulk...if this means anything to you?
Lucyhenn123 said:
Thanks for the reply!
I hope that's not the case forgot to mention,when I plug my phone into a computer and go into device manager, it shows qhsusb_bulk...if this means anything to you?
Click to expand...
Click to collapse
Nope.. I have no idea.. Sorry
Try the sd recovery method .
First you can try to flash the pit partion .
You can find that on xda .
Just search for note 4 pit files.
Download the n910f pit file with correct csc.
TRY flashing via download mode.
Try flashing .
Use this guide for using sd card to get into download mode if you cant access download mode
There is a method for http://cloud.tapatalk.com/s/57e756f41dc6e/read me for brick fix.txt
Reporting via N910G