yashsingh1/xdaforums huggingface dataset:
[Pixel C General] newsted44:
Well, most embarrassingly I am actually stuck at the end of the first section "unlock bootloader." The last task #10 under "unlock bootloader", which is to reboot and re-enable usb-debugging is where I am stuck. I have not flashed a thing. On that step it is stuck on " erasing."

I've read elsewhere this may be a corrupt memory module, but nothing appears conclusive.

Thanks for replying. I love the tablet and would like to use it!

Best,

Newsted
[Pixel C General] followmsi:
Tested your new TWRP version a few minutes ago .. bootloop. :(

Back to xceed TWRP for now.

Does your TWRP version include the fix fastboot option too ?

Thanks

---------- Post added at 01:41 AM ---------- Previous post was at 01:36 AM ----------

Can you try to relock bootloader and then unlock again.

Sorry, no more Input from my side.

Good luck !
[Pixel C General] NYCHitman1:
You're going to bootloop because you need to reflash a kernel. That will always happen on Dragon.

EDIT: Misunderstood what you meant. Will see if I missed something during the compile.
[Pixel C General] newsted44:
Thanks for the suggestion. Yes tried relocking and unlocking bootloader a bunch. No avail. *Update - Google sending me a new one as this one is only two weeks old. I gave up.

Thanks for the input though.

Newsted
[Pixel C General] followmsi:
No, this is not normal on Pixel C and you don't need to install new kernel when installing TWRP.

Thanks for fixing.

Does your TWRP has fix fastboot option too ?
[Pixel C General] susvin:
In TWRP it is unable to mount anything. Reflashed the kernel. However, it is again just booting in recovery.
[Pixel C General] NYCHitman1:
I missed a flag to call for TWRP's fstab in yesterday's image, so that was likely the issue.
[Pixel C General] Ava Pug:
I tried installing this one but I get a bootloop. When I reflash the older one from https://www.androidfilehost.com/?fid=24521665358594788 it boots fine into TWRP.
[Pixel C General] timothydonohue:
has anyone managed to get the april update flashed? i tried flashing the zip in twrp, but keep getting errors (the update is expecting to see stock recovery, but doesn't like twrp, I guess)
[Pixel C General] NYCHitman1:
Yup, I know. Read my last post :) .
[Pixel C General] followmsi:
Are you talking about the April or the May update ?

which .zip did you install via TWRP ?

which version of TWRP did you use ?
[Pixel C General] drewski_1:
yes it does . . . at least the original 3.0.2-0 that was uploaded by NYCHitman1 has the option.
[Pixel C General] followmsi:
Thanks .. good to know.

There are different versions flying around right now.

Some of them seems to be buggy.

Yesterday I have tried one version myself, bootloop when you boot into recovery.

I am back to the good old xceed version for now :)
[Pixel C General] timothydonohue:
TWRP v 3.0.0-0

both april and may update fail. they say

package expects build fingerprint of google/ryu/dragon:6.0.1/somenumber:user/release-keys or google/ryu/dragon:6.0.1/differentnumber:user/release-keys; this device has android/aosp-dragon/dragon:6.0.1/MMB29T/build02070424:eng/test-keys

updater process ended with error:7
done

i omitted the actual number, because it's a build number. also omitted some linux lines that don't matter (checking for md5, skipping because not found etc...)

that's why i'm wondering what's going on. is there a flashable update that will take me from mmb29t straight to m5c14j, and isn't going to be hunting for google/ryu ?
[Pixel C General] followmsi:
Ok, you try to flash the original factory images via TWRP.

This is not working and has never worked before.

Or did you download the OTA zip files manually ?

Here you need stock recovery.

Install them month by month.

The factory images have to be installed via 'fastboot' command.

Or you just use one of the scripts inside .. flash-all.

This will wipe all your data.

To update to May Version, it's ok to flash system.img and vendor.img via fastboot.

Forget April ;)

This month is also a new bootloader to be installed.

Also done via fastboot.

Look into the flash-all script .. there is the command for the bootloader.

Maybe you try TWRP flashable update for May.

http://xdaforums.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591

Hope you understood ..

Good luck !
[Pixel C General] CrazyPeter:
Never had any luck with any of the TWRP builds (3.0.0.0 or 3.0.0.2), they all just keep booting into recovery, if I reboot, it tries to boot up normally, fail and back to recovery.

Scratching my head as to what to do. All I want it root. With the new SuperSU, is there a SIMPLE set of instructions (with links) on how to get a rooted device on a Pixel C with an unlocked bootloader? I don't want custom kernels, or other such nonsense.

