[F1f] [ROM] [Color OS] OTA updates for rooted / unlocked devices (F1fEX_11_160922) - Oppo F1

Hi, I started the topic, because "rooted" (unlocked) devices can't get OTA updates.
Last stable version: ColorOS V2.1.0i - F1fEX_11_160922 (Android 5.1.1)
Note: Full package could wipe user data, please backup your data (e.g. with backup&restore app) before updating. Data on phone storage such as movies and photos could be affected.
Because of the "case-sensitive"-bug in TWRP for Oppo F1, I had to modify the updater-script in the \META-INF\com\google\android\ - directory in flashable zip-files
Code:
[COLOR="Red"]-- getprop("ro.build.product") == "F1f" || abort("This package is for \"F1f\" devices; this is a \"" + getprop("ro.build.product") + "\".");[/COLOR]
[COLOR="YellowGreen"]++ assert(getprop("ro.build.product") == "F1f" || getprop("ro.product.device") == "F1f" || getprop("ro.build.product") == "f1f" || getprop("ro.product.device") == "f1f" || abort("This package is for device: F1f; this device is " + getprop("ro.product.device") + "."););[/COLOR]
"magictricks" (fastboot-mode & unlock bootloader) by uberlaggydarwin and your custom recovery will survive the flash.
Downloads:
Recovery: TWRP | Stock
Full-Rom: ColorOS V2.1.0i - F1fEX_11_160507 (OTA_10_all, modified updater-script, removed stock recovery and aboot-image)
OTA (010-891): F1EX_11_OTA_010-891_patch_201606221750 (F1fEX_11_160622; modified updater-script, removed stock aboot-image)
OTA (891-894): F1EX_11_OTA_891-894_patch_201609221406 (F1fEX_11_160922; modified updater-script, removed stock aboot-image)
AFH-Mirror: Full-ROM | OTAs
Brick your device and can't get into recovery or fastbode mode? this workaround will make your day!
How to install?
1) (recommend) backup your data via backup&restore app
1.1) Boot into TWRP recovery
1.2) (optional) make a full twrp backup
1.4) (recommend) wipe dalvik / system / [optional] data / cache
2.1) Flash the complete flashable zip of your current Color OS
2.2) Flash new OTA incremental update zip (if available)
3) (optional) for root, flash SuperSu (v2.78 stable is working for me)
4) (optional) restore data
5) Reboot
6) (optional) restore data via backup&restore app
OTA notification still available after the update? - It's easy fixed by deleting /data/data/com.oppo.ota folder then rebooting (thxs to @MiniBlu)

..reserved for future work!

Awesome work.
I'll get a new TWRP built for you
PM me for the latest stock image if you need it.

uberlaggydarwin said:
Awesome work.
I'll get a new TWRP built for you
PM me for the latest stock image if you need it.
Click to expand...
Click to collapse
Thanks!
..Before I flashed TWRP, I made a dd-image of the stock-recovery..

Link is updated
Should work perfectly now. We also have a device page: https://twrp.me/devices/oppof1.html

Latest ColorOS is here
http://community.oppo.com/en/forum.php?mod=viewthread&tid=46142&extra=page=1
Thanks for your work.
PS Currently I am testing Spectrum Beta.

uberlaggydarwin said:
Link is updated
Should work perfectly now. We also have a device page: https://twrp.me/devices/oppof1.html
Click to expand...
Click to collapse
hmm.. I redownloaded from https://dl.twrp.me/f1f and reflashed TWRP.. but install breaks with same error 7
Code:
This package is for "F1f" devices; this device is a "f1f".
updater-script:
getprop("ro.build.product") == "F1f" || abort("This package is for "F1f" devices; this is a "" + getprop("ro.build.product") + "".");
Code:
/system # cat build.prop | grep ro.build.product
ro.build.product=F1f

mermigas said:
Latest ColorOS is here
http://community.oppo.com/en/forum.php?mod=viewthread&tid=46142&extra=page=1
Thanks for your work.
PS Currently I am testing Spectrum Beta.
Click to expand...
Click to collapse
I'm not allowed to view this forum.. I think because I'm a new forum-member there..

mdkeil said:
I'm not allowed to view this forum.. I think because I'm a new forum-member there..
Click to expand...
Click to collapse
For beta Spectrum android M testing you must reply to this post.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=45999&extra=page=1

mermigas said:
For beta Spectrum android M testing you must reply to this post.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=45999&extra=page=1
Click to expand...
Click to collapse
I replied 2 days ago ..and Spectrum is still closed Beta.. I will expand the OP for Spectrum in the future. :fingers-crossed:

mdkeil said:
hmm.. I redownloaded and reflashed TWRP.. but install breaks with same error 7
Click to expand...
Click to collapse
same for me.
and here's a newer firmware: (ah, I can't post links yet)
got to the community oppo forums then add/en/forum.php?mod=viewthread&tid=46153&extra=
or search for F1 ColorOS V2.1.0i Stable Version (20160507)

