Database Develop

SGN N7000: Help needed with repartitioning efs to ext 4 and error mounting efs??

I have tried to find more about my situation but asking seems to be the only way since all the info is either scattered or not available!
For two weeks I've been trying to fix my note from this ics emmc bug which made me loose efs folder and I have tried several methods with no luck, so I thought that repartitioning sd might kill the bug, so I repartioned just (parts)7,9,10,11 and also went for efs part that was empty anyway thought it might clear bad blocks, although afterwards I flashed efsfix.zip from another thread on here somewhere, because of which network and everything works just no lock screen and power button dialog? And when I flash any rom stock/custom it says (in red) error mounting efs, I found a solution for that by using terminal emulator and commanding "mount", But gotta do it manually afer every reboot?
And my imei is not the same as under my fone, how could I manually edit the imei and insert original fone info?
Could anyone help or guide me to a link so that I can recreate efs partition to ext 4 and the sort out other issues?
Edit: info in-depth!!
Thanks!

Does anyone know how to create/recreate an efs ext 4 partition on galaxy note? Is there a command or certain way to mount efs part as ext 4?

without efs backup you have lost your emei. Unless you resort to illegal methods in most countries (expensive z3x box)
At this point, just go to Samsung and have them illegally legally restore it lmao, they somehow are allowed to do it.
Anyway, how did you analyze its efs thats corrupted, cause if you can flash gb from pc odin succesfully its not super bricked
Sent from my GT-N7000 using Tapatalk 2

recreate can be done by flashing gb with pitfile and option clear efs. Then you should get generic emei. Which stupidly is also blocked in some countries.
That emei stuff is so overrated by secret agencies.
Sent from my GT-N7000 using Tapatalk 2

Thanks for the reply baz77.
Basically, I wasnt aware of this emmc wipe bug when I bought Note, I got my rom flashing experience and knowledge from SGS2, so after like a week of purchase I tried to flash ICS stunnner on my Note with squeaky clean, but resulted in getting my fone back from samsung after being revived, took 3weeks to return.
At this point I still didnt know about the bug because I had assumed that my own doing caused the super hardbrick, till I flash a criskelo rom with a wipe and my problems started off with not registered on network, after that I have been krazily searching and flashing to have the fone working flawless again without having to send the fone back to samsung becasue of the wait and tiny chips n crack on my fone.
And I figured that efs is corrupted by googling and gathering info about my particular problem and everything pointed towards efs being corrupted!
I am really hoping for them release a fix and I can get my fone back working as a whole again!
Edit: added missing words! Lol
Sent from my GT-N7000 using xda premium with Alliance Rom v1.2 + no lock screen and power button dialog!?!?

Could I plz ask, where can I get the stock gb with pit file samsung
Sent from my GT-N7000 using xda premium with Alliance Rom v1.2 + No lockscreen and No Power button dialog!?!?

baz77 said:
recreate can be done by flashing gb with pitfile and option clear efs. Then you should get generic emei. Which stupidly is also blocked in some countries.
Click to expand...
Click to collapse
Apparently, pitfile and efs clear option doesn't work, I tried GB with pitfile got the red 'error mounting efs' and tried stock UK ICS 4.0.3 from (thanks to) Dr.Ketan but Ive still got the error and no lockscreen and faulty power button?!? Plus:- Sim Network is gone :banghead: , i'll just have to flash that efsfix.zip and do the terminal "mount" procedure again!!! manually!
"Probaly Leagality issues there" I'll try the same pitfile procedure with rom from another country if it doesnt work then dont really want to but guess this fone's going back to Samsung for repairs before I sell it off.
Many Thanks for your help!!
<<SUNG>>from my <<SAM>> GT-N7000

baz77 said:
At this point, just go to Samsung and have them illegally legally restore it lmao, they somehow are allowed to do it. 2
Click to expand...
Click to collapse
I have the custom binary count reset, so they shouldnt have any problems with repairing illegally then?? With stock UK ICS 403 Rom from this forum!?!
<SAMSUNG><ASONG> From GT-N7000!

