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?
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
I've had a problem with my phone since flashing Lineage and Gapps in TWRP, something went wrong, it's acting like I have a corrupted version of Lineage with only the basic functions, Gapps is not installed and I've lost root.
The phone is an Xperia Z5, prior to flashing Lineage zip I had successfully rooted the phone, i flashed Lineage and then Gapps, an error appeared saying Gapps had not installed (possibly because it was the wrong version). After that the phone went into a bootloop (Sony logo, battery icon, then restart with red light in the corner). I was able to turn the phone on by holding down the power button for 5 seconds and lineage started up as normal with just the basic apps, I have been using the phone for the last month like this unable to find an answer on the forum. If I was able to connect the phone to PC i could use flashtool to flash the stock rom and start from scratch, but it only charges even though i have usb set to MTP in developer options, it's not detected by PC no matter how many cables I try. Also, it will not install apps from the Play website, it downloads and says app is installed but app isn't shown in list of apps. Can't get into TWRP because it says device is not rooted. When I switch phone off it restarts again and goes into bootloop, have to hold down power button to start it up. I wondered if anyone was familiar with these strange symptoms and knew if there was any way out? My phones stuck in limbo until I can find a way of doing a hard reset but without being able to get into TWRP or connect phone to PC I'm stuck.
Hi and thanks for reading.
My S6 is the 920p model. I had it rooted with Magisk v16.0, stock kernel, no xposed, DRA2.
Let me explain what happened.
Yesterday, I woke up because of a call sound. Once I finished talking, I tryed to unlock my phone using the fingerprint sensor. It was unlocked but suddenly it rebooted. When it booted I tryed to unlock it using the pin (obviousy), but it rebooted again.
I made a few more attempts but no luck, so I booted in TWRP, backed up my data on my laptop and made a factory reset.
Now the phone doesn't finish the boot, it only stays at "Samsung" blinking logo and the led in blue dimming, restarting again and again.
I installed the NexusOS 8.1, it booted, the phone is usable, but this rom doesn't recognize modem, so, no signal (Sprint modem not supported).
Since it works with that rom installed, I tried installing the DRA2 stock firmware wich I had installed at the beginning, but again stuck at bootloop.
Next thing I tried was using .pit file, and flashing one by one bl, ap, cp and csc. It only reached the "Optimizing apps" and rebooted again. I booted into recovery, wiped cache and reached "Starting apps" but, te phone rebooted again.
Right now I'm using it with the NexusOS rom wich is pretty, but with te Ril issue.
So, that's my problem, hope somebody help me.
Finaly solved: I just had to mark (Phone EFS Clear)
Apparently EFS was corrupt. After that, I had to unlock it. It's working properly.
I recently tried to install android 10 (PixelExperience) on my Samsung Galaxy S7 through this guide : wiki.pixelexperience.org/devices/hero2lte/install/. It worked fine for about 15 hours or so, and then it randomely stopped working. (it crashed and would not boot) I could not get past the Samsung Galaxy S7 logo before it would crash and reboot. I tried to reinstall the stock OS, bootloader and recovery, and the recovery works, except for now it wont boot anything (be it the pixelexperence rom, or the stock rom...)
I even tried to load a twrp backup that I took before I changed anything, and it did not work (it had dissapeared)
When I try to do the format option from the recovery, it does nothing.
Does anyone have anything else I can try??
EDIT : Just as I posted this, it randomely worked. All I did this time was 1. Flashed the stock (AP, BL, CP, and CSC) using ODIN, then I flashed TWRP using ODIN, then I flashed the pixelexperience rom via adb sideload.
Now I have a new question. What was happening, and why did this work (I did almost the same thing before) and why did the problem happen in the first place??
EDIT : I still found a problem. The phone works fine in the pixel OS, but it does not see any wifi or bluetooth networks. I tried to reinstall the CP modem driver thing, but it did nothing. It was working earlier though.
TheRuntingMuumuu said:
I recently tried to install android 10 (PixelExperience) on my Samsung Galaxy S7 through this guide : wiki.pixelexperience.org/devices/hero2lte/install/. It worked fine for about 15 hours or so, and then it randomely stopped working. (it crashed and would not boot) I could not get past the Samsung Galaxy S7 logo before it would crash and reboot. I tried to reinstall the stock OS, bootloader and recovery, and the recovery works, except for now it wont boot anything (be it the pixelexperence rom, or the stock rom...)
I even tried to load a twrp backup that I took before I changed anything, and it did not work (it had dissapeared)
When I try to do the format option from the recovery, it does nothing.
Does anyone have anything else I can try??
EDIT : Just as I posted this, it randomely worked. All I did this time was 1. Flashed the stock (AP, BL, CP, and CSC) using ODIN, then I flashed TWRP using ODIN, then I flashed the pixelexperience rom via adb sideload.
Now I have a new question. What was happening, and why did this work (I did almost the same thing before) and why did the problem happen in the first place??
EDIT : I still found a problem. The phone works fine in the pixel OS, but it does not see any wifi or bluetooth networks. I tried to reinstall the CP modem driver thing, but it did nothing. It was working earlier though.
Click to expand...
Click to collapse
You need to ask any questions about a custom ROM on the ROM thread it self so the DEV can answer you.
Why is it happening? Don't know could be a million things. ask the Dev.
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