Related
Facing error"error executing updater binary in zip" ( 12.1.1 YOG7DAS2K1) Oneplus one
I tried wiping Data, Cache, System and then after flashing above update it says flashing failed.
Following are the details of my Oneplus one
TWRP : 2.8.7.0
CyanogenMod Version: 12.1-YOG4PAS3JL
Build Number: LMY48B
Device model- A0001
need a solution.
yeah same with me. Weird thing is it just says Error! nothing else is printed on the screen
I have found a solution for this problem.
You can follow this step:
1) Instead of downloading 65.8 MB incremental file go to cyanogen -support website( Sorry couldn't paste the link as i am new user) search for your device and you will find a link which will download the latest complete rom. This rom is of around 700mb.
2) Copy this downloaded rom mentioned above to ur device.
3) Take a Backup
4) Wipe Data, Cache,System or Simply just do factory reset with the help of TWRP
5) Install the Rom using TWRP
6) Reboot and finally your device will be updated and there will be no error.
it worked for me.
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.
TWRP and Rooting a Cubot Cheetah 2 (Nougat)
Android_Dog_Walker said:
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.
Click to expand...
Click to collapse
I have done a lot of searching and found the following;
a) Fastboot boot recovery.img does not work on this phone, There may be some Kernel options required to be passed but I cannot find them,
b) Flashing MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 from Needrom, flashes ok by either using "SP Flash tool" or "Fastboot flash recovery recovery image", but when you start the phone or reboot using "Fastboot reboot" and enter recovery, the stock rom has overwritten it. I have tried multiple flashes and erasing the partition first with no success.
The above appear to mean that I cannot use TWRP (or other Custom recovery) and so cannot install the SuperSu.zip. I have raised this on Needrom with TWRP creator who cannot offer a solution.
Before I try using an app, I'd like to ask if anyone has a solution to stop recovery being overwritten. (I have been unable to find a pre rooted image or an image containing TWRP).
Thanks
Solution Found.....The file available from NeedROM will not work with Nougat on a Cheetah 2.
rebuilt MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 using Carliv Image Kitchen and the Nougat stock rom Recovery and.... the Fastboot boot recovery.img works. I will confirm if the flashing option works during the next couple of days, but this helps understanding of why earlier attempts failed.
The Cubot Cheetah 2 gives no error messages if you are trying to start an incompatible recovery file, it just overwrites recovery with stock recovery and opens that.
This thread can now be closed
I confirm that my modified version works (flash or boot). I do not know how to modify the version info yet, so I cannot publish it.
Any idea on when you might be able to post some info on the modified build? Or even some instructions for us to try and follow your lead?
I would be happy to share my version but I am concerned that it is a ported version based on the current version in Needrom created by MDSdev and the opening screens reflect that ROM build info. If someone would advise me what the rules are regarding this I am happy to change it and then publish.
Alternatively I could finish writing out the process (already started) I went through so that I have a record and others can use it to port their own version, but each version created will also reflect MDSdev's original configuration information and this does not sit well as they did the hard bit of configuring TWRP to work with Cubot Cheetah 2 hardware and earlier Android (6.0/6.1). All I have done is get it working on a Nougat(7.0) version of the Cheetah 2. Advice from an expert in these matters would be helpful.
Gotcha, hopefully someone will
chime in, I would hope given the nature of xda, as long as those who input are acknowledged and recognised all should be well....
Cubot Cheetah 2 Android 7 Root by EpicFail2017
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017
Any idea why the IMEI might get lost? I'm aware that that can happen in mediatek stuff with custom, but is this due to a binary check of boot.img or one of the other ROMS? Or is it the spflash util acting up because of boot.img?
I've two of these phones at the min, one of them already has some issues so don't want to play with that one as of yet - power on issues and fingerprint sensor seems to act up - anyone else?
I'm already on nougat, and your procedure is exactly the same as I was thinking (already patched boot.img using magisk 14.0 but maybe I need use the beta as you did). I didn't get to the flashing of boot.img as I'm more comfortable doing flashing the partition straight from PC (adb/fastboot etc). I'm guessing mediatek can only be flashed safely with sptool? Do we need to reflash ALL partitions as IF we can, flashing boot.img to an upgraded phone should work without loss of data/imei? maybe?
What is the 'R' near the signal in your screenshots?
I'll answer my own questions with a way to root The Cubot Cheetah 2 (Nougat) in just a few minutes ..
I was already on the same version of nougat as the download before I started.
1. Download the ROM shown above and extract, grab the SPFlash too and the drivers. Ensure unknown sources is ticked, unlock bootloader - I also disabled pin security etc (dunno if this was needed).
* Note, install the drivers with the phone NOT connected via USB.
2. Transfer the boot.img to your phone and run it through Magisk (I used the beta 14.2 as documented above and manager 5.35), patch the image file (boot.img)
3. Move the patched boot.img from the magisk folder back to the computer.
4. Run the SPFlash tool load the scatter file, select DOWNLOAD and untick everything asides from boot.img
5. With phone switched off, connect it via USB
Flash
Wait until complete
Reboot
Rooted
No loss of IMEI or data.
It's good to see some responses. I seemed to struggle with TWRP and rooting for a while and now several options are apparently available. My personal opinion (I would say this wouldn't I!) is that if I can get advice on publishing/sharing the working version of TWRP on Cubot Cheetah 2, it is really simple to root the device by flashing TWRP, copy latest version of Supers.zip onto to SD card, open phone in recovery (Which is now TWRP), set English as default language (a one time action), install the Supers.zip. Job done, rooted with the best SuperSu facilities and an industry recognised backup facilities.
Unfortunately I have not yet had any advice on how to version the Nougat version from anyone on XDA yet and I am looking at trying to get MDSdev (the Cheetah 2 Marshmallow TWRP developer) to adopt the Nougat version.
That was my worry, not sure of compatibility of TWRP or boot time stuff on the mediatek devices. Rooting is now very very simple with the previous instructions, I was thinking flashfire or flashify or similar to push recovery onto the recovery partition but it's making sure TWRP is aware of the partitions. 10 years ago I'd have had a good look through the sourcecode for any possible problems but simply don't have the time these days :/
Love the phone but was put off using it as my primary phone due to lack of root. Okay I had to install stuff on the computer to flash this, but it's turned out it's very very easy and seems very safe too!
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Android_Dog_Walker said:
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Click to expand...
Click to collapse
EpicFail2017 said:
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017
Click to expand...
Click to collapse
Anyone uploading a mirror of nougat TWRP, please.
Also i´m kind of shy flashing the recovery with patched boot.img, any experience?
Someone with nougat and superSU here? Magisk seems to have some errors with some xposed moduls duo lag of "su-root-floder"
Do you password protect your recovery?
I have now tried the Magisk and TWRP routes to achieve rooting. My preference is the TWRP route because it has the fewest steps and works!.
An point worth noting is that if you are a new user on needrom, you need to register using Chrome, Firefox or other non Microsoft browser. Once registered Microsoft Edge works. I don't know why the registration with Edge fails but It is annoying when you complete the process and do not get the registration e-mail. Without registering you cannot get the TWRP download referenced above.
Hi,
Everything seems fine except if i make a wipe of dalvik cache every app stop working. The only solution is to wipe data or flash rom again with flashtool.
any can fix it on TWRP 3.1.1.1 ?
EpicFail i´m not sure, maybe security related issue. Instead of flashing rom i prefer restore backup^^
Still did not find a public nougat TWRP download
Both old 6.0 twrp freeze if timer is set and screen is going to turn off. Isn´t an issue anymore?
Today i hardly crashed system, it was in relation to magisk modul (busybox) update issue https://forum.xda-developers.com/apps/magisk/module-canstantly-module-updated-reboot-t3696943
EDIT: switched to supersu, busybox now working
Yesterday xposed appsops was getting a fix it is still unoffical
https://forum.xda-developers.com/xposed/modules/xposed-appopsxposed-appops-4-3-t2564865/page89
Edit:
updated to magisks unoffical xposed framework 3.1.4
Follow the instructions
Files required to be download:
Aosp 9:here
build.prop: here
Flash GSI with TWRP use this fix sd card not read in twrp here
reboot to twrp by pressing power + volume up
Perform a factory reset within TWRP. format data
Download and extract system-arm-aonly-gapps-su.img.xz and you will get system-arm-aonly-gapps-su.img
Transfer the system-arm-aonly-gapps-su.img from your PC to your device’s internal storage where TWRP can access it.
Tap on “Install
Change the type from “zip” to “image.
Find and select the system-arm-aonly-gapps-su.img you downloaded.
Choose to flash to the system partition
no need to flash modified vendor
Once that is done, reboot your device.
Fix : performance copy the build.prop to system/
Bugs: google certification (fix here) after registration clear the google apps data (framewrork/services)
XDA:DevDB Information
Aosp 9 Redmi Go, ROM for all devices (see above for details)
Contributors
samsungics1200, phhusson
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: Aosp 9
Version Information
Status: Testing
Current Beta Version: April 16 2019
Created 2019-04-17
Last Updated 2019-06-11
is there any bug?
Fix : performance copy the build.prop : here copy to system/
Click to expand...
Click to collapse
File needs permission to access - is there another link?
Thanks - the file is available for download now.
I have installed the ROM and it works well but do you know if it is possible to disable the forced device encryption?
Also, my SIM2 is not recognised. Any ideas?
Auto booting to fastboot after installing... (installed to redmi go, it is unlocked, followed instruction, tried minimum 3-4 times, tried several variants of 9.0 Pie GSI etc.)
If You installed 9.0 by the instruction above and it successfully started, it means there is some hardware difference between different region redmi go devices. Mine is Global version.
Stock 8.1 GO is installing and starting normally from TWRP. Problem occurs only with the rom from this thread.
I want to switch to 9.0 beacuse stock 8.1 GO have push notification issue. Believe me, I tried everything to fix it, but unsuccessfully...
Waiting for Your help.
Instructions
NOTE: Do not flash the vendor file from the OP, that causes bootloops on my device.
This is what I did - now happily running AOSP 9:
- Restore stock firmware (http://en.miui.com/download-365.html)
- Reboot then perform system update to get latest release
- Reboot to bootloader (fastboot mode)
- Download the GSI image from the OP
- fastboot flash system system-test-20190415-arm-a.img
- Boot to TWRP recovery
- Mount system partition
- Replace /system/build.prop with one from OP
- Reboot
Additionally, if you want to disable encryption:
- Format data partition (You will loose all of your data!)
- Download vendor image file from OP
- Extract default.prop and fstab.qcom
- Mount vendor partition
- Replace extracted files to phone
Update
Hello to my Russian friends who are following this thread from http://4pda.ru/forum/index.php?showtopic=939092&view=findpost&p=84933744
I have attached the files that need to be replaced to this post
hello guys. i have tried both procedures. it gets stuck on "android" logo (booting i guess).
shall i use vendor? shall not use vendor?
"
- Restore stock firmware (http://en.miui.com/download-365.html)
....
- Replace /system/build.prop with one from OP
- Reboot"
now it should boot?
i tried stopping here, and no luck. i tried doing those "additionally.." steps, same lack of luck.
You only need to touch vendor if you want to disable forced encryption.
These instructions worked when I posted them on 4pda:
- Unlock bootloader - there are instructions elsewhere
- Download: http://treble.phh.me/system-test-20190415-arm-a.img (system.img)
- Download TWRP from other thread (trwp.img)
- Download files.zip from my previous post and extract build.prop
- Power off the phone
- Press volume down and power buttons to go to fastboot bootloader
- Connect your phone to your computer via usb cable
- Type in terminal: fastboot flash system system.img
- Wait for process to finish
- Type in terminal: fastboot boot twrp.img
- Phone will reboot to TRWP recovery mode
- Select "Mount" then "System"
- Type in terminal: adb push build.prop /system/
- Type in terminal: adb shell chmod 600 /system/build.prop
- Reboot phone
If you need GApps, grab the latest pico from https://github.com/opengapps/arm/releases - ie https://github.com/opengapps/arm/releases/download/20190507/open_gapps-arm-9.0-pico-20190507.zip - and install from TWRP.
in locks every time in the "Encryption unsuccessful ... RESET PHONE"
/vendor issue
What process did you use? Did you touch the /vendor partition? Does formatting /data from TWRP help?
Restore stock formware (all partitions from fastboot) then follow steps here: post 10
Camera issue
Only issue I spotted on this ROM for now is - Camera quality became worse. Is it a driver or just app level issue?
This is a Project Treble device which means that the drivers remain untouched in the /vendor partition and the new GSI uses them, unlike older ROMs which contained their own drivers. Which version of firmware did you have before installing the GSI? On 4pda it was observed that camera2 api apps was the issue but I have not seen any such problem.
Just updated to the May 2019 build (v113) and all is good - just had to resize the image to fit the partition. I shall keep updating monthly as long as phh keeps making them.
The ROM from the original post is no longer available. If anyone is interested then I can make an updated GSI available.
Note: FM radio is missing
Kyuunex said:
Note: FM radio is missing
Click to expand...
Click to collapse
Indeed, but the developer is on it, follow progress here: Include FM Radio app
I can't find a gsi that will fit my system partition
need the smallest GSI possible for an obscure mt6580 device
EDIT: would love to try the outdated image that's no longer available ANYWHERE
This guide is specifically aimed for Z010DD users who want to flash custom ROMs:If you want to stay on stock and only wanna flash TWRP and root the Stock ROM, please skip this thread and refer to @jide1 's guide here instead: https://forum.xda-developers.com/as...ot-asus-zenfone-max-zc550kl-qualcomm-t3652518
Things to be noted beforehand:
1. Make sure you are on the latest/final stock rom/firmware
2. Need Unlocked bootloader (Linked below, install the apk and follow the steps)
3. Take backup of all of your data from the internal storage. (To avoid depression if accidentally wiped your precious data)
4. Minimal ADB and Fastboot (Thread Linked below, Download from there and follow on-screen steps).
Steps:
A. To flash TWRP:
1. Once you have unlocked the bootloader, download 'minimal adb and fastboot zip' and PBRP zip(extract img from it).
2. Boot into fastboot by switching off the device, then POWER + VOLUME 'UP'. (You'll enter CSC ode screen, which is fastboot so don't worry)
3. Place the recovery image into the fastboot folder and open a command window there.
4. Connect your device, then type 'fastboot devices' and Enter, just to verify if your device is shown.
5. type: fastboot flash recovery recoveryname.img
THE NEXT STEP IS IMPORTANT, Pay Attention.
6. Now REBOOT Directly to twrp by holding POWER + VOLUME 'DOWN'. Don't boot into system else stock recovery will get restored.
B. Preparing for Flashing ROMs:
Once you have booted to twrp successfully, you will need to 'format' all the partitions, which includes:
System, Data, Cache, Dalvik/ART Cache, & Internal Storage.
HERE YOU WILL LOSE ALL OF YOUR DATA, YOU HAVE BEEN WARNED ALREADY SO, yeah.
Click to expand...
Click to collapse
1. In TWRP, go to WIPE -> ADVANCED WIPE;
2. Select the above listed partitions and then SWIPE TO WIPE.
Note: You will notice a partition called 'ASDF' ,wipe/skip, doesn't matter.
3. Come back to home, go to REBOOT -> RECOVERY
C. Flashing ROMs:
1. Download the ROM, Patch, and Kernel zip (Linked Below).
2. Flash them in the mentioned order.
3. Flash Opengapps (if needed) (Nano Gapps recomended).
4. Reboot.
(NOTE: FOR MAGISK, FLASH IT 'AFTER FIRST BOOT ONLY', AND IF FLASHING ZIP NOT WORKING, THEN see POST #3)
Bugs and Notes:
1. Notification LED doesn't BLINK when a notification arrives, it stays on (colors are correct though).
2. VoLTE is broken on pie roms (ignore the volte logo), stick to Oreo if you want VoLTE. (LTE data works fine).
3. Reboot Sometimes get stuck in black screen, its RANDOM, LONG Press the power button for 15 secs instead if that happens.
4. If any ROM contains 'Always On' functionality, disable it as the feature doesn't work properly. (Ambient display has no issues)
Links: Refer POST #2 .
Credits:
@SakilMondal for roms.
@YaAlex for kernel and patch for Z010DD.
Myself for testing.
Created 2019-04-22
Last Updated 2019-05-20
Links:
ROMs: https://sourceforge.net/projects/zenfone-max-updates/files/Z010D/ (Please flash the latest ones only, don't use old ones)
Patch (link updated): https://anonymousfiles.io/3WLplRtD/
Kernel (link updated + new kernel update): https://anonymousfiles.io/m4oKP6wL/
TWRP Recovery (Image file, Flash via fastboot): https://drive.google.com/file/d/1txHT0vRNo0gTMkD0Sb5kpuQQT0dAiphH/view
ASUS Official Bootloader Unlock Tool for 8939 Devices: http://dlcdnet.asus.com/pub/ASUS/Ze...513.74708998.1502054577-2083321676.1502054577
Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
Troubleshooting:
Instructions for Magisk:
1. Extract boot image from the rom zip
2. Go to Magisk Manager app
3. Tap 'Install' next to 'Magisk is not installed' line.
4. Tap 'Select and patch a file'
5. Navigate to the extracted boot image. It will now create a new boot image and save it in mentioned location.
6. Reboot to recovery, Flash the Boot image + KERNEL zip.
7. Reboot to system.
To fix CTS Mismatch in Magisk:
Open /system/build.prop, replace the line 'ro.build.fingerprint=' with:
Code:
ro.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys
Open /system/vendor/build.prop , replace the line 'ro.vendor.build.fingerprint=' with:
Code:
ro.vendor.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys
Patch is required for sd410 devices??
koushik99 said:
Patch is required for sd410 devices??
Click to expand...
Click to collapse
Nope, patch is only for DD.
Guide has been updated. Please check.
unable to flash GAPPS
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl
I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?
PRASAD.ASRS said:
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl
Click to expand...
Click to collapse
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.
ihatebarrels said:
I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?
Click to expand...
Click to collapse
In both oreo and pie, for both z010d and dd, reboot and shutdown is an issue
It doesn't happen everytime, its random, and no fix is found yet.
Is it working on asus zenfone max 2016 sd 615?
Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files
james_imch said:
Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files
Click to expand...
Click to collapse
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).
Kaustav365 said:
Is it working on asus zenfone max 2016 sd 615?
Click to expand...
Click to collapse
Hope you have read the OP properly
This thread is only for sd615/Z010DD/MSM8939, and its clearly mentioned.
TechNova said:
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).
Click to expand...
Click to collapse
PBRP Recovery (flashable zip) link is also not working. Please update it.
james_imch said:
PBRP Recovery (flashable zip) link is also not working. Please update it.
Click to expand...
Click to collapse
Done,
Removed pbrp and now Twrp link posted.
TechNova said:
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.
Click to expand...
Click to collapse
Hey! I am also facing the same issue. I tried the nano version of Gapps on my Asus Zenfone Max Z010D and my phone is still crashing it keeps restarting and then automatically turns off. Is there any issue to fix this?
unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939
Eric0000 said:
unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939
Click to expand...
Click to collapse
I too facing same problem
Unlocking the apk no longer works
Hello, so, my problem is same as title says.
I´ll try to write it as short as possible.
I tried to install Resurrection Remix, Lineage OS, Arrow OS, BootLeggers ( All are unofficial builds for my Redmi 6 ), but everytime I got the constant rebooting bootloop, so I need to go to TWRP and flash Official MIUI ROM
Here are my installation steps for Resurrection Remix ( Pretty same as In this Tutorial ) :
1. - I went to TWRP ( LR. Team TWRP 3.3.1 )
2. - It was showing Internal Storage (0MB), so I click on Wipe - Format Data - yes
3. - After that also Wipe - Advanced Wipe - I selected Dalvik / ART Cache, System, Cache, Data, Vendor
4. - I moved RR Flashable .zip file and Magisk v19.3 from my PC to phones Internal Storage (via USB Cable)
5. - I clicked on Install - RR-P-v7.0.2-20200111-cereus-Unofficial.zip - Add more zips - Magisk-v19.3.zip
6. - After that, I clicked on Wipe cache/dalvik, checked if I´ve got any errors and clicked on Reboot
7. - After that, phone started to restart around every 5 seconds until I went to TWRP and Installed Official MIUI ROM
BONUS. - Tried also on second try to flash MIUI Firmware before RR .zip file, but the results were same.
Also I don´t want Gapps in my phone so i didn´t flash them.
With other ROMs it was same, always bootloop. Here are all .zips, links to forums, tutorials that I followed.
So please message me what´s the issue, especially while installing Resurrection Remix, because this is the ROM that I would like to install the most.
I know it's too late for reply I'm just posting this so that others (like myself) can see this. Lets keep the community for this phone alive!
Install MIUI V10.4.4.0 (I found that this version works for me), Disable DM verity (https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/) and finally wipe data and install your custom rom.
It will bootloop on the first boot so wait a few seconds then force reboot