Hi,
yesterday I tried upgrading my Moto Z running LOS 15.1 to 16. For some reason I had to undo the full disk encryption first because my lock pattern was not recognized anymore after the update.
So I removed the encryption first, did the upgrade, booted, and enabled encryption again under LOS 16.
The phone now restarts but is then stuck in a bootloop. I'm using TWRP 3.2.3.0 as there is no newer version for the Moto Z. Has anyone seen the same or do you have any idea what went wrong here?
Kind regards
Question on how to remove the encryption
KRKroenen said:
Hi,
yesterday I tried upgrading my Moto Z running LOS 15.1 to 16. For some reason I had to undo the full disk encryption first because my lock pattern was not recognized anymore after the update.
So I removed the encryption first, did the upgrade, booted, and enabled encryption again under LOS 16.
The phone now restarts but is then stuck in a bootloop. I'm using TWRP 3.2.3.0 as there is no newer version for the Moto Z. Has anyone seen the same or do you have any idea what went wrong here?
Kind regards
Click to expand...
Click to collapse
Hi, since you encrypted your phone, I have a question, My Moto Z Factory firmware comes with encryption enabled and i dont know how to disable it, if you could help me it would be great, thanks
MacoAndroidRon said:
Hi, since you encrypted your phone, I have a question, My Moto Z Factory firmware comes with encryption enabled and i dont know how to disable it, if you could help me it would be great, thanks
Click to expand...
Click to collapse
Hi, you try this:
Boot into recovery.
Identify the /data device location: adb shell df /data
this will return something like: /dev/block/blabla
then: adb pull /dev/block/blabla userdata.img
Then wipe the partition.
Then unmount the partition, adb push the userdata back into it and remount.
KRKroenen said:
Hi,
yesterday I tried upgrading my Moto Z running LOS 15.1 to 16. For some reason I had to undo the full disk encryption first because my lock pattern was not recognized anymore after the update.
So I removed the encryption first, did the upgrade, booted, and enabled encryption again under LOS 16.
The phone now restarts but is then stuck in a bootloop. I'm using TWRP 3.2.3.0 as there is no newer version for the Moto Z. Has anyone seen the same or do you have any idea what went wrong here?
Kind regards
Click to expand...
Click to collapse
So i found out there's an encryptionfix.zip from Erfano. Perhaps that could also solve the problem although I have not tested yet:
https://forum.xda-developers.com/showpost.php?p=79068444&postcount=265
KRKroenen said:
Hi, you try this:
Boot into recovery.
Identify the /data device location: adb shell df /data
this will return something like: /dev/block/blabla
then: adb pull /dev/block/blabla userdata.img
Then wipe the partition.
Then unmount the partition, adb push the userdata back into it and remount.
Click to expand...
Click to collapse
Thanks for your help, I've already fixed this problem, but now I have another 2 questions:
1. Have you tryed Multi Rom?
2. And if so, do u know Why do I get error 7 every time I try to install Lineage OS 16 (having stock 7.1.1 as my primary ROM)
MacoAndroidRon said:
Thanks for your help, I've already fixed this problem, but now I have another 2 questions:
1. Have you tryed Multi Rom?
2. And if so, do u know Why do I get error 7 every time I try to install Lineage OS 16 (having stock 7.1.1 as my primary ROM)
Click to expand...
Click to collapse
Sorry, no I didn't try Multi ROM
Related
Hello,
My apologies if I've posted this thread in the wrong section.
I bricked my One Plus X trying to install the Nougat Nightlies update. I accidentally wiped off the entire data include internal storage so now I cannot boot or restore to the old image. The OS is gone and the phone gets stuck at the boot screen.
The plan was to install the One Plus recovery and then install the OOS3.1.4. I managed to install the One Plus Marshmallow recovery using adb -- the issue is when I try to push the Oxygen OS 3.1.4 image to the internal storage it gives me this error message
Code:
C:\adb>adb push OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip /system/
failed to copy 'OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip'
to '/system//OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip':
Read-only file system
I cannot run adb as root it effectively complaints about the phone being in production mode so I'm honestly out of ideas on how to fix this.
It was pretty stupid of me to attempt to flash my phone w/o prior knowledge of rooting. I just want my phone to go back to the older version.
Any help is greatly appreciated.
Thank you.
VayneSpotting said:
Hello,
My apologies if I've posted this thread in the wrong section.
I bricked my One Plus X trying to install the Nougat Nightlies update. I accidentally wiped off the entire data include internal storage so now I cannot boot or restore to the old image. The OS is gone and the phone gets stuck at the boot screen.
The plan was to install the One Plus recovery and then install the OOS3.1.4. I managed to install the One Plus Marshmallow recovery using adb -- the issue is when I try to push the Oxygen OS 3.1.4 image to the internal storage it gives me this error message
Code:
C:\adb>adb push OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip /system/
failed to copy 'OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip'
to '/system//OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip':
Read-only file system
I cannot run adb as root it effectively complaints about the phone being in production mode so I'm honestly out of ideas on how to fix this.
It was pretty stupid of me to attempt to flash my phone w/o prior knowledge of rooting. I just want my phone to go back to the older version.
Any help is greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Anyhow ,do you have access to custom recovery ?
Sent from my MotoG3-TE using Tapatalk
[email protected] said:
Anyhow ,do you have access to custom recovery ?
Sent from my MotoG3-TE using Tapatalk
Click to expand...
Click to collapse
Yes I do have the CM Nightly recover but it doesn't boot due to the <dtb not found> error message.
VayneSpotting said:
Yes I do have the CM Nightly recover but it doesn't boot due to the <dtb not found> error message.
Click to expand...
Click to collapse
Install the latest TWRP using Adb then ? https://dl.twrp.me/onyx/twrp-3.0.3-0-onyx.img.html
Whats the error while you try to install the recovery ?
Open Adb:
Type "adb reboot bootloader"
fastboot flash recovery twrp.img
[email protected] said:
Install the latest TWRP using Adb then
Whats the error while you try to install the recovery ?
Open Adb:
Type "adb reboot bootloader"
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Holy moly. The latest twrp recovery worked perfectly. I installed the OS 3.1.4 and it's working perfectly fine.
Not a big deal but I was just wondering if there's a way to switch back to official One Plus recovery rom without messing with the OS?
Many thanks dude!
VayneSpotting said:
Holy moly. The latest twrp recovery worked perfectly. I installed the OS 3.1.4 and it's working perfectly fine.
Not a big deal but I was just wondering if there's a way to switch back to official One Plus recovery rom without messing with the OS?
Many thanks dude!
Click to expand...
Click to collapse
Yeah there is ,let me figure out and do some searching
Unofficial TWRP 3.1.0-0 Moto G5 (cedric)
Latest TWRP changelog :
New features of 3.1.1-0 (adb backup, tweaked MTP startup routines and plenty of bug fixes - for full changelog)
Download Link
twrp-3.1.1-0-cedric.img
Working/Bugs
I have just tested on 16 GB variant and all seems to be working. If something is broken lemme know.
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide
Make sure you have unlocked bootloader
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
XDA:DevDB Information
[Unofficial] TWRP 3.1.1-0 Moto G5, Tool/Utility for the Moto G5
Contributors
Santhosh M
Source Code: http://Using prebuilt stock kernel and hence no kernel source available
Version Information
Status: Stable
Stable Release Date: 2017-10-05
Created 2017-03-17
Last Updated 2017-10-05
Reserved
Reserved
Even though I have the plus variant, it's cool to see these features popping up.
Johny Cipeli said:
Even though I have the plus variant, it's cool to see these features popping up.
Click to expand...
Click to collapse
+1
Grt @Santhosh M
Santhosh M said:
Reserved
Click to expand...
Click to collapse
Gonna get that g5+ Bro? it would be awesome if you will be there for support too.
xt1670 model
Hi Santhosh
Will this TWRP work on Moto G5 model xt1670?
If so, can it be rooted using twrp temporary boot?
EDIT: I have tried this several time, I'm always getting stuck at boot, after the first data wipe, only solution is to install stock system again.
I have the Modem Version: M8937_8000.122.02.40R, 32GB
I'm offering to test
Thanks
Works fine for the most part, though reboot options Bootloader and Power Off doesn't work, just restarts normally.
XT1676
KawaiiNeko said:
Works fine for the most part, though reboot options Bootloader and Power Off doesn't work, just restarts normally.
XT1676
Click to expand...
Click to collapse
Plz share the procedure you had followed.
Did you able to achieve root access?
fAIyaZ said:
Plz share the procedure you had followed.
Did you able to achieve root access?
Click to expand...
Click to collapse
Unlocked bootloader, flashed twrp, factory reset, good to go. Sadly no root though.
KawaiiNeko said:
Unlocked bootloader, flashed twrp, factory reset, good to go. Sadly no root though.
Click to expand...
Click to collapse
Try phh su.
Flash it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/d....phh.superuser
fAIyaZ said:
Try phh su.
Flash it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/d....phh.superuser
Click to expand...
Click to collapse
worked perfectly! https://i.imgur.com/71G0cN2.png
I'll get my G5 16gb lunar grey tomorrow and can't wait to root
Thanks for testing out
Bootlooping
Hi guys, I got bootloop in my moto g5 after TWRP boot/install, should I open a new thread or somebody can help here?
linsspinho said:
Hi guys, I got bootloop in my moto g5 after TWRP boot/install, should I open a new thread or somebody can help here?
Click to expand...
Click to collapse
Depending on your phone version, you might need to flash system using fastboot.
KawaiiNeko said:
worked perfectly! https://i.imgur.com/71G0cN2.png
Click to expand...
Click to collapse
So i believe TWRP works as intended and root is also achieved via phh/whatever?
If all works fine for you would like you to make reply in the thread with detailed flashing instructions as i am not sure why few in thread have issues
can this version of twrp be used for POTTER version of moto G5 plus?
After installing TWRP my Phone stucks at the "Your device has been unlocked" screen. My system seems to be gone. I've downloaded the image from the other thread and tried to sideload it, but twrp says it's in the wrong format. TWRP boots fine
(Anyone who can upload a fully working NANDROID or sth like that?)
What can i do :/?
Edit: Solved. Unzipped the firmware and flashed manually via fastboot. Working fine!
But then again at the startup of the recovery, there's the encryption message. What to wipe now, that it'll work? Wiping /data ends in boot loop...
.sirhc said:
After installing TWRP my Phone stucks at the "Your device has been unlocked" screen. My system seems to be gone. I've downloaded the image from the other thread and tried to sideload it, but twrp says it's in the wrong format. TWRP boots fine
(Anyone who can upload a fully working NANDROID or sth like that?)
What can i do :/?
Edit: Solved. Unzipped the firmware and flashed manually via fastboot. Working fine!
But then again at the startup of the recovery, there's the encryption message. What to wipe now, that it'll work? Wiping /data ends in boot loop...
Click to expand...
Click to collapse
Did you tried wiping data, and formatting data? Remember that wiping /data is where your apps and settings are stored, and formatting /data/media is the massive storage... Maybe if you wipe both it would work
Enviado desde mi Moto G (5) Plus mediante Tapatalk
After
fastboot flash recovery twrp.img
I'm booting into recovery, cancel the encryption password verification, swipe to allow modification, wipe & format data -> Bootloop
Flashing system (and only system, not recovery etc) -> Phone boots normally, twrp ist gone ...
Greetings
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!
Hello,
My Thor device seems to be bricked after trying to enable encryption in Lineage OS (this happened a couple of months ago).
The device used to have an unlocked bootloader with TWRP 3.1.1-1, Lineage OS 14.1 20170710 and Open GApps installed and was running without any problems (thanks to all the people here who have made this possible btw!) until enabling encryption. The encryption process was running for an eternity (more than one day), so I switched the device off.
Since then, I only get a grey "kindle fire" logo. No booting of Lineage or TWRP anymore . It's possible to start in fastboot mode via pressing the on/off switch and the volume button simultaneously, though.
I don't have any experience with bricked devices. Any suggestions what to do? And are there known issues with encryption on this device?
Many thanks in advance for your help!
RiseT said:
Hello,
My Thor device seems to be bricked after trying to enable encryption in Lineage OS (this happened a couple of months ago).
The device used to have an unlocked bootloader with TWRP 3.1.1-1, Lineage OS 14.1 20170710 and Open GApps installed and was running without any problems (thanks to all the people here who have made this possible btw!) until enabling encryption. The encryption process was running for an eternity (more than one day), so I switched the device off.
Since then, I only get a grey "kindle fire" logo. No booting of Lineage or TWRP anymore . It's possible to start in fastboot mode via pressing the on/off switch and the volume button simultaneously, though.
I don't have any experience with bricked devices. Any suggestions what to do? And are there known issues with encryption on this device?
Many thanks in advance for your help!
Click to expand...
Click to collapse
Have you tried booting a TWRP image from fastboot? If that works recovery will be a lot easier.
fastboot devices
--> if no response to this command you'll need to update host drivers
fastboot boot <twrp-image-name>
--> you can download a suitable TWRP image from here
Davey126 said:
Have you tried booting a TWRP image from fastboot? If that works recovery will be a lot easier.
fastboot devices
--> if no response to this command you'll need to update host drivers
fastboot boot <twrp-image-name>
--> you can download a suitable TWRP image from here
Click to expand...
Click to collapse
Excellent! MANY MANY THANKS! You've made my day! Worked like a charm (i. e. worked like a charm after my usual trial & error for hours to make Windows accept a Kindle Fire driver for fastboot - had to force one it warned me about on it to make it finally work).
A couple more question if I may:
When and why does one need a "Fastboot cable" (always been confused about this)?
Do you happen to know if device encryption normally works with this device?
Does switching debugging off in Lineage prevent unbricking via fastboot like this (wouldn't think so but want to make sure)?
Thanks again!
RiseT said:
Excellent! MANY MANY THANKS! You've made my day! Worked like a charm (i. e. worked like a charm after my usual trial & error for hours to make Windows accept a Kindle Fire driver for fastboot - had to force one it warned me about on it to make it finally work).
A couple more question if I may:
When and why does one need a "Fastboot cable" (always been confused about this)?
Do you happen to know if device encryption normally works with this device?
Does switching debugging off in Lineage prevent unbricking via fastboot like this (wouldn't think so but want to make sure)?
Thanks again!
Click to expand...
Click to collapse
Quick answers as I'm on the move (sorry for brevity) ...
- Moto drivers almost always work with HDX devices; install this package (don't have to launch it) which includes drivers; no warnings either
- Fastboot cables are largely ineffective on Amazon devices and rarely needed (special/unique cases beyond scope of this post)
- Encryption is NOT supported with custom ROMs on this device; dipping your head in boiling oil is a more enjoyable experience
- Prior debug setting in Lineage should have little/no impact on unbricking success
If you are unable to reload a ROM (Lineage in particular) you may have to do some further work on the data partition to remove encryption remnants. Post back if this is the case; I'll try to scare up the related material.
Davey126 said:
If you are unable to reload a ROM (Lineage in particular) you may have to do some further work on the data partition to remove encryption remnants. Post back if this is the case; I'll try to scare up the related material.
Click to expand...
Click to collapse
Thanks for your replies!
Thanks, my Thor is already up & running with the latest LineageOS and Open GApps. No problems so far. Prior to installing, In order to play it safe, I've made sure to wipe/format all partitions (including the data partition) from TWRP. Had a feeling that this would possibly be a good thing to do after that (partially?) failed encryption experience...
RiseT said:
Thanks, my Thor is already up & running with the latest LineageOS and Open GApps. No problems so far. Prior to installing, In order to play it safe, I've made sure to wipe/format all partitions (including the data partition) from TWRP. Had a feeling that this would possibly be a good thing to do after that (partially?) failed encryption experience...
Click to expand...
Click to collapse
Suspect encryption run was incomplete as simply the wiping data partition in TWRP is usually insufficient to remove critical remnants. A format is needed along with something else I don't immediately recall. You would be aware if that was needed as Lineage would hang on boot.
I can second this warning, do NOT USE ENCRYPTION. I tried so unter Lineage OS 14.1. As a result I had to wipe/format the data partition using TWRP, which let me escape from the bootloop.
Davey126 said:
Suspect encryption run was incomplete as simply the wiping data partition in TWRP is usually insufficient to remove critical remnants. A format is needed along with something else I don't immediately recall. You would be aware if that was needed as Lineage would hang on boot.
Click to expand...
Click to collapse
Can you give more details on how to remove these remnants? I did the same thing as OP this morning & now I'm here trying to undo my mistake :crying:
I still have TWRP 3.1.1-1 & I can flash stock 4.5.5 rom, but I can't flash any other custom roms as I'd get into a boot loop with grey kindle fire logo. I did wipe everything except sdcard, and the stock rom is running perfectly fine, except for root & gapps, of course.
Edit: SOLVED, courtesy to this post https://forum.xda-developers.com/showpost.php?p=74710623&postcount=1029
My phone just got the android 9 update, I already had installed root with twrp on my device with android 8.0
So when I tried to re-root my phone I needed to reinstall the TWRP but it couldn't decrypt the data
I tried all of the posible solutions to this but nothing
I think that is the TWRP version that can't decrypt data in android 9.0
But in the web isn't any version that support the Mi 8 LIte with Android 9.0
Do I need to wait until someone update the TWRP version or what can I do?
Thanks in advance
Sebaxe07 said:
My phone just got the android 9 update, I already had installed root with twrp on my device with android 8.0
So when I tried to re-root my phone I needed to reinstall the TWRP but it couldn't decrypt the data
I tried all of the posible solutions to this but nothing
I think that is the TWRP version that can't decrypt data in android 9.0
But in the web isn't any version that support the Mi 8 LIte with Android 9.0
Do I need to wait until someone update the TWRP version or what can I do?
Thanks in advance
Click to expand...
Click to collapse
Formatting data have to decrypt it, you have to be sure that TWRP is able to mount data partition.
SubwayChamp said:
Formatting data have to decrypt it, you have to be sure that TWRP is able to mount data partition.
Click to expand...
Click to collapse
So I need to erease all of my phone data to be able to use twrp? But why it didn't have this problem the first time?
Sebaxe07 said:
So I need to erease all of my phone data to be able to use twrp? But why it didn't have this problem the first time?
Click to expand...
Click to collapse
You are upgrading now; for this you need to decrypt it for first time and probably every time that you switch from a miui to an AOSP rom. Be sure that your data partition is mounted and I guess you can´t see the files under TWRP. Try first with this zip https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Stock Miui re-encrypt data on first boot after factory reset, so you need to flash Universal DM-Verity
I also need TWRP for pie.
Try this recovery, It has more features than TWRP https://sourceforge.net/projects/orangefox/files/test_builds/OrangeFox-R9.0-1-platina.zip/download
SubwayChamp said:
Try this recovery, It has more features than TWRP https://sourceforge.net/projects/orangefox/files/test_builds/OrangeFox-R9.0-1-platina.zip/download
Click to expand...
Click to collapse
Thanks
SubwayChamp said:
Try this recovery, It has more features than TWRP https://sourceforge.net/projects/orangefox/files/test_builds/OrangeFox-R9.0-1-platina.zip/download
Click to expand...
Click to collapse
Would you happen to know if opengapps aroma works with this recovery. I have tried 3 or 4 other revoveries and once options are selected and install starts recovery reboots. After that I have to hold power to force reboot because no matter what reboot option I choose it just goes back to recovery.
cidxtc said:
Would you happen to know if opengapps aroma works with this recovery. I have tried 3 or 4 other revoveries and once options are selected and install starts recovery reboots. After that I have to hold power to force reboot because no matter what reboot option I choose it just goes back to recovery.
Click to expand...
Click to collapse
Unfortunately I can't tell you for sure cause left 3 days to unlock my bootloader but I used this recovery in two Xiaomi devices (R5Plus and Mi Max) and was the best I ever tried, never had issue flashing Aroma zips.
Be sure that once finished the installation Reboot box in Aroma be unticked
SubwayChamp said:
Unfortunately I can't tell you for sure cause left 3 days to unlock my bootloader but I used this recovery in two Xiaomi devices (R5Plus and Mi Max) and was the best I ever tried, never had issue flashing Aroma zips.
Be sure that once finished the installation Reboot box in Aroma be unticked
Click to expand...
Click to collapse
Never had an issue with redmi note 4x and aroma either. The reboot box does not make a difference because the install never happens. I will download and try.
Sebaxe07 said:
I think that is the TWRP version that can't decrypt data in android 9.0
But in the web isn't any version that support the Mi 8 LIte with Android 9.0
Click to expand...
Click to collapse
If you are using the wzsx150 3.2.3 twrp found under the ROM/recovery section, versions 0121 and 0212 are both supposed to be for Android 9. I haven't tried myself though, as I am still on 8.
I can confirm version 0212 does indeed decrypt data partition, making it mountable it inside TWRP. Of course phone's now running on official Android 9 MIUI 10, updated on Wednesday.
So heads up for anyone trying to use open gapps aroma installer. No recovery will install it. Tried batik, orange fox, perp, and wzsx150 twrp and all do the same. After all the selections when the actual installation starts the device reboots (installs nothing but does save setting options) back to recovery. All reboot options (system, fastboot, etc) all reboot back to recovery only holding power button will allow device to boot into system.
MetallicGR said:
I can confirm version 0212 does indeed decrypt data partition, making it mountable it inside TWRP. Of course phone's now running on official Android 9 MIUI 10, updated on Wednesday.
Click to expand...
Click to collapse
I am using wzsx150 3.2.3-1003 and it does not decrypt data, even with proper password.. Where can I find 0212. I cannot find it in this forum. ..only the bad one I am using.
EDIT: Nevermind. Found it.
MetallicGR said:
I can confirm version 0212 does indeed decrypt data partition, making it mountable it inside TWRP. Of course phone's now running on official Android 9 MIUI 10, updated on Wednesday.
Click to expand...
Click to collapse
Any idea why is 0212 half the size of 0121, and the others for that matter (28MB vs 60MB).
I believe it's somehow compressed. If you open these files with something like 7zip you'll see the size is very close between the two.
MetallicGR said:
I believe it's somehow compressed. If you open these files with something like 7zip you'll see the size is very close between the two.
Click to expand...
Click to collapse
Oh okay. That would make sense.
lexridge said:
I am using wzsx150 3.2.3-1003 and it does not decrypt data, even with proper password.. Where can I find 0212. I cannot find it in this forum. ..only the bad one I am using.
EDIT: Nevermind. Found it.
Click to expand...
Click to collapse
Can yo share the 0212 img to Pie I'm stll in Oreo and the Pie update notification is a little annoying so I want to update but I haven't found the twpr 0212 for mi 8 lite.
Here you go. https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46
Another member replied to your other thread as well.