Ok, first of all: I used the search button and Google a lot before coming here to post this.
My question is totally noob: can I make a NAND backup of my mobile, *before* rooting it, *before* installing custom recovery?
I'd like to do it because I'd really like to install a custom firmware (I'm oriented towards Prime or Megatron) on my O1, but I really want to have an opportunity to come back to the original firmware in case I need to repair my phone.
I've seen a large number of ways for doing backup of a phone *after* the custom recovery, but no one before.
Another question is: is it necessary to install the Android SDK for installing custom recovery, or can I run the adb commands from my mobile?
Thanks everyone in advance for the help!
The answer to your question "can I make a NAND backup of my mobile, *before* rooting it, *before* installing custom recovery?" is no. The custom recovery is the software that provides the nandroid backup facility. Without that custom recovery, you can't make a NAND backup (yet another good reason to do it).
What you can do is to backup the existing recovery image. From http://forum.xda-developers.com/showpost.php?p=9377725&postcount=9, you can do
Code:
dd if=/dev/mtd/mtd2 of=/sdcard/recovery-dump-T.img bs=4096
which will save off the stock recovery image to your sdcard. If you want to restore to the stock recovery, you can do
Code:
flash_image recovery /sdcard/recovery-dump-T.img
after you have installed the flash_image program. (Installing the flash_image program is a completely reversible step that needs root permissions, but can be completely undone.)
For your second question, all of the commands can be run from the Terminal on your phone. Note that your phone will need to be rooted and you will have to do "su" before you start typing commands. Having done "su", your prompt should turn to # instead of $.
Thank you very much for your detailed answer.
Now the question is: do I really need to do all of this stuff, or there's a way to bring back to the phone to original recovery/original OS without doing a backup myself, i.e. there is some image available from LG that restores the phone as out-of-the box?
There is only one tool from LG - LG update which updates whole your phone. It rewrite everything, also custom recovery.
Same "work" can be done with tool called KDZ_FW_UPD but, I didn't recommend it if it is not necessary.
For more information about KDZ_FW_UP take look on http://forum.xda-developers.com/showthread.php?t=875881
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!​
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
Hi, just wondering if anyone can share his/her signed boot.img from stock rom RETMX, the one I tried to flash with fasboot ends in: (bootloader) signed with bad key. The phone boots, and i can flash roms with twrp and stuff, but when in stock, trying to install OTA gets in error due to the bad key.
edit: Going into more reasoning, I realize that the main cause of the OTAS not installing, is because i've already taken the last update, and that probably messed with the gpt.bin, because when trying to flash it, the fastboot console says that I'm trying to downgrade, and aborts. So my only hope to restore this to total stock is if someone with an untouched twrp backup can share his backup with me. It needs to be in the latest update of RETMX. I would really apreciate it. Thanks.
Hi there,
I have recently installed a Magisk Module on my successfully rooted phone that so far didn't display any problems until I enabled said module (this one: Pix3lify, sorry can't post links)
Now it's stuck in a bootloop and I dont know how to recover my data from this position. I do know how to reinstall the stock rom and re-root just fine, I dont need help with recovery. What I do really wish is to backup some files from the user data partition.
I don't know how to do this as I never been in this position and before I spend all day trying to recover it I was wondering if you guys maybe know a way to do it, if possible at all.
I have access to:
- Fastboot
- Recovery (the BlackView Recovery ROM, no TWRP, couldn't find an image that runs. However, I do have access to `fastboot boot` to flash any image)
- SP Flash tools
As is expected, the device is rooted and the bootloader is unlocked. I just want my data if it's possible. If not, I'll just recover using the method that will remove all data, sadly...
Thanks in advance!
EDIT: I decided to swallow my loss and install the stock rom since nobody replied yet, however, I did make a full backup of my ROM (especially userdata) and I now can see the filesystem inside WWR_MTK, but I can't read /data because it's encrypted (but I know the password) my new question therefore is if i can open up this image still. Thanks in advance!
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
sako21 said:
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
Click to expand...
Click to collapse
Flash latest A13 update u will get stock recovery
pankspoo said:
Flash latest A13 update u will get stock recovery
Click to expand...
Click to collapse
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
sako21 said:
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
Click to expand...
Click to collapse
Just try keep unrooted boot. Img backup of your current rom.
Then go ahead though it's got currpted (one person faced that at insta but he used that commnads when he has twrp it must work with stock recovery) but after restoring boot imgae all was fine.
But try at u r own risk later don't tag [email protected] pankspoo - guide
Thanks. Will try that out.
And yes, wont tag you!
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
Wait u want to relock bootloader?
You need a otg adapter. Put Stock boot.img and the last ota update file to the usb storage.
flash stock boot.img via FKM
go to developer settings and lock oem
uninstall magisk with restore all (not image)
start phone in bootloader
fastboot flash relock
fastboot reboot recovery
select update from storage
use otg adapter with ota file
install
restart
done
For any assistance contact @sakarya1980
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
did you get the relock bootloader?
If you're still searching for the stock recovery, I've attached the .img file (unzip it first)