Background:
The boot-loop happened few days after installing the Arrow OS [Pie]. Below is the link from where I installed the same.
https://forum.xda-developers.com/oneplus-one/development/unofficial-arrow-os-bacon-t3836884
I've tried the following things till now:
1. Tried "Advanced Wipe" via TWRP (only dalvik cache and other cache)
2. Tried "Restore" the back up I had saved for old OS (RR Oreo OS)
3. Tried "Advanced Wipe" via TWRP (wiped everything including system and installed RR Oreo OS again)
4. Tried Flashing CM Stock ROM (cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB) - Currently, my phone is on this ROM.
Please help me on this.
Related
Hi,
I was trying to install lineage os, I had TWRP 3.0.2. I booted to recovery, did factory reset, then wiped dalvik, system, data and cache. Then when i tried to flash os, i got error code 7. I downloaded latest TWRP-3.1.0 and flashed it to recovery, after which my phone is not going to recovery at all.
Please help me in this.
My bootloader is unlocked.
Using FlashTool 0.9.18.6, I flashed "Sony Xperia L C2105 15.3.A.1.17 Generic DE" - FTF, which I downloaded from:
https://forum.xda-developers.com/xperia-l/general/sony-xperia-l-flashable-ftfs-locked-t2560642
Downloaded CM11 from FreeXperia's thread, from that I extracted boot.img and using FlashTool flashed it.
Downloaded CM12.1 from Oliver's thread and moved it into my external sdcard. Using CWM, did a clean wipe (dalvik, cache, data and system), and flashed the zip.
ROM installed and was working fine.
Downloaded CM13 from Oliver's thread and moved it into my external sdcard.
Enabled USB debugging.
Downloaded TWRP 3.0.2-0, from:
https://dl.twrp.me/taoshan/twrp-3.0.2-0-taoshan.img.html
Rebooted into bootloader using adb. And flashed TWRP, using fastboot:
"fastboot flash boot twrp.img"
Rebooted into recovery. The interface was flickering non-stop and the left part was overlapping over the right part and vice-versa, but I managed to factory reset and wipe my dalvik, cache, data, system, sdcard and android secure.
Then I flashed CM13 from my external sdcard.
No errors.
Wiped dalvik, cache and my external sdcard.
Rebooted.
Bootloop.
Rebooted into CM Recovery.
Factory Reset and wiped cache.
Rebooted.
Bootloop.
I have also tested 7.x.x (CM14 and Resurrection Remix) and it also gets me in a bootloop until the battery reaches 0%.
The problem started with Beta 2 of CM13 (anything before it works fine), after I flashed it almost a year ago. I also made a post there at that time about my problem:
"I'm not certain if this is the right thread to ask, and I don't think this qualifies as a bug report, I'm just asking for some help as my phone is stuck on the boot logo forever until the battery runs out (from 90-100% to 0%).
I've previously used CM11, CM12.1 and the previous beta 1 of CM13, but after flashing beta 2 a couple days ago it's just stuck on trying to boot.
The recovery I'm using is TWRP 3.0.2. I wiped my phone completely(the system, sdcard, cache etc). After that I connected my phone to my PC, while on recovery, and copied the ROM zip and GAPPS zip to my external sdcard. I disconnected my phone from the PC. Flashed the ROM and after that GAPPS (Open GApps Platform: ARM / 6.0 / pico). The logs didn't show any error so I wiped the dalvik cache and rebooted the phone. The phone went into the boot logo and now is just stuck there, I waited ~5 hours and it still didn't fully boot after an hour or so the battery ran out. So I decided to do everything again, charging the phone to 100%, wiping the phone completely 10 times(for reasons) and flashing everything the same way(I also downloaded the ROM from a different mirror, and tested both zips for any errors), this time I left it overnight, keeping the charger connected and in the morning it was still stuck on the boot logo. The third time I tried a different GAPPS package(A-GAPPS) and the same result. Can anyone provide some help? Maybe I'm just missing something or being really stupid. I'm sorry for being such a bother."
https://forum.xda-developers.com/xperia-l/orig-development/rom-cyanogenmod-13-0-t3254779/page20
I made this thread in hope of finding out what's causing this. Any help is appreciated.
It's been almost a year and I still have this problem with newer ROMs. Does nobody have any suggestions, anything at all? Is more information required? I'd be happy to give/do anything*, if it would mean getting these ROMs working.
The only error I've noticed is that after flashing LineageOS 14.1, if I try a fully factory reset through the default "Android Recovery" it will fail and I'll get "E: format_volume: failed to open /persist/footer" (This doesn't happen if I do a factory reset through TWRP).
Hey guys, this is my first time here, sorry in advance if I say something wrong or anything.
I just unlock my Redmi Note 3 (SD 650 variant) bootloader via the unofficial way (the miflash tool way, without permissions from xiaomi).
It was done, I already checked the oem unlock status via command prompt, and then I was able to flash TWRP via fastboot.
Then I did a complete wipe of my device through TWRP, and flashed Resurrection Remix and GAPPS.
At first I was getting error 7 and error 6 everytime I flashed the rom, but I managed to fix that through some readings.
The problem is that, I always stuck in bootloop (the RR boot screen).
I tried with LineAge OS, because at first I thought it was a ROM issue, and the same thing happened: it stuck in bootloop (the LineAge OS boot screen in this case).
The step I did was :
TWRP 3.1.1-0 ---> Wipe ---> Swipe to Factory Reset ---> Install ROM and Gapps ---> Wipe Dalvik Cache ---> Reboot System
Note: I also tried without the Wipe Dalvik step before rebooting, same result.
Another thing I tried was :
TWRP 3.1.1-0 ---> Wipe ---> Advanced Wipe ---> then I select "Dalvik/ART cache", "System", "Data", and "Cache" ---> Swipe to Wipe ---> Install ROM, Gapps ---> Wipe Dalvik Cache ---> Reboot System
Note: I tried this one without the Wipe Dalvik aslo, same result.
This phone is my daily driver, so can anyone please educate me on what's happening?
(Yes I know it's not good for beginners to do this by himself on his daily driver, but in the past I have rooted and install custom ROM on my Galaxy S3 Mini...that's why I was a bit confident -.- )
Thanks in advance, I hope I get an answer here.
rioyoyo29 said:
Hey guys, this is my first time here, sorry in advance if I say something wrong or anything.
I just unlock my Redmi Note 3 (SD 650 variant) bootloader via the unofficial way (the miflash tool way, without permissions from xiaomi).
It was done, I already checked the oem unlock status via command prompt, and then I was able to flash TWRP via fastboot.
Then I did a complete wipe of my device through TWRP, and flashed Resurrection Remix and GAPPS.
At first I was getting error 7 and error 6 everytime I flashed the rom, but I managed to fix that through some readings.
The problem is that, I always stuck in bootloop (the RR boot screen).
I tried with LineAge OS, because at first I thought it was a ROM issue, and the same thing happened: it stuck in bootloop (the LineAge OS boot screen in this case).
The step I did was :
TWRP 3.1.1-0 ---> Wipe ---> Swipe to Factory Reset ---> Install ROM and Gapps ---> Wipe Dalvik Cache ---> Reboot System
Note: I also tried without the Wipe Dalvik step before rebooting, same result.
Another thing I tried was :
TWRP 3.1.1-0 ---> Wipe ---> Advanced Wipe ---> then I select "Dalvik/ART cache", "System", "Data", and "Cache" ---> Swipe to Wipe ---> Install ROM, Gapps ---> Wipe Dalvik Cache ---> Reboot System
Note: I tried this one without the Wipe Dalvik aslo, same result.
This phone is my daily driver, so can anyone please educate me on what's happening?
(Yes I know it's not good for beginners to do this by himself on his daily driver, but in the past I have rooted and install custom ROM on my Galaxy S3 Mini...that's why I was a bit confident -.- )
Thanks in advance, I hope I get an answer here.
Click to expand...
Click to collapse
i had the same issue, solution to this is : just flash MM bootloader from TWRP.
Here: https://drive.google.com/file/d/0B3tM1cVKiyp6Q3RvNUtLdEp1Q3M/view?usp=drivesdk
I have tried to install custom roms on my samsung galaxy grand prime g530m device but when I install them they do not pass the rom logo, I have tried to install lineage os (android pie) and resurrection remix (andrioid oreo) and the two remain in the logo of the rom , if I install the custom rom the cell phone returns to normal but I want to update it ...
What solution is there?
fortex123 said:
I have tried to install custom roms on my samsung galaxy grand prime g530m device but when I install them they do not pass the rom logo, I have tried to install lineage os (android pie) and resurrection remix (andrioid oreo) and the two remain in the logo of the rom , if I install the custom rom the cell phone returns to normal but I want to update it ...
What solution is there?
Click to expand...
Click to collapse
First, boot into TWRP and choose the "Backup" option to create a nandroid backup. This backup can be used to restore back what you had when you made the backup, restore this backup whenever you have issues.
When flashing your custom ROM, you need use the factory reset option in TWRP, then wipe the cache partition and the dalvik cache partition before or after you flash the ROM.
Failing to factory reset and wipe the caches causes bootloop(stuck at logo) when flashing a ROM, unless the ROM you are flashing is an updated version of the exact same ROM you already have.
If factory resetting and wiping caches doesn't solve your bootloop, you may need to use the advanced wipes in TWRP to run a full system wipe and then clean flash the ROM. To use the advanced wipes, choose the "Wipe" option in TWRP, then choose the "advanced wipe" option, then choose only the system, data, cache and dalvik cache partitions. Then swipe the slider to wipe, then go back to home page in TWRP flash your ROM.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
First, boot into TWRP and choose the "Backup" option to create a nandroid backup. This backup can be used to restore back what you had when you made the backup, restore this backup whenever you have issues.
When flashing your custom ROM, you need use the factory reset option in TWRP, then wipe the cache partition and the dalvik cache partition before or after you flash the ROM.
Failing to factory reset and wipe the caches causes bootloop(stuck at logo) when flashing a ROM, unless the ROM you are flashing is an updated version of the exact same ROM you already have.
If factory resetting and wiping caches doesn't solve your bootloop, you may need to use the advanced wipes in TWRP to run a full system wipe and then clean flash the ROM. To use the advanced wipes, choose the "Wipe" option in TWRP, then choose the "advanced wipe" option, then choose only the system, data, cache and dalvik cache partitions. Then swipe the slider to wipe, then go back to home page in TWRP flash your ROM.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I already did the steps you tell me in the message but the problem is that the phone is locked in the custom rom symbol ...
Greetings,
I want to ask if there is any solution to fix inverted touch (position X) on screen on my Samsung Galaxy S6 [G920FXXS5EQL1].
With TWRP 3.3.1.0 I made backup of official Samsung Android Nougat 7.0 I have installed on my phone.
Then I wiped Dalvik / ART Cache, Cache, System and Data. Rebooted back to TWRP, downloaded LOS 17.1 UNOFFICIAL ROM and then put it into Internal Storage.
Started flashing this ROM, when flashing was completed I wiped Dalvik / ART Cache, then Rebooted to System. Everything was fine, until Setup screen.
When I clicked on Next, it clicked on Emergency call, I was confused so I restarted back to recovery TWRP but now even in TWRP the touch is inverted, so I wiped
again Dalvik / ART Cache, Cache, System and Data. Rebooted back to recovery TWRP and installed back backup. The problem still persists even on official Samsung Android Nougat 7.0.
Rebooted back to recovery TWRP and wiped Dalvik / ART Cache, Cache, System, Data and Internal Storage. Downloaded and flashed /e/ OS but still, touch on screen is inverted.
I already tried USSD/MMI code *#2663# from this thread on LOS and /e/ but on these ROMs, this doesn't work.
Is there any solution to fix this ?
Thank you
you probably flashed the wrong twrp. You will need to install stock rom and then reinstall touch firmware.
Thanks for advice.
It's already working. The official 3.3.1.0 TWRP for Samsung Galaxy S6 caused this inverted touch.
So I flashed original firware via Odin G920FXXS6ETJ6_G920FOXX6ETI6_G920FXXU6ERF6_HOME.tar.md5 (tried 18 different firmwares, only this one worked)
Reinstalled touch firmware in Samsung Test Menu.
I used this time unofficial twrp-3.5.2_9-0-zeroflte.img via Odin.
Then I flashed /e/ OS via TWRP and everything works like I wanted.