Hi, I recently got my phone working again with some help from this forum so I thought I'd come back.
Before I failed flashing a ROM so I told myself I'd stick to xposed until I learned more. Well this module had me edit build.prop to work. Once I edited and rebooted my phone, I was stuck with a black screen.
LG Mobile Support Tool/Flash Tool doesn't work now (in download mode) and ADB won't detect my device. I even tried Ubuntu in a VM and I couldn't get it to find my phone even though I was able to add it as a USB device in VirtualBox.
I barely know anything about this stuff but I knew I was supposed to install a recovery, I installed TWRP, I can't boot into anything at all though. Hardware factory reset doesn't work, download mode works but again LG flashing doesn't. So confused.
I've looked all over and I'm unable to find anything. If I can get this fixed, I'm not even going to root my phone.
EDIT: Can a mod please move this to the proper section? Thanks
Is my phone completely useless now?
Related
[SOLVED]
MESSAGE TO DEVELOPERS/ANYONE WHO CAN HELP
Long story short, i edited my build.prop incorrectly and reset (yes i know very stupid) now my motorola cliq opens up to the motoblur screen but repeated messages saying "Sorry! the process X has shut down" show up.
Literaly, nearly nothing can open up but i am able to enter usb mode if i fight with the endless popups. i can also enter recovery mode because my phone was rooted before this. The problem is that my recovery image doesnt have any options that could help me
(reboot, apply sd card:update.zip, and wipe data/factory reset)
i've tried putting an official motorola update.zip onto my sd card then running the apply.. but like i told you before my build.prop is messed up a little so an error shows up saying:
Installing update...
E/:Failure at line 1: assert file_contains("SYSTEM:build.prop", "ro.build.fingerprint=motorola/morrison_two_us/morrison/morrison:1.5/CUPCAKE/1.4.8:user/rel-keys" == "true" || file_contains("SYSTEM:build.prop", "ro.build.prop", "ro.build.fingerprint=MOTO/morrison_two_us/moInstallation aborted
Press Menu+Back to reboot
All i need to do is fix the line of code i messed up but i cant reach my systems files,...i attached my original build.prop and a copy of my corrupted one to show you.. I also cannot use the phone service or network service (even wifi) because like i said, nearly ALL the services are unable to stay on, they immediately shut off at startup.
Ways to fix this would be to REACH/EDIT THE SYSTEMS FILES
1. I cant use an app like root explorer since i cant access any apps on my phone even things like my settings
2. Turn on usb debugging somehow (I cant access my settings app so im lost on this one)
1. ingenious DESKTOP program that can somehow access my phone's system files without adb (if it can access the sd there has to be a way..)
3. Ive looked around to maybe find a custom image recovery that had options like editing system files (shouldn't be hard to make..) but ive found none with that option and im not sure how i would install it without adb...
What i CAN do
1. ENTER USB MODE (that has to count for something so Developers Please help me)
2. I can play with the motoblur intro screen to some degree to make it go away, then a blank black home menu appears. If i wait a while for the popups to stop at the motoblur screen, i follow the instructions but it gets stuck at registering a new account or existing one since you need network access.
3. ENTER REVOVERY MODE (but the only option that looks helpful is the sdcard update which gave me an error...) I havent tried the wipe data/factory reset because the factory reset doesnt touch the build.prop so its pointless
WHat should I do? WHoever sees this please give me advice or direct me somewhere to get it... THANK YOU
[EDIT]
BTW what i was trying to do on the build.prop was replace this line (ro.build.fingerprint=generic/sdk/generic:3.2/HTJ85B/140714:eng/test-keys)
with (ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys)
but i messd up and put
(ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/rel)
youll see this in the attachments...what this does is unlock my 1.5 firmware market to ALL the apps (updating to the official 2.1 using recovery wouldve handled this but i didnt even know of this update till after my mistake)
I just thought id mention...
if you have adb abilities you can push the old build.prop. If you do not know a out this then post back and I will help you.You said you can enter recovery, but that is stock original recovery that anyone can get access to. If you ever bootstrapped your phone you can try pull the battery out, wait about 10 seconds, then plug your phone charger in without the battery in. If your bootstrappped this will pull you into a more advanced recovery mode. The last option is to use rsd lite to flash an sbf to your phone if nothing else works. If you have never done this just look up sbfing motor cliq to stock.
Good luck, and remember to thank me if this helped
SOLVED!!
I fixed my phone on my own but THANKS to rootfan for being the first to answer.
HERES HOW:
I was able to access recovery mode and from there i discovered the sd update option.
It took hours of research and work but i learned alot about adb,motorola, cliq, etc.
Anyway, i originally found the Blur_Version.2.1.5.MB200.T-Mobile.en.US.zip and i tried to put that in my sd card (i could get into it from the phone) but when i tried to update using recovery it gave me an error so i decided to try the "latest 1.5 with Blur 1.6.1" which was actually very hard to find... you can get it here
motorola. com/staticfiles/Support/Experiences/sdcards/US-EN/tmo/cliq/downgrade-to-cupcake .html
Lastly, i put that on my sd as update.zip, went into recover, and the update was SUCCESSFUL! MY PHONE REBOOTED AND NOW IS ACTING NORMAL AGAIN. Now, im trying to update to the Android™ 2.1 (Eclair):
motorola. com/staticfiles/Support/Experiences/sdcards/US-EN/tmo/cliq/2-1_index. html
but im still getting that error whether i update using recovery or the settings/about phone/system update option... Thats strange but my phone is still working normally and ill find a way to update to 2.1...
ONCE AGAIN THANKS TO ROOTFAN AND HOPEFULLY THIS POST WILL WORK FOR SOMEONE ELSE WHO MAY BE HALF-BRICKED (no adb, no usb debug, no root explorer) THERS STILL HOPE IN RECOVERY+USB DRIVE+BLUR VERSION SOFTWARES
Thanks man, now this is probabaly a redicilous reply, since im sure you would have already tried this, but you can try going into settings, about phone, and click on update and see if the 2.1 eclair ota update will work on your phone.
i've got a simila problem on my samsung Galaxy S5570...
... and i need to prepare an update.zip .
Can you help in this, or you only downloaded a new rom ?
stepph said:
i've got a simila problem on my samsung Galaxy S5570...
... and i need to prepare an update.zip .
Can you help in this, or you only downloaded a new rom ?
Click to expand...
Click to collapse
You can reflash a stock rom back if you wanna get it done easily - or even a updated gingerbread one from samfirmware.com
Search for S5570 in these fora for some guides
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please note I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronize me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image. Any help or suggestions would be very much appreciated.
Carbon131 said:
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please not I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronage me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image flashed. Any help or suggestions would be very much appreciated.
Click to expand...
Click to collapse
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
polobunny said:
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
Click to expand...
Click to collapse
Hopefully someone may know what to do.
Carbon131 said:
Hopefully someone may know what to do.
Click to expand...
Click to collapse
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
polobunny said:
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
Click to expand...
Click to collapse
Yeah I can't seem to do that.
Carbon131 said:
Yeah I can't seem to do that.
Click to expand...
Click to collapse
Make sure your cable is connected when you try to put your phone in download mode. Turn off the phone, then hold both volume + and -, and press power. Continue holding volume buttons until you see download mode.
i have an lg g2 vs980 and i rooted it but have not yet installed a recovery like twrp it is only the very basic root with super user. it decided to install some ota update and now it will not boot past lg screen, white letters flash really fast all i could make out was secure boot error or something. i cannot get it into any kind of download or reset mode, iv tried absolutely everything anyone on this forum has recommended or suggested and nothing works, also when i connect it to my pc running windows 8 it is seen as QSUSB_BULK i have installed the correct updated drivers for my phone and iv manually installed them, nothing i have done will allow my pc to see my phone correctly. when i plug it in it under computer there are local drives f-u that pop up and say i have to format them in order to use them, but they are write protected so i cannot view whats in them, format them or anything. does anyone out there have any kind of suggestion to fix this or am i just completely stupid and missing some big major step? i am also very new to android this is my first android phone lol im a converted apple user haha so the more indept detailed instructions would be greatly appreciated
Same issue here
haeli said:
i have an lg g2 vs980 and i rooted it but have not yet installed a recovery like twrp it is only the very basic root with super user. it decided to install some ota update and now it will not boot past lg screen, white letters flash really fast all i could make out was secure boot error or something. i cannot get it into any kind of download or reset mode, iv tried absolutely everything anyone on this forum has recommended or suggested and nothing works, also when i connect it to my pc running windows 8 it is seen as QSUSB_BULK i have installed the correct updated drivers for my phone and iv manually installed them, nothing i have done will allow my pc to see my phone correctly. when i plug it in it under computer there are local drives f-u that pop up and say i have to format them in order to use them, but they are write protected so i cannot view whats in them, format them or anything. does anyone out there have any kind of suggestion to fix this or am i just completely stupid and missing some big major step? i am also very new to android this is my first android phone lol im a converted apple user haha so the more indept detailed instructions would be greatly appreciated
Click to expand...
Click to collapse
Has anyone come up with a solution to this? I am very new to Android, I have Rooted my G2 so I could install Custom Rom's. Yesterday I receive a OTA update, I refused it and then later when it came up again was going to refuse it, but my shaky finger touched the screen and started the update! next thing I know I have a $600.00 brick. if you hold the power button down It will flash the LG logo and then NADA, screen is lit but nothing happens. Hold the power button and after a few it will Flash the logo again but NADA again. If you hold the down and power button it will go to the reset screen, but again this will not reset the device. PLEASE HELP!
Thank you.
I just bought a LG G2 I rooted it with towelroot. Then i used autorec to install a recovery. I installed the wrong version of autorec & then i got the constant fastboot log. After that i read a fix for that via fastboot flash and not knowing my computer wouldn't flash the aboot.img i removed aboot.img and it would not flash it. So now my LG G2 just has a black screen. However when I plug it in a whole bunch of flash drives pop up continuously, and everytime that they blink on and off my screen semi lights up black so it flashes between that and completely black. I have tried to use linux because i read a tut to fix a similar problem that way. However I cannot seem to get anything to work for my phone. If anyone can help please let me know! the back of my phone says it is version D800 however when i rooted my phone with towelroot i tried using freegee to bypass the bootloader and it said it wasn't compatible with version D802u......Update! However i did manage to use linux to get it back into fastboot mode i cant seem to get anything to work in fastboot ive tried flashing the laf.img and it wont flash it just comes up with a error. I can say fastboot reboot and it will reboot
Update phone is fixed and working just fine. Apparently I did everything wrong but something was wrong with the cm11 snapshot I flashed. Just rerooted my phone and installed cm11 flawlessly! I would like to thank Windows 8 & Linux along with all the forums on xda that helped me fix my phone without them it wouldn't have been possible!
This post doesn't seem to match others asked before.
I had a perfectly working rooted/rom'd HTC One (M8). Unfortunately, screen cracked so I sent it off to the insurer to sort. It came back looking great. However, I was now unable to access any of the internal storage. Everytime I tried to download a photo, voice clip or Mod Edit: removed mention of warez it would say 'unable to download', 'cannot save' or something along those lines.
I checked to see the device was still rooted. It was. Nevertheless, I perhaps in ignorance, ran through all the steps over again and spent 3.5 hrs doing so! I now have a wonderful adb file on my desktop and I was fiddling around doing fast reboots etc and trying to flash a customrom in the hope that this would fix the storage invisibility/lack of permissions. I tried fixing with busybox etc but I couldn't even install busybox as it didn't recognise that there was any internal storage whatsoever! I also could not load onto my storage (for the same reason!) the latest SuperSU zip to flash as a rom.
In the end, through fiddling about, I was able to find my old storage pack. It was all there and I located an old SuperSU from when I had previously rooted about 6 months ago (an old version now I assume). Flashed this and rebooted. I was still adb connected so ran a fastboot and chose to run the TeamWin Recovery Wipe (standard setting, not advanced).
When wiped, I tried to get my phone to turn back on thinking it would be factory reset and I could start again but now I literally cannot get my phone on!! It is plugged into the computer via USB (i've tried disconnecting it too) and no matter what I try I cannot get this phone to do anything now - it's just a black screen that doesn't look completely off if I look closely it looks like it is on somehow....? Tried holding down vol down and power - nothing. It has flatlined!
Any help PLEASE!!!!! ?????
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-one-m8 To get help on your specific problem try asking here, http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783