I thought each rom had efs file, not so sure anymore. download and install 7zip, open the tar md5 rom file with it and ignore the warnings. should be efs. img in there, if not best download one, same csc as you have, if you know what it was before it became corrupt. I think kj4 has one, so you can flash whole gb rom with options efs clear and the pitfile.
If that fails, then perform a factory reset with code, do this only from gb, *2767*3855# in dialer. That might force the efs to reset itself to generic. Should not be needed, but hey it cant harm trying on gb. note own risk
If that fails, flash stock ics which you had in first place and ask them to fix it.
You need them anyway to get original emei back, which is why I said best go there. However if you still want to try above could give you a working emei. Its generic test emei and blocked in some countries thought, so if you need to travel...
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
I thought each rom had efs file, not so sure anymore. download and install 7zip, open the tar md5 rom file with it and ignore the warnings. should be efs. img in there, if not best download one, same csc as you have, if you know what it was before it became corrupt. I think kj4 has one, so you can flash whole gb rom with options efs clear and the pitfile.
If that fails, then perform a factory reset with code, do this only from gb, *2767*3855# in dialer. That might force the efs to reset itself to generic. Should not be needed, but hey it cant harm trying on gb. note own risk
If that fails, flash stock ics which you had in first place and ask them to fix it.
You need them anyway to get original emei back, which is why I said best go there. However if you still want to try above could give you a working emei. Its generic test emei and blocked in some countries thought, so if you need to travel...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Hey baz77,
I tried the same pitfile method with a GB236 Rom built from HongKong and flashed it twice, because I read on this forum somewhere that in the event of errors, missing files and apps after a flash, roms should be flashed atleast once more to get'em fully loaded but unfortunately even that method failed to mount the efs part.
Afterwards, I was just googling for more solutions and I decided to download and flash another GB236 rom Open europe built (wipe version) from Dr. Ketan's stock rom deposites and to my joyous surprise there were 2 extra tar. files, one named efs.md5.tar, so I quickly got my fone in download mode and flashed the rom with pitfile and when that was done, I got the fone back in download mode and Flashed the efs.tar (PDA), CSC, Modem (PHONE) and for the first time in 2 weeks the fone booted up normally as it should with the welcome screen, working lock screen and power button dialog! pheeeewwww!!!
But the imei is still not the same as under the hood, but I guess since the efs part had been corrupted, my fones probabaly using the emergency imei, Im using Alliance v1 with no apprent faults or errors.
i'll flash the GB Rom and try the factory rest code method by you and if it works then dont have to go to samsung and if doesnt then i'll keep using the fone as it is for as long as I have it and keep looking for solutions, if nothing happens then i'll get it sorted from samsung before selling it.
Your help is much appreciated, Thanks baz77!!! :thumbup: :thumbup:
<SAMSUNG><ASONG>from<GT-N7000

back then.. there was an application on playstore that can fix IMEI issues... its called GSII repair.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
It worked mostly on all phones that I have heard of.. including the Note's of my friends whom their IMEIs got toasted.
See if you can give that a shot bud..
Ps. by the way.. most corrupted IMEIs have a mocked imei of 004999010640000
Others said that they were able to restore their original IMEI by flashing to stock GB, root the phone and install Root explorer, after that, you need to go to /EFS folder inside your phone(thru root explorer) and backup first your orig ' nv_data.bin ', now if you see a nv_data.bak in there with a previous date different from the bin file, then delete accordingly the nv_data.bin and rename the bak file to nv_data.bin reboot phone and check if orig IMEI is back on your phone.
Now this isn't applicable if your bak and bin files for ( nv_data) are all on the same date though.
don't try this yet unless your willing to give all possible options to restore back your original IMEI. Don't forget to try first the link I showed to you at the top.
Cheers.
:good:

letters_to_cleo said:
back then.. there was an application on playstore that can fix IMEI issues... its called GSII repair.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
It worked mostly on all phones that I have heard of.. including the Note's of my friends whom their IMEIs got toasted.
See if you can give that a shot bud..
Ps. by the way.. most corrupted IMEIs have a mocked imei of 004999010640000
Others said that they were able to restore their original IMEI by flashing to stock GB, root the phone and install Root explorer, after that, you need to go to /EFS folder inside your phone(thru root explorer) and backup first your orig ' nv_data.bin ', now if you see a nv_data.bak in there with a previous date different from the bin file, then delete accordingly the nv_data.bin and rename the bak file to nv_data.bin reboot phone and check if orig IMEI is back on your phone.
Now this isn't applicable if your bak and bin files for ( nv_data) are all on the same date though.
don't try this yet unless your willing to give all possible options to restore back your original IMEI. Don't forget to try first the link I showed to you at the top.
Cheers.
:good:
Click to expand...
Click to collapse
Hi Letters_to_cleo,
Thank you for the suggestions mate, at the moment Im on Alliance v.1 403 rom, and I have just tried the fix from your link, did the steps1 & 2 restarted checked imei and it's the same serial (#to#) as you have stated, then i tried the step 3 which indicated that the nv_data.bin file is missing from that folder.
I have already gone to certain extents to return the fone in its generic state, so it won't matter if I tried once more besides trying repairs on GB rom is probably much safer then on ICS builts as long as the fone doesnt die on me,(completely again!), I 'll try your 2nd method in a bit and report back after!
Thanks for the support!!:thumbup:
<SAMSUNG><ASONG>from<GT-N7000

