The phone is OPPO r7 plus(china mobile).After I make a CM-12.1 ROM for my phone,I flash the Rom to my phone.But my phone can not enter into the new system,and it just looping boot animaton,so I executed "adb shell >> /sdcard/log.txt" to get log,some mistakes are
I/aee/core_forwarder( 3517): compress_files: complete save fileROCESS_COREDUMP with size 121638912 to /data/core/zcore-3515.zip
W/art ( 3502): Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Failed to generate image '/data/dalvik-cache/arm/[email protected]@boot.art': Failed execv(/system/bin/dex2oat --image=/data/dalvik-cache/arm/[email protected]@boot.art --dex-file=/system/framework/core-libart.jar --dex-file=/system/framework/conscrypt.jar --dex-file=/system/framework/okhttp.jar --dex-file=/system/framework/core-junit.jar --dex-file=/system/framework/bouncycastle.jar --dex-file=/system/framework/ext.jar --dex-file=/system/framework/framework.jar --dex-file=/system/framework/telephony-common.jar --dex-file=/system/framework/voip-common.jar --dex-file=/system/framework/ims-common.jar --dex-file=/system/framework/mms-common.jar --dex-file=/system/framework/android.policy.jar --dex-file=/system/framework/apache-xml.jar --dex-file=/system/framework/oppo-framework.jar --dex-file=/system/framework/mediatek-common.jar --dex-file=/system/framework/mediatek-framework.jar --
How can I resolve these problems?
Related
Hello guys, I have a little problem with developing apps in my phone.
I installed Stock Android 4.1.2 v4 for my Xperia U ST25i ( http://forum.xda-developers.com/showthread.php?t=2284394 ) (I wanted to post this issue in this thread but i'm new here and I just can't... anyways, rules are rules), and i'm have some issues when I want test APK's in my phone via ADB or Eclipse-ADT.
When I click excecute ( or do adb install), the process will fail, showing me that:
Code:
[2013-07-23 16:40:48 - AWifiSignal] ------------------------------
[2013-07-23 16:40:48 - AWifiSignal] Android Launch!
[2013-07-23 16:40:48 - AWifiSignal] adb is running normally.
[2013-07-23 16:40:48 - AWifiSignal] Performing net.elsemieni.awifisignal.SplashActivity activity launch
[2013-07-23 16:40:48 - AWifiSignal] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2013-07-23 16:40:51 - AWifiSignal] WARNING: Unknown device API version!
[2013-07-23 16:40:51 - AWifiSignal] Uploading AWifiSignal.apk onto device 'YT9002B59S'
[2013-07-23 16:40:52 - AWifiSignal] Installing AWifiSignal.apk...
[2013-07-23 16:40:53 - AWifiSignal] Installation failed due to invalid APK file!
[2013-07-23 16:40:53 - AWifiSignal] Please check logcat output for more details.
[2013-07-23 16:40:53 - AWifiSignal] Launch canceled!
In simple words, doesn't install beacuse [INSTALL_FAILED_INVALID_APK] error code.
Of course, i have Debugging activated in my phone and install 3rd party applications.
By the way, Logcat gives me that
Code:
07-21 18:05:23.663: W/zipro(25492): Unable to open zip '/data/local/tmp/AWifiSignal.apk': Permission denied
07-21 18:05:23.673: W/PackageParser(25492): Unable to read AndroidManifest.xml of /data/local/tmp/AWifiSignal.apk
That's curious I can't write inside it. I searched the forums and I applied a workaroud solution (http://forum.xda-developers.com/showthread.php?p=40040546&postcount=4), to make a link from tmp to sdcard folder. It worked in this way, but ruined the phone sys after reboot ( crashes randomly, most critical app's frezzes, etc), so doesn't work.
I know that's a firmware bug, but... any ideas about this? There's another workaround to make tmp safely writable, or any way to change the folder who ADB uses to install apps remotely?
Thanks! :laugh:
A few years ago, my bro has set a pattern lock for his old "G-Tide E66", then the phone was left abandoned. Now, I need this phone for some reason.
Info:
1- USB Debugging disabled.
2-Volume Up/Down corrupted.
3-Wifi / Mobile data are turned off.
Details:
- I get to the pattern screen.
-Andriod: Chocolate II
-Drop down menu, not working from the lock screen.
- No shareit to try open Wifi glitch.
Trials:
1-I tried looking for a pinhole to reset the phone ( Couldn't find where it is.)
2- Using Andriod Debug Bridge (ADB):
adb reboot recovery ( I got No command, Fixed it by holding the power button. then stuck in the recovery with corrupted volume down, I thought of triggering the key event from adb)
adb shell input keyevent 25 (25 = VOLUME_DOWN) ( I got this error: - exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) - Not sure about solution so I thought of another method.)
3-Using FastBoot:
adb reboot bootloader ( the phone reboots in recovery mode)
fastboot devices ( the device shows)
fastboot -w ( Loading for about 9 hours in "erasing 'user data'...." , I got this error: "FAILED TO read user data too many links" , I saw suggestions about rebooting the device, PC connecting to another socket ( In my case I have 5 , 2 of which are SS v3) triple failure.)
Other manual erases like:
fastboot erase cache (fail too).
4- Using Android Multi Tools v1.02b FAISAL JEE from SE-Thiland.
Reset Face/PIN Lock : rm failed for /data/system/password.key, Permission denied
Reset Face/Gesture Lock: rm failed for /data/system/gesture.key, Permission denied
Reset GMail:
rm failed for /data/data/com.android.providers.settings/databases/settings.db, Permission denied
rm failed for /data/data/com.android.providers.settings/databases/settings.db-shm, Permission denied
rm failed for /data/data/com.android.providers.settings/databases/settings.db-wal, Permission denied
Wipe Data/cache:
erasing 'cache' (forever.)
Wipe Data:
Wiping /data
Error opendir'ing /data 'Permission denied'
Done wiping /data
5- Looking for G-Tide reset code , I failed too ( Found None and I got Not Emergency number pop up).
6- Using the wisdom " When you are stuck , start to F***" , I started typing random ****, eventually failed too.
7- Calling 999 and trying to unlock fails.
8- Rooting using superSU
I tried this command not sure if correct:
adb install <PATH of SuperSU.apk>
"com.noshufou.android.su.apk"
I got success and not sure what to do next.
9- Recovery img:
fastboot flash recovery < RECVERY IMG>
I used this
cm-13.0-20160901-NIGHTLY-d851-recovery.img
Result:
sending 'recovery' (11648 KB)...
OKAY [ 0.373s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.392s
10- MirrorGO software.
11- Google Android Manager , apparently no internet so no luck too.
12- <I didn't try this> Installing a ROM
not really sure if that will work or screw everything, any ideas and how to install ?
is it ?
adb install <PATH of ROM.zip>
NOTE: I know the phone is dirt cheap , but I have to unlock it whatever the hell I do.
NOTE: If you think you can help through operating my PC through TeamViewer, give it a try.
I will connect the phone and you do the job.
NOTE: It seems like I have a masterpiece no info regarding E66, like the company created a single device.
Thanks in advance.
Hi everyone,
I have recently been trying to port Ubuntu Touch to our beloved surnia.
I'm using the phablet-5.1 tree with AOSP-5.1 device, vendor, kernel and other repositories.
I managed to finish the build with the kernel config adapted to work with Ubuntu. (using jamino's phablet-porting-scripts (on github) and patching some files about uid/gid errors). But this isn't the problem, the default defconfig causes the same problems.
I can confirm my kernel/e3 recovery both work and can mount partitions etc, but only when I'm using the
Code:
fastboot boot recovery.img
command AND my custom boot.img isn't flashed to the device.
When trying to boot the recovery directly from the phone I get a
Code:
Error: Failed to load kernel!
error message in the bootloader log.
If my boot.img is flashed to the phone, whatever file I try to load with
Code:
fastboot boot
, I get an error from my computer :
Code:
booting...
FAILED (remote failure)
but no error from the phone
I had to replace the prebuilt gcc toolchains in the android source tree with my system's ones, could it cause the problem?
I'm quite new to android development and all so please don't blame me if the fix is obvious.
Thanks in advance
Hey guys,
I made a python script to flash custom logo images as boot logos / charging logos / fastboot logos. This will replace the default Xiaomi startup logos when you reboot or charge your phone.
Requirements:
- Linux/Mac/Win with Python3 installed
- TWRP on your MiMix3
Instructions:
- Go to https://github.com/travisjayday/logo-patcher-mix3
- Download the repo and find logogen.py (this is the python script that patches the logo img)
- Run it with python3 logogen.py and follow the instructions to generate a logo_patched.img
- Move the logo_patched.img to your phone and reboot into TWRP
- Flash it in TWRP onto the Logo partition
- Profit
For more detailed instructions, please read the README.md in the GitHub repo or execute python3 logogen.py --help
Hope you like custom logos!
Have fun!
Thanks for this.
There's something wrong when I tried to patch fastboot image.
Log is below.
C:\logo-patcher-mix3-master>python logogen.py -b new_boot.bmp -f new_fastboot.bmp
Unpacking vendor logo.img file for MiMix3...
Reading bitmap image from new_boot.bmp
Succesfully read bitmap with dimensions (1080x1920x24)
Patching boot image at: 0x5000
Original size: 6220854 bytes
Replacement size: 6220856 bytes
Patched boot logo successfully...
Patching unlocked image at: 0x7b8000
Original size: 6220854 bytes
Replacement size: 6220856 bytes
Patched unlocked logo successfully...
Reading bitmap image from new_fastboot.bmp
Succesfully read bitmap with dimensions (558x992x24)
Traceback (most recent call last):
File "logogen.py", line 155, in <module>
main()
File "logogen.py", line 44, in main
if dim != dimens["fast"][1]:
KeyError: 'fast'
Click to expand...
Click to collapse
Ah~ Find it!You should type fastboot instead of fast in line 44&45.XD
@Seraph_X thanks for finding and letting me know of this error!
Anyone have any already modded boot logos, that i can just flash?
Hi, I have the phone at MIUI 11, I tried to do this, and it didn't work, luckily I don't have a brick now, hahahahaha.
I got an error message, I didn't know what it said exactly, and it continued with the normal start.
The error appeared, because in twrp the logo partition doesn't appear, so I did it from ADB.
Any ideas?
Thank you.
Done.
It was just a procedural error.
To avoid this, the ideal is that whoever makes this kind of script, make the step-by-step tutorials for donkeys, like me.
I've found a lot of "tutorials" to flash all kinds of things, and unfortunately most of them don't explain almost anything -
We newcomers must beg for help, which in most cases is denied because it is taken for granted what most people do not know.
While it is true that you should not do anything you do not know, it is also true that those who share should be more talkative, and leave everything prepared for those who wish to enjoy their work.
Greetings.
I just realized that my mi mix 3 boot logo become apple logo, i never have bootloader unlocked and just upgraded to miui 11 weeks ago
Is there some kind of virus that did this?
Is anyone successful in loading modded system.img to a system-as-root device like Pixel 2+? With the nexus 5x I use to make some changed to the build.prop and init.rc to get adb on boot/OOBE but due to the new system-on-root with the Pixel devices, I need to modify the system image. I bought the paid version of Kitchen to do just that, and I can build an image (signed and non-signed... not sure the difference, so I've tested both). Below are the steps I've used but the device always fails to load after.
boot-slot: a
Console: DISABLED
Secure Boot: yes (Production)
Device state: unlocked
"ERROR: LoadImageAndAuth Failed: Load Error"
Code:
1. Download Pixel2 8.1.0 firmware from google
2. Pull the system.img
3. Run Kitchen tool and create a new project
4. add the system.img to the project folder
5. Extract the system image (#4 Extract for new rom)
6. Give it a name: TEST
7. Which perm type would you like to use?: #4 raw_img
8. Don't make any changes yet.... testing to see if it can load
9. Go to #8, -> #7 Build Menu -> #2 build ext4 img -> #1 system -> #2 sparse -> #4 system.img
Code:
fastboot flash system_a C:\Users\username\Desktop\Pixel2_Images\system_new.img
fastboot flash system_b C:\Users\username\Desktop\Pixel2_Images\system_new.img
and/or
Code:
fastboot flash system C:\Users\username\Desktop\Pixel2_Images\system_new.img
and/or
Code:
1. rename system_new.img to system.img
2. Repack the system.img in the Pixel Firmware zip
3. Run flash-all.bat
Update 1:
I have also tried the following.
Code:
1. Boot Pixel 2 Image from firmware site
2. Reboot device into recovery mode
2. Wait till you see a Android icon with !
3. Hold Power and hit up arrow
4. Select Wipe data/factory reset
5. When it boots to OOBE, reboot to bootloader
# load the latest TWRP.img
6. fastboot boot C:\Users\username\Downloads\twrp-3.3.0-0-walleye.img
# Device will boot once to TWRP
# Select Wipe -> swipe for factory reset
7. adb push <The image i created using Kitchen> /sdcard/Download
8. select Install and select the Image
Device Boots with error "Can't load Android system. Your data may be corrupt."