Database Users

[ROM][WWE][Nov.17.2010] T WM w ANDROID COOKED IN! BlueTopia 1.0.3 by cmylxgo

ANDROID THE EASY WAY v3
My UltraLite ROM with the following Android Built In (Screens in Post 2):
Desire Sense - BlueTopia v1.0.3, by cmylxgo.
FAST, STABLE, COOL as Heck! Thank you cmylxgo for allowing me to cook your fantastic builds into my ROMs. If you like this version of Android, please take the time to thank cmylxgo in his thread.
Booting into Android is controlled by My Android AutoBoot MortScript.​
This ROM is for people who want to run Android on their HD2, but maybe don't know where to start. I've spent many hours getting this all working together and working out the bugs so you don't have to. Just run my AutoFlash file, Wait 20-25 minutes, and you will be running Android on your HD2. No worries about where to copy things, or what Radio works with what ROM.
IT JUST WORKS!!!
(As well as Android CAN work on an HD2)​
The Windows Portion of this ROM is based on latest T-Mobile 3.14 with almost everything removed, and Radio 2.15.50.14. Not really worth booting into WM as it's VERY stripped down, and it's just used to load Haret to get Android going.​
If you want to Flash this ROM, then change the Android build to another, you may, by replacing the Android Folders on your SD Card with your desired Build.​
Please read all below before starting. Warning, this will erase all your data and your current ROM. Please backup your DATA First! You can always flash back to your prefered ROM if you don't want to keep this.​
Watch the Videos or Follow the 7 Steps Below.​
Step 1. Download: Download all files listed here.
a. HardSPL3 Required. If you already have HardSPL3 flashed, you can skip this.​
b. Task29 provided by doloop.zip Required.​
c. AutoFlash SuperSport - BlueTopia 1.0.3 by cmylxgo - Radio - Hasterin Kernel 8.5.1 v3 Required.
Grab All 4 Parts. Sorry so LARGE!! It's the only way to include everything. MediaFire allows Multiple downloads at a time, so if you have a fast Connection, grab all 4 pieces at once. Mirrors at bottom of this post.​
Step 2. Unpack Files: Unzip Task 29 and HardSPL3.​
Step 3. Prepare SD Card: Clean old Android and any Android helper folders OFF SD Card ie: Android, Media, FilesToBeDeleted, etc. Recommended - For best results, backup your card, then re-format FAT32.​
Step 4. Insert SD Card: Be sure your SD Card is re-installed in your HD2 if not already.​
Step 5. HardSPL3: If needed, Flash HardSPL3: Run HSPL3_PKG.exe that you extracted earlier, or be sure you’ve already done it in the past. Follow the instructions found HERE if you don’t know how to install it. This will take about 3 mins.
Step 6. Task29: Run Task29 provided by doloop.exe that you extracted earlier. This should be done before ANY Flash, not only this one. If running Windows Vista or 7, you must Right Click and Run as Administrator. Be sure your phone is connected by USB before running and follow the instructions. It’s just like flashing a ROM. When it reaches 95%, press and HOLD the Volume Down button until it reboots into Bootloader Mode (Red, Green, Blue Screen). This will take about 2 mins.
Step 7. Flash My ROM: Be sure your SD Card is installed in your HD2, then Flash your phone with my ROM. Be sure your phone is connected by USB then enter Bootloader Mode (Red, Green, Blue Screen) by Holding Down the Volume Down button while turning on phone. Run the file "AutoFlash SuperSport - BlueTopia 1.0.3 by cmylxgo - Radio - Hasterin Kernel 8.5.1.part1.exe", the one with My Icon. Follow the Instructions until your phone Reboots. This will take about 9 1/2 mins. Windows will Automatically Reboot a couple more times. Please Wait for Android to start loading. Do NOT touch anything during this step.
Step 8. Wait while Android Starts: Android will now start initializing. You will see the Green hTC logo. Allow Android to set up the Data Space. This takes a LONG time! Be VERY Patient. Up to 10 mins the first time (Mine was 8 mins, Future boots after the first time boot quickly). It will sit on the HTC logo for a LONG time, then blank screen, then final boot. When you see the Slide Down to Unlock Screen, Android is running!!! Complete the Android Setup, then do a final Reboot to finish setting all the programs. To Reboot Android, press and hold the Red Hangup/Power button, then select Reboot, then Select Normal and OK.
That's It, Enjoy!
Installation Video:
How to Prepare for and then Flash My ROM with Android Included
To Play Larger, Click the Video During Playback to open in YouTube.
TIPS:
To Sync Android with your PC, you can use your Google Account, or HTC Sync. HTC Sync allows Photo and Music Sync along with APP Installations.
If you want to prevent the phone from booting into Android, press cancel when prompted just after phone starts up. It will be in WM on a white screen. You only have 6 seconds before AutoBooting into Android Happens.
To Flash another ROM, enter Bootloader - Hold down the Volume Down button while powering on your phone, then Flash your prefered ROM. You can run another Windows Mobile ROM and keep the Android Build on your SD Card if you prefer. Just flash another ROM, then browse your SD Card to the Android Folder, then run CLRCAD.exe, then haret.exe.
Installation Timing Table:
Start Flash
00:00
WM Flash Complete after
9 Minutes 20 Seconds
2 Reboots - LET THE PHONE DO THIS. DO NOT Manually Reboot your phone.
Moving Android to SD Card. Looks like nothing is happening, but it is. Be SURE to wait for this.
3 Minutes
Reboot to Green hTC - Also let the phone do this. DO NOT Manually Reboot the phone.
Green hTC Turns Off after (Important, This is where the Data File is being created, wait for this)
7 Minutes 30 Seconds
Droid Sound and Blue Logo after
30 Seconds
Android Lock Screen after
1 Minute 30 Seconds
DONE! Unlock and finish setting up accounts, etc... NOW you can Manually Reboot one more time.
This is how long everything takes on My HD2. Your's might be slightly different, but it should be within a minute or two for each step. Different SD Cards MIGHT effect the time taken. If something seems to be too long, give it an additional 1-2 minutes for each step, then try again.
Thanks to Scabes24 for this Mirror:
MegaUpload Mirror - http://www.megaupload.com/?f=E28BQS7N
Change boot time of AutoBoot (2 Second) (6 Second)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Manilla ROM Upgrade.
This ROM is an upgrade for the ROM posted on the first page. This ROM will replace the ROM on the First post. If you have not flashed the ROM on the first page, you will not get Android with this Upgrade.
What this ROM will do:
This is a Fully Capable Sense ROM with extras included, Swype, IME Keyboard, etc. It's based off the latest T-Mobile v3.14 Release ROM. It does not include the Radio or Android. I HIGHLY recommend using THIS RADIO for use with Android.
You can also use this ROM if you want to run another Android Build. As long as you've installed the Android build into the 'Android' folder on your SD Card and CLRCAD.exe and haret.exe are both in that folder, it will boot as before.
DOWNLOAD NOW
Grab BOTH parts and run the first part. After Flashing this ROM, do a Soft Reset, then wait for it to automatically reboot twice! It's now ready for Android.

