yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] TheKicKer69:
Very easy step-by-step tutorial - great job.

Got my unlocked 32GB Shield 4G/LTE today - updated OTA to the latest 5.0.1

then i followed instructions here and all is working perfectly.

I used to root to OC my tablets (Motorola Xoom, Lenovo A3300) but with this baby i don't need to - in fact i need root for one thing and one thing only TITANIUM BACKUP cuz i have some games that no matter wot u do if u don't use titanium backup pro u won't have the latest stages u played.

Now after rooting i tried system update and it says "There Was an ERROR fetching OTA information"

all of u savvy out there can u tell me wot i need to do in order to receive OTA from NVIDIA while being able to use titanium backup (so must be rooted i guess right?)

Tx in advance for telling me wot to do

And again great job i can confirm with the latest update 5.0.1 on May 7th, 2015 ur method worked without any flaw!
[Shield Tablet Android Development] bosou:
thanks your guide help reduce the hassle
[Shield Tablet Android Development] Cable123:
thanks and can it update ota still

first I want to say thank you for the root went through really smooth.:good: second I wanted to know if after this stock will I still receive Nvidia shield updates used to have shield portable and after I did root it could not update properly with stock rom just curious if this will still update through Nvidia ota update :confused: keeping the stock four key mapping controller and console mode. haven't seen any ROMs with those features yet. If so i would flash one . I hear someone is making the mapping controller coming soon might flash after that. thank you for any information on this root
[Shield Tablet Android Development] Jak Crow:
It seems like after doing adding CWM in fastboot, it's only good for one boot to get into recovery and flash supersu. Attempts after that result the dead android with a red ! coming out of its front panel, which I assume means the recovery image is missing. Ideas?
[Shield Tablet Android Development] AnthonyMooreDevices:
Still Cant Root it...

Ok… i AM downloading the official drivers, plugging My tablet in with debugging and unknown sources turned on, right clicking on “Computer” in the file explorer on win7 (cwm file was broken on win8 for Me) and clicking “Manage” then finding the adb driver, then a msg pops up on My Shield Tablet asking if i trust this source, then i copy the LTE image, the cwm recovery image, and supersu.zip to tablet’s sd card, go into cmd panel and type everything and it all works except “fastboot flash recovery recovery.img (even tried “fastboot flash recovery recovery.img.img and fastboot boot recovery.img) and it never finds it, tried puting it all in one place, putting all files on the tablet, even the adb mini, etc… Is it supposed to be able to see My tablet after reboot into recovery because it doesnt and it can never load the recovery file, the only time it seems to something is when its not in recovery and I’m on the homscreen, then i press “fastboot flash recovery recovery.img” then it says “waiting for device” but i cant do anything, and even tho its unlocked and has cwm recovery and supersu.zip on sd card, when i boot to recovery, it is not cwm recovery… Also, recovery file seems to be a disc image and cannot be made into a zip or anything, only burned to a disc? What AM i supposed to do?
[Shield Tablet Android Development] dbasinge:
This work for me, but everything I reboot it gets stuck on the NVidia boot screen. The only fix it to wipe cache and dalvak cache. Any ideas?
[Shield Tablet Android Development] rembrandtlnx:
Like a charm on my 5.1.1, easy and fast.

Using Windows 10 Pro.

---------- Post added at 05:56 PM ---------- Previous post was at 05:42 PM ----------

