yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] dfrliltiger:
have a wiko viox phone and a friend told me to do format all on it to do a fresh install,well i know nothing at all about this kind of phone so im asking can some body help me to get it back up and running all i see is a red light on top and a blank screen,any and all hep is welcome if i could i would by you some coffe but theres nothing here for me to do so, so back to the phone please help me.:cry:
[General Questions and Answers] xXx yYy:
Preparation:

1. Find the Stock ROM:

Unfortunately, Wiko doesn't always provide easy access to stock ROMs on their website. You'll need to search online for your specific Wiko Viox model variant (e.g., Wiko Viox 3+ Stock ROM). Be cautious when downloading from untrusted sources.

2. Download Flashing Tool:

You'll likely need a specific flashing tool based on the Wiko Viox model. Common tools include SP Flash Tool or Smartphone Flash Tool. Search for "[Wiko Viox model] Flash Tool download".

Re-flash Instructions (General Guidance - refer to specific guide for your Wiko Viox model):

1. Extract Downloaded Files: Extract the downloaded Stock ROM package and Flashing Tool.

2. Install Drivers: Some Flashing Tools require MediaTek drivers for your computer to recognize the phone. Find and install the appropriate drivers.

3. Launch Flashing Tool: Run the Flashing Tool as administrator.

4. Load Scatter File: Within the Flashing Tool, locate the scatter file (usually named "scatter.txt") found in the Stock ROM package. This file tells the tool how to flash the ROM.

5. Select Flashing Options: Depending on the Flashing Tool, you might have options to choose what parts of the ROM to flash. Consult your specific guide for recommendations.

6. Prepare Phone: The guide will likely instruct you to put your phone in a specific flash mode (often involving button combinations while booting).

7. Connect Phone: Connect your Wiko Viox to your computer using a USB cable while in flash mode.

8. Start Flashing: In the Flashing Tool, initiate the flashing process according to the specific tool's instructions.

9. Wait for Completion: The flashing process might take some time. Do not interrupt it!

10. Reboot Phone: Once complete, the phone should reboot automatically.
[General Questions and Answers] mvikrant97:
Is it ?

View attachment 6092583
[General Questions and Answers] dfrliltiger:
wiko voix u616at
[General Questions and Answers] dfrliltiger:
wiko voix u616at

mtk auth tool says?

Waiting for mtk usb device... ok

BootMode : BootLoader[COM7]

USBDriver : wdm_usb

DriverVersion : 3.0.1504.0

DriverDate : 1-22-2015

ProviderName : MediaTek Inc.

Connecting to BootROM......

● Chipset MT6761

● Identifier Helio A22

● Info 8A00_CA01_0200_Merlot

Switch preloader to bootrom...crash succeed!

Waiting for mtk usb device... ok

BootMode : BootRom[COM8]

USBDriver : wdm_usb

DriverVersion : 3.0.1504.0

DriverDate : 1-22-2015

ProviderName : MediaTek Inc.

Connecting to BootROM......

● Chipset MT6761

● Identifier Helio A22

● Info 8A00_CA01_0200_Merlot

● MEID:8B81C69F0DE013F57F17B2B45F965E6F

● SecCFG SBC

Disabling watchdog..

Disable BRom protection...

BRom_MT6276::Brom:err:(1D08)

send usb_ctrl data ...!

MTK Auth Disable(SLA/DAA) error!
[General Questions and Answers] dfrliltiger:
mtk auth says?

Waiting for mtk usb device... ok

BootMode : BootLoader[COM7]

USBDriver : wdm_usb

DriverVersion : 3.0.1504.0

DriverDate : 1-22-2015

ProviderName : MediaTek Inc.

Connecting to BootROM......

● Chipset MT6761

● Identifier Helio A22

● Info 8A00_CA01_0200_Merlot

Switch preloader to bootrom...crash succeed!

Waiting for mtk usb device... ok

BootMode : BootRom[COM8]

USBDriver : wdm_usb

DriverVersion : 3.0.1504.0

DriverDate : 1-22-2015

ProviderName : MediaTek Inc.

Connecting to BootROM......

● Chipset MT6761

● Identifier Helio A22

