yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
Did you format userdata? It's worth a try.
[Nexus 6P Q&A, Help & Troubleshooting] .G33K:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.
[Nexus 6P Q&A, Help & Troubleshooting] Wiltron:
So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that :P

I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.
[Nexus 6P Q&A, Help & Troubleshooting] .G33K:
Hi There,

Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.

However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?

Meanwhile, all my fastboot commands are working with no issues at all.

EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.
[Nexus 6P Q&A, Help & Troubleshooting] bcjk8210:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?
[Nexus 6P Q&A, Help & Troubleshooting] TemplesOfSyrinx:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.
[Nexus 6P Q&A, Help & Troubleshooting] TemplesOfSyrinx:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
[Nexus 6P Q&A, Help & Troubleshooting] crewzta:
This happened to my wife's phone, sent back to Bell. Will see what happens.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?
[Nexus 6P Q&A, Help & Troubleshooting] TemplesOfSyrinx:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.

If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
[Nexus 6P Q&A, Help & Troubleshooting] fapste:
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.
[Nexus 6P Q&A, Help & Troubleshooting] TemplesOfSyrinx:
Food for thought. I used to always root and install custom ROMs on my Nexus devices. Now with Android N, the gap between what a custom ROM does and stock Android is very narrow. I might have to go back to my flashoholic ways.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
You should at least enable the developers menu and tick allow OEM Unlock, just in case you run into a problem on stock. The Nexus 6P goes into bootloops more than any phone I have ever owned. I didn't think I would flash a custom ROM on the Nexus because Nougat is pretty excellent but I ended up using Cortex Rom because I like the Pixel features but can't afford a Pixel.
[Nexus 6P Q&A, Help & Troubleshooting] bcjk8210:
Thanks for the input

Thanks for getting back to me guys - I apologise for not returning the favour; out at work right now and am using a temporary phone replacement that I don't get all my usual notifications on.

Thankfully, my phone is still under warranty and has been shipped to Bell Mobility for repair/replacement. Should have a new one in a couple weeks. Not overly happy with Bell over this experience. They didn't have any loaner phones available in 3 stores I visited and ended up having to use a friend's old Samsung S3. There weren't many options for upgrading or replacement either - no store in Vancouver or Calgary has a Pixel 128GB available. One store had a Nexus 6P, but refused to budge from Bell's replacement policy, despite the evidence that my phone is toast. When I get my replacement 6P in the mail, I'll definitely not make the mistake again of keeping the bootloader locked. I'll continue to run the 6P for now - until either the Pixel comes down in price, or Microsoft comes through with their much anticipated Surface Phone, which I'm keen to check out... We'll see.

Again, thanks for your concerns and input. Hopefully Bell is quick to replace my 6P. Cheers.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
Good luck. As much as I like my 6P I would probably replace it with the Pixel as well if the prices were more reasonable. Hopefully my 6P will actually last long enough for that to happen.
[Nexus 6P Q&A, Help & Troubleshooting] sebasanchez:
Hi guys, I had the previous versión of nougat, updated vía ota several weeks ago. (My nexus is 100% stock). But yesterday my phone goes into bootloop.

I tried return to marshmallow or fasboot the latest nougat, but I got nothing. I'm thinking apply warranty, but I dont know if there's something else that I can do.

Best regards
[Nexus 6P Q&A, Help & Troubleshooting] CyberpodS2:
And the list keeps getting longer and longer...
[Nexus 6P Q&A, Help & Troubleshooting] puddi:
if i get this boot loop can i flash it back to stock and lock the bootloader so i can return to the store where i bought it ?

still under warranty and i did get a random boot loop only once.
[Nexus 6P Q&A, Help & Troubleshooting] sebasanchez:
It's weird. If the bootloop is vía OTA, it shouldnt be a hardware problem.

Sure that Isnt there another thing to do?

