yashsingh1/xdaforums huggingface dataset:
[Galaxy Grand 2 General] ##W4TCH0UT##:
This is a tutorial for noobs or members who are new to Rooting and want to root their phone.

Downloads:

*Odin 3 v3.0.9

*CWM recovery thread(Downloads available for 4.3 and 4.4 also)

*SuperSU

Steps to root your phone:

1) Download the first two files given above to your laptop/PC.

2) Turn off your phone.

3) Go to download mode (by pressing Vol.down+home+power buttons at the same time for about 7-8 secs)

4)Open the ODIN file you downloaded on your laptop/pc.

5) Connect your phone to your laptop/PC through USB cable(do I have to tell that :p)

6) When ODIN detects your phone, the ID:COM area will become yellow/blue

7) In ODIN click on PDA and then select the recovery file you downloaded. Also tick the check box beside PDA(if there is any)

8) Click on start. The flashing process will start.

9) If the flashing succeeds, ODIN will show 'PASS'. That means the recovery flashed successfully. Yay!!!

10) Now turn on your phone and download the third file and place it in your external SD card.

11) Turn off your phone.

12) Reboot to recovery(by pressing Vol.up+home+power buttons).

13) The recovery will start. You have to navigate by volume buttons and power button.

Vol.up - move up

Vol.down - move down

Power button - select option

14) Select 'install zip'.

15) Select 'Choose zip from ext_sd or external SD card'.

16)Select the third file you downloaded. Flashing process will start.

17) After it finishes, go back and reboot your phone.

It's upon you, of you want to follow this:

18)Use Knox Remover to remove all Knox files.

Enjoy your rooted Galaxy grand 2!!! Now you can flash other recoveries or flash other custom ROMs or custom kernels.

Some useful tips(Experimental/WIP):

You can use Triangle Away to reset the flash counter after flashing ROMs and make your device status from custom to official. This is a really useful app. Report here if it works. You needn't download from google play, you can scroll down and download from the attachments.

CREDITS:

[MENTION=2614663]shabbypenguin[/MENTION]: For CWM recovery.

[MENTION=631273]Chainfire[/MENTION]: For SuperSU and Triangle Away.

[MENTION=4648515]AL_IRAQI[/MENTION]: For Knox remover.
[Galaxy Grand 2 General] jeetujaan:
Its working or not
[Galaxy Grand 2 General] viewedit:
Will this work on Kitkat 4.4.2
[Galaxy Grand 2 General] ##W4TCH0UT##:
yep.
[Galaxy Grand 2 General] viewedit:
I did what was in description,, It didnt work on 4.4.2, but it has modified the phone,, as when I try update it says phone has been modified, try to update through kies...
[Galaxy Grand 2 General] shabbypenguin:
you need to flash supersu in recovery, load up supersu when you have rebooted and have it disable knox, then reboot into recovery and reflash supersu and youll be rooted.
[Galaxy Grand 2 General] sbsharma:
Have you tested it?
[Galaxy Grand 2 General] ##W4TCH0UT##:
I don't have this device, but I think shabbypenguin is right. Follow that method for kk. I'll update the thread, once kk recovery is released.
[Galaxy Grand 2 General] BuHaneenHHHH:
I used towelroot v1 to root my G7102 on JB 4.3

I flashed the indian stock rom to get the update to kitkat and now downloading the update for kitkat

after updating I will test towelroot on 4.4.2 and post results
[Galaxy Grand 2 General] shabbypenguin:
Similar, I'm in teh US with a nexus 5, in no way shape or form will i ever hold this device in my hand so no way for me to test it out.

there will be no kitkat recovery, the mere fact he booted to recovery and was able to flash the supersu means that is is working. the cwm i put out is already compatible with 4.4
[Galaxy Grand 2 General] viewedit:
I had even flashed the super user it failed saying couldn't verify signature. When u boot in recovery it doesn't say CMW recovery. In the center of the screen under the logo it says no command and down in the screwn it says manual mode.

About knox I checked there is nothing I can disable. while in recovery..

I have used Cwm in s2. . So I know it's interface..
[Galaxy Grand 2 General] shabbypenguin:
you had stock recovery not cwm
[Galaxy Grand 2 General] viewedit:
One last Question

Well then the CWM didnt flash through odin,, its funny bec Odin gave all the indication that it successfully flashed the recovery.. Just one last thing I need to know,, I am sure somehing is broken at the recovery/software level now..as when I check for software update, it says ur device has been modified,, how do I fix this.. flashing stock 4.4.2 rom?
[Galaxy Grand 2 General] shabbypenguin:
You need to uncheck auto reboot in odin. When it finishes flashing disconnect the device and pull battery. Then put it back in and manually boot to recovery
[Galaxy Grand 2 General] AnTeBiOs57:
Is this process work on sm-g7105 ?
[Galaxy Grand 2 General] ##W4TCH0UT##:
Don't know. You can try and post here if it works.
[Galaxy Grand 2 General] b0rni67:
Booterror

