Hi, I have a bricked I337 and I would like to have some opinions before I give up trying to fix it.
Here is a short version of what I have done.
The phone came to me with null IMEI which I was trying to fix. After trying several tools, the phone became dead, no boot, nothing. At this point I went for a JTAG solution. JTAG software detected it well, and repair procedure was successfull as reported by JTAG software, phone was still dead.
With the help of the JTAG software programmer I got an M919 full dump which I tried to write to phone, after 4 hours of writing the dump, battery completely died at 95% of writing. I recharged battery and after that moment have been unable to connect with phone via JTAG. JTAG software detects its hardware ID but can't initialize phone for writing.
I have read every unbrick thread from other phones, have tried QPST with many files I have found on the way and all I get are errors. So I have been unable to communicate with phone.
Is this finally a faulty phone? Have anyone have another idea?
y3kt said:
Hi, I have a bricked I337 and I would like to have some opinions before I give up trying to fix it.
Here is a short version of what I have done.
The phone came to me with null IMEI which I was trying to fix. After trying several tools, the phone became dead, no boot, nothing. At this point I went for a JTAG solution. JTAG software detected it well, and repair procedure was successfull as reported by JTAG software, phone was still dead.
With the help of the JTAG software programmer I got an M919 full dump which I tried to write to phone, after 4 hours of writing the dump, battery completely died at 95% of writing. I recharged battery and after that moment have been unable to connect with phone via JTAG. JTAG software detects its hardware ID but can't initialize phone for writing.
I have read every unbrick thread from other phones, have tried QPST with many files I have found on the way and all I get are errors. So I have been unable to communicate with phone.
Is this finally a faulty phone? Have anyone have another idea?
Click to expand...
Click to collapse
Wow, sorry to hear this. the battery went dead before jtag finished? ouch. QPST will not help for this, a phone will still boot with no IMEI, this is not good, may want to start a warranty ticket on it. I have a jtag box, so there is a release update for the G4 for it? I did not know this, haven't check in awhile, pull the battery for a good while, replace and charge all the way, and give it one more shot. Sorry bro.
TheAxman said:
Wow, sorry to hear this. the battery went dead before jtag finished? ouch. QPST will not help for this, a phone will still boot with no IMEI, this is not good, may want to start a warranty ticket on it. I have a jtag box, so there is a release update for the G4 for it? I did not know this, haven't check in awhile. pull the battery for a good while, charge all the way, and give it one more shot. Sorry bro.
Click to expand...
Click to collapse
This is exactly what I didn't want to hear :crying:
I have used Riff as JTAG solution.
Unfortunately warranty is not an option for me so I will pull the battery for a couple of days before I try again. At this point it seems is really dead.
I have found many files for QPST that are supposed to do everything to a dead phone, even a command line utility for the same purpose, with some hex and mbn files, but as I said they all failed, it seems to me that eMMC chip is not working at all.
I'll keep you updated if I ever find a way to fix this phone.
y3kt said:
This is exactly what I didn't want to hear :crying:
I have used Riff as JTAG solution.
Unfortunately warranty is not an option for me so I will pull the battery for a couple of days before I try again. At this point it seems is really dead.
I have found many files for QPST that are supposed to do everything to a dead phone, even a command line utility for the same purpose, with some hex and mbn files, but as I said they all failed, it seems to me that eMMC chip is not working at all.
I'll keep you updated if I ever find a way to fix this phone.
Click to expand...
Click to collapse
I did not know this, I will keep that in mind for future ref. Really hope you get it going.
Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
y3kt said:
Hi, I have a bricked I337 and I would like to have some opinions before I give up trying to fix it.
Here is a short version of what I have done.
The phone came to me with null IMEI which I was trying to fix. After trying several tools, the phone became dead, no boot, nothing. At this point I went for a JTAG solution. JTAG software detected it well, and repair procedure was successfull as reported by JTAG software, phone was still dead.
With the help of the JTAG software programmer I got an M919 full dump which I tried to write to phone, after 4 hours of writing the dump, battery completely died at 95% of writing. I recharged battery and after that moment have been unable to connect with phone via JTAG. JTAG software detects its hardware ID but can't initialize phone for writing.
I have read every unbrick thread from other phones, have tried QPST with many files I have found on the way and all I get are errors. So I have been unable to communicate with phone.
Is this finally a faulty phone? Have anyone have another idea?
Click to expand...
Click to collapse
i have the same problem but i need an imge file to write it im my device (m919) do u have one?
shadigsm said:
i have the same problem but i need an imge file to write it im my device (m919) do u have one?
Click to expand...
Click to collapse
Yes, I do have an M919 dump image from a working phone you can use.
Here you have the link http://jtagbox.com/downloads/m919/M919.rar
y3kt said:
Hi, I have a bricked I337 and I would like to have some opinions before I give up trying to fix it.
Here is a short version of what I have done.
The phone came to me with null IMEI which I was trying to fix. After trying several tools, the phone became dead, no boot, nothing. At this point I went for a JTAG solution. JTAG software detected it well, and repair procedure was successfull as reported by JTAG software, phone was still dead.
With the help of the JTAG software programmer I got an M919 full dump which I tried to write to phone, after 4 hours of writing the dump, battery completely died at 95% of writing. I recharged battery and after that moment have been unable to connect with phone via JTAG. JTAG software detects its hardware ID but can't initialize phone for writing.
I have read every unbrick thread from other phones, have tried QPST with many files I have found on the way and all I get are errors. So I have been unable to communicate with phone.
Is this finally a faulty phone? Have anyone have another idea?
Click to expand...
Click to collapse
Hi, I was wondering if you got your problem solved, I too have a Galaxy S4 M919 which came to my shop also with IMEI null, I also tried to repair it with RIFFBOX and the phone is dead now. I want to know if you repaired your phone and how you did it. Thank you very much. I also tried the M919 full dump you posted but the riffbox wont recognize it.
frankjasmin said:
Hi, I was wondering if you got your problem solved, I too have a Galaxy S4 M919 which came to my shop also with IMEI null, I also tried to repair it with RIFFBOX and the phone is dead now. I want to know if you repaired your phone and how you did it. Thank you very much. I also tried the M919 full dump you posted but the riffbox wont recognize it.
Click to expand...
Click to collapse
Hi, yes, I did repair the phone with RIFF BOX and a dump from a working phone the RIFF BOX programmer sent me.
y3kt said:
Yes, I do have an M919 dump image from a working phone you can use.
Here you have the link http://jtagbox.com/downloads/m919/M919.rar
Click to expand...
Click to collapse
Wow, they usually don't do that, keep that puppy in a safe location
Good deal.
y3kt said:
Hi, yes, I did repair the phone with RIFF BOX and a dump from a working phone the RIFF BOX programmer sent me.
Click to expand...
Click to collapse
Can you share the dump for the I337?
I'm having the same problem with my S4.
Thanks a lot...
I'm am in a loop, how do I flash from odin?
realgadawg said:
I'm am in a loop, how do I flash from odin?
Click to expand...
Click to collapse
You don't need to use ODIN to fix a boot-loop, just use the 3-button combo to go into recovery and flash a backup or a ROM (Following proper wiping steps).
y3kt said:
Hi, yes, I did repair the phone with RIFF BOX and a dump from a working phone the RIFF BOX programmer sent me.
Click to expand...
Click to collapse
can you share a working link with the dump for m919 please i need one to repair my dead i337
I have a RIFF BOX. I have an M919 here that is completely dead. I tried 3 P.C.'s that won't even detect it. RIFF doesn't see it either. Any ideas on what my options are ? This is driving me crazy, please help
Related
after using the "Odin3 One-Click Downloader" my i9000 only loops the att logo on and off, recovery mode and download mode are no longer working... had anyone experienced this?
well this is f...ed up..... my i9000 was unbranded, and that one click crap must have flashed the captivate fw or smth, should i let my phone die in peace now?
There are different oneclick apps for different branded SGSs. Which one did you download? Sounds like you downloaded the AT&T version.
You have to boot your phone into download mode again to flash the correct ROM for your specific phone. There are many different ways to get the phone into download mode. Check the dev forum or instructions.
foxbat121 said:
There are different oneclick apps for different branded SGSs. Which one did you download? Sounds like you downloaded the AT&T version.
You have to boot your phone into download mode again to flash the correct ROM for your specific phone. There are many different ways to get the phone into download mode. Check the dev forum or instructions.
Click to expand...
Click to collapse
"[STOCK ROM] Odin3 One-Click Downloader and Drivers" I've downloaded this one... and i cant boot into download mode, the 3 button methods died on me
Its for captivate.... And your phine iscompletely bricked. Needs a new mother board.
Why people download weird **** from untrusted sources?
Sent from my GT-I9000 using XDA App
Phone is completely bricked. Happened to me, and a few others too. Seems that these one-click odin downloaders do more harm than good. Hahaha...
Anyway, phone is bricked. Samsung replaced the motherboard for me. Luckily it's under warranty at no cost to me..
Seifer1975 said:
Phone is completely bricked. Happened to me, and a few others too. Seems that these one-click odin downloaders do more harm than good. Hahaha...
Anyway, phone is bricked. Samsung replaced the motherboard for me. Luckily it's under warranty at no cost to me..
Click to expand...
Click to collapse
replace the motherboard? what the fudge.. i gave it to a local repair shop (samsung recommended one) and well.. they will try to reflash it or smth.. if that wont work, how much would replacing the motherboard cost? i'm out of warranty
dupel said:
Its for captivate.... And your phine iscompletely bricked. Needs a new mother board.
Why people download weird **** from untrusted sources?
Click to expand...
Click to collapse
What untrusted source? He went into Captivate forum here in XDA to download Captivate stock ROM. What do you think the outcome will be?
it might cost you around $150 or so, if i remember reading a recent post about a guy replacing his mb too. I think he had the same problem as you.
SwiftPolar said:
it might cost you around $150 or so, if i remember reading a recent post about a guy replacing his mb too. I think he had the same problem as you.
Click to expand...
Click to collapse
could you find that post for me? i cant seem to find it myself...
well, so far, i've found out that by flashing the i9000 (unbranded) with a captivate FW remapped all the buttons except for the power button, so download mode or recovery mode is impossible via any button combination. But if the phone does show something on the screen, its still only semi-bricked, in my case, its stuck at the bootloader. its fixable with JTAG ... i hope the service i took it to has a jtag device and will reflash to the i9k FW. and it would only cost me 10$ for the repairs
who had a similar experience?
I had exactly the same problem, after updating my phone through kies which failed halfway through i downloaded odin which at the time i didn't know was the wrong one and not for the i9000. in the end i had to get a new phone.
Sent from my GT-I9000 using XDA App
aaronlivo said:
I had exactly the same problem, after updating my phone through kies which failed halfway through i downloaded odin which at the time i didn't know was the wrong one and not for the i9000. in the end i had to get a new phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
were you under warranty? did you try to repair it ?
well my sgs is not fully bricked, it does not need a new motherboard... it just needs to be reflashed with jtag or smth >.<
a fully bricked (faulty) device would not turn on at all
allright, so just by flashing the phone with that one click odin crap, the repairs are going to cost me 250$
Looks like I have a hard brick with the device manager reporting qhsusb_dload. This appears to be related to corrupt partitioning, the last thing I flashed was a zip package in CWM and rebooted the phone and it didn't reboot by vibrating and showing the Samsung logo, it just was black.
I pulled the battery and attempted to power it on again and I was getting no response from the device, I plugged it into my pc and that's when I saw the qhsusb_dload missing driver which I found drivers for, but it doesn't help me.
My question is, is this something JTAG can fix? I don't want to take a chance on warranty replacement and getting a MF3 factory phone since I wont be able to Loki. Any info would be appreciated.
ChaosMinionX said:
Looks like I have a hard brick with the device manager reporting qhsusb_dload. This appears to be related to corrupt partitioning, the last thing I flashed was a zip package in CWM and rebooted the phone and it didn't reboot by vibrating and showing the Samsung logo, it just was black.
I pulled the battery and attempted to power it on again and I was getting no response from the device, I plugged it into my pc and that's when I saw the qhsusb_dload missing driver which I found drivers for, but it doesn't help me.
My question is, is this something JTAG can fix? I don't want to take a chance on warranty replacement and getting a MF3 factory phone since I wont be able to Loki. Any info would be appreciated.
Click to expand...
Click to collapse
Yes, unfortunately it's down to JTAG with a RIFF box or similar equipment.
GiantBallSack said:
Yes, unfortunately it's down to JTAG with a RIFF box or similar equipment.
Click to expand...
Click to collapse
Figures... now I gotta find someone that can do the JTAG/RIFF repair.
ChaosMinionX said:
Figures... now I gotta find someone that can do the JTAG/RIFF repair.
Click to expand...
Click to collapse
I found this on GSM-Hosting, and was reported to be a Samsung driver. If the driver installs successfully, QPST will probably see the phone, but I doubt that ODIN would. I still think you are down to JTAG, but here's the driver if you want to mess around with the phone some more
GiantBallSack said:
I found this on GSM-Hosting, and was reported to be a Samsung driver. If the driver installs successfully, QPST will probably see the phone, but I doubt that ODIN would. I still think you are down to JTAG, but here's the driver if you want to mess around with the phone some more
Click to expand...
Click to collapse
Thanks, I had the drivers after looking on google so now it shows up as Qualcomm HS-USB QDLoader 9008 (COM6). ODIN so far doesnt appear to be able to see the phone any longer. Will QPST be able to do anything?
ChaosMinionX said:
Thanks, I had the drivers after looking on google so now it shows up as Qualcomm HS-USB QDLoader 9008 (COM6). ODIN so far doesnt appear to be able to see the phone any longer. Will QPST be able to do anything?
Click to expand...
Click to collapse
If you had a full flash file, you could flash it with QPST and unbrick it. Those files are extremely hard to come by, only the service centers seem to have them. It may be possible to backup a different S4 and flash it but you may end up with an identical copy of the other person's phone. My only experience with QPST is changing the service programming for CDMA phones. Hard-bricks I had equipment for. I have it installed, I'll see if I can pull a dump of my phone that can be flashed, but I still wonder about the EFS partitions.
GiantBallSack said:
If you had a full flash file, you could flash it with QPST and unbrick it. Those files are extremely hard to come by, only the service centers seem to have them. It may be possible to backup a different S4 and flash it but you may end up with an identical copy of the other person's phone. My only experience with QPST is changing the service programming for CDMA phones. Hard-bricks I had equipment for. I have it installed, I'll see if I can pull a dump of my phone that can be flashed, but I still wonder about the EFS partitions.
Click to expand...
Click to collapse
Alright thanks, yeah I can get the phone in QPST its listed in Download mode. Wonder if a dump from a working phone could fix it?
ChaosMinionX said:
Alright thanks, yeah I can get the phone in QPST its listed in Download mode. Wonder if a dump from a working phone could fix it?
Click to expand...
Click to collapse
It's possible. Check your PM.
JTAG service only. Period
Sent from my GT-I9505 using xda premium
TheAxman said:
JTAG service only. Period
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Anyone on the forum do JTAG service? I dont want to take chance of ATT warranty sending me a MF3 phone.
GiantBallSack said:
It's possible. Check your PM.
Click to expand...
Click to collapse
I've done a lot of research and experimenting in this area, because I'm currently stuck in a similar situation with my phone stuck in QPST mode. If you have any knowledge about a working .hex file for this device, please let me know (PM me if needed?).
TheAxman said:
JTAG service only. Period
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Pretty much. Unfortunately in my case, JTAG appears not even a viable option. Might be different for the OP, however. Probably has a different "style" of hard-brick.
ChaosMinionX said:
Anyone on the forum do JTAG service? I dont want to take chance of ATT warranty sending me a MF3 phone.
Click to expand...
Click to collapse
There's a few people on the forums with JTAG boxes offering service. Perhaps the most reputable would be @connexion2005 - his website is mobiletechvideos.com. Costs $60 for an S4, plus extras (rush shipping, rush processing, data recovery, etc.), last I looked.
Only problem is, if you're hard-bricked because of the MF3 update somehow, you might be SOL. Last I heard, mobiletechvideos.com sent back a phone to another XDA member, unfixed for this reason. Still waiting to hear the whole story on this, so I wouldn't discredit mobiletechvideos.com yet. They're very good at what they do, and they've repaired thousands of hard-bricks on many different models of phones.
Aou said:
I've done a lot of research and experimenting in this area, because I'm currently stuck in a similar situation with my phone stuck in QPST mode. If you have any knowledge about a working .hex file for this device, please let me know (PM me if needed?).
Click to expand...
Click to collapse
We worked on a good bit today, and QPST just wouldn't cooperate with the phone in anyway. It wouldn't write aboot.mbn like the phone needs. A full flash in .mbn format is needed.
GiantBallSack said:
We worked on a good bit today, and QPST just wouldn't cooperate with the phone in anyway. It wouldn't write aboot.mbn like the phone needs. A full flash in .mbn format is needed.
Click to expand...
Click to collapse
Correct. Also need an appropriate .hex file too for certain operations in QPST.
I've tried flashing certain .mbn files that are explicitly designed to convert the entire device into a glorified 16gb, unformatted flash drive (which is repairable using very careful DD commands from a linux PC), but I can't get the device that far. Problem is, the only .hex and .mbn files out there for the MSM8960 are not signed, and the device refuses to accept them.
Aou said:
Correct. Also need an appropriate .hex file too for certain operations in QPST.
I've tried flashing certain .mbn files that are explicitly designed to convert the entire device into a glorified 16gb, unformatted flash drive (which is repairable using very careful DD commands from a linux PC), but I can't get the device that far. Problem is, the only .hex and .mbn files out there for the MSM8960 are not signed, and the device refuses to accept them.
Click to expand...
Click to collapse
I didnt have MF3 official on there, the only files from MF3 I used were the Modem, and Tasks's latest AOKP had MF3 RIL. I wonder if I am in the same boat as you?
I do however have a replacement device on its way tomorrow, I wonder if ATT has officially gone to MF3 for replacement warranty devices yet?
ChaosMinionX said:
I didnt have MF3 official on there, the only files from MF3 I used were the Modem, and Tasks's latest AOKP had MF3 RIL. I wonder if I am in the same boat as you?
I do however have a replacement device on its way tomorrow, I wonder if ATT has officially gone to MF3 for replacement warranty devices yet?
Click to expand...
Click to collapse
I certainly hope they haven't. If they have, I'd rather pay the $199 deductible on a new device through insurance instead!
Aou said:
I certainly hope they haven't. If they have, I'd rather pay the $199 deductible on a new device through insurance instead!
Click to expand...
Click to collapse
You and me both! I would just assume sell the warrantied device and pay difference to get a Google Edition, I am not real keen on HTC phones. Guess we will see what they ship me when it arrives tomorrow!
Aou said:
Correct. Also need an appropriate .hex file too for certain operations in QPST.
I've tried flashing certain .mbn files that are explicitly designed to convert the entire device into a glorified 16gb, unformatted flash drive (which is repairable using very careful DD commands from a linux PC), but I can't get the device that far. Problem is, the only .hex and .mbn files out there for the MSM8960 are not signed, and the device refuses to accept them.
Click to expand...
Click to collapse
nevermind, sorry
Well good news! My replacement from warranty came today and its still running MDL, so guess I will be returning the bricked device. Sigh of relief seeing MDL and not MF3 thats for sure :good::good:
ChaosMinionX said:
Well good news! My replacement from warranty came today and its still running MDL, so guess I will be returning the bricked device. Sigh of relief seeing MDL and not MF3 thats for sure :good::good:
Click to expand...
Click to collapse
man you sure lucked out there
GiantBallSack said:
It's possible. Check your PM.
Click to expand...
Click to collapse
Hey, could you tell me how it is possible ?
i have a I9505 in QPST DL mode and i don't know how to get a dump from a working model !
thx !
Ok long story short I flashed something on my ls980 I believe my efs. Got wiped. I have no iemi. Unknown baseband. No service whats hoever I have tried LG flash tool and my stock tot no luck cback stock no root my phone restats every minute or so I can't find my efs backup. From io rootf. Can any body help I've got qpst. But don't know what to do. Please help
Rite now I'm on zv8. I had it on the t mobile Tom for straight talk
Also I can only get charge only and dowliad mode to respond USB please someone help
Sorry to break to you, but I don't think there's a solution at this point. I was in the same situation last month and there wasn't a solution through xda. I tried, believe me.
Try your best to wipe your phone and remove root status, and then claim LG warranty. The warranty was rejected the first time (as well as unprofessional not-returning-calls to anybody or picking up the phone), but I posted on their Facebook page and got the "executive" team to contact me. Under a week later, I was sent a new/refurbished phone, box and all.
Most stories of LG warranty are terrible though, so best of luck to you. I dealt with LG Canada.
Can you get into recovery at all? I take it you don't have a Nandroid backup? What rom were you trying to flash?
cheetahcat79 said:
Can you get into recovery at all? I take it you don't have a Nandroid backup? What rom were you trying to flash?
Click to expand...
Click to collapse
I got rooted stock. Recovery zv8 I talked to a boy with sprint and it is most def a efs issue as for just give up I wont I've unbricked every bricked done I've come across I got diagnosis mode on but I don't know how to set up my qualcom USB modem settings its a ## number but I can't find it n e where I have download mode but tot restores are the same I cannot get qpst to recognized I can get my PC to connect every other USB mode mtp ptp charge only ect I need help restoreing my efs I have my original box with alleluia my numbers plus iemi calc. Please any body
TheMadScientist420 said:
I got rooted stock. Recovery zv8 I talked to a boy with sprint and it is most def a efs issue as for just give up I wont I've unbricked every bricked done I've come across I got diagnosis mode on but I don't know how to set up my qualcom USB modem settings its a ## number but I can't find it n e where I have download mode but tot restores are the same I cannot get qpst to recognized I can get my PC to connect every other USB mode mtp ptp charge only ect I need help restoreing my efs I have my original box with alleluia my numbers plus iemi calc. Please any body
Click to expand...
Click to collapse
Did you make a backup of your efs before rooting and flashing roms?
doktor buknasty said:
Did you make a backup of your efs before rooting and flashing roms?
Click to expand...
Click to collapse
I did and my dumb ass deleted it I have all my nummbers on my original box to reflash them just can't get qpst to reconize all other USB modes work half the time
http://forum.samdroid.net/f38/guide-recover-your-imei-9-steps-vaskodogamagmail-xda-6008/
See if there's anything helpful in here...
yeah, well, go back to exact situation you made the backup(romversion on phone/etc), then restore it with the tool version you made backup with. it will require you to probably have the efs backup in the location its backed up to. my tip would be to always back it up manually somewhere else as well as remember where you put it.
but if you cant find it you did a lousy backupjob right? How is that warrantee claimable.... ?seems user error to me
I understand that u are a senior men but apparently u don't read my backup is gone I've posted that 3 or 4 times now and I know it not claimable
TheMadScientist420 said:
I understand that u are a senior men but apparently u don't read my backup is gone I've posted that 3 or 4 times now and I know it not claimable
Click to expand...
Click to collapse
sorry. then there is not much you can do. There is probably a special way thats not allowed to talk about here. google about recovering imei without backup and lg g2
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
Hi Guys.
This is a Mediatek Helio X25 Redmi Pro and it came to me bricked from its owner who tried to root it the wrong way. I managed to flash an official rom and bring it back to life but as apparently is the case with these phones, the nvram has been corrupted/rewritten and there's no Imei numbers on the phone, which means no calls and stuff. WiFi works fine. I've already had permission to unlock the bootloader but obviously I can't do anything about it since the software won't ID the device. I believe I might be able to flash a backup of nvram.bin, but I don't have one from this phone, which is why I am posting this here, hoping that maybe one of you can help me by sending me a copy of his own Redmi Pro nvram.bin file. Of course I only need it to get the thing back in the system, after which I can unlock it and use the original Imei numbers. Or if someone has another suggestion, I would greatly appreciate it.
Thanks in advance.
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Binnylaw said:
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Click to expand...
Click to collapse
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
nsterjo said:
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
Click to expand...
Click to collapse
Tried this method?
http://en.miui.com/thread-411112-1-1.html
Sent from my Redmi Note 4 using Tapatalk
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Binnylaw said:
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Click to expand...
Click to collapse
I have tried maybe 3 different versions of Sp Flashtool, including this one. I usually get a timeout message. But I will try again. Is there any specifics I should observe regarding the mdb files I need to use? I have tried all the ones that come with the roms I've tried, but without luck.
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
No, you understood fine; it was me who typed SP Flashtool instead of SN Writer, which was what I meant. Everything else is as I wrote. I have tried 3 different versions of SN Writer, I connect fine and it starts the procedure following the same instructions you mentioned, but it stops half way, giving me an error message. I have tried different combinations of MDB and APDB files from several different ROMs I've downloaded, but they all fail. I'm not very familiar with these things but I can follow instructions and am quick to learn. Still, I have no idea why SN Writer or Maui Meta are not working. I tried to download an nvram.bin file I got from the internet with SP Flashtool, but it would not accept it as it was for Helio X20 I believe, which is why I was hoping someone would make available a copy of nvram.bin for this particular phone. I will also try to make a deepflash cable, hoping that might get me into EDL after which I can use MiFlash to reflash a new official Rom, but I don't know if it will work.
help please
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
Hi there, please can you tell me where I find the files (mdb and adb)? Are they somewhere on the phone's firmware? Or somewhere in the rom i flashed?
I'm a beginner having a very similar issue having flashed a rom in rescuing a bricked phone and now have invalid IMEI numbers.
Thanks so much