Thanks
[Pixel C General] susvin:
Hi,

I faced the same problem 2 days ago. Tried both versions, was ending up with recovery bootloops.

This solved it:

1) Installing the recovery - twrp-3.0.0-0-dragon-ryu-02-11-2016-1.img

2) Installing the kernel - xceed-kernel-google-dragon-v6.10-RELEASE-mxc14g.img

As I was not installing kernel before, it was ending up in a bootloop. Hence, I guess installing/reinstalling kernel is required.

Hope it helps :)
[Pixel C General] followmsi:
Yes, do it like this ..

Install xceed TWRP and the flash stock kernel via TWRP.

You can use the TWRP flashable stock kernel from here.

http://xdaforums.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591

Install SuperSU 2.72 directly afterwards.

Reboot done.

Just a comment ..

If you change recovery versions there is normally no need to re-apply kernel.

Here we need to change the ramdisk of the stock boot.img - to be prepared for SuperSU.

Xceed did this manually before 2.72.

Like in xceed-kernel-google-dragon-v6.10-RELEASE-mxc14g.img.

But the xceed kernel has also other optimization.

As from SuperSu 2.72 on, all stock rooted kernels are obsolete, SuperSU.zip is taking care of ramdisk modifications automatically.

For example to remove forced encryption for data partition .. etc.

Cheers
[Pixel C General] dkryder:
is it still necessary to format /data if one needs to remove encryption ?
[Pixel C General] followmsi:
[/COLOR]

Yes, if it was encrypted before.

SuperSu is changing the fstab and changes "forceencrypted"' to "encryptable".

This allows you to format data unencrypted, which is not possible on stock.

Because of this fstab entry in kernel ramdisk.

---------- Post added at 02:45 PM ---------- Previous post was at 02:35 PM ----------

I have repacked TWRP 3.0.2.0 version - based on xceed settings.

TWRP_dragon_3.0.2.0.img

Added newest SuperSU 2.72 binaries as well.

This recovery.img is booting fine - no bootloop expected. ;)

Download from here: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59

Please test and give feedback.

Thanks
[Pixel C General] houtx2:
Booted fine for me. No bootloops.
[Pixel C General] followmsi:
Thanks for testing !
[Pixel C General] NYCHitman1:
Add this to the fstab to enable vendor image flashing.

/vendor_image	emmc /dev/block/platform/700b0600.sdhci/by-name/VNR flags=flashimg=1
[Pixel C General] followmsi:
Thanks a lot .. new version just uploaded.

TWRP_dragon_3.0.2-0_v2.img

Have checked your twrp.fstab :)

Before you have used ...

/vendor_image	ext4 /dev/block/platform/700b0600.sdhci/by-name/VNR flags=flashimg=1

But as we want to falsh image this way .. make sense to change from ext4 to emmc.

Normal vendor is still mounted as ext4.

I have added one "experimental" line ... which is not working. :(

/devices/70098000.usb/70090000.usb-host/usb* auto auto defaults flags=display="USB OTG";voldmanaged=usb:auto

Maybe I will try ..

/usb-otg vfat /devices/70098000.usb/70090000.usb-host/usb* flags=display="USB OTG";voldmanaged=usb:auto

Most probably it´s not enough to have a "correct" fstab entry to solve the OTG issue. ;)

Thanks
[Pixel C General] NYCHitman1:
Yeah, ext4 is a filesystem -- you can't flash an image to that in TWRP.

As for MTP access - it's not the fstab. It's the sysfs path which is different. The init.rc has to be modified to include this path creation for instances other than on boot.
[Pixel C General] followmsi:
Thanks for your hints .. there were a few smaller issues.

Finally I have manged it :)

Uploaded new version .. as TWRP flashable zip !

Update.ZIP_TWRP_dragon_3.0.2-0_v4.zip

Just made a fresh backup to my usb-stick via USB-OTG .. :)

Finally we can make OTG on Pixel C !

Thanks for all your help ..

Cheers
[Pixel C General] Istvan_86:
Hi guys,

I have the same problem that you but I can´t fix. Do you know any other method to try to solve the bootloop?

I was trying to flash Dirty Unicorns build, Here is my other post with more details: http://xdaforums.com/pixel-c/orig-d...-dragon-05-05-16-t3372823/page10#post66948573

Thanks in advance.
[Pixel C General] yolka:
Problem with Roor Explorer:

Problem with Roor Explorer:

