Database Info

[Q] Dead touchscreen

Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.

Sapphire18 said:
Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.
Click to expand...
Click to collapse
Em so is the bootloader unlocked? you could try to see if adb is working in fastboot or if it is unlocked I think TWRP lets you use adb.

Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.

Sapphire18 said:
Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.
Click to expand...
Click to collapse
Ok but have you tried adb in fastboot?

adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.

Goatshocker said:
adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.
Click to expand...
Click to collapse
Omg so forgot you can use a mouse so going to do that now for no reason lol.

Darknites said:
Omg so forgot you can use a mouse so going to do that now for no reason lol.
Click to expand...
Click to collapse
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.

Goatshocker said:
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.
Click to expand...
Click to collapse
Cool think I have a play later.

Okay, here is what I got, the OTG cable is not working, that means the phone doesn't have Android 4.1.
The ShareKM application requires installation into the phone, meaning it is out of question too.
I am experimenting with this ADB in fastboot, but I am not really sure how that fastboot command works when I run ADB.exe trough command prompt and list devices, it show me only my other phone in USB debugging, when I run the fastboot.exe and type adb devices it says "waiting for the device", I do not really know how to work with this with a little guide, it shows me some commands there, i tried the one with rebooting into bootloader, but it still says only "waiting for device".
Could you give me a little guide perhaps link to guide what exactly I am supposed to do to run ADB in fastboot?
I am pretty technical type, dont need noobish explanation.
Thank you

Okay, I managed to get into fastboot, I always thought it is something with the fastboot.exe in SDK Platform-tools, well, anyway, I am inside, it says Fastboot USB, but adb still isnt showing the device in the list.
Also there is a big pink ***LOCKED***, that means that bootloader is locked I guess.
Any other ideas how I could backup the files? or any other suggestions?
Thank you

Moving slowly forward, I was being stupid and I was using the ADB command instead fastboot command, when I am in fastboot mode now, well, trough fastboot command now the PC recognizes the phone, altho what is the next step now?
Thanks again

Yeah, the ShareKM app was never really ment for you, it was more of a suggestion to dark sorry if it confused you.
I ran some quick tests, and yeah Im afraid adb is, in fact, not working in bootloader.
What happens if you boot into recovery? Maybe it works there?
What kind of things do you need to save? Is it just like pictures and stuff from the sdcard?
In that case, you could unlock the bootloader (this will wipe the device data, like applications etc) and install TWRP. Im 100% sure ADB works in TWRP without you needing to use the screen.

Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?

Sapphire18 said:
Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?
Click to expand...
Click to collapse
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.

Darknites said:
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.
Click to expand...
Click to collapse
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?

Sapphire18 said:
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?
Click to expand...
Click to collapse
Em did you try scan under select device?

Darknites said:
Em did you try scan under select device?
Click to expand...
Click to collapse
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.

Sapphire18 said:
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.
Click to expand...
Click to collapse
Then I'm out of ideas because unlocking the Bootloader will wipe the sd.

Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)

Goatshocker said:
Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)
Click to expand...
Click to collapse
And I am not throwing any blame either, I am just open to every solution
How would unlocking the bootloader help me? so I could put that TWRP inside and do some magic with it?
For the recovery part, I am not really sure how it is supposed to work, but every picture I googled shows some text
along with the exclamation mark, but the only thing I am getting is exclamation mark, and after a while the phone reboots.
I am guessing the recovery either wont load up, or something is wrong, should I try running ADB while that exclamation mark is shown?

[Q] Stock Nexus 5 Bootloop Trouble, Please Help

