yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] darbizman:
Boolloop on Nexus 6 while flashing BlissPop rom 3.3

Hi pjgraber,

I have a Nexus 6 running on BlissPop 3.2. I downloaded BlissPop 3.3, tried to flash it but all I got was a bootloop. What should I do? :)
[BLISS ROMS Development] ac3theone:
Clean flash
[BLISS ROMS Development] PhattyMcGee:
This is just my 2¢. . . I always dirty flash my ROM as long as it's the same version: 3.1 on 3.1, 3.2 on 3.2, etc. Whenever when there is a version change, (3.1 to 3.2, etc) I wipe everything except internal, then flash. I have never had a problem with this method (except when I fail to check the MD5 hash and I have a bad download ;))
[BLISS ROMS Development] rush420:
This is odd behavior lately. yesterday it wouldn't boot on internal storage it booted on secondary, multi rom an ran fine I tried to switch it to internal storage an boot loop, I'm beginning to think my internal storage is corrupt the new updates from yesterday an today won't boot on internal storage I just don't get it. I forgot to mention that I've also tried to clean install meaning factory reset everything except internal storage it wouldn't boot. An its I'm running it the on 15th update on secondary.
[BLISS ROMS Development] jerrycoffman45:
didbt work for me clean flash and 3.3 still stuck at boot animation
[BLISS ROMS Development] ac3theone:
Idk then, I wonder whats going on smh
[BLISS ROMS Development] jerrycoffman45:
​

i noticed the rom is 2mb smaller then the last build and it doesnt match the size listed on the website
[BLISS ROMS Development] nemofbaby2010:
Flash a kernel I did and it booted up pretty quickly

---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------

Also is there any fix for the unknown bug in the dialer?
[BLISS ROMS Development] ac3theone:
Not sure but I haven't had that problem
[BLISS ROMS Development] darbizman:
I did the dirty flash. Still no changes.
[BLISS ROMS Development] sonofevil77:
Oh damn I blindly dirty flashed 3.3 over 3.2 and I have no issues Thank the Lord sweet baby Jesus lol.

Chromatose
[BLISS ROMS Development] WhiteEVO:
I've tried flashing every way possible and still get the boot loop...I was lucky at one time to get the 5/14 3.3 installed and booted after a full wipe including internal, then I flashed the 5/15 3.3 build and it bootlooped...no matter how I installed it still bootlooped...
[BLISS ROMS Development] nemofbaby2010:
Flash Franco kernel after you install
[BLISS ROMS Development] jeanmauri90:
Bootlooping on me too already tried 7 times and it just won't boot :(
[BLISS ROMS Development] WhiteEVO:
Hahaha! After staying up till 2am flashing a diff rom, I figured I try 5/15 3.3 again...this time it booted fine! I didnt flash any different than the prev. times...not sure what's going on...seems different results for diff people...
[BLISS ROMS Development] aalupatti:
For people with bootloop just flash a different kernel like code blue or any....
[BLISS ROMS Development] jerrycoffman45:
tried that didnt work for me
[BLISS ROMS Development] Othoric:
I just dirty flashed 5-15 and code blue kernel over 5-12 and it booted up and is running fine. Last night when I tried it kept getting stuck at the boot animation. Very odd...
[BLISS ROMS Development] jerrycoffman45:
just tried agian with fresh download and franco kernel and its booting
[BLISS ROMS Development] aalupatti:
Anyone with loosing the network signal intermittently on the 5-15 build?
[BLISS ROMS Development] abjexstallion:
[MENTION=5346868]pjgraber03[/MENTION] still seeing the "unknown" caller in dialer on latest build FYI. Besides that, as usual, working flawlessly.
[BLISS ROMS Development] Othoric:
I've been using it since this morning and so far I haven't noticed any loss of signal at all.
[BLISS ROMS Development] aalupatti:
I think it was my kernel. Changed from code blue to Franco and all ok.

But for the love of God can't get v4a to work. May need an internal sd wipe.
[BLISS ROMS Development] Othoric:
Are you using the flashable zip or apk? I used to use the zip but for whatever reason it breaks screen mirroring on Chromecast. With the apk all I had to do was install. And then copy and paste the apk to the Viper4Android folder I created in the system/priv-app folder. I also would copy and paste it to the MusicFX folder in system/priv-app as well. However, I haven't installed v4a since I flashed Blisspop, simply because I don't really notice that big of a difference on audio quality with the Bluetooth speaker I use.
[BLISS ROMS Development] PhattyMcGee:
I've used nothing but code_blue for over a month and I've never had an issue flashing any of the updates. If I dirty flash an update, I always wipe cache and dalvik BEFORE and AFTER flashing my ROM, kernel, and gapps. I don't know if that will make a difference or not. Just a suggestion. Also, I have a feeling that the stock kernel is causing some bootloop issues, but I cannot confirm this since I use a custom kernel on each update.