Reserved for Future Use
Screen Shot of my Stripped Base ROM
Screen Shots of cmylxgo's BlueTopia 1.0.3

if i had just installed this on the 16th the other way is there any differances to flashing agin this way or just keep what i have?

2002blackedge said:
if i had just installed this on the 16th the other way is there any differences to flashing agin this way or just keep what i have?
Click to expand...
Click to collapse
This particular build was not up yesterday. It's a new Android Build. If you like what you have, you can stay with it. Check out the Android Build Link above to decide what you want to do.
PS: For anyone who has not already downloaded this, Please wait! I'm uploading an update. Nothing major, so if you've already got it, it's fine. Just differences in how it copies the Android files over to SD and how it boots up. I'll post new links when complete.

i will probably reflash being that there was quite a bit more added to the android rom plus some fixes to things, how often will you be updating yours to keep up with the android rom? sorry for the noob question now but how would i go about reflashing after having ur other one installed, just reformat the sd card fat 32 and do it or do i need to use task 29 again?

2002blackedge said:
i will probably reflash being that there was quite a bit more added to the android rom plus some fixes to things, how often will you be updating yours to keep up with the android rom? sorry for the noob question now but how would i go about reflashing after having ur other one installed, just reformat the sd card fat 32 and do it or do i need to use task 29 again?
Click to expand...
Click to collapse
Actually, if all you want to do is update the Android Build and you are happy with the Windows Mobile portion, you can just download the new Android Build from cmylxgo's thread and replace it on your SD Card. I recommend reformatting your SD Card, but you can just delete all the old Android folders if you want. Remember, you will loose all your Android settings, etc.
I have heard about a program called Titanium Backup that is supposed to backup/restore programs and settings, but I have not used it yet. Try a search for it if interested. It's also in the Android Marketplace, I believe.
PS: The ROM cooked into My Release today is BlueTopia 1.0.2. cmylxgo released BlackTopia 1.0.3 today. Be sure to get the one you want.

for the android folders that get deleated, in the root menu of the sd card is it just the folder that says android and then all the folders inside of it, or are there other folders in the root of the sd card?

YouTube Installation Video
I just uploaded an HD Quality video to YouTube with Instructions on how to Install this ROM. It's at the bottom of Post #1 or on the YouTube site HERE.
It may be a few minutes before it becomes live, and a couple more before it's HD Quality. I JUST uploaded it.

2002blackedge said:
for the android folders that get deleated, in the root menu of the sd card is it just the folder that says android and then all the folders inside of it, or are there other folders in the root of the sd card?
Click to expand...
Click to collapse
Definately that folder and everything inside, but there may also be other folders.
On my SD Card, I would delete the Following
.android_secure
.footprints
Android
LOST.DIR
media
rosie_scroll
rssreader
Each build is a little different. Also depends on any apps installed.

mms
anyone get pic msg working i can send txt msg but not pic msg!!!

How long is the battery lifetime? About a day?

ihateu said:
anyone get pic msg working i can send txt msg but not pic msg!!!
Click to expand...
Click to collapse
What Internet Provider are you with? Im on ATT, and I need to install a patch to get it working correctly... Not sure if it would help you or not. Once you install it, you can't uninstall it. You'd need to load Android again to remove it.
The developer of the Android Build says the patch is for anyone that's not strictly on T-Mobile, so I don't know who all it would help. You can get it here:
http://forum.xda-developers.com/showthread.php?t=820696 attached to the first post at the bottom. It's called Topia.Series.NON-TMOUS.Patch.rar and installation instructions are also on the bottom of first post.
beenja said:
How long is the battery lifetime? About a day?
Click to expand...
Click to collapse
If you are VERY conservative, it will go a day, 8-12 hours. But, the way I use it (Ride it like a Race Horse), I can kill the battery in a couple hours. Lot's of Email, Internet, Youtube, Games, etc... Android is a new toy for me, so I use it hard.

still having a pretty bad issue with the touch screen not working all the timo, have to keep locking and unlocing the phone until it comes back. any thoughts?

The problem i had was that after i did everything i think i interupted the last part of the syncronisation, so when it was in stock mode it didnt boot android. If u will ahve this problem just restart the last part of the instalation(Just run the "AutoFlash SuperSport Android BlueTopia 6" wich has the superman mark =) and dont interupt anything, Let it work and after a while it should boot android , It is working perfectly and is realy nice to have android. It kicks WM6.5 sence ass

2002blackedge said:
still having a pretty bad issue with the touch screen not working all the timo, have to keep locking and unlocing the phone until it comes back. any thoughts?
Click to expand...
Click to collapse
I haven't run into that at all yet. I will keep my eyes open and if I run into a fix, I will share.
Samorau said:
hmm im having a little problem, after i done everything you said, i folowed the youtube guide, I got into stock android thingie but when it tries to boot android it says "failed to load file/storage card/android/zImage What is the problem :/?
Click to expand...
Click to collapse
It sounds like files didn't finish copying to your SD Card.
After the Flash started, did you tell the phone to reset at any point during setup? The phone will do all the reboots for you until Android Starts. If you reset the phone at the wrong time, it might have prevented all the Android files from copying to your SD Card.
Try flashing again, and don't touch until the Android Lock Screen Appears.

I installed the previous build of this ROM and love it - using the 0.6 version of BlueTopia. I have a few minor issues, but nothing serious. Is there any compelling reason to update to the new Android build? I ask becuase I have all my settings etc and dont really want to start over just for the sake of installing an update.
T-Mobile USA HD2

Samorau said:
Problem fixed =)
Click to expand...
Click to collapse
Can you please repost the question and what you did to fix it, just for others benefit? Thank you! Just in case anyone else is having the same problem...

jasonatr0n said:
I installed the previous build of this ROM and love it - using the 0.6 version of BlueTopia. I have a few minor issues, but nothing serious. Is there any compelling reason to update to the new Android build? I ask becuase I have all my settings etc and dont really want to start over just for the sake of installing an update.
T-Mobile USA HD2
Click to expand...
Click to collapse
I think if it's working for you and you are happy, stick with it. The updates are mostly theme updates and fixes for things that don't work. If yours works I'd leave it. 0.6 is still a GREAT build.

touch screen
I'm having same issue with touch screen haven't been able to get mines working for hrs now how are u getting yours to come back
BTW mine is on the lock screen that u have to slide down

I would recommend removing the battery and reboot. See if it clears up. If not, might need to start from Task29.
Sent from my HD2 using Android BlueTopia & XDA app.

How to REALLY Root and update your 2.2.1 Slide to cyanogen 7 - Noob Edition Summer 11