Hello Xda community, I open this thread after two days of reading and trying different ways to solve my problem.
My Nexus 5 runs Android 5.1.1 which I got OTA, I've never Rooted, installed any ROMS or done anything that might violate the system or the warranty.:angel:
Few days ago I downloaded some crappy program to my PC called Wondershare Dr.Fone (BURN IN HELL !!!) that was suppose to recover my deleted photoes from the Nexus, during the process of syncing etc.. it asked me to open developer settings and turn ON debugging mode.. which I did... and after about 30-40 minutes of "working" I realized it FROZE
The program didn't have any "Abort" button, and it was already late, so I just disconnected my Nexus, and after a moment it restarted and went into Bootloop
First I waited about an hour to realize it was infinite, then I tried going into Recovery Mode and deleting Cache Partition then restarting... it also didn't help, whenever I tried to turn it off, it was just turning on again, showing the Google Logo and then bashing those infinite Spinning Google Ballz in my face (I can turn off the phone using the Bootloader which works just fine, but it doesn't helps with the bootloop)...
The next whole day I was trying to at least recover my photos and videos, hoping that I can use the ADB to Pull the Camera folder out... I tried to install maaaany Google USB drivers following the steps of dozen tutorials, downloaded the SDK Manager and tried to install them thru Google server, and even Installed Naked Drivers with Windows 8.1 Signature Check Disabled... and tried it on 3 different PCs (win 8.1 and 7) the result was the same: Nexus 5 remained invisible until I Clicked in recovery mode "ADB Sideload.." in which case my Nexus 5 appeared in Device manager under Other Devices section (which let me install the drivers) otherwise it was invisible for my PCs...
The problem: whenever I was lunching the ADB from it's folder and typing "adb devices" I saw some sort of serial number, and "Sideload" next to it (while in other tutorials people have the word "Device" instead) and every command such as "adb usb" or "adb pull /sdcard/" or "adb pull /Camera/" result in "Error: closed" :crying:
In despair I tried to Factory reset my Nexus, and after about an hour of wiping, it allowed me to reboot which ended up in another infinite Bootloop....
I don't know what to do now, I don't live in the States and don't have warranty, I feel it's really unfair how after preserving my Nexus and it's Stock OS for so long... some Dr.fone bull**** broke it...
Please help me save my Nexus

Yea well... I knew nobody would give a crap in here... >.>

iJutsu said:
Yea well... I knew nobody would give a crap in here... >.>
Click to expand...
Click to collapse
[sarcasm]Way to stay positive.[/sarcasm]
You said you've tried doing a factory reset and that your system detects your device while in sideload mode on the stock recovery, correct? If so, have you at least tried sideloading the stock system update? Could be worth a shot at least.
Or with the driver issues, have you looked into opening device manager and see if it reads any kind of connection when hooked up not under sideload?

When adb is in sideload mode, you cant use any of the normal adb operations, like pull or push.

davehasninjas said:
You said you've tried doing a factory reset and that your system detects your device while in sideload mode on the stock recovery, correct? If so, have you at least tried sideloading the stock system update? Could be worth a shot at least.
Or with the driver issues, have you looked into opening device manager and see if it reads any kind of connection when hooked up not under sideload?
Click to expand...
Click to collapse
Factory reset didn't give any results, just destroyed any hope of recovering the photos I had onboard...
The system did detect my device for some time only when I activated the "ADB Sideload.." in the Recovery mode, but it wasn't same as in most guides and tutorials I've seen... When I typed the command "adb devices" it showed "4bd...serial.. Sideload", while according to tutorials it should be detected as "4bd.... Device"... Also I think the phone should get detected even without pushing the "Adb Sideload"... but the main problem is that every command results in "Error: Closed" so I can Pull or Push or Sideload anything since it's always same error"... which made me think perhaps the drivers aren't Okey, but I tried every Nexus 5/Google driver I could find, and I really doubt it's the drivers fault.
As I said the device remains invisible both in Device Manager and in Devices and Printers, until I click the Adb Sideload on the Nexus...
Factory Reset didn't work even tho I've never did any root or install Stock ROM or Kernel or anything of that sort, makes me wonder if that Dr.Fone crap app actually bricked my phone...
Thanks for trying to help

beekay201 said:
When adb is in sideload mode, you cant use any of the normal adb operations, like pull or push.
Click to expand...
Click to collapse
Aw... that's what I suspected... But activating the ADB sideload is the only way to make my Nexus 5 visible when I type "adb devices".... Does the fact that my PC can see it during ADB Sideload means that the Drivers are installed correctly? what may be the problem then? uff..

Have u tried this
Since you dont mind losing your data, I guess u already did a factory reset, I seriously suggest trying this guide. Read carefully. It worked perfectly for me which was in bootloop after 5.1.1 update.
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632

Unlocking and Rooting AT&T LG V10 H900?

