Develop Bugs

CM13 not booting

After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.

Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.

RDChase said:
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
Click to expand...
Click to collapse
Just did it, it still seems to be booting like it previously was. Wiped cache, dalvic, data, and system and then installed CM13 and gapps. Still booting as I write this.

Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.

RDChase said:
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
Click to expand...
Click to collapse
I've kind of given up at this point. Even CM12 doesn't work. The only thing that seems to work is the stock rom. My phone is the regular SPH-L710 model. I didn't even know the L710t was a thing.

I have the same problem, and sometimes it boot in the system setup mode, but the sensor is not working, i can turn on airplane mode, reboot or power off, and sensor works, what happend i dont know((

ovil101 said:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))

1vankill1 said:
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
Click to expand...
Click to collapse
That just seems to be a stock rom.

yes it stock rom, after it was installed, I was able to install 13 cm

TWRP installed; Do I need anything else to flash CM13?

Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?

riahc3 said:
Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?
Click to expand...
Click to collapse
No, but most people would flash gapps 6 too, else you will miss a lot (must be done at the same time as the ROM the first time to set permissions)

IronRoo said:
No, but most people would flash gapps 6 too, else you will miss a lot (must be done at the same time as the ROM the first time to set permissions)
Click to expand...
Click to collapse
What I ment is before flashing it....Afterwards/during of couse Ill flash gapps

riahc3 said:
Title basically says it all.
I have been able to install TWRP on a S4 Mini. Do I need anything else to flash CM13?
Click to expand...
Click to collapse
Copy CM13 rom and gapp in your sd card.
Backup your old firmware through twrp.
Do a factory Reset from Wipe.
And install CM13 and gapp respectively.
And enjoy ^_^

syednawaz said:
Copy CM13 rom and gapp in your sd card.
Backup your old firmware through twrp.
Do a factory Reset from Wipe.
And install CM13 and gapp respectively.
And enjoy ^_^
Click to expand...
Click to collapse
checked every file hash matches, did exactly as written, done all of above and it doesn't work
TWRP went on in less than 10 second does that sound normal ? and how do you know if its actually on there?

Nope. Installation take atleast 2 or 3 minutes.
and if its installed properly you would have seen different rom from the stock.
Here is what i use for s4 mini(i9192). Also used it on i9190 model as well.
http://forum.xda-developers.com/galaxy-s4-mini/development/rom-aokp-rom-25-apr-2016-t3366314
and these steps mentioned in the website.
A. Initial install
1. Copy ROM and Gapps to your external SD Card or internal memory
2. Boot into recovery
3. Wipe
4. Install ROM and Gapps
5. Reboot
Its simple. Should have worked.
I hope you have installed your model rom.

A question the system format is required to install the rom ??

juanpabloml said:
A question the system format is required to install the rom ??
Click to expand...
Click to collapse
In TWRP Swipe for factory reset will do the job. you can also do dalvik /art cache in advance wipe. System or other wipe never did it for changing roms.

syednawaz said:
In TWRP Swipe for factory reset will do the job. you can also do dalvik /art cache in advance wipe. System or other wipe never did it for changing roms.
Click to expand...
Click to collapse
Ie that enough only to make WIPE FACTORY RESET AND WIPE DALVIK CACHE is not necessary to the FORMAT SYSTEM, DATA AND CACHE ??

sorry i do not understand.
to install a rom just do a factory reset. nothing else is necessary.
If you do not do factory reset, sometimes you will not be able to install a new version of rom(for example, from kitkat to lollipop).
if you do not do factory reset its called dirty flash.
for example
you are using custom rom cm13. and it has a new update released, you go in twrp recovery and install the updated rom without doing factory reset. this way you can keep all the application and data you have.
i hope i am making some sense. it is hard for me to explain.
well do some flashing and you will understand but always make a backup.

Root / SuperSU Failing to complete? ( Help)

When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.

savvymatthew said:
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
Click to expand...
Click to collapse
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.

LS.xD said:
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
Click to expand...
Click to collapse
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.

savvymatthew said:
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
Click to expand...
Click to collapse
OnePlus.net offers the rom files as download:
OOS 3.2.6 (capable for OTA 3.2.8)
Open Beta 7
I'm using the Open Beta at the moment and it runs without any issues
OOS roms can be flashed with custom TWRP
For a clean installation just wipe partitions (System; Data; Cache; Int. Storage) with TWRP before flashing the new rom

Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.

Hw4ng3r said:
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Click to expand...
Click to collapse
Thank you for pointing on that I backup all my stuff on my computer once a week but others may not.
By never wiping your internal or manually deleting folders you will collect garbage over time when you change android installations.

I have a back up from when i first set it up, so its very old. After i Flash and set everything up again think im gonna start making weekly back ups, with all the roms and stuff for this phone probably be smart.
Thanks guys

Questions about flashing Lineage 15.0

