yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] nighthawk658:
Yes did try to Google the errors but seem to be very little information about the errors and what does come up either relates to a different phone or states various things like changing drivers and versions of flash tool

The firmware I got is the exact firmware version I found on the phone I got the firmware version by pulling the version.bin file off of the phone and opening it in a hex program it was rather hard to find the version I can't remember the site I found it on but it all appears to be a complete set of files

In the firmware it has all the image files boot.img system.img and so on also the .elf files needed for Qfil the patch and so on

It also contains the batch files for using fastboot

In fastboot I can detect the phone using fastboot devices command it shows the serial number when executing the flashall command it will start sending data but will then just say cannot flash in locked state

I have tried ADB commands and from what I can remember it doesn't respond even ADB devices command shows nothing I assume because debugging is not enabled

To enter the recovery and or factory reset menu I tried all the combination the hold down of volume down plus power and volume up plus power only thing that appears is the CSC fastboot mode so where I would normally enter into factory reset on other phones using the standard procedure doesn't work on this phone

And I can enter EDL by holding both volume buttons and plugging in usb cable

I would like to post the last errors as I mentioned above that shows an error NAK and where it shows on each image it stops at a fixed percentage for example system.img stops at 84%

Due to the huge amount of data in the text file I can't copy it on here

Unfortunately I can't get a memory card yet stores nearby not got one in 4GB range in stock and due to restrictions can't get into city so am a bit stuck there
[General Questions and Answers] Droidriven:
Trying different versions of flashtool has been known to solve flashing issues.

As for fastboot saying it can't flash while in locked state. Have you tried connecting to fastboot and then typing the command:

fastboot OEM unlock

Or

fastboot flashing unlock

If those don't work, do a Google search for:

"How to unlock bootloader (your specific model number"

Unlocking bootloader may allow fastboot to flash your file(s). Try flashing the whole file first, if it will not flash all at once, try flashing the .img files one at a time, but, make sure you use the correct command for each individual .img, using the wrong command could flash them in the wrong partition which would then cause a bigger problem to fix.

If your file has a series of .img files in it when you extract it, then the file you have is not the file that is designed to be flashed via stock recovery. That file is not going to work with the methods described in the guide. Stop being stubborn and listen to me, download the update from the guide, download it, download it, download it.

The memory card doesn't necessarily have to be 4GB, it can be any size greater than that, you only need the card as a medium to store the file so that stock recovery can find, access and flash the file.

Not all devices boot into recovery the same way, some have different button combinations and some have a bootloader menu with recovery as one of the options on the list. Unless you have corrupted your recovery partition, you should be able to boot into recovery.

You may have to use "fastboot erase" commands to wipe the cache partition and system partition then try flashing the firmware via fastboot. E.g. "fastboot erase cache" and "fastboot erase system". This may clear out any issues that were interfering with it successfully flashing. Have you tried extracting the file that you have and then flashing each individual file one at a time via fastboot? For exampleq:

fastboot flash system <name of your system.img>

fastboot flash boot <name of your boot.img>

If you attempt to flash your .img files via fastboot, remember to put your file in your fastboot folder on your PC, then extract the various .img files from inside it. Then, with the fastboot folder open in Windows file explorer, hold the shift key then right-click on your mouse, in the menu that pops up, select "open command here".

How did this issue start? What was your original reason for flashing the device? How many different ways have you tried to flash the device and what problems did you encounter with those methods? Depending on what you have tried up to now, you may have corrupted the device to the point that normal flashing methods won't work. You may have to use EDL mode to flash it. Have you found a guide that explains how to flash your specific device using EDL mode?

Please read this post carefully and answer every question I've asked. I'm trying to approach your issue from as many different angles as possible, maybe one of them will lead to a solution.
[General Questions and Answers] nighthawk658:
here is an update

have downloaded the firmware from the site you mentioned but i will need to wait till i get a memory card and cannot do the sideloading using ADB as i cannot enable developer options but i did try it anyway and will show the error messages

i also tried the erase command you mentioned i tried the erase on the cache it seemed to have done something rather quickly but did not show any error so then tried to flash the cache image from the firmware folder and did get an error

here is the errors for both adb and fastboot commands note there is 2 errors for the flash part because i did it fastboot flash cache.bin but per your message it said to fastboot flash cache cache.bin

