Hi,
New to XDA, amazing place!
Did a search and nothing posted has helped except perhaps attempting maskrom, but I don't want to void my warranty in case I have to argue with Xtrons via aliexpress (want to leave the case uncracked).
Hope someone can give advice on something further to try to fix my issue as Xtrons won't do an RMA since they feel the bootloop is because I didn't allow updates to complete (which is not the case).
Trying to keep it brief:
my hu: Xtrons TE103AP (px5) CPU: 8 core 64-bit CPU Cortex-A53 @ 1.5G
Andy vers: 8.0.0 Oreo
Kernel vers: 4.4.93+, [email protected] #343, sat sep 15 2018
MTCE_GS_v2.94.3, sep 13 2018
Mem: 3891MB
The scoop:
Last week during a very cold day (windchill -31C) (probably not a factor) the unit locked up while Waze and PowerAmp where running. I was driving (so left it be) and after awhile it rebooted itself to a (recovery) screen with two choices:
1) Factory Reset
2) Reboot
Chose 2) reboot. Screen blanked, that was all she wrote.
Got home (1.5 hours later), took out hu to trouble shoot and possibly reflash system rom inside house (if required).
Test boot (using bench PS (computer PS 12+V and GND rails)): System shows Oreo car multi-media logo for 6 seconds and then Toyota boot animation then blank for 6 seconds and then Oreo car multimedia logo (for 6 sec) again, then blank for 6s then Oreo logo again for 6 sec... (Oreo bootloop). Link: removed Dropbox url - becasue: I'm too new
Contacted Xtrons (via aliexpress) they were quick to offer a link to ROM (sep 20, 2018 vers) Link: removed Dropbox url
and a poorly written, incomplete instruction sheet. Link: removed Dropbox url
Procedure attempted and results:
Used reset toggle to enter stock recovery on a TE103AP:
step 1- use paperclip hold in rst abt 20s (@ 15s panel lights will flash on an off), released for 1s, then
step 2- hold in rst for 3s, release for 1s, then
step 3- click RST (release immediately)
Get E: mount errors for ntfs? Just below the recovery Menu. (I'm assuming it's because I used 128GB tf in GPS and SD slots when hu was working (tfs formatted by Chrome OS, so why ntfs???) and now they are not there. Assuming this doesn't affect problem???)
E: trying mount /dev/block/mmcblk0p1 to ntfs.
E: tring mount /dev/block/mmcblk0 ntfs.
E: failed to mount /mnt/external_sd error: No such device
E: trying mount /dev/block/mmcblk0p1 to ntfs.
E: tring mount /dev/block/mmcblk0 ntfs.
E: failed to mount /mnt/external_sd error: No such device
(verbatim)
Used RESET (rst) to move selection to wipe cache and select (successful) and then factory reset (successful), then inserted TF (16GB FAT32) card with unzipped files) into GPS slot (SD slot (2nd TF slot) left empty).
Moved selection to Update system ROM, select (after 290.7s update successful) returned back to stock recovery menu.
Moved selection to Update MCU, selected. Checks for ROM (OK), flashes MCU (Front panel lights flash on and off). Successful.
System reboots itself: Screen flashes with Oreo logo (car multimedia system) for a few seconds and then blanks for 6 seconds and then Oreo logo reappears ad infinitum.
Link: removed Dropbox url
I have allowed the bootloop to run for 12 hours with no change.
I have also hard powered down (PS off) for 5-10 minutes and powered-on and get:
Oreo logo briefly, the Toyota Boot animation, starting android and a reboot to the 6s Oreo boot loop again or (sometimes) the homescreen (how I was able to get pictures of settings and attempt updates through settings). However, the hu will randomly start the 6s Oreo bootloop again.
Additionally, attempted update procedures:
2) stock recovery: factory reset, wipe cache, update system. select reboot in recovery. Result - same
3) stock recovery: wipe cache, factory reset, select reboot. Result - same
4) stock recovery: factory reset, wipe cache, update MCU (only). Auto-reboot (I release GPS card after it says successful). Result - same
5) From settings: Update system rom, (insert TF) select wipe option. (Successful). Select Update MCU (Successful). HU reboots automatic. Results - same
6) From settings: selcting update system rom OR MCU (successsful), rebooting. Results - same
7) From homescreen, insert TF card, Popup Update system ROM, select wipe option. Successful. Result - same.
Am I doing something wrong (as Xtrons assumes)?
What do I tell Xtrons it is so I can get an RMA and ultimately a working system?
Any help would be greatly appreciated!
Robert
Related
Axim X50 Mid - Change rom WM5 02 to WM6.1
1) Unpack files from archive into root of FAT32 SD-Card.
WM50_K_A04_X50_WM61_ENG_nb0.crc + WM50_K_A04_X50_WM61_ENG.nb0
2) Insert the SD-Card into your Axim and start the SD Image Loader by Pressing Wireless + Power + Reset
3) The Image Loader will search for flash images on your SD-Card.
4) Press the action key twice, this starts the update process.
5) After the process is finished you will be asked to hard reset your device. Follow this instruction and wait for the OS to load.
Click to expand...
Click to collapse
Ugrade writte screen: image update fail (-1)
Restart Axim boot screen logo DEll freeze 80%
Power + Reset: Screen: To restore factory settings press CONTACT. To cancel this operation, press POST. Note: All existing data is lost when you restore factory settings.
key:
CONTACT - power off DELL
POST - boot screen logo DEll freeze 80%
Wifi + Power + Reset:
1. screen: SD Image Update A02
2. screen: loading - Image Updating - Reading SD card
3. screen: loading - Image Updating - Image Writting Flash
4. screen: loading - Image Updating - Erasing storage... > screen: image update fail (-1)
To same ROM X50_mid_WM5_A02
Actual freeze: Erasing storage... > image update fail (-1)
Please help me
BACKGROUND
1) Running Australian TF700T
2) Updated via OTA to firmware v9.4.5.30
3) Rooted using DebugFS
4) Installed app named "[Root] Beats Audio Installer" from Google Play
5) Installed Beats Audio using app "[ROOT] Beats Audio Installer"
6) At device reboot, I am now stuck in a bootloop at the ASUS screen showing the spinning wheel
NOTES
a) Bootloader is stock (ie. not unlocked)
b) Recovery is stock showing WW_epad_9.4.5.30_20120907 A30 (ie. no fastboot)
ATTEMPTS TO FIX
7) DATA RESET
7a) Hold POWER + VOL DOWN to enter stock recovery
7b) VOL DOWN to Wipe Data
Result: Device restarts but still stuck in bootloop at Asus screen with spinning wheel
Conclusion 1: The Beats Audio has messed with the /system partition, not the /data partition
8) FULL FACTORY RESET
Note: Followed steps in thread "Full Factory Reset" at http://forum.xda-developers.com/showthread.php?t=1777203
8a) Downloaded latest firmware from ASUS Support Download as "WW_epad_user_9_4_5_30_20120907_UpdateLauncher.zip"
8b) Unzipped firmware resulting in file "WW_epad-user-9.4.5.30.zip"
8c) Using Windows 7 PC, formatted a 4GB Lexar Class 4 sd card as FAT32 in Windows 7
8d) Using Windows 7 PC, copied file "WW_epad-user-9.4.5.30.zip" to sdcard
8e) Inserted sdcard into TF700 and pressed POWER + VOL DOWN for 10 seconds, then VOL UP to enter Recovery Mode
8f) Stock recovery runs and shows Android with open chest. Progress bar runs.
8g) Android on back displayed with red exclamation triangle.
8h) No text is displayed showing the firmware update is found on the sdcard
8i) Result: Device restarts but still stuck in bootloop at Asus screen with spinning wheel
Notes: I've tried saving the firmware update to the sdcard with the following names, with the same result being a stuck bootloop:
a) WW_epad-user-9.4.5.30.zip
b) EP201_768_SDUPDATE.zip
Conclusion 2: There is something wrong with the sdcard reader in my TF700
Conclusion 3: Stock recovery finds the update file but does not apply it as it is the same firmware version as is already installed.
Conclusion 4: I'm using the wrong filename or recovery process
9) NVFLASH
9a) I've looked into NvFlash from http://androidroot.mobi/t3_nvflash/ to try to reimage the /system partition, but the NvFlash
website states: "For TF700: If you upgraded to 9.4.5.30, it *won’t* work!"
Conclusion 5: As I'm running Android 9.4.5.30, I can't use NvFlash to reimage /system
Any help at this point would be much appreciated!
Have you tried reverting to stock using micro sd?
Solution
tbtaf said:
Have you tried reverting to stock using micro sd?
Click to expand...
Click to collapse
Thanks tbtaf.
The solution involves saving the Asus stock firmware to a microsd card not a standard sd card and then booting into stock recovery. The stock recovery finds the firmware update file and reimages the device.
I now have a working TF700 again.
Glad it worked!
gfrgf
jffh
I am trying to encrypt my device (to satisfy BYOD rules for my employer) and have not been able to get it to work.
I have setup a PIN and followed the following with my device fully charged and plugged in.
1. Select encrypt from Security
2. Click the encrypt button at the bottom
3. Enter my PIN
4. From the follow up encrypt screen I click the encrypt button at the bottom again
5. Tablet reboots by itself
6. I am presented with a Android logo (robot with gears in the middle) for about a minute
7. Tablet then reboots by itself back to the system
8. I check the encrypt setting in Security and it looks exactly the same as before (like my device is not encrypted)
I do not receive any error message
I've tried this with and without my SD card in place.
I've tried this in the keyboard and out of the dock.
It's the same result every time.
I am running Cromi-x 5.2a (just installed over the Thanksgiving weekend) and have done some tweaks with Pimp my Rom.
Appreciate any suggestions as to why my device will not encrypt, or throw any error messages.
Additional testing
OK, did some additional testing.
After the above steps failed, I did another factory reset and wipe of my device (Asus tf700) and then executed the following:
1. After the reset/wipe I flashed Cromi-X 5.2a (US build with _that kernel v6)
2. I then set my PIN (4 numbers because I'm lazy)
3. I then selected Encrypt from the Security menu and selected the Encrypt button
4. My PIN was successfully entered
5. On the second encrypt screen I selected the encrypt button
As before my device rebooted by itself, and also as before I got a screen with just the green android robot with gears in the middle
Also as before, After a very short period of time (a few minutes at most) the tablet rebooted itself.
This time however, I got a different response. Instead of booting all the way through to the lock screen. The system just hangs at the Cromi-X boot screen (spinning circle).
I even let it sit all night thinking it was "encrypting", but nope came up in the morning and it was still just sitting there.
One more item to note, this time when I went to reset/wipe my device I did get a message in TWRP that my device was encrypted. I had to enter my PIN in order to wipe/reset the device.
So while it won't boot, some sort of encryption happened.
HELP!!??
Same...
Same thing happens to me, after I press the encrypt button the Android guy with gears appears and it seems that it is an app. Then the tablet force shutdown itself (because it never takes that fast) and reboots...
everything is same, except I'm running Cromi-x 5.4 and not 5.2a.
Pi Dark [substratum] - Apps on Google Play
Android Pie like Substratum Theme 🎨
play.google.com
Default Dark Theme for Substratum - Apps on Google Play
Dark material theme for the Substratum Theme Engine
play.google.com
[GUIDE/TUTORIAL/HOWTO] Motorola Moto G 4G Any version to Android 9 Pie/LineageOS 16
[GUIDE/TUTORIAL/HOWTO] Motorola Moto G 4G/LTE 2013 Peregrine XT1039 Any version to Android 9 Pie/LineageOS 16
Complete guide to install Android 9 on your Motorola Moto G 4G/LTE.
This tutorial only applies to this model, to check the correct version:
in Android, go to Settings > About, make sure it is this model: Motorola Moto G 4G 2013 Peregrine XT1039.
We will only use a USB 2.0 port and a phone fully charged (but USB3 works too).
CHANGELOG
v14. TWRP 3.5, Magisk 22, BitGApps
v13. Rework tutorial (TWRP 3.4 manipulation, latest Magisk)
v12. Latest fastboot binary, TWRP 3.4, USB drivers for 32/64 bits, Magisk root, boot logo and simpler tutorial
v11. LOS 16 2020 Septembre update (thx to @sdembiske)
v10. LOS 16 2020 May update
v9. Updated pack with TWRP recovery 3.3.1-0, fix glitches in tutorial
v8. Moved tutorial for Android 9 and updated pack with TWRP recovery 3.3.0-0 and Addonsu 16
v7. Updated pack v5 with newest TWRP and removed outdated custom kernel, added links for newest ROMs
v6. Added Google Mobile Services (GMS) certification
v5. Added custom Bootlogo flash
v4. Recovery TWRP 3.2.1-0, MD5 signature for kernel and recovery
v3. Custom kernel, overclock, recovery TWRP 3.1.1-0, no /cache in F2FS (bootloops)
v2. Moved to Android 7.1 Nougat
v1. Initial release
1 ) WHAT YOU NEED
- djibe Moto G 4G pack (~20 Mo): http://bit.ly/motoGLTEdjibepackv5
(Contains link to Motorola Bootloader unlock + flashable Bootloader unlocked logo + TWRP Recovery 3.5.0_9-0 + Magisk root + Motorola USB drivers x32/64 + fastboot)
+ ROM LineageOS Unofficial 16: https://forum.xda-developers.com/moto-g/4g-development/rom-lineageos-16-0-t3835030
Download latest build available here: https://mega.nz/file/haBkzLCA#Aw4qZ09cKi5Jqs-p6SiUaDpxD_bMOQ8PzXACT1xKhr0
Want older and stable versions ?
Use this if you want to give/sell your phone to someone.
Grab Lineage OS 14.1 for peregrine here: https://forum.xda-developers.com/t/rom-lineageos-14-1-substratum-for-moto-g-lte-peregrine.3967207/
+ BitGApps ARM 9 R13: https://xiaomifirmware.com/download/16147/
For LineageOS 14.1, use this package: https://opengapps.org/?arch=arm&api=7.1&variant=pico
+ a microSD card formatted in FAT32 : copy ROM, GApps, Magisk and logo.zip on it.
You can chose another boot logo from this collection: https://forum.xda-developers.com/showthread.php?t=2686441
And download the file according here: https://androidfilehost.com/?w=files&flid=49201
2 ) INSTALL DRIVERS
Install Motorola 64 bits drivers (32 or 64 bits depending on your Windows version).
Then plug Moto G to PC and let the install go on.
3 ) BACKUP YOUR DATA
When your phone is connected to Windows, search for all .jpg, .mp3, .mp4 files on your phone and make copies on your PC.
Then, with an app like Backupyourmobile, backup all your SMS, MMS, contacts.
Make sure the backup is located on microSD card.
4 ) UNLOCK BOOTLOADER
Update your Moto G to the latest official Android 5.1 Lollipop.
In Android, go to Settings > About > Updates. Make sure you have latest version.
Then, go to Motorola website (shortcut in my archive or right below):
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b[/URL]
Subscribe using your Google Account or email.
Shut down phone.
Power it on in fastboot mode: Hold Power et Volume- during 3-4 secondes and release.
Screen is black with lines of text, starting with AP Fastboot Flash Mode (S).
Connect phone to USB2, wait for fastboot drivers to install.
In Windows, select the /flash subfolder you unzipped from my archive.
On keyboard, make a combo Shift + right click -> Open command windows here.
Write this command in Windows terminal :
Code:
fastboot oem get_unlock_data
confirm using Enter.
Command sends back a message like this :
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
OKAY [ 0.146s]
Select all text -> right click -> select all.
Open a notepad editor, and paste text.
Rework the text to get it on 1 line, and remove all spaces and "(bootloader)" messages.
It should look like this : 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Now, copy this text line and paste it in Motorola website : https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Below, click on Verify Eligibility.
Next, I Agree.
You get the unlock key by email, looking like : 56ITMEJ2BFHX5JVXMA4J
Use this unlock key in the following Windows command :
Code:
fastboot oem unlock YOUR_UNLOCK_CODE
Confirm with enter and wait a moment ... till success is confirmed : "Unclock Completed, wait to reboot",
don't disconnect it from PC !
phone reboots to Android with a blank screen "Warning, Bootloader unlocked".
Keep Windows command opened.
4 ) FLASH RECOVERY & BOOTLOADER LOGO
Shutdown phone again.
Power on in fastboot mode: Hold Power et Volume- during 3-4 secondes and release.
In Windows command, use this command:
Code:
fastboot flash recovery twrp-3.5.0_9-0-peregrine.img
confirm with Enter.
Terminal confirms : "Finished. Total time: 0.670s".
### In bootloader screen, you see error "mismatched partition size (recovery)" ? No problem. TWRP is smaller than stock recovery.
### For future TWRP updates, TWRP binary can be flashed from TWRP recovery itself (Install > Install Image)
Now, on the phone in fastboot mode, press Volume- to select the Recovery option. Confirm with Volume+.
Welcome to TWRP 3.5 recovery.
TWRP asks for Keep System Read Only ? -> check "Never show this screen during boot again" and Swipe to Allow Modifications.
### You don't see this waring screen? Then you'll get "TWRP unable to mount storage" while trying to wipe partitions.
### > in TWRP, go to Reboot > Recovery so Recovery will refresh and popup the partition writing privilege.
5 ) WIPE PARTITIONS
In TWRP home screen, go to Wipe > Format data.
Type yes and confirm to format partition.
Go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup from step 2), then Swipe to Wipe,
then back.
### Don't try F2FS, it won't work.
Go to Reboot > Recovery.
Let phone reboot.
6 ) FLASH ROM, OPENGAPPS AND BOOTLOGO
Back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > BiTGApps*.zip,
optional: then Add more Zips > logo*.zip,
then Swipe to confirm Flash.
Wait for operation to end.
### Don't flash Magisk now
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Wait for the phone to boot during 10 minutes.
7 ) ROOT ACCESS AND DEVELOPER MENU
With Magisk, you are root once phone is started. No extra manipulation needed.
For developer menu: open the Settings menu > About Phone.
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Now go to Settings menu > System > Developer settings.
Switch Advanced restart on.
Now use menus to Restart > Recovery.
Back to TWRP, go to Install > magisk*.zip
Reboot.
You are root.
8 ) ENHANCE PHONE
Go to Settings > Developer options
In drawing, set Windows animation scale, Transition animation scale to Animation off (or 0.5x).
Install Greenify, grant Superuser privileges and follow tutorial to set as System app.
Switch on:
- Smart hibernation > Enabled
- Light hibernation
- Aggressive sleep
- Automatic hibernation
That's it.
### When I play music, it comes out of the phone speaker but not the headphone jack.
Use stock AudioFX app to fix this.
Enjoy,
djibe
New version to upgrade Moto G to Android 7.1 Nougat
Enhenced tutorial
Updated version with overclocking of the Moto G 4G
Overclocking introduced
Tutorial updated for better performances
TWRP 3.2 and MD5 file verification for Kernel flash
Added : flash bootloader unlocked screen at boot.
New version of tutorial to obtain the Google Play Certification.
Do you think I should upgrade tutorial for Lineage OS 15.1 ?
Thread and pack updated with latest LOS updates.
guide updated
Tutorial updated
Hi guys, tutorial updated to enjoy Android 9 on your old Moto G 4G !!!
Enjoy
Added download links for older Android versions if needed
Checked for newer packages.
Tutorial is up to date.
Works, except no sound from headphone jack
This worked for me today which I was chuffed about until I started to use the phone and found that when I played music it came out of the phone speaker but not the headphone jack. Any ideas?
Robert Steed said:
This worked for me today which I was chuffed about until I started to use the phone and found that when I played music it came out of the phone speaker but not the headphone jack. Any ideas?
Click to expand...
Click to collapse
I've just found the solution to this which is to disable Audio FX.
@Robert Steed. thx for sharing.
@Robert Steed. thx for sharing.
Hey there.
A while back I set the power off on this unit (flashed with a Malaysk ROM) to go off after 5 min. It seemed to make things buggy and often had to be reset after I restarted the car.
One day, it just didn't come back on. No lights on the buttons. Holding down power and reset doesn't seem to do anything.
When the ACC is powered on, I hear two beeps coming from the CANBUS.
Anyone else encounter this? Better yet, does anyone know of a solution? Not sure I can accept that it's burned our or bricke yet. .
supaneko said:
Hey there.
A while back I set the power off on this unit (flashed with a Malaysk ROM) to go off after 5 min. It seemed to make things buggy and often had to be reset after I restarted the car.
One day, it just didn't come back on. No lights on the buttons. Holding down power and reset doesn't seem to do anything.
When the ACC is powered on, I hear two beeps coming from the CANBUS.
Anyone else encounter this? Better yet, does anyone know of a solution? Not sure I can accept that it's burned our or bricke yet. .
Click to expand...
Click to collapse
Mine is currently screwed.... I bought an Eonon GA6164F MTCD_KLD and the steering wheel controls were buggy and a mess.
Their support gave me a link to an update.img file, and it wouldnt work through the normal Settings \ About \ Software Update (couldnt find file) I renamed to dupdate.img and it found it and wanted to install.... rebooted, did its thing.... then black screen...
I cant get it to do anything now..... ive even removed battery, tried all the resetting combo's with the reset + power , let go of reset, let go of power... cant get anything on the screen..... worst still, ive only had this thing for 3 days... WTF... I tried using the recover from brick with a bootable SD card in the GPS slot, but cant get anything on the screen at all.... perhaps its a bad update.img file, but surely i would see somthing on the screen....
Geniee33 said:
Mine is currently screwed.... I bought an Eonon GA6164F MTCD_KLD and the steering wheel controls were buggy and a mess.
Their support gave me a link to an update.img file, and it wouldnt work through the normal Settings \ About \ Software Update (couldnt find file) I renamed to dupdate.img and it found it and wanted to install.... rebooted, did its thing.... then black screen...
I cant get it to do anything now..... ive even removed battery, tried all the resetting combo's with the reset + power , let go of reset, let go of power... cant get anything on the screen..... worst still, ive only had this thing for 3 days... WTF... I tried using the recover from brick with a bootable SD card in the GPS slot, but cant get anything on the screen at all.... perhaps its a bad update.img file, but surely i would see somthing on the screen....
Click to expand...
Click to collapse
And from today I have the same issue.
Ga6161f. Support advise me to rename update.img to dupdate.img.
Now I have just a black screen, no any sign that is powered, and light just came when/while I press reset button.
I escalate it to vendor and probably it will be returned to them.
Does anyone have some advice how to correct it?
Is it dead, HW damaged or just black screen?
Thanks to all ...
vlsasha said:
And from today I have the same issue.
Ga6161f. Support advise me to rename update.img to dupdate.img.
Now I have just a black screen, no any sign that is powered, and light just came when/while I press reset button.
I escalate it to vendor and probably it will be returned to them.
Does anyone have some advice how to correct it?
Is it dead, HW damaged or just black screen?
Thanks to all ...
Click to expand...
Click to collapse
I did get a tiny bit further last night, i loaded up the latest Malaysk 11.4 firmware onto an SD card and made it bootable using SD_Firmware_Tool.exe.
Unplugging the rear plug of the stereo (to make sure its powered down)
Put the SD card in the GPS slot
Plug the rear plug/cables back in
Turn ACC on
It at least showed somthing on the screen then
I noticed it was Restore 5.2 where before i was Restore/Recovery 5.1.1
It failed to install the firmware
I tried using the menus and tried all other methods of getting either the Malaysk or the Feb 2017 Eonon provided firmware through the usb or normal SD slot, but it would only error and then a Reboot would still leave it doing nothing.
I managed to fix my device.
Long story, but ive started writing up a document.
If I can get to 10 posts, I can start a new topic and include spefics. including pictures. but for now.
This is my rough text.
It might be able to help you too.
BTW. once I had the Malaysk version working, I attempted to re-install the update Eonon had given me and it bricked the device again.
So its def. something bad / funny with that file they supplied.
--
Experiance taken on an Eonon GA6164F
MCU version : MTCD_KLD_V2.09_1
Dec 27 2016 20:06:37
Android Version : 5.1.1
Kernal Version : 3.0.101+
[email protected] #54
Wed Dec 21 11:22:23 CST 2016
Build Number
rk3188-userdebug 28122016.16:07:17
Reboot into recovery on a healthy device
----------------
Hold RES
Press Power
Release RES (while still holding power)
Let go of power 1-2 secs after
Should reboot into recovery
---
Boot into recovery and restoring on a un-healthy device
----------------------
If cant boot into recovery
Create bootable SD card using 'rockchip create upgrade disk tool v1.4'
(Run .exe as admin, dont check 'SD Boot', just leave 'Upgrade Firmware'
(If you cant see your USB drive, check that you have right clicked-Run as Admin in windows on the .exe)
Select Malaysk MTCD dupdate.img file
First post has download links - https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3385309
Fully power off device (unplug from the back).
Insert new-bootable SD card into GPS slot
Plug device back in
- Device will boot into recovery and complain about no update file (thats fine) the Bootable SD card is just to get you into recovery.
Once in recovery, remove the GPS slot SD card and use a USB stick with an update.img (my machine was looking for dupdate.img so i had to rename it).
Press power button to skip down the settings
Hold power button to select an option
Select 'Update system/mcu image from usb and clear all'
<processing>
Device reboots
Toyota logo shows (never progresses)
Press RES
Device reboots
Toyota logo shows
Android is starting (optimizing app XX of XX)
Geniee33 said:
I managed to fix my device.
Long story, but ive started writing up a document.
If I can get to 10 posts, I can start a new topic and include spefics. including pictures. but for now.
This is my rough text.
It might be able to help you too.
BTW. once I had the Malaysk version working, I attempted to re-install the update Eonon had given me and it bricked the device again.
So its def. something bad / funny with that file they supplied.
--
Experiance taken on an Eonon GA6164F
MCU version : MTCD_KLD_V2.09_1
Dec 27 2016 20:06:37
Android Version : 5.1.1
Kernal Version : 3.0.101+
[email protected] #54
Wed Dec 21 11:22:23 CST 2016
Build Number
rk3188-userdebug 28122016.16:07:17
Reboot into recovery on a healthy device
----------------
Hold RES
Press Power
Release RES (while still holding power)
Let go of power 1-2 secs after
Should reboot into recovery
---
Boot into recovery and restoring on a un-healthy device
----------------------
If cant boot into recovery
Create bootable SD card using 'rockchip create upgrade disk tool v1.4'
(Run .exe as admin, dont check 'SD Boot', just leave 'Upgrade Firmware'
(If you cant see your USB drive, check that you have right clicked-Run as Admin in windows on the .exe)
Select Malaysk MTCD dupdate.img file
First post has download links - https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3385309
Fully power off device (unplug from the back).
Insert new-bootable SD card into GPS slot
Plug device back in
- Device will boot into recovery and complain about no update file (thats fine) the Bootable SD card is just to get you into recovery.
Once in recovery, remove the GPS slot SD card and use a USB stick with an update.img (my machine was looking for dupdate.img so i had to rename it).
Press power button to skip down the settings
Hold power button to select an option
Select 'Update system/mcu image from usb and clear all'
<processing>
Device reboots
Toyota logo shows (never progresses)
Press RES
Device reboots
Toyota logo shows
Android is starting (optimizing app XX of XX)
Click to expand...
Click to collapse
IT WORKS !!
Only difference was:
Device reboots
FORD logo shows (never progresses) *mine is Ford
Press RES
Device reboots
FORD logo shows
Android is starting (optimizing app XX of XX) but it was not visible.
Wait for home screen . (1-2min.)
That's great news.
You can change the boot logo in the settings- factory settings - logo. Don't fiddle with other settings in there unless you have pictures of what they are when it's all fine. I'm glad I could share the knowledge and you got yours working too. It's not documented very well , I spent 24 hours digging through forums to finally get that procedure ... oh well
You did a GREAT JOB !
Now there is a manual.
Thanks
Hey I have followed your steps listed above however I get the following:
Code:
Recovery system v5.2.2
--Update rkimage. . .
Finding update package . . .
=== UPDATE RKIMAGE ===
Find and check firmware . . .
E: Check Failed
Can not found firmware image or invalid image.
Update rimage complete.
Instalation rkimage aborted
I have an Eonon GA5155F. At the moment, my unit will not load past the car manufacturer's logo.
Any help would be greatly appreciated.
Thanks.
Hi I have a Eonon I think it is a GA6201F it was installed in the care before I got the BMW so I don't really know Its not that old ,My problem is It was working when I fires got the car then it stopped I contacted Eonon.com and they sent me an upgrade I had the unit pulled out at the time of upgrade then after I installed it back in it wouldn't work I checked the power supply that's ok I checked fusses they are ok then I tried to reset it no beeps and no lights black screen holding the reset button in as well as the power still no beeps and then when I let the reset button out the lights are on but they are red and then when I let the power button go they go out then if I push the reset button and then release it the red tight comes on for one second and then it goes out ,can it be fixed the person I got the car off payed nearly $500 for it I cant afford to get another one I will need to get a cheep cd player that may not fit properly or leave a big hole in my dash or do I walk across the road to the water and see how long it takes to sink after I throw it and let the fish fix it because they might have more luck than I have
Haven't been around for a while and thought I'd try to fix the Eonon GA5151 I have. Did a Google search and ended up back on my own post.
I tried to follow your instructions but did not have any luck.
The screen does not turn on. Here's what I did:
1. Used Rockchip program to create update SD card using update.img provided in the RK3066 Malaysk ROM (can't check SD boot anyway as the program crashes if I do).2
2. Disconnected plug at back of Eonon unit; inserted SD card.
3. Re-inserted plug and waited
4. Nothing ...
I still get the two beeps coming from the CANBUS but I'm not seeing anything on the screen. Now I'm beginning to wonder if I should check my remote wire or something else. It just makes no sense to me how or why this is going on.
Any ideas?
Geniee33 said:
I managed to fix my device.
Long story, but ive started writing up a document.
If I can get to 10 posts, I can start a new topic and include spefics. including pictures. but for now.
This is my rough text.
It might be able to help you too.
BTW. once I had the Malaysk version working, I attempted to re-install the update Eonon had given me and it bricked the device again.
So its def. something bad / funny with that file they supplied.
--
Experiance taken on an Eonon GA6164F
MCU version : MTCD_KLD_V2.09_1
Dec 27 2016 20:06:37
Android Version : 5.1.1
Kernal Version : 3.0.101+
[email protected] #54
Wed Dec 21 11:22:23 CST 2016
Build Number
rk3188-userdebug 28122016.16:07:17
Reboot into recovery on a healthy device
----------------
Hold RES
Press Power
Release RES (while still holding power)
Let go of power 1-2 secs after
Should reboot into recovery
---
Boot into recovery and restoring on a un-healthy device
----------------------
If cant boot into recovery
Create bootable SD card using 'rockchip create upgrade disk tool v1.4'
(Run .exe as admin, dont check 'SD Boot', just leave 'Upgrade Firmware'
(If you cant see your USB drive, check that you have right clicked-Run as Admin in windows on the .exe)
Select Malaysk MTCD dupdate.img file
First post has download links - https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3385309
Fully power off device (unplug from the back).
Insert new-bootable SD card into GPS slot
Plug device back in
- Device will boot into recovery and complain about no update file (thats fine) the Bootable SD card is just to get you into recovery.
Once in recovery, remove the GPS slot SD card and use a USB stick with an update.img (my machine was looking for dupdate.img so i had to rename it).
Press power button to skip down the settings
Hold power button to select an option
Select 'Update system/mcu image from usb and clear all'
<processing>
Device reboots
Toyota logo shows (never progresses)
Press RES
Device reboots
Toyota logo shows
Android is starting (optimizing app XX of XX)
Click to expand...
Click to collapse
want to update GA5155
hi can someone please help me understand how to update been told thers no update to this machine but pumpking did same duelcore stereo with kitkat 4.4.4 which i am wanting thankyou in advance