yeah that app wont work if you dont have efs backup. It distills from original. bak file the emei, now with the reflash of efs, even before you had lost it. only generic stuff left.
you need as mentioned before to go to samsung to repair emei, or find a phone place that can do it. You can yourself but in most countries its illegal. You need z3d box or equivalent for that, 150$$$$ lol, I have seen people who bought it offer that service for small fee. But be careful as ot could be illegal in your country, even if its going from generic emei to original emei lol.
Oh and you are welcome, been there done that, with the efs stuff. Samsung fixed mine.
My help is free, now if another has this you know how to help them
After Samsung fixes it,stay on gb, root phone and backup efs on multiple locations(pc, cdrom, floppy disk, bank vault you get it) In future when you buy android do that first. How to is in dr ketans toolbox thread in general section.
edit efs backup is not in nandroid, nor titanium backups. In fact still to date there is not one solution that can back everything up on your phone.
Sent from my GT-N7000 using Tapatalk 2

letters to cleo, corrupt emeis are empty or 0000000000000000000000000,
the 490000 emei is given when resetting efs. That is not corrupt anymore to my knowledge
Sent from my GT-N7000 using Tapatalk 2

oh I ran into missing lockscreen issues after fully fixing it, I have in my profile then statistics started a thread which links to a solution for that
Sent from my GT-N7000 using Tapatalk 2

Hi Enseven reporting,
@Letters_to_cleo, the methods you suggested dont work but thanks for trying to helping, i didnt find the bak file in efs folder but there 2 nv_data files, and they're both dated from Jan2011, renaming them just disable's the network and doent change the imei#, it remains the same!
@baz11, Yes mate, you are right this fone's going back to samung bcuz im not looking to $pend 150 on some box that I wont even use twice.
Im not really that fussed about imei not being as same on fone hardware, just as long the fone works, but like you said it probably is illegal to sell a fone with messed up serial no.
And on top of that fone's price would drop for having software issues, only wanted to fix it so that I could sell it on without loosing much $$ from the original price I paid for it, it'll be disapointing since Ive only had the fone for just over 2 months.
And I did manage to fix the welcome/lockscreen/power button issues by flashing efs.tar I got from that wipe version Open Europe Rom but even after the flash, it restore's the needed files but doesnt really prompt the features so I gotta insert this command through terminal emulator: "echo n- ON> /efs/imei/keystr" "sync"and factory reset, then the fone reboots normally with everything working but the IMEI ofcourse!
Wonder if your lockscreen fix works ive looked for it on your profile's statistic's tab but uable to find it, could you plz provide a link. Thanks
Ive tried all methods with some luck and no further progress apart from having to buy expensive equipment, so I guess i'll keep using the fone and looking for any miraculous solution till I resort to Samsung.
P.S: If they cant find a fix for the emmc bug by working on scripts , they should atleast invent a nano tech powder (gadget bug killer) to sprinkle on the motherboard, LOL!!!
because this problem goes way back, like another user said on here you could make a movie about now, and ithink it started off as a scifi now its a scifi/thriller, "shall I wipe before flashing & risk hardbrick Or shall I wait for samsung to pace up the support!!!
Thanks to xda and memebrs for being online 247 and all the support though!!
<SAMSUNG><ASONG>from<GALAXY-GTN7000>using xda premium!!!

Hi En7,
Sorry to hear my steps didn't work on your phone bud.
I checked some forums here in XDA and I've come across this one: http://forum.xda-developers.com/showthread.php?t=1804117. (I'm not sure though if you have come across that link before or not).
It is for the S3 forum but there's a tool in there that you can try to download and run to somehow restore your corrupted IMEI. It's worth taking the risk I should say but who knows..any given tool/info is highly useful and it could be a clear shot in bringing back your original IMEI back right?
Cheers bud!

lol that cracked me up nano powder hahaha good one.
you found the lockscreen fix, its the same fix I found while back from some guru.
I guess you can change emei to original with someone who has such a box. Finding is not to difficult, just need to go to a shop that can repair emei. Preferably Samsung thought, Just go to a samsung service centre, or store where you bought phone. Best unroot and put stock firmware that matches your phones original csc, to avoid anoying questions. Just tell the truth you updated phone and emei was gone/changed and you want original imei back. Samsung can fix it. Note, this time dont use pit or clear csc. Its not needed anymore.
I searched hard and long when I had that issue with emei, wasnt without a backup able to change it back to original, other then Samsung or such a box.
It annoyed the crap out of me. I can relate to what you were going through.
Everybody is nandroid this titaniun backup that, apparently efs is the only thing not standardly backed up with any standard mainstream solution.
Sent from my GT-N7000 using Tapatalk 2

