I've flashed hundreds of ROMs on phones over the years and have never seen this issue before.
I flash LineageOS, phone boots lineageOS, power cycle the phone (turn off or restart) and its back on stock rom?!? I've flashed the rom with both TWRP and Lineage Recovery. I've checked slots A and B after the power cycle and no matter what, Lineage isn't on the device. Its like booting Linux off a USB on your computer... it boots then once you reboot, its not installed anymore
What were your steps for flashing? It's possible it boots lineage once, then after rebooting it won't boot correctly and reverts back to the other slot with oos on it maybe.
Related
so i installed lineageOS 14.1 through twrp and got stuck in a black screen, so i went back to twrp, wiped data, cache, etc and flashed an hybrid bootstack and rebooted into recovery, but all of a sudden the lineage os logo pops up and after a while it gets to the os, i cant get further than the get a fresh start option, it stays at checking for updates forever, adb doesnt recognize the device and i cant get to twrp, vol down+ power doesnt do anything
Were you able to fix the problem?
Which hybrid bootstack did you flash?
I have the same issue on a D803 coming from Kitkat
The thing is my zuk z1 is in a boot loop i can go into the recovery and all modes but if i flash any rom ie Pixel experience,ZUI anything via twrp it just bootloops .. I tried qfil/qpst to flash cm stock and zui stock both .. the qfil said succeeded but to no help it still went to bootloop just goes to the logo of zuk powered by android and then boot loops please help me my device is unusable would very much appreciate if u could help...
Note: I also tried to wipe all partitions via twrp and fastboot and again changed all of them(via twrp) to ext4 and again flashed lineage os but still went to the boot logo of lineage os and rebooted please help
press and hold power button for some seconds until the phone turns off. (be patient, it will restart first, but keep holding power button it will power off.) after that flash cm 12.1 qfil rom using qfil.
i have faced similar problem but i got recovered by flashing cm 12.1 rom using qfil. and after that i flashed mm_firmware zip using twrp file and then mokee rom 7.1.2 release rom.
I've got a T-Mobile 6T, and I messed up. First, I installed TWRP and that went well, then I tried to install Resurrection Remix.
I wiped all of the partitions except Vendor because thats what I used to do on my OnePlus 3T, but this time whenever I would try to flash Resurrection Remix, it would give me an error. I tried and tried to fix it, and then I went to reboot into the recovery through TWRP to see if that would fix it, it just booted into the bootloader. Now I'm stuck in the bootloader, and I'm not sure what to do.
I've got no ROM installed, and no Recovery installed(I assume because I can't boot into it), and I can't get the MSMDownloadTool to detect my phone. Thanks.
Rtap1134 said:
I've got a T-Mobile 6T, and I messed up. First, I installed TWRP and that went well, then I tried to install Resurrection Remix.
I wiped all of the partitions except Vendor because thats what I used to do on my OnePlus 3T, but this time whenever I would try to flash Resurrection Remix, it would give me an error. I tried and tried to fix it, and then I went to reboot into the recovery through TWRP to see if that would fix it, it just booted into the bootloader. Now I'm stuck in the bootloader, and I'm not sure what to do.
I've got no ROM installed, and no Recovery installed(I assume because I can't boot into it), and I can't get the MSMDownloadTool to detect my phone. Thanks.
Click to expand...
Click to collapse
Turn off phone completely, hold volume down (or up and down, can't remember) and plug in phone to PC. MSMTool should recognize your phone now.
To get the phone to turn on and enter Qualcomm 9008 mode, turn the phone completely off, hold down both Volume Up and Down, then connect the phone directly into the PC without pressing the power button. If MSM does not recognize the device, reinstall the drivers. If that fails, make sure you are connected to a USB 2.0 port, not a 3.0.
Since you can access the bootloader, just flash a fastboot rom. Allow it to flash completely and reboot. Use the flash_all_partitions file.
Rtap1134 said:
I've got a T-Mobile 6T, and I messed up. First, I installed TWRP and that went well, then I tried to install Resurrection Remix.
I wiped all of the partitions except Vendor because thats what I used to do on my OnePlus 3T, but this time whenever I would try to flash Resurrection Remix, it would give me an error. I tried and tried to fix it, and then I went to reboot into the recovery through TWRP to see if that would fix it, it just booted into the bootloader. Now I'm stuck in the bootloader, and I'm not sure what to do.
I've got no ROM installed, and no Recovery installed(I assume because I can't boot into it), and I can't get the MSMDownloadTool to detect my phone. Thanks.
Click to expand...
Click to collapse
Just fastboot boot twrp and flash full rom zip or restore a backup if you have one.
twinnfamous said:
Just fastboot boot twrp and flash full rom zip or restore a backup if you have one.
Click to expand...
Click to collapse
Or you can use the fail safe MSM download tool.
I've had a Galaxy SM-T510 for about 18 months. I installed a custom ROM and it worked fine. When it booted up I received a message "Bootloader is unlocked and security cannot be guaranteed, press power button" and when you pressed the power button it booted up fine. Recently, I installed TWRP and when I rebooted it goes to the some "Bootloader is unlocked, etc" error message, but when you press the power key it restarts and loops to the same point. Holding the power key, with volume up, volume down or both makes no difference. I installed Fonepaw which appears to only work in Download mode which I can't access. If I run Odin or Kies it doesn't recognise that there is a phone attached. Any suggestions?
I've solved the problem. Holding down both volume up & volume down at the same time, and plugging it in puts the device into download mode.
Actually, I haven't solved the problem. I can now install an OS thru either Odin or TWRP, but all the OS I have tried go into a bootloop and the device never finishes booting up.
I'm disappointed no one has any suggestions. I decided to replace TWRP with Orange Fox and installed Lineage, the device of course went into a bootloop. I then booted it into recovery and it went into TWRP. So I installed Orange Fox and wiped everything, I reebooted and this time it went into Orange Fox. I reinstalled Lineage -> another bootloop, tried to get back into recovery and it was TWRP.
BillSchutt said:
I'm disappointed no one has any suggestions. I decided to replace TWRP with Orange Fox and installed Lineage, the device of course went into a bootloop. I then booted it into recovery and it went into TWRP. So I installed Orange Fox and wiped everything, I reebooted and this time it went into Orange Fox. I reinstalled Lineage -> another bootloop, tried to get back into recovery and it was TWRP.
Click to expand...
Click to collapse
You aren't getting help because you are posting in the wrong place. And, if you are coming from an old custom ROM, you have to first flash the right stock ROM. I no longer have a 510 so I'm not sure which stock ROM you need but if you check the first post for the custom ROM you want in the ROMs, kernels and recovery thread, it should tell which one it is based on.
I have the Nexus 7 2013 wifi edition, it's been sitting here for a bit so I decided to give it new life by flashing lineage os on it.
Well the issue starts with the recovery, when I do `fastboot boot recovery.img` nothing happens, tried both the lineage recovery and twrp.
At the top of the screen it shows `booting downloaded image`, but nothing happens, the device actually freezes.
This device is stock, updated and unlocked.
Any suggestions?
I have the same tablet and the same problem. I have also tried both the lineage recovery and twrp. It just hangs...
Help?!