Develop Bugs

CWM Nandroid Backup Fails

Hi everyone,
I recently upgraded my cwm from 6.0.1.2 non touch to 6.0.2.3 touch with Odin and when doing a backup it takes a really long time and eventually fails about halfway through backing up /data. I thought maybe the recovery got corrupt or something so I used rom manager to upgrade to 6.0.3.1 non touch and tried again. This time it took longer to backup /system and while backing up data the phone rebooted. I've been running CM10.1 nightlies for quite some time now and kt kernel with no issues, and I always backup before flashing but I need to fix this before i flash anymore nightlies. Anyone else have this issue before? I've been wanting to clean wipe/install my phone for a while now but I just don't have the time right now.
My phone is a d2can on Bell. I know that's relatively irrelevant information but doesn't hurt to mention.
Also I installed the same 6.0.2.3 touch on a GS3 that I just got for my girlfriend and it backs up fine.

Also apparently in attempting these backups it somehow messed up some of my settings. I had a sign in error for gmail which went away as soon as I hit sync now in the Google account, although I had to sign back in to Facebook. It also changed a bunch of my sound settings... Imagine my surprise as I get a Whatsapp message and an Opeth song starts blaring (and also doesn't stop upon checking the message...) lol.
I back up my apps and settings with Titanium Backup so I can easily restore everything when I have a chance to do a clean wipe and install, but how do I fully wipe/reinstall the recovery to fix this backup issue? Maybe I just have to hit the factory reset button in the recovery?

Lessaj said:
Also apparently in attempting these backups it somehow messed up some of my settings. I had a sign in error for gmail which went away as soon as I hit sync now in the Google account, although I had to sign back in to Facebook. It also changed a bunch of my sound settings... Imagine my surprise as I get a Whatsapp message and an Opeth song starts blaring (and also doesn't stop upon checking the message...) lol.
I back up my apps and settings with Titanium Backup so I can easily restore everything when I have a chance to do a clean wipe and install, but how do I fully wipe/reinstall the recovery to fix this backup issue? Maybe I just have to hit the factory reset button in the recovery?
Click to expand...
Click to collapse
I would download Goo Manager and flash TWRP, forget CWM. If you hit factory reset then you are going to have to go through the clean install process. If I were you I'd flash TWRP and then clean install whatever your into. It'll take maybe 30 minutes to get the rom setup the way you want it and you'll have the piece of mint that everything was cleanly wiped and you have a fresh start.

I guess I can try TWRP. I don't really get why everyone rags on CWM, it works just fine. I was using 6.0.1.2 for about 7 months without a hitch, this is the first problem.
If I did a clean wipe I'd still backup my pictures and my apps from TiBu and restore everything after wiping, it would just take a while. I don't have an external SD so it's all on the internal. I might have some time tonight to try it out.

Lessaj said:
I guess I can try TWRP. I don't really get why everyone rags on CWM, it works just fine. I was using 6.0.1.2 for about 7 months without a hitch, this is the first problem.
If I did a clean wipe I'd still backup my pictures and my apps from TiBu and restore everything after wiping, it would just take a while. I don't have an external SD so it's all on the internal. I might have some time tonight to try it out.
Click to expand...
Click to collapse
I would copy your pictures (or any other irreplaceable files) to a computer for safe keeping just in case it hits the fan. Apps are whatever, but you can't retake pictures so I'd back them up somehow; computer, dropbox, etc.

Same Issues on a SG3
I also recently upgraded and have been having the same issues. It doesn't seem to matter whether I enter recovery through or use Rom Manager to enter into in recovery. Each time the back up fails. I had just switch back after having TWRP issues where it back up would not fail but when they were to be use in recovery I would get a message before restarting stating I didn't actually back up the OS. ( I realize it might not be reliant info but I've learn a little to much is better than not at all)
I've noticed it will fail and restart only when I try to back up to my SD card. Yesterday it was giving me trouble by mounting and unmounting repeatedly. I thought I had fixed all the problems after I did a diskcheck and had my computer scan and fix all found errors.
If anyone can link me to a previous version of CWM or help with this back up issue you'll have the OP's and my appreciation.
Thanks in advance.
---------- Post added at 03:36 PM ---------- Previous post was at 03:00 PM ----------
Are you backing up to an SD card or the phone it's self?
Lessaj said:
Hi everyone,
I recently upgraded my cwm from 6.0.1.2 non touch to 6.0.2.3 touch with Odin and when doing a backup it takes a really long time and eventually fails about halfway through backing up /data. I thought maybe the recovery got corrupt or something so I used rom manager to upgrade to 6.0.3.1 non touch and tried again. This time it took longer to backup /system and while backing up data the phone rebooted. I've been running CM10.1 nightlies for quite some time now and kt kernel with no issues, and I always backup before flashing but I need to fix this before i flash anymore nightlies. Anyone else have this issue before? I've been wanting to clean wipe/install my phone for a while now but I just don't have the time right now.
My phone is a d2can on Bell. I know that's relatively irrelevant information but doesn't hurt to mention.
Also I installed the same 6.0.2.3 touch on a GS3 that I just got for my girlfriend and it backs up fine.
Click to expand...
Click to collapse

Icon000 said:
Are you backing up to an SD card or the phone it's self?
Click to expand...
Click to collapse
I'm backing up to the phone itself, I do not have an SD card.

Lessaj said:
I'm backing up to the phone itself, I do not have an SD card.
Click to expand...
Click to collapse
So was your problem fixed by switching to TWRP?

I know when I had tried using TWRP, the issue I was having after back ups, was it would ask me if I was sure I wanted to leave since it said I didn;t install a OS.
Does that help you to find a solution?
post-mortem said:
So was your problem fixed by switching to TWRP?
Click to expand...
Click to collapse

post-mortem said:
So was your problem fixed by switching to TWRP?
Click to expand...
Click to collapse
Yes.

HELP! Factory reset while rebooting into recovery!

Hey guys,
I really need help. I was about to update my brother op3 from 3.2.4 to 3.2.8. When I was done I wanted to continue to flash to 4.0 but when I use the advanced reboot to boot into recovery it suddenly said "factory reset"!!!! Everything is gone even from the storage! I cant even backup from the backup file from twrp because it is gone! Can anyone please help me out? There are software to recovery this but I have to pay for all of them and they are not cheap!
Thank you in advance!

After a factory reset, even paid recovery tools aren't able to fully restore your data to their original state. At best, you'll get back a majority of the individual files you had on your phone prior to the wipe. The more you use the phone after wiping it, the more the old data is overwritten. At this point, I would just make the best out of this unfortunate event and clean flash whatever OS you were trying to update to. At least the phone will be de-cluttered at this point. You may even notice that the phone feels a little faster afterwards, and may even improve your battery life slightly.
If you had something really important on your phone that wasn't backed up, data recovery tools may be able to restore it, but I wouldn't hold my breath. Additionally, TWRP backups do not backup media files such as music, photos, personal documents, etc. Even if you were able to find a nandroid backup, you would only get back your OS, apps, and app data. Most of this can be restored by just downloading everything again.
In the future, I would recommend saving nandroid backups directly to a USB flash drive through USB OTG. Music and photos can also be backed up to the cloud through various free or paid services (Google Photos for example).

shujin51 said:
Hey guys,
I really need help. I was about to update my brother op3 from 3.2.4 to 3.2.8. When I was done I wanted to continue to flash to 4.0 but when I use the advanced reboot to boot into recovery it suddenly said "factory reset"!!!! Everything is gone even from the storage! I cant even backup from the backup file from twrp because it is gone! Can anyone please help me out? There are software to recovery this but I have to pay for all of them and they are not cheap!
Thank you in advance!
Click to expand...
Click to collapse
Chance to recover your files are verry slim. Use the TWRP provided by Bluspark, it's on his main thread, stock twrp seems to have many issues.

Missing partitions

To cut to the chase…
My G5 (XT1671 32GB) has no IMEI. The one smart(?) thing I did before starting to screw around was make a backup with TWRP - 2 backups actually, one stock, the other AtomicOS. When I try to restore the backup I get an "unable to locate partition by backup name" message for these partitions: efs1, efs2, logo, oem. I gather the efs partitons are the ones that correspond to IMEI and other modem related things.
Is there any way to bring these partitions back? I've reinstalled the stock ROM (a few times now) and that doesn't seem to restore them (however when I try restoring I always get an error message on this line "fastboot flash partition gpt.bin"
Is restoring even going to fix the IMEI? From what I've read those backups are supposed to be an exact clone of the device - sort of like using Macrium to make an image of your PC (btw the backups include everything, whether it was needed or not ~6-7GB in size)
Cheers

Once you've flashed an oreo rom, imei will always be 0 when reverting to stock.
You could try this though: https://www.youtube.com/watch?v=XmKg84IXEbo

Going back to stock isn't the issue with the IMEI, it's whether you can turn off auto-update fast enough no to let an OTA update through (at least that's what screwed me)
I did run through the video you linked before hand. Kinda worked. Got 3G back, but when I tried the steps to restore 4G I just lost my IMEI again.
Still doesn't answer why I kept getting the missing partition message in TWRP. I do have full backups so you'd think restoring my efs would be the answer.
Turns out that was the answer… I have no idea what exactly happened but after trying the steps in that video again I decided to restore my AtomicOS backup (prefer it to Pixel Experience) for WIFI usage if nothing else. I got the same missing partitions message and this time somewhere during the restore process TWRP crashed/rebooted (could only boot as far as the bootloader menu). When I booted back into recovery to try and restore again I finally had all the options to restore my efs/logo/etc.. So I restored everything available (minus "system image") and am back to a fully functional AtomicOS.
I'm thinking I could also restore my stock backup now without problem now since I made it way before I ever tried any 64bit/Oreo roms. But ATM I don't want to tempt fate. Besides probably better to wait until Moto/Lenovo officially launches their Oreo update before considering stock again

Android Q beta2 Rollback

Hi all
Does anyone know the best way to roll back from updating to AndroidQ?
I have issues (android auto, casting etc) so would like to roll back to the lastest stable release
I am having a right pain restoring to to anything at the moment
Thanks

nick w said:
Hi all
Does anyone know the best way to roll back from updating to AndroidQ?
I have issues (android auto, casting etc) so would like to roll back to the lastest stable release
I am having a right pain restoring to to anything at the moment
Thanks
Click to expand...
Click to collapse
Yeah you can either use the "flash-all.bat" file that comes in the android p stock image zip or fastboot boot twrp.img and once booted into twrp just restore a backup. But you'll need to create a folder on you sdcard called TWRP. Then put a backup in it. I've even booted twrp then flashed pixel dust. It's not as critical as it was years ago when once you went up bootloader then downgraded which would cause bricking. At least I haven't run into any issues. Just make sure you turn off any lock screens and have "USB debugging" enabled.

If you are enrolled in the beta, just opt out on the website where you opted in. You'll get an OTA, which will wipe your device, so back up first. Just did this last night. Couldn't have gone any more smoothly.

For some odd reason when I rolled back my battery refuses to charge up to 100% any one else having this issue?

You have to have your phone unlocked... Yes, you will lose everything from internal memory, but can restore all your apps and settings.
I made this path twice, on beta 1 and now on beta 2.
First, make sure you have twrp. Back up on twrp everything but you will need only the data partition. Also don't forget to backup your internal memory (different from the data partition).
After that, just flash normally the last factory image from Pie, or at least the same version that you have on your nandroid backup.
After finish the installation, install again twrp. Go into twrp and restore ONLY the data partition!!! You can also restore the boot if you like (if you had magisk installed for instance). This worked flawless with me.
I repeat, no use if you try to restore ALL partitions on twrp!! At least with me, twrp would just reboot in the middle of restoring the system partition (no idea why that happened on beta 1 and now on 2). Second, the same if you try to flash factory image without the -w (without wiping internal memory), it just reboot every time it tries to enter android.

reno218 said:
For some odd reason when I rolled back my battery refuses to charge up to 100% any one else having this issue?
Click to expand...
Click to collapse
This is a bug that was fixed in Q. You can alternatively fix it in pie by flashing a kernel that has Q patches merged in.

Bluetooth problem after flashing TWRP

Hi,
I flashed TWRP on my unlocked Redmi Note 8T with MIUI Global 12.5.5. Everything was great until I rebooted it and saw Bluetooth error which pops every time I try to turn Bluetooth on or just randomly during usage of the device. I also tried to re-flas TWRP with Orange fox but it unfortunatelly did not help. Now I have no idea what to do but there are also some other people with this problem (for example:
https://www.reddit.com/r/Xiaomi/comments/y9zsak
).
Does anybody know any solution? Thanks!
Btw Orange fox is for ginko devices, I did not find version for willow

I had the exact same problem when I tried to root my stock rom in ginkgo. I was getting a lot of "app keeps stopping" pop ups, and that also included bt. My bt was completely broken until I changed rom. Also I'm guessing this had happened when I had rooted my phone with magisk, not by flashing recovery itself. Perhaps you could try to uninstall magsik, and see it it resolves the issue for you. If that would be the case, then you would have found your problem, and maybe you can flash a custom rom to safely root your phone.

Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
So now it tried one of my ideas, which was to install Magisk (root) and uninstall it but it also did not help (I expected that)

vasik006 said:
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
Click to expand...
Click to collapse
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.

Yeah, that's true. But don't you know how to backup data from these "offline" apps? I was trying to solve this also before unpocking bootloader like a year ago but unsuccessfuly.
Also, which rom should I choose? I'm deciding between LineageOS and Pixel experience.
So I have LOS installed but I can´t install other zip files (like Google apps). Im only getting error: signature verification failed while. Im using LOS recovery so where is the problem?
Solved it!

Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.

Thanks, this might help someone else with this problem. I have already formatted my phone, installed Lineage OS and everything is ok

For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.

Jatin Verma x821 said:
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Click to expand...
Click to collapse
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly? Tks

ennev said:
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly?
Click to expand...
Click to collapse
no need to unroot. simple factory reset the device and you're done.

Jatin Verma x821 said:
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Click to expand...
Click to collapse
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.

Alpha_Geek1 said:
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Click to expand...
Click to collapse
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.

Jatin Verma x821 said:
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Click to expand...
Click to collapse
TWRP does backup personal apps and their settings. Once you restore a TWRP backup, you have everything back except media files - images, videos, documents, etc. The launcher icons, the apps, the system settings - everything is a perfect clone which you can restore on a new device (same model, of course).
I actually came across this thread searching to see if others had a problem where merely flashing TWRP caused Bluetooth to crash (and Atmos).

Use OrangeFox

is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?

I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
s3rv said:
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Click to expand...
Click to collapse
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
starkshadow said:
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
Click to expand...
Click to collapse
It looks like this guy didn't have any luck with it either. It may be divice specific

Dredead said:
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
It looks like this guy didn't have any luck with it either. It may be divice specific
Click to expand...
Click to collapse
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.

starkshadow said:
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
Click to expand...
Click to collapse
It seems to be a twrp issue. What version do you have? And what version of magisk do you have?
I have recently flashed miui 12 (android 10) after bricking the phone using qtel. I noticed the Bluetooth problem last week and didn't find a fix. I have twrp 3.6.2 and magisk 25.1. I had twrp 3.7.1 but if failed to decrypt data using pattern so I rolled back to 3.6.2. And I thought that magisk had to do with the Bluetooth problem so I rolled back to 25.1 from 26.
I still can't use the Bluetooth, and I don't have time to reset the phone, I just finished restoring everything

I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210

Olfason said:
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Click to expand...
Click to collapse
I can't afford resetting my phone right now , don't have enough time. I'll let it like that for some months.
Edit : I have miui 12.0.6 installed (android 10) and I'm not planning to upgrade since I have much better battery life (even better than every mod I tried). I wander if I flash miui rom from recovery can fix it?
Edit 2: flashing the rom from recovery didn't fix it