Database Users

Stuck on bootlogo whenever flashing a cm13 rom

Regardless of what recovery I used, (yash28, regalstreak, official twrp) or even starting from the scratch( flashing stock OxygenOS using the Oneplus tools) and then reflashing the recovery, my attempts to succesfully load into a ROM has been futile. As of now, I am pretty much unable to boot into any recovery, and I am stuck using the stock OxygenOS. I tried flashing modem, first attempt was clean flashing the new modem, then flashing it dirty after flashing my rom, I tried doing the same thing with the old modem, my attempts have been futile. If anyone could shed light in this situation, it would be great, I would hate to be stuck using the stock OxygenOS rom, and not try out the great roms that are developed. I can however flash oxygenOS stock rom.

i have the same problem and i cant find any solution i thought of starting fromt he scratch as it didnt help u it might not help me too

Have the same, I've done everything. I've made the phone full stock again and still won't boot.

I have finally found the solution to my own problem
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.

abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
So now youre able to flash CM13 without bootloops?

yousuf.shareef said:
So now youre able to flash CM13 without bootloops?
Click to expand...
Click to collapse
Yep! Also make sure you are using official TWRP (https://dl.twrp.me/oneplus2/) Good luck.

abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
FINALLY! Thank you!! Ive been stuck all day without getting ANY MM ROM to boot,. and this ...thing...fixed it! Thanks again

Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!

JudderArts said:
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
Click to expand...
Click to collapse
Dont forget to thank people.

abhisek1994 said:
Dont forget to thank people.
Click to expand...
Click to collapse
JudderArts said:
thank you!
Click to expand...
Click to collapse
That's exactly what I did.

I think i faced the same problem, im using h2os 6.0.1 close beta, with twrp 3.0, but without rooting. I can restore my rom tru twrp without problem. But my try to flash grarak cm13 and new mokee os 6.0 ended up with bootloops, both stuck at oneplus logo

abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen

muthukumarc said:
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
Click to expand...
Click to collapse
You have to downgrade fastboot/bootloader to the Lollipop one (just flash the usual revert_to_lollipop.zip found in these forums as usual).

Camera not working after root

I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!

kwcty6888 said:
I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!
Click to expand...
Click to collapse
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?

Heisenberg said:
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?
Click to expand...
Click to collapse
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?

kwcty6888 said:
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?
Click to expand...
Click to collapse
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.

Heisenberg said:
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.
Click to expand...
Click to collapse
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!

kwcty6888 said:
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!
Click to expand...
Click to collapse
Flash the full factory images (except userdata), then flash the latest TWRP, not boot into TWRP and enter the wipe menu, select advanced wipe, tick the data box and wipe it. Boot up and see if that helps.

Bricked, always loops back to splash screen

Title says it all. Fastboot works, flashing works. Even if I try to charge the phone on power off condition, it loops infinitely to splash screen. Tried flashing both custom and official ROMs via fastboot. I don't think this is an emmc problem since I can still format and erase all partitions.
Before all of this, I used the official RR Nougat ROM. Everything works fine until it suddenly bootloops out of thin air.

bakanui said:
Title says it all. Fastboot works, flashing works. Even if I try to charge the phone on power off condition, it loops infinitely to splash screen. Tried flashing both custom and official ROMs via fastboot. I don't think this is an emmc problem since I can still format and erase all partitions.
Before all of this, I used the official RR Nougat ROM. Everything works fine until it suddenly bootloops out of thin air.
Click to expand...
Click to collapse
Flash stock firmware with QFIL

mshoaib7 said:
Flash stock firmware with QFIL
Click to expand...
Click to collapse
I have tried to flash via QFIL, but it stopped midway flashing the system and device won't turn on now
I guess it's just me messing up somehow with the cables or something
Thank you anyway mshoaib7!

https://boycracked.com/2016/02/12/e...rmware-any-android-devices-via-fastboot-mode/
Try this one. May help u. Extract from official ROM. And flash those things. System IMG is not needed if u have any old backup means. Flash use this. Go to recovery and restore old one.
Bcz system image is large, so sumtyms it fails to flash. That's y I said lrave the system data image flashing and restore the backup.

mshoaib7 said:
Flash stock firmware with QFIL
Click to expand...
Click to collapse
@mshoaib7 bro you like idli or dosa??

Give it to service centre

bakanui said:
I have tried to flash via QFIL, but it stopped midway flashing the system and device won't turn on now
I guess it's just me messing up somehow with the cables or something
Thank you anyway mshoaib7!
Click to expand...
Click to collapse
bro use downloader the flash tool which is already given in the stock firmware if still it get stuck in the middle then it is driver problem then format u r pc or use friend pc

how to properly revert back from mm or nougat roms to stock kitkat rom?
I was on cm13 by ed300, then I tried to restore nandroid backup of stock kk via twrp
then my phone stuck on boot logo, only fastboot mode works, then flashed twrp and stock kk rom after some attempts.
So what are the steps to successfully revert back to kk? (in case this problem happens again in future)

Gyrometer not working after twrp restore

So I restored my PureNexus backup after trying Android O DP2, just noticed this morning that my phone doesn't recognize rotation. I have a motorcycle game that requires rotating the phone and it doesn't recognize any input. I also tried rotation a YouTube video to full screen and no beans. Autorotate is on btw...
I already tried wiping the system/cache and reinstalling PN, my only other option is a full wipe unless there is any easier fix.

Running into the same issue....
flashed "O" yesterday, installed TWRP, clean flashed PN,vendor,radio, bootloader and have no rotation. also brightness is not working and proximity isn't working either. also a slow wake up from screen off (1-2 seconds)
I just flashed May's factory Image and my brightness was still messed up (didn't test the other stuff...woops) currently flashing April's Image to see if that fixes it.
nope, didn't fix it. rotation and brightness don't work. flashing O now. what a ****ing PITA.
Did "O" just **** our sensors?

