I've compiled Android and tried to flash system.img to my phone (British Nexus S i9020) and although Fastboot reports that it sends the data across OK, the write fails with a red line of text in the bootloader: "Invalid magic code 0x03"
I've tried a different system.img and I get the same error. Though, I tried flashing a radio image across and that worked fine, I flashed the old one back as well too.
I've not found much when searching, instead something suggesting that I need stock Android, well, I am on stock, with a manual upgrade from 2.3.1 to 2.3.2, 2.3.3, and finally 2.3.4, so, I'm stumped.
Has anyone experienced this before? Could you give me any clues or pointers on what it could be please?
Thanks
bumping because i'm really frustrated.
I just had this problem, i couldn't flash anything through fastboot
i tried searching for how to copy files from recovery or bootrom couldn't find a thing
but i just found it so i thought i'd research this thread and ler u know what i did
i flahed the clockwork recovery which is the only thing that worked
i went into mounts
and mounted USB storage
copied my nexus S clockwork recovery backup (available online) and restored and my phone is working agian
hope yours will too
let me know if u need help, i'll try but i am afraid i am a noob just like u
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Have you tried flashing different radios (baseband)?
http://forum.xda-developers.com/showthread.php?t=1785999
causticfix said:
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Click to expand...
Click to collapse
Take a look at this thread, it may help. http://forum.xda-developers.com/showthread.php?p=25172599#post25172599
thanks for the replies...
I've flashed UCM1 and UCLL3 radios, they flash fine but no change...still can't flash to stock and no imei/baseband/service.
That fix thread was one of the first I found, but as I still have my keystr file in the efs folder, I didn't think it would apply to me...I suppose I could make an external backup of my efs, delete it and try one of those methods from scratch.
read through the restore to stock sticky http://forum.xda-developers.com/showthread.php?t=1652398 and go through the trouble shooting sections, if that doesn't help u could have bad hw
causticfix said:
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Click to expand...
Click to collapse
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Vgkiller said:
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Click to expand...
Click to collapse
Just factory reset when it boot loops
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Vgkiller said:
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Click to expand...
Click to collapse
will do.
also, you may know this already, but just in case, be aware the skyrocket doesn't use nv_data.bin...I thought it did too when I first started searching around about this, and when i couldnt find it I was pretty freaked out...but then i found out the skyrocket actually uses 3 encrypted partitions rather than a nv_data file. so if you have at least some files in your efs/imei folder you may be in a better spot than it seems. of course if its totally empty, you'll likely have a lot more work to do.
I'll update if I have any luck.
causticfix said:
will do.
also, you may know this already, but just in case, be aware the skyrocket doesn't use nv_data.bin...I thought it did too when I first started searching around about this, and when i couldnt find it I was pretty freaked out...but then i found out the skyrocket actually uses 3 encrypted partitions rather than a nv_data file. so if you have at least some files in your efs/imei folder you may be in a better spot than it seems. of course if its totally empty, you'll likely have a lot more work to do.
I'll update if I have any luck.
Click to expand...
Click to collapse
Yes I have two files in my imei folder i,e keystr and mps_code.dat!
I tired changing them from root explorer! pasted someones else's efs folder! but still I cant fix my imei is stays 0.
i donno how to get to diag mode with this rom, otherwise i could have tried my luck with QPTS.
Incase you have broken your imei without backing it up, there is another way. And yes it is legal.
Here's the tutorial http://goo.gl/wtW29 and here's the needed tools (software & hardware) http://goo.gl/54mtk.
lingowistico said:
Incase you have broken your imei without backing it up, there is another way. And yes it is legal.
Here's the tutorial http://goo.gl/wtW29 and here's the needed tools (software & hardware) http://goo.gl/54mtk.
Click to expand...
Click to collapse
I actually have octopus box as well as the z3x samsung tool installed, however, they're both server activation based...the software is useless without an $89 (octopus) to $120( (z3x) activation.
I'd rather not spend that kind of money for something I'll likely only need once, so I'm gonna do as much as I can in the way of free solutions, and if I have no luck there I'll probably just send it to mobiletechvideos for their $40 efs/imei repair. I'm guessing they use one or more of these repair box programs themselves anyway, and will do the same job for only $40.
thanks for the suggestion anyway though..
causticfix said:
I actually have octopus box as well as the z3x samsung tool installed, however, they're both server activation based...the software is useless without an $89 (octopus) to $120( (z3x) activation.
I'd rather not spend that kind of money for something I'll likely only need once, so I'm gonna do as much as I can in the way of free solutions, and if I have no luck there I'll probably just send it to mobiletechvideos for their $40 efs/imei repair. I'm guessing they use one or more of these repair box programs themselves anyway, and will do the same job for only $40.
thanks for the suggestion anyway though..
Click to expand...
Click to collapse
There's this polish guy who probably also has all the same boxes and he takes €10 for imei repair by remote desktop.
http://forum.samdroid.net/f70/repair-imei-s2-5729/
And finally you could try helping the op of this thread to add compatibility for skyrocket, this would be free.
lingowistico said:
There's this polish guy who probably also has all the same boxes and he takes €10 for imei repair by remote desktop.
http://forum.samdroid.net/f70/repair-imei-s2-5729/
And finally you could try helping the op of this thread to add compatibility for skyrocket, this would be free.
Click to expand...
Click to collapse
Isn't there any way to fix my imei on my own ?
Mt efs folder also looks good now with all the files it should have but still the imei remains unaffected.
Also i'd like to know that the qualcom nv tool showed my esn as dead and mied as 000....000 does the dead thing mean it isnt repairable ?
I tried using QPTS but this is where I get stuck.. (img attatched)
Vgkiller said:
Isn't there any way to fix my imei on my own ?
Mt efs folder also looks good now with all the files it should have but still the imei remains unaffected.
Also i'd like to know that the qualcom nv tool showed my esn as dead and mied as 000....000 does the dead thing mean it isnt repairable ?
I tried using QPTS but this is where I get stuck.. (img attatched)
Click to expand...
Click to collapse
Obviously there is since some random polack can do it for you on his PC, the problem is the lack of knowledge.
Those who know won't tell you how, because they want € for it :crying:
lingowistico said:
Obviously there is since some random polack can do it for you on his PC, the problem is the lack of knowledge.
Those who know won't tell you how, because they want € for it :crying:
Click to expand...
Click to collapse
This totally defeats the purpose of this forum then. Its sad.
Vgkiller said:
This totally defeats the purpose of this forum then. Its sad.
Click to expand...
Click to collapse
People want money for it because it's mostly used for making stolen phones work again.
That means real life risks like fines, jail etc.
Of course there are lots of examples when people experiment with this or that and delete their imei accidentally, or want to change the imei for some other reason. But these are more rare.
An update...
I managed to finally get flashed to stock...still null/null imei & baseband unknown. Efs folder is still there with files, keystr file is on...not sure what else I can do myself at this point so, I guess its time for the Polish dude or mobiletechvideos.
Hi People,
Did any1 found any solution?
talk2sharn said:
Hi People,
Did any1 found any solution?
Click to expand...
Click to collapse
unfortunately not for me. I finally got the polish dude to try restoring the imei remotely...he used like 3 or 4 different programs, nothing worked.
so, i just got a broken SR with a cracked lcd off ebay for $50 and used the motherboard from it.
causticfix said:
unfortunately not for me. I finally got the polish dude to try restoring the imei remotely...he used like 3 or 4 different programs, nothing worked.
so, i just got a broken SR with a cracked lcd off ebay for $50 and used the motherboard from it.
Click to expand...
Click to collapse
Ohkies.
Did you ask the polish guy about the reason why he was not able to fix your mobile. Coz, I'm just having similar problem like yours. I tried working with all the local samsung service centre guys, nothing worked. One guy said that my mobile IMEI is locked in some database, so it is not picking or detecting my SIM, hence locked. I know that my mobile is unlocked and is valid, I ignored his comments.
I assume you changed your MotherBoard of the mobile with the new cracked SR's, so that it could take new IMEI instilled in new board. Is it so?
Also, please suggest me about any alternatives on how to fix this problem.:crying:
ive been searching around and cant get this thing to connect to a network. i was on mm and i wanted to go back to kk so i tried just doing a full wipe and flashed the fastboot 44s rom (i had a bunch of useless crap saved on my phone and i wanted to get rid of it anyways).
the phone booted up but it says audiofx error and then just reboots. ive tried the msm coloros download tool but its not recognizing my phone in fastboot and neither is the cm11s version of it. i can flash fastboot cm11s roms but i can not get this thing to stay on for more than 3secs.
i have an efs backup from a year ago when this happened but it says the files are corrupted but they shouldnt be. they were iso and i changed their file types to bin (not sure if that makes any sense at all)
could someone please help. thanks in advance
There is already one thread for your problem, kindly search before post
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
drmuruga said:
There is already one thread for your problem, kindly search before post
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Click to expand...
Click to collapse
ohhh, believe me, i searched and searched lol. i now have about 10 different programs seeing they can fix it. i just got it to turn on and stay on but i still do not have cell or wifi. the link you gave is one of many i have been trying. im giving up till the morning. wanting to watch some house of cards.
btw, the link you shared is the one that fixed the bootloops. im kinda freaking out a little because i wasnt seeing people with the same issues too often in my searches and i use my phone for work. i dont feel like buying a phone for monday
thanks for the reply though. i think im making progress.
found the problem. bluestacks was stopping some commands from working. read it in another thread (been searching a lot so i dont have a link), but i just quit bluestacks and things would work in cmd prompt. thanks for trying to help man
Hey there guys. I bought an HTC One M7 from amazon which came unlocked. Problem was, i couldnt get it to connect to my provider, Koodo. Long story short, i went to flash a Stock Telus Rom to it, no META file in the zip. Already wiped my phone. So now theres no OS. I have TWRP still (thank god for that) but it just sits at the HTC logo and wont boot, as i know thats what happens when you mess up. Fairly familiar with THIS issue, as ive done it to my Samsung Galaxy SIII MANY times before, but had odin to fix it. I have an RUU.exe. Got it from a forum here. Cant connect to my phone (error 171 i believe). Everything is connected properly, and my PC recognizes it, but only as an MTP device. I am gonna try an RUU.zip and flash it with fastboot. See if that method works. But any help at all would be GREATLY appreciated as i dont want to have spent $299 to waste it like betting on the Maple Leafs.
Side note: I cannot get ADB Sideloader to work properly. I have a Custom Rom that i attempted to flash that way, but i got the error that was like ADB version (31) is not up to date with server (36) or something along the lines of that and then it fails to load daemon everytime. Tried some fixes from these forums but none of them were successful. Not familliar with ADB and all that stuff, so if anyone has any fix for the ADB, please dumb it down to kindergardener levels.
Sorry this is so long. Tried to explain everything as detailed as possible for a more acturately helpful response.
UPDATE Got the RUU.zip file to work after a couple hours of messing around with it. Had to fast boot getvar to obtain my model id, and change that in the android-info.txt in the zip file. Is flashing now. HUGE thanks to all of the thousands of XDA forums. Helped me out with everything!
AndyA2098 said:
Hey there guys. I bought an HTC One M7 from amazon which came unlocked. Problem was, i couldnt get it to connect to my provider, Koodo. Long story short, i went to flash a Stock Telus Rom to it, no META file in the zip. Already wiped my phone. So now theres no OS. I have TWRP still (thank god for that) but it just sits at the HTC logo and wont boot, as i know thats what happens when you mess up. Fairly familiar with THIS issue, as ive done it to my Samsung Galaxy SIII MANY times before, but had odin to fix it. I have an RUU.exe. Got it from a forum here. Cant connect to my phone (error 171 i believe). Everything is connected properly, and my PC recognizes it, but only as an MTP device. I am gonna try an RUU.zip and flash it with fastboot. See if that method works. But any help at all would be GREATLY appreciated as i dont want to have spent $299 to waste it like betting on the Maple Leafs.
Side note: I cannot get ADB Sideloader to work properly. I have a Custom Rom that i attempted to flash that way, but i got the error that was like ADB version (31) is not up to date with server (36) or something along the lines of that and then it fails to load daemon everytime. Tried some fixes from these forums but none of them were successful. Not familliar with ADB and all that stuff, so if anyone has any fix for the ADB, please dumb it down to kindergardener levels.
Sorry this is so long. Tried to explain everything as detailed as possible for a more acturately helpful response.
UPDATE Got the RUU.zip file to work after a couple hours of messing around with it. Had to fast boot getvar to obtain my model id, and change that in the android-info.txt in the zip file. Is flashing now. HUGE thanks to all of the thousands of XDA forums. Helped me out with everything!
Click to expand...
Click to collapse
Thread closed as OP fixed his issue