Related
This has been my biggest problem with my OP3 and OOS. I want to be able to safely dirty flash my rom without losing data.
Im a long time Android power user. CyanogenMod would always be a nice easy upgrade to the latest version. Dirty unicorns, albeit buggy on my Oppo Find 7, would upgrade easily.
The last time I tried an OTA update, it trashed all my data and settings. Subsequent updates have been major upgrades (updating kernels. Major changes like OOS 3.X to 4.X. etc etc), so I haven't tried doing a OTA/Dirty flash in a while. I have been cautious since the data wipe last time.
Any advice on how I can do an OTA easily and safely?
I have TWRP. I'm UNrooted and on OOS 4.1.1.
Backup everything.. Wipe system flash 4.1.1 and it should be fine, if not restore your back up. System does not contain any data nor settings.
Ok. Will it work with the 4.1.6 OTA I got? Or should I download the full room from the website
You have to download the full zip if you have TWRP installed. You can't update via ota.
I would recommend a TWRP backup and system, cache/dalvic wipe too.
Gucci! Thanks fam
ssjaken said:
Gucci! Thanks fam
Click to expand...
Click to collapse
Well, you know, I had the same issue with my wife's 3T. Was terrible (and lucky), right out of the box, try to upgrade like you want to do, and the update would fail in the middle, requiring to wipe the phone to have it boot.
Luckily, as I said, the phone was new like 5 minutes old. I don't imagine what would happen after a few months use.
What I did to make it work was to use the stock recovery to flash the full rom zip from OP servers, and that worked.
All subsequent updates went well (with a little bit of stress we all know : will it boot, won't it? and if it does not, will I keep my head?)
Haha. Of course, you must be on stock recovery to do so, but it's easy to do, just follow the official way to do it "manually".
Oh, and backup all your stuff
My mi max 3 is currently boot loader locked and I've waited the 30 days to unlock it and should be ready to do so now. However, is it still worth going through the trouble? I mean unlike some other phones, there are not a ton of custom ROMs options anyway. I'm a tinkerer and have owned many Android devices in the past including multiple Xiaomi phones and have always installed custom ROMs on them. I had to wait 30 days and use the currently factory installed global ROM and other than missing out on backups through TWRP and titanium, I haven't really wanted anything else. At this moment, my phone is loaded with apps and data that I would rather not have to reinstall. What do you guys suggest, go the custom route or stay stock? Also, any way to backup all the apps with dates without root. Mi mover only does a few apps and some of the paid options require a PC which is a pita.
Thanks
I'm happy with stock.
I did consider going to a custom ROM but figured out it may break things I'd rather not break...
I just debloated manually some of the unnecessary chinese apps...my stock was China Stable
IMO there is no reason to stay with Stock China or Global ROMs if your bootloader is unlocked. And considering you waiting the 30 days, take advantage of it.
You're right, there are not a ton of custom ROMs specifically for the MM3, however there are generic custom options, not that I've gone that path.
For me and what I think is the best and easiest option for now, is xiaomi.eu.
You're getting the latest beta builds without the bloat and Pie is running smoothly and without any problems that I've found.
Another bonus is in-between builds, it's a simple flash without losing or resetting the phone, like you have to with customs.
My custom ROM MM2 is sitting collecting dust, because this phone is awesome.
@ehudmi, Do you mind sharing how and what you debloated?
Thanks
Actually don't I actually don't have the unlock bootloader yet. The reason why I'm having a second thought about it is because of having to hard reset the phone when I unlock the bootloader. Reinstalling all the apps as well as restoring all the data would be a pain in the ass. I agree with you that this phone is awesome. I also have a custom rom mi Max 2 sitting around unused as well as a Mii mix 2.
I'm not sure I remember everything - I pretty much checked the forums on debloating Mi Max 3 and since I didn't root I used the manual method and app inspector - I removed the mi remote, mi music, mi video, mi assistant, mi notes. I don't recall if there was an email and browser apps but if there were I chucked them out. There may be have been some more.
You can probably chuck out their abroad sim app and mi cloud but double check to see you don't remove anything that might be essential. Use the mi max 3 debloat forum discussions for more apps to remove and the general xiaomi debloat discussions. Don't remove their app store.
Cool, thanks for the info!
So I've read enough posts to get this first - GLOBAL ONLY I got my phone on Amazon its a global unlocked NOTE8PRO. Any of you with something else like China or India try this method and brick your phone don't cry to me over it. After trial and error, bricking my device and paying some guy in Spain 30EUR to unbrick it (thanks brother you rock) I thought I'd share my final experience and how you can get your GLOBAL RN8P to a stable place to install the ROMS available at this time. I will include at the end my thoughts on the 2 ROMS I installed and used over the past week. Honestly if you're on a global version I'm not sure it's worth it although as I type this I kinda want to flash Pixel Experience again, I really liked it. But more on that later. I compiled this guide from sources here, if I don't give you credit I apologize in advance please just let me know.
First let's make sure we don't brick this mofo.
Hit the MEGA thread if you haven't read it then you shouldn't be flashing your phone, and do this from a clean install of MIUI-V11.0.6.0PGGMIXM and do yourself a favor and get it from Xiaomi or a reliable source, not everyone on here has good intentions. There are some "official" ROMS out there that have been played with and will break your phone.
1. Do it how you want I did this from fastboot. Dump the official MIUI global ROM in a folder, and (I'm on linux box so adjust yourself if you're sadly using Windows) I executed this command from FASTBOOT in the MIUI ROM folder with ADB and FASTBOOT installed for my system.
./flash_all.sh (I think its flash_all.bat for Windows)
This going to wipe your stuff out, have it backed up. I'm dedicated to Google and GDRIVE I don't care I get everything back when I wipe including sms and phone records etc, but to each his own.
It's going to wipe and restore to factory image on that ROM version and you're going to go throught setup again, tedious (I say that having done it 4 times this week) but none the less it is what it is. After you are up and running on that ROM version keeping in mind if you're going to flash a new ROM like PE then don't set it up all the way because you're going to do it all over again anyways move to the next step.
2. From the MEGA thread flash this and reboot. Read the thread download the files and do what Agent_fabulous (awesome guy btw) says. Reboot. Make sure you can reboot to SYSTEM and all is well, don't worry about recovery or bootloader yet.
Code:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
3. OK kids we're almost there, now you need to install TWRP and there are MANY versions floating around. Honestly the official version sucks IMHO. go to this thread and download TWRP and do exactly what it says in the thread. Assuming you're device is unlocked already and if its not then come back later follow EXACTLY steps 2 and 3. From there you will update MAGISK after the reboot and be fully rooted and pass SaftyNet checks.
You are stable and rooted. All you do next is enjoy your rooted device and or install a custom ROM. If you do install a custom ROM - READ READ READ and FOLLOW directions I hate to add to the confusuion but there are so many threads on this phone (becasue it sucks to MOD it) and it's frustrating because all of it assumes you know everything or they just don't give you all the steps and you end up bricking your phone. I have never by the way rooted or flashed a phone in my life before this one.
At this time all the custom ROMS need to be flashed after flashing the Indian Vendor image, this is in fact the only way I know and it worked for me everytime. So at this point if you're flashing a new ROM first flash the India Vendor image then flash the new from all from TWRP. But in my experience just follow what it says because Agent_fabulous and friends may crack this tomorrow and it won't be the same. What I am giving you is a VERY stable platform to start flashing ROMS from or just to be rooted and happy. As an FYI from this you can install RIRU and EdXposed if you want to do that, I wasn't impressed other than dark mode in GMail on A9 and ad-blocking in YouTube, I get the ads in YouTube but Google no dark mode in GMail on A9? WTF??
Happy rooting and ROMing.
DC.
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
Given how aggressive the battery optimizer is on stock, I doubt you'll get more juice out of it.
Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
It's fine to flash ROMs I felt PE was way faster the audio was better over Bluetooth and it was pretty stable. Battery improvement was negligible.
@dcindallas glad you had such a nice experience. have you tried flashing miui 12 on it? seems there are some beta versions for it. seems to bring a lot of eye candy, privacy and performance fixes. give it a go.
@dcindallas hi, can you please add a portion for updating miui rom through twrp (when new version available) the procedure. thanks.
I've not flashed anything but custom ROMS I had to wipe go back to A9 stock ROM due to Pixel Experience dropping wifi constantly.
Well, I appreciate all the effort going into this thread and this device. Thru all the reading I've done on this simple project with different advice, it almost seems there's too much info on it. Anyway, I'm having a dickens of a time with it, just getting it to load up TWRP! I thought I followed all the directions.. y'know... hold this button, dont hold this one, release this one, then repress that one... but I got a bootloop just from flashing TWRP. I had to re-flash the whole MIUI (an older one even) with Mi Flash, the only one I could find that had a flash-all script in it.
I'm a little gun shy, but I'd sure like to give it a go again.
I flashed twrp-3.3.1-0-begonia.img, then rebooted. Any advice why I bootlooped? Was it the TWRP version or did I mess up the button press?
Cheers
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
mkhcb said:
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
Click to expand...
Click to collapse
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
scott.hart.bti said:
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
Click to expand...
Click to collapse
I came from the OnePlus realm and owned the OPO + OP5T. My parents had the OPO and currently have the 7 Pro. I have been beyond spoiled with TWRP.
Needing a computer to flash and update + keep flash is a pain in the butt... Plus the uninstall Magisk, update, then flash method has never worked for me and 2x I lost all my data + pictures.
mkhcb said:
I came from the OnePlus realm and owned the OPO + OP5T. My parents had the OPO and currently have the 7 Pro. I have been beyond spoiled with TWRP.
Click to expand...
Click to collapse
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
scott.hart.bti said:
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
Click to expand...
Click to collapse
Well if you want to lose the inactive dev title, I 100% will support that . I know many people would appreciate it!
i'd certainly spend my money for a twrp!
I hate adb and hate having to connect my pixel (or any other phone) to a pc for install whatever i want
TWRP was a thing when phones had SD card slots. It still would be nice, however, just not as handy as it were then. ;-)
scott.hart.bti said:
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
Click to expand...
Click to collapse
I'm coming straight from S5 and can say even with Source Code available it's really hard to see functional updates.
Aroma Installer support was lost for about 5 years. Then an interested developer finally came up and fixed it but didn't want to maintain it, but still it became official ipdate for device tree not unofficial. However the next two updates after it (as far as I know there haven't been more) by an official maintainer skipped all the fixes he did (Aroma Installer support is just the most important). So TWRP for S5 is back to be bugged like for last 5 years and I don't expect it to get fixed ever again.
So no: even if source is available, you can't expect to have good TWRP support.
I'm quite shocked about the S20 development: It's a flagship phone only 2 years old but Stock based development is down to one ROM and one kernel actively maintained, Vanilla Android (based) ROM is not there only LOS based (okay this is Vanilla based in the end, but itself modified and all the ROMs start from this one) and as this one is still not bug free, all depending ROMs are not bug free.
Back in the active days of S5 you had 3-5 Stock ROMs active, AOSP, AOKP and than Cyanogen (based) ROMs available, quite a lot. And Samsung was always hated for their undocumented changes that gave developers quite the headache and reverse engineering was needed a lot. I think GSI should make development easier compared to S5 or has Custom Android development gone down at all?
scott.hart.bti said:
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
Click to expand...
Click to collapse
Huh? My Samsungs and Oneplus had TWRP, it's not rare just not on Pixel
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
But maybe by now, someone has made it for Android 12 in general and I just haven't heard about it, who knows. I used it some on my Pixel 1, but I really haven't missed it.
Edit: There are several TWRP-related threads in this section, and here's some news I shared a month after I got my Pixel 6 Pro:
[General] TWRP 3.6.0 major parts rewritten from scratch to support Google's Android 11 changes, so they are hopeful for a much quicker Android 12 release
So it took them quite a while to get Android 11 support in general.
cpufrost said:
TWRP was a thing when phones had SD card slots. It still would be nice, however, just not as handy as it were then. ;-)
Click to expand...
Click to collapse
Use a USB C to USB A dongle. Works like a charm and also works in TWRP.
TWRP is still being worked on from what I just checked, but they have no ETA when it'll be finished. There's a status page on Zulip with more info, but I'm not signing up for it.
TWRP 3.6.1 Released
TWRP 3.6.1 is out now for most currently supported devices.
twrp.me
mkhcb said:
Use a USB C to USB A dongle. Works like a charm and also works in TWRP.
Click to expand...
Click to collapse
True, I forgot about those. I even have a 128GB tiny Sandisk USB drive that is USB C native that does work so there's that.
roirraW edor ehT said:
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
But maybe by now, someone has made it for Android 12 in general and I just haven't heard about it, who knows. I used it some on my Pixel 1, but I really haven't missed it.
Edit: There are several TWRP-related threads in this section, and here's some news I shared a month after I got my Pixel 6 Pro:
[General] TWRP 3.6.0 major parts rewritten from scratch to support Google's Android 11 changes, so they are hopeful for a much quicker Android 12 release
So it took them quite a while to get Android 11 support in general.
Click to expand...
Click to collapse
yes
namely the fold 3 - however with samsung devices, encryption needs to be disabled for TWRP to work and be able to access the data partition and thus make and store nand backups of userdata etc.
Firstly it transpred that disabling encryption broke a whole range of samsung and google things such as samsung Dex mode and even downloading attachments from gmail.
Then it transpired that data backups were not being sucecssful (although system partition backups were still possible)
In the end it wasn't worth it and the Dev moved over to pixel 6 pro lol
roirraW edor ehT said:
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
Click to expand...
Click to collapse
It was only officially ported to Android 11 in November 2021, so I doubt there's any official A12 builds yet.
I think reliance on TWRP has dwindled over the past few years due to slow releases, dev's releasing ROM's that are flashable with fastboot, kernels being flashable while online, and most root mods moving towards systemless Magisk modules.
I mainly used TWRP to do an image backup of my phone before doing anything "dangerous". I really hate having to before each monthly update in the hopes something doesn't go wrong that will cause me to have to wipe my phone. With TWRP, I could do an image backup, screw something up, and be back up and running right where I was in a matter of minutes.
Am I missing something here? Is there another way to do a full image backup and restore it quickly? I have Titanium Backup but using that to backup each individual app and it's data, transfer that backup off the phone, then if I have to wipe the phone, I have to copy everything back, then do a restore of each app, will take literally hours!
What's the quickest way to do an image backup if not TWRP?
Thanks,
Dave
Dataman100 said:
Am I missing something here? Is there another way to do a full image backup and restore it quickly?
Click to expand...
Click to collapse
There has "always" (very, very long time) been a way to do image backups manually using ADB, however, it's unreliable - the only reason TWRP or other recoveries were slightly more reliable was that they could "verify" the backup and ensure that what it sees in the partition is indeed what is backed up.
With the ADB commands, you might not find out your backup isn't good until you restore it, and that's no help.
I still found TWRP backups to be hit and miss, at least six years ago when I was still using it.
Dataman100 said:
I have Titanium Backup but using that to backup each individual app and it's data, transfer that backup off the phone, then if I have to wipe the phone, I have to copy everything back, then do a restore of each app, will take literally hours!
Click to expand...
Click to collapse
I switched to Swift Backup and I don't even backup locally as most of my 512 GB of space is filled with music. I have it backup to my Google Drive directly. It's slower to restore stuff from the cloud, but at least they aren't taking up precious space, and I know wiping the phone won't cause me to lose my backups.
FYI, you can set up cloud backups in Titanium Backup as well, or tell it to do that manually. In TB's case, the cloud backups don't replace the local backups, but I have used them before just in case I have to wipe. I've been away from Titanium Backup long enough that I don't recall if TB restores could be done from the cloud, however (unlike Swift Backup, which can restore directly from the cloud). TB's method is probably closer to your manual copy the files back method, so only slightly an improvement as you can schedule the TB cloud backups to happen automatically.
roirraW edor ehT said:
There has "always" (very, very long time) been a way to do image backups manually using ADB, however, it's unreliable - the only reason TWRP or other recoveries were slightly more reliable was that they could "verify" the backup and ensure that what it sees in the partition is indeed what is backed up.
With the ADB commands, you might not find out your backup isn't good until you restore it, and that's no help.
I still found TWRP backups to be hit and miss, at least six years ago when I was still using it.
I switched to Swift Backup and I don't even backup locally as most of my 512 GB of space is filled with music. I have it backup to my Google Drive directly. It's slower to restore stuff from the cloud, but at least they aren't taking up precious space, and I know wiping the phone won't cause me to lose my backups.
FYI, you can set up cloud backups in Titanium Backup as well, or tell it to do that manually. In TB's case, the cloud backups don't replace the local backups, but I have used them before just in case I have to wipe. I've been away from Titanium Backup long enough that I don't recall if TB restores could be done from the cloud, however (unlike Swift Backup, which can restore directly from the cloud). TB's method is probably closer to your manual copy the files back method, so only slightly an improvement as you can schedule the TB cloud backups to happen automatically.
Click to expand...
Click to collapse
Thanks! Yeah, I was aware of all those options. It's still a very manually intensive and time consuming process with either Swift or TB to the cloud.
I came to the P6P from an LG V30s which had TWRP. Right before any major update, (OS, Magisk, etc). I'd do a quick full image backup to the SD card. It took about 20 mins max. Then I'd perform whatever update task, and if it boot looped, or soft bricked, I'd immediately reboot into TWRP and restore. I remember having to do that at least twice on the LG. Each time the backup restored properly and I was up and running again in 20 mins or less. There's no current backup/restore process for the Pixel that even comes close. Titanium even lets you restore individual apps/data from a TWRP backup image. You don't have to restore the entire thing. Which I'd done several times on the LG.
It's a shame. One of the reasons I chose the P6P was because I thought with it's popularity, it wouldn't take long for TWRP to be available. It may not be as valuable or necessary as it was in the past for it's flashing functions, but it certainly would be very useful, (to me anyway) for it's image backup function.
I'd definitely chip in for a TWRP bounty. For the backup alone.
Dataman100 said:
Thanks! Yeah, I was aware of all those options. It's still a very manually intensive and time consuming process with either Swift or TB to the cloud.
Click to expand...
Click to collapse
I have Swift backup to the cloud automatically every night at ~2 AM whenever the battery is at 50% or more. I never have to do anything for that manually. That way, if I'm going to do something dangerous, there's that much less I have to worry about.
I think I used to have Titanium Backup sync to the cloud nightly on a schedule also, besides having it do a scheduled new backup beforehand.
I only actually ever restore select app data - I always start with the Google Cloud restore, and then probably just a few apps that don't use Google Cloud backup, so I manually restore the data for those apps as I come across them in normal use. I never do like I used to do in Titanium Backup and do a restore all.
Dataman100 said:
I came to the P6P from an LG V30s which had TWRP. Right before any major update, (OS, Magisk, etc). I'd do a quick full image backup to the SD card. It took about 20 mins max. Then I'd perform whatever update task, and if it boot looped, or soft bricked, I'd immediately reboot into TWRP and restore. I remember having to do that at least twice on the LG. Each time the backup restored properly and I was up and running again in 20 mins or less. There's no current backup/restore process for the Pixel that even comes close. Titanium even lets you restore individual apps/data from a TWRP backup image. You don't have to restore the entire thing. Which I'd done several times on the LG.
It's a shame. One of the reasons I chose the P6P was because I thought with it's popularity, it wouldn't take long for TWRP to be available. It may not be as valuable or necessary as it was in the past for it's flashing functions, but it certainly would be very useful, (to me anyway) for it's image backup function.
I'd definitely chip in for a TWRP bounty. For the backup alone.
Click to expand...
Click to collapse
Nice. It is definitely good to have options.
mkhcb said:
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
Click to expand...
Click to collapse
Yeah if the p6pro gets official lineage os would even be cool to have lineage recovery
Just a thought.
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