Related
[TIPS] ROOTING and FLASHING anything on P8000 WITHOUT PC
Hi guys, I found a method to root and flash anything on my P8000 without unlock the bootloader, use SP Flash Tool and even use PC. I tried to go this way because I was not able to get my P8000 recognized by Flash Tool nor as a MTP (mass storage) device in any Windows 7 laptop. I decided to write this post because no-one over the net talks about alternative method of rooting Elephone P8000.
Disclaimer: I'm not responsible for ANY damage (software or hardware of any type) caused to your device, remember that I'm not a developer, and I'm only reporting my personal experience. DON'T try to flash rom linked below on other devices or flash roms which are not compatible with P8000.
Rooting and flashing process may VOID YOUR WARRANTY.
LET'S START.
1) DOWNLOAD THE STUFF: download everything directly through the browser of your P8000.
-TWRP recovery: http://www.mediafire.com/download/8g....7.0_v.4_1.zip
-Custom Rom: choose the rom you prefer from the link below and download it directly in your smartphone, my favorite one is Nexus rom:
-Eragon rom:http://www.needrom.com/download/eragon-3-for-p8000/
-CyanogenMod 12.1: http://www.needrom.com/download/stab...nogenmod-12-1/
-Mokee OS: http://www.needrom.com/download/mokeeos-2/
-EMUI V3.1 : http://www.needrom.com/download/emui...lite-stable-2/
-NEXUS rom v2.4: http://www.needrom.com/download/nexus-10/
-Flyme rom: http://www.needrom.com/download/p800...5-3-15082-5-1/
-Gapps: if you choose to install Nexus rom. or Mokee OS or CyanogenMod 12.1, you may need to install google apps also if you want google services and play store to run on your device. Click on the link from the browser of your device. Select ARM_64, then 5.1, and than "pico" and click on the button to download: http://opengapps.org/. If you need others apps download them from the play store.
2) ROOT YOUR P8000.
Use an app called Kingroot, but you will not find it on play store. Get it from the link below:
http://kingroot.it.uptodown.com/android
Download the app directly using the browser on your smartphone, then install and open.
Skip the tutorial and click on "Root device". Wait the process to be done (few minutes) and don't be scared if the device reboots. This app is able to root the most of android devices, but not the 100% is compatible.
3)UNZIP THE RECOVERY:
Install an app knows as RAR from play store, than open it and navigate to the directory where the twrp recovery zip is contained (usually "download" folder). Open the zip and extract the IMG file contained in it into the same folder.
4)INSTALL FLASHIFY.
You can find this app on the play store, or you may download it from the link below:
http://www8.zippyshare.com/v/pqLDpS5F/file.html. Open the app and grant superuser permissions, than accept the agreement.
Click on "Recovery image", than "choose a file" and than "downloads", select the IMG file of the recovery you extracted before and wait for the process to finish, a message will appear. This app can be used on any android device that is compatible, but flash only IMG and zip files specific for your model. Now we can install the Rom or any zip file you want through the twrp recovery.
5) NANDROID BACKUP:
Power off your P8000 and than boot into recovery mode. To do this press and hold power button and volume up at the same time, release them when white writings appear. Press volume app button to select "recovery mode" and than volume down to enter recovery mode.
Swipe the bar to allow system modifications, click on " backup" and select every partition displayed, then choose where the backup file will be stored and write the name you want to give to the backup file.
Swipe the bar to start and wait untill the process finishes ( few minutes). Press the back button to return to the main menu.
6) INSTALL ROMS OR OTHER ZIPS:
Before Installing a new rom you need to wipe many partitions of the device, from the main menu select "wipe" and "Advanced wipe", then select the partitions that you may wipe: system, data, cache.
Swipe to wipe and wait the process to finish (few minutes) an then press back button to return to main menu.
Now click on "install" and select "internal sorage" among the options, navigate and select the "download" folder where your downloaded zip files are(rom and gapps in this case). Select the zip that you want to install ( the rom in our case), swipe to confirm and wait few minutes, than press back and install the gapps zip as well.
At the end of the process click on "reboot system" and wait for the smartphone to reboot.
The first time it will take more time than a usual reboot (from 5 minutes to 10 minutes).
I hope this article will help you out!
Please forgive me for my bad english.
It's wrong that nobody over the internet talked about the method. I talked about this method in the last command at this page http://forum.xda-developers.com/elephone-p8000/general/tutorial-flash-root-update-elephone-t3248742.
ElephoneP8000_0wner said:
It's wrong that nobody over the internet talked about the method. I talked about this method in the last command at this page http://forum.xda-developers.com/elephone-p8000/general/tutorial-flash-root-update-elephone-t3248742.
Click to expand...
Click to collapse
Yeah but nobody explained how to do it completely without using PC.
I thought this method of flashing ROMs with recoveries (philz, cm, twrp etc...) was common knowledge? I've been flashing ROMs like this since my HTC evo days. Isn't that the whole point to having a third party recovery?
Sent from my p8000 using Tapatalk
kgoerbig said:
I thought this method of flashing ROMs with recoveries (philz, cm, twrp etc...) was common knowledge? I've been flashing ROMs like this since my HTC evo days. Isn't that the whole point to having a third party recovery?
Click to expand...
Click to collapse
Hi do you speak italian?
Can you learning Moore?
Jacopo123
Hello here I bring you like having a beta of the rom oreo 8.1 with gapps.
Download links
Rom 4.16 stock:
Mega:https://mega.nz/#!Eo5CwYYY!ZS7vhVbXWRsLtSbyRKPMhwMYea-aB4ws39y3CFHuLFQ
(link donated by nikos of xda)
zip to update to oreo:
Mega:https://mega.nz/#!iQJQBTxC!iS65Wt4DnnSVnwk8NQDVUrxN8UOMcOjTm7rZoW90sKw
(link donated by alextork)
Opengapps pico: http://opengapps.org/
recoverys:
Mega:https://mega.nz/#!jExHGDBa!CJLUqQ37Vtkg_smwz_bAxd1X-Re05LyWWid6LFtD4kc
I upload the folder where the two recoverys are stored and where to open the commands window
necessary application:
Mega:https://mega.nz/#!XQ4SQQ7C!TWnOq5Qyv_izVL1rE2cAosTYRJzGMeVH66ANB8nlVSs
instructions for installation and putting gapps:
This was possible thanks to the android thread information 8.1. Thank you
First of all we must make a modification in opengapps with winrar.
in the computer we open with winrar, we go to the core folder and we eliminate these two files:
setupwizarddefault-all.tar.lz
setupwizardtablet-all.tar.lz
1.
Install a rom different from the rom oreo or if you have installed a rom other than the rom oreo
example:https://forum.xda-developers.com/nubia-z17/how-to/rom-miui-9-9-2-bugs-t3775694
2
we installed the mobile drivers in addition to the fastboot drivers.
unzip the packnubiaz17 folder
inside we click right button + shift and open powershell or command window.
we put the phone in fastboot mode. volume button down and power.
we connect the mobile.
we wrote cmd
we wrote fastboot oem nubia_unlock NUBIA_NX563J
we write fastboot flash recovery recovery.img
reboot recovery
we flashed the previously modified pic.o opengapps.
we restart
we install the necessary application.
let's go to settings-application information-google play store-force disable.
we need to connect to a wifi or have mobile data.
once this is done. We enter the play store.
We try to download any app. if download pending pending.
We force Google Play to stop and we disable Google Play and re-enable it. So I should go when I enter.
3
we install 4.16 stock rom, start it, unlock development options, unlock oem and activate debug usb, then do a factory reset.
We do not have to start after the factory reset, we must give it a button up and power
this will make us return to the official recovery of nubia, restart in the official recovery of nubia. Inside we make data wipe and then through otg we search in the usb that we have previously entered the update oreo. We select it and let it finish. Once done, we start and configure.
4
we go to fastboot mode. in the folder we start to start the commands window and put the same commands as in step 2. once done this we go to wipe. advanced wipe and there we select data and we give ext2 first and then ext4.
5
we flashed the previously modified pic.o opengapps.
we restart
we install the necessary application.
let's go to settings-application information-google play store-force disable.
we need to connect to a wifi or have mobile data.
once this is done. We enter the play store.
We try to download any app. if download pending pending.
We force Google Play to stop and we disable Google Play and re-enable it. So I should go when I enter.
6
we go again to fastboot mode.
open command window
we wrote cmd
we wrote fastboot oem nubia_unlock NUBIA_NX563J
we wrote fastboot flash recovery recoveryo.img
Any bug report so we can know, the rom is not yet tested. I hope your collaboration
:good::good::good:
I think everything before point 3 is not needed, since 4.16 overwrites everything, and you start clean there. is there any reason why point 1 and 2 are done?
also when using twrp 3.2.1-0 from opening post from 8.1 thread https://forum.xda-developers.com/nubia-z17/development/stock-rom-4-16-update-package-5-t3774018 you don't even need to wipe data anymore since it stays accessible in this twrp version...
the thing I'm interested in... is this 'necessary application'. what does it do? This Google Account Manager?
MrBlubke said:
I think everything before point 3 is not needed, since 4.16 overwrites everything, and you start clean there. is there any reason why point 1 and 2 are done?
also when using twrp 3.2.1-0 from opening post from 8.1 thread https://forum.xda-developers.com/nubia-z17/development/stock-rom-4-16-update-package-5-t3774018 you don't even need to wipe data anymore since it stays accessible in this twrp version...
the thing I'm interested in... is this 'necessary application'. what does it do? This Google Account Manager?
Click to expand...
Click to collapse
Hi MrBlubke,
I believe he is trying to explain how to install Gapps without root on both Oreo and non-Oreo. What I don't understand is it is mentioned in Point 2 that to install Mobile Driver in addition to Fastboot Driver. I have been searching for a while for drivers for Nubia Z17, but have not found any driver working on my Windows 10 Enterprise version. Do you have most updated driver for Nubia Z17? If yes, can you please share it with me.
Thank you.
the steps should be followed as they are explained without skipping any, if you skip any or do it another way it will not work. Regarding the drivers I have 300 downloaded and one worked. I'll link you and tell me if it works for you. 2 links
https://forum.xda-developers.com/showthread.php?t=2588979
Mega: https://mega.nz/#!iAYzzYYC!quiDZfgAKdlQpLfolfbYim1R5HaERwuXAG3lUaaonJg
MrBlubke said:
I think everything before point 3 is not needed, since 4.16 overwrites everything, and you start clean there. is there any reason why point 1 and 2 are done?
also when using twrp 3.2.1-0 from opening post from 8.1 thread https://forum.xda-developers.com/nubia-z17/development/stock-rom-4-16-update-package-5-t3774018 you don't even need to wipe data anymore since it stays accessible in this twrp version...
the thing I'm interested in... is this 'necessary application'. what does it do? This Google Account Manager?
Click to expand...
Click to collapse
@MrBlubke u r right...
but his method really works...
great job n thanks @isaac121212:good::good:
isaac121212 said:
the steps should be followed as they are explained without skipping any, if you skip any or do it another way it will not work. Regarding the drivers I have 300 downloaded and one worked. I'll link you and tell me if it works for you. 2 links
https://forum.xda-developers.com/showthread.php?t=2588979
Mega: https://mega.nz/#!iAYzzYYC!quiDZfgAKdlQpLfolfbYim1R5HaERwuXAG3lUaaonJg
Click to expand...
Click to collapse
hi Isaac, is driving me crazy but no drivers fit for fastboot mode after you updgrade to oreo, Ive actually trying with port 2.0 and nothing. Did you find a suitable driver? BTW greetings from Peru
I've put a link with fastboot mode drivers, some of them work, which no idea
Hello,
I'm trying to install LineageOS with the least amount of Google footprint possible along with Magisk Manager.
However, when booting into LineageOS, it uses Google to setup my device instead of the LineageOS.
My process of installation:
1. Open Recovery and Advance wipe everything (excluding OTG, including Internal Storage) and Format Data after that
2. Reboot into bootloader
3. fastboot flash recovery twrp-3.3.1-1-20190713-codeworkx-dumpling.img
4. fastboot boot twrp-3.3.1-1-20190713-codeworkx-dumpling.img
5. adb sideload lineage-16.0-20190816-nightly-dumpling-signed.zip // I've also tried flashing / installing it like a regular zip
6. adb push open_gapps-arm64-9.0-pico-20190816.zip // I've also tried using aroma sometimes
7. adb push Magisk-v19.3.zip
8. Install / Flash Gapps
9. Install / Flash Magisk
10. Boot into System
Using the above method, Google loads up to setup my device.
I'd like to use LineageOS with its stock apps and ONLY Play Store from Google if possible.
Any help is much appreciated.
JohnnyBoiiJB said:
Hello,
I'm trying to install LineageOS with the least amount of Google footprint possible along with Magisk Manager.
However, when booting into LineageOS, it uses Google to setup my device instead of the LineageOS.
My process of installation:
1. Open Recovery and Advance wipe everything (excluding OTG, including Internal Storage) and Format Data after that
2. Reboot into bootloader
3. fastboot flash recovery twrp-3.3.1-1-20190713-codeworkx-dumpling.img
4. fastboot boot twrp-3.3.1-1-20190713-codeworkx-dumpling.img
5. adb sideload lineage-16.0-20190816-nightly-dumpling-signed.zip // I've also tried flashing / installing it like a regular zip
6. adb push open_gapps-arm64-9.0-pico-20190816.zip // I've also tried using aroma sometimes
7. adb push Magisk-v19.3.zip
8. Install / Flash Gapps
9. Install / Flash Magisk
10. Boot into System
Using the above method, Google loads up to setup my device.
I'd like to use LineageOS with its stock apps and ONLY Play Store from Google if possible.
Any help is much appreciated.
Click to expand...
Click to collapse
you can't
for play store you need google core apps and google play services
if you don't want google at setup remove
setupwizard folder from system/priv-app
after flashing gapps
AlMaghraby said:
you can't
for play store you need google core apps and google play services
if you don't want google at setup remove
setupwizard folder from system/priv-app
after flashing gapps
Click to expand...
Click to collapse
Does that make LineageOS do the setup instead of Google? Sorry new to this whole thing..
AlMaghraby said:
you can't
for play store you need google core apps and google play services
if you don't want google at setup remove
setupwizard folder from system/priv-app
after flashing gapps
Click to expand...
Click to collapse
Also, in this youtube video here: v=3wI2ht0kbeU , you can see the person sideloading lineage and setup the phone and then load gapps. However, in the LineageOS Installation guide, it is highly recommended to flash the gapps immediately after flashing LOS.
JohnnyBoiiJB said:
Does that make LineageOS do the setup instead of Google? Sorry new to this whole thing..
Click to expand...
Click to collapse
yes
---------- Post added at 11:46 PM ---------- Previous post was at 11:44 PM ----------
JohnnyBoiiJB said:
Also, in this youtube video here: v=3wI2ht0kbeU , you can see the person sideloading lineage and setup the phone and then load gapps. However, in the LineageOS Installation guide, it is highly recommended to flash the gapps immediately after flashing LOS.
Click to expand...
Click to collapse
most of the apps you use require google play services to work
that's why
If you want the smallest Google footprint possible then you can use MicroG instead of Gapps. There is even a LineageOS weekly build that comes with it preinstalled https://download.lineage.microg.org/dumpling/
Hi everyone, I tried to get LineageOS 18.1/Android 11 again onto my A8 and this time it worked. I have written down all the steps I followed.
You can take these steps and do whatever you want but don't blame me if it breaks anything. You are responsible for what you do to your phone. You will loose your warranty. You will loose all data on your phone including internal storage. I don't think you will pass Safetynet afterwards so say bye to banking apps.
Some steps are copied out of other posts so big thank you to them. I always linked them. Actually this is more or less a summary of different guides I read put together in one.
I don't use Google Services so I don't know if they'll work.
CHAPTER 0 - Prerequisites
- Make a backup of all your important data
- Make a backup of data in your internal storage
- Have the bootloader unlocked (Go to settings/Developer options and enable OEM unlock)
- Be RMM unlocked (no RMM State prenormal). You can check this in download mode (Power + Vol. Up + Vol. Down) by reading the small text
- Read everything before you start
- You can also download all the things before starting
CHAPTER 1 - Reset
I don't think that this is necessary but things like calls were broke for me before so I decided to reset everything by flashing stock firmware. Please decide for yourself if you need this.
- Download Odin
- Download official firmware (e.g. from here: https://galaxyfirmware.com/model/SM-A530F)
- Extract zip file
- Enter download mode (turn off, then Power + Vol. Up + Vol. Down)
- Connect phone to computer
- Open Odin
- Select all the files you extraced from the firmware zip in Odin (BL/AP/CP...)
- Untick Autoreboot under options
- Hit start
- When finished, disconnect phone
- Press "Power" and "Vol. Down" until screen goes black
- In this moment, press all buttons (Power + Vol. Up + Vol. Down) again to reenter download mode!
CHAPTER 2 - Install custom recovery
see https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3760975/
- Download TWRP tar file from here: https://twrp.me/samsung/samsunggalaxya82018.html
- After chapter 1, your phone is in download mode. If you skipped it, turn off and press Power + Vol. Up + Vol. Down to enter download mode
- Connect phone to computer
- Open Odin, go into options and untick Auto-reboot and put the TWRP tar file in AP tab of odin, hit Start and wait
- When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Power" + "Vol. Down" + "Vol. Up" buttons until the downoad mode disappears
- At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
- ***Don't boot into rom because it will lock your device again!!!!
CHAPTER 3 - Wipe
- Swipe "Allow modifications"
- Go into Wipe menu and select "Format data" - note that this will erase all your data including internal storage
CHAPTER 4 - Trebelize
see https://forum.xda-developers.com/t/...-guide-for-galaxy-a8-2018-18-04-2019.3894881/
- Download Treble creator and treble TWRP
- Wipe system/cache/data
- Copy the TrebleCreator.zip(of your variant) and TWRP-jackpotlte-Treble.img to your Internal/SDcard
- Flash the TrebleCreator.zip through TWRP recovery
- After completing your device will reboot to RECOVERY
- Now touch INSTALL > Select Image > Locate TWRP-jackpotlte-Treble.img
- Flash TWRP-jackpotlte-Treble.img to recovery
- Reboot your device to recovery
- Wipe system, cache, vendor, dalvik cache and data.
CHAPTER 5 - Android 11
- Download Vendor, GSI (if you used the linked vendor, you'll need: arm64, A/B, vndklite)
- Vendor download: https://forum.xda-developers.com/t/...dor-quack-v2-5-for-galaxy-a8-a8-2018.4157533/
- GSI download (recommendation): https://forum.xda-developers.com/t/gsi-11-lineageos-18-x-gsi-all-archs.4205461/
- Extract the system image .xz file
- Reboot to recovery
- Copy files onto the phone
- Install vendor zip
- Flash gsi image as system image
- Reboot to system
CHAPTER 6 - Enjoy
Don't turn on "Workaround for broken fingerprint".
WHAT WORKS
The system seems to be pretty stable for a GSI. I haven't experienced any random freezes yet.
- Phone, Mobile data
- Wifi
- Bluetooth
- NFC
- Hotspot (I opened one but didn't try to connect to it)
- Camera (also 3rd party apps, YES!)
- Fingerprint
If you downloaded the LineageOS version I linked above, you will automatically have root because it's based on the phh treble GSI. You can install the Superuser app from F-Droid: https://f-droid.org/de/packages/me.phh.superuser/ just as a normal APK file.
NOT WORKING
- probably everything that doesn't work in any GSI like voLTE and Bluetooth calls but havent tested any of them
- of course the second front cam
- USB accessories? (they are broke with this vendor)
What is your experience with this gsi so far?
JohnnyxS said:
What is your experience with this gsi so far?
Click to expand...
Click to collapse
It's about as good as the Android 10 gsi I used earlier. The camera app takes some seconds to start but I had no other problems with it (except for the things mentioned in the post under "not working")
Have you used other GSIs before?
jannis3 said:
It's about as good as the Android 10 gsi I used earlier. The camera app takes some seconds to start but I had no other problems with it (except for the things mentioned in the post under "not working")
Have you used other GSIs before?
Click to expand...
Click to collapse
I haven't, i managed to install it but not with google services, lost an entire day trying: (
I am a complete n00b, I'm going trough this.
Thanks a lot @jannis3 for these clear instructions!
Here are my observations, in case someone needs them:
Chapter 0:
- Have the bootloader unlocked (Go to settings/Developer options and enable OEM unlock)
To access the Develloper Menu, you need to tap 7 time the Build number in about page:
How do I turn on the Developer Options menu on my Samsung Galaxy device?
Find out how to turn on the Developer options menu on your Samsung Galaxy device.
www.samsung.com
- Be RMM unlocked (no RMM State prenormal). You can check this in download mode (Power + Vol. Up + Vol. Down) by reading the small text
This did not show on my device (no mentions of RMM).
However, there was:
FRP LOCK: ON
OEM LOCK: ON
First one needs to be disabled by remove ALL accounts before starting to flash
Second one is removed trough the Bootloader option in the developer menu.
Chapter 5:
Choose the "treble_arm64_avS.img" version
JohnnyxS said:
I haven't, i managed to install it but not with google services, lost an entire day trying: (
Click to expand...
Click to collapse
Hello Johny,
I just lost my day trying too.
No GApps with this GSI, because it keeps shrinking the system partition to 1MB Left.
Do you have a suggestion of another GSI that works nice on our A8?
I'm on it again!
I just found out about Phhusson and its incredible work.
Since LineageOS clearly does not work if you want GApps, here are the releases for Phh-Treble:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Specific page for A8 (2018):
Samsung Galaxy A8 (Exynos)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Make sure you use: system-roar-arm64-ab-vndklite-gapps.img.xz for the A8.
Upon bootup, Google framework goes bezerk about not being Play Protect Certified.
Follow the instructions to register your device to google here:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
After a reboot, I then had everything working but the Play Store would still throw me a Google Play Protect error.
Clearing data and cache on Google Play Services worked for me.
Google Play Store Not Working? Fixes and Solutions | nextpit
Google Play Store problems can usually be fixed simply by clearing the cache, but if not, we have even more solutions in this article!
www.nextpit.com
jaylimo84 said:
I'm on it again!
I just found out about Phhusson and its incredible work.
Since LineageOS clearly does not work if you want GApps, here are the releases for Phh-Treble:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Specific page for A8 (2018):
Samsung Galaxy A8 (Exynos)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Make sure you use: system-roar-arm64-ab-vndklite-gapps.img.xz for the A8.
Upon bootup, Google framework goes bezerk about not being Play Protect Certified.
Follow the instructions to register your device to google here:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
After a reboot, I then had everything working but the Play Store would still throw me a Google Play Protect error.
Clearing data and cache on Google Play Services worked for me.
Google Play Store Not Working? Fixes and Solutions | nextpit
Google Play Store problems can usually be fixed simply by clearing the cache, but if not, we have even more solutions in this article!
www.nextpit.com
Click to expand...
Click to collapse
Meh i gave up for now, i might return at some point to trying it again.
jaylimo84 said:
I'm on it again!
I just found out about Phhusson and its incredible work.
Since LineageOS clearly does not work if you want GApps, here are the releases for Phh-Treble:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Specific page for A8 (2018):
Samsung Galaxy A8 (Exynos)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Make sure you use: system-roar-arm64-ab-vndklite-gapps.img.xz for the A8.
Upon bootup, Google framework goes bezerk about not being Play Protect Certified.
Follow the instructions to register your device to google here:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
After a reboot, I then had everything working but the Play Store would still throw me a Google Play Protect error.
Clearing data and cache on Google Play Services worked for me.
Google Play Store Not Working? Fixes and Solutions | nextpit
Google Play Store problems can usually be fixed simply by clearing the cache, but if not, we have even more solutions in this article!
www.nextpit.com
Click to expand...
Click to collapse
Have you tried Android 12L?
g000n said:
Have you tried Android 12L?
Click to expand...
Click to collapse
Nope... 12L did not exist at the time.
Also, I gave up.
Phh-Treble was less stable than my mother in law.
My first goal was to "save" the A8 to use it for one or two year more, but the difficulty to get something simple and stable was getting harder by the minute.
I got a pretty good deal on a S20 FE 5G, so I moved on.
Great work !
Hi, I followed the guide, I don't flashed the stock ROM because I'm doing with heimdall (linux odin) and it can boot after flash. But I follow the other chapter and steps and works. The only issue I have is that after the LineageOS without GApps is installed and I reboot the phone enters in a boot loop and it can't boot. If I try to enter in the recovery boot freezes at TWRP logo splash screen.
The question is: Why enters in the boot loop ? What can I do ?
Hi, today I tried flashing the phh Android 12 GSI and it actually booted. It's a bit laggy and apparently you cannot set a screen lock for whatever reason (I read something about too old keys?). Also some random things did not work so I wanted to get back to the Android 11 LineageOS GSI. I restarted into the recovery mode but only the TWRP splash screen showed up, just as @ferriol mentioned earlier. What I did to recover my phone was:
Go to download mode
Flash original OS
It then automatically rebooted to the original recovery
I selected something like "wipe data" or "reset phone"
rebooted to original OS (It wouldn't start for me, idk why)
force reboot (power + vol. down) into download mode (power + vol. down + vol. up)
Follow my own instructions from Chapter 2 on and flashed Android 11 again
I did this three times. I don't know what actually did the job in the end but I think it was wiping the system using the original recovery and rebooting (or trying at least) into the original OS
Sooo weird... My next phone is probably not a samsung one xD
ferriol said:
Hi, I followed the guide, I don't flashed the stock ROM because I'm doing with heimdall (linux odin) and it can boot after flash. But I follow the other chapter and steps and works. The only issue I have is that after the LineageOS without GApps is installed and I reboot the phone enters in a boot loop and it can't boot. If I try to enter in the recovery boot freezes at TWRP logo splash screen.
The question is: Why enters in the boot loop ? What can I do ?
Click to expand...
Click to collapse
I resolved flashing the RMM_Bypass_v3_corsicanu.zip and no-verity-opt-encrypt-6.1.zip after flashed lineage-19.1-20220510-UNOFFICIAL-arm64_bvS-vndklite.img
Thanks for your work !
Hi!
Thanks for your tutorial. It is of great help!
I can install the os find on my A8 and run it but i noticed a few issues:
- camera app is missing
- updater app is misssing
- I cannot install GAPPS (opengaps nano or pico) because of missing space (32mb left on system) and I tried to resize system but TWRP gives an error: /sbin/e2fsck -fp /dev/plock/platform/13500000.dwmmc0/by-name/SYSTEM process ended with ERROR: 8
Unable to repair System.
I tried upgrading TWRP to 3.9.2_9-0 but still have the same issue.
Do you have any idea on how to fix the resize error?
For those looking to make lineageos work on galaxy A8 SM-A530W here is what I did:
follow the guide and then:
instead of LOS 18.1 install lineage-17.1-20210808-UNOFFICIAL-treble_arm64_bvS.img.xz
install opengapps 10 nano
If stuck on loading screen, reinstall os and opengapps without wiping the disk
I still have the camera not working though. Everything else seems fine.
lejeanf said:
For those looking to make lineageos work on galaxy A8 SM-A530W here is what I did:
follow the guide and then:
instead of LOS 18.1 install lineage-17.1-20210808-UNOFFICIAL-treble_arm64_bvS.img.xz
install opengapps 10 nano
If stuck on loading screen, reinstall os and opengapps without wiping the disk
I still have the camera not working though. Everything else seems fine.
Click to expand...
Click to collapse
Here is a lead: https://forum.xda-developers.com/t/everything-you-need-to-know-to-fix-camera-on-custom-rom.4218165/ " No easy route it seems.
Hi man, thanks for the ROM. However, a couple of hours ago, I tried to install it, and I'm not sure if it's because the project has been discontinued or because I didn't fully understand the instructions in English, but I couldn't install the ROM. Is it still functional, or should I look for other alternatives?
Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
leathan said:
Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Click to expand...
Click to collapse
Sorry, I messed with the reply: it's my previous post.
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course)
leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
leathan said:
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
Click to expand...
Click to collapse
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
fux1976 said:
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
Click to expand...
Click to collapse
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
leathan said:
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
Click to expand...
Click to collapse
Phone looks certified, country WW, safetynet passed and upgraded to .160. Only 2 problema left: voice dictation of GBoaed and Android auto not working.
I tried several ways but they didn't solve. Voice dictation worked and then stopped: I guess something interferes... Android Auto app crashes although phone connects to car and is recognised.
Very strange behaviour...
Do you have any idea on how to reflash last .160 zip without twrp? Once installed it gets ignored by system when saved in home directory...
Everything else is working properly.
Isn't Android Auto no more (i.e discontinued).....?
elmor0 said:
Isn't Android Auto no more (i.e discontinued).....?
Click to expand...
Click to collapse
what?!? where did you hear that? It'just something causing problems (compatibility issues with app or setting: magisk, modules, adaway, skipad, disabled system apps and so on). If I could manage to reflash the stock rom it'll work again (I hope)
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
finallau said:
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
Click to expand...
Click to collapse
I only have raw for .143 but I updated to .160*...can I use the previous version or do I get bricked? I don't trust anti roll back mechanism. I can live with this 2 "limitations" waiting for twrp and then be able to flash zip with no hassle.
*I downloaded source code from the Asus site but not sure how to use it (and unzipped is around 10 gb )
Thank you for this! I've been out of the root game for years but noticed with your post that I can hide root from Google Pay and my banking apps, so thinking of trying this. One question though - you mentioned that official updates need to be manually downloaded and the phone re-rooted. Would this wipe the phone each time?
fastboot driver doesnt support win64
Will the phone do a factory reset after unlocking the bootloader?
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
MrKioFLow said:
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
Click to expand...
Click to collapse
Yes, if you unlock the bootloader using the bootloader unlock app (which is a step that is missing in the original post), your phone will perform factory reset.
Troubleshooting
Once you boot into the bootloader with the adb reboot bootloader command, stay on the screen with the green START. Do not navigate to the fastbootd.
Use the side USB port to connect to your computer - not the bottom one.
Run the adb and fastboot commands in Command Prompt as Administrator.
Before you reboot into bootloader, remove Lock screen in Settings.
If you execute fastboot flashing unlock and you got FAILED (remote: 'permission denied'), just ignore it.
It's always better to install the latest updates, then download the firmware to your PC from ASUS Webpage and extract the boot.img and patch it in Magisk in the phone using this tutorial.
Thanks for the guide! Should add that you have to use the side port for fastboot to see the device. Was stuck for a while trying to figure out why neither mac nor pc couldn't find it when it was in bootloader mode - it was because I was using the bottom port lol!
Also if you want to disable verity and verification for the verified boot images, you have to do for both vbmeta.img and vbmeta_system.img. Didn't boot for me until I did that, and had to do an additional factory reset from recovery because of this.