As far as V4A is concerned, I've NEVER gotten that to work. If anyone has a successful method of getting it to work properly, I'd be interested [emoji6]
[BLISS ROMS Development] WhiteEVO:
With the 3.3 roms the boot loops do seem to be kernel related...I tried a clean flash with hells core and it boot looped, i then tried a clean flash with Vindictator and it booted fine...
[BLISS ROMS Development] RanceJustice:
Just letting everyone know, the in-line/OTA updater from BlissPop 3.2 (honestly, I can't remember. One of the early May variants) to the newest 3.3, resulted in unrecoverable bootloop. Previous updates (downloading using the built in BlissPop Updater, hash verified, then booting into TWRP for a dirty flash update. Note, I did not flash gapps after every update and it worked just fine; I originally flashed Banks' Gapps during original install) worked fine, but this one put me into a bootloop. Note: I am not using any after market kernel, just the one that BlissPop comes with. I had to use WugFresh's Nexus Root Toolkit's "Flash to stock, unroot" option with the Bootloop issue flag set; at current I'm back on stock 5.1 and have used NRT to root and install TWRP again in preparation to go back to custom ROMs

I guess I'll be giving it another go, but I'm a bit concerned. Other post suggest it is mandatory to flash Gapps every time, please place that somewhere in the updater's text. That was never necessary for instance, when I used normal CyanogenMod in the past and used their in-line updater to load new Nightlies, so I figured it wasn't necessary here.. I really hope this issue doesn't continue. Would anyone know a way out of a bootloop like this without having to flash back to stock?

Also, an unrelated question - has anyone on CM12.1 and/or BlissPop, using T-Mobile as their provider, been able to ensure that tethering is not metered separately when it comes to data use? That is to say, tethering data (including using the phone as a WiFi hotspot to share the LTE data connection, as well as Bluetooth/USB tethering) is not detected as different from ordinary data use?

Thanks.
[BLISS ROMS Development] Othoric:
I usually just make sure to perform a nandroid backup with TWRP before flashing. When I experience a bootloop (like I did when dirty flashing the newest build for the first time. Second time I flashed code blue kernel with it and it booted fine.) I always just turn the phone off. Boot up the boot loader and go into recovery and click restore and restore my backup I made before I flashed. It will save you a lot of time if you do run into any issues with flashing. Also, you do not need to flash gapps when dirty flashing on any ROM as far as I know. Only needed when clean flashing.
[BLISS ROMS Development] PhattyMcGee:
I agree! ALWAYS do a nandroid backup right before flashing any ROM. That way IF something goes wrong, just restore the backup and start over.
[BLISS ROMS Development] RanceJustice:
Thanks for the advice - once I get settled on a ROM (I'll probably use Bliss again, but I just want to compare a few things. I wonder if the BlissRom devs could add some of the same features that we see in many of the "CM 12.x + cherry picks" ROMs, like Temasek's and Spring?), I'll make Nandroid backups again; I've not messed with them since using my Nexus 4.

