Hi all,
anyone can point in the right direction how to get this boot loop fixed? theoretically i would want to push back the correct 3 locksettings files into /data/system as i have bad locksettings.db uploaded in it.
background info:
- boots into main home launcher then immediately reboots
- samsung note 3 with MJ7 stock rom but with MJ1 bootloader
- rooted and android 4.3, can access download mode and stock recovery mode
- knox 0 and wishing to remain as is
If you have USB Debugging enabled and have accepted the authentication request, then you should be able to remove the lockscreen settings like this:
adb shell
su
rm /data/system/locksettings.db
rm /data/system/locksettings.db-wal
rm /data/system/locksettings.db-shm
reboot
Other than that, you might just have to do a factory reset as that will remove the old lockscreen settings as well.
es0tericcha0s said:
If you have USB Debugging enabled and have accepted the authentication request, then you should be able to remove the lockscreen settings like this:
adb shell
su
rm /data/system/locksettings.db
rm /data/system/locksettings.db-wal
rm /data/system/locksettings.db-shm
reboot
Other than that, you might just have to do a factory reset as that will remove the old lockscreen settings as well.
Click to expand...
Click to collapse
how do i get into adb? booting into download mode and stock recovery, i can't see any devices through the command "adb devices".
if i'm in stock recovery and choose the option "apply update from adb", only then can i see the device but i'm limited to adb sideload only without shell.
ebackbone said:
how do i get into adb? booting into download mode and stock recovery, i can't see any devices through the command "adb devices".
if i'm in stock recovery and choose the option "apply update from adb", only then can i see the device but i'm limited to adb sideload only without shell.
Click to expand...
Click to collapse
Have to be booted or custom recovery for adb to work.
es0tericcha0s said:
Have to be booted or custom recovery for adb to work.
Click to expand...
Click to collapse
initially that's what i thought.
i'm wondering is it possible to reflash through odin a small subset so that it replaces certain files into /data/system alone? theoretically that could work right? if so, i need some pointers on where to go to attempt that.
ebackbone said:
initially that's what i thought.
i'm wondering is it possible to reflash through odin a small subset so that it replaces certain files into /data/system alone? theoretically that could work right? if so, i need some pointers on where to go to attempt that.
Click to expand...
Click to collapse
No. For 2 reasons. One, Odin doesn't work like that. It can install all the separate partitions, but not individual files and settings. And two, official firmware files don't wipe data.
Related
Introduction
The purpose of this guide is to help users understand how to use the default Android System Recovery <3e> image that is installed on the Nexus 10. Note that if you have already installed a custom recovery image such as Clockworkmod Recovery (CWMR) or Team Win Recovery Project (TWRP) this will overwrite the stock default Android System Recovery. This guide will teach you how to access recovery mode, and how to use all the features of the default Android System Recovery <3e>.
Click to expand...
Click to collapse
What is Recovery Mode?
Recovery mode is a special environment that you can boot into for troubleshooting and upgrading purposes such as applying an update, performing a factory reset, or wiping the cache partition.
Click to expand...
Click to collapse
How to Access Recovery Mode
Recovery mode can be accessed in one of two ways by pressing a key combination or using adb. When you enter recovery mode the recovery options menu will be hidden and you will see an Android lying on it's back with a red triangle exclamation point. To show the recovery menu simultaneously hold the Power Button + Volume Up buttons.
Key Combination Method
The first way of accessing recovery mode is by pressing a key combination simultaneously. For the Nexus 10 recovery mode can be accessed by simultaneously holding the Power Button + Volume Up + Volume Down buttons. To show the recovery menu simultaneously hold the Power Button + Volume Up buttons.
ADB Method
The second way of accessing recovery mode is by issuing the following ADB (If you don't know what ADB is you can learn more about it here) command:
Code:
adb reboot recovery
To show the recovery menu simultaneously hold the Power Button + Volume Up buttons.
Click to expand...
Click to collapse
Using the Recovery Menu Options
When the recovery menu appears you will be presented with a menu selection that appears similar to this:
Code:
Android system recovery <3e>
Volume up/down to move highlight:
power button to select.
------------------------------------
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
------------------------------------
The volume up and volume down button can be used to highlight different options and the power button can be used to confirm your selection.
Reboot system now
The reboot system now option will exit recovery mode and reboot the tablet normally starting the normal Android operating system.
Apply update from ADB
The apply update from ADB option allows you to sideload a stock Android update to your device using ADB without the need for root access or a custom recovery (Note: You will need a custom recovery to flash a custom ROM, custom kernel, or other modifications, this only meant to apply official Google updates).
Prior to using the "apply update from adb" option you must make sure you have installed the Nexus 10 USB drivers, installed ADB, and made sure "USB Debugging" is checked under developer settings within Android. Once you have done these things from ADB issue the following command:
Code:
adb sideload <path/to/update.zip>
Where path/to/update.zip is the location on your computer that the update file is stored at and update.zip is the name of the file. An example using adb to sideload an update:
Code:
adb sideload JDQ39.zip
After you enter the sideload command the file should transfer to your device and once it is done transferring it will begin the update process. Once it has completed the update process, reboot your device.
Wipe data/factory reset
The wipe data/factory reset option erases the contents of /data partition as well as the /cache partition. This will erase any apps, pictures, music, data etc. you have stored on /data partition in addition to erasing the /cache partition. This will not erase your /system partition.
Wipe cache partition
The wipe cache partition erases the contents of /cache partition. Wiping the /cache partition is one common way of fixing a bootloop.
Click to expand...
Click to collapse
Conclusion
I hope that the contents of this guide have been helpful to you and that you have enjoyed this how to .
Click to expand...
Click to collapse
Nexus 10 - Google Play and Internal storage not accessible
Your explanation on recovery was useful. Thanks
My son rooted his new nexus 10 in january and reinstalled stock rom back again. After reinstallation, google play and the internal storage were not accessible. So the device could not install any new apps from Google and the Camera could not be used. When trying to open the camera it gives an error asking to install mass storage.
I too installed google stock rom both versions 4.2.2 and 4.2.1, formatted and wiped /data/media/ and /cache partitions several times but the end result is the same. Only some basic apps like gmail and chrome browser works.
Tried using different user id to log in , still there was no solution.
I was able to push and pull files into /data/media/ successfully. I learnt in one of the forum that /data/media/ is also named as /sdcard/ , i tried to write a fole to /sdcard/ folder it didn't work. So what's the problem with google play and internal storage? Is there anything I can do in the system folder to set it right.
kareemyas said:
Is there anything I can do in the system folder to set it right.
Click to expand...
Click to collapse
Were you trying to restore the stock factory image? Did you have a custom recovery installed? It sounds like in the process of restoring the stock factory image it didn't restore properly and that's likely what's causing your problem with storage and camera. I would recommend restoring your tablet to stock by flashing the nexus 10 factory image for 4.2.2 https://dl.google.com/dl/android/aosp/mantaray-jdq39-factory-d79f489e.tgz.
Sent from my SCH-I535 using xda premium
I flashed into Stock Recovery and flashed the factory Google Image for 4.2.2, same from your link. Update runs without error. But the problem is still there.
kareemyas said:
I flashed into Stock Recovery and flashed the factory Google Image for 4.2.2, same from your link. Update runs without error. But the problem is still there.
Click to expand...
Click to collapse
Interesting, even after using fastboot to erase all the partitions and then using fastboot to flash the factory image your storage problem still persists correct? Have you encountered this problem before you root the tablet?
There was no problem before the rooting.
kareemyas said:
There was no problem before the rooting.
Click to expand...
Click to collapse
If your device is still giving you problems with the internal storage after flashing the Nexus 10 factory image (Through fastboot) multiple times it is possible a hardware issue has arisen in which case warranty would be your best option.
Just a note for everybody trying to get into recovery menu with wipe data etc. It's a bit tricky. First, get into the Recovery (lying robot) as described above. And then press briefly all three buttons (power+vol up+vol down) at the same time. If nothing happens, try again and again and again. You'll get there eventually. It requires some practice to press all those buttons at exactly same time. Holding them won't help.
What is the best version of TWRP to flash to the m XT907?Thanks Bryan
bryan942 said:
What is the best version of TWRP to flash to the m XT907?Thanks Bryan
Click to expand...
Click to collapse
The current stable unofficial version of TWRP for the Razr M is 2.5.0.0 http://forum.xda-developers.com/showthread.php?t=2302969 an alpha version of 2.6.0.0 can be found there as well.
Sent from my SCH-I535 using xda premium
I cant get to normal mode after installing cwm recovery
I have flashed cwmr in my micromax A25. but i cant get to normal mode after that. When i reboot to normal mode it stuck with the micromax logo and i cannot get back to normal mode. I tried many times, but i cant get back to my normal mode. Can anyone help me to solve this issue?
raj_ said:
I have flashed cwmr in my micromax A25. but i cant get to normal mode after that. When i reboot to normal mode it stuck with the micromax logo and i cannot get back to normal mode. I tried many times, but i cant get back to my normal mode. Can anyone help me to solve this issue?
Click to expand...
Click to collapse
Try wiping cache in recovery mode and see if that helps, if it doesn't resolve the problem I would re-flash the stock recovery image for your phone and see if that fixes it.
Can you flash a custom recovery while in stock recovery (adb sideload) and not rooted?
cma371 said:
Can you flash a custom recovery while in stock recovery (adb sideload) and not rooted?
Click to expand...
Click to collapse
You cannot, you will need to use fastboot to flash a custom recovery since your not rooted.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Thank you for the informative post.. :good:
Couple questions about stock revoery
1. Does adb option have root access? Or can it get it?
2. Will the adb option allow you to issue fastboot command?
3. If adb can't get root option how does it do the update?
phipps_2000 said:
1. Does adb option have root access? Or can it get it?
2. Will the adb option allow you to issue fastboot command?
3. If adb can't get root option how does it do the update?
Click to expand...
Click to collapse
To answer your questions:
1. You can restart the ADB daemon as root, by running the command adb root provided it is enabled in the build. Keep in mind stock recovery adb access other then sideload doesn't always work.
2. ADB and Fastboot are two separate things, you will need to boot the device into the bootloader in order to issue Fastboot commands to the device.
3. I assume you are talking about adb sideload, the process that performs the sideload operation runs as root through kernel level operations (File permissions and otherwise). Overall the whole sideload operation is coded into the recovery to allow it to be performed with the necessary file permissions and processes.
If you have any further questions let me know I'll be happy to help you out.
OK, here's the deal. My i777 was running SlimROM, updated, and now my power button is inop. Flashed back to stock ICS, but I forgot to do one critical step - a complete wipe before installing. Now my phone gets stuck at the "Rethink Possible" screen, and I can't do anything else.
I've booted into 3e recovery and tried recovery --wipe_data through adb, but it still hangs. (as suggested here). I've got a jig, forced it into download mode, and tried flashing another ROM, but I still get stuck on the Rethink Possible screen.
Is there a way that I can basically nuke all the contents of the phone so I can use it again? I've read through most of the documentation for adb, but I don't see an option.
steelforce said:
OK, here's the deal. My i777 was running SlimROM, updated, and now my power button is inop. Flashed back to stock ICS, but I forgot to do one critical step - a complete wipe before installing. Now my phone gets stuck at the "Rethink Possible" screen, and I can't do anything else.
I've booted into 3e recovery and tried recovery --wipe_data through adb, but it still hangs. (as suggested here). I've got a jig, forced it into download mode, and tried flashing another ROM, but I still get stuck on the Rethink Possible screen.
Is there a way that I can basically nuke all the contents of the phone so I can use it again? I've read through most of the documentation for adb, but I don't see an option.
Click to expand...
Click to collapse
Id wait until a dev chimes in, but my understanding is that as you can still get into DL mode, ODIN would be your best bet. Id flash one of the all in one ODIN ICS packages that also contain boot loaders (LL6 would be most recent). As a last resort you can also flash the stock .pit file and repartition the whole phone, BUT BE SURE TO BACKUP YOUR EFS FOLDER if possible. I say this as I did not do this and now have a generic IMEI on my phone, hindering some aps from working.
ADB is able to reformat and flash ROM packages as far as i know, though it should be unnecessary as long as you can still use ODIN. The only reason i used ADB was to resurrect a S2 i bought of someone that flashed a ROM from a i9100.
steelforce said:
OK, here's the deal. My i777 was running SlimROM, updated, and now my power button is inop. Flashed back to stock ICS, but I forgot to do one critical step - a complete wipe before installing. Now my phone gets stuck at the "Rethink Possible" screen, and I can't do anything else.
I've booted into 3e recovery and tried recovery --wipe_data through adb, but it still hangs. (as suggested here). I've got a jig, forced it into download mode, and tried flashing another ROM, but I still get stuck on the Rethink Possible screen.
Is there a way that I can basically nuke all the contents of the phone so I can use it again? I've read through most of the documentation for adb, but I don't see an option.
Click to expand...
Click to collapse
You need root access to format the data partition. I don't use adb a lot, but I think you can boot into recovery, then "adb shell", then "format data." You might have to type "su." If that doesn't get you out of the Rethink Possible screen, the I would format data, format system, and format cache. Then turn the phone off, by pulling the battery if necessary, and enter download mode and flash the full stock distribution. As the previous poster suggested, UCLL6 would be a good choice. You can get it from the download repository. See the link in my signature.
creepyncrawly said:
You need root access to format the data partition. I don't use adb a lot, but I think you can boot into recovery, then "adb shell", then "format data." You might have to type "su." If that doesn't get you out of the Rethink Possible screen, the I would format data, format system, and format cache. Then turn the phone off, by pulling the battery if necessary, and enter download mode and flash the full stock distribution. As the previous poster suggested, UCLL6 would be a good choice. You can get it from the download repository. See the link in my signature.
Click to expand...
Click to collapse
Thanks. I forgot to grab the phone before I left for the office this morning, so I'll try it when I get home later tonight.
steelforce said:
Thanks. I forgot to grab the phone before I left for the office this morning, so I'll try it when I get home later tonight.
Click to expand...
Click to collapse
So, home with my phone. When I get into the shell, format isn't a valid command:
Code:
[email protected]:/ $ format
format
/system/bin/sh: format: not found
Trying to su ends up segfaulting, so I don't think it's a permissions issue. Other sources suggest using fastboot, but as I understand it, the i777 doesn't support it.
I'm looking at the mounts - is there documentation on which of the /dev/block/mmcblk0pX partitions map to the mount points? I'm familiar with Linux (at least enough to get me in trouble), but I'm lost on where to go next.
You have to have root access to do the format command. Requires the # prompt, like this:
Code:
adb shell
$ su
# format data
# exit
$ exit
Probably, cache is mounted but system and data are not mounted. It shouldn't make any difference though, if I remember right.
If you can't get the su command to give you the # prompt, then maybe adb is not connected to the daemon correctly?
Edit:
I have never used adb in recovery before, so for my own interest, I decided to do a little experimentation. First of all, to get a hash prompt in shell try
Code:
adb root
followed by
Code:
adb shell
From reading, it seems some people say both wipe and format commands should work in shell in recovery, but I couldn't get them to work. I would get "/sbin/sh: format: not found" error. So the work around is this:
Code:
adb shell
~ # mount /data
~ # rm -rf /data/*
~ # reboot
This will recursively force the removal of the contents of the data directory. I did not test this, but I did test "rm -rf /cache/*" and successfully removed the contents of the cache directory, so I know it should work.
If your system still doesn't boot, you could wipe cache and system as well as data and then reboot into download mode and flash the full stock tar
Code:
adb shell
~ # mount /data
~ # mount /system
~ # rm -rf /cache/*
~ # rm -rf /data/*
~ # rm -rf /system/*
~ # reboot download
creepyncrawly said:
Edit:
I have never used adb in recovery before, so for my own interest, I decided to do a little experimentation. First of all, to get a hash prompt in shell try
Code:
adb root
followed by
Code:
adb shell
Click to expand...
Click to collapse
Ugh - adb root fails with the following error:
Code:
D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb root
adbd cannot run as root in production builds
Looks like it's because the build that I have flashed doesn't have root. Wicked catch-22, since I can't root the phone until I wipe the cache to actually boot.
steelforce said:
Ugh - adb root fails with the following error:
Code:
D:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools>adb root
adbd cannot run as root in production builds
Looks like it's because the build that I have flashed doesn't have root. Wicked catch-22, since I can't root the phone until I wipe the cache to actually boot.
Click to expand...
Click to collapse
Well, yes, you need root. You could flash one of the stock plus root packages, probably Entropy512's original uckh7 plus root since it has busybox, with odin, see links in my sig. I didn't see anything in your original posts that indicate the flash would fail.
creepyncrawly said:
Well, yes, you need root. You could flash one of the stock plus root packages, probably Entropy512's original uckh7 plus root since it has busybox, with odin, see links in my sig. I didn't see anything in your original posts that indicate the flash would fail.
Click to expand...
Click to collapse
The flash doesn't fail, but it's never able to boot past the AT&T "Rethink Possible" splash screen. I've tried flashing a couple of different packages, but i'll try some more tonight.
steelforce said:
The flash doesn't fail, but it's never able to boot past the AT&T "Rethink Possible" splash screen. I've tried flashing a couple of different packages, but i'll try some more tonight.
Click to expand...
Click to collapse
Flash the rooted package and you will then have root. Whether the phone boots or not, the system will then contain the superuser.apk and the su binary. I suggested Entropy512's package because I'm not sure but I think you need busybox to use the unix commands in adb in recovery. My stock plus root packages don't have busybox, and if you can't boot, you can install it from the play store. Once you have root in the system, then adb root should succeed.
creepyncrawly said:
Flash the rooted package and you will then have root. Whether the phone boots or not, the system will then contain the superuser.apk and the su binary. I suggested Entropy512's package because I'm not sure but I think you need busybox to use the unix commands in adb in recovery. My stock plus root packages don't have busybox, and if you can't boot, you can install it from the play store. Once you have root in the system, then adb root should succeed.
Click to expand...
Click to collapse
I tried both of Entropy512's packages from here. Flashed them and tried to boot, both hung at the Rethink Possible screen. Rebooted into recovery, was able to connect to it via adb - but adb root failed on both.
I'm getting closer and closer to punting and picking up a Nexus 4 after this....
With lineage recovery I do a full wipe like:
Code:
mkfs.ext4 -qFF /dev/block/by-name/userdata
mkfs.ext4 -qFF /dev/block/by-name/cache
mkfs.ext4 -qFF /dev/block/by-name/system
Like a lot of people, I rooted, busyboxed and installed SafeStrap. Unfortunately, I can't boot anymore, the best I can do is get into SafeStrap or recovery. I know I can manually remove safestrap using adb shell.
When I try to run adb shell while in SafeStrap, I get this:
Code:
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh"; caused by library "libc.so" not found
If I'm in actual recovery, adb devices does not list the phone.
Someone please help me get into ADB shell so I can dump SafeStrap!
CapinWinky said:
Like a lot of people, I rooted, busyboxed and installed SafeStrap. Unfortunately, I can't boot anymore, the best I can do is get into SafeStrap or recovery. I know I can manually remove safestrap using adb shell.
When I try to run adb shell while in SafeStrap, I get this:
Code:
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh"; caused by library "libc.so" not found
If I'm in actual recovery, adb devices does not list the phone.
Someone please help me get into ADB shell so I can dump SafeStrap!
Click to expand...
Click to collapse
Try "adb shell /system/bin/sh"
Something's not right, as there's no "/sbin/sh" file on my *stock* SGS4.
However. Removing Safestrap will probably just brick your phone. What build, bootloader, etc?
I'm NC5. I rooted with towelroot. Everything was actually working fine for several days, then I let the battery die and now I can't get past SafeStrap. I tried your suggestion trying to launch ADB shell and it returned the same error.
When I run ADB devices while in safestrap, it returns as being in recovery. I can also get it into sideload mode in the stock recovery. It is not detected when rebooted into Download.
At this point, I would be happy to completely factory reset with ODIN if that's even possible. I'm not familiar with ODIN, so I'm trying to read up.
While in Safestrap (I'm using v3.72 on a Galaxy S4 NB1), go to Mount -> Select "System". After mounting the system partition, I was then able to adb shell into the device like normal.
NOTE: One difference in adb that I noticed was that I lost my adb shell root access in Safestrap mode (even tho the device was rooted beforehand). Might be something with SELinux.
HTH.
The long awaited Full
unroot method is finally here for the Att variant of the lg g vista d631.
+++++Prerequisites+++++
Root
Busy box by Stephen ( it's the only one I used and know works) {you may need to use a root explorer to manually delete the busybox file from system/shin, xbin, data/media, data/data, or wherever you may have installed it too}
KingUser app installed on phone
Fastboot
Stock laf partition (download link at the bottom of this post.
P.s.
(I have cwm still installed right now and download mode reads unrooted in grayed out text)
First of all if you do not know how to enable fastboot you have to run this adb command
adb shell
su
dd if=/dev/zero of=/dev/block/mmcblk0p15
Now uninstall busybox first if you have it installed.
Now open up kinguser and click the top left settings and open up the manage root permissions. Click remove root. Then click clear.
Power off your phone.
Boot into fastboot mode and run these commands (vol+ then plug phone into pc)
fastboot erase rct
fastboot format rct
Then run this command to flash the stock laf partition back
fastboot flash laf xxxxxxxx.img (Xxxxxx is the directory of the laf.img
(Laf is the stock lg download mode, when you zero it out it just has fastboot)
Now unplug your phone
Pull the back cover off with it on and remove the battery.
Wait 10 seconds
Power it back on
Open up your dialer and dial this
3845#*631#
Scroll down to lg rct
Click it
Open display results
And it should say not rooted now
Now power off your phone
Wait a few seconds
Boot into download mode (vol+ then plug your phone into the pc)
Verify it says Unrooted.
So yeah here is a full unroot method to pass lg download mode root check.
I'm downloading update again and will post results in the lg root request thread
If your phone says you are up to date do this
Open up settings
Apps
Go to the all tab
Sellect Google services
Click manage data
Clear all at the bottom
Go to about phone software update and check..
Still says it...
Do it again...
Now it says wait a day.....
Change time and date ahead one day.
Check again...
Bam it's there
Also I'm not sure if I need stock recovery. Ill update with that.
And just to clarify you do need stock recovery to flash the software update.
However I am not able to update. And that's all it says. Error 0x1117008
Link to laf folder on my drive and they are labeled.
https://drive.google.com/folder/d/0B-GvkM12QEbMZkRNVjdyWlIxU3M/edit
Link will be posted for laf partitions in 1 hour due to slow upload speeds
Thanks, it is necessary to try. It is better to get drain D631 10B or 20D KDZ the file of course.
----------------
I deleted everything but....
So when I went to erase the rct it went thru but formating didn't. I also cant figure out how to change the directory to find where I have the laf.img. I have it in E:\laf.img but fastboot wouldn't take it. Any help would be appreciated trying to get 5.0 so my bluetooth will work again.
jbird6143 said:
So when I went to erase the rct it went thru but formating didn't. I also cant figure out how to change the directory to find where I have the laf.img. I have it in E:\laf.img but fastboot wouldn't take it. Any help would be appreciated trying to get 5.0 so my bluetooth will work again.
Click to expand...
Click to collapse
Same for me. I can't format rct. If you place the laf.img in your fastboot directory, you won't have to change directories.
Just to add to this, I was able to reset the root checker. It said I still have busybox installed even though I never installed it. So I was able to use adb to delete the remaining file, run this command without quotes: "adb shell rm -r /data/local/tmp/busybox" Reboot your device. Run the root check again, it still shows busybox. To reset it copy the attached file (unzip first) to the root of your internal storage and reboot. This forces the root checker to check again. Now it should say Not rooted. But I still get Error 0x1117008. This is driving me crazy! I hope we can figure this out.
How do you get rid of your software status say modified so I can update my phone to lollipop? Need Help!!!
My android (jellybean) tablet was turned off in middle of update and now is in boot loop. It was rooted with USB debugging on.
I MUST recover files (PDFs, .doc, .wav .JPEG, etc ) without erasing them.
Questions:
1 Do I use Odin and TWRP together?
2 Will Odin flash Samsung stock firmware erase files on device?
3. Will TWRP .img file erase everything?
4. Are these instructions correct?
I recommend you install TWRP recovery. It's the most feature-rich of all the recoveries I have used, and I will be assuming that is the recovery you use for the rest of this.
1. Boot into TWRP. (how? TWRP is an .img file )
2. Push your ADB public key to your device to force authentication.
____On Windows, do: adb push %UserProfile%\.android\ad
bkey.pub /data/misc/adb/adb_keys
3. Reboot into Android. Try adb shell and see if you get a shell prompt. If so, great! Exit it and run adb logcat, and read the huge error log for problems. If you didn't get the shell, well, then I think you're screwed, unless someone has cooked up a recovery zip for enabling adb.
What happens after ADB logcat?
Thank you..