You have undoubtedly seen lot of Rooting guides for the Mytouch 3G Slide, claiming to root the phone:
wiki.cyanogenmod.com/wiki/TMobile_myTouch_Slide:_Full_Update_Guide
http://forum.xda-developers.com/showthread.php?t=1108316 New way to downgrade from 2.2 to 2.1
http://forum.xda-developers.com/showthread.php?t=999121 Ultra Easy Rooter [dbzfanatic][xologist]
http://forum.xda-developers.com/showthread.php?t=1025336 How-To [Root][NewLinks] The myTouch 3GS if you updated to Offical 2.2.1 and lost root
SuperOneClick doesn't work. Nothing works, I've tried them all several times from several different angles. Therer is some sort of NAND lock on the phone, above and beyond typical. Anyways.
None of the aformentioned guides work, so won't waste your time like I did. They are also all written by people who can not communicate well with other human life forms, and they assume you have a CS and/or IS degree, and also assume you have all the software installed on your machine that they have on theirs, and have all the same settings on your phone that you "should" have on yours and they also assume you are doing some "obvious" steps in the middle of their steps that you should know how to do. They won't tell you that, but they do. So here is the REAL definitive step by step guide, with pics, on how to do it. BTW, you don't need a gold card. You don't need to mess with any consol crap. This should take 15-20 minutes max. What we're basically going to be doing is downgrading to 2.1-update1, then rooting, then putting on the Cyanogen Mod, then adding the google apps (which are not included in the cyanogen mod). I've put as many pics as I could and tried to do a step by step that ANYONE can follow.
I was using Windows 7 64-bit SP1 and I think these are the things that you need to have set up, you may not need them but I was trying so many of everything that I don't even know if they are all required, I'm sure I missed some things, but I will keep editing this guide as needed)
*Make sure you have at least 25MB of free space on your phone's internal memory.
*Make sure you've backed everything up you want to (text messages, bookmarks, programs, etc) But the google cloud should keep most your other stuff okay. (email etc) http://tinyurl.com/3b4qp6q
*Turn USB Debugging on your phone. (Settings, applications, development > USB Debugging - check)
*Turn phone to charge mode only when you plug in the USB cable
*PDAnet was running on the PC (This is required it will install the correct driver for step 1, though it's a tethering app and you won't need it for that) - http://junefabrics.com/android/download.php
1. Plug in phone and go to device manager from control panel on your computer.
You open the "Android USB Devices" and see what driver it says.
If it says something like "Mytouch Slide 3G"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
go to Update driver > Browse my computer for driver software > Let me pick
pick this one: "ADB Device Interface" , say okay, etc.
If it does say "ADB Drvice Interface" you're good. Exit out of that.
2. Download "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" from here http://www.htc.com/us/support/t-mobile-mytouch-3g-slide/downloads/ (157MB)
3. Go to your temp windows folder. IF you do Start > Search %TEMP% it should pop up. Keep on eye on this folder as you do the next step. (Maybe sort by date modified to help)
4. Double Click the "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" file and have it extract everything. At the first main screen, just wait there with it open and not installed.
You hopefully should have seen some folders be created in your temp file. There were 2 on mine, like so, check them both out:
When you see the one that looks like this:
and has a folder structure like this:
that's the folder you want to copy. So:
5. Highlight the folder with "ARUWizard.exe" and "rom.zip" in it. Mine had about 74 files in it. Copy it, and copy it to another part of your hard drive, and rename that awful folder, sheesh. (not needed)
6. You can close out of the Rom Update Utility.
7. In that NEW copied folder, delete "rom.zip"
8. Download the ~140 MB "ESPRIMG.zip" from here: http://www.4shared.com/file/OsmF_ZD7/ESPRIMG.html
9. Put it into the folder that we copied out, and rename it from ESPRIMG.zip TO rom.zip
10. Now, while you are in that folder, "ARUWizard.exe" check check, next, etc.
11. This will downgrade your phone from 2.2.1 to 2.1-update1
12. Tada! Good job. Now, go download the lastest Cyanogen firmware ROM here: http://download.cyanogenmod.com/?type=stable&device=espresso
13. Rename the "update-cm-7.X.X-Slide-signed.zip" to "update.zip"
14. While you are doing this, download the lastest Google Apps from here: http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps Mine was called "gapps-gb-20110613-signed.zip" and put that on your phone's memory card as well, no renaming needed.
15. Turn off your phone and take out the memory card and put it in your computer (or turn the phone back into a mountable drive) and copy over the update.zip onto the root director of your memory card.
16. Hold "down volume" and "power" which will boot you into a techy looking screen. Ignore any errors, the volume up and down navigates, so go into "Recovery" Mode.
17. Once in the Recovery, you will see a device with a triangle. Press "Volume Up" & the "Power" button.
18. Select the option to Wipe data/factory reset. Then select the option to Wipe cache partition.
19. See the option to "apply sdcard:update.zip" ? Do it, with power as confirm. This will put the Cyanogen mod on your phone!
20. Reboot system now. Now, you should boot into Cyanogen 2.3.x! However, you will notice you don't have any of the google apps.
21. So, Now, go into your programs on the phone, and you will see "Rom Manager" a eye with a tophat. Say "Install Rom from SD Card" and pick the "gapps-gb-20110613-signed.zip" You may have to fiddle with the plugging in USB/etc to get access to this, you don't have to buy the program, it will do it, but you have to have it set up so you can see the MicroSDcard, etc.
It will reboot your phone and you will now and install all the google apps. The most important one is MARKET, so you can download stuff. It will now go through all the TOS for each google program you said you want. The rest the wizard should navigate you through properly.
Holy hell this was a terribly troubleshooting process which probably took me 20 hours to figure out they were ALL wrong. Big thanks to "Da Maestro" who helped me on Cyanogenmod.
Enjoy!

wait wait wait... so will this method revert the hboot from 1. whatever to the older version and allow S-OFF?!

yeah, I don't even know what you're saying, I'm such the nube. I don't think this deals with the S-On/Off problem though. I saw some other posts that fixed that. This method does nothing to do with that, as far as I know
All I'm saying is I have Cyanogen 7 on my phone and this is how I did it from 2.2.1 stock.
txdeathray said:
wait wait wait... so will this method revert the hboot from 1. whatever to the older version and allow S-OFF?!
Click to expand...
Click to collapse

as far as i'm aware of, there's no S-OFF after you upgrade to 2.2.1, so i was thinking if you can check your hboot by powering off your phone and then turn it on by holding down volume down and power button. hboot version should be on the very top of your screen.

Bootloader error
I get 140 bootloader version error from the RUU. So far I have not been able to get any of the root mrthods to work with my slide.
Any ideas?

nikolag said:
I get 140 bootloader version error from the RUU. So far I have not been able to get any of the root mrthods to work with my slide.
Any ideas?
Click to expand...
Click to collapse
Well at least your not alone in that club. Getting the same error, even using a goldcard. I guess back to the drawing board for us at least.

