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
Related
My friend rooted his Galaxy Tab, and attempted to install a custom rom on it. For some reason, he flashed a jelly bean gapps zip, and now all of the google apps force close (still on the stock rom). This happens even after a full wipe and factory reset, since I would assume the wrong gapps has still been flashed. I downloaded ROM manager from the tablet's browser and tried flashing CWM recovery, but when I reboot into recovery, it just shuts off, and after a while, it's reverted back to the stock recovery (where I can't install zip from sdcard). In addition to this, for some reason, the tablet never gives the option to view files and folders on PC when connected via USB, so I can't even copy the zip files over (USB debugging is enabled). There isn't even any mount/unmount options in the storage settings.
What's going on here, and how can I fix this? As of now, it seems I can't do anything and I may just give it back to my friend.
adnana1024 said:
My friend rooted his Galaxy Tab, and attempted to install a custom rom on it. For some reason, he flashed a jelly bean gapps zip, and now all of the google apps force close (still on the stock rom). This happens even after a full wipe and factory reset, since I would assume the wrong gapps has still been flashed. I downloaded ROM manager from the tablet's browser and tried flashing CWM recovery, but when I reboot into recovery, it just shuts off, and after a while, it's reverted back to the stock recovery (where I can't install zip from sdcard). In addition to this, for some reason, the tablet never gives the option to view files and folders on PC when connected via USB, so I can't even copy the zip files over (USB debugging is enabled). There isn't even any mount/unmount options in the storage settings.
What's going on here, and how can I fix this? As of now, it seems I can't do anything and I may just give it back to my friend.
Click to expand...
Click to collapse
If you're looking to restore the tablet back to original purchased state then check out this thread here:
http://forum.xda-developers.com/showthread.php?t=1342995
Install Kies before using Odin as that will give you the proper drivers assuming you're using a Windows PC. The drivers will install the first time that you have Odin set up and you have the tablet in download mode. More than likely, even though you clicked start, Odin will sit or hang like it's waiting for something. If it sits for a while without doing anything at all, early on, close Odin and restart the setup process again. This time around the drivers are already installed and it should go smoothly from there. The tablet will restart on its own when its finished and after long boot you'll be greeted by the intial setup. It should naturally do about 3 software updates once setup is complete. That means that it will download the 1 update at a time and ask you if you want to install. After each reboot you should see more downloading activity until updates are complete I recommend after the very first boot you shut off mobile data and use Wifi only as these updates may munch up data...
Good luck.:fingers-crossed:
Wow, I really appreciate your response. I'll try this out later today, and post back with what happened (Can't right now as I'm at work). Thanks for your help!
Had not rooted this device before, I installed autorec.
Rebooted and flashed:
xdabbeb_vs98025b_bootstack.zip
Wiped everything (including internal storage :/) then rebooted back into recovery to install:
xdabbeb_vs98025b_lg_apps.zip
TWRP recovery works, Download mode "seemingly works" but LG flash tool never finds the port the device is on and I dont see a spot to change the COM in device manager, Sideload & push work just fine to put roms on the device.......but no matter what I flash it will not get past the LG logo, is there a bootloader issue?
everything pushed or sideloaded, transfers fine to the device and installations are successfull...but I never get past the LG screen
what are my options, somehow use the LG flash tool to go back to the default verizon install file and get user data back?
I have to go to a party but hopefully I can figure this out. I apologize if this has been solved many of times, but I dont seem to find an answer that works....
i got the same problem as of yesterday too.however i was rooted and i accidentally pressed the over the air update install button im stumped on what to do, because i dont want to wipe the internal storage.
jaymax97 said:
i got the same problem as of yesterday too.however i was rooted and i accidentally pressed the over the air update install button im stumped on what to do, because i dont want to wipe the internal storage.
Click to expand...
Click to collapse
I simply followed the install instructions and put 2.0.0/25a on on the phone instead...works....
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.
I have a Samsung Galaxy Tab 4 8” SM-T330NU running 5.1.1. The box tells me the ‘real’ model is SM-T330NYKAXAR. I decided to root the phone, because I want to get to Marshmallow and to get rid of this extra bloat where. (I will mention I have a good amount of experience rooting, including just rooting my Droid Turbo).
Anyway, after a lot of looking around the forums, I decided to use the CF-AutoRoot method (CF-Auto-Root-milletwifiue-milletwifiue-smt330nu) to root. I got Odin and installed it (along with the Samsung drivers) onto my Windows 10 PC; set debugging, on; and ran Odin. I followed the directions and it appeared to root properly; and I got to CWM recovery. Woo hoo! (Or so I thought)
So then after making sure I can get into recovery, I rebooted back into my stock ROM. Unfortunately, I got stuck at the Samsung logo; tried rebooting multiple times; even did a factory reset/wipe (as per instructions I saw on the forum) but to no avail. (Even let it set for over an hour but it never got past the Samsung logo).
After some more reading, I figured I might as well go ahead and flash a new ROM; so I think (if I remember correctly) I tried the JazzROM. It got up to about 69% and then it just quit - screen went black, and then it rebooted back to Odin mode. Obviously it didn’t work; then when I tried to get back into recovery to wipe and try the flash again, I got the message ‘Cannot mount \system - invalid argument’.
Again, after much reading and trying, I was able to get TWRP recovery installed and then wiped/formatted the system partition, which I had read would help get rid of that error. And it did seem to fix it.
So I can re-root with Odin without any issues; I can get to Recovery (either CWM or TWRP depending on which I flash), but no matter what I do, it either gets about 2/3 the way thru the flash process and then reboots back to Odin mode; or (using TWRP) I can get it certain ROMS to flash successfully, but after rebooting it goes right to Odin mode (saying it could not do normal boot). I even tried loading a stock, with the same result.
Which leads me to my first question: Exactly which ‘stock’ file should I be loading? I am having a hard time finding one - either it leads me to a dead end, or the download doesn’t work.
- When in CWM recovery, it shows the following:
At the top:
LMY47X.T330NUUEU1BOI1
Bottom:
#Manual Mode#
— Applying Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
Are these correct?
- When TWRP is installed (3.0.0-3) it starts by asking me about the ‘Unmodified System Partition’ and whether it should be kept read-only or allow modifications. I assume allow mods? Otherwise I don’t see how you could apply a new ROM? (I haven’t seen this in a while, not in my install of TWRP to the Droid Turbo). So just want to make sure I am selecting the right option.
- I am also concerned about whether I am using the right packages for this tablet. Based upon what I see on the box and sticker (which I still have) this should use the stock ROM LMY47K.T330NUUEU1BOI1 model; but I’ve also seen things referring to a BOG1 model? Mine is the T330NU English and (I assume) US model since I am in the US.
Any ideas as to what is going on? If I can at least get back to stock I could then start from scratch with the appropriate info; or just install one of the new ROMS (I’ve tried Jazz, Dirty Unicorns, UltraStock). I don’t think I am ‘bricked’ because if so I wouldn’t be able to get to Odin or recovery. Any help appreciated here. Thanks!
-Tom (Chimp)
NM, finally got it working, running DU and running fantastically, if I may say so. Getting TWRP to install finally fixed everything.
Sent from my SM-T530 using XDA-Developers mobile app
So basically, few months ago i tried to root the phone, get new recovery and different rom. If I remember correctly I got stuck trying to get custom recovery to work, because everytime I restarted phone it would be replaced by the stock one. So I left the phone as it was, and disabled the TWRP app on it. Problem was, I could not update phone. Today I tried to completely revert to stock.
I flashed stock recovery but when I tried to install update from the phone storage, it did not even give me option to select a file.
I tried to update the recovery to newer one which gave me the option to select a file, but the installation got canceled after few seconds, putting me back on the file selection screen in recovery.
I tried to instal TWRP but I can't even boot into it at all because the phone is just stuck with blackscreen and lightblue led light.
I tried to ADB sideload the newest stock rom that I downloaded from OP5 site but this one went to around 50% and then crashed as well.
I also tried to do the update using the Settings>System update > Local Upgrade but this one also fails once it gets into recovery.
I tried wiping cache/reset system settings or wiping every data on the phone before any update but none of it seems to help and everytime I restart the phone afterwards the TWRP app is still there needing an update.
I tried to just lock the bootloader but I got the "Your device is corrupt. It can't be trusted and will not boot" message followed by link to google support. I assume that is because of the TWRP app that is on the phone but I can't get rid of it no matter what I try. I tried searching for people having simillar problems but I couldn't find anything that would help me.
Any suggestions?
Thanks in advance.
You can go with the last resort and use the Unbrick tool.
https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706