Thanks to GaBuzz for helping me install this update. If you think I need to add anything to the steps I listed, please let me know. I am just trying to help anyone having the same issue or wanting to update their unlocked bootloader Amazon phone.
Steps for anyone on a unlocked bootloader:
1. Make a nandroid backup with TWRP of the 48 or 49 firmware.
2. Backup your nandroid to you PC (http://www.howtogeek.com/240655/how-to-copy-twrp-android-backups-to-your-pc-for-safe-keeping/), but keep a copy on your SD card.
3. Download the MPJ24.139-64 Retail from XT1625-XT1644_ATHENE_RETUS_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (From https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/)
4. Extract the Firmware zip file and reboot your device into Bootloader mode.
5. Run RSD Lite Download Link: (http://forum.xda-developers.com/showthread.php?t=2637338) and look for the Servicefile.xml in the Firmware folder and install.
6.The G4 will boot into recovery and will not completely boot. Reboot back to bootloader mode and run Rootjunkie root script (http://rootjunkysdl.com/files/?dir=Moto G 4th Gen XT1625/Root Script). This will install TWRP and SuperSu. Once in TWRP go to Restore and look for the backup nandroid and uncheck everything except the boot file. You can also flash the boot file from the 49 firmware version to flash it.
7. Once the boot install is complete, you will be able to completely boot, still have your data and be on the latest July security update.
8.*** IMPORTANT *** I lost WiFi after installing Xposed and rebooting. Make sure you also do a Titanium Backup of all your apps, data and settings to restore. You may have to fresh install, use the boot from 49 version and restore with Titanium. As long as you have a Nandroid backup, you can restore and do a Titanium backup and do the fresh install.
Hope this helps anyone who is having problems updating. I use Nova Launcher, so its easy for me to restore my icons layout (just make sure you backup the files to your pc or sd card to restore later.
ugh!! I did the above but my nandroid somehow got corrupted. I cannot restore the boot file as mentioned in step 6. Is there any other way to get that boot file? Any way you can share it so that I can restore it?
I got it to boot my flashing the boot.img from -49, however, I get no WiFi and cannot turn WiFi on.
Sent from my Nexus 6P using Tapatalk
caifan said:
I got it to boot my flashing the boot.img from -49, however, I get no WiFi and cannot turn WiFi on.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I had the same issue. It was working, but I think when I installed Xposed thats when I lost WiFi after rebooting. My mac address changed to 02:00:00:00:00:00 and I could not solve it. I had to use Titanium Backup to backup all my apps, data and settings and use the Flashfile.xml (Deletes all data, just like a fresh install) to flash the 64 again. I then rooted and flashed the boot file to get past the bootloop to recovery and the WiFi is working. Going to restore with Titianium (Titianium needs Root & Busybox) and will let you know if it still works after that.
I am waiting for Titanium to restore all my apps, data and settings. As of right now is still restoring, but wifi is still working.
Danny1976 said:
I had the same issue. It was working, but I think when I installed Xposed thats when I lost WiFi after rebooting. My mac address changed to 02:00:00:00:00:00 and I could not solve it. I had to use Titanium Backup to backup all my apps, data and settings and use the Flashfile.xml (Deletes all data, just like a fresh install) to flash the 64 again. I then rooted and flashed the boot file to get past the bootloop to recovery and the WiFi is working. Going to restore with Titianium (Titianium needs Root & Busybox) and will let you know if it still works after that.
Click to expand...
Click to collapse
Which version of boot.img did you flash after the clean -64 update? I tried -48 and -49 and neither give me WiFi. I try to toggle it on and it just reverts.
caifan said:
Which version of boot.img did you flash after the clean -64 update? I tried -48 and -49 and neither give me WiFi. I try to toggle it on and it just reverts.
Click to expand...
Click to collapse
Here is the boot image I used, but I am using ElementalX kernel:
https://mega.nz/#!QtsDSbYb!rEQ32qUaUK3OB2IknJQ4-jMRAngsJvuGJA9EW45RIXw
If that doesn't fix it. Back up your stuff with titanium backup and flash the 64, then the boot file and restore with titanium.
I got it back to work by restoring my nandroid, update to 64, flash boot IMG, and restore some missing stuff with titanium backup. What caused my WiFi to not function was when I installed Xposed.
Yes! The boot.img you provided did the trick! Now on Amazon XT1625 unlocked, no ads, no bloat, rooted, WiFi working, and on the latest version -64.
Sent from my Nexus 6P using Tapatalk
caifan said:
Yes! The boot.img you provided did the trick! Now on Amazon XT1625 unlocked, no ads, no bloat, rooted, WiFi working, and on the latest version -64.
Click to expand...
Click to collapse
I am very happy for you. Glad it worked out. I have been figuring this out for days. I finally got it working. I hope the next update is not like this. Just make sure that now that is working, that you make a good nandroid backup. It saved me a lot of time.
I was using the elementalX kernel as well, so I'm guessing that it is needed to get everything working. Just as a note, after doing this update and updating the baseband most of the cm based ROMs are now working with it and no longer have the phone call bug.
GaBuzz said:
I was using the elementalX kernel as well, so I'm guessing that it is needed to get everything working. Just as a note, after doing this update and updating the baseband most of the cm based ROMs are now working with it and no longer have the phone call bug.
Click to expand...
Click to collapse
Is this the correct baseband for the CM Roms to work M8952_70009.08.03.45R? I notice the good thing about the CM Roms is that they have the latest Security Android Patches, which is very important. I am going to give OctoOS a try...Its suppose to some with Quake Kernel, but I am not sure if to keep ElementalX.
I tried OctoOS, but I like the moto apps that come in the stock version. I will stick with the moto stock rom and use ElementalX Kernel. It works very good.
Danny1976 said:
Thanks to GaBuzz for helping me install this update. If you think I need to add anything to the steps I listed, please let me know. I am just trying to help anyone having the same issue or wanting to update their unlocked bootloader Amazon phone.
Steps for anyone on a unlocked bootloader:
1. Make a nandroid backup with TWRP of the 48 or 49 firmware.
2. Backup your nandroid to you PC (http://www.howtogeek.com/240655/how-to-copy-twrp-android-backups-to-your-pc-for-safe-keeping/), but keep a copy on your SD card.
3. Download the MPJ24.139-64 Retail from XT1625-XT1644_ATHENE_RETUS_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (From https://mirrors.lolinet.com/firmware...fficial/RETUS/)
4. Extract the Firmware zip file and reboot your device into Bootloader mode.
5. Run RSD Lite Download Link: (http://forum.xda-developers.com/showthread.php?t=2637338) and look for the Servicefile.xml in the Firmware folder and install.
6.The G4 will boot into recovery and will not completely boot. Reboot back to bootloader mode and run Rootjunkie root script (http://rootjunkysdl.com/files/?dir=Moto G 4th Gen XT1625/Root Script). This will install TWRP and SuperSu. Once in TWRP go to Restore and look for the backup nandroid and uncheck everything except the boot file. You can also flash the boot file from the 49 firmware version to flash it.
7. Once the boot install is complete, you will be able to completely boot, still have your data and be on the latest July security update.
8.*** IMPORTANT *** I lost WiFi after installing Xposed and rebooting. Make sure you also do a Titanium Backup of all your apps, data and settings to restore. You may have to fresh install, use the boot from 49 version and restore with Titanium. As long as you have a Nandroid backup, you can restore and do a Titanium backup and do the fresh install.
Hope this helps anyone who is having problems updating. I use Nova Launcher, so its easy for me to restore my icons layout (just make sure you backup the files to your pc or sd card to restore later.
Click to expand...
Click to collapse
Soft-Bricked moto g4 Prime Exclusive XT1625
WE HAVE DETECTED AN ATTEMPT TO FLASH UNAUTHORIZED SW ON YOUR DEVICE.
Help! Please
He was installing the ROM ATHENE_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
:llorando::llorando::llorando:
AnderGuzmanD said:
Soft-Bricked moto g4 Prime Exclusive XT1625
WE HAVE DETECTED AN ATTEMPT TO FLASH UNAUTHORIZED SW ON YOUR DEVICE.
Help! Please
He was installing the ROM ATHENE_MPJ24.139-64_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
:llorando::llorando::llorando:
Click to expand...
Click to collapse
1. Reboot your Phone into the bootloader.
adb reboot-bootloader
2. Check if your device has been detected
adb devices
3. Flash boot.img
adb flash boot boot.img
Download link for boot.img
https://mega.nz/#!QtsDSbYb!rEQ32qUaUK3OB2IknJQ4-jMRAngsJvuGJA9EW45RIXw
Danny1976 said:
1. Reboot your Phone into the bootloader.
adb reboot-bootloader
2. Check if your device has been detected
adb devices
3. Flash boot.img
adb flash boot boot.img
Download link for boot.img
https://mega.nz/#!QtsDSbYb!rEQ32qUaUK3OB2IknJQ4-jMRAngsJvuGJA9EW45RIXw
Click to expand...
Click to collapse
friend gives you step the same? my phone is amazon prime, and have done everything possible to get out of that problem methods.
:crying::crying::crying:
---------- Post added at 02:49 PM ---------- Previous post was at 02:46 PM ----------
Danny1976 said:
1. Reboot your Phone into the bootloader.
adb reboot-bootloader
2. Check if your device has been detected
adb devices
3. Flash boot.img
adb flash boot boot.img
Download link for boot.img
https://mega.nz/#!QtsDSbYb!rEQ32qUaUK3OB2IknJQ4-jMRAngsJvuGJA9EW45RIXw
Click to expand...
Click to collapse
I have tried a hundred times to reinstall the operating system amazon,
ATHENE_AMZ_MPJ24.139-64_65_cid50_amz.tgz
but I still dating the same error. :crying::crying:
---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------
Danny1976 said:
1. Reboot your Phone into the bootloader.
adb reboot-bootloader
2. Check if your device has been detected
adb devices
3. Flash boot.img
adb flash boot boot.img
Download link for boot.img
https://mega.nz/#!QtsDSbYb!rEQ32qUaUK3OB2IknJQ4-jMRAngsJvuGJA9EW45RIXw
Click to expand...
Click to collapse
I have tried a hundred times to reinstall the operating system amazon,
ATHENE_AMZ_MPJ24.139-64_65_cid50_amz.tgz
but I still dating the same error. :crying::crying:
AnderGuzmanD said:
friend gives you step the same? my phone is amazon prime, and have done everything possible to get out of that problem methods.
:crying::crying::crying:
---------- Post added at 02:49 PM ---------- Previous post was at 02:46 PM ----------
I have tried a hundred times to reinstall the operating system amazon,
ATHENE_AMZ_MPJ24.139-64_65_cid50_amz.tgz
but I still dating the same error. :crying::crying:
---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------
I have tried a hundred times to reinstall the operating system amazon,
ATHENE_AMZ_MPJ24.139-64_65_cid50_amz.tgz
but I still dating the same error. :crying::crying:
Click to expand...
Click to collapse
No te estoy pidiendo que reinstales el systema operativo. Lo unico que necesitas hacer es solo instalar el boot.img sobre el viejo.
Danny1976 said:
No te estoy pidiendo que reinstales el systema operativo. Lo unico que necesitas hacer es solo instalar el boot.img sobre el viejo.
Click to expand...
Click to collapse
friend and I did and does nothing really
AnderGuzmanD said:
friend and I did and does nothing really
Click to expand...
Click to collapse
It says Retail at the top of the message. Is that the Amazon Prime version?
Danny1976 said:
It says Retail at the top of the message. Is that the Amazon Prime version?
Click to expand...
Click to collapse
that's what I'm trying to say a while friend is amazon prime xt1625
AnderGuzmanD said:
that's what I'm trying to say a while friend is amazon prime xt1625
Click to expand...
Click to collapse
Try this firmware:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Related
Hello everyone. I started this thread because I don't think I've seen anything with this issue on my specific phone on this forum. Apologies if this has been discussed before.
Anyway, I'm having issues installing a ROM with adb sideload on TWRP recovery.
I got the ROM and the recovery image from blox2.com (I would post the links but apparently the forum doesn't allow me to...)
Everything works fine, I'm able to boot into TWRP recovery and inititiate the adb sideload, but the process gets stuck when it reaches 28% and throws the error message:
serving: 'BLOX2core-v1.1.1-31217.zip' (~28%) * failed to read command: Success
Click to expand...
Click to collapse
In case this has anything to do with ADB version, I'm using Debian and my adb version is 1:7.0.0+r1-4
If you need any more info, please ask.
Thanks in advance.
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
max_157 said:
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
Click to expand...
Click to collapse
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
ieatgravity said:
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
Click to expand...
Click to collapse
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
I figured it out. I disabled MTP from the mount menu and disabled DM-Verify and encryption from the Advanced menu... same results
max_157 said:
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
Click to expand...
Click to collapse
Flash supersu then flash the ROM
ieatgravity said:
Flash supersu then flash the ROM
Click to expand...
Click to collapse
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
max_157 said:
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
Click to expand...
Click to collapse
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Where do you have the files located at? Is it on the SDcard or on the flash drive?
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
ieatgravity said:
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Click to expand...
Click to collapse
The bootloader was indeed unlocked.
I haven't tried flashing TWRP to the phone. Would this make it work? I'm kind of scared of having a recovery image that crashes whenever I try stuff. Can I restore the stock recovery in case anything happens?
AlienTeck said:
Where do you have the files located at? Is it on the SDcard or on the flash
drive?
Click to expand...
Click to collapse
Internal flash drive.
AlienTeck said:
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Click to expand...
Click to collapse
Yup! It works. It says it's already unlocked.
AlienTeck said:
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Click to expand...
Click to collapse
I did wipe cache and everything else, and had MTP disabled.
AlienTeck said:
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
Click to expand...
Click to collapse
64/4 BLU X2 version.
I can't find BLU Life One X2 on the official TWRP website, the only version I tried was on blox2.com, which I think is a modified version of 3.0.2-0.
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
QFIL
I got the QFIL rom from blox2.com
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
AlienTeck said:
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
Click to expand...
Click to collapse
I was able to flash the stock back, but via QFIL, not TWRP. The rebooting issue still persists.
I didn't make a nandroip backup, will get to it now.
Oh, I'm actually now trying to fix the rebooting issue. I think it might be a write protection, like the one HTC has. Example: https://www.youtube.com/watch?v=KV3YaMBnEYI
I really really need to be able to modify the system partition because the phone comes with a lot of crawpare and even some malware (https://www.cyberscoop.com/android-malware-china-huawei-zte-kryptowire-blu-products/)
FotaProvider installs some apps without your consent like Uber and some games and supposedly sends some info, too.
When I try to remove it with root uninstallers, the phone reboots. I though I had gotten rid of this issue by reflashing the ROM but apparently not...
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
AlienTeck said:
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
Click to expand...
Click to collapse
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
max_157 said:
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
Click to expand...
Click to collapse
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
ieatgravity said:
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
Click to expand...
Click to collapse
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
max_157 said:
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
Click to expand...
Click to collapse
We have a new tool that you can use to flash TWRP and root. All auto matic. Give it a try and let me know if it works for you.
[TOOL]Draco’s Blox2Autoroot - http://wp.me/p8gYUZ-5x
Afterwards you'll be able to flash Blox2core
Also I was unaware of this TWRP 3.0.3 for the blox2. The only one that has been ported has been 3.0.2 last I checked.
I would say disable MTP in TWRP options and developer options as well. dirst disabled it in developer options before I found out that did not stop the kernel rebooting the phone when /system became writable. I had not installed the oct update BLU sent out and maybe that makes a difference? Although the QFIL should also have the original boot/kernal image? so not sure what is going on..
If that dont stop it we need a new kernal.. I think I have the original kernal/boot saved. If anyone wants to see if that fixed the reboot.
twrp gave a MD5 of it..
152479bd51790d374885cc1a847e4c31 boot.emmc.win
Seems I need a faster course in android.. A few months ago I thought an android was some guy in dr who.
---------- Post added at 12:08 PM ---------- Previous post was at 11:46 AM ----------
The OTA update showed up one day and it installed it.. For the longest time I ignored it but I suppose someone hit ok on it.. But SuperSU seemed to have vanished before that I think. Spending time on 2 other problem phones so this one is not a priority since it works very well comparatively. I love it though it is heavy as a brick. Even my N5x case fits with a little coaxing. Although the DPI setting is set much higher like for a HD screen and not FHD. Maybe we can change it in build.prop to fix it. The N5x has much smaller icons and letters and actually fit 5 icons to a row although they both have the same density screen.. BLU has much better touch though and is far brighter and richer.
---------- Post added at 12:30 PM ---------- Previous post was at 12:08 PM ----------
The 2 boot images ARE different.. But you should first try to write a backup back to itself and see if there are problems and guess I dont have the previlage of attaching files just yet on here.
max_157 said:
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
I got the QFIL rom from blox2.com
Click to expand...
Click to collapse
Could you share the link to the stock ROM you used with QFIL?
Thanks!
Return to Un-modded Stock:
Bootloader unlocked and TWRP and Root included
The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download.
Be Advised
Do your research before flashing anything, I am not responsible for any damage caused to your device, due to impatience and missed steps. However, rest assured this recovery is solid and will absolutely return your X720 or X727 to stock 5.8.21s (with the bootloader already unlocked, TWRP installed and rooted)
I was asked by several people if I would be willing to share a link to my Stock X727 recovery, I created this thread to provide the 5.8.21s recovery for anyone who is experiencing dire issues or is simply wanting to restore the last official x727 recovery, as a daily driver or as a means to troubleshoot their issues by returning to the fully stock rom, stock partitions and ready to start over.
Attached is my full stock TWRP Recovery for my Le Eco Pro 3, version: 5.8.21s (X727)
It is a clean TWRP backup recovery that I did not mod in any way other than unlocking the bootloader.
The link is to my Google Drive account. https://drive.google.com/open?id=19dtLHmE5bsx5mdtEXOns4Z5drpeY79Em
The file is compressed
Ensure that you perform a full wipe before applying this recovery, and that you know what you are doing before attempting to install.
Please note that any changes that you make to your device is done at your own risk.
Please use caution and make sure that you have TWRP recovery installed.
Be in the habit of booting back to recovery before booting to system....This is a good practice for ensuring TWRP stays installed
You must unpack the downloaded 7zip file, before it will be useable.
As long as you can boot into TWRP and have root access you will have the full permissions needed to install anything , and reverse any actions that do not workout as planned.
Personally, I make a backup of my existing installation prior to making any changes. I recommend that you do the same. If you buy an OTG adapter and a USB 3.0 drive it takes 5 minutes.
The steps provided on the following link can be used to install my recovery file. https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
When clicking the link, Google will attempt to scan. Click download to see the file, and then choose download if wanted.
Flash the appropriate files below for which ever device you own. ( X727 - Not needed, I provided the files anyway just in case.)
Firmware - X720
https://mega.nz/#F!kDgFQJ6R!MDhxCFw5KjfB0CfxAWwr9w
Firmware - X727
https://drive.google.com/open?id=136-4UpUUsj3exNsTc3d5n2iQuYUxr00H
Modems
X720: https://mega.nz/#F!pZ4WGARZ
Key : !2oG3Z2LS_wP8BzcWUQjfHg
X727: https://mega.nz/#F!NJ5VHS7Z
Key : !p0iO7bDiZ4kXny03EiAlWw
Build Prop Fix Device ID Tool ( Credit to @Ascertion )
https://mega.nz/#F!oAZ3yC4b
Key: !MDwbHXNTRdrpgMvQ42yviw
EFS:
Warning : Use this only if you have unrepairable IMEI Issues! Otherwise its not needed, and you could forever lose your original IMEI info.
https://drive.google.com/open?id=10n2VjwBYHmrq_PllcWmTaGUtMIeYynZ7
[B ]Just for Fun[/B] - Boot Screens and Boot Animations -
https://mega.nz/#F!JB51zbwR
Key: !sG_wXTPqyKpugg5QIZFo9w
These splash-screens and animations came from various sources. If you created them contact me so i can give you credit.
The Red Splash came from the Couco modified EUI : version 5.9.028s VR4
Other Helpful Hints and Tips More to Come!
Unlock Bootloader and Flash Roms, Gapps and Magisk https://forum.xda-developers.com/showpost.php?p=75009966&postcount=692 ( If using original Stock
Viper Settings : https://forum.xda-developers.com/showpost.php?p=75449097
Installing Viper and Dolby: https://forum.xda-developers.com/showpost.php?p=76362493&postcount=19
Edit
October 8, 2018:
I uploaded the Leeco Full Stock Rom 5.8.26s to my MegaDrive.
If you are selling your phone and want it to have stock without TWRP and without root , just flash this Rom and your stock radio driver "firmware" for your device
Link for EUI 21S : https://mega.nz/#!FRhh1ArL
Key: V5ua3oj91kFtgvLYBhl1X6Oq3bsScyDFruN3UptkWN0
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Soul0Reaper said:
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Click to expand...
Click to collapse
Thats Awesome! I am glad that it helped you.
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
dunas2331 said:
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
Click to expand...
Click to collapse
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
tsongming said:
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
Click to expand...
Click to collapse
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Hi tsongming, you know if can work on a x720?
thanks
Toni Moon said:
Hi tsongming, you know if can work on a x720?
thanks
Click to expand...
Click to collapse
Yes x720 and x727 are practically identical phones.
Sent from my LEX720 using XDA Labs
Scruffdog1978 said:
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Click to expand...
Click to collapse
I don't have time at the moment to provide lengthy instructions. With respect, I am providing a working, clean unlocked recovery file and pointing the way to instructions already that exist all throughout the LeEco forums.
But here's a quick answer
First use TWRP to reset your phone with a clean wipe, like you would for any ROM. Set developer options to the standard settings.
Next, your storage is encrypted. So it needs to be formatted. Use TWRP format the storage only. Then reboot to recovery.
****Important****
Don't ever format the storage without ensuring that you have a TWRP recovery. Always check the boxes to check if TWRP is installed before swiping. If you don't have a recovery you have a soft brick.
For you information, TWRP recovery is installed on it's on it very own partition. Formatting the storage does not affect the TWRP partition. Nonetheless, if you see the check box option, make sure they are checked.
I would suggest that you install the all in one tool : https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
This tool helps a lot and makes this stuff easier if are new to flashing custom Roms.. The all in one tool will update the Google driver and ADB installation on your computer.
After you format your drive you will have to flash the recovery from the PC. The links provided show all of the steps, or you can use the all for one tool. When your storage is encrypted you have no choice but to format.
If you use the all in one tool , see their page for instructions.
Read the instructions, then read them again. when learning something new it's a good idea to take notes.
Do not deviate from those steps or you could brick your phone.
There have been many people that have messaged me by PM who successfully returned to stock using my recovery, so it will work as long as you are careful and follow the instructions verbatim and you will be fine. Plus, It's a great idea to create your own working recovery before you begin.
Reminder, you are restoring to stock under you own discretion, I am not responsible if you miss a key step, have a power outage, use faulty cables or brick your device.
One final suggestion, when you install the recovery make sure your phone is fully charged. Unplug all unneeded external peripherals from your desktop computer.
Temporarily, disable antivirus, insert USB cable into the back of your desktop PC. Those outlets provide more power.
Please look past any typos, I typed this on little keys.
One last suggestion
Read this
http://www.androidtipsz.com/top-5-things-to-do-before-installing-a-custom-rom-on-your-android-device
Sent from my LEX720 using XDA Labs
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
meh4life321 said:
Will I keep twrp after restore? Thanks
Click to expand...
Click to collapse
Also, could I just restore the system?
Could I just flash this in TWRP and keep twrp as my recovery?
meh4life321 said:
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
Also, could I just restore the system?
Click to expand...
Click to collapse
No it will not keep twrp. follow the instructions in the link I provided above, there was no reason to duplicate the instructions on my post.
The difference is that my backup will restore your phone to Eui 5.8.21s with bootloader unlocked. You will need to reflash Twrp and root the phone with Magisk if you want to keep Twrp recovery ( that is what I would do) You will not be able to get OTA updates. But that doesn't matter because there probably not be any more OTA updates for the x727
Thank you, sir! This is great work. I was able to restore back to stock.
On the strange side of thing, my TWRP was saved. Previously, I was running AICP, but having multiple sound issues with it.
Here are the steps I followed to restore:
1) Move the file to OTG flash drive
2) Restore through TWRP via Restore
For my 727, it just reboot on logo, and doesn't go past it.
rob_z11 said:
For my 727, it just reboot on logo, and doesn't go past it.
Click to expand...
Click to collapse
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
tsongming said:
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
Click to expand...
Click to collapse
Will try again. How long is while? ?
rob_z11 said:
Will try again. How long is while?
Click to expand...
Click to collapse
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
tsongming said:
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
Click to expand...
Click to collapse
It actually worked for second time without any issues. Just can't get the root, but will follow your instructions.
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
blanktape said:
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
Click to expand...
Click to collapse
This recovery is stock EUI 5.8.21s. The exception is that the bootloader is unlocked, and it has TWRP Recovery instead of EUI Recovery. I do not remember which version of Magisk I Installed. I would advise that you flash the newest version of Magisk and you will not have any safety net issues.
If you are wanting a complete return to stock, you should instead reflash the stock Full Rom, which will reinstall EUI recovery and lockdown the bootloader.
*** OUTDATED, WORK HAS NOW PROGRESSED TO POISON ROM, https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720 ***
Features
Removed Bloatware apps such as Twitter, Team Viewer etc.
Removed Dummy Play Store App
Removed Outdated versions of apps and replaced them with latest versions as of time of writing, like Playstore, Firefox, Kodi etc.
Used a Custom Launcher (Created by Ricky Divjakovski) to give device a fresh look.
Enter Key now works on External Keyboards
Known Bugs:
Play Store shortcut on Launcher does not work, Can open Playstore through Setting/Apps. ***Fixed***
Enter key on External Keyboard doesn't work. ***Fixed***
Navigation Bar does not come back if minimised without a reboot.
When you go to Settings/About/Status sometimes has an error and doesn't open, opens on second attempt though.
Any other bugs feel free to report.
***IMPORTANT ***
You need to be on Stock 7.1.2 Firmware before flashing the Custom Rom. So I recommend you make a backup of your existing Firmware if for any reason you want to go back to your Existing Firmware and setup. To make a backup, you need to get Custom Recovery (TWRP) installed, you need to install the right version of TWRP depending on your existing firmware. Download your existing Firmware Custom Recovery files from below.
TWRP FILES
If on Firmware 6.0.1 from here
If on Firmware 7.1.1 from here
If on Firmware 7.1.2 from here
INSTALLING CUSTOM RECOVERY
METHOD 1:
Download Ricky's Amlogic Flash Tool from AmlogicFlashTool.zip and follow the instructions from his thread over at https://forum.xda-developers.com/an...c/amlogic-devices-amlogic-flash-tool-t3745640.
METHOD 2:
1. Download ADB from here and install it on your pc, then open a command prompt (Windows 10 hold Shift and press Right Mouse button, will take you to Power Shell) in the directory of the custom recovery
2. Enable USB debugging, go to settings>about and click build number about 10 times, then go back to the main settings menu and you will see developer options, enter it and check allow USB debugging.
3. Connect to your device via IP address. go to settings>about>status and get your IP address. it should be something like 192.168.25.19
4. In CMD type the following commands, replace YOURIPADDRESS with the address we got from step 3
Code:
adb connect YOURIPADDRESS
adb push custom-recovery.img /sdcard/
adb shell su -c dd if=/sdcard/custom-recovery.img of=/dev/block/recovery
adb reboot recovery
TWRP BACKUP
Now go ahead and make a backup of your existing setup before proceeding any further. I recommend putting the backup onto a usb drive.
Step:
1. Go to Backup
2.If desired name your backup on name setting up top left hand corner, not necessary but can do if you like.
3. Select Storage: USB or SDCard depending on which one you are going to use. Click OK.
3. Swipe to Backup
4. Let it do it's thing, When finished remove usb/sd card and reboot to system.
5. Recommend putting a copy of your backup from your usb or sd card to your PC as well.
FLASHING 7.1.2 STOCK FIRMWARE
You need to download the Stock 7.1.2 firmware from here
Use the provided USB Burning tool to flash the firmware if you have a USB Male to Male cable. Video of how to here
Now 7.1.2 Stock is installed, you now have to flash the Custom Recovery (TWRP) for 7.1.2, follow the instructions earlier to install Custom Recovery with the 7.1.2 file.
CUSTOM ROM
NOTE: Remember to make sure you have a backup of your old existing firmware before flashing this custom rom
Instructions:
1. Download the 3/32GB T95Z Custom Rom 7.1.2.zip from here
and put it on a usb stick.
2. Reboot into recovery
3. Wipe Cache, System and Data
4. Go back to the main menu and select install, then choose the 3/32GB T95Z Custom Rom 7.1.2.zip and swipe to install!
Reboot and enjoy!
Please give 5 to 10 minutes on first reboot after flash.
Contributors
Ricky Divjakovski, whiteak
ROM OS Version: 7.x Nougat
Credits:
Magendanz (TWRP)
Snoop05 (Adb)
Version Information
Status: Testing
Great job! A whole range of ROMS for Amlogic devices is about to unveil once i release the rom skeletop package!
Hi on my device when i reboot to recovery after put TWRP by adb it's stuck on T95z plus logo... Any idea ?
after unplug the power cable and plug it again the box start, but i can't start in recovery by the adb... can u give me some help ?
Thanks by advance.
---------- Post added at 11:36 AM ---------- Previous post was at 11:31 AM ----------
I do that and i don't see any error..
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb connect 192.168.1.100
connected to 192.168.1.100:5555
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb push custom-recovery.img /sdcard/
custom-recovery.img: 1 file pushed. 6.6 MB/s (13793280 bytes in 1.986s)
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb shell su -c dd if=/sdcard/custom-recovery.img of=/dev/block/recovery
26940+0 records in
26940+0 records out
13793280 bytes transferred in 2.774 secs (4972343 bytes/sec)
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb reboot recovery
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>
Is your box 2/16gb or 3/32gb, you may be flashing the wrong TWRP.
whiteak said:
Is your box 2/16gb or 3/32gb, you may be flashing the wrong TWRP.
Click to expand...
Click to collapse
32Gb box and i take the twrp from your thread.
papla83 said:
32Gb box and i take the twrp from your thread.
Click to expand...
Click to collapse
Try this TWRP here
It's a earlier version, but I ported this one myself. It's the one I used until I found a newer version.
whiteak said:
Try this TWRP here
It's a earlier version, but I ported this one myself. It's the one I used until I found a newer version.
Click to expand...
Click to collapse
Same result, hang on t95Zplus logo and doesn't move....
papla83 said:
Same result, hang on t95Zplus logo and doesn't move....
Click to expand...
Click to collapse
And you definitely have a 3/32gb box, I don't know what could be the problem. I had the exact same problem, but it was because I was using the 2/16 version on my 3/32 box. You don't have any usb sticks plugged into the box either? if you do try pulling them out when flashing.
whiteak said:
And you definitely have a 3/32gb box, I don't know what could be the problem. I had the exact same problem, but it was because I was using the 2/16 version on my 3/32 box. You don't have any usb sticks plugged into the box either? if you do try pulling them out when flashing.
Click to expand...
Click to collapse
yes i have, i will try whitout sd card and usb stick and make a feedback
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
same result
can i brick my box if i flash it with the 16Gb model ? because maybe i can try with no risk ( the recovery doesn't start anyway )
Worst case is it should only do the same thing, I was pushing the 16gb model on my box a fair few times and all it did hang at the T95Z Plus logo.
whiteak said:
Worst case is it should only do the same thing, I was pushing the 16gb model on my box a fair few times and all it did hang at the T95Z Plus logo.
Click to expand...
Click to collapse
When i try to send twrp 16gb version to my box i have an error message failed to send file ( i use the amlogic adb tool by Ricky Divjakovski )...
papla83 said:
yes i have, i will try whitout sd card and usb stick and make a feedback
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
same result
can i brick my box if i flash it with the 16Gb model ? because maybe i can try with no risk ( the recovery doesn't start anyway )
Click to expand...
Click to collapse
By personal experience your best bet is to re flash the original rom with the usb flashing tool.
Once it is done you can try flashing different TWRP until you find one that work. Installing TWRP from the store just does not work on those device.
Installing SU also soft brick your device and normal recovery do not work.
Also to flash using to USB burning tool make sure you use the OTG USB port on your device (usually port no, 1).
whiteak said:
Known Bugs:
Play Store shortcut on Launcher does not work, Can open Playstore through Setting/Apps.
Navigation Bar does not come back if minimised without a reboot.
When you go to Settings/About/Status sometimes has an error and doesn't open, opens on second attempt though.
Any other bugs feel free to report.
Click to expand...
Click to collapse
I got play store to work on my original rom from the launcher after disabling it in the app settings, and replacing system/app/GoogleStore folder by the one from SuperCeleron 3/32g custom rom ans installing it from the apk. Might be worth a look to get it working on your rom.
Funny thing is that I tried to install SuperCeleron Rom on my machine but it brick it every time.
Also on initial setup after you have an option to give root acces or not and also to enables init.d support, I just can't remember where it was in the Droid settings on the launcher or the most advance settings in the apps folder. I will have to go thru all the settings to find them.
I tried your ROM but it disabled my Play Store in the launcher and in the apps and did not let me reinstall it for some reason. I had to go thru TotalCommander to be able to launch it. Since I did not want to fool around to restore it. I just flashed back my Rom.
I can live with the way my device perform right now has the most important part for me was Kodi.
Stuck at logo as well
I got everything to go just fine: ADB went smooth, TWRP running just fine, successful flash from microSD card, wiped cache, rebooted and waited 15 minutes and I'm just stuck at the logo
I even pulled AC and ejected the card and then plugged it in let it sit for 20 minutes and nothing but the logo still.
I'm 101% sure I'm have a 3G+32Gb T95z Plus (AP6225 WLAN)
LeMaestro said:
I got play store to work on my original rom from the launcher after disabling it in the app settings, and replacing system/app/GoogleStore folder by the one from SuperCeleron 3/32g custom rom ans installing it from the apk. Might be worth a look to get it working on your rom.
Funny thing is that I tried to install SuperCeleron Rom on my machine but it brick it every time.
Also on initial setup after you have an option to give root acces or not and also to enables init.d support, I just can't remember where it was in the Droid settings on the launcher or the most advance settings in the apps folder. I will have to go thru all the settings to find them.
I tried your ROM but it disabled my Play Store in the launcher and in the apps and did not let me reinstall it for some reason. I had to go thru TotalCommander to be able to launch it. Since I did not want to fool around to restore it. I just flashed back my Rom.
I can live with the way my device perform right now has the most important part for me was Kodi.
Click to expand...
Click to collapse
I want just have the best experience with this box, the box ,at this time and with this rom works, but i feel the works doesn't finish and i think we have a huge possibility with a finalised and optimised rom.
---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------
Semper 5 said:
I got everything to go just fine: ADB went smooth, TWRP running just fine, successful flash from microSD card, wiped cache, rebooted and waited 15 minutes and I'm just stuck at the logo
I even pulled AC and ejected the card and then plugged it in let it sit for 20 minutes and nothing but the logo still.
I'm 101% sure I'm have a 3G+32Gb T95z Plus (AP6225 WLAN)
Click to expand...
Click to collapse
Hi. sorry for the dumb question but do you wipe to the factory data too or only wipe cache ?
papla83 said:
Hi. sorry for the dumb question but do you wipe to the factory data too or only wipe cache ?
Click to expand...
Click to collapse
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Semper 5 said:
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Click to expand...
Click to collapse
Take a look here maybe you will find what you need.
https://forum.xda-developers.com/an...95z-plus-one-thread-files-recoveries-t3737040
I used the custom recovery for the 3/32Gb variant and it worked perfect, now I have a working TWRP.
papla83 said:
I want just have the best experience with this box, the box ,at this time and with this rom works, but i feel the works doesn't finish and i think we have a huge possibility with a finalised and optimised rom.
Click to expand...
Click to collapse
Me to I would like to have a few thing added or fixed in the launcher, but those guys just started to work on this a few days ago, so let give them time to make it better. I screw up my box enough in the last week so let be patient.
Semper 5 said:
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Click to expand...
Click to collapse
TWRP link updated, not sure why it unlinked but anyway should be good to download again.
LeMaestro said:
Take a look here maybe you will find what you need.
https://forum.xda-developers.com/an...95z-plus-one-thread-files-recoveries-t3737040
I used the custom recovery for the 3/32Gb variant and it worked perfect, now I have a working TWRP.
Me to I would like to have a few thing added or fixed in the launcher, but those guys just started to work on this a few days ago, so let give them time to make it better. I screw up my box enough in the last week so let be patient.
Click to expand...
Click to collapse
That link in the other thread links to my mega folder, can I ask which custom recovery you used the 3.1.1-0 or the 3.0.2, both should work, but just curious. Also so you did manage to flash my custom zip successfully and it did boot up? Not sure why people are having problems.
This is just my guide for updating. i wrote it down because i tend to forget how i did things when i want to do it again.
i am no expert. there could be better ways to do it.
Update after twrp
This includes a factory reset.
Root, TWRP and all your DATA is gone after this.
Do a backup before you do this!!!
1.
Activate usb debugging
Power off the phone completely.
Press and hold the Volume Up and Power button to enter Fastboot mode.
2. fastboot flash recovery stockrecovery.img
3. boot into recovery (volume down+power)
install from SD: UL-ASUS_Z01KD_1-WW-14.1064.1711.96-user.zip
4. start system.
Factory reset
than shut down.
5. boot into recovery (volume down+power)
install from SD: latest update
You could share the file link to flash user.zip?
matracapx said:
You could share the file link to flash user.zip?
Click to expand...
Click to collapse
What do you mean? The firmware? You can download it from the Asus website.
Does anyone know the current procedure for updating the ROM stock via TWRP. It looks like we should download the full updated firmware and the Magisk. Restart on TWRP, and flash the ROM and then the Magisk, one by one. Can anyone confirm?
-------------------------------------------------------------------------------------------------------------------------------------------------------
Alguém sabe o procedimento atual para atualizar a stock ROm via TWRP. Parece que devemos baixar o firmware atualizado completo e o Magisk. Reiniciar na TWRP, e flashear a ROM atulizada e depois o Magisk, um por um. Alguém pode confirmar?
Following...
badvag said:
Does anyone know the current procedure for updating the ROM stock via TWRP. It looks like we should download the full updated firmware and the Magisk. Restart on TWRP, and flash the ROM and then the Magisk, one by one. Can anyone confirm?
-------------------------------------------------------------------------------------------------------------------------------------------------------
Alguém sabe o procedimento atual para atualizar a stock ROm via TWRP. Parece que devemos baixar o firmware atualizado completo e o Magisk. Reiniciar na TWRP, e flashear a ROM atulizada e depois o Magisk, um por um. Alguém pode confirmar?
Click to expand...
Click to collapse
You just answered your own question. That's how it's always been done, doesn't matter whether you got a ASUS Zenphone or a Galaxy S phone from Samsung for that matter.
urbanman2004 said:
You just answered your own question. That's how it's always been done, doesn't matter whether you got a ASUS Zenphone or a Galaxy S phone from Samsung for that matter.
Click to expand...
Click to collapse
I do not know the procedure for updating the ROM by TWRP, do you know? Can you tell me more details?
I want to say that in the normal way I know how to do it, but I'm still not sure how to update the ROM via TWRP without losing Magisk and Xoosed (if you're using it)
badvag said:
I do not know the procedure for updating the ROM by TWRP, do you know? Can you tell me more details?
I want to say that in the normal way I know how to do it, but I'm still not sure how to update the ROM via TWRP without losing Magisk and Xoosed (if you're using it)
Click to expand...
Click to collapse
I use Magisk, but not Xposed. These instructions are based on the assumption that the bootloader is unlocked, and that TWRP is already installed on your device, and that the Rom in question has already been copied to a USB Stick via OTG cable:
01. Boot into Recovery Mode (hold down Volume Down + Power Buttons)
02. Always make a [Nandroid] backup (via USB-OTG, saving data on USB Stick preferably) when going from one Rom to another; Save separate important data (texts, call logs, documents)/apps prior to Rom Install using backup utility apps, e.g., Titanium Backup.
03. Sideload your Rom (via USB-OTG, copied onto USB Stick preferably)
04. Hit WIPE – Do a Factory Reset: Wipe Data /Cache/ Dalvik. Hit Back
05. Hit MOUNT – Mount USB-OTG. Select the storage device. Hit Back
06. Hit INSTALL – Browse for the Rom (zip file). Install Rom
07. Remember to Flash Google Apps
08. REBOOT the System
09. Complete the startup wizard and give the phone a 10 to 15 minutes before the next step.
10. Now reboot into Recovery and flash any mods/theme or kernel compatible with your new ROM.
a. Remember to 'wipe cache/dalvik' after flashing kernel
urbanman2004 said:
I use Magisk, but not Xposed. These instructions are based on the assumption that the bootloader is unlocked, and that TWRP is already installed on your device, and that the Rom in question has already been copied to a USB Stick via OTG cable:
01. Boot into Recovery Mode (hold down Volume Down + Power Buttons)
02. Always make a [Nandroid] backup (via USB-OTG, saving data on USB Stick preferably) when going from one Rom to another; Save separate important data (texts, call logs, documents)/apps prior to Rom Install using backup utility apps, e.g., Titanium Backup.
03. Sideload your Rom (via USB-OTG, copied onto USB Stick preferably)
04. Hit WIPE – Do a Factory Reset: Wipe Data /Cache/ Dalvik. Hit Back
05. Hit MOUNT – Mount USB-OTG. Select the storage device. Hit Back
06. Hit INSTALL – Browse for the Rom (zip file). Install Rom
07. Remember to Flash Google Apps
08. REBOOT the System
09. Complete the startup wizard and give the phone a 10 to 15 minutes before the next step.
10. Now reboot into Recovery and flash any mods/theme or kernel compatible with your new ROM.
a. Remember to 'wipe cache/dalvik' after flashing kernel
Click to expand...
Click to collapse
That way I would lose the Magisk, XPosed and phone settings. When flashing the original ROM, it will overwrite custom recovery (TWRP). I would like to know a way to update the original ROM without losing anything, understand? It is possible?
badvag said:
That way I would lose the Magisk, XPosed and phone settings. When flashing the original ROM, it will overwrite custom recovery (TWRP). I would like to know a way to update the original ROM without losing anything, understand? It is possible?
Click to expand...
Click to collapse
Did you not just read what I took the time to write? If not, you're on your own
urbanman2004 said:
Did you not just read what I took the time to write? If not, you're on your own
Click to expand...
Click to collapse
I read, I should not have understood. Does the procedure you passed do not lose the settings and root (Magisk)?
badvag said:
That way I would lose the Magisk, XPosed and phone settings. When flashing the original ROM, it will overwrite custom recovery (TWRP). I would like to know a way to update the original ROM without losing anything, understand? It is possible?
Click to expand...
Click to collapse
badvag said:
I read, I should not have understood. Does the procedure you passed do not lose the settings and root (Magisk)?
Click to expand...
Click to collapse
I can tell English is not your native language. If you notice under instruction #2:
Always make a [Nandroid] backup (via USB-OTG, saving data on USB Stick preferably) when going from one Rom to another; Save separate important data (texts, call logs, documents)/apps prior to Rom Install using backup utility apps, e.g., Titanium Backup.
Click to expand...
Click to collapse
That implies that your settings will not be saved, and refers you to other means to backup/restore them; a) creating a Nandroid backup within TWRP will backup the OS/Rom (and installed apk's) but no settings, data, files, etc., b) Titanium Backup does a number of things, if not all of what you inquired a/b. I would highly implore you do your research and due diligence before plunging into something blindly that you're not well-versed in which seems to be the case here. Just b/c I mentioned here what is it that I would do in your situation doesn't mean it works best based on your use case scenario. Hope that provides you more, and better clarity.
urbanman2004 said:
I can tell English is not your native language. If you notice under instruction #2:
That implies that your settings will not be saved, and refers you to other means to backup/restore them; a) creating a Nandroid backup within TWRP will backup the OS/Rom (and installed apk's) but no settings, data, files, etc., b) Titanium Backup does a number of things, if not all of what you inquired a/b. I would highly implore you do your research and due diligence before plunging into something blindly that you're not well-versed in which seems to be the case here. Just b/c I mentioned here what is it that I would do in your situation doesn't mean it works best based on your use case scenario. Hope that provides you more, and better clarity.
Click to expand...
Click to collapse
Of course, English is not my native language.
But I had read, I really did not have much practice in doing this by Titanium backup and recovering these settings. My initial question was: Is there any way to flash the updated ROM without losing anything? I realized that there isn't.
how can i find stockrecovery.img ?
euojunior said:
how can i find stockrecovery.img ?
Click to expand...
Click to collapse
i added stock recovery to the first post
https://forum.xda-developers.com/attachment.php?attachmentid=4694253&d=1548542582
joeblond999 said:
i added stock recovery to the first post
https://forum.xda-developers.com/attachment.php?attachmentid=4694253&d=1548542582
Click to expand...
Click to collapse
Thanx Guy God Bless U !!
Thank you ! all happened normally here God bless you !
I'm coming back here to explain how to update the ROM stock using TWRP and the Asus Flash Tool.
Some guys who are experts say it does not work, but there are videos on Youtube showing that it is possible to do the firmware flash directly through TWRP, I did not do it because of the risk of the softbrick.
These are the videos:
https://www.youtube.com/watch?v=HebmIzuAfS0&t=194s
https://www.youtube.com/watch?v=thEDEvA5UUs
https://www.youtube.com/watch?v=nzBQz1x4xfg
It may also be possible for "adb sideload xxxx" in the sideload option of TWRP (use TWRP version 3.2.3, which is hard to find on the internet), I have not tested it.
In my procedure the TWRP will be lost:
1) Download RAW firmware ZE554KL
2) Install ASUS Flash Tool (in version v2.0.1 does not seem to work), I used version v1.0.0.45.
3) Now, with your phone turned on and your debug mode enabled.
4) Open ASUS Flash Tool ((it does not matter if the model of the device is not listed)
5) Select the RAW firmware you've downloaded.
6) Click on the Serial Number of your device.
7) Click Start. I do not remember, but I think now the phone starts with TWRP or you start custom recovery and then put it in FASTBOOT mode (if you do this before Asus FlashTool will not recognize the device).
8)Start the process on the start button (I can not remember if it has to start again), and then the RAW firmware will start to be copied. The phone will reboot again through TWRP, do nothing until the process is finished (check for TWRP and Asus Flash Tool), then just start the device. Recovery will be back to normal and the device will have the firmware updated.
*I could not attach twrp3.2.3 and Asus Flash Tool (v1.0.0.45) because of the size of the files.
badvag said:
I'm coming back here to explain how to update the ROM stock using TWRP and the Asus Flash Tool.
Some guys who are experts say it does not work, but there are videos on Youtube showing that it is possible to do the firmware flash directly through TWRP, I did not do it because of the risk of the softbrick.
These are the videos:
https://www.youtube.com/watch?v=HebmIzuAfS0&t=194s
https://www.youtube.com/watch?v=thEDEvA5UUs
https://www.youtube.com/watch?v=nzBQz1x4xfg
It may also be possible for "adb sideload xxxx" in the sideload option of TWRP (use TWRP version 3.2.3, which is hard to find on the internet), I have not tested it.
In my procedure the TWRP will be lost:
1) Download RAW firmware ZE554KL
2) Install ASUS Flash Tool (in version v2.0.1 does not seem to work), I used version v1.0.0.45.
3) Now, with your phone turned on and your debug mode enabled.
4) Open ASUS Flash Tool ((it does not matter if the model of the device is not listed)
5) Select the RAW firmware you've downloaded.
6) Click on the Serial Number of your device.
7) Click Start. I do not remember, but I think now the phone starts with TWRP or you start custom recovery and then put it in FASTBOOT mode (if you do this before Asus FlashTool will not recognize the device).
8)Start the process on the start button (I can not remember if it has to start again), and then the RAW firmware will start to be copied. The phone will reboot again through TWRP, do nothing until the process is finished (check for TWRP and Asus Flash Tool), then just start the device. Recovery will be back to normal and the device will have the firmware updated.
*I could not attach twrp3.2.3 and Asus Flash Tool (v1.0.0.45) because of the size of the files.
Click to expand...
Click to collapse
Please upload files to google drive? thank you!
matracapx said:
Please upload files to google drive? thank you!
Click to expand...
Click to collapse
Link: https://drive.google.com/open?id=1s6O3RMVqNe3K-mFzzo2k5vFZByABi0YF
*Reminder: you can recover the original recovery easily. The stock recovery file is also on the link.
Hey!
A few months ago I rooted my Mate 10 Pro (UK version on Three) using that all-in-one tool. It installed TWRP and Magisk.
I've been having a pending OTA update for months and it fails when trying to install rebooting onto TWRP.
Is there a safe way to go back to stock recovery, let the phone update and then root back? (without wiping the whole thing?) If so, could you please guide me giving some very specific steps? Many thanks!
Use hrupdater 0.4 and twrp, but read well how to do it, if you are on a xloader2 version, you can't install xloader1 version. First read well all threads you can and then if you know what are you doing, update and root again. If you only want to update and you don't mind about root, install the stock recovery and unroot and update via OTA.
Huawei is a diificult smartphone for rooting in my view, be carefull and do all by your own risk, there are many people that have bricked this smartphone due to the lack of knowledge of what they were doing (and others due to bad luck of the downgrade of xloader)
My question is how can you flash to the lastest OTA EMUI 9.0 if twrp doesn't support emui 9.0.
durc12 said:
Use hrupdater 0.4 and twrp, but read well how to do it, if you are on a xloader2 version, you can't install xloader1 version. First read well all threads you can and then if you know what are you doing, update and root again. If you only want to update and you don't mind about root, install the stock recovery and unroot and update via OTA.
Huawei is a diificult smartphone for rooting in my view, be carefull and do all by your own risk, there are many people that have bricked this smartphone due to the lack of knowledge of what they were doing (and others due to bad luck of the downgrade of xloader)
Click to expand...
Click to collapse
I just wanted to continue to expand on this. All the info I gathered is pulled from the link below.
Xloader checker
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you are rooted can also dump your own xloader if you want to see what you're currently on.
Download Terminal Emulator from the play store and open it
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
hungrymr2 said:
I just wanted to continue to expand on this. All the info I gathered is pulled from the link below.
Xloader checker
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you are rooted can also dump your own xloader if you want to see what you're currently on.
Download Terminal Emulator from the play store and open it
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
Click to expand...
Click to collapse
Thank you so much for taking the time to help me out. However, I clicked on that link and I don't understand anything!
My goal is to install the update and keep my phone rooted (a must!). So I downloaded terminal emulator and followed your instructions, now I have an "xloader.img" on my SD card and I don't know what to use to open it or do next. Please have some patience and help me out?
93starletgt said:
Thank you so much for taking the time to help me out. However, I clicked on that link and I don't understand anything!
My goal is to install the update and keep my phone rooted (a must!). So I downloaded terminal emulator and followed your instructions, now I have an "xloader.img" on my SD card and I don't know what to use to open it or do next. Please have some patience and help me out?
Click to expand...
Click to collapse
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
hungrymr2 said:
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
Click to expand...
Click to collapse
I just did an OTA update with HiSuite 9.0.2.304, it was ridiculously easy. I simply clicked update. There's a chance you might lose root.
hungrymr2 said:
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
I just did an OTA update with HiSuite 9.0.2.304, it was ridiculously easy. I simply clicked update. There's a chance you might lose root.
Click to expand...
Click to collapse
Thanks for the tip. Were you rooted before the update? If so, was it Magisk or SuperSu? Also, did you have TWRP installed?
I was not rooted when I installed the ota
hungrymr2 said:
I was not rooted when I installed the ota
Click to expand...
Click to collapse
Right, that's my main problem. If I wasn't rooted I could do the normal update through HiSuite or OTA. I'll click on those links you sent and read thoroughly. Thanks.
First restore stock recovery, flash this script in TWRP to do that https://mega.nz/#!8Swx3QaC!3JQ9imU70E9O1BxgO53Z754lGCZxCbKGgSHqvTEcXsQ
(assuming you haven't modified eRecovery as it will copy its ramdisk to recovery).
Secondly you can go to menu in System Updater and Download Latest full. That one will not fail to install. OTA can fail if you have modified ramdisk, kernel, system, vendor, product, cust (but not all are checked/patched in all OTA).
Full will not wipe data.
ante0 said:
First restore stock recovery, flash this script in TWRP to do that https://mega.nz/#!8Swx3QaC!3JQ9imU70E9O1BxgO53Z754lGCZxCbKGgSHqvTEcXsQ
(assuming you haven't modified eRecovery as it will copy its ramdisk to recovery).
Secondly you can go to menu in System Updater and Download Latest full. That one will not fail to install. OTA can fail if you have modified ramdisk, kernel, system, vendor, product, cust (but not all are checked/patched in all OTA).
Full will not wipe data.
Click to expand...
Click to collapse
I just noticed your reply! So, if I understand correctly, that Mega script is a flashable Zip through TWRP that will restore the stock recovery?
93starletgt said:
I just noticed your reply! So, if I understand correctly, that Mega script is a flashable Zip through TWRP that will restore the stock recovery?
Click to expand...
Click to collapse
Yes. It will write eRecovery_ramdisk to recovery_ramdisk (these partitions are exactly the same, only different entrypoints).
So as long as you have not modified eRecovery_ramdisk by flashing TWRP to it, it will restore your stock recovery.
ante0 said:
Yes. It will write eRecovery_ramdisk to recovery_ramdisk (these partitions are exactly the same, only different entrypoints).
So as long as you have not modified eRecovery_ramdisk by flashing TWRP to it, it will restore your stock recovery.
Click to expand...
Click to collapse
Thank you very much! I booted into TWRP, uninstalled Magisk (by flashing Magisk Uninstall Zip), flashed the stock recovery through TWRP (using the file on the link you gave me: https://mega.nz/#!8Swx3QaC!3JQ9imU70...bKGgSHqvTEcXsQ), rebooted and phone was stock again! I appreciate your help!