● Info 8A00_CA01_0200_Merlot

● MEID:8B81C69F0DE013F57F17B2B45F965E6F

● SecCFG SBC

Disabling watchdog..

Disable BRom protection...

BRom_MT6276::Brom:err:(1D08)

send usb_ctrl data ...!

MTK Auth Disable(SLA/DAA) error!
[General Questions and Answers] xXx yYy:
The error "MTK Auth Disable(SLA/DAA) error!" you're encountering with the flash tool indicates an issue with authentication on your MediaTek device.

There are two main reasons you might see this error:

You're trying to flash something unauthorized:

The firmware or files you're trying to flash might not be signed by the manufacturer, triggering the authentication check to fail.

You're attempting to bypass security:

Some tools or methods might try to disable SLA/DAA for flashing purposes.

That's what you should avoid:

Disabling Security:

Disabling SLA/DAA can leave your device vulnerable. It's generally not recommended unless you absolutely know what you're doing and understand the risks.

Generic Tools:

Avoid tools that specifically advertise "MTK Auth Bypass." These tools might be unreliable and potentially harm your device.

Instead, consider these options:

Authorized Firmware:

Ensure you're using firmware officially provided by your device manufacturer.

Contact Support:

Reach out to your device manufacturer's support for assistance.
[General Questions and Answers] dfrliltiger:
+ thank you a Million times thankt you going to call them right now.
[General Questions and Answers] dfrliltiger:
they told me to find this firmware :wiko voix u616at

(8A00_CA01_0200_Merlot) look for this firmware

Helio A22

Chipset MT6761

CPU: MT6761

(SW:0200 Ver: CA01) this on A22) can you guys help me out?

I would be very thankful and if i could i would buy you some coffe as well.
[Touch HD Windows Mobile ROM Development] Boady:
I don't like to see "smart mobility" anymore on my starting boot-screen ! :mad:

Does somebody knows, how to change it ? :confused:

Perhaps it's possible to change over extraction by a kitchen to edit it.

But I don't know how to and which file has to be changed ?

Thanks in advance for an advice.
[Touch HD Windows Mobile ROM Development] HDuser:
Well here is an option.

Navigate to the balckstone root page the one were all four sections are.

The under sub forum balckstone use the "search the forum"

The type in splashscreen

Please read the stickys and the anouncements before you post your first post. That way you might get more replies that views.

http://xdaforums.com/announcement.php?f=453
[Touch HD Windows Mobile ROM Development] Boady:
Sorry, I wasn't asking, how to search something.

In the existing threads there is nothing that solves this problem.

I think you don't understand my question. I don't want to change the "splashscreen" of TouchHD-Animation or WindowsMobile-Welcomehead.

I mean the first starting Boot-Splash, that is black and where is written "smart mobility".
[Touch HD Windows Mobile ROM Development] paolonio:
There is already an identical 3d here

http://xdaforums.com/showthread.php?t=460622

Unfortunalety no solution yet.

I'm trying the Kaiser method, but the HTCRT does not support yet the Blackstone:o
[Touch HD Windows Mobile ROM Development] duttythroy:
My HTCRT which I use but u need to modify urs is

[Info]

Magic=kateiloveyou

Version=1003

[Defaults]

DefCountryId=11111111

DefVersionId=1.00.000.0

DefLanguageId=WWE

[Devices]

BlackStone=1

[BlackStone]

Experimental=0

ModelId=BLAC*****

SignMaxChunkSize=64

RomSections=4, "0x200,SPL,524288,TRUE", "0x600,Splash,655360,FALSE", "0x301,Radio,20840448,TRUE", "0x400,OS,0,FALSE"
[Touch HD Windows Mobile ROM Development] paolonio:
A very big thans Dutty!!!!!!

Updated the HTCRT, now I'm facing another problem...

Also the "nb_image converter" from madkat and (not sure 100%) the "SplashTool" from pof needs to be updated for the new image size (originally made for the classic QVGA 240x320)...

