I was trying to free up space and saw LG Home was taking up some space. Never knew it was a critical launcher. Ive tried millions of methods on various sites including xda, android forums, android central with no luck. Here is a rundown of the situation.
1. I had clockwork installed then it "disappeared" adb reboot recovery stopped letting me go to the clockwork bootloader
2. I have a custom ROM sitting on an sdcard called Cyanogen.zip Its never been messed with yet.
3. I do not have a "nandroid" backup or backup of the stock rom because clockworkmod never worked
4. Doing a factory reset did not fix the issue because apparently the OS runs live off the rom aka it never installs itself to the device like in WIndows . SO I get a total black screen setup screen with only a signal bar on top.
So the latest thing ive been trying is adb pushing a copy of LG_Home into the /system . This is not working because im getting a "permission denied" . Now before you get hasty please do not have me do these commands:
1. mount /system already did this back when doing clockwork
2. remount -o ,rw does not work, probably due to already having root
3. adb root tried it and it doesn't really do anything, I still get permission denied, and usage errors
This does not make sense because the phone is rooted (does factory reset take away root? ) , chmod 777 has been applied to /system . If I lost root doing a factory reset, is there a way to root the phone now that I don't have a functioning phone?
Here is what im aming to do with your help
1. Force the LG_Home.apk file into the /system
2. Force some way to get cyanogen mod installed as I now have a corrupt stock rom
Something has to work and im hoping someone will help me
Hi,
I would need to know your model of LG to point you in a direction to ask for help.
Thanks!
Darth said:
Hi,
I would need to know your model of LG to point you in a direction to ask for help.
Thanks!
Click to expand...
Click to collapse
sorry hah, its an LG Enlighten
OK, Unfortunately there's no section for your device on XDA. You will need to ask for help here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
Thank you. Thread closed.
Related
I got a Lenovo S850 from China and it came rooted from factory. I deleted apps I shouldnt and it booted up with constant security warning. I download what I thought was the correct rom and it did not install but phone would not come on. I found a rest of world rom to install that I thought was correct but after install imei's were missing and it had nvram warning in wifi. I have fixed that issue permanently but still with any sim card it says no service and a manual search fails.
Not sure if the first rom made a mess of the partitions etc but I have no idea why etc.
Just wondering if there was an expert that could connect to my pc via team viewer and take a look at it as I can connect it via adb but no idea what else to do. I think partitions are messed as in custom recovery it will not mount anything and had to adb sideload root.zip.
I will return it under warranty if I cant sort it though they may refuse to fix if they see it has a differnt rom on etc,
Anyone help?
Thanks
Simon.
Hi,
I can't find anything for your device on XDA, so you would need to ask here and hopefully someone can help. Otherwise I suggest you contact the manufacturer for original firmware and Flashing instructions...
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck!
Thanks I will ask there.
So I messed up. I've never done anything like this before and I think I bricked my phone. I tried rooting my Nexus 4 so that I could install the Lollipop preview and I did everything, installed Clockwork and all that. So when I got to installing the actual preview, I read that I had to wipe the cache and wipe the data so I did that and then went into the SDcard to install the preview and it failed. I tried again and it failed. I went to "reboot system now" and it boots straight back to Clockwork. I have no idea what to do and I'm freaking out. No matter what I do I can't leave Clockwork recovery/boot recovery. Please help me.
I don't know if my phone even has an OS on it anymore because I don't even get a boot logo (like glowing balls and all of that)
I do have a backup that I made (a tutorial I followed showed me how) using the Android SDK stuff. In my Device Manager Android ADB Interface is there but my Nexus 4 isn't even showing up for me to copy anything over.
Hi,
You probably need to flash stock again with fastboot. Here's a guide on that,
> Google Nexus 4 > Nexus 4 General > [HOW-TO] How to flash a factory image / return to stock / unlock / root #
You can ask for help there also or explain your situation.
Good luck!
KJ said:
Hi,
You probably need to flash stock again with fastboot. Here's a guide on that,
> Google Nexus 4 > Nexus 4 General > [HOW-TO] How to flash a factory image / return to stock / unlock / root #
You can ask for help there also or explain your situation.
Good luck!
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU! It worked. I finally worked! I honestly can't thank you enough. I love you.
Awesome! ?
Thread closed.
Hello all. I am a relatively new member to XDA and I have actually posted this issue on the thread to from which I downloaded the custom ROM I'm running. I am using and LG G2 D800 running [ROM][5.0][CM12][UNOFFICIAL][ALL-VARIANTS] CyanogenMod 12.0 For The LG G2, which I installed about a month ago. I originally rooted my phone using towelroot and installed TWRP custom recovery 2.7.0.0. I installed 3 or 4 other custom ROMS, using just my phone, that I honestly had no idea how to root using a computer. Since, then I have learned and acquired the tools I need to root from my computer, and after trying for quite some time, was able to find drivers for my phone that allowed my computer to recognized it.
There are 2 main problems that arose about a day after installing this ROM.
Firstly, after I had installed all of the pertinent files needed to flash the above ROM, I attempted to install the beta version of SU that the thread related to the above ROM said was necessary to keep root. Well, that version did not install correctly, though the ROM did install and is working about as well as an experimental version of a ROM can....
Once the ROM had been running for about a day or so, I realized how buggy it was and decided that it would be smart to go back to a more stable ROM as Lollipop was just around the corner(Or at least a stable CM12).
So, I went to go back into my TWRP custom recovery to do a wipe then install another ROM that I had backed up. When I attempted to do this, I realized the 2nd BIG PROBLEM, my phone had stopped recognizing my internal sd card, so I was unable to view any Backups I had previously saved. So, I started researching and found the the adb shell code to get my phone to recognize my sd card, but when I tried to use the command to do so, I was given the reply that su(part of the command) could not be found. So, I posted again, and was told,"you need to re-root." Well, that is good and well, but I have tried every method I can find to root my phone from my PC, but they are all for LG G2 D800 running some lesser version of android, never 5.0....
Any help would be greatly appreciated, and oh yeah, I was able to get the new Beta super SU file pushed onto my phone and saved in the remaining space it does recognize, but I couldn't actually install it to give me SU priveleges again. Basically, if I can re-root, I can get my SD card back, do a full wipe, then install another more stable ROM ASAP>
Thanks again, so so very much. Please, Please help me get this phone working. I'm feeling more and more like a fool everyday knowing Im paying for a phone I can barely even use....
Happy Holidays,
Thad
Hi,
Asking in the rom thread is a good idea. If you don't find answers there, then you can ask for help in this dedicated help thread in your device section,
> LG G2 > G2 Q&A, Help & Troubleshooting > [HELP THREAD][Noob Friendly] LG G2 Ask any question
XDA Assist is here to help navigate the site, not for support. ?
Good luck!
I have been searching for answer over 10 days, but still can't figure out how to resolve this. I don't how exactly it bricked, it just couldn't start anymore. I can get into recovery menu, but there isn't any option to recover android. It was rooted before, and worked normally. I cant find any other way to flash any rom on it. I appreciate any help on this matter, tnx in advance!
XDA Visitor said:
I have been searching for answer over 10 days, but still can't figure out how to resolve this. I don't how exactly it bricked, it just couldn't start anymore. I can get into recovery menu, but there isn't any option to recover android. It was rooted before, and worked normally. I cant find any other way to flash any rom on it. I appreciate any help on this matter, tnx in advance!
Click to expand...
Click to collapse
Hello, and welcome to XDA Assist!
Please register for an account so you can post to the rest oif the site. The [Ask Any Question][Newbie Friendly] thread of the > Android Development and Hacking > Android Q&A, Help & Troubleshooting will provide a good start to resolve your issue.
What seems confusing is that there may be some Arnova's made by Archos. Archos has a forum, but sadly, Arnova does not (not finding much about your device either).
At any rate, try the thread/forum above, and be patient with regard to a response. This seems to be a rare device, so it would be harder to get the attention you need.
Hope this helps, and good luck!
The other way
I understood that the complete system is wiped out. I can use adb while its in recovery menu. I used it to transfer official system image onto it, but in its options i cant find it. I transferred it to multiple locations, all of them can be seen in recovery menu but all are empty. I wonder if there is a way to flash some other android version on it? Or some ROM like CWM, but apparently there are no official releases. And since i am not very good at this i wonder how to make sure that kernel is OK? Can such thing be done? It has Android system recovery <3e>
Ricci2u said:
I understood that the complete system is wiped out. I can use adb while its in recovery menu. I used it to transfer official system image onto it, but in its options i cant find it. I transferred it to multiple locations, all of them can be seen in recovery menu but all are empty. I wonder if there is a way to flash some other android version on it? Or some ROM like CWM, but apparently there are no official releases. And since i am not very good at this i wonder how to make sure that kernel is OK? Can such thing be done? It has Android system recovery <3e>
Click to expand...
Click to collapse
CWM is a recovery, not a ROM, but can be used to flash ROMs.
With 3e, you should be able to flash the stock ROM for the device via adb (called side loading). So that may work for you.
Hope this helps.
Sent from my ASUS ZenFone 2
rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.
XDA Visitor said:
rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!
joel.maxuel said:
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!
Click to expand...
Click to collapse
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man
jasj0410 said:
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man
Click to expand...
Click to collapse
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.
joel.maxuel said:
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.
Click to expand...
Click to collapse
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot
jasj0410 said:
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot
Click to expand...
Click to collapse
Hello,
Fastboot is unable to flash zips unfortunately. That's the recoveries job.
If you can find fastboot images of stock, you can flash back that way.
Especially at this point, I would urge you to take advantage of the help thread I mentioned earlier. They know more about your device (particularly what's available and what not) they I would.
Hope this helps!