Hi
I don't know how but my imei has been deleted
I flash back the stock firmware using rsdlite but it's the same
There is a solution to restore my old imei ?
edit
Rom JB --> Rom ICS --> imei 0 --> recover it http://forum.xda-developers.com/showthread.php?t=1960918
Yes, you can repair the IMEI using RadioComm or QPST to write it back to NV Item 550 NV_UE_IMEI_I.
You need to use DIAG mode access to read/write to the NVM(Non Volatile Memory) of the radio chipset.
I don't have time before work to write up the complete method, but you can definitely fix this and I will try to post the method with links tonight after work.
You will need the latest version of RadioComm and Motorola drivers installed on your PC or QPST 2.7 build 378 or later.
Thank you it would be really great to do that! I think it's going to happen to other people too
So I try and if I can't restore my imei I will exchange it against a new tomorrow
I am not certain it will work on your device with this chip set so I am discussing it with a knowledgeable friend.
I don't have an HD, I have a dev edition Razr M, so I can't verify everything myself for your device.
Edit: In the meantime, it would be a good idea to explain everything you have done leading up to this so we can establish better information about your circumstances for other users.
wipe data, wipe cache, flash ICS SFR rom with rsdlite, I tried to root from recovery with .zip (doesn't work), root with motofail2go, and update JB from recovery (root ok)
I think maybe it's because of that : when I flashed ICS rom with rsdlite at the end of flashing the phone reboot alone... so I unplogged it without waiting the "finish state" on rsdlite...
Stange thing, the phone still worked some hours although I rebooted it several times
The night, no network, and I saw that I had no imei
I hope you enjoy my "google trad" English :cyclops:
i have do the same and i don't have any probleme with my iemi.
PM me for how you get root with JB.
Thanks
Update: After more research, it looks like I was wrong and it is not possible to write/repair IMEI on this phone, at least with the tools we currently have.
I have spoken with a good friend and tried myself in various ways and the NV Item is read only.
I suggest you return your phone. Although it's possible we may find a solution, it is not likely to be in any time frame you would be willing to wait for.
cellzealot said:
Update: After more research, it looks like I was wrong and it is not possible to write/repair IMEI on this phone, at least with the tools we currently have.
I have spoken with a good friend and tried myself in various ways and the NV Item is read only.
I suggest you return your phone. Although it's possible we may find a solution, it is not likely to be in any time frame you would be willing to wait for.
Click to expand...
Click to collapse
Ho my god i have the same problem, but don't forget... bootloader unlock => warranty void ! OMG plz try help us :crying:
cellzealot said:
Update: After more research, it looks like I was wrong and it is not possible to write/repair IMEI on this phone, at least with the tools we currently have.
I have spoken with a good friend and tried myself in various ways and the NV Item is read only.
I suggest you return your phone. Although it's possible we may find a solution, it is not likely to be in any time frame you would be willing to wait for.
Click to expand...
Click to collapse
Okay we are now 4 persons with the same problem I hope you will succeed!!
i have same thing....
BE CAREFUL, if you flashed JB, DON'T reflash ICS after otherwise the phone is dead (imei : 0)
android69800 said:
BE CAREFUL, if you flashed JB, DON'T reflash ICS after otherwise the phone is dead (imei : 0)
Click to expand...
Click to collapse
Too late... Mine's dead too...
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
Anyone tried flashing another ROM than SR ICS to see if it somehow restores the IMEI? (I am currently flashing ICS Orange...)
I went back to ics. Had no signal. So did a wipe and flashed ics again and my signal is fine now
Sent from my XT925 using xda premium
---------- Post added at 02:39 AM ---------- Previous post was at 02:37 AM ----------
Imei still shows 0 though
Sent from my XT925 using xda premium
madmonkey57 said:
Too late... Mine's dead too...
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
Anyone tried flashing another ROM than SR ICS to see if it somehow restores the IMEI? (I am currently flashing ICS Orange...)
Click to expand...
Click to collapse
Tried plenty of flash/wipe combinations, but can't get my IMEI back...
All right, I give up... Returning the phone to Motorola...
I changed mine on the coming week.
I am disgusted.
it will do a very good mp3 player ......... *PAN* *Head Shot*
The fact that it can be blanked by some bug suggests a vulnerability itself, so there is some hope for a solution.
A similar bug has presented itself on the Samsung GS III but because Samsung security is much less "secure" on their devices, it can be fixed by various NV access methods.
Motorola, for better or worse, has always had much more rigorous security protocols on their devices, in particular relating to ESN/MEID/IMEI repair.
If we can learn the mechanism of the bug that corrupts/erases it then we may learn how to fix it.
Flash back up to JB, IMEI will still be 0 but radio will function again
Sent from my XT925 using xda app-developers app
I'm return ics to jb no radio.
Envoyé depuis mon XT925 avec Tapatalk
My IMEI is currently @ 0 however with the JB upgrade, I can, at the very best, establish a HSPA+ connection.
LTE (although shown as an option) no longer works.
I'm curious if this is something that could be resolved with Cygwin & Dsixda's Kitchen (e.g. use the JB modem firmware on ICS)?
Best of luck to everyone with this issue. Hopefully we'll have a resolve in a few days.
Related
Hello, i bought myself an att motorola atrix 2 used phone it was not rooted, it had gb 2.3.6 and imei and baseband unknown... I FXZ back to stock 2.3.5 with rsd lite and att fxz files, but that did not fix the problem i'm still stuck in airplane mode and imei and basenband unknown. please help
maybe your mobile NVRAM is corrupted,i have no experience in TI Radios and NVRAM settings/tools ,i was in same situation in my LG GW620(qualcomm) and fixed it,it was a great thing,i'll check and try this in TI.
---------- Post added at 08:10 AM ---------- Previous post was at 08:01 AM ----------
try fxz back to the correct spl (related to your provider if your phone is branded)
with "TI Blank Flash" option in rsd lite.
---------- Post added at 08:14 AM ---------- Previous post was at 08:10 AM ----------
and try
http://omappedia.org/wiki/Android_How-tos#Clearing_Airplane_Mode
---------- Post added at 08:21 AM ---------- Previous post was at 08:14 AM ----------
try above,and put feedback before trying the dangerous way !!
Thx a bunch i'll give it a try
Sent from my MB860 using xda app-developers app
I did use att's spl now it says android version 2.5.3 but still no imei nor baseband... and still stuck in ap mode
Sent from my MB860 using xda app-developers app
try
http://forum.xda-developers.com/showthread.php?t=1264021
What i think migjt have happen is that even dough my phone is att branded i am not in att coverage cause im in the dominican republic so maybe i should try with an international sbf... wild guess... thx in advance
Sent from my MB860 using xda app-developers app
I have two guesses.
One is that the phone is still locked to att, but that is unlikely since you have unknown baseband.
As sad as this is to say, I think you got ripped off with a broken phone. this seems odd, and not fixable to me.
damn imma go ahead and try that imei fix stuff and post a reply briefly
same problem here... even SD card is not recognised
couldnt do it.. im sorry but i am what u guys describe as a noob... is there like a one click way to do it? or at least an easier way out... i really like my phone... there must be a way to recover that efs folder or at least create it or replace it...
another thing i think i rooted my phone but im not sure... how can i tell?
catillito said:
couldn't do it.. im sorry but i am what u guys describe as a noob... is there like a one click way to do it? or at least an easier way out... i really like my phone... there must be a way to recover that efs folder or at least create it or replace it...
Click to expand...
Click to collapse
this problem is not easy ! many things may leads to corrupted NVRAM, there is few tools and many parameters to change/revert.
there is no one click magic solution !
what you did exactly to be in this situation?
sad_but_cool1 said:
this problem is not easy ! many things may leads to corrupted NVRAM, there is few tools and many parameters to change/revert.
there is no one click magic solution !
what you did exactly to be in this situation?
Click to expand...
Click to collapse
i bought this phone used and the baseband was corrupted (unknown) so was the imei... it was runing 2.3.6 and i fxz back to stock 2.3.5 att... but that did not fix the issue... then i think i rooted the phone but im not sure cause i dont know how to tell if it is rooted.. i have the super user app if that helps... then i tried this http://forum.xda-developers.com/showthread.php?t=1264021.. but i just dont know how to get to the root folder or that efs foder or partition... i'm willing to do anything cause in the meantime i got myself an atrix 4g... so im at your disposal... thx in advance
catillito said:
i bought this phone used and the baseband was corrupted (unknown) so was the imei... it was runing 2.3.6 and i fxz back to stock 2.3.5 att... but that did not fix the issue... then i think i rooted the phone but im not sure cause i dont know how to tell if it is rooted.. i have the super user app if that helps... then i tried this http://forum.xda-developers.com/showthread.php?t=1264021.. but i just dont know how to get to the root folder or that efs foder or partition... i'm willing to do anything cause in the meantime i got myself an atrix 4g... so im at your disposal... thx in advance
Click to expand...
Click to collapse
there is no efs partition on moto devices,they are pds ! read the topic and related replays
anyway , we must know that the problem caused by trying to unlock bootoader or by trying to flash wrong kernel/pds/radio/cdt or flashing using modified device_tree binary
u must help us to help u as we can
we need to cause , then i/we will send you the corrects dumps and settings to use/write via cdmaworkshop app or nvram read/write tools
it's not a game !
This also happened to me...I was on GB 2.3.6 trying to OTA update to ICS. The phone was working fine at the time. The update downloaded and started to install but froze around "Updating STE BP" I received an assert failed message the phone rebooted and said the installation failed..When i checked settings i have unknown baseband version and no IMEI as well as not being able to take the phone off airplane mode. Phone restarts every 4-5 min any ideas
blackiceboi said:
This also happened to me...I was on GB 2.3.6 trying to OTA update to ICS. The phone was working fine at the time. The update downloaded and started to install but froze around "Updating STE BP" I received an assert failed message the phone rebooted and said the installation failed..When i checked settings i have unknown baseband version and no IMEI as well as not being able to take the phone off airplane mode. Phone restarts every 4-5 min any ideas
Click to expand...
Click to collapse
was your phone rooted ?
did you tried to update via rsd-lite with a good known 2.3.6 package (correct MD5 checksum)?
did you tried to use a good known formated sdcard that contains the update package (correct MD5 checksum)?
did the update process was acting while usb cable plugged?
sad_but_cool1 said:
was your phone rooted ?
did you tried to update via rsd-lite with a good known 2.3.6 package (correct MD5 checksum)?
did you tried to use a good known formated sdcard that contains the update package (correct MD5 checksum)?
did the update process was acting while usb cable plugged?
Click to expand...
Click to collapse
the phone was rooted when trying the initail OTA update after i fxz using RSDlite to 2.3.5 the OTA back to 2.3.6
Havent found a good known 2.3.6 package or just havent looked hard enough..
At the time of the OTA ICS update USB was not plugged
you fxz back to 2.3.6 successfully ? good !
your mobile now is rooted,install bootmenu manager (3rd party cwm) , do a double wipe (cache and data),then fxz again to 2.3.6,then try to update ota without rooting ! just check update after installing 2.3.6 without modifying or rooting.
sad_but_cool1 said:
you fxz back to 2.3.6 successfully ? good !
your mobile now is rooted,install bootmenu manager (3rd party cwm) , do a double wipe (cache and data),then fxz again to 2.3.6,then try to update ota without rooting ! just check update after installing 2.3.6 without modifying or rooting.
Click to expand...
Click to collapse
can you post link to thread for bootmenu manager
also how will this fix baseband and no IMEI
blackiceboi said:
can you post link to thread for bootmenu manager
also how will this fix baseband and no IMEI
Click to expand...
Click to collapse
why you asking too much ?
why not you try to do a simple search ? plz try to use the search feature in xda or google or qq , it's free !!!!!!!!!
***ONLY VERIZON GS3***
A lot of people have been having problems with flashing CM10.1 and the SlimBean 4.2.1 beta. This guide will tell you how to fix the data. At first it looks like you lost your IMEI, but you probably didn't. It is a simple fix.
What you will need:
Odin: http://samsung-updates.com/Odin307.zip
Stock Rom: https://www.dropbox.com/s/wjaifmod7d78lt0/stock.vzw_root66.tar
Instructions:
1. Go into Odin put the stock rom into the PDA part and make sure the check mark next to it is checked.
2. Boot into Download mode by hitting Volume Down + Power + Home
2. Make sure only "Auto Reboot" and "F. Reset Time" are checked under options (if not you can seriously mess up your phone).
3. Flash the stock rom using Odin.
4. Once it says pass in Odin take your phones battery out and boot into recovery by hitting Volume Up + Power + Home.
5. Hit wipe data/factory reset (your phone should restart)
6. Hit the bottom left then right then left then right then volume up to pass activation.
7 Then type *2767*3855# into the phone once you set it up (you shouldn't have to press call).
Now you phone should be fixed, and you should be able to root, unlock your boot loader and try again.
Tip:
When flashing SlimBean 4.2.1 beta 1 and CM10.1 use a dirty flash over a 4.1.1 or 4.1.2 rom.
- Dirty flash is when you don't clear your data before you flash.
I think you forgot a step, after step 4 when they boot into recovery they need to wipe data/factory reset and then boot the ROM, and THEN dial the number to re-provision.
Thank you for this. I have been trying to fix my phone for a couple days now from this roaming thing. I flashed the stock VRALHD, erased data, called that *2767blahblah number over and over. Nothing seemed to work. Finally, after leaving my family's Christmas party to catch my ferry back home, I figured I would try to dial that *2767*3855# again so I'd be able to let my family know I made the boat. After reboot, I had data! Not sure what changed but I'm afraid to reboot or do anything in fear of losing data again and being stuck in roaming. I'm going to try this fix when I get home. Thanks again, and merry Christmas!
Sent from my SCH-I535 using xda premium
Jborch8 said:
Thank you for this. I have been trying to fix my phone for a couple days now from this roaming thing. I flashed the stock VRALHD, erased data, called that *2767blahblah number over and over. Nothing seemed to work. Finally, after leaving my family's Christmas party to catch my ferry back home, I figured I would try to dial that *2767*3855# again so I'd be able to let my family know I made the boat. After reboot, I had data! Not sure what changed but I'm afraid to reboot or do anything in fear of losing data again and being stuck in roaming. I'm going to try this fix when I get home. Thanks again, and merry Christmas!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Once the phone successfully re-provisions you won't have any problems with data anymore, unless you flash a 10.1 build without RIL support for data that is. If you want to flash 10.1 again make sure it is the 12/24 nightly or later.
Chris123NT said:
Once the phone successfully re-provisions you won't have any problems with data anymore, unless you flash a 10.1 build without RIL support for data that is. If you want to flash 10.1 again make sure it is the 12/24 nightly or later.
Click to expand...
Click to collapse
Thank you. Any ideas as to why it took so many attempts at re-provisioning? Like I said, I've been trying for two days now.
Sent from my SCH-I535 using xda premium
This is a touchy subject. I once had the triangle and roaming with dual clock. I did all I could with all the fixes. Wound up getting sim replaced. Then happened again with the slim bean update. So both were triangles. But the luck the second time was flashing the backup of strumer jons miui. It has all the nice deep network settings. And it worked. I see now many are talking about the fix in most cases kust going in to network settings and chainging to ruim from nv ...then auto. So try this if you have the roaming triangle and still have your imei and number.. min
Sent from my SCH-I535 using xda premium
Droid2drummer said:
This is a touchy subject. I once had the triangle and roaming with dual clock. I did all I could with all the fixes. Wound up getting sim replaced. Then happened again with the slim bean update. So both were triangles. But the luck the second time was flashing the backup of strumer jons miui. It has all the nice deep network settings. And it worked. I see now many are talking about the fix in most cases kust going in to network settings and chainging to ruim from nv ...then auto. So try this if you have the roaming triangle and still have your imei and number.. min
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hello i am dealing with this right now as i type this. I have gone into Network settings and switched everything i can possibly find, nothing seems to get rid of the triangle
Also tried flashing other roms i had backed up
Also tried a fresh factory reset
Right now im downloading this ROM and Odin, and ill give it a whirl. If all else fails i guess i have to go get a new SIM? What do i tell them at the counter? Will they care that I am rooted? Do i even need to bring my phone to them or can i just bring the SIM and ask for a new one?
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
To the OP ... you mentioned follow these steps then i should be able to root/unlock ... but I already have. Do you mean that by following these steps I will lose my root and ill need to do it again?
Thanks
I wish this guide was out a couple days ago I had to figure it out by googling and flashing through Odin/face plants into keyboard. But what he says is what I did works great!
Sent from my SCH-I535 using Tapatalk 2
I feel like such a nub lol, never did use Odin. Im following this process ... i booted the phone and i see the little android robot. It says "Downloading... Do not turn off Target!"
I open Odin and i pointed the PDA path to the ROM i downloaded, check box is checked ... I hit start, and nothing happens.
Just says "<OSM> All threads completed. (succeed 0 / failed 0)"
Did i do it wrong?
EDIT, apparently i had to wait for it to "ADD" my drive ... now i hit start and its doing all sorts of ish ... wish me luck!
---------- Post added at 07:38 PM ---------- Previous post was at 07:12 PM ----------
I have gotten through to step 5 (factory reset) and now booted. It appears to be in an "Activation Loop" or something? I see the triangle is on top, and actually it sometimes switches to an "R" but then back to a triangle.
The phone says "Activating ..." and every minute it dials out to some number and connects for 2 seconds, then disconnects, and just keeps repeating.
It did that maybe 5 or 6 times, now it says my only option is to restart or make an emergency call. Cannot dial the code in step6 from the emergency keypad, it wont let me.
Im restarting, not sure what to do, there are no options.
Is this normal?
rsarno said:
I feel like such a nub lol, never did use Odin. Im following this process ... i booted the phone and i see the little android robot. It says "Downloading... Do not turn off Target!"
I open Odin and i pointed the PDA path to the ROM i downloaded, check box is checked ... I hit start, and nothing happens.
Just says "<OSM> All threads completed. (succeed 0 / failed 0)"
Did i do it wrong?
EDIT, apparently i had to wait for it to "ADD" my drive ... now i hit start and its doing all sorts of ish ... wish me luck!
---------- Post added at 07:38 PM ---------- Previous post was at 07:12 PM ----------
I have gotten through to step 5 (factory reset) and now booted. It appears to be in an "Activation Loop" or something? I see the triangle is on top, and actually it sometimes switches to an "R" but then back to a triangle.
The phone says "Activating ..." and every minute it dials out to some number and connects for 2 seconds, then disconnects, and just keeps repeating.
It did that maybe 5 or 6 times, now it says my only option is to restart or make an emergency call. Cannot dial the code in step6 from the emergency keypad, it wont let me.
Im restarting, not sure what to do, there are no options.
Is this normal?
Click to expand...
Click to collapse
The R or triangle is what this is fixing that means your roaming just get out of the activation screen and call the number.
Right on ... it worked! I googled "How to get past activation screen" and could not believe that tapping actually worked, but it did lol. Dialed the number and bam .. service.
Now im assuming i need to reroot and unlock? Ill get on that now
Thanks so much to everyone.
rsarno said:
Hello i am dealing with this right now as i type this. I have gone into Network settings and switched everything i can possibly find, nothing seems to get rid of the triangle
Also tried flashing other roms i had backed up
Also tried a fresh factory reset
Right now im downloading this ROM and Odin, and ill give it a whirl. If all else fails i guess i have to go get a new SIM? What do i tell them at the counter? Will they care that I am rooted? Do i even need to bring my phone to them or can i just bring the SIM and ask for a new one?
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
To the OP ... you mentioned follow these steps then i should be able to root/unlock ... but I already have. Do you mean that by following these steps I will lose my root and ill need to do it again?
Thanks
Click to expand...
Click to collapse
This was the case for me. However easy to go into verizon without your phone. Tell them its ar home and you just need new sim. Offer to pay for it. Then they will give it free.
Sent from my SCH-I535 using xda premium
---------- Post added at 08:51 PM ---------- Previous post was at 08:49 PM ----------
Also you need to make sure you still have #. Abd imei is correct.
Sent from my SCH-I535 using xda premium
rsarno said:
Right on ... it worked! I googled "How to get past activation screen" and could not believe that tapping actually worked, but it did lol. Dialed the number and bam .. service.
Now im assuming i need to reroot and unlock? Ill get on that now
Thanks so much to everyone.
Click to expand...
Click to collapse
No, you don't need to unlock, the root66 ROM preserves your unlocked bootloader. All you have to do is flash Clockworkmod recovery, or TWRP recovery, and then you can flash back your custom ROM
So I originally had the roaming issue. Went back to the stock rom and entered the code provided in the dialer, re rooted and unlocked bootloader and flashed a custom recovery. Tried flashing 10.1 again...still the same deal. Roaming. How can I get past this roaming with an android 4.2 rom!? has anyone been successful at it?
any suggestions would be greatly appreciated haha
996 said:
So I originally had the roaming issue. Went back to the stock rom and entered the code provided in the dialer, re rooted and unlocked bootloader and flashed a custom recovery. Tried flashing 10.1 again...still the same deal. Roaming. How can I get past this roaming with an android 4.2 rom!? has anyone been successful at it?
any suggestions would be greatly appreciated haha
Click to expand...
Click to collapse
You have to do a dirty flash over a 4.1.1 or 4.1.2 rom.
Post over at the cyanogenmod forums suggest trying:
Go into Mobile Settings -> Mobile Networks
Change CDMA mode to RUIM
Toggle Airplane Mode (or reboot)
Haven't been able to verify myself, but if it can save someone from reflashing it's worth a shot.
fuego3048 said:
Post over at the cyanogenmod forums suggest trying:
Go into Mobile Settings -> Mobile Networks
Change CDMA mode to RUIM
Toggle Airplane Mode (or reboot)
Haven't been able to verify myself, but if it can save someone from reflashing it's worth a shot.
Click to expand...
Click to collapse
I just tried this to fix my s3 and I can confirm it works
fuego3048 said:
Post over at the cyanogenmod forums suggest trying:
Go into Mobile Settings -> Mobile Networks
Change CDMA mode to RUIM
Toggle Airplane Mode (or reboot)
Haven't been able to verify myself, but if it can save someone from reflashing it's worth a shot.
Click to expand...
Click to collapse
Worked for me also.
Sent from my SCH-I535 using xda app-developers app
This worked for me but I have a couple question.
- How do I get to be bone stock from here? I don't want to be rooted or flash any roms
For some reason, I don't have any 4LTE service only 3g.
I went to status update two times and both times I got upgraded to 4.04 not 4.1
Basically I would like the phone like it just came out of the box and I did an OTA update for 4.1
Thanks.
toonz333 said:
This worked for me but I have a couple question.
- How do I get to be bone stock from here? I don't want to be rooted or flash any roms
For some reason, I don't have any 4LTE service only 3g.
I went to status update two times and both times I got upgraded to 4.04 not 4.1
Basically I would like the phone like it just came out of the box and I did an OTA update for 4.1
Thanks.
Click to expand...
Click to collapse
Are you sure that your in a 4g area?
Hi everyone & thanks for reading this!
I bought 2 new, unused Nexus 5 as presents for my sisters for Christmas (not via playstore, but via a reseller. Still: new, sealed, unused.)
I unlocked, installed a custom recovery, rooted both devices without problems, then set up one in a smartphone-newbie-friendly way, which took quite some time. Then, to save me some time, I fear I made quite a big mistake: I made a nandroid-backup of the newly-setup device and restored/installed it on the second nexus (so I wouldn't have to change all the settings again, install apps, etc).
Unfortunately, this seems to have erased the IMEI on the second device (it shows as IMEI=0), so I can't connect to any cell service. Some googling leads me to believe that this might be due to a corrupt/missing EFS-folder, which, second mistake, I did NOT make a backup of beforehand. I know, it's my own fault - my thinking was: why backup, there's nothing backupworthy on the device *yet*.
FML. :crying:
I am not sure if the phone is still in warranty (and even if it was - I guess I voided that by unlocking/rooting?!). I want to re-iterate that I own both devices LEGALLY, I have the bill, I have the original sticker with the original IMEI - I just need a way to re-enter it. Any dialer-code for that? Any modify-able EFS-backups? Any other way?
Thanks in advance!
PS: tried so far & found useless: other simcard (not working) & simcard in other phone (working), so it's a device-issue; factory-reset;
Try fastboot flashing the cache.img from the factory image.
jd1639 said:
Try fastboot flashing the cache.img from the factory image.
Click to expand...
Click to collapse
thanks for the super-quick reply jd1639!
to make sure I understand you correctly:
I can use the factory image from
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
(nexus 5, android 4.4.2), extract the cache.img from there & flash that via fastboot? (or would it have to be a factory image of this very device - which I do not have, unfortunately)
and, just for my understanding: how does that restore the imei? I mean, the factory image itself (or it's cache) can't really contain MY imei. does this just delete the invalid imei & force the phone to get it's original imei from some other, not yet overwritten source? e.g. hardware?
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Thank you for clarifying, rootSU - that gives me hope.
I will try tomorrow & hopefully report success
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
charesa39 said:
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
Click to expand...
Click to collapse
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
CellPhish said:
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
Click to expand...
Click to collapse
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
If all fails you can try to contact LG service and tell them your situation. Though its not good to lie, just tell them you got the IMEI=0 problem, they'll say its a hardware problem and will replace the motherboard(if your device is on warranty)
Sent from a potato
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
rootSU said:
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The IMEI is stored in the EFS partition, not the cache partition.
RogerG said:
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
Click to expand...
Click to collapse
Sounds like you turned the phone into a $400 paperweight. TWRP backs up and restores the EFS partition by default, and each device has a unique EFS partition, which contains the IMEI among other things. I don't know of a way of manually restoring the EFS data. This is unfortunately a $400 lesson for people who tinker without first doing their homework.
Hey guy. Let's not be so judgemental. There's always a risk of the imei being corrupted when you flash a ROM. As a matter of fact just before I even unlocked my nexus the imei got corrupted and I had to factory flash my phone to save it. Its scary but op, if you manage to get your phone working again make a backup and store it on your PC and or email yourself the backup.
BirchBarlow said:
The IMEI is stored in the EFS partition, not the cache partition.
Click to expand...
Click to collapse
Ha ha thanks! Can't believe you think I don't know that :/
Actually the "EFS partition" is 2 partitions..
/dev/block/platform/msm_sdcc.1/by-name/modemst1
And...
/dev/block/platform/msm_sdcc.1/by-name/modemst2
That doesn't change the fact that reflashing the cache.img is a known fix for missing IMEI. Corrupt cache can make the imei appear as 0 even when the EFS imei is in tact so reflashing the cache.img can resolve this.
Unfortunately though, I didn't read the OP fully. I just elaborated on an earlier response for the OP
jd1639 said:
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
Click to expand...
Click to collapse
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
rootSU said:
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes but all talks about how to change it in any way are not allowed here. Legally the only people that are allowed to do so is the OEM. You can look at international news reports of cellular dealers that are doing so are being closed down and arrested.
That is why it is well know to back up the efs before you do anything.
Bat cave One
My newly bought Nexus 5 shows IMEI 0 also
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
i just update my newly bought nexus 5 from initial 4.4.2 to 4.4.4 which is appear at update section but then my IMEI appear =0 .. dont understand what to do..
if your problem solved, pls tell me the detail procedure to recover my IMEI no.
RogerG, did you ever get this working? I'm on 6.0 and having the same problem, flashing cache.img also does nothing.
Thanks.
i am using nexus 5 on t-mobile network on stock lollipop. Now my phone does not recognize my SIM card, i think there is radio issue but dont know the solution. I tried so many options but there is no success. So far i did following things
Restarted.
APN checked an different APN settings.
Different T-mobile SIM.
different carrier SIM.
Same SIM in different phone and it works.
Opened back cover and checked antena but looks fine.
Finally reset to factory default with no luck.
Can anyone please suggest me any fix, i will greatly appreciate it.
Thanks.
Anyone please?
mak101 said:
Anyone please?
Click to expand...
Click to collapse
Try flashing a factory image:
https://developers.google.com/android/nexus/images?hl=en
Try flashing different modems from modem thread. Try a custom ROM if stock doesn't work.
Sent from my Nexus 5 using XDA Free mobile app
How is the sim card reader?
@mak101
Bump
Upupup
Have you checked your IMEI number?
Mine lost it and had to be replaced under warranty.
Sent from my Nexus 5 using XDA Free mobile app
C7SS said:
Have you checked your IMEI number?
Mine lost it and had to be replaced under warranty.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
If the warranty period should be how? Such as EFS lost?
---------- Post added at 02:28 PM ---------- Previous post was at 02:18 PM ----------
C7SS said:
Have you checked your IMEI number?
Mine lost it and had to be replaced under warranty.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
How should outside if the warranty period? For example, EFS is lost, what should the recovery partition? Recourse
I havent flash it yet, but plan to do it tonight, will update here after flashing it. Thanks.
mak101 said:
I havent flash it yet, but plan to do it tonight, will update here after flashing it. Thanks.
Click to expand...
Click to collapse
Results?
@mak101
I see I'm not the only one. Mine ran completely out of battery and when recharged it had lost radio - it sees the SIM if I extract and insert with the N5 switched on (which I wouldn't have thought was good practice, but since the initialisation sequence after factory reset suggests it then it must be ok), but at reboot it's gone again.
I have flashed half a dozen radios back as far as Kitkat. Installed various Lollipop ROMS from the Nexus factory image site. Installed Kitkat 4.4.4. Installed Android M preview 2 MPZ79M. Installed Chroma & Cyanogenmod.
Nothing works.
I don't have the technical knowledge to understand what component a dead battery kills. Does anyone? Surely someone in XDA will have a clue...?
Despite the phone being nominally out of warranty, since I ordered it on 31st October 2013 and received it in December 2013, I don't think that an expensive (£350) phone should last only 18 months. I have therefore written to Google support quoting the Sale of Goods Act and asking for repair, replacement or refund. I suggest that everyone affected by this design flaw does the same.
It's unbelievable that on a battery-driven device such a basic event as a drained battery can kill the most fundamental function of a phone.
dahawthorne said:
I see I'm not the only one. Mine ran completely out of battery and when recharged it had lost radio - it sees the SIM if I extract and insert with the N5 switched on (which I wouldn't have thought was good practice, but since the initialisation sequence after factory reset suggests it then it must be ok), but at reboot it's gone again.
I have flashed half a dozen radios back as far as Kitkat. Installed various Lollipop ROMS from the Nexus factory image site. Installed Kitkat 4.4.4. Installed Android M preview 2 MPZ79M. Installed Chroma & Cyanogenmod.
Nothing works.
I don't have the technical knowledge to understand what component a dead battery kills. Does anyone? Surely someone in XDA will have a clue...?
Despite the phone being nominally out of warranty, since I ordered it on 31st October 2013 and received it in December 2013, I don't think that an expensive (£350) phone should last only 18 months. I have therefore written to Google support quoting the Sale of Goods Act and asking for repair, replacement or refund. I suggest that everyone affected by this design flaw does the same.
It's unbelievable that on a battery-driven device such a basic event as a drained battery can kill the most fundamental function of a phone.
Click to expand...
Click to collapse
Great news (at least for now ) After many days I got some time to work on this problem which was started probably a month ago. I also flashed few ROMs and did not work until now. But finally I found the combination which works now. May be following steps will help you to fix your problem.
1. Download Nexus Root Tool Kit - You dont have to be techie or expert to use this - very simple to use
2. Watch video here for how to use Nexus Root Tool Kit - Select Automate Flashing ROMs under RootJunky section.
3. Dowload xTRaSmoth hammerhead ROM - I picked xTRaSmooth_MPZ79M_hammerhead_Final.zip
More Information about this ROM here
3. Download radio zip (which finally worked)
Hope this helps.
Thanks, mak101. I've downloaded both.
I see that the radio link contains a boot image - is that part of your solution, or did you flash just the radio? I'm a bit nervous of boot images.
I've used NRT a lot, particularly over the past few days...
If you could post the steps that you followed it would probably help not just me but others who have the same problem.
I'll let you know what Google Support reply.
Thanks for your help - appreciated.
Yes that is the file I used for Radio flash its about 23 MB, I generally never change ROM but I did first time because of this problem and it worked. In NRT first I selected hammerhead ROM and next I selected radio rom and falshed it to gathered.
dahawthorne said:
Thanks, mak101. I've downloaded both.
I see that the radio link contains a boot image - is that part of your solution, or did you flash just the radio? I'm a bit nervous of boot images.
I've used NRT a lot, particularly over the past few days...
If you could post the steps that you followed it would probably help not just me but others who have the same problem.
I'll let you know what Google Support reply.
Thanks for your help - appreciated.
Click to expand...
Click to collapse
Did you manage to make your N5 works? Got the same issue here
No, I never got it to work. I gave up, called Google, and they replaced it with a refurbished N5 which was indistinguashable from a new one.
So im wondering if anyone has repair firmwares for the USA SM_G955U. i recently installed a U2QK4 update OTAusing ADB from the ATT section and everything went bad from there. I was told i may not be able to downgrade but thats not the problem. I CANT DO ANYTHING WITH MY PHONE NOW! IT HAS NO RECOVERY AT ALL IT JUST FLICKERS THE BLUE SCREEN WITH THE ANDROID AND A TEXT APPEARS OCCASIONALLY ON THE FLICKERING SCREEN WITH A WHOLE BUNCH OF FAILS. THERE IS NO UPLOAD MODE AT ALL. I CAN ONLY ACCESS DOWNLOAD MODE WHICH MAKES NO SENSE TO FLASH ANYTHING CAUSE NOTHING WORKS. THE ONLY THING THAT IS FLASHABLE ON NON-MODDED AND MODDED ODIN IS CP! I DONT EXACTLY UNDERSTOOD WHAT HAPPENED. EVERYTHING WAS OPERABLE AND THEN THE PHONE ENCRYPTED ITSELF,REBOOTED ANDA BLUE SCREEN WITH A CARD WAS FLASHING AND ALL WENT TO HELL. TRIED REBOOTING AND THATS WHERE IT ALL BEGAN! I HAVE NEVER EXPERIENCED THAT ON A PHONE BEFORE!
ITS BEEN DAYS SINCE THIS HAPPENED AND I WAS TOLD THE FIRMWARE WAS BEING UPDATED FROM THE OP AND STILL NOTHING! I DONT THINK PEOPLE SHOULD POST THINGS TO FLASH WITH JUST A WARNING ON HERE, THEY SHOULD TEST IT BEFORE POSTING BECAUSE PEOPLE LIKE ME GET CURIOUS AND WANT TO FLASH THINGS,BUT, THE POSTER DOESNT HAVE ANY IDEA WHAT IT DOES!NOT HIS FAULT AS I AM TO BLAME,
ILL SAY IT HERE AGAIN SO PEOPLE DONT THINK IM BLAMING ANYONE,
I I AM TO BLAME!!!!
OKAY, BUT, NOW I AM STUCK WITH A $950 PAPERWEIGHT! AND HONESTLY I WANTED TO BRICK IT, BUT, I THOUGHT WARRANTY OR INSURANCE WOULD COVER IT IN WHICH THEY WONT BECAUSE ATT IS GETTING CRAPPY WITH THEIR CUSTOMER SERVICE. IT SEEMS I HAVE BEEN LEFT IN THE DARK WITH NO CLUES OR HELP.
SORRY FOR CAPITAL LETTERS FORGOT TO TURN IT OFF AND AM NOT ABOUT TO RE-TYPE.
IF ANYONE KNOWS WHAT TO DO OR HOW TO FIX THIS PLEASE HELP.
(AND GETTING A NEW PHONE WONT HELP, SO THAT RESPONSE IS SHOT)
LOOKING FOR A FIX. THANKS IN ADVANCE
Please, don't SHOUT!
dalanik said:
Please, don't SHOUT!
Click to expand...
Click to collapse
Haha I didn't know text could be so loud shoot I even hurt my ears while I typed this hahaha
podagee said:
Haha I didn't know text could be so loud shoot I even hurt my ears while I typed this hahaha
Click to expand...
Click to collapse
Few things:
U2QK4? I don't think that's a model number for a firmware... We certainly haven't seen a U2 g955/0u firmware yet...
And sammobile has it as u1aqk3 for vzw so tmb should be u1qk4.
Can you double check what you flashed?
podagee said:
So im wondering if anyone has repair firmwares for the USA SM_G955U. i recently installed a U2QK4 update OTAusing ADB from the ATT section and everything went bad from there. I was told i may not be able to downgrade but thats not the problem. {screaming redacted }
Click to expand...
Click to collapse
1. A good, new odin that will flash an official package.
https://odindownload.com/download/Odin3_v3.12.3.zip
2.Not the latest firmware, but a solid base (which you can then use to OTA updated to the latest patches)
https://www.sammobile.com/firmwares/galaxy-s8/SM-G955U/ATT/download/G955USQU1AQC9/129108/
Download both, use the former to flash the latter. Let us know how it goes!
EDIT: AND IF IT DOESN'T WORK! Please attach a screenshot of Odin and a picture of your phone (if you can). It'll help us get you squared away.
partcyborg said:
Few things:
U2QK4? I don't think that's a model number for a firmware... We certainly haven't seen a U2 g955/0u firmware yet...
And sammobile has it as u1aqk3 for vzw so tmb should be u1qk4.
Can you double check what you flashed?
Click to expand...
Click to collapse
I'm pretty sure norbarb, the provider of the U2BQK4 firmware knew that it was for the N950(note 8) and posted it in his adb update thread. I bought a new motherboard and will not ever update from that person again because of what has happened. I am not bashing him I just don't want to go through this mess again. and so far I've gotten a bootloader's to flash by using the.elf files from a u2b file from the note 8. Still no recovery and stuck at the bootloader's screen. Can still get into download mode.
The quickest fix I know is for a new motherboard.
Thanks guys
podagee said:
I'm pretty sure norbarb, the provider of the U2BQK4 firmware knew that it was for the N950(note 8) and posted it in his adb update thread. I bought a new motherboard and will not ever update from that person again because of what has happened. I am not bashing him I just don't want to go through this mess again. and so far I've gotten a bootloader's to flash by using the.elf files from a u2b file from the note 8. Still no recovery and stuck at the bootloader's screen. Can still get into download mode.
The quickest fix I know is for a new motherboard.
Thanks guys
Click to expand...
Click to collapse
You wouldn't be able to flash n8 firmware on a s8. Secure boot / Knox would stop you
partcyborg said:
You wouldn't be able to flash n8 firmware on a s8. Secure boot / Knox would stop you
Click to expand...
Click to collapse
Well idk know ALL I KNOW IS HE PROVIDED A U2BQK4 FILE AND I CANT FIND IT ANYWHERE ELSE EXCEPT ON A NOTE 8 !
podagee said:
Well idk know ALL I KNOW IS HE PROVIDED A U2BQK4 FILE AND I CANT FIND IT ANYWHERE ELSE EXCEPT ON A NOTE 8 !
Click to expand...
Click to collapse
Lol no need to capslock everywhere. Just download and flash stock and it will be fine. You can get to download mode right?
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
eregev said:
1. A good, new odin that will flash an official package.
https://odindownload.com/download/Odin3_v3.12.3.zip
2.Not the latest firmware, but a solid base (which you can then use to OTA updated to the latest patches)
https://www.sammobile.com/firmwares/galaxy-s8/SM-G955U/ATT/download/G955USQU1AQC9/129108/
Download both, use the former to flash the latter. Let us know how it goes!
EDIT: AND IF IT DOESN'T WORK! Please attach a screenshot of Odin and a picture of your phone (if you can). It'll help us get you squared away.
Click to expand...
Click to collapse
All due respect but aqc9 is ancient and full of bugs that will make your experience with your phone sub par. Just go to updato.com and download the latest version for your carrier and device. By default updato is slow but if you use a download manager it flies. I can get 3MB/s easily
i honestly dont think people read in these forums. But everyone surely knows everything.
I am starting to get annoyed with that. PLEASE READ CAREFULLY:
1. i have flashed a rom provided by norbarb in the AT&T forums(he took it down) G955USA1US2BQK4,
2. after installing that update, phone went haywire, encrypted and erased everything except download mode,
3. ABSOLUTELY NO RECOVERY AT ALL,
4. nothing will flash over, NOTHING!! phone error: SW REV ablFAILED 1>binary >2 ODIN error. FAIL(AUTH) and FAIL dismatch model in non-modded ODIN and modded odin.
5. i got a bootloader to flash using abl files from a U2b (meaning bootloader 2) from another file U2BQK5 provided from a third party pm.
6. stuck in a bootloop at bootloader screen,
7. STILL NOTHING FLASHES OVER.
8. EDL cable needed per eli, went ahead and ordered another motherboard.
IF ANYONE CARES OR DECIDES TO BADGER ABOUT REPAIR FIRMWARE, PLEASE CHECK OUT GSM FORUMS, THERE ARE OTHER FORUMS WITH USEFUL INFORMATION ABOUT REPAIR FIRMWARES.
thank you all for your help. i just went ahead and ordered another motherboard cause i found it easier and less stressful to deal with less people who do not read the OP.
partcyborg said:
Lol no need to capslock everywhere. Just download and flash stock and it will be fine. You can get to download mode right?
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
All due respect but aqc9 is ancient and full of bugs that will make your experience with your phone sub par. Just go to updato.com and download the latest version for your carrier and device. By default updato is slow but if you use a download manager it flies. I can get 3MB/s easily
Click to expand...
Click to collapse
yes i can but nothing will flash
podagee said:
yes i can but nothing will flash
Click to expand...
Click to collapse
My friend. You keep saying you download stuff from PM or from other sources yet it doesn't seem like you have bothered to try any of the links I or others on here have posted for you. Especially trying the latest Odin can help with software mismatch errors.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
partcyborg said:
Lol no need to capslock everywhere. Just download and flash stock and it will be fine. You can get to download mode right?
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
All due respect but aqc9 is ancient and full of bugs that will make your experience with your phone sub par. Just go to updato.com and download the latest version for your carrier and device. By default updato is slow but if you use a download manager it flies. I can get 3MB/s easily
Click to expand...
Click to collapse
No you're right it is ancient BUT it does have a direct update path straight to last month's security patch. And, maybe most importantly, OP could be using an older ODIN and hasn't tried the new one so I figured an older firmware has best shot at being compatible, he can OTA from there.
eregev said:
My friend. You keep saying you download stuff from PM or from other sources yet it doesn't seem like you have bothered to try any of the links I or others on here have posted for you. Especially trying the latest Odin can help with software mismatch errors.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
No you're right it is ancient BUT it does have a direct update path straight to last month's security patch. And, maybe most importantly, OP could be using an older ODIN and hasn't tried the new one so I figured an older firmware has best shot at being compatible, he can OTA from there.
Click to expand...
Click to collapse
hey bro, just to clarify with you i have flashed every file that there is from the links provided and from the forums i have about 8 copies of each file haha looks like i wont be running out soon. seems like the reason it crashed is the memory test that the rom i flashed inflated too much. i think it damaged my board which is okay i have another coming.
podagee said:
hey bro, just to clarify with you i have flashed every file that there is from the links provided and from the forums i have about 8 copies of each file haha looks like i wont be running out soon. seems like the reason it crashed is the memory test that the rom i flashed inflated too much. i think it damaged my board which is okay i have another coming.
Click to expand...
Click to collapse
Say what now? What made you think it was the memory test? What made you think it was the board or an actual hardware issue with the phone? A memory test can't 'inflate' anything much less can it damage your memory or the actual board.
I had a problem with my device from a badly restored backup where my modem would crash the machine to upload mode moments after booting on anything but a stock rom, and even that the radio didn't work and it would rebolt about 30 times to get to a state where it finished booting at all.
Needless to say I fixed it (I'm still here) but I essentially had to implement my own repair procedure and after about 30 hours total of working in it over two days I managed to get it working enough that I could get a rooted os booted and could then do another restore with a good backup.
If you problem sounds similar (iirc it was in the same general area) and it is then I'm afraid you wasted your money, as all you need is a restore of those partitions outside the rom part of your nvram.
partcyborg said:
Say what now? What made you think it was the memory test? What made you think it was the board or an actual hardware issue with the phone? A memory test can't 'inflate' anything much less can it damage your memory or the actual board.
I had a problem with my device from a badly restored backup where my modem would crash the machine to upload mode moments after booting on anything but a stock rom, and even that the radio didn't work and it would rebolt about 30 times to get to a state where it finished booting at all.
Needless to say I fixed it (I'm still here) but I essentially had to implement my own repair procedure and after about 30 hours total of working in it over two days I managed to get it working enough that I could get a rooted os booted and could then do another restore with a good backup.
If you problem sounds similar (iirc it was in the same general area) and it is then I'm afraid you wasted your money, as all you need is a restore of those partitions outside the rom part of your nvram.
Click to expand...
Click to collapse
I've been messaging with Eli and he said an EDL cable would fix the problem as it needs the deep flash. What would be your suggestion? I have been trying everything and I noticed somewhere saying windows 8 had problems with Odin software so I am currently installing a fresh copy of windows 10. Any suggestions would be appreciated
podagee said:
I've been messaging with Eli and he said an EDL cable would fix the problem as it needs the deep flash. What would be your suggestion? I have been trying everything and I noticed somewhere saying windows 8 had problems with Odin software so I am currently installing a fresh copy of windows 10. Any suggestions would be appreciated
Click to expand...
Click to collapse
Snapdragon right?
partcyborg said:
Snapdragon right?
Click to expand...
Click to collapse
Yes snapdragon G955U AT&T
podagee said:
I've been messaging with Eli and he said an EDL cable would fix the problem as it needs the deep flash. What would be your suggestion? I have been trying everything and I noticed somewhere saying windows 8 had problems with Odin software so I am currently installing a fresh copy of windows 10. Any suggestions would be appreciated
Click to expand...
Click to collapse
.
I thought windoze 10 was the "worst" because of the driver signing gotcha . This was true of me and my alibaba smart watch . For me, I had to resurrect an old h.d. with windoze 7 . . .
old_fart said:
.
I thought windoze 10 was the "worst" because of the driver signing gotcha . This was true of me and my alibaba smart watch . For me, I had to resurrect an old h.d. with windoze 7 . . .
Click to expand...
Click to collapse
Yeah windows 7 is the best but I kinda like the metro theme with 8 and 10, though 8 is bad........
partcyborg said:
Say what now? What made you think it was the memory test? What made you think it was the board or an actual hardware issue with the phone? A memory test can't 'inflate' anything much less can it damage your memory or the actual board.
I had a problem with my device from a badly restored backup where my modem would crash the machine to upload mode moments after booting on anything but a stock rom, and even that the radio didn't work and it would rebolt about 30 times to get to a state where it finished booting at all.
Needless to say I fixed it (I'm still here) but I essentially had to implement my own repair procedure and after about 30 hours total of working in it over two days I managed to get it working enough that I could get a rooted os booted and could then do another restore with a good backup.
If you problem sounds similar (iirc it was in the same general area) and it is then I'm afraid you wasted your money, as all you need is a restore of those partitions outside the rom part of your nvram.
Click to expand...
Click to collapse
still waiting on a reply from you