Database Info

[26 Dec.] ► German WM6.5 ◄ 28004 by ChrBeck (CHome)

Updated: 26th Decmeber​
Os is 28004.
{
"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"
}
More screenshots in post 2.
Download: http://rapidshare.com/files/326251426/Kaiser_28004_V0.9_GER_ChrBeck.zip
Credits:
-TPC and Joshkoss for the good Platform Rebuilder Kitchen
-CRACING from Wizard forum for some infos and cool files.
-Bepe for all his tools.
-All I missed. (Fell free to tell me that I missed you)
Changelog:
V0.9:
-WLAN button fixed
-Touchscreen fixed
-Taskmanager fixed
Donations:
-adlerweb 10$
-slurm 3€
-anonymous 7$
Feel free to donate if you like my work and want to help me keep on working. (Just klick here)
Thanks to all who donated!
Bugs:
- No bugs found.

Reserved 2.

Reserved 3.

Thanks Beck, can you up to another server
it is difficult to downlaod from rapid

Yea I think I can upload it somewhere else tomorow too.

Hey,
which Radio-rom and hard-spl do you use with this rom?
m4c

SPL I use is 3.56.Hard and Radio is 1.65.16.25.
Hope that helps.

Hello,
it's me again. I again tried to flash your new ROM, but I have again the same problem as in the previous version.
Again I have 148 MB available RAM and the same problems with the camera.
How can I limit the RAM to 101 MB? Is there a specific program or patch, what should I install?
Thanks for the help would be great if I could use your ROM (it is not so overloaded ...)
Greats
JamDe
Hallo,
ich bins wieder. Habe wieder versucht Dein neues ROM zu flashen, aber ich habe wieder dasselbe Problem wie in der vorherigen Version.
Wieder habe ich 148 MB verfügbaren RAM und die gleichen Probleme mit der Kamera.
Wie kann ich den RAM auf 101 MB beschränken? Gibt es ein spezielles Programm oder Patch, welchen ich installieren muss?
Danke für die Hilfe, wäre toll wenn ich Dein ROM nutzen könnte (ist nicht so überladen...)
Gruss
JamDe

OK. In Speicher the Value called Programmspeicher (Gesammt) should be 101.38 MB . (It is for me). If it is ways differnt then you have a problem I can't reproduce. by the way the cam was bad for me one time too. I added some files and now it works fine here.

OK,frag nicht wieso, aber der Gesamt-Programmspeicher (nicht der freie) beträgt bei mir nun auch 101.38 MB (38.36 belegt 63.02 frei) - habe nochmal geflasht.
Die Navisoftware funktioniert nun auch komplett und ohne Fehler (nun zum 10. Mal).
Einzig die Kamera zeigt noch die gleichen Probleme. Das Speichern der Fotos ist nicht möglich: Nach über 1.5 MInuten (Windows Sanduhr) erscheint -bei abgeschalteter Vorschau- die Fehlermeldung "Foto kann nicht aufgenommen werden. Interner Fehler".
Hier ist ein Foto davon, hoffentlich siehst Du was ich meine:
Gibt es irgendwo Konfigurationsdateien, wo man festlegen kann, wo die Kamera die Photos genau abspeichert (nicht nur Speicherkarte/Hauptspeicher, sondern den genauen Pfad) wo vielleicht ein Fehler drin ist?
Gruss
JamDe
Und das beste kommt jetzt:
Wenn ich meine Navigationssoftware laufen habe und dann die Kamera gleichzeitig parallel starte funktioniert die Kamera ebenfalls...
Die Kamera funktioniert bei mir nur, wenn wenig Speicher verfügbar ist?
OK, do not ask why, but the total program memory (not free) is with me now 101.38 MB (38.36 not available available) 63.02 - had flashed again.
The Navisoftware now works completely and without errors (now) for the 10th time.
Only the camera still shows the same problems. The saving of the photos can not: appear after about 1.5 minutes (Windows hourglass) when turned off the preview, the error message "photo can not be recorded. Internal error".
Here is a photo, I hope you see what I mean:
Are there configuration files somewhere where you can specify where the camera saves the photos closely (not just memory card / memory, but the exact path), where perhaps an error in it?
Greats
JamDe
And the best part comes next:
If I run my navigation software and then run parallel to the camera while the camera also works ...
The camera works for me only if enough memory is available?

Ok. I got 48MB used from the beginning on. I know the Camera problem as I saw it one time too. But I added some packages and the problem left. Have you flashed the original ROM before flashing mine and have you done a hardreset after flashing mine? If not try that maybe it helps. Otherwise I'll tell you how to go on.

Hallo,
ich war gestern ausser Haus, deshalb melde ich mich erste jetzt.
OK. Ich habe nun folgende Schritte gemacht:
- Original T-Mobile ROM (aktuellstes von der Webseite) geflasht.
- Hard-Reset nach flashen vom Original-ROM.
- ChrBeck (27.Nov) geflasht
- Hard-Reset nach flashen
(Hard Reset jeweils die linke und rechte Taste drücken beim reset mit Stift.)
Reproduzierbar das selbe Problem wie auf dem Bild. Kamera funktioniert nicht sofort. Kamera funktioniert nur, wenn ich die Navisoftware starte, im Hintergrund lasse, und dann erst die Kamera parallel starte.
Sind beide Programme einmal zusammen gelaufen, kann ich auch die Navi-Software wieder beenden. Ab dann läuft die Kamera auch ohne Navisoftware. Warscheinlich bleibt die Kamera-Software im Speicher?
Was kann ich noch tun?
Vielen Dank nochmal für die Mühe. Toller Support.
JamDe
Hello,
I was yesterday outside the home, so I sign my first now.
Ok. I have now taken the following steps:
- Original T-Mobile ROM (latest from the website) flashed.
- Hard reset after flash the original ROM.
- ChrBeck (27.Nov) flashed
- Hard reset after flash
(Hard reset both the left and right button reset with the stylus.)
Reproduced the same problem as in the picture. Camera does not immediately work. Camera only works when I start the Navisoftware, leaving her in the background, and then the camera run in parallel.
Once both programs are running together, I can also stop the Navi software again. From then on, the camera will run without Navisoftware. Probably remains the camera software in the memory?
What can I do?
Thanks once again for the effort. Great support.
JamDe

wrong place

Wrong place???

OK. So then it is very strange. Have you tried to use camera before you installed the nav software? Has it worked then?

