yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] :
Ok, first device tree looks incomplete ( no fstab, no partitions sizes on BoardConfig...) and the second is for lollipop. Also, from those recoveries you mention only cwm will be available for cm-10, and maybe philz but without touch (CTR for cm 10 was only for mtk phones). You need the device tree the recovery version and the building environment to match.

Now reading again your first post the flashing in the wrong partition doesn't have anything to do with recovery but with the flashing process - or maybe I didn't understand this part right.

To get more help you have to be open and to make public available your sources so the people can check them and spot the error. If that device tree from first link is the one you are really using (although I don't think so because I didn't see your fstab in it), then you need to improve it because that is not complete. The building error you say can be caused by a case letter, a wrong device name in any of file, a wrong defined path, and so on... Without seeing the actual device tree I can't tell which is.
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
ok, i'll upload it on github

---------- Post added at 09:08 PM ---------- Previous post was at 08:34 PM ----------

I've uploaded sources here SOURCES.

I've another question: Can I compile cm 12 on cm 12.1 tree?
[Android Q&A, Help & Troubleshooting] :
Ok, first you should build it in CM12.1 because the device tree is made for that. You may want to check this one too because it seems better.

Now, your device tree alone and just as it is won't compile because it needs some additional things like this and this or something like these. If you want to build only the recovery with a prebuilt kernel then you need to extreme slim down that device tree, to add arch definitions in your BoardConfig and a rule to add as built utility the dbToolCM from kernel/tools folder since your custom mkbootimg.mk uses that.

Apart from that in your existing device tree you have to do some modifications:

- remove this from cm.mk because it doesn't exists and it will trigger an error:

$(call inherit-product, vendor/cm/config/gsm.mk)

- add this in vendorsetup.sh because custom recoveries have to be built as eng:

add_lunch_combo cm_a5ultexx-eng

- if you plan to use this device tree as it is you need to add also in device_a5ultexx.mk this line because these are device config but they are not included in any of your device files:

$(call inherit-product, device/samsung/a5ultexx/common.mk)

And probably you will need to add samsung repo in hardware folder too.

I think it will be better to study the github repos of the guy I gave you as an example to understand how it works the entire samsung ecosystem. I made the changes I told you and the recovery started to build but stopped because I didn't have a kernel folder for that device and since I don't have any samsung device I don't want to download it only for tests.
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
I've deleted mkboot img and I add some modifies to the tree such as delete mkbootimg and delete twrp entries to boardconfig.mk and minor changes, now I'm compiling the recovery :fingers-crossed:

---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------

I've another question :D : Do I need kernel sources, because I read that for building recovery I can use prebuilt kernel?

PS= I modified the kernel tree, to get no errors related to kernel sources, now I'll upload it, if you want to take a look
[Android Q&A, Help & Troubleshooting] :
Seems buildable to me.
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
Yep, I'm building your recovery, thanks for having uploaded your source, for your magnific recovery and... for your help :)
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
Hey, I'm still here, because I had a problem with your new recovery. Two days ago, I've compiled cyanogen recovery and it worked very well, but when I compiled your recovery (on cm 12.1) I had a problem with the GUI: when I enter in recovery, I stuck on this image (see attached), but when I tap reboot phone button (i think it is that), my phone reboot, so, i think it's a problem related to the GUI, but i don't know. You can find updated device tree HERE and unpacked recovery.img HERE
[Android Q&A, Help & Troubleshooting] :
I can't see anything in the picture, but if the recovery doesn't work just build first twrp and if you get that working it will be easy to make my recovery work. I'm not an expert in twrp but there are so many around here.
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
Sorry for bad quality, the picture shows the splash screen, but it's all ok on unpacked recovery.img?
[Android Q&A, Help & Troubleshooting] :
The recovery.img can't show in any way if it will work or no. It looks ok, except the fact that are missing few folders (but those are empty anyway and probably they got deleted on upload). You really need to build and boot a twrp first and only after that there is a chance to fix this.
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
Yesterday I built twrp recovery, but I'm getting the same problem: the gui won't start. An hour ago, i booted in your recovery, I tapped the screen, and when I booted my phone my data has wiped, so my problem is related to the gui that won't start. I remember I removed this line:

#else
ionAllocData.heap_mask =

