Related
I upgraded my XDA Exec with the new ROM 1.30.162 WWE and Activesync 4.1 but each time I sync, I get a "bad_pool_header" error on a blue background which crashes my machine.
I installed Activesync 4.1 on another laptop to check if this problem was due to drivers etc on my main laptop, and discovered that the device syncs with no problems. There is, therefore, a conflict between the new Activesync 4.1 or the new ROM, and something on my main laptop.
Has anyone come across this problem?
Thanks
The problem is definitely on your PC. Reinstall motherboard drivers, reflash bios, remove antivirus, reinstall windows, etc.
Thanks - pretty drastic...!
Is there a short cut? ie reinstalling drivers one by one? If so, which are likely to be the main culprits? Motherboard? Broadband modem? etc
The error code after reboot of the laptop is:
BC code 19 BCP1:00000020 BCP2: 89A76000 BCP3: 89A766C0 BCP4: 0AD8000
OS Ver 5_1_2600 SP: 2_0 Product 256_1
\WER22c7.dir00\Mini052506-06.dmp
\WER22c7.dir00\sysdata.xml
Does this reveal anything that could explain which driver?
Thanks
10860 said:
Does this reveal anything that could explain which driver?
Click to expand...
Click to collapse
no.
You should create a complete crash dump, and use microsoft debugging tools to find faulting driver. Or better reinstall windows.
I looked at the minidump file and used MS debugger, the readout is below. I am not sure if I did the debugging ok, or how to interpret it. Anything useful in the readout?
Thanks
Loading Dump File [C:\Mini052406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed May 24 20:25:34.038 2006 (GMT+1)
System Uptime: 0 days 0:52:32.633
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, 88187000, 881876c0, ad80000}
Probably caused by : Unknown_Image ( nt!KeBugCheck2+4d4 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 88187000, The pool entry we were looking for within the page.
Arg3: 881876c0, The next pool entry.
Arg4: 0ad80000, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: 88187000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 00000000 to 8053331e
STACK_TEXT:
f78cab74 00000000 00000000 00000000 00000000 nt!KeBugCheck2+0x4d4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeBugCheck2+4d4
8053331e ?? ???
FAULTING_SOURCE_CODE:
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KeBugCheck2+4d4
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: ZEROED_STACK
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------
Nothing useful, minidump does not have enough information
It is very difficult to debug pool corruptions.
Hello
I am working directly with AT commands on my phone. For example: AT$GSM?\r for the GSM page of the FieldTest application.
I wrote a little app which call the command "AT$GSM?\r". The app is running nicely on a HTC Magic 32 B (CM 7) and a Nexus One (CM 9). Now I installed it on the CM10 on my HTC One X. But I only get the response +CME ERROR: 100.
The detailed "logcat -b radio" output is:
AT$GSM?\r
(t=1357078390)>> AT$GSM?\r
D/HTC_RIL ( 161): TX::> AT$GSM?\r
}/RILJ ( 698): [3691]< OEM_HOOK_STRINGS {UNIAT, +CME ERROR: 100
When I call the RIL through the byte commands I get the error:
< OEM_HOOK_RAW error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
At the moment I use CM9 with baseband-version: 2.1204.119.17
In FASTBOOT is the information:
RADIO-1.1204.105.14
MODEM PATH: OFF
Does anybody has an idea how to solve it?
Felix
Hi Felix,
FelixGroup said:
OEM_HOOK_STRINGS {UNIAT, +CME ERROR: 100
Click to expand...
Click to collapse
Did you ever resolve this?
CME ERROR: 100 is labelled as "unknown" in the 3GPP 27.007 docs, so it means that your script is working but perhaps that AT command/device is not enabled on that device. Usually ATCoP on Qualcomm MSM8960 can be easily customized by OEM. Since HTC love to customize everything, perhaps its a RIL thing. Many RILs can be made to "interpret" AT commands, and thus they either don't reach CP at all, and is faked by RIL in AP, or reformatted or blocked. Basically anything can happen. Did you try some other AT commands and see if something changes.
[Q&A] [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Q&A for [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
alarm clock
Recently discussed the problem that the included headphones alarm clock rang only from external speakers. Now it rings only from the headphones. But it would be optimal to it when headphones are connected rang simultaneously and external speakers and headphone out. So it is correct and it is so sold on the official firmware.
Sorry for my bad English.
Del
---------- Post added at 03:30 AM ---------- Previous post was at 03:24 AM ----------
Hi, will snapshot m12 for LTE?
Do you just dirty flash the nightlife? I tried going the update route but it doesn't work.
Hi all!
First of all thank you for the Roma and the whole tutorial is perfect on my side on my "tab pro lte"
I would like to know how to overclock the processor above its Standard power?
sorry for the mistakes, I'm French and I use google translation ... oO
thank you!
No mobile data
Thanks to the dev for his continuous efforts on this rom, keep up the good work. However, i noticed that mobile data doesn't work for 2g networks. I've tried using the "preferred network type" and even changing the sim but it still won't work. When i get into 3g or LTE zonse the mobile data begins to work. Please could you suggest a fix. I'm currently limited to 2g so it would be a big help. Thanks
Any hints on building CM12 for this device ? I'm willing to do it if there is any documentation help.
Firmware crude
CM-12 test
Deleted
DensonX said:
Sorry if this is off-topic, but I have seen a lot of people requesting CyanogenMod 12 for this device. I managed to build CM-12 for the mondrianlte, however it does not flash on my device. I get an error saying E: error executing binary in zip. I suspect this may be due to the fact that I have a european Tab Pro, so if anyone with a US Tab Pro LTE wants to try to install it here's a file. https://drive.google.com/file/d/0Bxf2YUR9_3hDX3JUbnJYbWVfTTA/view?usp=sharing
Do NOT forget to backup before attempting to install this, as it likely will not work.
Also if anyone knows how to solve my problem with flashing this please let me know.
Click to expand...
Click to collapse
Please do not post links to other builds in my thread. Especially ones that you can't even flash because it doesn't work for you!
This only adds confusion.
I will try to release something soon. It may have a broken camera (the camera is broken on picassolte and if I can't figure it out I'll have to just leave it broken for both mondrianlte and picassolte for now) but otherwise has been working well for me on picassolte.
SM-T325, CM12 and encryption
Hello,
First Thank you crpalmer for your great work on mondrianlte. I've been using for roughly one month and did not encounter any serious issue, it is working so much better than stock Samsung ROMs ! I only got into problems when trying to encrypt the tablet (with cm-12-20150321-UNOFFICIAL-mondrianlte).
Once the process was started it rebooted very quickly and got stuck on the boot cyanogenmod screen. A forced off/on cycle was able to restore the tablet normal operation, but it had not been encrypted.
Relevant portions of the adb log seem to be :
(just after the beginning of the encrytion process)
Code:
E/Cryptfs ( 243): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
D/Cryptfs ( 243): Just asked init to shut down class main
and later when the tablet reboots :
Code:
D/Cryptfs ( 243): unmounting /data succeeded
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 243): Loading keymaster app failed
E/Cryptfs ( 243): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 243): Failed to init keymaster
--------- beginning of crash
F/libc ( 243): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 315 (vold)
F/libc ( 243): Unable to open connection to debuggerd: Connection refused
I/Vold (26973): Vold 2.1 (the revenge) firing up
D/Vold (26973): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold (26973): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs (26973): Check if PFE is activated on Boot
E/Cryptfs (26973): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs (26973): Error getting crypt footer and key
files /vendor/firmware/keymaster/keymaster.* have permission 644, user/group root, and are symlinks into /firmware/image/. In /firmware/image/, keymaste.* files have permission 440, user system, group drmrpc. Based on the QSEECOMAPI errors above, I am unable to determine whether these access rights are correct. I assume that even if they were, some incorrect SElinux configuration could cause access problems ?
Is anyone able to figure out what is happening ? Is it useful that I post a full log of the process ?
I rooted my SGH-T999, running Android 4.3, flashing TWRP recovery w/ Odin.
The rooting was successful.
Now, on to the part where I ran into trouble.
Problem: I can't successfully install any ROMs for Android M or later.
NOTE: I need Android M or later to have more control over individual apps' permissions.
I tried to flash Pac-ROM through TWRP, like so:
(from TWRP home menu)
1. Wipe>Swipe to Factory Reset
2. Go Back to Home Menu
3. Install>Select pac_d2tmo_MM.Beta.Official_20160920-165602.zip>Swipe to confirm Flash
Note: The first time I tried to flash Pac-ROM, I wasn't aware of GApps. So, I didn't flash it.
4. Reboot
The phone booted to the "Welcome/Language Selection" screen, but I couldn't select a language.
It seems that the UI elements belonging to the "Welcome" screen fail to respond to touch, while other UI elements respond normally (as demonstrated at the end of the video at the URL below).
All attempts to re-flash, since, have included the additional step off adding the GApps zip (for ARM, Android 6.0) to the "ZIP Queue".
However, all attempts end the same way.
I've documented the process in the video @ the following URL: youtu.be/EZTwaURkRSs
Another strange behavior (that isn't apparent in the video) is that, immediately after being shown on the display, the "Welcome" screen looks fine for a few hundred milliseconds or so before the screen is drawn with a yellowish-hue. As if blue-light filtering kicks in (even when the system clock is mid-day).
I also tried to flash a different ROM (Oct-OS OCT-M-R3) on a few of the attempts, but again I observed the same exact behavior ("Welcome" screen's yellowish hue and lack of response to touch).
It doesn't seem to be a hardware issue, because touch does work, just not on the "Welcome" screen.
I'm fairly certain I've selected the correct ROM for the model.
So, what did I mess up?
I am facing similar issue.. i was on carbon rom 7.1.2 and then i thought of downgrading to octos M for xposed and cm theme engine and same thing happened as you faced with both roms (pac and oct os r3) .. i restored my backup of carbon rom 7.1.2 and my screen went black (sod) and i had to flash stock (4.4.2) os to get my phone working again
andynoob said:
I am facing similar issue.. i was on carbon rom 7.1.2 and then i thought of downgrading to octos M for xposed and cm theme engine and same thing happened as you faced with both roms (pac and oct os r3) .. i restored my backup of carbon rom 7.1.2 and my screen went black (sod) and i had to flash stock (4.4.2) os to get my phone working again
Click to expand...
Click to collapse
Do you mean that you were able to flash a ROM successfully, after flashing stock (4.4.2)?
Or, you were ONLY able to flash stock (4.4.2) successfully?
Thank you for the reply,
Gerald
I just restored my twrp backup of stock os .. Had urgent work so couldn't try to flash those ROMs again.. will try them next week
UPDATE:
So, I successfully restored my stock backup.
With the stock setup I experienced no problems.
Since my original post, I've alternated between restoring stock backup and flashing ROMs.
I tried flashing Oct-OS and Pac-ROM, again and again.
I also tried to install LineageOS, as well.
I am able to install CyanogenMod 12.1, but this doesn't meet my requirement of android version 6 or later.
Installation of any of the custom ROMs has resulted in the same behavior demonstrated in the video (youtu.be/EZTwaURkRSs):
- after boot, device fails to respond to touch input
- however, device does accept touch input on some UI objects. so, I don't think it's a screen/hardware issue
How can I debug further?
I'd like to try to capture some sort of boot log, but adb is "offline" during boot process.
And, since I can't make it past the "language selection/welcome" screen, I can't get to settings and enable USB debugging.
UPDATE:
I managed to enable ADB during boot, by using the ADB shell while the device was in recovery mode.
Code:
[email protected] ~ $ adb push ~/.android/adbkey.pub /data/misc/adb/
[email protected] ~ $ adb shell
~# cd /data/misc/adb/
/data/misc/adb# cat adbkey.pub > adb_keys
/data/misc/adb# cd /
~# mkdir /system2
~# mount -o rw /dev/block/mmcblk0p14 /system2 ## NOTE: for this command, had to figure out which partition was the system partition; here it was /dev/block/mmcblk0p14
~# echo "persist.service.adb.enable=1" >> default.prop
~# echo "persist.service.debuggable=1" >> default.prop
~# echo "persist.sys.usb.config=mtp,adb" >> default.prop
~# echo "persist.service.adb.enable=1" >> /system2/build.prop
~# echo "persist.service.debuggable=1" >> /system2/build.prop
~# echo "persist.sys.usb.config=mtp,adb" >> /system2/build.prop
~# ## now press Ctrl-D to exit the ADB shell
NOTE: thanks to @ErnestChia for the following post forum.xda-developers.com/showpost.php?p=63829295&postcount=27
So, I was able to get a logcat during the SetupWizard.
There were 3 lines, related to the SystemUI, that were repeated over and over.
Code:
W BroadcastQueue: Timeout of broadcast BroadcastRecord{51dfd23 u-1 android.intent.action.TIME_TICK} - [email protected], started 10010ms ago
W BroadcastQueue: Receiver during timeout: BroadcastFilter{a4079bf u0 ReceiverList{4b103de 730 com.android.systemui/10018/u0 remote:448f719}}
I ActivityManager: Skipping duplicate ANR: ProcessRecord{768d889 730:com.android.systemui/u0a18} Broadcast of Intent { act=android.intent.action.TIME_TICK flg=0x50000014 (has extras) }
All I've gathered is that SystemUI isn't responding.
Which seems to have started during boot, with the following output.
Code:
W ActivityManager: Timeout executing service: ServiceRecord{dd2251a u0 com.android.systemui/.ImageWallpaper}
E ActivityManager: ANR in com.android.systemui
E ActivityManager: Reason: executing service com.android.systemui/.ImageWallpaper
E ActivityManager: 4.1% 730/com.android.systemui: 2.2% user + 1.8% kernel / faults: 1246 minor 2 major
SystemUI Stack Trace
Code:
Cmd line: com.android.systemui
Build fingerprint: 'samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys'
ABI: 'arm'
Build type: optimized
Zygote loaded classes=3986 post zygote classes=991
Intern table: 46441 strong; 62 weak
JNI: CheckJNI is off; globals=427 (plus 368 weak)
Libraries: /system/lib/libandroid.so /system/lib/libcompiler_rt.so /system/lib/libjavacrypto.so /system/lib/libjnigraphics.so /system/lib/libmedia_jni.so /system/lib/libsoundpool.so /system/lib/libwebviewchromium_loader.so libjavacore.so (8)
Heap: 5% free, 12MB/13MB; 84371 objects
Dumping cumulative Gc timings
Total number of allocations 84371
Total bytes allocated 12MB
Total bytes freed 0B
Free memory 813KB
Free memory until GC 813KB
Free memory until OOME 179MB
Total memory 13MB
Max memory 192MB
Zygote space size 1972KB
Total mutator paused time: 0
Total time waiting for GC to complete: 0
Total GC count: 0
Total GC time: 0
Total blocking GC count: 0
Total blocking GC time: 0
...
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 obj=0x745992a0 self=0xb77f9b30
| sysTid=730 nice=0 cgrp=default sched=0/0 handle=0xb6efab44
| state=S schedstat=( 0 0 0 ) utm=64 stm=14 core=1 HZ=100
| stack=0xbe5d0000-0xbe5d2000 stackSize=8MB
| held mutexes=
native: #00 pc 0004290c /system/lib/libc.so (__ioctl+8)
native: #01 pc 00049391 /system/lib/libc.so (ioctl+14)
native: #02 pc 0001e8c9 /system/lib/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+132)
native: #03 pc 0001eefb /system/lib/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+38)
native: #04 pc 0001f0b1 /system/lib/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+124)
native: #05 pc 0001a0b3 /system/lib/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+30)
native: #06 pc 00089471 /system/lib/libandroid_runtime.so (???)
native: #07 pc 00db9189 /data/dalvik-cache/arm/[email protected]@boot.oat (Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+140)
at android.os.BinderProxy.transactNative(Native method)
at android.os.BinderProxy.transact(Binder.java:503)
at android.hardware.ICameraService$Stub$Proxy.getCameraCharacteristics(ICameraService.java:421)
at java.lang.reflect.Method.invoke!(Native method)
at android.hardware.camera2.utils.Decorator.invoke(Decorator.java:80)
at java.lang.reflect.Proxy.invoke(Proxy.java:393)
at android.hardware.ICameraService.getCameraCharacteristics(ICameraService.java:-2)
at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:635)
at android.hardware.camera2.CameraManager.getCameraIdList(CameraManager.java:99)
- locked <0x0da89d30> (a java.lang.Object)
at com.android.systemui.statusbar.policy.FlashlightController.getCameraId(FlashlightController.java:126)
at com.android.systemui.statusbar.policy.FlashlightController.<init>(FlashlightController.java:62)
at com.android.systemui.statusbar.phone.PhoneStatusBar.makeStatusBarView(PhoneStatusBar.java:1087)
at com.android.systemui.statusbar.phone.PhoneStatusBar.addStatusBarWindow(PhoneStatusBar.java:3285)
at com.android.systemui.statusbar.phone.PhoneStatusBar.createAndAddWindows(PhoneStatusBar.java:3281)
at com.android.systemui.statusbar.BaseStatusBar.start(BaseStatusBar.java:619)
at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:800)
at com.android.systemui.statusbar.SystemBars.createStatusBarFromConfig(SystemBars.java:106)
at com.android.systemui.statusbar.SystemBars.onNoService(SystemBars.java:58)
at com.android.systemui.statusbar.ServiceMonitor.startService(ServiceMonitor.java:230)
at com.android.systemui.statusbar.ServiceMonitor.-wrap5(ServiceMonitor.java:-1)
at com.android.systemui.statusbar.ServiceMonitor$1.handleMessage(ServiceMonitor.java:73)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5466)
at java.lang.reflect.Method.invoke!(Native method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
i solved this issue by flashing the pac rom 6.0 from at&t . (Flash only the rom )
Do you have a copy of carbon ROM or Pac man for the d2tmo?
Central project page
[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1 [Alpha]
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :) Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you! Official site...
forum.xda-developers.com
09.02.2022
android-12.0.0_r28 (February security patchlevel)
OEMv1c support
Click to expand...
Click to collapse
14.02.2022
hotfix for the bootloop
Click to expand...
Click to collapse
30.03.2022
android-12.1.0_r1 (March security patchlevel)
Click to expand...
Click to collapse
MartinX3 said:
30.03.2022
Click to expand...
Click to collapse
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1
Carljaynp03 said:
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1
Click to expand...
Click to collapse
It's 90% aosp.
Please report any bug in the linked issue tracker.
MartinX3 said:
It's 90% aosp.
Please report any bug in the linked issue tracker.
Click to expand...
Click to collapse
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please
Carljaynp03 said:
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please
Click to expand...
Click to collapse
Thank you, please follow the link in the first post.
There it is also in the first post.
12.04.2022
android-12.1.0_r3 (April security patchlevel)
Click to expand...
Click to collapse
Bug....the touch does not work and it seems to reboot intermittently
Mint rhfo said:
Bug....the touch does not work and it seems to reboot intermittently
Click to expand...
Click to collapse
Bug....report?
MartinX3 said:
Bug....report?
Click to expand...
Click to collapse
Yeah! It's Bug report!
Mint rhfo said:
Yeah! It's Bug report!
Click to expand...
Click to collapse
I don't see a valid bug report according to the instructions.
Or you claim that I'm god and know everything.
But maybe I'm god, who knows.
Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!
BigWoodFarmer said:
Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!
Click to expand...
Click to collapse
Hey,
I'm sorry and fixed the type.
There was a wrong whitespace character in the manual.
It's `oem_a`, that's correct.
Did you flash everything and wiped the userdata before?
Because other XZ2C owners were able to post logs.
Also it is mandatory to run the latest stock firmware on both slots once before in the lifetime of your phone.
Hi,
Thank you for your fast reply. I flashed everything and wiped as described with "fastboot -w"
I am unsure what you mean by both slots, you mean Firmware and Software Content Erase? I used EMMA to flash: H8324 52.1.A.0.618 Customized_UK 1313-5469 R3C User-Live COM on the device.
Some other questions I had:
a) Do I need Magisk for root on the device?
b) can I use another Version the twrp 3.4.0.0.? If I install this to my recovery partition, I can't use it when booting since the screen seems frozen.
sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all
BigWoodFarmer said:
sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all
Click to expand...
Click to collapse
Nice that you achieve to flash it.
The camera is currently not implemented because of the russian invasion in the ukraine.
Code:
04-12 19:02:48.363 0 0 I init : starting service 'vendor.camera-provider-2-4'...
04-12 19:02:48.451 3114 3114 I [email protected]: [email protected] legacy service is starting.
04-12 19:02:48.452 3114 3114 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.453 3114 3114 D hw-ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.452 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc44 returned -22
04-12 19:02:48.453 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc24 returned -22
04-12 19:02:48.489 3114 3114 E [email protected]: Could not load camera HAL module: -2 (No such file or directory)
04-12 19:02:48.489 3114 3114 E [email protected]_64: getProviderImpl: camera provider init failed!
04-12 19:02:48.490 3114 3114 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xb400007a624ceaa0)
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::getCurrentInternal not linked, returning null
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::logStackInternal not linked
04-12 19:02:48.492 3114 3114 E HidlServiceManagement: Could not find instance 'legacy/0' in library [email protected] Keeping library open.
04-12 19:02:48.493 3114 3114 E LegacySupport: Could not get passthrough implementation for [email protected]::ICameraProvider/legacy/0.
04-12 19:02:48.501 0 0 I init : Service 'vendor.camera-provider-2-4' (pid 3114) exited with status 1
04-12 19:02:48.501 0 0 I init : Sending signal 9 to service 'vendor.camera-provider-2-4' (pid 3114) process group...
04-12 19:02:48.501 0 0 I libprocessgroup: Successfully killed process cgroup uid 1047 pid 3114 in 0ms
04-12 19:02:48.504 0 0 E init : process with updatable components 'vendor.camera-provider-2-4' exited 4 times in 4 minutes
04-12 19:02:48.513 0 0 I init : processing action (sys.init.updatable_crashing=1) from (/system/etc/init/flags_health_check.rc:10)
04-12 19:02:48.514 0 0 I init : starting service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)'...
04-12 19:02:48.541 0 0 I init : SVC_EXEC service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)' pid 3115 (uid 1000 gid 1000+0 context default) started; waiting...
04-12 19:02:48.564 3115 3115 I flags_health_check: ServerConfigurableFlagsReset reset_mode value: 1
04-12 19:02:48.565 3115 3115 I flags_health_check: ServerConfigurableFlagsReset updatable crashing detected, resetting flags.
Please subscribe to
[Tama][XZ2C][AOSP12][4.19] Apollo camera provider init failed (every 5secs) · Issue #751 · sonyxperiadev/bug_tracker
Platform: Tama Device: XZ2C (apollo) Kernel version: 4.19.188-ge73c1a837c4f-dirty Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a (latest official Sony...
github.com
[Tama][4.19][AOSP12] Device reboots for no clear reason any time it is not idle · Issue #755 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a Description The device reboots after a few minutes o...
github.com
[TAMA][12][4.19] Bootloop · Issue #748 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: 12 Software binaries version: v1c Previously working on Stock Description Bootloop and no ADB logs available. The device was flas...
github.com
and firstly this will get fixed: https://github.com/sonyxperiadev/bug_tracker/issues/770
20.05.2022
android-12.1.0_r5 (May security patchlevel)
Click to expand...
Click to collapse
Because of problems with the ftp server the new release is on google drive.
Click to expand...
Click to collapse
Hello, what changes between this rom and the stock based roms ?