Related
This is a build at a really early stage so take care !
Ok, so the method I propose is absolutely non intrusive. You might want to flash the recovery you'll find here-under but I personally haven't done it so feel free to go first Flashing back the original recovery shouldn't be a big deal anyway.
Prerequisite
You should have installed:
K910 ADB Driver (available on the CD that appear when you connect the device)
ADB
Fastboot
Rooting
So the method is pretty easy:
Download the latest SuperSU update.zip and put it at the root of your Internal SD Card
(Optional) Download Google Apps for Android 4.2.2 (thanks to TeamAndroid) and put it at the root of your Internal SD Card
Download the recovery.img (build 140205)
un-7zip it
Restart your device in the bootloader:
Code:
adb reboot-bootloader
Boot your phone into the ClockworkMod recovery:
Code:
fastboot boot cwm_recovery_custom.img
Install zip, wipe partition, backup/restore, adb sideload, ...
Reboot
The phone is left untouched except for the zip you flashed.
Update on the 6th of February (Build 140205):
Bigger font
/sdcard mounted on the first user's internal storage (= symlink /sdcard /data/media/0)
Makes use of the latest kernel
The old recovery.img stays available.
For those who would be stuck on K910_SS_S_2_040_0039_131101, I posted the official update.zip here
How to build my own recovery
If you are curious about building the recovery, I'll post here a few tips.
First of all, you'll need a good tutorial like the one on XDA University. The steps are the following:
Prepare your OS to receive a cyanogenmod repository. I would advice an Ubuntu so you can following this guide. Note that this is for a plain Android so you need to stop following it when they issue the first repo command
Then you need to carefully read this guide on porting CyanogenMod ROM. You don't need to build the full system (which is a completely other story) but only the recovery. I prepared the vendor directory for you (base on LG Optimus and a lot of research).
The building happens according to this guide.
You could be done by now if it wasn't for the dtb. If you try to boot your recovery as is, fastboot will complain about it. You'll find other people having the same issue, just follow their solution.
csu333 said:
This is a build at a really early stage so take care !
Ok, so the method I propose is absolutely non intrusive. You might want to flash the recovery you'll find here-under but I personally haven't done it so feel free to go first Flashing back the original recovery shouldn't be a big deal anyway.
So the method is pretty easy:
Download the recovery.img
un-7zip it
Restart your device in the bootloader:
Code:
adb reboot-bootloader
Boot your phone into the ClockworkMod recovery:
Code:
fastboot boot recovery-clockwork-6.0.4.6-kiton.img
Install zip, wipe partition, backup/restore, adb sideload, ...
Reboot
The phone is left untouched except for the zip you flashed.
More precisions to come in a next edit.
Click to expand...
Click to collapse
Yess!!! Thanks!!!
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
What rom version did you have when boot .img?
cwm (loki) .img from lg g2 says ok afterall, but phone restarts after showing me a nice blue line .
take a look https://gitlab.com/itsmikeramsay/mkbootimg/tree/master and this http://looollll.doorblog.jp/archives/29337755.html and this http://forum.xda-developers.com/showthread.php?t=2469510
I believe this really may be helpful to you http://forum.xda-developers.com/showthread.php?t=2073775
katalinscrob said:
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
QUOTE]
Same result for me too.
Click to expand...
Click to collapse
katalinscrob said:
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
What rom version did you have when boot .img?
cwm (loki) .img from lg g2 says ok afterall, but phone restarts after showing me a nice blue line .
take a look https://gitlab.com/itsmikeramsay/mkbootimg/tree/master and this http://looollll.doorblog.jp/archives/29337755.html and this http://forum.xda-developers.com/showthread.php?t=2469510
I believe this really may be helpful to you http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
I have K910_SS_S_2_040_0109_131226 but it shouldn't be an issue anyway. This sounds like I uploaded the wrong recovery (I have so many) because "dtb not found" is the message you receive when, well, the DTB doesn't appear in the recovery. Adding the DTB is the very last step to build the recovery.
Try this one instead.
Just for your information, note that following the guide I mentioned earlier did work but I have to add a custom init.rc because there was no backlight on the screen.
csu333 said:
I have K910_SS_S_2_040_0109_131226 but it shouldn't be an issue anyway. This sounds like I uploaded the wrong recovery (I have so many) because "dtb not found" is the message you receive when, well, the DTB doesn't appear in the recovery. Adding the DTB is the very last step to build the recovery.
Try this one instead.
Just for your information, note that following the guide I mentioned earlier did work but I have to add a custom init.rc because there was no backlight on the screen.
Click to expand...
Click to collapse
Other possible root???
http://lenovobbs.cnmo.com/thread-14620407-1-1.html
sakilxda said:
Other possible root???
http://lenovobbs.cnmo.com/thread-14620407-1-1.html
Click to expand...
Click to collapse
I honestly doubt it: all the 1 click root I've seen until know are based on a bug in the backup mechanism that have been fixed for a while now. But since it seems pretty recent, anything is possible. I can't confirm since I'm rooted now
Right now with this method, and when I get my Lenovo steps that I can do?
Update first and then use this method to root?
I do not understand English, use google translate, and as I see there seems to be no problems?
Still it take at least 2 weeks to receive it and I'm sure there will be changes and improvements ...
Thanks again for sharing your experiences.
Big thanks button should be available too...
Managed to boot in cwm, root from cwm (btw very nice option ), Gapps full reinstall and finally a backup. EVRIKA! YOU DID IT ! Respect man ! permanent img flash would be next step I assume...
sakilxda said:
Right now with this method, and when I get my Lenovo steps that I can do?
Update first and then use this method to root?
I do not understand English, use google translate, and as I see there seems to be no problems?
Still it take at least 2 weeks to receive it and I'm sure there will be changes and improvements ...
Thanks again for sharing your experiences.
Click to expand...
Click to collapse
You're right: best method is to upgrade then root with this method. If it seems difficult to get the upgrades, I can post the zip files (it took me more than a week to get the first one).
katalinscrob said:
Big thanks button should be available too...
Managed to boot in cwm, root from cwm (btw very nice option ), Gapps full reinstall and finally a backup. EVRIKA! YOU DID IT ! Respect man ! permanent img flash would be next step I assume...
Click to expand...
Click to collapse
You're very welcome
Well, actually, there should be no problem flashing this recovery, it's just that it could break the OTA process (and that I haven't tested it myself yet)
So next step after testing is to find a way to make this menu readable. I mean, I almost need a magnifying glass to read it :laugh:
It isn't really an issue, maybe to correct the dafult push backup folder to internal sdcard clockworkmod instead of root folder (mnt...). I suppose that until seriously modded ROM's will appear it's best to mantain non flashed anyway for the OTA capability IMHO. Anyway, very nice job, put a paypal to receive some beers from us.
I still cannot install zips (SuperSU / gapps) from recovery, though recovery.img was flashed without any error. Am I missing anything?
Hello friends, you have seen this guide?
http://lenovo-forums.ru/topic/4131-...-lenovo-vibe-z-k910-пока-только-wcdma-версия/
sakilxda said:
Hello friends, you have seen this guide?
http://lenovo-forums.ru/topic/4131-...-lenovo-vibe-z-k910-пока-только-wcdma-версия/
Click to expand...
Click to collapse
It is based on csu333's work. I linked thid thread to russian fellows.
katalinscrob said:
It is based on csu333's work. I linked thid thread to russian fellows.
Click to expand...
Click to collapse
Ok, just thought it was a copy
nlohani said:
I still cannot install zips (SuperSU / gapps) from recovery, though recovery.img was flashed without any error. Am I missing anything?
Click to expand...
Click to collapse
Are you sure you are in the custom recovery? The Lenovo one look similar but doesn't have the clockwork mod logo in the background. It lets you install zip...as long as they are signed by Lenovo.
csu333 said:
Are you sure you are in the custom recovery? The Lenovo one look similar but doesn't have the clockwork mod logo in the background. It lets you install zip...as long as they are signed by Lenovo.
Click to expand...
Click to collapse
You are right, after re-flashing your recovery I was able to install SuperSU.zip, but still couldn't find it in the device.
Just to share further-
1. Titanium backup still fails to get root access
2. One root checker application says my device is rooted, but 'rescue root checker' says it is not
katalinscrob said:
It isn't really an issue, maybe to correct the dafult push backup folder to internal sdcard clockworkmod instead of root folder (mnt...). I suppose that until seriously modded ROM's will appear it's best to mantain non flashed anyway for the OTA capability IMHO. Anyway, very nice job, put a paypal to receive some beers from us.
Click to expand...
Click to collapse
Good suggestions. I'll take a look.
Now that I know what it takes to build a recovery, I'll think twice before starting a project of a really modded ROM
nlohani said:
You are right, after re-flashing your recovery I was able to install SuperSU.zip, but still couldn't find it in the device.
Just to share further-
1. Titanium backup still fails to get root access
2. One root checker application says my device is rooted, but 'rescue root checker' says it is not
Click to expand...
Click to collapse
I 've had the same behavior with the oldest ROM. This is why I provided a custom ROM with busybox installed even if I knew most people wouldn't need it. It was just impossible to install it afterwards. It might then be version related. Which version are you running?
Hello,
somehow I had a problem that many apps force closed after doing something, so I tried flashing opengapps - worst idea. I started the phone and nothing worked because I always get force close on Setup Assistent.
I were on Cydras Rom (https://forum.xda-developers.com/le-pro3/development/rom-google-edition-cydras-t3514742). So now I tried overflashing it again but somehow it says successfully installed and also "cant unmount system: volume not found". The system image is now about 900mb big, the zip 1.3gb - can't be possible. It doesn't but and stuck on the first Leeco screen. Now I tried sideload: failed - invalid command..
Well, I tried getting another rom and put it on phone by MTP in TWRP.. Same problem - TARS causes boot into Recovery and CM13 by Superluminal doesn't even flash: stuck on "patching system image unconditonally".
Has someone a solution or more like is there any system image I can flash through fastboot?
Or could someone make one? PLEASE!
I think somehow the system can't be mounted...
Probably flashing stock ROM jacked your phone into locked system.
Are you able to fastboot flash/boot TWRP?
If yes, try to copy the official firmware zip by renaming it to update.zip and putting it into internal storage.
Next you have to flash stock recovery from fastboot, reboot into recovery right away and then apply update. If you succeed you should have a working back-to-stock.
You didn't mention if u have x727 or x720? And you didn't mention what possible "something" u did which jacked up your apps to FCs. Looks like a kernel level modification to me...
Have u tried the bootloader unlock checking command?
Somehow I tried this twrp backup: https://forum.xda-developers.com/le-pro3/how-to/le-pro-3-lex727-twrp-backup-eui-5-8-019s-t3504761
Now I can't mount storage, because it's encrypted... -.-
I have x720 and I don't really know what caused the FCs, the last I remember was uninstalling Android WebView.
Now I have to try to get access to storage again..
## bootloader is unlocked
dark_prince said:
Probably flashing stock ROM jacked your phone into locked system.
Are you able to fastboot flash/boot TWRP?
If yes, try to copy the official firmware zip by renaming it to update.zip and putting it into internal storage.
Next you have to flash stock recovery from fastboot, reboot into recovery right away and then apply update. If you succeed you should have a working back-to-stock.
You didn't mention if u have x727 or x720? And you didn't mention what possible "something" u did which jacked up your apps to FCs. Looks like a kernel level modification to me...
Have u tried the bootloader unlock checking command?
Click to expand...
Click to collapse
Okay, my internal storage is now lost.. but idc.
I tried getting 20s stock zip and it says "apk not found" in stock recovery..?
Grossoshop ROM is fastboot installable.
Presterin said:
Grossoshop ROM is fastboot installable.
Click to expand...
Click to collapse
Link?
idragonx said:
Link?
Click to expand...
Click to collapse
Sure, here you go: http://blog.grossoshop.net/leeco-x720-grossoshop-rom-italiano-ota/
idragonx said:
Okay, my internal storage is now lost.. but idc.
I tried getting 20s stock zip and it says "apk not found" in stock recovery..?
Click to expand...
Click to collapse
Unlocked bootloader so far so good.
Flash TWRP and try to reformat partitions.
ADB side-load your favorite ROM (make sure to verify MD5 first before side-loading)...
dark_prince said:
Unlocked bootloader so far so good.
Flash TWRP and try to reformat partitions.
ADB side-load your favorite ROM (make sure to verify MD5 first before side-loading)...
Click to expand...
Click to collapse
How to reformat? I tried wiping all & make it ext4 in TWRP.
Sideload doesn't work: * failed to read command: Invalid argument
Advanced wipe > modify or repair file system?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
What appears if u use the 2nd wipe option instead of advanced wipe (the option other than slide to factory reset & Advanced wipe, I forgot it's name but it reformats internal storage as well)
dark_prince said:
Advanced wipe > modify or repair file system?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
What appears if u use the 2nd wipe option instead of advanced wipe (the option other than slide to factory reset & Advanced wipe, I forgot it's name but it reformats internal storage as well)
Click to expand...
Click to collapse
All wipes work, but sideload still doesn't work.
I tried now downloading the grossoshop zip and there is no batch like in the screenshots, so I tried flashing system.img manually out of the zip and I get:
fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Elaborate side load doesn't work.... Is it an error on TWRP? Or you just can't find device while doing "ADB devices"?
Is ADB correctly installed? Is ur device correctly recognized drivers-wise ? Check device manager after enabling side load while ur device is connected via USB....
Which device is it? 720 or 727?
Drivers? Check in device manager after "Swipe to enable side load"
idragonx said:
All wipes work, but sideload still doesn't work.
I tried now downloading the grossoshop zip and there is no batch like in the screenshots, so I tried flashing system.img manually out of the zip and I get:
fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
That's weird, I downloaded it couple of days ago, and it has batch file. Corrupted download?
Presterin said:
That's weird, I downloaded it couple of days ago, and it has batch file. Corrupted download?
Click to expand...
Click to collapse
I used this from the post: https://mega.nz/#!tUkUQJwZ!h3tniWVWlSiYJICadW7MuEdYLDFKfNmNcEOBQ-eL1JM
dark_prince said:
Elaborate side load doesn't work.... Is it an error on TWRP? Or you just can't find device while doing "ADB devices"?
Is ADB correctly installed? Is ur device correctly recognized drivers-wise ? Check device manager after enabling side load while ur device is connected via USB....
Which device is it? 720 or 727?
Drivers? Check in device manager after "Swipe to enable side load"
Click to expand...
Click to collapse
It's x720.
Drivers seems to work in device manager, I can use adb, but on sideload it goes to ~3% and the the error I mentioned comes with invalid argument.
Can I change somehow the maximum system.img size for device? Somehow I need to flash it with fastboot
#####
I GOT IT.
Finally - https://mega.nz/#!VEM1QIYL!HwT9hk7-GA6KZBTRMv0IQ9kleYaG-el63UF21S6P0us
It could do it using fastboot - oh god thanks. Now I try to flash my custom rom.
idragonx said:
It's x720.
Drivers seems to work in device manager, I can use adb, but on sideload it goes to ~3% and the the error I mentioned comes with invalid argument.
Can I change somehow the maximum system.img size for device? Somehow I need to flash it with fastboot.
Click to expand...
Click to collapse
mD5 verified?
Alright try this. Get latest CM13 build from teamsuperluminal website and also get the x720 patch from there too. Then in TWRP (while connected to USB) go to advanced wipe > cache + system + dalvik + data.
Open downloaded CM13 zip in 7-zip file manager, go to META-INF > Android folder and extract only the updater_script file. (Should be in that or in a subwoofer). Keep the 7-zip opened and dont close it.
Open the updater_script file in notepad++ and remove first line which starts with "assert". Save
Then drag drop it back into 7-zip( in the same folder structure.) Close 7-zip after
Enable side load in TWRP
Now side load x720 patch first
Then side load CM13 ROM file u just modified into your phone.
dark_prince said:
Enable side load in TWRP
Now side load x720 patch first
Then side load CM13 ROM file u just modified into your phone.
Click to expand...
Click to collapse
Thank you very much for your help, but finally I found the 18s from grossoshop with the BATCH - it could fastboot load the system.img partially and now it boots <3
Ah sweet. Lol
I couldn't flash CM13 until I tried 5 different methods to get Round patching system lockout...
dark_prince said:
Ah sweet. Lol
I couldn't flash CM13 until I tried 5 different methods to get Round patching system lockout...
Click to expand...
Click to collapse
Well, but I can't flash back my cydras ROM
Imho it should work now to go back to stock. Download official Chinese firmware zip file (not OTA) and rename it to update.zip
Put it in internal storage (not into any folder)
Go to fastboot and flash stock recovery.
Then boot into stock recovery and apply update.zip
Result should be profiting.
idragonx said:
Well, but I can't flash back my cydras ROM
Click to expand...
Click to collapse
HI ALL! With new Rom
VertexOS aims to provide a simple but enhanced near-stock AOSP experience with carefully selected features and an emphasis on stability and smoothness.
what doesn't work ?
everything is working perfectly.
Coming from another ROM, OR if a CLEAN FLASH is required
1) Download the Vertex... .zip file.
2) Download a 7.1 GApps package.
3) Boot into recovery (TWRP)
4) Full wipe (Dalvik Cache, Cache, System, Factory Data Reset)
5) Flash the Vertex... .zip file
6) Flash Nougat-compatible GApps : http://opengapps.org/ / ARM64,7.1,pico
7) Reboot
Download:https://www.androidfilehost.com/?fid=745425885120707303
enjoy!
Credits:
- LineageOS
- AOSPA
- Citrus-CAF
- DU
- PureNexus
- Zephyr-OS
IF YOU LIKE MY WORK PLEASE HIT THANKS .
-IMPORTANT- : To install this rom you must have installed TWRP-3.0.3.0 , download from here https://www.androidfilehost.com/?fid=529152257862697990
To easy install from TWRP recovery :
1- open "install" section.
2- SELECT "install img" in the bottom .
4- Chose the place of TWRP-3.0.3.0.
5- install as RECOVERY , then reboot to recovery.
XDA:DevDB Information
ROM [AOSP + LOS], ROM for the Wileyfox Storm
Contributors
PS-DEV
Source Code: https://github.com/VertexOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP + LOS
Version Information
Status: Stable
Created 2017-02-11
Last Updated 2017-02-20
Received
Received !
Firstly, thanks loads for producing these ROMs it is much appreciated. :good:
I am unfortunately having issues getting both this and your CypherOS rom to work.
After full wipes of everything both roms get stuck on the "Wileyfox powered by Android" boot screen.
I get the same result sideloading via adb and from the internal memory.
I have tried TWRP 3.0.2.0 and older versions, I have also tried old and new Cyanogen recoveries.
I have successfully got the Slimrom 7.1 rom working and the LineageOS 14.1 rom which also works but with many random reboots.
Any thoughts on what I might be missing when flashing your ROMs?
Again many thanks for the work.
Any chance of grabbing your recipe for building this from source? Own personal use only. I have the VertexOS repo cloned. A copy of your roomservice and local manifest would help enormously.
This seems much more stable than Lineage at the moment. Please note you *MUST* use TWRP 3.0.2-1, the non-test version, to install Vertex and a fastboot -w also can't hurt.
Cannot inatall gapps (Wrong Architecture)
Hi,
I installed VortexOS 1.9... but when I tried to install ARM64 7.1 pico Open gapps package then following Error occurs:
"ERROR 64: Wrong architecture to set-up Open GApps pre-bundled busybox"
I use TWRT 3.0.3-0 (kipper)
Any ideas what I made wrong?
best regards, Chuck
Vertex appears to be built as ARMv7, which means 32 bit. Try the 32 bit pico.
I installed fine with the nano apps and 64 bit, no issues
miSAKe said:
Firstly, thanks loads for producing these ROMs it is much appreciated. :good:
I am unfortunately having issues getting both this and your CypherOS rom to work.
After full wipes of everything both roms get stuck on the "Wileyfox powered by Android" boot screen.
I get the same result sideloading via adb and from the internal memory.
I have tried TWRP 3.0.2.0 and older versions, I have also tried old and new Cyanogen recoveries.
I have successfully got the Slimrom 7.1 rom working and the LineageOS 14.1 rom which also works but with many random reboots.
Any thoughts on what I might be missing when flashing your ROMs?
Again many thanks for the work.
Click to expand...
Click to collapse
Check the first post . i have been edit.
Chron0s said:
Any chance of grabbing your recipe for building this from source? Own personal use only. I have the VertexOS repo cloned. A copy of your roomservice and local manifest would help enormously.
This seems much more stable than Lineage at the moment. Please note you *MUST* use TWRP 3.0.2-1, the non-test version, to install Vertex and a fastboot -w also can't hurt.
Click to expand...
Click to collapse
show your PM.
Chron0s said:
Vertex appears to be built as ARMv7, which means 32 bit. Try the 32 bit pico.
Click to expand...
Click to collapse
NO NO
ARM64 ARMv8 .
ChuckeCheese said:
Hi,
I installed VortexOS 1.9... but when I tried to install ARM64 7.1 pico Open gapps package then following Error occurs:
"ERROR 64: Wrong architecture to set-up Open GApps pre-bundled busybox"
I use TWRT 3.0.3-0 (kipper)
Any ideas what I made wrong?
best regards, Chuck
Click to expand...
Click to collapse
1- check to wipe this partitions :
- SYSTEM
- CACHE
- Dalvick-cache.
- DATA
and dont forget to factory reset .
2- first install rom then Gapps. download from here http://bit.ly/2kQf3Le
PS-DEV said:
Check the first post . i have been edit.
Click to expand...
Click to collapse
Thanks again,
Unfortunately I could not get that recovery to work via TWRP 3.0.2.1 or fastboot.
I can flash it but not boot to recovery.
If booting the image directly I get
Code:
FAILED (remote: dtb not found)
I will try building it myself when I get some time.
miSAKe said:
Thanks again,
Unfortunately I could not get that recovery to work via TWRP 3.0.2.1 or fastboot.
I can flash it but not boot to recovery.
If booting the image directly I get
Code:
FAILED (remote: dtb not found)
I will try building it myself when I get some time.
Click to expand...
Click to collapse
You flash via TWRP or fastboot ??
And looking for the method to install TWRP 3.0.3.0 ?
And after chose recovery , you install in "boot" or "reocvery" section ?
PS-DEV said:
You flash via TWRP or fastboot ??
And looking for the method to install TWRP 3.0.3.0 ?
And after chose recovery , you install in "boot" or "reocvery" section ?
Click to expand...
Click to collapse
Both, from TWRP i selected recovery, this flashes but results in recovery not loading.
from fastboot the flash fails, as does booting the image via fastboot.
miSAKe said:
Both, from TWRP i selected recovery, this flashes but results in recovery not loading.
from fastboot the flash fails, as does booting the image via fastboot.
Click to expand...
Click to collapse
The phone boot to rom or not ??
PS-DEV said:
The phone boot to rom or not ??
Click to expand...
Click to collapse
Yes can still boot to Slimrom 7.1 with or without working recovery.
I have reverted to TWRP 3.0.2.1 though.
Thanks for your help.
miSAKe said:
Yes can still boot to Slimrom 7.1 with or without working recovery.
I have reverted to TWRP 3.0.2.1 though.
Thanks for your help.
Click to expand...
Click to collapse
Can you check your bootloader version ?
Because TWRP 3.0.3.0 Needs to kipper-13-.... bootloader
See the photo .
PS-DEV said:
Can you check your bootloader version ?
Because TWRP 3.0.3.0 Needs to kipper-13-.... bootloader
See the photo .
Click to expand...
Click to collapse
Got it kipper-12.1
I reverted to stock recently.
Solved the issue, thank you very much.
miSAKe said:
Got it kipper-12.1
I reverted to stock recently.
Solved the issue, thank you very much.
Click to expand...
Click to collapse
Stock firmware or what? ,, to install version 13 Bootloader , just install any nightly cm13 then back to recovery and install TWRP 3.0.3.0 ??.
Hello,
I have a rooted Oneplus 5 (Android 8.1, OxygenOS 5.1.7) and I'm trying to update it to get the newest version of Oxygen OS.
I found the Firmwares here : https://www.getdroidtips.com/oneplus-5-stock-firmware/
However, when I try to install it via TWRP, I get this
Code:
Updating partition details...
...done
Full SELinux support is present.
Data successfully decrypted
Updating parition details...
...done
MTP Enabled
Installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988.zip
Checking for Digest file...
Skipping Diggest check: no Digest file found
[COLOR="Red"]E:String resource 'zip_compatible_err' not found.
Using default value.
Zup Treble compatibility error!
Invalid zip file format!
Error installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_042_all_1812232102_a034988.zip[/COLOR]
Updating partition details...
...done
After looking around on the internet, I found that it is because my TWRP is outdated.
I tried to download newer versions from the Official TWRP App but when I go to the recovery, I only get a black screen.
I reinstalled this version 3.2.3 : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 but still can't manage to update OxygenOS.
Any help ?
Thanks
Mouchoir said:
Hello,
I have a rooted Oneplus 5 (Android 8.1, OxygenOS 5.1.7) and I'm trying to update it to get the newest version of Oxygen OS.
I found the Firmwares here : https://www.getdroidtips.com/oneplus-5-stock-firmware/
However, when I try to install it via TWRP, I get this
After looking around on the internet, I found that it is because my TWRP is outdated.
I tried to download newer versions from the Official TWRP App but when I go to the recovery, I only get a black screen.
I reinstalled this version 3.2.3 : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723 but still can't manage to update OxygenOS.
Any help ?
Thanks
Click to expand...
Click to collapse
Hello, I can't recommend any guide on outside of xda cause they're not consistent...
Just follow this guide in the first post https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 would help you.
You can't flash twrp 3.3.1 cause you need newer firmware, pie firmware.
Please answer all the questions:
What is you current twrp recovery (file name)?
What is your current Rom(file name)?
What is your magisk version?
Is your storage encryped or decrypted?
Hello and thanks for your answer.
My current TWRP is twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
I am not sure about my ROM's file name
My Magisk version is 19.3 (19300) - Magisk Manager version is 7.3.4 (235) : it says everything's up to date
I think my storage is encrypted since it asks for my password when I start TWRP
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo and use a TWRP that does not ignore the compatibility.zip check: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using an Oreo TWRP if you're on Oreo Firmware/ROM or Pie TWRP if you're on Pie Firmware/ROM) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash xXx No Verity 4.0.zip from here
Reboot
Note: First boot may take some time, so please be patient and wait for it to boot.
Click to expand...
Click to collapse
If I understand correctly from the link you sent me, TWRP doesn't ignore the compatibility.zip check so in order to install OxygenOS 9.0.8 I need to delete this part of the ZIP first ?
Thanks
Mouchoir said:
Hello and thanks for your answer.
My current TWRP is twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
I am not sure about my ROM's file name
My Magisk version is 19.3 (19300) - Magisk Manager version is 7.3.4 (235) : it says everything's up to date
I think my storage is encrypted since it asks for my password when I start TWRP
If I understand correctly from the link you sent me, TWRP doesn't ignore the compatibility.zip check so in order to install OxygenOS 9.0.8 I need to delete this part of the ZIP first ?
Thanks
Click to expand...
Click to collapse
Exactly, delete the compatibility.zip from 9.0.8 rom file and flash it with your current twrp, exactly like in the linked guide for update, not clean flash if you have already a rom above OxygenOS 5.1.4, so please check your OxygenOS version(settings, about).
strongst said:
Exactly, delete the compatibility.zip from 9.0.8 rom file and flash it with your current twrp, exactly like in the linked guide for update, not clean flash if you have already a rom above OxygenOS 5.1.4, so please check your OxygenOS version(settings, about).
Click to expand...
Click to collapse
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho
Mouchoir said:
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho
Click to expand...
Click to collapse
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP
Mouchoir said:
Hello,
Indeed, I have OxygenOS 5.1.7
I have struggle to understand the difference between clean and not clean flash tho
Click to expand...
Click to collapse
Clean flash wipes system and data, so no os, data and settings.
PierreVicquery02 said:
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP
Click to expand...
Click to collapse
Thanks I'll do that. Can I go for the newest version directly or do I have to flash them one by one untill the most recent one ?
Mouchoir said:
Thanks I'll do that. Can I go for the newest version directly or do I have to flash them one by one untill the most recent one ?
Click to expand...
Click to collapse
As I already wrote you: if you are already at 5.1.4 or newer, you can flash 9.0.8
strongst said:
As I already wrote you: if you are already at 5.1.4 or newer, you can flash 9.0.8
Click to expand...
Click to collapse
Better safe than sorry !
I downloaded the version here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
and deleted compatibility.zip from OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip but I still have an issue when installing :
Code:
Data successfully decrypted
Updating parition details...
...done
Successfully decrypted with a default password.
Updating parition details...
...done
Full SELinus support is present.
MTP ENabled
Installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip
Checking for Digest file...
Skipping Diggest check: no Digest file found
Patching system image unconditionally...
E1001 Failed to update system image.
[COLOR="Red"]Updater process ended with ERROR:7
Error installing zip file '/sdcard/Download/OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip[/COLOR]
Updating partition details...
...done
Mouchoir said:
Better safe than sorry !
I downloaded the version here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
and deleted compatibility.zip from OnePlus5Oxygen_23_OTA_051_all_1907311835_5de64c.zip but I still have an issue when installing :
Click to expand...
Click to collapse
Error 7 is corrupt file, you'll find about it here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003/page591
Yeah I can't seem to find the solution. I've tried to use codework's TWRP as stated here : https://forum.xda-developers.com/showpost.php?p=75543048&postcount=3104
I've tried to wipe cache/Dalvik : https://forum.xda-developers.com/showpost.php?p=75079739&postcount=2470
I tried to flash then restart and flash again : https://forum.xda-developers.com/showpost.php?p=75077082&postcount=2416
I just can't seem to find the solution to the ERROR:7
Mouchoir said:
Yeah I can't seem to find the solution. I've tried to use codework's TWRP as stated here : https://forum.xda-developers.com/showpost.php?p=75543048&postcount=3104
I've tried to wipe cache/Dalvik : https://forum.xda-developers.com/showpost.php?p=75079739&postcount=2470
I tried to flash then restart and flash again : https://forum.xda-developers.com/showpost.php?p=75077082&postcount=2416
I just can't seem to find the solution to the ERROR:7
Click to expand...
Click to collapse
With which tool did you remove the compatibility.zip from the rom zip? That's the key usually and explained within the instructions
strongst said:
With which tool did you remove the compatibility.zip from the rom zip? That's the key usually and explained within the instructions
Click to expand...
Click to collapse
As stated here, I used 7zip
PierreVicquery02 said:
If you have TWRP, move the OTA file to the PC, open it with 7zip (NOT WinRAR) and delete the compatibility.zip. Then copy it again to the phone, flash and before rebooting flash a Pie TWRP
Click to expand...
Click to collapse
I re-did all the process and managed to update my OS on the second try.
Now I have an issue trying to put TWRP and Magisk back : I'm following this tutorial https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 but I can't seem to be able to put TWRP.
When my phone is on and connected to the computer,
Code:
adb devices
does see the phone but then when I go into the bootloader and I type
Code:
fastboot devices
nothing happens. When I go for
Code:
fastboot flash recovery recovery.img
it just tells me it's waiting for any device.
I've tried deleting and reinstalling the drivers with the too provided in the thread, but still doesn't work.
Yes because to use fastboot you have to be in fastboot mode...
PierreVicquery02 said:
Yes because to use fastboot you have to be in fastboot mode...
Click to expand...
Click to collapse
Thanks for your answer. I believe I am in fastboot mode/bootloader as I said in my previous message. I've been following this tutorial : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
I just checked on Youtube, this is the screen I am on : https://www.youtube.com/watch?v=4xlmZXgkUrQ
So as I said, once I am on this screen where I can select between START/POWER OFF/RECOVERY MODE/RESTART BOOTLOADER and I type the "fastboot device" command, nothing comes up.
Is this screen not the "Fastboot mode" ?
Mouchoir said:
As stated here, I used 7zip
I re-did all the process and managed to update my OS on the second try.
Now I have an issue trying to put TWRP and Magisk back : I'm following this tutorial https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 but I can't seem to be able to put TWRP.
When my phone is on and connected to the computer,
Code:
adb devices
does see the phone but then when I go into the bootloader and I type
Code:
fastboot devices
nothing happens. When I go for
Code:
fastboot flash recovery recovery.img
it just tells me it's waiting for any device.
I've tried deleting and reinstalling the drivers with the too provided in the thread, but still doesn't work.
Click to expand...
Click to collapse
Mouchoir said:
Thanks for your answer. I believe I am in fastboot mode/bootloader as I said in my previous message. I've been following this tutorial : https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
I just checked on Youtube, this is the screen I am on : https://www.youtube.com/watch?v=4xlmZXgkUrQ
So as I said, once I am on this screen where I can select between START/POWER OFF/RECOVERY MODE/RESTART BOOTLOADER and I type the "fastboot device" command, nothing comes up.
Is this screen not the "Fastboot mode" ?
Click to expand...
Click to collapse
Yes this is fastboot sorry maybe I didn't understand. If you are able to backup your data, use Unbrick tool to update your device
PierreVicquery02 said:
Yes this is fastboot sorry maybe I didn't understand. If you are able to backup your data, use Unbrick tool to update your device
Click to expand...
Click to collapse
I was hoping I could flash TWRP and Magisk without wiping my data
It's weird that when it's on I can see it with "adb devices" and Windows sees it's a Oneplus, but when it's in fastboot I can't with "adb fastboot" and Windows detects an USB but can't say what it is.
I feel its a driver issue but can't figure it out
Mouchoir said:
I was hoping I could flash TWRP and Magisk without wiping my data
It's weird that when it's on I can see it with "adb devices" and Windows sees it's a Oneplus, but when it's in fastboot I can't with "adb fastboot" and Windows detects an USB but can't say what it is.
I feel its a driver issue but can't figure it out
Click to expand...
Click to collapse
That's such a strange bug. If you are in fastboot, it's impossible for your PC to recognize it in ADB mode. Try with another computer or use unbrick tool to clean your phone (it installs Oxy 9.0.8)
Well I managed to see the fastboot thanks to the EOM cable but I think I bricked my phone
Hi!
I'm trying to install an update of OxygenOS. I wanted to install this with a .zip folder via my TWRP custom recovery (TWRP 3.2.3-0). However, I'm still having an issue with every ROM that I'm trying to install: "Invalid zip file format!", following by: " Error installing zip file 'OxygenOS.zip' ".
I precise that I have this issue with every .zip ROM that I'm trying to install...
I actually don't have any ROM installed on my OP5, so I can't boot right now.
I'm only fighting with my TWRP recovery and my Bootloader !
The Android version I had before that was Android 7.1.1( old boy...)
I'd be pleased if someone could help me solving this issue...
Have a nice day & Thx !
SkyZFr said:
Hi!
I'm trying to install an update of OxygenOS. I wanted to install this with a .zip folder via my TWRP custom recovery (TWRP 3.2.3-0). However, I'm still having an issue with every ROM that I'm trying to install: "Invalid zip file format!", following by: " Error installing zip file 'OxygenOS.zip' ".
I precise that I have this issue with every .zip ROM that I'm trying to install...
I actually don't have any ROM installed on my OP5, so I can't boot right now.
I'm only fighting with my TWRP recovery and my Bootloader !
The Android version I had before that was Android 7.1.1( old boy...)
I'd be pleased if someone could help me solving this issue...
Have a nice day & Thx !
Click to expand...
Click to collapse
Hello, you need to clean flash 5.1.4, then ota update to 9.0.9 and then flash twrp from PC again with root.
See here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 including last pages where it's been explained a lot
strongst said:
Hello, you need to clean flash 5.1.4, then ota update to 9.0.9 and then flash twrp from PC again with root.
See here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 including last pages where it's been explained a lot
Click to expand...
Click to collapse
what do you mean by " clean flash 5.1.4 " ? Android 5.1.4 ? or Oxygen ?
thx
SkyZFr said:
what do you mean by " clean flash 5.1.4 " ? Android 5.1.4 ? or Oxygen ?
thx
Click to expand...
Click to collapse
I mean OxygenOS 5.1.4
strongst said:
I mean OxygenOS 5.1.4
Click to expand...
Click to collapse
I tried so much, but actually I really can't flash nothing...
I'm now having : "Updater process ended with ERROR: 4"
I also had ERRO 7 from TWRP, but I tried everything, like changing a part of the code of one script of the ROM, but nothing is working.