from minuictr/graphics_overlay.c, because I got an error. Is it the cause of my problem?

Thanks in advance :)

PS: Does your recovery support snapdragon processors?
[Android Q&A, Help & Troubleshooting] :
Since I don't have a device with qualcomm I don't know. Maybe someone with knowledges will test and tell me if it does.

That's the reason I told you to focus on twrp first. For twrp there are many developers with qualcomm devices and they can help you to solve the boot. After that if you came here and tell me what did you have to do to make it boot in twrp I can fix it for my recovery too.
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
For "make it boot" you mean settings in BoardConfig.mk?

PS: your recovery boots :) is the gui that won't start
[Android Q&A, Help & Troubleshooting] cosinusdealfa:
[MENTION=5186178]bluefirebird[/MENTION] Will this guide work for CM12.1 repo too? I want to make CWM recovery, and after that, try and make a ROM. The device is Allview X3 Soul, which has MT6753 SoC, and the recovery unpacking worked without "unpack_MTK_img" script. It's my first time trying to build something for an Android device. I get this error:

make: *** No rule to make target `bootable/recovery-cwm/etc/init.rc', needed by `/home/cosinus/Workspace/X3_Soul-CM12.1/out/target/product/X3_Soul/ramdisk-recovery.img'. Stop.

Would you please tell me how to fix this?
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
You can't compile cwm on cm12.1 source, because the cwm supporto ended on cm11 sources, and you nave to compile on cm10 or cm11 (if u want philz)
[Android Q&A, Help & Troubleshooting] cosinusdealfa:
[MENTION=7511870]DeadSquirrel01[/MENTION] Thank you for your answer. I will try using CM10 or CM11 sources then.
[Android Q&A, Help & Troubleshooting] DeadSquirrel01:
If you want to compile in cm12.1 u can compile the new ctr recovery by [MENTION=5186178]bluefirebird[/MENTION], it's like cwm but with more features, I love it :)
[Nexus 9 General] bynarie:
http://download.cyanogenmod.org/?device=flounder

BOOT.IMG - link to boot.img for cm12 n9 that does not force encryption . remember to wipe userdata, or will not work.

PA Gapps

Basketbuild Gapps
[Nexus 9 General] Ishwara Sandesh C M:
:cool:Yeay!!!! We got it.. :thumbup::D
[Nexus 9 General] b1bub4bu:
Can anyone post a video of ROM please :) ?
[Nexus 9 General] tyvar1:
Does this mean that the cm based roms here for the nexus 9 will be better? :)
[Nexus 9 General] garva1:
Thanks for this.
[Nexus 9 General] Hashbang173:
Not really, device tree for N9 is extremely similar to mine. Plus it currently has forced encryption.
[Nexus 9 General] vboyz103:
Installed latest nightly with ElementalX kernel and everything looks good. I like the Expanded Desktop view to maximize viewing screen. Moreover, the options on launcher to show big icons is a plus.
[Nexus 9 General] albsat:
What gapps do they recommend?
[Nexus 9 General] edgardo_0691:
Try this version of Gapps http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900
[Nexus 9 General] mag13:
Does anybody get trusted face working?
[Nexus 9 General] Winesnob:
How's the performance of CM12 compared to stock? It made a HUGE difference on the 2012 Nexus 7, so curious if the same on the N9.
[Nexus 9 General] aleandre1974:
Yes, I am also interested to know about the performance and, especially, battery life benefits of CM12 on our Nexus 9. I am refraining from rooting my 5.0.1 stock for the moment hoping that 5.1 finally adresses the governor "issue" in order to get better battery life and less hiccups out of this thing while browsing, but if CM12 delivers already, I might just go all the way and install it right now.
[Nexus 9 General] Vinzie:
Same here, don't want to reset my tablet for every new rom, but if CM12 offers better performance/smoother experience/better battery I'm willing to switch roms again. Otherwise waiting for 5.1 to be released...
[Nexus 9 General] nyaznteen:
There are sound bugs that the clicking volume like keyboard can't be lowered. Charging is very slow. Performance is comparable or slightly slower than stock Rom.
[Nexus 9 General] GiantAxe:
this,right here.

The charging isnt even just slow, its eratic honestly. if i use a 1.2 amp charger it takes over 13 hours to charge. using a 1.8 amp one reduces it to around 8 hours.

