Hi,
last week I successfully installed LineageOS as of March 15 on my OP6 and it worked perfectly.
This morning, I applied the system update to the latest version as of March 22. It took a long time to process (about 5 minutes), then rebooted as usual, but then surprisingly stuck in Crashdump mode.
After some switching off and on again with the same result, I found I still could boot into recovery by VolDown + Power (it’s the simple lineage recovery, not TWRP).
Since then, I tried several times to reinstall both Lineage versions as of 15th and 22nd the usual way, but the phone never would boot any system. The recovery works perfectly, system can be flashed by ADB sideload and reports success, but after rebooting from recovery into system, it either runs into Crashdump or back into fastboot.
Bootloader is unlocked.
I have applied the copy-partition tool to make sure there is no bad software in the other slot but that didnt help either.
I have done factory reset / format all and re-flashed Lineage (latest and older version) but same result - fastboot or Crashdump.
Any hints what I can try to get a working Lineage again?
--ks
Update: It was possible to flash OxygenOS by MsmDownload, which booted perfectly and is running through its setup procedure now. Though I prefer LineageOS by far, I won’t switch back unless I am sure this won’t happen again
Browsing a bit further through this forum, I got the impression this is quite common on OnePlus phones from OP6 on, and so might happen at random intervals even with the manufacturer’s OS. In other words, a built-in fault. I want my wonderful OP 5T back
--ks
Related
Hi all,
well, to be honnest I already posted my story in the help thread but no answer came so I try with a new thread
We'll see if I'm luckier this way !
a few weeks ago I broke my screen and decided to change it myself.
Everything went fine (even restarted successfully my phone before applying the tape to fix the screen) until I finally tried to restart my phone after the repair is done.
Since then I'm not able to turn on my phone
Holding the power button starts fastboot mode, UP + power doesn't do anything and DOWN + power enters recovery. Weird !
Another weird thing: it only works if I'm not plugged. When I'm plugged nothing ever happens.
I suspected I could have damaged buttons or cables. I have looked carefully but nothing appears to be broken.
Here is what I already did without any result:
- I had access to the original recovery so wiped the cache
- I tried to recover the phone but that did not work so
- I installed twrk using adb (like here)
- and then installed the rom as explained here (I used the last release here, so it should be cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip). It seemed to work but finally no, same situtation
- I tried this but so far not able to get the qualcomm port listed once the phone is on. It may be related to the fact that I have to unplug to boot it but I always got a Android bootloader interface listed.
Any idea someone ?
Thank you very much for your help !
Did you try to "fastboot reboot" while in fastboot mode?
Try flashing a CM14 rom. Mine came with CM12 so I tried flashing back to CM11 and I did flash it successfully through Fastboot but alas it won't boot. The boot logo loads but then I'm introduced to a black screen.. So I flashed back to a (at that time the latest stable) CM12.1 but same result. And I got worried. Then I decided to flash a CM13 rom which was a beta build (at that time newly released Android 6) and it booted into it alright! So I suggest flashing a CM14 and let me know how it does.
The problem seems be much deeper than just a broken screen. It may sometime affect the chipset of the cellphone.
For that we can't do anything.
For now you can try the following things :
1 . Flash the latest Cyanogen Firmware from the same place you have downloaded the snapshot cm13.
2. Flash recovery (TWRP) using adb.
3. Wipe
-System
-Data
-Cache and Dalvik Cache
4. Flash the latest Cyanogen Rom .
5. Boot into recovery.
6. Flash some gapps as per the Android version.( Open Gapps I recommend)
7. Boot back to recovery .
8. Boot into System.
This is the max you can do for now.
You can also check device forums for recovering from a bricked device post.
Go through the post and check if any symptoms matches yours. You'll find the answer right away.
And the last option you can do is going to service center, they will charge you mostly (even if in warranty as you have yourself tampered hardware of the phone.)
Hope it will help. Thanks
Hello,
I was running SailfishOS on my H3223, but I decided to go back to Android. I used the EMMA tool, and restored the latest "service" to the device. Everything worked perfectly. Then, I flashed Lineage 17.1, and again, everything worked, and I used the ROM for several days until I noticed that my GPS wasn't working. The latest firmware version available in the EMMA tool was 50.1, so I figured that must be the problem. I used XperiFirm to download the H3223 Customized US firmware which is 50.2, and then I used newflasher to flash it. Everything worked perfectly, including the GPS.
This is where the problem started. I then tried to flash Lineage 17.1 again. The flash completed without errors, but once I reboot it, I just get a black screen. If I change the volume, the volume dialog shows on the screen, but nothing else - it's like the initial setup has frozen, or the launcher failed to start or something. If I force it to reboot, it hangs on the lineageos boot animation. Since then I've tried using EMMA to restore, I've flashed a few different firmware's using newflasher. Every time, I get the same results - the Sony firmware works perfectly. Anything else I try and flash boots to a black screen. The volume dialog will always show up. If the ROM has ADB enabled, and I plug in a cable, the ADB authorization window will show, but otherwise the screen is just black. Forcing it to reboot either hangs on the boot animation, or boot loops. I've tried flashing Lineage 16.0, Lineage 17.1, AlaskaLinuxUser's AOSP 9 and 10, and all behave the same.
I feel like I have to be missing something simple, because any version of a Sony ROM that I use works perfectly.
Any ideas?
I got my Nokia 3.1 in a bit of a weird situation trying to flash the stock ROM. I feel like it's a lost cause, but since I can still boot in recovery mode, there may still be a solution, I will explain in case someone can help.
It started when I tried to update from Android 8.0 to 10.0 (none of the previous OTA updates had worked and would always reboot in Oreo 8.0). This time, it didn't work and got the phone stuck in a boot loop.
The phone is still under warranty, but because I bought it overseas and there's no Nokia care centre here is New Zealand, I had no option but trying to repair it myself.
A wipe/factory reset didn't help, but after changing the active slot from B to A (using fastboot), it booted again in Oreo 8.0. Only problem is that I could no longer start a fresh Oreo 8.0 install without updating first and since all updates failed, I was stuck.
I suspect slot B is damaged or corrupt, hence the impossibility to update. To check it, I switched back the active slot to B after a factory reset, and that was not a great idea, the phone wouldn't even boot and looked hard-bricked.
But I still managed to use SP tool to download firmware, so I did that with the original Nokia 3.1 stock ROM (ES2).
However, I could not flash all files, I'm not too sure why.
I had the error message:
ERROR: STATUS_SEC_INSUFFICIENT_BUFFER
Verified boot is enabled
Please download signed image (sutinfo-verified.img) or disable verified boot
I didn't know how to do either of these, so I skipped the three problematic files: sutinfo.img, systeminfo_a.img, and cda_a.img (not sure what they do?).
It worked and un-bricked the phone, but it now boots to recovery mode only. What puzzles me is that I also no longer have access to fastboot, even when I reboot to bootloader (as if it skipped bootloader and went straight to recovery). I suspect it is because it still boots on slot B but I don't know how I can check that or change it back to slot A without fastboot access.
I tried using adb: adb shell getprop ro.boot_suffix but although it can see the device, it failed because it says device is unauthorized. I've tried all the fixes for this I found, to no avail.
So that's where I am, able to boot to recovery (but with adb unauthorized), able to flash firmware (except those files that must be signed), and unable to access fastboot.
I'm giving up hope that it's repairable, but I'd love to at least understand what happened, if someone has any idea...
Sorry for the long story...
Hello,
I tried flashing LineageOS for my OG Pixel 2 XL because the security updates stopped. I managed to flash it , but then couldn't fit the GApps on it because the system partition was too small. Long story short I tried various methods of increasing it (even though TWRP no good) & including a format command. (Which started this issue)
Now when I try to get back into TWRP, it's just stuck at the teawin logo I can't actually get in anymore.
I also fastboot flashed the twrp image to see if that got me past the logo, but it's not still stuck.
I've pushed the full OTA image of 11 back onto it, but it's not listed any longer in fastboot devices even thoughthe driver I previously installed is still there. (Android composite ADB interface)
It's listed in ADB devices as recovery. Did I push too much? I should have just flashed back to stock when I saw that the Gapps didn't have enough space, but wanted to press ahead. The power button takes 1-5x tries to work, the screen is cracked with circuits exposed in 3 different places, it has two thick horizonal white lines on the right side because of those cracks. (which didn't appear until months later while on vacation in high elevation...) I guess I'm attached to this phone and want to say forget the security updates I'm happy going back to stock and just keeping it until it dies.
What else can I try? If I'm out of luck, I'm deciding between a 4a and an SE. (Apple at least gives 5 years of updates.)
Thanks!
https://lineageos.org/
Update I managed to get flash.all working and flashed it back to stock.
Is there no way to get LineageOS 17.1 & the stock Open GApps to have enough space on the system partition? I need those apps for work.
Thanks!
The short story is that I used the MSM Tool to try reset my OP7 Pro completely back to stock. I have the US/Global variant (GM1917). The image I used is the guacamole_21_P.31_201105 (found on this thread under GM21AA tools -> Android 10 -> OOS 10.3.7: https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/)
The MSM tool completed its work with no errors and the phone rebooted after it completed. On the first reboot it spun on the red dot and white circles screen for a few seconds before rebooting itself again. On the second reboot it stayed on that spinning dot screen for 15+ minutes, after which time I powered the phone off. I can get into fastboot/recovery. My understanding was using the MSM tool should basically completely reset back to the factory image, am I doing something wrong? Is there anything else I can do at this point or is the phone just hosed?
Longer history
The phone was originally unrooted, stock, locked bootloader, etc. No changes done by me. The phone started having a few random reboots yesterday (and some games I were playing started throwing random security violations or just outright closing themselves). This morning the phone itself started rebooting every minute or two. This had also happened back in October and only after about 4 or 5 factory resets did it finally stabilize itself. Instead of going the same route again I did some search around searching around. I decided I'd try to replace the kernel with arter97's (https://forum.xda-developers.com/t/r64-arter97-kernel-for-oneplus-7-series.3952578/) since it seemed like the OS itself was randomly crapping out. I unlocked the bootloader, installed TWRP (twrp-3.5.0_9-0-guacamole.img) and Magisk (latest version) first in the same recovery session with no reboots in between. I rebooted and was having a bootloop issue at that point, but figured I'd proceed with the kernel update as well to see if that resolved it. When that also didn't help I decided I'd try to go the MSM route.