yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] S_2z:
Set GSM/UMTS Band Problem Resolved

:good::good::good::good:

Yep! Flashing the Chroma ROM did it! It's all back to normal now. Thank you scoobysnack soooooooooo much for your help!

what I did are;

1. Hard reset

2. Unlock bootloader

3. Install TWRP

4. Root

5. Install custom firmwares

6. Revert back to stock firmware

7. Install different 'radio' images

8. Install different stock firmwares

Unfortunately, none gave me a positive outcome.

Last Hope Was:

I flashed Chroma, a lightweight AOSP ROM focused on battery, performance and stability.

http://xdaforums.com/nexus-6p/development/rom-chroma-11-08-2015-lockscreen-navbar-t3244444...

The following link is for Chroma download and installation instruction:

http://nexus6proot.com/nexus-6p-custom-roms/chroma-rom-for-nexus-6p-android-6-0-1/2/

This custom ROM for Huawei Nexus 6P was first recommended by a scoobysnack:cool:. It works with a proper selection of bands according to your country.

On the dialer, use this codes *#*#4636#*#*

Selection for different bands would then available.
[Nexus 6P Q&A, Help & Troubleshooting] XxMORPHEOUSxX:
I'm glad you figured it out. However, If you tried the factory image and it didn't work, that's a problem! You should have had cellular service right out of the box and definitely after you flashed the factory image. Unless you did not actually try the factory image itself. Can you clarify. Because if that's the case you have a defective unit and it will be an issue when you need to actually restore your device some day. Also don't want people to get the idea that a factory image is not a fix for this.
[Nexus 6P Q&A, Help & Troubleshooting] scoobysnack:
Flashing the factory image does not work. I messed with my phone for 4 hours trying to get of to work again. I was originally on chroma when I screwed my bands up. That's how I knew about the other bands. I believe it only fixes international phones . I'm in the US on VZW and flashed factory image and had to select band 6. So depending on where you are depends on what method you have to use to correct the problem. And yes a sticky and FAQ should be made as a lot of people seen to have this problem.
[Nexus 6P Q&A, Help & Troubleshooting] XxMORPHEOUSxX:
The images work on either variant. It confuses me why a factory image would not fix it but I'm sure there is a reason. Its new to me though. What's weird is I am on Verizon in the US as well. Works right out of the box for me and any issues that I have come across have been fixed by a factory image. I wonder if people having problems on Verizon are having issues due to network and sim card provisioning issues and by switching bands you are fixing it but you are not on the normal bands maybe. I know some people on Verizon had to call and tell them to activate LTE on their line even though they were supposed to be getting it. And that fixed the no service.
[Nexus 6P Q&A, Help & Troubleshooting] S_2z:
Nexus 6p - Set GSM/UMTS Band Problem

I guess the reason why a factory image did not fix the problem is because my phone version is US not International. And I am now not from US, originally from Middle East. So there is no compatibility between US and the international bands. The only choices I had from the Bands are USA Band, 6 and 7. I am guessing that the International version has more options and compatible with variant bands.
[Nexus 6P Q&A, Help & Troubleshooting] mohawahba:
guys. try to install chroma rom , it has several different bands. just to get it working . then return back to stock if you want :) i had the same issue and i had data working and sms without calls until a guy helped me ( im very grateful for him ). i hope it works. please let me know :)

[MENTION=497842]scoobysnack[/MENTION] .. man, I came to help but you were faster haha
[Nexus 6P Q&A, Help & Troubleshooting] S_2z:
I used Chroma ROM it gives you proper selection of bands according to your country.
[Nexus 6P Q&A, Help & Troubleshooting] erpsindhu:
Similar problem

I have the same issue and my carrier is Airtel - from India. Will Chroma work with this?
[Xperia Z5 Q&A, Help & Troubleshooting] FYLin21:
I tried restarting the phone, but then Google Play and all my apps were gone, it's as if the device is partly in Ultra Stamina Mode with other functions still working. Google Play services keeps crashing also...

I think maybe I pressed "activate/deactivate" Ultra Stamina too many times as it was not exiting out of the mode at all...
[Xperia Z5 Q&A, Help & Troubleshooting] Skyet:
same situation...got it fixed yet?
[Xperia Z5 Q&A, Help & Troubleshooting] FYLin21:
Ouch!

