yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 General] willcor:
hi,

read my post #8 in this thread with relevant links (regarding

rooting this Rom etc)

http://xdaforums.com/showthread.php?t=3194008

good luck
[Galaxy Note 4 General] mojoe:
Best to do a factory reset and reinstall all apps and data

Thank you.

Followed your thread.

Rooted and working, although I do not see speed improvement greater than 8%.

Antutu benchmark went up to 42000 (Lollipop 5.1.1.) from 39000 (Lollipop 5.0.1).

Did a complete factory reset (wipe cache, dalvick and all data).

Great ROM

Antutu benchmark went up to 51000. Fantastic.
[Galaxy Note 4 General] @home:
Can we flash back to stock KK from the 5.1.1 version of this Rom via odin?
[Galaxy Note 4 General] lrm537:
Yes. But will need a full wipe to prevent bootloop.
[Galaxy Note 4 General] lisbon2004:
Hi there!

i'm currently on 4.4.4 and need to update the bootloader before flashing a custom rom.

cannot find a stand-alone BL file from 5.1.1..

do i get it right that if i will downoad this 1.4GB firmware:

>> N910FXXU1COH4_N910FOXA1BOC3_alexndr.7z << (Android 5.1.1)

and will flash it via Odin, this will update the bootloader?
[Galaxy Note 4 General] dewingerd:
@ _alexndr Great work ! Would it be possible to make a version with more csc's ? My csc is "LUX".

Thanks in advance.
[Galaxy Note 4 General] gordonthegun:
There's build COI3 now, with a greater changelist.

Can we expect you, _alexndr, to repack that too?
[Galaxy Note 4 General] alessandro_xda:
i think he gave up, he published the rooted version on september the 27th but after 10 days still nothing here...
[Galaxy Note 4 General] gordonthegun:
So I decided to install _alexndr's COI3 devbase deodexed and then Xposed.

Beautiful!

Thank you _alexndr, don't give up that.
[Galaxy Note 4 General] alessandro_xda:
Unfortunately that rom is for rooted/knox-tripped devices [emoji53]
[Galaxy Note 4 General] dixi83:
help n910f for root knox 0x0

bonjour je viens de faire l'acquisition d'un galaxy note 4 n910f. il était en 5.1.1 apres une mise a jour. suite a cela je cherchais a le rooté. pour cela j'ai installé la version 4.4.4. en imaginant trouvé un moyen de le root sans touché a knox. j'aiemrai savoir s'il existe un tuto pour rooté avec un firmware officiel tout operateur FR pour le pas touché a knox.merci
[Galaxy Note 4 General] Wacco001:
English please ..
[Galaxy Note 4 General] gordonthegun:
Traslation:

Good morning,

I've just got a Galaxy Note 4 N910F.

It was on 5.1.1 after an update.

After that I tried to root it.

For this reason I've flashed 4.4.4, thinking I would find a way to root it without tripping knox.

I'd like to know if there is a tutorial for rooting an official firmware for any French carrier without tripping knox.

Thank you.
[Galaxy Note 4 General] alessandro_xda:
there is no way to root a 910F without tripping knox
[Galaxy Note 4 General] gordonthegun:
Il n'existe pas un moyen pour rooter le Galaxy N910F sans toucher le knox.
[Galaxy Note 4 General] Wacco001:
Please check XDA Forum Rules (here) and check rule 4 .. :angel:

English please !
[Galaxy Note 4 General] gordonthegun:
Pardon.
[Galaxy Note 4 General] alessandro_xda:
thanks for the POI4 uptate, is there any chance to repack the COI3?

thanks
[Galaxy Note 4 General] dixi83:
and with kingroot , and after replace kingroot with supersume is not possible on n910f? https://www.youtube.com/watch?v=3O3DcpeS_Ic
[Galaxy Note 4 General] _alexndr:
Seems like you do not unterstand the main idea of this thread...

Re-packing is useful if Samsung releases a new ROM base but there is no multi CSC OXA version available yet

In case of both latest builds (COI3 and COJ3) Samsung released original OXA builds very fast so re-packin is not needed ;)
[Galaxy Note 4 General] alessandro_xda:
Sorry for my misunderstanding but on samfirmware i only see the nation-specific firmwares and i can't find the multi csc ones