GatorsUF said:
So I restored my PureNexus backup after trying Android O DP2, just noticed this morning that my phone doesn't recognize rotation. I have a motorcycle game that requires rotating the phone and it doesn't recognize any input. I also tried rotation a YouTube video to full screen and no beans. Autorotate is on btw...
I already tried wiping the system/cache and reinstalling PN, my only other option is a full wipe unless there is any easier fix.
Click to expand...
Click to collapse
turdbogls said:
Running into the same issue....
flashed "O" yesterday, installed TWRP, clean flashed PN,vendor,radio, bootloader and have no rotation. also brightness is not working and proximity isn't working either. also a slow wake up from screen off (1-2 seconds)
I just flashed May's factory Image and my brightness was still messed up (didn't test the other stuff...woops) currently flashing April's Image to see if that fixes it.
nope, didn't fix it. rotation and brightness don't work. flashing O now. what a ****ing PITA.
Did "O" just **** our sensors?
Click to expand...
Click to collapse
Same thing happened to me when I went back to 7.1.2. The only thing that fixed it was to completely wipe the /data partition. Back up all your data before you do it :good:

bouchigo said:
Same thing happened to me when I went back to 7.1.2. The only thing that fixed it was to completely wipe the /data partition. Back up all your data before you do it :good:
Click to expand...
Click to collapse
doesn't flashing a factory image do this? I flashed 2 different image files and neither one fixed it. if I have to flash back to 7.1.2, then boot into TWRP and Wipe Data, I'll do that. just want to make sure is all.
I flashed back to O and everything is working now, so I know the sensors are't physically damaged, its absolutely software related.

turdbogls said:
doesn't flashing a factory image do this? I flashed 2 different image files and neither one fixed it. if I have to flash back to 7.1.2, then boot into TWRP and Wipe Data, I'll do that. just want to make sure is all.
I flashed back to O and everything is working now, so I know the sensors are't physically damaged, its absolutely software related.
Click to expand...
Click to collapse
Yes, it's software related. I usually don't wipe /data unless necessary. Are you flashing images one by one, using the flash-all.bat, or flashing the OTA. Flashing images one by one won't wipe /data, and the OTA will not wipe /data. Using the flash-all.bat should, unless you modify the file and remove the "-w" from one of the lines in the file.
Yes, flash back to 7.1.2, then wipe data.

bouchigo said:
Yes, it's software related. I usually don't wipe /data unless necessary. Are you flashing images one by one, using the flash-all.bat, or flashing the OTA. Flashing images one by one won't wipe /data, and the OTA will not wipe /data. Using the flash-all.bat should, unless you modify the file and remove the "-w" from one of the lines in the file.
Click to expand...
Click to collapse
I downloaded the factory image .zip and used Nexus Root toolkit to flash it. my internal memory is wiped completely during the install. not sure what the flash-all.bat is.

turdbogls said:
I downloaded the factory image .zip and used Nexus Root toolkit to flash it. my internal memory is wiped completely during the install. not sure what the flash-all.bat is.
Click to expand...
Click to collapse
I don't know how that tool kit works, I prefer doing things manually. I just went back to stock 7.1.2 (flashing images one by one), then wiped /data, and all my sensors worked after that.
flash-all.bat is in the main file, you use that to flash all the images without using any tool kits:

bouchigo said:
I don't know how that tool kit works, I prefer doing things manually. I just went back to stock 7.1.2 (flashing images one by one), then wiped /data, and all my sensors worked after that.
Click to expand...
Click to collapse
I'm flashing stock 7.1.2 now. how did you wipe /data? through command lines, or through stock/custom Recovery?
---------- Post added at 10:41 AM ---------- Previous post was at 10:36 AM ----------
bouchigo said:
I don't know how that tool kit works, I prefer doing things manually. I just went back to stock 7.1.2 (flashing images one by one), then wiped /data, and all my sensors worked after that.
flash-all.bat is in the main file, you use that to flash all the images without using any tool kits:
Click to expand...
Click to collapse
looks like the toolkit flashes the images one by one. i following the command line and its doing them (bootloader, radio, boot,recovery,vendor, system) one by one.

