Related
So I installed a version of the P9 OS EVAL09 from here - https://forum.xda-developers.com/p9/development/bluewei-test-crossflash-to-l09-c432-t3608270 the B387 version.
Prior to this, I was running unofficial CM 13 with TWRP installed, and it worked mostly fine.
The B387 .zip had a .update log which I was supposed to install via SDcard upgrade or something like that, however instead I removed a few lines from the update binary and installed via TWRP (in hindsight, probably what caused this problem).
Since then, I have launched into the new ROM with the purpose of updating, then moving to the unofficial Lineage OS.
However, I have encountered the biggest problem which is that, when I tried to reaccess TWRP it would automatically redirect to Huawei eRecovery, which does not allow me to reset/upgrade (as it says package info isn't correct).
I then tried to redo the process of flashing TWRP via ADB fastboot, and then it says that writing recovery has failed.
I can't download the stock ROM from huawei hicloud from the thread here - https://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 - as it always says the website is unavailable.
So far, the current OS installed is unusable, and I do not have any custom recovery software. If I can get TWRP to work again, then I should be ok as I made backups before.
edit 2018-01-18: The fix is to make the dload folder in the sd card and hard flash the ROM, which will get me back to a working stable version.
So I have a lineageOS on my redmi 4x and a twrp recovery, but whenever I try to flash something new from TWRP (I tried magisk and some other thing) it completely deleted my OS, I had a backup so its not a problem, but how could I flash something new again? Should I wipe something or what?
Use Latest 3.1.1/3.2.0 TWRP from official TWRP page. It's a Recovery Problem.. if you're On N go for latest 3.2.0 and Also check if you're Device is not encrypted (like you can't see Internal storage In TWRP) Clean Flash ROM, If anything Doesn't work... This is strange, I heard this issue the first time. Maybe Recovery Problem, Try and Reply.
SleepyWeeb said:
So I have a lineageOS on my redmi 4x and a twrp recovery, but whenever I try to flash something new from TWRP (I tried magisk and some other thing) it completely deleted my OS, I had a backup so its not a problem, but how could I flash something new again? Should I wipe something or what?
Click to expand...
Click to collapse
If your Problem solved report back
I was running Sultan's latest version of CM which was discontinued somtime last year. So, I decided I should upgrade to the latest Sultan Lineage OS version. I updated TWRP to the most current version, took a Backup of the system using the new TWRP (so I could restore back to a working phone). I also downloaded the Sultan version of Lineage OS (and this is where my mistakes began). I accidentally downloaded the incorrect version for the OnePlus 1 and not for the OnePlus 3T. I should have done this from a computer and not from the browser on my phone to prevent this mistake.
So, in TWRP, I cleared cached and the system partition, then tried to install the Sultan Lineage OS. TWRP correctly told me that it was the wrong version for my phone. Okay, no problem. Then, my fallback also failed. I tried to restore the image that I had backed up of my working phone and the image loads properly. However, when the phone is rebooted, it is stuck in a bootloop. I can get into TWRP and the bootloader, but that's all I can do.
What are my options now?
(1) Can I use adb fastboot to copy over the correct version of Sultan's Lineage and go to that?
(2) Why is my recovery image not working?
I essentially have a phone that seems to be bricked. I hope that this is not the case. Any help is greatly appreciated.
weaponG said:
I was running Sultan's latest version of CM which was discontinued somtime last year. So, I decided I should upgrade to the latest Sultan Lineage OS version. I updated TWRP to the most current version, took a Backup of the system using the new TWRP (so I could restore back to a working phone). I also downloaded the Sultan version of Lineage OS (and this is where my mistakes began). I accidentally downloaded the incorrect version for the OnePlus 1 and not for the OnePlus 3T. I should have done this from a computer and not from the browser on my phone to prevent this mistake.
So, in TWRP, I cleared cached and the system partition, then tried to install the Sultan Lineage OS. TWRP correctly told me that it was the wrong version for my phone. Okay, no problem. Then, my fallback also failed. I tried to restore the image that I had backed up of my working phone and the image loads properly. However, when the phone is rebooted, it is stuck in a bootloop. I can get into TWRP and the bootloader, but that's all I can do.
What are my options now?
(1) Can I use adb fastboot to copy over the correct version of Sultan's Lineage and go to that?
(2) Why is my recovery image not working?
I essentially have a phone that seems to be bricked. I hope that this is not the case. Any help is greatly appreciated.
Click to expand...
Click to collapse
1. You can either sideload the correct version in TWRP and ADB. Or fopy the file to your internal storage using TWRP and ADB or by enabling MTP in TWRP (under Mount menu) and then flash it. Don't forget to do a factory reset in TWRP as you're changing ROMs.
2. What partitions were included in your backup?
If boot, data, and system were included then I have no idea why restoring it didn't work.
And, when you say "most current version of TWRP" do you mean version 3.2.1-0 from https://dl.twrp.me/oneplus3/ or something else?
Sent from my OnePlus3T using XDA Labs
BillGoss said:
1. You can either sideload the correct version in TWRP and ADB. Or fopy the file to your internal storage using TWRP and ADB or by enabling MTP in TWRP (under Mount menu) and then flash it. Don't forget to do a factory reset in TWRP as you're changing ROMs.
2. What partitions were included in your backup?
If boot, data, and system were included then I have no idea why restoring it didn't work.
And, when you say "most current version of TWRP" do you mean version 3.2.1-0 from https://dl.twrp.me/oneplus3/ or something else?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
(1) I was successfully able to download the proper Sultan Lineage OS version for OnePlus 3T. I have copied that and the latest firmware sited in this link:
https://forum.xda-developers.com/on...t/op3-op3t-unofficial-lineageos-14-1-t3588696
(2) The following partitions were included: Boot, Data (excl. storage), Recovery, System, System Image, EFS. It is unknown as to why recovery failed.
(3) The version is Team Win Recovery Project (TWRP) 3.2.1-0
weaponG said:
(1) I was successfully able to download the proper Sultan Lineage OS version for OnePlus 3T. I have copied that and the latest firmware sited in this link:
https://forum.xda-developers.com/on...t/op3-op3t-unofficial-lineageos-14-1-t3588696
(2) The following partitions were included: Boot, Data (excl. storage), Recovery, System, System Image, EFS. It is unknown as to why recovery failed.
(3) The version is Team Win Recovery Project (TWRP) 3.2.1-0
Click to expand...
Click to collapse
Oh wow. I had to apply the Firmware Update, and now I am running Sultan's Lineage. This is truly exciting. The animated splash/intro screen is still occurring on the phone. This should be great. Thanks so much for your kind assistance.
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.
Hello,
I've installed twrp 3.4.0.1 via fastboot, but after I select yes when i'm asked about erasing my data, the phone just boot up normally without deleting any of my data, but does not enter twrp either. Tried 3.4.0.0 too, no luck. Only 3.3.1.0 worked, but when I try to backup it says something like 'can't mount system partition' and some other errors. I think that version is too old for my rom, so I'm afraid to use it for backup/flash. My phone is LG G6 H870, Android 9, software version V30b. The phone is not rooted, the bootloader is unlocked. Tried to erase cache partition and install twrp 3.4.01 again, didn't work. I can't install Skyhawk or Orangefox becuase I can't use twrp.
Is anybody facing this problem too?
Thanks!
Bootloader unlocked?
Mendoo said:
Bootloader unlocked?
Click to expand...
Click to collapse
Yes
Thelock1 said:
Hello,
I've installed twrp 3.4.0.1 via fastboot, but after I select yes when i'm asked about erasing my data, the phone just boot up normally. Tried 3.4.0.0 too, no luck. Only 3.3.1.0 worked, but when I try to backup it says something like 'can't mount system partition', I think that version is too old for my rom. My phone is LG G6 H870, Android 9, software version V30b. My phone is not rooted.
Is anybody facing this problem too?
Thanks!
Click to expand...
Click to collapse
HI You need to use OrangeFox recovery or SkyHawk. If you plan to go to 10, then you need SkyHawk. And I think SkyHawk is maintained but OrangeFox not.
Links:
SkyHawk https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/H870/
OrangeFox https://forum.xda-developers.com/lg-g6/development/recovery-orangefox-recovery-project-t3943594
jis251 said:
HI You need to use OrangeFox recovery or SkyHawk. If you plan to go to 10, then you need SkyHawk. And I think SkyHawk is maintained but OrangeFox not.
Links:
SkyHawk https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/H870/
OrangeFox https://forum.xda-developers.com/lg-g6/development/recovery-orangefox-recovery-project-t3943594
Click to expand...
Click to collapse
So can I install SkyHawk via fastboot over stock recovery without installing twrp beforehand? I see there are multiple files in the shyhawk zip, should I only extract the recovery img and install it via fastboot? I'm kinda new to this, thanks!
Thelock1 said:
So can I install SkyHawk via fastboot over stock recovery without installing twrp beforehand? I see there are multiple files in the shyhawk zip, should I only extract the recovery img and install it via fastboot? I'm kinda new to this, thanks!
Click to expand...
Click to collapse
HI. It is made to flash in TWRP (same as OrangFox) So I really don't know if that recovery.img flashing through Fastboot works. Never tried, sorry.
Maybe someone knows though.
jis251 said:
HI. It is made to flash in TWRP (same as OrangFox) So I really don't know if that recovery.img flashing through Fastboot works. Never tried, sorry.
Maybe someone knows though.
Click to expand...
Click to collapse
Ok, thanks, I'll try to find a solution, or maybe I'll just wait for the next version of twrp.
You should try installing the recovery and immediately installing any custom rom, when i flashed twrp the first time i had to do it several times cause somehow it got "erased" every time i noot the stock OS.
Ig you don't want to install a custom rom try right after installing twrp and on the fastboot screen to reboot to recovery with (Volume - ) button and power.
I think the idea is not letting the Stock os boot
Also that error. i have the same problem, the only moment it doesn't appear is when you wipe all data with the "Format Data" option inside "Wipe" menu in twrp.
After you boot to the OS once and go back to recovery it will come again everytime you flash something.
Not sure if its a problem or not, because i've dirty installed some updates and also installed gapps and magisk even with that error.
Im currently in A10 using Havoc and NikGapps.
TWRP 3.2.3-0
AlejandroMota said:
You should try installing the recovery and immediately installing any custom rom, when i flashed twrp the first time i had to do it several times cause somehow it got "erased" every time i noot the stock OS.
Ig you don't want to install a custom rom try right after installing twrp and on the fastboot screen to reboot to recovery with (Volume - ) button and power.
I think the idea is not letting the Stock os boot
Also that error. i have the same problem, the only moment it doesn't appear is when you wipe all data with the "Format Data" option inside "Wipe" menu in twrp.
After you boot to the OS once and go back to recovery it will come again everytime you flash something.
Not sure if its a problem or not, because i've dirty installed some updates and also installed gapps and magisk even with that error.
Im currently in A10 using Havoc and NikGapps.
TWRP 3.2.3-0
Click to expand...
Click to collapse
Yes, I know I have to install twrp again every time I let the stock rom boot, but the only version of twrp working is 3.2.3 and I think that was released before the G6 received official Android 9 update, so that's why I'm not very confident using it. I've tried to enter recovery immediately after I've installed it, so I don't think that's the problem.
I have the same problem on the LG G6 H870. I won't get to TWRP. I tried several versions of TWRP and nothing.
Edit.
This twrp is functional:
https://androidfilehost.com/?w=files&flid=289997
After installation using fastboot, restart directly to twrp using power+vol. down.
Finally i've successfully flashed Skyhawk using TWRP 3.3.1, so thanks everyone for advice!
Still couldn't make official TWRP 3.4.0/3.4.0.1 work.
Update TWRP 3.1 to 3.4 problem
Thelock1 said:
Finally i've successfully flashed Skyhawk using TWRP 3.3.1, so thanks everyone for advice!
Still couldn't make official TWRP 3.4.0/3.4.0.1 work.
Click to expand...
Click to collapse
Hi, I don't know if this goes here, I hope you can help me, I update twrp from version 3.1 to 3.4 and now I can't access twrp, how can I fix it?
Hello again, I answer myself, and if it helps someone else, using adb fastboot with twrp 3.2 Melina solves it and twrp works perfectly again.