Since huawei started to mess around with online firmwares that twrp couldn't handle I decided to create my own offline package with updated firmware(s) and i thought why not create a offline package thread with latest firmwares in it.
This case we can always keep ourself up to date (system wise) without having to restore to stock recovery etc.
However this is a "dirty" way of update firmware and it will only update following partitions:
Boot
Cust
Product
System
Vendor
Version
All other partitions will stay intact! Why? Because if we add other partitions there's a HIGH potential of hard brick the device and I mean really high!
But with official packages it updates all partitions!
Yes. And we can't (for now, or never) re create this procedure we'd have to know how the UPDATE.APP is being built and we can't re create a UPDATE.APP for now.
So far only available homebrewed package is 394 created by me.
See post 2 on how to create your own custom offline package!
Downloads:
FRD-L09C432B934
https://mega.nz/#!j0QXjJKa!i5lOMYjO_GusfzCTT6qVAR7LgzVGdpLT4i66FKCrshQ
blackbuffalo said:
Here is Offline fw for L04C567B385 thanks @blackbuffalo
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
Click to expand...
Click to collapse
Thanks @SnoopHTC
L19-C432B398
https://gofile.me/3wKsh/4wlivV41v
Nortonko said:
so coz the link from SnoopHTC is dead i made my own package for FRD-L19C432B398. Here is the link: https://webshare.cz/file/73v2t363K5/twrp-frd-l19c432b398-zip
Click to expand...
Click to collapse
How to do it yourself package.
In order to create a unofficial update package you'll need
Huaweiupdateextractor (google it)
Simg2img (google it)
This template
https://mega.nz/#!i1Y3Wa5J!VfELb8aRkA5bon_OlIRPNAS_xUAmzMq0I-rVywHbvi4
Now extract all needed partitions
Boot
System
Vendor
Product
from big update file
cust
version
from small update file *this can be found in any of the 2 extra small zips
Open cmd and navigate to the folder where you have to both simg2img and your system files. Now cd into your work directory to convert the images.
Simg2img.exe system.img s.img will give you a converted system image with the name s.img
Convert these following partitions
system
Product
Version
Cust
Vendor
Once completed check the update-script
The
c.img is cust
v.img is vendor
ve.img is version
p.img is product.
b.img is boot
s.img is system
you can change these names to its regular name like system.img for system or make it more confusing if you want [emoji14]
Make sure the partitions are exactly the same!
If you decide you want to change the name of the files from s.img to system.img make sure you do it correct!
Because system.img in updater-script is not the same as System.img in root of zip. If you have a captive letter in root and not in updater-script the zip will fail to flash.
Now simply compress the images into a zip and you're done.
Note: after you flashed your offline zip make sure to patch boot! Else it will reboot to recovery
Note you'll get result
Error: Unknown command []] this is not a issue since we're using stock huawei updater binary.
Sent from my FRD-L09 using Tapatalk
Your awesome work will save a lot :good:
Nice but it should not be in "roms etc" threads? More people will find it.
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
WYPIERDAALAAC said:
Nice but it should not be in "roms etc" threads? More people will find it.
Click to expand...
Click to collapse
Because I simply put it here
extpumajl said:
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
Click to expand...
Click to collapse
Hmm you might have to patch boot after flash??
PalakMi said:
Your awesome work will save a lot :good:
Click to expand...
Click to collapse
It will save a lot of time yes.
Sent from my FRD-L09 using Tapatalk
extpumajl said:
I get bootloop into eRecovery after flashing. Restored my backup of B392 and now in the phone info i have as build name FRD-L09C432B394, what can't be true, because it wasn't successfully flashed. Anyway local.prop was edited and not restored
Click to expand...
Click to collapse
I have the same problem..
Bootloop into eRecovery, restored a Backup of b389 but build is b394 [emoji28]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem FRD-L09 mit Tapatalk
LastStandingDroid said:
Hmm you might have to patch boot after flash??
Click to expand...
Click to collapse
What schould i do?
Rommco05 said:
I can't find simg2img version which works on Windows 10. One version shows me only
Using STDIN as input
Using STDOUT as output is that right?
Maybe don't know how use this program
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/dev-simg2img-windows-t3156459
This one works just great.
I forgot you might have to use a cmd to convert images will edit post 2
Silencer3007 said:
I have the same problem..
Bootloop into eRecovery, restored a Backup of b389 but build is b394 [emoji28]
View attachment 4250767
Gesendet von meinem FRD-L09 mit Tapatalk
Click to expand...
Click to collapse
Patch boot with either Supersu or magisk.
Did the backup include version? I doubt which is why you'll get B394 in settings.
It doesn't restore the partition which contains the build number info.
extpumajl said:
What schould i do?
Click to expand...
Click to collapse
Patch boot and try again
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Patch boot and try again
Click to expand...
Click to collapse
Thx. Now is everything fine.
Didn't work for me since the simg2img tool wouldn't let me convert the BOOT.IMG. I was getting a "no magic" message (which I didn't notice at the beginning) and a 0KB BOOT file output. Funny thing I just realized this after trying to unsuccessfully flash the custom update zip.
So after some researching and reading (a couple of hours actually) I managed to flash the L19C432_B398 update by flashing the original extracted SYSTEM, BOOT, and CUST images through Fastboot command. Then by going into TWRT recovery to flash the simg2img converted PRODUCT, VENDOR, and VERSION images through ADB push command to their appropriate dev partitions which are available inside the updater-script. Finally, I did a dalvik/cache wipe and reboot.
So far so good.:fingers-crossed:
*Forgot to mention that my device is a US L14C567 rebranded to L19C432.
Dominikrod said:
Didn't work for me since the simg2img tool wouldn't let me convert the BOOT.IMG. I was getting a "no magic" message (which I didn't notice at the beginning) and a 0KB BOOT file output. Funny thing I just realized this after trying to unsuccessfully flash the custom update zip.
So after some researching and reading (a couple of hours actually) I managed to flash the L19C432_B398 update by flashing the original extracted SYSTEM, BOOT, and CUST images through Fastboot command. Then by going into TWRT recovery to flash the simg2img converted PRODUCT, VENDOR, and VERSION images through ADB push command to their appropriate dev partitions which are available inside the updater-script. Finally, I did a dalvik/cache wipe and reboot.
So far so good.:fingers-crossed:
*Forgot to mention that my device is a US L14C567 rebranded to L19C432.
Click to expand...
Click to collapse
I'm curious but where did it say convert boot?
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
I'm curious but where did it say convert boot?
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Dominikrod said:
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Click to expand...
Click to collapse
Ah no its just that it has to flash boot as well ?
Sent from my FRD-L09 using Tapatalk
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
Dominikrod said:
It's all in my head! LOL
I got confused when I saw the part where it talks about the updater-script file naming. When I saw b.img thought that BOOT needed to be converted as well.
Thanks for pointing that out. :good:
Click to expand...
Click to collapse
No need convert Boot.img, just rename then put it into zip
blackbuffalo said:
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
No need convert Boot.img, just rename then put it into zip
Click to expand...
Click to collapse
Great that you contribute ?
Sent from my FRD-L09 using Tapatalk
blackbuffalo said:
Here is Offline fw for L04C567B385
Just tested on my device
https://androidfilehost.com/?fid=961840155545591339
No need convert Boot.img, just rename then put it into zip
Click to expand...
Click to collapse
Bro can you confirm the build number is not NRDm keys ?
venugopalu007 said:
Bro can you confirm the build number is not NRDm keys ?
Click to expand...
Click to collapse
It won't unless he packed the product files which stores the build info
Sent from my FRD-L09 using Tapatalk
venugopalu007 said:
Bro can you confirm the build number is not NRDm keys ?
Click to expand...
Click to collapse
it not imcluded
blackbuffalo said:
it not imcluded
Click to expand...
Click to collapse
Ok,then it shows build number correctly?
Related
I'm trying manually install 4.1.2 on my rooted Nexus 7 with CMW.
I downloaded the zip, placed it on my Nexus 7, proceeded regularly to install zip
i selected the zip and it aborted, says Status 7.
Thanks to the community below are solutions to get the update to flash.
EDIT
Thanks to Logic_
You can flash this .zip instead which disables all the checks but do it at your own risk as it can brick your tablet
https://www.dropbox.com/s/isqpvb0w26....1.2edited.zip
This is the update with the checks disabled. I didn't make this, got it off another forum, I just used it because I had moved an update to chrome into my /system and there was no easy way to revert it.
I wouldn't advise using this if you made build.prop modifications, but it is useful if your update is failing over some apps like google wallet.
Once again, I didn't make this and I'm not responsible if you for some reason use this to flash the update over some heavily modded rom
It's from JRO03D btw.
Click to expand...
Click to collapse
EDIT 2
osm0sis method to get the update to work is simpler and possibly risk free.
osm0sis said:
For those who've done some modding and can't remember what they did to pass the OTA asserts, all you need to do is dirty flash the system.img from 4.1.2 factory image in fastboot and eveything should work.
Click to expand...
Click to collapse
Did you try to redownload the zip?
Sent from my Nexus 7 using xda app-developers app
I got a similar error for build.prop file. I had changed it to enable/force auto rotation of the home screen when I was on 4.1.1. When I reverted the build.prop to its original file, it worked for me.
I see the error code is the same in your case as well. Is there a chance that you would have changed BrowserProviderProxy.apk?
mayoor_rao said:
I got a similar error for build.prop file. I had changed it to enable/force auto rotation of the home screen when I was on 4.1.1. When I reverted the build.prop to its original file, it worked for me.
I see the error code is the same in your case as well. Is there a chance that you would have changed BrowserProviderProxy.apk?
Click to expand...
Click to collapse
I didn't edit it which is weird, I don't think this matters but I did sideload aosp browser as I'm not a fan of chrome
Sent from my Nexus 7 using Tapatalk 2
Sebianoti said:
I didn't edit it which is weird, I don't think this matters but I did sideload aosp browser as I'm not a fan of chrome
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It's from the side loading of the browser. I had this too. You have to restore those mentioned browser proxy file(s) to their original state. I also temporarily removed the browser apk from the system/app folder as well, although I'm not sure if this was required. The update installed fine after doing this.
Sent from my Nexus 7 using XDA Premium HD app
nyijedi said:
It's from the side loading of the browser. I had this too. You have to restore those mentioned browser proxy file(s) to their original state. I also temporarily removed the browser apk from the system/app folder as well, although I'm not sure if this was required. The update installed fine after doing this.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Oh okay, how would I restore those files to their original state though?
Sent from my Nexus 7 using Tapatalk 2
I'm having the same problem. I cannot seem to flash the update with CWM. I haven't edited any of the system files or anything like that. Is it the fact that I'm using a different launcher that's causing the problem?
Sebianoti said:
Oh okay, how would I restore those files to their original state though?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'd like to know too. I get the Build.prop error too.
You've made no changes whatsoever? What about the kernel? Worst case just use mskip's toolkit to flash back to stock 4.1.1. Check the lag thread I posted what I did and it worked like butter.
Sent from my Nexus 7 using xda premium
Hi all.....
I'm currently using stock Nexus 7 and did all ways possible here to update and nothing worked, last thing I did was go to setting, backup and restore and hit factory data reset and buala automatically got the update to 4.1.2
Nota: this is not a recommendation but if u wanna try do a Backup and good luck.
Sent from my Nexus 7 using xda premium
I deleted the original browser files in the system/app folder too.
Found them on the rootwiki site here....
http://rootzwiki.com/topic/35089-can-someone-hook-me-up-with-browserproviderproxyapk/
Worked perfectly after
modded build.prob / update problems to 4.1.2
i have similar Problem
Picture
h**p://i49.tinypic.com/w979qt.jpg
i modded my build.prob to Landsape mode. I guess that i corrupt the Md5 hash
(deleting the row with the added contend didnt solve it....)
I tried a factory reste and an Temp Wipe in clockwork. I thought this should solve the problem but i l get the sam error ....
What should i do ?
Flash a facotory Image ?
How do i get back my root, if the factory image is my only option?
Thanks a lot for your help
greets Razzor
I also had the same problem then remembered that I use FullScreenToggle to get rid of the nav bar. I just had to re-enable it and it installed fine.
If you are getting the error on 'build.prop' look in the /System folder with Root Explorer or the ES explorer. If you see a build.prop.bak, that is probably your original file. Rename build.prop to something else and rename build.prop.bak to build.prop. Restart and then try taking the update again.
If you side-loaded the gnex browser so you could use flash, go to the /System/App folder and make sure you have BrowserProviderProxy.apk and BrowserProviderProxy.odex named properly. As stated earlier, rename browser.apk to browser.apk.bak. Restart and then try taking the update again. I had that problem. After getting the OTA installed, I renamed the browserproviderproxy files again, and made it browser bak file browser.apk. Now I have flash working perfectly again on the gnex stock browser.
Okay i managed to fix the browser proxy thing, turns out i had 10.apk at the end of it for some reason
and i renamed browser.apk to browser.apk.bak so that worked,
but now i got the same problem but with wallet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I remember having to jack around with Wallet to get the original update which allowed other credit/debit cards to be added. Some offered a solution where you could download a modified wallet.apk that would work instead of going through the other hoops. If you did that, the apk probably doesn't pass the verification. If you used a modified Wallet.apk did you backup the original one first?
Groid said:
I remember having to jack around with Wallet to get the original update which allowed other credit/debit cards to be added. Some offered a solution where you could download a modified wallet.apk that would work instead of going through the other hoops. If you did that, the apk probably doesn't pass the verification. If you used a modified Wallet.apk did you backup the original one first?
Click to expand...
Click to collapse
I didn't, and i did use a modified APK, but i deleted that, then i downloaded an original but still not working
build.prob error
Fixing steps for build.prob error :
VERY IMPORTANT: You will los all of your data, please make a backup befor you following this stepps ^^
Error Message apply_patch_check("/system/build.prob - "Numbers" , "Numbers")
My way which worked for me
1.)
The only way, if you dont have any backup of the original build prob file youl have to flash a copy of the factory IMAGE.
In my case i used the Nexus Toolkit 3.2 V - with this marvelous tool I copied the Factory Image 4.1.1 on it
2.)
After the factory Image you will lose your root. Install Clockwork or a other custom recovery image. Then its easy too get back your root with the Toolkit (follow the steps)
3.) If your not able to receve the OTA update to 4.1.2, download it and copy the ZIP to your Nexus 7
After this, go back to Fastboot and install the Updates using the up an down Volium buttons to navigate
Now the updating process should go very smooth
greets Razzor
I have the same error when installing from CWM and the ONLY CHANGES I made to my N7 are:
- Unlock
- Root
- CWM
- Battery Icon
Any other ideas? Will installing from ADB and Android own Recovery will work?
EDIT: I tried the update on my SECOND N7, which have all the above EXCEPT the battery icon mod and it works. So looks like the battery icon mod is the issue! Anyone know how to revert back to the original battery icon?
Also, since the first update failed, when I clicked on "Check" under SYstem Update, now my N7 said the system is up to date. How do I force the update to run again?
The system checks are there for a reason and I am in no way responsible if anyone bricks their device with this but...
https://www.dropbox.com/s/isqpvb0w26kqjdx/4.1.2edited.zip
This is the update with the checks disabled. I didn't make this, got it off another forum, I just used it because I had moved an update to chrome into my /system and there was no easy way to revert it.
I wouldn't advise using this if you made build.prop modifications, but it is useful if your update is failing over some apps like google wallet.
Once again, I didn't make this and I'm not responsible if you for some reason use this to flash the update over some heavily modded rom
It's from JRO03D btw.
This is vanilla build of clockwork mod recovery from CyanogenMod repo. The image we get from clockworkmod.com has some proprietary additions which blocks any app other than ROM Manager to access recovery. But I wanted open source build of CWM to make it work with CyanDelta, so I compiled myself.
You can flash this recovery using fastboot.
Code:
fastboot flash recovery recovery.img
Download
IMG File - androidtweak.in/downloads/crespo/recovery.img
Flashable zip - androidtweak.in/downloads/crespo/opensource-cwm-6.0.2.7.zip
Known Issues:
* USB mount not working within recovery.
jishnu7 said:
This is vanilla build of clockwork mod recovery from CyanogenMod repo. The image we get from clockworkmod.com has some proprietary additions which blocks any app other than ROM Manager to access recovery. But I wanted open source build of CWM to make it work with CyanDelta, so I compiled myself.
You can flash this recovery using fastboot.
Code:
fastboot flash recovery recovery.img
Download: androidtweak.in/downloads/crespo/recovery.img
Click to expand...
Click to collapse
Thank you for compiling this
Great idea! is this touch or non-touch version?
can anyone create a flashable zip ? Thanks for this Open Version!
AABatteries said:
Great idea! is this touch or non-touch version?
Click to expand...
Click to collapse
This is non touch version
matatr0n said:
can anyone create a flashable zip ? Thanks for this Open Version!
Click to expand...
Click to collapse
OK. I'll create a flashable version later today.
Sent from my Nexus S using xda app-developers app
Did usb mount work for you ?
raducux said:
Did usb mount work for you ?
Click to expand...
Click to collapse
Still not worked for me... back to 6.0.1.0 btw thanks dude for bring this..:good::good:
Here is the flashable zip.
xxxMADxxx said:
Still not worked for me... back to 6.0.1.0 btw thanks dude for bring this..:good::good:
Click to expand...
Click to collapse
is V. 6.0.1.0 has 2 mode of recovery? tar mode and blob? (i looked not 2 mode)
Edit: Here is the flashable zip.
mypat said:
is V. 6.0.1.0 has 2 mode of recovery? tar mode and blob? (i looked not 2 mode)
Edit: Here is the flashable zip.
Click to expand...
Click to collapse
Like this?? I even dont know what a mean "blob" folder :banghead:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus S using Tapatalk 2
xxxMADxxx said:
Like this?? I even dont know what a mean "blob" folder :banghead:
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Mode 1 tar mode this means backup makes one tar file.
Mode 2 blob mode what i said before makes 1 main backup after that makes little backup files what was changed so it's little faster but you can't copy this to your computer completely which i never like.
mypat said:
Mode 1 tar mode this means backup makes one tar file.
Mode 2 blob mode what i said before makes 1 main backup after that makes little backup files what was changed so it's little faster but you can't copy this to your computer completely which i never like.
Click to expand...
Click to collapse
Ohh i see..btw mount storage is working for you on 6.0.2.7 dude?
Sent from my Nexus S using Tapatalk 2
xxxMADxxx said:
Ohh i see..btw mount storage is working for you on 6.0.2.7 dude?
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
I didn't tried yet also i don't want because it's not official . I'am still using 5.8.0.2.
mypat said:
I didn't tried yet also i don't want because it's not official . I'am still using 5.8.0.2.
Click to expand...
Click to collapse
Lol..
Sent from my Nexus S using Tapatalk 2
matatr0n said:
can anyone create a flashable zip ? Thanks for this Open Version!
Click to expand...
Click to collapse
OP updated with flashable zip.
is sdcard mount in recovery working? that's a very important matter, since it has a potential of bricking your device if you happen to lose your backup from sdcard and end up in a bootloop.
this CMW version has blob version backup? if yes, could the OP build the latest full-backup version of CWM in a similar manner? We would all be grateful, and even happy to donate for your effort.
cheers!
AABatteries said:
is sdcard mount in recovery working? that's a very important matter, since it has a potential of bricking your device if you happen to lose your backup from sdcard and end up in a bootloop.
this CMW version has blob version backup? if yes, could the OP build the latest full-backup version of CWM in a similar manner? We would all be grateful, and even happy to donate for your effort.
cheers!
Click to expand...
Click to collapse
if you big want to use this make 2 zip of recovery in your sd card one this the other 6.0.1.0 or 5.0.8.2 if you need mount sd flash the zip which have mount sd support. and this versiyon have 2 mode backup one what you want and the other blob, there is an opthin which you can be able to choose backup mode.
jishnu7 said:
The image we get from clockworkmod.com has some proprietary additions which blocks any app other than ROM Manager to access recovery.
Click to expand...
Click to collapse
This is not true. I use official cwm images exclusively and I've never had any app fail to reboot into recovery. If you're going to make a claim, please at least make sure there is some merit to it.
also, this is not touch-enabled.
hp420 said:
This is not true. I use official cwm images exclusively and I've never had any app fail to reboot into recovery. If you're going to make a claim, please at least make sure there is some merit to it.
also, this is not touch-enabled.
Click to expand...
Click to collapse
It's actually true. If you're going to make a claim, please make sure there's some merit to it. ;P
Only ROM Manager can interact with CWM recovery because extendedcommand are encrypted to only work with it due to licensing bull****. Doesn't mean reboot to recovery, means manage stuff to flash from within Android.
https://github.com/CyanogenMod/andr...mmit/08bedb21d87dede99f1e89a4869609389bb7cee7
Also, touch feature is not open sourced if I'm not mistaken.
polobunny said:
Only ROM Manager can interact with CWM recovery because extendedcommand are encrypted to only work with it due to licensing bull****. Doesn't mean reboot to recovery, means manage stuff to flash from within Android.
Click to expand...
Click to collapse
I know this is a little old, but do you have any (non-cyandelta) references for this? CM Updater seems to work just fine with CWM official, and it's very open source:
https://github.com/CyanogenMod/android_packages_apps_CMUpdater/blob/jellybean/src/com/cyanogenmod/updater/UpdatesSettings.java
If they can do it, I don't know why cyandelta can't.
bill.allrobots.org said:
I know this is a little old, but do you have any (non-cyandelta) references for this? CM Updater seems to work just fine with CWM official, and it's very open source:
https://github.com/CyanogenMod/android_packages_apps_CMUpdater/blob/jellybean/src/com/cyanogenmod/updater/UpdatesSettings.java
If they can do it, I don't know why cyandelta can't.
Click to expand...
Click to collapse
Read the first 3 lines of the commit I linked to
-// Copyright ClockworkMod, LLC. Reference and porting purposes only. Usage of the extendedcommand API
-// is restricted to those granted explicit permission, or by use of the ROM Manager Recovery API.
-// https://github.com/koush/TestRomManager
Click to expand...
Click to collapse
and
http://wiki.rootzwiki.com/OpenRecoveryScript
OpenRecoveryScript is a scripting engine that allows applications to pass commands to a custom recovery.
It is similar to extendedcommands used in ClockworkMod Recovery. However, OpenRecoveryScript is completely open-source, unencrypted, and available for every app to use without requiring a paid or limited API.
Click to expand...
Click to collapse
Cheers
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
CLEAR/DELETE DALVIK-CACHE FOLDER FROM "/data/dalvik-cache" IN ROOT EXPLORER OR TWRP AFTER INSTALLING BOOT IMAGE TO ALLOW SYSTEM TO ADJUST
##FLASH THE LATEST SUPERSU ZIP BELOW##
P.S. I NOTICE IT IS NO LONGER SYSTEM-LESS MODE. SO WE CAN TRIM THE SUPERSU SYSTEM-LESS CONTENT FROM THE RAMDISK.
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
If you have ISSUES WITH DATA SPEEDS in certain areas, especially if you tether, GO INTO THE DIALER and DIAL *#*#4636#*#* then ACCESS PHONE INFORMATION and SELECT CDMA auto (PRL) UNDER SET PREFERRED NETWORK TYPE. LTE seems to be problematic in certain areas with speeds dropping to 150kbps and with this solution you'll be getting about 600 to 700kbps so at least it'll be a gain until you get into an area with better LTE coverage. In a good coverage area, I get download speeds of up to 5 to 7 mbps with LTE on, but in bad areas, CDMA works better. If you want to tether with a wireless third party solution make sure to run in a terminal window or adb shell as root : pm disable com.htc.tetheringguard
DOWNLOAD BOOT IMAGE: http://forum.xda-developers.com/attachment.php?attachmentid=3917986&d=1477604429
DOWNLOAD SUPERSU BETA: https://download.chainfire.eu/1009/SuperSU/SR2-SuperSU-v2.78-SR2-20161029143931.zip?retrieve_file=1
DOWNLOAD SCRIPTS: http://forum.xda-developers.com/attachment.php?attachmentid=3863279&d=1472880351
DOWNLOAD PIE FIX: http://forum.xda-developers.com/attachment.php?attachmentid=3844539&d=1471383163
DOWNLOAD BOOT IMAGE TOOL : http://forum.xda-developers.com/attachment.php?attachmentid=3917995&d=1477605263
DOWNLOAD HTC DRIVERS AND MINIMAL ADB + FASTBOOT: http://forum.xda-developers.com/attachment.php?attachmentid=3868562&d=1473328405
ANDBLOCKDEV.sh from scripts zip will speed up file input and output speeds, its contents have been incorporated into the boot image so the scripts files are for your own archival.
The zip DESIRE626SIMGTOOL.zip contains the android image kitchen and the 6.0.1 Boost Desire 626S boot image contents already extracted into two folders split_img and ramdisk with recent modifications. Enjoy!
http://www.vysor.io/ is a great tool to control your android device from a computer within chrome. You should try it out.
I provided a zip named HTCDrivers.zip containing the installation for both fastboot and adb drivers for the Boost Desire 626S, and minimal adb and fastboot. This will help you connect your device up with Vysor.
COPY the FILES; fastboot.exe, adb.exe, AdbWinUsbApi.dll and AdbWinApi.dll FROM - C:\Program Files (x86)\Minimal ADB and Fastboot - TO - C:\Windows\System32 - AND - C:\Windows\SysWOW64
Once you have installed the drivers for HTC devices,
and copied the minimal adb and fastboot files specified above to both system folders, you should be able to run adb commands without a problem by just opening a command prompt as administrator,
and RUNNING the command:
adb devices
- to start the adb server. This will allow connection with Vysor.
##########
For those who prefer nightbreed813's 6.0.1 slim rom version, I uploaded 601VPNDIALOGSFIX.zip to fix the issue with authorizing VPN clients, but first YOU HAVE TO CREATE /system/priv-app/VpnDialogs in Root Explorer or any other root filesystem browser, then reboot to TWRP recovery and flash the zip.
DOWNLOAD VPNFIX : http://forum.xda-developers.com/attachment.php?attachmentid=3860930&d=1472669879
##########
Also, you can get your MSL/SPC security code easily.........
Use the info in this thread to get your MSL/SPC security code so you can write new values to NV entries in the modem. Some values are locked but you can change the BC config for both LTE and CDMA so that would at least be helpful.
INFO HERE: http://forum.xda-developers.com/spri...k-sim-t3314755
##########
Android settings can be changed in the terminal for three namespaces; system, global and secure.
In the terminal run:
settings list system
settings list global
settings list secure
For each namespace all associated settings and their values will be listed. To change a setting type:
settings put system setting_name_here value_here
settings put global setting_name_here value_here
settings put secure setting_name_here value_here
##########
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Look now has working VPN......
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
anthonykb said:
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
Click to expand...
Click to collapse
Will this run on the Metro Variant?
As far as I know no but you can try in case it might.
Enter these commands in a new terminal window:
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
The backup boot image can be flashed from the sdcard in TWRP recovery if the device fails to boot into the system after flashing the boot image contained in the zip in the attachments.
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
MetroPCS Boot Image
GotHeart said:
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
Click to expand...
Click to collapse
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
anthonykb said:
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
Click to expand...
Click to collapse
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
GotHeart said:
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
Click to expand...
Click to collapse
I meant so you tried the boost version and it wouldn't boot?
anthonykb said:
I meant so you tried the boost version and it wouldn't boot?
Click to expand...
Click to collapse
No i havent tried it yet
GotHeart said:
No i havent tried it yet
Click to expand...
Click to collapse
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
Then unzip the 601bootimg.zip file with Zarchiver in the Play Store and flash the extracted boot image.
anthonykb said:
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
Click to expand...
Click to collapse
Okay ill do it now and let you know
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
GotHeart said:
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
Click to expand...
Click to collapse
Flash back the backed up boot image in TWRP and see if the sdcard mounts right. The mount point contained in the boost boot image is probably wrong for the the sdcard/emmc in the metropcs phone.
I did but my sdcard got corrupted so i was forced to format it.
GotHeart said:
I did but my sdcard got corrupted so i was forced to format it.
Click to expand...
Click to collapse
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
anthonykb said:
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
Click to expand...
Click to collapse
Its nothing important lol.any chance you can share what you did or how?
Use the Android Image Kitchen by osm0sis
GotHeart said:
Its nothing important lol.any chance you can share what you did or how?
Click to expand...
Click to collapse
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
anthonykb said:
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
My mistake i was in a hurry when i typed that last reply.
Im aware of how to unpack/repack boot images and i appreciate the link,but i was wondering what modifications that were made.if youd prefer not to share,i can upload my boot image if youd like to make the modifications yourself.im just trying to make this compatible with the metro version.
The same modifications done for the Boost Desire 626S might not work well for the MetroPCS version so upload the image you backed up yesterday as an attachment in a reply post and I'll work on it.
Thanks a ton!
MetroPCS Boot Image
GotHeart said:
Thanks a ton!
Click to expand...
Click to collapse
Run busybox top in the terminal on your phone and post some screenshots so I can see what might need to be done. We want to see what processes would be the culprit behind bogging down precious processor time and reducing the snappiness of the device in reacting to realtime input and handling current requests.
Hi all!
Happy to share a workaround for root and successful DRM fix.
If you lose your drm key, that's okay, this fix will restore all function which depends on it (picture quality, super vivid mode, etc.....). There's nothing satisfying than using your phone at its full potential with your own custom. Spot the difference!!!!
1. Unlock bootloader
2. Flash boot.img (Patched to be compatible with the drmfix)
>>> fastboot flash boot boot.img
3. Flash recovery.img
>>> fastboot flash recovery recovery.img
4. Boot to recovery by holding vol - and power; then swipe to allow modification and Format data (mandatory)
5. Flash drmfix.zip
6. Flash Magisk 14.0
7. Boot to android, you're done!!!
Type *#*#7378423#*#* then >>Service info>>Configuration or >>Service tests>>Security to check if all your keys are active.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download link:
# For boot.img here!!!
# For recovery.img here!!!
# For drmfix This does the trick
@pa7taloha Recovery Download link not working for me. Is normal TWRP also okay?
Edit: Nevermind, just saw its for F3311 not for F3111.
F3311? You mean Xperia XA or Xperia E5?
okhayko said:
F3311? You mean Xperia XA or Xperia E5?
Click to expand...
Click to collapse
I mean Xperia xa F3111. OP corrected, Thank you
Hi OP, still not working, all my is are "unknown"
okhayko said:
Hi OP, still not working, all my is are "unknown"
Click to expand...
Click to collapse
That's Strange, can you provide further info, like did you got any error when flashing the drmfix?
pa7taloha said:
That's Strange, can you provide further info, like did you got any error when flashing the drmfix?
Click to expand...
Click to collapse
Unfortunately, it's flashed well, no error.
Before i flash the drmfix, just 2 first lines are [Unknow Error] and the other lines are all [Active], Number or something like that
After i flash the drmfix, all of them are [Unknow Error]
okhayko said:
Unfortunately, it's flashed well, no error.
Before i flash the drmfix, just 2 first lines are [Unknow Error] and the other lines are all [Active], Number or something like that
After i flash the drmfix, all of them are [Unknow Error]
Click to expand...
Click to collapse
That means the drmfix you've flashed has deleted your credential which is located at /data/credmgr/ . For sure the linked drmfix here will not delete anything in your system.
Note: This drmfix will not be compatible with another boot.img different from the O.P. You have to do some mod in your boot.img to make this working. If you want to, let me know.
pa7taloha said:
That means the drmfix you've flashed has deleted your credential which is located at /data/credmgr/ . For sure the linked drmfix here will not delete anything in your system.
Note: This drmfix will not be compatible with another boot.img different from the O.P. You have to do some mod in your boot.img to make this working. If you want to, let me know.
Click to expand...
Click to collapse
Hi, can i ask a question?
My model is F3116, can i do step by step with this guide to make it work?
Sorry but i did not flash your boot.img file, i flashed boot.img file from the other thread, i though it the same. i will try your method but can you answer me that this will work with my model TY!
okhayko said:
Hi, can i ask a question?
My model is F3116, can i do step by step with this guide to make it work?
Sorry but i did not flash your boot.img file, i flashed boot.img file from the other thread, i though it the same. i will try your method but can you answer me that this will work with my model TY!
Click to expand...
Click to collapse
Post here your boot.img then, I will try to mod it. But make sure you still have your credmgr.db file which is located at /data/credmgr, this Fix won't work without it.
pa7taloha said:
Post here your boot.img then, I will try to mod it. But make sure you still have your credmgr.db file which is located at /data/credmgr, this Fix won't work without it.
Click to expand...
Click to collapse
Thanks buddy. Here is my boot.img that i was flash
boot.img file
For F3116 [33.3.A.1.97]
okhayko said:
Thanks buddy. Here is my boot.img that i was flash
boot.img file
Click to expand...
Click to collapse
Now
1. flash this bootF3116.img file, using the command "fastboot flash boot bootF3116.img" (without quotes)
2. Go to twrp recovery and "format data" (I suppose you already have flashed twrp)
3. Flash drmfix.zip
4. Flash Magisk if you need root.
5. Reboot
Download link
bootF3116.img
The compatible drmfix.zip
If you still have any problem let me know
Hi,
i had a F3112, is the DRM fix compatible ?
thanks
bobladure said:
Hi,
i had a F3112, is the DRM fix compatible ?
thanks
Click to expand...
Click to collapse
Hi, F3112 and F3116 has the same boot.img file so you can try to flash the boot.img, and drmfix.zip above your post and post your feedback here
Hi @pa7taloha,
Can you share your kernel drm fix changes (github or some other cloud server)? I'm trying to implement some custom changes in the kernel and I could add this as well. Thanks.
cojocar.andrei said:
Hi @pa7taloha,
Can you share your kernel drm fix changes (github or some other cloud server)? I'm trying to implement some custom changes in the kernel and I could add this as well. Thanks.
Click to expand...
Click to collapse
Sorry for late reply.
I will try to be clear as much as I can(bad english speaker).
We have tested this workaround to: xperia xa f3111(Mediatek, Nougat) and xperia x perfomance(qualcom, Nougat and 0reo) and it work fine in Nougat and Oreo too. I hope this will work too to the other xperia devices, so we can relate it.
I did not compile kernel from source, I have just extracted it with flashtool kernel.elf and unpacked/repacked it with AIK Linux/Carliv-image-kitchen. I am a Linux user.
For mediatek processor,
In the kernel, unpack it and edit.
1. disable dm-verity
2. edit init.rc
add this red line in on early-init, .
Code:
on early-init
[COLOR="Red"]restorecon /vendor/lib64/libdrmfix.so
restorecon /vendor/lib/libdrmfix.so[/COLOR]
# Set init and its forked children's oom_adj.
write /proc/1/oom_score_adj -1000
# Disable sysrq from keyboard
write /proc/sys/kernel/sysrq 0
3. edit init.aee.rc
add this red line in on init
Code:
on init
export LD_PRELOAD libdirect-coredump.so
write /proc/self/coredump_filter 39
setprop ro.aee.enperf off
[COLOR="Red"]export LD_PRELOAD libdrmfix.so[/COLOR]
4. edit default.prop
change the value of "ro.secure=0" to "ro.secure=1"
7. Open "fstab.mt6755" and copy in new text file the path to your system, it should be in the first line, we will use this later in the drmfix.zip
6. repack your kernel
II. We will do some mod to the drmfix.zip
open with the "open archive manager" the drmfix.zip and edit the updater-script in drmfix/META-INF/com/google/android/
This red line in the updater-script should be the same path to your system found in "fstab.mt6755" file in the boot.img (you've copied in step 5 in kernel)
Code:
ui_print(" ==================================");
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system[/COLOR]", "/system");
ui_print("updating..");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done!!!");
save it and update the drmfix.zip
For Qualcom processor
In the kernel, unpack it and edit.
1. disable dm-verity
2. edit init.rc
add this red line in on early-init
Code:
on early-init
[COLOR="red"]restorecon /vendor/lib64/libdrmfix.so
restorecon /vendor/lib/libdrmfix.so[/COLOR]
# Set init and its forked children's oom_adj.
write /proc/1/oom_score_adj -1000
# Disable sysrq from keyboard
write /proc/sys/kernel/sysrq 0
3. edit init.environ.rc
add this red line to the last line.
Code:
export SYSTEMSERVERCLASSPATH /system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
[COLOR="red"]export LD_PRELOAD libdrmfix.so[/COLOR]
4. edit default.prop
change the value of "ro.secure=0" to "ro.secure=1"
5. Open "fstab.qcom" and copy in new text file the path to your system, we will use this later in the drmfix.zip
6. repack your kernel, flash it
II. We will do some mod to the drmfix.zip
open with the "open archive manager" the drmfix.zip and edit the updater-script in drmfix/META-INF/com/google/android/
This red line in the updater-script should be the same path to your system found in "fstab.qcom" file in the boot.img (you've copied in step 5 in kernel)
Code:
ui_print(" ==================================");
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/bootdevice/by-name/system[/COLOR]", "/system");
ui_print("updating..");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done!!!");
save it and update the drmfix.zip, and flash it.
Avalaible for clarification.
https://imgur.com/OHuNKyk
Guys I can't seem to get it to work, tried reflashing your boot.img and recovery.img, tried formatting data and factory reset after every flash and wipe cache/dalvik cache after drm.zip install, nothing seems to get rid of those "Unknown error", btw I'm using F3111 single SIM on 33.3.A.1.97.
Almost forgot, when i plug my phone in fastboot and flash the files i don't get that flash status on the phone itself, only on cmd screen that it's done.
matan290 said:
https://imgur.com/OHuNKyk
Guys I can't seem to get it to work, tried reflashing your boot.img and recovery.img, tried formatting data and factory reset after every flash and wipe cache/dalvik cache after drm.zip install, nothing seems to get rid of those "Unknown error", btw I'm using F3111 single SIM on 33.3.A.1.97.
Almost forgot, when i plug my phone in fastboot and flash the files i don't get that flash status on the phone itself, only on cmd screen that it's done.
Click to expand...
Click to collapse
Sorry to hear that, It is always recommended to do a full nandroid backup before flashing anything. To get rid of those Unknown error you have to reflash your firmware. What causes these error is that the drm.zip you've flashed has deleted the credmgr.db file in /data/credmgr/, this contains all your phone credential. May be you've flashed any drmfix(old drmfix in other thread) before flashing this, because this fix will not delete anything in your system. And no need to wipe cache/dalvik after flashing it.
Yeah that's the problem,cause i flashed the other DRM fix few weeks ago. Can you please post a link or something for a firmware I can flash or should I try the PC Companion.
matan290 said:
Yeah that's the problem,cause i flashed the other DRM fix few weeks ago. Can you please post a link or something for a firmware I can flash or should I try the PC Companion.
Click to expand...
Click to collapse
You can use flashtool and download a frimware the latest version by xperifirm which is integrated in the flashtool. Or if you want to use Pc Companion you have to relock your bootloader and unlock after it's done.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fastboot Enhance
What it can do?
- Show fastboot vars
- Switch between fastbootd & bootloader
- Switch between A & B slot
- Flash Payload.bin in fastbootd
- Flash images
- Erase partitions
- Delete logical partitions
- Create logical partitions
- Resize logical partitions
- Unpack Payload.bin
- Extract specific image from Payload.bin
- Show Payload vars
- Show dynamic partition metadata
And above all, it has friendly GUI
Download
Releases · libxzr/FastbootEnhance
A user-friendly Fastboot ToolBox & Payload Dumper for Windows - libxzr/FastbootEnhance
github.com
By using this, you can freely switch between different versions of HydrogenOS & OxygenOS & Custom ROMs.
It is mostly tested on 8T but should work fine on any device shipped with dynamic partitions.
Notes for fastboot visualization
- You need to pre-install related fastboot usb drivers to make sure the device can be recognize by the software.
- Only in fastbootd or bootloader mode can the software recognize your device.
reserved2
I wonder if this would work with kb2007 TMO to go to ColorOS? I will download a check it out, thanks for the contribution!
xzr467706992 said:
Fastboot Enhance
Click to expand...
Click to collapse
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
mslezak said:
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
Click to expand...
Click to collapse
Disregard I just found your thread
Great job
mslezak said:
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
Click to expand...
Click to collapse
Google has mentioned the copy-on-write(COW) device here
Virtual A/B Overview | Android Open Source Project
source.android.com
For virtual a/b, the COW devices are created during the process of update. When there's enough spaces in super, they'll be created there, otherwise they'll be created in /data/gsi/ota.
xzr467706992 said:
Google has mentioned the copy-on-write(COW) device here
Virtual A/B Overview | Android Open Source Project
source.android.com
For virtual a/b, the COW devices are created during the process of update. When there's enough spaces in super, they'll be created there, otherwise they'll be created in /data/gsi/ota.
Click to expand...
Click to collapse
Yes I found it there for "virtual A/B" just an hour or two ago actually. They don't explain it too well, however.
Please don't mind I have few doubts about how to use this.
1. Suppose I have installed a custom rom and now I want to go back to Oxygen OS, can I do it by flashing the payload.bin using this fastboot enhance tool? If yes, what exact steps I have to go through?
2. If I flash the payload bin using this tool, will my all partitions will be recreated automatically as it was in a fresh stock condition when I used this 8T for first time even if the custom rom did any mess up with size or anything else? Also will it cleanup inactive slot too?
Amsal1 said:
Please don't mind I have few doubts about how to use this.
1. Suppose I have installed a custom rom and now I want to go back to Oxygen OS, can I do it by flashing the payload.bin using this fastboot enhance tool? If yes, what exact steps I have to go through?
2. If I flash the payload bin using this tool, will my all partitions will be recreated automatically as it was in a fresh stock condition when I used this 8T for first time even if the custom rom did any mess up with size or anything else? Also will it cleanup inactive slot too?
Click to expand...
Click to collapse
Yes, you can switch between custom ROMs and OOS using this tool.
This tool will only flash partitions listed in payload.bin, that means other partitions will remain unchanged.
Logical partitions will be automatically resized during flashing.
This tool will not create snapshot & switch slot when flashing, which is different from a normal update or sideload. That means the current slot will be flashed with new images in payload.
Note that on 8T, only the current slot you are using is bootable because of virtual ab, DO NOT SWITCH SLOT.
xzr467706992 said:
Yes, you can switch between custom ROMs and OOS using this tool.
This tool will only flash partitions listed in payload.bin, that means other partitions will remain unchanged.
Logical partitions will be automatically resized during flashing.
This tool will not create snapshot & switch slot when flashing, which is different from a normal update or sideload. That means the current slot will be flashed with new images in payload.
Note that on 8T, only the current slot you are using is bootable because of virtual ab, DO NOT SWITCH SLOT.
Click to expand...
Click to collapse
Thanks for your clarification
So the exact steps to flash any rom(OOS, Custom Rom) would be:
1. Boot to fastbootd mode
2. Load the payload.bin in Fastboot enhance v1.8
3. Click the flash payload.bin
4. Reboot to recovery and wipe
5. Reboot to system
right?
Amsal1 said:
Thanks for your clarification
So the exact steps to flash any rom(OOS, Custom Rom) would be:
1. Boot to fastbootd/bootloader mode
2. Load the payload.bin in Fastboot enhance v1.8
3. Click the flash payload.bin
4. Reboot to system
right?
Click to expand...
Click to collapse
Yes but you need to reboot to fastbootd for logical partitions (also theres hint in software)
Btw remember to enter recovery and wipe data after flashing
xzr467706992 said:
Yes but you need to reboot to fastbootd for logical partitions (also theres hint in software)
Btw remember to enter recovery and wipe data after flashing
Click to expand...
Click to collapse
reboot to fastbootd for logical partitions? I didn't got this.
Sure I will wipe from recovery after flashing the rom!
Amsal1 said:
reboot to fastbootd for logical partitions? I didn't got this.
Sure I will wipe from recovery after flashing the rom!
Click to expand...
Click to collapse
That means: flash payload in fastbootd because we have logical partitions.
xzr467706992 said:
That means: flash payload in fastbootd because we have logical partitions.
Click to expand...
Click to collapse
How can I enter fastbootd mode bro ? Thank you
hieu76pro said:
How can I enter fastbootd mode bro ? Thank you
Click to expand...
Click to collapse
If you are in system
adb reboot fadtboot
If you are in bootloader
Press the "reboot to fastbootd" button in software
xzr467706992 said:
If you are in system
adb reboot fadtboot
If you are in bootloader
Press the "reboot to fastbootd" button in software
Click to expand...
Click to collapse
Thanks bro
I am getting this while trying to flash evo x rom payload.bin:
These are the two cow partitions I found:
Is it safe to delete these two partitions?
Amsal1 said:
I am getting this while trying to flash evo x rom payload.bin:
View attachment 5383121
These are the two cow partitions I found:
View attachment 5383123
Is it safe to delete these two partitions?
Click to expand...
Click to collapse
Yes if system update status is none