Did you put recovery.img and supersu.zip inside the installation directory of miniadb? (C://program files/miniadb**) You are not supposed to place the files in the tablet internal memory/ microsd. If they are already in the right place, using "fastboot flash recovery recovery.img" must work without exceptions. Unless you give a different name to the recovery.img file.

Sent from: Galaxy S6 Edge 64GB using Tapatalk
[Shield Tablet Android Development] Aventura5:
I know this was a while ago, but would you mind sharing that transcript (with personal info removed)?
[Shield Tablet Android Development] _d4ni3l:
Thank you so much. Really easy and hassle free. The only problem I had was when I used adb reboot bootloader command it didn't reboot to the bootloader, but simply rebooted back to the android. It has taken several tries before it worked...
[Shield Tablet Android Development] wiQbold:
you have to open command prompt in the directory on your PC where you copied the files like recovery.

or you can maybe try 'fastboot flash recovery Place/on/PC/recovery.img'
[Shield Tablet Android Development] guily6669:
Can't I flash the latest OTA using stock unlocked bootloader without locking the old tablet by the recall program.

I don't want to install a CFW.
[Shield Tablet Android Development] TheClap:
Does this method still work? I'm still sitting at 4.4.2 since I've been super lazy.
[Shield Tablet Android Development] BlackBoxDemon:
Well, I did it about a month ago. And it worked great though I must confess it took me some time to understand the instructions ... old noob here.

Once you have gone through the poccess once, it does get easier :D
[Shield Tablet Android Development] unfortuN8:
Hi I'm trying to root my shield tablet original and am stuck on flashing the recovery image. I typed in what you suggest "fastboot flash recovery recovery.img" but it says error device null. Then i tried the same command but instead of just recover.img I gave the full file directory (E:\Program Files (x86)\Minimal ADB and Fastboot\recover.img) and it gets stuck on waiting for device. I googled this problem and others have had it as well, people suggest the drivers aren't up to date but the pc is able to see the device once i boot into android again. Please help!
[Shield Tablet Android Development] unfortuN8:
Managed to get it working after messing around with it for a bit. Not sure exactly what worked though haha
[Xperia Z General] Aazeb:
I was messing with xposed framework and rebooted my phone and it's stuck in bootloop. It shows the Sony logo then the loading screen and then again reboots. Please help guys. I'm not gonna get another phone :(

PS: Rooted Xperia Z running 4.4.4
[Xperia Z General] kingvortex:
Try activating the Xposed safe mode. There's an explanation in this post.

If that doesn't work, flash the Xposed disabler zip in recovery (if you have a custom recovery).

If neither works, flash an FTF as already stated.

Also, just for future reference: Do Not Post Questions/Help/Troubleshooting in General :)

Sent from my C6603
[Xperia Z General] Aazeb:
Thanks man :)
[LG G Watch R] mitchellvii:
Google must think we are idiots. They force us to look at that stupid "Ok Google" banner every time the watch enters bright mode - as if we somehow forgot the magic words since the last 300 times we said them.

Is there a hack to turn this off? Thanks in advance.
[LG G Watch R] mitchellvii:
Ok, just figured this out i think.

You can permanently disable the "Ok Google" banner by clicking the fob, saying "Ok Google", then clicking it again to dim. Repeat this 5 times and the "Ok Google" banner should permanently disable. I guess Google figures we have it figured out by then. :)
[LG G Watch R] RoosW:
Change your watchface, and it appears again :( There is no way to get permanently rid of this blight!
[LG G Watch R] mitchellvii:
Not correct. If you follow my method the banner will never come back. Changing watchfaces has no effect, at least under 5.01.
[LG G Watch R] RoosW:
Thanks! Indeed it stays away now, lets hope i do not need another system reset any time soon :)
[LG G Watch R] Testingchip:
I was thinking after you "kill" it it stays gone till reboot.
[LG G Watch R] fg:
Confirmed with 5.0.1 - the banner does not come back after a reboot or after changing faces.

-fg
[LG G Watch R] Rosch89:
If clicking it doesn't work just use the OK Google command for some random searches about 5-6 times and it will definitely not appear anymore after you've done so. Had the same issue initially but found it disappeared after a few uses.
[LG G Watch R] RoosW:
I have had it reappear twice now (went away after one 'ok google') while i have followed the instructions, not a clue why it did, the last time it just was there when i pulled the watch from the charging cradle..
[LG G Watch R] rmx36:
There are some external watchface apps where you can take it out if you're into those at all.
[LG G Watch R] pakure:
It is a cue for saying OK Google...