Waiting for some HD's cook suggestion !!!
[Touch HD Windows Mobile ROM Development] paolonio:
Done!!!!!!!!!!!!
[Touch HD Windows Mobile ROM Development] paolonio:
I don't know why, but the original Splash have a size of 786432, instead of the 655360, so I changed this value and flashed the nbh.... WORKS GREAT!!!!!!!!!

Follow the guidelines of mr.POF here http://xdaforums.com/showthread.php?t=405118 and then use the HTCRT to compile the *.nb file
[Touch HD Windows Mobile ROM Development] borce_razor:
Somebody explane more and make simple tutorial please
[Touch HD Windows Mobile ROM Development] paolonio:
The guide is here: http://rapidshare.com/files/179849983/Splash_HD.rar

In the package there is also a (poor) WWE pfd with the instructions :D

This is an example
[Touch HD Windows Mobile ROM Development] Isotopes:
Thanks for the link. :eek:

Finally, I can solve the problem with the black border at the bottom. :)

The picture is now on the whole screen displayed. :D
[Touch HD Windows Mobile ROM Development] paolonio:
Happy to ear some positive comments ! ! ! ! !

Thanks:D
[Touch HD Windows Mobile ROM Development] HDuser:
Would you please mind opening a wiki page with your findings and thus help others ??
[Touch HD Windows Mobile ROM Development] paolonio:
Added link to the HD-Blackstone Wiki pages :)

Thanks
[Touch HD Windows Mobile ROM Development] Boady:
Now I realized a very good solution ! :)

1. Extracting original 02_MainSplash.nbh to 02_MainSplash.nb with (NBHUtil) NBH-Utility V0.9 of Olipro 2008

2. Converting 02_MainSplash.nb to 02_MainSplash.nb.bmp with nbimg-1.1win32

3. Changing 02_MainSplash.nb.bmp by painting with my creations of Intro

4. Converting 02_MainSplash.nb.bmp to Splash.nb with nbimg-1.1win32

5. Editing XML of NBHUtil with:

<device name="Touch HD" chunksize="64">

<ModelID>BLACK*****</ModelID>

<CID>11111111</CID>

<Ver>1.00.BlackStone</Ver>

<Lang>GER</Lang>

<Item value="0x200">SPL</Item>

<Item value="0x301">Radio</Item>

<Item value="0x400">OS</Item>

<Item value="0x600">Splash</Item>

</device>

6. Building Splash.nbh with NBHUtil

7. Flashing Splash.nbh with customruu.exe

Big Thanks to all, who gave the resources to solve this problem :)
[Touch HD Windows Mobile ROM Development] The_Steph:
Boady,

I used your procedure but unfortunately I amm still facing the black bottom issue. Any idea to solve it?

The_Steph
[Touch HD Windows Mobile ROM Development] paolonio:
For those who are still facing the problem with the splash screen...

Here you can download the quick guide ITA + WWE and tools

http://rapidshare.com/files/179849983/Splash_HD.rar
[Touch HD Windows Mobile ROM Development] avimak:
thanks, i'll give it a shot :)

YES! I did it ;)
[Touch HD Windows Mobile ROM Development] The_Steph:
Tested and approved.

The_Steph
[Touch HD Windows Mobile ROM Development] onoz:
One question.

Will the splash screen be updated to default one when upgrading ROM?

Do I need to redo this after ROM upgrade?

TIA
[Touch HD Windows Mobile ROM Development] The_Steph:
onoz,

It depends on the ROM cookers. Some are replacing SplashScreens, some not.

The_Steph
[Touch HD Windows Mobile ROM Development] onoz:
Thanks!!

I've successfully done it, many thanks for sharing.
[Touch HD Windows Mobile ROM Development] axbaquero:
Excelent! It work´s good job tks, for the manual.
[Touch HD Windows Mobile ROM Development] sbettencourt:
Please... Someone can please tell what name should i give to .nbh file of splash screen to flash with RUU???

Thank's
[Touch HD Windows Mobile ROM Development] kieboy:
Can you please care to explain how to eliminate the black border cutting off the pic? i did as intructed in the forum but still no effect.

Generated the .nb file with these parameters: nbim -F 02_MainSplash.bmp -w 480 -h 800 -p400