I have "Could not do normal boot" when I boot to recovery
[Galaxy Grand 2 General] shabbypenguin:
use teh new cwm thats for ng4
[Galaxy Grand 2 General] b0rni67:
Help me? NG4?

Sorry, what Device is NG4? SG4?

6.0.3.2 for Samsung Galaxy S4 (i9500) ?

Thxs
[Galaxy Grand 2 General] shabbypenguin:
No. NG4 is the build number of the new 4.4 update for the g7102
[Android Q&A, Help & Troubleshooting] lolwatpear:
I'm trying to understand how the recent apps screen works in android. I really like the card-style recent apps used in HTC sense. Unfortunately, I've never seen an alternative rom or some app be able to do this. So, I want to know, is the recent apps/task switcher based on an apk somewhere in the system? Is it possible to modify the recent apps easily with an alternative apk or something? How would you go about getting the sense recent apps under a different phone?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mforce:
A friend om mine owns an MDA Vario, upgraded to Molski's 2.26.. The Wizard lags horribly at games, music and any other cpu intensive task (even before Molski's ROM!), their are also strange logfiles on the root of the wizzard (dbgtostorage..) about 4MB each, they pile up and one of them (active one..) can't be deleted so its in use by something.. what could it be?

Anyway, I think it's an hardware issue and want to send it for RMA, before doing that I want to flash it back to stock Dutch TMobile IPL/SPL/ROM..

For some reason the SPL can't be downgraded? ROM and IPL change after an update but the SPL sticks at 2.26 (Molski's)

The latest TMobile (2.21) can't be used :( asks me to find a newer updatetool, can't downgrade..

I've already tried Boot's 1.05 but it won't downgrade the SPL and also tried the Cingular 1.8, same problem.. SPL stil 2.26..

What would happen if I would flash an G4 device with G3 IPL\SPL, would the device stil work but crash or is it just not possible to flash G3 on G4 device?

Is their some commandline IPL\SPL\ROM updatetool without checks and stuff?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mforce:
(Thnx to Dr Puttingham for posting a solution in another topic and faria for making it possible)
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Dr Puttingham:
Glad I could be of assistance!
[TouchPad Q&A, Help & Troubleshooting] parimalnyk:
It is recommended to have the following partition layout for CM 11:

Quote:

system - 600mb

cache - 200mb

media - 400mb

data - [remaining space] (i.e. ~11.5gb for 16gb TouchPads)

How can I check this on the existing HP touchpad? Please mention any per-reqauisite software required if any to execute the command to display this information.
[One (M7) Q&A, Help & Troubleshooting] illy_80:
I can't figure out which update variant I should be using. Here's what I get with getvar all:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.14.3250.13

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.401.2

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4245mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))

finished. total time: 0.068s

I updated the modelid from PN0712000 to PN0710000.

I've tried:

RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1

OTA_M7_UL_JB43_SENSE55_MR_HTC_Europe_3.62.401.1-2.24.401.8_release_338160gxmo5sd9337kadux

OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404wj19h95c0x6oa19n

They all fail. Any suggestions?
[One (M7) Q&A, Help & Troubleshooting] majmoz:
The RUU is an executable file and has to be run from windows. You just have to double click the file and it will run, then just follow the prompts. The OTA will not run because you have the wrong version on your phone, it doesn't match. Double check to see if the MD5 is correct for the RUU and try again. Then let us know at what step it failed, if it was not successful.
[Galaxy Note 3 Q&A, Help & Troubleshooting] mneimeyer:
I have a new desk job and I've been abusing the new T-Mobile free music data to listen to Pandora all day which is killing my battery.

When I plug my Note 3 into a USB 3 Port it defaults to USB 2 mode. I know I can go to "USB computer connection" in settings and change it to "Media device (USB 3.)" to get it to change over. Does the fact that I have to manually change it over to USB 3 for data mean that I'm also not getting USB 3.0 900mA to charge with?

An additional frustration is that it is hard to test that because if I don't use the USB 3.0 to transfer data then it eventually "falls back" to USB 2 mode automatically. Is there any way to make it stay USB 3 when plugged into USB 3?

Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] master123467:
It defaults to 2.0 because a lot of computers and laptops that people have dont always have usb 3.0, if you can do it you have the option to switch
[Galaxy Note 3 Q&A, Help & Troubleshooting] mneimeyer:
Fair enough, but it seems like the Note has the ability to detect that it is plugged into a USB 3 port because it only offers the USB 3 media mode when it is.

