How do I enter recovery on an Eonon GA6154F (MTCD KDL) - MTCD Android Head Units General

I have an Eonon GA6154F. From looking in the System Info I believe that it is an MTCD based KDL device.
It has become increasingly slower over time. I would like to try resetting and installing a different ROM on it to see if it helps speed things up at all. But no matter what I try I cannot seem to enter the recovery system.
I have tried holding in the reset button whilst also holding the power button, then releasing the reset button and then releasing the power button 1 - 2 seconds later but it still just boots up as normal.
I have also tried following the instructions in this thread: https://forum.xda-developers.com/an...al/eonon-ga6164f-mtcd-rk3188-mtcdkld-t3594368 but when I try the write the firmware file to an SD Card an error message comes up on screen saying something about failing to write the MBR. The SD Card application also records error 87 in it's log file.
I am currently running a stock ROM from around November 2016. I would like to either reinstall a stock ROM or one of the available customised ROMs, I'm not fussed which. My ultimate goal is to effectively factory reset my Android Head Unit in the hope that it speeds it back up.
Hopefully someone can help me out with this

push and hold the power knob untul you see the units buttons flash 3 times, let go and push the power knob again you will see the recovery screen come up.
jim1985 said:
I have an Eonon GA6154F. From looking in the System Info I believe that it is an MTCD based KDL device.
It has become increasingly slower over time. I would like to try resetting and installing a different ROM on it to see if it helps speed things up at all. But no matter what I try I cannot seem to enter the recovery system.
I have tried holding in the reset button whilst also holding the power button, then releasing the reset button and then releasing the power button 1 - 2 seconds later but it still just boots up as normal.
I have also tried following the instructions in this thread: https://forum.xda-developers.com/an...al/eonon-ga6164f-mtcd-rk3188-mtcdkld-t3594368 but when I try the write the firmware file to an SD Card an error message comes up on screen saying something about failing to write the MBR. The SD Card application also records error 87 in it's log file.
I am currently running a stock ROM from around November 2016. I would like to either reinstall a stock ROM or one of the available customised ROMs, I'm not fussed which. My ultimate goal is to effectively factory reset my Android Head Unit in the hope that it speeds it back up.
Hopefully someone can help me out with this
Click to expand...
Click to collapse

Related

Need desperate help with possibly bricked Diamond

Hi all,
Just received my Vodafone-branded Diamond, and I'm afraid I already managed to brick it!
It was equipped with version "1.37.172.3 NLD" so I decided to upgrade it to the latest version.
The installation of OliNex Hard-SPL 1.93 went flawless, but the installation of ROM "RUU_Diamond_HTC_WWE-ME_1.93.456.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe" stopped at about 25% with error code 302. The recovery method that came with the package didn't help, every time the upgrade stopped at the same moment.
Since the device is stuck in the bootloader, and I'm left with a non-chargeable battery, I tried the official Vodafone-branded "RUU_Diamond_Vodafone_NL_1.97.172.4_Radio_Signed_Diamond_52.44.25.24_1.08.25.08_Ship.exe" ROM. Unfortunately, this upgrade stops at 48% and throws the same 302 error.
Anyone who can tell me what I'm doing wrong, and what I can do to solve all this?
I hope I don't have a brand new, but bricked device on Christmas!
TIA and have a nice day.
Try a hard reset first. If this doesn't help google or search at XDA for MTTY.
This tool can fix your device
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Stuck_at_bootloader
Try this, maybe will work
Try a Vodafone branded stock rom before mtty.
Regards,
Carty..
He already tried a stock rom....
Potential Solution
Have you looked at the thread titled,
[UPG][TRBL]How-to fix: Update/Flash doesnt work, stops at 0% or 5% (invalid model ID)
It may just be a model ID glitch that can me fixed.
Take a look. It's in this forum in a sticky by cptsunshine.
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Besides, the bootloaders says upgrade ROM code error please try again.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Install Rom via Internal Memory Method
Steps from Suiller:
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
Let me know how it goes.
Make sure you have Net framework 3.5 installed on devices.
Nakkie27 said:
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Click to expand...
Click to collapse
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
band27 said:
Steps from Suiller:
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!
Click to expand...
Click to collapse
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
janielsen said:
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
Click to expand...
Click to collapse
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Nakkie27 said:
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Click to expand...
Click to collapse
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
janielsen said:
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
Click to expand...
Click to collapse
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on, and I can't get a USB-connection.
Edit:
Volume down + reset brought me in the bootloader again, although it's saying SPL-1.93.OliNex.
Nakkie27 said:
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on.
Click to expand...
Click to collapse
that i know but as i say in the post that when u do it that way i say u can load new firmware whitout it needs to boot try my friend i have done it 3 times because wrong loading of firmware
u have to only push thoose 2 buttom then it will work because u go to rescue mode
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Nakkie27 said:
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Click to expand...
Click to collapse
u need to hold them down until it leave the 3 color display an turns into grey
Ok, finally managed to do a hard reset. Afterwards I tried upgrading to the official Vodafone NL 1.97 ROM once more, but it failed at 48% again.
Any ideas what to do? I know have Diamond with Hard-SPL 1.93 (which says upgrade ROM code error) with no working OS.
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Hi all,
I have a quit similar problem. I've read a lot, but couldn't find an answer to my problem - may bye someone can help me.
I updated my Dimond (OliNex Hard-SPL 1.93, radio 1.09.25.23 and rom dutty V4). When I start my phone most of the time (95% plus) I end up in the color screen - however some time it's starts perfect (without changing anything).
When I get stock in the color screen, I can start the phone with mtty and the command "boot".
What can I do to make my phone always start in the normal way?
Thanks!
Nakkie27 said:
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Click to expand...
Click to collapse
i smell a radio issue - last time i was trying to upgrade my radio - ended up with something similar, managed it out like you did - but now you're up - so that's good!!
try some other rom (this time without radio) - i don't think you should have any issues going forward... good luck and have fun!

