I created this thread just to help anyone with the same problem I had when restoring a TWRP backup on a ZTE Blade L3. The SIM Card was not detected at all!
The complete situation: I made a backup of a stock rom (4.4.2) with my stuff using TWRP (2.8.7.0) and when I restored it, the SIM card was not detected at all. In MTK Engineering Mode/CDS Information/ Phone x (or whatever number yours is) everthing was at null or unkown.
AND I FOUND A WAY TO SOLVE THIS!
Flash a ROM that detects the SIM card and enter the IMEI numbers. Then, go to TWRP, DON'T FORMAT ANYTHING and then restore the backup selecting the options to restore that you want (for example boot; nvram; system;... those ones). In my case, I restored all of them and I got it to work! I hope this helps! This because the phone memory needs to be installed and with android 4.4.2 kitkat the phone storage is not in the backup, only the system storage. I hope this helps the KitKat users and others (because I've never tested this in other versions)!
Cheers.
Related
I have spice mi 300 which is a z71 variant as much as I know..I installed the cyanogen 6.1 stable through the rom manager..during the steps I marked both backup current rom and wipe cache..but after the installation.I went into recovery mode to make a partition on my memory card..and the process formatted my card data..now I m not able to go to stock eclair mode because all the backups and data on my SD card were wiped.I tried the software updater tool by spice but now it does not detect my phone as it has turned to z71...I need to go back to stock because of having booting issues with cyanogen..plz if anyone could help me...sorry for such a long description as I could not express the problem properly with short explanation.....
I shattered the screen on my Nexus 5, and G was kind enough to send a replacement (refurbished). Since I have TWRP Nandroid backups, I thought it would be an easy matter to unlock/root/TWRP the new replacement phone, copy over the backup files, then restore. However, TWRP does not seem to be working - I get a bootloop, with an android mascot with a red triangle and the words "no command" when I select "Recovery".
My original N5: unlocked, rooted, TWRP, Android 4.4.4
Replacement N5:
- originally with Android 4.4.0
- unlocked, rooted and TWRP installed with Nexus Root Toolkit (NRT)
- system was then upgraded to 4.4.2, 4.4.3, 4.4.4
- went into fastboot, tried to select Recovery....and nothing.
Is this an issue with TWRP? Should I try flashing a different version?
Is this an issue with the process? Should I use NRT to "Return to Stock", THEN let the system update itself to 4.4.4, THEN try unlock/root/TWRP and recovery?
Is this an issue with the root process? Should I use CF Auto Root and try to re-root, re-install SuperSU, etc. on the current system?
TIA
Ed
That's stock recovery. Do yourself a favour and flash recovery properly without using a toolkit.
Thank you - that was absolutely correct. Apparently NRT either didn't install TWRP, or didn't flash an error message saying TWRP install failed (or I missed it).
I downloaded a TWRP flash image, and after some tweaking with drivers, managed to flash it just fine.
I then copied over my original N5 TWRP backup, and restored it. Aside from some minor data location problems (e.g., Evernote detected new SD Card, re-sync'd all notes), it worked fine and the new phone is in the exact same state/configuration as the original phone.
Now to go track down the "TWRP restore to a different device" threads.
Thanks!
The rule really is never restore EFS from another device.
Old device, backup system, boot and data
New device, make a small backup to generate the serial number folder. Then copy the backup from the old device.
After installation TWRP 3.0.2-1 (2016/10/08) I erased everything and probably I changed something in the partition, I erased system
the phone stops logo LENOVO and that's it.I can run TWRP but I do not have to upload the rom memory because the phone does not have a card reader
the phone also probably not charging. before was uploaded lollipop 5.1.1. What to do? Please help. Thanks.
2.47.709.1. , I have the right mid cid, even the release keys match (thanks to Ziand) twrp backup. Twrp asks me what partition to flash? But no way of selecting it. Can you restore off temporary twrp. I've tried with a 32gb card as I had problems twrp recognising my 128gb, won't mount. Hope one of you can help
New to the A/B slot root scene, apologies. I also searched but couldn't find an answer for something matching this exact specificity . I know its fixable but I cant figure out what would be best to do.
I am (or was) running TWRP/Magisk on 10.3.4 Stock OOS. broke the OS boot and it will only goes right into fastboot, no TWRP anymore, doesn't even show the warning from OP when booting a rooted OP device.
Weighing my restore options, I changed the active slot with the fastboot command and that slot was able to boot into TWRP just fine, however, the mounting folder that's usually emulated/o (SDcard) was just a bunch of folders with random text and capitalization.
I have a TWRP backup (around 8GB) . Can i just change the active slot back to the non active one and restore to the other? I am concerned i will break it worse or restore it to the wrong slot somehow. If i restored it to both slots, would that be ok?
edit: I connected my TWRP backup and wasn't able to force the restore to another slot. The backup includes Boot, System, Data (excluding storage) and EFS. I could "swipe to restore" at any moment but unsure how that would effect everything seeing as the backup was done on Slot A and now I am on slot B.
I read you should flash the 10.3.4 full while staying on the same slot but was having issues getting it to upload to the phone (no drive mounts on my computer OS on the default slot, only can do so when i change slots) I have a very recent titanium backup i can restore once i am back in, either way.
I am just not 100% exactly how to get myself back up and running.
Lastly, i only started rooted again after a 10-15 year break because I got real sick of the background data the official OOS build was sending. I was interested in converting to LineageOS with gapps form Micro (if it can pass safetynet) but Open to any ROM that could assist in stopping the official background activity. I would love a ROM that can pass safetynet, help with the battery life on my aging OP6 and hopefully keep rocking on Android 10.
Thank you to everyone or anyone that reads this and assists. I know it must be annoying to read what may just be the same question over and over but this exact issue was hard to find another experiencing with the latest OOS.
Take care.
I ended up trying to restore the TWRP backup to the different slot, this put both slots in a fastbootloop. i then flashed all partitions with a fastboot image of 10.3.4 and this fix my phone and got it back up in running. i rooted again, flashed twrp and then tried to restore the TWRP backup again and it completed successfully, however, both slots were back to bootlooping.
i will just wipe all again, root/magisk and then install titanium to restore my full backup of that. Im sure ill be coming to a new issue trying that too, but who knows.
I fixed it the way i wanted (off the backup i made with TWRP) by restoring my backup (without EFS this time, per the tips on the devs website, rebooted into fastboot, flashed the OOS 10.3.4 fastboot image (WITHOUT -w to keep my user files), let it run. when it rebooted i had everything back from the TWRP backup!.
all i did then was boot the TWRP image, flash its zip, then flashed magisk again and rebooted.
All is well! (until Slot B issues rear their ugly head) I really hope to flash both and move to a custom ROM but saying encrypted is more important to me than I thought it was.
I hope anyone who finds themselves in the same stupid situation is helped by this come day.
PS. titanium backup is really not a system restore feature like I thought it would be when you are encrypted. TWRP was my only viable solution and so happy this worked. Ill be running that weekly, for sure.