Also, any ideas on whether the data mode affects the ability to charge at the higher USB 3 900mA instead of the USB 2 500mA?
[Huawei Ascend P6, Mate] Mezzi:
Hello everyone, I am having trouble installing font themes on my Huawei phone. I use ifont and I select huawei mode, the theme appears in the app themes and I select the font because the theme has the font name. I reboot and the theme is applied but after a couple of hours the font becomes gibberish and I have to reboot. When I reboot the phone reverts to the original font. Even if there is no problem and I turn off the phone, when I restart it the original font is there instead of the new theme font.

I have also tried putting the hwt files in the hwthemes folder but when I do these themes do not appear in the theme app so I cannot select them.

I really hate the fonts that came with the phone and would really love to find a permanent way to change the font.

Thanks in advance for your help.
[Huawei Ascend P6, Mate] ivanskie01:
Is your phone rooted? I think the most stable way of installing fonts is rooting the device and using font-replacing apps that needs root permission :)
[Huawei Ascend P6, Mate] danielpsx:
you can use other software that changes fonts, i used on some samsung galaxy s a software called Font Installer, the phone was rooted, heres the link

https://play.google.com/store/apps/details?id=com.jrummy.font.installer remember you must be rooted, i havent tested it on my p6... so do some backup, and donwload the rom you are using now on your sd card on a folder called dload, so if you get boot loop you can reapair it faster.
[One (M7) Android Development] ssrij:
Say hello to Android L Developer Preview for HTC One​

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

What is this?

This is a direct port of Android L Developer Preview, which was released for the Nexus 5 and Nexus 7 (2013, WiFi). This is not a SDK port, this is the real deal!

How did you do it?

Magic! Just kidding, a lot of hard work went into porting everything. Special thanks to these mega awesome guys, this ROM would've not been possible if they didn't help us (make sure you thank them too):

sykopompos - For helping me out with ramdisk and providing useful tips

poondog - For helping me fix the graphical glitches in kernel (and yes, I am using his awesome kernel)

feltox and manups4e - For helping me in additional debugging of the builds

What works and what doesn't work?​

At the moment, this port is in alpha stages. We are working really hard every day to fix the major issues quickly, but since this is a non-Nexus device, it's quite complicated to get things working smoothly. Half of the things work, half of the things don't work.

You are more than welcome if you want to help us in fixing bugs, together we can eliminate the bugs and fix issues faster

What doesn't work at the moment:

WiFi

Bluetooth

Data DATA WORKS NOW (thanks to [MENTION=2849215]manups4e[/MENTION])

Sensors (except GPS)

Camera

Sound

What works at the moment:

Everything else as far as I know, but do let me know if you find anything else that doesn't work

Once again, this is currently in ALPHA stage and we are working to fix whatever is not working, so please don't spam this thread with posts like "Camera does nt work, what 2 do"

Screenshot

How to install:

Download the ROM

Place the ROM in your internal storage/SD card

Reboot into recovery (MUST BE LATEST TWRP/CWM)

Wipe the following partitions: cache, dalvik cache, data and system

Flash ROM

Reboot

First boot takes around 10-15 minutes

Download

ALPHA 2:

https://docs.google.com/file/d/0B64IJ9xlDpb4UFRiTkVOWm9rVkU/preview

Changelog

10/8 - ALPHA #2

> Fixed data (3G/4G now works)

11/7 - ALPHA #1

> Initial build

FAQ

Q. Can I flash a custom kernel on top of it?

A. No, we use a heavily modified ramdisk and kernel, so if you flash another kernel the ROM will stop booting. DO NOT FLASH ANY CUSTOM KERNEL ON TOP OF THIS

Q. XYZ doesn't work

A. This ROM is currently in ALPHA stages so that is expected. On top of that, Android L is currently a developer preview so any bugs in the developer preview will show up on this port as well.​
[One (M7) Android Development] poondog:
Hi everyone,

GPL required Kernel source here, more info soon

https://github.com/poondog/android_kernel_htc_msm8960
[One (M7) Android Development] fcjan:
looks nice, great job!! I will try it when few bugs are ironed out, don't have time right now. Keep up the good work :highfive:
[One (M7) Android Development] sykopompos:
Camera dnt work, wat 2 do?