Has anyone looked into the at&T variant yet? I'm having troubles getting into the bootloader and into stock recovery. I want to unlock so I can test whether anything for the h901 works with the h900 ( and eventually get on stock 6.0. This DPI is driving me nuts). I've tried all the button combos I've read and could think of, and adb reboot bootloader just reboots back into Android. I don't think AT&T is pulling what Verizon is, since I have the 'OEM unlock' option in dev options. So, there's gotta be some way to do it... Hopefully we can get this guy figured out

T get to stock recovery I used a trick we had to use for the OUYA. I send an "Alt+Sysrq+i" command with a keyboard via OTG, on boot at the LG logo. Holding "alt+sysrq" then tap "i" 5 or 6 times and it will load into recovery. I was hoping once there I could do something like "adb/fastboot reboot booloader". But couldnt get adb to see the device. I think there is some auto repair script that's running, hard to tell since there is no feedback on the screen other then the recovery icon. But after 3-4 minutes it reboots goes through the "app upgrade dialog".
For the EOM unlock option, I noticed that it never does actually check in the box after you select "enable". Maybe look at the log cat and see if we can find some app/process messing with it?
Haven't opened the thing up yet, but maybe see if we can throw some commands at it while its in recovery via UART pins with serial to usb (bus pirate)?

I have successfully booted into download mode but unfortunately ADB and Fastboot dont work. I did also manage to get into the factory reset screen with the hard buttons. I am backing up my phone right now and gonna see if maybe it'll take me to recovery instead of actually wiping the whole device. Maybe even check if ADB works on the screen I will share my findings once I've made sure it won't harm anyones device doing this.
I just realised I have a fresh install on laptop and my ADB might be the older version cause it was downloaded from synaptics manager. I'll be home later this evening and ill mess around with it. I am downloading android SDK tools for Linux right now so lets hope thats what it was.

sharky481232 said:
I have successfully booted into download mode but unfortunately ADB and Fastboot dont work. I did also manage to get into the factory reset screen with the hard buttons. I am backing up my phone right now and gonna see if maybe it'll take me to recovery instead of actually wiping the whole device. Maybe even check if ADB works on the screen I will share my findings once I've made sure it won't harm anyones device doing this.
I just realised I have a fresh install on laptop and my ADB might be the older version cause it was downloaded from synaptics manager. I'll be home later this evening and ill mess around with it. I am downloading android SDK tools for Linux right now so lets hope thats what it was.
Click to expand...
Click to collapse
How'd you manage to do that? I've tried a combination of buttons, but nothing.

RobertVanHagar said:
How'd you manage to do that? I've tried a combination of buttons, but nothing.
Click to expand...
Click to collapse
Download mode - power off device completely, hold down volume up and plug usb in to PC.
Factory Reset - power off device, hold down volume down, hold down power and let go of power button once LG logo comes on but hold volume down, it'll reboot twice I think and then take you to factory reset screen.

sharky481232 said:
Download mode - power off device completely, hold down volume up and plug usb in to PC.
Factory Reset - power off device, hold down volume down, hold down power and let go of power button once LG logo comes on but hold volume down, it'll reboot twice I think and then take you to factory reset screen.
Click to expand...
Click to collapse
Really hope you find the work around. Alot of people say at&t isnt going to allow rooting of new devices.......if theres a will theres a way!good luck

no updates?

I have this h900 but when looking for the 10f update, in the update center,it shows that im in the latest version, im in 10d and afaik there are some people with the 10f version that fixed the finger print scanner.. How to get this update?

betovanbuuren said:
I have this h900 but when looking for the 10f update, in the update center,it shows that im in the latest version, im in 10d and afaik there are some people with the 10f version that fixed the finger print scanner.. How to get this update?
Click to expand...
Click to collapse
I have the same problem with my AT&T H900. I'm on 90009e and wanted 90010f. AT&T Tech support couldn't get it to upgrade either which I find very odd. We really need some phone mastermind to unlock the secrets of the AT&T LG V10 H900. I'm unable to get it into download mode or unlock the boot loader either.
Thanks,
Silver

