I've been trying to downgrade to 3.5.3 from 3.5.4 through TWRP but keep on getting stuck at Patching System Unconditionally. This also happened when I tried flashed the leaked nougat build but luckily I had a nandroid backup. I have the chinese model and think the problem is related to this. If anyone can help please do so, as the battery drain on 3.5.4 is getting unbearable.
The OEM roms need to be flashed onto F2FS system.
It does take a long time iirc
Have you tried sideloading the rom via ADB?
Related
Hello there!
I’m currently the newest Nougat image (7.0.0 NBD90Z). Before flashing to this version I was on the latest marshmallow image (6.0.1 MOB31H). Initially I dirty-flashed the image, keeping the data partition intact.
However, after I tried to root the phone with SuperSU 3.78 SR1 via TWRP recovery I got into a bootloop. After restoring stock again, I backed up my data partition (nandroid backup) and did a clean flash. On the clean ROM rooting works just fine - when I tried restoring my data partition after root was up the phone got into a bootloop again.
I repeated my experiments with SuperSU 3.78 (non-SR) and 3.76 - same results.
It seems the phone gets stuck quite late into the booting process since it is detected by my PC and listed under adb (as offline, mind you).
I don't even know how to begin to analyze or debug this problem since rooting and even dirty-flashing between major versions has been working for me since Nexus 4 / KiteKat times.
Letting go of all my userdata (at least entirely) is not an option.
Any ideas or directions how I could proceed into tracking down the problem?
So I've been having lots of problems, it all started trying to upgrade to oreo from nougat and I got stuck part way with trying to install recoveries and missing the _ramdisk part. So then I think I was stuck somewhere in-between nougat and oreo and @Jannomag has been a huge help trying to push the device towards Oreo. You can see the thread where that begun here (https://forum.xda-developers.com/p1...-partition-length-t3766191/page2#post75966617) and Jannomag's guide here (https://forum.xda-developers.com/showpost.php?p=75760807).
After that as going to oreo wasn't working I looked into maybe trying to roll back to nougat as TWRP 3.2.1 was working. I have followed this guide as best I could (https://forum.xda-developers.com/p10/how-to/guide-to-rollback-huawei-p10-oreo-to-t3735156) and got to the end where you install the update let the phone reboot to huawei recovery to install the update. However the update got to 6% in verifying update and failed. At this point I tried to reflash twrp from fastboot. That seemed to flash fine however when I reboot the phone to recovery (vol-Up + pwr) it boots to the huawei recovery menu with reboot/wipe data/wipe cache options. I have tried flashing both twrp 3.2.1 3.1.1 and 3.0.1 and even reflashing the stock recovery before these from the file linked in the rollback guide that HWOTA8 uses (MHA_RECOVERY8_NoCheck.img)
Any ideas for fixes this are appreciated,
Thanks
Edit: Solved using DC-phoenix
The newest TWRP 3.2.3.-1 does not let me boot into ROM, just brings me back to TWRP again. I have to restore a backed up boot image (with 3.2.3-0) to boot normally. Even flashing TWRP 3.2.3-0 in TWRP does not bring me back.
Anyone else having experiencing this? I have attached my recovery logs.
I was on stock ...and just install los16 without problem... So i dont have problems with TWRP.
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
jhedfors said:
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
Click to expand...
Click to collapse
There is always a risk when flashing your device. One of the reasons why I prefer to flash using Linux was that Windows would have so much going on in the background that I risked the data transfer being corrupt. That said, if you're using Windows, I'd close all programs and especially disable any anti-virus running in the background. Sure, Linux may have a few things running, but I have always found it did a better job multitasking resources than Microsoft Windows with a fewer chance of data loss.
It is probably because after installing Google Apps, your /data partition gets corrupted.
So after installing Google Apps, go to TWRP > Wipe > "Format Data" & reboot.
I've the same problem & this resolves the issue for me.
For me, this did not help. I had to reflash everything from bootloader.
Funny thing is: it just has downloaded and installed an OTA update. With open bootloader.
I ran into this issue yesterday when a bad flash caused the infamous "no bootable A/B" error. After I resolved it and install TWRP I kept being rebooted back into TWRP. The 3.2.3-0 version resolved everything. I really do believe 3.2.3-1 is a bit buggy. I mean it works, but once you really start to use it more than the average user, you start to notice little things.
I too had this same issue. Eventually realized that updating TWRP by flashing zip from TWRP caused it. I had to flash stock boot partition, then follow the process for flashing TWRP as if you are flashing it for the first time (first boot into TWRP and then flash the corresponding zip). This resolved the issue.
Hi,
maybe someone here can help me or point me in the right direction for a guide. That would be much appreciated!
I have a Oneplus 3T (A3003) that I flashed to LineageOS 14.1 with Magisk-Root a while ago.
I have been stuck on 14.1-20171005-NIGHTLY-oneplus3 for a while now, because since then, whenever I tried to do a nandroid backup from within TWRP, the backup failed because of some kind of error on the data partition (I believe). I haven't flashed a new version since then and haven't come around to it until now, because everything ran very smoothly. :silly:
Since I would like to switch to a more modern ROM (I was thinking of going back to Oxygen OS (5.08)) I started playing around with it yesterday and noticed that TWRP (I think 3.2.0) would not start anymore. It will always get stuck on the logo screen.
I then tried to flash a new version (3.2.3.1) through the Official TWRP app. It still got stuck on the logo screen and I tried flashing 3.2.3.0 after reading about problems with 3.2.3.1 but the results were the same.
Can you please tell me how to get TWRP working again and how to flash OxygenOS 5.08 on my 3T or point me to the neccessary guides?
Thank you.
Data about the phone:
ONEPLUS A3003
Android Verson 7.1.2
LineageOS Version 14.1-20171005-NIGHTLY-oneplus3
Security Oct. 5th 2017
Baseband MPSS.TH.2.0.c1.9-00102-M8996FAAANAZM-1.89286.1.99649.1
Kernel 3.18.31-lineageos-g0036392...
As OOS implies enforced encryption of data partition, going to an from it can be a bit tricky. Simplest way is by wiping using Qualcomm factory restore tool and then just OTA upgrade or flash latest OOS zip.
Skickat från min ONEPLUS A3003 via Tapatalk
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Click to expand...
Click to collapse
That worked, thank you. Yes, my data partition is/was encrypted.
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
r_wraith said:
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
Click to expand...
Click to collapse
The OOS zip includes the firmware. Custom ROMs don't because they use the OOS firmware. The firmware is stored in separate partitions so it isn't affected by wiping the system and data positions.
Since you're coming from Los 14.1 you'll need to do the following in TWRP:
- take a backup of your current system
- do a factory reset to clear the data partition without losing the files stored on internal storage
- flash the OOS zip file
- flash Magisk 18.0 which will root the phone as well as prevent TWRP from being replaced by the stock OOS recovery
Sent from my OnePlus3T using XDA Labs
Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
ajadamjones87 said:
Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
Click to expand...
Click to collapse
your devices is encrypted try flash other custom rom first then try revert to stock hope it help u out
Thanks very much for your response. Based on your advice i tried to flash the latest Kraken 11 Vanilla rom from this fourm, however after installing via TWRP now i can't even get into recovery anymore, just goes straight to fastboot.
Any other suggestions please?
I have now managed to get back in to TWRP and tried flashing lineage latest rom but still i am stuck in a boot loop taking me to fastboot this time.
Please can someone help suggest hwo i can get my phone working agian. At this point i dont care which rom i end up (custom or stock) with as long as i can get it to function again
If your device is rooted, you can NOT update the system using the OTA (over-the-air), or the device will be stucked in bootloop.
If your device is rooted, you need to update the system MANUALLY, using the fastboot or spflashtool.
I suggest to update the system using the fastboot.
Now, you need to flash the whole MIUI again, except userdata and you will have your device back.
For anyone with a asimilar problem i eventually managed to fix my issue by using miflash tool version 20180528 and flashing merlin_eea_global_images_V12.0.10.0.QJOEUXM_20210413.0000.00_10.0_eea_c4a9d5d7fc fastboot version which i downloaded from the xiami site.
I had to try this multiple times because the extraction of the file did not seem to be correct on the first attempts.