I just did a factory reset and everything is fine now. Unfortunately I didn't back anything up and once this glitch occurs you can't! (you can't even view your IMEI number)

Sony gave me this reply but it wasn't helpful as I already did the factory reset:

1. If the issue is caused by a glitch on the software, you can try to force the device to restart, connecting the device to the wall charger and then press and hold down the volume up and the power key together at least 5 seconds, or until the device vibrates 3 times, then power on the device.

2. If that does not work you will need to find the OFF key that is next to the SIM card, is a red/yellow button, and please press and hold down the OFF button for 120 seconds.

3. If none of the steps stated before works, you will need to perform a factory data reset, please remember to perform a backup of the information because this process will reset the device into factory settings.

Factory data reset.

From your Home screen, tap the Application screen icon.

Find and tap Settings > Backup & reset > Factory data reset.

If you also want to erase data such as pictures and music, which is saved to your device's internal storage, mark the Erase internal storage checkbox (does not affect the SD card).

Tap Reset phone/tablet or Erase everything.

If required, draw your screen unlock pattern or enter your screen unlock password or PIN to continue.

To confirm, tap Erase everything.

If none of the steps previously taken solved the issue, in this case I will recommend you to perform a software repair to your phone, here are the steps on how to do it, we have an extended guide that should help you fix the Pattern Lock issue on your phone, please follow the instructions carefully:

We have an extended guide that should help you fix the Pattern Lock issue on your phone, please follow the instructions carefully:​

Let me know what happens! Now I'm afraid of using Ultra Stamina Mode.
[Xperia Z5 Q&A, Help & Troubleshooting] Skyet:
Thanks for the information. I read something about the step 1, but i tried and no luck..I did a backup before resetting my sony z5p, but the backup could not be loaded because it is saying that the Android OS is old (I guess Safe-mode). Luckily the Backup & Restore inside the xperia phone backed up almost everything, just some apps' chat history is gone.

I'm very afraid of using the Ultra Stamina mode, even know i am certain of the error that i (might have) made.
[Xperia Z5 Q&A, Help & Troubleshooting] FYLin21:
Apparently quite a few Z3/Z2/Z1 users have also encountered the same problem - appears to be a Lollipop-related bug. I couldn't even backup as the only option under "Backup & Reset" was Factory Reset
[Xperia Z5 Q&A, Help & Troubleshooting] Arturiosan:
try to enter Ultra Stamina again, and then quit it

It helped me
[Nexus 6P Q&A, Help & Troubleshooting] ThaBlobFish:
So, last night I was messing around with some custom roms, and tried installing CM, I accidentally installed CM recovery as the boot img, and tried to backup from my backup file that I created via TWRP.

Now, when restoring i get into a bootloop, i think, and if I'm trying to install a custom ROM i either get a status 7 error or it can mount /system. I tried going into the Mount tab in TWRP and checking the system check-box, but it won't let me.

Help XDA-kenobi, you're my only hope.
[Nexus 6P Q&A, Help & Troubleshooting] XxMORPHEOUSxX:
Flash a factory image and start fresh. And don't flash the wrong img to the wrong partition this time :-p
[Nexus 6P Q&A, Help & Troubleshooting] ThaBlobFish:
... Device won't show up when i try to list it in CMD under fastboot devices... makes it knda hard to flash. Maybe I should just stop messing with this ****...

Disregard, I am apparently mentally challenged...
[Nexus 6P Q&A, Help & Troubleshooting] XxMORPHEOUSxX:
You did not mention that in earlier post. If you can't flash via recovery and can't use fastboot then you are screwed. Take this as an expensive lesson to always triple check what you are flashing.

---------- Post added at 02:04 PM ---------- Previous post was at 01:51 PM ----------

After thought. Have you tried flashing just a boot img from recovery?
[Nexus 6P Q&A, Help & Troubleshooting] ThaBlobFish:
I used an old directory with old files which I used to root my M7, that's why it didn't show up. It's all fixed now.
[Nexus 6P Q&A, Help & Troubleshooting] XxMORPHEOUSxX:
Oh, Good. Glad you figured it out!
[X Style (Pure) Q&A, Help & Troubleshooting] Laucien:
Hi!,

I have a 16gb Moto X Style with a decently fast 64GBs sd card and have it formatted as internal memory (mostly so I can put all my spotify music on it without having to deal with workarounds on the ****ty app). Everything works great and I'm quite happy and all that but I've been having issues with transferring stuff back and forth between my computer and my phone from day one and want to know if it's common or if I'm doing something wrong.

My issues are this:

If I connect the phone to my computer via USB Windows recognizes it but I can't browse it's content. It's empty.

If I use an app like ES File Explorer to transfer files through wifi I can save stuff and browse it on the phone but if I transfer a rom and then boot to TWRP it's not accessible.

TWRP can't make nandroid backups at all.

Are all those side effects of the sd card being encrypted? Am I doing something wrong?.
[X Style (Pure) Q&A, Help & Troubleshooting] Orion116:
Change USB mode to mtp
[X Style (Pure) Q&A, Help & Troubleshooting] Speculation:
I'm having the exact same problem. I too formatted my 64gig sdcard and can not make back ups. I get error code 5 in twrp, unable to create back up folder. I also can't browse some folders, I use fx file explorer and when I open some folders they say access denied. I have given the app permissions as well. If anyone can help it'd be much appreciated!
[X Style (Pure) Q&A, Help & Troubleshooting] Speculation:
Haven't figured it out yet. Also can not install busybox using any of the install locations
[Galaxy Grand Prime Q&A, Help & Troubleshooting] dellthehacker:
I really liked that trapkernel root that ShinySide created. I was wondering if any one knew a good method for the AZ model? I own both models I tried to flash it but it didn't work for the AZ but the T worked perfectly. I used the root method to add 20gbs of space to my internal memory so that i could install more apps because I love the phone beside the memory since it comes with 8GBs and you only get access to 3GBs. :fingers-crossed:
[Pixel C Original Android Development] cheep5k8:
This is UNOFFICIAL TWRP for the Pixel C. That said, the TeamWin team greatly helped me in getting this working. But at the same time, neither TeamWin nor me take any responsibility whatsoever for any undesired outcome resulting from any kind of use of this project and project files! If you don't exactly know what you're doing then just walk away and do something good. Don't touch any options of which you don't exactly know what they're for!

What works:

* So far, everything; encryption support should work, but some feedback on this would be welcome

Problems:

* The GUI will be sometimes slow, sometimes super slow. This is probably due to the high screen resolution of the Pixel C.

How to install:

- Unlock bootloader

- In the bootloader, run "fastboot flash recovery <.img file>"

- Reboot into Pixel C bootloader

- Boot into recovery (or later on/from Android through "adb reboot recovery")

If the recovery doesn't stick after booting into Android:

- Do the install procedure as above

- Do NOT reboot into Android

- Press Vol-Down + Power until you see the bootloader menu

- Select "Boot into Android Recovery"

- When in TWRP, mount system

- Using TWRP's File Manager, or using adb, delete the file "/system/bin/install-recovery.sh"

- Reboot

After doing this, OTAs won't work any longer, but they wouldn't work anyway after installing TWRP. Just so you know ;)

