I have some data (other than contacts, SMS, photos) and my phone booted in ColorOS recovery mode.
All of my data is there in the phone storage.
Is there a way to backup my data to SD card?
I suppose the cause of the issue to be uninstalling some bloatware in Realme UI using pm uninstall -k --user 0.
P.S:
1. My Volume Down button is also not working.
2. I have not unlocked the bootloader.
3. Android version: ColorOS 7 (Realme UI v1.0)
Try flashing your current RUI version ozip by stock recovery
Related
WARNING! Although I find a way to install this on our beloved SHV-E370K, this ROM is official for the GT-I9190 and GT-I9195 variant only, and therefore may not have support from CM team!
Your warranty is now void. I am not responsible for bricked devices, dead SD cards, or lose your data. PLEASE READ THIS THREAD COMPLETELY AND BACKUP YOUR NAND BEFORE DO ANYTHING.
Note 1: If you do not know how to use ODIN, flash a recovery, and/or using CMW recovery, please have a research before trying anything.
Note 2: This method do not require root.
Note 3: ROOT access is implemented in CM12 rom, so do not ask me how to root.
Note 4: 3G working fine. LTE are not tested (although it suppose so). Network operators in my country do not support LTE yet, so I can not guaranty it is work.
Note 5: Tested on CM-12-20150123 and 20150124.
CM-12.0 Android Lollipop 5.0.2 Install Guide.
1. Make sure you have latest ORIGINAL ROM (build E370KKTU2BNK5) installed on your device, or at least the baseband E370KKTU2BNK5. You can check this by go to Settings -> About phone -> Baseband version. This is to ensure all network connections are functional.
2. Download and install CMW recovery (attachment).
3. Download CM-12.0: https://download.cyanogenmod.org/?device=serranoltexx. And GAPPS for Android 5.0: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900. Put those file into your SD card (internal memory also work).
4. BACKUP your DATA (SMS, picture, contact, ...) before taking next step.
5. Reboot into recovery by completely turn off your phone. Press VOL + and HOME and POWER button at a sametime for 2 - 3 seconds.
Backup your phone by go to "Backup and restore -> Backup to SDcard". You will need this backup later if you decide to go back to your previous ROM and data.
Go to "Install from sdcard" and install ROM file first, then GAPPS file.
Wipe Data, Cache and Davik cache.
Reboot your system.
6. Wait till boot complete and enjoy CM12 on your little SHV-E370K. Restore your data if needed.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Upgrades
Upgrades from previous versions of CM-12.0 are the same process as install, except you do not need to wipe anything. Contrary to popular belief, you do not need to even wipe cache and dalvik-cache when upgrading between CM-12.0 versions. You only need to wipe if you are doing a major upgrade, switching to a different ROM entirely, or attempting to fix bugs caused by bad backups or corrupt app data.
Credits:
Epic CM Team.
Everyone that donated beers
Excuse me. I have some questions.
What is difference between this guide and general recovery install guide?
I'm using with official CM12 nightly for GT-I9195 with my shv-e370k.
But I don't have major problems.
Just I can't check HD Voice(VoLTE) and LTE+(Broadband LTE) are work.
Is there any other problems?
Can i use stock recovery in doing this?
how can I update my firmware?
---------- Post added at 02:20 PM ---------- Previous post was at 01:47 PM ----------
do anyone test this rom???
Tnx dude,
ask
can i use this for my firmware e370kktu2bpl1
Hi
How can i downgrade from 7.2.9 to 6.12.22 (both xiaomi.eu developer)?
Will i loose my data and applications already are installed?
Sent from my Redmi Pro
No idea???
Sent from my Redmi Pro
I believe you will have to full wipe to downgrade, sorry you lose all.
A full wipe and clean install is needed.
You can make a backup of all your installed apps + data (not system apps) with titanium backup or some other software.
Then restore after fresh rom install.
I have just clean flashed OS 5.1.5 including data format etc. because I was still running 5.0.4 dirty flashed over 4.5.14 and I wanted to get rid of some errors. Yesterday, after spending an hour or 6 re-installing apps and doing settings, nothing too excited, I thought, before installing Magisk-Mods etc. it was time for a back-up (Nandroid). Went to Recovery (TWRP Cheeseburger 3.2.3.0) and made the Nandroid. That went totally wrong:
After back-upping boot and recovery, it went to back-up system which gave me red letters:
createTarFork() proces beëindigd met fout: 255
Sorry for the Dutch language [proces ended with error 255]. And it ends with "Back-up failed. Clean up Back-up folder" (translated from Dutch). Than no Nandroid was taken and that was it.
Today I started all over (clean flash). Installed TWRP and Magisk. Made Nandroid, worked well. Also putting Nandroid back went well.
But whatever I flash (Mod in TWRP for old bootloader) or if I install some Magisk modules, and reboot to Recovery, I get the same error. It's very frustrating, because if I have no reason to believe this won't come back, why would I proceed. Anyone who has seen this and can help?
I know how to flash but I would not consider myself an experienced flasher whatsoever. I am running stock, normally encrypted and rooted with Magisk (tried 16.0 and 16.7 beta, results is the same). Everytime I look in "mount" in TWRP either System and/or Vendor are not ticked after a reboot to TWRP. I don't know if that's inportant. Although when I do tick them, they might be "unticked" after a next reboot to TWRP. If anyone needs to see for example logs then please tell me how to make / create / export them. I really hope someone can help!
Things getting worse!
Now, things are stranging up! I found out that many of my errors and app-closings were caused by (systemless) Xposed on 5.0.4
What I did is:
- uninstalled Xposed
- uninstalled Magisk
- flashed new recovery TWRP Cheeseburger 3.2.3.0
- dirty flashed 5.1.5 over 5.0.4
- did all the wipe cash stuff etc.
- flashed Magisk
Voila. Up and running! 5.1.5 smoothless without problems.
I made at least 10 Nandroids in between in the last 24 hours and also put those back (trying all the time).
I literally made NO changes whatsoever to critical things. I only have root via Magisk and 4 modules installed.
Just, a few minutes ago, I want to make another Nandroid before trying to work on Substratum / Ozone (which I had not installed before on OS 5.x.x).
Guess what. Same createTarFork-Error, I'm going crazy, now I can't make Nandroids anymore, is there no one who can help?
5.1.4 first?
Double post sorry
5.1.4 first?
I read in other posts that 5.1.4 should have been flashed BEFORE 5.1.5 - I came straight from 5.1.4 - could that be the problem?
Still, I was able to make Nandroids (System-partition is causing the error). I just don't feel like having to set up my whole phone again. Therefore. Question:
- should I flash 5.1.4 NOW?
- than reboot and reinstall 5.1.5
Should that help, anyone to explain exact steps?
exis_tenz said:
I read in other posts that 5.1.4 should have been flashed BEFORE 5.1.5 - I came straight from 5.0.4 - could that be the problem?
Still, I was able to make Nandroids (System-partition is causing the error). I just don't feel like having to set up my whole phone again. Therefore. Question:
- should I flash 5.1.4 NOW OVER 5.1.5 - and would that work?
- than reboot and reinstall 5.1.5
Should that help, anyone to explain exact steps?
Click to expand...
Click to collapse
Please anyone? Can I install 5.1.4 OVER the actually running 5.1.5 without losing settings / data etc.?
Will that fix my ability to make full Nandroids?
This is a known issue on certain devices that TWRP devs don't seem to be able to fix for some reason. Even yesterday I got hit by this, both on an OOS backup and a custom AOSP ROM backup. It seems to freak out with certain specific directories, mostly on OnePlus devices. It's all over Google since 2015 or so...
Okay, thanks for that! But CAN I flash 5.1.4 OVER 5.1.5? Or is 'downgrading' like that impossible?
Is it so that with 5.1.4 those directories were splitted?
I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:
1 - Use a correct TWRP implementation
TWRP need to access the uncyphered partition /data.
There no possibility to backup it, if TWRP does not implement deciphering user data partition.
2 - Remove all users except user 0 (the administrator)
You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".
To remove the others users :
Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).
Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.
On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).
On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).
On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)
On others devices ... you must find all parameters that create those unwanted users.
If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").
3 - Do not forget to protect your backups by a password
This would be stupid to cipher your /data partition and keep backups of this partition unprotected.
These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.
I post on this forum because I hope that this will be helpful for others devices owners.
Hey, a few days ago i fked up again.
I was on the rooted global 10.3.9 rom (which is not the latest global version).
I got daily notifications to update to MIUI 11 but they were annoying and there was no way to disable those notifications. So i deleted the system updater app on titaniumbackup, also freezed the system APP updater and system app config or something.
Then I rebooted but it didn't boot system, it went to twrp instead (russian version).
So i figured i had to re-install the rom that was already on it to get the deleted system updater apps back. Dirty flashed it, but it booted into twrp again. And that's where I'm at now.
I don't want to factory reset because i forgot to back up my whatsapp chats...
Any solutions?
I still have all my personal data btw.
Hello everybody
I solved a boot loop caused by a Magisk update with the Motorola Rescue and Smart Assistant sw (link).
Now I have Android 9 in the device (I had Oreo before and I was fine)
But now I have the problem that there is no Xposed for Pie, and the alternatives I tried (Riru EdXposed, Riru LsPosed) cause the device to bootloop.
Question: so far to restore the Moto G6 Plus I go to recovery and performed the factory reset; is there the possibility to restore the device while keeping the configurations and apps installed?
Or alternatively, is it possible to downgrade to Android 8 Oreo?
Ps
Sorry for my english, I use Google translate...
Use titanium backup to save apps from restoring. first backup, then save the files on computer, then Put them back and use titanium backup to restore.
Titanium backup needs root.
As for downgrading... You just have to flash it like any other stock rom, but you have the chance of something not working...