I'm having the documented problem of no data connection, always on roaming, after flashing to CM 10.1. My prior rom was CleanRom 5.1, and I have several nandroid backups from various roms over the last few months. GS3 (d2vzw) with root and unlocked bootloader.
So the question is... What's the best way to restore IMEI info and get mobile data back?
As far as I can tell from the dev forums, these are the options, but there are a couple of steps I'm not sure of:
Option 1: Flash a nandroid recovery, backup IMEI using terminal emulator, and then crack-flash away
1. If I restore my phone to a previous backup, is the correct IMEI information included?
2. Also having a problem getting the MD5 sum's to match. Should I flash through ADB instead of clockworkmod? Or use Odin to get back to stock and then re-root? If correct IMEI included with flash back to stock?
3. Assuming I restore a nandroid, the plan was to use "reboot nvbackup" in terminal emulator to save IMEI info.
4. Flash back to CM 10.1.
Option 2: Use IMEI Generator and NV Reader/Writer:
1. Based on this thread: http://forum.xda-developers.com/showthread.php?t=1804117
2. Problem: The link to the generator tool in the OP is broken (404). I can get the converted IMEI number from an alternative program, but don't know how to format the text file correctly to use with NV Reader/Writer. Does anyone have a standard format of a dummy IMEI text file?
If you screwed up your IMEI file, what would you do? Mucho gracias.
Okay, I just fixed this issue after spending the better part of 2 days flashing ROMs, messing up my phone worse, and even calling vzw for support. Nearly tried to cash in on the warranty.
Steps taken (without any guarantees):
1. Flashed to stock ICS using ODIN. Flashed stock kernel as well.
2. Rooted the phone.
3. Downloaded ez-unlock (bootloader) from Google Play. Unlocked bootloader.
4. Along the way, I had a problem with my phone booting into factory mode, so I edited the efs file (labeled "factory" something or other) to say "ON" as opposed to "OFF". It's counter intuitive, but on is off and off is on.
5. Also went through the entire process of using NV reader/writer software. Tip: search for the explanatory video... it's a lifesaver. I ended up writing the correct imei file back to the phone.
6. Probably unnecessary, who knows, but I erased the efs file (after backing it up to Dropbox first). I also backed up the IMEI file.
7. Used Root Manager to get to clockworkmod, factory reset, and turned the phone on again, hoping to recreate the efs file. Efs was recreated, but this didn't fix the problem... Not yet.
8. Re-rooted phone. Re-unlocked boot loader.
9. Used a combo of Astro File Manager and ES File Manager to restore refs and IMEI files to proper place in phone. First downloaded (from Dropbox) to internal SD with Astro, then moved to top level system/root folder with ES.
10. Using ROM Manager, rebooted to clockworkmod and factory reset, clear cache, flashed LiquidSmoothRom and GApps, then cleared dalvik cache. (Note: this rom was pre-rooted but unlocked bootloader again anyway to make sure).
11. By now, I'm no longer getting the factory mode popup annoyance, my imei info is correct in settings > about phone, but still not getting mobile phone or data.
12. Here's the key, I think: Activated a backup phone, and in so doing, deactivated the sg3. Went onto vzw website and activated the Sim for the sg3. Now I have a working phone.
It may have been one crucial step, or maybe a combination of all the steps, maybe even a Christmas miracle. Just happy to have my best friend... err... phone back.
Please note: At one point while using a CM10 ROM, I noticed my imei info was correct, but not the phone number. I actually downloaded an app that lets you edit your phone number. Not sure if that did anything, but want to be thorough. Anyway, noticing that was what led me to focus on trying to reset the Sim. Vzw told me to do a battery pull and take out the Sim for 10 seconds, but that didn't do squat.
FYI, there's no *228 option on sg3. It was news to me. Hope this helps someone.
Sent from my SCH-I535 using xda app-developers app
Related
Hi,
I am trying to restore a couple of nandroid backups, but a Device Administrator app gone "quirky" seems to materialize no matter what I do. I did a CWM Wipe, restored the nandroid backup before the app went bad. However that did not work, the app was still misbehaving. So I wiped again, restored a nandroid backup from before I had installed the app. Still the app shows up again. It has in effect locked me out of the device.
Can anyone tell what can I do to get rid of the app?
Are these Device Admin app supposed to persist like this? Or am I doing something wrong?
Do I need to choose a different wipe mode (I chose the normal one, which wipes /data/, /cache etc). I did not try to wipe /cache separately, as the first wipe does that by itself. Neither did I wipe the dalvik cache, as I thought they are not relevant here. I don't see any relevant files in the sdcard either, though how the app reappears in the nandroid restore before it was installed is a mystery.
Should I mount more partitions before wiping, like the data/cache etc.
Since the wipes don't seem to make it go away, I am not even sure flashing a different ROM would get rid of this app either, however I can try that (since I was planning to anyway, before this mishap). If that doesn't work either, I might just have the most unusual case of bricking ever.
The XDA forum does not seem to be much info about device-admin apps and my search-fu is not good enough today to find anything directly relevant about the other stuff.
PS. btw the app actually modifies the lockscreen. So I don't actually see the files it has with the pre-app restore, however the lockscreen still comes up, perhaps because of some remanant of the app or because of a setting it left in there somewhere.
efs?
Just to add more info, I see some files in /efs, which look relevant to the lockscren/ They have file names like this "/efs/cryptoprop_lockscreen".
Would these files store the data this app stored. I fortunately have an EFS backup, should I consider restoring these files.
If someone doesn't know the answer, can they suggest which devs would be good to ask about this.
AnDruid said:
Hi,
I am trying to restore a couple of nandroid backups, but a Device Administrator app gone "quirky" seems to materialize no matter what I do. I did a CWM Wipe, restored the nandroid backup before the app went bad. However that did not work, the app was still misbehaving. So I wiped again, restored a nandroid backup from before I had installed the app. Still the app shows up again. It has in effect locked me out of the device.
Can anyone tell what can I do to get rid of the app?
Are these Device Admin app supposed to persist like this? Or am I doing something wrong?
Do I need to choose a different wipe mode (I chose the normal one, which wipes /data/, /cache etc). I did not try to wipe /cache separately, as the first wipe does that by itself. Neither did I wipe the dalvik cache, as I thought they are not relevant here. I don't see any relevant files in the sdcard either, though how the app reappears in the nandroid restore before it was installed is a mystery.
Should I mount more partitions before wiping, like the data/cache etc.
Since the wipes don't seem to make it go away, I am not even sure flashing a different ROM would get rid of this app either, however I can try that (since I was planning to anyway, before this mishap). If that doesn't work either, I might just have the most unusual case of bricking ever.
The XDA forum does not seem to be much info about device-admin apps and my search-fu is not good enough today to find anything directly relevant about the other stuff.
PS. btw the app actually modifies the lockscreen. So I don't actually see the files it has with the pre-app restore, however the lockscreen still comes up, perhaps because of some remanant of the app or because of a setting it left in there somewhere.
Click to expand...
Click to collapse
Do a CWM wipe, and turn off the phone when done by selecting "Power Off"
Now enter download mode, and ODIN flash a stock ROM.
Then re-root with CF-Root and install custom ROM if desired.
pulser_g2 said:
Do a CWM wipe, and turn off the phone when done by selecting "Power Off"
Now enter download mode, and ODIN flash a stock ROM.
Then re-root with CF-Root and install custom ROM if desired.
Click to expand...
Click to collapse
Thanks for the help pulser_g2. I am still concerned about the files i saw in /efs related to the lockscreen (see my second post). Would the stock ROM overwrite settings/configuration inside /efs (I guess since the IMEI etc are all in there, that might not be the case)?
Got through finally.
pulser_g2 said:
Do a CWM wipe, and turn off the phone when done by selecting "Power Off"
Now enter download mode, and ODIN flash a stock ROM.
Then re-root with CF-Root and install custom ROM if desired.
Click to expand...
Click to collapse
OK this worked.
However after I Odin flashed the stock rom and rebooted, I got this
1. First got a different kind of lockscreen.
2. I entered the wrong password five times (after trying the Device Admin alternate password, my Google password, a new 2-step auth password from google) .
3. it said something about wiping sd card. I couldn't catch it (I should probably have videoed this using my point and shoot camera, but this did not strike me then as it was 2am).
4. I was hoping that the stock ROM will boot, cause it stayed on the Samsung logo for too long. (I had already ordered my USB Jig on ebay anyway, but it could have taken time because of my being far off from the seller.). Finally I got the Android Welcome screen and I let out my breath.
In any case, things seem to ok right now. I feel a slight slowness in the rooted stock ROM from my earlier rooted stock ROM, but I am gonna flash a custom ROM later anyway. Thanks a lot for your help pulser.
Hello, I always find the people on this corner of xda very helpful. As usual, I think I know what I'm doing, but I'd like to check that I am proceeding in the right direction.
I've been using Mik's Cyanogen ROMs on my Optimus One. That's going well. But I need to SIM unlock my phone and I need to go back to a stock ROM to input the codes (please let me know if this is incorrect).
Before installing Mik's ROM, I performed a Nand backup. I have boot, cache, data, recovery and system img files. I think I can flash these through recovery and I should be back to stock.
Do I lose my apps and settings by doing this? Do I need to clear any caches?
What about returning to Cyanogen after I unlock my phone... Do I have to root my phone again or will I still be able to flash using recovery?
Using Clockwork, I just backed up my current ROM. I assume I will be able to restore from this later.
Is there anything else I should be aware of?
Thanks for answering my questions / clearing up my confusion.
Hello, I always find the people on this corner of xda very helpful. As usual, I think I know what I'm doing, but I'd like to check that I am proceeding in the right direction.
I've been using Mik's Cyanogen ROMs on my Optimus One. That's going well. But I need to SIM unlock my phone and I need to go back to a stock ROM to input the codes (please let me know if this is incorrect).
this is correct
Before installing Mik's ROM, I performed a Nand backup. I have boot, cache, data, recovery and system img files. I think I can flash these through recovery and I should be back to stock.
Do I lose my apps and settings by doing this? Do I need to clear any caches?
to revert back to stock, you must wipe data/factory reset, cache, and dalvik cache. you will lose your settings. as for your apps, you can back them up with titanium backup and restore them after you have restored your backup.
What about returning to Cyanogen after I unlock my phone... Do I have to root my phone again or will I still be able to flash using recovery?
when you restore your backup of the stock rom, you will still have root. i dont think unlocking your phone will cause you to lose root. your root access and custom recovery will still be intact
Using Clockwork, I just backed up my current ROM. I assume I will be able to restore from this later.
yes this is true
Is there anything else I should be aware of?
just to be on the safe side, please list the steps you are going to follow
Thanks for answering my questions / clearing up my confusion.
Thanks for the quick answer...
I on my sd card, I have a /clockwork directory with two subdirs. One is my original backup that I made before first installing Cyanogen. The other is the one I just made. Both contain boot, cache, data, recovery and system img files. The difference is that with my new backup the image files have an extra yaffs2 suffix: cache.img (stock) but cache.yaffs2.img (Cyanogen). Any problem here?
1. boot into recovery
2. restore stock from my sdcard using nandroid and wipe caches as you indicated
3. reboot, enter unlock code
4. reboot into recovery
5. restore current ROM from my sdcard using nandroid and again wipe the same caches
6. reinstall / restore apps (I'm not using Titanium, instead I backed up the list of installed apps)
Will I need to find and reinstall the GoogleApps (Market, etc) or will they come with the backup of my current ROM?
Pretty simple really. This make sense?
Thanks for the quick answer...
I on my sd card, I have a /clockwork directory with two subdirs. One is my original backup that I made before first installing Cyanogen. The other is the one I just made. Both contain boot, cache, data, recovery and system img files. The difference is that with my new backup the image files have an extra yaffs2 suffix: cache.img (stock) but cache.yaffs2.img (Cyanogen). Any problem here?
there might be a problem. what clockworkmod version did you use to make the backup of the stock rom? if i remember correctly, using cwm 3.x.x.x backs up a certain way (and also does not have the yaffs2 suffix) and using cwm 5.x.x.x backs up a different way (with the yaffs2 suffix) so backups may not be "inter"compatible (more info on that here). however, you can just flash back cwm 3.x.x.x right now (you can do it using rom manager), restore your stock rom backup, do the following steps, flash back cwm 5.x.x.x, then restore your backup
1. boot into recovery
2. restore stock from my sdcard using nandroid and wipe caches as you indicated (i recommend wipe first then restore)
3. reboot, enter unlock code
4. reboot into recovery
5. restore current ROM from my sdcard using nandroid and again wipe the same caches
(same here again, wipe first then restore)
6. reinstall / restore apps (I'm not using Titanium, instead I backed up the list of installed apps)
Will I need to find and reinstall the GoogleApps (Market, etc) or will they come with the backup of my current ROM?
i think you will have to flash gapps again
Pretty simple really. This make sense?
looks good (how sure am i? id say 80-90%. it definitely makes sense, but i have never done this before)
Good good. It's getting late so I'll tackle this tomorrow. Thanks for the detailed help... I'm glad I asked before going at it.
sweetnsour said:
looks good (how sure am i? id say 80-90%. it definitely makes sense, but i have never done this before)
Click to expand...
Click to collapse
I followed your instructions (I downgraded Clockwork before starting) and the 10-20% chance of you being wrong came true... but in a good way
Restoring from the backup brings everything back: apps, settings, contacts, SMSs etc. So it was actually even easier than you suggested since I didn't have to use my backups at all.
Thanks again for the tips!
bosth said:
I followed your instructions (I downgraded Clockwork before starting) and the 10-20% chance of you being wrong came true... but in a good way
Restoring from the backup brings everything back: apps, settings, contacts, SMSs etc. So it was actually even easier than you suggested since I didn't have to use my backups at all.
Thanks again for the tips!
Click to expand...
Click to collapse
glad it worked out for you i am assuming your phone is now unlocked right?
sweetnsour said:
glad it worked out for you i am assuming your phone is now unlocked right?
Click to expand...
Click to collapse
Yes... when I was back in stock I could access the unlock menu by entering 2945*#500# on my keypad. The SIM unlock code that I have worked fine. I haven't actually tested with another SIM card but the phone claimed to have been unlocked, so I should be good to go.
recovery just says something is wrong, look at log?
I tried a few versions (of the backup sets), same error.
What am I doing wrong? How do I fix it? :crying:
Log from recovery run...
Starting recovery on Thu Aug 16 21:58:52 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
fuzzynco said:
recovery just says something is wrong, look at log?
Click to expand...
Click to collapse
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
I kind of follow... RA is an image backup
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
fuzzynco said:
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
Click to expand...
Click to collapse
In reply to the bolded part: Basically, yes. AR's nandroid places the backups in a folder with your phone's serial as the folder name. Attempting to restore any backup from a folder with any other name will fail to prevent the issues I mentioned above.
I do not and have not ever used Titanium Backup, so in regards to that, I can't be of any help.
If you have a linux machine, you can mount the data.img from any of your backups and then copy all the files from /data/app and data/data to your phone. This will restore most of your apps, and app data/settings. There will still be a few things you'll have to redo from scratch, and this may not work 100% for every app on your phone, but at least this way you don't have to redownload every single app and manually redo all your settings...
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
fuzzynco said:
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
Click to expand...
Click to collapse
not sure...
I couldn't get ViperROM 1.0.3 to not crash (com.android.phone kept crashing).
Trying a couple of others that are prerooted and deboated. So far the ICS &
Sense 3.6 looks fine. Still have the 'social network' stuff to freeze though,
Could I do something like make a zip (from adb shell) of the user apps
/data/app & /data/data directories (to preserve the unix permissions).
and leave that on fat32 sd card? Then merge that into the zip for the
rom to be installed so the installer will reload them?
Would I need to add lines to the installer script to have it load /data (with
the subdirs ../app and ../data)?
hmms maybe better to make a seperate zip to preinstall my saved
/data subdirs? Can I copy the ROMs installer binary and build
a installer script to mount /data, then install the /data directory,
umount /data?
a.mcdear said:
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
Click to expand...
Click to collapse
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
This app might work. I use it and it works great but I'm not sure if it restores data.
synisterwolf said:
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
Click to expand...
Click to collapse
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
a.mcdear said:
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
Click to expand...
Click to collapse
Good to know. Thanks
In my case, the backup is from a device that i bricked totally. couldnt get into download mode so im thinking they will just use it as parts
Sent from my iPhone...
Hi guys,
I just installed the Cyanogenmod 11 (Kit Kat) in my YP-G1 (US) and now the home button doesn't work. I have read that this problem could be solved with a "wipe data". Is that true?
The installation was made from the stock rom (rooted), then TerraSilent, then the preflash and finally the cm-11.zip (and obviously the gapps).
Thank you so much!
SourCinnamon said:
Hi guys,
I just installed the Cyanogenmod 11 (Kit Kat) in my YP-G1 (US) and now the home button doesn't work. I have read that this problem could be solved with a "wipe data". Is that true?
The installation was made from the stock rom (rooted), then TerraSilent, then the preflash and finally the cm-11.zip (and obviously the gapps).
Thank you so much!
Click to expand...
Click to collapse
you are most likely missing parts of your efs. as the install instructions said, make sure you have a backup so you can restore it. just put the needed files in your efs folder and you should be set
goldflame09 said:
you are most likely missing parts of your efs. as the install instructions said, make sure you have a backup so you can restore it. just put the needed files in your efs folder and you should be set
Click to expand...
Click to collapse
I did not have this issue on CM 10.2, so flashing to CM 11 caused my EFS to disappear? At the moment, I am back at stock and trying to restore my EFS with zaclimon's dummy EFS, but I don't seem to be making too much progress, as I still am missing my lockscreen and power options.
kusanou said:
I did not have this issue on CM 10.2, so flashing to CM 11 caused my EFS to disappear? At the moment, I am back at stock and trying to restore my EFS with zaclimon's dummy EFS, but I don't seem to be making too much progress, as I still am missing my lockscreen and power options.
Click to expand...
Click to collapse
I doubt that your efs got erased with the flash of cm11, have you checked it to see if everything was in order? If so are you able to restore your efs from the backup made into /sdcard/backup/efs?
zaclimon said:
I doubt that your efs got erased with the flash of cm11, have you checked it to see if everything was in order? If so are you able to restore your efs from the backup made into /sdcard/backup/efs?
Click to expand...
Click to collapse
I actually was unable to find any backups by the time I was able to access data again. Admittedly, I had wiped data in order to get everything up and running onto kit Kat, and even after that, I was not able to find a backup, which led me to resort to the dummy efs.
Wiping system after replacing the EFS with the dummy, and flashing factoryfs worked wonders. I am now back up and running, home button works fine, however, i still cannot seem to charge my device on CM10.2, something that I forgot to check while I was on CM11, so I will check that out now.
^ Same problem, can you help me with replacing using the dummy EFS? I'm assuming you follow Zaclimon's recovery method (using Heimdall because mine is US) but I don't know how to incorporate the EFS dummy file in there. I've reformatted to stock before but can't figure out what to do with the EFS.
I have no EFS backup though I did notice there were a couple files in a folder called system/firmware/efs
Although I fixed the EFS issue, my battery doesn't seem to want to charge. When it is plugged in, the battery indicator in the status bar shows charging, but battery stats in settings says it is not charging.
For the dummy EFS, just edit the files that Zaclimon says to edit in his post. Check your MAC address in phone information in settings, and copy that into your bt.txt. The buyer_code.dat can be opened up in wordpad, and I changed it to XAA. Lastly, serial.info should be your serial number, which you can find in the battery compartment on a sticker. After all of that is done, copy everything in the dummy efs to your efs folder on your device, wipe system, and reboot. That's all I have done to get it working. Once everything is working just fine, save that edited dummy efs somewhere, in my case, I have it saved in a Google drive folder, as the reason why I lost my EFS in the first place was because my computer was wiped along with all of my backups.
I've gotten and changed the three files but now can't find how to paste the EFS folder over the one in the system. I can't do it with file manager and permission is denied when I try doing it in ES File Explorer (even though it's granted root acces).
Also, there are two EFS folders on the system, on in /efs and one which is /sys/firmware/efs.....not sure which one to copy over.
Sportfreunde said:
I've gotten and changed the three files but now can't find how to paste the EFS folder over the one in the system. I can't do it with file manager and permission is denied when I try doing it in ES File Explorer (even though it's granted root acces).
Also, there are two EFS folders on the system, on in /efs and one which is /sys/firmware/efs.....not sure which one to copy over.
Click to expand...
Click to collapse
Do you have supersu installed from the play store? I had a similar issue once before, just install super su and then reinstall es file explorer, then grant access through super su. Also, just copy over to /efs, make sure you transfer everything from the dummy efs, including the modified files.
I have re-rooted by re-flashing CM11 but the problem I'm having now is that ES File explorer says no space available on /device when I try and copy/paste the EFS folder there over the old one. The other file managers like Astro don't seem to work either when doing it.
Question...after you copy/paste the backup folder in /system, do you close and then format /system or wipe data/factory reset?
Ok, this is a very strange device. After copying/pasting another backup up efs withotu doing any factory or system reset stuff and just restarting....home button is working.
What I'm curious about is why some people can install CM11 without this issue and others have to restore the efs....there must be a way to install CM11 without having to worry about efs problems.
Home Button Not Working.
May I get instructions on how to fix the home button issue on the cm11? I am on Carbon. :laugh:
Found a partial fix
Home button fix (without messing with /efs) worked for my wifes phone.
Still, quick settings doesn't work (can't switch to panel by pressing button from drawer)
Tested, incoming calls/texts work fine.
Run terminal
su
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
“update global set value=1 where name=’device_provisioned’;”
Reboot your tablet/phone
You might want to "select * from global where name=’device_provisioned’;" before the update query, to be certain what you're changing from in case you need to change it back.
Hi. Recently I stuffed my ZTE Blade A452 with MIUI ROM found on here: hxxp://forum.android.com.pl/topic/319435-a452miui-v8-miui-global-8020. I also installed TWRP . I've been using it for a while and unfortunately it didn't meet my expectations. It is barely usable, phone crashes a few times a day, apps aren't kept in background.
I decided to come back to my stock ROM. I don't have, however, any back up of it. There are some sdcard packages on ZTE's support page, however when I tried to install it with TWRP, it displays that packages (all of them) are for device id P635F33, while my device is P635E40. And I found nothing for my dev id.
Is there a way to force installing one of those packages in my phone? Editing version.txt inside update.zip did nothing.
Maybe one of you guys have a matching package?
Also my sister's got the same model, Blade A452, bought at the same service provider. Maybe there is a way to extract a ROM from her phone and put it into mine? (Her device must be left quite untouched).
damiandbcz said:
Hi. Recently I stuffed my ZTE Blade A452 with MIUI ROM found on here: hxxp://forum.android.com.pl/topic/319435-a452miui-v8-miui-global-8020. I also installed TWRP . I've been using it for a while and unfortunately it didn't meet my expectations. It is barely usable, phone crashes a few times a day, apps aren't kept in background.
I decided to come back to my stock ROM. I don't have, however, any back up of it. There are some sdcard packages on ZTE's support page, however when I tried to install it with TWRP, it displays that packages (all of them) are for device id P635F33, while my device is P635E40. And I found nothing for my dev id.
Is there a way to force installing one of those packages in my phone? Editing version.txt inside update.zip did nothing.
Maybe one of you guys have a matching package?
Also my sister's got the same model, Blade A452, bought at the same service provider. Maybe there is a way to extract a ROM from her phone and put it into mine? (Her device must be left quite untouched).
Click to expand...
Click to collapse
You Have a Same Phone Available .That is Great. You can give her Sleep Drug Sneak Into Her Room.Get the Phone From Under The pillow.And Now You can Unlock The bootloader flash TWRP Make a Backup and Then Flash Stock Recovery.Then Put The Phone Back Under The Pillow.The Process Will only Take about 30Mins.
5Min to unlock Bootloader
2.5Min to flash TWRP.
2.5Min to install stock Recovery
And 20 min to move the back Up
Or
You can Slice her Throat and Get the phone.Seriously Save 30Min of time.
Or
You can Backup Using a Desktop Application and Restore on your Phone.
Sent from my Nexus 6P using Tapatalk
Atifbaig786 said:
You can Unlock The bootloader flash TWRP Make a Backup and Then Flash Stock Recovery
Or
You can Backup Using a Desktop Application and Restore on your Phone.
Click to expand...
Click to collapse
Yeah, TWRP on her phone isn't an option, as the whole system is quite buggy and she's gonna probably use the restore option. I'm gonna try with some desktop apps and give an answer in 1-2 hours. Thank you.
Sorry it took so long to answer.
I couldn't make a nandroid backup any desktop app (MTK Droid Tools can't create scatter file, couldn't find any other app).
As I said, TWRP was not an option. But I managed to do the nandroid backup from phone-level anyways.
First I rooted the source device with KingRoot, installed on it BusyBox and made a custom TWRP-style backup on SDcard with Online Nandroid Backup *ROOT. Default settings are fine, even though it couldn't recognize my phone model.
Then I moved SD into target device and performed a backup with TWRP (just to create my device directory). Then I moved the source-phone backup into the new-created directory and performed Restore.
And Voila! On my phone there was a 1:1 copy of the system. It wiped out TWRP so I could perform a system Restore and get a factory-new soft.
Thank You. I didn't even realize it was possible to restore A-Backup on B-Device. Even though my sister's phone was a P635F33 (I didn't know it earlier) and mine was P635E40, it worked well.
damiandbcz said:
Sorry it took so long to answer.
I couldn't make a nandroid backup any desktop app (MTK Droid Tools can't create scatter file, couldn't find any other app).
As I said, TWRP was not an option. But I managed to do the nandroid backup from phone-level anyways.
First I rooted the source device with KingRoot, installed on it BusyBox and made a custom TWRP-style backup on SDcard with Online Nandroid Backup *ROOT. Default settings are fine, even though it couldn't recognize my phone model.
Then I moved SD into target device and performed a backup with TWRP (just to create my device directory). Then I moved the source-phone backup into the new-created directory and performed Restore.
And Voila! On my phone there was a 1:1 copy of the system. It wiped out TWRP so I could perform a system Restore and get a factory-new soft.
Thank You. I didn't even realize it was possible to restore A-Backup on B-Device. Even though my sister's phone was a P635F33 (I didn't know it earlier) and mine was P635E40, it worked well.
Click to expand...
Click to collapse
It Did Work Right.I am Happy To Be of Your Assistance.
Sent from my Nexus 6P using Tapatalk