Under ADB commands

C:\Users\Me\Desktop\firmware flashing>adb sideload update.zip

adb: sideload connection failed: no devices/emulators found

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: no devices/emulators found

fastboot commands

C:\Users\Me\Desktop\firmware flashing>fastboot devices

J2AXHM011670RNJ fastboot

C:\Users\Me\Desktop\firmware flashing>fastboot erase cache

******** Did you mean to fastboot format this ext4 partition?

Erasing 'cache' OKAY [ 0.008s]

Finished. Total time: 0.023s

C:\Users\Me\Desktop\firmware flashing>fastboot flash cache.bin

unknown partition 'cache.bin'

fastboot: error: cannot determine image filename for 'cache.bin'

C:\Users\Me\Desktop\firmware flashing>fastboot flash cache cache.bin

fastboot: error: cannot load 'cache.bin': No such file or directory

as you asked earlier about the files within the firmware folder i have taken a screenshot so you can have a look at whats what it also should show the version details there also

i have also attached a text document (( i hope it shows up on site this time )) this is the log i saved directly from the information under the progress bar in Qfil it shows a lot of errors but i will also show what i was talking about when i mentioned it stops afrer a certain percentage

hope the information given could be helpful

again thanks for your time much appreciated
[General Questions and Answers] Droidriven:
The command to flash your cache.bin is:

fastboot flash cache cache.bin

Fastboot commands to flash .img/.bin files to their proper partitions work like this:

fastboot flash <name of partition> <name of .img/.bin>

For example, to flash system.img:

fastboot flash system system.img

Do you see how it says "fastboot flash system" and then it says "system.img"? Do you see how it says "fastboot flash"(this tells fastboot that you want to flash a file), then it says "system"(this tells fastboot which physical partition you want to flash a file to), then it says "system.img"(this tells fastboot which file you want to flash to the specified partition)? You are telling fastboot that you want to flash "this" partition with "that" file.

To flash recovery:

fastboot flash recovery recovery.img

Again, the action that you want fastboot to perform(fastboot flash) followed by the name of the partition(recovery) followed by the name of the file that you want to flash to that partition(recovery.img)

A bit overdefined but I hope this helps you understand the structure or syntax required for fastboot flash commands.

To post your .txt file, upload it to hosting site of some kind and then post a link to it here then it can be viewed here.

Also, just to be sure, place your files inside your fastboot folder on your PC, then, when you open a command window, do it by going to the fastboot folder in Windows file explorer, then, with the mouse pointer somewhere in the empty field of that folder, hold the shift key and then right click, on that menu that pops up, select "open command here", then try the commands. This "might" fix the unknown file error because it bypasses the need for a file path in your commands and flashes files located in the fastboot folder by default without having a path name in the commands, you don't have to tell it to look for the file in fastboot folder, it does it automatically if the file is located in that folder.

Other than what I have told you so far, I think I might agree with you that you may not get anything to work with the bootloader being locked and USB debugging not being enabled. You may have to resort to EDL flashing methods, it is more of a "brute force" flashing method as it bypasses the bootloader.
[General Questions and Answers] Droidriven:
Yep, that data shows the bootloader is definitely locked, I don't have anything else to offer for advice in the scenario you are in as I'm not familiar enough with your model number or hardware architecture. I'd probably get you stuck in worse position from here on. As far as I can tell since I started helping, you haven't really done anything except erase the cache.img, that shouldn't be too complicated to straighten out if you can get the firmware to flash. I don't understand why the firmware won't flash, if it is the exact same version that was already on the device, it seems like it should flash without having to unlock the bootloader. It may be due to USB debugging not being enabled instead of it being an issue with the bootloader being locked.

EDL seems to be your only option from here going forward, I doubt anything else will, its virtually your last and only shot.
[General Questions and Answers] nighthawk658:
yes does seem the bootloader or something to do with debugging is a possible issue

i have tried to use Qfil as mentioned before but that always kept throwing up errors and also has been a mix bag of activity also most of the versions of Qfil i tried never did anything other than throwing up an error almost instantly