oh, and good idea, maybe you should write a scifi thriller
Sent from my GT-N7000 using Tapatalk 2

[Q] Unrooting & pulldown menu from lock screen questions?

Hi guys, just 2 things to ask:
1) I rooted my phone a few weeks back & thought everything was ok (I used binary's v26 toolkit) & thought everything went ok, however only noticed there were problems when it came to deleting/renaming/modifying anything in /system where my phone would constantly reboot.
So I have been advised to use SEUS to restore stock & to fully unroot - I just wanted to make sure this is safe to do & I won't have any errors etc? I know I will have to backup everything which isn't a problem, but is it fine to use on a 'broken' root? What is the difference between using SEUS to go back to factory & using the phone's factory reset anyway?
I plan to use this short guide: http://www.youtube.com/watch?v=B8LlNufSP2E, can anyone confirm I can use this method in my current situation? I also have CWM, I don't plan to re root after etc, not for a while anyway, so doesn't bother me losing CWM & root!
2) I have only just noticed when I pull down the status bar from the lock screen, only the back & home shortcuts appear, whereas the 'recent apps' shortcut doesnt? Is this normal? I could have sworn it used to be there, makes sense that it's not but just wondered! Probably never noticed it was absent to begin with
Appreciate any help & advice.
Many thanks!

SalamiQueen said:
Hi guys, just 2 things to ask:
1) I rooted my phone a few weeks back & thought everything was ok (I used binary's v26 toolkit) & thought everything went ok, however only noticed there were problems when it came to deleting/renaming/modifying anything in /system where my phone would constantly reboot.
So I have been advised to use SEUS to restore stock & to fully unroot - I just wanted to make sure this is safe to do & I won't have any errors etc? I know I will have to backup everything which isn't a problem, but is it fine to use on a 'broken' root? What is the difference between using SEUS to go back to factory & using the phone's factory reset anyway?
I plan to use this short guide: http://www.youtube.com/watch?v=B8LlNufSP2E, can anyone confirm I can use this method in my current situation? I also have CWM, I don't plan to re root after etc, not for a while anyway, so doesn't bother me losing CWM & root!
2) I have only just noticed when I pull down the status bar from the lock screen, only the back & home shortcuts appear, whereas the 'recent apps' shortcut doesnt? Is this normal? I could have sworn it used to be there, makes sense that it's not but just wondered! Probably never noticed it was absent to begin with
Appreciate any help & advice.
Many thanks!
Click to expand...
Click to collapse
SEUS will completely wipe your phone same as a FTF with data, If you unroot it there will still be the old folders just inactive so for warranty i would just say flash with a FTF but if unsure then just do a SEUS restore

Maddhouse said:
SEUS will completely wipe your phone same as a FTF with data, If you unroot it there will still be the old folders just inactive so for warranty i would just say flash with a FTF but if unsure then just do a SEUS restore
Click to expand...
Click to collapse
I wouldn't have a clue how to use FTF, I am pretty much a noob to all this
But using SEUS to restore will basically get rid of root, just the old files would be there you mean? No way to get rid of them? My main purpose to unroot is because I hear that if I update to 4.2.2 (whenever it arrives!) there is a good chance I will get bootloops & other issues as my root is not 100% fully working. So I don't want to risk it when it comes to updating really.. I am pretty lost with what is the best method to do to get rid of root
SEUS will make my phone go back to how it came out of the box, just to confirm? Sorry for the many questions, am just very cautious!
Thanks for the reply too btw

Yes sues will resort it to out of the box, room gone, folders, pictures etc.
Just one little pointer look into flash tool beta 5 in xz original android and then download a global ftf in android development there is a tutorial about using it on here somewhere, it is always best to keep it to hand just incase something happens while you are nodding then you can easily go back to stock, I think 4.2.2 will be fine upgrading to because it will just delete root
Just found one
http://forum.xda-developers.com/showpost.php?p=10879507&postcount=1
Sent from my C6603 using xda premium

Lol I am getting a bit confused because everything seems to be getting a lil complicated for my understanding
Is it necessary to have global FTF even after I successfully use SEUS to restore back to stock? Like I said I don't plan to re root after this, it has given me a headache for a few weeks trying to figure out what to do haha, I don't want to risk bricking my phone which is prob what will happen knowing me!
I know updating to 4.2.2 will remove root & update fine - BUT would that be the case with a 'broken' root like mine, since mine is not working properly? Otherwise if it's fine to I may as well just leave the phone as it is & update when it's released, that way I won't lose any data etc & have root removed too If however there will be problems which another user has mentoned such as bootloops because of installing root incorrectly, I want to just use SEUS to restore my phone & remove root that way just to be sure. I just wanted to know if that method in the youtube video will be ok to do on mine, because I have said before, my root is 'broken' lol.
Hope that makes sense?