DOWNLOAD

twrp-3.0.0-0-dragon-ryu-02-11-2016-1.img

SHA1 hash: 3e97aae6cc18975683eda2bd3732faaecec14166

Changelog

:: 01-19-2016-1

- Removed screen timeout by default, since the GUI is very slow and the screen unlock slider is very hard to use

- Added an option to fix the Fastboot Full Cap flag directly from TWRP; you find the option in "Advanced". If the Pixel C should ever not let you flash in fastboot, boot into TWRP, select Advanced -> Fix Fastboot, swipe to confirm, and you're set.

:: 02-11-2016-1

- Rebased on twrp/android-6.0 branch (i.e. upgraded to TWRP 3.0.0-0)

The recovery is based on the Pixel C stock kernel.
[Pixel C Original Android Development] DaConcho:
Awesome! I can survive without root for the time being but being able to enable multiwindow would be amazing!

Thanks!

Edit: I am getting a FAILED (remote: unsupported command) error and cant flash this. Anyone know a work around?
[Pixel C Original Android Development] brando56894:
Worked fine for me with "fastboot flash recovery [image name]" did you unlock your bootloader? Also root works just fine, you just have to boot from your PC.
[Pixel C Original Android Development] DaConcho:
I did unlock my bootloader but can't get anywhere. Tried updating my sdk, drivers everything. I guess I will have to keep playing with it.

Edit: I relocked my bootloader, and then unlocked it again and now it is working. If anyone else runs into this give it a try.
[Pixel C Original Android Development] dkryder:
it successfully installed on my pixel c. is reachable as the Android Recovery option. and boots to bootloader to allow boot of boot.img

this is a good thing. thanks to all involved.

it's been 1 month since release and good way to celebrate.
[Pixel C Original Android Development] xennos:
Good work. Thanks you :)
[Pixel C Original Android Development] doumer:
hooray thanks! just to clarify: I need encryption disabled to use twrp or just to flash SuperSU?