Im thinking to relock Bootloader, then apply warranty. :(
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
Unlocking the bootloader doesn't void the warranty on Nexus devices but you should definitely flash stock. If you do a clean install of full stock image (not ota) that might fix your boot loop problem. It has worked for me multiple times after updates borked my phone. But I mean completely clean flash-all.bat update with no modifications to preserve anything.
[ONE Q&A, Help & Troubleshooting] funkyirishman:
Hi

Was running on the CM 12.1 and no issues with wifi. Then I decided to update and went with the RR per below

http://xdaforums.com/oneplus-one/development/rom-ressurrection-remix-m-t3270147

Did a clean install and loaded gapps and everything seemed ok but then had issues with Wifi dropping constantly. I tried google and changed channel on router to channel one and also tried app called Wifi Analyser but still the same issue.

Saw a fix for cm 12 in the below

http://xdaforums.com/oneplus-one/general/fix-wifi-connectivity-issues-drops-t3070045

Not sure if same fix applies to 13 as it seems to be an issue with the CM 13 and not the ROM itself..??

Had to go back to CM12.1 and no wifi issues pity as was happy enough but no wifi is a showstopper. Posted in the RR thread but maybe this might be a CM13 issue so wondering if anyone knows any fixes for it as I may try again

Thanks
[ONE Q&A, Help & Troubleshooting] kroukes2000:
I have the same issue, need to turn off bluetooth, try it it may work for you also
[General Questions and Answers] iamcharlesjay:
I've been installing custom ROMs on my G900F device for several times and I cannot decide which ROM should I use as my daily driver. I love vanilla android and Cyanogenmod 13 is the kind of ROM I've been looking for. But I just can't exactly decide if I should keep using it or what. So I keep switching ROMs such as:

• CM13

• Resurrection Remix

• SmallWiz v6.1 S7 ROM

• PureGoogle (This is one of the best ROMs I've used so far because of the Vanilla Android UI but the SD card can't be read and lockscreen does not work)

• Samperia (I also like this ROM because I find Xperia's UI really good, but again, SD card can't be read, too)

But I still go back to the original G900F firmware I downloaded from Sammobile, and then install a custom ROM again. I reached out to the developer of PureGoogle and Samperia for a fix but i was told to back-up my SD card files and format it in the ROM and then put the files back to the SD card. I have a 64GB card and it has 53GB of data stored in it. And you all know that it takes a lot of time just to transfer that large amount of data to a computer and then put it back to the SD card. I don't have a whole day to do this. And I know I may end up with a bricked phone but I just can't decide which is which. If you have a G900F device and you're using a Custom ROM, can you tell me the ROM you're using as your daily driver? A friendly and kind suggestion will greatly help.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Motawa88:
Anyone know how to get the adoptable storage on MM? Tried the how to for the S7 but it doesnt work.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Bart3n:
If you are rooted you can download "Root Essentials". It has a mode there that will activate the adoptable storage. But remember you can't use your sd card anymore on your computer..
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
Removed
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
Facing errors while repo sync... Please have a look on the attached files
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ECr34T1v3:
Excellent initiative, bro. I can help in any way possible, also call upon my friend @Caio99BR to help. How about if we make a group Telegram to discuss development?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
Yea sure why not, can you get members?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ECr34T1v3:
Yes. Yes, I can. But for now I only have contact Caio99BR who is my friend. Could you give me your telegram? I even create the group, I add and add Caio .. But the contact Ih24n I have not
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
Here, daelitexploiter
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
I am not have a telegram
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
Please help me with that log and xml file
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Caio99BR:
The right is like it:

https://gist.github.com/Caio99BR/e07cf69b7e8777e746fdf4b47671f961

But i have made this too

https://github.com/TeamVee-Kanas/android_.repo_local_manifests

Because path need to be "<folder>/samsung/kanas" not "<folder>_samsung_kanas"

---------- Post added at 03:12 PM ---------- Previous post was at 03:11 PM ----------

Also my Telegram is ... Caio99BR :P :silly:
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] AnDrOiiiD_YT:
Sorry I can't help you so much, I'm a noob :P But I can try help you aslong as I can ;)

And keep up the work together we can boot up CM12 on kanas :)
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
So, install it man. After getting your account PM me there, daelitexploiter
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] samuel.freitos:
Hey bro! I am interested with this, but I am noob with compiling :( so, I will try to help with anything, good luck with that :D
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
Anyone willing to help in building message me on telegram
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] FedericoPeranzi:
Any advanced bro?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Mhmmdadnan62:
; (

Baseband is unknown imei unknown after flash a custom rom lollipop on my core2 g355h please help ?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Nexxit99_Gaming:
Did you get the ROM booted up ?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Anish Prasad:
Glad to see everyone developing a cm12.1 for this phone... May your efforts succeed in making a history
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Anish Prasad:
Hello respectful developer's is the WIP of cm12 going well?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Marquitas:
Work

Is someone working on this?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Nexxit99_Gaming:
Go look at the CM 11 thread they have already booted up cm 12 on there.
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Anish Prasad:
What about this thread??
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] samuel.freitos:
We already have the cm12, look at the CM11 thread from [MENTION=6737662]Ih24n[/MENTION]
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
UPDATE

Sorry, I didn't get it to work because of constant connectivity and bandwidth problems.

Btw, congratulations to [MENTION=6737662]Ih24n[/MENTION] for Building CM 12.1 successfully, I support you bro...!

To other people, "Sorry for making your hopes high...".
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
Ok.. then I have 6 rom base Lollipop again but not uploaded yet and not tested(will test later) it is, Carbon,Tesla,RR(5.4.2 and 5.5.9),Crdroid,PAC-ROM,Temasek. Also I re-work on MM Version (CM13 and RR 5.7.2). If I release the rom I will make a post on personal blog then in XDA(some times very long not make thread but already post in personal blog).

So Stay tunned with me on my blog here SANDROID-TEAM or on XDA thread.
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] AnDrOiiiD_YT:
Finally RR :D

Great work!
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
RR MM maybe will be lost since the 4GB ram from my friend now come back to him. But I am done compile CM13 and will be test on sunday.