i got a file of 768,432 as what needed.
[Touch HD Windows Mobile ROM Development] kieboy:
Got it finally, mixed up with the numbers, its 786,432 not 768,432.
[Touch HD Windows Mobile ROM Development] Stalix:
could someone please modify this splash nbh to have it say T8285 instead of t8282.

i know its a minuscule request but i'm a stickler for detail. thanks all.
[Touch HD Windows Mobile ROM Development] sbettencourt:
If you don't know how to do the .nbh file, i can do it... for now, here it is the change in the pic...
[Touch HD Windows Mobile ROM Development] tuppaacc:
hey guys I was wondering if THIS COULD BE COMPAIBLE WITH HD2!?!

just making some changes for it to work on hd2

thanks :D
[Touch HD Windows Mobile ROM Development] Stalix:
I have made the proper resolution bmp file, and converted it to .nb but i cant seem to figure out how to get it to nbh.

could someone make this image into a flashable nbh file.

nervermind got it working by just adding the -D BLAC120 command.
[Honor 8 Lite Questions & Answers] Omar_62:
i am trying to connect honor 8 lite to my pc (runs ubuntu)

the pc does not show the device at all and i also had this issue on windows

using adb it shows daemon started and then not show the device in its list

this is very concerning and i need to back up the data for use on my pc

any help?
[Honor 8 Lite Questions & Answers] Omar_62:
bump
[Honor 8 Lite Questions & Answers] BujangTan:
You can try to Enable USB Debugging, to do this go to setting - about device - tap on build number multiple times until you see a pop up saying you've enabled Developer options. Now, again go to settings - developer options then enable USB Debugging.
[Honor 8 Lite Questions & Answers] Omar_62:
I did do this. It won't connect, even to Linux machines. I'm suspecting a dead USB port. Can you tell me how to downgrade using dload? (EMUI 8 to EMUI 5) I also was looking at root using OTG but it would not work as that needs working USB.
[MTCD  Android Head Units Q&A] fiuto11:
Good morning,

I have an Isudar PX6 Rk 3399 (1024x600)

Android 10 - Kernel version 4.19.1111+

MCU MTCE_LY_V3.65_1 Oct 27 2020 17.03.57

A few days ago my radio wouldn't start anymore, so I installed the stock ROM GS11_rk3399 from Yandex. The radio restarted and everything works, even the steering wheel controls or the door opening indication. The problem, however, is that when I try to log in to the Google Play Store, I get a black screen. If I try to update Google apps, when I try to log in, the apps crash. I tried wiping and clearing the app data, I tried updating and adding various versions, but nothing. I also tried adding the Android System WebView but it doesn't change anything. The only Google app that works, only if I don't update it, is Chrome. I also tried installing other stock ROMs, both earlier and later ones, but the same result. I'm trying to install hak9k or malaysk now but I get the error: Verifying update package.Update package verification took 56.3 s (result O).

Installing update. target rockchip/rk3399/rk3399:10/qq2a.200305.004.A1/eng.htc2.20210407.165629:userdebug/test-keys assert failed:update_dynamic_partition(package_extract_fi le("dynamic_partitions_op_list"))

E:Error in /mnt/usb_storage/update.zip (status 7)

Any help?

View attachment 6092512View attachment 6092513View attachment 6092514View attachment 6092515View attachment 6092516
[MTCD  Android Head Units Q&A] Pavel-71:
You probably installed a firmware that has a problem with webview. Try installing a newer firmware: #9

A status 7 error means that your current firmware does not allow downgrading. The only solution is to reinstall the recovery using IMG, then install the required OTA update (Hal9k, Malaysk). #1
[MTCD  Android Head Units Q&A] fiuto11:
I finally installed Malaysk and upgraded to full version v5, but I'm experiencing issues with slow GPS fix and Zlink. Can you help me improve the GPS fix timing? Perhaps by working on the gps.conf file and adding my location server? Additionally, would updating the MCU be helpful? I tried to find an updated version of mine (MTCE_LY_V3.65_1 Oct 27 2020 17:03:57), but it seems there hasn't been any updates beyond my version.

Regarding Zlink, I'm encountering the same problem as before:

"Neither MFI nor Dev-Id found"