yeah I had that error too,
http://forum.cyanogenmod.com/topic/28205-stuck-on-step-8-rooting/
EDIT: To fix it, make sure PDANet it installed and that will install the driver so you can change it from "t-mobile mytouch 3G" to "ADB Device..." It's step 1.
raziel420 said:
Well at least your not alone in that club. Getting the same error, even using a goldcard. I guess back to the drawing board for us at least.
Click to expand...
Click to collapse

That is one thing I didn't see, although upon checking it,s not there, and I do have the android SDK installed :/
If it helps any I'm on windows 7 ultimate x64 (since the problem seems driver related).
*edit 1* I keep seeing places where it says to check for the ADB interface driver, but nobody seems to know how to actually install said driver, or where it can be found at.
*edit 2* Turns out that PDAnet is what supplies the ADB driver, so as it happens that IS required (and here I thought that was a stupid tethering app)
*Edit 3* So just to make sure I downloaded the software on the posted links just to make sure some of the other versions I had were not incompatable, and still no joy. At this point I've spent a good 6 hours trying to root this phone and growing significantly more annoyed with it. If anyone has any feel free to contact me, I'd really like to get this working.

hey thanks, I'll edit the guide to say it's required.

Same here, went through all of the steps, still keep getting the 140 error.
edit* went all the way through the steps again very thoroughly, still getting the same error 140. Any Ideas?

It was such a complicated process, dealing with all the other guides some part of them may have worked that I missed. Maybe you do indeed need to make a gold card. It didn't work (I think) on one MicroSD card so I changed to another one.
So I guess make a gold card and give it a try. This is the guide I used to make a gold card:
http://wiki.cyanogenmod.com/wiki/Howto:_Create_a_Goldcard
Thanks for helping me get this guide correct.
One thing I did have to do is change USB ports and USB cables, as stupid as that is, I know, I know. The ones in my monitor worked but the front ones on my computer didn't work with the ROM update utility, but I think the error code I was getting was 170 or 171 USB disconnect error.
dgrwe2512 said:
Same here, went through all of the steps, still keep getting the 140 error.
edit* went all the way through the steps again very thoroughly, still getting the same error 140. Any Ideas?
Click to expand...
Click to collapse

What if you were to save that rom.zip file directly on the SD card, as the update.zip file first? Would that load 2.1? Because the installer wont.
I'm going to try it....
Nope, didn't work.

The gold card would be great if I had a second sd card, guess I will have to go buy one if I want to regain root.

the gold card worked for me just fine after getting my replacement phone on 2.2.1 all i did was back up everything on my sd card make and use the gold card get root and put every thing back on my sd card just fine.

dgrwe2512 said:
Same here, went through all of the steps, still keep getting the 140 error.
edit* went all the way through the steps again very thoroughly, still getting the same error 140. Any Ideas?
Click to expand...
Click to collapse
Do you have PDANet Installed?

Yes, its installed and running. Also, I made a gold card out of my SD card and tried again, and still got the same error. I am starting to hate T-Mobile!

katbastard said:
the gold card worked for me just fine after getting my replacement phone on 2.2.1 all i did was back up everything on my sd card make and use the gold card get root and put every thing back on my sd card just fine.
Click to expand...
Click to collapse
Do you have a link to the Gold Card method that worked for you? I keep getting a bootloader error with this method, about ready to give up.

dgrwe2512 said:
Do you have a link to the Gold Card method that worked for you? I keep getting a bootloader error with this method, about ready to give up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1025336
did this as it reads, i am not a super geek, just know how to follow a list of things to do. i rooted one other time before this when it was really hard to do still. i thought this way was easier

I'm kinda confused why there is gold card discussion here. The method outlined in the first post specifically says that you don't need a gold card. Does this method not work and is that why you are trying gold card stuff?

dgrwe2512 said:
Yes, its installed and running. Also, I made a gold card out of my SD card and tried again, and still got the same error. I am starting to hate T-Mobile!
Click to expand...
Click to collapse
I don't think should have it running while you root. (I would assume that would just cause problems.) You just need to install it for the usb drivers and make sure it works.

[GUIDE] Android 8 API27 SUPERMOD for YT9216BF YT9216CFJ YT9216BJ YT9216BFJ YT9216CJ - root, Viper4Android, TWRP, Custom UI, brick recovery and more

Hi all,
If you want to greatly improve the way your head unit works, sounds and looks like - you've come to the right place!
Why install this?
With this package you will greatly improve:
Stability
Speed
User Interface
Sound tweaking options
Customisation options
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ON PHYSICAL BUTTONS: this software has only been tested on head units with no physical buttons (like volume) | Before making any changes, access the CAR SETTINGS -> FACTORY SETTINGS -> ENCODER SETTINGS on your head unit and take a screenshot of the current settings (see example below). After installing the package, go back to these settings and adjust them if needed. If that doesn't help and if you can't successfully re-calibrate the buttons after installing the firmware, restore your backup
Disclaimer
I do not create the software itself but rather use research and put together different mods and hacks into one package that includes very user-friendly step-by-step instructions on how to install it all. You will find the links to original posts in the instructions pdf's if credit is due. The software might include smaller changes made by me and has been fully tested in real units.
This firmware works on the following 1Gb RAM and 2 Gb RAM units with fake Android 8.1, 9.0, 9.1, 10 and Android 11 installed, with screen resolution of 1024x600 px. It will not work on Tesla-style units:
- YT9216BF | YT9216CFJ | YT9216BJ | YT9216BFJ | YT9216CJ
!! TAKE A PICTURE OF YOUR SYSTEM INFO AND KERNEL VERSION BEFORE DOING ANYTHING TO YOUR HEAD UNIT !!​
The zip file package contains:
Modified firmware - courtesy of Stranger21UFA @ 4PDA (link to the original post)
TWRP (separate folders for 1GB and 2GB RAM units)
Root via Magisk
Viper4Android
Car Launcher
Boot Animation
SEPARATE INSTRUCTIONS ARE INCLUDED IN EVERY FOLDER
​>>>> ALWAYS BACKUP YOUR UNIT BEFORE MAKING ANY CHANGES TO IT <<<<​​!! IMPORTANT !!​This is a fairly advanced installation process and will require you to follow the individual guides included in the software package - to the letter. Failing to do so, will (in "best" case) result in a slow and buggy head unit and in the worse case - brick it altogether.​
DOWNLOAD
YT9216BF * YT9216CFJ * YT9216BJ * YT9216BFJ * YT9216CJ - supermod software package & drivers
STEP-BY-STEP GUIDE (upgrading from working stock firmware):
DO NOT SKIP ANY STEPS, AND INSTALL EVERYTHING IN THE CORRECT ORDER. STEPS 5 AND 6 ARE MOST CRITICAL.
Proceed to download the software package for your unit and the drivers package in the same folder
It's highly recommended to do these upgrades with your unit connected on your desktop, rather than in the car. Video Guide
Install the Mediatek & ADB drivers on your Windows computer. Video Guide - use the same principle for ADB drivers.
Backup your current system by exporting a full memory dump. Video Guide
Import back your memory dump from step-5 to ensure it fully works. This is how.
Install the package. Separate instructions are included in every folder of the downloaded zip file. Follow them by the order.
IF THIS SOFTWARE PACKAGE HAS BRICKED YOUR HEAD UNIT AND YOU HAVE YOUR BACKUP AVAILABLE, follow the steps below:
DO NOT SKIP ANY STEPS, AND INSTALL EVERYTHING IN THE CORRECT ORDER.
It's highly recommended to do these upgrades with your unit connected on your desktop, rather than in the car. Video Guide
Install the Mediatek & ADB drivers on your Windows computer. Video Guide - use the same principle for ADB drivers - (download link is in the video description)
Watch this video on Test Point recovery
Import back your memory dump. This is how.
If successful - try to install the software package again or stay with your original one
IF THIS SOFTWARE PACKAGE HAS BRICKED YOUR HEAD UNIT AND YOU HAVE NO BACKUP AVAILABLE, follow the steps below:
Share the pictures of your System Info and Kernel in this thread and we'll try to help you
------------------------------------------
This post is being frequently updated and you'll find more guides and mods in our signature​------------------------------------------
** IF YOU ARE UNABLE TO RESTORE YOUR UNIT, PLEASE CONSIDER DONATING IT TO US @ ExtremeMOD, SO WE CAN BUILD MORE MODS AND TUTORIALS​
Thanks! And if this post is helpful to you please don't forget to "like" it.
Enjoy!​
[V4A][VIPER4ANDROID][ViperFX][ROOT][TWRP][8227L][YT9216BF] [YT9216CFJ] [YT9216BJ] [YT9216BFJ] [YT9216CJ]

