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

Android Bootloop, adb logs for Interpretation

V

Virucyde

Newbie
So my Chinese device is stuck in a standard bootloop, but I managed to adb into it. However, it doesn't have a boot menu and has no recovery mode(tried them through ADB, and can't get any button combos to work).

So my hope is that I may be able to fix it through ADB, since at least that's working. I've got the logs from a fresh boot here, using the command "adb wait-for-device | adb logcat > logcat.txt" and then turning on the device, I left it loading for around a minute:

pastebin.com/WpDSKbtt

If anyone has any suggestions how I can fix this issue, please let me know!
 
Virucyde,

Can you tell us what might have happened or been done on/to the device just prior to the bootloop?

Knowing what might have happened or was the trigger is certainly key to helping figure-out how you might be able to fix it.

Also, are you rooted? (you might have some options if you are, not so much if you are not)

I sort of think you're device is rooted or at least running an engineering build since I see "Running ENG build: no pre-dexopt!" in the logcat that you provided.

That message appears just before the 6 instances of "Exception reading jar: /system/framework/maps.jar" which appears to be the first (and repeating) error that demonstrates your bootloop.

Also, you said you tried some adb combos to get into recovery, does that include "adb reboot recovery", "adb reboot bootloader", and "adb reboot-bootloader"? My thought here is to help you get to a place to attempt a factory reset (although that's not guaranteed to help). You could also have a hardware (memory?) issue.

Fixing this might still be very difficult...

Hope that helps a little.
 
From what I can tell the problem began happening when the power button got held down in a carrying case, I believe this forced a hard shutdown.

I am quite certain it's a rooted device, since I've been able to install any apk and make any modification without problems (I was able to pull the sys directory, if that proves anything). It was purchased in Uruguay and appears to be a Boxchip A13 Chinese tablet (XION XI-TAB700). That leaves me assuming it came rooted.

I tried adb reboot-bootloader and adb reboot recovery, both simply rebooted the device and it continued with its bootloop. The device has an embedded reset button on the back, but all combinations I've attempted with it appear to simply power off and power on the tablet. I don't believe there's a boot menu for this tablet, nor a recovery mode.

I emailed the manufacturer(XION) in Portuguese, Spanish, and English, and a week later I still have no response, and I don't think there's any ROM support for it online, I can't seem to find anyone else with the same tablet, the Chinese Allwinner Boxchip A13 looks different, even though it uses the same specs.

At this point my plan is to attempt wiping the cache(I'll have to look that up online) and from there I'm hoping that maybe someone has some ideas for maybe file replacements that could get it working again.

Thanks for responding!

EDIT: Cleared cache, still looping :( But I verified that I do indeed have root access.
 
I decided to mess around a little bit with the maps.jar, since the IO Exception appears to happen there.

Here's the actual file, attached, I was able to extract it inside of Windows after pulling it, but I don't know if that's a true test of whether it's corrupt or not.

I tried replacing it with this maps.jar file:
java2s.com/Code/Jar/c/Downloadcomgoogleandroidmapsjar.htm

I made sure to get the permissions correct as well with chmod, but while the IOException has disappeared, I now get a NullPointer, although it may be simply because I'm using the wrong maps.jar. here's the new error log:
mediafire.com/view/7ntbmb2kbquixud/ne2wlog2.txt
 

Attachments

Yeah, that might be tough to identify and find exactly the right version of the file in question--if indeed the file is the issue since it could also be a hardware issue (bad memory block, etc.).

Since you've got root and adb access, you've got the tools you need to help you try to figure this.

There's also the "getprop" command you can run which will tell you all kinds of information about your device, including Android version and possibly the board, maker, etc. that might help you find the proper stock system files:

c:> adb shell getprop
Click to expand...

or

c:> adb shell
$ getprop
Click to expand...

or

$ su
# getprop
Click to expand...

:thumbup:
 
[dalvik.vm.heapsize]: [48m]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[debug.egl.hw]: [1]
[hwui.render_dirty_regions]: [false]
[init.svc.adbd]: [running]
[init.svc.bootanim]: [running]
[init.svc.dbus]: [running]
[init.svc.debuggerd]: [running]
[init.svc.drm]: [running]
[init.svc.installd]: [running]
[init.svc.keystore]: [running]
[init.svc.media]: [running]
[init.svc.netd]: [running]
[init.svc.prein_disable]: [stopped]
[init.svc.ril-daemon]: [running]
[init.svc.servicemanager]: [running]
[init.svc.surfaceflinger]: [running]
[init.svc.u3gmonitor]: [running]
[init.svc.vold]: [running]
[init.svc.zygote]: [running]
[media.cedarx.chipver]: [5]
[net.bt.name]: [Android]
[net.change]: [net.tcp.buffersize.gprs]
[net.tcp.buffersize.default]: [4096,87380,110208,4096,16384,110208]
[net.tcp.buffersize.edge]: [4093,26280,35040,4096,16384,35040]
[net.tcp.buffersize.gprs]: [4092,8760,11680,4096,8760,11680]
[net.tcp.buffersize.hspa]: [4094,87380,262144,4096,16384,262144]
[net.tcp.buffersize.lte]: [524288,1048576,2097152,262144,524288,1048576]
[net.tcp.buffersize.umts]: [4094,87380,110208,4096,16384,110208]
[net.tcp.buffersize.wifi]: [524288,1048576,2097152,262144,524288,1048576]
[persist.sys.country]: [US]
[persist.sys.language]: [en]
[persist.sys.localevar]: []
[persist.sys.profiler_ms]: [0]
[persist.sys.strictmode.disable]: [1]
[persist.sys.strictmode.visual]: [0]
[persist.sys.timezone]: [America/Sao_Paulo]
[persist.sys.usb.config]: [mass_storage,adb]
[ro.allow.mock.location]: [1]
[ro.baseband]: [unknown]
[ro.board.platform]: [exDroid]
[ro.bootloader]: [unknown]
[ro.bootmode]: [unknown]
[ro.build.characteristics]: [tablet]
[ro.build.date.utc]: [1364893115]
[ro.build.date]: [Tue Apr 2 16:58:35 CST 2013]
[ro.build.description]: [nuclear_evb-eng 4.0.4 IMM76D 20130402 test-keys]
[ro.build.display.id]: [nuclear_evb-eng 4.0.4 IMM76D 20130402 test-keys]
[ro.build.fingerprint]: [softwinners/nuclear_evb/nuclear-evb:4.0.4/IMM76D/20
02:eng/test-keys]
[ro.build.host]: [yyb]
[ro.build.id]: [IMM76D]
[ro.build.product]: [nuclear-evb]
[ro.build.tags]: [test-keys]
[ro.build.type]: [eng]
[ro.build.user]: [along]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [20130402]
[ro.build.version.release]: [4.0.4]
[ro.build.version.sdk]: [15]
[ro.carrier]: [unknown]
[ro.com.android.dateformat]: [MM-dd-yyyy]
[ro.config.alarm_alert]: [Alarm_Classic.ogg]
[ro.config.notification_sound]: [pixiedust.ogg]
[ro.config.ringtone]: [Ring_Synth_04.ogg]
[ro.crypto.fs_flags]: [0x00000406]
[ro.crypto.fs_mnt_point]: [/data]
[ro.crypto.fs_options]: [barrier=0]
[ro.crypto.fs_real_blkdev]: [/dev/block/nande]
[ro.crypto.fs_type]: [ext4]
[ro.crypto.state]: [unencrypted]
[ro.debuggable]: [1]
[ro.factorytest]: [0]
[ro.hardware]: [sun5i]
[ro.kernel.android.checkjni]: [0]
[ro.opengles.version]: [131072]
[ro.product.board]: [nuclear]
[ro.product.brand]: [softwinners]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [nuclear-evb]
[ro.product.firmware]: [1.5]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [unknown]
[ro.product.model]: [XI-TAB700]
[ro.product.name]: [nuclear_evb]
[ro.property.tabletUI]: [true]
[ro.revision]: [41275]
[ro.secure]: [0]
[ro.serialno]: []
[ro.setupwizard.mode]: [OPTIONAL]
[ro.udisk.lable]: [XION]
[ro.wifi.channels]: []
[sys.usb.config]: [mass_storage,adb]
[sys.usb.state]: [mass_storage,adb]
[system_init.startsurfaceflinger]: [0]
[wifi.interface]: [wlan0]
[wifi.supplicant_scan_interval]: [15]
Click to expand...

There's the output, any ideas? What are the key bits of information here?

There appear to be a couple builds online with the same number, but different dates for the build, not sure if it's safe to use them, also, how do I apply a build through ADB? When I find the right one, of course.
 
These are/were the "interesting" items that might help you in your search for files, ROMs, help, etc.:

[ro.board.platform]: [exDroid]
[ro.build.display.id]: [nuclear_evb-eng 4.0.4 IMM76D 20130402 test-keys]
[ro.build.fingerprint]: [softwinners/nuclear_evb/nuclear-evb:4.0.4/IMM76D/2002:eng/test-keys]
[ro.build.version.release]: [4.0.4]
[ro.product.board]: [nuclear]
[ro.product.brand]: [softwinners]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [nuclear-evb]
[ro.product.model]: [XI-TAB700]
[ro.product.name]: [nuclear_evb]
Click to expand...

(but I see your edit above that you've already started looking, using some of the key values above)

I'm not sure how specific (or actually helpful) I can be here, Virucyde :(, since I don't have your device or the root- or stock-related files for it.

If you could identify and get a hold of a custom recovery for your device, I could tell you how to manually flash it (using flash_image or dd) [assuming we could identify your recovery partition]. Then you ought to be able to find and flash a stock ROM (if you could find one).

Otherwise, you're basically limited to guessing and updating various files one-by-one (not a pleasing prospect, I know).
 
So I found a build with a really similar name online (docs.google.com/file/d/0B9yfbmrBB-rBb1oxc2NlTzZYTDg/edit?pli=1) Just a different date on the build, since it appears a build with my date doesn't exist(Am I the only one to have ever bought this tablet?!)

At this point my plan is to do just that, replacing files(more likely directories) one by one to see if I can get it fixed. Any hints on an intelligent way to go about that?

Specifically, are there any directories that tend to be device-specific and therefore shouldn't be touched, vs others that could definitely be replaced without issue?

BETTER QUESTION:
How do I extract the IMG file in Windows? I can't seem to get the files out of it. I found this: forum.xda-developers.com/showthread.php?t=2294909

But it EXT4 unpacker isn't recognizing the format.
 
Yeah, that file does indeed look very similar to some of the getprop info from above.

I downloaded it on my Linux PC and tried unpacking the .img file to no avail...neither unyaffs (results in "broken image file") nor simg2img (results in "bad magic") worked :(.

:dontknow:
 
I suspected the ROM might have just been bad...

This one's name is a bit worse, but it's as close as I'm seeing now: filefactory.com/file/15k90z4rncyl/n/A13_MID_nuclear_pfdq88c-eng-IMM76D-Factory_Image_TechKnowForum.net_.7z

EDIT: Ext4 Unpacker isn't opening this one either, I unfortunately don't have access to a Linux machine at the moment, so I can't try out the standard methods.
 
I think I may have just successfully bricked it permanently. Well, fixing it was a longshot anyway :(

I can no longer abd shell into it, I get a permission denied to /system/bin/sh. Is there a way I can fix this at this point? I can still push files, and I pulled the entire root folder before messing with anything.

However, I just discovered how dumb I was not to make a an adb backup before messing with anything..

So.. At this point I'm thinking it's time to just start trying to flash the device with whatever custom ROMs look like they might work. How do I go about doing that, considering I have no stock ROM and no boot loader?
 
You must log in or register to reply here.
Back
Top Bottom