CLICK HERE FOR UPDATING TO B27 WITH
OR
WITHOUT ROOT
OR
COMING FROM ANY B20 FORM OR SHAPE
PLUS STOCK FLASHABLE ZIP FILES VIA TWRP
FOR ALL VARIANTS
I Apologize for creating a separate thread for all this but , was needed for all the info / files and guide for all of this.
ok, i see there's a few users with B20_boot or Rooted who want to get B27 OTA, well here is the little guide
- Download stock Recovery from here B20 stock recovery thanks @rczrider and this one ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Go to TWRP, WIPE DATA- CACHE-DALVIK .
- Now make sure SYSTEM was unchecked in mount and check mount system read-only ( THIS IS IMPORTANT DON'T SKIP THIS STEP)
- Flash this file ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Flash stock recovery you downloaded and reboot and you can now safely just Update to B27 via System Update app.
-------------------------------------------------------------------------------------------------------------------------
charlie.s said:
This procedure does not work for my officially unlocked Axon 7 (U). I am successful in reverting to stock v.20, but as soon as I ask for an update, i get the upgrade to v.20_boot.
Click to expand...
Click to collapse
you are different story,
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to you SDCard.
- Enable OEM UNLOCKING in Developers Options
- reboot to stock recovery
- Apply via SDCard > Select your file and apply.
-------------------------------------------------------------------------------------------------------
If The first doesn't work out do this then :
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to your root of your INTERNAL STORAGE.
- Go to Software update
- you may or may not see the B27 Update CHOOSE that one there and apply .
--------------------------------------------------------------------------
with this method you do lose the unlocked bootloader, don't you?
I tried it on my friend's axon 7 the other day and he was able to get the update but the bootloader was locked again. For him it doesn't matter as he uses stock and no apps that require root.
clementinox said:
with this method you do lose the unlocked bootloader, don't you?
I tried it on my friend's axon 7 the other day and he was able to get the update but the bootloader was locked again. For him it doesn't matter as he uses stock and no apps that require root.
Click to expand...
Click to collapse
as far my understanding if you are already BOOTLOADER UNLOCK you still be in the same state (Unlock).
I must have used the "fastbook oem lock" by mistake through the whole process then.
So i only need recovery.img from B20 untouched provided by rczrider? or i need boot.img as well
DrakenFX said:
ok, i see there's a few users with B20_boot or Rooted who want to get B27 OTA, well here is the little guide
- Download stock Recovery from here B20 stock recovery thanks @rczrider and this one ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Go to TWRP, WIPE DATA- CACHE-DALVIK .
- Now make sure SYSTEM was unchecked in mount and check mount system read-only ( THIS IS IMPORTANT DON'T SKIP THIS STEP)
- Flash this file ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Flash stock recovery you downloaded and reboot and you can now safely just Update to B27 via System Update app.
-------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
genbu said:
So i only need recovery.img from B20 untouched provided by rczrider? or i need boot.img as well
Click to expand...
Click to collapse
i DON'T mention boot in my guide, just the recovery from him and my flashable zip file and you'll be set.
This procedure does not work for my officially unlocked Axon 7 (U). I am successful in reverting to stock v.20, but as soon as I ask for an update, i get the upgrade to v.20_boot.
charlie.s said:
This procedure does not work for my officially unlocked Axon 7 (U). I am successful in reverting to stock v.20, but as soon as I ask for an update, i get the upgrade to v.20_boot.
Click to expand...
Click to collapse
I'm guessing you went through the official ZTE bootloader unlock process, ie filled out the form on their site. When you do that, your device IMEI is placed on a list that will no longer receive regular OTA updates, and will only get B20_Boot.
Try putting the B27 OTA update ZIP on an microSD card, rename to update.zip, make sure that OEM Unlocking is enabled in your developer options, boot into stock recovery, and apply update from microSD card.
charlie.s said:
This procedure does not work for my officially unlocked Axon 7 (U). I am successful in reverting to stock v.20, but as soon as I ask for an update, i get the upgrade to v.20_boot.
Click to expand...
Click to collapse
you are different story,
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to you SDCard.
- Enable OEM UNLOCKING in Developers Options
- reboot to stock recovery
- Apply via SDCard > Select your file and apply.
-------------------------------------------------------------------------------------------------------
If The first doesn't work out do this then :
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to your root of your INTERNAL STORAGE.
- Go to Software update
- you may or may not see the B27 Update CHOOSE that one there and apply .
@DrakenFX - Have you updated to B27?
Just curious if I should update to B27 (from B20_Boot), or just wait a bit longer for something "bigger" before I update? Or even a flashable .zip file so I don't have to re-do everything (I'm getting lazy in my old age).
clementinox said:
I must have used the "fastbook oem lock" by mistake through the whole process then.
Click to expand...
Click to collapse
Must have. I am on B27 with bootloader still unlocked.
tele_jas said:
@DrakenFX - Have you updated to B27?
Just curious if I should update to B27 (from B20_Boot), or just wait a bit longer for something "bigger" before I update? Or even a flashable .zip file so I don't have to re-do everything (I'm getting lazy in my old age).
Click to expand...
Click to collapse
no i haven't , cuz i don't have the device right now...by trying to create a flashable update zip + keeping my data intact, i ended up with a brick, i'll be getting replacement in a few days.
DrakenFX said:
no i haven't , cuz i don't have the device right now...by trying to create a flashable update zip + keeping my data intact, i ended up with a brick, i'll be getting replacement in a few days.
Click to expand...
Click to collapse
Ouch!
DrakenFX said:
no i haven't , cuz i don't have the device right now...by trying to create a flashable update zip + keeping my data intact, i ended up with a brick, i'll be getting replacement in a few days.
Click to expand...
Click to collapse
That happened to me doing root on B20 - It took them a week of playing around before they sent me a replacement. Is it gone already? I am on full stock B27 now and if there is a way to pull the software off it for you just give me a step by step so you get what you want
I used method in the OP to go from bootloader unlocked B20 to bootloader unlocked B27. Thank you!!
DrakenFX said:
you are different story,
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to you SDCard.
- Enable OEM UNLOCKING in Developers Options
- reboot to stock recovery
- Apply via SDCard > Select your file and apply.
-------------------------------------------------------------------------------------------------------
If The first doesn't work out do this then :
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to your root of your INTERNAL STORAGE.
- Go to Software update
- you may or may not see the B27 Update CHOOSE that one there and apply .
Click to expand...
Click to collapse
I followed your first scenario and was indeed able to install B27. Thanks!
DrakenFX said:
ok, i see there's a few users with B20_boot or Rooted who want to get B27 OTA, well here is the little guide
- Download stock Recovery from here B20 stock recovery thanks @rczrider and this one ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Go to TWRP, WIPE DATA- CACHE-DALVIK .
- Now make sure SYSTEM was unchecked in mount and check mount system read-only ( THIS IS IMPORTANT DON'T SKIP THIS STEP)
- Flash this file ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Flash stock recovery you downloaded and reboot and you can now safely just Update to B27 via System Update app.
-------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Did this, after AXON screen i am being asked for a password. I tried my backup password but it doesn't work. Was I suppose to turn off lock before attempting a revert to B20 or did I goof somewhere?
lifestar53 said:
Did this, after AXON screen i am being asked for a password. I tried my backup password but it doesn't work. Was I suppose to turn off lock before attempting a revert to B20 or did I goof somewhere?
Click to expand...
Click to collapse
You wipe data? I know is a pain reinstall things but that maybe you issue there.
What about steps to root B27 stock?
I am on B20 stock and haven't update to B27 yet due to waiting to see if Bootloader unlock and root are still possible after b20. Or is it like the old SGS5 days of having to go back to older version, root and then go forward with updates?
DrakenFX said:
You wipe data? I know is a pain reinstall things but that maybe you issue there.
Click to expand...
Click to collapse
I wiped data, dalvick and cache. I ended up letting the phone wipe itself. I'm in now. How do I return to root after updating to B27?
Related
ZVA TOT is out!
Thanks, once again, to our anonymous donor we now have the ZVA TOT. I have also broken down the TOT and uploaded the individual partitions which can be flashed if rooted and custom recovery(TWRP) is installed. Speaking of root it seems the Download Mode root still works with some modifications that l33tlinuxh4x0r figured out... check his thread out for that - http://forum.xda-developers.com/sprint-lg-g3/general/one-click-root-zva-t3141390
Changelog:
Factory Reset Protection
--TOT (*.zip) can be downloaded *HERE*
Flash this TOT using the same method as ZV4/ZV6/etc. You will need to select "Board DL" in LG Flash, otherwise you will get stuck. After the TOT flashes it will reboot your phone into the "MiniOS".. unplug the USB cable and press and hold the power button on the phone then press on the "Normal Boot" option on your phones screen. You are now on stock ZVA.
--Individual ZVA partitions to flash manually can be downloaded *HERE*
*disclaimer -- you can mess your phone up if you do not know what you're doing*
Also, you may need a "bump'd" stock boot.img if you are still running on the old KK bootloader. See my post HERE for a bump'd boot.img.
The ZVA bootloader blocks Bump... do not flash the bootloader img files if you want to use Bump'd files. If manually updating I'd suggest system.img, boot.img, modem.img, tz.img and rpm.img.
To manually flash a partition in TWRP use ADB shell or TWRP's built in terminal to enter the following commands after placing the files on your internal sdcard (changes to commands will be needed if file names change or location of img files changes):
Code:
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
dd if=/sdcard/rpm.img of=/dev/block/platform/msm_sdcc.1/by-name/rpm
dd if=/sdcard/tz.img of=/dev/block/platform/msm_sdcc.1/by-name/tz
(be sure to wipe data in TWRP [wipe button > swipe slider] if coming from an "AOSP-type" rom)
--ZV8-to-ZVA OTA update.zip *NOTYETAVAILABLE*
Anyone have the OTA link? I will assume the manual steps to update w OTA zip still work but as I do not have the phone someone will need to confirm... the steps for zv6 -> zv8 are below and should work the same with zv8 -> zva
You must be on ZV8 and have a stock recovery and stock system partition for this to work.
Directions:
1. Rename downloaded .zip into update.zip
2. Remove USB cable from phone.
3. Power phone off.
4. Press and hold volume down + power until you boot into stock recovery.
5. Select "update with adb"
Code:
adb sideload update.zip
Alternate Directions to skip using ADB (needs microSD card):
1. Format microSD card as EXT4.
2. Rename downloaded .zip to update.zip
3. Move update.zip onto external SD card. EZ way would be to stick SD card in phone then connect phone to PC and use MTP.
4. Power off and boot into stock recovery (vol down + power)
5. Select the Update from SDCARD option.
Alternate Directions to skip using ADB (must have root):
1. Stick OTA zip file in the /cache directory
2. Power off and boot into stock recovery (vol down + power)
3. Select the Update from cache option... then select the update zip you placed in /cache
Click to expand...
Click to collapse
I will make this into a flashable zip tonight for everyone. Much appreciated auto
Changelog
Hey Autoprime,
Only one change in ZVA from ZV8 ?
do we have full changelog ?
swapcall said:
Hey Autoprime,
Only one change in ZVA from ZV8 ?
do we have full changelog ?
Click to expand...
Click to collapse
You can find all changelogs (for every ZV version) HERE
So I've got most of the zip built but I keep running into boot problems. I'm getting past the error when you turn the device on and it's about the boot img not being bumped. So I used the one from the old post. Starts to boot fine but device then goes to LG Security Error. Amy idea?
Changelog
1619415 said:
You can find all changelogs (for every ZV version) HERE
Click to expand...
Click to collapse
it does not mentioned any thing only factory reset protection.
do u have any other link
swapcall said:
it does not mentioned any thing only factory reset protection.
do u have any other link
Click to expand...
Click to collapse
Sprints Page is the Changelog for each Firmware. Even contacting LG, they will say the same thing. There was only one change.
Wait what the hell is ZVA
iiEatTurdz said:
Wait what the hell is ZVA
Click to expand...
Click to collapse
ZVA is a new update that was recently released to fix an issue.
colin0998 said:
ZVA is a new update that was recently released to fix an issue.
Click to expand...
Click to collapse
Well duh but what issues and where's the full comprehensive changelog
I tried installing the system, modem, rpm, and tz images but I get a "Security Error" at boot... I already had the modified boot.img from before.
I don't see a system.img included. I've been checking for the past 12 hours.
Warboy said:
I don't see a system.img included. I've been checking for the past 12 hours.
Click to expand...
Click to collapse
You have to get the system.img from the .tot. He doesn't upload that.
Is There??
Is there a flashable zip out there for this I can flash with twrp?? If I missed it somewher I apologize.
Thanks in advance
Explanation of factory reset protection:
https://nakedsecurity.sophos.com/20...p-5-1-brings-promised-anti-theft-kill-switch/
I should have a system.img up in the next few hours in case anyone's interested. Its gonna be on Dropbox so someone may want to download and re-host it
Sent from my SPH-L710 using XDA Free mobile app
Jguff5 said:
Is there a flashable zip out there for this I can flash with twrp?? If I missed it somewher I apologize.
Thanks in advance
Click to expand...
Click to collapse
Currently trying to build a flushable zip but none of the boot.img's are currently working. It just goes to LG Security Error.
colin0998 said:
Currently trying to build a flushable zip but none of the boot.img's are currently working. It just goes to LG Security Error.
Click to expand...
Click to collapse
I can help (maybe).... Send me a PM if you want me to
colin0998 said:
Currently trying to build a flushable zip but none of the boot.img's are currently working. It just goes to LG Security Error.
Click to expand...
Click to collapse
This is the same issue I'm getting
I'll just put this here. It's not quite ready, but should be in the next couple days
Hi
Yesterday I received the OTA update (LMY48I stagefright-fix) on my unlocked and rooted Nexus 9. When I tried to install it update the tablet rebooted and I ended up with a dead android on screen and the message: "Error". I was able to reboot but the update was not installed. I assume it is because it is rooted that I can't use OTA update.
How do I properly update to LMY48I without risking bricking my device? I have been searching around a bit but I can't seem to find a safe way to do it.
Has anyone experienced similar problems?
Any help is appreciated.
Thanks
Kenneth Andreasen said:
Hi
How do I properly update to LMY48I without risking bricking my device? I have been searching around a bit but I can't seem to find a safe way to do it.
Click to expand...
Click to collapse
OTA failed to install because you were rooted, as you suspected.
I assume that by "unlocked", you mean your bootloader is unlocked?
If so, follow the "Long Method" in the following tutorial (short method, flash_all doesn't work) > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Download your factory image from here > https://developers.google.com/android/nexus/images
cam30era said:
OTA failed to install because you were rooted, as you suspected.
I assume that by "unlocked", you mean your bootloader is unlocked?
If so, follow the "Long Method" in the following tutorial (short method, flash_all doesn't work) > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Download your factory image from here > https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
can i do all that and still keep all my apps and data? im thinking of going to LMy48l too
cobyman7035 said:
can i do all that and still keep all my apps and data? im thinking of going to LMy48l too
Click to expand...
Click to collapse
Yes. Only flash the following files:
bootloader.img
system.img
vendor.img
boot.img.
Note the following:
1) Make sure your Android SDK is reasonable up to date. Google updated fastboot in November 2014, to allow flashing these very large system.img files for Lollipop.
2) IF you are unencrypted, you will need to flash an unencrypted kernel.
3) IF you want to keep root and TWRP, do the following:
- after you fastboot flash the last .img file, stop using your PC/terminal.
- pick up your N9 and using the volume buttons, navigate to hboot and select it with power button.
- once in hboot, use buttons to navigate to and select Recovery
- TWRP will boot. Flash your SuperSU .zip and then reboot from recovery
cobyman7035 said:
can i do all that and still keep all my apps and data? im thinking of going to LMy48l too
Click to expand...
Click to collapse
Have the same situation as you wherein I am unlocked and am rooted. Follow this guide for the respective LMY48I build and you should be fine with no data loss. Just remember to reroot with CF-Auto root afterwards as you will loose root.
http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26
Just wanted to say that I used the Nexus Toolkit (http://www.wugfresh.com/nrt/) to easily flash the stock lmy48i upgrade, then re-root & re-flash my custom recovery. All while preserving my data and apps.
The process was super simple, and the toolkit program even downloads and verifies the stock images for you.
Thanks to @peramikic and @rczrider for fulfilling the request. I will post the compressed unmodified system.img if no one (@Unjustified Dev) beats me to it.
Just a note that I was successful in making my A2017U a stock B20. I first relocked my bootloader, then flashed the 4 images from TWRP. I was then able to reapply B20_boot update.
Keeping the request procedure below for archival purposes:
Code:
Hoping someone is still stock running B20 and willing/able to help. You'll need a micro-SD formatted exFAT with at least 8GB, and working ADB.
Following [URL="http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204"]tenfar's method[/URL], please backup both your stock boot and recovery using axon7backup.
Using axon7root, only apply the recovery included in tenfar's package (-r).
Reboot into recovery (volume up and power button). [U]KEEP READ ONLY! Do not slide the slider to make modifications![/U] Make sure under mount button that Micro SDCard is mounted.
On your PC, use the following commands:
[CODE]
adb shell
cd external_sd/
dd if=/dev/block/sde13 of=system.img
This will take a while as it copies ~6GB to your SD card (at least 10 minutes). When it's done, you should be returned to the prompt.
Using tenfar's method again, restore your recovery backup only. (-r)
Compress that file and upload it somewhere.[/CODE]
jkuczera said:
Hoping someone is still stock running B20 and willing/able to help. You'll need a micro-SD formatted exFAT with at least 8GB, and working ADB.
Following tenfar's method, please backup both your stock boot and recovery using axon7backup.
Using axon7root, only apply the recovery included in tenfar's package (-r).
Reboot into recovery (volume up and power button). KEEP READ ONLY! Do not slide the slider to make modifications! Make sure under mount button that Micro SDCard is mounted.
On your PC, use the following commands:
Code:
adb shell
cd external_sd/
dd if=/dev/block/sde13 of=system.img
This will take a while as it copies ~6GB to your SD card (at least 10 minutes). When it's done, you should be returned to the prompt.
Using tenfar's method again, restore your recovery backup only. (-r)
Compress that file and upload it somewhere.
Click to expand...
Click to collapse
@Unjustified Dev is getting his Axon 7 probably Monday and I told him to give us a hand about pulling system_image from untouched b20 , but if someone else can do it before him that will rock too.
DrakenFX said:
@Unjustified Dev is getting his Axon 7 probably Monday and I told him to give us a hand about pulling system_image from untouched b20 , but if someone else can do it before him that will rock too.
Click to expand...
Click to collapse
That's great to hear. Hopefully it's still B20 My attempt to go back to B20 stock failed on the system image. I really don't want to miss out on the next update!
Would be great if the next one was a full image!
jkuczera said:
That's great to hear. Hopefully it's still B20 My attempt to go back to B20 stock failed on the system image. I really don't want to miss out on the next update!
Would be great if the next one was a full image!
Click to expand...
Click to collapse
After all the jumbo-monbo we have giving them about factory images I bet there's be one for us waiting hehehe well hope so lol,
Probably UDev A7 still on B20 and he can give is a hand on this matte or Anyone else who want to help with this request will be great..
EDIT : @jkuczera
Out of my curiosity, i downloaded the Stock B20 backup from Here which you already have + a2017u b20 (inside there is a boot.img) and what i just did was,
- Move / Copy the System B20 Stock to my TWRP backup directory
- Move / Copy the Boot.img to SDCard (which was inside of the a2017u b20 zip file)
- Boot to TWRP
- Wipe Cache - Dalvik - Data - System ( twice as usual , well for me it is )
- Tap Restore > Select to B20 Stock Folder > Restore System
- Tap Install > Tap Install Image > go to where B20 Stock Boot.img is located > Flash Boot image
- Reboot (here is where i was crossing all my finger hehehe)
- Waited for about 10 min. or so and Booted
NOTE : i don't know if this Stock B20 backup is Untouch / UnModified as you request but , restoring the b20 stock backup + boot.img (Wiping all the above / mention partitions) work for me, WIFI - DATA working by the way and TWRP still bootable either by adb or manually
DrakenFX said:
NOTE : i don't know if this Stock B20 backup is Untouch / UnModified as you request but , restoring the b20 stock backup + boot.img (Wiping all the above / mention partitions) work for me, WIFI - DATA working by the way and TWRP still bootable either by adb or manually
Click to expand...
Click to collapse
Try doing a B20_Boot update; it should fail on verifying system. Otherwise you found the golden ticket.
DrakenFX said:
After all the jumbo-monbo we have giving them about factory images I bet there's be one for us waiting hehehe well hope so lol,
Probably UDev A7 still on B20 and he can give is a hand on this matte or Anyone else who want to help with this request will be great..
EDIT : @jkuczera
Out of my curiosity, i downloaded the Stock B20 backup from Here which you already have + a2017u b20 (inside there is a boot.img) and what i just did was,
- Move / Copy the System B20 Stock to my TWRP backup directory
- Move / Copy the Boot.img to SDCard (which was inside of the a2017u b20 zip file)
- Boot to TWRP
- Wipe Cache - Dalvik - Data - System ( twice as usual , well for me it is )
- Tap Restore > Select to B20 Stock Folder > Restore System
- Tap Install > Tap Install Image > go to where B20 Stock Boot.img is located > Flash Boot image
- Reboot (here is where i was crossing all my finger hehehe)
- Waited for about 10 min. or so and Booted
NOTE : i don't know if this Stock B20 backup is Untouch / UnModified as you request but , restoring the b20 stock backup + boot.img (Wiping all the above / mention partitions) work for me, WIFI - DATA working by the way and TWRP still bootable either by adb or manually
Click to expand...
Click to collapse
Like jkuczera said, the B20_Boot will fail since your system is not hash consistent (and recovery partition in not stock) and so will MR2 OTA . While all the right files are there, they are not in the right order (think file layout on the partition). TWRP can supposedly do a system image backups and if you take it with /system read-only when you run TWRP (i did), it is supposed to be a hash consistent. Restoring it where it get's iffy i guess. You are supposed to mount /system read-only and restore system image so TWRP will not modify it when you are done, but someone said did not restore (could be user error). It is also fastboot flashable but i think the fastboot images we have are limited in payload file size, someone i think tried and got the max payload error. I'll zip mine up and see if i can upload it somewhere once i get home. The image will have stock boot and system and TWRP rec, so all that would be needed is to flash stock rec to get correct sigs.
jkuczera said:
Try doing a B20_Boot update; it should fail on verifying system. Otherwise you found the golden ticket.
Click to expand...
Click to collapse
peramikic said:
Like jkuczera said, the B20_Boot will fail since your system is not hash consistent (and recovery partition in not stock) and so will MR2 OTA . While all the right files are there, they are not in the right order (think file layout on the partition). TWRP can supposedly do a system image backups and if you take it with /system read-only when you run TWRP (i did), it is supposed to be a hash consistent. Restoring it where it get's iffy i guess. You are supposed to mount /system read-only and restore system image so TWRP will not modify it when you are done, but someone said did not restore (could be user error). It is also fastboot flashable but i think the fastboot images we have are limited in payload file size, someone i think tried and got the max payload error. I'll zip mine up and see if i can upload it somewhere once i get home. The image will have stock boot and system and TWRP rec, so all that would be needed is to flash stock rec to get correct sigs.
Click to expand...
Click to collapse
what actually fails when i try to apply the zip using Stock Recovery is when check for boot, which System been the first partition to check and pass, boot.img i'm using is the one from tenfar for the whole reason of booting, but what i didn't Test was using a Full stock Boot.img even if i don't boot but to see if pass,
omw to try that report back,
DrakenFX said:
what actually fails when i try to apply the zip using Stock Recovery is when check for boot, which System been the first partition to check and pass, boot.img i'm using is the one from tenfar for the whole reason of booting, but what i didn't Test was using a Full stock Boot.img even if i don't boot but to see if pass,
omw to try that report back,
Click to expand...
Click to collapse
The first check you pass is the fingerprint, which is fine since you have restored stock system. The comes the sha1 check for boot, recover and system. You failed the hash check on the boot partition. Was the boot.img root mod one? that's not going to work.
What's the best way to pull it.... I got mine today. I haven't touched anything.
Sent from my ZTE A2017U using Tapatalk
shoman94 said:
What's the best way to pull it.... I got mine today. I haven't touched anything.
Click to expand...
Click to collapse
Check the OP. I can give you a place to upload to if you need it.
shoman94 said:
What's the best way to pull it.... I got mine today. I haven't touched anything.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Just like JK said in first post, dump your boot and recovery with tenfars tool, then flash modded TWRP only. Make sure you stay in read only in TWRP on the first prompt
I would the do full TWRP backup including system image. then use the dd command above to dump /system part by itself.
Put it all on SD Card. Then flash back the stock recovery with tenfar's tool. You will have the stock backup of main partitions and phone ready for the MR2 OTA.
The main quirk of course is that the current BL unlock zip will most likely not work after MR2 OTAs until someone requests one. So trick is to see if the MR2 can be flashed with BL unlocked but going back to B20 boot, system and recovery
jkuczera said:
Check the OP. I can give you a place to upload to if you need it.
Click to expand...
Click to collapse
Yea, kinda ballsy.... I'll think about it. I can't afford to mess something up at the moment. Lol
Sent from my ZTE A2017U using Tapatalk
peramikic said:
The first check you pass is the fingerprint, which is fine since you have restored stock system. The comes the sha1 check for boot, recover and system. You failed the hash check on the boot partition. Was the boot.img root mod one? that's not going to work.
Click to expand...
Click to collapse
@jkuczera
yeah i take all that back, fails after 40% system fault , was turning things around getting apply from sdcard using stock recovery to work but well we need that system_img unmodified then ...
@jkuczera @DrakenFX check your PM
peramikic said:
@jkuczera @DrakenFX check your PM
Click to expand...
Click to collapse
check your PM
DrakenFX said:
check your PM
Click to expand...
Click to collapse
Done, also check this link on how it should be used
https://github.com/Lrs121/android_resources/wiki/Take-OTA-on-Block-Devices
peramikic said:
Done, also check this link on how it should be used
https://github.com/Lrs121/android_resources/wiki/Take-OTA-on-Block-Devices
Click to expand...
Click to collapse
got it thanks man,
DrakenFX said:
@Unjustified Dev is getting his Axon 7 probably Monday and I told him to give us a hand about pulling system_image from untouched b20 , but if someone else can do it before him that will rock too.
Click to expand...
Click to collapse
I have the system.img 6.4GB I did modified my system file a bit by installing busybox...
Is it ok for you?
If yes I will upload it through MEGA
manu7irl said:
I have the system.img 6.4GB I did modified my system file a bit by installing busybox...
Is it ok for you?
If yes I will upload it through MEGA
Click to expand...
Click to collapse
Needs to be 100% unmodified to pass signature checks. Thanks though!
I@jkuczera I can get back to stock with the untouched twrp backup, then save it for you.
I just restored my system patition from the B20 untouched twrp backup.
But still, I first restored the default recovery then made a factory rest. Then I flashed twrp again also made a format data, then backed up my current system and restored the system backup form the untouched B20.
but still after reboot twrp is asking for a password... I'm on twrp 3.0.2-2.
If I do:
Code:
do if=/dev/zero of=/dev/block/bootdevice/by-name/userdata bs=1m
This will be completely wipe the data partition...
Am I right? @DrakenFX
Could it help with this F***ing encryption??
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
joaomPT said:
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
Click to expand...
Click to collapse
As you are already familiar with adb and other stuff so will write a short post for you.
To download latest firmware, head to
http://forum.xda-developers.com/hon...tock-firmware-packages-honor-7-t3448747/page1
Google, download and install Huawei update extractor and open UPDATE.APP in it (obtained after extracting firmware).
You can see all the images. Just extract recovery and boot to platform-tools folder.
Meantime, do the unlocking command again, with
Fastboot OEM unlock xxxxxxxxxxxxxxxx
Followed by fastboot reboot
And press and hold the vol down button again until you reboot in bootloader.
Flash the recovery and boot you extracted using
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
(I got a habit of extracting and flashing system and Cust using
Fastboot flash system system.img
Fastboot flash Cust Cust.img
But they are not necessary)
Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again).
Please do report back if it comes to life.
To root, just flash twrp and then use SuperSU 2.62 (no other version) and update it later using play store.
Sent from my PLK-L01 using XDA Labs
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
joaomPT said:
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
Click to expand...
Click to collapse
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
muradulislam said:
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
joaomPT said:
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
Click to expand...
Click to collapse
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said » version 2.62 «
I cant thank you enough!! Can I pay you a coffee?
Thank you!
joaomPT said:
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said �?�» version 2.62 �?�«
I cant thank you enough!! Can I pay you a coffee?
Thank you!
Click to expand...
Click to collapse
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
You can find him somewhere in this thread
http://forum.xda-developers.com/honor-5x/help/honor-5x-kiw-ul00-boot-loop-t3449554/page1
Decision is yours
muradulislam said:
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
Whichever you like...
Click to expand...
Click to collapse
Alright man, cheers
joaomPT said:
Alright man, cheers
Click to expand...
Click to collapse
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
joaomPT said:
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
Click to expand...
Click to collapse
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
tgergo said:
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
Click to expand...
Click to collapse
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
I'll try... But seems too simple to be true...
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
Hi again,
I'm doing this OS installation now. It starts fine but stucks at 90%, (I'm trying to install the latest stock ROM which can be downloaded from Huawei site, B220 or221). Did you have the same issue? I waited more than half an hour at 90% but did not go on.
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Maybe formatting, Flash stock Android 5 recovery using Honor multitool , and then Flash a Android 5 firmware
Not sure it Will Work without rollback..
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
tgergo said:
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
Click to expand...
Click to collapse
Is this really work? i cant rollback to any version.
Yuaru said:
Is this really work? i cant rollback to any version.
Click to expand...
Click to collapse
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
tgergo said:
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
Click to expand...
Click to collapse
Thanks for the answer. Im gonna try this method. I can't reflash any region rom.
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!