I've followed all instructions and have successfully rooted my pixel c: at least the root checker sais it is rooted, and some apps requiring root, such as "GMD Auto Hide Soft Keys" are working fine.

However, when I try to grant full access permissions to Root Explorer, it sais that the device is not rooted.

Please, help.
[Pixel C General] dkryder:
some apps hard code the location of the su files and as things have changed with the way the files are stored those apps will consider the device not rooted. best thing to do is write the dev of the app and ask them to update the app. you are talking about es file explorer, right? find a different file manager. or a different method of rooting. total commander works. however, it is possible to have a compatibility hack to get it to work..

read the compatibility section,

https://plus.google.com/+Chainfire/posts/N6EARb8LF3d
[Pixel C General] drewski_1:
What root method did you use?

Root Explorer is working fine for me with SuperSU v2.74
[Pixel C General] yolka:
I've followed the instructions posted here:

http://xdaforums.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183

BTW, where can I get the SuperSU 2.74, and how should I properly install it?

Thanks a lot for your help!
[Pixel C General] dangersnake:
First off I wanted to thank orairwolf for this guide.

I have tried a few different versions of the xceed kernel and I've read and re-read this guide and most of the replies. I have my bootloader unlocked and twrp 3.0.2 working but once I get to flashing the xceed kernel and su.img I seem to get stuck. The first few times I tried it seemed that everything was working ok but no root after the final reboot into android. I suspect it may have to do with the su.img that I am using. At this point my pixel c is looping from boot back to the twrp 3.0.2 screen. I'm pretty sure if I follow the steps with the right files I can get back out of the loop but so far nothing I have tried gives me root access once booted back into android.

I can provide more info. Let me know what you need.

EDIT: So I found out how to get out of the recovery bootloop. I am going to try installing the newer supersu next
[Pixel C General] followmsi:
Here you find always the latest BETA version of SuperSU ..

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Install the ZIP via TWRP.

---------- Post added at 12:49 PM ---------- Previous post was at 12:46 PM ----------

Since SuperSu v2.72 the Pixel C is supported now ..

Install SuperSU.ZIP directly onto stock boot.img.

No need to copy su.img anymore.

Cheers
[Pixel C General] yolka:
Thanks a lot for your help!
[Pixel C General] dangersnake:
Everything working now. Thanks!
[Pixel C General] 530farm:
So now with 2.72+ you can just flash the SuperSU zip in twrp? Does it work with stock kernel, or would you still need to fastboot flash xceed before hand? So of I was coming from stock the steps would be :

Flash twrp

Format data to decrypt

Add SuperSU zip to the internal storage

Flash SuperSU zip

Good to go?

Thanks
[Pixel C General] followmsi:
Yes, it's supposed for stock kernel, due to automatic ramdisk modifications.

You can do your way .. or you can ..

Flash TWRP

Use USB Stick to flash SuperSU.zip

Stay encrypted on stock or any other kernel, do not format data.

Reboot

But TWRP still can not access encrypted data partition.

All installations have to be done via USB Stick.

Hope this helps ...
[Pixel C General] 530farm:
It does thanks. So I could flash xceed before flashing SuperSU as well?

Thanks for the tip on getting around decrypting, don't have a c to b USB thing so probably can't test it. However would you be able to adb push a file while in twrp and then be able to access it while still in that same session?
[Pixel C General] followmsi:
The adb push to tmp should may work too .. not tested yet.

Don't know the current xceed kernel .. old xceed was pre-rooted .. e.g modified ramdisk.

If the ramdisk is already modified, SuperSU will skip this part.

But you are still rooted.

It's more "clean" if SuperSU make the changes, as per every SuperSU version change the ramdisk modifications may change too.

Hope this helps..
[Pixel C General] drewski_1:
I think you need to be decrypted (in Fastboot) to get into TWRP.

Can't remember if there's a CF-autoroot for the Pixel

---------- Post added at 01:48 AM ---------- Previous post was at 01:43 AM ----------

Iirc, current Exceed is not pre-rooted.

latest SuperSU is v2.74-2
[Pixel C General] NYCHitman1:
Feel free to try this if you're still encrypted.
[Pixel C General] hugehead83:
June security bulletin is out with new factory images: https://developers.google.com/android/nexus/images#ryu

"Ryu" MXC89H.
[Pixel C General] nigelhealy:
So the latest stock factory images are updated for June. I'm currently on this thread's guide so I'm not encrypted with the modified boot.img.

