Related
I rooted my motoe lollipop (1st gen),it worked.
Today i got an official update from android and i downloaded it,
but when i installed it i gone to twrp. I rebooted it but it keeps on rebooting every minute
after entering system and goes back to twrp. Plsss help ... i'm stuck:crying:
Goto /cache directory from TWRP file manager, and delete tge content on it, first mount the system on twrp
Tarun1808 said:
I rooted my motoe lollipop (1st gen),it worked.
Today i got an official update from android and i downloaded it,
but when i installed it i gone to twrp. I rebooted it but it keeps on rebooting every minute
after entering system and goes back to twrp. Plsss help ... i'm stuck:crying:
Click to expand...
Click to collapse
OTA can not be installed when the TWRP or ROOT are installed.
They interfere with the installation by modifying the original system, especially TWRP because the OTA is not to flash. Care! Try to install the OTA with installed ROOT and TWRP can brick your Moto E.
Return to Stock 4.4.4. It does not have ROOT or TWRP. This enables the OTA installation usually via stock recovery with no problem.
[[[Sorry for my "bad English". I am a Brazilian and I'm using Google translator (which is horrible). Do not worry, I'm a power user, have tested over 15 custom roms and I've done a lot on my Moto E.]]]
So either I suck or I literally have the process wrong, but I was trying to install 6.0.1 last night for 2 hours. Originally I had 6.0 installed rooted, twrp, etc. OTA didnt work because I'm guessing twrp was installed as it errored out. So I decided to take WUG downloaded the binaries/newest stuff and decided to just manually flash 6.0.1. However at the same time I wanted to use the decrypter tool here.
My process was/is:
Flash Stock/Unroot button in WUG (with newest 6.0.1 already downloaded
Root button and flash customer recovery button/checkbox
Flash the perm recovery zip, supersu, and busybox
Flash the decrypter zip
Wipe data/cache/system/davik/etc and then freshly reboot
The problem is, it just hangs on the animation screen and never loads. I've tried it twice now, and its driving me insane. Where could I have went wrong? What is flawed about my process or maybe I'm using the wrong stuff. Thank you in advance guys!
chugger93 said:
So either I suck or I literally have the process wrong, but I was trying to install 6.0.1 last night for 2 hours. Originally I had 6.0 installed rooted, twrp, etc. OTA didnt work because I'm guessing twrp was installed as it errored out. So I decided to take WUG downloaded the binaries/newest stuff and decided to just manually flash 6.0.1. However at the same time I wanted to use the decrypter tool here.
My process was/is:
Flash Stock/Unroot button in WUG (with newest 6.0.1 already downloaded
Root button and flash customer recovery button/checkbox
Flash the perm recovery zip, supersu, and busybox
Flash the decrypter zip
Wipe data/cache/system/davik/etc and then freshly reboot
The problem is, it just hangs on the animation screen and never loads. I've tried it twice now, and its driving me insane. Where could I have went wrong? What is flawed about my process or maybe I'm using the wrong stuff. Thank you in advance guys!
Click to expand...
Click to collapse
I don't think the NRT is updated to properly root on 6.0.1 (Could be wrong).
Get the Latest SuperSU-v2.62-3 and flash that, It will modified the boot.img for you and include no forced encryption.
As long as you remove the encryption of the data partion in twrp from this guide
You shouldn't need the decrypter zip, also if you flash TWRP and boot into it before booting the system, you also won't need perm recovery.
Going by what I have read, still encrypted on my Device.
corkiejp said:
I don't think the NRT is updated to properly root on 6.0.1 (Could be wrong).
Get the Latest SuperSU-v2.62-3 and flash that, It will modified the boot.img for you and include no forced encryption.
As long as you remove the encryption of the data partion in twrp from this guide
You shouldn't need the decrypter zip, also if you flash TWRP and boot into it before booting the system, you also won't need perm recovery.
Going by what I have read, still encrypted on my Device.
Click to expand...
Click to collapse
ok so everytime I flash the supersu, it does its thing, then I format data, the reboot and twrp says supersu is not installed, do you wanna install it now? You can swipe to install or do not install.
Which I dont get becuase clearly I flashed the supersu zip a sec ago. if I continue to just flash it like it says, when I boot up, all I see in my drawer is the "SuperSU Installer" I have no idea what I'm doing wrong. If I dont have twrp install it when it asks, I got nothing in my app drawer
think I may have gotten it, had to download supersu from play store, then reflash, then let twrp flash it when it says it needed too, not I can launch supersu from the app drawer and it works.
Next problem is encryption. Under security it still says "Encrypted" do I need to actually hit the "Format Data' button in twrp? I just did a factory wipe slide.
chugger93 said:
ok so everytime I flash the supersu, it does its thing, then I format data, the reboot and twrp says supersu is not installed, do you wanna install it now? You can swipe to install or do not install.
Which I dont get becuase clearly I flashed the supersu zip a sec ago. if I continue to just flash it like it says, when I boot up, all I see in my drawer is the "SuperSU Installer" I have no idea what I'm doing wrong. If I dont have twrp install it when it asks, I got nothing in my app drawer
Click to expand...
Click to collapse
From the linked SuperSU thread
From the linked SuperSU thread said:
If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
Click to expand...
Click to collapse
This is do with the new systemless root and TWRP needs to be updated to reflect this change.
chugger93 said:
think I may have gotten it, had to download supersu from play store, then reflash, then let twrp flash it when it says it needed too, not I can launch supersu from the app drawer and it works.
Next problem is encryption. Under security it still says "Encrypted" do I need to actually hit the "Format Data' button in twrp? I just did a factory wipe slide.
Click to expand...
Click to collapse
From the linked guide above said:
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
Click to expand...
Click to collapse
Answers in quoted messages.
Never had to get SuperSU app from the store, maybe because I already had it installed, the app is also in the SuperSU zip.
I got the update for the January Security Update today. I grabbed the .zip's location and the link on Google's servers is:
https://android.googleapis.com/pack...51c56752.signed-angler-MMB29P-from-MMB29M.zip
Hope it helps others!
PSA: this is not flashable over custom ROMs, and cannot be used to install the factory OS from nothing. That's what the factory images are for . This .zip is solely to incrementally update from the December security update to the January one.
Is there an easy way to flash this update.zip without the need of a computer?
tinker_tf said:
Is there an easy way to flash this update.zip without the need of a computer?
Click to expand...
Click to collapse
Unless you have a custom recovery, no. Sorry about that
Updated. Thanks for the link!
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Also, I don't have the December update, where do I find that?
And lastly, I'm on MDB08L Build, will that work?
For those wanting to use this update and have completely stock system based on MMB29M. Boot into recovery and do an ADB sideload update.zip (rename zip first). Mine updated with no issues.
CipherSec said:
I have a rooted, stock ROM and TWRP and with several Xposed Modules, can I flash this?
Click to expand...
Click to collapse
If you've got all that set up, why not just update using the full factory image (without the wipe)
LeoRex said:
If you've got all that set up, why not just update using the full factory image (without the wipe)
Click to expand...
Click to collapse
I assumed I'll lose all my system modifications (i.e. Xposed Modules and their settings) as well as losing root and TWRP and having to reroot again.
pmedwards25 said:
Unless you have a custom recovery, no. Sorry about that
Click to expand...
Click to collapse
This is exactly the file you need if you don't have custom recovery, don't have root, and have not unlocked bootloader. It is the same file that would eventually come to you OTA. You do however need access to adb and a computer. I don't think this is flashable with a custom recovery.
Thanks..
Thanks for this file bro. dont need to wait.
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Casyis said:
Alright, feeling like a complete noob, here. I'm on systemless root 2.61 with TWRP. I fastboot flashed the stock boot.img and stock recovery, then tried to sideload the OTA zip. I got a "system contains unexpected contents" error, then installation aborted. Now, with systemless root, I had the understanding that flashing the stock system.img would not be necessary. I was not using systemless root before when I flashed the previous OTA zip. Can anyone spot where I might have gone wrong?
Click to expand...
Click to collapse
Try flash stock system image
Does this update fix the LTE issue?
HRodMusic said:
Does this update fix the LTE issue?
Click to expand...
Click to collapse
No it does not
I got it:
For systemless root, fastboot flash: 1) boot.img; 2) recovery.img; 3) vendor.img; 4) system.img
Boot to recovery and enter sideloade mode. adb sideload [update].zip
Reboot to bootloader. Re-flash TWRP, then in TWRP re-flash kernel (if custom) & superSU.
I used a toolkit to root my 6P. I'm using rooted stock rom. I got an OTA update but it seems I can't update it that way as per all others. So how do I go about installing this on my mobile? Do I need to unroot, flash stock recovery & then flash the new image? Then again I have to root?
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
asj0422 said:
fyi: i'm rooted with systemless root and twrp
I tried to take this update per usual as i would if i were unrooted, of course that didn't work totally. i assumed i would just find the update.zip file (i did: /data/data/com.google.android.gms/app.download/update.zip, icywtk) but when i tried to flash that it said the zip was corrupted. i deleted the zip and now it still says my december build is up to date. can't we just flash the update.zip with twrp? i did allow for the system to be modified this time when i booted twrp.
Click to expand...
Click to collapse
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
kmp14 said:
I am rooted with twrp. Same deal, twrp reports and error 7 when trying to flash the Jan security update.
Click to expand...
Click to collapse
i just tried this again with the same results. it says that the installer is expecting a different build (the one that my settings app shows i'm on) but that i have a build called huawei/mmasomething/ dee_stroyer somethingsomething. (i would post exactly what it says but i've already rebooted into system). I do remember something with "dee_stroyer" when i was rooting but it's not the system...
anyone else have any ideas? i'd like to just update normally and keep my data... and the stock android with root.
EDIT: also, the update won't update my recovery will it? i don't want to have to reflash that. i should be able to update even when i'm away from a computer haha.
Rooted with TWRP. I just tried an ADB sideload and get the same error.
Hi,
I was running:
Unlocked, TRWP and magisk on most actual version, beryllium-9.5.6-9.0-vendor-firmware, lineage-16.0-20190506-nightly-beryllium-signed
Today I started an OTA Lineage Update, but my Poco is now stuck in fastboot mode!
When I start minaml adb and type "fastboot continue", Lineage OS will boot normally. The TRWP-App Icon disappeared, but I can still start the TRWP-App via Google Play.
I copied all zips necessary for a clean new install onto my SD-Card, but I cannot boot into TRWP Recovery any more!
I downloaded the All in one tool, it connects: ADB device Ready. But I just don't know what to do for a clean new install.
Please help a newbie, I don't want to brick my Poco any further. I found a few threads that OTA Updates do not work that reliable, but I haven't figured out a solution.
Best regards
If I understand correctly, the Lineage OTA Update wiped the recovery Partition with TRWP?
That would explain why I cannot boot anymore to recovery.
As I remember I have been using OTA Updates in the past working fine. How should I update Lineage in the future? Always clean install? And how to backup all my data then, nandroid?
Should I now use the All in one tool to Flash TRWP again to recovery? How? Use "Recovery Flasher and Root" -> TRWP and check "Root after flash"?
Andi900rr said:
If I understand correctly, the Lineage OTA Update wiped the recovery Partition with TRWP?
That would explain why I cannot boot anymore to recovery.
As I remember I have been using OTA Updates in the past working fine. How should I update Lineage in the future? Always clean install? And how to backup all my data then, nandroid?
Should I now use the All in one tool to Flash TRWP again to recovery? How? Use "Recovery Flasher and Root" -> TRWP and check "Root after flash"?
Click to expand...
Click to collapse
Get the TWRP recovery image on to your pc, together with vendor/firmware zip for at least 2019-05-23. fastboot boot [TWRP recovery img] to boot the recovery, copy the vendor/firmware file over with adb, flash it with TWRP and reboot. If all goes well, great. If it doesn't, well...
Hi, I am unsure what you refer to by "TWRP recovery image", do you refer to "twrp-3.3.0-0-beryllium.img" or to some kind of backup image?
I have the "beryllium-9.5.23-9.0-vendor-firmware.img" on both, sd-card and PC now. I just do not know how to flash TWRP with the All in one tool, either by
Recovery -> Recovery Flasher and Root -> select recovery -> twrp-3.3.0-0-beryllium.img [and check the box "Root after Flash"]
or
Miscellaneous -> Advanced Options -> fastboot flash recovery twrp-3.3.0-0-beryllium.img
I just guess the first Option (Recovery)
Andi900rr said:
Hi, I am unsure what you refer to by "TWRP recovery image", do you refer to "twrp-3.3.0-0-beryllium.img" or to some kind of backup image?
I have the "beryllium-9.5.23-9.0-vendor-firmware.img" on both, sd-card and PC now. I just do not know how to flash TWRP with the All in one tool, either by
Recovery -> Recovery Flasher and Root -> select recovery -> twrp-3.3.0-0-beryllium.img [and check the box "Root after Flash"]
or
Miscellaneous -> Advanced Options -> fastboot flash recovery twrp-3.3.0-0-beryllium.img
I just guess the first Option (Recovery)
Click to expand...
Click to collapse
twrp-3.3.0-0-beryllium.img is what I was referring to. Boot it with the command I gave. The vendor-firmware is a zip file, not an img file. You need to flash that after booting TWRP.
Sent from my POCO F1 using XDA Labs
yes, vendor is of course zip not img.
Thank you for helping me!
I was using the all in one tool to Flash TWRP again with the Checkbox "root" activated, booted recovery and went though a whole new clean install, device is running fine again.
I am Kind of afraid to touch the OTA update Option ever again. Seems that when updating via OTA, one Need to still checkout compatibility of all other zips and TWRP Version etc.
So the effort is the same to do a clean install with all updated.
EEa(EU) rom 10.3.3.0 update
Received it too yesterday and all is ok.
Does anyone know how to flash that update using TWRP? I have rooted my Stock ROM with TWRP, and the Update is downloaded OTA and then reboots to recovery, but TWRP obviously is unable to install it: First it doesn't ask for the password to decrypt the data partition and shows the crypted content of the partition, making it impossible to see or select the downloaded update. A reboot into recovery decrypts the data partition and shows the downloaded Update (as a ZIP) in the folder /downloaded_rom. I tried to install that ZIP from TWRP manually, but to no avail - all you get is an error message.
Edit: Forget the question. Seems the phone healed itself. The first OTA download was an update 10.3.1 to 10.3.3 with a size of around 500 MB, and that couldn't be installed. When the System Updater saw this didn't succeed, it downloaded the complete 10.3.3 Package (2,2 GB) OTA, and installed that via TWRP with no problems whatsoever. I lost Magisk, which i needed to reinstall, but other than that, everything's fine.
Edit 2: The complete package obviously also overwrites TWRP, which i had to reinstall, too.
cgdams said:
Does anyone know how to flash that update using TWRP? I have rooted my Stock ROM with TWRP, and the Update is downloaded OTA and then reboots to recovery, but TWRP obviously is unable to install it: First it doesn't ask for the password to decrypt the data partition and shows the crypted content of the partition, making it impossible to see or select the downloaded update. A reboot into recovery decrypts the data partition and shows the downloaded Update (as a ZIP) in the folder /downloaded_rom. I tried to install that ZIP from TWRP manually, but to no avail - all you get is an error message.
Edit: Forget the question. Seems the phone healed itself. The first OTA download was an update 10.3.1 to 10.3.3 with a size of around 500 MB, and that couldn't be installed. When the System Updater saw this didn't succeed, it downloaded the complete 10.3.3 Package (2,2 GB) OTA, and installed that via TWRP with no problems whatsoever. I lost Magisk, which i needed to reinstall, but other than that, everything's fine.
Edit 2: The complete package obviously also overwrites TWRP, which i had to reinstall, too.
Click to expand...
Click to collapse
reagarding edit 2: which twrp did you use? I have real problems after the update, as the phone has no wifi now and the recovery is not working anymore
I also want to know if there's a place to get flash able zips through twrp for the latest eu roms.
lvnatic said:
I also want to know if there's a place to get flash able zips through twrp for the latest eu roms.
Click to expand...
Click to collapse
Here you can get all the official ROMs, fastboot and recovery
https://xiaomifirmwareupdater.com/archive/miui/raphael/
magdap said:
reagarding edit 2: which twrp did you use? I have real problems after the update, as the phone has no wifi now and the recovery is not working anymore
Click to expand...
Click to collapse
sorry i'm late with an answer, but i always use the newest version of mauronofrios TWRP (https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363).
Robbo.5000 said:
Here you can get all the official ROMs, fastboot and recovery
https://xiaomifirmwareupdater.com/archive/miui/raphael/
Click to expand...
Click to collapse
Thanks, can I flash the file using twrp and keep the recovery?
lvnatic said:
Thanks, can I flash the file using twrp and keep the recovery?
Click to expand...
Click to collapse
You will need to flash Magisk immediately after the ROM to stop MIUI restoring stock recovery.