Related
Hi All,
Good day to all. I'm new in this site and i really need help from anyone. It's just that i flashed my Cube U9GT tablet with U9GT2 firmware. I used RKBatchTool_1.5 software to flash my device. After flashing, i can only see white screen that keeps turning on everytime i try to reboot. It can still detect by my laptop thats why i'm not yet worried much. For now all i can think is to have a copy of Original or Custom firmware for my U9GT tablet so that i can flash it again with the correct firmware.
If anyone have a copy of working firmware for my tablet, kindly please help by giving me a working link where i can download it. I already browse google but unfortunately until now i can't find any.
I'm hoping for your favorable response with my concern. Thanks a lot in advance.
By the way, below is the specs of my tablet.
Screen:7" 4:3 TFT capacitance multi-touch screen with resolution 800*600
CPU:Rockchip 2918,1.2GHZ Cortex A8
OS:Android 2.3,more than 100,000 software are available online
RAMDRII 512MB
Storage:Built-in 2GB-16GB,TF card extended 128MB-16GB
Internet Access: "Wifi 802.11b/g Max54Mbps,3G module dongle"
support OpenGL ES 2.0 and Open VG
Video:support 1080P encoding for H.264,VP8,RV,WMV,AVS,H.263,MPEG4 format
Support YouTube,HTML5 and Flash10.1
Audio:support MP3,WMA,APE,FLAC,RA，AAC,OGG，WAV format
Image:support JPG,BMP,PNG format
E-book: support TXT,LRC,PDF,Html,Htm,EPUB,PDB,FB2 format
Playback time:up to 5 hours movie playback time,up to 15 hours music playback time,
up to 7 hours web page view time
Multi language,record function,G-sensor and keyboard supported
Battery Capacity:4250mAh
Product Dimension(mm):182*144*7
2016 UPDATE:
I HAVE IDENTIFIED IT MYSELF: The Mainboard is T733-MAINBOARD-V2.1
Firmware can be downloaded from here:
http://www.needrom.com/download/a13-chipset-t733-mainboard-v2-1-dual-sim-fully-working-and-tested/comment-page-3/#comments
LiveSuite from here:
https://androidmtk.com/download-livesuit-all-versions
Flashing guide here:
https://androidmtk.com/flash-stock-rom-using-livesuit
You will need to install the following first:
1. http://universaladbdriver.com/wp-content/uploads/universaladbdriver_v3.0.zip
2. https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.4.3.zip
After reflash, you will need to install Play store, because Android market cannot connect.
Google Play store from here:
http://www.apkmirror.com/apk/google-inc/google-play-store/
I'm still looking for recovery.
--------------------------------------------------------------
Hi all, Could you help me identifying a chinese/korean tablet and help getting a custom recovery onto it.
The tablet is bought here in the Philippines as SAMSUNG GALAXY Tab 3, I got it from my GF who swapped her old phone in a market in Manila, for this one - Seller claimed original(as usual).
Model
FCC ID: A3LGTP1000 RATED: 5V=2A
MADE IN KOREA
CE0168
Se photos below
I used SpecDevice to pull all the info I could of the tablet and its in the provided link - I can't post it here or the thread will be too large, so please follow the link http://specdevice.com/showspec.php?id=f475-9a5c-3a0b-df1d2dfafbec
Now, I know this tablet is NOT original SAMSUNG Tab 3, I have been living in the Philippines long enough to know a fake when I see one - but its damn good copy - Except for a few things:
It has:
Boxchip Allwinner A13 Singlecore 1Ghz
512MB Ram
Storage according to the Partition table APP:
/system: 504MB(463MB used),
/data: 1008MB(494MB used),
/cache: 315MB(5MB used),
/mnt/extsd: 30021(8772MB used) - this is the external SD card of 32MB,
/mnt/sdcard: 1401(172MB used)
adding the storage space up gives 3228MB which would mean this tab has approx. 4GB Rom. According to seller it should have 8GB(so again something fake). In settings>storage it says:
INTERNAL STORAGE:
Total space: 0.98GB - Apps:440MB - Available: 503MB
------------------------------------------------
Then something strange
INTERNAL STORAGE
Total space: 5.63GB - Apps: 110MB - Pictures, videos: 3.40MB - Audio: 3.22MB - Downloads: 1.15MB - Available: 5.48GB
--------------------------------------------------------
And strange again
EXTSD
Total space: 5.63GB - Available: 5.48GB
--------------------------------------------------------
I think this info is from the buildprop and that its fake, but I'm no expert in tablets - so need your help on this one - how to set it correctly?
------------------------------------------------------------------------------------------------------------------------------
Something else, this one comes with ICS installed, and in About tablet it says android version 4.2.1 - all that is written on the SpecDevice page, just follow the link above.
What I need from you Guys/Galls is a way to identify this tablet and get help to put custom recovery on it, either CWM or TWRP.
It has stock recovery but it can only be accessed by Settings>Backup and reset> Reboot to recovery - If I try the Power and Vol+ I get tilted green android with red exclamation mark, and I have tried all combinations of buttons that I could find on the net. I need custom recovery before I start modifying it, or there is no way to reflash it, if something goes wrong - Please help me with this
Cpu Identifier(By Davy Bartoloni) tells me this:
Cpu type: Boxchip Allwinner A13
Tablet type: T733 (Allwinner)
More info: Screen size 7.0 Inches
Supported frequency states: 29
NEON capable (fast video playback)
Ram memory module: 512 Mb DDR (Usable 353 Mb)
GPU type:
Mali-400 MP (single core GPU)
By ARM Holdings plc / ARM Norway
Going to the page for GPU:
Real inches: 7.0"
GPU: Mali-400 MP
Dispaly size: 800 x 480 (Normal)
X/Y dpi: 160 / 160 density: 160
Software inches: 5.00"
enlargement ratio: 1.4
GPU display stress factor: 1.95 (normal to manage)
Going to android device page:
Device: T733
Declared PCB: nuclear
Compiled for:
Product: nuclear_evb
Code name: nuclear-evb
OS version: 4.2.1(Jelly Bean)
Battery level: 98%
Flash memory: 1,007 MB
free flash memory: 502 MB
battery temperature: 30.0 C
Kernel compiled on 'gtide' workstation by user: fwj (build 20130627)
Going to Bogomips page:
Processor: ARMv7 Processor rev. 2 (v7I)
Bogomips: 1001.88
CPU implementer: 0x41
CPU Architecture: 7
CPU variant: 0x3
CPU part: 0xc08
Cpu revision: 2
Hardware: sun5i
Revision: a13b
Serial: this is very long and I don't know if you guys need it
EDIT: Some immidiate problems I could use some help with, the screen size is 800x480 but when in ES file explorer I can't see the full text of pop-up boxes, and have to turn the tablet upside down in order to catch a glimpse of OK or other buttons(to the right). Kind of annoying when having to set /system to R/W.
I think it has to do with the screen itself being 7" but widescreen style, and its not set correctly somewhere. As you can see above in CPU identifier, it says its "software inches: 5.00".
Just found out the screen is 800 x 432 and not 800 x 480 - that could explain why ES File explorer have a problem.
I used this tool: https://play.google.com/store/apps/details?id=com.sturnus.screeninfo
And this tool https://play.google.com/store/apps/details?id=com.xizz.resolutioninfo which told me that the screen is actually not 7" nor 5.8" as SpecDevice said, but in reality 5.7".
Now, somewhere in the system files something is written wrong - how do I fix it?
This is starting to be a very long thread, so if there is any other info you guys need then just ask
Hope you can help me
With kind regards
JBJ
EDIT: The tablet is pre-rooted, it just needed me to install SuperSU and busybox(Stericsson).
Maybe you can find something here: http://ublaze.ru/forum/topic1232-1860.html It's in Russian, so you'll need something like Google Translate, but seems like a pretty decent list of Allwinner stuff.
es0tericcha0s said:
Maybe you can find something here: http://ublaze.ru/forum/topic1232-1860.html It's in Russian, so you'll need something like Google Translate, but seems like a pretty decent list of Allwinner stuff.
Click to expand...
Click to collapse
Thanx for the quick reply, and the link - unfortunately google translate is horrible to translate from russian to english and I also think we should stay in this thread, so others can find benefit of this - there are alot of theese tabs sold here in the Philippines - but no support.
Please take a look at the EDIT's I made
With kind regards
JBJ
Hi again, I figured something is wrong with my build.prop or platform.xml so I have attached them here, plus lsmod transcript. In the build.prop there is no line to change the LCD density or resolution.
Could someone take a look at it - please
Remember this is IMM76D ICS version 4.0.4 release 4.2.1(thats what it says), maybe thats why - but what do I know, I'm no expert
Thanx in advance
JBJ
I'd reach out to one of the moderators over at GSM Forums (2nd post) : http://forum.gsmhosting.com/vbb/f906/help-firmware-my-t733-allwinner-a13-cortex-a7-1-0mhz-1744680/
ehh, what do you mean by 2nd post? Also, I said that I like to stay in this forum as it would make it easier to someone else who has same tablet - please do that And post any info here;
There are enough trouble finding info scattered across many forums, with links to other forums, that again has links to other forums - this makes it extremely difficult for newbies to find info - I hope you understand my point, and want to continue the help
thanx in advance
JBJ
Clearly, what do you ask for? :what:
Hope I helped you!
If I did , then why not press that Thanks button under my post...
SavvasPro said:
Clearly, what do you ask for? :what:
Hope I helped you!
If I did , then why not press that Thanks button under my post...
Click to expand...
Click to collapse
Hi, Please read all post since I ask for help identifying and for help with display problem
Try this:
https://play.google.com/store/apps/details?id=com.dama.hardwareinfo
==============================
Hope I Helped You . If I did, then why not press the "Thanks" button under my post.
Thanks for the link, but these tools rarely do something new, they just copy the functions of eachother - basicaslly all the same except for the name. They cannot tell you who is the manufacturer, they can only list what is wriiten in build.prop.
With kind regards
JBJ
2 days until I have to return to Denmark, I really don't want to
hey insomia
do you have the firmware of this?sorry for making it not related to the topic but this is same as my tablet i think, i want the firmware of your tablet, i also live in philippines (tropa sige na kung pwede sana iprovide mo yung link ng firmware nyan) thankyou hoping for your response.
PS:
make it flashable to livesuit cause some of later 2012-2013 img files are not, most of them i got error like 0x162 or maybe because of installing cwm or anything modification i made make that img file got the error 0x162. thankyou
BoomPork said:
do you have the firmware of this?sorry for making it not related to the topic but this is same as my tablet i think, i want the firmware of your tablet, i also live in philippines (tropa sige na kung pwede sana iprovide mo yung link ng firmware nyan) thankyou hoping for your response.
PS:
make it flashable to livesuit cause some of later 2012-2013 img files are not, most of them i got error like 0x162 or maybe because of installing cwm or anything modification i made make that img file got the error 0x162. thankyou
Click to expand...
Click to collapse
Hi, I don't have the firmware, but i might be able to make a firmware/Rom dump using uberizer - if you then can make the IMG file yourself. But I don't have any storage apace to upload it too. Also I don't have time to look at this now, but will get back to you later on.
With kind regards
JBJ
Its, Insomniacno1 = sleepless maniac
Ok, I decided that we need to collect the different ROMs made by the DEVs and sort them into 1 place.
What I like to do here is to try to explain the different ROMs Kit Kat and Lollipop by Malaysk, ###8310 and Booroondook.
And while we now know that MCU's need to stay via KLD, KLD2, KLD6 etc, you can upgrade within those parameters with only changing factory settings (KLD6-V2.83 to KLD6-V2.97 is ok)
I have played with these roms and follow an certain rule.. Before you go from Factory to a custom rom, take pictures of settings and factory settings.
Don't update unless you are sure you know how to revert back. Know what buttons to push. Know what screen resolution your unit is! All those minor points.
All the roms we are talking about look like a filename as "update.img". 4.4.4 and 5.1.1 all for MTCB and MTCC are called out this way. I do believe MTCD is something different (dupdate.img ???)
MCU for MTCB and MTCC are "mcu.img".. and are found on the file servers as KLD?-V2.?? .. sub your version (others are available)
The fileserver can be found under typos1 name on most posts. I will link it soon.
I would suggest you read his very informative wiki as well.
Malaysk (MTCB 4.4.4 and 5.1.1) is probably the most popular ROM here. He and like the other DEVs make the ROMs to their liking's. They will on occasion add suggestions to the ROM image if they think it is beneficial.
Malaysk and ###8310 (MTCB to MTCC fake out via xPosed does a reboot once to complete loading) will have 2 files to chose from which are for resolutions. 800x480 and 1024x600. Choosing the wrong one will make the your display look awkward. (reason to know how to get back into recovery if you make this mistake)
Booroondook has a setup that creates the resolution size, thus 1 file to get and run and answer questions.
Bloatware may be added to customize roms. The reason they are customized.. Right Even factory roms have it, don't like it.. well...
So little memory, so many apps.. 1g, 2g.. well Malaysk does the FUSE trick which opens up the full memory. Booroondook, I don't recall, maybe maybe not. ###8310 has it set to 3g right now I think, but I think there might be choice of default.
Malaysk has customized Launchers. JY5.1.1 typically (one other too)has a speed display on his 4.4.4 and 5.1.1 roms
Booroondook has a few and DSA8310 is mostly clean and factory based (Klyde)
###8310 uses what factory firmware uses. The Windows like and some other with the old time flip card time piece.
You may install the rom image via MicroSD card (plugs normally into the GPS slot) or the USB port 0 (Normally the Mini port front plug thingy behind the door)
If you have update.img with mcu.img, both will get programmed to the device.
If you are going from factory to any rom, you should do the wipe data/factory cache option after the rom is flashed. You can do this anytime after the reboot. And the 1st reboot takes a long time.
If you go from and DEVs rom to another, do the data/factory cache wipe option as well, in fact you can do this anytime you update.
Stopping here since at work and will edit and add later. This is the start.
##8310, Typos1 and others, I like input..
If you had a problem and fixed it, let me know
Hands Free Messaging
If you want to hear and reply to messages on your radio from your cell, get the app from Google Playstore readitotme and install on your phone
Under Profiles: Make sure you link it as "CAR KIT" and enable it
And set to BT Mono
If you want voice reply, enable that (you get 2 weeks free) and you'll need to download addition app
It will automatically use your Messages app on the phone for the app. So under the Apps, do not enable it.
But you can select additional apps and how you like to hear them Header, message etc
Under Contacts, you can also what to hear.. One area has ALL, so selecting anything under that will enable ALL contacts with that feature.
Other features and more stuff are listed, but this should work fine.
Adding Launchers from 5.1.1
5.1.1 update.img:
Both Malaysk and Booroondook load their images with a few launchers. If a launcher is in their ROM image, you can grab it from the image by using a program called "RK3xxx Firmware tools" (google it)
Simply load the update.img via the tool (select Img... box) , extract it (Extract under Firmware image tools), then extract again under System.img tools.
Then "Open folder..."
Locate folder "priv-app"
Find the launcher you like (Launcher2mtc3_5_1_1) example
copy to a USB flash drive
Some launchers use weather on their screen, so grab the weather one too folder "app" (MTCWeather) and copy to the USB Flash drive
take the flash drive and reverse the procedure.
To copy from the USB flash drive to the system, look for "mnt" in root of the device. Find the usb drives and locate your drive.
Copy the MTCWeather to "app" (this will make it appear in the apps folder) and set permission to 755 for folder and the apk in the folder 644 using Root Explorer
Copy the (Launcher2mtc3_5_1_1) launcher to "priv-app" folder and set permission to 755 for the folder and the apk in the folder to 644
Reboot
I have been trying to get the JY5.1.1 speedo to work.. ran out of time.. WIP
Test MCU and Factory ROM
MCU= KLD6-V2.91 (from Factory)
ROM= 5.1.1 (800x400 Pumpkin)
Radio had MAL 5.1.1 800x Aug file.
Fuse vs Standard RAM
1st: Flashed MCU from V2.97 to V2.91
2nd: Flash Factory ROM.
Reboot had issue,
3rd: Did a Data/Factory Cache and Wipe..
4th: Flash Factory ROM again.
5th: System rebooted to Factory Images
Results are that V2.91 and Factory 5.1.1 works fine. Will be adding apps and place JY5.1.1 launcher soon. (Can't, no root!)
The settings retained Factory settings
The About Device says MTCC -KLD6-V2.91 5.1.1 800x480
Its all good from MTCB
Oldpapa49 said:
Test MCU and Factory ROM
MCU= KLD6-V2.91 (from Factory)
ROM= 5.1.1 (800x400 Pumpkin)
Click to expand...
Click to collapse
Hi OP,
Three weeks ago i bought an MTCB KLD6-V2.86 w ROM 5.1.1 840x400 Pumpkin, ori release May 04 2016
Now got from pumpkin a rom from 05 August 2016 which works much better (reboots on button press in settings are gone...). The MCU stays on V2.86...
Q: whats the difference between KLD6 2.86 and KLD6 2.91 or KLD6 2.97 ? Are they just Upgrades or different functionality ? Is it dangerous to flash a 2.91 over 2.86 ? Will it bring features ? Are there mcu roms inside Malaysk Roms? For KLD6 the latest Version i could find on servers were 2.85. I would like to remap some keys to other functionality (eg Band or Scan to Mediaplayer...) maybe possible with Xposed ? Is Malaysk with preloaded Xposed the better choice ?
eblackie said:
Hi OP,
Three weeks ago i bought an MTCB KLD6-V2.86 w ROM 5.1.1 840x400 Pumpkin, ori release May 04 2016
Now got from pumpkin a rom from 05 August 2016 which works much better (reboots on button press in settings are gone...). The MCU stays on V2.86...
Q: whats the difference between KLD6 2.86 and KLD6 2.91 or KLD6 2.97 ? Are they just Upgrades or different functionality ? Is it dangerous to flash a 2.91 over 2.86 ? Will it bring features ? Are there mcu roms inside Malaysk Roms? For KLD6 the latest Version i could find on servers were 2.85. I would like to remap some keys to other functionality (eg Band or Scan to Mediaplayer...) maybe possible with Xposed ? Is Malaysk with preloaded Xposed the better choice ?
Click to expand...
Click to collapse
MCUs are improvements. It is odd that your unit is V2.86 , but it now says that KLD6-V2.86 will allow 5.1.1 work. Can you find typos1 and tell him you have a MTCB unit with 5.1.1. dated Aug 5th. 800x480 image.
I use to have KLD6-V2.81, Pumpkin told me they had a newer one and it is KLD6-V2.91. I have installed KLD6's 2.83, 2.85. 2.91, 2.95 (I think) and 2.97
Just remember to get your FACTORY Settings recorded. so you can set the right info.
MCU file are not attached to any ROMs by any Dev.
Dev roms are rooted and they supply a remap apk for keys. I have never used it.
As in the 1st post, DEVs develop the ROMs to their likings. Since you are on 5.1.1, DSA8310 has a pretty clean ROM and will chnage you MCU to look like a MTCC unit.
Since you have a MTCB, you might be able to go between 4.4.4 and 5.1.1. But make sure you have all the info settings in factory, Very important!
I'm just a basic person and like certain things... So I look and set my HU to my likings.
I change my ROM evrytime a DEV makes a change to tests. I'm on MALs latest 4.4.4 ..
Note: I rarely use radio, I use Sirius App. Radio signals stink where I live.
Oldpapa49 said:
MCUs are improvements. It is odd that your unit is V2.86 , but it now says that KLD6-V2.86 will allow 5.1.1 work. Can you find typos1 and tell him you have a MTCB unit with 5.1.1. dated Aug 5th. 800x480 image. *i did*
As in the 1st post, DEVs develop the ROMs to their likings. Since you are on 5.1.1, DSA8310 has a pretty clean ROM and will chnage you MCU to look like a MTCC unit.
Since you have a MTCB, you might be able to go between 4.4.4 and 5.1.1.
I'm just a basic person and like certain things... *so am i*
Click to expand...
Click to collapse
Thanks for this detailed answer! As i know now i can step back to 4.4.4 i will give it a try, maybe things are a bit faster then.... i also read in a Xposed thread, dsa8310 plans something about resoldering bigger RAM's, sounds interesting! Maybe i can find one who can do this for me and take away the laggyness, but first i want to do this Sound-Chip-Mod which looks easy to do, as this unit here has only poor sound and settings to offer... If the device survives, i will play around with the rk3xxx_firmware_tools
Oldpapa49 said:
MCUs are improvements...
Just remember to get your FACTORY Settings recorded. so you can set the right info.
... But make sure you have all the info settings in factory, Very important!
Click to expand...
Click to collapse
Just a few points to add:
1) In general we can assume that a higher rev MCU has better features/fewer bugs than a lower rev. (Otherwise why would the authors bother to create it?) But as @pa.ko has cautioned several times, that is not necessarily always true. There is some risk that a higher rev may seem to work fine, yet introduce subtle bugs that don't show up right away.
So while it is generally good to install the MCU image with highest rev #, it is also really important to remember which MCU you had originally, and make sure you have a copy of that image before you upgrade. Then if you do come across something that seems like an MCU bug, you can revert to your original MCU image to see if it goes away. If you can't get the exact rev#, then you will want to have the closest rev# to your original.
Note that there is currently no way to "upload" an MCU image from your HU, so you can only get them from the HU vendor (or from a fileserver).
2) You can save the "factory" settings to a 516 byte file called mcu.cfg; the option is in the factory settings area (behind the "126" password). You can then reload the mcu.cfg file and it should restore your factory settings to their prior values. There is no guarantee that an mcu.cfg file from a lower rev MCU will be compatible with a higher rev MCU, but they usually are (in my experience anyway).
Incidentally, 512 bytes of that 516 byte config file get downloaded into the MCU's memory (the 4 other bytes are a short header "MTC" and a checksum byte), and that memory area then configures the "personality" of the MCU. There is a one-to-one correspondence between the bytes of the config file and the bytes in that memory area in the MCU. If you look at the mcu.cfg file you will see that most of those bytes are zeros.
dhmsjs said:
Just a few points to add:
1) In general we can assume that a higher rev MCU has better features/fewer bugs than a lower rev. (Otherwise why would the authors bother to create it?) But as @pa.ko has cautioned several times, that is not necessarily always true. There is some risk that a higher rev may seem to work fine, yet introduce subtle bugs that don't show up right away.
So while it is generally good to install the MCU image with highest rev #, it is also really important to remember which MCU you had originally, and make sure you have a copy of that image before you upgrade. Then if you do come across something that seems like an MCU bug, you can revert to your original MCU image to see if it goes away. If you can't get the exact rev#, then you will want to have the closest rev# to your original.
Note that there is currently no way to "upload" an MCU image from your HU, so you can only get them from the HU vendor (or from a fileserver).
2) You can save the "factory" settings to a 516 byte file called mcu.cfg; the option is in the factory settings area (behind the "126" password). You can then reload the mcu.cfg file and it should restore your factory settings to their prior values. There is no guarantee that an mcu.cfg file from a lower rev MCU will be compatible with a higher rev MCU, but they usually are (in my experience anyway).
Incidentally, 512 bytes of that 516 byte config file get downloaded into the MCU's memory (the 4 other bytes are a short header "MTC" and a checksum byte), and that memory area then configures the "personality" of the MCU. There is a one-to-one correspondence between the bytes of the config file and the bytes in that memory area in the MCU. If you look at the mcu.cfg file you will see that most of those bytes are zeros.
Click to expand...
Click to collapse
Ina cases of issues with/after loading mcu.cfg (problems, incomparibility,...) you may reset my to default (factory default / clear) state by creating empty mcu.cfg (don't forget to check permissions)
Empty MCU.cfg forces MCU to reinitialise ... At least Russians are saying so, in some previous MCU vers, I didn't check in code for myself
Truck with empty MCU.cfg reset us better than reglazing my as reglazing is not overriding that particular memory area of config params
Call Home...
Ok, I have tried this on 4.4.4 and 5.1 (both roms)
1. Works better on 5.1 and not 4.4.4. It seems to crash google using 4.4.4 unless I did something incorrect.
2. You need to get the mtcservice (headunit 2.34 or 2.35) to make it function. I tried the one off playstore and I just don't really know about it.
When you use the mic to call the 1st time, make sure you select 'mtcsevice' (steering wheel icon) to make calls. It should complete after.
Hi,
I've been trying to locate the "boot photo" on an Amlogic S912 TV box that I have in order to change it. It is the first image that you see when you power the unit on, followed by the boot video which I have already changed and is located in the "etc" folder of the unit. I cannot find the location of the initial photo though. If anyone can tell me what folder it is located in I would certainly appreciate it! I believe it is either in bmp format or png format. The unit is running android 6 and these are the folders that are in the unit. (If this question is in the wrong section I apologize in advance!)
Thanks for any help anyone can offer.
It's not gonna be there. That image is stored in one of 2 places in every device I have had. It was either on the boot partition or bundled with the kernel. Either way you would have to flash the device to change it.
I just discovered that it is in the "logo.partition" which shows up in temp/ level 1 with the Amlogic Customization Tool, but I'd like to find out how to modify that with my own photo and then repack the firmware. Any ideas?
fxbill said:
I just discovered that it is in the "logo.partition" which shows up in temp/ level 1 with the Amlogic Customization Tool, but I'd like to find out how to modify that with my own photo and then repack the firmware. Any ideas?
Click to expand...
Click to collapse
You would need to extract that partition and find the file that it is placing in temp. Change the file and refresh the partition. Mind you this is dangerous and doesn't always work. But as long as you ha e an unlocked bootloader you should be able to recover.
The "logo.partition" is a single file in the level 1 temp file directory. It is actually a single file type, but I don't know how to disassemble the file or what program would open it. I can get a hex editor to open it, but that doesn't help me much since it is a 6 megabyte file and the hex, of course, is unreadable...at least to me. There are about 20 files in the level one temp folder of which this is just one. The program works just fine with Amlogic devices that are running Android 5 and below and does almost everything with Android 6, but this is one of the things that it won't do in Android 6 and the Customization program has not been updated for a couple of years. I'm hope that eventually it will be but at this point I need another way or program that will allow me to do it!
Found it..... It's in the Level 2 folder. Easy to put into the firmware once you know where it is!
Hello,
I have a DOOGEE DG-700 that I am trying to resuscitate. All has gone well, except for one problem: the toush area of the screen is shifter tpo the left by about 40 pixels, and nothing in the left area (like the letter 'p', or some 'close' buttons) can be accessed, and I believe this is also why the "swipe to execute" in the TWRP recovery does not work, which makes the recovery tool even more useless that the stock chinese language one :/
I have tried every calibration app I could find, tried changing screen resolutions, which had no effect. I even tried to edit the script.bin file (which I could not find) to change to x/y coords and the /data/data/touchscreen.calibration/files files (which did not exist). There is a utility called "Edit Script EasyTools v2.exe" that claims to edit script.bin, but I not been able to find a copy that is not corrupted.
So... how do I go about moving the active area of the touchscreen to the right about 40 pixels?
I have seen the suggestion of installing a new rom, but I have yet to find another rom for the DG700 that works, including the rom from DOOGEE !
Thanks
Details
Model: Titans2_DG700
Android Version: 5.0
Baseband Version: DOOGEE-Titans2_DG700.2015/05/12
Kernel Version: [email protected]2015/05/12
Build Number: DOOGEE-Titans2_DG700-Android5.0R21-2015_07_02
ROM: custom R21, rooted, made by the XDA dev "Yalita35254"
Recovery: recovery_TWRP_2860_DG700_LP.img