I flashed this on my YT9216BJ and everything flashed 100%, but when I went to reboot I got nothing. It looks like the unit isn't turning on at all. There is a blue LED on the board that is lit up when I connect power. Any ideas as to what went wrong?

dustindavidson900 said:
I flashed this on my YT9216BJ and everything flashed 100%, but when I went to reboot I got nothing. It looks like the unit isn't turning on at all. There is a blue LED on the board that is lit up when I connect power. Any ideas as to what went wrong?
Click to expand...
Click to collapse
Sorry to hear that. Please try the following steps:
1. Completely disconnect your head unit from power, start Flash Tool as Administrator and execute the command: Format+ALL including deleting the bootloader
2. Run the steps from "Brick Recovery" starting with Step-6.
If the above doesn't work - revert back to your original firmware by restoring your backup. Share your System Info screen found in Car Settings as well as your build.prop file and we'll have a look.
Make sure the USB cable is properly attached. The firmware update should not take more than 20 min. If it does, it indicates a bad cable/connection.

My PC will not detect the head unit at all. I'll try the test point recovery tomorrow and report back.

dustindavidson900 said:
My PC will not detect the head unit at all. I'll try the test point recovery tomorrow and report back.
Click to expand...
Click to collapse
In that case, follow the full brick recovery guide in the OP but use your backup to restore it. Once completed, share the info mentioned in my previous reply.
PS try step 1 in my previous reply. Because the unit is only detected once you push "Download" in Flashtool and then connect the USB cable to your computer. Before that nothing will be shown in your Device Manager. If nothing happens in Flashtool then do test point method.

dustindavidson900 said:
My PC will not detect the head unit at all. I'll try the test point recovery tomorrow and report back.
Click to expand...
Click to collapse
you need test point method now to make that alive again , after shorting them for some 2,3 times,run flash tool ,select scatter and press download, then connect headhunt with a usb a cable...

Why would I need to short them for 3 minutes? Isn't shorting them while I connect the usb enough. That's what the test point instructions say.
Edit: I was able to recover using the Android 6 version of the mod. Could not get the Android 8 mod to work. Thank you for the guide

dustindavidson900 said:
Why would I need to short them for 3 minutes? Isn't shorting them while I connect the usb enough. That's what the test point instructions say.
Edit: I was able to recover using the Android 6 version of the mod. Could not get the Android 8 mod to work. Thank you for the guide
Click to expand...
Click to collapse
Glad to hear it! Android 6 is the recommended option, hands down. I made Android 8 for those that can't successfully rollback to 6.
The unit you see in the pictures in the Android 6 post is a project of mine where rollback caused physical buttons to no longer work and I couldn't remap them either. So had to put together Android 8 package.

vijay_joon said:
you need test point method now to make that alive again , after shorting them for some 2,3 minutes,run flash tool ,select scatter and press download, then connect headhunt with a usb a cable...
Click to expand...
Click to collapse
Please avoid flooding this thread with bad or misleading instructions. Thank you

Hi, can I update my yt9216bj without disconnect it from my car?

matteo2 said:
Hi, can I update my yt9216bj without disconnect it from my car?
Click to expand...
Click to collapse
You absolutely can. However you need to disconnect it from car battery.

dustindavidson900 said:
Why would I need to short them for 3 minutes? Isn't shorting them while I connect the usb enough. That's what the test point instructions say.
Edit: I was able to recover using the Android 6 version of the mod. Could not get the Android 8 mod to work. Thank you for the guide
Click to expand...
Click to collapse
i meant to say 2,3 times , my mistake , i amended, shorting them removes the previous preloader stuff , i may be noob here but this is what worked for me

The method I had to use slightly differs from everything I have read.
1.) I wired a toggle switch to my positive lead. Left it in the off position (no power to head unit)
2.) I connected my radio to my PC (most instructions said do this after)
3.) Pressed the download button in flash_tool.
4.) Shorted the test points and turned on the toggle switch. As soon as I flipped the switch the radio connected and flashed %100.
I actually soldered a button to the test points to make it easier and in case I have to do it again. Took me a minute but then I realized it's just the volume up button and the procedure is essentially the same as putting a phone into download mode.

dustindavidson900 said:
The method I had to use slightly differs from everything I have read.
1.) I wired a toggle switch to my positive lead. Left it in the off position (no power to head unit)
2.) I connected my radio to my PC (most instructions said do this after)
3.) Pressed the download button in flash_tool.
4.) Shorted the test points and turned on the toggle switch. As soon as I flipped the switch the radio connected and flashed %100.
I actually soldered a button to the test points to make it easier and in case I have to do it again. Took me a minute but then I realized it's just the volume up button and the procedure is essentially the same as putting a phone into download mode.
Click to expand...
Click to collapse
Soldering a button switch is indeed by far the best approach. However since the majority of folks here are very new to these types of units, the guide makers here aim to keep it as simple as possible.
You're correct about the buttons and their functionality but since the majority of these devices come without physical buttons, you need to force download mode this way.
Finally, test point method is only required if you mess up your preloader. This should rarely happen. The only times you need to write a new preloader is when changing Android API, i.e upgrading or downgrading. And of course if you modify some of the hardware inside.
The majority of times users accidentally delete the preloader from their units in FlashTool.

I thing i found the picture for the test points but i am a little confuses 2 and three are on the same pad but 1 and 4 are different. Do i short them all together?