[Q] Help?

Hello All,
I've been browsing and searching pretty much all day, so I'm now going to ask for help.
Symptoms:
My screen is black. No white bars. Nada.
I know the phone turns on because the charging light goes off and the phone vibrates once when I press the down volume and power to go into recovery.
Preceding events:
I had just finished making a phone call, and the phone rebooted. I (was) running OMGB v6. When it came back, it started into a boot loop. It would run through the splash animation and then restart.
So, I decided to clear everything out and re-flash. Pulled my card out, wiped everything. Backed up my card, cleared it out, formatted it, and put the rom image in the root directory. When I tried to flash, I received the following error:
Cant mount /dev/block/mmcb1k0p1 (Invalid Argument)
Mounting /dev/block/mmcblk0p1 on /data failed: Invalid argument
I pushed parted (and a few other files) in adb and checked out what was going on. It looked like my phone's internal memory had somehow become screwed. So, I followed the directions outlined here:
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage (Sorry, can't post links yet. I'm not that cool. .smirk.)
When I got to the step of re-flashing PN31IMG.zip, Everything seemed to go through fine, then it rebooted and Voila! The screen is dead.
I think it may be because I have the slcd version, but I have no way of knowing for sure.
Any input or suggestions would be both welcome and helpful.
EDIT: Can you even get into hboot?
And you formatted your SD card as FAT32 right?
Probably a SLCD screen and the PB31IMG was for 2.1/AMOLED.
Try this guide. http://forum.xda-developers.com/showthread.php?t=786436
Flash the PB32IMG.zip in part 2. It's the stock 2.2 with support for the SLCD model. Thats just my 2 cents.
Input: In addition to searching and browsing, you should post your thread in the right section.
and yes as said above it was probably the incorrect screen version.
EDIT: I am doing just as you advised. Will post after trying. Thanks!
I am fairly certain that I can get into hboot, as this is what happens:
Press and hold down volume and Power
Wait 5 seconds, release power/volume down
Charging light goes off
Camera shutter clicks
I wait a good 15 seconds, just in case it's scanning my sdcard
Then, I presume it is in hboot and press the volume down key to move the selection to recovery, then press power to select, so that I can *hopefully* adb to fix it
It vibrates, as though going into recovery, But I can't see anything on the screen from start to finish, so I'm not sure.
And I have to be screwing it up somewhere, because no device is detected in adb
kaiserII101 said:
Input: In addition to searching and browsing, you should post your thread in the right section.
and yes as said above it was probably the incorrect screen version.
Click to expand...
Click to collapse
Thank you, kind sir.
As I am obviously ill-educated as to the correct place to post, would you mind pointing me in the right direction; or, as you agree with my assessment, offering a solution?
Update:
So, I finally got the timing right and booted the phone enough to get to adb.
I pushed parted and associated files to the phone and re-partitioned the internal memory (Swap, EXT2, FAT32), then disconnected from the computer.
I pulled the battery for 30 Minutes. Unnecessary? Probably. But I'm saying what I did just in case someone else has this issue.
While the battery was pulled, I downloaded:
ttp://dougpiston.com/files/RUU/build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
I formatted a 4gb card FAT32, and loaded said zip on the card's root directory. Then I turned the phone on and held the down volume to enter hboot.
I waited 5 minutes. Then I pressed the up volume key to confirm installation aaaaaaannnnddd......
I waited. 15 minutes this time. Then I pressed volume up to confirm phone reboot. 90 seconds later my screen came on, and booted into VZW stock!
Oh, and kaiserII101 - I would like to extend my personal thanks to you for pointing out that this was in the wrong thread.... ..... and then not responding. Where I come from, that's called asshattery. Not appreciated. Next time you feel obliged to make a snarky comment instead of actually being helpful, do us all a favor: Don't.
dismal moron said:
Update:
So, I finally got the timing right and booted the phone enough to get to adb.
I pushed parted and associated files to the phone and re-partitioned the internal memory (Swap, EXT2, FAT32), then disconnected from the computer.
I pulled the battery for 30 Minutes. Unnecessary? Probably. But I'm saying what I did just in case someone else has this issue.
While the battery was pulled, I downloaded:
ttp://dougpiston.com/files/RUU/build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
I formatted a 4gb card FAT32, and loaded said zip on the card's root directory. Then I turned the phone on and held the down volume to enter hboot.
I waited 5 minutes. Then I pressed the up volume key to confirm installation aaaaaaannnnddd......
I waited. 15 minutes this time. Then I pressed volume up to confirm phone reboot. 90 seconds later my screen came on, and booted into VZW stock!
Oh, and kaiserII101 - I would like to extend my personal thanks to you for pointing out that this was in the wrong thread.... ..... and then not responding. Where I come from, that's called asshattery. Not appreciated. Next time you feel obliged to make a snarky comment instead of actually being helpful, do us all a favor: Don't.
Click to expand...
Click to collapse
Most cool - glad that worked, and thanks for posting the means to correct it so others may benefit from your experience!
Had a similar thing happen as well a while back ~ since then, I've made weekly copies of my SD card onto my PC - overkill perhaps, but then there's always a full backup of my goodies.
Happy modding!
I'm glad you got it working and I'm even more glad that I don't have the SLCD version of the Dinc. They just have so many issues...
Have fun!