Inviato dal mio GT-N8010 utilizzando Tapatalk
[Galaxy Note 4 General] _alexndr:
In case of N910F all builds for Germany are in fact multi CSC OXA and contain CSCs listed in post #1. It is enough to filter all available firmwares for N910F by typing "OXA" :cool:
[Galaxy Note 4 General] alessandro_xda:
thanks, i didn't know it
[Galaxy Note 4 General] sPEADy:
[MENTION=5150393]_alexndr[/MENTION] Hi Bro, any chance of update to this with POK1 ? with German CSC? Thanks for any reply.
[Galaxy Note 4 General] StevePritchard:
See next response - it includes link to release.
[Galaxy Note 4 General] StevePritchard:
Here is a link to my release which is the POK1 with DBT CSC - after some testing, it's been determined that it's ok to mix the CSC.

http://xdaforums.com/showpost.php?p=64234902&postcount=3063
[Galaxy Note 4 General] asfand007:
urgent

i have sm-n910f mobile of TMB reigon. i dont get any automatic update even i am not rooted. my mobile has kitkat version. will this lolipop firmware work on mine. coz even searched sam mobile but they didnt have any of tmb reigon. though i live in pakistan i dont want ma fone to stop working plz guide
[Galaxy Note 4 General] StevePritchard:
If you have a phone with TMB, then I think it's likely to be a SM-N910T (USA T-Mobile), not F. Lollipop is the latest release for this version unless you can find a custom ROM.
[Galaxy Note 4 General] StevePritchard:
FYI Marshmallow has just been released for your phone (assuming it is a N910T).

Cheers,

Steve.
[Galaxy Note 4 General] asfand007:
but bro i have seen in phone info it is N910F confirm but numbers showed its still tmb reigon plz help me can i still install update of anyother reigon? or will it affect my fone?

product code is SM-N910TZKETMB
[Galaxy Note 4 General] StevePritchard:
Your product code SM-N910TZKETMB seems to indicate that I'm right, and it's an SM-N910T which is the American T-Mobile version (http://www.samsung.com/us/mobile/cell-phones/SM-N910TZKETMB).

To ensure that you don't get compatibility problems, you should make sure that you use the Marshmallow version for that device which has just been released.

Check out http://xdaforums.com/note-4/general/download-t-mobile-note-4-marshmallow-t3406835
[Galaxy Note 4 General] asfand007:
but here is the thing bro. if its sm-N910t, why is it showing in phone info and even when i connect to kies its shows SM-N910F and not SM-N910T. plz guide me i have been stuck in this problem for days now
[Galaxy Note 4 General] StevePritchard:
I think you would be better off asking in an N910T thread. If I were to guess, I'd say you have T hardware, with a (possibly modified) F firmware, but it would be a guess - sorry.
[Galaxy Note 4 General] the dreamer:
how can i upgrade my rooted N910C 5.1.1 knox 0 to MM without losing root & knox
[Amazon Fire Phone] coachadrian:
Moto360 works great with the last update now and the update has to be the 4.6.1 US versions ending in 820 and not 320

I had the one ending in 320 and was not working and Google services was working from time to time, but now with the update ending in 820 everything was fix with latest google services and latest play store and Google maps all working great and obviously Android Wear for my Moto360 that works like a charm :)

If you have questions let me know and I will try to help :)

I have an AT&T fire phone unlocked.
[Amazon Fire Phone] bbnsol:
Just wanted to add to this because I've just got my Sony Smartwatch 3 working.

Had to install system software version 820 but otherwise everything is fine.

I've got a UK O2 device.
[Amazon Fire Phone] footneek:
Please explain the steps. I have a Note 4 already paired to my Moto360. I want to add a second device.

Thanks.
[Amazon Fire Phone] hugoprh:
LG G Watch

Confirmed that the LG G Watch running 5.1.1 Android wear, works fine, just the stock Amazon email app, does not trigger the watch to vibrate when a new email is received, other apps, messages, calls, Facebook, notifications work great =) Finally I can use this phone =)
[Amazon Fire Phone] omxx:
congrats!
[Amazon Fire Phone] BjornBear:
I thought that update wasn't available yet for all of us using the UK handsets? Did you update using the US firmware? I put off doing that because I thought perhaps US versions weren't optimised for uk carrier networks.

Trying to get my moto 360 to work with this phone, migrated from a moto e 2nd gen. Boy did I underestimate how primitive fire os is. I mean, on paper: this phone is the best bang for your buck (on offer, anyways), but man 'dat os tho'. My moto 360 has literally served as a glorified regular watch with a ridiculously short battery life for the past month. I'm also on o2, and I'm not sure what you did to get that update but please let me know.
[Amazon Fire Phone] junisir:
Which version of google service do you use?

I am using 4.6.1 (3820) and whenever I play Android wear then it shows

"Update the Goolge app on the Play Store. Then open Android Wear again"

even the android wear and connect are latest version. So I cannot connect to my