Do random searches 5 times by saying OK Google..(OK Google.. What's the weather..) Let it finish searching each time.. It will be gone... It will reappear if you reset your watch or after a new update... Do some Search 5 times again
[LG G Watch R] RoosW:
Yeah, did that, following the method described somewhere on the first page of this thread, i was assured it would be gone, over and done with, and would not even reappear after a reboot, but it does, kinda random, and always gone for a few days when i 'Ok Google' once.

But it should not happen as i have done the 5 times and such!
[LG G Watch R] fg:
I've had it also reappear (and disappear on it's own) a few times the last 2 weeks. No idea what the trigger is it was gone after the last update for at least 3 weeks before it came back.
[Galaxy S 4 Themes and Apps] dlclassic:
I made a few boot animations for my personal use, and am sharing if anyone else wants to use them. They can all be flashed from recovery:

removed for now.
[Galaxy S 4 Themes and Apps] PremiumISM:
Does these called boot animations?
[Galaxy S 4 Themes and Apps] dlclassic:
These are animations that play when you boot/reboot your phone.
[Galaxy S 4 Themes and Apps] dlclassic:
update

some were redone, some new ones
[Wing, P4350 General] parax:
Hi,

I have a question regarding my htc p4350. I have set up my four own email accounts on my device. Besides them there is an account for sms, mms and hotmail. Now the problem is I have more than those four accounts which I have to check daily. So is there a solution/registry tweak or something like this to disable the restriction of max. email accounts on wm5? It's not really user friendly to only allow four accounts.

Regards,

Dennis
[Samsung Galaxy Mini] midzan21:
CyanogenMod 11.o M12 for Samsung Galaxy Mini 2 (standard versio and no_internal version)​

Changelog is in #2 post

What's not working:

Camcorder

Native screen recording

Internal memory can't be mounted - FIX: Use no_internal version

Download:

Normal mount of memories

https://www.androidfilehost.com/?fid=95855108297851274

no_internal version - try if you can't mount internal memory with normal mount version

https://www.androidfilehost.com/?fid=95857557620392723

Kernel sources: https://github.com/TheWhisp/android_kernel_samsung_msm7x27a

Device tree: https://github.com/midzan21/android_device_samsung_s6500d

Device tree specific for msm7x27a chipset: https://github.com/midzan21/android_device_samsung_msm7x27a-common

Local manifest: https://github.com/midzan21/local_manifest-s6500d

Credits: [MENTION=4148720]TheWhisp[/MENTION] for all sources which i reuploaded because of stupid errors on syncing, CyanogenMod team for CyanogenMod ROM, legaCyMod for some things for building libs, @bleached for no_internal kernel and midzan21 (aka myself) for rebuilding ROM

XDA:DevDB Information

CyanogenMod 11, ROM for the Samsung Galaxy Mini

Contributors

midzan21, TheWhisp, erikcas, bleached, legaCyMod, Dazzozo and everyone else that is working on CM11

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

Based On: CyanogenMod

Version Information

Status: Stable

Stable Release Date: 2014-12-12

Created 2014-12-13

Last Updated 2014-12-16
[Samsung Galaxy Mini] midzan21:
Changelog

12.12.2014

* updated [MENTION=4148720]TheWhisp[/MENTION] CM11 M8 to M12

* for our phone: mostly bugfixes at CM base

* read CM blog for all updates from M9 up to M12

* all apk's and frameworks are updated

* libs are same just like kernel from 03.08.2014 build so this is why in About phone it writes TheWhisps kernel build date (I had some issues with that so I replaced my built kernel with TheWhisps)

* audio should work without editing build.prop (already edited file to make it working)

13.12.2014

*DevDB started (so it should be cleaner than original thread where is posted)

