Database Info

[Q] [Generic Device] Howto upgrade OS inside the img file

Recently i was given an android device by a friend.. once i got to looking around at it, it appears to be some generic device from china.
After searching for days, i found the maker as fugetek. I emailed them asking for a release date on OS upgrade (from 4.1.1 -> kitkat) and was informed that " Updates are needed, and won't be made. "
Emailed them again asking for the source / project files they used to build the android OS for this device so i could update it myself...
Here is what they sent me:
(image attached)
As you can see.. these are hardly project files / source files, but rather a flashing tool, a set of " how to " doc's for flashing the device, and a compiled *.img
My Question:
1) Is it possible to extract / mount the img file, and manually upgrade the OS to kitkat witout losing any hardware functionality
2) If it is indeed possible to upgrade the android OS version using the img file as src, does anyone know of a step-by-step guide / tutorial on how this is done.
[EDIT] UPDATE: Seems the PheonixUSBPro flashing utility links to an " Alwinner " PDF when you click help..
I am assuming this is pretty much the same image being passed around by the chinese for their generic 7" Android Devices
From what i'm reading.. this is going to a fun, and somewhat convoluted project
Device Details:
Manufacturer: Fugitek Technologies / Lonestar Group:
Model: OCOCCI_MID
Android: 4.1.1
Baseband: jellybean
Kernel Version:
308+
[email protected] #206
Mon Nov 4 14:17:42 CST 2013
Build Number:
nuclear_pfdq88d-eng 4.2.2 JRO03C 20130913 test-keys
Any help would be most appreciated
If anyone requires the " source " zip they sent me, let me know, and i'll upload it somewhere for you.

CM 13 to Stock