[Q] I'm dead with lost IMEI on Beanstalk with my Xperia ZR

First and most, I am a long-time reader of xda-forum and this is my first account and/or post ever here.
And come with it bad personal news:
My Xperia ZR lost its IMEI and stalled with bootloop on Beanstalk.
I am really thankful to the developers who have made such a charming ROM, at least to me although it's CM based.
However, things become bad for me when I firstly unlock my bootloader (by official instructions of Sony), then I fastboot the boot.img extracted from Beanstalk zip. Then, off with my phone to recovery and I install the custom ROM.
Everything was just fine, my phone worked like a charm on the new ROM with great battery and gaming experiences; however, it was doomed after 5 days of using.
Phone calls could not be heard although the signals were alright.
I thought it was caused by the ROM, then I chose to fastboot boot.img extracted from CM10.2 and proceeded to install the CM10.2.
That was when I messed up with my own phone for the issue persisted with more frequent bootloop.
I reverted to flash a .ftf (claimed to be stock .244 pudding TW
Still I could not resolve the problems of calling.
Then, I relock my bootloader to try to fix the phone with PCC and SUS - By now, I think that was a very risky action to take.
The phone was perfect on 4.2.2 with bootloop and "System process isn't responding"
Thus, I lost my IMEI on the phone which was the major cause for the bootloop (some reading in the forum about resolving bootloop by recovering TA back-ups which I've failed to do at the beginning.
I've struggled with reading and testing out the instructions (re-unlocking by flashtool) just to get back to CWM Swipe and Beanstalk (with bootloop every 15mins).
And, of course, I've checked the status of my phone, unknown IMEI was there.
I know it's desperate to call for your help here because more attentions are made to Z and others but ZR.
I've been thinking about injecting IMEI back to the Xperia ZR phone ('inspired' by the Backup TA and other success on Samsung devices that I've read in the forum to solve the bootloop). I've also read about the legality of such action but swear to my ZR that I would use that for my very own personal purposes.
But you know, I'm now in vain and pain :crying:
Thank you for your reading to this very line.

xperia_loser said:
First and most, I am a long-time reader of xda-forum and this is my first account and/or post ever here.
And come with it bad personal news:
My Xperia ZR lost its IMEI and stalled with bootloop on Beanstalk.
I am really thankful to the developers who have made such a charming ROM, at least to me although it's CM based.
However, things become bad for me when I firstly unlock my bootloader (by official instructions of Sony), then I fastboot the boot.img extracted from Beanstalk zip. Then, off with my phone to recovery and I install the custom ROM.
Everything was just fine, my phone worked like a charm on the new ROM with great battery and gaming experiences; however, it was doomed after 5 days of using.
Phone calls could not be heard although the signals were alright.
I thought it was caused by the ROM, then I chose to fastboot boot.img extracted from CM10.2 and proceeded to install the CM10.2.
That was when I messed up with my own phone for the issue persisted with more frequent bootloop.
I reverted to flash a .ftf (claimed to be stock .244 pudding TW
Still I could not resolve the problems of calling.
Then, I relock my bootloader to try to fix the phone with PCC and SUS - By now, I think that was a very risky action to take.
The phone was perfect on 4.2.2 with bootloop and "System process isn't responding"
Thus, I lost my IMEI on the phone which was the major cause for the bootloop (some reading in the forum about resolving bootloop by recovering TA back-ups which I've failed to do at the beginning.
I've struggled with reading and testing out the instructions (re-unlocking by flashtool) just to get back to CWM Swipe and Beanstalk (with bootloop every 15mins).
And, of course, I've checked the status of my phone, unknown IMEI was there.
I know it's desperate to call for your help here because more attentions are made to Z and others but ZR.
I've been thinking about injecting IMEI back to the Xperia ZR phone ('inspired' by the Backup TA and other success on Samsung devices that I've read in the forum to solve the bootloop). I've also read about the legality of such action but swear to my ZR that I would use that for my very own personal purposes.
But you know, I'm now in vain and pain :crying:
Thank you for your reading to this very line.
Click to expand...
Click to collapse
first thing first, do you have your original imei saved somwhere? one your phone box or on the e-mail you've got from sony for the unlocking code? (they require your imei for that code)
so there should be nothing illigal with reinjecting your own imei.
second thing, i have no idea how to do it...

First thing first
shteren said:
first thing first, do you have your original imei saved somwhere? one your phone box or on the e-mail you've got from sony for the unlocking code? (they require your imei for that code)
so there should be nothing illigal with reinjecting your own imei.
second thing, i have no idea how to do it...
Click to expand...
Click to collapse
I'm rather noob by not following the backing-up tricks before messing with its very inside mechanism, thus, I've lost the code on my device; however, I have the imei code written on the box.
The problem is "I have no idea how to do it either" :highfive:
I've been scrawling around with google help and my reading comprehensive but nothing gained so far.
I've called the service center of Sony in my country and been given addresses of service shops where I would visit in a couples of days.
Thank you for your care and hopefully help may come. :angel:

well, u've bricked ur device hard times..
What abt. TA Partition Backup?
U hv to relock the bootloader and for that u need ur TA partition (Do not use others)
I faced the same prob on my XZ lost baseband and and and
Restored TA partition and locked the bootloader, now my XZ is healthy with twins XZR and BB Q10 lol
Good Luck :silly:
Edit :
Read this -- My post about Bricked XZ

No TA back-up, it's totally doomed
shysparrow said:
well, u've bricked ur device hard times..
What abt. TA Partition Backup?
U hv to relock the bootloader and for that u need ur TA partition (Do not use others)
I faced the same prob on my XZ lost baseband and and and
Restored TA partition and locked the bootloader, now my XZ is healthy with twins XZR and BB Q10 lol
Good Luck :silly:
Edit :
Read this -- My post about Bricked XZ
Click to expand...
Click to collapse
Thank you so much, I've read that later on; however, it was silly of me not to have made any TA back-up :cyclops:
Thus, it's my fabulous brick now lolo=

I need your advice
I am not a good learner but... I've read more these days and found:
http://forum.xda-developers.com/showthread.php?t=2449244&page=4
Quote:
Originally Posted by iconoclastnet View Post
Well, it's md5 seems to have changed, at least for me.
I took a backup of it first thing when the phone arrived, hadn't even put the sim card into it yet, rooted and backed up the TA partition and compared the md5 sum of the backup with the partition.
Then I poped in a sim card, did the usual setup stuff, played with the phone for a few days, did the ota of 518 -> 534, etc.
Before unlocking the boot loader I double checked the TA partition backup, and the md5 sums no longer matched. So I made another backup alongside the original, checking the md5 sums of the new backup, etc.
So, I have two TA backups made at different times from the same phone and they're different in some way. It may only be one bit, I haven't checked to see just how different they are, but they are different. At the time I assumed that it was related to the 534 upgrade, but that may have been just coincidental.
I have no doubt that they're unique to each device, but I'm not convinced that they're constant.
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
Yep. Just make sure to copy the resulting backup somewhere safe (off of the device) at some point afterward.
I just checked with vbindiff what contents actually change after the OTA upgrade. The first part is identical. This was to be expected since that part contains device specific information like the IMEI (0xB2D), SN#, ... . At 0x33D8 are OS version strings stored - which changed since the OTA. In my case that values changes from "1274-8313_14.1.G .1.518" to "1274-8313_14.1.G .1.534". That behaviour was also to be expected. After that, large parts of the files differ. Many of those differences ist just shifted (by some bytes) data. Other parts actually changed entirely. Not sure what is going on there. Be it as it may, i would only restore the newest TA-backup.
Cheers
Click to expand...
Click to collapse
This is the reply of gladiac and something came to my mind:
I've back up my TA by v9.9 (on my bricked phone of course) and receive a zip file in which I have TA.img
By such information above, we have the location for IMEI on hexa table of the file.
In my case of bricking my device by my fool and risky action, I thought of overiding the TA.img to inject my IMEI (now the text on the box and the back of my phone only, not in TA partition any more :crying in to TA.img? Will there be any further harm?
I dare not test it because I am still very vague about my exit if something might go wrong. If problems may arise after my tinkering of the TA.img and restoring the tinkered TA.img back, then, in such scenerio, will my reverting back to the very first TA.img (the not tinkered one) save my bricked phone at the least?
I really dont know if Backup TA can restore TA partition when the phone is in bad state.
It might be silly questions to you but please, I really need help.
Thank you for your appreciation.

xperia_loser said:
First and most, I am a long-time reader of xda-forum and this is my first account and/or post ever here.
And come with it bad personal news:
My Xperia ZR lost its IMEI and stalled with bootloop on Beanstalk.
I am really thankful to the developers who have made such a charming ROM, at least to me although it's CM based.
However, things become bad for me when I firstly unlock my bootloader (by official instructions of Sony), then I fastboot the boot.img extracted from Beanstalk zip. Then, off with my phone to recovery and I install the custom ROM.
Everything was just fine, my phone worked like a charm on the new ROM with great battery and gaming experiences; however, it was doomed after 5 days of using.
Phone calls could not be heard although the signals were alright.
I thought it was caused by the ROM, then I chose to fastboot boot.img extracted from CM10.2 and proceeded to install the CM10.2.
That was when I messed up with my own phone for the issue persisted with more frequent bootloop.
I reverted to flash a .ftf (claimed to be stock .244 pudding TW
Still I could not resolve the problems of calling.
Then, I relock my bootloader to try to fix the phone with PCC and SUS - By now, I think that was a very risky action to take.
The phone was perfect on 4.2.2 with bootloop and "System process isn't responding"
Thus, I lost my IMEI on the phone which was the major cause for the bootloop (some reading in the forum about resolving bootloop by recovering TA back-ups which I've failed to do at the beginning.
I've struggled with reading and testing out the instructions (re-unlocking by flashtool) just to get back to CWM Swipe and Beanstalk (with bootloop every 15mins).
And, of course, I've checked the status of my phone, unknown IMEI was there.
I know it's desperate to call for your help here because more attentions are made to Z and others but ZR.
I've been thinking about injecting IMEI back to the Xperia ZR phone ('inspired' by the Backup TA and other success on Samsung devices that I've read in the forum to solve the bootloop). I've also read about the legality of such action but swear to my ZR that I would use that for my very own personal purposes.
But you know, I'm now in vain and pain :crying:
Thank you for your reading to this very line.
Click to expand...
Click to collapse
dude, i used the same pudding tw file and lost baseband and imei.but later i flashed with official android 4.1.2 ftf file which removed bootloop problems but still i dont have imei or baseband.i have flashed many c5502/c5503 roms and basebands but there was no use.i think the pudding ftf file could be the reason...

Easy fix
The same thing happened to me. Baseband and IMEI were unknown suddenly.
Then I did a factory reset, wiped all caches and flashed cm-11 followed by GAPPS & I got back network.
It was a pain to reinstall all apps and do all the same settings again though.

I remember seeing a stickie on the sp thread. That was a good guide to rooting etc.
http://forum.xda-developers.com/showthread.php?t=2100529
The same was appearing in more than one sub forum. Why can't we have such a stickie here?
I am waiting for my ZR.
Sent from my GT-S5570 using xda app-developers app

ajgo333 said:
dude, i used the same pudding tw file and lost baseband and imei.but later i flashed with official android 4.1.2 ftf file which removed bootloop problems but still i dont have imei or baseband.i have flashed many c5502/c5503 roms and basebands but there was no use.i think the pudding ftf file could be the reason...
Click to expand...
Click to collapse
Actually, I was on Beanstalk (CM based) first, which I can use normally with IMEI and baseband on. I lost them as my nephew touched the "plane" icon. So, the problem was on CM.
For the 'lost' wording, I dont think we lose IMEI and baseband but actually the phone fails to connect to IMEI and baseband data.

ayushag96 said:
The same thing happened to me. Baseband and IMEI were unknown suddenly.
Then I did a factory reset, wiped all caches and flashed cm-11 followed by GAPPS & I got back network.
It was a pain to reinstall all apps and do all the same settings again though.
Click to expand...
Click to collapse
I've tried that but bootloop occured.
On US ftf, no bootloop but wifi cannot be turned on.
On Beanstalk, everything's fine but no IMEI and baseband.
I am using my phone as a paperweight with wifi-connection and good gaming experience, lol

IMEI loss after flashing to CM11

Hello everyone,
i flashed CM10.2 from the FreeXperia Project on my Z1 and it worked fine,
but the camera was very blurry and didn't take pictures at all.
So i decided to flash CM11 (also from FXP), the camera worked damn fine,
but now the IMEI is set to 0 (and IMEISV to 26, if thats a matter).
Without the IMEI my provider is blocking my access to UMTS and mobile
connection, so the phone is pretty much useless.
So my question is - is there a way to set the IMEI or flash it in from previous backups?
Thanks in advance
Ps: Sorry, forgot to mark it as a question and can't do it from editing.

Ok, i got the settings back by doing a full wipe and reflashing the stock rom.
Now i try to find a tool, that makes a backup of my efs-partition and is able
to restore it on cm11, if the IMEI is getting killed again.
The only tools i find for this are for other phones (though not safe for z1) or
not from reliable sources. Does somebody know a tool like that?
Thanks in advance

Nath.Schwarz said:
Ok, i got the settings back by doing a full wipe and reflashing the stock rom.
Now i try to find a tool, that makes a backup of my efs-partition and is able
to restore it on cm11, if the IMEI is getting killed again.
The only tools i find for this are for other phones (though not safe for z1) or
not from reliable sources. Does somebody know a tool like that?
Thanks in advance
Click to expand...
Click to collapse
I heard not heard of such a tool for the Z1. I remember reading about IMEI 0 some time ago, but don't remember many details. Search more, it's been mentioned before. You may have to go back to a stock FTF to fix it.

[Q] RUU

Hi, I did a lot of things with my One Mini 2 and I actually really don't know what to do anymore... So much options and yet there always seems to be a problem. Let me explain everything.
What I did:
-flashed a custom rom, then went back to a stock rom of this forum
-flashed the dt2w kernel, it messed up my phone so I then flashed the liberty one, which worked
But with the liberty one I had some memory problems, for exemple I couldn't take screenshots... That's why I decided that I wanted to put my phone just as it was when I bought it, I really hope that's possible, by that I mean having official firmwares etc, therefore being able to do official upgrades from my phone (is that what OTA is?).
I looked on internet and it looks like what I need is RUU, as it includes everything (from what I understood)... I know a lot of threads were made about this, but quite a few months ago, so that's why I'm making a new one, and to make things clear.
Also, I downloaded an official kernel from htcdev.com, but each time I tried flashing it with TWRP, it "failed".
So, if you guys have an answer, solution or, in best case, the actual RUU, that would be great.
Thanx

Linkalex1 said:
Hi, I did a lot of things with my One Mini 2 and I actually really don't know what to do anymore... So much options and yet there always seems to be a problem. Let me explain everything.
What I did:
-flashed a custom rom, then went back to a stock rom of this forum
-flashed the dt2w kernel, it messed up my phone so I then flashed the liberty one, which worked
But with the liberty one I had some memory problems, for exemple I couldn't take screenshots... That's why I decided that I wanted to put my phone just as it was when I bought it, I really hope that's possible, by that I mean having official firmwares etc, therefore being able to do official upgrades from my phone (is that what OTA is?).
I looked on internet and it looks like what I need is RUU, as it includes everything (from what I understood)... I know a lot of threads were made about this, but quite a few months ago, so that's why I'm making a new one, and to make things clear.
Also, I downloaded an official kernel from htcdev.com, but each time I tried flashing it with TWRP, it "failed".
So, if you guys have an answer, solution or, in best case, the actual RUU, that would be great.
Thanx
Click to expand...
Click to collapse
Still no RUU's avaiable as HTC wont release them. your best option is to use TWRP backup and restore.
Original stock backup

Thank you, but my backup kind of disappeared... I saw your post where there was the "HTC Original Backup.zip", I tried to flash but again it failed... Am I supposed to flash it as a backup?

Linkalex1 said:
Thank you, but my backup kind of disappeared... I saw your post where there was the "HTC Original Backup.zip", I tried to flash but again it failed... Am I supposed to flash it as a backup?
Click to expand...
Click to collapse
You need to send it as it is to your phone and use TWRP > restore. choose file and done.

Thanx so much for answering... I uses the backup you told me to. Although I had to use the "install" option instead of the backup one, it now works perfectly! But how do I know if my phone is "official"? Are the upgrades going to be made straight from the phone?

Linkalex1 said:
Thanx so much for answering... I uses the backup you told me to. Although I had to use the "install" option instead of the backup one, it now works perfectly! But how do I know if my phone is "official"? Are the upgrades going to be made straight from the phone?
Click to expand...
Click to collapse
Yes OTA updates should work just fine. just look for updates in settings>about >software update.
you may have one for polaris office.

Hi, I just want to check this too before I screw up wife's phone..
She has CM12 on her phone now as I replaced recovery as well as unlocking bootloader. Now she wants it back to stock as too many things crash on her. I get that I can install your backup but what worries me is that other posts have said you need the stock recovery to allow for OTA updates to work and the link to this no longer works.
She MUST have OTA updates or my balls will be removed, so can you please confirm this, but also explain why.
Thanks (on behalf of my testicles and unborn children!)
(Oh, and she wants it unrooted ant the bootloader relocked)

arm1e said:
Hi, I just want to check this too before I screw up wife's phone..
She has CM12 on her phone now as I replaced recovery as well as unlocking bootloader. Now she wants it back to stock as too many things crash on her. I get that I can install your backup but what worries me is that other posts have said you need the stock recovery to allow for OTA updates to work and the link to this no longer works.
She MUST have OTA updates or my balls will be removed, so can you please confirm this, but also explain why.
Thanks (on behalf of my testicles and unborn children!)
(Oh, and she wants it unrooted ant the bootloader relocked)
Click to expand...
Click to collapse
Stock Recovery
To unroot just lock bootloader:
fastboot oem lock