ian1mm989 said:
I thing i found the picture for the test points but i am a little confuses 2 and three are on the same pad but 1 and 4 are different. Do i short them all together?
View attachment 5389427
Click to expand...
Click to collapse
Also my board looks a little different.

ian1mm989 said:
Also my board looks a little different.
View attachment 5389429
Click to expand...
Click to collapse
Please read the instructions carefully. The link is in the main post.

I have problem with my Unit (Ebilaen YT9216BF 2GB/32GB).
I installed your firmware, and try reboot to twrp (using command: reboot recovery).
After that my unit doesn't boot (black screen).
After that i want to install TWRP (by SPFlashTools as says Tutorial), but Unit was bricked.
My problem is i didn't make backup firmware.
Right now when i try to unbrick my Unit (using a lot of firmware versions) in SP Flash Tools has error: s_ft_enable_dram_fail (4032) (olso when using TestPoint in motherboard).
I think this error means that i have wrong preloader.bin
Any chance to unbrick Unit without having original firmware?
Information about Unit from motherboard:
B9216BF v0.5/C 32G
A005-B9216BF011(9.0)
20210220
Problem solved. I find correcr preloader.bin

ian1mm989 said:
Also my board looks a little different.
View attachment 5389429
Click to expand...
Click to collapse
Doesn't look that different to me. Here are your 2 test points.

dustindavidson900 said:
The method I had to use slightly differs from everything I have read.
1.) I wired a toggle switch to my positive lead. Left it in the off position (no power to head unit)
Click to expand...
Click to collapse
You could share a picture of your soldered button. Some folks here might find it helpful
I'm thinking of making a guide going for a permanent mod, where the soldered tactile SMD button will be accessible through a small hole in the back of the head unit (similar to how you access the RESET button). That way you can use a 'needle' to short the test points, rather than picking the unit apart every time.

Trying to revive a Nook Glowlight 3