I'm currently using phhusson's noverity boot-img to boot and with a modified vendor img root is working fine while encryption is enabled ... just having to boot via fastboot every time is a bit awkward. And since I don't know what happens if the device got stuck and reboots itselfe without the modfied boot it would be awesome to have at least a nandroid backup ;)
[Pixel C Original Android Development] cheep5k8:
Hey... You can use TWRP even with encryption enabled, you just can't write anything to /data.

However for the next build I'm going to enable TWRP's decryption option and see if it works with the Pixel C. If it does I'll post a new build this evening (European Time).

I tried the systemless SuperSU on a decrypted /data partition but it wouldn't work (bootloop), clearly there's a lot of ground to cover here, but like I said maybe the decryption functionality will help us here.

EDIT: I'm also working on a boot.img with disabled forced encryption. Looks like we're going to get proper root very soon.
[Pixel C Original Android Development] Khaon:
Hello thank you for this. Yesterday I tried to build as well twrp but it wasn't fully working.

I just imported this config with TW_INCLUDE_L_CRYPTO := true && TW_INCLUDE_CRYPTO := true

I didnt copy paste the twrp.fstab I added but added its path to BOAR_smthing.

Also I used omnirom's android-6.0 revision with dragon's device tree.

The recovery seems to boot, as

adb devices

returns XXXXXx recovery.

Also I can reach the device's shell with adb shell. Just the screen stays black.

I was wondering if I missed something. Is your device tree available online ?
[Pixel C Original Android Development] cheep5k8:
Not yet. I'm going to upload it later on to the TWRP devs for official inclusion.

You need to merge the minui patch so TWRP can use DRM for video on the Pixel C; there is no fb0 device.
[Pixel C Original Android Development] dkryder:
there were some new boot images out today. i flashed one of them. when i boot to recovery the sdcard is not able to be mounted. do you have any suggestions on what i need to do or look at in order to get it fixed?
[Pixel C Original Android Development] cheep5k8:
Because /data is (force-)encrypted. I uploaded a new TWRP build with various fixes but decryption doesn't work.

What I also found out is that the boot image for the Pixel C is NOT an Android boot image (!), but a ChromeOS one. This puts a lot of things in doubt, for example I am not sure if systemless SuperSU can handle this.

But, I'm working on all that ;) (working on boot img without forced encryption right now, but so far it doesn't want to boot completely)
[Pixel C Original Android Development] cheep5k8:
OK, so, I'm running the device unencrypted now, but there are many issues still to resolve.
[Pixel C Original Android Development] cheep5k8:
OK guys, if you really want actual SuperSU, and other root stuff, and decrypted /data, here's how it works but it's complicated and will only work tethered as far as I can tell.

First, download this boot image: dragon-boot-encryptable-01092016-1.img

Now here are the steps:

