the handset is samsung galaxy grand neo I9060. I rooted with kingoroot and it was sucessful. Checking with root checker apps also gives green signal. But i could not get any response for su in linux command mode . Moreover opening the linux, i forgot the actual word, or app, i do not get hash # simple to show it as rooted but a dollar $ sign to show it not as rooted. What is the actual stage?
I want to delete the batterystats.bin to find the cause or to fix the problem of depleing battery after 40 percent. I tried so much things.
how to access the said file, so that i actually manually delete it to see its deletion.
Regarding the battery problem, try if a new battery works for you.
If it fixes the problem, well good job.
If it doesn't the problem is somewhere else and you got 2 batteries now.
If the battery isn't replaceable then you're screwed
Sent from my Samsung Galaxy S7 using XDA Labs
Did you run the command adb devices ? If the daemon doesn't start after you do that, adb isn't working. If you get the serial, or model number, adb is working. I try to find the official way to root, instead of using kingoroot, I don't know if the apps changed, but when I used it, you have to re-enable it every time you reboot. It might not work with adb, since when you reboot, root's gone, and you have to re-enable through the phone being on.
Related
So I've been trying to root my thunderbolt for about a week with no success.
At first I used the method here: http://forum.xda-developers.com/showthread.php?t=1005292
It has continually failed on step 2, tried on different computer also. No luck.
I gave up on rooting it for a few days/
Since the first step went through I am downgraded, running 1.03.605. It's got quite a few bugs and when I try to software update from the phone nothing is found. All I really wanted was to get it to the current firmware to fix connectivity bugs but after searching high and low I still have no idea how to/if it is possible.
I assumed I may have to just root it at this point, so I gave the manual root on theMikMik a shot. While setting up my ABD everything runs smooth until I try to enter commands into abd. I get permissions denied, every time. I've tried looking for an answer to this with no luck. Guide I used found here: http://www.themikmik.com/forums/viewtopic.php?f=66&t=256
So my main question, is there any way to get the latest firmware onto my phone without rooting? I've tried downloading an update, naming it update.zip then updating from bootloader with no luck.
If not, what the hell am I doing wrong that is denying me permission in ABD. I've turned anti-virus off, rebooted etc.
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Edit:
While that may should work, I believe you could start from the beginning with Step 1 using the link I just posted as well. Just don't flash the old firmware (1.0.3.605 that you currently have) after you go through that for any reason (see: http://forum.xda-developers.com/showthread.php?t=1008824).
Absolute_Zero said:
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Click to expand...
Click to collapse
*Facepalm*
So I tried what you said from that guide, step 5 failed for me. So I tried from the beginning...still failed.
So, I decided to record it and hopefully you can tell me what I'm doing wrong.
Link: http://www.youtube.com/watch?v=o2AFZEIVIio
Figured that'd be a better way to get the help I need with less reading on your part.
Sorry, I was commuting home from work.
According to the output of "adb shell" you're either already rooted or psneuter has already been run since boot. (note the "#" output instead of "$").
There's no reason to run psneuter to gain permroot again. So once you see that pound sign, start from a two steps down where it says "/data/local/busybox md5sum /data/local/misc.img". IOW, skip that particular "/data/local/psneuter" step.
And I would highly recommend that if you are going to copy/paste, only copy one line at a time to prevent errors.
Off to grab dinner. I'll check back later when I can but hopefully you will be good from here on out.
Edit:
I'm perfectly happy with walking you through it (and I believe you should be fine after this post anyway) but if you still wanted to use that easyroot method that you started with you might want to read this if you haven't http://bit.ly/qsvOkN. I didn't use that easyroot method but it looks like if a step fails, people just run it again until it works. /shrug
I like adb and people should know how to use it anyway.
Hello guys, first i hope it's in the right place to post this and second sorry for my english.
And also thx for many tips i got from here on my road to get this working. But now i don't know what to do.
(Win 7 Starter 32bit, Android Debug Bridge version 1.0.31)
My situation: had a S3 (I9300) with Android 4.3 and a broken screen. Touch is still working. The broken screen wasn't a problem at first, because as it fell down, the screen was all right. After about 15 min it started to get black at the top. But most of the screen was ok. After the night everything was black.
So i read about droidatscreen and started to root and play with the device. First i put CF-Root-SGS3-v6.4 with Odin on the phone and then started to try to make adb work under Android.
I was in recovery and add this line to the build.prop "persist.service.adb.enable=1" .
I'm not sure, but i think after a reboot of the phone i had adb running under Android. At this time adb said not authorized and the window with the confirmation for usb debugging wasn't popping out (because i tried and tried to touch at the place where it shold be).
Than i read about "persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb" adding to default and build.prop , also didn't work.
Than i added "ro.adb.secure=0" and changed "ro.adb.qemud=1" to 0 in both files, and after rebooting the phone i hit the place on the screen and adb devices went from unauthorized to device. I finally made it and could use droidatscreen. (i don't think that ro.adb.secure=0 deactivated the rsa fingerprint, but i think it got it to pop up the confirmation window).
Now i was able to see the menue, i changed some things in options, like touch sound and screen unlock sound to be able to hear the things i couldn't see, i also changed the setting for showing touches in the dev menue.
And now the bad thing happened, i touched the option usb debugging (not on the check, but on the word itself (i could see it because of the latency of droidatscreen and the phone rebooted and wasn't able to connect to adb).
Now i only get the mtp device and adb devices shows nothing but a blank line.
I'm still able to change build.prop and other data in recovery but even load the original files to the phone and going step by step further didn't bring me the unauthorized message in adb devices.
I hope someone could help me. Maybe someone knows the files which are changed during changing the options in Android menue.
Btw. i already wiped cache, but do not want to do more than this (i mean wiping ).
Thx
Edit:
Solved the problem.
Found out about the getprop and setprop commands and used getprop in adb shell. Didn't found anything like "persist.service.adb.enable" ... , only something like
[service.adb.root]: [1] [ro.adb.qemud]: [1] and [persist.sys.usb.config]: [mtp] .
Searched in /data/property for adb things, and saw "persist.service.adb.enable" "persist.sys.usb.config" .
"getprop persist.service.adb.enable" showed a blank line, so i "setprop persist.service.adb.enable 1",
now "getprop persist.service.adb.enable" showed a 1 and after rebooting phone, i was able to get a unauthorized message from adb devices, and reconneting the usb let the confirmation popup.
Thx anyways.
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
M1kesky said:
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
Click to expand...
Click to collapse
Is demo mode enabled in the system UI tuner under settings?
I would suggest flashing the latest factory images in fastboot.
cam30era said:
I would suggest flashing the latest factory images in fastboot.
Click to expand...
Click to collapse
Would be a great idea, except I'm not sure you can get into Developer Options to enable Allow OEM Unlock while in Demo Mode, which would make unlocking the bootloader (which has to be done before fastboot can function properly) quite difficult.
borxnx said:
Would be a great idea, except I'm not sure you can get into Developer Options to enable Allow OEM Unlock while in Demo Mode, which would make unlocking the bootloader (which has to be done before fastboot can function properly) quite difficult.
Click to expand...
Click to collapse
You're right, in that I'm not sure either (about enabling Developer Options). But it's worth a try.
M1kesky said:
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
Click to expand...
Click to collapse
This ADB command should do the trick:
Code:
adb shell am broadcast -a com.android.systemui.demo -e command exit
Edit:
In case that sounded overwhelming and/or to help others with this issue, here's more more info about how to do that.
You must first install the ADB drivers to your PC. I suggest using Minimal ADB rather than installing the entire Android SDK, then use Command Prompt to navigate to your ADB directory (the folder where your ADB application is installed. Use the cd command to change directories [get it, cd?] to the complete filepath to the folder containing your ADB program in Windows. I put my Minimal ADB folder that I extracted from the zip directly onto the C:\ drive so the filepath is "C:\adb". I open my command prompt and type "cd C:\adb" and it's ready to roll. Super easy), once it says C:\adb> or whatever your filepath is, copy the command code above exactly into the prompt and press Enter.
To ensure your device is properly connected, after using "cd C:\adb" to get to your ADB application, run the command "adb devices". The daemon will start and it will either list your device number if it's successfully connected or will remain blank and go back to the "C:\adb>" prompt if it's not connected properly.
There may be a notification on the device when you try to connect ADB, but i may be getting this confused with ADB Debugging. If you see a notification pop up with warnings or aging your precision to connect to your PC just click the "chill out bro it's cool, I got this" button.
I hope you get it up and running properly and can enjoy your Nexus 9!
Sent from my XT1575 using Tapatalk
Thanks guys, I'm in work tomorrow so i'll take my laptop in and give it a try, thanks for all these suggestions!
I'll tell you the results afterwards.
Hi, I am trying to unlock a Galaxy J1 Ace SM-J111F/DS for my colleague. The phone belonged to his younger brother who had passed away in an accident, now that he's gone, we have no information as to now to unlock his phone.
I have tried researching and searching around for methods but to no avail. I was hoping maybe someone here could provide some assistance
A factory reset is out of the question as he needed to access information stored inside the phone
Some device details:
Device is locked by a pattern lock
Unable to unlock via Google account(No one in his family knows his account name/password)
Phone is not Rooted
Phone is FRP Locked
Things I have wanted to try and done so far:
Intended to flash a bypass to unlock the lock screen
Attempted to flash a custom recovery in order to flash the bypass, however FRP is locked and it does not allow a custom recovery to be flashed
Attempted various methods of "security exploits" to unlock, but appears to be patched on current firmware
Tried to search methods of unlocking FRP, however all the methods I've seen so far requires access to developers option, or requires a flash of stock firmware.
Tried accessing device via ADB, however it does not work as USB debugging is not enabled
I'm currently out of options trying to do this by myself, we would really appreciate it if someone could help us out in this
If powered on, and plugged in to PC, is it 'seen' at all?
robneymcplum said:
If powered on, and plugged in to PC, is it 'seen' at all?
Click to expand...
Click to collapse
Yes, it is "seen", but I can't do anything else to it
If it is seen, there is a chance you can get data off it.
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Chilli71 said:
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Click to expand...
Click to collapse
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
XenoJin said:
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
Click to expand...
Click to collapse
Ill jump in this one to. im in a similar situation. I have a lg g vista that no conventional method is working to bypass frp. Device is not encrypted. My prob is. I believe if i can downgrade back to stock kk which the phone was released with it didnt hve frp then so bam im in. But lgflash tool wont downgrade. Always errors. Loads of diffrent settings have been made. Also followed guides to a t.
But in ure case to if it is possible to dlmode and odin back to kk or earlier u should the be able to skil the google login totally. I dont know if ure device came with kk from factory or lolipop. Frp was implemented in loli so kk should be good. Maybe
Two comments:
1) I have a Huawei G8 in front of me. I worked all weekend with it with bootloader/fastboot. I wanted to test the lock screen/adb behavior, But to my surprise ADB does not find it w/ and w/o lockscreen. --> There are different possibilities why the phone does not show up (it worked in the past with this phone/notebook, but quit working). Before you flash make sure that your setup is working (best with an identical mobile). It seems that USB connection can behave different in Bootloader/Recover/Android OS mode.
2) I made a dirty flash (w/o erasing flash) of Lollipop over Marschmallow last weekend. The result was that many directories including SDCard0 where not accessible. Also user data was not accessible. And you have always the chance that you mess something up when flashing and you loose the content.
If the data is really important your friend could pay a data rescue company (if you don't loose your face). I'm pretty sure that programs exist that can be loaded into RAM with bootloader (fastboot boot) that provide an interface to the PC (in the easiest case, adb again).
Chilli
This thread for question and answer. Reserved.
Hey I need your help. I have edited /fstab.qcom file(backup fastab.qcom.bak). I can start TWRP but I don't where the "root" partition is?
/-
|- /system is patirtion
|- /data is patirtion
But where is / itself
I tried restoring boot partition from dd IMG that I had, but it didn't help. Help me please. It's urgent. My phone was only phone. This is my only phone.
Someone tell me where are / or root are stored
ro.build.id=LMY47V
ro.build.version.security_patch=2017-07-01
ro.product.name=Alcatel_4060A
def.tctfw.brandMode.name=Alcatel IDEAL
def.tctfw.build.number=M7UUAU1
ro.product.pcsuite=Alcatel IDEAL
Does this version support VoLTE Video call?
Has anyone realise sudden changes in brightness to 100% while using ?
Well I happens with my phone. Sometime at night when I set brightness to minimum and using my phone the brightness increases. To set to minimum I change the valve by sliding then back to minimum.
Are you guys are suffering from this problem or its just me.
Does this phone support usb otg?
Why my contact app is showing nickname, how can I disable this, I tried installing google contact, but no success, looks like problem of OS not contact app.
kdm6389 said:
Has anyone realise sudden changes in brightness to 100% while using ?
Well I happens with my phone. Sometime at night when I set brightness to minimum and using my phone the brightness increases. To set to minimum I change the valve by sliding then back to minimum.
Are you guys are suffering from this problem or its just me.
Click to expand...
Click to collapse
Fixed by M7UUAU1 ROM
@Chupi383 I want to draw your lillte attantion for once to post number #3, #5, #6. These are not serious issue. just i want to know if u have suffered these problem, maybe you have fix to share with us.
The root partition on Android is always in the initrd in the boot partition.
I see no option for video call of any sort on any firmware for this phone. It is designed for US use, and video call isn't a standard feature here.
No, USB OTG is not supported. The software stack for it is present, so some USB OTG detector apps will tell you it's supported, but the hardware for it is not there. I plugged in a few devices with USB OTG adapters that work on my Galaxy S7 Edge and nothing happens -- no power to the device, nothing detected on the phone. Even using a tee adapter that lets me power both the device and phone USB port, the phone doesn't enumerate or detect the device.
I have been using Google's contacts app successfully and it works well. I haven't tried assigning a "nickname" to a contact. It just shows their first and last name as I've entered them.
Brightness does randomly change to 100% on some firmware versions. Best I can tell, it only happens with USB debugging enabled, or possibly only after connecting to the phone on adb. Disable USB debugging and reboot after you're done hacking and it shouldn't do that anymore.
Alcatel 4060a I rooted device using kingoroot or king root with purify already with it, I obtained root ,used phone. I removed system apps n bloatware. Ok then I wanted to give my phone away airgo I took back root access, n went n removed all my Google account s then went into phone settings, and reset it. Well erased n Reeset. As soon as I hit the reset button. It went to black then Alcatel powered by Android screen. Now is stuck can't get it to boot to anything. My computer recognizes but when I run adb command window says no connected devices. Help me please like step by step instructions please
ashluvsgary420 said:
Alcatel 4060a I rooted device using kingoroot or king root with purify already with it, I obtained root ,used phone. I removed system apps n bloatware. Ok then I wanted to give my phone away airgo I took back root access, n went n removed all my Google account s then went into phone settings, and reset it. Well erased n Reeset. As soon as I hit the reset button. It went to black then Alcatel powered by Android screen. Now is stuck can't get it to boot to anything. My computer recognizes but when I run adb command window says no connected devices. Help me please like step by step instructions please
Click to expand...
Click to collapse
adb dont work on reseted phone, to anable you have to go setting > developer mode > USB debugging.
or wait for 30min to start phone since it take little time after reset
or you have bricked your alcatel
try using
Code:
$ [B]fastboot -i 0x1bbb devices[/B]
ashluvsgary420 said:
Alcatel 4060a I rooted device using kingoroot or king root with purify already with it, I obtained root ,used phone. I removed system apps n bloatware. Ok then I wanted to give my phone away airgo I took back root access, n went n removed all my Google account s then went into phone settings, and reset it. Well erased n Reeset. As soon as I hit the reset button. It went to black then Alcatel powered by Android screen. Now is stuck can't get it to boot to anything. My computer recognizes but when I run adb command window says no connected devices. Help me please like step by step instructions please
Click to expand...
Click to collapse
Go to through https://forum.xda-developers.com/android/general/super-guide-alcatel-one-touch-4060a-t3621525 to unbrick