Sent from my C6916
[One (M7) Android Development] manups4e:
ahahahahahahahhahahah
[One (M7) Android Development] cygnus56:
:D
[One (M7) Android Development] lewonsky:
keep it up...hope others can also help solve the existing problems
[One (M7) Android Development] HeavyHDx:
Those bugs should be fixed much quicker now that more people have acces to it... at least I hope so.
[One (M7) Android Development] manups4e:
you forgot to mention that mtp doesn't work properly too....to me htc one is shown on mobile devices but i can't access the sdcard without adb
[One (M7) Android Development] ARNOB:
What is the kernel used? Maybe that is the main reason for most of the bugs since most of them are driver related issues.
[One (M7) Android Development] sykopompos:
I'm not sure what one of my guys did to fix that but it was fixed. What are you guys using for your base? N5 and n7 mixed or the n4 port? We fixed a lot of things in the port that wasn't working right in the Dev preview

Sent from my C6916
[One (M7) Android Development] manups4e:
the kernel is aosp with cyanogenmod cafs (thx poondog) and the ramdisk files are the cm ones updated with latest android L strings
[One (M7) Android Development] ssrij:
N7 2013 + app, priv-app and framework from N5 + proprietary files from GPE
[One (M7) Android Development] ssrij:
The kernel is by [MENTION=4379011]poondog[/MENTION], he modified it a bit to fix the graphical glitches on our ROM.
[One (M7) Android Development] manups4e:
proprietary files from gpe have different dimensions then the cm ones....if we are using cm cafs isn't it better to use cm proprietary files?
[One (M7) Android Development] sykopompos:
I've split the boot image and seen that yesterday. I might look at the gpe ramdisk tomorrow and maybe that can be cleaned up a bit better then mucking around in the cm one removing the extra crap that you guys don't have and if you did would probably break L

Sent from my C6916
[One (M7) Android Development] ssrij:
libs don't have "dimensions" lol

I am not using anything from CM in the latest build, it's all from GPE
[One (M7) Android Development] sykopompos:
You guys should have used the n4 port as a base, there is a lot of stuff that we went through and fixed in it that is broken if you use the developer preview bases. I thought you switched to us for your base and that is why I couldn't understand why some things weren't working when I knew they were working and fixed in the n4 port

Sent from my C6916
[One (M7) Android Development] manups4e:
ahahaha i'm italian...forgive me...in italy bytes and multiples are called "dimensioni" and i translated accidentally wrong ^^ what i was saying is that cm proprietary files and gpe proprietary files have different filesizes ^^
[One (M7) Android Development] ssrij:
I tried to but was having way more issues. Anyway, I'll look into that again tomorrow, right now I have to clean the builds, there are lots of libs and files that are specific to flo and serve no purpose to m7 so gotta throw them away.
[Galaxy S III Q&A, Help & Troubleshooting] MikeCordero:
<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CheckROM_V4_LG8.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

Please help work phone my skype mike.2477
[Galaxy S III Q&A, Help & Troubleshooting] Ler Gies:
You should Forced to restart your phone and try to use odin do it again.
[Galaxy Note 3 Q&A, Help & Troubleshooting] vinokirk:
Just updated to Maps 8.1.1 but it keeps FCing when opened.

Anyone else?
[Galaxy Note 3 Q&A, Help & Troubleshooting] MystaMagoo:
Nope not here but I don't like or use GM because of it's need to use data.
[Galaxy Note 3 Q&A, Help & Troubleshooting] vinokirk:
Cleared cache and dalvik from recovery+ all is OK now :)
[8125, K-JAM, P4300, MDA Vario General] Seppl82:
Hi,

ive extracted my nk.nbf file (comeing from Vario_AKU2.0_05-2006.exe ) with typho5.exe -x nk.nbf and got the following files...

80040000-OS_0.nb

9b000000-Extension.nb

96000000-GSM_0.nb

91000000-SPL_1.nb

90000000-IPL_1.nb

91000000-SPL_2.nb

90000000-IPL_2.nb

9d000000-HTC.nb

92000000-Splash.nb

But, its not possible to extract more than 2 Megabyte from 80040000-OS_0.nb with dumprom.exe? (dumprom.exe 80040000-OS_0.nb -d test)

Ive only got the files below... Where is the failure? I've want to get the files usualy but to My Device/Windows

29.10.2006 00:43 342.824 nk.exe

29.10.2006 00:43 269.840 coredll.dll

29.10.2006 00:43 153.252 filesys.exe

29.10.2006 00:43 43.504 cecompr.dll

29.10.2006 00:43 2.608 device.exe

29.10.2006 00:43 36.584 devmgr.dll

29.10.2006 00:43 5.736 regenum.dll

29.10.2006 00:43 12.808 busenum.dll

