Database Users

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.

Nexus 4 lollipop OTA fail [Solved]

Hi,
I recently tried to update my stock encyrpted Nexus 4 using the OTA Lollipop update. Now when I try to start the phone I can get past the decryption unlock screen as usual, but after that it gets perpetually stuck in the spinning circles sequence. Unfortunately, I have not backed up my data and would like to retrieve it if possible (I thought the backup to cloud feature was enabled, but I guess it wasn't...). I've tried pushing the official Lollipop update using adb sideload; everything seems to work fine (it unpacks and installs without any errors), but when I reboot the phone I still have the exact same problem as before.
Can anyone think of anything that I can do to recover my files? I'm holding out hope that my photos are still on the phone and can be recovered somehow.
Thanks!

I cannot update the software after recovering from softbrick

I originally had OOS3.0.2, and I tried to get Beanstalk rom installed. Beanstalk didn't load correctly, and I softbricked my phone. I managed to go through the recovery of downloading the qualcomm drivers and that weird updating program and then sideload an older version of OOS (2.2). I went to this link and did method 1 https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/. But when I get things fixed up, I can't seem to update to CM13, or even to do a normal update with root, without root, with twrp, without twrp. Nothing. Strangely enough, no matter what I've been doing, the data I had from the very original pre-screw-up time is still all there. Every time I try an update it hangs on the 1+ screen and stays there. How can I get past this? I can't seem to upgrade, and I'm stuck in lollipop.

Well I was still able to get into my phone and do a stock recovery from the Update and Restore option from the phones settings menu, so that fixed it.

Bootloop after O install

Rooted 6P on stock ROM. Today I got a System update notification. Ignored it, went to Google OTA download location, downloaded the O OTA and attempted to install via Flashify. When the phone rebooted it was in a bootloop. Downloaded OTA to my PC at home, side loaded via ADB and attempted to install via TWRP, failed with Error 7. I then edited the install file to remove the "asserts" from the install script. the script installed seemingly OK but the phone again went into a bootloop. At this point I have re-installed N. Anyone seen that or has suggestions? There is a thread on the Google product forums where a number of people are reporting similar behavior. As usual Google is not responding. They truly are becoming the Microsoft of the early 90s - too fat, too rich, and extremely arrogant.
UPDATE: after downgrading to N (and loosing root in the process since I simply flashed the OTA) I attempted to just take the O update straight from Google as a system update. Everything went without error messages until the reboot, now in a bootloop for the last 5 minutes. Will give it another 5 and then downgrade permanently to N until Google fixes their mess three updates from now. Yup, three updates, just as many as Microsoft used to need to get things right.

GroovyGeek said:
Rooted 6P on stock ROM. Today I got a System update notification. Ignored it, went to Google OTA download location, downloaded the O OTA and attempted to install via Flashify. When the phone rebooted it was in a bootloop. Downloaded OTA to my PC at home, side loaded via ADB and attempted to install via TWRP, failed with Error 7. I then edited the install file to remove the "asserts" from the install script. the script installed seemingly OK but the phone again went into a bootloop. At this point I have re-installed N. Anyone seen that or has suggestions? There is a thread on the Google product forums where a number of people are reporting similar behavior. As usual Google is not responding. They truly are becoming the Microsoft of the early 90s - too fat, too rich, and extremely arrogant.
UPDATE: after downgrading to N (and loosing root in the process since I simply flashed the OTA) I attempted to just take the O update straight from Google as a system update. Everything went without error messages until the reboot, now in a bootloop for the last 5 minutes. Will give it another 5 and then downgrade permanently to N until Google fixes their mess three updates from now. Yup, three updates, just as many as Microsoft used to need to get things right.
Click to expand...
Click to collapse
Since it's a new version, I downloaded the factory image and flashed everything via fastboot. No problems. In fact, every time I have a problem using flashify or down grading, flashing via fastboot solves everything. Maybe you ought to try doing that.

The OTA file seems to be structurally very different from the N files. There are a bunch of files I have not seen before in N OTAs - bootloader.cmnlib, bootloader.hyp, bootloader.keymaster - the list goes on and on. I am going to have to read up on what to flash and what not to, since the potential to brick the device is significant.

GroovyGeek said:
The OTA file seems to be structurally very different from the N files. There are a bunch of files I have not seen before in N OTAs - bootloader.cmnlib, bootloader.hyp, bootloader.keymaster - the list goes on and on. I am going to have to read up on what to flash and what not to, since the potential to brick the device is significant.
Click to expand...
Click to collapse
I'm sorry to say this, but it's probably down to operator error. Making mistakes is just part of the learning process. Just use the full Google image and be done with it. Don't use OTA with Flashify or TWRP. You could have used flash-all.bat with the -w switch removed to leave your data intact, or used the full image with Flashfire retaining root and TWRP. FF makes life very easy, especially when the security updates come monthly.

Yes, this was my mistake. Flashify was messing up for whatever reason, the flashing via fastboot from the full factory image went through fine. I had not done it for a while since Flashify seemed to be doing a fine job with the N incremental upgrates.

GroovyGeek said:
Yes, this was my mistake. Flashify was messing up for whatever reason, the flashing via fastboot from the full factory image went through fine. I had not done it for a while since Flashify seemed to be doing a fine job with the N incremental upgrates.
Click to expand...
Click to collapse
It looks like the Flashify dev has moved on and abandoned his project in Dec. 2015. Flashfire is an awesome product that you should look into. It does have a bit of a learning curve, but well supported by Chainfire. You can still freeload until sometime next year. There is a dedicated thread here on XDA. Works a treat on regular monthly updates, although I prefer to use the full image with FF, rather than OTA. By default it will preserve root and recovery while flashing. Primer and FAQ can be found here. The only good news is you probably won't make that same mistake again!