Android phone bricked - General Topics

I think my qualcomm mobile development platform MSM8655 based android phone has been bricked. I was trying to install browser.apk on my phone from my computer using adb. I followed the instructions below.
adb push (location of stock Browser.apk) /system/app/Browser.apk
adb shell
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
sync
For some reason, when I was "mounting" the phone, it gave me a message that " the device is busy". I still went ahead and did the "sync".
After that, I switched off the phone. When I tried to switch on the phone, nothing comes on the screen. Not even the android logo!
I tried to do a hard reset by holding both the power and volume up button. But it still didnot work.
In some forums, I read that this problem may occur because of USB charging. They had suggested to charge the phone using the plug and removing the battery and placing it again. I tried it and it also did not work.
I did found that adb is detecting the device. Is there anything that I can do using adb?
I am very desperate. Please help me.. Thanks

So you went ahead after if hadn't mounted the device. That means what you thought you put onto what you were trying to mount hasn't gone there at all.

Update
I guess you are right about it. I think the browser.apk which I was trying to install did not get installed.
Anyway, I went ahead and tried to do some debugging using adb. When I typed "adb logcat *:W", I am seeing an error message saying "Error preloading android.webkit.WebViewCore". Can anybody decipher the meaning of this? Thanks for the help

Update
I think my phone is stuck in a boot loop. The adb log message keeps printing the stuff below. Can anybody decipher the meaning of it? I think it has to do something with the browser installation which I was playing with.
I don't have a custom recovery or nandroid backup. So I am in a big soup. Please help me. Any pointers will be greatly appreciated...
W/MediaProfiles( 8660): could not find media config xml file
W/dalvikvm( 8660): Exception Ljava/lang/UnsatisfiedLinkError; thrown during Land
roid/webkit/WebViewCore;.<clinit>
E/Zygote ( 8660): Error preloading android.webkit.WebViewCore.
E/Zygote ( 8660): java.lang.ExceptionInInitializerError
E/Zygote ( 8660): at java.lang.Class.classForName(Native Method)
E/Zygote ( 8660): at java.lang.Class.forName(Class.java:235)
E/Zygote ( 8660): at java.lang.Class.forName(Class.java:182)
E/Zygote ( 8660): at com.android.internal.os.ZygoteInit.preloadClasses(Zyg
oteInit.java:302)
E/Zygote ( 8660): at com.android.internal.os.ZygoteInit.main(ZygoteInit.ja
va:579)
E/Zygote ( 8660): at dalvik.system.NativeStart.main(Native Method)
E/Zygote ( 8660): Caused by: java.lang.UnsatisfiedLinkError: Library webcore no
t found
E/Zygote ( 8660): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/Zygote ( 8660): at java.lang.System.loadLibrary(System.java:557)
E/Zygote ( 8660): at android.webkit.WebViewCore.<clinit>(WebViewCore.java:
61)
E/Zygote ( 8660): ... 6 more
E/Zygote ( 8660): setreuid() failed. errno: 17
W/dalvikvm( 8660): threadid=1: thread exiting with uncaught exception (group=0x4
001d7d8)

Hard bricking sucks
I just bricked a week old atrix, so I know exactly how you feel... It really sucks when something like that happens.

I was bricked my alcatel one touch 990 ,but i now use Htc hd2 and its soo nice and good phone,i love it

So is your device rooted??? If so, could you wipe and re-install your OS???

Please try to refrain from practicing thread necromancy just to say "me too." Start your own thread if you're having issues.....

There are many ways to unbrick your phone, just find a valid forum post and follow the iunstructions

Since adb is able to detect the phone, if you can find an ruu for your particular device then perhaps you can restore everything to stock.

Have you tried putting it in download mode and connecting to Odin to flash?
GL!

A couple of weeks ago I bricked my Samsung Galaxy S plus, but I just put it into download mode and flashed it. Maybe that will help.

Related

Hard to track down bug: "Unable to read AndroidManifest.xml"

