Database Info

SafeStrap Restore Fail ( on ROM Slot: stock )

So after all this mess » http://forum.xda-developers.com/general/help/watsapp-apk-installer-reboots-android-t3410453
I do the next logical thing...
SafeStrap...
and restore the backup i made like 2 months ago...
now
on ROM Slot: rom-slot1 (a cian one)
the backup restore fine... the Android boots and is all ok... jast like it was wen i do the backup... :laugh:
on ROM Slot: stock (the red one) said
Restore complete ( in white ) :good:
Fail ( in red )
The Android boots and it look ok. also... but i am not sure...
I'm beginning to think that is a problem in the physical memory assigned to ROM Slot: stock....
is any way of knowing what fail during the restore?
is any way do a the memory test of the ROM Slot: stock on safestrap or any other app.... from the android running in the ROM Slot: rom-slot1 for example...??

OK... me respondo a mi mismo.... use un traductor... el "FAILED" en rojo que da el SafeStrap al finalizar el Restore.... es simplemente porque no se pudo restablece 1 archivo.... ( lo averigue revisando el "recovery.log" del SafeStrap )..... es un archivo relativo al Super User....... y efectivamente en el Android Restaurado.... la app Super user no anda.... fue necesario reintalarla..... luego de eso.. quedo todo OK....

Blackview BV8000 Pro - Development & Support

In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.​
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 7.0)
- 20170829: https://mega.nz/#!tGgnXIia!AITcSq9KOvFhJvr52B4vXQfKN5PqUkv9UwGFRDNwkJI
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
- 20170822: https://mega.nz/#!8HoXkD6A!wdawC1oCPjYWGsmTGE7zrZ2YF3cbggMi9UHlOMbmeWo
- 20170814: https://mega.nz/#!IfRUyTYK!79mgMoIrpi5G5wN9r5dR3eP1q857vDuu2LtLqrK5AAY
- 20170718: https://mega.nz/#!BHhA0IrA!UCjPq7vLbv8MFJafqXNnDtYpp9dDSUOKxL_hy5Ko8W0
Flash Tool
- Latest SP Flash Tool for Windows and Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A​
Recovery:
- TWRP 3.1.1 by @jemmini : https://mega.nz/#!lEUwBAzK!OSyygGsLE9UCRiHn91Fg6-kuGbXkgE2vnt7ihoWFNWw​
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu​
Extras (Root-Only):
Customization
- Xposed Framework (not available on Nougat yet): http://forum.xda-developers.com/showthread.php?t=3034811​
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en​

HOW-TO Root, Install Custom Recovery (TWRP) and Restore Stock ROM guide: https://docs.google.com/presentation/d/1NJcDBkLk8zMwyv2BTqRjn2NB_ZOWKjP1fRpSVr44Oxk
Proudly provided by GearLabs (me)

Blinking the screen on BV8000 pro - is the problem of hardware and software?

Mamay2u said:
Blinking the screen on BV8000 pro - is the problem of hardware and software?
Click to expand...
Click to collapse
If the problem doesn't disappear after you restore the Stock ROM, then it is an hardware problem.

Hello,
the phone is not fully rooted, SuperSu binarys are not updateable and busy box cant be installed (my phone is encrypted).
Is there any solution to make Android multiuser/guestmode working on that phone?
Thx

Pappmann said:
Hello,
the phone is not fully rooted, SuperSu binarys are not updateable and busy box cant be installed (my phone is encrypted).
Is there any solution to make Android multiuser/guestmode working on that phone?
Thx
Click to expand...
Click to collapse
Have you followed my root guide?
About the guest/multiuser mode, you should be able to enable it by adding two lines to the build.prop file.
Code:
fw.show_multiuserui=1
fw.max_users=5

Alberto96 said:
Have you followed my root guide?
About the guest/multiuser mode, you should be able to enable it by adding two lines to the build.prop file.
Code:
fw.show_multiuserui=1
fw.max_users=5
Click to expand...
Click to collapse
i know, but that does not work, i also changed to
Code:
ro.ag.userswitch=yes
ro.remove.multiuser.switch=no
But User swich is not available in statusbar. When i add a new user, i can access to new profile but i cant switch back.

Pappmann said:
i know, but that does not work, i also changed to
Code:
ro.ag.userswitch=yes
ro.remove.multiuser.switch=no
But User swich is not available in statusbar. When i add a new user, i can access to new profile but i cant switch back.
Click to expand...
Click to collapse
They (Mediatek or the company who produces the software for Blackview) messed up the framework then.