I'm unable to update or uninstall/reinstall Zlink without encountering a black screen and being unable to boot the ROM.

Any help?

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] karras_vagelis:
hello i am a new member and i am teasing my diamond.i tryed to do this http://xdaforums.com/showthread.php?t=460295 and ι made the mess!!please help:o

now i see only the "ok" and "help" menu before opening the TF3D menu screen.
[Touch Diamond, MDA Compact IV Themes and Apps] DfenZ:
since it's installed by cab, i believe you can just uninstall it. First disable TF3D.Then uninstall and enable TF3D again. think that atleast will restore youre TF3D to normal.
[Touch Diamond, MDA Compact IV Themes and Apps] karras_vagelis:
yes dfenz we had the same conference but i install it at the internal memory and now it doesnt exists
[Touch Diamond, MDA Compact IV Themes and Apps] harpreet1988:
If worse comes to worst you can hard reset your Diamond. Look in the wiki on how to do this
[Touch Diamond, MDA Compact IV Themes and Apps] karras_vagelis:
oh no please not again...there is something that i can do.
[Touch Diamond, MDA Compact IV Themes and Apps] arcsvibe:
Trust me it is better to hard reset. I had a problem like yours and doing the hard reset did the trick.
[General Topics] i9003noob:
I have been using roms from Elite Development/ TN.

I wanted to know how can start with this modding journey
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] Alisson1397:
When updating to Android 14, that beautiful traditional Motorola ambient screen was replaced, is there any way to revive it? Go back to using the A13's ambient screen?
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] Don Kihoty:
You mean lock screen and AOD?

No, its broken.

Will it be fixed? Whi knows.
[Nokia 3 ROMs, Kernels, Recoveries, & Other Develop] IsHacker:
View attachment 6092546

Team Win Recovery Project, or TWRP for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface, with no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Download Link: https://drive.google.com/file/d/1QwDdBF0iDO5siZ0oA9H-xahTdO3MzeSS/view?usp=sharing

Flashing: - fastboot flash recovery TWRP_3.5.2_heart.img

Internal storage is showing 0 MB?

Format data, It Removes Encryption, but temporarily.

Permanent (but partial) solution: go to developer options and select "convert to file based encryption" and then tap "wipe and convert". It will format data and enable fbe, and you can mount and view /data in the recovery, but your internal storage will just have files and folders with random letters and numbers.

Extra features:

1.Responsive touch in the "Mount /system read-only?" screen

2.Works with latest Android 9 (Pie) stock ROM

3. Works with LineageOS 14.1 and LineageOS 15.x

4-Default language is English

5. CPU Temparature is realtime and correctly shown

6.The recovery is 64-bit

Bugs:

1.Battery is always 50%

2.Can't decrypt data without formatting

3.Settings are reset after reboot

4-ADB sideload doesn't work

Credits:

1.TeamWin

2.CM/Lineage/Omni Android

3.Me

Kernel: Prebuilt kernel
[Nokia 3 ROMs, Kernels, Recoveries, & Other Develop] IsHacker:
CHANGELOG (Download link updated):

1. Fixed ERROR CODE 7 when flashing OTA from TWRP.
[Nokia 3 ROMs, Kernels, Recoveries, & Other Develop] notnoelchannel:
can you link lineageos thread? thanks
[Nokia 3 ROMs, Kernels, Recoveries, & Other Develop] IsHacker:
The link in the lineage os thread is dead, but you can download from here: https://androidfilehost.com/?fid=4349826312261770632
[Nokia 3 ROMs, Kernels, Recoveries, & Other Develop] notnoelchannel:
can you link me the lineageos 15 build? thanks
[Nokia 3 ROMs, Kernels, Recoveries, & Other Develop] IsHacker:
Here you go.

lineage-15.0-20170901-UNOFFICIAL.zip

drive.google.com
[Samsung Gear VR] advadv:
I have a Samsung S7 that works well with Gear VR. But, it is an old model and the battery and CPU don't handle the experiences properly. Recently, I bought a second hand Xperia 1 (with a 4K OLED screen), with the hope of being able to install the different apps and run Oculus/Gear services on it. Unfortunately, and as I have read previously in several posts, it seems not be possible.