*Found problem with missing FM Radio apk (FIXED, UPLOADED WORKING VERSION)

16.12.2014

*Created no_internal version of ROM and uploaded to AFH

*Updated thread name
[Samsung Galaxy Mini] Nour Sherif:
Is it normal that the changelog lists only changes till M11?
[Samsung Galaxy Mini] midzan21:
Yes it is normal. Cyanogen team forget to add M12 in changelog and for M12 they fixed POODLE issue (Google what is POODLE issue)

Sent from Mini 2 using TVZMod v1.1 via xda-developers free
[Samsung Galaxy Mini] dante.:
great job man, tnx :)
[Samsung Galaxy Mini] TurkeyAndroidHacker:
screenshot ????

screenshot ????
[Samsung Galaxy Mini] meganukebmp:
We dont need screenshots... This is just an update to all frameworks and apps. Nothing that big of a change.
[Samsung Galaxy Mini] midzan21:
[MENTION=6245393]TurkeyAndroidHacker[/MENTION] Never quoute OP, that is one rule of xda so please if have any other question ask

[MENTION=6204518]Lazarevic[/MENTION] yes you can install TouchWiz from my thread which you can find in signature

[MENTION=5134145]meganukebmp[/MENTION]you got it right ;) It is almost pure Android AOSP experience...
[Samsung Galaxy Mini] Antox97:
Touchwiz can be installed by a zip that you could find here

---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------

So let me think [MENTION=4203213]midzan21[/MENTION]

This is that upgrade you've say into another thread? I will test it now
[Samsung Galaxy Mini] Antox97:
I was testing but CWM can't install "status 7 error"
[Samsung Galaxy Mini] midzan21:
Yes this is that upgrade. I created separate thread to be cleaner than in old thread

Also for status 7 error, try Philz Touch Recovery (contact me via PP for flashable zip) because I use that recovery for last few months and there works fine
[Samsung Galaxy Mini] Antox97:
Hm, now I've see that I have an old cwm, lol

---------- Post added at 09:58 PM ---------- Previous post was at 09:39 PM ----------

Camera doesn't work.
[Samsung Galaxy Mini] midzan21:
Camera works on my phone because it is based on good old stable CM11. camcorder is only thing that doesn't work on our phone.
[Samsung Galaxy Mini] Arathon:
I installed your rom from stock howerver the camera doesn't work, the camera app will crash when i try to open it. I've done all the wipes but the problem still persist.

EDIT: i tried miui camera and it seems to work however it asks to insert an SD card to save the photos when i've already inserted one. Do you know how can i solve this problem?

EDIT2: I pinpoited the root of the problem, every camera app i tried could initilise the camera sensor however it couldn't save the photo because it doesn't find the sd card. I mounted it from the memory setting and the problem still persis. I dunno how to solve this.

EDIT3: at the end it was the internal memory which is not mounted. Unfortunately i'll hv to look for another rom.
[Samsung Galaxy Mini] Antox97:
I think that on my phone camera doesn't work 'cause firmare. This ROM is for s6500d. I have once without "d". And also, the repo that [MENTION=4263819]Arathon[/MENTION] describes
[Samsung Galaxy Mini] Arathon:
I have the model 6500 that is plagued with the internal memory issues, I resolved all the problems by installing the cm rom made by bleached.
[Samsung Galaxy Mini] Antox97:
Hm I remember, TheWhisp CM11 doesn't recognize storages. But I think that CM11 isn't totally stable
[Samsung Galaxy Mini] toncata:
I am using this since it was released. Very good. I have some lag but I have switched to ART and I think this is the problem. The problem with storage could be fixed by installing pit file from ODIN. That is the way I fixed the issue. Can the developer tell if ART is working fine or Dalvik is fine.
[Samsung Galaxy Mini] midzan21:
[MENTION=4263819]Arathon[/MENTION] and [MENTION=5386729]Antox97[/MENTION] I wroted on first post: this is made for S6500D and it isn't tested on S6500 (non D) version. Problems with memory can be fixed by using boot.img from bleached CM11 build and replacing it in my build. If I got some more spare time today I should make it (no_internal version) and upload it tommorow.