professorpoptart said:
T get to stock recovery I used a trick we had to use for the OUYA. I send an "Alt+Sysrq+i" command with a keyboard via OTG, on boot at the LG logo. Holding "alt+sysrq" then tap "i" 5 or 6 times and it will load into recovery. I was hoping once there I could do something like "adb/fastboot reboot booloader". But couldnt get adb to see the device. I think there is some auto repair script that's running, hard to tell since there is no feedback on the screen other then the recovery icon. But after 3-4 minutes it reboots goes through the "app upgrade dialog".
For the EOM unlock option, I noticed that it never does actually check in the box after you select "enable". Maybe look at the log cat and see if we can find some app/process messing with it?
Haven't opened the thing up yet, but maybe see if we can throw some commands at it while its in recovery via UART pins with serial to usb (bus pirate)?
Click to expand...
Click to collapse
Hmmm that's wiered because mine has stayed checked since I got the phone,although I don't t think it matters since it isn't unlocked. What's funny is i don't know why you can check it if bootloader is locked, I'm still lost on that one .

kotafoxx said:
Has anyone looked into the at&T variant yet? I'm having troubles getting into the bootloader and into stock recovery. I want to unlock so I can test whether anything for the h901 works with the h900 ( and eventually get on stock 6.0. This DPI is driving me nuts). I've tried all the button combos I've read and could think of, and adb reboot bootloader just reboots back into Android. I don't think AT&T is pulling what Verizon is, since I have the 'OEM unlock' option in dev options. So, there's gotta be some way to do it... Hopefully we can get this guy figured out
Click to expand...
Click to collapse
This has been asked and answered here

How to get into stock recovery
1) Enable USB dubugging
2) Plug phone into computer
3) Set USB connection type to MTP
-Now the "USB debugging connected" notification should appear.
4) Entering "sudo adb reboot recovery" into the terminal will reboot you into the stock recovery.
Note: Entering "sudo adb reboot bootloader" will only reboot your phone...
Using: at&t LG V10
Model Number: LG-H900
Android Version: 5.1.1
Build Number: LMY47V
Computer OS: Ubuntu 15.10

I was able to root an LG escape2 with this method. You can communicate and push files to your phone through the download mode without technically using adb. Any chance a method like this would work?
http://androidforums.com/threads/gui...2-2015.937446/

in case you are subscribed to this thread go here..... http://forum.xda-developers.com/att-lg-v10/general/root-lg-h900-real-tot-make-tungkick-t3336317/post65864734#post65864734

Yup, rooted on my Att V10 with xposed, adaway, flux, removed bloatware and titanium backup.
Worked pretty smooth as well.
Link to the thread on XDA
http://forum.xda-developers.com/att...e-tungkick-t3336317/post65870954#post65870954

jiggajatt said:
Yup, rooted on my Att V10 with xposed, adaway, flux, removed bloatware and titanium backup.
Worked pretty smooth as well.
Link to the thread on XDA
http://forum.xda-developers.com/att...e-tungkick-t3336317/post65870954#post65870954
Click to expand...
Click to collapse
Excuse me, what's flux?

manny18pr said:
Excuse me, what's flux?
Click to expand...
Click to collapse
http://techcrunch.com/2016/03/15/popular-blue-light-reducing-app-f-lux-arrives-on-android/

Galaxy amp 2 rootable?

Have done a little research trying to find any thing about an easy rooting for this device but no hits. I do know of some apps that can give root access haven't tried them but don't exactly trust them to much as have had them soft brick a few devices.
But any way here is device specs.
Carrier: cricket wireless
Phone name: Samsung Galaxy amp 2
Model number: Samsung-sm-j120az
Android version: 6.0.1
Baseband: J120AZTUU1APC4
if need any other info on it can supply it

I'm looking for the same thing. No roms no nothing.

