yashsingh1/xdaforums huggingface dataset:
[Galaxy Grand 2 General] drrami75:
i have grand 2 same condition after update to 4.4.2 customer make downgrade after that became completely dead i try sdc not done so i try emmc direct connect so i whant dump file sm-g7102

please help ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
I cannot root it, I cannot install any recovery besides the stock one that comes with it, I cannot get it to connect to the computer as mass storage, only as a media device.

Im thinking I just blew $215 on a paperweight.

I CANNOT EVEN INSTALL TITANIUM BACKUP TO GET RID OF THE FREAKING ATT CRAP!

What have I did wrong?

I have CWM v5.5.0.3!

Ive tried countless number of rooting programs including some poplular ones:

1. Casual - http://xdaforums.com/showthread.php?t=2189536

2. Kingo Android ROOT - http://www.kingoapp.com/android-root.htm

3. Towelroot - https://towelroot.com/

4. CF Root (Flashed SU but does not work) - http://download.chainfire.eu/269/CF-Root/CF-Auto-Root/CF-Auto-Root-d2can-d2vl-sghi747m.zip

CF Root flashed Superuser but it says unfortunately Superuser has stopped.

Im about to take this back to the store I got it from....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OKAstro:
Tell us your phone's specifics (firmware, modem, bootloader, is it AT&T or some other carrier). Does the phone work OK otherwise?

Do you have a ROM you want to try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
How are you flashing the recovery? Do you have Knox on your phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
Model Number: Samsung-SGH-I747

Its an At@T Phone with a new AT@T sim card in it. The phone works on stock stuff. It will boot up just fine with CWM installed but I cannot actually go into CWM. It just gives me a black screen.

Android Version: 4.4.2

Baseband Version: I747UCUFNE4

Kernel Version

3.4.0-1514807

dpi@SWDD3003 #1

Mon May 19 21:00:05 KST 2014

Build number: KOT49H.I747UCUFNE4

SE for Android Status:

Enforcing

SEPF_SAMSUNG-SGH-I747_4.4.2_0016

Mon May 19 20:59:50 2014

It doesn't matter if I got a ROM or not. I cannot install a custom recovery.

I am flashing Recovery thru Odin. Ive even tried different versions of Odin from 1.7 to 3.09. I prefer to use Odin 1.85.

And I have no clue what knox is or even if its installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OKAstro:
Have you tried this thread?

http://xdaforums.com/showthread.php?t=2789917
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
Im not able to flash a working custom recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OKAstro:
Well - maybe try flashing the stock 4.42 ROM again through Odin and then if that sticks, try the steps in the thread I linked

Good luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
I had booted into download mode being about to flash CWM to my phone via Odin (Again) and I noticed this:

(If you cannot see it it says):

Factory Mode

Product Name: SGH-I727

Current Binary: Custom

System Status: Custom

Qualcomm Secureboot: Enable

Warranty Bit 1

Bootloader AP Swrev: 3

Is this bad?

Am I still able to root?

Am I able to install custom Recovery?

Am I able to install ROMS like CM 11?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OKAstro:
The fact that you can get to download mode is good. But sorry, what this means is out of my league. Try PM'ing "DocHoliday77". He seems to be a great resource for all things SGS3. He's in numerous threads in the Development forum

EDIT: I booted into download and mine says the exact same thing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
You have Knox on your phone. You tripped the knox counter and changed the warranty bit to 1 which means the warranty on your phone has been voided.

When flashing a custom recovery phone in Odin, do not check auto reboot. When you see the word reset appear in the status window, remove the usb cable, pull the battery, and use the button combo to boot inter recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
No still nothing.

It vibrates when you first start it up and then the Samsung logo comes up with Recovery is starting in blue at the top for about a second and then goes to a black screen and nothing never happens afterwards.

What is Knox by the way? Is this keeping my phone from being rooted?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Figured id post here now rather than having two threads going for the same problem.

The more this goes on though, the more i am suspecting some sort of hardware problem.

I want to suggest using the PIT file to repartition the device, but theres no firmware to use along side it. Theres a program here on xda called PIT Magic i think. I dont know much about it, but maybe it could help you to somehow repartition....?

As for knox, there is tons of info out there on it already,so i wont get into it here. It wont block you from rooting, but it can deny root access when an app requests it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
Will the pit wipe it?

Will installing cm 11 using the installer work? Does it work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Yes, repartitioning will wipe your data.