For [MENTION=3445523]toncata[/MENTION] - ART is sluggish and slow on devices like ours. ART is primarly made for Nexus 5 and newer devices which have enough internal memory and more RAM. I use Dalvik because of Xposed Framework ( for Instagram downloader and AppSettings modules), but I tested ART (needed because of development one application for college) and that is my personal opinion.

Also for all you, tomorrow I should update #1 post with Philz Touch CWM download link, so you can try it if CWM gives you Status 7 Error. No_internal version should be also in first post.
[Samsung Galaxy Mini] meganukebmp:
I dont think thats the problem since both phones have very minor differences hardware and software wise. Only difference is NFC sensor and NFC frameworks and apks.

Its most likely due to board/screen model. Thats why some people have white screen and others dont.
[Samsung Galaxy Mini] midzan21:
Thread update

Check #1 post for no_internal version ;) Please test it, but I think that should work fine.

Also in #1 post I added Philz Touch CWM so if you have Status 7 error on any other CWM try first 6.0.4.5 and after that if there is also Status 7 error try Philz CWM.
[Samsung Galaxy Mini] TurkeyAndroidHacker:
Whİte screen fİx ??

Is white screen problem was solved ??? and this rom how much ram is using :confused:
[Samsung Galaxy Mini] midzan21:
WS isn't fixed because I don't have that issue for last 18 months (after cleaning contacts inside phone). WS is one issue which is problematic with some series of phone and not all have it. For RAM usage: let's say that I have about 100MB free RAM within standard usage (and after I close some RAM heavy apps like FB or Chrome with 8 tabs opened) but average for phone is from 120MB to 60MB free RAM from 384MB.
[Samsung Galaxy Mini] Antox97:
[MENTION=4203213]midzan21[/MENTION] I have CWM 6.0.4.7! So I think that I will try with Philz CWM
[Samsung Galaxy Mini] nefescalanadam:
I hope everything is work one day. I will watch your projects, good luck :fingers-crossed:
[Samsung Galaxy Mini] bryanjohn17:
i installed this rom since this morning and currently it has no problem.. i will check further and feedback again next day.. thanks!:good:
[Samsung Galaxy Mini] dogu48:
Where is g apps ?
[Samsung Galaxy Mini] PlayFeast:
You can download it from here.

Thanks for the rom! It works great so far. Do you plan on porting to this device the CyanogenMod 12 version when it comes out?
[Samsung Galaxy Mini] midzan21:
Well I got that issue before few days when I had to use my old 2GB SD card which was almost 100% full. Try to remove some files from SD card using recovery (Mounts and storage, Mount USB storage) and than use your SD card regulary. I freed it up to 40% of size and now it works fine.
[Samsung Galaxy Mini] TurkeyAndroidHacker:
Thanks

Does this rom fast? Is it slow in the game? for example, 10.1 cm very successful and fast. Thank you.
[Samsung Galaxy Mini] Antox97:
No. It isn't
[Samsung Galaxy Mini] midzan21:
For regular daily usage which includes surfing web in Chrome, some Facebook & Messenger, WhatsApp and few other Croatian apps it is fine. I don't play any games so I don't know gaming performance.

AND PLEASE I BEG YOU ALL DON'T QUOTE MY FIRST POST!!! It is one of rules of xda and bunch of other forums where I'm registred. You can quote part of post but not all if it is huge like mine. Thanks.
[Samsung Galaxy Mini] midzan21:
Well if you play games than isn't fast enough. For regular usage it is fast to use it (about 60MB of RAM is free when I close Facebook and Chrome).
[Samsung Galaxy Mini] satfan:
Hi,