MOTO 360. Can you help?:)
[Amazon Fire Phone] tylersfd2:
Hi,

I had the same problem and here is how i fixed it!

1. Open playstore

2. Download the Google app...literally type in "google" and its the app with the white looking google symbol

3. Android wear works!

My fire phone is running 4.6.3 ver. 620 = this is the last three digits of my software version.

Google play store version 5.9.12

I also downloaded Motorola connect and selected the moto360 from menu and clicked open in android wear.

hope this helps im getting my watch tomorrow.
[Amazon Fire Phone] junisir:
Thanks a lot.

After I upgrade to 4.6.3 and I forced to remove Amazon app store and then everything works smoothly.

Thanks.:o
[Amazon Fire Phone] stunvn:
I really like the moto360 2015 .. but it's $299 sad...
[Amazon Fire Phone] tylersfd2:
Moto360 1st edition is $149.99.

From my reading on the new 2015 edition their is increased battery life and a slight change in button placement.

My moto360 will last the entire day with with a full charge to start that day. Ambient mode is on and I use paid watch faces with lots of colors.

I didn't feel the extra $150 for the second edition was justifiable to me. The 1st edition is still quite fashionable and useful.
[Moto G Q&A, Help & Troubleshooting] Kyozumoh:
Hey, so i want to root my Moto G XT1033 16GB dual SIM running android 5.0.2.

I've bricked a smarthone before while trying to root it, so i want some help to root my phone the safest way possible. My warranty has already expired.

Obs: my phone is from brazil, i'm not sure if that changes anything.

I've attatched a screenshot if any other info is needed.
[Moto G Q&A, Help & Troubleshooting] .:Dark:.:
If you have a custom recovery installed you can flash it from there. Go here and grab SuperSU and follow the instructions.
[Moto G Q&A, Help & Troubleshooting] sjandroiddeveloper:
Install a custom recovery like Philz or twrp

And flash supersu zip by chainfire
[Moto G Q&A, Help & Troubleshooting] Kyozumoh:
so yeah.

many DL's such wow, wich one do i pick? (attachment)

Also, do i unlock the bootloader before installing twrp?
[Moto G Q&A, Help & Troubleshooting] sjandroiddeveloper:
You must unlock the bootloader before flashing a custom recovery otherwise it will not install

And do no download twrp for moto g from twrp's official site, it still have bugs

Download from this thread

[RECOVERY][falcon]TWRP 2.8.6.0 touch recovery [2015-04-06]

http://xdaforums.com/showthread.php?t=2980621

Sent from falcon

PRESS THANKS IF HELPED????
[Moto G Q&A, Help & Troubleshooting] Kyozumoh:
Hey, so how do i know if my moto g is GPE or not?
[Moto G Q&A, Help & Troubleshooting] sjandroiddeveloper:
If you are on stock ROM that came with your phone then if you have stock Motorola apps and Motorola options in settings then you have retail variant and if you don't have these apps and settings then you are gpe
[ONE Q&A, Help & Troubleshooting] microserf:
Hey everybody. Maybe someone here has another idea.

I had a small mountainbike accident today with the Oneplus One in my sidepocket. (Bike is broken, I am well fyi). Although there is no visible damage, the phone won't turn on since then. Battery is definitively charged but I get no reaction. The suggested "power circle", 5x 20sec on the power button, did not help and I can't either get to fastboot nor to the qualcomm "debug" mode (vol+ / power). It won't even show of as a device in the system manager in Win 7. Only sign of life that I am getting is the the camera led. When I keep pressing the powerbutton, every 10secs the led goes on and fades off. Same thing when I unplug and replug the battery - Camera LED goes on, stays on a few seconds, fades off.

I already "replugged" the battery but right now I am out of ideas. I am pretty sure it's not software related but before you ask it's stock rooted 4.4 / CM11s with no further modifications to the kernel or ROM.