I dont use CM roms so im not familiar with the installer. Sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
My main thing is I want to root my unrootable SGS3 so I can remove the ATT crap.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Im out of ideas for you...sorry. I kinda think its probably a hardware issue. It sounds like youve done everything you can to get root or recovery. Might be wise to start looking into a motherboard replacement...and keep your backups up to date!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
I just spent $215 on this. I don't think the place where I bought it from will ever take it back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
I wish i had something better for you to try. Sorry.

If you are willing and able to consider it, i saw several motherboards and devices with broken screens (but otherwise functional) go for less than $65 today. Its the best option i can think of now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
Where at?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Sorry. It was on ebay. They often will go for a bit more than that, but if you are patient you should be able to get one relatively cheap.

Just do not buy any that say no power. Just look at ones that are a good motherboard, or a device with a broken screen where they say it powers on, just with no display. Also make sure the IMEI is clean.

Good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
I am going to visit my sister near Bryan Texas. I'm going to see what josh groce from mobiletechvideos.com can do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Cool. Let us know what he finds!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
Ok.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
Good news!

after 5 days and 263 attempts I now have a working CWM on this phone. CWM 5.5.0.3.

Still trying to find a solution for Root....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
Ran Root checker Pro and this is what it give me:

Root Access is not properly configured or was not granted.

Super User Application Status:

Superuser application - version 3.1.3 - is installed!

SuperSU application - is NOT installed.

System File Properties for Root Access:

Standard Location

Check Command: ls -l /system/bin/su:

Result: /system/bin/su: No such file or directory

Analysis: File /system/bin/su does not exist.

Standard Location

Check Command: ls -l /system/xbin/su:

Result: -rwxr-xr-x root root 380532 1969-12-31 18:18 su

Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!

Alternative Location

Check Command: ls -l /sbin/su:

Result: /sbin/su: Permission denied

Analysis: File system permissions restricted and denied access.

Alternative Location

Check Command: ls -l /system/xbin/sudo:

Result: /system/xbin/sudo: No such file or directory

Analysis: File /system/xbin/sudo does not exist.

Root User ID and Group ID Status:

SU binary not found or not operating properly

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

ADB Shell Default User:

ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Dont use Superuser, its very, very old. Use SuperSU. Download here and flash in recovery.

http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip

Reboot and open the app to let it disable knox.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
When I open SuperSU I get this message:

Unfortunately, SuperSU has stopped.

After I hit OK it never opens, so I guess knox is keeping this from launching?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
I rerun Root Checker Pro and this is what it gave me:

Super User Application Status:

SuperSU application - version 2.02 - is installed!

System File Properties for Root Access:

Standard Location

Check Command: ls -l /system/bin/su:

Result: /system/bin/su: No such file or directory

Analysis: File /system/bin/su does not exist.

Standard Location

Check Command: ls -l /system/xbin/su:

Result: -rwxr-xr-x root root 125424 1969-12-31 19:03 su

Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!

Alternative Location

Check Command: ls -l /sbin/su:

Result: /sbin/su: Permission denied

Analysis: File system permissions restricted and denied access.

Alternative Location

Check Command: ls -l /system/xbin/sudo:

Result: /system/xbin/sudo: No such file or directory

Analysis: File /system/xbin/sudo does not exist.

Root User ID and Group ID Status:

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

ADB Shell Default User:

ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Can you go into app manager and disable any Knox related apps? When youtry to use an app requiring root do you get a message in the statusbar?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
The "Turn off" button is greyed out on all of the Knox related stuff.

And using Titanium backup as an example, it gets stuck on "Asking for root rights".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
You could try flashing the stock rom from enewman17.

Or using cwm built in file manager, delete the knox apk's.

Otherwise the only other thing i could think to recommend would be to start over with a fresh firmware flash, which im pretty sure you want to avoid!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
Where are knox apks kept at?

I want to avoid from having to flash a rom. If I flash anything, I am putting CM11 on this....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
/system/app and /system/priv-app

There are knox removal scripts around too. If on 4.4.2 they may not work, but you can look at the script for an idea of what exactly needs to be removed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
Scratch my previous reply.

I now have full root on this phone.

I ended up copying the Superuser.apk from This .zip file and putting it on the root portion of my sdcard.

Then I used "My Files" in my app drawer to browse for the superuser.apk i placed on earlier and installed it. Do the all option.

After that has completed, I got the message that SuperSU detected Knox and removed it successfully.

Now Titanium backup works great now and no longer hangs on Asking for root rights.