However, when I was in a bootloop, I couldn't get into the recovery (that is to say, TWRP). All I could do was let it keep trying to boot and eternally load, or go into fastboot/bootloader (by holding power+volume down when turning on the device). It wouldn't seemingly let me into TWRP from there. Was there something I missed?
[BLISS ROMS Development] gdonanthony:
any mirror ? i always get slow download speed :(
[BLISS ROMS Development] Othoric:
As far as I know all you should have to do is go into the boot loader and use the volume keys to select recovery, then press the power button.
[BLISS ROMS Development] ffchampmt:
Unable to flash until later but I'm curious if anyone is having luck installing the 5/16 build? Procedure you used?

Worried about the bootloops that plauged the last release.

Sent from my Verizon Nexus 6 running BlissPop
[BLISS ROMS Development] WhiteEVO:
After getting the boot loop issue solved (flash either code blue or vindicator kernel before re booting) I've run into another issue...

I have build Official-20150516-1809 installed, I get a message saying there is an update to build Official-20150516-1900. After downloading and flashing build 1900 "About Phone" still states I have build 1809 installed...I dont even see a build 1809 on their site. I got the 1809 build automatically through "update" in about phone.
[BLISS ROMS Development] Phaze1585:
Ive tried installing the latest version on my Nexus 6, using the latest banks, and each time my phone gets caught in a boot loop. Any ideas?
[BLISS ROMS Development] PhattyMcGee:
Which kernel did you flash with the ROM?
[BLISS ROMS Development] jerrycoffman45:
i had to flash franco kernel to get it to boot
[BLISS ROMS Development] Phaze1585:
I hadnt tried flashing it with any kind of kernel, just stock.

---------- Post added at 09:34 AM ---------- Previous post was at 09:34 AM ----------

Would hell kernel work you think or the new elemental X?
[BLISS ROMS Development] Mr.Holmes:
and for the sake of not looking like a complete idiot, I do know where the cm nav bar tweaks are in settings, I just assumed you were referring to something else since I already tried that. So one more time.. Thanks!
[BLISS ROMS Development] djsins1:
Yes its encrypted. I found out the hard way, and honestly can't figure out why being Google removed forced encryption on 5.1
[BLISS ROMS Development] zige:
That's weird. I have been decrypted since bought my Nexus at december and i was also decrypted when moved from Bliss to Euphoria to Benzo to Bliss to Benzo and to Bliss... So that's really weird...

Games has most of problems for some reason when restoring with titanium.
[BLISS ROMS Development] rndchef:
Do themes have the potential to break the dialer on this rom? I discovered that I would get a call and it would show on screen but locked up and couldn't answer it. It would then cause a reboot. Just want to know if I am breaking it or potential issue already. Thanks
[BLISS ROMS Development] EdwinAzul8:
Hi. I was just wondering if these ROMs are safe to flash on my nexus 6. Because I already downloaded about 4 or 5 of them and when I go to flash them, they all say that they are incompatible and that my system can become unusable. I'm new to this so I don't know
[BLISS ROMS Development] apophis9283:
Try flashing 5.1 bootloader and radio
[BLISS ROMS Development] EdwinAzul8:
How do I do that and where do I download that? And can I even download that if I already have chroma ROM 5.0.2 installed?
[BLISS ROMS Development] apophis9283:
http://xdaforums.com/nexus-6/development/bootloader-radio-boot-img-boot-loader-t3052425

You should be fine, im running 5.0 with 5.1 radio and bootloader
[BLISS ROMS Development] forty0z:
Going to try this ROM out right now thanks.
[BLISS ROMS Development] EdwinAzul8:
OK... But I'm just scared to do it though because I go to XDA to download the bootloader 5.1 but it says that you shouldn't download it and flash it if you are running 5.0. Also, when I do go to flash it, it also says that it is incompatible and it can render my system unusable
[BLISS ROMS Development] apophis9283:
Up to you. Im running it just fine. What you dont want go do is downgrade your bootloader
[BLISS ROMS Development] ithamatam:
I did also, i gave up and flashed stock havent switched kernels yet
[BLISS ROMS Development] sonofevil77:
Yeah I'm waiting it out now. Stock screen color kills my eyes lol. I've had a Samsung for the past 4 years so my eyes like that over saturated look. I'm using Rayglobe and Bliss with multirom now so I'm ok. I was using bliss with franco until the acore closes and crap I have now.

Rayglobe rocked Nexus 6
[BLISS ROMS Development] juscozimme:
Love this rom, finally I was able to install the Bliss last night. I didn't use TB to restore. Everything installed successfully, I tried to add a theme, unsuccessful. Normally I use the Zedge widget for wallpaper, but when I click the widget the screen would change to solid random colors. I was able to choose a wall paper by pressing home screen selecting the wallpaper from menu. I notice the battery drains quick, checked kernel all four cores were running max 2649 mhz,I changed settings from performance to interactive seemed to help a little. On the way home from work battery was at 97% I was talking on the phone for about 30 minutes, battery dropped to 82% , when I got home call dropped and phone locked up, rebooted phone twice before finally able to access home page. Anyways, I think I'm going to do factory reset and try again.
[BLISS ROMS Development] pjgraber03:
NEW BUILD

i have posted a new build 4-10-1807 and it is built with 03,krait and pipe optimizations.. also is built with new tool chains =)
[BLISS ROMS Development] umair shaikh:
Is encryption on ?
[BLISS ROMS Development] pjgraber03:
well i'm not sure TARGET_HW_DISK_ENCRYPTION := false that is in the device tree so it shouldn't be encrypting it but i'm not sure.. i have never decrypted
[BLISS ROMS Development] blueyes:
Volte

