Develop Bugs

Cannot mount /data, can't flash ROMs

Hi guys
My Find7 using LVM and Paranoid ROM had rebooting issues (long time issues). I tried to 'fix file system' and it threw an 'encryption failed ' screen on ROM boot. That happened a few tims so I went into TWRP and attempted NANDROID restore.
That failed with error 225. I cannot after removing LVM install ColorOS 1.2.1i or 1.2.7.i . TWRP says it cannot mount '/data'. ColorOS stock recovery fails too.
Now I can't reflash through Fastboot TWRP
I think I recall fixing this by flashing Clockwork but I can't find a version for the Find 7.
Any help?
Thanks so much!

okay as soon as I published, I had moved through mass mounting coloros 1.2.7i using coloros stock recovery
I flashed and it worked.
Hours of failure prior to this.
Thanks, myself.

For anyone who can't flash recovery and is stuck do this
install fastboot. Google it.
download colorOS 1.2.7i and extract the zip to say the folder FIX
download this oppo find7 stock recovery to FIX http://s000.tinyupload.com/index.php?file_id=00219433653419942379 or use TWRP in its place (change the recovery.img name to whatever your twrp file is called.)
hold shift + right click (windows) in FIX and click open command prompt here
copy each line below and right click and paste line by line
Fastboot oem unlock
flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash LOGO logo.bin
fastboot flash reserve4 reserve4.img

Lost Recovery mode!!!???

I did the follwoing:
fastboot -i 0x2970 erase recovery
fastboot -i 0x2970 flash recovery /Users/xxxx/Desktop/androidtools1/cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NN-crackling-recovery.img
fastboot reboot
all went well- terminal reported ok
then reboot into recovery mode to install the cm13.zip file - failed!
device does not boot into recovery. I get black screen and dead device.
device comes back to life after battery is out and in again.
so no recovery mode menu.
any ideas what to do next?

wisdomlight said:
I did the follwoing:
fastboot -i 0x2970 erase recovery
fastboot -i 0x2970 flash recovery /Users/xxxx/Desktop/androidtools1/cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NN-crackling-recovery.img
fastboot reboot
all went well- terminal reported ok
then reboot into recovery mode to install the cm13.zip file - failed!
device does not boot into recovery. I get black screen and dead device.
device comes back to life after battery is out and in again.
so no recovery mode menu.
any ideas what to do next?
Click to expand...
Click to collapse
normally I just do
Code:
fastboot flash recovery <recovery-image-file>
Also how do you attempt to boot recovery?
- VolDn+Pwr ?
- adb reboot recovery ?
What if you flash stock recovery or twrp?

do you actually write <recovery-image-file> ??
I thought the actual .img file needs flashing. ??
either way - VolDn+Pwr and adb. = black screen dead device.
I thought cm-13.img is stock recovery. I downloaded it from cyanogen
twrp needs rooted device. I am trying to instal the OTA update from 12.1 to 13.0 and it doesn't work. and i was advised to un-root my device.
so now i have a un-rooted device but with no recovery.
arrrghhh

wisdomlight said:
do you actually write <recovery-image-file> ??
I thought the actual .img file needs flashing. ??
either way - VolDn+Pwr and adb. = black screen dead device.
I thought cm-13.img is stock recovery. I downloaded it from cyanogen
twrp needs rooted device. I am trying to instal the OTA update from 12.1 to 13.0 and it doesn't work. and i was advised to un-root my device.
so now i have a un-rooted device but with no recovery.
arrrghhh
Click to expand...
Click to collapse
if you unpack cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip from cyngn.com you may try to flash stock COS 13.0 as follows:
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img

How to backup current official OS

I have a swift phone with it is original OS "12.1.1-YOG7DAS2FI" and the phone already got two updates and downloaded them but I have never install any of them. the last one downloaded today is "13.0-ZNH0EAS2NH"
I saw many people are complaining about the new OS and others saying it is very good. so I am confused whether to upgrade or not. So I am thinking of upgrading, But I need to make sure I have everything backed up in case i didn't like the new OS. I need detailed steps how to completely backup current OS and how to restore it in case anything happened.
also If anyone can help and summary all cons and pros of the upgrade, it would be very helpful.
Thanks