Anyone has seen this "LED" thing before or has a hint what else I could check? Any suggestions would be highly appreciated.
[T-Mobile LG G3] Desertburn:
When can somebody figure this out?
[T-Mobile LG G3] m3xicanprid3:
I think that you can unroot via supersu on the settings. Theres an option where it says full unroot idk if it works cuz i havent try it .
[T-Mobile LG G3] RealPariah:
Dude, this is easy. First find and flash a stock unrooted ROM then once flashed follow button guide for reset factory defaults G3 (it's like hold vol down and power to boot, then when you see boot logo release power and hold it again until you get on screen prompt about wiping all user data (now release both keys) use vol keys to select yes accept warning and it will actually drop to TWRP and not run any cleaning script). Then just flash stock recovery should have a recovery flash zip for stock recovery somewhere on XDA or use Google.

Or the more official way (guide (follow the TOT guide listed last in OP)):http://xdaforums.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667

It just walks you through downloading official firmware and utility needed to flash it. If using same computer you used to root phone then can skip the driver installs and just install the utility, follow connect your phone to computer steps. Once utility sees the phone select firmware you downloaded and flash. This method reports to pass inspection by carrier so they won't know you rooted it.

If all you want is stock ROM imho leave custom recovery alone so you can go back to a custom ROM anytime and just flash the stock debloated image in Android development section. If you don't like super user install supersu (if it's not already) open app go to settings tap full removal. This will remove super user binary and you won't have the ability to use super user unless you flash it back in recovery.
[Android Q&A, Help & Troubleshooting] ravenmk:
Hi, is it possible to enable soft keys with ADB?
[Android Q&A, Help & Troubleshooting] NOOK!E:
Yes, but not without root.

The procedure (if you had root) would be like so:

1. Make a Nandroid backup!

2. Connect your PC to your Android device with ADB.

3. Execute these commands:

adb shell mount -o rw,remount rootfs /
adb pull /system/build.prop

4. Add the following line to the end of the build.prop file you just pulled:

qemu.hw.mainkeys=1

5. Execute these commands:

adb push build.prop /system
adb reboot

6. Done!
[Android Q&A, Help & Troubleshooting] ravenmk:
Oh. Ok, thanks!
[Sprint Samsung Galaxy Note 3] tx_dbs_tx:
I wanted to give you all an early set of instructions on properly moving to Lollipop. Being that I have already been through the trials & errors of this subject with the note 4, i wanted to give you all a head start to save you a bunch of time scratching your heads wondering why your stock ota/odin flash is buggy. It seems that the stock Lollipop tar's don't wipe everything especially data. So when you go to Odin the stock Lollipop tar without first wiping from your current custom recovery, you WILL have left over data which causes some issues. ALWAYS wipe everything per usual (including the factory reset option) BEFORE you odin the stock Lollipop tar. It's also been noticed that the Lollipop ota hasn't been nearly as stable as the official rom tar. So even if you took the official ota, I would recommend following these simple instructions for the best results. If you have never rooted your device then you can disregard otherwise keep reading. For the BEST trouble-free experience do the following.

***First you will need to download and copy to your sd-card the custom/stock rom zip*** (Custom/Stock ROMs are coming soon!)

1. Wipe everything several times in current custom recovery (including factory reset option) (TWRP recommended)

2. Odin the official lollipop tar.

3. Setup rom per usual. (At this point if you want to remain on the stock ROM you can stop here)

4. Enable usb debugging.

5. Reboot to download mode and odin the compatible cf-auto-root for your device.

6. Odin latest TWRP compatible with your device.

7. At this point you will be ready to flash a stock or custom Lollipop rom.]

Get ready. Roms will be coming soon... you will need to know this important info before you start flashing.
[Sprint Samsung Galaxy Note 3] garyfunk:
Thank you for the great information. May I ask that you please fix your font colors?
[Sprint Samsung Galaxy Note 3] kingdazy:
just to be clear, you're recommending that we Odin the stock tar, even if we're already rooted w/ custom recovery (on KK, as an example)?

and again, a sincere *thank you* for your attention to this device and its forum.
[Sprint Samsung Galaxy Note 3] w7excursion:
Looks ok here so....
[Sprint Samsung Galaxy Note 3] garyfunk:
Switch to a dark theme.
[Sprint Samsung Galaxy Note 3] weavr:
If you are going to flash a Lollipop based ROM, then yes Odin the OC5 update first. You will need to re-root and flash another custom recovery but it will be well worth it! :)
[Sprint Samsung Galaxy Note 3] kingdazy:
interesting! I have no issue doing it, if that's the req. easy enough to do. (you can see i've been here for a while)

But can you (or someone like [MENTION=1503720]tx_dbs_tx[/MENTION] ) explain why?

