Related
hey all!
So this is a first for me... I've been rooting and playing with android for a very long time (going back to the g1 days) and this is the first time I've ever seen this.
So I was on an old version of CM and decided it was time to update finally. I had unrooted a long time ago, but was still running cm perfectly fine. I went to install a new version of recovery (so I could update) and now when I try to boot into recovery I just get the oneplus logo. Here's the strange part, the phone isn't soft bricked... I can still boot into android no problem.
Anyone else every seen this problem? Do I need to start over (unlock bootloader, root, recovery, rom)?
Anyone else ever seen this happen on Oneplus One or any other phone for that matter?
Thanks in advance!
Same Problem Here
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Click to expand...
Click to collapse
I tried it and I got the following error:
/system/bin/sh: wipe_misc: not found
Click to expand...
Click to collapse
I don't know what else to do now. Please help.
janc_z said:
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
I tried it and I got the following error:
I don't know what else to do now. Please help.
Click to expand...
Click to collapse
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
zbt1985 said:
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
Click to expand...
Click to collapse
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
janc_z said:
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
Click to expand...
Click to collapse
Lucky you!
I on the other hand can't connect via adb, only fastboot...
Unofficial TWRP for Moto G5S Plus (Sanders)
Additional Features over Official TWRP:
Supports flashing of both 32bit and 64bit ROMs and Kernels.
OREO Images/ROMs support.
Decryption and Encryption support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
NTFS support(Both Read and Write).
Covers more partitions for nandroid backup (OEM, FSG and FSC).
Experimental support for SD cards that are partitioned for partial adopted storage and partial removable storage.
Faster I/O performance.
Fixed Gapps/aroma freeze issues.
IMPORTANT!!! : READ INSTRUCTIONS CAREFULLY BEFORE PROCEEDING TO FLASHING PROCESS..!!
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 Magisk or flash any of the verity disabler zips available on 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
Flashing Instructions:
Using Existing TWRP:
Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery
Other Methods(Fastboot) :
Make sure you have unlocked bootloader
Reboot to bootloader
Enter following command in terminal: fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary boot)
Incase your device is encrypted (while coming from stock rom), Follow these steps to decrypt:
Reboot to recovery > cancel the password prompt > mount all partitions > Format Data/Userdata (on f2fs) > Reboot Recovery > Mount all partitions again > Flash Magisk > Reboot
Now you are free to use Stock ROM (Decrypted) or Flash any custom rom you want.
Download Links: https://www.androidfilehost.com/?w=files&flid=216298
TWRP Themes: Check 3rd post
Known Issues: None || Report if you find any.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!), Tool/Utility for the Moto G5S Plus
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/twrp_device_motorola_sanders
Version Information
Status: Stable
Current Stable Version: r20
Stable Release Date: 2018-04-04
Created 2017-10-26
Last Updated 2018-04-04
|| Changelog ||
r20:
Fixed Encryption support on custom roms.
Updated kernel
Updated build fingerprint for latest bootloader support.
Reverted pigz changes.
Switched back to original twrp themes. (TWRP Themes can be found in 3rd post )
Various bug fixes and improvements.
r16:
Fixed compatibility with New Bootloader (C2.07-December patch)
Merged october patches in kernel.
Various twrp upstream patches and fixes.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
r15:
Added 64bit Support (You can flash both 32bit/64bit roms or kernels with it).
Fixed Encryption Support! (No need to format data to decrypt and mount).
Updated to 3.2.1 upstream changes with full oreo support.
Remove android reboot during password check on multiple wrong inputs.
r9:
Fixed F2FS mount issues(You can flash magisk modules or SuperSu now).
Enabled NTFS Write Support (You can make backups on sdcard/pendrives formatted on NTFS).
Fixed size of various partitions.
Switched to LZMA compression to decrease size.
r7: Initial Public Release
|| Themes ||
Here are some of the twrp themes:
Preview images: https://photos.app.goo.gl/DLrfDseGzfxE8Uq93
Download link: https://androidfilehost.com/?w=files&flid=233551
:good:
Only one that has actually be working for me ever since I got the phone. Thank you for your efforts.
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Well my guess is that the kernel in the present twrp is from the -26 firmware posted in the other thread. That firmware was US Retail also. The OP in the other thread states in can be used on other models. But I am not going to tell you that because I do not know. I have not found any other firmware for the sanders model.
Ae3NerdGod said:
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Click to expand...
Click to collapse
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Stock kernel is same in both the firmwares.
-45 is just for US variant, i dont recommend you to even flash that firmware on other variants.
CheckYourScreen said:
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
Click to expand...
Click to collapse
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Ae3NerdGod said:
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Click to expand...
Click to collapse
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
CheckYourScreen said:
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
Click to expand...
Click to collapse
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Ae3NerdGod said:
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Click to expand...
Click to collapse
Yes, same buttons to take a screenshot in TWRP
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
gewe said:
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
Click to expand...
Click to collapse
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
CheckYourScreen said:
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
Click to expand...
Click to collapse
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
gewe said:
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
Click to expand...
Click to collapse
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
lilcdroid said:
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
Click to expand...
Click to collapse
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Brycearuuni said:
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Click to expand...
Click to collapse
Sorry I wasn't aware you weren't still on stock. That kernel will only work on stock. I would verify with the maintainer of AOSP extended ROM that the kernel is patched to work with Magisk.
Sent by way of magic
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
ASUS - ZenFone 4 Pro - Z01G
TWRP Version: 3.3.1-0
Kernel Version: WW-15.0410.1904.104
*** WARNING ***
This image is NOT compatible with other ZenFones. If flashing is initiated on an unsupported device it COULD and/or WILL brick the device.
YOU ASSUME ALL RESPONSIBILITY!!
Notes:
This image was built from the official TWRP Minimal Manifest source for Android 8.1 and uses the prebuilt kernel from the WW-15.0410.1904.104 update posted on the ASUS website.
- The kernel has been patched to disable DM-Verity.
Installation:
Using fastboot from a command line or terminal you need to do-
fastboot flash recovery twrp-3.3.1-0-O8.1-PrebuiltKernel-15.0410.1904.104.img
fastboot oem reboot-recovery
Enjoy
Download Link
Thanks to shakalaca for his efforts in getting TWRP to our devices and his Device Tree!!
Hi, thanks for contributing to development on this phone!
So if I have my ZS551KL updated to the latest firmware version, and the bootloader is unlocked, can I flash this without wiping anything, and go on to flash Magisk v19.3?
Yes, you should be able to. Magisk should patch your bootloader for DM-verity.
Should i upgrade my twrp 3.2.1 to this version? what is the difference between twrp 3.2.1 and twrp 3.3.1?
So I went into fastboot mode, and flashed this image, then I went into recovery and flashed Magisk, rebooted into system and it worked.
Then I did a factory reset from the system settings, and now it only boots into TWRP. I just wanted to add TWRP and Magisk and start anew. What should I do?
At this point I would start fresh. Sounds like something went amiss. So from TWRP, I would wipe Dalvik, System, Data and Cache. Then back up to the reboot screen and tell it to reboot to recovery. At this point the system will warn that no OS is installed. Tell it to go ahead. It should reboot and bring you back to the recovery. From a PC download the zip below. Then transfer it to your phone while it's still in TWRP recovery. After it's transferred use TWRP to install it. It's my full update that also includes TWRP and the patched bootloader. Then tell the device to reboot. You should be completely fresh then. At that point of you want to install Magisk, go ahead. There isn't any reason to wipe it after installing Magisk.
https://mega.nz/#!BegyVKiB!zxgzNBr_XJ4WnlJBwqMq1oqbQgnuECkdClcZLNVIPz8
Okay, thanks. I am gonna try that tomarrow.
That image you gave me has TWRP 3.2.1 right? Right now I have the latest, 3.3.1.
Can I have TWRP update itself , or should I reflash the 3.3.1 from your other post again?
Sorry to all the questions, I'm relatively new and you seem like you know how everything works.
Okay, I did what you said. I noticed the phone hanging up in some parts of first-time-setup that it wasn't before, but it might be nothing. I also keep having a popup say "FOTAService keeps stopping" with a Close app option. Closing the app doesn't fix it, it returns maybe a minute or two later. The only way I can stop it is by force stopping the app, but It restarts the next time my phone is rebooted. I've cleared its data/cache and it didn't help. I've seen some people say to 'freeze' the service to fix it. How would you fix it?
Also, on another side note: did you add the google assistant to this update, or was it added by ASUS? I don't recall it being there when I first started, but its a nice surprise to see its included.
---------- Post added at 05:46 PM ---------- Previous post was at 05:31 PM ----------
Welp, I just answered my own question. I went into TWRP and wiped Davlik again, and FOTA stopped stopping :good:
As for it being slow during first-time-setup, it might just be Davlik optimizing everything since the cache was cleared.
So I'm gonna try to update TWRP from that image you gave me, because it bothers me not having the newest version lol
Thanks so much! Very helpful
Cool, after flashing your image, I flashed your TWRP image from your other thread and i have the lateat version.
I also wanted to add that the FOTAService thing kept happening for a while. I am not sure exactly what did the trick, but some combonation of force stopping the FOTAService, clearing all data for the app, and then botting into TWRP and clearing Davlik, and then possibly letting the phone do its work reoptimizing apps finally stopped it for good. Just wanted to post that incase anybody else was having the same issue.
bobs50000 said:
So I went into fastboot mode, and flashed this image, then I went into recovery and flashed Magisk, rebooted into system and it worked.
Then I did a factory reset from the system settings, and now it only boots into TWRP. I just wanted to add TWRP and Magisk and start anew. What should I do?
Click to expand...
Click to collapse
bobs50000 said:
Cool, after flashing your image, I flashed your TWRP image from your other thread and i have the lateat version.
I also wanted to add that the FOTAService thing kept happening for a while. I am not sure exactly what did the trick, but some combonation of force stopping the FOTAService, clearing all data for the app, and then botting into TWRP and clearing Davlik, and then possibly letting the phone do its work reoptimizing apps finally stopped it for good. Just wanted to post that incase anybody else was having the same issue.
Click to expand...
Click to collapse
I'm sorry I didn't respond sooner, it's been daughters birthday. I'm glad you go everything lined out. The FOTA issue is kinda odd. Never had it. I've probably flashed and reflashed this phone close to a hundred times. Heck because I was bored the other night I even went back to 7.1.1 to play around. I'm not sure which version I like better, lol. I'm probably going to end up posting pure OEM zips for those that want to be 99% stock. We just can't relock the bootloader. Cheers!
TheCapesCrew said:
ASUS - ZenFone 4 Pro - Z01G
TWRP Version: 3.3.1-0
Kernel Version: WW-15.0410.1904.104
*** WARNING ***
This image is NOT compatible with other ZenFones. If flashing is initiated on an unsupported device it COULD and/or WILL brick the device.
YOU ASSUME ALL RESPONSIBILITY!!
Notes:
This image was built from the official TWRP Minimal Manifest source for Android 8.1 and uses the prebuilt kernel from the WW-15.0410.1904.104 update posted on the ASUS website.
- The kernel has been patched to disable DM-Verity.
Installation:
Using fastboot from a command line or terminal you need to do-
fastboot flash recovery twrp-3.3.1-0-O8.1-PrebuiltKernel-15.0410.1904.104.img
fastboot oem reboot-recovery
Enjoy
Download Link
Thanks to shakalaca for his efforts in getting TWRP to our devices and his Device Tree!!
Click to expand...
Click to collapse
Hello everyone!
Can I get a NEW download link? or if there is a new further version ... the link in the post has expired ... THANKS
Hello,
Since MIUI 10.3.1.0 (PEIMIXM) was launched, I tried to update my device. After the update, when the smartphone rebooted it kept stuck in Mi logo sreen (Android loading wasn't also appearing). I tried to use MiFlash to reflash the ROM and the same happended.
Thinking it was a random problem of MIUI I decided to move to Pixel Experience because I had used it before and I liked. In the same day of MIUI 10.3.1.0 (PEIMIXM) launch, Pixel Experience also launched a new whyred version (in the beggining of June, i think).
I did what was needed to successfully install the ROM according to the dev's thread:
-I downloaded all the needed files (MIUI 10.3.1.0 PEIMIXM firmware, Pixel Experience ROM, recommended modified TWRP version of the developer);
-Initially, I installed TWRP via fastboot mode;
-I flashed the firmware;
-I wiped the partitions Cache Dalvik / ART, System, Cache, Data, vendor;
-I flashed Pixel Experience ROM;
-I wiped Internal Storage;
-I rebooted the device.
After those steps, I couldn't get access to my "homescreen". Basically, my phone stays stuck at the Mi logo screen. And nothing happens.
Considering it could be a recovery problem, I tried to use Pitch Black Recovery (the latest version available for whyred) that supports Oreo and Pie. I used TWRP to flash this one, and after that I made all the steps above again and the same happened.
I'm now only available to flash MIUI (if it is Android 8.1). I can only flash Pixel experience versions that were released before the MIUI Pie stable for this device.
I really appreciate if you could help me!
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
htchd2sucks said:
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
Click to expand...
Click to collapse
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
floater3 said:
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
Click to expand...
Click to collapse
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
htchd2sucks said:
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
Click to expand...
Click to collapse
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
floater3 said:
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
Click to expand...
Click to collapse
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
htchd2sucks said:
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
Click to expand...
Click to collapse
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
floater3 said:
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
Click to expand...
Click to collapse
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
htchd2sucks said:
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
Click to expand...
Click to collapse
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
floater3 said:
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
Click to expand...
Click to collapse
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
htchd2sucks said:
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
Click to expand...
Click to collapse
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
floater3 said:
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
Click to expand...
Click to collapse
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
htchd2sucks said:
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
Click to expand...
Click to collapse
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
floater3 said:
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
Click to expand...
Click to collapse
It's clearly not related to recovery, at least, not directly.
-Check what "wipes" you have done, and ideally do all of them + format data (you can always reencrypt later). Then, reboot, and redo the flashing of everything.
-Another option would be to flash with "miflash" which I think will also restore some boot things. In that scenario, you are on your own because I don't know about ARB in your case and all potential issues.
I can only say that I did a "miflash" when I used to have ARBv3, and it went fine (I had to redo the recovery, etc... after).