Ja habe ich immer als erstes probiert.
Wenn ich die Kamera starte ohne vorher das Navi und die Kamera gestartet zu haben funktioniert die Kamera nicht.
Habe ich beides zusammen einmal benutzt funktioniert die Kamera einwandfrei.
Gibt es den HTC-Taskmanager als .cab Datei? (Oder ist der irgendwie anders zu installieren?) Dann kann ich mal die Speicherauslastung der Kamera sehen und prüfen ob die Kamera nach dem Schliessen noch im Speicher ist wenn das Navi aus ist.
Yes, I have always tried first.
When I start the camera without having the Navi and the camera started at the camera does not work.
I have both together once used the camera properly.
Is it the HTC Task Manager as a. Cab file? (Or install any of the other way?) Then I can see times the memory capacity of the camera and check whether the camera is still in memory after closing when the Navi is off.

Yea there is a cab. Just search in the forum. But what I wanted to say is: Have you tried it before INSTALLING the navigation software?
Hast du die Cam mal vor der Installation der Software getestet?

Can't download
Hello CBeck,
downloading is not possible at the moment, rapidshare only allows premium users to download. Can you (or anybody else) provide a mirror?
So far no 6.5 ROM did the job for me. Because of the german keyboard I find it very difficult to use WWE ROMs, so I'm very interested in trying your ROM!
Regards
Herb

Now you should be able to downlaod it. Otherwise I'll mirror it later today.

great news regarding locked boot loaders

So people do listen:
http://htcpedia.com/news/your-voices-have-been-heard-htc-will-no-longer-lock-bootloaders.html
http://www.facebook.com/HTC/posts/10150307320018084
Although the questions are:
1) when is the next phone due to come out so we can see of they're true to their word ?
2) and more importantly for us, will they htc ever unlock the currently locked devices (DS&IS etc) using OTA updates?
I think that the locking of the sensation, their flagship device and one that many devs intend to buy was the last straw for the community leading to such a large backlash and probably was the tipping point for htc as locking may have affected sales and bottom line.
EDIT: didn't realize that the other post for the petition on boot loaders in the DS forum contained this news also.
Sent from my HTC Desire S using XDA App

Nice, but is information about ota updates confirmed somewhere?
Sent from my HTC Desire S using Tapatalk

Numline1 said:
Nice, but is information about ota updates confirmed somewhere?
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
No that is the point, nothing has be been said about ota updates as yet, so we will have to wait for another press release from htc or confirmation from elsewhere
Sent from my HTC Desire S using XDA App

In the midst of the thanks they posted this.
We are excited to share the news with everyone! Thank you so much. Please note that more specific details will be shared at a later date.
Click to expand...
Click to collapse

I'm not gonna lie, I'm not getting my hopes up until more details arrive. I would like to know if they mean just new phones though, because I would like to be able to root my Desire S without an issue in the future.

It's in the news that Xperia Android phone that had been unlocked will never going to get an official fw update. Wonder, what would be the situation with HTC?

http://www.facebook.com/HTC/posts/10150307320018084
"There has been overwhelmingly customer feedback that people want access to open bootloaders on HTC phones. I want you to know that we've listened. Today, I'm confirming we will no longer be locking the bootloaders on our devices. Thanks for your passion, support and patience," Peter Chou, CEO of HTC
Click to expand...
Click to collapse

titus1 said:
It's in the news that Xperia Android phone that had been unlocked will never going to get an official fw update. Wonder, what would be the situation with HTC?
Click to expand...
Click to collapse
Pretty sure its the same with HTC .. i hope the test signed RUU for DS never reach public eyes for same reason now.
Sent from my HTC Desire S using XDA Premium App

Dont see what the problem is if you dont get official updates once bootloader unlocked. The whole point is to install custom ROM so why would you need original software?
Sent from my Desire HD using XDA Premium App

I would like to unlock the correct way true HTC . Not some homemade workaround .. witch is not made yet..Hope you understand.
Sent from my HTC Desire S using XDA Premium App

ricey1986 said:
Dont see what the problem is if you dont get official updates once bootloader unlocked. The whole point is to install custom ROM so why would you need original software?
Click to expand...
Click to collapse
Not everybody wants a custom rom, I am happy with small modifications on the original rom as I like Sense very much. Which is one cause to buy a HTC in the first place.

Glibberman said:
Not everybody wants a custom rom, I am happy with small modifications on the original rom as I like Sense very much. Which is one cause to buy a HTC in the first place.
Click to expand...
Click to collapse
Very true. After flashing dif'rent roms onto my Old Desire, I've always comes back to stock (rooted) Sense. Apps that needed Superuser is another thing.

Thank you for your email regarding your HTC Desire S.
You currently have the following question: Boot Loader Lock
Unfortunately you can not remove the boot loader lock.
HTC have now decided that all new devices do not lock should have more.
It might be possible in the future.
From Here to HTC.com page, wait for new news on this topic.
For more useful information, we invite you to visit our support website. The link is listed below.
We hope we have helped you with that answer. If you have any questions, please do not hesitate to contact us again.
If this answer has answered your question and you have no other more, we ask your ticket via the link below to close.
After you have closed the ticket you receive an invitation to participate in a customer survey to tell us whether you are satisfied with our service or we can do to improve our service to you.
Sincerely,
John
HTC
Vielen Dank für Ihre E-Mail bezüglich Ihres HTC Desire S.
Sie haben gegenwärtig folgende Frage: Bootloader Lock
Leider können Sie der bootloader lock nicht entfernen.
HTC haben sich Jetzt entschieden, das alle neue Geräte kein lock mehr haben sollen.
Es könnte in Zukunft möglich sein.
Sie sollten noch auf die HTC.com seite, auf neue Nachrichten zu diese thema warten.
Für weitere nützliche Informationen laden wir Sie ein, unsere Support-Webseite zu besuchen. Den Link finden Sie nachfolgend.
Wir hoffen, Ihnen mit dieser Antwort geholfen zu haben. Sollten Sie noch weitere Fragen haben, zögern Sie bitte nicht, uns wieder zu kontaktieren.
Wenn diese Antwort Ihr Frage beantwortet hat und Sie keine weiteren mehr haben, dann bitten wir Sie das Ticket über den nachfolgenden Link zu schliessen.
Nachdem Sie das Ticket geschlossen haben erhalten Sie eine Einladung an einer Kundenumfrage teilzunehmen, um uns mitzuteilen, ob Sie mit unserem Service zufrieden waren bzw. was wir tun können, um unseren Service für Sie zu verbessern.
Mit freundlichen Grüßen,
John
HTC