mdkeil said:
hmm.. I redownloaded from https://dl.twrp.me/f1f and reflashed TWRP.. but install breaks with same error 7
Click to expand...
Click to collapse
Oppo's fault. I don't have time to debug this now. Seems Oppo brought back fastboot in project spectrum.

DezeB said:
same for me.
and here's a newer firmware: (ah, I can't post links yet)
got to the community oppo forums then add/en/forum.php?mod=viewthread&tid=46153&extra=
or search for F1 ColorOS V2.1.0i Stable Version (20160507)
Click to expand...
Click to collapse
Using OTA_9 + incremental OTA_9-10 you will have the same firmware. [emoji6].. I will try this firmware later..
Gesendet von meinem ONE E1003 mit Tapatalk

uberlaggydarwin said:
Oppo's fault. I don't have time to debug this now. Seems Oppo brought back fastboot in project spectrum.
Click to expand...
Click to collapse
Yes fastbook is back and OEM unlock button is working

Will it help rooting using root app by Unlocking bootloader only or we need twrp recovery and flashing su binaries?
Sent from my F1f using XDA-Developers mobile app

You need to flash the su binaries via twrp and install supersu via playstore..
Gesendet von meinem ONE E1003 mit Tapatalk

stock rom and recovery
how to install stock rom and recovery.
plz send link

..at first posting you find all what you need.. I don't write a beginner how to flash a rom / recovery.. You can easy ask the search / Google for this.
Gesendet von meinem ONE E1003 mit Tapatalk

i have a doubt?, the link provided for stock rom at the starting post it says "F1fEX" but in d link in google drive it is "F1EX" so is the stock rom for F1F or just normal F1

It's for "F1f"
Gesendet von meinem ONE E1003 mit Tapatalk

Related

[ROM] CyanogenMod 7 (mesmerizemtd/showcasemtd) - [07/21/11]