Alberto96 said:
They (Mediatek or the company who produces the software for Blackview) messed up the framework then.
Click to expand...
Click to collapse
Is there any way to replace the statusbar/quick settings menu to stock android or a user shortcut in configuration menu or in launcher?

Im really thinking of buying this phone. My main worry is that the UBS-C port on works with the cable that comes with it and that regular headphones wont work with the headphone output on this phone. Can anyone make any of this clear?

Pappmann said:
Is there any way to replace the statusbar/quick settings menu to stock android or a user shortcut in configuration menu or in launcher?
Click to expand...
Click to collapse
Not that easy, you need to modify the SystemUI.apk.
hobs0n said:
Im really thinking of buying this phone. My main worry is that the UBS-C port on works with the cable that comes with it and that regular headphones wont work with the headphone output on this phone. Can anyone make any of this clear?
Click to expand...
Click to collapse
As regards the USB-C port, you can find compatible cables that fit (as long as the connector isn't too short, it works. For example, AUKEY ones are not compatible but iVoler ones yes), unfortunately though you are right for the headphone jack. As far as i know, there are no other headphones/earphones with a long plug.

20170814 Stock ROM added to first post.
Changelog:
- Minor bug fixes (Camera Blur issue)

Alberto96 said:
Not that easy, you need to modify the SystemUI.apk.
Click to expand...
Click to collapse
Does anyonehere have Experience to change the SystemUI.apk to stock android Statusbar/Quicksettings?

20170822 Stock ROM added to first post. Fixes all issues with Waze and Google Play. (for users being impacted by these issues)

Ciao @Alberto96 , ho da pochissimo acquistato questo grandissimo telefono dopo aver avuto il bv6000. Non mi dilungo... Ho seguito alla lettera la tua guida per il root, appena ho terminato il flash al primo avvio tenendo premuto v+ mi parte la recovery TWRP ma al riavvio successivo premendo sempre v+ mi si avvia la recovery originale.
In più riprovando e rimettendo TWRP ho seguito la procedura per installare supersu che sembra andare a buon fine ma al riavvio successivo non è tra le app e rimane sempre non rootato.
La versione di rom che ha è la V0.1_20170803_20170829-1811 è ho usato la tua versione di TWRP e di SP Flash Tool.
Cosa posso fare? Ti servono altre info? Grazie in anticipo per l'aiuto.

danielesr82 said:
Ciao @Alberto96 , ho da pochissimo acquistato questo grandissimo telefono dopo aver avuto il bv6000. Non mi dilungo... Ho seguito alla lettera la tua guida per il root, appena ho terminato il flash al primo avvio tenendo premuto v+ mi parte la recovery TWRP ma al riavvio successivo premendo sempre v+ mi si avvia la recovery originale.
In più riprovando e rimettendo TWRP ho seguito la procedura per installare supersu che sembra andare a buon fine ma al riavvio successivo non è tra le app e rimane sempre non rootato.
La versione di rom che ha è la V0.1_20170803 è ho usato la tua versione di TWRP e di SP Flash Tool.
Cosa posso fare? Ti servono altre info? Grazie in anticipo per l'aiuto.
Click to expand...
Click to collapse
Solo Inglese su XDA-Developers.
I'll summarize your question to let others who don't understand Italian know it. He is asking why the device keeps losing TWRP after a reboot, as well as SuperSU.
I guess the system partition gets mounted as read-only, thus, all changes won't get applied.
To be sure, after installing SuperSU, go to the TWRP's File Manager, browse to /system, and delete the "recovery-from-boot.p" file. Please make sure that the system partition is mounted before doing this, otherwise you will get a blank folder.
If you get an error, then it means that the system partition has been mounted as read-only. You will find the RW flag in the Settings menu.
Keep me informed

20170829 ROM added to first post, should fix all issues with camera focus.

I'm sorry to all for my bad English. Thanks for the help Alberto, it was mounted read-only.
Enabling it I managed to get on /system and delete the "recovery-from-boot.bak" file (I did not see any other names).
I tried again to install SuperSU and restart, to reflash TWRP and check that the file was always deleted, the memory enabled RW .... but at first I do not find SuperSU and I reboot the original recovery as well.
Now I'm trying again with another Windows but it does not change the situation.
PS: Looking at the log better when installing Super SU writes: Boot image patcher - Finding Boot Image - Boot image: / dev / block / mmcblk0p21 - extracting ramdisk - failure, aborting.

danielesr82 said:
I'm sorry to all for my bad English. Thanks for the help Alberto, it was mounted read-only.
Enabling it I managed to get on /system and delete the "recovery-from-boot.bak" file (I did not see any other names).
I tried again to install SuperSU and restart, to reflash TWRP and check that the file was always deleted, the memory enabled RW .... but at first I do not find SuperSU and I reboot the original recovery as well.
Now I'm trying again with another Windows but it does not change the situation.
PS: Looking at the log better when installing Super SU writes: Boot image patcher - Finding Boot Image - Boot image: / dev / block / mmcblk0p21 - extracting ramdisk - failure, aborting.
Click to expand...
Click to collapse
It sounds like a LZMA ramdisk then.
Could you try Magisk instead? https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

Alberto96 said:
It sounds like a LZMA ramdisk then.
Could you try Magisk instead? https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
Click to collapse
I tried to install Magisk-v13.3.zip with TWRP just installed but:
Mounting /data/magisk.img to /magisk - Magisk image mount failed...

Super guide: Persist file the magical file

This is a guide that will help all users who have problems with WIFI (bad mac address), bluetooth, sensors, cameras and everything related to the part of the hardware malfunction of our device in this case of POCO F1 (also It can work on most phones with Qualcomm processor but persist.img file and twrp are diferent, search on your device thread for files) when moving from one ROM to another: From MIUI to AOSP or vice versa, or from AOSP to AOSP.
Requirements
1. It is mandatory to have the bootloader unlocked
2. Being in some AOSP rom based on android 9 or MIUI, in Q the WIFI works normally (something strange lol)
3. Use the recovery (TWRP) found in the attached files
4. Use the persist file that I am going to attach
Steps
1. Install the attached TWRP
2. Start in TWRP
3. Conect device to PC and put "pocopersist8.img" on internal memory
4. Go to install, select IMG option, select persist file "pocopersist8.img" and install on persist partition
5. Reboot your SO and check
Donwloads
https://drive.google.com/file/d/1MWLwpR-n9sDC5w1gGzZnBdPbSjYzK_9-/view
Note: Not forget press thanks button
Thanks for all guys (not remember usernames)
Tester
@syazzess Thanks for try this

This caused me problems..
I flashed this and then noticed the phone took longer to start.. Then today I was watching youtube so I switched to auto rotation and I was shocked to see rotation still locked.. so I restarted and was on 15% battery and after restart it jumped to 40%.. the reboot didn't fix the problem so I entered CIT to check hardware and found out that the proximity, accelerometer, gps, gyro, magnetic sensors aren't working..
I was smart enough to have taken a backup before flashing the persist image.. I restored the backup and everything was fixed.. battery became 15% and boot was fast etc.
I have the global version of pocophone.. I think this isn't compatible..
if you want to fix any issue just do a fastboot flash of stock rom but keep bl unlocked..

adhammagdy said:
This caused me problems..
I flashed this and then noticed the phone took longer to start.. Then today I was watching youtube so I switched to auto rotation and I was shocked to see rotation still locked.. so I restarted and was on 15% battery and after restart it jumped to 40%.. the reboot didn't fix the problem so I entered CIT to check hardware and found out that the proximity, accelerometer, gps, gyro, magnetic sensors aren't working..
I was smart enough to have taken a backup before flashing the persist image.. I restored the backup and everything was fixed.. battery became 15% and boot was fast etc.
I have the global version of pocophone.. I think this isn't compatible..
if you want to fix any issue just do a fastboot flash of stock rom but keep bl unlocked..
Click to expand...
Click to collapse
Wait, what? did you flashed this although everyting was working fine for you? What the hell

EugenStanis said:
Wait, what? did you flashed this although everyting was working fine for you? What the hell
Click to expand...
Click to collapse
Had imei problem.. thought it was persist but turns out to be rom bug ?

this persist file made me able to flash miui 9 oreo again after having "find device storage corrupted" and missing mac address/no wifi.
many thanks

adhammagdy said:
Had imei problem.. thought it was persist but turns out to be rom bug
Click to expand...
Click to collapse
Did you fixed imei problem, can you explain how to fix

eduardozeassesme said:
This is a guide that will help all users who have problems with WIFI (bad mac address), bluetooth, sensors, cameras and everything related to the part of the hardware malfunction of our device in this case of POCO F1 (also It can work on most phones with Qualcomm processor but persist.img file and twrp are diferent, search on your device thread for files) when moving from one ROM to another: From MIUI to AOSP or vice versa, or from AOSP to AOSP.
Requirements
1. It is mandatory to have the bootloader unlocked
2. Being in some AOSP rom based on android 9 or MIUI, in Q the WIFI works normally (something strange lol)
3. Use the recovery (TWRP) found in the attached files
4. Use the persist file that I am going to attach
Steps
1. Install the attached TWRP
2. Start in TWRP
3. Conect device to PC and put "pocopersist8.img" on internal memory
4. Go to install, select IMG option, select persist file "pocopersist8.img" and install on persist partition
5. Reboot your SO and check
Donwloads
https://drive.google.com/file/d/1MWLwpR-n9sDC5w1gGzZnBdPbSjYzK_9-/view
Note: Not forget press thanks button
Thanks for all guys (not remember usernames)
Tester
@syazzess Thanks for try this
Click to expand...
Click to collapse
I'm on MiRoom 9.12.26 but find device storage corrupted if i flash this file can it solve the problem

ttreddy2210 said:
I'm on MiRoom 9.12.26 but find device storage corrupted if i flash this file can it solve the problem
Click to expand...
Click to collapse
read earlier replies. it did solve such problem in my case!

rar files are corrupted..i need backup of persist files..tia

Hello! I would be very grateful if you could help me. I have problems with camera software on my POCO f1. If we look at MY camera device info, we can see that camera id, resolution, focus mode, all settings are wrong for both cameras. (2nd pic) On 1st pic we can see right setting.. &My flash light, camera flash as well is not working, when I check in the cit mode flash light is working. Did factory reset, downgrade miui and custom ROM also tried. Still problem..Can i use persist.img to fix?

eduardozeassesme said:
Este é um guia que vai ajudar todos os usuários que têm problemas com WIFI (endereço mac ruim), bluetooth, sensores, câmeras e tudo relacionado à parte do mau funcionamento do hardware do nosso dispositivo neste caso do POCO F1 (também pode funcionar no a maioria dos telefones com processador Qualcomm, mas arquivo persist.img e twrp são diferentes, pesquise no encadeamento do dispositivo por arquivos) ao mover de uma ROM para outra: De MIUI para AOSP ou vice-versa, ou de AOSP para AOSP.
Requisitos
1. É obrigatório ter o bootloader desbloqueado
2. Estando em alguma rom AOSP baseada em android 9 ou MIUI, no Q o WIFI funciona normalmente (algo estranho rsrsrs)
3. Use a recuperação (TWRP) encontrada nos arquivos anexados
4. Use o arquivo persistente que irei anexar
Passos
1. Instale o TWRP anexado
2. Comece em TWRP
3. Conecte o dispositivo ao PC e coloque "pocopersist8.img" na memória interna
4. Vá para a instalação, selecione a opção IMG, selecione o arquivo persistente "pocopersist8.img" e instale na partição persistente
5. Reinicie seu SO e verifique
Donwloads
https://drive.google.com/file/d/1MWLwpR-n9sDC5w1gGzZnBdPbSjYzK_9-/view
Nota: Não se esqueça de pressionar o botão de agradecimento
Obrigado a todos (não me lembro dos nomes de usuário)
Testador
[MENTION = 10062917] syazzess [/ MENTION] Obrigado por tentar isto
Click to expand...
Click to collapse
Meus sensores pararam de funcionar
Esse arquivo também funciona na miui 12 global?

n0v4c41n3 said:
Hello! I would be very grateful if you could help me. I have problems with camera software on my POCO f1. If we look at MY camera device info, we can see that camera id, resolution, focus mode, all settings are wrong for both cameras. (2nd pic) On 1st pic we can see right setting.. &My flash light, camera flash as well is not working, when I check in the cit mode flash light is working. Did factory reset, downgrade miui and custom ROM also tried. Still problem..Can i use persist.img to fix?
Click to expand...
Click to collapse
Hey man, I'm having exactly same issue. Did you find any fix?
i tried flashing persist but it doesn't work.

Thank you very musch bro it worked i got an error while changing rom
Twrp say failed to mount '/persist' (no data massage)
And not booting in any custom rom even globla l stock rom
Then flashed your pesisr file orangefox mount problem solved and phone boot up
Working fine

thanks friend!
You save me!
BR

Ulefone Power 5 - TWRP v3.3.1 + Root + Decrypt

Ok, I'll start right away. I can't post links because I have never posted on XDA before, but I can tell you where to get what the title says. Just google for "needrom CarelMinnaar" and you will find the link under my name.
I've made a "pack" to get the Ulefone Power 5 MF2 (MF2 is the 6GB version, although the steps should also work for the MF1 4GB version) Rooted with Magisk (v20.3) and Magisk Manager (v7.5.1) while also installing TWRP (v3.3.1) and getting rid of the Forced Encryption, DM-Verity and Disk Quota - all at the same time... This will not revert back to the factory recovery mode if you follow the steps in my readme file (inculded in the .rar file).
This work is heavilly based/reliant on Topjohnwu, Jcadduono, Zackptg5 and Hadenix - they deserve the credit and thanks for their hard work. I have tested, ported and combined all this to make it work on the Ulefone Power 5 (and in the process took a few days to brick my device a few times until I get it perfectly right so you don't have to struggle / go through the headaches).
As with anything you do – it is at your own risk, not mine.
You can download it over at NeedROM: Just google for "needrom CarelMinnaar" and you will find the link under my name. This will ensure your internal storage is decrypted, so you should be able to back it up, etc. I wish I could post it here, but I'm not very active posting on here, maybe someone else wants to put up the link...

Mano isso é show , alguém poderia fazer um tutorial do ulefone Power 5 tem muita gente usando e querendo modificar eu msm já modifiquei tanto que quero de novo mais quero mais novidades, vlw o post

Hey man, thanks for your work! I had planned to reprogram the whole vendor partition, but I will try your work first!
This is the file you uploaded?

Problem with 64gb micro sd, a photo is damaged and it does not allow me to maneuver the unit, that is, it does not allow me to format it.

I miss a warning that the sd card could have problems, I tried to open it on my mobile but it did not respond, so I did it from the pc. It turns out that there is a photo that is damaged, when trying to delete it I get the error 0x80070570, so I tried to format the drive. I did it from the format button when you give the options with the mouse, and I tried it from the device manager, without slow formatting, in both file systems (NTFS / extFAT) and neither worked, when I finished formatting it opened the drive and nothing had been erased. When I selected all the files and deleted them manually, only the photo remained there. Then I resorted to a CMD. First with the DEL command, I get the same error, so I use CHKDSK and I skip the following error: Chkdsk E: / f The file system type is exFAT. The volume serial number is 0C22-CA71 Windows is checking files and folders ... Corruption was found while browsing the files in the \ DCIM \ Camera \ directory (5086). Corruption was found while examining files and directories. Corruption was found when examining the volume bitmap. Failed to recover lost files. I tried to search for info on the internet but nothing appeared, so I hope someone here can help me tot

If it's a downloaded image you may have an infected jpeg.
Nasty critters.
Normally their mischief is confined to the folder they're in but that's only from what I've experienced. They can execute global changes on PC based platforms. I haven't seen that in Androids... that's not to say they can't. If it's a new one it may not be detectable by virus scans as no definition may exist but it's actions give it away.
If so low level format the SD card. If it's an infected jpeg delete it at all costs. I hope you were using redundant backup... and don't let those SD files near the backups

Formatting the SD-card should work with
SD Memory Card Formatter for Windows Download | SD Association
www.sdcard.org

blackhawk said:
Si se trata de una imagen descargada, es posible que tenga un archivo jpeg infectado.
Bichos desagradables.
Normalmente, sus travesuras se limitan a la carpeta en la que están, pero eso es solo por lo que he experimentado. Pueden ejecutar cambios globales en plataformas basadas en PC. No he visto eso en Androides ... eso no quiere decir que no puedan. Si es uno nuevo, es posible que no sea detectable mediante análisis de virus, ya que puede que no exista una definición, pero sus acciones lo delatan.
Si es así, formatee la tarjeta SD de bajo nivel. Si es un jpeg infectado, elimínelo a toda costa. Espero que estuvieras usando una copia de seguridad redundante ... y no permitas que esos archivos SD se acerquen a las copias de seguridad
Click to expand...
Click to collapse
No es un jpg descargado, es una foto. El teléfono me advirtió que la sd estaba llena y podría tener problemas pero no me importa, y aparentemente es el archivo el que está causando problemas. El formateo limpio no funciona. Intente formatearlo de varias maneras, pero recuperará todos sus archivos cuando lo abra.
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example),translation added below:
It is not a downloaded jpg, it is a photo. The phone warned me that the sd was full and might have problems but I don't care, and apparently it is the file that is causing problems. Clean formatting doesn't work. Try to format it in various ways, but it will get all your files back when you open it.