Really don't know where to put.

First of all - I am a Sprint customer with the Latest Htc Rom -stock
List of problems and actions taken.
Problems
Soft reset reboots with phone in Airplane mode.
When the end key is pushed not long pressed but pushed it puts phone into Airplane mode.
Battery run time is not about half or even less than it was before.
Actions taken
Removed battery for about 10 minutes and tried a hard reset. Got to the screen where you are supposed to hit volumn up to restore to original and well the volumn up button gets pressed but nothing happens. So after waiting for about 15 minutes I do a soft reset to get back to the HTC Sense screen (today screen). I take the phone out of Airplane mode cause from reset. I hit the volumn up button and it works fine. I tap the end key and it puts me back in Airplane mode.
So I reflash stock rom back in that by the way wouldn't go until I unlocked the phone with HardSPL. Apon first reboot it still boots with phone shutting down into Airplane mode. Turn phone back on then turn power off. Take battery out. Replace battery. While holding Talk ad End buttons I tap power on for hard reset. Goes through try colored screen then to the volumn up option screen. I tap volumn up and nothing still happens.
I'm looking at Task 29 but I am worried about the volumn button not working.
Anyone have any ideas on what direction to take. Thank you
Hootyhoo said:
First of all - I am a Sprint customer with the Latest Htc Rom -stock
List of problems and actions taken.
Problems
Soft reset reboots with phone in Airplane mode.
When the end key is pushed not long pressed but pushed it puts phone into Airplane mode.
Battery run time is not about half or even less than it was before.
Actions taken
Removed battery for about 10 minutes and tried a hard reset. Got to the screen where you are supposed to hit volumn up to restore to original and well the volumn up button gets pressed but nothing happens. So after waiting for about 15 minutes I do a soft reset to get back to the HTC Sense screen (today screen). I take the phone out of Airplane mode cause from reset. I hit the volumn up button and it works fine. I tap the end key and it puts me back in Airplane mode.
So I reflash stock rom back in that by the way wouldn't go until I unlocked the phone with HardSPL. Apon first reboot it still boots with phone shutting down into Airplane mode. Turn phone back on then turn power off. Take battery out. Replace battery. While holding Talk ad End buttons I tap power on for hard reset. Goes through try colored screen then to the volumn up option screen. I tap volumn up and nothing still happens.
I'm looking at Task 29 but I am worried about the volumn button not working.
Anyone have any ideas on what direction to take. Thank you
Click to expand...
Click to collapse
Which model is your device? You can find the model number above the barcode that is under your battery. It will be in the form of RHODxxx where "xxx" is a three digit number. From here, I'll be able to help you a bit better once I know which model you are using.
Thank you for the reply. The model# is M8RHOD400. Since my first post I have tried flashing other Roms and I think it was the Sharkie Rom that actually said it could find the end key file. Other than that all the other Roms I tried pretty much do the same. When end key is tapped it shut phone off. Plus the volumn up still doesn't work at the hard reset state. It works normal otherwise but when I try to hard reset it will not go past the first screen that says press vol. up to reset. Thanks again so far.
Hootyhoo said:
Thank you for the reply. The model# is M8RHOD400. Since my first post I have tried flashing other Roms and I think it was the Sharkie Rom that actually said it could find the end key file. Other than that all the other Roms I tried pretty much do the same. When end key is tapped it shut phone off. Plus the volumn up still doesn't work at the hard reset state. It works normal otherwise but when I try to hard reset it will not go past the first screen that says press vol. up to reset. Thanks again so far.
Click to expand...
Click to collapse
Ok, so the first thing we need to test for is hardware fault. To do this, you will need to perform a task29 and then flash the latest Sprint ROM. After that, try to see if you have the same problems. Please do not install anything while testing. If it works fine like this, then we will need to do some specific testing on the custom ROMs to narrow down the cause.
Things have changed a bit. Long morning. I tried flashing a few ROMs to see if any would fix it. I know a feeble attempt. Well one went bad and never got past the splash screen when it went to restart. Won't connect to ActiveSync. So I tried reflashing from SD card. and I get to
RHODIMG.nbh
OS -
Press Power button
to start update image
Press VolDn button
to cancel update image
The problem is I press power button and nothing happens. I press any buttons and nothing happens. I pulled the battery and reinstalled it and got the same again. I tried to run Task 29 but how. Won't load. Tried renaming rbh file but got the same results as above. I need a way to hard reset without buttons and its obvious that nothing working outside of windows. I'm lost.
Hootyhoo said:
Things have changed a bit. Long morning. I tried flashing a few ROMs to see if any would fix it. I know a feeble attempt. Well one went bad and never got past the splash screen when it went to restart. Won't connect to ActiveSync. So I tried reflashing from SD card. and I get to
RHODIMG.nbh
OS -
Press Power button
to start update image
Press VolDn button
to cancel update image
The problem is I press power button and nothing happens. I press any buttons and nothing happens. I pulled the battery and reinstalled it and got the same again. I tried to run Task 29 but how. Won't load. Tried renaming rbh file but got the same results as above. I need a way to hard reset without buttons and its obvious that nothing working outside of windows. I'm lost.
Click to expand...
Click to collapse
First of all, you should stop trying to update with the SD card. That's the problem you're having, so we need to try something different. Flash it via USB. You don't need an Activesync connection. It just needs to change from SERIAL to USB at the bottom of the bootloader screen. Once that happens, simply run the RUU and it will flash to your device. Do task29 first. Then do the stock Sprint ROM. Task29 cannot be flashed via SD anyway. The NBH file in task29 is a filler file. It's the actual RUU in it that is modified to perform the wipe.
So, let's try this again.
1. Get into the bootloader by holding voldown while turning the device on.
2. Plug it in to a USB port on your PC.
3. Once the text at the bottom of the screen changes from SERIAL to USB, begin running the task29 RUU.
4. Once the progress bar gets to 99% on the task29 flash, hold the voldown button again and await the restart.
5. Once it restarts into the bootloader and the text changes again, begin flashing the latest Sprint ROM.
6. Allow the ROM to boot up all the way and settle down, then give it one soft reset.
7. When it comes back again, go ahead and test it out to see if your problems persist.
8. Report back here with the results, and we'll move on from this step.
Task 29 doesnt seem to working because it reboots back to the last rom. Everything is still there. I really don't think that any of the hardware buttons work outside of working in the OS and at startup. IE volumn works when unit is on or when putting unit into bootloader mode but Volumn button does not work when trying to do a hard reset or a Task 29. Power button turns on unit, turns off unit, puts into bootloader mode, starts hardreset. I have loaded a Custom Rom just because maybe with the X button on the bottom and bigger it might be easier. I'm all ears from here on out. Its seems I need to clear ROM or Cmos without button usage. I don't know if that makes any sense to you but like I said I'm all ears on what to do now. Thanks for the little lesson on flashing without Activesync. Feeling kinda stupid about that one. Thanks for the help so far.
Hootyhoo said:
Task 29 doesnt seem to working because it reboots back to the last rom. Everything is still there. I really don't think that any of the hardware buttons work outside of working in the OS and at startup. IE volumn works when unit is on or when putting unit into bootloader mode but Volumn button does not work when trying to do a hard reset or a Task 29. Power button turns on unit, turns off unit, puts into bootloader mode, starts hardreset. I have loaded a Custom Rom just because maybe with the X button on the bottom and bigger it might be easier. I'm all ears from here on out. Its seems I need to clear ROM or Cmos without button usage. I don't know if that makes any sense to you but like I said I'm all ears on what to do now. Thanks for the little lesson on flashing without Activesync. Feeling kinda stupid about that one. Thanks for the help so far.
Click to expand...
Click to collapse
I don't know where you got your task29 utility from, but you cannot run it from SD. It HAS to be used with the RUU that came with it. It is the modified RUU that runs the task29 function. Just to eliminate the confusion, I'm uploading a modified RUU to this post that is very simple to use. Extract it from the archive and follow these instructions.
1. Connect the device (in bootloader) to your PC and wait for USB to show in the bootloader.
2. Run the RhodiumWAdvancedRUU.exe
3. Select the third radio button that says "Perform task29 only."
4. Uncheck the box that says "Restart utility when task29 completed."
5. Hit Next and keep going through it until it flashes.
6. Once the progress bar gets to 99%, hold your voldown button and wait for the reboot.
7. Once you are back into the bootloader, wait for USB to show up on the screen again and then flash the stock ROM.
8. Once the flash is complete, allow it to boot once and settle, then soft reset.
9. Once it restarts, test the problems again.
10. If the problems persist, we can move on from here.
Note: If you want to make sure that the task29 utility worked, feel free to try and boot it after performing the task29 and see how far it gets. If it gets stuck at the bootscreen, then you know it worked. Simply pull the battery, or hit the reset button, and power it back on while holding voldown to return to the bootloader and continue with step 7.
I cannot find the uploaded file that you sent, but also I am not trying to run the Task 29 file from SD card. I'm trying from the comp but like I said, when in any mode other than Windows, I really believe none of the buttons work. Volumn down at 99%. Volumn up on a hardreset. The buttons work to get me into the various mode either from Windows or at startup, but once into the special modes I think I don't get any buttons. That and the fact that the only thing the endkey button does in turn phone on and off but doesnt end anything is peculiar to a person like me. Anyways I didn't get your Task 29 file yet.
Thanks again
Hootyhoo said:
I cannot find the uploaded file that you sent, but also I am not trying to run the Task 29 file from SD card. I'm trying from the comp but like I said, when in any mode other than Windows, I really believe none of the buttons work. Volumn down at 99%. Volumn up on a hardreset. The buttons work to get me into the various mode either from Windows or at startup, but once into the special modes I think I don't get any buttons. That and the fact that the only thing the endkey button does in turn phone on and off but doesnt end anything is peculiar to a person like me. Anyways I didn't get your Task 29 file yet.
Thanks again
Click to expand...
Click to collapse
That's because I forgot to upload it. Sorry. here it is.
I know you feel that way, but there are a few things we can try. We just need to go step by step to rule things out. Please trust me on this. I'm trying to keep from saying that your phone is having hardware troubles, because I think it is fixable as it is now. We just have a certain order to attack it from.
I do appreciate the help I have always gotten from this site and thank you. The worries that I have are actually getting any buttons to work when doing any work on the phone outside of the windows format. I noticed that at 99% I am to tap the vol. dw button and I don't think thats gonna work. From my desktop computer exsperience that I have I know there is actually 3 modes happening that work in conjunction with one another. CMOS MSDOS and Windows. I don't think its a windows issure and I don't know what else there is in these phones that work, but I will try this program and thank you again. I will let you know where I at with it in a few.
Hootyhoo said:
I do appreciate the help I have always gotten from this site and thank you. The worries that I have are actually getting any buttons to work when doing any work on the phone outside of the windows format. I noticed that at 99% I am to tap the vol. dw button and I don't think thats gonna work. From my desktop computer exsperience that I have I know there is actually 3 modes happening that work in conjunction with one another. CMOS MSDOS and Windows. I don't think its a windows issure and I don't know what else there is in these phones that work, but I will try this program and thank you again. I will let you know where I at with it in a few.
Click to expand...
Click to collapse
Even if holding voldown doesn't work, you will still be able to boot back into the bootloader. task29 will clear the internal memory of everything. There won't be anything to load, so it will hang on the splash screen if it tries to load. Don't worry. We're going to try everything we can before we call it quits. This is a unique problem, but I think it can be fixed. Like I said, we just have to go in order.
Okay. First of all I'm sorry for the void between your last message and now. Its been a wild week so far. Thanks again for the help so far. With that said and done heres were I am at. I tried your Task 29 software and it did seem to be different at visualy. Possible problem is, is that when it rebooted after following your instructions, it did not go to the tri colored screen but to a blueish looking screen with the words Touch Pro 2 across the center. It almost looked like a splash screen, but never went any farther. So I'm not sure if that was acceptable or not as a proper task 29 but I did go ahead and load the stock rom into it and it went find. After the first reboot it started up with Airplane mode on. I shut it off and turned on the phone again. Everything was okay. You can only assign the phone button and nothing else that I know of so I couldn't see what was assigned to the end key so I pushed it. immediately it stuck the phone back into airplane mode again. Push or I should say tap and it took it out of it. I realize that by default the phone set the long press end key to shut the airplane mode on and off, but I am tapping and only tapping as I always have in the pass. Well so I got the idea of trying a different Rom in hopes that something will program the key to not shut the phone function off everytime I accidently tap the end key, I tried a few and Sharkies seems to surfice for the moment. By tapping the end key only brings up the Comm Manager instead of shutting the phone function down. Funny thing is though is that also was Sharkies default for long press. The problem has become with that now is that it has been just popping up by itself over and over. So I started tapping the end key when it popped up and suddenly it seems that it worked until I realized the the end key doesnt seem to be working at all. It clicks but thats it. So what to do now. Good thing at this time is the fact that I dont have to worry anymore about accidentally tapping the end key.Good chance it could be the button it self. I don't know. What ya think?
Hootyhoo said:
Okay. First of all I'm sorry for the void between your last message and now. Its been a wild week so far. Thanks again for the help so far. With that said and done heres were I am at. I tried your Task 29 software and it did seem to be different at visualy. Possible problem is, is that when it rebooted after following your instructions, it did not go to the tri colored screen but to a blueish looking screen with the words Touch Pro 2 across the center. It almost looked like a splash screen, but never went any farther. So I'm not sure if that was acceptable or not as a proper task 29 but I did go ahead and load the stock rom into it and it went find. After the first reboot it started up with Airplane mode on. I shut it off and turned on the phone again. Everything was okay. You can only assign the phone button and nothing else that I know of so I couldn't see what was assigned to the end key so I pushed it. immediately it stuck the phone back into airplane mode again. Push or I should say tap and it took it out of it. I realize that by default the phone set the long press end key to shut the airplane mode on and off, but I am tapping and only tapping as I always have in the pass. Well so I got the idea of trying a different Rom in hopes that something will program the key to not shut the phone function off everytime I accidently tap the end key, I tried a few and Sharkies seems to surfice for the moment. By tapping the end key only brings up the Comm Manager instead of shutting the phone function down. Funny thing is though is that also was Sharkies default for long press. The problem has become with that now is that it has been just popping up by itself over and over. So I started tapping the end key when it popped up and suddenly it seems that it worked until I realized the the end key doesnt seem to be working at all. It clicks but thats it. So what to do now. Good thing at this time is the fact that I dont have to worry anymore about accidentally tapping the end key.Good chance it could be the button it self. I don't know. What ya think?
Click to expand...
Click to collapse
On task29, it removes the entire ROM from the device's internal memory. There was nothing to boot up, so it stopped at the splash screen. That's how task29 works.
Well, this allows us to completely remove the possibility of the software's effect on your problem. What is happening is that the device is recognizing a short press as a long press. Since the button commands are interpreted by the SPL, we've got one last thing to try before declaring hardware fault. We'll need to flash the stock SPL, again to see if that clears it up. To do this, I'd ask that you flash the latest stock ROM to your device. After this, you'll need to go back to the CDMA Hard SPL thread and grab the latest stock SPL. Flash that to your device. Then boot it up and see if the problems persist. If it continues to register short presses as long one, then you have a hardware fault. If this fixes it, then you should be able to flash Hard SPL again and load another ROM with no problem.
Accidental post

