ok so I installed custom framework-res.apk but stupid me I renamed the original one with root-explorer and then suprise suprise my system crashed as there was no framework-res.apk present
anyways now I'm stuck at the samsung galaxy s2 boot screen with the yellow triangle on it as I have rooted my phone.
Now the next problem is, I tested to de-activate USB debugging to see if it had an effect on my battery life but now obviously I cant access adb without usb debugging and im stuck at bootscreen...
what can I do? can anybody help me I'm lost!!!
Locster126 said:
ok so I installed custom framework-res.apk but stupid me I renamed the original one with root-explorer and then suprise suprise my system crashed as there was no framework-res.apk present
anyways now I'm stuck at the samsung galaxy s2 boot screen with the yellow triangle on it as I have rooted my phone.
Now the next problem is, I tested to de-activate USB debugging to see if it had an effect on my battery life but now obviously I cant access adb without usb debugging and im stuck at bootscreen...
what can I do? can anybody help me I'm lost!!!
Click to expand...
Click to collapse
Did you try accessing adb while in recovery?
If I type adb devices it says list of devices and its empty..i thought its because I disabled usb-debugging...???
EDIT:
ok tried now and it worked...strange..ok happy anyways...
Locster126 said:
If I type adb devices it says list of devices and its empty..i thought its because I disabled usb-debugging...???
EDIT:
ok tried now and it worked...strange..ok happy anyways...
Click to expand...
Click to collapse
Glad it worked
I have the same problem as I renamed the framework-res.apk file and now stuck on boot screen...
How can I activate the USB debugging mode now if I cant access the settings tab in the GUI?
How can I restore the framework-res.apk ????
Also adb shows no Device?
Please help!!!
Do adb kill-server and then adb devices again, should work.
Sent from my GT-I9100 using Tapatalk
did you find any solution to this problem?
renamedresfile said:
did you find any solution to this problem?
Click to expand...
Click to collapse
Did you read the entire thread?
I can only see one page and I read it completely. Here is description of my problem:
I already rooted my kindle fire, downloaded android market I loggedin using a google account. After that I was unable to change the google account. Browsed web and I saw the post of the video. I followed the instructions in the video.
steps followed: using root explorer, went to /system/framework and renamed framework-res.apk and and after I completed the renaming, the device crashed (or I clicked something; hence crashed?) and stuck in blank carrousel page.
So, I rebooted and all I get now if boot logo of 'Kindle fire'. It doesnt go any forward.
I connected to PC and I am able to see the device in ADB. But no root access in shell. So, any adb command I give I get back errors like: no permission; read-only folder, etc.
When I use the Kindle fire utility v0.9.3 and try to do temp root or root, I get.
Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running?
adbd cannot run as root in production builds
PC detects the device as 'Android Composite ADB interface'. But cant do anything in adb. I can push files to /data/local/tmp folder. Thats about it.
when I do
adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk
I get:
failed on '/system/framework/framework-res.apk.bak' - Read-only file system
Can someone help rename this file back to original framework-res.apk?
Thank you very much;
Oh! by the way, I also have a cable jigged as described in another thread. I plugged in the cable, did adb and the device is recognized. But no root access so all commands come back with permission denied; read-only file system, etc.
renamedresfile said:
I can only see one page and I read it completely. Here is description of my problem:
I already rooted my kindle fire, downloaded android market I loggedin using a google account. After that I was unable to change the google account. Browsed web and I saw the post of the video. I followed the instructions in the video.
steps followed: using root explorer, went to /system/framework and renamed framework-res.apk and and after I completed the renaming, the device crashed (or I clicked something; hence crashed?) and stuck in blank carrousel page.
So, I rebooted and all I get now if boot logo of 'Kindle fire'. It doesnt go any forward.
I connected to PC and I am able to see the device in ADB. But no root access in shell. So, any adb command I give I get back errors like: no permission; read-only folder, etc.
When I use the Kindle fire utility v0.9.3 and try to do temp root or root, I get
Error type 2 android.util.AndroidException: Can't connect to activity manager; is the system running?
adbd cannot run as root in production builds
PC detects the device as 'Android Composite ADB interface'. But cant do anything in adb. I can push files to /data/local/tmp folder. Thats about it.
when I do
adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk
I get:
failed on '/system/framework/framework-res.apk.bak' - Read-only file system
Can someone help rename this file back to original framework-res.apk?
Thank you very much;
Click to expand...
Click to collapse
First off, you're asking for help on your Kindle Fire in a forum for the GT-I9100. Totally different device...
That said, if you're getting "failed on '/system/framework/framework-res.apk.bak' - Read-only file system", this means your system folder needs to be remounted as read/write before you are allowed to rename or otherwise alter files in the system folder.
You need to do "adb remount" before you do "adb shell mv /system/framework/framework-res.apk.bak /system/framework/framework-res.apk"
EDIT: I'm also confused... Why the heck are you trying to rename framework-res.apk to solve what sounded like an issue with changing the google account attached to the device? No offense, but it doesn't sound like you should have root on your device at all. At least, until you understand what you're doing.
EDIT 2: Alternatively to the "adb remount", can you boot into recovery and rename the file there? I don't know anything about Kindle Fires, but on my I9100, I can boot to recovery, run an adb shell, and have root access to rename /system files once I remount.
But again, since you have a Kindle Fire, I don't know if that will work for you.
Is there a kindle fire forum?
renamedresfile said:
Is there a kindle fire forum?
Click to expand...
Click to collapse
Yikes. You really shouldn't be messing with root stuff if you have to ask this question. No offense - I'm not trying to be insulting.
Kindle Fire forum. Found by going to the forum home page and searching for the text "Kindle Fire" on the page.
I've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.
The 2016 honda pilot is running 4.2.2 with a hondalink launcher. I tried to install apks through the usb but the install button on the bottom is grayed out. I was able to enter the hidden settings. I have the developers options turn on, usb debugging checked, and installing unknown sources checked. I wasnt able to connect with adb with usb but I using wifi works. I was able to pull most of the files and info for file system. I tried to install a file manager apk by adb install and it gave a failure for internal error. The system does not have a sdcard directory and when I tried to install apks in the /system/app it gave me a perimission denied error. The /system/bin doesnt have SU or reboot recovery. im stump on what to do next. Help please!
Hi, I tried to install apps through adb over wifi and also had no luck. Did you try anything else since your last post. Does anyone else have any other ideas?
anekin007 said:
The 2016 honda pilot is running 4.2.2 with a hondalink launcher. I tried to install apks through the usb but the install button on the bottom is grayed out. I was able to enter the hidden settings. I have the developers options turn on, usb debugging checked, and installing unknown sources checked. I wasnt able to connect with adb with usb but I using wifi works. I was able to pull most of the files and info for file system. I tried to install a file manager apk by adb install and it gave a failure for internal error. The system does not have a sdcard directory and when I tried to install apks in the /system/app it gave me a perimission denied error. The /system/bin doesnt have SU or reboot recovery. im stump on what to do next. Help please!
Click to expand...
Click to collapse
Did you find any solution , I have the same problem and dont know what can I do I have honda accord 2017 with android version 4.2.2 I couldnt install any apps please if you have solution tell me
After fighting with this for nearly a month and reading dozens of threads on xda, stack-overflow, etc... I finally figured out this issue, so I'm putting it here in hopes it saves someone else the frustration.
The issue presented itself on my HTC One (M8) running the ViperOne 6.1.0 ROM.
I'm putting this thread in the general section though since I've seen many people with very similar, if not the same issues on a wide variety of devices.
I believe the root cause of my particular issue may be the way HTC sets their devices to simply allow all debugging without authorization if the phones are s-off.
Mine is still s-on, but I have another M8 that's s-off with the exact same ROM as well as an s-off M9, and both of them go straight into debugging, no questions asked, no prompt.
I'm wondering if maybe the ROM was developed using a developer version of the phone and is just missing the prompt, or something similar, but this is just conjecture.
The basic problem was that, when I tried to connect ADB, it showed the phone as "unauthorized" and no matter what I did, the prompt would not come up on the phone to allow debugging.
Also of note, I was missing the "Revoke USB debugging authorizations" menu item entirely (I could search for it, but it wasn't actually there in the menu)
I tried many different combinations of changing drivers, USB modes, enabling/disabling debugging, different machines, deleting the public and private keys for ADB on the computer, etc... all to no avail.
Finally, after much research and testing, I found this comment on stack-overflow and figured out how to manually authorize keys.
Note: This will require root, a custom recovery, or some way of writing the the system partition (I used TWRP at first, then TerminalEmulator later)
The key was to understand what clicking the dialog to 'always allow' a machine actually does.
When you click to always allow, android appends the public key from ADB on the computer into a specific file on the phone.
Since my phone wouldn't connect in the first place though, I didn't have that file or understand the format, etc...
The file is called adb_keys, it is a file (not folder) which is located at: /data/misc/adb/
The format of this file is one public key per line.
Thus, there are a couple of ways to go about manually authorizing a machine for debugging.
First, manually building the adb_keys file. (This is what I did at first)
Second, copying an existing adb_keys file from another device (Which doesn't need root)
For manually building the adb_keys file, the first step is to find the public key on the computer.
For me (Windows 10) it was located at C:\Users\<my profile>\.android\adbkey.pub
For Linux and OSX, I believe it is at: ~/.android/adbkey.pub
If you only need to authorize one computer:
Simply copy the adbkey.pub onto the device location: /data/misc/adb/ and rename it from adbkey.pub to adb_keys
chmod 0644 and then reboot.
Now, the phone should accept debugging from the computer just as though you clicked the dialog.
If you need to authorize several computers...
As mentioned, the /data/misc/adb/adb_keys file is actually a list of all the keys which have debugging permissions, one key per line.
First, collect the adbkey.pub files from each computer you want to authorize.
Then, using a text editor which supports linux style line breaks (Notepad++ if on windows) simply create your own adb_keys file by appending the contents of each adbkey.pub file, putting a line break between each key
Now save the adb_keys file you just created, and put it on the phone's /data/misc/adb/ folder using whatever method you prefer, and chmod 0644
If you need to revoke debugging permissions, (like the menu option, if the menu option is missing)
Simply delete /data/misc/adb/adb_keys
And finally,
If you have access to another device (does not have to be rooted) and want to replicate its debugging permissions
Plug the 'donor' device into the computer first, then issue:
adb pull /data/misc/adb/adb_keys c:\temp\adb_keys
(Or replace "C:\temp\adb_keys" with whatever file path works for you)
Then, copy the file to the 'target' device in the same location (/data/misc/adb/adb_keys) and chmod 0644
I've tested all of these methods and they worked well.
In the end, I used the last method since my tablet had all the debugging permissions I wanted on my phone.
Thanks,I have the same issue with the same rom. I tried your solution and it worked.
Hi, I ran into this issue with my Moto G5 plus. The only difference is that I'm not missing the Revoke Auth option, even though using it does nothing for me, and I still fail to get the Authorization popup when connecting via USB/using ADB.
I tried the above method of copying the adbkey.pub file to my device directory, renaming, etc. I am doing something wrong and would like a hint.
I copied the adb_keys via Windows Explorer to my devices root directory. There was a /data/ directory, but only Titanium Backup had a subdirectory within, so I created .../misc/adb/, and placed the adb_keys file there.
I rebooted to the TWRP recovery Terminal, and navigated to the /data/misc/adb directory. I ran chmod, and the system could not find the file specified. Listing directory contents also showed the directory to be empty (yet when viewed in Explorer or LineageOS, it's visible).
Did I place the keys file in the wrong place?
Copying via windows explorer does not place it in the device root.
Inception
I was trying to Copy one donor device's Adb key file to my broken android phone to mirror it on my PC, Following the guide of another post, and somehow i stumbled across this post, after failing to copy from Donor device. Now i managed to copy the adb_key from Donor device but LOL my broken Android device is Unauthorized. What should i do? IS THERE ANY SOLUTION?
misuvi said:
I was trying to Copy one donor device's Adb key file to my broken android phone to mirror it on my PC, Following the guide of another post, and somehow i stumbled across this post, after failing to copy from Donor device. Now i managed to copy the adb_key from Donor device but LOL my broken Android device is Unauthorized. What should i do? IS THERE ANY SOLUTION?
Click to expand...
Click to collapse
Do you have any way of writing to the /data/misc/adb/adb_keys file on the broken device?
I think i just did!
NFSP G35 said:
Do you have any way of writing to the /data/misc/adb/adb_keys file on the broken device?
Click to expand...
Click to collapse
I rebooted into recovery mode, copied, but still the mirroring application is not working, still prompting for allowing USB debugging. Now i connected the donor device on That mirroring application and Saved the RSA of Mirroring application, and going once again. Wish me good luck
misuvi said:
I rebooted into recovery mode, copied, but still the mirroring application is not working, still prompting for allowing USB debugging. Now i connected the donor device on That mirroring application and Saved the RSA of Mirroring application, and going once again. Wish me good luck
Click to expand...
Click to collapse
Well, don't forget to post back if it worked :good:
Guess I did i good job
NFSP G35 said:
Well, don't forget to post back if it worked :good:
Click to expand...
Click to collapse
Well it didn't work since the Adb server of Cmd and mirroring application were different, so i searched for another application which has same server as Cmd, and luckily i found a great software by Genymobile, named scrcpy, from github, just one click on scrcpy-noconsole and boom? Thanks for all the help.
misuvi said:
Well it didn't work since the Adb server of Cmd and mirroring application were different, so i searched for another application which has same server as Cmd, and luckily i found a great software by Genymobile, named scrcpy, from github, just one click on scrcpy-noconsole and boom Thanks for all the help.
Click to expand...
Click to collapse
Cool, glad to help.
For a while, I looked for ways to get around this from a different angle (for example, making the keys match on the ADB server side) but I ran into some issues and ended up getting what I needed via the steps in the OP.
Glad you got it working though!
"And finally,"...you should have led with that
I cannot thank you enough! Other proposed solutions to this hellish problem made my head hurt. This was beautifully simple - copy file from the working device onto non-working, change permissions and BOOM! It works.
Thanks again, you're awesome!
Happy to help!
Oh my god, it's not a folder! Thank you so much! I was about to give up, this was driving me totally crazy. Everywhere on the internet they just keep repeating the same advice that did nothing, I actually created that as a folder and no wonder it wasn't working.
I still can't believe it's working now, ahhh...
can't believe in my eyes. work perfect for me. thanks you so much!!
I am trying to use the 'copy keys file from another device' method.
I've copied the adb_keys file to my PC.
Now, how do I copy that file from the PC to the data folder?
adb won't allow it as it's not authorised, what am I missing?
Thank you in advance for your help!
Bungle2000 said:
I am trying to use the 'copy keys file from another device' method.
I've copied the adb_keys file to my PC.
Now, how do I copy that file from the PC to the data folder?
adb won't allow it as it's not authorised, what am I missing?
Thank you in advance for your help!
Click to expand...
Click to collapse
You can't copy to the device through ADB until you get ADB authorized... that's the whole point... you have to use some other method to get the file there.
I used TWRP custom recovery to copy the file from an external SD card the folder.
If you don't have an external SD card, use USB MTP/PTP, Mass Storage, a USB OTG adapter and thumb drive... if you desperate, zip the file and email it to yourself... pretty much endless methods of actually getting the file onto the phone somehow.
But you'll need root (or a custom recovery) to copy the file from wherever it is on the device to the correct location (/data/misc/adb/adb_keys)
You could potentially use several methods, for example you could use terminal emulator or a root file explorer to get the file to the correct folder.
NFSP G35 said:
You can't copy to the device through ADB until you get ADB authorized... that's the whole point... you have to use some other method to get the file there.
I used TWRP custom recovery to copy the file from an external SD card the folder.
If you don't have an external SD card, use USB MTP/PTP, Mass Storage, a USB OTG adapter and thumb drive... if you desperate, zip the file and email it to yourself... pretty much endless methods of actually getting the file onto the phone somehow.
But you'll need root (or a custom recovery) to copy the file from wherever it is on the device to the correct location (/data/misc/adb/adb_keys)
You could potentially use several methods, for example you could use terminal emulator or a root file explorer to get the file to the correct folder.
Click to expand...
Click to collapse
Hey NFSP G35, thank you for the reply!
I figured there was something I was missing, I just don't know the steps to do it right.
I have a Moto X Play that has a broken screen, so no display, and does not accept touch input.
It powers on and is working as it was before the screen broke as far as I can tell, so I'm trying to connect it up to the PC to get all the data off it.
However, before it broke, something happened with the software that meant Google Play disappeared.
The device is stock Motorola device, so not rooted, no TWRP etc. USB debugging is enabled but not authorised.
What would you recommend is the best way to get the adb_keys onto the phone given the issues above?
Your help is greatly appreciated!
Sorry, given your circumstances, it's likely impossible or very difficult
?? Thanks, it worked perfectly on Samsung J6 run Evolution X 4.0
Thank you it's working