• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Help!!! I Think I bricked my phone!!!

trebor7

Newbie
Hi. So I used the app Beats Audio Installer and everything ran smoothly. When it rebooted itself, it stayed on the LG Splash Screen. It stayed there for about 10 minutes when I pulled the battery. Now whenever I boot it up, it stays on the LG splash screen and does nothing else. Help me please!!! I am super new to the world of rooting, and I can't even do basic ADB commands! Please help ASAP! I'm really scared!
 
Don't worry to much, you should be okay. It's when it won't boot at all, not even a little bit, that will kill you. Someone who knows your phone will help you out.
 
Dont use apps made for other phones...

try this to fix the boot loop : http://androidforums.com/elite-all-things-root/567788-fix-boot-loops-please-post-yours.html


if that doesnt work,try reflashing using the jcase root method here : http://androidforums.com/elite-all-things-root/564734-lg-optimus-elite-root-vm696-virgin-mobile.html
Curtis1973, thank you so much for your advice. The only problem is that I don't have DIAG mode enabled for my Elite, and I don't have my MSL. I'm trying to use QPST to get my MSL to no avail. I'm not sure what to do at this point...
 
Curtis1973, thank you so much for your advice. The only problem is that I don't have DIAG mode enabled for my Elite, and I don't have my MSL. I'm trying to use QPST to get my MSL to no avail. I'm not sure what to do at this point...



ok,best advice considering you are trapped in loop.. call virgin mobile usa,tell them you have gotten an error 67 message after turning on wi-fi and cant access the web. play dumb. (i know its a bit of a white lie,but the error message is real and will gain you your msl number.) play along as if you are entering everything they are asking you to. once you get the msl number and write it down,hang up. then proceed with using the jcase root method or qpst boot loop fix. im not thinking the boot loop fix will work as i believe beats damaged your audio drivers. so jcase root method is probably your only option. once you have everything setup to use the jcase root method,boot into recovery mode by holding the volume down button and power on until the recovery menu appears. now just leave the phone in recovery without changing anything. next plug your device into usb port. now start up lgnpst and proceed as the guide suggests. you can then enter your msl code. with any luck the flash will proceed as i hope it will and return your android system to a useable state. assuming it works,update your device with the lg update then use giantpunes apk set to reroot your device. ill check back in the morning to see how things went and will help further if i can. but you may end up needing to send the device back for a replacement. either to store of purchase or virgin mobile if you are still under warranty.
 
If the phone boots up enough for adb to work, then you should be able to fix this without lying to LG and/or flashing the entire tot. The beats installer probably writes 1 or 2 small files in /system somewhere that could be replaced with the stock files using an adb shell.
 
Decompling the app shows that it puts things like "libbeatsbass.so" in /system/lib/soundfx, and some build.prop stuff-

Code:
htc.audio.global.state=0
htc.audio.lpa.a2dp=0
htc.audio.global.profile=0
htc.audio.q6.topology=0
htc.audio.enable_dmic=1
persist.htc.audio.pcm.samplerate=44100
persist.htc.audio.pcm.channels=2
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=analog
htc.audio.swalt.mingain=14512
htc.audio.swalt.enable=1
htc.audio.alc.enable=1

The way they coded their app was shit, there's a bunch of stuff left over from what looks like a previous version of the app called "RockoDev Beats", and a bunch of classes/activities that never get used. No wonder it's a hit and miss with this thing.
 
yeah the whole thing with gaining the msl and sending device back is distasteful,and im betting the phone can be seen by adb. pushing replacement files would be far easier. not good with adb,good time to learn i guess. either way its going to take some effort and learning some command line to get it operating again.
 
If the phone boots up enough for adb to work, then you should be able to fix this without lying to LG and/or flashing the entire tot. The beats installer probably writes 1 or 2 small files in /system somewhere that could be replaced with the stock files using an adb shell.

I wish adb shell worked in stock Recovery. But it's still worth trying it in the way giantpune suggested.
 
Thank you all SO much for all of your support. I configured ADB correctly, and my Elite is showing up as an ADB device when it boots far enough. Please excuse my n00b-ness, but can someone please give me the ADB commands that would fix my Elite? Thank you all so much again!
 
First, we need to see what audio drivers it installed, type in

adb devices (to make sure its ready)
adb shell
cd /system/lib/soundfx/
ls

Then tell us what it gives you after you type "ls".
 
First, we need to see what audio drivers it installed, type in

adb devices (to make sure its ready)
adb shell
cd /system/lib/soundfx/
ls

Then tell us what it gives you after you type "ls".
Did what you said and this was the output:

cd /system/lib/soundfx
$ ls
ls
libbundlewrapper.so
libreverbwrapper.so
libvisualizer.so
libxloudwrapper.so
libsrsfx.so
libcyanogen-dsp.so
libbeatsbass.so
libaudiopreprocessing.so
$
 
Okay, I've never tried this so it might not work. It's not going to do anything that will brick your phone though, it just puts the stock stuff back in place. Download the zip, extract, and put the files inside the "stuff" folder with your adb (aka platform-tools folders). Again, put the files only, not the "stuff" folder.- https://www.box.com/s/725u5svbgtc051hoxck2

Then run these things in cmd once the adb can see the phone.

adb pull /system/build.prop
adb push build.prop.stock /system/
adb push libbundlewrapper.so.stock /system/lib/soundfx/
adb push libreverbwrapper.so.stock /system/lib/soundfx/
adb push libvisualizer.so.stock /system/lib/soundfx/
adb wait-for-device shell
mount -o remount,rw /dev/block/mmcblk0p12 /system
cd /system/lib/soundfx/
rm libbundlewrapper.so
rm libreverbwrapper.so
rm libvisualizer.so
rm libxloudwrapper.so
rm libsrsfx.so
rm libcyanogen-dsp.so
rm libbeatsbass.so
rm libaudiopreprocessing.so
mv libbundlewrapper.so.stock libbundlewrapper.so
mv libreverbwrapper.so.stock libreverbwrapper.so
mv libvisualizer.so.stock libvisualizer.so
cd /system/
rm build.prop
mv build.prop.stock build.prop
mount -o remount,ro /dev/block/mmcblk0p12 /system
exit
adb reboot
 
I'm just tossing out a guess here, but that libFatAssBassThatsoundsLikeATrunkFullOfEmptycans.so isn't doing anything at all to hurt the phone. It is probably the buildprops that broke it.
 
libFatAssBassThatsoundsLikeATrunkFullOfEmptycans.so

Bro...Beats by Dre is a proprietary high definition audio experience engineered from the ground up to provide an unparalelled amount of high quality soundwaves. That "trashy" bass you hear, is the result of excellent craftsmanship, handmade to ensure quality. They have people in the lab 24/7 coming up with cutting edge technology previously unseen by mankind. Dr.Dre will lead us into a better, and more vibrant era of listening to music.

*cough/giggle/suppress laughter*

Ehh, it helps to drown out my siblings so its good for that purpose.
 
Thanks for the quick reply. I had to remount the system before I got to work with the first step: the build.prop. Now, when I try to push the audio drivers to their folder, I am denied permission:

C:\adb>adb push libbundlewrapper.so.stock /system/lib/soundfx/
failed to copy 'libbundlewrapper.so.stock' to '/system/lib/soundfx//libbundlewra
pper.so.stock': Permission denied

C:\adb>
 
build.prop for zv5. just change file ext. from txt to prop
Thanks a lot. But I think this is deeper than just the build.prop getting screwed. I ran a logcat and I found this message:

E/AndroidRuntime( 730): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 730): java.lang.UnsatisfiedLinkError: Cannot load library: li
nk_image[1962]: 724 could not load needed library 'libsystem_server.so' for 'l
ibandroid_servers.so' (link_image[1962]: 724 could not load needed library 'li
baudioflinger.so' for 'libsystem_server.so' (link_image[1962]: 724 could not l
oad needed library 'libaudio.so' for 'libaudioflinger.so' (reloc_library[1311]:
724 cannot locate 'audcal_initialize'...

So the system crashing is probably directly related to the missing/damaged audio drivers. At this point, I'm considering trying to give my best "I'm Innocent" act to Best Buy, as my phone is under their one year guarantee. Only problem is I'm not sure how to sell off the bootloop as something not of my doing...
 
you got up this morning,powered it on,and it kept looping. you have no clue why ;) blame it on dr dre lol
Alright then. As soon as I get my replacement I'll get right back on the rooting scene, thanks to everyone's hard work. Thanks a lot to everyone who tried to help me rescue my phone and to all of you who made rooting this device possible. As a last request, is there any way I can mount the internal memory and get some photos and videos from there? I had video of Bruce Springsteen from a concert I went to on the weekend, and I didn't move it to my computer in time :( is there any chance I can use some adb magic and pull those videos to my computer?
 
adb pull /sdcard

That should pull both internal and external memory to your platform-tools folder.
 
It says there's no such directory...probably because it isn't mounted. Never mind about the videos, that's what YouTube is for ;) I'll go to Best Buy sometime tomorrow I guess once I find the damned receipt for the phone...wish me luck and thanks once more!
 
And never mind about the video: I booted into recovery and adb was working and the SD card was mounted so I was able to get my photos and pictures back, along with my Titanium Backup of apps :D things are starting to look bright.
 
Back
Top Bottom