@jasperjax Don't worry about it, there's not such thing as a flawless security system.
Universal rooting methods:
Warnings:
You are modifying your own phone on your own risk.
There is a slight chance that your phone may brick,
and if it does I will not be held responsible for whatever you do to your phone.
If you have a warranty, after rooting it will no longer be valid.
If your phone has a flash counter, some methods may trip it
resulting in a void warranty or a bricked phone (or both).
If your phone has KNOX, it may be tripped by some methods,
resulting in, once again, a void warranty.
If your phone is encrypted, the data partition
may be wiped for some methods.
There are more warnings specific to certain devices. Do your own research on your particular device model.
Click to expand...
Click to collapse
Computerless methods:
1. Framaroot
2. Towelroot
3. Kingroot for Android
4. Kingoroot for Android (Not recommended, but often works)
5. iRoot for Android
6. z4root
Methods requiring a computer:
1. iRoot
2. Root Master
3. Kingroot
3. Kingoroot (Not recommended)
4. CF-Auto-Root
Root Checker - Check if your device is correctly rooted
SuperSU - the recommended superuser application
ADB and fastboot drivers:
ADB and fastboot are (extremely simplified) a way for your computer to talk to your phone. And installing them may be a bit of a problem for some users.
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Recovery:
A custom recovery is an important part of device unlocking. It's the best and the most convenient way to fix your device if something goes wrong.
Root is required (in most cases) for installing the recovery.
The two most popular recoveries are:
1. Clockworkmod recovery (CWM) - CWM is a very stable recovery with many useful features. You can use the link here to download and install the official version via the ROM Manager app.
2. Team Win Recovery Project (TWRP) - TWRP is a stable recovery with a very nice UI and many features such as the terminal, partition management, file browser and so on. I personally use TWRP because of it's functionality, but if you're starting out CWM would be a better choice because of it's stability and compatibility. Also TWRP is a tiny bit more difficult to install as there is no one click installer.
If your device is not officially supported you can get an unofficial version, however there is no grantee the unofficial version will work, it might even forever break your device. In most cases it does work, just look at what other people who tested it say.
To find unofficial recoveries Google:
[your phone model] cwm recovery
or
[your phone model] twrp recovery
After installing the recovery the first thing you should do it do a nandroid backup.
If you have any questions first try to Google the answer, but if you can't find it feel free to ask me here with a post (not a PM).
Also remember to quote me or tag me with @janekmuric if you want me to respond.

most of those do not work for 6.0 correct? Amp2 comes with 6.0 stock

Has anyone heard anything more about rooting the Cricket Galaxy amp 2?
Just bought it yesterday for a friend and would love to root and possibly unlock it?

i have tried all the computer less ways of trying for root. none have worked. haven't done much with the ones requiring computer to root But does not mean i wont try them at some point. right now this is mostly a Backup phone Just in case i kill my Galaxy s4 (running goldeneye lollipop 5.0.1 rom) other then that have not seen anything New pop up around the net about it still on my todo list tho

2nd update to this. have tryed iroot root master and kingroot pc version best i get is blacked out screen with phone not responding to anything. Almost like a hard brick. pull battery hold power for a few put battery back in then kicks on just fine like nothing happened. but saddly no root havnt tried CF-Autoroot as to well phone not being listed. much less figuring out how to unlock bootloader. (If its even Able to be unlocked)
Tho i have noticed something in dev options. a switch to allow for OEM Unlocking. yet booting into recovery and doing the good old "fastboot oem unlock" just gives me the waiting for device that sits there for the next hour. any takes on this @janekmuric ?

jasperjax said:
2nd update to this. have tryed iroot root master and kingroot pc version best i get is blacked out screen with phone not responding to anything. Almost like a hard brick. pull battery hold power for a few put battery back in then kicks on just fine like nothing happened. but saddly no root havnt tried CF-Autoroot as to well phone not being listed. much less figuring out how to unlock bootloader. (If its even Able to be unlocked)
Tho i have noticed something in dev options. a switch to allow for OEM Unlocking. yet booting into recovery and doing the good old "fastboot oem unlock" just gives me the waiting for device that sits there for the next hour. any takes on this @janekmuric ?
Click to expand...
Click to collapse
Sorry for not posting for 20 days. I've been of xda for a while. Anyways the reason why it's stuck there is because you are trying to run fastboot commands in recovery. You are supposed to run them in fastboot mode.
Just Google "[phone name] how to enter fastboot mode" or try pressing random buttons to boot the phone into fastboot. From there you should be able to run "fastboot oem unlock" (This will erase ALL data).
If it still doesn't work even if you are in fastboot mode then you have incorrectly installed fastboot drivers on your PC. Google is your best friend here.

