Hi everyone,
Frist I have to say : my engish is bad, I'll do my best to understand and to be understandable.
Maybe someone has had the same problem as me before, but I haven't found or understood the solution.
Here it is :
After following tutorials, I installed Lineage OS (17.1 or later) on my samsung galaxy S7. But, during the first start (and all others), the lineage OS logo loads for about 3 minutes, then reboots on TWRP. I can't run the OS I want to.
When reinstalling an operator rom, it is clearly displayed that the S7 is rooted, but the OEM unlocking is locked (when I switch the button, it immediately returns to the off position, even if I wait 7 days or more without restarting the smartphone)
How can i fix it ?
Thank you for your attention
Hello,
<what SoC have you ? qualcomm or Exynos ?
Hello,
I have the G930F, Exynos I think.
Related
Hello guys,
I think I cracked up my Zenfone 2 551ML completely and I don't even know why..
I just wanted to flash android 6 stock rom instead of 5.0 which I had installed.. and now my device does nothing anymore. It just shows up the asuslogo white background black color. but then nothing. YES i have unlocked my bootloader and I think I destroyed my bootloader.
I've tried EVERYTHING I could find on the web
I found this xfstk tool to reinstall my bootloader but it doesnt work it says: "Firmware download completed. Continuing to OS..." and then my phone restarts showing the asus logo and doing nothing. and the timeout runs out and my device is not detected in device manager under IntelSoC anymore. it only detects my device when I power it off and then power it on but only for a few seconds then it disappears in device manager again..
I'm so frustrated I don't know what to do. I did everything as in the instructions. all drivers are installed...
What shall I do to get it back to life (except bringin it to a support center cz I won't do that).
I was in same situation and with this guide i got it work again
https://forum.xda-developers.com/showthread.php?p=68477856
Be sure to set the correct address in xfstk 0x80000807 (4 zero after first 8). some guides here showing a wrong address with 5 zero.
Further i did not used AsusFlashTool, i made all steps manually as described.
Good luck.
I made an account just to ask this question because I’m honestly at a loss lol I’ve been reduced to using my girlfriends old iPhone and I miss my G4 ?
Anyways I recently had installed TWRP on my G4 along with the most recent version of Lineage OS on my phone. Not too long after that a new build came out so I updated my phone but I lost root access after that. I tried to root it again by flashing Supersu using TWRP but I guess I messed up a step along the way because afterwards my phone hasn’t been booting properly. It stays stuck at the animation screen after the LG logo appears.
I’ve tried to access recovery mode using the buttons on the phone but it doesn’t work. The only thing I can do is enter download mode but even then when I plug in my phone to my computer it doesn’t recognize my phone.
I feel like I’ve searched everywhere for answers but I’m clueless right now lol I would really appreciate any advice or help! I wanna get back to using my Android this iPhone isn’t the same ? I can provide any other information as needed.
See my answer in your original post:
https://forum.xda-developers.com/tmobile-g4/help/soft-bricked-g4-attempting-to-root-t3688296
.
Hello All,
I have Honor 8 Pro from 1 year now and i have been using Custom ROMs (Thanks to the Developers here) from very long. I was using OpenKirin ROM and then when Android P was release I used FFW to get the latest one and tried to upgrade the phone (thinking that i know everything ).
And the result was catastrophic! Now my phone only boots to recovery mode and if i try to do recovery, it fails.
Current status (Attached Screenshots for reference):
Bootloader locked : says "PHONE locked"
Tried HCU: cannot see any phone info other than Serial number
I have DC-Phoenix+HCU 3 days pack. So please let me know if something can be done to revive my phone. Please let me know if someone can help.
Hi, did you recover your phone finally.? Actually mine also stuck with same problem but the only difference is my phone status shows phone BOOTLOADER Unlock, FRP - UNLOCK.
Unable to do anything but am able to flash twrp and have Access in twrp but unable to flash anything coz all partitions are deleted. Shall I keep any hopes.??
This is old but it might help.
https://forum.xda-developers.com/honor-8-pro/how-to/unbrick-device-revert-to-stock-complete-t3802298
Hi all, I put you in situation. I recently acquired a xiaomi terminal, but the problem and what I like least is that the phones use their own systems, so I ventured to install a custom rom. For this I had to wait a week to unlock it with the miunlock. My surprise has been that after unlocking it and installing twrp, when installing the custom rom of aosp extended it remains in the redmi logo and in loop. I have also tried another custom rom called pixysos, both look great but they give me the problem and I do not know if it is my fault about how I installed twrp or what happened to me, I have followed several guides and I have done the same. In fact, when I installed twrp and started the xiaomi system and returned to the recovery instead of loading me, twrp loaded the xiaomi recovery. What could have happened to me?
Sorry for my bad english
I got an miui 12.0.1.0.RCOINXM update after which phone started to randomly reboot, especially when there was some drop down notification or call.
So I decided to install custom rom. I tried to install Pixel Experience Recovery but that was giving "System is destroyed press power button to shutdown". I fixed it by flashing orange fox but using orange fox pixel experience got in boot loop. So I installed Pixel Experience Recovery from orange fox recovery and the used ADB to sideload pixel experience which worked and I setting up my phone but suddenly I get a notification and the phone reboots which is similar behavior to miui 12.0.1.0.RCOINXM. is there some thing else that I can change like kernel or something which can resolve this problem.
I am using PixelExperience_ginkgo-11.0-20211216-1154-OFFICIAL.zip
pls help
PS : the phone remains in boot loop if not plugged in charging and idk why but fastboot logo didn't change to pixel experience's
GundamSierra said:
I got an miui 12.0.1.0.RCOINXM update after which phone started to randomly reboot, especially when there was some drop down notification or call.
So I decided to install custom rom. I tried to install Pixel Experience Recovery but that was giving "System is destroyed press power button to shutdown". I fixed it by flashing orange fox but using orange fox pixel experience got in boot loop. So I installed Pixel Experience Recovery from orange fox recovery and the used ADB to sideload pixel experience which worked and I setting up my phone but suddenly I get a notification and the phone reboots which is similar behavior to miui 12.0.1.0.RCOINXM. is there some thing else that I can change like kernel or something which can resolve this problem.
I am using PixelExperience_ginkgo-11.0-20211216-1154-OFFICIAL.zip
pls help
PS : the phone remains in boot loop if not plugged in charging and idk why but fastboot logo didn't change to pixel experience's
Click to expand...
Click to collapse
PixelExperience_ginkgo-11.0-20211216-1154-OFFICIAL.zip is for the original Redmi Note 8 (ginkgo)
Judging by your MIUI version (if i remember correctly the new Note 8 ships with MIUI 12.5), you are in the wrong forum, the original Note 8 forum is here.
OR
You have installed a Note 8 (ginkgo) rom to a Note 8 (2021) (biloba) witch is not compatible with the new note 8.
Thanks for reply Aninuscsalas but No my redmi note 8 is 2019 edition and even after install correct roms even downgrading the same issue persists
I think as my device is A partition only devices [Non-A/B] there might have been something wrong during the update process and that might have made some problems.
Here is my partition table can anyone pls confirm if this is Ok?[in attached]
GundamSierra said:
Thanks for reply Aninuscsalas but No my redmi note 8 is 2019 edition and even after install correct roms even downgrading the same issue persists
I think as my device is A partition only devices [Non-A/B] there might have been something wrong during the update process and that might have made some problems.
Here is my partition table can anyone pls confirm if this is Ok?[in attached]
Click to expand...
Click to collapse
Sorry i can't help. (I know almost nothing about phones.)
But if your phone is the 2019 version then you are in the wrong forum.
Maybe someone in that forum can help:
https://forum.xda-developers.com/c/redmi-note-8.9200/