but i did download a package named flashone and as mentioned before gave the most activity by actually trasnfering images and progress bar moving i think the progrss bar stopped at 85% with images stopping at random percentages but all in all that was more activity than it ever did before using Qflash so something is amiss somewhere

and it took me a while to figure out the exact firmware that was on the phone luckily i used San mobile Qualcomm tool and i pulled files off of the phone and looked in the version image using a hex tool and found the exact firmware

have even tried using san mobile tool to flash over the images but get an error

there is a suggestion it may be a hardware issue the fact that i can pull data off of the phone suggests its not a read problem

but to rule out any hardware issues do you know of any tools i can run a memory test look for bad sectors on the phone memory if any a way to partition around them

but i do thank you for all your assisance on this it has been very much appreciated
[Introductions] Jemchone:
I do actually need some help with my android head unit yt9217b? I believe 8” 10.1 . Anyway I having issues with the color rendering on it I was in developer opts and hit the wrong button which I couldn’t get to my homescreen or settings I’ve fixed that where it operates however the colors are different and it is out of focus where it’s unreadable I have agama as a launcher but I don’t know what else to do HELP
[Introductions] Oswald Boelcke:
A very warm welcome to XDA, and I hope you'll always find solutions and assistance to your issues here. Regarding the now specific one, did you already check this forum?

Head Units

xdaforums.com
[Touch Pro, Fuze General] darek001:
Hi,

Just hard-resetted my touch pro, and now i cant make e-mail work.

All email account settings have same as before, so its pretty much hopeless.

Internet browser works fine.

Its on t-mobile, and every time i try to connect to new e-mail account, i got error message: "cant connect with current settings".

What am i missing?

Any help?
[Touch Pro, Fuze General] annonymouse:
this is a known issue with some windows mobile devices im suffering from the same sadly

usually a hard reset should work

can u receive but not send?
[Touch Pro, Fuze General] lloydcody:
I had this and posted a fix for it somewhere. It's a stupid simple setting....

I'll find it now and post back if i can

LLOYDY
[Touch Pro, Fuze General] lloydcody:
OK - found my reply in this thread:

http://xdaforums.com/showthread.php?p=2633874

To save u the hassle I'll paste agian it here:

I've been pulling my hair out over this for a few hours and FINALLY solved it. For me the issue seem that when T-Mobile downloads all its settings to the phone the Internet service is called "T-Mobile Internet" where the email settings are trying to use "Internet" (which then no longer exists).

So in short - this is how I fixed it...

At you mail inbox: Menu > Tools > Options > Click ur email account > Edit Account Setup > press Next until you get to the Outgoing (SMTP) Mail server settings page > Click the Advanced Server Settings link at the bottom > change Network connection to your internet provider instead of the default "Internet" (e.g. mine's "T-Mobile Internet") > carry on through the pages until finished. It should now connect without the Error Synchronising message.

LLOYDY
[Touch Pro, Fuze General] darek001:
wow, thanks mate. You are the man! :)

Knew its something simple, just couldnt figure out where to look for it.

Everything works now.

Thanks a lot.
[Touch Pro, Fuze General] lloydcody:
Good to hear - no probs!

(btw - u might want to add [SOLVED] to the start of the title of this thread - helps others no it's been fixed.)

LLOYDY
[Huawei Y6 Questions & Answers] sabyrkhan:
Are there any official ROMs for Y6 (2019)?
[OnePlus Nord N200 5G] mr_reaper:
Have to be rooted and give your file manager su permissions, load Magisk app, find the log and see where the .Magisk file is

Since Magisk app v8.0.0 the advanced settings/install options for dm-verity and forced encryption won't be available on most modern devices (see Advanced Settings/Install Options for details). The tools are still there and may be accessed through various means.

Keeping dm-verity and forced encryption:

If your device supports it, the app will auto-detect if your device is encrypted and if it’s recommended to keep dm-verity enabled and the “Preserve forced encryption” and “Preserve dm-verity” will then be enabled by default. If these options aren’t enabled, you can keep dm-verity and forced encryption by checking the options for this before installing a new version of Magisk through the app.

If you install through recovery (either for the first time or as an update) run one or both of the following commands in a terminal emulator or in your recovery's terminal before installing:

echo KEEPVERITY=true>>/cache/.magisk

echo KEEPFORCEENCRYPT=true>>/cache/.magisk

If you can't access /data (TWRP can't decrypt, etc) you can instead use either /data/.magisk or/system/.magisk, but please note that using /system/.magisk isn't systemless.

