Hi,
Recently my phone has been acting up, I tried reflashing the rom I was using (http://forum.xda-developers.com/showthread.php?t=1768702) but strangely it won't wipe or factory reset. I've googled the problem a bit but is seemed the only solution was to reflash a stock sbf. For the last couple of days I've been trying to flash a sbf using RSD Lite 4.9 but it won't flash. I keep getting the following errorlog:
13:13:59, February 19, 2013
Line: 902
ERROR: The file selected is an invalid superfile.
Please enter in a valid superfile.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashFileIO.cpp
13:13:59, February 19, 2013
Line: 1824
ERROR: Error validating image files.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_Flash.cpp
Device ID: 0
13:14:46, February 19, 2013
Line: 902
ERROR: The file selected is an invalid superfile.
Please enter in a valid superfile.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashFileIO.cpp
13:14:46, February 19, 2013
Line: 552
ERROR: The superfile specified does not exist
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse
I've tried relocating, renaming the sbf file and reinstalling drivers even on a fresh windows install. On google I've found one guy (http://www.android-hilfe.de/root-ha...y/75504-loesung-fuer-rsd-lite-0x7100-usw.html) that seemed to have the same problem unfortunately its in german and I can't really make out what the solution was.
I hope someone can help with this, its been bugging me like crazy!
Found this http://androidforums.com/droid-all-...ed-flashing-process-0x7100-in-rsd-lite-2.html
Hey intemptesta,
I also found that thread but unfortunately it seems like its something else then the problem rezo was facing, I'm truly lost on how to fix it.
Related
Hi there,
When I'm installing the rom ([ROM][31.01.2011][WWE-ITA-FRA-ELL-GER-RUS-SPA-NLD-DAN] ver 2.30 nsourm -build 23152), I get the following error:
ERROR [224] : Device not responding
This happens on WinXPx86 and Win7x64. No topic delivers an usefull answer.
I have used several roms from nsourm build 23152, but non were effective.
Is this a known issue, and does anyone have a solution for this?
With kind regards,
Raizy
Solved
I solved the issue due unpacking the DSL_SSP_MINI.zip with winrar.
Started the installation on a WinXP machine.
First time i got in the 3 colored screen and got again an error:246
Unchecked the following settings: start-->settings-->others-->USB-PC , both marks.
2nd time the installation did go complete!
I have the Nexus 4 and I'm getting a really annoying error. I had the latest pre-KitKat stock ROM on it yesterday. I received the KitKat OTA update and proceeded to install it. It installed fine and went through the application optimisation steps and once it did it's final reboot it came up with an "Unfortunately, the process android.process.acore has stopped". I've got options to Report or click Ok. Clicking Ok will just bring the message back often immediately but sometimes with a few seconds gap. I could interact with the UI between dialogs but literally have split seconds so made navigation extremely slow (i.e. takes a dozen attempts sometimes to click on something behind the dialog).
I've tried a full factory resetting from the phone menu and from the recovery menu, both have done nothing. The phone continues to display the error as soon as the phone boots up after the reset (i.e. before I even go through the phone setup).
I've managed to Report the issue and Preview the details which reveal the following:
Report type: Crash
Package name: com.android.providers.userdictionary
Package version: 19
Package version name: 4.4-920375
Installed by: com.google.android.gms
Process name: android.process.acore
System app: true
Device: mako
Build Id: KRT16S
Build type: user
Build fingerprint: google/occam/mako:4.4/KRT16S/920375:user/release-keys
Product: occam
SDK version: 19
Release: 4.4
Incremental version: 920375
Codename: REL
Board: MAKO
Brand: google
Exception class name: java.lang.ClassNotFoundException
Source file: BaseDexClassLoader.java
Source class: dalvik.system.BaseDexClassLoader
Source method: findClass
Line number: 56
I've also tried google searching, various other people have had the same issue but what they did to resolve it hasn't worked for me.
Does anyone know what I can do for this?
I'm going to try the full stock binary image from Google's website (https://developers.google.com/android/nexus/images#razorkrt16s). Surely this must resolve the issue.
Techno79 said:
I'm going to try the full stock binary image from Google's website (https://developers.google.com/android/nexus/images#razorkrt16s). Surely this must resolve the issue.
Click to expand...
Click to collapse
And it did indeed solve it.
The problem of the sdfuse dir is suddenly gone.
I tried updating it normally and it fails and it Goes in to recovery.
In recovery I tried to update it manually with SD update.
I get a error: package expects build fingerscanner of zuk/ham : 5.1.1 / lmy48/yog4pas34n : user / release-key
The fingerscanner doesn't work at the moment
I'm currently on 12.1-yog4PAS3AJ
Hope there is anyone who knows how to fix this
Help would be really appreciated
Sorry for posting 2 problems in a short time
OmniRom 6.0
make update-api doesn't help.
Code:
Checking API: checksystemapi-current
/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/system-api.txt:2065: error 17: Field android.R.style.TextAppearance_Material_Widget_Button_Inverse has changed value from 16974548 to 16974565
/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/system-api.txt:2110: error 17: Field android.R.style.ThemeOverlay_Material_Dialog has changed value from 16974550 to 16974564
/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/system-api.txt:2111: error 17: Field android.R.style.ThemeOverlay_Material_Dialog_Alert has changed value from 16974551 to 16974566
/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/system-api.txt:2220: error 17: Field android.R.style.Theme_Material_Light_LightStatusBar has changed value from 16974549 to 16974563
******************************
You have tried to change the API from what has been previously released in
an SDK. Please fix the errors listed above.
******************************
build/core/tasks/apicheck.mk:92: ошибка выполнения рецепта для цели «/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/checksystemapi-last-timestamp»
make: *** [/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/checksystemapi-last-timestamp] Ошибка 38
make: *** Ожидание завершения заданий…
/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/public_api.txt:1966: error 17: Field android.R.style.TextAppearance_Material_Widget_Button_Inverse has changed value from 16974548 to 16974565
/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/public_api.txt:2011: error 17: Field android.R.style.ThemeOverlay_Material_Dialog has changed value from 16974550 to 16974564
/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/public_api.txt:2012: error 17: Field android.R.style.ThemeOverlay_Material_Dialog_Alert has changed value from 16974551 to 16974566
/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/public_api.txt:2120: error 17: Field android.R.style.Theme_Material_Light_LightStatusBar has changed value from 16974549 to 16974563
******************************
You have tried to change the API from what has been previously released in
an SDK. Please fix the errors listed above.
******************************
build/core/tasks/apicheck.mk:46: ошибка выполнения рецепта для цели «/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/checkpublicapi-last-timestamp»
make: *** [/home/daniil/working_directory/android/OmniRom/6.0/out/target/common/obj/PACKAGING/checkpublicapi-last-timestamp] Ошибка 38
How to fix it?
Hmm. Does this disappear if you use "brunch <device>" instead of "make"?
Obviously it needs to be fixed (someone screwed up...) but if it doesn't fail when using brunch, that explains how this issue was missed (most developers use brunch - which is usually far easier BUT does cause API-check failures to get hidden for some reason.)
Entropy512 Thank you.
Solution: Assemble a team brunch instead of make.
Topic can be closed.
DANIIL2017 said:
Entropy512 Thank you.
Solution: Assemble a team brunch instead of make.
Topic can be closed.
Click to expand...
Click to collapse
While you've worked around the problem, I think there's still some investigation on the end of others to figure out why it's breaking - because that's an indication of a potential problem there.
I had the same problem when building my rom for P8 Lite.
I tried "make update-api" but the problem was still present.
Entropy512 said:
While you've worked around the problem, I think there's still some investigation on the end of others to figure out why it's breaking - because that's an indication of a potential problem there.
Click to expand...
Click to collapse
Is there already a solution for this problem, i still have the same problem while building for a non official Omnirom device.
Finally found a solution for the problem:
In the file "build/core/tasks/apicheck.mk" change line 21.
Code:
ifeq (,$(filter true, $(WITHOUT_CHECK_API) $(TARGET_BUILD_PDK)))
change to
Code:
ifeq (,$(filter true, true $(WITHOUT_CHECK_API) $(TARGET_BUILD_PDK)))
It's a workaround but now i can finally build my tree.
So I made a TWRP device tree for it using twrpdtgen by SebaUbuntu and I’m doing the repo sync of the twrp minimal manifest but I haven’t really built TWRP for a device before. The device tree is android_device_mbox_dolphinp1 but I will also try to make it obvious that that device is also the Easytone… etc so it is easy to find and I will make XDA post when it is fully complete. The main thing I need to do now is double check all the stuff in the build tree and any settings I want TWRP to have in boardconfig.mk and compile and test it. I own this device so if all goes well it could be at least booting by the end of the week. Is there anyone with TWRP building experience that would be willing to help if I make any stupid mistakes? The end goal is to make an official TWRP build on the TWRP website. This year I may also consider looking into ROM development just because I really love tinkering with this device and I would love to see it running a custom ROM with the Android TV controls and features in mind. I also want to help anyone who bought this device and was disappointed by the stock experience, which can be slow and clunky to say the least.
I am trying to do lunch but I get this error please help
~/dolphinp1-twrp/device/mbox/dolphin-p1$ lunch twrp-dolphin-p1
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
device/mbox/dolphin-p1/AndroidProducts.mk:11: error: device/mbox/dolphin-p1: twrp_dolphin-p1-user: Invalid variant: p1.
16:28:41 dumpvars failed with: exit status 1
Device twrp not found. Attempting to retrieve device repository from TeamWin Github (http://github.com/TeamWin).
Found repository: android_device_emulator_twrp
Checking branch info
Calculated revision: android-12.1
Branch android-12.1 not found
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:312:
device/mbox/dolphin-p1/AndroidProducts.mk:11: error: device/mbox/dolphin-p1: twrp_dolphin-p1-user: Invalid variant: p1.
16:28:47 dumpvars failed with: exit status 1
build/make/core/version_defaults.mk:56: warning: Invalid TARGET_PLATFORM_VERSION 'p1', must be one of
In file included from build/make/core/config.mk:313:
In file included from build/make/core/envsetup.mk:68:
build/make/core/version_defaults.mk:57: error: SP2A.
16:28:48 dumpvars failed with: exit status 1
** Don't have a product spec for: 'twrp'
** Do you have the right repo manifest?