Root Checker Pro:

Congratulations! You have root access!

Super User Application Status:

SuperSU application - version 2.02 - is installed!

System File Properties for Root Access:

Standard Location

Check Command: ls -l /system/bin/su:

Result: /system/bin/su: No such file or directory

Analysis: File /system/bin/su does not exist.

Standard Location

Check Command: ls -l /system/xbin/su:

Result: -rwxr-xr-x root root 125424 1970-01-01 09:01 su

Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!

Alternative Location

Check Command: ls -l /sbin/su:

Result: /sbin/su: Permission denied

Analysis: File system permissions restricted and denied access.

Alternative Location

Check Command: ls -l /system/xbin/sudo:

Result: /system/xbin/sudo: No such file or directory

Analysis: File /system/xbin/sudo does not exist.

Root User ID and Group ID Status:

Root user id:

uid=0(root)

Root group id:

gid=0(root)

System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

ADB Shell Default User:

ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
Huge thanks for everyone who helped me with this. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnapolean1:
One little annoyance I have is every time I restart the phone or turn it off I have to repeat the SuperSU install or I just get the error: Unfortunately, SuperSU has stopped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Try copying it to /system/app and setting permissions.
[Transformer TF300T Q&A, Help & Troubleshooting] costaslalas:
Hi, i have an Asus tf300t (with 4.2.1). when i boot in recovery ( volume down + power) and press the RCK button, i stuck with error (red triangle). Pressing the power button the asus starting again normally. My question : how can i solve this problem and load custom rom?
[Transformer TF300T Q&A, Help & Troubleshooting] cmendonc2:
Have you flashed a recovery, such as TWRP yet? That usually occurs when there is no custom recovery installed. You need to flash a recovery in order to use the recovery :p
[One (M7) Q&A, Help & Troubleshooting] bboybtek:
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo O.o after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.

When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...

I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
[One (M7) Q&A, Help & Troubleshooting] alray:
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.

You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.

When your drivers issue are solved, flash twrp 2.6.3.3:

fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader

then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
[One (M7) Q&A, Help & Troubleshooting] bboybtek:
The only weird thing is, I used the 2.7.1.1 to flash the sense rom in first place and everything worked fine :/ . Anyway, thanks for the shout! :good: I'll give it a try right now and see how it goes.
[One (M7) Q&A, Help & Troubleshooting] bboybtek:
Right, I'm having problems installing the drivers for some reason. The ones downloaded from this thread don't seem to be doing anything at all. When click on them they show up for a split second in task manager and then they disappear. No install wizard no nothing. So i downloaded the ones for Windows 7 from here but this just gives me a message that "Windows could not find driver software for your device." . I mean, what the hell? O.o

Edit: Right, after a lot of struggle I've managed to successfully bring my phone back to life! I have no idea what caused the issues with installing the drivers. I've spent ages deleting every trace of HTC drivers, then installed Windows 7 ones and somehow it worked. Then flashed t.w.r.p 2.6.3.3 and venom and it seems to be working smoothly! Hopefully no more problems :) . Thanks a lot for helping out man!
[Android Apps and Games] Trofimcheg:
Your task is to keep changing the meandering path of movement, think it's that simple?

ZigZag Trip change your opinion! 3D graphics and easy controls make ZigZag Trip incredibly addictive and fun game. Download now!

P.S. tell me what can I add or change in game please.

Download:

https://play.google.com/store/apps/details?id=com.TastyGames.ZigZagTripFree

Gameplay:

[YOUTUBE]watch?v=V0rNAh4MG5k[/YOUTUBE]
[Android Apps and Games] vsgames:
Just some advices:

1) Add background music

2) Add "Exit" button

3) If you make route wider at beginning it will be more simply to start playing.
[Android Apps and Games] Yellon:
1) Make it easier at the beginning.

2) A bit boring after a while.
[Android Apps and Games] Trofimcheg:
Thanks for your comments, in the next update, I'll consider your advice!
[Android Apps and Games] Trofimcheg:
Update 1.4!

- Added new buttons,"exit" and "mute"

- Added background music

- optimized gameplay

P.S tell me what can I add else please
[General Questions and Answers] adamski88:
Hi,

Been contemplating getting the LG G3, I really like the specs and the screen size however Ive heard completely mixed reports about how good it performs. Lots of people say its laggy, then other say the updates fixed it, some say they didnt fix it etc etc!

