How to check build number: Settings ⇒ System ⇒ About ⇒ Build number (at the bottom). For more information about build numbers, please see Nokia release summary.
00WW_5_180_SP04 (Android 9): https://mega.nz/file/fhVElD6Q#M0qv7pUkwDc9l4Kc0NOMvRkrGhcza0RVWcSg0q5_VfE
Related
As I'm sure many will know Telechips do not release their SDK or linux BSP to people without buying and expensive development board and commitment to buying vast amounts of chips.
I have a cx-01 and the device is crippled on kernel features and force loading of kernel modules is disabled by default.
cnxsoft had some information regarding the kernel source release, but without framework recompile it won't boot.
Android source will give me the envsetup.sh, but misses the telechips profile out.
I wondered if anyone has the telechips 8923 folder in WORKING_DIRECTORY/device -if so where did you get it and can I have a copy.
Failing that I have a decompiled system image for the cx-01 and a copy of telechips 8902 profile-I wondered if it is possible to create a working tcc8923 with these?
I notice back in January nobody had a working custom kernel for this processor- am I barking up the wrong tree?
To build Android from source for a new device, you need to set up a board config and its makefiles. This is generally a long and tedious process. Luckily, if you are only building recovery, it is a lot easier. From the root of your Android source directory (assuming you've run envsetup.sh), run the following (substituting names appropriately): ( I gues envsetup.sh means running: 1: . build/envsetup.sh
2: lunch 3: 1 (my choice) 4: make m805_892x my tablet type)
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
For my Tom-Tec 7 excellent, the command will go as follows :
Code:
build/tools/device/mkvendor.sh YG m805_892x ~/boot.img
> ore: build/tools/device/mkvendor.sh YG m805_892x ~/recovery.img
the later needed kernel is in recovery.img it seems.
Please note that m805_892x is the device name..... Only use "~/boot.img" if you have the boot image in your home directory. Or else please specify the correct path.
You will receive the confirmation "Done!" if everything worked. The mkvendor.sh script will also have created the following directory in your Android source tree:
manufacturer_name/device_name
YG/m805_892x
Sow get youŕe recovery.img and use that to get WORKING_DIRECTORY/device/YG/m805_892x
Device name is in build.prop
Try this link to see what it makes from the board config and its makefiles http://builder.clockworkmod.com
Personally i´m still stuck making a cwm recovery thats works 100% on my tablet.
I build from CWM source.
some links:
>> Porting CWM to other devices Part 2 (OS X): http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-os-x-part2/
wiki: http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
http://forum.xda-developers.com/showthread.php?t=1337786
http://www.twobitcoder.com/?p=158
tcc TCC8902/TCC8803 tablets http://forum.xda-developers.com/showthread.php?t=1101094
> http://forum.xda-developers.com/showthread.php?t=1866545
http://forum.xda-developers.com/showthread.php?t=1026853
make recovery: http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
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.
Hello ,
i have device : vertu astra . i want to root this device .
i have already unlocked oem
Problem is i dont have recovery file for this device
Dtails :
Model number : Aster
android version : 4.4.2
baseband version : m8974a-aaaanazm-2.0.70021
kernel version : 3.4.0-g67c21bd [email protected] #1 Tue jan 27 2015
build number : 4.4.2_1.760.6.056
can some one help me to compile a recovery file for this device . i can give all details needed . may be BoardConfig.mk or any other info .
Open EFS Pro, starts up....
Checking application environment...
-----------------------------------
Terminating process: adb.exe, PID: 7204 ...
Initializing ADB server... Okay.
ADB server is running!
Searching for device... Okay.
Connecting to device... Okay.
Checking device status... Okay.
-----------------------------------
Performing device checks...
-----------------------------------
Root status: Perm Rooted
SU binary version: 3.26:kinguser_su
-----------------------------------
BusyBox status: Installed
BusyBox version: 1.20.1-Stericson
Checking BusyBox applets... Okay.
-----------------------------------
EFS Professional is ready for use.
-----------------------------------
Device info works and displays:
---------- Hardware Information ----------
Connected Device SN.: S567018180b68
Device Manufacturer: SAMSUNG
Device Model: GT-S5670
Product Code: GT-S5670PWATHR
Hardware Version: MP 0.301
---------- Firmware Information ----------
PDA Version: S5670JPKQ7
Baseband Version: S5670XWKQ4
CSC Version: S5670OJPKQ4
---------- Software Information ----------
Kernel Release: 2.6.35.7-perf-CL577623
Kernel Version: #1 PREEMPT Sun Sep 18 18:34:47 KST 2011
ROM Build: GT-S5670-user 2.3.4 GINGERBREAD JPKQ7 release-keys
Android Version: 2.3.4
BusyBox Version: 1.20.1-Stericson
SU Binary Version: 3.26:kinguser_su
When I select 'All Partitions' in device filters, I get the following messages:
Enumerating device partitions...
Extracting PIT from device for mapping... Skipped, already exists.
Checking PIT file integrity...
Operation Failed!
This is stock ROM for Galaxy Fit GT-S5670. I want to make sure I can correctly backup my IMEI and the EFS data before pushing modified ROM image to the device. I used mobogenie to do initial push of .apk files for rooting, and also ran the Mobogenie ROOT tool.
On EFS Pro (Beta) (couldn't find a stable OLDER version...I would like to try an old one.) I go to the Backup Tab, and under device filters I don't see my version of Samsung Galaxy FIT In the Manage section of device filters. Anytime I try to do anything with the Device Partitions or Device Filters I get the message: Number was less than the array's lower bound in the first dimension. Parameter name: srcindex
Please advise me if this is just a dumb question of a newbie?
Hi i have created release keys in my amlogic build version 9. But after the box is booted using the compiled image it still displays as test keys.
Fixed. Added entry in Makefile to release-keys.