Its deff possible. Volte is working perfectly on Benzo... Only one I've used that does though... Love bliss, hopefully it gets ironed out.
[BLISS ROMS Development] kronikings:
I love all of the customization options this rom provides! Is it just me or is there a trade-off in the performance department?
[BLISS ROMS Development] jerrycoffman45:
i tried with hells and it didnt work for me
[BLISS ROMS Development] Phaze1585:
Ok. Ill try EX and franco.
[BLISS ROMS Development] jerrycoffman45:
after you get it to boot you can flash hells and it will boot i dont understand that
[BLISS ROMS Development] atrix4nag:
Bootloops

I installed the latest build and its bootlooping..

From the previous comments I assume installing a different kernel should fix the issue..

Which kernel do you suggest.

TIA
[BLISS ROMS Development] Othoric:
I've been using code blue and I've been very pleased with it so far. I've also heard very good things about ElementalX but I personally haven't tried it yet.
[BLISS ROMS Development] PhattyMcGee:
I use Code_Blue and I haven't had any issues at all
[BLISS ROMS Development] WhiteEVO:
Is anyone else having this problem?
[BLISS ROMS Development] jerrycoffman45:
yes probably just a typo in the build prop
[BLISS ROMS Development] abjexstallion:
Screencast not working.
[BLISS ROMS Development] aalupatti:
Works with some apps like youtube and so on but not with cast screen or solid explorer..
[BLISS ROMS Development] nicholaschum:
Nah, we don't type out our build props. Our automation system does that automatically. The build was most likely yanked after building but the ota3.xml was not removed
[BLISS ROMS Development] WhiteEVO:
Has anyone gotten the appbar working?
[BLISS ROMS Development] RanceJustice:
So is it "safe" to use the 5/16/15 3.3 release (particularly with its own built in kernel, as opposed to having to flash another kernel to avoid bootlooping)? Or are there any known errors, and thus it would be best to wait?

Also, has anyone had difficulty with the Peer5 downloader? It seems to be an issue of continual frustration for me. I'm using the latest Firefox (thus far I've tested on Windows. Haven't tried on Linux yet, but I have used an addon to set my user agent to Linux), and it rarely allows me to actually download the file. The bar shows up, showing a swift download speed and continues to 100%, but once it gets there it doesn't give me the Firefox prompt to save the file anywhere! I've also noticed it causing system slowdown (ie making the browser temporarily unresponsive). Is there any way to just download a single file directly? All I've found thus far is by checking the checkbox on mouse over, then going to the top of the page the search icon will change to a download one, and provide an archive that is named after the entire repository (ie pjgraber03.tar) but when I've done that and gone to extract it, 7z seems to work but tosses an error about trailing zeroes, so I want to ensure there are no issues. Reading a bit I think trailing zero filled records is related to the .tar spec, but I'm not sure if their absence in this case is an issue or not. Thanks!
[BLISS ROMS Development] nicholaschum:
As pat and I use code blue, we suggest flashing a custom kernel. We are planning to change kernels soon but for now if some people are having trouble with the stock kernel, this is most likely a CM fault as we mainly sync upstream from CM repos.

On the OnePlus where I also beta test releases where our other admin posts, there was a new TZ assertion algorithm inside the CM rom, which required flashing a new rom. This could be related to why recently there have been reports of boot loop with stock kernel.

As such, I would like to assure all users that Pat's Bliss base is always built in "make clean" mode, thus ensuring our upstream Bliss changes synced live onto the releases he pushes - as well as clearing junk. The kernel is a local one, which MAY need updating/replacing when CM updates require to do so.