Hello,
A long time ago I was using a Nook Glowlight 3. I had rooted it, installed relaunchX and a bunch of readers. Later I switched to Boox Air (for size) and did not use the Nook for a long time.
Recently my son showed interest in reading books from a tablet, and I thought Nook would be suitable for him. However, since it was rooted, it was a bit complicated for him to navigate, so I decided to return it to its original state. Here is what I did to end up where I am now. I will be happy to elaborate on any of these, but I do not want to make my initial post too long, so people will be less likely to skip it.
1. I did a factory reset (by pressing home button during reboot), but this somehow erased the Nook launcher (or maybe I had erased it before, I am almost it was working before). After this reset, upon a boot, I would get past basic setup (timezones and wi-fi) and then get a blank screen.
2. Then using 5taps L-R trick, I turned on USB debugging again and rooted it again.
3. I installed relaunchX and Renate's launcher, but I could not tie them to the home button. I did not know how (I still do not know). I could launch them with adb shell and monkey command though.
4. I tried to get into recovery mode or fastbook through adb (by using things like "adb reboot recovery"), but did not succeed.
5. I downloaded and put the update.zip for this Nook and put it on / as well as /sdcard/ directories. Put Nook to sleep and waited a long time, but no success there either.
6. I was getting frustrated at this point and finally did something really stupid: I unzipped update to a directory under sdcard, remounted various partitions rw and tried to copy all the files coming from update.zip via a cp command. After a short while this command ran, I received an error message, something like "/bin/sh permission denied" (I guess it was referring to execute permissions not being present, and got kicked out of adb shell.
7. Now, the machine is going into factory reset upon boot and after the factory reset it reboots and goes into factory reset again. I tried interrupting the reboot multiple times, pressed various button combinations during reboot, but there are only two outcomes: power off or going into factory reset.
Is there anything I can do? If you can think of a software solution, I'd love to hear it.
I am not good with hardware, and I don't have any equipment (in particular I do not have a UART) but I am faculty member in a physics department in a university, so I can probably access any reasonable electronics equipment. I am willing to do some hardware tinkering, or perhaps to call on a favor or two from some of my experimental colleagues.
I am willing to try pretty much anything since my son is asking if I repaired the Nook almost everyday, and I would like to be able to honestly say I tried everything.
Thanks in advance for any help you may provide.
cheers,
ato

Manually installing an update.zip is not difficult, but that's not how to do it.
If it's really in a loop that you can't break and there's no ADB then you'll have to get more drastic.
One way is to use a UART and interrupt u-boot while it's booting and going to fastboot. From there you can flash a recovery and go to it, do a manual update, maybe fix something that's broken.
Another way is to defeat the flash memory on boot so that it goes to the ROM bootloader. From there you can use my imxlink.exe to load a modified bootloader that will go directly to fastboot,
Either of those two ways requires you opening the case. The Glow3 is not as bad as the Glow2, it doesn't use tape.

Thank you for your response. I can definitely open the case. I found some instructions here:
Barnes And Noble Nook Glowlight 3 Disassembly
This is a disassembly Guide For the nook...
www.ifixit.com
that looks doable.
It sounds like your second suggestion does not require additional equipment (except to open the case). Did you describe elsewhere on this forum how to defeat the flash memory on boot? I have read so many of your postings here in the last few weeks (and I am very grateful for those). I am guessing this might be something you already described before.

I can also order a UART. Will a CP2102 unit w/ 3.3 and 5V be adequate? I just think having a serial connection is so cool that I need to try it.

Yeah, any USB UART will do.
OTOH, I'm a bit more of a fan of the FTDI than the CP2102. I did have problems with a driver years ago but haven't touched them since.
If you fall in love with UARTs and want to use them on something modern, you might need 1.8V
I think that these are pretty cool in having selectable logic level.
https://www.amazon.com/DSD-TECH-SH-U09C5-Converter-Support/dp/B07WX2DSVB/
OTOH, anything will work for now.

I live in Turkey and that FTDI does not seem to be available here. I will keep your recommendation in mind though, thank you!
I ordered a CP2102. They had links to a driver on the order page, hopefully I will not have big problems. It should arrive in a few days.

I will try and open my glow3. Do I need to do anything special about the power? It is almost fully charged, so it would take a long time to drain the battery, but I can certainly try.

OK. I took a leap of faith and opened it up (I have a small window when my kids are sleeping), hopefully did not blow up anything.
Here is a photo in case it might help with someone looking to replace their nook glowlight 3 battery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I need to tinker with J11, J12 or J13, I can tell that they are way beyond my soldering capabilities. Do I need to get some connectors?
Would more detailed pictures help?
cheers,
atakan

No, you don't need to solder unless you want to make it permanent.
Usually just sticking wires in holes and adding a bit of sideways pressure is enough to make good contact.
If you have those 0.025" gold pins (like on cable ends) they are a close fit to the hole and work great.
Do you have any resistors on hand? Maybe 100 ohms or so?
We can try to get you going before the UART arrives.

I do not have any resistors on hand, but I can pick some up in about an hour. I will do so.
Unfortunately I do not have any gold pins either, but i think I can find some 0.5mm cables, which are probably actually 0.025''.

I found some resistors including 100 ohms (but also 47, 1000 etc). I also found some cables that measure 3/128 inches, quite close to 0.025. I got my avometer and optician's screwdriver set
How should I proceed?
While waiting your reply, I will install the WinUSB driver from zadig, I am guessing I will need that.

Download from my sig imxlink.exe and nnglow3.img (Neo Noogie).
Get the attached ub3fb.img
Code:
C:\>imxlink.exe ub3fb.img nnglow3.img
Now connect from TP23 to your 100 ohm resistor to a ground on the board.
While doing that LONG press the power button.
As soon as Windows "bongs" or imxlink.exe reacts disconnect the resistor and sit back.
You might have to try it a few times. Windows might be slow the first time that it sees 15a2/0063 on USB.

Wow! Something happened. iMX Link is working and now saying waiting for Fastboot or ADB.
Before that, the red led for Bootloader was on briefly.
The screen is showing the nook image that it shows while starting to boot.

Mmm, do you have the drivers for fastboot already loaded?
Are you sure that it isn't in fastboot?
When you pull the USB cable and reinsert it does it go "bong"?
Check in devmgmt.msc with "Show all devices". Look for 18d1/d00d
Make sure that it has a driver.
It really should go Red - Yellow - Green.
If not, try doing it again.

I do not know what the drivers for fastboot are. How I check for them?
When I pull the cable it goes "bong", but not when I reinsert it, not upon further pulls.
I'll try again.

Well, if you never saw yellow, you don't have drivers or something.
Did you ever have fastboot working on your desktop?
It's the same "Google drivers" as for ADB.
If you see something with an exclamation mark in Device Manager (devmgmt.msc) that's it.
I know this stuff works because on my Glow3 I intentionally erased u-boot so that I could always reboot using imxlink.exe and get a direct choice of boot image.

No, I always used ADB on Linux before, and not on Windows, which it what I am using now.
It is trying to install i.mx6sl driver from windows update and failing.
I will look for this "Google drivers" for ADB

I installed the Google drivers. It now went to red, then yellow but not green.
It is now saying
Waiting for disconnect...
Waiting for ADB...

Quote the text please, I don't know what's going on.
What's the screen doing?
You probably need to install the drivers for ADB.
If your Linux system has ADB you should be able to plug it in now.

I am sorry, I am really a noob w/ Windows, I cannot even take a screenshot (I tried PrtSc button).
Here is the output:
C:\Users\ato\Downloads\renate>imxlink.exe ub3fb.img nnglow3.img
Waiting for bootloader or Fastboot or ADB...
Found iMX6SL
Load addr 87800400, DCD offset 002c, DCD size 0220
67 DCD ops processed
Write, addr 87800400, size 00039270
********************************************************************************
********************************************************************************
*********************************************************************
Jumping to 87800400
Device disconnected correctly
Waiting for Fastboot or ADB...
product i.mx6sl NTX Smart Device
version 0.5
Sending boot image, 6043648 bytes... ok
Waiting for disconnect...
Waiting for ADB...
I installed Google ADB drivers.
When I try to run ADB from Windows, for "adb devices -l" I get an empty list.
Should reboot into linux and try?

Brand new UIS8762 qled 6gb 128gb 8core never started, and no support from Witson

Hi,
I've been googling and searching here and on Youtube for three weeks and I can't find any help.
My brand new head unit doesn't start, and has never started. The touch buttons don't work so after hours and days seaching the web I found out that I could at least get it to the boot logo by pushing a pin into the reset hole for 10 seconds, another short push and then a third push for 5 seconds, but that's about it.
Sometimes when I do that I get to a "no command" screen and then nothing.
When I contacted Witson who sold it to me, they sent me a file to install, but the problem is that the update stops (around 80-90%) and reboots before it's finished. After 3 restarts/reboots of the update it just goes black again. After sending several photos and videos to Witson of what's going on I asked for a refund and then they just stopped answering me. Nice, huh. (And I've followed their instructions to push the reset button when the boot logo appears - let it reboot - push the reset button when the boot logo appears - let it reboot - push the reset button when the boot logo appears.
So now I'm stuck here with a head unit that's never been used. Could there be a chance that they sent me the wrong update perhaps? I'm not used to head units but I've tried many things to solve it. I can't get into recovery mode, god knows I've tried for days with maaaany different tricks picked up on the web. I've even opened it up and tried to reset by short circuiting the special poles people say you should do. Nothing helps. I've tried to figure out what other brand sells these to find another file to install, and so far I've tried at least 10 different files, both USB contacts and three different USB FAT32 sticks, but no difference. Boot loop is the only thing this head unit is capable of.
If anyony could kindly assist me it would be extremely appreciated.
I'll try to post some pictures for you. I don't even know the proper name of this thing.
It's supposed to be a Witson DHG (W2-DHX1001) with Android 12, , but it seems to have many names. As I said, it's never started up properly and I've never played with a device like this before.
Many thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

This looks like a UIS 7862 FYT unit. DO the files they sent include a lsec6315update and a 6315_1.zip?
Normally, when the update fails you will get a message in red about the failure and the unit will reboot after 5 minutes or so, yours just reboots?
Anyway, if you got the unit from Aliexpress the safest thing would be to open a dispute with them.

Hi,
Thanks for your reply.
Thanks, I'm not by the computer right now but they sent me a 2,1gb zip-file with a zipped 6315 file name in it. (Does that make sense? ) Not sure if both those files was in that package, but one of them was.
I can't recall the exact name right now. But they just wrote that I should unzip the big file as is onto a USB stick and do as described earlier.
There was no red alert text when I used the file. Only reboot after reboot at around midnight 80% install. (One of the other files I downloaded later from the web showed that red failure text)
I did open a dispute and was reimbursed $160 of the $400 I spent in total. So here I am $240 down and a piece of glass.
Would be fantastic if someone has a file that fits this head unit or someone knows if there's a possibility that the main board or something else is broken.
Cheers

You definitely have a FYT unit.
There is plenty of info on this unit in this thread.

m00n61 said:
You definitely have a FYT unit.
There is plenty of info on this unit in this thread.
Click to expand...
Click to collapse
Thanks, I'll check it out. Much appreciated.

m00n61 said:
You definitely have a FYT unit.
There is plenty of info on this unit in this thread.
Click to expand...
Click to collapse
Ah, yes I recognize that thread. Been reading a lot in it but I couldn't make anything out of it in relation to my unit. I guess I have to give it another go and see if I can make anything out of it now when I know it's a FYT unit, thanks.

Short version:
Get a FAT32-formatted USB stick, good quality. Bad USBs may cause setup to abort.
Copy the firmware files (minimum: config.txt, 6315_1.zip, lsec6315update and updatecfg.txt) to the stick.
updatecfg.txt should contain
test
twipe_all
config.txt should look like
#test
#ro.fyt.launcher = com.android.launcher04
sys.fyt.bluetooth_type=1
persist.fyt.zh_frontview_enable=false
sys.fyt.ec_version=6
ro.fyt.splitscreen=0
persist.syu.camera360 = 1
# 0不带360 1带360
persist.lsec.pip_rect_clear=true
ro.sf.swrotation=90
persist.lsec.enable_a2dp=true
ro.lsec.btname=Bluetooth 2
persist.lsec.iphone_usb=true
carmark#0
persist.sys.navi.carmarkset=0
launcher name may be different, depends on firmware version.
Make sure 6315_1.zip and lsec6315 update are both dated either before or after July 2, 2022. You cannot mix on from before with another one from after.
You can get a suitable firmware from here. Look for the 7862/9" 10" line ( or 7862-9"-10"-360: if you have 360 view)
Insert the USB and start the unit. You may have to reset up to 5 times until it boots from the USB stick.
If you get an error message, post it here.
If you don't and it still aborts at 80% chances are you have a HW failure

Amazing, thank you for the detailed explanation. Well needed for a noob in this area.
I'll try it out when I get back on the computer later tonight. I guess the night sleep is canceled.
Thanks again, very impressive.
I'll get back to you as soon as I have any results.

I think that this file update he got is not for his device, it does not recognize hardware and stops in a middle of process of install.
Install other updates suitable for your model and year and see if error repeats again.

Anton TNT said:
I think that this file update he got is not for his device, it does not recognize hardware and stops in a middle of process of install.
Install other updates suitable for your model and year and see if error repeats again.
Click to expand...
Click to collapse
Hi Anton,
Thanks. It's what I suspected too. But it seems all the different files I've tried has behaved the same way so far. I'm trying this file that was recommended by @m00n61 here above. So far to reboots and same thing. Stops and reboots at the exact same spot. Switching USB and USB stick in a few minutes for continued trying.

m00n61 said:
Short version:
Get a FAT32-formatted USB stick, good quality. Bad USBs may cause setup to abort.
Copy the firmware files (minimum: config.txt, 6315_1.zip, lsec6315update and updatecfg.txt) to the stick.
updatecfg.txt should contain
test
twipe_all
config.txt should look like
#test
#ro.fyt.launcher = com.android.launcher04
sys.fyt.bluetooth_type=1
persist.fyt.zh_frontview_enable=false
sys.fyt.ec_version=6
ro.fyt.splitscreen=0
persist.syu.camera360 = 1
# 0不带360 1带360
persist.lsec.pip_rect_clear=true
ro.sf.swrotation=90
persist.lsec.enable_a2dp=true
ro.lsec.btname=Bluetooth 2
persist.lsec.iphone_usb=true
carmark#0
persist.sys.navi.carmarkset=0
launcher name may be different, depends on firmware version.
Make sure 6315_1.zip and lsec6315 update are both dated either before or after July 2, 2022. You cannot mix on from before with another one from after.
You can get a suitable firmware from here. Look for the 7862/9" 10" line ( or 7862-9"-10"-360: if you have 360 view)
Insert the USB and start the unit. You may have to reset up to 5 times until it boots from the USB stick.
If you get an error message, post it here.
If you don't and it still aborts at 80% chances are you have a HW failure
Click to expand...
Click to collapse
Yes, unfortunately it looks like it's the same thing with the recommended files (7862/9). It reboots at the same point at the install and no error messages. I'm trying out the other USB input now and will then try yet another USB stick.
Thanks again.

So I tried to install both the whole file and only the necessary files @m00n61 mentioned earlier. And I tried this on both of the USB inputs and with three different USB sticks. All with the same outcome. the install stops exactly where I showed in the picture in the first post, and then reboots, restarts the install and it goes on like this three times until it just goes black.
Is there any other way that may help? I've read about connecting the head unit to a computer with a USBa-USBa cable and some sort of sofware.
Thanks for your input!

Peter studio tech said:
Is there any other way that may help? I've read about connecting the head unit to a computer with a USBa-USBa cable and some sort of sofware.
Click to expand...
Click to collapse
Yes, including flashing of ROM but it must be done with guidance and by a pro...
But it is last resort, let's try something else first.
Format SD card (if device has slot for it) in FAT 32 not exFAT with default allocation settings - not USB drive but SD card !
- if device has no SD card slot use any SD card reader if you have any and insert it then into USB slot with update files on it
- before unit boot try tapping with one finger on the middle of screen till see message DETECTED
- let the update begin
- if same error appears - press RESET button rapidly each time units starts for 5 times
- as soon as unit starts again tap the screen with all five fingers till recovery mode begins (message erasing will apear and begin to erase system files)
- when boots again into Android download a application named FILE MANAGER from Google Playstore
- go to app
- on the left side of app there is a menu - choose ROOT folder it looks like this "/.."
- there are system files that are hidden from users
- if unit is rooted you can go inside each of this folder
- if not rooted, delete the CACHE folder
- restart unit and try update again with SD card or USB drive
Fingers crossed !

Anton TNT said:
Yes, including flashing of ROM but it must be done with guidance and by a pro...
But it is last resort, let's try something else first.
Format SD card (if device has slot for it) in FAT 32 not exFAT with default allocation settings - not USB drive but SD card !
- if device has no SD card slot use any SD card reader if you have any and insert it then into USB slot with update files on it
- before unit boot try tapping with one finger on the middle of screen till see message DETECTED
- let the update begin
- if same error appears - press RESET button rapidly each time units starts for 5 times
- as soon as unit starts again tap the screen with all five fingers till recovery mode begins (message erasing will apear and begin to erase system files)
- when boots again into Android download a application named FILE MANAGER from Google Playstore
- go to app
- on the left side of app there is a menu - choose ROOT folder it looks like this "/.."
- there are system files that are hidden from users
- if unit is rooted you can go inside each of this folder
- if not rooted, delete the CACHE folder
- restart unit and try update again with SD card or USB drive
Fingers crossed !
Click to expand...
Click to collapse

Thank you so much! I'll try it out tonight! (it's morning here)
The unit has no card slot so I'll give it a go with a card reader.
I've read about the five finger tap (which didn't work on this one) but never the one finger tap. Looking forward to try out your suggestions!
Thanks!

Peter studio tech said:
Thank you so much! I'll try it out tonight! (it's morning here)
The unit has no card slot so I'll give it a go with a card reader.
I've read about the five finger tap (which didn't work on this one) but never the one finger tap. Looking forward to try out your suggestions!
Thanks!
Click to expand...
Click to collapse
Five tap is not working on every device, every device has different way.
You must find your way to get into recovery mode and get system to clear cache and junk files
Also, maybe you have residual update files left on main folders like factorysettings.bin log files mem.ini etc. delete those too !
BTW you can go into recovery mode if you can access Android and go from infotainment menu or from factory settings (accessed with PIN code)

Yes thank you, I've yet to figure out how to get into recovery mode. And I've never been able to start the device, so recovery mode seems like prio one so far, if I can't get any of the files to work via SD card etc.
Thanks!