janekmuric said:
Sorry for not posting for 20 days. I've been of xda for a while. Anyways the reason why it's stuck there is because you are trying to run fastboot commands in recovery. You are supposed to run them in fastboot mode.
Just Google "[phone name] how to enter fastboot mode" or try pressing random buttons to boot the phone into fastboot. From there you should be able to run "fastboot oem unlock" (This will erase ALL data).
If it still doesn't work even if you are in fastboot mode then you have incorrectly installed fastboot drivers on your PC. Google is your best friend here.
Click to expand...
Click to collapse
your fine this has been a slow moving project for me anyway. and yes i know about running fastboot in fastboot mode BUT heres my issue. i have download mode or recovery. thats about it. attempted this in download mode also for giggles and got same thing expected that honestly but worth a shot. from adb have tryed "adb reboot fastboot , adb reboot bootloader" and a few others just to get close to anything that would give me a different screen. as for key combo's nothing has worked. tryed with normal shutoff and turn on and with taking battery out holding power then popping battery back in with no luck. as for googling how to get into fastboot just some info that covers "Most" devices still not a whole lot about this device on how to root it much less anything more. heck half my searching brings up this forum thread as the top item. so this really has me stumped.

jasperjax said:
your fine this has been a slow moving project for me anyway. and yes i know about running fastboot in fastboot mode BUT heres my issue. i have download mode or recovery. thats about it. attempted this in download mode also for giggles and got same thing expected that honestly but worth a shot. from adb have tryed "adb reboot fastboot , adb reboot bootloader" and a few others just to get close to anything that would give me a different screen. as for key combo's nothing has worked. tryed with normal shutoff and turn on and with taking battery out holding power then popping battery back in with no luck. as for googling how to get into fastboot just some info that covers "Most" devices still not a whole lot about this device on how to root it much less anything more. heck half my searching brings up this forum thread as the top item. so this really has me stumped.
Click to expand...
Click to collapse
If your device doesn't have fastboot mode there is no point in trying to do anything with it. Anyways try downloading Poot and rooting with that. It's just an app that you install on your phone. I've tried it on my phones, it never worked, but a lot of people on the internet are saying it worked for them so you should try it.

janekmuric said:
If your device doesn't have fastboot mode there is no point in trying to do anything with it. Anyways try downloading Poot and rooting with that. It's just an app that you install on your phone. I've tried it on my phones, it never worked, but a lot of people on the internet are saying it worked for them so you should try it.
Click to expand...
Click to collapse
yeah poot has never worked for me on any device so far. always get (Ministro can not satisfy your application depedencies) error. just as this time around. but as i have located an "updated" rom for this device (and as i forgot to turn off device last night it took on the update on its own anyway Yay me) i may just try doing some light flashing. with odin at the ready just to be safe.

Anyone figure this out? I have a cricket samsung galaxy amp 2 (SM-J120AZ). I've tried every way possible to root it with no luck. I've tried all the methods above and none of them work for the amp 2.

@imagetrekker Not yet. another device very close to this one is the SM-J120A (Samsung Galaxy Express 3) everything matchs up besides the android version is comes with.(6.0) would think if they root that one this one would be able to be rooted same way or if this one gets rooted first should work on other.

Anyone figure out how to root this phone yet? I have never had a device that can't be rooted one way or another but this one is being really tricky...

I'd like to bump this too! I've tried many methods with no success. Any other options to try?

Bump

Where did you find that SM-J120AZ ROM ?
jasperjax said:
yeah poot has never worked for me on any device so far. always get (Ministro can not satisfy your application depedencies) error. just as this time around. but as i have located an "updated" rom for this device (and as i forgot to turn off device last night it took on the update on its own anyway Yay me) i may just try doing some light flashing. with odin at the ready just to be safe.
Click to expand...
Click to collapse
Hey man, this is very very important. You said you located an updated ROM for the Samsung Galaxy Amp 2 (SM-J120AZ Cricket). I've been searching high and low, so if you could direct me to where you found it, I would so very much appreciate it.

Can't format SD card for internal use
So I guess Samsung have saw fit to disable the ability to format an SD card for internal storage, which means you can't move any apps to the SD card. With the limited memory on this Galaxy Amp2 this makes it near useless!
We need to get root on this so maybe we can fix this...
adb shell sm set-force-adoptable true
Should fix it, but only with root...

