Database Users

[q] nexus 7 not booting

Hi All
I've been trying to update to JB 4.2, I used the auto update feature in the nexus but it kept failing to install! I then resorted to using ADB/SDK (only started using it yesterday so an extreme novice) to try and flash to JB 4.2, still it did not work.
Something went wrong when trying to flash as my nexus gets stuck on GOOGLE writing when booting up!! I'm using adb sideload with a factory image.tgz but it loads sideload to 100% in the command window (my nexus is in adb mode at this point) my nexus receives the files then says it's verifying update package, then says installation aborted!!!
Not sure what to do, really stuck, any help appreciated...:crying:

[Q] Rooted Nexus 4 refuses to encrypt. Resets itself.

I cannot use the default "Encrypt Phone" option on the settings menu of my Nexus 4. When used, it just reboots the phone and I have done this process over 5 times with no success.
I used the Android Nexus 4 ToolKitv2.0.0 and the recommended root tools and am running obviously 4.2.2.
Any reason why it's doing this? Thanks.

Bubblewhip said:
I cannot use the default "Encrypt Phone" option on the settings menu of my Nexus 4. When used, it just reboots the phone and I have done this process over 5 times with no success.
I used the Android Nexus 4 ToolKitv2.0.0 and the recommended root tools and am running obviously 4.2.2.
Any reason why it's doing this? Thanks.
Click to expand...
Click to collapse
Are you using a custom recovery - TWRP or CWM? You need to be using the stock recovery image to encrypt your phone. The nexus toolkit will allow you to re-flash the stock recovery.
One the stock recovery has been re-flashed, you should be able to encrypt your phone. I had to re-flash stock recovery, reboot the phone, then reflash the stock recovery again.
Once the device has been successfully encrypted using the stock recovery, you can re-flash either the TWRP or CWM as your recovery. TWRP supports reading data from encrypted devices, so it is probably the way to go (not sure if CWM dows now, but it didn't last time I looked).

Does encrypting the phone make a dramatic difference in speed (as in slow down) for the phone or does it mainly affect boot times?
Thanks for the tip about having stock recovery as I also wanted to encrypt phone as well. Would one have to de-encrypt phone then install custom recovery to update a custom Rom (I'm running paranoid android) then flash to stock recovery to encrypt phone again- seems long winded :-\
Just from reading the above post once flashed to stock recovery and then encrypted device, it's okay to flash back to TWRP and still have an encrypted device?
Is there another way to do this when running a custom rom?
Sent from my Nexus 4

randomvector said:
Does encrypting the phone make a dramatic difference in speed (as in slow down) for the phone or does it mainly affect boot times?
Thanks for the tip about having stock recovery as I also wanted to encrypt phone as well. Would one have to de-encrypt phone then install custom recovery to update a custom Rom (I'm running paranoid android) then flash to stock recovery to encrypt phone again- seems long winded :-\
Just from reading the above post once flashed to stock recovery and then encrypted device, it's okay to flash back to TWRP and still have an encrypted device?
Is there another way to do this when running a custom rom?
Sent from my Nexus 4
Click to expand...
Click to collapse
I haven't noticed a difference in speed, however technically there will be a little bit of a slowdown.
I'm running stock Android, so I don't know how well it plays with custom ROMs, but you can re-flash a TWRP recovery after encrypting your phone with stock Android on it.
If the custom ROM installation wipes the data partition, it would remove the encryption.

I've tried flashing stock recovery using Nexus 4 Toolkit and recovery is back to stock. However the phone is still just rebooting when I press encrypt device. What am I doing wrong?

For some reason I had to reflash the stock recovery, reboot, then reflash the stock recovery again. No idea why, but it worked for me!
Sent from my Nexus 4 using Tapatalk 2

Booted back into stock recovery device is still rebooting itself after hitting the encrypt button, Encryption did not happen.

Found the problem but I can't seem to fix it. Flashing the stock recovery doesn't seem to actually do it. When I boot to recovery when flashed to stock, it just shows the android mascot with an open chest and a warning symbol. Have reflashed many times over 5, and still doesn't work. It seems like I need the actual image recovery file. something like Recovery.img?

Bubblewhip said:
Found the problem but I can't seem to fix it. Flashing the stock recovery doesn't seem to actually do it. When I boot to recovery when flashed to stock, it just shows the android mascot with an open chest and a warning symbol. Have reflashed many times over 5, and still doesn't work. It seems like I need the actual image recovery file. something like Recovery.img?
Click to expand...
Click to collapse
The android with a warning symbol is the normal symbol of stock recovery.
However, I wonder, if you could solve the problem? My nexus doesn't want to encrypt itself too. Flashed stock recovery already twice and it just keeps rebooting when I start the encryption process.

Quick update: After trying it several times in a row it finally worked (after the fourth time or so). I have no clue why it didn't work before as I haven't change anything.

c_m_l said:
Quick update: After trying it several times in a row it finally worked (after the fourth time or so). I have no clue why it didn't work before as I haven't change anything.
Click to expand...
Click to collapse
Thanks for your perseverance! I spent half a day trying to encrypt my rooted Galaxy S4 with the similar problem as you:
I go into System Settings, click "Encrypt Phone", then I get the green android and the phone just reboots itself as normal.
What worked for me: AIRPLANE MODE.
I was rebooting it time after time with no effect (following your suggestion). Once I turned on the Airplane Mode, the encryption started working.
My Current Setup:
Android 4.2.2 Jelly Bean
Samsung Galaxy S4 Google Edition (GT-I9505g) rooted via CF auto root. + Full disk encryption!
Works perfectly!
Now I can have different passwords for disk encryption (long strong password) and for locker screen (simple)

JohnnyBBB said:
Thanks for your perseverance! I spent half a day trying to encrypt my rooted Galaxy S4 with the similar problem as you:
I go into System Settings, click "Encrypt Phone", then I get the green android and the phone just reboots itself as normal.
What worked for me: AIRPLANE MODE.
I was rebooting it time after time with no effect (following your suggestion). Once I turned on the Airplane Mode, the encryption started working.
My Current Setup:
Android 4.2.2 Jelly Bean
Samsung Galaxy S4 Google Edition (GT-I9505g) rooted via CF auto root. + Full disk encryption!
Works perfectly!
Now I can have different passwords for disk encryption (long strong password) and for locker screen (simple)
Click to expand...
Click to collapse
Old thread, same issue, HTC One w/ OmniROM (m7att). My Nexus 10 did it as well.
The person saying to reflash stock? DOn't listen to that. Doesn't need to be done. Encrypted all my devices w/ TWRP installed.
Airplane mode DID work, though.

I just had this issue with my N4, too. I read on the Google Product Forum that this was because a process prevents from unmounting the /data partition. ("Nexus 5 is not going through encryption process" - can't post link due to being new)
With that in mind, I rebooted into safe mode and then tried again and it worked on the first try (At least it started the encryption process, it's at 10% now)

I had this problem for a looooong time. Thankfully, I seem to have discovered a solution for those still encountering this issue.
Turn off SuperSU (Settings -> More -> Application manager -> All -> SuperSU -> Turn Off)
Reboot into Safe Mode (How to)
Run encryption (Settings -> More -> Security -> Encrypt Device)
Turn on SuperSU after complete (Settings -> More - > Application manager -> Turned Off -> SuperSU -> Turn On)

[Q] Nenus 4 not recognized on PC????

I rooted my nexus 4 on 4.2 with no problems.
I then upgraded to 4.2.2 while temporary unrooting with voodoo OTA rootkeeper then restored root and everything worked ok.
Now recently my Nexus 4 does not show up anywhere on my laptop but charges ok.
I have downloaded the latest toolkit V2.0.0 and installed the drivers (option 1) and it says they install.
In device manager I have an exclamation mark next to both google nexus 4 ADB interface and also both BootLoader Interface tabs.
Im totally stuck and dont know what to do.
Usb debugging is on, MTP is checked
If i do a factory reset on my phone, will it take it back to 4.2 unrooted like when i bought it and give me no problems?
I would be grateful for any help

Doing factory reset doesn't erase root.
Sent from my Nexus 4 using Tapatalk 2

Paul203360 said:
I rooted my nexus 4 on 4.2 with no problems.
I then upgraded to 4.2.2 while temporary unrooting with voodoo OTA rootkeeper then restored root and everything worked ok.
Now recently my Nexus 4 does not show up anywhere on my laptop but charges ok.
I have downloaded the latest toolkit V2.0.0 and installed the drivers (option 1) and it says they install.
In device manager I have an exclamation mark next to both google nexus 4 ADB interface and also both BootLoader Interface tabs.
Im totally stuck and dont know what to do.
Usb debugging is on, MTP is checked
If i do a factory reset on my phone, will it take it back to 4.2 unrooted like when i bought it and give me no problems?
I would be grateful for any help
Click to expand...
Click to collapse
Even I had similar problem in my N4.
Try re-installing the drivers of N4. :good:
I also did that when my phone stops recognizing after flashing rom.

I have tried this but its still not working.

Can I roll back to 4.2 without connecting to PC?

Trouble In Paradise

First time poster here.....in DESPERATE need of help!
So here's the rundown: After many attempts, I was finally able to update to KitKat 4.4.2 on my G2 with root intact. I wanted this for flashing the camera for 4k and 120fps modes. I attempted to install it today via TWRP but now I've basically bricked my phone.
Here's what I did:
- Installed FreeGee
- From inside FreeGee, I installed TWRP
- Installed TWRP Manager
- Copied .zip file to sdcard
- Booted into recovery mode
- Installed camera update
- Restarted and got a neverending LG Logo screen
I have since attempted every which way to recover from this. At this point, I don't even care about my data, I just want a working phone back! I am receiving no errors other than a frozen logo screen.
Here's what I've tried thus far with no success:
- ADB sideload (said phone was connected, got the dreaded "cannot read file" error no matter what I did).
- Factory reset
- Custom wipe of all but sdcard data
- LGFlashTools attempt to restore back down to 4.2.2 "o".....phone will not connect (read more below)
- Attempted fastboot flash from CMD prompt, just said "waiting for phone" forever
Some information......I CANNOT get the phone to be recognized on my PC when in "Download Mode". It never moves past the small Download Mode label into the "Firmware Update" with the big circular arrows circle. If I am in TWRP Recovery (which I get to by holding the Power and Volume Down button [original factory reset]), the PC does recognize the phone, but only under a new label called Android Phone, not Ports. I cannot change the COM ports at all as there is no option given under Properties.
I am at my wits end here. Any idea what I can do? It still appears to function normally under TWRP interface, but outside of that it's a brick. Please please PRETTY Please, anyone been in this situation and know what to do?
Thanks for any guidance.

Just wanted to give everybody an update here in case someone else is in the same situation.
So Sideload REFUSED to work even with the correct names typed. So I scratched that approach.
I anded up using the adb "push" method to send the zip file to the phone. I was having so much trouble with it at first, but I realized that was because I was going into sideload mode on the phone! You DO NOT turn on the sideload mode in TWRP if trying to push a file to the phone. You simply need the device recognized in the command prompt "adb devices" to say "23908hjf982j0e8jdf2 RECOVERY", or something to that effect. If you have sideload mode turned on, you will get the error, "error: closed". Well duh, it's closed for a sideload function! I should have caught this earlier.
ANYWAY, once I pushed a CyanogenMod 11 rom to the phone, it installed and booted right up! I didn't like it, however and wanted to go back to stock 4.2.2. So I downloaded the stock LG Jellybean rom and attempted to install it but it failed. Not sure why. I then downloaded KitKat 4.4.2 and installed it but that also failed, and this time it REALLY bricked it. I was getting loading errors on the LG Logo screen and it would shut off and act like it was turned off. At this point, I tried to restore to CyanogenMod from TWRP recovery, but it didn't work. Go figure.
I had a bricked phone. It wouldn't even boot into TWRP anymore due to the stock rom being partially installed (but failed).
Just when I thought all was lost, I attempted the old LGFlashTool reboot. I figured that maybe, just MAYBE....the Download Mode was fixed due to the partially installed stock ROM. I was right! I cleared all my old testing/configuration drivers on my PC and reinstalled the stock LGUnitedMobile 3.10.1 drivers, set the phone to download mode and VOILA! It FINALLY popped under a newly showing PORTS (COM & LPT) in my device manager. I configured it to COM41 as needed, configured LGFlashTool to load up the stock 4.2.2. jeallybean ROM, put the phone into Download Mode once again and LGFlashTool FINALLY recognized it and loaded up the stock ROM as it did the other day I tried it.
I am now on 4.2.2. rooted "q" (updated from "o" to "q" after installing SuperSU Pro and checked the Survival Mode option). I am moving up to KitKat 4.4.2. with Survival Mode on, which will keep my Root ability (Yes, it DOES work and have already verified it worked before all hell broke lose due to the xdabbeb's update on 4.4.2. (I probably did something wrong....not saying it's his fault!).
Anyway, just thought I would post this so that it may help someone else out.
Peace out gents.

goodlookin1 said:
I am now on 4.2.2. rooted "q" (updated from "o" to "q" after installing SuperSU Pro and checked the Survival Mode option). I am moving up to KitKat 4.4.2. with Survival Mode on, which will keep my Root ability (Yes, it DOES work and have already verified it worked before all hell broke lose due to the xdabbeb's update on 4.4.2. (I probably did something wrong....not saying it's his fault!).
Anyway, just thought I would post this so that it may help someone else out.
Peace out gents.
Click to expand...
Click to collapse
If you eventually want to have recovery as well you'll need to go back to 10d as later versions (o,q) break loki and are not compatible with the custom kernel needed to load stock based KK roms. But if you just want root until the next ota you're set.

I tried to flash xdabbebs mod on KK using flash gordon flasher and it worked fine for me.. http://forum.xda-developers.com/showthread.php?t=2250555
Sent from my LG-D800 using XDA Premium 4 mobile app

Trying To Recovery N10 (old version).

Hi guys,
I have searched around the forums and still unsure, weary of what to do. I got my nexus when they first came out. I used it for a while and eventually unlocked it so that i could get certain apps that needed root access. I dont think i flashed a custom rom on it though. I havnt updated android to 4.4 yet. Its been a long time since i updated anything. Hence the start of my dilemma. I went to backup my tablet. It told me SuperUser or the bootloader needed to be updated. So im like oh fine update. Tablet then restarts brings me to my boot screen and says downloading target do not turn off. Its been stuck like this and nothing happens. I held down the power and rocker buttons and got back to boot option screen. Here's where im lost and dont remember what to do. I have tried start, recovermode, restartbootloader, and nothing seems to work. They all bring me back to the dead little android guy ​
Here's the device info.
product name: manta
variant: wifi
h/w version 8
bootloader version: mantam03
carrier info: none
serial: ****
lock state: unlocked
reboot mode flag: recovery
I slightly recall when i first unlocked it using twrp or clockworkmod? I could be wrong. Either way i no longer have the rootkit nor the computer i originally used to unlock it. What software do i need to install to get me back up and running. I was worried i may brick it if i installed the wrong version kit. That maybe newer version wouldn't work with my n10 because it was running an old version. Any advice would be much appreciated.

Jshannon22 said:
... I was worried i may brick it if i installed the wrong version kit. That maybe newer version wouldn't work with my n10 because it was running an old version. Any advice would be much appreciated.
Click to expand...
Click to collapse
Considering that you have not used the N10 in a very long time your user data may not be all that important so here are some options.
1) You could flash the factory image for Android 5 which will wipe out your user data but give you a clean system including stock recovery.
2) You could flash the factory image for Android 5 but first you need to change the "flash-all".(bat,sh) script by removing the "-w" option which will prevent your userdata from being wiped. That takes some knowledge to edit the script but all you need is a simple text editor.
After either of those options you can root and replace your recovery. Root before you change your recovery or you will run into an issue due to specific changes in Android 5.
Instructions for installing a factory image.
Nexus 10 lollipop factory image.
How to install Android Lollipop factory image on Nexus 5, 7 and 10 (and keep your data)
Good Luck

I'm having similar issues! When trying to install lollipop over sideload it always errors and states not enough space.
I've formated all the data so I'm at a loss.
Any ideas to install lollipop?
Sent from my Galaxy Nexus using XDA Free mobile app

I'm concerned I've bricked the device. To be honest I'd be happy just to get kitkat back!
When the device powers up it automatically goes into a "no command" bootloop. With the android on its side with an exclamation point sign coming out.
Holding power and the volume it then goes to the android recovery where I have four options: reboot, apply update from adb, factory reset, wipe cache.
When in command, typing adb devices shows my device.
Using adb sideload I've tried to update, but I always get the error "creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip
status 7 installation aborted"
So I downloaded the kitkat image and tried to run the script "flash all". But then the command screen just says "waiting for device"
After all that failed, I tried to hold power and the volume button when it restarts. That takes me to the odin screen, where it just states "downloading, do not remove target" The volume buttons do nothing. pressing the power button just reboots.
Any help would be much appreciated!

I have the same issue. There does not seem to be a way to install any (old) version of android. All I get is the same error message "creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip status 7 installation aborted"
I did not root my device nor did I install a custom rom. I just started installing the OTA update and that's when the tablet got stuck in the boot loop thingy.
I also searched the internet and all I found were similar instructions on how to install factory images etc. using adb sideload.... as I mentioned, following those instructions lead to the error message.
I can' believe this.
Thanks for your help

I also have similar issue. I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device. As novice even I do not know to install ADB sideloaded.
Can you suggest how best I can revive N10?
Regards,

Guys,
I also had the exact problem. What finally worked for is to flash custom recovery (TWRP latest version) with "fastboot flash recovery <recovery.img>" command.
Then from the recovery I installed custom ROM (http://forum.xda-developers.com/showthread.php?t=1998585), as the official ROM also failed.
Hope it will help someone.

Shleim, this seems to just have worked out fine. Many thanks for your help!
I'm still kinda wondering why it wouldn't work with the official ROM. In any case, this is by far better than having a bricked tablet and at least now I know it still works.
Awesome, thanks for this tip!!!

fliuwoek said:
Shleim, this seems to just have worked out fine. Many thanks for your help!
I'm still kinda wondering why it wouldn't work with the official ROM. In any case, this is by far better than having a bricked tablet and at least now I know it still works.
Awesome, thanks for this tip!!!
Click to expand...
Click to collapse
No worries, glad it helped you.