Related
To make a long story short, after unlocking bootloader and rooting a friend of mine thought it would be a GREAT idea to install Layers on a stock ROM... after that my phone goes black after the Motorola screen. Ended up wiping the OS off the phone and didn't have a chance to do a nandroid backup... I can get into TWRP just fine... is there anyway to get this thing working again... btw i tried the WIndows Tool with no success and tried it on a Mac with Terminal with no luck... Any ideas?
What exactly have you tried so far. The solution to issues like this is typically to get hold of a factory system image and ADB reflash the system partition while in fastboot mode.
See this post http://forum.xda-developers.com/showpost.php?p=63074207&postcount=89
The same happened to me and I if you are able to boot into TWRP, then you can follow the exact steps to re-flash the image files and be able to restore to factory stock.
Hey guys so my phone appears to me to be bricked. I have a rooted angler on stock 7.0.0 (NBD90X, Oct 2016). I have ElementalX kernal.
A few weeks ago I was looking in to putting on MultiROM. After I flashed the custom TWRP recovery for MultiROM, the recovery wouldn't work. It just goes to the TWRP blue startup screen and freezes. I have been procrastinating on flashing a functioning recovery ever since. I know, I'm an idiot. Lesson learned. Well the November security update was pushed to my phone a few days ago. I ignored it. Last night I wanted to see if the update included 7.1 or if it was just security update, so I tapped on the update notification and it automatically downloaded the updates without prompt (which I did not want to do.)
Well an hour later my phone died. When I plugged in to the charger, it immediatly started up by itself and booted to the non-functioning recovery and froze. It does this every time I try to boot the device now. I booted in to the bootloader and tried plugging in to my PC to flash a working recovery, but the device will not get picked up by the PC anymore. I don't believe it's a driver issue I use adb all the time with this same device and pc.
Also want to add, factory reset from bootloader went to google startup animation, but then just shut off as soon as it was done. Also, when I select shutdown from bootloader with it plugged in to charger, it will turn off and stay off but does not appear to be charging in any way.
Well that's the backstory. Any help you all can provide is very much appreciated. Turns out the battery in my backup phone is only good for a couple hours anymore. You all know how helpless we are without our phones, ha! Please help! Is it bricked?
I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.
RoyJ said:
I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.
Click to expand...
Click to collapse
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Edit: If you can boot to bootloader your device should be read with 'fastboot devices' - if it isn't, delete any Android / Nexus / Google drivers. **Reboot your PC** and install them again. After you install them again reboot your PC one more time and try again.
RoyJ said:
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Click to expand...
Click to collapse
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.
Nebul0us said:
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.
Click to expand...
Click to collapse
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.
RoyJ said:
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.
Click to expand...
Click to collapse
Okay so I left the phone on the charger with the frozen screen in twrp multirom edition. After that rebooted in to the bootloader. I then selected the factory option. If loaded the google animation like before, but this time actually booted up the system. The notification bar had two diagnostic tools that said tap to run...one was called sims i think? Anyways I held power button and did a hard reboot. It booted up fine. I then used twrp manager to install 3.0.2.2....then i used fastboot to flash 3.0.2.3 that i had a copy of. Things seem to be working fine now. Close call. I'm not sure what the factory option is in the bootloader, but it's not factory reset and it was the only way I could boot. I think the phone was trying to boot to recovery to install the latest updates and I had to boot to factory to get it out of "update mode," if you will...
Does anyone know what the factory option is in the bootloader?
Thanks for your help RoyJ
Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Factory options is meant to restart the system with some manufacturers apps available just so you can test certain functions of the phone, mostly to see if all sensors and hardware are working properly.
Hi,
I unlocked the bootloader of my H870, installed TWRP 3.1.1.0 and SUPERSU. Everything was working great untill I decided to restore my system defaults to make a fresh start with my G6. After choosing the option to restore system defaults, my phone rebooted and it booted into TWRP. I rebooted my phone and it kept doing this all the time.
I decided to look for a stock ROM and flash that ROM.
I succesfully flashed the "LG-H87010f-Flashable.COMPLETE.zip" ROM (from autoprime's post) trough TWRP. But this did not work. I even wiped all the data from my phone (even system) and flashed the ROM again; still nothing.
Before having this issue, I had the same Baseband version, Kernel version, Build number. Only the dates and the Software Version are different.
I had the V10b-EUR-XX Software Version installed on my phone. I see this is the 10f version. I guess this should not be a problem right?
After this I took these steps solve this issue:
1. Downloaded new LG Mobile Drivers (LGMobileDriver_WHQL_Ver_4.2.0)
2. Downloaded and installed LGUP. LGUP doesnt recognize my phone as a LG G6 and this method did not work for that reason.
Fastboot mode is working on my phone; I can reboot my phone trough the commandline on my PC and things like that . However, my PC is not recognizing my phone as a LG G6 device in Fastboot mode.
My PC recognices my phone as a H870 when in TWRP. In Fastboot mode it recognices my phone as Android Device.
3. Installed LG Bridge for more drivers; did not work either
4. Downloaded Uppercut, but it doenst work without LGUP.
4. Looked all over the internet to find a Stock ROM in .zip or .img format; found nothing
5. Downloaded WindowsLGFirmwareExtract-1.2.6.1 and tried to extract the H87010d_00_OPEN_EU_OP_0327.kdz file. I extracted it into .bin files, but they were not usable. After that, I combined these .bin files into a system.img file. But that .img file was bigger then 5 GB and for that reason it was not usable to flash trough Fastboot or TWRP.
7. Looked for other methods to obtain a H870 Stock Rom, including another extraction method, but I cant figure out how to do this.
I have spend countless hours on this problem, but I cant find an usable H870 stock rom to flash my phone with.
Is there someone that can help me out with this problem? Im willing to donate some € if someone helps me to get my phone working again.
Really hoping for a kind person to help me out and provide me solution for this issue.
Thanks in advance
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
autoprime said:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
Click to expand...
Click to collapse
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
autoprime said:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
Click to expand...
Click to collapse
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Swizzle82 said:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Click to expand...
Click to collapse
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!
Thanks a lot for your help guys! I really apreciate it! :victory::victory:
autoprime said:
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.
Click to expand...
Click to collapse
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
RoyalD said:
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!
Thanks a lot for your help guys! I really apreciate it! :victory::victory:
Click to expand...
Click to collapse
Probably because you already did all the flashing prior to. Glad it worked. This happened when I first got my V20 and was stoned not thinking. I reset using the in phone option and it caused twrp bootloop. I too learned the hard way.
Had the same issue, fixed it, thanks.
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
matthew33 said:
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
Click to expand...
Click to collapse
Flash a firmware trough LGUp, or flash again the last TWRP available trough fastboot.
RoyalD said:
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:
Click to expand...
Click to collapse
Please help, i have the same problem and nothing, what exactly is a boot to the hard side? I ve tried to power off the phone, press vol down and power, realase power 1 sec, press again...but nothing...still boot on twrp...
Well, I finally solved it with lgup and uppercut... what a nightmare.
matthew33 said:
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
Click to expand...
Click to collapse
Flash stocl .kdz with uppercut and lg up
Saved my G6!
Swizzle82 said:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Click to expand...
Click to collapse
Great tip @Swizzle82! It allowed me to restore my LG G6 after bootloop. It had not been detected by PC, and this hardware reset helped!
Hi, all
If I understand, and to sum up :
I rooted my LG-G6 few weeks ago, and intall TWRP. When OTA wants to install official update, the reboot stops in TWRP mod, so ... failed :-/
Is the solution to flash through Uppercut/LGUP with a .kdz file, without risk of brick the phone ?
Thx
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
auxillium said:
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
Click to expand...
Click to collapse
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
marvelljones said:
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
Click to expand...
Click to collapse
What do you mean by "hitting the power button and continue to boot"? When I hit the power button on the "Decryption unsuccessful" screen it just locks and unlocks like normal, but stays there.
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
auxillium said:
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
Click to expand...
Click to collapse
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
marvelljones said:
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
Click to expand...
Click to collapse
Will this allow me to install magisk without a factory reset?
auxillium said:
Will this allow me to install magisk without a factory reset?
Click to expand...
Click to collapse
I didn't have to, but I can't guarantee it will work for you. I had previously factory reset my phone but at the time I sideloaded Magisk I had been using the phone for at least a week. Just make a backup of everything first to be safe. *edit* I am using the beta version of Magisk (16.4), not sure if that's making a difference.
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
Did you get twrp installed? Wipe data by typing yes after flashing?
dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
You can follow this. If you want to install lineage os and want Google service make sure follow the "non gapp version" under installation method.
Havoc Flashing Notes for OnePlus 6 /6T from OOS 11 [Using TWRP Recovery]
1. Clean Flash : 2. Dirty Flash 3. Update oos base 1. Clean Flash : 🔊 Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; we're going to format the data partition and you're going to lose everything from internal storage. Basic requirements ○...
telegra.ph
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my 6T.
dequadim said:
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my
Click to expand...
Click to collapse
OnePlus definitely didn't do anything to make it harder. You need to fastboot boot twrp.img then flash the twrp installer zip. I'll attach both In next post. Reboot to recovery. Then install OOS, twrp installer, reboot to recovery. Install oos again, twrp installer again, reboot to recovery. Now install lineage, twrp installer, reboot to recovery. Install lineage again, twrp installer again, reboot to recovery. Factory reset and wipe data by typing yes. Boot to system
The img is for fastboot boot
The zip is for installing in twrp
Thanks for your reply.
I'm still wondering how to speed up the boot.
dequadim said:
Thanks for your reply.
I'm still wondering how to speed up the boot.
Click to expand...
Click to collapse
If everything is installed correctly it won't take long to boot
Brettroth said:
If everything is installed correctly it won't take long to boot
Click to expand...
Click to collapse
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
If you can't fastboot boot into that twrp on a11 without crash dumping there is something really wrong
If you can't fastboot boot into that twrp on a11 without crash dumping there is something really
dequadim said:
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
Click to expand...
Click to collapse
You sure you didn't try 3.6.0_9?
Clearing your cache might help with current boot. But once you install a new os everything will run smooth like it should
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
dequadim said:
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
Click to expand...
Click to collapse
That twrp version always will crash dump on a11. Use the one I sent
I followed these steps:
after having managed to make MSM Download Tool detect the phone in EDL mode, I proceeded by reinstalling OOS v9.0.13, after which I reconfigured the phone and restored the apps backup stored in my Google account.
Later, I don't remember the details well, I received the update notification for OOS v10 and later for OOs v11.1.2.2.
I don't remember exactly where the boot started to stretch, however this is more or less the process I followed to bring my 6T back to life.
Brettroth said:
That twrp version always will crash dump on a11. Use the one I sent
Click to expand...
Click to collapse
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
dequadim said:
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
Click to expand...
Click to collapse
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Brettroth said:
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Click to expand...
Click to collapse
Keep your finger crossed...
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
dequadim said:
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
Click to expand...
Click to collapse
Or you could use USB OTG. Or a PC and use adb sideload