[Q] Tried to update, now unuseable

So I have upgraded my i927 captivate glide using the ROM from , but I only Androidupdate com called I927UCLH2_I927ATTLH2_I927UCLH2_Home tar md5 but I get a black screen with a slide down menu saying the date ‘Ongoing’ and an option to change the way that the device connects to another computer.
The update stated pass, it booted and proceeded to tell me that it was updating apps or something like that, then a black screen with the pull down menu from the top of the screen near the usb symbol came up but nothing else. I got a message a few hours later stating that the update application or something like that was not responding and an option to wait or quit. I chose wait, but nothing came of it eventually.
I then proceeded to try reflashing the process with no success even after factory reset and rebooting.
I then tried the pre-release ICS update as per XDA developers and other websites. Same thing
I tried a few other ODIN programs and ROMs but no success. Same issues including the hang up on the Samsung logo. I tried rooting it once and for some reason it started up into what looked like the same pull down menu, but it was requesting that I needed an to input a lock code for the network. I assume that is because my sim card was in it by now, but maybe not. I got so frustrated that I tried the bootloader and update bootloader options using the official ICS update ROM for some stupid reason but nothing. The thing is that at least it booted into the pull down menu that i got with a black screen again.
I then flashed with an updated ICS, CWM6 but cannot do the:
Third: Reboot into CWM6 (Volume- and power) install from sdcard (superuser)
Link to superuser: Superuser-3.2-RC2-arm-signed zip
Forth: Repeat third step above but install keyboard fix.
Link to keyboard fix: CWM_keyboard_backlight_fix zip
since I do not have an SD card that is working. I did get the SD Card in the device but I have always had problems with the format of it and I cannot put the zips onto the card due to the computer Win7 not recognizing it. I tried reformatting the device is HPUSB format program and windows. I inserted the card into the device to hopefully have it recognized on windows, and i gave me an option to format the SD card. So I proceeded and success. I was able to put the Zips onto the card. However, I returned to the CWM6 screen by pressing the VOL- and power keys but the files were no where to be found on the SD Card.
I moved on after a few other tries at it, so I tried to go backwards to the Gingerbread ROM. No success, same hanging issue at the Samsung logo.
I then tried to reflash with the devices original ROM as provided by DroidAngel on androidupdate com. Both without success.
I wanted to try the process involved on the 'stuck on boot screen' thread, but I cannot access the zip files on the sdcard in order to be able to do that.
I also bought my phone unlocked from the US (ATT version) and had it sent to me in Canada unlocked so I cannot just return it to the seller to get a new one, so my new phone is pretty useless.
I have spent two days reading through and trying different fixes and updated ROMs on multiple sites but I just cannot figure out what the heck to do now. I know that this site is not to spoon feed people and I am a noob to all of this but I am out of ideas and cannot find anything else to help out.
Where do I go from here. Is there a possibility of reformatting EVERYTHING on the device including all partitions etc etc.? I mean the hardware is fine, it is just a software issue. I do this to my laptop whenever I get into a bind.
Have you tried booting into CWM and restoring factory?
sent from my captivate glide running ICS (NardROM 0.3 Rooted)
Just a note, the SD card you're seeing in CWMR isn't actually your physical SD card, its the internal phone memory. I don't think we have a version of CWMR that reads the real external SD unless modified. So anything you put on it won't show up there. The folder structure will look like ... /sdcard/external_sd/ where /sdcard/ is where you want to put your files for CMWR to see, /external_sd/ is your physical card you can take in/out.
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
EaglesIII said:
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
Click to expand...
Click to collapse
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Evil Alex said:
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Click to expand...
Click to collapse
Okay, so right now I can still get into the download mode to flash, the CWM6 to factory reset and reboot which I have tried already as stated, and I have not been asked for the network key again since the one time quite a long time ago. The network key is only asked when I load one of the other custom ROMS though, but I have not tried any of those in a while.
I am stuck at the black screen with white Samsung logo.
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Got it running on Bio360 but 'Not Registered on Network' now
Evil Alex said:
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Click to expand...
Click to collapse
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
EaglesIII said:
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
Click to expand...
Click to collapse
You're very welcome! Glad to hear the phone is usable again. In order to get data back you will have to set your APN manually. Stock ROMs come with the APN settings for all providers it is expected to be sold with. But custom ROMs usually come without those settings. You can find the APN settings for your provider online, just do a search. There is even an app for it, but the name eludes me at the moment. You'll need wifi to get the app, though! Once the settings are in place (You put them in under wireless & Networks), you'll have data again.
As for the limited functionality, I had the same thing, at first. The upgrade was broken for me, I guess some settings/apps were causing problems. So, after flashing the upgrade, I did a factory reset in CWM. I also wiped the cache, and the Dalvik cache, for good measure(Under advanced in CWM). It rebooted, said it was upgrading and installing, and I let it sit for a few minutes. Then I was greeted by an initial setup screen, and the phone has been on a working ICS ever since! I did lose all my settings and such, but I had a back-up of those with Titanium Backup, and got those back that way.
Hope this will help as well.