Then I release device tree on my github look at here so other dev can do it. https://github.com/ih24n69?tab=repositories
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
You're too fast[emoji16]
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] kirik_world:
Hello developers CM 12.1

Thanks for your great work

I create fix for your OS and instal

I find Error in your OS and fix it

My fix great work and i use it

Thanks for your CM
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
Fix from which bug?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
I Working on RR MM... Hard to compile cause my ram is very low 2GB(maybe some one will be donate his ram to me :v) but finally its compiled...

I dont know will bootingup or not but now I have cm13 and RR MM... So dont forget to always check here @SANDROID-TEAM

Then since CM12.1 only work on H and M version and make bootloop on HN version . So I release Device tree then other dev will compile/develope on HN version... Tree here : https://github.com/ih24n69

DONT FORGET TO HIT THANKS BUTTON!
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] CM_PUNK:
CM 12.1 by ih24n is stable....

Working smoothly????????????
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
Beta but like as stable... Only off charging and change font make bootloop... And maybe GPS too.
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] salman986:
CM12.1 rom for Samsung Galaxy Core 2 [SM-G355H]

its working
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
Yes working...
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] salman986:
can u suggest any cm12.1 or cm13 stable rom for core prime sm-g360h
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] SrWladimir:
you are planning to make CM13? or you will try to fix bugs first?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
Look at on the core prime threads, you will find the cm12.1 and cm13

---------- Post added at 01:20 PM ---------- Previous post was at 01:19 PM ----------

Maybe yes. because I done compile cm13 but hav eproblem on kernel, the kernel cannot bring up cm13 to booting up.
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] neuropsychosis:
Best I've tried.
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
I have only one main issue with CM 12.1, it drains battery very very fast... I am using very few apps (No games, No Facebook, No Messenger, No Twitter, No Instagram). Is there a way to fix it?

Update: No gapps, Xposed, Greenify, Bootmanager (Xposed), DS Battery Saver (Xposed), Lollipop memory leak fix (xposed).

Now the battery lasts 1 and half day(s) ????
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Oscarm99:
Hi! Awesome work!!!!

BTW I cannot connect my core 2 M variant with this cm 12.1 rom to mobile data. It calls and recieves sms but neither 2g nor 3g work

Is this a known issue? Is there a fix?

Thanx in advance
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] rafael_scostaa:
how to solve the battery bug that carries not shut down?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] vdutch:
Hi, i'm using [MENTION=6737662]Ih24n[/MENTION] CM12 rom on a g355h, working great but facing a bug on calls... proximity sensor seems to not be working, the screen never locks/blackout during a call, is this happening to everyone or it's just some problem on my side?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] David.Tay:
Lol this phone doesn't have proximity sensor isn't it?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] vdutch:
Lol, that's a good reason not to work... But... Something must be wrong, because in touchwiz ROMs when you answer a call the screen locks ( i assumed it was using a proximity sensor, it must be something else)
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
Core 2 do not have proximity sensor.... CM defferent with touchwiz. In touchwiz lock when calling is not use proxymity .... How to get lockscreen in CM is use proxymity but we know core 2 not have it so lockscreen when calling cannot used in cm12.1 core 2.
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] vdutch:
Ok, thanks for the clarification ;)
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
If I found the ways to make lockscreen without proximity I will update. But untill now not found it :'v
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Todos123:
Does anyone know how to port this on G355HN?

Is there any way to port this on G355HN? I want this on my Core 2 so much :(
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
Removed. Will switch to XDA thread.

will clean up my post for apply something.
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
[MENTION=5929176]vdutch[/MENTION]
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] vdutch:
I'll try it tomorrow ;)
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] rafael_scostaa:
Ihsan how to solve the battery bug that carries not shut down?
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] shane_master00:
g355hn

Make this work on g355hn, I'm gettin boot loop :(
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
I will make a kernel for HN and you can try solve the bootloop or not.
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
I tried building cm 13.0 with your sources but I got build errors, please check this out
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] sanghrsh1234:
Sim cards not working what to do
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] ItsMeShouko:
It happens many times, unfortunately you have wipe, data, cache, ART-cache and reboot your device. If sim cards works, you are good to go. If they do not work wipe, data, cache, ART-cache, system and flash the CM 12.1 rom again and reboot. Setup your whole device and settings and also install everything you want to. Go to recovery and backup your device from TWRP. If next time sim cards do not work or device gets stuck in bootloop, restore from the backup you took earlier.
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
My device tree still WIP . can to make build done but stuck at bootlogo. You need more knowledge..

---------- Post added at 06:26 AM ---------- Previous post was at 06:25 AM ----------

Look at your IMEI/baseband if null you need AOB1 XSE firmware. To solve it.
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] sanghrsh1234:
Thank you now it is working fine
[Samsung Galaxy Core 2 ROMs, Kernels, Recoveries, &] Ih24n:
Ok Enjoy the real Lollipop rom :)