I was running CM 10.1.3 with no issues. I was attempting to connect my Exchange E-mail account and it said that it needed to encrypt the files, not a big deal, I have had to do this in the past. It starts to do its thing but I see no progress bar like I am used to, just the CM logo spinning. I thought there was a problem and restarted the phone (big mistake) and now I am getting a message that there was an Encryption Error and it tells me to reboot the phone and then reformat. It reboots but goes right back to the message. I boot into recovery mode and attempt to load the .zip from SD card. I get an error "E: can't mound/sdcard". So I'm thinking I need to sideload instead. I download the SDK per some instructions on the internet, install the platform-tools and the USB drivers. I think everything is where it needs to be, I connect the phone, find the ADB.exe file, run a command prompt, type ADB devices but I get nothing.
Please let me know where to go from here!!!
Thanks in advance!
Bump for some ideas for this guy.
Resolved!
Related
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.
As the title says, I wanted to try CM installer, and I was on everything stock, not rooted. I downloaded PC, and android programs, followed the instructions, however at one point CM installer on my PC said it cannot communicate with my phone, and it was when it was trying to flash recovery. It said I should try different cable, or USB port, but no luck with either, and now it says my phone is not supported.
I tried to enter recovery, but I only get CM guy and it's stuck, even when I turn off the phone, it turns itself on automatically, and to fully turn it off I need to enter fastboot mode, and then turn off. I tried flashing full stock image (I know how to do that, and I have previous experience on this phone), but my fastboot crashes (Fastboot.exe Has stoped Working), tried to download fastboot again, but nothing helped. I also tried to flash recovery only, and I get the same thing... Also tried to do that with custom recovery, but nothing....
Is there something I can do, or do I need a new phone?
Also, I had like 70% battery when I started, so I am afraid to keep trying, cause if I go out of juice, it's game over, right?
Looks more like issues with your pc communicating with your device, which might have causes other side effects due to that. But I have not tried CM Installer yet.
You should see about getting fastboot working correctly first and getting the right adb/fastboot driver (such as latest Universal Naked Driver, link in my sig). You should also use the latest adb/fastboot .exe from Google, download their latest ADT package. If it still crash, use it on a different machine, if you're on Windows 8 try Windows 7 or Ubuntu.
Also make sure the factory image isn't corrupt, I always have issues downloading it from Google.
Also, I had like 70% battery when I started, so I am afraid to keep trying, cause if I go out of juice, it's game over, right?
Click to expand...
Click to collapse
If the battery goes to 0%, just charge it, do you think everyone throw away their N4 when the battery goes to 0? There is the red light problem, but its an easy fix.
Thanks for answering, I fixed it with a strange method (to me). On CM forum j_cor told me this:
"Your device appears to be stuck in sideload. So the good news is no, you are not bricked. Here is what I would try to do:
1. Boot the device - wait for the "stuck" CM guy to display
2. Plug phone to PC and open a command prompt to the directory to C:\Users\enter_your_name\cminstaller\bundle\win32
3. from the prompt "C:\Users\enter_your_name\cminstaller\bundle\win32>" type "adb.exe sideload ClockwordMod.cer" (no quotes) and hit enter
4. This will try and sideload this .cer file and will fail - but it should kick you out to the main recovery screen. Select the Reboot option from Recovery
5. Device should boot back up. It will most likely still be the stock ROM. My guess would be that something disrupted the sideload process when installing the system.zip with CM."
However, this did not fix my problem, but it got my phone to communicate with fastboot. So I was able to flash custom recovery, and do a factory reset, which brought me to the stock ROM, I flashed CM the old-fashioned way then.....
And my PHONE IS UP AND WORKING AGAIN!!!
The main problem in communication was that phone blocked every time I booted into fastboot, and plugged USB cable in.... It immediately became unresponsive to any commands, after I did this, phone wasn't getting stuck in fastboot, so that solved my issue.
Hi all, I'm having problems with my Nexus 4.
I'm on CyanKang & (tried to, it said it had an error & aborted the installation) installed a nightly build which wasn't quite right - must've gotten garbled when downloading or something. Point is, my phone is stuck in a boot loop.
As it's only a 8GB one, I, somewhat stupidly, didn't keep any stable versions of the ROM I was using or backups on the device.
Now I've downloaded a stable version of the ROM but the problem is I have no way of getting the .zip onto the device. It doesn't mount on my computer & according to adb, it's unauthorised & doesn't bring up the authorisation dialogue to let me grant it authorisation. Killing & restarting adb server & unplugging & plugging in the phone again didn't make a difference.
I'm a bit lost as to what I can do to get my phone working again.
Thanks in advance.
Fixed my problem - cleared my personal data on the device which deleted the adb key. Then flashed a working boot.img with fastboot which let me authorise adb & push an update file to my phone which I could flash in recovery
Hi all, the other night i went to be and my phone woke us up making a ticking noise. i looked at the screen to find it suddenly asking for a password/pin to decrypt. i have NEVER encrypted or even looked at the menu to encrypt my phone. the phone is also completely stock from verizon, although as i understand the vzw variant claims to be rooted. i do not have a pass or pin to unlock. it also says i have 0/10 attempts left to enter my pass/pin. if i enter one at random, the attempts remaining changesto 1/10. this seems backwards to me. if i enter any more false passwords the number does no go up or down anymore. i can access the hard factory reset screen by using the vol down +power key combo but when i confirm the device to wipe i get e cannot mount cahce and e cannot open cahce log. it also says unknown error 150. if i try to wipe cache it says the same thing. i tried to use the sideload from adb option and my computer recognizes an adb connection but it only allows me to run the adb sideload command, which fails due to the mounting errors as well. if i try to run any other adb commands it immediately says "closed" in my command prompt. i cannot load any images from sd card either since the phone has no sd card slot and i cannot access the internal storage in any way ive tried. i went to use the lg flash tool to try and just flash a new image and everything goes fine until the 15 or 16 second mark and then it tells me it fails because the erase command is unsuccessful.
im getting ready to send it in to lg or verizon but i just hate being beaten by such a mysterious problem. can it not mount or give me access to overwrite with the flash tool because of encryption? or is it "encrypted" due to a faulty chip causing an issue? its weird that it can still boot to this pass/pin screen, it has the standard soft keys on bottom of the screen, so it looks like th UI is actually still being recognized. also, i am/was connected to a corporate exchange server but we have never had a policy in place to require encryption and there is another android user in our office who has not had this happen. i am the tech guy and i have verified this. can anyone help me at least understand what the problem might be? i just hate not knowing, even if i still have to send it in. is it truly hardware? or is it just software gone crazy?
This is to say good bye to my beloved One Plus One bacon.
It started with the clock quitting its service. Suggestion do a factory reset.
I backed up all what TEAMWARE was offering and did the reset. Restored my backup, everything worked well no error messages what so ever.
But the phone didn't boot. The blue android symbol came up and flashed, the phone got hot but no prevail. All attempts to get back into recovery failed. But the phone went into fastboot mode. ADB devices test from a computer isn't finding the phone.
Has anybody any idea? Thanks
Geridhenner said:
This is to say good bye to my beloved One Plus One bacon.
It started with the clock quitting its service. Suggestion do a factory reset.
I backed up all what TEAMWARE was offering and did the reset. Restored my backup, everything worked well no error messages what so ever.
But the phone didn't boot. The blue android symbol came up and flashed, the phone got hot but no prevail. All attempts to get back into recovery failed. But the phone went into fastboot mode. ADB devices test from a computer isn't finding the phone.
Has anybody any idea? Thanks
Click to expand...
Click to collapse
If your phone is going in fastboot mode, use 'fastboot devices' to look for the phone after connecting to computer, not 'adb devices'. They are two separate modes/protocols. If you don't have the 'fastboot' executable, google "minimal adb and fastboot" and download it. Hopefully your computer will install drivers automatically.
Once in fastboot mode, and connected and detected properly, just download the "signed fastboot" image from cyngn.com (go to support) and follow steps in item number 8 on this link