got a Problem here, Gapps installed but no playstore or any Google Login at the beginning when starting up the Rom the first time!

Tried to install diffrent Kind of gapps but the playstore wont appear...

can anyone give an advice what to do?

Will try the other Version of the Rom and have a look!

BG
[Samsung Galaxy Mini] Vut:
Hi, I have a problem. I have now installed cyanogenmod 10.1 improved, which works without a problem, and when I installed CyanogenMod 11.0 M12, irritating problem occurs, when I the block and I want to unlock the screen, white screen appears. It happens once or twice that this does not happen, but usually it occurs. You can do something about it?
[Samsung Galaxy Mini] midzan21:
You mean, no any kind of settings at beggining of booting ROM for a first time, or just no Google accounts for add at first time? If it is second thing than you can reflash ROM from stratch and install PA Gapps Pico (I use that Gapps now for few months on any KitKat ROM and on bunch of devices and always get Google login at first boot and first settings) right after CM11 installation (no reboots of any kind, just flash CM11, then Gapps).

It is sporadic thing and I wroted that is issue with some phones before. You can try not to do fast unlocks and locks, and also check if your phone is hotter than usual there should be problem sometimes (that was my issue before year ago when I got last WS on 3.x kernels).
[Samsung Galaxy Mini] satfan:
Thanks for your Advice:

I did a new flash and searched for the PA Gapps Pico,

they work and now everthing is ok, altough the Handy does not seem to be the fastet, ok ist just in emergency cases as a second phone.....

Thanks again!
[Samsung Galaxy Mini] apex39:
Why MSM display drivers, which lack probably causes the white screen, cannot be added to 3.x kernels?
[Samsung Galaxy Mini] midzan21:
Mabe because on OmniROm which uses caf kernel with MSM display drivers (don't blame me if I write something wrong) had issue with black screen during unlock while in some apps, or even worse sometimes phone can't be unlocked because of black screen without any apps in foreground & beackground. I didn't tried that on Whisps kernel, but I would give a try during January while try to port sort of functional Lollipop port (CM12 based, or maybe Omni 5.0 based I need to decide before start doing anything).
[Samsung Galaxy Mini] BlayDee:
Hello, i've found out that Galaxy mini 2 have same chipset as mine. I have GSmart g1345, its pretty rare phone and theres no updates for this device. Last one is GingerBread 2.3.4. I also got sources for it:

repo init -u git://codeaurora.org/quic/qrd-android/platform/manifest.git -b refs/tags/R7227TCNCJNLYA71542302
repo sync

How can i port CM12.0 from to my device?
[Samsung Galaxy Mini] toncata:
Hello! I have been using this rom since it was uploaded. It's great but I have one issue. I have Mi Band and the app cant sync (connect). Anyone can report such a problem? I think it is some kind of bluetooth pairing issue. My N4 (both KK and Lollipop) has no issue.
[Samsung Galaxy Mini] midzan21:
I'm soryy man but I can't port CM12 to your device. It had different chipset MSM7227T while our have MSM7227A which is based on Cortex A5 CPU, while your is based on even older chipset and it doesn't have enough ROM for CM11 nor even CM12 (on Mini 2 we have almost 1GB for system on 4GB of internal storage).
[Samsung Galaxy Mini] BlayDee:
Aww, you're right, my mistake. Thanks for reply tho. Do you know any other device based on MSM7227T maybe?

---------- Post added 30th December 2014 at 12:15 AM ---------- Previous post was 29th December 2014 at 11:42 PM ----------

Wait, here says that ur using msm7227T too O.o Sorry for double post
[Samsung Galaxy Mini] midzan21:
That's what that site said... In reality it is better to check GSMArena where you can see that Mini 2 uses MSM7227A while Gsmart uses MSM7227T . Also I noticed that only some GSmart (or as in my country call it older Chinese phones) use MSM7227T even if MTK6XXX SoC are much cheaper than Qualcomm.