If I were to move to the Supersu 2.72+ which modifies the boot.img itself, would I get back forced encryption with the stock kernel?
[Pixel C General] NYCHitman1:
Probably. Why not just use a custom ROM (like DU) if you don't mind me asking?
[Pixel C General] followmsi:
No .. still the default behaviour of SuperSU is to change fstab into "encryptable".

So you stay decrypted .. like me and all others too.

But chainfire was in discussions to change the default and keep forceencrypted.

You can change this like you want with Flags on data partition.

But right now the default is still to change to encryptable..

Hope this helps ..

But you can still try DU ;)
[Pixel C General] NYCHitman1:
Lmfao! I totally read what he wrote as "would be remain decrypted" -- time to get my eyes checked :cyclops:
[Pixel C General] spamolamo:
After following these instructions, i can't get Unknown Sources switch to stay on. It grays out as soon as I switch it. Any thoughts?

---------- Post added 11-06-2016 at 12:42 AM ---------- Previous post was 10-06-2016 at 11:53 PM ----------

Nevermind, reflashed supersu and it's OK now.
[Pixel C General] taddyj:
hey guys,

I cant boot into android recovery.. cant figure out why.. I try and install a new one and I get this message

C:\adb>fastboot flash recovery recovery.img

target reported max download size of 268435456 bytes

erasing 'recovery'...

FAILED (remote: unsupported command)

finished. total time: 0.005s

The pixel C still works fine.. BUT I cant lock the bootloader. when I do it says it needs to be recovered.

any suggestions

TIA?
[Pixel C General] NYCHitman1:
Looks like you've tripped the failsafe on the Pixel C. You need to run the fwtool command to reset the flag.
[Pixel C General] taddyj:
The FWTool?
[Pixel C General] Alxoom33:
I've been finding it impossible to get my Win 10 laptop to recognize my Pixel C in Fastboot mode. Everything works, until I use adb to reeboot the Pixel to Fastboot mode and I try to use the fastboot oem unlock command to unlock the bootloader. Then, both the Pixel and the adb window wait for the other and can't communicate.

---------- Post added at 10:34 AM ---------- Previous post was at 10:33 AM ----------

BTW, tried to delete the Google drivers and have the laptop recognize the Pixel from scratch with the same result. Thanks,
[Pixel C General] pkelly517:
While in fastboot, check the Windows Device Manager. Look for the yellow triangle. Reload the driver, using the adb option.

I saw the same thing in Win 7,and that was the issue .

Good luck .
[Pixel C General] NYCHitman1:
Yep. Search for it here in the Pixel C forum -- you'll find it.
[Pixel C General] drewski_1:
If you can get into TWRP, use the Fix Fastboot option. IIRC, under Advanced
[Pixel C General] taddyj:
Thats the thing... I cant even get into TWRP... :/ and no root either.
[XDA Assist] sjoerdwilps:
Is there a way to remove emotionUI from my honor 4X?
[XDA Assist] dottat:
Closing thread as this is a duplicate question already asked.
[General Questions and Answers] Samgarr:
Hello,

i want to hide navigation bar when launcher (Nova Launcher) is displayed. I know how to enable Immersive mode for specific app but not for launcher. It is there any solution? I tried looking for Xposed modules, launchers, ROM, but without succes. My device is rooted Nexus 5 with Cataclysm ROM w/ Marshmallow 6.0.1. Thanks.
[General Questions and Answers] techmatlock:
As we've seen, Android's flagship phones are equipped with some of the latest and best hardware; however, I read articles that mention Apple iOS takes full advantage of Apple hardware. The iPhone 6S with their A9 dual core processor including 2gb of RAM is able to compete with a Nexus 6P that has a hexacore Snapdragon processor with 3gb of RAM.

On the 6th iteration of Android (Marshmallow), why is Google unable to optimize their OS for their phone's hardware like Apple does?

Edit: My first post was never answered, so I'll try to get to the point. Does Apple's iOS communicate with the hardware more efficiently, whereas Android takes more steps to communicate with the hardware; therefore being less efficient?
[General Questions and Answers] TikiThePug:
It's not Google's hardware. Google does not make the Nexus line.
[General Questions and Answers] techmatlock:
I'm not sure why I wrote that. You are correct, every Nexus phone has been manufactured by different companies. On a side note that might change. I read from a few tech news sources that Google is possibly going to take stricter control of the Nexus line and start manufacturing phones under their brand (same way Apple does).