Hello,
I flashed CM 13 on my phone and everything went well. I tested everything and it worked fine. However, a day later, my LTE/3G is acting up. At first I could not send messages, and now it says my SIM card is not showing up. I want to flash back to stock, however CM 13,being marshmallow based, merged my internal SD card with my external SD card and now I do not have access to it via recovery mode (I'm using the CM recovery -- it changed from TWRP to CM during flash). So the zip files of the ROMs I had on my external SD are not visible under recovery.
Does anyone have any idea on what I could do? I hear you can flash a rom through ODIN but I do not know if my merged SD cards will screw up anything. I am stuck and don't know how to proceed. Any help would be appreciated.
Here is some info:
Android Version : 6.0.1
CyanogenMod version: 13.0-20151221-UNOFFICIAL-kltespr
CyanogenMod API level: Dragon Fruit (4)
Android security patch level : December 1, 2015
Baseband version: g900PVPU1BOA6
Kernel Version: 3.4.0-g5683635 [email protected] #1 MON DEC 21 01:10:43 PST 2015
Build number: cm_kltespr-userdebug 6.0.1 MMB29M ce104643a0
SELinux status: Permissive

Evinreud said:
Hello,
I flashed CM 13 on my phone and everything went well. I tested everything and it worked fine. However, a day later, my LTE/3G is acting up. At first I could not send messages, and now it says my SIM card is not showing up. I want to flash back to stock, however CM 13,being marshmallow based, merged my internal SD card with my external SD card and now I do not have access to it via recovery mode (I'm using the CM recovery -- it changed from TWRP to CM during flash). So the zip files of the ROMs I had on my external SD are not visible under recovery.
Does anyone have any idea on what I could do? I hear you can flash a rom through ODIN but I do not know if my merged SD cards will screw up anything. I am stuck and don't know how to proceed. Any help would be appreciated.
Here is some info:
Android Version : 6.0.1
CyanogenMod version: 13.0-20151221-UNOFFICIAL-kltespr
CyanogenMod API level: Dragon Fruit (4)
Android security patch level : December 1, 2015
Baseband version: g900PVPU1BOA6
Kernel Version: 3.4.0-g5683635 [email protected] #1 MON DEC 21 01:10:43 PST 2015
Build number: cm_kltespr-userdebug 6.0.1 MMB29M ce104643a0
SELinux status: Permissive
Click to expand...
Click to collapse
This should work, sadly I'm trying to do the same but running in to some issues... Best of luck this is the best place to find the software that I've found. You may need to rename the .tar.md5 file that is the firmware to .tar before you open that file with Odin to load to the phone.
Links to Odin and stock Firmware are there in the page and all links work.
(I'm not allowed to post links to urls yet )
look up sm-g900p unroot and goto the androidrootz page called "How to Unroot Galaxy s5 complete stock"

Did you try *#*#4636#*#* in the dial pad and editing the network settings

Problem with installing Plasma Mobile on Nexus 5 with MultiROM.

Hey, I created a question at Android Enthusiasts: "https://android.stackexchange.com/questions/157664/plasma-mobile-in-multirom-manager-on-nexus-5".
I tried to install Plasma Mobile on Nexus 5. It is very important to me to start testing it in MultiROM Manager first (with some other mobile operating systems).
I followed this tutorial.
In section:
Finally install the Plasma Phone
on:
It will take while to download. After download is over, it will reboot to recovery, in recovery it will make real installation process, so drink a coffee meanwhile.. ; )
I got error:
cheching file device-687a931c47e1...d6b63d42054.tar.xz..FAILED
I checked "dev" (version 8), but I got same error on: "dev-proposed" (version 1).
I have:
OS version (official Nexus 5 latest update - 6 IX 2016):
Andorid 6.01
Kernel:
3.4.0-g4ad03fa-dirty
[email protected] #1
Tue Feb 9 21:30:30 CET 2016
Compilation number:
M0B31E
In MultiROM (patched - like in tutorial) I have installed: Can you help me with it?
MultiROM v33
Recovery 2016-02-10 (0)"
Kernel: Stock 6.0 and 6.1
How can I solve this error message?
Click to expand...
Click to collapse
And here is link to tutorial: "https://community.kde.org/Plasma/Mobile/MultiROM".
Can you help me with it?

Cant install APK files

Hello,
i have a Android Car Radio,
i want to install some APPs that arent on the App store, so i downloaded the APK file.
If i click on them and press the install button, on the top left (where the current open APP name is) Package Installer pops up for a sec and instandly dissaperas. No error messages, nothing
The APK file doint get installed.
Is the Package Installer damaged?
How can i fix this? Did i need to update the Firmware / MCU ? If yes, whats the correct Firmware / MCU for me?
Modell: px5 (1024x600)
Android: 8.0.0
Kernel: 4.4.93+
Build-Nummer: px5-userdebug 8.0.0
MCU: MTCE_XRC_v2.85f_2
CPU: 8core 64bit Cortex A53 @ 1,5ghz
Thanks for helping

PX5 Assert Failed: update _dynamic partitions... when flashing ROMs (Help Request)

Hey guys,
The title says it all. When trying to flash ROMs, I get an error saying= assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")) E:error in /mnt/usb_storage/update.zip (status 7) Installation aborted.
Recovery version: HCT 10.3.0 rockchip/rk3368/rk336810/QQ2A.200305.004.A1/hct206241158userdebug/test-keys
PX5 Head Unit 4GB Ram Android 10 HCT the latest
I have 5 people and a couple of friends from XDA suffering from the same problem. We all have px5 devices that were originally android 8.0.0, which we updated to android 10 using ModInstaller Pro.
The ROMs we are trying to flash are updated HCT ROMs(stock), Malaysk or VIVID. All exhibit the same problem.
I had an idea to remove the assert update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")) from updater.script but I don't know what it does really. Dynamic partitions are a new thing for me. We do not have OTG support so if it gets bricked its game over.
Steps followed: Format Usb flash drive with fat32 filesystem (I tried 2 tested and working ones, one new).
Put update.zip in it.
Boot the head unit and click wipe data and install when it pops up.
We always get the same error.
Any help is truly appreciated.

Try Mr. Hanichl procedure # 347:
>> Revert to Android 9 from Android 10
>> ModInstaller : Android 9 && install Hal9K Android 9
>> ModInstaller: Android 10 && install Malaysk Lite 10
[ROM][PX5][Q][10.0] Malaysk ROM for PX5 RK3368 with Android 10
Only for devices processor Rockchip PX5, MCU - MTCD, MTCE Android 10.0 ! Mod Q 10.0 Android PX5 RK3368 For PX6 RK3399 mod 10 android is HERE Only for those who have 10 android installed, a PX5 processor and have an installed MCU that starts with...
forum.xda-developers.com

boltthrower56 said:
Hey guys,
The title says it all. When trying to flash ROMs, I get an error saying= assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")) E:error in /mnt/usb_storage/update.zip (status 7) Installation aborted.
Recovery version: HCT 10.3.0 rockchip/rk3368/rk336810/QQ2A.200305.004.A1/hct206241158userdebug/test-keys
PX5 Head Unit 4GB Ram Android 10 HCT the latest
I have 5 people and a couple of friends from XDA suffering from the same problem. We all have px5 devices that were originally android 8.0.0, which we updated to android 10 using ModInstaller Pro.
The ROMs we are trying to flash are updated HCT ROMs(stock), Malaysk or VIVID. All exhibit the same problem.
I had an idea to remove the assert update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")) from updater.script but I don't know what it does really. Dynamic partitions are a new thing for me. We do not have OTG support so if it gets bricked its game over.
Steps followed: Format Usb flash drive with fat32 filesystem (I tried 2 tested and working ones, one new).
Put update.zip in it.
Boot the head unit and click wipe data and install when it pops up.
We always get the same error.
Any help is truly appreciated.
Click to expand...
Click to collapse
There are threads for paid roms and support via the mod, what does the developer suggest when approached for paid support.
If paid app fails and developer is unable to support, have free, factory methods such as OTG been tried.
Also, this isn't software development, requesting mod moves to q&a forum.