does that means that desire S will not have bootloader lock removed ????????????

No, it means it's HTC support and they know what we know - nothing. There is no part where guy from support said there won't be unlocked bl for ds. Just have patience, it won't do any good to write to htc support.
Sent from my HTC Desire S using Tapatalk

We can found HTC answer here:
{
"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"
}

I am thinking of buying a htc desire s tomorrow, and this only makes me more excited, i am able to buy almost every htc phone, but i think the desire s have the perfect size and possessor, not need more..
Lets hope they release a way to unlock the phone so we can have custom roms!

It answers only part of the question - new devices. We are trying to figure out, if htc plans to unlock current devices. You should at least read context of this discussion.
Sent from my HTC Desire S using Tapatalk

madmax241178 said:
Thank you for your email regarding your HTC Desire S.
You currently have the following question: Boot Loader Lock
Unfortunately you can not remove the boot loader lock.
HTC have now decided that all new devices do not lock should have more.
It might be possible in the future.
From Here to HTC.com page, wait for new news on this topic.
For more useful information, we invite you to visit our support website. The link is listed below.
HTC
Click to expand...
Click to collapse
i wrote an email yesterday asking about my desire s bootloader and got a very different response
" Thank you for contacting HTC regarding your mobile phone HTC Desire S.
I understand that you wish to know if your phone will get an update to unlock the Bootloader.
We’re pleased to announce that we have heard everyone’s comments and constructive suggestions and have decided to go forward with this initiative. Currently we don’t have a schedule yet, but stay tuned; we will let you know via through our official website and official social media outlets.
Regarding which phones will be unlocked, currently we don’t have information but keep an eye on our official website and official social media outlets for announcements about which phones will be bootloader unlocked."
you notice it specificaly mentions "update to unlock the bootloader"
so to me thats pretty clear they understand im not just talking about phones still to come, but phones already out

"Currently we don’t have a schedule yet"
Damn, it can take months
But reading the response we can we 100% sure they are talking about current locked devices
Also, seems they were thinking of keeping locked part of them by reading this line
"about which phones will be bootloader unlocked"

[A700][ROM] CoolOne700 - V1

