I looked through A LOT of bricked KF threads but I can't fix the issue that I'm having. Before I found this forum and the very useful looking tools that it provides (KFU, etc) I managed to root my KF by using adb and pushing / installing burritoroot by the command prompt. Everything looked OK, I installed su and got root access to work in the adb shell as well as for apps.
I attempted, without much success, to get the Android Market working on my KF but it always crashed. I messed with some permissions like for /system/app, but I changed that one back to match the other folders in /system.
I may have deleted an apk out of /system/app that wasn't the Android Market, but I'm not sure...
Anyway, I tried to reboot my KF and it got stuck in a boot logo loop. It reports a boot mode of 4000 (normal).
I tried the fastboot recovery method and also KFU, but there are some issues:
Root access seems to have disappeared (access through adb shell cannot be elevated)
Burritoroot will not install anymore through KFU (I get the message "Error: Could not access the Package Manager. Is the system running?"
The above message also occurs when I try to use the adb install command
Fastboot never recognizes the device. It sits on <Waiting for Device> forever.
I've tried rebooting the KF while connected and reconnecting the USB.
I made a Factory Cable, but the Fastboot condition is the same.
I uninstalled my Windows drivers until it showed up as "Kindle" in the Device Manager and installed the files that came with KFU.
I tried the KF Unbrick utility, but that didn't seem to do anything that I missed.
Additionally, when I connect with adb shell I have limited file system access. I can is through /system and some other folders, but I can't access /sdcard and I can't seem to mount the sd card
After writing all this and thinking it through, I decided to compare the /system/app directory on my KF with one in an update.zip file that I downloaded.
It looks like I deleted the file ApplicationsProvider.apk from /system/app
That seems to be the only thing missing.
Is this a Try-to-return-your-KF important file? Is my KF hosed?
fonetik said:
Is this a Try-to-return-your-KF important file? Is my KF hosed?
Click to expand...
Click to collapse
Nope, if you can get fastboot working it doesn't matter how broken /system is. Try this to sidestep the Windows driver problems I think you're having:
http://forum.xda-developers.com/showthread.php?t=1430038
Once you get TWRP installed you can restore from the stock update which will wipe and replace /system.
Thanks I'll give this a shot. I had some issues with Windows when trying to install Cyanogen on my Droid X and a Linux Live-CD got me back on track. Hopefully this will do the trick. I'll report back.
Well, I'm in Ubuntu and I got the firekit stuff up, but it does the same thing. It refuses to connect with fastboot. It just sits at < Waiting for Device >.
I had a similar problem and it was my usb driver set up:
/etc/udev/rules.d/##-android.rules
the ## for Meerkat is 70
SUBSYSTEM==”usb”, ATTR{idVendor}==”0bb4″, MODE=”0666″
Vendorid is 1949 for KF
link that got me going: http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
sorry if you already know this.
I'm new to this so thanks. I'll try it tomorrow when I get a chance.
fonetik said:
Well, I'm in Ubuntu and I got the firekit stuff up, but it does the same thing. It refuses to connect with fastboot. It just sits at < Waiting for Device >.
Click to expand...
Click to collapse
Are you sure you're in fastboot at that point? Are you using your factory cable? Try doing this to get into fastboot mode and use a different USB cable to connect with fastboot. If that doesn't work, do the same but use Firekit in case the fastboot drivers are messed up.
I'm probably not in fastboot. I'll give this a shot. Thanks again.
Edit:
That seems to have gotten me into Fastboot! I'll see if I can get TWRP installed.
There's a faint pulse =)
Edit 2: TWRP installed OK and I used it to try and install the stock update.zip. It rebooted and then got stuck at the logo again, but I'm going to keep working on it. At least I have a tool I can use.
Edit3: I seemed to be stuck at the TWRP yellow triangle, I think I managed to install FireFireFire, and managed to get back into TWRP. I cleared all my caches and did a factory reset. Then I installed a pre-rooted version of 6.2.1. It did a little reboot dance for a while and then came up into the OS!
Thanks a ton pokey9000. I'm happy to send a couple $$ your way.
fonetik said:
Edit3: I seemed to be stuck at the TWRP yellow triangle, I think I managed to install FireFireFire, and managed to get back into TWRP.
Click to expand...
Click to collapse
Just in case someone else reads this... The Yellow Triangle is not TWRP... it is FireFireFire... TWRP by default is the blue themed screens you get after the FireFireFire icon and will start out saying TEAMWIN in Landscape mode.
BTW, good to hear you fixed the problem. You should edit the original post and change the Subject adding [SOLVED]
krelvinaz said:
Just in case someone else reads this... The Yellow Triangle is not TWRP... it is FireFireFire... TWRP by default is the blue themed screens you get after the FireFireFire icon and will start out saying TEAMWIN in Landscape mode.
BTW, good to hear you fixed the problem. You should edit the original post and change the Subject adding [SOLVED]
Click to expand...
Click to collapse
Sorry about the confusion. It was the FFF triangle, but the KF wasn't going into recovery when I held the power button down. I reinstalled with FFF using adb and it worked. Original post subject updated.
Related
Hello, brand new to the Kindle. I rooted my device just fine last night and decided to use Kindle Fire Utility to install TWRP. ADB was recognizing the device perfectly and the script seemed to be running fine until it rebooted the Kindle. At that point the script said "reboot: operation not permitted waiting for device" for an extended period of time. After waiting awhile, at this point I did something I probably shouldn't have, I unplugged the Kindle and rebooted it using the power button. It's been getting stuck at the "kindle fire" boot animation ever since. I haven't gotten a screen with a triangle and fire logo.
I tried following the instructions in the sticky but it seems adb no longer recognizes the device, so I can't push zergRush or anything past that.
Is it permanently bricked or is there a method to fix my problem yet?
Thanks for any help.
_______________________
Update: kindle was fixed by uninstalling drivers, reinstalling as android composite usb device, and switching it out of fastboot. not permanently bricked.
sounds like its in fast boot.
open the utility again, check if its in fast boot, if it is run the install command again. if u can't get it installed, use utility to change boot mode back to 4000.
I had the same problem this method worked for me http://forum.xda-developers.com/showpost.php?p=20509949&postcount=245 http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Thanks for the fast replies!
When I try to change the bootmode using the fastboot it just says waiting for device and never progresses. KindleFireUtility shows ADB Online, Boot status at 4002, and fastboot as offline. Device manager doesn't show a Kindle, just an android adb interface with a yellow ! triangle.
I did restart the PC once and the kindle a few times. No luck yet.
I installed the ADB Composite driver again for the device and got this error (attached)
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
uninstall the driverand use the driverin the utility thread? someone said leaving ur kindle connected to ur pc and rebooting ur pc will reboot the kindle? if it works su with terminal and change bootmode back to 4000
sent from my kindle fire
Alright everyone, I got it working after uninstalling the driver for the Android device, shutting down, starting up again, and plugging in and reinstalling the driver, then changing the bootmode using the instructions previously posted. Thank you all SO MUCH for helping as much as you could. Now to try this again!
terracode said:
I had the same issue. It turned out that I had forgotten to update my computer with the drivers needed for TWRP install after copying them to the Android and .Android folders. I was able to get to the first reboot.. waiting for device and then checked device manager when it wouldn't progress. I found that the the driver was unrecognized. After updating the drivers in device manager, TWRP completed install successfully and I was able to backup my FW6.2 and then flash CM7.
Click to expand...
Click to collapse
Now I'm wondering what you mean by making sure the drivers are installed for TWRP to install correctly. Obviously I missed a step the first time, what do I do to make sure I don't miss it again? Right now when I try to install TWRP again it says "The system cannot find the filepath specified" several times.
would recomend to use following:
http://forum.xda-developers.com/showthread.php?t=1399889
download the utility and prepare according:
http://forum.xda-developers.com/showthread.php?p=20574755#post20574755
change bootmode, install twrp or whatever with the utility
Got twrp on it last night successfully and flashed CM7.
My question is somewhat related to this thread...
I'm on 6.2 (wifi turned off) and was already rooted and am trying to update to the 6.2.1 secured update with root installed update found on XDA. I'm using Kindle Fire Utility v.6, and to the best of my knowledge using the drivers included with the KF Utility program.
In the utility I show...
ADB Status: Online
Boot Status: 4000
Fastboot Status: Offline
Question is I'm not familiar with fastboot and unclear if I have everything configured in order to (safely) install TWRP. In a command prompt when I type 'fastboot devices' nothing is displayed ("adb devices" shows the device). Combined with the fact I've never seen anything but "Offline" for the Fastboot Status, I'm a little concerned I'm missing a piece of the puzzle and hesitant to install TWRP until I know better.
Any help/advice would be appreciated. Thanks!
look at my post on page 1 of this thread !
@Stevebro: I believe if you are using KF Utility v.6, then you should be good to go. As long as you installed and updated the usb Drivers and then ran zergRush, you should be at the point where you can install TWRP. Just make sure you are using the latest version of KF Utility and it should go pretty smoothly.
... After you install TWRP, I'd recommend going back to your KF OS and do a Titanium Backup of your apps and then doing a TWRP backup. When you flash to CM7 you can restore all your apps easily and painlessly using Titanium backup to restore with the Batch restore option.
Couple nervous moments, reboots and switching out of fastboot mode in the utility... but it all went well. Thanks for the help!!
glad to hear everything is fine ...
Glad to hear everything worked out. I myself sat staring at the "yellow triangle" for a couple of hours. lol, but I just kept working through it and tried not to panic and I got everything working again.
I think OP should edit the first post, or get a mod to edit the title. I keep reading random posts about "lot's of people permanently bricking their Kindle Fires" while I cannot recall a single instance of someone bricking and having to return one and it is getting tiresome.
Hi there i have a rotted kindle fire with burrito root.
I rooted it yesterday and everything was fine, then i turned it off and back on later it worked fine.
the next day it hangs on the boot logo (it is animated no triangle)
adb recognizes it yet i cant access adb root, remount etc Permission denied.
I cant install TWRP
What i wanted to do was go to the /sdcard directory and push the update.zip there. but i cant because it read-only. How do i change any of these? Ive read 6 other posts on possible fixes none of which work.
Have you tried pressing the power button for 20 seconds and then restarting it?
nope
Yes i did that does not help.
adb says it cannot be root in production builds. I looked up how to do it but its either vague or makes no sense or does not work. why is it a production buold? it didnt do that when i rooted my fire in the first place so why is it doing it now?
What i believed happened is that when i went to past the andoid market's vending.apk into the system/app folder it deleted all of the things in the folder and nothing worked not even the GUI. I hard reset and then i got stuck at the logo. Dont know if that would clarify anything
that clariefys a lot - if you messed up your /system this should help you:
http://forum.xda-developers.com/showthread.php?t=1414832
then you should be able to install twrp
hopefully ...
Thanks but that did not help. It isnt recognized in adb like that.
Can you get into recovery? When you boot it up do you see FireFireFire at all?
No it says KindeFire and its animated.
sorry but i think you'll need a factory cable to get in fastboot mode
you'r not the first one ...
I have a micro usb and it works to connect (well until i followed that link and followed the instructions )
melmantheman said:
No it says KindeFire and its animated.
Click to expand...
Click to collapse
Hi,
Did you have a look at this too:
http://forum.xda-developers.com/showthread.php?t=1356257
I had quite the same issue with mine ...Device was not recognizable at all on Windows (unknown drivers)
I used this guide and it just worked like a charm.
regards
mjay
melmantheman said:
I have a micro usb and it works to connect (well until i followed that link and followed the instructions )
Click to expand...
Click to collapse
i think you did'nt understand what a factory cable is
it's a special cable which forces the kf in fastboot mode
you can build or buy one
make a search for "factory cable" and you'll know ...
http://forum.xda-developers.com/showpost.php?p=21151545&postcount=118
So I JUST got this thing today, and was trying to get android marketplace.
here is the list of things that have happened so far:
1. after moving vending.apk to apps folder, main GUI crashes and hitting the home button only switches through apps
2. decide to reboot since it is the next step for installing marketplace anyway
3. stuck in boot loop with shiny animations
4. manage to get TWRP installing
5. post says I need to hit 'reboot' on my kindle. I do.
6. stuck on yellow triangle, with all the drivers no longer working no matter what I do.
known fixes I've tried:
-uninstalling and reinstalling drivers
-rebooting computer and kindle multiple times
-selecting 'android driver' or whatever
-pressing the home button right after startup to try and get back into recovery mode
when looking in the device manager, it used to come up as 'kindle' with the yellow exclamation mark. now it only shows up as 'unknown device'
I JUST got this thing, and it wasn't from an official seller, so im basically on my own... anyone know what I should do?
EDIT: now the device manager IS saying 'android composite ADB interface' but it still wont how up in the kindle fire utility...
EDIT2: I was able to get it into restore mode, and get TWRP to pop up. I then have it clear the cache, and restored back to factory defaults. when I told it to reboot, it rebooted back to recovery mode. I then used the Kindle Fire Utility to set it to normal boot mode.
NOW, the problem im having is that it is stuck in a boot look with the animated 'kindle fire' logo.
Click to expand...
Click to collapse
Its working now! turns out that originally, all I needed to do was change the system permissions back to 755.
Do you have TWRP installed?
If so this link may be helpful to you. I've read a lot of jayceooi's stuff; he may be able to help you.
http://forum.xda-developers.com/showthread.php?t=1430446&highlight=jayceooi
ra0ultortugas said:
Do you have TWRP installed?
If so this link may be helpful to you. I've read a lot of jayceooi's stuff; he may be able to help you.
http://forum.xda-developers.com/showthread.php?t=1430446&highlight=jayceooi
Click to expand...
Click to collapse
Yes, I have twrp 2.0 installed. It had worked fine until yesterday.
have a .android folder in your home dir ?
should have adb_usb.ini in it with this entry: 0x1949 and 0x18D1 - if not add it
then it should show up in kfu
to test manually:
cd with an (elevated) command promt to the tools folder of kfu and do:
adb devices - should return serialnumber and bootmode
b63 said:
have a .android folder in your home dir ?
should have adb_usb.ini in it with this entry: 0x1949 and 0x18D1 - if not add it
then it should show up in kfu
to test manually:
cd with an (elevated) command promt to the tools folder of kfu and do:
adb devices - should return serialnumber and bootmode
Click to expand...
Click to collapse
When I went thru this procedure it says "list of devices attached"
and empty line (So no devices found).
I think my problem is drivers. Since my pc recognizes kf for several seconds only.
During those several seconds nothing really I can do.
Use the liux method. Worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038
wigsey said:
Use the liux method. Worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
thanks. will give it a try.
Hello,
I know there are many similar threads but i have a slightly different issue: I was editing /system/build.prop and did a reboot and i got stuck, right after the Kindle Fire logo pops up it goes black at the time the animation is supposed to start, computer reads it fine but ADB nor Fastboot will pick it up.KWRP also doesn't work, Any help?
IMPORTANT:
I have a backup of a TESTED and WORKING build.prop, if i can mount the Kindle in windows i will be able to apply the backup and fix it that way.
FYI:
I don't exactly care about keeping my data anymore, I just want it to turn on and be usable...
When you first try to power on the device and the amazon logo is still being displayed have you tried to get adb shell rooted or set it to recovery mode boot? Without the firefirefire bootloader it is going to be difficult to use adb unless you can at some point get adb to connect. Just out of curiosity, why didn't you also flash the boot loader instead of just flashing twrp? All I know to try is either kfu and keep hitting 0 to recheck device status and maybe you will get an Online+Rooted read out at some point before the system attempts to load & crashes.
linuxsociety said:
When you first try to power on the device and the amazon logo is still being displayed have you tried to get adb shell rooted or set it to recovery mode boot? Without the firefirefire bootloader it is going to be difficult to use adb unless you can at some point get adb to connect. Just out of curiosity, why didn't you also flash the boot loader instead of just flashing twrp? All I know to try is either kfu and keep hitting 0 to recheck device status and maybe you will get an Online+Rooted read out at some point before the system attempts to load & crashes.
Click to expand...
Click to collapse
I try to get into recovery mode, I'm not sure why i didn't use FireFireFire, this is my first tinker with an android device, I tried KFU from the instant i pressed power button to the black screen and its just unknown device. Is it broke for good?
I have a crazy idea and i have no idea if it will work, but it's worth a shot:
After reading the Kindle Fire breakdown, I think i can take the kindle apart and get access to it's internal SD, my questions is this: can I somehow plug it into a computer?
superbomb17 said:
I try to get into recovery mode, I'm not sure why i didn't use FireFireFire, this is my first tinker with an android device, I tried KFU from the instant i pressed power button to the black screen and its just unknown device. Is it broke for good?
Click to expand...
Click to collapse
So KFU is reporting unknown device? Sounds like you need to install the kindle fire USB drivers again. Is this on linux or on windows? unknown device means that it is recognizing a device, just doesn't know what device it is.. You need the correct drivers installed for the Kindle Fire, be sure to re-install those and try again.
When I was stuck on Fastboot I just reinstalled the Drives and then changed the boot over KFU.
Hausschuh said:
When I was stuck on Fastboot I just reinstalled the Drives and then changed the boot over KFU.
Click to expand...
Click to collapse
Did you try plugging it into another PC to see if that PC detects it?
superbomb17 said:
Hello,
I know there are many similar threads but i have a slightly different issue: I was editing /system/build.prop and did a reboot and i got stuck, right after the Kindle Fire logo pops up it goes black at the time the animation is supposed to start, computer reads it fine but ADB nor Fastboot will pick it up.KWRP also doesn't work, Any help?
IMPORTANT:
I have a backup of a TESTED and WORKING build.prop, if i can mount the Kindle in windows i will be able to apply the backup and fix it that way.
FYI:
I don't exactly care about keeping my data anymore, I just want it to turn on and be usable...
Click to expand...
Click to collapse
The fact that it goes black right after the kindle fire logo makes me think it's not stuck in fastboot (would be unlikely in a build prop edit) which is why you can't get fastboot to recognize; at the same time depending on where it's failing during the boot init adb won't load either.
superbomb17 said:
I have a crazy idea and i have no idea if it will work, but it's worth a shot:
After reading the Kindle Fire breakdown, I think i can take the kindle apart and get access to it's internal SD, my questions is this: can I somehow plug it into a computer?
Click to expand...
Click to collapse
First off; I seriously doubt you would be able to mount the sd from your PC properly. Rather than cracking the device I would try booting it from a factory cable, it should hopefully force fastboot mode at which point you should be able to resolve your issues.
***TL;DR AT THE BOTTOM***
*^*EDIT 2!!*^*
Utilizing Cerberus, I was able to get passed the boot animation into the lock screen, though the Launcher is, for all intents and purposes, nonexistent. However, I was able to install Nova Launcher and can go to a home screen just fine. THIS IS NOT SATISFACTORY. I want to get back to STOCK Launcher, but it apparently does not exist anymore. I've managed to copy over my backup of Launcher2.apk, but it still refuses to acknowledge its existence. Can I get an update.zip that'll reinstall the default launcher from someone? I can boot into recovery via ROM Manager now I suppose!
+++EDIT!+++
+++~~~I have discovered that my problem is not the device being stuck in boot up, but that the boot animation will not cease--as +in the device is actually powered on, just displaying the boot animation like a screen saver. I cannot boot into recovery as I get +the Google splash screen and it never goes anywhere, my bootloader is freezing every time I plug it into my computer, and the +drivers will not install. My computer cannot detect fastboot and I can't connect to the Nexus via adb either. I CAN access internal +storage but that's about the extent of what I can do.+++~~~
Long version:
I decided I wanted to change the App Drawer icon from stock to a Nexus X that inverted its colours when pressed. I found the icon, converted it to png, inverted the colours and everything was going fine.
After a while I finally managed to find the right icons to replace in the system apk file "launcher2.apk". "ic_allapps.png" and "ic_allapps_pressed.png" or something very similar. I simply replaced them with my two icons, installed my modified launcher2.apk, and that was it.
Immediately, my home wouldn't open at all, no matter how many times I pressed the home button. It just would not exit the app I had up. So I started backing and ended up in an infinite back loop. I powered off the device, waited a minute, and powered it back on.
It came to the usual "Google" screen with the unlocked symbol at the bottom, no problems. However, then it started playing the boot animation. The boot animation never stopped. It looped infinitely. I tried resetting the tablet a few times for the same result. It was after 3 am and I had to get up for work in 4 and a half hours. I thought that maybe it was gonna take a while. So I flipped the Nexus over while it was "booting up" and went to sleep.
When I woke up and checked the tablet at 7:30, it was STILL booting up. Obviously I had screwed something up.
Now, stupid me, I had never flashed CWM recovery on my Nexus 7 (haven't had it that long), so all I'm stuck with is STOCK Recovery. I'm pretty sure I can rescue the Nexus by factory resetting it or something similar, but I'd rather try to save it first. All I modified was a LAUNCHER application, so I'm pretty sure the current state of the Nexus itself shouldn't be too far gone. Is there any way to save the Nexus WITHOUT a data wipe? And if the data wipe DOESN'T fix my problem, is it possible to somehow flash a stock ROM through stock Android Recovery?
***TL;DR***
I modified launcher2.apk and replaced "ic_allapps.png" and "ic_allapps_pressed.png" with two customized .png files (which I renamed to their appropriate file names). Now my Nexus is stuck on the boot animation indefinitely. I would like to save all of my data, as a data wipe would be inconvenient, but if I must do one I shall. I am on a stock ROM and a stock Recovery. If a data wipe/factory reset will not save my device, is it possible to flash a stock ROM through regular Android Recovery?
===Related but irrelevant to the problem===
Is it completely impossible to change the stock App Drawer icon to something different? I'd rather not have to get a different launcher app just to create a Nexus theme! I did a little more research and found that I should've modified the "all_apps_button_icon.xml" file as well, but I have NO idea how to do that.
Many thanks,
VonDerThWood.
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
NeoMagus said:
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
Click to expand...
Click to collapse
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
simms22 said:
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
Click to expand...
Click to collapse
How can I reflash the ROM on stock Android recovery? Googling that returns CWM results.
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
NeoMagus said:
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
Click to expand...
Click to collapse
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
If you don't have fastboot set up you might want to give this post a look he describes how to get it set up.
simms22 said:
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
Click to expand...
Click to collapse
I don't use custom recoveries and backup my data regularly with Titanium, so restoring after a reflash is really just an afterthought here, to each there own
The problem is not as it seems.
When I plug the Nexus into the computer when in Fastboot mode, it freezes the Recovery. I cannot select anything OR move the selection to anything else. The hell?
I noticed that when the Nexus attempts to boot up, the boot animation gets brighter.
__
Wait, when it attempted to boot up when plugged into my PC, AutoPlay recognized the device as Nexus 7. There is nothing on my screen but the boot animation, however I can browse internal storage.
I cannot, however, connect to it via adb apparently. ADB devices returns nothing.
____
Okay, the problem is NOWHERE near what I thought it was. The boot animation is replacing the lock screen/home screen/everything. I just received an email (I could tell because of the notification noise the tablet made). It is booting up, just not displaying anything passed the boot animation and ADB cannot detect the device. I KNOW it has USB Debugging mode activated and all, but what can I do now?
===
I usually make backups and nandroids but I've barely owned this device. ;P
Does fastboot detect the device?
janedoesmith said:
Does fastboot detect the device?
Click to expand...
Click to collapse
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
VonDerThWood said:
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Click to expand...
Click to collapse
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
NeoMagus said:
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
Click to expand...
Click to collapse
Fastboot has the "Recovery mode" option but it just gives me the Google logo with the unlocked icon at the bottom indefinitely...which means I cannot access recovery either? Why didn't I notice this before? >_<
simms22 said:
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
Click to expand...
Click to collapse
Tried 10 times by booting into bootloader first, then 10 times by plugging it in and booting into it while it's plugged in. This is a very...odd bug.
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
it is an odd bug. i think every n7 owner who likes to flash roms/kernels has had to deal with it at least once.
VonDerThWood said:
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
Click to expand...
Click to collapse
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
janedoesmith said:
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
Click to expand...
Click to collapse
Now that I think about it, it DID say something about failing to install an unknown driver the first time I plugged it in. Let me uninstall/reinstall the drivers.
____
After reinstalling the drivers (and removing both of the Nexus7 specific ones), I also removed one named "Android", which, coincidentally, is the driver that the tablet is trying to install upon being plugged in. I have tried to reinstall it several times, but it fails each time, AND I just reinstalled the real Nexus 7 drivers.
___
The Nexus drivers won't reinstall now. I even went to Asus's website and downloaded them, but I have no clue how to install it in this format.
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Whoa! Stroke of GENIUS!
I have Cerberus installed on my tablet. Since I know the tablet is booting up, just not displaying passed the boot animation, I decided to give it a try.
I started an alarm, which forced the tablet to the lock screen...I can open apps through the Play Store (as I got an update notification) and the like, but I can NOT get to the home screen.
I opened Total Commander via Play Store, but I can't do anything with it. The app that I used was NinjaMorph and I'm pretty sure the only way I can correct my mistake is through that app. What do I do?
Found NinjaMorph in the Play Store, it couldn't fix my problem. Oh hell.
I tried to copy/replace the launcher2.apk file I screwed up with a backed up one but TotalCommander couldn't do it. It was even granted SuperUser permissions. Attempting with Root Explorer.
Success! I have copied the original Launcher2.apk back into the /system/app folder. HOWEVER, I can NOT install it.
Managed to connect via adb! Things are looking up! Now, how to install this stuff...?
When trying to reinstall the launcher2.apk, it gives me the following error:
INSTALL_FAILED_UID_CHANGED
So I tried uninstalling it to no avail. Troubling.
SO! Now what? I am into the device, and any app I have downloaded through the Play Store is available to me, but I cannot go to the home screen. I need to reinstall the original Launcher2.apk!
Retrying NinjaMorph. It supposedly installed my Launcher2.apk. However, I still cannot return to the Home screen. WTF.
I'm going to install a different Launcher. Hope that works!
Success. I can now return home to Nova Launcher. HOWEVER...
This is not satisfactory. I want my STOCK launcher. Anybody know how I can fix this? The stock launcher is acting like it doesn't exist anymore. Is there a way to just wipe THAT data and keep all the other data on my device?? (Though I admit, I do like how I already was able to change my App drawer icon to my Nexus X <3.)
Edit: I see you resolved it. Good job! I'll just leave this here... :good:
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Click to expand...
Click to collapse
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
comminus said:
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
Click to expand...
Click to collapse
I managed to get ADB working (via adbWireless) after the above post I made, however I cannot get launcher2.apk to install. This time I got the "INSTALL_FAILED_DEXOPT" error instead of the "INSTALL_FAILED_UID_CHANGED" one.