Some devices need to keep dm-verity enabled to work properly. One example is some Huawei devices that might otherwise experience weird behaviour or bootloops.

Disabling dm-verity and forced encryption:

If you on the other hand want to disable either dm-verity or forced encryption, you can go about it the same way as described above. If you're using the .magisk file method, just change KEEPVERITY and/or KEEPFORCEENCRYPT in the commands to false:

echo KEEPVERITY=false>>/data/.magisk

echo KEEPFORCEENCRYPT=false>>/data/.magisk

If you can't access /data (TWRP can't decrypt, etc) you can instead use either /cache/.magisk or/system/.magisk, but please note that using /system/.magisk isn't systemless.

If disabling verity through Magisk doesn't help, you can try the following command (provided that your device has a vbmeta.img):

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

think its from here: https://forum.hovatek.com/thread-32719.html

or

https://www.reddit.com/r/Magisk/comments/mvk9j9
[OnePlus Nord N200 5G] Didgeridoohan:
*cough* Copy-pasta... *cough*

When citing a text it's customary to also give the source.
[OnePlus Nord N200 5G] mr_reaper:
fixed my bad
[OnePlus Nord N200 5G] Didgeridoohan:
He, he...

I guess you got it from that Reddit link, but look closer at the bottom of that post for the actual source (hint: look even closer at the URL). :)
[OnePlus Nord N200 5G] edale1:
Computer Tower: $1500

Monitor: $500

Mouse and Keyboard: $50

Internet Service: $50/month

Accidentally plagiarize one of the mods... Priceless.

LOL
[OnePlus Nord N200 5G] mr_reaper:
oh ****, LMFAOOOO. my bad was just trying to help *shurgs*
[Moto G 5G Questions & Answers] eurovive:
Hi there. Got ATT version of One Ace 5G. Problem with phone information menu i.e *#*#4636#*#* - it doesn't run. Tried another dialer same problem. Imei code shows and some debug stuff. If anyone have solve for this problem please write.

Nick
[Moto G 5G Questions & Answers] eurovive:
System repair menu can be entered by turning off phone, then pressing Power + Volume down key , then releasing.
[Moto G 5G Questions & Answers] eurovive:
Changing ROM will be solution.
[Tilt, TyTN II, MDA Vario III General] NoFatePPC:
before i install a rom with Manila... Is this possible?

I really like PhoneAlarm becauase of all its advanced features (profiles, Activesync settings, ringtones, reminder sms settings,...)

But i dont use the buttons on the today screen, BUT phonealarm needs to be activated as a today plugin to work...

Thnx
[Tilt, TyTN II, MDA Vario III General] dalavar:
Not sure about manila compatability but there is an invisble skin for PhoneAlarm on their site so you can have it run but not see it on your home screen.
[Tilt, TyTN II, MDA Vario III General] NoFatePPC:
perfect, thats the answer i was looking for :)

now indeed, it has to work with manila :S

we shall see
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] enau_kongkham:
Anyone had any success flashing xiaomieu on ALOITHIN devices??

Mine keeps on sayin that the rom is for aloith... And I can't find any xiaomieu for ALOITHIN...
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] NULL2:
I have seen in YouTube that people just change variables inside bat or sh file, from alioth to aliothin. Not sure if it helps
[Realme 6 Questions & Answers] joeyharm200:
Hi, i've been wondering what happened to my device after i install orangefox recovery(latest) then flashed new lineageOS(latest) on my realme 6(rmx2001) i can't enter recovery mode. i tried sp tool but it won't detect on brom.bat exe. is there any fix to this? thanks if someone can help me. currently stuck in

oplus verify fail

need to verify signature to another brand

oplus verify pass

fastboot verify success

fastboot_unlock_verify ok
[Realme 6 Questions & Answers] joeyharm200:
nvm, fixed using sp flashtool. uninstalled all mediatek drivers, removed the battery and and run Mediatek Bypass Tool by MCT TEAM then run spflashtool in download mode then plugged. it works as intended.