Just wanted to post a quick note about a bug we ran into while putting together a theme. I thought it might be applicable to many other situations where tons of people have no problem at all with an update, yet others get a boot loop or other weird behavior...
The common error to show up in the logcat is this where ***** can be a seemingly random apk file:
Code:
07-09 02:08:05.999: DEBUG/asset(137): failed to open Zip archive '/system/app/******.apk'
07-09 02:08:06.019: WARN/PackageParser(137): Unable to read AndroidManifest.xml of /system/app/******.apk
07-09 02:08:06.019: WARN/PackageParser(137): java.io.FileNotFoundException: AndroidManifest.xml
07-09 02:08:06.019: WARN/PackageParser(137): at android.content.res.AssetManager.openXmlAssetNative(Native Method)
What we found was people with the older SPL were running out of space on the /system/ partition (usually when dex-opt'ing a larger apk file).
So when you are developing an update and are about to release it, it might be a good idea to run 'df' from the terminal and see how much space you are using on /system. The common SPL 1.33.2005 only has 69120K total on my phone.

[FIX] DSP Manager working on sense rom. +Possible fix for bad speaker

I don't like quite speaker of DHD, and don't want use non sense rom.
After small research i have found working solution
DSP manager needs customized libaudioflinger.so, but if just replace it, all sound gone on sense rom.
I have taken libaudioflinger.so and libaudio.so from CyanogenMod 6.1.0 Beta 3, and replaced. DSP Manager WORKS fine!
But then i have found another problem, DSP Manager disables it's eq when phone in call (also when it's ringing), so i have modified manager source and added new page for speaker settings when phone ringing.
All what you do, you doing on own risk, I'm not responsible for any damage!
Backup libaudioflinger.so and libaudio.so from /system/lib/ before continue
This patch will break dolby and srs features of preinstalled music player
2010.11.29 This patch also breaks working of stereo bluetooth headset, but in in call bluetooth headset works well
- Install patch using Recovery
Download DSPManager-DHD-update.zip
Copy it to phones sdcard
Reboot to recovery and apply this update.
- Install manually (using adb) * you need to know what is adb and how use it, and have S-OFF with ENG HBOOT
Download DSPManager-DHD-files.zip
Unpack files to temporary directory
Remount /system on phone as rw (run 'adb shell', then rund command in shell 'mount -o remount,rw /dev/block/mmcblk0p25 /system')
Run commands from computer
#adb push libaudio.so /system/lib/
#adb push libaudioflinger.so /system/lib/
#adb push DSPManager-DHD.apk /system/app/
and then reboot your phone.
- Uninstall manually (using adb) * you must have S-OFF with ENG HBOOT
Connect phone to computer using usb
Open adb shell (run adb shell)
Remount system as read write (run in shell 'mount -o remount,rw /dev/block/mmcblk0p25 /system')
Then you need copy to /system/lib/ on phone backuped files libaudioflinger.so and libaudio.so.
If you backuped it on computer, then locate they and in backup folder run
#adb push libaudio.so /system/lib/
#adb push libaudioflinger.so /system/lib/
if you backuped files on sdcard, then from adb shell run commands
cp libaudio.so /system/lib/
cp libaudioflinger.so /system/lib/
rm /system/app/DSPManager-DHD.apk
then reboot your phone
- Uninstall with recovery, rollback libs to stock v 1.32.405.6
Download DSPManager-DHD-uninstall.zip
Place it on sdcard, and install this update from recovery.
How it's works (amplify about +6db):
to moderators: i'm posting in
'Desire HD Android Development' because using this patch required changing /system/ partition
So is it a lot louder with DSP manager installed?
I am especially interested in ring volume and notification volume as i am finding that I tend to miss some calls and SMS's because i dont hear them
Speaker it self not so good.
But overal volume can be increased. Is it will be enough for you - don't know.
All changes made by 5band equalized, in range +/- 10db (as drawn in configuration utility)
Works great, thanks!
I find the trick with the DHD is to make sure you put it in your pocket with the screen facing your leg since the back speaker is much more powerful than the front one.
exidler said:
Speaker it self not so good.
But overal volume can be increased. Is it will be enough for you - don't know.
All changes made by 5band equalized, in range +/- 10db (as drawn in configuration utility)
Click to expand...
Click to collapse
Ok I have installed it.
What settings are you using for gain in the 5 bands? I have tried +6 in all five.
Will this also work for notifications and sms notifications?
I posted about this app on the LeeDroid Rom thread. Maybe Lee could add the app to his Rom if enough people are interested...
Just to inform you all this knocks out dolby and srs. Restoring the system lib files should restore them though.
broncogr said:
What settings are you using for gain in the 5 bands?
Click to expand...
Click to collapse
i have using 5.0, 6.7, 6.5, 6.0, 4.3 (i'm don't like high pich of speaker)
SkilletDesire said:
Just to inform you all this knocks out dolby and srs. Resorting the system lib files should restore them though.
Click to expand...
Click to collapse
thanks, i will write about it in first post.
Would it be possible to hack the Dolby / SRS feature in a way that you can globally enable it so that every music player and even system sounds/notifications can benefit from it?
That would be pretty awesome, I kinda like the sound of those features, but I dislike the music player. I think this would be a cool thing to explore / include on custom ROMs.
Nice job! Was getting round to this one, its already an add-on for my Desire ROM
Swyped from my LeeDrOiD loaded HTC Desire HD using my thumb....
Excellent work
maybe some one would be so kind to make a before and after video so that we can all see how great this patch works?
lukesky said:
maybe some one would be so kind to make a before and after video so that we can all see how great this patch works?
Click to expand...
Click to collapse
I have uploaded video, look in first post.
Noticed the difference...great work !
Doesn't work on Legend/FroYo
I am using an unofficial froyo build for the legend. http://forum.xda-developers.com/showthread.php?t=841517
Unfortunately the DSPManager doesn't work with that rom
E/AndroidRuntime( 122): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 122): java.lang.UnsatisfiedLinkError: Library android_servers not found
E/AndroidRuntime( 122): at java.lang.Runtime.loadLibrary(Runtime.java:461)
E/AndroidRuntime( 122): at java.lang.System.loadLibrary(System.java:557)
E/AndroidRuntime( 122): at com.android.server.SystemServer.main(SystemServer.java:908)
E/AndroidRuntime( 122): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 122): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 122): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 122): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 122): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 122): Sending signal. PID: 122 SIG: 9
E/AndroidRuntime( 122): Error reporting crash
E/AndroidRuntime( 122): java.lang.NullPointerException
E/AndroidRuntime( 122): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 122): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:887)
E/AndroidRuntime( 122): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:884)
E/AndroidRuntime( 122): at dalvik.system.NativeStart.main(Native Method)
I/Zygote ( 121): Exit zygote because system server (122) has terminated
D/AndroidRuntime( 130):
Click to expand...
Click to collapse
Just a quick side note...
Couldn't get the CWM.zip to work so I pushed the files using root explorer...worked fine
Excellent job I can hear now lol
Kimi123 said:
I am using an unofficial froyo build for the legend. http://forum.xda-developers.com/showthread.php?t=841517
Unfortunately the DSPManager doesn't work with that rom
Click to expand...
Click to collapse
This *.so libraries only for Desire HD hardware.
Look for original DSP Manger package
@exidler
I have written a little guide for your DSPManager patch on our website, hope you don't mind.
http://hemorrdroids.net/do-you-wish-your-desire-hd-speaker-could-be-louder/#more-2424
Thanks a lot for this development. At least we know this low speaker issue can be developed or fixed via software update, I hope HTC engineers will see and integrate it this into new batches with a few developments so that new users al least will not suffer

Help with logcat errors? (Building CM10 for AT&T One X+)

So over at the One X+ forums, we've been working on trying to get CM10 running, and I've been running into some errors in logcat. The build I currently have will get to the boot animation, but stay there forever. Here's the full logcat: http://cl.ly/text/2i3h24340S3F
The specific error I believe is causing the problem is:
Code:
F/libc ( 151): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 151 (zygote)
This error comes up every 100 lines or so. From what I've read, zygote is a process generated by app_process in /system/bin, but replacing it with ones from different ROMs does nothing. Is zygote the problem, or is something else preventing the ROM from fully booting up?

[Q] Glamour S4 4.3 Rom (Unfortunately Settings Has Stopped)

Hi, Im getting an "Unfortunately Settings Has Stopped" error at boot of this rom, does anyone know a fix for this ?
mdcool26 said:
Hi, Im getting an "Unfortunately Settings Has Stopped" error at boot of this rom, does anyone know a fix for this ?
Click to expand...
Click to collapse
Post a logcat.
If you don't know how, then you can run the tool in my signature and use the command lgctnp
Then post the generated text file as an attachment here.
missis roo
Lgrootnoob said:
Post a logcat.
If you don't know how, then you can run the tool in my signature and use the command lgctnp
Then post the generated text file as an attachment here.
Click to expand...
Click to collapse
I've never done a logcat before. But I have adb installed with phone connected through usb. typed in "adb logcat -v long > Settings has stopped.txt" with message saying "- waiting for device -" then nothing happens when booting phone ?
mdcool26 said:
I've never done a logcat before. But I have adb installed with phone connected through usb. typed in "adb logcat -v long > Settings has stopped.txt" with message saying "- waiting for device -" then nothing happens when booting phone ?
Click to expand...
Click to collapse
Sorry, you will need the drivers for your device and you will have to have usb debugging on.(> the reasons for the waiting for device)
If you don't have debugging on then we must find a recovery with adbd running.
Then use my tool's command lgctnp
then exit notepad.
post the text file from the Work folder here in an attachment.
Then we can move along.
Lgrootnoob said:
Sorry, you will need the drivers for your device and you will have to have usb debugging on.(> the reasons for the waiting for device)
If you don't have debugging on then we must find a recovery with adbd running.
Then use my tool's command lgctnp
then exit notepad.
post the text file from the Work folder here in an attachment.
Then we can move along.
Click to expand...
Click to collapse
Here's a logcat. I had to update adb to latest version to get working.
mdcool26 said:
Here's a logcat. I had to update adb to latest version to get working.
Click to expand...
Click to collapse
Now we got something.
Status update in 5 minutes.
---------- Post added at 03:57 PM ---------- Previous post was at 03:39 PM ----------
DISCLAIMER: I'm not a developer. So expect some hiccups.
Potential issues:
dlopen failed: library "/system/lib/libnetcmdiface.so" not found
^Missing module. (Might mean networking problems )
bool android::SecHdmi::create(int, int)::FIMC0: Insufficient memory size(0x 3c00KB) for Graphic layers
^Hdmi? Don't worry 'bout this one.
(Seems like Hdmi out on this phone won't work} Does this phone have Hdmi out?
Back to the point.
Do you have trouble with airplane mode or wifi or any other networking?
What settings have you touched in developer options?
It says something about database issues with the settings application. Have you changed the default database at all with titanium backup?
(as in: Convert dbs to WAL mode)
Go run fix permissions in recovery.
Try the settings.
Then if it doesn't work try clearing data for settings app, and rebooting into recovery and clearing dalvik cache.
Can you quote this post to the rom developer please?
Other Stuff to highlight:
Code:
[ 12-01 04:11:07.846 7678: 7718 E/Volley ]
[287] NetworkDispatcher.run: Unhandled exception java.lang.NullPointerException
java.lang.NullPointerException
at com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:100)
at com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:105)
[ 12-01 04:11:13.736 4615: 4700 D/CrashAnrDetector ]
processName: com.android.settings
[ 12-01 04:11:13.736 4615: 4700 D/CrashAnrDetector ]
broadcastEvent : com.android.settings system_app_crash
This looks like a major issue:
[ 12-01 04:11:07.776 7771: 7783 E/DatabaseUtils ]
Writing exception to parcel
java.lang.NullPointerException
at com.visionobjects.resourcemanager.util.Version.compareTo(Version.java:88)
at com.visionobjects.resourcemanager.util.Version.compareTo(Version.java:1)
at java.util.ComparableTimSort.countRunAndMakeAscending(ComparableTimSort.java:286)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:153)
at java.util.ComparableTimSort.sort(ComparableTimSort.java:142)
at java.util.Arrays.sort(Arrays.java:1973)
at java.util.Collections.sort(Collections.java:1867)
at com.visionobjects.resourcemanager.core.FileSystemHelper.keepOnlyMostRecentLibVersion(FileSystemHelper.java:64)
at com.visionobjects.resourcemanager.core.FileSystemHelper.<init>(FileSystemHelper.java:52)
at com.visionobjects.resourcemanager.DataStorageProvider.buildLangCache(DataStorageProvider.java:270)
at com.visionobjects.resourcemanager.DataStorageProvider.buildLangsCursor(DataStorageProvider.java:315)
at com.visionobjects.resourcemanager.DataStorageProvider.query(DataStorageProvider.java:175)
at android.content.ContentProvider.query(ContentProvider.java:744)
at android.content.ContentProvider$Transport.query(ContentProvider.java:199)
at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:114)
at android.os.Binder.execTransact(Binder.java:388)
at dalvik.system.NativeStart.run(Native Method)
[ 12-01 04:11:07.786 7743: 7743 D/AndroidRuntime ]
Shutting down VM
[ 12-01 04:11:07.786 7743: 7743 W/dalvikvm ]
threadid=1: thread exiting with uncaught exception (group=0x41c70700)
[ 12-01 04:11:07.801 5072: 5072 W/dalvikvm ]
Refusing to reopen boot DEX '/system/framework/commonimsinterface.jar'
[ 12-01 04:11:07.806 7743: 7743 E/AndroidRuntime ]
FATAL EXCEPTION: main
java.lang.RuntimeException: Unable to start receiver com.android.settings.SettingsIntentReceiver: java.lang.NullPointerException
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2541)
at android.app.ActivityThread.access$1600(ActivityThread.java:159)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1392)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5419)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:525)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1046)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:862)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:115)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
at android.os.Parcel.readException(Parcel.java:1437)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:185)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:137)
at android.content.ContentProviderProxy.query(ContentProviderNative.java:385)
at android.content.ContentProviderClient.query(ContentProviderClient.java:86)
at android.content.ContentProviderClient.query(ContentProviderClient.java:67)
at com.android.settings.handwritingsearch.RMHelper.getLangList(RMHelper.java:43)
at com.android.settings.SettingsIntentReceiver.checkVOLanguage(SettingsIntentReceiver.java:1752)
at com.android.settings.SettingsIntentReceiver.onReceive(SettingsIntentReceiver.java:565)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:2525)
... 11 more
[ 12-01 04:11:07.836 4615: 5202 I/ActivityManager ]
Notify an ApplicationCrash
problem in glamour s4 rom
I am also using glamour s4 rom on s3 but there are some problems which lack my device performance .!
The camera isn't working properly when I click the button to capture the image the camera is unfortunately get stopped .!
Sometimes settings also stopped !
And a window appear on which writen
Unfortunately touchwiz stopped .!
Plz help me guys .!
Although I respect the work of henery and his partners !
May I get the solutions of these all problems .!
Otherwise the best rom having features of s4 and of note 3 .!

IKeyStore Force Closes

I had the 4.4.4 CarbonRom flashed and decided to try out the new 5.X.
Without updating my bootloader ( It was 4109 I think) I clean wiped my phone and flashed the euphoria rom. I was unable to open the Security Settings menu or uninstall any app. I posted the logcat from the 5.1 rom in the euphoria thread.
Since I was on the old bootloader I updated to the 4118 versione without a problem but I still couldnt open Security or uninstall any app. I tried other roms such as the AOSP 5.1, but it still wasn't working. So I tried going back to the stock 4.4.4 rom but I'm still having the same problems. The logcat from the 4.4.4 stock is attached. I've also tried the 5.1 stock rom, same result.
Any idea on how to fix this?
Ok I managed to fix this by searching for another string I found in the logcat, specifically :
Code:
E/QSEECOMAPI: ( 6008): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 6008): Error::Cannot open the file /firmware/image/keymaste.mdt
I'm reposting the solution and the relevant logcat lines for any poor soul that has the same problem in the future:
Code:
E/AndroidRuntime(19798): java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException: Attempt to invoke interface method 'int android.security.IKeystoreService.is_hardware_backed(java.lang.String)' on a null object reference
E/AndroidRuntime(20411): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException: Attempt to invoke interface method 'int android.security.IKeystoreService.zero()' on a null object reference
E/AndroidRuntime(25642): java.lang.NullPointerException: Attempt to invoke interface method 'int android.security.IKeystoreService.clear_uid(long)' on a null object reference
I found the solution in this thread. You have to copy the keymaster files I attached in the zip into the /firmware/image/ folder after mounting the /firmware with read write permissions. Be sure to chmod 644 all the files too.

Categories

Resources