Although pat hasn't posted much on XDA and doesn't have a super high thanks meter, he's a great and amazing dev and knows what he's doing. (he's in charge of Team Bliss site, server, gerrit and github).

Problems with VoLTE and such aren't problems because of the dev, it is because there are collisions in the code and we don't have not many internal testers who can test VoLTE, hence we hope for the best as we merge in verified Verizon and other vendor's proprietary libs.

Regarding Peer5, we are looking into more efficient ways it can be handled, currently there are known issues with Peer5 and pat is looking into it. As we aren't profiting and running this off our own sweat and blood, we have to act smart to see what our wallets can get us. We have a limit on http downloads for the Updates app, which is around 1.10mb/s for most users internationally, and Peer5 should download at around 5mb/s at max peak if applicable. This is actually very fast, and we have scheduled rollouts for other devices as well, hence sharing this speed would not be efficient if other devices grasp around 2000 user's every few days. The best and most reliable way to download will obviously be http, which you can do so by right clicking the package on our download server and open in new tab, or you can use Peer5, but please make sure to download the md5 alongside.

To everyone else: I'll try to be as active as I can on this thread, to be part of the support staff here, as Pat is like a machine, he builds, let Jenkins (our automation system) handle all the automation work, posts the build without announcing like an auto builder, and lives his life. As we are all human (mostly, unlike him [emoji23]), we might not be able to answer all questions, but please have faith in us, and if you have any questions, doubts or reasons to leave this rom, tell us, we're not strict on feature requests and/or bug acknowledgement.

Peace out.
[BLISS ROMS Development] aalupatti:
Thank you team Blisspop. Inspite of some complaints here this is one of the most feature rich and smooth room.

Ps: Would love to see V4A included ( I know one of the devs is already working on it )

Thanks once again
[BLISS ROMS Development] WhiteEVO:
Yes, no complaints here, love this rom! Keep up the great work Bliss team.
[BLISS ROMS Development] jewnersey:
Is MMS only in dark mode now? Conv list is good but message view is dark.
[BLISS ROMS Development] ffchampmt:
Tried dirty flash of 5/16 with elementalx and got bootloops.

Then clean flashed same combo - bootloops.

Then I clean flashed my nandroid backup, again a bootloop.

I then dirty flashed just the 5/12 build and phone is back running.

Not sure if it makes a difference but I am still encrypted and it never gets to the decrypt screen when it starts the loops.

Sent from my Verizon Nexus 6 running BlissPop
[BLISS ROMS Development] Itzamistry:
I just flashed the latest version and encountered a bootloop. Any ideas?
[BLISS ROMS Development] Othoric:
I also experienced bootloops with elementalx and stock kernels unfortunately. Try code blue kernel.

Flash code blue kernel as well. That fixed the bootloops I was experiencing.
[BLISS ROMS Development] nicholaschum:
Just to inform, next build should be cooked with lean to fix boot loops on stock kernel.
[BLISS ROMS Development] david1985:
does anyone ever get a real bad lag on the stable? like the phone just freezes up and slows down? anyway around that? thanks
[BLISS ROMS Development] nicholaschum:
Not here, but then again I am on code blue kernel.

I had it on the previous kernels, and lean, but having it set to blu_active has been great to me.
[BLISS ROMS Development] nozzleman_85:
I'm not sure what the issue is.. But I can't get the 05-17 build to get past the boot screen..followed the install instructions exactly as typed and used Banks' dynamic gapps (05-14-15)...guess I'll move on to a different Rom..
[BLISS ROMS Development] lasphyxial:
You need to flash Franco or code blue stock kernel isn't working at the moment
[BLISS ROMS Development] fleadog99:
If you are in bootloop since the 5.3 builds, then make sure you flash rom, then Gapps, then kernel (zip). I would also go into bootloop, but after I started flashing the kernel after the gapps, it works just fine. Make sure to do them all in the same session. Meaning don't reboot in between steps.
[BLISS ROMS Development] PhattyMcGee:
I'm not trying to sound condescending. I counted 15 posts over the last 2 days that specifically identify the stock kernel as the most likely reason for the bootloops and yet I'm still reading posts like "Update bootloops! Any ideas?" Please take 5 mins. and read a couple of pages back before posting (whatever) bug. There is a decent chance that it's been identified and maybe a workaround has already been suggested. After due diligence has been done, go ahead and ask.
[BLISS ROMS Development] nicholaschum:
Can we get some confirmation after people flashed the 17th build? It should be built with lean and shouldn't have the bootloop issue.
[BLISS ROMS Development] ibilln:
Flashed 05/18 (not 05/17) - boot loop. Reflashed it with Franco Kernel - OK.
[BLISS ROMS Development] nicholaschum:
Hmm, then how about reflashing it with latest lean?
[BLISS ROMS Development] nemofbaby2010:
Is the unknown bug still present?
[BLISS ROMS Development] ibilln:
Flashed all from 05/17 inclusive (see pic) - from here. All boot-looped. By "latest lean" perhaps you meant something else.
[BLISS ROMS Development] nicholaschum:
Like actually flashing the kernel manually: http://xdaforums.com/nexus-6/orig-development/kernel-leankernel-minimalistic-kernel-t2954316
[BLISS ROMS Development] ibilln:
Well, yes, that works - like flashing franco or others. I thought the issue was that the rom should now boot by itself with no boot loops. Sorry, my bad.

---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------

Hard to tell.
[BLISS ROMS Development] BakedFiend:
I believe the unknown bug is something with CM. It only seems to appear on CM based ROMs that I have tried