Help recovering a "bricked" MTCE, PX6 (Xtrons) unit

Hi all,
first post in this section, so be nice I have a very recent build Xtrons TQ700L unit that i have managed to soft(?) brick after rooting and removing a factory app ("Easy Connect"). On boot I get the initial logo, then after a long time a black screen that goes nowhere. I'm looking for advice on the best strategy to recover/rebuild it.
Hardware details...
build number:
rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct2.20200521.120545 test-keys
MCU version:
MTCE_GS_V3.53_3
As i understand it i have an "MTCE, GS" MCU and can ONLY flash MCU updates from the GS manufacturer. The MCU is probably not the problem here though.
I have a PX6, Android 10 build date of 20200521. Am I correct in saying i can flash any android 10 ROM designed for the PX6 that is newer than this date? Are the only differences between manufacturers cosmetic, like the nice launcher Xtrons supplies?
When i look on Yandex (https://yadi.sk/d/umCvHqCDzHccr), there is no PX6/Android 10 firmware at all from "GS", but there is from "HCT". Should i be looking at flashing the HCT/PX6/Android 10 firmware date 20200612 from the recovery menu? I can get to recovery easily enough by holding, then double clicking the reset button - i just dont know whether i should be flashing part of or the whole of the above package to fix my brick.
thanks.
So in case this helps anyone else, it was an easy fix. Baby steps below.
- grab the latest "Android 10", "PX6/RK3399" factory ROM either from threads here, or from Yandex. I found HA3_RK3399_10.0_ota(20200706).zip here on XDA.
- unzip the outer layer ZIP file and copy the inner "update.zip" to a micro SD card. The stock recovery systems dont allow any selection of ROM file names, so it must be update.zip.
- put the SD card in the "GPS" SD slot.
- with the unit on, reboot to recovery. My way was using a nail to hold the reset button in until the touch button lights began the flash, then quickly release and double click the reset again.
- in recovery, menu items can be scrolled through by either clicking the reset button, or (in my case) touching anywhere on the screen (easier).
- push and hold the rest button (or screen) to select the item.
- do a "wipe data/factory reset" (i guess) to be sure of cleaning out the old mess.
- then do "Apply update from SD card". it should automatically find the update.zip and apply it to all partitions.
- select reboot. Done.
The ROM i used was a "HA" branded generic ROM, so it didnt have the same launcher as my original "GS" (Xtrons) branded ROM. Xtrons wouldn't supply me with their stock ROM when i asked. The generic one was a little better anyway, since it has a stack of boot animations to choose from, whereas the Xtrons one only had the Xtrons logo. It also doesnt have the Easy Connect app, which is what I was trying to remove in the first place!
Additionally, i was able to obtain root easily by using the wifi ADB method here.
I did the same thing. Stupid app kept opening.
I don't have a micro sd card slot, hope it works with usb stick. Don't have one at the moment to try.
Same as yours.
Also, entering recovery mode you..
Hold reset button for 10 sec, release and immediately press it once.
I have a dicola px6 mtce
I'll update if i get it working.

Categories

Resources