I have not yet received the phone, but when I do I will boot loader unlock/root. (If I don't intend to stay with Oxygen OS at all, should I even root or just flash the new ROM?) Also, is dirty flashing ok with this? Can I just flash it without wiping?

ZVNexus said:
I have not yet received the phone, but when I do I will boot loader unlock/root. (If I don't intend to stay with Oxygen OS at all, should I even root or just flash the new ROM?) Also, is dirty flashing ok with this? Can I just flash it without wiping?
Click to expand...
Click to collapse
When you unlock the bootloader it will wipe the device so dirty flashing is not in the equation.
If you are flashing CM then you dont need to root first but you will need to root after. (last I knew) Most roms these days dont come with root by default.

zelendel said:
When you unlock the bootloader it will wipe the device so dirty flashing is not in the equation.
If you are flashing CM then you dont need to root first but you will need to root after. (last I knew) Most roms these days dont come with root by default.
Click to expand...
Click to collapse
Yeah it will wipe it, but the system files are still there right? I was watching a video of someone installing a new ROM, and they deleted
Dalvik/ ART Cache
System
Data
Cache
Or am I wrong? Do I not need to wipe all those partitions before flashing? Really sorry for being a bother, fairly new to this.

ZVNexus said:
Yeah it will wipe it, but the system files are still there right? I was watching a video of someone installing a new ROM, and they deleted
Dalvik/ ART Cache
System
Data
Cache
Or am I wrong? Do I not need to wipe all those partitions before flashing? Really sorry for being a bother, fairly new to this.
Click to expand...
Click to collapse
That is what is called a clean flash. (always the best bet when flashing a rom rom and even suggested by all devs. You will be told that you can "dirty" flash (wiping only system and both caches) so your app data and settings stay after the flash but to be honest that is just being lazy as you will have to clean flash before you can post a bug report anyway, so why not do it from the start)
Yes when you unlock the bootloader the system will be fine. What the unlock does is pretty much a factory reset. So make sure to back up any pic, music or what ever.

HTC One M8 with LineageOS 16, package installer crashes

Package installer crashes and i cant install .apk files, i tried other installers, but they crash too. Also, when I want to give location permission to app, it crashes saying package installer crashed. What could be the cause? (i know i can install apps through adb, but i dont always have access to computer)

You've started 3 threads now, all possibly related. Starting multiple threads is not a good idea, as it's only going to confuse you and those trying to help you. The info in this thread is very incomplete. I only know this from helping you on another thread. Helped by the fact that traffic is low on this device forum, otherwise I probably wouldn't connect the dots on this. So consider yourself lucky, and please post smarter moving forward.
I know you previously flashed the wrong boot.img. Then re-flashed the ROM. When you re-flashed the ROM, did you dirty flash? If so, sometimes that works, sometimes it doesn't. Having random problems after a dirty flash, is usually an indicator that you need to go back and do a clean flash. Back up your personal data by method of your choice. Then clean flash (default wipe in TWRP - data, cache, Dalvik), then flash ROM again, and flash gapps if needed for the ROM.

redpoint73 said:
You've started 3 threads now, all possibly related. Starting multiple threads is not a good idea, as it's only going to confuse you and those trying to help you. The info in this thread is very incomplete. I only know this from helping you on another thread. Helped by the fact that traffic is low on this device forum, otherwise I probably wouldn't connect the dots on this. So consider yourself lucky, and please post smarter moving forward.
I know you previously flashed the wrong boot.img. Then re-flashed the ROM. When you re-flashed the ROM, did you dirty flash? If so, sometimes that works, sometimes it doesn't. Having random problems after a dirty flash, is usually an indicator that you need to go back and do a clean flash. Back up your personal data by method of your choice. Then clean flash (default wipe in TWRP - data, cache, Dalvik), then flash ROM again, and flash gapps if needed for the ROM.
Click to expand...
Click to collapse
i did backup, then i wiped data, system, cache, dalvik, and after flashing ROM its still happening. It must be something with the Package Installer. Is there any way i can install Package Installer on my own, because what i found was only some external program which still used Package Installer.

DarkKnightComes said:
i did backup, then i wiped data, system, cache, dalvik, and after flashing ROM its still happening. It must be something with the Package Installer. Is there any way i can install Package Installer on my own, because what i found was only some external program which still used Package Installer.
Click to expand...
Click to collapse
Try flashing another Lineage build, is probably the easiest way.

redpoint73 said:
Try flashing another Lineage build, is probably the easiest way.
Click to expand...
Click to collapse
nevermind, I needed to update GApps, but I didn't saw a notification, so i didnt know i needed to update GApps, its working now

DarkKnightComes said:
nevermind, I needed to update GApps, but I didn't saw a notification, so i didnt know i needed to update GApps, its working now
Click to expand...
Click to collapse
Ah yes, that pesky gapps. Very easy to forget!

Lineage 16 on the M8, is it a smooth experience?
Cheers