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
Related
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
Hi
I had installed NamelessRom along with the unified storage layout. All was working smoothly and then I was getting random freezes.
Only way to avoid was to revert back to stock ColorOs. Now however I have the 48mb problem with the partition. On top of that, I can't boot to recovery, it just goes to fastboot. I have tried running the swaplayout.bat partition tool again, but the phone just stays on fastboot for half an hour at least.
Is there any way that I can install NamelessRom again and see if it recognises the unified layout from the first boot?
Any help would be greatly appreciated. Virtual hugs and beers await...
I had the same problem.
download colorOS 1.2.7i and extract the zip
in adb
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
if your bootloader is locked
Fastboot oem unlock
here is a stock oppo recovery that will handle colorOS1.2.7.i install. http://s000.tinyupload.com/file_upl...3653419942379&del_id=58779725699588589872&gk=
TWRP recovery to remove LVM
Custom ROMS cause random reboots for me. I'm stuck on coloros 2 beta but that is stable. I really want Nameless LVM unified though.
i have a oppo find 7 a year and since then I did to the root, but today decided to change rom but something went wrong because now he is always the restart and go to the screen of fastboot ? I can do is urgent ...
The rom and I put SlimSaber - find7-5.1.1-20150926 find 7
Hello.
Use "fastboot oem unlock", then flash recovery again and everything should work.
Regards.
Hei kucici a link to donwload please?
Hello. I already have an oppo find 7 for a year and I've root it and changed its rom twice. Last rom was color os 1.2.7 and I've changed it to SlimSabet find 7-5.1.1-20150926 find 7 and all went right but when it was 100% the phone reset and it was like you can see in the picture above.
The problem now is that my pc windows 7 has no conection to my oppo find 7. In the device manager it appears android phone and below alcatel adb interface. I can't do the connection between my pc and the oppo and I can't do the recovery.
I always had smartphones, but as it is the first time I have one with windows os and the first time I do this kind of stuff to an android I'm a bit confused...
My oppo is like thart for two weeks now and I don't know what else to do. I've searched in a lot of foruns, but no one has a solution for my problem. Can anybody help me, please?
THANK YOU
darrenpauli said:
I had the same problem.
download colorOS 1.2.7i and extract the zip
in adb
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
........=[/url]
TWRP recovery to remove LVM
Custom ROMS cause random reboots for me. I'm stuck on coloros 2 beta but that is stable. I really want Nameless LVM unified though.
Click to expand...
Click to collapse
YOU MADE MY DAY...... Thank you so much, everything works again.
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
Can anyone pls tell me where I can download stock rom for (lenovo) p2 preferable in zip format . And is there any unbricking tutorial .
I want this too...? if anyone can help...
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Then share it no
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
aleleo87 said:
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
Click to expand...
Click to collapse
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
itsjustbilly said:
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
Click to expand...
Click to collapse
Ah ok i didnt understand that you have this modem issue. I don't kno how to help you...you phone is bricked so you can test few solutions without more risks .
before flash the original recovery , boot and system by fastboot, you can try to install TWRP again and flash only the bootloader from TWRP (should support .zip and .img files). Then you turn the phone in fastboot mode and flash other stuff .
Taken from post 4 of the TWRP page on lenovo P2 forum
smaranramesh said:
Then share it no
Click to expand...
Click to collapse
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
itsjustbilly said:
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Click to expand...
Click to collapse
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
veimus said:
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
Click to expand...
Click to collapse
Witaj. Mozesz napisać jak wgrałeś czysty soft do Lenovo p2. Tez mam rom z t.mobile a nigdzie nie ma poradnika jak wgrać czysty soft.Pozdrawiam
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
Is there an alternative download link? What is Mega? I want to avoid these third party download utility if I can...
I put the following into a BAT file and placed it into ADB / Fastboot directory:
Code:
fastboot flash partition gpt_both0.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
pause
Extract all the files listed in the BAT file or simply extract the entire archive to ADB / Fastboot and launch the BAT file.
Does this work?? @Undesirable
the above post
Oh yeah, it unbricked me and put me back to stock so I could get OTA updates for Nougat. You need the archive posted earlier in the thread though.
@Undesirable Nice and elegant solution man! Typing all this stuff was so annoying.
For those who need an alternative download source, I offer this magnet link:
Code:
magnet:?xt=urn:btih:ef05ea3af4da8a0cbb137c10621942f3ae16d46f&dn=P2a42_S048_161111_ROW_fastboot.7z
It's slow unless lots of people help to seed it.
Is it possible to flash this firmware 2a42_S048_161111_ROW_fastboot.7z on the P2c72 with firmware build number: V3.5_1652_5.1342.1_ST_p2c72 ???
I bought this phone 4GB Ram/64GB from china, but I want to put the international firmware on it.
Thanks!
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
how can I replace my data partition? It's not getting formatted due to an encryption error
If fastboot erase userdata doesn't work, then use TWRP to change user data file system to EXT4 then change it back to F2FS again.
Need help...
I flashed back the stock ROM (due to encryption error in custom 7.0 ROM) using fastboot commands, but my SIGNAL WON'T WORK after I started d phone . I've tried reflashing the stock firmware (and also custom ROMs) but my phone won't detect the signal. "About phone" settings show unknown baseband and IMEI... how to get it back
---------- Post added at 08:58 AM ---------- Previous post was at 08:06 AM ----------
I've flashed 'ROW' variant of stock ROM. Is there a different version for Indian variant?
How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)
I am currently on lineage OS 14.1 (7.1.2) dated 18.09.2017.
I want to go back to stock firmware as I am facing some issues with lineage.
How to find the latest firmware. Found this website which has all the images https://firmware.center/firmware/Motorola/Moto Z Play/Stock/XT1635-02/
But I am unable to select the correct one for my device. (do not want to brick it). Also found another thread stating latest firmware
https://forum.xda-developers.com/moto-z-play/help/addisonnpns26-118-22-1cid50subsidy-t3675521
I am an Indian MOTO Z Play
Is there a way to go full stock and also start to receive OTA updates. Can someone provide me with full guide with links?
First you need exactly your software channel and the build of your baseband and bootloader. You know how to get this information?
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
kkube said:
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
Click to expand...
Click to collapse
I'll be waiting for it.
Process to go from custom rom back to stock (August update)
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
Click to expand...
Click to collapse
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
And can we do OTA updates after doing this?
Thank you so much for this guide, my phone was rebooting to recovery every single time and nothing worked. I flashed this rom as you said and my phone just booted and it's working. I can't believe it.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
Click to expand...
Click to collapse
My phone is reteu and after flashing is still on reteu, so it should be fine, dont worry. Also you should get any future updates via OTA.
kkube said:
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Click to expand...
Click to collapse
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk
akshaypatil869 said:
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Click to expand...
Click to collapse
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk
Does anyone receive the update with September patch via OTA after back to stock following post #5 instructions?
This a fantastic guide - THANKS!!! - I have linked to it giving credit. Thanks!
I have also a thread, if you follow that one. Bootloader is locked/ u will be able to get ota'$