My first post was never answered, so I'll try to get to the point. Does Apple's iOS communicate with the hardware more efficiently, whereas Android takes more steps to communicate with the hardware; therefore being less efficient?
[General Questions and Answers] xdvs23:
iOS is developed explicitly for Apple's hardware. They know exactly what they have to do to take the full advantage of the hardware. They don't have to optimize the OS for other hardware because it only runs on Apple devices. In fact, Android runs on hundreds and thousands of different devices, which all have different hardware. Android needs to be optimized for the specified hardware but it is not so easy and also Android has to run on very different hardware without loosing compatibility.

The other thing that makes Android slower, is that applications run on a virtual machine. Applications on iOS are native and run directly.

Another point is that Android's responsiveness to the touch screen is worse than iOS' responsiveness. If you tap on something in iOS, it is immediately processed. In Android it takes some little time to process the touch event. Also you can tune up your Android system to increase responsiveness by increasing the allowed events per second on the windows manager and reducing the minimum pointer duration. You can also set the surface flinger velocity higher, so stuff on the screen would build up faster and render faster.

So the conclusion is:

In general, Android's responsiveness is not so good as iOS' responsiveness.

And iOS is made specially for Apple devices, so 100% hardware support is available.

Android needs to run on many many devices, so it is difficult to maintain 100% hardware support and compatibility as well as efficiency.

Hope that is clearly enough :)
[General Questions and Answers] Planterz:
"Specs" are also misleading. If specs on paper told the whole tale, AMD processors would be better than Intel, Mediatek would be better than Samsung and Qualcomm, and the Tegra K1 dual core used by the Nexus 9 would be laughably underpowered. iOS also doesn't need as much RAM as Android (remember, it's Linux based) for the way it handles memory. Don't go assuming that the "slow" speeds and fewer cores you see on Apple devices means that the hardware is inferior. If it were, they wouldn't get such impressive benchmarking scores.
[General Questions and Answers] techmatlock:
Is this because there's more 'layers' in Android's OS, so it takes more steps for it to create the response?

Thanks for taking the time to write out that long response. It was very well written and explained a lot for me.
[General Questions and Answers] silenteffectsllc:
This is the same reason game consoles stay relevant years after they come out with inferior hardware. Interesting how it works - better hardware but software can't take advantage cause of the potential audience
[General Questions and Answers] xdvs23:
It is because of the way android is made. Android was initially made for non-touchscreen devices with hardware keyboard. Later Google added the touch feature over the existing functionality instead of changing the whole system to optimize for touch devices.

---------- Post added at 10:43 AM ---------- Previous post was at 09:48 AM ----------

Do you mean that android is linux based or iOS? Keep in mind that Android uses a modified linux kernel, which is optimized to be used with the Dalvik VM (or ART).

iOS is not based on linux. According to Wikipedia, iOS is based on Apple OS X, which uses the Darwin kernel, which is based on NeXTStep, and the top root of that is unix (BSD).

---------- Post added at 10:52 AM ---------- Previous post was at 10:43 AM ----------

Btw, Android has a delay when handling touch input events. When you tap on the touch screen, the kernel intercepts the touch event, notifies the system about it (window manager), then it is redirected to the currently active window and then it is handled by the corresponding application. The window manager is set to handle 30-60 (depends on the ROM) events per second by default, but I have adjusted it to 1200 and you really notice a difference. By setting the pointer duration to the minimum, the responsiveness is also increased. In that way, the delay is kept as small as possible, nearly coming to iOS level.

AFAIK iOS handles the input event directly. When you tap, the kernel redirects the event directly to the corresponding application which handles the input immediately. Also the performance in native iOS apps (they are written in Objective-C or Swift) is better than in android (written in Java, optionally expanded by C/C++ shared libraries).

Another important factor is that Android applications do all the stuff in the main UI thread by default. That means, whenever you tap on the screen, everything is handled in the UI thread, what causes that the UI is freezed for the time the application is processing the touch event. (Although this is a very very small hardly noticable timespan, it results in lag). Poorly developed android applications are very laggy because they don't use separate threads to do time intensive work.

In iOS instead, everything is handled in a separate thread by default. That means that when you tap somewhere, the UI would not freeze or lag during operations in the second thread. The result is, that you don't experience any lags while navigating through an user interface.

Conclusion is: Android is fast but it does not handle touch events so fast. Also, by default, operations are done in the main thread. On iOS they are handled separate.
[Sprint HTC One (M9)] vsawda:
SPRINT HTC ONE M9 Sim Unlock for free here......

SPRINT SAMSUNG ALL Models UICC Unlock for free......

MSG ME ON hangout prerakagrawal85@gmail.com

between 12 -6 (UTC+5:30)...
[Sprint HTC One (M9)] sunilromy:
i sent you invite.