AboudMokh said:
I have a swift phone with it is original OS "12.1.1-YOG7DAS2FI" and the phone already got two updates and downloaded them but I have never install any of them. the last one downloaded today is "13.0-ZNH0EAS2NH"
I saw many people are complaining about the new OS and others saying it is very good. so I am confused whether to upgrade or not. So I am thinking of upgrading, But I need to make sure I have everything backed up in case i didn't like the new OS. I need detailed steps how to completely backup current OS and how to restore it in case anything happened.
also If anyone can help and summary all cons and pros of the upgrade, it would be very helpful.
Thanks
Click to expand...
Click to collapse
if you have the cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip file you can always 100% downgrade to that original OS (aka stock firmware) using fastboot for all parrtitions. Same way you can 100% upgrade to cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip stock firmware.
However going 12.1 13.0 back and forward will result in factory reset. Or you can factory reset first yourself and even backup / format external SD as well.
Here is howto flash any original OS
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
I have no complaints at all about 13.0 cleanly flashed that way. Not a single 'con'.

How to fresh install Cyanogen OS?

Hi,
I am currently running Cyanogen OS 13.0 and I have not managed to update via OTA and TWRP. After TWRP-Update the system just hangs on boot. OTA just does not do the update after reboot. I just keeps downloading the OTA-Update again and again which eats my data plan, unless I notice and stop it. I am looking for a clear instruction on how to flash the newest version directly via cable. I could not find one. Alternatively I would be happy if someone could show me a way to stop the repeating downloads of the latest OTA-version.
Thanks!

basically you unzip the flashtool zip and do
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
if you want to keep data skip userdata (but clear dalvik cache in twrp)
if you want to keep twrp do not flash recovery

Dior DNA said:
basically you unzip the flashtool zip and do
Code:
fastboot flash splash splash.img[/QUOTE]
It worked thanks. Unfortunately I am back to bootloops after flashing supersu.v2.46 via twrpThis worked with previous versions.
Any idea how to do this correctly?
Click to expand...
Click to collapse

sambahb said:
It worked thanks. Unfortunately I am back to bootloops after flashing supersu.v2.46 via twrp. This worked with previous versions.
Any idea how to do this correctly?
Click to expand...
Click to collapse
You need to root MM with system less SuperSU ZIP version, I believe v2.65 onwards (v2.76 may be latest, you need to check). And each time you flash kernel (aka boot.img) again you need to root.

Dior DNA said:
You need to root MM with system less SuperSU ZIP version, I believe v2.65 onwards (v2.76 may be latest, you need to check). And each time you flash kernel (aka boot.img) again you need to root.
Click to expand...
Click to collapse
Its better to use super su 2.76 because it has boot image patcher.
Sent from my Wileyfox Swift using XDA-Developers mobile app

Rooting Motorola G6 Play gone wrong

Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke

Hi Sven,
This isn't going to be the most advanced reply, as I'm not very experienced with this stuff either, but it seems you have accidentally flashed your twrp image to 'boot', wherever that is, which is why the phone isn't able to boot to system.
Can you still boot into bootloader and recovery (twrp)?
If so, then I'd suggest using fastboot to flash a sock or custom ROM. I'm not sure exactly which one though, you have basically the same model as me and that seems to use the JETER ROMS a list of which are over here (can't post links yet, so you will just have to search on mirrors . lolnet . com /firmware/moto/jeter/official/ or remove the spaces
I seem to have somehow lost the partitions on mine, but will start a new thread question about that.

Sven Onderbeke said:
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.imgpicture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Click to expand...
Click to collapse
Just flash a stock boot.img to boot. Then just flash TWRP to recovery. In TWRP, format data. Type yes. Then reboot recovery. Then Use TWRP to flash magisk. Done.

Hi again Sven,
I just wanted to let you know that I just downloaded the following RETAIL ROM
ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and used the following fastboot commands, one at a time.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.