Here is a test build/preview of the 2.6.35 MTD CM7 port for the Mesmerize and Showcase. It is built off the work of TeamHacksung, and is very different from earlier CM7 builds. At this point it is very functional, but still in very much of an ALPHA state.
Working:
Calls!!
SMS
3G data
GPS!!
Bluetooth!!
WiFi
Camera/Camcorder
USB mass storage / sdcard
Sensors!!
MMS
Not Working:
bugs
Known Issues:
* occassionally the radio may completely die (usually after phone has been powered off for a while) - fix: (shouldn't have to say this): pull the battery.
Included in the package is the base ROM and kernel. GAPPS must be flashed separately. Link below. You may also use nemesis2all's kernel here : http://forum.xda-developers.com/show....php?t=1119169
When flashed the first time, your filesystems will be converted to MTD (yaffs2/ext4). Do not try to flash any other ROMs via cwm at that point, and do not try to get into recovery via the 3 button method. Use adb reboot recovery or the reboot recovery option from the power menu. To revert, and switch to another ROM, flash a full Odin/Heimdall package.
Since your filesystems are being fully converted, there is no need for Voodoo or any other lagfix. DO NOT TRY TO INSTALL ANY KIND OF LAGFIX ON THIS ROM!!! Voodoo sound capability is however included in the kernel.
To install, boot into cwm recovery, wipe data, and flash the ROM. It will reboot and then do the actual install. If you are on a previous version, you can simply flash it over your current install. If you have problems, try wiping data first. The ROM will work whether you are on rfs or ext4.
*** Update 06/09 ***
fixed in-call audio
fixed bluetooth in-call audio
*** Update 06/20 ***
fixed GPS
re-enabled backlight notifications (you DO NOT need BLN control app)
disabled (broken) auto-brightness
other misc changes, see my github
*** Update 6/24 ***
fixed BT that was accidentally broken in previous build
updated to latest CM code
added standalone kernel zips to address sensor issues ** stand-alone zips removed
*** Update 6/26 ***
fixed sensor issues - now all sensors can be activated simultaneously
updated to latest CM code
*** Update 07/05 ***
added standalone zip to fix LED flash and deep sleep wake-up issues
simply flash the attached zip over the current ROM
full ROMs will be posted once I have time to clean up and redo my source repos
*** Update 07/21 ***
fixed MMS
updated to latest CM code
these builds are up-to-date with fascinate now
This is a WiP, and meant as more of a preview than anything else. If you enjoy it, click the Thanks or Donate buttons. Either one is fine by me. Enjoy
http://www.mediafire.com/?18gzh11s4enkx4h - Mesmerize ROM
http://www.mediafire.com/?08b7o4svmddr0rv - Showcase ROM
http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip - GAPPS
Awesome. Downloading now.
Sweet! Thank you so much jt. If I had a computer I would press the button.
Sent from my CM7 SCH-i500
Thanks for all that you do JT!!
THANKS! Just was on irc looking for this.
works like a charm!!!! runs nice and smooth...thank you for your god-like skillz!!!!!
Awesome work love it
Fast question. My phone has one of jt's older voodoo touchwiz kernels and I have cwm recovery 2.5.x red. The ROM is just a stock USCC froyo which is rooted.
Can I just flash this in cwm 2.5 or do I need to first odin cwm 3.0 and then flash? Do I have to disable the voodoo lagfix or change the kernel before I flash? Sorry I'm not as much of an expert as most people around here but I'm trying!
EDIT:
Oh and when using softlocker, won't that seriously decrease battery life?
userno69 said:
Fast question. My phone has one of jt's older voodoo touchwiz kernels and I have cwm recovery 2.5.x red. The ROM is just a stock USCC froyo which is rooted.
Can I just flash this in cwm 2.5 or do I need to first odin cwm 3.0 and then flash? Do I have to disable the voodoo lagfix or change the kernel before I flash? Sorry I'm not as much of an expert as most people around here but I'm trying!
EDIT:
Oh and when using softlocker, won't that seriously decrease battery life?
Click to expand...
Click to collapse
Well, im sure it will decrease it a bit, but what's your option really ?
userno69 said:
EDIT:
Oh and when using softlocker, won't that seriously decrease battery life?
Click to expand...
Click to collapse
yes. That's why, as much as I like this rom, I need decent battery life and have to receive calls, so I'm not flashing this until that bug is fixed.
That being said, INCREDIBLE work, jt! I can't wait for a daily driver.
Sent from my SCH-I500 using Tapatalk
All right, what about the other stuff? Can I flash this in CWM 2.5 and it will just install CWM 3.0 for me along with the ROM? Do I need to touch my kernel, or at the very least disable the lagfix before flashing? Does this rom overwrite any previous kernel you have?
Always disable lag fix,unless you want fc hell. .im not certain about this bit of software. But yeah most Roms come with the kernel best suited..at least from the devs standards. Rule of thumb if a program is active then it eats battery. Back up yo stuff cuz its gonna wipe you data
Sent from my SCH-I500 using XDA App
jt just wanted to say thx for getting gingerbread on the mesmerize/fascinate/showcase.. without all of ur hard work we prolly wouldnt see it for a while.... gratz on victory
puk3n said:
Always disable lag fix,unless you want fc hell. .im not certain about this bit of software. But yeah most Roms come with the kernel best suited..at least from the devs standards. Rule of thumb if a program is active then it eats battery. Back up yo stuff cuz its gonna wipe you data
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Kernel is included. Lagfix does not matter - the rom flash will override everything anyway. Do not try to enable lagfix in anyway on cm7. Not needed and won't work.
akellar said:
Kernel is included. Lagfix does not matter - the rom flash will override everything anyway. Do not try to enable lagfix in anyway on cm7. Not needed and won't work.
Click to expand...
Click to collapse
Ok but I thought I read somewhere that when you have CWM 3.0 that it has a bug that automatically enables the lagfix. Is that true? How would you prevent this?
userno69 said:
Ok but I thought I read somewhere that when you have CWM 3.0 that it has a bug that automatically enables the lagfix. Is that true? How would you prevent this?
Click to expand...
Click to collapse
The rom isn't flashed in cwm3 - it will flash cwm4 first and the flash the rom.
curious, what kind of quadrant / linpack scores are you guys getting? I'm tempted to flash but i'd really like the deep sleep / mms to get fixed before I jump on.
Ok I am getting install errors in clockwork. Everytime I try to install, it says error installation aborted, something about "status 7." I have never had this problem before. I saw were you need to delete the 4 lines in the update script, but what exactly do I need to delete? Or what do I need to do to be able to install?
I am currently running jt's 5/18 build port if that helps.
Thanks.
userno69 said:
Ok but I thought I read somewhere that when you have CWM 3.0 that it has a bug that automatically enables the lagfix. Is that true? How would you prevent this?
Click to expand...
Click to collapse
on your sdcard there is a voodoo folder..inside that you need to place a file called disable_lagfix kiev and that will prevent spontaneous conversions..if I got the file name wrong someone e please correct me
Sent from my SCH-I500 using XDA Premium App
When I attempt to install this from cwm 3.2 I get the following error:
Code:
assert failed getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" || getprop("ro.product.board") == "aries" ||
getprop("ro.product.device") == "mesmerize" || getprop("ro.build.product") == "mesmerize" || getprop("ro.product.board") == "mesmerize" ||
getprop("ro.product.device") == "mesmerizemtd" || getprop("ro.build.product") == "mesmerizemtd" || getprop("ro.product.board") == "mesmerizemtd" ||
getprop("ro.product.device") == "SCH-I500" || getprop("ro.build.product") == "SCH-I500" || getprop("ro.product.board") == "SCH-I500"
Upon the recommendation of lmartin92 I removed this text from the updater-script file, which results in me getting a (Status 4) failure instead.
EDIT: I forgot to say it before, thanks so much for the work you've put in jt. I really appreciate it, and I can't wait for it to be fully ready

[ROM][STOCK[GT-S7275R] Stock ROM CWM Edition

Good followers! Today I bring you something that can be very useful, especially if you can not use Odin and you need to flash stock rom due to a brik or bootloop.
Today I bring the Spanish Samsung Stock Rom, flashable by CWM Recovery! It is completely original, the same as if you flash Stock ROM via Odin.
Click to expand...
Click to collapse
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Bugs:
- It shouldn't has bugs
Click to expand...
Click to collapse
Features:
-CSC: BTU, CYV, DBT, ETL, ITV, MEO, NEE, PHE, SEB, SEE, TMN, TPH, XEF, XEH, XEO
- Compiled: 22.04.2015
Click to expand...
Click to collapse
Installation:
1. Place the file in the SDCard and boot into CWM Recovery
2. Wipe data
3. Wipe cache
4. Wipe Dalvik-Cache (advanced menu)
5. Format system (mounts and storage menu)
6. Install zip from sdcard
7. Choose zip from sdcard or internal sdcard
8. Install
9. Reboot system now
10. Done!
Click to expand...
Click to collapse
Download:
- GT-S7275R_signed_PHE.zip
Click to expand...
Click to collapse
***Mirroring my ROM and builds is not appreciated***
Click to expand...
Click to collapse
Credits:
- Me
Click to expand...
Click to collapse
Code:
If you like it, give me a thanks ;)
Maniakk said:
Wow nice bro! Tomorrow I flash! Good work man!
Click to expand...
Click to collapse
It was built a long time ago, and I copy the post in our new thread of Ace 3. I'm not a very big developer, I don't know how to fix the bugs.
Also you might have problems with modem.
Enviado desde mi GT-S7275R usando Tapatalk 2
Maniakk said:
You will be something to do with it? fix bugs? Or maybe you do port in Galaxy Ace 4? Android 4.4.4.
Click to expand...
Click to collapse
I'm not really sure. I'll try to build again this stock rom, and if I fix the bugs, I'll make my own stock based rom, and then port some JB ROMs.
I leave the work on KK to kostoulhs or other developer.
Enviado desde mi GT-S7275R usando Tapatalk 2
Running in s7275b ?
lcosta2 said:
Running in s7275b ?
Click to expand...
Click to collapse
I'm not sure. I think not, cause is extracted of Stock Rom of GT-S7275R
Enviado desde mi GT-S7275R usando Tapatalk 2
Arcanister99 said:
Good followers! Today I bring you something that can be very useful, especially if you can not use Odin and you need to flash stock rom due to a brik or bootloop.
Today I bring the Spanish Samsung Stock Rom, flashable by CWM Recovery! It is completely original, with a few things added by me.
I couldn't test it. Do it at your own risk! I'm not responsibleof any damage!
Bugs:
- SIM detection
- WiFi
- Maybe more
Features:
- Removed (most) ads
- Rooted with SuperSU
- Busybox
- Init.d Support
- Preinstalled Apps (Aptoide, Titanium Backup, Root Explorer ...)
- Custom Bootanimation Enabled
- Other small things!
Installation:
1. Place the file in the SDCard and boot into CWM Recovery
2. Wipe data
3. Wipe cache
4. Wipe Dalvik-Cache (advanced menu)
5. Format system (mounts and storage menu)
6. Install zip from sdcard
7. Choose zip from sdcard or internal sdcard
8. Install
9. Reboot system now
10. Done!
Download:
- GT-S7275R_unsigned_PHE.zip
Screenshots:
* I'm waiting you test it and send captures*
Credits:
- Me
- Scripts Creators that I added
- People who have helped me (almost "mahond")
Click to expand...
Click to collapse
Would you be fixing the bugs?
tthmatt said:
Would you be fixing the bugs?
Click to expand...
Click to collapse
If I have time, I'll work on it ?
Enviado desde mi GT-S7275R usando Tapatalk 2
How did you make this ROM?
tthmatt said:
How did you make this ROM?
Click to expand...
Click to collapse
Due to it was the first rom, I made it from 0.
Firstly, I downloaded the Stock ROM of Samsung, then, using a tool and some programmes that I don't remember, I extracted all the folders and files from tar file. After, I made some mods and finally I built the updater-script (thanks to mahond).
Enviado desde mi GT-S7275R usando Tapatalk 2
New Build!!!!
Good news! I compiled a second build of this ROM. However, this build is pure-stock.
It doesn't have root, or busybox or any of this stuff. It's the same Stock Rom as if you flash it via Odin. The good part is that you recover the guarantee flashing this.
If all bugs are fixed this time (I've not tested it), I'll do the same with more Ace 3 variants, and finally I'll work in a modified stock rom.
Uploading 2nd build soon!!!!
(Sorry for my bad english )
EDIT: 1st post updated, new build is uploaded!!
Maniakk said:
Nice! I will Wait to deodex and root and very very more. I believe you.
Click to expand...
Click to collapse
Yeah, I'll do it, but first I need that someone tests it and report that all is working fine...
Enviado desde mi GT-S7275R usando Tapatalk 2
Maniakk said:
Twrp recovery instal this rom?
Click to expand...
Click to collapse
Of course
Enviado desde mi GT-S7275R usando Tapatalk 2
I was flashing stock ROM zip via CWM and I got this error: Installing: /storage/sdcard1/Downloads/GT-S7275R_signed_PHE.zip
Finding update package...
I:Update location: /storage/sdcard1/Downloads/GT-S7275R_signed_PHE.zip
Opening update package...
Installing update...
I:Using legacy property environment for update-binary...
assert failed: write_raw_image("/tmp/boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot")
I:Legacy property environment disabled.
E:Error in /storage/sdcard1/Downloads/GT-S7275R_signed_PHE.zip
(Status 7)
Installation aborted.
T0037847F said:
I was flashing stock ROM zip via CWM and I got this error: Installing: /storage/sdcard1/Downloads/GT-S7275R_signed_PHE.zip
Finding update package...
I:Update location: /storage/sdcard1/Downloads/GT-S7275R_signed_PHE.zip
Opening update package...
Installing update...
I:Using legacy property environment for update-binary...
assert failed: write_raw_image("/tmp/boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot")
I:Legacy property environment disabled.
E:Error in /storage/sdcard1/Downloads/GT-S7275R_signed_PHE.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Ummmm, it seems to be that the command line to flash de kernel is wrong written...I'll have a look.
Is this ROM still available somewhere? I have trouble flashing a stock ROM via Odin. Can you please re-upload this ROM again somewhere? Thanks

Guide: aicp nougat prealpha i got it to boot and you can too

this guide will show you how to flash aicp 12 nougat on the kltevzw
this thread is only for s5 verizon bootloader unlocked rooted devices thanks Alexander Seibel developer of aicp 12 for klte
please please take a twrp full backup or cwm full backup of your device before you follow this guide just in case
You must be on a lollipop rom/firmware
here is the link for aicp nougat klte use this new updated build
https://drive.google.com/file/d/0B0CIUMAYWOakM3IxVE5Hc1VuMWM/view
nougat gapps use banks dynamic gapps
go to sammobile.com and download g900F btu uk boi3 firmware
it boots !!!!!
here is how to get it to boot
have root and bootloader unlock with a custom recovery installed on pb1 firmware on s5 verizon
then install supersu and flashfire and busybox
download g900F btu uk boi3 firmware download it from here sammobile.com
then download 7zip file manager from here http://www.7-zip.org/
open 7 zip file manager and click extract and choose boi3 firmware zip
then rename it to G900FXXU1BOI3_G900FOXA1BOI3_G900FXXU1BOI3_HOME.tar
then open 7zip file manager again and choose G900FXXU1BOI3_G900FOXA1BOI3_G900FXXU1BOI3_HOME.tar and click extract
then open 7 zip and find the system img in the G900FXXU1BOI3_G900FOXA1BOI3_G900FXXU1BOI3_HOME folder
and choose it then click add and choose tar
then move system img tar to phone
then open flashfire and click plus symbol then click flash firmware and choose firmware system img tar this is the g900F boi3 system img tar
then click system only
then click checkmark
then click flash
wait for your phone to boot important
then boot to recovery e.g. twrp and
flash aicp 12 zip use 10-2-16 build
then flash gapps either open gapps or banks gapps i used banks and i know it works
wait for it to boot and have fun
about 1/3 of the features don't work by my estimation status bar broken, no notifications, home button doesnt work, recents button doesn't work ,screenshot combo doesn't work, terminal apps doesnt work dont use them they will cause a reboot of the device, developer option menu doesn't open/popup when you click build number 8 times
calling data and texting works now ,root works adb is permmissive and se linux is permissive wifi works camera works
usb otg works sound quality is awesome using audio fx equalizer and spotify on high quality :laugh:
i would have done screenshots but no screenshot combo
here is youtube video of a screen recording
i got a fix for some of the broken features
developer options can be turned on
backlight can be turned off
notifications work
status bar settings avaliable now
lockscreen apps show up on lockscreen
home and recents button work now
quick settings are available now
buttons settings avaliable now
system ui tuner setting shows up now
on a g900v device
so to do this fix install settings database editor app from google play
then open a terminal app
and type
su
pm grant by4a.setedit.WRITE_SECURE_SETTINGS
then open settings daabase editor
under secure tab find user setup complete change this to 1
then under global tab find device provisioned and change this to 1
screenshot still broken causes a device reboot
and call delay and bluetooth still broken
this fix breaks power menu just reboots now
dont turn on advanced reboot in developer menu either
here is a video of fix
https://www.youtube.com/watch?v=rwDzloTgCrg
thanks aicp development team for your outstanding work
Thanks Alexander Seibel developer of aicp 12 for klte
thanks opengapps
thanks Chainfire for flashfire and supersu
thanks Denys Vlasenko for busybox
thanks team windows recovery project for twrp
Thank you so much but it seems complicated and needs lots of stuffs to do why just to flash that rom directly using twrp lol.. Thanks again
i didn't say just flash it because it doesn't work you get a twrp error 7 this is the fix for error 7.
Error 7 it has to do with asserts, and the build prop file which you can't edit.
So this flashing the system img of the g900f in effect gives you the build prop file of a g900f fooling twrp into thinking the phone you are using is a g900f and lets the rom flash in twrp so this is why i had to do this.
[email protected] said:
i didn't say just flash it because it doesn't work you get a twrp error 7 this is the fix for error 7.
Error 7 it has to do with asserts, and the build prop file which you can't edit.
So this flashing the system img of the g900f in effect gives you the build prop file of a g900f fooling twrp into thinking the phone you are using is a g900f and lets the rom flash in twrp so this is why i had to do this.
Click to expand...
Click to collapse
I have to correct you...To bypass this error 7 you have to edit updater-script in meta-inf folder not build.prop in /system partition. All you need to do is to remove or change a part of script which checks device model number.
For example, this is from CM13:
Code:
assert(getprop("ro.product.device") == "kltexx" || getprop("ro.build.product") == "kltexx" ||
getprop("ro.product.device") == "kltelra" || getprop("ro.build.product") == "kltelra" ||
getprop("ro.product.device") == "kltetmo" || getprop("ro.build.product") == "kltetmo" ||
getprop("ro.product.device") == "kltecan" || getprop("ro.build.product") == "kltecan" ||
getprop("ro.product.device") == "klteatt" || getprop("ro.build.product") == "klteatt" ||
getprop("ro.product.device") == "klteub" || getprop("ro.build.product") == "klteub" ||
getprop("ro.product.device") == "klteacg" || getprop("ro.build.product") == "klteacg" ||
getprop("ro.product.device") == "klte" || getprop("ro.build.product") == "klte" ||
getprop("ro.product.device") == "kltekor" || getprop("ro.build.product") == "kltekor" ||
getprop("ro.product.device") == "klteskt" || getprop("ro.build.product") == "klteskt" ||
getprop("ro.product.device") == "kltektt" || getprop("ro.build.product") == "kltektt" ||
abort("This package is for device: kltexx,kltelra,kltetmo,kltecan,klteatt,klteub,klteacg,klte,kltekor,klteskt,kltektt; this device is " + getprop("ro.product.device") + "."););
I removed whole asserts line and got could not find updater binary error
Sent from my SM-G900V using Tapatalk
Already one step ahead of you
Sent from my SM-G900V using Tapatalk
Can we expect any future updates on this? Seems really promising considering it is so early
It was updated on 10-2 now has cell data and texting working I just booted it on this device all the credit goes to Alexander seibel for making the rom for klte
Sent from my SM-G900V using Tapatalk
Here is new update from developer Alexander seibel
https://drive.google.com/file/d/0B0CIUMAYWOakUjdhMnJ5TC1NQjQ/view
I haven't flashed it personally yet
Sent from my SM-G900V using Tapatalk
Here is his Google+ profile if you want to follow this project: https://plus.google.com/101577397694816898663
People say its nearly daily driver, but expect bluetooth bugs and some call delay
Uwe303 said:
Here is his Google+ profile if you want to follow this project: https://plus.google.com/101577397694816898663
People say its nearly daily driver, but expect bluetooth bugs and some call delay
Click to expand...
Click to collapse
Call delay? Please specify
Sent from my SM-G900F using Tapatalk
EstusBottle said:
Call delay? Please specify
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
I just tested it and as soon as you start calling a number it Kind of "freezes" 3-5 sec and then the call begins.
But the ROM seems very stable and fast ,no app crash in 24h usage, battery life seems improved , camera works, Video recording ,mobile data ,calling ,....
Uwe303 said:
I just tested it and as soon as you start calling a number it Kind of "freezes" 3-5 sec and then the call begins.
Click to expand...
Click to collapse
Ok thank you Ill try it out. Well as far as Ihave been using this rom, not many probwlms actually. Some settings dont work, camera doesnt record videos and one more specific problem - cant acces my bank acount using an app witch uses the Sim ToolKit. Other than that, everything seems ok
Sent from my SM-G900F using Tapatalk
I cant use recent button home button and notification dont work screenshot combo doesn't work developer option sdoesnt pop up after clicking build number 8 times
Sent from my SM-G900F using Tapatalk
[email protected] said:
I cant use recent button home button and notification dont work screenshot combo doesn't work developer option sdoesnt pop up after clicking build number 8 times
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Just curious how many people are developong this version of nougat?
Sent from my SM-G900F using Tapatalk
You mean aicp here you go https://plus.google.com/communities/101008638920580274588
I have tried flashing this ROM over nemesis note 7 port and after the process completed it stuck on some configuration and did not happened anything for more than 20min. Then I flashed cm13. Any solution to boot this ROM..??
Sent from my SM-G900F using XDA-Developers mobile app
mukdiwalaazim said:
I have tried flashing this ROM over nemesis note 7 port and after the process completed it stuck on some configuration and did not happened anything for more than 20min. Then I flashed cm13. Any solution to boot this ROM..??
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you wiped your system before flashing? Wiping again after flash and clear cache can also help.
i got a fix for some of the broken features
developer options can be turned on
backlight can be turned off
notifications work
status bar settings avaliable now
lockscreen apps show up on lockscreen
home and recents button work now
quick settings are available now
buttons settings avaliable now
system ui tuner setting shows up now
on a g900v device
so to do this fix install settings database editor app from google play
then open a terminal app
and type
su
pm grant by4a.setedit.WRITE_SECURE_SETTINGS
then open settings daabase editor
under secure tab find user setup complete change this to 1
then under global tab find device provisioned and change this to 1
screenshot still broken causes a device reboot
and call delay and bluetooth still broken
here is a video of fix
https://www.youtube.com/watch?v=rwDzloTgCrg
Uwe303 said:
Did you wiped your system before flashing? Wiping again after flash and clear cache can also help.
Click to expand...
Click to collapse
Did you actually flash it on a G900V?!
Proud PalmOS user!

z3 with Carbon Rom not responding how to reinstall or fix?

I have installed Carbon Rom Version from december for z3 and for 3 months it worked fine but now I have Problem that it freezes very often and it doesnt even recognize my sim Card for some reason. How can i fix this Problem? Xperia Companion was the way with original Sony Rom but it wont recognize my phone either. I downloaded february update of Carbon Rom and when i try to install it or update it, it return
error 7 E:unknown command[log] error. I think that it Fails to recognize to phone type although my phone is D6602. I found the update-script in the zip file and removed first lines which to detect phone build but it didnt help either, this time it Returns another error "Couldnt find META-INF/com/Google/Android/update-binary". when i check the path, file is there but i dont get why i cant find.
Please shed me some lights to fix this Problem.
I have just downloaded december and january Carbon roms for xperia z3 and they arent installing either. I think because of Carbon Rom remosves phone build number, it doesnt appear as D6602 any longer after installing it. So I wonder what is the sence of Code below in the update-script
(getprop("ro.product.device") == "D6602" || getprop("ro.build.product") == "D6602" ||
getprop("ro.product.device") == "D6603" || getprop("ro.build.product") == "D6603" ||
getprop("ro.product.device") == "D6643" || getprop("ro.build.product") == "D6643" ||
getprop("ro.product.device") == "D6653" || getprop("ro.build.product") == "D6653" ||
getprop("ro.product.device") == "z3" || getprop("ro.build.product") == "z3" ||
getprop("ro.product.device") == "leo" || getprop("ro.build.product") == "leo") || abort("E3004: This package is for "D6602,D6603,D6643,D6653,z3,leo" devices
this is a "" + getprop("ro.product.device") + "".");
EDIT:
I have tried to Format internal drive using TWRP and installl the Carbon zip but I still get error above. Question is here why it is trying to execute update-script still if I formatted it.
Finally i found the reason and solution. It is silly that latest Carbon Rom is not possible to install using older Version of twrp. you should use 3.2 Version. on the other Hand, if you want to install gapps, 3.2 gives your error 64. so the way to do correct Installation
- use twrp 3.2 to install Carbon Rom. i have here bad experience with Carbon Rom february update. Google Play Services Keep crashing. thats why i used january Version for my z3 and it works fine.
- use twrp 3.0.2 to install gapps. as i said using 3.2 twrp, gapps not possible to install. download non-64 bit Version of gapps even your phone is 64bit.
emil_bg said:
Finally i found the reason and solution. It is silly that latest Carbon Rom is not possible to install using older Version of twrp. you should use 3.2 Version. on the other Hand, if you want to install gapps, 3.2 gives your error 64. so the way to do correct Installation
- use twrp 3.2 to install Carbon Rom. i have here bad experience with Carbon Rom february update. Google Play Services Keep crashing. thats why i used january Version for my z3 and it works fine.
- use twrp 3.0.2 to install gapps. as i said using 3.2 twrp, gapps not possible to install. download non-64 bit Version of gapps even your phone is 64bit.
Click to expand...
Click to collapse
Latest released carbon rom working fine for me. At first i installed gapps arm pico but with that Google play services keep crashing but then i flashed gapps arm stock which is 600 mb and now not a single error occurred till then nor any services crashed. It's damn smooth and more features with gapps stock. And now I'm running version 11.3.2019 dated update with that gapps stock.

[RECOVERY][karnak] TWRP touch recovery (Fire HD8 2018/ 8th gen)

Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Quote:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Click to expand...
Click to collapse
NOTE: This version of TWRP is intended to be used with the original unlock for karnak by xyz`.
If you unlocked or updated using amonet-3 it already contains an updated TWRP.
This version will still work, but it lacks support for features such as reboot to hacked BL.
Features:
amonet-aware
SDCard support
USB-OTG support
Backup/Restore support
Downgrade/Overwrite-protection for LK/PL/TZ
Autorestore of broken boot-patch
Also patches amonet-microloader when flashing images
Supports flashing stock-update bins (rename to .zip, no modification necessary )
NOTE: Your device needs to be unlocked.
NOTE: When backing up or restoring stock ROM (or any other ROM that has dm-verity enabled) make sure to select "System Image" instead of "System".
Many thanks to @Kaijones23 for testing!
Download: twrp-karnak-3.3.1-0.zip
XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the Amazon Fire HD 8 and HD 10
Contributors
k4y0z, xyz`
Source Code: https://github.com/chaosmaster/android_bootable_recovery
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-07-17
Created 2019-07-16
Last Updated 2019-07-17
Changelog
17.07.2019:
Update TWRP to 3.3.1-0
Add support for vendor partition
16.07.2019:
Fix USB-OTG
Reserved #2
Reserved #3
Sent from my Pixel 3a XL using Tapatalk
@k4y0z @Kaijones23 good work guys!!
Great work!
Just flash from existing TWRP to update?
Michajin said:
Great work!
Just flash from existing TWRP to update?
Click to expand...
Click to collapse
Yup
Just uploaded a new build, that also fixes USB-OTG
Works great on my HD8 2018 that I just got today.
New build is up
Update TWRP to 3.3.1-0
Add support for vendor partition
k4y0z said:
New build is up
Update TWRP to 3.3.1-0
Add support for vendor partition
Click to expand...
Click to collapse
Wow very nice!
Does karnak has vendor partition??
Rortiz2 said:
Wow very nice!
Does karnak has vendor partition??
Click to expand...
Click to collapse
It has, but not used by stock as far as i can tell.
I added support in TWRP, so it could potentially be used by custom ROMS.
Working great on my brand new HD8. Installed 3.3.1 from your 3.2.3 release, rebooted to recovery, reflashed magisk, no issues. Thanks!
jibgilmon said:
Working great on my brand new HD8. Installed 3.3.1 from your 3.2.3 release, rebooted to recovery, reflashed magisk, no issues. Thanks!
Click to expand...
Click to collapse
Reflashing Magsik should not have been necessary if it was already installed
Quick question,
Can I just go to my existing TWRP, click Install, select the ZIP file attached here and flash or do I need to extract the image and install the Image file from within the current TWRP version?
Thanks!
agr8lemon said:
Quick question,
Can I just go to my existing TWRP, click Install, select the ZIP file attached here and flash or do I need to extract the image and install the Image file from within the current TWRP version?
Thanks!
Click to expand...
Click to collapse
You can do it either way, but just flashing the zip in recovery is probably the easiest way. You can reboot recovery while in TWRP to check that it flashed successfully, if you want to.
Hey, quick question
Can i install any .zips that i want? If not, what or which types of .zips should i try to avoid?
(In this case i just want to install YT Vanced)
Thanks
5442 said:
Hey, quick question
Can i install any .zips that i want? If not, what or which types of .zips should i try to avoid?
(In this case i just want to install YT Vanced)
Thanks
Click to expand...
Click to collapse
I just installed YouTube Vanced from Magisk.
nujak said:
I just installed YouTube Vanced from Magisk.
Click to expand...
Click to collapse
I'm not talking about magisk, as i will be flashing LineageOS, and it already has root so i wanna know about recovery, not magisk
5442 said:
I'm not talking about magisk, as i will be flashing LineageOS, and it already has root so i wanna know about recovery, not magisk
Click to expand...
Click to collapse
Flashing YT VANCED in TWRP will also work.

Categories

Resources