I am writing this guide with all the steps I did to successfully boot Android P on my Whyred device, I am not responsible for any damage, brick, dead SD and so on.
All you have to do is:
-Boot to Recovery (you'll need a Treble Recovery).
-Go to "Clean" section and perform a Factory Reset by swiping the arrow below.
-On "Clean" section tap "Advanced Clean" and select all the partitions (Internal storage, USB-OTG and microSD excluded).
-Go to "Install" section and install last MoKee Rom (in order to boot Android P you'll need MoKee's Vendor).
-After you succesfully installed MoKee rom's zip, go back to recovery main menu and then again "Install" but now press "Install IMG file" and select P-DP3-sGSI.img mounting it as System Image.
-Now go back to recovery main menu and then tap on "Mount" section, here simply uncheck and then check again "vendor".
-Go back to "Install" and then simply install the three files which come after the installation of P-DP3-sGSI.img (POST-sGSI_1_v0.9.zip, POST-sGSI_2_v0.12.zip and POST-sGSI_3.zip in this exact order).
-Simply reboot to System and...you're DONE!
If you want Magisk, you'll need to flash it simply going back to Recovery mode but this only after you firstly setup the phone! (Also I don't know if there is a Magisk.zip compatible with Project Treble for Whyred. EDIT: Magisk 16.6 is working flawlessly).
Here some useful links:
Treble Recovery: https://dl.twrp.me/whyred/
MoKee Rom: https://download.mokeedev.com/?device=whyred&type=nightly
Android P files: https://androidfilehost.com/?w=files&flid=275999
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Some useful infos from Android P GSI's topic:(https://forum.xda-developers.com/pr...nt/rom-android-p-developer-preview-t3816659):
How to fix mtp:
Enable developer settings (Please google to know if you don't know)
Scroll down to select Default USB Configuration
Select File Transfer
Fix google account and playstore:
install https://tinyurl.com/gmscore
Have in-call audio bug?
flash (need vendor and system to be munted) : https://androidfilehost.com/?fid=5862345805528048703
Here some screenshots! :
{
"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"
}
Here a video review of Android P by TechDroider: https://www.youtube.com/watch?v=YguzLYgV1Jg
KNOWN BUGS: Camera not working, even when enabling HAL3 manually from build.prop, tested both Footej Camera and GCAM; Notification LED not working (LED is working only when charging), Double Tap To Wake not working.
This guide has been written by oieNao/TH3WH1T3WOLF, don't forget to quote if you post it somewhere else, a "thanks" would be appreciated
oieNao said:
I am writing this guide with all the steps I did to successfully boot Android P on my Whyred device, I am not responsible for any damage, brick, dead SD and so on
Click to expand...
Click to collapse
is your camera working?
Tyrany said:
is your camera working?
Click to expand...
Click to collapse
Nope, seems like camera is not working at all. I even enabled camera2api manually and tested both Footej Camera and GCAM with no results.
oieNao said:
Nope, seems like camera is not working at all. I even enabled camera2api manually and tested both Footej Camera and GCAM with no results.
Click to expand...
Click to collapse
did you try any legacy camera like mi camera for custom roms?
or try this adb logcat | grep cam and grab a log please
Do i need to Formal my data?
Tyrany said:
did you try any legacy camera like mi camera for custom roms?
or try this adb logcat | grep cam and grab a log please
Click to expand...
Click to collapse
So I connect the phone to my pc and simply use the command you wrote to take a log? You think then we'll be able to fix cam?
No I didn't try mi camera for custom roms but...is there any zip file to flash it? So maybe I'll be able to do it...
AlishaSama said:
Do i need to Formal my data?
Click to expand...
Click to collapse
Yes.
oieNao said:
Yes.
Click to expand...
Click to collapse
stock camera https://forum.xda-developers.com/re...miui-stock-camera-portrait-mode-dual-t3816069
for the log cat you enter the adb console, check adb devices and if the device appears run the command
Ty
oieNao said:
Yes.
Click to expand...
Click to collapse
Kay....
Ty....
Tyrany said:
did you try any legacy camera like mi camera for custom roms?
or try this adb logcat | grep cam and grab a log please
Click to expand...
Click to collapse
So MIUI Stock Cam isn't working and from adb it says "grep" is not a recognised command...any other way I should try?
I simply did "adb devices" and then I pasted "adb logcat | grep cam", did I do it right?
EDIT: I do not have linux so I can't do anything with grep.
the gcam is working for me also ar stickers work but not the front hdr as I have the ai variant. however the miui cam for custom roms does not work. also can't get mtp...
the thing that is missing in your tutorial is that it does not boot with an encrypted data partition. I had to "format data" ( the option available in wipe menu which wipes data and internal storage) than install mokee and than flash no-verity, boot up and afterwards continue with the installation. this is mentioned in the original tutorial.
Anyone tried DP4!?
Hrishi1834 said:
Anyone tried DP4!?
Click to expand...
Click to collapse
my comment above was about dp4
B!GBOY said:
my comment above was about dp4
Click to expand...
Click to collapse
Is playstore working?
Hrishi1834 said:
Is playstore working?
Click to expand...
Click to collapse
yes, after you install the gmscore linked in the OP it works.
this is basically a giant hack to get a preview software working on a device it didn't meant to, so the fact that so many things work as expected is a big deal (thanks to project treble).
btw my mobile data does not work on the second sim and the camera situation is really messy
somehow arnova8g2 camera works but you cant get in to its settings as it remembers there's no camera
but dont expect a daily driver. it's just fun playing with stuff and trying new things
B!GBOY said:
yes, after you install the gmscore linked in the OP it works.
this is basically a giant hack to get a preview software working on a device it didn't meant to, so the fact that so many things work as expected is a big deal (thanks to project treble).
btw my mobile data does not work on the second sim and the camera situation is really messy
somehow arnova8g2 camera works but you cant get in to its settings as it remembers there's no camera
but dont expect a daily driver. it's just fun playing with stuff and trying new things
Click to expand...
Click to collapse
How to root ? use the normal magisk zip?
---------- Post added at 10:54 AM ---------- Previous post was at 10:25 AM ----------
Hrishi1834 said:
How to root ? use the normal magisk zip?
Click to expand...
Click to collapse
Do I have to enable camera2API?
Please send the link of the Gcam.
oieNao said:
I am writing this guide with all the steps I did to successfully boot Android P on my Whyred device, I am not responsible for any damage, brick, dead SD and so on.
All you have to do is:
-Boot to Recovery (you'll need a Treble Recovery).
-Go to "Clean" section and perform a Factory Reset by swiping the arrow below.
-On "Clean" section tap "Advanced Clean" and select all the partitions (Internal storage, USB-OTG and microSD excluded).
-Go to "Install" section and install last MoKee Rom (in order to boot Android P you'll need MoKee's Vendor).
-After you succesfully installed MoKee rom's zip, go back to recovery main menu and then again "Install" but now press "Install IMG file" and select P-DP3-sGSI.img mounting it as System Image.
-Now go back to recovery main menu and then tap on "Mount" section, here simply uncheck and then check again "vendor".
-Go back to "Install" and then simply install the three files which come after the installation of P-DP3-sGSI.img (POST-sGSI_1_v0.9.zip, POST-sGSI_2_v0.12.zip and POST-sGSI_3.zip in this exact order).
-Simply reboot to System and...you're DONE!
If you want Magisk, you'll need to flash it simply going back to Recovery mode but this only after you firstly setup the phone! (Also I don't know if there is a Magisk.zip compatible with Project Treble for Whyred. EDIT: Magisk 16.6 is working flawlessly).
Here some useful links:
Treble Recovery: https://dl.twrp.me/whyred/
MoKee Rom: https://download.mokeedev.com/?device=whyred&type=nightly
Android P files: https://androidfilehost.com/?w=files&flid=275999
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Some useful infos from Android P GSI's topic:(https://forum.xda-developers.com/pr...nt/rom-android-p-developer-preview-t3816659):
How to fix mtp:
Enable developer settings (Please google to know if you don't know)
Scroll down to select Default USB Configuration
Select File Transfer
Fix google account and playstore:
install https://tinyurl.com/gmscore
Have in-call audio bug?
flash (need vendor and system to be munted) : https://androidfilehost.com/?fid=5862345805528048703
Here some screenshots! :
Here a video review of Android P by TechDroider: https://www.youtube.com/watch?v=YguzLYgV1Jg
KNOWN BUGS: Camera not working, even when enabling HAL3 manually from build.prop, tested both Footej Camera and GCAM; Notification LED not working (LED is working only when charging), Double Tap To Wake not working.
This guide has been written by oieNao/TH3WH1T3WOLF, don't forget to quote if you post it somewhere else, a "thanks" would be appreciated
Click to expand...
Click to collapse
HI Could anyone please tell me if we could go back to installing/ flashing oreo custom roms or the miui 9 nougat rom normally/regularly if we install this android p GSI? I hope it allows for such downgrade!! However I'm not sure as it may make changes to partitioning? Please someone reply!!
---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------
B!GBOY said:
the gcam is working for me also ar stickers work but not the front hdr as I have the ai variant. however the miui cam for custom roms does not work. also can't get mtp...
the thing that is missing in your tutorial is that it does not boot with an encrypted data partition. I had to "format data" ( the option available in wipe menu which wipes data and internal storage) than install mokee and than flash no-verity, boot up and afterwards continue with the installation. this is mentioned in the original tutorial.
Click to expand...
Click to collapse
Hi, you seem to have gone through the whole process of installing so could you tell me if you can flash oreo custom roms or miui 9 nougat regularly once we install this gsi image this way? What if I don't want to stick there so can I go back easily by flashing any rom using twrp or flashing miui via fastboot?
Is it stable enough to be used as a daily driver?
Hrishi1834 said:
How to root ? use the normal magisk zip?
Do I have to enable camera2API?
Please send the link of the Gcam.
Click to expand...
Click to collapse
read the first post about how to install magisk.
yes
checkout arnova8g2 thread in apps and themes section
Thetpcguy said:
HI Could anyone please tell me if we could go back to installing/ flashing oreo custom roms or the miui 9 nougat rom normally/regularly if we install this android p GSI? I hope it allows for such downgrade!! However I'm not sure as it may make changes to partitioning? Please someone reply!!
Hi, you seem to have gone through the whole process of installing so could you tell me if you can flash oreo custom roms or miui 9 nougat regularly once we install this gsi image this way? What if I don't want to stick there so can I go back easily by flashing any rom using twrp or flashing miui via fastboot?
Click to expand...
Click to collapse
it does not contain a firmware update. A GSI is literally only a system image so it does not affect that.
you use the mokee for vendor and other stuff and the system image from the GSI
make a backup from everything
ajul_raj said:
Is it stable enough to be used as a daily driver?
Click to expand...
Click to collapse
read my last posts ( short answer: imho no )
Related
{
"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"
}
This is a Official Build of madOS ( based on AOSP Oreo ) for Wiko Fever (2gb ram and 3gb ram) with MTK 6753 SoC and its clones:
Micromax Canvas 5 E481
Blu Life One X
Myphone 36
Qmobilez10
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.
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.
*/
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors
Lights;
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Not working:
XDA:DevDB Information
madOS_O_FEVER, ROM for all devices (see above for details)
Contributors
DerTeufel1980, fire855, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: unlocked bootloader, twrp
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-03-19
Created 2018-03-13
Last Updated 2018-03-22
First time Install Instructions
0) Preparation
0.1) Backup your important data to PC
0.2) Ensure you are running Wiko Fever Android 6 already (also/especially when your device is not wiko fever, but a clone). If you are not, please update to it, before continuing here (replace the preloader from the wiko rom with your stock one, then use 'firmware upgrade' mode in sp flashtool. NEVER use 'format all + download')
Extra steps, if you are on blu life one x:
https://forum.xda-developers.com/showpost.php?p=76003104&postcount=81
0.3) Download “twrp_wiko_fever_oreo.img“: [url]http://www.mediafire.com/file/e96x8ltlyka392e/twrp_wiko_fever_oreo.img[/URL]
0.4) Download “madOS_8.1.0_fever_2018xxyy.zip“ [url]https://www.facebook.com/MediatekAndroidDevelopers/[/URL]
0.5) Optional, Download “Google Apps (aka Gapps)“: [url]http://opengapps.org/[/URL]. Choose: “ARM64“, “Android 8.1“, “nano“ or “pico“ package
1) Unlock bootloader (if not done already):
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking” and “USB debugging” (if not enabled already), and choose to alollow usb debugging in the popping up window.
1.2) Boot the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
2) Flash the recovery and boot to it. (choose option a) if you don't have another TWRP already installed, else choose b))
2.1a) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader").
Then execute command “fastboot flash boot twrp_wiko_fever_oreo.img”;
and then “fastboot reboot” (this is a trick to directly bring you to the newly flashed recovery. You can't boot up your current/stock rom at this point anymore).
2.1b) Boot to your current TWRP. Choose install --> image, and select “twrp_wiko_fever_oreo.img“. Then choose “recovery“ as the target. After few seconds, and succesful installation, hit “back“ several times, then go to “reboot --> recovery“
3) Install
3.0) Optional, but recommended: Go to "Wipe --> Advanced Wipe", click "Cache" and then "Repair or Change File system". Then select "Change File system" and choose "F2FS". Swipe to confirm.
Hit "back" three times (you can again choose a partition to change now). Choose "Data" and do as above.
Hit "back" several times, to get back to the main menu. Choose "Reboot --> Recovery".
3.1) While already in recovery (TWRP), connect your phone to pc, and copy “madOS_8.1.0_fever_2018xxyy.zip“ and the Google Apps to your phone.
3.2) Go to "Wipe", and directly slide the slider to the right.
3.3) Get back to main menu with the "back" button
3.4) Go to "Install" and hit “madOS_8.1.0_fever_2018xxyy.zip“, then uncheck all boxes and hit "Add more zips", now choose the Google Apps.
Confirm installation by swiping the slider to the right.
3.5) Reboot System
Click to expand...
Click to collapse
Follow up Install Instructions
Download rom and gapps
boot to recovery
flash rom and gapps
optional: flash superSu/Magisk
reboot system
General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery for OREO 8.1.0
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Update: On Oreo 8.1.0:
- We have extended Theme support even further ( madLauncher, messaging, etc)
- As well as many fixes
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 onwards.)
2: Super SU ( v2.82 onwards)
IF there are problems in rooting, you need to report it to the root-threads...There's nothing we can do
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A: openGapps arm64 nano/pico
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
Pure Nexus
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...
Changelog 19th March 2018:
fixed offline charging
fixed proximity and light sensor
fixed applying smartwake settings after reboot
Facebook release post: https://www.facebook.com/notes/mad/rom-810-official-mados-wiko-fever-mt6753/1640799096003857/
for whatever reason, devDB is not working (very well) at the moment...causing this thread to be shown up, hours after i created it....now it's finally here and updated...and can be used
Thank u so much sir...we owe you?
superdragonpt said:
Android Oreo released
https://forum.xda-developers.com/android/development/rom-official-mados-wiko-fever-clones-t3762804
Click to expand...
Click to collapse
superdragonpt said:
The ROM was made using an Wiko device in the bring up
I know very well this TINNO devices, that are rebranded to many OEMs
In case of baseband (ie: BLU,Qmobile, MMX, you should use your stock baseband modem and place it under vendor/etc)
Cheers
PS: can you, that have other clones ( non-wiko) send us your working baseband?
(This way, we could perhaps just made an flashable zip for baseband or so)
Click to expand...
Click to collapse
Here is firmware folder(baseband) from Life One X with MM update.
Opened an issue about some sensors
https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
mrmazak said:
Here is firmware folder(baseband) from Life One X with MM update.
Click to expand...
Click to collapse
FERRARI81 said:
Opened an issue about some sensors
https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
Click to expand...
Click to collapse
Great
This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc
For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
superdragonpt said:
Great
This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc
For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
Click to expand...
Click to collapse
So the sensor.lib from Blu?
I will pull it and share.
superdragonpt said:
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
Click to expand...
Click to collapse
Ehm...I have not blue, I have original Wiko Fever
And...I'm noob ...in wich way I could check what's the sensor?
FERRARI81 said:
Ehm...I have not blue, I have original Wiko Fever
And...I'm noob ...in wich way I could check what's the sensor?
Click to expand...
Click to collapse
just because adaptive brightness is not working , does not mean it is the sensor.
If sensor was not working , there is another test (check) you can do.
make a call, then put phone to head and see if screen goes off.
I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.
I am away from my LOX now and for few days , so cant give direct test of light sensor.
attached just in case is usefull here are sensor libs from BLU-LOX. They are in /system/lib/hw and /system/lib64/hw.
I believe on oreo they go into /vendor/
Can we flash it over stock Lollipop ROM of Micromax Canvas 5 ??
I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65.
Thanks
mrmazak said:
just because adaptive brightness is not working , does not mean it is the sensor.
If sensor was not working , there is another test (check) you can do.
make a call, then put phone to head and see if screen goes off.
I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.
Click to expand...
Click to collapse
It doesn't work in call too : the screen is always on.
QUIZILLA said:
I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65.
Thanks
Click to expand...
Click to collapse
Please remove the quote of the whole FAQ. This is totally useless to ask your question...
You need to flash wiko mm rom first
FERRARI81 said:
It doesn't work in call too : the screen is always on.
Click to expand...
Click to collapse
I'll check it today
Hello, I write from Padova, Italy,
I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.
Can I do this update procedure with this problem?
I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.
Riccardo
ianto:
Rikadoo said:
Hello, I write from Padova, Italy,
I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.
Can I do this update procedure with this problem?
I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.
Riccardo
ianto:
Click to expand...
Click to collapse
Why root? To update to oreo, you don't need root... But you still need to copy the new rom to your phone, as well as unlock the bootloader and install the twrp recovery. This needs to be done in fastboot mode by pc. I'd suggest to just try it
Unfortunately I am not very experienced, but I am very interested in solving my problem. I want to install this ROM, but without having to connect the device to the PC.
If I copy the ROM on the SD card. Can I then install?
I am in process of installing new oreo twrp and MADOS.
During install of TWRP, I loose adb authorization. (adb session is "unathorized")
in "prop.default" it has
Code:
ro.secure=1
security.perf_harden=1
ro.adb.secure=1
ro.allow.mock.location=0
ro.debuggable=0
is this intentional?
additional question,
Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.
I think the adb auth problem is my pc, my other phone just started to do this too.
edit:
I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.
tried just adding blu files ontop of original rom files.
tried removing rom files and adding blu files
tried removing whole folder then adding blu folder
each time I get unknown baseband.
I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
One and more questions,....
1. Our bootloader is blocked or already unlocked?
2. If is locked, to unlock the bootloader of our device wiko fever which app I have to install?
3 if isn't locked, how I install a custom recovery like twrp manager?
4 how I boot the custom recovery twrp manager? Maybe if I switch off the device and reboot it, starts automatically the custom recovery?
5 at the end, from twrp can I flash the ROM Oreo?
AHH , last question, can I flash this ROM from my phone with Android MM?
mrmazak said:
I am in process of installing new oreo twrp and MADOS.
During install of TWRP, I loose adb authorization. (adb session is "unathorized")
in "prop.default" it has
is this intentional?
additional question,
Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.
I think the adb auth problem is my pc, my other phone just started to do this too.
edit:
I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.
tried just adding blu files ontop of original rom files.
tried removing rom files and adding blu files
tried removing whole folder then adding blu folder
each time I get unknown baseband.
I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
Click to expand...
Click to collapse
Someone already uploaded vendor files for his model... Was it you? If not, please upload it for us
I'm not responsible for whatever damage this could possibly cause to your device.
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Welcome to GSI For Galaxy A7 2018 ONLY FOR A750F/A750FN/A750GN
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
If any bugs you face, Report them to the appropriate Threads of the GSI you installed or github issues section, as those are not mine to fix i only provide the Guide and kernel that allows GSIs to run on.
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
All Sensors
- QUANTUM KERNEL FEATURES:
CPU Governors
I/O Schedulers
TCP Algorithms
WireGuard Support
Drivedroid support (0.10.48+)
Boeffla wakelock blocker v1.1.0
and many more here https://forum.xda-developers.com/galaxy-a7/development/kernel-quantum-kernel-v1-0-t3923731
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
Flash "GSI_Fix_boot.zip"
Flash "Quantum_Kernel_GSI_V2.zip".
- STEPS FOR INSTALLING GAPPS
Download the appropriate opengapps
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- FOR INSTALLING FIXES:
Camera Fixes (Flash only on NON Working GSIs)
- KNOWN BUGS:
Fingerprint
Bluetooth calls are broken
No Network bars (Calls/data works)
May be more, Let me know
Credits:
- @jdstrydom for testing
Downloads. F.A.Qs below
Kernel Source
XDA:DevDB Information
Guide on How to flash GSI, for the Samsung Galaxy A7 (2018)
Contributors
prashantp01
ROM OS Version: 9.0 Pie
Version Information
Status: Beta
Created 2019-05-26
Last Updated 2019-05-26
{
"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"
}
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Generic System Image (GSI) : Github
Treble folder : Gdrive
---------------------------------------------------------------
Bugs :
1- some users might face SDCard issues
If you did , back up its data and format it in GSI.
2- If you face "Error 70: Insufficient storage space available in the system partition" while flashing Gapps
If you get do this : Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
F.A.Q
Q : Do i need to format internal storage ?
A : No
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : No, only A-ONLY_ARM64 Are supported
Q : Can i flash any sGSIs ?
A : No unless they match the Arch above
prashantp01 said:
[...]
- KNOWN BUGS:
Fingerprint
[...]
Click to expand...
Click to collapse
Fingerprint works with phhusson GSI ROM (following this thread) . Did the vendor image or kernel you posted here introduce that issue?
Do you have a list of working GSI ROMs for A750x? Only phhusson GSI ROM worked ever when following the above linked thread. Will any GSI ROM (A-Only, Arm64) work if I flash the vendor image and kernel you provided?
blazzer12 said:
Fingerprint works with phhusson GSI ROM (following this thread) . Did the vendor image or kernel you posted here introduce that issue?
Do you have a list of working GSI ROMs for A750x? Only phhusson GSI ROM worked ever when following the above linked thread. Will any GSI ROM (A-Only, Arm64) work if I flash the vendor image and kernel you provided?
Click to expand...
Click to collapse
Fingerprint is bugged on Pie vendor, earlier on oreo vendor it was working. For recommendations follow this link : https://drive.google.com/drive/folders/1hOWkrrYWxfseFe1mbM7jJ1NQakzse6SS?usp=sharing
prashantp01 said:
Fingerprint is bugged on Pie vendor, earlier on oreo vendor it was working. For recommendations follow this link : https://drive.google.com/drive/folders/1hOWkrrYWxfseFe1mbM7jJ1NQakzse6SS?usp=sharing
Click to expand...
Click to collapse
Thank you! Will check them out.
Screen Lock (PIN) is broken, tried the following pie ROMS: phhusson, Resurrection Remix, OmniROM. ViperOS did not boot.
When the Screen Lock (PIN) is set it is does not come into effect immediately. Turning off and turning on the screen does not present the enter PIN dialouge. When restarted the screen is locked but screen randomly blacks out giving no chance to enter PIN. Doesn't seem to be particular to any ROM since it is observed across ROMs.
blazzer12 said:
Screen Lock (PIN) is broken, tried the following pie ROMS: phhusson, Resurrection Remix, OmniROM. ViperOS did not boot.
When the Screen Lock (PIN) is set it is does not come into effect immediately. Turning off and turning on the screen does not present the enter PIN dialouge. When restarted the screen is locked but screen randomly blacks out giving no chance to enter PIN. Doesn't seem to be particular to any ROM since it is observed across ROMs.
Click to expand...
Click to collapse
It didn't booted because u didn't followed my thread steps.... whenever u flash gsi then make a reboot to recovery and then flash whatever fix is needed
prashantp01 said:
It didn't booted because u didn't followed my thread steps.... whenever u flash gsi then make a reboot to recovery and then flash whatever fix is needed
Click to expand...
Click to collapse
They booted FINE with no issues. When I try to put a lock screen it's not working. Screen blacks out at enter pin dialog.
blazzer12 said:
They booted FINE with no issues. When I try to put a lock screen it's not working. Screen blacks out at enter pin dialog.
Click to expand...
Click to collapse
It should work, do this go back to official stock pie and then try again, there should be no issues
prashantp01 said:
It should work, do this go back to official stock pie and then try again, there should be no issues
Click to expand...
Click to collapse
Flashed stock ROM and updated to the latest version. Installed TWRP and followed instructions in the OP. Setting a screen lock PIN still results in black out on lock screen.
blazzer12 said:
Flashed stock ROM and updated to the latest version. Installed TWRP and followed instructions in the OP. Setting a screen lock PIN still results in black out on lock screen.
Click to expand...
Click to collapse
Weird, join our telegram group and let's figure out the issues
prashantp01 said:
Weird, join our telegram group and let's figure out the issues
Click to expand...
Click to collapse
The telegram link has expired!
s_karimi said:
The telegram link has expired!
Click to expand...
Click to collapse
No lol
blazzer12 said:
Flashed stock ROM and updated to the latest version. Installed TWRP and followed instructions in the OP. Setting a screen lock PIN still results in black out on lock screen.
Click to expand...
Click to collapse
This issue might be due to bad vendor partition. If you have been flashing official stock firmware through ODIN and still facing issues you might try flashing* Quantum Stock V2 and then following the instructions in the OP as usual.
*the intention is to flash a firmware that will install a correct vendor partition.
Issues I faced before this solution: Setting lock screen PIN resulted in soft reboots and screen flicker making it impossible to get past lock screen. Impossible to set fingerprint since lock screen PIN is broken (Says PIN in wrong no matter what). `Bitwaden` password manager app force closed. I don't face these issue anymore.
Joining the telegram channel in OP helped me with this issue. :good:
LineageOS 16.0 from this link work well !
Choose "avN" version.
For OpenGapps choose the pico version.
If you get "Error 70: Insufficient storage space available in the system partition" do this :
Make sure Internal Storage is mounted (Mount > Select Storage > Internal Storage)
Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
Lenny Bard said:
LineageOS 16.0 from this link work well !
Choose "avN" version.
For OpenGapps choose the pico version.
If you get "Error 70: Insufficient storage space available in the system partition" do this :
Make sure Internal Storage is mounted (Mount > Select Storage > Internal Storage)
Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
Click to expand...
Click to collapse
Can you give me a pm on how tou instled it from the start? You got GN?
dlsygaco said:
Can you give me a pm on how tou instled it from the start? You got GN?
Click to expand...
Click to collapse
I have the FN version.
What problem do you have ?
Hello how are you
I tell you my situation, I have a Galaxy A7 (2018) SM-A750GN, which was rooted without problems using MAGISK 6 when I updated it and restarted the phone, it was left with a BootLoop (Samsung black screen and first home screen turned off alone and returned) reinstall firmware using ODIN 3.13.1 and all good, then perform all the processes, running, root and all good ... update the Magisk and the BootLoop is back
I repeated the indicated processes and everything was fine ... just ship the way to correct that Samsung Pass could run on the computer with root, install Xposed and nothing happened, I continued with the process to give security using the fingerprint, and it stuck with the password, return to Recovery Mode, and insists reinstalling ANOTHER firmware for the same phone but this time the process was stuck in Odin and computer abusedly disconnected the cable from the computer and the Odin was stuck, but the computer resumed its functions.
Now I have my Galaxy A7 with a beautiful BootLoop that lasts 4 sgds, very fast I see an exclamation point, the android robot and texts that I can't read well, using the keys I can't turn off just restarting. Samsun logod appears a vibration, black screen and the elements just mentioned before appear ...
My query is simple: Can anything be done? Is Brickeado or Killing ... ???
a hug and thanks in advance
Is there any way to fix the network icons they are empty on every gsi rom and any possible way to get volte work on gsi?
{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
******************************************
Hi there,
This is the official build (beta) based on TWRP sources and xiaomi blobs ... fully working !
(Mi CC9 meitu Edition)
!!! IT'S NOT MY PROBLEM, IF YOU DON'T READ AND FOLLOW MY INSTRUCTION CAREFULLY, IF YOU DON'T HAVE TIME FOR THIS, OR IF YOU FLASH SOMETHING OR DO A MANIPULATION I DIDN'T MENTION HERE !!!
Installation Procedure (first time) :
- Unlock your bootloader D)
- Enable ADB from your Official MIUI Developer option
- Plug your USB cable to your Windows PC and type :
adb reboot bootloader
- type then :
fastboot flash recovery twrp-3.3.1-0-vela-final (auto-decrypt).img (rename your image just by twrp.img)
fastboot flash vbmeta vbmeta.img
fastboot reboot (keep Vol+ pressed until you see TWRP splash)
- Wait for decrypting ... (if already you set a lockscreen pattern or a fingerprint)
- Format Data (button on the right) + Type "yes" on the keyboard popup
- Reboot
- To boot TWRP from MIUI : reboot menu + keep Volume UP pressed.
- To boot from phone off : power button + Volume UP
TWRP can now auto-decrypt your crypted /data partition so you can make backup with no issue.
This is a big fix that prevent to loose your fingerprint and pattern ...
For MIUI users, you must flash the fstab.zip fix after flashing your MIUI rom !!!
Enjoy ! :good:
Update : 2019-11-05
-version : 3.3.1-0
-busybox update
-terminal fixed
-stable and optimized : setting lockscreen pattern and fingerprint on the first boot is no longer needed !
BE SURE WHEN YOU WIPE YOUR DATA, YOU KEEP THE "4 FOLDERS BELOW + .layout_version". THESE ARE YOU ENCRYPTION DATA. IF YOU DELETE THEM, YOU WILL NOT BE ABLE TO RESTORE YOUR DATA BACKUP UNTIL YOU FORMAT YOUR DATA AGAIN.
TRICK TO SAVE YOUR LIFE : ALWAYS KEEP YOUR BACKUPS ON THE EXTERNAL STORAGE !!!
!!! This recovery is only for flashing "vela" roms in the future. Don't use it to flash pyxis roms. For this, use pyxis recovery instead !!!
Download
link
XDA : DevDB Information
TWRP, Tool/Utility for the Mi CC9 meitu Edition (vela)
Contributors
gringo80
Source Code 1 : https://github.com/TeamWin
Source Code 2 : Prebuilt Recovery Kernel from MIUI
Version Information
Status : Stable
Release Date : 2019-11-05
Hi.
First of all, thank you so much for all the time and effort you have put in to make this recovery for all of us.
Second, The url is bad I get a 404 error.
I would appreciate it if you could resend the correct link.
yotamy said:
Hi.
First of all, thank you so much for all the time and effort you have put in to make this recovery for all of us.
Second, The url is bad I get a 404 error.
I would appreciate it if you could resend the correct link.
Click to expand...
Click to collapse
It's working now. Thanks
I think it works
gringo80 said:
It's working now. Thanks
Click to expand...
Click to collapse
I did all your that you have instructed.
All my data was deleted, due to format data in twrp.
i will continue to test it and let you know.
@gringo80 , what will it take for you to create a global rom for this device?
yotamy said:
I did all your that you have instructed.
All my data was deleted, due to format data in twrp.
i will continue to test it and let you know.
@gringo80 , what will it take for you to create a global rom for this device?
Click to expand...
Click to collapse
i need time. may be next week !
btw, i'm working on a GSI patch. Some issues need to be fixed. I'm focusing myself now on this !
thanks. Some QA
gringo80 said:
i need time. may be next week !
btw, i'm working on a GSI patch. Some issues need to be fixed. I'm focusing myself now on this !
Click to expand...
Click to collapse
@gringo80 , you are the best!
you made me so happy.
you dont have to apologize or to explain yourself regarding the ROM . you are great
if you can send me a link to tutorial for creating a rom i will start the learning process
after examining the recovery:
1. it works! it identifies vela official rom
2. can not create twrp backup.
there is an error message after the attempt to backup DATA.
"create tar fork() process ended with error: 255" (attached recovery log and screenshot)
3. when choosing to install from internal storage, I get a list of unidentified folders
when you go up one level, everything is ok with the folders names (attached screenshot)
this is a minor bug
4. when changing things in settings, like "reversed navbar layout"
after reboot the values are changing to the original values. they are not saved.
this is a minor bug
Yotam
yotamy said:
@gringo80 , you are the best!
you made me so happy.
you dont have to apologize or to explain yourself regarding the ROM . you are great
if you can send me a link to tutorial for creating a rom i will start the learning process
after examining the recovery:
1. it works! it identifies vela official rom
2. can not create twrp backup.
there is an error message after the attempt to backup DATA.
"create tar fork() process ended with error: 255" (attached recovery log and screenshot)
3. when choosing to install from internal storage, I get a list of unidentified folders
when you go up one level, everything is ok with the folders names (attached screenshot)
this is a minor bug
4. when changing things in settings, like "reversed navbar layout"
after reboot the values are changing to the original values. they are not saved.
this is a minor bug
Yotam
Click to expand...
Click to collapse
this is not a bug. you have to format data after installing twrp.
from twrp homescreen, go to :
Wipe > Format Data (on the right) > type yes from the keyboard
TWRP don't support backup/ restore from encrypted files/folders. You must decrypt by formatting data !
Reboot to system. Install and config your rom then go TWRP to make backup !
Always put your roms and zip on the External SD Card... or sideload them by adb cmd from your windows PC !
Flash fstab.zip (OP) to avoid the encryption again by your MIUI rom !
sorry. i dont understand
gringo80 said:
Flash fstab.zip (OP) to avoid the encryption again by your MIUI rom !
Click to expand...
Click to collapse
fstab = file system table?
where do i find it?
flash it how? via twrp or fastboot?
yotamy said:
fstab = file system table?
where do i find it?
flash it how? via twrp or fastboot?
Click to expand...
Click to collapse
lol
it's inside the zip. go to my mediafire link. you will find everything
yes you flash it on twrp
i cannot thank you enough
thanks again
New Update (TWRP auto-decrypt)
yotamy said:
i cannot thank you enough
thanks again
Click to expand...
Click to collapse
Please update you TWRP ! (Highly recommended). Read OP carefully !
Thanks
:good:
You are the best.
I hope this will fix the issue I have with the fingerprint scanner. It's not working well since the twrp
yotamy said:
You are the best.
I hope this will fix the issue I have with the fingerprint scanner. It's not working well since the twrp
Click to expand...
Click to collapse
Yes, the fingerprint and the lockscreen pattern.
Follow the instruction on the OP !
Are the font files related to this twrp?
There are 2 font files in the link
yotamy said:
There are 2 font files in the link
Click to expand...
Click to collapse
NO, for the roms !
Speaking of roms.....
yotamy said:
Click to expand...
Click to collapse
work in progress
now its working good
gringo80 said:
work in progress
Click to expand...
Click to collapse
@gringo80 ,
the recovery works better now and recognizes fingerprint and lockscreen pattern
1. do you know why this twrp does not save my request to reverse navbar?
after each reboot it returns to the original values
2. in the rom, do you know how I can add 3 way reboot or advanced reboot?
in the china rom, under developer options, I dont have this option like in xiaomi.eu rom.
Thanks again @gringo80 for all the time and effort you put in
Yotam
yotamy said:
@gringo80 ,
the recovery works better now and recognizes fingerprint and lockscreen pattern
1. do you know why this twrp does not save my request to reverse navbar?
after each reboot it returns to the original values
2. in the rom, do you know how I can add 3 way reboot or advanced reboot?
in the china rom, under developer options, I dont have this option like in xiaomi.eu rom.
Thanks again @gringo80 for all the time and effort you put in
Yotam
Click to expand...
Click to collapse
Don't delete TWRP folder on your internal storage, to keep your TWRP settings.
3 way reboot is framework related. Sorry i don't support MIUI for now because i'm busy with GSI. Try to download "Simple Reboot" from the playstore.
{
"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"
}
YOU ARE THE SOLE RESPONSINLE FOR WHAT HAPPENS TO YOUR DEVICE. PROCEED WITH CAUTION!
Hi all! I should have posted this years ago but anyways... This rom is made due to the fact that there is no bug-free rom for Galaxy J8, not even any development going on. So, I decided to de-bloat the latest stock firmware, polish it a bit, configure some settings and fix some of the issues.
Twrp and Root Guide: https://forum.xda-developers.com/t/...d-flash-twrp-j810f-g-m-y-gf-j8y18lte.4479201/
WORKING
Everything that works on stock rom, including VOLTE.
NOT WORKING
Nothing.
CHANGELOG
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder.
BLOATWARE LIST
Read the "More Info About Bloatwares" pdf file inside the Google Drive folder.
INSTRUCTIONSHOW TO MAKE A CLEAN INSTALLATION (WARNING! YOU WILL LOSE ALL YOUR DATA INCLUDING INTERNAL STORAGE -pictures, songs, downloads, files, apps etc.-)
1. Install/Update TWRP (use v3.5.0) (big thanks go to goldfish07)
2. Create backup, INCLUDING VENDOR (everything you need - including your files in internal storage - use an external storage if possible)
3. Reboot into TWRP. Navigate to Wipe/Format Data type yes and apply it. Then, go to Wipe-Advanced Wipe, select ONLY these "Dalvik/Art Cache - System - Vendor - Data - Cache" and format them.
4. Copy "J8_De-Bloated_Stock_Rom_v7.1.zip" to your internal or external storage and flash it.
5. Reboot and enjoy! (it might say "NO OS INSTALLED", it is normal when you format system from advanced wipe and then install the zip, just swipe and system will start) (first boot may take a couple of minutes, please be patient, YOU WILL ONLY SEE THE "SAMSUNG LOGO", NOT the animation and it is NORMAL)
HOW TO MAKE A DIRTY INSTALLATION (ONLY IF YOU ARE COMING FROM ANOTHER VERSION OF DEBLOATED ROM) (YOU WILL NOT LOSE ANY DATA)
1. Open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android.
2. Go inside the "data" folder and delete the 3 folders (adb, app, system). Do not delete the "local" folder.
3. Copy the "J8_De-Bloated_Stock_Rom_v7.1.zip" to your phone.
4. Reboot into TWRP.
5. Flash the "J8_De-Bloated_Stock_Rom_v7.1.zip".
6. When installation completes, select "Wipe cache/dalvik" and swipe.
7. Reboot and enjoy!
Contributors
goldfish07 (Ayush Bisht) for anykernel and TWRP
Kernel Source (thanks to goldfish07 (Ayush Bisht))
GitHub - goldfish07/android_kernel_samsung_j8y18lte: base: LA.UM.8.6.r1-04700-89xx.0
base: LA.UM.8.6.r1-04700-89xx.0. Contribute to goldfish07/android_kernel_samsung_j8y18lte development by creating an account on GitHub.
github.com
ROM INFO:
Security Patch Level2021-12-01OS VersionAndroid 10PDAJ810FJXU6CVA1
Download: https://tinyurl.com/J8-Debloated-Rom
Reserved
New Update v7.1!
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder for changelog details.
BNFCTR said:
New Update v7.1!
Read the "!!! READ ME FIRST !!!" text inside the Google Drive folder for changelog details.
Click to expand...
Click to collapse
Hi, thank you firstly.
I installed this rom everythink is ok but no internet connection.
Any solution?
sinanlenfom said:
Hi, thank you firstly.
I installed this rom everythink is ok but no internet connection.
Any solution?
Click to expand...
Click to collapse
Please follow the clean installation steps carefully.
Hi bro thank you so much this rom work perfectly everything work thanks a lot
Download link (https://tinyurl.com/J8-Debloated-Rom) is not working ((
Who can share it?
there is a way to make a ROM to make the touch work, I have a j810m and the touch stopped after updating to Android 10 binary 3 version, I had changed the display and I didn't know I couldn't update
Cheat said:
Download link (https://tinyurl.com/J8-Debloated-Rom) is not working ((
Who can share it?
Click to expand...
Click to collapse
The link is working. Please try using another browser or use vpn.
jabsjrm said:
there is a way to make a ROM to make the touch work, I have a j810m and the touch stopped after updating to Android 10 binary 3 version, I had changed the display and I didn't know I couldn't update
Click to expand...
Click to collapse
While system update check, it also verifies your display originality. If you change your display on untouched stock rom, it will be permanently disabled unfortunately. You should have upgraded to debloated rom or disabled system update apps so that you could keep using changed display. There is no luck fortunately. (you cannot downgrade to Android 9 to solve the issue because bootloader does not allow that)
This and the "More info about bloatwares" is great, thanks for all your efforts. The device is finally usable without stutter even when scrolling.
But there is a small thing -> I think you should remove default magisk so that it can be installed with app and be able to update.
erfto said:
This and the "More info about bloatwares" is great, thanks for all your efforts. The device is finally usable without stutter even when scrolling.
But there is a small thing -> I think you should remove default magisk so that it can be installed with app and be able to update.
Click to expand...
Click to collapse
You're welcome. I configured some of the Magisk settings so that you do not need to do anything so as to be able to successfully pass SafetyNet. Additionally, If I remove default installation of Magisk as an app, stub app will give you error while downloading the app unfortunately. Lastly, Magisk v24.3 is the latest working version for J8. Magisk v25.x versions will bootloop the device. Therefore, do not attempt to update Magisk. Considering these issues, I decided to include Magisk and its configurations. If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.
BNFCTR said:
You're welcome. I configured some of the Magisk settings so that you do not need to do anything so as to be able to successfully pass SafetyNet. Additionally, If I remove default installation of Magisk as an app, stub app will give you error while downloading the app unfortunately. Lastly, Magisk v24.3 is the latest working version for J8. Magisk v25.x versions will bootloop the device. Therefore, do not attempt to update Magisk. Considering these issues, I decided to include Magisk and its configurations. If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.
Click to expand...
Click to collapse
I'm not knowledgable about this but i get it now, thanks for informing !
where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev
X - root said:
where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev
Click to expand...
Click to collapse
just do what was posted above?
BNFCTR said:
... SNIP ... If you still want to remove it, open "J8_De-Bloated_Stock_Rom_v7.1.zip" using the latest version of "WinRAR" on pc or the latest version of "RAR" on Android. Go inside the "data" folder and delete the 2 folders (adb, app). Then flash the .zip.
Click to expand...
Click to collapse
Where are people getting TWRP from? I can't see it listed for the J8 on their website: https://twrp.me/Devices/Samsung/
There's an unofficial one here:
[RECOVERY] TWRP 3.6.x.x for Samsung Galaxy J810G/GF/F/M/Y j8y18lte
TWRP 3.6.x.x for Samsung Galaxy J8 Note: I AM NOT RESPONSIBLE OF ANY DAMAGE WILL HAPPEN AFTER YOU FLASH THIS TWRP , ALWAYS DO BACKUP FIRST DOWNLOAD MODE 1. power off your Samsung J8/On8 2. press & hold both vol+ & vol- keys and insert USB driver...
forum.xda-developers.com
Bro i need galaxy theme is there any solution ?
X - root said:
where i can get non root (magisk) boot.img
i want to uninstall magisk from this rom.
thank you so much dev
Click to expand...
Click to collapse
You can uninstall it from Magisk homepage "Uninstall Magisk". The system may not boot without Magisk. Keep this in mind.
Canyoning.cat said:
Where are people getting TWRP from? I can't see it listed for the J8 on their website: https://twrp.me/Devices/Samsung/
There's an unofficial one here:
[RECOVERY] TWRP 3.6.x.x for Samsung Galaxy J810G/GF/F/M/Y j8y18lte
TWRP 3.6.x.x for Samsung Galaxy J8 Note: I AM NOT RESPONSIBLE OF ANY DAMAGE WILL HAPPEN AFTER YOU FLASH THIS TWRP , ALWAYS DO BACKUP FIRST DOWNLOAD MODE 1. power off your Samsung J8/On8 2. press & hold both vol+ & vol- keys and insert USB driver...
forum.xda-developers.com
Click to expand...
Click to collapse
Here: https://forum.xda-developers.com/t/...d-flash-twrp-j810f-g-m-y-gf-j8y18lte.4479201/
Kevin Ackerman said:
Bro i need galaxy theme is there any solution ?
Click to expand...
Click to collapse
Download the necessary apps from "Deleted Apps" folder inside the Google Drive folder and copy them to corresponding folder and reboot.
Hi all,
i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions!
As usual all care no responsibility! Nothing here is without risk.
Android 13
5 March 2023 Security Patch Level
1. Unlock your bootloader. (Very easy to do - https://www.hardreset.info/devices/...-s6/faq/bootloader-unlock/samsung-bootloader/)
2. Download the official vbmeta image provided by TWRP > https://dl.twrp.me/gts4lv/vbmeta.tar.html
3. Download TWRP https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
4. Open Odin
5. Put VBMETA.TAR in the CP Slot & TWRP in AP slot and flash. On reboot hold down the Pwr/Up button so it boots straight into TWRP or sometimes it can be overwritten.
3. Format Data, reboot back into TWRP and Full Factory Reset . (Take a backup if you need one).
4. Transfer the LoS image file to the tablet via TWRP then Flash the LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
(might need to use the adb push command to copy the file across) adb push filename.extension /sdcard
5. Flash magisk if you like.
6. Reboot to system and enjoy!
i used the one above which includes GAPPS though there are ones that don't if you prefer
I only just finished installing though - quick summary:
Working:
Fingerprint!
Hardware Buttons
SDCard
Wifi
Bluetooth
Gapps and Google Setup
Tablet is very fast!
Charging
USB File Transfer
Audio
Video out for USB-C
Auto-rotate
GPS
Official Samsung Keyboard Physically attached working fine too!
Themes
Colours
Mic
SPen
Not Working:
Only bottom speakers work
SafetyNet
Workarounds:
To pass SafetyNet (BASIC):
Flash Magisk in TWRP
Use Magiskhide
Turn on Zygist
Install Displax modified SafetyNet-Fix from link below;
hxxps://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.2
Configure your Denylist in Magisk for Google Play Store and Services apps. (And anything else you need to not detect root).
To Fix Brightness:
Go to Settings - Phh - Misc Features - Tick the box for "Use Linear Brightness Slider"
To Help with Fingerprint:
Turn off taskbar in Settings to help alignment with Fingerprint scanner
Hope we can get some community effort behind this so we can bring this tablet back into support since Samsung gave up on it..
Credit to @AndyYan for the builds!
[GSI][13] LineageOS 20 TrebleDroid-based
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
RESERVED
In my case only bottom speakers work!
Sage said:
Hi all,
i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions!
5.Install LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
Click to expand...
Click to collapse
Thanks so much for this!
I have built LOS for a couple unsupported devices in the past and would love to dedicate as much time and resources as needed to this project.
Could you share which build trees were used from Github and the extracted blobs?
I would like to replicate this build and put in a request with LOS developer stinX for an official one.
tablet_seeker said:
Thanks so much for this!
I have built LOS for a couple unsupported devices in the past and would love to dedicate as much time and resources as needed to this project.
Could you share which build trees were used from Github and the extracted blobs?
I would like to replicate this build and put in a request with LOS developer stinX for an official one.
Click to expand...
Click to collapse
I am not sure mate about the GIT and Blobs. These are GSI so "generic" so they may not have them. From my understanding they work with the existing Vendor image and take advantage of Treble to ensure everything works.
The source of the files is here:
[GSI][13] LineageOS 20 TrebleDroid-based
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
m0byn said:
In my case only bottom speakers work!
Click to expand...
Click to collapse
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Sage said:
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Click to expand...
Click to collapse
I should add i think this is MUCH faster than stock and battery life is looking great too!
I am happy there are some other people who are using this GSI on a Tab S6. I installed it some time ago and am very satisfied!
Some things I found:
Fingerprint XY coordinates are somehow off. Specifically, the symbol showing on screen and the actual reader are not on the same place. I think it is related to the app bar somehow, since it seems to be off by that. I think this could be fixed by an overlay.
Auto-brightntess is not available as well. Either use an app for that, or don´t use it. This can also be fixed by an overlay as far as I know.
Maybe it is also possible to get the top speakers working by making an overlay? I am not sure regarding this, however.
Obviously, DolbyAtmos is not included. However, I think there exists a Magisk Module. Maybe it would also be possible to integrate this into an overlay? This would be amazing
I am very new to the custom ROM/GSI scene. So, my experience with overlays and so on is basically none. However, I would try to contribute as good as I can if someone feels ready to create an overlay and then getting it implemented into the GSI.
Anyone interested in cooperating?
Sage said:
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Click to expand...
Click to collapse
I will try to do that as well...lets see.
I would explicitly add to the working section that the spen works and also pressure sensitivity of the spen works! At least in the Saber Handwritten Notes app which I use. This is amazing.
Sage said:
1. Unlock your bootloader. (Very easy to do - https://www.hardreset.info/devices/...-s6/faq/bootloader-unlock/samsung-bootloader/)
2. Install TWRP via Odin https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
3. Full wipe thru TWRP. Including format data. (Take a backup if you need one).
4. Reboot back to TWRP.
5.Install LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
6. Boot and enjoy!
Click to expand...
Click to collapse
Didn`t you patch the vbmeta.img, or did you flash the multidisabler zip?
Somehow, one has to disable verified boot such that you can even boot LineageOS...as far as I know!
m0byn said:
Didn`t you patch the vbmeta.img, or did you flash the multidisabler zip?
Somehow, one has to disable verified boot such that you can even boot LineageOS...as far as I know!
Click to expand...
Click to collapse
All I did was what I posted above! I'm surprised how easy it was tbh!
Sage said:
All I did was what I posted above! I'm surprised how easy it was tbh!
Click to expand...
Click to collapse
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
m0byn said:
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
Click to expand...
Click to collapse
Nope. Started from stock. Literally unlocked bootloader right before moving to GSI. Just like the steps above.
I did install Magisk which may help disable verified boot though
Sage said:
Nope. Started from stock. Literally unlocked bootloader right before moving to GSI. Just like the steps above.
I did install Magisk which may help disable verified boot though
Click to expand...
Click to collapse
Ah, that might make the difference! So I think it is worth to mention to either install Magisk, or to patch the vbmeta.img in order to boot. If coming from stock with the stock vbmeta.img, then Android Verified Boot will not allow booting into a different ROM.
m0byn said:
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
Click to expand...
Click to collapse
OP is wrong.
Be careful flashing the latest TWRP for SMT-860 Wifi with Odin.
This happened to me today after doing it. "Error verifying vmbeta image: Invalid vmbeta header"
{
"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"
}
The device gets stuck like this and won't boot anymore, but you can get it back to normal by flashing the recovery.img from your firmware files (It's in AP)
You cannot install TWRP on the Galaxy Tab S6 without fixing the vmbeta.img issue.
I tried with the latest Samsung firmware downloaded via SamFirm and an older one.
@m0byn: Do you know what needs to be done with the vmbeta.img on this device, to allow for TWRP to be flashed?
I have found many different prescribed solutions such as patching boot.img with Magisk or just the vmbeta.img , but nothing seems to work.
Tablet, search my post here https://forum.xda-developers.com/t/t865-rooting-with-android-12-bootloop-and-error.4452641/ and try
Hey man, thank you for the suggestion. That post seems to be about Magisk and rooting.
The problem here is the vmbeta.img.
According to older posts from 2021 this can be resolved by flashing vbmeta_disabled.tar , but the latest 2022 version of TWRP should no longer require this. It's weird.
I am sorry. I thought something went wrong when you patched the firmware with Magisk
Probably flashing Magisk automatically patches the vbmeta.img. Not sure though.
Follow the steps below. This is how I did it. It worked.
I am assuming a stock recovery in this process. If you already installed TWRP just try if it works as well. not sure if this is impacting the process.
Unpack firmware using 7Zip tool
Unpack AP.tar.md5 using 7Zip tool
Unpack vbmeta.img.lz4 using 7Zip-ZS tool
Open file in FrhedPortable (HEX editor) to patch it
Go to offset (block) 123 and write 03 and save
Compress vbmeta.img to vbmeta.img.tar using 7Zip tool
Connect device via USB to computer
Hold volume up & volume down buttons
Press volume up button to proceed to download mode
Open Odin -> verify whether device number is added
Untoggle "auto-reboot" in options
Select AP section
Choose patched vbmeta.img.tar file
Click start to flash
When flashing process is done: hold power & volume down button to exit and power off device
IMPORTANT: as soon as device shuts off immediately release volume down button and press volume up button to enter recovery mode
Click factory reset
Click reboot to bootloader
Thanks @m0byn I managed to figure it out with your help.
For anyone else facing the same problem, here is what you need to do:
Download the official vbmeta image provided by TWRP > https://dl.twrp.me/gts4lv/vbmeta.tar.html
Proceed to flash with Odin.
Put the TWRP recovery image in AP and vbmeta.tar in the CP slot.
After this you can boot into the TWRP recovery normally, but for some reason any changed settings in TWRP are not saved. So everytime I reboot into TWRP recovery all previously selected TWRP settings are lost. I wonder if that's normal, but everything else seems to work.
Next step will be flashing the Lineage GSI, i'll keep you guys posted.