#fixedby this tutorial:https://xdaforums.com/t/guide-unbri...india-6s-using-spflash-tool-for-free.4222027/
[Realme 6 Questions & Answers] soler37:
Bump, thanks! THIS SHOULD BE STICKIED!!!
[Google Pixel 6 Pro] Opensystem:
Hey guys, looking for confirmation. I recently started exploring this phone's VRR to see if I could find a way to force max refresh of 90hz on the pro to try and save battery. Ran into trouble and found this video showing the phone only goes from 60-120hz:

I've heard arguments against being able to see the refresh rate with the developer options tool, as refresh rates of LPTO displays happen at lower (hardware) level than the "show refresh rate" tool (software) can view.

Many VRR displays use profiles rather than true "seemless" switching, ie: 1hz, 10hz, 11hz, 24hz, 30hz, 40hz, 60hz, 120hz.

Does anyone have the necessary expertise to tell me what's going on here? Do our Pixel 6/Pro displays have two refresh profiles, 60hz and 120hz, and that's it? Or is this a failure of the methodology being used in the above video's test? Further, is this a hardware limitation, or something that can be fixed via a software update in the future?

Thanks to anyone with some insight

*Edit* Here's a pic of the website "smartprix" claiming the P6P is variable down to 10hzView attachment 5464893
[Google Pixel 6 Pro] Opensystem:
Here's another troubling post about the display on this thing, if anyone is interested. I'm hoping we can get some of these things addressed in updates, because I really love this phone. I just want to find a way to make the battery last a bit longer..

View attachment 5464901

Are these issues that perhaps custom kernels may also address? Sorry if any of these are obvious questions, I just plan on keeping this phone a long time and hate seeing these head-scratching issues. Thanks
[Google Pixel 6 Pro] Batfink33:
He also mentions in that thread that this is pretty much unfixable. I wouldn't bet on custom kernels etc being able to fix this.
[Google Pixel 6 Pro] Morgrain:
It is fixable (in theory).

The hardware supports a variable refresh rate from 10-120 Hz, so in theory that can be used "fully". Meaning 10, 30, 60, 24, 90, whatever.

BUT - Google locks it down. As of now, we do not know why, or how.

Maybe someone will find/make a fix/a mod one day, maybe Google will do it.

Right now we do not have a fix, and don't know more. Not much more to say.
[Google Pixel 6 Pro] gpvecchi:
So, would it be better to force 120 Hz in developer options?
[Google Pixel 6 Pro] Opensystem:
I don't see how, it would just cost more battery. The phone ramps up to 120hz fine, it's lower frequencies that are the issue. Which leads to yet another thing that's compounding battery problems
[Google Pixel 6 Pro] mz3r0:
Is it possible to get different control with a custom ROM?
[Google Pixel 6 Pro] Flyview:
Interested to know if you've found any updates on this in the almost 2 years since you asked. Setting the max refresh rate to 90Hz would be cool!
[Google Pixel 3 Questions & Answers] northpoleforce:
if you can offer or sell, contract with me

northpoleforce@qq.com
[Touch CDMA Windows Mobile ROM Development] zfly9:
Has anyone tried this with the Vogue??

http://xdaforums.com/showthread.php?t=430718
[Touch CDMA Windows Mobile ROM Development] The Signal:
Yes i tried it and got it to load up but with no imagines and it was real slow .But i'm still trying a few things.
[Touch CDMA Windows Mobile ROM Development] fallingup:
there are no opengl drivers for the vogue. its gonna be slow and super unusable.
[General Questions and Answers] samuel103195:
Can you brute force a salted hash with a unknown salt?
[General Questions and Answers] Deleted member 1890170:
IMO the salt must be known to retrieve the unsalted hash.
[General Questions and Answers] samuel103195:
Does this mean what I am trying out is impossible?
[General Questions and Answers] Deleted member 1890170:
Not impossible, but would require a computer with enormous computing power.

For example, imagine you have a small salt with 4 digits, each from 0-9. You don't know its value.

So you set all the numbers back to 0 and try them one by one: 0001, 0002, 0003, and so on until it matches. In the worst case scenario, it would take 10,000 tries to find the salt used.
[General Questions and Answers] samuel103195:
Is this always the case even if I have the hashed value just doesn't know to decrypt it.