I went into carphone warehouse today to test one, which probably didnt have the latest update, and did have large amounts of crap on it... but it was incredibly slow, opening a picture took about 2 seconds, going back to home screen etc took forever, compared to the HTC One m8 it was like a prehistoric phone.

Could anyone confirm whether the lag is actually fixed cuz I kind of really want this phone!

Cheers

Adam
[Asus Transformer TF701] aMachi:
Hi to everyone.

I was updating my tab to the latest version of the ROM of sbdags.

Everything was fine until i reboot the tab to use it for the first time: loop in the boot animation and never come out from it.

I came from the previous version of the rom, the Cromi-x 6.1 with 10.26.1.18 bootloader.

The process i use to update was this:

1) wipe of data/factory reset, wipe with format /boot, wipe with format /system

2) Install the CWM recovery 6.0.5.0 and update the bootloader to 11.4.1.17 by flashing they with the file that you can find in the rom page.

3) repeat point 1

4) install the rom by flashing it from an SD. Complete the Aroma installer and answer to every option that it ask to me.

5) reboot the system and stuck in the bootanimation :(

I use the WW format cause i'm italian and i check the md5 :(

What's wrong? I can go to recovery everytime i need and i have a backup just in case i need it.

Sdbags, i really want to offer you a beer for your work. I think i will do it in every case, but yes, kitkat on my tab would be great :victory:

Sorry for bad english. For every question, i'm here. Thanks a lot.

M.
[Asus Transformer TF701] sbdags:
Don't do step 3. Try it again please.

Try the default options first.
[Asus Transformer TF701] sbdags:
That log is fine - everything is installed.

Read out the bootloader version from the bootloader screen to double check please.

Also you are rebooting after installing the bootloader and cwm package aren't you?
[Asus Transformer TF701] aMachi:
When i install cwm and bootloader package i reboot from cwm but i stuck in boot animation. The same that happen when i try to reboot after install the rom.

In bootloader screen i read

Android macallan-user BL released by WW_epad-11.4.1.17-20140711
[Asus Transformer TF701] sbdags:
Right and then you boot back to CWM, do a full wipe (you may need to wipe your internal sdcard so back it up first) and then flash the rom. After that it should boot fine.

If not please search xda for how to get a logcat and post one of it bootlooping please.
[Asus Transformer TF701] aMachi:
I try the first thing that you say but nothing, still loop in bootanimation.

I'll do a logcat through adb in the afternoon. Now i had some problem cause i can't mount usb storage through cwm for some reason. Late i'll find drivers or what's missing.

Maybe can help: when i reboot frequently cwm ask me if i want to fix root. It's normal?

Thanks you for your help.
[Asus Transformer TF701] sbdags:
That message is normal. Just a bug in CWM.

We need to find why you are bootlooping.
[Asus Transformer TF701] aMachi:
Ok, logcat is here.

Hope it can help.
[Asus Transformer TF701] sbdags:
OK You got some serious problems there. It would appear that your internal sdcard doesn't mount:

D/Vold ( 359): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)

D/Vold ( 359): *********** Success!! "ro.epad.mount_point.sdcard=/mnt/media_rw/sdcard"

D/Vold ( 359): Volume usbdrive state changing -1 (Initializing) -> 0 (No-Media)

D/Vold ( 359): *********** Success!! "ro.epad.mount_point.usbdrive=/mnt/media_rw/usbdrive"

I/Vold ( 359): opening the sysfs of TF701

E/Vold ( 359): lookupVolume usbdisk1 failed!

E/Vold ( 359): lookupVolume usbdisk2 failed!

E/Vold ( 359): lookupVolume sdreader failed!

D/Vold ( 359): checkUsbdisk sucess.

D/DirectVolume( 359): i:0 minor:48

D/Vold ( 359): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)

D/DirectVolume( 359): i:1 minor:49

D/Vold ( 359): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)

[MENTION=5123642]lj50036[/MENTION], [MENTION=4878287]_that[/MENTION] any suggestions for this one?

[MENTION=5854617]aMachi[/MENTION] - what is the SKU of your device? And you can restore a nandroid back to 4.3 and it works fine?
[Asus Transformer TF701] aMachi:
i've some problem to find the SKU code. I search on the box of the tablet but there are too many codes and i don't know what's the right. Can you give me an exemple of it?

Yes, i can restore to 4.3. In this right moment i'm writing with the tab with cromix 6. Everything seems to work fine.

In case like this you really know how much important is to do a backup.. ;)