29.10.2006 00:43 44.040 pm.dll

29.10.2006 00:43 65.688 fatfsd.dll

29.10.2006 00:43 10.024 diskcache.dll

29.10.2006 00:43 31.012 fatutil.dll

29.10.2006 00:43 45.224 imgfs.dll

29.10.2006 00:43 21.024 rawfs.dll

29.10.2006 00:43 13.816 romfilter.dll

29.10.2006 00:43 80.216 fsdmgr.dll

29.10.2006 00:43 19.848 mspart.dll

29.10.2006 00:43 22.752 ramfmd.dll

29.10.2006 00:43 6.376 ramdisk.dll

29.10.2006 00:43 47.800 cereg.dll

29.10.2006 00:43 223.248 updateapp.exe

29.10.2006 00:43 13.280 packageinfoapi.dll

29.10.2006 00:43 13.984 ceddk.dll

29.10.2006 00:43 27.008 serial.dll

29.10.2006 00:43 46.596 sdbus.dll

29.10.2006 00:43 12.808 sdmemory.dll

29.10.2006 00:43 6.312 mmtimer.dll

29.10.2006 00:43 57.936 dwnldapp.exe

29.10.2006 00:43 12.520 updatemgr.exe

29.10.2006 00:43 2.616 certmod.dll

29.10.2006 00:43 2.592 uldrui.dll

29.10.2006 00:43 188.420 TrueFFS.dll

29.10.2006 00:43 29.688 OMAP850_SDHC.dll

29.10.2006 00:43 2.448 ceconfig.h

29.10.2006 00:43 33.150 initobj.dat

29.10.2006 00:43 40.960 boot.hv

29.10.2006 00:43 65.536 default.hv

29.10.2006 00:43 28.672 user.hv

Edit/Delete Message
[8125, K-JAM, P4300, MDA Vario General] Seppl82:
I cant believe that nobody else than me has this problem...
[8125, K-JAM, P4300, MDA Vario General] Seppl82:
And the most exiteing is that i dont get any search results if i take a look for nk.nbf
[Xperia SP Q&A, Help & Troubleshooting] copy2050:
Hi all, i want to know if anyone know's some app's have ported to Xperia SP from te LG devices like the task killer and file manager, these two i want it on my XSP because i have a LG G Pad and have to say that two are very efficient app' and most important: cea app's doesnt have better.

Already search in web but dont find any of that app's.

If anyone can help i will be thankd 4ever! :)
[Fairphone 1] einsweniger:
Since support can't help me I am turning to you guys. (also first post yay ;D)

I'd like to use the Fairphone as device to run my Apps I develop for android.

Since I own multiple android devices I can point out, that the FP1 is the only device suffering from this problem.

Problem:

The FP1 just spews hundreds of logcat messages per second, even Android Studio can't keep up with all the lines the FP1 produces. I'd provide a log, but I can't possibly sort through all the lines it produces, possibly leaking information I don't want public, because I can't even grasp what might be output. (2 Minutes of Logcat is 47272 lines of output)

I'm getting output for every single decoded and/or scaled media, SSL certificate checks, what the LED is doing, basically every little step my phone makes. I even get Log.wtf() outputs o_0

And the spam is so agressive I can't even find my debugging messages between all this.

Possible Cause/Replication:

I've tapped the "build number" (settings > about phone) quite a few times while playing around with the phone, problem is I don't know if it was like this by default or if this is a general problem with FP1.

I've tried until now:

I've written FP-Support twice now, first request got lost, the second pointed me here :/

I since reflashed it via SPFtool because I tried fixing this by deleting /system (don't ask -.- brain fart), but the output persists.

I have played around with the cmdline tool called xlog (/system/bin/xlog) which can filter some of the output of logcat, seems MediaTek specific, don't know if FP1 specific. That has toned it down quite a lot, but some of the vital Exceptions are also filtered out. That left me puzzled for a while because my App crashed and I did not get any output via logcat, what I did wrong. Also: some outputs seem to be caused by a binary called logwrapper which forwards stdout, stderr messages of cmdline tools to logcat. like netbsd-lib output for DNS resolving. It's started via init, so I can't do much about it and some messages won't even filter via xlog.

Has anybody experienced this and/or knows a fix? I'm stumped

If not, can you replicate so we can suffer together? o_0'

best regards

David
[Fairphone 1] _keesj:
Hi,

The thing to look for is how to lower the system log level. The loglevel is set in /init.rc using the loglevel syntax (in the ramdisk)

http://elinux.org/Android_Debugging#init_logging. Our next builds will have a lower logging level and you can not modify this easily until we can build our own kernels/repack the kernel.