Its stable and all, but the charging issue, thats the reason i've decided to go back to stock rom.
[Nexus Player Q&A, Help & Troubleshooting] alinescoo:
Nexus Player is a sad/simple/boring device. Its remote is really silly and useless. Anyone who have used an Air mouse type remote (Lg Magic Remote or Samsun's one) knows how comfortable it is to have a pointer on the screen and move the hand to reach the cursor where you need. Google decided to use a simply remove which basically is a left/right/left/left/down/down/down until you reach your option.

I've bought a USB OTG cable and connected my mouse. While the cursor is moving on the screen and it works on some apps, in most it does work. So for instance, on a game I can't click on the buttons... Is there a way to make the mouse clicks on all apps ?

Also, some apps which are forced for portrait orientation, will be displayed lying as the tv is 1920x1080. Any way to force the orientation of apks ?

Thanks.
[Nexus Player Q&A, Help & Troubleshooting] midnightzak:
I've had this problem too. Apparently some developers code in touches and/or mouse clicks, and some only code in the touch command. That is why some games aren't working for you.

You've got two options, either complain to the development team to add mouse clicks (which I'm told should be an easy thing to do) or use the DroidMote app by Zulu.
[Nexus Player Q&A, Help & Troubleshooting] alinescoo:
Thank you [MENTION=2792805]midnightzak[/MENTION] for making it clear to me. It seems that even the games from the Google Play for android TV are not working as supposed. For instance I installed Minion Rush (which is officially supported) and after it installed on start, it ask me to enter my age but I can't enter it because when moving around with remove for the Age editbox and clicking ok button does nothing, no keyboard popup. Tried it with controller too, same thing.

Another short question. On Chromecast on my LG smart TV I had Simplink enabled. Not sure if because of this, but when I started to cast a video from my phone, the tv switches from cable input to chromecast input. This does not work for Nexus Player, I need to manually switch input to HDMI port of the player. Is this normal ?

I have a magic motion remote for my LG tv, which is basically an air mouse remote. LG firmware has an option to control other devices connected through HDMI with the remote and when I try to add a new device, I get all sorts of Box sets from different producers. I was wondering if there is a way to make the remote work on nexus player.
[Nexus Player Q&A, Help & Troubleshooting] philhachey:
The nexus player doesn't officially support HDMI CEC which is the protocol required for the auto switching of inputs to work. It's also what would make your remote work unfortunately.
[Nexus Player Q&A, Help & Troubleshooting] opticron:
I have a LG "smart" TV as well and at first the Nexus Player did not appear to support the expected HDMI-CEC functionality (input switching and magic remote passthrough). On LG "smart" TVs, you have to re-enable HDMI-CEC for that port when you switch devices. This is also sometimes a very annoying setting to find if you haven't touched it in a while.
[Nexus Player Q&A, Help & Troubleshooting] alinescoo:
[MENTION=2653229]opticron[/MENTION] so you say that you LG TV does work with Nexus player and also you can use the magic remote for it ? Can you tell me some more details on how to enable the HDMI-CEC on the tv for the player HDMI port ?

My other concern: should the cable be of any special type to support CEC ?

Later edit: I have replaced the HDMI cable I had with an newer cheap one. The older one did not work with simplink enabled, while the new one does. I can use the lg remote to navigate around the nexus player. The cursor does not trigger any action (too bad) but up/down/left/right/ok/back works from the magic remote.
[Nexus 6 Q&A, Help & Troubleshooting] veenab:
Does rooting void my warranty? And i can unroot it fully ? By fully i mean is there a counter associated with rooting similar to knox counter in Samsung?
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
There are various different schools of thinking here. I take my answer from when I had a nexus 5 - in that if you unlocked, Google didnt care - which meant if you bought from Play, you were fine. However, if you bought elsewhere, you had to send it to LG and they routinely refused warranty on unlocked phones, regardless of how many laws they "broke" by doing that. With the 5, there was a tamper flag, but I haven't seen any evidence that one exists on the 6 yet, meaning relocking it *should* be fine if you can.
[8125, K-JAM, P4300, MDA Vario ROM Development] prinsipe21:
i have my HTC 8125 mobile with WM5 OS.

i didnt unlock my CID yet but I will unlock it later right after if someone answers my important question that always twinkling in my mind.:confused:

Upgrading roms for WM5 to WM6 is just like installing a application? ( sorry coz this is my first time to do this.)

currently downloading Xplore1.1 and farias rom. is it alrady overclocked when i installed one of those? do i need to overclock my mobile?

thanks alot!
[8125, K-JAM, P4300, MDA Vario ROM Development] thankins:
I would stick with Xlpore's Rom, since you didn't mention that you had a 4g or 3g, since it will work great on both. Just extract those files and run it, simple as that. If i were you i would read up a little on the whole process. nothing like having a $200 brick cause you didn't know what you were doin
[8125, K-JAM, P4300, MDA Vario ROM Development] mfrazzz:
Dude, you have a LOT of reading to do before I'd suggest you even start to do this (based on that question alone). No, its not like installing an application. You are installing an entire new OS (Installing, not Upgrading). So when you do this, its going to wipe out everything on your phone (not your SD card, but on your phone's internal memory).

I'd highly advise you to read and understand whats in the Wiki for the wizard. Then read and understand the stickies at the top of this forum and the ones at the top of the Wizard Upgrading forum.

For the sake of your phone, make sure you understand this stuff. Don't just run an executable because it sounds cool. I'm not trying to scare you off or anything, I just want you to understand what you are looking at doing and understand that flashing custom roms isn't the fix to everything.

Understand also that these custom roms are (for the most part) test things. There are bugs, there are quirks, and there are things that flat don't work. Sure, for the most part they give you more power, and a better functioning phone, but for some of the roms that requires tweaking to get it to that point, so you need to understand what is involved (people here will assist, but we won't spoon feed).

Here's an excellent post with TONS of pointers to information (yeah its buried in the XPLore thread. We need to pull this out into the Wiki or make a sticky with this):

http://xdaforums.com/showpost.php?p=1206964&postcount=894

Read and learn before you start flashing. You will save yourself a lot of grief, and may even save the life of your phone.
[8125, K-JAM, P4300, MDA Vario ROM Development] prinsipe21:
little scared

im scared to upgrade my mobile to wm6 please.

could someone please link me to a step by step process how to upgrade my phone? an easy step by step for newbies. too many threads i dont know which i read first and which one should i start!

is it? UNLOCKING CID>Install ROM> DONE? that easy?

Wizard is not available in my country yet but few stores sells PDA's not repairing PDA's if it was bricked! so thats why i am very scareD!

