Ive been reading about the need and importance to backup the TA Partition. Earlier I had it backed up on my C Drive but later when reverting back to windows 7 i accidentally formatted the backup along with it. So anyways, I had unlocked the booloader which basically wiped out clean all my personal data, then installed TWRP and wiped out the phone and flashed PA Rom to try it out. So later went back to stock using Flashtool app, everything went smooth and all apps are still working as it should. I was able to use Walkman app, Bravia Engine still works, OTA works, etc. So what exactly am I missing by not backing up the TA Partition? Ive come from Nexus line so please excuse me if I come as a bit naive lol. Any response is appreciated.
bushako said:
Ive been reading about the need and importance to backup the TA Partition. Earlier I had it backed up on my C Drive but later when reverting back to windows 7 i accidentally formatted the backup along with it. So anyways, I had unlocked the booloader which basically wiped out clean all my personal data, then installed TWRP and wiped out the phone and flashed PA Rom to try it out. So later went back to stock using Flashtool app, everything went smooth and all apps are still working as it should. I was able to use Walkman app, Bravia Engine still works, OTA works, etc. So what exactly am I missing by not backing up the TA Partition? Ive come from Nexus line so please excuse me if I come as a bit naive lol. Any response is appreciated.
Click to expand...
Click to collapse
pre 4.4 it would break track ID and x-reality, it does look as if Sony have fixed these 'bugs'. A valid TA may/is still needed to get the phone repaired under warranty
blueether said:
pre 4.4 it would break track ID and x-reality, it does look as if Sony have fixed these 'bugs'. A valid TA may/is still needed to get the phone repaired under warranty
Click to expand...
Click to collapse
Don't mean to sound rude but can you please provide a source of this info? I've done searches and this hadnt come up. Also how does one check the validity of the TA?
I unlocked my boot loader the first day I got my Xperia Z Ultra, and destroyed the TA not having made a backup.
I've never missed what I never had. I don't use the Sony music or video service so I can't tell you if they would be broken due to the lack of DRM keys,and I've never had any app complain they're missing.
In the very early days the Sony Camera App would force close, but I switched to A Better Camera app, later versions of the stock ROM didn't have the problem.
Overall then, don't panic, they don't matter.
hey thanks for the reply. Ive got everything still working as it should so as mentioned by the earlier poster id agree its only an issue with pre kitkat roms and perhaps for warranty purpose.
speculatrix said:
I unlocked my boot loader the first day I got my Xperia Z Ultra, and destroyed the TA not having made a backup.
I've never missed what I never had. I don't use the Sony music or video service so I can't tell you if they would be broken due to the lack of DRM keys,and I've never had any app complain they're missing.
In the very early days the Sony Camera App would force close, but I switched to A Better Camera app, later versions of the stock ROM didn't have the problem.
Overall then, don't panic, they don't matter.
Click to expand...
Click to collapse
Related
Ok, so first off, I was interested in the prospect of using the Droid3 camera because I heard it was better and supported high speed video recording (something that I really want on the Atrix) but I heard that you had to be Deodexed. Well, I knew that if I unlocked my bootloader and installed a custom ROM such as Alien or CherryPie, it would work, but I didn't want to unlock my bootloader. I was rooted though.
So then I decided to google how to manually deodex, and I came across the program xUltimate whatever, followed the directions (although it seemed to be intended for the Droid and not the Atrix, I don't think I should've done that) and part of the process through running xUltimate, I got a message saying that I was out of space on my Atrix relating to the process it was in the middle of doing, and was like, oh crap.
My phone didn't start, but I had made a recovery a couple of days earlier in Tenfar's CMW, so I went to restore that. Then when that was restoring, it froze on some process when it was restoring, and I let it try and try for hours, but to no avail, because it had been hours and it was still stuck on the same spot. So I restarted my phone.
Well, then upon my phone starting, everything was gone in terms of my apps, and the stock gingerbread background was there. I thought, well, maybe it's fine and I'll just restore my apps with TiBu, and everything will be fine. That wasn't the case at all because any app that I downloaded from the market with the exception of a few would automatically force close. So I couldn't get TiBu to work, or Superuser, or anything.
So at that point I knew that I had seriously messed up some files on my phone, and I decided I was gonna flash .sbf. So I got the stock 2.3.4 .sbf and flashed it with RSD Lite 5.3.1.
It flashed gingerbread, and when it rebooted, everything looked fine and dandy, but it was exactly the same problem, where apps would force close.
Then as a last hope of solving the problem I tried to use fastboot to recover my phone with the nandroid backup that I had made, but it said that the image file was too large. And that also probably has something to do with the fact that I can't actually use fastboot to do that unless I have an unlocked bootloader, right?
So my question is, how can I fix it? How can I start over fresh (since flashing .sbf didn't wipe everything) so that those system files that I messed with when I was running the deodexing utility are returned to their proper state?
I mean, at the moment, it works as a phone, it receives and makes calls, and I can send texts and take pictures, and use the stock browser, but no other app will open.
And secondly, has anyone gotten the 120fps video recording working with the d3 camera apk?
But of course, more importantly, how do I get out of this rut?
Thank you so much and I'm really sorry for writing so much, I just wanted to give you as much info as possible so that you could come up with the best answer. And I apologize for my stupidity,
Thanks again,
did you try a factory restore after the sbf flash? you have to do that to restore the phone to the orignal state. flashing the.sbf doesn't do it...
Sent from my MB860 using Tapatalk
thank you so much, after doing the factory reset, it works fine now. Now to go mess with it again hehehe.
Sent from my MB860 using XDA App
Glad your sorted as to your fastboot problem. Use moto fastboot as it splits large files for you.
Sent from my MB860 using XDA App
So, I thought I had fixed the problem, but after unlocking the bootloader, I installed Alien, and the radio is all wonky...I'm not getting service 99% of the time, and that's kinda really bad, and, yes I checked the APNs, and there were no problems there (at least I think, I restored default) and I even tried flashing a radio, which made no difference. And I know that flashing using RSD is bad but I didn't know better at the time so I reflashed stock Gingerbread 4.5.91, but the radio problem is still there.
And could someone tell me what I'm doing wrong because I've tried flashing two different roms (Alien and the Star Wars one) and it seems as if its not actually doing everything that it should, for example the star wars one, there is no camera app, or rather it force closes, and the bootanimation and boot image are stock at&t, and the lockscreen is default....and I even checked the build.prop which should have been modified for the d3 camera and it wasn't modified, which led me to think that anything that involved root access didn't work when flashing the rom. Further proof for that idea is that after I flashed either rom, I lost root access and had to re-root my phone.
This is really weird, and it's starting to bug me because now my phone can't even be used as a phone
Thank you for your help.
I bought my phone almost a week ago, but I only have a 7 day return policy so I need to figure this out quickly.
It's the C6802, bought in China (where I live), with HK firmware 1.4.1.B.0.475. Naturally, right when turning on the phone, it says to update to 532. The phone shop merchant did this for me when I bought it via PC (not sure what software he used), and afterwords the phone would suddenly just go dead and restart.
So I went back to stock 475, worked fine. Once home, I tried firmware 526, using flashtools, to see if it was stable, and same deal. The seller I bought it from says all the other firmwares are really buggy and I should just wait until there is a newer firmware to upgrade. But by that time, I won't be able to return the phone if indeed the problem IS the phone and not the firmware.
I was able to unlock the bootloader, root the phone, and install CWM, but every time I try to use CWM (whether backup, restore, or just navigating), after a couple seconds, the phone goes dead and restarts (same problem when using other firmware). I tried to install TWRP via goodplay, and that didn't work at all. I'm not sure how to flash it so I can use it during recovery because CWM doesn't work and I haven't seen an img of it for the z ultra (I'm still pretty noob at this as you can probably tell).
So does some firmware just bug out on some phones, like in my case, and will future firmwares fix this random death/restart? Do I just have extremely bad luck with CWM and firmware? Or is it a hardware problem and I should return the phone? Or is there a way to update to 532 and fix the crash problems? My first born for some expert advice.
The software you need to update on your PC is the Sony PC Companion suite. It should not prompted you to install it when you first plugged your phone in to your PC. Download that & see if you can update to 532 through there before you try anything else. To me it sounds like a bad flash & redoing it may resolve your issues. Hopefully...
Nuwidol said:
The software you need to update on your PC is the Sony PC Companion suite. It should not prompted you to install it when you first plugged your phone in to your PC. Download that & see if you can update to 532 through there before you try anything else. To me it sounds like a bad flash & redoing it may resolve your issues. Hopefully...
Click to expand...
Click to collapse
OK, I'll do that first thing tmrw morning, right now I'm making back-ups of everything using titanium and nandroid. But I can only use them when the phone is on, they don't work during recovery, nothing does. And using TWRP even with the phone on just causes it to die and reboot as soon as I click "OK" - is this something to be concerned about? It still rebooting even with CWM (in recovery) and TWRP (in normal bootup), even with stock 475 firmware, this certainly shouldn't be normal, right? I'll update how the PCC flash to 532 goes tomorrow...
I agree with Nuwidol, it does sound like a bad flash...
To put thing simple, forget CWM / TWRP for the moment, try 'CLEAN' install your phone with the latest firmware (532), then test using it for a day or two and see if it works properly. Yes, all firmwares released by Song so far for this phone are kind of buggy but nothing serious - just minor issues I would say, and definitely not random death or restart like you said.
To clean install, I like using SUS (Sony Update Service) because, unlike PC Companion which packs with a whole bunch of functions, SUS only deals with one thing, to reinstall or update firmware for your phone, and it works well.
First, backup whatever you find important, then relock you bootloader (restore from your TA partition backup, and flash back any stock FTF... stuff like that...).
Hook up your phone with SUS by following its instruction. Choose 'erase / format everything (...or something like that)' when it provides you with update options. Sit and wait until it finishes.
Turn on your phone, skip WiFi setting as well as the Google account, go straight to Home. Then:
'Settings' --> 'Backup & reset' --> 'Factory data reset'
Choose 'erase / format everything' (or something like that) again.
After reboot, you should have a very clean system by now. Use it as is for a few hours / days and see if anything strange comes up. If nothing strange comes up, then your phone is fine; if not, go return it or ask for exchange.
One minor note, rooting the phone is ok, pretty straightforward and safe to do I would say. But unlocking the bootloader? Well... it is ok too, unless you know what you're doing.
Hope this help.
so far so good
littopillo said:
I agree with Nuwidol, it does sound like a bad flash...
To put thing simple, forget CWM / TWRP for the moment, try 'CLEAN' install your phone with the latest firmware (532), then test using it for a day or two and see if it works properly. Yes, all firmwares released by Song so far for this phone are kind of buggy but nothing serious - just minor issues I would say, and definitely not random death or restart like you said.
To clean install, I like using SUS (Sony Update Service) because, unlike PC Companion which packs with a whole bunch of functions, SUS only deals with one thing, to reinstall or update firmware for your phone, and it works well.
First, backup whatever you find important, then relock you bootloader (restore from your TA partition backup, and flash back any stock FTF... stuff like that...).
Hook up your phone with SUS by following its instruction. Choose 'erase / format everything (...or something like that)' when it provides you with update options. Sit and wait until it finishes.
Turn on your phone, skip WiFi setting as well as the Google account, go straight to Home. Then:
'Settings' --> 'Backup & reset' --> 'Factory data reset'
Choose 'erase / format everything' (or something like that) again.
After reboot, you should have a very clean system by now. Use it as is for a few hours / days and see if anything strange comes up. If nothing strange comes up, then your phone is fine; if not, go return it or ask for exchange.
One minor note, rooting the phone is ok, pretty straightforward and safe to do I would say. But unlocking the bootloader? Well... it is ok too, unless you know what you're doing.
Hope this help.
Click to expand...
Click to collapse
Litto... your awesome. This has probably been one of the single most helpful replies in my history on xda. I did everything you said, step by step, and I was able to flash 532 without any problems, and so far, after using it for half a day, it's been completely stable. Granted, I haven't installed a single app on it yet or synced anything, I'm hesitant, ha. But I'll do that tonight, and Lord willing, nothing will happen. But so far so good. You really helped me a ton, thanks so much. :victory:
As for the issue about unlocking the bootloader, well, I did it because I was told that is the only way you can install custom ROMs and CWM? So for flashing anything besides stock, I would think it's pretty much mandatory, am I wrong? I hope to install radioactive or paranoid android eventually, but of course with it crashing during CWM and any firmware upgrade, that wasn't an option before. I'll use it for awhile longer with the stock (but rooted) 532 and if no problems occur, I'll move onto flashing the CWM/TWRP img by krabappel, which means then I can finally flash a custom ROM. Here's hoping...
Hi! I got my Sony Z2 (or Sirius) a bit ago, August. After about two to three weeks of using it, I decided that I didn't like the design, and so I spent a day or two researching everything on it before flashing Cyanogenmod.
I've gone through Cyanogenmod and Carbon ROM. Both excellent ROMs! I miss my high quality camera and my excellent audio though... Although I did end up installing Viper4Audio or whatever its called, the amazing EQ, I do miss Walkman and its superior sound quality.
So, Ive been wanting to revert back to the stock ROM. That's where I'm stuck. I don't know what ROM to flash, or what build etc. I also don't know when I should do my TA Partition restore, after or before the flash? I'm not too tech-savvy android wise.
Thanks guys, love you all and the amazing forums here.
All help appreciated!
(I have attached myI'vebout Phone' section of my settings and proof of my TA backup. The TA backup is on my phone cause I kept a spare copy on my phone incase my computer broke... Luckily I did, cause my PC did break. I've got a new one now so its all good.)
xphiles said:
Hi! I got my Sony Z2 (or Sirius) a bit ago, August. After about two to three weeks of using it, I decided that I didn't like the design, and so I spent a day or two researching everything on it before flashing Cyanogenmod.
I've gone through Cyanogenmod and Carbon ROM. Both excellent ROMs! I miss my high quality camera and my excellent audio though... Although I did end up installing Viper4Audio or whatever its called, the amazing EQ, I do miss Walkman and its superior sound quality.
So, Ive been wanting to revert back to the stock ROM. That's where I'm stuck. I don't know what ROM to flash, or what build etc. I also don't know when I should do my TA Partition restore, after or before the flash? I'm not too tech-savvy android wise.
Thanks guys, love you all and the amazing forums here.
All help appreciated!
(I have attached myI'vebout Phone' section of my settings and proof of my TA backup. The TA backup is on my phone cause I kept a spare copy on my phone incase my computer broke... Luckily I did, cause my PC did break. I've got a new one now so its all good.)
Click to expand...
Click to collapse
you can use flashtool from flashtool.net and a FTF(top of general section) to revert to total stock
just run the script to restore your TA Partition backup, it will relock your bootloader( try looking at the fourm thread you use to backup your TA)
I don't know what version to install, when I got my phone it WAS unlocked, came with a Telstra sim but I use an Optus sim now. I don't know what to do, or what version to download...
Scratch that. I'm just going to use the latest Australian Unbranded version. If I get a ****ed up Kernel again or something, at least I'll know how to fix it this time due to previous trial and error after flashing the wrong thing All praise Doomlord's kernel ahaha
Soft bricked!
Soft bricked my device. (Something in-between hard and soft? Screen doesn't come on like in soft brick, but it isn't hard bricked. I got this after restoring a backup [I did that last time and got the same result].) Great, now I have to flash another kernel over and do the FTF. I can only access fastboot as far as I'm concerned, but that's good, I can at least flash things!
Great! Fixed my phone. Well, partially. When I attempt to restore my TA Partition backup... the CMD window doesn't come up with any options... ? It's as if it's just backing up? I don't know. It doesn't seem to be doing anything at all, neither does it make an actual backup file. All it does is create a few files in the folder the .bat is in, and when it's done deletes them...
Hello everyone. As you saw in the title my right speaker(or lower one) isn't working properly. It sounds like 25% of the left one (or above one). I noticed that after I flashed stock ROM thru flashtool and I wiped everything and also I ticked MASTER-RESET in TA section. I've flashed XGEN rom thinking it would fix the problem without a success. AFAIK I should still have my guarantee and ofc I can't find my TA Backup anywhere.
What I am thinking right now, if reflashing with flashtool again will fix the problem. And if it won't, should I relock my bootloader without TA and send it to my carrier to try to fix the problem? Also is there anyway to see if your drm stuff is missing when bootloader is locked other than testing camera and etc. Hope you understood me and could help me fix the issue.
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
Have you updated your vendor firmware?
sotosgolf said:
Have you updated your vendor firmware?
Click to expand...
Click to collapse
Thank's for the reply, Yes, I've tried, with command line, MiTool and even Xiaomi's Pro tool I've been at this since yesterday The attempts mentioned "completed successfully" but NO wifi or SIM recognition! Motherboard? the phone has been restored to miui 10, and "actvated" using an "OTG" cable and looking thru the settings for any clues. the microsd card is recognized, bluetooth, everything else seems to be working. any thoughts? I've contacted "parts" dealers and I'm waitng. I think I'll take another break and come back to it over the weekend. Thanks for listening. Phillip
[email protected] said:
Thank's for the reply, Yes, I've tried, with command line, MiTool and even Xiaomi's Pro tool I've been at this since yesterday The attempts mentioned "completed successfully" but NO wifi or SIM recognition! Motherboard? the phone has been restored to miui 10, and "actvated" using an "OTG" cable and looking thru the settings for any clues. the microsd card is recognized, bluetooth, everything else seems to be working. any thoughts? I've contacted "parts" dealers and I'm waitng. I think I'll take another break and come back to it over the weekend. Thanks for listening. Phillip
Click to expand...
Click to collapse
I've been on custom ROMs since 2013 and fixing smartphones since 2015. I've only seen hardware related damage because of software only once and it was after someone flashed the full firmware of an entirely different phone into his own.
Don't spend the money on the motherboard before checking other software aspects.
Also (IF it's a hardware issue) your antenna cable might have gotten out of place because of a fall. You can't really know until you open the phone.
One can't really know, until they open the phone. If you're still on warranty, get it to your repair center.
sotosgolf said:
I've been on custom ROMs since 2013 and fixing smartphones since 2015. I've only seen hardware related damage because of software only once and it was after someone flashed the full firmware of an entirely different phone into his own.
Don't spend the money on the motherboard before checking other software aspects.
Also (IF it's a hardware issue) your antenna cable might have gotten out of place because of a fall. You can't really know until you open the phone.
Click to expand...
Click to collapse
If he Will open The back of the phone.
He will loose his Phone Warranty.
Flashed Th Stock MiUi.
Then Go To Service Centre.
If you have backup Restore The Backup.
Olystem said:
If he Will open The back of the phone.
He will loose his Phone Warranty.
Flashed Th Stock MiUi.
Then Go To Service Centre.
If you have backup Restore The Backup.
Click to expand...
Click to collapse
I didn't realize it looked like an urge for someone to open their phone without knowing what to do.
I'll edit.
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
It seems you lost/corrupted your EFS partition which contains your device IMEI/wifi/communication settings.
This is a problem in Xiaomi phones and Samsung phones as far as I remember. Once you start playing with custom roms this problem happens. I've always backup this "EFS" partition as soon as I unlock any xiaomi phone and it saved me couple of times when custom roms corrupts this partition I just boot to TWRP and restore it and it always works and I get sim card / wifi back again.
I'm not sure if there is a way to restore your EFS partition other than send it back for service center.
Based on your reply, Question(s) If the phone is "working/functioning" in my case "without wifi & sim" can I assume that my efforts to "bring back to stock" were successful? This is really what I've been wrestling with, Firmware, Stock rom, etc. Bootloader is still unlocked, Stock Recovery in place, I hope all that leaves is securing part(s) in this case a MotherBoard (modular?) to get "wifi & simcard" working again? Thank's XDA
The_wolf88 said:
It seems you lost/corrupted your EFS partition which contains your device IMEI/wifi/communication settings.
This is a problem in Xiaomi phones and Samsung phones as far as I remember. Once you start playing with custom roms this problem happens. I've always backup this "EFS" partition as soon as I unlock any xiaomi phone and it saved me couple of times when custom roms corrupts this partition I just boot to TWRP and restore it and it always works and I get sim card / wifi back again.
I'm not sure if there is a way to restore your EFS partition other than send it back for service center.
Click to expand...
Click to collapse
REPLY... funny that you mention this "EFS" one of the backups (4) of the PE rom I remember seeing this partition and only this one "saved" how can I re-flash this? Its still on the SD card I pulled, I'm going to check it or just save it for a tech when I bring it in for service and discuss it.
[email protected] said:
REPLY... funny that you mention this "EFS" one of the backups (4) of the PE rom I remember seeing this partition and only this one "saved" how can I re-flash this? Its still on the SD card I pulled, I'm going to check it or just save it for a tech when I bring it in for service and discuss it.
Click to expand...
Click to collapse
Easy just boot to TWRP and chose restore. Select your backup which contains EFS (Deselect other options like system, data etc.) and restore it.
Then boot to android and it should pickup the sim card and wifi.
Taking a break, tired... I have to re-install TWRP, then I'll check the SDcard tomorrow, and Post a GOOD conclusion... I hope! while i have your attention, as far as "service" any reccomendations? I split my time in Philadelphia/Maryland or I could ship if needed. Thank-you!
This happened to my girls poco, she has PE on it. All of a sudden thebphone dint read sim or sd (wifi was good). I switched the slots for each, had no effect, then i took her whole tray and inserted it into my poco where they worked. My sim and sd dint work in hers.
I updated vendor/firmware(no effect), clean flashed rom etc did everything, made a google backup and a twrp backup of data partition.
I ended up using mi flash to put miui fully back and it still dint work. I spent the night trying all this stuff and went to bed frustrated.
I woke up and decided ill just bring it to the phone repair shop downstairs and see (he has a poco). I have no idea how but we put her sim in and it worked, just like that, sd card also. I went back up installed twrp, flashed pe, restored data and she was right back to where she was after moving backup files.
I dont know if all this helps but its my short anecdote.
The_wolf88 said:
Easy just boot to TWRP and chose restore. Select your backup which contains EFS (Deselect other options like system, data etc.) and restore it.
Then boot to android and it should pickup the sim card and wifi.
Click to expand...
Click to collapse
I knew there was a "fix" I couldn't believe it was a "hardware" problem either... 2 good articles on "EFS Partitions" one here on XDA Read Up all!!! I'll post a "conclusion" when I
attempt tomorrow, need a break! Thanks too all that replied. Phillip
Poco is BACK!!! It was the EFS partition!, not a hardware issue at all, recovered from a backup after re-installing TWRP. Thanks to all... and especially Wolf88!
Sorry for the delay, out enjoying the day, ... https://dl.twrp.me/beryllium/ ... I used "3.2.3.2- Beryllium" if you have a "backup" just de-select everything but the "EFS" partition, thats what I did and it recovered successfully! Good luck!
poco wfi
hi just asking about backing up my EFS files as in imei number as there can come corrupt.i have backed them with twrp on google pixel rom not original rom will be ok as back up
berty321 said:
hi just asking about backing up my EFS files as in imei number as there can come corrupt.i have backed them with twrp on google pixel rom not original rom will be ok as back up
Click to expand...
Click to collapse
ROM doesn't matter. So long as you have the EFS partition backed up, it is good.
Some time ago it happened to me as well - no cellular and wifi. I fixed it by restoring from a full backup. I keep it on the SD so I can torture my phone any way I see fit and get away with it when I sc*ew things up.
Good to know the specific reason for losing the comms tho. Thanks for specifying. Next time I get there I'll start with efs restoration, instead of full system restore.
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
i happen to suffer from the same problem and I dont have a backup of efs or anything what solution can you give me?
[email protected] said:
Hello, I've owned this phone since March and upon purchase went straight for "rooting" and the Pixel Experience ROM, I was successful with the flashing and haven't looked back until last weekend
I updated the PE rom and something went wrong! As of today I have a device that doesn't "see" wifi and the sim card(s). I've re-flashed several times "manually" even used the Xiaomi Fastboot Toolkit
on the last 2 attempts hoping the "modem/sim" would flash, apparently nothings worked. Thinking about getting a replacement MB for it as a last resort. Help please? Phillip
Click to expand...
Click to collapse
You wipe the vendor and esf partition. You lost imei ,and wifi . Try hardware test ,because you lost gyroscope and etc working .flash a with fastboot stock miui and fő service .
My friend get same in note 7