Hi people,
I think I'm now ready to present my first ROM!
{
"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"
}
Description:
CoolOne700 - V1
Android 4.1.1 (Jelly Bean) - Based on AV051RV16RC01 (last official GERMAN version)
Aroma Installer
Multi-Region support - Choose the country setting in the aroma (UK, U.S., DE, ES & FR)
full ROOT
Insecure boot.img
BusyBox (latest version)
Zipaligned
Fully de-odexed
init.d scripts (BusyBox run-parts) support
3 Different Installation Options:
Full Rom Install
Small Rom Install
Custom Rom Install
Based of A051RV16RC01_EMEA_DE
4way reboot mod installed
Firmware update included
more tweaks for system performance and battery life
some apps moved to /data (easier uninstall)
You have the choice to Install three different Rom's.
Full Rom
* all Apps installed
* all mod's installed
* you can select additional Apps
Small Rom
* most apps are installed (below the list of Apps NOT installed)
* all mod's installed
* you can select additional Apps
Custom Rom
* you can select which apps you won´t Install
* you can select which mod's to Install
* you can select additional Apps
Removed Apps in small Rom:
***********************
Acer Apps:
------------------
Acer Cloud
Acer Euro Sport
Acer Files
Acer Print
Acer Shell
McAfee
Other apps:
------------------
7digital
Acetrax Movies
Amazon Kindle
Aupeo
Barcode Scanner
Books
ClearFi Apps
EquiView
Evernote
Google Calendar
Polaris Office
Stock Gallery
TegraZone
Youtube
Zinio
Games:
------------------
Monopoly
Real Racing 2
Solitaire
Widgets:
------------------
Digital Clock Widget
Weather Widget
Needed:
Jelly Bean firmware / bootloader
Acer Iconia Tab A700 with "unlocked bootloader"
ClockworkMod Recovery - 6.0.1.5
Recommendation:
FULLWIPE
because the Rom is DeOdexed and to avoid issues it´s recommend to do a fullwipe and a clean install (as always on CR's)
Flash Instructions:
Download the ROM and save to the SD card (or internal)
Boot into CWM recovery (via adb or via keyboard shortcut)
In CWM select "install zip from sdcard"
select "choose zip from sdcard" and choose the Rom : CoolOne700-V1.zip
If you are still on ICS - select in Aroma to update the firmware
Reboot after flashing the Tab
Download:
CoolOne700-V1 (md5 : a458d081fd2532ab811838df2b256cee)
Polaris-Fix (forgot to put in Rom sorry)
Credits to:
Vorbeth for allow using Rom Parts and help
Chrack for support
Team Union for support
Moscow Desire for help patching the kernel
pawitp for the CWM used to flash
mike1986 for Tweaks & Aroma scripts
all others i forgot

Thanks for u Work.....i will try it, can u post some Screenshots please.
Greetz From Bavaria
Gesendet von meinem A700 mit Tapatalk 2

Thanks for the ROM! Hopely more ROMs came out for the A700. I will try your ROM now...
Webitu

Its stock look !
Gesendet von meinem A700 mit Tapatalk 2

Cant try it, cant Boot in recovery, no PC for Now...
Gesendet von meinem A700 mit Tapatalk 2

What?
..................
Sorry für manche Schreibfehler, aber mit Slide It ist zwar schnell aber nit schön geschrieben!
Gesendet vom Note OTA
...................

meier2009 said:
What?
..................
Sorry für manche Schreibfehler, aber mit Slide It ist zwar schnell aber nit schön geschrieben!
Gesendet vom Note OTA
...................
Click to expand...
Click to collapse
My english is so...
I mean i cant Boot in to cwm with key Combi Boot My acer in system recovery and not in cwm. Iam confused
Gesendet von meinem A700 mit Tapatalk 2

Then You have to install/flash first cwm in fast boot mode
..................
Sorry für manche Schreibfehler, aber mit Slide It ist zwar schnell aber nit schön geschrieben!
Gesendet vom Note OTA
...................

meier2009 said:
Then You have to install/flash first cwm in fast boot mode
..................
Sorry für manche Schreibfehler, aber mit Slide It ist zwar schnell aber nit schön geschrieben!
Gesendet vom Note OTA
...................
Click to expand...
Click to collapse
Hab ich gemacht. I dont have a Computer here in The Hotel....so i cant flash again
Gesendet von meinem A700 mit Tapatalk 2

http://forum.xda-developers.com/showthread.php?t=1984566
look inside and read my post after that.
i think that was your problem, you have to use trick17 to install cwm fix
or look here: http://www.android-hilfe.de/root-cu...-installieren-rooten-ota-updates-reseten.html
good luck

meier2009 said:
http://forum.xda-developers.com/showthread.php?t=1984566
look inside and read my post after that.
i think that was your problem, you have to use trick17 to install cwm fix
or look here: http://www.android-hilfe.de/root-cu...-installieren-rooten-ota-updates-reseten.html
good luck
Click to expand...
Click to collapse
THX
Yeah i used ur instructions in android-hilfe, The temporäre. OK then i must wait to tomorrow evening when i come home...
Need a PC for ADB fastboot....
Gesendet von meinem A700 mit Tapatalk 2

Dangit! Time to do a backup and check your ROM out so I can add it to the How-To Guide. I know it'll be essentially the same steps as the others, but I wanna be thorough .

s.supervisor said:
Hab ich gemacht. I dont have a Computer here in The Hotel....so i cant flash again
Gesendet von meinem A700 mit Tapatalk 2
Click to expand...
Click to collapse
Das ist lustig, wir reden alle Englisch zusammen obwohl wir aus Deutschland kommen. :laugh:
Damit niemand meckert:
That's funny, we all talk English together even we come from Germany. :laugh:
Your ROM is awesome! Hopely you can make more GPU Tweaks that the most of the Games runs over 15 fps.
Webitu

Webitu said:
Das ist lustig, wir reden alle Englisch zusammen obwohl wir aus Deutschland kommen. :laugh:
Damit niemand meckert:
That's funny, we all talk English together even we come from Germany. :laugh:
Your ROM is awesome! Hopely you can make more GPU Tweaks that the most of the Games runs over 15 fps.
Webitu
Click to expand...
Click to collapse
LoL

Thats why my home forum is android Hilfe
..................
Sorry für manche Schreibfehler, aber mit Slide It ist zwar schnell aber nit schön geschrieben!
Gesendet vom Note OTA
...................

hi there
someone told me that it seems that i forgot Polaris to install
here you are

Hey Guys,
Last week I got the Acer Iconia A700.
Since then, i'm running on the ROM CoolOne700 V1.
So far, no problems, everything's fine.
Great Rom for great German Users
Thank You!
Greetz, SoLdieR9312

Hey Guys!
A friend of mine almost bricked his device by flashing this ROM.
His device was powered by CM10 with the stock unlocked bootloader and ICS CWM 6.0.2.3 Touch.
After flashing rebooting the only thing on the display immediately after showing the bootlogo was "Boot image verified failed". So appearently the ROM relocked the bootloader and destroyed CWM.
He was able to get into fastboot and unlock the bootloader again and therefore was able to boot into the ROM but the touchscreen calibration is messed up. He mentioned that it was already during the AROMA installation which lead us to the assumption that CWM was not compatible.
He will try to reflash everything with JB CWM in version 6.0.1.4.
Link to his thread: http://forum.xda-developers.com/showthread.php?p=36174362

the.cybot said:
Hey Guys!
A friend of mine almost bricked his device by flashing this ROM.
His device was powered by CM10 with the stock unlocked bootloader and ICS CWM 6.0.2.3 Touch.
After flashing rebooting the only thing on the display immediately after showing the bootlogo was "Boot image verified failed". So appearently the ROM relocked the bootloader and destroyed CWM.
He was able to get into fastboot and unlock the bootloader again and therefore was able to boot into the ROM but the touchscreen calibration is messed up. He mentioned that it was already during the AROMA installation which lead us to the assumption that CWM was not compatible.
He will try to reflash everything with JB CWM in version 6.0.1.4.
Link to his thread: http://forum.xda-developers.com/showthread.php?p=36174362
Click to expand...
Click to collapse
Yes, in order to install a JB based ROM, you need the JB compatible CWM. Where did this 6.0.2.3 come from? Use 6.0.1.5 from pawitp. I've used it and swapped/flashed ROMs at least ten times. Never encountered that issue (or any issue). As a matter of fact, I would just run Vorbeth's EasyRoot as it does all the grunt work for you. I've used it twice and it worked flawlessly.

the.cybot said:
Hey Guys!
A friend of mine almost bricked his device by flashing this ROM.
His device was powered by CM10 with the stock unlocked bootloader and ICS CWM 6.0.2.3 Touch.
After flashing rebooting the only thing on the display immediately after showing the bootlogo was "Boot image verified failed". So appearently the ROM relocked the bootloader and destroyed CWM.
He was able to get into fastboot and unlock the bootloader again and therefore was able to boot into the ROM but the touchscreen calibration is messed up. He mentioned that it was already during the AROMA installation which lead us to the assumption that CWM was not compatible.
He will try to reflash everything with JB CWM in version 6.0.1.4.
Link to his thread: http://forum.xda-developers.com/showthread.php?p=36174362
Click to expand...
Click to collapse
And I will throw a concur with the previous.
If you are on ICS with an ICS bootloader, you don't want to be flashing JB roms. Don't work.
Also, you don't want to be flashing ANY Rom, until you look at the installer/Aroma scripts, and see just exactly what's going on. To do so, is ludicrous. In some cases, we include the recent JB bootloader in the install.
Your mate can easily fix this, by doing the Data "toggle" to delete the previous installed data, then flashing a stock rom afte flashing a stock recovery.
MD
MD

[Tutorial] FNF Ifive Mini 4s custom recovery and root

I finally managed to get a custom recovery and root working on my new FNF Ifive Mini 4s
I found This post, that claimed to be a recovery working for all tablets with a rk3288 chipset, so i decided to check it out. I would like to say thanks to Oma7144 for making the post on archtablet.com and another huge thanks to CrewRKTablets who made the tool and recoveries
The tool can in theory also install TWRP, which actually also worked for me, but the touch part does not work so it is pretty useless. This is why we are going to use ClockworkMod If anyone figures out how to get TWRP working, please do tell me
So first of all you need to download the recovery tool and a supersu of your choosing. Chainfire seemed to be the only thing working, so I am going to use that.
Chainfire SU
Recovery tool (New link thanks to k8500)
Now follow these steps:
Extract the recovery tool
Enter the RKDriverInstaller folder and run Driverinstall.exe as admin.
Press Uninstall driver
Press Install driver
Enter the RKAndroidTool folder and run AndroidTool.exe as admin.
Turn off your tablet
Enter Loader mode by connecting your tablet to the computer with the included usb cable and pressing Power-button and Vol-.
The AndroidTool should look like this now.
{
"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"
}
Check box number 12 as shown here.
Press run. Your tablet should reboot now.
Now transfer the Supersu zip file to the tablet.
Turn off the tablet and enter your new recovery by pressing the power button and Vol- button. This time without the powercable in.
Nagivate to install zip with the Vol- and Vol+. Select it by pressing the powerbutton once.
Select Choose zip from /Sdcard
Now find your zip file and select it.
Confirm the installation by selecting Yes.
Now reboot. If CWM asks if it should repair supersu select No.
You should now be rooted.
If you did something wrong and ended up in a bootloop I have written a tutorial on how to fix it. You can find it here.

Split_X: z said:
Hello, still running one with 1.1.1.C image.
I has definitely some bugs but I don't know if it would ever be recycled so I'm trying to integrate it into a DIY project.
Any backup of modded LineageOS 14.1 by Oma (aka post 61) ?
http://www.arctablet.com/blog/forum...-custom-root-firmware-20170609/page-5/#p60891
Click to expand...
Click to collapse
Hello,
I own a Fnf iFive mini 4 (not the 4s) and I'm also interested in the lineage 14.1 ROM build by OMA. Unfortunately, all links on arctablet are down...
Is there anyone who have a backup of the package referenced in the 1st post ?
Thank you in advance
PS : my old iFive is still running the custom Riley ROM under Kit Kat !

spiou said:
Hello,
I own a Fnf iFive mini 4 (not the 4s) and I'm also interested in the lineage 14.1 ROM build by OMA. Unfortunately, all links on arctablet are down...
Is there anyone who have a backup of the package referenced in the 1st post ?
Thank you in advance
PS : my old iFive is still running the custom Riley ROM under Kit Kat !
Click to expand...
Click to collapse
I have read the 18th pages of arc tablet forum. OMA did NOT manage to build a stable build. That's the reason we cannot find files. It is without support and non working. OMA did not own the device so it was rather difficult to debug specific issue, as most people don't know what is a log and how to send it.
- Touchscreen had a strange mapping (inverted input in some cases!)
- Wifi driver was not found as on some models running an unsupported version.
- battery voltage was not readable.
I will try to flash android 10 but I'm expecting to encounter similar issues. Main reason is beacause it is a cheap tablets, some shortcuts have been taken.
Nevertheless, Android 6.0 with root is very well supported thanks to Xposed (not tested on this device yet).
Also there are dev boards with similar specs (no display though) so we can find some kernels on Github...

Split_X: z said:
I have read the 18th pages of arc tablet forum. OMA did NOT manage to build a stable build. That's the reason we cannot find files. It is without support and non working. OMA did not own the device so it was rather difficult to debug specific issue, as most people don't know what is a log and how to send it.
- Touchscreen had a strange mapping (inverted input in some cases!)
- Wifi driver was not found as on some models running an unsupported version.
- battery voltage was not readable.
I will try to flash android 10 but I'm expecting to encounter similar issues. Main reason is beacause it is a cheap tablets, some shortcuts have been taken.
Nevertheless, Android 6.0 with root is very well supported thanks to Xposed (not tested on this device yet).
Also there are dev boards with similar specs (no display though) so we can find some kernels on Github...
Click to expand...
Click to collapse
Thanks for your response.
Which model do you own ? IFive mini 4 or 4s ?
Have you some links about Android 6.0 ?

spiou said:
Thanks for your response.
Which model do you own ? IFive mini 4 or 4s ?
Have you some links about Android 6.0 ?
Click to expand...
Click to collapse
4s on 1.1.1C
There's a link for some stock roms
- Magisk ZIP install doesn't seem to work.
- So we only have limited CWM (no SDext/ No install) -> that would require to
- SuperSU works fine.
- Only way to flash is to use the Custom crewRKT windows tool. Using .img format
- some work required to build a custom kernel, without proper drivers that might be difficult

Worked well. Thanks !

feydakin said:
Worked well. Thanks !
Click to expand...
Click to collapse
I am glad it did

I'am waiting for mine but thanks in advance I will try and let you know after.

hello, the RKDriverInstaller works on windows 10??

RVA84 said:
hello, the RKDriverInstaller works on windows 10??
Click to expand...
Click to collapse
Yes it does.

UnknownDK said:
Yes it does.
Click to expand...
Click to collapse
I am trying to upgrade to version 1.0.6 and in factorytool, when I connect the tablet to the pc I get "wait for loader fail" and not updated. What happen??

RVA84 said:
I am trying to upgrade to version 1.0.6 and in factorytool, when I connect the tablet to the pc I get "wait for loader fail" and not updated. What happen??
Click to expand...
Click to collapse
You did not enter the loader mode correctly. You have to plug your device in first, and then pres the power butten and vol- at the same time.

UnknownDK said:
You did not enter the loader mode correctly. You have to plug your device in first, and then pres the power butten and vol- at the same time.
Click to expand...
Click to collapse
I have done and now it puts "lowerformat device fail"
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
I have repeated the process and it seems that its being updated

RVA84 said:
I have done and now it puts "lowerformat device fail"
Click to expand...
Click to collapse
Did you remember to first uninstall the driver and then install it?

RVA84 said:
I have done and now it puts "lowerformat device fail"
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
I have repeated the process and it seems that its being updated
Click to expand...
Click to collapse
Okay, I'm glad it works.

Tablet updated and root. Thank you very much!!!

RVA84 said:
Tablet updated and root. Thank you very much!!!
Click to expand...
Click to collapse
Happy to help

Hoffe es ist ok das ich auf Deutsch schreibe.
Die Anleitung ist gut, gut verständlich (Vielen Dank dafür !), und cwm und root funktionieren mit dem FNF Ifive Mini 4S problemlos, genau wie das aufspielen der aktuelle Rom 1.0.6.
Leider kommt es zum beenden der google Dienste nach deren Aktualisierung, aber auch nur wenn man explizit die Dienste aktualisiert. Ich weiß nicht ob das mit cwm/root Rechnen zusammenhängt.
Kennt jemand hier das Problem oder kann vlt helfen ?

Reflexiony said:
Hoffe es ist ok das ich auf Deutsch schreibe.
Die Anleitung ist gut, gut verständlich (Vielen Dank dafür !), und cwm und root funktionieren mit dem FNF Ifive Mini 4S problemlos, genau wie das aufspielen der aktuelle Rom 1.0.6.
Leider kommt es zum beenden der google Dienste nach deren Aktualisierung, aber auch nur wenn man explizit die Dienste aktualisiert. Ich weiß nicht ob das mit cwm/root Rechnen zusammenhängt.
Kennt jemand hier das Problem oder kann vlt helfen ?
Click to expand...
Click to collapse
Meinen Deutche ist nicht sehr gut, aber ich denke das diesen application kanst deinen problem repariert.
https://play.google.com/store/apps/details?id=com.weberdo.apps.serviceinfo

I have now written a review on the tablet
You can read it here
https://forum.xda-developers.com/android/general/review-fnf-ifive-mini-4s-tablet-t3590084

Instructions are perfect... thanks a million. Great tablet too.

Thanks, this works well. Only problem is that CWM recovery is very limited... no USB storage, no ADB, no external SD card support CWM backups work OK though.

Works!!!
Many thanks!!!
Another tablet updated and rooted.
Great work!!
PD: Waiting for TWRP, it has more tools and tactile does not work for me.

Sequence
RVA84 said:
I am trying to upgrade to version 1.0.6 and in factorytool, when I connect the tablet to the pc I get "wait for loader fail" and not updated. What happen??
Click to expand...
Click to collapse
This is the sequence that works for me:
1 - Press the - volumen
2 - Wait a second
3 - Push the power button
4 - When you see some message in the window application (in the "usb hubs") leave both buttons.

[MOD][MCU] BD375xx Sound Processor

I spent some time and I prepared SoundPatch similar to 7floor modification.
The difference is: It's no need any hardware modification, only patched MCU firmware and modified android Amplifier apk
That's how it looks:
{
"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"
}
Remember
I am not responsible for anything that may happen to your unit by flashing the mod image.
You do it at your own risk and take the responsibility upon yourself.
Update 18-08-2019 (remarks below)
@adrianpop1990 has prepared repository on GitHub. Many thanks for him
If someone are interested in contribute this mod please look at https://github.com/avp90/MTCAmpSetupBD375XXMod
Links:
Patched MCU firmwares:
MTCE_CHS → MTCE_CHS_3.15bd.zip | MTCE_CHS_3.10bd.zip
MTCE_CZ  → MTCE_CZ_2.97bd.zip
MTCE_GS  → MTCE_GS_3.17bd.zip | MTCE_GS_3.10bd.zip | MTCE_GS_3.07bd.zip | View attachment MTCE_GS_300bd.zip | MTCE_GS_2.94bd.zip | MTCE_GS_2.93bd.zip | MTCE_GS_2.88bd.zip
MTCE_HA  → MTCE_HA_3.14bd.zip | MTCE_HA_3.10bd.zip | MTCE_HA_3.06bd.zip | View attachment MTCE_HA_299bd.zip | MTCE_HA_2.89bd.zip | MTCE_HA_2.88bd.zip
MTCE_HT  → MTCE_HT_3.03bd.zip
MTCE_HXD → MTCE_HXD_3.06bd.zip | View attachment MTCE_HXD_295bd.zip | MTCE_HXD_2.93bd.zip | MTCE_HXD_2.86bd.zip
MTCE_KGL → MTCE_KGL_3.10bd.zip | View attachment MTCE_KGL_296bd.zip
MTCE_KLD → MTCE_KLD_3.01bd.zip | View attachment MTCE_KLD_294bd.zip | MTCE_KLD_2.88bd.zip
MTCE_KSP → View attachment MTCE_KSP_300bd.zip | MTCE_KSP_2.89bd.zip
MTCE_LM  → MTCE_LM_3.16bd.zip | MTCE_LM_3.10bd.zip | MTCE_LM_3.06bd.zip | MTCE_LM_3.01cbd.zip | View attachment MTCE_LM_288bd.zip
MTCE_MX  → MTCE_MX_3.13bd.zip | MTCE_MX2_3.13bd.zip | MTCE_MX_3.08bd.zip | MTCE_MX_3.06bd.zip | View attachment MTCE_MX_300bd.zip | MTCE_MX_2.94bd.zip | MTCE_MX_2.91bd.zip | MTCE_MX_2.90bd.zip
MTCE_OLS → MTCE_OLS_3.12bd.zip
MTCE_PSD → View attachment MTCE_PSD_288bd.zip
MTCE_TONE→ MTCE_TONE_3.17bd.zip | MTCE_TONE_3.06bd.zip
MTCE_WWW → View attachment MTCE_WWW_294bd.zip
MTCE_XRC → MTCE_XRC_3.01bd.zip | View attachment MTCE_XRC_294bd.zip | MTCE_XRC_2.89bd.zip | MTCE_XRC2_2.84bd.zip
MTCE_YB  → MTCE_YB_3.10bd.zip | MTCE_YB_3.08bd.zip
MTCE_YL  → MTCE_YL_3.10bd.zip
Modified Amplifier apk:
MTCAmpSetupMOD→View attachment MTCAmpSetupMOD_v1.1.apk (View attachment MTCAmpSetupMOD.apk) - It installs as a separate application
MTCAmpSetupROOT→View attachment MTCAmpSetupROOT_v1.1.apk (View attachment MTCAmpSetupROOT.apk) - Replaces the original/buildin MTCAmpSetup application (Android must be rooted)
* Notice *
Some users reported issue with installing ROOT version (I did not have that problem and still have not).
Possible solutions at posts: #486, #542, #552
Revert to previous version:
Flash your original MCU firmware
Amplifier apk:
If you installed only MOD version, uninstall it
If you applied ROOT version you must install original version MTCAmpSetup.apk
MTCAmpSetup→View attachment MTCAmpSetup.apk (mirror) - from Android 6
MTCAmpSetup8→View attachment MTCAmpSetup8.zip (mirror)- from Anrodid 8
MTCAmpSetupHCT3→View attachment MTCAmpSetupHCT3.apk (mirror)- from Malaysk ROM
Inconveniences what I noticed:
In Music app, the button marked in red (below) works not properly when Amplifier app not running in the background
Have a nice fun/use/whatever
Update:
18-08-2019 - new MCU CHS_3.15bd, CZ_2.97bd, GS_3.17bd, GS_3.10bd, HA_3.14bd, LM_3.16bd, MX_3.13bd, MX2_3.13bd, OLS_3.12bd, TONE_3.17bd, YB_3.10bd, YL_3.10bd preapred by @2uPGodCnrwa
06-05-2019 - new MCU CHS_3.10bd, HA_3.10bd, HT_3.03bd, HXD_3.06bd, KGL_3.10bd, MX_3.08bd, YB_V3.08bd preapred by @2uPGodCnrwa (link)
04-05-2019 - new MCU LM_3.06bd, HA_3.06bd, GS_3.07bd, MX_3.06bd, XRC_3.01bd, KLD_3.01bd, TONE_3.06bd preapred by @2uPGodCnrwa (link)
18-02-2019 - new MCU LM_3.01cbd preapred by @2uPGodCnrwa (link)
27-12-2018 - AmpSetupMOD & ROOT updated (restoring settings after cold reboot and range subwoofer is configurable after click/touch SUB label) LINK
25-12-2018 - new MCUs GS_3.00bd, HA_2.99bd, HXD_2.95bd, KGL_2.96bd, KLD_2.94bd, KSP_3.00bd, MX_3.00bd, PSD_2.88bd, WWW_2.94bd, XRC_2.94bd
27-10-2018 - corrected MCUs GS_2.94bd, MTCE_HA_2.89bd, HXD_2.93bd, MTCE_KLD_2.88bd, KSP_2.89bd, MTCE_LM_2.88bd, MX_2.94bd, XRC_2.89bd (restoring preamp settings after wakeup)
16-10-2018 - new MCUs GS_2.94bd, HXD_2.93bd, KSP_2.89bd, MX_2.94bd, XRC_2.89bd
01-10-2018 - added link to GitHub repository. Thanks @adrianpop1990
13-09-2018 - new MCUs GS_2.93bd, HA_2.89bd, MX_2.91bd
03-09-2018 - corrected MCU for MX_2.90
02-09-2018 - new MCU's and MTCAmpSetupMOD & ROOT: loudness Gain and HiCut
28-08-2018 - MTCAmpSetupMOD & ROOT: ability to change the slider value even without releasing it
Please don't ask for patched MCU firmware for other versions & other manufactures. Maybe, if I will find more free time, I will prepare more versions.
 
 
 

MTCAmpSetup MOD&ROOT
 
Link to GitHub repository (thanks to @adrianpop1990 for preapring this repository)
https://github.com/avp90/MTCAmpSetupBD375XXMod
Links to sources:
MTCAmpSetup refactored from Android 6 MTCAmpSetupRefactor.zip
MTCAmpSeup MOD & ROOT MTCAmpSetupMod_v1.1.zip | MTCAmpSetupMod_v1.0.zip
Projects are for AndroidStudio. Currenty I use version:
To build MTCAmpSetup MOD and ROOT at the same time use: (apk will be built in folder Output)
This is my first program for Android and first in Java so please be understanding

Info how to prepare patched MCU
First and foremost remember !!!
You make changes to the firmware at your own risk. You must be sure what you are doing. Otherwise you block/brick the unit
I hope that nobody will have to use this thread Guide how to unlock bricked MCU units
Update 26-12-2018
- new guide for MCU GS V3.00, new/updated project for AtollicTrueStudio
Needed tools:
IDA Pro
usefully files from MTCD/E MCU firmware modification
Atollic TrueStudio
any binary file editor (for example HxDen)
Files:
View attachment Guide_GS300.zip (Guide_GS288.zip) - guide/info how I patched MCU firmware version GS_2.88 (PDF in zipped file)
View attachment SoundPatchTrueStudio.zip - project for Atollic TrueStudio
SoundPatched.zip - MCU's firmware what I patched up to now (with some steps and IDA files)
What you must know yet?
This method applies for firmware version >= 2.84
A few hints at posts : #367, #370, #378
And new guidelines for new versions at posts: #374, #488, #606
Please be understanding if I have written something not clearly (especially for my English)
 
 

What?

German Guide
Its Very amazing..thanks you
I write a German Guide for the Facebookgroup
MCU Ändern und Sound Modding
!!!GERÄT KANN GEBRICKED WERDEN!!!
Aktuell für GS und HA sowie MCTD und MCTE Modelle.
Siehe Einstellungen->Über das Gerät
Wer aber, so wie ich, zB XRC besitzt, muss erst mal auf GS oder HA switchen.
Vorher Werkseinstellung gehen (Passwort meistens 126, 123456, m123456, 123456m)
Und Einstellung Exportieren
1. MCUUnmatch.apk Downloaden und installieren (kostenloses Konto erforderlich)
https://www.sendspace.com/file/ijmf13
2.MCU Downlaoden und flashen
Für GS 2.88bd MCU https://www.sendspace.com/file/wryn8n
Für HA 2.88bd MCU https://www.sendspace.com/file/j1g87m
dmcu.img auf SDCard legen, Einstellungen->Über das Gerät-> MCU Update->Startet automatisch neu, installiert sich und startet nochmal neu
3. Radio wird beim ändern der MCU piepen..(ausser man installiert GS auf GS/HA auf HA)
Dazu MCU unmatch App starten, unlock klicken und rebooten.
--------------Ab hier bei Geräten ohne MCU Switch------------
(vorher aber modifizierte MCU installieren)
4.Modifizierte Sound APK Installieren, öffnen
Als Extra App https://www.sendspace.com/file/m6sjtv
Originale App ersetzen https://www.sendspace.com/file/bw34ux
5. Dieser MOD befindet sich noch in der Aufbau Phase. zB SUB Regler hängt bei manchen...
Bei mir hingegen läuft es tadellos.
Nur auf eigene Gefahr und ohne Gewähr.
Obwohl ich dies eben in 5 min erledigt habe und noch nicht weiter zum testen kam, war der Unterschied schon enorm hörbar. Endlich arbeitet ein 2Wege System auch so wie es soll.
EDIT: Wer die MCU geswitcht hat, muss Bootlogo etc und seine Tasten neu anlernen (Werkseinstellung->126->Letzter Reiter->bei mir war es dann Touch Key Study) oder die exportierte dmcu.cfg auf die sdcard schieben, dmcu.img löschen und wieder MCU Update durchführen (Dabei wird nur die alte Konfiguraton vor dem Update wiederhergestellt)
Originalthreads bei XDA
https://forum.xda-developers.com/an...elopment/mod-bd375xx-sound-processor-t3834657
https://forum.xda-developers.com/an.../solution-version-unmatch-hope-final-t3805092

If you have no interest in modifying other firmware, I'd be interested in a write-up on how to do it.

Nasty_z said:
I tried going to stock MCU and then back to your patched MCU but the issue still remains. Not a big deal I suppose if you don't move the sliders around after properly tuning the audio once.
Click to expand...
Click to collapse
I changed slider's handling a bit. I hope it will help. Now you can move the slider and hear changes immediately. Updated MTCAmpSetupMOD&ROOT in first post.

Thanks you!! this is the best!
Loudnes gain adjustment is specified in specification. Can not you set it up?
Loudness
Gain:20dB～0dB/1dB step
・0=250/400/800Hz
・Hicut1/2/3/4
THX

emre33 said:
Loudnes gain adjustment is specified in specification. Can not you set it up?
Loudness
Gain:20dB～0dB/1dB step
・0=250/400/800Hz
・Hicut1/2/3/4
Click to expand...
Click to collapse
I looked if it could be done but for the moment I gave up. For now it is difficult.

Wadzio said:
I changed slider's handling a bit. I hope it will help. Now you can move the slider and hear changes immediately. Updated MTCAmpSetupMOD&ROOT in first post.
Click to expand...
Click to collapse
I can confirm the issue is gone now.
Can you please change the subwoofer output levels to +15 max and -15 min?
The reason for this is that it's difficult to be precise and adjust the subwoofer level especially while driving. We don't really need anything below -15. Below that point it's better to just control the gain on the amplifier connected to the subwoofer instead.

How do i install this?

updated my MX unit with GS MCU, did the unlock and installed the root apk -> works.
Though, the unlock locks again after changing factory settings, so kinda tricky
Do all settings while locked and unlock after.

Nasty_z said:
Can you please change the subwoofer output levels to +15 max and -15 min?
The reason for this is that it's difficult to be precise and adjust the subwoofer level especially while driving. We don't really need anything below -15. Below that point it's better to just control the gain on the amplifier connected to the subwoofer instead.
Click to expand...
Click to collapse
Yes, I can, but it will be good to know if other users are thinking the same.
I can remove also Subwoofer LPF (Output Select) because when we look at schematic in our case is unuseful. Only one channel is outputted/connected:

Xorit said:
Though, the unlock locks again after changing factory settings, so kinda tricky
Do all settings while locked and unlock after.
Click to expand...
Click to collapse
Hmm... interesting, I did not have such a case yet. I changed many times HA, GS, XRC, MX (original was GS). Have you got dmcu.cfg on sdcard when you are doing it?

Wadzio said:
Hmm... interesting, I did not have such a case yet. I changed many times HA, GS, XRC, MX (original was GS). Have you got dmcu.cfg on sdcard when you are doing it?
Click to expand...
Click to collapse
Actually i flashed your mod mcu, unlocked it and then flashed my saved backup.
After the boot it was locked again, so i unlocked again but noticed, that my flashed setting didnt function properly, eg no panel buttons, no canbus app.
I rebooted again and still nothing.
Went then to alter some option in factory settings and after the reboot all options where set to default..

Xorit said:
Actually i flashed your mod mcu, unlocked it and then flashed my saved backup.
After the boot it was locked again, so i unlocked again but noticed, that my flashed setting didnt function properly, eg no panel buttons, no canbus app.
Click to expand...
Click to collapse
This "feature" is known to me. In dmcu.fg is written "special" code so when you restored settings from dmcu.cfg you got 'version unmatch' again.
I rebooted again and still nothing.
Went then to alter some option in factory settings and after the reboot all options where set to default..
Click to expand...
Click to collapse
Did you finally get rid of "Version unmatch" and managed to set up your settings?

Wadzio said:
This "feature" is known to me. In dmcu.fg is written "special" code so when you restored settings from dmcu.cfg you got 'version unmatch' again.
Did you finally get rid of "Version unmatch" and managed to set up your settings?
Click to expand...
Click to collapse
yep its solved. Though I hope next time I change something this wont happen again.

Wadzio said:
Yes, I can, but it will be good to know if other users are thinking the same.
I can remove also Subwoofer LPF (Output Select) because when we look at schematic in our case is unuseful. Only one channel is outputted/connected:
Click to expand...
Click to collapse
The bass, middle and treble sliders have a frequency selection below them that resets the position of the sliders every time you switch to another frequency. (I.e only one frequency can be controlled by one slider).
This doesn't affect me too much as I use Viper4Android's equaliser but do you think it's possible to make the dB levels for each frequency stick?
Therefore, let's say I moved bass up +4db for 80hz while keeping +2db for 60hz? (If I click 60hz, slider shows +2db, if I click 80hz, slider shows +4db)
This way, we can control all of those frequencies at the same time.
Currently, raising +4db for 80hz would remove previously adjusted +2db for 60hz. (I think this is what happened when I fiddled with it. I switched back to Viper4Android so I didn't test it further. Can you confirm on this?)
This should allow for more fine tuning of audio as all frequencies can be changed. I hope you understand what I'm trying to say.

Xorit said:
yep its solved. Though I hope next time I change something this wont happen again.
Click to expand...
Click to collapse
This occurred as Wadzio explains because the configuration file was applied to the changed MCU.
From experience - only use the specific MCU manufacturer .cfg as a backup only. When changing between factory MCU types always document all settings and manually make the changes after applying the MCU update.

Nasty_z said:
The bass, middle and treble sliders have a frequency selection below them that resets the position of the sliders every time you switch to another frequency. (I.e only one frequency can be controlled by one slider).
This doesn't affect me too much as I use Viper4Android's equaliser but do you think it's possible to make the dB levels for each frequency stick?
Therefore, let's say I moved bass up +4db for 80hz while keeping +2db for 60hz? (If I click 60hz, slider shows +2db, if I click 80hz, slider shows +4db)
This way, we can control all of those frequencies at the same time.
Currently, raising +4db for 80hz would remove previously adjusted +2db for 60hz. (I think this is what happened when I fiddled with it. I switched back to Viper4Android so I didn't test it further. Can you confirm on this?)
This should allow for more fine tuning of audio as all frequencies can be changed. I hope you understand what I'm trying to say.
Click to expand...
Click to collapse
Understood (I hope). You would like to be able to remember the gain for each available frequency.
And I hope you understand me now
This mod was intended to enable a "full" control of the sound processor from Android without modifying hardware. The Chinese coded(hardcoded) the basic control of SP in firmware(in their own way) . Therefore, you had the option of setting only basic gains.
What you now want is the case of the android software and its further development.
I have plan to publish sources of MTCAmpSetup so maybe someone will want to further develop this application