:( please help me!
[8125, K-JAM, P4300, MDA Vario ROM Development] bwesty:
http://xdaforums.com/showthread.php?t=298613&highlight=tutorial

Listen to the advice that mfrazzz gives you. Mfrazzz knows what he is talking about.

Your welcome to ask as many questions as you like just make sure that when you post your question you prove that you've attempted to search yourself. Present your question in a an informative manner and im sure someone more knowledgeable will reply.
[8125, K-JAM, P4300, MDA Vario ROM Development] nstefanelli:
You definately need to read the Wiki before you do anything. It gives you step by step instruction and will most definately make flashing your device easier. If you have any questions, please don't hesitate to PM me. Good luck.

-Nstefanelli-
[AT&T HTC One (M7)] aldo.pareja:
Hello guys, new on unlocking androids and these things, I want to learn and get more involved in this community.

For now I just gotta a problem and can't find the answer over the internet. My problem is that I wanna buy the best buy at&t blue htc one m7, but I will be using in Colombia in another network, do I need to buy a plan in the USA to get the best buy version?, or just pay the 200 dollars and that's it?. Is it easy to unlock it and make it work in Colombia?, there is an unlocked at&t blue on amazon but they charge me a hundred dollars more, is it worth it?

Sorry for being a little lost here,
[AT&T HTC One (M7)] badger109:
s-off

I'm trying to unlock & S-off my new phone. Maybe someone can help? Android 4.1.2 HBoot 1.44

tried revone stock

got some error

installed weaksause & superSU to get root

tried revone a few more times

now I get error -6

Is there anything specific to AT&T devices that I'm missing? (I'll post in the revone thread or start a new one if I can't get it)

Thx
[AT&T HTC One (M7)] clsA:
You need to use Rumrunner to s-off your phone

I ran this RUU first then rumrunner

http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
[AT&T HTC One (M7)] jhotwenty1:
install custom rom

I got mine today.

hboot 1.55

unlocked bootloader, installed 2.8 twrp, rooted, and s-off

android ver 4.3

software ver 3.17.502.3

radio: 4T.20.3218.13

to install the maximushd 46 or any custom rom, do I just download the zip and install from SDcard?

or is it much easier to update the stock rom to 4.4.2 (any directions will be greatly appreciated)

I am such a newbie please bear with me.
[AT&T HTC One (M7)] phonymike:
I bought a blue one a few days ago, love it, but had trouble getting S-Off. I bought it to use on T-Mobile. I submitted an unlock request to AT&T through their website and am waiting on a reply. If that fails I'll just buy an unlock code. I wish I would have found this thread sooner.

hboot 1.55

android ver 4.3

software ver 3.17.502.3

radio: 4T.20.3218.13

Unlocked bootloader with htcdev.com no problem. Flashed custom recovery with twrp 2.8.74.0-m7 and root with UPDATE-SuperSU-v2.45.

I could not for the life of me get revone or rumrunner to work, revone -P would fail (even as su), rumrunner would say cleaning skunky rum and have a progress bar where it would request su (granted it) and fail. I tried firewater and it wouldn't run after being pushed to the device. After that I used SunShine ($25) and that was painless and finally got S-Off.

I changed the CID to T-MOB010, I also used MID_Change_1.01 to set MID to PN0713000 (under custom recovery). I was able to flash TMOUS_3.24.531.3 Zip, bringing it to factory recovery, and it did a few OTAs being around 600MB each bringing it to TMOUS_6.10.531.10. For fun I tried to install TMOUS_6.10.531.10 Exe, and it wouldn't continue unless the CID was 11111111.

To switch back to AT&T, I set CID CWS__001 and MID PN0712000 (under custom recovery), flash Cingular_US_3.17.502.3 Zip and I can then flash Cingular_US_3.17.502.3 Exe but not Cingular_US_4.18.502.7 Exe. I can't seem to get any OTA with 3.17.502.3 but I don't have a valid AT&T sim card. I'm pretty new to this stuff and I'll probably just stick to the GPE 5.0.1 Zip (works great).
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] tbgreen89:
So I just picked up my Note 4 last night. Coming from a G3. Screen is bright and colors are great. Liking the phone. But one thing that bugs me and it may just be me.. is the color shift during different viewing angles of the screen. Mine turn to like a greenish blue tint when tilted all directions. It's most noticeable on lighter screens. Darker colors not so much.

Does anyone else have this? Does it bother you? Should I go exchange?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] johntuck77:
Mess around with these settings first
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] tbgreen89:
Doesn't make a difference. Anybody else have this problem?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] arjun90:
All the displays in the Note 4 have screen viewing angle issues. Some have vertical shift issues wheres others have horizontal shift issues and others have both. People tend to keep their eyes oriented on just the vertical aspect and look at their devices eye-on, a big factor as to why you don't read many others acknowledging this on their AMOLED devices (Note, not just pertaining to the Note 4). AMOLED has perfect viewing angles, the culprit is usually the digitizer and glass which are incorporated on top of the AMOLED screen. The digitzer and Glass are responsible for the color shift due to inorganic elements used to manufacture such components. I've seen red shift to orange when looking at certain Note 4's from a horizontal angle, and I've seen Blues shifting to purple from vertical angles, and I've seen worse in which a demo unit had pink shift and green and blue shift. A replacement is not going to help. The iPhone circumvents the screen viewing angle problems thanks to the separation between the LCD panel, backlight, and glass. Recently, Apple decided to combine the backlight and LCD, thus reducing 3 layers to 2, the results did not compromise the screen viewing angles. IPS displays are still a versatile choice when thinking about appropriate displays. AMOLED is simply good for folks that are addicted to saturated colors.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] ShrekOpher:
Never had any issue. When I first got my phone, when I viewed the screen from a heavy angle it had a bit of a pink tint on white colors, but that had gone away now.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] arjun90:
Are you using any screen protector as well?

BTW,

There are several factors involved,

- Amount of Oleophobic Coating which distorts the actual colors discernible by the viewer

- The Digitizer

- The Corning Gorilla Glass

- And the amount of bonding used to keep the AMOLED display adhered to its bottom layer (Remember: Organic by Nature).