turdbogls said:
I'm flashing stock 7.1.2 now. how did you wipe /data? through command lines, or through stock/custom Recovery?
Click to expand...
Click to collapse
You can do it in fastboot if you want, but I just did it in twrp.

bouchigo said:
You can do it in fastboot if you want, but I just did it in twrp.
Click to expand...
Click to collapse
F me. still isn't working. had O DP2 installed, flashed stock 7.1.2, flashed TWRP, wiped data, even formated data. still not working. any other suggestions?
Edit: resetting the device thorugh the settings>backup & reset seems to have worked. brightness working, rotation working, prox I assume is working.
thanks for the help everyone!

Could it be radio or bootloader? O still have those images flashed from the ODP

turdbogls said:
Running into the same issue....
flashed "O" yesterday, installed TWRP, clean flashed PN,vendor,radio, bootloader and have no rotation. also brightness is not working and proximity isn't working either. also a slow wake up from screen off (1-2 seconds)
I just flashed May's factory Image and my brightness was still messed up (didn't test the other stuff...woops) currently flashing April's Image to see if that fixes it.
nope, didn't fix it. rotation and brightness don't work. flashing O now. what a ****ing PITA.
Did "O" just **** our sensors?
Click to expand...
Click to collapse
I fixed the problem by flashing stock with the flash-all.bat file and locking the bootloader. Android O really messed up my mind. For a second i thought my phone was faulty, starting hitting the thing on my palm like a hard reset would work:laugh::laugh::laugh:

A20 stuck in SANSUNG logo screen

After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?

MorneDJ said:
After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
Click to expand...
Click to collapse
That's really strange.
What is your firmware date?

physwizz said:
That's really strange.
What is your firmware date?
Click to expand...
Click to collapse
I used this Firmware: XFA-A205FXXU2ASFA-20190803073130

MorneDJ said:
After trying a bunch of options, I had to turn to asking for help please.
I installed TWRP and rooted via Magisk a few weeks ago. Everything worked perfectly for a few weeks. Then, suddenly the screen had an issue where the touchscreen stopped working. I could boot back to TWRP but the touchscreen was still not working. After allowing the battery to drain to 0, the touchscreen started working again.
I got into TWRP and tried to restore a previous backup, but suddenly the screen got stuck at the SAMSUNG screen.
Since then I have tried a factory install, a wipe of the data/system file, I tried an install from a stock image I got here, etc. Somewhere in the last 3 days (yes, been trying for 3 days) I managed to wipe the OS.
TWRP 3.3.1-0 is still installed, and I can access that. Note: I see the following in RED when I try a restore.
E: FBE found but FBE support not present in TWRP
Could anyone please assist in this ?
Click to expand...
Click to collapse
Reflash stock firmware via ODIN
then reinstall twrp
Or if you don't have a pc download a GSi in another phone with a SD card , extract the .img GSi file , put the sd card in your phone and flash it via Twrp to SYSTEM
Also use twrp 3.0.2-0 because newer versions are reported to have some problems

Imyou said:
Reflash stock firmware via ODIN
then reinstall twrp
Or if you don't have a pc download a GSi in another phone with a SD card , extract the .img GSi file , put the sd card in your phone and flash it via Twrp to SYSTEM
Also use twrp 3.0.2-0 because newer versions are reported to have some problems
Click to expand...
Click to collapse
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20

MorneDJ said:
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
Click to expand...
Click to collapse
GSIs are here
https://forum.xda-developers.com/galaxy-a20/how-to/gsi-galaxy-a20-t3964546
Not sure about 3.0.2-0
I use this one
https://forum.xda-developers.com/ga...p-samsung-galaxy-a20-custom-recovery-t3955271

MorneDJ said:
OK, two main questions.
- Which GSi would you recommend for the A20.
- How do I downgrade to TWRP 3.0.2-0, as I could only find the one version for the A20
Click to expand...
Click to collapse
Gsi* - I recommend HavocOs
Very stable , everything works and no bugs so far.
Been using it as my daily driver for like 2 weeks!
And as for twrp you can retry with the one you have but I don't know if the problem will happen again.
I'm sorry I have lost the link that I found my twrp

OK. I have tried a few GSI roms, but all of them the same problem where the phone gets stuck in the bootloader. I finally just decided to go back to standard Samsung ROM, but my touchscreen is dead. I am currently setting it up using an OTG connector with a USB mouse ....
Any idea what I can try. Yesterday the touchscreen was working in TWRP, but, after numerous retries and flashing that is no longer working. I do not want to chuck the phone ...

MorneDJ said:
OK. I have tried a few GSI roms, but all of them the same problem where the phone gets stuck in the bootloader. I finally just decided to go back to standard Samsung ROM, but my touchscreen is dead. I am currently setting it up using an OTG connector with a USB mouse ....
Any idea what I can try. Yesterday the touchscreen was working in TWRP, but, after numerous retries and flashing that is no longer working. I do not want to chuck the phone ...
Click to expand...
Click to collapse
Touch screen not working.
I would take it back under warranty.