I manage to install the following apps:

- Oculus

- Oculus App Runtime

- Oculus Browser

- Oculus Core Mobile Services

- Oculus Home

- Oculus Media Plugin

- Oculus System Activities

- Oculus System Driver

- Oculus System Utilities

- Oculus VR

- GearVR System

- GearVR SetupWizard

- GearVR Input Service

Except GearVR Service, that fails with error "INSTALL_FAILED_SHARED_USER_INCOMPATIBLE:[...] com.samsung.android.hmt.vrsvc has no signatures that match those in shared user android.uid.system"

I also installed other apps, that, as far as I read are not needed:

- Meta App Installer

- Meta App Manager

- Meta Quest

And GearVR apps: Catan VR, Gala Launcher, Insta360VR, Samsung Gallery VR, Samsung VR Mobile, Youtube VR.

But the end result is connecting the glasses does nothing (I can use the pad as a trackpad, mouse shows in the screen), no head tracking, no launch of Oculus Home or anything else. Looking for information I found that there is some people that seem to have been close (or even make it work?) in the past, specially this two threads:

- https://xdaforums.com/t/mod-vr-dev-samsung-gear-vr-on-other-devices.3588601/page-3

- https://xdaforums.com/t/port-gear-vr-software-to-other-android-device.3540402/

I tried several options with LuckyPatcher (unsigned, resigned app...) but my Xperia 1 is not rooted, and it is a japanese version with the bootloader blocked (apparently possible to unlock paying 20$, but I didn't for now).

I think the best chance is a GearVR Services modified app?

Any ideas will be really appreciated!
[Samsung Galaxy S20 FE Questions & Answers] Trace.Oneil:
Hello everyone. So as we all know by now im sure, software updates and support for the S20 FE is all but done with only quarterly security updates to look forward to now.

With that in mind, i am starting to look in to rooting my phone so that i can update to Android 14 and so on. What is confusing me though, is the fact i live in South Africa and to my knowledge, the model i have was sold as an exynos model as it only has 4g and we never got the 5g Snapdragon varient here.

However, when i run tests such as Geekbench or Antutu, my device comes up as a Snapdragon model which is confusing me as i have always been under the impression it is an exynos 4g device as that it what we got in my country. My device model is the SM-G780G dual sim. Can anybody please clarify for me if this is in fact a Snapdragon device or did they also come with the Exynos chipset in the same model too?
[Samsung Galaxy S20 FE Questions & Answers] Zxalilh:
The SM-G780G has a Snapdragon 865 5G. It's basically a S20FE 5G without the 5G.
[Samsung Galaxy S20 FE Questions & Answers] Trace.Oneil:
Thank you @Zxalilh. So in other words it was wrongly promoted here in South Africa as having an Exynnos chip. If its a Snapdragon device, why is it that i cant seem to adjust my RGB display colours on it since new?

Usually one can see a colour change when adjusting the red, green and blue colour sliders and on my device it makes no visible change. I always figured it had something to do with it being an Exynnos device, clearly that cant be it now that it is actually a Snapdragon device.
[Samsung Galaxy S20 FE Questions & Answers] Zxalilh:
Could you define what you mean by "adjusting the colours of the display"?
[Samsung Galaxy S20 FE Questions & Answers] Trace.Oneil:
Hi, yes. In the settings menu, display settings if you tap screen mode, it opens to advanced settings. There you have your white balance adjustment with the RGB sliders.

Usually when adjusting these, you see some sort of change to your screen. Either more red, green or blue which has an affect on the screen that is visible. With my phone, these dont seem to be working as there is no noticeable change to the screens output colour at all.
[Samsung Galaxy S20 FE Questions & Answers] Zxalilh:
It's probably just a software problem. Reflashing stock might help.
[MTCB Android Head Units Q&A] tayran.ozturk:
Hello, I am having problems with sleep mode and steering wheel buttons not working. Please share MTCB MX V2.55 ROM
[MTCB Android Head Units Q&A] tayran.ozturk:
@Malaysk
[MTCB Android Head Units Q&A] tayran.ozturk:
Please help me