sorry had some computer issues shortly after a thunderstorm but im back up and running so Sorry for the very late replys
MuzicSoulWorldly said:
Hey man, this is very very important. You said you located an updated ROM for the Samsung Galaxy Amp 2 (SM-J120AZ Cricket). I've been searching high and low, so if you could direct me to where you found it, I would so very much appreciate it.
Click to expand...
Click to collapse
@MuzicSoulWorldly was actualy able to get it from http://updato.com/firmware-archive-select-model?r=&v=&q=j120az&exact=1
Greywire said:
So I guess Samsung have saw fit to disable the ability to format an SD card for internal storage, which means you can't move any apps to the SD card. With the limited memory on this Galaxy Amp2 this makes it near useless!
We need to get root on this so maybe we can fix this...
adb shell sm set-force-adoptable true
Should fix it, but only with root...
Click to expand...
Click to collapse
@Greywire Not quite you can do it with out root. commands are as this
Code:
adb shell
sm list-disks
sm partition <DISK> private
reboot
<DISK> needs to be replaced with the output of the previous command. For example sm partition disk:179,64 private. That will format the entire SD card and adopt it. Another way would be to use sm partition <DISK> mixed <VALUE> replace <DISK> same as with other way but value would be in a % of disk you want adopted example "sm partition disk:179,64 mixed 50" would make adopt half your sd card.

thanks..
I actually discovered this right after I posted. Hopefully anybody else having this issue will see your posting though for the solution.
Still would be nice to get root on this phone. Any ideas on how to carrier unlock it?

[Completed] AppTab Dual talk - Bootloader problems

Hello,
My friend gave me his locked out phone AppTab Dual talk...( a company name unheard of) and asked me to unlock it for him. He doesn't know his account password. Now I tried booting into recovery or anything. I held power and vol down. Some stuff in Chinese came up. Image attached.
And language barrier apart, only vol down and up buttons work in that to scroll through the options . I've tried everything to try and select an option in that. But no luck!
If I hold down vol up and power buttons, something like a broken Android logo screen comes up which I believe is recovery mode for this device.
Then I plugged it on to my PC and installed the adb drivers for it.
adb devices --> I can see the device listed
Fastboot devices --> I can't see the device
adb reboot bootloader --> the stupid phone just reboots into actual rom instead of bootloader.
I tried to see if the bootloader is locked..now how do I unlock it? fastboot OEM unlock? Damn thing doesn't get recognised in fastboot.
I thought I'll enable USB debugging..which I believe isnt enabled.
So I searched online and came across this command.
adb pull /data/property/persist.sys.usb.config ~/
But the out put of this is either "error: no device" or "permission denied"
I don't know what to do. Here it doesn't go into bootloader. If I want to flash a custom recovery, fastboot commands ain't working, if fastboot shud work I shud enable USB debugging some how, and that too isn't working. If I hold down some random buttons also there is no bootloader mode or anything.
And the options which it gives and which I believe will have the factory reset option also doesn't work bcoz I can't select any option in that.
And yeah...I tried one more thing
adb shell recovery --wipe_data
Which also dint work
I tried
adb shell
Wipe /data
Wipe /system
Wipe /all
I also tried to side load one zip package which could disable the pattern lock
Bt that also dint work.
I tried adb USB and then adb side load <file>
Still no luck.
I might just recommend my friend to throw this phone into the water!
Thanks in advance

I've never heard of that device either and I couldn't find much information here. The adb commands that you tried won't work unless the phone's rooted. You can't access /system or /data or any other nested folders hence the "permission denied." It also looks like the bootloader isn't unlockable since adb reboot bootloader doesn't work. If you just need to unlock the phone you can check this thread but you need to have usb debugging enabled.

Art Vanderlay said:
I've never heard of that device either and I couldn't find much information here. The adb commands that you tried won't work unless the phone's rooted. You can't access /system or /data or any other nested folders hence the "permission denied." It also looks like the bootloader isn't unlockable since adb reboot bootloader doesn't work. If you just need to unlock the phone you can check this thread but you need to have usb debugging enabled.
Click to expand...
Click to collapse
Well, that still keeps me in the loop. I have to enable usb debugging & if i have to do that i have to root & so on.
Thanks for the reply. No luck with the thread you linked either.