(my point being, if I haven't yet odin'd the stock tar or gone the route to receive the OTA already, it seems redundant to wait for tx_dbs_tx to put out his rom at this point. since being req'ed to odin and reroot will get me the same as what I would be about to flash... make sense? lol)
[Sprint Samsung Galaxy Note 3] tx_dbs_tx:
If you are currently on any version of KitKat you MUST either take the official Lollipop ota update OR wipe everything in your current recovery and Odin flash the official Lollipop rom tar. you MUST do one or the other before flashing any custom/stock rooted Lollipop rom or you WILL have a non booting phone. If you simply fash a Lollipop rom with a KK bootloader & carrier partitions, it will be a no go and you will have to start over by odin'ing the stock Lollipop rom tar. Lollipop brings a lot of new things and most importantly there afe partitions that must be written to your phone that are required. Simply flashing a custom or even a stock rooted Lollipop ROM WILL NOT write these important partitions. Only the official rom tar will do this as well as the regular ota. So no, the stock rooted rom i'm working on will not properly upgrade your phone to Lollipop. If you plan to move to Lollipop (which i highly recommend due to major system optimizations, features, etc) then go ahead and prep by flashing the official Lollipop rom tar using the wipe methods i explained above. Trust me it will save you a lot of grief. I hope this makes sense.

Edit: I need a couple of people to help me troubleshoot and test the stock rooted lollipop rom i'm trying to finish. I have one person helping me but his work schedule interferes. If you have some basic knowledge on how to flash, use root explorer and also know how to extract and zip a rom, please pm me and i'll give you the files and info you need. I'd like to help you all get a couple of stock rooted roms going so others can then have something to work with for future themes, roms, etc.
[Sprint Samsung Galaxy Note 3] jdg2002:
i would be happy to help

i did some testing for you on the note 4. i would be happy to test for you on the note 3 as well.
[Sprint Samsung Galaxy Note 3] kaos420:
I xm test what ever you need. Its 305 ill be home and fully charged by 5 shoot me a pm. Cant test anything. Im fully updated via Odin. And Knox has been triple since day 1. So ill test lol

Sent from my 0x1 Note 3...... I love tep
[Sprint Samsung Galaxy Note 3] evilvoice:
I can test a rom. I am currently working on building my own and have been failing. I finally got everything deodexed, but building a rom that boots is another story. TWRP backup really messed things up. Have been using Odin to flash the official stock tar about 5 times now to try and get to a clean base. I found a DevBase in 9005 thread that I am testing now. Would love to get something going on this phone to help others (make a minimal devbase for others) since I haven't found a kitchen that works. ArchiKitchen does not work for our device, at least not without some editing

UPDATE: So I finally got it to flash, time to cut down on some of the extraneous files that won't be needed. I'll probably throw it together and post a thread for people to use as a base, just add their own stuff. I'm not looking at releasing a ROM just yet, just a base for people to build on.

I can still test yours and see how it goes. There was an issue with mine where it hung on first boot, booted into recovery and reboot system, all is fine.
[Sprint Samsung Galaxy Note 3] kingdazy:
thank you for taking the time to explain. since I had a kid a little over a year ago, I've been out of the loop. (barely time to flash things, nonetheless read the tech details like I used to...) I knew LP had a lot of changes under the hood (art, etc), but was unaware of the partition changes.

I'd like to toss you a bit of a donation for your stockROMs when they come out. your time here is appreciated.
[Advantage X7500, MDA Ameo General] essojay:
My Ameo,s main camera started by showing blurry and distorted image, then the camera does not start all together at time and the last issue is that when it finally started nothing was showing on the main camera as of now but the inner camera is working good... tweaked all settings, NO WAY! could this be as a result of a corrupt camera application in the extended rom or a manufacturer defect?

If it is an application problem, can someone please post the appliaction .cab file.

thanks

bR
[Advantage X7500, MDA Ameo General] Zatesz:
I have problem with main camera too. Is cab file fix this problem?

Will you send me this cab to ateszka@gmail.com?

thanks
[Advantage X7500, MDA Ameo General] bilalperwaiz:
yea dude me too...but the front vga camera seems to respond much quicker and gives better quality!
[Advantage X7500, MDA Ameo General] coolish:
my main camera has a problem of "green color area" around the left-bottom corner of each photos

every photos took by the main carema has the same area "more green"
[Advantage X7500, MDA Ameo General] bilalperwaiz:
the green area izz DEFAULT...that cannot be fixed..since it izz a manufacturing fault from HTC!!!
[Advantage X7500, MDA Ameo General] coolish:
do you have the same problem? how do you know that?:(
[Advantage X7500, MDA Ameo General] Madhadder:
The problem I have been having soince flashing to the newest WM6 Rom

is that ever now and then the picture taken is just a solid grey.. The Camera

app works as normal, but the resulting pic. is just all grey.. It seems to happen once every 10 or so pix, sometimes more.
[Advantage X7500, MDA Ameo General] coolish:
I have this problem, only when I place it extremely close to the screen of my laptop to take pictures of the screen.
[Advantage X7500, MDA Ameo General] Madhadder:
Mine happens at all times.. Inside, Outside, still subjects, moving subjects..

It happens at random times.. 10 pix will be good the 11th is screwed then the

next 7 work, then 1 bad.. etc.etc.