Related
Hey all,
I noticed many people seem to be having problems with the new OTA update (174.44.1 US). I also tried to update and my Moto G went into a bootloop. After much tinkering, I found a possible solution.
As far as I can tell, the update problems are caused by:
- Xposed modules like Gravitybox (not really sure why)
- Hacks like the H/H+ hack that replaces SystemUI.apk
- Any other mod that changes something in /system
This is what I did:
(Note that I have 4.4 Stock, rooted and PhilZ CWM recovery. Xposed, Gravitybox, H/H+ hack and Logo hack)
- Downloaded the zip from http://forum.xda-developers.com/showthread.php?t=2653978
- Placed it in the SD of the phone
- Unchecked all modules in Xposed and rebooted
- Rebooted again, this time into PhilZ and installed the update zip from the SD
It showed me an error with SystemUI.apk (and I remembered changing it for the H,H+ hack). So I went and restored the original.
Then I tried again. It went smoothly. And I still have root
Now I'm just waiting to see if the new SystemUI.apk is different from the old one before I restore the hack.
NOTE: For those who can't remember any/all changes made to /system, the stock system.img should be flashed in fastboot mode.
Hope this is useful...
(FIRST THREAD!:laugh
[UPDATE]: I have included my stock SystemUI.apk and .odex. Copy into /system/priv-app, overwrite existing files and set permissions to rw-r--r--.
All Xposed tweaks can be undone by unselecting the modules in the Xposed framework and rebooting.....before rebooting again into recovery..
UPDATE: Added the version of Philz recovery I use, for those with the "this package is for falcon_umts devices : this is a xt1034" error.
Extract into your fastboot folder and issue command:
fastboot flash recovery PhilZ.img
That should set all that straight...
When you say stock system.img do you mean system.img_sparsechunk1 2 and 3? Would I just flash them with fastboot flash system system.img? Would it wipe anything other than mods made in the system folder?
draco259 said:
When you say stock system.img do you mean system.img_sparsechunk1 2 and 3? Would I just flash them with fastboot flash system system.img? Would it wipe anything other than mods made in the system folder?
Click to expand...
Click to collapse
It will return the system folder to default. All changes should be reset, as far as I can tell...
secretkloud said:
Hey all,
I noticed many people seem to be having problems with the new OTA update (174.44.1 US). I also tried to update and my Moto G went into a bootloop. After much tinkering, I found a possible solution.
As far as I can tell, the update problems are caused by:
- Xposed modules like Gravitybox (not really sure why)
- Hacks like the H/H+ hack that replaces SystemUI.apk
- Any other mod that changes something in /system
This is what I did:
(Note that I have 4.4 Stock, rooted and PhilZ CWM recovery. Xposed, Gravitybox, H/H+ hack and Logo hack)
- Downloaded the zip from http://forum.xda-developers.com/showthread.php?t=2653978
- Placed it in the SD of the phone
- Unchecked all modules in Xposed and rebooted
- Rebooted again, this time into PhilZ and installed the update zip from the SD
It showed me an error with SystemUI.apk (and I remembered changing it for the H,H+ hack). So I went and restored the original.
Then I tried again. It went smoothly. And I still have root
Now I'm just waiting to see if the new SystemUI.apk is different from the old one before I restore the hack.
NOTE: For those who can't remember any/all changes made to /system, the stock system.img should be flashed in fastboot mode.
Hope this is useful...
(FIRST THREAD!:laugh
Click to expand...
Click to collapse
Hi can you include your original systemui.apk i lost mines >.<
serophia said:
Hi can you include your original systemui.apk i lost mines >.<
Click to expand...
Click to collapse
Added to first post...
secretkloud said:
Added to first post...
Click to expand...
Click to collapse
i restored recovery, disabled all mods, unrooted, and did a factory reset when i try to install update i get an "error" in stock recovery? Any other suggestions i should do?
EDIT: nvm fixed by flashing system.img adaway was the problem for me >.<
Error when in recovery
I downloaded the zip but when I go to CWM recovery and try to install it from the SD it shows me an error.
it says; This package is for "falcon_umts" devices; this is a xt1032.
any help?
Maybe you'll find the solution to your problem here.
thanks!!
mokkami said:
Maybe you'll find the solution to your problem here.
Click to expand...
Click to collapse
thanks dude, now I just gotta know how to change the recovery haha
Thanks
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
mdentener said:
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Why root??
OP says he kept root after update was applied??
Sent from my Nexus 7 using Tapatalk
mdentener said:
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Same thing for me!
Is this gonna be worked with the last update 176...
i have used ur system ui but i still get the error
serophia said:
i restored recovery, disabled all mods, unrooted, and did a factory reset when i try to install update i get an "error" in stock recovery? Any other suggestions i should do?
EDIT: nvm fixed by flashing system.img adaway was the problem for me >.<
Click to expand...
Click to collapse
Adaway modifies the "system/etc/hosts" file. It should also be disabled before updating.
irishpancake said:
QUOTE=mdentener;50672956]Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Why root??
OP says he kept root after update was applied??
Sent from my Nexus 7 using Tapatalk[/QUOTE]
I kept my root also after the update. Those mods were installed before the OTA and remained installed after. I only disabled xposed modules temporarily and changed CWM to Phil's CWM to install the OTA.
Sent from my Moto G using Tapatalk
This post is to get TWRP running properly on a G2 that has updated to 5.0
There is an apk called autorec.apk that is supposed to install TWRP, and it does, but when you reboot, it gives you a security error and shuts the phone down. Basically soft bricks it. This method is what i used to install twrp and allow flashing of custom ROMs.
First, downgrading to 4.4.2 is not only fairly easy, it is also necessary to get TWRP working properly.
Download and install the LG flashing tool here
then do the same with the LG driver found here
Then youre going to need 2 files for the flashing tool
1: LG Flashing dll
2: the 4.4.2 image that the flashing tool installs here
instructions for using the flashing tool are found here
Make sure to follow all of the instructions including changing the port # for the device to 41
After flashing back to 4.4.2, using towleroot to root takes mere seconds to complete
after that, download TWRP and place the file somewhere easily located on your phone.
Install Flashify, and use it to flash the TWRP 2.8.6.0 D800 image file for your custom recovery.
VERY IMPORTANT!! Reboot your phone to recovery and once in recovery, be sure to reboot recovery from within TWRP before rebooting system.
After that is done, you are ready to flash custom ROMs.
This is the procedure I used and it worked like a charm. There might be other methods that work, but this one positively worked for me on the D800 i dealt with.
I know this set of instructions isnt as pretty as other tutorials, but it works. Let me know if you have any issues with the links or process.
The way I have done it on my 5.0 d800 G2, first root with One Click root from Windows, then install SuperSU from play store, autorec, then install TWRP. No problems whatsoever.
Im glad that your method worked for you! The G2 i was working on belonged to a friend of mine and it kept bootlooping using your method. So, i guess for those who encounter the same issue that I did, they can use the method listed above
MIUI 8 GLOBAL BETA 6.8.11 reported for DOOGEE DG700
Requirements:
Stock 4.4 KK firmware installed on the phone
Custom recovery
A working brain ... and some patience!
Credits:
All credits go to team ARGN for crossporting MTK6592 to MTK6582 and updating their ported rom here
Me for porting from Gionee M2 to DG700
Feautures:
Cross ported from the latest MIUI8 xiaomi.eu release for Redmi Note. (credits go to team ARGN)
DG700 rom uses as base TEAM ARGN crossports from MTK6592 to MTK6582.
Working: dual sim 3g (using dual sim control apk), wifi, bluetooth, gps, camara, sdcard, and everything else.
No chiness apps
All gapps preinstalled as system apps.
Enhanced camera pics quality (must be enabled in camera settings).
Repartitioned internal storage to 6G, custom carliv touch recovery (using stock kk firmware in the downloads at the end of the post).
Xposed and xposed modules working.
Many more ...
Known bugs:
Theme apk SOMETIMES FC's, but themes are working.
NVRAMWARNING wifi bug, easilly fixable (search xda or google for fix), wifi works just ok even with the NVRAMWARINING bug.
Battery capacity will be shown only at 3100mah, even so battery life is far more superior than the actual R25 lollipop firmware for DG700. (I get about 3 days with wifi / data on, moderate usage of the phone on the current MIUI8 based on kk rom)
Custom recovery CTR touch NOT WORKING. USE HARDWARE KEYS!
Installing
Download DG700_MIUI8_beta_global_6.8.11.zip (link at the end of the post), copy it on the sd card.
Download Stock R14 firmware linked at the end of the post (the attached build INCLUDES CTR custom recovery and repartitioned internal storage to 6G), unzip the archive and flash it with sp flash tools.
After flashing R14 go directly to recovery, DO NOT BOOT into android.
Once in recovery take the following steps:
1. Wipe and Format Options > Clean to Install a new rom ... wait for the recovery to wipe system, data, go back to the main menu
2. Install zip > Choose zip from storage/sdcard1 > browse for DG700_MIUI8_beta_global_6.8.11.zip and select it, install and wait for the installer to finish, go back to the main menu
3. Reboot system now, when asked to install su / root phone, select NO! (if you want to root the phone later you can install Chainfire SU binaries from the recovery, and than SU app from the market)
Wait for the rom to load, for the first time it will take some time ... be patient.
If you are not on stock KK THIS WILL NOT WORK! After flashing R14 firmware you will loose the IMEI's. Follow the guide frome here to restore the IMEI's:IMEI REPAIR / RESTORE /BACKUP
Customizing ... well ... the sky is the limit ... I use Plak to remove titles from the hotseat / launcher icons (as you cans see in the attached screenshots) and MIUI Tweaks for status bar (notification bar) customization ...
IF ALL GOES WELL or IF YOU ENCOUNTER ANY PROBELMS PLEASE POST BACK!
If this post helped you hit the Thanks button!
ENJOY!
Downloads:
DG700 R14 Stock KK with CTR and repartitioned internal memory: DOWNLOAD LINK
DG700 MIUI8 xiaomi.eu global beta v6.8.11: DOWNLOAD LINK
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
simchaleh said:
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
Click to expand...
Click to collapse
You will need to use spflash tool and the stock rom attached in my first post in order to install (flash) kitkat. Search google or xda for a tutorial on how to use spflash tool.
Have in mind that this is an advanced process and many things might go wrong if you don't have experience with flashing the whole android on your phone.
I think that at some point even doogee had a tutorial at their site showing how to upgrade from kitkat to lollipop (see here: http://www.doogee.cc/download.php?ProId=41). It is the same process only you need to format the whole phone before flashing and instead of flashing lp use kk images and scatter attached by me. If you're not sure what you are doing do some research first ... there are lots of great tutorials on the net for spflashtools and mtk6582 phone. Also have in mind that for some newer DG700 models it is impossible to flash kitkat because of some drivers issues ... or so it was stated on the 4pda.ru dg700 thread.
Hey @tvladan,
thanks a lot for this thread!!!
My experience and feedback:
All went smooth until I booted with the Miui installed. Because the IMEI problem I was not able to log into android (use than play store) nor Miui and the system would not let me go any further until I could by magic.
IMEI
I could not log in (system need unique phone ID such IMEI) so I needed to get the apks and move/save on the sdcard to be installed.
I could not restore the IMEI with MTK which was suggesting a reset in order to fix it and I had no clue how to reset (not reboot).
Mobile uncle. I made a IMEI backup but even if the app was restoring without problem, it really did not do anything also after rebooting
Chameleon: the only app that did something although not permanent. I'm working to fix it
Nvram error: fixed with no issue as on this thread
MIUI: it is definitively a nice designed UI although the one I personally do not prefer. It is flexible if you want to do things as developers allow you which is on my opinion sometime to strick if we consider we all are looking for a rooted phone and than we are bond by the UI. For sure there are some features that are useful as were some I really appreciate from the stock ROM. One example: I agree that moving app to the SD card might slow down the system and use more battery but now that I've achieved a 6GB rom I'm using all of it for the app and just marginal cache/data will be saved on the SD....
@tvladan: If I'd like to try only the KK rom without the MIUI and avoid the IMEI problem, are the following steps correct:
1) restore LP with TWRP
2) install stock R14 KK
3) install your KK with 6gb partition
If this is correct, in all this writing and overwriting, is there any chance I'll flash the recovery TWRP?
In case it will happen, can I use the one as by this thread by @NaturalBornCamper
thanks and enjoy your DG700
ciao
gipsea said:
Hey @tvladan,
thanks a lot for this thread!!!
If I'd like to try only the KK rom without the MIUI and avoid the IMEI problem, are the following steps correct:
1) restore LP with TWRP
2) install stock R14 KK
3) install your KK with 6gb partition
If this is correct, in all this writing and overwriting, is there any chance I'll flash the recovery TWRP?
In case it will happen, can I use the one as by this thread by @NaturalBornCamper
thanks and enjoy your DG700
ciao
Click to expand...
Click to collapse
Yes you can install stock kk but not using the steps you posted. You can not restore it via twrp, you must flash it with spflash tools (using format mode, kk or lp, as you please) BUT you will still loose imei's. This happens because of the format method used by spflash tools, in most MTK phones, that erases all the internal partitions of the phone.
Regarding LP, there is a latest firmware (official) by dooge - R25 that has the internal memory repartitioned to 5.5Gb. I would recommand installing that and than rooting (if needed) via twrp using chainfire binaries. You can download the R25 from here: https://docs.google.com/uc?id=0B_UWiyCZx5s1Z2xxZTRYTE9OcGc&export=download. The thread by NaturalBornCamper is old, deprecated and useless now. That was in the beggining when we did not have a custom recovery or the knowledge on how to root / repartition the DG700 phone.
Regarding lost IMEIS i RECOMMAND the MAUI 3G METHOD to restore them for our phone presented here: http://forum.xda-developers.com/unite-2/general/guide-repair-imei-invalid-micromax-t3048984 It needs a little more work, but once the correct drivers are installed it should work no matter what! (It also has a video tutorial, with some patience and little knowledge you should succeed in properly restoring the IMEI's). In your situation, whatever rom / firmware you will flash now using spflsh tools it will NOT restore the imei's because the nvram was formated.
Good Luck!
LE: To sum it up, to have the latest LP, repartitioned and rooted you will have to follow these steps (and have some knowledge on how to use spflash tools)
1. Flash R25 using spflashtools in format mode.
2. Start up the phone, wait to boot into android (just wait, it will take a while because it will encrypt the data partition). Setup the phone, fix imei's using maui 3g tool methond posted above. At this point you should have a "re-partitioned", unrooted, on stock recovery phone with the proper IMEI's
3. Download the latest chainfire su binaries from here: https://download.chainfire.eu/696/supersu/ and copy the zip to sd card. (UPDATE-supersu-v...... link)
4. Flash TWRP using spflashtools in download mode.
5. DO NOT START ANDROID, Reboot the phone in recovery mode witch should be now twrp that you just flashed before. If you start up android it is possible and very likely that it will restore the stock recovery, but if restarting in twrp first it will override the restoring of the stock recovery forever.
6. Flash the update-supersu-file via twrp
7. Reboot the phone in andorid (if asked by twrp to root, select NO), go to the market, instal chainfire supersu apk, and voila you are now on the latest LP (witch is repartitioned), custom twrp recovery and rooted.
if you need the link to twrp only pls post back I'll upload it somewhere for you!
ciao @tvladan,
thanks for your reply.
Quick question: as I did back up the LP with TWRP including NVRAM, if I restore it will it be permanent? I read the thread you suggested about IMEI/NVRAM but if this work it is a straight shot
I'd like to try the R25 LP and KK. Did you tried both? KK apparently was better compared to the LP up to R24.
Thanks
gipsea said:
ciao @tvladan,
thanks for your reply.
Quick question: as I did back up the LP with TWRP including NVRAM, if I restore it will it be permanent? I read the thread you suggested about IMEI/NVRAM but if this work it is a straight shot
I'd like to try the R25 LP and KK. Did you tried both? KK apparently was better compared to the LP up to R24.
Thanks
Click to expand...
Click to collapse
LP moves a little slower than kk. Nothing to worry about. Regarding battery life there is a 12 -24 hours difference from lp to kk, kk lasting longer. If you install xposed framework on lp it will move a LOT slower. If you do not need xposed I recommend R25 LP. Also I have no knowledge of TWRP being able to backup nvarm. I might be wrong. All you can do is try different methods until you succeed. It is a devious and annoying process but when you get it right you'll be satisfied. Also after lots of hours fking around with this phone I really stand by the steps posted in my previous post as to how to repartition / root / repair imeis the fastest way!
simchaleh said:
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
Click to expand...
Click to collapse
tvladan said:
Yes you can install stock kk but not using the steps you posted. You can not restore it via twrp, you must flash it with spflash tools (using format mode, kk or lp, as you please) BUT you will still loose imei's. This happens because of the format method used by spflash tools, in most MTK phones, that erases all the internal partitions of the phone.
Regarding LP, there is a latest firmware (official) by dooge - R25 that has the internal memory repartitioned to 5.5Gb. I would recommand installing that and than rooting (if needed) via twrp using chainfire binaries. You can download the R25 from here: https://docs.google.com/uc?id=0B_UWiyCZx5s1Z2xxZTRYTE9OcGc&export=download. The thread by NaturalBornCamper is old, deprecated and useless now. That was in the beggining when we did not have a custom recovery or the knowledge on how to root / repartition the DG700 phone.
Regarding lost IMEIS i RECOMMAND the MAUI 3G METHOD to restore them for our phone presented here: http://forum.xda-developers.com/unite-2/general/guide-repair-imei-invalid-micromax-t3048984 It needs a little more work, but once the correct drivers are installed it should work no matter what! (It also has a video tutorial, with some patience and little knowledge you should succeed in properly restoring the IMEI's). In your situation, whatever rom / firmware you will flash now using spflsh tools it will NOT restore the imei's because the nvram was formated.
Good Luck!
LE: To sum it up, to have the latest LP, repartitioned and rooted you will have to follow these steps (and have some knowledge on how to use spflash tools)
1. Flash R25 using spflashtools in format mode.
2. Start up the phone, wait to boot into android (just wait, it will take a while because it will encrypt the data partition). Setup the phone, fix imei's using maui 3g tool methond posted above. At this point you should have a "re-partitioned", unrooted, on stock recovery phone with the proper IMEI's
3. Download the latest chainfire su binaries from here: https://download.chainfire.eu/696/supersu/ and copy the zip to sd card. (UPDATE-supersu-v...... link)
4. Flash TWRP using spflashtools in download mode.
5. DO NOT START ANDROID, Reboot the phone in recovery mode witch should be now twrp that you just flashed before. If you start up android it is possible and very likely that it will restore the stock recovery, but if restarting in twrp first it will override the restoring of the stock recovery forever.
6. Flash the update-supersu-file via twrp
7. Reboot the phone in andorid (if asked by twrp to root, select NO), go to the market, instal chainfire supersu apk, and voila you are now on the latest LP (witch is repartitioned), custom twrp recovery and rooted.
if you need the link to twrp only pls post back I'll upload it somewhere for you!
Click to expand...
Click to collapse
About #4), flash TWRP. I have used the one posted by @NaturalBornCamper on his thread on step 11
If the TWRP for KK is different please post
I'm working on R25
Next fun step, R14
Thanks
It is the same twrp, works on kk and lp. You have the right one. For r25 it does not matter on what you are now, the spflashtool needs to format all the phone in order to install r25.
Thanks and good to know.
Now I'm getting curious about NVRAM/IMEI and TWRP...
TWRP can make backup of NVRAM and I did before installing the KK with MIUI8.
If I understood correctly IMEI information is stored in the NVRAM so, theoretically, if I restore the first back up of the NVRAM I should restore also the IMEI?!?!?!
how can I check the difference between a temporary IMEI installation like with chamelephone from a permanent solution?
ciao
gipsea said:
Thanks and good to know.
Now I'm getting curious about NVRAM/IMEI and TWRP...
TWRP can make backup of NVRAM and I did before installing the KK with MIUI8.
If I understood correctly IMEI information is stored in the NVRAM so, theoretically, if I restore the first back up of the NVRAM I should restore also the IMEI?!?!?!
how can I check the difference between a temporary IMEI installation like with chamelephone from a permanent solution?
ciao
Click to expand...
Click to collapse
All you can do is try to restore via twrp ... temp imei restore should be erased at reboot.
Thank you for this very Good rom. it's better than the stock KitKat
Do you have any resurrection remix for this device or any marshmallow based on KitKat kernel..please
Unfortunately no, i moved to a mi5 last year and placed my old doogee in a drawer for safe keeping. This is the last port i made.
tvladan said:
Unfortunately no, i moved to a mi5 last year and placed my old doogee in a drawer for safe keeping. This is the last port i made.
Click to expand...
Click to collapse
Sorry for bothering you again . I just wanted to know if it is possible to restore lollipopTWRP backup without flashing stock lollipop with flashing tool . When I'm on KitKat..is it possible to just flash The kernel .
Thank you
zidane01 said:
Sorry for bothering you again . I just wanted to know if it is possible to restore lollipopTWRP backup without flashing stock lollipop with flashing tool . When I'm on KitKat..is it possible to just flash The kernel .
Thank you
Click to expand...
Click to collapse
Unfortunately it is not possible to restore lolipop over kitkat or opposite because of the big differences in partition tables used by each of them. So the only way to restore a nandroid image is to flash stock with spflash tools with format, install the custom recovery and than restore the recovery backup.
tvladan said:
Unfortunately it is not possible to restore lolipop over kitkat or opposite because of the big differences in partition tables used by each of them. So the only way to restore a nandroid image is to flash stock with spflash tools with format, install the custom recovery and than restore the recovery backup.
Click to expand...
Click to collapse
Ok thank you...then I better stick with kitkat even do some applications stopped supporting it.
You can move to doogee s60, it's on sale on gearbest and it is way better than titans s2. Also comes with android n from factory.
tvladan said:
You can move to doogee s60, it's on sale on gearbest and it is way better than titans s2. Also comes with android n from factory.
Click to expand...
Click to collapse
Thank you for the tip but I will stick with my beloved dg700 until it dies or I die.. Lol
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Code:
SYSTEMLESS=true
So the best is to make sure you don't use an older version of SuperSU than 2.79 SR3!
That's it and it works. SuperSU.apk is going to be installed in step 6.
Successfully tested with XT1642, XT1622 (eta82), XT1643 (Adarsh balu), XT1644 (WTF?), XT1641 (EkisDeMX).
It's the same old guide man. Please see before posting if similar threads exist. XDA is getting confusing for the common non-techie person anyways.
Works perfect on Moto g4 (XT1622) :good:
I've tried to install SuperSU before and it didn't work on my device XT1640. I've got a bootloop and had to flash stock ROM (now I'm using another supersu). Does it really work now? Cuz I don't want to get a bootloop again and lose all my data.
Dex5er said:
I've tried to install SuperSU before and it didn't work on my device XT1640. I've got a bootloop and had to flash stock ROM (now I'm using another supersu). Does it really work now? Cuz I don't want to get a bootloop again and lose all my data.
Click to expand...
Click to collapse
You have to use SuperSU v2.79 SR3. If you use any older version, it won't install systemless and causes bootloops.
Which version of SuperSU did you flash?
And you have to flash ElementalX kernel before installing SuperSU. Otherwise you will get bootloop too.
tywinlannister7 said:
It's the same old guide man. Please see before posting if similar threads exist. XDA is getting confusing for the common non-techie person anyways.
Click to expand...
Click to collapse
Didn't find any thread which describes the method rooting with SuperSU in the first post and as its topic.
In some threads (with other topics like how to root with phh's SuperUser) there is in the discussion mentioned this method with SuperSU but nobody will ever find these posts...
disguisedview said:
You have to use SuperSU v2.79 SR3. If you use any older version, it won't install systemless and causes bootloops.
Which version of SuperSU did you flash?
And you have to flash ElementalX kernel before installing SuperSU. Otherwise you will get bootloop too.
Click to expand...
Click to collapse
I've installed ElementalX Kernel first then I installed SuperSU and I've got a bootloop. I used SuperSU v2.62 and got a bootloop, then I tried with SuperSU v2.74 and also got a bootloop.
Dex5er said:
I've installed ElementalX Kernel first then I installed SuperSU and I've got a bootloop. I used SuperSU v2.62 and got a bootloop, then I tried with SuperSU v2.74 and also got a bootloop.
Click to expand...
Click to collapse
Ok, seems to be the reason. You have to use version 2.79 SR3 or newer if available.
Otherwise it won't work without further modification...
disguisedview said:
Ok, seems to be the reason. You have to use version 2.79 SR3 or newer if available.
Otherwise it won't work without further modification...
Click to expand...
Click to collapse
Alright, is there any problem if I unroot my device with this supersu and root again with the SuperSU that you said, will I get any problem? Do I have to reinstall ElementalX Kernel and twrp again?
Dex5er said:
Alright, is there any problem if I unroot my device with this supersu and root again with the SuperSU that you said, will I get any problem? Do I have to reinstall ElementalX Kernel and twrp again?
Click to expand...
Click to collapse
I don't know. If you have backup of your partitions then flash your original system and boot partition and start from beginning (ElementalX and then SuperSU 2.79 SR3).
If you don't have backups then download (here on xda or somewhere else) stock firmware and flash system und boot partition.
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Asish.pradhan said:
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Click to expand...
Click to collapse
Is it really not working? Or it just doesn't show the popup "TurboPower connected"?
does it work on XT1643 Indian variant ?
---------- Post added at 04:44 PM ---------- Previous post was at 04:40 PM ----------
Asish.pradhan said:
I am currently using the resurrection remix ROM on my moto g4 plus....and my turbo charging is not working...is there anything that I can do to fix this
Click to expand...
Click to collapse
Turbo Power worked fine in my device when using the Ressuruction Rom. Probably restarting the device would solve the issue.
I checked the power input using ampere..its working fine..thnks every1
disguisedview said:
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Code:
SYSTEMLESS=true
So the best is to make sure you don't use an older version of SuperSU than 2.79 SR3!
That's it and it works. SuperSU.apk is going to be installed in step 6.
Successfully tested with XT1642, XT1622 (eta82).
Click to expand...
Click to collapse
Does it work with XT1643 Indian variant ? Please do let me know .
arpith.pr said:
Here are the steps to root the Moto G4 (Plus) on Android 7.0 with SuperSU.
1. Unlock your bootloader with the Code you can receive from Motorola. Further instructions: unlocking bootloader. You have to create a Motorola account first.
2. Flash TWRP 3.0.2.0 through bootloader. Download and how-to-flash: twrp athene
3. Backup partitons in TWRP (especially the boot-partition)
4. Flash Kernel ElementalX through TWRP. Download and further information: ElementalX
5. Wipe Cache and ART-Cache through TWRP (don't know if necessary but doesn't harm)
6. Flash SuperSU v2.79 SR3 through TWRP. Download SR3-SuperSU-v2.79-SR3-20170114223742.zip: SuperSUv2.79SR3.
SuperSU v2.79 SR3 (or newer) will flash as systemless by default on Motorola devices running Android 6+. Older versions of SuperSU won't do that without creating a config file .supersu in /data containing the line
Does it work with XT1643 Indian variant ? Please do let me know .
Click to expand...
Click to collapse
Nobody confirmed it yet in this thread.
I could it only test with 1642.
But normally i would say it should also work on 1643 variant.
arpith.pr said:
Does it work with XT1643 Indian variant ? Please do let me know .
Click to expand...
Click to collapse
Yes it does work. It is the only way to root stock N on any of the models.
tywinlannister7 said:
Yes it does work. It is the only way to root stock N on any of the models.
Click to expand...
Click to collapse
Thanks
Working on XT1643....
Im making a video on how to do this to make it easier .... For others like me to understand
I can just Reboot to custom recovery, root and then still use my stock recovery?
Hi guys,
I bought the "new" Moto X Style last week for 250€(new, white, 32gb) and updated it to the highest Android 6.0 version from Motorola. After that, i flash the OTA-file from:
https://forum.xda-developers.com/moto-x-style/general/ota-moto-x-style-android-7-0-nougat-t3630248
After that, i unlock the bootloader, flash TRWP, clean the data and create a System backup:
https://xda.bioharz.xyz/2017-07-15--06-20-47_NPH25.200-15.7z
This is unmodified! and unrootedI actually have no time to create a System image, but this should also work for you.
I hope this can help you.
Thanks,
One question, this backup work in XT1572 CID12?
Necrodaemon said:
Thanks,
One question, this backup work in XT1572 CID12?
Click to expand...
Click to collapse
nope, only for the EU model
Netflix not working after installing
anth0nymDROID said:
Netflix not working after installing
Click to expand...
Click to collapse
Probably failing SafetyNet API check but what is the error?
Nougat will fail if the bootloader is unlocked and you don't have the Magisk module to stop SafetyNet. In Nougat an unlocked bootloader is enough to get it to fail even if otherwise 100% stock.
Netflix could also be confused as to your region if you restored the backup in this thread.
acejavelin said:
Probably failing SafetyNet API check but what is the error?
Nougat will fail if the bootloader is unlocked and you don't have the Magisk module to stop SafetyNet. In Nougat an unlocked bootloader is enough to get it to fail even if otherwise 100% stock.
Netflix could also be confused as to your region if you restored the backup in this thread.
Click to expand...
Click to collapse
Im reteu fr in Germany but if that's the case well no mobile Netflix I can still live my life without it.
anth0nymDROID said:
Im reteu fr in Germany but if that's the case well no mobile Netflix I can still live my life without it.
Click to expand...
Click to collapse
Magisk 13.3 can help with the safety net test. Here is how to install at stock: post #4
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
dzidexx said:
Magisk 13.3 can help with the safety net test. Here is how to install at stock: post #4
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Click to expand...
Click to collapse
That's good advice!! Thanks I'll try it later and see how it goes
What is the proper way to flash this backup using TWRP? I did a adb push to /sdcard with al files from the extracted .7z file but TWRP can't ze the backup.
What am I doing wrong?
xabr3 said:
What is the proper way to flash this backup using TWRP? I did a adb push to /sdcard with al files from the extracted .7z file but TWRP can't ze the backup.
What am I doing wrong?
Click to expand...
Click to collapse
Extract the backup zip file. Copy the last folder (containing the boot and system images) to your phone's TWRP Backup folder. Now you will see it in TWRP. Now perform a full backup. Then restore the copied-over nougat backup. Now you can pick on of the following two options.
1. f you have time, you do not need to delete your data before rebooting. You can always uninstall and reinstall any problem apps that show up after rebooting. That is what I did.
2. Of course, if you are in a hurry, you can delete your data and then reboot. That would be called a "clean install" and I don't do that very often.
Hope this helps.
@bioharz
Cheers for this. I was contemplating what method might be easiest for upgrading my rooted Moto X Style (EU) from MM 6.01 to Nougat 7.0. Ideally, this would have been a TWRP flashable ZIP, however, you have provided the second best option, which is a TWRP backup.
My method was as follows:
1) Make full TWRP backup of existing MM installation to extSD
2) Backup my Nova settings to extSD
3) Download, unzip and copy your backup to the TWRP location on extSD
4) Boot into TWRP and wipe Dalvik/ART, Cache, System and Data partitions via Advanced Wipe menu
5) Flash System and Boot partitions from your Nougat backup, BUT NOT EFS partition !!!
6) Reboot, log onto previous Google Account and restore all apps.
7) Restore Nova settings
8) Root with SuperSU (systemless) and SuHide
Worked a treat :good:
Are you sure - you need nougat with old radios?
You could reflash stock MM, update to Nougat, root, restore all you want. @Yemble
Will it work on moto x style Indian variant?
dzidexx said:
Are you sure - you need nougat with old radios?
You could reflash stock MM, update to Nougat, root, restore all you want. @Yemble
Click to expand...
Click to collapse
I am certain that I do not wish to screw up my phone with someone elses IMEI. Besides, what exactly is wrong with the MM radios? They are working perfectly on my phone.
Actually, given that I am now in a good position to experiment further, I have flashed the Nougat EFS partition on its own to my phone. Thankfully, it did not affect the IMEI or any network connectivity (SIM or WiFi). However, it has not changed the base band version either, so it may, in fact, be identical to the MM EFS anyway!
coolncoolest said:
Will it work on moto x style Indian variant?
Click to expand...
Click to collapse
Take a TWRP backup first, then give it a go. What have you got to lose?
I suggest that you try it without the EFS partition first. If that works, take another TWRP backup and then try flashing EFS on its own.
@coolncoolest @Yemble
Don't flash/restore EFS from another phone - you can lose your IMEI.
India - RetAsia version has the same baseband as RetEu - cid7.
Dual sim probably will not work.
dzidexx said:
@coolncoolest @Yemble
Don't flash/restore EFS from another phone - you can lose your IMEI.
India - RetAsia version has the same baseband as RetEu - cid7.
Dual sim probably will not work.
Click to expand...
Click to collapse
Clearly you are wrong about this (on this particular phone model), as I have already tried it and it proved that it did not break, or change, anything! I am aware that flashing EFS can be dangerous on older Samsung phones, hence my cautious approach that you appeared to be dissing in your previous post
I believe in hard facts, rather then hearsay. I have now upgraded three XT1572 (EU) phones from the posted TWRP image using the method that I outlined previously, together with the later flashing of the EFS partition. All three phones work perfectly and all three pass SafetyNet.
Someone else may be less fortunate than you and there is no reason to flash/restore efs.
Not only Samsung can lost imei in this way - Lenovo(+tablets), other Moto series, all Mtk devices(there is easy way to restore imei).
For Moto I don't know any restoring procedure. Sorry - one - mainboard replacement. @Yemble
dzidexx said:
Someone else may be less fortunate than you and there is no reason to flash/restore efs.
@Yemble
Click to expand...
Click to collapse
Really, then what was the point of your post at the top of this page?
Yemble said:
Really, then what was the point of your post at the top of this page?
Click to expand...
Click to collapse
Do you mean:
Nougat with old radios?
I meant:
Flash stock 6.0.1 24...58-5 with fastboot and get ota update.
Somewhere I uploaded my backup(6.0.1 EU) - without efs.