- make sure you have a stock boot.img handy in case something goes wrong (as usual I can not take responsibility but chances of bricking are extremely slim if you know what you're doing)

- boot into fastboot

- flash the above boot image to boot ("fastboot flash boot dragon-boot....")

- flash the TWRP recovery (latest version) ("fastboot flash recovery twrp-dragon-...")

- hold power+vol down pressed.. the device will turn off, keep it pressed even as it turns off, it will turn on again and you are in the coreboot menu

- select "Android Recovery" which will start TWRP

- in TWRP, select system as read only when it asks ("never write onto the system partition").. my boot image does not disable dm-verity which seems to be still in effect, so if you change /system, the Pixel will refuse to boot (even though it's unlocked... no idea)

- once in TWRP, go to "Wipe" and then choose at the bottom "Format Data" (just wiping will not work)

- when that's done stay in the recovery

- get SuperSU 2.66 from somewhere and flash it through TWRP (using sideload for example)

- when it's done, go to "Backup" in TWRP and only backup boot (the kernel) - no password - no compression

- somehow copy the backed up kernel from the device to your computer ("adb pull" for example), but in no case let the Pixel boot into Android

- when that's done, tell TWRP to boot back into the bootloader

Now get ready to be real quick...

- boot (just boot, not flash) the TWRP backed up boot image (it's 32MB large and called boot.emmc.win, but it's all good): "fastboot boot boot.emmc.win" (and now you have to be rather quick)

- It will boot up for a second and then go back to the "The OS will boot in 30 seconds screen"

- Again press power+vol down and hold it, even as the device turns off, until you're in the coreboot bootloader

- There, choose fastboot again

- And once again boot the boot.emmc.win image ("fastboot boot boot.emmc.win")

- Now let it boot up

- If everything went OK you should be in Android, with decrypted /data, and SuperSU should be installed and working

If you want to avoid being encrypted again (although SuperSU should survive that) you will have to boot tethered everytime using that boot.emmc.win image.

Known Issues: Somehow because /data is decrypted, "Security" settings in Android will crash. Hopefully you don't need anything in there. You might also want to skip setting a lock pattern or pin when doing the initial setup, it might crash too.

So far, I tried installing AdAway using root which worked just fine.

If someone figures out how make this untethered: you da real MVP!
[Pixel C Original Android Development] oRAirwolf:
Thank you sir!! I will report back if I encounter any undocumented issues.
[Pixel C Original Android Development] cheep5k8:
OK so I've managed to install Xposed, was pretty straightforward except for the tethered boot. Still looking into making it untethered.
[Pixel C Original Android Development] dkryder:
since your modified boot and no encryption it seems to be smoother in graphics. in any event, the thing worked in format of data and install of the supersu zip. so, well done.
[Pixel C Original Android Development] ZiggSVO:
So, followed these instructions and whenever I try to reboot into recovery I get the no command screen. Am I missing something? lol

Edit: So figured thats the stock recovery stuff. Got to the stock recovery but can't get into twrp

2nd Edit: I redownloaded the file and didnt rename it shorter this time and now it works...weird :p
[Pixel C Original Android Development] Khaon:
Thank you for those informations :p.
[Pixel C Original Android Development] xploitnt:
Thank you so much for this! Aside from the laggy UI, which isn't an issue since we got TWRP (f yes!!!), this is amazing. Do you foresee any issues flashing fonts? I am not familiar with ChromeOS and Android structure combination as it seems there is a lot of talk about. Flashing a file that replaces the stock fonts with the ones of my choosing hypothetically should not pose a problem to /system/fonts/, correct? Thank you for your work :D
[Pixel C Original Android Development] cheep5k8:
You should then use a kernel to disable dm-verity as well so you can modify the /system partition freely (mine or phhusson's kernel) but other than that I'm pretty sure flashing a font should be just as fine as on any other device ;)
[Pixel C Original Android Development] xploitnt:
I have rooted my Pixel via your boot image :) is that the boot you are speaking of? Thanks for the quick reply!

Also, I did root the non-encryption method :)
[Pixel C Original Android Development] cheep5k8:
OK, then you're good to go! BTW check the kernel thread for updates of my kernel since I'm updating it frequently with patches and fixes. Right now I'm debugging the WiFi issue and have good results after fixing a kernel bug and updating the WIFi firmware on my Pixel C ....coming soon! :good:
[Pixel C Original Android Development] xploitnt:
Great - you're a godsend to the stagnant Pixel C community :P I was so happy when I checked the thread and finally saw un tethered root! Thanks again, I'll let you know how everything flys :highfive:

---------- Post added at 03:57 PM ---------- Previous post was at 03:18 PM ----------

Flashed perfectly :D . Root, TWRP, and a gorgeous(er) UI! What else could you want?!?! Thanks again bud :)
[Pixel C Original Android Development] cheep5k8:
You got it ;)
[Pixel C Original Android Development] xploitnt:
Confirmation number: 6VU009882S0067916 - couldn't resist. Enjoy & Happy post Holidays! :silly:
[Pixel C Original Android Development] dkryder:
would it be possible to create a changelog of sorts in the original post? i just curious cause i noticed the image is quite a bit smaller since the original #1= ~9MB /#4= ~6MB
[Pixel C Original Android Development] cheep5k8:
Hey,

Since I started building the kernel from source (uh.. the timespans are so short.. basically, yesterday?) I've enabled LZMA compression on the kernel image, since the ChromeOS depthcharge bootloader of the Pixel C can handle that, and the image is much smaller, so why not? (Not sure if a normal Android bootloader can) That's really the primary reason for the size difference.

But you're right, I've included a few patches and fixed a couple of bugs in the kernel which is not exactly obivous. I'm going to add a changelog but I'm down with a really terrible flu at the moment so I have to take it a bit easy, and also have to find a suitable format for the log.

(it's my first public kernel so if anyone has a suggestion for how or where to best store the changelog I'm all ears :)
[Pixel C Original Android Development] dkryder:
10-4. take care.