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.
Related
I've got an Iconia tablet with a broken recovery (I've been using CWM and Thor's ICS ROM). I'm going to follow the steps outlined here
http://forum.xda-developers.com/showthread.php?t=1129873
but.... when I look up the UID from every method, all I get is 0123456789ABCDEF.
Given all the dire warnings about not being able to recover if/when things go wrong without the real UID... this 123 UID isn't the real UID.... is it safe to proceed with the repair here? Or are things really messed up?
I have not messed with ICS myself, but my understanding from reading the ICS threads in the Iconia forums is that the device is no longer using the uid for usb serial number. So it seems you can't get it that way if you have installed any of the ICS updates.
The suggestion I have seen is to look for androidboot.serialno in dmesg directly after booting, but that does not seem to help everyone.
Another option might be to get the device into APX mode and do a usb bulk read, the first read should return 8 bytes that is the UID. I would assume this to still work even after you have installed ICS but I have not tried. I pasted some code for opening the device, reading and printing the uid (using libusb, tested on Linux) on the Iconia forum earlier this week.
Hmm OK that's helpful info. Thanks.
I tried the androidboot.serialno in dmesg, but I wasn't able to find the string.... I will try that again after a clean boot.
I've been doing all the debugging from my one Windows machine... I haven't tried plugging it into my Linux PC yet... that's next... I haven't discovered APX mode yet. Time to do some more reading, thanks for the pointers.
Edit 1: OK checked lsusb -v and I serial also shows 0123456789ABCDEF
Edit 2: Clean boot and did a new dmesg dump.. parsed the output and no sign of androidboot.serialno or anything that even resembles it.
OK, things are not getting better here. I've been tinkering a lot, and in some respect I've just made things worse.
I still cannot find the UID with any of the documented methods here on XDA. I've tried
using adb devices
using Linux lsusb -v
checking the output of dmesg for androidboot.serialno
plugging in to Windows and looking at the USB mount info using USBDeview
looking at the device manager in Windows and checking the "Parent" field
I have also booted into APX mode and to discover the UID that way too... and nothing.
All I get is 0123456789ABCDEF
At this point the frustration level was getting high enough for me to be a bit reckless... I copied "itsmagic" into /data made it executable and ran it. No errors.
I rebooted into Recovery mode, and there I get scrambled graphics on the screen (it's the Acer logo duplicated several times with loads of tearing and distortion) and the tablet vibrates constantly.. non stop until I reboot it.
I can boot normally into the current ROM (Thor2002ro v96) so I haven't busted it completely. If I try to use my existing CWM manager to install any other ROM or use the manager to reboot into recovery mode, it goes back to the scrambled screen and vibrating constantly.
Does anyone have any ideas or suggestions here? I'd be happy to even roll back to stock and start fresh. There is nothing on the tablet that needs to be saved... except the functionality of the tablet itself.
When you write nothing about APX mode, does that mean literary nothing or nothing different?
If you have root you can see if you have anything interesting in /proc/cmdline.
If not I'm out of ideas on how the get the UID for now.
While i very much doubt 0x0123456789ABCDEF is the UID used to generate the SBK of the device you could try reading and decrypting the beginning of mmcblk0 using the SBK that would give (0xA9EA7E00 0xF12BEB06 0x3AD20804 0x364A5F03) to verify this.
You could probably overwrite the restore partition from your running system, I have never done that myself though.
OK, it's SOLVED.
After much swearing and crying and a little help from the forum here and in other posts the solution to fixing the broken tablet was actually quite easy.
Based on the information here:
http://forum.xda-developers.com/showthread.php?t=1459821
- I downloaded recovery-ra-iconia-3.16-gnm.img using teh links provided on the thread above
- I ran itsmagic
- Then I did these steps:
Code:
adb push recovery-ra-iconia-3.16-gnm.img /mnt/sdcard
adb shell
su
dd if=/mnt/sdcard/recovery-ra-iconia-3.16-gnm.img of=/dev/block/mmcblk0p1
sync
reboot recovery
This booted a working recovery mode (FINALLY), and I was able to successfully flash the latest Thor2002ro ICS ROM.
Thanks for your help and suggestions eppeP, they got me thinking in the right direction.
Hello guys I am trying to bypass screen lock via adb but when I write adb devices it shows "0123456789ABCDEF Device" and then when I type adb shell then it shows"$" after that whatever I type it shows permission denied(even if I write adb).Please Help
please clear up Google
account lock
whats up guyz im new/old to this forums new/old means , i dont get online to much
well i have been tweaking a little bit with my droid DNA and found out some work around for some problems people might be having trying to unlock their bootloaders
the first problem i encountered was the adb killing process , adb is out of date . there is a little work around for this , that worked with me and my friend s DNAs to resolve this we just killed the adb daemon with this command
adb kill-server
then we started the server with the command
adb start-server
allright . the only way you will not get that error of adb out of date is , if you see adb starting on some port . i forgot the port number, but thats the only way you will not be getting the error ..
the second problem i encountered in the process of unlocking my phone was the restore update not finishing , which was caused by the bug of adb out of date error. once you resolve the problem with the adb bug out of date error , then you will be able to restore the phone successfully
but hold on , there is another problem some people might be getting , when you execute the command " adb restore backup.ab " if your device is taking to long to finish the restore and the window is behind looping, dont worry about it just wait couple of minutes control -c on the window looping and control -c on the window that you waiting on the restore to finish ... i tried that couple of times then i figure that the restore did go thru ..
some people might be getting an error with this command "adb shell mv /data/DxDrm /data/DxDrm_org" if you getting the error that says failed to blah blah blah permission denied , the cause for of that error is that the restore didnt go thru . if you got that error you can reboot safely , your device is not bricked yet lolz ..
when you get to the section that you have to repeat the exploit again , you gonna start getting the error again with the adb killing the process out of date thingy , dont worry just redo the work around i posted above , i control c the restore window and the loop window
couple of times just to make sure it was working fine , and it did . it was working fine
sorry for my english guys . i just wanted to point out those little flaws in the process of unlocking the bootloader , just in case some people get the same errors , they wont have to break their heads with it ... blessed be ..
Minor audible...
I was using the video made by DroidModderX and was able to get through it basically step by step with one minor hiccup. One the step where you start the first command prompt to do that "loop of errors" and move to the second command prompt, my system had an error doing this until I unplugged the phone and plugged in again. That wasn't mentioned in the tutorial but worked great once I did that part. It seemed like ADB got a little screwed up or something but, once I unplugged/ replugged it all worked normally. One other thing I noticed was that in the video (he uses a mac) the first command prompt continues to "loop" until you hit CRTL + C and on mine as soon as did the command in "prompt 2" the loop stopped on its own although all of the commands still worked as planned. I was doing this on Windows7 32bit. Hopefully that makes sense or is helpful to someone...
all you had to do was kill, then restart adb? that's not doing the trick for me, damn
EDIT: I got mine to work by uninstalling HTC Sync, it has an adb.exe file that was causing the error
I was able to leave HTC Sync installed but I had to uninstall Droid Explorer from my Incredible days. Only then did the ADB out of date error stop.
I used this before with HTC Sync. Maybe that is why I was able to keep it installed.
The attached zip is from http://visualgdb.com/adbfix/
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.
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.
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